Method and apparatus for configured grant transmission in unlicensed spectrum

Abstract

Methods, apparatus, systems, architectures, and interfaces for performing configured grant (CG) uplink (UL) transmissions are provided. The method includes receiving configuration information associated with a plurality of CG configurations for a CG UL transmission, determining to transmit the CG UL transmission in accordance with any of (1) a set of available channel bandwidths, (2) a number of code block groups (CBGs), and (3) transmission parameters associated with the CG UL transmission, selecting a first CG configuration in accordance with any of (1) the set of available channel bandwidths, (2) the number of code block groups (CBGs), and (3) the transmission parameters associated with the CG UL transmission, and transmitting any number of CBGs as the CG UL transmission using resources associated with the selected first configuration, wherein the resources of the selected first CG configuration are entirely within the set of available channel bandwidths.

Description

BACKGROUND

[0001] The present disclosure relates to the field of communications, and more particularly, to methods, devices, systems, architectures, and interfaces for communications in advanced or next generation wireless communications systems, including communications using New Radio and / or New Radio (NR) access technologies and communications systems. NR access technologies and communications systems can use unlicensed spectrum for wireless communications. BRIEF DESCRIPTION OF DRAWINGS

[0002] Furthermore, like reference numerals in the figures denote like elements, wherein:

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

[0004] FIG. 1B 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 FIG. 1A illustrated in FIG. 1;

[0005] FIG. 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 FIG. 1A illustrated in FIG. 1;

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

[0007] FIG. 2 is a diagram illustrating per-subband multi-CG configuration according to an embodiment;

[0008] FIG. 3 is a diagram illustrating CBG-based retransmission based on HARQ feedback according to an embodiment; and

[0009] FIG. 4 is a diagram illustrating CG configuration with long duration according to an embodiment.

[0010] Example networks for implementation of embodiments

[0011] FIG. 1Ais 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-filter OFDM, filter bank multicarrier (FBMC), and the like.

[0012] As shown FIG. 1A 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, but 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

[0013] The communications system 100 can also include a base station 114a and / or a base station 114b. Each of the base stations 114a and / or 114b can be any type of device configured to wirelessly interface with one or more 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 Node B, a site controller, an access point (AP), a wireless router, and the like. While each base station 114a, 114b is 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.

[0014] The base station 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 station 114a and / or the base station 114b can be configured to transmit and / or receive wireless signals on one or more carrier frequencies of the cell (not shown). These frequencies can be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. The cell can provide service to a relatively fixed geographic area that is relatively fixed or can change over time. The cell can be further divided into cell sectors. For example, the cell associated with the 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 use 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.

[0015] 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 employ any suitable radio access technology (RAT) to establish the air interface 116.

[0016] More specifically, as noted above, the communications 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 in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c can implement a radio technology such as Universal Mobile Telecommunications System (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).

[0017] 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.

[0018] 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).

[0019] 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 (e.g., 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., a eNB and a gNB).

[0020] In other embodiments, the base station 114a and the 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.

[0021] FIG. 1A The base station 114b in FIG. 1C can be a wireless router, Home Node B, Home eNode B, or access point, for example, and can utilize any suitable RAT for facilitating wireless connectivity access points employing the 802.11 designation, for example. The base station 114b and the WTRUs 102c, 102d in FIG. 1C 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. FIG. 1A

[0022] 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, a FIG. 1A ​It is to be understood that the RAN 104 / 113 and / or the CN 106 / 115 can each include other elements that are not explicitly shown, as well. For example, the RAN 104 / 113 and / or the CN 106 / 115 can each also include relay nodes, backhaul links, load balancers, serving gateways, etc. 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 be utilizing a NR radio technology, the CN 106 / 115 can also be in communication with another RAN (not shown) that can be utilizing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0023] 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

[0024] 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. FIG. 1A The WTRU 102c shown in Figure 1 A can be configured to communicate with the base station 114a using a cellular-based radio technology and with the base station 114b using an IEEE 802 radio technology.

[0025] FIG. 1B Figure 1 B shows a system diagram of an example WTRU 102. As shown in FIG. 1B 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 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.

[0026] 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 FIG. 1B The processor 118 and the transceiver 120 are depicted as separate components, however, it will be appreciated that the processor 118 and the transceiver 120 can be integrated in an electronic package or chip.

[0027] The transmit / receive element 122 can be configured to transmit signals to, and 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 another 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.

[0028] Although the transmit / receive element 122 is depicted in the FIG. 1B WTRU 102 can include any number of transmit / receive elements 122. More specifically, the WTRU 102 can employ MIMO technology. Thus, 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.

[0029] The transceiver 120 can be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 can have multi-mode capabilities. 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.

[0030] 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 information in, any 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 information in, a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0031] 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.

[0032] 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

[0033] The processor 118 can also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, etc. Modules, FM radio units, digital music players, media players, video game console modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, and activity trackers, etc. Peripheral devices 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0034] WTRU 102 may include a full-duplex wireless device, wherein the reception or transmission of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous for the wireless device. The full-duplex wireless device may include an interference management unit that reduces and / or substantially eliminates self-interference by means of hardware (e.g., choke coils) or by means of a processor (e.g., a separate processor (not shown) or by means of processor 118) for signal processing. In one embodiment, WTRU 102 may include a half-duplex wireless device that transmits or receives some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)).

[0035] FIG. 1C This is a system diagram illustrating RAN 104 and CN 106 according to one embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c using E-UTRA radio technology on air interface 116. RAN 104 can also communicate with CN 106.

[0036] 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 140a, for example, can use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

[0037] 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. FIG. 1C

[0038] FIG. 1C The CN 106 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.

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

[0040] ​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 also 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.

[0041] 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.

[0042] The CN 106 can also serve as a gateway for the WTRUs 102a, 102b, 102c 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

[0043] While not shown in FIG. 1A-1D WTRUs 102a, 102b, 102c are described as wireless terminals, it is contemplated that in certain representative embodiments such terminals can use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

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

[0045] A WLAN employing an Infrastructure Basic Services Set (BSS) model may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may access or interface with a distributed system (DS) or other types of wired / wireless networks that send traffic into and / or out of the BSS. Traffic originating outside the BSS and destined for a STA can be delivered to the STA via the AP. Traffic originating from a STA and destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via the AP, for example, where a source STA can send traffic to the AP and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic can be sent between the source and destination STAs (e.g., directly therebetween) using Direct Link Establishment (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). For example, a WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP) and can communicate directly with each other either within the IBSS or with the STAs using the IBSS (e.g., all STAs). Here, the IBSS communication mode is sometimes referred to as a "self-organizing" communication mode.

[0046] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel (e.g., the primary channel). The primary channel can have a fixed width (e.g., a 20 MHz bandwidth) or a width dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by STAs to establish connections with the AP. In some representative embodiments, carrier-sensing multiple access with collision avoidance (CSMA / CA) can be implemented (e.g., in an 802.11 system). For CSMA / CA, STAs, including the AP (e.g., each STA), can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA can back off. In a given BSS, at any given time, there is only one STA (e.g., only one station) transmitting.

[0047] High-throughput (HT) STAs can communicate using channels with a width of 40 MHz (e.g., by combining a 20 MHz main channel with adjacent or non-adjacent 20 MHz channels to form a 40 MHz channel).

[0048] Very High Throughput (VHT) STAs can support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. 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 encoding, the data can be passed through a segment parser that can split 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 data can be transmitted by the transmitting STA. At the receiver of the STA performing reception, 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).

[0049] 802.11af and 802.11ah support sub-1 GHz modes of operation. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah as compared to 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. 802.11ah can support meter type control / machine type communication (e.g., MTC devices in a macro coverage area) in accordance with representative embodiments. MTC devices can have certain capabilities, such as including restricted capabilities that support (e.g., only support) certain and / or limited bandwidths. MTC devices can include a battery, and the battery life of the battery is above a threshold (e.g., to preserve a long battery life).

[0050] For WLAN systems that can support multiple channels and channel bandwidths (e.g., 802.11η, 802.1 lac, 802.1 laf, and 802.1 lah), these systems include a channel that can be designated as the primary channel. The bandwidth of the primary channel can be 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 that is derived from all STAs operating in the BSS supporting the minimum bandwidth operating mode. In the example of 802.1 lah, even though the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes, the width of the primary channel can be 1 MHz for STAs (e.g., MTC type devices) that support (e.g., only support) 1 MHz mode. 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., because a STA (which only supports 1 MHz operating mode) is transmitting to the AP), then the entire available frequency band can be considered busy even though most of the frequency band remains space and available for use.

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

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

