CSI and RSRP reporting adaptation for LP-WUS monitoring users

Abstract

Systems, methods, and devices for transmitting a report, such as a CSI and / or RSRP report. A first low-power wake-up signal (LP-WUS) is received. The report is transmitted. The report is transmitted based on a field of the first LP-WUS and on a second LP-WUS, based on the field of the first LP-WUS having a first value. The report is transmitted based on the field of the first LP-WUS without receiving the second LP-WUS, based on the field of the first LP-WUS having a second value. In some implementations, the report is transmitted without receiving the second LP-WUS, based on the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold.

Description

IDC-2024P00698WCCSI AND RSRP REPORTING ADAPTATION FOR LP-WUS MONITORING USERSCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 701,222, filed September 30, 2024, the contents of which are incorporated herein by reference.BACKGROUND

[0002] Wake-up signals (WUS) are a type of power saving mechanism where a wireless device attempts to save power by powering down a main radio until a WUS is received on a low-power WUS radio receiver. Channel state information (CSI) may include information about a wireless channel between a wireless transmitter and a wireless receiver. Reference signal received power (RSRP) may include a measurement of power, at a wireless receiver, of a reference signal.SUMMARY

[0003] Some implementations provide systems, methods, and devices for transmitting a report, such as a CSI and / or RSRP report. A first low-power wake-up signal (LP-WUS) is received. The report is transmitted. The report is transmitted based on a field of the first LP-WUS and on a second LP-WUS, based on the field of the first LP-WUS having a first value. The report is transmitted based on the field of the first LP-WUS without receiving the second LP- WUS, based on the field of the first LP-WUS having a second value. In some implementations, the report is transmitted without receiving the second LP-WUS, based on the field of the first LP-WUS having the first value and the first LP- WUS including a number of fields having the first value exceeding a threshold.BRIEF DESCRIPTION OF THE DRAWINGS

[0004] 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:

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

[0006] FIG. 1B 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;

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

[0008] FIG. 1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1 A according to an embodiment;- 1 -9365181.1IDC-2024P00698WG

[0009] FIG. 2 is a block diagram illustrating example receiver architecture for a WTRU that is configured for operation with a LP-WUS;

[0010] FIG. 3 is a bitmap illustrating an example payload structure of first LP-WUS and second LP-WUS in a first case;

[0011] FIG. 4 is a bitmap illustrating an example payload structure of first LP-WUS and second LP-WUS in a second case;

[0012] FIG. 5 is a flowchart illustrating an example procedure relating to first and second LP-WUS;

[0013] FIG. 6 is a flow chart illustrating an example method implemented in a WTRU; and

[0014] FIG. 7 is a flow chart illustrating an example method implemented in a base station.DETAILED DESCRIPTION

[0015] Some implementations provide a method implemented in a wireless transmit / receive unit (WTRU). A first low-power wake-up signal (LP-WUS) is received. A report is transmitted. The report is transmitted based on a field of the first LP-WUS and on a second LP-WUS, based on the field of the first LP-WUS having a first value. The report is transmitted based on the field of the first LP-WUS without receiving the second LP-WUS, based on the field of the first LP-WUS having a second value.

[0016] Some implementations provide a WTRU. The WTRU includes circuitry configured to receive a first LP- WUS. The WTRU includes circuitry configured to transmit a report. The report is transmitted based on a field of the first LP-WUS and on a second LP-WUS, based on the field of the first LP-WUS having a first value. The report is s transmitted based on the field of the first LP-WUS without receiving the second LP-WUS, based on the field of the first LP-WUS having a second value.

[0017] In some implementations, the report is transmitted without receiving the second LP-WUS, based on the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold. In some implementations, the report is transmitted without receiving the second LP-WUS based on the field of the first LP-WUS having the first value, based on the first LP-WUS including a number of fields having the first value exceeding a threshold, and based on an identity of the WTRU. In some implementations, the report is transmitted according to a default behavior based on the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold. In some implementations, the report is transmitted according to a default behavior based on the field of the first LP-WUS having the first value and the second LP-WUS not being received. In some implementations, the report is transmitted based on a threshold amount of time being exceeded since a previous report having been transmitted. In some implementations, the report comprises a CSI report or an RSRP report. In some implementations, the first LP-WUS comprises a bitmap, and wherein the field of the first LP-WUS occupies a position in the bitmap corresponding to an identity of the WTRU. In some implementations, the first LP-WUS includes an indication of whether the second LP-WUS will occur. In some implementations, the bitmap includes an indication of whether the second LP-WUS will occur.- 2 -9365181.1IDC-2024P00698WC

[0018] Some implementations provide a base station. The base station includes circuitry configured to transmit a first LP-WUS. The base station includes circuitry configured to receive a report. A field of the first LP-WUS having a first value indicates that the report is to be transmitted based on a second LP-WUS. The field of the first LP-WUS having a second value indicates that the report is to be transmitted without the second LP-WUS.

[0019] Some implementations provide a method implemented in a base station. A first LP-WUS is transmitted. A report is received. A field of the first LP-WUS having a first value indicates that the report is to be transmitted based on a second LP-WUS. The field of the first LP-WUS having a second value indicates that the report is to be transmitted without the second LP-WUS.

[0020] In some implementations, the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold indicates that the report is to be transmitted without receiving the second LP-WUS. In some implementations, the field of the first LP-WUS having the first value, the first LP-WUS including a number of fields having the first value exceeding a threshold, and an identity of a wireless transmit / receive unit (WTRU), indicate that the report is to be transmitted without receiving the second LP-WUS. In some implementations, the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold, indicate that the report is to be transmitted according to a default behavior. In some implementations, the field of the first LP-WUS having the first value, and the second LP-WUS not being received, indicate that the report is to be transmitted according to a default behavior. In some implementations, the report is received based on a threshold amount of time being exceeded since a previous report was transmitted. In some implementations, the report comprises a CSI report or an RSRP report. In some implementations, the first LP-WUS comprises a bitmap, and wherein the field of the first LP-WUS occupies a position in the bitmap corresponding to an identity of a wireless transmit / receive unit (WTRU). In some implementations, the first LP-WUS includes an indication of whether the second LP-WUS will occur. In some implementations, the bitmap includes an indication of whether the second LP-WUS will occur.

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

[0022] 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 (ON) 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- 3 -9365181.1IDC-2024P00698WCWTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a station (ST A), 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-Fl 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 WTRU.

[0023] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 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 114a, 114b may include any number of interconnected base stations and / or network elements.

[0024] The base station 114a 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 114a 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 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0025] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless 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).

[0026] 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- 4 -9365181.1IDC-2024P00698WC technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed Uplink (UL) Packet Access (HSUPA).

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

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

[0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, 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).

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

[0031] The base station 114b in FIG. 1A 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 114b and the WTRUs 102c, 102d may utilize a cellularbased 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 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106.

[0032] The RAN 104 may be in communication with the CN 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 - 5 -9365181.1IDC-2024P00698WG 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.

[0033] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications 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.

[0034] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multimode 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 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0035] 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 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, 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.

[0036] 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 118 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 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0037] 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 116. 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- 6 -9365181.1IDC-2024P00698WG signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

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

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

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

[0041] The processor 118 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., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0042] The processor 118 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 GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 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.

[0043] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera - 7 -9365181.1IDC-2024P00698WC(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.

[0044] 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 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 118). In an embodiment, the WTRU 102 may include a halfduplex 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., for transmission) or the DL (e.g., for reception)).

[0045] FIG. 1C 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 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 ON 106.

[0046] 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 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. 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.

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

[0048] The CN 106 shown in FIG. 1C 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.

[0049] 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- 8 -9365181.1IDC-2024P00698WG between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

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

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

[0052] 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 other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

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

[0054] In representative embodiments, the other network 112 may be a WLAN.

[0055] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access 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.11e 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.

[0056] When using the 802.11 ac 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 - 9 -9365181.1IDC-2024P00698WC 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.11 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.

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

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

[0059] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11n, 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.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah 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).

[0060] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11ac, 802.11 af, 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.11ah, 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 (which supports 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.- 10 -9365181.1IDC-2024P00698WC

[0061] 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 from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.

[0062] FIG. 1 D 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 NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0063] 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 116. In one embodiment, the gNBs 180a, 180b, 180c may implement Ml MO 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).

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

[0065] 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.- 11 -9365181.1IDC-2024P00698WQ

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

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

[0068] 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 be established 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.

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

[0070] 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 110, 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.

[0071] 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 - 12 -9365181.1IDC-2024P00698WG 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 112, 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.

[0072] 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 114a-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 the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

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

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

[0075] Some implementations include LP-WUS monitoring.

[0076] FIG. 2 is a block diagram illustrating example receiver architecture 200 for a WTRU that is configured for operation with a low-power (LP) wake-up signal (WUS). Receiver architecture 200 includes a wake-up radio receiver 202 and a main radio receiver 204. Wake-up radio receiver 202 and main radio receiver 204 are each in communication with a baseband processor 206, which is in communication with an application processor 208. Wakeup radio 202 is configured to receive a LP-WUS 210, and main radio receiver 204 is configured to receive a main radio signal 212.

[0077] Architecture 202 is implementable in any suitable WTRU, such as WTRU 102 as shown and described with respect to FIG. 1A, 1 B, 1C, and 1 D. For example, in some implementations, wake-up radio receiver 202 and main radio receiver 204 are implemented as a part of transceiver 120, and baseband processor 206 and application processor 208 are implemented as a part of processor 118.- 13 -9365181.1IDC-2024P00698WC

[0078] Implementing the example architecture shown in FIG. 2, a 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 referred to as a low-power WUS (LP-WUS). The first radio may be referred to as a low-power radio (LR) or a low power wake-up radio (LP-WUR). A WUS (e.g., an LP-WUS) received, for example via the LR, may trigger wake-up or use of a second radio of the WTRU (e.g., the main radio (MR) of the WTRU) for data and / or control signal transmission and / or reception. This has the potential to reduce the power consumption of wireless devices.

[0079] The architecture shown and described with respect to FIG. 2 is implementable in any suitable WTRU, such as WTRU 102 as shown and described with respect to FIG. 1A, 1 B, 1C, and 1 D. For example, in some implementations, the wake-up radio receiver and main radio receiver are implemented as a part of transceiver 120, and baseband processor and application processor are implemented as a part of processor 118.

[0080] Some implementations include channel state information (CSI) and reference signal received power (RSRP) reporting with discontinuous reception (DRX) operation.

[0081] In some implementations, e.g., in connected mode DRX (C-DRX), CSI (e.g., periodic CSI) reporting and RSRP (e.g., L1-RSRP) reporting are semi-statically configured via radio resource control (RRC) configurations. In some implementations, an RRC configuration includes a first configuration of one or more CSI and / or RSRP report configurations and a second configuration indicating whether to transmit CSI and / or RSRP reports associated with skipped DRX active times.

[0082] In some implementations, if a WTRU monitors physical downlink control channel (PDCCH)s in a DRX active time, the WTRU transmits (e.g., periodic) a CSI and RSRP report or reports (e.g., any CSI and RSRP reports) configured by the first configuration. In some implementations, the WTRU transmits CSI and RSRP reports associated with skipped DRX active times if the second RRC configuration indicate to transmit CSI and RSRP reports.

[0083] Connected mode LP-WUS monitoring is configured with C-DRX, however, semi-statically configured CSI and RSRP reporting associated with C-DRX may not be appropriate for LP-WUS monitoring WTRUs, e.g., due to low power efficiency concerns, e.g., due to unnecessary transmissions of a CSI and RSRP report or reports in the case a WTRU that is awoken frequently. Further, semi-statically configured CSI and RSRP reporting associated with C-DRX may not be appropriate for LP-WUS monitoring WTRUs, e.g., as it may not be suitable for supporting long DRX durations, e.g., because CSI and / or RSRP reporting may not be able to be controlled dynamically. Further, semi- statically configured CSI and RSRP reporting associated with C-DRX may not be appropriate for LP-WUS monitoring WTRUs, e.g., because of higher resource use due to unnecessary transmissions of one or more CSI and RSRP reports. Further, semi-statically configured CSI and RSRP reporting associated with C-DRX may not be appropriate for LP-WUS monitoring WTRUs, e.g., because it may not be an optimal solution for WTRUs with low mobility and relatively stable link quality, e.g., which may be expected for LP-WUS monitoring WTRUs. Accordingly, it may be desired to provide a mechanism capable of dynamically controlling transmission of CSI and RSRP reports. It may be desired to provide devices, methods, and systems to dynamically control transmitting CSI and L1-RSRP reports for LP-WUS monitoring WTRUs.- 14 -9365181.1

[0084] FIG. 3 is a bitmap 300 illustrating an example payload structure of first LP-WUS 302 and second LP-WUS 304 for a first case, where a total number of WTRUs indicated to skip PDCCH monitoring is less than or equal to nSkipMax.

[0085] In some implementations, e.g., as shown in FIG. 3, based on indications received in the first LP-WUS, several WTRUs (indicated as UE(1), UE(3), UE(4), UE(5), and UE(7) in the figure) begin monitoring PDCCHs, and several other WTRUs (indicated as UE(0), UE(2), and UE(6) in the figure) skip monitoring PDCCHs (e.g., based on the corresponding bitmap values). In some implementations, e.g., assuming a time (timeSincelndicationToTxCSI in this example) < a 1st threshold for each WTRU and based on an indication for monitoring for a second LP-WUS (shown in the figure as x = 1), a WTRU determines to skip monitoring PDCCHs, and receives a 2nd LP-WUS.

[0086] In some implementations, e.g., as shown in FIG. 3, based on an indication received in the second LP-WUS, UE(0) and UE(2) do not report CSI and / or RSRP (e.g., based on indications shown in the figure as x=0), whereas UE(6) reports CSI and / or RSRP measurements (e.g., based on indications shown in the figure as x=1) based on a first CSI and / or RSRP report configuration group.

[0087] FIG. 4 is a bitmap 400 illustrating an example payload structure of first LP-WUS 402 and second LP-WUS 404 for a second case, where a total number of WTRUs indicated to skip PDCCH monitoring is greater than nSkipMax.

