Method, apparatus and system for unlicensed uplink multiple access

Abstract

Methods, apparatuses, and systems are provided for unlicensed (GL) uplink multiple access. A wireless transmit / receive unit (WTRU) may receive a configuration of a set of GL physical uplink shared channel (GL-PUSCH) frequency resources. The WTRU may monitor a downlink control information (DCI) message, wherein the DCI message includes an indication of the presence of at least a subset of the set of GL-PUSCH frequency resources. If the WTRU successfully receives the DCI message, the WTRU may select one or more GL-PUSCH frequency resources from a subset of the set of GL-PUSCH frequency resources, and may select a time period. The WTRU may transmit data on the GL-PUSCH using the selected GL-PUSCH frequency resource during the selected time period. The WTRU may also monitor a hybrid automatic repeat request acknowledgement (HARQ-ACK) based on the selected GL-PUSCH frequency resource. The WTRU may monitor the DCI during a fixed time window.

Description

[0001] This application is a divisional application of the Chinese invention patent application with the application date of August 10, 2017, application number 201780060784.9, and invention name “Method, device and system for unlicensed uplink multiple access”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 373,040, filed August 10, 2016, U.S. Provisional Application No. 62 / 400,934, filed September 28, 2016, and U.S. Provisional Application No. 62 / 474,838, filed March 22, 2017, the contents of which are incorporated herein by reference. Technical Field

[0004] The present application relates to the field of wireless communication technology. Background Art

[0005] The applications of New Radio (NR), also known as Next Generation Radio or Fifth Generation (5G), can be summarized into three main categories: enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable and low latency communications (URLLC). Under each category, there are a range of applications available for various needs and deployment scenarios that meet specific performance requirements. For example, mMTC and URLLC applications range from automotive to health, agriculture, utilities, and logistics industries. Implementing mMTC and URLLC features may require the design of new modulation and coding schemes, waveforms, feedback processes, beamforming mechanisms, and new multiple access methods.

[0006] For mMTC applications, the system is expected to be able to support up to one million mMTC devices per square kilometer, but transmission latency for this application is not as critical as for other applications. For URLLC applications, the density of user equipment (UE) or wireless transmit / receive unit (WTRU) per cell is significantly smaller, but such applications require a target latency of less than 1 millisecond (ms) and a 100% latency of 32-byte messages. -5 High reliability with low error probability. Despite the differences between these two use cases, both require new uplink multiple access (MA) approaches to enable them to achieve their target performance metrics. Summary of the invention

[0007] The present invention provides methods, apparatus and systems for grant-based (GB) and grant-free (GL) uplink transmission in a multiple access (MA) scheme. In an example, a wireless transmit / receive unit (WTRU) may receive a configuration of a GL physical uplink shared channel (GL-PUSCH) frequency resource set. The WTRU may monitor a downlink control information (DCI) message, wherein the DCI message includes an indication of the presence of at least one subset of the GL-PUSCH frequency resource set. If the WTRU successfully receives the DCI message, the WTRU may select one or more GL-PUSCH frequency resources from the subset of the GL-PUSCH frequency resource set, and may select a time period. The WTRU may send data on the GL-PUSCH using the selected one or more GL-PUSCH frequency resources during the selected time period.

[0008] In addition, the WTRU may also determine a time location for receiving a hybrid automatic repeat request acknowledgement (HARQ-ACK) associated with the transmitted GL-PUSCH data based on the selected one or more GL-PUSCH frequency resources. The WTRU may monitor the reception of the HARQ-ACK during the determined time location. In another example, the determination of the time location may be further based on the GL-PUSCH resource index.

[0009] In an example, the DCI message may be a common DCI message. In another example, the selection of one or more GL-PUSCH frequency resources from a subset of GL-PUSCH frequency resources may be determined randomly. In another example, the selection of one or more GL-PUSCH frequency resources from a subset of GL-PUSCH frequency resources may be determined based on a WTRU-ID. In yet another example, the selection of a time period may be determined randomly. In yet another example, the selection of a time period may be determined based on a WTRU-ID.

[0010] Furthermore, in an example, the WTRU may monitor the DCI during a first fixed time window. In another example, the time location may have a second fixed time window. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which:

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

[0013] Figure 1B It shows that Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the illustrated communication system;

[0014] Figure 1C It shows that it can be Figure 1A a system diagram of an example radio access network (RAN) and an example core network (CN) used within the illustrated communication system;

[0015] Figure 1D It shows that Figure 1A A system diagram of another example RAN and another example CN used within the illustrated communication system;

[0016] Figure 2 is a timing diagram of an example scheduling request (SR) procedure in Long Term Evolution (LTE);

[0017] Figure 3 is a flow chart of an example process for using contention-based SR (CB-SR);

[0018] Figure 4A and 4B is a timing diagram of an example SR process;

[0019] Figure 5 is a resource allocation map of an example of a dynamic indication of UL resource grant for grant-free physical uplink shared channel (GL-PUSCH) transmission;

[0020] Figure 6 is a resource allocation diagram of examples of different grant-based physical uplink shared channel (GB-PUSCH) resource types according to physical uplink shared channel (PUSCH) resource types;

[0021] Figure 7 is a resource allocation diagram of an example of Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) timing based on one or more associated GL-PUSCH frequency locations;

[0022] Figure 8 is a resource allocation diagram of an example of dynamic GL-PUSCH resource allocation and its associated HARQ-ACK timing based on one or more GL-PUSCH frequency locations;

[0023] Fig. 9 are timing and transmission diagrams illustrating examples of repetition of signals transmitted using different beams;

[0024] Fig.10 are timing and transmission diagrams showing examples of transmission of simultaneous beams;

[0025] Fig.11 is a format diagram showing an example of an independent format of GL-PUSCH;

[0026] Fig.12is a format diagram showing an example of a control and data-only format for GL-PUSCH transmission;

[0027] Fig.13 is a timing diagram illustrating an example of a GL-PUSCH interference scenario between different formats;

[0028] Fig.14 is a timing diagram showing an example of a dedicated subcarrier for a GL-PUSCH preamble;

[0029] Fig.15 is a format diagram and a timing diagram showing an example of UL grant-free transmission;

[0030] Fig.16 is a flow chart illustrating an example process for performing UL grant-free transmission using a preamble;

[0031] Fig.17 is a format diagram and a timing diagram showing another example of UL grant-free transmission;

[0032] Fig.18 is a format diagram and timing diagram illustrating an example of a UL grant-free transmission with no gaps between portions of the transmission;

[0033] Fig.19 are format diagrams and timing diagrams showing examples of UL grant-free transmissions with no gaps between portions of the transmission; and

[0034] Fig. 20 is a flow chart illustrating an example of a multi-part transmission process with acknowledgement and power control. DETAILED DESCRIPTION

[0035] Figure 1A 1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 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 discrete Fourier transform spread orthogonal frequency division multiplexing (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0036] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. As examples, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to send 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 phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, 102d may be interchangeably referred to as a UE.

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

[0038] 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), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send 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 licensed spectrum, unlicensed spectrum, or a combination of licensed spectrum and unlicensed spectrum. A cell may provide coverage of wireless services for a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Thus, in one example, the base station 114a may include three transceivers, one for each cell sector. In the example, 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 send and / or receive signals in a desired spatial direction.

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

[0040] More specifically, as described above, the communication 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, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116. 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 ​​Uplink (UL) Packet Access (HSUPA).

[0041] In an example, 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).

[0042] In an example, 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).

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

[0044] In other examples, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 Evolution-Data / Evolution-Data-Optimized (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), etc.

[0045] For example, Figure 1AThe base station 114b in the example may be a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In one example, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an example, 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 another example, 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 a femtocell. Figure 1A As shown, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

[0046] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more WTRUs 102a, 102b, 102c, 102d. Data may have different quality of service (QoS) requirements, such as different throughput requirements, delay requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Although not described in detail in the specification, the RAN 104 / 113 may be configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, delay requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, Internet connectivity, video distribution, etc., and / or perform advanced security functions, such as user authentication. Figure 1A Although not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0047] 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). 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), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0048] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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 via different wireless links). Figure 1A The illustrated WTRU 102c 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.

[0049] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keyboard 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. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0050] 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 associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

[0052] Although the transmit / receive element 122 is Figure 1B 1 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 example, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for sending and receiving wireless signals over the air interface 116.

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

[0054] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keyboard 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit, or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keyboard 126, and / or the display / touchpad 128. In addition, the processor 118 may access information and store data from any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory 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 a memory that is not physically located on the WTRU 102, such as a server or a home computer (not shown).

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

[0056] 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 from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals 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.

[0057] The processor 118 may also 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 electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Module, FM radio unit, digital music player, media player, video game player module, Internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. The peripheral device 138 may include one or more sensors. The sensor 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 posture sensor, a biometric sensor, a humidity sensor, etc.

[0058] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both UL (e.g., for transmission) and DL (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 through hardware (e.g., chokes) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an example, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for both UL (e.g., for transmission) or DL ​​(e.g., for reception)) may be concurrent and / or simultaneous.

[0059] Figure 1C 1 is a system diagram showing the RAN 104 and the CN 106. As described 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.

[0060] 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 example, 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.

[0061] Each of the eNodeBs 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, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

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

[0063] 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, etc. 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.

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

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

[0066] 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 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 other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0067] Despite Figures 1A-1D WTRUs are described in the specification as wireless terminals, but in certain representative embodiments, it is contemplated that such terminals may use (eg, temporarily or permanently) a wired communication interface with a communication network.

[0068] In a representative embodiment, the other network 112 may be a WLAN.

[0069] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or other types of wired / wireless networks that transmit services to and / or outflow from the BSS. Services from STAs outside the BSS may arrive through the AP and may be delivered to the STA. Services originating from the STA to a destination outside the BSS may be sent to the AP to be delivered to various destinations. Services between STAs within the BSS may be sent through the AP, for example, where the source STA may send services to the AP, and the AP may deliver services to the destination STA. Services between STAs within the BSS may be considered and / or referred to as point-to-point services. Point-to-point services may be sent between the source and destination STAs (e.g., directly between them) using direct link establishment (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an ad-hoc communication mode.

[0070] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP may send a beacon on a fixed channel (e.g., a primary channel). The primary channel may be a fixed width (e.g., a 20 megahertz (MHz) wide bandwidth) or a width dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA 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 an 802.11 system. For CSMA / CA, a STA (e.g., each 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.

[0071] A high throughput (HT) STA may communicate using a 40 MHz wide channel, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0072] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing respectively. The stream can be mapped to two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be sent to the media access control (MAC).

[0073] 802.11af and 802.11ah support operating modes below 1 gigahertz (GHz). The channel operating bandwidth and carrier used in 802.11af and 802.11ah are reduced relative to the channel operating bandwidth and carrier used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz and 20MHz bandwidths in the TV White Space Band (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah can support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices can have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain and / or limited bandwidths. MTC devices can include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0074] A WLAN system that can support multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah, including channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by the STA in all STAs operating in the BSS, which supports the minimum bandwidth operating mode. In the example of 802.11ah, for STAs (e.g., MTC type devices) that support (e.g., only support) 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only 1MHz operating mode) is sending to the AP, even if most of the band remains idle and may be available, the entire available band may be considered busy.

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

[0076] Figure 1D1 is a system diagram showing the RAN 113 and the CN 115. As described above, the RAN 113 may employ 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.

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

[0078] The WTRUs 102a, 102b, 102c may communicate with the gNB 180a, 180b, 180c using transmissions associated with the scalable parameter configuration. For example, the OFDM symbol spacing and / or the 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 the gNB 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths, for example, containing different numbers of OFDM symbols and / or with continuously varying absolute time lengths.

