Multiplexing and priority indication for two codeword transmissions

Abstract

The WTRU may be configured to transmit UL-SCH data and / or UCI using one or more CWs (e.g., a first CW (CW1) and a second CW (CW2)) based on a UL-SCH indicator received in an uplink (UL) grant. For example, a WTRU may receive a UL grant using two CWs and / or an indication to schedule a PUSCH transmission. The indication may be, for example, a UL-SCH indicator in a UL grant DCI. The WTRU may determine a value of the UL-SCH indicator (e.g., a value of a field in the UL grant DCI). In an example, a WTRU may transmit UL-SCH data and / or UCI using one or more of a CW1 and a CW2. Each CW for UL-SCH data or UCI may be determined based on any of: an indication; attributes and / or parameters of at least one of the CWs; and / or criticality, importance and / or priority of the UCI.

Description

[0001] Cross-references to related applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 445,569, filed February 14, 2023, and U.S. Provisional Patent Application No. 63 / 617,903, filed January 5, 2024, the entire contents of which are incorporated herein by reference. Background Technology

[0002] The 8TX WTRU can support uplink transmission up to 8 layers. For uplink transmission up to rank 4, a single CW (Callable Wave) can be supported. For transmissions with a rank greater than 4, more than one CW can be used. The 8TX WTRU can use more than one CW for uplink transmission. The Radio Transmitter / Receiver Unit (WTRU) can use a single CW to transmit up to 4 layers. Enhancements such as UL-SCH, β_Offset, priority indication, and the like can be provided for dynamic indication of transmission parameters and control. In the example, the number of indications can be increased proportionally to the number of CWs. However, proportionally increasing the number of indications may lead to increased use of the downlink control channel. Summary of the Invention

[0003] A Wireless Transmitter Receiver Unit (WTRU) can be configured to receive an uplink (UL) grant that uses a first Channel Warp (CW) and a second CW to schedule Physical Uplink Shared Channel (PUSCH) transmissions. The UL grant may include an Uplink Shared Channel (UL-SCH) indicator. The WTRU can be configured to determine the value of the UL-SCH indicator. The WTRU can be configured to determine, based on the UL-SCH indicator having a first value, whether to use the first CW and the second CW to transmit UL-SCH data. If the UL-SCH indicator has a second value, the WTRU can determine to use the first CW to transmit UL-SCH data. The WTRU can be configured to determine, based on the UL-SCH indicator having the second value and parameters, whether to use the second CW to transmit UL-SCH data or Uplink Control Information (UCI). The WTRU can be configured to use either the first or second CW to transmit UL-SCH data or UCI based on this determination.

[0004] The parameter can be associated with the second CW. The parameter can include a configuration indicated in downlink control information (DCI), a modulation and coding scheme (MCS), an antenna group, a new data indicator (NDI), a hybrid automatic repeat request (HARQ) process identification, a transmission / reception point (TRP), or a sounding reference signal (SRS) resource indicator (SRI). The NDI can be toggled or not toggled. The TRP can be primary or secondary. The SRS can indicate whether the CW is associated with a first SRI or a second SRI. The parameter can include a priority of the UCI.

[0005] The priority can be associated with HARQ feedback or time critical CSI. The priority can indicate transmission on the first CW or the second CW.

[0006] The parameter can include a UCI size threshold. If the UCI at the WTRU is greater than the UCI size threshold, the WTRU can be configured to transmit the UCI using the second CW. If the UCI at the WTRU is less than the UCI size threshold, the WTRU can be configured to transmit UL-SCH data using the second CW. The UL-SCH indicator can include a field in the UL grant DCI.

[0007] A WTRU includes a processor that can be configured to receive a UL grant that schedules a PUSCH transmission using a first CW (CW) and a second CW. The UL grant can include a UL shared channel (UL-SCH) indicator. The WTRU can be configured to determine a value of the UL-SCH indicator. The WTRU can be configured to determine whether to transmit UL-SCH data or uplink control information (UCI) using the first CW and the second CW based on the value. If the WTRU determines that the UL-SCH indicator has a first value, the processor can be configured to determine to transmit UL-SCH data using the first CW and the second CW. If the WTRU determines that the UL-SCH indicator has a second value, the processor can be configured to determine to transmit uplink control information (UCI) using the first CW and the second CW. The WTRU can be configured to transmit the UL-SCH data or the UCI using the first and second CW based on the determination. The UL-SCH indicator can include a field in the UL grant DCI. BRIEF DESCRIPTION OF DRAWINGS

[0008] Figure 1A FIG. 1 is a system diagram illustrating an example communications system in which one or more disclosed embodiments can be implemented.

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

[0010] Figure 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that can be used within the communications system Figure 1A illustrated in FIG. 1.

[0011] Figure 1D is a system diagram illustrating a further example RAN and a further example CN that can be used within the communications system Figure 1A illustrated in FIG. 1.

[0012] Figure 2 is a table of example mappings of four beta offset indication values to offset indices.

[0013] Figures 3A-3B is an example flow diagram illustrating a procedure for priority indication based on configured DCI field lengths. DETAILED DESCRIPTION

[0014] Figure 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments can be implemented. The communications system 100 can be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 can enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 can 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.

[0015] As Figure 1AAs shown in FIG. 1, the communications system 100 can include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a CN 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 network elements. Each of the WTRUs 102a, 102b, 102c, 102d can 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 can be referred to as a “station” and / or a “STA”)

[0016] The communications system 100 can also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b can 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 can 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 can include any number of interconnected base stations and / or network elements.

[0017] The base stations 114a can be part of the RAN 104 / 113, which can 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 stations 114a and / or the base stations 114b can be configured to transmit and / or receive wireless signals on one or more carrier frequencies (which can be referred to as a cell (not shown)). These frequencies can be in the licensed spectrum, the unlicensed spectrum, or a combination of the licensed and unlicensed spectrums. A cell can provide wireless service to a particular geographic area that can be fixed or it can change in size and shape as network and / or user conditions change. A cell can further be divided into cell sectors each with an associated coverage area. For example, the cell associated with a base station 114a can be divided into three sectors. Thus, in one embodiment, the base station 114a can include three transceivers, one for each sector of the cell. In an embodiment, the base station 114a can employ multiple-input multiple-output (MIMO) techniques and can utilize multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in a desired spatial direction.

[0018] The base stations 114a, 114b can communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over the air interface 116, which can 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 can be established using any suitable radio access technology (RAT).

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

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

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

[0022] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c can implement multiple radio access technologies. For example, the base station 114a and WTRUs 102a, 102b, 102c can implement LTE wireless access and NR wireless access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c can 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).

[0023] In other embodiments, the base station 114a and WTRUs 102a, 102b, 102c can 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 IX, 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.

[0024] Figure 1AThe base station 114b in such embodiments can be, for example, a wireless router, Home Node B, Home eNode B, or access point, and can utilize any suitable RAT for facilitating wireless connectivity access in a localized 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 can 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 can 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 can 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. 1C, the base station 114b can have a direct connection to the Internet 110. Thus, the base station 114b can not be required to access the Internet 110 via the CN 106 / 115. Figure 1A

[0025] The RAN 104 / 113 can be in communication with the CN 106 / 115, which can 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 can 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 can 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 can 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 can employ a NR radio technology, the CN 106 / 115 can also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology. Figure 1A

[0026] ​​The CN 106 / 115 can 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 can include circuit-switched telephone networks that provide infrastructure for the provision of voice telephony. The Internet 110 can 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 can include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 can include another CN connected to one or more RANs, which can employ the same RAT as the RAN 104 / 113 or a different RAT.

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

[0028] Figure 1B is a system diagram of an example WTRU 102. As shown in Figure 1C, the WTRU 102 can 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 can include any sub-combination of the foregoing elements while remaining consistent with an embodiment. Figure 1B

[0029] ​The processor 118 can 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 Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 can 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 can be coupled to the transceiver 120, which can be coupled to the transmit / receive element 122. While Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it will be understood that the processor 118 and the transceiver 120 can be integrated together in an electronic package or chip.

[0030] The transmit / receive element 122 can 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 can be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 can 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 can be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0031] Although the transmit / receive element 122 is depicted in the WTRU 102 Figure 1B In one embodiment, the WTRU 102 can include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0032] The transceiver 120 can be configured to modulate information to be transmitted by the transmit / receive element 122 and to demodulate information received by the transmit / receive element 122. As indicated above, the WTRU 102 can be a multi-mode device. Thus, the transceiver 120 can include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[0033] The processor 118 of the WTRU 102 can be coupled to, and can 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 can also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 can 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 can include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 can 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 can 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).

[0034] The processor 118 can receive power from the power source 134 and can be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 can be any suitable device for powering the WTRU 102. For example, the power source 134 can 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.

[0035] The processor 118 can also be coupled to the GPS chipset 136, which can 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 can 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 can acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0036] The processor 118 can further be coupled to other peripherals 138 that can include one or more software modules and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 can 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 frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or an augmented reality (VR / A R) device, an activity tracker, and the like. The peripherals 138 can include one or more sensors, which can 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.

