WO2019005712A1 - 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

UPLINK TRANSMISSION WITHOUT AN UPLINK GRANT

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. provisional patent application no. 62/524,820, filed June 26, 2017, which is incorporated herein by reference in its entirety.

BACKGROUND

[0002] Mobile communications continue to evolve. A fifth generation may be referred to as 5G. A previous (legacy) generation of mobile communication may be, for example, fourth generation (4G) long term evolution (LTE). Mobile wireless communications implement a variety of radio access technologies (RATs), such as New Radio (NR). Use cases for NR may include, for example, extreme Mobile Broadband (eMBB), Ultra High Reliability and Low Latency Communications (URLLC) and massive Machine Type Communications (mMTC).

SUMMARY

[0003] Systems, methods and instrumentalities are disclosed for uplink transmission without an uplink grant. The uplink transmission may be a 5G PHY uplink PUSCH transmission without a grant. A wireless transmit/receive unit (WTRU) may receive a grant free configuration from a network node (e.g., a NodeB). The network node may be a next generation NodeB (gNB) and the grant free configuration may be received via a radio resource control (RRC) message. 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 first access resource set may be associated with a first hybrid automatic repeat request (HARQ) process. The first access resource set may be associated with a first access pattern having a first plurality of resources in time and frequency. The second access resource set may be associated with a second HARQ process. The second access resource set may be associated with a second access pattern having a second plurality of resources in time and frequency. The grant free configuration may indicate a third access resource set and a fourth access resource set. The third access resource set may be associated with a third HARQ process. The fourth access resource set may be associated with a fourth HARQ process.

[0004] 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 first characteristics associated with the first access resource set may include a first timing and a first frequency. The second characteristics may include a second timing and a second frequency. The WTRU may select the first access resource set based on the comparison of the requirements to the first characteristics and the second characteristics. For example, the requirements associated with the data may include a latency tolerance below a threshold. The first access resource set may be selected based on the first timing better matching the latency tolerance than the second timing. The first access resource set may be selected based on the first frequency better aligning with the latency tolerance than the second frequency. The WTRU may select the first access resource set based on latency priority, and/or reliability. The WTRU may transmit the data in the uplink without receiving a grant from the network node (e.g., NodeB). The WTRU may transmit the data using the first access resource set. The WTRU may retransmit the data using the first access resource set. The WTRU may receive an acknowledgment (ACK) in response to the transmitted data. The WTRU may receive a control channel (e.g., a physical downlink control channel (PDCCH) grant that allocates resources for grant based uplink transmission from the WTRU.

BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0009]

[0010] FIG. 2 is an example of using RRC to configure periodicity of a UL SPS transmission.

[0011] FIG. 3 is an example of using RRC to configure periodicity of a UL SPS transmission and TF resources.

[0012] FIG. 4 is an example of using RRC to configure periodicity of a UL SPS transmission, TF resources, and MCS.

[0013] FIG. 5 is an example of a WTRU assigned to single resource.

[0014] FIG. 6 is an example of a gNB resource search.

[0015] FIG. 7 is an example of assigning a WTRU to multiple resources.

[0016] FIG. 8 is an example of a gNB resource search.

[0017] FIG. 9 is an example of assigning a WTRU to a single logical resource.

[0018] FIG. 10 is an example of a gNB resource search.

[0019] FIG. 11 is an example of a grant free transaction with an initial transmission, repetitions and grant/(N)ACK.

[0020] FIG. 12 is an example of time based synchronization for Initial Tx.

[0021] FIG. 13 is an example of memory based synchronization for Initial Tx.

[0022] FIG. 14 is an example of reset based synchronization for Initial Tx.

[0023] FIG. 15 is an example of independent HARQ processes with different access patterns.

[0024] FIG. 16 is an example of independent HARQ processes with the same access pattern.

[0025] FIG. 17 is an example of reset based synchronization for Initial Tx.

DETAILED DESCRIPTION

[0026] A detailed description of illustrative embodiments will now be described with reference to the various Figures. Although this description provides a detailed example of possible implementations, it should be noted that the details are intended to be exemplary and in no way limit the scope of the application.

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

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

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

[0030] The base station 114a may be part of the RAN 104/113, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions. [0031] The base stations 1 14a, 1 14b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 1 16, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

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

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

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

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

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

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

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

[0039] The CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 1 10, and/or the other networks 112. The PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common

communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and/or the internet protocol (IP) in the TCP/IP internet protocol suite. The networks 1 12 may include wired and/or wireless communications networks owned and/or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/1 13 or a different RAT.

[0040] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU

102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0041] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a

speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0073] The CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator. [0074] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 1 13 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like. The AMF 162 may provide a control plane function for switching between the RAN 1 13 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.

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

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

[0077] The CN 115 may facilitate communications with other networks. For example, the CN 1 15 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 1 15 and the PSTN 108. In addition, the CN 1 15 may provide the WTRUs 102a, 102b, 102c with access to the other networks 1 12, which may 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 may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b. [0078] In view of Figures 1 A-1 D, and the corresponding description of Figures 1 A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 1 14a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.

[0079] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the

communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or may performing testing using over-the-air wireless communications.

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