[0053] The RAN 113 can include gNBs 180a, 180b, 180c, although the RAN 113 can include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c can communicate with one or more of the WTRUs 102a, 102b, 102c over one or more air interfaces 1 16 using transceivers 184. Each of the gNBs 180a, 180b, 180c can include one or more transceivers 184 for communicating with the WTRUs 102a, 102b, 102c over the air interface 1 16. In one embodiment, the gNBs 180a, 180b, 180c can implement MIMO technology. For example, the gNBs 180a, 180b can utilize beamforming to transmit and / or receive signals to and / or from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, can employ a number of antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In one 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 the unlicensed spectrum, while the remaining component carriers can be on a licensed spectrum. In one 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).

[0054] The WTRUs 102a, 102b, 102c can use transmission associated with scalable numerology to communicate with gNBs 180a, 180b, 180c. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. 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 different amounts of OFDM symbols and / or lasting different absolute lengths of time).

[0055] 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., eNode-Bs 160a, 160b, 160c). In the standalone configuration, the WTRUs 102a, 102b, 102c can utilize one or more of gNBs 180a, 180b, 180c as a mobile anchor point. In the standalone configuration, the WTRUs 102a, 102b, 102c can utilize signals

[0056] Each of the gNBs 180a, 180b, 180c can be associated with a certain 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, implement dual connectivity, implement interworking with 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, the gNBs 180a, 180b, 180c can communicate with one another over an Xn interface. FIG. 1D As shown, the gNBs 180a, 180b, 180c can be in communication with the AN 180a, 180b, 180c over an Xn interface.

[0057] FIG. 1DThe illustrated CN 115 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.

[0058] 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 the control node. For example, the AMF 182a, 182b can be responsible for authenticating WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, managing the WTRU 102a, 102b, 102c registration area, terminating NAS signaling, and mobility management, etc. The AMF 162 can utilize network slicing to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service or the type of access requested by the WTRUs 102a, 102b, 102c. For example, different network slices can be established for access by WTRUs 102a, 102b, 102c using ultra-reliable low-latency (URLLC) access, using enhanced massive mobile broadband (eMBB) access, and / or using machine-type communication (MTC) access, etc. The AMF 162 can provide control plane functionality for switching between the RAN 113 and other RANs (not shown) using different radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[0059] 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 routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b can perform other functions, such as managing and allocating 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.

[0060] 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 downlink packets, and providing mobility anchoring, among other examples.

[0061] 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 and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0062] In view of the FIG. 1A-1D and the corresponding description of FIG. 1A-1D one or more or all of the functions described in one or more of the appended descriptions can be performed by one or more emulation devices (not shown): 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 described herein. The emulation devices can be one or more devices configured to emulate one or more 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 functions.

[0063] The one or more emulation devices can perform one or more, or all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices can be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement tests on one or more components.

[0064] The one or more emulation devices can perform one or more, or all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices can be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement tests on one or more components. The emulation device(s) can be test equipment. The emulation devices can transmit and / or receive data directly with other devices and / or via wireless communications utilizing RF circuitry (by way of example). DETAILED DESCRIPTION

[0065] Unlicensed spectrum

[0066] Channel access (e.g., generally) in unlicensed bands (e.g., unlicensed spectrum for unlicensed operation) uses a listen-before-talk (LBT) mechanism. For example, a channel access procedure such as and / or including an LBT mechanism (e.g., LBT operation / process) can be performed on an available channel bandwidth, which can be interchangeably referred to herein as an LBT bandwidth. In some cases, LBT can be required independent of whether the channel is occupied, and in other cases, immediate transmission can be applied, e.g., after a short switching gap. In the case of a frame-based system, LBT can be characterized by any of the following: a clear channel assessment (CCA) time (e.g., ~20 μβ), a channel occupancy time (COT) (e.g., minimum of 1 ms, maximum of 10 ms), an idle period (e.g., minimum of 5% of the channel occupancy time), a fixed frame period (e.g., equal to the sum of the channel occupancy time and the idle period), a short control signaling transmission time (e.g., maximum duty cycle of 5% within a 50 ms observation period), and a CCA energy detection threshold. In the case of a load-based system (e.g., the transmit and / or receive structure can not be fixed in time and can vary according to varying load), LBT can be characterized by, e.g., a number N corresponding to the number of idle slots in an extended CCA, rather than by a fixed frame period. N can be randomly selected within a certain range. In the case of long term evolution (LTE), for unlicensed spectrum, there are two categories of CCA for each of uplink and downlink. According to the first category, a node senses the channel for a duration of N slots, where N is a random value selected from a range of values (e.g., allowed values, contention window). The contention window size and its adjustment can depend on the channel access priority.

[0067] New radio (NR) technology, as specified by 3GPP and different from LTE, supports flexible transmission durations within a slot. NR also supports "configured grant" for uplink transmissions, such that the network can semi-statically configure an uplink grant and the WTRU can use (e.g., autonomously) the uplink grant, e.g., without a layer 1 (L1) indication / activation. Furthermore, NR introduces (e.g., new) features referred to as code block group (CBG)-based transmission, e.g., to support large BW allocation for (e.g., given) transport blocks (TBs). In the case of CBG transmission, a transport block (e.g., of large size) can be divided into multiple CBGs. In this case, rather than acknowledging the entire transport block with a single acknowledgement (ACK) / negative ACK (NACK) bit, multiple hybrid automatic repeat request (HARQ) bits can be used to acknowledge each CBG. In this case, for example, a transmitter can retransmit only the CBGs that were NACKed, rather than retransmitting the entire TB.

[0068] 3GPP has initiated a work item to support NR operation in unlicensed bands (NR-U, e.g., NR in unlicensed spectrum), and it is an objective within the scope of this work item to specify NR-based operation in unlicensed spectrum. Such NR-based operation in unlicensed spectrum can include any of the following: initial access, scheduling, HARQ and mobility operations, as well as methods and / or operations to allow coexistence with LTE License Assisted Access (LAA) and other incumbent radio access technologies (RATs). Deployment scenarios can include any of the following: different standalone NR-based operations, different variants of dual connectivity operations (e.g., E-UTRA-NR Dual Connectivity (EN-DC) with at least one carrier operating according to LTE RAT and / or NR Dual Connectivity (DC) with at least two sets of one or more carriers operating according to NR RAT), and / or different variants of carrier aggregation (CA), e.g., which also include different combinations of zero or more (e.g., any number of) carriers for each of LTE RAT and NR RAT. NR-U can support any of the following: configured grant transmissions and CBG-based transmissions for configured grants, which can be referred to as CG.

[0069] CBG-based transmissions and / or retransmissions for configured uplink grants can not be supported in NR (e.g., initially). That is, in the case of NR Release 15 (Rel-15), configured grant transmissions can be targeted for ultra-reliable low latency communication (URLLC) type of services, e.g., with small amounts of data to be transmitted. In the case of NR-U spectrum, configured grants can be used to reduce latency of uplink transmissions (e.g., targeted for). In this case, a WTRU can be semi-statically configured with (e.g., configured) uplink (UL) grants, and can autonomously start transmissions when data is available, e.g., without performing LBT before transmitting a scheduling request, and receiving downlink control information to schedule an uplink grant, which is also after LBT by a gNB.

[0070] In the case of NR-U, because configured uplink grants (e.g., according to configured uplink grant configurations) can support different TB sizes, it can be inefficient to indicate the (e.g., single) TB size to be used by a WTRU in (e.g., configured) uplink grant configurations with radio resource control (RRC) configuration. Thus, there can be issues in configuring resources with large TB sizes that can not be (e.g., fully) used by a WTRU (e.g., always). Also, there can be issues in configuring resources with small TB sizes that are not suitable for CBG-based transmissions.

[0071] According to embodiments, NR-U can include (e.g., use) multiple configured grant configurations and procedures for WTRU selection (e.g., associated) resources.

[0072] Code block group activation and / or deactivation

