Determining suitability of LP-WUS monitoring in RRC state or LP-WUS configuration

Abstract

A wireless transmit / receive unit (WTRU) may receive configuration information from a network that activates the WTRU to perform low power (LP) signal monitoring using a low power radio of the WTRU. The configuration information may indicate a threshold associated with the condition. The condition may be associated with LP signal monitoring. The WTRU may receive an indication to determine suitability of the WTRU for LP signal monitoring. The WTRU may determine suitability of the WTRU for LP signal monitoring based on a threshold associated with the condition. The WTRU may send a report indicating the determination.

Description

[0001] Cross Reference to Related Applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 518,000, filed August 7, 2023, the entire contents of which are incorporated herein by reference. BACKGROUND

[0002] Low power wake-up signal (LP-WUS) monitoring can reduce power consumption of a WTRU and / or other small battery powered devices. A separate ultra-low power receiver can monitor a wake-up signal (WUS) and / or trigger a main radio (MR). The MR can be dedicated to data and control signal transmission and / or reception.

[0003] For example, a deep sleep state can be supported for the MR when the WTRU is in an RRC IDLE and / or RRC INACTIVE state. Skipping monitoring PDCCH when the WTRU is in an RRC CONNECTED state can also be supported. SUMMARY

[0004] Systems and methods as described herein can include a wireless transmit / receive unit (WTRU) determination of one or more RRC states and / or one or more LP-WUS configurations. A wireless transmit / receive unit (WTRU) can receive configuration information from a network that activates the WTRU to perform LP signal monitoring using a low power radio of the WTRU. The configuration information can indicate a threshold associated with a condition. The WTRU can receive an indication to determine suitability of the WTRU for low power (LP) signal monitoring. The WTRU can determine suitability of the WTRU for LP signal monitoring based on the threshold associated with the condition. The WTRU can transmit a report indicating the determination.

[0005] The WTRU can determine suitability of the WTRU for LP signal monitoring based on a state of the WTRU. The state of the WTRU can be a connected mode, an idle mode, or an inactive mode.

[0006] In an example, the WTRU can receive the configuration information via a main radio of the WTRU. The WTRU can receive the indication via the main radio of the WTRU. The WTRU can transmit the report via the main radio of the WTRU. The WTRU can receive the configuration via the main radio of the WTRU. In response to receiving the configuration from the network that activates the WTRU to perform LP signal monitoring, the WTRU can also monitor a low power signal via a low power radio of the WTRU.

[0007] In one embodiment, the condition may include any one or more of the following: LP signal, signal received by the main radio (MR), beam quality of the beam associated with the WTRU's main radio, beam quality of the beam associated with the WTRU's low-power radio, WTRU activity, WTRU mobility, WTRU location, coverage area of ​​the WTRU's low-power radio, or coverage gap between the WTRU's low-power radio and the WTRU's main radio.

[0008] In another example, the indication may include the Radio Resource Control (RRC) status by which the WTRU determines its suitability for LP signal monitoring.

[0009] In another embodiment, the configuration information may indicate multiple thresholds and multiple conditions. Each of the multiple thresholds may be associated with a Radio Resource Control (RRC) state or the periodicity of a low-power signal. The report may indicate the suitability of the WTRU for LP signal monitoring for each RRC state or periodicity of the low-power signal.

[0010] The WTRU can receive a second instruction to perform LP signal monitoring periodically in a first Radio Resource Control (RRC) state or with a first low-power signal. The WTRU can also monitor the LP signal using its low-power radio according to the second instruction.

[0011] When the mobility parameter is greater than the mobility threshold, the activity parameter is greater than the activity threshold, or the beam quality measurement is less than the beam quality threshold, the WTRU can determine that LP signal monitoring is unsuitable.

[0012] When the mobility parameter is less than the mobility threshold, the activity parameter is less than the activity threshold, or the beam quality measurement is greater than the beam quality threshold, the WTRU can determine that LP signal monitoring is appropriate.

[0013] This report can indicate the conditions used to determine the suitability of the WTRU for LP signal monitoring. Attached Figure Description

[0014] Figure 1A This is a system diagram illustrating an example communication system in which one or more of the disclosed embodiments may be implemented.

[0015] Figure 1B The illustration shows a method according to one embodiment. Figure 1A The diagram shows a system diagram of an example wireless transmit / receive unit (WTRU) used in a communication system.

[0016] Figure 1C The illustration shows a method according to one embodiment. Figure 1AThe diagram illustrates a system diagram of an example radio access network (RAN) and an example core network (CN) used in the communication system.

[0017] Figure 1D The illustration shows a method according to one embodiment. Figure 1A The illustrated system diagram shows yet another example RAN and yet another example CN used in the communication system.

[0018] Figure 2 This is a diagram illustrating an example receiver architecture for a WTRU that utilizes a low-power wake-up receiver. Detailed Implementation

[0019] Figure 1A This is a schematic diagram 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 Unique Word DFT Spread Spectrum OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0020] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, Public Switched Telephone Network (PSTN) 108, Internet 110, and other networks 112. 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, and 102d may 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 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 WTRUs.

[0021] 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 to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), node B, eNode B, home node B, home eNode B, gNB, NR node B, site controller, access point (AP), wireless router, 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 stations and / or network elements.

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

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

[0024] 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 air interfaces 115 / 116 / 117 using Wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or evolved HSPA (HSPA+). HSPA may include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​UL Packet Access (HSUPA).

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

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

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

[0028] In other embodiments, base station 114a and WTRUs 102a, 102b, 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), GSM EDGE (GERAN), etc.

[0029] For example, Figure 1ABase station 114b can be a wireless router, home node B, home eNodeB, 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, 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, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish 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.

[0030] 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 1A Although 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 connecting to RAN 104 / 113, which may utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0031] 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 / 113 or a different RAT.

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

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

[0034] 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 an electronic package or chip.

[0035] 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 yet another 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.

[0036] 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. More specifically, WTRU 102 may employ MIMO technology. Thus, 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.

[0037] 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, for example, NR and IEEE 802.11.

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

[0039] 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 for powering 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.

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

[0041] The processor 118 may be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or videos), 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. Peripheral devices 138 may include one or more sensors, which may be one or more of the following: 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.

[0042] 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 UL (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 139 to reduce and / or substantially eliminate self-interference via hardware (e.g., a choke) 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 UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

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

[0044] 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. eNode-Bs 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 / or receive radio signals from WTRU 102a.

[0045] 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 UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160c can communicate with each other on the X2 interface.

[0046] 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 (or 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.

[0047] The MME 162 can connect to each of the eNode-Bs 162a, 162b, and 162c 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.

[0048] 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 inter-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.

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

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

[0051] Despite WTRU in Figures 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.

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

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

[0054] When using 802.11ac infrastructure operating mode or a similar operating 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.

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

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

[0057] 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 can support metering-type control / machine-type communications, 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).

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

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

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

[0061] 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 gNBs 180a, 180b, and 180c. Therefore, for example, gNB 180a may use multiple antennas to transmit radio signals to 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).

[0062] 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., containing a variable number of OFDM symbols and / or a continuously variable absolute time).

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

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

[0065] 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 possibly a 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.

[0066] 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 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 to customize CN support for WTRU 102a, 102b, and 102c based on the service types 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 Machine Type Communication (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 WiFi.

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

[0068] 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 provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) 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.

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

[0070] Given Figures 1A-1D as well as Figures 1A-1D The corresponding descriptions herein indicate that one or more of the following functions can be performed by one or more emulation 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, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) 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.

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

[0072] One or more simulation 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, simulation devices may be used to test test scenarios in laboratory and / or non-deployment (e.g., testing) wired and / or wireless communication networks to implement the testing of one or more components. One or more simulation devices may be test devices. Simulation 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).

[0073] Figure 2 An example receiver architecture for a WTRU using a low-power wake-up receiver is depicted. Low-power wake-up signal (LP-WUS) monitoring can reduce power consumption of the WTRU and / or other small battery-powered devices. A separate ultra-low-power receiver can monitor the wake-up signal (WUS) and / or trigger the master radio (MR). The MR can be dedicated to data and control signal transmission and / or reception, such as... Figure 2 As shown.

[0074] For example, deep sleep states of the MR can be supported when the WTRU is in RRC IDLE and / or RRC INACTIVE states. It can also be supported that the WTRU skips monitoring the Physical Downlink Control Channel (PDCCH) when in RRC CONNECTED state.

[0075] The systems and methods described herein can allow for power savings. The level of power savings achievable through LP-WUS monitoring can depend on selecting (e.g., the correct) LP-WUS monitoring configuration (e.g., the MR is in deep sleep when the WTRU is in RRC IDLE, the WTRU skips monitoring the PDCCH when the MR is in RRC CONNECTED, etc.), activating Low Power Wake-up Signal (LP-WUS) monitoring under (e.g., appropriate) conditions (e.g., WTRU activity level, WTRU mobility level, link quality level), and / or selecting (e.g., appropriate) LP-WUS monitoring settings (e.g., appropriate link / beam quality for LP-WUS monitoring), etc. The systems and methods described herein may involve selecting (e.g., the correct) LP-WUS monitoring configuration, selecting (e.g., appropriate) conditions for activating LP-WUS monitoring, and / or selecting (e.g., appropriate) (one or more) beams / links for LP-WUS monitoring.

[0076] For example, in different RRC states and / or LP-WUS configurations, the WTRU can determine the suitability and / or feasibility of LP-WUS monitoring. The WTRU determination of the suitability and / or feasibility of LP-WUS monitoring in different RRC states can be based on, for example, one or more conditions and one or more thresholds configured and / or indicated by the gNB.

[0077] The WTRU may receive, for example, configuration information from the gNB for satisfying one or more conditions for LP-WUS monitoring (e.g., monitoring of low-power synchronization signals (LP-SS), LP-WUS, LP-PDCCH via low-power wake-up radio (LP-WUR)). WUS monitoring conditions may include one or more of the following: link / beam quality, WTRU activity, WTRU mobility, location, LR coverage / LR-MR coverage gap (e.g., coverage gap between LR and MR), and / or so on.

