Timing advance and processing capability in latency reducing systems

Abstract

The present application describes timing advance and processing capability in latency reduction systems, and specifically relates to methods and devices for handling reduced available processing times in systems configured to reduce latency, such as systems using configurable transmission time intervals (TTIs) or short TTIs (sTTIs) and processing capability (PC). A wireless transmit / receive unit (WTRU) may be configured to use a PC. The WTRU may receive a TTI configuration. The WTRU may determine a PC of the WTRU. The PC may be determined based on at least one of a TTI configuration and a processing standard. The WTRU may then transmit a report of the determined PC. A report may be transmitted to the eNB. The PC may be a timeline, and the timeline may be reported as a number of time units, where the time units are at least one of a symbol, a TTI, a time sample, and a set of time samples.

Description

[0001] This application is a divisional application of the Chinese invention patent application with the application date of August 9, 2017, application number 202211679399.1, and invention name “Timing Advance and Processing Capability in Systems with Reduced Waiting Time”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Application Serial No. 62 / 373,123, filed on August 10, 2016, the contents of which are incorporated herein by reference. Background Art

[0004] Emerging applications for cellular technology, such as alarm reporting, automotive safety, factory process control, and machine type communications (MTC), may benefit from the use of low latency cellular communications. Low latency applications may find that the 1 ms transmission time interval (TTI) and associated latency that may be used, for example, in LTE-Advanced (LTE-A) systems is insufficient. Existing applications such as gaming and real-time applications (such as voice over LTE (VoLTE) and video calling / conferencing) also benefit from reduced latency, for example in terms of enhanced perceived quality of experience. Some applications may use short TTI (sTTI) to reduce latency; however, the use of sTTI reduces the available processing time. Summary of the invention

[0005] The present application describes methods and apparatus for handling reduced available processing time in a system configured to reduce latency, such as a system using a configurable transmission time interval (TTI) or short TTI (sTTI).

[0006] A wireless transmit / receive unit (WTRU) may be configured to determine one or more processing capabilities, send a processing capability (PC) indication to an eNode B (eNB) based on the determined processing capabilities, receive a PC configuration from the eNB, determine a maximum timing advance or a maximum Rx-Tx time difference based on the PC configuration and the determined processing capabilities, and limit the applied timing advance or Rx-Tx time difference to the maximum timing advance or the maximum Rx-Tx time difference for a particular TTI length. The WTRU may also be configured to measure a processing value (PV) of a processing parameter, determine a margin, which is the difference between the PV and the PC, and report the margin based on a condition. The WTRU may also perform an action based on a condition.

[0007] In one example, the WTRU may be configured to use PC. The WTRU may receive a TTI configuration. The WTRU may determine the PC of the WTRU. The PC may be determined based on at least one of: the TTI configuration and a processing criterion. The WTRU may then transmit a report on the determined PC. The report may be transmitted to the eNB. The PC may be a time axis, and the time axis may be reported as a plurality of time units, wherein the time unit is at least one of a symbol, a TTI, a time sample, and a time sample set.

[0008] In another example, the WTRU may be configured to use a configurable TTI. The WTRU may receive a TTI configuration. The WTRU may determine a PC for the configured WTRU for the TTI based on a processing criterion. The WTRU may then transmit a report about the determined PC, and the determined PC may be based on the number of symbols in the TTI or the TTI length used and / or configured. The WTRU may also determine a current processing value (PV). The report may be based on satisfying a proximity condition, suspending one or more UL transmissions, or dropping an UL transmission. The processing criterion may include, for example, the number of symbols in the TTI or the TTI length used and / or configured.

[0009] In another example, the WTRU may be configured to use sTTI. The WTRU may receive the sTTI configuration and determine the PC for the WTRU configured for the sTTI based on processing criteria. The WTRU may determine the current PV. The WTRU may report the PC proximity based on the determined PC and the determined PV, and based on meeting the proximity condition, suspend one or more UL transmissions or discard the UL transmission. In this example, the processing criteria may include, but are not limited to, the following: sTTI length, timeline, transport block (TB) size, uplink (UL) channel type, the time between the sTTI of the short physical downlink control channel (sPDCCH) and the sTTI of the UL. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals represent like elements and in which:

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

[0012] Figure 1B It is shown that according to the embodiment, Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within a communication system is shown;

[0013] Figure 1C It is shown that according to the embodiment, Figure 1AA system diagram of an example radio access network (RAN) and an example core network (CN) used within the illustrated communication system;

[0014] Figure 1D It is shown that according to the embodiment, Figure 1A A system diagram of another example RAN and another example CN used within the illustrated communication system;

[0015] Figure 2 is an example of transmit receive timing;

[0016] Figure 3 Provides examples of transmission and reception timing for applying TA;

[0017] Figure 4 Another example of applying the transmission and reception timing of TA is provided;

[0018] Figure 5 is an example of a close report;

[0019] Figure 6 is another example of proximity reporting;

[0020] Figure 7 is an example of modifying a UL transmission when a condition is met;

[0021] Figure 8 is an example of a transmission pause;

[0022] Fig. 9 is another example of a transmission pause; and

[0023] Fig.10 is an example of a transmission pause when the pause condition is met. DETAILED DESCRIPTION

[0024] Figure 1A 1 is a diagram showing an exemplary 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 use one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word discrete Fourier transform spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, and filter bank multi-carrier (FBMC), etc.

[0025] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112, although it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network components. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, any of the WTRUs 102a, 102b, 102c, 102d may be referred to as a “station” and / or “STA”, which may be configured to transmit and / or receive wireless signals, and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular 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 working in an industrial and / or automated process chain environment), consumer electronic devices, and devices working 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.

[0026] 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 facilitate access to one or more communication networks (e.g., the CN 106 / 115, the Internet 110, and / or other networks 112) by wirelessly interfacing with at least one of the WTRUs 102a, 102b, 102c, 102d. For example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an eNode B, a Home Node B, a Home eNode B, a Next Generation Node B (gNB), a New Radio (NR) Node B, a site controller, an access point (AP), a wireless router, and a transmission / reception point (TRP), etc. Although each of the base stations 114a, 114b is described as a single component, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network components.

[0027] The base station 114a may be part of the RAN 104 / 113, and the RAN may also include other base stations and / or network components (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, and the like. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies called cells (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage for a specific geographic area that is relatively fixed or may change over time. A 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 embodiment, the base station 114a may include three transceivers, that is, each transceiver corresponds to a sector of the cell. In an embodiment, the base station 114a may use multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, by using beamforming, signals may be transmitted and / or received in a desired spatial direction.

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

[0029] More specifically, as described above, the communication system 100 may be a multiple access system and may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, and SC-FDMA, among others. 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 ​​UL Packet Access (HSUPA).

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

[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using NR.

[0032] In an embodiment, 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 jointly implement LTE radio access and NR radio access (e.g., using dual connectivity (DC) principles). Thus, the air interface used 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).

[0033] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 Evolution Data-Only / 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), and GSM EDGE (GERAN), among others.

[0034] 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 use any appropriate RAT to facilitate wireless connectivity in a local area, such as a business location, a residence, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless local area network (WLAN) by implementing a radio technology such as IEEE 802.11. In an embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless personal area network (WPAN) by implementing a radio technology such as IEEE 802.15. In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell by using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, and the like). Figure 1A As shown, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114b does not need to access the Internet 110 via the CN 106 / 115.

[0035] 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 of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency 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 may perform advanced security functions such as user authentication. Although in Figure 1A Although not shown, 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 or a different RAT as the RAN 104 / 113. For example, in addition to being connected to the RAN 104 / 113 employing NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0036] The CN 106 / 115 may also act 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 network devices that use common communication protocols, such as TCP, User Datagram Protocol (UDP), and / or IP in the Transmission Control Protocol / Internet Protocol (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, where the one or more RANs may use the same RAT or a different RAT as the RAN 104 / 113.

[0037] 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, transmitters, or receivers for communicating with different wireless networks over 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.

[0038] Figure 1B is a system diagram showing an example WTRU 102. Figure 1B As shown, the WTRU 102 may include 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, a removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and 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.

[0039] 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, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 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, however it should be appreciated that the processor 118 and the transceiver 120 may also be integrated together in an electronic package or chip.

[0040] The transmit / receive component 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive component 122 may be an antenna configured to transmit and / or receive RF signals. As an example, in an embodiment, the transmit / receive component 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, the transmit / receive component 122 may be configured to transmit and / or receive RF and light signals. It should be appreciated that the transmit / receive component 122 may be configured to transmit and / or receive any combination of wireless signals.

[0041] Although in Figure 1B 102 as a single component, but the WTRU 102 may include any number of transmit / receive components 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive components 122 (e.g., multiple antennas) for transmitting and receiving radio signals over the air interface 116.

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

[0043] The processor 118 of the WTRU 102 may be coupled to the speaker / microphone 124, the keyboard 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data from these components. 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 from and store data in any suitable memory such as the non-removable memory 130 and / or the 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 storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in memories that are not physically located in the WTRU 102, such as, for example, a server or a home computer (not shown).

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

[0045] 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) related to 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) via 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 via any suitable positioning method while remaining consistent with an embodiment.

[0046] 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, Modules, frequency modulation (FM) radio units, digital music players, media players, video game console modules, Internet browsers, virtual reality and / or augmented reality (VR / AR) devices, and activity trackers, etc. Peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

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

[0048] Figure 1C 1 is a system diagram showing the RAN 104 and the CN 106 in accordance with an embodiment. As described above, the RAN 104 communicates with the WTRUs 102a, 102b, 102c by employing an E-UTRA radio technology over the air interface 116. The RAN 104 may also be in communication with the CN 106.

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

[0050] 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, user scheduling in the UL and / or DL, and the like. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

[0051] Figure 1C The illustrated CN 106 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 components is described as being part of the CN 106, it should be appreciated that any of these components may be owned and / or operated by an entity other than the CN operator.

[0052] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c 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, performing bearer activation / deactivation processing, and selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

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

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

[0055] 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, such as an IP Multimedia Subsystem (IMS) server, and the IP gateway may serve 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 that are owned and / or operated by other service providers.

[0056] Although in Figures 1A-1D The WTRU is described as a wireless terminal, however it should be appreciated that in certain typical embodiments, such a terminal may use a (eg, temporary or permanent) wired communication interface with a communication network.

[0057] In a typical implementation, the other network 112 may be a WLAN.

[0058] A WLAN using an infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may access or be connected to a distributed system (DS) or other types of wired / wireless networks that send traffic into and / or out of the BSS. Traffic originating from outside the BSS and destined for the STA may arrive through the AP and be delivered to the STA. Traffic originating from the STA and destined for a destination outside the BSS may be sent to the AP for delivery to the corresponding destination. Traffic between STAs within the BSS may be sent through the AP, for example, the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. The point-to-point traffic may be sent using a direct link establishment (DLS) between the source and destination STAs (e.g., directly between them). In some typical embodiments, the DLS may use 802.11e DLS or 802.11z channelized 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. Here, the IBSS communication mode may sometimes be referred to as an "ad-hoc" communication mode.

[0059] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP may transmit a beacon on a fixed channel (e.g., a primary channel). The primary channel may have a fixed width (e.g., a bandwidth of 20 MHz) or a width that is dynamically set with the aid of signaling. The primary channel may be a working channel of the BSS and may be used by the STA to establish a connection with the AP. In certain typical embodiments, carrier sense multiple access (CSMA / CA) with collision avoidance (e.g., in an 802.11 system) may be implemented. For CSMA / CA, STAs (e.g., each STA) including the AP may sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, the particular STA may back off. In a specified BSS, one STA (e.g., only one station) may transmit at any given time.

[0060] A high throughput (HT) STA may communicate using a 40 MHz wide channel (eg, by combining a 20 MHz wide primary channel with a 20 MHz wide adjacent or non-adjacent channel to form a 40 MHz wide channel).

[0061] Very high throughput (VHT) STA can support channels with widths of 20MHz, 40MHz, 80MHz and / or 160MHz. 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 discontinuous 80MHz channels (this combination can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data can be transmitted and passed through a segment parser, which can separate the data into two streams. Inverse fast Fourier transform (IFFT) processing and time domain processing can be performed separately on each stream. The stream can be mapped on two 80MHz channels, and the data can be transmitted by the STA performing the transmission. At the receiver of the STA performing the reception, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).

[0062] 802.11af and 802.11ah support sub-1 GHz operating modes. Compared with 802.11n and 802.11ac, the channel operating bandwidth and carrier used in 802.11af and 802.11ah are reduced, and 802.11af supports 5MHz, 10MHz and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz and 16MHz bandwidths using non-TVWS spectrum. According to a typical embodiment, 802.11ah can support meter type control / machine type communication (such as MTC devices in macro coverage areas). MTC can have certain capabilities, such as limited capabilities including support (such as only support) certain and / or limited bandwidths. MTC devices can include a battery, and the battery life of the battery is higher than a threshold (for example, for maintaining a very long battery life).

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

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

[0065] Figure 1D 1 is a system diagram showing the RAN 113 and the CN 115 according to an embodiment. 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.

[0066] 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. Each gNB 180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may use beamforming processing to transmit and / or receive signals to and / or from the gNBs 180a, 180b, 180c. Thus, for example, the gNB 180a may use multiple antennas to transmit wireless signals to the WTRU 102a and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit a plurality of component carriers (not shown) to the WTRU 102a. 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 embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and gNB 180b (and / or gNB 180c).

[0067] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameter configurations (numerology). For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may be different for different transmissions, different cells, and / or different portions of the radio transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., containing different numbers of OFDM symbols and / or varying absolute time lengths).

[0068] 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 use 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 an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect to the gNB 180a, 180b, 180c while communicating / connecting to another RAN (e.g., the eNode-B 160a, 160b, 160c). For example, the WTRU 102a, 102b, 102c may communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c in a substantially simultaneous manner by implementing the DC principle. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput to serve the WTRU 102a, 102b, 102c.

[0069] 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, user scheduling in UL and / or DL, support network slicing, implement dual connectivity, implement interworking between NR and E-UTRA, route user plane data to a user plane function (UPF) 184a, 184b, and route control plane information to an access and mobility management function (AMF) 182a, 182b, and the like. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an X2 interface.

[0070] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and may include a data network (DN) 185a, 185b. Although each of the aforementioned components is described as part of the CN 115, it should be understood that any of these components may be owned and / or operated by entities other than the CN operator.

[0071] 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 act 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 PDU sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, and mobility management, etc. The AMF 182a, 1823b may use network slicing processing to customize the CN support provided to the WTRU 102a, 102b, 102c based on the type of service used 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, and / or services for machine type communication (MTC) access, etc. The AMF 182a, 182b may provide a control plane function for switching between the RAN 113 and other RANs (not shown) using other radio technologies (e.g., LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi).

[0072] 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 may 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, and providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0073] The UPF 184a, 184b can be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N3 interface, which can provide the WTRUs 102a, 102b, 102c with access to packet-switched networks (e.g., the Internet 110) to facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b can perform other functions such as routing and forwarding packets, implementing user plane policies, supporting multi-host PDU sessions, processing user plane QoS, buffering downlink packets, and providing mobility anchor processing, etc.

[0074] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts 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 embodiment, the WTRUs 102a, 102b, 102c may be connected to a local data network (DN) 185a, 185b via an N3 interface connected to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b and through the UPF 184a, 184b.

[0075] In view of Figures 1A-1D and about Figures 1A-1D , one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU 102a-d, base station 114a-b, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein. These simulation devices may be one or more devices configured to simulate one or more or all of the functions herein. For example, these simulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[0076] The simulation device can be designed to implement one or more tests about other devices in a laboratory environment and / or an operator network environment. For example, the one or more simulation devices can perform one or more or all functions while being implemented and / or deployed as part of a wired and / or wireless communication network in whole or in part to test other devices inside the communication network. The 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. The simulation device can be directly coupled to other devices to perform the test, and / or can use over-the-air wireless communication to perform the test.

