WO2025212661A1

WO2025212661A1 - Methods and apparatus for supporting aperiodic drx active time

Info

Publication number: WO2025212661A1
Application number: PCT/US2025/022558
Authority: WO
Inventors: Prasanna Herath; Young Woo Kwak; Nazli KHAN BEIGI; Benoit Pelletier; Moon Il Lee; Jongwoo HONG; Brian Martin; Virgile Garcia
Original assignee: InterDigital Patent Holdings Inc
Current assignee: InterDigital Patent Holdings Inc
Priority date: 2024-04-01
Filing date: 2025-04-01
Publication date: 2025-10-09
Anticipated expiration: 2026-10-01

Abstract

A method comprises receiving configuration information comprising a threshold value for skipping a second discontinuous reception (DRX) active time period after activation of a first DRX active time period, and receiving an indication, via a low power wake-up signal (LP-WUS), for activating the first DRX active time period and starting a DRX on duration timer associated with the first DRX active time period after a time offset from reception of the LP-WUS. A PDCCH transmission is received in resources while the DRX on duration timer associated with the first DRX active time period is running and receiving a PDSCH transmission or transmitting a PUSCH or PUCCH transmission based on the received PDCCH transmission. The method comprises determining to skip the second DRX active time period based on the at least one threshold value and reporting CSI in substitute CSI reporting uplink resources in the first DRX active time period.

Description

METHODS AND APPARATUS FOR SUPPORTING APERIODIC DRX ACTIVE TIME

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63/572,686, filed April 1 , 2024, the contents of which are incorporated herein by reference.

BACKGROUND

[0002] A wireless transmit/receive unit (WTRU) may monitor and receive a wake-up signal (WUS) via a first radio (e.g., a low-power or ultra-low power radio). The WUS may be called a low-power WUS (LP-WUS). The first radio may be called a low-power radio (LR) ora low power wake-up receiver (LP-WUR). Receiving a WUS (e.g., an LP-WUS), for example via the LR, may trigger wake-up or usage of a second radio of the WTRU (e.g., the WTRU’s main radio (MR)) for data and/or control signal transmission and/or reception.

SUMMARY

[0003] A wireless transmit/receive unit (WTRU) may be configured to receive configuration information. The configuration information may comprise at least one threshold value regarding skip conditions associated with a periodic discontinuous reception (DRX). The WTRU may be configured to receive an indication for activating an aperiodic DRX active time via a low power - wake up signal (LP-WUS). The WTRU may be configured to activate an aperiodic DRX active time at a time offset from the LP-WUS. The WTRU may be configured to receive a physical downlink control channel (PDCCH) transmission during the aperiodic DRX active time. The WTRU may be configured to skip a subsequent periodic DRX active time based on the received configuration information. The configuration information may comprise a first threshold value on a time difference between a beginning of an aperiodic DRX active time and a beginning of a subsequent periodic DRX active time. The configuration information may comprise a second threshold value on a time difference between an end of an aperiodic DRX active time and a start of a subsequent periodic DRX active time. The configuration information may comprise a threshold value regarding available battery power. The WTRU may be configured to receive uplink grant information indicating uplink resources in a periodic DRX inactive time to substitute for an uplink grant or scheduled uplink resources for channel state information (CSI) reporting in each periodic DRX active time. The WTRU may be configured to receive a configuration for low power - wake up signal (LP- WUS) monitoring, a DRX configuration, an offset between a LP-WUS and an aperiodic DRX active time, and configuration information for monitoring the LP-WUS. The WTRU may be configured to skip a subsequent periodic DRX active time on a condition that the time difference between a beginning of an aperiodic DRX active time and a beginning of a subsequent periodic DRX active time is less than the first threshold value. The WTRU may be configured to skip a subsequent periodic DRX active time on a condition that the time difference between an end of an aperiodic DRX active time and a start of a subsequent periodic DRX active time is less than the second threshold value. The WTRU may be configured to skip a subsequent periodic DRX active time on a condition that an available battery power is less than the threshold value regarding available battery power. The skipping a subsequent periodic DRX active time may comprise not starting an associated drx-onDurationTimer and keeping a main radio in a sleep state. The skipping a subsequent periodic DRX active time may further comprise early reporting a CSI using the received uplink grant information on a condition that a CSI report is scheduled to be sent within the skipped DRX active time. The resources for transmitting the early CSI may be an earliest resource located within the aperiodic DRX active time. The skipping a subsequent periodic DRX active time may further comprise indicating a decision to skip a subsequent periodic DRX active time, a reason to skip a subsequent periodic DRX active time, and battery status information. The skipping a subsequent periodic DRX active time may further comprise monitoring a LP-WUS during the skipped periodic DRX active time. If a start-to-startJimeGap is greater than or equal to the first threshold value on time gap and/or the end-to-startJimeGap is greater than or equal to the second threshold on time gap and/or available battery power is greater than or equal to the configured threshold value regarding available battery power, the WTRU may begin the periodic DRX active time according to the configured schedule and may limit the active time (e.g., may scale down drx-onDurationTimer by a pre-configured factor). The WTRU may monitor for and receive a PDCCH transmission during a periodic DRX active time.

[0004] A method may be used by a wireless transmit/receive unit (WTRU). The method may comprise receiving configuration information. The configuration information may comprise at least one threshold value for skipping a second discontinuous reception (DRX) active time period after activation of a first DRX active time period. The method may comprise receiving an indication, via a low power wake-up signal (LP-WUS), for activating the first DRX active time period. The method may comprise starting a DRX on duration timer associated with the first DRX active time period after a time offset from reception of the LP-WUS. The method may comprise monitoring for and receiving a physical downlink control channel (PDCCH) transmission in resources while the DRX on duration timer associated with the first DRX active time period is running. The method may comprise receiving a physical downlink shared channel (PDSCH) transmission or transmitting a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission based on the received PDCCH transmission. The method may comprise determining to skip the second DRX active time period based on the at least one threshold value. The method may comprise reporting channel state information (CSI), for a CSI report scheduled to be reported in the second DRX active time period, in substitute CSI reporting uplink resources in the first DRX active time period. The method may comprise skipping the second DRX active time period based on the at least one threshold value, based on the determining to skip. The method may comprise skipping the second DRX active time period may comprise the main radio (MR) continuing in a sleep state and not starting a DRX on duration timer associated with the second DRX active time period. The at least one threshold value may comprise: an end-to-start time gap threshold value associated with a time difference between an end of the first DRX active time period and a start of the second DRX active time period, wherein the end of the first DRX active time period is based on an end of a timer associated with the first DRX active time period, and wherein the start of the second DRX active time period is based on start of a DRX on duration timer associated with the second DRX active time period. The method may comprise determining to skip the second DRX active time period based on the end of the first DRX active time period and the start of the second DRX active period time being less than the end-to-start time gap threshold value. The at least one threshold value may comprise an available battery power threshold value. The method may comprise determining to skip the second DRX active time period based on an available battery power being less than the available battery power threshold value. The method may comprise monitoring a LP- WUS using a low power radio (LR) during a skipped second DRX active time period. The configuration information may comprise uplink grant information indicating substitute CSI reporting uplink resources during the first DRX active time period. The reporting CSI in substitute CSI reporting uplink resources may be based on a CSI report being ready and CSI measurements being performed before or during the first DRX active time period.

[0005] A wireless transmit/receive unit (WTRU) may comprise a receiver; a transmitter; and a processor. The receiver may be configured to receive configuration information. The configuration information may comprise at least one threshold value for skipping a second discontinuous reception (DRX) active time period after activation of a first DRX active time period .The receiver may be further configured to receive an indication, via a low power wake-up signal (LP-WUS), for activating the first DRX active time period. The processor may be configured to start a DRX on duration timer associated with the first DRX active time period after a time offset from reception of the LP-WUS. The processor and the receiver may be further configured to monitor for and receive a physical downlink control channel (PDCCH) transmission in resources while the DRX on duration timer associated with the first DRX active time period is running. The receiver may be further configured to receive a physical downlink shared channel (PDSCH) transmission or the transmitter may be configured to transmit a physical uplink shared channel (PUSCH) transmission ora physical uplink control channel (PUCCH) transmission based on the received PDCCH transmission. The processor may be further configured to determine to skip the second DRX active time period based on the at least one threshold value. The transmitter may be further configured to report channel state information (CSI), for a CSI report scheduled to be reported in the second DRX active time period, in substitute CSI reporting uplink resources in the first DRX active time period. The processor may be further configured to skip the second DRX active time period based on the at least one threshold value, based on the determining to skip. Skipping the second DRX active time period may comprise the main radio (MR) continuing in a sleep state and not starting a DRX on duration timer associated with the second DRX active time period. The at least one threshold value may comprise: an end- to-start time gap threshold value associated with a time difference between an end of the first DRX active time period and a start of the second DRX active time period, wherein the end of the first DRX active time period is based on an end of a timer associated with the first DRX active time period, and wherein the start of the second DRX active time period is based on start of a DRX on duration timer associated with the second DRX active time period. The processor may be further configured to determine to skip the second DRX active time period based on the end of the first DRX active time period and the start of the second DRX active period time being less than the end-to-start time gap threshold value. The at least one threshold value may comprise an available battery power threshold value. The processor may be further configured to determine to skip the second DRX active time period based on an available battery power being less than the available battery power threshold value. The processor and the receiver may be further configured to monitor a LP-WUS using a low power radio (LR) during a skipped second DRX active time period. The configuration information may comprise uplink grant information indicating substitute CSI reporting uplink resources during the first DRX active time period. The reporting CSI in substitute CSI reporting uplink resources may be based on a CSI report being ready and CSI measurements being performed before or during the first DRX active time period.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, wherein like reference numerals in the figures indicate like elements, and wherein:

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

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

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

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

[0011] FIG. 2 shows an example simplified receiver architecture of a WTRU utilizing a low-power wake-up receiver;

[0012] FIG. 3 shows an example of Long DRX operation;

[0013] FIG. 4 shows an example of activating aperiodic DRX active time via a LP-WUS;

[0014] FIG. 5 shows an example DRX operation with aperiodic DRX time activation;

[0015] FIG. 6 shows an example method for power efficient aperiodic DRX active time; and

[0016] FIG. 7 shows an example method for power efficient DRX active time.

DETAILED DESCRIPTION

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

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

[0019] The communications systems 100 may also include a base station 114a and/or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and/or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, 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.

[0020] The base station 114a may be part of the RAN 104, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, and the like. The base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

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

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

[0023] 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). [0024] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using NR.

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

[0026] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like. [0027] The base station 114b in FIG. 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.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 yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106.

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

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

[0030] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellularbased radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0031] FIG. 1B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

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

[0033] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 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 an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and/or receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

[0034] Although the transmit/receive element 122 is depicted in FIG. 1B as a single element, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116. [0035] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.

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

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

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

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

[0040] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)). [0041] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

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

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

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

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

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

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

[0048] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers. [0049] Although the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0063] The CN 106 shown in FIG. 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.