[0088] In some implementations, e.g., as shown in FIG. 4, based on indications received in first LP-WUS, several WTRUs (indicated as UE(1), UE(5), and UE(7) in the figure) begin monitoring PDCCHs, and several other WTRUs (indicated as UE(0), UE(2), UE(3), UE(4) and UE(6) in the figure) skip monitoring PDCCHs (e.g., based on the corresponding bitmap values). In some implementations, , e.g., assuming timeSincelndicationToTxCSI < 1 st threshold for each WTRU and based on an indication for monitoring for a second LP-WUS (shown in the figure as x = 1), out of WTRUs determining to skip monitoring PDCCHs, WTRU (6) determines that CSI and / or RSRP reporting indication for the WTRU is not included in second LP-WUS and reports CSI and / or RSRP measurements based on a default CSI and / or RSRP report configuration, whereas UE(0), UE(2), UE(3), UE(4), receive a second LP-WUS, e.g., because there are only enough bits (nSkipMax) available in the second LP-WUS to provide indications for UE(0), UE(2), UE(3), UE(4).

[0089] In some implementations, e.g., based on an indication received in 2nd LP-WUS, UE(0) and UE(2), do not report CSI and / or RSRP measurements, whereas UE(3) and UE(4) reports CSI and / or RSRP measurements based on 1 st CSI and / or RSRP report configuration group.

[0090] As discussed herein, the terms monitoring for downlink (DL) scheduling and PDCCH monitoring may be used interchangeably. As discussed herein, the terms LP-WUS occasion (LO) may be used interchangeably with MO and LP-WUS MO are used interchangeably. As discussed herein, DRX active time may be used to refer an on- duration of a DRX cycle regardless of WTRU monitoring for or not monitoring for any DL scheduling indication (e.g., PDCCH).

[0091] Some implementations provide CSI and / or RSRP reporting based on indications in a second LP-WUS.- 15 -9365181.1IDC-2024P00698WC

[0092] In some implementations, a LP-WUSs may be used to adapt CSI (e.g., CSI other than L1-RSRP) and / or RSRP (e.g., L1-RSRP) reporting by WTRUs while monitoring for LP-WUSs. Some such implementations may have the advantage of saving WTRU power, e.g., because adaptive CSI and / or RSRP reporting may avoid unnecessary CSI and / or RSRP reports. Further, Some such implementations may have the advantage of saving WTRU power, e.g., because adaptive CSI and / or RSRP reporting may extend sleep time of WTRUs in DRX operation. In some implementations, e.g., to support adaptive CSI and / or RSRP reporting via LP-WUS, a WTRU may implement one or more of the following steps and / or procedures.

[0093] Some implementations relate to a WTRU receiving a configuration.

[0094] For example, in some implementations, a WTRU may receive one or more of the following configurations and / or indications from gNB. In some implementations, the WTRU may receive the configurations and / or indications via RRC signaling, MAC control element (MAC-CE) indication, downlink control information (DCI) indication, SI, RRC release message, and so forth.

[0095] In some implementations, the configuration and / or indication may include a DRX configuration. The DRX configuration may include, indicate, and / or configure one or more of the following: DRX cycle duration; one or more timers associated with DRX active time (e.g., drx-onDurationTimer, drx-lnactivityTimer, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL), and rx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL; and / or a starting time of a first DRX active time (e.g., drx-SlotOffset) (e.g., a starting time of a first drx-onDurationTimer, e.g., during which the WTRU monitors for PDCCHs.)

[0096] In some implementations, the configuration and / or indication may include a LP-WUS monitoring configuration. For example, WTRU may receive a configuration for receiving first and second LP-WUS. In some implementations, the configuration may include, indicate, and / or configure one or more of the following: two LP-WUS occasions (LOs) (e.g., first LO and second LO) - for example, in some implementations, the WTRU may receive offsets for each LO with respect to (e.g., offset from) the starting time of the DRX active time; one or more LP-WUS MOs in each LO (e.g., the WTRU may receive starting time and duration of each LP-WUS MO within LO); and / or one or more LP synchronization signals (LP-SSs) (e.g., the WTRU may receive an indication of periodicity, a starting point of a first LP-SS or LP-SS burst which consists of multiple LP-SS, and a structure of the LP-SS and / or LP-SS burst.)