[0079] 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 a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNBs 180a, 180b, 180c while also communicating / connecting with another RAN, such as an eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may serve as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0080] 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 UL and / or DL, support of network slicing, interworking between DC, NR, and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0081] Figure 1DThe CN 115 shown in FIG. 1 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although each of the aforementioned elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0082] The AMF 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 serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, termination of non-access stratum (NAS) signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of service being utilized by the WTRU 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 MTC access, and / or the like. The AMF 182a, 182b may provide a control plane function for switching between the RAN 113 and other RANs (not shown) employing other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0083] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0084] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the 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 DL packets, providing mobility anchoring, etc.

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

[0086] Given that Figures 1A-1D as well as Figures 1A-1D In accordance with the corresponding description of the present invention, one or more or all of the functions described herein with respect to one or more of the following may be performed by one or more simulation devices (not shown): WTRU 102a-d, base station 114aB, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182aB, UPF 184aB, SMF183aB, DN 185aB, and / or any other device described herein. The simulation device may be one or more devices configured to simulate one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0087] 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, one or more simulation devices can perform 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. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. A simulation device can be directly coupled to another device for the purpose of testing and / or can perform testing using over-the-air wireless communications.

[0088] One or more simulation devices may perform one or more (including all) functions, rather than being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device may be used in a test scenario in a test lab and / or a non-deployed (e.g., testing) wired and / or wireless communication network to enable testing of one or more components. One or more simulation devices may be test devices. Direct RF coupling and / or wireless communication via RF circuits (e.g., which may include one or more antennas) may be used by the simulation device to send and / or receive data.

[0089] Multiple access (MA) is a scheme whereby multiple users (eg, multiple WTRUs) gain access to and use resources simultaneously that are monitored and controlled by an eNodeB. For example, OFDMA uses several carriers that carry data independently of each other and do not interfere with each other.

[0090] In LTE, uplink access may be enabled through a contention-free procedure. The WTRU is configured to initiate the access procedure using a specific physical uplink control channel (PUCCH) resource. In the absence of a scheduled scheduling request (SR) resource, the WTRU may initiate the access procedure through a random access channel (RACH) procedure.

[0091] Figure 2is a timing diagram of an example SR procedure in LTE. As shown in the example in timing diagram 200, the procedure for contention-free uplink access in LTE may assume an SR interval of 10 milliseconds (ms). The SR procedure for contention-free uplink access may be summarized in the following main operations. The WTRU may notice the arrival of uplink data at the WTRU's uplink buffer (step 230). The WTRU may then wait for a subframe with an SR transmission opportunity (1-9 ms) and send an SR using dedicated resources on an uplink control channel (e.g., PUCCH) during the SR transmission opportunity (step 240). The SR transmission opportunity of step S240 is earlier in time than the SR transmission opportunity of step 280 and may be the first available SR transmission opportunity after the arrival of uplink data on the WTRU's uplink buffer (step 230). Upon receiving the SR, the eNodeB issues an uplink grant to the WTRU for physical uplink shared channel (PUSCH) transmission (step 250), which may be issued during a regular subframe. After receiving the grant, the WTRU may send uplink data on the PUSCH (step 260). If needed, the WTRU may also send its buffer status report (BSR) in the same subframe (step 260). Based on the received BSR, the eNodeB may schedule resources for further PUSCH transmissions. At a later time, the uplink data sent by the WTRU may be received by the eNodeB and may be available at the eNodeB (step 270).

[0092] As outlined, the SR procedure requires coordination and control between the WTRU and the eNode B. Assuming that the initial SR transmission on the PUCCH is successful, the completion of the SR procedure may take approximately 20 ms before the actual PUSCH transmission.

[0093] Hereinafter, uplink data transmission with uplink grant (e.g., downlink control information (DCI) for scheduling) may be referred to as DCI message, grant-based PUSCH transmission (GB-PUSCH), and uplink data transmission without uplink grant may be referred to as grant-free (GL) PUSCH (GL-PUSCH) transmission. PUSCH transmission may be used interchangeably with uplink transmission, uplink data transmission, and uplink control information transmission. Hereinafter, uplink resources that may be used for GL-PUSCH may be referred to as GL-PUSCH resources, and uplink resources that may be used for GB-PUSCH may be referred to as GB-PUSCH resources. One or more of the following may apply. In the example used here, the SR may be a contention-based SR (CB-SR), and the SR resources may be CB-SR resources, and these terms may be used interchangeably. Moreover, as used herein, the terms control portion, control channel, control channel information, and control information may be used interchangeably.

[0094] Due to the density of WTRUs in massive machine type communication (mMTC) applications, it is inefficient to employ contention-free access for each mMTC WTRU. Employing contention-free access for each mMTC WTRU requires several uplink / downlink signaling steps; thus, significantly reducing the spectral efficiency of the system. From the perspective of URLLC applications, the URLLC WTRU may have as a primary goal to send its packets with a minimum amount of delay. Therefore, the goal may prohibit the use of conventional scheduling and authorization procedures.

[0095] Considering the mMTC and URLLC use cases, there is a motivation to develop unlicensed MA procedures to enable fast and reliable access for URLLC WTRUs and to serve a large number of mMTC WTRUs with a minimal amount of control overhead.

[0096] The following example aspects are considered here: independent transmission of CB-SR, SR and GL-PUSCH, ungranted uplink transmission and hybrid automatic repeat request (HARQ) design, beam selection considerations, format of ungranted UL transmission, and ungranted access resource configuration.

[0097] The CB-SR procedure for MA is provided in the examples herein. For example, the SR may be a request for one or more resources (e.g., UL resources) that may be used for UL data transmission. The SR may be a request for grant-based resources, such as GB-PUSCH. The SR may include at least one bit. In the example, the SR may include a single bit.

[0098] CB-SR resources may be provided and / or used during a CB-SR procedure. CB-SR resources may be used simultaneously, for example, by one or more WTRUs in a group of WTRUs that may be allocated or configured with a set of CB-SR resources. Transmissions of WTRUs sending SRs on CB-SR resources may be coherently combined.

[0099] When multiple WTRUs send SRs on the same CB-SR resources, the eNodeB receiving the CB-SR resources may receive the SRs with a higher signal-to-noise ratio (SNR) than when one WTRU sends one SR on the resources. When the eNodeB receives the SR on the CB-SR resources, the eNodeB may understand that at least one WTRU in a group of WTRUs that may use the CB-SR resources may have sent the SR.

[0100] A set of at least one resource that may be used for SR (e.g., CB-SR) may be allocated and / or configured for the WTRU. A set (e.g., the same set) of at least one resource for SR (e.g., CB-SR) may be allocated and / or configured for a group of one or more WTRUs. In another example, the WTRU may select or determine a set or subset of CB-SR resources, for example, from a set of CB-SR resources that may be available in a cell. The configuration of CB-SR resources available in a cell may be broadcast by an eNodeB.

[0101] A WTRU (e.g., a WTRU that may be expected to perform an ungranted transmission) may determine at least one resource to be used for the SR. For example, the WTRU may select a resource from a set of allocated, configured, or determined resources. The WTRU may send the SR on the determined or selected SR resource.

[0102] An eNodeB receiving an SR on CB-SR resources may respond with a grant for resources (e.g., GB-PUSCH resources that may be used for data transmission). The grant may be directed to a set of WTRUs that may use the CB-SR resources, e.g., a set of WTRUs that may be configured with and / or may use the CB-SR resources.

[0103] The intended group may be indicated by a group identifier. A WTRU sending a CB-SR may expect a response with an authorization that may be expected for the group. The response may be referred to as a CB-SR response. The CB-SR response may provide authorization for resources (e.g., GB-PUSCH resources) to one or more WTRUs. A WTRU, such as the WTRU sending the CB-SR, may monitor the CB-SR response. The WTRU may monitor a CB-SR response that corresponds to (e.g., points to) the group, such as via a group identifier associated with the CB-SR sent by the WTRU.

[0104] If the WTRU receives a CB-SR response that is intended for the WTRU, a group to which it belongs, or a group associated with a CB-SR that the WTRU has sent, the WTRU may transmit on the granted resource or resources (e.g., using GB-PUSCH). The WTRU may determine that the CB-SR response is intended for the group based on the group identifier.

[0105] A WTRU in a group (e.g., a group associated with a set of SR resources) may be configured with a group identifier. A set of CB-SR resources may be associated with a group identifier. A WTRU may be configured with a group identifier that is associated with a set of CB-SR resources that it may use. The WTRU may use the configured group identifier to monitor for CB-SR responses, receive CB-SR responses, or both.

[0106] The WTRU may determine a group identifier for monitoring and / or receiving CB-SR responses, for example, based on a CB-SR resource or set of resources that the WTRU may use to transmit the CB-SR. The WTRU may use the determined group identifier to monitor CB-SR responses, receive CB-SR responses, or both.

[0107] The group identifier may be a Radio Network Temporary Identifier (RNTI), for example, a Group-RNTI (G-RNTI). It may be contemplated that a Cyclic Redundancy Check (CRC) for a control channel of the group may be masked or scrambled with the G-RNTI.

[0108] For example, a conflict may occur when more than one WTRU transmits on a granted resource such as GB-PUSCH. For example, a conflict may occur when more than one WTRU in a group may transmit an SR on a CB-SR resource and receive a granted resource (e.g., with a corresponding group identifier).

[0109] When multiple WTRUs may use the same resources, one or more of the following examples may be applied to avoid collisions and / or enable WTRU separation. In an example, different WTRUs may transmit different demodulation reference signals (DMRS), for example, when transmitting on the same resources. In another example, different WTRUs may transmit on different resources that may be associated with a resource grant (e.g., a resource grant).

[0110] For example, a WTRU may be configured with a DMRS pattern that the WTRU may use when transmitting on a granted resource that may be used by multiple WTRUs. The DMRS pattern may be configured, for example, semi-statically, such as through radio resource control (RRC) signaling. The DMRS pattern may be selected from a set of DMRS patterns. The set may be fixed or configured, for example, semi-statically, such as through RRC signaling. The set may be identified in a grant, for example, a CB-SR response grant. The WTRU may determine a DMRS pattern based on a configured or known set of patterns.

[0111] The DMRS pattern may be determined, defined, or configured based on at least one of a time / frequency position, a cyclic shift index, a scrambling sequence index, an orthogonal cover code index, and a transmission power level.

[0112] For example, the DCI for the CB-SR response may include a DMRS indicator or an indication of a set of DMRS patterns. The WTRU may determine the DMRS pattern based on the DMRS indicator or select a DMRS pattern from the set.

[0113] The WTRU can determine and / or select a DMRS mode based on at least one of the following: a DMRS indicator, a DMRS pattern set, a WTRU identifier (ID) (e.g., an International Mobile Subscriber Identity (IMSI)) and / or a configured value or ID (e.g., a cell-RNTI (C-RNTI), a resume ID, etc.).

[0114] In another example, a set of granted resources (e.g., GB-PUSCH resources) may be used. The set may be configured (e.g., semi-statically) and / or indicated in a DCI message that may be used for a CB-SR response. The WTRU may determine or select a granted resource (e.g., GB-PUSCH) from the configured and / or indicated set of resources based on at least one of the WTRU ID (e.g., IMSI) and / or a configured value or ID (e.g., C-RNTI, CV ID).

[0115] The WTRU may transmit on a determined or selected granted resource using a determined or selected DMRS pattern.In an example, the WTRU may transmit on a determined or selected GB-PUSCH using a determined or selected DMRS pattern.

[0116] The WTRU may include information in the transmission of the granted resources that may identify or further identify the WTRU, the capabilities of the WTRU, the traffic type of the WTRU, etc.