[0081] 5G wireless networks (e.g., NR) may support diverse applications and different terminal types and categories. 5G networks may support, for example, ultra reliable low latency communications (URLLC) and massive machine-type communications (mMTC). URLLC may involve (e.g., require) very stringent low latency while mMTC may involve connectivity with a large number of devices. Other networks (e.g., long term evolution (LTE) systems) may not support low latency and massive connectivity (e.g., for uplink (UL) transmission). Signaling time to establish a UL communication between a WTRU and gNB in LTE systems may be significant (e.g., prohibitive) to support URLLC. Significant L1 control signaling overhead for massive connectivity in mMTC in UL communication may be very costly to implement in LTE systems. A cost of dynamic L1 control signaling for UL may be higher for small packets, e.g., given a higher ratio of signaling overhead to useful payload. URLLC and mMTC may, for example, use small packets (e.g., to carry critical information). UL scheduling schemes may be provided herein for transmission without grant or semi-persistent scheduling (SPS) with low latency and/or low L1 control signaling. [0082] UL transmission without grant may provide low latency with minimal L1 control signaling for UL transmission in NR. Transmission without grant may be used to initiate a UL transmission, for example, for URLLC. A transmission mechanism may be switched to grant-based, for example, upon transmission of a first few transport blocks (TBs), e.g., for improved reliability. A WTRU may map a received UL grant to one or more previous UL transmissions without grant.

[0083] WTRUs may be activated/reactivated and deactivated (e.g., efficiently with a minimal amount of L1 control signaling).

[0084] Resource allocation may be a component of a transmission without grant scheme, e.g., to provide efficient mapping among single/multiple WTRUs and single/multiple time-frequency logical/physical resources.

[0085] A UL SPS transmission feature in LTE may reduce control channel overhead, e.g., for VolP/VoLTE based services. UL SPS for mMTC may involve significant L1 control signaling overhead, e.g., due to a very large number of devices. LTE UL SPS may not be (e.g., directly) applicable to one or more (e.g., general) scenarios for transmission without grant in NR URLLC for one or more (e.g., following) reasons.

[0086] Ultra low latency may be achieved, for example, (e.g., only) by WTRU autonomous UL transmission after RRC configuration. UL SPS L1 control signaling may not be necessary to enable transmissions of URLLC traffic, which may be aperiodic and sporadic.

[0087] A network may not provide (e.g., necessary) resources in a timely manner to guarantee URLLC service quality, for example, when L1 signaling may be applied for deactivation, e.g., where arrival of URLLC traffic may not be predictable.

[0088] UL SPS transmission may be designed, for example, to support an efficient grant-free mechanism for UL transmission.

[0089] Example implementations are provided for WTRU retransmissions for UL with and without grant. A WTRU may not have data to transmit in the UL (e.g., WTRU buffer may be empty). A WTRU may indicate the status of its buffer to a gNB, for example, using one or more of the following examples.

[0090] A WTRU may indicate (e.g., explicitly) on a UL control channel (e.g., PUCCH), for example, regarding release of a configured UL grant and/or the status of a WTRU buffer. In an example, an indication (e.g., a Scheduling Release Request (SRR)) may be, for example, (e.g., one-bit) information that may be transmitted on a Short PUCCH in UL. A short PUCCH may include a reduced number of OFDM symbols than a PUCCH (e.g., a normal PUCCH). For example, a short PUCCH may include one or two OFDM symbols.

[0091] A WTRU may indicate to a gNB that it has nothing to transmit in UL, for example, by transmitting zeros on data resources of a configured uplink grant that may be used for initial transmission while transmitting configured UL reference symbol (e.g., DM-RS, SRS) in a slot. A WTRU may repeat transmitting zeros on data resources of a configured uplink grant that may be used for an initial transmission multiple times, e.g., until it reaches a certain semi-statically pre-configured parameter. A WTRU may (e.g., implicitly) release a configured uplink grant and may stop (re)transmissions in the UL. A gNB may determine that a WTRU's buffer may be (e.g., is) empty, for example, by detecting a configured UL Reference Symbol that may be used for an initial transmission and by detecting zeros on a PUSCH data part.

[0092] A WTRU may indicate (e.g., implicitly) to a gNB that it has nothing to transmit in the UL, for example, by transmitting nothing on a configured uplink grant that may be used for an initial transmission (e.g., on/off scheme). In an example, a gNB may determine that a WTRU's buffer may be empty, for example, by not detecting anything on a configured uplink grant that may be used for an initial transmission.

[0093] A WTRU may receive an (e.g., explicit) indication on a DL control channel (e.g., PDCCH, PHICH) from a gNB to stop (re)transmissions in a configured uplink grant that may be used for an initial transmission. An indication may be (e.g., one-bit) information that may be (e.g., dynamically) signaled on a group-common PDCCH. A WTRU may distinguish a grant-free DL control channel from other control channels, for example, by using a PDCCH CRC, which may be masked, e.g., by a GF-RNTI that may be allocated for transmission without grant.