[0077] The one or more simulation devices can perform one or more functions, including all functions, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test lab and / or a test scenario of a wired and / or wireless communication network that is not deployed (e.g., tested) to implement tests on one or more components. The one or more simulation devices can be test devices. The simulation device can transmit and / or receive data using direct RF coupling and / or wireless communication with the aid of RF circuits (as an example, the circuits can include one or more antennas).

[0078] The use of WTRU and eNB in ​​the embodiments described in this application is for illustrative purposes. The methods described in this application may be performed by any device described in this application, including but not limited to WTRU, base station, AP, eNB, gNB, TRP, or any other device capable of operating in a wireless communication system.

[0079] The total end-to-end latency experienced by the WTRU may be due to one or more factors. These factors may include, but are not limited to, scheduling grant acquisition time, transmission time interval (TTI), processing time, and hybrid automatic repeat request (HARQ) round trip time (RTT).

[0080] The transmission of requests, grants, HARQ feedback and / or data may be performed at and / or according to the timing of blocks or chunks (in some embodiments, the blocks or chunks may be, for example, or correspond to subframes). These blocks or chunks (e.g., subframes) may have a fixed or known duration (e.g., 1 ms). The duration may be referred to as a TTI.

[0081] A TTI may be or may include a subframe, a plurality of subframes, a time slot, a plurality of time slots, a symbol, a plurality of symbols, and / or a plurality of time samples. A TTI may be used to represent a time that may correspond to a TTI. For example, a TTI may be or may include a time that may correspond to at least one of: a subframe (e.g., 1 ms), a plurality of subframes, a time slot (e.g., 0.5 ms), a plurality of time slots, a symbol, a plurality of symbols, a time sample (e.g., Ts), and / or a plurality of time samples. The term Ts may be used to represent a time sample and / or a time corresponding to a time sample. In the examples and embodiments described herein, time slots and / or subframes may be used as non-limiting examples of TTIs. Other examples of TTIs may be used and still conform to the examples and embodiments described herein.

[0082] After successfully or unsuccessfully receiving a transmission, for example, any device described herein may transmit feedback, such as HARQ feedback. The feedback may include a positive acknowledgement (ACK) or a negative acknowledgement (NACK), which may indicate successful or unsuccessful reception of the transmission, respectively.

[0083] There may be a time relationship between a transmission by a sender (e.g., an actual transmission or a scheduled transmission) and when a receiver or expected receiver may transmit feedback. The relationship may be a known, configured, or expected time relationship. For example, when data is or may be transmitted and / or received at time n (e.g., actually transmitted and / or received or scheduled to be transmitted and / or received), feedback (e.g., HARQ feedback) may be transmitted and / or received at time n+x, where x may be equal to kx TTI. Feedback may be used for or may correspond to data or transmission. Feedback may indicate successful or unsuccessful reception of data or transmission. In this example, k may be an integer, such as 4.

[0084] In another example, when data is or can be transmitted and / or received (e.g., actually transmitted and / or received or scheduled to be transmitted and / or received) (e.g., in a downlink (DL)) in subframe n, HARQ feedback (e.g., for or corresponding to the data) can be transmitted and / or received in subframe n+4 (e.g., in an uplink (UL)). The n+4 HARQ or feedback timing (e.g., timing relationship) can, for example, be applicable to a system using frequency division duplex (FDD). In another example, for a system using time division duplex (TDD), the HARQ timing can depend on the TDD configuration (e.g., UL / DL configuration).

[0085] For example, HARQ feedback for or corresponding to data that is or may be transmitted and / or received at time n is available at time n+(kx TTI), where k may be 4 for FDD and / or at least 4 for TDD, depending on the TDD configuration. Time n may be subframe n. Time n+(kx TTI) may be subframe n+k.

[0086] In another example, HARQ feedback for DL ​​transmission in DL TTI n may be transmitted and / or received at a UL TTI that is at least kx DL TTIs after DL TTI n. This may be the next UL TTI that is at least kx TTIs after DL TTI n.

[0087] The timeline may be a scheduling timeline and / or a feedback timeline (e.g., a HARQ timeline). The scheduling timeline may include a relationship between when a scheduling grant or allocation is transmitted or received and when corresponding data is transmitted or received. For example, for a grant or allocation received in TTI n, data may be received in TTI n+k. The k value may be, for example, 0 or 1 for DL ​​reception. The k value may be, for example, an integer, such as 4 or at least 4 for UL transmission. An example timeline relationship may be represented by TTI n→TTI n+k. Another example timeline relationship may be time n→time n+x.

[0088] The timeline may be considered a standard timeline for a first value of x or k. The timeline may be considered a shortened timeline for a second value of x or k that may be less than the first value of x or k. For example, k may be 4 for the standard timeline and 2 or 3 for the shortened timeline. The shortened timeline may have a lower latency than the standard timeline.

[0089] The WTRU may adjust its reception and / or transmission timing based on the frame timing of the received cell (e.g., the received DL frame timing). The cell may be, for example, a reference cell. The WTRU may synchronize its reception and / or transmission timing to the frame timing of the received cell.

[0090] The cell may be a primary cell (PCell), a secondary cell (SCell), or a primary SCell (PSCell), which may be used with carrier aggregation (CA) or bidirectional connectivity in some embodiments. The PCell may be a primary serving cell. The WTRU may have, for example, at least one or only one PCell. The SCell may be a secondary serving cell. The WTRU may have at least one SCell. The WTRU may aggregate the PCell with one or more SCells, or the WTRU may aggregate multiple SCells, which may, for example, increase bandwidth. The PSCell may be a primary SCell. The WTRU may have at least one PSCell. For example, the WTRU may have one PSCell per SCell group, which may belong to the same medium access control (MAC) entity. The WTRU may have at least one MAC entity. The PCell and one or more SCells may be associated with a MAC entity. The PSCell and one or more SCells may be associated with a MAC entity.

[0091] The timing of frame boundaries of frames received by the WTRU varies over time due to WTRU motion and / or other factors (e.g., oscillator drift). The WTRU may, for example, autonomously adjust its receive and / or transmit timing accordingly. For example, the WTRU may autonomously adjust its downlink receive timing and / or uplink transmit timing based on the received downlink frames of the cell, and the timing may change.

[0092] The WTRU may apply a timing advance (TA) to its UL transmission timing. The WTRU may start transmission of an UL time unit (e.g., a subframe or TTI) some amount of time (e.g., an applied TA) before the start of the corresponding DL time unit. For example, the WTRU may start transmission of UL subframe n at an applied TA before the start of the corresponding DL subframe n. The TA may be a variety of time units, such as a time sample (e.g., Ts) or an integer number of time samples (e.g., an integer number of Ts). The TA may be applied in this manner to account for signals arriving at the eNB at different times due to cell size. The TA may be used to advance or delay transmissions to account for the distance of the WTRU from the eNB and to enable transmissions from the WTRU to better align with transmissions of other WTRUs at the eNB receiver. For example, when the WTRU is close to the eNB, a small TA may be applied so that the WTRU sends its signal at a later time. In this example, as the distance of the WTRU from the eNB increases, a larger TA may be applied so that the WTRU sends its signal at an earlier time. Using the TA in this example may enable the eNB to receive signals from WTRUs at different distances at similar times.

[0093] The WTRU may receive a TA command, for example, from a cell or an eNB with which the WTRU may communicate. The TA command may be received from the eNB during a random access procedure. The TA command may be received independently of the random access procedure. The TA command may be received in a MAC control element (CE). The eNB may provide a TA command whereby UL transmissions from one or more WTRUs at or corresponding to a time or time period (e.g., a subframe or TTI) may nominally arrive at the cell simultaneously or within a receive time window. The WTRU may apply one or more received TA commands to adjust its UL timing. The TA command may provide a TA value or a TA adjustment (e.g., increase or decrease).

[0094] The WTRU may apply a TA or a TA adjustment, for example, based on a received TA command, an amount of time after receiving a TA command. The amount of time may be an integer number of TTIs (e.g., 6 TTIs) after the TTI in which the command was received. The amount of time may be fixed or configured. The WTRU may apply a TA based on the TA value it receives. The WTRU may apply a TA that is an adjusted TA (e.g., after adjusting the TA). The WTRU may adjust the TA based on the TA adjustment it receives. For example, the WTRU may adjust a previously applied TA based on the TA adjustment it receives, and the WTRU may then apply and / or use the adjusted TA. The phrases "applying a TA adjustment" and "applying a TA based on a TA adjustment" may be used interchangeably in this application. When the WTRU applies a TA, the time difference between the WTRU's receive timing and the transmit timing may be set to the applied TA. For example, it may be set exactly to the applied TA or set within an allowed tolerance of the applied TA.

[0095] After applying a TA (e.g., an applied TA), the difference between the WTRU's receive timing and transmit timing may drift away from the applied TA. The WTRU may adjust its transmit timing so that the time difference between its receive timing and transmit timing may be within a threshold or tolerance value of the applied TA.

[0096] The TA adjustment may be an increment of a TA step value. For example, the TA adjustment may be requested, commanded, received and / or applied in increments of a TA step value. The TA step value may, for example, be an integer multiple of a time sample (e.g., Ts). The TA step value may, for example, be 16Ts. For a Ts of 1 / (30720000) seconds and an example TA step value of 16Ts, the example TA step value is approximately 0.52us.

[0097] The TA command may indicate whether the applied TA should be increased or decreased, which may be represented, for example, by an amount of time, which may be referred to as ΔTA. The TA command may indicate applying a new TA, for example to replace an existing applied TA with a newly applied TA. The TA command may include a new value for the applied TA. When the existing applied TA is zero, replacement of the existing applied TA may be applied.

[0098] In some examples and implementations described herein, eNB, cell, serving cell, and component carrier (CC) may be used interchangeably and / or substituted for one another and still comply with the examples and implementations described herein.

[0099] As described above, the eNB may transmit a TA command to the WTRU. The WTRU may not receive the transmitted TA command, for example due to interference or poor channel adjustment. The eNB may not be aware of when the WTRU misses the TA command. The eNB may not be aware of the applied TA (e.g., the exact applied TA) that the WTRU is using, for example because the eNB is not aware that the WTRU has missed one or more TA commands.

[0100] The applied TA may be the TA that the WTRU applies, for example, to adjust its UL timing (where the adjustment may be relative to its DL timing). The applied TA of the WTRU may be different from the sum of one or more (e.g., all) TA commands transmitted by the eNB to the WTRU. In some examples and embodiments described herein, TA may be used to represent the applied TA.

[0101] Figure 2 is an example of transmission and reception timing 200 between two nodes that may be communicating with each other. In this example, the eNB may transmit 201 at a time that it considers to be time 0 210. The WTRU may receive 202 a transmission at an amount of time t1 214 after the eNB's time 0 210, e.g., due to propagation delay. Thus, the WTRU may consider its time 0 211 to be the time at which it receives the transmission sent by the eNB at the eNB's time 0 210. The WTRU may transmit 203 to the eNB at the WTRU's time 0 211. The eNB may receive 204 a transmission from the WTRU at an amount of time t2 215 after the WTRU's transmission. This delay may also be due to propagation delay, for example. Thus, reception at the eNB may be at time t1+t2 216. This may be due to a two-way or round trip delay between the WTRU and the eNB, for example. The values ​​of t1 and t2 may be equal or approximately equal, e.g., when there is channel reciprocity.

[0102] exist Figure 2 219. In the example of , the eNB start time n 212 may be used and the same principles may apply. For example, the WTRU may receive 202 a transmission at an amount of time t1 218 after the eNB's time n 212, eNB time n 212, eNB time n 213, for example, due to propagation delay. Thus, the WTRU may consider its time n 213 to be the time at which it received the transmission sent by the eNB at the eNB's time n 212. The WTRU may transmit 203 to the eNB at the WTRU's time n 213. The eNB may receive 204 a transmission from the WTRU at an amount of time t2 219 after the WTRU's transmission. This delay may also be due to propagation delay, for example. Thus, the eNB may receive the WTRU transmission at eNB time n+t1+t2 217.

[0103] As described above, communications between the eNB and different WTRUs may include different delays. It is desirable that transmissions from a set of WTRUs fall within a time window, which may, for example, be (and / or referred to as) a receive window of the eNB. As described above, the TA may be used to regulate when the WTRU transmits in the UL, for example, to regulate when the eNB receives the transmission.

[0104] Figure 3 An example 300 of transmission and reception timing with applied TA is provided. In this example, the delay from the eNB transmission 301 to the WTRU reception 302 may be t1 310, and the delay from the WTRU transmission 303 to the eNB reception 304 may be t2 311. The TA 316 may be relative to (e.g., applied or used relative to) the WTRU reception time. The applied TA 316 may be t1+t2, for example, to align the WTRU's time 0 transmission 313 received by the eNB with the eNB's time 0 314. The WTRU may transmit its time 0 transmission 313 (e.g., in UL) at TA 316 before its time 0 reception 315 (e.g., in DL). The eNB may receive transmission t2 afterwards, which may align the eNB's time 0 314 transmission time. By using a TA 316 of t1+t2, the eNB may receive a transmission from the WTRU at eNB time 323 (0+t1+t2)-(t1+t2). The eNB time 323 may be the reception time without TA (0+t1+t2) minus the applied TA 316 (t1+t2) (equal to eNB time 0 314 in this example). The eNB may transmit 301 at eNB time 0 314. The WTRU may receive the eNB time 0 314 transmission at a later t1 310 and the WTRU may use that time for the WTRU's reception time 0 315.

[0105] exist Figure 3 318, and / or WTRU receive time n 319) may be used instead of time 0 and the same principles may apply. The WTRU may transmit 303 at TA 320 prior to the WTRU receive at time n 319. In this example, the delay from the eNB transmission 301 to the WTRU receive 302 may be t1 322, and the delay from the WTRU transmission 303 to the eNB receive 304 may be t2 321. The eNB may receive the transmission at a later time t2, which may be time aligned with the eNB transmission at time n 317. The eNB may receive the transmission at eNB time 324, which may be (n+t1+t2)-(t1+t2) and may be equal to eNB time n.

[0106] exist Figure 3The example of aligning TA with eNB time 0 is for example purposes. Any other adjusted or aligned TA may be consistent with the examples and embodiments described in this application.

[0107] UL and DL are used as non-limiting examples of transmission directions. Other directions such as a side link may additionally or alternatively be used and still conform to the examples and embodiments described herein.

[0108] The WTRU or MAC entity of the WTRU or any other device described in the present application may have and / or maintain at least one time alignment timer (TAT). For example, the WTRU may have and / or maintain a TAT for (e.g., each) timing advance group (TAG). The TAG may be or may include a group of service cells (e.g., of the WTRU) using the same timing reference, the same timing reference cell, and / or the same TA value. The TAG may be or may include a group of service cells with a configured UL. The timing reference, timing reference cell, and / or TA may be applied to a cell with a configured UL. The primary TAG (pTAG) may be a TAG that includes a PCell or a PSCell. The secondary TAG (sTAG) may be a TAG that does not include a PCell and / or does not include a PSCell. The WTRU and MAC entities may be used interchangeably in the examples and embodiments described in the present application.

[0109] The TAT may be configured or may be configurable. The TAT may be associated with a TAG. The TAG may be associated with a MAC entity. The TAT may be used to control how long the MAC entity considers the serving cell associated with the TAG to be uplink time aligned.

