Methods, architectures, apparatuses, and systems for low power wake-up signal (LP-WUS) sequence selection based on energy storage conditions

Abstract

Programs, methods, architectures, apparatus, systems, devices, and computer program products including a wireless transmit / receive unit (WTRU) configured to obtain first information indicating a configuration associated with at least one low power-wakeup signal (LP-WUS) type, wherein the configuration includes at least one reception duration and at least one energy storage threshold; determine activation of LP-WUS monitoring; determine a type of LP-WUS to monitor based on a comparison of an energy storage status of the WTRU to the at least one energy storage threshold; and receive at least one LP-WUS from a network node during the at least one reception duration based on the determined type of LP-WUS and based on the first information.

Description

[0001] Cross-references to related applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 546,340, filed on October 30, 2023, which is incorporated herein by reference in its entirety. Technical Field

[0002] This disclosure generally relates to the fields of communications, software, and coding, including, for example, methods, architectures, apparatuses, and systems for low-power wake-up signal (LP-WUS) sequence types, such as methods, apparatuses, and systems for providing LP-WUS type and duration selection based on wireless transmit / receive unit (WTRU) type and energy storage status. Attached Figure Description

[0003] A more detailed understanding can be obtained by referring to the following detailed description, which is given by way of example in conjunction with the accompanying drawings. Similar to the detailed description, the figures in these drawings are illustrative. Therefore, the figures (FIGs.) and detailed description should not be considered limiting, and other equally valid examples are possible and likely. Furthermore, similar reference numerals (“ref.”) in the figures indicate similar elements, and wherein: Figure 1A This is a system diagram illustrating an example communication system; Figure 1B The illustration can be found Figure 1A The diagram shows a system diagram of an example WTRU used in a communication system. Figure 1C The illustration can be found Figure 1A The diagram shows a system diagram of an example radio access network (RAN) and an example core network (CN) used in a communication system. Figure 1D The diagram can be found Figure 1A The diagram shows another example RAN and another example CN used in the communication system. Figure 2 The illustration shows an example of a receiver architecture for a WTRU (e.g., a UE) that utilizes a low-power wake-up receiver; Figure 3 An example illustrating the generation of a low-power wake-up signal (LP-WUS) in a single bit within a single orthogonal frequency division multiplexing (OFDM) symbol; Figure 4 An example of using frequency domain multiplexing to generate LP-WUS in a single OFDM symbol with multiple bits is illustrated. Figure 5 An example of generating LP-WUS using a multi-tone single bit is shown; Figure 6 An example of using time-domain multiplexing to generate LP-WUS with multiple bits in a single OFDM symbol is illustrated; and Figure 7 The diagram illustrates a procedure for selecting LP-WUS type and duration based on WTRU (e.g., UE) type and energy storage status; and Figure 8 This diagram illustrates another procedure for providing LP-WUS type and duration selection based on WTRU (e.g., UE) type and energy storage status. Detailed Implementation

[0004] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments and / or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, processes, 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 expressly, implicitly, and / or inherently described, disclosed, or otherwise provided (collectively, “Provided”) herein. Although various embodiments are described and / or claimed herein (where apparatuses, systems, devices, etc., and / or any elements thereof perform operations, processes, algorithms, functions, etc., and / or any part thereof), it should be understood that any embodiment described and / or claimed herein assumes that any apparatus, system, device, etc., and / or any element thereof is configured to perform any operation, process, algorithm, function, etc., and / or any part thereof.

[0005] Example Communication System The methods, apparatus, and systems provided herein are well-suited for communications involving both wired and wireless networks. Regarding... Figure 1A-1D An overview of various types of wireless devices and infrastructures is provided, wherein various elements of the network may: utilize, perform, be arranged in accordance with, and / or be adapted to, and / or be configured for use with the methods, apparatuses and systems provided herein.

[0006] Figure 1AThis is a system schematic illustrating an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multi-access system that provides content such as voice, data, video, messages, and broadcasts to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail (ZT) Unique Word (UW) Discrete Fourier Transform (DFT) Spread Spectrum OFDM (ZT UWDTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0007] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, radio access networks (RANs) 104 / 113, core networks (CNs) 106 / 115, public switched telephone networks (PSTNs) 108, the Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include (or be) user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a WTRU (e.g., a UE).

[0008] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d, for example, to facilitate access to one or more communication networks, such as CN 106 / 115, Internet 110, and / or Network 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), node Bs (NBs), eNode Bs (eNBs), home node Bs (HNBs), home eNode Bs (HeNBs), g node Bs (gNBs), NR node Bs (NR NBs), site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each depicted as a single element, it should be understood that base stations 114a and 114b may include any number of interconnected base station and / or network elements.

[0009] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in a desired spatial direction.

[0010] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116. Air interface 116 can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0011] More specifically, as described above, the communication system 100 can be a multi-access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can establish an air interface 116 using Wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access (HSUPA).

[0012] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c may implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which may use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro) to establish air interface 116.

[0013] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can establish an air interface 116 using a new radio (NR).

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

[0015] In one embodiment, base station 114a and WTRUs 102a, 102b, and 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSMEDGE (GERAN), etc.

[0016] For example, Figure 1A Base station 114b can be a wireless router, home node B, home eNode-B, or access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drone use), roads, etc. In one embodiment, base station 114b and WTRUs 102c and 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c and 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In one embodiment, base station 114b and WTRUs 102c and 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of the following: small cells, picocells, or femtocells. Figure 1A As shown, base station 114b can be directly connected to the Internet 110. Therefore, base station 114b may not need to access the Internet 110 via CN 106 / 115.

[0017] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, and / or perform advanced security functions such as user authentication. Although in Figure 1AAlthough not shown, it should be understood that RAN104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which may utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that uses any of the following radio technologies: GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi.

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

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

[0020] Figure 1B This is a system diagram illustrating example WTRU 102. (Example:) Figure 1BAs shown, among other things, WTRU 102 may include, in particular, a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other components / peripherals 138, etc. It should be understood that WTRU 102 may include any sub-combination of the foregoing components while remaining consistent with the embodiments.

[0021] 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. Processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, which may be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it should be understood that the processor 118 and transceiver 120 may be integrated together in, for example, an electronic package or chip.

[0022] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmitting / receiving element 122 can be, for example, a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In one embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF and optical signals. It should be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

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

[0024] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multi-mode capability. Therefore, for example, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0025] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Furthermore, the processor 118 can access and store information from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. 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. Removable memory 132 may include a user identification module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access and store information from memory that is not physically located on WTRU 102 (e.g., a server or home computer (not shown)).

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

[0027] 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) about the current location of the WTRU 102. In addition to, or instead of, information from the GPS chipset 136, the WTRU 102 may receive location information on the air interface 116 from base stations (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method while remaining consistent with the embodiments.

[0028] Processor 118 may be further coupled to other components / peripherals 138, which may include one or more software and / or hardware modules / units providing additional features, functions, and / or wired or wireless connectivity. For example, components / peripherals 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (e.g., for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Components / peripherals 138 may include one or more sensors, such as gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, attitude sensors, biosensors, and / or humidity sensors, etc.

[0029] WTRU 102 may include a full-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for uplink (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and / or substantially eliminate self-interference via hardware (e.g., chokes) or via signal processing by a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, WTRU 102 may include a half-duplex radio for which the transmission and reception of some or all signals (e.g., signals associated with specific subframes for uplink (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0030] Figure 1C This diagram illustrates a system diagram of RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using E-UTRA radio technology. RAN 104 can also communicate with CN 106.

[0031] RAN 104 may include eNode-Bs 160a, 160b, and 160c; however, it should be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. Each eNode-B 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c on air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit and receive radio signals from WTRU 102a.

[0032] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink (UL) and / or downlink (DL), etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other on the X2 interface.

[0033] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (PGW) 166. While each of the foregoing elements is described as part of CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0034] The MME 162 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0035] The SGW 164 can connect to each of the eNode Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions such as anchoring the user plane during eNode-B handover, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0036] SGW 164 can connect to PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks such as Internet 110, so as to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0037] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRU 102a, 102b, and 102c with access to a circuit-switched network such as PSTN 108, facilitating communication between WTRU 102a, 102b, and 102c and traditional landline communication equipment. For example, CN 106 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRU 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0038] Despite WTRU in Figure 1A-1D While described as a wireless terminal, it is conceivable that, in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

[0039] In a representative embodiment, another network 112 may be a WLAN.

[0040] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can access or interface with a distributed system (DS) or another type of wired / wireless network that transmits traffic to and / or out of the BSS. Traffic originating outside the BSS destined for a STA can reach and be delivered to the STA via the AP. Traffic originating from a STA destined for an external BSS can be sent to the AP for delivery to the appropriate destination. For example, traffic between STAs within the BSS can be transmitted via the AP, where the source STA can send traffic to the AP, and the AP can deliver traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be transmitted between source and destination STAs (e.g., directly between them) using Direct Link Establishment (DLS). In some representative embodiments, the DLS can use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode may not have an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode is sometimes referred to here as an "ad-hoc" communication mode.

[0041] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of a fixed width (e.g., a wide bandwidth of 20 MHz) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, each STA, including the AP, can sense the primary channel. If a particular STA senses / detects and / or determines that the primary channel is busy, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0042] High-throughput (HT) STAs can communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels.

[0043] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data passes through a segment resolver, which splits the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. These streams can be mapped onto two 80 MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC) layer, entities, etc.

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

[0045] WLAN systems that can support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include channels that can be designated as the primary channel. The bandwidth of the primary channel can be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by the STA among all STAs operating in the BSS that supports the minimum bandwidth operating mode. In the example of 802.11ah, for STAs that support (e.g., only support) the 1 MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier Sense and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports the 1 MHz operating mode) is transmitting to the AP, the entire available band can be considered busy, even if most of the available band remains idle and can be available.

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

[0047] Figure 1D This diagram illustrates a system diagram of RAN 113 and CN 115 according to one embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR radio technology. RAN 113 can also communicate with CN 115.

[0048] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c on air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from WTRUs 102a, 102b, and 102c. Therefore, for example, gNB 180a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers can be on unlicensed spectrum, while the remaining component carriers can be on licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c can implement Coordinated Multipoint (CoMP) technology. For example, WTRU 102a can receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0049] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with scalable digitization. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing can differ for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., including a variable number of OFDM symbols and / or a continuously variable absolute time).

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

[0051] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing user plane data to User Plane Functions (UPF) 184a and 184b, and routing control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other on the Xn interface.

[0052] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0053] AMF 182a and 182b can connect to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different Protocol Data Unit (PDU) sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, and so on. AMF 182a and 182b can use network slicing, for example, to customize CN support for WTRU 102a, 102b, and 102c based on the service type used by WTRU 102a, 102b, and 102c. For example, different network slices can be established for different use cases, such as services relying on Ultra Reliable Low Latency Time (URLLC) access, services relying on Enhanced Massive Mobile Broadband (eMBB) access, services for MTC access, and / or so on. AMF 162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies such as Wi-Fi.

[0054] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure the routing of services through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating WTRU (e.g., UE) IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0055] UPF 184a and 184b can be connected to one or more gNBs 180a, 180b, and 180c in RAN 113 via the N3 interface. This N3 interface can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as the Internet 110), for example, to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices. UPF 184 and 184b can 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, and providing mobility anchoring.

[0056] CN 115 can facilitate communication with other networks. For example, CN 115 may include, or be able to communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 115 and PSTN 108. Furthermore, CN 115 can provide WTRUs 102a, 102b, and 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, WTRUs 102a, 102b, and 102c may be connected to local data networks (DNs) 185a and 185b via the N3 interface to UPFs 184a and 184b and the N6 interface between UPFs 184a and 184b and DNs 185a and 185b.

[0057] Given Figure 1A-1D as well as Figure 1A-1D The corresponding descriptions herein indicate that one or more of the following functions can be performed by one or more emulation components / devices (not shown): WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF184a-b, SMF 183a-b, DN 185a-b, and / or any other components / devices described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0058] Simulation devices can be designed to perform tests on one or more other devices in laboratory and / or carrier network environments. For example, one or more simulation devices can perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. One or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices can be directly coupled to another device for testing purposes and / or can perform tests using over-the-air wireless communication.