[0117] Figure 3300 is a flow chart of an example process using contention-based SR (CB-SR). As shown in flowchart 300, a WTRU using CB-SR may receive a configuration for a set of CB-SR resources and an associated group ID (G-ID) (step 310). The WTRU may then select a CB-SR resource from the set of CB-SR resources (step 320). In the example, the WTRU may make this selection randomly. In addition, the WTRU may send an SR on the selected CB-SR resource (step 330). The WTRU may monitor for a CB-SR response including the G-ID (step 340). In addition, the WTRU may continue to monitor until a CB-SR response is received or until a time period has passed (step 350). Conditional on receiving a CB-SR response, the WTRU may obtain a grant of UL resources and a DMRS set identifier (step 360). The WTRU may also determine a DMRS pattern from the identified set (step 370). In addition, the WTRU may transmit on the granted UL resources using the determined DMRS pattern (step 380).

[0118] Example procedures for independent transmission of both SR and GL-PUSCH transmissions are discussed herein. In the example, SR and GL-PUSCH transmissions may be transmitted simultaneously during independent transmission of both SR and GL-PUSCH transmissions. For example, in RRC_CONNECTED mode, the WTRU may attempt to perform independent transmission of both SR and GL-PUSCH transmissions to increase the likelihood of successful transmission and reduce the waiting time for high priority payloads. GL-PUSCH transmissions may be on a contention-based basis, where multiple WTRUs attempt to transmit using the same resources.

[0119] The GL-PUSCH transmission may contain a BSR or another form of indication of the WTRU buffer status to indicate whether a subsequent PUSCH transmission may follow. The indication of the buffer status may be explicit or implicit. Implicit indication may be achieved, for example, through specific use of DMRS, use of certain cyclic shifts, etc.

[0120] Depending on the WTRU configuration of the resources used for transmission of the Scheduling Request Indicator (SRI), the independent transmissions of SR and PUSCH may be simultaneous or offset in time.

[0121] Figure 4A and 4B is a timing diagram of an example SR process. Figure 4A and 4B An exemplary timeline of SR and PUSCH transmissions is shown. Figure 4AAn example of time-offset independent transmission of SR and PUSCH is shown. As shown in the timing diagram 400, the WTRU may determine the arrival of uplink data at the physical layer (step 430). The WTRU may then send a PUSCH (step 440). In addition, the WTRU may wait for a subframe with an SR transmission opportunity and send an SR during the SR transmission opportunity (step 450). Upon receiving the SR, the eNodeB may issue an uplink grant for PUSCH transmission to the WTRU (step 460), which may be issued during a regular subframe. After receiving the grant, the WTRU may send uplink data on a subsequent PUSCH transmission (step 470). In addition, the WTRU may be provided with a subframe with an additional SR transmission opportunity (step 480).

[0122] Figure 4B An example of simultaneous independent transmission of SR and PUSCH transmissions is shown. Figure 4B As shown, the WTRU may determine the arrival of uplink data at the physical layer (step 435). The WTRU may then send a SR transmission and a PUSCH transmission simultaneously during the SR transmission opportunity (step 445). Upon receiving the SR, the eNodeB may issue an uplink grant to the WTRU for a PUSCH transmission (step 465), which may be issued during a regular subframe. After receiving the grant, the WTRU may send additional uplink data on a subsequent PUSCH transmission (step 475). In addition, the WTRU may be provided with a subframe with an additional SR transmission opportunity (step 485).

[0123] like Figure 4A As shown in the example of FIG, the PUSCH transmission of step 440 may occur before the SR transmission of step 450. In contrast, in Figure 4B In the example of FIG. 4 , the WTRU may send both SR and PUSCH transmissions simultaneously (step 445 ).

[0124] exist Figure 4B In another example shown, the WTRU may defer a PUSCH transmission for at least one transmission cycle to avoid splitting its power. For example, the WTRU may send an SR without a PUSCH and then send a subsequent PUSCH transmission in a later transmission cycle (step 475). In this way, the WTRU may avoid splitting its power between the SR transmission and the PUSCH transmission.

[0125] The dynamic determination of GL-PUSCH resources may be performed during independent transmissions of both SR and GL-PUSCH transmissions. For example, the WTRU may dynamically determine the size and location of the PUSCH resources through layer 1 (L1) control signaling. The L1 control signaling may be WTRU specific or may be for a group of WTRUs. In the case of a group of WTRUs, the size of the resources may be defined based on the number of WTRUs and the mission importance or quality of service of the group. The defined set of resources may be permanent or valid for a specific time period (e.g., based on a validity timer).

[0126] In a carrier aggregation system, the defined resource sets may or may not be on the same component carrier. Alternatively, to reduce the possibility of conflict, the WTRU may be configured to use two resource sets defined on each component carrier. The resource sets on each component carrier may be similar in size and location in the resource grid. The WTRU may explicitly or implicitly determine information about the resource sets on the secondary component carrier from the defined resource sets for the primary component carrier.

[0127] The WTRU behavior in response to the success or failure of an independent transmission may be determined during the independent transmission of both the SR and the GL-PUSCH transmission. For example, the WTRU may take different steps to proceed depending on the success of each transmission. If the eNodeB correctly decodes both the SR and the GL-PUSCH transmission, the eNodeB may process the received payload on the GL-PUSCH and, in response to the received SR, it may issue an uplink grant for a subsequent PUSCH transmission by the WTRU.

[0128] An uplink grant may be considered valid for a predetermined number of transmission events. In an example, the WTRU may be configured with an expiration window length, beyond which the WTRU should not use the uplink grant for uplink transmissions. In another example, upon receiving an uplink grant, the WTRU may use the uplink grant for a new subsequent first transmission or a retransmission. In another example, in a subsequent transmission, the WTRU may indicate whether its uplink grant needs to be updated or terminated in advance in the case of an expiration window.

[0129] In another example, the eNodeB may correctly decode the GL-PUSCH transmission and may not be able to decode the SR. In this case, if the GL-PUSCH transmission contains a BSR or another form of indication of the WTRU buffer status, the eNodeB may determine whether the WTRU requires further uplink grants and send an uplink grant accordingly.

[0130] In addition, assuming that the transmission interval n SR and n GL-PUSCHWTRU transmissions for SR and GL-PUSCH transmissions in the event n=max(n SR ,n GL-PUSCH )+k receives an UL grant or HARQ feedback, the WTRU may initiate a RACH procedure. If the eNodeB decodes the SR correctly and fails to decode the GL-PUSCH transmission, it may issue an UL grant for the GB-PUSCH transmission.

[0131] An example of a GL uplink transmission and HARQ design is provided herein. In an example, a WTRU may send an uplink transmission without an uplink grant. In an example, an uplink grant may be dynamically signaled in each transmission time interval (TTI). For example, a WTRU may send uplink data, such as a PUSCH, in an uplink resource without scheduling.

[0132] An example of GL-PUSCH resource configuration for grant-free UL transmission is provided herein. In an example, a WTRU may send GL-PUSCH in one or more uplink resources that may be configured, determined and / or used for GL-PUSCH transmission.

[0133] The uplink resources may include at least one of a subframe, a radio frame, a physical resource block (PRB), a PRB pair, a DMRS cyclic shift index, a resource element, a symbol, a subcarrier, a tone, etc. GL-PUSCH and / or GB-PUSCH resources may be determined, defined, used and / or configured as an uplink resource set. In an example, the GL-PUSCH and / or GB-PUSCH resources may be determined as a PRB pair in one or more subframes.

[0134] The one or more uplink resources used for GL-PUSCH transmission may be a subset of the uplink resources that may be used for GB-PUSCH transmission. For example, a subset of GB-PUSCH resources may be configured or determined as GL-PUSCH resources, which may be used for GL-PUSCH transmission or GB-PUSCH transmission. In another example, the WTRU may send a GL-PUSCH transmission in a GL-PUSCH resource within the configured or determined GL-PUSCH resources. In another example, a subset of GB-PUSCH resources that may be used for GL-PUSCH resources may be determined based on at least one of the following: a higher layer configuration; a dynamic indication in a related DCI message; a function of one or more of system parameters, including a physical cell ID, a subframe number, and a radio frame number; and a function of one or more of WTRU-specific parameters, including a WTRU-ID or a UE-ID (e.g., IMSI, System Architecture Evolution (SAE)-Temporary Mobile Subscriber Identity (TMSI) (s-TMSI), C-RNTI, etc.).

[0135] In another example, the WTRU may monitor or receive an associated DCI message for GB-PUSCH resource determination or configuration at a known time location (e.g., a subframe before UL data is sent). For example, the WTRU may monitor in subframe nk for an associated DCI message for GB-PUSCH resource determination in subframe n, where n and k may each be a positive integer. The associated DCI message for GB-PUSCH resource determination or configuration may include at least one of: a subset of PRB pairs, one or more DMRS cyclic shift indices, one or more symbols, etc.

[0136] In an example, one or more frequency resources may be used for GL-PUSCH transmission, and the location of the one or more frequency resources may be determined based on a time index. The time index may include, for example, a subframe number, a TTI number, etc. Therefore, one or more of the following examples may apply.

[0137] In an example, one or more subbands may be used, determined, and / or configured for GL-PUSCH transmission such that a subband may be a continuous one or more PRBs (or PRB pairs) in a subframe. In another example, the number of subbands may be determined based on the system bandwidth. In another example, the number of PRBs (or PRB pairs) of a subband may be determined based on the system bandwidth. In another example, an index may be used for a subband, and the subband index may be determined as an increasing order starting from the lowest PRB index.

[0138] In another example, a subset of subband indices may be used to indicate one or more frequency resources for GL-PUSCH transmission. The subset of subband indices may be determined based on a subframe number, a system frame number (SFN) number, or both. Furthermore, the subset of subband indices may be different from one subframe to another.

[0139] In another example, in a subband set for GL-PUSCH transmission, one or more subbands may be used semi-statically, and the remaining subbands in the set may be configured, determined, and / or used using dynamic indications. For example, if Na subbands are configured for GL-PUSCH transmission, a subset of Na (e.g., Ns, where Ns≤Na) may be determined as a fallback set of GL-PUSCH resources, which may be considered as GL-PUSCH resources, and the remaining GL-PUSCH resources may be dynamically set on / off based on an indication (e.g., dynamic GL-PUSCH resources). The fallback set of GL-PUSCH resources may be used for a first type of uplink data service, such as URLLC, and the dynamic set of GL-PUSCH resources may be used for a second type of uplink data service, such as mMTC.

[0140] In another example, the presence of one or more GL-PUSCH resources in a specific time window may be indicated in a known time / frequency position. For example, a set of GL-PUSCH resources may be configured, for example, via higher layer signaling, and the presence of the configured set of GL-PUSCH resources may be indicated dynamically. For example, an indication of the presence of GL-PUSCH resources may be received and / or monitored by the WTRU in a known downlink control signal. For example, one or more downlink control resources, such as HARQ-acknowledgement (ACK) resources, may be reserved and may be used to indicate the presence of GL-PUSCH resources. If the indication exists, the WTRU may send a GL-PUSCH transmission in the GL-PUSCH resource. The presence indication may be received and / or monitored by the WTRU, which may be configured and / or determined to support GL-PUSCH transmission. The presence indication may be received and / or monitored by the WTRU, which may support a certain type of data service, such as URLLC or mMTC. The presence of GL-PUSCH resources may be implicitly indicated from the presence indication of other types of signals, such as a sounding reference signal (SRS).

[0141] In another example, a common uplink grant may be used to schedule uplink resources that may be used for GL-PUSCH transmission. For example, a common uplink grant may be used to indicate which uplink resources may be used for GL-PUSCH transmission. In an example, the common uplink may be a common DCI message. The common uplink grant may be monitored or received by the WTRU, and the WTRU may be configured or determined to use GL-PUSCH transmission. In an example, the eNodeB may send a DCI message during a fixed time window.