[0037] The WTRU 102 can include a full duplex radio for which transmission and reception of some or all signals can be concurrent and / or simultaneous. The full duplex radio can include an interference management unit 139 to reduce and / or substantially eliminate self-interference and / or mutual interference between the transmission and reception. In an embodiment, the WRTU 102 can include a half duplex radio for which transmission and reception cannot be concurrent and / or simultaneous.

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

[0039] The RAN 104 can include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 can include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c can 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 can implement MIMO technology. Thus, the eNode-B 160a, for example, can use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

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

[0041] Figure 1C The CN 106 shown in FIG. 10 can 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 can be owned and / or operated by an entity other than the CN operator.

[0042] The MME 162 can be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and can serve as a control node. For example, the MME 162 can 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 can 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.

[0043] ​The SGW 164 can be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 can generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 can 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.

[0044] The SGW 164 can be connected to the PGW 166, which can 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.

[0045] The CN 106 can also serve as a gateway for the WTRUs 102a, 102b, 102c to access the PSTN 108, the Internet 110, or other networks 112. The PSTN 108 can include circuit-switched

[0046] Although WTRUs are described in Figures 1A-1D as wireless terminals, it is contemplated that in certain representative embodiments some terminals can use wired communication interfaces in addition to or instead of wireless communication interfaces.

[0047] In representative embodiments, the other network 112 can be a WLAN.

[0048] A WLAN in Infrastructure Basic Service Set (BSS) mode can have an Access Point (AP) which can be used by one or more stations (STAs) associated with the AP for communication. The AP can 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 from the BSS. Traffic to STAs that originates from outside the BSS can arrive through the AP and can be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS can be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS can be sent through the AP, for example, where the source STA can send traffic to the AP and the AP can deliver the traffic to the destination STA. The traffic between STAs within a BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS can use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode can not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS can communicate directly with each other. The IBSS mode of communication can sometimes be referred to herein as "ad-hoc" mode of communication.

[0049] When using an 802.11 ac infrastructure mode of operation or similar modes of operation, an AP can transmit beacons on a fixed channel, such as a primary channel. The primary channel can be a fixed width (e.g., 20 MHz wide bandwidth) or a width that is dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by STAs to establish a connection with the AP. In certain representative embodiments, a carrier sense multiple access with collision avoidance (CSMA / CA) with collision avoidance can be implemented, for example, in 802.11 systems. For CSMA / CA, a STA, including the AP (e.g., each STA) can sense the primary channel. If the primary channel is sensed / detected as busy and / or determined to be busy by a particular STA, the particular STA can back off. Only one STA can transmit in a given BSS at any given time.

[0050] High Throughput (HT) STAs can use 40 MHz wide channels 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.

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

[0052] 802.11af and 802.11ah support sub-1 GHz modes of operation. The channel operating bandwidth and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11η and 802.11ac. 802.11af 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 representative embodiments, 802.11ah can support meter type control / machine type communication, such as MTC devices in a macro coverage area. MTC devices can have certain capabilities, e.g., limited capabilities, including support for (e.g., support only) certain bandwidths and / or limited bandwidth. MTC devices can include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0053] WLAN systems that can support multiple channels and channel bandwidths such as 802.11η, 802.11ac, 802.11af, and 802.11ah include a channel that can be designated as a primary channel. The primary channel can have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by a STA from among all STAs operating in the BSS that supports the smallest bandwidth operating mode. In the example of 802.11ah, for a STA (e.g., MTC-type device) that supports (e.g., only supports) a 1 MHz mode, the primary channel can be 1 MHz wide even if other STAs in the AP and 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 can depend on the status of the primary channel. If the primary channel is busy, e.g., due to a STA (that only supports a 1 MHz operating mode) transmitting to the AP, then the entire available frequency band can be considered busy even if most of the frequency band remains idle and can be available.

[0054] In the United States, the available frequency bands for 802.11ah use is from 902 MHz to 928 MHz. In Korea, the available frequency bands is from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands is from 916.5 MHz to 927.5 MHz. Depending on the country code, the total bandwidth available for 802.11ah is 6 MHz to 26 MHz.

[0055] Figure 1D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As

[0056] The RAN 113 can include gNBs 180a, 180b, 180c, although it will be appreciated that the RAN 113 can include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c can 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 can implement MIMO technology. For example, gNBs 180a, 108b can utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, can 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 can implement carrier aggregation technology. For example, the gNB 180a can transmit multiple component carriers (not shown) to the WTRU 102a. A subset of these component carriers can be on unlicensed spectrum while the remaining component carriers can be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c can implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0057] The WTRUs 102a, 102b, 102c can use transmissions associated with a scalable numerology to communicate with gNBs 180a, 180b, 180c. For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary from transmission to transmission, from cell to cell, and / or from portion of the wireless transmission spectrum to portion of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c can communicate with gNBs 180a, 180b, 180c using subframes 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).

[0058] The gNBs 180a, 180b, 180c can be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, the WTRUs 102a, 102b, 102c can communicate with the gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, the WTRUs 102a, 102b, 102c can utilize signals according to one or more standards developed by

[0059] Each of the gNBs 180a, 180b, 180c can be associated with a particular cell (not shown) and can 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 functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. 1C, the gNBs 180a, 180b, 180c can communicate with one another over an Xn interface. Figure 1D As shown, the gNBs 180a, 180b, 180c can communicate with one another over an Xn interface.

[0060] Figure 1DThe CN 115, as shown in FIG. 10B, can 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 can be owned and / or operated by an entity other than the CN operator.

[0061] The AMF 182a, 182b can be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and can serve as a control node. For example, the AMF 182a, 182b can be responsible for authenticating the WTRUs 102a, 102b, 102c, supporting 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 can be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the type of service plans the WTRU 102a, 102b, 102c has subscribed to. For example, different network slices can be set up 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 can provide control plane functionality 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.

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

[0063] The UPF 184a, 184b can be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which can 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 can perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering of downlink packets, providing mobility anchoring, and the like.

[0064] The CN 115 can facilitate communications with other networks. For example, the CN 115 can include, or can 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 can provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which can include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c can be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface between the UPF 184a, 184b and the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0065] In view of Figures 1A-1D And Figures 1A-1D In view of the corresponding description of the above, one or more or all of the functions described herein with reference to one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein can be performed by one or more emulation devices (not shown). The emulation devices can be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices can be used to test other devices and / or to simulate network and / or WTRU functionality.

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

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

[0068] For uplink transmissions, there can be coverage, reliability, and / or throughput enhancements. For example, an eight antenna (8TX) WTRU can support eight layers for UL transmission. For uplink transmissions up to rank four, a single codeword (CW) can be supported. However, for transmissions with a rank greater than four, more than one CW can be used. Embodiments discussed herein can enable more than one CW transmission for uplink, with a focus on supporting two CW transmissions by an 8TX WTRU. It should also be understood that embodiments discussed herein are equally applicable to other cases of number of CWs and TX antenna size.

[0069] In an example, a WTRU can transmit four layers using a single CW transmission. To support more than one CW transmission in uplink, there can be dynamic indication of transmission parameters and control, e.g., UL-SCH, β_Offset, priority indication, etc. For example, one approach can be to increase the number of such indications proportionally to the number of CWs. However, such a solution can result in a significant increase in downlink control channel. As such, embodiments discussed herein support dynamic indication of transmission parameters and control for uplink transmission using more than one CW.

[0070] For multiplexing and / or priority indication of two CW transmissions in UL, there can be latency and / or coverage enhancements. In an example, a wireless transmit / receive unit (WTRU) can be configured for enhanced dynamic indication of uplink shared channel (UL-SCH), beta offset, and / or priority indication. The WTRU can be configured to provide UL-SCH indication for two CW operation. The WTRU can provide (e.g., be configured for) UCI multiplexing for two CW transmissions. In an example, the WTRU can be configured to provide priority indication for two CW transmissions.

[0071] For two CW operation, there can be a UL-SCH indication. A WTRU can be configured to use one or more CWs (e.g., a first CW (CW1) and a second CW (CW2)) to transmit UL-SCH data and / or UCI based on a received UL-SCH indicator. In an example, a WTRU can receive a UL grant that indicates scheduling a PUSCH transmission using 2 CWs. The indication can be, for example but not limited to, a UL-SCH indicator, which can be a field (e.g., a 1-bit field) in a UL grant DCI, and / or can have a value. A WTRU can determine a value of the UL-SCH indicator (e.g., a value of the field in the UL grant DCI). In an example, a WTRU can use one or more of CW1 and CW2 to transmit UL-SCH data and / or UCI. Each CW to use for UL-SCH data or UCI can be determined based on any of the following: an indication; a property and / or parameter of at least one of the CWs; and / or criticality, importance, and / or priority of the UCI. For example, a parameter and / or property of at least one of the CW(s) can be based on a configuration and / or indication in a DCI. In an example, the property and / or parameter can include one or more of the following: a modulation and coding scheme (MCS), an antenna group, a new data indicator (NDI), a HARQ process ID, a transmission / reception port (TRP), and / or a sounding reference signal (SRS) resource indicator (SRI). The NDI can or can not be toggled. The TRP can be primary or secondary. In an example, the SRS can indicate whether a CW is associated with a first SRI or a second SRI. The criticality, importance, and / or priority of the UCI can be based on, for example, HARQ feedback and / or time critical channel state information (CSI) that is indicated to be transmitted on a CW (e.g., a first CW (CW1) or a second CW (CW2)). In an example, the criticality, importance, and / or priority can be based on a respective property or parameter of a CW. For example, if the UCI includes CSI associated with a high (e.g., first) priority and CSI associated with a low priority (e.g., a second priority that is lower than the first priority), a WTRU can be configured to map the high priority CSI or the first priority CSI to a CW with a higher MCS and map the low priority CSI or the second priority CSI to a CW with a lower MCS.