[0097] In some implementations, the configuration and / or indication may include a structure or structures of first and second LP-WUS payloads which may include, indicate, or configure one or more of the following: In some implementations, if a first LP-WUS and second LP-WUS are bitmap-based and LP-WUS include a per-WTRU or per- subgroup wake-up indicated in the first LP-WUS, WTRU may receive configuration to identify one or more bits that carry indications for the WTRU or the subgroup of the WTRU (in some implementations, the configuration may include a mapping (e.g., mapping rule) between WTRU ID and payload in the first and second LP-WUS; and / or a mapping (e.g., mapping rule) between subgroup IDs and payload in the first and second LP-WUS); a configuration or indication of a number (M) of WTRUs associated with a first LP-WUS, an ID of WTRUs for first and second LP-WUS (e.g., local WTRU ID = {0, 1, 2, .... M-1}, a priority order of M WTRUs for CSI and / or RSRP reporting indication or WTRU determines priority based on local WTRU ID; and / or a configuration or indication of a number (N) of subgroups of - 16 -9365181.1IDC-2024P00698WCWTRUs associated with first LP-WUS, ID of subgroups of WTRUs for first and second LP-WUS (e.g., local subgroup ID = {1 , 2, .... N-1}; a priority of N subgroups of WTRUs for CSI and / or RSRP reporting indication; and / or WTRU determines priority based on local subgroup ID. Alternatively, in some implementations, the structure of each LP- WUS may be known to both gNB and WTRU (e.g., based on specifications).

[0098] In some implementations, the configuration and / or indication may include, indicate, or configure first, second, and third CSI (e.g., CSI reporting other than L1-RSRP measurements) and / or RSRP (e.g., L1-RSRP) report configuration groups. In some implementations, each group may include a set of one or more (e.g., periodic) CSI and / or RSRP report configurations, or a null set (e.g., corresponding to skipping transmitting CSI reports).

[0099] In some implementations, the configuration and / or indication may include, indicate, or configure the applicability of a second LP-WUS indication for CSI and / or RSRP reporting associated with each CSI and / or RSRP reporting configuration group. For example, in some implementations, the configuration and / or indication may indicate that the second LP-WUS indication: is applicable for CSI (i.e., CSI reporting other than L1-RSRP reporting) reporting only; is applicable for RSRP reporting only; or is applicable for both CSI and RSRP reporting. Alternatively, in some implementations, the applicability of a second LP-WUS indication for CSI and / or RSRP reporting may be a property of (e.g., may be indicated by) a CSI and / or RSRP reporting configuration. In another alternative, in some implementations, the applicability of a second LP-WUS indication for CSI and / or RSRP reporting may be a property of (e.g., may be indicated by) an individual CSI and RSRP report configuration associated with each CSI and / or RSRP report configuration group.

[0100] In some implementations, the configuration and / or indication may include, indicate, or configure a timer (e.g., CSI-Reporting-Appi ication-Timer) associated with a duration (e.g., in terms of a number of DRX cycles, slots, or frames, time (e.g., in milliseconds), etc.), and / or received indication for CSI and / or RSRP reporting via second LP- WUS is valid or used by a WTRU.

[0101] In some implementations, the configuration and / or indication may include, indicate, or configure a threshold (e.g., a first threshold) on time since the most recent indication for CSI and / or RSRP reporting via LP-WUS.

[0102] In some implementations, the configuration and / or indication may include, indicate, or configure a timer (e.g., CSI-RSRP-ConfigUpdateTimer) associated with a CSI reporting configuration group indication and / or RSRP report configuration indication within DRX active time.

[0103] In some implementations, the configuration and / or indication may include, indicate, or configure an indication to activate LP-WUS monitoring. For example, in some implementations, a WTRU may receive an indication (e.g., via MAC-CE indication, DCI indication, SI, RRC release message) to start monitoring LP-WUS. In some implementations, based on receiving the indication and / or receipt of the indication, the WTRU may start monitoring LP-WUS. Alternatively, in some implementations, the WTRU may start monitoring for LP-WUS based on the WTRU receiving one or more configurations (e.g., configuration of LP-WUS MO, LO, signal structure etc.). For example, in some implementations, in an example, WTRU may start monitoring LP-WUS at first LP-WUS MO (e.g., starting from the first symbol of LP-WUS MO) e.g., located at an offset, or a at least a preconfigured (e.g., via RRC signaling, MAC- CE indication, DCI indication) offset from the time WTRU receives indication or configuration for monitoring LP-WUS.- 17 -9365181.1IDC-2024P00698WCIn another example, in some implementations, the WTRU may start a preconfigured (e.g., via one or more of MAC- CE indication, DCI indication, SI, and RRC release message) timer once WTRU receives indication and / or configuration for monitoring LP-WUS. In some implementations, the WTRU may start monitoring LP-WUS from the first LP-WUS MO (e.g., first symbol of the LP-WUS MO) after timer expires.

[0104] Some implementations relate to a WTRU determining a CSI and / or RSRP reporting configuration.

[0105] For example, in some implementations, a WTRU monitoring LP-WUS may implement one or more of the following steps and / or procedures to determine a CSI and / or RSRP reporting configuration e.g., relating to WTRU wake-up based on first LP-WUS, CSI and / or RSRP reporting adaptation by WTRUs activated for a DRX active time, and / or CSI and / or RSRP reporting adaptation for WTRUs skipping a DRX active timer.

[0106] FIG. 5, discussed further below, is a flowchart illustrating an example procedure 500 relating to first and second LP-WUS, for determining a CSI and / or RSRP reporting configuration. Procedure 500 describes an example of WTRU CSI and / or RSRP reporting configuration, which is discussed in the context of other possible implementations herein.

[0107] For example, for some implementations relating to WTRU wake-up based on first LP-WUS, in some implementations, e.g., in step 502 of FIG. 5, a WTRU may monitor for and receive first LP-WUS in configured LP- WUS MOs of first LO. In some implementations, e.g., as shown by condition 504 of FIG. 5, based on indications received in first LP-WUS, the WTRU may determine whether to wake up (e.g., whether to wake up MR for monitoring and receiving PDCCHs in a next occurrence of DRX active time) or not to wake up (e.g., to continue monitoring for LP-WUS while MR is in a power saving state).

[0108] In some implementations, in an example configuration (referred to herein as "example configuration-A”), a WTRU may receive a bitmap-based first LP-WUS, e.g., of (M+1) bits. In some implementations, the first M bits may indicate a wake-up indication for M WTRUs or subgroups. In some implementations, the first M bits used for the wakeup indication may be ordered, e.g., based on local WTRU ID, or subgroup ID, or configured priority. In some implementations, e.g., based on local WTRU ID or subgroup ID, the WTRU may determine a bit that carries a wakeup indication for the WTRU. In some implementations, e.g., based on the received value (e.g., 0 or 1) of wake-up indication bit, the WTRU may determine to wake up MR for PDCCH monitoring in a next (e.g., next occurrence of) DRX active time (e.g., if the wake-up indication is first value (e.g., 1)) or to continue monitoring for LP-WUS (e.g., if the wake-up indication bit is second value (e.g., 0)) via LR. In some implementations, e.g., based on (M+1 )th bit, the WTRU may determine whether a second LP-WUS is transmitted or not. For example, in some implementations, if the received (M+1 )th bit has a first value (e.g., 0), the WTRU may determine that the second LP-WUS is not transmitted. If the received (M+1)th bit has a second value (e.g., 1), the WTRU may determine that the second LP-WUS is transmitted.

[0109] For some implementations relating to CSI and / or RSRP Reporting Adaptation by WTRUs Activated for a DRX Active Time, e.g., on condition 504 that the WTRU determines to wake up MR (e.g., to monitor for and receive DL scheduling indications, e.g., PDCCHs in the next DRX active time) based on indications received in first LP-WUS,- 18 -9365181.1IDC-2024P00698WC the WTRU may determine a CSI and / or RSRP reporting configuration, e.g., based on one or more of the following examples.

[0110] In a first example, in some implementations, at step 506, the WTRU may report CSI and / or RSRP measurements, e.g., based on a second CSI and / or RSRP report configuration group. For example, in some implementations, if a second CSI and / or RSRP report configuration group configures one or more CSI and / or RSRP reports (e.g., within next DRX active time), the WTRU may transmit respective CSI and / or RSRP reports. In some implementations, the WTRU may or may not return to LP-WUS monitoring in step 502 following step 506.

[0111] In a second example, in some implementations, the WTRU may determine a new CSI and / or RSRP reporting configuration, e.g., based on an indication received within a DRX active time. For example, in some implementations, a WTRU may start a preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication) timer (e.g., CSI-RSRP-ConfigUpdateTimer for example) during (e.g., at the beginning of) DRX active time. In some implementations, while the CSI-RSRP-ConfigUpdateTimer is running, the WTRU may monitor for and / or receive an indication (e.g., via a DCI on a preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication) control resource set (CORESET)) for a new CSI and / or RSRP report configuration group. In some implementations, the WTRU may report one or more CSI and / or RSRP reports configured by a new CSI and / or RSRP report configuration group within the DRX active time.

[0112] For some implementations relating to CSI and / or RSRP Reporting Adaptation for WTRUs skipping a DRX Active Timer, in some implementations, e.g., on condition 504 that the WTRU determines to not wake up (e.g., skips monitoring PDCCHs in the next DRX active time) for a DRX active time, e.g., based on indications received in first LP- WUS, the WTRU may implement one or more of the following steps and / or procedures to determine whether to transmit CSI and / or RSRP reports and a CSI and / or RSRP report configurations to use for CSI and / or RSRP reporting.

[0113] In some implementations, e.g., on condition 504 that the WTRU determines not to wake up based on indications received in first LP-WUS, the WTRU may determine a CSI and / or RSRP reporting configuration based indications received in a second LP-WUS or based on a default configuration. In some implementations, to this end, the WTRU may follow one or more of the following steps and / or procedures.

[0114] For example, in some implementations, a WTRU that does not receive a wake-up indication in a first LP- WUS may determine whether a prior received indication for CSI and / or RSRP reporting associated with DRX active time (e.g., in skipped DRX active times) is still valid, e.g., at condition 508. For example, in some implementations, each time the WTRU receives a new indication for CSI and / or RSRP reporting indicating whether to report CSI and / or RSRP reports in skipped DRX active times, the WTRU may start a timer (e.g., “CSI-Reporting-Application-Timer”). In some implementations, if the timer has expired, the WTRU may determine that most recently received indication for CSI and / or RSRP reporting is invalid or outdated (e.g., at condition 508). In some implementations, if the timer is running, the WTRU may determine that most recently received indication (e.g., to transmit or not to transmit) CSI and / or RSRP reporting is invalid or outdated (e.g., at condition 508). Alternatively, in some implementations, the WTRU may track (e.g., timeSincelndicationToTxCSI) time since the most recently received indication for CSI and / or RSRP reporting in skipped DRX active times. In some implementations, if the time timeSincelndicationToTxCSI > configured- 19 -9365181.1IDC-2024P00698WC threshold, the WTRU may determine that the prior indication (e.g., to transmit or not to transmit) for CSI and / or RSRP reporting is outdated (e.g., at condition 508). In some implementations, if the time timeSincelndicationToTxCSI < the configured threshold, the WTRU may determine that the prior indication (e.g., to transmit or not to transmit) for CSI and / or RSRP reporting is valid (e.g., at condition 508).

[0115] In some implementations, on condition 508 that the WTRU determines that the most recently received CSI and / or RSRP reporting configuration is still valid, the WTRU may report CSI and / or RSRP reports based on a prior (e.g., the most recently received) indication at step 510. For example, if the most recently received indication for CSI and / or RSRP reporting indicated to transmit CSI and / or RSRP reports in the next DRX active time, the WTRU may transmit respective CSI and / or RSRP reports (e.g., based on the same CSI and / or RSRP report configuration group activated by second LP-WUS). In some implementations if the most recently received indication for CSI and / or RSRP reporting indicated to not to transmit any CSI and / or RSRP reports in the skipped DRX active time, the WTRU may skip transmitting CSI and / or RSRP reports in the next DRX active time. After reporting CSI and / or RSRP reports based on a prior indication at step 510, the WTRU may update and / or otherwise track timeSincelndicationtoTxCSI (or any other suitable time threshold tracking for reporting configuration validity) at 512, and may resume LP-WUS monitoring for first LP-WUS at 502.

[0116] In some implementations, on condition 508 that the WTRU determines that the most recently received indication for CSI and / or RSRP reporting is invalid, the WTRU may receive a new indication for CSI and / or RSRP reporting via second LP-WUS.

[0117] For example, in some implementations, on condition 508 that the WTRU does not have a valid indication for CSI and / or RSRP reporting associated with a skipped DRX active time (e.g., in skipped DRX active time), on condition 514 that the WTRU does not receive a new indication for CSI and / or RSRP reporting via a second LP-WUS the WTRU may determine a CSI and / or RSRP reporting configuration, e.g., based on a default configuration, at 516, and may resume LP-WUS monitoring at 502.

[0118] On condition 514 that the WTRU does receive a new indication for CSI and / or RSRP reporting via a second LP-WUS, the WTRU may monitor for a second LP-WUS at 518.

[0119] In some implementations, the WTRU may determine whether a second LP-WTRU has been received (e.g., at condition 520). On condition 520 that the WTRU does not receive a second LP-WUS, the WTRU may determine a CSI and / or RSRP reporting configuration, e.g., based on a default configuration, at 516 and may resume LP-WUS monitoring at 502 .

[0120] In some implementations, the WTRU may determine whether a second LP-WUS is transmitted for the WTRU or its subgroup and an indication for the WTRU or its subgroup is included in second LP-WUS based on the following steps and / or procedures.

[0121] For example, in some implementations, the WTRU may determine whether the second LP-WUS is transmitted for the WTRU based on one of the following: based on a configuration and or indication received from gNB (e.g., via RRC signaling, SI, MAC-CE indication, DCI indication) and / or based on an indication received in first LP- WUS (for example, in "example configuration-A” based on indication received in (M+1 )th bit of first LP-WUS, the WTRU - 20 -9365181.1IDC-2024P00698WC may determine whether second LP-WUS is transmitted or not, or, for example, if (M+1)th bit is first value (e.g., 0) WTRU determines that second LP-WUS is not transmitted, If (M+1 )th bit is second value (e.g., 1) WTRU determines that second LP-WUS is transmitted).

[0122] In some implementations, the WTRU may determine whether the second LP-WUS includes an indication for the WTRU or its subgroup based on one or more of the following. Based on received indications in first LP-WUS and payload size of second LP-WUS (nSkipMax). For example, in some implementations, a second LP-WUS may include a maximum of nSkipMax bits, each associated with a first (e.g., based on WTRU ID or subgroup ID) nSkipMax WTRUs or subgroups indicated by first LP-WUS to not to wake up. In some implementations, if nSkipMax bits are not enough for all WTRUs or subgroups indicated by the first LP-WUS to not wake up, a configured priority or ID (e.g., local WTRU ID or subgroup ID) number of WTRUs may determine CSI and / or RSRP transmission indication of which WTRUs are included in second LP-WUS. In some implementations, the WTRU may determine whether the second LP-WUS includes an indication for the WTRU or its subgroup based on its WTRU ID, nSkipMax, and the WTRUs indicated to skip the next DRX active time by first LP-WUS.

[0123] For example, in some implementations, e.g., as shown in the configuration depicted in FIG. 4, a bitmapbased per-WTRU wake-up indication is received in a first LP-WUS, and a per-WTRU CSI and / or RSRP reporting indication is received in a second LP-WUS . In this example, M = 8 and a value of (M+1 )th bit = x. In this example, UE(k) is the WTRU with the kth local ID. In this example, based on indications received in the first LP-WUS, UE(1), UE(5), and UE(7) begin monitoring for PDCCHs in the next DRX active time, and UE(0), UE(2), UE(3), UE(4) and UE(6) skip monitoring for PDCCHs. In some implementations, if the timer (e.g., “CSI-Reporting-Application-Timer”) of all WTRUs are expired (e.g., a new indication via second LP-WUS needs to be received), and x = 1 (i.e., a second LP-WUS is transmitted), UE(0), UE(2), UE(3), UE(4) may receive second LP-WUS. UE(6) may not receive second LP-WUS, e.g., because the second LP-WUS does not include an indication for it.

[0124] In some implementations, if the WTRU determines that it does not have a valid indication for CSI and / or RSRP reporting, a second LP-WUS is transmitted, and an indication is included for the WTRU, the WTRU may receive a new indication for CSI and / or RSRP reporting in second LP-WUS.

[0125] In the example procedure 500, on condition 520 that a second LP-WUS is not received, the WTRU may determine a CSI and / or RSRP reporting configuration, e.g., based on a default configuration at 516. Otherwise, on condition 520 that a second LP-WUS is received, on condition 522 that the second LP-WUS indicates to report CSI and / or RSRP measurements, the WTRU may transmit CSI and / or RSRP reports based on a first CSI and / or RSRP reporting configuration group at 524, and the WTRU may update and / or otherwise track timeSincelndicationtoTxCSI (or any other suitable time threshold tracking for reporting configuration validity) at 512, and may resume LP-WUS monitoring for first LP-WUS at 502. Otherwise, on condition 522 that the second LP-WUS does not indicate to report CSI and / or RSRP measurements, the WTRU may resume LP-WUS monitoring at 502.

[0126] For example, in some implementations, if a second LP-WUS includes a 1-bit indication with a first value (e.g., 1) for a WTRU or its subgroup, the WTRU may transmit CSI and / or RSRP reports based on a first CSI and / or RSRP reporting configuration group at 524. In some implementations, the WTRU may transmit any CSI and / or RSRP- 21 -9365181.1IDC-2024P00698WC reports included in skipped DRX active time, e.g., based on first CSI and / or RSRP reporting configuration group. In some implementations, the WTRU may determine the type or types (e.g., CSI only, RSRP only, etc.) For example, in some implementations, if the second LP-WUS indication is applicable for both CSI and RSRP reports associated with first CSI and / or RSRP reporting configuration group, the WTRU may wake-up the MR and transmit both CSI and RSRP reports configured during skipped DRX active time. In an example, in some implementations, if a second LP- WUS includes the 1 -bit indication with a second value (e.g., 0) for a WTRU or its subgroup, WTRU may transmit CSI and / or RSRP reports configured by default CSI and / or RSRP reporting configuration group during skipped DRX active time. For example, in some implementations, if a second LP-WUS indication is applicable for RSRP reporting only, the WTRU may wake up the MR and transmit all RSRP reports configured during skipped DRX active time by default CSI and / or RSRP report configuration group. In another example, in some implementations, if the WTRU does not receive a second LP-WUS, the WTRU may report CSI and / or RSRP reports during skipped DRX active time based on default CSI and / or RSRP report configuration group. For example, in some implementations, if the default CSI and / or RSRP report configuration group includes one or more CSI and / or RSRP reports during skipped DRX inactive time, the WTRU may turn on the MR and transmit respective CSI and / or RSRP reports. If the default CSI and / or RSRP report configuration group does not include CSI and / or RSRP reports during skipped DRX inactive time, the WTRU may continue to monitor for LP-WUS.

[0127] Some implementations provide CSI and / or RSRP reporting based on a duration since the most recently received report.

[0128] The following section is referenced as "part A”. In some implementations, when a WTRU is monitoring for LP-WUS, the WTRU may refrain from transmitting measurement reports or UL reference signals (RSs) (e.g., sounding reference signal (SRS)). For example, in some implementations, the WTRU may not transmit CSI (e.g., CSI except RSRP) reports, and / or RSRP (e.g., L1-RSRP) reports, and / or SRSs while monitoring LP-WUS. In some implementations, not transmitting measurement reports and / or UL RSs while LP-WUS monitoring may make CSI and UL channel measurement available at the gNB, base station, or other network device out of date. Further, in some implementations, the gNB, base station, or other network device, may not be able to support the WTRU for UL synchronization. In some implementations, the impact of not transmitting measurement reports and / or UL RSs while LP-WUS monitoring may be severe during long inactivity periods, which may be expected to be supported via LP- WUS monitoring. Accordingly, it may be desired to provide devices, systems, and / or methods to support transmitting measurement reports and / or UL RSs while monitoring LP-WUS. Accordingly, in some implementations, the WTRU may track the time since it most recently transmitted measurement reports (e.g., CSI (except L1-RSRP) reports, L1- RSRP reports, etc.) and / or channels (e.g., physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH)) and / or UL RSs (e.g., SRS). In some implementations, if the time since the most recently transmitted reports and / or, channels, and / or RSs exceeds respective preconfigured thresholds, the WTRU may transmit one or more measurement reports, and / or channels (e.g., a low payload PUCCH, PUCCH carrying a buffer status report (BSR)), UL RSs (e.g., SRS). To this end, in some implementations, the WTRU may implement one or more of the following solutions and / or procedures.- 22 -9365181.1IDC-2024P00698WC

[0129] For example, some implementations relate to the WTRU receiving a configuration.

[0130] In some implementations, the WTRU may receive one or more of the following configurations and / or indications from the gNB, base station, or other network device (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI): DRX configuration; LP-WUS monitoring configuration; two or more CSI and / or RSRP report configuration groups; two or more SRS configurations; a first set of timers and / or a set of counters; and / or an indication and / or configuration to start monitoring LP-WUS.

[0131] In some implementations, e.g., where the WTRU receives a DRX configuration, the DRX configuration may include one or more of the following: a DRX cycle duration; one or more first set of timers associated with DRX active time (e.g., drx-onDurationTimer, drx-lnactivityTimer, drx-RetransmissionTimerUL, drx-RetransmissionTimerDL) and rx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL; and / or a starting time of a first DRX active time (e.g., drx- SlotOffset) (e.g., a starting time of first drx-onDurationTimer during which WTRU monitoring for PDCCHs.)

[0132] In some implementations, e.g., where the WTRU receives a LP-WUS monitoring configuration, for example, the WTRU may receive a configuration for receiving one or more signals (e.g., LP-WUS, LP-SS) via LR. In some implementations, such configuration may include one or more of the following: LP-WUS occasions (LOs) (e.g., the WTRU may receive offsets for each LO with respect to a starting time of DRX active time; One or more LP-WUS MOs in each LO (e.g., the WTRU may receive a starting time and duration of each LP-WUS MO within LO); and / or LP-SSs (e.g., the WTRU may receive periodicity, a starting point of a first LP-SS or LP-SS burst which consists of multiple LP- SS, and / or a structure of an LP-SS and / or LP-SS burst.

[0133] In some implementations, e.g., where the WTRU receives two or more CSI and / or RSRP report configuration groups (e.g., first CSI-RSRP-ReportConfig group, second CSI-RSRP-ReportConfig group), each group may be associated with one or more CSI (e.g., CSI except RSRP) and / or RSRP report configurations.

[0134] For example, in some implementations, a first CSI-RSRP-ReportConfig group may be associated with transmitting CSI and / or RSRP measurements when MR is activated for monitoring PDCCHs (e.g., PDCCH monitoring during on-duration(s) of a DRX cycle). In some implementations, a second CSI-RSRP-ReportConfig group may be associated with transmitting CSI and / or RSRP measurements when MR is not activated for monitoring PDCCHs (e.g., when skipping on-duration(s) of a DRX cycle (e.g., while WTRU is monitoring LP-WUS)). For example, in some implementations, a second CSI-RSRP-ReportConfig group may be associated with transmitting CSI and / or RSRP reports based on expiration of a timer that tracks the time since most recently transmitted CSI and / or RSRP measurements.

[0135] In another example, in some implementations, instead of two CSI and / or RSRP report configuration groups, the WTRU may be configured with one CSI and / or RSRP report configuration group. In this example, in some implementations, the first CSI-RSRP-ReportConfig group and second CSI-RSRP-ReportConfig group may be referred to as CSI and / or RSRP report configuration groups (first CSI-RSRP-ReportConfig group = second CSI-RSRP- ReportConfig group = CSI-RSRP-ReportConfig group).

[0136] In some implementations, e.g., where the WTRU receives two or more SRS configurations (e.g., first SRS configuration, second SRS configuration), in some implementations, for example, a first SRS configuration may be - 23 -9365181.1IDC-2024P00698WC associated with transmitting SRSs when MR is activated for PDCCH monitoring (e.g., PDCCH monitoring during on- duration of a DRX cycle). In some implementations, a second SRS configuration may be associated with transmitting SRS when MR is not activated for monitoring PDCCHs (e.g., when skipping an on-duration of a DRX cycle (e.g., while WTRU is monitoring LP-WUS)). For example, in some implementations, a second SRS configuration may be associated with transmitting SRSs based on expiration of a timer that tracks the time since most recently transmitted SRS. In another example, in some implementations, instead of two SRS configurations, the WTRU may be configured with one SRS configuration. In this example, in some implementations, the first SRS configuration and second SRS configuration may be referred to as SRS configuration (first SRS configuration = second SRS configuration = SRS configuration).

[0137] In some implementations, e.g., where the WTRU receives a first set of timers and / or a set of counters (e.g., a counter which counts number of DRX cycles, LP-WUS MOs, LOs, etc.,) and / or a set of thresholds for tracking time since most recently transmitted CSI (e.g., CSI excepts RSRP) report and / or RSRP report, and / or most recently transmitted signal or channel out of a preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) set of UL signals (e.g., SRS) and / or channels (e.g., PUCCH, PUSCH etc.), the following may apply. In some implementations, a first set of timers may include a CSI-report-absence-timer. For example, in some implementations, a CSI-report-absence-timer (e.g., frames, DRX cycles, slots, symbols, time (e.g., in units of milliseconds, nanoseconds etc.) may track time since most recently transmitted CSI report. In some implementations, a first set of timers may include a RSRP-report-absence-timer. For example, in some implementations, a RSRP-report-absence-timer (e.g., frames, DRX cycles, slots, symbols, ms, ns and etc.) may track timer since most recently transmitted RSRP report. In some implementations, a first set of timers may include an SRS-absence-timer. For example, in some implementations, an SRS-absence-timer (e.g., frames, DRX cycles, slots, symbols, ms, ns and etc.) may track time since most recently transmitted SRS. In some implementations, a first set of timers may include a UL-Tx-absence- timer. For example, in some implementations, an UL-Tx-absence-timer (e.g., frames, DRX cycles, slots, symbols, ms, ns and etc.) may track the time since most recently transmitted signal or channel out of a preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication) set of UL signals (e.g., SRS) and / or channels (e.g., PUCCH, PUSCH).

[0138] In some implementations, a first set of counters may include one or more of the following. In some implementations, configuration of each counter may include respective maximum value for the counter. In some implementations, a first set of counters may include a CSI-report-absence-counter. For example, in some implementations, a CSI-report-absence-counter may track time instances (e.g., in terms of PUCCH / PUSCH resources (e.g., configured for CSI report), on-durations, DRX cycles, slots, frames, etc.) since most recently transmitted CSI reports. In some implementations, a first set of counters may include an RSRP-report-absence-counter. For example, in some implementations, an RSRP-report-absence-counter may track time instances (e.g., in terms of PUCCH / PUSCH resources (e.g., configured for CSI report), on-durations, DRX cycles, slots, frames etc.) since most recently transmitted RSRP report. In some implementations, a first set of counters may include an SRS-absence- counter. For example, in some implementations, an SRS-absence-counter may track time (e.g., in terms of SRS resources (e.g., configured for SRS transmission, on-durations, DRX cycles, slots, frames etc.) since most recently transmitted SRS. In some implementations, a first set of counters may include an UL-Tx-absence-counter. For - 24 -9365181.1IDC-2024P00698WC example, in some implementations, an UL-Tx-absence-counter may track time (e.g., in terms of configured for SRS transmission, on-durations, DRX cycles, slots, frames etc.) since most recently transmitted signal or channel out of a set of preconfigured (e.g., via one or more of SI, RRC signaling, MAC-CE indication, DCI indication) UL signals (e.g., SRS) and / or channels (e.g., PUCCH, PUSCH).

[0139] In some implementations, a set of thresholds may include one or more of the following: a threshold-CSI- report-absence-time; threshold-RSRP-report-absence-time; threshold-SRS-absence-time; and / or threshold-UL-Tx- absence-time.

[0140] In some implementations, the WTRU may be configured second set of timers. In some implementations, the second set of timers may be implemented for one or more of the following: extending PDCCH monitoring duration; receiving re-transmissions; and / or transmitting acknowledgement for received DL signals and / or channels.

[0141] In some implementations, the WTRU receives an indication and / or configuration to start monitoring LP- WUS. For example, in some implementations, the WTRU may receive an indication (e.g., via one or more of MAC- CE indication, DCI indication, SI, and RRC (e.g., release message)) to start monitoring LP-WUS. In some implementations, based on receiving the configuration and / or indication, the WTRU may begin monitoring LP-WUSs. in some implementations, beginning monitoring LP-WUS may involve one or more of, turning on LR, monitoring for and receiving one or more signals and / or channels via LR (e.g., LP-SS, LP-WUS), not monitoring PDCCHs / POs, turning off MR, placing MR in a sleep state, disabling part of functionality or components of WTRU, and / or etc. In some implementations, the WTRU may reset the first set of timers (CSI-report-absence-timer, RSRP-report-absence- timer, SRS-absence-timer, UL-Tx-absence-timer) and / or the first set of counters (CSI-report-absence-counter, RSRP- report-absence-counter, SRS-absence-counter, UL-Tx-absence-counter) with the start of LP-WUS monitoring.

[0142] For example, in some implementations, the WTRU may begin monitoring for LP-WUS at a (e.g., first) LP- WUS MO and / or LO (e.g., starting from the first symbol of LP-WUS MO or LO) located after a preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication) offset from the time WTRU receives indication and / or configuration for monitoring LP-WUS.

[0143] In another example, in some implementations, the WTRU may start a preconfigured (e.g., via one or more of MAC-CE indication, DCI indication, SI, and RRC release message) timer based on (e.g., after or upon) the WTRU receiving an indication and / or configuration for monitoring for LP-WUS. In some implementations, the WTRU may begin monitoring for LP-WUS from the first LP-WUS MO and / or LO (e.g., first symbol of the LP-WUS MO and / or LO) after timer expires.

[0144] Some implementations relate to a WTRU transmitting measurement reports, RSs, and / or channels based on absence durations.

[0145] For example, in some implementations, a WTRU may keep monitoring LP-WUS while tracking the time since the most recently transmitted signal and / or reports and / or channels of a preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) set of measurement reports (e.g., CSI reports, RSRP reports) and / or channels (e.g., PUCCH, PUSCH), and / or signals (e.g., SRS). For example, in some implementations, the WTRU may keep monitoring LP-WUS while one or more timers (CSI-report-absence-timer, RSRP-report-absence-timer, SRS-absence- - 25 -9365181.1IDC-2024P00698WC timer, UL-Tx-absence-timer) and / or counters (CSI-report-absence-counter, RSRP-report-absence-counter, SRS- absence-counter, UL-Tx-absence-counter) are running.

[0146] In some implementations, if WTRU receives an indication via LP-WUS (e.g., WTRU receives one or more of its ID in LP-WUS, one bit indication mapped to WTRU ID or subgroup ID) to wake up for monitoring PDCCHs (DL scheduling signals and / or channels), prior to one or more timers are expire, or one or more counters reaches their maximum values, WTRU may perform one or more of the following steps and / or procedures.

[0147] In some implementations, the WTRU may turn off LR, stop monitoring LP-WUS, turn on MR and monitor for PDCCHs / POs. Monitoring PDCCHs / POs by MR may be based on a timer. For example, in some implementations, the WTRU may start a preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) timer for monitoring PDCCHs / POs at preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) location(s) in time. In an example, in some implementations, the WTRU may start the next occurrence of drx-onDurationTimer (or a timer associated with PDCCH monitoring during on-duration of a drx cycle) configured by the DRX configuration and monitor for and receive PDCCHs while drx-onDurationTimer is running. In an example, in some implementations, the WTRU may start a preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) timer associated with PDCCH monitoring based on reception of a wake-up indication via a LP-WUS. WTRU may monitor for PDCCHs while the timer is running. In an example, in some implementations, the WTRU may monitor for PDCCHs within a time window located after a preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) offset with respect to the received LP-WUS (e.g., MO(s) and LO(s). For example, in some implementations, a starting point of the time window for PDCCH monitoring may be configured (e.g., via one or more of RRC signaling, MAC-CE indication, DCI indication and SI) with an offset from the received LP-WUS (e.g., from first / last / last+1 symbol of LO(s) and / or MOs where WTRU detected LP-WUS).

[0148] In some implementations, based on PDCCH reception, WTRU may perform one or more of the following. In some implementations, the WTRU may start one or more second set of timers (e.g., one or more of timers related to extending PDCCH monitoring duration (e.g., based on receiving / detecting a PDCCH), timers for receiving retransmissions (e.g., based on transmitted ACK / NACK by the UE), timers for transmitting acknowledgement for received DL signals and / or channels, and etc.) In some implementations, the WTRU may receive one or more signals (e.g., CSI-RSs, synchronization signal blocks (SSBs)) and / or channels (e.g., physical downlink shared channel (PDSCH), PDCCH). In some implementations, the WTRU may transmit one or more signals (e.g., SRS) and / or channels (e.g., PUCCH, PUSCH, physical random access channel (PRACH)).

[0149] In some implementations, the WTRU may transmit one or more CSI (e.g., CSI except RSRP) reports and / or one or more RSRP (e.g., L1-RSRP) reports associated with first CSI-RSRP-ReportConfig group. In an example, in some implementations, if the one or more CSI reports and / or the one or more RSRP reports are configured during the timer activated for PDCCH monitoring (e.g., UL resources for the reports are located during active time by the timer), the WTRU may transmit the one or more CSI and / or the one or more RSRP reports. In an example, in some implementations, If the one or more CSI reports and / or the one or more RSRP reports are configured during the one or more second set of timers, the WTRU may transmit the one or more CSI and / or the one or more RSRP reports. In- 26 -9365181.1IDC-2024P00698WC an example, in some implementations, if transmitting one or more CSI reports and / or one or more RSRP reports are associated with activated PDCCH monitoring window (e.g., UL resources for the reports are located during active time by the monitoring window), the WTRU may transmit the one or more CSI and / or the one or more RSRP reports. In an example, in some implementations, the WTRU may measure one or more RS resources associated with the one or more CSI reports and / or the one or more RSRP reports during one or more of the activated timer for PDCCH monitoring, the one or more of second set of timers, and the activated PDCCH monitoring window.

[0150] In some implementations, a WTRU may transmit one or more SRSs associated with a first SRS configuration. In an example, in some implementations, if one or more SRSs are associated with the timer for PDCCH monitoring (e.g., the one or more SRS resources are configured within the timer), the WTRU may transmit the one or more SRSs. In an example, in some implementations, if one or more SRSs are associated with the one or more second set of timers (e.g., the one or more SRS resources are configured within the one or more second set of timers), the WTRU may transmit the one or more SRSs. In an example, in some implementations, if one or more SRSs are associated with activated PDCCH monitoring window (e.g., the one or more SRS resources are configured within the activated PDCCH monitoring window), the WTRU may transmit the one or more SRSs.

[0151] In some implementations, a WTRU may reset one or more of a first set of timers and / or one or more of a first set of counters, e.g., based on a transmitted one or more measurement reports (e.g., the one or more CSI reports and / or the one or more RSRP reports based on first CSI-RSRP-ReportConfig group), and / or channels (e.g., PUCCH, PUSCH), and / or RSs (e.g., SRS based on first SRS configuration). In an example, in some implementations, the WTRU may reset a CSI-report-absence-timer and / or CSI-report-absence-counter if the WTRU transmitted at least one CSI report. In an example, in some implementations, the WTRU may reset RSRP-report-absence-timer and / or RSRP- report-absence-counter if WTRU transmitted at least one RSRP report. In an example, in some implementations, the WTRU may reset SRS-absence-timer and / or SRS-absence-counter if WTRU transmitted at least one SRS. In an example, in some implementations, the WTRU may reset UL-Tx-absence-timer and / or UL-Tx-absence-counter if WTRU transmitted at least one of the preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication) set of UL signals (e.g., SRS) and / or channels (e.g., PUCCH, PUSCH).