[0064] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.

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

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

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

[0068] In view of FIGs. 1A-1 D, and the corresponding description of FIGs. 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.

[0069] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications.

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

[0071] The following abbreviations and acronyms may be referred to:

Af Sub-carrier spacing gNB NR NodeB

ACK Acknowledgement

AP Aperiodic

BFR Beam Failure Recovery

BFD-RS Beam Failure Detection-Reference Signal

BLER Block Error Rate

BWP Bandwidth Part

CA Carrier Aggregation

CAPC Channel access priority class

CB Contention-Based (e.g. access, channel, resource)

CCA Clear Channel Assessment

CCE Control Channel Element

CDM Code Division Multiplexing

C-DRX Connected Mode DRX

CE Control Element

CG Configured grant or cell group

CLI Cross-Link Interference

CoMP Coordinated Multi-Point transmission/reception

COT Channel Occupancy Time

CP Cyclic Prefix

CPE Common Phase Error

CP-OFDM Conventional OFDM (relying on cyclic prefix) CQI Channel Quality Indicator CN Core Network (e.g. LTE/NR packet core or NR core) CRC Cyclic Redundancy Check CSI Channel State Information CSI-RS Channel State Information-Reference Signal CU Central Unit CW Contention Window CWS Contention Window Size CO Channel Occupancy D2D Device to Device transmissions (e.g. LTE Sidelink) DAI Downlink Assignment Index DC Dual Connectivity DCI Downlink Control Information DCP DCI with CRC scrambled by PS-RNTI DFI Downlink feedback information DG Dynamic grant DL Downlink DM-RS Demodulation Reference Signal DR Detection Rate DRB Data Radio Bearer DRX Discontinuous reception DU Distributed Unit EN-DC E-UTRA - NR Dual Connectivity EPC Evolved Packet Core FD-CDM Frequency Domain-Code Division Multiplexing FDD Frequency Division Duplexing FDM Frequency Division Multiplexing FSK Frequency Shift Keying HARQ Hybrid Automatic Repeat Request ICI Inter-Cell Interference ICIC Inter-Cell Interference Cancellation IP Internet Protocol LAA License Assisted Access LBT Listen-Before-Talk LCH Logical Channel LCID Logical Channel Identity LCP Logical Channel Prioritization LLC Low Latency Communications LP Low Power LP-SS Low Power Synchronization Signal LP-WUS Low Power Wake-Up Signal LP-WUR Low Power Wake-Up Receiver LR Low Power Radio LTE Long Term Evolution e.g. from 3GPP LTE R8 and up MAC Medium Access Control MAC CE Medium Access Control Element NACK Negative ACK MAC Medium Access Control MAC-CE MAC Control Element MBMS Multimedia Broadcast Multicast System MCG Master Cell Group MCS Modulation and Coding Scheme MDR Missed Detection Rate MIMO Multiple Input Multiple Output MO Monitoring Occasion MR Main Radio MTC Machine-Type Communications MR-DC Multi-RAT Dual Connectivity NAS Non-Access Stratum NCB-RS New candidate beam-Reference Signal NE-DC NR-RAN - E-UTRA Dual Connectivity NR New Radio NR-DC Dual Connectivity with OCC Orthogonal Cover Code OFDM Orthogonal Frequency-Division Multiplexing OFDMA Orthogonal Frequency-Division Multiple Access OOB Out-Of-Band (emissions) OOK On Off Keying P Total available UE power in a given transmission interval Pcell Primary cell of Master Cell Group PCG Primary Cell Group PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared Channel PDU Protocol Data Unit PER Packet Error Rate PF Paging Frame PHY Physical Layer PLMN Public Land Mobile Network PLR Packet Loss Rate PO Paging Occasion PRACH Physical Random-Access Channel PRB Physical Resource Block PRI PUCCH Resource Indicator PRS Positioning Reference Signal Pscell Primary cell of a Secondary cell group PSS Primary Synchronization Signal PT-RS Phase Tracking-Reference Signal PS-RNTI Power Saving RNTI PUCCU Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QoS Quality of Service (from the physical layer perspective) RAB Radio Access Bearer RAN PA Radio Access Network Paging Area RACH Random Access Channel (or procedure) RAR Random Access Response RAT Radio Access Technology RB Resource Block RCU Radio access network Central Unit RF Radio Front end RE Resource Element RLF Radio Link Failure RLM Radio Link Monitoring RNTI Radio Network Identifier RO Random Access Occasion ROM Read-Only Mode (for MBMS) RRC Radio Resource Control RRM Radio Resource Management

RS Reference Signal

RSRP Reference Signal Received Power

RSRQ Reference Signal Received Quality

RTT Round-Trip Time

SBFD Subband non-overlapping full duplex

SCG Secondary Cell Group

SCMA Single Carrier Multiple Access

SCS Sub-Carrier Spacing

SDU Service Data Unit

SDT Small Data Transmission

SOM Spectrum Operation Mode

SP Semi-persistent

SpCell Primary cell of a master or secondary cell group.

SRB Signaling Radio Bearer

SS Synchronization Signal

SRS Sounding Reference Signal

SSS Secondary Synchronization Signal

SUL Supplementary Uplink

SWG Switching Gap (in a self-contained subframe)

TB Transport Block

TBS Transport Block Size

TCI Transmission Configuration Index

TDD Time-Division Duplexing

TDM Time-Division Multiplexing

Tl Time Interval (in integer multiple of one or more symbols)

TTI Transmission Time Interval (in integer multiple of one or more symbols)

TRP Transmission / Reception Point

TRPG Transmission / Reception Point Group

TRS Tracking Reference Signal

TRx Transceiver

UE User Equipment

UCI Uplink Control Information

UL Uplink

URC Ultra-Reliable Communications

URLLC Ultra-Reliable and Low Latency Communications

V2X Vehicular communications

WLAN Wireless Local Area Networks and related technologies (IEEE 8O2.xx domain)

WUS Wake-up signal

XDD Cross Division Duplex

[0072] FIG. 2 shows an example of a simplified receiver architecture of a WTRU utilizing a low-power wakeup receiver. The WTRU may comprise a wake-up radio receiver (RX) 230 that may be a low-power radio (LR) or a low power wake-up radio (LP-WUR). The WTRU may comprise a main radio RX (MR) 240. The wake-up RX may receive a LP-WUS 210. The MR may receive a main radio signal 220. This has the potential to reduce the power consumption of wireless devices. The WTRU may comprise a baseband processor 250 and an application processor 260.

[0073] A Rel-19 Work Item (Wl) on LP-WUS/LP-WUR for NR is focused on supporting a deep sleep state for the MR while the WTRU is in a radio resource control (RRC) IDLE or RRC INACTIVE state (referred to as IDLE/INACTIVE mode LP-WUS monitoring) and supporting the WTRU to skip monitoring a PDCCH while in an RRC CONNECTED state (referred to as CONNECTED mode LP-WUS monitoring).

[0074] Discontinuous reception (DRX) is used to reduce WTRU power consumption by allowing the WTRU to periodically enter in to a ‘power saving state’ (DRX inactive) during which the WTRU is not required to monitoring for a PDCCH. To monitor a PDCCH for possible downlink/uplink data, the WTRU switches to an ‘active state’ for a limited time (DRX active time) before returning to a ‘power saving state’.

[0075] FIG. 3 shows an example of Long DRX operation. Connected Mode DRX (C-DRX) is used in wireless communications to help a WTRU save power while the WTRU is in an RRC connected state. With C- DRX, within each DRX cycle, a WTRU periodically performs PDCCH monitoring for a short period of time (DRX active time) and remains in a power saving state during the rest of the time (DRX inactive time). This helps a WTRU to save power.

[0076] The downside of DRX is high latency. For example, when a gNB receives DL data during a DRX inactive time, the gNB has to wait until an upcoming DRX active time to schedule DL transmissions.

[0077] The use of aperiodic DRX Active Time may reduce latency in DRX. The latency due to use of DRX (e.g., C-DRX) may be reduced by supporting aperiodic DRX active time within a (periodic) DRX inactive duration. For example, when a gNB receives DL data during a (periodic) DRX inactive time, without waiting until the subsequent (periodic) DRX active time to schedule DL data transmission, the gNB may trigger an aperiodic DRX active time for a WTRU. To trigger an aperiodic DRX active time, an early indication signal (e.g., LP-WUS) may be used as shown in FIG. 4.

[0078] The latency due to use of C-DRX may be reduced by using a LP-WUS to activate an aperiodic DRX Active time (e.g., trigger drx-onDurationTimer). Dynamically activated aperiodic DRX active time for PDCCH monitoring may increase power consumption and create high power consumption during a short span of time due to the following reasons. If aperiodic DRX active time is supported, the WTRU wakes up the MR for PDCCH monitoring more often than expected in C-DRX and if an aperiodic DRX active time and a periodic DRX active time takes place within a short span of time, power demand on the WTRU’s battery may be high for a short span of time. A procedure on how to support aperiodic DRX active time in a power efficient way is needed.

[0079] In an embodiment, a WTRU may activate an aperiodic DRX active time prior to a scheduled periodic DRX active time based on an indication received via a LP-WUS. The WTRU may skip the periodic DRX active time and skip or early transmit CSI reporting configured to be transmitted during the skipped periodic DRX active time.

[0080] A WTRU may receive one or more of the following configuration or indications.

[0081] A WTRU may receive one or more thresholds or threshold values (e.g. skip conditions for periodic

DRX) for skipping a periodic DRX active time after activation of an aperiodic DRX active time. For example, a first threshold (e.g., 1st threshold on time gap) on a time difference (i.e. start-to-startJimeGap) between the beginning of an aperiodic DRX active time and beginning of a subsequent periodic DRX active time (e.g., time difference between starting points of drx-onDurationTimers associated with aperiodic DRX active time and subsequent periodic DRX active time). For example, a second threshold or threshold value (e.g., 2^nd threshold on time gap) on a time difference (i.e. end-to-start_time_gap) between an end of an aperiodic DRX active time (e.g., end of associated drx-lnactivityTimer) and start of a subsequent periodic DRX active time (e.g., start of associated drx-onDurationTimer). For example, a third threshold or threshold value regarding available battery power.

[0082] The WTRU may receive a set of grants or UL resources (substituting CSI reporting resources) in a periodic DRX inactive time to substitute for grants or scheduled UL resources for CSI reporting in each periodic DRX active time.

[0083] The WTRU may receive a configuration for LP-WUS monitoring (e.g., LP-WUS periodicity, timefrequency resources, etc.), DRX configuration, offset between LP-WUS and aperiodic DRX active time, and indication/configuration for monitoring LP-WUS.

[0084] The WTRU may receive an indication for activating an aperiodic DRX active time via a LP-WUS. The WTRU may activate an aperiodic DRX active time (e.g., start drx-onDurationTimer associated with aperiodic DRX active time and monitor for PDCCH) at the configured time offset from the LP-WUS reception. The WTRU may receive a PDCCH transmission during the aperiodic DRX active time and/or may transmit a physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH) transmission based on scheduling received via the PDCCH or configured scheduling.