[0073] According to embodiments, there can be a new class and / or new type of product convolutional code that can be referred to as differential triangle set (DTS)-product convolutional code (PrCC). According to embodiments, DTS-PrCC can reduce (e.g., significantly) decoding complexity and / or latency compared to other types of product convolutional codes. According to embodiments, DTS-PrCC can provide pre-served and / or improved error correction performance. Further, according to embodiments, for use cases of interest and associated constraints, DTS-PrPCC can allow for higher throughput and / or less decoding complexity.

[0074] According to embodiments, CBGs can be activated and / or deactivated for CG transmissions. According to embodiments, a WTRU can be configured to (e.g., dynamically) enable and / or disable CBG-based transmissions, e.g., for CG uplink transmissions. A WTRU can enable CBG transmissions based on any of the following: active BWP size; number(s) of CGs selected by the WTRU for transmission in a (e.g., given) slot and / or transmission opportunity; any of the following: MCS of the selected CG (e.g., number of information bits that the CG can carry), number of symbols within a slot, and number of PRBs; number of interlaces of the CG configuration and / or number associated with interlaces (e.g., their identifiers); unlicensed channel bandwidth size; any of the following: number of LBT sub-bands acquired by the WTRU and size of LBT bandwidth (e.g., available channel bandwidth) acquired by the WTRU; number of LBT sub-bands that the CG maps to; buffer size status of the WTRU; indication from a gNB (e.g., base station); channel measurements; and signal measurement information, such as received signal strength indication (RSSI) measured within a sub-band containing the CG resources.

[0075] According to embodiments, in case of active BWP size, the WTRU can be configured to use CBG-based transmission for BWP size above a threshold, e.g., 10MHz. According to embodiments, in case of number of CGs selected by the WTRU for transmission in a (e.g., given) slot and / or transmission opportunity, the WTRU can select two CGs for transmission in a given slot, and the WTRU can (e.g., then) enable CBG-based transmission and transmit two CBGs per CG. According to embodiments, in case of any of modulation and coding scheme (MCS) of the selected CG, number of symbols within a slot, and number of PRBs, the WTRU can be configured with a CG having information bits above a threshold, and the WTRU can (e.g., then) activate CBG-based transmission for that CG. According to embodiments, in case of any of number of LBT sub-bands acquired by the WTRU and size of LBT bandwidth (e.g., available channel bandwidth) acquired by the WTRU, when the WTRU acquires two sub-bands, the WTRU can (e.g., from the MAC layer) receive that a TB can be transmitted in its entirety. In this case, if the WTRU acquires only 1 sub-band to transmit part of the TB, the WTRU can transmit CBG-based transmission.

[0076] According to embodiments, in case of number of LBT sub-bands that the CG is mapped to, the CG resources can be mapped to multiple LBT sub-bands, and the WTRU can (e.g., only) acquire a subset of all the required LBT sub-bands. Further, in this case, the WTRU can use CBGs, e.g., to enable puncturing of data mapped to unacquired LBT sub-bands). According to embodiments, in case of buffer size status of the WTRU, if the buffer of the WTRU contains N bits, which is above a configured threshold, the WTRU can enable CBG-based transmission. According to embodiments, in case of indication from the gNB, the WTRU can be configured with multi-CG configuration. In this case, the gNB can activate a CG by indication (e.g., information indicating whether CBG-based transmission can be used).

[0077] According to embodiments, in case of channel measurement, e.g., if the interference level measured on the resources of the CG is not constant, i.e., if the measured interference level varies in different RBs, the WTRU can activate CBG-based transmission. In this case, the WTRU can (e.g., then) activate CBG-based transmission to receive multi-bit HARQ-ACK feedback, and can map each CBG to a different RB (e.g., RBs which are experiencing different channel variations, e.g., measured interference level).

[0078] According to embodiments, in case of RSSI measured within a subband containing the CG resource, the WTRU can be configured with multiple CG configurations within different subbands. In this case, the WTRU can select one of the CG resources and can determine whether to use CBG transmission (e.g., further) based on the RSSI of the subband. For example, if the RSSI is above a configured threshold, CBG transmission can be activated.

[0079] According to embodiments, a WTRU can be configured to use CBG-based transmission semi-statically, e.g., for a given UL CG transmission. In this case, the WTRU can be configured to use (e.g., always) CBG-based transmission for a CG with any of a large BW allocation and multiple symbols and / or slots.

[0080] Multiple configured grant configurations

[0081] According to embodiments, multiple configured grant configurations can be used for any CG and / or CBG-based transmission. According to embodiments, a WTRU can be configured with multiple CG configurations, e.g., for CBG transmission. According to embodiments, a WTRU can be semi-statically configured with any number of (e.g., a set of) CGs. Further, each CG can include any of, e.g., a modulation and coding scheme for transmission within that configured grant, any number of symbols, and any number of PRBs.

[0082] According to embodiments, a WTRU can be configured to select multiple CGs, e.g., to transmit a TB including any number (e.g., multiple) of CBGs, and each CBG can be mapped to a CG, e.g. According to embodiments, a WTRU can be configured to select multiple CGs, e.g., based on any of a TB size and / or a maximum number of configured CBGs. According to embodiments, a WTRU can select the CG resources, e.g., based on whether the CG resources are adjacent in time and / or frequency. That is, CG resources that are adjacent in time can enable the WTRU to perform a single LBT before transmitting on all of the CG resources.

[0083] According to embodiments, a WTRU can attempt LBT before a first CG resource, and in case of successful LBT, the WTRU can not perform LBT for the remaining associated CG resources. In case of failed LBT, the WTRU can be able to perform LBT before a second CG resource. According to embodiments, in case of successful LBT, the WTRU can transmit before the second resource, and the WTRU can continue transmitting in the remaining resources. According to embodiments, in case of failed LBT, e.g., failed to acquire the channel before the second resource, the WTRU can attempt to acquire the channel before a third CG resource, and so on.

[0084] According to embodiments, the mapping of CBGs can depend on the timing of the first acquired, possibly adjacent, CG resource. For example, the WTRU can (e.g., always) sequentially transmit CBGs, e.g., starting from the time of the first acquired CG resource. According to embodiments, the WTRU can drop CBGs mapped to (e.g., specific) CG resources associated with a channel that is not acquired. According to embodiments, the WTRU can use a cyclic shift to transmit CBGs. For example, in the case that the WTRU acquires the channel before the Xth CG resource, the WTRU can transmit the Xth CBG. Further, the WTRU can continue until the last CBG is transmitted, and can (e.g., then) add the first (X-1) CBGs that were dropped initially due to the channel not being acquired.

[0085] According to embodiments, the WTRU can be configured with any number (e.g., one) of CGs containing any number (e.g., multiple) of resources for CBG-based transmissions. For example, the multiple resources of a CG can be contiguous in frequency. According to embodiments, a CG can contain (e.g., include, have, etc.) two resources, e.g., such that the first resource ends at PRB n and the second resource starts at PRB n+1. According to embodiments, the multiple resources can be configured to have a frequency offset (e.g., such that they are separated) within a BWP. According to embodiments, any number (e.g., multiple) of resources of a CG can be contiguous in time domain. For example, a CG can contain two resources, such that the first resource starts at symbol 7 and the second resource starts at symbol 8. According to embodiments, any number (e.g., multiple) of resources of a CG can be non-contiguous in time domain.

[0086] According to embodiments, any of CBG and subband (e.g., subchannel) LBT can be applied for CG transmissions. According to embodiments, a WTRU can be configured with a CG that spans (e.g., is associated with, covers, includes, etc.) any number (e.g., multiple) of subbands (e.g., a subband can be 20 MHz). According to embodiments, in a case where a WTRU is configured with a CG that includes multiple resources, any number (e.g., each) of the resources can be in different (e.g., respective) subbands. According to embodiments, for example, in the previously mentioned case, the WTRU can (e.g., then) use the different (e.g., respective) resources for CBG-based transmissions. In this case, since the WTRU can perform multiple channel access procedures (i.e., multiple LBT procedures) per subband, the probability of accessing a channel on unlicensed spectrum can increase (e.g., increased LBT success). In this case, if a transmission in any number (e.g., one) of the subbands fails (e.g., the WTRU cannot access the subband), retransmission can be performed (e.g., only) for the failed CBG transmission. According to embodiments, the WTRU can be configured to use a subband on which retransmission is successful (e.g., for one or more retransmissions).