[0152] In some implementations, if one or more timers expire and / or one or more counters reach their maximum values prior to WTRU receive a wake-up indication, the WTRU may transmit CSI and / or RSRP reports based on second CSI-RSRP-ReportConfig group. In an example, in some implementations, if a CSI-report-absence-timer expires or CSI-report-absence-counter reaches its maximum value prior to WTRU receiving a wake-up indication, the WTRU may transmit one or more CSI (e.g., CSI except RSRP) reports based on second CSI-RSRP-ReportConfig group. To this end, the WTRU may first turn on MR and measure one or more resources (e.g., CSI-RSs, SSBs) associated with CSI reports to be transmitted. In some implementations, based on the measurements, the WTRU may transmit one or more CSI reports associated with second CSI-RSRP-ReportConfig group based on one of the following. In an example, in some implementations, the WTRU may report one or more CSI reports on resources configured by second CSI-RSRP-ReportConfig group. In an example, in some implementations, a second CSI-RSRP- ReportConfig group may not include UL resources for transmitting CSI reports, or UL resources (e.g., PUCCH)- 27 -9365181.1IDC-2024P00698WC configured in a second CSI-RSRP-ReportConfig group may be disabled based on a configuration or indication received (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) from gNB. As a result, in some implementations, the WTRU may request (e.g., via a SR) and receive UL resources (e.g., PUSCH resource), e.g., from a gNB, base station, or other network device, for reporting CSI reports. After receiving UL resources, the WTRU may transmit CSI reports configured by second CSI-RSRP-ReportConfig on the received UL resources. In an example, in some implementations, if an RSRP-report-absence-timer expires or RSRP-report-absence-counter reaches its maximum value prior to the WTRU receiving a wake-up indication, the WTRU may transmit one or more RSRP (e.g., L1-RSRP) reports based on second CSI-RSRP-ReportConfig group. To this end, in some implementations, the WTRU may first turn on its MR and measure one or more resources (e.g., CSI-RSs, SSBs) associated with RSRP reports to be transmitted. In some implementations, subsequently, the WTRU may transmit one or more RSRP reports associated with second CSI-RSRP-ReportConfig group based on one of the following. In an example, in some implementations, the WTRU may report one or more RSRP reports on resources configured by second CSI-RSRP-ReportConfig group. In an example, in some implementations, a second CSI-RSRP-ReportConfig group may not include UL resources for transmitting RSRP reports, or UL resources (e.g., PUCCH) configured by second CSI-RSRP-ReportConfig group may be disabled based on a configuration or indication received (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) from gNB. Accordingly, in some implementations, the WTRU may request (e.g., via SR) and / or receive UL resources (e.g., PUSCH resource), e.g., from a gNB, base station, or other network device, for reporting RSRP reports. In some implementations, e.g., after receiving UL resources, the WTRU may transmit RSRP reports configured by second CSI-RSRP-ReportConfig on the received UL resources. In some implementations, if a time since a most recent CSI (e.g., CSI except RSRP) report exceeds a threshold-CSI-report- absence-time prior to the WTRU receiving a wake-up indication, the WTRU may transmit one or more CSI (e.g., CSI except RSRP) reports based on second CSI-RSRP-ReportConfig group. In some implementations, if a time since the most recent RSRP report exceeds a threshold-RSRP-report-absence-time prior to the WTRU receiving a wake-up indication, the WTRU may transmit one or more RSRP (e.g., L1-RSRP) reports based on second CSI-RSRP- ReportConfig group.

