Determining exit conditions for LP-WUS monitoring

Abstract

A WTRU monitors one or more exit conditions based on identified missed signals (e.g., low-power wake up signal (LP-WUS) and / or LP-synchronization signal (LP-SS). Based on the monitored exit conditions, the WTRU determines to exit or continue with LP signal monitoring. One WTRU method includes receiving configuration information including a set of tag IDs, a set of sequences and association between sequences and tag IDs and one or more low-power (LP) monitoring exit conditions. The WTRU receives an indication to monitor for LP-wake up signals (WUS) and / or LP-synchronization signals (SS) associated with the configured tag IDs or sequences and receives a plurality of LP-WUSs and / or LP-SSs for monitoring. The WTRU determines, based on received and expected tag IDs or sequences, one or more missed LP-WUS or LP-SS signals and evaluates one or more LP monitoring exit conditions based on the missed LP-WUS or LP-SS and the configured LP monitoring exit conditions.

Description

DETERMINING EXIT CONDITIONS FOR LP-WUS MONITORINGCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 553,419, filed February 14, 2024, the contents of which are incorporated herein by reference.BACKGROUND

[0002] A mobile device such as a user equipment (UE), interchangeably referred to as a wireless transmit receive unit (WTRU), may monitor and receive a wake-up signal (WUS) via a first radio (e.g., a low-power or ultra-low power radio). The WUS may be called a low- power WUS (LP-WUS) and / or synchronization signal (LP-SS). The low-power radio (LR) or low power wake-up radio (LP-WUR) may receive a WUS (e.g., an LP-WUS), to trigger the WTRU to wake-up or use a second radio of the WTRU (e.g., the WTRU’s main radio (MR)) for data and / or control signal transmission and / or reception. This framework has the potential to reduce the power consumption of wireless devices.

[0003] LP-WUS / LP-WUR for new radio (NR) is focused on supporting a deep sleep state for the MR while the WTRU is in radio resource control (RRC) IDLE or RRC INACTIVE states (referred to as IDLE / INACTIVE mode LP-WUS monitoring) and supports the WTRU skipping monitoring the physical downlink control channel (PDCCH) while in RRC CONNECTED state (referred to as CONNECTED mode LP-WUS monitoring).

[0004] Monitoring exit conditions may be important for LP-WUS. If exit condition monitoring is not supported, the WTRU may continue to depend on receiving LP-WUS for a wake-up indication (e.g., indication for monitor paging signals via the main radio (MR), to PRACH for initial access via MR) while the reliability of LP-WUS is not sufficient. This can lead to additional latency and higher power consumption. Improved devices and methods to determine to exit LP-WUS monitoring are needed.SUMMARY

[0005] According to one aspect, a WTRU monitors one or more low-power mode exit conditions based on identified missed low power (LP) signals (e.g., low-power wake up signal (LP-WUS), low-power synchronization signal (LP-SS). Based on the monitored exit conditions and identified missed LP signals, the WTRU determines to exit monitoring LP signals or continue with LP signal monitoring.

[0006] In one example, a WTRU / method for the WTRU may include receiving configuration information indicating a set of tag IDs of LP signals, a pattern associated with sequential reception of the LP signals and one or more LP signal monitoring exit conditions. The WTRU may identify one or more missed LP signals based on a tag ID of each received LP signal and the pattern. Next, the WTRU may evaluate the one or more LP signal monitoring exit conditions using the identified missed LP signals and determine to exit LP signal monitoring when one or more of the evaluated LP signal monitoring exit conditions have been met.

[0007] In exiting LP signal monitoring, the WTRU may activate its main radio (MR) and report to a network, indication of one or more of: a number of, and which exit conditions were met; the identified missed and / or consecutively missed LP signals, or a value of a timer during the consecutively missed LP signals. In examples, LP signal monitoring exit condition may include determining that a missed detection rate (MDR) of LP signals is greater than a respective configured threshold or determining that a number of consecutively missed LP signals is greater than a configured threshold. Another example exit condition is when a missed LP signal counter exceeds a respective configured threshold.

[0008] In certain aspects, the pattern used to detect missed LP signals is based on an order of tag IDs associated with the anticipated sequential reception of the LP signals. In other aspects, the pattern is based on an order of sequences associated with tag IDs of the sequential reception of the LP signals. In one example, each sequence of the order of sequences is based on an orthogonal frequency division multiplexing (OFDM) sequence overlaid on an on-off keying (OOK)- based LP signal. In another example, each sequence is based on a sequence used to scramble at least part of a corresponding LP signal. In various aspects, the LP signals may be low power wake-up signals (LP-WUSs) and / or low power synchronization signals (LP-SSs).. Additional embodiments are disclosed.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

[0014] FIG. 2 is a block diagram showing a simplified receiver architecture of a wireless transmit receive unit (WTRU) utilizing a low-power wake-up receiver (LR) that receives a low-power wake-up signal (LP-WUS) to wake up the WTRU main radio (MR);

[0015] FIG. 3 is a flow diagram showing an example method for a WTRU to monitor for exit conditions of a LP state / mode according to one example embodiment;

[0016] FIG. 4 is a timing chart showing a method of identifying missed LP-WUS using a tag ID received with the LP-WUS in an example embodiment; and

[0017] FIG. 5 is a timing chart showing a method of identifying missed low-power synchronization signals (LP-SSs) based on configured sequences and associated tag IDs of received LP-SSs according to an example embodiment.DETAILED DESCRIPTION

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

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

[0020] The communications systems 100 may also include a base station 1 14a and / or a base station 1 14b. Each of the base stations 1 14a, 1 14b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or the other networks 1 12. By way of example, the base stations 1 14a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 1 14a, 1 14b may include any number of interconnected base stations and / or network elements.

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

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

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

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

[0025] In an embodiment, the base station 1 14a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 1 16 using NR.

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

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

[0028] The base station 1 14b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 1 14b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 1 10. Thus, the base station 1 14b may not be required to access the Internet 1 10 via the ON 106.

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

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

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

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

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

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

[0035] Although the transmit / receive element 122 is depicted in FIG. 1 B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 1 16.

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

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

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

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

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

[0041] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (DL) (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 1 18). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., fortransmission) orthe DL (e.g., for reception)).

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

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

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

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

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

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

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

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

[0050] Although the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0051] In representative embodiments, the other network 1 12 may be a WLAN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0072] Referring to FIG. 2, an example architecture 200 of a WTRU utilizing a low-power wake-up receiver is shown. The WTRU may monitor and receive a wake-up signal (WUS) via a first radio 205 (e.g., a low-power or ultra-low power radio). The WUS may be called a low-power WUS (LP-WUS). The first radio 205 may be called a low-power radio (LR) or a low power wake-up radio (LP-WUR). Receiving a WUS (e.g., an LP-WUS), for example via the LR, may trigger a wake-up or usage of a second radio 210 of the WTRU (e.g., the WTRU’s main radio (MR)) for data and / or control signal transmission and / or reception, (see Figure 1-1). This has the potential to reduce the power consumption of wireless devices.

[0073] A new radio (NR) Rel-19 work item on LP-WUS / LP-WUR is focused on supporting a deep sleep state for the main radio (MR) while the WTRU is in RRC IDLE or RRC INACTIVE states (referred to as IDLE / INACTIVE mode LP-WUS monitoring) and supporting the WTRU to skip monitoring PDCCH while in RRC CONNECTED state (referred to as CONNECTED mode LP-WUS monitoring).

[0074] The Rel-19 effort is expected to support the following features / functionalities for IDLE / INACTIVE mode LP-WUS monitoring: (1) Use of LP-WUS reception to trigger pagingmonitoring; (2) Sub-grouping (e.g., LP-WUS sub-grouping indication); and / or (3) Entry / exit condition(s) for LP-WUS monitoring.

[0075] Monitoring exit conditions may be important for LP-WUS monitoring. If exit condition monitoring is not supported, the WTRU may continue to depend on LP-WUS for receiving a wake-up indication (e.g., indication for monitoring paging signals via the main radio (MR), to PRACH for initial access via the MR) while the reliability of LP-WUS is not sufficient. This can lead to additional latency, and higher power consumption. In the disclosed embodiments, it may be addressed how a WTRU determines to exit LP-WUS monitoring, interchangeably referred to as LP signal monitoring. An LP signal may refer to one of, or collectively as, an LP-WUS and / or LP-SS.

[0076] Hereinafter, a “signal” may be interchangeably used with one or more of following, but still consistent with the disclosed embodiments: Sounding reference signal (SRS), channel state information - reference signal (CSI-RS), demodulation reference signal (DM- RS), phase tracking reference signal (PT-RS) and / or synchronization signal block (SSB).

[0077] As used herein, a “channel” may be interchangeably used with one or more of following, but still consistent with the disclosed embodiments: Physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), physical random access channel (PRACH), etc.