[0094] . In examples, a WTRU may not start using SPS grants/assignments, for example, unless it may (e.g., does) receive an activation command from an eNB, which may be transmitted (e.g., explicitly) in Downlink Control Information (DCI). Transmitting an activation command in DCI may (e.g., in NR) substantially increase downlink control overhead, for example, when there may be a large number of ultra- reliable low-latency WTRUs in the system. A (e.g., each) WTRU may transmit a packet at any time within a latency boundary of the service. Waiting for an activation command to be (e.g., dynamically) transmitted (e.g., by gNB) to a WTRU may be implausible.

[0095] A WTRU may be configured to send data in the UL without receiving a grant (e.g., an UL grant). UL transmission without UL grant may be activated, for example, by Radio Resource Control (RRC).

[0096] A WTRU may receive (e.g., via a configuration message) a grant free configuration associated with grant free uplink transmissions. A WTRU may receive an activation command, for example, in (e.g., as part of) a configuration by higher layer signaling (e.g., Radio Resource Control (RRC)). The WTRU may receive the activation command via a configuration message (e.g., the configuration message that includes the grant free configuration). The WTRU may activate grant free uplink transmissions based on receipt of the activation command. A WTRU may receive, for example, a configuration message from a scheduler. In an example, a configuration message may be referred to as an Uplink Transmission Without Uplink Grant (UTWUG)-ConfigUL. A configuration message may include, for example, one or more of the following fields: (i) UL grant activation; (ii) UL grant de-activation; (iii) UL grant release; (iv) UTWUG- Radio Network Temporary Identifier (RNTI); (v) UTWUG interval; (vi) time-frequency resource assignment (e.g., including slot(s)/OFDM symbols and Resource Blocks (RBs)); (vii) modulation and coding scheme (MCS); (viii) redundancy version; (ix) cyclic shift of a Demodulation Reference Symbol (DM-RS); and/or (x) Transmit Power Control (TPC) command.

[0097] A WTRU may be configured, for example, by an UTWUG_ConfigUL. A WTRU may (e.g., immediately) use a grant for UL transmission, for example, when it has a packet to transmit without waiting for dynamic signaling (e.g., from gNB on DCI).

[0098] A WTRU may follow instructions in a DCI (e.g., rather than an RRC configuration), for example, when the WTRU receives a DCI. A configuration provided dynamically (e.g., by DCI) may (e.g., always) overwrite configuration or instruction (e.g., a configuration message) provided by higher layer signaling.

[0099] Semi-persistent scheduling may be provided with reduced L1 control signaling. URLLC and mMTC may be characterized, for example, by sporadic and unpredictable transmission of relatively small payloads. UL SPS transmission (e.g., properly configured and modified to reduce L1 control signaling) may be provided, for example, for UL grant-free transmission for services such as URLLC and mMTC.

[0100] In an example, (e.g., of UL SPS), a terminal may be provided with a scheduling decision on a DL control channel. A scheduling decision may, for example, be provided with an indication that the scheduling decision may apply to every nth subframe (e.g., until further notice), where n may be periodicity and a value of n may be a positive integer. Control signaling may be used (e.g., only) once and overhead may be reduced.

[0101] FIG. 2 is an example of using RRC to configure periodicity of a UL SPS transmission. One or more (e.g., other) configurations may (e.g., additionally or alternatively) be provided, for example, by L1 signaling.

[0102] In an example (e.g., as shown in FIG. 2), a periodicity (e.g., the value of n) for a UL SPS transmission may be configured (e.g., in advance) by RRC signaling. Activation/reactivation and/or deactivation may be accomplished, for example, using L1 control signaling (e.g., by semi-persistent C- RNTI). In an example (e.g., for URLLC where latency may be a consideration), a scheduler may configure a periodicity (e.g., of 1 ms) for SPS. A gNB may activate the semi-persistent pattern (e.g., by L1 signaling such as PDCCH), for example, when the WTRU requests scheduling. Other configurations (e.g., modulation and coding scheme (MCS) and time-frequency (TF) resource) may (e.g., also) be configured (e.g., every time) during activation/reactivation. [0103] A WTRU may monitor (e.g., continue to monitor) a PDCCH for uplink and downlink scheduling commands, for example, after enabling semi-persistent scheduling. A dynamic scheduling command may (e.g., when detected) take precedence over SPS in a subframe, which may be useful, for example, when SPS allocated resources may need to be increased.

[0104] FIG. 3 is an example of using RRC to configure periodicity of a UL SPS transmission and TF resources. One or more (e.g., other) configurations may (e.g., additionally or alternatively) be provided, for example, by L1 signaling.

[0105] In an example (e.g., as shown in FIG. 3), a periodicity of UL SPS transmission and TF resources may be configured (e.g., in advance) by RRC signaling. Activation/reactivation and deactivation may be accomplished, for example, using L1 control signaling (e.g., by semi-persistent C-RNTI). In an example (e.g., for URLLC where latency may be crucial), a scheduler may configure a periodicity of 1 ms for SPS. A gNB may activate a semi-persistent pattern (e.g., by L1 signaling such as PDCCH), for example, when a WTRU requests scheduling. Other configurations (e.g., modulation and coding scheme (MCS)) may (e.g., also) be configured (e.g., every time) during activation/reactivation.

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

[0107] FIG. 4 is an example of using RRC to configure periodicity of a UL SPS transmission, TF resources, and MCS.