[0153] In some implementations, if one or more timers expire and / or one or more counters reach their maximum values prior to the WTRU receiving a wake-up indication, the WTRU may transmit one or more SRSs based on a second SRS configuration and / or may transmit one or more preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication) UL channels (e.g., PUCCH carrying a status report (BSR)). For example, in some implementations, if an SRS-absence-timer expires or an SRS-absence-counter reaches its maximum value prior to a WTRU receiving a wake-up indication, the WTRU may transmit one or more SRS based on a second SRS configuration. For example, in some implementations, if a UL-Tx-absence-timer expires or UL-Tx-absence-timer reaches its maximum value prior to the WTRU receiving a wake-up indication, the WTRU may transmit one or more preconfigured set of UL signals (e.g., SRS configured based on second SRS configuration) and / or channel transmissions (e.g., PUCCH carrying a status report (e.g., buffer status report (BSR)), a low payload PUCCH). For example, in some implementations, if a time since a most recent SRS transmission exceeds threshold-SRS-absence- time prior to the WTRU receiving a wake-up indication, the WTRU may transmit one or more SRS based on second - 28 -9365181.1IDC-2024P00698WCSRS configuration group. For example, in some implementations, if a time since transmission of one or more preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication) set of UL signals (e.g., SRS) and / or channel (e.g., PUCCH, PUSCH) exceeds threshold-UL-Tx-absence-time prior to the WTRU receiving a wake-up indication, the WTRU may transmit one or more preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication) set of UL signal (e.g., SRS configured based on second SRS configuration) and / or channel (e.g., PUCCH carrying a status report (e.g., BSR)).

[0154] In some implementations, a WTRU may reset one or more of a first set of timers and / or one or more of a first set of counters based on a transmitted one or more measurement reports (e.g., the one or more CSI reports and / or the one or more RSRP reports based on second CSI-RSRP-ReportConfig group), and / or channel transmissions (e.g., PUCCH, PUSCH), and / or RSs (e.g., SRS based on second SRS configuration group). For example, in some implementations, the WTRU may reset a CSI-report-absence-timer and / or CSI-report-absence-counter if the WTRU transmitted at least one CSI report. For example, in some implementations, the WTRU may reset a RSRP-report- absence-timer and / or RSRP-report-absence-counter if the WTRU transmitted at least one RSRP report. For example, in some implementations, the WTRU may reset an SRS-absence-timer and / or SRS-absence-counter if the WTRU transmitted at least one SRS. For example, in some implementations, the WTRU may reset an UL-Tx-absence-timer and / or UL-Tx-absence-counter if the WTRU transmitted a preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication) set of UL signals (e.g., SRS) and / or channels (e.g., PUCCH, PUSCH).

[0155] The following section is referenced as "part B”. Some implementations relate to a WTRU receiving a configuration for timer-based reporting.

[0156] In some implementations, a WTRU may receive a CSI measurement and report configuration or update (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI), which may include measurements of various RS, such as based on SSB or CSI-RS. In some implementations, the measurements and / or reports may be configured to prepare and / or report various quantities, such as (L1-)RSRP, received signal strength indicator (RSSI), signal-to- interference-plus-noise ratio (SI NR) values, etc.

[0157] In some implementations, a WTRU may receive a configuration (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) indicating multiple groups of CSI reporting configurations. In some implementations, each group may be associated with one or more measurement reporting configurations. For example, in some implementations, a first group may be indicated in a first CSI-RSRP-ReportConfig-Group indicating the indices of the corresponding reporting configurations, and a second may be indicated in a second CSI-RSRP-ReportConfig-Group. For example, in some implementations, groups may be configured to separate the different types RS measured by the WTRU, e.g., a first CSI-RSRP-ReportConfig-Group group may include the measurements based on SSBs, while a second CSI-RSRP-ReportConfig-Group group may include measurements based on CSI-RS. In some implementations, the type of RS may be indicated in the configuration of the CSI-RSRP-ReportConfig-Group group explicitly instead of indicating the indices of the different report configuration. For example, in some implementations, groups may be configured to separate the different reporting quantities measured by the WTRU. For example, in some implementations a first CSI-RSRP-ReportConfig-Group group may include the measurements reporting L1-RSRP,- 29 -9365181.1IDC-2024P00698WC while a second CSI-RSRP-ReportConfig-Group group may include measurements reporting other quantities. In some implementations the type of quantity may be indicated in the configuration of the CSI-RSRP-ReportConfig-Group group explicitly or implicitly instead of indicating the indices of the different report configuration. For example, in some implementations, the groups may also separate measurements for the WTRU's cell and mobility measurements, from other neighboring cells. For example, in some implementations, the WTRU may combine more that one of the previously indicated examples.

[0158] In some implementations, a WTRU may receive a configuration (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) including multiple UL transmissions configuration, such as an SRS (e.g., including SRS resources, SRS resources sets), a phase tracking reference signal (PTRS), or other UL transmission channels (e.g., PUCCH, PUSCH). In one example, in some implementations, the WTRU receives an RRC configuration including two SRS resources sets (including one or more SRS resources each) for transmissions. In some implementations, the SRS resources or resource sets may be indicated to be used for synchronization usage.

[0159] In some implementations, a WTRU may receive a configuration (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) including multiple sets of timers (e.g., CSI-report-absence-timer, UL-Tx-absence-timer) and / or multiple sets of counters (e.g. CSI-report-absence-counter, UL-Tx-absence-counter) for tracking time since transmitting the most recent CSI report (e.g., CSI reporting excepts L1-RSRP), and / or L1-RSRP report, and / or transmitting at least one out of preconfigured set of UL signals / channels (e.g., SRS, SR, PUCCH, PUSCH etc.).

[0160] In an example, in some implementations, a first CSI-report-absence-timer may be associated with a first group of CSI-RSRP-ReportConfig-Group, and / or a second CSI-report-absence-timer may be associated with a second group of CSI-RSRP-ReportConfig-Group. In an example, in some implementations, a first UL-Tx-absence-timer, may be associated with one or more type of UL signal / channel transmission, e.g., SRS, PTRS, UL demodulation reference signal (DMRS) transmissions, and further associated with a one or more of the received multiple UL transmission configuration, e.g., a first SRS resource set; and a second type of UL-Tx-absence-timer, may be associated with one or more UL signal / channel transmission, e.g., SR, PUSCH, PUCCH, etc. and further associated with a one or more of the received multiple UL transmission configuration, e.g., a second SRS resource set. In an example, in some implementations, a first CSI-report-absence-counter may be associated with a first group of CSI-RSRP-ReportConfig- Group, and a second CSI-report-absence-counter may be associated with a second group of CSI-RSRP- ReportConfig-Group. In an example, in some implementations, a first UL-Tx-absence-counter, may be associated with one or more type of UL signal / channel transmission, e.g., SRS, PTRS, UL DMRS transmissions, and further associated with a one or more of the received multiple UL transmission configuration, e.g., a first SRS resource set; and a second type of UL-Tx-absence-counter, may be associated with one or more UL signal / channel transmission, e.g., SR, PUSCH, PUCCH, etc. and further associated with a one or more of the received multiple UL transmission configuration, e.g., a second SRS resource set. In an example, in some implementations, a set of timers / counters may be associated with reporting configuration or reporting configuration groups that correspond to L1-RSRP measurements. In one example, when the CSI-report-absence-timer, UL-Tx-absence-timer, CSI-report-absence- counter and UL-Tx-absence-counter are associated with a CSI-RSRP-ReportConfig-Group for L1-RSRP- 30 -9365181.1IDC-2024P00698WC measurements. In another example, an additional set of timers / counter dedicated to L1-RSRP measurements and reports may be configured, e.g., RSRP-report-absence-timer and RSRP-report-absence-counter. In an example, in some implementations, Two sets of timers / counters may be associated to a single reporting configuration or reporting configuration group. In one example, the first set of timer / counter is configured with a longer timer / threshold and the second set with shorter time / threshold. In some example, the counters may be configured or preconfigured to count a number of DRX cycles, LP-WUS MOs, slots, symbols, CSI report occasions, SSB, transmissions, etc. In an example, in some implementations, the WTRU may receive one or more of the previous configuration in a first signaling and be indicated to activate such configuration, or any subset of the configuration via another signaling. In one example, the WTRU may receive the first indication via RRC configuration or reconfiguration, and the second via a RRC Release message.

[0161] Some implementations include For example, in some implementations, a WTRU resetting timers and counters on activation of LP-WUS monitoring.

[0162] In some implementations, a WTRU may receive configuration and / or indication (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) to start monitoring LP-WUS. For an example, WTRU may receive RRC release message indicating to activate LP-WUS monitoring.

[0163] In some implementations, the WTRU may enter a main radio-off (MR-OFF) mode (e.g., for monitoring LP- WUS while WTRU is in RRC IDLE or RRC INACTIVE or RRC CONNECTED state). For example, in some implementations, the WTRU may enter MR-OFF mode a preconfigured (e.g., via RRC signaling, MAC-CE indication, DCI indication, SI) time offset from receiving RRC release message or after receiving configuration for LP-WUS monitoring.

[0164] Based on activating the LP-WUS monitoring, in some implementations, the WTRU may reset the sets of timers, and reset the sets of counters configured previously. For example, in some implementations, the RRC release message may include an indication or configuration for activating the timers and / or counters and / or may indicate a time / delay after which to reset the timers. For example, in some implementations, the timers may be reset and / or restarted when the WTRU is entering the LP-WUS monitoring mode. For example, in some implementations, the timers may be reset and / or restarted when the WTRU receives the indication of activation (or the indication triggering the activation) of the LP-WUS monitoring.

[0165] Some implementations include a WTRU transmitting CSI reports and / or UL signals or channel transmissions based on timers and / or counters.

[0166] In some implementations, a WTRU, when monitoring for LP-WUS, may be triggered to transmit a measurement report and / or a RS transmission, based on it not having performed such transmissions for a configured duration, for example, based on the expiration of the timers or after reaching the counter limit values. For example, in some implementations, the WTRU may receive an indication from the network to wake up its MR, e.g., by receiving a LP-WUS for monitoring PDCCH, and the WTRU wakes its MR.

[0167] In some implementations, during the DRX active duration, for a WTRU configured with reporting group or groups with at least a set of timer / counter, the WTRU may for example: transmit a group of measurement reports, - 31 -9365181.1transmit an SRS, and / or transmit UL signals / channels. For example, in some implementations, the WTRU may transmit a group of measurement reports if the measurement report group is associated with the ongoing DRX active time; e.g., the reporting configuration includes resources in this DRX active time, and if the timer associated with the group has expired or if the counter associated with that group reached the threshold. In some implementations, the WTRU resets and restarts the timers / counters associated with the transmission of these measurement report and / or associated with a UL transmission of type measurement report. In some implementations, the WTRU may transmit an SRS if the SRS is associated with the ongoing DRX active time, e.g., the configured SRS resource include resources in this DRX active time, and if the timer associated with the SRS transmission expired or if the counter associated with that group reached the threshold. In some implementations, the WTRU resets and restarts the timers / counters associated with this SRS transmission and / or associated with a UL transmission of type SRS. In some implementations, the WTRU may transmit UL signals / channels, e.g., SRS, PUCCH, PUSCH, etc. based on the received indication from the LP-WUS and / or from a received indication in the monitored PDCCH. In this case, in some implementations, the WTRU resets / restarts the timers and / or counters associated with such transmission (e.g., either by type of transmission or transmission itself). For instance, in some implementations, if the WTRU transmits an HARQ feedback, the WTRU resets the UL-TX-absence-timer timers.