[0142] Figure 5 5 is an example resource allocation diagram of a dynamic indication of UL resource grant for GL-PUSCH transmission. As shown in resource diagram 500, if the WTRU has data traffic to be transmitted using GL-PUSCH resources, a WTRU receiving a common uplink grant for GL-PUSCH transmission may determine one or more GL-PUSCH resources 520, 530, 540 that are authorized for GL-PUSCH transmission. The WTRU may receive a common uplink grant for GL-PUSCH transmission in a DL control region 515 in a subframe 510. The data traffic transmitted using the GL-PUSCH resources may be a second type of data traffic, such as mMTC. The common uplink grant may be signaled, sent and / or carried in a DCI message that may be monitored by the WTRU in a common search space. The DCI message may be located in the DL control region 515. The common search space may be monitored by the WTRU, and the WTRU may be configured or determined to use GL-PUSCH transmission. In the example, the DCI message may be a common DCI message. In another example, the DCI message may include a subset of the GL-PUSCH resource set.

[0143] In an example, if the WTRU successfully receives a DCI message with an indication of the presence of at least one subset of a set of GL-PUSCH resources, the WTRU may select one or more GL-PUSCH resources from the subset. For example, the WTRU may select a GL-PUSCH frequency resource, a GL-PUSCH time resource, or both. In addition, the WTRU may select a time period within a fixed time window. The WTRU and the eNodeB may then, respectively, send and receive data on the GL-PUSCH during the selected time period using the selected GL-PUSCH resources.

[0144] In an example, the WTRU may select the GL-PUSCH frequency resource based on a random determination. In another example, the WTRU may determine the selection of the GL-PUSCH frequency resource based on the WTRU-ID.

[0145] In another example, the WTRU may select the time period based on a random determination. In another example, the WTRU may determine the selection of the time period based on the WTRU-ID.

[0146] An example of resource sharing between GL-PUSCH and GB-PUSCH is provided herein. In the example, for example, a WTRU may use one or more GL-PUSCH resources for GB-PUSCH transmissions. For example, one or more GL-PUSCH resources may be configured by an eNodeB, and the configured one or more GL-PUSCH resources may be scheduled for GB-PUSCH transmissions. In this case, GL-PUSCH resources and GB-PUSCH resources may conflict in the same resources, which may result in performance degradation.

[0147] In another example where such performance degradation may be reduced, muting of resource elements (REs) of GB-PUSCH for dynamically configurable GL-PUSCH resources may be used. For example, if the GL-PUSCH resources are inactive, the WTRU may send GB-PUSCH using scheduling resources that may conflict with the GL-PUSCH resources. If the GL-PUSCH resources are active, the WTRU may mute the GB-PUSCH resources that may conflict with the GL-PUSCH resources (e.g., puncture the GB-PUSCH resources or rate match around the GB-PUSCH resources). GL-PUSCH resources for which the WTRU receives an indication of presence may be referred to as active GL-PUSCH resources, and GL-PUSCH resources for which the WTRU does not receive an indication of presence may be referred to as inactive GL-PUSCH for a time unit. A time unit may include at least one of several types of time units, such as a time slot, a set of time slots, a subframe, a set of subframes, a TTI, a radio frame, and the like.

[0148] In an example case, the presence of GL-PUSCH resources may be indicated for a time unit, where a time unit may include at least one of a time slot, a set of time slots, a subframe, a set of subframes, a TTI, a radio frame. The number of time slots, subframes and / or TTIs of a time unit may be configured in a cell-specific or WTRU-specific manner.

[0149] In another example, the presence of GL-PUSCH resources may indicate a subset of GL-PUSCH resources that are activated for the associated time unit. The WTRU may puncture or rate match around scheduled GB-PUSCH resources that may conflict only with active GL-PUSCH resources. The WTRU may send GB-PUSCH transmissions on GB-PUSCH resources that may conflict with inactive GL-PUSCH resources.

[0150] In another example, the WTRU may monitor for common DCI messages that may indicate the presence of GL-PUSCH resources even though the WTRU may not be configured for GL-PUSCH transmissions. Common DCI messages may be monitored in a common search space with an RNTI that may be used for GL-PUSCH presence indication, such as a GL-RNTI.

[0151] In another example, the WTRU may receive an existence indication in a DCI message for a GB-PUSCH transmission. For example, the WTRU may receive a DCI message for a GB-PUSCH transmission, and the DCI message may include an existence indication of GL-PUSCH resources. One or more GL-PUSCH resource sets may be configured, and at least one of the configured GL-PUSCH resource sets may be indicated as an active GL-PUSCH resource in the DCI message.

[0152] In another example, the state (e.g., active or inactive) of the GL-PUSCH resource may be implicitly or explicitly indicated. For example, the state (e.g., active or inactive) of the GL-PUSCH resource may be implicitly determined based on one or more system parameters, which may include at least one of a cell ID, a subframe number, a time slot number, a radio frame number, and a parameter configuration (e.g., a subcarrier spacing, a cyclic prefix (CP) length, etc.). The state (e.g., active or inactive) of the GL-PUSCH resource may be explicitly indicated in a DCI message.

[0153] In another example, if the GB-PUSCH resource has a lower priority than the GL-PUSCH resource, the GB-PUSCH resource that may conflict with the active GL-PUSCH resource may be punctured or rate matched around the GB-PUSCH resource. For example, the data RE of the GB-PUSCH resource may have a higher priority than the data RE of the GL-PUSCH resource, and the data RE of the GB-PUSCH resource may have a lower priority than the reference signal of the GL-PUSCH resource. Therefore, the GB-PUSCH data RE may be punctured or rate matched around the reference signal of the active GL-PUSCH resource.

[0154] In addition, if the GB-PUSCH data RE collides with one or more higher priority GL-PUSCH REs that may include at least one of DMRS and uplink control information (UCI), the GB-PUSCH data RE may be muted (e.g., puncturing the GB-PUSCH data RE or rate matching around the GB-PUSCH data RE). Regarding DMRS, the DMRS pattern (e.g., time / frequency position) of the GB-PUSCH may be different from the DMRS pattern of the GL-PUSCH. Regarding UCI, the GL-PUSCH may include control information that may be a higher priority than the GL-PUSCH data RE.

[0155] In an example solution, a listen before talk (LBT) technique may be a monitoring technique used in radio communications whereby a radio transmitter first senses its radio environment before it starts transmitting. LBT techniques may be used for GL-PUSCH transmissions to reduce conflicts between GL-PUSCH and GB-PUSCH. For example, a WTRU may be required to check or sense the channel's use of GL-PUSCH resources before it may send GL-PUSCH on the configured GL-PUSCH resources.

[0156] GL-PUSCH transmission with LBT may be referred to as Type-1 GL-PUSCH, while GL-PUSCH transmission without LBT may be referred to as Type-2 GL-PUSCH.

[0157] The WTRU may be configured with a Type 1 GL-PUSCH or a Type 2 GL-PUSCH. The Type 1 GL-PUSCH or the Type 2 GL-PUSCH may be determined based on at least one of a WTRU-specific configuration (e.g., using a WTRU-specific RRC), a cell-specific configuration (e.g., using a broadcast channel), and / or a resource-specific configuration (e.g., a PRB level).

[0158] The first one or more symbols in the GL-PUSCH resource may be used to sense channel usage (e.g., channel sensing) and / or switch from sensing the channel to performing a GL-PUSCH transmission. For example, during sensing channel usage, the WTRU may measure the signal strength in the GL-PUSCH resource and if the signal strength is above a predetermined threshold, the WTRU may drop the GL-PUSCH transmission. Otherwise, the WTRU may send a GL-PUSCH transmission.

[0159] Additionally or alternatively, the WTRU may perform channel sensing at a per PRB level and any detected unused PRB within the GL-PUSCH resource may be used for GL-PUSCH transmission. Additionally or alternatively, the WTRU may perform channel sensing at a per subframe level and if the signal strength measured in a GL-PUSCH resource (or GL-PUSCH resources) is above a predetermined threshold, the WTRU may drop the GL-PUSCH transmission and wait until the next GL-PUSCH resource is available.

[0160] In another example solution, one or more orthogonal reference signals may be used between GL-PUSCH and GB-PUSCH. For example, a first set of orthogonal reference signals may be reserved, configured, or allocated for GL-PUSCH transmission, and a second set of orthogonal reference signals may be used for GB-PUSCH transmission, wherein the first set of orthogonal reference signals and the second set of orthogonal reference signals may be mutually exclusive.

[0161] In an example, an orthogonal reference signal set may be used in a cell. In addition, a subset of the orthogonal reference signal set may be configured for GL-PUSCH transmission.

[0162] In another example, the WTRU may determine one or more orthogonal reference signals within a configured subset of orthogonal reference signals for GL-PUSCH transmission. For example, the one or more orthogonal reference signals may be determined based on at least one of a WTRU parameter (e.g., WTRU-ID), a cell-specific parameter (e.g., cell ID), and a GL-PUSCH resource index.

[0163] In another example solution, the GB-PUSCH structure can be adjusted according to the PUSCH resource type. The PUSCH resource type may include, for example, a GB-PUSCH resource type or a GL-PUSCH resource type. For example, one or more GB-PUSCH types may be used, and each GB-PUSCH type may have a different resource structure or GB-PUSCH structure based on the resource type on which the GB-PUSCH may be transmitted. For example, a first GB-PUSCH type (e.g., a first GB-PUSCH structure) may include only data resources, and a second GB-PUSCH type (e.g., a second GB-PUSCH structure) may include silent RE resources, so that the first GB-PUSCH type may be used for PRBs that may not be configured as GL-PUSCH resources, and the second GB-PUSCH type may be used for PRBs that may be configured as GL-PUSCH resources. The silent REs in the second GB-PUSCH type may be located on REs of preambles and / or control resources used for GL-PUSCH transmission.

[0164] Figure 6 600 is a resource allocation diagram of examples of different GB-PUSCH types according to PUSCH resource types. As shown in the example in resource diagram 600, a first GB-PUSCH type 610 for transmission on GB-PUSCH resources may include only data resources, and a second GB-PUSCH type 620 for transmission on GL-PUSCH resources may include silent RE resources 625. The data resources may include at least one of data REs and reference signal REs. The silent resources may be located on REs for preambles and control information. For example, the silent RE resources 625 of the second GB-PUSCH type 620 may be located on REs for preambles 633 and control information 635 about GL-PUSCH resource types 630.

[0165] An example of HARQ operation for ungranted UL transmission is provided herein. In the example, for a GL-PUSCH transmission, the WTRU may monitor or receive an associated HARQ-ACK (e.g., ACK, negative ACK (NACK), and / or discontinuous transmission (DTX)). The associated HARQ-ACK for the GL-PUSCH transmission may be sent via a DL HARQ-ACK channel, where the DL HARQ-ACK channel may be at least one of: a HARQ-ACK physical channel that may be used only for HARQ-ACK transmissions, a DCI message that may carry one or more HARQ-ACKs for one or more GL-PUSCH transmissions, and / or a type of HARQ-ACK that may be determined based on an uplink data traffic type (e.g., a HARQ-ACK physical channel or a common DCI message).

[0166] In an example, the HARQ-ACK physical channel may be used only for HARQ-ACK transmissions. The HARQ-ACK physical channel may be configured with a HARQ-ACK resource set, and the HARQ-ACK resource used for GL-PUSCH transmission may be determined based on at least one of the time and / or frequency resources of the GL-PUSCH transmission, the WTRU-ID, and / or the subframe (and / or radio frame) number.