[0108] In an example (e.g., as shown in FIG. 4), multiple (e.g., all) parameters (e.g., periodicity of a UL SPS transmission, TF resources, and MCS) may be configured (e.g., in advance) by RRC signaling. L1 control signaling to activate or deactivate WTRUs may be unnecessary, for example, when WTRUs remain activated.

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

[0110] Resource allocation may be provided (e.g., efficiently) for grant free transmission. In an example, a WTRU may be assigned to a (e.g., single) resource for grant free transmission. A gNB may (e.g., in this case) know which resource to search for the WTRU. Examples are shown in FIGS. 5 and 6.

[0111] FIG. 5 is an example of a WTRU assigned to single resource. A resource (e.g., a single resource) may be assigned to a WTRU. [0112] FIG. 6 is an example of a gNB resource search. One or more WTRUs may be assigned to a resource. A gNB may know to which resource a WTRU is assigned.

[0113] In an example (e.g., as shown in FIG. 6), a gNB may know to search for UE1 (e.g., WTRU 1) and UE2 (e.g., WTRU 2) in resource 2 (e.g., only search in resource 2) and to search for UE3 and UE4 (e.g., WTRU 3 and WTRU 4) in resource 4 (e.g., only search in resource 4).

[0114] Grant free transmission failures may occur, for example, when multiple WTRUs may be (e.g., are) assigned to a single resource. Grant free transmission failures may occur, for example, due to collisions between simultaneous grant free transmissions from multiple WTRUs. This may be resolved, avoided or minimized, for example, by assigning multiple WTRUs to multiple resources and allowing a (e.g., each) WTRU to (e.g., autonomously) select a resource (e.g., randomly). This may result in an increase in decoding complexity at a gNB.

[0115] FIG. 7 is an example of assigning a WTRU to multiple resources. Multiple resources may be assigned to a WTRU.

[0116] FIG. 8 is an example of a gNB resource search. Multiple (e.g., all) WTRUs may be assigned to the same resources. For example, multiple WTRUs may each be assigned to the same multiple resources.

[0117] In an example (e.g., as shown in FIG. 8), a gNB may know to search for (e.g., all) WTRUs (e.g., UE1 , UE2, UE3, and UE4) in the multiple (e.g., all) resources that are available for grant free access (e.g., resources 2 and 4).

[0118] A WTRU may be assigned to multiple resources that may be accessed in a deterministic manner. The deterministic manner may be an access pattern known to the WTRU and a network node (e.g., a gNB). A blocking probability and decoding complexity at the gNB may be reduced or minimized, for example, by assigning a WTRU to multiple resources and by accessing the resources in a deterministic manner that may be known to the WTRU and gNB (e.g., using a known access pattern). An (e.g., each) element of a pattern may be used, for example, during resource access. Resource access may occur, for example, (i) during successive initial transmissions in a grant-free transmission from a WTRU; (ii) during repetitions of a transmission from a WTRU that may be transmitting a grant free transmission (e.g., before it receives a response from a gNB); and/or (iii) during a (e.g., specific) HARQ process.

[0119] A WTRU may be assigned to a single logical set of resources. The logical set of resources may be mapped, for example, using an access pattern to multiple physical resources (e.g., as shown by example in FIG. 9).

[0120] FIG. 9 is an example of assigning a WTRU to a single logical resource. A logical resource may comprise multiple physical resources (e.g., with an access pattern). A WTRU may be assigned to multiple physical resources (e.g., of a single logical resource). [0121] A gNB may know a resource that may be used by a WTRU . Complexity of a decoding procedure may be reduced, for example, when a gNB knows a resource that may (e.g., will) be used by a WTRU . An example is shown in FIG. 10.

[0122] FIG. 10 is an example of a gNB resource search . Multiple WTRUs may be assigned the same resources (e.g., in one or more activation/repetition slots).

[0123] In an example (e.g., as shown in FIG. 10), a gNB may search for UE1 in resource 2 for slot 1 and resource 4 for slot n . A gNB may search for UE2 in resource 2 for slots 1 and n . A gNB may search for UE3 in resource 4 for slot 1 and resource 2 for slot n . A gNB may search for UE4 in resource 4 for slots 1 and n .

[0124] A WTRU may be assigned to a (e.g., single) logical set of resources. The logical set of resources may be assigned to a single resource with a single pattern, which may be similar to a single resource assignment (e.g., discussed in a previous example with respect to FIGS. 5 and 6). Assignment to a set of resources with multiple resources with a pattern that may (e.g., does) allow access to multiple resources within a slot may be similar to assigning multiple WTRUs to multiple resources (e.g., discussed in a previous example with respect to FIGS. 7 and 8).

[0125] A framework may be provided for selection and implementation of one or more of multiple procedures. An applicable procedure may be decided, for example, by gNB configuration signaling .

[0126] Pattern synchronization may be provided. A gNB and WTRU may (e.g., must) know a pattern . The gNB and/or the WTRU may be able to synchronize their locations in the pattern, for example, to send and receive a signal in the same resource. In an example, a WTRU (e.g., UE1 ) may be transmitting in resource 2 for slot 1 and a gNB may (e.g., must) be monitoring for the WTRU in resource 2 for slot 1 .