[0059] One or more emulation devices may perform one or more functions, including all functions, rather than being implemented / deployed as part of a wired and / or wireless communication network. For example, emulation devices may be used to test test scenarios in laboratory and / or non-deployment (e.g., testing) wired and / or wireless communication networks to perform testing of one or more components. One or more emulation devices may be test equipment. Emulation devices may transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0060] The following provides acronyms / abbreviations for terms and phrases commonly used in this application: Subcarrier spacing gNB NR NodeB AP non-periodic BFR beam failure recovery BFD-RS Beam Failure Detection - Reference Signal BLER block error rate BWP bandwidth portion CA carrier aggregation CB is based on contention (e.g., access, channel, resources). CCA Idle Channel Assessment CDM (Code Division Multiplexing) CG Community Group CLI Cross-Link Interference CoMP Cooperative Multipoint Transmit / Receive COT channel occupancy time CP cyclic prefix CPE Common Phase Error CP-OFDM vs. Conventional OFDM (depending on the cyclic prefix) CQI Channel Quality Indicator CN core network (e.g., LTE packet core or NR core) CRC Cyclic Redundancy Check CSI Channel State Information CSI-RS Channel State Information - Reference Signal CU Central Unit D2D device-to-device transmission (e.g., LTE side link) DC Dual Connection DCI Downlink Control Information DL downlink DM-RS demodulation reference signal DRB Data Radio Bearer DU Distributed Unit EN-DC E-UTRA–NR Dual Connection EPC Evolved Packet Core FD-CDM Frequency Domain-Code Division Multiplexing FDD (Frequency Division Duplex) FDM (Frequency Division Multiplexing) FSK Frequency Shift Keying ICI inter-cell interference ICIC Inter-cell Interference Cancellation IP Internet Protocol LBT Listen before you speak LCH Logical Channel LCID (Logical Channel Identifier) LCP Logical Channel Priority LLC Low Latency Communication LP-WUS Low Power Wake-up Signal LP-WUR Low Power Wake-up Receiver LTE Long Term Evolution, for example, starting from 3GPP LTE Release 8 and above. MAC Media Access Control MAC CE Media Access Control Element NACK (Negative Response) MBMS Multimedia Broadcasting System MCG Main Cell Group MCS modulation and coding scheme MIMO (Multiple Input Multiple Output) MR main radio MTC Machine Type Communication MR-DC Multi-RAT Dual Connection NAS Non-Access Layer NCB-RS New Candidate Beam - Reference Signal NE-DC NR-RAN–E-UTRA Dual Connectivity NR New Radio NR-DC Dual Connection OCC Orthogonal Cover Code OFDM (Orthogonal Frequency Division Multiplexing) OFDMA (Orthogonal Frequency Division Multiple Access) Out-of-band (OOB) emission OOK On / Off Key Control Pcmax is the total available WTRU (e.g., UE) power within a given transmission interval. The primary cell in the Pcell primary cell group PCG Main Cell Group PDU Protocol Data Unit PER (Passive Error Rate) PHY physical layer PLMN Public Land Mobile Network PLR packet loss rate PRACH (Physical Random Access Channel) PRB (Physical Resource Block) PRI PUCCH resource indicator PRS Positioning Reference Signal Primary cell in Pscell secondary cell group PSS Master Synchronization Signal PT-RS Phase Tracking Reference Signal QoS (Quality of Service) from a physical layer perspective RAB Radio Access Bearer RAN PA (Radio Access Network) Paging Area RACH (Random Access Channel or Procedure) RAR Random Access Response RAT Radio Access Technology RB resource block RCU Radio Access Network Central Unit RF radio front end RE Resource Elements RLF radio link failure RLM radio link monitoring RNTI Radio Network Identifier RO random access timing ROM read-only mode (for MBMS) RRC Radio Resource Control RRM Radio Resource Management RS reference signal RSRP reference signal received power RSRQ reference signal reception quality RTT round trip time SBFD Subband Non-overlapping Full-Duplex SCG auxiliary community group SCMA (Single Carrier Multiple Access) SCS Subcarrier Spacing SDU Service Data Unit SI System Information SOM Spectrum Operation Mode SP Semi-Persistent The primary cell in a SpCell primary or secondary cell group SRB signaling radio bearer SS synchronization signal SRS Detection Reference Signal SSS auxiliary synchronization signal SUL supplements uplink SWG switching interval (in a self-contained subframe) TB transfer block TBS (Transfer Block Size) TCI Transport Configuration Index TDD (Time Division Duplex) TDM (Time Division Multiplexing) TI time interval (represented as an integer multiple of one or more symbols) TTI (Transmission Time Interval) (expressed as an integer multiple of one or more symbols) TRP Transmit / Receive Point TRPG Transmit / Receive Point Group TRS Tracking Reference Signal TRx transceiver UL uplink URC Ultra-Reliable Communication URLLC Ultra-Reliable Low Latency Communication V2X vehicle communication WLAN (Wireless Local Area Network) and related technologies (IEEE 802.xx domain) XDD Cross-duplex.

[0061] A WTRU (e.g., a UE) can transmit or receive a physical channel or reference signal based on at least one spatial domain filter. The term "beam" can be used to refer to a spatial domain filter.

[0062] A WTRU (e.g., a UE) can transmit a physical channel or signal using the same spatial domain filter used to receive RS (such as CSI-RS) or SS blocks. The WTRU (e.g., the UE) transmission can be referred to as the "target," and the received RS or SS block can be referred to as the "reference" or "source." In this context, it can be said that the WTRU (e.g., the UE) transmits a target physical channel or signal based on the spatial relationship referencing such an RS or SS block.

[0063] A WTRU (e.g., a UE) can transmit a first physical channel or signal based on the same spatial domain filter used to transmit a second physical channel or signal. The first transmission and the second transmission can be referred to as the “target” and the “reference” (or “source”), respectively. In this case, it can be said that the WTRU (e.g., the UE) transmits the first (target) physical channel or signal based on a spatial relationship referencing the second (reference) physical channel or signal.

[0064] Spatial relationships can be implicit, configured by the RRC, or signaled by the MAC CE or DCI. For example, a WTRU (e.g., a UE) can transmit DM-RS for PUSCH and PUSCH based on the same spatial domain filter as SRS (e.g., implicitly), with SRS indicated by an SRI in the DCI or configured by the RRC. In another example, spatial relationships can be configured by the RRC for an SRS resource indicator (SRI) or signaled by the MAC CE for PUCCH. This type of spatial relationship can also be referred to as "beam indication".

[0065] The WTRU (e.g., a UE) can receive a first (target) downlink channel or signal based on the same spatial domain filter or spatial reception parameters as the second (reference) downlink channel or signal. For example, this association can exist between a physical channel such as PDCCH or PDSCH and its corresponding DM-RS. This association can exist at least when the first and second signals are reference signals, and when the WTRU (e.g., a UE) is configured with a quasi-co-location (QCL) assumption type D between corresponding antenna ports. This association can be configured as a TCI (Transmission Configuration Indicator) state. The WTRU (e.g., a UE) can be indicated by an index to a set of TCI states configured by RRC and / or signaled by the MAC CE, indicating the association between the CSI-RS or SS block and the DM-RS. This indication can also be referred to as a "beam indication".

[0066] Subsequently, a TRP (e.g., a transmit and receive point) may be used interchangeably with one or more of the following: TP (transmit point), RP (receive point), RRH (remote radio head), DA (distributed antenna), BS (base station), sector (a sector of a BS), and cell (e.g., the geographic cell area served by a BS), but still consistent with the present invention. Subsequently, multiple TRPs may be used interchangeably with one or more of MTRP, M-TRP, and multiple TRPs, but still consistent with the present invention.

[0067] The WTRU (e.g., UE) may report a subset of Channel State Information (CSI) components, wherein the CSI components may correspond at least to the CSI-RS Resource Indicator (CRI), the SSB Resource Indicator (SSBRI), an indication of the panel used for reception at the WTRU (e.g., UE) (such as panel identifier or group identifier), measurement results such as L1-RSRP, L1-SINR obtained from the SSB or CSI-RS (e.g., cri-RSRP, cri-SINR, ssb-Index-RSRP, ssb-Index-SINR), and other channel state information, at least such as the Rank Indicator (RI), Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Layer Index (LI), and / or the like.

[0068] A WTRU (e.g., a UE) can receive synchronization signal / physical broadcast channel (SS / PBCH) blocks. An SS / PBCH block (SSB) can include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The WTRU (e.g., a UE) can monitor, receive, or attempt to decode SSBs during initial access, initial synchronization, radio link surveillance (RLM), cell search, cell handover, etc.

[0069] WTRU (e.g., UE) can measure and report channel state information (CSI), wherein the CSI for each connection mode may include or be configured with one or more of the following: (1) CSI reporting configuration; (2) CSI-RS resource set; and / or (3) NZP CSI-RS resource.

[0070] CSI report configuration may include one or more of the following: (1) CSI report quality (e.g., Channel Quality Indicator (CQI), Rank Indicator (RI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), Layer Indicator (LI), etc.); (2) CSI report type (e.g., aperiodic, semi-persistent, periodic); (3) CSI report codebook configuration (e.g., Type I, Type II, Type II port selection, etc.); and / or (4) CSI report frequency.

[0071] The CSI-RS resource set may include one or more of the following CSI resource settings: (1) NZP-CSI-RS resources for channel measurements; (2) NZP-CSI-RS resources for interference measurements; and / or (3) CSI-IM resources for interference measurements.

[0072] NZP CSI-RS resources may include one or more of the following: (1) NZP CSI-RS resource ID; (2) periodicity and offset; (3) QCL information and TCI-status; and / or (4) resource mapping, such as number of ports, density, CDM type, etc.

[0073] A WTRU (e.g., a UE) may indicate, determine, or be configured with one or more reference signals. The WTRU (e.g., a UE) may monitor, receive, and measure one or more parameters based on the corresponding reference signals. For example, one or more of the following may be applicable. The following parameters are non-limiting examples of parameters that may be included in the measurement results of the reference signals(s). One or more of these parameters may be included. Other parameters may be included.

[0074] The SS reference signal received power (SS-RSRP) can be measured based on a synchronization signal (e.g., the demodulated reference signal (DMRS) in the PBCH or SSS). It can be defined as a linear average of the power contributions of the resource elements (REs) carrying the corresponding synchronization signal. Power scaling of the reference signal may be necessary when measuring RSRP. If SS-RSRP is used for L1-RSRP, the measurement can be performed based on a CSI reference signal other than the synchronization signal.

[0075] CSI-RSRP can be measured by linear averaging of the power contribution of the resource element (RE) carrying the corresponding CSI-RS. CSI-RSRP measurement can be configured within the measurement resources at the configured CSI-RS timing.

[0076] The signal-to-interference-plus-noise ratio (SS-SINR) can be measured based on a synchronization signal (e.g., DMRS in PBCH or SSS). It can be defined as the linear average of the power contribution of the resource element (RE) carrying the corresponding synchronization signal divided by the linear average of the noise and interference power contributions. If SS-SINR is used for L1-SINR, noise and interference power measurements can be performed based on resources configured by higher layers.

[0077] CSI-SINR can be measured by dividing the linear average of the power contribution of the resource element (RE) carrying the corresponding CSI-RS by the linear average of the noise and interference power contributions. If CSI-SINR is used for L1-SINR, noise and interference power measurements can be performed based on resources configured by higher layers. Otherwise, noise and interference power can be measured based on resources carrying the corresponding CSI-RS.

[0078] The Received Signal Strength Indicator (RSSI) can be measured based on the average total power contribution in the configured OFDM symbols and bandwidth. Power contributions can be received from different resources (e.g., co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.).

[0079] The average measurement of the cross-layer interference received signal strength indicator (CLI-RSSI) in the configured OFDM symbols based on the configured time and frequency resources can be performed. Power contributions can be received from different resources (e.g., cross-layer interference, co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc.).

[0080] The detection reference signal RSRP (SRS-RSRP) can be measured based on the linear average of the power contribution of the resource element (RE) carrying the corresponding SRS.

[0081] The secondary synchronization signal reference signal reception quality (SS-RSRQ) can be measured based on the results of measurements of the reference signal received power (SS-RSRP) and received signal strength (RSSI). In one example, SS-RSRQ can be calculated as the ratio of N × SS-RSRP / NR carrier RSSI, where N can be determined based on the number of resource blocks in the corresponding NR carrier RSSI measurement bandwidth. Accordingly, the measurement results used in the numerator and denominator can be on the same set of resource blocks.

[0082] CSI Reference Signal Received Quality (CSI-RSRQ) can be measured based on measurements of the CSI-RSRP and RSSI. In one example, SS-RSRQ can be calculated as the ratio of N × CSI-RSRP / CSIRSSI, where N can be determined based on the number of resource blocks in the corresponding CSI-RSSI measurement bandwidth. Accordingly, the measurements used in the numerator and denominator can be from the same set of resource blocks.

