Method, architecture, apparatus, and system for network energy conservation - Patents.com

Abstract

The present disclosure relates to a method and apparatus for network energy conservation. The method may be implemented in a wireless transmit / receive unit (WTRU). The method may include receiving first information indicating i) one or more scheduling request (SR) resources and (ii) a set of wake-up request occasions, each SR resource may be associated with one or more levels of availability. The method may include determining that the WTRU may be at a first level of availability. The method may include transmitting a first wake-up request using a first wake-up request occasion of the set of wake-up request occasions based on a determination that the SR may be transmitted using an SR resource associated with a second level of availability of the one or more levels of availability. The method may include transmitting an SR in an SR resource associated with the second level of availability.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Patent Application No. 63 / 275,207, filed November 3, 2021, and U.S. Patent Application Publication No. 63 / 327,462, filed April 5, 2022, the disclosures of which are incorporated by reference in their entireties.

[0002] The present disclosure relates to methods, architectures, and apparatus for network energy conservation. [Background technology]

[0003] The 3rd Generation Partnership Project (3GPP) Radio Area Network (RAN) has discussed improvements regarding energy conservation for wireless transmit / receive units (WTRUs) and networks. For example, the design of New Radio (NR) Release 15 allows for improved energy conservation by reducing transmissions from the network when there is no data. The network may consume significant energy for processing operations other than transmission, such as baseband processing for reception and / or beamforming. The embodiments described below are designed with the above in mind. Summary of the Invention

[0004] Described herein are methods, architectures, apparatus, and systems directed to network energy conservation. In one embodiment, the method may be implemented in a WTRU. The method may include receiving first information indicating i) one or more scheduling request (SR) resources and (ii) a set of wake-up request occasions, where each SR resource may be associated with one or more levels of availability. The method may include determining that the WTRU may be at a first level of availability. The method may include transmitting a first wake-up request using a first wake-up request occasion of the set of wake-up request occasions, where the first wake-up request may be transmitted based on a determination that the SR may be transmitted using an SR resource associated with a second level of availability of the one or more levels of availability. The method may include transmitting the SR on an SR resource associated with the second level of availability. Under the condition that the time period after transmission of the first wake-up request ends without receiving an availability level indication, the WTRU may transmit a second wake-up request using a second wake-up request occasion of the set of wake-up request occasions, where the first wake-up request may be transmitted at a first transmit power and the second wake-up request may be transmitted at a second transmit power that may be higher than the first transmit power. In an embodiment, an apparatus including any of a transmitter, a receiver, a processor, and a memory may be configured to perform the methods described herein. [Brief description of the drawings]

[0005] A more detailed understanding may be had from the following detailed description, given in conjunction with the drawings that accompany this specification by way of example. Such drawing figures, like the detailed description, are illustrative. Thus, the figures and detailed description should not be considered as limiting, as other equally effective embodiments are possible and likely to be. Moreover, like reference numbers ("ref") within the drawings ("FIG") indicate like elements. [Figure 1A]1 is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] 1A is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A. [Figure 1C] FIG. 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 illustrated in FIG. 1A. [Figure 1D] FIG. 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system illustrated in FIG. 1A. [Diagram 2] 1 is a transmission timing diagram illustrating an example of WTRU operation that enables network energy savings. [Diagram 3] FIG. 1 illustrates an example of a method for network energy conservation. [Figure 4] FIG. 1 illustrates another example of a method for network energy conservation. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0006] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the embodiments and / or examples disclosed herein. It will be understood, however, that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the following description. Furthermore, embodiments and examples not specifically described herein may be practiced in place of, or in combination with, the embodiments and other examples explicitly, implicitly and / or inherently described, disclosed or otherwise provided herein (collectively "provided").

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

[0008] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112, although it will be understood that the disclosed embodiments 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” and / or “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, paging, mobile phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., for remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated processing chain context), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

[0009] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base station transceiver station (BTS), a Node B, an eNode B, a Home Node B, a Home eNode B, a gNB, an NR Node B, a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each illustrated 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 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage for 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 embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell, for example, using beamforming to transmit and / or receive signals in a desired spatial direction.

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

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

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

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

[0015] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, e.g., using dual connectivity (DC) principles. Thus, the radio interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to and from multiple types of base stations (e.g., eNBs and gNBs).

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

[0017] 1A may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, but may utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as a location of a business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). 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 need to access the Internet 110 via the CN 106 / 115.

[0018] The RAN 104 / 113 may communicate with the CN 106 / 115, 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, such as, for example, different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may communicate directly or indirectly with other RANs employing the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or Wi-Fi radio technology.

[0019] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network 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 the transmission control protocol (TCP), user datagram protocol (UDP), and / or the internet protocol (IP) of the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RANs 104 / 113, 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 different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a, which may employ a cellular-based wireless technology, and a base station 114b, which may employ an IEEE 802 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 foregoing elements while remaining consistent with an embodiment.

[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) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although FIG. 1B illustrates 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 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via the wireless interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

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

[0025] The transceiver 120 may be configured to modulate signals transmitted by the transmit / receive element 122 and 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, for example, NR and IEEE 802.11.

[0026] The processor 118 of the WTRU 102 may be coupled to, and may receive user-entered data from, a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as 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 embodiments, the processor 118 may access information from and store data in memory that is not physically located on the WTRU 102, such as on a server or 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 the 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. In addition to, or in lieu of, information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may obtain location information by way of any suitable location determination method while remaining consistent with an embodiment.

[0029] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic 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 modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, which 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, and / or a humidity sensor.

[0030] The WTRU 102 may include a full-duplex radio where transmission and reception of some or all of the signals (e.g., associated with a particular subframe for both the uplink (e.g., for transmission) and downlink (e.g., for reception)) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit 139 to reduce and or substantially eliminate self-interference either through hardware (e.g., chokes) or signal processing via a processor (e.g., via a separate processor (not shown) or processor 118). In an embodiment, 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 uplink (e.g., for transmission) or downlink (e.g., for reception)).

[0031] 1C is a system diagram illustrating the RAN 104 and the CN 106, according to one embodiment. As mentioned above, the RAN 104 may employ E-UTRA radio technology and communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also communicate with the CN 106.

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

[0033] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and / or downlink (DL), etc. As shown in FIG 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another 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 (or PGW) 166. Although each of the foregoing elements is illustrated 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 function 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 attachment of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

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

[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 communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0038] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0039] Although the WTRU is depicted in FIGS. 1A-1D as a wireless terminal, in certain representative embodiments it is contemplated that such a terminal may use a wired communications interface (e.g., temporarily or permanently) with the communications 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) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating from outside the BSS to the STA may arrive through the AP and be delivered to the STA. Traffic originating from the STA to a destination outside the BSS may be sent to the AP and transmitted to the respective destination. Traffic between STAs within the BSS may be transmitted, for example, through the AP, where the source STA may transmit traffic to the AP, which may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be transmitted between (e.g., directly between) the source STA and the destination STA using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may be referred to herein as an "ad-hoc" communication mode.

[0042] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit a beacon 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 width that is dynamically set via signaling. The primary channel may be the operating channel of the BSS, but may be used by STAs to establish a connection with the AP. In certain representative embodiments, Carrier sense multiple access with collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. With CSMA / CA, STAs (e.g., all STAs), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0043] A High Throughput (HT) STA may use a 40 MHz wide channel for communication, which may be formed, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels.

[0044] A Very High Throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. A 40 MHz and / or 80 MHz channel may be formed by combining multiple contiguous 20 MHz channels. A 160 MHz channel may be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, after channel encoding, the data may pass through a segment parser that 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 to 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 may be reversed and the combined data may be transmitted to the Medium Access Control (MAC).

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

[0046] WLAN systems that may support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that may be designated as a primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be configured and / or limited by the STAs among all STAs operating in the BSS that support the smallest bandwidth operating mode. In an 802.11ah example, the primary channel may be 1 MHz wide for STAs (e.g., MTC-type devices) that support (e.g., only) 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. For example, if the primary channel is busy due to STAs (that only support 1 MHz mode of operation) transmitting to the AP, the entire available frequency band may be considered busy even though most of the frequency band may remain idle and available for use.

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

[0048] 1D is a system diagram illustrating the RAN 113 and the CN 115, according to one embodiment. As mentioned above, the RAN 113 may employ NR radio technology and communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also communicate with the CN 115.

[0049] The RAN 113 may include gNBs 180a, 180b, 180c, although it will be understood that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to transmit and / or receive signals to the gNBs 180a, 180b, 180c. Thus, the gNB 180a may transmit and / or receive wireless signals to and from the WTRU 102a, for example, using multiple antennas. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In one embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (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 vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of different or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).