[0072] UCI multiplexing for two CW transmissions can be described herein. A WTRU can be configured to determine a CW and / or resource usage for UCI multiplexing. A WTRU can receive a configuration of a threshold. For example, a WTRU can be configured to receive a configuration of a threshold to determine UCI splitting. In an example, a WTRU can be configured to receive an UL grant scheduling a PUSCH transmission using 2 CWs (e.g., a first CW (CW1) and a second CW (CW2)). In an example, a WTRU can be configured to determine whether to use one or more CWs to transmit UCI based on a size of the UCI. For example, if the UCI size is greater than a threshold, a WTRU can be configured to split the UCI into two parts and transmit one part using CW1 and another part using CW2. If the UCI size is less than the threshold, a WTRU can use one CW (e.g., CW1 or CW2) to transmit the UCI. For example, based on the size of the UCI, one CW can be used to transmit the UCI. For example, a WTRU can use a CW with a higher or lower MCS to transmit the UCI based on a priority of the UCI. In an example, a MCS of a CW can be indicated by a scheduling grant (e.g., a scheduling DCI). A WTRU can determine one or more CWs based on the configuration and use the determined one or more CWs to transmit the UCI. For example, a WTRU can be configured to use one or more of CW1 and CW2 to transmit the UCI based on a size of the UCI and whether UL-SCH data is also to be transmitted. For example, a WTRU can be configured to use different thresholds (e.g., separately configured, higher or lower thresholds) to determine whether to split the UCI between two CWs when UL-SCH data is to be transmitted.

[0073] For two CW transmissions, there can be a UL-SCH indication. In an example, a WTRU can be configured to determine a priority of one or more CWs. In an example, a WTRU can receive a UL grant that schedules a PUSCH transmission using 2 CWs and / or a UL-SCH indicator. The UL-SCH indicator can include one or more values and / or parameters (e.g., priority indicator in UL grant DCI). In an example, a WTRU can determine a priority of one or more CWs based on a size of the indication (e.g., size of the indicator field). In an example, a WTRU can be configured to set a priority of one or more CWs based on an indication field with more than one information element. In an example, a WTRU can be configured to set a priority of one or more CWs based on an indication field with a single information element. In an example, a WTRU can determine a CW to use for a transmission (e.g., transmission of UL-SCH data) based on one or more of the following: an association with a highest MCS, an association with a toggled NDI, an association with a particular TRP (e.g., primary / secondary TRP), and / or determined by a semi-static or dynamic indication (e.g., RRC configured indication, MAC-CE, or another DCI). In an example, a WTRU can transmit a PUSCH according to the determined priority, unless the transmission would result in a collision with a PUCCH.

[0074] The following description is for exemplary purposes, and is not intended to limit the applicability of the methods described herein to any wireless technology and / or other technology, as applicable. The term network in this disclosure can refer to one or more gNBs, which in turn can be associated with one or more TRPs, or any other node in a radio access network.

[0075] A WTRU can receive an UL-SCH indicator for two CW operations. The WTRU can be configured to use one or more CWs (e.g., a first CW (CW1) and a second CW (CW2)) to transmit UL-SCH data and / or UCI based on the received UL-SCH indicator. In an example, a WTRU can receive an UL grant that schedules a PUSCH transmission using one or more (e.g., two) CWs. The UL grant can include an indicator. The indicator can be, for example, an UL-SCH indicator, which can be a field (e.g., a 1-bit field) in the UL grant DCI. In an example, the WTRU can use one or more of a first (e.g., CW1) and a second (e.g., CW2) to transmit UL-SCH data and / or UCI. The WTRU can determine to use one or more of CW1 and CW2 to transmit UL-SCH data and / or UCI based on the indicator and / or one or more of the following: a property or parameter of at least one of the CWs, and / or criticality, importance, and / or priority of the UCI. For example, the property or parameter of at least one of the CWs can be based on a configuration and / or indication in the DCI. In an example, the property and / or parameter can include one or more of the following: MCS, antenna group, NDI, HARQ process ID, TRP, and SRS. The NDI can or can not be toggled. The TRP can be primary or secondary. The SRS can be based on whether the CW has a first SRI or a second SRI. The criticality, importance, and / or priority of the UCI can be based on, for example, HARQ feedback and / or time-critical channel state information (CSI) that is indicated to be transmitted on a CW (e.g., a first CW (CW1) or a second CW (CW2)). In an example, the criticality, importance, and / or priority can be based on the respective property or parameter of the CW. For example, if the UCI includes CSI associated with a high (e.g., first) priority and CSI associated with a low priority (e.g., a second priority that is lower than the first priority), the WTRU can be configured to map the high priority CSI or the first priority CSI to a CW with a higher MCS and the low priority CSI or the second priority CSI to a CW with a lower MCS.

[0076] The UL-SCH indicator can include a bit field. The bit field of the UL-SCH indicator can include a value. The WTRU can determine the value of the UL-SCH indicator bit field. The WTRU can determine to use one or more CWs to transmit data based on the determined value of the UL-SCH indicator bit field. In an example, a UL-SCH bit field value (e.g., value 1) can indicate that UL-SCH is to be transmitted on PUSCH. In an example, a UL-SCH bit field value (e.g., value 0) can indicate that UL-SCH is not to be transmitted on PUSCH (e.g., only UCI). The WTRU can be scheduled with PUSCH transmission using 2 CWs and can receive a UL-SCH indicator including a single bit field. If the UL-SCH indicator includes a single UL-SCH bit field, the WTRU can implement one or more of the following behaviors.

[0077] The WTRU can operate based on the selection of one of the CWs. If the WTRU receives a UL-SCH indicator including a single bit field, the WTRU can operate based on the selection of one of the CWs. The WTRU can determine the value of the UL-SCH indicator (e.g., the value of the bit field of the UL-SCH) and determine one or more CWs for transmission based on the determined value. The received UL-SCH bit field can indicate an operation to be applied using one or more of the CWs. In an example, the state of the UL-SCH indicator can apply to one CW (e.g., CW1 or CW2) while the other CW can remain dedicated for UL-SCH. For example, if the UL-SCH indicator value = “1”, CW1 can be used for UL-SCH data while CW2 can be used for UL-SCH data. For example, if the UL-SCH indicator value = “0”, CW1 can be used for UL-SCH data while CW2 can be used for UCI.

[0078] The WTRU can determine the CW that remains dedicated and the CW that is targeted (e.g., indicates for UL-SCH data or UCI) as the UL-SCH indicator bit field based on one or more of the following: a CW with a higher MCS; a CW associated with a set of antennas; a CW associated with a toggled NDI; a CW associated with a particular HARQ process ID; a CW associated with a particular TRP (e.g., primary / secondary TRP); and / or a CW associated with a first SRI or a second SRI.

[0079] If the WTRU receives a UL-SCH indicator including a single bit field, the WTRU can operate based on selecting one CW or two CWs. For example, if the UL-SCH indicator value = "0" (e.g., which can be interpreted to indicate UCI transmission only), the WTRU can determine whether to use one CW or two CWs to transmit UCI based on UCI size and / or type (e.g., UCI size threshold). For example, if the UL-SCH indicator value = "1", the WTRU can determine that CW1 can be used for UL-SCH data and CW2 can be used for UL-SCH data. If the UL-SCH indicator value = "0", the WTRU can determine whether to use one or two CWs to transmit UCI based on UCI size threshold. For example, if the UL-SCH indicator value = "0" and UCI size is greater than UCI size threshold, the WTRU can determine to use two CWs to transmit UCI. The WTRU can split UCI onto two CWs for transmission. For example, the WTRU can split and map CW1 = UCI and CW2 = UCI. For example, if the UL-SCH indicator value = "0" and UCI size does not satisfy UCI size threshold, the WTRU can map UCI onto a single CW. In an example, the WTRU can map CW1 = UCI and CW2 = UL-SCH.

[0080] If the WTRU receives a UL-SCH indicator including a single bit field, the WTRU can operate based on applying the status of the UL-SCH indicator on two CWs. The WTRU can receive a UL-SCH indicator including a bit field and determine a value of the received UL-SCH indicator. The WTRU can determine to apply the determined value of the UL-SCH indicator to two CWs. In an example, the WTRU can determine whether to use both a first CW and a second CW to transmit UL-SCH data or UCI based on the determined value of the UL-SCH indicator. For example, both CWs can transmit UL-SCH data or UCI. For example, if the UL-SCH indicator value = "1", the WTRU can determine to use CW1 and CW2 to transmit UL-SCH data. For example, if the UL-SCH indicator value = "0", the WTRU can determine to use both CW1 and CW2 to transmit UCI.