[0083] CSI report configurations (e.g., CSI-ReportConfigs) can be associated with a single BWP (e.g., indicated by BWP-Id) where one or more of the following parameters are configured: (1) CSI-RS resources and / or CSI-RS resource sets used for channel and interference measurements; (2) CSI-RS report configuration type, including periodic, semi-persistent, and aperiodic; (3) CSI-RS transmission periodicity for periodic and semi-persistent CSI reports; (4) periodic, semi-persistent, and aperiodic CSI reports. (5) CSI-RS transmission slot offset list for semi-persistent and non-periodic CSI reports; (6) time constraints for channel and interference measurements; (7) reporting band configuration (wideband / subband CQI, PMI, etc.); (8) thresholds and calculation modes for the number of reports (CQI, RSRP, SINR, LI, RI, etc.); (9) codebook configuration; (10) group-based beam reporting; (11) CQI table; (12) subband size; (13) non-PMI port indication; and / or (14) port index.

[0084] A CSI-RS resource set (e.g., NZP-CSI-RS-ResourceSet) may include one or more of the CSI-RS resources (e.g., NZP-CSI-RS-Resource and CSI-ResourceConfig), wherein a WTRU (e.g., UE) may be configured in the CSI-RS resource with one or more of the following: (1) CSI-RS periodicity and slot offset of periodic and semi-persistent CSI-RS resources; (2) CSI-RS resource mapping for defining the number, density, CDM type, OFDM symbol and subcarrier occupancy of CSI-RS ports; (3) the bandwidth portion allocated to the configured CSI-RS; and / or (4) a reference to the TCI-state, including (multiple) QCL source RSs and (multiple) corresponding QCL types.

[0085] A WTRU (e.g., a UE) may be configured with one or more RS resource sets. The RS resource set configuration may include one or more of the following: (1) RS resource set ID; (2) one or more RS resources of the RS resource set; (3) repetition (i.e., on or off); (4) non-periodic trigger offset (e.g., one of 0-6 time slots); and / or (5) TRS information (e.g., true or false).

[0086] A WTRU (e.g., a UE) may be configured with one or more RS resources. RS resource configuration may include one or more of the following: (1) RS resource ID; (2) resource mapping (e.g., RE in PRB); (3) power control offset (e.g., a value of -8, ..., 15); (4) power control offset with SS (e.g., -3 dB, 0 dB, 3 dB, 6 Db); (5) scrambling code ID; (6) periodicity and offset; and / or (7) QCL information (e.g., based on TCI state).

[0087] In the following, the nature of the grant or assignment may include information indicating any of the following: (1) frequency allocation; (2) aspects of time allocation, such as duration; (3) priority; (4) modulation and coding scheme; (5) transport block size; (6) number of spatial layers; (7) number of transport blocks; (8) TCI status, CRI or SRI; (9) number of repetitions; (10) whether the repetition scheme is type A or type B; (11) whether the grant is a configured grant type 1, type 2 or dynamic grant; (12) whether the assignment is a dynamic assignment or a semi-persistent scheduling (configured) assignment; (13) the configured grant index or semi-persistent assignment index; (14) the periodicity of the configured grant or assignment; (15) channel access priority category (CAPC); and / or (16) any parameters provided in the DCI by the MAC or RRC for scheduling grant or assignment.

[0088] In the following, indications made via DCI may include information indicating any of the following: (1) (e.g., explicit) indications made via DCI fields or via RNTIs for masking or scrambling DCIs; and / or (2) (e.g., implicit) indications made via properties such as DCI format, DCI size, core set or search space, aggregation level, first resource element of the received DCI (e.g., index of the first control channel element), wherein the mapping between properties and values ​​may be signaled by RRC or MAC.

[0089] Receiving or monitoring DCI by means of or using RNTI may mean masking or scrambling the CRC of DCI by means of RNTI.

[0090] Subsequently, the signal may be used interchangeably with one or more of the following: (1) sounding reference signal (SRS); (2) channel state information-reference signal (CSI-RS); (3) demodulation reference signal (DM-RS); (4) phase tracking reference signal (PT-RS); and / or (5) synchronization signal block (SSB).

[0091] Subsequently, the channel may be used interchangeably with one or more of the following: (1) Physical Downlink Control Channel (PDCCH); (2) Physical Downlink Shared Channel (PDSCH); (3) Physical Uplink Control Channel (PUCCH); (4) Physical Uplink Shared Channel (PUSCH); and / or (5) Physical Random Access Channel (PRACH).

[0092] Subsequently, signals, channels, and messages (e.g., in DL or UL signals, channels, and messages) may be used interchangeably, but still in accordance with the present invention.

[0093] Subsequently, RS can be used interchangeably with one or more of RS resources, RS resource sets, RS ports, and RS port groups, but still in accordance with the present invention.

[0094] Subsequently, RS can be used interchangeably with one or more of SSB, CSI-RS, SRS, DM-RS, TRS, PRS and PTRS, but still in accordance with the present invention.

[0095] In this document, time instances, time slots, symbols, and subframes can be used interchangeably, but are still consistent with the present invention.

[0096] In this document, the terms SSB, SS / PBCH block, PSS, SSS, PBCH, and MIB are used interchangeably and remain consistent with the present invention.

[0097] Subsequently, the proposed embodiments for beam resource prediction can be used for beam resources belonging to a single or multiple cells and a single or multiple TRPs, and remain consistent with the present invention.

[0098] Subsequently, CSI reports can be used interchangeably with CSI measurements, beam reports, and beam measurements, but still in accordance with the present invention.

[0099] Subsequently, RS resource sets can be used interchangeably with beam groups, but still consistent with the present invention.

[0100] Figure 2 The diagram illustrates a simplified receiver architecture for a WTRU (e.g., a UE) that utilizes a low-power wake-up receiver.

[0101] Low-power wake-up signal (LP-WUS) monitoring has the potential to reduce power consumption in WTRUs (e.g., UEs) and other small battery-powered devices. This is achieved by using a separate ultra-low-power receiver that monitors the wake-up signal (WUS) and triggers the main radio (MR) dedicated to data and control signal transmission / reception, such as... Figure 2 As shown in the image.

[0102] Within 3GPP, a RAN-level study for environmental IoT was approved in RAN#97e (RP-222685) with the following device characteristics. This study considers the following three types of identified devices: Device A: No energy storage, no independent signal generation / amplification, i.e., backscatter transmission.

[0103] Device B: It has energy storage but no independent signal generation; that is, it uses backscatter transmission. The stored energy can be used to amplify the reflected signal.

[0104] Device C: It has energy storage and independent signal generation, i.e., an active RF component for transmission.

[0105] Although Rel-18 LP-WUS only considers low-power receivers without energy harvesting, support for energy harvesting receivers has been considered from the outset. Furthermore, Rel-19 will likely support environmental IoT with energy harvesting receivers. Since environmental IoT considers similar low-power devices with LP-WUS, it may be obvious that an extension of LP-WUS supporting energy harvesting devices identified in environmental IoT would be appropriate.

[0106] For energy harvesting equipment, support for energy harvesting sequences prior to LP-WUS is required. However, supporting energy harvesting sequences requires additional overhead and energy consumption at network nodes (e.g., gNBs). Therefore, supporting different sequences based on WTRU (e.g., UE) type and corresponding conditions may be beneficial.

[0107] Methods and apparatus may be provided that allow a WTRU (e.g., a UE) to support an energy harvesting receiver as an LP-WUR.

[0108] According to certain embodiments, determination of LP-WUS sequence type and duration based on WTRU (e.g., UE) type and energy storage status report via LP-WUS can be provided.

[0109] According to some embodiments, LP-WUS sequence selection during the activation process can be provided based on energy storage status.

[0110] According to some embodiments, an LP-WUS activation procedure can be provided that indicates the status of the WTRU (e.g., UE) and the corresponding time duration when the WTRU (e.g., UE) is not ready.

[0111] Methods and apparatus are provided for determining LP-WUS back-off based on energy storage conditions.

[0112] WTRU (e.g., UE) can indicate the WTRU (e.g., UE) capability for operation of WTRU (e.g., UE) without energy harvesting for different energy levels.

[0113] For example, a WTRU (e.g., a UE) can indicate the potential operating durations X1a and X2a of energy storage status (e.g., 75% and 50%, respectively).

[0114] The WTRU (e.g., UE) may receive LP-WUS configuration, for example, from a network node (e.g., gNB), including operating durations X1b and X2b for energy storage conditions (e.g., for 75% and 50% respectively), DL resources for each LP-WUS type (e.g., first type LP-WUS and second type LP-WUS), and UL resources. For example, X1b and X2b may be less than X1a and X2a, respectively.

[0115] The WTRU (e.g., UE) can receive LP-WUS activation messages from a network node (e.g., gNB).

[0116] Based on the activation message, if the WTRU (e.g., UE) is a first-type WTRU (e.g., UE) (e.g., capable of energy storage and indicating energy storage status), then the WTRU (e.g., UE) can indicate its energy storage status in the UL resource.

[0117] WTRU (e.g., UE) can monitor LP-WUS based on the indicated energy storage status and WTRU (e.g., UE) type.

[0118] If the WTRU (e.g., UE) is a first-type WTRU (e.g., UE) (e.g., capable of energy storage and indicating energy storage status), then the WTRU (e.g., UE) supports the following operations.

[0119] If the indicated energy storage condition is greater than a first threshold (e.g., 75%), the WTRU (e.g., UE) may receive a first type of LP-WUS (e.g., LP-WUS without an energy harvesting sequence) during the X1b duration based on the LP-WUS configuration. After the X1b duration, the WTRU (e.g., UE) may receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence).

[0120] If the indicated energy storage condition is greater than a second threshold (e.g., 50%) (and, for example, less than a first threshold), the WTRU (e.g., the UE) can receive a first type of LP-WUS (e.g., LP-WUS without an energy harvesting sequence) during the X2b duration based on the LP-WUS configuration. After the X2b duration, the WTRU (e.g., the UE) can receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence).

[0121] If the indicated energy storage condition is less than (or equal to) a second threshold (e.g., 50%), the WTRU (e.g., UE) may receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence).

[0122] WTRU (e.g., UE) can monitor LP-WUS based on the determined LP-WUS type.

[0123] When a WTRU (e.g., a UE) receives an LP-WUS in a defined LP-WUS resource, the WTRU (e.g., a UE) can monitor the PDCCH associated with the paging.

[0124] Methods and apparatus are provided for determining the LP-WUS sequence type and duration based on WTRU (e.g., UE) type and energy storage status.

[0125] The WTRU (e.g., UE) can receive the LP-WUS configuration from the network node (e.g., gNB). The LP-WUS configuration includes time (e.g., periodicity and offset) and frequency resources, as well as UL resources, for each LP-WUS type (e.g., first type LP-WUS and second type LP-WUS).

[0126] The WTRU (e.g., UE) can receive LP-WUS activation messages from a network node (e.g., gNB).

[0127] According to some embodiments, network nodes (e.g., gNBs) may indicate the LP-WUS type.

[0128] According to some embodiments, the WTRU (e.g., UE) can activate LP-WUS with a default type.

[0129] WTRU (e.g., UE) can monitor LP-WUS in time and frequency resources and can indicate energy storage status to network nodes (e.g., gNB) in UL resources.

[0130] If the indicated energy storage condition is greater than a first threshold (e.g., 75%), the WTRU (e.g., UE) may monitor the first type of LP-WUS (e.g., LP-WUS without an energy harvesting sequence) until the next energy storage condition indication.

[0131] If the indicated energy storage condition is greater than a second threshold (e.g., 50%) (and less than a first threshold), the WTRU (e.g., UE) may receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence) until the next energy storage condition indication.

[0132] If the indicated energy storage status is less than (or equal to) a second threshold (e.g., 50%), then the WTRU (e.g., UE) activates MR.

[0133] WTRU (e.g., UE) can monitor LP-WUS based on the determined LP-WUS type.

[0134] When a WTRU (e.g., a UE) receives an LP-WUS or activates an MR based on an indicated energy storage condition, the WTRU (e.g., a UE) can monitor the PDCCH associated with the paging.

[0135] A method and apparatus are provided for confirming LP-WUS activation based on energy storage status.

[0136] The WTRU (e.g., UE) can receive the configuration of LP-WUS, which includes DL resources and UL resources for LP-WUS monitoring.

[0137] The WTRU (e.g., UE) can receive LP-WUS activation messages from a network node (e.g., gNB).

[0138] WTRU (e.g., UE) can determine the energy storage status and indicate whether it is ready based on the energy storage status in UL resources.

[0139] If the determined energy storage status is greater than a threshold (e.g., 50%), the WTRU (e.g., UE) can indicate readiness and can monitor LP-WUS in the configured DL resources.

[0140] If the determined energy storage status is less than (or equal to) a threshold (e.g., 50%), the WTRU (e.g., UE) can indicate that it is not ready and the time offset for the next indication (e.g., another ACK / NACK) from the WTRU (e.g., UE).

[0141] A WTRU (e.g., a UE) can indicate another WTRU (e.g., a UE) based on an updated energy storage status.

