Methods, architectures, devices and systems for discontinuous reception and logical channel prioritization for HARQ state information based on L1 indication

Abstract

In an embodiment, a method implemented in a wireless transmit / receive unit is described herein. The method may include receiving configuration information indicating: (1) a downlink control information (DCI)-based indication of a hybrid automatic repeat request (HARQ) state, and (2) a first HARQ state associated with a HARQ process. The method may include performing a first discontinuous reception (DRX) operation based on the first HARQ state. The method may comprise: receiving DCI; and determining that the DCI may indicate a second HARQ state associated with the HARQ process based on configuration information indicating that a DCI-based indication of the HARQ state may be enabled. The method may include performing a second DRX operation associated with the HARQ process based on the second HARQ state.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims the benefit of U.S. patent application No. 63 / 410,791, filed on September 28, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to the fields of communications, software, and coding, including methods, architectures, devices, and systems for, for example, discontinuous reception (DRX) and logical channel prioritization (LCP). Background Art

[0004] Non-terrestrial networks (NTNs) can facilitate the deployment of wireless networks in areas where land-based antennas may be impractical, for example, due to geography or cost. For example, NTNs can be coupled with terrestrial networks to enable coverage of the Third Generation Partnership Project (3GPP) 5G network. Initial 3GPP Rel-17 NTN deployments can support basic calls and texts. It is expected that further releases combined with the proliferation of next-generation low-orbit satellites can enable enhanced services such as web browsing. The embodiments described herein are designed with the above in mind. Summary of the invention

[0005] Methods, architectures, devices, and systems are described herein for adaptive DRX and LCP based on either downlink control information (DCI) and a physical layer (L1) based indication of whether hybrid automatic repeat request (HARQ) feedback is enabled or disabled. In an embodiment, a method may be implemented in a wireless transmit / receive unit (WTRU). The method may include receiving downlink control information indicating HARQ state information, and performing discontinuous reception (DRX) based on the HARQ state information. In an embodiment, the WTRU may be configured to receive downlink control information indicating HARQ state information, and perform DRX based on the HARQ state information.

[0006] In an embodiment, a method implemented in a WTRU is described herein. The method may include receiving configuration information indicating (1) a DCI-based indication of a HARQ state and (2) a first HARQ state associated with a HARQ process. The method may include: performing a first DRX operation based on the first HARQ state. The method may include: receiving a DCI; and determining, based on the configuration information, that the DCI may indicate a second HARQ state associated with the HARQ process, the configuration information indicating that the DCI-based indication of the HARQ state may be enabled. The method may include: performing a second DRX operation associated with the HARQ process based on the second HARQ state.

[0007] In an embodiment, a WTRU is described herein, the WTRU comprising a processor and a transmitter and a receiver (e.g., a transceiver) operably coupled to the processor. The WTRU may be configured to receive configuration information indicating (1) a DCI-based indication of a HARQ state and (2) that downlink HARQ feedback may be disabled for a HARQ process. The WTRU may be configured to perform a first discontinuous reception (DRX) operation with downlink HARQ feedback disabled. The WTRU may be configured to receive a DCI and determine based on the configuration information that the DCI may indicate that downlink HARQ feedback may be enabled for the HARQ process, the configuration information indicating that the DCI-based indication of the HARQ state may be enabled. The WTRU may be configured to perform a second DRX operation with downlink HARQ feedback enabled, wherein monitoring to receive retransmissions may be delayed based on a WTRU to base station round trip time. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] A more detailed understanding may be obtained from the following detailed description given by way of example in conjunction with the accompanying drawings. As with the detailed description, each of the figures in such drawings is an example. Therefore, the figures (figures) and detailed description should not be considered limiting, and other equally effective examples are possible and possible. In addition, the same reference numerals ("labels") in the various figures indicate the same elements, and wherein:

[0009] Figure 1A is a system diagram illustrating an example communication system;

[0010] Figure 1B It shows that it can be Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within a communication system is shown;

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

[0012] Figure 1D It shows that it can be Figure 1A A system diagram of yet another example RAN and yet another example CN used within the communication system shown;

[0013] Figure 2 is a system diagram showing examples of different interfaces in a non-terrestrial network;

[0014] Figure 3 is a diagram illustrating an example of a user plane and a control plane protocol stack for a transparent payload system;

[0015] Figure 4 is a system diagram illustrating an example of DRX adaptation based on HARQ feedback state and HARQ feedback mode;

[0016] Figure 5 is a system diagram showing an example of LCP adaptation;

[0017] Figure 6 is a system diagram illustrating an example method for adaptive DRX based on L1 indication;

[0018] Figure 7 is a system diagram illustrating an example method for adaptive DRX based on L1 indication;

[0019] Figure 8 is a diagram illustrating an example method for adaptive DRX based on L1 indication; and

[0020] Fig. 9 is a diagram illustrating an example method for adaptive DRX based on L1 indication. DETAILED DESCRIPTION

[0021] In the following detailed description, many specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples can be practiced without some or all of the specific details set forth herein. In other cases, well-known methods, programs, components and circuits are not described in detail to avoid blurring the following description. In addition, the embodiments and examples not specifically described herein can replace the embodiments and other examples explicitly, implicitly and / or inherently described, disclosed or otherwise provided (collectively referred to as "providing") herein to practice or practice in combination with them. Although various embodiments in which equipment, systems, devices, etc. and / or any of its elements perform operations, processes, algorithms, functions, etc. and / or any part thereof are described and / or claimed herein, it should be understood that any embodiment described and / or claimed herein assumes that any equipment, systems, devices, etc. and / or any of its elements are configured to perform any operations, processes, algorithms, functions, etc. and / or any part thereof.

[0022] Example Communication System

[0023] The methods, devices, and systems provided herein are well suited for communications involving wired and wireless networks. Figures 1A to 1D An overview of various types of wireless devices and infrastructure is provided in which various elements of the network can utilize, perform, be arranged according to, and / or be adapted and / or configured for the methods, devices, and systems provided herein.

[0024] Figure 1A is a system diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through shared system resources including wireless broadband. For example, the communication system 100 may employ one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail (ZT) unique word (UW) discrete Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, 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, an air access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include (or be) a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated process chain), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, 102d may be interchangeably referred to as a UE.

[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 wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to, for example, facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the network 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a master Node-B (HNB), a master eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0027] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of a licensed spectrum and an unlicensed spectrum. A cell may provide coverage of wireless services to a specific geographic area that may be relatively fixed or may vary over time. The cell may also be divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology, and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and / or receive signals 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 air access technology (RAT).

[0029] More specifically, as described above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Air 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 Packet Access (HSDPA) and / or High Speed ​​Uplink 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-A Pro).

[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as New Radio (NR) that may use NR air interface access to establish the air interface 116.

[0032] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple air interface access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE air interface access and NR air interface access, for example, using dual connectivity (DC) principles. Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of air interface access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0033] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0034] Figure 1A The base station 114b in the example may be, for example, a wireless router, a master Node-B, a master eNode-B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-a, LTE-a Pro, NR, etc.) to establish any of a small cell, a pico cell, or a femto cell. As Figure 1A As shown, base station 114b may be directly connected to Internet 110. Therefore, base station 114b may not need to access Internet 110 via 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 perform high-level security functions, such as user authentication. Although Figure 1ANot shown, but it will be appreciated that the RAN 104 / 113 and / or 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, which may be utilizing an NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs any of GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technologies.

[0036] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may use the same RAT as the RAN 104 / 114 or a different RAT.

[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 for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0038] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other elements / 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, etc. 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, but it will be appreciated that the processor 118 and the transceiver 120 may be integrated together, such as in an electronic package or chip.

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

[0041] Although the transmit / receive element 122 is Figure 1B Although depicted as a single element in the figure, the WTRU 102 may include any number of transmit / receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

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

[0043] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from: a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on 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 the power to and / or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[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) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of receiving signals from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0046] The processor 118 may also be coupled to other components / peripherals 138, which may include one or more software and / or hardware modules / units that provide additional features, functionality, and / or wired or wireless connectivity. For example, the components / peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (e.g., for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. Components / peripherals 138 may include one or more sensors, which may be 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 transmission and reception of some or all of the signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via hardware (e.g., choke) or signal processing via a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio in which transmission and reception of some or all of the signals (e.g., associated with specific subframes for both uplink (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0048] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c 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, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an 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 receive wireless signals from, the WTRU 102a.

[0050] Each of the eNode-Bs 160a, 160b, and 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 uplink (UL) and / or downlink (DL), etc. Figure 1C As shown, 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 (PGW) 166. While each of the foregoing elements is depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

[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 and from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-eNode-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

[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 may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0056] Although the WTRU Figures 1A to 1D Although depicted as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may (eg, temporarily or permanently) employ a wired communications interface with a communications network.

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

[0058] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) associated with the AP. The AP may access a distribution system (DS) or another type of wired / wireless network that loads traffic into and / or out of the BSS or has an interface thereto. Traffic originating from outside the BSS to the STA may be reached by the AP and may be delivered to the STA. Traffic from the STA to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be sent by the AP, for example, where the source STA may send traffic to the AP, and the AP may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be sent between the source STA and the destination STA using a direct link setup (DLS) (e.g., directly sent between them). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0059] When using the 802.11ac infrastructure mode of operation or a similar mode of operation, the AP can transmit a beacon on a fixed channel, such as a primary channel. The primary channel can be a fixed width (e.g., a 20 MHz wide bandwidth) or a width dynamically set via signaling. The primary channel can be an operating channel of the BSS and can be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access-collision avoidance (CSMA / CA) can be implemented, for example, in an 802.11 system. For CSMA / CA, STAs (e.g., each STA) including the AP can sense the primary channel. If the primary signal is sensed / detected by a particular STA and / or is determined to be busy, the particular STA can back off. One STA (e.g., only one station) can transmit in a given BSS at any given time.

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

[0061] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels, or by combining two discontinuous 80MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, the data can be passed through a fragment parser after channel coding, which can divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing can be performed on each stream respectively. The stream can be mapped to two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the above-mentioned operation of the 80+80 configuration can be reversed, and the combined data can be sent to a media access control (MAC) layer, an entity, etc.

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

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

[0064] In the United States, the available frequency band that can be used by 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. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0065] Figure 1D1 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. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the WTRUs 102a, 102b, 102c. Thus, for example, the gNB 180a may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be located on an unlicensed spectrum, while the remaining component carriers may be located 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 sets. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).