[0110] For example, when the MAC entity receives a TA command, the MAC entity may start or restart the TAT. The TA command may be received in a MAC-CE or a random access response (RAR). For example, the TA command may be received in a RAR during or after a random access procedure. For example, the MAC entity may start or restart the TAT associated with the indicated TAG, which may be indicated by the TA command.

[0111] The TAT may expire. The TAT may be associated with a TAG, which may be associated with a MAC entity. When the TAT expires, for example, when the MAC entity determines that the TAT expires, or when the MAC entity deems that the TAT expires, the MAC entity may perform at least one TAT termination action, including but not limited to the following:

[0112] flushing one or more (eg, all) HARQ buffers of one or more (eg, all) serving cells (which may, for example, belong to or be associated with the TAG where the TAT terminates);

[0113] clearing one or more (e.g., all) HARQ buffers of one or more serving cells, which may include clearing one or more (e.g., all) HARQ buffers of all serving cells associated with a MAC entity (e.g., when the TAG may be a pTAG);

[0114] releasing and / or notifying a radio resource control (RRC) to release a physical uplink control channel (PUCCH) and / or a sounding reference signal (SRS) for one or more (e.g., all) serving cells, such as one or more serving cells belonging to a TAG whose TAT has been terminated;

[0115] Releasing and / or notifying RRC to release PUCCH and / or SRS for one or more serving cells, wherein the one or more serving cells may be all serving cells associated with the MAC entity (for example, when the TAG for which the TAT has been terminated may be a pTAG);

[0116] clearing one or more (e.g., any) DL assignments and / or one or more (e.g., any) UL grants, wherein the assignments and / or grants may be for a MAC entity (e.g., when the TAG for which the TAT has terminated may be a pTAG); and

[0117] For example, when the TAG whose TAT has been terminated may be a pTAG, it is considered that one or more (eg, all) TATs associated with the MAC entity are terminated.

[0118] There may be one or more HARQ entities at the MAC entity. For example, there may be a HARQ entity for (e.g., each) serving cell with a configured UL. The HARQ entity may maintain multiple HARQ processes, which may, for example, be in parallel to allow transmissions to proceed while waiting for HARQ feedback for successful or unsuccessful reception of a previous transmission. The HARQ process may be associated with a HARQ buffer.

[0119] When the TAT associated with the TAG to which the serving cell belongs is not running, the MAC entity may not perform one or more UL transmissions on the serving cell. For example, when the TAG associated with the TAG to which the serving cell belongs is not running, the MAC entity may not perform one or more UL transmissions (e.g., any UL transmission) on the serving cell except for the random access preamble transmission. The terms "belonging to" and "associated with..." may be used interchangeably in the examples and embodiments described in the present application.

[0120] When the TAT associated with the pTAG is not running, the MAC entity may not perform one or more UL transmissions on a serving cell (e.g., associated with the MAC entity). For example, when the TAT associated with the pTAG is not running, the MAC entity may not perform UL transmissions on any serving cell except for random access preamble transmissions on a special cell (SpCell). The SpCell may be, for example, a PCell or a PSCell.

[0121] When a timer such as TAT ​​is started or restarted, the timer may be set to zero or to a maximum or termination value that may be configured. The timer may terminate when it reaches zero (e.g., when counting down) or when it reaches a maximum or termination value (e.g., when counting up). A timer such as TAT ​​may be adjusted (e.g., incremented or decremented) at or for a TTI (e.g., each TTI). For example, TAT may be adjusted at or for a TTI or subframe. For example, TAT may be adjusted at or for each TTI or subframe. When a timer such as TAT ​​terminates or may terminate, is terminated and / or when it is stopped, the timer may not be running.

[0122] A receive-transmit (Rx-Tx) time difference may be the time difference between the receive timing and the transmit timing of a WTRU or any device described herein. The Rx-Tx time difference may be different from the value of the applied TA. The Rx-Tx time difference may be the applied TA plus or minus an offset. The offset may be due to, for example, at least one of WTRU motion, oscillator drift, and / or applied TA error. The WTRU may adjust its Rx-Tx time difference to be within a threshold or tolerance value of the applied TA. The WTRU may be configured (e.g., may receive a configuration to) measure and / or report the WTRU Rx-Tx time difference.

[0123] The WTRU may measure and / or report the WTRU Rx-Tx time difference to, for example, the eNB (eg, based on configuration). The WTRU may measure and / or report the WTRU Rx-Tx time difference, for example, periodically (eg, based on configuration).

[0124] In an example, the WTRU Rx-Tx time difference may be defined as TWTRU_RX - TWTRU_TX. TWTRU_RX may be the WTRU receive timing of a downlink time unit (e.g., subframe or radio frame) #i from, for example, a serving cell. The receive timing may be defined by the time path that is first detected. TWTRU_TX may be the WTRU transmit timing of an uplink time unit (e.g., subframe or radio frame) #i. A reference point may be used for the WTRU Rx-Tx time difference measurement. For example, the reference point may be a WTRU antenna connector.

[0125] In the examples and embodiments described herein, TA, applied TA, WTRU Rx-Tx time difference, Rx-Tx time difference, and UL / DL time difference may be used interchangeably and / or substituted for one another and still represent the present disclosure.

[0126] In an example, an UL transmission (e.g., a frame transmission) may be performed [(NTA+NTA offset) x Ts] before reception of a corresponding downlink transmission (e.g., a frame transmission) from a cell (e.g., a reference cell), which may be performed before reception of a first detected path (e.g., in time). The first detected path may be received from a corresponding downlink transmission from the cell. NTA may be a TA or an applied TA. NTA offset may be an offset from a TA or an applied TA. The Rx-Tx time difference may be [(NTA+NTA offset) x Ts].

[0127] The processing time may be or may include, for example, the time required or used to process data and / or control signaling or information at or by the WTRU and / or eNode B (eNB) or any other device described herein. Processing data and / or control signaling or information may be or may include, for example, encoding, decoding, interpreting, understanding, preparing, using and / or applying data and / or control signaling. For example, the processing time for DL ​​data reception may include one or more of the following (e.g., may include time for one or more of the following): decoding control signaling (e.g., DL grant) to determine the location and / or decoding parameters for the data channel, attempting to decode the data channel, determining whether the data was successfully received, delivering the received transport block (TB) to a higher layer, and / or preparing to send HARQ feedback. The processing time for preparing HARQ feedback (e.g., for a DL grant) may include one or more of (e.g., all of) the portions that may be included in the processing time for DL ​​data reception.

[0128] The processing time for UL data transmission may, for example, include one or more of the following (e.g., include time for one or more of the following): decoding control signaling (e.g., UL grant) to determine transmission parameters and / or location for a data channel, preparing a transport block (TB) for transmission, and / or determining power for transmission. The processing time (e.g., data processing time) may be a function of (e.g., proportional to) the TB size of the data and / or the TTI length.

[0129] Figure 4 Another example 400 of transmission and reception timing with TA applied is provided. Figure 4414 ). In the example of WTRU 406 , a WTRU may receive 401 a DL grant at time n 412 (e.g., WTRU Rx time n). The WTRU may process the DL grant during processing time 414, and the WTRU may transmit 402 a HARQ feedback at time n+x 413 (e.g., WTRU Tx time n+x). The units of time n and time n+x may be subframes, slots, symbols, minislots, or TTIs. The value of x may be an integer, such as 4. For example, due to TA 411 , 416, the WTRU Rx timing 412 , 415 and the WTRU Tx timing 410 , 413 (e.g., corresponding Tx timing) may be different. The applied TA 416 may affect the available processing time 414 between the Rx time n 412 and the Tx time n+x 413. For example, if the starting point for determining the available processing time is the start of the WTRU Rx time n 412, the available processing time may be x-applied TA (or x-WTRU Rx-Tx time difference). If another starting point is used, the available processing time 414 may be adjusted accordingly. For example, the starting point for the available processing time 414 may be the end of the time unit (e.g., TTI) in which the control channel may be received, or the beginning of the next time unit (after the time unit in which the control channel may be received). For the subtraction, x and the applied TA (or WTRU Rx-Tx time difference) may be converted to a common unit, such as time samples.

[0130] In some applications, short TTI (also referred to herein as sTTI) may be used, for example, to reduce latency. Using short TTI may reduce available processing time, for example, for generating and / or transmitting HARQ feedback in the UL (e.g., associated with DL reception) and / or UL data transmission.

[0131] Using an applied TA may reduce the available processing time, eg, to even less.For shorter TTIs, the WTRU may not be able to support some values ​​of applied TA that it may support for longer TTIs.

[0132] For example, refer to Figure 4, the available processing time for UL transmission (e.g. HARQ or data transmission) after DL data reception or UL grant may be x minus the applied TA. In this example, x may be 4TTIs and the TTI may have a duration of 1ms for long TTI and 0.5ms for sTTI. The final available processing time may be 4ms minus the applied TA for long TTI and 2ms minus the applied TA for sTTI. For example, if the WTRU requires 2ms to process 1ms of data and 1ms to process 0.5ms of data, then the WTRU may support a 2ms applied TA for a 1ms TTI and a 1ms applied TA for a 0.5ms TTI. This may enable the WTRU to handle this reduced TA capability when using sTTI operation. This may enable the eNB to handle this reduced TA capability of the WTRU communicating with it when using sTTI operation.

[0133] One way to handle this reduced TA capability may be to limit the TA based on the TTI length. For example, the TA may be limited to a maximum value for all WTRUs.

[0134] However, considering additional factors and / or alternative approaches may provide a more optimized solution, because, for example, WTRUs may have different processing capabilities and multiple processes may affect processing time. The embodiments described in this application provide the following approaches and concepts related to handling TA and processing capabilities and related methods in a system for reducing latency:

[0135] determining a processing capability (PC) or processing limit (e.g., a processing time capability or limit, a TA capability or limit, or an Rx-Tx time difference capability or limit), which may, for example, be based on (e.g., determined based on) parameters including, but not limited to, a TTI, a transport block size (TBS), a transmission type, a transport channel, and / or a scheduling / HARQ timeline;

[0136] Determine, provide, receive and / or use PC (or limit) instructions;

[0137] Determine, provide, receive and / or use PC (or limit) configurations;

[0138] Determine and / or indicate proximity to a PC or limit (e.g., margin);

[0139] Report when proximity is below a threshold and / or above a threshold;

[0140] Triggering a PC (or limit) margin (e.g., reporting thereof) and / or reporting a PC (or limit) margin, wherein the report may be triggered and / or sent in a TTI crossing a threshold, which may be, for example, a TTI and / or TBS cross-correlated;

[0141] Exception handling when a PC (or limit) is violated (e.g., exceeding a PC / limit which may be a maximum value or falling below a PC / limit which may be a minimum value), wherein the exception handling includes, but is not limited to, capping a process value (PV) (e.g., setting the PV to a PC), stopping one or more transmissions in the UL (e.g., for a short TTI, for multiple TTIs, and / or for all TTIs), stopping a time alignment timer (e.g., generally or for a short TTI), clearing one or more HARQ buffers (e.g., generally or for a short TTI), and / or sending an error message or a proximity / margin report, such as using a transmission with a longer TTI length (e.g., when scheduled) or a physical random access channel (PRACH);

[0142] Avoiding abnormal conditions by prioritizing TTIs, channels, and / or transmission types (e.g., UCI versus data) and / or dropping at least one lower priority TTI, channel, or transmission type to avoid reaching abnormal conditions (e.g., for at least one of the TTIs); and / or

[0143] When a TTI length less than a subframe is used, the TA is applied in subframe n+6 (e.g., at its beginning) for a TTI (e.g., sTTI) received within a subframe (e.g., at any time within subframe n), and / or in subframe n+y (where y may be fixed, configured or a function of the TTI length, PC and / or the time difference between DL TTI and UL TTI), which may be done at the beginning of the subframe (e.g., regardless of the TTI length).

[0144] A PC may be configured, determined and / or used. A PC may be a restriction or a processing restriction. The term restriction may be used to refer to a processing restriction.

[0145] The phrases and terms PC, WTRU PC or PC of a WTRU may be used interchangeably herein. Capabilities and limitations may be substituted for one another in the embodiments and examples provided herein and still be consistent with the present disclosure.

[0146] Channels such as PUSCH and PUCCH are used herein as non-limiting examples of UL channels (e.g., UL data and control channels). PUSCH and PUCCH are channels that can be used with long TTI (e.g., 1 ms) or sTTI (e.g., values ​​shorter than 1 ms). Other channels, such as sPUSCH and sPUCCH, can replace PUSCH and PUCCH and still comply with the examples and embodiments described herein.

[0147] Channels such as the physical downlink shared channel (PDSCH) and the physical downlink control channel (PDCCH) are used herein as non-limiting examples of DL channels (e.g., DL data and control channels). PDSCH and PDCCH are channels that can be used with long TTI (e.g., 1 ms) or short TTI (e.g., values ​​shorter than 1 ms). Other channels, such as sPDSCH and sPDCCH, ePDCCH, mPDCCH, and at least one of nPDCCH can replace PDSCH and PDCCH and still represent the examples and embodiments described in this application.

[0148] A normal or regular TTI may be a TTI that may correspond to a subframe (eg, 1 ms).A long TTI may be considered a normal or regular TTI.

[0149] The PC may be determined (eg, the WTRU may determine the processing capability) at a TTI (eg, every TTI) or for (eg, at least one) TTI (eg, every TTI).

[0150] In embodiments described herein, a WTRU may have, may determine, and / or may be configured with a (e.g., WTRU's) PC or processing limit based on at least one of: UL and / or DL ​​TTI length, UL and / or DL ​​TBS, UL transmission type (e.g., feedback or data), a channel that may be used for UL transmission (e.g., PUCCH or physical uplink shared channel (PUSCH)), and / or a timeline (e.g., scheduling and / or HARQ timeline). Alternatively or additionally, the (e.g., WTRU's) PC or limit may be based on, may be a function (e.g., proportional to), may be associated with, may correspond to, may be determined (e.g., by the WTRU) based on, and / or may be configured (by the eNB) based on: at least one processing criterion, e.g., at least one of a plurality of processing criteria. For example, a WTRU may have, may determine, and / or may be configured with a PC that is based on, is a function of, is associated with, and / or corresponds to a processing criterion, e.g., at least one processing criterion, which may be at least one of a plurality of processing criteria. The eNB may provide the PC configuration, for example, via signaling such as RRC signaling and / or broadcast signaling (e.g., in system information). In addition, one PC may be a function of another PC. For example, a WTRU may have, may determine, and / or may be configured with a PC that is based on, is a function of, is associated with, and / or corresponds to another PC. The WTRU may determine a PC using any or a combination of the embodiments or examples described herein.

[0151] The PC indication may be provided and / or used. The WTRU may provide (eg, transmit or signal) a set of one or more processing capabilities of the WTRU to, for example, an eNB. The WTRU may provide the set of one or more processing capabilities via signaling, such as RRC signaling.

[0152] The PC of the WTRU may be or may include at least one of the following:

[0153] TA capabilities (or limitations), e.g., TAs that can be supported and / or used;

[0154] Maximum TA capabilities (or limitations), e.g., the maximum TA that can be supported and / or used;

[0155] Rx-Tx time difference capabilities (or limitations), e.g., Rx-Tx time differences that can be supported and / or used;

[0156] Maximum Rx-Tx time difference capability (or limitation), e.g., the maximum Rx-Tx time difference that can be supported and / or used;

[0157] Processing time capabilities (or limitations), such as the processing time that can be supported, required, and / or used;

[0158] Minimum or maximum processing time capabilities (or limitations), such as the minimum or maximum processing time that can be supported, required, and / or used;

[0159] Available processing time, e.g., time available for processing (e.g., for a UL TTI, a DL TTI, and / or a combination of at least one DL TTI and at least one UL TTI);

[0160] TTI (e.g., TTI length) capabilities (or limitations), such as TTIs that can be supported and / or used;