[0085] The WTRU may skip a subsequent periodic DRX active time based on ‘skip conditions for periodic DRX’. For example, if start-to-startJimeGap < 1st threshold on the time gap and/or end-to-startJimeGap < 2nd threshold on the time gap and/or available battery power < configured threshold, the WTRU may skip the subsequent periodic DRX active time (e.g., WTRU does not start associated timers (e.g., drx-onDurationTimer), and keeps the MR in a sleep state) and performs one or more of the following: (i) If a CSI report is scheduled to be sent within the skipped DRX active time, the WTRU may early report the CSI using a ‘substituting CSI reporting resources’ (e.g., the earliest resource located within aperiodic DRX active time). For example, the WTRU may early report CSI based on the corresponding CSI report is ready and/or CSI measurements are performed before or during the aperiodic DRX active time; (ii) the WTRU may indicate (e.g., along with an early CSI report in an aperiodic DRX active time/ preconfigured PUCCH within aperiodic DRX active time) to the gNB its decision on skipping a subsequent periodic DRX active time and a reason (e.g., ‘skip conditions for periodic DRX’ met) and/or report additional information (e.g., battery status, buffer status report); (iii) the WTRU may monitor a LP-WUS during a skipped periodic DRX active time. If a start-to-startJimeGap > 1st threshold on the time gap and/or the end-to-startJimeGap > 2nd threshold on the time gap and/or available battery power > configured threshold, the WTRU may begin the periodic DRX active time according to the configured schedule and may limit the active time (e.g., may scale down drx-onDurationTimer by a pre-configured factor). The WTRU may monitor for and receive a PDCCH transmission during a periodic DRX active time. [0086] A benefit of the an aperiodic DRX active time prior to a scheduled periodic DRX active time may be to limit the increase of power usage due to an aperiodic DRX active time. Another benefit may be to reduce latency caused by the use of DRX.

[0087] FIG. 5 shows an example of DRX operation with an aperiodic DRX time activation. A WTRU may activate an aperiodic DRX active time prior to a periodic DRX active time based on an indication received via a LP-WUS. For example, a WTRU may start a PDCCH monitoring timer, for example a drx-onDurationTimer, and monitor for and receive a PDCCH transmission during aperiodic DRX active time. Aperiodic DRX active time may be started within a DRX inactive time of a DRX cycle. The WTRU may skip a subsequent configured periodic DRX active time (e.g., the WTRU does not start drx-onDurationTimer during the DRX active time) and may skip or early transmit a CSI report scheduled to be transmitted during a skipped periodic DRX active time. [0088] Hereafter, 1st DRX configuration may be interchangeably used with periodic DRX configuration and DRX configuration associated with periodic DRX.

[0089] Hereafter, 2nd DRX configuration may be interchangeably used with DRX configuration for aperiodic DRX active time.

[0090] Hereafter, DRX active time scheduled by a 1st DRX configuration and periodic DRX active time may be interchangeably used.

[0091] Hereafter, periodic DRX active time may be interchangeably used with periodic C-DRX active time. [0092] Hereafter, aperiodic DRX active time may be interchangeably used with aperiodic C-DRX active time.

[0093] A WTRU may receive one or a combination of configurations and/or indications.

[0094] The WTRU may receive one or more thresholds or threshold values (e.g. skip conditions for period DRX) for skipping a periodic DRX active time after activation of an aperiodic DRX active time.

[0095] The WTRU may receive a threshold or threshold value (e.g. ‘1^st threshold on time gap’) on a time difference (e.g. ‘start-to-start JimeGap’) between a beginning of an aperiodic DRX active time and a beginning of a subsequent periodic DRX active time (e.g. the first DRX active time scheduled by the 1^st DRX configuration immediately after an aperiodic DRX active time). In an example configuration, start-to-start JimeGap may be the time difference between the starting time of drx-onDurationTimer associated with an aperiodic DRX active time (e.g., DRX active time activated via a LP-WUS) and the stating time of drx-onDurationTimer of a subsequent periodic DRX active time. In an example configuration, start-to-start JimeGap may be the time difference between the reception time of a first PDCCH (e.g., starting point of drx-lnactivityTimer) within an aperiodic DRX active time and a stating time of drx-onDurationTimer of a subsequent periodic DRX active time. [0096] The WTRU may receive a threshold or threshold value (e.g. ‘2nd thresholds on time gap’) on a time difference (e.g. ‘end-to-start JimeGap’) between an end of an aperiodic DRX active time and a start of a subsequent periodic DRX active time. In an example configuration, end-to-start JimeGap may be the time difference between the end of a timer associated with an aperiodic DRX active time (e.g., drx-lnactivityTimer, drx-onDurationTimer in the case drx-lnactivityTimer is not configured or not started due to not detecting a PDCCH, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL) and a starting time of a scheduled subsequent periodic DRX active time.

[0097] The WTRU may receive a threshold or threshold value on available battery power. For example, the available battery power information may comprise a percentage of remaining battery power, a duration the WTRU can be powered based on a preconfigured power use, and/or an absolute power left (e.g. mWh or mAh). [0098] The WTRU may receive information regarding a potential overlapping of an active time of an aperiodic DRX active time and a scheduled periodic DRX active time (e.g., overlap of drx-onDurationTimer or drx-lnactivityTimer of an aperiodic DRX active time and a scheduled subsequent periodic activity time).

[0099] The WRU may receive a first DRX configuration (e.g. DRX configuration associated with periodic DRX), which may include one or more of the following: DRX cycle duration for the periodic DRX, starting time of the periodic DRX active time (e.g., drx-SlotOffset), and one or more timers associated with the periodic DRX active time (drx-onDurationTimer, drx-lnactivityTimer, drx-RetransmissionTimerUL, drx- RetransmissionTimerDL), and rx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL.

[0100] The WRU may receive a second DRX configuration(e.g. DRX configuration for aperiodic DRX active times). In an example, the second DRX configuration may be configured via RRC signaling, medium access control - control element (MAC-CE) indication, or system information (SI). The second DRX configuration may include information regarding one or more of a DRX cycle duration, one or more timers (e.g., drx- onDurationTimer, drx-lnactivityTimer, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL, drx drx- HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL). In an example, the WTRU may determine the second DRX configuration based on the first DRX configuration. For example, a DRX cycle of the first DRX configuration may equal a preconfigured integer (e.g., preconfigured via RRC signaling, MAC-CE indication, or SI) x DRX cycle of the second DRX configuration, drx-onDurationTimer of the second DRX configuration may equal a preconfigured first scalar x drx-onDurationTimer of the second DRX configuration, drx-onDurationTimer of the second DRX configuration may equal a preconfigured second scalar x drx-lnactivityTimer of the second DRX configuration. The first and second scalar may be preconfigured via RRC signaling, MA-CE indication, or SI.

[0101] The WTRU may receive an offset between a LP-WUS and an aperiodic DRX active time (e.g. aperiodic DRX active time starting offset). For example, the offset may be from the time of the LP-WUS reception to the starting time of the aperiodic DRX active time (e.g., starting time of drx-onDurationTimer of aperiodic DRX active time).

[0102] The WTRU may receive a set of grants or UL resources (e.g. ‘substituting CSI reporting resources’) in an inactive time of the periodic DRX configuration to substitute for grants or scheduled UL resources to report CSI in (e.g., each) periodic DRX active time. [0103] The WTRU may receive a configuration associated with a LP-WUS and/or a low power synchronization signal (LP-SS). This may include one or more of the following: resource allocation (e.g., timefrequency resources, periodicity, etc.), modulation (e.g. OOK1 , OOK4, etc.), bandwidth, structure of LP-WUS and/or LP-SS.

[0104] The WTRU may activate connecting mode LP-WUS monitoring. In an embodiment, the WTRU may receive an indication or configuration (e.g., via RRC signaling, MAC-CE indication, downlink control information (DCI) indication, SI updates) for activating LP-WUS monitoring while in an RRC connected state (e.g., while C- DRX is configured). For example, the WTRU may be configured (e.g., via RRC signaling, MAC-CE indication, or SI) with a timer (e.g. LP-WUS monitoring activation timer) and/or a counter (e.g. LP-WUS monitoring activation counter). The WTRU may use the timer and/or counter to activate LP-WUS monitoring based on one or more of the following.

[0105] In an example, the WTRU may start a LP-WUS monitoring activation timer based on an indication received (e.g., via one or more of DCI indication, for example WTRUs specific and/or group specific, MAC-CE indication and SI) from the gNB. The WTRU may reset the LP-WUS monitoring activation timer based on detection of one or more events (e.g., reception of a PDCCH transmission, transmission of a PUCCH/PUSCH, physical random access channel (PRACH), etc.). If the timer expires, the WTRU may start monitoring a LP- WUS and/or LP-SS via the LR for example, starting from the first periodic DRX inactive or active time scheduled after a pre-configured (e.g., via RRC signaling, SI, MAC-CE indication) time offset. While monitoring for and receiving one or more channels/signals (e.g., LP-WUS, LP-SS) via LR, the WTRU may keep the MR in a power saving state.

[0106] In an example, the WTRU may receive an indication (e.g., via DCI indication, MAC-CE indication, or SI) from the gNB to start a counter, which may count one or more events (e.g., within a given time), and/or a timer. For example, the one or more events may be one or more of a number of activated periodic DRX (e.g., by initiating drx-onDurationTimer), number of one or more scheduled DL/UL channels (e.g., physical downlink shared channel (PDSCH) and/or PUSCHs), number of received/detected PDCCHs, number of transmitted UL channels/signals (e.g., one or more of PUCCH, PUSCH and PRACH), number of CSI reports sent by the WTRU, etc.) and a number of monitored first DRX cycles. If the counter reaches a threshold value (e.g., preconfigured via RRC signaling, MAC-CE indication, or SI) (e.g., before the timer expires), the WTRU may reset the timer and/or the counter. If the timer expires before the counter reaches the threshold value, the WTRU may start monitoring LP-WUS and/or LP-SS via the LR. For example, the WTRU may start monitoring of LP-WUS and/or LP-SS in a first periodic DRX inactive or active time (e.g., based on DRX configuration) after a time offset (e.g., a preconfigured/indicated time offset via one or more of RRC signaling, SI and MAC-CE indication) from the expiration of the timer. While monitoring for and receiving one or more signals/channels via the LR (e.g., LP-SS, LP-WUS, SSS, PSS), the WTRU may keep the MR in a power saving state (e.g., sleep state). [0107] In an example, the WTRU may receive an indication to start monitoring LP-WUS/LP-SS (e.g., via one or more of DCI indication, MAC-CE indication, RRC signaling and SI), for example from the gNB. The WTRU may start monitoring LP-WUS/LP-SS after a time offset (e.g., pre-configured via one or more of RRC signaling, SI, MAC-CE indication) from the indication to monitor LP-WUS/LP-SS. The WTRU may receive a configuration of the time offset in terms of a DRX cycle duration. For example, the time offset may be N x the DRX cycles duration (e.g., first DRX cycles) wherein N may be predefined/configured/indicated (e.g., via one or more of RRC, MAC CE and DCI). In another example, the time offset may be predefined/configured/indicated (e.g., via one or more of RRC, MAC CE and DCI) (e.g., in number of slots/frames/symbols, absolute time (e.g., time in milliseconds/seconds).

[0108] In an example, the WTRU may receive an indication (e.g., via one or more of DCI indication, MAC- CE indication, RRC signaling and SI), for example from the gNB). The WTRU may start monitoring for and receiving a LP-WUS and/or LP-SS from the beginning of subsequent DRX inactive time (e.g., latest DRX inactive time after the indication), or DRX active time (e.g., latest DRX active time after the indication) associated with first DRX configuration.

