UCI transmission associated with OCC based pusch in NR ntn

Abstract

Uplink control information (UCI) may be transmitted with an orthogonal cover code (OCC)-based physical uplink shared channel (RUSCH) in a non-terrestrial network (NTN). A device (e.g., a wireless transmit / receive unit (WTRU)) may include a processor. The device may receive an indication of an OCC length associated with an uplink (UL) RUSCH transmission. The processor may determine that the OCC length is greater than a threshold. The device may determine that a condition is satisfied, wherein the condition is determined to be satisfied based at least on the determination that the OCC length is greater than the threshold. The device may, based on the determination that the condition is satisfied, if an UCI is to be multiplexed, and / or if the UCI is available prior to a RUSCH preparation time, send the UCI via a higher layer signaling.

Description

UCI TRANSMISSION ASSOCIATED WITH OCC BASED PUSCH IN NR NTNCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 572,654, filed April 1 , 2024, the contents of which is incorporated by reference herein.BACKGROUND

[0001] Mobile communications using wireless communication continue to evolve. A fifth generation may be referred to as 5G. A previous (legacy) generation of mobile communication may be, for example, fourth generation (4G) long term evolution (LTE).SUMMARY

[0002] Systems, methods, and devices are described herein that may be associated with an uplink control information (UCI) transmission associated with an orthogonal cover code (OCC)-based physical uplink shared channel (PUSCH) in a New Radio (NR) non-terrestrial network (NTN). A wireless transmit / receive unit (WTRU) may include one or more of the following: a processor, a memory, or a transceiver (e.g., a transmitter and / or receiver). The WTRU may be configured to perform one or more of the following. The WTRU may receive an indication of an OCC length associated with an uplink (UL) PUSCH transmission. The WTRU may determine that the OCC length is greater than a threshold. The WTRU may determine that a condition is satisfied. The condition may be determined to be satisfied based at least on the determination that the OCC length is greater than the threshold. The WTRU may, based on the determination that the condition is satisfied, if an UCI is to be multiplexed and / or if the UCI is available prior to a PUSCH preparation time, send the UCI via a higher layer signaling.

[0003] A method may include one or more of the following. The method may include receiving an indication of an OCC length associated with a UL PUSCH transmission. The method may include determining that the OCC length is greater than a threshold. The method may include determining that a condition is satisfied. The condition may be determined to be satisfied based at least on the determination that the OCC length is greater than the threshold. The method may include, based on the determination that the condition is satisfied, if an UCI is to be multiplexed and / or if the UCI is available prior to a PUSCH preparation time, sending the UCI via a higher layer signaling.

[0004] The WTRU may be configured to perform (e.g., and / or the method may similarly include) one or more of the following. For example, the WTRU may determine that the UCI is to be transmitted in a slot carrying the UL PUSCH transmission. The condition may be determined to be satisfied further based on the determination that the UCI is to be transmitted in the slot carrying the UL PUSCH transmission. The WTRU may, based on the determination that the condition is satisfied and / or if the UCI becomes available after the PUSCH preparation time, send the UL PUSCH transmission without the UCI. The WTRU may determine a transport block size based on the OCC length. The WTRU may determine a transport block processing over multiple-slot (TBoMS) length as a function of the OCC length based on the determination that the condition is satisfied. If the UCI is to be multiplexed and / or if the UCI is available prior to the PUSCH preparation time, the UCI sent via the higher layer signaling may indicate HARQ ACK feedback, a configured grant (CG)-UCI, and / or channel state information. The higher layer signaling may be a medium access control element (MAC CE). The WTRU may disable HARQ feedback based on the determination that the condition is satisfied.

[0005] Systems, methods, and instrumentalities are described herein related to an UCI transmission associated with an OCC-based PUSCH in a NR NTN.

[0006] An example device may include a processor configured to perform one or more actions. For example, a device (e.g., a WTRU) may receive configuration information. The configuration information may indicate at least OCC information associated with an UL PUSCH. The device may determine to send UCI via higher layer signaling. The determination to send the UCI via the higher layer signaling may be based on one or more conditions being satisfied. The one or more conditions may comprise an OCC length being greater than a threshold. The OCC length may be greater than the threshold. The device may disable hybrid automatic repeat request acknowledgement (HARQ ACK) feedback or follow a HARQ ACK disabling configuration. The device may determine a TBoMS length, for example, as a function of the OCC length. The device may send / transmit a PUSCH transmission over an allocated resource.

[0007] The configuration information may indicate the OCC length, an OCC sequence, and / or whether slot based or symbol based OCC repetitions are configured.

[0008] The one or more conditions may (e.g., further) comprise that the UCI is to be transmitted in a slot configured for PUSCH transmission and / or the UCI is available prior to a PUSCH preparation time.

[0009] The one or more conditions being satisfied may comprise the OCC length being greater than the threshold, that the UCI is to be transmitted in a slot configured for PUSCH transmission, and / or that the UCI is available prior to a PUSCH preparation time.

[0010] The device may not put the UCI in a slot indicated for re-transmission of a transport block.

[0011] The device sending the UCI via higher layer signaling may comprise sending the UCI via a MAC CE.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;

[0013] FIG. 1 B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0014] FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (ON) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment;

[0015] FIG. 1 D is a system diagram illustrating a further example RAN and a further example ON that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0016] FIG. 2 illustrates an example of physical uplink shared channel (PUSCH) mapping with inter-slot 4x orthogonal cover code (OCC).

[0017] FIG. 3 illustrates an example of PUSCH mapping with inter-transport block processing over multislot (TBoMS) 2x OCC.DETAILED DESCRIPTION

[0018] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0019] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a ON 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or networkelements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “ST A”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0020] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0021] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0022] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0023] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

[0024] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0025] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).

[0026] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., an eNB and a gNB).

[0027] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0028] The base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in alocalized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1 A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

[0029] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing a NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0030] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0031] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0032] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0033] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0034] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0035] Although the transmit / receive element 122 is depicted in FIG. 1 B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0036] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.

[0037] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0038] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0039] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable locationdetermination method while remaining consistent with an embodiment.

[0040] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequencymodulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0041] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).

[0042] FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0043] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

[0044] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0045] The CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0046] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0047] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0048] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0049] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

[0050] Although the WTRU is described in FIGS. 1 A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0051] In representative embodiments, the other network 112 may be a WLAN.

[0052] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to thedestination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to- peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11 z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

[0053] When using the 802.11 ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0054] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0055] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0056] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac. 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0057] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0058] In the United States, the available frequency bands, which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.

[0059] FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0060] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a maytransmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0061] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the orthogonal frequency division multiplexing (OFDM) symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0062] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, 102c.

[0063] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0064] The CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network(DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0065] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0066] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernetbased, and the like.

[0067] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0068] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, theWTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0069] In view of Figures 1A-1 D, and the corresponding description of Figures 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0070] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and / or may performing testing using over-the-air wireless communications.

[0071] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0072] Systems, methods, and instrumentalities are described herein related to uplink control information (UCI) transmission with orthogonal cover code (OCC) based physical uplink shared channel (PUSCH) in NR non-terrestrial networks (NTNs). A WTRU may receive a configuration of orthogonal cover coded periodic configured grant (CG) UL PUSCH transmissions, which may indicate one or more of the following: an OCC length and / or OCC sequence assigned to the WTRU; selection of slot based or symbol based OCC repetitions; PUSCH transmission parameters; transport block processing over multi-slot (TBoMS) related parameters (e.g., a length or a set of length parameters); and / or priority rule(s) for PUSCHversus physical uplink control channel (PUCCH) transmissions. TBoMS may be referred to as transport block processing over multiple slots or transport block processing over multi-slot.

[0073] The WTRU may transmit UCI via a higher layer signaling (e.g., via a MAC control element (CE)), for example, if one or more of the following conditions are satisfied: an OCC length is longer than a threshold (e.g., an OCC length is greater than 1); UCI needs to be transmitted in any of the slots carrying a PUSCH transmission (e.g., a UCI may be transmitted in a slot carrying a PUSCH transmission); and / or UCI is available prior to a PUSCH preparation time (e.g., n-PUSCH preparation time).

[0074] The WTRU may disable hybrid automatic repeat request acknowledgement (HARQ ACK) feedback (e.g., if the WTRU determines that one or more of the conditions described herein are satisfied). If the WTRU does not disable HARQ ACK, the WTRU may follow a HARQ ACK enable / disable configuration for the HARQ process (e.g., as per the configuration received from the network).

[0075] The WTRU may determine a TBoMS length as a function of the OCC length (e.g., same length for both), for example, based on the WTRU being configured for TBoMS based PUSCH transmission (e.g., if the WTRU determines that one or more of the conditions described herein are satisfied).

[0076] A NTN may include an aerial and / or space-borne platform configured (e.g., via a gateway (GW)) to transport signals from a land-based based gNB to a WTRU and / or vice-versa. Aerial or space-borne platforms may be classified in terms of orbit. A non-geosynchronous orbit (NGSO) satellite may have a low- earth orbit (LEO) with an altitude range of 300 - 1500 km. A medium-earth orbit (MEO) satellite may have an altitude range of 7000 - 25000 km. NGSO satellites may move continuously overhead relative to earth. Geosynchronous orbit (GSO) satellites may remain fixed overhead, for example, by maintaining an altitude at 35,786 km.