[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 also accessing other RANs (e.g., such as the eNode Bs 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 with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the eNode-B 160a, 160b, 160c. For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may serve 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 for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0070] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least two session management functions (SMFs) 183a, 183b, and at least one data network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[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 serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing, for example, to customize CN support for the WTRU 102a, 102b, 102c based on the type of service the WTRU 102a, 102b, 102c is utilizing. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies (such as LTE, LTE-A, LTE-A Pro) and / or non-3GPP access technologies (such as Wi-Fi).

[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 configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0073] The UPF 184a, 184b may be connected via the N3 interface to one or more of the gNBs 180a, 180b, 180c in the RAN 113, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, for example, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184a, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, 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) 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 local data networks (DNs) 185a, 185b via the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0075] Given that Figures 1A to 1D and Figures 1A to 1D 102a to 102d, base stations 114a to 114b, eNode-Bs 160a to 160c, MMEs 162, SGWs 164, PGWs 166, gNBs 180a to 180c, AMFs 182a to 182b, UPFs 184a to 184b, SMFs 183a to 183b, DNs 185a to 185b, and / or any other elements / devices described herein. A simulation device may be one or more devices configured to simulate one or more or all of the functions described herein. For example, a simulation device 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 of other devices in a laboratory environment and / or an operator network environment. For example, one or more simulation devices can perform one or more or all functions when fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices can perform one or more or all functions when temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device can be directly coupled to another device for testing purposes, and / or can use over-the-air wireless communication to perform testing.

[0077] One or more simulation devices can perform one or more (including all) functions when not implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used for testing scenarios in a test laboratory and / or a wired and / or wireless communication network that is not deployed (e.g., testing) to implement testing of one or more components. One or more simulation devices can be test equipment. The simulation device can use direct RF coupling and / or wireless communication via RF circuits (e.g., which can include one or more antennas) to transmit and / or receive data.

[0078] Throughout the embodiments described herein, the terms "serving base station", "base station", "gNB" are collectively referred to as "gNB" and may be used interchangeably to designate any network element, such as, for example, a network element acting as a serving base station. The embodiments described herein are not limited to gNBs and are applicable to any other type of base station.

[0079] For clarity, throughout the embodiments described herein, satisfying, failing to satisfy conditions (e.g., criteria), and "configuration condition parameters" are described relative to thresholds (e.g., greater than or less than a threshold), values ​​(e.g., thresholds), configuration values ​​(e.g., thresholds), etc. For example, satisfying a condition (e.g., a criterion) may be described as being above a value (e.g., a threshold), and failing to satisfy a condition (e.g., a criterion) may be described as being below a value (e.g., a threshold). The embodiments described herein are not limited to conditions (e.g., criteria) based on thresholds. Any variety of other conditions and parameters (e.g., belonging to or not belonging to a range of values) may be applicable to the embodiments described herein.

[0080] Throughout the embodiments described herein, (e.g., configuration) information may be described as being received by the WTRU from the network, such as through system information or via any kind of protocol message. Although not explicitly mentioned throughout the embodiments described herein, the same (e.g., configuration) information may be pre-configured in the WTRU (e.g., via any kind of pre-configuration method, such as via factory settings) so that the (e.g., configuration) information can be used by the WTRU without being received from the network.