[0078] Hereinafter, a signal, channel, and message (e.g., as in DL or UL signal, channel, and message) may be used interchangeably, but remain consistent with the disclosed embodiments. Reference signal (RS) may be interchangeably used with one or more of RS resource, RS resource set, RS port and / or RS port group. RS may also be interchangeably used with one or more of synchronization signal block (SSB), CSI-RS, SRS, and DM-RS, TRS, PRS, and PTRS. The terms time instance, slot, symbol, and subframe may be used interchangeably. The terms SSB, SS / PBCH block, PSS, SSS, PBCH, and MIB may be used interchangeably for purposes of the disclosed embodiments. LP-WUS monitoring may refer to monitoring and / or receiving and / or decoding and / or detecting and / or attempting to receive one or more LP signals (e.g., via a low-power radio (LR)). Exiting LP-WUS monitoring may refer to a WTRU stopping / pausing of monitoring and / or receiving and / or decoding and / or detecting and / or stop attempting to receive one or more or all LP signals.

[0079] Embodiments are disclosed for monitoring for exit conditions by identifying missed LP signals based on indicated sequential order of transmitted / received signals. These embodiments relate to, for example, when a WTRU monitors one or more exit conditionsbased on identified missed signals (e.g., LP-WUS and / or LP-SS). Based on the monitored exit conditions, the WTRU determines whether to exit monitoring LP-WUS or whether to continue with LP-WUS monitoring.

[0080] In one embodiment, a WTRU monitors one or more LP-WUS exit conditions based on identified missed LP signals (e.g., LP-WUS and / or LP-SS). Based on the monitored exit conditions, the WTRU determines to exit monitoring LP signals or continue with LP signal monitoring.

