WTRU reachability in energy-saving networks

Abstract

We provide WTRUs related to energy-saving networks. [Solution] The WTRU may receive configuration information indicating that the second cell should be used for Paging Early Notification (PEI) monitoring when the first cell is a camp cell and / or the first cell is in a network energy saving (NES) state. Based on the determination that the first cell is in an NES state, the WTRU may monitor PEI through the second cell. The WTRU may receive PEI through the second cell. The WTRU may monitor paging through the first cell and / or the second cell based on PEI subgroups. If a page is received through the second cell, the WTRU may send an instruction through the second cell indicating the identity of the first cell. If a page is received through the first cell, the WTRU may send a signal through the first cell.

Description

Technical Field

[0001] (Cross - Reference to Related Applications) This application claims priority to U.S. Provisional Patent Application No. 63 / 394,735, filed on August 03, 2022, and U.S. Provisional Patent Application No. 63 / 410,327, filed on September 27, 2022, the entire contents of each of these provisional applications are incorporated herein by reference.

Background Art

[0002] Techniques for energy saving in a specific network (e.g., a 5G network) may be under consideration. For example, one or more extensions may be considered to enable the network to minimize power consumption due to transmission and / or reception. Such minimization can be beneficial for reducing operating costs and / or environmental sustainability.

[0003] In comparison with previous systems, in one or more (e.g., specific) networks (e.g., 5G NR), for example, when there is no data, one or more transmissions from the network can be minimized. For example, the cell - specific reference signal (CRS), which is always on, can be made unused in one or more (e.g., specific) efficient networks, which can further result in reduced energy consumption.

[0004] In one or more examples, the network can consume energy even when there is no transmission from one or more other activities, such as baseband (e.g., digital) processing for reception and / or beamforming. Such wasted power consumption can be non - negligible (e.g., in a high - density network) even when there is no WTRU receiving service during a given period. For example, if the network avoids such activities when there is no transmission to a WTRU, energy consumption can be reduced.

[0005] In addition, or / or, one or more (e.g., a specific) network (e.g., 5G NR) may support beamforming using one or more (e.g., a large number) ports (e.g., up to 64 transmit and receive ports), and / or, energy consumption may increase as the number of ports used increases. For one or more (e.g., all) specific WTRUs, it may not be necessary to use the maximum number of ports. For example, if the network optimizes the number of ports (e.g., to only the necessary number), energy consumption may be reduced.

[0006] For example, network energy efficiency may aim to improve the operation of the cellular ecosystem and / or enable more efficient optimization of the network's transmit and / or receive resources in the time domain, frequency domain, spatial domain, and / or power domain. For example, such a scenario may receive support, feedback, and / or assistance from one or more WTRUs. For example, echo-friendly WTRU operation may be provided (e.g., enabling the deployment of more environmentally friendly network deployments and / or reducing emissions and running costs associated with the operation of cellular networks). For example, one or more (e.g., specific) networks (e.g., 5G) may eliminate the need for always-on synchronous and / or reference signal transmission and / or support optimized bandwidth and / or MIMO capabilities, thereby achieving greater efficiency in the operation of newer deployments. [Overview of the project]

[0007] A wireless transmit-receive unit (WTRU) may be associated with a network energy saving (NES) group. The WTRU may be configured to monitor downlink resources associated with the NES group. For example, the WTRU may receive notifications related to the NES group via the downlink resources. The WTRU may be configured to receive configuration information related to discontinuous reception (DRX). For example, the configuration information may include instructions for a first DRX cycle. The WTRU may monitor paging messages from a serving cell according to the first DRX cycle. The WTRU may receive instructions that a serving cell is in the NES state, for example, via downlink resources associated with the NES group. In response to the received instructions that a serving cell is in the NES state, the WTRU may transition to a second DRX cycle (e.g., an NES DRX cycle). For example, the WTRU may determine the second DRX cycle based on a function. In response to the instruction that a serving cell is in the NES state, the WTRU may monitor paging messages from the serving cell according to the second DRX cycle. Additionally, or alternatively, in response to the received instruction that a serving cell is in the NES state, the WTRU may monitor paging messages from the second cell according to the first DRX cycle.

[0008] The WTRU may receive configuration information. The WTRU may receive configuration information indicating that the first cell is associated with the second cell. The configuration may include, for example, an instruction that the second cell should be used for paging early indication (PEI) monitoring when the first cell is selected as a camped cell and / or the first cell is in a network energy saving (NES) state. The configuration information may indicate the first PEI subgroup and / or the second PEI subgroup. The first PEI subgroup may be associated with the second cell. The second PEI subgroup may be associated with the first cell. The WTRU may monitor PEI via the second cell, for example, based on a determination that the first cell is in an NES state. The WTRU may receive PEI via the second cell, for example. The WTRU may monitor paging. For example, a WTRU may monitor paging through a second cell, provided that the PEI received through the second cell indicates a first PEI subgroup. A WTRU may transmit a signal through the first cell if a page is received through the first cell, and / or transmit an instruction through the second cell indicating the identity of the first cell if a page is received through the second cell. A WTRU may determine, for example, that the first cell is no longer in an NES state if a page is received through the first cell.

[0009] A first cell may be associated with a first intermittent reception (DRX) cycle. A second cell may be associated with a second DRX cycle. A WTRU may apply the first DRX cycle, for example, provided that the WTRU is connected to the first cell. A WTRU may apply the second DRX cycle, for example, provided that the WTRU is connected to the second cell. A WTRU may determine the paging frame (PF) and / or paging occasion (PO) of the first or second cell, for example, based on NES-specific WTRU identification information (ID).

[0010] The WTRU may receive broadcast signaling and / or one or more synchronization signal block (SSB) transmissions. The WTRU may determine that one or more SSB transmissions and / or one or more POs are delayed and / or skipped in the first cell. For example, based on the determination that one or more SSB transmissions and / or one or more POs are delayed or skipped in the first cell, the WTRU may determine that a subset of physical downlink control channel (PDCCH) POs for the second DRX cycle will not be transmitted. The WTRU may determine the first and / or second cell by receiving broadcast signaling and / or one or more SSB transmissions. For example, the WTRU may determine the first and / or second cell based on the received broadcast signaling and / or based on one or more properties related to one or more SSB transmissions.

[0011] WTRU can determine a second cell. For example, WTRU can determine a second cell based on one or more channel measurements and / or one or more handover candidate settings.

[0012] The WTRU can determine the NES state of the first cell. For example, the WTRU can determine the NES state of the first cell based on the reception of a primary synchronization signal (PSS) transmission. For example, the WTRU can determine the NES state of the first cell based on the reception of a secondary synchronization signal (SSS) transmission. The WTRU can determine the NES state of the first cell based on the reception of both a PSS transmission and an SSS transmission.

[0013] A WTRU may receive configuration information that includes instructions indicating that a WTRU is included in a set of one or more WTRUs, for example, under the condition that one or more sets of WTRUs are located within one or more cells that are in an NES state. A WTRU may monitor and / or receive one or more group common instructions related to one or more sets of WTRUs in an NES state. [Brief explanation of the drawing]

[0014] [Figure 1A] This is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] This is a system diagram illustrating an exemplary wireless transmit / receive unit (WTRU) that may be used in a communication system illustrated in Figure 1A, according to one embodiment. [Figure 1C] This is a system diagram illustrating an exemplary radio access network (RAN) and an exemplary core network (CN) that may be used in a communication system illustrated in Figure 1A according to one embodiment. [Figure 1D] This is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used in the communication system illustrated in Figure 1A according to one embodiment. [Figure 2] An example related to the time / frequency structure of SSB is shown. [Figure 3] An example related to beam sweeping is shown. [Figure 4] This example illustrates the switching of the NES DRX cycle while WTRU is in an idle / inactive state for the NES. [Figure 5] This provides an example related to the paging procedure in the NES state, including paging reception from the second cell. [Figure 6] Here is a second example related to the paging procedure in the NES state. [Modes for carrying out the invention]

[0015] Figure 1A illustrates an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, message transmission, and broadcast to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique-word OFDM (UW-OFDM), resource block filtering OFDM, and filter bank multicarrier (FBMC).

[0016] As shown in Figure 1A, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, and 102d, RAN 104 / 113, CN 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, but it will be understood that the disclosed embodiments intend any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d, any of which may be referred to as “stations” and / or “STAs,” may be configured to transmit and / or receive radio signals and may include user equipment (WTRUs), mobile stations, fixed subscriber units or mobile subscriber units, subscriber-based units, pagers, mobile phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, radio sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., for remote surgery), industrial devices and applications (e.g., robots and / or other radio devices operating in industrial and / or automated processing chain contexts), consumer electronics devices, and devices operating on commercial and / or industrial radio networks. WTRU102a, 102b, 102c, and 102d can all be referred to as WTRU for compatibility purposes.

[0017] The communication system 100 may also include base stations 114a and / or base stations 114b. Each of the base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), node B, enode B, home node B, home enode B, gNB, NR node B, site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are each depicted as single elements, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0018] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), and relay nodes. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be licensed spectra, unlicensed spectra, or a combination of licensed and unlicensed spectra. Cells may provide coverage of wireless services to a particular geographic area, which may be relatively fixed or change over time. Cells may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver per sector of the cell. In one embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

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

[0020] More specifically, as described above, the communication system 100 may be a multiple access system and may employ one or more channel access methods such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base stations 114a within RAN104 / 113 and the WTRUs 102a, 102b, 102c may implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use wideband CDMA (WCDMA) to establish the air interfaces 115 / 116 / 117. WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

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

[0022] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as NR radio access, which may use New Radio (NR) to establish the air interface 116.

[0023] In one embodiment, base station 114a and WTRU 102a, 102b, 102c may implement multiple radio access technologies. For example, base station 114a and WTRU 102a, 102b, 102c may implement LTE radio access and NR radio access together, for example, using the dual connectivity (DC) principle. Thus, the air interface utilized by WTRU 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions made to multiple types of base stations (e.g., eNB and gNB).

[0024] In other embodiments, base stations 114a and WTRUs 102a, 102b, and 102c may implement wireless 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), and GSM EDGE (GERAN).

[0025] The base station 114b in Figure 1A may be, for example, a wireless router, home node B, home e-node B, or access point, and may utilize any suitable RAT to facilitate wireless connectivity in local areas such as offices, homes, vehicles, campuses, industrial facilities, aerial corridors (for use by drones, for example), roads, etc. In one embodiment, the base station 114b and WTRU 102c, 102d may implement wireless technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and WTRU 102c, 102d may implement wireless technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base stations 114b and WTRUs 102c, 102d may establish picocells or femtocells using cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). As shown in Figure 1A, base station 114b may have a direct connection to the internet 110. Therefore, base station 114b may not need to access the internet 110 via CN 106 / 115.

[0026] RAN104 / 113 may communicate with CN106 / 115, 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 WTRU102a, 102b, 102c, and 102d. The data may have various Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, and mobility requirements. CN106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, internet connectivity, video distribution, etc., and / or implement high-level security functions such as user authentication. Although not shown in Figure 1A, it will be understood that RAN104 / 113 and / or CN106 / 115 may communicate directly or indirectly with other RANs employing the same or different RAT as RAN104 / 113. For example, in addition to being connected to RAN104 / 113 which can utilize NR radio technology, CN106 / 115 may also communicate with another RAN (not shown) by employing GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0027] CN106 / 115 may also function as a gateway for WTRU102a, 102b, 102c, 102d to access PSTN108, the Internet 110, and / or other networks 112. PSTN108 may include a circuit-switched telephone network providing plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices, which use common communication protocols such as the transmission control protocol (TCP), the user datagram protocol (UDP), and / or the Internet protocol (IP) of the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may employ the same RAT as RAN 104 / 113 or a different RAT.

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

[0029] Figure 1B is a system diagram illustrating an exemplary WTRU 102. As shown in Figure 1B, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be understood that the WTRU 102 may include any partial combination of the aforementioned elements while maintaining consistency with one embodiment.

[0030] The processor 118 may be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functions that enable the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120 which can be coupled to a transmit / receive element 122. Figure 1B depicts the processor 118 and transceiver 120 as separate components, but it will be understood that the processor 118 and transceiver 120 can be integrated together in an electronic package or chip.

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

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

[0033] The transceiver 120 may be configured to modulate the signal transmitted by the transmit / receive element 122 and demodulate the signal received by the transmit / receive element 122. As described above, the WTRU 102 may have multimode capabilities. Therefore, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

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

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

[0036] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. In addition to, or instead of, the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that WTRU102 can acquire location information by any preferred location determination method while maintaining consistency with one embodiment.

[0037] The processor 118 may be further coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connectivity. For example, peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. The peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscope, accelerometer, Hall effect sensor, magnetometer, compass sensor, proximity sensor, temperature sensor, time sensor, geolocation sensor, altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor, and / or humidity sensor.

[0038] WTRU102 may include a full-duplex radio in which the transmission and reception of some or all of the signals associated with specific subframes for both UL (e.g., for transmission) and downlink (e.g., for reception) may be in parallel and / or simultaneous. The full-duplex radio may include an interference management unit 139 for reducing and / or substantially eliminating self-interference via either hardware (e.g., chokes) or signal processing via a processor (e.g., via a separate processor (not shown) or processor 118). In one embodiment, WRTU102 may include a half-duplex radio for the transmission and reception of any of the signals (e.g., associated with specific subframes for either UL (e.g., for transmission) or downlink (e.g., for reception)).

[0039] Figure 1C is a system diagram illustrating RAN104 and CN106 according to one embodiment. As described above, RAN104 may employ E-UTRA radio technology to communicate with WTRU102a, 102b, and 102c via the air interface 116. RAN104 may also communicate with CN106.

[0040] RAN104 may include e-nodes B160a, 160b, and 160c, but it will be understood that RAN104 may include any number of e-nodes B while maintaining consistency with one embodiment. Each of e-nodes B160a, 160b, and 160c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, e-nodes B160a, 160b, and 160c may implement MIMO technology. Thus, e-node B160a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU102a.

[0041] Each of the e-nodes B160a, 160b, and 160c may be associated with a specific cell (not shown) and may be configured to handle wireless resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. As shown in Figure 1C, the e-nodes B160a, 160b, and 160c may communicate with each other via the X2 interface.

[0042] The CN106 shown in Figure 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Although each of the aforementioned elements is depicted as part of CN106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0043] The MME162 can be connected to each of the e-nodes B162a, 162b, and 162c in RAN104 via the S1 interface and can function as a control node. For example, the MME162 may perform roles such as authenticating users of WTRU102a, 102b, and 102c, activating / deactivating bearers, and selecting a specific serving gateway during the initial attachment of WTRU102a, 102b, and 102c. The MME162 may provide control plane functionality for switching between RAN104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0044] SGW164 can be connected to each of the e-nodes B160a, 160b, and 160c in RAN104 via the S1 interface. Generally, SGW164 can route and forward user data packets to and from WTRU102a, 102b, and 102c. SGW164 can also perform other functions, such as anchoring the user plane during e-node B handovers, triggering paging when DL data is available to WTRU102a, 102b, and 102c, and managing and remembering the context of WTRU102a, 102b, and 102c.