[0081] If the WTRU applies the state of UL-SCH indicator on two CWs, the WTRU can determine the mapping of the CWs (e.g., mapping data to CW1 and CW2). For example, the WTRU can map time critical CSI to one or more of the following: a CW associated with a higher MCS; a CW associated with an antenna group; a CW associated with toggled NDI; a CW associated with a specific HARQ process ID; a CW associated with a specific TRP (e.g., primary / secondary TRP); and / or a CW associated with a first SRI or a second SRI. In an example, the time critical CSI can be Type II Part I, aperiodic CSI measurement, Doppler related CSI, etc.

[0082] The WTRU can receive an indication (e.g., UL-SCH indicator) in the UL grant (e.g., from a gNB) on whether the WTRU can transmit UCI without UL data (e.g., UL-SCH) on the granted PUSCH resource. In an example, for “UCI only on PUSCH”, the WTRU can transmit UCI without UL-SCH on the granted PUSCH resource. In an example, for “UCI piggybacked PUSCH”, the WTRU can transmit UCI and UL-SCH on the granted PUSCH resource based on the indication in the UL grant. The indication in the UL grant can be the UL-SCH indicator and can include a bit field. The WTRU can determine the value of the UL-SCH indicator. The uplink can be dynamic grant, semi-persistent grant, or configured grant. The dynamic grant can provide an indication of PUSCH resource per DCI scheduling. The semi-persistent grant can provide an indication of a set of PUSCH resources per DCI for a given time window. The configured grant can provide an indication that the PUSCH resource can be semi-statically configured or activated and deactivated. UCI only on PUSCH can be a PUSCH transmission where the coded bits of UCI can be transmitted in the granted PUSCH resource. UCI piggybacked PUSCH can be a PUSCH transmission where UCI and UL-SCH can be transmitted together in the granted PUSCH resource.

[0083] In an example, if a single UL-SCH bit field is indicated and two CWs can be used for PUSCH, and the UL-SCH bit indicates UCI only on PUSCH, the WTRU can perform UCI only on PUSCH for one or both of the CWs. Note that UCI only on PUSCH can be used interchangeably with “UCI only” and “UCI only PUSCH”. Also, note that “CW” can be used interchangeably with “CW”.

[0084] A WTRU can be configured to apply a determined UL-SCH indicator value (e.g., a bit field) to one of the CWs. A WTRU can be configured to use one of CW1 or CW2 for transmission of UL-SCH data and / or UCI based on the UL-SCH indicator value determined by the WTRU. In an example, if UCI is reported in PUSCH using two CWs, a WTRU can be configured to report or piggyback UCI in one of the CWs.

[0085] A WTRU can determine to use one or more CWs for transmission of UL-SCH data or UCI based on the UL-SCH indicator with parameters. In an example, a WTRU can determine one of the CWs for UCI reporting based on parameters of the UL-SCH indicator including one or more of: an associated MCS for each CW; a CW identification; a CW with new data transmission; an associated HARQ process identification; an associated antenna group; an associated SRI index; an associated TRP index; an associated timing advance (TA) value; and / or UCI bit overhead. In an example, if the UL-SCH indicator bit field indicates UCI only on PUSCH, a WTRU can determine a CW for UCI only transmission on PUSCH based on one or more of: an associated MCS for each CW; a CW identification; a CW with new data transmission; an associated HARQ process identification; an associated antenna group; an associated SRI index; an associated TRP index; an associated TA value; and / or UCI bit overhead.

[0086] A WTRU can determine a CW for transmission based on an associated MCS for each CW. A WTRU can determine to use a CW with a higher MCS level. The MCS level can be indicated or determined. In an example, if two CWs have the same MCS level, a WTRU can use a CW with the lowest (or highest) CW identification for UCI transmission.

[0087] A WTRU can determine a CW for transmission based on a CW identification. A WTRU can determine a CW with the lowest (or highest) CW identification for UCI transmission.

[0088] A WTRU can determine a CW for transmission based on a CW with new data transmission (e.g., a CW with toggled NDI). For example, if there are two CWs for PUSCH and a first CW is indicated for retransmission (e.g., NDI not toggled) and a second CW is indicated for new transmission (e.g., NDI toggled), a WTRU can determine to use the second CW for transmission of UCI.

[0089] A WTRU can determine a CW for transmission based on an associated HARQ process identification. A WTRU can determine a CW for UCI transmission based on an associated HARQ process identification. In an example, a WTRU can determine a CW for transmission if the associated HARQ process identification of the CW satisfies one or more of the following: one or more HARQ process identifications configured for UCI transmission; an even (or odd) HARQ process identification; and / or a HARQ process identification modulo X becomes Y. In some cases, X and / or Y can be a predetermined number (e.g., X = 3, Y = 0). In some other cases, X and / or Y can be a number configured via higher layer signaling.

[0090] A WTRU can determine a CW for transmission based on an associated antenna group. For example, each CW can be associated with an antenna group, and a WTRU can determine a CW based on an associated antenna group identification.

[0091] A WTRU can determine a CW for transmission based on an associated SRI index. A WTRU can receive one or more SRIs for PUSCH transmission. One or more CWs (e.g., each CW) can be associated with an SRI. A WTRU can determine a CW for UCI transmission if a particular SRI is indicated for the respective CW.

[0092] A WTRU can determine a CW for transmission based on an associated TRP index. For example, if a WTRU is indicated for PUSCH transmission using multiple CWs, each CW can be associated with a TRP (e.g., a CSI-RS or an SSB). A WTRU can determine a CW associated with a particular TRP or TRP identification (e.g., a primary TRP, a serving cell TRP, and the like).

[0093] A WTRU can determine a CW for transmission based on an associated TA value. One or more CWs (e.g., each CW) can be associated with a particular TA value. In an example, a WTRU can determine a CW with a minimum TA value for UCI transmission. Note that a CW associated with a minimum TA value can be considered as a CW targeting a TRP closest to the WTRU.

[0094] A WTRU can determine a CW for transmission based on UCI bit overhead and / or UCI size. If a UCI overhead (or UCI size) is higher than a threshold (e.g., a UCI size threshold), a WTRU can determine a CW with a higher MCS. In an example, if a UCI overhead (or UCI size) is lower than a threshold (e.g., a UCI size threshold), a WTRU can determine a CW with a lower MCS.

[0095] In an example, the WTRU can apply a different set (or sets) of conditions to determine one or more CWs for UCI transmission based on the UL-SCH indicator and / or parameter. For example, if the WTRU determines that the UL-SCH indicator value = “0”, the WTRU can use a first set of conditions to determine the CWs for UCI transmission. In an example, if the WTRU determines that the UL-SCH indicator value = “1”, the WTRU can be configured to use a second set of conditions to determine the CWs for UCI transmission. For example, the first set of conditions can include CWs with higher MCS, and the second set of conditions can include CWs with HARQ process identification.

[0096] In an example, the WTRU can determine the number of CWs for transmission (e.g., UCI transmission) based on the size of the UCI. The UCI can be transmitted in a granted PUSCH. For example, if the UCI size is greater than a threshold (e.g., UCI size threshold), the WTRU can determine to use a first number of CWs (e.g., 2 CWs) to transmit the UCI. For example, if the UCI size is less than or equal to the threshold (e.g., UCI size threshold), the WTRU can determine to use a second number of CWs (e.g., 1 CW) to transmit the UCI. In an example, multiple CWs can be used for UCI transmission. The WTRU can transmit high priority UCI in a first CW and the rest of the UCI in a second CW. The high priority UCI can be, for example, wideband channel quality indicator (CQI), wideband precoding matrix indicator (PMI), rank indicator (RI), HARQ, layer indicator (LI), CSI-RS resource indicator (CRI), etc. The low priority UCI can be, for example, subband CQI, subband PMI, etc. For example, the first CW can be a CW with higher MCS, smaller TA value, NDI toggling, and / or lower CW identification.

[0097] If multiple CWs are used for UCI transmission, the WTRU can split (e.g., equally split) and transmit UCI bits on multiple CWs. In an example, when UCI is transmitted on multiple CWs, the WTRU can independently encode each part of the UCI in each CW.

[0098] The WTRU can determine the number of CWs for UCI transmission based on an indication (e.g., UL-SCH) in the DCI. For example, if the WTRU is indicated to transmit only UCI on PUSCH, the WTRU can determine a single CW transmission regardless of the rank. For example, if the WTRU is not indicated to transmit only UCI on PUSCH, the WTRU can determine the number of CWs based on the rank indicated by the gNB for PUSCH transmission.