[0142] WTRU (e.g., UE) can monitor LP-WUS after indicating that it is ready.

[0143] When a WTRU (e.g., a UE) receives LP-WUS in LP-WUS resources, the WTRU (e.g., a UE) can monitor the PDCCH associated with paging.

[0144] According to some embodiments, LP-WUS can be generated using one or more of the following waveforms: (1) where K can be the size of the IFFT of CP-OFDMA, N can be the number of SCs used by LP-WUS, including potential guard bands; (2) OOK; (3) FSK; (4) CP-OFDM (OFDMA); and / or (5) a mixed waveform.

[0145] OOK can include any of the following options: (1) option OOK-1; (2) option OOK-2; (3) option OOK-3; and / or (4) option OOK-4.

[0146] Option OOK-1 (Broadband Transmission) (e.g.) Figure 3 The diagram in the figure can correspond to a single bit in an OFDM symbol. The SC of LP-WUS can be: (1) OOK=1 means that all SCs are modulated; (2) OOK=0 means that all SCs are zero power (from the perspective of baseband).

[0147] Option OOK-2 (e.g.) Figure 4 The diagram (as shown in the figure) corresponds to a parallel M-bit OOK in the frequency domain. The N SCs of LP-WUS can be further divided into M segments (M=2 in the diagram), which may have guard bands between and / or around them. OOK=1 means that all SCs in the segment are modulated. OOK=0 means that all SCs in the segment are at zero power (from a baseband perspective). Option OOK-3 (e.g.) Figure 5 The diagram shown in the image corresponds to a multi-tone single-bit OOK. The N SCs of LP-WUS can be divided into L segments (in...). Figure 5 Above, L=2), there is no guard band between segments, but there may be guard bands around the segments. OOK=1 can mean that one subcarrier in each segment (known to the UE) is modulated, and the remaining SCs are at zero power (from the baseband perspective). OOK=0 can mean that all SCs in all segments are at zero power (from the baseband perspective).

[0148] Option OOK-4 (e.g.) Figure 6(As shown in the diagram) M-bit OOK can be transformed in the time domain: The N SCs of OOK-1 can be generated by a transform (DFT / least squares method). N' samples can be generated from M bits. Signal modification may or may not be used. Truncation or other additional modifications may or may not be used; if not, N can be the same as N'. N' can be the same as K.

[0149] FSK may include any of the following options: (1) option FSK-1; (2) option FSK-2.

[0150] In option FSK-1, the N SCs of LP-WUS can be divided into M pairs of segments, with potential guard bands between and around these segments. A segment can include a subcarrier or multiple consecutive SCs. In a pair of segments, one segment can be modulated, and the other segment can be zero power (from a baseband perspective).

[0151] In option FSK-2, the N SCs of LP-WUS can be divided into 2^M segments, with potential guard bands between and around these segments. A segment can include a subcarrier or multiple consecutive SCs. One segment from the 2^M segments can be modulated, while the other segments of the SCs can be at zero power (from a baseband perspective).

[0152] In one example, CP-OFDM (OFDMA) can be used for LP-WUS generation. OFDM-based modulation symbols and / or sequences (e.g., PSS and / or SSS sequences) can be used for CP-OFDM (OFDMA)-based LP-WUS.

[0153] In one example, the mixed waveform can be used for LP-WUS generation. For instance, a combination of OOK and OFDMA can be used by applying an OFDM sequence on top of OOK modulation. In another example, a combination of OOK and FSK can be used.

[0154] According to some embodiments, a WTRU (e.g., a UE) may be configured with one or more LP-WUS monitoring configurations. For example, a monitoring type (e.g., continuous or duty cycle), monitoring window (periodic and / or offset), LP-WUS bandwidth, low-power synchronization signal (LP-SS) configuration, etc., may be configured. If the WTRU (e.g., a UE) receives / detects one or more LP-WUS, the WTRU (e.g., a UE) may apply one or more of the following procedures after receiving / detecting one or more LP-WUS: (1) monitoring the PDCCH; (2) applying system information (SI) updates; and / or (3) applying paging-related information updates.

[0155] According to some embodiments, the WTRU (e.g., UE) can wake up (e.g., activate the primary radio (MR) and / or deactivate the low-power wake-up receiver (LP-WUR)) and begin monitoring the PDCCH (e.g., for paging).

[0156] According to some embodiments, the WTRU (e.g., UE) may apply an update to the SI based on the received LP-WUS. In one example, the WTRU (e.g., UE) may apply one or more indicated SI sets (e.g., via LP-WUS) after receiving one or more LP-WUS. In another example, the WTRU (e.g., UE) may receive the updated SI (e.g., via LP-WUS and / or PDSCH after activating MR).

[0157] According to some embodiments, the WTRU (e.g., UE) may apply updates to paging-related information based on received LP-WUS. In one example, the WTRU (e.g., UE) may apply one or more indicated sets of paging-related information (e.g., via LP-WUS) after receiving one or more LP-WUS. In another example, the WTRU (e.g., UE) may receive updated paging-related information (e.g., via LP-WUS and / or PDSCH after MR activation).

[0158] If the WTRU (e.g., UE) does not receive / detect one or more LP-WUS, the WTRU (e.g., UE) can continue to monitor LP-WUS based on one or more LP-WUS monitoring configurations.

[0159] According to some embodiments, the WTRU (e.g., UE) may receive configurations of LP-WUS resources. LP-WUS resources may be a set of configurations for LP-WUS reception. For example, the configuration of LP-WUS resources may include information indicating any of the following: (1) signal structure; (2) waveform; (3) monitoring type; and / or (4) frequency resources.

[0160] According to some embodiments, the WTRU (e.g., UE) may receive a configuration of the signal structure. For example, the WTRU (e.g., UE) may receive one or more of the following: support for energy harvesting sequences, preamble, preamble length (if configured), etc.

[0161] According to some embodiments, the WTRU (e.g., UE) can receive waveform configurations. For example, the WTRU (e.g., UE) can receive one of OOK-1, OOK-4, OFDMA, etc., as the waveform for LP-WUS.

[0162] According to some embodiments, the WTRU (e.g., UE) can receive a monitoring type configuration. For example, the WTRU (e.g., UE) can receive either continuous monitoring or duty cycle monitoring.

[0163] According to some embodiments, the WTRU (e.g., UE) can receive a configuration of frequency resources. For example, the WTRU (e.g., UE) can receive a configuration based on one or more of RB, subband, BWP, etc., to indicate frequency resources for receiving LP-WUS.

[0164] According to some embodiments, the WTRU (e.g., a UE) can receive a configuration of time resources. For example, the WTRU (e.g., a UE) can receive a configuration based on one or more of periodicity, offset, etc. Instructions for the configuration can be based on OFDM symbols, us, time slots, etc.

[0165] Methods and apparatus are provided for determining LP-WUS back-off based on energy storage conditions.

[0166] WTRU (e.g., UE) can indicate the WTRU (e.g., UE) capability for operation of WTRU (e.g., UE) without energy harvesting for different energy levels.

[0167] For example, a WTRU (e.g., a UE) can indicate the potential operating durations X1 and X2 of energy storage status (e.g., 75% and 50%, respectively).

[0168] The WTRU (e.g., UE) can receive the configuration of LP-WUS, which includes the operating durations X1 and X2 for energy storage conditions (e.g., for 75% and 50% respectively), DL resources for each LP-WUS type (e.g., first type LP-WUS and second type LP-WUS), and UL resources.

[0169] The WTRU (e.g., UE) can receive LP-WUS activation messages from a network node (e.g., gNB).

[0170] WTRU (e.g., UE) can monitor LP-WUS and indicate its energy storage status in UL resources.

[0171] If the WTRU (e.g., UE) is a Type I WTRU (e.g., UE) (e.g., capable of energy storage and indicating energy storage status), then the WTRU (e.g., UE) can indicate the energy storage status to the network node (e.g., gNB) in UL resources (e.g., prior to LP-WUS activation).

[0172] If the indicated energy storage condition is greater than a first threshold (e.g., 75%), the WTRU (e.g., UE) can receive a first type of LP-WUS (e.g., LP-WUS without an energy harvesting sequence) during the X1 duration based on the LP-WUS configuration. After the X1 duration, the WTRU (e.g., UE) can receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence).

[0173] If the indicated energy storage condition is greater than a second threshold (e.g., 50%) (and less than a first threshold, for example), the WTRU (e.g., the UE) can receive a first type of LP-WUS (e.g., an LP-WUS without an energy harvesting sequence) during the X2 duration based on the LP-WUS configuration. After the X2 duration, the WTRU (e.g., the UE) can receive a second type of LP-WUS (e.g., an LP-WUS with an energy harvesting sequence).

[0174] If the indicated energy storage condition is less than (or equal to) a second threshold (e.g., 50%), the WTRU (e.g., UE) may receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence).

[0175] If the WTRU (e.g., UE) is a second type WTRU (e.g., UE) (e.g., unable to perform energy storage and indicate energy storage status), then the WTRU (e.g., UE) can receive a second type LP-WUS (e.g., LP-WUS with energy harvesting sequence).

[0176] WTRU (e.g., UE) can monitor LP-WUS based on the determined LP-WUS type.

[0177] When a WTRU (e.g., a UE) receives an LP-WUS in a defined LP-WUS resource, the WTRU (e.g., a UE) can monitor the PDCCH associated with the paging.

[0178] Subsequently, LP-WUS can be used interchangeably with UE, but still in accordance with this disclosure.

[0179] According to some embodiments, a WTRU (e.g., UE) may indicate the capability of a WTRU (e.g., UE) for determining one or more parameters. For example, a WTRU (e.g., UE) may indicate the capability of a WTRU (e.g., UE) for operation of a WTRU (e.g., UE) in the absence of energy harvesting for different energy levels. This indication may be based on one or more of the following: (1) an energy storage condition threshold; and / or (2) the duration of operation.

[0180] For example, the WTRU (e.g., UE) may indicate one or more energy storage condition thresholds (e.g., for determining LP-WUS sequence type and / or duration). This indication may be used for each LP-WUS parameter (e.g., LP-WUS sequence type). For example, the first LP-WUS sequence type may be LP-WUS without an energy harvesting sequence, and the second LP-WUS sequence type may be LP-WUS with an energy harvesting sequence.

[0181] For example, a WTRU (e.g., a UE) may indicate one or more operating durations. Each duration may be associated with each LP-WUS parameter (e.g., LP-WUS sequence type) and / or energy storage condition. For example, a WTRU (e.g., a UE) may indicate potential operating durations X1a and X2a for energy storage conditions (e.g., for 75% and 50%, respectively).

[0182] According to some embodiments, a WTRU (e.g., a UE) may receive a configuration for LP-WUS operation (e.g., having an energy harvesting sequence). This configuration may be based on the WTRU (e.g., UE) type. For example, a first-type WTRU (e.g., a UE) (e.g., capable of both energy harvesting and energy storage) may receive this configuration (e.g., including operation durations X1b and X2b for energy storage status (e.g., for 75% and 50% respectively), DL resources for each LP-WUS type (e.g., first-type LP-WUS and second-type LP-WUS), and UL resources). In another example, a second-type WTRU (e.g., a UE) (e.g., unable to perform energy harvesting or energy storage) may not receive this configuration. This configuration may be based on one or more of the following: (1) an energy storage status threshold; (2) an operation duration; and / or (3) an acknowledgment resource.

[0183] For example, a WTRU (e.g., a UE) may receive a configuration that includes one or more energy storage condition thresholds (e.g., for determining the LP-WUS sequence type and / or duration). This configuration may be used for each LP-WUS parameter (e.g., the LP-WUS sequence type). For example, a first LP-WUS sequence type may be an LP-WUS without an energy harvesting sequence, and a second LP-WUS sequence type may be an LP-WUS with an energy harvesting sequence.

[0184] In another example, the energy storage status thresholds can be predefined (e.g., predefined as 75% and 50%).

[0185] The threshold can be indicated as one or more of the following: energy storage percentage, watt-hour (Wh), milliampere-hour (mAh), etc.

[0186] For example, a WTRU (e.g., a UE) may receive configurations for one or more operating durations. Each duration may be associated with each LP-WUS parameter (e.g., LP-WUS sequence type) and / or energy storage status (e.g., 75% or 50%).

[0187] For example, a WTRU (e.g., a UE) may receive configurations for potential operating durations X1b and X2b for energy storage conditions (e.g., for 75% and 50%, respectively). The configured durations may be based on reported WTRU (e.g., UE) capabilities. For example, the configured durations X1b and X2b may be less than (or equal to) reported durations X1a and X2a, respectively. In another example, the configured durations X1b and X2b may be greater than (or equal to) reported durations X2a and X2a, respectively. Alternatively, based on capability reports, the configured durations X1b and X2b may be X1a and X2b, respectively.