[0087] According to embodiments, a WTRU can be configured with multiple CGs, and for example, each CG can be within (associated with, included in, encompass, etc.) a different subband (e.g., equal to 20 MHz or any other suitable and / or similar frequency range used as a subband and / or any of the subbands and / or subchannels). According to embodiments, the WTRU can (e.g., then) use the different CGs for CBG-based transmissions. For example, two CBGs can be transmitted in two different CGs in different (e.g., respective) subbands. According to embodiments, for CBG retransmission, the WTRU can select (e.g., fewer or more) CGs based on feedback for transmitted CBGs (e.g., feedback associated with initially transmitted CBGs).

[0088] According to embodiments, a WTRU can adjust its interlaces, for example, according to (e.g., based on, in accordance with, etc.) the number of CG resources acquired. For example, in a case where a single CG resource is acquired, the WTRU can use multiple interlaces, for example, to achieve higher throughput. According to embodiments, and for example, in another aspect, in a case where multiple (e.g., and contiguous in frequency) CG resources are acquired (e.g., successfully), the WTRU can use fewer (e.g., a single) interlace to transmit data.

[0089] Configured grant(s) selection

[0090] According to embodiments, a WTRU can select a configured grant (CG). According to embodiments, a WTRU can be configured to select any number of CGs, for example, depending on (e.g., based on) whether CBG-based transmission is enabled. For example, a WTRU can be configured to dynamically enable and / or disable CBG-based transmission. Once CBG-based transmission is enabled, a WTRU can select a CG with (e.g., having) a number of resources equal to the number of activated CBGs. As another example, in a case where a WTRU selects multiple CGs, each CG can correspond to one (e.g., respective) CBG transmission. In this case, a WTRU can be configured to enable two CBGs. According to embodiments, a WTRU can (e.g., then) select two CGs to transmit the CBGs.

[0091] According to embodiments, a WTRU can be configured to select any number of CGs depending on (e.g., based on) a buffer status of the WTRU. According to embodiments, a WTRU can be configured with multiple CGs, and each CG can have a different TB size (TBS) and / or a number of bits (e.g., information, data, etc.) to carry. According to embodiments, a WTRU can (e.g., then) select a CG with any TBS and / or number of bits that satisfies a buffer status requirement of the WTRU. For example, a WTRU can be configured with N CGs having TBS and / or number of information bits equal to {S1, S2,..., SN}. In this case, a buffer of the WTRU can contain X information bits to be transmitted, and the WTRU can select S j = min{S i s.t. S i -X ≥ 0}.

[0092] According to embodiments, a WTRU can be configured to select a (e.g., one) CG with multiple resources or any of multiple CGs, for example, depending on (e.g., based on) any of: an LBT result; a time domain allocation of the CG; a frequency domain allocation of the CG; a logical channel priority and / or latency requirement; a logical channel group; an uplink timing alignment; a measured RSSI per subband; a channel quality / load on the resources configured for CG; a transmission rate and LCP parameters; a delay and / or time; and a HARQ-ACK status of previous transmission(s) performed using the CG.

[0093] According to embodiments, in a case where the WTRU selects any of the CGs with multiple resources or multiple CGs according to the LBT result (e.g., channel access result), the WTRU can perform multiple independent LBTs, for example, on different CG resource configuration(s), on different sub-bands, and can select the CG(s) on the sub-band where the channel access is successful. According to embodiments, in such a case, the WTRU can reselect another CG configuration, for example, if the LBT on the sub-band fails and / or the number of LBT attempts is greater than a value of a configured threshold, for example. According to embodiments, the threshold can be configured to the WTRU semi-statically, for example, using RRC signaling, higher layer, or can be fixed according to the specification.

[0094] According to embodiments, in a case where the WTRU selects any of the CGs with multiple resources or multiple CGs according to the time domain allocation of the CG, the WTRU can select multiple CGs with small duration and same transmission time, for example, so that latency can be reduced, and COT (Channel Occupancy Time) can be shared with the gNB for transmitting HARQ-ACK feedback.

[0095] According to embodiments, in a case where the WTRU selects any of the CGs with multiple resources or multiple CGs according to the logical channel priority and / or latency requirement, the WTRU can select a CG based on the priority (e.g., priority of one or more logical channels (LCHs) in the MAC PDU). In such a case, the WTRU can be configured with a mapping between the CG and the LCH priority, and the WTRU can select the appropriate CG, for example, based on the LCH priority(ies) within the MAC PDU.

[0096] According to embodiments, in a case where the WTRU selects any of the CGs with multiple resources or multiple CGs according to the uplink timing alignment, the WTRU can be configured with CGs on any of different sub-bands and different carriers, for example, experiencing different uplink timing. According to embodiments, the WTRU can select a CG on different sub-bands and / or carriers, for example, if the CG is time-aligned (e.g., determined by the WTRU). According to embodiments, the WTRU can perform LBT on the sub-bands and / or carriers where the WTRU performs uplink timing alignment.

[0097] According to embodiments, in a case where the WTRU selects any of the CGs with multiple resources or multiple CGs according to the measured RSSI per sub-band, the WTRU can be configured to measure the RSSI per sub-band. In such a case, the WTRU can select a CG configuration based on, for example, whether the measured RSSI per sub-band is less than a threshold value.

[0098] According to embodiments, in case the WTRU selects any of the CGs with multiple resources or multiple CGs according to the channel quality / load on the resources configured for the CG, the WTRU can select a CG in order to maintain certain radio channel quality conditions. In this case, the WTRU can select (e.g., only select) the CG(s) on subbands and / or carriers for which the measured RSRP and / or RSRQ metrics are above a value, e.g., a certain threshold value predetermined or configured by higher layers.

[0099] According to embodiments, in case the WTRU selects any of the CGs with multiple resources or multiple CGs according to the transmission rate and LCP parameters, the WTRU can select or prioritize the active CG(s) on which the largest amount of data can be transmitted. In this case, the WTRU can select and / or prioritize the active CG(s) on which the largest amount of data with certain priority can be transmitted. According to embodiments, such priority can be predetermined and / or preconfigured. According to embodiments, the WTRU can select or prioritize the active CG(s) on which the data with the highest priority can be transmitted.

[0100] According to embodiments, in case the WTRU selects any of the CGs with multiple resources or multiple CGs according to the delay and / or time, the WTRU can be configured to prioritize a subset of CGs, e.g., a subset with a certain periodicity, if the time elapsed since the construction of the PDU is greater than a certain threshold. According to embodiments, the WTRU can select and / or prioritize a subset of CGs that, e.g., (e.g., can, can be able to, etc.) meet the QoS latency and / or deadline configured by higher layers, for example. According to embodiments, the WTRU can select and / or prioritize a subset of CGs that can meet the deadline for reordering provided by higher layers, for example.

[0101] According to embodiments, in case the WTRU selects any of the CGs with multiple resources or multiple CGs according to the HARQ-ACK status of previous transmission(s) performed using the CG, the WTRU can be configured with multiple CGs and can select one CG for transmission. In this case, the WTRU can (e.g., then) determine that a large number (e.g., above a threshold) of transmissions were NACKed and / or no HARQ-ACK feedback was received, and the WTRU can (e.g., then) select a different CG configuration for the subsequent transmission.

[0102] FIG. 2 FIG. 2 is a diagram illustrating per-subband multi-CG configuration according to embodiments.

[0103] According to embodiments, a WTRU can be configured with multiple CGs, e.g., located (e.g., arranged in, included in, etc.) in different (e.g., respective) subbands. Further, a WTRU can be configured with multiple subbands on which channel access can be performed. According to embodiments, a WTRU can prepare multiple (e.g., potential) transmission configurations prior to transmission. According to embodiments, after performing a channel access procedure, a WTRU can select one of the (e.g., potential) transmission configurations, e.g., based on success and / or failure of the channel access procedure. For example, there can be a case where a WTRU is configured with two subbands and 3 CG configurations. In this case, a first CG configuration can occupy a first and second subband with a 3 symbol transmission duration within a slot. Further, in such a case, a second CG configuration can occupy a first subband with a 6 symbol transmission duration within the slot, and a third CG configuration can occupy a second subband with a 6 symbol transmission duration within the slot.