[0099] A WTRU can be configured for UCI multiplexing on two CW transmissions. In an example, a WTRU can be configured to determine a CW and / or resource usage for UCI multiplexing. In an example, a WTRU can determine to use one or more of CW1 and CW2 for transmission of UCI based on a parameter. In an example, a WTRU can receive a configured parameter including a threshold. For example, a WTRU can receive a configuration of a threshold to determine UCI splitting. In an example, a WTRU can receive an UL grant scheduling PUSCH transmission using two CWs (e.g., CW1 and CW2). In an example, a WTRU can determine to use one or more of CW1 and CW2 for transmission of UCI based on a size of UCI. A WTRU can determine to use one or more of CW1 and CW2 for transmission of UCI based on a UCI size threshold. For example, if the UCI size is greater than the UCI size threshold, a WTRU can split the UCI into multiple parts (e.g., two parts), and transmit a first part using CW1 and a second part using CW2. In an example, if the UCI size is less than the threshold, a WTRU can transmit the UCI using one of CW1 or CW2.

[0100] If UCI is transmitted using one CW based on a size of UCI, a WTRU can use a CW with a higher or lower MCS for transmission of UCI based on a priority of UCI. The MCS of a CW can be indicated by a scheduling grant (e.g., a scheduling DCI). In an example, a WTRU can use the determined one or more CWs for transmission of UCI. In an example, a WTRU can optionally use one or more of CW1 and CW2 for transmission of UCI based on a size of UCI and whether UL-SCH data is also to be transmitted. For example, a WTRU can be configured to use different thresholds (e.g., separately configured, higher or lower thresholds) to determine whether to split UCI between 2 CWs when UL-SCH data is to be transmitted.

[0101] A WTRU can be configured to multiplex UCI information, such as HARQ, ACK / NACK, and / or CSI, on PUSCH. For example, if a higher layer parameter betaOffsets = dynamic, a 2-bit length beta_offset indicator in a scheduling DCI can be used to indicate an amount of PUSCH resources that can be used for UCI multiplexing on PUSCH, as illustrated in Figure 2

[0102] Figure 2 Table 200 is an example mapping of four beta_offset indicator values to offset indices. A WTRU can determine a CW for transmission and / or resource usage for multiplexing.

[0103] ​A WTRU can determine whether one or more (e.g., two) CWs are used for UCI multiplexing. For example, if the RRC configuration (e.g., uci-OnPUSCH-ListDCI-r18) includes two sets of betaOffset indicators 202, and / or if the RRC configuration (e.g., uci-OnPUSCH) includes an index similar to betaOffsets = dynamic2, the WTRU can use two CWs for UCI multiplexing. In an example, the WTRU can use a single CW for UCI multiplexing.

[0104] If a single CW is used, the WTRU can determine which CW is used for UCI multiplexing. The WTRU can determine the CW to be used for UCI multiplexing based on one or more of the following: a CW associated with a set of antennas; a CW associated with toggling NDI; a CW associated with a particular TRP (e.g., primary / secondary TRP); and / or a CW associated with a first / second SRI.

[0105] If two CWs are used for UCI multiplexing, the WTRU can determine CSI mapping. The WTRU can map CSI to a CW based on HARQ, ACK / NACK, and / or CSI part I. In an example, the WTRU can map CSI to a CW with a higher MCS, and / or a CW associated with a set of antennas.

[0106] In an example, the WTRU can determine betaOffset for UCI multiplexing. For example, if a single CW is used, the WTRU can determine resource usage for UCI multiplexing according to the indicated betaOffset. In another example, if two CWs are targeted for UCI multiplexing, the WTRU can determine betaOffset. For example, when the RRC configuration includes two betaOffset tables similar to Table 200. As Figure 2 illustrated in FIG. 2, a beta_offset indicator 202 in a DCI can point to a pair of betaOffset values 204 from respective configuration tables. In an example, if the RRC configuration includes a single betaOffset table, but the RRC configuration (e.g., uci-OnPUSCH) includes an index similar to betaOffsets = dynamic2, the WTRU can be configured to apply the same beta_offset value on both CWs.

[0107] A WTRU can be configured to transmit one or more CWs in uplink using one or more layers. In an example, a WTRU can transmit two CWs using two layers. In an example, a WTRU can transmit one CW on the first four layers and a second CW on the remaining layers. In some examples, CW can be used interchangeably with UCI. Further, in some examples, CSI and UCI can be used interchangeably with HARQ-ACK / NACK, CSI part 1, and CSI part 2. Further, in some examples, resource can be used interchangeably with time / frequency domain resource. There can be one or more implementations for resource indication requirements for multiplexing UCI (e.g., HARQ-ACK / NACK, CSI part 1, and / or CSI part 2) on one or more CWs.

[0108] The WTRU can be configured for UCI multiplexing with DCI indication field present on one or more CWs. For example, uplink transmission can be scheduled via a DCI format. The uplink transmission can be, for example, but not limited to, PUSCH transmission using one or more CWs. The DCI format can have an indication field of resources needed for multiplexing UCI on one or more CWs.

[0109] A WTRU can be configured for UCI multiplexing on one CW. In an example, a DCI scheduling PUSCH can contain an indication field of resources needed for multiplexing UCI on one CW. The indication field can contain additional information to indicate the index of the CW for multiplexing UCI. For the case of including two CWs, the DCI indication field can contain an additional 1-bit information for indicating the CW index for UCI multiplexing.

[0110] A DCI can contain separate indication fields for indicating the CW index for UCI multiplexing. For the case of including two CWs, a DCI format scheduling PUSCH can contain separate indication fields for indicating the CW index for UCI multiplexing.

[0111] The DCI scheduling the PUSCH can not contain a separate indication field for indicating the index of the CW for UCI multiplexing. The DCI indication field for the required resources can also not have additional information for indicating the index of the CW for UCI multiplexing. In an example, the WTRU can multiplex UCI on the CWs transmitted on the first N layers. In an example, the WTRU can determine the index of the CW for multiplexing UCI based on a particular MCS. For example, the WTRU can multiplex UCI on the CW with the highest MCS. In some cases, the WTRU can determine the CW index associated with the toggled NDI as the target CW for multiplexing UCI. If more than one CW is toggled with the NDI, the WTRU can determine the first CW toggled with the NDI as the CW for multiplexing UCI.

[0112] The WTRU can be configured for UCI multiplexing on more than one CW. In an example, the DCI indication field for indicating the required resources for multiplexing UCI can apply to some CWs (e.g., all CWs). In one or more other cases, the DCI can contain separate indications for each CW for multiplexing UCI. For example, each DCI indication field for each CW can include additional information on the type of UCI to be multiplexed on the CW. In an example, two-bit additional information can be included in the indication field to indicate the type of UCI to be multiplexed on the CW (e.g., HARQ-ACK / NACK, CSI part 1, and / or CSI part 2). In an example, two-bit additional indication can be included in the indication field to indicate the type of UCI (e.g., HARQ-ACK / NACK, or CSI part 1 and CSI part 2, or HARQ-ACK / NACK, CSI part 1, and CSI part 2).

[0113] The WTRU can receive an indication of a threshold (e.g., threshold UCI) from the network (e.g., via RRC signaling). The WTRU can be configured with and / or indicated the threshold. The WTRU can receive or determine a parameter including a UCI size threshold. For example, the WTRU can receive the parameter in a field of the UL grant DCI and / or determine the parameter based on the CW. In an example, the parameter can include a threshold (e.g., UCI size threshold) and the WTRU can use the parameter to determine whether one or more CWs are to be used for multiplexing UCI. To determine whether to use one or more CWs for UCI multiplexing, the WTRU can do one or more of the following: To determine whether one or more CWs are to be used for UCI multiplexing, the WTRU can determine whether one or more CWs should be used for UCI multiplexing if the UCI size satisfies a configured and / or indicated threshold (e.g., threshold UCI). For example, the WTRU can use more than one CW when the UCI payload size exceeds the configured threshold. In an example, the WTRU can use only one CW for UCI multiplexing when the UCI size falls below the threshold (e.g., UCI size threshold).

[0114] If the WTRU uses more than one CW, the WTRU can split the UCI payload into multiple parts (e.g., two parts) and map each part to a different CW according to the priority and / or time sensitivity of each part. For example, the WTRU can use a CW associated with a higher transmission quality metric (e.g., higher MCS, higher power capability, reliability, etc.) for UCI payload with higher priority (e.g., ACK / NACK, SP-CSI, Doppler domain information, time related information, etc.).

[0115] If the WTRU uses more than one CW, the WTRU can scale differently for the indicated resource usage (e.g., betaoffset) of each CW. For example, the WTRU can scale the resource usage of each CW according to the respective MCS value of the CW to prevent penalizing the CWs associated with lower MCS. Penalizing the CWs can mean allocating less resources to the CWs, which can result in worse performance. In an example, the WTRU can utilize a first and second scaling factor to scale the indicated betaoffset value of each CW for the CWs with the highest and lowest MCS, respectively. In an example, the first scaling factor can be a function of unity while the second scaling factor can be a function of MCS. In an example, at least one of the scaling factors can be configurable.