[0077] Satellite platforms may be (e.g., further) classified as having a “transparent” or “regenerative” payload. Transparent satellite payloads may implement frequency conversion and / or RF amplification in uplink and / or downlink. Transparent satellite payloads may be associated with multiple transparent satellites that may be connected to a (e.g., one) land-based gNB. Regenerative satellite payloads may implement a full gNB or a gNB distributed unit (DU) onboard the satellite. Regenerative payloads may perform digital processing on the signal, which may include one or more of the following: demodulation, decoding, re-encoding, re-modulation, and / or filtering.

[0078] An NTN satellite may support multiple cells. A (e.g., each) cell may include one or more satellite beams. Satellite beams may cover a footprint on Earth (e.g., like a terrestrial cell). Satellite beams may range in diameter, such as from 100 - 1000 km in NGSO deployments, 200 - 3500 km diameter in GSO deployments, etc. Beam footprints in GSO deployments may remain fixed relative to Earth. The area covered by a beam / cell in NGSO deployments may change over time, e.g., due to satellite movement.Beam movement may be classified as earth moving, where a beam (e.g., NGSO beam) moves continuously across the earth, or earth fixed, where a beam may be steered to remain covering a fixed location, for example, until another (e.g., new) cell overtakes the coverage area, e.g., in a discrete and / or coordinated change.

[0079] An NTN may pose challenges, including one or more of the following: 1 ) continuous movement of NGSO satellites overhead may result in frequent and / or continuous cell change; 2) cell sizes may be up to 3500km in diameter; and / or 3) a round trip times (RTT) may be several orders of magnitude larger than terrestrial networks (e.g., up to 541.46 ms).

[0080] NTN UL capacity may be enhanced, for example, through multiplexing techniques.

[0081] The coverage of NTN satellites may be very wide. A large number of WTRUs may be within a satellite’s coverage given device density. A large number of WTRUs in coverage (e.g., for LEO) may transmit data during a satellite coverage, indicating that access to and release of satellite resources may be (e.g., need to be) rapid.

[0082] The total spectrum resources available to the network may be limited, e.g., especially in the early phases of NR NTN deployments. Some users may utilize more resources than others, e.g., depending on their traffic patterns. Granularity of resource multiplexing may (e.g., significantly) improve system capacity efficiency.

[0083] High per-WTRU resources may be allocated to better support voice over new radio (VoNR)Zvoice over internet protocol (VoIP) services in coverage-limited scenarios.

[0084] NG-RAN based NTNs may be enhanced with respect to one or more of the following: a GSO and NGSO, e.g., including LEO and MEO; an Earth fixed tracking area (e.g., Earth fixed and Earth moving cells for NGSO); a frequency domain duplexing (FDD) mode; the WTRUs with Global Navigation Satellite Systems (OFDM) capabilities; in frequency band(s) above 10 GHz (e.g., both Terminal Type 1 (e.g., electronic steering antenna) and Type 2 (e.g., mechanical steering antenna) for GSO and NGSO); (e.g., implicit) compatibility to support High Altitude Platform Station (HAPS) and / or Air To Ground (ATG) scenarios (e.g., where relevant).

[0085] A very small aperture terminal (VSAT) device with external antenna on a moving platform may be equivalent to a device that operates on platforms in motion, which may be referred to as Earth Station In Motion (ESIM).

[0086] Uplink capacity / throughput enhancement for FR1-NTN (e.g., RAN1 , RAN2, RAN4) may include DFT-s-OFDM PUSCH enhancements via OCC, e.g., considering OCCs across OFDM symbols, across slots, and / or within an OFDM symbol.

[0087] NR NTN may support dynamic and / or configured grant based PUSCH transmissions. Satellite cells may have very large coverage areas spanning hundreds of kilometers. The number of WTRUs in a satellite coverage area may be very large. Limited spectrum may be currently allocated and in use. Accordingly, the UL capacity may be severely limited to support WTRUs present in a given coverage area. There may be a long distance between WTRUs and satellites. WTRUs may have limited power available. WTRUs may (e.g., need to) transmit multiple repetitions of the same transport block (TB) for decodability. The repetitions may (e.g., further) reduce the system capacity and spectral efficiency.

[0088] OCC based PUSCH and UCI multiplexing may be utilized. Due to multiple repetitions transmitted for PUSCH, the use of OCCs may enable user multiplexing over the same time frequency resource, which may increase the system capacity. In an OCC based PUSCH and UCI multiplexing scheme, multiple WTRUs may transmit their PUSCH transmissions with the application of OCC. A gNB can de-multiplex PUSCH transmissions from different WTRUs based upon the applied OCC from respective WTRUs.

[0089] With a scheduled / configured PUSCH transmission, the WTRU may multiplex UCI over PUSCH, for example, if the WTRU needs to transmit UCI over PUCCH in the same slot. With the application of OCC, the PUSCH modulated symbols may be the same over the application period of the whole OCC sequence. There may be PUSCH degradation due to UCI multiplexing. A large UCI multiplexed over multiple PUSCH slots may degrade PUSCH quality, e.g., due to reduced resource elements (REs) available for data transmission. There may be a UCI timing issue, for example, if UCI becomes available in the middle of the OCC repetition duration. UCI multiplexing may be performed, for example, if / when a WTRU is transmitting OCC based PUSCH transmissions.