[0188] If the configured durations X1b and / or X2b do not meet the requirements (e.g., X1b and / or X2b are greater than X1a and / or X2a, respectively), the WTRU (e.g., the UE) may consider a rollback configuration and / or operation. The rollback configuration and / or operation may be one or more of the following: (i) applying the values ​​reported by the WTRU (e.g., the UE); and / or (ii) applying a rollback operation.

[0189] For example, in cases where the rollback configuration and / or operation application reports values ​​from the WTRU (e.g., UE), if X1b and / or X2b are greater than X1a and / or X2a, the WTRU (e.g., UE) can use X1a and / or X2a as the configuration values ​​for X1b and / or X2b.

[0190] For example, in cases where a fallback configuration and / or operation applies a fallback operation, a WTRU (e.g., a UE) can monitor one or more LP-WUS resources based on a default type (or fallback type). For example, a WTRU (e.g., a UE) can monitor a second type of LP-WUS (e.g., an LP-WUS with an energy harvesting sequence) without considering duration and energy storage conditions.

[0191] For example, a WTRU (e.g., a UE) may receive a configuration that includes acknowledgment resources. For example, a WTRU (e.g., a UE) may receive one or more acknowledgment resources (e.g., from a gNB). These one or more resources may be one or more of the resources used for PDCCH, PDSCH, PRACH, DL RS, etc.

[0192] According to some embodiments, the WTRU (e.g., UE) can receive an LP-WUS activation message from a network node (e.g., gNB). The activation message can be based on one or more of RRC, MAC CE, and DCI. If DCI-based activation messages are supported, the DCI can be a WTRU (e.g., UE)-specific DCI (e.g., part of PDSCH scheduling and / or PUSCH scheduling). In another example, the DCI can be a group-specific DCI.

[0193] According to some embodiments, a WTRU (e.g., a UE) can determine activation / deactivation based on WTRU (e.g., UE) measurements and / or WTRU (e.g., UE) implementation methods. For example, a WTRU (e.g., a UE) can measure one or more RSs (e.g., LP-SS). Based on this measurement, the WTRU (e.g., the UE) can determine the quality (e.g., RSRP). Based on the determined quality, the WTRU (e.g., the UE) can determine activation / deactivation (e.g., the measured quality is greater than or less than a threshold). Instead of the measured quality, other metrics can be used (e.g., WTRU (e.g., UE) traffic, time since the most recent transmission / reception, etc.).

[0194] According to some embodiments, the WTRU (e.g., UE) can determine the energy storage status (e.g., by measuring the remaining energy in its battery) (e.g., expressed as energy storage %, watt-hours (Wh), milliampere-hours (mAh), etc.).

[0195] According to some embodiments, based on a received activation message and / or a determined activation (e.g., by the UE), the WTRU (e.g., the UE) can indicate its energy storage status. This indication can be based on one or more of the following: (1) reporting to the WTRU (e.g., the UE); (2) reporting resources; and / or (3) energy reporting.

[0196] According to some embodiments, the indication of the energy storage status of a WTRU (e.g., a UE) can be based on the WTRU (e.g., a UE) type. For example, if the WTRU (e.g., a UE) is a first-type WTRU (e.g., a UE) (e.g., capable of energy storage and indicating energy storage status), then the WTRU (e.g., a UE) can indicate the energy storage status to a network node (e.g., a gNB) in a UL resource (e.g., before LP-WUS activation). If the WTRU (e.g., a UE) is a second-type WTRU (e.g., a UE) (e.g., unable to perform energy storage and indicate energy storage status), then the WTRU (e.g., a UE) can monitor one or more LP-WUS resources (e.g., in the absence of an indication of energy storage status).

[0197] According to some embodiments, the indication of the energy storage status of a WTRU (e.g., a UE) can be based on a reporting resource. For example, the reporting can be done in a configured UL resource. For example, the reporting can be done in an indicated UL resource. For example, an activation message (e.g., a UL scheduling DCI) can indicate the UL resource used for WTRU (e.g., UE) reporting. For example, the report can be one or more of PRACH, PUCCH, PUSCH, UL RS, etc.

[0198] According to some embodiments, the indication of the energy storage status of a WTRU (e.g., a UE) can be based on energy reports. For example, the WTRU (e.g., a UE) can indicate energy (e.g., expressed as energy storage %, watt-hours (Wh), milliampere-hours (mAh), etc.). For example, the WTRU (e.g., a UE) can indicate one of the configured energy threshold values. The energy threshold value can be based on the reported WTRU (e.g., a UE) capacity and / or a configured energy threshold.

[0199] According to some embodiments, the WTRU (e.g., UE) can receive confirmation of the indicated energy storage status (e.g., via one or more configured confirmation resources). This confirmation can be one or more of PDCCH, PDSCH, MAC CE, DL RS, etc. Based on this confirmation, the WTRU (e.g., UE) can support one or more of the following operations.

[0200] If the WTRU (e.g., UE) receives this acknowledgment, the WTRU (e.g., UE) can determine and / or the network node (e.g., gNB) instructs to monitor one or more LP-WUS resources based on the WTRU (e.g., UE).

[0201] If the WTRU (e.g., UE) does not receive the acknowledgment, the WTRU (e.g., UE) may transmit another indication of its energy storage status. For example, the WTRU (e.g., UE) may indicate another WTRU (e.g., UE) energy storage status. For instance, a counter / timer associated with the WTRU (e.g., UE) energy storage status report may be reset by using the initial report and / or acknowledgment before it expires. If the WTRU (e.g., UE) does not receive acknowledgment for its report, the WTRU (e.g., UE) may increment the counter value by one. The reporting resource may be based on the latest configured UL resource or a resource with a defined time offset (e.g., through configuration and / or WTRU (e.g., UE) capabilities).

[0202] Based on this confirmation, the WTRU (e.g., UE) can support rollback operations. For example, the WTRU (e.g., UE) can monitor a second type of LP-WUS (e.g., an LP-WUS with an energy harvesting sequence) without prior monitoring of the second type of LP-WUS.

[0203] According to some embodiments, a WTRU (e.g., a UE) can monitor one or more LP-WUS resources (e.g., determined based on the WTRU (e.g., a UE) type and / or reported energy storage status).

[0204] According to some embodiments, (e.g., if the WTRU (e.g., UE) is a first-type WTRU (e.g., UE) (e.g., capable of energy storage and indicating energy storage status)), the WTRU (e.g., UE) can determine the type of LP-WUS monitoring based on the indicated energy storage status (e.g., to the gNB) (e.g., before LP-WUS activation). One or more of the following can be applied to monitor one or more LP-WUS resources.

[0205] For example, if the indicated energy storage condition is greater than a first threshold (e.g., 75%), the WTRU (e.g., the UE) may monitor and receive a first type of LP-WUS (e.g., LP-WUS without an energy harvesting sequence) during the X1b duration (e.g., based on the LP-WUS configuration and / or the reported WTRU (e.g., the UE) capability). After the X1b duration, the WTRU (e.g., the UE) may monitor and receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence).

[0206] For example, if the indicated energy storage condition is greater than a second threshold (e.g., 50%) (and, for example, less than a first threshold), the WTRU (e.g., the UE) may monitor and receive a first type of LP-WUS (e.g., LP-WUS without an energy harvesting sequence) during the X2b duration (e.g., based on the LP-WUS configuration and / or the reported WTRU (e.g., the UE) capability). After the X2b duration, the WTRU (e.g., the UE) may monitor and receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence).

[0207] For example, if the indicated energy storage status is less than (or equal to) a second threshold (e.g., 50%), the WTRU (e.g., UE) can monitor and receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence) (e.g., from the start of activation).

[0208] According to some embodiments, (e.g., if the WTRU (e.g., UE) is a second type WTRU (e.g., UE) (e.g., unable to perform energy storage and indicate energy storage status)), the WTRU (e.g., UE) can monitor and / or can receive a second type LP-WUS (e.g., LP-WUS with energy harvesting sequence) (e.g., without considering the indicated energy storage status).

[0209] According to some embodiments, the WTRU (e.g., UE) may receive indications of LP-WUS monitoring type and / or corresponding resources. For example, the WTRU (e.g., UE) may receive indications of one or more LP-WUS resource set IDs (e.g., having an energy harvesting sequence type and a corresponding duration). For example, the indicated set may include a configuration X1b duration or X2b duration for applying a first type of LP-WUS. According to some embodiments, the WTRU (e.g., UE) may receive indications of the duration of a first type of LP-WUS monitoring. For example, the WTRU (e.g., UE) may receive indications of either an X1b duration or an X2b duration. The WTRU (e.g., UE) may apply this duration to the first type of LP-WUS monitoring duration. After this duration, the WTRU (e.g., UE) may apply a second type of LP-WUS monitoring.

[0210] According to some embodiments, based on determined LP-WUS resources and cells, a WTRU (e.g., a UE) can monitor LP-WUS in determined LP-WUS resources of determined cells. If the WTRU (e.g., the UE) receives LP-WUS in the determined LP-WUS resources, the WTRU (e.g., the UE) can support corresponding operations based on the received LP-WUS information. For example, when the WTRU (e.g., the UE) receives LP-WUS in the determined LP-WUS resources, the WTRU (e.g., the UE) can monitor the PDCCH associated with paging. Additionally, the WTRU (e.g., the UE) can monitor system information and / or paging-related information indicated by the LP-WUS application.

[0211] Methods and apparatus are provided for determining the LP-WUS sequence type and duration based on WTRU (e.g., UE) type and energy storage status.

[0212] The WTRU (e.g., UE) can receive the LP-WUS configuration from the network node (e.g., gNB). The LP-WUS configuration includes time (e.g., periodicity and offset) and frequency resources, as well as UL resources, for each LP-WUS type (e.g., first type LP-WUS and second type LP-WUS).

[0213] The WTRU (e.g., UE) can receive an LP-WUS activation message from a network node (e.g., gNB). For example, the network node (e.g., gNB) can indicate the LP-WUS type. For example, the WTRU (e.g., UE) can activate LP-WUS with a default type.

[0214] WTRU (e.g., UE) can monitor LP-WUS in time and frequency resources and can indicate energy storage status to network nodes (e.g., gNB) in UL resources.

[0215] If the indicated energy storage condition is greater than a first threshold (e.g., 75%), the WTRU (e.g., UE) may monitor the first type of LP-WUS (e.g., LP-WUS without an energy harvesting sequence) until the next energy storage condition indication.

[0216] If the indicated energy storage condition is greater than a second threshold (e.g., 50%) (and less than a first threshold), the WTRU (e.g., UE) may receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence) until the next energy storage condition indication.

[0217] If the indicated energy storage status is less than (or equal to) a second threshold (e.g., 50%), then the WTRU (e.g., UE) activates MR.

[0218] WTRU (e.g., UE) can monitor LP-WUS based on the determined LP-WUS type.

[0219] When a WTRU (e.g., a UE) receives an LP-WUS or activates an MR based on an indicated energy storage condition, the WTRU (e.g., a UE) can monitor the PDCCH associated with the paging.

[0220] When LP-WUS supports energy harvesting, selecting an LP-WUS type that supports energy condition awareness can increase the number of WTRUs (e.g., UEs) that network nodes (e.g., gNBs) can support for energy harvesting. Furthermore, this can increase the efficiency of utilizing available resources (e.g., time-frequency resources, transmitted energy). For this purpose, LP-WUS monitoring of UEs can use one or a combination of the following solutions.

[0221] The WTRU (e.g., UE) may receive one or a combination of the following indications / configurations: (1) multiple LP-WUS types; (2) UL resources; and / or (3) one or more thresholds regarding energy storage status (e.g., a first threshold, a second threshold, etc.).

[0222] A WTRU (e.g., a UE) can receive configurations for multiple LP-WUS types (e.g., Type 1 LP-WUS, Type 2 LP-WUS). Each LP-WUS type can be associated with different configurations for time (e.g., periodicity and offset), duration, and frequency resources (e.g., FR, bandwidth), etc.

[0223] The WTRU (e.g., UE) can receive configuration of UL resources from a network node (e.g., gNB) to indicate the selected LP-WUS type and / or the status of energy storage, etc. UL resources may include resources and authorizations for PUCCH / PUSCH transmissions, preamble resources (e.g., each preamble resource is associated with one or more LP-WUS types), etc.

[0224] According to some embodiments, the WTRU (e.g., UE) can receive an activation message for LP-WUS monitoring from a network node (e.g., gNB) (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI update). Upon receiving the activation message, the WTRU (e.g., UE) can activate itself by following one or a combination of the following procedures to perform LP-WUS monitoring using the selected type(s) of LP-WUS.