[0116] The WTRU can be configured for UCI multiplexing without the need for a DCI indication field for the required resources. In an example, the WTRU can be configured to use one or more CWs for scheduling uplink transmissions (e.g., PUSCH transmissions) via a DCI format. The DCI format can or can not have certain fields / indication fields. For example, the DCI format can not include an indicator field to indicate the resources required to multiplex UCI using one or more CWs. In another example, the DCI format can not include an indicator (e.g., indicator field) to use a CW for multiplexing UCI. For example, the DCI format can not include an indication field to multiplex UCI on a first CW or multiplex UCI on a second CW.

[0117] A WTRU can be configured for UCI multiplexing using one CW. In an example, a WTRU can receive an RRC configuration (e.g., configuration_DCI-format_UCI-resource). The configuration can include an indication of a CW index for multiplexing UCI. In an example, the configuration can include an indication of multiplexing UCI on one of the CWs. The configuration can include an indication of multiplexing UCI on a first CW or multiplexing UCI on a second CW. The configuration can include an indication of a separation of resources needed for multiplexing HARQ-ACK, CSI part 1, and / or CSI part 2. In an example, the configuration can include one or more of the following: an index of a CW for multiplexing UCI, an indication of resources needed for HARQ-ACK, and / or an indication of resources needed for CSI part 1. In an example, a WTRU can determine resources needed for CSI part 2 from the indicated resources for CSI part 1. In one or more cases, a WTRU can receive a configuration including one or more of the following: an index of a CW for multiplexing UCI, an indication of resources needed for HARQ-ACK, and / or an indication of resources needed for CSI part 2. A WTRU can determine resources needed for CSI part 1 from the indicated resources for CSI part 2.

[0118] A WTRU can determine an index of a CW for multiplexing UCI based on a layer index. In an example, a WTRU can multiplex UCI on a CW transmitted on the first N layers. In another example, a WTRU can multiplex UCI on a CW transmitted on a layer other than the first N layers. In an example, a WTRU can determine an index of a CW for multiplexing UCI based on a CW having a particular MCS. In an example, a WTRU can multiplex UCI on a CW having a highest MCS. In an example, a WTRU can multiplex UCI on a CW having a lowest MCS. In an example, a WTRU can determine a CW index associated with a toggled NDI as a target CW (e.g., a CW to be used for multiplexing UCI). If more than one CW is toggled with an NDI, a WTRU can determine one of the CWs toggled with the NDI as a CW for multiplexing UCI (e.g., a first CW toggled with the NDI, or a second CW toggled with the NDI).

[0119] A WTRU can be configured with different priorities for uplink transmissions (e.g., PUSCH transmissions). For example, a PUSCH transmission can have a priority (e.g., 0 or 1). A PUSCH transmission with a certain priority value (e.g., priority 1) can be considered a higher priority PUSCH transmission. In an example, a PUSCH transmission with a priority value of 0 can be considered a low priority PUSCH transmission relative to a PUSCH transmission with a priority value of 1. In an example, a PUSCH transmission can have a priority of 1 or 0, where a PUSCH with a priority of 0 can be considered a higher priority PUSCH transmission, and a PUSCH with a priority of 1 can be considered a low priority PUSCH transmission relative to a PUSCH transmission with a priority of 0. Each CW can also have a priority. In an example where two CWs are used, each CW can have a priority value (e.g., a value of 1 or 0). A CW with a priority of 1 can be considered a high priority transmission compared to a CW with a priority of 0. Alternatively, a CW with a priority of 0 can be considered a high priority transmission compared to a CW with a priority of 1. A WTRU can be configured to determine and assign a priority to a CW and provide a priority indication.

[0120] If the uplink transmissions have different priorities, and / or each CW on the PUSCH transmission has different priorities, one or more of the following can apply. The WTRU can receive an RRC configuration. The RRC configuration can be configured based on a DCI format scheduling the PUSCH and a priority value of the PUSCH. In an example, the WTRU can receive a configuration_PUSCH-1_DCI-format for a PUSCH with priority 1 multiplexing UCI (e.g., HARQ-ACK / NACK and / or CSI part 1 and / or CSI part 2). The RRC configuration can include an indication of a CW for multiplexing UCI. In an example, the WTRU can receive a MAC-CE indication or a DCI indication of a dynamic indication of a CW index for multiplexing UCI. In an example, the RRC configuration can be configured based on a number of bits required for HARQ-ACK / NACK, CSI part 1, and / or CSI part 2. In an example, the WTRU can be configured with one or more of the following RRC configurations: configuration_PUSCH-1_DCI-format_Confi-1, configuration_PUSCH-1_DCI-format_Confi-2, and configuration_PUSCH-1_DCI-format_Confi-3. The WTRU can be configured with configuration_PUSCH-1_DCI-format_Confi-1 if a number of resources required for HARQ-ACK / NACK, CSI part 1, and / or CSI part 2 is less than a threshold (e.g., threshold_a). The WTRU can receive a configuration including configuration_PUSCH-1_DCI-format_Confi-2 if the number of resources required for HARQ-ACK / NACK, CSI part 1, and / or CSI part 2 is greater than threshold_a and less than threshold_b. The WTRU can receive a configuration including configuration_PUSCH-1_DCI-format_Confi-3 if the number of resources required for HARQ-ACK / NACK, CSI part 1, and / or CSI part 2 is equal to or greater than threshold_b.

[0121] The WTRU can be configured for UCI multiplexing on more than one CW. The DCI format scheduling the PUSCH can or can not include an indication field of resources required for multiplexing any of the CWs for UCI. One or more of the following can apply.

[0122] The WTRU can receive RRC configuration (e.g., configuration_DCI-format_UCI-resource_CW-index). For each CW, the WTRU can receive a configuration including a type of UCI (e.g., HARQ-ACK / NACK, CSI part 1, CSI part 2) to multiplex on the CW and / or an indication of resources needed to multiplex the UCI on the CW.

[0123] In an example, the WTRU can determine an index of a CW for multiplexing a particular type of UCI (e.g., HARQ-ACK / NACK, CSI part 1, and / or CSI part 2) based on a layer index. In an example, the WTRU can multiplex HARQ-ACK / NACK, CSI part 1, and / or CSI part 2 on a CW transmitted on the first N layers. In an example, the WTRU can multiplex the remaining UCI (if any) on a CW transmitted on a layer other than the first N layers.

[0124] In an example, the WTRU can determine an index of a CW for multiplexing a particular type of UCI (e.g., HARQ-ACK / NACK, CSI part 1, and / or CSI part 2) based on a CW with a particular MCS. In an example, the WTRU can multiplex HARQ-ACK / NACK, CSI part 1, and / or CSI part 2 on a CW with the highest MCS.

[0125] In an example, the WTRU can determine a CW index associated with a toggled NDI for a handover as a target CW for multiplexing a particular UCI. If more than one CW is toggled with the NDI, the WTRU can determine a first CW toggled with the NDI as a CW for multiplexing a particular UCI (e.g., HARQ-ACK / NACK, CSI part 1, and / or CSI part 2). Alternatively, the WTRU can determine a second CW toggled with the NDI as a CW for multiplexing a particular UCI.

[0126] For PUSCH transmissions with different priorities (e.g., priority 0 or priority 1), and if each CW includes a priority value (e.g., CW1 with priority 0 and CW2 with priority 1), one or more of the following can apply for allocating resources for UCI multiplexing on PUSCH. In an example, the WTRU can receive an RRC configuration. The configuration (e.g., RRC configuration) can be based on one or more of the following: a DCI format scheduling the PUSCH, a priority value of the PUSCH, and / or a priority value of the CW. For example, for a CW with priority 0 used for multiplexing UCI for a PUSCH transmission with priority 1, the WTRU can receive configuration_PUSCH-1_DCI-format_CW-0. The RRC configuration can include a type of UCI (e.g., HARQ-ACK / NACK, CSI part 1, and / or CSI part 2) to be multiplexed on the CW. The RRC configuration can include an indication of resources to be used for multiplexing a particular type of UCI on a particular CW of the PUSCH. In one or more other cases, the WTRU can receive a dynamic indication of the type of UCI, a MAC-CE indication or a DCI indication, resources needed for multiplexing the UCI, and a CW index for multiplexing the UCI.

[0127] The RRC configuration can be based on a number of bits needed for HARQ-ACK / NACK, CSI part 1, and / or CSI part 2. In an example, the WTRU can receive one or more of the following RRC configurations: configuration_PUSCH-1_DCI-format_Confi-1_CW-1, configuration_PUSCH-1_DCI-format_Confi-2_CW-0, and / or configuration_PUSCH-0_DCI-format_Confi-3_CW-1. If the number of resources needed for HARQ-ACK / NACK, CSI part 1, and / or CSI part 2 on, for example, a PUSCH with priority 1, the WTRU can be configured with configuration_PUSCH-1_DCI-format_Confi-1_CW-1. The PUSCH can be scheduled by a DCI format (e.g., DCI format 0_0 / 0_1). The configuration can indicate multiplexing UCI on a CW with priority 1 that is less than a threshold (e.g., threshold_a).

[0128] If the number of required resources for HARQ-ACK / NACK, CSI part 1, and / or CSI part 2 is on PUSCH with priority 1, for example, the WTRU can receive a configuration including configuration_PUSCH-1_DCI-format_Confi-2_CW-0. The PUSCH transmission can be scheduled by a DCI format (e.g., DCI format 0_0 / 0_1). The configuration can indicate multiplexing UCI on a CW with priority 0 that is greater than threshold_a and less than threshold_b.

