Methods and apparatus for wireless transmit / receive unit (WTRU) power control

Abstract

To provide methods and apparatus for a wireless transmit / receive unit.SOLUTION: A method includes receiving a time domain resource allocation list configuration including entries, each including a resource allocation that includes a slot offset value. L1 signaling is received indicating a minimum slot offset value. Downlink control information on a physical downlink control channel in a slot is decoded. An index for identifying an entry in the TDRA list is obtained from the decoded DCI. A particular slot offset value identified by the index is retrieved from the TDRA list and compared with the minimum slot offset value. If the particular slot offset value is less than the minimum slot offset value, the entry is invalid. If the particular slot offset value is greater than or equal to the minimum slot offset value, a physical downlink shared channel is received.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to a method and apparatus for power control of a wireless transmit / receive unit (WTRU). [Background technology]

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 62 / 720,547, filed August 21, 2018, U.S. Provisional Patent Application No. 62 / 73,539, filed September 25, 2018, U.S. Provisional Patent Application No. 62 / 752,797, filed October 30, 2018, U.S. Provisional Patent Application No. 62 / 753,597, filed October 31, 2018, and U.S. Provisional Patent Application No. 62 / 840,935, filed April 30, 2019, the contents of which are incorporated herein by reference.

[0003] Next-generation air interfaces, including LTE Advanced Pro and further evolutions of New Radio (NR), are expected to support a wide range of use cases. Such use cases may have diverse service requirements, such as low-overhead, low-data-rate, power-efficient services (mMTC), ultra-reliable, low-latency services (URLLC), and high-data-rate mobile broadband services (eMBB), with respect to diverse WTRU capabilities, such as low-power, low-bandwidth, very wide-bandwidth (e.g., 80 MHz), and high-frequency (e.g., >6 GHz). Such use cases may have various spectrum usage models, such as licensed or unlicensed / shared, and may operate under various mobility scenarios, such as stationary / fixed or high-speed trains, using architectures flexible enough to fit diverse deployment scenarios, such as standalone, non-standalone with assistance from different air interfaces, centralized, virtualized, or distributed over ideal / non-ideal backhaul. Summary of the Invention

[0004] A method and apparatus for power control of a wireless transmit / receive unit (WTRU) are described. The method includes receiving a time domain resource allocation (TDRA) list configuration including entries, each of which includes a resource allocation including a slot offset value. L1 signaling indicating a minimum slot offset value is received. Downlink control information (DCI) is decoded for a physical downlink control channel in a slot. An index identifying an entry in the TDRA list is obtained from the decoded DCI. A specific slot offset value identified by the index is retrieved from the TDRA list and compared with the minimum slot offset value. If the specific slot offset value is less than the minimum slot offset value, the entry is invalid. If the specific slot offset value is greater than or equal to the minimum slot offset value, a physical downlink shared channel is received.

[0005] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate similar elements and in which: [Brief explanation of the drawings]

[0006] [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system in which one or more disclosed aspects may be implemented. [Figure 1B] 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communication system shown in FIG. 1A according to an embodiment. [Figure 1C] 1B is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communication system shown in FIG. 1A according to an embodiment. [Figure 1D] 1B is a system diagram illustrating a further example RAN and a further example CN that may be used within the communication system shown in FIG. 1A according to an embodiment. [Figure 2] FIG. 1 is a diagram of an example of discontinuous reception (DRX). [Figure 3] FIG. 1 is a diagram of an exemplary DRX cycle with wake-up and go-to-sleep signaling. [Figure 4] FIG. 1 is a diagram of an example channel state information (CSI) resource configuration and CSI reporting configuration. [Figure 5] 10 is a flow diagram of an example method for power control in a WTRU. [Figure 6] 1 is a diagram of an example WTRU configured with multiple receiver components that can support different power modes. [Figure 7] FIG. 1 is a system diagram illustrating an example use of a low power mode receiver in different coverage scenarios. [Figure 8] 1 is a diagram of an example of switching between two radio performance states. [Figure 9] FIG. 10 is a signal diagram of an example of multiple DRX configurations based on power modes. [Figure 10] FIG. 10 is a signal diagram of an example of power mode switching during ON durations in different DRX cycles. [Figure 11] 1 is a signal diagram of an example of a wake-up signal (WUS) that determines an associated PDCCH monitoring power mode and a set of aggregation levels for physical downlink control channel (PDCCH) monitoring. [Figure 12] FIG. 10 is a signal diagram of an example of aperiodic CSI reporting triggering with associated power mode indication. [Figure 13] FIG. 1 is a signal diagram of an example of periodic CSI reference signal (CSI-RS) and aperiodic CSI reporting. [Figure 14]FIG. 10 is a signal diagram of an example of periodic CSI-RS and periodic CSI reporting. [Figure 15] FIG. 10 is a signal diagram of an exemplary maximum rank limit with a timer. [Figure 16] 1 is a graph illustrating an example of a reduced number of receive radio frequency (Rx RF) chains based on radio link monitoring (RLM) measurements. [Figure 17] 10 is a graph showing increasing numbers of Rx RF chains based on RLM measurements. [Figure 18] FIG. 10 is a signal diagram of an example of processing a resynchronization signal (RSS) along with a DRX ON duration time interval. DETAILED DESCRIPTION OF THE INVENTION

[0007] 1A illustrates an example communication system 100 in which one or more disclosed aspects may be implemented. The communication system 100 may be a multiple-access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communication system 100 may enable the multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tailed 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), etc.

[0008] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be understood that the disclosed aspects contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of 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 user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspot or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0009] The communications system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communications networks, e.g., the CN 106, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNodeB (eNB), a home NodeB, a home eNodeB, 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, etc. Although the base stations 114a, 114b are each shown as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0010] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network elements (not shown), e.g., a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for wireless service to a particular geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one aspect, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an aspect, 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.

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

[0012] More specifically, as described 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, etc. 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).

[0013] In an aspect, 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).

[0014] In an aspect, 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.

[0015] In an aspect, 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 both LTE radio access and NR radio access, e.g., using a dual connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0016] In other aspects, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless technology, 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), etc.

[0017] 1A may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point and may utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, etc. In one aspect, 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 aspect, 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 aspect, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or a femtocell. 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 through the CN 106.

[0018] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various quality of service (QoS) requirements, e.g., separate throughput, latency, error tolerance, reliability, data throughput, mobility, etc. The CN 106 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, e.g., user authentication. Although not shown in FIG. 1A , it will be understood that the RAN 104 and / or CN 106 may be in direct or indirect communication with other RANs employing the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may utilize NR radio technology, the CN 106 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0019] 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 other networks 112. The PSTN 108 may include a circuit-switched telephone network providing 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 Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or IP in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the network 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.

[0020] 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 separate wireless networks over separate wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a that may employ cellular-based wireless technology and with a base station 114b that may employ IEEE 802.11 wireless technology.

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

[0022] The processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other function 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 understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

[0024] 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 aspect, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) to transmit and receive wireless signals over the air interface 116.

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

[0026] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. Additionally, the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or 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, etc. In other aspects, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, for example, on a server or home computer (not shown).

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

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

[0029] The processor 118 may be further 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 photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. 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.

[0030] The WTRU 102 may include a full-duplex radio (e.g., where transmission and reception of some or all of the signals associated with a particular subframe for both the UL (e.g., for transmission) and DL (e.g., for reception) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference through signal processing in hardware (e.g., a choke) or via a processor (e.g., via a separate processor (not shown) or via processor 118). In an aspect, the WTRU 102 may include a half-duplex radio for transmission and reception of some or all of the signals (e.g., associated with a particular subframe for either the UL (e.g., for transmission) or DL ​​(e.g., for reception)).

[0031] 1C is a system diagram illustrating an embodiment of the RAN 104 and the CN 106. As described above, the RAN 104 may employ 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.

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

[0033] 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, etc. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.

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

[0035] 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 act as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, activating / deactivating bearers, selecting a particular serving gateway during initial connection of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0036] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as fixing the user plane during handover between eNode Bs, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, etc.

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

[0038] The CN 106 may facilitate communication 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 communication between the WTRUs 102a, 102b, 102c and traditional landline communication devices. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. Additionally, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0039] Although the WTRU is described in Figures 1A-1D as a wireless terminal, it is contemplated that in certain representative aspects such a terminal may be capable of using (e.g., temporarily or permanently) a wired communication interface with the communication network.

[0040] In an exemplary embodiment, the other network 112 may be a WLAN.

[0041] 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 to or interface with a distribution system (DS) or another type of wired / wireless network that carries traffic to and from the BSS. Traffic to a STA originating from outside the BSS may arrive through the AP and be delivered to the STA. Traffic originating from a STA to a destination outside the BSS may be sent to the AP for delivery to the respective destination. Traffic between STAs within a BSS may be sent through the AP, for example, if the source STA can send traffic to the AP, which can deliver the traffic to the destination STA. Traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent between (e.g., directly between) a source STA and a destination STA using direct link setup (DLS). In certain exemplary aspects, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may have no APs, and STAs within or using an IBSS (e.g., all of the STAs) may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an "ad hoc" mode of communication.

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

[0043] High-throughput (HT) STAs may, for example, use 40 MHz wide channels for communication via combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels to form the 40 MHz wide channel.

[0044] A Very High Throughput (VHT) STA may support channels of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz width. A 40 MHz channel and / or an 80 MHz channel may be formed by combining adjacent 20 MHz channels. A 160 MHz channel may be formed by combining eight adjacent 20 MHz channels or two non-adjacent 80 MHz channels (which may be referred to as an 80+80 configuration). For the 80+80 configuration, after channel encoding, the data may be passed through a segment parser, which may split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing may be performed separately on each stream. The streams may be mapped onto two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration can be reversed and the combined data can be sent to the media access control (MAC).

[0045] Sub-1 GHz modes of operation are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared 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, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative aspect, 802.11ah can support meter-type control / machine-type communication (MTC), such as MTC devices in macro coverage areas. MTC devices can have limited capabilities, including, for example, support for (e.g., only support for) specific and / or limited bandwidths. MTC devices can include batteries with above-threshold battery life (e.g., to maintain very long battery life).

[0046] A WLAN system capable of supporting multiple channels and channel bandwidths, e.g., 802.11n, 802.11ac, 802.11af, and 802.11ah, includes a channel that may be designated as a primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by the STA supporting the smallest bandwidth operating mode among all STAs operating in the BSS. In the example of 802.11ah, for a STA (e.g., an MTC-type device) that supports (e.g., only supports) the 1 MHz mode, the primary channel may be 1 MHz wide, 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) setting may depend on the status of the primary channel. If the primary channel is busy, for example due to STAs (that only support a 1 MHz mode of operation) transmitting to the AP, then all available frequency bands may be considered busy even if most of those available frequency bands remain idle.

[0047] In the United States, the available frequency bands that can be used by 802.11ah are from 902 MHz to 928 MHz. In South 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 available bandwidth for 802.11ah is 6 MHz to 26 MHz depending on the country code.

[0048] 1D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may employ 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.

[0049] While the RAN 104 may include gNBs 180a, 180b, and 180c, it will be understood that the RAN 104 may include any number of gNBs while remaining consistent with an aspect. The gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. In one aspect, the gNBs 180a, 180b, and 180c may implement MIMO technology. For example, the gNB 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, and 180c. Thus, the gNB 180a may use multiple antennas, for example, to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In aspects, 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 aspects, the gNBs 180a, 180b, 180c may implement coordinated multipoint (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and 180b (and / or 180c).

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

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

[0052] 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, supporting network slicing, DC, interworking between NR and E-UTRA, routing of user plane data to user plane functions (UPFs) 184a, 184b, routing of control plane information to access and mobility management functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D , the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.

[0053] 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 above-mentioned elements are shown as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0054] 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 act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling separate protocol data unit (PDU) sessions with separate requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating non-access stratum (NAS) signaling, mobility management, etc. Network slicing may be used by the AMF 182a, 182b to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service being utilized by the WTRU 102a, 102b, 102. For example, separate network slices may be established for separate use cases, such as services relying on Ultra-Reliable Low-Latency (URLLC) access, services relying on enhanced High-Capacity Mobile Broadband (eMBB) access, services related to MTC access, etc. The AMFs 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0055] The SMFs 183a and 183b may be connected to the AMFs 182a and 182b in the CN 106 via an N11 interface. The SMFs 183a and 183b may also be connected to the UPFs 184a and 184b in the CN 106 via an N4 interface. The SMFs 183a and 183b may select and control the UPFs 184a and 184b and configure the routing of traffic through the UPFs 184a and 184b. The SMFs 183a and 183b may perform other functions, such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0056] The UPFs 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 communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPFs 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, etc.

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

[0058] 1A-1D and the corresponding description thereof, one or more or all of the functions described herein in connection with one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices 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.

[0059] The emulation device 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, one or more emulation devices may perform one or more, or all, functions while fully or partially implemented and / or deployed as part of a wired and / or wireless communications network to test other devices in the network. One or more emulation devices may perform one or more, or all, functions while temporarily implemented / deployed as part of a wired and / or wireless communications network. The emulation device may be directly coupled to another device for testing and / or performing testing using over-the-air wireless communications.

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

[0061] One or more networks are described herein and may refer, in aspects, to one or more gNBs, each of which may be associated with one or more transmit / receive points (TRPs) or any other node in the RAN.

[0062] The WTRU receiver may need to implement automatic frequency control (AFC) to keep the frequency of its local oscillator aligned with the oscillator used at the transmitter. This function may be supported by various synchronization signals (SS) and / or reference signals (RS). Maintaining coarse AFC may be necessary for coherent detection of the physical downlink control channel (PDCCH) and any incoming scheduled DL transmissions. In LTE, coarse AFC may use PSS / SSS synchronization codes, which may be present every 5 ms, and CRSs, which may be present on at least two OFDM symbols per 1 ms interval. In NR, coarse AFC may use synchronization signal blocks (SSBs), which may have a periodicity of at least 20 ms. NR devices may also utilize CSI reference signals (CSI-RSs), if configured and activated, or demodulation reference signals (DMRSs), which may be present only during DL transmissions. A special signal called a tracking reference signal (TRS) can also be configured and activated for NR devices to facilitate coarse AFC. The TRS can be configured as a non-zero power CSI-RS resource set with a recurrence period of 10, 20, 40, or 80 ms. It can be present on three resource elements (RE) in a resource block (RB) and in two out of fourteen OFDM symbols in two consecutive time slots. A reduced-density TRS that only uses the first time slot can also be configured.

[0063] FIG. 2 is a diagram 200 of an example of discontinuous reception (DRX). FIG. 2 shows a complete DRX cycle 202a and a portion of a second DRX cycle 202b. In the example shown in FIG. 2, each DRX cycle 202a, 202b includes an ON duration 204a, 204b and an OFF duration 206a, 206b. A WTRU may monitor a DL control channel, such as a PDCCH, during the ON durations 204a, 204b and enter a sleep state (e.g., not monitor the PDCCH) during the OFF durations 206a, 206b. Although only two DRX cycles 202a, 202b are shown in FIG. 2, a WTRU configured for DRX may periodically repeat the DRX cycle for any number of cycles.

[0064] As shown in the example of Figure 2, the WTRU may start a DRX cycle with an ON duration. An ON duration timer may be used to determine the number of consecutive PDCCH occasions that the WTRU may need to monitor or decode, such as after waking up from a DRX cycle or at the beginning of a DRX cycle. A DRX inactivity timer may be used to determine when to switch to an OFF duration. A DRX retransmission timer may be used to determine the number of consecutive PDCCH occasions to monitor if a retransmission is expected by the WTRU. A DRX retransmission timer may be used to determine the maximum duration before a grant for a DL or UL retransmission can be received.

[0065] In addition to not monitoring DL channels, such as PDCCH, during OFF durations, such as OFF durations 206a, 206b, the WTRU may not measure or report channel state information (CSI) in subframes configured for measuring and / or reporting periodic CSI reports. In aspects, the WTRU may need to monitor PDCCH or PDCCH occasions during active time, which may occur during ON or OFF durations. In other aspects, active time may start during an ON duration and continue during an OFF duration. Active time may include time when at least one of the following is true: Any DRX timer, such as an ON duration timer, an inactivity timer, a retransmission timer, or a random access contention resolution timer, is running, a scheduling request is sent (e.g., on the physical uplink control channel (PUCCH)), and no PDCCH indicating a new transmission addressed to the Cell Radio Network Identifier (C-RNTI) of the MAC entity of the WTRU has been received after successful reception of a random access response for a contention-based random access preamble that has not been selected by the MAC entity.

[0066] A DRX cycle, such as DRX cycles 202a, 202b, may be a short DRX cycle or a long DRX cycle. In an aspect, a WTRU may use a short DRX cycle for a period of time and then use a long DRX cycle. A DRX inactivity timer may be used to determine the duration (e.g., in terms of transmission time intervals (TTIs)) after a PDCCH occasion in which a successfully decoded PDCCH indicates an UL or DL ​​user data transmission. A PDCCH occasion may be a time period that may include a PDCCH, such as a symbol, a set of symbols, a slot, or a subframe. A DRX short cycle may be the first DRX cycle that a WTRU enters after expiration of the DRX inactivity timer. The WTRU may be in the short DRX cycle until expiration of the DRX short cycle timer. If the DRX short cycle timer expires, the WTRU may use the long DRX cycle. The DRX short cycle timer may be used to determine the number of consecutive subframes that a short DRX cycle may follow after expiration of the DRX inactivity timer.