[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 another RAN (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 with and connect to a gNB 180a, 180b, 180c while also communicating with and connecting to another RAN, such as an eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In 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 uplink (UL) and / or downlink (DL), support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards user plane functions (UPFs) 184a, 184b, routing of control plane information towards 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. Although each of the foregoing elements is illustrated as part of the CN 115, 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 113 via an N2 interface and may function 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 different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. The network slices may be used by the AMF 182a, 182b to customize the CN support of the WTRUs 102a, 102b, 102c based on the type of service utilizing the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. The AMFa 82a, 182b may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

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

[0056] The UPFs 184a, 184b may connect to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The 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 downlink packets, providing mobility anchoring, etc.

[0057] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (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 DNs 185a, 185b.

[0058] 1A-1D and the corresponding description thereof, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNodeBs 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 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 communication network to test other devices in the communication 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 communication network. The emulation device may be directly coupled to another device for testing purposes and / or may implement the testing using terrestrial wireless communication.

[0060] The one or more emulation devices may perform one or more functions, inclusive, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in an undeployed (e.g., test) 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 include, for example, one or more antennas) may be used by the emulation devices to transmit and / or receive data.

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

[0062] For clarity, satisfying, not satisfying, and "configuring a condition parameter" are described throughout the embodiments described herein with respect to a threshold (e.g., greater than or less than a value (e.g., a threshold), configuring a value (e.g., a threshold), etc.). For example, satisfying a condition may be described as exceeding a value (e.g., a threshold), and not satisfying a condition (e.g., a performance criterion) may be described as being below a value (e.g., a threshold). The embodiments described herein are not limited to threshold-based conditions. Any type of other condition and parameter (e.g., falling within or not falling within a range of values, etc.) may be applicable to the embodiments described herein.

[0063] Network Energy Savings Examples There may be a new research item in 3 GPP RAN on network energy conservation in Release 18 for research to expand the network's ability to reduce (e.g., minimize) its power consumption from either transmission and reception. Such reduction (e.g., minimization) may make it possible to reduce operational costs and improve environmental sustainability.

[0064] Compared to previous systems, the design of NR in Release 15 allows for reduced (e.g., minimized) transmissions from the network in the absence of data. For example, always-on cell-specific reference signals (CRS) are not used in NR. For example, energy consumption (in NR Release 15) can be further reduced.

[0065] For example, a network may consume energy for non-transmit processing operations, such as, for example, baseband (e.g., digital) processing for reception and / or beamforming. Such "idle" power consumption may be (e.g., even) non-negligible in dense networks when a WTRU is not served during a period of time. Turning off these processing operations when not transmitting to a WTRU may allow the network to reduce energy consumption.

[0066] For example, NR may support beamforming with up to 64 transmit and receive ports, and energy consumption may increase as the number of ports utilized increases. Utilizing a large number of ports (e.g., a maximum, a constant number) may not be practical for all WTRUs. Adapting the number of ports to, for example, what may be expected by one or more WTRUs may allow for reducing energy consumption in the network.

[0067] In a 3GPP Release 17NR based system, idle power consumption reduction on the network side may remain limited in the absence of traffic from the WTRU. This is because resources may be configured by the network for the WTRU so that the network can attempt (e.g., frequently) to receive (e.g., from the WTRU). For example, the network may configure resources for either a Scheduling Request (SR), a Random Access Channel (RACH), and a Configuration Grant (CG) for (e.g., each) WTRU with a periodicity that may depend on its latency characteristics (e.g., expectations). For example, the network may configure periodic Sounding Reference Signal (SRS) and / or Channel State Information (CSI) resources, e.g., for link adaptation purposes. Even during periods when the WTRU may not have data to transmit, the network may be expected to attempt to receive and transmit CSI-RS on these resources to support periodic CSI.

[0068] The embodiments described herein may enable the network to know (e.g., determine) when transmission and / or reception may be turned off (or a fewer number of antenna ports may be used) for such resources, allowing the network to maintain quality of service for the served WTRUs.

[0069] overview Throughout the embodiments described herein, the terms "availability state," "availability level," and "readiness state" may be used interchangeably to designate a state among a set of (e.g., expected transmission / reception) states of a WTRU that represents (e.g., is associated with) a level of (e.g., discrete) activity of the WTRU.

[0070] For example, the WTRU may determine whether to transmit (or receive) one or more resources depending on an availability state that may be indicated by the network (e.g., via transmitted information). In a first availability state, some resources may not be available during one or more time periods during which the network may turn off baseband processing and other related processing operations (e.g., activity). Under one or more conditions, the WTRU may further transmit a request (e.g., a wake-up request, etc.) to the network to change from the first availability state to a second availability state in which resources may be available that may meet the WTRU expectations. Such a wake-up request may correspond to a transmission that may be decodable by a low-complexity receiver at the gNB, in which energy consumption may be reduced.

[0071] The availability state of the WTRU may imply (e.g., be associated with) the power saving state of the gNB. In one embodiment, the WTRU may determine an “availability state” (e.g., be in an “availability state”) according to one or more of the following examples:

[0072] In an example, the WTRU may determine an availability state (e.g., being in an availability state) based on receiving an availability state (e.g., level) indication, for example, from any of a group-common physical downlink control channel (PDCCH), a MAC control element (MAC CE), and WTRU-specific downlink control information (DCI). The terms "availability state indication" and "availability level indication" may be used interchangeably throughout the embodiments described herein to refer to any transmission that indicates that the WTRU may be in an availability state.

[0073] In another example, the WTRU may determine the availability state (eg, be in the availability state) after either receiving a signal indicating a wake-up response or transmitting a signal indicating a "wake-up request."

[0074] In yet another example, the WTRU may determine to be in a default availability state (e.g., is in a default availability state). For example, the first / second availability state may be valid for a period of time following either (i) receipt of either an availability state indication and a wake-up response signal, and (ii) transmission of a wake-up request signal, upon expiration of which the WTRU may determine to be in the default availability state.

[0075] In yet another example, the WTRU may determine that it is in the first / second availability state (e.g., is in the first / second availability state) when it determines that a certain amount of time has elapsed after transmitting a wake-up request signal or after receiving an availability state indication.

[0076] In one embodiment, the WTRU may determine whether resources are available for transmission / reception for the determined availability state according to one or more of the following examples.

[0077] In an example, the WTRU may determine whether resources are available for transmission / reception for a determined availability state based on whether the resources may be for any of a scheduling request (SR), a configuration grant, an SRS, a channel state information reference signal (CSI-RS), a physical random access channel (PRACH), etc.

[0078] In another example, the WTRU may determine whether a resource is available for transmission / reception for the determined availability state based on a (e.g., maximum) number of ports associated with the resource. A resource may be characterized (e.g., associated with) a (e.g., maximum) number of ports. (E.g., the available number of ports may depend on the availability state).

[0079] In yet another example, the WTRU may determine whether resources are available for transmission / reception for a determined availability state based on receiving (e.g., explicit) configuration information indicating either the availability of resources for the (e.g., each) availability state, a time mask pattern associated with the (e.g., each) availability state, etc.

[0080] In yet another example, the WTRU may determine whether resources are available for transmission / reception for the determined availability state based on the periodicity of the resources.

[0081] In one embodiment, the WTRU may receive information indicating a configuration of resources for one or more "wake up requests" (WURs) according to one or more of the following examples.

[0082] In one example, the configuration of resources for one or more WURs may include resource characteristics such as a scrambling initiator, a set of time occasions, a frequency span, and any of a spatial filter.

[0083] In another example, the configuration of resources for one or more WURs may include a power control configuration.

[0084] In yet another example, the configuration of resources for one or more WURs may include any parameters that may be used in a WUR procedure (e.g., maximum number of repetitions, "prohibit" timers, etc.).

[0085] In one embodiment, the WTRU may initiate a "wake-up request" procedure (eg, send a WUR) if one or more of the following conditions occur (eg, are met):

[0086] In an example, the WTRU may send a WUR when an SR is triggered and / or when there are no resources available for SR with the current availability state, eg, within a latency limit.

[0087] In another example, the WTRU may transmit a WUR when a Buffer Status Report (BSR) is triggered and / or resources are not available for a BSR MAC CE transmission in the current availability state, for example within a latency limit.

[0088] In yet another example, the WTRU may transmit a WUR when permission to transmit data available for transmission (e.g., taking into account logical channel prioritization (logical channel priority (LCP) limitations) is not available, e.g., within a latency threshold).

[0089] In yet another example, the WTRU may transmit a WUR if the buffer status satisfies a condition (eg, is higher than a threshold).

[0090] In yet another example, the WTRU may transmit a WUR when any of the mobility and channel related events (eg, a radio resource management (RRM) event, bidirectional forwarding detection (BFD), etc.) are triggered.

[0091] In yet another example, the WTRU may transmit a WUR if the channel measurements meet or fail a condition (e.g., above or below a configured threshold). For example, the channel measurements that meet or fail a condition may include any of: (i) a measured Received Signal Strength Indicator (RSSI) and / or Reference Signal Signal-to-Interference-and-Noise Ratio (RS-SINR) above or below a threshold, (ii) no synchronization signal block (SSB) samples to measure, and (iii) no primary synchronization signal / secondary synchronization signal (PSS / SSS) detection.

[0092] In yet another example, the WTRU may transmit a WUR if an availability signal is detected according to any embodiment described herein.

[0093] In yet another example, the WTRU may transmit a WUR in the event of arrival of uplink data to a secondary cell group (SCG) bearer.

[0094] In yet another example, the WTRU may transmit a WUR in case of arrival of data from a data resource bearer DRB and any of (eg, some of) signaling radio bearers (SRBs).

[0095] In yet another example, the WTRU may send a WUR when any of the RRC state changes and RRC procedures (eg, RRC restart, RRC establishment, RRC re-establishment, etc.) are triggered.

[0096] In yet another example, the WTRU may send a WUR if an RRC message (eg, RRC release) is received.

[0097] In yet another example, the WTRU may transmit a WUR when any of the positioning procedures are performed and information indicative of a positioning report is transmitted, determining a possible location within the cell coverage, for example as the best server.

[0098] In yet another example, the WTRU may transmit a WUR in response to any of the triggers described herein for transmitting a wake-up request. In one embodiment, the WTRU may select the wake-up request resource (and / or the WUR payload) according to one or more of the following example information:

[0099] In an example, the WTRU may select a wake-up request resource (and / or a WUR payload) based on the target availability state. For example, a wake-up request resource may be selected if the wake-up request resource is associated with the target availability state.

[0100] In yet another example, the WTRU may select the wake-up request resource (and / or the WUR payload) based on an indication of the resources to be used.

[0101] In yet another example, the WTRU may select the wake-up request resource (and / or WUR payload) based on an indication of what triggered the wake-up request (either SR ID, logical channel ID, logical channel priority, buffer status, etc.).

[0102] In yet another example, the WTRU may select a wake-up request resource (and / or a WUR payload) based on the timing of the occasion for using the resource.

[0103] In one embodiment, the WTRU may start a timer.

[0104] In one embodiment, the WTRU may transmit and / or receive on available resources according to the requested availability state, either before receiving any information from the network indicating the availability state, or after receiving information indicating (e.g., confirming) the availability state.

[0105] In one embodiment, the WTRU may complete the wake-up request procedure if one or more of the following conditions occur:

[0106] In a first example, the WTRU may complete a wake-up request procedure if the WTRU receives information indicating an availability status.

[0107] In another example, the WTRU may complete the wake-up request procedure if the WTRU receives (any) unicast PDCCH.

[0108] In yet another example, the WTRU may complete a wake-up request procedure upon timer expiration according to any embodiment described herein.

[0109] In yet another example, the WTRU may complete the wake-up request procedure when a (e.g., maximum) number of wake-up request transmissions has been reached. The WTRU may report this event by sending information in any of the DCI, MAC CE, and Radio Resource Control (RRC) messages.

[0110] 2 is a transmission timing diagram illustrating an example of a WTRU operation that enables network energy savings. For example, a WTRU may have received (i) one or more SR resources and (ii) first information indicating a set of wake-up request occasions, where the (e.g., each) SR resource may be associated with one or more availability levels, e.g., Level 0, Level 1, etc. For example, the WTRU may determine that it is at a first level of availability (e.g., Level 0).

[0111] At time 200, there may be SR resources that may be available (eg, associated with) either a first level of availability (eg, Level 0) and a second level of availability (eg, Level 1).

[0112] At time 202, the WTRU may determine that the SR may be transmitted using an SR resource associated with a second level (eg, level 1) of availability of the one or more levels of availability.

[0113] At time 204, for example, if there are no SR resources associated with a second level of availability (e.g., level 1), the WTRU may transmit a first wake-up request using a first wake-up request occasion of the set of wake-up request occasions. For example, the WTRU may start a timer to monitor for receipt of an availability level indication.

[0114] At time 206, the WTRU may transmit an SR in an SR resource associated with a second level of availability.

[0115] At time 208, the WTRU may receive a transmission indicating the availability level indication and may stop the timer. If the timer expires (e.g., if the time period after transmission of the first wake-up request has expired) without receiving an availability level indication, the WTRU may transmit a second wake-up request using a second wake-up occasion of the set of wake-up request occasions, where the first wake-up request may be transmitted at the first transmit power and the second wake-up request may be transmitted at a second transmit power, which may be higher than the first transmit power.

[0116] Example of determining availability state The WTRU may determine an availability state from several availability states based on any of the following examples. For example, there may be two availability states ("on" and "off"), three availability states (e.g., "deep sleep", "microsleep", "on"), or four availability states (e.g., "off", "deep sleep", "microsleep", "on"). An availability state may be applicable to (e.g., associated with) at least one resource, and a resource may be associated with one or more availability states. An availability state may be applicable to (e.g., associated with) at least one time period, such as any of a time slot and a time symbol. An availability state may be applicable to (e.g., associated with) any of a serving cell, a cell group, a frequency band, a bandwidth portion, and a range of frequencies within the bandwidth portion.

[0117] Example of receiving DCI or MAC CE In one embodiment, the WTRU may receive information (e.g., an indication therefrom) in any of the downlink control information (DCI) and the MAC control element and may determine the availability state based on such information (e.g., the indication). For example, the information (e.g., the indication) may be included in a group-common PDCCH. The information (e.g., the indication) may indicate at least one identification of the availability state for at least one time period, such as, for example, any of a symbol, a slot, and a frame. For example, the information (e.g., the indication) may correspond to an index into a table, where an (e.g., each) entry in the table may indicate a sequence of availability states applicable to, for example, a respective sequence of time symbols from the start of the next time slot. The table may be predefined or may be configured by receiving configuration information, for example, based on an RRC message.

[0118] In another example, the information (e.g., indication) may comprise a MAC CE indicating an index into an availability state. The availability state may be applicable starting from a delay after receipt of the MAC CE or from a delay after transmission of a Hybrid Automatic Repeat Request Acknowledge (HARQ-ACK) acknowledging a Physical Downlink Shared Channel (PDSCH) carrying the MAC CE. The WTRU may start a timer at that point. The availability state may be applicable until either receipt (or transmission) of signaling indicating (e.g., triggering) a new availability state or until expiration of the timer. At least one of the delay and timer may be predefined, signaled in the MAC CE, and configured by receiving configuration information, for example, based on RRC.

[0119] Example of Receiving Availability Status Indication Signals Throughout the embodiments described herein, the terms "availability state indication," "availability state indication signal," "availability level indication," and "availability level indication signal," "transmission indicating an availability state indication," and "transmission indicating an availability level indication" may be used interchangeably to designate any transmission that acknowledges that a WTRU may be in an availability state (e.g., is at an availability level).

[0120] In one embodiment, the WTRU may determine the availability state (e.g., being in an availability state) from detection (e.g., reception) of an availability state indication (ASI) signal. Such a signal may be generated from at least one sequence, such as, for example, any of a Zadoff-Chu, M sequence, and Gold sequence. The WTRU may attempt to detect such a signal during one or more occasions. Such occasions may be tied to (e.g., associated with) SSB (synchronization signal block) transmission times for the serving cell according to a (e.g., defined) timing relationship. Information indicative of any of the timing of the ASI signal occasions and the timing relationship of the ASI signal with the SSB may be received by the WTRU (e.g., may be indicated by higher layers from system information, etc.). The WTRU may determine the availability state (e.g., being in an availability state) based on at least one characteristic of the availability state indication. For example, the at least one characteristic may include any of a parameter, a time offset, and a frequency offset used for generation of the at least one sequence. The parameters and / or offsets may be either predefined and signaled (e.g., indicated) by higher layers such as system information. The indicated availability state may be applicable until the next (e.g., subsequent) ASI signal occasion.

[0121] Example of sending a wake-up request or receiving a wake-up response In one embodiment, the WTRU may determine the availability state (e.g., being in an availability state) after any of transmitting a wake-up request signal and receiving a wake-up response signal. The wake-up response signal may be a DL signal (e.g., or channel) including any of an SSB signal, a reference signal, a measurement resource, a PDCCH transmission, and a PDSCH transmission. In another example, the wake-up response may be indicated by a downlink RRC message. The availability state may be applicable from a delay (which may be zero) after transmitting the wake-up request or receiving the wake-up response. The availability state may be indicated by the wake-up response signal. For example, the WTRU may determine the availability state based on characteristics of the wake-up response signal according to any embodiment described herein for the availability state indication signal.

[0122] Example of higher layer configuration and signaling In one embodiment, the WTRU may determine the availability state (e.g., being in an availability state) based on receiving a (e.g., higher layer) signaling message, such as, for example, an RRC. For example, the WTRU may receive information indicating an initial availability state for the serving cell in an RRC message, such as, for example, any of an RRC connection setup and an RRC (re)configuration message. The information indicating the (e.g., initial) availability state for the serving cell may be received in a broadcast transmission indicating a broadcast configuration. In another example, the WTRU may receive information indicating an availability state to apply upon activation of the serving cell and / or upon switching to the bandwidth portion, for at least one serving cell and bandwidth portion. For example, the WTRU may receive information indicating switching to an availability state in a part of a (e.g., RRC) message (such as, for example, any of a DL DCCH message, a DL Common Control Channel (CCCH) message, an RRC release message, an RRC pause message, and an RRC establishment message confirmation).

[0123] Examples of RRC connection states or modes For example, the WTRU may determine the availability state (e.g., be in an availability state) based on a (e.g., RRC) connection state or mode. For example, the WTRU may determine the availability state (e.g., be in an availability state) from receipt of an indication multiplexed portion of a (e.g., RRC) message. The WTRU may either be configured and predefined with a default availability state that may or may not be specific to (e.g., associated with) a (e.g., certain RRC) state. For example, the WTRU may autonomously determine the availability state after transitioning to an inactive state.

[0124] Default Availability State Examples In one embodiment, the WTRU may determine a default availability state (e.g., be in a default availability state). The WTRU may determine to be in the default availability state after a certain amount of time has elapsed after determining an availability state (e.g., be in an availability state) in accordance with any embodiment described herein. The WTRU may determine to be in the default availability state in a time interval in which an otherwise applicable availability state is not determined. For example, if the WTRU does not detect (e.g., receive) signaling information indicating an availability state in an occasion for a PDCCH or ASI signal, the WTRU may determine a default availability state (e.g., be in a default availability state) for a time interval applicable to the PDCCH or ASI signal, such as the time interval between that occasion and a subsequent occasion.

[0125] Example of determining availability status from lack of ASI signal reception The WTRU may monitor for reception of an availability state indication signal (ASI) or channel from the gNB associated with one or more availability states (e.g., on or microsleep). For example, the WTRU may be configured with (e.g., receive configuration information indicating) any of a periodicity associated with the availability indication signal for each cell, and a monitoring occasion pattern for detection of the availability state indication signal of the cell. The availability state indication signal may be a DL signal (e.g., or channel), including any of an SSB signal, a reference signal, a PDCCH transmission, and a PDSCH transmission. For (e.g., each) cell or carrier, the WTRU may be configured with (e.g., receive configuration information indicating) an association between an SSB (e.g., or other DL signal) and an availability signal for the cell. For example, if the WTRU does not detect (e.g., receive) an availability state indication signal associated with that state (e.g., any of SSB and CSI-RS), the availability state may not be active. For example, the availability state may be any of OFF, micro-sleep, and deep-sleep if the WTRU does not detect (eg, receive) an availability state indication signal associated with the availability state "ON".

[0126] If a signal is measured with a quality metric (e.g., either Radio Signal Received Power (RSRP) and Signal to Interference and Noise Ratio (SINR)) that does not meet a strength condition (e.g., below a (e.g., configured) threshold), the WTRU may determine that an availability status indication signal or a wake-up response signal is not detected (e.g., received).

[0127] For example, the WTRU may use a counter or detection timer before changing the active availability state or making an availability state decision based on the ASI, whereby the WTRU may change the availability state (e.g., only) if the timer expires or if the WTRU counts a number of consecutive missing samples of the availability state indication signal. For example, the WTRU may determine the availability state (e.g., being in an availability state) based on lack of reception of an ASI signal. For example, lack of reception of an ASI signal may be determined based on not detecting (e.g., not receiving) the ASI during a period of time and any of a number of consecutive missing samples of the ASI signal. For example, the WTRU may be configured (e.g., receive configuration information indicating) a period for measuring availability state indication signal samples. If the determined measurement over this period satisfies a condition (e.g., is greater than a threshold), the WTRU may stop or (re)start the detection timer or reset the counter. If the determined measurement of the availability signal over this period does not meet the condition (eg, is below a threshold), the WTRU may increment a counter and / or the WTRU may (re)start a detection timer.

[0128] Example of determining resource availability for an availability state How the WTRU may determine which resources may be available for a (e.g., each) state is described herein. For example, which resources may be available for which state may be based on either explicit configuration information and a time pattern.

[0129] For either the default resources and the additional resources, the WTRU may use one or more of the following techniques to determine whether the resource is available for transmission or reception for a (eg, given) availability state.

[0130] The resource may correspond to any of the following examples:

[0131] In one example, the resources may correspond to physical uplink control channel (PUCCH) resources configured, for example, for any of HARQ-ACK (e.g., semi-persistent scheduling HARQ-ACK), scheduling requests (SR), link recovery requests (LRR), and periodic (e.g., or semi-persistent) CSI.

[0132] In another example, the resources may correspond to physical uplink shared channel (PUSCH) resources configured for configuration grant type 1 and / or type 2, for example.

[0133] In yet another example, the resources may correspond to PRACH resources, e.g., any of the PRACH configurations and a subset of PRACH resources may be configured as being available (e.g., associated with) in (e.g., only in) a subset of availability states.

[0134] In yet another example, the resource may correspond to an SRS resource.

[0135] In yet another example, the resource may correspond to a CSI-RS resource (e.g., configured for any of CSI reporting, beam failure detection or recovery, radio link monitoring, and measurements).

[0136] In yet another example, the resources may correspond to positioning reference signal (PRS) resources.

[0137] In yet another example, the resources may correspond to PDCCH resources and / or an associated core set.

[0138] In yet another example, the resource may correspond to a PDSCH resource (eg, configured for semi-persistent scheduling).

[0139] In yet another example, the resource may correspond to an SSB resource.

[0140] In some embodiments, the WTRU may determine that resources indicated by the DCI (e.g., excluding resources activated by the DCI) may be available for any availability state. For example, the WTRU may determine that resources activated by either the DCI and the MAC CE may be available for any availability state. For example, a subset of uplink resources (e.g., PRACH, PUCCH, or PUSCH) may be activated after successful reception of a gNB response to a wake-up request, such as a DL wake-up signal associated with a wake-up receiver radio at the WTRU. For example, the subset of uplink resources may be activated following transmission of the wake-up signal.

[0141] Explicit Resource Configuration Example In some embodiments, the WTRU may receive (e.g., in an RRC message) configuration information indicating resources that may be available (e.g., associated) for (e.g., each possible) availability state. The WTRU may receive configuration information indicating, for example, resources that may be available in any availability state. Such resources may be referred to as "minimum resources" and resources available in (e.g., only in) a subset of the availability states may be referred to as "additional resources." The configuration may correspond to at least one additional information element for (e.g., each) resource that indicates at least one state in which the resource may be available. In another example, the configuration may correspond to an additional information element that indicates, for (e.g., each) state, resources (e.g., additional resources) available (e.g., associated) to the availability state.

[0142] Examples of additional state-specific parameters In some embodiments, the WTRU may receive information indicating, for at least one parameter of a resource, a configuration of values ​​that the at least one parameter may take for a (e.g., respective) availability state. For example, a periodicity parameter may take a first (second) value in a first (second) availability state. In another example, a parameter indicating a number of ports may take a first (second) value in a first (second) availability state.

[0143] Time Pattern Examples In some embodiments, the WTRU may receive configuration information (e.g., via either RRC and MAC CE) indicating a set of time intervals, e.g., a time pattern for (e.g., each) availability state. Such a time pattern may indicate time intervals during which resources may be available (or may not be available) for an availability state. For example, the time pattern may correspond to a sequence of bits (e.g., a bitmap) corresponding to a respective sequence of time units, such as time symbols, slots, and frames. The WTRU may determine that a resource, such as a periodically or semi-persistently repeated (e.g., repeated) resource, may be available for a (e.g., given) repeated (e.g., repeated) instance if the time pattern indicates that it is (e.g., completely) contained (or partially contained) within a time interval that may indicate availability.

[0144] In the case of PRACH, the WTRU may receive configuration information indicating a subset of PRACH occasions for (eg, each) availability state.

[0145] maximum periodicity In some embodiments, the WTRU may determine that a periodically, or e.g., semi-permanently repeated (e.g., repeated) resource may be available for an availability state if the periodicity of the resource satisfies, e.g., a condition associated with this state (e.g., greater than (or is equal to or greater than) a threshold configured for this state). For example, if the threshold is 2 slots (e.g., per time unit) for an availability state, then the resource may be available in this availability state if its periodicity is equal to or greater than 2 slots (e.g., per time unit) and may not be available otherwise. The condition (e.g., threshold) applicable to (e.g., associated with) a state may be configured by the RRC (e.g., by receiving configuration information indicating the condition) or may be signaled (e.g., indicated) in the MAC CE indicating the availability state.

[0146] Maximum Number of Antenna Ports In one embodiment, the WTRU may determine that a resource may be available for an availability state if, for example, the number of antenna ports associated with or configured for the resource satisfies a condition associated with the state (e.g., is less than (or less than) a threshold configured for the state). The condition (e.g., threshold) applicable to (e.g., associated with) a state may be configured by the RRC (e.g., by receiving configuration information indicating the condition) or may be signaled (e.g., indicated) in the MAC CE indicating the availability state.

[0147] Example of DL resource adaptation per availability state Radio Resource Management (RRM) / Radio Link Management (RLM) / Beam Fault Detection (BFD) For example, a WTRU may be configured with (eg, may receive configuration information indicating) any of different beam failure detection and RLM resources to monitor for each availability state.

[0148] For example, the WTRU may monitor any of the additional RLM, RRM, and BFD resources (e.g., reference signals (RS) or SSBs) after sending a wake-up request signal or after receiving a wake-up request response. Sending a wake-up request from a (e.g., particular) availability state may imply (e.g., indicate) a request for any of the additional RLM, RRM, and BFD resources sent by the network (NW) and monitored by the WTRU.

[0149] SSB / RS For example, the WTRU may be configured with (e.g., may receive configuration information indicating) a different set of SSBs and / or CSI-RS to monitor for each availability state. For example, the WTRU may be configured with (e.g., may receive configuration information indicating) a different monitoring periodicity for the applicable SSBs and / or CSI-RS for each availability state. For example, the WTRU may adjust measurement occasions according to the applicable SSB and / or CSI-RS periodicity associated with the active availability state. For example, the WTRU may measure (e.g., only) SSB and / or CSI-RS samples in occasions applicable to the active availability state. For example, the WTRU may skip configured measurement gaps that may not overlap with applicable SSB and / or CSI-RS occasions in the active availability state according to the configured SSB and / or CSI-RS periodicity associated with the availability state.

[0150] PDCCH Monitoring For example, the WTRU may be configured with (e.g., may receive configuration information indicating) a different set of core sets, search spaces, and / or PDCCH occasions to monitor for each availability state. Within the configured core set or search space, the WTRU may be configured with (e.g., may receive configuration information indicating) a PDCCH occasion mask that may indicate to the WTRU which subset of PDCCH occasions to monitor or skip within the configured core set or search space. For example, the WTRU may monitor the PDCCH in (e.g., only in) occasions applicable to the active availability state. The WTRU may skip PDCCH occasions that may not be transmitted in the active availability state.

[0151] Example of Coordination Between WTRU Power Savings and Availability States In one embodiment, the WTRU may be configured or pre-determined with an association between a WTRU power saving state and an availability state. For example, the WTRU may switch its WTRU power saving state to a state associated with an active availability state. For example, the WTRU may determine the active availability state based on an active WTRU power saving state. For example, the WTRU may determine the active availability state based on a (e.g., signaled) WTRU power saving state WTRU (e.g., based on receiving information indicating the WTRU power saving state). For example, the WTRU may apply associated resource and measurement configurations configured for the availability state and / or the WTRU power saving state. The WTRU power saving state may include at least one of the following examples.

[0152] In an example, the WTRU power saving state may include a DRX state (active vs. inactive).

[0153] In another example, the WTRU power saving state may include a DRX cycle (long vs. short).

[0154] In yet another example, the WTRU power saving state may include primary or secondary DRX.

[0155] In another example, the WTRU power saving state may include an indication of whether the WTRU monitors for a wake-up signal from the network.

[0156] In another example, a WTRU power saving state may be associated with a number of active antenna chains or element(s).

[0157] In another example, the WTRU power saving state may include any of the RRM and RLM mitigation states.

[0158] In another example, the WTRU power saving state may include a PDCCH skip state.

[0159] Example of WUR signal determination In some embodiments, the WUR signal may be a sequence (e.g., any of Zadoff-Chu, m-sequences, and Gold sequences). For example, a set of sequences may be reserved, configured, or used for WUR signal indication. The WTRU may determine a sequence for a WUR transmission within the set of sequences to indicate relevant information regarding the WUR signal, which may include one or more of the following example information:

[0160] In an example, a sequence in the set of sequences may be associated with (e.g., may indicate) a coverage level of the WTRU, which may be determined based on any of: (1) the WTRU's most recent coverage level before the network may transition to an idle state (e.g., a dormant state); (2) the WTRU's most recent coverage level before the WTRU may transition to an idle state (e.g., an inactive state); and (3) proximity to a gNB (e.g., based on the WTRU location and the gNB location).

[0161] In another example, a sequence in the set of sequences may be associated with (e.g., may indicate) a geographic location, and the geographic location information may be determined based on either (1) a zone identification in which the WTRU may be located (e.g., one or more zones may be configured by the gNB and the WTRU may determine a zone (e.g., identification) based on the WTRU location), where each zone (e.g.) may be associated with a sequence; or (2) an absolute WTRU location.

[0162] In yet another example, a sequence in the set of sequences may be associated with (e.g., may indicate) a measurement of a reference signal, which may be measured, for example, periodically by the gNB.

[0163] In yet another example, a sequence in the set of sequences may be associated with (eg, may indicate) a WTRU buffer status.

[0164] In yet another example, a sequence in the set of sequences may be associated with (e.g., may indicate) a traffic type (e.g., any of URLLC, enhanced high speed large capacity (eMBB), and high capacity machine type communications (mMTC)).

[0165] In yet another example, a sequence in the set of sequences may be associated with (e.g., may indicate) a WTRU type (e.g., either a low capability WTRU, a high capability WTRU, etc.), which may be determined based on any of the number of Rx antennas, supported bandwidth, power class, etc.

[0166] In yet another example, a sequence in the set of sequences may be associated with (eg, may indicate) an expected (minimum) bandwidth.

[0167] In yet another example, a sequence in the set of sequences may be associated with (e.g., may indicate) a determined SSB index (or, e.g., preferred beam information).

[0168] In some embodiments, the WUR signal may be a UL signal (e.g., a PRACH, a PUCCH, an SRS, a demodulation reference signal (DMRS), etc.). For example, a set of UL signal resources may be reserved, configured, or used for (e.g., to transmit) the WUR signal indication. For example, the WTRU may determine a UL signal resource for WUR transmission within the set of UL signal resources to indicate related information for the WUR signal.

[0169] Example of WUR signal based on coverage level In some embodiments, the WUR signal may be defined, designed, or configured based on a coverage level of the WTRU. For example, the coverage level of the WUR signal may be determined based on one or more of the following examples:

[0170] In an example, the WUR signal may be determined based on a waveform (e.g., a first waveform may be used when the WTRU is in a first coverage level and a second waveform may be used when the WTRU is in a second coverage level, and the first waveform may be based on Cyclic Prefix OFDM (CP-OFDM) and the second waveform may be based on Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)).

[0171] In another example, the WUR signal may be determined based on the number of repetitions (e.g., if the WTRU is in a worse coverage level, a larger number of repetitions may be used for WUR).

[0172] In yet another example, the WUR signal may be determined based on a sequence length (e.g., if the WTRU is in a first coverage level, a first sequence length may be used for WUR, if the WTRU is in a second coverage level, a second sequence length may be used for WUR, and if the first coverage level is worse than the second coverage level, the first sequence length may be longer than the second sequence length).

[0173] In yet another example, the WUR signal may be determined based on the sequence type.

[0174] In yet another example, the WUR signal may be determined based on the number of tones (e.g., subcarriers) used for WUR.

[0175] In yet another example, the WUR signal may be determined based on the subcarrier spacing used for WUR (e.g., a smaller subcarrier spacing may be used if the WTRU is in a worse (e.g., lower) coverage level).

[0176] Example of gNB response to WUR signal In some embodiments, the WTRU may expect to receive a gNB response after transmitting a WUR signal, and the gNB response may include one or more of the following examples:

[0177] In one example, the gNB response may include an SSB (e.g., an SSB associated with the WUR signal).

[0178] As another example, the gNB response may include information indicating a PDCCH (or search space) associated with the WUR signal.

[0179] In yet another example, the gNB response may include a reference signal associated with the WUR signal (e.g., a tracking reference signal (TRS), any of the CSI-RS, etc.).

[0180] For example, if a gNB response is not detected (e.g., received) within a time window after transmitting a WUR signal, the WTRU may perform one or more of the following example actions.

[0181] In one example of operation, the WTRU may increase the transmit power of the WUR signal (e.g., may increase the transmit power with an offset) for a period of time after the transmission of the WUR ends without receiving a gNB response.

[0182] In another example of operation, the WTRU may increase the coverage level of a wake-up request signal (WUR).

[0183] In yet another example of operation, the WTRU may change the WUR type.

[0184] In yet another example of operation, the WTRU may determine that the serving cell may be out of coverage and may perform an initial cell search.

[0185] Wakeup Request Resource Configuration In some embodiments, the WTRU may receive configuration information indicating one or more wake-up request (WUR) resources. The configuration information may include (e.g., indicate) any of: (i) parameters for initializing at least one sequence; (ii) parameters determining a set of (e.g., possible) time occasions; (iii) frequency domain information; and (iv) spatial filter (beam) information. The configuration information may include (e.g., indicate) parameters that may be used in the WUR procedure, such as, for example, any of: a (e.g., maximum) number of iterations, a value of a “prohibit” timer, and a value of a timer (e.g., time period) for transitioning back to a default availability state.

[0186] The WUR resource configuration information (eg, as illustrated therein) may depend on or be selected based on one or more of the following examples.

[0187] In a first example, the WUR resources may be associated with one or more availability states and may be selected based on the availability state requested by the WTRU.

[0188] In another example, the WUR resource may be associated with a scheduling request.

[0189] In yet another example, the WUR resource may depend on or be selected based on either a logical channel identity and a logical channel priority over which data may be available for transmission (e.g., an SR may be transmitted).

[0190] In yet another example, the WUR resources may be dependent on or selected based on the amount of data available for transmission.

[0191] In yet another example, the WUR resources may depend on or be selected based on the type of trigger (such as any of the triggers described herein).

[0192] In yet another example, the WUR resources may depend on or be selected based on the coverage level as described herein.

[0193] In some embodiments, where the WUR comprises a set of modulated symbols, any of the parameters described above may be encoded and mapped (e.g., associated) to the modulated symbols.

[0194] For example, the WTRU may receive configuration information indicating power control parameters applicable to the WUR. For example, such parameters may include any of an offset P0 to the estimated path loss and an alpha parameter.

[0195] Wake-up request triggers and procedures are described herein.

[0196] Wake-up request triggers and procedures Wake-up request triggers and procedures are described herein.

[0197] Example conditions for sending a wake-up request The WTRU may transmit (eg, trigger the transmission of) a wake-up request signal if one or more of the following example conditions are met:

[0198] In an example, the WTRU may transmit (e.g., trigger the transmission of) a wake-up request signal when new data arrives (e.g., from any subset of data resource bearers (DRBs), SRBs, logical channels (LCHs), and logical channel groups (LCGs), which may be associated with any priority level and index).

[0199] In another example, the WTRU may transmit (e.g., trigger the transmission of) a wake-up request signal in case of transmission on an associated uplink resource (e.g., the WTRU may trigger the wake-up request if it is transmitting a transport block (TB) on a subset of the associated resources (e.g., any of the PUSCH, PUCCH, and PRACH resources).

[0200] In yet another example, the WTRU may transmit (e.g., trigger the transmission of) a wake-up request signal when the amount of buffered data satisfies a condition (e.g., exceeds a threshold). The WTRU may trigger a wake-up request, for example, when the amount of buffered data exceeds a configured or predefined threshold, for example, from any subset of the DRB, LCH, and LCG.

[0201] In yet another example, the WTRU may transmit (e.g., trigger the transmission of) a wake-up request signal when either a buffer status report (BSR) and a SR are triggered (e.g., determined to be transmitted). The WTRU may trigger a wake-up request, for example, when a new BSR and / or a new SR is triggered, e.g., when the new SR is for (e.g., is associated with) a particular SR configuration (e.g., a particular SR resource, etc.).

[0202] In yet another example, the WTRU may transmit (e.g., trigger the transmission of) a wake-up request signal when any of uplink control information (UCI) and data to transmit is available. (For example, the WTRU may trigger a wake-up request when new UCI is to be transmitted depending on any of (i) the UCI type (e.g., any of HARQ ACK, CSI, and Precoding Matrix Indicator (PMI)), (ii) the priority associated with the UCI, and (iii) the LCH and DRB associated with the UCI.)

[0203] In yet another example, the WTRU may transmit (eg, trigger the transmission of) a wake-up request signal upon detection of a beam failure and / or a radio link monitoring (RLM) event.

[0204] In yet another example, the WTRU may transmit (e.g., trigger the transmission of) a wake-up request signal when channel conditions are measured with acceptable or unacceptable quality (e.g., above or below a (e.g., configured) threshold). The channel conditions may include, for example, any condition related to radio / channel conditions, which may be determined by the WTRU based on any of: (1) WTRU measurements (e.g., (i) L1 / SINR / RSRP, (ii) Channel Quality Information / Modulation and Coding Scheme (CQI / MCS), (iii) Channel Occupancy, (iv) Received Signal Strength Indicator (RSSI), (v) Power Headroom and / or Exposure Headroom); (2) L3 / Mobility-based measurements (e.g., RSRP and / or Reference Signal Received Quality (RSRQ)); (3) RLM state; and (4) channel availability in the unlicensed spectrum (e.g., whether the channel is occupied based on a Listen Before Talk (LBT) procedure determination and / or whether the channel is deemed to have experienced (e.g., consistent and durable) LBT failures).

[0205] In yet another example, the WTRU may transmit (eg, trigger the transmission of) a wake-up request signal when an L3 or mobility event is triggered.

[0206] In yet another example, the WTRU may transmit (e.g., trigger the transmission of) a wake-up request signal when a (e.g., consistent, persistent) wake-up request signal is transmitted and a UL LBT failure is detected on the serving cell and / or active BWP.

[0207] In yet another example, the WTRU may transmit (e.g., trigger the transmission of) a wake-up request signal when the WTRU autonomously switches BWP (e.g., upon expiration of a BWP switching timer and / or upon BWP switching due to initiation of a RACH).

[0208] In yet another example, the WTRU may transmit (e.g., trigger the transmission of) a wake-up request signal when it enters any of (e.g., a particular) discontinuous reception (DRX) states, cycles, and power saving modes, including, for example, short and / or long connected mode DRX.

[0209] In yet another example, the WTRU may transmit (e.g., trigger the transmission of) a wake-up request signal when either a tracking area update and a RAN paging area update are triggered (e.g., upon mobility outside the serving RAN paging area to a cell that may not have a WTRU context).

[0210] Example Procedures for Transitioning Between Availability States and Wake-Up Request Retransmission In some embodiments, the WTRU may start a timer (e.g., a "prohibit" timer) upon transmitting a wake-up request after transitioning to an availability state. For example, the WTRU may transition to an availability state associated with the wake-up request upon (e.g., after) transmitting a wake-up request. In another example, the WTRU may transition to an availability state associated with the wake-up request after (e.g., only after) receiving a response from the gNB, which may be any of a PDCCH transmission, a PDSCH transmission, and receipt of any of the control signals and control elements. The WTRU may stop the timer if any of the availability state indications and a response to the wake-up request are received from the gNB. The WTRU may stop the timer upon (e.g., after) receiving a downlink signal from the gNB.

[0211] In some embodiments, the WTRU may transition to a default configured availability state after expiration of the "prohibit" timer or to the state that was active before sending the wake-up request. The WTRU may change its (e.g., RRC) state (e.g., to either inactive or idle mode) after expiration of the "prohibit" timer. For example, the WTRU may transmit another (or second) wake-up request or retransmit it after expiration of the timer with modified transmission parameters including, for example, any of transmit power, timing advance, and spatial filter. For example, the WTRU may set the value of the "prohibit" timer as a random backoff, whereby the random value may be selected between 0 and the (e.g., configured maximum) timer value. The WTRU may retransmit the wake-up request on the supplemental uplink (SUL) after expiration of the "prohibit" timer and / or after a configured number of attempts. For example, the WTRU may send a wake-up request associated with a different availability state, a different transmission / reception point (TRP), and a different carrier after (i) not receiving a response to the wake-up request from the network, (ii) expiration of a "prohibit" timer, and (iii) sending a configured number of wake-up request attempts.

[0212] For example, the WTRU may be configured with (e.g., receive configuration information indicating) a (e.g., maximum) number of allowed wake-up request transmissions. For example, the WTRU may maintain a counter, and the WTRU may increment the counter (e.g., by one) after transmitting a wake-up request. For example, the WTRU may transmit multiple wake-up request signals up to a configured value for the (e.g., maximum) number of allowed wake-up request transmissions. For example, the WTRU may reset the counter upon receiving a response to the wake-up request from the gNB. If the (e.g., maximum) number of allowed wake-up request transmissions is reached, the WTRU may either (i) transition to a default configured availability state for the cell, (ii) transmit a wake-up request signal on a different serving cell and / or TRP, and (iii) change its (e.g., RRC) state.

[0213] Example of resource monitoring and selection by availability state For example, the WTRU may activate or deactivate beam failure detection and / or RLM according to the active availability state. The WTRU may be configured (e.g., receive configuration information indicating) whether RLM and / or bidirectional forwarding detection (BFD) should be used for each availability state. After switching to an availability state, the WTRU may monitor BFD and / or RLM signals if BFD and / or RLM signals are configured (e.g., associated) for the availability state.

[0214] For example, the WTRU may be configured with (e.g., may receive configuration information indicating) different beam failure detection and / or RLM resources to monitor for each availability state. For example, BFD and / or RLM resources may be associated with one or more availability states. The WTRU may use different values ​​for either the BFD timer and BFD threshold depending on the active availability state. The WTRU may apply different values ​​for either the RLM timer and count threshold depending on the active network availability state. The WTRU may suspend BFD and / or RLM when the network (and / or the WTRU) is in the "off" or "deep sleep" availability state.

[0215] In some embodiments, the WTRU may be configured or predefined to initiate cell reselection or SI acquisition procedures after switching to an availability state. For example, the WTRU may further perform any of cell search, initial access, and mobility procedures. For example, the WTRU may be configured (e.g., may receive configuration information indicating) for each availability state whether the WTRU may perform cell reselection. For example, the WTRU may be configured (e.g., may receive configuration information indicating) with alternative serving cells that may be used by the WTRU in the availability state if the WTRU determines that the serving cell may have transitioned to the availability state. For example, the WTRU may initiate a random access procedure to connect to the alternative serving cell.

[0216] In some embodiments, the WTRU may activate or deactivate one or more carriers and / or bandwidth portions (BWPs) on the serving cell according to the active availability state. For example, the WTRU may be configured (e.g., may receive configuration information indicating) for each availability state with a subset of carriers and / or BWPs that the WTRU may deactivate if the WTRU decides to transition to this availability state. For example, the WTRU may reactivate those carriers and / or BWPs if it decides to transition from an availability state to a different state. This may be configured on an active carrier basis. For example, the WTRU may monitor availability signals for availability states for each active component carrier and / or BWP.

[0217] In some embodiments, a subset of the serving cell's uplink resources (e.g., any of the RACH, PUSCH, and PUCCH) may not be used by the WTRU if the WTRU does not receive an availability signal preceding the uplink resources. For example, all uplink resources may not be available for transmission by the WTRU until the next availability signal occasion if an availability signal is not detected. For example, the WTRU may start a timer based on not detecting an availability signal in an availability signal occasion, and the WTRU may not use any uplink resources while such timer is running (e.g., for the time period corresponding to the timer). For example, the WTRU may transition to a C-DRX state (e.g., short DRX or long DRX) based on not detecting an availability signal.

[0218] For example, the WTRU may be configured with a resource configuration that may be used (e.g., may receive configuration information indicating that the resources may be used) for each active availability state, including, for example, any of uplink resources, measurement resources, downlink data resources, and control resources. The WTRU may, for example, activate or deactivate pre-configured resources (e.g., any of RACH, PDCCH, PUCCH, PUSCH, CG, and DL semi-persistent scheduling (SPS) resources) according to the active availability state. The WTRU may not use (for uplink) or monitor (for downlink) resources that may be deactivated based on a transition to an availability state that may not be associated with the resource.

[0219] In some embodiments, the WTRU may be configured to transmit a wake-up request signal on either a normal uplink (NUL) and a supplemental uplink (SUL). For example, the WTRU may transmit a wake-up request signal on the SUL when a channel measurement (e.g., RSRP) is unsatisfactory (e.g., below a (e.g., configured) threshold). The WTRU may transmit a wake-up request signal on the SUL, for example, in a subset of availability states. For example, the WTRU may transmit a wake-up signal on the SUL when the WTRU does not detect an availability indication signal. For example, UL resources on the SUL may be active in (e.g., only in) a subset of (e.g., configured) availability states.

[0220] In some embodiments, for a DRB configured with either carrier aggregation (CA) and DC replication, the WTRU may (e.g., autonomously) deactivate replication if at least one of the legs Ψ associated with the replicated DRB changes availability state (e.g., is turned off or put into sleep mode). For example, the WTRU may apply replication in (e.g., only in) a subset of availability states that may be configured by RRC (e.g., by receiving configuration information). For example, the WTRU may perform DC replication when the master node (MN) and secondary node (SN) are in the same availability state (e.g., “on”).

[0221] In some embodiments, in the case of a split bearer, the WTRU may transmit data (e.g., to both gNBs) in (e.g., only in) a subset of availability states that may be configured by the RRC (e.g., by receiving configuration information). For example, the WTRU may perform normal Packet Data Convergence Protocol (PDCP) split bearer operation if (e.g., only if) the MN and SN are in the same availability state (e.g., "on").

[0222] Example of a wake-up request in RRC inactive and idle In some embodiments, the WTRU may be configured to (e.g., autonomously) switch to a (e.g., RRC) state (e.g., either (e.g., RRC) idle or inactive, etc.) when the availability state is active or is no longer active. For example, the WTRU may switch to either the (e.g., RRC) inactive or idle state based on determining that the availability state is "off."

[0223] For example, a WTRU may be configured with (e.g., receive configuration information indicating) a subset of physical random access channel (PRACH) and / or PUCCH resources (e.g., RACH occasions) that may be used while the WTRU is in an availability state (e.g., either off or deep sleep). The WTRU may not use other RACH occasions when the applicable availability state is active.

[0224] In some embodiments, the WTRU may receive (e.g., consider) the preamble transmission as a wake-up request signal when the WTRU is in a (e.g., RRC) state (e.g., either an (e.g., RRC) idle or inactive state, etc.). For example, the WTRU may initiate an RA procedure based on transmitting (e.g., triggering) a wake-up request (e.g., when a condition for transmitting a wake-up request is met). For example, the WTRU may initiate a new RA procedure when data arrives while in an applicable availability state (e.g., "off" or "deep sleep").

[0225] 3 illustrates an example of a method 300 for network energy conservation. For example, the method may be implemented in a WTRU. In step 310, the WTRU may determine an availability state based on any of the DCI, MAC CE, and signaling. In step 320, the WTRU may determine whether resources may be available based on the availability state. In step 330, the WTRU may transmit a wake-up request signal in response to determining that resources may not be available. In step 340, the WTRU may switch to an availability state in which resources may be available in response to determining that resources may not be available.

[0226] For example, the WTRU may start a timer when it switches to an availability state in which resources may be available.

[0227] For example, in response to expiration of the timer, the WTRU may return to an availability state in which resources may not be available and may transmit another wake-up request signal at a higher power than another power at which the wake-up request signal may have been previously transmitted.

[0228] For example, the WTRU may determine that the WTRU may have transmitted a maximum number of allowed wake-up request signals, and in response to determining that the WTRU may have transmitted a maximum number of allowed wake-up request signals, may perform the following actions: (i) the WTRU may transition to a default configured availability state for the current serving cell, (ii) the WTRU may transmit a wake-up request signal on a different serving cell, (iii) the WTRU may change the WTRU's radio resource control (RRC) state.

[0229] For example, the WTRU may receive an indication of an availability state in which resources may be available, and the WTRU may stop the timer in response to receiving the indication.

[0230] For example, the WTRU may be configured with an association between a WTRU power saving state and an availability state in which the resources may be available. The method may further comprise, in response to determining, by the WTRU, that the resources may not be available, switching to a WTRU power saving state associated with an availability state in which the resources may be available.

[0231] For example, the WTRU may be configured with different resources to monitor for each availability state. The method may further include, in response to determining that the resources may not be available, monitoring, by the WTRU, resources associated with an availability state for which the resources may be available.

[0232] FIG. 4 illustrates another example of a method 400 for network energy savings. For example, the method 400 may be implemented in a WTRU. In step 410, the WTRU may receive first information indicating (i) one or more SR resources and (ii) a set of wake-up request occasions, each SR resource associated with one or more availability levels. In step 420, the WTRU may determine that the WTRU may be at a first level of availability. In step 430, the WTRU may transmit a first wake-up request using a first wake-up request occasion of the set of wake-up request occasions based on a determination that the SR may be transmitted using an SR resource associated with a second level of availability of the one or more levels of availability. In step 440, the WTRU may transmit an SR in an SR resource associated with the second level of availability. In step 450, under the condition that the time period after transmission of the first wake-up request ends without receiving an availability level indication, the WTRU may transmit a second wake-up request using a second wake-up occasion of the set of wake-up request occasions, where the first wake-up request may be transmitted at a first transmit power and the second wake-up request may be transmitted at a second transmit power that may be higher than the first transmit power.

[0233] For example, a first wake-up request occasion may be selected based on a determination that the first wake-up request occasion may be associated with a second level of availability.

[0234] For example, the WTRU may be determined to be at a first level of availability based on receiving a transmission indicating the first level of availability.

[0235] For example, the transmission may comprise a DCI indicating a first level of availability.

[0236] For example, the transmission may comprise a MAC CE indicating a first level of availability.

[0237] For example, the first level of availability may be applicable after receiving a MAC CE indicating the first level of availability or after acknowledging a transmission carrying the MAC CE.

[0238] For example, the transmission may comprise a signal generated from the at least one sequence, and the first level of availability may be determined based on at least one characteristic of the at least one sequence.

[0239] For example, the at least one characteristic may comprise any of a parameter, a time offset, and a frequency offset used to generate the at least one sequence.

[0240] For example, the transmission may comprise an RRC message indicating a first level of availability.

[0241] For example, the WTRU may be determined to be at the first level of availability upon determining that a certain amount of time has elapsed after determining that the WTRU may be at the third level of availability without receiving a transmission indicating any level of availability.

[0242] For example, an SR resource may be associated with a periodicity, and the SR resource may be associated with a second availability level if the periodicity satisfies a condition associated with the second availability level.

[0243] For example, a condition associated with a second availability level may be met if a periodicity associated with the SR resource is greater than or equal to a threshold associated with the second availability level.

[0244] For example, an SR resource may be associated with a number of antenna ports, and the SR resource may be associated with a second level of availability if the number of antenna ports meets a condition associated with the second level of availability.

[0245] For example, a condition associated with a second availability level may be met if the number of antenna ports associated with the SR resource is less than or equal to a threshold associated with the second availability level.

[0246] For example, the first information may further indicate a condition associated with the second level of availability.

[0247] For example, the first level of availability and the second level of availability may be associated with a first power saving state and a second power saving state of the WTRU, respectively.

[0248] For example, the determination that an SR may be transmitted using an SR resource associated with a second level of availability may be based on either the logical channel and the priority of the logical channel on which the SR may be transmitted.

[0249] For example, the method may further comprise determining sequences for the first wake-up request and the second wake-up request within a set of sequences that may be associated with any of: i) coverage level; (ii) geographic location; (iii) reference signal measurements; (iv) buffer status; (v) traffic type; (vi) logical channel or logical channel priority over which the SR may be transmitted; (vii) WTRU type; (viii) requested bandwidth; and (ix) beam information.

[0250] For example, the first information may further indicate parameters for initializing at least one sequence of the set of sequences.

[0251] For example, the method may further comprise initiating cell reselection with an alternative serving cell, which may be associated with a second level of availability.

[0252] For example, the first information may indicate an alternative serving cell to be used at the second level of availability.

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

[0254] Any features, variations, or embodiments described in the methods are compatible with an apparatus device comprising means for processing the disclosed methods, a device comprising circuitry including any of a transmitter, receiver, processor, and memory configured to process the disclosed methods, a computer program product comprising program code instructions, and a non-transitory computer readable storage medium storing the program instructions.

[0255] Although features and elements are provided above in specific combinations, one skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. The present disclosure is not limited in terms of the specific embodiments described in this application, which are intended as illustrations of various aspects. As will be apparent to those skilled in the art, many modifications and variations may be made without departing from the spirit and scope of the present invention. No element, operation, or instruction used in the description of this application should be construed as critical or essential to the invention unless expressly set forth as such. In addition to those enumerated herein, functionally equivalent methods and apparatuses within the scope of the present disclosure will be apparent to those skilled in the art from the foregoing description. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that the present disclosure is not limited to any particular method or system.

[0256] The foregoing embodiments are discussed with respect to the terminology and structure of infrared-enabled devices (i.e., infrared emitters and receivers) for simplicity, however, the discussed embodiments are not limited to these systems and may also be applied to other systems that use other forms of electromagnetic waves, or non-electromagnetic waves such as acoustic waves.

[0257] It should also be understood that the terms used herein are for purposes of describing particular embodiments only and are not intended to be limiting. As used herein, the term "video" or "image" may mean any of a snapshot, a single image, and / or multiple images displayed over time. As another example, the term "user equipment" and its abbreviation "UE", the term "remote" and / or the term "head mounted display" and its abbreviation "HMD" as referred to herein may mean (i) a wireless transmitting and / or receiving unit (WTRU), (ii) any of several embodiments of a WTRU, (iii) a wireless enabled and / or wired enabled (e.g., tetherable) device specifically configured to have some or all of the structure and functionality of a WTRU, (iii) a wireless enabled and / or wired enabled device configured to have less than all of the structure and functionality of a WTRU, or (iv) otherwise. Details of an exemplary WTRU that may represent any WTRU listed herein are provided herein with respect to FIGS. 1A-1D. As another example, various embodiments disclosed herein above and below are described as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than a head-mounted display may be utilized and that the present disclosure and any or all of the various disclosed embodiments may be modified accordingly without undue experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adaptive reality experience.

[0258] In addition, the methods provided 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 over 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 in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, MME, EPC, AMF, or any host computer.

[0259] Modifications of the methods, apparatus, and systems provided above are possible without departing from the scope of the present invention. In view of the wide variety of embodiments that may be applied, it should be understood that the illustrated embodiments are merely examples and should not be construed as limiting the scope of the following claims. For example, the embodiments provided herein include a portable device, which may include or be utilized with any suitable voltage source, such as a battery providing any suitable voltage.

[0260] Further, in the above embodiments, it should be noted that processing platforms, computing systems, controllers, and other devices including processors. These devices may include at least one central processing unit (CPU) and memory. In accordance with the practices of those skilled in the art of computer programming, references to operations and symbolic representations of operations or instructions may be performed by various CPUs and memories. Such operations and operations or instructions may be referred to as being "executed," "computer executed," or "CPU executed."

[0261] Those skilled in the art will appreciate that the operations and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. The electrical system represents data bits that may cause a resultant transformation or reduction of the electrical signals, and maintains the data bits in memory locations of the memory system, thereby reconfiguring or otherwise altering the operation of the CPU and the processing of other signals. The memory locations in which the data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be appreciated that the embodiments are not limited to the platforms or CPUs mentioned above, and that other platforms and CPUs may support the methods provided.

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

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

[0264] There is little distinction between hardware and software implementations of aspects of the system. Whether to use hardware or software is generally a design choice that represents a cost vs. efficiency tradeoff (although in some circumstances the choice between hardware and software may be important). There may be a variety of vehicles (e.g., hardware, software, and / or firmware) in which the processes and / or systems and / or other techniques described herein may be effective, and the preferred vehicle may vary depending on the context in which the processes and / or systems and / or other techniques are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may select a primarily hardware and / or firmware vehicle. If flexibility is paramount, the implementer may select a primarily software implementation. Alternatively, the implementer may select some combination of hardware, software, and / or firmware.

[0265] The foregoing detailed description has illustrated various embodiments of devices and / or processes through the use of block diagrams, flow charts, and / or examples. To the extent that such block diagrams, flow charts, and / or examples include one or more functions and / or operations, it will be appreciated by those skilled in the art that each function and / or operation within such block diagrams, flow charts, or examples may be individually and / or collectively implemented by a wide range of hardware, software, firmware, or substantially any combination thereof. In one embodiment, some portions of the subject matter described herein may be implemented via application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated forms. However, those skilled in the art will recognize that certain aspects of the embodiments disclosed herein may be equivalently implemented, in whole or in part, in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as substantially any combination thereof, and that designing circuitry and / or writing software and / or firmware code is within the skill of those skilled in the art in light of this disclosure. In addition, those skilled in the art will recognize that the subject matter mechanisms described herein may be distributed as program products in a variety of forms, and that representative embodiments of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to actually effect the distribution. Examples of signal bearing media include, but are not limited to, recordable type media such as floppy disks, hard disk drives, CDs, DVDs, digital tape, computer memory, and transmission type media such as digital and / or analog communications media (e.g., fiber optic cables, wave guides, wired communications links, wireless communications links, etc.).

[0266] Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner described herein and then use engineering techniques to integrate such described devices and / or processes into a data processing system. That is, at least a portion of the devices and / or processes described herein may be integrated into a data processing system through a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, memory such as volatile and non-volatile memory, a processor such as a microprocessor and a digital signal processor, computing entities such as an operating system, drivers, graphical user interfaces, and application programs, one or more interactive devices such as a touchpad or screen, and / or a control system including feedback loops and control motors (e.g., feedback to sense position and / or velocity, control motors to move and / or adjust components and / or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing / communication systems and / or network computing / communication systems.

[0267] The subject matter described herein may illustrate different components that are included within or connected to different other components. It should be understood that such illustrated architectures are merely examples, and that in fact many other architectures that achieve the same functionality may be implemented. Conceptually, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Thus, any two components herein that are combined to achieve a particular functionality may be considered to be "associated" with one another such that the desired functionality is achieved, regardless of the architecture or intervening components. Similarly, any two components that are so associated may be considered to be "operably connected" or "operably coupled" with one another to achieve the desired functionality, and any two components that can be so associated may be considered to be "operably couplable" with one another to achieve the desired functionality. Examples of operably coupleable include, but are not limited to, physically matable and / or physically interacting components, and / or wirelessly interactable and / or wirelessly interacting components, and / or logically interacting and / or logically interacting components.

[0268] With respect to the use of substantially any plural and / or singular term herein, those of skill in the art may convert from plural to singular and / or from singular to plural as appropriate to the context and / or application. For purposes of clarity, various singular / plural permutations may be expressly set forth herein.

[0269] In general, those skilled in the art will understand that the terms used in this specification, and particularly in the appended claims (e.g., the body of the appended claims), are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," and the term "includes" should be interpreted as "includes but is not limited to"). Furthermore, those skilled in the art will understand that where a specific number of recitations of an introduced claim are intended, such intention is expressly set forth in the claim, and in the absence of such recitation, no such intention exists. For example, where only one item is intended, the term "single" or similar language may be used. To aid in understanding, the following appended claims and / or the description of this specification may include the use of the introductory phrases "at least one" and "one or more" to introduce the claim recitations. However, the use of such phrases should not be interpreted as meaning that the introduction of a claim recitation with the indefinite article "a" or "an" limits any particular claim that includes such an introduced claim recitation to an embodiment that includes only such one recitation, even if the same claim contains the introductory phrase "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should be interpreted to mean "at least one" or "one or more"). The same applies to the use of definite articles used to introduce claim recitations. In addition, those skilled in the art will recognize that even if a specific number of recitations of an introduced claim are explicitly recited, such recitation should be interpreted to mean at least the recited number (e.g., the simple recitation "two recitations" without any other qualifiers means at least two recitations, or more than two recitations).Furthermore, when notation similar to "such as at least one of A, B, and C" is used, such structure is generally intended as a person of ordinary skill in the art would understand the notation (e.g., "a system having at least one of A, B, and C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). When notation similar to "such as at least one of A, B, or C" is used, such structure is generally intended as a person of ordinary skill in the art would understand the notation (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). Those skilled in the art will further appreciate that virtually any disjunctive word and / or phrase presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" should be understood to include the possibility of "A" or "B" or "A and B." Additionally, as used herein, the term "any of," followed by a list of items and / or a list of categories of items, is intended to include "any of," "any combination of," "any more than," and / or "any more than," of the items and / or categories of items, individually or in combination with other items and / or other categories of items. Additionally, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. Also, as used herein, the term "multiple" is intended to be synonymous with "a plurality."

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

[0271] As will be appreciated by those skilled in the art, for all purposes, including in terms of providing a written description, all ranges disclosed herein also encompass any possible subranges and combinations of subranges thereof. Any recited range can be readily recognized as fully descriptive and allowing the same range to be broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, a middle third, an upper third, etc. As will also be appreciated by those skilled in the art, all words such as "up to," "at least," "greater than," "less than" and the like refer to ranges that include the recited numbers and that can be further broken down into subranges as discussed above. Finally, as will be appreciated by those skilled in the art, a range includes each individual element. Thus, for example, a group having 1 to 3 cells refers to a group having 1, 2, or 3 cells. Similarly, a group having 1 to 5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so on.

[0272] Moreover, the claims should not be read as limited to the provided order or to the provided elements unless specifically so stated. In addition, the use of the term "means for" in any claim is intended to invoke 35 U.S.C. ...

[0273] Suitable processors include, by way of example, 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), an application specific standard product (ASSP), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), and / or a state machine.

