[go: up one dir, main page]

WO2025235550A1 - Procédés de prise en charge d'informations de signal de réveil à faible puissance dans des modes connectés - Google Patents

Procédés de prise en charge d'informations de signal de réveil à faible puissance dans des modes connectés

Info

Publication number
WO2025235550A1
WO2025235550A1 PCT/US2025/028042 US2025028042W WO2025235550A1 WO 2025235550 A1 WO2025235550 A1 WO 2025235550A1 US 2025028042 W US2025028042 W US 2025028042W WO 2025235550 A1 WO2025235550 A1 WO 2025235550A1
Authority
WO
WIPO (PCT)
Prior art keywords
wtru
wus
wake
indication
receive
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2025/028042
Other languages
English (en)
Inventor
Prasanna Herath
Young Woo Kwak
Moon Il Lee
Nazli KHAN BEIGI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2025235550A1 publication Critical patent/WO2025235550A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal where the received signal is a power saving command
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/028—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • Embodiments described herein include a method performed by a WTRU comprising: receiving a configuration for a low power wake-up signal (LP-WUS) including at least one low-power wake-up occasion (LO) and at least one monitoring occasion (MO) associated with each LO; determining a LO for monitoring from among the at least one LO based on at least one of: a configured association between the at least one or more LOs and a search space (SS) for monitoring a downlink control information (DCI) message, a position of a wake-up indication for the WTRU within the DCI message or a payload size of the DCI message; determining an MO; receiving the LP-WUS during the determined LO and the determined MO; and determining to wake up a main radio to receive the DCI message based on a payload of the LP-WUS; wherein the DCI message includes a cyclical redundancy check (CRC) scrambled by a power savings radio network identifier (PS-
  • the method may include wherein the determination to wake up the main radio is based on an indication of secondary cell dormancy in the LP- WUS payload. Additionally/alternatively the method may include wherein the determination to wake up the main radio is based on a lack of an indication of secondary cell dormancy in the LP-WUS payload. Additionally/alternatively the method may include wherein, on a condition that the WTRU has one or more configured or activated secondary cells, the determination to wake up the main radio is based on lack of indication of secondary cell dormancy in the LP-WUS payload.
  • the method may include wherein, on a condition that the WTRU has more than one configured or activated secondary cells and the LP-WUS includes a secondary cell dormancy indication, determining to wake up the main radio to receive the DCI message. Additionally/alternatively the method may include wherein the LP-WUS payload comprises a wake-up indication field and a dormancy indication field. Additionally/alternatively the method may include receiving the DCI message; and determining from the DCI message whether any secondary cells configured for the WTRU are dormant.
  • the method may include, monitoring for a physical downlink control channel PDCCH in a secondary cell configured for the WTRU wherein the secondary cell is not indicated to be dormant in the DCI message. Additionally/alternatively the method may include the determination of the MO is based on a number of MOs associated with the determined LO. Additionally/alternatively the method may include wherein the determination of the MO is further based on an ID of the WTRU for the DCI.
  • a wireless transmit/receive unit comprising: a processor and a transceiver, wherein the processor and transceiver are configured to: receive a configuration for a low power wake-up signal (LP-WUS) including at least one low-power wake-up occasion (LO) and at least one monitoring occasion (MO) associated with each LO; determine a LO for monitoring from among the at least one LO based on at least one of: a configured association between the at least one or more LOs and a search space (SS) for monitoring a downlink control information (DCI) message, a position of a wake-up indication for the WTRU within the DCI message or a payload size of the DCI message; determine an MO; receive the LP-WUS during the determined LO and the determined MO; and determine to wake up a main radio to receive the DCI message based on a payload of the LP- WUS; wherein the DCI message includes a cyclical red
  • the WTRU may include wherein the determination to wake up the main radio is based on an indication of secondary cell dormancy in the LP-WUS payload. Additionally/alternatively the WTRU may include wherein the determination to wake up the main radio is based on a lack of an indication of secondary cell dormancy in the LP-WUS payload. Additionally/alternatively the WTRU may include: wherein, on a condition that the WTRU has one or more configured or activated secondary cells, the determination to wake up the main radio is based on lack of indication of secondary cell dormancy in the LP-WUS payload.
  • the WTRU may include wherein, on a condition that the WTRU has more than one configured or activated secondary cells and the LP-WUS includes a secondary cell dormancy indication, the processor and transceiver are further configured to determine to wake up the main radio to receive the DCI message. Additionally/alternatively the WTRU may include wherein the LP-WUS payload comprises a wake-up indication field and a dormancy indication field. Additionally/alternatively the WTRU may include wherein the processor and transceiver are further configured to: receive the DCI message; and determine from the DCI message whether any secondary cell configured for the WTRU are dormant.
  • the WTRU may include wherein the processor and transceiver are further configured to: monitor for a physical downlink control channel PDCCH in a secondary cell configured for the WTRU wherein the secondary cell is not indicated to be dormant in the DCI message. Additionally/alternatively the WTRU may include wherein the determination of the MO is based on a number of MOs associated with the determined LO. Additionally/alternatively the WTRU may include wherein the determination of the MO is further based on an ID of the WTRU for the DCI.
  • FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
  • WTRU wireless transmit/receive unit
  • 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. 1A according to an embodiment;
  • RAN radio access network
  • CN core network
  • FIG. 1 D 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. 1A according to an embodiment
  • FIG. 2 is a block diagram of an example low-power wake up receiver
  • FIG. 3 is a timing diagram for discontinuous reception
  • FIG. 4 is an example structure of a block-based low power-wake up signal (LP-WUS);
  • FIG. 5 is an example of a bit-map-based LP-WUS;
  • FIG. 6 is a flow chart of an example process for WTRU low power wake up.
  • 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.
  • 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.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT-UW-DFT-S-OFDM zero-tail unique-word discrete Fourier transform Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • 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.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (for example, remote surgery), an industrial device and applications (for example, 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.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • a vehicle a drone
  • 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.
  • 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.
  • 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.
  • BSC base station controller
  • RNC radio network controller
  • 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.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • 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 (for example, 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).
  • RAT radio access technology
  • 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.
  • the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 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).
  • 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).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • 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.
  • a radio technology such as NR Radio Access
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • 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.
  • DC dual connectivity
  • 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 (for example, an eNB and a g N B) .
  • 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.
  • 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 Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • the base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (for example, for use by drones), a roadway, and the like.
  • 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).
  • WLAN wireless local area network
  • 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).
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (for example, WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106.
  • 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.
  • QoS quality of service
  • 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.
  • the RAN 104 and/or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT.
  • 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.
  • 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).
  • POTS plain old telephone service
  • 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.
  • 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.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multimode capabilities (for example, the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • 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.
  • FIG. 1B is a system diagram illustrating an example WTRU 102.
  • 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.
  • GPS global positioning system
  • 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.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (for example, the base station 114a) over the air interface 116.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • 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.
  • 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 (for example, multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • 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.
  • the WTRU 102 may have multi-mode capabilities.
  • 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.
  • 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 (for example, 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.
  • 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.
  • SIM subscriber identity module
  • SD secure digital
  • 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).
  • 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.
  • the power source 134 may include one or more dry cell batteries (for example, nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (for example, longitude and latitude) regarding the current location of the WTRU 102.
  • the WTRU 102 may receive location information over the air interface 116 from a base station (for example, 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.
  • 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.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • 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.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (associated with particular subframes for both the UL (for example, for transmission) and DL (for example, 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 (for example, a choke) or signal processing via a processor (for example, a separate processor (not shown) or via processor 118).
  • the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (for example, associated with particular subframes for either the UL (for example, for transmission) or the DL (for example, for reception)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • 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 overthe air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • 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. 10, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • 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.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • 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.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
  • the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
  • 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.
  • 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.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • 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.
  • the CN 106 may include, or may communicate with, an IP gateway (for example, an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • 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.
  • 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 (for example, temporarily or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • 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 (for example, directly between) the source and destination STAs with a direct link setup (DLS).
  • 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 (for example, 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.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (for example, 20 MHz wide bandwidth) or a dynamically set width.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems.
  • the STAs for example, 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 (for example, only one station) may transmit at any given time in a given BSS.
  • 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.
  • 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.
  • 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.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting 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).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11af and 802.11ah relative to those used in 802.11 n, and 802.11ac.
  • 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine-Type Communications (MTC), such as MTC devices in a macro coverage area.
  • MTC Meter Type Control/Machine-Type Communications
  • MTC devices may have certain capabilities, forexample, limited capabilities including support for (for example, only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (for example, to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11n, 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.
  • the primary channel may be 1 MHz wide for STAs (for example, MTC type devices) that support (for example, 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.
  • STAs for example, MTC type devices
  • NAV Network Allocation Vector
  • 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.11ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • 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.
  • 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.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • 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.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • 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 (for example, containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • 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.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (for example, such as eNode- Bs 160a, 160b, 160c).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • 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.
  • 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.
  • 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.
  • 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.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • 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.
  • SMF Session Management Function
  • 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.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (for example, 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.
  • PDU protocol data unit
  • 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 ofservices being utilized WTRUs 102a, 102b, 102c.
  • 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.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • 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- Third Generation Partnership Project (3GPP) access technologies such as WiFi.
  • 3GPP Third Generation Partnership Project
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like.
  • a PDU session type may be IPbased, non-IP based, Ethernet-based, and the like.
  • 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.
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may include, or may communicate with, an IP gateway (for example, an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • 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.
  • 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.
  • 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.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • 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.
  • 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.
  • 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.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (for example, 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 (for example, which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • CN Core Network e.g. LTE/NR packet core or NR core
  • LTE Long Term Evolution for example, from 3GPP LTE R8 and later
  • TRP T ransmission-Reception Point (used interchangeably with GnB)
  • a WTRU may monitor for and receive a wake-up signal (WUS) via a first radio.
  • the WUS may be called a low-power WUS (LP-WUS).
  • the first radio may be called a low-power radio (LR) or a low power wakeup radio (LP-WUR).
  • Receiving a WUS (for example, an LP-WUS), for example via the LR, may trigger wake-up or usage of a second radio of the WTRU (for example, the WTRU’s main radio (MR)) for data and/or control signal transmission and/or reception.
  • MR main radio
  • FIG. 2 is a diagram of an example receiver architecture of a WTRU 200 comprising a low-power wake-up receiver 221 , a main radio receiver 231 , a baseband processor 212, and an application processor 214.
  • the WTRU is configured to receive an LP-WUS 220 and a main radio signal 230.
  • the inclusion of a low power wake-up receiver has the potential to reduce the power consumption of wireless devices.
  • a deep sleep state for the MR while the WTRU is in Radio Resource Control (RRC) IDLE or RRC INACTIVE states (referred to as IDLE/INACTIVE mode Low Power Wake-Up Signal (LP-WUS) monitoring) may be implemented in embodiments.
  • the WTRU may skip monitoring Physical Downlink Control Channel (PDCCH) while in RRC CONNECTED state. This may be referred to herein as CONNECTED mode LP-WUS monitoring.
  • DRX Discontinuous Reception
  • CRC Cyclic Redundancy Check
  • DCP powersaving radio network identifier PS-RNTI
  • DRX may be used to reduce WTRU power consumption by allowing the WTRU to periodically enter in to a power saving state (DRX inactive), during which the WTRU suspends at least PDCCH monitoring.
  • FIG. 3 shows an example timing diagram 300 comprising DRX active periods 312, 322, 332, and DRX inactive periods, for example 326.
  • the WTRU may be configured to suspend one or more additional operations (for example, transmitting (for example, periodic) Channel State Information (CSI) reports, L1- Reference Signal Received Power (RSRP) report) during DRX inactive time.
  • CSI Channel State Information
  • RSRP L1- Reference Signal Received Power
  • the WTRU may switch to an active state for a limited time (DRX active time). Once scheduled, UL/DL data/control transmissions are over, the WTRU returns to a power saving state.
  • DRX active time a limited time
  • DCI with CRC scrambled by a power-saving radio network identifier may be used with DRX.
  • DCP may be used to represent a DCI such as a DCI with CRC scrambled with a particular RNTI such as a power savings RNTI (for example, PS-RNTI).
  • a WTRU may monitor for and receive a DCP 310, 320 330 prior to (for example, in a search space (SS) configured ps-Offset (314, 324 ,334) from the starting time of each DRX active time) each DRX active time.
  • SS search space
  • a WTRU may receive an indication for activating (for example, for PDCCH monitoring)/not activating the MR for the next DRX active time via DCP.
  • DCP may carry dormancy indication for a configured one or more Secondary Cells (SCells).
  • a DCP may include a wake-up indication and SCell dormancy information for one or more WTRUs (for example, WTRUs configured with the same SS for DCP).
  • the SCell dormancy information may indicate separately the dormancy status (dormant or non-dormant) for each SCell (for example, configured or activated) associated with a WTRU.
  • a WTRU may monitor and/or receive the DCP to determine whether to wake-up, for example, to monitor and/or receive DL signals such as PDCCH, Physical Downlink Shared Channel (PDSCH), Channel State Information-Reference Signal (CSI-RS).
  • DL signals such as PDCCH, Physical Downlink Shared Channel (PDSCH), Channel State Information-Reference Signal (CSI-RS).
  • a low-power wake-up signal may be used (for example, instead or in addition to the DCP) to indicate wake-up and SCell dormancy information.
  • the LP-WUS payload size may be smaller than the DCP payload size. Embodiments are described herein for LP-WUS to support similar indications supported via DCP with limited payload size.
  • wake-up indication for WTRUs associated with a DCP may be carried in multiple LP- WUSs.
  • a WTRU may determine to wake-up and may determine dormancy status of SCells via LP-WUS payload (for example, with a bitmap or codepoint structure).
  • availability of SCell dormancy status for a WTRU may depend on WTRU priority. The embodiments may reduce power usage of WTRUs and/or support activation of SCells faster and be less power consuming. In embodiments the following steps may be performed:
  • LOs LP-WUS occasions
  • MOs monitoring occasions
  • SS search space
  • Size of the payload of LP-WUS sizeLPWUS
  • ID of the WTRU for DCP for example, 2nd local WTRU ID
  • structure of LP-WUS payload for example, indicated as bitmap based or codepoint based.
  • structure may be known by the WTRU and not be indicated; and/or e) DCP information indicating the location of the WTRU’s wakeup and/or SCell dormancy information in the DCP.
  • the WTRU may monitor for and receive an LP-WUS in an LO of the configured LOs and in one or more MOs of the configured MOs associated with the LO.
  • the WTRU may determine the LO for monitoring and receiving the LP-WUS based on one or more of the following: a) the configured association between the one or more LOs and the SS for monitoring the DCP; or b) the position of the WTRU’s wake-up indication within the DCP and/or the payload size of the DCP (for example, the determined LO is a first LO, or a second LO based on whether the WTRU’s wake-up indication is in the first or second half of the DCP payload).
  • the WTRU may determine the one or more MOs of the configured MOs based on the number of MOs associated with the determined LO and the WTRU’s ID for DCP.
  • the WTRU may determine from the payload of the LP-WUS whether the LP-WUS indicates that the WTRU should wake up and, for example, if the WTRU is indicated to wake-up, whether the WTRU needs to receive the DCP to obtain more information (for example, regarding SCell dormancy).
  • the LP-WUS payload may include a wake-up indication for each of the M WTRUs and the WTRU may determine whether to wake-up based on its wake-up indication. The WTRU may determine to wake-up when its wake-up indication indicates to wake-up.
  • the WTRU may determine to receive the DCP based on whether the LP-WUS includes an SCell dormancy indication for the WTRU and what the SCell dormancy indication indicates if included.
  • the WTRU determines to receive the DCP based on whether the LP-WUS includes an SCell dormancy indication for the WTRU and what the SCell dormancy indication indicates if included, for example: a) if the WTRU has one or more configured or activated SCells and the LP-WUS does not include an SCell dormancy indication for the WTRU, the WTRU may determine to receive the DCP; b) if the WTRU has more than one configured or activated SCell and the LP-WUS includes an SCell dormancy indication (for example, 1 bit indication that indicates all SCells are dormant or at least one SCell is non-dormant) for the WTRU that indicates non-dormant, the WTRU may receive the DCP (for example, to determine which SCell(s) are not dormant); c) in an example (for example, using a bitmap based LP-WUS structure), the LP-W
  • the DIF may indicate SCell dormancy information for WTRUs indicated to wake-up. If there are not enough DIF bits for all WTRUs indicated to wake-up, the priority or ID (for example, first local WTRU ID) number of the WTRU may determine which WTRUs have DIF bits and which DIF bit belongs to each WTRU. d) In an example (for example, using a codepoint based structure) a separate field or codepoint (for example, 2 bits) may be used for each WTRU.
  • the field or codepoint may indicate one or more of: do not wake-up, wake-up, all SCells are dormant, at least one SCell is non-dormant, or the first SCell (for example, lowest cell ID) is non-dormant.
  • the WTRU wakes-up the main radio and receives the DCP or PDCCHs from the Primary Cell (PCell) (for example, PCell of a Master Cell Group) and/or one or more SCells.
  • PCell Primary Cell
  • SCell for example, PCell of a Master Cell Group
  • the WTRU receives the DCP and determines from the DCP whether any SCells are non-dormant and/or which SCells are non-dormant.
  • the WTRU monitors for and/or receives a PDCCH from at least one SCell indicated to be non-dormant.
  • DCP is used to dynamically indicate one or more WTRUs to wake-up or not wake-up for the next DRX Active Time (for example, for monitoring and receiving PDCCH, to transmit CSI-RS and/or L1-RSRP reports).
  • a WTRU may be configured to monitor and receive a LP-WUS, which may fully/partially/opportunistically replace the need for monitoring and receiving DCP.
  • the supported payload/information carrying capacity of a LP-WUS may be lower than that of DCP.
  • a set of WTRUs supported by one DCP may be mapped/distributed to one or more LP-WUSs and/or LP-WUS may carry limited and/or compressed information compared to DCP.
  • a WTRU may receive one or a combination of the following indications/configurations (for example, via RRC signaling, MAC-CE indication, System Information (SI) (for example, SI updates), and/or DCI indication).
  • SI System Information
  • a WTRU may receive a DRX (for example a C-DRX) configuration.
  • a DRX for example a C-DRX
  • a WTRU may receive a configuration of one or more LP-WUS occasions (LOs) and one or more monitoring occasions (MOs) associated with each LO.
  • LOs LP-WUS occasions
  • MOs monitoring occasions
  • a WTRU may receive the configuration (for example, based on one or more offsets with respect to starting resource of drx-onDurationTimer, periodicity etc., received via RRC signaling, SI, MAC-CE indication) of one or more LOs per DRX (for example, C-DRX) cycle.
  • the WTRU may receive the configuration (for example, based on one or more offsets with respect to starting resources of LO) of one or more (K) LP-WUS MOs (for example, resources for receiving LP-WUS) within each LO.
  • K LP-WUS MOs
  • the WTRU may receive the configuration of N*K LP-WUS MOs for each LO.
  • a WTRU may receive an association between one or more LOs and a search space (SS) for monitoring a DCP.
  • a WTRU may receive (for example, via RRC signaling, SI, MAC-CE indication, DCI indication) one or more offsets with respect to the starting resources of SS configured for receiving DCP.
  • Each offset may associate with an LO (for example, starting resources of each LO).
  • a WTRU may receive a number (M) of WTRUs associated with a LP-WUS.
  • a WTRU may ID of the WTRU for DCP (second local WTRU ID), and total number of WTRUs associated with DCP.
  • a WTRU may receive a priority order of M WTRUs for SCell dormancy indication. Alternatively, a WTRU may determine priority based on a local WTRU ID (for example, a WTRU with the lowest first local WTRU ID has the higher priority, a WTRU with the second lowest first local WTRU ID has second highest priority). [0090] In embodiments, a WTRU may receive a size of the payload of LP-WUS (sizeLPWUS).
  • a WTRU may receive a structure of LP-WUS payload for example, configured/indicated (for example, via RRC signaling, SI, MAC-CE indication, DCI indication) as bitmap based, codepoint based, or block based.
  • structure may be known by the WTRU (for example, based on specifications) and not configured/indicated by the gNB/CN.
  • a WTRU receives a structure of an LP-WUS payload, it may be a bitmap-based structure of LP-WUS.
  • WIF wake-up indication filed
  • DIF dormancy indication field
  • the DIF may be shared between WTRUs indicated to wake up by WIF based on an allocation rule (DIF allocation rule). For example, If sizeDIF ⁇ number (numWakeup) of WTRUs indicated to wake up by WIF, 1 bit in DIF may be allocated to WTRUs based on priority (highest to lowest) until all sizeDIF bits are allocated.
  • Allocated DIF bits may be ordered (most significant bit (MSB) to least significant bit (LSB)) based on WTRU’s first local WTRU ID. If sizeDIF > numWakeup, 1 bit in DIF may be allocated to each WTRU indicated to wake-up via WIF.
  • An SCell dormancy indication bit of WTRUs indicated to wake-up may be ordered based on first local WTRU ID (for example, ⁇ woken-up WTRU with the lowest 1st local WTRU ID, woken-up WTRU with the second lowest first local WTRU ID ⁇ ). Remaining (sizeDIF - numWakeup) information bits may be left unused/unassigned (for example, all set to 0).
  • a WTRU receives a structure of an LP-WUS payload, it may be a codepoint based structure of LP-WUS.
  • a codepoint based structure of LP-WUS payload may comprise ordered (for example, based on a WTRU’s first local WTRU ID) list of codepoints of configured lengths where separate codepoint may be assigned for each WTRU (for example, ⁇ codepoint for WTRU#0, codepoint for WTRU#1, ..., codepoint for WTRU#M-1 ⁇ , where WTRU#m represents the WTRU with m th first local WTRU ID).
  • a WTRU may receive configuration for the starting position of a codepoint in LP-WUS (for example, when the same codepoint size (bit with of code point) is not used for all the WTRUs associated with LP-WUS).
  • a WTRU may receive an association/mapping between possible values of a codepoint configured for the WTRU and meaning of each value.
  • the meaning of codepoints may include don’t wake-up (for example, codepoint value 00), wake-up and all SCells are dormant (for example, codepoint value 01), wake-up and at least one SCell is non-dormant (for example, codepoint value 10), wake-up and the first SCell (for example, lowest cell ID) is non-dormant (for example, codepoint value 11).
  • a WTRU receives a structure of an LP-WUS payload, it may be a block-based structure of LP-WUS.
  • FIG. 4 is an example structure of a block- based LP_WUS.
  • Block Number m may associate with WTRU#m. The block associated with WTRU#m, me ⁇ 0,1 ,2,..
  • ,,M- 1 ⁇ may include wake-up indication (410, 414, ,420) (for example, 1 bit wake-up indication (for example, 1st bit in the block)), and SCell dormancy indication (412, 414, 422) (for example, L m bits (DIF) for SCell dormancy indication if the WTRU is configured with one or more SCells (for example, L m ⁇ number (LTM Ceiis ) of SCells the WTRU is configured with).
  • a WTRU may receive configuration/indication for the starting position of block associated with the WTRU.
  • a WTRU may receive configuration/indication for a mapping rule between indication bits in DIF and LTM Cells SCells, the WTRU is configured with. For example, when L m ⁇ LTM Cells , the WTRU may receive configuration/indication of one of the following mapping rules.
  • a mapping rule may be known by the WTRU (for example, based on specifications).
  • L m 1 for all WTRUs.
  • 1 bit DIF may indicate that at least one SCell is non dormant (for example, if 1 bit DIF is 1 st value (for example, 1)), or all SCells are dormant (for example, if 1 bit DIF is 2 nd value (for example, 0)).
  • a mapping rule may be: mapping rule 3: Each bit in first L m -1 bits may indicate dormancy of floor(LTM Ce;;s lL m ) SCells (for example, 1 st bit may indicate SCell dormancy of first set of floor(L ⁇ e;;s lL m ) SCells, 2 nd bit may indicate SCell dormancy of second set of floor(LTM Ce;;s lL m ) SCells, etc.).
  • L m th bit may indicate that at least one of the last (LTM Cells - floor(LTM Ce;;s / L m ) x - 1) SCells are non-dormant.
  • floor(.) is the floor function.
  • L m 1 for all WTRUs.
  • 1 bit DIF may indicate change of dormancy status (for example, dormant, or non-dormant) of at least 1 SCell with respect to a preconfigured (for example, preconfigured via RRC signaling, SI, MAC-CE indication, DCI indication) reference (dormancy status of all SCells).
  • a WTRU may receive a configuration including DCP information indicating the location of the WTRU’s wake-up and/or SCell dormancy information in the DCP.
  • the WTRU may determine SCell dormancy information carried via DCP based on configuration associated with Carrier Aggregation (CA). For example, size of the dormancy indication is determined based on the number of SCells the WTRU is configured with.
  • CA Carrier Aggregation
  • the WTRU may determine association between one or more SCells and dormancy indication received via DCP based on IDs of SCells and order of dormancy indication field (for example, MSB associated with SCell with the lowest ID, LSB associated with SCell with the highest ID).
  • the WTRU may receive the configuration for one or more LOs. Each LO may associate/be configured with multiple MOs. In embodiments, the WTRU may receive LP-WUS intended for the WTRU in a subset/all of MOs within one or more configured LOs. To determine one or more LOs for receiving LP-WUS, the WTRU may follow one or more of the following embodiments.
  • a WTRU may determine one or more LOs for receiving (for example, in one or more MOs associated with each LO) LP-WUS based on one or more of the following: a) association between one or more LOs and SS for monitoring DCP; b) position of wake-up indication within DCP; c) 2nd local WTRU ID; or d) explicit indication/ configuration (for example, in a bit map received via SI, RRC signaling, MAC-CE indication, where each bit may associate with each configured LO by gNB and 1st value in a bit indicates that the corresponding LO is configured for the WTRU) of one or more LOs by gNB/CN.
  • the WTRU when a WTRU is configured with one LO (for example, within DRX Inactive time) or the WTRU determines one LO based on configured association between LOs and SS for monitoring DCP, the WTRU may determine the configured/determined LO for monitoring and receiving LP-WUS.
  • the WTRU may determine a LO for receiving LP-WUS intended for the WTRU based on position of wake-up indication within DCP. For example, a WTRU may determine LO is a first LO, or a second LO based on whether the WTRU’s wake-up indication is in the first or second half of the DCP payload.
  • the WTRU may determine that the LP-WUS intended for the WTRU may be received in a first LO. If the position of wake-up indication bit within DCP is greater than or equal to the sizeDCP/2, the WTRU may determine that LP-WUS intended for the WTRU may be received in a second LO.
  • the WTRU may determine a LO for receiving LP-WUS intended for the WTRU based on the WTRU’s second local WTRU ID.
  • a WTRU may determine a LO is a first LO, if the WTRU’s second local ID ⁇ (total number of WTRUs associated with DCP)/2.
  • a WTRU may determine LO is a second LO, if the WTRU’s second local ID > (total number of WTRUs associated with DCP)/2.
  • the WTRU may determine a subset of LOs for receiving LP- WUS intended for the WTRU based on second local WTRU ID. For example, if a WTRU’s second local WTRU ID is even, the WTRU determines one or more LOs with even indices for receiving LP-WUS. If the WTRU’s second local WTRU ID is odd, the WTRU may determine one or more LOs with odd indices for receiving LP-WUS.
  • a WTRU may monitor all MOs associated with the determined /configured LOs. In further embodiments, the WTRU may determine one or more MOs of determined/configured LOs for monitoring and receiving LP-WUS based on one or combination of the following. [0111] In embodiments, a WTRU may determine one or more MOs of determined/configured LOs for monitoring and receiving LP-WUS based on gNB/CN indication/configuration. For example, the WTRU may receive (for example, in a bit map) configuration/indication for MOs for receiving LP-WUS.
  • a WTRU may determine one or more MOs of determined/configured LOs for monitoring and receiving LP-WUS based on a number of MOs configured within LOs and a second local WTRU ID.
  • a (each) LO may associate with two MOs (for example, two MOs per beam in the case of beam-based operation).
  • a WTRU may determine a MO (for example, out of two MO of LO) for receiving LP-WUS based on a WTRU’s second local WTRU ID.
  • a WTRU may determine a MO is a first MO, if the WTRU’s second local ID ⁇ (total number of WTRUs associated with DCP)/2.
  • a WTRU may determine a MO is a second MO, if a WTRU’s 2nd local ID > (total number of WTRU associated with DCP)/2.
  • a WTRU may determine one or more MOs of determined/configured LOs for monitoring and receiving LP-WUS based a Number of MOs configured within LOs and position of wake-up indication within DCP.
  • a LO may associate with two MOs (for example, two MOs per beam in the case of beam-based operation).
  • a WTRU may determine a MO (for example, out of two MO of LO) for receiving LP-WUS based on position of wake-up indication within DCP.
  • a WTRU may determine a MO is a first MO, or a second MO based on whether the WTRU’s wake-up indication is in the first or second half of the DCP payload.
  • a WTRU may determine one or more MOs of determined/configured LOs for monitoring and receiving LP-WUS based on a configuration/indication received from a gNB/CN (via SI, RRC signaling, MAC-CE indication). For example, a WTRU may receive a configuration/indication in a bit map. Each bit in the bitmap may associate with a MO within each LO. A bit of first value in the bit map may indicate the WTRU to monitor for an associated MO.
  • Embodiments for a WTRU to determine wake-up indication and/or SCell dormancy indication via a bitmapbased LP-WUS are described below.
  • a WTRU may receive a configuration/indication for structure of a bitmap based LP-WUS (for example, via RRC signaling, SI, MAC-CE indication, DCI indication).
  • the structure of LP-WUS may be known by the WTRU (for example, as a part of specification) and not be configured/indicated.
  • a WTRU may determine whether to wake-up (for example, to monitor for and receive PDCCH in at least PCell, start drx-onDurationTimer in a DRX Active time) or not to wake-up (for example, continue monitoring LP-WUS) based on a WTRU’s wake-up indication bit received in a wake up indication field (WIF). For example, if a bit in WIF associated with a WTRU indicates first value (for example, 1), a WTRU may wake-up its main radio.
  • WIF wake up indication field
  • a WTRU may determine whether an SCell dormancy indication is included in the dormancy indication field (DIF). If a WTRU determines that SCell dormancy indication is included in DIF, the WTRU may determine the position of the SCell dormancy indication within DIF based on WTRU’s first local ID. Based on the received SCell dormancy indication in DIF for the WTRU, the WTRU may determine the dormancy status (for example, dormant, or non-dormant) of one or more SCells.
  • DIF dormancy indication field
  • a WTRU may receive a DCP. Based on SCell dormancy indication received via DCP, a WTRU may determine which SCells are nondormant.
  • a WTRU may monitor for and receive PDCCH and/or transmit (for example, periodic) CSI-RS/L1-RSRP reports (for example, during next DRX Active Time) in one or more SCells determined to be non-dormant.
  • a WTRU may determine that at least one SCell is non-dormant. If a WTRU is configured with one SCell, a WTRU may determine that configured SCell is non-dormant. If a WTRU is configured with more than one SCell, a WTRU may receive a DCP. Based on the indication received in the DCP, the WTRU may determine which SCells are non-dormant. A WTRU may monitor for and receive PDCCH and/or transmits (for example, periodic) CSI-RS/L1-RSRP reports (for example, during next DRX Active Time) in one or more SCells determined to be non-dormant.
  • PDCCH Physical Downlink Control Channel
  • a WTRU may receive DCP. Based on the indication received in DCP, a WTRU may determine which SCells are non-dormant. In embodiments, a WTRU may monitor for and receive PDCCH and/or transmits (for example, periodic) CSI-RS/L1-RSRP reports (for example, during next DRX Active Time) in one or more SCells determined to be non-dormant.
  • LP-WUS of eight bits (510, 512, 514, 516, 518, 520, 522 and 524) are used for wake-up indication and SCell dormancy indication of six WTRUs (WTRU#0, WTRU#1 , WTRU#2, WTRU#3, WTRU#4, WTRU#5).
  • WTRU#0, WTRU#1 , WTRU#2, WTRU#3, WTRU#4, WTRU#5) are configured with priority (for example, highest (1) to lowest (6)), 1 , 3, 5, 4, 2, and 6.
  • Based on a WIF of 001011 , WTRU#2, WTRU#4, and WTRU#5 determine to wake-up the main radio (for example, for monitoring and receiving PDCCH).
  • DIF size DIF
  • the WTRUs Based on the first local ID of WTRU#2 (i.e., 2) and WTRU#4 (i.e., 4), the WTRUs determine that DIF indicates SCell dormancy indication is in the format of ⁇ SCell dormancy of WTRU#2, and SCell dormancy of WTRU#4 ⁇ . Based on received LP-WUS (i.e., WIF and DIF), WTRUs may determine their wake-up indication and SCell dormancy indication as follows:
  • a WTRU’s first local ID is 2, the WTRU wakes-up.
  • the WTRU determines SCell dormancy indication based on DIF and/or DCP. If a WTRU is configured with one SCell, the WTRU determines that SCell is non-dormant. If a WTRU is configured with more than one SCell, the WTRU receives DCP. Based on the SCell dormancy indication received via DCP, the WTRU determines dormant and non-dormant SCells.
  • a WTRU may receive the configuration/indication for structure of codepoint based LP- WUS (for example, via RRC signaling, SI, MAC-CE indication, DCI indication).
  • structure of the LP-WUS may be known by the WTRU (for example, as a part of specification) and not be configured/indicated.
  • a codepoint based structure of LP-WUS may comprise an ordered (for example, based on first local WTRU ID) list of codepoints of configured length (for example, ⁇ codepoint for WTRU#0, codepoint for WTRU#1 , ..., codepoint for WTRU#M-1 ⁇ ).
  • a WTRU may receive mapping between one or more possible values of the codepoint configured for the WTRU and the meaning/interpretation of the codepoint values.
  • the meaning/interpretation of the codepoint values may include, but not be limited to: do not wake-up MR, wake-up MR and all SCells are dormant, wake-up MR and at least one SCell is non-dormant, wake-up MR and the first SCell (for example, lowest cell ID) is non-dormant.
  • a WTRU may be configured with two or more configurations for meaning/interpretation of codepoint values.
  • both the WTRU and gNB may be aware of the different configurations for meaning/interpretations of codepoint values (for example, based on specifications).
  • a WTRU may be configured with two or more tables (codepoint mapping table) where each table maps one or more codepoint values to different meaning/interpretation.
  • Each table may associate with different configuration of codepoint (for example, bit width).
  • the WTRU may determine a codepoint mapping table out of the two or more configu red/specified tables based on one or more of the following.
  • a WTRU may determine a codepoint mapping table out of the two or more configured/specified tables based on bit width of the codepoint. For example, the WTRU may receive two configurations for meaning/interpretation of codepoints. If bit width of the codepoint is a first bit width, the WTRU may determine first configuration for meaning/interpretation of codepoint. If the bit width of the codepoint is a second bit width, the WTRU may determine a second configuration for meaning/interpretation of codepoint.
  • a WTRU may determine a codepoint mapping table out of the two or more configured/specified tables based on the number of SCells the WTRU is configured with. For example, the WTRU may receive configuration of two codepoint mapping tables. In an embodiment, the WTRU may determine a first codepoint mapping table if the number of SCells configured for the WTRU is a first number. In embodiments, the WTRU may determine a second codepoint mapping table if the number of SCells configured for the WTRU is a second number.
  • a WTRU may determine a codepoint mapping table out of the two or more configured/specified tables based on LO and/or MO UE received LP-WUS/configured to receive LP-WUS. For example, the WTRU may receive a configuration of two codepoint mapping tables and two types (for example, with different supported LP-WUS payloads) of LO and/or MO. If the WTRU receives a LP-WUS in a first type LO and/or MO, the WTRU may determine the codepoint mapping table is a first table. If the WTRU receives the LP-WUS in a second type LO and/or MO, the WTRU may determine the codepoint mapping table is a second table.
  • a WTRU may determine a codepoint mapping table out of the two or more configured/specified tables based on modulation of the LP-WUS (for example, OOK1 , OOK4, etc.). For example, the WTRU may receive a configuration of two codepoint mapping tables. In embodiments, a WTRU may determine a first codepoint mapping table if the modulation of LP-WUS received is a first type (for example, OOK1). In embodiments, a WTRU may determine a second codepoint mapping table if the modulation of LP-WUS received is a second type (for example, OOK4).
  • a first codepoint mapping table if the modulation of LP-WUS received is a first type (for example, OOK1).
  • a WTRU may determine a second codepoint mapping table if the modulation of LP-WUS received is a second type (for example, OOK4).
  • the WTRU may determine whether to wake-up the MR and/or dormancy status of one or more SCells (for example, if one or more SCells are configured). If the WTRU determines to wake-up the MR, the WTRU may perform one or more of: starting a timer associated with PDCCH monitoring (for example, drx-onDurationTimer), monitoring for and receiving PDCCH in at least PCell (for example, monitor for and receive PDCCH in next DRX active time), transmit CSI and/or L1-RSRP reports.
  • PDCCH monitoring for example, drx-onDurationTimer
  • PCell for example, monitor for and receive PDCCH in next DRX active time
  • transmit CSI and/or L1-RSRP reports for example, CSI and/or L1-RSRP reports.
  • a WTRU may determine to wakeup MR and receive DCP. If the WTRU determines to receive DCP, the WTRU may receive the DCP. The WTRU may then determine from the DCP whether any SCells are non-dormant and/or which SCells are non-dormant. The WTRU may monitor for and receive PDCCH in one or more SCells determined to be non-dormant. The WTRU may transmit (for example, periodic) CSI and/or L1-RSRP reports configured for one or more SCells determined to be non-dormant. [0139] In an example configuration, a WTRU may be configured with code point of two bits with four possible values, 00, 01 , 10, 11 , where configuration of meaning/interpretation of each codepoint given by Table 1.
  • a WTRU may determine to wake-up/not wake-up MR and SCell dormancy as follows.
  • the WTRU keeps MR in a power saving state deep sleep) and monitor for and receive LP-WUS.
  • the WTRU wakes-up MR, and may monitor for and receive PDCCH in
  • the WTRU wakesup the MR and receive the DCP.
  • the WTRU determines from the DCP whether any SCells are non-dormant and/or which SCells are non-dormant.
  • the WTRU may monitor for and receive PDCCH in one or more SCells determined to be non-dormant based on indication received in DCP.
  • the WTRU may transmit (for example, periodic) CSI and/or L1-RSRP reports configured for one or more SCells determined to be non-dormant.
  • Embodiments for a WTRU determining wake-up indication and/or SCell dormancy indication based on block-based LP-WUS are described below.
  • the WTRU may receive the configuration/indication for structure of block based LP-WUS (for example, via RRC signaling, SI, MAC-CE indication, DCI indication).
  • the structure of a LP-WUS may be known by the WTRU (for example, as a part of specification) and not be configured/indicated.
  • the WTRU may determine a block of information (i.e., L m + 1 bits) intended for the WTRU based on a configured/determined starting position (for example, within LP-WUS) of an information block associated with the WTRU.
  • the WTRU may determine position (for example, first bit in the block) of wake-up indication within the received information block based on structure of LP-WUS.
  • wake-up indication indicates the WTRU to wake-up (for example, WUS bit is first value (for example, 1))
  • the WTRU may wake-up the MR (for example, monitor for and receive PDCCH, start drx-onDurationTimer, and transmit (for example, periodic) CSI/L1 -RSRP reports).
  • the WTRU may determine which SCell is dormant and non-dormant based on one or more of DIF, DCP and a mapping rule between DIF and configured SCells.
  • L m LTM Cells (i.e., DIF has a unique bit for each SCell the WTRU is configured with)
  • kth bit in DIF is first value (for example, 1)
  • the WTRU may determine that kth SCell configured for the WTRU is non-dormant.
  • kth bit in DIF is second value (for example, 0)
  • the WTRU may determine that kth SCell configured for the WTRU is dormant.
  • the WTRU may receive DCP. Based on the received SCell dormancy indication via DCP, the WTRU may determine dormant and non-dormant SCells.
  • the WTRU may determine dormant and non-dormant SCells based on one or more of the following. If the WTRU receives a first value (for example, 1) for 1 bit DIF, the WTRU may determine that at least 1 SCell is non dormant. The WTRU may receive DCP. Based on the received SCell dormancy indication via DCP, the WTRU may determine dormant and non-dormant SCells. If the WTRU receives a second value (for example, 0) for 1 bit DIF, the WTRU may determine that all SCells the WTRU is configured with are dormant.
  • a first value for example, 1 bit DIF
  • the WTRU may determine that at least 1 SCell is non dormant.
  • the WTRU may receive DCP. Based on the received SCell dormancy indication via DCP, the WTRU may determine dormant and non-dormant SCells. If the WTRU receives a
  • the WTRU may determine that kth SCell is dormant, b) If the WTRU receives a first value (for example, 1) for L m th bit in DIF, the WTRU may determine that at least one of the remaining SCells (SCell with indices L m to LTM Cells ) is non-dormant. The WTRU may receive DCP. The WTRU may determine dormant and non-dormant SCells based on an indication in DCP.
  • the WTRU may monitor and receive PDCCH and/or transmit (for example, periodic) CSI and/or L1-RSRP reports in one or more SCells determined to be non-dormant. If the WTRU receives a second value (for example, 0) for L m th bit in DIF, the WTRU may determine that all remaining SCells (SCell with indices L m to LTM Cells ) are dormant.
  • a second value for example, 0
  • the WTRU may monitor for and (for example, attempt to) receive PDCCH in all SCells in kth set of floor(LTM Ce;;s lL m ) SCells. If the WTRU receives value of kth bit in DIF, k e ⁇ 1, 2, ...
  • the WTRU may determine that all SCells in kth set of floor(LTM ;e// , lL m ) SCells are dormant, b) If the WTRU receives a first value (for example, 1 ) for the L m th bit in DIF, the WTRU may determine that at least one SCell of last (LTM Cells - floor(LTM Ce;;s / L m ) x (L m - 1) SCells are non-dormant.
  • the WTRU may monitor for and (for example, attempt to) receive PDCCH in all SCells in all last (LTM Ceiis - floor(LTM Ce;;s / L m ) x (L m - 1) SCells. If the WTRU receives a second value (for example, 0) for the L m th bit in DIF, the WTRU may determine that all of the last (L? rp// . - floor(L T deliberately, ⁇ / L m ) x L - 1) SCells are dormant.
  • a WTRU if a WTRU receives a configuration/indication for mapping rule 4, the WTRU uses mapping rule 4 based on specifications (for example, when L m ⁇ LTM Cells ), the WTRU may determine dormant and non-dormant SCells based on one or more of the following: a) If the WTRU receives a first value (for example, 1) for a 1 bit DIF, the WTRU may determine that dormancy status of at least one SCell has changed with respect to a preconfigured (for example, via RRC signaling, MAC-CE indication, DCI indication, SI) reference (for example, a preconfigured DRX Cycle/DCP where all the WTRUs may receive SCell dormancy indication via DCP).
  • a preconfigured for example, via RRC signaling, MAC-CE indication, DCI indication, SI
  • a WTRU may receive DCP. Next, based on the received SCell dormancy indication via the DCP, the WTRU may determine dormant and non-dormant SCells. b) If the WTRU receives the second value (for example, 0) for a one bit DIF, the WTRU may determine that dormancy status of all SCells the WTRU is configured with are unchanged with respective a preconfigured (for example, via RRC signaling, MAC-CE indication, DCI indication, SI) reference (for example, a preconfigured DRX Cycle/DCP where all the WTRUs may receive SCell dormancy indication via DCP).
  • a preconfigured for example, via RRC signaling, MAC-CE indication, DCI indication, SI
  • a WTRU may monitor and receive PDCCH and/or transmit (for example, periodic) CSI and/or L1-RSRP reports in one or more SCells determined to be non-dormant.
  • FIG. 6 is a flow chart for an exemplary process.
  • the WTRU receives a configuration for low power wake-up.
  • the WTRU receives a low power wake-up signal (LP-WUS) based on the configuration;
  • the WTRU determines whether the low power wake-up signal includes an instruction for the WTRU to wake up.
  • the WTRU wakes up a main radio based on the instruction.
  • LP-WUS low power wake-up signal
  • a method performed by a WTRU may include: receiving a configuration for low power wake-up; receiving a low power wake-up signal (LP-WUS) based on the configuration; determining whether the low power wake-up signal includes an instruction for the WTRU to wake up; and waking up a main radio based on the instruction.
  • LP-WUS low power wake-up signal
  • the methods may include: wherein the configuration includes at least one of: a configuration of at least one low-power wake-up occasion (LO) and at least one monitoring occasion (MO) associated with each LO; an association between one or more LOs and a search space (SS); a number of WTRUs associated with the LP WUS; a structure of an LP WUS payload and information indicating a location within the LP-WUS of the WTRU’s wake-up information or of secondary cell (SCell) dormancy information.
  • LO low-power wake-up occasion
  • MO monitoring occasion
  • SS search space
  • SCell secondary cell
  • the methods may include: wherein the WTRU determines an LO for monitoring and receiving the LP-WUS based on at least one of an association between an LO and an SS; or a position of the WTRU’s wake-up location in a down link control information (DCI).
  • the methods may include: wherein the LP-WUS includes a wake-up indication for a plurality of WTRUs and the WTRU determines to wake up based on a wake-up indication for the WTRU.
  • the methods may include: wherein the WTRU determines to wake up based on a position of the WTRU’s wake up indication within a DCI.
  • the methods may include: wherein the WTRU determines to receive the a DCI based on whether the LP-WUS includes an SCell dormancy indication for the WRTU. In further embodiments the methods may include: wherein in a case where the WTRU wakes up, the WTRU receives a DCI or a physical downlink control channel (PDCCH) message from a primary cell and/or at least one secondary cell. In further embodiments the methods may include: wherein the WTRU determines from the DCI any secondary cells that are nondormant. In embodiments, a WTRU may be configured to perform any of the above methods.
  • PDCCH physical downlink control channel
  • a WTRU comprises: a low power wake-up receiver; a main radio comprising a transceiver; and a processor, wherein: the processor is configured to receive a configuration related to low power wake-up; the low power wake-up receiver is configured to receive a low power wake-up signal (LP-WUS) based on the configuration; the processor is configured to determine whether the LP-WUS includes an instruction for the WTRU to wakeup; and in a case where the processor determines the LP-WUS includes the instruction to wake up, the processor wakes up the main radio based on the instruction.
  • LP-WUS low power wake-up signal
  • the configuration includes at least one of: a configuration of at least one low-power wake-up occasion (LO) and at least one monitoring occasion (MO) associated with each LO; an association between one or more LOs and a search space (SS); a number of WTRUs associated with the LP WUS; a structure of an LP WUS payload and information indicating a location within the LP-WUS of the WTRU’s wake-up information or of secondary cell (SCell) dormancy information.
  • LO low-power wake-up occasion
  • MO monitoring occasion
  • SS search space
  • SCell secondary cell
  • the processor determines an LO for monitoring and receiving the LP-WUS based on at least one of: an association between an LO and an SS; or a position of the WTRU’s wake-up location in a down link control information (DCI).
  • the LP-WUS includes a wake-up indication for a plurality of WTRUs and the processor determines to wake up based on a wake-up indication for the WTRU.
  • the processor determines to wake up based on a position of the WTRU’s wake up indication within a DCI.
  • the processor determines to receive the a DCI based on whether the LP-WUS includes an SCell dormancy indication for the WRTU.
  • the transceiver in a case where the WTRU wakes up, is configured to receive a DCI or a physical downlink control channel (PDCCH) message from a primary cell and/or at least one secondary cell.
  • the WTRU determines from the DCI any secondary cells that are dormant.
  • PDCCH physical downlink control channel
  • 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).
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des procédés sont décrits pour qu'une WTRU surveille et reçoive un signal de réveil (WUS) par l'intermédiaire d'une première radio. Le WUS peut être un WUS à faible puissance (LP-WUS). La première radio peut être une radio basse puissance (LR) ou une radio à réveil basse puissance (LP-WUR). Les procédés consistent à déterminer si le signal de réveil à faible puissance comprend une instruction pour que la WTRU se réveille et réveiller une radio principale sur la base de l'instruction.
PCT/US2025/028042 2024-05-06 2025-05-06 Procédés de prise en charge d'informations de signal de réveil à faible puissance dans des modes connectés Pending WO2025235550A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463643102P 2024-05-06 2024-05-06
US63/643,102 2024-05-06

Publications (1)

Publication Number Publication Date
WO2025235550A1 true WO2025235550A1 (fr) 2025-11-13

Family

ID=96141195

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/028042 Pending WO2025235550A1 (fr) 2024-05-06 2025-05-06 Procédés de prise en charge d'informations de signal de réveil à faible puissance dans des modes connectés

Country Status (1)

Country Link
WO (1) WO2025235550A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220210866A1 (en) * 2018-02-14 2022-06-30 Samsung Electronics Co., Ltd. Method and apparatus for power savings at a user equipment
US20230171688A1 (en) * 2019-11-04 2023-06-01 Qualcomm Incorporated Secondary cell dormancy indication and application delay
KR20240024267A (ko) * 2021-08-06 2024-02-23 엘지전자 주식회사 하향링크 제어 채널을 송수신하는 방법 및 이를 위한 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220210866A1 (en) * 2018-02-14 2022-06-30 Samsung Electronics Co., Ltd. Method and apparatus for power savings at a user equipment
US20230171688A1 (en) * 2019-11-04 2023-06-01 Qualcomm Incorporated Secondary cell dormancy indication and application delay
KR20240024267A (ko) * 2021-08-06 2024-02-23 엘지전자 주식회사 하향링크 제어 채널을 송수신하는 방법 및 이를 위한 장치
US20240349187A1 (en) * 2021-08-06 2024-10-17 Lg Electronics Inc. Method for transmitting and receiving downlink control channel and apparatus therefor

Similar Documents

Publication Publication Date Title
US20250193635A1 (en) Methods for sidelink transmit-receive distance determination
EP4505806A1 (fr) Accès à un réseau discontinu
US20210084620A1 (en) Methods for physical downlink control channel (pdcch) candidate determination
US12119937B2 (en) Open loop HARQ in wireless systems
EP3497981B1 (fr) Rendement énergétique de réseau
US12185314B2 (en) Methods and apparatus for dynamic spectrum sharing
JP7599266B2 (ja) 低減された能力のｗｔｒｕのための低減された帯域幅のための方法、装置、及びシステム
US11991630B2 (en) WTRU power saving in active time
EP4616548A1 (fr) Appareil et procédés de gestion de faisceau pour une liaison d'accès dans un répéteur commandé par réseau nouvelle radio (nr-ncr)
WO2025235550A1 (fr) Procédés de prise en charge d'informations de signal de réveil à faible puissance dans des modes connectés
EP3949206B1 (fr) Procédés de détermination de distance d'émission-réception de liaison latérale
US20250358752A1 (en) S_ssb frequency hopping for robust sidelink in contested and congested environments
US20250317926A1 (en) Uplink carrier prioritization
WO2025235505A1 (fr) Procédés et appareils pour prendre en charge des informations lp-wus dans des modes au repos/inactifs
WO2025212661A1 (fr) Procédés et appareil pour prendre en charge un temps actif de réception de drx apériodique
WO2025212596A1 (fr) Procédés de planification d'améliorations pour un canal physique à travers des symboles sbfd et non sbfd
WO2024173407A1 (fr) Transmission de wtru d'une indication pour changer un motif de blocage
WO2024178206A1 (fr) Procédés pour une opération de temps de réveil cible à chevauchement coordonné à ap multiples
WO2025034322A1 (fr) Sélection de porteuse parmi des porteuses sous licence et sans licence
WO2025090884A1 (fr) Procédés de prise en charge d'un rapport de faisceau de faible puissance et de rapport de csi
WO2025015247A1 (fr) Acquisition d'informations système et de synchronisation dans des réseaux à économie d'énergie associés à un signal de pré-synchronisation
WO2025034830A1 (fr) Détermination d'adéquation pour une surveillance de signal de réveil faible puissance (lp-wus) dans des états de rrc ou des configurations de lp-wus
TW202439843A (zh) 用於多ａｐ訊務狀態交換之方法及增強型ｕｏｒａ設計
WO2025147693A1 (fr) Procédés, architectures, appareils et systèmes pour des indications de réveil basées sur des sous-groupes
WO2025175301A1 (fr) Accès au canal secondaire coordonné à ap multiples dans des systèmes wi-fi