[0168] A WTRU may be configured with one or more reporting group and two sets of timers and / or counters; e.g., a first set with a longer duration and a second set with a shorter duration. Typically, this may be set such that a first duration is a "normal” or regular duration of the timer, whereas the second duration is a duration for which the WTRU may trigger a report before the normal duration (which may be referred to as an "anticipating” duration). In some implementations, the WTRU may transmit a group of measurement reports and / or an SRS associated with a second set of timers and / or counters that have expired and / or reached a threshold, for which the WTRU is configured with reporting resources in that DRX active duration. In some implementations, the WTRU resets both first and second set of timers and / or counters corresponding to that measurement reporting group or SRS transmission. In some implementations, the WTRU further resets and / or restarts any timer and / or counter associated with the corresponding transmission or transmission type.

[0169] In some implementations, this may be beneficial, e.g., in cases where the WTRU wakes up its MR, but "regular” measurement reporting or SRS transmission is intended slightly after the DRX active duration, which in some implementations, may let the WTRU wake up once again in a near future, consuming energy. Here, in some implementations, the WTRU uses an early (e.g., triggered and / or commanded) DRX active duration to report the measurement in anticipation, and in some implementations, resets both timers such that the next report follows a "regular” duration.

[0170] In another option, in some implementations, where WTRU did not receive an indication from the network to wake up the MR, skipping the incoming DRX active time, the WTRU may determine whether to wake up its MR and transmit the measurement report and / or SRS transmission based on the timers and / or counters associated with the different reporting groups or SRS configurations.- 32 -9365181.1

[0171] For example, in some implementations, a WTRU configured with different reporting groups and / or SRS transmissions associated with different sets of timers and / or counters may wake up its MR and perform the transmission (e.g., measurement report or SRS) based on the associated timer and / or counter expiring and / or passing a threshold, and in some implementations, the corresponding transmission resources are included in the DRX active duration that was indicated to be skipped.

[0172] For example, in some implementations, the WTRU may resets and / or restarts the timers and / or counters associated to the corresponding transmissions.

[0173] For example, in some implementations, a WTRU configured with a reporting group configuration and / or SRS transmission configuration associated with two sets of timers / counters may wake up its MR and transmit the measurement reporting and / or SRS transmission associated with the second set of timers and / or counters if the second set of timer expired and / or reached threshold, and if the transmission resources associated with that report and / or SRS are included in the DRX active duration that is indicated to be skipped. For example, in some implementations, when the second set of timers and / or counters has a duration longer than the first set. In some implementations, the benefit may be that the WTRU may be configured to allow some margin for transmissions, and may wait for a triggered active DRX duration before "forcing” wake-up of the MR.

[0174] For example, in some implementations, a WTRU configured with a reporting group configuration and / or SRS transmission configuration associated with two sets of timers and / or counters may, after the transmission, reset and / or restart the two sets of timers and / or counters for the given transmission, e.g., so that the regular timing may be restored. In some implementations, the WTRU may also reset and / or restart timers and / or counters associated with any UL transmission or with the type of transmission performed.

[0175] Some implementations provide CSI and / or RSRP reporting based on different types of LP-WUSs.

[0176] In some implementations, a WTRU may be configured with and / or receive an indication of one or more types of signaling, where the WTRU may determine the mode of operation based on the type of received signaling. In some implementations, the WTRU may be configured with and / or receive an indication of one or more LP-WUS monitoring occasions (MO), e.g., based on which the WTRU may monitor to receiver and / or detect LP-WUS. For example, in some implementations, the WTRU may be configured with one or more types of LP-WUS. In an example, in some implementations, the WTRU may be configured with a first type of LP-WUS, a second type of LP-WUS, and so forth. In an example, in some implementations, the WTRU may determine to operate based on a first mode of operation if the WTRU receives a first type LP-WUS, the WTRU may determine to operate based on a second mode of operation if the WTRU receives a second type LP-WUS, and so forth. In an example, in some implementations, different types of LP-WUS may include one or more sets of wake-up configuration information and / or indications. For example, in some implementations a first type LP-WUS may include one or more first sets of wake-up configuration and / or indications, a second type LP-WUS may include one or more second sets of wake-up configuration and / or indications, and so forth. In an example, in some implementations the first and second sets of wake-up configuration and / or indications may include different, the same, or similar content.- 33 -9365181.1

[0177] Some implementations relate to configurations. For example, in some implementations, a WTRU may receive, be configured with, and / or receive an indication of one or more configuration information and / or indications on different types of LP-WUS. For example, in some implementations, the WTRU may receive the configuration information, for example from a gNB, base station, and / or other network device, for example via system information block (SIB), RRC, MAC-CE, DCI, etc. In some implementations the configuration information may include but is not limited to one or more of the following: types of LP-WUS, MOs, associated codepoints, and / or CSI report configurations.

[0178] In implementations, e.g., where the configuration information relates to types of LP-WUS, for example, a WTRU may receive one or more configuration information and / or indications of the number of LP-WUS types. In an example, in some implementations, the WTRU may be configured or preconfigured and / or indicated or pre-indicated on the information and the potential modes of operation associated with each of the configured types of LP-WUS. For example, in some implementations, the configuration information in first type of LP-WUS may include a wake-up indication, whereas the configuration information in the second type of LP-WUS may include a wake-up indication and / or one or more indications for one or more CSI reporting occasions.

[0179] In implementations where the configuration information relates Monitoring Occasions (MO), for example, a WTRU may receive, be configured, and / or receive an indication of one or more LP-WUS MOs. In an example, in some implementations, the WTRU may receive, be configured, and / or receive an indication of time and / or frequency resources, periodicity, total number of MOs, etc. for one or more MOs. In some implementations, the WTRU may receive the indications on the time and / or frequency resources for one or more MOs, for example based an explicit indication and / or an implicit indication.

[0180] In some implementations, e.g., where the WTRU receives the indications on the time and / or frequency resources for one or more MOs, based an explicit Indication, the WTRU may receive the indications on the time and / or frequency resources for one or more MOs, based a separate indication, time offset with regard to configured DRX cycle, and / or time offset with regard to a paging frame. For a separate indication, for example, in some implementations, the WTRU may receive, be configured, and / or indicated with one or more MO time and / or frequency resources, MO periodicity, etc. For a time offset with regard to configured DRX cycle, in some implementations, for example, the MOs may be configured based on DRX configurations. For example, in some implementations, the WTRU may be configured and / or indicated with one or more MOs in DRX active and / or inactive time. For example, in some implementations, the WTRU may receive, be configured, and / or indicated with the time offset with regards to the configured DRX active time as the time resources for one or more configured MOs. For example, in some implementations, the indicated and / or configured time offset may be before or after a configured DRX active time. In another example, in some implementations, the indicated and / or configured time offset may be in the middle of a configured DRX inactive time. For a time offset with regard to paging frame, in some implementations, for example, in some implementations, the WTRU may receive frame offset for LP-WUS. For example, in some implementations, the WTRU may receive offset from the start of a reference frame for LP-WUS (e.g., the start of a frame) to the start of a first paging frame of the paging frames associated with LP-WUS monitoring for the WTRU. Based on the first paging- 34 -9365181.1frame, in some implementations, the WTRU may receive a symbol offset to a LP-WUS occasion. For example, in some implementations, the WTRU may receive symbol offset for LP-WUS. For example, in some implementations, the WTRU may receive or receive an indication of an offset (e.g., in number of symbols) from the start of the frame to the start of the first LP-WUS occasion.

[0181] In some implementations, e.g., where the WTRU receives the indications on the time and / or frequency resources for one or more MOs, based an implicit indication, for example, in some implementations, in case of absence of configured time and frequency resources for the configured MOs, the WTRU (e.g., implicitly) may determine to use one or more default and / or configured / preconfigured configurations and / or indications for the configured MOs. In an example, in some implementations, the default and / or configured / preconfigured time resources may be with regard to a reference time instance (e.g., symbol, slot, frame, etc.). For example, in some implementations, the reference time may be with regard to Frame 0, etc. In another example, in some implementations, the default and / or configured / preconfigured frequency resources may be with regards to a reference frequency. For example, in some implementations, the reference frequency may be with respect to the lowest physical resource block (PRB) and / or middle PRB within the associated PRBs, configured CC (Component Carrier), and / or BWP (e.g., initial BWP, active BWP, etc.).

[0182] In some implementations, a WTRU may be configured with and / or receive an indication of one or more LP- WUS MOs for monitoring different types of LP-WUS. In an example, in some implementations, the WTRU may be configured with and / or receive an indication to monitor a common set of MOs for detecting and / or receiving different types of LP-WUS. In another example, in some implementations, the WTRU may be configured with and / or receive an indication to monitor a first set of configured MOs for detecting and / or receiving a first type of LP-WUS, the WTRU may be configured with and / or receive an indication to monitor a second set of configured MOs for detecting and / or receiving a second type of LP-WUS, and so forth.

[0183] In implementations where the configuration information relates associated codepoints, for example, a WTRU may be configured with and / or receive an indication of one or more codepoints that may be associated with configured different types of LP-WUS. For example, in some implementations, the WTRU may be configured with and / or receive an indication of a first set of codepoints associated with a first type of LP-WUS, and the WTRU may be configured with and / or receive an indication of a second set of codepoints associated with a second type of LP-WUS, and so forth.

[0184] In an example, in some implementations, the LP-WUS may be based on ON-OFF Keying (OOK) signaling. Alternatively, in some implementations, an overlaid sequence may be applied on top of the OOK symbols in LP-WUS systems. In some implementations, the overlaid OFDM sequences may carry information for the WTRUs whose LP- WUR is capable to detect OFDM sequences.

[0185] In an example, in some implementations, the WTRU may be configured with and / or receive an indication of one or more (e.g., overlaid) sequences that may be transmitted via LP-WUS, wherein the different sequences may be associated with different types of LP-WUS. For example, in some implementations, the WTRU may be configured- 35 -9365181.1with a first set of sequences associated with a first type of LP-WUS, the WTRU may be configured with a second set of sequences associated with a second type of LP-WUS, and so forth.

[0186] Some implementations relate to CSI Report Configurations.

[0187] For example, in some implementations, a second type LP-WUS may include one or more indications and / or configuration information regarding one or more CSI reporting occasions. In an example, in some implementations, the WTRU may receive an indication to a CSI reporting candidate configuration or pre-configuration, e.g., where the WTRU may have received the configured or pre-configured CSI reporting configuration information, for example via semi-static configurations, e.g., via one or more of SI, MAC CE and RRC. In some implementations, the WTRU may receive the index and / or codepoint associated to the configured or pre-configured CSI reporting configurations via a detected and / or received LP-WUS. As such, in some implementations, the WTRU may use the indication received via LP-WUS to use and / or apply the (pre)configured CSI reporting (e.g., indicated via the LP-WUS). For example, in some implementations, the index to the CSI reporting configurations may be included in a second type LP-WUS.

[0188] Some implementations relate to determining the type of a received LP-WUS. In some implementations, a WTRU may determine the type (e.g., first type, or second type) of a received LP-WUSs based on one or more received indications. For example, in some implementations, after monitoring, detecting, and / or receiving a first LP-WUS, the WTRU may determine whether the first LP-WUS is of a first type LP-WUS, a second type LP-WUS, and so forth. For example, in some implementations, the WTRU may receive the indications on the type of the LP-WUS based on an explicit indication and / or an implicit indication.

[0189] In some implementations where the WTRU receives the indications on the type of the LP-WUS based on an explicit indication, the WTRU may receive a flag indication and / or a codepoint and / or sequences.

[0190] In some implementations where the WTRU receives a flag indication, for example, the WTRU may receive one or more indications via received and / or detected LP-WUS, for example as part of LP-WUS payload. For example, in some implementations, the WTRU may receive a flag indication, e.g., where a first value (e.g., value zero) may indicate the LP-WUS to be a first type LP-WUS; a second value (e.g., value one) may indicate the LP-WUS to be a second type LP-WUS, and so forth.

[0191] In some implementations where the WTRU receives a codepoint and / or sequences, for example, the WTRU may determine the type of the detected and / or received LP-WUS based on the codepoint associated with the received LP-WUS. For example, in some implementations, the WTRU may determine the type of the detected and / or received LP-WUS based on the (e.g., overlaid) sequence associated with the received LP-WUS. For example, in some implementations, if the WTRU receives a first codepoint and / or a first (e.g., overlaid) sequence via LP-WUS, the WTRU may determine that the received LP-WUS is of a first type; if the WTRU receives a second codepoint and / or a second (e.g., overlaid) sequence via LP-WUS, the WTRU may determine that the received LP-WUS is of a second type.

[0192] In some implementations where the WTRU receives the indications on the type of the LP-WUS based on an implicit indication, the WTRU may receive a sequential Tx of LP-WUS types, and / or MOs where LP-WUS was received, and / or time offset since most recent LP-WUS reception.- 36 -9365181.1

[0193] In some implementations where the WTRU receives a sequential Tx of LP-WUS types, for example, the WTRU may be configured with and / or receive an indication that different types of LP-WUS may be transmitted based on a periodicity. For example, in some implementations, the WTRU may be configured to receive a first type LP-WUS based on a first periodicity, a second type LP-WUS based on a second periodicity, and so forth. For example, in some implementations, the WTRU may be configured to expect to receive a specific type of LP-WUS unless indicated otherwise. That is, in some implementations, the WTRU may expect to receive a first type LP-WUS at each configured MO, where the WTRU may be configured and / or indicated with one or more MOs to monitor to receive second type LP-WUS. For example, in some implementations, the WTRU may be configured with a periodicity to receive the second type LP-WUS. For example, in some implementations, the WTRU may be configured and / or indicated that different types of LP-WUS may be transmitted sequentially. As such, after successful reception of a first LP-WUS with a first type, in some implementations, the WTRU may expect to receive a second LP-WUS with a second type, for example in the next configured MO. For example, in some implementations, the WTRU may determine the successful LP-WUS reception based on cyclic redundancy check (ORC), sequence detection, etc., e.g., received in configured (e.g., common) resources for monitoring LP-WUS.

[0194] In some implementations where the WTRU receives MOs where LP-WUS was received, for example, in some implementations, the WTRU may determine the type of the detected and / or received LP-WUS based on the MO where the LP-WUS was detected and / or received. For example, in some implementations, if the WTRU receives a first LP-WUS in a first MO, the WTRU may determine that the received LP-WUS is of a first type; if the WTRU receives a second LP-WUS in a second MO, the WTRU may determine that the received LP-WUS is of a second type.