[0129] If the number of required resources for HARQ-ACK / NACK, CSI part 1, and / or CSI part 2 is on PUSCH with priority 0, for example, the WTRU can receive a configuration including configuration_PUSCH-0_DCI-format_Confi-3_CW-1. The PUSCH transmission can be scheduled by a DCI format (e.g., DCI format 0_0 / 0_1). The configuration can indicate multiplexing UCI on a CW with priority 1 that is greater than threshold_b.

[0130] In an example, a WTRU can be configured for priority indication for two CW transmissions. The WTRU can be configured to set different priorities for each CW (e.g., CW1 and CW2). In an example, the WTRU can be configured to receive a UL grant scheduling a PUSCH transmission with 2 CWs. The UL grant can include an indication including a priority indicator in the UL grant DCI, for example. In an example, the WTRU can determine whether a priority should be set for each CW based on the size of the indicator field.

[0131] Figure 3A are example procedures 300a, 300b for priority indication based on the length of the DCI field of the configuration. At 302, the WTRU can determine whether there is a configured priority field (e.g., priority indicator in the UL grant DCI). If the WTRU determines that there is no priority field, at 303, the WTRU can determine that there is no priority for URLLC. If at 302, the WTRU determines that there is a priority field, at 306, the WTRU can determine whether the priority indicator field includes more than one information element (e.g., 1-bit or 2-bit field). At 308, the WTRU can be configured to set the priority independently for each CW based on the indicator field having more than one information element.

[0132] If at 306, the WTRU determines that the priority indicator field includes only 1 information element (e.g., 1 bit), the WTRU can be configured to set the priority for one or more CWs, e.g., as shown in Figure 3B Figure 3B An example sub-procedure 300b for 1-bit field priority indication is illustrated. In an example, the WTRU can be configured to set the priority for one CW at 324 or for two CWs at 322 based on the indication field with a single information element. The WTRU can be configured to select the CW based on one or more of: association with the highest MCS at 326, association with toggled NDI at 328, association with a particular TRP (e.g., primary / secondary TRP) at 332, and / or determination by a semi-static or dynamic indication (e.g., RRC configured indication, MAC-CE, or another DCI) at 330. At 312, the WTRU can determine whether the PUSCH transmission will cause a collision. If the PUSCH transmission will not cause a collision with PUCCH, at 316, the WTRU can be configured to transmit the PUSCH according to the determined priority.

[0133] A priority indication (e.g., 0 or 1 bit) can provide ultra-reliability low latency communication (URLLC) support and can be used to indicate the priority of an uplink transmission. If in an active DL bandwidth part (BWP), the WTRU can monitor the PDCCH to detect a DCI format including a priority indicator field. The priority indicator field can include a priority index if configured. For example, DCI format 0_1 can be configured to carry a priority indication bit field to indicate the priority of the scheduled uplink transmission. In an example, for an 8TX WTRU scheduling uplink transmission with two CWs, if the priority field in the uplink scheduling DCI is configured, the WTRU can apply one or more of the following steps.

[0134] At 306, if the WTRU determines that the priority field is configured with a 2-bit length DCI field, at 308, each bit can independently set the priority of each CW. In an example, if the priority of one of the CWs is lowered in case of collision with PUCCH, it is assumed that the priority of the other CW is also lowered. At 310, either URLLC or eMBB can be selected to use each CW for transmission.

[0135] At 306, if the WTRU determines that the priority field is configured with a single-bit DCI field, at 322, the WTRU can determine the value of the field as indicating the priority of two CWs. At 336, either URLLC or eMBB can be selected to use both CWs for transmission.​

[0136] If the WTRU is configured with a single-bit DCI field, at 324, the state of the field can determine the priority of only one of the two CWs. The WTRU can determine the CW to use (e.g., target CW) based on one or more of the following: the CW with the highest MCS at 326; the CW with the toggled NDI at 328; the CW that is RRC configured or dynamically indicated by MAC-CE or another DCI at 330; and / or the CW associated with a particular TRP (e.g., primary / secondary TRP) at 332. In an example, when the priority of one of the CWs is lowered in case of PUCCH collision, it is assumed that the priority of the other CW is also lowered. At 338, one of URLLC or eMBB can be selected for transmission by the target CW.

[0137] In an example, the WTRU can be configured to set different priorities for each CW. For uplink transmission, the WTRU can support different traffic types, such as URLLC, enhanced mobile broadband (eMBB), and the like. While the transmission of eMBB traffic can utilize time and frequency resources, URLLC transmission can be sporadic and can utilize fewer resources to complete the transmission. If the WTRU is scheduled for transmission using two CWs and receives a priority index, the WTRU can not need to allocate both CWs for transmission of the URLLC payload.

[0138] In an example, the WTRU can be semi-statically configured to include a field of priority indication in the scheduling DCI. For an 8TX WTRU scheduled for uplink transmission with more than one CW, if the priority indication field is configured in the uplink scheduling DCI, the WTRU can apply one or more of the following. In an example, the WTRU can be configured with a DCI field of more than one bit length, where each bit can independently indicate the priority of each CW. For example, if the WTRU is configured with a 2-bit length field in the DCI, at 308, the WTRU can determine the first and second bits to indicate the priority of the first and second CWs, respectively.

[0139] In an example, if only one of the CWs is de-prioritized in case of collision with PUCCH transmission, the transmission of both CWs can be cancelled and the WTRU can proceed with the transmission of the PUCCH at 318. At 314, the WTRU can indicate the capability of supporting simultaneous transmission of PUSCH and PUCCH. If the WTRU indicates at 314 that it supports simultaneous transmission of PUSCH and PUCCH, the WTRU can proceed to transmit both PUSCH and PUCCH at 320. In an example, if one of the CWs is de-prioritized in case of collision with PUCCH transmission, the WTRU can proceed to transmit the other CW and PUCCH at 318. In an example, the WTRU can prioritize the PUCCH transmission for power allocation for a given maximum configured transmission power.

[0140] In one or more other cases, the WTRU can be configured with a single 1-bit DCI field for priority indication and can utilize procedure 300b. The WTRU can apply one or more of the following options. For example, at 322, the WTRU can determine the 1-bit priority indication field to indicate the priority of both CWs. In an example, both scheduled CWs can be maintained and the WTRU can proceed to transmit the higher priority scheduled transmission (e.g., URLLC payload). Alternatively, at 324, the WTRU can interpret the state of the priority indication field as the state of the priority of only one of the scheduled CWs and can proceed to transmit the other scheduled CW.

[0141] In an example, the WTRU can determine the target CW to apply the received priority indicator by employing one or more of the following. At 326, the WTRU can determine to use a CW with a certain MCS. For example, the WTRU can consider the CW with the highest MCS as the target to apply the received priority indicator to ensure a better transmission channel for transmitting the URLLC payload. At 328, the WTRU can determine to use a CW associated with a toggled NDI as the target CW. For example, if the channel corresponding to the CW has a more robust channel. At 330, the WTRU can determine to use a CW to apply the received priority indicator based on a configuration. For example, the CW can be RRC configured or dynamically indicated by a MAC-CE or another received DCI. At 332, the WTRU can determine to use a CW to apply the received priority indicator as the CW associated with a certain TRP (e.g., primary / secondary TRP). The association can be implied by, for example, but not limited to, a certain configured TCI, indicated SRI, SSBRI, CORESETPoolIndex, SRS resource set index, and the like. At 334, the WTRU can determine the target CW based on an associated antenna group, panel, and the like. For example, the WTRU can identify the target CW as the CW mapped to a first antenna group for scheduling uplink transmission. The indication can be provided in the form of, for example, but not limited to, an indicated SRI, antenna group index, SRS resource set index, and the like.

[0142] At 312, the WTRU can determine whether there will be a collision between the PUSCH transmission and the PUCCH transmission. If no collision is detected, at 316, the WTRU can perform the PUSCH transmission. In an example, if only one of the CWs is de-prioritized in case of collision with the PUCCH transmission, the transmission of both CWs can be cancelled and at 318, the WTRU can proceed with the transmission of the PUCCH.

[0143] At 314, the WTRU can indicate its capability to support simultaneous transmission of PUSCH and PUCCH and if the capability is supported, the WTRU can proceed to perform the PUSCH and PUCCH at 320. In an example, if only one of the CWs is de-prioritized in case of collision with the PUCCH transmission, the WTRU can proceed with the transmission of the other CW and the PUCCH. In an example, the WTRU can prioritize the PUCCH transmission for power allocation for a given maximum configured transmission power.

[0144] WTRU behavior based on multiplexing rules of priority indicator per CW can be described herein. A collision can occur when a WTRU is scheduled in a slot for PUSCH transmission, and / or a collision can occur when a WTRU is scheduled to transmit UCI (e.g., UCI carrying control information such as CSI or HARQ). A WTRU can use PUCCH resources to transmit UCI. However, in the presence of a collision, a WTRU can multiplex PUCCH into resources for PUSCH. If a WTRU transmits PUSCH using two CWs with priority indicators, the multiplexing rules for PUCCH can not be clearly defined. Multiplexing rules can be defined for STxMP cases where a UE transmits PUSCH+PUSCH or PUSCH+PUCCH simultaneously.