[0081] Throughout the embodiments described herein, the expression “the WTRU may be configured with a set of parameters” is equivalent to or may be used interchangeably with “the WTRU may receive configuration information indicating a set of parameters (e.g., received from another network element (e.g., gNB)”. Throughout the embodiments described herein, the expression “the WTRU may report something” and “the WTRU may be configured to report something” is equivalent to or may be used interchangeably with “the WTRU may transmit (e.g., report) information indicating something”.

[0082] Examples of non-terrestrial networks

[0083] Non-terrestrial networks (NTNs) can facilitate the deployment of wireless networks in areas where land-based antennas may be impractical, for example, due to either geography and cost. For example, NTNs can be coupled with terrestrial networks to achieve coverage of (e.g., truly ubiquitous) 5G networks. Initial Rel-17 NR NTN deployments can support (e.g., basic) calls and texts. It is expected that further releases combined with the proliferation of next-generation low-orbit satellites can enable enhanced services, such as, for example, web browsing.

[0084] The NTN may include either an airborne or spaceborne platform that may transmit (e.g., transmit) signals received from a land-based gNB to a WTRU via a gateway (GW), and vice versa. The Rel-17 NR NTN supports power class 3 WTRUs with omnidirectional antennas and linear polarization, or very small aperture antenna (VSAT) terminals with directional antennas and circular polarization. Support for LTE-based narrowband IoT (NB-IoT) and enhanced machine type communication (eMTC) type devices may be standardized in Rel-17 based on recommendations from 3GPP TR 36.736 “Solutions for NR support of non-terrestrial networks (NTN)” v16.1.0. For example, any Rel-17 NTN WTRU may be a global navigation satellite system (GNSS) capable of any device type.

[0085] Aerial and / or satellite-borne platforms can be classified based on their orbits. For example, the NR system can be based on any of a low earth orbit (LEO) satellite with an altitude range of, for example, 300km to 1500km and a geostationary orbit (GEO) satellite with an altitude of 35786km. The NR system can be compatible with other satellite platforms (e.g., classifications), such as medium earth orbit (MEO) satellites with an altitude range of, for example, 7000km to 25000km and high altitude platform stations (HAPS) with an altitude of, for example, 8km to 50km. Satellite platforms can be further classified as having any of a "transparent" payload and a "regeneration" payload. A transparent satellite payload system can, for example, utilize one or more transparent satellites connected to a land-based gNB to implement frequency conversion and RF amplification in uplink and downlink. A regeneration satellite payload system can implement any of a full gNB and a gNB distributed unit (DU) on a satellite. The regeneration payload system can, for example, perform digital processing on a signal, for example, including any of demodulation, decoding, recoding, remodulation, and filtering.

[0086] Figure 2 201 , 202 . For example, the NTN network may include a radio link between the satellites 21, 22 and the WTRU 23, which may be referred to as a service link 203. The NTN network may include a transmission link between the satellites 21, 22, which may be referred to as an inter-satellite link (ISL) 204. There may be (e.g., only) an ISL in the regenerative payload system, which may be compatible with either a 3GPP radio interface and a proprietary (e.g., optical) interface.

[0087] Depending on the satellite payload configuration (e.g., transparent or regenerative), different 3GPP interfaces may be used for (e.g., each) radio link. In a transparent payload system, the NR-Uu radio interface may be used for both the service link and the feeder link. For a regenerative payload system, the NR-Uu interface may be used on the service link and the Satellite Radio Interface (SRI) may be used for the feeder link. There is no description of ISL in 3GPP Rel-17.

[0088] Figure 33 is a diagram showing an example of a user plane (UP) 31 and control plane (CP) 32 protocol stack for a transparent payload system. Protocol stacks for other types of payload systems are described in 3GPP TR 38.821 v16.1.0 Sections 5.1 and 5.2 "Solutions for NR support of non-terrestrial networks (NTN)".

[0089] NTN satellites may support one or more cells, and a cell may include one or more satellite beams. A satellite beam may cover a coverage area on the earth (e.g., such as a terrestrial cell), the diameter of which may be, for example, in the range of 100km to 1000km in a LEO deployment, and in the range of 200lm to 3500km in a GEO deployment. The beam coverage area in a GEO deployment may remain fixed relative to the earth, and in a LEO deployment, the area covered by the beam (e.g., a cell) may change over time based on satellite movement. Where a LEO beam may move continuously over the earth, such beam movement may be referred to herein as "earth mobile," or where a beam may be manipulated to maintain coverage of a fixed location until a new cell may exceed the coverage area, for example, in a discrete and coordinated change.

[0090] Based on either the altitude and beam diameter of the NTN platform, the round trip time (RTT) and maximum differential delay may be greater than that of a terrestrial system. For example, in a transparent NTN deployment, the RTT may be in the range of 25.77 ms (for LEO at 600 km altitude) to 541.46 ms (for GEO), and the maximum differential delay may be in the range of 3.12 ms to 10.3 ms. The RTT of the regenerative payload system may be half that of the transparent payload system. In fact, a transparent configuration may include a service link and a feeder link, and the RTT of the regenerative payload system may (e.g., only) involve the service link. For example, the WTRU may perform timing precompensation prior to initial access to reduce (e.g., minimize) the impact on the existing NR system (e.g., such as avoiding preamble ambiguity or properly timing the receive window).

[0091] For example, the WTRU may obtain its position via GNSS and may obtain the feeder link (or common) delay and satellite position via satellite ephemeris data to proceed with the pre-compensation process. Satellite ephemeris data may be broadcast periodically in system information and may contain any of satellite velocity, direction, and speed. For example, the WTRU may determine (e.g., estimate) the distance (and, for example, delay) to the satellite. For example, the WTRU may add the feeder link delay component to obtain the full WTRU-gNB RTT, which may be used to offset any of the timer, receive window, and timing relationship. Frequency compensation may be performed, for example, by the network.

[0092] 3GPP NR Rel-17 NTN further describes WTRU mobility and measurement reporting. For example, the difference in reference signal received power (RSRP) between the cell center and the cell edge may not be as significant as in terrestrial systems. This, combined with, for example, larger cell overlap areas, may cause mobility based on 3GPP NR measurements to be less reliable in NTN environments. New conditional handover and measurement report triggers that depend on location and time may allow improved mobility management in NTN systems. Enhanced mobility may be particularly important in LEO deployments, where due to satellite movement, a stationary WTRU may perform a move (e.g., approximately) every 7 seconds (depending on the deployment characteristics).

[0093] Example of disabling HARQ feedback in Rel-17 NTN

[0094] HARQ stalling may be considered herein as (e.g., all) HARQ process identifiers (IDs) having been allocated and pending, such that none may be reused for new data transmission / reception. Several enhancements are introduced in Rel-17 NR NTN to avoid HARQ stalling due to increased propagation delay. For example, the ability to disable HARQ feedback may allow a HARQ process ID to be used for a new data transmission after (e.g., immediately) a transmission, such that HARQ stalling may be prevented.

[0095] For example, a radio resource control (RRC) configuration (e.g., information) that may be referred to herein as downlinkHARQ-feedbackDisabled may indicate whether downlink (DL) HARQ feedback is enabled or disabled. For example, the configuration downlinkHARQ-feedbackDisabled may be configured (e.g., RRC) for each serving cell (e.g., HARQ feedback may be disabled). For example, the WTRU may receive (e.g., semi-static) configuration information indicating whether the WTRU may generate HARQ feedback for DL ​​assignments addressed to the HARQ process ID for each HARQ process ID. Similarly, for example, RRC configuration information that may be referred to herein as uplinkHARQ-Mode may be applicable to UL HARQ processes. For example, the configuration information uplinkHARQ-Mode may be configured (e.g., RRC) for each serving cell (e.g., uplink HARQ mode A may be configured). For example, the WTRU may receive (e.g., semi-static) configuration information indicating whether the HARQ process may be configured as HARQ mode A or HARQ mode B for each HARQ process ID. For example, the network may provide UL grants independent of the HARQ mode configuration. For example, based on the WTRU DRX behavior, HARQ Mode A may be more suitable for a HARQ process that enables UL HARQ retransmissions (e.g., for a HARQ process that may enable monitoring of HARQ retransmission grant information), and HARQ Mode B may be more suitable for a HARQ process that disables UL HARQ retransmissions (e.g., for a HARQ process that may enable monitoring of HARQ retransmission grant information), as further described in the embodiments described herein.

[0096] The terms "HARQ mode A", "uplink HARQ mode A", "HARQmodeA", and "first uplink HARQ mode" are collectively referred to as "HARQ mode A" and may be used interchangeably throughout the embodiments described herein to refer to an uplink HARQ mode of a HARQ process that may be more suitable for enabling UL HARQ retransmissions (e.g., where monitoring of HARQ retransmission grant information may be enabled). The terms "HARQ mode B", "uplink HARQ mode B", "HARQmodeB", and "second uplink HARQ mode" are collectively referred to as "HARQ mode B" and may be used interchangeably throughout the embodiments described herein to refer to an uplink HARQ mode of a HARQ process that may be more suitable for disabling UL HARQ retransmissions (e.g., where monitoring of HARQ retransmission grant information may be disabled).

[0097] For example, for at least enhanced machine type communication (eMTC) devices, DL HARQ feedback may be either enabled or disabled via semi-static RRC configuration.

[0098] DRX Adaptive Example

[0099] The timing for reusing the HARQ process ID in subsequent transmissions may be based on whether DL HARQ feedback is enabled or disabled. For example, a HARQ process with DL HARQ feedback enabled may use at least one RTT for the WTRU to provide HARQ feedback and receive a subsequent transmission (e.g., a retransmission), while a WTRU process with DL HARQ feedback disabled may be reused (e.g., immediately) after (e.g., the last) transmission.

[0100] Figure 4 is a system diagram illustrating an example of DRX adaptation based on downlink HARQ feedback status and uplink HARQ feedback mode.

[0101] As shown at 41, the WTRU may determine whether the serving cell is configured to disable downlink HARQ feedback. In the event that the WTRU determines that the serving cell is configured to disable downlink HARQ feedback, as shown at 42, the WTRU may determine whether HARQ feedback is enabled for the HARQ process (e.g., ID). In the event that the WTRU determines that HARQ feedback is enabled for the HARQ process (e.g., ID), the WTRU may start a retransmission timer (referred to herein as drx-RetransmissionTimerDL) after the transmission, which may be delayed by an offset corresponding to the WTRU-gNB RTT so that the WTRU may wake up and monitor the Physical Downlink Control Channel (PDCCH) at an appropriate time (e.g., to receive an upcoming transmission). For example, for a HARQ process with HARQ feedback disabled, the WTRU process may not perform any subsequent retransmissions. In this case, the drx-RetransmissionTimerDL may not be started after the transmission, which may improve WTRU energy saving. In the event that downlink HARQ feedback is not configured to be disabled for the serving cell, the conventional behavior may be applied.

[0102] Similarly, in the UL case, as shown at 43, the WTRU may determine whether the serving cell is configured with an uplink HARQ mode. In the case where the WTRU determines that the serving cell is configured with an uplink HARQ mode, as shown at 44, the WTRU may determine which HARQ mode may be configured for the HARQ process ID. For example, in the case where the WTRU is configured with an uplink HARQ mode and the HARQ process is configured with HARQ mode A, the WTRU may offset (e.g., delay) the start of the DRX UL retransmission timer (which may be referred to herein as drx-RetransmissionTimerUL) by the WTRU-gNB RTT. In the case where the WTRU is configured with HARQ mode B, the WTRU may not start the DRX UL retransmission timer. In the case where no uplink HARQ mode is configured for the serving cell, the conventional behavior may apply.

[0103] In the embodiments described herein, the terms "drx-RetransmissionTimerDL", "DRX DL retransmission timer", and "DL retransmission timer" may be used interchangeably to refer to a period of time during which a WTRU may monitor (e.g., PDCCH) for (e.g., receive) DL retransmissions, e.g., as described in Section 5.7 of 3GPP TS 38.321. For example, the DL retransmission timer may be applicable to each DL HARQ process.

[0104] In the embodiments described herein, the terms "drx-RetransmissionTimerUL", "DRX UL retransmission timer", and "UL retransmission timer" may be used interchangeably to refer to a period of time during which a WTRU may monitor (e.g., PDCCH) to obtain (e.g., receive) an UL grant (e.g., information) for an UL retransmission. For example, the UL retransmission timer may be applicable to each UL HARQ process.

[0105] In the embodiments described herein, the term "DL HARQ RTT timer" may be used to refer to a period of time after which the WTRU may monitor (e.g., PDCCH) to obtain (e.g., receive) a DL assignment (e.g., information) for a HARQ retransmission, for example, as described in Section 5.7 of 3GPP TS 38.321. During this period of time, it is expected that the WTRU may not receive a DL assignment (e.g., information) for a HARQ retransmission. For example, the DL HARQ RTT timer may be applicable to each DL HARQ process.

[0106] In the embodiments described herein, the term "UL HARQ RTT timer" may be used to refer to a period of time after which the WTRU may monitor (e.g., PDCCH) to obtain (e.g., receive) a UL HARQ retransmission grant (e.g., information), for example, as described in Section 5.7 of 3GPP TS 38.321. During this period of time, it is expected that the WTRU may not receive a UL HARQ retransmission grant (e.g., information). For example, the UL HARQ RTT timer may be applicable to each UL HARQ process.

[0107] Example of LCP Adaptation

[0108] The gNB may disable UL HARQ retransmissions by sending grant information indicating a new grant with a switched new data indicator (NDI) before waiting for network decoding results, such that transmissions sent on (e.g., certain) HARQ processes may be less reliable than other HARQ processes. As discussed in the embodiments described herein, a UL HARQ process ID configured with HARQ mode A may receive information indicating a UL retransmission grant based on the network decoding results, and a UL HARQ process ID configured with HARQ mode B may not (e.g., a subsequent grant may be either a blind retransmission grant or a no retransmission grant).

[0109] The configuration of the uplink HARQ mode may imply that UL grants assigned to (e.g., certain) HARQ processes may be more reliable than other HARQ processes. For example, (e.g., new) LCP restrictions (referred to herein as allowed HARQ modes (e.g., allowedHARQ-Mode)) may be used. The allowed HARQ mode LCP restriction (allowedHARQ-Mode) may indicate that for each logical channel (LCH), data from the LCH may be mapped to (e.g., associated with) a HARQ process ID configured with HARQ mode A or HARQ mode B. In the case where neither the uplink HARQ mode nor the allowed HARQ mode is configured, conventional LCP behavior may be applied.

[0110] Figure 5is a system diagram illustrating an example of LCP adaptation. For example, the WTRU may receive grant information indicating an uplink grant for a LCH. At step 51, the WTRU may determine whether an allowed HARQ mode LCP restriction may be configured for the LCH. In the event that an allowed HARQ mode LCP restriction is configured for the LCH, at step 52, the WTRU may determine whether an UL HARQ mode has been configured for a HARQ process associated with the UL grant. In the event that an UL HARQ mode has been configured for the HARQ process, at step 53, the WTRU may determine whether an allowed UL HARQ mode configured by a mapping rule may match the UL HARQ mode configured for the HARQ process to determine whether the restriction is satisfied.

[0111] Overview

[0112] Disabling HARQ feedback may have an impact on either DRX and LCP, and the adaptation of WTRU behavior based on HARQ feedback status (e.g., of DRX and LCP) may depend on (e.g., received) RRC configuration information (e.g., downlink HARQ feedback is disabled, uplink HARQ mode, and allowed HARQ modes). For example, the (e.g., received) RRC configuration (e.g., information) may not be suitable for lower capabilities such as, for example, reduced capability (RedCap) and narrowband Internet of Things (NB-IoT). For example, NB-IoT may support fewer HARQ processes (e.g., one or two), so that the flexibility to enable or disable a set of HARQ processes may be less. For example, RRC reconfiguration may not be supported, so that the configuration may not be changed after the initial connection setup.

[0113] Embodiments described herein may allow for indicating whether HARQ feedback is either enabled or disabled via other means other than RRC configuration information (e.g., such as DCI-based indications). Embodiments described herein may allow for adaptive DRX and LCP operation for DCI-based solutions. For example, where L1-based (e.g., DCI) indications are used to enable / disable either DL HARQ feedback and provide (e.g., indicate) UL HARQ mode, embodiments described herein may allow for either adaptive DRX timer and LCP restriction.

[0114] Embodiments of reduced capability and IoT devices are described herein. The embodiments described herein are not limited to those reduced capability and IoT devices, and may be equally applicable to any device, technique, and / or environment that supports L1 based indication of HARQ feedback state information.

[0115] Throughout the embodiments described herein, the terms "DCI-based indication", "physical layer information indicating ...", and "L1-based indication" are collectively referred to as "L1 indication", and may be used interchangeably to refer to a technique for indicating a piece of information using L1 (e.g., physical layer) information. The embodiments described herein are not limited to DCI-based indications, and may be applicable to any other L1-based method capable of indicating whether downlink HARQ feedback is either enabled or disabled and / or indicating an uplink HARQ mode.

[0116] Throughout the embodiments described herein, the terms “HARQ state” and “HARQ feedback state” may be used interchangeably to refer to either: (i) DL HARQ feedback is enabled or disabled, and (ii) a UL HARQ mode (e.g., A or B) is configured, e.g., for at least one HARQ process.

[0117] Embodiments are described herein for adapting DRX and / or LCP based on an L1 -based indication of HARQ feedback status (eg, whether HARQ feedback is enabled or disabled).

[0118] Example of L1 indication of HARQ feedback status

[0119] L1 indications (eg, how a WTRU may determine HARQ feedback status (eg, based on a DCI)) are described in greater detail herein.

[0120] In an embodiment, the WTRU may receive information (e.g., an indication) indicating a HARQ feedback state (e.g., DL HARQ feedback may be enabled or disabled and / or UL HARQ mode A or B may be configured) via an indication (e.g., information) in L1. The indication (e.g., information) may be explicit or implicit. The indication (e.g., information) may work independently of or in conjunction with one or more RRC configurations (e.g., may be used for any of: (1) enabling HARQ feedback, (2) disabling HARQ feedback, and (3) configuring a HARQ mode for any of (i) a HARQ process and (ii) LCP mapping restrictions).

[0121] For example, the WTRU may receive information (e.g., an indication) indicating a HARQ feedback state within a DCI. In an example, the indication (e.g., information) may be present within a DL assignment, where the indication (e.g., information) may refer to a HARQ feedback behavior for a corresponding DL reception. In another example, the indication (e.g., information indicating a HARQ state) may be present in a UL grant, where the indicated HARQ behavior may refer to a corresponding UL transmission.

[0122] In an embodiment, the WTRU may receive information (e.g., an indication) via a DCI indicating: (1) a HARQ feedback state of an associated HARQ process (e.g., indicating whether HARQ feedback is enabled or disabled) and / or (2) a HARQ mode behavior. The indication may represent, for example, one or more of the following information examples:

[0123] In an example, the information may indicate whether DL HARQ feedback is enabled or disabled for a scheduled physical downlink shared channel (PDSCH) in the DCI.

[0124] In another example, the information may indicate whether DL HARQ feedback is enabled or disabled for all HARQ processes.

[0125] In yet another example, the information may indicate whether DL HARQ feedback is enabled or disabled for a subset of HARQ processes, where the subset may be configured (e.g., indicated by receiving configuration information) via higher layer signaling (e.g., such as RRC). For example, the WTRU may receive configuration information indicating one or more subsets of HARQ processes, where (e.g., each) subset of HARQ processes may be configured with (e.g., associated with) an index. The index may be indicated in (e.g., included in) the DCI.

[0126] In another example, the information may indicate that DL HARQ feedback may be disabled except for PDSCH carrying MAC control element (MAC-CE). For example, if the WTRU receives the indication, the WTRU may skip HARQ feedback for PDSCH except for the case where the PDSCH carries MAC-CE.

[0127] In yet another example, the information may indicate whether DL HARQ feedback is enabled or disabled for all HARQ processes except for the HARQ process that may be used for MAC-CE transmission. The HARQ process carrying MAC-CE may be, for example, any one of configured, determined, and indicated by the gNB. The HARQ process carrying MAC-CE may be, for example, implicitly determined based on a HARQ process number (e.g., any one of the lowest HARQ process identifier, the highest HARQ process identifier, etc.).

[0128] In yet another example, the information may indicate UL HARQ Mode A.

[0129] In yet another example, the information may indicate UL HARQ Mode B.

[0130] In yet another example, the information may indicate a switched HARQ feedback behavior for the HARQ process (eg, all subsequent DCIs addressed to the HARQ process may have the same HARQ feedback state unless otherwise indicated).

[0131] In yet another example, the information may indicate an RRC configuration covering the HARQ process.

[0132] Throughout the embodiments described herein, the term “enabling / disabling of HARQ feedback” may be used interchangeably with “activation / deactivation of HARQ feedback”.

[0133] In an embodiment, information related to the HARQ feedback state (eg, indicating the HARQ feedback state) may be indicated (eg, transmitted), and / or the WTRU may determine the HARQ feedback state via one or more of the following method examples.

[0134] In an example, an explicit flag within the DCI may indicate the HARQ feedback status (e.g., a flag bit set to 1 may correspond to DL HARQ feedback being enabled, while a flag bit set to 0 may correspond to HARQ feedback being disabled, and vice versa. Similarly, the flag may correspond to (e.g., indicate) UL HARQ mode A or UL HARQ mode B).

[0135] In another example, the HARQ feedback state may be indicated based on a DCI format. For example, one or more DCI formats may be configured (e.g., the WTRU may receive configuration information indicating one or more DCI formats). In the event that the WTRU receives a particular DCI format (e.g., a DCI format indicated by the gNB as being associated with and / or corresponding to either one of HARQ feedback enabling and disabling), the WTRU may determine to disable or enable HARQ feedback associated with a HARQ process based on the DCI format. For example, in the event that the WTRU receives a first DCI format for a PDSCH (e.g., DCI format A), the WTRU may determine that the associated HARQ feedback may be disabled (e.g., for subsequent DL assignments addressed to the HARQ process), and in the event that the WTRU receives a second DCI format for a PDSCH (e.g., DCI format B), the WTRU may determine that the associated HARQ feedback may be enabled (e.g., for subsequent DL assignments addressed to the HARQ process).

[0136] In yet another example, the WTRU may determine the HARQ feedback state based on a radio network temporary identifier (RNTI) scrambled with a cyclic redundancy check (CRC) of a scheduled DCI. For example, in a case where the DCI format for scheduling a PDSCH is scrambled with a first cell RNTI (C-RNTI) (e.g., C-RNTI-1), the WTRU may determine that HARQ feedback for the scheduled PDSCH may be disabled; in a case where the DCI format for scheduling a PDSCH is scrambled with a second C-RNTI (e.g., C-RNTI-2), the WTRU may determine that HARQ feedback for the scheduled PDSCH may be enabled. The WTRU may be configured with one or more C-RNTIs (e.g., receiving configuration information indicating the one or more C-RNTIs), and (e.g., each) C-RNTI may be associated with a HARQ feedback state (or mode). In a case where the WTRU is configured with a single HARQ process, HARQ disabling may not be supported, and a single C-RNTI (e.g., C-RNTI-1) may be used. In case HARQ disabling is not supported (eg, based on WTRU capabilities), the WTRU may be configured with a single C-RNTI.

[0137] In yet another example, the WTRU may determine the HARQ feedback state based on the PDCCH search space. For example, one or more PDCCH search spaces may be configured (e.g., indicated by received configuration information) or used; and (e.g., each) PDCCH search space may be associated with a HARQ feedback state (e.g., enabled or disabled). In the event that the WTRU receives a DCI in a first PDCCH search space (e.g., the first search space is associated with HARQ feedback enablement), the WTRU may determine that HARQ feedback may be enabled for a scheduled PDSCH. In the event that the WTRU receives a DCI in a second PDCCH search space (e.g., the second search space is associated with HARQ feedback disablement), the WTRU may determine that HARQ feedback may be disabled for a scheduled PDSCH. Throughout the embodiments described herein, the term "PDCCH search space" may be used interchangeably with "search space identifier," "control resource set (CORESET)," "PDCCH candidate," and "PDCCH search area identifier."

[0138] In yet another example, the WTRU may determine the HARQ feedback state based on scheduling information (e.g., transport block size (TBS), repetitions). For example, the HARQ feedback state (e.g., enabled / disabled) may be determined based on scheduling parameters of the PDSCH, including any of TBS, modulation and coding scheme (MCS), number of repetitions, demodulation reference signal (DMRS) density, NDI, HARQ process number, number of layers, number of codewords, and DMRS port indication.

[0139] Example of L1 indication of HARQ feedback status to higher layers

[0140] Embodiments for indicating HARQ feedback status to higher layers (eg, MAC) are described in more detail herein.

[0141] In an embodiment, the WTRU may (eg, always) indicate the HARQ feedback status (or L1 indication) to higher layers when (eg, after) the WTRU may receive a DL DCI that may schedule a PDSCH.

[0142] In another embodiment, the WTRU may indicate the HARQ feedback status to higher layers if one or more of the following conditions are met.

[0143] In an example, in case the HARQ feedback status indicated in the DCI is different from the HARQ feedback status configured, for example, via higher layer signaling (eg, RRC configuration), the WTRU may indicate the HARQ feedback status to higher layers.

[0144] In another example, in a case where the HARQ feedback state indicated in the DCI is different from a previous HARQ feedback state (e.g., a previously indicated HARQ feedback state), the WTRU may indicate the HARQ feedback state to a higher layer. For example, the WTRU may be indicated (e.g., receiving information indicating the following) to enable HARQ feedback for PDSCH in the DCI in a first time slot, and the WTRU may be indicated (e.g., receiving information indicating the following) to disable HARQ feedback for PDSCH in the DCI in a second time slot, where the first time slot may be earlier than the second time slot.

[0145] In yet another example, in a case where a time slot is configured as a time slot in which the WTRU may indicate the HARQ feedback status to a higher layer, the WTRU may indicate the HARQ feedback status to the higher layer, and the configuration of the time slot for indicating the HARQ feedback status to the higher layer may be (e.g., based on) periodic reporting.

[0146] In another example, when the number of disabled (or enabled) HARQ processes satisfies a condition (e.g., is higher than a certain value (e.g., a threshold)), the WTRU may indicate the HARQ feedback status to a higher layer, where the value (e.g., the threshold) may be any of pre-determined, configured, or indicated by the gNB.

[0147] In yet another example, in case HARQ feedback is disabled for all HARQ processes, the WTRU may indicate the HARQ feedback status to higher layers.

[0148] In an embodiment, the WTRU may be instructed by the gNB (e.g., in a DCI) to report the HARQ feedback status to higher layers.

[0149] In the embodiments described herein, the term “HARQ feedback state” may be used interchangeably with “L1 indication”, “L1 HARQ state indication”, “L1 state of HARQ feedback state” and “L1 indication of HARQ feedback state”.

[0150] In an embodiment, the L1 indication (eg, HARQ feedback status indicated to a higher layer) may include one or more of the following information.

[0151] In an example, the L1 indication may include information indicating whether HARQ feedback is enabled or disabled.

[0152] In another example, the L1 indication may include information indicating whether the HARQ feedback state is changed (eg, from enabled to disabled, from activated to deactivated, etc.).

[0153] In yet another example, the L1 indication may include information indicating the number of disabled (or enabled) HARQ processes.

[0154] In yet another example, the L1 indication may include information indicating a list of disabled (or enabled) HARQ processes.

[0155] In yet another example, the L1 indication may include information indicating, for example, a ratio between a HARQ feedback enabled case and a HARQ feedback disabled case within the window.

[0156] In yet another example, the L1 indication may include information indicating a duration of the indication.

[0157] Example of higher layer adaptation based on HARQ feedback status indicated by L1

[0158] This article describes the impact and adaptation of DRX and LCP based on L1 indication.

[0159] In an embodiment, the WTRU may adapt higher layer procedures (e.g., either DRX and LCP) based on HARQ feedback status indications (e.g., L1 indications) from lower layers. These adaptations may allow WTRU behaviors to be enabled based on the indicated HARQ feedback status, for example, in the absence of a default behavior or RRC configuration. The WTRU actions (e.g., operations) described herein may vary according to, for example, one or more of the following:

[0160] In a first example, the WTRU action (eg, operation) may be based on whether the RRC configuration to enable / disable HARQ feedback has been configured.

[0161] In a second example, the WTRU action (eg, operation) may be based on the indicated HARQ process.

[0162] In another example, the WTRU action (eg, operation) may be based on the number of HARQ processes supported by the WTRU.

[0163] In yet another example, the WTRU action (eg, operation) may be based on the serving cell from which the transmission bearing the indication may have been received.

[0164] In yet another example, the WTRU action (eg, operation) may be based on the content of the indication (eg, whether the HARQ process is indicated as having HARQ feedback enabled or disabled).

[0165] In yet another example, a WTRU action (e.g., operation) may be based on the device type (e.g., whether the device is classified as NB-IoT, eMTC, WTRU, VSAT, or RedCap).

[0166] In yet another example, WTRU actions (eg, operations) may be based on characteristics of a satellite (eg, whether the satellite belonging to a serving cell is geosynchronous orbit (GSO) or non-GSO in the case where the WTRU is connected to a non-terrestrial network).

[0167] In yet another example, a WTRU action (e.g., operation) may be based on the WTRU-gNB RTT (e.g., its length).

[0168] In yet another example, the WTRU action (eg, operation) may be based on whether the DCI indication is part of a DL assignment or a UL grant.

[0169] Example of maintaining HARQ feedback state for a HARQ process

[0170] In an example, the HARQ feedback state may be maintained in any of a new state and a variable (e.g., when RRC configuration is not supported or when a default state is not supported). The new variable may be maintained, for example, for any of: (1) each HARQ process, (2) each serving cell, (3) all HARQ processes, and (4) HARQ processes that may not have a configured HARQ feedback state (e.g., not configured as any of enabled, disabled, HARQ mode A, and HARQ mode B).

[0171] In an example, upon receiving the L1 indication, the WTRU may set any of the state and the variable to the value indicated within the L1 indication for the corresponding HARQ process to which the UL grant and / or DL ​​assignment may be assigned (e.g., HARQ feedback enabled, HARQ feedback disabled, HARQ mode A, or HARQ mode B). For example, (e.g., all) subsequent UL grants and / or DL ​​assignments addressed to that HARQ process may follow the HARQ feedback state, e.g., until the L1 indication may change (e.g., switch) the state value.

[0172] In an example, the state may apply and / or may change based on subsequent transmissions and / or indications from the network. For example, in the case where the L1 indicates switching HARQ feedback and / or HARQ mode, the WTRU may update the HARQ state after acknowledging and / or transmitting the corresponding UL transmission (e.g., in the case where the L1 indication is provided via a UL grant), receiving DL HARQ feedback (indicated DL assignment), and / or receiving a corresponding DL transmission associated with the DL assignment.

[0173] Example of DRX adaptation based on indication within DL assignment

[0174] In an example, the WTRU and / or MAC entity may adapt the DRX behavior based on an indication from a lower layer (e.g., either L1 or L2). For example, upon receiving a DL assignment carrying an L1 indication and / or upon receiving a corresponding DL transmission, in the case where the L1 indication indicates that DL HARQ feedback is enabled, the WTRU may, for example, perform one or more of the following example operations.

[0175] In an operational example, the WTRU may extend the length of the DL HARQ RTT timer to at least the WTRU-gNB RTT.

[0176] In another operation example, the WTRU may offset the start of the DL HARQ RTT timer by the WTRU-gNB RTT. During a time period corresponding to the (e.g., extended, offset) DL HARQ RTT, the WTRU may, for example, not monitor a downlink control channel (e.g., PDCCH) to save power.

[0177] In yet another operational example, the WTRU may offset the start of the DL retransmission timer by the WTRU-gNB RTT.

[0178] In yet another operational example, the WTRU may extend the length of the DL retransmission timer by the WTRU-gNB RTT. During a time period corresponding to the (e.g., extended, offset) DL retransmission time, the WTRU may, for example, monitor a downlink control channel to receive retransmissions.

[0179] In yet another example of operation, the WTRU may start a new timer (e.g., a MAC timer) of length equal to the sum of the DL HARQ RTT timer and the WTRU-gNB RTT. While the timer may be running, the WTRU may not monitor the downlink control channel (e.g., PDCCH). After the timer expires, the WTRU may, for example (e.g., begin) monitoring the downlink control channel (e.g., PDCCH) and may start a DL retransmission timer.

[0180] In yet another operational example, the WTRU may enter DRX active time. Throughout the embodiments described herein, "entering DRX active time" may be considered to monitor a downlink control channel (eg, PDCCH) to detect (eg, receive) a transmission directed to the WTRU, for example.

[0181] In case the L1 indication indicates that DL HARQ feedback may be disabled (eg, for either DL assignments and HARQ processes), the WTRU may, for example, perform one or more of the following example operations.

[0182] In an example operation, the WTRU may not start the DL HARQ RTT timer.

[0183] In another operation example, the WTRU may not start a DL retransmission timer. For example, the WTRU may monitor a downlink control channel (e.g., PDCCH) based on other DRX timers (e.g., such as any of an inactivity timer and a DL retransmission timer associated with other HARQ processes) other than the DL HARQ RTT timer and / or the DL retransmission timer.

[0184] In yet another operational example, the WTRU may enter DRX active time (eg, and may start a DL retransmission timer).

[0185] In yet another operational example, the WTRU may start a new timer (eg, while the timer may be running, the WTRU may monitor the PDCCH).

[0186] Example of DRX adaptation based on indication within UL grant

[0187] In an example, the WTRU and / or MAC entity may adapt the DRX behavior based on information (e.g., indication) from lower layers provided within (e.g., received therein) in a UL grant. The indication (e.g., physical layer information, L1 indication) may indicate (e.g., indicate), for example, any of the following: (i) UL HARQ retransmissions may be enabled, (ii) UL HARQ retransmissions may be disabled, (iii) DRX may be adapted based on HARQ mode A, and (iv) DRX may be adapted based on HARQ mode B.

[0188] In case the L1 indication indicates (e.g., indicates) that UL HARQ retransmissions may be enabled and / or adaptive DRX may be based on HARQ Mode A, the WTRU may, for example, perform one or more of the following operations after transmitting the corresponding UL transmission indicated within the UL grant.

[0189] In an operational example, the WTRU may extend the length of the UL HARQ RTT timer by the WTRU-gNB RTT after transmitting the corresponding UL transmission indicated within the UL grant.

[0190] In another operation example, the WTRU may offset the start of the UL HARQ RTT timer by the WTRU-gNB RTT after transmitting the corresponding UL transmission indicated within the UL grant. For example, the WTRU may delay downlink control channel monitoring for a period of time corresponding to the (e.g., extended, offset) UL HARQ RTT timer (e.g., to save power).

[0191] In yet another operation example, the WTRU may offset the start of the UL retransmission timer by the WTRU-gNB RTT after transmitting the corresponding UL transmission indicated within the UL grant.

[0192] In yet another operational example, the WTRU may extend the length of the UL retransmission timer by the WTRU-gNB RTT after transmitting the corresponding UL transmission indicated in the UL grant. For example, the WTRU may monitor the downlink control channel (e.g., to receive any one of an acknowledgment and a HARQ retransmission grant information) for a period of time corresponding to the (e.g., extended, offset) UL retransmission timer. For example, if no acknowledgment is received within the period of time, the WTRU may retransmit the UL transmission.

[0193] In yet another operational example, the WTRU may start a new timer (eg, a MAC timer) after transmitting a corresponding UL transmission indicated within a UL grant.

[0194] In yet another example of operation, the WTRU may enter a DRX active time after transmitting a corresponding UL transmission indicated within the UL grant. The length of a new timer (e.g., a MAC timer) may be equal to the sum of the UL HARQ RTT timer and the WTRU-gNB RTT. While the timer may be running (e.g., for a period of time corresponding to the new timer), the WTRU may not (e.g., is not expected to) monitor a downlink control channel (e.g., PDCCH). After the new timer expires (e.g., after an amount of time corresponding to the new time may have passed), the WTRU may, for example (e.g., begin) monitoring a downlink control channel (e.g., PDCCH) and may start a UL retransmission timer.

[0195] In case the L1 indication indicates (e.g., indicates) that UL HARQ retransmissions may be disabled and / or DRX may be adaptive based on HARQ Mode B, the WTRU may, for example, perform one or more of the following operations after transmitting the corresponding UL transmission indicated within the UL grant.

[0196] In an example operation, the WTRU may not start the UL HARQ RTT timer after transmitting the corresponding UL transmission indicated within the UL grant.

[0197] In another operation example, the WTRU may not start the UL retransmission timer after transmitting the corresponding UL transmission indicated in the UL grant. For example, the WTRU may monitor the downlink control channel (e.g., PDCCH) based on other DRX timers (e.g., such as any of the inactivity timers and retransmission timers associated with other HARQ processes) other than the UL HARQ RTT timer and / or the UL retransmission timer.

[0198] In yet another operational example, after transmitting the corresponding UL transmission indicated within the UL grant, the WTRU may enter a DRX active time (eg, without starting a UL retransmission timer).

[0199] In yet another operational example, after transmitting the corresponding UL transmission indicated within the UL grant, the WTRU may start a new timer during which the WTRU may monitor the downlink control channel (PDCCH).

[0200] Example of duration of L1-based DRX adaptation

[0201] In an embodiment, the WTRU may apply an adapted DRX behavior (e.g., adaptive DRX operation) for any of, for example, a specific duration, one or more transmissions, and one or more HARQ processes. For example, according to one or more of the following examples, the WTRU may adapt the DRX behavior based on the L1 indication.

[0202] In a first example, the WTRU may adapt the DRX behavior for transmissions scheduled by UL grants and / or DL ​​assignments that include an L1 indication.

[0203] In another example, the WTRU may adapt the DRX behavior for the next X transmissions and / or receptions used for and / or assigned to a HARQ process, where X may be any integer (eg, a fixed integer).

[0204] In yet another example, the WTRU may adapt the DRX behavior for (e.g., all) transmissions for a particular HARQ process (e.g., the WTRU may adapt the DRX behavior based on the L1 indication until a subsequent L1 indication addressed to the same HARQ process may be received, where the L1 indication may indicate a change in the DRX behavior).

[0205] In yet another example, the WTRU may adapt the DRX behavior for (eg, all) HARQ processes belonging to the serving cell.

[0206] In yet another example, the WTRU may adapt the DRX behavior for (eg, all) HARQ processes belonging to the MAC entity.

[0207] In yet another example, the WTRU may adapt the DRX behavior for (eg, all) UL HARQ processes belonging to (eg, all) serving cells or MAC entities.

[0208] In yet another example, the WTRU may adapt the DRX behavior for a configured and / or indicated duration. For example, the WTRU may have received information indicating a duration for which DRX adaptation may be performed.

[0209] In an embodiment, the WTRU may apply one or more of the behaviors according to any of the embodiments described herein based on, for example, one or more of the following: (i) an explicit indication, for example, from a lower layer (e.g., receipt of explicit information indicating one or more behaviors), (ii) receipt of information indicating one or more behaviors to be applied (e.g., RRC configuration), (iii) the number of HARQ processes, and (iv) whether the HARQ process is a UL or DL ​​HARQ process.

[0210] Example of configuration of L1-based DRX adaptation

[0211] In an embodiment, the WTRU may determine whether to adapt the DRX behavior based on an L1 indication (e.g., an indication within a DCI) rather than based on (e.g., explicit) configuration information. For example, the WTRU may receive configuration information, for example, via an RRC indicating enabling or disabling of L1-based DRX adaptation. In the embodiments described herein, the terms "enabling / disabling L1-based DRX adaptation" and "enabling / disabling L1-based indication of HARQ state" may be used interchangeably to refer to enabling / disabling an operating mode for the WTRU, where the HARQ state may be adjusted (e.g., modified) based on the L1-based indication. The configuration information may indicate that DRX may be adaptive DRX for all HARQ processes or on a granularity (e.g., level, basis) per HARQ process. The configuration information may be combined, for example, with other configuration information (e.g., such as downlink HARQ feedback disabling information) indicating whether HARQ feedback may be enabled or disabled for each HARQ process.

[0212] In an embodiment, the (e.g., RRC) configuration information may include an additional field (e.g., element) indicating enabling / disabling of DL HARQ feedback. For example, the (e.g., RRC) configuration information may indicate three states: 1) DL HARQ feedback is enabled; 2) DL HARQ feedback is disabled; and 3) DL HARQ feedback is controlled by L1 indication. In the case where the HARQ process is configured to enable or disable DL HARQ feedback, the WTRU may apply the behavior indicated by the (e.g., RRC) configuration information. In the case where the HARQ process is configured with HARQ feedback controlled by L1 indication, the WTRU may apply DRX behavior based on the L1 indication. For example, an additional HARQ mode (e.g., HARQ mode C) may be used in the (e.g., RRC) configuration information to indicate that the DRX behavior may be controlled based on the L1 indication within the UL grant.