[0161] Minimum TTI (e.g., TTI length) capability (or limitation), e.g., the minimum TTI that can be supported and / or used. The minimum TTI (e.g., TTI length) can be determined based on the number of symbols used and / or configured for a TTI and / or the subcarrier spacing used and / or configured;

[0162] TBS capabilities (or limitations), such as TBS that can be supported and / or used;

[0163] Maximum TBS capability (or limit), e.g., the maximum TBS that can be supported and / or used;

[0164] Timeline (e.g., scheduling and / or HARQ timeline) capabilities (or limitations), such as timelines that may be supported and / or used (e.g., the value of k in the timeline relationship of TTI n→TTI n+k); and / or

[0165] Minimum timeline (eg, scheduling and / or HARQ timeline) capabilities (or limitations), such as the minimum timeline that can be supported and / or used (eg, the minimum value of k in the timeline relationship of TTI n→TTI n+k).

[0166] The timeline may be at least one of: a scheduling timeline for UL (e.g., UL transmission); a scheduling timeline for DL ​​(e.g., DL reception); a HARQ timeline for DL ​​transmission (e.g., DL data reception → HARQ feedback transmission in UL); and / or a HARQ timeline for UL transmission (e.g., UL data transmission → HARQ feedback reception in DL). A timeline for retransmission (e.g., in UL) may be considered a scheduling timeline, which retransmission may be due to negative HARQ feedback (e.g., in DL).

[0167] The WTRU may determine, have, maintain, be configured and / or use one or more PCs, such as at least a first PC and a second PC. The first PC and the second PC may be determined based on different sets of processing criteria.

[0168] Support and / or use may be performed by the WTRU and / or the eNB.

[0169] The TTI length (eg, in time, such as microseconds, milliseconds, nanoseconds, etc.) may be determined (eg, by the WTRU) based on at least one of: subcarrier spacing and / or number of symbols that may be configured and / or used.

[0170] In the embodiments described in this application, the processing criteria may be or may include at least one of the following:

[0171] The number of symbols, which may be, for example, the number of symbols in a TTI or TTI length that may be used and / or configured (eg, in or according to a TTI configuration);

[0172] TTI (e.g., in UL and / or DL), e.g., TTI length (e.g., in UL and / or DL);

[0173] The time difference between a TTI in the DL and a TTI in the UL, e.g., the time between the start or end of a DL TTI that may enable (e.g., trigger or schedule) or cause a UL transmission in the UL and the start of a UL TTI where a UL transmission may occur;

[0174] TBS, e.g., a TBS that may be scheduled, granted, allocated, transmitted, or received in a time unit such as a TTI;

[0175] the number of tiers (e.g., rankings) that can be used for reception and / or transmission;

[0176] the number of codewords available for reception and / or transmission;

[0177] The number of time / frequency resources (e.g., physical resource blocks (PRBs)) that can be scheduled, granted, allocated, transmitted or received in a time unit such as a TTI;

[0178] a coding scheme (e.g., convolutional coding or Turbo coding) that may be used for reception of a channel (e.g., a DL channel such as a PDSCH) that may precede, correspond to, and / or result in a transmission (e.g., in the UL) to which the TA may be applied;

[0179] MIMO receiver schemes (e.g., MMSE, MMSE-IRC, or MMSE-SIC) that may be used for channel reception using one or more transport layers (e.g., DL channels such as PDSCH);

[0180] The waveform used for transmission (e.g., CP-OFDM or DFT-s-OFDM); and / or

[0181] The parameter configuration used or configured (e.g. CP length, subcarrier spacing).

[0182] Other processing criteria may be or may include, but are not limited to, transmission type, reception type, channel type, and / or channel location.

[0183] The processing criterion may be or may include a transmission type (e.g., UL transmission type), for example, a transmission type to which the TA may be applied. The transmission type may be, for example, at least one of: a control or feedback transmission (e.g., HARQ or CSI feedback), a data transmission, and / or an RS transmission (e.g., DMRS or SRS).

[0184] The processing criteria may be or may include a reception type (e.g., a DL reception type), such as a reception type that may precede, correspond to, and / or result in a transmission (e.g., in the UL) to which the TA may be applied. The reception type may, for example, be at least one of: control reception (e.g., DCI, DCI format, DL grant, UL grant, and / or aperiodic SRS triggering), data reception, and / or RS reception (e.g., CRS, DMRS, CSI-RS).

[0185] The processing criteria may be or may include a channel type (eg, UL channel type), such as a channel type to which the TA may be applied. The channel type may be, for example, at least one of a control channel (eg, UL control channel, such as PUCCH) or a data channel (eg, UL data channel, such as PUSCH).

[0186] The processing criteria may be or may include a channel type (e.g., a DL channel type), such as a channel type on which control or data may be received, which may correspond to and / or result in a transmission (e.g., UL) to which the TA may be applied. The channel type may, for example, be at least one of: a control channel (e.g., a DL control channel, such as a PDCCH) or a data channel (e.g., a DL data channel, such as a PDSCH).

[0187] The processing criteria may be or may include a channel location, such as a time and / or frequency location of a DL control channel that may be associated with, correspond to, and / or result in an UL transmission to which the TA may be applied. The channel location may be, for example, at least one of: a control region (e.g., a time or symbol where there may be no data) or a data region (e.g., a time or symbol where there may be data).

[0188] The processing criteria may be or may include a timeline (eg, a scheduling and / or HARQ timeline) that may be configured and / or used.

[0189] The processing criteria may be or may include a reference signal type or configuration that may be configured and / or used.

[0190] In the embodiments described herein, the WTRU may have, may determine and / or may be configured with a PC (or restriction) as defined above, which may be applied to UL transmissions. For example, the PC (or restriction) may be a TA (e.g., a maximum TA), an Rx-Tx time difference (e.g., a maximum Rx-Tx time difference) and / or a timeline (e.g., a minimum scheduling, HARQ or DL ​​to UL timeline), which may be supported (e.g., by the WTRU) and / or used (e.g., by the WTRU and / or the eNB), for example, for UL transmissions. The UL transmission may be or may include HARQ feedback that may correspond to a DL data transmission (e.g., a PDSCH transmission). The WTRU may transmit HARQ feedback on a UL channel (e.g., a PUCCH or PUSCH channel) using a TTI of TTI_ul. The UL transmission may be or may include a UL data transmission (e.g., a PUSCH) that may correspond to a grant (e.g., a UL grant) or an allocation (which may have been received in a DL control channel and / or DCI).

[0191] The WTRU may transmit UL data transmission using a TTI of TTI_ul. The TTI for DL ​​data transmission and / or for DL ​​control channel transmission may be TTI_dl. TTI_ul and TTI_dl may be the same or different TTIs (eg, may have the same or different values).

[0192] A TTI in which a PDSCH may be received may be referred to as TTI_dl A. A TTI in which a DL control channel, DCI, grant, and / or allocation for a PUSCH may be received may be referred to as TTI_dl B. TTI_dl A and TTI_dl B may be the same or different. A TTI in which HARQ feedback and / or PUSCH may be transmitted may be referred to as TTI_ul A.

[0193] Further processing criteria may be used in the embodiments described in this application. The processing criteria may be or may include at least one of the following:

[0194] TTI (e.g., TTI_ul and / or TTI_dl);

[0195] The time difference between TTI_dl and TTI_ul (e.g., between TTI_dl A and TTI_ul A, between TTI_dl B and TTI_ul A, and / or between TTI_ul A and one of TTI_dl A and TTI_dl B that is closer to TTI_ul A), where the time difference may be the time between the start (or end) of TTI_dl and the start of TTI_ul, e.g., excluding the case where TA is applied;

[0196] The TBS (e.g., actual TBS or maximum TBS) of a transport block (TB) or codeword (CW) that the PDSCH can carry;

[0197] the TBS (e.g., actual TBS or maximum TBS) of another TB or CW that the WTRU may receive (e.g., during TTI_dl A), which may affect the processing time required or used by the WTRU, e.g., when DL MIMO may be used;

[0198] The number of TBs or CWs that the WTRU can receive (e.g., the number that can be received during TTI_dl A);

[0199] the channel (e.g., PUCCH or PUSCH) that the WTRU may use for transmission of feedback (e.g., HARQ feedback), e.g., as a result of whether the WTRU is transmitting on a PUCCH or PUSCH channel, is about to transmit or is expected to transmit feedback (e.g., HARQ feedback);

[0200] For example, the set of channels that may be transmitted in a TTI when the WTRU may transmit feedback (e.g., PUCCH only, PUSCH only, or PUSCH and PUCCH);

[0201] For example, when the WTRU may transmit feedback (e.g., HARQ feedback), whether the WTRU transmits on PUCCH only, PUSCH only, or PUSCH and PUCCH in the UL in a TTI, and the results to be transmitted or expected to be transmitted;

[0202] The result of whether the WTRU receives an UL grant for a PUSCH transmission in the TTI in which the WTRU may transmit feedback (e.g., TTI_ul A) (e.g., the WTRU may need additional time to prepare for the UL transmission);

[0203] a TBS (or maximum TBS) of at least one transport block that the WTRU may transmit on the PUSCH in a TTI in which the WTRU may transmit feedback;

[0204] The number of layers, number of PRBs and / or coding schemes that can be used to receive PDSCH;

[0205] The TBS (or maximum TBS) of at least one transport block that the WTRU may transmit on the PUSCH in a TTI for which UL resources may be allocated or granted (e.g., TTI_ul A);

[0206] The result of whether the WTRU received a DL grant or allocation in the TTI (e.g., TTI_dl B) in which the WTRU received the UL grant or allocation (e.g., whether the WTRU needs to process a DL TB before UL transmission);

[0207] The result of whether the WTRU received a DL grant or allocation in or after TTI_dl B and before TTI_ul A (e.g., whether the WTRU needs to process a DL TB before UL transmission);

[0208] Results of whether the WTRU may transmit a PUSCH based on a CP-OFDM waveform or a DFT-s-OFDM waveform; and / or

[0209] The result of whether the WTRU can transmit or receive a signal based on the first parameter configuration (e.g., the first subcarrier spacing) or the second parameter configuration (e.g., the second subcarrier spacing).

[0210] For example, for a TTI value (e.g., TTI_dl and / or TTI_ul value) x (e.g., 2 symbols, 4 symbols, or 1 slot), the WTRU may have, may determine, or may be configured that it may use, may be expected to use, and / or may support a maximum TA (or maximum Rx-Tx time difference) of y. For example, the value of y may be a function of x or proportional to x. For example, y may be equal to x / 2. The value of y may be a function of the TBS, such as a function of the TTI and the TBS.

[0211] The PC (or limit) may be expressed in one or more (e.g., an integer number of) time units. A time unit may be or may include, but is not limited to, a subframe, a time slot, a mini-time slot, a TTI, a symbol, a time sample, an integer number of time slots and / or mini-time slots, an integer number of symbols, a fractional number of symbols (e.g., 1 / 2 symbol or 1 / 4 symbol), an integer number of time samples, a TA step size, or an integer number of TA step sizes. The TA step size may be, for example, 16 time samples. The PC may or may also be expressed in time units such as microseconds and / or nanoseconds.

[0212] A PC, TTI, time unit and / or multiple time units may be quantified and / or represented by a value in a set, list or table of values ​​or an index to a set, list or table of values ​​(e.g., when determined, configured, provided and / or reported).

[0213] A PC may be represented by a category (e.g., a category index) in a category set (e.g., short, medium, long). A category may represent a PC value. For example, short may represent or may be defined as a PC of x, medium may represent or may be defined as a PC of y, and long may represent or may be defined as a PC of z. For example, x, y, and z may be or may represent values, e.g., PC values, such as a maximum or minimum value that may be supported, required, and / or used. The values ​​of x, y, and z may satisfy the relationship x. <y<z。

[0214] The processing criteria may be determined (eg, the WTRU may determine the processing criteria) in a TTI (eg, every TTI) or for (eg, at least one) TTI (eg, every TTI).

[0215] The PC may be determined based on a reference signal type or configuration that may be used.One or more reference signal types or configurations may be used for a physical channel (eg, PDSCH or PUSCH) and the PC may be based on a reference signal type or configuration that may be configured and / or used.

[0216] In embodiments described herein, a WTRU may provide (e.g., send, signal, report or transmit) a PC (e.g., of the WTRU), for example, to an eNB. The WTRU may be configured (e.g., by an eNB) or request provision of a PC (e.g., to an eNB). The WTRU may provide a PC in response to a request to provide one or more capabilities of the WTRU. The WTRU may provide a PC in response to a request to provide at least a PC. For example, the WTRU may include its PC in a WTRU capabilities message.

[0217] In some examples and implementations, the terms providing, sending, signaling, reporting, and transmitting may be used interchangeably.

[0218] The WTRU may provide a PC (eg, to an eNB) that may be associated with and / or may correspond to a processing standard.

[0219] For example, the WTRU may provide or indicate one or more TTIs that the WTRU may support (e.g., TTI length) or the minimum TTI that the WTRU may support. The WTRU may indicate a PC for a TTI or supported TTIs (e.g., each TTI or supported TTI). For example, the WTRU may provide a maximum TA, a maximum Rx-Tx time difference, and / or a maximum TBS that the WTRU may support for a TTI or supported TTI. In another example, the WTRU may provide a minimum processing time required or used by the WTRU for a TTI or supported TTI. In another example, the WTRU may provide a maximum TA (or maximum Rx-Tx time difference) that the WTRU may support for at least one of the following (or a combination of at least two): TTI (UL and / or DL ​​TTI), TBS, transmission type, and / or channel type.

[0220] TTI, TTI length and TTI duration may be used interchangeably.

[0221] In another example, the WTRU may indicate one or more timelines that the WTRU may support (e.g., the value of k in the timeline relationship of TTI n→TTI n+k) or the minimum timeline that the WTRU may support. The WTRU may provide the PC of the timelines that the WTRU may support. For example, the WTRU may provide the maximum TA, maximum Rx-Tx time difference, and / or maximum TBS that the WTRU may support for the timelines that the WTRU may support.

[0222] In embodiments described herein, a WTRU may be configured with a PC (e.g., processing restrictions), and the configuration (e.g., PC configuration) may be provided by an eNB and / or received by the WTRU. The configuration may be provided and / or received in WTRU-specific signaling and / or cell-specific signaling. The signaling may be RRC signaling. The signaling may be broadcast signaling. For example, the PC may be provided and / or received in system information such as a system information block (SIB).

[0223] The WTRU may use or be configured to use a first TTI, such as a normal or conventional TTI. For example, when the WTRU configures a TTI, such as a second TTI or a short TTI (sTTI), the eNB may provide the PC and / or the WTRU may receive the PC. The second TTI may be shorter than the first TTI. The PC may be based on, be a function of, be associated with and / or correspond to: one or more of the processing criteria described above.

[0224] The terms standard and a standard may be used interchangeably herein. For example, "standard" may be used to mean "a standard".

[0225] For example, the eNB may provide and / or the WTRU may receive one or more TTIs (e.g., TTI lengths) that the WTRU and / or the eNB may support or use. The WTRU may be configured (e.g., by the eNB) with one or more TTIs (e.g., TTI lengths) that the WTRU may use. The WTRU may be configured with a PC for a TTI or configured TTIs (e.g., for each TTI or configured TTIs). Alternatively or additionally, the WTRU may be configured (e.g., by the eNB) with a maximum TA, a maximum Rx-Tx time difference, and / or a maximum TBS that the WTRU may support (e.g., need to support) (e.g., for configured TTIs). Alternatively or additionally, the WTRU may be configured (e.g., by the eNB) with a maximum TA (or a maximum Rx-Tx time difference) that the WTRU supports (or needs to support) for at least one (or a combination of at least two) of the following: TTI (UL and / or DL ​​TTI), TBS, transmission type, and / or channel type.