[0067] In RRC connected mode, the WTRU may use connected mode DRX (C-DRX). When an LTE or NR device is in C-DRX, it may be configured with a DRX cycle. Separate short and long DRX cycles may be configured. The C-DRX cycle may be set in the range of tens to hundreds of milliseconds. The WTRU may wake up at a determined time, such as during the DRX ON duration, and attempt to decode the PDCCH in the first timeslot of the DRX ON duration. If no message is received or decoded in that timeslot, the WTRU may decrement a configurable ON duration counter and may again attempt to decode the PDCCH at the next PDCCH monitoring opportunity on the active CORESET and for the configured search space. If the counter reaches zero, the WTRU may return to a sleep state and will not attempt to decode the PDCCH again until the next DRX ON duration.

[0068] To be able to decode the PDCCH at the beginning of the C-DRX ON duration (e.g., the first timeslot), the WTRU may need to have achieved at least coarse AFC. The DMRS contained within the RBs of the active bandwidth portion (BWP) carrying the PDCCH for the device can only be utilized to fine-tune the AFC during ongoing reception of that PDCCH and for subsequent timeslots. In LTE, the WTRU can achieve coarse AFC by waking up a short period of time before the beginning of the DRX ON duration and measuring the cell-specific reference signals (CRS) available in most subframes.

[0069] In aspects, a wake-up signal (WUS) and a go-to-sleep signal (GOS) may be used, for example, in conjunction with DRX operation. The WUS / GOS may be associated with one or more DRX cycles and may be transmitted and / or received before an associated time or portion of an associated DRX cycle.

[0070] 3 is a diagram 300 of an example DRX cycle 302 with a WUS and a GOS. In the example shown in FIG. 3, a WTRU may receive a WUS 308 and, in response, wake up to monitor the downlink channel during the associated ON duration 304. In an aspect, a WTRU receiving a WUS may wake up and monitor the downlink channel during the ON duration for one or more DRX cycles. The WTRU may also receive a GOS 310 and, in response, not monitor the downlink channel during the associated OFF duration 306. In an aspect, a WTRU receiving a GOS may not monitor the downlink channel for one or more DRX cycles and may remain in a sleep mode. In an aspect, either a WUS or a GOS, or both a WUS and a GOS may be implemented.

[0071] In NR, a WTRU may be configured with one or more CSI resource configurations, such as non-zero-power (NZP) CSI resources. Each CSI resource configuration may include one or more NZP-CSI-RS resource sets. Each NZP CSI resource set may include up to 64 NZP-CSI-RS resources. A triggering offset for aperiodic NZP-CSI-RS resources may be configured for each NZP-CSI-RS resource set. A WTRU may be further configured with one or more CSI reporting configurations. Each CSI reporting configuration may be associated with a CSI resource configuration for channel measurements. An associated BWP-ID and resource type (e.g., aperiodic, periodic, or semi-persistent) may be configured for each CSI resource configuration.

[0072] 4 is a diagram 400 of an example CSI resource and CSI reporting configuration, illustrating the association between various NZP-CSI-RS resources, NZP-CSI-RS resource sets, CSI resource configurations, and CSI reporting configurations. In the example shown in FIG. 4, a WTRU is configured with eight NZP-CSI-RS resources 401, 402, 403, 404, 405, 406, 407, and 408. However, the ellipsis in FIG. 4 indicates that the WTRU may be configured with any number of NZP-CSI-RS resources. NZP-CSI-RS resources 401 include resource set 410, NZP-CSI-RS resources 402 include resource set 411, NZP-CSI-RS resources 403 include resource sets 410 and 411, NZP-CSI-RS resources 404 and 405 each include resource set 412, and NZP-CSI-RS resources 406, 407, and 408 each include resource set 413. Resource set 410 may have an AP triggering offset of 0, and resource set 411 may have an AP triggering offset of 4. The remaining resource sets (e.g., 412 and 413) may also be configured with different AP triggering offsets.

[0073] Resource sets 410 and 411 may be associated with CSI resource configuration 420, resource set 412 may be associated with CSI resource configuration 421, and resource set 413 may be associated with CSI resource configuration 422. CSI resource configuration 420 may be for an aperiodic resource type and BWP-ID 0, CSI resource configuration 421 may be for a periodic resource type and BWP-ID 0, and CSI resource configuration 422 may be for a semi-persistent resource type and BWP-ID 2. CSI resource configuration 420 may be associated with CSI reporting configurations 430, 431, and 433, CSI resource configuration 421 may be associated with CSI reporting configurations 432 and 434, and CSI reporting configuration 422 may be associated with CSI reporting configuration 435.

[0074] The WTRU may receive an aperiodic CSI request in slot n, and the associated aperiodic CSI-RS (or NZP-CSI-RS) resource set may be located in slot n+x, where x may be at least one of {0, 1, 2, 3, 4}. Table 1 below shows examples of CSI request fields and associated reporting and resource configurations.

[0075] [Table 1]

[0076] Each CSI request field may be associated with a reporting setting (or CSI-related report configuration information), which may include up to 16 reporting configurations. Each reporting configuration may be considered a CSI reporting configuration. Provided that multiple aperiodic NZP-CSI-RS resource sets are associated with a reporting configuration, a single aperiodic NZP-CSI-RS resource set may be selected for the CSI request field. Each aperiodic NZP-CSI-RS resource set may be configured with a slot offset value from the slot in which the WTRU received the CSI request.

[0077] In NR, a WTRU may be configured with a set of slot offsets for physical downlink shared channel (PDSCH) scheduling from the slot in which the WTRU received scheduling DCI. The WTRU may be configured with a PDSCH-Time Domain Resource Allocation List (or PDSCH-TDRA list), which may include up to a certain number (e.g., 16) of PDSCH-TDRA configurations. Each PDSCH-TDRA configuration may include a slot offset value (e.g., k0), which may be, for example, one of {0, 1, ..., 32}, a mapping type, which may be, for example, one of {Type A, Type B}, and / or a starting symbol and length (e.g., SLIV), which may be, for example, one of {0, 1, ..., 127}. The k0 value may determine the slot offset for PDSCH reception from the slot in which the scheduling DCI is received. For example, if the WTRU receives DCI for PDSCH in slot #n, it may receive PDSCH in slot #n+k0. The mapping type may determine the slot length. For example, Type A may be used for a regular slot length, and Type B may be used for a subslot length. The SLIV may determine the starting symbol within the slot and the length of the PDSCH. In the examples and aspects described herein, the PDSCH may be replaced by a PUSCH, and slot offset k0 may be replaced by slot offset k2. For example, the WTRU may be configured with a PUSCH-TimeDomainResourceAllocationList (or PUSCH-TDRA list), which may include up to a certain number (e.g., 16) of PUSCH-TDRA configurations.Each PUSCH-TDRA configuration may include a slot offset value (e.g., k2), which may be, for example, one of {0, 1, ..., 32}, a mapping type, which may be, for example, one of {Type A, Type B}, and / or a starting symbol and length (e.g., SLIV), which may be, for example, one of {0, 1, ..., 127}. The k2 value may determine the slot offset for the PUSCH transmission from the slot in which the scheduling DCI is received.

[0078] A receiver of a wireless communication device may include multiple RF chains. Each such chain may include one or more antenna elements and analog circuitry (e.g., low-noise amplifiers, filters, oscillators, mixers, and / or analog-to-digital converters). Reception using multiple RF chains can improve performance through diversity and / or spatial processing. Minimum performance requirements for RF sensitivity assume that the WTRU is equipped with a minimum number of Rx antenna ports.

[0079] For operation in Frequency Range 1 (below 6 GHz), many NR devices will use four Rx RF chains for receiving DL signals and channels from a gNB, for example, to provide robust link performance and efficiently utilize spatial multiplexing to achieve high DL spectral efficiency. Minimum reception requirements using the four Rx RF chain assumption can be set for some NR operating bands. Dedicated-type NR devices, such as those intended for V2X-type applications, can be expected to use only two Rx RF chains. Dual-mode LTE / NR devices sharing a common RF can also be expected to follow LTE requirements for DL ​​reception. For operation in Frequency Range 2 (mmWave), many NR devices will implement analog beamforming support by using multiple RF panels. Among other benefits, beamforming can enable improved link budgets when operating at mmWave frequencies.

[0080] In existing NR technologies, similar to LTE, the number of Rx antennas to be used by a device for DL ​​reception depends on the operating band. Device performance requirements can be set by assuming the availability of a required number of device Rx antennas. A device can advertise support for a set of LTE or NR operating bands to the network, possibly along with supported band combinations for carrier aggregation or dual connectivity. This can implicitly indicate support for the required number of Rx chains on the device for the operating band.

[0081] Power consumption for active RF components such as oscillators, low-noise amplifiers (LNAs), and analog-to-digital (A / D) converters can vary proportionally with the number of active Rx chains in a device. The digital baseband (BB) can implement low-level functions such as channel sample buffering, spatial layer demapping, and channel estimation. Power consumption in low-level digital BB can also increase with the number of active Rx paths. Other high-level functions in digital BB, such as transport channel processing and channel decoding, can experience an increase in power consumption in the presence of reception using multiple active RF chains in a device, but primarily depending on the transmitted data rate (which can be higher with fewer Rx chains if the signal-to-interference-and-noise ratio (SINR) is sufficiently good).

[0082] WTRU power consumption is expected to increase in NR as higher carrier frequencies, wider bandwidths, and advanced MIMO schemes are deployed. For example, transceiver circuitry, including RF chains, consumes a significant amount of power, e.g., compared to baseband processing. Even when configured with C-DRX, data may not be received for significant periods of time while the WTRU monitors the PDCCH during active time. As a result, a WTRU with multiple receive (Rx) chains may waste a significant amount of power attempting to receive while no data is being transmitted. If a WTRU implementation attempts to save power by turning off some Rx chains during active time, there is a risk that the WTRU may not be able to meet performance requirements because the network may assume that it is always ready to receive the PDCCH and PDSCH using all Rx chains. Conventional power saving mechanisms do not allow for dynamic turning on and off of RF chains, or other parts of the transceiver circuitry. Aspects are described herein that may allow a WTRU to safely reduce the number of its Rx chains (if it can do so without impacting performance).

[0083] Additionally, the signals needed to achieve coarse AFC may not generally be available immediately before the beginning of the WTRU's on-duration. As a result, an NR WTRU may need to wake up during the on-duration for the sole purpose of detecting an appropriate signal (e.g., SSB). This may be less efficient than the WTRU immediately before the beginning of the on-duration, given the actual transition time for switching on and off associated circuitry. Aspects are described herein that may enable the maintenance of coarse AFC while reducing the number of wake-up intervals that are not related to the actual DRX on-duration.

[0084] Furthermore, for example, in R15 NR, DRX can be configured with at most a single DRX configuration. Sleep opportunities are purely time-domain based. Furthermore, the WTRU may spend a significant amount of time monitoring the PDCCH in an unscheduled state. In R15, during an ON duration, the WTRU is required to monitor all CORESETs and all search spaces in the active BWP for each ON duration, which may result in a significant number of blind decodes and consume a significant amount of device power. Given that a WTRU in DRX is likely to be in the default BWP due to the expiration of the inactivity timer, a potential tool to reduce the number of blind decodes using the R15 framework may be to configure a default BWP with a single search space and rely on sending a DCI with a BWP switch when scheduling the WTRU during a given ON duration. However, given that the RACH and SR functionality rely on the default BWP, and given that the WTRU may resort to the default BWP if the BWP inactivity timer is short, scheduling capacity may be limited if the default BWP is limited to one search space or one CORESET. Aspects that can address this are described herein.

[0085] The aspects described herein provide for a number of different radio performance states, radio performance modes, power modes, or transmission modes. Those of ordinary skill in the art will understand that these or similar terms may be used interchangeably throughout. In aspects, a WTRU may be configured to operate according to one of a set of possible radio performance states, radio performance modes, power modes, or transmission modes. The radio performance state, radio performance mode, power mode, or transmission mode may, for example, determine a set of maximum performance metrics and / or capabilities applicable to the WTRU at a given time.

[0086] As described above, the WTRU may be configured with a set of PDSCH-TDRAs (e.g., a PDSCH-TDRA list). The WTRU may receive an indication of one of the PDSCH-TDRAs in the DCI for PDSCH scheduling. For example, if the indicated PDSCH-TDRA is k0=0, extra WTRU power consumption may be required because the WTRU may need to buffer the PDSCH region in slots where the PDCCH is monitored for DCI using the C-RNTI or configured scheduling RNTI (CS-RNTI).

[0087] In some aspects, the power mode may determine which subset of PDSCH-TDRA entries in the configured PDSCH-TDRA list may be valid or present in the associated DCI for PDSCH scheduling. For example, when the WTRU is in a first power mode (e.g., normal mode), the WTRU may assume that all PDSCH-TDRA entries in the PDSCH-TDRA list may be used when the WTRU monitors the PDCCH in a slot. When the WTRU is in a second power mode (e.g., power save mode), the WTRU may assume that PDSCH-TDRA entries with k0=0 may not be used when the WTRU monitors the PDCCH in a slot, or the WTRU may ignore PDSCH-TDRA entries with k0=0.

[0088] In some aspects, a power mode may determine which subset of aperiodic CSI reporting trigger states in a configured CSI reporting trigger state list may be valid (or present) in an associated DCI for aperiodic CSI reporting. For example, when a WTRU is in a first power mode, the WTRU may assume or expect that all CSI reporting trigger states in the configured CSI reporting trigger state list may be valid when the WTRU monitors the PDCCH for aperiodic CSI reporting. When a WTRU is in a second power mode, the WTRU may assume or expect that CSI reporting trigger states associated with an aperiodic NZP-CSI-RS resource set with a slot offset less than a threshold may be invalid. As used herein, “invalid” and “unusable” may be used interchangeably in the context of CSI reporting triggers, with “unusable” being an example of “invalid.” In some aspects, the threshold value (Ttre) may be a predefined number, such as “1.” In some aspects, the threshold value may be determined based on numerology. For example, a first threshold may be used for a first subcarrier spacing (e.g., for a 15 kHz SCS, Ttre=1), and a second threshold may be used for a second subcarrier spacing (e.g., for a 60 kHz SCS, Ttre=3).

[0089] In some aspects, the power mode may determine a minimum slot offset value of an NZP-CSI-RS resource set associated with one or more configured aperiodic CSI reporting trigger states. In some aspects, the power mode may determine a maximum transmission rank and / or a maximum modulation order for the PDSCH. For example, when the WTRU is in a first power mode, the WTRU may determine a maximum transmission rank (R ) based on the capabilities of the WTRU when the WTRU monitors an associated PDCCH in a slot. max ) and / or maximum modulation order (M max ) when the WTRU is in the second power mode, the WTRU may expect to receive the PDSCH at a limited maximum transmission rank (R limit , R max >R limit ) and / or limited maximum modulation order (M limit , M max >M limit ) can be assumed or expected to receive the PDSCH.

[0090] In some aspects, the power mode may determine a set of aggregation levels and / or multiple candidates for aggregation levels. For example, when the WTRU is in a first power mode, the WTRU may monitor all aggregation levels and / or their associated multiple candidates configured for the search space. When the WTRU is in a second power mode, the WTRU may monitor a subset of aggregation levels and / or multiple candidates configured for the search space. In such aspects, a subset determined based on the first N entries of decoding candidates for each configured aggregation level may be monitored. N may be a predefined number configured via higher layer signaling or determined by the WTRU. Alternatively, or additionally, in such aspects, the maximum aggregation level within the configured aggregation levels may be monitored by the WTRU.

[0091] In some aspects, the power mode may determine the operating frequency bandwidth (e.g., the bandwidth of the active BWP). For example, when the WTRU is in a first power mode, the WTRU may monitor the PDCCH in the first BWP, and when the WTRU is in a second power mode, the WTRU may monitor the PDCCH in the second BWP. The first BWP may be wider than the second BWP.