[0213] In an embodiment, an L1 indication may have been received indicating a particular HARQ feedback behavior, and the HARQ process may have been pre-configured with the HARQ feedback behavior (e.g., by receiving RRC configuration information). In the event of a conflict between the indication provided by the L1 indication and the (e.g., RRC) configuration information, the WTRU may perform one or more of the following examples of actions (e.g., operations):

[0214] In a first operational example, the L1 indication may (eg, always) override the RRC configuration.

[0215] In another operation example, L1 indicates that the RRC configuration may be changed (eg, L1 indicates that the RRC configuration may be reconfigured).

[0216] In yet another example of operation, the L1 indication may override the RRC configuration based on one or more conditions (eg, such as based on any of transmission priority, repetition number, TBS size for one or more HARQ process IDs).

[0217] In another operation example, the RRC configuration may override the L1 indication. For example, the L1 indication may be ignored based on the RRC configuration information.

[0218] The actions (eg, operations) described herein may vary, for example, per WTRU, per HARQ process, per MAC entity and / or per serving cell. The actions that a WTRU may perform may, for example, depend on (eg, be based on) a WTRU configuration.

[0219] Example of WTRU behavior without L1 indication reception

[0220] In an embodiment, the WTRU may be able to adapt the DRX behavior. For example, it is expected that the WTRU may receive an L1 indication to determine how to adapt the DRX behavior. For example, the WTRU may have received configuration information indicating that the HARQ process may be configured with "DL HARQ feedback controlled by L1 indication" or "HARQ Mode C". If the expected L1 indication is not received, the WTRU may assume (e.g., apply) one or more of the following:

[0221] In the absence of a received L1 indication, the WTRU may apply a default behavior. For example, the default behavior may include one or more DRX adaptations according to any of the embodiments described herein and may be provided (e.g., received) or indicated (e.g., in system information), for example, via configuration information.

[0222] In case no L1 indication is received, the WTRU may apply legacy behavior for DRX operation (e.g., WTRU-gNB RTT may not be incorporated into the DRX process).

[0223] In case no L1 indication is received, the WTRU may apply the DRX adaptation indicated by the last received L1 indication to the corresponding HARQ process.

[0224] In case no L1 indication is received, the WTRU may apply the DRX behavior indicated via the RRC configuration (if available).

[0225] Example of Logical Channel Prioritization (LCP) Adaptation

[0226] In an embodiment, the WTRU may be configured with an LCP restriction (e.g., receive configuration information indicating the LCP restriction) that may map (e.g., associate) a logical channel (LCH) to a HARQ process configured with (e.g., a given) HARQ mode (e.g., HARQ Mode A or HARQ Mode B). For example, the WTRU may take into account the L1 indication (e.g., determined via a DCI indication within a UL grant) in the LCP process.

[0227] In an embodiment, the WTRU may adapt the LCP based on physical layer information received, for example, in the DCI (eg, HARQ state information indicated by L1).