[0274] The WTRU may be used in conjunction with hardware and / or software implemented modules, such as, for example, a Software Defined Radio (SDR), and may be implemented in other components, such as a camera, a video camera module, a video phone, a speaker phone, a vibration device, a speaker, a microphone, a television transceiver, a hands-free headset, a keyboard, a Bluetooth module, a Frequency Modulation (FM) radio unit, a Near Field Communication (NFC) module, an LCD display unit, an Organic Light Emitting Diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and / or a Wireless Local Area Network (WLAN) or Ultra Wide Band (UWB) module.

[0275] Although various embodiments have been described with respect to a communications system, it is contemplated that the system may be implemented in software on a microprocessor / general purpose computer (not shown). In particular embodiments, one or more of the functions of the various components may be implemented in software controlling a general purpose computer.

[0276] In addition, although the invention is illustrated and described herein with reference to specific embodiments, the invention is not intended to be limited to the details shown, but rather, various modifications can be made in the details within the scope of the claims and their equivalents and without departing from the invention.

[0277] The following references may be found above: RP-212422”Motivation for Network Energy Saving in Rel-18”,Ericsson.

Claims

1. 1. A wireless transmit / receive unit (WTRU) comprising a circuit including a transmitter, a receiver, a processor, and a memory, the circuit comprising: receiving information via Radio Resource Control (RRC) signaling indicative of a configured pattern of time periods, each time period including intervals during which a cell is available for reception or transmission and intervals during which the cell is not available for reception or transmission; receiving configuration information indicating physical uplink control channel resources (PUCCH resources) for transmission of a scheduling request (SR); receiving downlink control information (DCI) including an indication associated with the configured pattern of time periods, the indicated configured pattern of time periods being applicable after a predefined delay after the DCI is received; determining whether the indication indicates that the configured pattern of time periods is compatible with reception; determining that an SR will be transmitted on one of the PUCCH resources configured for transmission of an SR; determining not to transmit the SR if the PUCCH resource is not within an interval in which the cell is available for reception; It was configured as W.T.R.U.