[0225] According to some embodiments, a WTRU (e.g., a UE) may receive an indication of one or more LP-WUS types or be configured with one or more LP-WUS types. A WTRU (e.g., a UE) may begin monitoring LP-WUS by using the indicated LP-WUS type.

[0226] According to some embodiments, the WTRU (e.g., UE) can receive an indication / configuration from a network node (e.g., gNB) to activate the surveillance LP-WUS. The WTRU (e.g., UE) can activate an LP-WUS with a default LP-WUS type (e.g., using a pre-configured default LP-WUS type (via RRC signaling, MAC-CE indication, DCI indication, or SI configuration)).

[0227] A WTRU (e.g., a UE) can determine its energy storage status and indicate the determined energy storage status to a network node (e.g., a gNB) via configured UL resources. For example, a WTRU (e.g., a UE) can transmit a two-bit indication via PUCCH / PUSCH, where a two-bit value of 10 indicates an energy storage status above a first threshold, a two-bit value of 01 indicates an energy storage status above a second threshold, and a two-bit value of 00 indicates an energy storage status below the second threshold. In another example, a WTRU (e.g., a UE) can transmit a pre-configured preamble resource, where each preamble corresponds to an energy storage status. In response to the energy storage indication, the WTRU (e.g., a UE) can receive confirmation of successful reception of the energy storage indication from the network node (e.g., a gNB) (e.g., via a 1-bit indication in the DCI on a pre-configured PDCCH resource). Subsequently, the WTRU (e.g., a UE) can follow one or a combination of the following procedures to determine the type(s) of the LP-WUS(s) to be received and / or determine the configuration associated with the LP-WUS(s) to be received.

[0228] If the indicated energy condition is greater than a first threshold (e.g., 75%), the WTRU (e.g., UE) may receive a first type of LP-WUS (e.g., LP-WUS without an energy harvesting sequence). The WTRU (e.g., UE) may receive the first type of LP-WUS until the next energy condition indication. Alternatively, the WTRU (e.g., UE) may receive the first type of LP-WUS for a configured duration (e.g., pre-configured via RRC signaling, MAC-CE indication, or DCI indication). After the pre-configured duration and until the next energy condition indication, the WTRU (e.g., UE) may receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence). Activation or deactivation of receiving the second type of LP-WUS after the pre-configured duration may depend on the periodicity of the energy condition indication or the duration until the next UL resource updates the energy condition. For example, if the periodicity of the energy condition indication > a pre-configured threshold for the periodicity of the energy condition indication, the WTRU (e.g., UE) may activate receiving the second type of LP-WUS after the pre-configured duration. Otherwise, the WTRU (e.g., the UE) can continue to receive Type 1 LP-WUS until the next energy storage indication.

[0229] If the indicated energy condition is greater than a second threshold (e.g., 50%) and less than a first threshold, the WTRU (e.g., UE) may receive a second type of LP-WUS (e.g., LP-WUS with an energy harvesting sequence). The WTRU (e.g., UE) may receive the second type of LP-WUS until the next energy condition indication. Alternatively, the WTRU (e.g., UE) may receive the second type of LP-WUS until a pre-configured duration (e.g., pre-configured via RRC signaling, MAC-CE indication, or DCI indication). After the pre-configured duration and until the next energy condition indication, the WTRU (e.g., UE) may receive a first type of LP-WUS (e.g., LP-WUS without an energy harvesting sequence). Activation or deactivation of receiving the first type of LP-WUS after the pre-configured duration may depend on the periodicity of the energy condition indication or the duration until the next UL resource updates the energy condition indication. For example, if the periodicity of the energy condition indication is less than a pre-configured threshold for the periodicity of the energy condition indication, the WTRU (e.g., UE) may activate receiving the first type of LP-WUS after the pre-configured duration. Otherwise, the WTRU (e.g., the UE) can continue to receive Type II LP-WUS until the next energy storage indication.

[0230] If the indicated energy storage condition is less than (or equal to) a second threshold (e.g., 50%), the WTRU (e.g., UE) may activate the MR. After activating the MR / after indicating the energy storage condition, the WTRU (e.g., UE) may receive an NR paging signal / channel (e.g., the WTRU (e.g., UE) monitors for paging PDCCH and / or early paging indications) and / or transmit a PRACH for initial access.

[0231] A WTRU (e.g., a UE) that has indicated the selected LP-WUS type to a network node (e.g., a gNB) can monitor LP-WUS based on the determined LP-WUS type. For this purpose, the WTRU (e.g., the UE) can determine the resources and configurations for receiving LP-WUS based on the selected LP-WUS type (e.g., time-frequency resources, bandwidth, duration, etc.).

[0232] If LP-WUS instructs the WTRU (e.g., UE) to activate MR (e.g., by presence indication of LP-WUS determined via energy detection, or content indication via LP-WUS payload), the WTRU (e.g., UE) may receive NR paging signals / channels (e.g., the WTRU (e.g., UE) monitors for paging PDCCH and / or paging early indications), and / or transmit PRACH for initial access. If LP-WUS instructs the WTRU (e.g., UE) not to activate MR, the WTRU (e.g., UE) may continue to monitor LP-WUS using the selected LP-WUS type(s).

[0233] If the WTRU (e.g., UE) activates MR during the LP-WUS type selection procedure (e.g., the WTRU (e.g., UE) determines and indicates that the energy storage condition is less than a second threshold), the WTRU (e.g., UE) may receive NR paging signals / channels (e.g., the WTRU (e.g., UE) monitors for paging PDCCH and / or paging early indications), and / or transmit PRACH for initial access.

[0234] A method and apparatus are provided for confirming LP-WUS activation based on energy storage status.

[0235] The WTRU (e.g., UE) can receive the configuration of LP-WUS, which includes DL resources and UL resources for LP-WUS monitoring.

[0236] The WTRU (e.g., UE) can receive LP-WUS activation messages from a network node (e.g., gNB).

[0237] WTRU (e.g., UE) can determine the energy storage status and indicate whether it is ready based on the energy storage status in UL resources.

[0238] If the determined energy storage status is greater than a threshold (e.g., 50%), the WTRU (e.g., UE) can indicate readiness and can monitor LP-WUS in the configured DL resources.

[0239] If the determined energy storage status is less than (or equal to) a threshold (e.g., 50%), the WTRU (e.g., UE) can indicate that it is not ready and the time offset for the next indication (e.g., another ACK / NACK) from the WTRU (e.g., UE).

[0240] A WTRU (e.g., a UE) can indicate another WTRU (e.g., a UE) based on an updated energy storage status.

[0241] WTRU (e.g., UE) can monitor LP-WUS after indicating that it is ready.

[0242] When a WTRU (e.g., a UE) receives LP-WUS in LP-WUS resources, the WTRU (e.g., a UE) can monitor the PDCCH associated with paging.

[0243] According to some embodiments, the WTRU (e.g., UE) may receive configuration information indicating one or more of the following: (1) one or more LP-WUS; (2) one or more DL resources for LP-WUS; (3) one or more preferred LP-WUS resources; (4) one or more thresholds (e.g., threshold 1 and threshold 2); and / or one or more UL resources.

[0244] According to some embodiments, the WTRU (e.g., UE) may receive an indication of the type of LP-WUS waveform (e.g., OOK, OOK-2, CP-OFDM, FSK-1, FSK-2) based on the UE’s capabilities (e.g., based on the UE’s indication of the supported LP-WUS waveform types as part of its capability report).

[0245] According to some embodiments, the WTRU (e.g., UE) may receive an indication of the length of the LP-WUS sequence (e.g., the number of bits, such as the number of QAM symbols).

[0246] According to some embodiments, the WTRU (e.g., UE) may receive configuration of DL resources associated with one or more of the LP-WUS (waveform) types (e.g., via RRC / MAC-CE / DCI).

[0247] According to some embodiments, the WTRU (e.g., UE) may receive an indication of a DL resource associated with a preferred LP-WUS waveform.

[0248] According to some embodiments, the WTRU (e.g., UE) may receive indications for one or more UL resources associated with one or more LP-WUS types.