[0045] SGW164 may be connected to PGW166, which may provide WTRU102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices.

[0046] CN106 can facilitate communication with other networks. For example, CN106 can provide WTRU102a, 102b, and 102c with access to a circuit-switched network such as PSTN108 to facilitate communication between WTRU102a, 102b, and 102c and conventional terrestrial line communication devices. For example, CN106 may include, or communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that acts as an interface between CN106 and PSTN108. In addition, CN106 may provide WTRU102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0047] Although the WTRU is described as a wireless terminal in Figures 1A to 1D, in certain representative embodiments, such a terminal is intended to be able to use a wired communication interface with a communication network (e.g., temporarily or permanently).

[0048] In a typical embodiment, the other network 112 may be a WLAN.

[0049] A WLAN in Basic Service Set (BSS) mode may have access points (APs) of the BSS and one or more stations (STAs) associated with the APs. APs may have access to or interfaces with a Distribution System (DS) or another type of wired / wireless network that carries traffic within and / or outside the BSS. Traffic originating outside the BSS and destined for an STA may reach and be delivered to the STA via an AP. Traffic originating from an STA for a destination outside the BSS may be sent to an AP to be delivered to its respective destination. Traffic between STAs within the BSS may be sent, for example, via an AP, where a source STA may send traffic to an AP, and the AP may deliver the traffic to a destination STA. Traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent between a source STA and a destination STA (e.g., directly between them) using a direct link setup (DLS). In certain typical embodiments, the DLS may be an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using Independent BSS (IBSS) mode may not have APs, and STAs within or using the IBSS (e.g., all STAs) may communicate directly with one another. The IBSS mode of communication may also be referred to herein as an “ad-hoc” communication mode.

[0050] When using the 802.11ac infrastructure operating mode or a similar operating mode, an AP may transmit beacons on a fixed channel, such as the primary channel. The primary channel may be of a fixed width (e.g., a 20 MHz bandwidth) or a width dynamically set via signaling. The primary channel may be the operating channel of the BSS, but may be used by an STA to establish a connection with the AP. In certain typical embodiments, for example, in an 802.11 system, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented. In the case of CSMA / CA, an STA, including the AP (e.g., all STAs), may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, that STA may be backed off. A single STA (e.g., only one station) may transmit at any given time in a given BSS.

[0051] High-throughput (HT) STAs may use a 40 MHz wide channel for communication, which may be formed, for example, through a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels.

[0052] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. 160 MHz channels can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels, which may be referred to as an 80+80 configuration. In the 80+80 configuration, after channel coding, the data can pass through a segment parser that can split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed separately for each stream. The streams may be mapped to two 80 MHz channels, and the data can be transmitted by a transmitting STA. At the receiver of a receiving STA, the operation described above for the 80+80 configuration may be reversed, and the combined data may be sent to Medium Access Control (MAC).

[0053] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports bandwidths of 5 MHz, 10 MHz, and 20 MHz in the TV White Space (TVWS) spectrum, while 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using the non-TVWS spectrum. According to a typical embodiment, 802.11ah may support meter-type control / machine-type communications, such as MTC devices within a macro communication range area. MTC devices may have limited capabilities, including support for specific and / or limited bandwidths (e.g., support for these only). MTC devices may include batteries with battery life exceeding a threshold (e.g., to maintain very long battery life).

[0054] A WLAN system capable of supporting multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah includes a channel that can be designated as the primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by an STA from among all STAs operating in a BSS that support the minimum bandwidth operating mode. In an 802.11ah embodiment, the primary channel may be 1 MHz wide for an STA (e.g., an MTC type device) that supports (e.g., only) the 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. For example, if the primary channel is busy due to an STA (which only supports 1MHz operating mode) transmitting to the AP, the entire available frequency band may be considered busy, even though a large portion of the frequency band remains idle and could potentially be available.

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

[0056] Figure 1D is a system diagram illustrating RAN113 and CN115 according to one embodiment. As described above, RAN113 may employ NR radio technology to communicate with WTRU102a, 102b, and 102c via the air interface 116. RAN113 may also communicate with CN115.

[0057] RAN113 may include gNB180a, 180b, and 180c, but it will be understood that RAN113 may include any number of gNBs while maintaining consistency with one embodiment. Each of gNB180a, 180b, and 180c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, gNB180a, 180b, and 180c may implement MIMO technology. For example, gNB180a and 108b may use beamforming to transmit signals to and from gNB180a, 180b, and 180c. Thus, gNB180a may, for example, use multiple antennas to transmit and / or receive radio signals to and from WTRU102a. In one embodiment, gNB180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB180a may transmit multiple component carriers to WTRU102a (not shown). A subset of these component carriers may be on the unauthorized spectrum, while the remaining component carriers may be on the authorized spectrum. In one embodiment, gNB180a, 180b, and 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU102a may receive coordinated transmissions from gNB180a and gNB180b (and / or gNB180c).

[0058] WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c using scalable neurology and associated transmissions. For example, OFDM symbol intervals and / or OFDM subcarrier intervals may vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or having varying absolute time durations).

[0059] gNB180a, 180b, and 180c can be configured to communicate with WTRU102a, 102b, and 102c in standalone and / or non-standalone configurations. In a standalone configuration, WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c without accessing other RANs (e.g., e-nodes B160a, 160b, and 160c). In a standalone configuration, WTRU102a, 102b, and 102c can utilize one or more of gNB180a, 180b, and 180c as mobility anchor points. In a standalone configuration, WTRU102a, 102b, and 102c can communicate with gNB180a, 180b, and 180c using signals in unauthorized bands. In a non-standalone configuration, WTRU102a, 102b, and 102c can communicate / connect with gNB180a, 180b, and 180c, while also communicating / connecting with other RANs such as enodes B160a, 160b, and 160c. For example, WTRU102a, 102b, and 102c can implement DC principles for substantially simultaneous communication with one or more gNB180a, 180b, and 180c and one or more enodes B160a, 160b, and 160c. In a non-standalone configuration, enodes B160a, 160b, and 160c can function as mobility anchors for WTRU102a, 102b, and 102c, and gNB180a, 180b, and 180c can provide additional coverage and / or throughput to service WTRU102a, 102b, and 102c.

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

[0061] The CN115 shown in Figure 1D may include at least one AMF182a, 182b, at least one UPF184a, 184b, at least one Session Management Function (SMF)183a, 183b, and optionally a Data Network (DN)185a, 185b. Although each of the aforementioned elements is depicted as part of the CN115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0062] AMF182a and 182b can be connected to one or more gNB180a, 180b, and 180c in RAN113 via the N2 interface and can function as control nodes. For example, AMF182a and 182b may be responsible for user authentication of WTRU102a, 102b, and 102c, support for network slicing (e.g., handling different PDU sessions with different requirements), selection of specific SMF183a and 183b, management of registration areas, termination of NAS signaling, and mobility management. Network slicing may be used by AMF182a and 182b to customize CN support for WTRU102a, 102b, and 102c based on the type of service utilizing WTRU102a, 102b, and 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, and services for machine type communication (MTC) access. The AMF162 may provide control plane functionality for switching between RAN113 and other RANs (not shown) employing other radio technologies such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0063] SMF183a and 183b can be connected to AMF182a and 182b in CN115 via the N11 interface. SMF183a and 183b can also be connected to UPF184a and 184b in CN115 via the N4 interface. SMF183a and 183b can select and control UPF184a and 184b and configure the routing of traffic through UPF184a and 184b. SMF183a and 183b can perform other functions such as managing and assigning IP addresses for WTRUs, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0064] UPF184a and 184b may be connected via the N3 interface to one or more gNB180a, 180b, and 180c in RAN113, thereby providing WTRU102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices. UPF184 and 184b may perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multiple home PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0065] CN115 can facilitate communication with other networks. For example, CN115 may include, or communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that functions as an interface between CN115 and PSTN108. In addition, CN115 may provide WTRU102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRU102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via UPF184a, 184b through an N3 interface to UPF184a, 184b, and an N6 interface between UPF184a, 184b and DN185a, 185b.

[0066] In view of Figures 1A to 1D and their corresponding descriptions, one or more of the functions described herein with respect to one or more of the WTRU102a to d, base stations 114a and b, e-nodes-B160a to c, MME162, SGW164, PGW166, gNB180a to c, AMF182a to ab, UPF184a and b, SMF183a and b, DN185a and b, and / or any other devices described herein, may be performed by one or more emulation devices (not shown). An emulation device may be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0067] Emulation devices may be designed to implement one or more tests of other devices in a laboratory and / or carrier network environment. For example, one or more emulation devices may perform one or more or all functions while fully or partially implemented and / or deployed as part of a wired and / or wireless network to test other devices in a communications network. One or more emulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless network. Emulation devices may be directly coupled to another device for testing purposes and / or perform tests using terrestrial wireless communications.

[0068] One or more emulation devices may perform one or more functions, including all of the above, while not implemented / deployed as part of a wired and / or wireless communication network. For example, an emulation device may be used in a test laboratory test scenario, and / or in a wired and / or wireless communication network that is not deployed (e.g., for testing purposes), to implement testing of one or more components. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation device to transmit and / or receive data.

[0069] The systems, methods, and / or apparatus provided herein may relate to the grouping of WTRUs. For example, one or more methods for optimizing DRX to NES conditions, such as group-based intermittent reception (DRX), may be provided herein.

[0070] The systems, methods, and / or apparatus provided herein may relate to paging. Optimization of paging occasions and / or frames to align with network energy-saving (NES) conditions may be described herein. Monitoring of paging in alternate serving cells may be provided herein. For example, a WTRU may monitor paging in one or more alternate cells if the best serving cell and / or camp cell (based on one or more measured channel states) is in a particular availability state (e.g., deep sleep, dormant, and / or off) and / or does not detect presence signals associated with the best cell (e.g., discovery signals, synchronization signal blocks (SSBs), reference signals, and / or physical downlink control channels (PDCCHs) transmitted from cells in the NES) in a potentially different synchronization signal (SS). Instructions for NES-based subgroups in early paging (PEI) may be provided herein. For example, a WTRU may monitor PEI with cell-specific subgroups if the best serving cell is sleeping. PEI may be received from the same best cell and / or different cells. Delayed paging based on the detection of cell signal blocks and / or the absence of signal detection may be provided herein.

[0071] As described herein, channel state information (CSI) may include one or more of the following: channel quality index (CQI), rank indicator (RI), precoding matrix index (PMI), L1 channel measurement (e.g., reference signal received power (RSRP) such as L1-RSRP, or signal-to-interference and noise ratio (SINR)), CSI-reference signal (CSI-RS) resource indicator (CRI), physical broadcast channel (PBCH) block resource indicator (SSBRI), layer indicator (LI), and / or any other measured quantities measured by WTRU from configured CSI-RS or SS / PBCH blocks.

[0072] As described herein, uplink control information (UCI) may include one or more of the following: CSI, hybrid automatic repeat request (HARQ) feedback for one or more HARQ processes, scheduling request (SR), link recovery request (LRR), setting grant or cell group (CG-UCI), and / or one or more other control information bits that may be transmitted over a physical uplink control channel (PUCCH) and / or a physical uplink shared channel (PUSCH).

[0073] As described herein, channel status can refer to one or more (e.g., any) status of radio / channel status which can be determined by WTRU based on one or more WTRU measurements (e.g., L1 / SINR / RSRP, CQI / modulation and coding scheme (MCS), channel occupancy, received signal strength indicator (RSSI), power headroom, exposure headroom), L3 / mobility-based measurements (e.g., RSRP, reference signal received quality (RSRQ)), radio link monitoring (RLM) status, and / or channel availability in unlicensed spectrum (e.g., whether the channel is occupied based on a listen-before-talk (LBT) procedure determination and / or whether a consistent LBT failure is deemed to have occurred on the channel).

[0074] As described herein, a physical random access channel (PRACH) resource may refer to a PRACH resource (e.g., in frequency), a PRACH occasion (RO) (e.g., in time), a preamble format (e.g., in terms of total preamble duration, sequence length, guard time duration, and / or cyclic prefix length), and / or a specific preamble sequence used for transmitting a preamble in a random access procedure.

[0075] Scheduling information (e.g., uplink grants and / or downlink allocations) may include one or more of the following: frequency allocation, time allocation (e.g., mode of time allocation such as duration), priority, modulation and coding scheme, transport block (TB) size, one or more (e.g., a certain number) spatial layers, one or more (e.g., a certain number) transport blocks being carried, transmission configuration indicator (TCI) status and / or SRS resource indicator (SRI) (e.g., SRI may indicate uplink PUSCH spatial relation information), one or more (e.g., a certain number) iterations, and / or whether the grant is a configured grant type 1, type 2, or dynamic grant.

[0076] Downlink control information (DCI) and / or one or more (e.g., any) other (e.g., appropriate) instructions may include one or more of the following: instructions for values ​​used to mask the cyclical redundancy check (CRC) of the PDCCH (e.g., explicit instructions by the DCI field and / or by the radio network temporary identifier (RNTI)); implicit instructions by properties such as the DCI format, DCI size, core set or search space, aggregation level, and the identity of the first control channel resource for the DCI (e.g., the index of the first control channel element (CCE)) (where the mapping between properties and values ​​may be signaled by radio resource control (RRC) and / or medium access control (MAC)); and / or explicit instructions (e.g., by the downlink (DL) MAC control element (CE)).

[0077] The terms network availability status and NES status may be used interchangeably in this specification.

[0078] The terms selected cell, best cell, first cell, best measured cell, serving cell, and / or camp cell may be used interchangeably in this specification.

[0079] In one or more (e.g., a specific) networks (e.g., NRs), system information (SI) may include a master information block (MIB) and / or one or more (e.g., a certain number) system information blocks (SIB). For example, an SIB may be divided into a minimum SI and other SIs. The minimum SI may contain information used for initial access and / or to retrieve one or more (e.g., any other) SIs. The minimum SI may include the MIB and / or SIB1. For a WTRU to camp on to a cell, the WTRU may have already retrieved (e.g., must have retrieved) the contents of the cell's minimum SI.

[0080] One or more other SIs may include SIBs (e.g., all SIBs) that are not broadcast in the minimum SI. A WTRU may not receive an SIB until it accesses the cell (e.g., it may not need to receive one). Additionally or alternatively, other SIs may be called on-demand SIs (for example, a gNB may transmit and / or broadcast these SIBs only when explicitly requested by one or more WTRUs, for example, to conserve network energy).