[0228] For example, the LCH mapping restrictions within the LCP process may be reused.

[0229] For example, the WTRU may interpret the physical layer information (e.g., L1 indication) as indicating either HARQ mode A and HARQ mode B. In the case where the LCH is configured with an LCH mapping restriction in which the restriction is mapped to (e.g., associated with) a (e.g., specific) HARQ mode and the L1 indication within the UL grant matches the configured HARQ mode, the WTRU may map (e.g., associate) data from the logical channel to the UL grant. In another example, in the case where the HARQ mode indicated within the LCH mapping restriction does not match the HARQ mode indicated within the L1 indication in the UL grant, the data from the LCH may not be mapped to (e.g., associated with) the UL grant.

[0230] Example of DRX adaptation based on L1 indication

[0231] In an embodiment, the WTRU may receive information (e.g., such as indication and / or configuration information) indicating that HARQ state information may be provided and / or modified via an L1-based indication. The information (e.g., configuration and / or indication) may apply to any of the following: (i) each serving cell, (ii) each HARQ process, (iii) UL HARQ process, (iv) DL HARQ process, and (v) all HARQ processes.

[0232] The WTRU may receive information indicating HARQ state information (e.g., within any of a UL grant and a DL assignment). The HARQ state information may indicate, for example, any of the following: (i) HARQ feedback may be enabled, (ii) HARQ feedback may be disabled, (iii) HARQ mode A, (iv) HARQ mode B, (v) HARQ feedback and / or HARQ mode may be different from the RRC configuration, and (vi) HARQ feedback may be different from the previously indicated HARQ feedback state information.

[0233] In an example, an indication of HARQ state information (e.g., indicating HARQ state information information) may be provided and / or determined via any of: (i) an explicit flag within the DCI, (ii) based on a DCI format, (iii) based on an RNTI scrambled with a CRC of a scheduling DCI, (iv) a PDCCH search space, and (v) scheduling information (e.g., such as any of a TBS size, a number of repetitions). The HARQ state information may apply to, for example, any of: (i) an UL transmission scheduled by an UL grant, (ii) a DL reception scheduled by a DL assignment, (iii) one or more subsequent transmissions on a HARQ process, (iv) a group of HARQ processes (e.g., such as any of one or more HARQ processes, a UL HARQ process, and a DL HARQ process).

[0234] The WTRU may indicate HARQ state information to a higher layer (e.g., MAC). The indication to the higher layer may include, for example, any of: (i) HARQ feedback state (e.g., indicating whether HARQ feedback is enabled and / or disabled), (ii) HARQ mode (e.g., indicating either HARQ mode A or HARQ mode B), and (iii) duration and / or granularity of the indication (e.g., indicating whether the indication applies to a specific transmission and / or reception, whether the indication applies to one or more or a group of HARQ processes). For example, the indication may be provided to the higher layer after the indication may have been received. In another example, the indication may be provided to the higher layer if, for example, any of: (i) the HARQ state information is different from the HARQ state information configured via higher layer signaling (e.g., such as RRC), and (ii) the HARQ state signal is different from the previously indicated HARQ (e.g., feedback) state information.

[0235] After receiving physical layer information (e.g., an L1 indication of HARQ state information), the WTRU may, for example, adapt the DRX behavior based on the indicated HARQ state information. In the case where the L1 indication indicates that DL HARQ feedback may be enabled, the WTRU may perform any of the following: (i) modify the DL HARQ RTT timer (e.g., extend the length of the WTRU-gNB RTT or start an offset WTRU-gNB RTT); (ii) modify the DL retransmission timer (e.g., start an offset WTRU-gNB RTT or extend the WTRU-gNB RTT); (iii) start a new timer and (iv) enter DRX active time (e.g., monitor PDCCH). In the case where the L1 indication indicates that DL HARQ feedback may be disabled, the WTRU may perform any of the following: (i) do not start the DL HARQ RTT timer; (ii) do not start the DL retransmission timer and do not start a new timer.

[0236] In the case where the L1 indication indicates that UL HARQ retransmission is enabled and / or indicates HARQ Mode A, the WTRU may perform any of the following: (i) modify the UL HARQ RTT timer (e.g., extend the length of the WTRU-gNB RTT or start an offset WTRU-gNB RTT), (ii) modify the UL retransmission timer (e.g., start an offset WTRU-gNB RTT or extend the WTRU-gNB RTT), (iii) start a new timer, and (iv) enter DRX active time (e.g., monitor PDCCH). In the case where the L1 indication indicates that UL HARQ retransmission is disabled and / or indicates HARQ Mode B, the WTRU may perform any of the following: (i) do not start the UL HARQ RTT timer; (ii) do not start the UL retransmission timer and do not start a new timer (so that subsequent transmissions can be transmitted).

[0237] In an example, the WTRU may apply the DRX behavior for a specific duration (e.g., such as any of the following: (i) for (e.g., a specific) transmission and / or reception, (ii) for the next X transmissions and / or receptions, (iii) indefinitely, and (iv) until a subsequent indication can be received). Any of the L1 indication and the (e.g., RRC) configuration information may indicate the duration for which the WTRU may apply the DRX behavior. The WTRU may apply the DRX behavior to, for example, any of the following: (i) a specific HARQ process, (ii) one or more HARQ processes (e.g., any of a group of HARQ processes, (e.g., all) UL HARQ processes, and (e.g., all) DL HARQ processes), and (iii) (e.g., all) HARQ processes.

[0238] In the event that the L1 indication conflicts with a higher layer configuration, the WTRU may, for example, operate according to any of the following: (i) the L1 indication overrides the RRC configuration (e.g., always); (ii) the L1 indication changes the RRC configuration (e.g., the L1 indication may reconfigure the RRC configuration), (iii) the L1 indication overrides the RRC configuration based on one or more conditions (e.g., such as based on transmission priority, number of repetitions, TBS size, any of one or more HARQ process IDs), and (iv) the RRC configuration overrides the L1 indication.

[0239] Figure 6 is a system diagram illustrating an example method for adaptive DRX based on L1 indication.

[0240] As indicated at 610, the WTRU may receive first configuration information indicating whether HARQ feedback may be enabled or disabled, for example, for one or more HARQ processes.

[0241] As shown at 620, the WTRU may receive second configuration information indicating whether DRX adaptation may be enabled or disabled based on the L1 indication, for example, for one or more HARQ processes. For example, the first configuration information and the second configuration information may be received in one or more (e.g., RRC) messages. For example, configuration information may be received indicating any of: (i) an L1-based indication of a HARQ state and (ii) a first HARQ state. For example, a first DRX operation may be performed based on the first HARQ state.

[0242] As indicated at 630, the WTRU may determine whether the serving cell is configured to disable downlink HARQ feedback.

[0243] As indicated at 640, the WTRU may receive an L1 indication indicating a HARQ feedback status for one or more HARQ processes.

[0244] As shown at 650, the WTRU may determine whether to enable or disable DRX adaptation for one or more HARQ processes associated with the received L1 indication.

[0245] In the event that the WTRU determines that DRX adaptation may be enabled for one or more HARQ processes, the WTRU may determine whether the L1 indication indicates that HARQ feedback is enabled for the one or more HARQ processes, as shown at 660. For example, a DCI may be received, and the WTRU may determine that the DCI may indicate a second HARQ state based on the L1-based indication that the configuration information indicates that the HARQ state may be enabled. For example, a second DRX operation may be performed based on the second HARQ state.

[0246] In the event that the WTRU determines that HARQ feedback may be enabled as indicated by the L1 indication, the WTRU may offset the start of the DRX retransmission DL timer by the WTRU-gNB RTT, as shown at 670.

[0247] Figure 7 7 is a system diagram illustrating an example method 700 for adaptive DRX based on L1 indication. For example, the method may be implemented in a WTRU. As shown at 710, the WTRU may receive downlink control information indicating HARQ state information. As shown at 720, the WTRU may perform discontinuous reception based on the HARQ state information.

[0248] In various embodiments, the HARQ state information may be indicated in any of the uplink grant information and the downlink assignment information.

[0249] In various embodiments, the HARQ state information may indicate any of: (i) downlink HARQ feedback enabled, (ii) downlink HARQ feedback disabled, (iii) a first uplink HARQ mode, and (iv) a second uplink HARQ mode.

[0250] In various embodiments, the HARQ state information may indicate a first uplink HARQ mode, which may be different from a second uplink HARQ mode indicated by a previous HARQ state information.

[0251] In various embodiments, the HARQ state information may indicate a first downlink HARQ feedback state, which may be different from a second downlink HARQ feedback state indicated by a previous HARQ state information.