[0226] Alternatively or additionally, the WTRU may use or be configured to use a first timeline, such as a normal or conventional timeline. In this example, the WTRU may be configured or further configured (e.g., by an eNB) with a second timeline (e.g., a shortened timeline) that the WTRU may use.

[0227] When the WTRU may be configured with a timeline such as a second timeline or a shortened TTI, the eNB may provide and / or the WTRU may receive the PC. The second timeline may be shorter than the first timeline. For example, the WTRU may be configured (e.g., by the eNB) with a maximum TA, a maximum Rx-Tx time difference, and / or a maximum TBS that the WTRU may support (e.g., need to support), for example, for a configured timeline that may be a shortened timeline.

[0228] The non-exhaustive and non-exclusive embodiments described below relate to proximity of a PV to a PC. The PC may define limits, or what the WTRU can do or support (e.g., with respect to processing and / or transmission). The PV may define what the WTRU needs to do or support (e.g., with respect to processing and / or transmission) based on, for example, a configuration and / or UL / DL grant received by the WTRU. In the embodiments described herein, proximity (or limits) to a PC (e.g., a PV) may be determined, provided (e.g., indicated), and / or used.

[0229] The PV may be a value, such as a current or present value of a processing parameter. The PV may be related to UL transmission and / or DL ​​transmission (or reception). For example, the processing parameter may be or may include at least one of the following:

[0230] TA (e.g. applied TA);

[0231] Rx-Tx time difference;

[0232] Processing time (e.g., processing time that is available or can be used), such as processing time based on at least one of: a TTI, a TTI length, a number of symbols, a number of OFDM symbols, a symbol length, a number of samples, and a number of time samples;

[0233] A TTI (e.g., a TTI length), such as a TTI (e.g., a TTI length) that may be identified, requested, and / or configured;

[0234] TBS; and / or

[0235] A timeline or timeline value (eg, the value of k in a timeline relationship of TTI n→TTI n+k) may be requested, configured, and / or indicated semi-statically (eg, via RRC signaling) and / or dynamically (eg, in a DCI).

[0236] The WTRU may measure a processing parameter (eg, as defined above) to determine its value. The WTRU may average and / or filter one or more measurements of the processing parameter to determine the value of the processing parameter.

[0237] The WTRU may determine the proximity of the PV to the PC. For example, the proximity of the PV to the PC may be the difference between the PV and the PC, such as PV-PC or PC-PV. The proximity of the PV to the PC may be referred to as a margin in this application. The term proximity as used herein may refer to the proximity of the PV to the PC (e.g., the determined proximity). Therefore, proximity and margin may be used interchangeably.

[0238] For example, as described in one or more embodiments or examples of the present application, the WTRU may determine the PC. For example, as described in one or more embodiments or examples of the present application, the PC may be configured (e.g., received in a configuration). The PC may be configured (e.g., received in a configuration) from the eNB. The WTRU may receive the configuration.

[0239] The PV and / or proximity of the PV to the PC may be determined (eg, by the WTRU) in a TTI or for (eg, at least one) TTI. Additionally, the WTRU may determine the PV and / or proximity in each TTI or for each TTI.

[0240] In the embodiments described herein, the WTRU may also determine that (or when) the PV may meet (or satisfy) or may meet (or satisfy) a threshold comparison condition. The PV may meet (or satisfy) the threshold comparison condition when the PV reaches (e.g., is at) a threshold, crosses a threshold, exceeds a threshold, and / or is below a threshold. The PV may meet (or satisfy) the threshold comparison condition when the PV may reach (e.g., may be at) a threshold, may cross a threshold, may exceed a threshold, and / or may be below a threshold.

[0241] For example, the WTRU may determine that the PV may (or when) reach (e.g., at) a threshold, may cross a threshold, may exceed a threshold and / or may be below a threshold. When (e.g., when the WTRU may determine that) the PV may meet (or satisfy) or meets (or satisfies) a threshold comparison condition, the WTRU may trigger or provide a report or indication (e.g., to an eNB). The report or indication may indicate that the PV has met (or has met) a threshold or a threshold comparison condition.

[0242] In embodiments described herein, the WTRU may trigger or provide a report or indication (e.g., to an eNB) to indicate that a PV may meet, may satisfy, may have met and / or may have satisfied a threshold comparison condition. The report or indication may include the PV (e.g., may include a value of the PV or an indication representative of a value). The report or indication may identify that the threshold comparison condition is met (or satisfied) or may include an indication that the threshold comparison condition is met (or satisfied).

[0243] In embodiments described herein, the WTRU may determine that (or when) the proximity of the PV to the PC may meet (or satisfy) or meet (or satisfy) a threshold comparison condition. The proximity of the PV to the PC may meet (or satisfy) a threshold comparison condition when the proximity of the PV to the PC may reach (e.g., at) or reach (e.g., at) a threshold, may pass or pass a threshold, may exceed or exceed a threshold, and / or may be below or below a threshold. For example, the WTRU may determine that (or when) the proximity of the PV to the PC may reach (e.g., at) or reach (e.g., at) a threshold, may pass or pass a threshold, may exceed or exceed a threshold, and / or may be below or below a threshold.

[0244] When the WTRU determines that the condition will be met or satisfied (e.g., at or for a time unit or TTI for which such determination is made), the WTRU may consider the condition to be met or satisfied. When the WTRU determines that the condition will be met or satisfied (e.g., at or for a time unit or TTI for which such determination is made), the WTRU may determine that the condition is met or satisfied.

[0245] In embodiments described herein, the WTRU may trigger or provide a report or indication (e.g., to an eNB), for example, when (e.g., when the WTRU determines) that the proximity of the PV to the PC may meet (or satisfy) a threshold comparison condition. The report or indication may indicate that the proximity of the PV to the PC meets (or satisfies) a threshold or threshold comparison condition. The WTRU may trigger or provide a report or indication (e.g., to an eNB) to indicate that the proximity of the PV to the PC may meet or meet, may meet or satisfy, may have met or have met and / or may have met or have satisfied a threshold comparison condition.

[0246] In the embodiments described herein, the report or indication may include at least one of the following (e.g., may include a value or an indication representing a value of at least one of the following): PV, PC, and / or the proximity of PV to PC. The report or indication may identify that a threshold comparison condition is met (or satisfied) or may include an indication that a threshold comparison condition is met (or satisfied).

[0247] Alternatively or additionally, in embodiments described herein, the WTRU may determine that (or when) a proximity condition is met or satisfied or may be met or satisfied (e.g., determine or when a proximity condition is or may be true). The proximity condition may be at least one of the following (or the result of at least one of the following):

[0248] PV is or can be close to PC or threshold;

[0249] PV is or may be at or exceeds a PC or a threshold value (e.g., a first threshold value);

[0250] PV is or may be lower than PC or a threshold value (e.g., a second threshold value);

[0251] The PV is or may be within a threshold (e.g., a first threshold) of the PC;

[0252] PV is or may be above a threshold value (eg, a second threshold value) from PC;

[0253] The PV never changes within a threshold value (e.g., a first threshold value) of the PC or can change to be within a threshold value (e.g., a first threshold value) of the PC;

[0254] PV changes from a distance PC not higher than a threshold value (e.g., a second threshold value) or can change to a distance PC higher than a threshold value (e.g., a second threshold value);

[0255] The PV changes from being within a first threshold of the PC or can change to being above a second threshold from the PC;

[0256] PV changes or can change from being above a second threshold from PC to being within a first threshold of PC;

[0257] The proximity (e.g., PV to PC) changes from being above a threshold (e.g., a first threshold) or can change to being below a threshold (e.g., a first threshold);

[0258] The proximity changes or may change from below a threshold value (eg, a second threshold value) to above a threshold value (eg, a second threshold value);

[0259] The proximity changes or may change from below a first threshold to above a second threshold; and / or

[0260] The proximity changes or may change from above the second threshold to below the first threshold of PC. When the proximity condition may be met or satisfied (e.g., when the WTRU determines that the proximity condition may be met or satisfied), the WTRU may trigger or provide a report or indication (e.g., to the eNB).

[0261] In embodiments described herein, one or more thresholds may be provided and / or used. For example, an eNB may configure the one or more thresholds. The WTRU may receive one or more thresholds (e.g., configuration of one or more thresholds), for example, from an eNB. A first threshold may be used for a first threshold comparison (e.g., for a first threshold comparison condition). A second threshold may be used for a second threshold comparison (e.g., for a second threshold comparison condition). The first threshold and the second threshold may be the same or different.

[0262] For example, when using a threshold value to determine or determine when a threshold comparison condition may be met or satisfied, the threshold value may be adjusted by one or more offset or hysteresis values. For example, using an offset or hysteresis value may avoid triggering a report due to a small change in PV or proximity when the PV or proximity may be close to the threshold value.

[0263] The one or more thresholds may be associated with and / or may correspond to a TTI, for example a TTI that may be configured or supported. The one or more thresholds may be configured for or with a TTI.

[0264] In some examples and embodiments, "less than" may be replaced by "less than or equal to," "within" may be replaced by "in or within," "more than" may be replaced by "at least," and / or "greater than" may be replaced by "greater than or equal to," and still comply with the embodiments described herein.

[0265] The term "threshold" may be used to denote the value of a threshold. The threshold may be configured and / or represented in one or more (e.g., an integer number of) time units. The time unit may be, for example, at least one of: a symbol, a time sample, an integer number of symbols, a fractional number of symbols (e.g., 1 / 2 symbol or 1 / 4 symbol), an integer number of time samples, a TA step length, or an integer number of TA steps. The TA step length may be, for example, 16 time samples. The threshold may be configured and / or represented in time units such as microseconds and / or nanoseconds.

[0266] For example, the WTRU may determine (or determine when) a PV (e.g., TA, Rx-Tx time difference, processing time, or timeline) is or may be at a threshold, exceeds or may exceed a threshold, or is or may be below a threshold. The determination and / or PV may be for a TTI, such as a current TTI or an upcoming TTI. The determination and / or PV may be for a UL TTI or a UL transmission (e.g., an upcoming or current UL TTI or an upcoming or current UL transmission). The UL transmission may be for an upcoming or current TTI. The threshold and / or PV may be based on a processing time that may be associated with the UL transmission. The threshold and / or PV may be based on a reception, processing, and / or processing time that may be associated with one or more DL TTIs that may precede the UL transmission. The WTRU may trigger and / or provide a report or indication (e.g., to an eNB) that may indicate that the PV may be at a threshold, may exceed a threshold, or may be below a threshold.

[0267] In another example, the WTRU may determine (or determine when) the proximity of a PV (e.g., TA, Rx-Tx time difference, processing time, or timeline) to a PC (e.g., maximum TA capability or limit, maximum Rx-Tx time difference capability or limit, processing time capability or limit, or timeline capability or limit) is at or may be at a threshold, exceeds or may exceed a threshold, is below or may be below a threshold.

[0268] The determination, proximity, PV, and / or PC may be for a TTI, such as a current TTI or an upcoming TTI. The determination, proximity, PV, and / or PC may be for a UL TTI or a UL transmission (e.g., an upcoming or current UL TTI or a UL transmission). The UL transmission may be for an upcoming or current TTI. The threshold(s) (e.g., may be associated with the proximity, PV, and / or PC), the PV, and / or PC may be based on a processing time that may be associated with the UL transmission. The threshold(s) (e.g., may be associated with the proximity, PV, and / or PC), the PV, and / or PC may be based on a reception, processing, and / or processing time that may be associated with one or more DL TTIs preceding the UL transmission. The WTRU may trigger and / or provide a report or indication (e.g., to an eNB) that may indicate that the proximity of the PV to the PC is or may be at a threshold, exceeds or may exceed a threshold, or is or may be below a threshold.

[0269] A report may be or may include one or more indications. In some examples and embodiments, a report and an indication may be used interchangeably. In the embodiments described herein, a report or an indication may be or may include at least one of the following:

[0270] PV (e.g., current or present PV), such as current or present (e.g., most recently) applied TA, current or present (e.g., most recently) Rx-Tx time difference (e.g., measured Rx-Tx time difference), or current or present (e.g., most recently) processing time;

[0271] PC (e.g., the current, present, or most recent PC that may be determined by the WTRU);

[0272] the proximity (or margin) of the PV to the PC, such as the time to which it may correspond (e.g., TTI) or the time to which the report or indication may correspond;

[0273] a proximity (or margin) of the PV to the PC, such as a current or present (eg, most recent) proximity value that may be determined using the current or present (eg, most recent) PV and / or PC;

[0274] an indication as to (e.g. which) threshold value may or may have been exceeded;

[0275] an indication as to (e.g., which) threshold comparison condition may have been met (or satisfied);

[0276] an indication as to (e.g. which) proximity condition may have been met (or satisfied);

[0277] A TTI or TTI length, for example, a TTI or TTI length that may have exceeded a threshold and / or may have met (or satisfied) a comparison condition or a proximity condition; and / or

[0278] An indication of a condition that may have triggered a report or indication (eg, triggered transmission of a report or indication).

[0279] The PV, PC, proximity (e.g., proximity of PV to PC), margin, and / or TTI that may be included in a report may be expressed in terms of one or more (e.g., an integer number of) time units. The PV, PC, proximity (e.g., proximity of PV to PC), margin, TTI, time unit, and / or multiple time units may be quantified and / or expressed by a value or index to a set, list, or table of values ​​(e.g., when determined, configured, provided, and / or reported).

[0280] In the embodiments described herein, the report or indication may be provided via at least one of RRC, MAC, or physical layer signaling. The WTRU may provide and / or the eNB may receive the report or indication via at least one of RRC, MAC, or physical layer signaling. The report or indication may be provided and / or received in at least one of: RRC signaling; MAC control element (e.g., MAC-CE); PUCCH; UL control information (UCI); and / or scheduling request (SR). The report or indication may be provided and / or received using a physical layer channel, which may correspond to a TTI for which the report or indication may be provided (e.g., a UL TTI). The report or indication may be provided and / or received using a physical layer channel, which may correspond to another TTI (e.g., a UL TTI), such as a longer TTI, such as a normal or regular TTI.

[0281] A report or indication such as described herein may be referred to as a proximity report or a margin report. A margin report may be a timing margin report or a UL timing margin report. A proximity report may be periodic, aperiodic and / or event triggered. The period of the report may be configured, for example, by the eNB. A proximity report may be triggered and / or transmitted, for example, in a TTI, when one or more of the following events occurs or may occur:

[0282] Configuration (e.g., configuration reception) of using a TTI (e.g., short TTI (sTTI));

[0283] Configuration or reconfiguration (e.g., reception of a configuration or reconfiguration) of a TTI or a TTI length (e.g., a short TTI or a TTI length);

[0284] The periodic timer expires or has expired;

[0285] The threshold comparison condition is met or can be met;

[0286] The proximity condition is met or can be met;

[0287] Receiving an aperiodic request for proximity reporting (e.g., in a DL control channel and / or a DCI or a DCI format);

[0288] For example, the PV, PC, or proximity change exceeds a threshold due to the transmission of a recent proximity report;

[0289] The threshold comparison condition has changed (eg, satisfied vs. not satisfied), for example, due to the transmission of a recent proximity report; and / or

[0290] The proximity condition may have changed (eg, satisfied versus not satisfied), for example, due to the transmission of a recent proximity report.

[0291] The WTRU may trigger and / or transmit a proximity report when one or more of the events identified above occurs or may occur (e.g., when the WTRU determines that one or more of these events may occur). The WTRU may trigger and / or transmit a proximity report when the WTRU receives a configuration to use a TTI (e.g., an sTTI) and / or when the WTRU receives a configuration or reconfiguration of a TTI or TTI length (e.g., an sTTI or TTI length). In another example, the WTRU may trigger and / or transmit a proximity report in response to receiving an aperiodic request for a proximity report.