[0081] The MIB may contain cell prohibition status information and / or cell (e.g., required) physical layer information (which may be used to receive further system information, e.g., CORESET#0 settings). The MIB may be broadcast periodically on a broadcast channel (BCH) (e.g., the MIB may be transmitted with a periodicity of 80ms (in which case repeated transmissions may occur) and / or within 80ms).

[0082] SIB1 may include scheduling for one or more other system information blocks and / or specific information used for initial access. Additionally or alternatively, SIB1 may be referred to as the remaining minimum SI (RMSI) and / or may be periodically broadcast on a DL shared channel (SCH) and / or may be transmitted on a dedicated DL-SCH to one or more WTRUs in the RRC_CONNECTED state.

[0083] Figure 2 shows an example related to the time / frequency structure of an SSB. The synchronization signal and PBCH block (SSB) may include a primary synchronization signal and / or a secondary synchronization signal (PSS, SSS). For example, one or more of the PSS and / or SSS (e.g., each) may occupy one symbol and 127 subcarriers. The PBCH may consist of three orthogonal frequency-division multiplexing (OFDM) symbols and 240 subcarriers, although the symbols on both sides of the SSS may be unused, as shown in Figure 2. The time position in which an SSB may exist in a half-frame may be determined by the subcarrier spacing. The periodicity of the half-frame in which the SSB is transmitted may be set by the network. During a half-frame, different SSBs may be transmitted in one or more different spatial directions (e.g., using different beams that extend across the cell's coverage area).

[0084] One or more (e.g., multiple) SSBs may be transmitted within the carrier frequency span. The physical cell IDs (PCIs) of SSBs transmitted at different frequency locations do not have to be unique (e.g., different SSBs in the frequency domain may have different PCIs). When an SSB is associated with an RMSI, the SSB may be referred to as a cell-defined SSB (CD-SSB). A primary cell (PCell) may be associated with a CD-SSB located on a synchronous raster.

[0085] For example, unless the network has configured the WTRU to determine (e.g., assume) different subcarrier spacings, the WTRU may determine (e.g., assume) a band-specific subcarrier spacing for SSB. One or more (e.g., several) beams may be associated with a given cell, and / or one or more (e.g., multiple) SSBs may be transmitted within a given cell using one or more different beams (e.g., beam sweeping).

[0086] Figure 3 shows an example related to beam sweeping. As shown in Figure 3, one or more SSBs (e.g., 302a, 302b, 302c, 302d, 302e, 302f, 302g, 302h) may be transmitted at specific intervals. For example, each SSB may be identified by a unique number (e.g., an SSB index mapped to each beam, referred to as the SSB index). For example, SSB 302a may have a unique identifier 0 (SSB0), SSB 302b may have a unique identifier 1 (SSB1), SSB 302c may have a unique identifier 2 (SSB2), SSB 302d may have a unique identifier 3 (SSB3), SSB 302e may have a unique identifier 4 (SSB4), SSB 302f may have a unique identifier 5 (SSB5), SSB 302g may have a unique identifier 6 (SSB6), and / or SSB 302h may have a unique identifier 7 (SSB7). Each SSB may be transmitted via a specific beam radiated in a specific direction. Each transmitted beam may be spatial (for example, how a WTRU perceives one or more beams). For example, SSB 302a may be transmitted via a specific beam radiated in a different direction than SSB 302b, SSB 302c, and / or SSB 302d.

[0087] One or more (e.g., multiple) WTRUs (e.g., WTRU1 304a, WTRU2 304b) may be located at one or more (e.g., various) locations around gNB 301. A WTRU may measure the signal intensity of each SSB detected over a specific period (e.g., the period of one SSB set). For example, WTRU1 304a may measure the signal intensity of SSB0 302a, SSB1 302b, SSB2 302c, SSB3 302d, SSB4 302e, SSB5 302f, SSB6 302g, and / or SSB7 302h. For example, WTRU2 304b can measure the signal intensity of SSB0 302a, SSB1 302b, SSB2 302c, SSB3 302d, SSB4 302e, SSB5 302f, SSB6 302g, and / or SSB7 302h. From the measurement results (e.g., 308a, 308b), the WTRU (e.g., WTRU1 304a and / or WTRU2 304b) can identify the SSB index with the strongest signal intensity (e.g., 308a, 308b). Referring to the example shown in Figure 3, for example, WTRU1 304a can identify beam #1 306a as having the strongest signal intensity 308a, and / or WTRU2 304b can identify beam #7 306b as the SSB index with the strongest signal intensity 308b.

[0088] The number of different beams being transmitted may be determined by and / or based on how many SSBs are being transmitted within an SSB burst set (e.g., a set of SSBs transmitted within a 5ms window 306 of SSB transmission). In frequency range one (FR1), the maximum number of SSBs in an SSB set may be 4 or 8, while in frequency range two (FR2), the maximum number of SSBs in an SSB set may be 64.

[0089] The WTRU may determine whether transmission and / or reception is possible on one or more (e.g., specific) resources based on network availability states that may imply the power saving status of the gNB (golden network node). Availability states may correspond to network energy saving states and / or gNB activity levels. Availability states may be uplink (UL) or downlink (DL) specific and / or may change per symbol, per slot, per frame, and / or at a longer duration granularity. The WTRU may determine availability states and / or the network may indicate availability states. Availability states may include, for example, On, DL and UL active, UL active (e.g., UL only active), Off, Transmit (Tx) power reduced, Hibernate, Microsleep, Light sleep, and / or Deep sleep. These states may be abstracted by one or more network configuration parameters and / or values. As described herein, the WTRU may determine the network availability state based on instructions (e.g., dynamic instructions). For example, an indication of active availability status (e.g., a dynamic indication) may be sent to the WTRU (e.g., by DCI or MAC CE signaling). For example, an off availability state may imply that the gNB's baseband hardware is turned off. A sleep availability state may imply that the gNB periodically wakes up to transmit one or more (e.g., specific) signals (e.g., presence signals, synchronization, and / or reference signals) and / or receive one or more (e.g., specific) UL signals. In one or more (e.g., several) availability states, one or more (e.g., specific) DL and / or UL resources may be made unavailable for one or more (e.g., specific) periods, thereby allowing the network to turn off baseband processing and / or one or more other activities. One or more (e.g., several) measurement resources (e.g., SSB and / or CSI-RS) may be made available in one or more (e.g., specific) availability states (e.g., may only be available in those states). In addition, or alternatively, one or more (e.g., specific) measurements (e.g., RLM, beam failure detection (BFD), radio resource management (RRM) measurements, CSI-RS feedback settings, CSI feedback, etc.) may be performed and / or reported (e.g., may only be performed in specific availability states) under certain availability conditions.

[0090] In one or more (e.g., specific) scenarios, a WTRU may change the network's availability state by sending (e.g., further) requests to the network (e.g., wake-up requests). For example, a WTRU may request a change in the network's availability state to a state in which one or more resources that satisfy one or more WTRU requirements become available. Such a wake-up request may include a transmission that can be decoded by a low-complexity receiver in a gNB, which may minimize energy consumption. As described herein, wake-up requests, turn-on requests, and / or switch-on WTRU support information may be used interchangeably. In one or more (e.g., specific) availability states (e.g., microsleep and / or deep sleep), a wake-up request may be used (e.g., exclusively) and / or refer to a physical uplink signal sent by the WTRU to request a change in the network's availability state. One or more (e.g., various) physical layer designs of the wake-up request signal may be used. Alternatively, a switch-on request may be a physical layer (e.g., and / or layer 2 (L2)) instruction from the WTRU to the network, which may be delivered via MAC CE, UCI, RRC signaling, and / or RRC reconfiguration signaling (e.g., applicable to NES), PUCCH, and / or random access channel (RACH) instructions. For example, a switch-on request may include switch-on WTRU support information and / or positioning reports.

[0091] WTRU can determine the availability status, for example, based on the received availability status indication. For example, availability status indicators may be received and / or determined via Layer 1 (L1) / L2 signaling (e.g., group common DCI and / or indicators) (e.g., implicitly determined based on the reception or absence of periodic DL signaling). A WTRU may determine, for example, that a first cell is no longer in an NES state when a page is received via that first cell.

[0092] The WTRU may determine whether resources are available for transmission / reception and / or measurement related to the determined network availability state, for example, whether they are applicable in an active availability state. Additionally or alternatively, the WTRU may optimize its active connected mode DRX (C-DRX) cycle. Additionally or alternatively, the WTRU may optimize its active spatial elements (e.g., antennas or logical ports). Additionally or alternatively, the WTRU may optimize its active transmission / reception points (TRPs). Additionally or alternatively, the WTRU may optimize its paging occasions depending on the signaled and / or determined NES state. The WTRU may be configured with one or more sets of NES transmission and / or reception parameters (e.g., for each NES state). For example, a WTRU may be configured with one or more sets of NES transmit and / or receive parameters via signaling (e.g., broadcast and / or dedicated configuration signaling). A WTRU may apply a set of NES parameters according to the determined and / or signaled NES state. A WTRU may apply one or more applicable settings based on the determined NES state (e.g., accordingly). For example, this set of NES parameters may include one or more (e.g., a certain number) antenna ports, C-DRX settings, measurement settings (e.g., for RRM, RLM, and / or BFD), CSI-RS settings, SSB settings, conditional handover (CHO) or mobility candidates, and / or a set of active TRPs.

[0093] Availability states may be applicable to one or more transmit, receive, and / or measure resources. Availability states may be applicable to one or more time periods, such as time slots and / or time symbols. Availability states may be applicable to serving cells, cell groups, frequency bands, bandwidth portions, TRPs, sets of spatial elements, and / or ranges of frequencies within a bandwidth portion. For example, if the NES changes in a cell, the WTRU may receive an availability state change directive indicating that the change in state applies to that cell (e.g., only that cell). In the example, if the NES changes in a cell, the WTRU may receive an availability state change directive indicating that the change in state applies to a specific cell (e.g., all cells at the same frequency). In the example, if the NES changes in a cell, the WTRU may receive an availability state change directive indicating that the change in state applies to all cells in the same RAT.

[0094] A WTRU may determine the active availability state associated with a cell, carrier, TRP, and / or frequency band as off, deep sleep, and / or microsleep, based on (e.g., subsequently) the reception of DL signaling that modifies the availability state of one or more TRPs and / or one or more cells. For example, a WTRU may receive turn-off commands via broadcast signaling, RRC signaling, DCI (e.g., group common DCI), and / or DL ​​MAC CE (e.g., the instruction portion of PDSCH). A WTRU may determine the availability state based on availability state indications (e.g., their reception), which may be received via L1 / L2 signaling (e.g., group common DCI and / or indications). For example, a WTRU may determine a change in NES state based on the reception of group-common command L1 signaling (e.g., group-common DCI, multi-stage DCI, specific DCI formats, and / or DCI scrambled by configuration and / or specified NES-specific RNTI). The L1 signaling may indicate one of the configuration NES parameter sets to apply. Based on the L1 signaling, once the WTRU has determined the NES state change, it may determine the delta configuration from the current set of parameters. The WTRU may, for example, send feedback and / or acknowledgment to the gNB following the reception of the NES state change instruction. For example, the feedback and / or acknowledgment may be multiplexed with UL data (e.g., MAC CE and / or part of the UL TB as a subheader instruction) based on (e.g., following) the reception of the NES state change instruction.

[0095] In the example, the WTRU may determine a change in NES state based on the reception of broadcast signaling related to NES state indications and / or changes. For example, a change in NES state may be received via one or more SIBs and / or signaling in part of a broadcast and / or multicast PDSCH. Additionally or alternatively, the NES may be indicated to the WTRU in an SIB (e.g., explicitly indicated). The WTRU may be configured with one or more SIBs related to (e.g., exclusively related to) the configuration of NES parameters. For example, the WTRU may be configured to receive such broadcast and / or multicast indications (e.g., SIBs related to the configuration of NES parameters) (e.g., periodically). The WTRU may receive broadcast signaling and / or one or more SSB transmissions and, based on the received broadcast signaling and / or one or more properties related to one or more SSB transmissions, determine a first (e.g., serving, best, camping) cell and / or a second (e.g., non-serving) cell. The WTRU may determine that a misdetection has occurred (e.g., a periodic SIB, an indicator) if, for example, the SIB and / or indicator are not received on the expected periodic occasions (for example, if the WTRU is configured to periodically receive SIBs related to the configuration of NES parameters). Additionally or alternatively, the WTRU may determine that a misdetection has occurred (e.g., a periodic SIB, an indicator) if one or more (e.g., a certain number) misdetections are counted. Additionally or alternatively, the WTRU may determine that a misdetection has occurred (e.g., a periodic SIB, an indicator) if a timer has elapsed since the last reception of the NES status indicator. Based on the determination of a misdetection of the NES status indicator (e.g., subsequently), the WTRU may initiate one or more of the following: Based on the determination of a misdetection of the NES status indicator (e.g., subsequently), the WTRU may initiate an inter-cell measurement. The WTRU may initiate inter-frequency measurements based on (for example, subsequently) a determination of a false detection of the NES status indication.The WTRU may initiate RAT-to-RAT measurements based on (for example, subsequently) the determination of a false positive in the NES status indicator. The WTRU may initiate mobility procedures following the determination of a false positive in the NES status indicator. The WTRU may initiate evaluation of the configured CHO candidates following the determination of a false positive in the NES status indicator.

[0096] WTRU may determine (e.g., implicitly determine) a specific availability state (e.g., off, deep sleep, microsleep, and / or hibernate) related to a cell, carrier, TRP, and / or frequency band from one or more of the following:

[0097] A WTRU may determine the availability status based on the reception of commands and / or signals indicating a change in availability status. Commands and / or signals may include group common DCI in connection mode, and / or RRC signaling, and / or presence signals. A WTRU may determine (e.g., implicitly) the availability status based, for example, the reception of periodic DL signaling. A WTRU may be configured and / or specified to associate the availability status with one or more DL signal types (e.g., SSB, partial SSB, and / or one or more periodicities).

[0098] A WTRU may determine availability based on the reception of paging messages, paging DCIs, paging PDSCHs, paging-related signals (e.g., early paging notification (PEI)), and / or a subset of paging occasions (POs) (e.g., POs consistent with a configured subset of NES DRX cycles and / or PDCCH resources). A WTRU may determine (e.g., assume) that a given NES is active based on the reception of the DCI and / or PDCHH scheduling paging instruction portion (e.g., depending on P-RNTI, NES-RNTI). Additionally or alternatively, a WTRU may determine (e.g., assume) that a given NES is active based on the reception of an instruction (e.g., an explicit instruction) (e.g., on reserved bits). One or more of the following may apply: A WTRU may determine availability based on the reception of paging messages having a specific P-RNTI, a separately configured NES P-RNTI, and / or NES group RNTI. A WTRU may determine the availability status based on (e.g., after) the receipt of a paging message having a specific P-RNTI. A WTRU may have one or more PEI subgroups configured for an NES, where the subgroups may be associated with one or more availability statuses. For example, a first PEI subgroup may be associated with a second cell (e.g., a non-serving cell). For example, a second PEI subgroup may be associated with a first cell (e.g., a camp cell). (For example, if an NES subgroup has a specific availability status configured and / or associated with it,) a WTRU may determine the availability status based on the receipt of a PEI having the NES subgroup. An availability status or availability status switch instruction may be indicated in the paging payload, for example, as a flag portion of a paging message and / or short message. Such a paging instruction may (e.g., further) instruct one or more other cells to monitor paging while the cell from which the received signaling originated is off, sleep, and / or in an NES state.Such paging instructions may (for example) further indicate and / or signal one or more applicable reset parameters (for example, initial access, applicable PRACH resources, applicable SSB / RS occasions, applicable SI cycles, and / or one or more applicable cells and / or associated availability states).

[0099] WTRU can determine availability status based on the gNB's DTX status (e.g., whether the gNB is within active time and / or whether the associated activity timer is running).

[0100] A WTRU may determine the availability state based on the detection (e.g., or absence) of a presence indicator. One or more of the following may apply: For example, a WTRU may determine the availability state associated with a cell (e.g., off and / or deep sleep) if a presence indicator was not detected in one or more presence indicator occasions. A WTRU may determine the availability state based on the detection (e.g., or absence) of a presence indicator. For example, a WTRU may determine (e.g., assume and / or change) the availability state of a cell based on (e.g., a certain number) consecutive false detections and / or based on the timer expiring after the presence signal could not be detected. A WTRU may determine that the availability state is active or inactive after the timer associated with the availability state has expired. In the example, the timer may be set and / or maintained in one or more (e.g., specific) states and / or modes (e.g., connected mode only). In the example, the timer may be set and / or maintained in certain other states (e.g., idle state, inactive state). For example, a WTRU may determine an availability state based on the detection (e.g., or absence) of a presence indication. A WTRU may (e.g., implicitly) determine an availability state based on the failure to detect periodic DL signaling (e.g., the absence of periodic DL signaling reception). For example, a WTRU may have a signal quality threshold (e.g., an RSRP threshold). A WTRU may determine (e.g., assume) that an availability state is inactive and / or determine (e.g., assume) that a different availability state is active if, for example, the WTRU does not detect signals associated with an availability state that have a signal intensity above a threshold (e.g., presence signals and / or SSBs). Additionally or alternatively, a WTRU may determine (e.g., assume) that an availability state is inactive based on the failure to detect the identification sequence of a presence signal (e.g., detection of a PSS sequence).

[0101] A WTRU may determine availability status based on time and date. One or more of the following may apply: A WTRU may be configured to determine (e.g., automatically determine, automatically assume) a specific availability status (e.g., off, sleep, or hibernate) for a set subset of cells (e.g., capacity boosting cells) based on time and date (e.g., accordingly). For example, a WTRU may determine that a capacity boosting cell is available on for a first set of hours in a day, in deep sleep for a second set of hours in a day, and / or off for a third set of hours in a day.

[0102] WTRU may determine availability status based on the availability status of related cells (e.g., another carrier in the same MAC entity, another carrier in the same cell group, another carrier in the same gNB, another sector in the same gNB, and / or configured related cells and / or capacity boosting cells).

[0103] WTRU can determine availability status based on the detection of PSS signals (e.g., PSS-only signals) and / or SSB signals (e.g., simplified / stripped-down SSB signals).

[0104] WTRU can determine availability status based on the detection (e.g., or absence) of RS signals (e.g., CSI-RS, positioning reference signal (PRS), TRS).

[0105] The availability status of a WTRU can be determined based on its RRC status (e.g., Idle, Inactive, and / or Connected).

[0106] WTRU can determine availability status based on whether a paging message was received (for example, within a configured time window).

[0107] WTRU can determine availability status based on whether system information (e.g., a subset of periodic SIs and / or SIBs) has been received (e.g., within a set time window).

[0108] A WTRU may determine availability status based on one or more measured channel states falling below or above a threshold. For example, a WTRU may determine (e.g., assume) a change in NES status based on changes in one or more measured channel states. For example, a WTRU may determine (e.g., assume) a change in NES status based on channel measurements falling below (e.g., or above) a threshold. For example, a WTRU may determine NES status using degradation in one or more measurements of SSB and / or CSI-RS (e.g., in combination with other signaling). For example, a WTRU may measure one or more SSB and / or CSI-RS for degradation using a window set after DCI reception. A WTRU may determine that NES status has changed and / or determine (e.g., assume) one or more associated actions for such NES status (e.g., triggers for CHO candidate selection and / or group scheduling for mobility commands) if, for example, a delta of SSB-RSRP drop is measured.

[0109] A WTRU may be configured to monitor indicators that can characterize a level of network activity (e.g., availability status). Network activity may be related to a gNB and / or cell. A WTRU may assume the same availability status for one or more cells (e.g., all cells) that are part of the same gNB, e.g., cells of the same MAC entity. Network activity indicators (e.g., presence indicators) may include channels (e.g., PDCCHs) and / or signals (e.g., sequences). Activity indicators (e.g., NES state change indicators / commands) may indicate a level of activity (e.g., low activity, high activity, neutral activity) that the WTRU can expect from the relevant gNB and / or cell. Additionally or alternatively, activity indicators may include activity information from other gNBs / cells. Activity indicators may be received via PDCCH transmissions that include group common signaling. For example, a network may transmit group common DCIs (e.g., WTRUs in a serving cell) to a group of WTRUs indicating changes in activity status and / or activity levels (e.g., in UL and / or DL). The CRC of the PDCCH may be scrambled with RNTIs (e.g., dedicated activity instruction RNTIs, NES-RNTIs). The WTRU may have one or more search spaces related to the monitoring occasion of the activity instruction PDCCH. The instruction may include a go-to-sleep signal, e.g., a predefined sequence. For example, if the WTRU detects a go-to-sleep signal, the WTRU may anticipate a low activity level (e.g., over a specific duration). For example, the WTRU may activate the C-DRX for the indicated period. Additionally or alternatively, one or more (e.g., two) sequences may be used to indicate (e.g., normal) activity and / or low activity.

[0110] Signaling and / or activity indications within a PDCCH may include one or more of the following: The signaling and / or activity indications within a PDCCH may include the expected activity level (e.g., availability state) of the associated gNB / cell over a specific time interval. One or more activity levels may be predetermined and / or set. For example, activity levels may include normal activity, low activity, neutral activity, etc. Signaling may indicate activity levels. For example, if a bit in the signal is set to 1, normal activity may be indicated. In the example, if a bit in the signal is set to 0, low activity may be indicated.

[0111] Signaling and / or activity indications within a PDCCH may include transmit and / or receive attributes for one or more activity levels (e.g., each availability state). For example, during low activity, it may not be assumed that the WTRU monitors one or more (e.g., specific) PDCCH search spaces (e.g., all SSs), receives specific types of PDSCHs (e.g., all PDSCHs), transmits PUCCH / PUSCHs, and / or performs one or more (e.g., specific) measurements. The WTRU may initiate (and / or deactivate) monitoring of PDCCH resources and / or TCI states associated with a determined NES state. For example, the WTRU may initiate (and / deactivate) monitoring of PDCCH resources and / or TCI states associated with an (de-)activated TRP and / or one or more spatial elements.

[0112] Signaling and / or activity indications within PDCCH may include a set of settings. For example, this set of settings may be related to an activity level and / or be used / applied when that activity level is indicated (e.g., NES parameter set). For example, a set of settings may include SS settings, CSI reporting settings, and an index of transmitted SSBs. One or more of the sets of settings (e.g., each) may include attributes related to an activity level. For example, one or more sets of settings may include tags that can be set for lower activity levels.

[0113] Signaling and / or activity indications within a PDCCH may include time intervals in which the activity level is determined (e.g., assumed to be active). One or more of the following may apply: Time intervals may be signaled in the PDCCH and / or included in activity indications. For example, time intervals may be indicated using a bitmap, where one or more bits in the bitmap may relate to a particular duration, e.g., a slot and / or frame. For example, bit 1 of the bitmap may indicate normal activity, and bit 0 of the bitmap may indicate low activity in the relevant frame. For example, time intervals may be indicated using a start time and the length of the interval. The start time can be defined. For example, the start time can be determined by adding a fixed offset to the time the time instruction is received. The length of the interval can be set and / or signaled via instruction PDCCH.

[0114] Signaling and / or activity indications within the PDCCH may include and may be determined (e.g., predetermined) a time interval in which the activity level is valid (e.g., assumed). The WTRU may determine (e.g., assumed) an interruption delay (e.g., the time until the NES change occurs) based on (e.g., thereafter) the reception of the NES state change command (e.g., thereafter) (e.g., after the last symbol and / or slot in which the command was received). The interruption time may be absolute time. The interruption time may be one or more (e.g., a certain number) symbols. The interruption time may be one or more (e.g., a certain number) slots.

[0115] A WTRU may perform cell reselection (e.g., to a different cell, frequency layer, and / or RAT) based on determining NES changes (e.g., NES changes in camp cells, serving cells, and / or candidate cells for reselection). A WTRU may have alternative serving cells configured and / or predefined for performing initial access, mobility, and / or cell reselection. For example, if the current serving cell and / or capacity boosting cell is turned off, a WTRU may have alternative serving cells configured and / or predefined. Additionally, or alternatively, a WTRU may have alternative serving cells configured and / or predefined if one or more (e.g., specific) conditions are met. A WTRU may have alternative serving cells configured per broadcast, and / or a WTRU may have alternative serving cells configured via dedicated signaling. For example, a WTRU may have a list of one or more fallback and / or alternative serving cells (e.g., per serving cell and / or per gNB). For example, a WTRU may initiate cell reselection and / or mobility procedures for the cell from which the received turn-off instruction originated and / or for an alternative serving cell associated with the gNB. In the example, a turn-off instruction and / or go-to-sleep instruction may indicate to the WTRU, for example, by dedicated signaling and / or broadcast signaling, which cell to fall back to and / or connect to (for example, dynamically). The fallback / alternative cell may be configured and / or predefined to be a cell within the same gNB whose sector has entered an NES state (e.g., off, sleep, and / or low-power state). In the example, the fallback cell may be predefined (e.g., as the master node cell if the WTRU is in dual connectivity). The fallback / alternative cell may be configured and / or predefined to be a cell associated with a different RAT and / or frequency band.For example, a WTRU may fall back to the cell that originated the received turn-off instruction and / or the gNB-related LTE or FR1 cell (for example, if the WTRU is in a carrier aggregation (CA) and / or DC using one or more (e.g., multiple) RATs and / or multiple frequency bands).

[0116] The WTRU may determine that uplink and / or downlink resources, and / or signals, are available for transmission and / or reception. The WTRU may perform one or more measurements on the determined network availability state, for example, if applicable in an active availability state. The WTRU may determine that a subset of measurement resources and / or signals (e.g., SSB, CSI-RS, TRS, PRS) are not applicable in one or more (e.g., specific) availability states. The WTRU may determine that a subset of uplink or downlink resources (e.g., PRACH, PUSCH, PUCCH) are not applicable in one or more (e.g., specific) availability states. The WTRU may transmit one or more (e.g., several) uplink signals (e.g., sounding reference signal (SRS), pSRS, PRACH, UCI) in a subset of network (NW) availability states (e.g., only in a subset).

[0117] The WTRU may monitor (e.g., monitor for reception) presence indications and / or signals associated with a gNB that has one or more availability states (e.g., on, off, hibernate, and / or deep sleep) set. One or more of the following may apply: The presence indication may be a signal (e.g., a physical downlink signal). For example, the presence indication may be transmitted by the associated cell and / or gNB in ​​sleep mode, which may be in a particular availability state (e.g., deep sleep, microsleep, hibernate, and / or off) (e.g., it may be a physical downlink signal). Additionally or alternatively, the presence indication may be downlink information bits delivered to the WTRU, for example, by broadcast signaling (e.g., SIB) and / or dedicated signaling (e.g., RRC signaling and / or MAC CE).

[0118] The WTRU may change its availability state to one or more detected presence signals (for example, the WTRU may assume it is ON) based on (for example, subsequently) the WTRU's successful reception of a response (for example, from the cell that made the request). The response may include transmitted WTRU support information and / or a switch-on request transmitted by the WTRU. For example, the response may be received via DL signals and / or channels (e.g., SSB, CSI-RS, PRS, PDCCH, DCI, PDSCH, and / or HARQ-ACK) and / or L2 messages (e.g., RRC messages, DL MAC CE, Msg2, MsgB, and / or Msg4). The WTRU may monitor (e.g., initiate monitoring) one or more additional TRP, SSB, and / or CSI-RS resources after transmitting wake-up WTRU support information and / or a switch-on request, and / or based on (for example, subsequently) the successful reception of a response to the support information and / or switch-on request. For example, based on the WTRU's determination (e.g., measurement, measurement successful) that one or more channel states (e.g., RSRP, SINR) of one or more measurement resources in the relevant cells exceed a set threshold, the WTRU may change the availability state associated with the detection of the presence signal (e.g., on).

[0119] The presence indication signal may be one or more of the following: a simplified and / or stripped-down SSB signal (e.g., PSS / SSS without multiplexed PBCH), a wide-beam and / or omnidirectional SSB, PRS, CSI-RS, a signal detected based on energy sensing the ether (e.g., a DL signal associated with a wake-up radio (in a WTRU, if such hardware is capable of detecting it)), a PDSCH and / or PDCCH received in different cells and / or TRPs (e.g., in a configured subset of resources, core sets, and / or search spaces), and / or one or more SSBs received in different cells and / or TRPs (e.g., configured in a subset of SSB occasions).

[0120] In some cases, the network's energy consumption may be significant, or it may be unnecessary, for example, during quiet hours. The network may turn off small cells during quiet hours and / or rely on (e.g., depend on) one or more macrocells for coverage. The network may turn off one or more (e.g., several) sectors and / or gNBs. The network may reduce the power consumption of power amplifiers (PAs). The network may enable sleep patterns on the gNB side (e.g., without significantly impairing WTRU performance). One or more gNBs can combine information (e.g., one or more WTRU measurements, WTRU support information, interference status, load information, proprietary information) to determine how to respond to significant energy consumption (e.g., to add and / or reduce energy consumption).

[0121] From a WTRU perspective, a WTRU may experience coverage loss when one or more capacity cells activate NES. A WTRU may not be aware that a gNB has transitioned to an NES state (e.g., deep sleep and / or hibernation) when the WTRU is idle and / or inactive. To optimize network availability, a WTRU may know whether one or more (e.g., specific) cell signals (e.g., SSB, paging, SI) are being transmitted normally (rather than not being received due to one or more poor / bad channel conditions).

[0122] One or more (e.g., specific) WTRU control plane procedures for connectivity management, WTRU reachability, cell reselection, and / or WTRU battery consumption may be affected when one or more gNBs are sleeping and / or turned off. One or more of the following may apply: One or more paging messages and / or SIs may be affected as described herein. For example, one or more paging messages may be sent by the core network to one or more (e.g., all) gNBs in a RAN paging / notification area. One or more gNBs in the same RAN paging area may send a paging message even if, for example, there is no WTRU in its cell. For example, if one or more gNBs in the same RAN paging area send a paging message and there is no WTRU in its cell, one or more (e.g., many) gNBs may wake up to send a paging message (e.g., even if some gNBs are in a network energy-saving state, sleep and / or hibernation state and / or even if there is a single WTRU to page in the entire notification area). Furthermore, in one or more cases, it may be considered wasteful to keep the WTRU battery monitoring the normal idle-mode DRX cycles for paging. For example, if the gNB is in sleep mode (e.g., according to a different NES cycle and / or the WTRU is not supposed to be paged), it may be considered wasteful to keep the WTRU battery monitoring the normal idle-mode DRX cycles for paging.

[0123] One or more WTRUs in idle mode may not be aware of the gNB's sleep cycle, and / or one or more WTRUs in idle mode may not be aware of whether SIs (e.g., other residual SIs / SIBs) are broadcast by the network according to a regular (e.g., configured) periodicity.

[0124] The systems, methods, and / or apparatus provided herein may relate to the optimization of paging occasions. The systems, methods, and / or apparatus provided herein may relate to paging from different (e.g., second, non-serving) cells. The systems, methods, and / or apparatus provided herein may relate to instructing delayed paging of sleep cells. The systems, methods, and / or apparatus provided herein may relate to instructing one or more upcoming paging from a cell different from a first (e.g., serving, camping) cell (e.g., second, non-serving) cell. The systems, methods, and / or apparatus provided herein may relate to indicating one or more network energy saving (NES) states and / or delayed paging using one or more paging early notification (PEI) subgroups. The systems, methods, and / or apparatus provided herein may relate to muting a subset of physical downlink control channel (PDCCH) paging occasions (POs) that are not aligned with one or more transmitted synchronous signal blocks (SSBs).

[0125] The WTRU may receive configuration information. The WTRU may receive configuration information indicating that the first cell is associated with the second cell. The configuration may include, for example, an instruction that the second cell should be used for Paging Early Notification (PEI) monitoring when the first cell is selected as a camp cell and / or the first cell is in a Network Energy Saving (NES) state. The configuration information may indicate a first PEI subgroup and / or a second PEI subgroup. The first PEI subgroup may be associated with the second cell. The second PEI subgroup may be associated with the first cell. The WTRU may monitor PEI via the second cell, for example, based on a determination that the first cell is in an NES state. The WTRU may receive PEI via the second cell, for example. The WTRU may monitor paging. For example, the WTRU may monitor paging via the second cell, provided that the PEI received via the second cell indicates the first PEI subgroup. For example, a WTRU may monitor paging through a first cell, provided that the PEI received through the second cell indicates a second PEI subgroup. The WTRU may transmit a signal through the first cell if a page is received through the first cell, and / or the WTRU may transmit an instruction through the second cell indicating the identity of the first cell if a page is received through the second cell. The WTRU may, for example, determine that the first cell is no longer in an NES state if a page is received through the first cell.

[0126] A first cell may be associated with a first intermittent reception (DRX) cycle. A second cell may be associated with a second DRX cycle. A WTRU may apply the first DRX cycle, for example, provided that the WTRU is connected to the first cell. A WTRU may apply the second DRX cycle, for example, provided that the WTRU is connected to the second cell. A WTRU may determine the paging frame (PF) and / or paging occasion (PO) of the first or second cell, for example, based on NES-specific WTRU identification information (ID).

[0127] The WTRU may receive broadcast signaling and / or one or more synchronous signal block (SSB) transmissions. The WTRU may determine that one or more SSB transmissions and / or one or more POs are delayed and / or skipped in the first cell. For example, based on the determination that one or more SSB transmissions and / or one or more POs are delayed or skipped in the first cell, the WTRU may determine that a subset of physical downlink control channel (PDCCH) POs for the second DRX cycle will not be transmitted. The WTRU may determine the first and / or second cell by receiving broadcast signaling and / or one or more SSB transmissions. For example, the WTRU may determine the first and / or second cell based on the received broadcast signaling and / or based on one or more properties related to one or more SSB transmissions.

[0128] WTRU can determine a second cell. For example, WTRU can determine a second cell based on one or more channel measurements and / or one or more handover candidate settings.

[0129] The WTRU can determine the NES state of the first cell. The WTRU can determine the NES state of the first cell based, for example, on the reception of a primary synchronization signal (PSS) transmission. The WTRU can determine the NES state of the first cell based, for example, on the reception of a secondary synchronization signal (SSS) transmission. The WTRU can determine the NES state of the first cell based on both the reception of a PSS transmission and the reception of an SSS transmission.

[0130] A WTRU may receive configuration information that includes instructions indicating that a WTRU is included in a set of one or more WTRUs, for example, under the condition that one or more sets of WTRUs are located within one or more cells that are in an NES state. A WTRU may monitor and / or receive one or more group common instructions related to one or more sets of WTRUs in an NES state.

[0131] Systems, methods, and / or apparatus may be provided herein with respect to NES WTRU grouping. For example, one or more techniques relating to WTRU grouping while a network is in an NES state may be described herein. For example, one or more DRX configurations may be optimized to suit the NES state of the network (e.g., group-based DRX).

[0132] This specification describes one or more techniques related to paging while a network is in an NES state. For example, paging occasions and / or frames may be optimized to suit the network's NES state.

[0133] WTRU may monitor paging from alternative serving cells. One or more of the following may apply: For example, WTRU may monitor paging from one or more alternative cells if the serving cell (e.g., the best serving cell and / or camp cell) is in a certain availability state (e.g., deep sleep, hibernation, and / or off). Additionally or alternatively, if the serving cell (e.g., the best serving cell or camp cell), if WTRU is unable to detect presence signals associated with the serving cell (e.g., SSB or PDCCH) (e.g., in different SSs), WTRU may monitor paging from one or more alternative cells.

[0134] PEI may include instructions for NES-based subgroups. One or more of the following may apply: WTRU may monitor PEIs with cell-specific subgroups, for example, when a serving cell (e.g., the best serving cell) is sleeping. For example, PEIs may be received from a serving cell and / or a different cell. WTRU may monitor PEIs via a second cell, for example, based on a determination that a first cell is in an NES state.

[0135] Paging may be delayed, for example, based on the detection (or absence) of a cell signal.

[0136] A WTRU can be grouped with one or more other WTRUs. For example, a WTRU can be grouped with one or more other WTRUs for NES purposes (e.g., an NES WTRU group). For example, an NES WTRU group can be used to control one or more (e.g., a certain number of) WTRUs simultaneously, to indicate a bandwidth part (BWP) switch, to indicate a change in network availability status, to indicate one or more WTRU DRX cycles and / or changes to parameters, for mobility / cell reselection, for paging, and / or to activate and / or deactivate one or more DL measurement resources. A WTRU can receive configuration information that indicates it is part of a set of one or more WTRUs, provided that one or more WTRUs are located in one or more cells that are in an NES state. A WTRU can monitor and / or receive one or more group common indications associated with one or more WTRUs in an NES state. For example, a WTRU may have an NES group RNTI (e.g., an NES group identifier) ​​configured, and the NES group RNTI may be used for signaling and / or communication with one or more WTRUs within the same serving cell. A WTRU may monitor cell-specific DL resources for control and / or to receive data and / or one or more group-common instructions for the NES (e.g., group-common DCI, availability state switching command, NES PCell switching command, etc.).

[0137] A WTRU may have one or more (e.g., non-default) NES DRX cycles configured for use while the WTRU is idle, inactive, and / or connected (e.g., in mode). For example, one or more NES DRX cycles may be configured via SIB and / or RRC signaling. One or more NES DRX cycles may be configured on WTRUs within a cell (e.g., all WTRUs) and / or be cell-specific (e.g., applicable only by WTRUs within the same cell in which it was configured). NES DRX cycles may be used by a WTRU to wake up to read paging (e.g., PDCCH addressed to paging RNTI (P-RNTI)) while one or more idle and / or inactive states. NES DRX cycles may be used by a WTRU for scheduling (e.g., PDCCH addressed to cell RNTI (C-RNTI)) while the WTRU is connected and / or inactive. An NES DRX cycle and / or process may be associated with one or more NES states (e.g., one or more availability states). Such associations may have one or more SSB periodics defined and / or set and / or associated with them. For example, when a WTRU determines that a serving gNB is associated with an energy-saving mode (e.g., an availability state), the WTRU may apply an NES DRX cycle.

[0138] The WTRU may have mappings between SSB patterns, periodicity, and / or periodicity ranges, and / or NES DRX cycles. One or more of the following may apply: For example, if the WTRU determines that the serving gNB has entered a relevant NES state and / or that the relevant NES state should be applied, it may decide to activate the NES DRX cycle, switch to the NES DRX cycle, and / or apply the NES DRX cycle.

[0139] The WTRU may determine that a given serving cell is in a particular availability state (e.g., sleep, hibernate, deep sleep, and / or off) using one or more of the techniques described herein (e.g., based on the absence of signal detection, based on one or more received commands from the NW, and / or based on the reception of signals related to sleep / availability states).

[0140] The WTRU may switch to a given C-DRX cycle (e.g., an NES DRX cycle) upon detecting a signal and / or command (e.g., a group-common DCI, an availability state switching command, an NES PCell switching command, and / or a group-common wake-up signal (WUS) received from a gNB). The WTRU may switch to a different DRX cycle (e.g., a more frequent on-duration and / or a shorter DRX cycle) upon receiving a WUS from a gNB (e.g., a group-common WUS, a dedicated WUS, or an NES-specific group / cell-common WUS). The WTRU may be configured to detect NES-specific group / cell-common WUS. For example, the WTRU may detect an NES-specific group / cell-common WUS based on detecting a differentiated sequence for DL ​​WUS. For example, the WTRU may monitor NES and / or cell-common WUS when a serving cell and / or camp cell is determined to be in an NES state. For example, if a WTRU receives an NES state switching command and / or instruction, the WTRU may monitor the NES and / or cell-common WUS. The WTRU may also monitor the WUS in an NES-specific sequence when a camp cell and / or serving cell is in a given NES state (e.g., deep sleep, off, etc.).

[0141] A WTRU may switch to a given C-DRX cycle (e.g., an NES DRX cycle) based on (e.g., subsequently) the reception of a DRX switch command and / or paging (e.g., subsequently) a paging message, a PEI with a subgroup configured for the NES, a paging DCI and / or PDCCH, and / or a paging PDSCH). The DRX switch command may relate to a subset of paging occasions (POs) (e.g., POs aligned with the NES DRX cycle). A first cell may relate to a first DRX cycle. A second cell may relate to a second DRX cycle. A WTRU may switch to a given C-DRX cycle (e.g., an NES DRX cycle) upon receiving an availability state switch command (e.g., a group common DCI, etc.) and / or a WUS. For example, a WTRU may apply a first DRX cycle, provided that the WTRU is connected to a first cell. For example, a WTRU may apply a second DRX cycle, provided that the WTRU is connected to a second cell. A WTRU may switch to a given C-DRX cycle (e.g., an NES DRX cycle) when it determines that a cell (e.g., a camp cell, a selected cell, a serving cell, and / or the best measured cell) is in a given availability NES state (e.g., off, sleep, hibernate, etc.). For example, a WTRU may perform one or more channel state measurements on one or more detectable cells (e.g., a certain number of cells). A WTRU may designate the best measured cell as the cell having one or more best measurements (e.g., with respect to the channel states described herein).

[0142] Figure 4 illustrates an example related to NES DRX cycle switching while the WTRU is idle / inactive for the NES400. For example, the WTRU may be in (e.g., second) DRX cycles 405a, 405b (e.g., normal DRX cycle, legacy DRX cycle). In 401a, 401b, and / or 401c, for example, the WTRU may monitor one or more POs, paging, PDCCHs, and / or paging PDCCHs (e.g., in relation to second DRX cycles 405a, 405b).

[0143] In 404, the WTRU may receive a message as described herein. Message 404 may include a gNB sleep instruction, a PO skip command, and / or a determination that the serving gNB is in the NES. The WTRU may switch from DRX cycles 405a, 405b to NES DRX cycles 406a, 406b based on message 404, for example (as described herein). A first (e.g., serving, camping, best) cell may be associated with the first DRX cycles 406a, 406b. A second (e.g., non-serving) cell may be associated with the second DRX cycles 405a, 405b. The WTRU may apply the first DRX cycles (e.g., 406a, 406b) when connected to a first (camping, serving, best) cell. When the WTRU is connected to a second (e.g., non-serving) cell, a second DRX cycle 405a, 405b may be applied.

[0144] In the example, one or more POs may be skipped. For example, skipping a paging occasion in (e.g., a second) DRX cycle 405a, 405b and / or configuration may imply that the WTRU monitors paging, PO, PDCCH, and / or paging PDCCH in a different (e.g., a second) DRX cycle (e.g., NES DRX cycle 406). The WTRU may skip monitoring in 411, 412, and / or 413 (e.g., in the second DRX cycle 405a, 405b) if the WTRU is monitoring in the second DRX cycle 406a, 406b in 410b, 410c, 414b, 414c. The WTRU may determine that a subset of PRACH resources is applicable to one or more DRX cycles (e.g., for use when paging is received). For random access (RA) initiated based on (e.g., subsequently) a paging reception, the WTRU may use and / or select one or more PRACH resources (e.g., RO and / or preamble) associated with the DRX cycle that the WTRU is paging and monitoring (e.g., only that resource).

[0145] Paging may be performed based on the NES state. One or more of the following may apply: The WTRU may monitor paging from a cell if the cell is in one or more (e.g., specific) availability states (e.g., on and / or sleep) (e.g., only in those cases) and / or may skip wake-ups in the DRX cycle of that cell if (e.g., otherwise) the cell is in one or more other availability states (e.g., off, deep sleep, and / or hibernate) on occasions. The WTRU may monitor gNB wake-up signaling related to DRX and / or paging (e.g., power-saving DCI (DCP)) in a subset of the cell's availability states (e.g., on or sleep) (e.g., only in those cases). For example, a DCP may include a DCI with a CRC scrambled by a power-saving RNTI (PS-RNTI). The WTRU may use PS-RNTI (for example, for power saving purposes) to determine whether to monitor PDCCH during the next occurrence of the connected mode DRX on duration.

[0146] For example, a WTRU may be configured to send tracking area updates (TAUs) and / or RAN paging area updates (RAUs) on a subset of cells (e.g., only) that are in one or more (e.g., specific) availability states. For example, a WTRU may send TAUs and / or RAUs on a subset of cells (e.g., only) that are in an availability state (e.g., accordingly) (e.g., when a camp cell switches to a specific availability state such as off or deep sleep). A WTRU may avoid sending one or more TAUs on capacity boosting cells, and / or cells that have an availability state determined to be off, hibernating, and / or sleep. A WTRU may trigger and / or send RAUs and / or TAUs if, for example, the WTRU performs mobility and / or cell reselection on a cell that is in an NES state, which may be based on (e.g., accordingly) a change in the NES state between the camp cell and the reselected cell. For example, a WTRU may trigger an RAU and / or TAU if it re-selects itself from an NES cell (e.g., an NES-only cell) to a non-NES cell (e.g., a cell that is not NES-enabled and / or a cell that serves one or more legacy WTRUs). For example, a WTRU may trigger an RAU and / or TAU if it re-selects itself from an NES cell (e.g., an NES-only cell) to a non-NES cell (e.g., a cell that is not NES-enabled and / or a cell that serves one or more legacy WTRUs), even if the WTRU remains in the same paging and / or tracking area. A WTRU may determine from broadcast signaling (e.g., from SIB information) whether a cell is an NES-only cell (e.g., a cell that serves only NES-enabled WTRUs) or a non-NES-only cell (e.g., a cell that serves both legacy WTRUs and NES-enabled WTRUs).Additionally, or alternatively, the WTRU may determine (e.g., implicitly) whether a cell is an NES-only cell or a non-NES-only cell based on one or more SSB receiving properties (e.g., when receiving NES SSB, on-demand SSB, and / or SSB NES-only occasions).

[0147] Paging of sleeping gNBs and / or paging from alternate cells may be reduced. One or more of the following may apply: Paging messages may be sent by the core network to (e.g., all) gNBs in the RAN paging / notification area and / or tracking area (e.g., for inactive WTRUs). One or more gNBs in the same RAN paging area may send the same paging message (e.g., even if there is no WTRU in that cell). If gNBs in the same RAN paging area send the same paging message, one or more (e.g., many) gNBs may wake up to send paging (e.g., if some gNBs are in NES state, sleep state, and / or hibernation state).

[0148] If the WTRU's current best server (e.g., a camp cell, a selected cell, or the best serving cell based on one or more L3 channel measurements) is in an NES state, the WTRU may skip monitoring the PO on that cell (e.g., suspend PDCCH monitoring and / or monitor PDCCH using the NES DRX cycle). For example, if the WTRU determines that the current / previous NES state of a serving gNB is in a particular availability state, the WTRU may ignore the configured and / or default PO cycle and / or monitor paging using the NES DRX cycle. Additionally, or alternatively, if the WTRU has not received an updated NES state change command and / or the timer associated with the availability state change has expired and / or elapsed, the WTRU may ignore the configured and / or default PO cycle and / or monitor paging using the NES DRX cycle.

[0149] The WTRU may continue using the DRX cycle and / or wake up to monitor paging from different or alternative serving cells (e.g., cells in a CA having a camp cell and / or anchor cell). For example, in an idle and / or inactive state, the WTRU may measure and / or monitor one or more signals from one or more alternative serving cells when the best serving cell is in sleep and / or hibernation mode (e.g., a camp cell, a selected cell). The WTRU may receive instructions from the serving cell indicating which one or more alternative cells to monitor paging from while the serving cell (e.g., a camp cell, a selected cell, and / or the best measured cell) is in a state (e.g., NES). A WTRU may be configured (e.g., pre-configured, pre-defined) to monitor one or more designated cells (e.g., specific) related to a cell in the NES state, such as alternate cells, cell portions of the same gNB (e.g., cells in a CA with a camp cell), and / or cells from a secondary node (SN) and / or a master node (MN) (e.g., cells in a DC with a camp cell). A WTRU may monitor paging according to the DRX cycle associated with the monitored alternate cell. A WTRU may monitor paging in alternate serving cells (e.g., the best alternate serving cell, a second cell in a CA, an anchor cell, and / or an unselected cell), adjacent cells of the best server, and / or candidate cells for handover (e.g., if a camp cell or selected cell is in a particular availability state such as sleep, hibernate, and / or off). For example, a WTRU may monitor paging on a candidate cell for handover if the best-serving cell (e.g., camp cell, selected cell) is in one or more availability states (e.g., sleep, hibernate, and / or off). For example, if a WTRU detects presence DL signals (e.g., SSB, PDCCH, PBCH, and / or RS) associated with the best-serving cell (e.g., camp cell, selected cell) during the period prior to PO, the WTRU may monitor paging on an alternate cell.

[0150] A WTRU may determine one or more alternate cells to monitor paging based on one or more of the following: A WTRU may decide to monitor paging based on one or more measured channel states. For example, a WTRU may monitor paging from one or more alternate cells (e.g., only those cells) whose measured channel states exceed a set threshold (e.g., RSRP and / or RSRQ exceed the threshold). A WTRU may decide to monitor paging from one or more alternate cells based on each availability state associated with each alternate cell. A WTRU may monitor paging from an alternate cell if the cell is in one or more (e.g., specific) availability states (e.g., only in those cases). A WTRU may decide to monitor paging from an alternate cell based on the reception of a paging PDCCH. For example, a WTRU may monitor an alternate cell if the WTRU detects a PDCCH from that cell. A WTRU may decide to monitor paging from an alternate cell based on the reception of synchronization signals and / or RS signals associated with that alternate cell.

[0151] A WTRU may monitor its alternate cell (for example, further) if the WTRU is downlink-synchronized to the alternate cell (for example, based on reading and / or receiving PSS / SSS, one or more SIBs, SIs, and / or PBCHs associated with the cell). A WTRU may decide to monitor paging from an alternate cell based on instructions received by the WTRU. For example, instructions may be received by the WTRU via one or more previous paging messages (for example, part of one or more previous paging messages) and / or signaled (for example, and / or inferred from) one or more availability state change commands. A WTRU may decide to monitor paging from an alternate cell based on the WTRU's RRC connection status (for example, whether the WTRU is idle and / or inactive). Additionally or alternatively, a WTRU may decide to monitor paging from an alternate cell based on whether the WTRU has its maintained context.

[0152] The WTRU may determine (e.g., identify) a selected cell that has the measured cell (e.g., the best measured cell) and / or the best (e.g., best) L3 measurement (e.g., RSRP). The WTRU may camp on a cell that does not have the best (e.g., best) measured channel state (e.g., RSRP and / or RSRQ). The WTRU may monitor paging in one or more other alternative cells based on one or more of the following, for example: The WTRU may monitor paging in one or more other alternative cells if the WTRU is in an RRC idle state and / or RRC inactive state. The WTRU may monitor paging in one or more other alternative cells based on the type of data being transmitted. For example, the WTRU may monitor paging in one or more alternative cells if one or more data radio bearers (DRBs) (e.g., DRBs configured for small data, DRBs configured for low latency communications, and / or DRBs configured by the network for such purposes) are reactivated. A WTRU may monitor paging in one or more other alternate cells based on the type of active DRB, service, and / or QoS (e.g., configured, activated, and / or restarted flows). A WTRU may monitor paging in one or more other alternate cells based on the WTRU type and / or capability.

[0153] The WTRU may determine a differentiated P-RNTI for the NES (e.g., it may use an alternative P-RNTI). Additionally or alternatively, the WTRU may use the same P-RNTI for the NES (e.g., if the best serving cell, such as a camp cell or selected cell, is determined to be in a particular availability state such as sleep, hibernate, and / or off). The WTRU may use an alternative P-RNTI for DCI reception. For example, the alternative P-RNTI may be selected based on the cell the WTRU is monitoring for paging. The WTRU may receive, via paging messages (e.g., short messages, in part of paging messages), the cell ID (e.g., pointing to a cell ID) from which the received PDSCH originates and / or instructions for the timing of the paging message. The WTRU may use the NES group RNTI for receiving paging (e.g., when paging is monitored in a non-best serving cell and / or non-serving cell). The WTRU may monitor a second paging search space (e.g., and / or core set) related to receiving paging in a second serving cell (e.g., a second serving cell in a CA, a non-best serving cell, and / or an alternate cell / anchor cell). The WTRU may have a second paging search space configured. Additionally or alternatively, the WTRU may obtain a second paging search space via system information and / or broadcast signaling of a second (e.g., non-best) serving cell.

[0154] A WTRU may receive configuration information. A WTRU may have paging subgroups associated with NES (e.g., WTRU NES subgrouping). A WTRU may receive configuration information that includes instructions that when a first cell is selected as a camp cell and the first cell is in a Network Energy Saving (NES) state, a second cell should be used for Paging Early Notification (PEI) monitoring. The configuration information may indicate a first PEI subgroup and a second PEI subgroup. The configuration information may indicate that the first cell is associated with the second cell. A WTRU may be configured to monitor PEI simultaneously with paging monitoring. A WTRU may be configured to monitor PEI at a different time than paging monitoring (e.g., separately). One or more WTRU NES subgroups may be cell-specific and / or apply to WTRUs serviced by cells in an NES state (e.g., apply to all WTRUs serviced by cells in an NES state). One or more WTRU NES subgroups may be applicable when a serving cell (e.g., best serving cell, camp cell, and / or selected cell) is in an NES state and / or availability state (e.g., off, sleep, and / or hibernate). One or more (e.g., each) subgroup may be associated with one or more availability states. A WTRU may monitor early paging notifications (PEIs) corresponding to such subgroups. For example, a PEI may include one or more of the following: receipt (e.g., or absence thereof) of an existence indication signal, receipt (e.g., or absence thereof) of an NES state / network availability state change command, and / or broadcast signaling, and a determination that the best serving cell is in a given availability state (e.g., off, sleep, and / or hibernate). Based on (e.g., subsequently) the receipt of a PEI from an alternate and / or non-best serving cell, a WTRU may monitor one or more POs. Additionally, or alternatively, a WTRU may monitor one or more POs from alternative and / or non-best serving cells based on receiving PEIs that have a specific subgroup (e.g., the NES paging subgroup).

[0155] A WTRU may monitor PDCCH within its PO for paging, for example, if the subgroup to which the WTRU belongs is paging (for example, as indicated via the associated PEI). A WTRU may monitor paging within its PO if it cannot find its subgroup ID within the PEI configuration within the cell, and / or if it cannot monitor the associated PEI occasion corresponding to its PO.

[0156] A WTRU may monitor paging in non-serving cells (e.g., second cells, unselected cells, and / or non-best-serving cells) using the subgroup ID associated with the best-serving cell. For example, a WTRU may monitor paging in non-serving cells if the best-serving cell is in an NES state and / or in a given availability state associated with a subgroup. A WTRU may monitor paging through a second cell (e.g., a non-serving cell) provided that the PEI received through the second cell indicates a first PEI subgroup, and / or, a WTRU may monitor paging through a first cell provided that the PEI received through the second cell indicates a second PEI subgroup. A WTRU may, for example, send an instruction indicating the identity of the first cell through the second cell (e.g., a non-serving cell) when a page is received through the second cell (e.g., a non-serving cell). For example, if the WTRU receives a paging instruction from a different cell indicating that paging will soon occur in the best-serving cell (e.g., a PEI with a subgroup associated with the best-serving cell), it may monitor paging at the PO associated with the best-serving cell (e.g., the PO associated with the NES DRX paging cycle).

[0157] One or more paging frame (PF) and / or PO decisions may be made for a gNB in ​​the NES state. One or more of the following may apply: The WTRU may determine that a paging frame (PF) exists when the system frame number (SFN) mod T = (T div N) × (WTRU_ID mod N). The WTRU may determine one or more of the DRX cycle length, alternative values ​​for T, and / or applicable DRX cycles from an active availability state, such as shown in Figure 4. The WTRU may have non-default and / or NES values ​​set to apply to T (e.g., DRX cycle length). The WTRU may scale T by an NES factor that may be set by the network (e.g., if the serving cell is in the NES state). The WTRU may determine an alternative value for N based on (e.g., accordingly) an active availability state. The WTRU may have non-default and / or NES values ​​set to apply to N. WTRU can determine the value of N (for example, it can scale the value of N) if, for example, the serving gNB is in an NES state (for example, a non-default availability state). In the example, WTRU can scale the set values ​​of N and / or T (for example, the default N set in SIB) by the ratio of the default SSB periodicity to the active SSB periodicity (for example, SIB periodicity instead of SSB periodicity).

[0158] A WTRU may have a non-default value and / or an NES value set for use as a WTRU_ID. For example, a WTRU may determine the PF and / or one or more POs of a first (e.g., serving, camping, best) cell and / or a second (e.g., non-serving) cell based on an NES-specific WTRU_ID. A WTRU may determine the value of the WTRU_ID (e.g., scaling the WTRU-ID, adding an offset to the WTRU-ID) if a serving gNB is in a network energy-saving state (e.g., a non-default availability state). In the example, a WTRU may use an NES WTRU_ID value if it determines that a camping cell, anchor cell, and / or serving cell is in a particular NES state (e.g., sleep and / or off). A WTRU may use an NES WTRU_ID value if it receives an NES state change instruction for a camping cell, anchor cell, and / or serving cell. The WTRU may scale the settings for N and / or T (e.g., the default N set in SIB) based, for example, on the ratio of the default SSB periodicity to the active SSB periodicity (e.g., SIB periodicity instead of SSB periodicity). The WTRU may scale the settings for N or T (e.g., the default N set in SIB) based, for example, on the ratio of the default SIB periodicity to the active SIB periodicity. The WTRU may check the criteria for PF presence (e.g., further) if the WTRU detects SSB, presence indicator, and / or DL ​​signals (e.g., only if detected) before the start of the SFN and / or frame, and / or part of the same frame. The WTRU may skip monitoring the PDCCH for that frame.

[0159] WTRU may apply an offset to SFN to determine the paging frame. For example, the WTRU may subtract the gNB sleep counter from the SFN number, so that the gNB sleep counter may include one or more increments for one or more (e.g., each) frames in which the gNB was in the NES state. The WTRU may set the counter to 0 if the serving cell is not in the energy-saving state.

[0160] One or more PDCCH monitoring occasions within a PO may be optimized. One or more of the following may apply: The WTRU may skip monitoring a subset of PDCCH monitoring occasions associated with one or more (e.g., multiple) beams if, for example, a serving cell is transmitting a stripped-down SSB (e.g., an NES SSB and / or a partial SSB). For example, the WTRU may determine (e.g., assume) that a short message (and / or paging TB containing it) associated with a multi-beam cell is transmitted in a subset (e.g., one) of the default monitoring occasions (e.g., one) rather than a default repetition for one or more (e.g., all) SSBs.

[0161] A WTRU may configure alternative search spaces and / or RNTIs (e.g., non-default and / or NES search spaces and / or RNTIs) for PDCCH paging monitoring, which may be based on the paging cell. For example, a WTRU may monitor one or more alternative values ​​of firstPDCCH-MonitoringOccasionOfPO and / or nrofPDCCH-MonitoringOccasionPerSSB-InPO. A WTRU may monitor PDCCH based on one or more alternative values ​​(e.g., and / or NES). A WTRU may monitor the NES search space for paging, for example, if the serving cell is in an NES state (e.g., if the WTRU determines that the serving cell is in a particular availability state). If the WTRU determines that paging is delayed, it may use an alternative NES search space, which may be based on detecting presence signals (e.g., or absence thereof) as described herein.

[0162] In the example, if an NES paging search space is configured, the WTRU may determine one or more (e.g., a certain number) paging occasions within a frame, and / or the timing of their POs. Based on the reception of PDCCH and / or RNTI in such a search space, the WTRU may determine which PDCCH monitoring occasions, POs, and / or PFs should be monitored. For example, based on the reception of paging DCIs (e.g., paging DCIs addressed to P-RNTI, paging DCIs addressed to NES-RNTI, and / or paging DCIs addressed in an alternative NES search space), the WTRU may monitor POs and / or PFs using different DRX cycles (e.g., NES drx cycles). The WTRU may determine that the timing of a paging occasion lies in a portion of the frame that is consistent with the gNB's SSB transmission. If an NES paging search space is configured, the WTRU may determine the value of i_s (e.g., the slot number where the paging occasion resides).

[0163] The WTRU may determine a different number of PDCCH monitoring occasions per PO. For example, the WTRU may determine (e.g., assume) a different number of PDCCH monitoring occasions per PO if an NES paging search space is configured. For example, the WTRU may determine (e.g., assume) that the number of PDCCH monitoring occasions per PO is the same number of SSBs sent by the gNB in ​​an active availability state (e.g., and / or a scalar of the number of SSBs).

[0164] A WTRU may skip PDCCH monitoring for one or more PDCCH monitoring occasions related to a default SSB that is not transmitted (for example, due to the gNB being in a particular availability state). A WTRU may skip PDCCH monitoring for one or more POs and / or PFs if, for example, a serving cell is in a particular availability state (e.g., sleep, hibernate, and / or off). For example, a WTRU may monitor (e.g., monitor only) one or more PDCCH monitoring occasions corresponding to an SSB that has been received (e.g., the measured channel state is above a threshold). A WTRU may not monitor (e.g., skip monitoring) one or more other PDCCH monitoring occasions (e.g., PDCCH monitoring occasions where no SSB was detected on the associated beam).

[0165] WTRU may determine that a subset of SSBs within an SSB burst are not transmitted and / or muted. WTRU may determine that SSBs are missing from a burst if, for example, the difference between measured values ​​(e.g., L1 SS-RSRP) fluctuates and / or differs by a margin greater than a set and / or specified threshold. WTRU may (for example, further) determine whether an SSB is transmitted based on one or more channel states (e.g., one or more absolute channel state measurements related to an SSB). For example, WTRU may determine whether an SSB is transmitted based on whether one or more channel states are greater than or less than a set and / or specified threshold. For example, WTRU may measure SSB1 in x dB and / or SSB2 in y dB. For example, if the difference between x dB and y dB is greater than a first threshold (e.g., (xy) > first threshold), WTRU may determine that SSB2 is missing. WTRU may determine that SSB1 is being transmitted if x is greater than the second threshold.

[0166] The WTRU may determine that one or more SSBs in a burst are not transmitted if it detects one or more SSBs associated with the NES (e.g., a simplified SSB, a stripped-down SSB, an SSB with only a PSS, an SSB without a PBCH, etc.). The WTRU may determine that an SSB burst uses a different structure for the NES if it detects a PSS and / or SSS using a differentiated sequence for the NES and / or NES state. For example, the WTRU may determine the NES state of a first (e.g., serving, best, camped) cell based on the reception of a PSS transmission and / or an SSS transmission. The WTRU may determine a first (e.g., serving, camped, best) cell and / or a second (e.g., non-serving) cell based on one or more properties associated with one or more SSBs and / or based on one received broadcast signaling. The WTRU may be configured with an alternative SSB structure for the NES, thereby reducing and / or tailing the number of beams and / or SSBs in the burst (e.g., by configuration and / or by dedicated signaling such as RRC and / or DCI).

[0167] Additionally or alternatively, the WTRU may have an alternative SSB structure in the broadcast information (e.g., in an SIB related to an NES). For example, the alternative SSB structure that is set may include an NES SSB. For example, the alternative SSB structure (e.g., an NES SSB) may represent the WTRU, one or more (e.g., a certain number) SSBs per burst, and / or a subset of SSBs that may or may not be transmitted in one or more NES states. The setting of the alternative NES SSB structure may be set and / or determined for each NES state. The setting of the alternative NES SSB structure may be set and / or determined in response to receiving NES state change signaling. In the example, the WTRU may read an SIB IE with an SSB location in a burst and / or determine whether one or more SSBs will be muted in one or more NES states. In the example, the WTRU may read an SIB IE with an SSB location in a burst and / or determine whether an SSB is present in one or more NES states.

[0168] Paging may be delayed, for example, based on the detection (e.g., or absence) of a cell signal. One or more of the following may apply: If the WTRU receives a signal indicating that one or more (e.g., all) paging from a cell will be delayed until the next NES DRX occasion, it may skip paging until the next NES DRX occasion.

[0169] The WTRU may not wake up for paging if it does not detect a signal from the serving cell (e.g., an existence indicator and / or existence signal). The WTRU may skip one or more DRX occasions (e.g., PF and / or PO) until the next NES DRX occasion if it fails to detect an existence indicator signal. The WTRU may maintain a counter which may be used to determine whether it can skip one or more (e.g., the remaining) POs until the next NES DRX cycle.

[0170] The timing of one or more subsequent paging and / or SI transmit occasions may be determined, for example, based on whether the WTRU detects a transmit from the network. For example, if the WTRU receives a DCI for paging, presence signal, and / or SI transmit during the wake time, the WTRU may determine future paging and / or SI transmit occasions (for example, from a default set of timings). If the WTRU receives, for example, a signal indicating a channel acquired during the wake time (for example, only that signal) (for example, and nothing else), the WTRU may decide to skip a subset of one or more future paging and / or SI transmit occasions. If the WTRU receives, for example, a signal indicating a channel acquired during the wake time (for example, only that signal) (for example, and / or nothing else), the WTRU may determine the timing from a different set of configuration parameters (for example, non-default and / or NES DRX cycles). If the WTRU does not receive a transmission during the wake time, the WTRU may determine future paging or SI transmission occasions from a third function (e.g., a function that uses a third set of one or more inputs).

[0171] A WTRU may receive paging delay instructions and / or signals. For example, a WTRU may receive a paging delay instruction from a cell other than the best serving cell (e.g., a camp cell, a selected cell). Based on receiving a paging delay instruction, a WTRU may determine that paging will be delayed and / or postponed by one more paging occasion. For example, bits in a short message and / or PEI may indicate that the WTRU should monitor one or more further paging occasions (even if, for example, a P-RNTI is received). Bits in a short message may indicate the cell on which the WTRU should monitor for paging reception and / or PDSCH reception. In the example, a WTRU may skip one or more POs (e.g., it may not need to wake up from the DRX to monitor a PO) unless it is instructed to wake up for a PO (e.g., it is explicitly informed via a PEI that only that WTRU has received a PEI). A WTRU may skip one or more POs if it determines that the cell is in a given availability state. A WTRU may skip a PO if the time elapsed since the last availability state change (e.g., and / or reception of a state change command) is greater than (e.g., less than) a threshold (e.g., configured). For example, a WTRU may start and / or restart monitoring one or more (e.g., normal) POs in response to receiving a PEI (e.g., a new and / or updated PEI). One or more of the following may apply: The WTRU may start and / or restart monitoring one or more (e.g., normal) POs in response to receiving a PEI (e.g., a new and / or updated PEI) based on the WTRU's determination that the cell is in a given availability state. The WTRU may start and / or restart monitoring one or more (e.g., normal) POs in response to receiving a PEI (e.g., a new and / or updated PEI) if the time elapsed since the last availability state change (e.g., and / or reception of a state change command) is greater than (e.g., or less than) a (e.g., configured) threshold. For example, in the case of a state change command, the WTRU may start and / or restart monitoring one or more (e.g., normal) POs in response to receiving a PEI (e.g., a new and / or updated PEI).

[0172] A WTRU may determine, based on the reception of instructions in broadcast signaling (e.g., indicated in the MIB and / or one or more other SIBs) and / or from one or more properties of the received SSB (e.g., NES SSB), that paging will be delayed and / or skipped in one or more cells (e.g., one or more cells in a CA having camp cells). For example, a WTRU may receive instructions (e.g., in the MIB or SIB) for NES paging occasions and / or frame timing, instructions to skip decoding of paging PDSCH and / or PDCCH, instructions that paging will be delayed, and / or instructions for the WTRU to monitor paging using a different DRX cycle (e.g., NES paging cycle). A WTRU may receive instructions (e.g., in the MIB or SIB) to wake up instructions and / or signals (e.g., in the MIB or SIB) to monitor one or more upcoming paging occasions and / or frames, including indicators for paging. A WTRU may receive broadcast signaling and / or one or more SSB transmissions. A WTRU may determine, for example, based on one or more received POs and / or one or more received SSB transmissions, that one or more SSB transmissions and / or one or more POs are delayed and / or skipped in a first (e.g., serving, camping, best) cell.

[0173] A WTRU may transmit an RA and / or WUS in response to paging. One or more of the following may apply: The WTRU may respond with a UL instruction (e.g., RACH and / or NES WUS) to indicate to the network which cell the WTRU is camped on and / or the best measured cell (e.g., and / or camp cell, selected cell) when, for example, paging is received. For example, UL instructions may be the NES wake-up signal, RACH, PUCCH, and / or PUSCH. The WTRU may transmit a signal through a first cell, for example, when a page is received through that first cell. The WTRU may indicate the identity of a first cell by transmitting a signal through that first cell.

[0174] UL instructions may include instructions to the network (e.g., parts of the UCI, MAC CE, and / or RRC message portions of the PUSCH payload). UL instructions may indicate the WTRU's best serving cell and / or best measured cell (e.g., camp cell and / or selected cell). For example, a WTRU may send instructions via a second cell indicating the identity of the first cell when a page is received via the second cell. Instructions may include RRC messages, e.g., RRC connection resume requests and / or RRC connection re-establishment requests. UL instructions may include the WTRU's identity and / or RNTI (e.g., C-RNTI and / or inactive RNTI (I-RNTI) and / or international mobile subscriber identity (IMSI)). The WTRU may include, for example, an RRC connection reactivation request if the WTRU is in an inactive state and / or has one or more resources applicable to small data transmissions. The WTRU may include an RRC re-establishment request if, for example, it is in idle mode. The WTRU may monitor PDSCH and / or PDCCH reception based on (e.g., following) the transmission of a UL signal instruction and / or based on (e.g., after) the successful completion of an RA procedure (e.g., for receiving DL TB, paging messages, and / or uplink grants).

[0175] A WTRU may transmit UL signals (e.g., RA and / or WUS) in response to paging. One or more of the following may apply: A WTRU may transmit UL signals (e.g., RA and / or WUS) in response to paging received from a first cell different from the second cell from which uplink signals and / or instructions are transmitted (e.g., paging is received from a non-best cell, a second cell, an unselected cell, a non-serving cell, and / or an alternate cell). For example, the first cell may include the cell from which the WTRU is monitoring paging in its default (e.g., non-NES) state, the last connected cell, the cell with one or more best L1 and / or L3 measurements (e.g., the cell with the best measured SS-RSRP), and / or the cell from which the last availability state change command was received. The first cell may also refer to the second cell. The second cell may be determined (e.g., pre-determined) to be, for example, part of the same gNB as the first cell and / or a cell within the same cell group as the first cell. The second cell may be dual connectivity (DC) with the first cell (e.g., the first cell may be MN and / or the second cell may be SN, or vice versa). The second cell may be CA with the first cell (e.g., part of the same MAC entity as the first cell). The WTRU may determine (e.g., self-determined, independently determined) the second (e.g., non-serving) cell based, for example, one or more channel measurements and / or one or more handover candidate configurations. The relationship between the first and second cells may be established by the network (e.g., by the dedicated signaling portion and / or broadcast signaling portion of the SI).

[0176] The WTRU may transmit UL signals (e.g., RA and / or WUS) in response to receiving a PEI. For example, the received PEI may include one or more of the following: the received PEI having a configured NES subgroup, the PEI having a subgroup related to the availability status of the best measured cell (e.g., and / or camp cell, selected cell), and / or the PEI having a subgroup corresponding to the WTRU's serving / best measured cell.

[0177] The WTRU may transmit a UL signal (e.g., RA and / or WUS) if the best-measured cell is in a particular availability state and / or NES state. For example, the WTRU may transmit a UL signal (e.g., RA and / or WUS) if one or more measured channel states for a paging cell are below a threshold (e.g., or greater than a threshold). For example, the WTRU may transmit a UL signal (e.g., RA and / or WUS) if one or more measured channel states for the best-measured cell (e.g., and / or camp cell and / or selected cell) are greater than a threshold (e.g., or less than a threshold).

[0178] The WTRU may transmit a UL signal (e.g., RA and / or WUS) if the L3 measurement condition is below (e.g., or above) a threshold (e.g., L3 RSRP and / or SINR).

[0179] The WTRU may transmit a UL signal (e.g., RA and / or WUS) if the L2 measurement condition is below (e.g., or above) a threshold (e.g., Qin, block error rate (BLER), L1-RSRP, L1-SINR).

[0180] The WTRU may transmit UL signals (e.g., RA and / or WUS) based on whether the WTRU is camp-on to the cell from which the uplink signal and / or instruction is transmitted.

[0181] The WTRU may determine (e.g., assume) a change in the availability state of a cell to which a UL signal has been transmitted (e.g., a particular availability state such as being active, e.g., on). For example, the WTRU may determine (e.g., assume) a change in the availability state of a cell when transmitting such an uplink signal, based on the reception of a network response to the UL signal (e.g., at that time, and thereafter) and / or the successful completion of procedures related to the transmitted uplink signal (e.g., successful completion of RA and / or successful reception of WUS) (e.g., at that time).

[0182] A WTRU may transmit an NES wake-up signal. For example, a WTRU may transmit an NES wake-up signal if it is camp-on to a cell and / or if it is in an inactive state (e.g., following the reception of paging from a second cell). The NES wake-up signal and / or instruction may be transmitted by one or more PUSCH, PUCCH, and / or PRACH resources.

[0183] In the example, the network may not know which cell the WTRU is camped on and / or which cell it is located in (e.g., the best measured cell by the WTRU). If the network does not know which cell the WTRU is camped and / or located in, for example, the network may page the WTRU in one or more (e.g., several) cells that are on. The WTRU may respond (e.g., at that time) with a UL signal indicating to the network which cell the WTRU is camped on and / or the best cell (e.g., RACH on the best cell) based on receiving the paging (e.g., from a second cell other than the first cell). The network may turn on and / or change the availability state associated with that cell (e.g., the cell the WTRU is camped on) and / or page the WTRU in that cell (e.g., as shown in Figure 5) (e.g., and / or the network may send a PDSCH transmission to the WTRU).

[0184] Figure 5 shows Example 500 relating to an example of a paging procedure in the NES state, including receiving paging from a second cell. The WTRU may receive configuration information that indicates the second cell should be used for PEI monitoring when the first cell is selected as a camp cell and / or the first cell is in the NES state. The configuration information may indicate the first PEI subgroup and / or the second PEI subgroup. The configuration information may indicate that the first (e.g., camp, best, serving) cell is associated with the second (e.g., non-serving) cell.

[0185] In 502, the WTRU may determine that the best serving cell is in an NES state (e.g., sleep, hibernate, and / or off). For example, the WTRU may determine that the best serving cell is in an NES state based on the reception of an NES state switching command (e.g., group common DCI) and / or the absence of detection of periodic presence signals associated with the cell (e.g., SSB, RS, and / or PDCCH).

[0186] The WTRU may, for example, monitor PDCCH for paging on a sleeping serving cell using a configured non-default NES DRX configuration, based on (for example, subsequently) a determination that the cell is in a relevant availability state. The WTRU may skip one or more on-durations (e.g., one or more default on-durations) that are inconsistent with the gNB's active time (e.g., do not overlap with and / or are not within the time of SSB and / or PDCCH reception). For example, the WTRU may monitor one or more specific PDCCH occasions (e.g., only PDCCH occasions related to the cell NES state). For example, if a serving cell is transmitting a stripped-down SSB, the WTRU may skip monitoring a subset of PDCCH monitoring occasions (e.g., PDCCH monitoring occasions in a PO related to multiple beams). For example, a WTRU may determine that a subset of PDCCH POs in a second DRX cycle will not be transmitted based on the determination that one or more SSBs and / or one or more POs are delayed and / or skipped in a first (e.g., serving, camping, best) cell.

[0187] The WTRU may, for example, skip monitoring one or more of the next on-durations (e.g., the next default on-duration) on the best cell and / or the serving cell until the next NES on-duration. For example, the WTRU may skip monitoring one or more of the next default on-durations on the best / serving cell based on the reception (e.g., or lack thereof) of an instruction (e.g., from the serving cell) for monitoring one or more of the default on-durations. Additionally or alternatively, the WTRU may skip monitoring one or more of the next default on-durations on the best and / or serving cell based on the reception (e.g., subsequently) of a DL signal (e.g., a presence instruction) of a threshold intensity above the threshold from the serving cell, or the lack of such a reception.

[0188] In 504, the WTRU may monitor paging in one or more other cells. The WTRU may monitor paging in the best cell and / or the WTRU may monitor paging in one or more other (e.g., non-best) cells. For example, the WTRU may monitor PDCCH for paging in a second cell (e.g., a non-best cell). The WTRU may monitor the search space associated with the second cell. The WTRU may use P-RNTI (e.g., the same P-RNTI and / or alternative P-RNTI associated with the NES state) to monitor PDCCH for paging from the second cell. The WTRU may monitor PEI through the second cell, for example, based on the determination that the first cell is in the NES state. The WTRU may monitor PEI having cell-specific subgroups and / or NES subgroups from the first cell (e.g., the serving cell) and / or the second cell. Based on receiving instructions from a second cell (e.g., a non-best cell) that include PEIs related to NES subgroups and / or subgroups corresponding to the first cell and / or cells in the NES state, the WTRU may monitor one or more subsequent on-durations in the first cell (e.g., a serving cell or best-measured cell). Upon receiving such instructions, the WTRU may skip one or more on-durations and / or POs related to other cells (e.g., until the next NES on-duration in the first cell).

[0189] In 506, the WTRU may receive paging from a second cell (e.g., a non-best cell) but may also receive paging from a first cell (e.g., a serving cell or best measured cell) (e.g., via a PDSCH transmission) (512). For example, the WTRU may receive PEI via a second cell. The WTRU may monitor paging via a first (e.g., best, camp, serving) cell, provided that the PEI received via a second (e.g., non-serving) cell indicates a second PEI subgroup. The WTRU may transmit a signal via a first (e.g., best cell, camp cell, serving cell) if paging is received via the first cell. The signal may include an indication of the identity of the first (e.g., best, camp, serving) cell.

[0190] In 508, a WTRU may transmit one or more UL signals and / or information. A WTRU may transmit one or more UL signals (e.g., RACH, PUSCH, and / or PUCCH resources) related to the cell availability state. For example, a WTRU may transmit UL signals and / or information based on (e.g., at the time) receiving paging in a second cell (e.g., a non-best cell). One or more of the following may apply: A WTRU may send a RACH transmission in a paging cell (e.g., and / or best cell). A WTRU may determine (e.g., select) one or more PRACH resources related to the NES state if a RACH is transmitted in a first cell that is in an NES state. For example, a WTRU may transmit a RACH in a second cell (e.g., a paging cell) if one or more measured channel states exceed a threshold (e.g., a set and / or predetermined threshold). For example, based on receiving paging in a second cell (e.g., a non-best cell) (e.g., at that time), the WTRU may send an NES WUS in a cell such as the best cell (e.g., if the best cell is sleeping). For example, based on receiving paging in a second cell (e.g., a non-best cell) (e.g., at that time), the WTRU may send a MAC CE and / or UCI (e.g., cell ID in the Msg3 payload and / or MsgA) indicating the best serving cell. For example, based on receiving paging in a second cell (e.g., a non-best cell) (e.g., at that time), the WTRU may send an RRC message (e.g., RRC restart request, RRC re-establishment request, and / or RRC reset request).

[0191] In 510, for example, the WTRU may receive a message (e.g., Msg4) that may indicate the success of the RA completion. The WTRU may monitor the PDSCH in the indicated cell (e.g., during the next NES on duration). Based on the receipt of a response from the first cell (e.g., at that time), the WTRU may determine (e.g., assume) that the relevant availability state has changed to, for example, the default availability state and / or the on availability state.

[0192] In 514, for example, the WTRU may determine (e.g., assume) that the best cell is on based on (e.g., subsequently) the reception of the paging PDSCH. The WTRU may determine, for example, that the first (e.g., camp, serving, best measured) cell is no longer in the NES state when a page is received through the first (e.g., camp, serving, best measured) cell.

[0193] Figure 6 shows Figure 600 of a second example relating to an example of a paging procedure in the NES state. In 602, an alternative paging cell (e.g., a second non-serving cell) may be associated by configuration as described herein. The WTRU may receive configuration information indicating that a first cell (e.g., a camp cell, best cell, serving cell) is associated with a second (e.g., non-serving) cell as described herein. In 604, the WTRU may determine (e.g., via broadcast, paging, one or more measurements, etc.) that the best cell and / or camp cell are in the NES state (e.g., as described herein).

[0194] In 606, the WTRU may monitor the PEI in an alternative (e.g., a second, non-serving) cell (as described herein, for example). The second (e.g., alternative, non-serving) cell may be associated with a different DRX cycle than the one associated with the first (e.g., serving, camp, best) cell (as shown in Figures 4 and 5, for example).

[0195] In 608, the WTRU may detect a PEI. A PEI may represent one or more configured subgroups. For example, a PEI may represent one of two configured subgroups. A PEI may represent one or more configured subgroups. One or more configured subgroups may include NES-specific subgroups and / or subgroups about camp cells.

[0196] In 610a, the WTRU may monitor paging in an alternate cell if the subgroup indicated (for example, by PEI in 608) is an NES-specific subgroup. If the WTRU is paging, the WTRU may perform RA against the alternate cell. If the WTRU is paging, the WTRU may indicate a camp cell via the preamble / resource and / or via the msgA and / or msg3 payloads.

[0197] For example, if the subgroup indicated (e.g., by PEI in 608) is a subgroup of camp cells, then in 610b, the WTRU may monitor paging in the camp cells. If the WTRU is paging, for example, the WTRU may perform an RA on the camp cells. If the WTRU is paging, for example, the WTRU may determine (e.g., assume) that the NES state of the camp cells has ended (e.g., as shown in Figure 5).

[0198] WTRU can receive and / or acquire SI while the network is in the NES state. One or more of the following may apply: For a WTRU in an idle and / or inactive state, the WTRU may attempt to acquire an SI on one or more different occasions, for example, when the network is in an NES state and / or another given availability state. The WTRU may determine a modified timing for acquiring an SI and / or a subset of one or more SI transmissions (e.g., an SIB and / or a subset of other SIs). For example, the timing and / or periodicity of such an SI acquisition (e.g., residual SI) may be obtained by reading the minimum SI (e.g., which may be acquired using the default periodicity). The minimum SI may have the same periodicity as one or more other (e.g., legacy) periodicities, but may differ from the periodicity of other SIs and / or residual SIBs. The minimum SI may point to an alternative NES SI periodicity. A flag may be broadcast (e.g., in the resource used to receive the minimum SI and / or PBCH transmissions) so that the WTRU knows which periodicity is being used.

[0199] A WTRU may have one or more alternative NES SI periodicities. The WTRU may determine the periodicity of the active NES SI periodicity pattern based on one or more of the following: the difference between the current SSB and / or RS measurement occasion and one or more (e.g., a certain number) past measurements, and / or a comparison thereof; the overall signal quality of the cell (e.g., based on one or more measurements of L3 RSRP and / or present signals); and / or the mobility status of the WTRU. The WTRU may also determine the periodicity of the active NES SI periodicity pattern from the resources and / or timing of the received minimum SI.

[0200] For a WTRU in connected mode, for example, L1 signaling and / or L2 signaling may indicate a switch between one or more configured NES SI periodics. The WTRU may, for example, determine (e.g., assume) different periodics of SI, other SI, and / or subsets of SIB upon receiving such a command.

[0201] For a WTRU in idle mode, for example, it may determine SI periodicity and / or whether an SI occasion is missing (e.g., whether it was transmitted from a gNB) based on one or more past measurements. The WTRU may associate the reception of an SI with the reception of an SSB. For example, the WTRU may determine (e.g., assume) that one or more SI reception occasions within a time period from one or more received SSBs (e.g., having a communication metric above a threshold) are valid SIs and / or one or more broadcast occasions. The WTRU may determine that no broadcast SI is transmitted if, for example, the current SSB measurement in a measurement occasion differs by a difference greater than a predetermined and / or set value from one or more (e.g., a number) past measurements (e.g., and / or a moving average over a number of past measurements). For example, the number of past measurements may be predetermined and / or set.

[0202] WTRU may use a window for minimum SI reception and / or other SI receptions. During such a window, the WTRU may monitor broadcasts of minimum SIs and / or other SIs. The WTRU may periodically initiate windows, for example, according to a set period and / or a predetermined period. For example, the WTRU may initiate a window based on (for example, following) the reception of SSB, RS, and / or presence signals (e.g., presence signals with signal strength above a threshold and / or measured channel state).

[0203] A WTRU may request changes to the NES SI periodicity. In the example, a WTRU may trigger a request to change the NES SI periodicity by sending a request for an on-demand SI. In the example, a WTRU may trigger a request to change the NES SI periodicity by sending a wake-up request. In the example, a WTRU may trigger a request to change the NES SI periodicity by sending a support information request. A WTRU may trigger a request for an SI and / or other SI (e.g., by initiating an RA to acquire an SI) if it is determined that the serving cell is in one or more NES states. A WTRU may request other SIs after the expiration of an NES sleep duration window (e.g., a period related to the NES cell validity timer and / or NES SBB periodicity). For example, if a WTRU fails to receive a DL signal and / or presence indication from a gNB within a certain period, the WTRU may request other SIs after the NES sleep duration window expires. Additionally, or alternatively, the WTRU may request other SIs after the NES sleep duration window expires based on whether the WTRU receives broadcast signaling and / or one or more SSB transmissions from the serving cell (e.g., after receiving them).

Claims

1. Wireless Transmitter / Receiver Unit, WTRU, Memory and (1) When the first cell is selected as a camp cell and the first cell is in a network energy saving (NES) state, configuration information is received indicating that the second cell will be used for monitoring. Based on the fact that the first cell is in the NES state, the notification is monitored via the second cell. The notification is received via the second cell, Monitoring paging, and monitoring said paging means (1) via the second cell, provided that the notification is associated with a first group, or (2) via the first cell, provided that the notification is associated with a second group. A processor configured in such a way A WTRU characterized by having the following features.

2. The WTRU according to claim 1, characterized in that the notification is received via signaling corresponding to one or more of the following: paging early notification (PEI), physical downlink control channel (PDCCH), or wake-up signal (WUS).

3. The WTRU according to claim 1, further characterized in that the processor determines that when the paging is received through the first cell, the first cell is no longer in the NES state.

4. The WTRU according to claim 1, further characterized in that the processor is configured to receive configuration information indicating that the first cell is associated with the second cell.

5. The WTRU according to claim 1, characterized in that the first group is associated with the second cell, and the second group is associated with the first cell.

6. The first cell is associated with a first intermittent reception (DRX) cycle, and the second cell is associated with a second DRX cycle. The processor is further configured to apply the first DRX cycle on the condition that the WTRU is connected to the first cell, and to apply the second DRX cycle on the condition that the WTRU is connected to the second cell. The WTRU according to feature 1.

7. The WTRU according to claim 1, further configured to determine the paging frame (PF) or paging occasion (PO) of the first cell or the second cell based on NES-specific WTRU identification information (ID).

8. The aforementioned processor, Upon receiving broadcast signaling or one or more synchronous signal blocks (SSB) transmissions, It is determined that one or more SSB transmissions or one or more paging occasions are delayed or skipped in the first cell. Based on the determination that one or more SSB transmissions or one or more paging occasions are delayed or skipped in the first cell, it is determined that a subset of the physical downlink control channel (PDCCH) paging occasions of the second DRX cycle will not be transmitted. The WTRU according to claim 1, further characterized by being configured as follows.

9. The aforementioned processor, (1) When the paging is received via the first cell, transmit a signal via the first cell, or (2) When the paging is received via the second cell, transmit a notification via the second cell indicating the identity of the first cell. The WTRU according to claim 1, further characterized by being configured as follows.

10. The WTRU according to claim 1, characterized in that the first cell corresponds to a carrier, or the second cell corresponds to a carrier.

11. A method performed by a wireless transmission / reception unit, WTRU, (1) Receiving configuration information indicating that when the first cell is selected as a camp cell and the first cell is in a network energy saving (NES) state, the second cell will be used for monitoring, Based on the fact that the first cell is in the NES state, the notification is monitored via the second cell, Receiving the notification via the second cell, Monitoring paging, wherein monitoring paging means (1) via the second cell on the condition that the notification is associated with a first group, or (2) via the first cell on the condition that the notification is associated with a second group. A method characterized by comprising:

12. The method according to 11, characterized in that the notification is received via signaling corresponding to one or more of the following: paging early notification (PEI), physical downlink control channel (PDCCH), or wake-up signal (WUS).

13. The method according to 11, further comprising: transmitting a signal through the first cell when the paging is received through the first cell, or transmitting a notification indicating the identity of the first cell through the second cell when the paging is received through the second cell.

14. The method according to 11, further comprising receiving configuration information indicating that the first cell is associated with the second cell.

15. The method according to 11, characterized in that the first group is associated with the second cell, and the second group is associated with the first cell.

16. The first cell is associated with a first intermittent reception (DRX) cycle, and the second cell is associated with a second DRX cycle. The method according to 11, further comprising: applying the first DRX cycle on the condition that the WTRU is connected to the first cell; and applying the second DRX cycle on the condition that the WTRU is connected to the second cell.

17. The method according to 11, further comprising determining the paging frame (PF) or paging occasion (PO) of the first cell or the second cell based on NES-specific WTRU identification information (ID).

18. Receiving broadcast signaling, or one or more synchronous signal blocks (SSB) transmissions, It is determined that one or more SSB transmissions or one or more paging occasions are delayed or skipped in the first cell. Based on the determination that one or more SSB transmissions or one or more paging occasions are delayed or skipped in the first cell, it is determined that a subset of the physical downlink control channel (PDCCH) paging occasions of the second DRX cycle will not be transmitted. The method according to 11, further comprising:

19. (1) When the paging is received via the first cell, transmit a signal via the first cell, or (2) When the paging is received via the second cell, transmit a notification via the second cell indicating the identity of the first cell. The method according to 11, further comprising:

20. The method according to 11, characterized in that the first cell corresponds to a carrier, or the second cell corresponds to a carrier.

Images