[0078] Configuration (e.g., configuration information) may include one or more thresholds (e.g., a first threshold, a second threshold, ..., a k-th threshold) for LP-WUS monitoring conditions (e.g., for each condition). The k-th threshold (e.g., for a specific condition) may be associated with the k-th RRC state of the WTRU during LP-WUS monitoring (e.g., RRCIDLE, RRC INACTIVE, and RRC CONNECTED states), and / or LP-WUS configuration (e.g., LP-WUS periodicity) may be associated with LP-WUS monitoring.

[0079] The WTRU can receive from the gNB indications for testing the suitability and / or feasibility of using LP-WUS monitoring with one or more RRC states and / or LP-WUS configurations (e.g., LP-WUS periodicity). The Radio Resource Control (RRC) states (one or more) for which suitability and / or feasibility have been tested can be determined by the WTRU based on, for example, one or more explicit indications and / or the WTRU's current RRC state (e.g., CONNECTED state). These indications can be received via one or more of the following: requests for CSI-RS measurements and / or reports for one or more beams associated with the LR; capability queries related to WUS monitoring; activation of a specific TCI state; and / or explicit indications (e.g., via MAC-CE, Downlink Control Information (DCI), RRC).

[0080] WTRU can determine the suitability and / or feasibility of monitoring LP-WUS in one or more (e.g., each) of the indicated one or more RRC states, for example, based on one or more configured conditions and a corresponding threshold for each of the one or more RRC states.

[0081] For example, if WTRU mobility is greater than the mobility threshold for the k-th RRC state, then LP-WUS monitoring may be infeasible / unsuitable for the k-th RRC state. If WTRU mobility is less than the mobility threshold for the k-th RRC state, then LP-WUS monitoring may be feasible / suitable for the k-th RRC state.

[0082] For example, if the WTRU activity level (e.g., the number of SRs emitted during a pre-configured time window) is greater than the activity threshold for the k-th RRC state, then LP-WUS monitoring may be infeasible / unsuitable for the k-th RRC state. If the WTRU activity level is less than the activity level threshold for the k-th RRC state, then LP-WUS monitoring may be feasible / suitable for the k-th RRC state.

[0083] For example, if the link quality is greater than the link quality threshold for the k-th RRC state, then LP-WUS monitoring may be feasible / suitable for the k-th RRC state. If the link quality is less than the link quality threshold for the k-th RRC state, then LP-WUS monitoring may be infeasible / unsuitable for the k-th RRC state.

[0084] For example, based on a suitability / feasibility determination, the WTRU can report the suitability / feasibility monitored by LP-WUS in one or more RRC states (e.g., each RRC state). This report may include one or more of the following: indications of feasibility / suitability or infeasibility / unsuitability (e.g., for each RRC state); and / or conditions that do not meet the suitability / feasibility criteria (e.g., included separately for each RRC state), such as if infeasibility / unsuitability is met for one or more conditions. Suitability / feasibility reports can be transmitted using MAC-CE indications, via the Physical Uplink Control Channel (PUCCH), via the Physical Uplink Shared Channel (PUSCH), and / or via one or more of PRACH Tx.

[0085] The WTRU can, for example, receive an instruction / configuration from the gNB / network that indicates / activates the use of LP-WUS monitoring.

[0086] The WTRU can receive an RRC release message from the gNB indicating that it has entered the RRC INACTIVE state. The release message may include an indication of monitoring using LP-WUS.

[0087] When in RRC CONNECTED state, the WTRU can receive instructions from the gNB regarding the use of LP-WUS monitoring in CONNECTED state.

[0088] WTRU can receive non-access stratum (NAS) messages indicating that LP-WUS monitoring is used in the RRC IDLE state.

[0089] WTRU can use LP-WUS monitoring in RRC status, for example, based on indications received from the gNB / network.

[0090] For example, when in an RRC state (e.g., RRC CONNECTED, RRC IDLE, RRC INACTIVE state), the WTRU can monitor LP-SS and / or LP-WUS. The WTRU can monitor and / or receive one or more DL signals (e.g., PDCCH) based, for example, on the reception of LP-WUS.

[0091] For example, when in an RRC state (e.g., RRC CONNECTED, RRC IDLE, RRC INACTIVE state), the WTRU can monitor LP-SS and / or LP-WUS. For example, the WTRU can monitor and / or receive one or more paging-related signals (e.g., paging PDCCH / DCI, Permanent Device Identifier (PEI)) based on the reception of LP_WUS.

[0092] The systems and methods described herein may include beam determination for LP-WUS monitoring. The WTRU may, for example, determine one or more beams(s) for LP-WUS reception using a second set of BFR thresholds. It may be assumed that the MR and LR share the same RF hardware.

[0093] The WTRU can receive configuration information. This configuration may include a first beam failure recovery (BFR) resource set and / or a first set of BFR thresholds and / or a second set of thresholds. The first set of thresholds may be associated with (e.g., routine) operation of the main radio (MR). The second set of thresholds may be associated with LP-WUS thresholds or BFR thresholds. The WTRU may, for example, determine whether to monitor and / or select a beam set for low-power wake-up signal (LP-WUS) monitoring based on one or more measurements associated with this beam set and the second set of thresholds. The WTRU may send a report message indicating this determination.

[0094] The WTRU can receive an indication message for determining whether to select the beam set for LP-WUS monitoring. This configuration may include a second threshold and / or a second set of thresholds. The second threshold and / or the second set of thresholds may be associated with beam failure detection. The second threshold and / or the second set of thresholds may include one or more of the following: an LP-WUS block error rate (BLER) threshold, an estimated LP-WUS BLER threshold, an estimated physical downlink control channel (PDCCH) BLER threshold, a reference signal received power (RSRP) threshold, a beam selection threshold, and / or a beam failure indication (BFI) count threshold.

[0095] The WTRU can receive configurations for a first BFR resource set and / or a first set of BFR thresholds for general operation utilizing MR and / or a second set of thresholds (e.g., LP-WUS thresholds, BFR thresholds) for determining the beams used for LP-WUS surveillance utilizing LR. The first BFR resource set may include one or more of the following: a first beam set (e.g., BFD RS and / or PDCCH surveillance beams), a first candidate beam set (e.g., BFR candidate beams), a first PRACH resource set for beam failure indication, and / or so on. The first set of BFR thresholds may include one or more of the following: a first failure detection threshold (e.g., a first assumed PDCCH BLER threshold, a first failure detection RSRP threshold), a first new beam selection threshold, a first BFI maximum count, and / or so on. The second set of thresholds may include one or more of the following: a second failure detection threshold (e.g., an assumed LP-WUS BLER threshold, a second assumed PDCCH BLER threshold, a second failure detection RSRP threshold), a second new beam selection threshold, a second BFI maximum count, and / or so on.

[0096] The WTRU can receive indications from the gNB for determining the beams used for LP-WUS surveillance. For example, based on one or more beam measurements associated with a first beam set and / or a first set of BFR thresholds, the WTRU can determine that there is no beam failure for UL / DL communication (i.e., when using MR). For example, based on one or more measurements associated with one or more first beam sets and / or a second set of thresholds, the WTRU can determine the suitability / unsuitability of the first beam set for LP-WUS surveillance utilizing LR.

[0097] For example, if the assumed PDCCH BLER of the PDCCH surveillance beam is less than the second assumed LP-WUS BLER threshold, then the WTRU can determine that the PDCCH surveillance beam is suitable for LP-WUS surveillance. Conversely, if the assumed PDCCH BLER of the PDCCH surveillance beam is greater than the second assumed LP-WUS BLER threshold, then the WTRU can determine that the PDCCH surveillance beam is not suitable for LP-WUS surveillance.

[0098] For example, if the RSRP of the BFD RS is greater than the second failure detection RSRP threshold, the WTRU can determine that the BFD RS is suitable for LP-WUS surveillance. Conversely, if the RSRP of the BFD RS is less than the second failure detection RSRP threshold, the WTRU can determine that the BFD RS beam is not suitable for LP-WUS surveillance.

[0099] For example, if the WTRU determines that one or more beams in the first beam set are suitable for LP-WUS surveillance using the LR, the WTRU may indicate to the gNB at least one (e.g., all) of the identified one or more beams (e.g., via PUCCH, PUSCH / MAC-CE, or by using one or more pre-configured PRACH resources (e.g., a second set)).

[0100] For example, if the WTRU determines that no beam in the first beam set can be used for LP-WUS surveillance (by using LR), the WTRU can select one or more beams from the first candidate beam set for LP-WUS surveillance.