[0292] The triggering and / or transmission may be conditioned on whether a timer (e.g., an inhibit timer, such as a proximity inhibit timer) has expired. When transmitting a proximity report, a timer may be turned on (e.g., set to 0 or a configurable maximum or termination value). For example, a timer may be used to avoid excessive proximity reports. A timer may be adjusted (e.g., incremented or decremented) in a TTI (e.g., each TTI). A timer (e.g., a decrementing timer) may terminate when a value may be 0. A timer (e.g., an incrementing timer) may terminate when a value reaches or exceeds a configurable maximum or termination value. The maximum or termination value may be a prohibit timer maximum or termination value.

[0293] The triggering and / or transmission may be conditional on whether there is space in the UL transmission (eg, PUSCH) for a proximity report (eg, which may be transmitted in a MAC-CE).

[0294] The WTRU may evaluate and / or determine whether an event may occur in or for a TTI (e.g., every TTI). The WTRU may trigger and / or transmit a proximity report in a TTI (e.g., in the TTI or for which the WTRU determines that an event occurs or may occur). The TTI may be a DL TTI or a UL TTI. The TTI may be an sTTI or a long or regular TTI.

[0295] Figure 5is an example of a proximity reporting method 500 according to one example that can be used in combination with any of the examples described herein. Figure 5 Each step of the method 500 is shown and described separately, but the steps may be performed in a different order than shown, in parallel with each other, or simultaneously with each other. For example, the WTRU performs Figure 5 However, the method may also be performed by any node (eg, eNB, AP or base station) operating in a wireless communication system. Figure 5 In the example of , the WTRU may receive a TTI configuration, which may be, for example, an sTTI configuration 501. The configuration may also include a threshold (e.g., close to a reporting threshold). The threshold may be defined according to the above examples. The WTRU may determine a PC 502 of the WTRU for a TTI or sTTI (e.g., for a TTI or sTTI configuration), which may include, for example, a maximum (max) TA, a maximum Rx-Tx time difference, or any parameter defined in the above examples. The WTRU may also report the PC to the eNB according to the above examples. The PC may be determined based on at least one processing criterion (e.g., a criterion). The processing criteria may include, but are not limited to: the TTI length or the number of symbols in a TTI that may be used and / or configured (e.g., in or according to a TTI configuration), the sTTI length (in UL and / or DL), the TBS of the PDSCH for which HARQ feedback may be sent in the UL sTTI, the channel type (PUSCH or PUCCH) on which HARQ may be sent in the UL sTTI, the time between the DL TTI or DL ​​sTTI for PDCCH and the UL TTI or UL sTTI for PUCCH or PUSCH, or any other processing criteria defined in the above examples. The WTRU may determine the PV 503, which may include, for example, a TA or an Rx-Tx time difference, or any of the parameters defined in the above examples. The WTRU may determine the proximity of the PV to the PC 504 (e.g., determining PC-PV). The WTRU may determine whether a proximity condition is met 505, which may, for example, include determining whether the proximity of the PV to the PC is less than a proximity reporting threshold. If the proximity condition is met, the WTRU may send a proximity report 506, which may include reporting PV, PC, and / or proximity based on the proximity condition being met. The WTRU may perform a proximity report 506 for a TTI or sTTI (e.g., UL TTI or sTTI). Figure 5After sending (or determining to send) the proximity report or if the proximity condition is not met, the WTRU may end (e.g., the process) or may repeat (e.g., the process) for another TTI or sTTI (e.g., the next TTI or sTTI) 507. When repeating, e.g., when the configuration (e.g., TTI configuration) has not changed, the WTRU may, for example, start from 503. When a new configuration may be received, the WTRU may start from 501.

[0296] Figure 6 is another example of a proximity reporting method 600 according to another example that can be used in combination with any of the examples described herein. Figure 6 Each step of method 600 is shown and described separately in FIG. 6 , but the steps may be performed in a different order than shown, in parallel with each other, or simultaneously with each other. For example, the WTRU performs Figure 6 However, the method may also be performed by any node (eg, eNB, AP or base station) operating in a wireless communication system. Figure 6 In the example of , the WTRU may receive a sTTI configuration 601. The configuration may also include a threshold (e.g., close to a reporting threshold). The threshold may be defined according to the above examples. The WTRU may determine at least one processing criterion (e.g., one processing criterion) 602 for the UL sTTI. The processing criteria may include, but are not limited to: the TTI length or the number of symbols in the TTI that may be used and / or configured (e.g., in or according to the TTI configuration), the sTTI length (in UL and / or DL), the TBS of the PDSCH (for which HARQ feedback may be sent in the UL sTTI), the channel type (PUSCH or PUCCH) on which the HARQ may be sent in the UL sTTI, the time between the DL sTTI for the PDCCH and the UL sTTI for the PUCCH or PUSCH, or any other processing criteria defined in the above examples. The WTRU may determine the PC of the WTRU based on at least one processing criterion 603, which may include, for example, a maximum TA or a maximum Rx-Tx time difference. The WTRU may also report the PC to the eNB. The WTRU may determine PV 604, which may include, for example, TA or Rx-Tx time difference. The WTRU may determine the proximity of PV to PC 605 (e.g., determining PC-PV). The WTRU may determine whether a proximity condition is met 606, which may, for example, include determining whether the proximity of PV to PC is less than a proximity reporting threshold. If the proximity condition is met, the WTRU may send a proximity report 607, which may include reporting PV, PC, and / or proximity based on the proximity condition being met. The WTRU may perform a TTI or sTTI (e.g., UL TTI or sTTI) for each WTRU. Figure 6After sending (or determining to send) the proximity report or if the proximity condition is not met, the WTRU may end (e.g., the process) or may repeat (e.g., the process) 608 for another TTI or sTTI (e.g., the next TTI or sTTI). When repeating, for example, when the configuration (e.g., TTI configuration) has not changed, the WTRU may, for example, start from 604. When a new configuration may be received, the WTRU may start from 601.

[0297] As described above, the WTRU may determine (or determine when) a condition may be met or satisfied (e.g., determine or determine when a condition may be true). For example, the condition may be at least one of: a threshold comparison condition, a proximity condition, an abnormal condition, a transmission suspension condition, etc. The WTRU may determine or determine when a condition may be satisfied in a TTI (e.g., every TTI) or for (e.g., at least one) TTI (e.g., every TTI). The terms meet and satisfy may be used interchangeably in the examples and embodiments described herein.

[0298] According to another embodiment, the WTRU may not perform at least some UL transmissions, for example, when an abnormal condition is met or may be met (e.g., when the WTRU determines that the abnormal condition is met or may be met). The abnormal condition may be or may include, but is not limited to, at least one of the following (or is the result of at least one of the following):

[0299] The PV reaches or may reach or exceed or may exceed a threshold value or PC (e.g., the PC may be a maximum value or maximum PV that may be supported, allowed and / or used);

[0300] The proximity of the PV to the PC indicates (e.g., by its value) that the PV may reach or exceed a threshold value or PC;

[0301] PC is or can be reached or exceeded;

[0302] PV is not or cannot be supported;

[0303] The PV is or may be below a threshold or PC (eg, the PV may be a minimum value or minimum PV that may be supported, allowed, or used); and / or

[0304] The proximity of the PV to the PC indicates (eg, by its value) that the PV may be below a threshold or the PC.

[0305] The transmission suspension condition may be or may include at least one of the following (or be the result of at least one of the following):

[0306] A timer (e.g., TAT) may be stopped, terminated, or deemed terminated, such as a timer that may be associated with at least some UL transmissions;

[0307] A timer (e.g., TAT) may be stopped, terminated or considered terminated, such as a timer that may be associated with (e.g., may be for) a TTI (e.g., TTI length) and / or a TAG;

[0308] At least some UL transmissions may be stopped or suspended, such as one or more UL transmissions that may be associated with (eg, may be for) a TTI (eg, a TTI length) and / or a TAG; and / or

[0309] A flag or indicator (eg, a transmission stop or pause flag or indicator) may indicate that at least some UL transmissions may not be performed, such as one or more UL transmissions that may be associated with (eg, may be for) a TTI (eg, TTI length) and / or a TAG.

[0310] When a transmission suspension condition is met or may be met (eg, when the WTRU determines that the transmission suspension condition is met or may be met), the WTRU may not perform some UL transmissions.

[0311] For example, the WTRU may determine and / or may evaluate whether the PV has reached or may reach a threshold value or PC, whether the PV has exceeded or may exceed a threshold value or PC (e.g., a PC that may be a maximum value), and / or whether the PV has or may be below a threshold value or PC (e.g., a PC that may be a minimum value). The WTRU may make such a determination based on the evaluation. The WTRU may determine or determine when the PV may reach (e.g., may be at or may be equal to), may exceed, or may be below a threshold value or PC, for example, based on the evaluation. The WTRU may make the evaluation and / or determination at or for at least one TTI. For example, the WTRU may make the evaluation and / or determination for a UL TTI. For example, the WTRU may make the evaluation and / or determination in a DL TTI that may be associated with a UL TTI. A TTI (e.g., a UL TTI) may be a TTI to which the PV and / or PC may be applied.

[0312] In another example, when the WTRU receives or makes an adjustment to the first PV or the second PV, the WTRU may make an evaluation and / or determination for the first PV. For example, when the WTRU receives an adjustment to the TA (e.g., applied TA) or when the WTRU adjusts the TA (e.g., applied TA), the WTRU may make an evaluation for the TA (e.g., applied TA). When the WTRU receives an adjustment to the TA (e.g., applied TA) or when the WTRU adjusts the TA (e.g., applied TA), the WTRU may make an evaluation for the Rx-Tx time difference.

[0313] In another example, the WTRU may make an evaluation and / or determination regarding the PV when the PV changes, for example, due to received and / or applied adjustments to the PV or due to timing (eg, receive and / or transmit timing) that may affect the PV.

[0314] In another example, the WTRU may determine the proximity of the PV to the PC. The WTRU may use the proximity of the PV to the PC (e.g., the determined proximity) to determine and / or evaluate or determine and / or evaluate when the PV reaches, exceeds, or falls below the PC, determine and / or evaluate that the PV reaches, exceeds, or falls below the PC, or determine and / or evaluate whether the PV reaches, exceeds, or falls below the PC. When the determined proximity is 0, the WTRU may determine (or determine when) the PV reaches the PC. When the determined proximity (e.g., PC-PV) is negative, the WTRU may determine (or determine when) the PV exceeds the PC. When the determined proximity (e.g., PC-PV) is positive, the WTRU may determine (or determine when) the PV is below (e.g., not exceeding) the PC. Alternatively, when the determined proximity (e.g., PV-PC) is positive, the WTRU may determine (or determine when) the PV may exceed the PC. When the determined proximity (e.g., PV-PC) may be negative, the WTRU may determine (or determine when) the PV may be below (e.g., may not exceed) the PC.

[0315] For example, when the WTRU determines that the condition is met, the WTRU may do one or more of the following:

[0316] Setting the PV to a specific value (e.g., a specific value for the PV), such as a threshold, a configured value, a maximum value, or a PC, such as capping the PV at a supported maximum value;

[0317] For example, stopping, suspending and / or not performing at least some UL transmissions for a TTI, a TTI length and / or a combination of UL and DL TTI lengths;

[0318] performing at least some UL transmissions, e.g., for another TTI, another TTI length, and / or another combination of UL and DL TTI lengths;

[0319] modifying at least some UL transmissions, e.g., for a TTI, a TTI length, and / or a combination of UL and DL TTI lengths;

[0320] Stopping a timer (e.g., TAT), such as a timer (e.g., TAT) that may be related to a TAG, a TTI length, and / or a combination of UL and DL TTI lengths;

[0321] a timer (e.g. TAT) is deemed to have expired, such as a timer (e.g. TAT) that may be related to a TAG, a TTI length and / or a combination of UL and DL TTI lengths;

[0322] performing one or more timer (e.g., TAT) termination actions, transmission stop actions, and / or transmission pause actions;

[0323] Setting (or clearing) a flag or indicator, for example, to indicate that the PV may have reached or exceeded the PC; Setting (or clearing) a flag or indicator, for example, to indicate that the PV may be below the PC;

[0324] Setting (or clearing) a flag or indicator (e.g., a transmission stop or pause flag or indicator), e.g., to indicate that at least some UL transmissions may not be performed, e.g., some UL transmissions for a TTI, a TTI length, and / or a combination of UL and DL TTI lengths;

[0325] For example, sending an error message and / or a proximity report using a transmission with a TTI length for which the condition may not be met (e.g., a longer TTI length); and / or

[0326] For example, PRACH transmission and / or random access procedure is used to send error messages or indications and / or proximity reports.

[0327] In some examples and implementations described herein, the terms set and clear may be interchangeable and still be consistent with the present disclosure.

[0328] In another embodiment, the WTRU may set the PV to a specific value, such as a threshold, a configured value, a maximum value, or a PC, for example, when a condition is or may be satisfied.

[0329] For conditions that may be met for PV, threshold and / or PC, the WTRU may, for example, set the PV to the threshold or PC. For example, when the TA (e.g., the applied TA) may reach or reach or may exceed or exceed the maximum TA, the WTRU may set or limit the TA (e.g., the applied TA) to the maximum TA.

[0330] For conditions that may be satisfied for PV, threshold and / or PC, the WTRU may, for example, set another PV to a specific value. For example, when the Rx-Tx time difference may reach or reach or may exceed or exceed the maximum Rx-Tx time difference, the WTRU may set the TA (e.g., the applied TA) to the maximum TA. Setting the TA to the maximum TA may keep the Rx-Tx time difference from exceeding the maximum Rx-Tx time difference.

[0331] For example, in a case where the WTRU may be configured to use a first TTI (e.g., a short TTI) for at least some transmissions (e.g., at least some UL transmissions (e.g., PUSCH and / or PUCCH transmissions)) and, for example, not use a second TTI (e.g., a normal TTI), the WTRU may set the PV to a specific value.

[0332] For example, the WTRU may use a first value for PV (e.g., a specific or capped value) in one time unit (e.g., a subframe), such as a time unit in which the WTRU may transmit using a first TTI (e.g., a short TTI), and may use a second value for PV (e.g., a normal or uncapped value) in another time unit (e.g., a subframe) in which the WTRU may transmit using a second TTI (e.g., a normal TTI). For example, the WTRU may apply a capped TA in one subframe, such as a subframe in which the WTRU may transmit using a first TTI (e.g., a short TTI), and may apply a non-capped TA in another subframe in which the WTRU may transmit using a second TTI (e.g., a normal TTI).

[0333] For example, when the WTRU determines that the TA (e.g., the applied TA) may exceed or exceed the maximum TA (applied TA), when the WTRU determines that the Rx-Tx time difference may exceed or exceed the maximum Rx-Tx time difference, and / or when the WTRU determines that the processing time may exceed or exceed the maximum processing time, the WTRU determines that the condition may be met or satisfied.

[0334] In another example, the WTRU may determine that a condition may be met or satisfied when the WTRU determines, for example, that a processing time that may be required or used (e.g., a minimum processing time) may exceed or exceed the available processing time (or the available processing time may be less than or less than the processing time or the minimum processing time that the WTRU may need or use).

[0335] In another example, the WTRU may determine that a condition may be met when the WTRU may determine that a TTI (e.g., TTI length) that may be determined, indicated, requested, and / or configured may be lower than a minimum TTI that the WTRU may support. The TTI may be an sTTI. The TTI may be a UL TTI and / or a DL TTI. The minimum TTI may be associated with a channel (e.g., a PUSCH and / or a PUCCH). The minimum TTI may be associated with a combination of a UL TTI and a DL TTI.