[0195] In some implementations where the WTRU receives a time offset since the most recent LP-WUS reception, for example, the WTRU may determine the time duration since the most recent reception of an LP-WUS with a second type (e.g., CSI-absence-time). In case the determined time duration is longer than a threshold, in some implementations, the WTRU may determine that the next LP-WUS may be a second type LP-WUS.

[0196] Some implementations relate to modes of operation. For example, in some implementations, a WTRU may determine the mode of operation (e.g., on WTRU operation after receiving the LP-WUS) based on the type of the received LP-WUS, where the WTRU may operate based on the first mode of operation if a first type LP-WUS is received, the WTRU may operate based on the second mode of operation if a second type LP-WUS is received, and so forth. For example, in some implementations, in the first mode of operation, the WTRU may wake up MR upon reception of a first type LP-WUS. For example, in some implementations, in the second mode of operation, the WTRU may wake up MR and transmit one or more reports upon reception of a second type LP-WUS. For example, in some implementations, the WTRU may transmit one or more CSI reports.

[0197] In some implementations, a WTRU may determine on whether to wake up MR and whether to transmit reports based on one or more indications received from a received and / or detected LP-WUS. One or more of the following may apply.

[0198] In some implementations, the WTRU determines that a first type LP-WUS is received. In some such cases, the WTRU may determine whether to wake up MR based on one or more received indications. For example, in some- 37 -9365181.1IDC-2024P00698WC implementations, the WTRU may receive a bitmap indication via received LP-WUS with per WTRU or per subgroup based wake-up indication, where each bit may be associated with one or more WTRU IDs and / or subgroup IDs. For example, in some implementations, in case of bitmap indication, if the WTRU receives a first value (e.g., value one) in a first bit, associated with a first WTRU ID or a first subgroup ID, the WTRU may determine to wake up the MR. For example, in some implementations, in case the WTRU receives a second value (e.g., value zero) in a second bit, associated with a second WTRU ID or a second subgroup ID, the WTRU may determine to skip DRX active time, for example to skip monitoring PDCCH.

[0199] For example, in some implementations, the WTRU determines to wake up its MR and monitor to receive PDCCH. In some such cases the WTRU may receive one or more indications and / or configuration information on one or more CSI reports. For example, in some implementations, in case the WTRU determines to not wake up the MR and to not monitor PDCCH and to skip monitoring PDCCH, the WTRU may transmit one or more CSI reports based on configured or pre-configured and / or indicated or pre-indicated configuration for CSI reporting in skipped DRX active times. As such, in case the configured or pre-configured and / or indicated or pre-indicated configuration for CSI reporting in skipped DRX active times indicates to transmit CSI reports, the WTRU may transmit corresponding CSI reports. Otherwise, in case the configured or pre-configured and / or indicated or pre-indicated configuration indicated not transmitting CSI reporting in skipped DRX active times, the WTRU may not transmit CSI reports.

[0200] In some implementations, if the WTRU determines that a second type LP-WUS is received, the WTRU may determine whether to wake up its MR and transmit CSI reporting based on one or more received indications. For example, in some implementations the WTRU may receive a bitmap indication via received LP-WUS with per WTRU or per subgroup based wake-up indication, where two-bits indications may be associated with one or more WTRU IDs and / or subgroup IDs. In case of bitmap indication with two-bits in, in some implementations, in some implementations, a first bit may indicate whether to wake up MR or not, whereas the second bit may indicate whether to send CSI reporting or not. As such, in an example, in some implementations, if the WTRU receives a first value (e.g., value one) or a second value (e.g., value zero) in a first bit out of a first two-bit indication associated with a first WTRU ID or a first subgroup ID, the WTRU may determine to wake up or not to wake up the MR, respectively. For example, in some implementations, if the WTRU receives a first value (e.g., value one) or a second value (e.g., value zero) in a second bit out of a first two-bit indication associated with a first WTRU ID or a first subgroup ID, the WTRU may determine to transmit or not to transmit CSI reporting, respectively.

[0201] Some implementations provide CSI and RSRP reporting, and SRS transmissions based on detection of events. Some implementations relate to the evaluation of measurement results. In some implementations, the WTRU may be configured with one or more measurement event criteria to evaluate based on LR measurements. In some implementations, if the WTRU enables LR monitoring (and may turn off or reduce MR monitoring) the WTRU performs measurements based on reception of the LR reference signals (e.g. performs RSRP measurement) and evaluates based on a configured criteria or trigger condition.