[0081] In various embodiments, a WTRU monitors one or more low-power mode exit conditions based on identified missed low power (LP) signals (e.g., low-power wake up signal (LP-WUS), low-power synchronization signal (LP-SS). Based on the monitored exit conditions, the WTRU determines to exit monitoring LP signals or continue with LP signal monitoring.

[0082] In one example, a WTRU / method for the WTRU may include receiving configuration information indicating a set of tag IDs of LP signals, a pattern associated with anticipated sequential reception of the LP signals, and one or more LP signal monitoring exit conditions. The WTRU may identify one or more missed LP signals based on a tag ID of each received LP signal and the pattern. Next, the WTRU may evaluate the one or more LP signal monitoring exit conditions using the identified missed LP signals and determine to exit LP signal monitoring when one or more of the evaluated LP signal monitoring exit conditions have been met.

[0083] In exiting LP signal monitoring, the WTRU may activate its main radio (MR) and report to a network, indication of one or more of: a number of, and which exit conditions were met; the identified missed and / or consecutively missed LP signals, or a value of a timer during the consecutively missed LP signals. In examples, LP signal monitoring exit condition may include determining that a missed detection rate (MDR) of LP signals is greater than a respective configured threshold or determining that a number of consecutively missed LP signals is greaterthan a respective configured threshold. Another example exit condition is when a missed LP signal counter exceeds a respective configured threshold.

[0084] In certain aspects, the pattern used to detect missed LP signals is based on an order of tag IDs associated with the anticipated sequential reception of the LP signals. In other aspects, the pattern is based on an order of sequences associated with tag IDs of the anticipated sequential reception of the LP signals. In one example, each sequence of the order of sequences is based on an orthogonal frequency division multiplexing (OFDM) sequence overlaid on an on-off keying (OOK)- based LP signal. In another example, eachsequence is based on a sequence used for scramble at least part of a corresponding LP signal. In various aspects, the LP signals may be low power wake-up signals (LP-WUSs) and / or low power synchronization signals (LP-SSs)..

[0085] Referring to FIG. 3 an example method 300 for WTRU monitoring of WUS exit conditions is shown. Initially, a WTRU may receive 305 configurations / indications (e.g., via radio resource control (RRC) signaling, system information (SI), RRC release message) including one or more of: (1) Tag information including a set of tag IDs, e.g., {00, 01 , 10, 11 } and tag ID assignment pattern (e.g., a set of configured tag IDs are repeated, e.g., 00, 01 , 10, 1 1 , 00, 01 , ...), a set of sequences and an association between sequences and tag IDs; and (2) One or more exit conditions (e.g., mis-detection rate (MDR) of LP-WUS or LP- SS > a threshold, number of consecutively missed LP-WUSs or LP-SSs > a threshold, counter (e.g., ‘missed-signals counter’ that counts the number of missed LP-WUSs or LP- SSs against a timer > a threshold) and the thresholds of the one or more exit conditions.

[0086] Next, the WTRU receives 310 an indication to monitor for LP signals, e.g., LP- WUS and / or LP-SS (e.g., while in RRC IDLE and / or INACTIVE states) and the WTRU monitors 315 LP signals as indicated using its LP radio. Based on one or more of the received and expected tags, sequences, or tag IDs, of successfully received LP-WUS(s) and / or LP-SS(s), the WTRU may identify 320 one or more missed LP-WUSs and / or LP- SSs. For example, the WTRU determines a tag ID based on the received signals (e.g., LP- WUS, LP-SS). In one example, a tag ID is associated with a sequence of LP-WUS and / or LP-SS (e.g., an overlaid orthogonal frequency division multiplexing (OFDM) sequence or on-off keying (OOK) signal). In one example, a tag ID is associated with a time resource index (symbol, slot, time offset (e.g., with respect to a paging occasion (PO)), frequency offset).

[0087] In an example, when a LP-WUS or LP-SS is received, based on its tag ID (tag_new), and the tag ID of the last received LP-WUS or LP-SS (tag_old), the WTRU may identify one or more missed LP-WUSs or LP-SSs. In one example, if the WTRU determines that tag_new A next tag (tag_next) in the tag ID assignment pattern, with respect to the last received tag_old, the WTRU determines that one or more LP-WUSs or LP-SSs are missed. The WTRU determines the number of missed LP-WUSs or LP-SSs based on the minimum number of tags configured between tag_new and tag_old in the tag ID assignment pattern / LP exit conditions. On the other hand, if the WTRU determines that tag_new = tag_next, the WTRU determines that no LP-WUS or LP-SS were missed and tag_new becomes tag_old, and so on.

[0088] Next, when a WTRU identifies 320 one or more missed LP-WUSs or LP-SSs, the WTRU may evaluate 325 one or more exit conditions and corresponding threshold.In various examples, the WTRU evaluation of LP monitoring exit conditions may be use one or a combination of example items (i)-(iii) below:

[0089] (i) The WTRU determines a missed detection rate (MDR) of LP-WUS and / or LP-SS (e.g., number of missed LP-WUSs or LP-SSs within a configured time window-? (number of detected and missed LP-WUSs or LP-SSs within the time window));

[0090] (ii) The WTRU determines the number of consecutively missed LP-WUSs and / or LP-SSs (e.g., number of LP-WUSs or LP-SSs identified to be missed by the WTRU); and / or

[0091] (iii) The WTRU updates a ‘missed-signal counter’ based on the number of LP- WUS or LP-SS identified to be missed by the WTRU;

[0092] Based on the evaluated one or more exit conditions at step 325, if 330, the evaluated exit conditions meet configured thresholds, the WTRU determines 335 to exit monitoring LP signals. Alternatively, the WTRU may continue monitoring 315 LP signals.

[0093] In certain examples, the WTRU may determine to exit monitoring LP signals based on one or more of the following exit conditions being met:

[0094] (i) if the WTRU determines that the MDR of LP-WUS and / or LP-SS > a configured threshold;

[0095] (ii) if the WTRU determines that the number of consecutively missed LP-WUSs and / or LP-SS > a threshold; and / or

[0096] (iii) if the WTRU determines a ‘missed-signals counter’ exceeds a configured threshold.

[0097] If the WTRU determines to exit monitoring LP-WUS based on one or more evaluated exit conditions, the WTRU turns on 335 its main radio (MR) and receives one or more DL signals / channels (e.g., permanent equipment identifier (PEI), paging PDCCH, paging PDSCH, SI indicated via paging) and / or transmits one or more UL signals / channels (e.g., random access (RA) Msg1 , MsgA, Msg3).

[0098] In various embodiments, the WTRU may then report 340 to the network, e.g., a gNB / core network (CN) the one or more exit conditions met, and / or the evaluated exit conditions. For example, the WTRU reports the MDR of LP-WUS and / or MDR of LP-SS, and / or number of consecutively missed LP signals / types, and / or a value of the timer when ‘missed signal counter’ exceeds the threshold. In another example, the WTRU sends the report using resources preconfigured for a PUSCH resource (e.g., via a configured grant resource for small data transmission (SDT)). In another example, the WTRU indicates / reports the exit conditions met via a preconfigured physical random access channel (PRACH) resource. In one example, the WTRU sends the report / indication after receiving a page (e.g., the WTRU physical random access channel (PRACH) forconnection request, e.g., report MDR via Msg3, MsgA or later messages). In other examples, the WTRU determines a method and / or resources to report / indication based on the exit conditions met at step 330.

[0099] Examples of a WTRU receiving configurations / indications are disclosed. In one example, a WTRU may receive one or more of the following configurations (e.g., via RRC signaling, SI, RRC release message, paging message (e.g., paging PDSCH, paging PDCCH)): (i) A set of tag IDs and corresponding tag ID assignment patterns; (ii) a 1st set of sequences and association between the 1st set of sequences and tag IDs; (iii) a 2nd set of sequences and sequence assignment pattern and / or (iv) one or more exit conditions and corresponding thresholds. Examples are discussed below.

[0100] In an example configuration of a set of tag IDs and tag ID assignment pattern, the WTRU may receive a set of tag IDs (e.g., 4 tag IDs; 1st tag ID, 2nd tag ID, 3rd tag ID, 4th tag ID (e.g., represented as {00, 01 , 10, 1 1})). In one example, the WTRU may also receive configuration information for a tag ID assignment pattern associated with the configured set of tag IDs. In another example, the WTRU may determine a tag ID assignment pattern. For example, the WTRU may determine a tag ID assignment by sequentially repeating the set of configured tag IDs, e.g., 00, 01 , 10, 1 1 , 00, 01 , 10, 1 1 , ...).

[0101] A 1st set of sequences and association between the 1 st set of sequences and tag IDs may be configured / determined. For example, the WTRU may receive a configuration for a 1stparent sequence (e.g., a Zadoff-Chu sequence) from a base station (e.g., via RRC signaling, SI, RRC release message, or a paging message). The WTRU may determine a 1stset of sequences by cyclically shifting the 1stparent sequence (e.g., 1stseq. = parent sequence, 2ndseq. = sequence associated with 1 cyclic shift, 3rd seq. = sequence associated with 2 cyclic shifts, 4thseq. = sequence associated with 3 cyclic shifts, etc.). Each sequence in the 1stset of sequences may be associated with a tag ID (e.g., 1sttag ID, 2ndtag ID, ... , Nth tag ID, where N is the total number of tags IDs). For example, a kth sequence generated by (k-1) cyclic shifts of the parent sequence may associate with ((k mod N) + 1 )th tag ID, where k = 0, 1 , 2, 3,... For example, the WTRU may receive a 1stset of IDs (e.g., a set of IDs to initialize a scrambling sequence generator) and a 1stparent sequence (e.g., via RRC signaling, SI, RRC release message, a paging message) is used by the WTRU to generate a 1stset of sequences. In an example, the WTRU may generate a 1stset of sequences by scrambling the 1stparent sequence based on the scrambling IDs (e.g., via scrambling sequence generator). Each tag ID (e.g., 1st, 2nd, 3rd, and 4thtag IDs) may be associated with a subset of the 1stset of sequences (1st, 2nd, 3rd, and 4thsubset of sequences). In an example, scrambling IDs may be divided into subsets (e.g., 1st, 2nd, 3rd, and 4thsubsets of IDs) and the sequences generated using a kth subset of IDs mayassociate with a kth tag ID (e.g., k e {1, 2, 3, 4}). In one example, the WTRU may receive a 1stset of seeds to generate a 1stset of sequences (e.g., using a configured sequence generator which accepts a seed as one of its inputs) (e.g., via RRC signaling, SI, RRC release message, a paging message). Each sequence generated may be associated with a tag ID (e.g., 1st’ 2nd, 3rd, and 4thtag IDs). For example, 1stset of seeds may be divided into subsets (e.g., 1st, 2nd, 3rd, and 4thsubset of seeds), and sequences generated using a kth subset of seeds may associate with a kth tag ID (e.g., k G {1, 2, 3, 4}).

[0102] According to some embodiments, a 2nd set of sequences (e.g., 1 st seq, 2nd seq, 3rd seq, .... M th seq, where M is an integer) may be included with a sequence assignment. For example, the WTRU may receive a configuration for a 2nd parent sequence (e.g., Zadoff-Chu sequence) and set of cyclic shifts (e.g., 1 st cyclic shift, 2nd cyclic shift, 3rd cyclic shift) (e.g., via RRC signaling, SI, RRC release message, a paging message). The WTRU may determine a 2nd set of sequences by cyclically shifting the parent sequence (e.g., 1 st seq = parent sequence, 2nd seq = sequence associated with 1 st cyclic shift, 3rd seq = sequence associated with 2nd cyclic shift, 4th seq = sequence associated with 3rd cyclic shift).

[0103] In various examples, the WTRU may receive a configuration for a sequence assignment (e.g., 1st seq, 2nd seq, 3rd seq, 4th seq, 1st seq, 2nd seq, 3rd seq, 4th seq, ...) orto determine a sequence assignment (e.g., listing sequences by ordering the 2nd set of sequences based on associated number of cyclic shifts and repeating the ordered list). For example, the WTRU may receive a 2nd set of IDs (e.g., set of IDs to initialize a scrambling sequence generator) and a 2nd parent sequence (e.g., via RRC signaling, SI, RRC release message, a paging message) to generate a 2nd set of sequences. In an example, the WTRU may generate the 2nd set of sequences (e.g., 1 st seq, 2nd seq, 3rd se., 4th seq) by scrambling the parent sequence based on the scrambling IDs (e.g., by using the scrambling sequence generator). The WTRU may receive a configuration for a sequence assignment (e.g., 1 st seq, 2nd seq, 3rd seq, 4th seq, 1st seq, 2nd seq, 3rd seq, 4th seq, ...) or determine a sequence assignment (e.g., listing sequences by ordering the 2nd set of sequences based on scrambling IDs and repeating the ordered list). For example, the WTRU may receive a 2nd set of seeds to generate a 2nd set of sequences (e.g., using a 2nd configured sequence generator which accepts a seed as one of its inputs) (e.g., via RRC signaling, SI, RRC release message, a paging message). For example, the WTRU may generate the 2nd set of sequences (e.g., 1st seq, 2nd seq, 3rd seq, 4th seq) by using the seeds received (e.g., by using sequence generator). The WTRU may receive a configuration for a sequence assignment (e.g., 1 st seq, 2nd seq, 3rd seq, 4th seq, 1st seq, 2nd seq, 3rd seq, 4th seq, ...) or determine a sequence assignment (e.g., listingsequences by ordering the 2nd set of sequences based on index associated with the seed and repeating the ordered list).

[0104] One or more LP signal monitoring exit conditions and thresholds for use (e.g., a MDR threshold, a threshold on consecutive LP signals, a maximum value for missed- detection counter, a threshold on detection rate (DR), a threshold on number of missed LP signals) associated with each exit condition may be configured. For example, the WTRU may receive a configuration for one or more of the example exit conditions (1)-(5) below.

[0105] (1) The mis-detection rate (MDR) of LP-WUS and / or LP-SS > a MDR threshold;

[0106] (2) A number of consecutively missed LP signals, e.g., LP-WUSs and / or LP-SSs> a threshold on consecutive missed LP signals;

[0107] (3) A Counter (e.g., ‘missed-signals counter’) that counts the number of missedLP-WUSs and / or LP-SSs against a timer (e.g., ‘timer for missed-signal counter”) > a maximum value for the missed-signal counter;

[0108] (4) A detection rate (DR) of LP-WUS and / or LP-SS < a threshold on DR; and / or

[0109] (5) A number of missed LP-WUSs and / or LP-SSs within a configured time window (e.g., a moving time window) > a threshold on number of missed LP signals.

[0110] In certain example embodiments, a configuration for exiting LP condition monitoring. In various embodiments, the WTRU may receive an indication / configuration (e.g., via RRC signaling, RRC release message, downlink control information (DCI) indication, medium access control (MAC)-control element (CE) indication, paging signals, SI, RRC release message) to monitor for LP-WUS and / or LP-SS while in a configured / indicated / determined RRC state (e.g., RRC IDLE and / or INACTIVE states, RRC connected). The WTRU may place the main radio (MR) in a sleep state (e.g., deep sleep state) associated with LP-WUS monitoring mode (e.g., WTRU places its MR in a deep sleep state if the WTRU is configured to perform RRC INACTIVE / IDLE mode LP-WUS monitoring) and turn on its low-power radio (LR) for LP signal (e.g., LP-WUS, LP-SS) monitoring.

[0111] Examples of identifying one or more missed LP signals using tag IDs are disclosed. The WTRU may identify one or more missed LP signals (e.g., LP-WUS, LP-SS) based on received and expected tag IDs, and / or sequences (e.g., 1 st set of sequence), and / or tag IDs. The WTRU may determine received and expected tag IDS, and / or sequences, and / or IDs based on the successfully received LP signals (e.g., the WTRU may determine the success or failure of receiving a LP signal via detection of a valid sequence, and / or CRC check and / or energy detection). To this end, the WTRU may use one or combination of the following examples.

[0112] In one example, the WTRU may determine a tag ID associated with a LP signal based on one or more successfully received LP signals (e.g., LP-WUS, LP-SS). In an example configuration, the WTRU may receive tag IDs associated with a sequence of each LP-WUS and / or LP-SS. For example, the WTRU may receive a tag ID in an overlaid OFDM sequence on an OOK based LP-WUS or LP-SS (e.g., the overlaid OFDM sequence is associated with a tag ID out of configured set of tag IDs). In another example configuration, the WTRU may receive a tag ID which is associated with a time and / or frequency resource index (e.g., symbol, slot, time offset (e.g., w.r.t. PO), frequency offset). For example, the WTRU may receive LP signals of different tag IDs on different symbols and / or slot and / or with different time offsets compared to PO, and / or with different frequency offsets compared to a reference frequency. Based on the symbol and / or slot and / or time offset and / or frequency offset, the WTRU may determine the tag ID associated with the received LP signal. In another example configuration, the WTRU may receive a tag ID in the payload of LP-WUS or LP-SS (e.g., OOK based LP-WUS or LP-SS).

[0113] In one embodiment, when the WTRU receives a LP signal (referred to as a new LP signal) the WTRU may identify one or more missed LP signals (e.g., LP-WUSs or LP- SSs) based on the tag ID (referred to as tag_new) received in the new LP signal and tag ID (referred to as tag_old) received in a previously received LP signal (e.g., the LP signal received immediately prior to the new LP signal).

[0114] In one example configuration, if the WTRU determines that tag_new next tag (referred to as tag_next) in the tag ID assignment w.r.t. tag_old, the WTRU may determine that one or more LP signals (e.g., LP-WUSs or LP-SSs) are missed. The WTRU may determine the number of missed LP signals (LP-WUSs or LP-SSs) based on the minimum number of tags configured between tag_new and tag_old in the tag ID assignment. Referring to the example shown in FIG. 4, if the tag ID assignment is {00, 01 , 10, 11 , 00, 01 , 10, 1 1 , ...}, tag_new = 01 and tag_old = 10, the WTRU may determine that 2 LP-WUSs or LP-SSs are missed based on that minimum 2 tag IDs, i.e., 1 1 , and 00, that are listed between tag IDs 10 (i.e., tag_old) and 01 (i.e., tag_new) in the tag ID assignment. If the WTRU determines that tag_new = tag_next, the WTRU may determine that none of the LP-WUS or LP-SS is missed.

[0115] WTRU identifying one or more missed signals using sequences. In certain embodiments, the WTRU may identify one or more missed LP signals (e.g., LP-WUS, LP- SS) based on received and expected sequences (e.g., a sequence out of the 2nd set of sequence) and the configured / determined sequence assignment. The WTRU may determine received and expected sequences (e.g., out of 2nd sequences) based on the successful received LP signals (e.g., the WTRU may determine the success or failure ofreceiving a LP signal via detection of a valid sequence, and / or CRC check and / or energy detection). To this end, the WTRU may use one or combination of the following solutions.

[0116] In one example, the WTRU may determine a sequence (e.g., a sequence out of the 2nd set of sequences) associated with a LP signal based on one or more successfully received LP signals (e.g., LP-WUS, LP-SS). In an example configuration, the WTRU may receive a sequence in a LP signal based on the sequence used for scrambling at least a part of the LP signal. In an example configuration, the WTRU may receive a sequence in each LP-WUS and / or LP-SS. For example, the WTRU may receive an overlaid OFDM sequence on an OOK based LP-WUS or LP-SS.

[0117] When the WTRU receives a LP signal (new LP signal) the WTRU may identify one or more missed LP signals (e.g., LP-WUSs or LP-SSs) based on the received sequence (seq_new) received in the new LP signal and a sequence (referred to as seq_old) received in a previously received LP signal (e.g., the LP signal received immediately prior to new LP signal).

[0118] If the WTRU determines that seq_new =# next sequence (referred to as seq_next) in the sequence assignment w.r.t. seq_old, the WTRU may determine that one or more LP- WUSs or LP-SSs are missed. The WTRU may determine the number of missed LP-WUSs or LP-SSs based on the minimum number of sequences configured between two sequences seq_new and seq_old in the sequence assignment. In an example shown in FIG. 5, if sequence assignment is {seqO, seq1 , seq2, seq3, seqO, seq1 , ...}, seq_new = seq3 and seq_old = seq1 , then the WTRU may determine that 1 LP-WUSs or LP-SS associated with seq2 is missed. If the WTRU determines that seq_new = seq_next, WTRU may determine that none of the LP-WUS or LP-SS is missed.

[0119] Examples of WTRU evaluating exit conditions and exiting LP-WUS monitoring are disclosed. In various embodiments, if the WTRU identifies one or more missed LP signals (e.g., LP-WUSs or LP-SSs), the WTRU may evaluate / determine one or more configured and / or indicated exit conditions. Examples may include the following:

[0120] (1) The WTRU may determine / evaluate MDR of LP-WUS and / or LP-SS, whereMDR of LP-WUS and / or LP-SS may be defined as, number of missed LP-WUSs or LP-SSs within time windows (number of detected and missed LP-WUSs and / or LP-SSs within the time window).

[0121] (2) The WTRU may determine the number of consecutively missed LP-WUSs and / or LP-SSs as the number of LP-WUSs and / or LP-SSs identified to be missed by the WTRU.

[0122] (3) The WTRU may update the ‘missed-signal counter’ based on the number ofLP-WUSs or LP-SSs identified to be missed by the WTRU. For example, if timer for a missed-signal counter has expired, the WTRU may reset the counter. If the timer has not expired, the WTRU may add the number of identified missed LP signals (e.g., LP-WUS and / or LP-SS) to the missed-signal counter value. Once the missed-signal counter value is updated, the WTRU may test if the updated counter value exceeds the preconfigured threshold.

[0123] (4) The WTRU may update the number of missed LP-WUSs and / or LP-SSs within a configured time window (e.g., a preconfigured moving time window). For example, the WTRU may count the number of identified missed signals within a configured moving time window.

[0124] (5) The WTRU may determine / evaluate the detection rate (DR) of LP-WUS and / orLP-SS, where the DR of LP-WUS and / or LP-SS may be defined as, the number of detected LP-WUSs or LP-SSs within a configured time window-? (number of detected and missed LP-WUSs and / or LP-SSs within configured time window).

[0125] Based on the evaluated one or more exit conditions, the WTRU may determine to exit monitoring LP WUS (e.g., the WTRU stop receiving low-power signals via its LR, wakes up its MR, e.g., for monitoring paging signals / channels) or continue to monitor LP-WUS.

[0126] In one example, if MDR of LP-WUS and / or LP-SS (e.g., based on the determined MDR on LP-WUS and / or LP-SS) > the MDR threshold, the WTRU may determine to exit monitoring LP-WUS. If the WTRU determines that MDR of LP-WUS and / or LP-SS < the MDR threshold, the WTRU may determine to continue monitoring LP-WUS.

[0127] In another example, if the number of consecutively missed LP-WUSs and / or LP- SS > threshold on consecutive missed LP signals, the WTRU may determine to exit monitoring LP-WUS. If the number of consecutively missed LP-WUSs and / or LP-SS < the threshold on consecutive missed LP signals, the WTRU may determine to continue monitoring LP-WUS.

[0128] In yet another example, if the ‘missed-signals counter’ exceeds the configured threshold (a maximum value for missed-signal counter), the WTRU may determine to exit monitoring LP-WUS. Otherwise, the WTRU may determine continue monitoring LP-WUS.

[0129] In a further example, if the DR of LP-WUS and / or LP-SS < a threshold on DR, the WTRU may determine to exit monitoring LP-WUS. If DR of LP-WUS and / or LP-SS > a threshold on DR, the WTRU may determine to continue monitoring LP-WUS via LR.

[0130] As a further example, if number of missed LP-WUSs and / or LP-SSs within the moving time window > the threshold on number of missed LP signals, the WTRU maydetermine to exit monitoring LP-WUS. If number of missed LP-WUSs and / or LP-SSs within the moving time window < the threshold on number of missed LP signals, the WTRU may determine to continue monitoring LP-WUS via LR.

[0131] WTRU example behavior in exiting LP-WUS monitoring is disclosed. In various embodiments, a WTRU may stop, exit, deactivate, stop attempting to receive, or stop monitoring LP signals (individually or collectively referred to herein as exit monitoring LP signals, LP-WUS or exit LP-WUS monitoring). In various embodiments, the exiting of LP- WUS monitoring may be based on one or more of the configured / evaluated exit conditions. Once a WTRU exits monitoring LP-WUS, the WTRU may turn off the LR and / or begin, resume, or activate the MR. In activating the MR, the WTRU may receive one or more DL signals and or channels (e.g., one or more of PEI, paging PDCCH, paging PDSCH, and SI indicated via paging). Alternatively, or in addition, in activating the MR, the WTRU may transmit one or more UL signals and / or channels (e.g., one or more of Msg1 , MsgA, and Msg3). As shown in FIG. 3 step 340, the WTRU may report and / or indicate to the base station / gNB and / or the core network (CN), the one or more exit conditions met (e.g., from step 330), and / or the evaluated exit conditions of step 325 (e.g., MDR of LP-SS and / or MDR of LP-SS that triggered the WTRU to exit LP-WUS monitoring, the number of consecutively missed LP-WUSs / LP-SSs and / or value of the timer when the ‘missed signal counter’ exceeded the counter). In one example, the WTRU reports the number of exit conditions detected.

[0132] In various embodiments, the WTRU may use one or combination of the following examples to transmit / sent the report and / or indication of step 340.

[0133] In one example, the WTRU may transmit / send the report and / or indications by using a preconfigured PUSCH resource. As an example, the WTRU may transmit a PUSCH carrying the report and / or indication in a PUSCH resource using a configured grant resource (e.g., a configured grant for small data transmission (SDT)). In one example, the WTRU may transmit a PUSCH carrying the report and / or indication in a Msg 3 / Msg A of a random access procedure.

[0134] In another example, the WTRU may report and / or indicate the exit conditions met via preconfigured PRACH resource. By way of example, the WTRU may transmit one or more PRACH messages for the WTRU exit LP signal monitoring indication. For example, the WTRU may be preconfigured (e.g, via RRC signaling) with one or more PRACH preambles where each PRACH preamble is associated with an exit condition. The WTRU may select one or more PRACH preambles based on the exit conditions determined to be met. The WTRU may transmit a PRACH preamble in preconfigured PRACH resources.

[0135] In another solution, the WTRU may send the report and / or indication after the WTRU receives a page (e.g., the WTRU PRACH for connection request, report MDR via Msg3, MsgA or later messages).

[0136] In other embodiments, the WTRU may send the report and / or indication via one or more UL RSs (e.g., one or more of SRS, UL PT-RS, UL DM-RS, etc.). For example, the WTRU may transmit one or more SRS resources out of a configured set of SRS resources for the WTRU indication. The WTRU may select one or more SRS resources based on the exit conditions determined to be met, for example, based on preconfigured association (e.g., configured via RRC signaling) between SRS resources and exit conditions or number of exit conditions identified to be met (e.g., based on preconfigured association (e.g., via RRC signaling) between SRS resources and number of exit conditions met).

[0137] In some embodiments, the WTRU may transmit one or more PUCCH messages for the WTRU indication of exiting LP signal monitoring. The WTRU may determine the method and / or resources (e.g., transmit PRACH, send report / indication via a PUSCH / PUCCH, wait for a page and report / indication via Msg3 or MsgA etc.) for the report and / or indication based on exit conditions and / or number of exit conditions determined to be met. As an example, if the WTRU determines a first set of exit condition (e.g., exit condition on MDR on LP-WUS) is met, the WTRU may use a first exit reporting method and / or resource. If the WTRU determines a second set of exit conditions (e.g., exit conditions on MDR of LP-WUS and number of consecutively missed LP-WUSs) are met, the WTRU may use a second exit reporting method and / or resource. For example, if the WTRU determines a first number of exit conditions are met, the WTRU may use a first method and / or resource. If the WTRU determines a second number of exit conditions are met, the WTRU may use a second, different, method and / or resource.

[0138] Embodiments of monitoring for exit conditions by using configured monitoring occasions (MOs) for LP signal monitoring are now described.

[0139] In various of these embodiments, the WTRU may receive one or more of the following configurations / indications (e.g., via RRC signaling, SI, RRC release message, paging messages). WTRU configuration / indications may include: (i) one or more types of LP signals; (ii) resources configuration of one or more types of (e.g., periodic) monitoring occasions (MOs); and / or (iii) one or more exit conditions evaluated based on the success of the WTRU receiving at least one of the associated LP signals in a MO or failure to receive the associated LP signal in the MO and thresholds associated with each exit condition. Examples of configuration / indication information received these embodiments follow.

[0140] In one example, one or more types of LP signals (e.g., 1sttype LP signal, 2rdtype LP signal, 3rdtype LP signal) may be used. For example, a 1st type LP signal may be a LP- WUS, a 2ndtype LP signal may be a LP-SS, a 3rd type LP signal may be a LP beacon (e.g., the LP beacon may be a signal that indicates to the WTRU that the WTRU is in sufficient coverage). For example, if the beacon is able to be received, the WTRU may determine that it has sufficient radio reception coverage for LP signal reception. In another example, when a WTRU receives a LP beacon, the WTRU may determine that there is a gNB that supports LP-WUS monitoring.

[0141] In embodiments, an LP beacon may be a separate type of a LP signal or a part of a type of LP signal. For example, a LP-SS may consist of two parts, a 1stpart which is a synchronization signal and a 2ndpart which carries a payload. The LP beacon may be the 1stpart of the LP-SS (i.e., synchronization signal).

[0142] Resources configuration of one or more types of (e.g., periodic) MOs may be utilized (e.g., 1 st type MO, 2nd type MO, 3rd type MO). Example configuration information of each MO may include (i) association between each MO and one or more LP signals and (ii) one or more exit conditions with configured thresholds, examples of which follow.

[0143] Association between each (e g., periodic) MO and one or more LP signals. In an example configuration, each type of MOs may associate with one type of LP signal. For example, a 1sttype MO may be associated with a 1 st type LP signal (e.g., LP-WUS), a 2ndtype MO may be associated with a 2nd type LP signal (e.g. LP-SS), and a 3rdtype MO is associated with a 3rdtype LP signal (e.g., LP beacon). In another example configuration, a 2ndtype of MOs may be associated with more than one LP signal types (e.g., 2ndtype MO is associated with 2ndtype LP signal (e.g., LP-SS) and 3rdtype LP signals (e.g., LP beacon) but only one of the signals (i.e., 2nd type LP signal (e.g., LP-SS) or a 3rdtype LP signal (e.g., LP beacon)) is expected to be received in a MO). The periodicity of each type of MO may also be configured, for example, the WTRU may receive the relative periodicity of each type of MO compared to paging opportunities (Pos) (e.g., via RRC signaling, SI). Resource configuration of each MO (e.g., time-frequency resources of each MO (e.g., offset with respect to a PO or a PF)).

[0144] One or more exit conditions evaluated based on the success (e.g., WTRU receives at least one of the associated LP signals in the MO) or failure (e.g., WTRU receives none of the associated LP signal in the MO) of MOs and thresholds associated with each exit condition. For example, the WTRU may receive a configuration for example evaluated exit conditions, which may include one or more of the following example (1)-(6):

[0145] (1) Expiry of a timer (‘failed-MO timer’) which tracks the duration one or more types of MOs are failed (e.g., 1st type MO);

[0146] (2) The number of failed MOs of one or more types of MOs within a preconfigured time (e.g., a moving time window) > a threshold;

[0147] (3) A counter (‘failed-MO counter’) that counts the number of failed MOs belongs to one or more types of MOs against a timer > a threshold;

[0148] (4) The number of consecutively failed MOs of one or more types of MOs > a threshold;

[0149] (5) Failure rate of one or more types of MOs within a preconfigured time window(e.g., a moving time window) > a threshold, where failure rate of a type of MO = number of times the MOs of the type of MO failed within a time window / number of times the MOs of the type of MO occurred during the time window; and / or

[0150] (6) Success rate of one or more types of MOs < a threshold, where success rate of a type of MO = number of times MOs of the type of MO was successful within a time window / number of times the MOs of the type of MO occurred during the time window.

[0151] In one embodiment, the WTRU may receive an indication / configuration (e.g., via RRC signaling, RRC release message, DCI indication, MAC-CE indication, paging signals, SI, RRC release message) to monitor for LP-WUS(s), LP-SS(s) and / or LP beacon(s) while in a configured / indicated / determined RRC state (e.g., RRC IDLE and / or INACTIVE states, RRC CONNECTED). Upon the indication, the WTRU may place the MR in a sleep state (e.g., deep sleep state) associated with LP-WUS monitoring mode (e.g., WTRU places its MR in a deep sleep state if the WTRU is configured to perform RRC INACTIVE / IDLE mode LP-WUS monitoring) and turn on LR for LP signal (e.g., LP-WUS, LP-SS, LP beacon) monitoring.

[0152] Examples of WTRU monitoring MOs and evaluating exit conditions are disclosed. In one embodiment, a WTRU may determine the successful or failed operation in one or more monitoring occasions (MO). In an example, the WTRU may receive one or more configuration information and / or indications on one or more MO configurations. The configurations may include time and frequency resources, periodicity, LP signals, etc. For example, the WTRU may be configured with one or more LP-WUS signals, where the configuration may include corresponding sequences, OOK-based signaling, etc. In an example, the WTRU may be configured with time and frequency resources during which the WTRU may monitor to receive at least one of the configured LP signals and / or attempts to detect and / or decode one. In an example, the WTRU may receive configuration and / or indications, for example from a gNB, for example via SIB, RRC, MAC-CE, DCI, etc.

[0153] The WTRU may monitor one or more configured MOs, where for example, the monitored MOs may be of one or more different MO types. In an example, the WTRU may determine, identify, and / or indicate a first MO as successful, if the WTRU has received, detected, and / or decoded at least one of the configured LP signals in the first MO. For example, the WTRU may considerthe first MO as successful if the WTRU decodes at least one of the received and / or detected LP-WUS in the first MO and determines that the decoding is successful.

[0154] In another example, the WTRU may determine, identify, and / or indicate a second MO as failed, if the WTRU does not receive, detect, and / or decode any of the configured LP signals in the second MO. For example, the WTRU may consider the second MO as failed if the WTRU does not receive and / or detect any of the configured LP-WUS in the second MO. In another example, the WTRU may determine that the second MO is failed, if the WTRU cannot decode any of the received and / or detected LP-WUS successfully in the first MO.

[0155] According to certain embodiments, the WTRU may consider decoding of a received and / or detected LP-WUS successful if, for example, the WTRU could decode the cyclic redundancy check (CRC) in the received signaling without errors; the WTRU may consider decoding of a received and / or detected LP-WUS successful, if for example the detected sequence is the same as one of the configured sequences; the WTRU may consider decoding of a received and / or detected LP-WUS successful, if for example the energy detection receiver indicates detected energy higher than a configured threshold, and so forth.

[0156] In one embodiment, a WTRU may determine one or more exit conditions based on determined successful or failed MOs. As an example, the WTRU may determine, be configured, and / or indicated with one or more exit conditions, based on which the WTRU may determine to exit LP-WUS monitoring and, for example, wake up the MR, or continue monitoring LP-WUS. The WTRU may determine to exit monitoring LP-WUS if one or more of the configured and / or indicated exit conditions are met. In an example, the WTRU may receive configuration, indications, thresholds, timer, counter, etc. for determining one or more exit conditions, for example from a gNB, e.g., via system information block (SIB), RRC, MAC-CE, DCI, etc. In an example, the WTRU may be configured based on one or more of the example exit conditions (1)-(6) below.

[0157] (1) Failed-MO Timer. For example, the WTRU may be configured with a timer, where for example the WTRU may initiate when the WTRU starts LP-WUS monitoring. The WTRU may determine that exit condition is met, if no successful MO is determined and / or detected by the WTRU before the ‘failed-MO timer’ expires.

[0158] (2) Failed-MO Counter. For example, the WTRU may be configured with a MAX value counter for the number of failed MOs. The WTRU may initiate a counter when the WTRU starts LP-WUS monitoring and increments the counter for each failed MO. The WTRU may determine that exit condition is met, if the counter has reached the configured MAX value. Alternatively, in another example, the WTRU may be configured with a threshold for the failed-MO counter. As such, the WTRU may determine that exit condition is met, if the counter is higher than the configured threshold.

[0159] (3) Number of failed MOs. For example, the WTRU may be configured to count the total number of failed MOs in a determined, (pre)configured, (pre)indicated time duration, time period, and / or time window. The WTRU may receive indications and / or configuration on the start, duration, and end of the corresponding time window. The WTRU may determine that exit condition is met, if the counted total number of failed MOs within the configured, determined, and / or indicated time window is higher than a determined, (pre)configured, (pre)indicated threshold.

[0160] (4) Number of consecutively failed MOs. For example, the WTRU may be configured to count the total number of consecutive failed MOs. The WTRU may receive indications and / or configuration on one or more thresholds on the total number of consecutive failed MOs. The WTRU may determine that exit condition is met, if the counted total number of consecutive failed MOs higher than the corresponding determined, (pre)configured, (pre)indicated threshold.

[0161] (5) Failure Rate. For example, the WTRU may be configured to calculate the failure rate, for example over total number of configured MOs, for example in a determined, (pre)configured, (pre)indicated time duration, time period, and / or time window. In another example, the WTRU determine, be indicated, and / or configured to calculate the failure rate, for example over a determined, (pre)configured, and / or (pre)indicated number of configured MOs. The WTRU may receive indications and / or configuration on the start, duration, and end of the corresponding time window. The WTRU may receive configuration on the total number of MOs to be considered. The WTRU may receive configuration on the threshold on the failure rate. The WTRU may determine that exit condition is met, if the calculated failure rate is higher than the determined, (pre)configured, and / or (pre)indicated threshold.

[0162] (6) Success Rate. For example, the WTRU may be configured to calculate the success rate, for example over total number of configured MOs, for example in a determined, (pre)configured, (pre)indicated time duration, time period, and / or time window. In another example, the WTRU determine, be indicated, and / or configured to calculate the success rate, for example over a determined, (pre)configured, and / or (pre) indicated number of configured MOs. The WTRU may receive indications and / or configuration on thestart, duration, and end of the corresponding time window. The WTRU may receive configuration on the total number of MOs to be considered. The WTRU may receive configuration on the threshold on the success rate. The WTRU may determine that exit condition is met, if the calculated success rate is lower than the determined, (pre)configured, and / or (pre)indicated threshold.

[0163] In one embodiment, a WTRU may stop, exit, or deactivate monitoring of LP-WUS based on one or more of evaluated conditions. Based on the stop, the exit or the deactivation, the WTRU may begin, resume, or activate MR. Based on the activation, the WTRU may receive one or more DL signals and or channels (e.g., one or more of PEI, paging PDCCH, paging PDSCH, and SI indicated via paging). Based on the activation, the WTRU may transmit one or more UL signals and / or channels (e.g., one or more of Msg1 , MsgA and Msg3). The WTRU may transmit an indication (e.g., to a gNB and / or a CN). The WTRU indication may indicate that the one or more exit conditions are met (e.g., failed-MO timer expired and / or failed-MO counter exceeds a threshold). The WTRU indication may indicate evaluated exit conditions (e.g., success rate of one or more types of MOs, failure rate of one or more types of MOs, value of the timer when the failed-MO counter exceeds the threshold). The WTRU indication may be based on transmitting one or more of the following signals (1)-(4).

[0164] (1) PUSCH-ln one solution, the WTRU may transmit one or more PUSCH messages for the WTRU indication. The one or more PUSCH messages may include: transmitting a PUSCH in a PUSCH resource via a configured grant resource for SDT or transmitting a PUSCH for Msg 3 / Msg A;

[0165] (2) PUCCH-ln one example, the WTRU may transmit one or more PUCCH messages for the WTRU indication;

[0166] (3) PRACH— As an example, the WTRU may transmit one or more PRACH messages for the WTRU indication. The one or more PRACH messages may be include transmitting via the PRACH using a preconfigured PRACH resource and / or transmitting via the PRACH for connection request; and / or

[0167] (4) UL RSs (e.g., one or more of SRS, UL PT-RS, UL DM-RS and, etc.)— In an example, the WTRU may transmit one or more SRS resources for the WTRU indication as mentioned previously.

[0168] Referring to FIG.4 timing diagram 400 shows a first illustrative example of LP signal monitoring exit conditions identifying missed signals based on indicated sequential order of signals transmitted by a base station. As discussed previously with respect to FIG.3 method 400, a WTRU may receive configurations / indications (e.g., via RRC signaling, SI, RRC release message) including information of one or more the examples that follow.

[0169] Forthe example, in FIG. 4, WTRU configuration information may include indication of a set of tag IDs 405, e.g., {00, 01 , 10, 1 1} such that a received LP-WUS having a tag ID value may be identified to correspond to a specific set of configured tag IDs. The WTRU configuration information may also include indication of, or information for the WTRU to derive, a tag ID assignment pattern (e.g., a group of tag IDs that are expected to be received in sequential repetitions, e.g., 00, 01 , 10, 11 , 00, 01 , ...), which may be used to identify any missed LP-WUS(s) and / or confirm receipt of LP-signals, e.g., LP-WUS(s) and / or LP-SS(s), received in proper order, i.e., no LP signals are missed.

[0170] In addition, or alternatively, referring to the example of FIG. 5 timing diagram 500, WTRU configuration information may include, or information to derive, a 1stset of sequences 505 and association with tag IDs, such that a tag ID value of a received LP-SS may be identified to correspond a specific sequence of the 1 st set. The configuration in this example may include a 2ndset of sequences and a sequence assignment pattern (e.g., 2ndset of sequences (e.g., {seqO, seq1 , seq2, seq3}) are assigned in a sequential order, e.g., seqO, seq1 , seq2, seq3, seqO, ...), which may be used to identify any missed LP signals or confirm receipt of LP-SS(s) received in proper order, i.e., no LP-SS(s) signals are missed. The foregoing tag ID assignment pattern(s) (FIG. 4) or sequence assignment pattern (FIG. 5) may be configured and / or used exclusively from each other, or both used together for determining any missed LP signals based on WTRU selection / base station indication and / or used separately for different types of LP signals, e.g., tag ID assignment pattern for LP-WUS(s) as shown in FIG. 4 or tag ID sequence pattern for LP-SS(s) as shown in FIG. 5.

[0171] The WTRU may further be configured with one or more exit conditions and thresholds associated with each exit condition. For example:(i) Mis-detection rate (MDR) of LP-WUS and / or LP-SS > a threshold;(ii) Number of consecutively missed LP-WUSs and / or LP-SSs > a threshold;(iii) Counter (‘missed-signal counter’) that counts the number of missed LP- WUSs and / or LP-SSs against a timer > a threshold;(iv) Detection rate (DR) of LP-WUS and / or LP-SS < a threshold; and / or(v) Number of missed LP-WUSs and / or LP-SSs within a configured time window (e.g., a moving time window) > a threshold.

[0172] In various embodiments, the WTRU receives an indication to monitor for LP-WUS and / or LP-SS (e.g., while in, or transition to, RRC IDLE and / or INACTIVE states). Based on the received and expected tags and / or sequences (e.g., 1st set of sequences), or tag IDs, of the successfully received LP-WUSs and / or LP-SSs, the WTRU may identify one or more missed LP-WUSs and / or LP-SSs. It is noted that LP-WUS(s) and / or LP-SS(s) may be transmitted / received in an aperiodic or periodic fashion.

[0173] In the example of FIG. 4, the WTRU determines a tag ID 405 from the received LP signal (e.g., LP-WUS, LP-SS), shown as 1st-6thLP-WUS, and compares it to the configured / corresponding tag ID assignment pattern to determine missed LP signal(s). As shown in FIG. 4, once the WTRU receives the 6thLP-WUS 450 and its tag ID, the WTRU identifies that the 4thand 5thLP-WUS(s) corresponding to tags 1 1 and 00 were missed.

[0174] When a LP-WUS or LP-SS is received, based on its tag ID (tag_new), and the tag ID of the last received LP-WUS or LP-SS (tag_old), the WTRU identifies one or more missed LP-WUSs or LP-SSs. In one example, If the WTRU determines that tag_new A next tag in the tag ID assignment with respect to tag_old (tag_next), the WTRU determines that one or more LP-WUSs or LP-SSs are missed. The WTRU determines the number of missed LP-WUSs or LP-SSs based on the minimum number of tags configured between tag_new and tag_old in the tag ID assignment, e.g., if tag ID assignment is {00, 01 , 10, 1 1 , 00, 01 , ...}, tag_new = 01 and tag_old = 10, the WTRU determines that 2 LP-WUSs or LP- SSs are missed based on that minimum 2 tag IDs, i.e., 11 , and 00, (shown as 4thand 5thLP-WUS) are configured between tag IDs 10 and 01 in the tag ID assignment (see FIG. 4). If the WTRU determines that tag_new = tag_next, the WTRU determines that none of the LP-WUS or LP-SS are missed.

[0175] In the example of FIG. 5, the WTRU determines a tag ID based on the received signals (e.g., LP-WUS, LP-SS), e.g., a tag ID is associated with a sequence of LP-WUS and / or LP-SS (e.g., overlaid OFDM sequence on OOK signal). For example, a tag ID is associated with a time and / or frequency resource index (symbol, slot, time offset (e.g., with respect to the PO), frequency offset), e.g., a tag ID is received in the payload of LP-WUS or LP-SS (e.g., OOK based LP-WUS or LP-SS).

[0176] Based on the received and expected sequences (e.g., 2nd set of sequences pattern) of the successfully received LP-WUSs or LP-SSs, the WTRU identifies one or more missed LP-WUSs or LP-SSs. In one example, the WTRU determines a sequence (e.g., out of the 2ndset of sequences) based on received signals (e.g., LP-WUS, LP-SS), e.g., a sequence used to scramble at least a part of the LP-WUS or LP-SS, or e.g., a sequence received with LP-WUS or LP-SS.

[0177] When a LP-WUS or LP-SS is received, based on its sequence (seq_new), and the sequence of the last received LP-WUS or LP-SS (seq_old), the WTRU identifies one or more missed LP-WUSs or LP-SSs. As shown in FIG. 5, when the WTRU receives the 4thLP-SS 550, its sequence is identified from the configuration of sequences corresponding to the tag ID, e.g., (seq3). The WTRU determines the 3rdLP-SS corresponding to seq2 has been missed.

[0178] In one example, if the WTRU determines that seq_new A next sequence in the sequence assignment w.r.t. seq_old (seq_next), the WTRU determines that one or more LP-WUSs or LP-SSs are missed. The WTRU determines the number of missed LP-WUSs or LP-SSs based on the minimum number of sequences configured between two sequences seq_new and seq_old in the sequence assignment. As shown in FIG. 5, for example, if sequence assignment is {seqO, seq1 , seq2, seq3, seqO, seq1 , ...}, seq_new = seq3 and seq_old = seq1 , the WTRU determines that 1 LP-WUSs of LP-SS are missed based on that the minimum number of sequences between seq1 and seq3 sequences in the sequence assignment is 1. If the WTRU determines that seq_new = seq_next, the WTRU determines that none of the LP-WUS or LP-SS are missed.

[0179] When a WTRU identifies one or more missed LP-WUSs or LP-SSs, the WTRU evaluates one or more exit conditions. Example exit conditions to be evaluated may include:

[0180] (i) The WTRU determines MDR of LP-WUS and / or LP-SS (e.g., number of missedLP-WUSs or LP-SSs within time window-? (number of detected and missed LP-WUSs or LP-SSs within the time window));

[0181] (ii) The WTRU determines the number of consecutively missed LP-WUSs and / or LP-SSs (e.g., number of LP-WUSs or LP-SSs identified to be missed by the WTRU);

[0182] (iii) The WTRU updates ‘missed-signal counter’ based on the number of LP-WUS or LP-SS identified to be missed by the WTRU;

[0183] (iv) The WTRU updates the number of missed LP-WUSs and / or LP-SSs within a configured time window (e.g., a moving time window); and / or

[0184] (v) The WTRU determines the detection rate (DR) of LP-WUS and / or LP-SS (e.g., number of detected LP-WUSs or LP-SSs within a time window?- (number of detected and missed LP-WUSs or LP-SSs within the time window)).

[0185] Based on the evaluated one or more exit conditions, the WTRU may determine to exit monitoring LP-WUS or continue monitoring LP-WUS. Example evaluated conditions met for exiting LP-WUS monitoring may include the WTRU determining:

[0186] (i) that

[0187] (ii) that the number of consecutively missed LP-WUSs and / or LP-SS > a threshold;

[0188] (Hi) a ‘missed-signal counter’ exceeds the configured threshold;

[0189] (iv) that a detection rate (DR) of LP-WUS and / or LP-SS < a threshold; and / or

[0190] (v) that number of missed LP-WUSs and / or LP-SSs within the moving time window> the preconfigured threshold.

[0191] If the WTRU determines to exit monitoring LP-WUS based on one or more evaluated exit conditions, the WTRU turns on the MR and may receive one or more DL signals and or channels (e.g., PEI, paging PDCCH, paging PDSCH, SI indicated via paging) and / or transmit one or more UL signals and / or channels (Msg1 , MsgA, Msg3).

[0192] The WTRU may report to the base station / gNB and / or the core network (CN) the one or more exit conditions met, and / or evaluated exit conditions (e.g., MDR of LP-SS and / or LP-SS that triggered the WTRU to exit LP-WUS monitoring). Examples of reporting exit condition information include one, or any combination of the following:

[0193] (i) The WTRU reports MDR of LP-SS and / or MDR of LP-SS, and / or number of consecutively missed LP-WUSs, and / or value of the timer when ‘missed signal counter’ exceeds the threshold;

[0194] (ii) The WTRU sends the report using resources preconfigured for a PUSCH resource (e.g., via a configured grant resource for SDT);

[0195] (iii) The WTRU indicates / reports the exit conditions met via a preconfigured PRACH resource;

[0196] (iv) The WTRU sends the report / indication after receiving a page (e.g., the WTRU PRACH for connection request, report MDR via Msg3, MsgA or later messages);

[0197] (v) The WTRU determines method and / or resources to report or indication based on exit conditions met; and / or

[0198] (vi) The WTRU determines method and / or resources to report or indication based on the number of exit conditions met.

[0199] In embodiments for evaluating LP signal monitoring exit conditions by using configured monitoring occasions (MOs), in one example method, a WTRU receives one or more of the following configurations / indications (e.g., via RRC signaling, SI, RRC release message, paging message): (i) one or more types of LP signals; (ii) resources configuration of one or more types of MOs; and (iii) one or more exit conditions evaluated based on the success (e.g., WTRU receives at least one of the LP signals in the MO) or failure (e.g., WTRU receives none of the associated LP signal in the MO) of MOs. Examples of configurations / indications for these embodiments follow.

[0200] The configuration may include one or more types of LP signals (e.g., 1 st type LP signal, 2nd type LP signal, 3rd type LP signal). For example, a 1 st type LP signal is a LP- WUS, a 2nd type LP signal is a LP-SS, a 3rd type LP signal is a LP beacon.

[0201] The resources configuration of one or more types of (e.g., periodic) MOs (1st type MO, 2nd type MO, 3rd type MO) may include one or more of (i) association between each (e.g., periodic) MO and one or more LP signals; (ii) periodicity of each type of MO (e.g., periodic, etc.); and / or (iii) resource configuration of each MO.

[0202] In associating between each type of MO and one or more LP signals, examples include:

[0203] -Each type of MO is associated with one type of LP signal (e.g. ,1sttype MO is associated with 1st type LP signal (e.g., LP-WUS), 2ndtype MO is associated 2nd type LP signal (e.g. LP-SS), and 3rdtype MO is associated with 3rdtype LP signal (e.g., LP beacon); and / or

[0204] -The 2ndtype of MOs are associated with more than one LP signal types, (e.g., 2ndtype MO is associated with 2ndtype LP signal (e.g., LP-SS) and 3rdtype LP signals (e.g., LP beacon) but only one of the signals (i.e. , 2nd type LP signal (e.g., LP-SS) or a 3rdtype LP signal (e.g., LP beacon)) is expected to be received in a MO).

[0205] The resource configuration of each MO (e.g., time-frequency resources of each MO (e.g., offset w.r.t. a PO or a PF)) may also be configured.

[0206] The one or more exit conditions may be evaluated based on the success (e.g., WTRU receives at least one of the LP signals in the MO) or failure (e.g., WTRU receives none of the associated LP signal in the MO) of MOs. Example exit conditions may include:

[0207] -Expiry of a timer (‘failed-MO timer’) which tracks the duration one or more types of MOs failed (e.g., 1sttype MO);

[0208] -The number of failed MOs of one or more types of MOs within a preconfigured time (e.g., a moving time window) > threshold;

[0209] -A counter (‘failed-MO counter’) that counts the number of failed MOs belongs to one or more types of MOs against a timer > a threshold;

[0210] -The number of consecutively failed MOs of one or more types of MOs > a threshold.

[0211] -The Failure rate of one or more types of MOs within a preconfigured time window (e.g., a moving time window) > a threshold, where failure of a type of MO = number of times the MO of the type of MO failed within the time window / number of times the MOs of the type of MO occurred during the time window; and / or

[0212] - A success rate of one or more types of MOs < a threshold, where success rate of a type of MO = number of times MOs of the type of MO was successful within the time window / number of times the MOs of the type of MO occurred during the time window.

[0213] Next, the WTRU receives an indication to monitor for one or more LP signals (e.g., LP-WUS and / or LP-SS and / or LP beacon), for example while in RRC IDLE and / or INACTIVE states.

[0214] The WTRU monitors MOs of one or more types of MOs and determines the success (e.g., WTRU receives at least one of the LP signals in the MO) of failure (e.g., WTRU receives none of the associated LP signal in the MO) of MOs (e.g., the WTRU determine the success or failure of receiving a LP signal via CRC check and / or sequence detection and / or energy detection).

[0215] Based on the success or failure of MOs, the WTRU evaluated one or more exit conditions. Based on the evaluated exit conditions, the WTRU determines if the one or more exit conditions are met. For example, the WTRU determines an exit condition is met by:

[0216] (i) if timer ‘failed-MO timer’, the WTRU determine that exit condition on the ‘failed-MO timer’ is met;

[0217] (ii) If the number of failed MOs of one or more types of MOs within a preconfigured time (e.g., a moving time window) > a preconfigure threshold;

[0218] (iii) If the counter ‘failed-MO counter’ > a preconfigured threshold, the WTRU determines that exit condition on ‘failed-MO timer’ is met;

[0219] (iv) If the number of consecutively failed MOs of one or more types of MOs > a preconfigured threshold;

[0220] (v) If the failure rate of one or more types of MOs > a preconfigured threshold, the WTRU determines that exit condition on failure rate of one or more types of MOs is met; and / or

[0221] (vi) If success rate of one or more types of MOs < a preconfigured threshold.

[0222] If the WTRU exit monitoring LP-WUS is based on one or more evaluated exit conditions, the WTRU turns on the MR and receives one or more DL signals and or channels (e.g., PEI, paging PDCCH, paging PDSCH, SI indicated via paging) and / or transmits one or more UL signals and / or channels (Msg1 , MsgA, Msg3). The WTRU reports to the gNB and / or the CN the one or more exit conditions met (e.g., failed-MO timer’ expired, failed-MO counter exceeds the threshold), and / or evaluated exit conditions (e.g., success rate of one or more types of MOs, failure rate of one or more types of MOs, valueof the timer when the failed-MO counter exceeds the threshold). Example WTRU actions may include:

[0223] (i) The WTRU sends the report using resources preconfigured for a PUSCH resource (e.g., via a configured grant resource for SDT);

[0224] (ii) The WTRU indicates / reports the exit conditions met via preconfigured PRACH resource;

[0225] (iii) The WTRU sends the report / indication after receiving a page (e.g., the WTRU PRACH for connection request, report failure rate of a type of MO via Msg3, MsgA or later messages);

[0226] (iv) The WTRU determines method and / or resources to report or indication based on exit conditions met; and / or

[0227] (v) The WTRU determines method and / or resources to report or indication based on the number of exit conditions met.

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

Claims

CLAIMSWhat is Claimed:

1. A method for a wireless transmit receive unit (WTRU), the method comprising: receiving configuration information indicating a set of tag IDs of low power (LP) signals, a pattern associated with sequential reception of the LP signals, and one or more LP signal monitoring exit conditions; identifying one or more missed LP signals of the sequential reception of the LP signals, based on a tag ID of each received LP signal and the pattern; and evaluating the one or more LP signal monitoring exit conditions using the identified missed LP signals.

2. The method of claim 1 , further comprising: determining to exit LP signal monitoring when one or more evaluated LP signal monitoring exit conditions have been met.

3. The method of claim 2, wherein, upon determining to exit LP signal monitoring, the method further comprises: activating a main radio (MR); and reporting to a network using the MR, indication of one or more of: the evaluated LP signal monitoring exit conditions met and a number of met exit conditions; the identified missed LP signals, or a value of a timer during a number of consecutively missed LP signals.

4. The method of any one of claims 1-3, wherein an LP signal monitoring exit condition comprises determining that a missed detection rate (MDR) of LP signals is greater than a configured MDR threshold.

5. The method of any one of claims 1-3, wherein an LP signal monitoring exit condition comprises determining that a number of consecutively missed LP signals being greater than a configured consecutively missed LP signal threshold.

6. The method of any one of claims 1-3, wherein an LP signal monitoring exit condition comprises a missed LP signal counter exceeding a configured counter threshold.

7. The method of any one of claims 1-6, wherein the pattern comprises an order of the tag IDs associated with the sequential reception of the LP signals.

8. The method of one of claims 1-6, wherein the pattern comprises an order of sequences associated with tag IDs of the sequential reception of the LP signals.

9. The method of claim 8, wherein each sequence of the order of sequences is based on one of: (i) an orthogonal frequency division multiplexing (OFDM) sequence overlaid on an on-off keying (OOK)- based LP signal; or (ii) a sequence used for scrambling at least part of a corresponding LP signal.

10. The method of any one of claims 1-9, wherein the LP signals comprise one or more of low power wake-up signals (LP-WUSs) or low power synchronization signals (LP-SSs).11 . A wireless transmit receive unit (WTRU) comprising: a processor; and a transceiver communicatively coupled with the processor, the transceiver and the processor configured to: receive configuration information indicating a set of tag IDs of low power (LP) signals, a pattern associated with sequential reception of the LP signals, and one or more low-power LP signal monitoring exit conditions; identify one or more missed LP signals of the sequential reception of the LP signals, based on a tag ID of each received LP signal and the pattern; and evaluate the one or more LP signal monitoring exit conditions based on the identified missed LP signals.

12. The WTRU of claim 11 , wherein the processor is further configured to: determine to exit LP signal monitoring when one or more evaluated exit conditions have been met.

13. The WTRU of claim 12, wherein, upon determining to exit LP signal monitoring, the processor and the transceiver are further configured to: activate a main radio (MR); and report to a network using the MR, indication of one or more of: the evaluated exit conditions met and a number of met conditions; the identified missed LP signals, or a value of a timer during a number of consecutively missed LP signals.

14. The WTRU of any one of claims 11-13, wherein an LP signal monitoring exit condition comprises determining that a missed detection rate (MDR) of LP signals is greater than a configured MDR threshold.

15. The WTRU of any one of claims 11-13, wherein an LP signal monitoring exit condition comprises determining a number of consecutively missed LP signals being greater than a configured consecutively missed LP signal threshold.

16. The WTRU of any one of claims 11-13, wherein an LP signal monitoring exit condition comprises determining a missed LP signal counter exceeding a configured counter threshold.

17. The WTRU of any one of claims 11-16, wherein the pattern comprises an order of the tag IDs associated with the sequential reception of the LP signals.

18. The WTRU of one of claims 11-16, wherein the pattern comprises an order of sequences associated with tag IDs of the sequential reception of the LP signals.

19. The WTRU of claim 18, wherein each sequence of the order of sequences is based on one of: (i) an orthogonal frequency division multiplexing (OFDM sequence overlaid on an on-off keying (OOK)- based LP signal; or (ii) a sequence used for scrambling at least part of a corresponding LP signal.

20. The WTRU of any one of claims 11-19, wherein the LP signals include one or more of low power wake-up signals (LP-WUSs) or low power synchronization signals (LP-SSs).

Images