[0127] A deterministic pattern in which resources may be assigned may be indicated by a gNB and may be signaled to a WTRU . For example, a WTRU may receive a grant free configuration from a network node (e.g., a NodeB, a gNB, etc.). The grant free configuration may indicate the deterministic pattern. The deterministic pattern may be an access pattern having a plurality of resources in time and frequency. A deterministic pattern may be assigned for each access resource set. For example, a first access resource set may be associated with a first deterministic pattern and a second access resource set may be associated with a second deterministic pattern. Each access resource set may be associated with a hybrid automatic repeat request (HARQ) process.

[0128] A deterministic pattern in which resources are assigned may be randomly selected by a WTRU and signaled to a gNB.

[0129] FIG. 1 1 is an example of a grant free transaction with an initial transmission, one or more repetitions, and a grant/(N)ACK. [0130] In an example (e.g., as shown in FIG. 11 ), a grant-free transaction may include one or more of the following. A WTRU may have data to send in a grant-free manner (e.g., 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 (e.g., initial transmission in resource 1 as shown by example in FIG. 11) without receiving a grant. The WTRU may send multiple versions (e.g., repetitions in resource 3 and resource 2 as shown by example in FIG. 11) of the data (e.g., to a gNB) without receiving a grant. A WTRU may (e.g., then), for example, (a) receive an indication from a gNB that the data was successfully received; (b) receive an indication from the gNB that the data was not successfully received; (c) receive an indication from the gNB that the data was not received at all (e.g., assuming a simultaneous SR may have been sent with the data and decoded) and/or (d) not receive any signaling from a gNB.

[0131] 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 (e.g., retransmissions). A gNB may (e.g., for (a), (b) and (c)) switch a WTRU to a schedule based transmission with a (e.g., an explicit) grant. A WTRU may (e.g., for (d)), send a (e.g., an explicit) Service Request (SR).

[0132] A repetition may be a retransmission. For example, a repetition may (re)send the same information coded in the same manner or in a different manner. The number of repetitions may be dependent, for example, on WTRU capability, configuration, etc. In an example, K may be a number of time resources (e.g., slots) that a gNB may delay before sending a URLLC WTRU an ACK/NACK and/or a PDCCH that may indicate a resource to use. The value of K may, for example, depend on a latency that may be tolerated by a WTRU. In an example, lower values of K may be assigned to WTRUs with lower latency tolerances. In an example where K=1 , ACK/NACK/PDCCH may be sent in the next slot and (e.g., only) the initial transmission pattern may be valid. A WTRU may, for example, indicate parameter K (e.g., during initialization). A value for parameter K may (e.g., additionally or alternatively) be implied (e.g., based on a specific WTRU class).

[0133] A system may use one or more implementations to synchronize locations in a pattern.

Synchronization implementations may include, for example, time synchronization, memory based synchronization, and/or reset based synchronization.

[0134] FIG. 12 is an example of time based synchronization for Initial Tx. FIG. 12 shows an example of initial access in a grant free transaction.

[0135] In an example of time synchronization (e.g., as shown in FIG. 12), a resource that may be used for a grant-free transaction may be a function of time (e.g., a subframe, slot or mini-slot) and/or the number of elements in an access pattern. In an example of a slot-based time synchronization system, a pattern may be, for example, {3,1 ,2}, which may indicate that resource 3 may be used in time slot 1 , resource 1 may be used in time slot 2, and resource 2 may be used in time slot 3. This pattern may repeat, e.g., resource 3 may be used in time slot 4, and so on ad infinitum. A WTRU seeking to send a grant-free transmission may, for example, determine a time relative to a time marker (e.g., an index of a slot in the subframe). The WTRU may use the time relative to a time marker as an index into an access pattern. A resource that a gNB may monitor at a time slot may be given, for example, by:

access_pattern_index = slotjndex modulo number_of_elements_in_access_pattern.

A gNB may monitor the same resource, for example, as determined by a time relative to a time marker (e.g., an index of a slot in a subframe).

[0136] FIG. 13 is an example of memory based synchronization for Initial Tx. FIG. 13 shows an example of initial access in a grant free transaction.

[0137] In an example of memory based synchronization (e.g., as shown in FIG. 13), a resource that may be used for a grant-free transaction may be a function of the last element of a pattern that has been used. A WTRU and gNB may, for example, use a next resource index in a pattern to identify a grant-free resource. A WTRU and gNB may keep track of an index, e.g., so that a correct index may be accessed and monitored, respectively. In an example of a memory based system, a pattern may be, for example, {3,1 ,2}, which may indicate that resource 3 may be used the first time a resource may be needed. A WTRU may transmit on resource 3 and a gNB may monitor resource 3. Resource 1 may be used the next time a resource may be needed. The WTRU may transmit on resource 1 and the gNB may monitor resource 1. Loss of synchronization (e.g., in the event that a gNB may be unable to decode a transmission) may be prevented, for example, by transmitting the current index, e.g., in a simultaneous SR signal that may be sent with the transmission. A gNB may (e.g., be able to) identify a WTRU and its current index and may reset its monitoring to a correct index for the next grant-free transaction.

[0138] FIG. 14 is an example of reset based synchronization for Initial Tx. FIG. 14 shows an example of an initial access in a grant free transaction.

[0139] In an example of reset based synchronization (e.g., as shown in FIG. 14), a resource that may be used at the start of a grant-free transaction may (e.g., always) reset to an initial index in an access pattern. Additional transmissions within a grant-free transmission may use the next elements in the access pattern, for example, in order. In an example of reset based synchronization, a pattern may be, for example, {3,1 ,2}. A reset to resource 3 may occur, for example, at the beginning of an access.

Subsequent transmission(s) within a grant free transaction may access resource 1 then resource 2.

[0140] Smart allocation of a resource pool and assignment of a pattern to a WTRU (e.g., in time synchronization, memory based synchronization, and/or reset based synchronization) may reduce a probability of collisions between WTRUs that may be trying to use a resource.

[0141] A pattern that may be used for an initial transmission may be the same as or different from a pattern that may be used for repetition. [0142] In an example (e.g., example a), an initial transmission and a repetition may use a time based procedure. A specific resource that may be accessed by a WTRU/gNB may depend (e.g., entirely) on time.

[0143] In an example (e.g., example b), an initial transmission and a repetition may use a memory based procedure. An initial transmission may, for example, use the next index in an access pattern and a repetition may use the same index. Information may be chase combined, for example, when it may be (e.g., only) a decoding problem. An initial transmission may (e.g., alternatively) use the next index in an access pattern and a repetition may continue incrementing the indices.

[0144] In an example (e.g., example c), an initial transmission may use a reset procedure and a repetition may use a memory procedure. An initial transmission may, for example, use a first index in an access pattern and a repetition may use the same index. Information may be chase combined, for example, when it may be (e.g., only) a decoding problem. An initial transmission may (e.g., alternatively) use a first index in an access pattern and a repetition may continue incrementing the indices.

[0145] In an example (e.g., example d), transmission and repetition utilization of reset-based procedures may be similar to an example discussed with respect to FIGS. 5 and 6.

[0146] Table 1 is an example of pattern synchronization procedures (e.g., examples a, b, c, and d). There may be other procedures (e.g., with perhaps less efficiency), such as one or more of the following: (i) initial transmission based on time slot and repetition based on memory; (ii) initial transmission based on time slot and repetition based on reset; (iii) initial transmission based on memory and repetition based on time slot; (iv) initial transmission based on memory and repetition based on reset and/or (v) initial transmission based on reset and repetition based on time slot.

Table 1

[0147] Assignment of a pool of resources and a corresponding pattern may be accomplished, for example, statically, semi-statically, or dynamically.

[0148] Multiple HARQ processes may be provided, for example, for grant-free transmissions in URLLC. Multiple HARQ processes may, for example, help reduce the latency of transmission. In an example, URLLC data that may arrive within a short time of each other may be transmitted (e.g., immediately) on different HARQ processes. A WTRU may transmit data (e.g., URLLC data) via multiple HARQ processes. [0149] In an example where there may be multiple HARQ processes, a (e.g., each) HARQ process may be assigned a separate set/pool of resources with separate deterministic access patterns (e.g., as shown by example in FIG. 15).

[0150] FIG. 15 is an example of independent HARQ processes with different access patterns. As shown, a first HARQ process may be assigned a first set of resources (e.g., resources 1 , 2, 3) having a first pattern (e.g., 2,1 ,3). A second HARQ process may be assigned a second set of resources (e.g., resources 4,5,6) having a second pattern (e.g., 1 ,3,2). The second pattern may be time delayed (e.g., by 3 time slots).

[0151] In an example where there may be multiple HARQ processes, a (e.g., each) HARQ process may be assigned a separate set/pool of resources with a single deterministic access pattern.

[0152] FIG. 16 is an example of independent HARQ processes with the same access pattern. As shown, a first HARQ process and a second HARQ process may be assigned the same access pattern. The first HARQ process may be assigned a first set of resources (e.g., resources 1 , 2, 3) having a first pattern (e.g., 2,1 ,3). A second HARQ process may be assigned a second set of resources (e.g., resources 4,5,6) having the first pattern. The second pattern may be time delayed (e.g., by 3 time slots).

[0153] In examples (e.g., the cases associated with FIGs. 15 and/or 16), a gNB may (e.g., independently) monitor resources for a (e.g., each) HARQ process. A gNB may identify a HARQ process, for example, by a resource the HARQ process may be transmitted on (e.g., when the gNB identified the WTRU).

[0154] In examples, multiple (e.g., all) HARQ processes may be assigned a single set/pool of resources (e.g., with separate deterministic access patterns). Access patterns/resources may be, for example, orthogonal or semi-orthogonal. In an example of orthogonal access patterns/resources, a gNB may (e.g., independently) monitor resources for a (e.g., each) HARQ process. A gNB may identify a HARQ process by the resource the HARQ process may be transmitted on (e.g., once it has identified the WTRU). In an example of semi-orthogonal access patterns/resources, a WTRU and HARQ ID may be identified, for example, by one or more of the following: (i) explicit signaling of a HARQ ID (e.g., in the SR); (ii) masking a CRC with a WTRU and HARQ ID specific mask; and/or (iii) using RS identification (e.g., by using a WTRU and HARQ ID specific RS).

[0155] Multiple (e.g., all) HARQ processes may, for example, be assigned a single set/pool of resources (e.g., with a single deterministic access pattern).

[0156] A WTRU may transmit a grant free transmission.

[0157] FIG. 17 is an example of reset based synchronization for Initial Tx.

[0158] In an example (e.g., as shown in FIG. 17), a WTRU may (e.g., during initial access) indicate that it may be sending grant free transmissions to a gNB and may request grant free resources. [0159] A WTRU may (e.g., also) include information on its latency tolerance, for example, to enable a gNB to estimate grant free parameters based on WTRU needs.

Such an indication may be sent through a PRACH.

[0160] A gNB may send a grant-free configuration to a WTRU. The WTRU may receive the grant free configuration. The grant free configuration may be associated with grant free uplink transmission. For example, the WTRU may send grant free uplink transmissions based on the received grant free configuration.

[0161] A grant free configuration may include, for example, a pool of resources, an access pattern for grant free transmissions for (e.g., specific) HARQ processes, and/or a synchronization method. For example, the grant free configuration may indicate a plurality of access resource sets. Each of the access resource sets may be associated with a specific HARQ process. Resources may include, for example, multiple time, frequency, and/or MCS values, transmit power control parameters, RS locations, etc. For example, each of the access resource sets may have one or more characteristics, for example, such as a timing, a frequency, MCS values, transmit power control parameters, RS locations, etc.

[0162] A grant free configuration may include, for example, a pool of resources and an access pattern for grant free repetitions within a grant free transmission (e.g., for specific HARQ processes).

[0163] A grant-free configuration may be sent, for example, by L1 signaling or RRC configuration.

[0164] A WTRU may have and/or obtain data to be transmitted in a grant free manner. For example, the WTRU may determine that the data needs to be transmitted in the uplink. The data may have one or more requirements, for example, such as a latency tolerance. The latency tolerance may be specified as a threshold latency. For example, the data may require a latency below the threshold latency.

[0165] A WTRU may identify grant free resources, for example, based on a HARQ process to be used and a first resource index in an access pattern (e.g., for a reset procedure). For example, the WTRU may identify one or more characteristics associated with each of the grant free resources (e.g., access resource sets). The WTRU may compare the requirements of the data with the characteristics of the grant free resources. 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 a resource (e.g., an access resource set) that aligns (e.g., best aligns) with the data requirements. For example, the resource may be selected based on a timing and/or frequency better matching and/or aligning with the data requirements than other resources. As an example, the timing and/or the frequency of the resource may be compared to a latency tolerance of the data.

[0166] A WTRU may transmit a grant free frame (e.g., data via the grant free frame) to a gNB (e.g., WTRU may simultaneously transmit an SR to a gNB). For example, the WTRU may send the data using the selected resources without receiving a grant (e.g., from the NodeB). [0167] In an example where a WTRU may receive an ACK/NACK from a gNB, the gNB may identify the WTRU from the transmission. The gNB may send an ACK/NACK (e.g., in the form of a PDCCH grant), for example, when a packet was decoded/not decoded, respectively. Receipt of an ACK/NACK may result in an end to a current grant free transaction for a HARQ process. The WTRU may discontinue use of the grant free configuration upon receipt of an ACK/NACK and/or grant.

[0168] A gNB may identify a WTRU, for example, from a grant free transmission.

[0169] A gNB may identify a WTRU, for example, from a simultaneous SR signal.

[0170] A gNB may (e.g., based on an SR) allocate resources for a grant based transmission at a later time (e.g., depending on a latency tolerance of a WTRU).

[0171] A number of simultaneous HARQ processes may be identified (e.g., when there may be multiple simultaneous HARQ processes), for example, to ensure that a WTRU may be allocated enough resources.

[0172] In an example, multiple SRs may be sent by a WTRU with information to identify a HARQ process associated with an (e.g., each) SR.

[0173] In an (e.g., additional or alternative) example, an (e.g., a single) SR may (e.g., have fields that) identify the number of SRs and/or the identities of HARQ processes that may be associated with the SRs.

[0174] The time that an ACK/NACK/grant may be received by a WTRU may be dependent on a tolerance capability of the WTRU.

[0175] A WTRU may (e.g., when there may be a delay in receipt of an ACK/NACK/grant) use subsequent indices of an access pattern that may be associated with a specific HARQ process, for example, to identify grant free resources to send a repeated transmission to a gNB (e.g., for memory based transmission).

[0176] A WTRU may (e.g., alternatively) use the same resources to send a repeated transmission to a gNB.

[0177] A WTRU may receive an ACK/NACK PDCCH grant that may indicate a success/failure of a transmission and may allocate resources for a grant based transmission.

[0178] A gNB may signal a change to an access pattern and/or resource pool for grant free resources, for example, when there may be multiple collisions.

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

[0180] A WTRU may send repetitions, for example, in the same manner as a successful case before an expected arrival of an ACK/NACK. [0181] A WTRU may send an SR to a gNB and request resources, for example, when an expected ACK/NACK arrival time has expired (or timed-out). A WTRU may (e.g., also) request a change in grant free resource parameters.

[0182] Systems, methods and instrumentalities are disclosed for uplink transmission without an uplink grant (e.g., a 5G PHY Uplink PUSCH transmission without a grant). WTRU retransmissions for UL may be provided with and without a grant. A UL transmission without a UL grant may be activated, for example, by RRC. Semi-persistent scheduling may be provided, for example, with reduced L1 control signaling.

Resources may be efficiently allocated for grant free transmissions.

[0183] Features, elements and actions (e.g., processes and instrumentalities) are described by way of non-limiting examples. While examples may be directed to LTE, LTE-A, New Radio (NR) or 5G protocols, subject matter herein is applicable to other wireless communications, systems, services and protocols. Each feature, element, action or other aspect of the described subject matter, whether presented in figures or description, may be implemented alone or in any combination, including with other subject matter, whether known or unknown, in any order, regardless of examples presented herein.

[0184] A WTRU may refer to an identity of the physical device, or to the user's identity such as subscription related identities, e.g., MSISDN, SIP URI, etc. WTRU may refer to application-based identities, e.g., user names that may be used per application.

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

Claims

CLAIMS What is Claimed:

1 . A wireless transmit/receive unit (WTRU) comprising:

a memory; and

a processor configured to:

receive, from a NodeB, a grant free configuration associated with grant free uplink transmission that indicates a first access resource set associated with a first hybrid automatic repeat request (HARQ) process and a second access resource set associated with a second HARQ process;

determine that data needs to be transmitted in an uplink transmission;

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;

select, based on the comparison of the requirements to the first characteristics and the second characteristics, the first access resource set; and

transmit, using the first access resource set, the data in the uplink without receiving a grant from the NodeB.

2. The WTRU of claim 1 , wherein the first access resource set is associated with a first access pattern having a first plurality of resources in time and frequency, and wherein the second access resource set is associated with a second access pattern having a second plurality of resources in time and frequency.

3. The WTRU of claim 1 , wherein the grant free configuration indicates a third access resource set associated with a third HARQ process and a fourth access resource set associated with a fourth HARQ process.

4. The WTRU of claim 1 , wherein the first access resource set is selected based on one or more of latency, priority, or reliability.

5. The WTRU of claim 1 , wherein the first characteristics associated with the first access resource set comprise a first timing and a first frequency, and wherein the second characteristics associated with the second access resource set comprise a second timing and a second frequency.

6. The WTRU of claim 5, wherein the requirements associated with the data comprise a latency tolerance below a threshold, and wherein the first access resource is selected based on the first timing better matching the latency tolerance than the second timing.

7. The WTRU of claim 5, wherein the requirements associated with the data comprise a latency tolerance below a threshold, and wherein the first access resource set is selected based on the first frequency better aligning with the latency tolerance than the second frequency.

8. The WTRU of claim 1 , wherein the processor is further configured to retransmit the data using the first access resource set.

9. The WTRU of claim 1 , wherein the processor is further configured to:

receive an acknowledgment (ACK) in response to the transmitted data; and

receive a physical downlink control channel (PDCCH) grant that allocates resources for grant based uplink transmission from the WTRU.

10. The WTRU of claim 1 , wherein the NodeB is a next generation NodeB (gNB), and wherein the grant free configuration is received via a radio resource control (RRC) configuration message.

1 1. A method comprising:

receiving, from a NodeB, a grant free configuration associated with grant free uplink transmission that indicates a first access resource set associated with a first hybrid automatic repeat request (HARQ) process and a second access resource set associated with a second HARQ process;

determine that data needs to be transmitted in an uplink transmission;

comparing 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;

selecting, based on the comparing of the requirements to the first characteristics and the second characteristics, the first access resource set; and

transmitting, using the first access resource set, the data in the uplink without receiving a grant from the NodeB.

12. The method of claim 1 1 , wherein the first access resource set is associated with a first access pattern having a first plurality of resources in time and frequency, and wherein the second access resource set is associated with a second access pattern having a second plurality of resources in time and frequency.

13. The method of claim 11 , wherein the grant free configuration indicates a third access resource set associated with a third HARQ process and a fourth access resource set associated with a fourth HARQ process.

14. The method of claim 1 1 , wherein the first access resource set is selected based on one or more of latency, priority, or reliability.

15. The method of claim 11 , wherein the first characteristics associated with the first access resource set comprise a first timing and a first frequency, and wherein the second characteristics associated with the second access resource set comprise a second timing and a second frequency.

16. The method of claim 15, wherein the requirements associated with the data comprise a latency tolerance below a threshold, and wherein the first access resource is selected based on the first timing better matching the latency tolerance than the second timing.

17. The method of claim 15, wherein the requirements associated with the data comprise a latency tolerance below a threshold, and wherein the first access resource set is selected based on the first frequency better aligning with the latency tolerance than the second frequency.

18. The method of claim 1 1 , further comprising retransmitting the data using the first access resource set.

19. The method of claim 11 , further comprising:

receiving an acknowledgment (ACK) in response to the transmitted data; and

receiving a physical downlink control channel (PDCCH) grant that allocates resources for grant based uplink transmission.

20. The method of claim 11 , wherein the NodeB is a next generation NodeB (gNB), and wherein the grant free configuration is received via a radio resource control (RRC) configuration message.