[0145] In some examples, a WTRU can determine the multiplexing rules of PUCCH on PUSCH resources according to the priority indicator per CW (e.g., if the WTRU receives a priority indicator in the DCI of each CW).

[0146] A WTRU can be scheduled for PUSCH+PUSCH transmission in a slot where a first PUSCH carries a first CW and a second PUSCH carries a second CW (e.g., when in sDCI STxMP transmission mode). A WTRU can be scheduled with PUCCH transmission that occurs in the same slot. The WTRU can determine to multiplex PUCCH content onto the PUSCH CW with the highest or lowest indicated priority. Both PUSCH transmissions can be scheduled by DG (dynamic grant) or CG (configured grant).

[0147] A WTRU can be independently scheduled for PUSCH+PUSCH transmission by two different DCIs (e.g., when in mDCI STxMP). The PUSCH transmissions can or can not overlap (e.g., the PUSCH transmissions can partially overlap, fully overlap, or not overlap each other). Each PUSCH transmission can be scheduled with two CWs and / or priority indication per DCI. A WTRU can be scheduled with PUCCH that collides with PUSCH.

[0148] If the priority indicators are not the same, the WTRU can multiplex the PUCCH on the PUSCH CW with the lowest or highest priority index. The WTRU can determine the lowest or highest coresetPoolIndex and determine the CWs for each coresetPoolIndex. For example, assume CW 1 has the highest priority, the WTRU can multiplex on CW 1 and 2 with coresetPoolIndex = 0 and then on the CW with coresetPoolIndex = 1. Alternatively or additionally, the WTRU can determine the CWs with the highest or lowest priority and then determine the coresetPoolIndex. For example, assume CW 1 has the highest priority, the WTRU can multiplex on CW 1 from two coresetPoolIndex and then on CW 2 from two coresetPoolIndex.

[0149] If the priority indicators are the same, the WTRU can multiplex the PUCCH on the earliest in time starting PUSCH. Alternatively or additionally, the WTRU can multiplex on the PUSCH with the lowest or highest coresetPoolIndex.

[0150] The WTRU can be scheduled for PUSCH + PUCCH transmission, where the PUSCH carries CW one and two (e.g., using STxMP). The WTRU can receive a priority indicator for each CW. The resources allocated for the PUCCH can not be sufficient to carry all of the scheduled content bits (e.g., UCI). The WTRU can determine that a subset of the content can be dropped. For example, the PUCCH can carry UCI for a CSI report and the WTRU can determine to include a subset of the CSI report on the PUCCH. The WTRU can determine to multiplex the dropped content on one or more of the PUSCH CW indices, where, for example, the WTRU can determine the CW indices based on the highest or lowest priority index indicated in the DCI.

[0151] In some examples, a WTRU can be scheduled for PUSCH transmission with the PUSCH carrying CW one and two, each CW having an indicated priority. In such examples, the WTRU can be scheduled for PUCCH transmission in the same slot. The WTRU can determine to multiplex the PUCCH onto one or more CWs according to the priority indicator of each CW received in the DCI. For example, the WTRU can multiplex the PUCCH onto the CW with the highest or lowest priority indicator. If the two priority indicators are the same, the WTRU can multiplex the content onto both CWs. For example, the WTRU can multiplex onto the CW with the lowest or highest index (e.g., CW 1) and then onto the other CW (e.g., if needed). Alternatively or additionally, the WTRU can be configured with a split factor that the WTRU can use to determine the portion of the content to multiplex on the first and second CWs if both the first and second CWs have the same indicated priority. For example, the split factor can be a percentage, such as 50%. In such examples, the WTRU can multiplex 50% of the PUCCH on the first CW and another 50% of the PUCCH on the second CW.

Claims

1. A wireless transmission and reception unit (WTRU), comprising: The processor is configured to: Receive uplink (UL) grant, the uplink (UL) grant using a first CW (CW) and a second CW to schedule physical uplink shared channel (PUSCH) transmission, wherein the UL grant includes an uplink shared channel (UL-SCH) indicator; Determine the value of the UL-SCH indicator; Based on the UL-SCH indicator with a first value, it is determined whether to use the first CW and the second CW to send UL-SCH data; In response to determining that the UL-SCH indicator has a second value, the processor is configured to determine whether to use a first CW to transmit UL-SCH data, and based on the UL-SCH indicator having the second value and parameters, to determine whether to use a second CW to transmit UL-SCH data or uplink control information (UCI); and Based on the determination, the first CW and the second CW are used to transmit UL-SCH data or UCI.

2. The WTRU of claim 1, wherein the parameter is associated with the second CW, and wherein the parameter includes any one of the following: configuration, modulation and coding scheme (MCS), antenna group, new data indicator (NDI), hybrid automatic repeat request (HARQ) process identifier, transmit / receive port (TRP), or sounding reference signal (SRS) resource indicator (SRI) indicated in the downlink control information (DCI).

3. The WTRU of claim 2, wherein the NDI is switched or not switched, wherein the TRP is primary or secondary, and wherein the SRS indicates whether the second CW is associated with the first SRI or the second SRI.

4. The WTRU according to any one of claims 1 to 3, wherein the parameter includes the priority of the UCI.

5. The WTRU of claim 4, wherein the priority is associated with Hybrid Automatic Repeat Request (HARQ) feedback or Time-Critical Channel State Information (CSI), wherein the priority indicates transmission on the first CW or the second CW.

6. The WTRU according to any one of claims 1 to 5, wherein the parameter includes a UCI size threshold, and wherein the processor is configured to transmit UCI using a second CW if the UCI at the WTRU is greater than the UCI size threshold, and is configured to transmit UL-SCH data using a second CW if the UCI at the WTRU is less than the UCI size threshold.

7. The WTRU according to any one of claims 1 to 6, wherein the UL-SCH indicator includes fields from the UL Authorized DCI.

8. A method performed by a wireless transmission and reception unit (WTRU), comprising: Receive uplink (UL) grant, the uplink (UL) grant using a first CW (CW) and a second CW to schedule physical uplink shared channel (PUSCH) transmission, wherein the UL grant includes an uplink shared channel (UL-SCH) indicator; Determine the value of the UL-SCH indicator; The value of the UL-SCH indicator is used to determine whether to send UL-SCH data or uplink control information (UCI). If the UL-SCH indicator has a first value, the method includes determining whether to use a first CW and a second CW to send UL-SCH data. Wherein, if the UL-SCH indicator has a second value, the method includes determining to use a first CW to transmit UL-SCH data, and determining, based on parameters, to use a second CW to transmit UL-SCH data or uplink control information (UCI); and Based on the determination, the first CW and the second CW are used to transmit UL-SCH data or UCI.

9. The method of claim 8, wherein the parameter is associated with the second CW, and wherein the parameter includes any one of the following: configuration, modulation and coding scheme (MCS), antenna group, new data indicator (NDI), hybrid automatic repeat request (HARQ) process identifier, transmit / receive port (TRP), or sounding reference signal (SRS) resource indicator (SRI) indicated in the DCI.

10. The method of claim 9, wherein the NDI is switched or not switched, wherein the TRP is primary or secondary, and wherein the SRS indicates whether the second CW is associated with the first SRI or the second SRI.

11. The method according to any one of claims 8 to 10, wherein the parameter includes the priority of the UCI.

12. The method of claim 11, wherein the priority is associated with HARQ feedback or time-critical channel state information (CSI), wherein the priority indicates transmission on a first CW or a second CW.

13. The method of any one of claims 8 to 12, wherein the parameter includes a UCI size threshold, and wherein the processor is configured to transmit UCI using a second CW if the UCI at the WTRU is greater than the UCI size threshold, and is configured to transmit UL-SCH data using a second CW if the UCI at the WTRU is less than the UCI size threshold.

14. The method according to any one of claims 8 to 13, wherein the UL-SCH indicator includes fields from a UL-authorized DCI.

15. A wireless transmit / receive unit (WTRU) comprising a processor, the processor being configured to: Receive uplink (UL) grant, the uplink (UL) grant using a first CW (CW) and a second CW to schedule physical uplink shared channel (PUSCH) transmission, wherein the UL grant includes an uplink shared channel (UL-SCH) indicator; Determine the value of the UL-SCH indicator; Based on the value, it is determined whether to use the first CW and the second CW to send UL-SCH data or uplink control information (UCI). in, In response to determining that the UL-SCH indicator has a first value, the processor is configured to determine to use a first CW and a second CW to transmit UL-SCH data, and wherein, in response to determining that the UL-SCH indicator has a second value, the processor is configured to determine to use the first CW and the second CW to transmit uplink control information (UCI); and Based on the determination, the first CW and the second CW are used to transmit UL-SCH data or UCI.

16. The WTRU of claim 15, wherein the UL-SCH indicator includes fields from UL Authorized Downlink Control Information (DCI).

Images