[0252] In various embodiments, the HARQ state information may apply to any of: (i) uplink transmissions scheduled by uplink grants of downlink control information, (ii) downlink receptions scheduled by downlink assignments of downlink control information, (iii) one or more subsequent transmissions of one or more HARQ processes.

[0253] In various embodiments, the HARQ state information may indicate that downlink HARQ feedback may be enabled, and wherein performing DRX may include delaying monitoring to receive subsequent transmissions (eg, retransmissions) based on a WTRU to base station round trip time.

[0254] In various embodiments, the HARQ state information may indicate a first uplink HARQ mode, and wherein performing DRX may include retransmitting uplink transmissions that were not acknowledged within a time period that includes at least a WTRU to base station round trip time.

[0255] In various embodiments, the HARQ state information may indicate a second uplink HARQ mode, and wherein performing DRX may include monitoring a downlink control channel during a time period different from an uplink retransmission time period to receive a subsequent transmission.

[0256] In various embodiments, DRX may be performed based on the HARQ state information until subsequent HARQ state information may be indicated in subsequent downlink control information.

[0257] In various embodiments, after DRX is performed based on the HARQ state information for a period of time, DRX may be performed according to a default behavior.

[0258] In various embodiments, the method may further include receiving configuration information indicating that the HARQ state information may be modified based on the information indicated by the downlink control information.

[0259] In various embodiments, the HARQ state information may be applicable to any of the following: (i) each serving cell, (ii) each HARQ process, (iii) uplink HARQ process, (iv) downlink HARQ process, (iv) all HARQ processes.

[0260] Figure 8is a diagram illustrating an example method 800 for adaptive DRX based on L1 indication. The method 800 may be implemented in a WTRU. As shown at 810, the WTRU may receive configuration information indicating (1) a DCI-based indication of a HARQ state and (2) a first HARQ state associated with a HARQ process. As shown at 820, the WTRU may perform a first DRX operation based on the first HARQ state. As shown at 830, the WTRU may receive a DCI. As shown at 840, the WTRU may determine that the DCI may indicate a second HARQ state associated with the HARQ process based on the configuration information indicating that the DCI-based indication of the HARQ state may be enabled. As shown at 850, the WTRU may perform a second DRX operation (e.g., associated with the HARQ process) based on the second HARQ state.

[0261] In various embodiments, the second HARQ state may be indicated in any of the uplink grant information and the downlink assignment information.

[0262] In various embodiments, the second HARQ state may be different from the first HARQ state.

[0263] In various embodiments, any of the first HARQ state and the second HARQ state may indicate any of the following: (i) downlink HARQ feedback may be enabled, (ii) downlink HARQ feedback may be disabled, (iii) a first uplink HARQ mode, and (iv) a second uplink HARQ mode.

[0264] In various embodiments, the first uplink HARQ mode may be associated with monitoring of the HARQ retransmission grant information being enabled, and the second uplink HARQ mode may be associated with monitoring of the HARQ retransmission grant information being disabled.

[0265] In various embodiments, the second HARQ state may be applicable to any of: (i) uplink transmission scheduled by an uplink grant of a DCI, (ii) downlink reception scheduled by a downlink assignment of a DCI, (iii) one or more subsequent transmissions of a HARQ process.

[0266] In various embodiments, the first HARQ state may indicate that downlink HARQ feedback may be disabled and the second HARQ state may indicate that downlink HARQ feedback may be enabled.In various embodiments, performing the second DRX operation may include delaying monitoring to receive retransmissions based on a WTRU to base station round trip time.

[0267] In various embodiments, delaying monitoring to receive a retransmission may include delaying monitoring of a physical downlink control channel based on a WTRU to base station round trip time.

[0268] In various embodiments, DRX may be performed based on the second HARQ state until the first HARQ state may be indicated in a subsequent DCI.

[0269] In various embodiments, DRX may be performed according to the first HARQ state after DRX has been performed according to the second HARQ state for a period of time.

[0270] In various embodiments, the second HARQ state may be applicable to any of: (i) each serving cell, (ii) each HARQ process, and (iii) all HARQ processes of the WTRU.

[0271] In various embodiments, the LCP restriction may associate one or more logical channels with an uplink HARQ mode.In various embodiments, the LCP may be performed based on configuration information indicating that DCI-based indication of HARQ status may be enabled.

[0272] In various embodiments, data for one or more logical channels indicated in the LCP restriction may be transmitted in the second DRX operation based on the uplink HARQ mode indicated in the LCP restriction matching the second HARQ state indicated in the DCI.

[0273] Fig. 9 is a diagram illustrating an example method 900 for adaptive DRX based on L1 indication. The method 900 may be implemented in a WTRU. As shown at 910, the WTRU may receive configuration information indicating (1) a DCI-based indication of a HARQ state and (2) downlink HARQ feedback may be disabled for a HARQ process. As shown at 920, the WTRU may perform a first DRX operation with downlink HARQ feedback disabled. As shown at 930, the WTRU may receive a DCI. As shown at 940, the WTRU may determine that the DCI may indicate that downlink HARQ feedback may be enabled for the HARQ process based on the configuration information indicating that the DCI-based indication of the HARQ state may be enabled. As shown at 950, the WTRU may perform a second DRX operation (e.g., associated with a HARQ process) with downlink HARQ feedback enabled, wherein the WTRU may delay monitoring to receive retransmissions based on a WTRU to base station round trip time.

[0274] In various embodiments, delaying monitoring to receive a retransmission may include delaying monitoring of a physical downlink control channel based on a WTRU to base station round trip time.

[0275] In various embodiments, downlink HARQ feedback may be enabled for either: (i) a downlink reception scheduled by a downlink assignment of a DCI, and (ii) one or more subsequent transmissions of a HARQ process.

[0276] In various embodiments, DRX may be performed with downlink HARQ feedback enabled until a subsequent DCI may indicate that downlink HARQ feedback may be disabled.

[0277] In various embodiments, after DRX may be performed with downlink HARQ feedback enabled for a period of time, DRX may be performed with downlink HARQ feedback disabled.

[0278] In various embodiments, DRX operation with HARQ feedback enabled may be applicable to any of: (i) each serving cell, (ii) each HARQ process, and (iii) all HARQ processes of the WTRU.

[0279] The following references may have been cited above, and each is hereby incorporated by reference in its entirety.

[0280] 3GPP TS 38.321, “NR, Medium Access Control (MAC) Protocol Specification” v17.1.0.

[0281] 3GPP TS 36.321, “Evolved Universal Terrestrial Air Access (E-UTRA); Medium Access Control (MAC) Protocol Specification” v17.1.0.

[0282] This article describes the embodiments using 3GPP HARQ as an example of an automatic repeat request technology. The embodiments described herein may be applicable to any other type of automatic repeat request technology. This article describes the embodiments using 3GPP DRX as an example of a transmission / reception technology. The embodiments described herein may be applicable to any other type of transmission / reception technology.

[0283] Any features, variations or embodiments described for the method are compatible with an apparatus including means for processing the disclosed method, an apparatus including a processor configured to process the disclosed method, a computer program product including program code instructions, and a non-transitory computer-readable storage medium storing the program instructions.

[0284] Although features and elements are provided above in specific combinations, it will be understood by those skilled in the art that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited in terms of the specific embodiments described in the present application, which are intended to be illustrations of various aspects. Without departing from its spirit and scope, many modifications and changes can be made, as will be apparent to those skilled in the art. Any element, action or instruction used in the description of the present application should not be interpreted as being critical or necessary to the present invention unless explicitly provided as such. In addition to those listed herein, functionally equivalent methods and devices within the scope of the present disclosure are apparent to those skilled in the art from the foregoing description. Such modifications and changes are intended to fall within the scope of the appended claims. The present disclosure is limited only by the terms of the appended claims and the full scope of equivalents given by such claims. It should be understood that the present disclosure is not limited to specific methods or systems herein.

[0285] For simplicity, the foregoing embodiments are discussed with respect to terminology and structure of devices with infrared capabilities (i.e., infrared transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems using other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0286] It will also be understood that the terms used herein are used only for the purpose of describing specific embodiments and are not intended to be limiting. As used herein, the term "video" or the term "image" may mean any of a snapshot, a single image, and / or a plurality of images displayed over a certain time basis. As another example, when referred to herein, the term "user equipment" and its abbreviation "UE", the term "remote" and / or the term "head-mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and / or receive unit (WTRU); (ii) any of many embodiments of a WTRU; (iii) a device with wireless capabilities and / or wired capabilities (e.g., wearable) that is configured with some or all of the structure and functionality of a WTRU; (iii) a device with wireless capabilities and / or wired capabilities that is configured with less than all of the structure and functionality of a WTRU; or (iv) a similar device. References herein to Figures 1A to 1D Details of an example WTRU are provided, which may be representative of any WTRU set forth herein. As another example, various disclosed embodiments herein are described above and below as utilizing a head mounted display. Those skilled in the art will recognize that devices other than a head mounted display may be utilized, and some or all of the present disclosure and various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adapted reality experience.

[0287] In addition, the methods provided herein may be implemented in a computer program, software, or firmware that is incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of non-temporary computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

[0288] Variations of the methods, devices, and systems provided above are possible without departing from the scope of the present invention. In view of the various embodiments that may be applied, it should be understood that the embodiments shown are merely examples and should not be considered to limit the scope of the appended claims. For example, the embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery, etc.) that provides any suitable voltage.

[0289] In addition, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices including processors are mentioned. These devices may include at least one central processing unit ("CPU") and memory. According to the practice of those skilled in the art of computer programming, references to actions and symbolic representations of operations or instructions may be performed by various CPUs and memories. Such actions and operations or instructions may be referred to as "execution," "computer execution," or "CPU execution."

[0290] Those of ordinary skill in the art will appreciate that the actions and symbolic representations of operations or instructions include manipulation of electrical signals by the CPU. The electrical system represents data bits, which may cause the final conversion or reduction of electrical signals and maintain the data bits in memory locations in the storage system, thereby reconfiguring or otherwise changing the operation of the CPU and other processing of signals. The memory locations where the data bits are maintained are physical locations having specific electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs, and other platforms and CPUs may support the provided methods.

[0291] The data bits may also be maintained on a computer-readable medium, including a magnetic disk, an optical disk, and any other volatile (e.g., random access memory (RAM)) or non-volatile (e.g., read-only memory (ROM)) mass storage system readable by a CPU. The computer-readable medium may include cooperating or interconnected computer-readable media that reside only on a processing system or distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories, and other platforms and memories may support the provided methods.

[0292] In an illustrative embodiment, any operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and / or any other computing device.

[0293] There is little difference between hardware and software implementations of various aspects of the system. The use of hardware or software is usually (but not always, as in some cases, the choice of hardware or software may become important) a design choice that represents a cost-efficiency trade-off. There may be various vehicles (e.g., hardware, software, and / or firmware) with which the processes and / or systems and / or other technologies described herein can be implemented, and the preferred vehicle may change with the context in which the processes and / or systems and / or other technologies are deployed. For example, if the implementer determines that speed and accuracy are most important, then the implementer may select a primary hardware and / or firmware vehicle. If flexibility is most important, then the implementer may select a primary software implementation. Alternatively, the implementer may select some combination of hardware, software, and / or firmware.