[0104] According to embodiments, a WTRU can determine, e.g., after performing a channel access procedure, that a first subband is accessible (e.g., LBT is successful on the subband) and a second subband is not accessible (e.g., LBT fails). In this case, the WTRU can (e.g., then) select the second CG configuration, e.g., which spans only the first subband. According to embodiments, a WTRU can determine, e.g., after performing a channel access procedure, that a first and second subband are accessible (e.g., LBT is successful in both subbands). In this case, the WTRU can (e.g., then) select the first CG configuration, e.g., which spans (e.g., over) both subbands. In this case, a transmission can occupy a smaller duration and can allow a WTRU to share a COT with a gNB, e.g., to transmit HARQ feedback for a CG transmission, or e.g., to release the medium to give other UEs more probability to access the channel. According to embodiments, the configuration of multiple CGs at a same slot (e.g., with, including, indicating, etc.) can be transmitted by a network to, e.g., any number of WTRUs. That is, such a configuration can be transmitted, e.g., to increase resource usage efficiency, as not all (e.g., only a portion) of the configurations can be used by WTRUs at one time.

[0105] FIG. 3is a diagram illustrating HARQ feedback based CBG based retransmission according to an embodiment. According to an embodiment, a WTRU can select a configured grant according to (e.g., based on) HARQ feedback (e.g., received HARQ feedback). According to an embodiment, a WTRU can be configured to select any number of CGs based on received HARQ feedback. For example, there can be a case where a WTRU is configured with multiple CGs on different sub-bands. In this case, a WTRU can first transmit the CBGs through the CGs located on different sub-bands. Further, in this case, upon receiving (e.g., for, associated with, etc.) HARQ-ACK feedback for those transmissions, a WTRU can reselect the CGs on which the transmissions were successfully received, and the WTRU can (e.g., then) map the CBG retransmissions on those CGs.

[0106] According to an embodiment, a WTRU can select any number of CGs according to (e.g., based on) channel access category. According to an embodiment, a WTRU can be configured with a multi-CG configuration. According to an embodiment, a WTRU can select any number (e.g., zero, one, etc.) of the configurations based on LBT and / or channel access category, e.g., for transmission. According to an embodiment, a WTRU can be configured to select a CG with a time domain allocation, which can occur, for example, in a case where a gNB shares its channel occupancy time with a WTRU. In this case, a WTRU can determine, e.g., based on downlink signaling, that the gNB reserved the channel and that the uplink transmission can use (e.g., is performed using) channel access category 2. In this case, a WTRU can (e.g., then) select (e.g., have) a CG transmission with a transmission time less than the maximum time allowed for channel access category 2.

[0107] FIG. 4 is a diagram illustrating CG configuration with long duration according to an embodiment.

[0108] According to an embodiment, a WTRU can select a CG configuration that has (e.g., with) a longer duration and includes (e.g., consists of) multiple resources for CBG based transmission and resources for (e.g., potential) retransmission, as shown in FIG. 4 According to an embodiment, there can be a case where a WTRU initiates a channel access procedure and shares channel occupancy time with a gNB, e.g., to send HARQ-ACK feedback for transmitted CBGs. In this case, according to an embodiment, a WTRU can select and / or use a CG configuration with a longer duration, e.g., as referred to in FIG. 3According to embodiments, in case the gNB transmits NACK for all CBGs, the WTRU can use the remaining opportunities for CBG retransmission. According to embodiments, for example in case of CBG transmission is successful at the first transmission, the gNB can assign resources for CBG retransmission to another WTRU.

[0109] According to embodiments, the WTRU can indicate, for example, to the gNB, the transmission configuration. According to embodiments, the WTRU can be configured to indicate, for example, to the gNB, the transmission parameters for any number of CG transmissions. According to embodiments, the WTRU can be configured to indicate any number of CBGs included in (e.g., as part of) the CG transmission. For example, the WTRU can indicate the number of CBGs (e.g., as UCI) in the uplink control information (UCI), for example, multiplexed with the CG physical uplink shared channel (PUSCH). According to embodiments, the WTRU can be configured to indicate the CBG index of the CBG transmission. For example, there can be a case where the WTRU transmits different CBGs in different CG transmissions. In this case, the WTRU can include the CBG index on each CG transmission (e.g., the CBG index with each CG transmission) as well as the total number of CBGs.

[0110] Configured grant UCI

[0111] According to embodiments, the uplink control information (UCI) content can be any content, for example, selected and / or prioritized by the WTRU. According to embodiments, the content included in configured grant-UCI (CG-UCI) for transmission can be selected and / or prioritized according to, for example, various methods and / or characteristics. According to embodiments, the WTRU can be configured to transmit the CG-UCI and the CG-PUSCH transmission (e.g., together with the CG-PUSCH transmission). According to embodiments, the CG-UCI can include (e.g., can include information / content indicating, can include content containing / indicating) any of the following: WTRU ID, uplink power control information, redundancy version (RV) and / or HARQ process ID for uplink transmission, modulation and coding scheme (MCS) and / or code block group (CBG) related information for uplink transport block, and / or information associated with (e.g., information about) COT shared with the gNB.

[0112] According to embodiments, the CG-UCI can be control information (e.g., can include different content than those UCI) different from other (e.g., regular) UCI (e.g., such as UCI used in NR Rel-15). According to embodiments, the CG-UCI format can include, for example, a set of content that can be associated with (e.g., corresponding to) (e.g., a, certain, several, etc.) CG-CCI format. According to embodiments, different CG-UCI formats can include (e.g., have, indicate, etc.) different content. For example, CG-UCI format 0 can include any of HARQ process ID and RV, CG-UCI format 1 can include any of HARQ process ID, RV, and COT sharing information.

[0113] According to embodiments, the content of CG-UCI (e.g., content included in CG-UCI) can be determined by the WTRU. For example, according to embodiments, the WTRU can be configured to determine the content of CG-UCI based on the size of the CG-PUSCH resource. According to embodiments, different content of CG-UCI (e.g., different set of information included in CG-UCI) can correspond to different CG-UCI formats. According to embodiments, the WTRU can determine any of CG-UCI content and format according to any of: (1) the number of symbols allocated for the CG PUSCH; (2) any of the number of interlaces or the interlace size allocated to the CG-PUSCH; (3) the number of physical resource blocks (PRBs) allocated to the CG-PUSCH; (4) the number of aggregated slots of the CG-PUSCH; (5) any of: the number of listen-before-talk (LBT) bandwidths allocated to the CG-PUSCH or whether CBG-based transmission is used; (6) the LBT (e.g., type) (e.g., channel access category) used for the access channel; (7) any of: whether UCI is configured to be transmitted with the CG-PUSCH and / or the size of the UCI; (8) the number of HARQ processes with pending HARQ feedback; and (9) the UCI type.

[0114] According to embodiments, in case the WTRU determines any of the CG-UCI content and format according to the number of symbols allocated for the CG PUSCH, the WTRU can be configured (e.g., preconfigured) with multiple CG-UCI contents. For example, the WTRU can be preconfigured with multiple CG-UCI contents, where each content corresponds to a transmission duration (e.g., different length of CG-PUSCH). According to embodiments, in case of two-symbol PUSCH duration, this can carry (e.g., only) CG-UCI with UE ID, and in case of four-symbol PUSCH, this can carry CG-UCI with any of UE ID, HARQ ID, and RV. According to embodiments, the WTRU can be configured, preconfigured, and / or semi-statically configured with a mapping between the PUSCH duration and any of the CG-UCI content and format. According to embodiments, the WTRU can be configured with any of the CG-UCI format(s) and content, and CG-PUSCH configuration (e.g., in addition to the CG-PUSCH configuration).

[0115] According to embodiments, any of the CG-UCI content and format can be determined (e.g., selected by the WTRU) according to any of the number of interlaces and / or interlace size allocated to the CG-PUSCH. According to embodiments, the WTRU can determine any of the CG-UCI content and format according to (e.g., total) number of PRBs allocated to the CG-PUSCH (e.g., for CG-PUSCH transmission). According to embodiments, the WTRU can determine any of the CG-UCI content and format according to the number of aggregated slots of the CG-PUSCH, e.g., based on the number of repetitions (e.g., the WTRU is configured for) of the CG transmission.

