TW201907743A - Uplink transmission without an uplink grant - Google Patents

Abstract

Systems, methods and instrumentalities are disclosed for uplink transmission without an uplink grant. A wireless transmit/receive unit (WTRU) may receive a grant free configuration from a network node (e.g., a NodeB). The grant free configuration may be associated with grant free uplink (UL) transmission. The grant free configuration may indicate a first access resource set and a second access resource set. The WTRU may determine that data needs to be transmitted in an UL transmission. The WTRU may compare requirements associated with the data to first characteristics associated with the first access resource set and second characteristics associated with the second access resource set. The WTRU may select the first access resource set based on the comparison of the requirements to the first characteristics and the second characteristics. The WTRU may transmit the data in the uplink without receiving a grant from the network node (e.g., NodeB).

Description

No-chain license winding transmission

CROSS- REFERENCE TO RELATED APPLICATIONS This application claims priority to US Provisional Patent Application No. 62/524,820, filed on Jun.

Mobile communications are continuing to evolve. The fifth generation can be called 5G. The previous (old) generation of mobile communications may be, for example, 4th Generation (4G) Long Term Evolution (LTE). Mobile wireless communications implement a variety of radio access technologies (RATs), such as new radios (NRs). Use cases for NR may include, for example, Extreme Mobile Broadband (eMBB), Ultra High Reliability and Low Latency Communication (URLLC), and Large Scale Machine Type Communication (mMTC).

Systems, methods and tools for uplink transmission without a chaining license are disclosed. The uplink transmission can be an unlicensed 5G PHY uplink PUSCH transmission. A wireless transmit/receive unit (WTRU) may receive an unlicensed configuration from a network node (e.g., a Node B). The network node can be a Next Generation Node B (gNB) and the license-free configuration can be received via a Radio Resource Control (RRC) message. This license-free configuration can be associated with license-free uplink (UL) transport. The license-free configuration may indicate a first set of access resources and a second set of access resources. The first set of access resources may be associated with a first hybrid automatic repeat request (HARQ) process. The first set of access resources may be associated with a first access mode having a first plurality of resources in time and frequency. The second set of access resources can be associated with a second HARQ process. The second set of access resources can be associated with a second access mode having a second plurality of resources in time and frequency. The license-free configuration may indicate a third set of access resources and a fourth set of access resources. The third set of access resources can be associated with a third HARQ process. The fourth set of access resources can be associated with a fourth HARQ process.

The WTRU may determine that the data needs to be transmitted in the UL transmission. The WTRU may compare the requirements associated with the profile with a first characteristic associated with the first set of access resources and a second characteristic associated with the second set of access resources. The first characteristic associated with the first set of access resources can include a first timing and a first frequency. The second characteristic can include a second timing and a second frequency. The WTRU may select the first set of access resources based on the comparison of the requirement with the first characteristic and the second characteristic. For example, the requirement associated with the profile includes latency tolerance below a threshold. The first access resource may be selected based on the first timing being better matched to the second timing than the latency tolerance. The first access resource may be selected based on the first frequency being better aligned than the second frequency. The WTRU may select the first set of access resources based on latency priority and/or reliability. The WTRU may transmit the data in the uplink without receiving permission from the network node (e.g., Node B). The WTRU may use the first set of access resources to transmit the data. The WTRU may use the first set of access resources to retransmit the data. The WTRU may receive an acknowledgement (ACK) in response to the transmitted material. The WTRU may receive a control channel (e.g., a Physical Downlink Control Channel (PDCCH)) grant that allocates resources for license-based uplink transmissions from the WTRU.

A detailed description of the illustrative embodiments will now be described with reference to the various drawings. While the description provides a detailed example of possible embodiments, it is to be understood that the details are not intended to limit the scope of the application.

FIG. 1A is a diagram showing an exemplary communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 can be a multiple access system that provides content for a plurality of wireless users, such as voice, data, video, messaging, broadcast, and the like. The communication system 100 can enable multiple wireless users to access such content via sharing system resources including wireless bandwidth. For example, communication system 100 can use 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 extended OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filter bank multi-carrier (FBMC) and many more.

As shown in FIG. 1A, communication system 100 can include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104/113, CN 106/115, public switched telephone network (PSTN) 108, the Internet. Path 110 and other networks 112, however, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. For example, any of the WTRUs 102a, 102b, 102c, and 102d may be referred to as "station" and/or "STA," and the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals. And may include user equipment (UE), mobile station, fixed or mobile subscriber unit, subscription-based unit, pager, mobile phone, personal digital assistant (PDA), smart phone, laptop, small pen Electric, personal computer, wireless sensor, hotspot or Mi-Fi device, Internet of Things (IoT) device, watch or other wearable device, head mounted display (HMD), vehicle, drone, medical device and application (eg far End surgery), industrial devices and applications (such as robotics and/or other wireless devices operating in industrial and/or automated processing chain environments), consumer electronics, and devices operating on commercial and/or industrial wireless networks and many more. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as UEs.

Communication system 100 may also include base station 114a and/or base station 114b. Each of the base stations 114a, 114b may be configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks (eg, CN 106/115, Any type of device of the Internet 110, and/or other network 112). For example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNodeB, a local Node B, a local eNodeB, a gNB, an NR Node B, a website controller, an access point (AP). , as well as wireless routers and so on. While base stations 114a, 114b are each depicted as a single component, it should be understood that base stations 114a, 114b can include any number of interconnected base stations and/or network elements.

The base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC) ), relay nodes, and so on. Base station 114a and/or base station 114b may be configured to transmit and/or receive wireless signals at one or more carrier frequencies, and base station 114a and/or base station 114b may be referred to as cells (not shown). These frequencies can be in the licensed spectrum, the unlicensed spectrum, or a combination of authorized and unlicensed spectrum. Cells may provide wireless service coverage for a particular geographic area that is relatively fixed or that may change over time. Cells can be further divided into cell sectors. For example, a cell associated with base station 114a can be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, that is, one transceiver corresponds to one sector of a cell. In one embodiment, base station 114a may use multiple input multiple output (MIMO) technology and may use multiple transceivers for each sector of a cell. For example, beamforming can be used to transmit and/or receive signals in a desired spatial direction.

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d via the null plane 116, where the null plane 116 may be any suitable wireless communication link (e.g., radio frequency (RF), Microwave, centimeter wave, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). The empty intermediaries 116 can be established using any suitable radio access technology (RAT).

More specifically, as noted above, communication system 100 can be a multiple access system and can utilize one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, to name a few. For example, base station 114a and WTRUs 102a, 102b, 102c in RAN 104/113 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use wideband CDMA ( WCDMA) to establish an empty intermediate plane 115/116/117. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink (DL) Packet Access (HSDPA) and/or High Speed UL Packet Access (HSUPA).

In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may use Long Term Evolution (LTE) and/or Or an advanced LTE (LTE-A) and/or an advanced LTA Pro (LTE-A Pro) to establish an empty interworking plane 116.

In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, where the radio technology may use a new radio (NR) to establish an empty intermediation plane 116.

In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement a variety of radio access technologies. For example, base station 114a and WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together (e.g., using a dual connectivity (DC) principle). Thus, the null intermediaries used by the WTRUs 102a, 102b, 102c can be characterized by multiple types of radio access technologies and/or transmissions to/from multiple types of base stations (e.g., eNBs and gNBs).

In other embodiments, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (ie, Wireless Fidelity (WiFi)), IEEE 802.16 (ie, Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), for GSM evolution Enhanced Data Rate (EDGE) and GSM EDGE (GERAN) and more.