[0294] The foregoing detailed description has been described various embodiments of the apparatus and / or process by using block diagrams, flow charts and / or examples. Insofar as such block diagrams, flow charts and / or examples include one or more functions and / or operations, it will be understood by those skilled in the art that each function and / or operation within such block diagrams, flow charts or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware or indeed any combination thereof. In an embodiment, several parts of the subject matter described herein may be implemented via an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP) and / or other integrated formats. However, those skilled in the art will recognize that all or part of some aspects of the embodiments disclosed herein may be equivalently implemented in an integrated circuit, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware or almost as any combination thereof, and according to the present disclosure, designing circuit systems and / or writing codes for software and / or firmware will be completely within the skill range of those skilled in the art. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein can be distributed as a program product in a variety of forms, and that the illustrative examples of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to actually carry out the distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable media such as floppy disks, hard drives, CDs, DVDs, digital tapes, computer memory, etc.; and transmission media such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0295] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner set forth herein, and thereafter use engineering practices to integrate such described devices and / or processes into data processing systems. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system by a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system can typically include a system unit housing, a video display device, a memory such as volatile and non-volatile memory, a processor such as a microprocessor and a digital signal processor, a computing entity such as an operating system, a driver, a graphical user interface, and an application, one or more interactive devices such as a touch pad or screen, and / or a control system including a feedback loop and a control motor (e.g., feedback for sensing position and / or velocity; a control motor for moving and / or adjusting components and / or quantities). A typical data processing system can be implemented using any suitable commercially available components, such as components typically found in data computing / communication and / or network computing / communication systems.

[0296] The subject matter described herein sometimes illustrates different parts that are included in different other parts or connected with different other parts.It should be understood that the architecture of such description is only an example, and many other architectures that realize the same function can actually be implemented.In a conceptual sense, any arrangement of parts for realizing the same function is effectively "associated" so that the desired function can be realized.Therefore, any two parts that are combined to realize a specific function in this article can be regarded as "associated" with each other so that no matter how the architecture or intermediate parts realize the desired function.Similarly, any two parts that are associated in this way can also be regarded as "operably connected" or "operably coupled" to realize the desired function, and any two parts that can be associated in this way can also be regarded as "operably coupled" to realize the desired function.The specific example of operable coupling includes (but is not limited to) parts that can be matched physically and / or physically interact, and / or parts that can be wirelessly interacted and / or wirelessly interacted, and / or parts that can be logically interacted and / or parts that can be logically interacted.

[0297] With respect to the use of substantially any plural and / or singular terms herein, those skilled in the art can translate from the plural to the singular and / or from the singular to the plural where appropriate to the context and / or application. For clarity, the various singular / plural arrangements may be expressly set forth herein.

[0298] Those skilled in the art will understand that, in general, the terms used herein and particularly in the appended claims (e.g., the bodies of the appended claims) are generally intended to be "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "including but not limited to," etc.). Those skilled in the art will further understand that if a specific number of an introduced claim statement is intended, such intent will be expressly stated in the claim, and in the absence of such a statement, such intent is not present. For example, where only one item is intended, the term "single" or similar language may be used. To aid understanding, the following appended claims and / or the description herein may include the use of the introductory phrases "at least one" and "one or more" to introduce multiple claim statements. However, the use of such phrases should not be interpreted as implying that a claim recitation introduced by the indefinite article "a" or "an" will limit any particular claim including such introduced claim recitation to embodiments including only one such recitation, even if the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"). The same is true for the use of definite articles to introduce claim recitations. In addition, even if a specific number of introduced claim recitations is explicitly recited, one skilled in the art will recognize that such recitation should be interpreted as meaning at least the recited number (e.g., merely reciting "two recitations" without other modifiers means at least two recitations or two or more recitations). Furthermore, in those cases where a convention similar to “at least one of A, B, and C, etc.” is used, generally, such construction is intended to represent the convention that one skilled in the art would understand (e.g., “a system having at least one of A, B, and C” would include, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and / or both A, B, and C, etc.). In those cases where a convention similar to “at least one of A, B, or C, etc.” is used, generally, such meaning is intended in the sense that one skilled in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and / or both A, B, and C, etc.). One skilled in the art would further understand that any transitional words and / or phrases (whether in the specification, claims, or drawings) that actually give two or more alternatives should be understood to contemplate the possibility of including one of the items, either of the items, or both of the items.For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B." In addition, the term "any" as used herein followed by a list of multiple items and / or categories of items is intended to include "any," "any combination," "any multiple," and / or "any combination of multiples," either alone or in combination with other items and / or other categories of items. Furthermore, the term "set," as used herein, is intended to include any number of items, including zero. Additionally, the term "number," as used herein, is intended to include any number, including zero. And the term "plurality," as used herein, is intended to be synonymous with "multiple."

[0299] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0300] As will be understood by those skilled in the art, for any and all purposes, such as in providing a written description, all ranges disclosed herein also encompass any and all possible sub-ranges and combinations of sub-ranges thereof. Any listed range can be easily identified as fully describing and capable of decomposing the same range into at least equal halves, one-third, one-quarter, one-fifth, one-tenth, etc. As a non-limiting example, each range discussed herein can be easily decomposed into a lower third, a middle third, and an upper third, etc. As will be understood by those skilled in the art, all languages ​​such as "at most", "at least", "greater than", "less than", etc. include the enumerated numbers, and refer to the ranges that can be subsequently subdivided into sub-ranges as discussed above. Finally, as will be understood by those skilled in the art, the range includes each individual member. Therefore, for example, a group with 1 to 3 units refers to a group with 1, 2 or 3 units. Similarly, a group with 1 to 5 units refers to a group with 1, 2, 3, 4 or 5 units, and so on.

[0301] Furthermore, the claims should not be read as limited to the order or elements provided unless otherwise stated. In addition, the use of the term "means for..." in any claim is intended to invoke 35 U.S.C. § 112, 6 or means-plus-function claim format, and any claim without the term "means for..." is not intended to be so.

Claims

1. A method implemented in a wireless transmitting / receiving unit, the method comprising: receiving configuration information indicating: (1) a downlink control information (DCI)-based indication of a hybrid automatic repeat request (HARQ) state, and (2) a first HARQ state associated with the HARQ process; performing a first discontinuous reception (DRX) operation based on the first HARQ state; Receive DCI; determining, based on the configuration information, that the DCI indicates a second HARQ state associated with the HARQ process, the configuration information indicating that DCI-based indication of the HARQ state is enabled; as well as A second DRX operation associated with the HARQ process is performed based on the second HARQ state.

2. The method according to claim 1, wherein: The second HARQ state is indicated in any one of uplink grant information and downlink assignment information.

3. The method according to any one of claims 1 to 2, wherein: The second HARQ state is different from the first HARQ state.

4. The method according to any one of claims 1 to 3, wherein: Any of the first HARQ state and the second HARQ state indicates any of the following: (i) downlink HARQ feedback is enabled, (ii) downlink HARQ feedback is disabled, (iii) a first uplink HARQ mode, and (iv) a second uplink HARQ mode.

5. The method according to claim 4, wherein: The first uplink HARQ mode is associated with monitoring of HARQ retransmission grant information being enabled, and wherein the second uplink HARQ mode is associated with monitoring of HARQ retransmission grant information being disabled.

6. The method according to any one of claims 1 to 5, wherein: The second HARQ state is applicable to any of: (i) uplink transmission scheduled by an uplink grant of the DCI, (ii) downlink reception scheduled by a downlink assignment of the DCI, (iii) one or more subsequent transmissions of the HARQ process.

7. The method according to any one of claims 4 to 6, wherein: The first HARQ state indicates that downlink HARQ feedback is disabled, wherein the second HARQ state indicates that downlink HARQ feedback is enabled, and wherein performing the second DRX operation comprises delaying monitoring to receive retransmissions based on a WTRU to base station round trip time.

8. The method according to claim 7, wherein: Delaying monitoring to receive a retransmission includes delaying monitoring of a physical downlink control channel based on the WTRU to base station round trip time.

9. The method according to any one of claims 5 to 6, wherein: The second HARQ state indicates the first uplink HARQ mode, and wherein performing the second DRX operation comprises monitoring the HARQ retransmission grant information during a time period that includes at least a WTRU to base station round trip time.

10. The method according to any one of claims 1 to 9, wherein: DRX is performed based on the second HARQ state until the first HARQ state is indicated in a subsequent DCI.

11. The method according to any one of claims 1 to 9, wherein: After performing DRX according to the second HARQ state for a period of time, performing DRX according to the first HARQ state.

12. The method according to any one of claims 1 to 11, wherein: The second HARQ state is applicable to any of: (i) each serving cell, (ii) each HARQ process, and (iii) all HARQ processes of the WTRU.

13. The method according to any one of claims 1 to 12, wherein: Logical channel prioritization (LCP) restricts associating one or more logical channels with an uplink HARQ mode, and wherein the LCP is performed based on the configuration information indicating that DCI-based indication of HARQ status is enabled.

14. The method according to claim 13, wherein: Data of the one or more logical channels indicated in the LCP restriction are transmitted in the second DRX operation based on the uplink HARQ mode indicated in the LCP restriction matching the second HARQ state indicated in the DCI.

15. A wireless transmit / receive unit (WTRU) comprising a circuit system including any of a transmitter, a receiver, a processor, and a memory, the WTRU being configured to: receiving configuration information indicating: (1) a downlink control information (DCI) based indication of a hybrid automatic repeat request (HARQ) state, and (2) disabling downlink HARQ feedback for a HARQ process; performing a first discontinuous reception (DRX) operation with downlink HARQ feedback disabled; Receive DCI; determining, based on the configuration information, that the DCI indicates enabling downlink HARQ feedback for the HARQ process, the configuration information indicating that DCI-based indication of HARQ state is enabled; as well as A second DRX operation is performed with downlink HARQ feedback enabled, wherein the WTRU is configured to delay monitoring to receive retransmissions based on a WTRU to base station round trip time.

16. The WTRU of claim 15 wherein: The WTRU being configured to delay monitoring to receive a retransmission includes the WTRU being configured to delay monitoring of a physical downlink control channel based on a round trip time from the WTRU to a base station.

17. The WTRU of any one of claims 15 to 16, wherein: Downlink HARQ feedback is enabled for either: (i) downlink reception scheduled by a downlink assignment of the DCI, and (ii) one or more subsequent transmissions of the HARQ process.

18. The WTRU of any one of claims 15 to 17, wherein: The WTRU is configured to perform DRX with downlink HARQ feedback enabled until a subsequent DCI indicates that downlink HARQ feedback is disabled.

19. The WTRU of any one of claims 15 to 17, wherein: The WTRU is configured to perform DRX with downlink HARQ feedback disabled after performing DRX with downlink HARQ feedback enabled for a period of time.

20. The WTRU of any one of claims 15 to 19, wherein: DRX operation with HARQ feedback enabled applies to either: (i) each serving cell, (ii) each HARQ process, and (iii) all HARQ processes of the WTRU.

Images