[0116] According to embodiments, a WTRU can determine any of CG-UCI content / format according to any of: (1) a number of LBT bandwidths (e.g., available channel bandwidths) allocated to a CG-PUSCH; and (2) whether CBG-based transmission is used. For example, a WTRU can include CBG-related information, e.g., CBG transmission indication (CBGTI) and CBG flushing indication (CBGFI), e.g., only for the case of multiple LBT bandwidths (e.g., more than two LBT bandwidths). According to embodiments, a WTRU can determine CG-UCI content and / or format according to a channel access category, e.g., according to LBT used to access a channel. According to embodiments, a WTRU can include COT sharing information, e.g., only in the case of category 4 channel access (e.g., cat4 LBT) or any other similar and / or suitable channel access category. According to embodiments, a WTRU can determine any of CG-UCI content and format according to whether UCI is configured to be transmitted with a CG-PUSCH and / or a size of UCI. For example, a WTRU can be configured to transmit HARQ-ACK feedback for downlink transmissions with a CG-PUSCH transmission. As another example, a WTRU can be configured to transmit CSI reports with a CG-PUSCH transmission.

[0117] According to embodiments, a WTRU can select CG-UCI content according to (e.g., based on) a number of UCI bits (e.g., a number of UCI bits transmitted). According to embodiments, a WTRU can determine any of CG-UCI content and format according to a number of HARQ processes with (e.g., pending) HARQ feedback. For example, a WTRU can determine CG-UCI content and / or format according to a number of ACK / NACK bits. According to embodiments, a WTRU can determine any of CG-UCI content and format according to a UCI type. According to embodiments, a WTRU can determine CG-UCI content and / or format according to whether any of a CSI report, a HARQ ACK, and / or a scheduling request (SR) is reported to a gNB. For example, a WTRU can determine any of CG-UCI content and / or format taking into account, e.g., a number of bits required to indicate a selected SR configuration.

[0118] Configured grant transmission through multiple repetitions

[0119] According to embodiments, a WTRU can (e.g., be configured to) split CG-UCI content over any number (e.g., different, multiple, some, etc.) of repetitions of a CG-PUSCH transmission. For example, according to embodiments, a WTRU can transmit different CG-UCI content for (e.g., occurring in) the same CG-PUSCH transmission in different repetitions of a CG-PUSCH transmission. According to embodiments, there can be a case of a WTRU configured with a CG-PUSCH transmission with 2 repetitions. In this case, the same transport block can be repeated in the repetition (e.g., transmission) opportunities. In this case, during the first transmission (e.g., first repetition), the WTRU can include (e.g., only include) its WTRU ID, and in the second transmission (e.g., second repetition), the WTRU can include the RV and HARQ process ID of the transport block. According to embodiments, as another example, in the first repetition, the WTRU can include the WTRU ID and COT information shared with the gNB. According to embodiments, a WTRU can be configured to determine whether to split CG-UCI content (e.g., to include in a transmission repetition) according to any of: (1) size and / or content of the CG-UCI; (2) number of (e.g., configured) repetitions associated with (e.g., of, for, etc.) the CG transmission; (3) size of the UCI and / or whether the UCI is configured to be sent with the CG-PUSCH transmission; (4) priority of the UCI to be multiplexed with the CG-PUSCH transmission; and (5) whether the same number of data bits can be maintained (e.g., for repetitions of the CG-PUSCH transmission).

[0120] According to embodiments, a WTRU can split CG-UCI according to any of the size and content of the CG-UCI. For example, in a case where more than one UCI type is reported (e.g., required), a WTRU can split the UCI over different transmissions. According to embodiments, a WTRU can split CG-UCI according to the number of configured repetitions of the CG transmission. For example, in a case where a WTRU is configured with a number of repetitions higher than a value (e.g., a configured threshold), the WTRU can split the CG-UCI into multiple messages and the WTRU can transmit the messages over different (e.g., multiple, sequential, serial, etc.) repetitions. According to embodiments, a WTRU can split CG-UCI according to the size of the UCI. According to embodiments, a WTRU can split CG-UCI according to whether the UCI is configured to be transmitted with the CG-PUSCH. For example, a WTRU can be configured to transmit HARQ-ACK feedback for a downlink transmission with a CG-PUSCH transmission, e.g., according to a particular size of the CG-PUSCH transmission. As another example, a WTRU can be configured to transmit a CSI report with a CG-PUSCH transmission, e.g., according to a (e.g., different) particular size of the CG-PUSCH transmission. According to embodiments, a WTRU can select CG-UCI content according to the number of UCI bits.

[0121] According to embodiments, a WTRU can split CG-UCI according to a priority, e.g., according to a priority of UCI to be multiplexed with the CG-PUSCH. According to embodiments, a WTRU can be configured to transmit UCI with a CG-PUSCH transmission. In this case, the WTRU can determine a priority of the UCI, e.g., based on the content of the UCI. In this case, for example, HARQ-ACK feedback can have a higher priority than a CSI report. According to embodiments, in a case where the UCI priority is higher than the CG-UCI priority, the WTRU can determine whether (e.g., whether) to split the CG-UCI content over multiple repetitions. According to embodiments, a WTRU can be configured with any of (e.g., information indicating, information associated with, etc.) a priority of different UCI and a priority of CG-UCI (e.g., CG-UCI priority). According to embodiments, a WTRU can be configured with such priority information (e.g., semi-statically) using RRC signaling and / or any other suitable type of signaling. According to embodiments, a WTRU can split CG-UCI according to whether the same number of data bits can be maintained. For example, in a case where the same number of data bits received from a higher layer can be included in a repetition, a WTRU can change the UCI content for (e.g., each) repetition.

[0122] According to embodiments, a WTRU can change a rate matching factor, which can be referred to as a beta factor for rate matching, between repetitions (e.g., from one repetition to the next repetition). According to embodiments, a WTRU can keep the same UCI bits between repetitions and can change the rate matching factor (e.g., beta factor) from one repetition to the next repetition, for example, in order to increase reliability of UCI between repetitions and / or to increase reliability of PUSCH between repetitions. According to embodiments, for example, a WTRU can use a first (e.g., more reliable) beta factor for UCI multiplexing in a first repetition and, in the next repetition, the WTRU can decrement the rate matching factor (e.g., beta factor), for example, to allow for better reliability of PUSCH bits.

[0123] While features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein can be implemented in a computer program, software, or firmware incorporated in a computer- readable medium for execution by a computer or processor. Examples of non-transitory computer-readable media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software can be used to implement a radio frequency transceiver for use in a UE, WTRU, terminal, base station, RNC, or any host computer.

[0124] Further, the above-described embodiments can be implemented in terms of processing platforms, computing systems, controllers, and other devices (including constrained servers and rendezvous points / servers that contain processors). These devices can include at least one central processing unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or computations unambiguously implies the associated physical operations or processes being performed by the CPU(s) and memory. Such acts and operations or computations can be referred to as being "executed" by the CPU(s).

[0125] Those skilled in the art will understand that actions and symbolically represented operations or instructions include the manipulation of electronic signals by the CPU. The electronic system represents data bits that may cause electronic signals to be transformed or reduced, and memory locations in the memory system that store the data bits, thereby reconfiguring or otherwise altering the data bits in CPU operations and other signal processing. The memory location holding the data bits is a physical location having specific electrical, magnetic, optical, or organic properties corresponding to or representing the data bits. It should be understood that the exemplary embodiments described herein are not limited to the platforms or CPUs described above, and other platforms and CPUs can also support the methods provided.

[0126] Data bits can also be stored on computer-readable media, including disks, optical disks, and any other volatile (e.g., random access memory (“RAM”) or non-volatile (e.g., read-only memory (“ROM”)) mass storage systems readable by the CPU. Computer-readable media can include cooperative or interconnected computer-readable media, which can exist solely on the processing system or distributed across multiple interconnected processing systems located locally or remotely to the processing system. It should be understood that these representative embodiments are not limited to the aforementioned memories, and other platforms and memories can also support the described methods.

[0127] In one illustrative embodiment, any operations, processes, etc., described herein can be implemented as computer-readable instructions stored on a computer-readable medium. These computer-readable instructions can be executed by a processor of a mobile unit, network component, and / or any other computing device.

[0128] There is virtually no difference between the hardware and software implementations of various aspects of the system. The choice between hardware and software is typically (but not always, as the choice between hardware and software can be significant in certain contexts) a design choice representing a trade-off between cost and efficiency. The processes and / or systems and / or other technologies described herein can be implemented by various carriers (e.g., hardware, software, and / or firmware), and the preferred carrier can vary depending on the context in which the processes and / or systems and / or other technologies are deployed. For example, if the implementation determines that speed and accuracy are paramount, then the implementer may tend to use a primarily hardware and / or firmware carrier. If flexibility is paramount, then the implementer may tend to use a primarily software implementation. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0129] The specific embodiments described above have illustrated various embodiments of the device and / or processing using block diagrams, flowcharts, and / or examples. Just as such block diagrams, flowcharts, and / or examples encompass one or more functions and / or operations, those skilled in the art will understand that each function and / or operation within such block diagrams, flowcharts, or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware, or virtually any combination thereof. As examples, suitable processors include general-purpose processors, special-purpose processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), field-programmable gate arrays (FPGAs), any other type of integrated circuit (IC), and / or state machines.