[0101] The WTRU can measure the beam quality (e.g., RSRP) of the first candidate beam set. The WTRU can determine one or more beams for LP-WUS surveillance, for example, based on one or more measurements associated with one or more first candidate beam sets and / or a second new beam selection threshold. The WTRU can indicate to the gNB at least one (e.g., all) of the selected one or more beams (e.g., transmitted via PUCCH, PUSCH / MAC-CE, or by using one or more pre-configured PRACH resources (a third set). For example, if the WTRU determines that there are no beams suitable for LP-WUS surveillance in either the first beam set or the first candidate beam set, the WTRU can indicate to the gNB that no suitable beams were found for LP-WUS surveillance (e.g., transmitted via PUCCH, PUSCH, or by using pre-configured PRACH resources).

[0102] The WTRU can receive indications and / or configurations from the gNB and / or network indicating / activating the use of LP-WUS monitoring. The WTRU can receive indications and / or configurations for a first set of beams used for LP-WUS monitoring. The WTRU can receive and / or activate such indications after sending an indication for one or more selected or suitable beams (e.g., from the first set of beams or a first candidate set of beams) used for LP-WUS monitoring.

[0103] The WTRU can receive from the gNB an indication of using LP-WUS monitoring when in CONNECTED state, and / or an acknowledgment indication (e.g., a 1-bit indication) for LP-WUS monitoring using a beam selected and indicated by the WTRU.

[0104] The WTRU can receive RRC release messages from the gNB. RRC release messages can indicate entry into the RRC INACTIVE state. Release messages may include indications for using LP-WUS monitoring. The WTRU can receive beam subset configurations and / or indications (e.g., in a bitmap). Beam subsets can be derived from the WTRU selecting and / or indicating the beams used for LP-WUS monitoring.

[0105] The WTRU can use one or more of the indicated and / or configured beams. Alternatively, the WTRU can monitor the LP-WUS, for example, to detect wake-up indications from the gNB.

[0106] The WTRU can use one or more of the indicated / configured beams to monitor LP-SS and / or LP-WUS, for example, when under LP-WUS monitoring in RRC connected state. The WTRU can monitor and / or receive one or more DL signals (e.g., PDCCH) based, for example, on LP-WUS reception. The WTRU can determine PDCCH monitoring resources (e.g., search space and / or PDCCH monitoring timing) based, for example, on the configured association between the indicated / configured beams and PDCCH monitoring resources.

[0107] The WTRU can use one or more of the indicated / configured beams to monitor LP-SS and / or LP-WUS, for example, when monitoring LP-WUS in RRC IDLE or RRC INACTIVE states. The WTRU can monitor and / or receive one or more paging-related signals (e.g., paging PDCCH / DCI, PEI) based, for example, on indications received on LP-WUS.

[0108] The WTRU can transmit and / or receive physical channels and / or reference signals, for example, based on at least one spatial domain filter. The term "beam" can be used to refer to a spatial domain filter.

[0109] The WTRU can use the same spatial domain filter used to receive RS (e.g., CSI-RS) and / or SS blocks to transmit physical channels and / or signals. The WTRU transmission can be referred to as the "target". The received RS and / or SS blocks can be referred to as the "reference" and / or "source". It can be said that the WTRU transmits the target physical channel and / or signals based on the spatial relationships of such RS and / or SS blocks.

[0110] The WTRU can transmit the first physical channel and / or signal using the same spatial domain filter as the spatial domain filter used to transmit the second physical channel and / or signal. The first transmission and the second transmission can be referred to as "target" and "reference" or "source," respectively. It can be said that the WTRU transmits the first (e.g., target) physical channel and / or signal based on the spatial relationship of the reference second (e.g., reference) physical channel or signal.

[0111] Spatial relationships can be implicit, configured by the RRC, and / or signaled by the MAC CE and / or DCI. For example, the WTRU can implicitly transmit the PUSCH and / or the DM-RS of the PUSCH according to the same spatial domain filter as the SRS, which is indicated by the SRI indicated in the DCI and / or configured by the RRC. In another example, spatial relationships can be configured by the RRC for the SRS Resource Indicator (SRI) and / or signaled by the MAC CE for the PUCCH. (For example, such spatial relationships can also be referred to as "beam indications".)

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

[0113] Beam measurement and / or beam quality measurement and / or beam quality can refer to one or more of the following parameters measured and / or estimated and / or derived, for example, based on measurements performed on a beam or beam set: RSRP, RSRQ, RSSI, SINR, CQI, RI, LI, PMI, CRI, AoA, AoD, Doppler spread, Doppler shift, average Doppler, delay spread, average delay, and / or channel occupancy.

[0114] Differential beam measurement and / or spatial differential beam measurement of two beams are the differences between two beam measurements. For example, the spatial differential L1-RSRP of two beams can be the difference between the L1-RSRPs of the two beams.

[0115] Time-domain differential beam measurement can be the difference between beam measurements of the same beam at two different times. For example, the time-domain differential L1-RSRP of a beam can be the difference between the L1-RSRP of the beam at two different times.

[0116] LP-WUS monitoring can refer to monitoring, detecting, decoding, and / or receiving one or more signals associated with a Low Power Wake-up Radio (LR). For example, a Low Power Synchronization Signal (LP-SS) can help the LR maintain time synchronization with the gNB. LP-WUS can instruct the WTRU to perform one or more operations based on the content and / or presence of the signal. For example, upon receiving LP-WUS, the WTRU can wake up its MR for PDCCH monitoring. In another example, upon receiving LP-WUS, a group of WTRUs can wake up their MRs during their next DRX on-duty period for PDCCH / DCI reception or to receive Early Paging Indication (PEI). The MR and LR can share radio frequency hardware. The WTRU can receive LP-WUS using the MR. The WTRU can receive configuration information via its master radio. The WTRU can receive indications via its master radio.

[0117] For example, in different RRC states and / or LP-WUS configurations, the WTRU can determine the suitability and / or feasibility of LP-WUS monitoring. The WTRU can determine the suitability and / or feasibility of LP-WUS monitoring in different RRC states and / or LP-WUS configurations based on conditions and / or thresholds configured and / or indicated by the gNB. The WTRU can receive configurations indicating thresholds associated with the conditions. The WTRU can receive configurations from the gNB for satisfying one or more conditions for LP-WUS monitoring (e.g., monitoring LP-SS, LP-WUS, and / or LP-PDCCH via LP-WUR) or low-power signal monitoring. WUS monitoring conditions may include one or more of link / beam quality, WTRU activity, WTRU mobility, location, low-power wake-up radio (LR) coverage / LR-MR coverage gap (e.g., the coverage gap between LR and MR) and / or so on. Configurations may include, for example, a first threshold, a second threshold, ..., a k-th threshold for each LP-WUS monitoring condition. The kth threshold (e.g., for a specific condition) can be associated with the kth RRC state of the WTRU during LP-WUS monitoring (e.g., RRC IDLE, RRC INACTIVE, and / or RRC CONNECTED state) and / or condition (e.g., LP-WUS periodicity).

[0118] The WTRU can receive from the gNB an indication that it is testing the suitability and / or feasibility of using LP-WUS monitoring using one or more RRC states and / or LP-WUS configurations (e.g., LP-WUS periodicity). The RRC states(s) for which suitability and / or feasibility should be tested can be determined by the WTRU based on one or more explicit indications and / or the WTRU's current RRC state (e.g., CONNECTED state), or based on condition-related thresholds. The WTRU's suitability for LP signal monitoring can be based on the WTRU's state. The CONNECTED state can be connected mode, idle mode, or inactive mode. This indication can be received via one or more of the following: requests for CSI-RS measurements and / or reports for one or more beams associated with the LR; capability queries related to WUS monitoring; (specific) TCI state activation; and / or explicit indications (e.g., via MAC-CE, DCI, and / or RRC).

[0119] WTRU can determine the suitability and / or feasibility of monitoring LP-WUS in each of the indicated one or more RRC states, for example, based on one or more configured conditions and / or a corresponding threshold for each of the one or more RRC states.

[0120] For example, if WTRU mobility is greater than the mobility threshold for the k-th RRC state, then LP-WUS monitoring may be infeasible / unsuitable for the k-th RRC state. Conversely, if WTRU mobility is less than the mobility threshold for the k-th RRC state, then LP-WUS monitoring may be feasible / suitable for the k-th RRC state.

[0121] For example, if the WTRU activity level (e.g., the number of SRs emitted during a pre-configured time window) is greater than the activity threshold for the k-th RRC state, then LP-WUS monitoring may be infeasible / unsuitable for the k-th RRC state. Conversely, if the WTRU activity level is less than the activity level threshold for the k-th RRC state, then LP-WUS monitoring may be feasible / suitable for the k-th RRC state.

[0122] For example, if the link quality is greater than the link quality threshold for the k-th RRC state, then LP-WUS monitoring may be feasible / suitable for the k-th RRC state. Conversely, if the link quality is less than the link quality threshold for the k-th RRC state, then LP-WUS monitoring may be infeasible / unsuitable for the k-th RRC state.

[0123] For example, based on a suitability / feasibility determination, the WTRU can report the suitability / feasibility of LP-WUS monitoring in one or more (e.g., each) of one or more RRC states and / or LP-WUS configurations (e.g., LP-WUS periodicity). The report may include one or more of the following: indications of feasibility / suitability or infeasibility / unsuitability (e.g., for each RRC state); conditions that do not meet the suitability / feasibility criteria may be indicated in the report (e.g., included separately for each RRC state), for example, if one or more conditions are infeasible / unsuitable. The suitability / feasibility report can be transmitted using MAC-CE indication, via PUCCH, via PUSCH, and / or via PRACH Tx, or more. The report may indicate the determined suitability of the WTRU for LP signal monitoring. The WTRU may transmit the report via its main radio. The WTRU may receive configuration via its main radio. In response to receiving configuration from the network to activate the WTRU to perform LP signal monitoring, the WTRU may monitor low-power signals via its low-power radio.

[0124] Ancillary information used to determine LP-WUS configuration (e.g., LP-WUS periodicity) may include LP signals, signals received by the main radio (MR), WTRU activity level, beam quality measurements of one or more beams, LR coverage (coverage area of ​​the WTRU's low-power radio), coverage gap between the WTRU's low-power radio and the WTRU's main radio, WTRU mobility (e.g., speed of movement, direction of movement), and / or WTRU location, or one or more of these. The WTRU may receive an indication / configuration from the gNB / network that indicates / activates the use of LP-WUS monitoring. This configuration may activate the WTRU to perform LP signal monitoring using its low-power radio. The WTRU may receive an RRC release message from the gNB indicating entry into the RRCINACTIVE state. The release message may include an indication to use LP-WUS monitoring. When in the RRCCONNECTED state, the WTRU may receive an indication from the gNB to use LP-WUS monitoring in the CONNECTED state. The WTRU may receive NAS messages, such as indications to use LP-WUS monitoring in the RRC IDLE state.

[0125] The WTRU can monitor LP-WUS in RRC states, for example, based on indications received from the gNB / network. For instance, when in an RRC state (e.g., RRC CONNECTED, RRC IDLE, RRC INACTIVE states), the WTRU can monitor LP-SS and / or LP-WUS. The WTRU can monitor and / or receive one or more DL signals (e.g., PDCCH) based on LP-WUS reception. For instance, when in an RRC state (e.g., RRC CONNECTED, RRC IDLE, RRC INACTIVE states), the WTRU can monitor LP-SS and / or LP-WUS. For instance, the WTRU can monitor and / or receive one or more paging-related signals (e.g., paging PDCCH / DCI, PEI) based on LP-WUS reception.

[0126] The WTRU can be configured to monitor one or more LP-WUS and / or associated signals (e.g., LP-SS) via, for example, LR and / or using MR radio frequency (RF) hardware (e.g., when the LR and MR share RF hardware). The WTRU can be configured to monitor one or more LP-WUS and / or associated signals while the WTRU is in different RRC states. For example, the WTRU can be configured to monitor LP-WUS while in an RRC CONNECTED state. The WTRU can (e.g., then) skip receiving one or more PDCCHs (e.g., all) until / unless instructed to wake up the master receiver (MR) and / or decode such a PDCCH by an LP-WUS received via a low-power wake-up radio (LR). In another example, as described herein, the WTRU can be configured to monitor LP-WUS while the WTRU is in an RRC IDLE state or an RRC INACTIVE state. The WTRU can (e.g., then) skip one or more paging messages from the gNB / network until / unless instructed to wake up the MR and receive such a paging message by an LP-WUS received via the LR. One or more LP-WUS and / or associated signals (e.g., LP-SS) and / or LP-WUR can be configured differently. For example, LP-WUS / LP-WUR can be configured with one or more of the following: different periodicity (e.g., first periodicity, second periodicity, and / or etc.), different subcarrier spacing (SCS) values, different bandwidths, different carrier frequencies, different configurations related to MR operation in the absence of one or more configured / scheduled LP-WUS (e.g., MR wake-up or MR not wake-up), and / or different configurations related to LR operation in the absence of one or more configured / scheduled LP-WUS (e.g., LR increases monitoring frequency / LR decreases monitoring periodicity).

[0127] The RRC status of the WTRU for LP-WUS monitoring and / or the suitability / feasibility of the LP-WUS configuration may depend on the different conditions the WTRU is experiencing and / or has experienced. This indication may include the RRC status of the WTRU used to determine its suitability for LP signal monitoring. Information about the WTRU's conditions (e.g., some conditions) / its status can be readily obtained from the gNB. Information about some of these conditions / its status is generally known to the WTRU, and / or the most recently updated information / status is available at the WTRU (e.g., most of the time). For example, the gNB can readily know the DL buffer status and / or the availability of pending HARQ feedback. In another example, one or more of the following may be known to the WTRU: WTRU activity (e.g., the number of SRs transmitted in a pre-configured time window), WTRU mobility (e.g., speed, direction of movement), beam quality, radio link quality, location, LR coverage, LR-MR coverage gap, etc. (e.g., known only to the WTRU). Additionally or alternatively, the WTRU may know the most current information / status. There may be consideration of one or more conditions, such as determining the appropriate RRC status and / or LP-WUS / LP-WUR configuration.

[0128] The WTRU can use one or more of the following solutions to determine the suitability / feasibility of LP-WUS monitoring with different RRC states and / or LP-WUS / LP-WUR configurations. The WTRU can be equipped with one or more receivers. A first receiver (e.g., a primary receiver) can receive a first type of signal, and a second receiver (e.g., a low-power receiver) can receive a second type of signal. The first type of signal may include signals dedicated to the first receiver and used for data transmission, and the second type of signal may include signals dedicated to maintaining connectivity with the network and / or allowing the first receiver to be in an inactive mode and / or sleep mode for power saving. In this document, the first receiver may be referred to as the primary receiver (MR), and the second receiver may be referred to as a low-power wake-up receiver (LP-WUR), a low-power receiver (LR), or an auxiliary receiver (SR). The second type of signal can be at least one of LP-WUS, LP-SS, and LP-PDCCH. One or more second-type signals may generally be referred to as LP-WUS.

[0129] The WTRU can indicate the suitability and / or feasibility of receiving a second type of signal (e.g., a signal specifically designed for LP-WUR) based on one or more predefined and / or configured conditions. In this document, these conditions may be referred to as monitoring conditions. The WTRU can determine to monitor the second type of signal when one or more predefined and / or configured conditions for monitoring and / or gNB indication and / or configuration for monitoring are met.

[0130] The WTRU can receive configuration (or configuration information) and / or can be configured with one or more of the following. The configuration information can indicate multiple thresholds and multiple conditions. One or more conditions may exist to test the suitability or feasibility of LP-WUS monitoring (e.g., which may be referred to herein as suitability). The configuration information can indicate thresholds associated with the conditions. Each of the multiple thresholds can be associated with the periodicity of RRC status or low-power signals. The WTRU can receive one or more signals from the gNB via the LP-WUR. The one or more signals received via the LP-WUR may include LP-WUS. LP-WUS can instruct the MR to perform one or more of the following: begin receiving / detecting / monitoring signals from the gNB and / or other transmitters (e.g., relays, WTRUs, etc.), and / or receive one or more supporting signals (e.g., synchronization signals for LP-WUR / MR). LP-WUS monitoring conditions may include one or more of WTRU activity, WTRU mobility, beam quality, LR coverage, LR-MR coverage gap, and / or radio link quality.

[0131] WTRU activity can include calculating / determining its activity level based on one or more operations / signaling transmissions performed by the WTRU within a time window (e.g., the duration of a recently configured period). For example, the WTRU can count the number of scheduling requests (SRs) it transmits to the gNB within a pre-configured time window. In another example, the WTRU can count the number of PDCCHs and / or PDSCHs it receives within a pre-configured time window.

[0132] WTRU mobility may include one or more of the following: WTRU speed, direction of movement (e.g., towards the gNB compared to a reference direction), number of times the WTRU changes its direction of movement beyond a pre-configured angle within a time window (e.g., the duration of the configuration that has just passed), and / or change of direction of movement compared to a reference direction (e.g., direction of movement over x milliseconds / slot that has just passed).

[0133] The location of the WTRU can include the distance between the WTRU and the service node (e.g., gNB, relay, repeater, RRH). In another example, the WTRU might be located in an absolute geographic location / region.

[0134] Beam quality may include WTRU being configured to measure beam quality measurements associated with one or more beams (e.g., BFR candidate beams, BFDRS) and / or compare them with one or more pre-configured thresholds.

[0135] LR coverage may include the WTRU measuring beam quality / radio signal strength and / or measuring / estimating / determining the distance between the WTRU and the serving node (e.g., gNB, relay, RRH) using a second receiver (e.g., LR). The WTRU may (e.g., subsequently) compare the signal strength and distance between the WTRU and the serving node (e.g., using a lookup table), for example, by using the LP-WUR / LP-WUS capabilities at the WTRU and / or additional details of the LP-WUS transmitter (e.g., BW, minimum radio, LP-WUS transmit power). Alternatively or additionally, the WTRU may determine LR coverage based on measurements from a first receiver (e.g., MR).

[0136] LR-MR coverage gaps may include WTRUs measuring beam quality or signal strength of one or more beams using LR and MR measurements. The WTRU can calculate the difference between the beam quality and / or radio signal strength measurements between LR and MR. This difference can be compared to one or more pre-configured thresholds to determine the suitability of LP-WUS monitoring.

[0137] Radio link quality can include radio signal strength and / or the number of times the radio signal strength falls below a pre-configured threshold within a pre-configured time window.

[0138] A WTRU can be configured with one or more thresholds (e.g., a first threshold, a second threshold, ..., a k-th threshold, where k is an integer ≥ 1) for one or more conditions (e.g., each condition) tested to determine the suitability of LP-WUS monitoring. For example, a first WTRU activity threshold, a second WTRU activity threshold, ..., a k-th WTRU activity threshold can be associated with the LP-WUS monitoring condition of WTRU activity. The k-th threshold (e.g., for WTRU mobility or WTRU activity) can be associated with the WTRU's RRC state during LP-WUS monitoring (e.g., RRC IDLE state, RRC INACTIVE state, and / or RRC CONNECTED state) and / or one or more additional configurations associated with LP-WUS / LP-WUR (e.g., which may be referred to herein as LP-WUS configurations). LP-WUS configurations may include LP-WUS periodicity, configurations related to MR operation in the absence of one or more LP-WUS signals (e.g., MR wake-up or MR not wake-up), and / or one or more of the following.

[0139] One or more thresholds can be determined based on one or more of the periodicity of the second type of signal (e.g., LP-WUS, LP-SSB, etc.) and / or the number of repetitions of the second type of signal.

[0140] The WTRU can determine the suitability and / or feasibility of LP-WUS monitoring. The WTRU can receive instructions and / or configurations from the gNB for determining / testing the suitability of using LP-WUS monitoring. These instructions / configurations may include one or more RRC states (e.g., RRC IDLE state, RRC INACTIVE state, and / or RRC CONNECTED state) and / or one or more LP-WUS configurations (e.g., LP-WUS periodicity), for which the suitability of LP-WUS monitoring needs to be determined / tested.

[0141] The WTRU can receive indications for testing the suitability of LP-WUS monitoring via one or more of the following: requests to perform CSI-RS measurements and / or report associated measurements of one or more beams / beam resource sets associated with the LR; capability queries related to LP-WUS monitoring; activation of one or more pre-configured TCI states; and / or explicit indications.

[0142] Requests to perform CSI-RS measurements and / or report associated measurements of one or more beams / beam resource sets associated with the LR may include, for example, the WTRU receiving requests for CSI-RS measurement reports and / or beam measurement reports, where CSI-RS resources or beams are associated with the LR. For instance, based on a pre-configured association between CSI-RS resources / beams and the LR, the WTRU may determine, in addition to performing CSI measurements and reporting, the suitability of the WTRU for LP-WUS monitoring. This report may indicate the WTRU's suitability for LP signal monitoring for each RRC state or periodicity of the low-power signal.

[0143] Capability queries related to LP-WUS monitoring may include, for example, a capability query received by the WTRU requesting the WTRU to report one or more capabilities (e.g., supported BW) associated with LP-WUS / LP-WUR. The WTRU may interpret a received capability query as an implicit indication for testing the suitability of LP-WUS monitoring.

[0144] The activation of one or more pre-configured TCI states may include, for example, the WTRU receiving an indication for activating one or more pre-configured TCI states (e.g., via a PDCCH indication, MAC-CE indication). The WTRU may interpret the activation of one or more pre-configured TCI states as an implicit indication for testing the suitability of LP-WUS monitoring. The WTRU may receive another indication for performing LP signal monitoring periodically in an RRC state or with a first low-power signal. Based on this other indication, the WTRU may use its low-power radio to monitor the LP signal.

[0145] Explicit indications can be made via one or more of MAC-CE indications, DCI indications, and / or RRC signaling.

[0146] The WTRU can receive indications and / or configurations regarding RRC status and / or LP-WUS configuration, for which the suitability of LP-WUS monitoring can be tested via explicit indications (e.g., RRC signaling, and / or MAC-CE indications and / or DCI indications). Alternatively or additionally, the WTRU can determine the RRC status based on implicit indications, for which suitability should be tested for LP-WUS monitoring. For example, the WTRU can utilize the current RRC status (e.g., the WTRU's RRC status when it receives an indication / configuration from the WTRU for determining / testing the suitability of LP-WUS monitoring) to determine / test the suitability of LP-WUS monitoring. In another example, the WTRU can determine one or more RRC statuses based on a pre-configured association between a first RRC status (e.g., the current RRC status) and a second RRC status (e.g., the RRC status for which the suitability / feasibility of LP-WUS monitoring is to be tested). For example, a WTRU can be pre-configured with two RRC state association configurations, including {first RRC state: RRC CONNECTED, second RRC state: RRC CONNECTED, RRC INACTIVE, RRC IDLE} and {first RRC state: RRC INACTIVE, second RRC state: RRC INACTIVE, RRC IDLE}. In the example configuration, the WTRU can determine the first RRC state based on the current RRC state. Based on the configured RRC state association configuration between the first and second RRC states, the WTRU can determine the set of RRC states against which to test the suitability of LP-WUS monitoring. For example, if the WTRU determines its first RRC state is RRC CONNECTED, the WTRU can use the RRC CONNECTED, RRC INACTIVE, and / or RRC IDLE states to test the suitability of LP-WUS monitoring. In another example, if the first RRC state is determined to be the RRC INACTIVE state, the WTRU can use the RRC IDLE state to test the suitability of LP-WUS monitoring.

[0147] The WTRU can determine a threshold associated with each of one or more conditions to be tested to determine / test the suitability of LP-WUS monitoring, based on the RRC status and / or LP-WUS configuration. For example, to determine the suitability of a first RRC status and / or LP-WUS configuration, the WTRU can test one or more conditions of LP-WUS monitoring associated with a first set of pre-configured thresholds (e.g., WTRU activity). In another example, to determine the suitability of a k-th RRC status and / or LP-WUS configuration, the WTRU can test one or more conditions associated with a k-th set of pre-configured thresholds (e.g., WTRU activity, location).

[0148] In the example configuration, the nth set of thresholds can be configured with thresholds related to WTRU mobility. The WTRU can measure its mobility (e.g., the WTRU measures its velocity based on position estimates at two different times) and can compare it to the WTRU mobility thresholds configured via the nth set of thresholds. For example, if the WTRU mobility > the mobility threshold configured for the nth RRC state and / or LP-WUS, the WTRU can determine that LP-WUS surveillance is not suitable for the nth RRC state and / or LP-WUS configuration. Conversely, if the WTRU mobility < the mobility threshold configured for the nth RRC state and / or LP-WUS configuration, the WTRU can determine that LP-WUS surveillance is suitable for the nth RRC state and / or LP-WUS configuration.

[0149] In the second example configuration, the nth set of thresholds can be configured with thresholds related to WTRU activity. The WTRU can measure its activity (e.g., by calculating the number of SRs transmitted within a pre-configured time window) and compare it to the WTRU activity thresholds configured via the nth set of thresholds. For example, if WTRU activity > the activity threshold configured for the nth RRC state and / or LP-WUS, the WTRU can determine that LP-WUS monitoring is not suitable for the nth RRC state and / or LP-WUS configuration. Conversely, if WTRU activity < the activity threshold configured for the nth RRC state and / or LP-WUS configuration, the WTRU can determine that LP-WUS monitoring is suitable for the nth RRC state and / or LP-WUS configuration. The WTRU can determine that LP signal monitoring is unsuitable when the mobility parameter is greater than the mobility threshold, the activity parameter is greater than the activity threshold, or the beam quality measurement is less than the beam quality threshold. The WTRU can determine that LP signal monitoring is suitable when the mobility parameter is less than the mobility threshold, the activity parameter is less than the activity threshold, or the beam quality measurement is greater than the beam quality threshold.

[0150] In the third example configuration, the nth set of thresholds can be configured with thresholds related to beam quality. The WTRU can measure the beam quality of one or more beams configured with the WTRU (e.g., by measuring the beam quality associated with BFD-RS) and can compare it with the thresholds for beam quality configured via the nth set of thresholds. For example, if the measured beam quality associated with one or more beams is greater than the beam quality threshold of the nth RRC state and / or LP-WUS configuration, the WTRU can determine that LP-WUS monitoring is suitable for the nth RRC state and / or LP-WUS configuration. For example, if the measured beam quality associated with one or more beams is less than the activity threshold of the nth RRC state and / or LP-WUS configuration, the WTRU can determine that LP-WUS monitoring is not suitable for the nth RRC state and / or LP-WUS configuration. When the mobility parameter is greater than the mobility threshold, the activity parameter is greater than the activity threshold, or the beam quality measurement is less than the beam quality threshold, the WTRU can determine that LP signal monitoring is unsuitable. When the mobility parameter is less than the mobility threshold, the activity parameter is less than the activity threshold, or the beam quality measurement is greater than the beam quality threshold, the WTRU can determine that LP signal monitoring is appropriate.

[0151] The WTRU can, for example, report the suitability of LP-WUS monitoring in one or more (e.g., each) RRC state and / or LP-WUS monitoring configurations based on suitability determined by the WTRU. For instance, the WTRU can indicate the suitability of LP-WUS monitoring using one or more (e.g., each) RRC state and / or LP-WUS monitoring configurations via PUCCH indication, MAC-CE indication, or RRC signaling (e.g., the indication is a bitmap where a bit value of 1 can indicate that the RRC state and / or LP-WUS configuration corresponding to that bit is suitable, and a bit value of 0 can indicate that the RRC state and / or LP-WUS configuration corresponding to that bit is unsuitable). In another example, the WTRU can receive from the gNB a configuration indicating the association between the RRC state and / or LP-WUS configuration (e.g., each RRC state and / or LP-WUS configuration) and a set of PRACH resources (e.g., via MAC-CE indication, RRC signaling). By transmitting one or more PRACH resources corresponding to the RRC state and / or LP-WUS configuration determined to be suitable, the WTRU can indicate the suitability of one or more RRC states and / or LP-WUS configurations. The suitability / feasibility report associated with the RRC state and / or LP-WUS configuration may also include one or more of the following. This report can indicate the conditions used to determine the WTRU's suitability for LP signal monitoring.

[0152] The WTRU may report conditions that the WTRU does not meet (e.g., WTRU mobility, location), e.g., for (e.g., each) RRC state and / or LP-WUS configuration, the WTRU determines that LP-WUS monitoring is not feasible. The WTRU may use one or more of RRC signaling, MAC-CE indication, and / or DCI indication.

[0153] The WTRU may report auxiliary information for determining LP-WUS monitoring conditions / configurations / parameters (e.g., bandwidth, SCS, modulation, coding rate, and / or etc.). The auxiliary information may include one or more of the WTRU activity level, beam quality measurements of one or more beams, LR coverage, WTRU mobility (e.g., speed of movement, direction of movement), and / or WTRU location. The gNB may use one or more of the reported auxiliary information to determine one or more of the conditions / configurations / parameters associated with LP-WUS.

[0154] The WTRU may determine the priority for each RRC state and / or LP-WUS configuration determined to be suitable. The WTRU may be configured with (e.g., additional) priority determination parameters (e.g., WTRU mobility, beam quality) and / or priority determination thresholds. For example, the WTRU may determine that LP-WUS monitoring is suitable when the WTRU is in RRC IDLE and / or RRC INACTIVE. For example, if the WTRU mobility (speed) > the preconfigured priority determination threshold for RRC IDLE, the WTRU may determine that for LP-WUS monitoring, the RRC INACTIVE state has a higher priority than the RRC IDLE state. For example, if the WTRU mobility (speed) < the preconfigured priority determination threshold for RRC IDLE, the WTRU may determine that for LP-WUS monitoring, the RRC IDLE state has a higher priority than the RRC INACTIVE state. The WTRU may indicate the priority of each determined RRC state to the gNB (e.g., via PUCCH indication, MAC-CE indication, and / or RRC signaling).

[0155] The WTRU may receive an indication and / or configuration from the gNB or the network (e.g., from the core network (CN) via non-access stratum (NAS) signaling) to start using LP-WUS monitoring, for example. The WTRU may receive an indication and / or configuration from the gNB via RRC signaling, MAC-CE indication, and / or DCI indication (e.g., via DCI scrambled with a preconfigured RNTI (e.g., a dedicated RNTI for signaling related to LP-WUS monitoring)).

[0156] The WTRU can receive an RRC release message from the gNB indicating that it is entering the RRC INACTIVE state. The release message may include an indication to monitor using LP-WUS. The WTRU can enter the RRC INACTIVE state and / or begin monitoring LP-WUS using LR.

[0157] When in RRC CONNECTED state, the WTRU can receive instructions from the gNB to use LP-WUS monitoring while in CONNECTED state. The WTRU can remain in RRC CONNECTED state and / or begin monitoring LP-WUS using LR.

[0158] The WTRU can receive NAS messages instructing it to use LP-WUS monitoring in RRC IDLE state. The WTRU can enter RRC IDLE state and / or begin monitoring LP-WUS using LR.

[0159] The WTRU can use LP-WUS monitoring in RRC status and / or LP-WUS configuration, for example, based on indications and / or configurations received from the gNB (e.g., via DCI indications, MAC-CE indications, RRC signaling) and / or the network (e.g., NAS signaling). In one example, based on one or more signals (e.g., LP-SS, LP-WUS) received via the LR, the WTRU can wake up the MR to monitor / detect / receive one or more signals / channels / indications / configurations (e.g., PDCCH, PDSCH, and / or etc.). In another example, based on one or more signals (e.g., LP-SS, LP-WUS) received via the LR, the WTRU can avoid waking up the MR. In yet another example, based on one or more signals (e.g., LP-SS, LP-WUS) received via the LR, the WTRU can skip monitoring one or more (e.g., a pre-configured or indicated number) future LP-WUS monitoring opportunities.

[0160] For example, when the WTRU is in RRC state (e.g., RRC CONNECTED, RRC IDLE, RRC INACTIVE state), the WTRU can monitor LP-SS and / or LP-WUS. Based on the reception of LP-WUS, the WTRU can monitor and / or receive one or more DL signals (e.g., PDCCH). Similarly, when the WTRU is in RRC state (e.g., RRC CONNECTED, RRC IDLE, RRC INACTIVE state), the WTRU can monitor LP-SS and / or LP-WUS. Based on the reception of LP-WUS, the WTRU can monitor and / or receive one or more paging-related signals (e.g., Paging PDCCH / DCI and / or Paging Early Indication (PEI)).

[0161] There may be beam determination for LP-WUS monitoring. The WTRU can determine one or more beams for LP-WUS reception by using a second set of BFR thresholds. It can be assumed that the MR and LR share the same RF hardware.

[0162] The WTRU can receive configurations for a first BFR resource set and / or a first set of BFR thresholds and / or a second set of thresholds (e.g., LP-WUS thresholds, BFR thresholds) for regular operation using MR, to, for example, determine the beams used for LP-WUS surveillance using LR. The first BFR resource set may include one or more of a first beam set (e.g., BFD RS and / or PDCCH surveillance beams), a first candidate beam set (e.g., BFR candidate beams), a first PRACH resource set for beam failure indication, and / or so on. The first set of BFR thresholds may include one or more of a first failure detection threshold (e.g., a first assumed PDCCH BLER threshold, a first failure detection RSRP threshold), a first new beam selection threshold, a first BFI maximum count, etc. The second set of thresholds may include one or more second failure detection thresholds (e.g., an assumed LP-WUS BLER threshold, a second assumed PDCCH BLER threshold, a second failure detection RSRP threshold), a second new beam selection threshold, a second BFI maximum count, etc.

[0163] The WTRU can receive indications from the gNB for determining the beams used for LP-WUS monitoring. For example, based on one or more beam measurements associated with a first beam set and a first set of BFR thresholds, the WTRU can determine that there is no beam failure for UL / DL communication (i.e., when using MR).

[0164] For example, based on one or more measurements associated with one or more first beam sets and a second set of thresholds, the WTRU can determine the suitability / unsuitability of the first beam set for LP-WUS surveillance using LR. For example, if the assumed PDCCH BLER of the PDCCH surveillance beam is less than the second assumed LP-WUS BLER threshold, the WTRU can determine that the PDCCH surveillance beam is suitable for LP-WUS surveillance. For example, if the assumed PDCCH BLER of the PDCCH surveillance beam is greater than the second assumed LP-WUS BLER threshold, the WTRU can determine that the PDCCH surveillance beam is unsuitable for LP-WUS surveillance. For example, if the RSRP of the BFD RS is greater than the second failure detection RSRP threshold, the WTRU can determine that the BFD RS is suitable for LP-WUS surveillance. For example, if the RSRP of the BFD RS is less than the second failure detection RSRP threshold, the WTRU can determine that the BFD RS beam is unsuitable for LP-WUS surveillance.

[0165] For example, if the WTRU determines that one or more beams in the first beam set are suitable for LP-WUS surveillance using the LR, the WTRU may indicate to the gNB at least one (e.g., all) of the identified one or more beams (e.g., transmitted via PUCCH, PUSCH / MAC-CE, or by using one or more pre-configured second PRACH resource sets). For example, if the WTRU determines that no beams in the first beam set can be used for LP-WUS surveillance (e.g., by using the LR), the WTRU may select one or more beams from the first candidate beam set for LP-WUS surveillance.

[0166] The WTRU can measure the beam quality (e.g., RSRP) of a first candidate beam set. The WTRU can determine one or more beams for LP-WUS monitoring, for example, based on one or more measurements associated with one or more first candidate beam sets and a second new beam selection threshold.

[0167] The WTRU can indicate to the gNB at least one (e.g., all) of the selected one or more beams (e.g., via PUCCH, PUSCH / MAC-CE, or by using one or more pre-configured PRACH resources (a third set). For example, if the WTRU determines that there are no beams available for LP-WUS surveillance in either the first beam set or the first candidate beam set, the WTRU can indicate to the gNB that no suitable beam was found for LP-WUS surveillance (e.g., via PUCCH, PUSCH, or by using pre-configured PRACH resources).

[0168] The WTRU can receive indications and / or configurations from the gNB and / or network that indicate and / or activate the use of LP-WUS monitoring. The WTRU can receive indications and / or configurations of a set of beams for LP-WUS monitoring. For example, the WTRU can receive an indication and / or activation after sending an indication of one or more selected or suitable beams for LP-WUS monitoring (e.g., from a first beam set or a first candidate beam set). The WTRU can receive from the gNB an indication of using LP-WUS monitoring while in the CONNECTED state, and / or receive confirmation indications (e.g., a 1-bit indication), such as for using the beams selected and indicated by the WTRU for LP-WUS monitoring. The WTRU can receive from the gNB an RRC release message indicating entry into the RRC INACTIVE state. The release message may include an indication of using LP-WUS monitoring. The WTRU can receive configurations and / or indications (e.g., in a bitmap) of a subset of beams. The subset of beams may come from beams selected and / or indicated by the WTRU for LP-WUS monitoring.

[0169] The WTRU can detect wake-up indications from the gNB using one or more of the indicated and / or configured beams and / or by monitoring LP-WUS. For example, when in LP-WUS monitoring in RRC connected state, the WTRU can use one or more of the indicated and / or configured beams to monitor LP-SS and / or LP-WUS. For example, based on LP-WUS reception, the WTRU can monitor and / or receive one or more DL signals (e.g., PDCCH). The WTRU can determine PDCCH monitoring resources (e.g., search space and / or PDCCH monitoring timing) based, for example, on the configured association between the indicated and / or configured beams and PDCCH monitoring resources. For example, when in LP-WUS monitoring in RRC IDLE or RRC INACTIVE state, the WTRU can use one or more of the indicated / configured beams to monitor LP-SS and / or LP-WUS. For example, based on indications received on LP-WUS, the WTRU can monitor and / or receive one or more paging-related signals (e.g., paging PDCCH / DCI and / or PEI).

[0170] Beam quality monitoring and / or radio link monitoring may be present. The WTRU may use / receive and / or configure one or more sets of reference signals for each BWP, for example, for monitoring and / or detecting beam failure. For example, the term q0 may be used for the beam failure detection set. This beam failure detection set may include one or more reference signals. The reference signals may be CSI-RS resource configuration indexes and / or SS / PBCH block (SSB) indexes. The reference signals included in the beam failure detection RS set may be the same as the reference signals configured / used / received for radio link monitoring (RLM).

[0171] For example, if no beam failure detection RS set is provided and / or configured for the WTRU for the BWP, the WTRU can determine the appropriate RS set. For instance, the WTRU can determine the RS signals to be included in the beam failure detection RS set for the BWP based on a periodic CSI-RS resource configuration index, which the WTRU uses to monitor the PDCCH in the corresponding CORESET as indicated by the TCI status.

[0172] The WTRU can measure reference signals included in the beam failure detection RS set and / or accordingly estimate radio link quality. The WTRU can use one or more thresholds / ranges to monitor and / or estimate radio link quality. For example, a loss-of-synchronization threshold (e.g., Q_out) and / or a synchronization threshold (e.g., Q_in) can be used. Thresholds Q_out and / or Q_in can be used to estimate the quality of the radio link and / or (one or more) corresponding beams. The terms Q_out and Q_in can be used to represent one or more attributes and parameters and their corresponding values.

[0173] The threshold Q_out can be used to determine the radio link and / or beam quality at which signal transmission may not be reliably received, for example, corresponding to the out-of-synchronization block error rate (BLER_out). Alternatively or additionally, the threshold Q_in can be used to determine the radio link and / or beam quality at which signal transmission may be reliably received, for example, corresponding to the synchronization block error rate (BLER_in). BLER_out and / or BLER_in can be explicitly determined by the gNB.

[0174] If the gNB does not explicitly determine BLER_out and / or BLER_in, they can be estimated based on one or more parameters. For example, the WTRU can use, receive, or configure PDCCH transmission parameters to perform out-of-sync and / or synchronization assessments. In the example, the number of OFDM symbols, aggregation level, the ratio of assumed PDCCH RE energy to average SSS RE energy, the ratio of assumed PDCCH DMRS energy to average SSS RE energy, BWP in the PRB quantity, subcarrier spacing, etc., can be used to determine the BLER_out and / or BLER_in thresholds.

[0175] Beam failure detection can exist. The WTRU can monitor the beam failure detection RS set in the active BWP. The WTRU can (e.g., further) estimate beam and / or radio link quality. The WTRU can report out-of-synchronization and / or synchronization status. In the example, the WTRU can measure the radio link quality (e.g., L1-RSRP) of (one or more) SSBs and / or (one or more) CSI-RSs in the corresponding beam failure detection RS set. The WTRU can (e.g., then) compare the measurements with corresponding thresholds to determine, indicate, and / or detect whether a beam failure instance (BFI) has occurred.

[0176] The WTRU may indicate, determine, and / or configure one or more Beam Failure Detection (BFD) counters. The WTRU can detect beam failures by counting BFI indications. The WTRU may indicate, determine, and / or configure one or more of BFI_Counter, BFI_Max_Count, BFD_Timer, and / or BFI_Counter. BFI_Counter can be used to count the number of BFIs, and it may, for example, be initially set to 0 and / or increment with each BFI detection. BFI_Max_Count may include the maximum value of BFI_Counter, which may, for example, trigger beam failure detection. BFD_Timer may be started on the first BFI detection. If the timer expires before BFI_Counter reaches BFI_Max_Count, the beam failure detection procedure can be stopped. The parameters described herein are non-limiting examples that may include and / or be used for beam failure detection. One or more of these parameters may be included. Other parameters may be included.

[0177] In the example, if BFI has already occurred, the WTRU starts or restarts BFD_Counter and increments BFI_Counter by 1. If BFI_Counter reaches BFI_Max_Count, the WTRU can trigger a BFD event and / or initiate a beam failure recovery (BFR) procedure.

[0178] Beam failure recovery may exist. The WTRU may determine, indicate, and / or trigger beam failure recovery, for example, based on a beam failure detection event. The WTRU may indicate, determine, and / or configure one or more of BFR_Timer, RSRP_Threshold, candidateBeamRSList, power ramp, and / or random access. BFR_Timer may be initiated with a beam failure recovery procedure. RSRP_Threshold may be used for RSRPs used in beam failure recovery. candidateBeamRSList may include a list of candidate beam reference signal indices to be monitored, measured, and / or selected during beam failure recovery. The power ramp may include parameters including power ramp step size, received preamble target power, and / or one or more of the following. Random access may include PRACH parameters including preamble index, SSB for each RACH timing, random access response window, PRACH configuration index, random access timing and SSB associated mask index, and / or one or more of the following. The above parameters are non-limiting examples of parameters that may be included in beam failure detection. One or more of those parameters may be included. Other parameters can be included.

[0179] The WTRU can use, receive, and / or configure one or more sets of reference signals for each BWP to monitor, measure, and / or select resources as beam failure recovery. For example, the term q1 can be used for a beam failure recovery set. This beam failure recovery set can include one or more reference signals. The reference signals can include one or more of the following: a CSI-RS resource configuration index, an SS / PBCH block (SSB) index, and / or so on. In the example, the reference signals included in the beam failure recovery RS set can be based on candidateBeamRSList (e.g., a portion configured as part of the BFR procedure).

[0180] The WTRU can initiate beam failure recovery based on a random access procedure. In an example, the WTRU can configure random access parameters, start the BFR_Timer, and / or apply power ramp parameters. The WTRU can monitor and / or measure one or more reference signals from the candidateBeamRSList. The WTRU can determine whether at least one SSB in the candidateBeamRSList has an SS-RSRP higher than the corresponding RSRP_Threshold. The WTRU can additionally or alternatively determine whether at least one CSI-RS has a CSI-RSRP higher than the corresponding RSRPP_Threshold of the CSI-RS in the candidateBeamRSList. The WTRU can (e.g., then) select the corresponding reference signal as a new candidate beam (NCB) and / or random access resource for the BFR procedure. For example, the term q_new can be used to present the newly selected beam and / or random access resource. The WTRU can perform a PRACH transmission in the corresponding random access resource. Alternatively or concurrently, the WTRU may perform PRACH transfers based on the periodic CSI-RS resource configuration and / or the spatial relationships with the associated SS / PBCH blocks and / or QCLs indexed as q_new (one or more).

[0181] PRACH preamble transmission can be based on contention-free PRACH transmission, which is subject to the WTRU being provided and / or configured with a preamble (e.g., an index) for PRACH transmission. PRACH preamble transmission can also be based on contention-based PRACH transmission; for example, for this purpose, the WTRU can select (e.g., randomly) a PRACH preamble (e.g., an index) from a set of available preambles (e.g., indices) for PRACH transmission.

[0182] The WTRU can identify, identify, and / or configure one or more CORESETs corresponding to random access procedures for corresponding beam failure recovery. In an example, the WTRU can monitor PDCCHs in the search space set, for example, to detect DCI formats with corresponding CRCs scrambled with radio network identifiers (e.g., C-RNTI or MCS-C-RNTI). The WTRU can determine antenna port quasi-co-address parameters that are the same as the antenna port quasi-co-address parameters associated with the index q_new for monitoring PDCCHs in the search space set and / or receiving the corresponding PDSCHs. For example, if the BFR_Timer has expired and / or the beam failure recovery procedure has not yet successfully completed, the WTRU can trigger link failure detection and / or follow the link failure recovery (LFR) procedure.

[0183] The WTRU can receive one or more configuration information sets, which may include a first set of BFR configurations and a second set of BFR configurations. The WTRU can use the first set of BFR configurations for a first operating mode and / or use the second set of BFR configurations for a second operating mode. For example, the first operating mode can be used for normal operation utilizing the MR, and / or the second operating mode can be used to determine the beam monitored by LP-WUS utilizing the LR.

[0184] In the example, the first set of BFR configuration information may include one or more parameters, timers, counters, and / or one or more first thresholds and / or maximum values, etc. For example, the first set of BFR configuration information may include a first assumed PDCCHBLER threshold, a first failure detection RSRP threshold, a first new beam selection RSRP threshold, a first BFI maximum count, and / or the like. In another example, the first set of BFR configuration information may include indications regarding one or more first beam resources. For example, first beam resources may include a first BFD RS beam set, a first PDCCH monitoring beam set, a first candidate beam set (e.g., BFR candidate beams), a first PRACH resource set for beam failure indication, and / or the like.

[0185] In the example, the second set of BFR configuration information may include one or more parameters, timers, counters, and / or one or more thresholds and / or maximum values, etc. For example, the second set of BFR configuration information may include a second assumed PDCCHBLER threshold, a second failure detection RSRP threshold, a second new beam selection RSRP threshold, a second BFI maximum count, and / or etc.

[0186] The WTRU can receive indications from the gNB regarding the determination of one or more beam resources for LP-WUS surveillance. The WTRU can use the first beam resource indicated in the first set of BFR configurations to determine the (e.g., optimal) beam for LP-WUS surveillance. In one example, the WTRU can use one or more beam resources from the first BFD RS beam resource set. In another example, the WTRU can use one or more beam resources from the first PDCCH surveillance beam resource set.

[0187] The WTRU can measure one or more parameters, for example, based on a first beam resource. The WTRU can measure RSRP based on one or more RSs received from the first BFD RS beam resource set. The WTRU can measure, for example, the (e.g., assumed) PDCCH BLER from one or more beam resources of the first PDCCH monitoring beam resource set.

[0188] The WTRU can compare the measured parameters with a first set of thresholds and / or determine that the measured parameters of the first beam resource are within acceptable ranges. In one example, the WTRU can determine that the RSRP measured based on one or more RSs received from the first BFD RS beam resource set is greater than the corresponding first failure detection RSRP threshold. In another example, the WTRU can determine that the measured assumed PDCCH BLER from one or more beam resources of the first PDCCH monitoring beam resource set is lower than the corresponding first assumed PDCCH BLER threshold. The WTRU can determine that the first beam resource is suitable for UL / DL communication when using MR, and no beam failure was detected.

[0189] The WTRU can compare parameters, for example, based on one or more measurements of a first beam, with one or more corresponding second thresholds to determine whether the first beam is suitable for LP-WUS surveillance. In one example, the WTRU can determine that the RSRP measured based on one or more RSs received from the first BFD RS beam resource set is greater than the corresponding second failure detection RSRP threshold. The WTRU can then determine that the corresponding beam resource is suitable for LP-WUS surveillance. In another example, the WTRU can determine that the RSRP measured based on one or more RSs received from the first BFD RS beam resource set is less than the corresponding second failure detection RSRP threshold. The WTRU can then determine that the corresponding beam resource is not suitable for LP-WUS surveillance.

[0190] In one example, the WTRU can determine that the measured assumed PDCCH BLER of one or more beam resources from the first PDCCH monitoring beam resource set is lower than the corresponding second assumed PDCCH BLER threshold. The WTRU can then determine that the corresponding beam resource is suitable for LP-WUS monitoring. In another example, the WTRU can determine that the measured assumed PDCCH BLER of one or more beam resources from the first PDCCH monitoring beam resource set is higher than the corresponding second assumed PDCCH BLER threshold. Thus, the WTRU can determine that the corresponding beam resource is unsuitable for LP-WUS monitoring.

[0191] The WTRU can determine one or more of the first beam resources suitable for LP-WUS surveillance using the LR. The WTRU can (e.g., to the gNB) send an indication to indicate at least one of the determined beam resources. In an example, the WTRU can send this indication as part of a CSI report via PUCCH, PUSCH, UCI, MAC-CE, and / or by using one or more (pre)configured PRACH resources (e.g., a second set).

[0192] The WTRU can determine that none of the first beam resources are suitable and none can be used for LP-WUS monitoring via LR. The WTRU can select one or more beams from the first candidate beam set. The WTRU can, for example, measure one or more parameters based on the selected beam. In an example, the WTRU can measure the RSRP based on the received RS of the selected beam. The WTRU can compare the measured parameters with one or more second thresholds. In an example, the WTRU can compare the measured RSRP with a second new beam selection RSRP threshold. For example, if the measured parameters are within acceptable ranges (e.g., the measured RSRP is above the second RSRP threshold), the WTRU can report the selected beam resource (e.g., to the gNB). In an example, the WTRU can transmit this indication as part of a CSI report via PUCCH, PUSCH, UCI, MAC-CE, and / or by transmitting using one or more (pre)configured PRACH resources (e.g., a third set).

[0193] The WTRU can determine that neither the first beam resource nor the first candidate beam resource is suitable, and none of them can be used for LP-WUS surveillance using the LR. In one example, the WTRU can determine that none of the first beam resources from the first BFD RS beam resource set is suitable for LP-WUS surveillance using the LR. In another example, the WTRU can determine that none of the first beam resources from the first PDCCH surveillance beam resource set is suitable for LP-WUS surveillance using the LR. In yet another example, the WTRU can determine that none of the first candidate beam resources is suitable for LP-WUS surveillance using the LR. Thus, the WTRU can (e.g., to the gNB) send an indication that no suitable beam resource was found for LP-WUS surveillance. The WTRU can send this indication as part of a CSI report via PUCCH, PUSCH, UCI, MAC-CE, and / or by using one or more (pre)configured PRACH resources.

[0194] Beams in the first beam resource set of the LR can be associated with beams in the beam resource set of the MR. For example, beams in the first beam resource set can be used for QCL with beams in the beam resource set of the MR. The beam resource set of the MR can be used for beam failure detection of the MR and / or detection of new candidate beams for the MR. Beams in the beam resource set of the MR can be used as source beams for beams in the first (or second) beam resource set of the LR.

[0195] LP-WUS monitoring using the determined beams may exist. The WTRU may receive configurations of one or more of the following: a first RS resource set, a second RS resource set, a first TCI state set, a second TCI state set, and / or a CSI report. The first RS resource set may include, for example, RSs associated with one or more candidate beams of the BFR. The first TCI state set may include, for example, one or more TCI states associated with one or more RS resources of the second RS resource set. The second TCI state set may include, for example, one or more TCI states associated with one or more signals / channels (e.g., PDCCH, e.g., PDSCH). The CSI report may include the configuration (e.g., periodic / aperiodic) of resources used for CSI reporting.

[0196] The WTRU can, for example, measure one or more RSs associated with a first RS resource set based on the received configuration. The WTRU can, for example, measure one or more RSs associated with a second RS resource set based on the received configuration. Alternatively or additionally, the WTRU can use one or more TCI states from a first TCI state set to measure one or more RSs associated with a second RS resource set. The WTRU can, for example, determine one or more RS quality / beam quality measurements based on the measurements of (one or more) RSs. One or more RS quality / beam quality measurements may include one or more of the following: L1-RSRP / CQI / SINR / RSSI / LOS probabilities of RSs associated with the first RS resource set and / or L1-RSRP / CQI / SINR / RSSI / LOS probabilities of RSs associated with the second RS resource set.

[0197] The WTRU can, for example, transmit indications of one or more RSs based on determined RS / beam quality values ​​(e.g., via a configured CSI-Report). The WTRU can indicate the CRI / beam ID of one or more RSs with the highest quality (e.g., highest L1-RSRP / LOS probability) among the measured RSs (e.g., all measured RSs). The WTRU can indicate the CRI / beam ID of one or more RSs with the highest quality among the measured RSs associated with a first RS resource set (e.g., all measured RSs) and / or one or more RSs with the highest quality among the measured RSs associated with a second RS resource set (e.g., all measured RSs).

[0198] The WTRU can report one or more associated RS measurements (e.g., L1-RSRP). The WTRU (e.g., when the WTRU is in a CONNECTED state, such as when the WTRU's main radio (MR) is ON) can receive, for example, connection state changes (e.g., CONNECTED to RRC INACTIVE) and / or configuration / indications for one or more RS / beams based on WTRU reports. For an RS / beam indicated by the WTRU, the WTRU can receive a 1-bit acknowledgment from the gNB. The WTRU can receive a bitmap-based indication from the gNB indicating a subset of the RS / beams indicated by the WTRU. The WTRU can receive configurations for a third set of RS resources. The WTRU can receive RRC release messages from the gNB (e.g., to indicate activation of the RRC INACTIVE / RRC IDLE state). Alternatively or additionally, the WTRU can receive RS / beam configuration / indications (e.g., 1-bit indications / bitmap-based indications).

[0199] The WTRU may attempt (e.g., determine) to detect / search / monitor LP-WUS using one or more Rx beams / Rx spatial filters associated with the RS (or Tx beam), as indicated by the gNB. The WTRU may perform beam scanning on the Rx beams associated with the RS indicated by the gNB, for example, to monitor LP-WUS and / or LP-SS.

[0200] The WTRU can monitor / attempt detection of LP-WUS and / or LP-SS in the RRC CONNECTED state. The WTRU can determine the monitoring resources for one or more DL signals (e.g., PDCCH / PDSCH) based, for example, on the reception / detection of LP-WUS and / or LP-SS. For instance, the WTRU can use TCI states from a second TCI state set (e.g., using TCI states associated with the Rx beam / Rx spatial filter used to receive / detect LP-WUS / LP-SS) to determine PDCCH monitoring resources (e.g., PDCCH search space, PDCCH monitoring timing).

[0201] The WTRU can monitor / attempt to detect LP-WUS and / or LP-SS in RRC IDLE or RRC INACTIVE states. The WTRU can, for example, monitor / search for and / or detect / receive one or more paging signals (e.g., paging PDCCH, paging DCI, PEI) based on the reception / detection of LP-WUS and / or LP-SS. For example, the WTRU can use TCI states from a second TCI state set to monitor and / or receive paging signals (e.g., using TCI states associated with the Rx beam / Rx spatial filter used to receive / detect LP-WUS / LP-SS).

Claims

1. A wireless transmit / receive unit (WTRU), comprising: Processor and memory, wherein the processor and memory are configured as follows: Configuration information is received from the network, which activates the WTRU to perform low-power (LP) signal monitoring using the WTRU's low-power radio, wherein the configuration information indicates a threshold associated with a condition, and wherein the condition is associated with LP signal monitoring; Receive an indication of the suitability of the WTRU for LP signal monitoring; The suitability of the WTRU for LP signal monitoring is determined based on a threshold associated with the conditions; and Send a report indicating the suitability of the WTRU for LP signal monitoring.

2. The WTRU according to claim 1, wherein, The processor and memory are configured to receive the configuration information via the main radio of the WTRU, receive the instruction via the main radio of the WTRU, and transmit the report via the main radio of the WTRU; as well as The processor and memory are configured as follows: In response to receiving configuration information from the network to activate the WTRU to perform LP signal monitoring, low-power signals are monitored via the low-power radio of the WTRU.

3. The WTRU according to claim 1, wherein, The conditions include any one or more of the following: beam quality of the beam associated with the main radio of the WTRU, beam quality of the beam associated with the low-power radio of the WTRU, the activity of the WTRU, the mobility of the WTRU, the location of the WTRU, the coverage area of ​​the low-power radio of the WTRU, or the coverage gap between the low-power radio of the WTRU and the main radio of the WTRU.

4. The WTRU according to claim 1, wherein, The indication includes a Radio Resource Control (RRC) status for the WTRU to determine its suitability for LP signal monitoring.

5. The WTRU according to claim 1, wherein, The configuration information indicates multiple thresholds and multiple conditions, wherein each of the multiple thresholds is associated with a Radio Resource Control (RRC) state or a periodicity of a low-power signal, and wherein the report indicates the suitability of the WTRU for LP signal monitoring for each RRC state or periodicity of the low-power signal.

6. The WTRU according to claim 1, wherein, The processor and memory are configured as follows: Receive a second instruction to perform LP signal monitoring periodically in a first Radio Resource Control (RRC) state or with a first low-power signal; and According to the second instruction, the low-power radio of the WTRU is used to monitor the LP signal.

7. The WTRU according to claim 1, wherein, The processor and memory are configured as follows: When the mobility parameter is greater than the mobility threshold, the activity parameter is greater than the activity threshold, or the beam quality measurement is less than the beam quality threshold, it is determined that LP signal monitoring is not suitable.

8. The WTRU according to claim 1, wherein, The processor and memory are configured as follows: When the mobility parameter is less than the mobility threshold, the activity parameter is less than the activity threshold, or the beam quality measurement is greater than the beam quality threshold, it is determined that LP signal monitoring is appropriate.

9. The WTRU according to claim 1, wherein, The report indicates the conditions used to determine the suitability of the WTRU for LP signal monitoring.

10. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: Configuration information is received from the network, which activates the WTRU to perform low-power (LP) signal monitoring using the WTRU's low-power radio, wherein the configuration information indicates a threshold associated with a condition, and wherein the condition is associated with LP signal monitoring; Receive an indication of the suitability of the WTRU for LP signal monitoring; The suitability of the WTRU for LP signal monitoring is determined based on a threshold associated with the conditions; and Send a report indicating the suitability of the WTRU for LP signal monitoring.

11. The method of claim 10, further comprising: The configuration information is received via the main radio of the WTRU, the instruction is received via the main radio of the WTRU, and the report is transmitted via the main radio of the WTRU. as well as Further includes: In response to receiving configuration information from the network to activate the WTRU to perform LP signal monitoring, low-power signals are monitored via the low-power radio of the WTRU.

12. The method according to claim 11, wherein, The conditions include any one or more of the following: beam quality of the beam associated with the main radio of the WTRU, beam quality of the beam associated with the low-power radio of the WTRU, the activity of the WTRU, the mobility of the WTRU, the location of the WTRU, the coverage area of ​​the low-power radio of the WTRU, or the coverage gap between the low-power radio of the WTRU and the main radio of the WTRU.

13. The method according to claim 11, wherein, The indication includes a Radio Resource Control (RRC) status for the WTRU to determine its suitability for LP signal monitoring.

14. The method according to claim 11, wherein, The configuration information indicates multiple thresholds and multiple conditions, wherein each of the multiple thresholds is associated with a radio resource control (RRC) status or periodicity of a low-power signal, and wherein the report indicates the suitability of the WTRU for monitoring the LP signal for each RRC status or periodicity of the low-power signal.

15. The method of claim 11, further comprising: Receive a second instruction to perform LP signal monitoring in a first Radio Resource Control (RRC) state or periodically with a first low-power signal; as well as According to the second instruction, the low-power radio of the WTRU is used to monitor the LP signal.

16. The method of claim 11, further comprising: When the mobility parameter is greater than the mobility threshold, the activity parameter is greater than the activity threshold, or the beam quality measurement is less than the beam quality threshold, it is determined that LP signal monitoring is not suitable.

17. The method of claim 11, further comprising: When the mobility parameter is less than the mobility threshold, the activity parameter is less than the activity threshold, or the beam quality measurement is greater than the beam quality threshold, it is determined that LP signal monitoring is appropriate.

18. The method according to claim 11, wherein, The report indicates the conditions used to determine the suitability of the WTRU for LP signal monitoring.

19. A wireless transmit / receive unit (WTRU), comprising: Processor and memory, wherein the processor and memory are configured as follows: Configuration information is received from the network, which activates the WTRU to perform low-power (LP) signal monitoring using the WTRU's low-power radio, wherein the configuration information indicates a threshold associated with a condition, and wherein the condition is associated with LP signal monitoring; The suitability of the WTRU for LP signal monitoring is determined based on the WTRU's state and a threshold associated with the condition; and Send a report indicating the suitability of the WTRU for LP signal monitoring.

20. The WTRU of claim 19, wherein, The state of the WTRU is either connected, idle, or inactive.

Images