2. The WTRU of claim 1, wherein the indication associated with the configured pattern of time periods indicates applying the configured pattern of time periods.

3. The WTRU of claim 1, wherein the indication associated with the configured pattern of time periods is received on a group common physical downlink control channel.

4. The WTRU of claim 1 , wherein the circuitry is configured to transmit the SR on a condition that the PUCCH resource is within the interval in which the cell is available for reception.

5. The WTRU of claim 1, wherein the configuration information further indicates physical uplink shared channel resources (PUSCH resources) for transmission of configured grants (CGs).

6. The circuit comprises: determining that a CG is to be transmitted on one of the PUSCH resources configured for transmission of the CG; and determining not to transmit the CG on a condition that the PUCCH resource is not within the interval in which the cell is available for reception. The WTRU of claim 5.

7. The WTRU of claim 1, wherein the configuration information further indicates channel state information (CSI) resources for transmitting CSI reports.

8. The circuit comprises: determining that a CSI report is to be transmitted on one of the CSI resources configured for transmission of a CSI report; and determining not to transmit the CSI report on a condition that the CSI resource is not within the interval in which the cell is available for reception. The WTRU of claim 7.

9. The WTRU of claim 1 , wherein the PUCCH resource configured for transmission of a SR is associated with a periodicity.

10. The circuit comprises: receiving a medium access control (MAC) control element (CE) signal indicating a threshold value for the periodicity of the PUCCH resource; determining that the periodicity of the PUCCH resource is greater than an indicated threshold; and determining to transmit the SR based on the period of the PUCCH resource being greater than the indicated threshold. The WTRU of claim 9.