[0109] The WTRU may activate an aperiodic DRX active time. In an embodiment, the WTRU may receive an indication for activating an aperiodic DRX active time via a LP-WUS. The WTRU may start an aperiodic DRX active time, in which the WTRU may monitor for and receive a PDCCH transmission and/or transmit a scheduled CSI report. To start an aperiodic DRX active time, the WTRU may follow one or a combination of the following.

[0110] In an example, to start an aperiodic DRX active time, the WTRU may start an drx-onDurationTimer associated with the aperiodic DRX (e.g., according to the second DRX configuration). For example, the WTRU may start drx-onDurationTimer after ‘aperiodic DRX active time starting offset’ from the reception of LP-WUS which indicates to activate an aperiodic DRX active time.

[0111] In an example, to start an aperiodic DRX active time , the WTRU may determine an aperiodic DRX active time based on the second DRX configuration and DRX inactive time of the first DRX configuration. For example, the WTRU may first select DRX active times configured by the second DRX configuration and located within DRX inactive time of the first DRX configuration. Then the WTRU may use a DRX active time (e.g., first DRX active time after reception of a LP-WUS) out of the selected DRX active times of the second DRX configuration as the aperiodic DRX active time. The WTRU may start an drx-onDurationTimer associated with the selected aperiodic DRX active time and monitor for and receive a PDCCH transmission and/or transmits scheduled CSI reports. The WTRU may determine that DRX active times in the second DRX configuration are located in the first DRX inactive time if one or more of the following conditions are satisfied: if each second DRX active time is not overlapped with any of the first DRX active time; if overlap between each second DRX active time and each first DRX active time is greater than a threshold value; if overlap between each second DRX active time and all colliding first DRX active times with the second DRX active time are greater than a threshold value.

[0112] In an example, to start an aperiodic DRX active time, the WTRU may receive configuration of one or more aperiodic DRX active times and an association between LP-WUS monitoring occasions (MOs) (e.g., via one or more of RRC signaling, MAC-CE indication and SI). Based on the association between a MO of the LP-WUS, on which the WTRU received an indication for activating an aperiodic DRX active time, and the configured aperiodic DRX active times, the WTRU may select an aperiodic DRX active time. For example, the WTRU may receive a configuration of a first MO associated with a first aperiodic DRX active time and a second MO associated with a second aperiodic DRX active time. If the WTRU receives a LP-WUS in the first MO, the WTRU may select the first aperiodic DRX active time. If the WTRU receives a LP-WUS in the second MO, the WTRU may select the second aperiodic DRX active time. Based on the selection, the WTRU may start a drx- onDurationTimer associated with the selected aperiodic DRX active time and monitorfor and receive a PDCCH transmission and/or transmits scheduled CSI report(s).

[0113] The WTRU may skip a periodic DRX active time and early report CSI information. A WTRU may skip one or more configured periodic DRX active times after activation of an aperiodic DRX active time. The WTRU may early report CSI scheduled to be transmitted in skipped periodic DRX active times. To this end, the WTRU may use one or combination of the following.

[0114] In an embodiment, the WTRU may skip (e.g., may not start drx-onDurationTimer and/or may keep the MR in a sleep state) one or more periodic DRX active times after activating an aperiodic DRX active time based on one or more of the following.