[0167] In another example, the DCI message may carry one or more HARQ-ACKs for one or more GL-PUSCH transmissions. A certain RNTI may be used for the DCI message, where the RNTI may be determined based on at least one of the time and / or frequency resource, WTRU-ID, and / or subframe (and / or radio frame) number of the GL-PUSCH transmission. The DCI message may be monitored or received in the downlink control channel region.

[0168] In another example, the type of the HARQ-ACK channel (e.g., a HARQ-ACK physical channel or a common DCI message) can be determined based on the uplink data service type. For example, a first HARQ-ACK channel (e.g., a HARQ-ACK physical channel) can be used for a first uplink data service type (e.g., URLLC), and a second HARQ-ACK channel (e.g., a common DCI message) can be used for a second uplink data service type (e.g., mMTC).

[0169] Figure 7 700 is an example resource allocation diagram of HARQ-ACK timing based on one or more associated GL-PUSCH frequency locations. In the example shown in resource diagram 700, the time location of the HARQ-ACK transmission for the GL-PUSCH transmission may be determined based on the frequency location of the GL-PUSCH resources used. For example, the WTRU may send a GL-PUSCH transmission in subframe n. In addition, the WTRU may assume, receive and / or monitor an associated HARQ-ACK transmission in subframe n+k, where k may be determined based on the frequency location of the GL-PUSCH transmission.

[0170] like Figure 7 As shown, the WTRU may send GL-PUSCH transmissions 720, 730, 740 during subframe 710. The eNodeB may similarly receive the GL-PUSCH transmissions 720, 730, 740. The timing position of the HARQ-ACK associated with each GL-PUSCH transmission may be determined by the frequency position of each GL-PUSCH transmission. For example, the HARQ-ACK associated with the GL-PUSCH transmission 720 may be sent by the eNodeB and received by the WTRU in the control region 755 of subframe 750 based on the frequency position of the GL-PUSCH transmission 720. In addition, the HARQ-ACK associated with the GL-PUSCH transmission 730 can be sent by the eNodeB and received by the WTRU in the control region 765 of the subframe 760 based on the frequency position of the GL-PUSCH transmission 730, and the HARQ-ACK associated with the GL-PUSCH transmission 740 can be sent by the eNodeB and received by the WTRU in the control region 795 of the subframe 790 based on the frequency position of the GL-PUSCH transmission 740.

[0171] As another example, the WTRU may use the GL-PUSCH frequency resources to send GL-PUSCH transmissions 720, 730, 740 during the subframe 710. The WTRU may then determine a time location for receiving a HARQ-ACK associated with the GL-PUSCH based on the GL-PUSCH frequency resources used to send the GL-PUSCH transmissions 720, 730, 740. The WTRU may then monitor for reception of the HARQ-ACK during the determined time location. In an example, the determination of the time location may be based on a GL-PUSCH resource index.

[0172] In an example, if more than one GL-PUSCH resource is used to send a GL-PUSCH transmission, the first GL-PUSCH (e.g., the GL-PUSCH resource with the lowest PRB index) may be used to determine the HARQ-ACK time position. Alternatively or additionally, the first GL-PUSCH resource index may be used to determine the HARQ-ACK time position.

[0173] In addition, if GL-PUSCH resources are configured or used in all subframes (or TTIs), k may be the same for all frequency locations of GL-PUSCH transmissions. Also, if a subset of subframes (or TTIs) contain GL-PUSCH resources, k may be different.

[0174] In another example, a time window may be used to monitor or receive a HARQ-ACK transmission associated with a GL-PUSCH transmission. For example, the WTRU may send a GL-PUSCH transmission in subframe n, and the WTRU may monitor or receive a corresponding HARQ-ACK for a time window (e.g., a HARQ-ACK time window) starting at subframe n+k1 and ending at subframe n+k2, where k1 and k2 are positive integers and satisfy k1 <k2。

[0175] In an example, k1 may be a fixed number (e.g., k1=4), and k2 may be determined based on at least one of the following. For example, k2 may be determined from a predetermined number (e.g., k2=8). In another example, k2 may be determined by higher layer signaling. In another example, k2 may be determined by the type of uplink data service. For example, if a first uplink data service (e.g., URLLC) is used, k2=k1, and if a second uplink data service (e.g., mMTC) is used, k2=8. In another example, k2 may be determined by a dynamic indication from a common DCI message, which may be used for an indication of GL-PUSCH resources.

[0176] In another example, a common DCI message may be used for one or more HARQ-ACKs and the DCI message may be monitored within a time window. An RNTI may be determined based on the time / frequency location of the GL-PUSCH transmission and the WTRU may monitor the common DCI message within the time window using the determined RNTI.

[0177] In another example, if the WTRU fails to receive a common DCI message (which may be, for example, a DCI message for an associated HARQ-ACK) within the time window, the WTRU may retransmit the GL-PUSCH transmission. The retransmission timing may be based on the last subframe index within the time window. The time position of the GL-PUSCH retransmission may be determined based on the UL data traffic type for the GL-PUSCH retransmission. For example, if the last subframe of the time window is subframe n, the WTRU may retransmit the GL-PUSCH transmission in the earliest subframe that may contain GL-PUSCH resources after subframe n+j, where j may be a positive integer and may be determined based on the UL data traffic type.

[0178] In an example, the uplink transmission power for GL-PUSCH retransmission or retransmission may be determined based on NACK or DTX. For example, if the WTRU fails to receive HARQ-ACK, the uplink transmission power may be increased by Δoffset (offset value), while if the WTRU receives NACK, the same uplink transmission power may be used. In the uplink power control formula, if the WTRU fails to receive HARQ-ACK in a time window (e.g., HARQ-ACK time window), there may be an offset value for increasing the transmission power.

[0179] In another example, the redundancy version of the GL-PUSCH transmission or retransmission may be determined based on a NACK or a DTX. For example, if the WTRU receives a DTX (e.g., the WTRU fails to receive the associated HARQ-ACK), the WTRU may use a first redundancy version of the GL-PUSCH, and if the WTRU receives a NACK, the WTRU may use a second redundancy version of the GL-PUSCH. The first redundancy version may be the same redundancy version as a previous transmission (e.g., a first transmission or an initial transmission). The second redundancy version may be a different redundancy version than the previous transmission. The second redundancy version or the redundancy version index may be known to the receiver, for example, the receiver may be an eNode B.

[0180] Figure 8A resource allocation diagram is an example of dynamic GL-PUSCH resource allocation and its associated HARQ-ACK timing based on one or more GL-PUSCH frequency locations. As shown in the example in resource diagram 800, a common DCI message can be used to indicate the presence of one or more GL-PUSCH resources in a subframe (or time slot, TTI, etc.), and the associated HARQ-ACK timing can be determined based on the frequency location of the one or more GL-PUSCH resources.

[0181] In an example, the eNodeB may send, and the WTRU may receive, a configuration of a GL-PUSCH resource set. The configuration of the GL-PUSCH resource set may include GL-PUSCH frequency resources, GL-PUSCH time resources, or both. The WTRU may then monitor for a DCI message including an indication of the presence of at least one subset of the GL-PUSCH resource set. In an example, the WTRU may monitor for the DCI message during a fixed time window. In an example, the fixed time window may be a first fixed time window. The eNodeB may send the DCI message during the fixed time window.

[0182] For example, the WTRU may receive a common uplink grant for GL-PUSCH transmission and, if the WTRU has data traffic to be sent using GL-PUSCH resources, may determine one or more GL-PUSCH resources authorized for GL-PUSCH transmission 820, 830, 840. The WTRU may receive a common uplink grant for GL-PUSCH transmission in the DL control region 815 in the subframe 810. The common uplink grant may be signaled, sent and / or carried in a DCI message, which may be monitored by the WTRU in a common search space. The DCI message may be located in the DL control region 815. The common search space may be monitored by the WTRU, and the WTRU may be configured or determined to use GL-PUSCH transmission. In an example, the DCI message may be a common DCI message. In another example, the DCI message may include a subset of a set of GL-PUSCH resources.

[0183] If the WTRU successfully receives a DCI message with an indication of the presence of at least one subset of the GL-PUSCH resource set, the WTRU may select one or more GL-PUSCH resources from the subset. For example, the WTRU may select a GL-PUSCH frequency resource, a GL-PUSCH time resource, or both. In addition, the WTRU may select a time period within a fixed time window. In an example, the fixed time window may be a second fixed time window. In another example, the first fixed time window may be different from the second fixed time window. In another example, the first fixed time window may be the same as the second fixed time window. The WTRU and the eNodeB may then, respectively, send and receive data on the GL-PUSCH using the selected GL-PUSCH resources during the selected time period.

[0184] In an example, the WTRU may select the GL-PUSCH frequency resource based on a random determination. In another example, the WTRU may determine the selection of the GL-PUSCH frequency resource based on the WTRU-ID.

[0185] In another example, the WTRU may select the time period based on a random determination. In another example, the WTRU may determine the selection of the time period based on the WTRU-ID.

[0186] As another example, the WTRU may send GL-PUSCH transmissions 820, 830, 840 using the selected GL-PUSCH frequency resource during subframe 805, which may be the selected time period. The WTRU may then determine a time location for receiving a HARQ-ACK associated with the GL-PUSCH based on the selected GL-PUSCH frequency resource. The WTRU may then monitor for reception of the HARQ-ACK during the determined time location. In an example, the determination of the time location may be based on a GL-PUSCH resource index.

[0187] Thus, the timing position of the HARQ-ACK associated with each GL-PUSCH may be determined by the frequency position of each GL-PUSCH. For example, the HARQ-ACK associated with GL-PUSCH 820 may be sent by the eNodeB and received by the WTRU in the control region 855 of subframe 850 based on the frequency position of GL-PUSCH 820. In addition, the HARQ-ACK associated with GL-PUSCH 830 may be sent by the eNodeB and received by the WTRU in the control region 865 of subframe 860 based on the frequency position of GL-PUSCH 830, and the HARQ-ACK associated with GL-PUSCH 840 may be sent by the eNodeB and received by the WTRU in the control region 895 of subframe 890 based on the frequency position of GL-PUSCH 840.

[0188] The use of time-division multiplexed HARQ-ACK transmissions based on the frequency location of the GL-PUSCH resources may be configured via higher layer signaling. For example, the WTRU may be configured to use time-division multiplexed HARQ-ACK transmissions, or the WTRU may be configured to use the same time location for HARQ-ACK transmissions regardless of the frequency location or locations of the GL-PUSCH resources selected or determined by the WTRU.

[0189] The use of time-division multiplexed HARQ-ACK transmissions may be determined based on the number of GL-PUSCH resources configured via higher layer signaling. For example, if the number of GL-PUSCH resources is below a predetermined threshold, the HARQ-ACK time position may be the same for all GL-PUSCH resources. Otherwise, the HARQ-ACK time position may be multiplexed and determined based on one or more frequency positions of the GL-PUSCH resources.

[0190] Examples of beam selection considerations are provided herein. In GL-PUSCH, the WTRU may start its transmission without an uplink grant. When the WTRU has multiple transmit antennas and / or multiple transmit / receive units, it may use a precoding matrix to precode the signal before it is transmitted. Precoding may be performed in the digital domain, the analog domain, or a combination of both (hybrid digital / analog).

[0191] In an example, the precoding matrix applied to the current signal may be selected as the precoding matrix used for the last transmission prior to the current transmission. In another example, the WTRU may determine the precoding matrix to apply to the current transmission by using the last receiver beamforming matrix used to receive a downlink signal. For example, the receiver simulated beamforming matrix used to receive the last downlink transmission may be used to precode the current uplink transmission.

[0192] In another example, the WTRU may make some measurements using various signals sent in the downlink and by using these measurements, calculate the precoding matrix for uplink transmission. For example, the WTRU may use the covariance matrix of the received downlink signal as a guide for uplink beamforming for the initial GL-PUSCH transmission.