The base station 114b in FIG. 1A may be, for example, a wireless router, a local Node B, a local eNodeB, or an access point, and may use any suitable RAT to facilitate a wireless connection in a local area, which may be, for example, a business Locations, homes, vehicles, campuses, industrial facilities, air corridors (eg for drone use), roads, etc. In one embodiment, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In still another embodiment, the base station 114b and the WTRUs 102c, 102d may use a cellular based RAT (eg, WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or Femtocell. As shown in FIG. 1A, the base station 114b can have a direct connection to the Internet 110. Therefore, the base station 114b does not necessarily have to access the Internet 110 via the CN 106/115.

The RAN 104/113 can be in communication with the CN 106/115, which can be configured to provide voice, data, applications, and/or the Internet to one or more of the WTRUs 102a, 102b, 102c, 102d Any type of network for Voice over Voice (VoIP) services. The data can have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, and mobility requirements. The CN 106/115 can provide call control, billing services, mobile location based services, prepaid calling, internet connectivity, video distribution, etc., and/or can perform high level security functions such as user authentication. Although not shown in FIG. 1A, it should be appreciated that the RAN 104/113 and/or CN 106/115 may communicate directly or indirectly with other RANs that use the same RAT or different RATs as the RAN 104/113. For example, in addition to being connected to the RAN 104/113 using NR radio technology, the CN 106/115 can also communicate with another RAN (not shown) using GSM, UMTS, CDMA 2000, WiMAX, E-UTRA or WiFi radio technology. .

The CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or other networks 112. The PSTN 108 may include a circuit switched telephone network that provides Plain Old Telephone Service (POTS). Internet 110 may include the use of public communication protocols (such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and/or Internet Protocol (IP) in the TCP/IP Internet Protocol suite). A system of globally interconnected computer networks and devices. Network 112 may include wired and/or wireless communication networks that are owned and/or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, where the one or more RANs may use the same RAT or a different RAT as RAN 104/113.

Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (eg, the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers that communicate with different wireless networks over different wireless links Device). For example, the WTRU 102c shown in FIG. 1A can be configured to communicate with a base station 114a that uses a cellular-based radio technology, and with a base station 114b that can use an IEEE 802 radio technology.

FIG. 1B is a system diagram showing an exemplary WTRU 102. As shown in FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/trackpad 128, a non-removable memory 130, and a removable Memory 132, power source 134, global positioning system (GPS) chipset 136 and/or other peripheral devices 138, and the like. It should be appreciated that the WTRU 102 may also include any sub-combination of the aforementioned elements while remaining consistent with the embodiments.

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 associated with the DSP core, a controller, a microcontroller , Dedicated Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit (IC), and state machine. Processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables WTRU 102 to operate in a wireless environment. The processor 118 can be coupled to a transceiver 120 that can be coupled to the transmit/receive element 122. Although FIG. 1B depicts processor 118 and transceiver 120 as separate components, it should be understood that processor 118 and transceiver 120 can also be integrated into one electronic component or wafer.

The transmit/receive element 122 can be configured to transmit signals to the base station (e.g., base station 114a) or receive signals from the base station (e.g., base station 114a) via the null plane 116. For example, in one embodiment, the transmit/receive element 122 can be an antenna configured to transmit and/or receive RF signals. As an example, 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. In still another embodiment, the transmit/receive element 122 can be configured to transmit and/or receive RF and optical signals. It should be appreciated that the transmit/receive element 122 can be configured to transmit and/or receive any combination of wireless signals.

Although the transmission/reception element 122 is depicted as a single element in FIG. 1B, the WTRU 102 may include any number of transmission/reception elements 122. More specifically, the WTRU 102 may use MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) that transmit and receive radio signals via the null intermediate plane 116.

The transceiver 120 can be configured to modulate signals to be transmitted by the transmission/reception element 122 and to demodulate signals received by the transmission/reception element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, transceiver 120 may include multiple transceivers that enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

The processor 118 of the WTRU 102 may be coupled to a speaker/microphone 124, a keypad 126, and/or a display/touchpad 128 (eg, a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may Receive user input from these components. The processor 118 can also output user profiles to the speaker/microphone 124, keypad 126, and/or display/trackpad 128. In addition, processor 118 can access information from any suitable memory, such as non-removable memory 130 and/or removable memory 132, and store the data to such memory. Non-removable memory 130 may include random access memory (RAM), read only memory (ROM), hard disk, or any other type of storage device. The removable memory 132 can include a Subscriber Identity Module (SIM) card, a memory stick, and Secure Digital (SD) memory, and the like. In other embodiments, the processor 118 may access information from, and store data to, the memory of the WTRU 102, as an example, such memory may be located on a server or a home computer (not shown) ).

The processor 118 can receive power from the power source 134 and can be configured to distribute and/or control the power to other elements in the WTRU 102. Power source 134 may be any suitable device that powers WTRU 102. For example, the power source 134 may include one or more dry battery packs (eg, nickel cadmium (Ni-Cd), nickel zinc (Ni-Zn), nickel metal compound (NiMH), lithium ion (Li-ion), etc.), solar cells. , as well as fuel cells and so on.

The processor 118 can also be coupled to a GPS chipset 136 that can be configured to provide location information (e.g., longitude and latitude) related to the current location of the WTRU 102. Additionally or alternatively to the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base station 114a, 114b) via the null plane 116 and/or receive from two or more nearby base stations. Signal timing to determine its position. It should be appreciated that the WTRU 102 may obtain location information using any suitable positioning method while remaining consistent with the embodiments.

The processor 118 can also be coupled to other peripheral devices 138, which can include one or more software and/or hardware modules that provide additional features, functionality, and/or wired or wireless connections. For example, peripheral device 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photo and/or video), a universal serial bus (USB) port, a vibrating device, a television transceiver, a hands-free headset, Bluetooth ® modules, FM radios, digital music players, media players, video game console modules, Internet browsers, virtual reality and/or augmented reality (VR/AR) devices, and activity tracking And so on. Peripheral device 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 sensing , temperature sensor, time sensor, geolocation sensor, altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor, and/or Humidity sensor.