[0115] The WTRU may skip (e.g., may not start drx-onDurationTimer and/or may keep the MR in a sleep state) one or more periodic DRX active times after activating an aperiodic DRX active time based on one or more ‘skip conditions for periodic DRX’. In an example, if the WTRU determines that one or more ‘skip conditions for periodic DRX’ are met, the WTRU may skip one or more configured subsequent (e.g., configured/scheduled immediately after the activated aperiodic DRX active time) periodic DRX active times. To this end, the WTRU may use one or a combination of the following ‘skip conditions for periodic DRX’: the start- to-startJimeGap (e.g., if start-to-startJimeGap is less than the 1st threshold on time gap, the WTRU may skip one or more configured subsequent periodic DRX active times; the end-to-startJimeGap (e.g., if end-to- startJimeGap is less than a 2nd threshold on time gap, the WTRU may skip one or more configured subsequent periodic DRX active times; the available battery power (e.g., if the available battery power is less than a configured threshold value, the WTRU may skip one or more configured subsequent periodic DRX active times). In an example, if the WTRU determines that one or more ‘skip conditions for periodic DRX’ are not met, the WTRU may begin a subsequent periodic DRX active time according to the configured schedule and may limit the active time. For example, if start-to-startJimeGap is greater than or equal to the 1st threshold on time gap and/or end-to-startJimeGap is greater than or equal to the 2nd threshold on time gap and/or available battery power is greater than or equal to the configured threshold value, the WTRU may begin the periodic DRX active time according to the configured schedule (e.g., WTRU starts drx-onDurationTimer and starts monitoring for and receive a PDCCH transmission, and/or transmits a CSI report). In addition, the WTRU may perform one or more of the following. The WTRU may limit the active time of one or more subsequent periodic DRX active times. For example, the WTRU may scale down drx-onDurationTimer and/or drx-lnactivityTimer by a factor (e.g., a preconfigured factor via RRC signaling, MAC-CE indication, SI) and/or the WTRU may start a DRX inactive time immediately after drx-onDurationTimer without waiting for drx-lnactivityTimer to end.

[0116] The WTRU may skip (e.g., may not start drx-onDurationTimer and/or may keep the MR in a sleep state) one or more periodic DRX active times after activating an aperiodic DRX active time based on a gNB indication/configuration. For example, the WTRU may receive an indication/config uration via a LP-WUS and/or via a DCI indication, or MAC-CE indication (e.g., within aperiodic DRX active time), to skip one or more configured subsequent periodic DRX active times. Based on the indication received, the WTRU may skip one or more configured periodic DRX active times (e.g., may not start drx-onDurationTimer and may keep the MR in a sleep state). If the WTRU does not receive an indication/configuration the WTRU may begin the subsequent periodic DRX active times according to the configured schedule (e.g., start drx-onDurationTimer and monitor for and receive a PDCCH transmission, and/or transmits CSI report(s)).

[0117] The WTRU may skip (e.g., may not start drx-onDurationTimer and/or may keep the MR in a sleep state) one or more periodic DRX active times after activating an aperiodic DRX active time based on absence of configured CSI reports associated with a subsequent configured periodic DRX active time. For example, the WTRU may skip the configured subsequent periodic DRX active time if a CSI report (e.g., periodic CSI report associated with periodic DRX active times) is not configured/scheduled within it. If a CSI report is configured within the subsequent periodic DRX active time, the WTRU may begin the subsequent periodic DRX active time according to the configured schedule (e.g., start drx-onDurationTimer and monitor for and receive a PDCCH transmission) and may send the configured CSI re-port to the gNB.

[0118] The WTRU may skip (e.g., may not start drx-onDurationTimer and/or may keep the MR in a sleep state) one or more periodic DRX active times after activating an aperiodic DRX active time based on potential overlapping of active time of aperiodic DRX active time and scheduled periodic DRX active time. For example, if the WTRU determines that drx-onDurationTimer or drx-lnactivityTimer of an aperiodic DRX active time overlaps with a scheduled subsequent periodic activity time, the WTRU may skip the subsequent scheduled periodic DRX active time.

[0119] In an embodiment, a WTRU may stop a started periodic DRX active time due to overlapping of the periodic DRX active time with an aperiodic DRX active time activated/indicated to activate (e.g., via LP-WUS). For example, the WTRU may receive an indication (e.g., via LP-WUS) to start a timer associated with an aperiodic DRX active time (e.g., drx-onDurationTimer) to activate an aperiodic DRX active time during a periodic DRX active time (e.g., PDCCH monitoring). In an example, a WTRU may determine an overlapping of an aperiodic DRX active time and a started periodic DRX active time. For example, a WTRU may receive an indication to start a timer associated with an aperiodic DRX active time (e.g., drx-onDurationTimer) to activate an aperiodic DRX active time while at least one timer associated with a periodic DRX timer is running (e.g., drx-onDurationTimer, drx-lnactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, ra- ContentionResolutionTimer, or msgB-ResponseWindow). For example, a WTRU may receive an indication to start a timer associated with an aperiodic DRX active time to activate an aperiodic DRX active time when a scheduling request is sent on a PUCCH and is pending (e.g., the WTRU transmitted a scheduling request but has yet to receive a DCI scheduling a PUSCH). For example, a WTRU may receive an indication to start a timer associated with an aperiodic DRX active time to activate an aperiodic DRX active time when receiving information via a PDCCH that indicates a new transmission (e.g., addressed to the cell - radio network temporary identifier (C-RNTI) of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contentionbased Random Access Preamble).

[0120] In an embodiment, a WTRU may determine to stop a running timer associated with a periodic DRX timer. For example, the WTRU may receive an indication to start a timer associated with an aperiodic DRX active time (e.g., drx-onDurationTimer) to activate an aperiodic DRX active time. If available battery power is less than a configured threshold value, the WTRU may stop (if running) any timer associated with a periodic DRX timer (e.g., drx-onDurationTimer, drx-lnactivityTimer, drx-RetransmissionTimerDL, drx- RetransmissionTimerUL, ra-ContentionResolutionTimer, or msgB-ResponseWindow) and start a timer associated with an aperiodic DRX active time.

[0121] In an embodiment, a WTRU may early report a CSI or part of CSI measurements scheduled to be reported in the skipped periodic DRX active times (e.g., CSI report scheduled to be transmitted in the first skipped periodic DRX active time). In an example, if a CSI report is scheduled to be sent within a skipped periodic DRX active time, the WTRU may early report the CSI (e.g., send the early CSI report within the aperiodic DRX active time). For example, the WTRU may early report the CSI based on one or more of the following. If the corresponding CSI report is ready (e.g., CSI measurements are performed before the start of an aperiodic DRX active time or within aperiodic DRX active time), the WTRU may send the CSI report to the gNB. If CSI measurements are performed before or during the aperiodic DRX active time, the WTRU may early report the CSI measurements performed. To send an early CSI report, the WTRU may determine UL resources based on one of the following. The WTRU may send the early CSI report via a ‘substituting CSI report resources’. For example, the WTRU may select the earliest resource located within the aperiodic DRX active time for the early CSI report. The WTRU may determine UL resources for an early CSI report based on the selected DRX active time for aperiodic DRX active time from the second DRX configuration. For example, the WTRU may transmit an early CSI report via UL resources configured in the selected DRX active time from the second DRX configuration. [0122] In an embodiment, a WTRU that skips one or more periodic DRX active times after activating an aperiodic DRX active time may indicate to the gNB its decision on skipping the subsequent scheduled periodic DRX active time and the reasons. In an example, the WTRU may indicate to the gNB its decision on skipping the subsequent periodic DRX active time and reasons along with an early CSI report in an aperiodic DRX active time or via preconfigured PUCCH within the aperiodic DRX active time. In an example, the WTRU may report that ‘skip conditions for periodic DRX’ met and/or report additional information (e.g., battery status, buffer status report, etc.).

[0123] In an embodiment, a WTRU may determine to monitor a LP-WUS or both a LP-WUS and a DCI with a cyclic redundancy check (CRC) scrambled by a power saving RNTI (PS-RNTI) DCI with CRC scrambled by PS-RNTI (DCP) for activating a DRX active time. The terms LP signal and LP-WUS may be used interchangeably.

[0124] A WTRU may determine a wake-up signaling option.

[0125] In an embodiment, a WTRU may determine a mode of operation for wake-up signal reception between a first mode (e.g., receiving LP-WUS only) and a second mode (e.g., receiving both LP-WUS and DCP, or monitoring DCP only). The determination of the mode of operation may be based on one or more of the following:

[0126] The determination of the mode of operation may be based on a signal quality/coverage. In an embodiment, the WTRU may determine a mode of operation (e.g., between the first mode and the second mode) based on signal quality/coverage. For example, If a LP-WUS/LP-SS signal quality is greater than a threshold value on a LP-WUS/LP-SS signal quality, the WTRU may determine the first mode of operation (e.g., monitoring/receiving only LP-WUS). If a LP-WUS/LP-SS signal quality is less than a threshold value on a LP- WUS/LP-SS signal quality, the WTRU may determine the second mode of operation (e.g., monitoring/receiving both LP-WUS and DCP, or monitoring DCP only). The threshold and/or the LP-WUS/LP-SS for signal measurement may be configured/activated/indicated via one or more of RRC, MAC CE and DCI.

[0127] The determination of the mode of operation may be based on mobility. In an embodiment, the WTRU may determine a mode of operation (e.g., between the first mode and the second) mode) based on WTRU mobility. For example, if mobility is less than a threshold value on LP-mobility, the WTRU may determine the first mode of operation (e.g., monitoring/receiving only LP-WUS). If mobility is greater than a threshold value on LP-WUS/LP-SS signal quality, the WTRU may determine the second mode of operation (e.g., monitoring/receiving both LP-WUS and DCP, or monitoring DCP only). The WTRU may determine mobility based on a change of signal quality. In an example, the WTRU may measure the serving cell quality (e.g. reference signal received power (RSRP)). If the difference between a current RSRP measurement and a reference RSRP is greater than a threshold value, the WTRU may determine a higher mobility state condition has been met and change the mode of operation, from a first mode (e.g., monitoring/receiving only LP-WUS) to a second mode (e.g., monitoring/receiving both LP-WUS and DCP, or monitoring DCP only). Alternatively, if the difference between a current RSRP measurement and a reference RSRP is less than a threshold value, the WTRU may determine that a relaxed monitoring condition has been met and change the mode of operation, from a second mode (e.g., monitoring/receiving both LP-WUS and DCP, or monitoring DCP only) to a first mode (e.g., monitoring/receiving only LP-WUS). The “relaxed monitoring” mode may indicate an opportunity for the WTRU to save power by monitoring a LP-WUS only. The reference RSRP may be initialized/updated to be set to the current RSRP measurement value based on one or more of the following conditions occurring: at the end of RRC reconfiguration procedure; upon selecting or reselecting a new cell; after configuring/enabling, or disabling, LP-WUS monitoring; after the mode of operation changes from a first mode (e.g., monitoring/receiving only LP-WUS) to a second mode (e.g., monitoring/receiving both LP-WUS and DCP, or monitoring DCP only), or vice-versa; after MAC successfully completes a random access procedure after applying a reconfigurationWithSync; and if the conditions for determining “higher mobility state” have not been met within a certain time duration. The WTRU mobility may be one or more of WTRU speed, WTRU direction change, number of handovers, and/or zone ID change. The threshold and/or the LP-WUS/LP-SS for measurement of WTRU mobility may be configured/activated/indicated via one or more of RRC, MAC CE and DCI.

[0128] The determination of the mode of operation may be based on a success/failure of receiving a LP- WUS. In an embodiment, the WTRU may determine a mode of operation (e.g., between the first mode and the second mode) based on a success/failure of receiving a LP-WUS. For example, if a detection rate of a LP- WUS is less than a threshold value on a detection rate, the WTRU may determine the first mode of operation (e.g., monitoring/receiving only LP-WUS). If a detection rate of a LP-WUS is greater than a threshold value on a detection rate, the WTRU may determine the second mode of operation (e.g., monitoring/receiving both LP- WUS and DCP, or monitoring DCP only). The threshold and/or the LP-WUS/LP-SS for measurement of WTRU mobility may be configured/activated/indicated via one or more of RRC, MAC CE and DCI. If the WTRU uses a LP-SS, the detection rate may be a hypothetical LP-WUS block error rate (BLER).

[0129] A WTRU may determine to wake up for a ‘DRX active’ time based on wake-up signaling options selected.

[0130] For DRX operations, a WTRU may be configured to monitor for a specific DCI (e.g. DCI with CRC scrambled by PS-RNTI (DCP), or DCI 2_6) in some PDCCH occasions to receive Wake-Up Signals (WUS). The DCP indicates to the WTRU whether to wake-up or sleep through the next DRX active time of the DRX cycle. The DCP is sent ahead of an active time of a long DRX cycle and includes an indication for one or more WTRUs to wake up on one or more cells, based on a received power saving DCP configuration. The DCP includes a wake-up indication of a single bit where: a first value (e.g, 'O' value), when reported to higher layers, indicates to not start the drx-onDurationTimer for the next long DRX cycle while a second value (e.g., 'T value) indicates to start the drx-onDurationTimerforVne next long DRX cycle. Sleeping through a periodic ‘DRX active’ time allows the WTRU to save energy by reducing the use of the radio to monitor for PDCCH when none are planned by the network.

[0131] In an example, the WTRU may determine or be configured to monitor for a LP-WUS and/or DCP to determine whether to wake up the MR and monitor the next ‘DRX active’ time of the DRX cycle. In an example, the WTRU may monitor a LP-WUS for a given DRX cycle, and DCP for another cycle. The WTRU may have determined or be configured with patterns indicating which signaling option to use for the next DRX cyde(s).

[0132] In an embodiment, the WTRU may indicate to the network the selected signaling option for the upcoming DRX cyde(s). The WTRU may use some UL indication, such as RRC configuration, MAC or uplink control information (UCI) indications to indicate a signaling option, or a pattern of signaling options. In an example, the WTRU may transmit this indication in one of the active DRX times of a DRX cycle.

[0133] A WTRU may determine to wake up for a ‘DRX active’ time based on a LP-WUS.

[0134] In an embodiment, a WTRU may have determined to use a “LP-WUS only” signaling approach (first mode wake-up signal reception), and the WTRU may determine to wake up its main radio for a ‘DRX active’ time based on the reception of LP signals.

[0135] In an example, the WTRU may be configured with an identification indication such as a WTRU ID, a group ID, or a LP-WUS ID, that may be specific to a LP-WUS. The WTRU may receive this identification configuration from the network through RRC signaling (e.g., as part of a RRC LP-WUS configuration), MAC indication or DCI signaling. In an example, the identification may be configured as a bit index of a bitmap with a given/configured size, where the bits of the bitmap correspond to different IDs.

[0136] In an example, the WTRU may receive a configuration for determining a group ID. For example, the WTRU may receive a WTRU ID. The WTRU may receive (e.g., via RRC signaling, SI, MAC-CE indication) a grouping configuration (e.g., number of groups per LP-WUS). The WTRU may determine a group ID based on the received WTRU ID and the grouping configuration (e.g., group ID = (WTRU ID mod ‘number of subgroups per LP-WUS’)).

[0137] The WTRU may monitor and receive a LP signal that includes the received/determined identification (e.g., WTRU ID, group ID, etc.). In an example, the WTRU may receive a LP-WUS including a bitmap of WTRU IDs or group ID. Upon decoding the bitmap, the WTRU may determine to wake up the main radio for the ‘DRX active’ time based on if the bit of the WTRU ID or group ID corresponds to an activated bit of the bitmap. The WTRU may determine not to wake up the main radio and skip the following ‘DRX active’ time based on if the bit of the WTRU ID or group ID corresponds to an inactivated bit of the bitmap. In an example, the LP-WUS may indicate explicitly one (or multiple) WTRU ID or group IDs or group ID, and the WTRU may determine to wake up or skip the following ‘DRX active’ time based on the WTRU ID or group ID is included in the LP-WUS indication. In an example, the WTRU may be configured to skip the following ‘DRX active’ time when included in the LP-WUS indication. The advantage of the skipping indication is to have a more reliable indication, and if the case where the WTRU misses or does not decode correctly the LP-WUS, it will by default monitor the ‘DRX active’ time. In another example, the WTRU may be configured to wake up and monitor the following ‘DRX active’ time when included in the LP-WUS indication. The advantage of an active wake-up indication is to reduce the overhead and signaling, and only transmitting the indication when the WTRU shall wake-up.

[0138] In an example, the WTRU may be configured to monitor and detect the presence of LP-WUS signals (e.g., in specific monitoring time and frequency occasions). The WTRU may receive the monitoring resource configuration from the network through RRC signaling (e.g., as part of a RRC LP-WUS configuration), MAC indication or DCI signaling. The presence of the LP signal may implicitly indicate the action for the WTRU. The WTRU may be configured to assume the presence of the LP signal when the LP signal is higher than a configured threshold value (e.g., based on measurement on the LP-WUS signal (e.g., LP-RSRP or LP-received signal strength indicator (RSSI) or LP-signal to interference plus noise ratio (SINR)). The WTRU may be configured to assume the presence of the LP signal when the LP signal may be or is correctly decoded. For example, the WTRU may be configured to wake up the main radio and monitor the following ‘DRX active’ time based on the detection of the presence of a LP signal in a configured time and frequency resource. For example, the WTRU may be configured to skip the following ‘DRX active’ time based on the detection of the presence of a LP signal in a configured time and frequency resource. Different WTRUs may be configured with different LP-WUS monitoring occasions so that the network may transmit the indication to one or more WTRUs at the same time and/or group WTRUs.

[0139] In an example, the WTRU may be (pre)configured with low power (LP) sequences that may be WTRU specific (e.g., based on the WTRU ID) or group specific (e.g., based on a group ID). The sequence may be, for example, an overlaid OFDM sequence. The WTRU may also be configured with time and frequency resource(s) where the sequence may be received. The WTRU may receive the sequence or be preconfigured with the sequence or receive the configuration from the network through RRC signaling (e.g., as part of a RRC LP-WUS configuration), MAC indication or DCI signaling. The WTRU may monitor for the sequence according to a received configuration and take actions when the sequence is received. For example, the WTRU may be configured to wake up the main radio and monitor the following ‘DRX active’ time based on the reception of the sequence that corresponds to the configured sequence (e.g., in the configured time and frequency resource). For example, the WTRU may be configured to not wake up the main radio and skip the following ‘DRX active’ time based on the reception of the sequence that corresponds to the configured sequence (e.g., in the configured time and frequency resource). For example, the WTRU may be configured to wake up the main radio and monitor the following ‘DRX active’ time based on the reception of the sequence that does not corresponds to the configured sequence (e.g., in the configured time and frequency resource). For example, the WTRU may be configured to not wake up the main radio and skip the following ‘DRX active’ time based on the reception of the sequence that does not corresponds to the configured sequence.

[0140] In an example (e.g., as a fallback mechanism), the WTRU may determine to wake up the main radio and monitor the following ‘DRX active’ time based on if the WTRU fails to decode a received LP-WUS, if a configured LP-WUS is not received/detected, or if the LP signal is received with a low signal strength (e.g., a LP-RSRP, LP-SINR or LP-RSSI of the received signal is below a configured threshold value).

[0141] In an example, the WTRU may be configured to receive a LP-WUS that includes a tag such as an (ordered) numbering sequence, and when receiving a LP-WUS, the WTRU may detect whether it missed a previous LP-WUS, for example, based on receiving consecutive LP-WUS whose tags are not consecutive in the configured numbering sequence. This may help the WTRU to know if it missed one or more WUSs.

[0142] When the WTRU determines to skip the ‘DRX active’ time monitoring, it does not wake up the main radio for the upcoming ‘DRX active’ time. The WTRU may further be configured (e.g., by the network through RRC, MAC or DCI configuration) to skip a configured number of ‘DRX active’ times. The WTRU may receive a number in the LP-WUS indicating how many ‘DRX active’ times to skip, or alternatively, a time indication for how long to skip ‘DRX active’ times.

[0143] When the WTRU determines to wake up and monitor a ‘DRX active’ time based on the reception of the LP-WUS, the WTRU may trigger or start the drx-onDurationTimer timer. The trigger timing may be delayed based on a received (pre)configuration. For example, the WTRU may be configured to monitor ‘DRX active’ starting at specific timing occasion, such as the beginning of a slot on specific slots. The WTRU may be (pre)configured with a fixed delay between the reception of the LP-WUS and the trigger of the drx- onDurationTimer (e.g., as a processing delay or a delay required by hardware to wake up the main radio). In this case, the WTRU may prepare and wake up the main radio to start monitoring for PDCCH during the DRX active time when the timer is triggered.

[0144] When the WTRU determines to wake up and monitor a ‘DRX active’ time based on the reception of the LP-WUS, the WTRU may prepare and wake up the main radio for the upcoming ‘DRX active’ time (e.g., based on the periodic DRX cycle timing, monitor for PDCCH and trigger drx-onDurationTimertor the next DRX cycle).

[0145] A WTRU may determine to wake up for a DCP occasion based on a LP-WUS. In an embodiment, the WTRU may have determined to use the signaling option where both a LP-WUS and DCP monitoring are used (e.g., first mode wake-up signal reception) to determine whether to wake up its main radio for a ‘DRX active’ time or skip it. In this embodiment, the WTRU may first be configured to monitor for a LP-WUS. The WTRU may then determine to monitor (or skip) for a DCP occasion (e.g., monitoring PDCCH occasions for DCI including a sleep/wakeup indication, e.g., DCI 2_6) based on the reception of a LP-WUS. When monitoring and receiving a DCP after a LP-WUS, the WTRU may then determine to monitor (or skip) the ‘DRX active’ time based on the reception of the DCP content.

[0146] Similar with the “LP-WUS only” signaling approach, the WTRU may be configured for LP-WUS monitoring including the time and frequency occasions where the WTRU may receive the LP-WUS. Different WTRUs may be configured with different LP-WUS monitoring occasions so that the network may transmit the indication to one or more WTRUs at the same time and/or group WTRUs. The WTRU may also be configured with an identification configuration, presence configuration or sequence configuration allowing the WTRU to identify, detect or recognize the LP-WUS presence and/or content.

[0147] The WTRU may then determine to monitor (or skip) for DCP based on one or more of the following. [0148] In an example, the WTRU may receive a LP-WUS including a bitmap of WTRU IDs or a group ID.

Upon decoding the bitmap, the WTRU may determine to wake up the main radio and monitor the upcoming DCP occasion based on if the bit of the WTRU ID or the group ID corresponds to an activated bit of the bitmap. The WTRU may determine not to wake up the main radio and skip the following DCP occasion based on if the bit of the WTRU ID or group ID corresponds to an inactivated bit of the bitmap.

[0149] In an example, the LP-WUS may indicate explicitly one (or multiple) WTRU or group IDs, or group ID, and the WTRU may determine to wake up or skip the following DCP occasion based on the WTRU ID, or group ID included in the LP-WUS indication. In an example, the WTRU may be configured to skip the following DCP occasion when included in the LP-WUS indication. The advantage of the skipping indication is to have a more reliable indication, and if the case where the WTRU misses or does not decode correctly the LP-WUS, it may by default monitor a DCP occasion. In an example, the WTRU may be configured to wake up and monitor the following DCP occasion when included in the LP-WUS indication. The advantage of an active wake-up indication is to reduce the overhead and signaling, and only transmitting the indication when the WTRU shall wake-up.

[0150] In an example, the WTRU may be configured to wake up the main radio and monitor the following DCP occasion based on the detection of the presence of a LP signal in a configured time and frequency resource.

[0151] In an example, the WTRU may be configured to skip the following DCP occasion based on the detection of the presence of a LP signal in a configured time and frequency resource.

[0152] In an example, the WTRU may be configured to wake up the main radio and monitor the following DCP occasion based on the reception of the sequence that corresponds to the configured sequence (e.g., in the configured time and frequency resource).

[0153] In an example, the WTRU may be configured to not wake up the main radio and skip the following DCP occasion based on the reception of the sequence that corresponds to the configured sequence (e.g., in the configured time and frequency resource).

[0154] In an example, the WTRU may be configured to wake up the main radio and monitor the following DCP occasion based on the reception of the sequence that does not corresponds to the configured sequence (e.g., in the configured time and frequency resource).

[0155] In an example, the WTRU may be configured to not wake up the main radio and skip the following DCP occasion based on the reception of the sequence that does not corresponds to the configured sequence. [0156] In an example, as a fallback mechanism, the WTRU may determine to wake up the main radio and monitor the following DCP occasion based on if the WTRU fails to decode a received LP-WUS, if a configured LP-WUS is not received/detected, or if the LP signal is received with a low reliability, for example based on a signal strength below a configured threshold value (e.g., a LP-RSRP, LP-SINR or LP-RSSI of the received signal or of the LP-SS).

[0157] In an example, the WTRU may be configured with different WTRU IDs, group IDs, or other identification information for the LP-WUS and for the DCP. For example, the WTRU may be configured with a group ID for a LP-WUS so that only a group of WTRU wakes up for DCP monitoring, and the WTRU may be configured with a WTRU ID for the DCP content, among the number of WTRUs in the LP-WUS group. The network may use the different IDs and a grouping mechanism to narrow down the number of WTRU s to wake up at each step, creating groups and subgroups.

[0158] When the WTRU determines to skip the DCP monitoring, it does not wake up the main radio for the upcoming DCP occasion. The WTRU may further be configured (e.g., by network through RRC, MAC or DCI configuration) to skip a configured number of DCP occasions. The WTRU may receive a number in the LP- WUS indicating how many DCP occasions to skip (or alternatively, a time indication for how long to skip DCP occasions).

[0159] When the WTRU determines to wake up and monitor PDDCH occasions for DCP (e.g., DCI format 2_6) time based on the reception of the LP-WUS, the WTRU may monitor the next scheduled DCP occasion (e.g., based on the received DRX configuration and DCP configuration). The WTRU may trigger an aperiodic DCP occasion (e.g., where the WTRU wakes up and monitor for DCP in a time window based on the received LP-WUS indication). The time window start may be delayed based on a received (pre)configuration. For example, the WTRU may be configured to monitor DCP occasions starting at specific timing occasion, such as the beginning of a slot or specific slots. The WTRU may be (pre)configured with a fixed delay between the reception of the LP-WUS and the beginning of the DCP monitoring (e.g., as a processing delay or a delay required by hardware to wake up the main radio). In this case, the WTRU may prepare and wake up the main radio to start monitoring for PDCCH during the DCP occasion.

[0160] Upon monitoring and receiving a DCP, the WTRU may determine to wake up or skip the following ‘DRX active’ time based on the indication received in the DCP. If the wake-up indication field (e.g. from the DCI 2_6 format) corresponding to the WTRU is particular value (e.g. ‘T), the WTRU may trigger drx- onDurationTimer for the next DRX cycle. If the wake-up indication field (e.g. from the DCI 2_6 format) corresponding to the WTRU is a different value (e.g. ‘0’), the WTRU may not trigger drx-onDurationTimer for the next DRX cycle.

[0161] In an embodiment, the WTRU may be configured and receive a LP-WUS indicating that the WTRU should wake up or skip the upcoming ‘DRX active’ time even when configured/determined to monitor LP-WUS triggering DCP monitoring. In an example, the WTRU may be configured to receive a LP-WUS with an indication including whether the LP-WUS triggers the monitoring of the following DCP or of the following ‘DRX active’ time. This indication may be a binary flag in the LP-WUS content, or the WTRU may be configured with different time/frequency LP-WUS resources for the DCP or DRX active monitoring or may be configured as a different sequence. Upon reception of the LP-WUS, the WTRU may determine whether to skip the DCP occasion and monitor ‘DRX active’ time, monitor DCP occasion or skip both DCP occasion and DRX active time.

[0162] A WTRU may determine to wake up for a ‘DRX active’ time based on both a LP-WUS and a DCP. In an embodiment, the WTRU may have determined to use both a LP-WUS and a DCP monitoring as a redundancy case, and the WTRU may determine to wake up its main radio for a ‘DRX active’ time based on the reception of both LP signals and DCP.

[0163] For example, the WTRU may be configured with LP-WUS monitoring to wake up the ‘DRX active’ time similarly as described in the “LP-WUS only” signaling approach. The WTRU may also be configured to monitor for DCP (monitor PDCCH for DCI indicating to wake up or sleep in the next ‘DRX active’ time, for example, DCI 2_6). The WTRU may perform the monitoring of both signals in parallel based on their respective configurations. The WTRU may first determine whether to monitor or skip the following ‘DRX active’ time based on the reception of both signaling separately (e.g., similarly as in “LP-WUS only” signaling approach and as in the regular DCP behavior).

[0164] The WTRU may determine to monitor or skip the ‘DRX active’ time based on both LP-WUS-based and DCP-based determinations.

[0165] The WTRU may determine to monitor the following ‘DRX active’ time based on: the WTRU determined that both LP-WUS and DCP signaling indicated to monitor the following ‘DRX active’ time; neither LP-WUS nor DCP was successfully received and decoded; the WTRU determined that the DCP indicated to monitor the following ‘DRX active’ time while the LP-WUS indicated not to monitor, or that the LP-WUS was not received or not successful decoded (e.g., when the DCP was received after the LP-WUS (e.g., indicating that the network has new data for the WTRU after the LP-WUS indication)); and/or the WTRU determined that the LP-WUS indicated to monitor the following ‘DRX active’ time while the DCP indicated not to monitor, or that the DCP was not received or not successful decoded (e.g., when the LP-WUS was received after the DCP (e.g., indicating that the network has new data for the WTRU after the LP-WUS indication)).

[0166] The WTRU may determine to skip the following ‘DRX active’ time based on: the WTRU determined that both LP-WUS and DCP signaling indicated to skip the following ‘DRX active’ time; the WTRU determined that the DCP indicated to skip the following ‘DRX active’ time while the LP-WUS indicated to monitor it, or that the LP-WUS was not received or not successful decoded (e.g., if the LP-WUS was received before the DCP, for example indicating that the network changed its scheduling or if the LP-WUS was received with a low signal quality, for example LP-RSRP<Threshold, and that the LP-WUS information may be not reliable, for example, in the case of sequence-based detection or presence detection when no decoding is needed); and/or the WTRU determined that the LP-WUS indicated to skip the following ‘DRX active’ time and that the DCP was not received or not successful decoded.

[0167] When the WTRU determined or is configured to monitor both LP-WUS and DCP, the WTRU may determine to skip the monitoring of one or more DCP occasion(s) based on a successful reception of a LP- WUS. The WTRU may determine a successful reception of the LP-WUS based on a signal quality of the received LP-WUS (e.g., RSRP/RSSI/SINR higher than a configured threshold value) and/or or a successful decoding of the information. The WTRU may determine to skip the monitoring of a DCP targeting a ‘DRX active’ time of a DRX cycle, based on a successful reception of a LP-WUS indicating to monitorthe same ‘DRX active’ time of the DRX cycle. The WTRU may determine to skip the monitoring of a DCP targeting a ‘DRX active’ time of a DRX cycle, based on a successful reception of a LP-WUS indicating to skip the same ‘DRX active’ time of the DRX cycle.

[0168] When the WTRU determined or is configured to monitor both LP-WUS and DCP, the WTRU may determine to skip the monitoring of one or more LP-WUS occasion(s) based on a successful reception of a DCP. The WTRU may determine a successful reception of the DCP based on a successful decoding of the information. The WTRU may determine to skip the monitoring of a LP-WUS targeting a ‘DRX active’ time of a DRX cycle, based on a successful reception of a DCP indicating to monitor the same ‘DRX active’ time of the DRX cycle. The WTRU may determine to skip the monitoring of a LP-WUS targeting a ‘DRX active’ time of a DRX cycle, based on a successful reception of a DCP indicating to skip the same ‘DRX active’ time of the DRX cycle.

[0169] When the WTRU determines to wake up and monitor a ‘DRX active’ time based on the reception of the LP-WUS and/or DCP, the WTRU may prepare and wake up the main radio for the upcoming ‘DRX active’ time (e.g., based on the periodic DRX cycle timing, monitors for PDCCH, and triggers drx-onDurationTimerfor the next DRX cycle).

[0170] A LP-WUS may be used with DRX.

[0171] DRX active time may be extended based on PDCCH reception and LP-WUS indication.

[0172] A WTRU may be configured to use a LP-WUS with DRX operations, where the WTRU may receive one or more indications and/or configuration information on a LP-WUS application along with DRX operation. In an example, the received configuration may include a first, a second, and a third threshold values on the quality of the detected, received, and/or measured LP-WUS and/or LP-SS. For example, the signal quality thresholds may be regarding the RSRP, total received power, hypothetical BLER of LP-WUS and/or LP-SS.

[0173] In an example, the WTRU may be configured, indicated, and/or determine to monitor a LP-WUS or a DCP within a DRX inactive time based on one or more measured signal quality parameters. In an example, if one or more of the measured signal quality parameters of the detected and/or received LP-WUS and/or LP- SS are greater than a corresponding configured first threshold value, the WTRU may monitor a LP-WUS within DRX inactive time. Otherwise, if one or more of the measured signal quality parameters of the detected and/or received LP-WUS and/or LP-SS are less than the corresponding configured first threshold value, the WTRU may monitor DCP within the DRX inactive time.

[0174] In case the WTRU receives an indication, for example via received and/or detected LP-WUS and/or DCP, the WTRU may trigger a DRX active time. In an example, the WTRU may trigger drx-onDurationTimer. As such, the WTRU may monitor for receiving and/or detecting PDCCH during the DRX active time and/or transmit scheduled CSI reports to the gNB.

[0175] In an embodiment, a WTRU that is in a DRX active time and is monitoring for receiving and/or detecting PDCCH, may monitor to detect and/or receive one or more LP-WUS, based on one or more conditions. In an example, the WTRU may monitor to detect and/or receive one or more LP-WUS during a DRX active time based on one or more measured LP-SS and/or LP-WUS quality parameters. In an example, if one or more of the measured signal quality parameters of the detected and/or received LP-WUS and/or LP-SS are greater than a corresponding configured second threshold value, the WTRU may monitor LP-WUS during the DRX active time. In this case, for example the WTRU may monitor to detect and/or receive a LP-WUS via the LR, while the WTRU may be monitoring for detecting and/or receiving PDCCH via the MR in DRX active time, for example while one or more timers (e.g., drx-onDurationTimer and/or drx-lnactivityTimer) are running.

[0176] In an embodiment, the WTRU that has monitored for both PDCCH and LP-WUS during a DRX active time and has detected and/or received either of them may extend or re-initiate one or more timers. For example, the WTRU may extend DRX active time (e.g., by restarting drx-lnactivityTimer). During the extended DRX active time, the WTRU may monitor for and receive a PDCCH transmission.

[0177] DRX UL retransmission timers may be triggered based on LP-WUS reception.

[0178] In an embodiment, a WTRU may determine to trigger one or more timers based on detection of a LP-WUS during a DRX active time in addition to one or more measured LP-WUS and/or LP-SS quality parameters. For example, the WTRU may determine to trigger an UL retransmission timer (e.g., drx- RetransmissionTimerUL) based on one or more measured LP-SS and/or LP-WUS quality parameters. In an example, if one or more of the measured signal quality parameters of the detected and/or received LP-WUS and/or LP-SS are greater than a corresponding configured third threshold value, the WTRU may monitor for detecting one or more configured LP-WUS after transmission of one or more scheduled UL signals and/or channels (e.g., during drx-HARQ-RTT-TimerUL). That is, upon reception of a configured LP-WUS, the WTRU may trigger an UL retransmission timerfor UL re-transmission scheduling. Otherwise, in case a LP-WUS is not received within a DRX active time, the WTRU may not trigger an UL retransmission timer.

[0179] In an example, if one or more of the measured signal quality parameters of the detected and/or received LP-WUS and/or LP-SS are less than a corresponding configured third threshold value, the WTRU may use the configurations based on a non-LP-WUS operation (e.g., legacy configurations) for triggering and/or extending and/or resetting one or more UL retransmission timers. [0180] In an embodiment for supporting power efficient aperiodic DRX active time, a WTRU may activate an aperiodic DRX active time prior to a scheduled periodic DRX active time based on an indication received via a LP-WUS. The WTRU may skip the periodic DRX active time and skip or early transmit CSI reporting configured to be transmitted during skipped periodic DRX active time.

[0181] FIG. 6 shows an example method for power efficient aperiodic DRX active time.

[0182] A WTRU may receive one or more configuration information or indications 610. The WTRU may receive one or more thresholds or threshold values (which may be referred to as ‘skip conditions for periodic DRX’) for skipping a periodic DRX active time after activation of an aperiodic DRX active time. The configuration information or indication may comprise a first threshold or threshold value (e.g., first threshold on a time gap) on a time difference (i.e., start-to-startJimeGap) between the beginning of an aperiodic DRX active time and beginning of a subsequent periodic DRX active time (e.g., time difference between starting points of drx- onDurationTimers associated with aperiodic DRX active time and subsequent periodic DRX active time). The configuration information or indication may comprise a second threshold or threshold value (i.e., second threshold on time gap) on a time difference (i.e. end-to-start_time_gap) between an end of an aperiodic DRX active time (e.g., end of associated drx-lnactivityTimer) and start of a subsequent periodic DRX active time (e.g., start of associated drx-onDurationTimer). The configuration information or indication may comprise a threshold or threshold value regarding available battery power.

[0183] The WTRU may receive a UL grant information (e.g. a set of grants) or UL resources (which may be referred to as ‘substituting CSI reporting resources’) in a periodic DRX inactive time to substitute for UL grants or scheduled UL resources for CSI reporting in each periodic DRX active time.

[0184] The WTRU may receive a configuration for LP-WUS monitoring (e.g., LP-WUS periodicity, timefrequency re-sources, etc.), DRX configuration, offset between LP-WUS and aperiodic DRX active time, and indication/configuration for monitoring LP-WUS.

[0185] The WTRU may receive an indication for activating an aperiodic DRX active time via a LP-WUS 620.

[0186] The WTRU may activate an aperiodic DRX active time (e.g., start a drx-onDurationTimer associated with an aperiodic DRX active time and monitor for a PDCCH) at the configured time offset from the LP-WUS reception 630.

[0187] The WTRU may receive a PDCCH transmission during the aperiodic DRX active time and/or may transmit a PUSCH or PUCCH transmission based on scheduling received via the PDCCH or configured scheduling and/or may receive a PDSCH transmission 640.

[0188] The WTRU may skip a subsequent periodic DRX active time based on the received configuration information or indications (i.e. ‘skip conditions for periodic DRX’) 650. For example, if start-to-startJimeGap is less than the first threshold value on time gap and/or end-to-startJimeGap is less than the second threshold value on time gap and/or available battery power is less than the configured threshold value regarding available battery power, the WTRU may skip a subsequent periodic DRX active time (e.g., WTRU does not start associated timers, for example, drx-onDurationTimer, and keeps the main radio (MR) in a sleep state) and performs one or more of the following: (i) if a CSI report is scheduled to be sent within the skipped DRX active time, the WTRU may early report the CSI using a ‘substituting CSI reporting resources’ (e.g., the earliest resource located within the aperiodic DRX active time). For example, the WTRU may early report CSI based on the corresponding CSI report is ready and/or CSI measurements are performed before or during the aperiodic DRX active time; (ii) the WTRU may indicate (e.g., along with an early CSI report in an aperiodic DRX active time/ preconfigured PUCCH within the aperiodic DRX active time) to the gNB its decision on skipping a subsequent periodic DRX active time and a reason (e.g., ‘skip conditions for periodic DRX’ met) and/or report additional information (e.g., battery status or buffer status report); (iii) the WTRU may monitor a LP-WUS during a skipped periodic DRX active time. If a start-to-startJimeGap is greater than or equal to the first threshold value on time gap and/or the end-to-startJimeGap is greater than or equal to the second threshold on time gap and/or available battery power is greater than or equal to the configured threshold value regarding available battery power, the WTRU may begin the periodic DRX active time according to the configured schedule and may limit the active time (e.g., may scale down drx-onDurationTimer by a pre-configured factor). The WTRU may monitor for and receive a PDCCH transmission during a periodic DRX active time.

[0189] FIG. 7 shows example method 700 for power efficient DRX active time. A WTRU may receive configuration information 710. The configuration information may comprise at least one threshold value for skipping a second discontinuous reception (DRX) active time period after activation of a first DRX active time period. The WTRU may receive an indication for activating the first DRX active time period 720. The indication may be received via a LP-WUS. The WTRU may start a timer for PDCCH monitoring, for example DRX on duration timer (e.g., drx-onDurationTimer), associated with the first DRX active time period after a time offset from reception of the LP-WUS 730. The WTRU may monitor for and receive a physical downlink control channel (PDCCH) transmission in resources while the DRX on duration timer associated with the first DRX active time period is running 740. The WTRU may receive a physical downlink shared channel (PDSCH) transmission or transmit a physical uplink shared channel (PUSCH) transmission ora physical uplink control channel (PUCCH) transmission based on the received PDCCH transmission 750. The WTRU may determine to skip the second DRX active time period based on the at least one threshold value 760. The WTRU may report channel state information (CSI), for a CSI report scheduled to be reported in the second DRX active time, in substitute (e.g., alternate / different) CSI reporting uplink resources in the first DRX active time period 770.

[0190] The WTRU may skip the second DRX active time period based on the at least one threshold value, based on the determining to skip. The skipping the second DRX active time period may comprise the main radio (MR) continuing in a sleep state and not starting a timer for PDCCH monitoring, for example a DRX on duration timer, associated with the second DRX active time period. The at least one threshold value may comprise: an end-to-start time gap threshold value associated with a time difference between an end of the first DRX active time period and a start of the second DRX active time period, wherein the end of the first DRX active time period is based on an end of a timer associated with the first DRX active time period, and wherein the start of the second DRX active time period is based on start of a DRX on duration timer associated with the second DRX active time period. The WTRU may determine to skip the second DRX active time period based on the end of the first DRX active time period and the start of the second DRX active period time being less than the end-to-start time gap threshold value. The at least one threshold value may comprise an available battery power threshold value. The WTRU may determine to skip the second DRX active time period based on an available battery power being less than the available battery power threshold value. The WTRU may monitor for and receive LP-WUSs using a low power radio (LR) during a skipped second DRX active time period. The configuration information may comprise uplink grant information indicating substitute CSI reporting uplink resources during the first DRX active time period. The reporting CSI in substitute CSI reporting uplink resources may be based on a CSI report being ready and CSI measurements being performed before or during the first DRX active time period.

[0191] In an embodiment, a method for power efficient aperiodic DRX active time may be used by a wireless transmit/receive unit (WTRU). The method may comprise receiving configuration information. The configuration information may comprise at least one threshold value regarding skip conditions associated with a periodic discontinuous reception (DRX). The method may comprise receiving an indication for activating an aperiodic DRX active time via a low power- wake up signal (LP-WUS). The method may comprise activating an aperiodic DRX active time at a time offset from the LP-WUS. The method may comprise receiving a physical downlink control channel (PDCCH) transmission during the aperiodic DRX active time. The method may comprise skipping a subsequent periodic DRX active time based on the received configuration information. The configuration information may comprise a first threshold value on a time difference between a beginning of an aperiodic DRX active time and a beginning of a subsequent periodic DRX active time. The configuration information may comprise a second threshold value on a time difference between an end of an aperiodic DRX active time and a start of a subsequent periodic DRX active time. The configuration information may comprise a threshold value regarding available battery power. The method may comprise receiving uplink grant information indicating uplink resources in a periodic DRX inactive time to substitute for an uplink grant or scheduled uplink resources for channel state information (CSI) reporting in each periodic DRX active time. The method may comprise receiving a configuration for low power - wake up signal (LP-WUS) monitoring, a DRX configuration, an offset between a LP-WUS and an aperiodic DRX active time, and configuration information for monitoring the LP-WUS. The method may comprise skipping a subsequent periodic DRX active time on a condition that the time difference between a beginning of an aperiodic DRX active time and a beginning of a subsequent periodic DRX active time is less than the first threshold value. The method may comprise skipping a subsequent periodic DRX active time on a condition that the time difference between an end of an aperiodic DRX active time and a start of a subsequent periodic DRX active time is less than the second threshold value. The method may comprise skipping a subsequent periodic DRX active time on a condition that an available battery power is less than the threshold value regarding available battery power. The skipping a subsequent periodic DRX active time may comprise not starting an associated timer for PDCCH monitoring, for example drx-onDurationTimer, and keeping a main radio in a sleep state. The skipping a subsequent periodic DRX active time may further comprise early reporting a CSI using the received uplink grant information on a condition that a CSI report is scheduled to be sent within the skipped DRX active time. The resources for transmitting the early CSI may be an earliest resource located within the aperiodic DRX active time. The skipping a subsequent periodic DRX active time may further comprise indicating a decision to skip a subsequent periodic DRX active time, a reason to skip a subsequent periodic DRX active time, and battery status information. The skipping a subsequent periodic DRX active time may further comprise monitoring a LP-WUS during the skipped periodic DRX active time.

[0192] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magnetooptical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

CLAIMS What is Claimed:

1. A method for use by a wireless transmit/receive unit (WTRU), the method comprising: receiving configuration information, wherein the configuration information comprises at least one threshold value for skipping a second discontinuous reception (DRX) active time period after activation of a first DRX active time period; receiving an indication, via a low power wake-up signal (LP-WUS), for activating the first DRX active time period; starting a DRX on duration timer associated with the first DRX active time period after a time offset from reception of the LP-WUS; monitoring for and receiving a physical downlink control channel (PDCCH) transmission in resources while the DRX on duration timer associated with the first DRX active time period is running; receiving a physical downlink shared channel (PDSCH) transmission or transmitting a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission based on the received PDCCH transmission; determining to skip the second DRX active time period based on the at least one threshold value; and reporting channel state information (CSI), for a CSI report scheduled to be reported in the second DRX active time period, in substitute CSI reporting uplink resources in the first DRX active time period.

2. The method of claim 1 , further comprising: skipping the second DRX active time period based on the at least one threshold value, based on the determining to skip.

3. The method claim 2, wherein skipping the second DRX active time period comprises the main radio (MR) continuing in a sleep state and not starting a DRX on duration timer associated with the second DRX active time period.

4. The method of claim 1 , wherein the at least one threshold value comprises: an end-to-start time gap threshold value associated with a time difference between an end of the first DRX active time period and a start of the second DRX active time period, wherein the end of the first DRX active time period is based on an end of a timer associated with the first DRX active time period, and wherein the start of the second DRX active time period is based on start of a DRX on duration timer associated with the second DRX active time period.

5. The method of claim 4, further comprising: determining to skip the second DRX active time period based on the end of the first DRX active time period and the start of the second DRX active period time being less than the end-to-start time gap threshold value.

6. The method of claim 1 , wherein the at least one threshold value comprises an available battery power threshold value.

7. The method of claim 6, further comprising determining to skip the second DRX active time period based on an available battery power being less than the available battery power threshold value.

8. The method of claim 1 , further comprising: monitoring a LP-WUS using a low power radio (LR) during a skipped second DRX active time period.

9. The method of claim 1, wherein the configuration information comprises uplink grant information indicating substitute CSI reporting uplink resources during the first DRX active time period.

10. The method of claim 1 , wherein the reporting CSI in substitute CSI reporting uplink resources is based on a CSI report being ready and CSI measurements being performed before or during the first DRX active time period.

11. A wireless transmit/receive unit (WTRU) comprising: a receiver; a transmitter; and a processor, wherein: the receiver is configured to receive configuration information, wherein the configuration information comprises at least one threshold value for skipping a second discontinuous reception (DRX) active time period after activation of a first DRX active time period; the receiver is further configured to receive an indication, via a low power wake-up signal (LP-WUS), for activating the first DRX active time period; the processor is configured to start a DRX on duration timer associated with the first DRX active time period after a time offset from reception of the LP-WUS; the processor and the receiver are further configured to monitor for and receive a physical downlink control channel (PDCCH) transmission in resources while the DRX on duration timer associated with the first DRX active time period is running; the receiver is further configured to receive a physical downlink shared channel (PDSCH) transmission or the transmitter is configured to transmit a physical uplink shared channel (PUSCH) transmission or a physical uplink control channel (PUCCH) transmission based on the received PDCCH transmission; the processor is further configured to determine to skip the second DRX active time period based on the at least one threshold value; and the transmitter is further configured to report channel state information (CSI), for a CSI report scheduled to be reported in the second DRX active time period, in substitute CSI reporting uplink resources in the first DRX active time period.

12. The WTRU of claim 11 , wherein the processor is further configured to skip the second DRX active time period based on the at least one threshold value, based on the determining to skip.

13. The WTRU claim 12, wherein skipping the second DRX active time period comprises the main radio (MR) continuing in a sleep state and not starting a DRX on duration timer associated with the second DRX active time period.

14. The WTRU of claim 11 , wherein the at least one threshold value comprises: an end-to-start time gap threshold value associated with a time difference between an end of the first DRX active time period and a start of the second DRX active time period, wherein the end of the first DRX active time period is based on an end of a timer associated with the first DRX active time period, and wherein the start of the second DRX active time period is based on start of a DRX on duration timer associated with the second DRX active time period.

15. The WTRU of claim 14, wherein the processor is further configured to determine to skip the second DRX active time period based on the end of the first DRX active time period and the start of the second DRX active period time being less than the end-to-start time gap threshold value.

16. The WTRU of claim 11 , wherein the at least one threshold value comprises an available battery power threshold value.

17. The WTRU of claim 16, wherein the processor is further configured to determine to skip the second DRX active time period based on an available battery power being less than the available battery power threshold value.

18. The WTRU of claim 11 , wherein the processor and the receiver are further configured to monitor a LP-WUS using a low power radio (LR) during a skipped second DRX active time period.

19. The WTRU of claim 11 , wherein the configuration information comprises uplink grant information indicating substitute CSI reporting uplink resources during the first DRX active time period.

20. The WTRU of claim 11 , wherein the reporting CSI in substitute CSI reporting uplink resources is based on a CSI report being ready and CSI measurements being performed before or during the first DRX active time period.