[0193] In another example, the WTRU may transmit repeatedly, i.e., transmit the same signal multiple times, where each of the multiple transmissions of the same signal may be precoded with a different precoding matrix. As an example, each transmission may be beamformed in a different direction so that at the end of the multiple transmissions, the signal may be received over a wide angular range, such as Fig. 9 as shown in the example.

[0194] Fig. 9 900 is a timing diagram and transmission diagram illustrating an example of repetition of signals transmitted using different beams. In the example shown in the timing diagram and transmission diagram 900, the transmission unit of the WTRU may be a waveform symbol (e.g., OFDM symbol, DFT-s-OFDM symbol, single carrier symbol, etc.), or may be a unit including several symbols (e.g., time slot, subframe, etc.). In the example, the signal in each transmission unit 910, 920, 930, 940 may be transmitted in a specific direction using the corresponding active beam 960, 970, 980, 990. The signal transmitted in each transmission unit may be generated from channel coded data, where the entire code block is transmitted in the transmission unit, such as one of the transmission units 910, 920, 930, 940. Alternatively, a portion of a code block may be transmitted in one transmission unit, and the entire code block may be transmitted in two or more transmission units.

[0195] In another solution, the WTRU may generate multiple simultaneous beams and may reuse the transmissions of these beams over multiple time intervals.The beams may be multiplied with an orthogonal vector, where each coefficient of the vector is applied on one transmission unit.

[0196] Fig.101000 is a timing diagram and transmission diagram showing an example of transmission of simultaneous beams. As an example shown in the timing diagram and transmission diagram 1000, the WTRU may generate two beams, where the complex coefficients used to multiply the data signal x are given by the vectors α and β, respectively. Then, the signals transmitted in two consecutive transmission units 1010, 1020 may be written as y1=1αx+1βx and y2=1αx-1βx, where the orthogonal codes [1 1] and [1 -1] have been used to multiply each of the corresponding beams 1060, 1070 over the two transmission units 1010, 1020. Other beam pairs may be multiplied with orthogonal cover codes and transmitted in subsequent transmission units (e.g., transmission units 1020, 1040). The signals transmitted within each transmission unit 1010, 1020, 1030, 1040 may be generated from channel coded data, where an entire code block is transmitted within the transmission unit. Alternatively, a portion of a code block may be sent within one transmission unit, and the entire code block may be sent within two or more transmission units. The precoding / beamforming matrix and / or orthogonal cover codes used to multiply the simultaneous beams may be configured by a central controller, such as an eNodeB or a controller within the eNodeB.

[0197] Examples of formats for ungranted UL transmissions are provided. For example, GL-PUSCH may use a standalone format, or GL-PUSCH may contain only control and data. For use cases where UL ungranted transmissions may be required, such as mMTC and / or URLLC, example mechanisms for eNodeBs to detect ungranted transmissions are provided.

[0198] A WTRU may be allowed to use UL ungranted transmissions with a pre-allocated set of time-frequency resources for GL-PUSCH transmissions. Given a potentially large number of connections and a limited number of resources, the eNodeB may pre-allocate the same set of resources to multiple WTRUs, for example based on path loss measurements reported by the WTRUs. Some UL ungranted transmissions from WTRUs pre-configured with the same set of resources may overlap, and a non-orthogonal MA (NOMA) scheme may be used to separate the various WTRU transmissions.

[0199] In an example, GL-PUSCH may use a separate format for grant-free UL transmission. The format may include a preamble field, a control field, and a data field.

[0200] Fig.11 is a format diagram showing an example of an independent format of GL-PUSCH. Fig.111100 is a format diagram showing an example of an independent format of GL-PUSCH. As shown in the format diagram 1100, the independent transmission format (which may be referred to as format 1) may include a preamble field 1110, a control channel information field 1120, and a data field 1130. The preamble field 1110 may enable the eNodeB to detect the presence of UL ungranted transmissions, and it may also enable the eNodeB to perform channel estimation. In other words, the preamble field 1110 may be used instead of a reference symbol or as a supplement to a reference symbol.

[0201] The preamble may use a sequence with good correlation properties (eg, a Golay sequence), for example, to orthogonalize the WTRU and enable channel estimation. For example, the preamble field 1110 may use a sequence with good correlation properties.

[0202] The type of preamble may be configurable during the initial connection establishment, for example, based on: the usage scenario (e.g., mMTC or URLLC) and / or the NOMA scheme employed in the system. For example, for NOMA schemes that require synchronous access (e.g., code domain NOMA), a shorter preamble may be used. Also, for NOMA schemes that may support asynchronous access (e.g., where the timing offset between WTRUs is greater than the cyclic prefix or guard interval), a longer preamble may be used.

[0203] Additionally, the preamble may also be dynamically configured by the WTRU as a function of the total number of REs pre-allocated for transmission and the packet size to be sent, e.g., the transport block size (TBS). For example, for a small TBS (where the target coding rate can be achieved with fewer REs than the pre-allocated number of REs), a longer preamble may be used, e.g., to improve detection probability and channel estimation.

[0204] The eNodeB may search for a predefined set of preambles within a pool of resources pre-allocated for UL ungranted access. Thus, the WTRU may select from a set of possible preamble lengths to reduce the complexity of the eNodeB search. For situations where the WTRU may select a preamble, the preamble configuration may be used to convey the WTRU type or other type of information or indication. An example of such an indication is whether the current transmission includes a control channel.

[0205] like Fig.11As shown, the control channel field 1130 for UL ungranted transmission is immediately adjacent to the preamble field 1110, and it may carry information including one or more of the following. For example, the control channel field 1130 may carry information about the WTRU identification, such as the WTRU ID or RNTI. In addition, the control channel field 1130 may carry information about the TBS and / or modulation and coding scheme (MCS) used for the transmission. Moreover, the control channel field 1130 may carry information about whether the current transmission is a single transmission or part of multiple packet transmissions. In addition, the control channel field 1130 may carry information about a new data indicator (NDI) configured to signal a new transmission or retransmission. In addition, the control channel field 1130 may carry information about other UL feedback information.

[0206] In an example, WTRU identification may be implemented in two stages. In an example stage, the WTRU type may be carried, for example, within the preamble 1110, where a determined or selected preamble may implicitly indicate the WTRU type or an explicit indicator may be signaled in the preamble field. In another example stage, the WTRU ID or RNTI may be carried, for example, by the control channel field 1120.

[0207] In another example format for independent transmission of ungranted UL transmission, which may be referred to as format 2, the GL-PUSCH may include control and data fields for ungranted UL transmission. For example, the GL-PUSCH may only include control and data fields for ungranted UL transmission.

[0208] Fig.12 1200 is a format diagram showing an example of a control and data only format for GL-PUSCH transmission. In the example shown in the format diagram 1200, the control and data only format may include a control channel information field 1220 and a data field 1230. In the example, when continuous transmission is required, for example, when more UL data needs to be transmitted or used, it can be used Fig.11 , so that the preamble field 1110 for the first transmission is included, and then the independent transmission format shown in Fig.12 The format in (ie, without the preamble field 1110) in which subsequent transmissions in a back-to-back UL grant-free transmission may be sent or used.

[0209] Fig.13is a timing diagram illustrating an example of a GL-PUSCH interference scenario between different formats. In the example shown in timing diagram 1300, each transmission 1320, 1330 after the first transmission 1310 may include independent WTRU identification information in the corresponding control channel field 1322, 1332, for example, to enable the eNodeB to separate overlapping transmissions from different WTRUs, one of which may use a first format and the overlapping WTRU may use a second format. Fig.13 An example scenario is shown in FIG. 1 , which shows a GL-PUSCH interference scenario between format 1 and format 2. WTRU1 may use format 2 after an initial transmission, which may be sent using format 1, and WTRU2 may use format 1 for the initial transmission and further transmissions. In the example, WTRU1 may use a first format, which may be format 1 and Fig.11 In addition, WTRU1 may use a second format, which may be Format 2 and Fig.12 1320, 1330. Thus, WTRU1 may send each transmission 1320, 1330 after the first transmission 1310 with independent WTRU identification information in the corresponding control channel fields 1322, 1332. The independent WTRU identification information may enable the eNodeB to separate overlapping transmissions from WTRU2. WTRU2 may use a first format, which may be format 1 and Fig.11 1360, 1370, 1380.

[0210] Additionally, in an example, a preamble of format 1 may use dedicated subcarriers, for example, to reduce interference between WTRUs' preambles using format 1 and to reduce interference between WTRUs' control fields using format 2. The dedicated subcarriers may be within pre-allocated resources.

[0211] Fig.14 1400 is a timing diagram showing an example of using dedicated subcarriers for GL-PUSCH preambles. As shown in timing diagram 1400, preambles 1411, 1461, 1471, 1481 may use dedicated subcarriers. However, overlapping control fields 1412, 1422, 1432, 1462, 1472, 1482 and data fields 1413, 1423, 1433, 1463, 1473, 1483 may lack dedicated subcarriers.

[0212] Examples of unauthorized access resource configuration are provided here. For example, different types of services may have different quality of service (QoS) requirements that may need to be considered. For example, URLLC services may need to be prioritized over mMTC services. Resource configuration (e.g., by an eNodeB) may take into account the QoS requirements of various service types. Resource configuration may include allocating a set of resources (e.g., PUSCH resources) for one or more service types.

[0213] As an example, a set of resources (e.g., dedicated resources) may be allocated for a service or transmission type and / or a set of resources may be made available for service or transmission type allocation. In the example, the service or transmission type may include URLLC or mMTC service or transmission. A set of resources may be allocated only for service or transmission type transmission and / or a set of resources may be made available for service or transmission type transmission. For example, the size of the resource set may be increased / decreased / reallocated based on factors such as service type, QoS and / or load. For example, based on QoS requirements, a smaller set of resources may be allocated for mMTC services than for URLLC services. For example, when the load may decrease, the resources allocated for the URLLC service may be reduced.

[0214] Conflicts for contention-based resources may be reduced by random resource selection. For example, the eNodeB may consider a resource set of K resources that may be used by a set of devices or for a type of service or transmission. In an example, the resources may be used for an mMTC device or device with an mMTC service or transmission. The device may select a subset of resources from the set of K resources. In an example, the device may need or use resources for a specific type of service or transmission. In another example, the device may select randomly. The device may select a subset of resources by utilizing a simple multiplication hash function that randomizes the starting resource, which may be part of a set of resources that may be contiguous and that the WTRU may use for its transmission. The WTRU may perform the hashing using its C-RNTI or its WTRUID (e.g., its IMSI).

[0215] In another example, the eNodeB may utilize multiple resource sets. The eNodeB may divide K resources into M sets. A subset of devices may be allowed to transmit on the sets. The sets may or may not overlap. The eNodeB may use a form of load balancing to distribute the WTRUs on different sets. The eNodeB may utilize downlink L1 / Layer 2 (L2) control signals to inform a WTRU or set of WTRUs which resource set the WTRU may utilize for transmission. In an example, the L1 / L2 control signal may be in a DCI message.

[0216] In addition to the NOMA scheme, resource configuration may also be used, for example, to provide an additional dimension of flexibility for the purpose of resource overload. In an example, the resource configuration may be a dedicated resource configuration. In another example, the NOMA scheme may be a power domain NOMA scheme.

[0217] Example procedures for UL grant-free transmission using a preamble are provided herein. For UL grant-free transmission using a preamble, mechanisms may be needed to handle potential conflicts of MA signatures of WTRUs that may be transmitting in the same time-frequency resources, for example, for WTRU power saving purposes. For example, these mechanisms may be used for the WTRU to continue UL data transmission when no conflict occurs, or to stop UL data transmission when a conflict may occur.