[0130] While features and elements in specific combinations have been described above, those skilled in the art will recognize that each feature or element can be used alone or in any combination with other features and elements. This disclosure is not intended to limit the scope to the embodiments described herein, which are intended to illustrate different aspects. Those skilled in the art will understand that numerous modifications and variations are possible without departing from the spirit and scope. Elements, actions, or instructions used in this specification should not be construed as essential to the invention unless explicitly provided otherwise. In addition to the methods and apparatuses enumerated herein, those skilled in the art will clearly understand from the above description functionally equivalent methods and apparatuses within the scope of this disclosure. Such modifications and variations should fall within the scope of the appended claims. This disclosure is limited only by the appended claims and the full scope of their equivalents. It should be understood that this disclosure is not limited to any particular method or system.

[0131] It should also be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. When referenced herein, the term "User Equipment" and its abbreviation "UE" may refer to (i) a Wireless Transmitting and / or Receiving Unit (WTRU) as described below; (ii) any of the various embodiments of the WTRU described below; (iii) a device with wireless and / or wired capabilities (e.g., connectable), particularly configured with some or all of the structures and functions of the WTRU described above; (iii) a device with wireless and / or wired capabilities configured with relatively fewer structures and functions compared to all the structures and functions of the WTRU described above; or (iv) a similar device. Details of any WTRU illustrated herein may be representative of the specific details of the WTRU.

[0132] In certain representative embodiments, several portions of the subject matter described herein can be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, some aspects of the embodiments disclosed herein, in whole or in part, can be implemented in the absence of such integrated hardware, but rather can be implemented exclusively using computer software embodied on a non-transitory, tangible, computer-readable storage medium such as, for example, memory (e.g., random access memory, flash memory, read only memory, etc.), a compact disc, a digital tape, a hard disk drive, a solid state drive, etc. In some embodiments, the subject matter described herein can be implemented using a combination of computer software and hardware. Further, some embodiments described herein can be implemented using a combination of one or more computer programs and a combination of one or more processors to execute these programs. In some embodiments, a processor can include, for example, a microprocessor, an embedded microprocessor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or any combination thereof. In some embodiments, a computer program includes a piece of software written in any suitable computer language, which can be employed to program a processor for implementation of the purposes to be served. In some embodiments, a processor or processors can be implemented as a combination of one or more of

[0133] The subject matter described herein is sometimes illustrated using different components contained within, or in connection with, different other components. It will be understood that such descriptions are merely illustrative and are not intended to limit the scope of the various aspects described herein. Certain aspects can be performed and / or implemented by one or more computers, such as a computerized device. Accordingly, some embodiments of the subject matter described herein can be embodied in computer-readable storage media (transitory or non-transitory) on which can be stored computer-executable instructions (e.g., software) that, when executed by one or more computers, carry out one or more of the methods described herein.

[0134] As used herein in reference to any multiplicative and / or singular term, one skilled in the art can convert from the plural to the singular and / or from the singular to the plural as the context and / or the application can require. For the sake of clarity, various single / plural permutations can be explicitly set forth herein.