[0249] A WTRU (e.g., a UE) can determine its energy storage status (e.g., based on the UE's implementation). A WTRU (e.g., a UE) can send indications of its LP-WUS monitorability and / or energy storage status in one or more of the following ways: According to some embodiments, a WTRU (e.g., a UE) may send an indication of the LP-WUS monitorability status (e.g., ready or not ready) associated with one or more LP-WUS resources (e.g., one or more LP-WUS types) via a configured UL resource (e.g., PUSCH / PUCCH) based on its energy storage status.

[0250] According to some embodiments, if the energy storage status of the WTRU (e.g., UE) is greater than a threshold 1, the WTRU (e.g., UE) may send an indication that it is ready for the first LP-WUS resource (e.g., OOK) (e.g., represented by 1 in a 1-bit indication); otherwise, it may send an indication that it is not ready (e.g., represented by 0 in a 1-bit indication).

[0251] According to some embodiments, if the energy storage status of the WTRU (e.g., UE) is greater than a threshold 2, the WTRU (e.g., UE) may send an indication that it is ready for the second LP-WUS resource (e.g., OOK-2) (e.g., represented by 1 in a 1-bit indication); otherwise, it may send an indication that it is not ready (e.g., represented by 0 in a 1-bit indication).

[0252] According to some embodiments, based on the UE's LP-WUS monitorability status (e.g., not ready), the WTRU (e.g., the UE) can indicate a time offset between the current indication and the next UE indication for the monitorability status. For example, the WTRU (e.g., the UE) can indicate a uniform time offset. For example, if the WTRU (e.g., the UE)'s current energy storage status is > a threshold (e.g., 40%), then the WTRU (e.g., the UE) can indicate a time offset of N slots / frames / milliseconds; otherwise, the WTRU (e.g., the UE) can indicate a time offset of N–M, where M > 0 and N > M.

[0253] According to some embodiments, the WTRU (e.g., UE) may determine the time-until-ready (e.g., the amount of time required for the WTRU (e.g., UE) to become ready for LP-WUS watchability based on the received LP-WUS configuration (e.g., number of bits, e.g., waveform type), the watchability status determined by the WTRU (e.g., UE) (e.g., not ready), and / or the energy storage / charging / generating rate (e.g., based on the WTRU (e.g., UE) implementation). According to some embodiments, the WTRU (e.g., UE) may send an additional indication of the time-until-ready based on the UE's watchability status (e.g., not ready).

[0254] According to some embodiments, the WTRU (e.g., UE) may send an indication of the time prior to readiness in a UL resource associated with the indicated preferred LP-WUS type.

[0255] According to some embodiments, the WTRU (e.g., UE) may send an indication of the time prior to readiness in a UL resource associated with a first LP-WUS type (e.g., an LP-WUS associated with a minimum energy storage threshold).

[0256] According to some embodiments, the WTRU (e.g., UE) may send an indication of the time prior to readiness in a UL resource associated with a second LP-WUS type (e.g., an LP-WUS associated with a maximum energy storage threshold).

[0257] According to some embodiments, the WTRU (e.g., UE) can send an indication of the time prior to readiness in all UL resources associated with a configured LP-WUS type having an unready monitorability condition.

[0258] According to some embodiments, the WTRU (e.g., UE) may send an indication of a new / updated LP-WUS monitorability condition based on an indicated time offset and / or a time prior to readiness.

[0259] According to some embodiments, the WTRU (e.g., UE) may send an indication of a new / updated LP-WUS monitorability status (i.e., ready / not ready) at a time offset after a previous WTRU (e.g., UE) indication of the monitorability status (e.g., not ready).

[0260] According to some embodiments, the WTRU (e.g., UE) may send an indication of the time before a new / updated LP-WUS monitorability condition (i.e., ready / not ready) is ready, following a previous WTRU (e.g., UE) indication of the monitorability condition (e.g., not ready).

[0261] According to some embodiments, the WTRU (e.g., UE) may send an indication of a new / updated LP-WUS monitorability status (i.e., ready / not ready) maximum value (time before ready, time offset) after a previous WTRU (e.g., UE) indication of the monitorability status (e.g., not ready).

[0262] According to some embodiments, the WTRU (e.g., UE) may send an indication of a new / updated LP-WUS monitorability condition (i.e., ready / not ready) minimum (time before ready, time offset) after a previous WTRU (e.g., UE) indication of the monitorability condition (e.g., not ready).

[0263] According to some embodiments, the WTRU (e.g., UE) may initiate monitoring of the LP-WUS after sending an indication that it is ready.

[0264] According to some embodiments, the WTRU (e.g., UE) may begin monitoring of a first LP-WUS (e.g., associated with the preferred LP-WUS resource) after indicating readiness for one or more LP-WUS resources (e.g., including a preferred LP-WUS resource).

[0265] According to some embodiments, the WTRU (e.g., UE) may switch monitoring from the first LP-WUS (e.g., not associated with the preferred LP-WUS resource) to the second LP-WUS (e.g., associated with the preferred LP-WUS resource) after it is ready for the second LP-WUS indication.

[0266] According to some embodiments, the WTRU (e.g., UE) can monitor the PDCCH associated with paging based on the received and / or decoded LP-WUS sequence.

[0267] Methods and apparatus for receiving and transmitting energy harvesting sequences are provided.

[0268] According to some embodiments, the WTRU (e.g., UE) can (e.g., from one or more UEs) receive a WTRU-specific energy harvesting sequence.

[0269] According to some embodiments, the WTRU (e.g., UE) may receive one or more sets of configurations for receiving energy harvesting sequences. Each set of configurations may include information indicating any of the following: (1) one or more time and frequency resources; (2) one or more sequences; (3) one or more request resources; (4) one or more acknowledgment resources; and / or (5) one or more energy thresholds.

[0270] According to some embodiments, the WTRU (e.g., UE) may receive configuration information indicating one or more time and frequency resources, including information indicating one or more of the following: (i) periodicity; (ii) offset; (iii) RB; (iv) subband; and / or (v) BWP.

[0271] According to some embodiments, the WTRU (e.g., UE) may receive configuration information indicating one or more sequences, including information indicating one or more of the following: (i) sequence type; (ii) sequence length; and / or (iii) sequence ID.

[0272] According to some embodiments, the WTRU (e.g., a UE) may receive configuration information indicating one or more requested resources (e.g., for requesting an energy harvesting sequence). For example, the one or more requested resources may be one or more uplink resources and / or sidelink resources.

[0273] According to some embodiments, the WTRU (e.g., a UE) may receive configuration information indicating one or more acknowledgment resources (e.g., for receiving acknowledgment of a request). For example, the one or more acknowledgment resources may be one or more uplink resources and / or sidelink resources. For example, each acknowledgment resource may be associated with each set of configurations for receiving an energy harvesting sequence. For example, each acknowledgment resource may be associated with each request resource for receiving an energy harvesting sequence.

[0274] According to some embodiments, the WTRU (e.g., a UE) may receive configuration information indicating one or more energy thresholds. For example, one or more energy thresholds may be configured to trigger an energy harvesting procedure. For example, each energy threshold may be associated with a set of configurations for receiving an energy harvesting sequence.

[0275] According to some embodiments, a WTRU (e.g., a UE) can indicate a request for the transmission of transmit energy. This indication can be based on one or more configured energy thresholds. For example, if the energy stored in the WTRU (e.g., the UE) is less than an energy threshold, the WTRU (e.g., the UE) can indicate the request in one or more configured request resources. This request can be based on one or more of PUCCH, PUSCH, PRACH, UL RS, PSCCH, PSSCH, SL RS, etc.

[0276] According to some embodiments, a WTRU (e.g., a UE) may receive one or more acknowledgments (e.g., in an associated acknowledgment resource) requested by a WTRU (e.g., a UE). The acknowledgment may be based on one or more of PUCCH, PUSCH, PRACH, UL RS, PSCCH, PSSCH, SL RS, etc.

[0277] Based on a WTRU (e.g., UE) request and / or confirmation, the WTRU (e.g., UE) may receive an energy harvesting sequence (e.g., in the associated time and frequency resources).

[0278] According to some embodiments, the WTRU (e.g., the UE) may indicate the termination of the energy harvesting procedure. This indication may be transmitted in one or more request resources. In another example, the indication may be transmitted in a separately configured termination request resource (e.g., it may be associated with a request resource and / or acknowledgment resource for receiving an energy harvesting sequence).

[0279] According to some embodiments, the WTRU (e.g., UE) can transmit a WTRU-specific energy harvesting sequence (e.g., to one or more UEs).

[0280] According to some embodiments, the WTRU (e.g., UE) may receive one or more sets of configurations for transmitting energy harvesting sequences. Each set of configurations may include information indicating any of the following: (1) one or more time and frequency resources; (2) one or more sequences; (3) one or more request resources; (4) one or more acknowledgment resources; and / or (5) one or more energy thresholds.

[0281] According to some embodiments, the WTRU (e.g., UE) may receive configuration information indicating one or more time and frequency resources, including information indicating one or more of the following: (i) periodicity; (ii) offset; (iii) RB; (iv) subband; and / or (v) BWP.

[0282] According to some embodiments, the WTRU (e.g., UE) may receive configuration information indicating one or more sequences, including information indicating one or more of the following: (i) sequence type; (ii) sequence length; and / or (iii) sequence ID.

[0283] According to some embodiments, the WTRU (e.g., a UE) may receive configuration information indicating one or more requested resources (e.g., for requesting an energy harvesting sequence). For example, the one or more requested resources may be one or more uplink resources and / or sidelink resources.

[0284] According to some embodiments, the WTRU (e.g., a UE) may receive configuration information indicating one or more acknowledgment resources (e.g., for receiving acknowledgment of a request). For example, the one or more acknowledgment resources may be one or more uplink resources and / or sidelink resources. For example, each acknowledgment resource may be associated with each set of configurations for receiving an energy harvesting sequence. For example, each acknowledgment resource may be associated with each request resource for receiving an energy harvesting sequence.

[0285] According to some embodiments, the WTRU (e.g., a UE) may receive configuration information indicating one or more energy thresholds. For example, one or more energy thresholds may be configured to trigger an energy harvesting procedure. For example, each energy threshold may be associated with a set of configurations for receiving an energy harvesting sequence.

[0286] According to some embodiments, the WTRU (e.g., UE) can monitor and receive requests for energy harvesting transmissions. These requests can be based on one or more of PUCCH, PUSCH, PRACH, UL RS, PSCCH, PSSCH, SL RS, etc.

[0287] According to some embodiments, a WTRU (e.g., a UE) may transmit one or more acknowledgments (e.g., in an associated acknowledgment resource) in response to a received WTRU (e.g., a UE) request. The acknowledgment may be based on one or more of PUCCH, PUSCH, PRACH, UL RS, PSCCH, PSSCH, SL RS, etc.

[0288] Based on a WTRU (e.g., UE) request and / or confirmation, the WTRU (e.g., UE) may transmit energy harvesting sequences (e.g., in associated time and frequency resources).

[0289] According to some embodiments, the WTRU (e.g., the UE) can monitor and receive termination of an energy harvesting procedure. This indication can be transmitted in one or more request resources. In another example, the indication can be transmitted in a separately configured termination request resource (e.g., it can be associated with a request resource and / or acknowledgment resource for receiving an energy harvesting sequence).

[0290] Figure 7 This is a flowchart illustrating a representative method 700 implemented using WTRU 102. (Reference) Figure 7 Representative method 700 may include receiving configuration information indicating low-power wake-up signal (LP-WUS) operation at block 710, wherein the configuration may include time and frequency resources for at least one LP-WUS type. At block 720, representative method 700 may include determining LP-WUS activation. At block 730, representative method 700 may include determining the type of LP-WUS to be monitored, for example, based on the energy storage status of the WTRU. At block 740, representative method 700 may include monitoring LP-WUS in associated time and frequency resources, for example, based on the determined type of LP-WUS.

[0291] According to some embodiments, when WTRU 102 receives LP-WUS in the determined LP-WUS time and frequency resources, WTRU 102 can monitor the physical downlink control channel associated with paging.

[0292] According to certain embodiments, WTRU 102 may send information indicating WTRU capability for operation of WTRU in the absence of energy harvesting for different energy levels, and wherein WTRU capability may be based on either: (1) an energy storage condition threshold and (2) an operation duration.

[0293] According to some embodiments, the configuration may be based on any of the following: (1) an energy storage status threshold, (2) an operation duration, and (3) a confirmed resource.

[0294] According to some embodiments, determining LP-WUS activation may include receiving an LP-WUS activation message from a network node via a WTRU.

[0295] According to some embodiments, determining the activation of LP-WUS can be based on WTRU measurements and / or WTRU implementation methods.

[0296] Figure 8 This is a flowchart illustrating a representative method 800 implemented via WTRU 102.

[0297] refer to Figure 8 Representative method 800 may include obtaining first information in block 810 indicating a configuration associated with at least one LP-WUS type, wherein the configuration includes at least one reception duration and at least one energy storage threshold.

[0298] Representative method 800 may include determining the activation of LP-WUS monitoring in box 820.

[0299] Representative method 800 may include, in block 830, determining the type of LP-WUS to be monitored based on a comparison of the energy storage status of the WTRU with at least one energy storage threshold; and Representative method 800 may include receiving at least one LP-WUS from a network node during at least one reception duration based on the determined type of LP-WUS and based on first information in block 840.

[0300] According to some embodiments, the at least one energy storage threshold may include a first energy storage threshold.

[0301] According to some embodiments, the at least one reception duration may include a first reception duration associated with a first energy storage threshold.

[0302] According to some embodiments, the energy storage condition based on the WTRU is better than (or otherwise satisfies) a first energy storage threshold. A representative method 800 may include receiving a first LP-WUS associated with a first type during a first reception duration, and / or receiving a second LP-WUS associated with a second type after the first reception duration.

[0303] According to some embodiments, the at least one energy storage threshold may include a second energy storage threshold, wherein the second energy storage threshold is less than the energy storage threshold.

[0304] According to some embodiments, the at least one reception duration may include a second reception duration associated with a second energy storage threshold.

[0305] According to certain embodiments, the energy storage condition based on the WTRU is lower than (or otherwise satisfies) a first energy storage threshold, and / or the energy storage condition based on the WTRU is better than (or otherwise satisfies) a second energy storage threshold. A representative method 800 may include receiving a first LP-WUS during a second reception duration, and / or receiving a second LP-WUS after the second reception duration.

[0306] According to some embodiments, the energy storage status based on the WTRU is lower than (or otherwise satisfies) a second energy storage threshold, and a representative method 800 may include receiving a second LP-WUS.

[0307] According to some embodiments, the first type may be an LP-WUS without an energy harvesting sequence, and / or the second type may be an LP-WUS with an energy harvesting sequence.

[0308] According to some embodiments, representative method 800 may include sending second information to a network node indicating the determined type of LP-WUS.

[0309] According to some embodiments, determining the activation of LP-WUS monitoring may include receiving third information from a network node indicating the activation of LP-WUS monitoring.

[0310] According to some embodiments, determining the activation of LP-WUS monitoring can be based on one or more WTRU measurements.

[0311] According to some embodiments, representative method 800 may include monitoring the physical downlink control channel associated with paging upon receiving the at least one LP-WUS.

[0312] According to some embodiments, representative method 800 may include sending the energy storage status of the WTRU to the network node when LP-WUS monitoring is determined to be active.

[0313] While features and elements have been provided above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. This disclosure is not limited to the specific embodiments described herein, which are intended as illustrative of various aspects. Many modifications and variations can be made without departing from its spirit and scope, as will be apparent to those skilled in the art. Unless expressly provided so, no element, action, or instruction used in the description of this application should be construed as essential or indispensable to the invention. Based on the foregoing description, functionally equivalent methods and apparatuses within the scope of this disclosure, other than those listed herein, will be apparent to those skilled in the art. These modifications and variations are intended to fall within the scope of the appended claims. This disclosure is limited only by the terminology of the appended claims and the full scope of their equivalents. It should be understood that this disclosure is not limited to any particular method or system.

[0314] For simplicity, the foregoing embodiments have been discussed in terms of terminology and structure relating to devices with infrared functionality (i.e., infrared transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0315] It should also be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the term "video" or the term "image" may mean any of a snapshot, a single image, and / or multiple images displayed on a time basis. As another example, when referred to herein, the term "user equipment" and its abbreviation "UE," the term "remote," and / or the term "head-mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmitting and / or receiving unit (WTRU); (ii) any of several embodiments of a WTRU; (iii) a device having wireless and / or wired (e.g., tetherable) capabilities configured with some or all of the structure and functions of a WTRU; (iii) a device having wireless and / or wired capabilities configured with fewer than all the structure and functions of a WTRU; or (iv) the like. Figure 1A-1D Details of an example WTRU that may represent any WTRU described herein are provided. As another example, the various disclosed embodiments herein are described above and below as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than head-mounted displays can be utilized, and some or all of this disclosure and the various disclosed embodiments can be modified accordingly without excessive experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adaptive, realistic experience.

[0316] Furthermore, the methods described herein can be implemented in computer programs, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) 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 optical discs (DVDs)). The processor associated with the software can be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

[0317] Variations of the methods, apparatus, and systems provided above are possible without departing from the scope of the invention. Given the various embodiments that can 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, embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery) that provides any suitable voltage.