The WTRU 102 may include a full-duplex radio for which some or all of the signals (e.g., associated with a particular subframe for UL (e.g., for transmission) and downlink (e.g., for reception)) Reception and transmission can be parallel and/or simultaneous. The full duplex radio may include an interference management unit to reduce and/or via a hardware (eg, a choke coil) or via a processor (eg, a separate processor (not shown) or via processor 118) / or basically eliminate self-interference. In one embodiment, the WTRU 102 may include a half-duplex radio for which some or all of the signals (eg, with a particular sub-signal for UL (eg, for transmission) or downlink (eg, for reception) The transmission and reception of the box is associated.

1C is a system diagram showing RAN 104 and CN 106 in accordance with one embodiment. As described above, the RAN 104 can use E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c via the null plane 116. The RAN 104 can also communicate with the CN 106.

The RAN 104 may include eNodeBs 160a, 160b, 160c, however it should be appreciated that the RAN 104 may include any number of eNodeBs while remaining consistent with the embodiments. Each of the eNodeBs 160a, 160b, 160c may include one or more transceivers that communicate with the WTRUs 102a, 102b, 102c via the null intermediaries 116. In one embodiment, the eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, for example, eNodeB 140a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, WTRU 102a. .

Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle user scheduling in radio resource management decisions, handover decisions, UL, and/or DL and many more. As shown in FIG. 1C, the eNodeBs 160a, 160b, 160c can communicate with each other via the X2 interface.

The CN 106 shown in FIG. 1C may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. While each of the foregoing elements is described as being part of CN 106, it should be understood that any of these elements may be owned and/or operated by entities other than the CN operator.

The MME 162 may be connected to each of the eNodeBs 162a, 162b, 162c in the RAN 104 via the S1 interface and may act as a control node. For example, the MME 162 may be responsible for verifying the users of the WTRUs 102a, 102b, 102c, performing bearer activation/deactivation, and selecting a particular service gateway during the initial connection of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide control plane functionality for switching between the RAN 104 and other RANs (not shown) that use other radio technologies, such as GSM and/or WCDMA.

SGW 164 may be connected to each of eNodeBs 160a, 160b, 160c in RAN 104 via an S1 interface. The SGW 164 can generally route and forward user data packets to the WTRUs 102a, 102b, 102c/route and forward user data packets from the WTRUs 102a, 102b, 102c. The SGW 164 can perform other functions, such as anchoring the user plane during handover between eNBs, triggering paging when DL data is available to the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c, etc. .

SGW 164 may be coupled to PGW 166, which may provide WTRUs 102a, 102b, 102c with packet switched network (e.g., Internet 110) access to facilitate communication between WTRUs 102a, 102b, 102c and IP-enabled devices. Communication.

The CN 106 can facilitate communication with other networks. For example, CN 106 may provide circuit switched network (e.g., PSTN 108) access to WTRUs 102a, 102b, 102c to facilitate communication between WTRUs 102a, 102b, 102c and conventional landline communication devices. For example, CN 106 may include or be in communication with an IP gateway, such as an IP Multimedia Subsystem (IMS) server, which may act as an interface between CN 106 and PSTN 108. In addition, CN 106 may provide WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and/or wireless networks owned and/or operated by other service providers.

Although the WTRU is described as a wireless terminal in Figures 1A through 1D, it is contemplated that in certain exemplary embodiments such terminals may use a wired network with a communication network (e.g., temporary or permanent). Communication interface.

In a typical embodiment, the other network 112 can be a WLAN.

A WLAN employing an Infrastructure Basic Service Set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or interface to a distributed system (DS) or another type of wired/wireless network that carries and/or carries traffic to the BSS. Traffic originating outside the BSS and to the STA may arrive via the AP and be delivered to the STA. Traffic originating from the STA and destined for a destination outside the BSS can be sent to the AP for delivery to the respective destination. Traffic between STAs within the BSS may be sent via the AP, eg, the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. Traffic between STAs within a BSS can be considered and/or referred to as point-to-point traffic. The point-to-point traffic can be sent between the source and destination STAs (eg, directly between them) with direct link setup (DLS). In some exemplary embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode does not have an AP, and STAs (eg, all STAs) that are within the IBSS or that use the IBSS can communicate directly with each other. Here, the IBSS communication mode may sometimes be referred to as an "ad-hoc" communication mode.

When using the 802.11ac infrastructure operating mode or similar operating mode, the AP can transmit beacons on fixed channels (eg, primary channels). The main channel can have a fixed width (eg, a bandwidth of 20 MHz wide) or a dynamically set width via messaging. The primary channel may be the operational channel of the BSS and may be used by the STA to establish a connection with the AP. In some exemplary embodiments, carrier sense multiple access with collision avoidance (CSMA/CA) may be implemented (eg, in an 802.11 system). For CSMA/CA, STAs including APs (eg, each STA) can sense the primary channel. If a particular STA senses/detects and/or determines that the primary channel is busy, then that particular STA may fall back. In a given BSS, one STA (eg, only one station) can transmit at any given time.

High throughput (HT) STAs can use 40 MHz wide channels for communication (eg, by combining a 20 MHz wide main channel with a 20 MHz wide adjacent or non-adjacent channel to form a 40 MHz wide channel).

Ultra High Throughput (VHT) STAs can support channels of 20 MHz, 40 MHz, 80 MHz, and/or 160 MHz wide. A 40 MHz and/or 80 MHz channel can be formed by combining successive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels or by combining two discrete 80 MHz channels (this combination can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel encoding, the data can be passed through the segmentation parser, which splits the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be performed separately on each stream. This stream can be mapped on two 80 MHz channels and the data can be transmitted by a transmitting STA. At the receiver of a receiving STA, the above operations for the 80+80 configuration may be reversed and the combined material may be sent to the Media Access Control (MAC).

802.11af and 802.11ah support the next 1 GHz mode of operation. The channel operation bandwidth and carrier are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidth 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. In accordance with an exemplary embodiment, 802.11ah can support meter type control/machine type communication (eg, MTC devices in a macro coverage area). The MTC device may have some capabilities, including, for example, support (e.g., support only) certain and/or limited bandwidth limited capabilities. The MTC device can include a battery and the battery life of the battery is above a threshold (eg, maintaining a very long battery life).

A WLAN system that can support multiple channels and channel bandwidths (eg, 802.11n, 802.11ac, 802.11af, and 802.11ah) includes channels that can be designated as primary channels. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and/or limited by the STA from all STAs operating in the BSS that support the minimum bandwidth mode of operation. In the 802.11ah paradigm, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth modes of operation, support (eg, only support) 1 MHz mode STAs (For example, an MTC type device), the width of the main channel can be 1 MHz. Carrier sensing and/or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy (eg, because the STA (which only supports 1 MHz mode of operation) transmits to the AP), then the entire available band can be considered busy even though most of the frequency band remains idle and available for use.

In the United States, the available frequency bands available for 802.11ah are from 902 MHz to 928 MHz. In Korea, the available frequency band is from 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is from 916.5 MHz to 927.5 MHz. According to the country code, the total bandwidth available for 802.11ah is from 6 MHz to 26 MHz.

Figure 1D is a system diagram showing RAN 113 and CN 115 in accordance with one embodiment. As described above, the RAN 113 may use NR radio technology to communicate with the WTRUs 102a, 102b, 102c via the null plane 116. The RAN 113 can also communicate with the CN 115.

The RAN 113 may include gNBs 180a, 180b, 180c, but it should be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with the embodiments. Each of the gNBs 180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c via the null plane 116. In one embodiment, gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may use beamforming to transmit signals to and/or receive signals from gNBs 180a, 180b, 180c. Thus, for example, gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, WTRU 102a. In one embodiment, gNBs 180a, 180b, 180c may implement carrier aggregation techniques. For example, gNB 180a may transmit multiple component carriers to WTR 102a (not shown). A subset of these component carriers may be on the unlicensed spectrum, while the remaining component carriers may be on the licensed spectrum. In one embodiment, gNBs 180a, 180b, 180c may implement Cooperative Multipoint (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and gNBs 180b (and/or gNBs 180c).

The WTRUs 102a, 102b, 102c may use transmissions associated with the set of scalable parameters to communicate with the gNBs 180a, 180b, 180c. For example, the OFDM symbol spacing and/or the OFDM subcarrier spacing may be different for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may use different or scalable length subframes or Transmission Time Intervals (TTIs) (eg, containing different numbers of OFDM symbols and/or continuing different absolute time lengths) to interact with the gNBs 180a, 180b, 180c communicates.

The gNBs 180a, 180b, 180c can be configured to communicate with the WTRUs 102a, 102b, 102c that employ independent and/or non-independent configurations. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may use signals in the unlicensed band to communicate with the gNBs 180a, 180b, 180c. In a non-independent configuration, the WTRUs 102a, 102b, 102c may communicate/connect with the gNBs 180a, 180b, 180c while communicating/connecting with another RAN (e.g., eNodeBs 160a, 160b, 160c). For example, the WTRUs 102a, 102b, 102c may implement the DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c. In a non-independent configuration, the eNodeBs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and/or throughput to serve the WTRU 102a, 102b, 102c.

Each of gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and/or DL, support network Road cutting, implementation of dual connectivity, implementation of interworking between NR and E-UTRA, routing of user plane data to user plane functions (UPF) 184a, 184b, and routing control plane information to access and mobility management Function (AMF) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, and 180c can communicate with each other via the Xn interface.

The CN 115 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possibly a data network (DN) 185a, 185b. While each of the foregoing elements is described as being part of CN 115, it should be understood that any of these element elements can be owned and/or operated by other entities than the CN operator.

The AMFs 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may function as a control node. For example, AMFs 182a, 182b may be responsible for authenticating users of WTRUs 102a, 102b, 102c, supporting network cuts (eg, handling different PDU conversations with different needs), selecting specific SMFs 183a, 183b, managing registration areas, terminating NAS Messaging, mobility management, and more. The AMFs 182a, 1823b may use network cuts to tailor the CN support provided to the WTRUs 102a, 102b, 102c based on the type of service used by the WTRUs 102a, 102b, 102c. As an example, different network slices can be established for different use cases, such as services that rely on ultra-reliable low latency (URLLC) access, services that rely on enhanced large-scale mobile broadband (eMBB) access, and/or Or services for machine type communication (MTC) access, etc. The AMF 162 may provide for switching between the RAN 113 and other RANs (not shown) that use other radio technologies (eg, non-3GPP access technologies such as LTE, LTE-A, LTE-A Pro, and/or WiFi). Control plane function.

The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 115 via the N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via the N4 interface. The SMFs 183a, 183b can select and control the UPFs 184a, 184b, and can configure traffic routing via the UPFs 184a, 184b. The SMFs 183a, 183b can perform other functions such as managing and allocating UE IP addresses, managing PDU conversations, controlling policy enforcement and QoS, providing downlink information notifications, and the like. The PDU conversation type can be IP based, non-IP based, Ethernet based, and the like.

The UPFs 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, such that the WTRUs 102a, 102b, 102c may be provided with a packet switched network (e.g., the Internet 110). Taken to facilitate communication between the WTRUs 102a, 102b, 102c and the IP-enabled device. The UPFs 184, 184b may perform other functions, such as routing and forwarding packets, implementing user plane policies, supporting multi-homed PDU conversations, handling user plane QoS, caching downlink packets, and providing mobility anchoring and the like.

The CN 115 can facilitate communication with other networks. For example, CN 115 may include or may be in communication with an IP gateway (eg, an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 115 and PSTN 108. In addition, CN 115 may provide WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and/or wireless networks that other service providers own and/or operate. In one embodiment, the WTRUs 102a, 102b, 102c may be connected via an N3 interface interfacing with UPFs 184a, 184b and an N6 interface between UPFs 184a, 184b and DNs 185a, 185b and via UPFs 184a, 184b. Go to the local data network (DN) 185a, 185b.

In view of the corresponding description of FIGS. 1A-1D and 1A through 1D, one or more or all of the functions described herein in relation to one or more of the following may be performed by one or more emulation devices (not shown) To perform: WTRUs 102a-d, base stations 114a-b, eNodeBs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DN 185 ab and/or any other device or devices described herein. These emulation devices may be one or more devices configured to emulate one or more or all of the functions herein. For example, these emulation devices can be used to test other devices and/or analog network and/or WTRU functions.

The simulation device can be designed to implement one or more tests of other devices in a laboratory environment and/or an operator network environment. For example, the one or more emulation devices may perform one or more or all of the functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network to test other within the communication network Device. The one or more emulation devices may perform one or more or all of the functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device can be directly coupled to another device to perform the test, and/or can perform the test using over-the-air wireless communication.

One or more emulation devices may perform one or more functions including all functions while not being implemented/deployed as part of a wired and/or wireless communication network. For example, the emulation device can be used in a test lab and/or in a test scenario of a wired and/or wireless communication network that is not deployed (eg, tested) to perform testing of one or more components. The one or more simulation devices can be test devices. The emulation device can transmit and/or receive data using direct RF coupling and/or via wireless communication via an RF circuit (which, by way of example, may include one or more antennas).

5G wireless networks (eg, NR) can support a wide variety of applications and different terminal types and categories. The 5G network supports, for example, ultra-reliable low-latency communication (URLLC) and large machine-type communication (mMTC). URLLC can involve (eg, requires) very strict low latency, while mMTC can involve connections to a large number of devices. Other networks (eg, Long Term Evolution (LTE) systems) may not support low latency and large connections (eg, for uplink (UL) transmissions). The time to establish UL communication between the WTRU and the gNB in the LTE system may be very important to support the URLLC (eg, very costly). In an LTE system, significant L1 control messaging overhead for implementing large connections within mMTC in UL communications can be very costly. For example, the cost of dynamic L1 control messaging for UL may be higher for small packets when the given messaging overhead is compared to the useful payload. URLLC and mMTC may, for example, use small packets (eg, to carry key information). A UL scheduling scheme is provided herein for unlicensed transmission, or semi-persistent scheduling (SPS) transmission with low latency and/or low L1 control signaling.

Unlicensed UL transmissions can provide low latency with minimal L1 control messaging for UL transmissions in the NR. Unlicensed transmissions can be used to initiate UL transmissions, for example for URLLC. For example, once the transmission of the first few transport blocks (TBs) is performed, the transport mechanism can be switched to license-based, for example to improve reliability. The WTRU may map the received UL grant to one or more previous unlicensed UL transmissions.

The WTRU may be activated/restarted and deactivated (eg, effectively activated/restarted and deactivated with a minimum amount of L1 control messaging).

Resource allocation may be part of an unlicensed transmission scheme to provide efficient mapping between single/multiple WTRUs and single/multiple time-frequency logical/entity resources.

The UL SPS transmission feature in LTE can reduce control channel overhead, for example for VoIP/VoLTE based services. For example, UL SPS for mMTC can involve significant L1 control messaging overhead due to the very large number of devices. For one or more reasons (eg, for the following reasons), LTE UL SPS may not be applicable (eg, may not be directly applicable) to one or more scenarios (eg, general scenarios) of unlicensed transmissions in the NR URLLC.

The ultra low latency may be achieved, for example, after RRC configuration by (eg, by only) WTRU autonomous UL transmission. For enabling the transmission of URLLC traffic (which may be aperiodic and sporadic), UL SPS L1 control messaging may not be necessary.

For example, when L1 messaging is applied to deactivation (eg, when the arrival of URLLC traffic may be unpredictable), the network may not provide resources (eg, necessary resources) in time to ensure URLLC service quality.

UL SPS transmissions can be designed to, for example, support an effective license-free mechanism for UL transmissions.

An exemplary implementation is provided for performing WTRU retransmission for UL with and without permission. The WTRU may not have data to transmit in the UL (eg, the WTRU cache may be empty). The WTRU may, for example, use one or more of the following examples to indicate its buffer status to the gNB.

The WTRU may indicate (e.g., explicitly indicate) the release of the configured UL grant and/or the WTRU buffer status on the UL Control Channel (e.g., PUCCH). In an example, the indication (eg, a Schedule Release Request (SRR)) may be, for example, information (eg, 1-bit information) that may be transmitted on a short PUCCH in the UL. The short PUCCH may include a smaller number of OFDM symbols than a PUCCH (eg, a normal PUCCH). For example, a short PUCCH may include one or two OFDM symbols.

While transmitting the configured UL reference symbols (eg, DM-RS, SRS) in the time slot, the WTRU may indicate to the gNB, for example, by transmitting zeros on the configured uplink licensed data resources available for initial transmission. There is no content to be transmitted in the UL. The WTRU may repeat the transmission of zeros on the configured data resources of the uplink license available for initial transmission, for example until it reaches a certain semi-static pre-configuration parameter. The WTRU may (e.g., implicitly) release the configured uplink grant and may stop transmission (retransmission) in the UL. For example, by detecting the configured UL reference symbols available for initial transmission, and by detecting zeros on the PUSCH data portion, the gNB can determine that the WTRU's buffer (possibly) is empty.

For example, by transmitting no content (eg, an on/off scheme) on a configured uplink license that is not available for initial transmission, the WTRU may indicate to the gNB (eg, implicitly) that it has no content to transmit in the UL. In an example, the gNB may determine that the WTRU's buffer may be empty, for example, by not detecting any content on the configured uplink grant available for initial transmission.

The WTRU may receive an indication (eg, an explicit indication) from the gNB to stop transmission (retransmission) in the configured uplink grant available for initial transmission on the DL Control Channel (eg, PDCCH, PHICH). The indication may be information (eg, 1-bit information) that may be sent (eg, dynamically transmitted) to the group public PDCCH. The WTRU may distinguish the unlicensed DL control channel from other control channels, for example by using a PDCCH CRC (which may be masked by using, for example, a GF-RNTI that may be allocated for unlicensed transmission).

In an example, the WTRU may not begin to use the SPS grant/assignment, for example unless it may (eg, does) receive a start command from the eNB, which may be in Downlink Control Information (DCI) (eg, explicit) Being transmitted. For example, when the system memory is in a large number of ultra-reliable low-latency WTRUs, transmitting a start command within the DCI may substantially increase the downlink control overhead (eg, within the NR). The WTRU (e.g., each WTRU) may transmit a packet at any time within the service latency boundary. It may be unbelievable to wait for a start command (eg, by gNB) to transmit (eg, dynamically) to the WTRU.

The WTRU may be configured to transmit data in the UL without receiving a license (eg, a UL grant). The UL transmission without UL grant can be initiated by, for example, Radio Resource Control (RRC).

The WTRU may receive an unlicensed configuration associated with the unlicensed uplink transmission (e.g., via a configuration message). The WTRU may receive a start command within a configuration, such as by a higher layer communication (e.g., Radio Resource Control (RRC)) (e.g., as part of a configuration). The WTRU may receive a start command via a configuration message (eg, the configuration message includes an unlicensed configuration). The WTRU may initiate an unlicensed uplink transmission based on receipt of the initiation command. The WTRU may receive configuration information, for example, from a scheduler. In one example, the configuration message can be referred to as a chain-free licensed uplink (UTWUG)-ConfigUL. The configuration message may include, for example, one or more of the following fields: (i) UL license activation; (ii) UL license deactivation; (iii) UL license release; (iv) UTWUG-radio network temporary identifier ( RNTI); (v) UTWUG interval; (vi) time-frequency resource assignment (eg, including time slot(s)/OFDM symbols and resource blocks (RB)); (vii) modulation coding scheme (MCS) (viii) redundancy version; (ix) cyclic shift of demodulation reference symbols (DM-RS); and/or (x) transmission power control (TPC) commands.

The WTRU may be configured by, for example, UTWUG_ConfigUL. For example, when a WTRU has a packet to transmit and does not wait for dynamic messaging (eg, dynamic messaging from the gNB on the DCI), the WTRU may (eg, immediately) use the license for the UL transmission.

For example, when the WTRU receives the DCI, the WTRU may follow the instructions in the DCI (eg, instead of the RRC configuration). Dynamically provided configurations (eg, dynamically provided by DCI) may (eg, always) rewrite configuration or instructions (eg, configuration messages) provided by higher layer messaging.

Semi-continuous scheduling can be provided with reduced L1 control messaging. URLLC and mMTC can be characterized by transmissions of, for example, sporadic and unpredictable relatively small payloads. UL SPS transmissions (e.g., the transmissions may be suitably configured and modified to reduce L1 control messaging) may be provided, for example, for UL license-free transmissions for services such as URLLC and mMTC.

In an example (eg, in the example of UL SPS), scheduling decisions can be provided to the terminal on the DL control channel. The scheduling decision may, for example, be provided with an indication that the scheduling decision is applicable to every nth subframe (eg, until otherwise notified), where n may be a period and the value of n may be a positive integer. Control messaging can be used once (eg, only once) and the overhead can be reduced.

Figure 2 is an example of a cycle in which UL SPS transmission is configured using RRC. One or more (eg, other) configurations may be provided (eg, additionally or alternatively) by L1 messaging, for example.

In an example (eg, as shown in FIG. 2), a period (eg, a value of n) for UL SPS transmission may be configured (eg, configured in advance) by RRC communication. Activation/restart and/or deactivation may be accomplished, for example, using L1 control messaging (eg, by a semi-persistent C-RNTI). In an example (eg, for a URLLC that might consider latency), the scheduler can configure the SPS period (eg, 1 ms). For example, when the WTRU requests scheduling, the gNB may initiate a semi-persistent mode (eg, by L1 messaging, such as PDCCH). Other configurations (eg, modulation coding scheme (MCS) and time-frequency (TF resources) may be configured (eg, also) during startup/restart (eg, each time startup/restart is performed).

For example, after enabling a semi-persistent schedule, the WTRU may monitor the PDCCH (eg, continuous monitoring) for uplink and downlink scheduling commands. The dynamic scheduling command may (e.g., when detected) take precedence over the SPS in the subframe, which may be useful, for example, when the resources allocated by the SPS may need to be increased.

Figure 3 is an example of using RRC to configure the period and TF resources of UL SPS transmission. One or more (eg, other) configurations may be provided (eg, additionally or alternatively) by L1 messaging, for example.

In an example (eg, as shown in FIG. 3), the periodicity and TF resources of the UL SPS transmission may be configured (eg, configured in advance) by RRC communication. Start/restart and deactivation can be done, for example, using L1 control messaging (eg, by semi-persistent C-RNTI). In an example (eg, a URLLC that may be important for latency), the scheduler may configure a 1 ms period for the SPS. For example, when the WTRU requests scheduling, the gNB may initiate a semi-persistent mode (eg, by L1 messaging, such as PDCCH). Other configurations (eg, modulation coding scheme (MCS)) may be configured (eg, also) during startup/restart (eg, each time startup/restart is performed).

For example, after enabling a semi-persistent schedule, the WTRU may monitor the PDCCH (eg, continuous monitoring) for uplink and downlink scheduling commands. The dynamic scheduling command may (e.g., when detected) take precedence over the SPS in the subframe, which may be useful, for example, when the resources allocated by the SPS may need to be increased.

FIG. 4 is an example of configuring a period, a TF resource, and an MCS of a UL SPS transmission using RRC.

In an example (eg, as shown in FIG. 4), multiple (eg, all) parameters (eg, periods of UL SPS transmission, TF resources, and MCS) may be configured (eg, configured in advance) by RRC communication. For example, L1 control messaging for activating or deactivating a WTRU may not be necessary when the WTRU remains active.

For example, after enabling a semi-persistent schedule, the WTRU may continue to monitor the PDCCH for both uplink and downlink scheduling commands. The dynamic scheduling command may (e.g., when detected) take precedence over the SPS in the subframe, which may be useful, for example, when the resources allocated by the SPS may need to be increased.

Resource configuration (eg, provisioning) can be provided for license-free transmissions. In an example, a WTRU may be assigned a resource (eg, a single resource) for license-free transmission. The gNB (eg, in this case) knows what resources to search for for the WTRU. Some examples are shown in Figures 5 and 6.

Figure 5 is an example of a WTRU being assigned to a single resource. A resource (eg, a single resource) can be assigned to the WTRU.

Figure 6 shows an example of gNB resource search. One or more WTRUs may be assigned to resources. The gNB can know which resource the WTRU is assigned to.

In an example (eg, as shown in FIG. 6), the gNB may be aware that in resource 2 (eg, only in resource 2) UE1 (eg, WTRUl) and UE2 (eg, WTRU2) and in resources 4 searches (eg, only in resource 4) UE3 and UE4 (eg, WTRU3 and WTRU4).

For example, when multiple WTRUs may be assigned to a single resource, an unlicensed transmission failure may occur. Unlicensed transmission failures may occur, for example, due to collisions between simultaneous unlicensed transmissions from multiple WTRUs. This may be resolved, avoided, or minimized, for example, by assigning multiple WTRUs to multiple resources and allowing the WTRU (e.g., each WTRU) to select resources (e.g., randomly select). This can result in an increase in decoding complexity at the gNB.

Figure 7 is an example of assigning a WTRU to multiple resources. Multiple resources may be assigned to the WTRU.

Figure 8 shows an example of gNB resource search. Multiple (eg, all) WTRUs may be assigned to the same resource. For example, each of the plurality of WTRUs can be assigned to the same plurality of resources.

In an example (eg, as shown in FIG. 8), the gNB may be aware of a search (eg, all) of multiple (eg, all) resources (eg, resources 2 and 4) available for license-free access. WTRU (e.g., UE1, UE2, UE3, and UE4).

A WTRU may be assigned to multiple resources that may be accessed in a determined manner. This determination may be an access mode known to the WTRU and a network node (e.g., gNB). For example, by assigning a WTRU to multiple resources and by accessing resources in a determined manner (eg, using a known access mode) that may have been known to the WTRU and gNB, the blocking probability and decoding complexity at the gNB may be Reduced or minimized. Elements of the pattern (eg, each element) may be used, for example, during resource access. Resource access may occur, for example, during (i) consecutive initial transmissions in unlicensed transmissions from the WTRU; (ii) repetitions of transmissions from WTRUs that may be transmitting unlicensed transmissions (eg, upon receipt thereof) Before the response from gNB); and/or (iii) (eg, specific) during the HARQ process.

A WTRU may be assigned to a single set of logical resources. The set of logical resources can be mapped to a plurality of entity resources, for example, using an access mode (eg, as shown in the example in FIG. 9).

Figure 9 is an example of assigning a WTRU to a single logical resource. A logical resource can include multiple physical resources (eg, with an access mode). A WTRU may be assigned to multiple entity resources (eg, multiple physical resources of a single logical resource).

The gNB may be aware of resources that may be used by the WTRU. For example, when the gNB is aware of resources that the WTRU may (eg, is about to use), the complexity of the decoding procedure can be reduced. Figure 10 shows an example.

Figure 10 shows an example of gNB resource search. Multiple WTRUs may be assigned the same resource (eg, at one or more start/reset time slots).

In an example (eg, as shown in FIG. 10), the gNB may search for UE1 in resource 2 for time slot 1 and resource 4 for time slot n. The gNB can search for UE2 in resource 2 for slots 1 and n. The gNB can search for UE3 in resource 4 for time slot 1 and resource 2 for time slot n. The gNB can search for UE4 in resource 4 for slots 1 and n.

A WTRU may be assigned to a set of logical resources (eg, a single set of logical resources). The set of logical resources can be assigned to a single resource with a single pattern, which can be similar to a single resource assignment (eg, as described in the above examples for Figures 5 and 6). Assigning to a set of resources having multiple resources having modes that can (eg, indeed allow access to multiple resources within the time slot) may be similar to assigning multiple WTRUs to multiple resources (eg, For the above examples of Figures 7 and 8).

A framework can be provided for selection and implementation of one or more programs. The application can be determined, for example, by gNB configuration messaging.

Mode synchronization is available. The gNB and the WTRU may (e.g., must) be aware of a mode. The gNBs and/or WTRUs may be able to synchronize their location in the mode to, for example, transmit and receive signals within the same resource. In an example, the WTRU (e.g., UE1) may transmit in resource 2 for time slot 1, and the gNB may (e.g., must) monitor the WTRU in resource 2 for time slot 1.

The deterministic mode (in which the resources can be assigned) can be indicated by the gNB and signaled to the WTRU. For example, a WTRU may receive an unlicensed configuration from a network node (eg, Node B, gNB, etc.). This license-free configuration can indicate this deterministic pattern. The deterministic mode can be an access mode with multiple resources in time and frequency. A deterministic pattern can be assigned to each access resource set. For example, the first set of access resources can be associated with a first deterministic mode and the second set of access resources can be associated with a second deterministic mode. Each set of access resources can be associated with a hybrid automatic repeat request (HARQ) process.

A deterministic mode (where resources can be assigned) can be randomly selected by the WTRU and communicated to the gNB.

Figure 11 is an example of an unlicensed transaction with an initial transmission, one or more repetitions, and a license/(N)ACK.

In an example (eg, as shown in FIG. 11), the license-free transaction may include one or more of the following. The WTRU may have data to be sent in a license-free manner (eg, in the UL). For example, the WTRU may determine that data needs to be transmitted in an uplink transmission. The WTRU may send the data without receiving permission (eg, the initial transmission in resource 1 as shown in the example of FIG. 11). The WTRU may send multiple versions of the material (eg, to the gNB) without receiving permission (eg, as shown in the example of FIG. 11 , repetitions in resource 3 and resource 2). The WTRU may (e.g., may thereafter), for example, (a) receive an indication from the gNB that the material was successfully received; (b) receive an indication from the gNB that the material was not successfully received; (c) receive the data from the gNB completely unreceived An indication (eg, assuming that the SR has been sent with the material and decoded); and/or (d) has not received any communication from the gNB.

The WTRU may receive a grant, for example, from a gNB. The WTRU may receive the grant after the initial UL transmission and/or one or more repetitions (eg, retransmissions). The gNB may (for example, (a), (b), and (c)) utilize a grant (eg, explicit grant) to switch the WTRU to a schedule-based transmission. The WTRU may send (e.g., explicit) a Service Request (SR) (e.g., for (d)).

Repeat can be a retransmission. For example, the repetition can send (or resend) the same information encoded in the same or different ways. The number of repetitions may depend on, for example, WTRU capabilities, configuration, and the like. In an example, K may be the number of time resources (eg, time slots) that the gNB may delay before sending the ACK/NACK and/or PDCCH (which may indicate the resources used) to the URLLC WTRU. The value of K may depend, for example, on the latency that the WTRU can tolerate. In an example, a lower value of K can be assigned to a WTRU with lower latency tolerance. In the example of K=1, the ACK/NACK/PDCCH may be transmitted in the next time slot and (eg, only) the initial transmission mode may be valid. The WTRU may, for example, during initialization, indicate the parameter K, for example. The value of the parameter K may be implied (eg, additionally or alternatively) (eg, based on a particular WTRU class).

The system can use one or more implementations to synchronize locations in the mode. Synchronous implementations may include, for example, time synchronization, memory based synchronization, and/or reset based synchronization.

Figure 12 is an example of time-based synchronization for initial transmission. Figure 12 shows an example of initial access in an unlicensed transaction.

In the example of time synchronization (eg, as shown in Figure 12), resources available for license-free transactions may be time (eg, subframes, time slots, or micro time slots) and/or elements in the access mode. The function of the quantity. In a time slot based time synchronization system, the mode may be, for example, {3, 1, 2}, which may indicate that resource 3 can be used in time slot 1, resource 1 can be used in time slot 2, and resource 2 Can be used in time slot 3. This mode can be repeated, for example, resource 3 can be used for time slot 4 medium infinite repetition. A WTRU seeking to send an unlicensed transmission may, for example, determine the time relative to the time stamp (e.g., the index of the time slot in the subframe). The WTRU may use the time relative to the time stamp as an index in the access mode. The resources that the gNB can monitor in the time slot can be given as, for example: The gNB can monitor, for example, the same resources as determined by the time relative to the time stamp (eg, the index of the time slot in the subframe).

Figure 13 is an example of memory-based synchronization for initial transmission. Figure 13 shows an example of initial access in an unlicensed transaction.

In an example of memory-based synchronization (eg, as shown in Figure 13), the resources available for the license-free transaction may be a function of the last element of the pattern that has been used. The WTRU and gNB may, for example, use the next resource index in the pattern to identify the unlicensed resource. The WTRU and gNB can track the index, for example, so that the correct index can be accessed and monitored separately. In an example of a memory based system, the pattern may be, for example, {3, 1, 2}, which may indicate that resource 3 may be used when resources are first needed. The WTRU may transmit on resource 3 and the gNB may monitor resource 3. Resource 1 can be used the next time resources are needed. The WTRU may transmit on resource 1 and the gNB may monitor resource 1. For example, (eg, in the same SR signal that can be transmitted with the transmission) can be avoided by transmitting the current index synchronization loss (eg, where the gNB may not be able to decode the transmission). The gNB may (eg, be able to) identify the WTRU and its current index, and may reset its monitoring to the correct index for the next license-free transaction.

Figure 14 is an example of reset-based synchronization for initial transmission. Figure 14 shows an example of initial access in an unlicensed transaction.

In an example of reset-based synchronization (eg, as shown in FIG. 14), resources available at the beginning of the license-free transaction may (eg, always) be reset to an initial index in the access mode. Additional transmissions within the unlicensed transmission may use, for example, the next element in the access mode in sequence. In an example of reset based synchronization, the mode may be, for example, {3, 1, 2}. Resetting to resource 3 can occur, for example, at the beginning of the access. Subsequent transfers (one or more) within the license-free transaction can access resource 1 and then access resource 2.

The intelligent allocation of resource pools and mode assignments to the WTRU (e.g., in time synchronization, memory based synchronization, and/or reset based synchronization) may reduce the likelihood of collisions between WTRUs that may attempt to use resources.

The modes available for initial transmission may be the same or different from the patterns used for repetition.

In an example (eg, example a), a time-based program can be used for initial transmission and repetition. The particular resources that the WTRU/gNB can access may (eg, completely) depend on time.

In an example (eg, example b), a memory based program may be used for initial transmission and repetition. The initial transmission may, for example, use the next index in the access mode, while the repetition may use the same index. Information can be added and merged, for example when it may be (for example, only possible) a decoding problem. The initial transmission may (eg, alternatively) use the next index in the access mode, while the repetition may continue to increment the index.

In an example (eg, example c), the initial transfer may use a reset procedure, and the repeat may use a memory program. The initial transmission may, for example, use the first index in the access mode, while the repetition may use the same index. Information can be added and merged, for example when it may be (for example, only possible) a decoding problem. The initial transmission may (eg, alternatively) use the first index in the access mode, and the repetition may continue to increment the index.

In an example (eg, example d), transmitting and reusing a reset based program may be similar to the examples described with reference to Figures 5 and 6.

Table 1 is an example of a pattern synchronization procedure (eg, examples a, b, c, and d). There may be other programs (eg, may have a slightly lower efficiency), such as one or more of: (i) time slot based initial transmission and memory based repetition; (ii) time slot based initial transmission and based on weight Repeated; (iii) memory-based initial transmission and time-slot-based repetition; (iv) memory-based initial transmission and reset-based repetition; and/or (v) reset-based initial transmission and time-based slot Repeat. Table 1

The assignment of resource pools and corresponding modes can be done, for example, statically, semi-statically or dynamically.

Multiple HARQ processes can be provided, for example for unlicensed transmission in URLLC. Multiple HARQ processes may, for example, help reduce transmission latency. In an example, URLLC data that is reached in a short time between each other can be transmitted on different HARQ processes (eg, transmitted immediately). The WTRU may transmit data (eg, URLLC data) via multiple HARQ processes.

In an example where multiple HARQ processes exist, (eg, each) HARQ process can be assigned a separate resource set/resource pool with separate deterministic access modes (eg, as shown in the example in Figure 15) .

Figure 15 is an example of an independent HARQ process with different access modes. As shown, the first HARQ process can be assigned a first set of resources (eg, resources 1, 2, 3) having a first mode (eg, 2, 1, 3). The second HARQ process may be assigned a second set of resources (eg, resources 4, 5, 6) having a second mode (eg, 1, 3, 2). The second mode can be time delayed (eg, delayed by 3 time slots).

In an example where multiple HARQ processes may exist, (eg, each) HARQ process may be assigned a separate resource set/resource pool with a single deterministic access mode.

Figure 16 is an example of an independent HARQ process with the same access mode. As shown, the first HARQ process and the second HARQ process can be assigned the same access mode. The first HARQ process can be assigned a first set of resources (eg, resources 1, 2, 3) having a first mode (eg, 2, 1, 3). The second HARQ process can be assigned a second set of resources (eg, resources 4, 5, 6) having the first mode. This second mode can be time delayed (eg, delayed by 3 time slots).

In an example (eg, associated with the 15th and/or 16th graphs), the gNB may (eg, independently) monitor resources for (eg, each) HARQ processes. The gNB may identify the HARQ process (e.g., when the gNB identifies the WTRU), for example, by resources over which the HARQ process may transmit.

In an example, multiple (eg, all) HARQ processes can be assigned (eg, with a separate deterministic access mode) to a single resource set/resource pool. Access patterns/resources can be, for example, orthogonal or semi-orthogonal. In an example of orthogonal access mode/resources, a gNB may (eg, independently) monitor resources for (eg, each) HARQ processes. The gNB may identify the HARQ process by the resources over which the HARQ process may transmit (eg, once it has identified the WTRU). In an example of a semi-orthogonal access mode/resource, the WTRU and the HARQ ID may be identified, for example, by one or more of: (i) explicit messaging of the HARQ ID (eg, in the SR); (ii) Using WTRU and HARQ ID specific masking to mask the CRC; and/or (iii) using RS identification (eg, by using WTRU and HARQ ID specific RS).

Multiple (eg, all) HARQ processes may, for example, be assigned a single resource set/resource pool (eg, with a single deterministic access mode).

The WTRU may transmit an unlicensed transmission.

Figure 17 is an example of reset-based synchronization for initial transmission.

In an example (eg, as shown in FIG. 17), the WTRU may indicate (eg, during initial access) that it may be transmitting an unlicensed transmission to the gNB and may request an unlicensed resource.

The WTRU may (e.g., may also) include information regarding, for example, its latency tolerance, to enable the gNB to estimate the license-free parameters based on the WTRU's needs. This indication can be sent via PRACH.

The gNB may send an unlicensed configuration to the WTRU. The WTRU may receive the license-free configuration. This license-free configuration can be associated with license-free uplink transmission. For example, the WTRU may send an unlicensed uplink transmission based on the received license-free configuration.

The license-free configuration may include, for example, a resource pool, an access mode for unlicensed transmission of (eg, a particular) HARQ process, and/or a synchronization method. For example, the license-free configuration can indicate multiple access resource collections. Each of the set of access resources can be associated with a particular HARQ process. Resources may include, for example, multiple time, frequency, and/or MCS values, transmission power control parameters, RS locations, and the like. For example, each of the set of access resources may have one or more characteristics, such as, for example, timing, frequency, MCS value, transmission power control parameters, RS location, and the like.

The license-free configuration may include, for example, a resource pool and an unlicensed repetitive access mode within the unlicensed transmission (eg, for a particular HARQ process).

The license-free configuration can be sent by, for example, L1 messaging or RRC configuration.

The WTRU may have and/or obtain material that will be transmitted in a license-free manner. For example, the WTRU may determine that the data needs to be transmitted in the uplink. The material may have one or more needs, such as, for example, latency tolerance. This latent tolerance can be specified as a threshold latency. For example, the data may require the submersible below the threshold value.

The WTRU may identify the unlicensed resource based, for example, on the HARQ process to be used, and the first resource index within the access mode (eg, for a reset procedure). For example, the WTRU may identify one or more characteristics associated with each of the unlicensed resources (eg, access resource sets). The WTRU may compare the requirement for the material to the characteristic of the license-exempt resource. The WTRU may select the resource based on the comparison. For example, the WTRU may select the resource based on latency, priority, and/or reliability. The WTRU may select resources (e.g., access resource sets) that are aligned (e.g., optimally aligned) with the data requirements. For example, the resource may be selected based on a timing and/or frequency that better matches and/or aligns the data requirements than other resources. As an example, the timing and/or frequency of the resource can be compared to the latency tolerance of the data.

The WTRU may transmit an unlicensed frame (e.g., via the data of the license-free frame) to the gNB (e.g., the WTRU may simultaneously transmit the SR to the gNB). For example, the WTRU may use the selected resource to transmit the material without receiving (eg, from a Node B).

In an example where the WTRU may receive an ACK/NACK from the gNB, the gNB may identify the WTRU from the transmission. The gNB may send an ACK/NACK (eg, in the form of a PDCCH grant), such as when the packet is decoded/not decoded, respectively. The receipt of ACK/NACK may result in the termination of the current license-free transaction for the HARQ process. Upon receiving an ACK/NACK and/or grant, the WTRU may no longer continue to use the license-free configuration.

The gNB may identify the WTRU, for example, from an unlicensed transmission.

The gNB may identify the WTRU, for example, from a simultaneous SR signal.

The gNB may (eg, based on the SR) allocate resources for license-based transmissions at a later time (eg, depending on the latency tolerance of the WTRU).

At the same time, the number of HARQ processes can be identified (eg, when there are multiple simultaneous HARQ processes), for example to ensure that the WTRU is allocated sufficient resources.

In an example, multiple SRs may be sent by the WTRU along with information for identifying HARQ processes associated with (eg, each) SR.

In an (eg, additional or alternative) paradigm, (eg, a single) SR may (eg, have the following fields) identify the number of SRs and/or the identification code of the HARQ process that may be associated with the SR.

The time at which the ACK/NACK/license can be received by the WTRU may depend on the tolerant capabilities of the WTRU.

The WTRU may, for example, use a subsequent index of an access mode that may be associated with a particular HARQ process to identify an unlicensed resource (eg, when there may be a latent time when receiving an ACK/NACK/license) to send a duplicate transmission to the gNB (eg, For memory-based transmissions).

The WTRU may (eg, alternatively) use the same resources to send repeated transmissions to the gNB.

The WTRU may receive an ACK/NACK PDCCH grant that may indicate a transmission success/failure and may allocate resources for the license based transmission.

For example, when there are multiple conflicts, the gNB can signal changes to the access mode and/or resource pool for the unlicensed resources.

In an example where the WTRU may receive an ACK/NACK from the gNB in the next slot, the gNB may not be able to identify the WTRU and may not be able to decode the transmission, in which case the entire transmission may fail.

The WTRU may send the repetition in the same manner as the successful case, for example, before the expected ACK/NACK is reached.

For example, when the expected ACK/NACK arrival time has expired (or timed out), the WTRU may send the SR to the gNB and request the resource. The WTRU may (e.g., may also) request a change in the license-free resource parameter.

Systems, methods, and tools are disclosed for uplink transmissions without uplink grants (eg, unlicensed 5G PHY uplink PUSCH transmission). WTRU retransmissions for UL may be provided with and without a license. UL transmissions without UL grants may be initiated, for example, by RRC. Semi-continuous scheduling can be provided by, for example, reduced L1 control messaging. Resources can be effectively allocated for license-free transmission.

Features, elements, and acts (eg, processes and tools) are described herein in a non-limiting manner. While the examples may be for LTE, LTE-A, New Radio (NR) or 5G protocols, the subject matter herein may be applied to other wireless communications, systems, services, and protocols. Each feature, element, act, or other aspect of the subject matter described herein, whether in the drawings or in the specification, can be implemented separately or in any combination, which may include Other topics, whether known or unknown, are implemented in conjunction with the examples given herein.

A WTRU may refer to the identity of a physical device, or the identity of a user, such as an identity associated with subscription, such as an MSISDN, SIP URI, and the like. A WTRU may refer to an application based identifier, such as a username that may be used for an application.

The processes described herein can be implemented in a computer program, software and/or firmware, which can be embodied in a computer readable medium for execution by a computer and/or processor. Examples of computer readable media include, but are not limited to, electronic signals (transmitted via wired and/or wireless connections) and/or computer readable storage media. Examples of computer readable storage media include, but are not limited to, read only memory (ROM), random access memory (RAM), scratchpad, cache memory, semiconductor memory device, magnetic media (eg, However, it is not limited to internal hard disks and removable disks), magneto-optical media, and/or optical media (such as CD-ROM discs and/or digital versatile discs (DVD)). A processor associated with the software is used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and/or any host computer.

ACK‧‧‧ response

GNB, 180a, 180b, 180c‧‧‧Next Node B

HARQ‧‧‧Hybrid automatic repeat request

MCS‧‧‧ modulation coding scheme

N2, N3, N4, N6, N11, S1, X2, Xn‧‧ interface

PDCCH‧‧‧ entity downlink control channel

RRC‧‧‧ Radio Resource Control

SPS‧‧‧ semi-continuous scheduling

SR‧‧‧Service Request

TF‧‧‧Time-Frequency

UE‧‧‧User equipment

URLLC‧‧‧ Ultra-reliable and low-latency communication

100‧‧‧Communication system

102, 102a, 102b, 102c, 102d‧ ‧ ‧ wireless transmit / receive unit (WTRU)

104, 113‧‧‧ Radio Access Network (RAN)

106, 115‧‧‧ Core Network (CN)

108‧‧‧Public Switched Telephone Network (PSTN)

110‧‧‧Internet

112‧‧‧Other networks

114a, 114b‧‧‧ base station

116‧‧‧Intermediate mediation

118‧‧‧Processor

120‧‧‧ transceiver

122‧‧‧Transmission/receiving components

124‧‧‧Speaker/Microphone

126‧‧‧Keypad

128‧‧‧Display/Touchpad

130‧‧‧ Non-removable memory

132‧‧‧Removable memory

134‧‧‧Power supply

136‧‧‧Global Positioning System (GPS) chipset

138‧‧‧ Peripherals

160a, 160b, 160c‧‧‧e Node B

162‧‧‧Mobility Management Entity (MME)

164‧‧‧Service Gateway (SGW)

166‧‧‧ Packet Data Network (PDN) Gateway (or PGW)

182a, 182b‧‧‧Route Control Plane Information to Access and Mobility Management (AMF)

183a, 183b‧‧‧Dialog Management Function (SMF)

184a, 184b‧‧‧ route user plane data to user plane function (UPF)

185a, 185b‧‧‧ Data Network (DN)

1A is a system diagram showing an exemplary communication system in which one or more embodiments of the disclosed embodiments may be implemented. 1B is a system diagram showing an exemplary wireless transmit/receive unit (WTRU) that can be used within the communication system shown in FIG. 1A, in accordance with an embodiment. 1C is a system diagram showing an exemplary Radio Access Network (RAN) and an exemplary Core Network (CN) that can be used within the communication system shown in FIG. 1A, in accordance with an embodiment. 1D is a system diagram showing another exemplary RAN and another exemplary CN that may be used within the communication system shown in FIG. 1A, in accordance with an embodiment. Figure 2 is an example of a cycle in which RRC is used to configure UL SPS transmission. Figure 3 is an example of using RRC to configure the period and TF resources of UL SPS transmission. FIG. 4 is an example of using RRC to configure a period of UL SPS transmission, TF resources, and MCS. Figure 5 is an example of a WTRU being assigned to a single resource. Figure 6 shows an example of gNB resource search. Figure 7 is an example of assigning a WTRU to multiple resources. Figure 8 shows an example of gNB resource search. Figure 9 is an example of assigning a WTRU to a single logical resource. Figure 10 shows an example of gNB resource search. Figure 11 is an example of an unlicensed transaction with an initial transmission, one or more repetitions, and a license/(N)ACK. Figure 12 is an example of time-based synchronization for Initial Transfer (Initial Tx). Figure 13 is an example of memory-based synchronization for initial transmission. Figure 14 is an example of reset-based synchronization for initial transmission. Figure 15 is an example of an independent HARQ process with different access modes. Figure 16 is an example of an independent HARQ process with the same access mode. Figure 17 is an example of reset-based synchronization for initial transmission.

Claims (20)

A wireless transmit/receive unit (WTRU) comprising: a memory; and a processor configured to: receive a license-free configuration associated with an unlicensed uplink transmission from a Node B, the license-free configuration indicating a first set of access resources associated with a first hybrid automatic repeat request (HARQ) process and a second set of access resources associated with a second HARQ process; determining that a data needs to be transmitted in an uplink transmission Transmitting; comparing the requirement associated with the data with a first characteristic associated with the first set of access resources and a second characteristic associated with the second set of access resources; based on the demand and the first characteristic and The comparison of the second characteristic selects the first set of access resources; and uses the first set of access resources to transmit the data in the uplink without receiving a permission from the Node B. The WTRU as claimed in claim 1, wherein the first set of access resources is associated with a first access mode having a first plurality of resources in time and frequency, and wherein the second access The set of resources is associated with a second access mode having a second plurality of resources in time and frequency. The WTRU as claimed in claim 1, wherein the license-free configuration indicates a third set of access resources associated with a third HARQ process and a fourth access resource associated with a fourth HARQ process. set. The WTRU as claimed in claim 1, wherein the first set of access resources is selected based on one or more of: a latency, a priority, or a reliability. The WTRU as claimed in claim 1, wherein the first characteristic associated with the first set of access resources comprises a first timing and a first frequency, and wherein the second access resource set The associated second characteristic includes a second timing and a second frequency. The WTRU as claimed in claim 5, wherein the requirement associated with the data comprises a latency tolerance below a threshold, and wherein the first access resource is based on the first timing ratio The second timing is better matched to the latency tolerance and is selected. The WTRU as claimed in claim 5, wherein the requirement associated with the data comprises a latency tolerance below a threshold, and wherein the first access resource is based on the first frequency ratio The second frequency is better aligned to this latent tolerance and is chosen. The WTRU of claim 1, wherein the processor is further configured to retransmit the data using the first set of access resources. The WTRU as claimed in claim 1, wherein the processor is further configured to: receive an acknowledgement (ACK) in response to the transmitted data; and receive an entity downlink control channel (PDCCH) grant, the PDCCH The grant allocates resources for a license-based uplink transmission from the WTRU. The WTRU as claimed in claim 1, wherein the Node B is a Next Generation Node B (gNB), and wherein the license-free configuration is received via a Radio Resource Control (RRC) configuration message. A method comprising: receiving, from a Node B, a license-free configuration associated with an unlicensed uplink transmission, the license-free configuration indicating a first access associated with a first hybrid automatic repeat request (HARQ) process a set of resources and a second set of access resources associated with a second HARQ process; determining that a profile needs to be transmitted in an uplink transmission; associating a requirement associated with the profile with the first access resource Comparing a first characteristic of the set with a second characteristic of the second access resource set; and selecting the first access resource set based on the comparison of the requirement with the first characteristic and the second characteristic; And using the first set of access resources to transmit the data in the uplink without receiving a permission from the Node B. The method of claim 11, wherein the first set of access resources is associated with a first access mode having a first plurality of resources in time and frequency, and wherein the second access The set of resources is associated with a second access mode having a second plurality of resources in time and frequency. The method of claim 11, wherein the license-free configuration indicates a third set of access resources associated with a third HARQ process and a fourth access resource associated with a fourth HARQ process. set. The method of claim 11, wherein the first set of access resources is selected based on one or more of: a latent time, a prioritized, or a reliability. The method of claim 11, wherein the first characteristic associated with the first set of access resources comprises a first timing and a first frequency, and wherein the second access resource set The associated second characteristic includes a second timing and a second frequency. The method of claim 15, wherein the requirement associated with the data comprises a latency tolerance below a threshold, and wherein the first access resource is based on the first timing ratio The second timing is better matched to the latency tolerance and is selected. The method of claim 15, wherein the requirement associated with the data comprises a latency tolerance below a threshold, and wherein the first access resource is based on the first frequency ratio The second frequency is better aligned to this latent tolerance and is chosen. The method of claim 11, further comprising retransmitting the data using the first set of access resources. The method of claim 11, further comprising: receiving an acknowledgement (ACK) in response to the transmitted data; and receiving an entity downlink control channel (PDCCH) grant, the PDCCH grant being based on a grant The uplink transmission allocates resources. The method of claim 11, wherein the Node B is a Next Generation Node B (gNB), and wherein the license-free configuration is received via a Radio Resource Control (RRC) configuration message.