[0218] Fig.15 1500 is a format diagram and timing diagram illustrating an example of UL grant-free transmission. In the example shown in the format diagram and timing diagram 1500, if the eNodeB successfully decodes a valid preamble sequence 1510 received from the WTRU, the eNodeB may send a preamble ACK. Once the preamble ACK is received within the valid acknowledgement window 1520, the WTRU may continue with UL grant-free transmission for control information 1530, 1550 and / or data 1540, 1560.

[0219] Fig.16 16 is a flow chart illustrating an example process for performing UL ungranted transmission using a preamble. In the example shown in flowchart 1600, the WTRU may receive, determine and / or decode the configuration of an available preamble resource set from a DL system information message (e.g., SIB) (step 1610). The WTRU may determine the preamble resource set from the available set and / or a group ID associated with the resource set (step 1615). In an example, the WTRU may determine the preamble resource set from the available set based on the WTRU ID, WTRU category, traffic type, etc. In another example, the group ID may be G_ID. The WTRU may select a preamble sequence from the preamble resource set (step 1620) and send the preamble using the selected preamble sequence (step 1630). In an example, the WTRU may randomly select the preamble sequence. In addition, the WTRU may monitor the preamble ACK, for example, within the preamble ACK window (step 1640). If the monitoring timeout is not reached, the WTRU may continue to monitor. The WTRU may determine whether the preamble ACK is received (step 1650). In an example, the preamble ACK may correspond to a transmitted preamble and / or a preamble ACK may be received with an associated G_ID.

[0220] If the preamble ACK is not received in the ACK window, the WTRU may perform one or more of the following. The WTRU may interrupt the transmission (DTx). In addition, the WTRU may increase the preamble Tx power (step 1660). In addition, the WTRU may select a new preamble sequence from the preamble resource set associated with the same G_ID (step 1620). The WTRU may resend the unauthorized UL preamble using new parameters (step 1630). The WTRU may resend the preamble during the next transmission opportunity and / or when the maximum number of retries for the preamble transmission is reached. In an example, the maximum number of retries may be based on exceeding a count threshold on a transmission counter. In addition, the WTRU may switch to a low power or sleep mode, for example, to save power, and restart the process after a certain amount of time.

[0221] If the WTRU receives a preamble ACK within a valid ACK window, for example, a preamble ACK with a matching G_ID, and / or a preamble ACK with a preamble sequence index that matches the selected or transmitted preamble sequence, the WTRU may proceed with UL ungranted transmission of control information and / or data. The WTRU may select a MA signature from a predefined set of MA signatures (step 1670). In an example, the WTRU may select a MA signature randomly. In another example, the MA signature set may be associated with a preamble sequence. In addition, the WTRU may use the selected MA signature to perform ungranted uplink transmission of UL control information and / or data (step 1680). The WTRU may also use MA physical layer (PHY) resources for ungranted uplink transmission. The MA signature may include at least one of a codebook, an interleaver, a spreading and / or scrambling sequence, and / or one or more reference signals or symbols. In the UL control signal, the WTRU may signal its ID (e.g., WTRU_ID or RNTI), which may be used by the eNodeB, for example, to confirm subsequent data transmissions from a specific WTRU.

[0222] For ungranted transmission of preambles, one or more WTRUs associated with the same G_ID may select the same preamble sequence and a preamble collision may occur. The eNodeB may still detect the preamble correctly and may send a preamble ACK within a valid window using the G_ID and the index of the preamble sequence. The WTRU may select a MA signature from a set of MA signatures. In an example, the WTRU may randomly select a MA signature using different random seeds. In an example, by decoupling the selection of the MA signature from the selection of the preamble sequence, the probability of collision on the data portion of the transmission may be reduced while keeping the complexity of the eNodeB preamble detection process fairly low. In an example, the low complexity may be maintained due to the limited size of the preamble resource set.

[0223] In another example, the WTRU may select a preamble sequence from a set of preamble resources and select an MA signature from a set of MA signatures. In an example, the WTRU may select a preamble sequence from a random set of preamble resources. The WTRU may send a preamble using the selected preamble sequence, which may be an ungranted preamble in the example, and continue the UL control channel transmission immediately following the preamble using the selected MA signature.

[0224] Fig.17 1700 is a format diagram and timing diagram showing another example of UL grant-free transmission. In the example shown in the format diagram and timing diagram 1700, the control channel 1720 may carry information for identifying the WTRU, such as the WTRU_ID. After sending the preamble 1710 and the control channel 1720 with control information, the WTRU may then begin monitoring for a preamble ACK with a specific WTRU identifier during the ACK window 1730.

[0225] If a preamble ACK with a particular WTRU identifier is not received during the valid ACK window 1730, the WTRU may retry the ungranted UL preamble 1710 transmission (with different parameters, as described above), or may stop subsequent data transmissions, for example, to save power.

[0226] If the eNodeB correctly detects the preamble 1710 and successfully decodes the control channel 1720, the eNodeB may send a preamble ACK with a specific WTRU identifier in the downlink. In this case, the WTRU may proceed with UL ungranted transmission of data 1750, 1770, for example, using the MA sequence selected for the control channel 1720, 1740, 1760 transmission. Alternatively, the control channel 1720 may carry information to signal the index of the MA sequence selected for ungranted data transmission.

[0227] Examples of ungranted transmission acknowledgement and power control are provided herein. The WTRU may make a transmission that may be an ungranted transmission. The transmission may include one or more parts. A part of the transmission may include at least one of a preamble, a control part that may include or provide control information, and / or a data part that may include or provide data (e.g., a data payload). For example, a transmission may include Fig.11 or 12. One or more of each of the one or more part types (e.g., preamble, data, and / or control) may be included in the transmission, e.g., as Fig.13 , 14 , 15 and 17. The transmitted parts can be in any order and still be consistent with the present disclosure. For example, the order can be as follows Fig.11 or Fig.18 as shown in .

[0228] Fig.18 1800 is a format diagram and timing diagram illustrating an example of a UL grant-free transmission with no gaps between portions of the transmission. In the example shown in the format diagram and timing diagram 1800, the UL grant-free transmission may include a preamble portion 1810, followed by a data portion 1820, which may be followed by a control portion 1830. The UL grant-free transmission may have no gaps between the portions 1810, 1820, 1830. As a result, the portions 1810, 1820, 1830 may be contiguous in time.

[0229] In another example, multiple portions of a transmission that may be considered part of the same transmission or set of transmissions may be consecutive or non-consecutive in time. Fig.14 , 16 There may be time windows or time gaps between the transmissions of the portions (such as those shown in FIG. 19 ).

[0230] Fig.19 1900 is a format diagram and timing diagram illustrating an example of a UL grant-free transmission with no gaps between portions of the transmission. In the example shown in the format diagram and timing diagram 1900, the UL grant-free transmission may include a preamble portion 1910, followed by a control portion 1920, which may be followed by a gap 1930, and then a data portion 1940 after the gap. Thus, the UL grant-free transmission may have a gap between portions 1920 and 1940. As a result, portions 1920 and 1940 may not be contiguous in time.

[0231] The WTRU may send a portion of a transmission if the WTRU receives an ACK for another portion of the transmission (e.g., a previous portion of the transmission). In an example, the WTRU may send a portion of a transmission only if it receives an ACK for another portion of the transmission. Thus, a continuation portion may be sent in response to receiving an ACK for a previously transmitted portion (more specifically, the immediately preceding transmitted portion).

[0232] The control part of a transmission or control information may include at least one parameter, such as a transmission parameter related to another part of the transmission or a part of another transmission.

[0233] For example, the control information may include one or more parameters related to the data portion of the transmission (and more specifically, to a subsequent data portion of the transmission).For example, the transmission may include at least the control information and the data transmission, and optionally a preamble.

[0234] In an example, control information may be sent for data transmission or a data portion of a transmission. The control information may include at least one of: time and / or frequency resources, for example, the location and / or quantity of resources, which may be represented by a resource block (RB), a PRB set, a RE set, etc.; a transport block size (TBS); a modulation and / or coding scheme; and / or a number of layers used for transmission.

[0235] Any part of a transmission, such as a control part or a data part, may include or provide a WTRU identifier. The WTRU identifier may be a function of a WTRU ID (e.g., an IMSI or a Temporary International Mobile Subscriber Identity (TIMSI)). The WTRU identifier may be a connection identifier of the WTRU, such as its C-RNTI. The WTRU identifier may be randomly selected or determined by the WTRU from a pool of identifiers or a set of identifiers that may be configured and / or may be broadcast. The WTRU identifier may be explicitly included. For example, the WTRU identifier may be represented by an index or a plurality of bits. The WTRU identifier may be implicitly included. For example, at least a portion of a transmission portion (e.g., a CRC) may be masked or scrambled with the WTRU identifier. Thus, the WTRU may provide information representation of the WTRU explicitly or implicitly.

[0236] The WTRU may determine or select a preamble for transmission, for example, from a pool or set of preambles that may be configured. There may be separate pools or sets of preambles for a WTRU in connected mode (e.g., a WTRU with an RRC connection) and a WTRU in idle mode or not in connected mode (e.g., a WTRU without an RRC connection).

[0237] The preamble may be selected based on at least a configuration of the transmission, where the configuration may include at least one of: a number of portions in the transmission, a type of portions in the transmission, a length of one or more portions in the transmission, etc. In an example, the length of the one or more portions in the transmission may be measured in time.

[0238] One or more transmissions ACK may be provided, used, or provided and used. In an example, ACK may be provided by an eNodeB and used by a WTRU. In another example, ACK may be provided by a WTRU and used by an eNodeB.

[0239] One or more portions of a transmission may be received, for example, by the WTRU and / or acknowledged, for example, by a network node such as an eNode B. In an example, each portion of the transmission may be acknowledged individually or in a bundled form. The WTRU may receive an acknowledgement of one or more portions of a transmission that may be made by the WTRU. In an example, the WTRU may receive an acknowledgement of each of the one or more portions of a transmission that may be made by the WTRU.

[0240] For example, the WTRU may be performing a transmission of a preamble, control information, and / or data. The WTRU may receive an ACK for one or more of the preamble, control information, and / or data. ACKs and / or NACKs for different parts of a transmission may be provided together or separately.

[0241] For example, after a transmission that may include one or more transmission parts, the WTRU may monitor the reception of an ACK / NACK. The WTRU may monitor a channel (e.g., a DL control channel), or monitor a resource that may be associated in time and / or frequency with at least one part of the WTRU's transmission. The association may be associated with at least one of a time, a frequency, and / or a code of at least one part of the transmission. The WTRU may monitor a channel or resource for receiving an ACK / NACK, for example, in DL control information, for the WTRU's transmission. In an example, for a transmission of N parts, there may be N indications to indicate an ACK or NACK for each of the N parts. In an example, the N indications may be N bits. For example, the N indications may be provided by an eNodeB in one transmission. In an example, the N indications may be provided in one DCI message.

[0242] In another example, one indication may be used to indicate ACK or NACK for multiple parts. For example, there may be one indication for indicating ACK or NACK for preamble transmission. There may be one indication for indicating ACK or NACK for data part and control part. Thus, ACK may indicate that both parts were successfully received. Similarly, NACK may indicate that at least one part was not successfully received.

[0243] In another example, the WTRU may perform a transmission including a preamble, a data portion, and / or a control portion sent in an iteration. If a receiver (e.g., an eNodeB) receives a preamble, the receiver may send an ACK for the preamble. The preamble may enable the receiver to locate one or more other portions of the transmission, such as a control portion and / or a data portion. If the receiver successfully receives and / or decodes the control portion, the receiver may send an ACK for the control portion. If the receiver does not successfully receive and / or decode the control portion, it may send a NACK or not send an ACK for the control portion. If the receiver successfully receives the control portion, the receiver may be able to locate and / or decode the data portion. If the receiver successfully receives and / or decodes the data portion, the receiver may send an ACK for the data portion. If it does not successfully receive and / or decode the data portion, it may send a NACK or not send an ACK for the data portion.