[0318] Furthermore, in the embodiments provided above, references to processing platforms, computing systems, controllers, and other devices including processors are mentioned. These devices may include at least one central processing unit (“CPU”) and memory. In accordance with the practice of those skilled in the art of computer programming, references to symbolic representations of actions and operations or instructions can be executed by various CPUs and memories. Such actions and operations or instructions may be referred to as “executed,” “computer-executed,” or “CPU-executed.”

[0319] Those skilled in the art will understand that the actions and symbols representing operations or instructions include the CPU's manipulation of electrical signals. The electrical system represents data bits, which can lead to the final transformation or reduction of electrical signals and the retention of data bits at memory locations in the memory system, thereby reconfiguring or otherwise altering the CPU's operation and performing other signal processing. The memory location holding the data bits is a physical location having specific electrical, magnetic, optical, or organic properties corresponding to or representing the data bits. It should be understood that the embodiments are not limited to the platforms or CPUs described above, and other platforms and CPUs may support the provided methods.

[0320] Data bits can also be stored on a computer-readable medium, including disks, optical disks, and any other CPU-readable volatile (e.g., random access memory (“RAM”) or non-volatile (e.g., read-only memory (“ROM”) mass storage system. The computer-readable medium can include cooperative or interconnected computer-readable media that are uniquely present on the processing system or distributed across multiple interconnected processing systems, which can be local or remote relative to the processing system. It should be understood that the embodiments are not limited to the memory described above, and other platforms and memories can support the provided methods.

[0321] In illustrative embodiments, any of the operations, processes, etc., described herein can be implemented as computer-readable instructions stored on a computer-readable medium. These computer-readable instructions can be executed by a processor of a mobile unit, network element, and / or any other computing device.

[0322] There is little difference between hardware and software implementations of various aspects of the system. The use of hardware or software typically (but not always, as the choice between hardware and software can become important in certain contexts) represents a design choice that weighs cost against efficiency. Various media (e.g., hardware, software, and / or firmware) may exist to implement the processes and / or systems and / or other technologies described herein, and the preferred media can vary depending on the context in which the processes and / or systems and / or other technologies are deployed. For example, if the implementer determines that speed and accuracy are most important, the implementer may choose a media that is primarily hardware and / or firmware. If flexibility is most important, the implementer may choose a primarily software implementation. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0323] The foregoing detailed description has illustrated various embodiments of the device and / or process using block diagrams, flowcharts, and / or examples. Where such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, those skilled in the art will understand that each function and / or operation within such block diagrams, flowcharts, or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware, or virtually any combination thereof. In embodiments, several portions of the subject matter described herein can be implemented via application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integration formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be equivalently implemented in an integrated circuit, in whole or in part, as one or more computer programs (e.g., one or more programs running on one or more computer systems), one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware, or virtually any combination thereof, and that designing circuits and / or writing code for software and / or firmware according to this disclosure will be entirely within the technical scope of those skilled in the art. Furthermore, those skilled in the art will understand that the mechanisms of the subject matter described herein can be distributed as a program product in various forms, and that the illustrative embodiments of the subject matter described herein are applicable regardless of the specific type of signal-bearing medium used to actually perform such distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable media (such as floppy disks, hard disks, CDs, DVDs, digital magnetic tapes, computer memory, etc.); and transmission media (such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.)).

[0324] Those skilled in the art will recognize that it is common practice in the art to describe devices and / or processes in the manner set forth herein, and subsequently to use engineering practice to integrate such described devices and / or processes into data processing systems. That is, at least a portion of the devices and / or processes described herein can be integrated into a data processing system through a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system generally includes one or more of the following: a system unit enclosure; 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, a graphical user interface, and applications; 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 for sensing position and / or speed, control motors for moving and / or adjusting components and / or quantities). A typical data processing system can be implemented using any suitable commercially available components, such as those commonly found in data computing / communication and / or network computing / communication systems.

[0325] The subjects described herein are sometimes illustrated with different components included within or connected to different other components. It should be understood that such depicted architectures are merely examples, and many other architectures can in fact achieve the same functionality. Conceptually, any arrangement of components achieving the same function is effectively “associated” so that the desired function can be achieved. Therefore, any two components combined herein to achieve a particular function can be considered “associated” with each other so that the desired function can be achieved, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” to each other to achieve the desired function, and any two components that can be suchly associated can also be considered “operably coupled” to each other to achieve the desired function. Specific examples of operably coupled components include, but are not limited to, components that can physically cooperate and / or physically interact and / or components that can wirelessly interact and / or logically interact and / or logically interact.

[0326] Regarding virtually any plural and / or singular terms used herein, those skilled in the art can appropriately convert them from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly listed herein.

[0327] Those skilled in the art will understand that, in general, the terminology used herein, and especially in the appended claims (e.g., the body of the appended claims), is intended to be “open-ended” (e.g., the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “including” should be interpreted as “including but not limited to,” etc.). Those skilled in the art will further understand that if it is intended to specify a particular number of introduced claim subjects, such intention will be explicitly stated in the claims, and if no such subject is present, such intention will not exist. For example, the term “single” or similar language may be used where only one item is anticipated. To aid understanding, the appended claims and / or the description herein may include the use of the introductory phrases “at least one” and “one or more” to introduce claim subjects. However, the use of such phrases should not be construed as implying that any particular claim including such introduced claim subject matter is limited to including only one embodiment of such claim subject matter by the indefinite article “a” or “an”, even when the same claim includes the introductory phrase “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” or “an” should be interpreted as meaning “at least one” or “one or more”). The same applies to the use of definite articles for introducing claim subject matter. Furthermore, even when a specific number of introduced claim subject matter is explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as meaning at least the stated number (e.g., in the absence of other modifiers, a bare statement of “two subject matter” means at least two subject matter, or two or more subject matter). Furthermore, in instances where the convention of "at least one of A, B, and C" is used, generally speaking, this construction implies that a person skilled in the art will understand that the convention (e.g., "a system having at least one of A, B, and C" includes, but is not limited to, systems having A alone, having B alone, having C alone, having both A and B, having both A and C, having both B and C, and / or having both A, B, and C). In instances where the convention of "at least one of A, B, or C" is used, generally speaking, this construction implies that a person skilled in the art will understand that the convention (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, systems having A alone, having B alone, having C alone, having both A and B, having both A and C, having both B and C, and / or having both A, B, and C). A person skilled in the art will further understand that, in fact, any separate words and / or phrases presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one term, any one of the terms, or both terms.For example, the phrase “A or B” will be understood to include the possibility of “A” or “B” or “A and B”. Furthermore, as used herein, the term “any one of…” followed by a list of multiple items and / or multiple item categories is intended to include items and / or item categories individually or in combination with other items and / or other item categories, “any one of…”, “any combination of…”, “any multiple of…”, and / or “any combination of multiples of…”. Furthermore, as used herein, the term “set” is intended to include any number of items, including zero. Furthermore, as used herein, the term “quantity” is intended to include any quantity, including zero. And, as used herein, the term “many” is intended to be synonymous with “multiple”.

[0328] Furthermore, in the case of the description of features or aspects of this disclosure in accordance with the Markush Group, those skilled in the art will recognize that this disclosure is therefore also described in accordance with any individual member of the Markush Group or a subgroup of its members.

[0329] As those skilled in the art will understand, for any and all purposes (such as for providing a written description), all scopes disclosed herein also encompass any and all possible subscopes and combinations thereof. Any listed scope can be readily identified as sufficiently descriptive and such that the same scope can be divided into at least two equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each scope discussed herein can be readily divided into a lower third, a middle third, and an upper third, etc. As those skilled in the art will also understand, all language such as “at most,” “at least,” “greater than,” “less than,” etc., includes the referenced number and refers to a scope that can subsequently be divided into subscopes as discussed above. Finally, as those skilled in the art will understand, a scope includes each individual member. 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 a group having 1, 2, 3, 4, or 5 cells, and so on.

[0330] Furthermore, unless otherwise stated, the claims should not be construed as being limited to the order or elements provided. Additionally, the use of the term "means for..." in any claim is intended to invoke the claim format of 35 USC §112, ¶ 6 or means plus function, and any claim without the term "means for..." is not intended to be so.

Claims

1. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: First information is obtained indicating a configuration associated with at least one low-power wake-up signal (LP-WUS) type, said configuration including at least one reception duration and at least one energy storage threshold; Determine if LP-WUS monitoring is active; The type of LP-WUS to be monitored is determined by comparing the energy storage status of the WTRU with the at least one energy storage threshold. as well as At least one LP-WUS is received from the network node during the at least one reception duration based on the determined LP-WUS type and based on the first information.

2. The method of claim 1, wherein the at least one energy storage threshold includes a first energy storage threshold, wherein the at least one reception duration includes a first reception duration associated with the first energy storage threshold, and further comprises: Based on the energy storage status of the WTRU satisfying the first energy storage threshold, a first LP-WUS associated with a first type is received during the first reception duration, and a second LP-WUS associated with a second type is received after the first reception duration.

3. The method of claim 2, wherein the at least one energy storage threshold includes a second energy storage threshold, wherein the second energy storage threshold is less than the energy storage threshold, wherein the at least one reception duration includes a second reception duration associated with the second energy storage threshold, and further comprises: Based on the energy storage status of the WTRU satisfying the first energy storage threshold and based on the energy storage status of the WTRU satisfying the second energy storage threshold, the first LP-WUS is received during the second reception duration, and the second LP-WUS is received after the second reception duration.

4. The method according to claim 3, further comprising: Based on the energy storage status of the WTRU meeting the second energy storage threshold, the second LP-WUS is received.

5. The method according to any one of claims 2-4, wherein the first type is an LP-WUS without an energy harvesting sequence, and the second type is an LP-WUS with an energy harvesting sequence.

6. The method according to any one of claims 1-5, further comprising sending second information to the network node indicating the type of the determined LP-WUS.

7. The method according to any one of claims 1-6, wherein determining the activation of LP-WUS monitoring includes receiving third information from the network node indicating the activation of LP-WUS monitoring.

8. The method according to any one of claims 1-6, wherein determining the activation of LP-WUS monitoring is based on one or more WTRU measurements.

9. The method according to any one of claims 1-8, further comprising, upon receiving the at least one LP-WUS, monitoring the physical downlink control channel associated with paging.

10. The method according to any one of claims 1-9, further comprising, upon determining that LP-WUS monitoring is activated, sending the energy storage status of the WTRU to the network node.

11. A wireless transmit / receive unit (WTRU) comprising a processor, a transmitter, a receiver, and a memory, said WTRU being configured to: First information is obtained indicating a configuration associated with at least one low-power wake-up signal (LP-WUS) type, said configuration including at least one reception duration and at least one energy storage threshold; Determine if LP-WUS monitoring is active; The type of LP-WUS to be monitored is determined by comparing the energy storage status of the WTRU with the at least one energy storage threshold. as well as Based on the determined type of LP-WUS and based on the first information, at least one LP-WUS is received from the network node during the at least one reception duration.

12. The WTRU of claim 11, wherein the at least one energy storage threshold includes a first energy storage threshold, wherein the at least one reception duration includes a first reception duration associated with the first energy storage threshold, and further comprises: Based on the energy storage status of the WTRU satisfying the first energy storage threshold, a first LP-WUS associated with a first type is received during the first reception duration, and a second LP-WUS associated with a second type is received after the first reception duration.

13. The WTRU of claim 12, wherein the at least one energy storage threshold includes a second energy storage threshold, wherein the second energy storage threshold is less than the energy storage threshold, wherein the at least one reception duration includes a second reception duration associated with the second energy storage threshold, and further comprises: Based on the energy storage status of the WTRU satisfying the first energy storage threshold and based on the energy storage status of the WTRU satisfying the second energy storage threshold, the first LP-WUS is received during the second reception duration, and the second LP-WUS is received after the second reception duration.

14. The WTRU of claim 13, further comprising: Based on the energy storage status of the WTRU meeting the second energy storage threshold, the second LP-WUS is received.

15. The WTRU according to any one of claims 12-14, wherein the first type is an LP-WUS without an energy harvesting sequence, and the second type is an LP-WUS with an energy harvesting sequence.

16. The WTRU according to any one of claims 11-15, further comprising sending second information to the network node indicating the type of the determined LP-WUS.

17. The WTRU according to any one of claims 11-16, wherein determining the activation of LP-WUS monitoring includes receiving third information from the network node indicating the activation of LP-WUS monitoring.

18. The WTRU according to any one of claims 11-16, wherein determining the activation of LP-WUS monitoring is based on one or more WTRU measurements.

19. The WTRU according to any one of claims 11-18, further comprising, upon receiving the at least one LP-WUS, monitoring the physical downlink control channel associated with paging.

20. The WTRU according to any one of claims 11-19, further comprising, upon determining that LP-WUS monitoring is activated, sending the energy storage status of the WTRU to the network node.

Images