11. 1. A method implemented in a wireless transmit / receive unit (WTRU), comprising: receiving, via Radio Resource Control (RRC) signaling, information indicative of a configured pattern of time periods, each time period including intervals during which a cell is available for reception or transmission and intervals during which the cell is not available for reception or transmission; receiving configuration information indicating physical uplink control channel resources (PUCCH resources) for transmission of a scheduling request (SR); receiving downlink control information (DCI) including an indication associated with the configured pattern of time periods, the indicated configured pattern of time periods being applicable after a predefined delay after the DCI is received; determining whether the indication indicates that the configured pattern of time periods is suitable for reception; determining that an SR is to be transmitted on one of the PUCCH resources configured for transmission of an SR; determining not to transmit the SR on a condition that the PUCCH resource is not within an interval in which the cell is available for reception; A method for providing the above.

12. The method of claim 11, wherein the indication associated with the configured pattern of time periods indicates applying the configured pattern of time periods.

13. The method of claim 11, wherein the indication associated with the configured pattern of time periods is received on a group common physical downlink control channel.

14. transmitting the SR on the condition that the PUCCH resource is within the interval in which the cell is available for reception. The method of claim 11 further comprising:

15. The method of claim 11, wherein the configuration information further indicates physical uplink shared channel resources (PUSCH resources) for transmission of configured grants (CGs).

16. The method of claim 15, further comprising: determining that a CG is to be transmitted on one of the PUSCH resources configured for transmission of the CG; determining not to transmit the CG on a condition that the PUCCH resource is not within the interval in which the cell is available for reception; The method of claim 15 further comprising:

17. The method of claim 11, wherein the configuration information further indicates channel state information (CSI) resources for transmitting CSI reports.

18. determining that a CSI report is to be transmitted on one of the CSI resources configured for transmission of a CSI report; determining not to transmit the CSI report if the CSI resource is not within the interval in which the cell is available for reception; 20. The method of claim 17 further comprising:

19. The method of claim 11 , wherein the PUCCH resource configured for transmission of a SR is associated with a periodicity.

20. The method of claim 1, further comprising: receiving a medium access control (MAC) control element (CE) signal indicating a threshold value for the period of the PUCCH resource; determining that the periodicity of the PUCCH resource is greater than an indicated threshold; determining to transmit the SR based on the periodicity of the PUCCH resource being greater than the indicated threshold; 20. The method of claim 19 further comprising:

Images