[0135] Those skilled in the art will appreciate that, in general, the terms used herein, including in the appended claims (e.g., in the body of the appended claims), are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). Those skilled in the art will further appreciate that if a specific number of an introduced claim limitation is intended, that intent should be clearly recited in the claim, and if not, no such intent exists. For example, if only one item is intended, the term "single" or similar language can be used. As an aid to understanding, the appended claims and / or the description herein can include the use of the introductory phrases "at least one" and "one or more" to introduce a claim recitation. However, the use of such phrases is not to be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations (e.g., the use of "at least one" or "one or more" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations, even if the same claim recitation is introduced by the introductory phrases "at least one" or "one or more" and the indefinite article "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). Similarly, the use of the indefinite article "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations (e.g., the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations). With respect to the use of the definite article "the" in the claims, the use of "the" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations (e.g., the use of "the" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations). With respect to the use of the indefinite article "a" or "an" in the claims, the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations (e.g., the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations). With respect to the use of the indefinite article "a" or "an" in the claims, the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations (e.g., the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations). With respect to the use of the indefinite article "a" or "an" in the claims, the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations (e.g., the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations). With respect to the use of the indefinite article "a" or "an" in the claims, the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations (e.g., the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations). With respect to the use of the indefinite article "a" or "an" in the claims, the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations (e.g., the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations). With respect to the use of the indefinite article "a" or "an" in the claims, the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations (e.g., the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations). With respect to the use of the indefinite article "a" or "an" in the claims, the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations (e.g., the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations). With respect to the use of the indefinite article "a" or "an" in the claims, the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations (e.g., the use of "a" or "an" should not be construed as limiting the scope of any claim recitation introduced therewith to only include embodiments that contain one or more such recitations).Those skilled in the art will further appreciate that virtually any disjunctive word and / or phrase presenting two or more alternative items, whether in the description, claims, or drawings, can be understood to exist in the alternative, that is, the item can be either one item or the other item, but not both items. For example, the phrase "at least one of A and B" can encompass the alternatives that can exist in either only A or in only B, or in both A and B. Also, as used herein, the term "any of" followed by a listing of a plurality of items, and / or the term "any of the" preceding a listing of a plurality of items, as used herein, is intended to mean the "any of the" listing of items or "any of the" listing of items individually or in any combination of two or more items. Further, as used herein, the term "set" or "group" is intended to mean any number of items, including zero. Additionally, as used herein, the term "number" is intended to mean any number, including zero.

[0136] Further, if a feature or aspect of the disclosure is described according to an embodiment in the form of a Markush group of alternatives, those skilled in the art will recognize that the disclosure is also thereby described in the form of any one member or subgroup of members of the Markush group.

[0137] Those skilled in the art will appreciate that all ranges disclosed herein are inclusive of the endpoints and subranges thereof. Any ranges of values disclosed herein are intended to include all values, both whole and fractional, between the upper and lower values of the range. Any numerical values disclosed herein are intended to include all values reasonably falling within these ranges, rounded to the nearest significant figure. Any numerical range disclosed herein is intended to include any and all sub-ranges of the same numerical precision, e.g. 1 to 5 includes 1 to 3, 2 to 4, 3 to 5, etc. Any list of values disclosed herein is intended to include all possible combinations of the listed values, e.g. a list of 1 to 5 includes 1 to 3, 1 to 4, 1 to 5, 2 to 4, 2 to 5, 3 to 5, etc.

[0138] Further, unless otherwise specified, no claim element across any of the claims is to be construed as being meant only the recited exact elements. Additionally, as used herein, the term "means for" is intended to invoke the provisions of 35 U.S.C. § 112, paragraph 6. or means "means-plus-function" claim format, and any claim element using the term "means for" is intended to invoke the provisions of 35 U.S.C. § 112, paragraph 6. Further, unless otherwise specified, no claim element across any of the claims is to be construed as being meant only the recited exact elements. Additionally, as used herein, the term "means for" is intended to invoke the provisions of 35 U.S.C. § 112, paragraph 6. or means "means-plus-function" claim format, and any claim element using the term "means for" is intended to invoke the provisions of 35 U.S.C. § 112, paragraph 6. Further, unless otherwise specified, no claim element across any of the claims is to be construed as being meant only the recited exact elements. Additionally, as used herein, the term "means for" is intended to invoke the provisions of 35 U.S.C. § 112, paragraph 6. or means "means-plus-function" claim format, and any claim element using the term "means for" is intended to invoke the provisions of 35 U.S.C. § 112, paragraph 6.

[0139] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions, both simple and conditional, from a memory or like storage and execute those instructions in relation to the data also stored in memory or like storage. Software can be stored on a computer-readable medium, which can include volatile memory or non-volatile memory, removable or non-removable storage media, or any suitable combination of the foregoing. Computer-readable media can include, by way of example, RAM (Random Access Memory), flash memory, and / or any other volatile or non-volatile storage medium. Modules, a frequency modulated (FM) radio unit, a near field communication (NFC) module, a liquid crystal display (LCD) display unit, an organic light emitting diode (OLED) display unit, a digital music player, a media player, a video game console module, an Internet browser, and / or any type of wireless local area network (WLAN) or ultra-wideband (UWB) module.

[0140] While the application has been described in terms of communication systems, it is contemplated that the system can be implemented in software on a microprocessor / general purpose computer (not shown). In certain embodiments, one or more of the functions of the various components can be implemented in software that controls the general purpose computer.

[0141] Moreover, although the application has been illustrated and described with respect to specific embodiments, it is not intended that the application be limited to the details shown, since various modifications and substitutions can be made, without departing from the scope of the application as defined in the claims.

Claims

1. A method implemented by a wireless transmit / receive unit (WTRU) for performing configured licensed (CG) uplink (UL) transmission, the method comprising: Receive configuration information indicating multiple CG configurations for CG UL transmission; Based on: (1) the number of code block groups (CBGs) used for transmission, and (2) the transmission parameters of the first CG configuration, the first CG UL transmission is transmitted via a first CG UL transmission resource contained in two or more subbands of the first available subband set, the first CG UL transmission including multiple CBGs; Receive CBG-based Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback information associated with the first CG UL transmission; Based on: (1) the first CG UL transmission resource associated with the CBG-based HARQ-ACK feedback information, (2) the number of one or more CBGs used for retransmission, and (3) the transmission parameters of the second CG configuration, the second CG UL transmission resource located entirely within the two or more subbands of the first available subband set is determined; and A second CG UL transmission is transmitted via the second CG UL transmission resource, the second CG UL transmission including the one or more CBGs for retransmission.

2. The method according to claim 1, further comprising: The first or second CG UL transmission is transmitted according to any of the following: (1) the active bandwidth portion (BWP) size; (2) the number of CGs selected by the WTRU for transmission in a time slot or transmission opportunity; (3) any of the following: the modulation and coding scheme (MCS) of the selected CG, the number of symbols in a time slot, and the number of physical resource blocks (PRBs); (4) the bandwidth size of the unlicensed channel; (5) the number of any of the multichannel subbands or listen-before-speak (LBT) subbands associated with the selected CG; and (6) the buffer size status of the WTRU.

3. The method according to claim 1, further comprising: Based on information associated with two or more CG configurations of the plurality of CG configurations, the number of CBGs included in the first CGUL transmission is determined. The first CG UL transmission is transmitted via a first CG UL transmission resource included in the plurality of CG configurations.

4. The method according to claim 1, further comprising: The first CG configuration is determined based on any of the following: the time-domain allocation of the plurality of CG configurations, the frequency-domain allocation of the plurality of CG configurations, logical channel priority or delay requirements, logical channel groups, HARQ feedback, and channel access category.

5. The method of claim 1, wherein the configuration information indicates any of the following: the modulation and coding scheme (MCS), the number of symbols, and the number of PRBs associated with the transmission within the respective CG associated with the plurality of CG configurations.

6. The method according to claim 1, wherein, The configuration information indicating the plurality of CG configurations used for CG UL transmission is received from the network via RRC signaling.

7. The method of claim 1, further comprising: Indicate to the network the transmission parameters associated with either the first CG UL transmission or the second CG UL transmission.

8. The method according to claim 1, wherein, Either the first CG UL transmission or the second CG UL transmission is a CG Physical Uplink Shared Channel (CG-PUSCH) transmission that includes a set of CG Uplink Control Information (CG-UCI).

9. The method according to claim 8, wherein, The content of the set of CG-UCIs and the format of the set of CG-UCIs used for transmission are determined based on any of the following: (1) the number of symbols allocated to the CG-PUSCH transmission; (2) the number of interleavings or the interleaving size allocated to the CG-PUSCH transmission; (3) the number of physical resource blocks (PRBs) allocated to the CG-PUSCH transmission; (4) the number of aggregation slots of the CG-PUSCH transmission; (5) the amount of LBT bandwidth allocated to the CG-PUSCH transmission; (6) the type of LBT used for accessing the first available subband set; (7) any of the following: whether the UCI is configured to be transmitted with the CG-PUSCH transmission and the size of the UCI; (8) the number of HARQ processes with pending HARQ feedback; and (9) the UCI type.

10. The method according to claim 9, wherein, The format of the set used to transmit the CG-UCI corresponds to the content of the CG-UCI set.

11. A wireless transmit / receive unit (WTRU), the WTRU comprising: The processor and transceiver are configured as follows: Receive configuration information indicating multiple CG configurations for configured authorized (CG) uplink (UL) transmissions; Based on: (1) the number of code block groups (CBGs) used for transmission, and (2) the transmission parameters of the first CG configuration, the first CG UL transmission is transmitted via a first CG UL transmission resource contained in two or more subbands of the first available subband set, the first CG UL transmission including multiple CBGs; Receive CBG-based Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback information associated with the first CG UL transmission; Based on: (1) the first CG UL transmission resource associated with the CBG-based HARQ-ACK feedback information, (2) the number of one or more CBGs used for retransmission, and (3) the transmission parameters of the second CG configuration, the second CG UL transmission resource located entirely within the two or more subbands of the first available subband set is determined; and A second CG UL transmission is transmitted via the second CG UL transmission resource, the second CG UL transmission including the one or more CBGs for retransmission.

12. The WTRU of claim 11, wherein the processor and the transceiver are configured to transmit the first or second CG UL transmission according to any of the following: (1) the active bandwidth portion (BWP) size; (2) the number of CGs selected by the WTRU for transmission in a time slot or transmission opportunity; (3) any of the following: the modulation and coding scheme (MCS) of the selected CG, the number of symbols in a time slot, and the number of physical resource blocks (PRBs); (4) the bandwidth size of the unlicensed channel; (5) the number of any of the multichannel subbands or listen-before-tell (LBT) subbands associated with the selected CG; and (6) the buffer size state of the WTRU.

13. The WTRU of claim 11, wherein the processor and the transceiver are configured to: Based on information associated with two or more CG configurations of the plurality of CG configurations, the number of CBGs included in the first CGUL transmission is determined. The first CG UL transmission is transmitted via a first CG UL transmission resource included in the plurality of CG configurations.

14. The WTRU of claim 11, wherein the processor and the transceiver are further configured to determine the first CG configuration based on any of the following: time-domain allocation of the plurality of CG configurations, frequency-domain allocation of the plurality of CG configurations, logical channel priority or delay requirements, logical channel groups, HARQ feedback, and channel access category.

15. The WTRU of claim 11, wherein the configuration information indicates any of the following: the modulation and coding scheme (MCS), the number of symbols, and the number of PRBs associated with the transmission within the respective CG associated with the plurality of CG configurations.

16. The WTRU of claim 11, wherein the configuration information indicating the plurality of CG configurations for CG UL transmission is received from the network via RRC signaling.

17. The WTRU of claim 11, wherein the processor and the transceiver are configured to indicate to the network transmission parameters associated with either the first CG UL transmission or the second CG UL transmission.

18. The WTRU of claim 11, wherein either the first CG UL transmission or the second CG UL transmission is a CG Physical Uplink Shared Channel (CG-PUSCH) transmission, the CG-PUSCH transmission including a set of CG Uplink Control Information (CG-UCI).

19. The WTRU according to claim 18, wherein, The content of the set of CG-UCIs and the format of the set of CG-UCIs used for transmission are determined based on any of the following: (1) the number of symbols allocated to the CG-PUSCH transmission; (2) the number of interleavings or the interleaving size allocated to the CG-PUSCH transmission; (3) the number of physical resource blocks (PRBs) allocated to the CG-PUSCH transmission; (4) the number of aggregation slots of the CG-PUSCH transmission; (5) the number of multichannel bandwidths or talk-before-you-talk (LBT) bandwidths allocated to the CG-PUSCH transmission; (6) the type of LBT used to access the CG-PUSCH; (7) whether the UCI is configured to be transmitted with the CG-PUSCH transmission and the size of the UCI; (8) the number of HARQ processes with pending HARQ feedback; and (9) the UCI type.

20. The WTRU of claim 19, wherein, The format of the set used to transmit the CG-UCI corresponds to the content of the CG-UCI set.

Images