[0244] A transmit power for a portion of a transmission that may be performed by the WTRU may be determined by the WTRU. In an example, a transmit power for a portion of a transmission may be determined separately and / or independently of a transmit power for another portion of the transmission. For example, a preamble power for sending a preamble may be determined separately and / or independently of a transmit power for a data portion or a control portion of the transmission. The transmit powers for the data portion and the control portion of the transmission may be determined together, separately and / or independently.

[0245] For example, the WTRU may determine the power of a transmission portion, such as a preamble power, based on measurements (e.g., path loss measurements) of a signal (e.g., a reference signal). The WTRU may determine the power of a transmission portion (e.g., a control portion) based on at least one or more parameters of the transmission that may be configured or predetermined. The WTRU may determine the power of a transmission portion (e.g., a data portion) based on at least one or more transmission parameters of the transmission that may be determined by the WTRU and / or provided, included, or sent in the control portion.

[0246] In another example, the transmission power for a first portion of a transmission may be determined based on the power for another portion of the transmission. For example, if the WTRU increases the power of one portion (e.g., the preamble portion), it may also increase the power of another portion (e.g., the control and / or data portion), and more specifically, increase the power of subsequent transmission portions. The power increase of the second portion may be a function of the power increase of the first portion.

[0247] For example, the transmission power for an ungranted transmission may depend on the time that has passed since a previous transmission that may or may not have been granted. For example, if the time that has passed since the previous transmission is less than a configurable threshold amount of time, the WTRU may set the power of the new transmission or the power of a portion of the new transmission according to a first rule. If the time that has passed since the previous transmission is greater than a configurable threshold amount of time, the WTRU may set the power for the transmission or the power of a portion of the transmission according to a second rule.

[0248] The first rule may be to perform at least one of the following. For example, the first rule may be to use a previous transmission power or a function of a previous transmission power for a power of a new transmission or a new transmission portion. In an example, the first rule may be to use a previous transmission power or a function of a previous transmission power to determine a power of a new transmission or a new transmission portion. In another example, the first rule may be to include a closed loop portion of a previous transmission when determining a power of a new transmission or a new transmission portion. In an example, the closed loop portion may include an accumulated transmit power control (TPC) command.

[0249] The second rule may be to not use previous power control information when determining the power of a new transmission or a new transmission portion. In an example, the second rule may be to not use any previous power control information when determining the power of a new transmission or a new transmission portion.

[0250] The retransmission power of a portion of a transmission that may be performed by the WTRU may be determined by the WTRU. For example, the WTRU may use ACK, lack of ACK, or NACK for a portion of a transmission to determine a power setting for a subsequent transmission or a retransmission of at least a portion of the transmission.

[0251] For example, the WTRU may make a multi-part transmission and receive an ACK for at least one part of the transmission and not receive an ACK (or receive a NACK) for at least another part of the transmission. The WTRU may retransmit the part for which an ACK was received at the same power as the original transmission. The WTRU may retransmit the part for which an ACK was not received (or received a NACK) at an increased power.

[0252] For example, the WTRU may send a 3-part transmission such as a preamble, a data portion, and a control portion. The WTRU may not receive an ACK, an ACK for one portion, an ACK for two portions, or an ACK for all three portions. For example, the WTRU may retransmit one or more portions of a transmission if at least one ACK is not received for the corresponding portion. For example, the WTRU may retransmit all portions of a transmission if at least one ACK is not received. When retransmitting, the WTRU may increase the power of the portion of the transmission for which an ACK was not received. The WTRU may not increase the power of the portion of the transmission for which an ACK was received. It should also be understood that in the examples discussed herein, not receiving an ACK and receiving a NACK may be used interchangeably.

[0253] In another example, the WTRU may send a preamble and a control portion before sending the data portion and wait for one or more ACKs. The WTRU may receive no ACK, an ACK for one portion, or an ACK for both portions. The WTRU may retransmit both portions of the transmission if an ACK is not received for at least one portion. The WTRU may increase the power for retransmitting the portion for which an ACK was not received. The WTRU may not increase the power for the portion for which an ACK was received.

[0254] If one ACK is for multiple parts, for example, a preamble and a control part, and if the WTRU does not receive an ACK, the WTRU may increase the power of one or both parts when retransmitting. For example, the WTRU may or may only increase the power of the preamble part. In another example, the WTRU may increase the power of both the preamble and the control part. When a subsequent part is sent after receiving an ACK for a previous part, the power of the subsequent part may be determined at least in part based on the power (e.g., the latest or current power) of the acknowledged (Acked) previous part. For example, when a data part is sent after receiving an ACK for the preamble and / or control part, the power of the data part may be determined at least in part based on the transmission power of the preamble and / or control part for which the ACK was received.

[0255] When a portion can be retransmitted, the portion can be modified. For example, one or more transmission parameters or characteristics of the portion can be modified. For example, when a preamble portion is retransmitted, a different preamble or different time-frequency resources can be used for transmission.

[0256] The power increase for the retransmission may be based on a power step size that may be configured. The power increase for the retransmission may be based on or according to a TPC command, for example with an ACK / NACK indication, that may be received from a network node. For example, the WTRU may send a preamble and a control portion. The WTRU may receive an ACK for the preamble and not receive an ACK for the control portion (or receive a NACK). A TPC command may also be received in the ACK for the preamble (or a NACK for the control portion) that may indicate how to increase or how much to increase the power of the control portion. When retransmitting the control portion, the WTRU may increase the power based on the received TPC command.

[0257] Fig. 20 2000, a WTRU may determine a set of transmission (Tx) parts to send (step 2010). In an example, the WTRU may determine to send a preamble part and a control part. In another example, the WTRU may determine to send a preamble part, a control part, and a data part.

[0258] The WTRU may determine the transmission power for each Tx portion (step 2015). In addition, the WTRU may transmit a set of Tx portions using the power determined for each portion (step 2020). In an example, the set may be one Tx portion. In another example, the set may be more than one Tx portion. The WTRU may then determine whether an ACK is received for at least one Tx portion in the set of Tx portions (step 2030).

[0259] If an ACK is not received for at least one Tx portion in the set, the WTRU may determine whether the expected ACK time has passed or whether the expected wait time has ended or expired (step 2050). Additionally, if the time has not expired, the WTRU may return to waiting for ACK reception (step 2030). If the time has passed, the WTRU may increase the transmit power of at least a portion of the transmission (step 2080). For example, the WTRU may increase the transmit power of the preamble. In another example, the WTRU may increase the transmit power of only the preamble. In another example, the WTRU may increase the transmit power of all portions. Furthermore, in an example, the power increase of at least a portion of the transmission may be based on a configurable power step size.

[0260] In another example, the WTRU may or may not then continue to update one or more Tx portions (step 2090). In an example, the WTRU may update the Tx portion by determining a new preamble. In another example, the WTRU may retransmit at least a portion of the transmission. In an example, the WTRU may retransmit a set of Tx portions (step 2020) using a power determined for each portion, including an increased power for at least one portion.

[0261] If an ACK is received for at least one Tx portion in the set, the process may further include determining whether an ACK is received for all Tx portions in the set (step 2040). If an ACK is not received for all Tx portions, the WTRU may increase the transmit power of at least a portion of the transmission (step 2070). In an example, the WTRU may increase the transmit power of at least a portion of the transmission for which an ACK is not received. In another example, the WTRU may increase the transmit power of at least a portion of the transmission for which a NACK is received. In another example, the power increase of at least a portion of the transmission may be based on a configurable power step size.

[0262] Similar to the example above, the WTRU may or may not then continue to update one or more Tx portions (step 2090). In addition, the WTRU may retransmit at least a portion of the transmission, similar to the example above. In yet another example, the WTRU may retransmit a set of Tx portions (step 2020) using a power determined for each portion, including an increased power for at least one portion.

[0263] If ACK is received for all Tx parts, the WTRU may determine that the transmission is successfully completed (step 2060). In addition, the WTRU may send the next Tx part or the next set of Tx parts during which Fig. 20The process shown may be repeated. In an example, the next Tx portion may be a data portion. In another example, the next Tx portion set may be a control portion and a data portion.

[0264] Although the features and elements are described above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media, such as non-transitory computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (e.g., internal hard disks and removable disks), magneto-optical media, and optical media (e.g., CD-ROM disks and digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A method for multiple access wireless communications for use in a wireless transmit / receive unit (WTRU), the method comprising: receiving configuration information indicating a set of physical channel frequency resources; receiving indication information, wherein the indication information indicates allocation of at least one subset of the set of physical channel frequency resources; determining one or more physical shared channel frequency resources and time periods from the subset of the set of physical channel frequency resources; sending data in a physical shared channel transmission using the determined one or more physical shared channel frequency resources during the determined time period; determining a time location for receiving hybrid automatic repeat request acknowledgement (HARQ-ACK) information associated with the transmitted data, wherein the determination of the time location is based on the subset of the set of physical channel frequency resources; and The HARQ-ACK information is received during the determined time location.

2. The method of claim 1 , wherein determining the one or more physical shared channel frequency resources from the subset of the set of physical channel frequency resources is based on a WTRU-ID.

3. The method of claim 1 , wherein the time period is determined based on a WTRU-ID. The method according to claim 1 , wherein the time period is within a fixed time window. The method of claim 1 , wherein the determination of the time position is further based on a physical channel resource index. The method of claim 1 , wherein control information is transmitted on the physical shared channel transmission.

7. The method of claim 1, wherein the HARQ-ACK information is received in a time slot.

8. The method of claim 1, wherein the configuration information is received via radio resource control (RRC) signaling.

9. The method according to claim 1, wherein the indication information is received via RRC signaling.

10. The method of claim 1, wherein the indication information comprises a presence indication.

11. A wireless transmit / receive unit (WTRU) for multiple access wireless communications, the WTRU comprising: transceiver; and The transceiver is operatively coupled to a processor; in: The transceiver is configured to receive configuration information indicating a set of physical channel frequency resources; The transceiver is configured to receive indication information, wherein the indication information indicates allocation of at least a subset of the set of physical channel frequency resources; The processor is configured to determine one or more physical shared channel frequency resources and time periods from the subset of the set of physical channel frequency resources; The transceiver and the processor are configured to transmit data on a physical shared channel transmission using the determined one or more physical channel frequency resources during the determined time period; The processor is configured to determine a time location for receiving hybrid automatic repeat request acknowledgement (HARQ-ACK) information associated with the transmitted data, wherein the determination of the time location is based on the subset of the set of physical channel frequency resources; and The transceiver and the processor are configured to receive the HARQ-ACK information during the determined time location.

12. The WTRU of claim 11, wherein determining the one or more physical shared channel frequency resources from the subset of the set of physical channel frequency resources is based on a WTRU-ID.

13. The WTRU of claim 11, wherein the time period is determined based on a WTRU-ID.

14. The WTRU of claim 11, wherein the time period is within a fixed time window.

15. The WTRU of claim 11, wherein the determination of the time position is further based on a physical channel resource index.

16. The WTRU of claim 11 wherein control information is transmitted on the physical shared channel transmission.

17. The WTRU of claim 11, wherein the HARQ-ACK information is received in a time slot.

18. The WTRU of claim 11, wherein the configuration information is received via radio resource control (RRC) signaling.

19. The WTRU of claim 11, wherein the indication information is received via RRC signaling.

20. The WTRU of claim 11, wherein the indication information comprises a presence indication.

Images