[0202] In some implementations, a measurement event trigger may be based on one or more of the following: time, (e.g., absolute or relative time measured time at the WTRU, system frame number (SFN), and / or subframe- 38 -9365181.1IDC-2024P00698WQ number, etc.); radio quality measurement or predicted radio quality one or more of the serving cells or target cells (e.g., RSRP (beam or cell), RSRQ (beam or cell), cri-RI-PMI-CQI, cri-RI-i1 , cri-RI-i1-CQI, cri-RI-CQI, cri-RSRP, ssb- Index-RSRP, and / or cri-RI-LI-PMI-CQI); position (e.g., an area (e.g. defined by reference point and radius) or range of co-ordinates, and / or a distance threshold from a reference location); an L3 measurement event (e.g., event A1 (e.g., serving becomes better than threshold), event A2 (e.g., serving becomes worse than threshold), event A3 (e.g., neighbor becomes offset better than SpCell), event A4 (e.g., neighbor becomes better than threshold), event A5 (e.g., SpCell becomes worse than thresholdl and neighbor becomes better than threshold2), event A6 (e.g., neighbour becomes offset better than SCell), event B1 (e.g., inter RAT neighbour becomes better than threshold), and / or an event B2 (e.g., PCell becomes worse than thresholdl and inter RAT neighbor becomes better than threshold2); an L1 measurement event or condition (e.g., any event defined which utilizes L1 beam measurements to evaluate whether a criteria or condition is met, such as lower layer triggered mobility LTM and / or MIMO BM. LTM may include, e.g., event LTM1 : Beam of serving cell becomes better than absolute threshold; event LTM2: Beam of serving cell becomes worse than absolute threshold; event LTM3: Beam of candidate cell becomes amount of offset better than beam of serving cell; event LTM4: Beam of candidate cell becomes better than absolute threshold; and / or event LTM5: Beam of serving cell becomes worse than absolute thresholdl AND Beam of candidate cell becomes better than another absolute threshold2. MIMO BM may include, e.g., event-1 : Quality of the current beam is worse than a certain threshold, event-2 (Quality of at least one new beam, such as L1-RSRP, becomes a threshold value better than the current beam.) event-7a: Quality of at least one new beam, such as L1-RSRP, becomes a threshold value better than the RS derived from the activated transmission configuration indicator (TCI) state with the worst quality. event-7b: Quality of at least one new beam, such as L1-RSRP, becomes a threshold value better than the RS derived from the activated TCI state with the best quality). Any time or location based condition (e.g., time measured at WTRU is within a duration from threshold, distance between WTRU and referenceLocationl is above thresholdl and distance between WTRU and referencel_ocation2 is below threshold2, and / or distance between WTRU and the serving cell moving reference location is above thresholdl and distance between WTRU and a moving reference location is below threshold2); and / or any combination of L3, L1 , time, location-based conditions or events (e.g., time measured at WTRU is within a duration from threshold AND Beam of candidate cell becomes better than absolute threshold, and so on; distance between WTRU and referenceLocationl is above thresholdl and distance between WTRU and referenceLocation2 is below threshold2 AND Beam of candidate cell becomes amount of offset better than beam of serving cell; and / or distance between WTRU and the serving cell moving reference location is above thresholdl and distance between WTRU and a moving reference location is below threshold2 AND Beam of serving cell becomes worse than absolute thresholdl AND Beam of candidate cell becomes better than another absolute threshold2).

[0203] Some implementations relate to scheduling request and report transmission. In some implementations, the WTRU may be configured to transmit a report of the one or more measurement event criteria being met. In some implementations, the report may be transmitted using one or more of an RRC message (e.g. a measurement report), a MAC CE (e.g. similar to LTM L1 measurement report) and a UCI (e.g. similar to beam management report, or as part of CSI report (e.g., via PUCCH and / or PUSCH)).- 39 -9365181.1IDC-2024P00698WC

[0204] In some implementations, in order to transmit such report, in the current system, when a WTRU has some uplink data to transmit (including when a MAC CE is available for transmission), the WTRU may transmit the uplink data on PUSCH if the WTRU has enough available uplink grant (e.g., enough granted resources on PUSCH). In some implementations, if there is not enough grant to transmit all of the pending uplink data, the WTRU transmits according to the priority of the data (for example, MAC CE usually has higher priority than other user data). In some implementations, the WTRU does not have sufficient uplink grant, the WTRU transmits a BSR to indicate the amount of data available for transmission, to request more grant. In some implementations, the WTRU does not have sufficient (e.g., has none) grant to transmit even a BSR, the WTRU first transmits a scheduling request (SR) to obtain a grant for transmitting the BSR.

[0205] In some implementations, if the WTRU does not have sufficient grant to transmit an event triggered measurement report (e.g., as may be the case if WTRU has been monitoring the LP-WUS because no scheduling has been received on PDCCH using the MR due to the WTRU not monitoring PDCCH using the MR), then using the existing mechanism of sending SR and BSR may in some implementations risk delaying the handover or scheduling decision based on the report because the WTRU must switch on the MR in order to receive scheduling after transmission of an SR and BSR. However, In some implementations, for MIMO beam management, a new mechanism may provide low latency. In some implementations, while MAC CE offers the advantage of flexibility (e.g., MAC CE can be of varying size, allowing different report lengths depending on the available measurement results) and reliability (MAC CE is transmitted on PUSCH using hybrid automatic repeat request (HARQ)), use of UCI offers a latency advantage in the case of not enough uplink grant for PUSCH.

[0206] In one example, in some implementations, the WTRU may transmit an indication using PUCCH that one or more LR events have been triggered. This indication may be carried as part of a scheduling request, as an indication that the scheduling request is for transmission of a high priority mobility report, which would avoid the need to additionally send a BSR.

[0207] In some implementations, in cases where LR based measurement events are configured, then PUCCH resources may also be configured for transmission of event reports. Some implementations include two modes of transmission of beam management reports, and in some implementations the network would configure which of the modes would be in use for a given event. In some implementations, for transmission of a LR based event, several options may be possible.

[0208] A first example is referred to as "mode A”. In step 1 of mode A, in some implementations, the WTRU may transmit one or more bits to indicate that an LR measurement event criteria has been met, in a first PUCCH channel to request a resource for a second UL channel to carry a measurement report based on the MR. In some implementations, the one or more bits may indicate an event ID. In some implementations, the one or more bits may be encoded in a new UCI format, or in one of the existing formats such as SR or CSI. In some implementations, the one or more bits may occur in different SR / UCI resources. For example, a resource may be reserved for different types of event. In some implementations, the one or more bits may be used to indicate whether the WTRU has subsequent information to transmit in a MAC CE or in a UCI format. In some implementations, the one or more bits may simply- 40 -9365181.1IDC-2024P00698WC indicate that the WTRU has some more information to transmit in a second UL channel, without explicitly indicating this is a LR event.

[0209] In step 2 of mode A, in some implementations, the DCI format comprises an UL-grant DCI format, and the second channel in Step-3 may be PUSCH or PUCCH. In some implementations, the UL-grant DCI format may comprise of DCI format 0_1 / 0_2 and the second channel may be PUSCH. In some implementations, the UL-grant DCI format may comprise of DL-grant DCI format, and the second channel in Step-3 is PUCCH. In some implementations, the network may, in response to WTRU indicating an LR event has occurred in step 1 , schedule PUSCH resources for transmission of a MAC CE.

[0210] In step 3 of mode A, in some implementations, the WTRU may transmit additional information, for example, in some implementations, the WTRU may transmit one or more bits in the second UL channel (which could be PUSCH or another PUCCH resource) to indicate the occurrence of a LR event- e.g. one bit to indicate a LR event, or more than one bit to identify the event which has been triggered. In some implementations, the WTRU may transmit MR measurement results, for example RSRP of serving and / or candidate beams on other cells. In some implementations, the WTRU may transmit one or more event IDs corresponding to LR and / or MR events. In some implementations, the WTRU may transmit an indication of the size of MAC CE that needs to be transmitted. This may be explicit (E.g. number of bits or bytes) or may be implicit (e.g. indication of MAC CE format ID, or event ID). In some implementations, the WTRU may transmit a MAC CE in this step, if it has indicated a LR event in step 1 or if the network explicitly schedules a PUSCH resource in step 2. In some implementations, in response to the WTRU indicating that a LR event has been triggered in step 3, the WTRU may receive a (e.g. further) PDCCH DCI to schedule PUSCH resources for MAC CE transmission.

[0211] A second example is referred to as "mode B”. In some implementations, mode-B is similar to Mode A, with one example difference being that a resource is pre-configured for transmission of a report in step 3. For Step-1 , one or more bits may be indicated in the first PUCCH channel to notify a second UL channel to carry MR report. For mode B, the WTRU may transmit a LR and / or MR report, or a MAC CE for LR and / or MR report in the pre-configured resource.

[0212] In some implementations, the WTRU may include an indication of a mobility event or mobility measurement results in any one or more steps of the beam reporting procedure. In some implementations, the WTRU may include only mobility results, may include both beam results and mobility results, or may include beam results only, with an indication of a mobility event or further mobility information to transmit in a MAC CE or other message.

[0213] Some implementations relate to performing measurements. In some implementations, e.g., when monitoring LR, the WTRU may turn off or reduce monitoring of signals using the MR. Accordingly, at this time any measurement event evaluation may need to be based on LR measurements.

[0214] In some implementations, the based on (e.g., upon) detecting that one or more LR measurements meet a configured criteria, the WTRU may enable MR reception and measurements. In some implementations, based on this (e.g., at this point) the WTRU may transmit a first report indicating the LR criteria has been met. In some implementations, the WTRU may transmit a SR only, to request a grant for transmission of further information. In some - 41 -9365181.1IDC-2024P00698WC implementations, this SR (or other UCI) may implicitly (e.g. by selecting a specific PUCCH resource) or explicitly (e.g. by including a flag or identity) indicate that a LR measurement event has been met. In some implementations, based on (e.g., once) the WTRU transmits the SR, and subsequently receives a grant or other indication to enable further information to be transmitted, the WTRU may start transmitting measurement results based on the MR measurements. For example, in a CSI report, MAC CE, and so on.

[0215] Some implementations relate to an uplink reference signal. In some implementations, the WTRU may be configured to transmit an uplink reference signal in response to detecting one or more LR measurement events.

[0216] "SRS” refers to Sounding Reference Signal, and may be a reference signal transmitted by the WTRU in the uplink. In some implementations, this may be used by the network (e.g. gNB) to estimate the uplink channel quality. SRS may be used to provide information to the network about multipath fading, scattering, Doppler, and power loss of the transmitted signal. In some implementations, the sounding reference signals are uplink physical signals employed by WTRU (e.g., user equipment (UE)) for uplink channel sounding, including channel quality estimation and synchronization. In some implementations, unlike Demodulation reference signals (DM-RS), SRS is not associated with any physical uplink channels and they support uplink channel-dependent scheduling and link adaptation. In some implementations, the SRS may assist with codebook-based closed-loop spatial multiplexing, control uplink transmit timing, reciprocity-based downlink precoding in multi-user MIMO setups, quasi co-location of physical channels and reference signals.

[0217] In some implementations, the network may perform measurements on the WTRUs transmitted SRS on one or multiple transmission reception points (TRPs). In some implementations, the WTRU selects SRS resources for the TRPs which provide the best measured downlink beams. In some implementations, the WTRU may transmit using more than one SRS resource representing multiple potential target TRPs. In some implementations, the WTRU may include an indication of a downlink measurement value (e.g. RSRP). In some implementations, the WTRU may include an indication of only the downlink measurement associated with the SRS resource selection, or may include an indication of multiple downlink measurements (e.g. the best N beams).

[0218] In one example, in some implementations, a WTRU receives a wake-up indication and indication of transmitting second LP-WUS via first LP-WUS. If first LP-WUS indicated WTRU not to wake up, and second LP-WUS is transmitted, WTRU receives second LP-WUS. WTRU determines whether to transmit CSI and / or RSRP reports based on indications received in second LP-WUS.

[0219] In an example procedure, in some implementations, a WTRU receives configuration and / or indication of one or more of the following from a gNB, base station, or other network device: a configuration and / or indication of first and second LP-WUS (e.g., LOs, MOs, etc.); a configuration and / or indication of a number (M) of WTRUs associated with first LP-WUS, ID of WTRU (local WTRU ID) for first and second LP-WUS (e.g., local WTRU ID = {0, 1 , 2, .... M-1}; a configuration and / or indication of a structure of first and second LP-WUS payload (e.g., indicating a bitmap-based first LP-WUS carrying per-WTRU wake-up, and / or a bitmap-based second LP-WUS carrying per-WTRU indications for CSI and / or RSRP reporting); a configuration and / or indication of first and second CSI, and 3rd(default) and / or RSRP (e.g., L1-RSRP) report configuration groups (e.g., where each group may be a set of one or more CSI- 42 -9365181.1IDC-2024P00698WC and / or RSRP report configurations, or null set which corresponds to not reporting; a configuration and / or indication of a threshold (e.g., a first threshold) time (e.g., timeSincelndicationToTxCSI in this example) since a most recent indication for CSI and / or RSRP reporting via LP-WUS; a configuration and / or indication of an applicability of a second LP-WUS indication for CSI and / or RSRP reporting (e.g., applicable for CSI reporting only (i.e., reporting CSI except L1-RSRP), applicable for L1-RSRP reporting, applicable for both CSI and L1-RSRP reporting); a configuration and / or indication for to the WTRU to begin monitoring LP-WUS.

[0220] In some implementations, e.g., after receiving the configuration and / or indication,

[0221] the WTRU monitors for and / or receives a first LP-WUS. See e.g., FIG. 5. In some implementations, if the first LP-WUS indicates for the WTRU to not wake up (e.g., to keep monitoring LP-WUSs), the WTRU may report CSI and / or RSRP measurements, e.g., based on indications received in second LP-WUS or by a default configuration. For example, in some implementations, if the threshold time timeSincelndicationToTxCSI > first threshold, WTRU receives a new indication from gNB. For example, If the first LP-WUS indicates that a second LP-WUS is to be transmitted and an indication for CSI and / or RSRP reporting is to be included for the WTRU in the second LP-WUS, WTRU monitors for the second LP-WUS. In some implementations, the WTRU receives an indication for CSI and / or RSRP reporting based on indications in second LP-WUS. For example, in some implementations, in a bitmap based LP-WUS with per WTRU wake-up and CSI and / or RSRP reporting indications, the first LP-WUS includes M+1 bits. In some implementations, the first M bits include a wake-up indication for M WTRUs. In some implementations, the (M+1)th bit indicates that a second LP-WUS will be transmitted. In some implementations, the second LP-WUS includes a maximum number (e.g., represented by nSkipMax in this example) of bits, e.g., shared among WTRUs that are not awoken by the first LP-WUS. In some implementations, each bit in second LP-WUS carries an indication for CSI and / or RSRP reporting for a WTRU. In some implementations, nSkipMax bits are insufficient for all WTRUs that are not awoken by the first LP-WUS, which WTRUs are included in the second LP-WUS is based on WTRU ID. In some implementations, if the second LP-WUS indicates for the WTRU to transmit CSI and / or RSRP reports, the WTRU may transmit CSI and / or RSRP reports based on a first CSI and / or RSRP report configuration group and a configured applicability of second LP-WUS indication for CSI and / or RSRP reporting, (e.g., if the second LP-WUS indication is applicable for L1-RSRP reporting, the WTRU transmits L1-RSRP reports (e.g., in skipped DRX active time)). In some implementations, if the WTRU fails to receive the second LP-WUS, the WTRU may report CSI and / or RSRP measurements, e.g., based on a default CSI and / or RSRP report configuration group (e.g., in skipped DRX active time). In some implementations, if the first LP-WUS indicates that second LP-WUS is not transmitted or if an indication for CSI and / or RSRP reporting is not included for WTRU in the second LP-WUS (e.g., the WTRU makes this determination), the WTRU may report CSI and / or RSRP measurements, e.g., based on a default CSI and / or RSRP report configuration group.

[0222] In some implementations, if timeSincelndicationToTxCSI < first threshold, the WTRU may transmits CSI and / or RSRP reports, e.g., based on a most recently received indication (e.g., in skipped DRX active time).

[0223] In some implementations, if the first LP-WUS indicates that the WTRU is to wake up, the WTRU may turn on MR, and may monitor for and / or receive DL scheduling indications (e.g., PDCCHs). In some implementations, if- 43 -9365181.1IDC-2024P00698WG the second CSI and / or RSRP report configuration group includes any CSI and / or RSRP reports in DRX active time, the WTRU transmits respective reports.

[0224] In some implementations, this or related approaches as discussed herein may have the advantage of increasing power saving achievable through LP-WUS monitoring, and / or may increase the efficiency of measurement reporting.

[0225] FIG. 6 is a flow chart illustrating an example method 600 implemented in a WTRU. In some implementations, method 600 may be implemented based on any devices, systems, and / or procedures discussed herein.

[0226] At 602, the WTRU receives a first LP-WUS. At 604, the WTRU transmits a report. In some implementations, the report is transmitted based on a field of the first LP-WUS and on a second LP-WUS, based on the field of the first LP-WUS having a first value.

[0227] In some implementations, the report is transmitted based on the field of the first LP-WUS without receiving the second LP-WUS, based on the field of the first LP-WUS having a second value. In some implementations, the report is transmitted without receiving the second LP-WUS, based on the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold. In some implementations, the report is transmitted without receiving the second LP-WUS based on the field of the first LP- WUS having the first value, based on the first LP-WUS including a number of fields having the first value exceeding a threshold, and based on an identity of the WTRU. In some implementations, the report is transmitted according to a default behavior based on the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold. In some implementations, the report is transmitted according to a default behavior based on the field of the first LP-WUS having the first value and the second LP-WUS not being received. In some implementations, the report is transmitted based on a threshold amount of time being exceeded since a previous report having been transmitted. In some implementations, the report comprises a CSI report or an RSRP report. In some implementations, the first LP-WUS comprises a bitmap, and wherein the field of the first LP- WUS occupies a position in the bitmap corresponding to an identity of the WTRU. In some implementations, the first LP-WUS includes an indication of whether the second LP-WUS will occur. In some implementations, the bitmap includes an indication of whether the second LP-WUS will occur.

[0228] FIG. 7 is a flow chart illustrating an example method 700 implemented in a base station, gNB, or other network device. In some implementations, method 700 may be implemented based on any devices, systems, and / or procedures discussed herein. At 702, the base station transmits a first LP-WUS. At 704, the base station receives a report.

[0229] In some implementations, a field of the first LP-WUS having a first value indicates that the report is to be transmitted based on a second LP-WUS. In some implementations, the field of the first LP-WUS having a second value indicates that the report is to be transmitted without the second LP-WUS. In some implementations, the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold indicates that the report is to be transmitted without receiving the second LP-WUS. In some - 44 -9365181.1implementations, the field of the first LP-WUS having the first value, the first LP-WUS including a number of fields having the first value exceeding a threshold, and an identity of a wireless transmit / receive unit (WTRU), indicate that the report is to be transmitted without receiving the second LP-WUS. In some implementations, the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold, indicate that the report is to be transmitted according to a default behavior. In some implementations, the field of the first LP-WUS having the first value, and the second LP-WUS not being received, indicate that the report is to be transmitted according to a default behavior. In some implementations, the report is received based on a threshold amount of time being exceeded since a previous report was transmitted. In some implementations, the report comprises a CSI report or an RSRP report. In some implementations, the first LP-WUS comprises a bitmap, and wherein the field of the first LP-WUS occupies a position in the bitmap corresponding to an identity of a wireless transmit / receive unit (WTRU). In some implementations, the first LP-WUS includes an indication of whether the second LP-WUS will occur. In some implementations, the bitmap includes an indication of whether the second LP-WUS will occur.

[0230] 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, WTRU, terminal, base station, RNC, or any host computer.- 45 -9365181.1

Claims

CLAIMSWhat is Claimed:1 . A method implemented in a wireless transmit / receive unit (WTRU), the method comprising: receiving a first low-power wake-up signal (LP-WUS); and transmitting a report, wherein the report is transmitted based on a field of the first LP-WUS and on a second LP-WUS, based on the field of the first LP-WUS having a first value, and wherein the report is transmitted based on the field of the first LP-WUS without receiving the second LP- WUS, based on the field of the first LP-WUS having a second value.

2. The method of claim 1 , wherein the report is transmitted without receiving the second LP-WUS, based on the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold.

3. The method of claim 1, wherein the report is transmitted without receiving the second LP-WUS based on the field of the first LP-WUS having the first value, based on the first LP-WUS including a number of fields having the first value exceeding a threshold, and based on an identity of the WTRU.

4. The method of claim 1 , wherein the report is transmitted according to a default behavior based on the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold.

5. The method of claim 1 , wherein the report is transmitted according to a default behavior based on the field of the first LP-WUS having the first value and the second LP-WUS not being received.

6. The method of claim 1, wherein the report is transmitted based on a threshold amount of time being exceeded since a previous report having been transmitted.

7. The method of claim 1 , wherein the report comprises a CSI report or an RSRP report.

8. The method of claim 1, wherein the first LP-WUS comprises a bitmap, and wherein the field of the first LP- WUS occupies a position in the bitmap corresponding to an identity of the WTRU.

9. The method of claim 1, wherein the first LP-WUS includes an indication of whether the second LP-WUS will occur.- 46 -9365181.

110. The method of claim 8, wherein the bitmap includes an indication of whether the second LP-WUS will occur.

11. A wireless transmit / receive unit (WTRU) comprising: receiver circuitry configured to receive a first low-power wake-up signal (LP-WUS); and transmitter circuitry configured to transmit a report, wherein the transmitter circuitry is configured to transmit the report based on a field of the first LP-WUS and on a second LP-WUS, based on the field of the first LP-WUS having a first value, and wherein the transmitter circuitry is configured to transmit the report based on the field of the first LP-WUS without receiving the second LP-WUS, based on the field of the first LP-WUS having a second value.

12. The WTRU of claim 11 , wherein the transmitter circuitry is configured to transmit the report without receiving the second LP-WUS, based on the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold.

13. The WTRU of claim 11 , wherein the transmitter circuitry is configured to transmit the report without receiving the second LP-WUS based on the field of the first LP-WUS having the first value, based on the first LP-WUS including a number of fields having the first value exceeding a threshold, and based on an identity of the WTRU.

14. The WTRU of claim 11, wherein the transmitter circuitry is configured to transmit the report according to a default behavior based on the field of the first LP-WUS having the first value and the first LP-WUS including a number of fields having the first value exceeding a threshold.

15. The WTRU of claim 11, wherein the transmitter circuitry is configured to transmit the report according to a default behavior based on the field of the first LP-WUS having the first value and the second LP-WUS not being received.

16. The WTRU of claim 11, wherein the transmitter circuitry is configured to transmit the report based on a threshold amount of time being exceeded since a previous report having been transmitted.

17. The WTRU of claim 11 , wherein the report comprises a CSI report or an RSRP report.

18. The WTRU of claim 11, wherein the first LP-WUS comprises a bitmap, and wherein the field of the first LP- WUS occupies a position in the bitmap corresponding to an identity of the WTRU.

19. The WTRU of claim 11, wherein the first LP-WUS includes an indication of whether the second LP-WUS will occur.- 47 -9365181.

120. The WTRU of claim 18, wherein the bitmap includes an indication of whether the second LP-WUS will occur.- 48 -9365181.1

Images