[0092] In some aspects, the power mode may be determined based on a search space type or ID. In an example, a first power mode may be used in a first search space type (e.g., any common search space associated with CORESET#0), and a second power mode may be used in a second search space type (e.g., a WTRU-specific search space). In another example, a first power mode may be used in a first search space (e.g., a search space ID not associated with the second power mode), and a second power mode may be used in a second search space for which the search space ID may be configured. Alternatively, the search space ID for the second power mode may be implicitly determined based on the search space ID associated with a particular CORESET. For example, a search space associated with CORESET#x may be determined for the second power mode, where the value x may be configured via higher layer signaling or predetermined (e.g., to 0). Additionally or alternatively, a search space ID for the second power mode may be implicitly determined based on a search space ID used for a particular RNTI. For example, a search space for a power saving RNTI (PS-RNTI) may be determined for the second power mode, where the PS-RNTI may be for the uplink and downlink shared channels (e.g., PDSCH and PUSCH).

[0093] In some aspects, the power mode may be determined based on a search space configuration parameter. In one example, the power mode may be determined based on the periodicity of the search space. For example, if the periodicity of the search space is greater than or less than a threshold, a first power mode may be used, and if the periodicity of the search space is less than or greater than the threshold, a second power mode may be used. The threshold may be predetermined or configured via higher layer signaling. In another example, the power mode may be determined based on an aggregation level set (or a minimum aggregation level, or a maximum aggregation level) configured for the search space.

[0094] In some aspects, the power mode may be configured via higher layer signaling, hi other aspects, the power mode may be indicated by an associated power save signal, which may indicate whether the WTRU needs to monitor an associated PDCCH monitoring occasion.

[0095] In some aspects, the power mode may be determined based on a WTRU RRC status, which may include an RRC idle state, an RRC connected state, and an RRC inactive state. The first power mode and the second power mode may be used for the RRC connected state, while the first power mode may only be used for the RRC idle state and the RRC inactive state.

[0096] In some aspects, the power mode may be determined based on PDSCH-TDRA entries in a configured PDSCH-TDRA list. For example, if the smallest k value of the PDSCH-TDRA entries in the configured PDSCH-TDRA list is less than a threshold, the first power mode may be used. Otherwise, the second power mode may be used. In some aspects, the threshold (Ttre) may be '1'. If one or more of the PDSCH-TDRA entries in the configured PDSCH-TDRA list include k=0, the WTRU may use the first power mode. If all PDSCH-TDRA entries in the configured PDSCH-TDRA list have k>0, the WTRU may use the second power mode. In other aspects, the threshold may be determined based on numerology. For example, a first threshold may be used for a first subcarrier spacing (e.g., for a 15 kHz SCS, Ttre=1), and a second threshold may be used for a second subcarrier spacing (e.g., for a 60 kHz SCS, Ttre=3). In some aspects, a power mode may be determined per bandwidth portion (BWP), cell, search space, CORESET, and / or physical channel.

[0097] In some aspects, the minimum slot offset (e.g., minimum k) value of PDSCH-TDRA entries in a configured PDSCH-TDRA list may be dynamically limited. For example, a power saving signal may indicate a threshold for the minimum k value for PDSCH-TDRA entries in the configured PDSCH-TDRA list, and the WTRU may ignore PDSCH-TDRA entries associated with a k value less than the threshold. For example, the WTRU may ignore a (e.g., any) PDSCH-TDRA entry associated with a k value less than the threshold.

[0098] The WTRU ignoring one or more PDSCH-TDRA entries may mean that the WTRU may not expect to receive such entries, that the WTRU may not have buffered the PDSCH region for slots less than a threshold from the slots for PDCCH monitoring, and / or that the WTRU may not have received a PDSCH in slots less than a threshold from the slots for PDCCH monitoring.

[0099] The WRTU may receive or monitor the power saving signal at predefined or predetermined time locations that may be associated with one or more PDCCH monitoring occasions.

[0100] The power saving signal may be at least one of a DCI, a reference signal, and / or a preamble.

[0101] k0 and k2 are used herein as examples of offsets (e.g., slot offsets). Other parameters may be used and still be consistent with the examples and aspects described herein. Other offsets, such as symbol offsets, may be used and still be consistent with the examples and aspects described herein.

[0102] 5 is a flow diagram of an example method 500 of power conservation for a WTRU. In the example shown in FIG. 5, a wireless transmit / receive unit (WTRU) may receive a TDRA list configuration 502. The TDRA list configuration may include multiple entries. Each of the entries may include a resource assignment, which may include, for example, a slot offset value for locating a slot for receiving a PDSCH (or transmitting a PUSCH). In an aspect, each entry in the TDRA list may include a mapping type and / or a startSymbolAndLength parameter, as described in more detail above.

[0103] The WTRU may receive physical layer or Layer 1 (L1) signaling, which may include a minimum slot offset value (504). In an aspect, the physical layer or L1 signaling may be used to dynamically provide the WTRU with the minimum slot offset value. The WTRU may decode DCI at or over a slot on the PDCCH, for example, if scheduled for a PDSCH (or PUSCH) (506). From the decoded DCI, the WTRU may obtain an index that identifies one of the entries in the TDRA list (508). The WTRU may retrieve the specific slot offset value identified by the index from the TDRA list (510).

[0104] The WTRU may compare the particular slot offset value with a minimum slot offset value received, for example, in physical layer or L1 signaling (512). If the particular slot offset value is less than the minimum offset value (514), the WTRU may determine that the entry in the TDRA list identified by the index is invalid (516). In an aspect, if the WTRU determines that the entry is invalid, the WTRU may (e.g., not) receive or buffer a scheduled PDSCH (or transmit a scheduled PUSCH), for example, at a slot offset from the slot in which the DCI was decoded (where the slot offset may be the particular slot offset value). However, if the WTRU determines (514) that the particular slot offset value is greater than or equal to the minimum slot offset value, the WTRU may proceed to receive a scheduled PDSCH (or transmit a scheduled PUSCH), for example, at a slot offset from the slot in which the DCI was decoded (where the slot offset may be the particular slot offset value).

[0105] The above aspects are described with respect to the PDSCH. However, those of ordinary skill in the art will understand that the same or similar methods can also be used with respect to the PUSCH. In aspects, a minimum slot offset may correspond to a particular radio performance state, and when the WTRU is in the particular radio performance state, it may attempt to decode the PDSCH or transmit the PUSCH only if the indicated slot offset (e.g., k0 and / or k2), which may be obtained from the DCI, is greater than or equal to a minimum value (e.g., k0min and / or k2min) applicable to the current radio performance state. In aspects, the minimum value (e.g., k0min or k2min) may be applicable only if the PDCCH is decoded in a particular time symbol of a slot or CORESET. For example, this value may be applicable if the PDCCH is decoded in the last three symbols of a slot. In an aspect, a minimum slot offset (e.g., AP trigger offset) for an NZP-CSI-RS resource set associated with an aperiodic CSI reporting trigger state may be limited or determined based on at least the minimum slot offset (e.g., k) of a PDSCH-TDRA in a PDSCH-TDRA list in the same BWP. For example, if the minimum k value is n (e.g., n=1) in the configured PDSCH-TDRA list, the minimum AP trigger offset value may be n (e.g., n=1) or may be limited to n (e.g., n=1), where n and n may be the same value or different values.

[0106] If a minimum k0 value has been determined for a BWP, the WTRU may not expect the minimum AP trigger offset value to be smaller than a threshold value (e.g., the minimum k0 value) for the same BWP. If a minimum k0 value has been determined for a BWP, the WTRU may ignore or not expect to receive a CSI reporting trigger condition associated with an NZP-CSI-RS resource set that has an AP trigger offset smaller than a threshold value (e.g., the minimum k0 value) for the same BWP. Ignoring a CSI reporting trigger condition may mean that the WTRU may not report CSI for a triggered CSI reporting trigger condition. If a minimum k0 value has been determined for a BWP, the WTRU may ignore a CSI reporting configuration associated with an NZP-CSI-RS resource set that has an AP trigger offset smaller than a threshold value (e.g., the minimum k0 value) in a triggered CSI reporting trigger condition for the same BWP. A CSI reporting trigger condition may include or correspond to one or more CSI reporting configurations, and each CSI reporting configuration may be associated with an NZP-CSI-RS resource set. The WTRU may report a CSI reporting configuration associated with an NZP-CSI-RS resource set that has an AP trigger offset greater than or equal to a threshold value (eg, a minimum k0 value).

[0107] Reporting a CSI reporting configuration may correspond to reporting CSI for that reporting configuration. Reporting a CSI reporting configuration may correspond to reporting CSI based on (e.g., based on measurements of) and / or using an associated NZP-CSI-RS resource set.

[0108] In other aspects, the minimum AP trigger offset value of an NZP-CSI-RS resource set for a CSI reporting configuration (or aperiodic CSI reporting trigger state) may be dynamically limited. For example, the power save signal may indicate a threshold value for the minimum AP trigger offset value for a CSI reporting configuration (or aperiodic CSI reporting trigger state), and the WTRU may ignore CSI reporting configurations (or aperiodic CSI reporting trigger states) associated with NZP-CSI-RS resource sets that have an AP trigger offset value smaller than the threshold.

[0109] The AP trigger offset may be an aperiodic trigger offset, which may be a slot offset. The AP trigger offset may be an offset relative to DL reception or UL transmission. The AP trigger offset may be an offset from the slot (or other time) of AP-triggered PDCCH reception to the RS resource set. The RS resource set may be used for (e.g., of) reception and / or measurement (e.g., of an RS) (e.g., may be, may contain, or may identify time and / or frequency resources therefor). The RS resource set may be used for (e.g., may be, may contain, or may identify time and / or frequency resources therefor) (e.g., of an RS). A CSI request is an example of an AP trigger. An SRS request is an example of an AP trigger.

[0110] An NZP-CSI-RS is an example of an RS. Another RS ​​may be used and still be consistent with the examples and aspects described herein. An NZP-CSI-RS resource set is an example of an RS resource set. Another RS ​​resource set may be used and still be consistent with the examples and aspects described herein. An SRS is another example of an RS for which a minimum offset may apply and may be used to restrict SRS transmissions to AP trigger offsets greater than or equal to the minimum offset.

[0111] A WTRU that is provided with k0min, k2min, and / or a minimum aperiodic CSI triggering offset may receive an aperiodic CSI triggering offset that is smaller than k0, k2, and / or the indicated minimum corresponding value, e.g., in a data scheduling DCI. In some aspects, if the WTRU receives an aperiodic CSI triggering offset that is smaller than k0, k2, and / or the indicated minimum corresponding value in slot n, the WTRU may set the respective k0min, k2min, and / or minimum aperiodic CSI triggering offset to a value (e.g., a configured or default value, such as 0). The WTRU may set or apply the updated value after (e.g., immediately after) decoding of the scheduling DCI is completed, e.g., in slot n or a later slot.

[0112] In some aspects, the WTRU may be provided with minimum slot offsets (k0min and / or k2min) and / or the value of a minimum aperiodic CSI-RS triggering offset. In such aspects, if the WTRU receives a downlink grant with a time domain resource allocation that refers to a PDSCH TDRA table entry with k0 < k0min, for example, a DCI, or an uplink grant with a time domain resource allocation that refers to a PUSCH TDRA table entry with k2 < k2min, or an uplink grant with a CSI request that refers to a state in a CSI-AperiodicTriggerStateList that indicates an aperiodic triggering offset smaller than the minimum aperiodic triggering offset, the WTRU may set the minimum aperiodic triggering offset (e.g., k0min and / or k2min) to a value (e.g., a configured or default value). The value may be zero. The WTRU may expect to receive a DCI (e.g., a scheduling DCI such as a DL grant and / or an UL grant) with a time domain resource allocation that refers to any entry in the PDSCH or PUSCH TDRA table. The WTRU may apply the new value of the minimum aperiodic triggering offset (e.g., k0min and / or k2min) in the slot in which the DCI is received, or it may apply the new value in a slot later than when the new value was received.

[0113] Additionally or alternatively, in aspects where the WTRU is provided with a value of a minimum slot grant with a time domain resource allocation that points to a PDSCH TDRA table entry with k0 < k0min, or an uplink grant with a time domain resource allocation that points to a PUSCH TDRA table entry with k2 < k2min, or an uplink grant with a CSI request that further indicates a state in a CSI-AperiodicTriggerStateList with an aperiodic triggering offset smaller than the minimum aperiodic triggering offset, the WTRU can set the minimum aperiodic CSI-RS triggering offset to a value (e.g., a configured or default value). The value can be zero. The WTRU can expect to receive a DCI (e.g., a scheduling DCI such as a UL grant) with a CSI request that points to any state in the CSI-AperiodicTriggerStateList. The WTRU can measure CSI-RS according to the indicated state of the CSI-AperiodicTriggerStateList. If the WTRU receives a PDCCH and decodes the DCI by the time the first OFDM symbol of the slot with the CSI-RS resource is received, the WTRU can measure the CSI-RS and feedback the indicated CSI report. The WTRU can also skip the CSI report indicated in the scheduling DCI if it is not possible for it to prepare the report.

[0114] In the above method, the default values ​​for k0min, k2min, and the minimum aperiodic triggering offset may be the minimum of all k0, all k2, and all aperiodic triggering offsets, respectively, as configured by the RRC in the corresponding lists. In some aspects, the aspects described in the two immediately preceding paragraphs may be similarly applicable when the WTRU initiates random access by transmitting a random access preamble and when the WTRU switches to a new BWP.

[0115] In some aspects, a DCI may be used to both schedule data and indicate to the WTRU to perform at least one power saving technique. For example, the DCI may schedule data and indicate the k0min value to the WTRU using at least one bit in the DCI.

[0116] In some aspects, there may be at least two configurations of the DCI, and the configurations may have the same number of bits. For example, DCI format 1_1 may be configured to have N bits, and in a first configuration, m of the N bits (e.g., m=2) may be configured to indicate a bandwidth portion to the WTRU, and in a second configuration, the same m bits may be configured to indicate a value of k0min to the WTRU.

[0117] In some aspects, separate search space configurations may be used by the WTRU to interpret the content of the DCI, with at least one search space configuration being used for each DCI configuration.

[0118] The WTRU may interpret the attributes indicated by the m bits (e.g., whether they indicate a BWP or k0min index) based on the time (slot index and / or OFDM symbol index within the slot) at which the PDCCH containing the DCI is received. A search space configuration parameter configuring the monitoring slot and slot offset, and / or the monitoring symbol within the slot may be used to indicate the time. Furthermore, the WTRU may be configured with two search spaces, and each search space configuration may have the same DCI format and a separate monitoringSlotPeriodicityAndOffset parameter. For example, the WTRU may monitor a configured CORESET (e.g., CORESET#1) every p1 slot, and if a PDCCH is detected, the DCI may indicate a BWP. Furthermore, the WTRU may monitor a configured CORESET every p2 slot, and if a PDCCH is detected, the DCI may indicate a k0min.

[0119] Alternatively, the WTRU may interpret the attributes indicated by the m bits (e.g., whether they indicate a BWP or k0min index) based on which CORESET the PDCCH containing the DCI is received on. A search space configuration parameter configuring the CORESET may be used to indicate the control resource element on which the PDCCH is received. Furthermore, the WTRU may be configured with two search spaces. Each search space configuration may have the same DCI format and a different controlResourceSetId parameter. For example, the WTRU may monitor a first configured CORESET (e.g., CORESET#1), and if a PDCCH is detected, the DCI may indicate BWP. Furthermore, the WTRU may monitor a second configured CORESET (e.g., CORESET#2), and if a PDCCH is detected, the DCI may indicate k0min.

[0120] In other aspects, a combination of at least two of the monitoringSlotPeriodicityAndOffset, monitoringSymbolsWithinSlot, and controlResourceSetId search space configuration parameters may be used to interpret the content of a received DCI.

[0121] In other aspects, at least one parameter in the search space configuration may be used to interpret the content of a received DCI, where the DCI is a DCI configured in the search space. A first BWP may be configured by RRC using a TDRA table, and the k0min / k2min applicable to the TDRA table for the first BWP may be dynamically changed by L1 signaling. When a WTRU operating in the first BWP receives an indication to switch to a second BWP, the WTRU may set the k0min / k2min values ​​applicable to the TDRA table for the first BWP to the values ​​indicated in the TDRA table configured by RRC. For example, the TDRA table configured by RRC for the first BWP may include k0min=0 slot, and the k0min value may be set to 1 slot by L1 signaling. When the WTRU switches to the second BWP, the k0min applicable to the TDRA table for the first BWP may be set to the value indicated by RRC, i.e., 0 slot. In other words, all entries in the TDRA table applicable to the first BWP may be available again. When the WTRU switches back to the first BWP, all entries in the TDRA table applicable to the first BWP are available.

[0122] In aspects, the WTRU may receive or monitor a power save signal, such as the L1 signaling described with respect to FIG. 5, at predefined or predetermined time positions that may be associated with one or more PDCCH monitoring occasions. In aspects, the power save signal may be a DCI, a reference signal, and / or a preamble. In aspects, the power save signal may be PHY signaling, RRC signaling, MAC, or MAC CE. The value of k0min may be configured for each bandwidth portion (BWP). In such aspects, the applicable value may be the value of an active BWP in which the PDCCH is decoded. Further alternatives regarding the power save signal are described below regarding how the WTRU can determine radio performance conditions.

[0123] In an aspect, the radio performance state may include at least one reference sensitivity level. Additionally or alternatively, the radio performance state may include a maximum TBS, rank, modulation order, or coding rate for PDSCH decoding or PUSCH transmission, and / or a set of possible PDSCH mapping types. Additionally or alternatively, the radio performance state may include a set or maximum number of BWPs that can be operated or active BWPs. Additionally or alternatively, the radio performance state may include a maximum number or a set or subset (per BWP, CC, or WTRU), active TCI states for PDCCH, active TCI states for PDSCH, one-port or two-port NZP-CSI-RS resources (e.g., CRI / RSRP, SSBRI / RSRP) for beam management, NZP CSI-RS or SSB resources for CSI reporting, NZP CSI-RS or SSB resources for RRM measurements, periodic CSI report, semi-persistent CSI report, or aperiodic CSI report configuration, CSI reports that the WTRU can process simultaneously, TRS resource sets that the WTRU can track simultaneously, CSI-RS or SSB resources for PDCCH quality monitoring, CSI-RS / SSB resources for new beam identification, and / or RSRP values ​​for non-group-based RSRP reporting.

[0124] In aspects, the radio performance state may include a certain number, a maximum number, or a set of CORESETs, PDCCH search spaces, PDCCH candidates, PDCCH aggregation levels, DCI formats, and / or monitored PDCCH occasions within a CORESET or pattern thereof for PDCCH monitoring (per BWP, CC, or WTRU), and / or whether PDCCH repetition can be used for PDCCH monitoring. Additionally or alternatively, the radio performance state may include monitoring behavior, such as whether a particular RS or SSB is expected to be received only during active time (or while a particular DRX timer is running) or whenever they are configured to occur. Additionally or alternatively, the radio performance state may include a level of WTRU processing and / or DRX configuration, aspects of the DRX configuration, and / or parameter configurations within the DRX configuration.

[0125] In an aspect, the radio performance state may include at least one of the following RRM requirements, such as those defined in an evaluation period for radio link quality: the number of NR or inter-RAT frequency carriers that may be monitored, the number of reporting criteria that may be supported in parallel, the number of intra-frequency, inter-frequency, or inter-RAT cells that may be monitored, the latency for identifying a new detectable intra-frequency, inter-frequency, or inter-RAT cell, the measurement period, and / or the accuracy requirements for the RRM measurements. Additionally or alternatively, the radio performance state may include a set of configured PDSCH-to-HARQ feedback timing indicators (k1) that may be indicated by the DCI. A minimum value k1min of the PDSCH-to-HARQ feedback timing may be configured. In such an aspect, the WTRU may transmit HARQ feedback only if, for example, the indicated k1 value is greater than or equal to the minimum value k1min applicable to the current radio performance state. A PDSCH-to-HARQ feedback timing offset k1off may be configured. In such aspects, the WTRU may apply a PDSCH-to-HARQ feedback timing that corresponds to the sum of the indicated k1 value and k1off applicable to the radio performance conditions.

[0126] In an aspect, the radio performance state may include a set of configured time-domain relationships between the PDCCH and the PDSCH, which may be indicated by the DCI, including, for example, the number of slots (k0) between the PDCCH and the PDSCH (e.g., a cross-slot scheduling offset), a PDSCH mapping type, and a combination of starting symbol and PDSCH length. Additionally or alternatively, the radio performance state may include an offset k0off of the number of slots k0 between the PDCCH and the PDSCH (or PUSCH). The WTRU may determine that the number of slots between the PDCCH and the PDSCH corresponds to the sum of the indicated k0 value and an offset k0off applicable to the current radio performance state. The offset value k0off may depend on or be applicable only if the PDCCH is decoded at a particular time symbol of the slot or of the CORESET. For example, the value may depend on whether the PDCCH is decoded at the last three symbols or the first four symbols of the slot. The value of k0off for radio performance conditions can be signaled by RRC or MAC CE. The value of k0off can be configured for each BWP. In this case, the applicable value may be the value of the active bandwidth portion where the PDCCH is decoded.

[0127] In aspects, the radio performance conditions may include multiple RF chains, active antenna chains, RF panels, and / or diversity branches expected for reception. Additionally or alternatively, the radio performance conditions may include multiple antenna elements for MIMO and / or MIMO algorithms.

[0128] When a WTRU operates in a radio performance state that includes reduced requirements or capabilities, the power consumption of the WTRU can be improved through various implementation aspects. For example, the WTRU may be able to switch off one or more RF chains if it knows that the required sensitivity level according to the current radio performance state has been relaxed to a certain value. The WTRU may also be able to switch off certain antenna panels if the number of active TCI states is reduced.

[0129] Similarly, the WTRU may be able to switch off one or more RF chains, and possibly some baseband components, if it knows that the maximum transport block size or rank for the PDSCH will be below a certain value until at least a known point in the future. For this to be effective, the allowed latency before switching to a radio performance state corresponding to higher performance should be longer than the latency required to turn on the necessary components in an actual implementation. Such a minimum latency may be an aspect of the radio performance state (or transition between states) and may be configurable or predefined.

[0130] The WTRU receiver may implement or use one or more receiver components (or configurations, types), each of which may have its own capabilities (e.g., configurations). For example, a first receiver component may use a single RF chain, and a second receiver component may use multiple RF chains. In another example, the first receiver component may support QPSK as a maximum modulation order, and the second receiver component may support 256QAM as a maximum modulation order. The first receiver component may provide low peak throughput performance while consuming less power / energy, and the second receiver component may provide high peak throughput performance while consuming more power / energy. The first receiver component may consume less power / energy than the second receiver component.

[0131] A WTRU may use one receiver component at a time, or the WTRU may use a set or a subset of receiver components at a time. A receiver component or a set of receiver components may be configured as a WTRU receiver with specific capabilities. Hereinafter, receiver component, set of receiver components, subset of receiver components, receiver configuration, Rx configuration, Rx component, receiver type, Rx type, receiver capability, and Rx capability may be used interchangeably. RF chain, transmit and receive unit (TXRU), RF transceiver, and RF may be used interchangeably.

[0132] In an aspect, a power or performance mode may determine one or more receiver components that the WTRU may use. Each receiver component may consume separate or different levels of power or energy. For example, a receiver component (or set of receiver components) capable of consuming high power / energy may correspond to a high-power mode. A receiver component (or set of receiver components) capable of consuming low power / energy may correspond to a low-power mode. The terms low-power mode, power saving mode, and power savings mode may be used interchangeably herein. The terms high-power mode, normal power mode, and non-power saving mode may be used interchangeably herein. For another example, a receiver component or set of receiver components capable of supporting a high peak throughput may correspond to a high-performance mode. A receiver component or set of receiver components capable of supporting a low peak throughput may correspond to a low-performance mode.

[0133] In aspects, a power or performance mode may be associated with one or more transmit and / or receive (Tx / Rx) parameters. The Tx / Rx parameters may be determined or known by the WTRU. The Tx / Rx parameters may be configured, such as via signaling from the gNB. The WTRU may signal or report its supported Tx / Rx parameters to the gNB. The WTRU may signal or report its supported Tx / Rx parameters for each receiver component, set of receiver components, power mode, and / or performance mode that it supports.

[0134] In an aspect, the Tx / Rx parameter may be the number of RF chains. The first power mode may use a first number (e.g., 4) of RF chains in a cell, carrier, or BWP, and the second power mode may use a second number (e.g., 1) of RF chains in a cell, carrier, or BWP. The number of RF chains used in the WTRU receiver may be referred to as the maximum rank supported for PDSCH reception. For example, if the maximum rank supported is X (e.g., 1 or 4), then at least X (e.g., 1 or 4) RF chains may be used or active for reception, etc., in the carrier / BWP. The first power mode may support a maximum rank of 4, and the second power mode may support a maximum rank of 1.

[0135] The number of RF chains used in the WTRU receiver may be indicated, determined, or used based on the coverage level of the WTRU. A first coverage level may be associated with a first power mode, and a second coverage level may be associated with a second power mode. The coverage modes and power modes may be used interchangeably.

[0136] The supported power modes may be indicated by or reported by the WTRU, such as WTRU capabilities. For example, if the WTRU supports multiple power modes (e.g., normal and low or high, medium, and low), the WTRU may report the supported power modes to the gNB. In another example, the WTRU may report that it supports a low mode or a power saving mode. The WTRU may report capabilities associated with a power mode or coverage level (e.g., the number of RF chains or maximum rank). For example, the WTRU may report its supported capabilities for each power mode and / or coverage level that it supports. If the WTRU supports multiple power modes, the WTRU may report the supported power modes and their associated capabilities to the gNB.

[0137] In an aspect, the Tx / Rx parameter may be a receiver sensitivity level, and the receiver sensitivity level may differ based on the power mode. The WTRU may report its receiver sensitivity level based on the power mode.

[0138] In an aspect, the Tx / Rx parameter may be a maximum supported modulation order (e.g., 256QAM), and the maximum supported modulation order may be determined, indicated, or reported for each power mode as a WTRU capability. The WTRU may indicate its capability of the maximum supported modulation order for each power mode. The maximum modulation order and maximum modulation coding scheme (MCS) level may be used interchangeably herein.

[0139] In an aspect, the Tx / Rx parameter may be a maximum supported RF bandwidth (e.g., 1 GHz). The maximum supportable bandwidth may be determined, indicated, or reported for each power mode as a WTRU capability. The maximum RF bandwidth may be indicated as a maximum number of RBs supported for the PDSCH. Additionally or alternatively, the Tx / Rx parameter may be at least one of a maximum number of supported carriers (e.g., simultaneously with carrier aggregation), a maximum BWP size within a carrier (e.g., up to 275 RBs), and / or a maximum number of BWPs supported for simultaneous reception. Additionally or alternatively, the Tx / Rx parameter may be a maximum number of supported beams (or beam groups). The number of supported beams may differ based on the power mode. The number of beams may be the number of Rx beams (or indicated as the number of SRS resources needed for beam management at the WTRU).

[0140] In an aspect, the Tx / Rx parameter may be a maximum supported coupling loss (e.g., coverage level). Additionally or alternatively, the Tx / Rx parameter may be a set of subcarrier spacings supported in a given frequency band (e.g., 15 kHz, 30 kHz, 60 kHz, 120 kHz). Additionally or alternatively, the Tx / Rx parameter may be at least one of a minimum HARQ-ACK timing supported for a set of scheduling parameters and / or conditions and a minimum timeline supported for a set of aperiodic CSI reporting configurations when it is triggered. Additionally or alternatively, the Tx / Rx parameter may be at least one of a channel estimation scheme, a precoding granularity for channel estimation of DM-RS, a channel coding scheme (e.g., turbo, LDPC, polar, convolutional, RM), and / or a MIMO receiver type (e.g., MMSE, ML). Additionally or alternatively, the Tx / Rx parameter may be a sleep mode (e.g., no sleep, deep sleep, partial sleep, light sleep). A wake-up time may be determined based on the sleep mode. The wake-up time may be a time (e.g., a time required) to start receiving a downlink signal (e.g., a PDCCH). The wake-up time, warm-up time, preparation time, and activation time may be used interchangeably.

[0141] Figure 6 is a diagram of an example WTRU 600 configured with multiple receiver components that may support different power modes. In the example shown in Figure 6, the WTRU 600 includes two antennas 610 and 612, which may be communicatively coupled to receiver components 604, 606, and 608. Although Figure 6 shows two antennas and three receiver components, one of ordinary skill in the art will recognize that the aspects described herein may be applicable to a WTRU having any number of antennas and receiver components.

[0142] In the example shown in FIG. 6 , one of the receiver components 604, 606, and 608 can be used at a time based on a target power mode. The first receiver component 604 may be used only for WUS reception and may consume a first (e.g., very low) amount of power. This may be because, for example, it is only capable of detecting sequences with a correlator. The second receiver component 606 may be used for downlink signal reception, for example, with scheduling restrictions (e.g., only QPSK modulation, up to rank 1, and up to 100 PRBs). The second receiver component 606 may consume a second amount of power (e.g., low power / energy). The third or Nth receiver component 608 may be used for downlink signals, for example, without scheduling restrictions. The third or Nth receiver component 608 may consume the third or Nth power / energy (e.g., the highest power / energy of the receiver components).

[0143] The number of receiver components may be based on WTRU capabilities. The WTRU may report the number of supported receiver components as WTRU capabilities. One or more sets of receiver components may be supported, and the WTRU may indicate which sets it supports. Example sets may include a first set (Set-1) (which may include a single receiver component and may, for example, support only a normal power mode), a second set (Set-2) (which may include two receiver components and may, for example, support only WUS reception or WUS reception and a normal power mode), a third set (Set-) (which may include two receiver components and may, for example, support a lower power mode and a normal power mode), and set 4 (Set-4) (which may include three receiver components and may, for example, support all power modes).

[0144] The WTRU may report the required switching time between receiver components (e.g., the time required by the WTRU to switch from one receiver component or set of receiver components to another receiver component or set of receiver components). The switching time may depend on the current power mode and the target power mode. For example, if the current power mode is a higher power mode than the target power mode, the switching time may be shorter. Otherwise, the switching time may be longer.

[0145] A receiver component or set of receiver components may have a coverage level. Two or more receiver components or sets of receiver components may have different coverage levels. A receiver component or set of receiver components that may be used for a power mode without scheduling restrictions may support the best coverage. A receiver component or set of receiver components that may be used for WUS reception only may support a coverage level similar to that of a normal power mode. A receiver component or set of receiver components that may be used for a power mode with scheduling restrictions may support lower or worst coverage, such as lower coverage than a receiver component or set of receiver components for a normal power mode without scheduling restrictions and / or for WUS reception, such as WUS reception only.

[0146] In an aspect, a WTRU may use one or more receiver components. The WTRU may determine a receiver component or a set of receiver components to use for receiving downlink signals. Which receiver component or set of receiver components to use for receiving downlink signals may be indicated to the WTRU (e.g., directly or indirectly). Furthermore, a set of scheduling restriction parameters (SRPs) may be configured or provided, such as by the gNB. The WTRU may determine which receiver component or set of receiver components to use based on the configured or provided SRPs. The scheduling restriction parameters (SRPs) may include one or more of a maximum rank (e.g., for PDSCH and / or PUSCH), a maximum modulation order (e.g., QPSK, 16QAM, 256QAM), a maximum TBS, a candidate transmission scheme (e.g., single TRP or multipoint TRP), a minimum or minimum coding rate, a maximum number of RBs, a minimum and / or maximum HARQ timeline, and / or a maximum timing advance (TA) value.

[0147] One or more search spaces or CORESETs may be configured, and each search space may be associated with a set of SRPs. For example, each search space ID (SearchSpaceID) may be associated with a set of SRPs. The WTRU may determine which receiver component, set of receiver components, or power mode to use based on the search space that the WTRU monitors. The DCI field in the DCI monitored for a search space may be determined based on the associated set of SRPs. One or more search spaces with different sets of SRPs may not be monitored simultaneously (e.g., in the same slot or the same time window). The WTRU may monitor a subset of the search space in a lower or higher power mode and skip monitoring the rest of the search space if one or more search spaces overlap in the same time window. If one or more search spaces with different sets of SRPs overlap in a time window (e.g., in the same slot), the WTRU may use a receiver component that is capable of receiving all of the search spaces in that time window. The terms search space and CORESET may be used interchangeably herein. One or more PDCCH candidates may be used, and each PDCCH candidate may be associated with a set of SRPs. The WTRU may determine a receiver component, a set of receiver components, or a power mode based on the PDCCH candidate from which it receives DCI.

[0148] The WTRU may determine a receiver component, set of components, or power mode to use based on the WTRU RRC connection status (e.g., RRC connected state, RRC idle state, and RRC inactive state). A first receiver component, set of receiver components, or power mode (e.g., low power mode) may be used when the WTRU is in the RRC idle state or the RRC inactive state. A second receiver component, set of receiver components, or power mode (e.g., high power mode) may be used when the WTRU is in the RRC connected state. The WTRU may use the first receiver component, set of receiver components, or power mode for the RRC idle state and the RRC inactive state. The WTRU may use either the first or second receiver component, set of receiver components, or power mode in the RRC connected state based on the determined set of SRPs.

[0149] The WTRU may determine which receiver component, set of components, or power mode to use based on the downlink channel type (e.g., PDCCH, PDSCH, SS / PBCH block). Additionally or alternatively, the WTRU may determine which receiver component, set of components, or power mode to use (e.g., in a BWP) based on the identity of the bandwidth portion (e.g., the BWP-id of the active BWP).

[0150] A set of SRPs may be configured for each BWP, and the WTRU may determine a receiver component, set of components, or power mode based on the associated set of SRPs in the active BWP. A first BWP may be associated with a subset of modulation orders (e.g., up to QPSK), and a second BWP may be associated with a second subset or the full set of modulation orders (e.g., up to 64QAM or 256QAM). Based on the set of modulation orders associated with the BWP, the WTRU may, for example, determine a receiver component, set of receiver components, or power mode to use when operating (e.g., receiving) in the BWP. An associated set of modulation orders (or a maximum modulation order) may be configured in each BWP configuration.

[0151] The CQI table for CSI reporting may be determined based on the BWP (or BWP-id of the active BWP) and / or the associated set of modulation orders (or the maximum modulation order). The number of entries for MCS indication for PDSCH scheduling may be determined based on the BWP (or BWP-id of the active BWP) and / or the associated set of modulation orders (or the maximum modulation order). The number of MCS bits in DCI for PDSCH scheduling may be determined based on the BWP-ID of the active BWP. The maximum modulation order may be limited for downlink or uplink only.

[0152] A first BWP switching time or gap may be used when an active BWP is switched between BWPs having the same set of SRPs, and a second BWP switching time (or gap) may be used when an active BWP is switched between BWPs having different sets of SRPs. A longer switching time (or gap) may be required or used when the receiver components, sets of receiver components, or power modes differ between the BWPs.

[0153] The WTRU may determine which receiver component, set of components, or power mode to use based on one or more of the carrier index (e.g., serving cell ID), frequency range (e.g., frequency range 1 or frequency range 2), traffic type (e.g., eMBB, mMTC, or URLLC), and / or QoS type (e.g., latency level, reliability level, required throughput level).

[0154] The WTRU may determine which receiver component, set of components, or power mode to use based on the coverage level. The receiver component, set of receiver components, or power mode may be determined based on the PDCCH aggregation level at which the WTRU received DCI. The receiver component, set of receiver components, or power mode may be determined based on one or more downlink measurements (e.g., CQI, SINR, L1-RSRP, RSRP, or RSRQ). The WTRU may monitor DCI, which may be associated with the determined receiver component, set of receiver components, or power mode.

[0155] FIG. 7 is a system diagram 700 illustrating an example use of a low power mode receiver in a separate coverage scenario. If a WTRU, such as WTRUs 710 and 712, is at the cell edge, the WTRU may not be able to receive modulation orders higher than QPSK, for example, due to poor channel conditions. If the WTRU uses a receiver component that supports only modulation orders up to QPSK, or if the gNB allows the WTRU to use that receiver component, the WTRU may be able to save battery. That receiver component may consume less power during PDCCH and PDSCH reception compared to a receiver component that supports higher modulation orders. A WTRU 708 that is not at the cell edge may operate in a different, higher power mode that supports up to 256QAM.

[0156] The WTRU may receive, such as from a gNB, a configuration or indication to use a receiver component, a set of receiver components, or a power mode that is capable of supporting a restricted maximum modulation order and / or one or more other scheduling restrictions. Alternatively, the WTRU may receive a configuration or indication of a maximum modulation order that may be scheduled or used, and / or one or more other scheduling restrictions. The WTRU may assume that a modulation order to be scheduled for a downlink channel, such as a PDCCH or PDSCH, may not be higher than the restricted maximum modulation order (e.g., QPSK). Based on the determined maximum modulation order used for the receiver component, a maximum transmission rank may be determined. Based on the determined maximum modulation used for the receiver component, a maximum transmission bandwidth may be determined.

[0157] The gNB may switch from a low power mode (e.g., up to QPSK) to a high power mode or vice versa with a dynamic indication (e.g., implicitly by search space activation or explicitly by DCI indication) along with a switching time. A switching time, such as a receiver component switching time, may be provided and / or used when the maximum modulation order for downlink scheduling is increased or decreased. The switching time may be the same as the switching time for BWP switching. The WTRU may skip monitoring the PDCCH during the switching time.

[0158] In some aspects, some radio performance aspects, such as those described above, may be independently configured and / or activated. For example, a first type of radio performance state may be defined with respect to RF aspects including, e.g., a reference sensitivity level and a number of RF chains, a second type of radio performance state may be configured with respect to baseband aspects including, e.g., a maximum transport block size, and a third type of radio performance state may be defined with respect to RRM aspects. In another example, a first type of radio performance state may be defined with respect to PDCCH decoding aspects and a second type of radio performance state may be defined with respect to PDSCH decoding aspects.

[0159] In an aspect, a radio performance state can be configured (e.g., by RRC) by configuring a set of values ​​for at least one applicable aspect. For example, an RRC configuration can include a list of radio performance states, each of which includes a maximum transport block size, a maximum rank, a receiver sensitivity value, and other information elements for the applicable aspect. Furthermore, for each radio performance state, an identity parameter can be configured. The identity parameters can be allocated such that, for example, higher values ​​may correspond to higher requirements.

[0160] In an aspect, a default radio performance state may be defined. Such a radio performance state may correspond to a set of capabilities (e.g., maximum performance or capabilities) of the WTRU provided to higher layers. Such a default radio performance may not require further configuration by the RRC. Alternatively, the default radio performance state may correspond to a power-efficient state.

[0161] A set of applicable radio performance states can be added to the configuration of the applicable aspect. For example, the configuration of a TCI state can include at least one further information element indicating one or more radio performance states in which this TCI state can be active. This indication can be provided with an information element indicating the maximum identity parameters of the applicable radio performance states. In the case where only two radio performance states are defined, the information element can be a Boolean value indicating whether the TCI state can be activated in the radio performance state corresponding to the power-efficient state.

[0162] Further information elements may be defined for the configuration of specific aspects when in a particular radio performance state. For example, an information element may be used that configures the CSI reporting configuration when in a non-default (power-efficient) radio performance state. This may be particularly useful when a large number of parameters are affected and only two performance states (e.g., the default state and the power-efficient state) are defined.

[0163] The WTRU may determine the applicable radio performance state based on at least one of a number of different methods. In some aspects, the radio performance state may be explicitly indicated by physical layer, MAC, or RRC signaling. For example, the WTRU may receive a MAC control element indicating values ​​related to the radio performance state or applicable aspects. The WTRU may activate the necessary components so that it is ready to operate using the indicated state by a predefined number of slots or symbols (or ms) following the transmission of a HARQ that confirms reception of the corresponding transport block.

[0164] For example, in some aspects, a minimum cross-slot scheduling delay (min k0 or min k2) may be indicated by a DCI field such as a time domain resource allocation (TDRA) field. For example, a minimum k0 or k2 value may be configured for each codepoint in this field in addition to existing parameters such as k0, mapping type, start symbol, and length. In cases where the minimum k0 (or k2) value indicated by this field differs from the value currently used by the WTRU, the WTRU may modify the minimum k0 (or k2) value accordingly. In addition, the WTRU may determine that a PDSCH (or PUSCH) is not received or transmitted. This may be applicable only if the indicated minimum value of k0 (or k2) is lower than the current value. To improve robustness, the WTRU may determine that a change in minimum k0 (or k2) is valid on the condition that at least one other field of the DCI is set to a predefined value. For example, the frequency domain resource allocation field may have to be set to a predefined value. The WTRU may acknowledge receipt of the signaling, for example, by sending a HARQ-ACK for the corresponding DCI over the resource indicated by the PUCCH resource indicator.

[0165] In some aspects, a radio performance state may be implicitly switched or activated when the WTRU receives an activation command for the associated aspect. For example, a TCI state may be configured to be applicable to a non-default radio performance state, such as one corresponding to a higher reference sensitivity or a smaller number of RF chains. Upon receiving a MAC CE indicating activation of this TCI state for PDCCH reception, the WTRU may operate according to the corresponding non-default radio performance state.

[0166] In some aspects, the radio performance state may be determined based on at least one WTRU measurement, such as an RRM measurement, or a CSI measurement, such as an L1-RSRP. For example, the WTRU may activate a default radio performance state if the RSRP of its serving cell is lower than a threshold. Such a threshold may be signaled by MAC or RRC. Conversely, the WTRU may activate a non-default radio performance state if the RSRP of its serving cell is higher than a threshold. The WTRU may signal such a switch in radio performance state using MAC or RRC signaling.

[0167] In some aspects, the WTRU may switch to a radio performance state, such as a radio performance state that allows for maximum performance, after decoding a PDCCH that includes a DL allocation or UL grant for this WTRU. Additionally or alternatively, in some aspects, the WTRU may be configured with a radio performance state timer of a particular duration. The WTRU may start or restart the radio performance timer upon decoding a PDCCH that includes a DL allocation or UL grant for this WTRU. When the timer expires, the WTRU may switch to a power-efficient radio performance state.

[0168] In some aspects, the radio performance state may be determined based on whether at least one DRX timer is running or based on receipt of a DRX MAC CE. For example, the WTRU may switch to a default radio performance state when the inactivity timer starts, and may switch to a non-default radio performance state when the inactivity timer, the UL or DL ​​retransmission timer, and the UL and DL HARQ RTT timers expire. In another example, the WTRU may switch to a non-default radio performance state after receiving a DRX command MAC CE or a long DRX command MAC CE.

[0169] In some aspects, a radio performance state may be configured to be associated with a BWP. Upon switching to a new BWP, the WTRU may also switch to the associated radio performance state. For example, a power-efficient radio performance state may be configured to be associated with a bandwidth portion having a relatively narrow bandwidth, and a radio performance state that allows for maximum performance may be configured to be associated with a bandwidth portion having a relatively wide bandwidth.

[0170] In some aspects, a radio performance state may be associated with a configured grant or allocation, into which the WTRU may switch upon transmission or reception of the configured grant or allocation.

[0171] FIG. 8 is a diagram 800 of an example of switching between two radio performance states. In the example shown in FIG. 8, a WTRU may switch between two radio performance states: a first radio performance state requiring the use of four Rx chains, and a second radio performance state requiring the use of only two Rx chains. In the example shown in FIG. 8, the WTRU may be triggered to switch to the first radio performance state by WTRU scheduling (e.g., receipt of a DL allocation or UL grant). The WTRU may be triggered to switch to the second radio performance state by expiration of a timer. For example, in (a), the WTRU may disable four Rx, use only two Rx, and attempt to detect a valid PDCCH. In (b), the WTRU may be scheduled, start a timer, and enable or re-enable four Rx processing. When the timer expires, the WTRU may stop monitoring. In (c), the WTRU returns to the two Rx's and attempts to detect a valid PDCCH.

[0172] In some aspects, the radio performance state can be determined (e.g., implicitly) based on scheduling information or properties of the decoded PDCCH. This approach can have the advantage of avoiding the need for additional DCI formats to switch between states. For example, the scheduling information can include timing information such as the number of slots (e.g., k0 or k2) between the PDCCH and the PDSCH (or PUSCH), or the duration of the PDSCH or PUSCH. For example, a WTRU in a first state can switch to a second state if the indicated number of slots k0 is lower than a first configured threshold, or corresponds to a configured value or code point. The above first threshold can correspond to the minimum number of slots k0min configured for the first state. A WTRU in a second state can switch to the first state if the indicated number of slots k0 is higher than a second configured threshold, or if the indicated number of slots k0 corresponds to a specific value or code point.

[0173] For example, as part of the performance state behavior, a WTRU that receives data scheduling DCI providing k0min (or k2min) and including or indicating k0 < k0min (or k2 < k2min) can set a new value of k0min (or k2min) to the received k0 (or k2), or it can set the value of k0min (or k2min) to a default value such as a zero slot.

[0174] There may be a time gap between when a scheduling DCI is received that implicitly indicates a new value for k0min (k2min) and when this information becomes available to the WTRU. This delay may be due to various receive operations, such as decoding and demodulation. In aspects, the WTRU may not have buffered any potential PDSCH during the time gap following the PDCCH, and data on the PDSCH may have been lost. In some aspects, instead of feeding back a NACK for the lost data, the WTRU may not be expected to send any acknowledgement feedback even if PUCCH resources are provided in the DCI. In other aspects, the DCI may indicate non-transmission of an ACK / NACK, such as by setting the PUCCH resource field (or another predetermined field) to a known value. These methods may generally be applicable when the WTRU performance state is implicitly switched to another performance state and a temporary loss of data occurs during the switch.

[0175] Scheduling information may include, additionally or alternatively, timing information such as a grant (DL or UL grant) that triggers an aperiodic reference signal (e.g., CSI-RS or SRS), and the number of slots (denoted as X) between the reception and / or transmission of the aperiodic reference signal. For example, a WTRU in a first state may be able to switch to a second state if the indicated number of slots is lower than a configured first threshold, or corresponds to a configured value or code point. A WTRU in a second state may be able to switch to the first state if the indicated number of slots is higher than a configured second threshold, or corresponds to a configured value or code point. As part of the performance state behavior, a WTRU that receives data scheduling DCI with Xmin provided and X < Xmin may be able to set a new value of Xmin to the received X. Alternatively, it may be able to set the value of Xmin to a default value such as zero slots. This may similarly apply to other possible parameters such as the SRS triggering offset.

[0176] The scheduling information may additionally or alternatively include a frequency allocation, such as a number of RBs, a set of RBs, or a bandwidth portion. For example, a WTRU in a first state may switch to a second state if the indicated number of RBs is higher than a configured threshold or if the indicated set of RBs includes RBs outside the configured subset of RBs for the first state. Additionally or alternatively, the scheduling information may include information on whether PDSCH or PUSCH resources in time or frequency overlap with resources of a configured allocation or grant or resources indicated by another grant or allocation. Additionally or alternatively, the scheduling information may include a BWP indication. For example, the WTRU may switch to a radio performance state configured for the indicated bandwidth portion (if different from the active bandwidth portion).

[0177] In an aspect, the scheduling information may additionally or alternatively include an MCS or an MCS table. For example, a WTRU in a first state may switch to a second state if the indicated MCS is above a configured MCS threshold or if the indicated MCS table is not part of the set of possible MCS tables configured for the first state. Additionally or alternatively, the scheduling information may include a number of layers (rank). For example, a WTRU in a first state may switch to a second state if the indicated number of layers is above a configured threshold. Additionally or alternatively, the scheduling information may include a TBS. For example, a WTRU in a first state may switch to a second state if the transport block size determined from the DCI is above a configured threshold.

[0178] In an aspect, the scheduling information may additionally or alternatively include PDSCH-to-HARQ feedback timing. For example, a WTRU in a first state may switch to a second state if the indicated PDSCH-to-HARQ feedback latency is lower than a threshold. Such a threshold may correspond to a minimum value of k1 configured for the first state. Additionally or alternatively, the scheduling information may include a transmission configuration indication (TCI). For example, a WTRU in the first state may switch to a second state if the indicated TCI is not part of the set of possible TCIs configured for the first state. Additionally or alternatively, the scheduling information may include information regarding scheduling on a supplemental uplink (SUL) or a normal UL (NUL). For example, a WTRU in the first state may switch to a second state if a PUSCH is scheduled on the SUL. For example, the second state may correspond to a radio performance state with a lower reference sensitivity level or a larger number of antennas.

[0179] In an aspect, the scheduling information may additionally or alternatively include an indication of a transmission profile that may indicate a priority associated with a transmission, such as for prioritization between eMBB and URLLC services. For example, a WTRU in a first state may switch to a second state if the indicated transmission profile is not part of the set of possible transmission profiles configured for the first state. Additionally or alternatively, the scheduling information may include information regarding logical channels whose data is included in a transport block. For example, a WTRU in a first state may switch to a second state if the transport block includes data from a logical channel that is not part of the set of possible logical channels configured for the first state. Such a configuration may be implicit from logical channel prioritization (LCP) restrictions configured for the logical channels. For example, the configuration may implicitly include any logical channels subject to a maximum PUSCH duration restriction whose duration may be lower than a threshold, or logical channels subject to a cell restriction, or logical channels mapped to a bearer for which duplication is configured or activated.

[0180] In some aspects, the scheduling information may additionally or alternatively include a PDSCH mapping type. For example, a WTRU in a first state may switch to a second state if the indicated PDSCH mapping type is not part of the subset of mapping types configured for the first state. Additionally or alternatively, the scheduling information may include a Radio Network Temporary Identifier (RNTI) used to decode the PDCCH. For example, a WTRU in a first state may switch to a second state if the indicated RNTI is not part of the subset of RNTIs configured for the first state.

[0181] In an aspect, a PDCCH-based WUS may be transmitted to a WTRU before the DRX ON duration to wake up the WTRU, so that it can start monitoring the PDCCH during the ON duration. The search space, CORESET, and monitoring period for monitoring during the ON duration may be indicated by the RNTI of the WUS. For example, for a first RNTI, the WTRU may monitor a first set of search spaces, and for a second RNTI, the WTRU may monitor a second set of search spaces. The association between the RNTI and the associated search space may be configured by the gNB.

[0182] In other aspects, the CRC bits that are not scrambled with the RNTI may be scrambled with an R-ID, and the R-ID may be associated with a search space, CORESET, or set of monitoring periods, for example, to monitor during the ON duration. For example, if the WTRU detects a first R-ID, it may be expected to monitor the associated search space. The association between the R-ID and the associated search space may be configured by the gNB. In other aspects, the R-ID may be the exact ID of the search space to be monitored during the ON duration, or it may be derived from a search space that is associated with a known relationship.

[0183] In an aspect, the scheduling information may additionally or alternatively include a DCI format. For example, a WTRU in a first state may switch to a second state upon receiving a preemption indication (format 2_1) or a TPC command (format 2_2). Additionally or alternatively, the scheduling information may include properties of a decoded PDCCH, such as a CORESET, a search space, or timing. For example, a WTRU in a first state may switch to a second state upon receiving a DCI in a particular configured search space or depending on whether the search space is a common search space or a dedicated search space. Additionally or alternatively, the scheduling information may be based on successful decoding of a PDCCH that schedules a particular type of transmission. For example, a WTRU may monitor and detect a PDCCH in a first power state and switch to a second power state if it is scheduled for semi-persistent data transmission. For example, a WTRU may monitor the PDCCH using a fewer number of RF chains, and when it receives and decodes a scheduling PDCCH, it may switch to a greater number of RF chains if it is scheduled with semi-persistent data. In an aspect, the scheduling information may additionally or alternatively include the number of allocations, grants, and / or DCIs received within a time period. For example, a WTRU in a first state may switch to a second state if such number exceeds a configured threshold within a configured time period applicable to the second state.

[0184] Similar to the example shown in Figure 8, for any of the above possible scheduling-based triggers, a timer may be started or restarted when the conditions that would lead to the decision to use the second state are met. When the timer expires, the WTRU may switch back to the first state.

[0185] As an alternative to the aspect shown in FIG. 8, in some aspects, one or more DRX cycles and / or configurations may be configured and used by the WTRU. Each DRX cycle or configuration may be associated with a power mode. As described above, the power modes may be predetermined, configured, defined, and / or used by the gNB and / or the WTRU. The power modes may have one or more attributes, e.g., power, energy budget, and / or transmit RF chain, for use, activation, or deactivation. In some aspects, the power modes may be activated or deactivated based on information provided by the WTRU, which may include, for example, coverage level, channel state information, battery level, and / or WTRU capability (e.g., to support multiple RF chains or to turn one or more RF chains on / off). FIGS. 9, 10, and 11 and corresponding description provide examples of various ways of using DRX cycles to implement various power modes.

[0186] FIG. 9 is a signal diagram 900 of an example of multiple DRX configurations based on power modes. In the example shown in FIG. 9, two DRX cycles 902 and 904 are configured. The second DRX cycle 904 may be longer than the first DRX cycle 902. The first DRX cycle 902 may be associated with a low power or power saving mode, and the second DRX cycle 904 may be associated with a high power or normal power mode. During the ON duration 906 of the first DRX cycle, the WTRU may operate in a low power mode. For example, the WTRU may turn on only a portion of its circuitry (e.g., a subset of RF chains), or it may turn off or not use at least some of its circuitry. During the ON durations 908a, 908b, the WTRU may operate in a normal power mode. For example, it may turn on and / or use all of its RF chains or a larger subset of those RF chains than for the first DRX cycle 902. As shown in FIG. 9, the second DRX cycle 904 is longer than the first DRX cycle 902, so the second DRX cycle 904 may include multiple ON durations 908a, 908b.

[0187] If one or more DRX configurations are used, at least one DRX parameter may differ for each DRX configuration. The use of a DRX cycle may correspond to monitoring or not monitoring the PDCCH based on the DRX cycle. For example, the use of a DRX cycle may correspond to monitoring or not monitoring the PDCCH based on at least one parameter, time, duration, timer, or aspect of the DRX cycle or configuration, such as ON duration, ON duration timer, active time, and OFF duration, OFF duration timer, and retransmissions.

[0188] The WTRU may use one DRX configuration (or DRX cycle) at a time. Alternatively, the WTRU may use one or more DRX configurations (or DRX cycles) simultaneously. Each DRX configuration may be associated with a power mode. For example, a high power mode may be associated with a first Rx configuration (e.g., a larger number of RF chains or a larger number of activated or used RF chains), and a low or lower power mode may be associated with a second Rx configuration (e.g., a smaller number of RF chains or a smaller number of activated or used RF chains).

[0189] The PDCCH transmitted by the gNB and / or received by the WTRU may be associated with a power mode or may carry associated power mode information, which may indicate the power mode.

[0190] The PDCCH, which may be associated with a power mode, may be monitored or received during the ON duration of the corresponding DRX cycle, which may be associated with the power mode.

[0191] One or more parameters or aspects of the PDDCH channel or of the PDCCH monitoring may be based on the power mode being used when the PDCCH is monitored. The WTRU may determine and / or use parameters or aspects of the PDCCH channel or of the PDCCH monitoring based on the power mode being used by the WTRU when the WTRU monitors the PDCCH. The parameters or aspects may be at least one of an aggregation level, a set of aggregation levels, and / or a REG bundle size.

[0192] For example, one or more higher levels of aggregation may be required and / or used to monitor the PDCCH for low power or power saving modes, e.g., due to coverage loss when fewer RF chains are used. In another example, a larger REG bundle size may be required and / or used to monitor the PDCCH for low power or power saving modes.

[0193] In an aspect, a first set of aggregation levels may be used to monitor the PDCCH during an ON duration or active time associated with a first DRX cycle. A second set of aggregation levels may be used to monitor the PDCCH during an ON duration or active time associated with a second DRX cycle. In an example, the first set of aggregation levels may include smaller aggregation levels, and the second set of aggregation levels may include larger aggregation levels. In another example, the second set of aggregation levels may include at least one aggregation level greater than the aggregation levels (e.g., all aggregation levels) in the first set of aggregation levels. In an aspect, a first REG bundle size may be used to monitor the PDCCH during an ON duration associated with a high power mode, and a second REG bundle size may be used to monitor the PDCCH during an ON duration associated with a low power mode.

[0194] If the WTRU receives a PDCCH while in an ON duration or active time, the WTRU may operate in a power mode to receive data on a PDSCH, for example, that may be scheduled or permitted by that PDCCH. For example, if a PDCCH is detected during the ON duration or active time of a particular DRX cycle, the WTRU may remain in that particular power mode while receiving the associated PDSCH and / or user data. After a PDCCH is detected during the ON duration or active time, the WTRU may start a timer and may monitor or continue to monitor the PDCCH, for example, until the timer expires. During this monitoring, the power mode associated with the detected PDCCH, ON duration, or active time may be used.

[0195] One or more parameters or aspects of the PDSCH channel or PDSCH transmission or reception may be based on, for example, the power mode when the associated PDCCH is monitored. The WTRU may determine and / or use parameters or aspects of the PDSCH channel or PDSCH transmission or reception based on, for example, the power mode being used by the WTRU when the WTRU monitors the associated PDCCH. The parameters or aspects may be at least one of a rank, a maximum rank, a DM-RS parameter such as DM-RS density, an MCS level, and / or a maximum MCS level.

[0196] The maximum rank for PDSCH reception may be determined or limited by the power mode associated with the PDSCH or associated with the PDCCH that scheduled the PDSCH. The power mode associated with the PDCCH may be the power mode associated with the DRX cycle, ON duration, and / or active time in which the PDCCH was detected. The rank may be used interchangeably with the number of layers, data streams, spatial layers, and data symbols transmitted simultaneously at the same time / frequency. A first maximum rank (e.g., 4) may be used when the WTRU monitors the PDCCH or receives DCI during the ON duration or active time associated with the first power mode, and a second maximum rank (e.g., 1) may be used when the WTRU monitors the PDCCH during the ON duration or active time associated with the second power mode. The nth maximum rank may be used for reception of the PDSCH scheduled by the PDCCH during the ON duration or active time associated with the nth power mode. A lower maximum rank may be used for a lower power mode. For example, a lower maximum rank may be used for the power saving mode than for the normal mode.

[0197] The DM-RS density for PDSCH reception may be determined based on a power mode associated with the PDSCH. A first DM-RS density for or with the PDSCH may be used when the WTRU monitors one or more PDCCHs or receives DCI for the PDSCH in a DRX cycle, ON duration, or active time associated with a first power mode. A second DM-RS density for or with the PDSCH may be used when the WTRU monitors one or more PDCCHs or receives DCI for the PDSCH in a DRX cycle, ON duration, or active time associated with a second power mode. The DM-RS density for or with the PDSCH may be based on or correspond to the number of DM-RS symbols used in a slot. For example, a first DM-RS density may use a first number of DM-RS symbols (e.g., four DM-RS symbols) in a slot for the PDSCH, and a second DM-RS density may use a second number of DM-RS symbols (e.g., two DM-RS symbols) in a slot for the PDSCH.

[0198] The maximum MCS level may be determined based on a power mode associated with the PDSCH. A first maximum MCS level (e.g., 256QAM) may be used when the WTRU monitors one or more PDCCHs or receives DCI for the PDSCH in a DRX cycle, ON duration, or active time associated with a first power mode. A second maximum MCS level (e.g., QPSK) may be used when the WTRU monitors one or more PDCCHs or receives DCI for the PDSCH in a DRX cycle, ON duration, or active time associated with a second power mode.

[0199] The low power mode may be a power saving mode. The high power mode may be a normal mode or a non-power saving mode. Active time may be used instead of ON duration in aspects and examples described herein and still be consistent with the present disclosure. ON duration or active time may be associated with a DRX cycle and / or a power mode.

[0200] As used herein, ON duration or active time may be replaced by duration, PDCCH monitoring occasion, and / or search space for PDCCH monitoring. The ON duration or active time may include one or more PDCCH monitoring occasions. The ON duration and / or active time may include one or more search spaces, for example, for monitoring the PDCCH. The WTRU may monitor the PDCCH at or during a PDCCH monitoring occasion. PDCCH occasion and PDCCH monitoring occasion may be used interchangeably herein.

[0201] FIG. 10 is a signal diagram 1000 of an example of power mode switching between ON durations in separate DRX cycles. In the example shown in FIG. 10, a WTRU may monitor a PDCCH during an ON duration 1002a of a DRX cycle or during a PDCCH monitoring occasion using an associated power mode. If a PDCCH is detected 1004 during the ON duration 1002a, the WTRU may operate or continue operating 1006 in the same power mode, which may include, for example, at least one of monitoring the PDCCH, receiving a PDSCH, and transmitting a PUSCH. The WTRU may receive an indication to change power modes. The indication may be received during the current ON duration and / or before the next ON duration 1002b. The message may be sent in DCI on the PDCCH or as a MAC CE or other format. The WTRU may switch 1008 the power mode based on the received indication. The WTRU may perform or apply the switch at the beginning of an ON duration, such as the next ON duration 1002b, or k (or at least k) PDCCH monitoring occasions after the switch indication is received. The WTRU may then continue data reception (1110) during the ON duration 1002b.

[0202] In an aspect, the WTRU may determine a receiver component, a set of receiver components, or a power mode based on a timer. For example, the WTRU may use a first receiver component, a set of receiver components, or a power mode to monitor the PDCCH for an ON duration or active time when the timer is running. When the timer expires, the WTRU may switch to a second or fallback receiver component, a set of receiver components, or a power mode. The second or fallback receiver component, a set of receiver components, or a power mode may have better coverage than the first receiver component, a set of receiver components, or a power mode. If the first receiver component, a set of receiver components, or a power mode is already a fallback receiver component, a set of receiver components, or a power mode, the inactivity timer may be stopped or reset.

[0203] The first receiver component, set of receiver components, or power mode may keep a first number of RF chains active. The fallback receiver component, set of receiver components, or power mode may keep a second number of RF chains active, where the first number may be smaller than the second number. The second number may be a larger or maximum number that can be supported by the WTRU based on WTRU capabilities. The fallback receiver component, set of receiver components, or power mode may support a maximum modulation order that may be higher than the maximum modulation order supported by the first receiver component, set of receiver components, or power mode. The fallback receiver component, set of receiver components, or power mode may support the highest maximum modulation order that the WTRU can support based on WTRU capabilities.

[0204] In an aspect, WUS may be used together with DRX to save power. By way of example, WUS may precede the ON duration of a DRX cycle. If WUS is detected, the WTRU may monitor one or more PDCCHs during the ON duration or active time, e.g., in one or more PDCCH occasions or monitoring occasions.

[0205] In aspects, a WTRU may determine a receiver component, a set of receiver components, or a power mode for monitoring the PDCCH during the ON duration or active time based on an associated WUS. The associated WUS may indicate which receiver component, set of receiver components, or power mode to use. For example, one or more WUS may be used, and if the WTRU receives a first WUS, the WTRU may use or turn on a first receiver component, set of receiver components, or power mode. If the WTRU receives a second WUS, the WTRU may use or turn on a second receiver component, set of receiver components, or power mode.

[0206] The one or more WUSs may be based on preambles, and the WTRU may blindly detect the preambles. If a first preamble is detected, the WTRU may use a first receiver component, set of receiver components, or power mode, and if a second preamble is detected, the WTRU may use a second receiver component, set of receiver components, or power mode.

[0207] 11 is a signal diagram 1100 of an example WUS that determines the power mode of an associated PDCCH monitoring occasion and the set of aggregation levels for PDCCH monitoring. In the example shown in FIG. 11, the WUS may indicate the number of RF chains to turn on or the power mode to use. For example, a WUS 1102 may be used to wake up a WTRU in a first power mode, and a second WUS 1104 may be used to wake up a WTRU in a second power mode.

[0208] The set of aggregation levels to be monitored in a particular search space may be determined based on the power mode indicated by the WUS. For example, the search space may be configured with one or more sets of aggregation levels. Each set of aggregation levels may be associated with a power mode. Based on the indicated power mode, the WTRU may determine a set of aggregation levels for PDCCH monitoring in the search space. For the first power mode, a larger aggregation level may be used, e.g., larger than for the second power mode. The larger level may be used, e.g., for a low power mode, because receiver capacity may be limited, e.g., due to use of less active RF chains. For the second power mode, a smaller aggregation level (e.g., a smaller maximum aggregation level) may be used, because, e.g., full receiver capacity may be supported.

[0209] In other aspects, the WUS may determine, for example, an associated ON duration, active time, or a first receiver component, set of receiver components, or power mode for PDCCH monitoring during one or more associated PDCCH monitoring occasions or PDCCH occasions. The WTRU may detect or receive a PDCCH, for example, during the associated ON duration, active time, or PDCCH monitoring occasion. The PDCCH may indicate a second receiver component, set of receiver components, or power mode to use for associated PDSCH reception.

[0210] The first receiver component, set of receiver components, or power mode and the second receiver component, set of receiver components, or power mode may be the same, for example, when the first receiver component, set of receiver components, or power mode is a high power mode or a normal power mode. In an aspect, the WUS may include a sequence or a combination of two or more sequences. When two or more sequences are used, at least one of scrambling the sequences, time division multiplexing the sequences, and frequency division multiplexing the sequences may be used to generate the WUS. At least one of the constituent sequences of the WUS may indicate a power mode. For example, when two sequences are scrambled to generate the WUS, one of the sequences may indicate a power mode.

[0211] In some aspects, the radio performance state may be implicitly determined when the WTRU receives downlink control information indicating a DL allocation or UL grant that cannot be complied with by the WTRU based on current radio performance conditions or capabilities. For example, upon receiving a DCI indicating a change in the active bandwidth portion (e.g., the indicated BWP index is different from the active BWP), the WTRU may switch to the configured radio performance state if the DCI indicates a PDSCH or PUSCH starting before the end of the allowed switching gap. For another example, the radio performance state may be implicitly determined upon receiving a DCI with a carrier indicator field that does not correspond to any configured carrier. In this case, the value of the field may be mapped to an index of the radio performance state. For another example, the radio performance state may be implicitly determined upon receiving an allocation or grant with a codepoint that corresponds to a reserved or invalid value (e.g., for the antenna port field). For another example, the radio performance state may be implicitly determined upon receiving an allocation or grant with invalid HARQ information, such as when receiving a HARQ process index that is greater than the configured number of HARQ processes. For another example, radio performance conditions may be implicitly determined upon receiving an allocation or grant that indicates invalid resources.

[0212] If the radio performance state is determined based on one of the above examples, the WTRU may switch to a default radio performance state regardless of the content of the DCI, or the WTRU may switch to a radio performance state indicated by one or more values ​​of at least one field.

[0213] In some aspects, the performance state of the WTRU may be inconsistent with the information carried in the data scheduling DCI, resulting in a mismatch. Such a mismatch may occur, for example, if the WTRU misses signaling that determines the performance state. For example, in some aspects, the WTRU may be configured to deactivate specific entries in the TDRA table. For example, entries with k0 (k2) below a threshold k0 (k2) may be deactivated. In this context, deactivation may mean that the WTRU does not expect to be scheduled with the deactivated entry. k0 (k2) may be assumed to be provided to the WTRU via L1, L2, or higher layer signaling. Similarly, the WTRU may be configured to deactivate specific entries in the CSI reporting trigger state list. For example, entries with X below a threshold X (X is the aperiodic CSI-RS triggering offset) may be deactivated. In this context, deactivation may mean that the WTRU will not expect to receive the CSI-RS corresponding to the deactivated entry.

[0214] If the WTRU is expected to be scheduled, for example, with k0(k2)>0 slots and X>0 slots, it can enter the micro-sleep mode as soon as the PDCCH in the current slot is received if it has not been scheduled to perform any other operation by the PDCCH of the previous slot. If the WTRU is configured with k0min but receives data scheduling DCI indicating k0 (where k0 < k0min in this case), a mismatch may occur. Similarly, if the WTRU is configured with k2min but receives data scheduling DCI indicating k2 (where k2 < k2min in this case), a mismatch may occur. A mismatch may also occur if the WTRU is configured with Xmin but receives data scheduling DCI indicating X (where X < Xmin in this case).

[0215] If a mismatch occurs, in some aspects, it is possible that the WTRU is expected to switch from the current performance state to the performance state associated with the k0 / k2 / X values indicated in the data scheduling DCI. For example, a WTRU configured with k0min = k2min = Xmin = 1 slot and operating in a power-saving state can switch to another performance state (e.g., a non-power saving state) if it receives data scheduling DCI indicating that at least one of k0 / k2 / X is 0 slots. For example, as part of the performance state behavior, a WTRU provided with k0min / k2min / Xmin and receiving data scheduling DCI including k0 < k0min and / or k2 < k2min and / or X < Xmin can set the new values of k0min / k2min / Xmin to the received k0 / k2 / X. Alternatively, it can set the values of k0min / k2min / X to a default value such as zero slots.

[0216] If a mismatch occurs, in some aspects the WTRU may send assistance information to the gNB indicating the occurrence of the mismatch. The MAC-CE may be used to transmit such information.

[0217] In another aspect, the WTRU may be configured with k0min (k2min) but may receive a data scheduling DCI indicating k0(k2), where k0>k0min (k2>k2min). This may occur as a result of a scheduling decision or mismatch. If the respective scheduling DCI continuously indicates k0>k0min (k2>k2min) over a particular period of time, the WTRU may send assistance information to the gNB indicating a possible mismatch. The same may apply to X.

[0218] In aspects, a mismatch may occur if a WTRU in a first performance state configured with a particular MIMO rank and / or number of Tx / Rx RF chains receives a data scheduling DCI indicating an inconsistent rank and / or number of RF chains. For example, the WTRU may be configured with Kmax (Kmax is the maximum rank) and / or Rmax (Rmax is the maximum number of active Tx and / or Rx RF chains) but receives a data scheduling DCI indicating K>Kmax and / or R>Rmax. If such a mismatch occurs, the WTRU may be expected to switch from its current performance state to a state associated with the information carried in the DCI. The WTRU may also send assistance information to the gNB indicating the occurrence of a mismatch. MAC-CE may be used to transmit such information. In other aspects, if the WTRU is continually scheduled with K(R) less than Kmin(Rmin) over a particular period of time, it may send assistance information to the gNB indicating a possible mismatch.

[0219] In general, if the data scheduling DCI has information that is inconsistent with the WTRU's performance state, the WTRU may switch its performance state to the state associated with the information included in the DCI and, if a single occurrence of the inconsistency is sufficient to establish a mismatch, send assistance information to the gNB indicating the mismatch. Alternatively, or additionally, the WTRU may send assistance information to the gNB indicating a possible mismatch if a single occurrence of the inconsistency is not sufficient to establish a mismatch, but such inconsistency occurs continuously over a certain period of time.

[0220] In some aspects, the WTRU may send an acknowledgment or notification that radio performance conditions have changed, for example, as a result of applying one of the aspects described above. The WTRU may send the acknowledgment using physical layer, MAC, or RRC signaling. For example, the acknowledgment may be sent over the PUCCH (or as uplink control information (UCI) multiplexed over the PUSCH) as a single bit, such as a HARQ-ACK, which may be multiplexed with other HARQ-ACKs and / or other UCIs. In another example, the notification may be sent in a MAC control element or an RRC message.

[0221] The state change may be signaled using a transmission to be decoded by multiple WTRUs. For example, the state change may be signaled using a PDCCH received from a group common search space and a C-RNTI allocated to a group of WTRUs. Such a transmission may be a power save signal, examples of which are described above. The WTRU may use at least one of the following aspects to determine the PUCCH resource over which to send the acknowledgment. Such aspects may also be used for scenarios other than power save signaling, where a state change is signaled using group signaling.

[0222] In some aspects, the payload of the power saving signal may indicate PUCCH resources for every WTRU in the group, such as if the power saving signal is WTRU group-specific. The WTRU may initially identify the location of a group of bits in the DCI that indicates the PUCCH resources the WTRU intends to use to transmit an ACK / NACK. Each set of bits may indicate a row in a table, and the row may contain information related to the PUCCH resource. The group of bits may indicate non-transmission of an ACK / NACK (e.g., by setting those bits to a predetermined value) and the location of the PUCCH resource. For example, assuming two bits, 00 may indicate non-transmission of an ACK / NACK, and 01, 10, and 11 may indicate specific PUCCH resources, respectively.

[0223] The location of a group of bits can be determined by the WTRU using a reference to another bit in the DCI payload. As an example, with three WTRUs in a group, each bit in the first three bits can indicate whether to wake up for a particular WTRU, and assuming two bits for PUCCH resource indication, the next two bits can indicate the PUCCH resource for the first WTRU, the next two bits can indicate the PUCCH resource for the second WTRU, etc. The WTRU index (i.e., first, second, etc.) can be configured or derived as a function of the WTRU ID.

[0224] In some aspects, a WTRU may be configured with default radio performance conditions for each BWP. At each On Duration, the WTRU may initially monitor the default radio performance conditions of one or more active BWPs. For example, a WTRU may be configured with a default search space or default CORESET for each BWP. At each On Duration, the WTRU may initially monitor the default search space or default CORESET for one or more active BWPs.

[0225] Upon receiving a PDCCH during a given ON duration or DCI format, the WTRU may, for example, change power savings aspects or radio performance states without changing its active BWP. For example, upon decoding a PDCCH for the WTRU during a given ON duration, the WTRU may increase the number of monitored search spaces or CORESETs in the active BWP. Such an increase may be binary, such as when all search spaces or CORESETs are monitored, or may be gradual, such as depending on the RRC configuration.

[0226] Upon expiration of a timer such as a DRX inactivity timer, the WTRU may, for example, change power saving aspects or radio performance states without changing its active BWP. For example, upon expiration of a DRX inactivity timer or a BWP inactivity timer, the WTRU may reduce the number of monitored CORESETs or the number of monitored search spaces, for example, to only the default search space or default CORSETs of one or more active BWPs.

[0227] In other aspects, upon receiving a WUS during a given on-duration, the WTRU may, in some aspects, change power savings aspects or radio performance states without changing its active BWP. For example, upon receiving a WUS during a given on-duration, the WTRU may increase the number of monitored search spaces or CORESETs in the active BWP. Such an increase may be binary, such as when all search spaces or CORESETs are monitored, or may be gradual.

[0228] The WTRU may further consider the content of the PDCCH scheduling information before changing the radio performance state (e.g., the number of monitored search spaces or CORESETs). For example, before changing the radio performance state, the WTRU may consider one or more of the size of the scheduled TB, the logical channel or DRB to which the data is scheduled, the QoS aspects of the scheduled data (e.g., the service type or included latency), and the provided features of the scheduled UL grant. In an aspect, the WTRU may consider the size of the UL grant and / or the amount of buffered data. In other aspects, the WTRU may consider the LCP mapping restrictions of the UL grant with respect to the buffered UL data.

[0229] The WTRU may further consider one or more of the above metrics to gradually change the radio performance state. For example, the WTRU may consider one or more of the above metrics to determine the number of further search spaces to monitor, e.g., depending on the RRC configuration.

[0230] In an aspect, one or more CSI report values, ranges, or indices for the CSI report may be determined based on a receiver component, a set of receiver components, or a power mode. The determination may be made by the WTRU.

[0231] A CQI table may be determined based on the power mode. For example, a first CQI table may be used for the first power mode, and a second CQI table may be used for the second power mode. The set of modulation orders may differ based on the CQI table. The CQI table for the first power mode may include a subset of modulation orders (e.g., QPSK only), and the CQI table for the second power mode may include the full set of modulation orders (e.g., QPSK, 16QAM, and 64QAM). The number of entries for the CQI table may differ based on the associated power mode. For example, a 3-bit CQI table (8 entries) may be used for the first power mode, and a 4-bit CQI table (16 entries) may be used for the second power mode.

[0232] The full set or a subset of CQI entries in the CQI table may be used based on the power mode. Table 2 shows an example of determining the full set or subset of CQI entries based on the associated power mode. In the example just given, power mode 1 uses CQI entries with QPSK, and power mode 2 uses CQI entries with all modulation orders.

[0233] The number of CQI bits for the CQI report may be determined based on the number of CQI entries in the set or subset determined for the power mode. Alternatively, the number of CQI bits for the CQI report may not be changed based on the power mode and may be determined based on the full set of CQI entries in the CQI table. The CQI entries, CQI indexes, and CQI values ​​may be used interchangeably.

[0234] [Table 2]

[0235] The maximum reported rank may be limited based on the power mode. For example, a first maximum reported rank (e.g., 4) may be used when a first power mode is determined for CSI reporting. A second maximum reported rank (e.g., 1) may be used when a second power mode is determined for CSI reporting. The maximum reported rank, the maximum rank index (RI) value, and the maximum RI may be used in other words.

[0236] A codebook subset restriction level may be determined based on the power mode. The minimum required CSI computation time for a given CSI reporting setting or configuration may differ based on the power mode. A shorter minimum required CSI computation time may be used for the high power mode, and a longer minimum required CSI computation time may be used for the low power mode.

[0237] In some aspects, one or more configured CSI reporting settings, resource settings, and / or CSI reporting configurations may be activated or deactivated based on a power mode used. For example, a CSI reporting setting may be deactivated when one or more conditions are met. The activation and / or deactivation may be performed by the WTRU. The conditions may be one or more of: a determined receiver component or set of components being in or corresponding to a low power mode; a number of antenna ports of an associated NZP-CSI-RS for CSI reporting being greater than a threshold (e.g., 8); an associated codebook type being Type II; a number of beams for performing measurements for L1-RSRP being greater than a threshold (e.g., 64); and a CSI reporting being periodic or semi-persistent.

[0238] In some aspects, a set of CSI reporting settings, resource settings, and CSI reporting configurations may be configured for each receiver component, set of receiver components, or power mode. For example, a first set of CSI reporting settings, resource settings, and CSI reporting configurations may be configured or used for a first receiver component, set of receiver components, or power mode. A second set of CSI reporting settings, resource settings, and CSI reporting configurations may be configured for a second receiver component, set of receiver components, or power mode.

[0239] The WTRU may report CSI based on a set of CSI reporting settings, resource settings, and CSI reporting configurations associated with a determined or current power mode. The WTRU may report CSI based on a set of CSI reporting settings, resource settings, and CSI reporting configurations associated with an indicated power mode. The power mode may be indicated in an aperiodic CSI reporting trigger, or the power mode may be implicitly indicated by an aperiodic reporting request index.

[0240] In some aspects, the same set of CSI reporting settings, resource settings, and CSI reporting configurations may be configured for several or all supported power modes. The WTRU may be requested to report the configured CSI along with one or more power modes. For example, the WTRU may be requested to report the CSI based on the power mode. The WTRU may be requested to report the CSI based on a set of power modes supported by the WTRU. If the indicated power mode for CSI reporting is different from the current power mode, a measurement gap may be provided or used for CSI measurements. During the measurement gap, the WTRU may be able to or may be enabled to skip monitoring the PDCCH.

[0241] When CSI reporting is based on multiple power modes, a delta offset of the CSI measurement may be used across power modes. For example, a reference CQI value may be measured based on the highest CQI value among the CQI values ​​for multiple power modes or the CQI value based on the highest power mode, and delta CQI values ​​for the rest of the power modes may be reported.

[0242] In some aspects, the WTRU may measure and report CSI based on the determined power mode if measurement resources are available. The WTRU may indicate an associated power mode for or along with each CSI report. The WTRU may indicate the identity of the power mode.

[0243] One or more PUCCH resources may be configured, and one of the PUCCH resources may be determined based on an associated power mode. The WTRU may use the determined PUCCH resource, for example, for CSI reporting.

[0244] In some aspects, the CSI reporting setting, resource setting, or configuration may include attributes associated with a receiver component, a set of resource components, or a power mode. For example, a first CSI resource may be configured such that the CSI-RS transmitted on that resource can be measured on a first number of RF chains. Another CSI resource may be configured such that the CSI-RS transmitted on that resource can be measured on a second number of RF chains.

[0245] FIG. 12 is a signal diagram 1200 of an example of aperiodic CSI reporting triggering with an associated power mode indication. In the example shown in FIG. 12, a DCI 1202 includes a power mode indication. A CSI-RS 1206 may be transmitted an offset time 1204 after DCI activation. The CSI-RS may be associated with a particular power mode. In aspects, the DCI may not need to include a power mode indication, such as if a CSI-RS resource is associated with the power mode. The association may be configured by higher layers. The WTRU may be performing CSI measurements using the CSI-RS reference signal and the indicated power mode. The WTRU may report the measurements in an associated CSI report 1210, e.g., a reporting offset 1208 after the CSI-RS 1206.

[0246] FIG. 13 is a signal diagram 1300 of an example of periodic CSI-RS and aperiodic CSI reporting. In the example shown in FIG. 13, when CSI-RS is periodic and CSI reporting is aperiodic, each CSI resource may be associated with a specific power mode. An activation or trigger message 1302, e.g., via DCI or higher layers, may indicate a power mode that may be used by the WTRU to determine the CSI-RS resources for measurement. The WTRU may perform measurements of the CSI reference signals 1304 and 1308 using one or more power modes indicated in the activation of the trigger message 1302. In the example shown in FIG. 13, the WTRU measures CSI-RS 1304 using a first power mode and CSI-RS 1308 using a second power mode. The DCI 1306 may trigger the WTRU to report CSI corresponding to one or more specific power modes. At a reporting offset 1310 after the DCI 1306, the WTRU may send a CSI report 1312, which may be for one or both power modes.

[0247] FIG. 14 is a signal diagram 1400 of an example of periodic CSI-RS and periodic CSI reporting. When the CSI-RS is periodic and the CSI reporting is also periodic, the CSI-RS resources may be associated with a particular power mode. In the example shown in FIG. 14, for example, an activation message 1402 indicates that a first power mode is associated with CSI-RS 1406 and a second power mode is associated with CSI-RS 1410. When a WTRU receives the activation message 1402, the WTRU may activate and measure 1404 the CSI-RS 1406 using the first power mode and measure the CSI-RS 1410 using the second power mode. The activation message 1402 may request or command the WTRU to report CSI corresponding to the indicated power mode. Thus, after measuring CSI-RS 1406, the WTRU sends CSI report 1408, and after measuring CSI-RS 1410, the WTRU sends CSI report 1412 without any further signaling required to trigger the CSI reporting.

[0248] The measurements performed by the WTRU may not be limited to CSI. For example, the WTRU may measure RSRP or another quantity. The WTRU may perform measurements using CSI-RS or some other reference signal. For example, the WTRU may perform measurements using SS-PBCH blocks. Each SS / PBCH block may be associated with a particular power mode. The WTRU may perform measurements on the SS / PBCH blocks while operating in the associated power mode. The WTRU measurements may include a coverage level.

[0249] The power mode may determine the maximum number of data streams the WTRU can receive. The maximum or minimum number of RF chains that can be turned on or used or the power mode that can be used may be indicated to the WTRU. The indication may be based on an explicit or implicit indication, as described in detail above. The indication may be carried in DCI format in the PDCCH, in the MAC CE, or in a configuration message from a higher layer. The WTRU may operate with the indicated number of RF chains or power mode, for example, in response to or based on the indication, or based on receiving the indication.

[0250] In an aspect, a timer may be used for power mode determination. The WTRU may operate in that power mode until the power mode is modified or deactivated, e.g., via a subsequent indication or based on expiration of a timer. The subsequent indication may overwrite or replace the previous indication. The WTRU may operate in that power mode until another power mode is activated, e.g., via a subsequent indication or based on expiration of a timer. The subsequent indication may overwrite or replace the previous indication.

[0251] The timer may be configured, for example, by the gNB, and / or used by the WTRU when a power mode is configured, activated, or used. The timer may be used for a subset of the power modes. For example, the timer may be used for power modes other than the normal power mode. The normal power mode may be considered a fallback power mode. When the timer expires, the WTRU may switch to the normal power mode.

[0252] The timer may be started or restarted by the WTRU when the maximum rank or power mode is received or determined by the WTRU and / or indicated or configured by the gNB. The timer value may be indicated or determined when the maximum rank or power mode is indicated and / or when the timer is started or restarted. The indication may include or identify the timer value. Alternatively, the timer value may be associated with the maximum rank or power mode. The indication of the maximum rank or power mode may implicitly indicate the timer value based on the association. When using the maximum rank or power mode, the WTRU may use the timer value associated with that maximum rank or power mode.

[0253] When the timer expires, the WTRU may stop using a maximum rank constraint or power mode that may be associated with the timer. The WTRU may use a different maximum rank or power mode, which may be configured or otherwise known. The WTRU may use a first set of ranks when the timer is running or not started, and a second set of ranks when the timer has expired or is not running. The maximum rank in the first set of ranks may be lower than the maximum rank in the second set of ranks. When the timer expires, the WTRU may use, resume, or switch to a default, fallback, predetermined, or other operating mode, such as a normal power mode.

[0254] 15 is a signal diagram 1500 of an example maximum rank restriction with a timer. In the example shown in FIG. 15, a base station, such as a gNB, provides a message 1502 including the maximum rank. At a trigger offset 1504 after the message 1502, the base station may begin using the maximum rank constraint (1506), and the WTRU may set a timer. When the timer expires (1508), the maximum rank restriction may end (1510).

[0255] In other aspects, the WTRU may receive a first indication or message that includes or identifies a first maximum rank or power mode. The WTRU may operate in the first maximum rank or power mode, e.g., after receiving the first indication or message. The WTRU may receive a second indication or message that includes or identifies a second maximum rank or power mode. The second indication or message may override or replace the first indication or message. The second maximum rank or power mode may override or replace the first maximum rank or power mode. The WTRU may operate in the second maximum rank or power mode, e.g., after receiving the second indication or message.

[0256] In other aspects, the WTRU may receive a DCI on the PDCCH for resource allocation, and the rank information in the DCI may be higher than a previously sent, configured, or received maximum rank. If the WTRU receives a rank higher than a previously sent, configured, or received maximum rank, the WTRU may assume that the existing maximum rank constraint has been disabled and may enter or resume a default mode. This default mode may be, for example, a normal power mode, a mode with all RF chains activated, and / or a mode with the maximum rank set to the maximum possible value allowed by the WTRU capabilities or WTRU hardware. Constraints and limitations may be used interchangeably herein. In an aspect, one of the DM-RS configuration and the power level of the RS may be determined based on the maximum rank.

[0257] A BWP may be determined based on the maximum rank. There may be at least one BWP configured, and each BWP may be associated with at least one of a maximum rank, a maximum number of RF chains, a power mode, and / or another parameter related to WTRU power consumption. When a BWP is activated, the WTRU may assume that one, more, or all of the associated parameters are valid for the duration of transmission and / or reception within the BWP. This assumption may not apply to parameters that are overwritten or reconfigured, e.g., by the gNB, e.g., via DCI, MAC, or higher layer signaling. If a parameter is overwritten or reconfigured with a new value, the WTRU may use the new value.

[0258] A CORSET configuration may be determined based on the maximum rank. There may be at least one CORESET configuration, and each configuration may be associated with at least one of a maximum rank, a maximum number of RF chains, a power mode, and / or another parameter related to WTRU power consumption. When a CORSET is configured, the WTRU may assume that one, more, or all of the associated parameters are valid for the duration of the transmission or when monitoring and / or receiving the CORESET. This assumption may not apply to parameters that are overwritten or reconfigured, such as by the gNB via DCI, MAC, or higher layer signaling. If a parameter is overwritten or reconfigured with a new value, the WTRU may use the new value.

[0259] Within the CORESET, there may be multiple search spaces in which the WTRU monitors the PDCCH. Each search space may be associated with one or more parameters described herein, such as one or more parameters related to WTRU power consumption. When monitoring a search space or when monitoring or receiving a PDCCH in a search space, the WTRU may use one or more associated parameters, which may be related to WTRU power consumption.

[0260] The WTRU may be configured with one or more levels of power savings. For example, the WTRU may be configured with a deep sleep mode (e.g., a first power mode) and / or a partial sleep power saving mode (e.g., a second power mode). In the deep sleep power saving mode, one or more entire RF chains may be turned off. In the partial sleep mode, certain functions within one or more RF chains may be shut down. For example, RF functions that may require or use a longer warm-up time may remain on in the partial sleep mode.

[0261] During C-DRX operation, the WTRU uses its available receive antennas (N RX ) can be used to perform radio link monitoring (RLM). The WTRU can adapt the size of the RX RF chain according to the link quality depending on the radio link measurements. In this specification, the RF chain can refer to the actual RF signal chain, or some specific function of the actual RF chain, or the whole or some part of the antenna subsystem.

[0262] In an aspect, the WTRU in C-DRX mode uses the minimum allowed number of receive antennas (N RLM_min ), in which case N RX ≧N RLM_min ≥ 1. The minimum allowed number of receive antennas (N RLM_min ) may be defined based on one or more criteria such as traffic type, reliability, or downlink transmission rank. In an aspect, the measured downlink radio link quality is determined over a specified period of time (T in_Ant ) over the threshold (Q in_Ant_K), one or more of the following may apply: The WTRU may increase the number of active Rx RF functions, chains, and / or Rx antennas by N RX It is possible to reduce it from RLM_min ), or the WTRU may change its power mode from a high power mode to a low power mode, which in aspects may consume more power / energy than the low power mode.

[0263] 16 is a graph 1600 illustrating an example of the number of Rx RF chains that are reduced based on RLM measurements. In the example shown in FIG. 16, the RLM measurements are in_Ant_K If the number of Rx RF chains exceeds Q, then the number of Rx RF chains is reduced. As shown in FIG. 16, by reducing the number of antennas, the RLM measurement in_Ant_K However, it does not exceed the required Q level to maintain synchronization. out The threshold remains above.

[0264] Q in_Ant_K The threshold is Q in or Q out can be defined as a relative offset from in and Q out are the synchronous and asynchronous thresholds, respectively. In the example, Q in_Ant_K Q in_Ant_K =Q in +ΔQ, or alternatively Q in_Ant_K =Q out −ΔQ. The WTRU may expect the relative offset ΔQ to be defined based on one or more criteria such as traffic type, reliability, or downlink transmission rank. For example, a URLLC WTRU handling reliable transmissions may have a larger Q than an mMTC WTRU which is expected to have a longer battery life. in_Ant_KIt is possible to select or configure with a value.

[0265] In an aspect, the measured downlink radio link quality is measured over a specified period of time (T out_Ant ) over the threshold (Q out_Ant_K ), the WTRU reduces the number of active Rx RF functions, chains, and / or Rx antennas to N RX It is possible to increase it again to the default size of

[0266] 17 is a graph 1700 illustrating the number of Rx RF chains increasing based on RLM measurements. In the example shown in FIG. 17, the RLM measurements indicate a downward change, so the number of active RF chains increases to the default size N RX As shown in Figure 17, the RLM measurement is improved. out_Ant T to adjust the power-up time for the RF components. int_Ant In some embodiments, the timer T in_Ant and T out_Ant may be reset with the expiration or start of the T310 timer used for RLM measurements.

[0267] In an aspect, the WTRU may indicate to the gNB a change in the number of Rx RF chains used by the WTRU. Following that indication, the WTRU may anticipate a change in the PDCCH aggregation level. The change in PDCCH aggregation may be deterministic or non-deterministic. The WTRU may anticipate that the change in the PDCCH aggregation level will be effective in n+k slots, where n and k are the indexes of the current slot and offset, respectively. In an aspect with a deterministic change in PDCCH aggregation, the WTRU may attempt PDCCH decoding using one or two specific larger aggregation levels. For example, the WTRU may only anticipate one or two of the highest available aggregation levels for its PDCCH decoding. Alternatively, in an aspect with a non-deterministic change in PDCCH, the WTRU may only prioritize larger aggregation levels for PDCCH blind decoding.

[0268] In other aspects, the WTRU may indicate a potential change in the number of Rx RF chains to the gNB. Following that indication, the WTRU may be provided with an indication to proceed with the change. If the WTRU does not receive a change or confirmation of its proposed change, the WTRU may retain its current Rx RF configuration.

[0269] Provided that the WTRU is allowed to proceed with the change, it may assume that it has received further information related to PDCCH decoding, such as the PDCCH aggregation level. For example, the WTRU may be provided with an indication that there will be no change in the aggregation level. Alternatively, the WTRU may be provided with an indication to use a larger aggregation level for its PDCCH decoding.

[0270] In other aspects, a power mode may be associated with a set of one or more measurement parameters or requirements. For example, a power mode may be associated with at least one of the following measurement parameters for a particular measurement: a measurement reporting period (e.g., for periodic measurements), a timer, a counter, a measurement threshold that may be used to determine when to trigger a measurement report, an accuracy requirement, a duration over which the accuracy requirement may be met, and / or a measurement sampling requirement, such as a minimum number of measurement samples to make over a period of time, for example, for averaging to determine a measurement value.

[0271] The first power mode may be associated with a first measurement parameter or a first set of measurement parameters for measurement. The second power mode may be associated with a second measurement parameter or a second set of measurement parameters for measurement. The WTRU may use the first measurement parameter or the first set of measurement parameters when operating in the first power mode. The WTRU may use the measurement parameter or the second set of measurement parameters when operating in the second power mode. The first measurement parameter and the second measurement parameter may be the same parameter with different values, rules, or requirements. The first and second sets of measurement parameters may include the same set of parameter types, where at least one parameter type in the first set may have a different value, rule, or requirement than the same parameter type in the second set.

[0272] For example, there may be multiple levels of sleep or power saving modes (e.g., level 1, level 2, level 3), such as no sleep, full sleep, normal or regular sleep, deep sleep, or partial sleep. The power modes may correspond to the levels of sleep.

[0273] The measurement parameters for the second power mode may be more relaxed or less stringent than the measurement parameters for the first power for a particular measurement. For example, the duration over which accuracy requirements for a measurement may be met may be longer for the second power mode than for the first power mode.

[0274] The one or more measurement parameters for the power mode may be set by a specification. The one or more measurement parameters for the power mode may be configured. The one or more measurement parameters for the power mode may be a function of the power mode. The WTRU may determine measurement parameters for measurements based on a power mode that the WTRU may be using. The WTRU may perform and / or report measurements using or in accordance with the determined power mode.

[0275] The measurement may be at least one of CQI, SINR, L1-RSRP, RSRP, RSRQ, or path loss. The measurement may be of a reference signal or synchronization signal, such as CSI-RS, ZP-CSI-RS, NZP-CSI-RS, SSS, or DM-RS. The measurement may be an SS / PBCH block measurement.

[0276] The power modes may be associated with one or more timers, counters, measurement parameters, and / or thresholds that may be related to the synchronous and / or asynchronous decision. The WTRU may use one or more timers, counters, measurement parameters, and / or thresholds that may be related to the synchronous and / or asynchronous decision to make a synchronous and / or asynchronous decision based on the power mode that the WTRU may be using.

[0277] In other aspects, power-efficient tracking may be used in addition to or as an alternative to using power modes for power control. In some aspects, the WTRU may process a resynchronization signal (RSS) transmitted by a base station, such as a gNB, along with the DRX ON duration time interval. The RSS may be used for at least one of the following purposes: AFC, time synchronization, beam management, or CSI measurement.

[0278] In some aspects, the RSS is transmitted by the gNB in ​​an identified time window and processed by the WTRU. The RSS reception time window can be linked to the DRX on duration for the WTRU either by configuration or by application of processing rules. For example, the RSS reception time window can be set to start N1 OFDM symbols before the beginning of the first time slot of the DRX on duration window and end N2 OFDM symbols before. Alternatively, the RSS reception time window starts N1 time slots before and ends N2 time slots before the DRX on duration for the device. In aspects, N2 can be set to zero. Alternatively, the RSS reception window can be configured for or applied to the first time slot or time slots of the DRX on duration. It may not be necessary for the RSS to occupy the entire RSS reception time window. The RSS can be present throughout the entire time interval [N1, N2], or it can start only during this time interval. The RSS may require less time for transmission than provided by the configured or applied RSS reception time window. The configuration of the RSS reception time window for use by the WTRU may be linked to the configured DRX parameters. The RSS reception time window may have a larger minimum size if DRX counters and / or timers are configured.

[0279] In other aspects, the RSS is transmitted by the gNB on an identified set of frequency resources and processed by the WTRU. The RSS reception bandwidth window for use by the WTRU can be known either by configuration or by application of processing rules in the WTRU.

[0280] For example, the RSS reception bandwidth window may be set to correspond to a currently active DL BWP in which the WTRU processes incoming PDCCH over the DRX on duration window. Alternatively, it may correspond to an identified subset of frequency domain resources linked to the WTRU's active DL BWP. Alternatively, the RSS reception bandwidth window may correspond to a determined subset of contiguous or non-contiguous frequency resources determined by configuration through RRC. In an aspect, multiple RSS reception bandwidth windows may be configured for a WTRU.

[0281] If the RSS is transmitted by the gNB in ​​the identified time window and processed by the WTRU, as described above, a coarse frequency / timing tracking function in the WTRU can be implemented with minimal wake-up overhead. Unlike conventional NR technology, the WTRU does not need to wake up and power up a significant portion of its RF and BB receiver chains for AFC purposes, even though the next DRX on duration period may be tens or hundreds of milliseconds away. By providing an RSS that is scheduled to begin a pair of OFDM symbols or timeslots just before or coincident with the beginning of the DRX on duration window, the WTRU can power up its RF and BB portions only when needed. Similarly, by processing the transmitted RSS in frequency resources linked to the active DL BWP, the WTRU can avoid frequency readjustments to receive and process one or more SSBs that do not normally coincide with the active DL BWP. Readjusting the WTRU receive bandwidth cost power incurs a penalty in terms of longer receiver on times for BWP switching. Furthermore, the RSS can be employed for beam management purposes.

[0282] In other aspects, the resynchronization signal may be processed by the WTRU in the identified set of REs in the RSS reception time and frequency window. In an aspect, the RSS may be transmitted on one or a set of REs configured as a CSI-RS resource set. For example, the RSS may be configured as a CSI-RS resource set. The RSS may be configured as a CSI_RS resource set, in which case every fourth OFDM symbol over a configurable transmission interval of one or more time slots may be used, with every RSS-carrying OFDM symbol carrying three RSS subcarriers. When configured as a CSI-RS resource set, dynamic signaling in the DCI may be used to match the rate of PDSCH transmissions to other devices around the RSS resources, depending on the type of CSI-RS resource configured (zero power or non-zero power). Similarly, existing configuration messages used for CSI-RS may be reused to indicate the RSS configuration.

[0283] In other aspects, the RSS may be transmitted over a contiguous frequency bandwidth occupying multiple RBs and one or more of multiple OFDM symbols, not necessarily consecutively. For example, the RSS may be transmitted as a length-127 m-sequence occupying 12 RBs via OFDM similar to the PSS, but using a separate m-sequence generator. These RSS-carrying symbols may be repeated, or a set of symbols may be used. In such aspects, existing implementations may be largely reused in devices to realize the RSS function. Furthermore, by using the RSS in the form of a CSI-RE resource set defined at the RE level, existing R15NR signaling may be used to match the rate of the PDSCH of other devices around the RSS, which may avoid decoding degradation and scheduling limitations.

[0284] In other aspects, the RSS sequence may be generated using an identifier configured by the gNB or determined by the WTRU. For example, an identifier linked to or identical to the C-RNTI used by the WTRU may be used to determine the RSS encoding sequence. This may include operations such as generating RSS sequence elements or scrambling the RSS sequence with a second sequence. Reception time parameters, such as symbol or time slot number, may be used to derive the RSS sequence. Explicitly chosen values ​​may be used to determine the RSS sequence. In such aspects, interference may be randomized and reception quality of the RSS may be improved.

[0285] In some aspects of WTRU receiver processing when operating in the presence of configured RSS generation, the WTRU may determine the DRX ON duration, determine a processing interval for reception of RSS, configure its receiver for reception of RSS on an identified set of time and frequency resources, determine the presence or absence of RSS, determine oscillator and / or timing corrections, and then apply the corrections to proceed with PDCCH reception. Any of these steps may imply some further known intermediate steps, e.g., channel estimation, which occurs while processing the PDCCH candidates of the received CORESET.

[0286] In some aspects, use of RSS by the WTRU may be determined to be applicable when conditions are met. For example, if a timer or counter value expires since the last time data or control or appropriate RS or SSB was received by the WTRU while in active time or during the DRX ON duration, RSS may be present and part of the WTRU receiver processing. The timer duration may be predefined or configured by higher layers. In this way, the maximum amount of time and maximum oscillator drift incurred by the WTRU not waking up for coarse AFC may be controlled to not exceed some tolerable value. A gNB that knows the WTRU's DRX ON duration or active time may send RSS to the WTRU if the counter or timer since last data / control reception exceeds a given value. It may not send RSS if it falls below a given value. This may minimize overhead from a network perspective.

[0287] In another example, the WTRU may determine the need for or presence of RSS linked to the DRX ON duration based on a signal level reception threshold. For example, if the DL path loss experienced by the WTRU exceeds a threshold (which may include an offset value), then RSS may be present and part of the WTRU receiver processing. The eNB may configure a signal threshold above which RSS cannot be transmitted and below which RSS is linked to the determined DRX ON duration.

[0288] In another example, the RSS may be present only on the condition that it is not in active time or one or more DRX timers are not running, such as an inactivity timer, an UL or DL ​​retransmission timer, and at least one of a DL or UL HARQ RTT timer, In another example, the RSS may be configured to be present only if the active BWP is one of a subset of configured BWPs.

[0289] FIG. 18 is a signal diagram 1800 of an example of processing an RSS in conjunction with a DRX ON duration time interval. In the example shown in FIG. 18, a WTRU may receive an RSS 1802 in one of an identified time window or set of frequency resources linked to a DRX ON duration 1806 of a DRX cycle 1808. The RSS may be used for AFC, time synchronization, beam management, and / or CSI measurements immediately before the start of the ON duration 1806. The WTRU may monitor a PDCCH monitoring occasion 1804 during the ON duration 1806. The WTRU may also receive an RSS 1812 during an RSS reception window 1822 immediately before the ON duration 1820 of a DRX cycle 1824. An RSS aperiodic NZP-CSI-RS resource set 1826 is also shown in detail with respect to the RSS reception window 1822. The device may be scheduled during a PDCCH monitoring occasion 1814, and a timer may be started or restarted. The timer may expire 1816, and the device may stop monitoring the PDCCH occasion in response to the expiration of the timer.

[0290] Although features and elements are described above in particular combinations, one of ordinary skill in the art will understand 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 embodied in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random-access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks and digital versatile disks (DVDs). A processor associated with software can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer. [Explanation of symbols]

[0291] 100 Communication Systems 102 WTRU 102a WTRU 102b WTRU 102c WTRU 102d WTRU 104 Radio Access Network (RAN) 106 Core Network (CN) 108 Public Switched Telephone Network (PSTN) 110 Internet 112 Network 114a base station 114b base station 116 Air Interface 118 processors 120 Walkie-Talkie 122 receiving elements 124 microphones 126 keypad 128 Touchpad 130 Memory 132 Memory 134 Power supply 136 chipset 138 Peripherals 162 Mobility Management Entity (MME) 164 Serving Gateway (SGW) 166 Gateway (PGW) 182a Mobility Management Function (AMF) 182b Mobility Management Function (AMF) 183a Session Management Facility (SMF) 183b Session Management Facility (SMF) 184a User Plane Function (UPF) 184b User Plane Function (UPF) 185a Data Network (DN) 185b Data Network (DN)

Claims

1. 1. A wireless transmit receive unit (WTRU), comprising: processor, and transceiver Equipped with the processor and the transceiver are configured to receive a configuration for discontinuous reception, the configuration including information associated with an ON duration; the processor and the transceiver are further configured to determine a plurality of DRX cycles based on the configuration, a start of each respective DRX cycle corresponding to a start of a respective ON duration; the processor and the transceiver are further configured to receive a signal prior to the start of the respective ON durations; the processor and the transceiver are further configured to determine to send a first set of channel state information (CSI) reports under a condition that the signals are received having a first value during the respective ON durations; the processor and the transceiver are further configured to determine to send a second set of CSI reports under a condition that the signals are received having a second value during the respective ON durations; The WTRU, wherein the second set is a subset of the first set.

2. 10. The WTRU of claim 1, wherein the processor and the transceiver are further configured to receive the signal on a physical downlink control channel (PDCCH).

3. 1. A method implemented in a wireless transmit receive unit (WTRU), comprising: receiving a configuration for discontinuous reception, the configuration including information associated with an ON duration; determining a plurality of DRX cycles based on the configuration, wherein a start of each respective DRX cycle corresponds to a start of a respective ON duration; receiving a signal prior to the start of the respective ON duration; determining to send reports during the respective ON durations, the reports being (1) a first set of channel state information (CSI) reports under a condition that the signals are received with a first value, or (2) a second set of CSI reports under a condition that the signals are received with a second value; Equipped with The method of claim 1, wherein the second set is a subset of the first set.

4. 4. The method of claim 3, wherein the signal is received on a Physical Downlink Control Channel (PDCCH).

5. A base station, processor, and transceiver Equipped with the processor and the transceiver are configured to send a configuration for discontinuous reception, the configuration including information associated with an ON duration; the processor and the transceiver are further configured to send a signal prior to a start of a respective ON duration of one of a plurality of DRX cycles, the start of each respective DRX cycle corresponding to a start of a respective ON duration; the processor and the transceiver are further configured to receive a first set of channel state information (CSI) reports under a condition that the signals are sent having a first value during the respective ON durations; the processor and the transceiver are further configured to receive a second set of CSI reports under the condition that the signals are sent with a second value during the respective ON durations; The base station, wherein the second set is a subset of the first set.

6. 6. The base station of claim 5, wherein the processor and the transceiver are further configured to send the signal on a physical downlink control channel (PDCCH).

7. 4. The method of claim 3, wherein the WTRU is in an active time when the ON duration begins, the method further comprising decoding at least one PDCCH transmission when the WTRU is in an active time.

8. 8. The method of claim 7, wherein the second set of CSI reports is sent during the ON duration except for an active time.

9. 2. The WTRU of claim 1, wherein the WTRU is in an active time when the ON duration begins, and the processor and the transceiver are further configured to decode at least one PDCCH transmission when the WTRU is in an active time.

10. 10. The WTRU of claim 9, wherein the second set of CSI reports is sent during the ON duration but not during an active time.

11. 1. A method implemented in a base station, comprising: Sending a configuration for discontinuous reception, the configuration including information associated with an ON duration; sending a signal prior to a start of a respective ON duration of one of a plurality of DRX cycles, the start of each respective DRX cycle corresponding to a start of a respective ON duration; receiving reports during the respective ON durations, the reports being (1) a first set of channel state information (CSI) reports under the condition that the signal is sent with a first value, or (2) a second set of CSI reports under the condition that the signal is sent with a second value; Equipped with The method of claim 1, wherein the second set is a subset of the first set.

12. 12. The method of claim 11, wherein the signal is sent on a Physical Downlink Control Channel (PDCCH).

Images