[0336] In another embodiment, the WTRU may stop, suspend, or not perform at least some UL transmissions (e.g., current, upcoming, and / or future UL transmissions), such as one or more UL transmissions for which TTIs and / or TTI lengths may apply PV and / or PC, for example, when a condition is or may be satisfied.

[0337] For example, for conditions that may be met or satisfied for PV and / or PC, the WTRU may not perform at least some UL transmissions for TTIs and / or TTI lengths for which PV and / or PC may be applied. The UL transmissions may include at least one of PUSCH, PUCCH, and / or SRS. The WTRU may not perform at least some UL transmissions starting from the current, upcoming, or next UL TTI (e.g., the current, upcoming, or next UL TTI (e.g., sTTI) for which PV and / or PC may be applied.

[0338] When PV and / or PC are applied to a first TTI and / or a first TTI length and / or a condition is met or may be met for the first TTI or the first TTI length, the WTRU may perform at least some UL transmissions, such as one or more UL transmissions for a second TTI and / or a second TTI length to which PV and / or PC may not be applied and / or to which the condition is not met or may not be met.

[0339] In embodiments described herein, when a condition is satisfied or may be satisfied (e.g., when the WTRU determines that the condition is satisfied or may be satisfied), the WTRU may at least one of:

[0340] stopping some (e.g. all) UL transmissions (e.g. of TTI length, e.g. of any TTI length), e.g. until a resumption condition is or can be met;

[0341] stopping some (e.g. all) UL transmissions of (e.g. any) TTI lengths (or DL / UL TTI length combinations) that meet or can meet the condition, e.g. until a resumption condition is met or can be met;

[0342] for a TTI in which a condition is or may be satisfied (e.g. in which or for which it can be determined that the condition may be satisfied), stopping some (e.g. all) UL transmissions of a (e.g. arbitrary) TTI length (or DL / UL TTI length combination);

[0343] Stopping some (eg, all) UL transmissions for (eg, any) channels that meet or can meet a condition, for example, until a recovery condition is met or can be met; and / or

[0344] Some (eg, all) UL transmissions for (eg, any) channels that satisfy or may satisfy a condition (eg, a TTI in which or for which it can be determined that the condition may be satisfied) are stopped.

[0345] Stopping and / or pausing transmission may also be referred to as skipping transmission, discarding transmission, not performing transmission, and / or not transmitting in this application. Therefore, in some examples and embodiments described in this application, stop, pause, skip, discard, not perform, and not transmit may be used interchangeably. Perform transmission and transmit may be used interchangeably. In some examples and embodiments, not transmit and 0 power transmission may be used interchangeably.

[0346] The UL transmissions that may be stopped may include current, upcoming or future UL transmissions.The WTRU may stop some UL transmissions, for example based on condition satisfaction, in a TTI (eg, the first TTI) in which the WTRU may determine that the condition may be satisfied and / or at the beginning of the TTI.

[0347] The WTRU may, for example, perform or resume some UL transmissions based on satisfying a resumption condition (eg, based on the WTRU determining that the resumption condition is satisfied).

[0348] A recovery condition may be satisfied (e.g., the WTRU may determine that a recovery condition is satisfied) when (e.g., when the WTRU determines that) at least one of the following may occur or may have occurred:

[0349] Reception of a TA command which may have been provided in a random access response, for example following a PRACH preamble transmission by the WTRU (where the PRACH transmission is triggered or indicated by a PDCCH order);

[0350] Receipt of a TA command that results in a condition no longer being met (e.g. a condition that may have been met);

[0351] The start or restart of a timer (eg, TAT), such as an associated timer (eg, TAT); and / or

[0352] Clear (or reset) a flag or indicator (eg, a transmission stop or pause flag or indicator). For example, when a flag or indicator (eg, a transmission stop or pause flag or indicator) is cleared or reset, the resume condition may be satisfied.

[0353] When the condition is not met (or is no longer met), the WTRU may perform or resume some UL transmissions, for example, one or more UL transmissions that the WTRU may have stopped based on the condition being met.

[0354] Alternatively or additionally, the WTRU may perform or not perform one or more UL transmissions based on the TTI length of the UL transmission. The WTRU may perform or not perform one or more UL transmissions based on the TTI length of the UL transmission and the TTI length of the associated DL transmission. The associated DL transmission for an UL HARQ transmission (e.g., on a PUCCH or PUSCH) may be the TTI length of the PDSCH over which the HARQ may be transmitted. The associated DL transmission for an UL data transmission (e.g., on a PUSCH) may be the TTI length associated with a DL control channel (e.g., a PDCCH) that may provide grant, allocation, or scheduling information for an UL data channel.

[0355] For example, the WTRU may be configured with and / or operate with a first TTI length and / or a second TTI length. The WTRU may cease transmissions (e.g., in the UL) that may use a first TTI length (e.g., sTTI) that satisfies or may satisfy a condition. The WTRU may perform transmissions (e.g., in the UL) that may use a second TTI length (e.g., nTTI) (e.g., a TTI length that does not satisfy the condition or a TTI length for which the condition or evaluation of the condition does not apply) or continue to perform transmissions (e.g., in the UL).

[0356] The WTRU may transmit (e.g., in UL) in at least one TTI (e.g., sTTI) (e.g., in the current or next TTI or starting, e.g., the current or next DL or UL TTI (e.g., sTTI) to which the condition and / or the PV or PC of the condition is applicable). The WTRU may not transmit (e.g., in UL) using a TTI length (e.g., sTTI).

[0357] Figure 7

[0063] An example method 700 of modifying an UL transmission when a condition is or may be satisfied according to another example that may be used in combination with any of the examples described herein. For example, when a condition (e.g., an abnormal condition) is or may be satisfied (e.g., a WTRU), the UL transmission may be modified. For example, the WTRU may delay the UL transmission (e.g., by a number of time samples or symbols). In another example, the WTRU may not transmit a portion of the UL transmission, which may include dropping or skipping a transmission of a number of time samples at the beginning of the transmission. Although shown and described separately Figure 7 Each step of the method 700 in FIG. 700 is described below, but multiple steps may be performed in a different order than shown, in parallel with each other, or simultaneously with each other. For example, the WTRU performs Figure 7 However, the method may also be performed by any node (eg, eNB, AP or base station) operating in a wireless communication system.

[0358] exist Figure 7In the example of , the WTRU may receive a TTI configuration 701, which may be, for example, an sTTI configuration. The configuration may also include a threshold. The threshold may be defined according to the above examples. The WTRU may determine a PC 702 for the WTRU configured for a TTI or sTTI, which may include, for example, a maximum TA, a maximum Rx-Tx time difference, or any parameter defined in the above examples. The WTRU may also report the PC to the eNB according to the above examples. The PC may be based on at least one processing criterion. The processing criteria may include, but are not limited to: a TTI length or the number of symbols in a TTI that may be used and / or configured (e.g., in or according to a TTI configuration), an sTTI length (in UL and / or DL), a TBS of a PDSCH (for which HARQ feedback may be sent in a UL sTTI for PDSCH), a channel type (PUSCH or PUCCH) on which HARQ may be sent in a UL sTTI, a time between a DL TTI or DL ​​sTTI for PDCCH and a UL TTI or UL sTTI for PUCCH or PUSCH, or any other criteria defined in the above examples. The WTRU may determine PV 703, which may include, for example, TA or Rx-Tx time difference, or any of the parameters defined in the above examples. The WTRU may then determine whether the PV exceeds or will exceed PC 704. Figure 7 In the example of , if the PV exceeds or will exceed the PC, the WTRU may modify its transmission to avoid exceeding the PC 705. For example, the WTRU may make modifications including, but not limited to, dropping (i.e., not transmitting) lower priority TTIs, channels, or transmission types. If the PV exceeds, may exceed, or will exceed the PC, the WTRU may also drop the first x time samples or symbols of the UL transmission, which may, for example, correspond to at least the PV-PC (e.g., the PV-PC is quantized into the second highest time unit that may skip transmissions). The WTRU may perform for a TTI or sTTI (e.g., a UL TTI or sTTI) Figure 7 After modifying (or determining to modify) its transmission to avoid exceeding the PC or if the PV has not exceeded or will not exceed the PC, the WTRU may end (e.g., the process) or may repeat (e.g., the process) for another TTI or sTTI (e.g., the next TTI or sTTI) 706. When repeating, such as when the configuration (e.g., TTI configuration) has not changed, the WTRU may, for example, start from 703. When a new configuration may be received, the WTRU may start from 701.

[0359] In another example, if the WTRU is capable of supporting a maximum TA or Rx-Tx time difference of x time samples and the current TA or Rx-Tx time difference is y time samples (e.g., y>x), the WTRU may not transmit the first z time samples or the first q symbols of an UL transmission, which may be an UL transmission for which at least one of the TA, maximum TA, Rx-Tx time difference, and / or maximum Rx-Tx time difference may apply. The UL transmission may be a transmission with a TTI (e.g., sTTI) that satisfies or may satisfy an abnormal condition (e.g., for TA or Rx-Tx time difference). For example, when y is greater than x, the WTRU may not transmit the first z time samples or the first q symbols.

[0360] The value of z may be yx. Alternatively, the value of z may be yx plus an offset (e.g., +1 or -1). The offset may be fixed or configured. The value of q may be the second highest integer number of symbols that may correspond to z. For example, the value of q may be CEIL[z / (number of time samples per symbol)].

[0361] The ceiling function CEIL[x] can map a number (eg, a real number) x to the smallest rounded-up integer. For example, CEIL[2.2] can be 3.

[0362] In another example, the processing time that the WTRU may need or may use may be y (e.g., PV may be equal to y). The available processing time may be x (e.g., PC may be equal to x). The WTRU may not transmit the first z (e.g., yx) time samples or the first q symbols of an UL transmission, e.g., an UL transmission for which processing time and / or available processing time apply. For example, when y is greater than x, the WTRU may not transmit the first z time samples or the first q symbols. The UL transmission may be a transmission with a TTI (e.g., sTTI) for which an abnormal condition (e.g., PV>PC) applies or may apply.

[0363] A timer (eg, TAT), a flag, and / or an indicator may be configured, provided, and / or used. The flag may be a transmission stop or pause flag. The indicator may be a transmission stop or pause indicator.

[0364] A timer (eg, TAT) may be associated with and / or configured for a TTI (eg, TTI length), such as a TTI (eg, TTI length) of a TAG. TAT may be used as a non-limiting example of a timer.

[0365] A flag or indicator (e.g., a stop or pause transmission flag or indicator) may be associated with and / or configured for a TTI (e.g., TTI length), such as a TTI of a TAG (e.g., TTI length). For example, the indicator may be or include a flag. The flag or indicator may be set to indicate stopping or pausing at least some UL transmissions, such as UL transmissions that may be associated with a TTI (e.g., TTI length).

[0366] The WTRU or (e.g., the WTRU's) MAC entity may have and / or maintain at least one timer and / or at least one indicator, which may be associated with and / or configured for a TTI (e.g., TTI length), such as a TTI (e.g., TTI length) of a TAG.

[0367] For example, when a condition may be met, the WTRU may stop the timer or consider the timer expired. The WTRU may stop the timer or consider the timer expired, for example, according to one or more examples and / or embodiments described herein.

[0368] The timer (e.g., TAT) termination action, transmission stop working, and / or transmission suspension action may be or may include at least one of the following:

[0369] flushing one or more (e.g. all) HARQ buffers for one or more TTIs or TTI lengths (e.g. all TTIs or TTI lengths) (e.g. a condition may be satisfied for this or a timer (e.g. TAT) may have expired);

[0370] flushing one or more (e.g. all) HARQ buffers for one or more TTIs or TTI lengths (e.g. all TTIs or TTI lengths except nTTI) (e.g. for TAGs for which a condition is or may be satisfied or a timer (e.g. TAT) may have expired);

[0371] Releasing and / or notifying RRC to release PUCCH (e.g. sPUCCH) and / or SRS (e.g. sSRS) for one or more TTIs or TTI lengths (e.g. all TTIs or TTI lengths) (e.g. a condition may be satisfied for this or a timer (e.g. TAT) may have expired);

[0372] Releasing and / or notifying RRC to release PUCCH (e.g., sPUCCH) and / or SRS (e.g., sSRS) for one or more TTIs or TTI lengths (e.g., all TTIs or TTI lengths except nTTI) (e.g., for TAGs for which a condition may be met or a timer (e.g., TAT) may have expired);

[0373] clearing one or more (e.g. any) DL assignments and / or one or more (e.g. any) UL grants, wherein the assignments and / or grants may be for one or more TTIs or TTI lengths (e.g. all TTIs or TTI lengths), for which, for example, a condition may be satisfied or a timer (e.g. TAT) may have expired; and / or

[0374] Clear one or more (e.g., any) DL assignments and / or one or more (e.g., any) UL grants, where the assignments and / or grants may be for one or more TTIs or TTI lengths (e.g., all TTIs or TTI lengths except nTTI), for example, for a TAG for which a condition may be met or a timer (e.g., TAT) may have expired.

[0375] One or more HARQ buffers may be associated with and / or used for a TTI or a TTI length. One or more portions of a HARQ buffer may be associated with and / or used for a TTI and / or a TTI length.

[0376] Clearing the HARQ buffer for a TTI or a TTI length may include at least one of:

[0377] Clearing a HARQ buffer (e.g., the entire HARQ buffer) that may be associated with and / or for a TTI or a TTI length;

[0378] Flushing a HARQ buffer (eg, the entire HARQ buffer) that may be at least partially associated with and / or for a TTI or a TTI length; and / or

[0379] Flushing the HARQ buffer may be associated with and / or used for a TTI or a TTI length.

[0380] The condition may be associated with (eg, may be directed to) at least one of: a TTI, a TTI length, a TAG, a channel, and / or a MAC entity.

[0381] For example, when a condition is or may be satisfied (e.g., when the WTRU determines that a condition is or may be satisfied) (e.g., for a TTI or TTI length), the WTRU may at least one of:

[0382] not performing at least some UL transmissions, for example, some (e.g., all) UL transmissions for at least one TTI or TTI length that may satisfy the condition;

[0383] not performing at least some UL transmissions, such as transmissions of one or more UL channels that may satisfy the condition;

[0384] not performing at least some UL transmissions, for example for a TTI or TTI length that may be shorter than a TTI or TTI length that satisfies the condition;

[0385] performing at least some UL transmissions, e.g., for a (e.g., another) TTI or TTI length for which the condition may not be met or may not apply; and / or

[0386] At least some UL transmissions are performed, for example, for (eg, another) TTI or TTI length, which may be nTTI and / or another TTI that may be longer than the TTI or TTI length that satisfies the condition.

[0387] The WTRU may determine whether a condition is met or may be met based on the TAG (e.g., for the TAG or separately for each TAG). The WTRU may stop one or more UL transmissions on the TAG where the condition is met or may be met. The WTRU may not stop one or more (e.g., all) UL transmissions on the TAG where the condition may not be met or may not apply.

[0388] The UL transmission may be a current, upcoming, or future UL transmission. For example, the WTRU may determine, for example, for a TAG, that UL transmissions may be suspended for a TTI length (e.g., sTTI). For example, the UL transmission may be suspended when an associated timer expires or may expire or an associated suspension transmission indicator is set or may be set. The WTRU may make a determination in a TTI or for a TTI (e.g., an upcoming UL TTI). If the WTRU determines that the UL transmission is suspended, the WTRU may skip the UL transmission for that sTTI for that TAG.

[0389] In another example, the WTRU may perform some (eg, all) UL transmissions of a TTI or TTI length when a timer associated with the TTI or TTI length is not stopped (eg, when the timer may be running).

[0390] Figure 8 is an example of a transmission pause method 800 according to another example that can be used in combination with any of the examples described herein. Figure 8 Each step of the method 800 in FIG. 800 may be performed in a different order than shown, in parallel with each other, or simultaneously with each other. For example, the WTRU performs Figure 8 However, the method may also be performed by any node (eg, eNB, AP or base station) operating in a wireless communication system. Figure 8In the example of , the WTRU may receive a TTI configuration 801, which may be, for example, an sTTI configuration. The configuration may also include a threshold. The threshold may be defined according to the above examples. The WTRU may determine a PC 802 for the WTRU configured for a TTI or sTTI, which may include, for example, a maximum TA, a maximum Rx-Tx time difference, or any parameter defined in the above examples. According to the above examples, the WTRU may also report the PC to the eNB. The PC may be based on at least one processing criterion. The processing criteria may include, but are not limited to: a TTI length or the number of symbols in a TTI that may be used and / or configured (e.g., in or according to a TTI configuration), an sTTI length (in UL and / or DL), a TBS of a PDSCH (for which HARQ feedback may be sent in an UL sTTI), a channel type (PUSCH or PUCCH) on which HARQ may be sent in an UL sTTI, a DL TTI or DL ​​sTTI for a PDCCH and a UL TTI or UL sTTI for a PUCCH or PUSCH, or any other processing criteria defined in the above examples. The WTRU may determine the PV 803, which may include, for example, the TA or the Rx-Tx time difference, or any of the parameters defined in the above examples. The WTRU may then determine whether the PV is greater than the PC 804. If the PV is greater than the PC, the WTRU may suspend at least some or all UL transmissions for the TTI or sTTI 805. For example, the suspension of UL transmissions may apply to TAGs where the PV is greater than the PC. If the PV is greater than the PC, the WTRU may send a report or initiate a random access procedure by transmitting a preamble on the PRACH.

[0391] The WTRU may perform a TTI or sTTI (e.g., UL TTI or sTTI). Figure 8 After suspending (or determining to suspend) at least some or all UL transmissions for a TTI or sTTI or if the PV is not greater than the PC, the WTRU may end (e.g., the process) or may repeat (e.g., the process) 806 for another TTI or sTTI (e.g., the next TTI or sTTI). When repeating, the WTRU may, for example, start from 803 when there is no change in the configuration (e.g., the TTI configuration). The WTRU may start from 801 when a new configuration may be received.

[0392] Fig. 9 is another example 900 of a transmission pause method according to another example that can be used in combination with any of the examples described herein. Although shown and described separately Fig. 9 Each step of the method 900 in FIG. 1 may be performed in a different order than shown, in parallel with each other, or simultaneously with each other. For example, the WTRU performs Fig. 9However, the method may also be performed by any node (eg, eNB, AP or base station) operating in a wireless communication system.

[0393] exist Fig. 9 In the example of , the WTRU may receive a TTI configuration 901, which may be, for example, an sTTI configuration. The configuration may also include a threshold. The threshold may be defined according to the above examples. The WTRU may determine a PC 902 for the WTRU configured for a TTI or sTTI, which may include, for example, a maximum TA, a maximum Rx-Tx time difference, or any parameter defined in the above examples. The PC may be based on at least one processing criterion. The processing criteria may include, but are not limited to: sTTI length (in UL and / or DL), TBS of the PDSCH (for which HARQ feedback may be sent in the UL sTTI), the channel type (PUSCH or PUCCH) on which the HARQ may be sent in the UL sTTI, the time between the DL TTI or DL ​​sTTI for the PDCCH and the UL TTI or UL sTTI for the PUCCH or PUSCH, or any other processing criteria defined in the above examples. The WTRU may determine a PV 903, which may include, for example, a TA or an Rx-Tx time difference, or any parameter defined in the above examples. The WTRU may then determine whether the PV is greater than the PC 904. If the PV is greater than the PC, the WTRU may suspend at least some or all UL transmissions for the TTI or sTTI 905. For example, the suspension of UL transmissions may apply to TAGs where the PV is greater than the PC. The WTRU may also consider the TTI or sTTI TAT to have expired and / or set a TTI or sTTI transmission suspension indicator 906. For example, considering the TTI or sTTI TAT to have expired and / or setting a TTI or sTTI transmission suspension indicator may apply to TAGs where the PV is greater than the PC. The WTRU may perform one or more TAT termination or transmission suspension actions for the TTI or sTTI 907. For example, performing one or more TAT termination or transmission suspension actions for the TTI or sTTI may apply to TAGs where the PV is greater than the PC. The WTRU may perform for a TTI or sTTI (e.g., a UL TTI or sTTI) Fig. 9 After the above steps or if the PV is not greater than the PC, the WTRU may end (e.g., the process) or may repeat (e.g., the process) for another TTI or sTTI (e.g., the next TTI or sTTI) 908. When repeating, the WTRU may, for example, start from 903 when there is no change in the configuration (e.g., TTI configuration). The WTRU may start from 901 when a new configuration may be received.

[0394] Fig.10is another example 1000 of a transmission suspension method when a suspension condition is met according to another example that can be used in combination with any of the examples described herein. Fig.10 Each step of the method 1000 in FIG. 1000 may be performed in a different order than shown, in parallel with each other, or simultaneously with each other. For example, the WTRU performs Fig.10 However, the method may also be performed by any node (eg, eNB, AP or base station) operating in a wireless communication system.

[0395] The suspension condition may be true when at least one of the following is true for the TAG: at least one UL transmission (e.g., all UL transmissions) is suspended (e.g., for a TTI), the TAT (e.g., for a TTI) is terminated, and a transmission suspension indicator (e.g., for a TTI) is set. Fig.10 In an example, the WTRU may determine whether a pause condition is true for a TTI 1001. If the pause condition is true for a TTI or sTTI, the WTRU may not transmit at least some or all UL transmissions for the TTI or sTTI 1002. For example, discarding transmissions may be applied to the TAG where the pause condition is true. If the pause condition is not true for the TTI or sTTI, the WTRU may allow transmissions to proceed and prepare transmissions of PUSCH, PUCCH and / or SRS for the TTI or sTTI 1003. For example, allowing transmissions to proceed and preparing transmissions may be applied to the TAG where the pause condition is not true. The WTRU may end the process or repeat the process for another TTI or sTTI (e.g., the next TTI or sTTI) 1004.

[0396] In another embodiment, the WTRU may prioritize one transmission over another, for example to avoid satisfying conditions such as: a first TTI (e.g., TTI length) may take precedence over a second TTI (e.g., TTI length); a transmission of a first TTI (e.g., TTI length) may take precedence over a transmission of a second TTI (e.g., TTI length); a first channel (e.g., PUCCH) type may take precedence over a second channel type (e.g., PUSCH); a transmission of a first channel type (e.g., PUCCH) may take precedence over a transmission of a second channel type (e.g., PUSCH); and / or a first transmission type (e.g., UCI, such as HARQ feedback) may take precedence over a second transmission type (e.g., data).

[0397] For example, when the first TTI length has a higher priority than the second TTI length, transmission of the first TTI length may be transmitted, and transmission of the second TTI length may be discarded (eg, not performed).

[0398] In another example, for example, when the transmission of the first TTI length and / or the preparation of the transmission of the first TTI length may result in the satisfaction of a condition (e.g., an abnormal condition) (where the condition is satisfied for the second TTI length), the transmission of the first TTI length may be transmitted and the transmission of the second TTI length may be discarded. Alternatively, for example, when the priority of the second TTI length may be higher than the first TTI length, the transmission of the second TTI length may be transmitted and the transmission of the first TTI length may be discarded. The first TTI length may be, for example, nTTI and the second length may be sTTI, or vice versa.

[0399] In another example, the WTRU may transmit or may be scheduled to transmit UCI (e.g., HARQ feedback) and data. The WTRU may transmit or may be scheduled to transmit UCI and data on a PUSCH (e.g., the same PUSCH). If processing of the PUSCH may result in a condition being met (e.g., an abnormal condition), the WTRU may discard (e.g., not transmit) the data and / or may not transmit the PUSCH. The WTRU may transmit UCI on the PUCCH.

[0400] In another example, the WTRU may receive a PDSCH for which the WTRU may generate UCI (e.g., HARQ feedback). The WTRU may transmit UCI on the PUCCH or PUSCH. The WTRU may receive an allocation or scheduling grant for the PUSCH before the time when the WTRU may transmit UCI and / or HARQ feedback. The PUSCH may be transmitted before, at least partially overlapping, or after the WTRU may transmit UCI, for example, according to the allocation or grant. For example, when preparing UL data for PUSCH transmission and / or PUSCH transmission results in a condition being met (e.g., an abnormal condition), the WTRU may not prepare UL data for PUSCH transmission and / or may not transmit PUSCH. The condition may be met for a TTI in which UCI may be transmitted or for a TTI length for UCI transmission. For example, when there is no PUSCH transmission (e.g., for data) when UCI and / or HARQ feedback may be transmitted, the WTRU may transmit UCI on the PUCCH.

[0401] The WTRU may provide an indication, for example, in a PUCCH transmission, indicating that PUSCH may be dropped and / or conditions (eg, abnormal conditions) may be met, for example, for a TTI of the PUCCH transmission.

[0402] One or more processing capabilities may or may not be applicable in a cell. For example, in a small cell, a short TA may be used for cell edge WTRUs. Some (eg, all) WTRUs in a small cell may support a maximum TA.

[0403] The eNB may provide an indication to indicate whether a PC (e.g., one or more PCs) is applicable in a cell. The indication may be provided in signaling (e.g., RRC signaling and / or broadcast signaling). The indication may be provided in system information (e.g., in a SIB). The eNB may provide the indication to at least one WTRU. The eNB may configure the WTRU with an indication, such as an indication of whether a PC is applicable.

[0404] The WTRU may receive an indication, such as provided and / or configured by an eNB. When applying PC, the WTRU may consider, determine and / or use at least one of: PV, PC, proximity and / or proximity reporting. When applying PC, the WTRU may use an indication that may be provided and / or configured (e.g., by an eNB).

[0405] As described above, a TA command in subframe n may be applied in subframe n+x, where, for example, x may be 6. For a TTI length equal to a subframe, a TA command may be applied in subframe n+x (eg, at the beginning thereof).

[0406] For TA commands that may be received in a TTI of length shorter than 1 subframe, the TA command may (e.g. still) be considered to be received in a subframe. For example, this may be useful for applying TA at subframe rates (e.g. at subframe boundaries) to allow the use of mixed TTI lengths so that there is no impact on TA application.

[0407] For a TA command that may be received (e.g., by a WTRU) in a TTI or TTI length (e.g., any TTI or TTI length) in subframe n, the TA command may be applied in subframe n+y, e.g., at the beginning of subframe n+y. The value of y may be x (e.g., 6).

[0408] The value of y may be a function of at least one of: a TTI length (eg, DL and / or UL TTI length) that may be configured and / or used; a PC, such as a maximum TA value in a cell; and / or a distance (eg, a time difference) between a DL TTI and a UL TTI.

[0409] The value of y may be fixed or configured, (eg, for a TTI length or a set of TTI lengths). The value of y may be indicated using a TA command.

[0410] For example, for TTI lengths less than or equal to a time period such as a time slot (eg, 0.5 ms), y may be a fixed or configured value (eg, 3).

[0411] The WTRU may receive more than one TA command that may be applied in subframe z, for example according to the n+y application rule. The WTRU may consider the reception of multiple TA commands in the same subframe as an error. The WTRU may apply one of the received TA commands, for example the earliest received TA command or the last received TA command. The WTRU may apply one of the received TA commands, for example according to the WTRU implementation. The WTRU may apply a combination of the received TA commands (e.g., and).

[0412] For example, subframe n+y may be the first subframe of at least k TTIs after subframe n. In another example, subframe n+y may be the first subframe of at least k TTIs after the TTI in which the TA command is received. The value of k may be a function of at least one of: a TTI length (e.g., DL and / or UL TTI length) that may be configured and / or used; a PC, such as a maximum TA value in a cell; and / or a distance between a DL TTI and a UL TTI.

[0413] Although the features and elements are described above in specific combinations, it will be appreciated by those skilled in the art that each feature or element can be used alone or in combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium to be executed by a computer and / or processor. Examples of computer-readable media include electronic signals (transmitted via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memories (ROMs), random access memories (RAMs), registers, buffer memories, semiconductor memory devices, magnetic media (e.g., internal hard disks and removable disks), magneto-optical media, and / or optical media (e.g., CD-ROM disks and / or digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, a terminal, a base station, an RNC, and / or any host computer.

Claims

1. A method for use in a wireless transmit / receive unit (WTRU), the method comprising: receiving downlink control information (DCI) indicating an uplink grant; Based on the uplink grant, determining a start time for a physical uplink shared channel (PUSCH) transmission; determining available processing time associated with the PUSCH transmission; as well as The PUSCH transmission is transmitted in case the determined start time of the PUSCH transmission is later than an uplink symbol time that is at least the determined available processing time after the end of the time unit at the end of the DCI. 2 . The method of claim 1 , wherein the determination of the available processing time is based on a timeline value indicated by the DCI.

3. The method of claim 1 , wherein the determination of the available processing time is based on a processing capability (PC) of the WTRU.

4. The method of claim 3, wherein the PC of the WTRU comprises a processing time capability of the WTRU. The method of claim 3 , wherein the PC corresponds to a number of symbols. The method of claim 3 , wherein the PC is based on the PUSCH transmission. The method of claim 1 , wherein the start of the PUSCH transmission is based on a timing advance (TA).

8. A wireless transmit / receive unit (WTRU), the WTRU comprising: transceiver; as well as a processor operably coupled to the transceiver; wherein: The transceiver is configured to receive downlink control information (DCI) indicating an uplink grant; The processor is configured to determine a start time of a physical uplink shared channel (PUSCH) transmission based on the uplink grant; The processor is configured to determine available processing time associated with the PUSCH transmission; and The transceiver and the processor are configured to transmit the PUSCH transmission if the determined start time of the PUSCH transmission is later than an uplink symbol time, the uplink symbol time being at least the determined available processing time after the end of the time unit at the end of the DCI.

9. The WTRU of claim 8, wherein the determination of the available processing time is based on a timeline value indicated by the DCI.

10. The WTRU of claim 8, wherein the determination of the available processing time is based on a processing capability (PC) of the WTRU.

11. The WTRU of claim 10, wherein the PC of the WTRU comprises a processing time capability of the WTRU.

12. The WTRU of claim 10, wherein the PC corresponds to a number of symbols.

13. The WTRU of claim 10, wherein the PC is based on the PUSCH transmission.

14. The WTRU of claim 8, wherein the start of the PUSCH transmission is based on a timing advance (TA).

15. A base station, comprising: transceiver; as well as a processor operably coupled to the transceiver; wherein: The transceiver and the processor are configured to transmit downlink control information (DCI) including an uplink grant; as well as The transceiver is configured to receive a physical uplink shared channel (PUSCH) transmission scheduled by the uplink grant, wherein a start time of the PUSCH transmission is later than an uplink symbol time, wherein the uplink symbol time is at least an available processing time after an end of a time unit at an end of the DCI, wherein the available processing time is associated with the PUSCH transmission. The base station of claim 15 , wherein the available processing time is based on a timeline value indicated by the DCI.

17. The base station of claim 15, wherein the available processing time is based on a processing capability (PC) of the WTRU.

18. The base station of claim 17, wherein the PC of the WTRU comprises a processing time capability of the WTRU.

19. The base station of claim 17, wherein the PC corresponds to a number of symbols.

20. The base station of claim 17, wherein the PC is based on the PUSCH transmission scheduled by the uplink grant.

21. The base station of claim 15, wherein the start of the PUSCH transmission is based on a timing advance (TA).

Images