[0090] As described herein, a WTRU may be configured to perform an OCC based PUSCH transmission, (e.g., and) for example, if an OCC length is determined to be longer than a threshold (e.g., if an OCC length is greater than 1), the WTRU may be configured to perform one or more actions as described herein (e.g., if the WTRU determines that one or more conditions as described herein are satisfied, for example, if an OCC length is longer than a threshold, if UCI is determined to be transmitted in a slot carrying a PUSCH transmission, and / or if UCI is available prior to a PUSCH preparation time). If an OCC length is equal to 1 for a PUSCH transmission, then the WTRU may consider the PUSCH transmission as no OCC PUSCH transmission (e.g., or an OCC-less PUSCH transmission), e.g., the WTRU may not perform one or more of the actions as described herein and / or the WTRU may perform an alternative action as described herein. In examples, an OCC length may be an OCC sequence length or the number of OCC coefficients, and / or, an OCC sequence may be applied at a symbol, slot, or multi-slot level. A WTRU may transmit a UCI via higher layer signaling (e.g., via a MAC CE), for example, if / when a UCI needs to be multiplexed (e.g., if a WTRU determines that one or more conditions as described hereinare satisfied). Otherwise, the WTRU may transmit the UCI as a part of the PUSCH transmission in the allocated UL resource. UCI as part of a PUSCH transmission may be achieved by multiplexing UCI over one or more (e.g., certain) parts of PUSCH resource elements, e.g., according to rules known to the WTRU and the network. HARQ ACK feedback may be disabled (e.g., if a WTRU determines that one or more conditions as described herein are satisfied), or (e.g., Otherwise the WTRU may follow a HARQ ACK disabling configuration for the HARQ processes. A TBoMS length may be determined, for example, as a function of the OCC length (e.g., same length for both, if a WTRU determines that one or more conditions as described herein are satisfied).

[0091] A device (e.g., a WTRU) may (e.g., be configured to) perform one or more of the following actions.

[0092] The WTRU may receive configuration information, which for example may indicate(s) a configuration of orthogonal cover coded periodic CG UL PUSCH transmissions. The configuration information may indicate one or more of the following: an OCC length and / or an OCC sequence assigned to the WTRU; a selection of slot based or symbol based OCC repetitions; PUSCH transmission parameter(s); TBoMS related parameter(s) (e.g., a TBoMS parameter such as a length, a set of length parameters, and / or the like); and / or priority rules for PUSCH versus PUCCH transmissions.

[0093] The WTRU may determine slots n, n+1 , .... m, (e.g., where m is greater than or equal to n) for UL CG transmission. The slots may have one or more OCC spread PUSCH repetitions.

[0094] The WTRU may transmit UCI via a higher layer signaling (e.g., via a MAC CE), for example, if at least one or more of the following conditions are satisfied: an OCC length is longer than a threshold (e.g., an OCC length is greater than 1); UCI is to be transmitted in any of the slots carrying a PUSCH transmission; and / or UCI is available prior to PUSCH preparation time (e.g., n-PUSCH preparation time). The WTRU may drop a UCI transmission in slots n to m, for example, if (e.g., any) one or more of the following conditions are satisfied: if UCI becomes available after a PUSCH preparation time (e.g., due to a UCI timeline) from the first slot of the OCC based PUSCH transmission; and / or if a CG transmission is a retransmission for a TB (e.g., a WTRU may not modify the re-transmission TB from the original transmission). The WTRU may transmit HARQ in an UL transmission (e.g., in an upcoming UL Tx opportunity) with (e.g., additional) information, e.g., the WTRU may transmit a HARQ status for (e.g., all) the active DL HARQ processes.

[0095] The WTRU may disable HARQ ACK feedback, or, e.g., otherwise, the WTRU may follow HARQ ACK disabling configuration for the HARQ processes (e.g., if the WTRU determines that one or more of the condition(s) described herein are satisfied).

[0096] The WTRU may determine a TBoMS length as a function of the OCC length (e.g., the same length for both), for example, if / when configured for TBoMS based PUSCH transmission (e.g., if the WTRU determines that a one or more of the condition(s) described herein are satisfied).

[0097] The WTRU may perform TB multiplexing and / or mapping over the scheduled and / or configured resource.

[0098] The WTRU may spread the modulated PUSCH symbols, for example, according to the configured slot / symbol wise OCC sequence.

[0099] The WTRU may transmit the OCC spread PUSCH symbols / slots over the UL resource.

[0100] Examples described herein may refer to a (e.g., specific) NTN deployment type (e.g., NGSO, GSO, etc.). Examples described herein may be applied (e.g., equally) to non-terrestrial deployments.

[0101] Examples described herein may refer to a non-terrestrial transmission scenario. Examples may be applied (e.g., equally) to a cell or cells originating from a network type (e.g., any network type (e.g., terrestrial cells).

[0102] Examples described herein may refer to a cell moving relative to Earth and / or may use the context of a cell originating from an NGSO satellite. Examples involving an Earth moving cell may be applied (e.g., equally) to other moving cells, such as from a mobile IBA node.

[0103] In examples described herein, the term “configured” is used. However, information may (e.g., additionally and / or alternatively) be indicated or (e.g., explicitly) specified (e.g., indicated and / or specified may be used interchangeably with configured).

[0104] The examples described herein may be (e.g., fully) applicable to transform pre-coded OFDM transmission (e.g., DFT-S-OFDM) and / or CP-OFDM based transmissions.

[0105] In examples, an operation such as TBoMS length determination and / or a TB size determination may be exposed for uplink transmissions. The operation(s) may be applied (e.g., equally) to downlink transmissions, sidelink transmissions, and / or (e.g., any) other types of transmissions.

[0106] A WTRU configuration may be applied for OCC based PUSCH transmissions. A WTRU may receive an uplink PUSCH configuration for transmission of uplink data. The uplink configuration may be related to one or more (e.g., any) of the following scheduling types: dynamic scheduling that the WTRU may receive through a dynamic indication (e.g., in DCI); periodic resources that may be configured through higher layer signaling (e.g., RRC signaling), such as CG Type 1 transmissions; periodic resources configured through higher layer signaling (e.g., RRC signaling) with dynamic (e.g., DCI based) activation, e.g., CG Type 2 transmissions.

[0107] A WTRU may receive, for example, one or more of the following configurations and configuration parameters in relation to an uplink transmission (e.g., within the uplink configuration and / or through separate configurations): OCC configuration parameter(s); PUSCH transmission parameter(s); UCI related parameter(s); a number of slots allocated for TBoMS (e.g., numberOfSIotsTBoMS); a number of repetitions of a TB (e.g., numberOfRepetitions); demodulation reference signal (DMRS) bundling; and / or priority rules for PUSCH versus PUCCH transmissions.

[0108] OCC configuration parameters may include, for example, one or more of the following: an OCC enable flag; an OCC length; an OCC sequence assigned to the WTRU; and / or an OCC type. An OCC type may include one or more of the following: an inter-repetition or inter-TBoMS OCC (e.g., the WTRU may be configured to apply OCC coefficients to TBoMS based repetitions, for example, if / when a WTRU is configured with TB processing over more than one slot); an inter-slot OCC (e.g., a PUSCH slot may be transmitted with an (e.g., given) OCC coefficient); an inter-symbol OCC; and / or an intra-symbol OCC (e.g., when OCC is applied pre-transform-precoding or post-transform-precoding according to the configuration).

[0109] PUSCH transmission parameters, may include, for example, one or more of the following: parameters related to a DMRS configuration; parameters related to time domain allocations; parameters related to frequency domain allocations; parameters related to a modulation and coding scheme (MCS) table selection and MCS; parameters related to PUSCH power control; a priority indication for PUSCH; a redundancy version (RV) sequence configuration; and / or a transform precoding enable / disable.

[0110] UCI related parameters may include, for example, one or more of the following: UCI on PUSCH (e.g., betaOffsets, via dynamic and / or semi-static configuration); UCI over higher layers (e.g., enable and / or betaOffsets, via dynamic and / or semi-static configuration); CG-UCI-Multiplexing (e.g., WTRU may perform joint encoding of HARQ ACK and CG-UCI, for example, if CG-UCI-Multiplexing is enabled); and / or a priority for one or more types (e.g., different) types of UCI (e.g., HARQ ACK, CG-UCI, CSI, etc.).

[0111] The number of slots allocated for a TBoMS may be indicated, for example, by a parameter, such as numberOfSIotsTBoMS. The WTRU may be configured with more than one numberOfSIotsTBoMS values for the parameter. A WTRU (e.g., if / when configured with more than one numberOfSIotsTBoMS) may determine a (e.g., one) suitable value, for example, based on an OCC configuration.

[0112] The number of repetitions of a TB may be indicated, for example, by a parameter, such as numberOfRepetitions. The number of repetitions of a (e.g., single) TBoMS may be indicated, for example, if / when numberOfSIotsTBoMS is set to 2, 4, or 8 (e.g., TBoMS PUSCH is enabled).

[0113] A WTRU may perform OCC based PUSCH transmissions. A WTRU may perform dynamic adaptations of OCC. A WTRU may be configured to adapt OCC parameters in a dynamic manner. The WTRU may dynamically update, for example, one or more of the following OCC parameters: an OCClength; an OCC sequence; an OCC enable / disable; and / or an OCC type (e.g., inter-symbol, intra-symbol, inter-slot or inter-TBoMS, etc.).

[0114] A WTRU may (e.g., determine to) adapt the OCC parameter(s) dynamically, for example, based upon one or more of the following: a dynamic indication to update the OCC parameter(s) received from the network; a WTRU determination of a change of TBoMS parameters (e.g., TBoMS length in number of slots); a WTRU determination of a change of a sched uled / config ured resource for transmission (e.g., one or more slots may become unavailable, for example, due to slot format indication, channel access failure on shared spectrum, high priority traffic arrival at the WTRU, etc.); receiving an indication from the network to stop an ongoing transmission; and / or receiving a dynamic scheduling from the network, for example, if / when the OCC based PUSCH is a semi-static resource configuration.

[0115] A WTRU may perform logical channel prioritization and / or MAC PDU generation with UCI. A WTRU may make a determination to (i) transmit an OCC based PUSCH transmission and / or (ii) transmit UCI via higher layer signaling. As described herein, the MAC layer at the WTRU may (e.g., based on the WTRU determination) perform multiplexing and assembly of UL-SCH data and UCI MAC CE (e.g., full UCI MAC CE or truncated UCI MAC CE, as determined by the WTRU) according to principles of logical channel prioritization and multiplexing rules for MAC CEs.

[0116] A WTRU may perform multiplexing and channel coding. A WTRU may perform multiplexing and channel coding (e.g., similar to operations for legacy uplink shared channel transmission without OCC spreading), for example, for the multiplexing and channel coding of an uplink shared channel related to PUSCH transmission with OCC spreading. Multiplexing and channel coding operations may include, for example, a CRC attachment, channel coding, and / or rate matching. A WTRU may perform (e.g., optional) operations, such as code block segmentation and / or code block concatenation, for example, based on a code block size being larger than a configured threshold.

[0117] A WTRU may perform data multiplexing in DMRS symbols. A WTRU may (e.g., upon determining to transmit an OCC based PUSCH transmission) determine to not multiplex data in DMRS symbols, e.g., if / when there may be available REs in DMRS symbols. The WTRU may determine to not multiplex data in DMRS symbols, for example, for a transmission (i) with transform precoding enabled (e.g., DFT-S-OFDM based waveform) and / or (ii) without transform precoding enabled (e.g., CP-OFDM based waveform). The WTRU may determine not to multiplex data in DMRS symbols based upon an indication from the network. The WTRU may determine not to multiplex data in DMRS symbols if the WTRU determines to transmit OCC based PUSCH.

[0118] A WTRU may perform TB processing, mapping, and / or OCC spreading. A WTRU may (e.g., for PUSCH transmission with OCC spreading) determine resource allocation in the time domain based on, forexample, a semi-static configuration and / or dynamic signaling. The WTRU may (e.g., determine to) perform the mapping of modulated PUSCH symbols over the determined resource based on, for example, the PUSCH configuration, a TBoMS configuration, an OCC configuration, and / or a determined OCC type. The WTRU may determine a RV for transmission, for example, according to the received configuration and / or rules for RV determination and / or selection.

[0119] A WTRU may repeat a determined RV of the TB in OCCJength slots, for example, if the WTRU determines the OCC type to be inter-slot OCC. The slots may be consecutive (e.g., for paired spectrum) or non-consecutive (e.g., for unpaired spectrum). The WTRU may spread the modulated TB symbols with the determined OCC sequence. The WTRU may map the first slot REs with the product of the first OCC coefficient and modulated TB symbols, map the second slot REs with the product of second OCC coefficient and modulated TB symbols, and so on, until obtaining the OCCJength slots. An example of PUSCH mapping is shown in FIG. 2 for four times (4x) OCC with eight (8) repetitions, where a WTRU OCC sequence is denoted as [d , c2, c3, c4]. The WTRU may map additional repetitions, for example(e.g., , if configured).

[0120] FIG. 2 illustrates an example of PUSCH mapping with an inter-slot 4x OCC.

[0121] A WTRU may (e.g., if the WTRU determines an OCC type to be an inter-TBoMS OCC) transmit a determined RV over a TBoMS length and / or may repeat an RV transmission OCCJength times. The slots may be consecutive (e.g., for paired spectrum) or non-consecutive (e.g., for unpaired spectrum). An example of inter-TBoMS PUSCH mapping is shown in FIG. 3 for two times (2x) OCC with four (4) repetitions, where a WTRU OCC sequence is denoted as [d , c2]. The WTRU may map additional repetitions, for example (e.g., if configured).

[0122] FIG. 3 illustrates an example of PUSCH mapping with an inter-TBoMS 2x OCC.

[0123] A WTRU may (e.g., if the WTRU determines an OCC type to be inter-symbol OCC) repeat a (e.g., each) PUSCH symbol in the determined RV of the TB in OCCJength symbols. The WTRU may prepare the modulated data for an (e.g., one) OFDM symbol (e.g., CP-OFDM with or without transform precoding according to the configuration). The WTRU may spread the symbol with the determined OCC sequence. The WTRU may map the first OFDM symbol REs with the product of the first OCC coefficient and modulated TB symbols, map the second OFDM symbol REs with the product of second OCC coefficient and modulated TB symbols, and so on, until obtaining the OCCJength symbols. The WTRU may continue the symbol multiplexing until reaching the end of one (1) TBoMS duration, for example, if / when the WTRU is configured with TBoMS with the WTRU determining TBoMS length larger than one (1) (e.g., a slot).

[0124] A WTRU may (e.g., if the WTRU determines the OCC type to be an intra-symbol OCC) repeat a (e.g., each) modulated symbol in the determined RV of the TB in OCCJength REs. The WTRU may take (e.g., obtain) the TB modulated symbols scaled by OCCJength, for example, to map data in an (e.g., one) OFDM symbol. The WTRU may spread a (e.g., each) modulation symbol with the determined OCC sequence, obtaining OCCJength modulated symbols. The WTRU may map the OCC spread modulated symbols in the corresponding OFDM symbols. The operations described herein may continue until the WTRU has mapped the intra-symbol spread TB modulated symbols over the allocated symbols for a (e.g., one) repetition. The WTRU may (e.g., if / when configured with TBoMS and if / when TBoMS length is determined to be larger than 1 (e.g., a slot)), continue the symbol multiplexing until reaching the end of 1 TBoMS duration.

[0125] A WTRU may perform an OCC based PUSCH transmission, e.g., with WTRU based TA compensation. A WTRU may be configured to apply WTRU based timing advanced (TA) compensation, for example, in NTN network(s). The WTRU may determine to not apply TA compensation for an OCC based PUSCH transmission. A PUSCH transmission (e.g., as described herein) may correspond to an uplink PUSCH transmission scheduled with multiple repetitions, e.g., with or without TBoMS. The WTRU may determine to not apply TA compensation, for example, based on one or more of the following: a TA / TA drift; a TA / TA drift being smaller than a threshold; a WTRU estimate of a local frequency offset; one or more of the characteristics of a WTRU local oscillator (e.g., crystal oscillator); the overall duration (e.g., in slots or in ms) of a PUSCH transmission; the duration (e.g., in slots or in ms) of an (e.g., one) OCC sequence transmission; and / or the type of OCC (e.g., inter-TBoMS, inter-slot, inter-symbol, intra-symbol, etc.).

[0126] TA / TA drift may include, for example, one or more of the following: a (e.g., common) TA value received from the network; the WTRU estimated TA at the beginning of the transmission or at the beginning of an (e.g., one) OCC sequence; the WTRU estimated TA at the beginning of the transmission or at the beginning of (e.g., one) OCC sequence; a TA drift value received from the network (e.g., for the feeder link); and / or a local TA drift value, e.g., computed based upon the satellite ephemeris.

[0127] In examples, the WTRU may determine to not apply TA compensation during the (e.g., whole) PUSCH transmission.

[0128] In examples, the WTRU may determine to not apply TA compensation during the (e.g., whole) PUSCH transmission, for example, if the WTRU estimated TA value at the beginning / end of the transmission is smaller than a threshold, e.g., configured by the network or known to the WTRU, such as through pre-configuration.

[0129] In examples, the WTRU may determine to not apply TA compensation during the duration of a (e.g., one) OCC sequence. The OCC sequence transmission duration may be based on an OCC type.

[0130] In examples, the WTRU may determine to not apply TA compensation during the duration of an (e.g., one) OCC sequence. The OCC sequence transmission duration may be based on the OCC type, for example, if the WTRU estimated TA value at the beginning / end of the relevant OCC sequence transmission is smaller than a threshold, e.g., configured by the network or known to the WTRU, such as through pre-configuration.

[0131] A WTRU may (e.g., determine to) reduce the periodicity of UCI reporting with an OCC based PUSCH transmission. A WTRU may (e.g., if / when configured to transmit OCC based PUSCH transmission) determine to reduce the periodicity of UCI reporting. The reduced UCI reporting periodicity may be applicable to channel state information (CSI) reporting, HARQ ACK reporting, etc.

[0132] In examples, the WTRU may (e.g., if the WTRU determines to reduce the UCI reporting periodicity) determine to reduce the reporting periodicity by a reduction factor N (e.g., 2, 4, or 8). The reduction factor may be configured to the WTRU, for example, with a PUSCH configuration or a UCI / PUCCH configuration.

[0133] The WTRU may determine to update the reporting content, for example, if the WTRU determines to reduce the periodicity of UCI reporting. In examples (e.g., for HARQ ACK), the WTRU may determine a second (e.g., different) HARQ codebook to be used with reduced reporting periodicity. In examples, the WTRU may determine a second (e.g., different) CSI reporting type or configuration, for example, if / when the WTRU determines to report CSI with reduced periodicity.

[0134] A WTRU may (e.g., determine to) perform a UCI transmission via higher layer signaling. A WTRU may transmit UCI, for example, along with a UL PUSCH transmission. The WTRU may determine to transmit UCI via a higher layer signaling (e.g., via a MAC CE), for example, if one or more of the following conditions are satisfied (e.g., if the WTRU determines that one or more of the condition(s) are satisfied): an OCC length is longer than a threshold (e.g., OCC length is greater than 1 ); UCI may (e.g., needs to, or is to) be transmitted in any of the slots n, n+1 , ...., m carrying PUSCH transmission; UCI is available prior to a PUSCH preparation time (e.g., for example, from the beginning of the first slot carrying PUSCH transmission, such as n - PUSCH preparation time) for the n-th slot being the first slot of the PUSCH transmission); and / or a PUSCH transmission is not a re-transmission for a TB.

[0135] In examples, the WTRU may (e.g., determine to) transmit UCI via a higher layer signaling based on a PUSCH transmission being a (e.g., new) transmission or a re-transmission of a previously encoded TB. For example, the WTRU may determine to transmit UCI via higher layer signaling (e.g., only) for (e.g., new) transmissions based on other condition(s) being fulfilled. The WTRU may (e.g., for a re-transmissionof a TB) determine to not transmit UCI via higher layer signaling, for example, even if other condition(s) to transmit UCI via higher layer signaling are fulfilled. An issue with UCI transmission via higher layer signaling may be that the PHY layer may transmit a TB that may be multiplexed between UL data and UCI MAC CE, which may result in a change of information bits for data compared to a first (e.g., an original) transmission where a PHY transmitted UL data without UCI MAC CE.

[0136] In examples, a WTRU may (e.g., upon determining to transmit UCI through higher layer signaling) determine to transmit UCI MAC CE, e.g., a full MAC CE. UCI MAC CE (e.g., UCI sent via a MAC CE) may include (e.g., comprise), for example, one or more of the following (e.g., when available): HARQ ACK feedback; a CG-UCI (e.g., if / when WTRU is transmitting CG-PUSCH and CG-UCI is configured for transmission); and / or CSI. CSI may include, for example, one or more of the following: a first part of CSI carrying a fixed amount of CSI (e.g., CSI Part 1), e.g., according to the CSI configuration; and / or a second part of CSI carrying a detailed CSI. The length of the second part may be indicated in the first part (e.g., CSI Part 2), e.g., according to the CSI configuration.

[0137] In examples (e.g., if / when the WTRU determines to transmit UCI through higher layer signaling, such as via a MAC CE), the WTRU may determine to transmit UCI MAC CE or a truncated UCI MAC CE based on, for example, one or more of the following: the size of the UCI bits to be transmitted; the time frequency resource allocated to the WTRU; the MCS (e.g., spectral efficiency) indicated for PUSCH transmission; the priority of PUSCH transmission (e.g., the priority indicated to the PHY layer or the priority of UL-SCH); and / or the priority of UCI (e.g., the priority of PDSCH or DL-SCH when known to the WTRU and for which WTRU is transmitting HARQ ACK, the priority of CSI report, the priority of PUSCH transmission for which CG-UCI is being reported, etc.).

[0138] In examples (e.g., if / when the WTRU has determined to transmit UCI through higher layer signaling, such as via a MAC CE), the WTRU may transmit UCI MAC CE, for example, if one or more of the following conditions are true: the size of the UCI bits to be transmitted is less than a threshold; the time frequency resource allocated to the WTRU is larger than a threshold; the ratio of the size of UCI bits to the total PUSCH Res is smaller than a threshold; the MCS indicated for PUSCH transmission is smaller than a threshold; and / or the MCS indicated for PUSCH transmission is larger than a threshold.

[0139] A WTRU may determine to transmit a truncated MAC CE, for example, if the WTRU (e.g., having determined to transmit UCI through higher layer signaling), determines that the condition(s) to transmit (e.g., full) UCI MAC CE are not fulfilled.

[0140] In examples, the WTRU may determine to transmit UCI through a truncated MAC CE based on, for example, one or more of the following being satisfied: the size of the UCI bits to be transmitted is larger than a threshold; the time frequency resource allocated to the WTRU is smaller than a threshold; the ratioof the size of UCI bits to the (e.g., total) PUSCH Res is larger than a threshold; and / or the MCS indicated for PUSCH transmission is I arger / smaller than a threshold.

[0141] A WTRU may determine to transmit (e.g., full) UCI MAC CE, for example, if the WTRU (e.g., having determined to transmit UCI through higher layer signaling) determines that the condition(s) to transmit truncated UCI MAC CE are not fulfilled.

[0142] A WTRU may determine to transmit a limited part of UCI, e.g., through a truncated UCI MAC CE, for example, based on a determination to transmit UCI through higher layer signaling and / or based on (e.g., upon additional) condition(s) (e.g., as described herein). A truncated UCI MAC CE may include (e.g., comprise), for example, one or more of the following (e.g., when available): HARQ ACK feedback; CG-UCI (e.g., when WTRU is transmitting CG-PUSCH and CG-UCI is configured for transmission); and / or CSI. CSI may include (e.g., indicate), for example, one or more of the following: a first part of CSI carrying a fixed amount of CSI (e.g., CSI Part 1), e.g., according to the CSI configuration; and / or a second part of CSI carrying a detailed CSI. The length of a second part may be indicated in the first part (e.g., CSI Part 2), e.g., according to the CSI configuration.

[0143] In examples, a truncated UCI MAC CE may include (e.g., comprise) (e.g., only) HARQ ACK and / or CG-UCI, e.g., if / when available and configured. A WTRU may (e.g., only) transmit (e.g., only) HARQ ACK in truncated UCI MAC CE for dynamic grant based transmissions and / or for configured based transmission, for example, if / when CG-UCI is not configured. A WTRU may not transmit CSI, for example, if / when the WTRU determines to transmit a truncated UCI MAC CE.

[0144] In examples, the truncated UCI MAC CE may be limited to transmit HARQ ACK, CG-UCI, and CSI Part 1 , e.g., if / when available and configured. A WTRU may not transmit CSI Part 2, for example, if / when the WTRU determines to transmit truncated UCI MAC CE.

[0145] In examples, the truncated UCI MAC CE may be limited to carry (e.g., only) CG-UCI, for example, if / when configured. The WTRU may not transmit HARQ ACK and CSI, for example, if / when the WTRU determines to transmit a truncated UCI MAC CE. In examples, the WTRU may transmit HARQ ACK and CG-UCI if the number of HARQ ACK bits is below a configured threshold. The threshold may be, for example, an absolute number (e.g., a value indicating a number of bits), a function of a WTRU determined TB size, or a function of available REs for PUSCH transmission.

[0146] A WTRU may indicate if / when UCI is not transmitted via higher layer signaling. A WTRU may determine to not transmit UCI with PUSCH in slot(s) carrying an OCC spread PUSCH transmission, e.g., the WTRU may determine to not multiplex UCI over OCC based PUSCH transmission. The WTRU may determine to not transmit UCI, e.g., via UCI multiplexed over PUSCH or via higher layer signaling, for example, if one or more of the following conditions is fulfilled: following the UCI timeline, if the UCIbecomes available after PUSCH preparation time prior to the start of the PUSCH transmission; and / or if the PUSCH transmission is a re-transmission for a TB (e.g., because the WTRU may not be able to modify the re-transmission TB from the original TB transmission).

[0147] A WTRU may determine to not transmit UCI in the slots that the WTRU determines for its UL OCC based PUSCH transmissions. The WTRU may determine to not transmit UCI based on the UCI availability and / or the PUSCH preparation timeline. The WTRU may be configured / indicated to transmit multiple repetitions of OCC based PUSCH transmissions. If / when the WTRU determines that UCI is to be (e.g., needs to be) transmitted in a slot that is part of an OCC block, the WTRU may evaluate the UCI timeline condition for the PUSCH preparation time based upon the first symbol of the first slot of the (e.g., relevant) OCC block. For example, if the WTRU is configured with two repetitions of 4x OCC in consecutive slots, the WTRU determines the PUSCH slots to be n to n+3 for the first OCC block, the WTRU determines the PUSCH slots to be n+4 to n+7 for the second OCC block, and if the WTRU determines UCI transmission in one of the slots for the second OCC block (e.g., if UCI needs to be transmitted in slot n+6), the WTRU may evaluate the UCI availability / timeline condition from the starting slot of the second OCC block (e.g., based upon the slot n+4). In this example, if the UCI, scheduled for slot n=6, is available at the WTRU PUSCH preparation time prior to the first symbol of the slot n+4, the WTRU may determine to transmit UCI. If the UCI, scheduled for slot n+6, becomes available after the time instant of the first symbol of the slot n+4 minus the PUSCH preparation time, the WTRU may determine to not transmit or to drop UCI. In examples, if / when the WTRU determines to not transmit UCI, the WTRU may determine to transmit UCI in the next UCI / PUCCH transmission occasion.

[0148] A WTRU may transmit an indication to the network, for example, if / when UCI is scheduled / configured to be transmitted in a slot (e.g., one of the slots) carrying a PUSCH transmission and the WTRU determines to not transmit UCI via higher layer signaling. The indication may inform the network of a missing UCI. In examples, the WTRU may determine to transmit UCI in an upcoming UL Tx opportunity with (e.g., additional) information. In examples, a WTRU may determine to transmit a CSI report with (e.g., additional) information, e.g., so that the additional information can be tied to the first (e.g., original) reporting configuration. The WTRU may transmit HARQ ACK feedback, for example, with an indication of the timing / slot where the WTRU was scheduled and the WTRU did not transmit via higher layer signaling. In examples, the WTRU may transmit a HARQ status for (e.g., all) active DL HARQ processes.

[0149] UCI may be scheduled / configured to be transmitted in a slot (e.g., one of the slots) carrying a PUSCH transmission. The WTRU may determine to not transmit UCI via higher layer signaling. The WTRU may determine to multiplex UCI over a PUSCH, e.g., according to the examples described herein.

[0150] A WTRU may determine a TBoMS length and a number of repetitions for PUSCH transmissions.

[0151] A WTRU may determine a TBoMS length. A WTRU may transmit an OCC spread uplink PUSCH transmission for TBoMS. The WTRU may determine a TBoMS length, for example, according to a TBoMS length configured as part of the PUSCH configuration or TBoMS length received in a dynamic indication, e.g., in DCI.

[0152] A WTRU may determine the number of slots for TB processing based on OCC parameters (e.g., OCC length), for example, if / when the WTRU is configured to choose (e.g., select) a suitable TBoMS lengths for its transmission and / or if / when the WTRU is configured with more than one TBoMS length values in its PUSCH configuration. The WTRU may select a suitable value, for example, based upon the determined OCC length for a PUSCH transmission. In examples, the WTRU may determine the TBoMS length in a slot equal to the spreading factor or OCC sequence length. The WTRU may determine that a numberOfSIotsTBoMS is to be equal to 4 slots, for example, if the WTRU is configured with a 4x spreading factor.

[0153] In examples, the WTRU may determine the number of slots for TB processing based on an OCC length and / or the duration of the scheduled / configured resource for a PUSCH transmission.

[0154] A WTRU may determine the number of PUSCH repetitions. A WTRU may be configured to transmit one or more repetitions of an OCC spread PUSCH transmission. In examples, the WTRU may be configured for TBoMS. The WTRU may determine to transmit one or more repetitions of a single TBoMS, for example, if the WTRU is configured or determines the number of lots for TBoMS transmission larger than 1 .

[0155] A WTRU may be configured with a parameter indicating the total length of the scheduling resource in a number of slots, e.g., N slots. The WTRU may be provided the parameter, for example, through configuration or a dynamic indication. The WTRU may receive the parameter explicitly or implicitly. In examples, the WTRU may determine the (e.g., total) length of a scheduling resource based on one or more (e.g., other) configured and / or indicated parameters.

[0156] The WTRU may determine the number of PUSCH repetitions based on, for example, one or more of the following: a total length of scheduling resource; TBoMS parameters (e.g., numberOfSIotsTBoMS); a WTRU determined length for TBoMS (e.g., determined based on configuration parameters and / or other configurations, such as described herein); and / or OCC parameters (e.g., OCC length).

[0157] In examples, the WTRU may determine the number of PUSCH repetitions by dividing the (e.g., total) length of a scheduling resource by the TBoMS length.

[0158] A WTRU may determine a TBoMS based PUSCH transmission without a network configuration. A WTRU may determine to transmit TBoMS, for example, (e.g., even) if the WTRU is not (e.g., explicitly) configured by the network for TBoMS transmission. The WTRU may determine to transmit TBoMS without explicit network configuration for TBoMS based on, for example, one or more of the following: the number of slots scheduled for a PUSCH; or the OCC configuration (e.g., OCC type, OCC length, and / or the like).

[0159] The WTRU may determine to transmit an OCC based PUSCH over a self-determined TBoMS, for example, if one or more of the following conditions is satisfied: the number of slots scheduled for PUSCH is larger than a threshold; an OCC type is an (e.g., one of the) inter-symbol OCC or an intra-symbol OCC; and / or an OCC length is smaller than a threshold (e.g., smaller than 4).

[0160] The WTRU may determine an OCC type to be an inter-symbol or an intra-symbol OCC with an OCC length of NJDCC. The WTRU may (e.g., also) determine that the time domain resource allocation duration in a number of slots N_PUSCH for PUSCH (e.g., along with the repetitions) exceeds a threshold, where N_PUSCH may be an integer multiple of NJDCC. The WTRU may determine to transmit a TBoMS PUSCH with the number of slots for TBoMS (N_TBoMBS), which may be determined, for example, in accordance with Eq. (1):N.TBoMS = N.PUSCH / NJDCC (1 )

[0161] The WTRU may determine to transmit a TBoMS based PUSCH. The WTRU may report an indication to the network for its determination (e.g., based on the WTRU’s determination).

[0162] A WTRU may (e.g., if the WTRU determines to transmit TBoMS (e.g., as described herein)), use the TB size determination based upon TBoMS length and OCC length (e.g., as per the examples described herein).

[0163] A WTRU may make a TB size determination for PUSCH transmissions. The WTRU may determine a TB size with OCC spreading. A WTRU may determine a TB size for a UL transmission. The WTRU may determine the TB size for a UL transmission based on, for example, one or more of the following: a time domain resource allocation; a frequency domain resource allocation; an OCC configuration parameter(s) (e.g., OCC length, and / or the like.); a WTRU determined OCC length (e.g., if / when more than one OCC length is configured); a TBoMS parameters (e.g., numberOfSIotsTBoMS); and / or a WTRU determined length for TBoMS. For example, the WTRU may determine a TBoMS length based on configuration parameters and / or a (e.g., other) configuration(s), e.g., as described herein.

[0164] In examples, the WTRU may determine the TB size based on an uplink resource allocation (e.g., time and frequency domain) and / or OCC configuration parameter(s). The WTRU may determine the TB size, for example, based on a determination of the REs allocated for uplink transmission in a slot, based on number of allocated PRBs in a slot, a number of sub-carriers in a PRB, a number of allocated symbols in a slot, a number of DMRS symbols, and / or the resource overhead as per the configuration. The number of REs may be determined, for example, in accordance with Eq. (2):N_RE = n_PRB * [N_sc * N_symbol - NJDMRS - N_ov] (2)

[0165] With reference to Eq. (2), N_RE may denote the (e.g., total) number of REs allocated for a PUSCH transmission computed based on n_PRB, denoting the number of PRBs allocated, N_sc, may denote the number of sub-carriers in a (e.g., one) PRB, N_symbol, may denote the number of symbols allocated for PUSCH in a (e.g., one) slot, NJDMRS, may denote the number of REs for DMRS in a (e.g., one) slot, e.g., including the overhead of CDM groups, and / or N_ov, may denote the resource overhead as per the higher layer configuration. N_RE may be used to determine an intermediate variable NJnfo, which may be calculated (e.g., roughly) in accordance with Eq. (3) based on the number of information bits according to the MCS providing modulation Q, the code rate R, and the number of layers v:NJnfo = N_RE * Q * R * v (3)

[0166] The WTRU may determine a TB size, for example, based on the determined NJnfo value. In examples, NJnfo may be used to determine the TB size according to the configuration tables for one or more (e.g., different) lengths of NJnfo.

[0167] In examples, the WTRU may determine to perform TB scaling with an OCC length if / when the WTRU is configured or determines to perform an inter-symbol or intra-symbol OCC spreading based PUSCH transmission. In examples, a WTRU may determine the OCC length NJDCC. The WTRU may scale the number of REs available for PUSCH transmission by NJDCC, for example, in accordance with Eq. (4):N_RE = 1 / NJDCC * n_PRB * [N_sc * N.symbol - NJDMRS - N_ov] (4)

[0168] In examples, the N_RE may be kept un-modified and / or NJnfo may be scaled down with the OCC length.

[0169] In examples (e.g., if / when the WTRU is configured or determines to perform inter-slot OCC based PUSCH spreading), the WTRU may not perform (e.g., any) TB scaling with OCC length.

[0170] In examples (e.g., if / when the WTRU is configured for TB processing over multiple slots), the WTRU may determine the TB size for a UL transmission based on one or more of the following: an uplink resource allocation, an OCC configuration parameter(s), an OCC length, an OCC type (e.g., intra-symbol, inter-symbol or inter-slot OCC), and / or TBoMS parameter(s). The WTRU may be provided with numberOfSIotsTBoMS, for example, through a higher layer configuration or dynamic signaling. The WTRU may determine a length in a number of slots for TBoMS for a PUSCH transmission (e.g., as described herein). As described herein, N_TBoMS may denote the length in the number of slots that the WTRU may use for TBoMS by transmitting a (e.g., single) TB over N_TBoMS slots. In examples, N_TBoMS may be equal to the numberOfSIotsTBoMS (e.g., network configured or indicated parameter) or based on a WTRU determination of the TBoMS length.

[0171] A WTRU may be configured or may determine to perform inter-symbol or intra-symbol OCC based PUSCH spreading. The WTRU may determine a length N_TBoMS for TBoMS. The WTRU may determine the total number of REs available for PUSCH, for example, in accordance with Eq. (5):N_RE = N.TBoMS / N.OCC * n.PRB * [N_sc * N.symbol - N.DMRS - N_ov] (5)

[0172] A WTRU may be configured or may determine to perform inter-slot OCC PUSCH spreading. The WTRU may determine a configuration for TBoMS over N_TBoMS slots. The WTRU may determine not to perform TB scaling for OCC spreading. The WTRU may determine the number of REs for PUSCH transmission, for example, in accordance with Eq. (6):N.RE = N.TBoMS * n.PRB * [N_sc * N_symbol - N.DMRS - N_ov] (6)

[0173] A WTRU may (e.g., determine to) disable HARQ feedback. A WTRU may determine to disable HARQ feedback for one or more of the DL HARQ processes. The WTRU may disable HARQ ACK feedback for one or more of the DL HARQ processes with activated HARQ based on, for example, one or more of the following conditions being fulfilled: if an OCC length is larger than a configured threshold; if an RTT and / or a TA is larger than x, if an OCC is used, and / or if an OCC_Length is larger than a specifiedlength; if the WTRU determines to do TB scaling for the TB size determination with an OCC spread PUSCH transmission; and / or if the WTRU determines the number of HARQ ACK bits to be transmitted is larger than a threshold.

[0174] HARQ may be disabled as a function of OCC_Length, for example, if an OCC length is larger than a configured threshold (e.g., larger than 1), e.g., despite the HARQ process and / or logical channel configured with HARQ being enabled.

[0175] A WTRU may follow a HARQ ACK disabling configuration for one or more of the HARQ processes, for example, if the WTRU determines to not disable HARQ ACK feedback.

[0176] A WTRU (e.g., that determines to disable HARQ ACK feedback) may disable HARQ feedback for one or more (e.g., any) of the following durations: permanently disable; as long as the WTRU has an active UL resource configuration with periodic / semi-static resources with OCC spreading disabling HARQ ACK feedback; as long RTT or TA conditions disabling HARQ feedback are true; and / or for HARQ ACK transmission events (e.g., if / when WTRU determines the number of HARQ ACK bits is larger than HARQ disabling threshold).

[0177] In an example of a WTRU permanently disabling HARQ ACK feedback, the network may (e.g., need to) reconfigure to activate HARQ ACK for the disabled HARQ ACK processes.

[0178] In an example of a WTRU disabling HARQ ACK feedback, as long as the WTRU has (e.g., if the WTRU has) an active UL resource configuration with periodic / semi-static resources with OCC spreading disabling HARQ ACK feedback, the WTRU may revert the HARQ ACK configuration back to the (e.g., original) configuration from the network for the HARQ processes and logical channels, for example, based on (e.g., upon) the UL resource configuration (e.g., that results in WTRU determination of HARQ disabling) being de-activated or becoming invalid.

[0179] A WTRU may perform UCI multiplexing over OCC based PUSCH transmissions. A WTRU may receive a configuration for UCI multiplexing over OCC based PUSCH transmissions. A configuration of UCI multiplexing over OCC based PUSCH transmissions may include, for example, one or more of the following: UCI on PUSCH without an OCC (e.g., betaOffsets, in a dynamic and / or semi-static configuration); UCI on PUSCH with an OCC (e.g., betaOffsets, in a dynamic and / or semi-static configuration, and / or OCC scaling, for example, if there is an additional UCI scaling enabled as a function of an OCC length); UCI over higher layers (e.g., enable and / or betaOffsets, in a dynamic and / or semi-static configuration); CG-UCI-Multiplexing (e.g., a WTRU performs a joint encoding of HARQ ACK and CG-UCI if CG-UCI-Multiplexing is enabled); criterion for UCI multiplexing over PUSCH; priority for different types of UCI (e.g., HARQ ACK, CG-UCI, CSI, and / or the like); priority rules for PUSCH versus PUCCH transmissions.

[0180] A WTRU may be configured with UCI-OnPUSCH (e.g., beta offsets and scaling factor) differently for non-OCC based and OCC-based PUSCH transmissions. The WTRU may (e.g., be indicated to) apply (e.g., additional) UCI scaling, for example, based on an OCC_Length, which may be indicated by OCC scaling, e.g., as part of the configuration.

[0181] A WTRU may determine UCI multiplexing over a PUSCH transmission. A WTRU may (e.g., determine to) multiplex UCI over an OCC based PUSCH transmission. The WTRU may determine to multiplex UCI over an OCC based PUSCH transmission based on, for example, one or more of the following: UCI configuration for PHY multiplexing; UCI configuration for higher layer transmission; UCI transmission time; UCI availability; the number of information / encoded bits or symbols for UCI transmission; the number of information / encoded bits or symbols of CG-UCI bits; the number of information / encoded bits or symbols of HARQ ACK bits; the number of information / encoded bits or symbols for CSI (e.g., or CSI part 1 and / or CSI part 2); and / or OCC parameter(s) (e.g., an OCC type, an OCC length, and / or the like).

[0182] A WTRU may determine to multiplex UCI over an OCC based PUSCH transmission, for example, if one or more of the following conditions are satisfied: UCI needs to be transmitted in a slot (e.g., any of the slots) intended for OCC based PUSCH transmission; UCI is available prior to a PUSCH preparation time (e.g., n-PUSCH preparation time); UCI information bits are smaller than a threshold; UCI encoded bits are smaller than a threshold; HARQ ACK is (e.g., gets) multiplexed over a single symbol; CSI (e.g., part 1 and part 2) is (e.g., get) multiplexed over a single symbol; an OCC type is a (e.g., specific) type (e.g., intersymbol OCC, inter-slot OCC, etc.); an OCC length is smaller than a threshold; a WTRU determination to not transmit UCI via a higher layer configuration; UCI configuration allows UCI multiplexing over an OCC based PUSCH; and / or UCI priority is higher than a threshold (e.g., HARQ ACK corresponding to DL data for a higher priority DL transmission).

[0183] A WTRU may determine multiplexing partial UCI over a PUSCH transmission. A WTRU may determine to multiplex partial UCI (e.g., and not the full UCI) over an OCC based PUSCH transmission, for example, if / when the WTRU determines to multiplex UCI over an OCC based PUSC transmission. The WTRU may determine to multiplex partial UCI over an OCC based PUSCH transmission based on, for example, one or more of the following: the number of information / encoded bits or symbols for UCI transmission; the number of information / encoded bits or symbols for a CG-UCI transmission; the number of information / encoded bits or symbols of HARQ ACK bits; the number of information / encoded bits or symbols for CSI (or CSI part 1 and / or CSI part 2); and / or an OCC parameter(s) (e.g., OCC type, OCC length, and / or the like).

[0184] A WTRU may determine to multiplex a partial UCI over an OCC based PUSCH transmission, for example, if / when one or more of the following conditions are fulfilled: UCI information and / or encoded bits are larger than a threshold; a CG-UCI, HARQ ACK, and / or CSI (e.g., CSI part 1 and / or CSI part 2) information and / or encoded bits are larger than a threshold; a CG-UCI and / or HARQ ACK is not multiplexed over a single symbol; CSI (e.g., part 1 and part 2) is not multiplexed over a single symbol; an OCC type is a (e.g., specific) type (e.g., inter-symbol OCC, inter-slot OCC, etc.); and / or an OCC length is smaller than a threshold.

[0185] In examples, a WTRU may drop CSI and (e.g., only) multiplex HARQ ACK (e.g., if any) with an OCC based PUSCH, for example, if PUSCH carries high priority data (e.g., high priority indication through a PHY priority or a UL-SCH priority) and / or if the number of UCI REs exceeds a configured threshold (e.g., absolute threshold or a fraction or percentage of sched uled / available REs for PUSCH in a symbol / slot / TBoMS).

[0186] In examples, a WTRU may drop HARQ ACK (e.g., if any) and may (e.g., only) transmit PUSCH data without HARQ ACK multiplexing, for example, if PUSCH carries high priority data (e.g., high priority indication through a PHY priority or a UL-SCH priority) and / or if the HARQ ACK corresponds to a low priority PDSCH and / or the number of REs needed (e.g., required) to map HARQ ACK is beyond (e.g., satisfies) a configured threshold (e.g., absolute threshold or a fraction or percentage of sched uled / available REs for PUSCH in a symbol / slot / TBoMS).

[0187] In examples, a WTRU may drop CSI and (e.g., only) multiplex HARQ ACK on an OCC based PUSCH transmission, for example, if the WTRU has CSI and HARQ ACK for multiplexing on an OCC based PUSCH, and / or if HARQ ACK corresponds to high priority DL data (e.g., determined through priority indicator field in DCI scheduling PDSCH or from RRC configuration or from DL-SCH configuration).

[0188] In examples, a WTRU may not transmit PUSCH and may transmit UCI as a PUCCH transmission, for example, if the WTRU has a scheduled / configured UCI transmission with at least HARQ ACK, if the WTRU determined priority of corresponding PDSCH (or DL-SCH) HARQ ACK is larger than a threshold, and / or if the WTRU determined priority of OCC based PUSCH transmission is smaller than another threshold.

[0189] A WTRU may map an inter-symbol OCC based PUSCH.

[0190] In examples (e.g., if a WTRU determines to multiplex HARQ ACK with inter-symbol based OCC spreading), the WTRU may map HARQ ACK on the set of symbols based on an (e.g., one full) OCC sequence, which may correspond to a PUSCH ACK symbol (e.g., the symbol after first DMRS symbol).

[0191] In examples, a WTRU may determine to multiplex CSI (e.g., part 1 and / or part 2) with an intersymbol based OCC spreading. CSI REs may be multiplexed on the first data symbol. The WTRU may repeat the symbol, for example, according to the determined OCC sequence.

[0192] In examples, a WTRU may determine to multiplex CSI (e.g., part 1 and / or part 2) with intersymbol based OCC spreading. The CSI REs may exceed the number of REs in the first allocated symbol. The WTRU may (e.g., in response) map CSI on the first symbol, repeat with the determined OCC sequence over OCC_Length symbols, multiplex the remaining CSI, and repeat (e.g., according to the OCC sequence) until (e.g., all) CSI is multiplexed. The WTRU may start multiplexing PUSCH modulated symbols from an (e.g., the next) available RE(s), for example, after CSI multiplexing is done.

[0193] In examples, a WTRU may determine to multiplex HARQ ACK and CSI (e.g., part 1 and / or part 2) with inter-symbol based OCC spreading. The first allocated symbol and the first symbol following the DMRS symbol may be within an OCC length. The WTRU may determine to transmit a HARQ ACK on the first OCCJength symbols. The WTRU may start to multiplex CSI from a (e.g., the next available) symbols.

[0194] In examples, a WTRU may determine to multiplex HARQ ACK and CSI (e.g., part 1 and / or part 2) with inter-symbol based OCC spreading. The first allocated symbol and the first symbol following the DMRS symbol may be within an OCC length. The WTRU may prepare symbols, for example, by (i) first multiplexing HARQ ACK (e.g., as described herein), and (e.g., then) (ii) multiplex CSI and repeat the symbols with an OCC sequence.

[0195] In examples, a WTRU may determine to multiplex HARQ ACK and CSI (e.g., part 1 and / or part 2) with an inter-symbol based OCC spreading. The first allocated symbol and the first symbol following the DMRS symbol may be within OCC length. The WTRU may determine to transmit HARQ ACK on the first OCCJength symbols and drop CSI multiplexing from the transmission. The WTRU determination to drop the CSI may be based on, for example, the priority of PDSCH corresponding to HARQ ACK and a CSI priority.

[0196] In examples, a WTRU may determine to multiplex HARQ ACK and CSI (e.g., part 1 and / or part 2) with inter-symbol based OCC spreading. The first allocated symbol and the first symbol following the DMRS symbol may be within an OCC length. The WTRU may determine to transmit CSI on the first OCCJength symbols and drop HARQ ACK multiplexing from the transmission. The WTRU determination to drop CSI may be based on, for example, the priority of PDSCH corresponding to HARQ ACK and a CSI priority.

[0197] As described herein, a WTRU may be configured to perform an OCC based PUSCH transmission, (e.g., and) for example, if an OCC length is determined to be longer than a threshold (e.g., if an OCC length is greater than 1), the WTRU may be configured to perform one or more actions asdescribed herein (e.g., if the WTRU determines that one or more conditions as described herein are satisfied, for example, if an OCC length is longer than a threshold, if UCI is determined to be transmitted in a slot carrying a PUSCH transmission, and / or if UCI is available prior to a PUSCH preparation time). If an OCC length is equal to 1 for a PUSCH transmission, then the WTRU may consider the PUSCH transmission as no OCC PUSCH transmission (e.g., or an OCC-less PUSCH transmission), and, the WTRU may not perform one or more of the actions as described herein and / or the WTRU may perform an alternative action as described herein. In examples, an OCC length may be an OCC sequence length or the number of OCC coefficients, and / or, an OCC sequence may be applied at a symbol, slot, or multi-slot level. A WTRU may transmit a UCI via higher layer signaling (e.g., via a MAC CE), for example, if / when a UCI needs to be multiplexed (e.g., if a WTRU determines that one or more conditions as described herein are satisfied). Otherwise, the WTRU may transmit the UCI as a part of the PUSCH transmission in the allocated UL resource. UCI as part of a PUSCH transmission may be achieved by multiplexing UCI over one or more (e.g., certain) parts of PUSCH resource elements, e.g., according to rules known to the WTRU and the network. HARQ ACK feedback may be disabled (e.g., if a WTRU determines that one or more conditions as described herein are satisfied), or (e.g., Otherwise the WTRU may follow a HARQ ACK disabling configuration for the HARQ processes. A TBoMS length may be determined, for example, as a function of the OCC length (e.g., same length for both, if a WTRU determines that one or more conditions as described herein are satisfied).

[0198] A device (e.g., a WTRU) may (e.g., be configured to) perform one or more of the following actions.

[0199] The WTRU may receive configuration information, which for example may indicate(s) a configuration of orthogonal cover coded periodic CG UL PUSCH transmissions. The configuration information may indicate one or more of the following: an OCC length and / or an OCC sequence assigned to the WTRU; a selection of slot based or symbol based OCC repetitions; PUSCH transmission parameter(s); TBoMS related parameter(s) (e.g., a TBoMS parameter such as a length, a set of length parameters, and / or the like); and / or priority rules for PUSCH versus PUCCH transmissions.

[0200] The WTRU may determine slots n, n+1 , .... m, (e.g., where m is greater than or equal to n) for UL CG transmission. The slots may have one or more OCC spread PUSCH repetitions.

[0201] The WTRU may transmit UCI via a higher layer signaling (e.g., via a MAC CE), for example, if at least one or more of the following conditions are satisfied: an OCC length is longer than a threshold (e.g., an OCC length is greater than 1); UCI is to be transmitted in any of the slots carrying a PUSCH transmission; and / or UCI is available prior to PUSCH preparation time (e.g., n-PUSCH preparation time). The WTRU may drop a UCI transmission in slots n to m, for example, if (e.g., any) one or more of thefollowing conditions are satisfied: if UCI becomes available after a PUSCH preparation time (e.g., due to a UCI timeline) from the first slot of the OCC based PUSCH transmission; and / or if a CG transmission is a retransmission for a TB (e.g., a WTRU may not modify the re-transmission TB from the original transmission). The WTRU may transmit HARQ in an UL transmission (e.g., in an upcoming UL Tx opportunity) with (e.g., additional) information, e.g., the WTRU may transmit a HARQ status for (e.g., all) the active DL HARQ processes.

[0202] The WTRU may disable HARQ ACK feedback, or, e.g., otherwise, the WTRU may follow HARQ ACK disabling configuration for the HARQ processes (e.g., if the WTRU determines that one or more of the condition(s) described herein are satisfied).

[0203] The WTRU may determine a TBoMS length as a function of the OCC length (e.g., the same length for both), for example, if / when configured for TBoMS based PUSCH transmission (e.g., if the WTRU determines that a one or more of the condition(s) described herein are satisfied).

[0204] The WTRU may perform TB multiplexing and / or mapping over the scheduled and / or configured resource.

[0205] The WTRU may spread the modulated PUSCH symbols, for example, according to the configured slot / symbol wise OCC sequence.

[0206] The WTRU may transmit the OCC spread PUSCH symbols / slots over the UL resource.

[0207] An example device may include a processor configured to perform one or more actions. For example, a device (e.g., a WTRU) may receive configuration information. The configuration information may indicate at least OCC information associated with an UL PUSCH. The device may determine to send UCI via higher layer signaling. The determination to send the UCI via the higher layer signaling may be based on one or more conditions being satisfied. The one or more conditions may comprise an OCC length being greater than a threshold. The OCC length may be greater than the threshold. The device may disable HARQ ACK feedback or follow a HARQ ACK disabling configuration. The device may determine a TBoMS length, for example, as a function of the OCC length. The device may send the UCI via the higher layer signaling. The UCI may be multiplexed over a PUSCH transmission.

[0208] The configuration information may indicate the OCC length, an OCC sequence, and / or whether slot based or symbol based OCC repetitions are configured.

[0209] The one or more conditions may (e.g., further) comprise that the UCI is to be transmitted in a slot configured for PUSCH transmission and / or the UCI is available prior to a PUSCH preparation time.

[0210] The one or more conditions being satisfied may comprise the OCC length being greater than the threshold, that the UCI is to be transmitted in a slot configured for PUSCH transmission, and / or that the UCI is available prior to a PUSCH preparation time.

[0211] The device may not put the UCI in a slot indicated for re-transmission of a TB.

[0212] The device sending the UCI via higher layer signaling may comprise sending the UCI via a MACCE.

[0213] Systems, methods, and devices are described herein that may be associated with an uplink control information (UCI) transmission associated with an orthogonal cover code (OCC)-based physical uplink shared channel (PUSCH) in a New Radio (NR) non-terrestrial network (NTN). A wireless transmit / receive unit (WTRU) may include one or more of the following: a processor, a memory, or a transceiver (e.g., a transmitter and / or receiver). The WTRU may be configured to perform one or more of the following. The WTRU may receive an indication of an OCC length associated with an uplink (UL) PUSCH transmission. The WTRU may determine that the OCC length is greater than a threshold. The WTRU may determine that a condition is satisfied. The condition may be determined to be satisfied based at least on the determination that the OCC length is greater than the threshold. The WTRU may, based on the determination that the condition is satisfied, if an UCI is to be multiplexed and / or if the UCI is available prior to a PUSCH preparation time, send the UCI via a higher layer signaling.

[0214] A method may include one or more of the following. The method may include receiving an indication of an OCC length associated with a UL PUSCH transmission. The method may include determining that the OCC length is greater than a threshold. The method may include determining that a condition is satisfied. The condition may be determined to be satisfied based at least on the determination that the OCC length is greater than the threshold. The method may include, based on the determination that the condition is satisfied, if an UCI is to be multiplexed and / or if the UCI is available prior to a PUSCH preparation time, sending the UCI via a higher layer signaling.

[0215] The WTRU may be configured to perform (e.g., and / or the method may similarly include) one or more of the following. For example, the WTRU may determine that the UCI is to be transmitted in a slot carrying the UL PUSCH transmission. The condition may be determined to be satisfied further based on the determination that the UCI is to be transmitted in the slot carrying the UL PUSCH transmission. The WTRU may, based on the determination that the condition is satisfied and / or if the UCI becomes available after the PUSCH preparation time, send the UL PUSCH transmission without the UCI. The WTRU may determine a transport block size based on the OCC length. The WTRU may determine a transport block processing over multiple-slot (TBoMS) length as a function of the OCC length based on the determination that the condition is satisfied. If the UCI is to be multiplexed and / or if the UCI is available prior to thePUSCH preparation time, the UCI sent via the higher layer signaling may indicate HARQ ACK feedback, a configured grant (CG)-UCI, and / or channel state information. The higher layer signaling may be a medium access control element (MAC CE). The WTRU may disable HARQ feedback based on the determination that the condition is satisfied.

[0216] Although features and elements described above are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without other features and elements.

[0217] Although the implementations described herein may consider 3GPP specific protocols, it is understood that the implementations described herein are not restricted to this scenario and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, NR or 5G specific protocols, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well.

[0218] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and / or wireless connections) and / or computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as compact disc (CD)-ROM disks, and / or digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

CLAIMSWhat Is Claimed Is:

1. A wireless transmit / receive unit (WTRU), comprising: a processor configured to: receive an indication of an orthogonal cover code (OCC) length associated with an uplink (UL) physical uplink shared channel (PUSCH) transmission; determine that the OCC length is greater than a threshold; determine that a condition is satisfied, wherein the condition is determined to be satisfied based at least on the determination that the OCC length is greater than the threshold; and based on the determination that the condition is satisfied: if an uplink control information (UCI) is to be multiplexed, and if the UCI is available prior to a PUSCH preparation time, send the UCI via a higher layer signaling.

2. The WTRU of claim 1, wherein the processor is further configured to: determine that the UCI is to be transmitted in a slot carrying the UL PUSCH transmission, wherein the condition is determined to be satisfied further based on the determination that the UCI is to be transmitted in the slot carrying the UL PUSCH transmission.

3. The WTRU of claim 1, wherein the processor is further configured to, based on the determination that the condition is satisfied: if the UCI becomes available after the PUSCH preparation time, send the UL PUSCH transmission without the UCI.

4. The WTRU of claim 1 , wherein the processor is further configured to determine a transport block size based on the OCC length.

5. The WTRU of claim 1 , wherein the processor is further configured to determine a transport block processing over multiple-slot (TBoMS) length as a function of the OCC length based on the determination that the condition is satisfied.

6. The WTRU of claim 1 , wherein if the UCI is to be multiplexed and if the UCI is available prior to the PUSCH preparation time, the UCI sent via the higher layer signaling indicates HARQ ACK feedback, a configuredgrant (CG)-UCI, or channel state information.

7. The WTRU of claim 1 , wherein the higher layer signaling is a medium access control element (MAC CE).

8. The WTRU of claim 1 , wherein the processor is further configured to disable HARQ feedback based on the determination that the condition is satisfied.

9. A method comprising: receiving an indication of an orthogonal cover code (OCC) length associated with an uplink (UL) physical uplink shared channel (PUSCH) transmission; determining that the OCC length is greater than a threshold; determining that a condition is satisfied, wherein the condition is determined to be satisfied based at least on the determination that the OCC length is greater than the threshold; and based on the determination that the condition is satisfied: if an uplink control information (UCI) is to be multiplexed, and if the UCI is available prior to a PUSCH preparation time, sending the UCI via a higher layer signaling.

10. The method of claim 9, wherein the method further comprises: determining that the UCI is to be transmitted in a slot carrying the UL PUSCH transmission, wherein the condition is determined to be satisfied further based on the determination that the UCI is to be transmitted in the slot carrying the UL PUSCH transmission.

11. The method of claim 9, wherein the method further comprises, based on the determination that the condition is satisfied: if the UCI becomes available after the PUSCH preparation time, sending the UL PUSCH transmission without the UCI.

12. The method of claim 9, wherein the method further comprises determining a transport block size based on the OCC length.

13. The method of claim 9, wherein the method further comprises determining a transport block processing over multiple-slot (TBoMS) length as a function of the OCC length based on the determination that the condition is satisfied.

14. The method of claim 9, wherein if the UCI is to be multiplexed and if the UCI is available prior to thePUSCH preparation time, the UCI sent via the higher layer signaling indicates HARQ ACK feedback, a configured grant (CG)-UCI, or channel state information.

15. The method of claim 9, wherein the higher layer signaling is a medium access control element (MAC CE).

Images