Discontinuous Network Access

Abstract

The present disclosure relates to devices, methods, and systems implemented for discontinuous network access. The implementation includes monitoring a presence indication signal in a second cell. The implementation includes determining to transmit a wake-up signal for a first cell based on detecting the presence indication signal in the second cell and based on a measurement performed on a Synchronization Signal Block (SSB) of the second cell being less than a threshold. The implementation includes transmitting the wake-up signal. The implementation includes monitoring transmission of an SSB of the first cell after transmitting the wake-up signal. The implementation includes receiving information indicating that the first cell has transitioned to an active state after transmitting the wake-up signal. The implementation also includes transmitting data via the first cell after receiving information indicating that the first cell has transitioned to an active state.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority to U.S. Provisional Patent Application No. 63 / 327,557, filed April 5, 2022, and U.S. Provisional Patent Application No. 63 / 391,357, filed July 22, 2022, the entireties of which are incorporated by reference herein. [Background technology]

[0002] Network energy consumption may be very significant or may be unnecessary at lower cell loads. Therefore, the network (NW) may turn off frequent periodic transmissions (e.g., synchronization signal blocks or system information transmissions) on some cells or carriers to enable network sleep periods. However, the network may not be aware of the sudden increase in wireless transmit / receive unit (WTRU) demand for network access when the number of active WTRUs changes or when WTRU concentration increases. Summary of the Invention

[0003] The present disclosure relates to devices, methods, and systems for discontinuous network access. In one or more implementations, a WTRU monitors discovery signals and presence information in an anchor cell to access a non-anchor cell when the non-anchor cell is in a Network Energy Savings (NES) state. The WTRU transmits a wake-up request to access the non-anchor cell, e.g., based on receiving the presence information. The WTRU monitors transmissions from the non-anchor cell, e.g., after transmitting the wake-up request. The WTRU changes the availability state of the non-anchor cell upon receiving a response from the non-anchor cell. In one or more implementations, the WTRU determines an active availability state associated with a given cell, e.g., upon receiving WTRU-specific or group-common Downlink Control Information (DCI), Medium Access Control (MAC) Control Element (MAC CE), or paging. In one or more implementations, the WTRU adapts Beam Failure Detection (BFD), Radio Link Monitoring (RLM), Reference Signaling / Synchronization Signal Block (RS / SSB) monitoring, and Channel State Information (CSI) measurements for the cell depending on the active availability state of the cell. In one or more implementations, the WTRU switches the active Bandwidth Part (BWP) to the group common BWP configured for the NES upon receiving a group common indication. In one or more implementations, the WTRU includes one or more of the following NES WTRU assistance information: cell index for which a state change is requested, desired availability state, and request for on-demand SSB.

[0004] In one or more implementations, the WTRU may use the presence indication to access resources in a cell, a gNB, or a Transmission / Reception Point (TRP). In one or more implementations, the WTRU may monitor a presence indication associated with a sleep / off gNB. In one or more implementations, the WTRU may receive a presence indication. In one or more cases, the WTRU may assume an availability state (e.g., "Off" or "Deep sleep") associated with the cell. In one or more cases, the WTRU may transmit a switch-on request, WTRU assistance information, or Random Access (RA) after successfully detecting a presence signal. In one or more implementations, the WTRU may monitor additional synchronization signal block (SSB) and / or CSI-RS resources after receiving a response to the transmission switch-on request or switch-on request. In one or more implementations, the WTRU may change the availability state of a cell after successfully receiving a response from the requested cell to the transmitted request or switch-on request.

[0005] Devices, methods, and systems for discontinuous network access may include SSB and CSI-RS adaptation. In one or more implementations, devices, methods, and systems for determining a cell's NES state are provided. In one or more cases, the devices, methods, and systems described herein may have an impact on synchronization, initial access procedures, BFD, and Random Access Channel (RACH) based on discontinuous network transmission of a common signal. In one or more cases, the devices, methods, and systems described herein may be used to know whether a WTRU measures MO. In one or more cases, the devices, methods, and systems described herein may be used to know whether a common cell signal (e.g., a synchronization signal or a reference signal) is transmitted normally as opposed to a WTRU not receiving the common cell signal based on poor channel conditions. In one or more cases, the devices, methods, and systems described herein may be used to determine measurements associated with a cell in an NES state, including RLM and BFD. In one or more cases, the devices, methods, and systems described herein may be used for the WTRU to determine which resources are applicable for data, control, or measurement for each availability state. In one or more cases, the devices, methods, and systems described herein may be used to determine initial access on an alternative cell.

[0006] A method for discontinuous network access is provided herein. In one or more implementations, the method includes monitoring a presence indication signal in a second cell. In one embodiment, the presence indication signal indicates that the first cell is in a low availability state. In one or more implementations, the method includes determining to transmit a wake-up signal for the first cell based on detecting the presence indication signal in the second cell and based on a measurement performed on a synchronization signal block (SSB) of the second cell being below a threshold. In one embodiment, the wake-up signal is transmitted prior to expiration of a predetermined time period after receiving the presence indication signal over the second cell. In one or more implementations, the method includes transmitting the wake-up signal. In one or more implementations, the method includes monitoring transmission of an SSB of the first cell after transmitting the wake-up signal. In one or more implementations, the method includes receiving information indicating that the first cell has transitioned to an active state after transmitting the wake-up signal. In one or more implementations, the method includes transmitting data over the first cell after receiving information indicating that the first cell has transitioned to an active state.

[0007] A wireless transmit / receive unit (WTRU) for discontinuous network access is provided herein. In one or more implementations, the WTRU includes a processor. In one or more implementations, the processor is configured to monitor a presence indication signal in a second cell. In one example, the presence indication signal indicates that the first cell is in a low availability state. In one or more implementations, the processor is configured to determine to transmit a wake-up signal for the first cell based on detecting the presence indication signal in the second cell and based on a measurement performed on a synchronization signal block (SSB) of the second cell being below a threshold. In one example, the wake-up signal is transmitted prior to expiration of a predetermined time period after receiving the presence indication signal over the second cell. In one or more implementations, the processor is configured to transmit the wake-up signal. In one or more implementations, the processor is configured to monitor transmissions of the SSB of the first cell after transmitting the wake-up signal. In one or more implementations, the processor is configured to receive information indicating that the first cell has transitioned to an active state after transmitting the wake-up signal. In one or more implementations, the processor is configured to transmit data via the first cell after receiving information indicating that the first cell has transitioned to an active state. [Brief description of the drawings]

[0008] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which like reference numbers indicate similar elements and in which: [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] 1 is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A. [Figure 1C]FIG. 1B is a system diagram illustrating an example Radio Access Network (RAN) and an example Core Network (CN) that may be used within the communication system illustrated in FIG. 1A. [Figure 1D] FIG. 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system illustrated in FIG. 1A. [Diagram 2] 1 is an exemplary time-frequency structure of a synchronization signal block (SSB). [Diagram 3] FIG. 2 is a diagram of an exemplary beam sweep. [Figure 4A] A figure showing an example of setting SSB transmission for anchor cells and non-anchor cells. [Figure 4B] 1 is a graph illustrating an example aspect of the present disclosure that may be implemented. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] 1A is a diagram illustrating an example 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, messaging, broadcasts, etc., to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources, including wireless bandwidth. For example, the communications system 100 may use 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 filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0010] 1A, communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, Public Switched Telephone Network (PSTN) 108, Internet 110, and other networks 112, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or “STA,” may be configured to transmit and / or receive wireless signals and may include User Equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, mobile phones, Personal Digital Assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (loT) devices, watches or other wearable, 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 wireless devices operating in an industrial and / or automated processing chain context), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.

[0011] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a Base Transceiver Station (BTS), a Node B, an eNode B, a Home Node B, a Home eNode B, a gNB, an NR Node B, a site controller, an Access Point (AP), a wireless router, etc. Although the base stations 114a, 114b are each depicted as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0012] The base station 114a may be part of the 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), a relay node, etc. The base station 114a and / or the 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 a cell (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage for a particular geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each 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, using beamforming to transmit and / or receive signals in a desired spatial direction.

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

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

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

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

[0017] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may jointly implement LTE radio access and NR radio access, e.g., using a Dual Connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

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

[0019] 1A may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as an office, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology, such as IEEE 802.11, to establish a Wireless Local Area Network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology, such as IEEE 802.15, to establish a Wireless Personal Area Network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106 / 115.

[0020] The RAN 104 / 113 may communicate with the CN 106 / 115, which may be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various Quality of Service (QoS) requirements, such as, for example, different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may communicate, directly or indirectly, with other RANs employing the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also communicate with another RAN (not shown) using GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0021] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 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 that 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. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may use the same RAT as the RANs 104 / 113 or a different RAT.

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

[0023] 1B is a system diagram illustrating an example WTRU 102. As shown in FIG. 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 source 134, a Global Positioning System (GPS) chipset 136, and / or other peripherals 138. It will be understood that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0024] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a Digital Signal Processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120, which may be coupled to a transmit / receive element 122. Although FIG. 1B depicts the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

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

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

[0028] The processor 118 of the WTRU 102 may be coupled to and may receive user-entered data from 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). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. It should be noted that the processor 118 may access information from and store data in any type of suitable memory, such as non-removable memory 130 and / or removable memory 132. The non-removable memory 130 may include a Random-Access Memory (RAM), a 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, etc. In other embodiments, the processor 118 may access information from and store data in memory that is not physically located on the WTRU 102, such as on a server or home computer (not shown).

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

[0030] 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) regarding the current location of the WTRU 102. In addition to, or in lieu of, information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over 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 appreciated that the WTRU 102 may obtain location information by way of any suitable location determination method while remaining consistent with an embodiment.

[0031] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an 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 peripherals 138 may include one or more sensors, which may be one or more of a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor, a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0032] The WTRU 102 may include a full-duplex radio where the transmission and reception of some or all of the signals associated with a particular subframe (e.g., for both the UL (e.g., for transmission) and the downlink (e.g., for reception) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit 139 to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., via a separate processor (not shown) or via the processor 118). In one embodiment, the WRTU 102 may include a half-duplex radio for the transmission and reception of some or all of the signals (e.g., associated with a particular subframe for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).

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

[0034] The RAN 104 may include eNodeBs 160a, 160b, 160c, although it will be understood that the RAN 104 may include any number of eNodeBs while remaining consistent with an embodiment. The eNodeBs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNodeBs 160a, 160b, 160c may implement MIMO technology. Thus, the eNodeB 160a may transmit wireless signals to and / or receive wireless signals from the WTRU 102a using multiple antennas, for example.

[0035] Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, etc. As shown in FIG 1C, the eNodeBs 160a, 160b, 160c may communicate with each other via an X2 interface.

[0036] 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 foregoing elements is depicted as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0037] The MME 162 may be connected to each of the eNodeBs 162a, 162b, 162c in the RAN 104 via an S1 interface and may function as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, activating / deactivating bearers, selecting a particular serving gateway during initial attachment of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0038] The SGW 164 may be connected to each of the eNodeBs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-eNodeB handovers, triggering paging when DL data is available to the WTRUs 102a, 102b, 102c, and managing and storing the context of the WTRUs 102a, 102b, 102c.

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

[0040] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or communicate with an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. Note that the CN 106 may provide the WTRUs 102a, 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.

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

[0042] In an exemplary embodiment, the other network 112 may be a WLAN.

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

[0044] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, an AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a width that is dynamically set via signaling. The primary channel may be the operating channel of the BSS, but may also be used by STAs to establish a connection with the AP. In certain representative 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, STAs (e.g., all STAs), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0045] A High Throughput (HT) STA 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.

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

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

[0048] WLAN systems that may support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that may be designated as a 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 configured by the STA and / or limited among all STAs operating in the BSS that support the smallest bandwidth operating mode. In an 802.11ah embodiment, the primary channel may be 1 MHz wide for STAs (e.g., MTC-type devices) that support (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) configuration may depend on the state of the primary channel. For example, when the primary channel is active due to a STA (that only supports a 1 MHz mode of operation) transmitting to the AP, the entire available frequency band may be considered active even though most of the frequency band may remain dormant and available.

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

[0050] 1D is a system diagram illustrating the RAN 113 and the CN 115, according to one embodiment. As mentioned above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also communicate with the CN 115.

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

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

[0053] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing another RAN (e.g., eNodeBs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate with and connect to a gNB 180a, 180b, 180c while also communicating with and connecting to another RAN, such as an eNodeB 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNodeBs 160a, 160b, 160c substantially simultaneously. In a non-standalone setting, the eNodeBs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

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

[0055] 1D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0056] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may function as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. The network slicing may be used by the AMF 182a, 182b to customize the CN support of the WTRUs 102a, 102b, 102c based on the type of service utilizing the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced Massive Mobile Broadband (eMBB) access, services for Machine Type Communication (MTC) access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[0057] The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 115 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via an N4 interface. The SMFs 183a, 183b may select and control the UPFs 184a, 184b and configure the routing of traffic through the UPFs 184a, 184b. The SMFs 183a, 183b may perform other functions such as managing and allocating WTRU IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session types may be IP-based, non-IP-based, Ethernet-based, etc.

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

[0059] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 115 and the PSTN 108. Note that the CN 115 may provide the WTRUs 102a, 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, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b through the UPFs 184a, 184b via an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.

[0060] 1A-1D and the corresponding description thereof, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-ab, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other devices described herein may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

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

[0062] One or more emulation devices may perform one or more functions, inclusive, while not implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in an undeployed (e.g., test) wired and / or wireless communication network to perform testing of one or more configuration elements. One or more of the emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, for example, one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0063] In this document, the following abbreviations and acronyms are used, among others: Acknowledgement (ACK), Block Error Rate (BLER), Bandwidth Part (BWP), Channel Access Priority (CAP), Channel access priority class (CAPC), Clear Channel Assessment (CCA), Control Channel Element (CCE), Control Element (CE), Configured Grant (CG) or Cell Group (CG), Cyclic Prefix (CP), Conventional OFDM (relying on cyclic prefix), CP-OFDM (dependent on cyclic prefix), Channel Quality Indicator (CQI), Cyclic Redundancy Check (CRC), Channel State Information (CSI), Contention Window (CQI), Channel Quality Indicator ... Window (CW), Contention Window Size (CWS), Channel Occupancy (CO), Downlink Assignment Index (DAI), Downlink Control Information (DCI), Downlink feedback information (DFI), Dynamic grant (DG), Downlink (DL), Demodulation Reference Signal (DM-RS), Data Radio Bearer (DRB), Enhanced Licensed Assisted Access (LICA)Access (eLAA), Further enhanced Licensed Assisted Access (FeLAA), Hybrid Automatic Repeat Request (HARQ), License Assisted Access (LAA), Listen-Before-Talk (LBT), Long Term Evolution (LTE) from 3GPP LTE R8 onwards, Negative ACK (NACK), Network Energy Saving (NES), Modulation and Coding Scheme (MCS), Master Information Block (MIB), Multiple Input Multiple Output (MIMO), New Radio (NR), Orthogonal Frequency-Division Multiplexing (OFDM), Physical Layer (PHY), Process ID ID, PID), Paging Occasion (PO), Physical Random Access Channel (PRACH), Primary Synchronization Signal (PSS), Random Access (or Procedure) (Random Access, RA), Random Access Channel (RACH), Random Access Response (RAR), Radio access network Central Unit (Radio access network Central Unit, RCU), Radio Front end (Radio Front end, RF), Radio Link Failure (RLF), Radio Link Supervision (Radio LinkMonitoring (RLM), Remaining System Information (RMSI), Radio Network Identifier (RNTI), RACH occasion (RACH occasion (RO), Radio Resource Control (RRC), Radio Resource Management (RRM), Reference Signal (RS), Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Service Data Unit (SDU), System Information (SI), System Information Block (SIB), Sounding Reference Signal (SRS), Synchronization Signal (SS), Synchronization Signal Block (SSB), Secondary Synchronization Signal (SSS), Switching Gap (SWG) (in self-contained subframes), Semi-Persistent Scheduling (SPS) Scheduling (SPS), Supplemental Uplink (SUL), Secondary Node (SN), Transport Block (TB), Transport Block Size (TBS), Transmission / Reception Point (TRP), Time-sensitive communications (TSC), Time-sensitive networking (TSN)networking (TSN), Uplink (UL), Ultra-Reliable and Low Latency Communications (URLLC), Wide Bandwidth Part (WBWP), and Wireless Local Area Network (WLAN) and related technologies (IEEE 802.xx area).

[0064] In Rel-18, network energy savings are being studied to allow the network to attempt to minimize power consumption for device transmission and / or reception. Such minimization is beneficial to reduce operational costs and environmental sustainability. The design of NR in Rel-15 more efficiently minimizes transmissions from the network when there is no data compared to conventional systems. For example, always-on cell-specific reference signals (CRS) are not used in NR. However, there is still potential for energy consumption reduction. For example, the network may consume energy when it is not transmitting during other activities, such as baseband (i.e., digital) processing for reception or beamforming. Furthermore, such "idle" power consumption may not be negligible in dense networks, even if the network does not serve a WTRU during a given period. Energy consumption may be reduced if the network can turn off these activities when it is not transmitting to a WTRU. Furthermore, NR may support beamforming with many ports (e.g., up to 64 transmit and receive ports), where energy consumption increases as the number of ports utilized increases. However, it may not be necessary for the network to utilize the maximum number of ports for all WTRUs. In one or more cases, energy consumption may be reduced if the network can adapt the number of ports to a required or minimum number of ports.

[0065] In one or more cases, the CSI may include one or more of a Channel Quality Index (CQI), a Rank Indicator (RI), a Precoding Matrix Index (PMI), an L1 channel measurement (e.g., an RSRP such as an L1-RSRP, or a signal to interference plus noise ratio (SINR)), a CSI-RS resource indicator (CRI), a SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), and / or any other measurement measured by the WTRU from the configured CSI-RS or SS / PBCH blocks. In one or more cases, the Uplink Control Information (UCI) may include CSI, HARQ feedback for one or more HARQ processes, Scheduling Request (SR), Link Recovery Request (LRR), CG-UCI, and / or other control information bits that may be transmitted on the PUCCH or PUSCH. In one or more cases, any channel conditions related to the state of the radio / channel conditions may be determined by the WTRU based on one or more of WTRU measurements, L3 / mobility based measurements, RLM state, and / or channel availability in the unlicensed spectrum. For example, the WTRU may determine the channel conditions based on WTRU measurements such as, but not limited to, L1 / SINR / RSRP, CQI / MCS, channel occupancy, RSSI, power headroom, exposure headroom, etc. In another embodiment, the WTRU determines the channel conditions based on one or more L3 / mobility based measurements such as, but not limited to, RSRP, RSRQ, etc. In yet another embodiment, the WTRU determines the channel conditions based on channel availability in the unlicensed spectrum.For example, the WTRU may determine whether the channel is occupied based on the determination of the LBT procedure. In another case, the WTRU may determine whether the channel has experienced consistent LBT failures. In one or more cases, the PRACH resource may be provided, for example, but not limited to, in frequency. In one or more cases, a PRACH occasion (RO) may be provided, for example, but not limited to, in a measurement of time. In one or more cases, a preamble format may be provided, for example, but not limited to, in terms of total preamble duration, sequence length, guard time duration, and / or cyclic prefix length. In one or more cases, a certain preamble sequence may be used for transmission of a preamble in a random access procedure. In one or more cases, the PRACH resource may be characterized based on one or more of a frequency resource, a time resource, a preamble format, etc. The frequency resource may include, for example, but not limited to, subcarriers, RBs, etc. The time resources may include, for example, but are not limited to, PRACH occasions, symbols, subframes, etc. The preamble format may include, for example, but are not limited to, one or more of a total preamble duration, a sequence length, a guard time duration, in terms of a cyclic prefix length.

[0066] In one or more cases, the characteristics of the scheduling information (e.g., uplink grant or downlink assignment) may include one or more of the following: frequency allocation, aspects of time allocation such as duration, priority, modulation and coding scheme, transport block size, number of spatial layers, number of transport blocks carried, TCI state or SRI, number of repetitions, and a decision of whether the grant is a configured grant type 1, type 2, or dynamic grant. In one or more cases, the indication by the DCI may include one or more of the following: an explicit indication by a DCI field or RNTI used to mask the CRC of the PDCCH (physical downlink control channel) and an implicit indication by properties such as, but not limited to, DCI format, DCI size, CORESET or search space, aggregation level, identity of the first control channel resource for the DCI (e.g., index of the first CCE). In one or more cases, the mapping between the properties and values ​​may be signaled by RRC or MAC. For example, the WTRU may signal, via RRC or MAC, the mapping between the properties and the values.

[0067] In one or more cases, the NR system information (SI) may include a MIB (Master Information Block) and several SIBs (System Information Blocks). In one or more cases, the SIB may be divided into a minimum SI and an other SI. In one or more cases, the minimum SI may carry information required for initial access and to acquire any other SI. In one or more cases, the minimum SI may include the MIB and SIB1. In order for the WTRU to be allowed to camp on a cell, the WTRU may obtain the contents of the minimum SI of that cell. In one or more cases, the other SI may include all SIBs that are not broadcast in the minimum SI. In one or more cases, the WTRU may not receive these SIBs before accessing the cell. In one or more cases, the other SI may also be known as on-demand SI, since the gNB may transmit / broadcast these SIBs when explicitly requested by the WTRU. The gNB may transmit / broadcast these SIBs when explicitly requested by the WTRU for network energy saving purposes.

[0068] In one or more cases, the MIB may include cell barring status information and further system information, e.g., essential physical layer information of cells required to receive the CORESET#0 configuration. In one or more cases, the MIB may be broadcast periodically on the BCH. For example, the MIB may be broadcast periodically on the BCH with a periodicity of 80 ms, and repeated transmissions may occur within the 80 ms. In one or more cases, SIB1 may define the scheduling of other system information blocks. SIB1 may also include information required for initial connection. In one or more cases, SIB1 may be referred to as Remaining Minimum SI (RMSI). In one or more cases, SIB1 may be broadcast periodically on the DL-SCH or sent in a dedicated manner on the DL-SCH to UEs in RRC_CONNECTED.

[0069] FIG. 2 illustrates an exemplary time-frequency structure of a transmission 200 including a synchronization signal block (SSB). In one or more cases, the synchronization signal and PBCH block (SSB) may include a primary synchronization signal (PSS) 202 and a secondary synchronization signal (SSS) 204. Each of the PSS 202 and SSS 204 occupies one symbol and 127 subcarriers. The SSB may include a PBCH 206 that spans three OFDM symbols and 240 subcarriers, but leaves an unused portion in the center for the SSS 204 on one symbol, as shown in FIG. 2. In one or more cases, the possible time locations of the SSB within a half frame may be determined by the subcarrier spacing and the periodicity of the half frame in which the SSB is transmitted as set by the network. Different SSBs may be transmitted in different spatial directions, for example, by the eNB. For example, different SSBs may be transmitted in different spatial directions during a half frame. Different SSBs may be transmitted, for example, using different beams and / or in different spatial directions across the coverage area of ​​a cell.

[0070] Within the frequency span of a carrier, multiple SSBs may be transmitted. In some cases, the PCI of SSBs transmitted at different frequency locations may not be unique. For example, different SSBs in the frequency domain may have different PCIs. In one or more cases, when an SSB is associated with an RMSI, the SSB may be referred to as a cell-defined SSB (CD-SSB). In one or more cases, a PCell may be associated with a CD-SSB located on a synchronization raster. In one or more other cases, a PCell may always be associated with a CD-SSB located on a synchronization raster.

[0071] In one or more cases, the WTRU may assume band-specific subcarrier spacing for the SSB. In one or more other cases, the WTRU may assume band-specific subcarrier spacing for the SSB unless the network configures the WTRU to assume a different subcarrier spacing.

[0072] In one or more cases, several beams may be associated with a given cell. In one or more cases, multiple SSBs may be transmitted in a given cell on different beams (i.e., in the case of beam sweeping). FIG. 3 illustrates an example of beam sweeping performed between a gNB 306 and multiple WTRUs (e.g., a first WTRU1 and a second WTRU2). As shown in FIG. 3, multiple SSBs 302 may be transmitted at regular intervals. Furthermore, each SSB may be identified by a unique number 308, e.g., an SSB index. The SSB index 308 may be mapped to each beam. Each SSB may be transmitted via a specific beam radiated in a specific direction. Multiple WTRUs, such as a first WTRU1 and a second WTRU2, may be located at various locations around the gNB 306. As shown in FIG. 3, the WTRU may measure the signal strength of each SSB detected by the WTRU over a period of time (e.g., the period of one SSB set). Further, based on the measurement results, the WTRU may identify the SSB index with the strongest signal strength. For example, as shown in FIG. 3, beam #1 is the best beam (i.e., the selected beam) for the first WTRU1. That is, beam #1 provides the strongest signal strength to the first WTRU1. In another embodiment, as shown in FIG. 3, beam #7 is the best beam for the second WTRU2. That is, beam #2 provides the strongest signal strength to the second WTRU2.

[0073] In one or more cases, the number of different beams being transmitted may be determined based on the number of SSBs being transmitted within an SSB burst set, which may be, for example, but not limited to, a set of SSBs transmitted within a 5 ms window of SSB transmission. For example, in FR1, the maximum number of SSBs in an SSB set may be 4 or 8, and in FR2, the maximum number of SSBs in an SSB set may be 64.

[0074] In one or more cases, the WTRU may determine whether the WTRU can transmit or receive on a particular resource. For example, the WTRU may determine whether the WTRU can transmit or receive on a resource based on a network availability state. The network availability state may include information that implies and / or indicates a power saving state of the gNB. In one or more cases, the availability state may correspond to a network energy saving state or a gNB activity level. In one or more cases, the availability state may be uplink specific (e.g., DRX) or downlink specific (e.g., DTX). Additionally or alternatively, the availability state may change on a symbol-by-symbol, slot-by-slot, frame-by-frame, or with a granularity of a longer duration. In one or more cases, the WTRU may determine the availability state. In one or more other cases, the network may indicate the availability state. The availability state may be, for example, without limitation, "on", "off", "dormant", "micro sleep", "deep sleep", or other similar state. Such states may be abstracted by network (NW) configuration parameters and / or values. An "off" availability state may indicate that the baseband hardware of the gNB is turned off. For example, an "off" availability state may indicate that the baseband hardware of the gNB is completely turned off. A "sleep" availability state may indicate that the gNB periodically wakes up to transmit certain signals (e.g., but not limited to, presence signals, synchronization, reference signals, etc.) or to receive certain UL signals. Availability states may be configured, for example, with periodic availability and non-availability periods. In some availability states, one or more DL or UL resources may not be available during a period of time (e.g., during a non-availability period). Thus, the network may turn off baseband processing and other activities.In one or more cases, some measurement resources (eg, SSB or CSI-RS) may be available in some availability states.

[0075] In one or more cases, the WTRU may send a request to the network to modify the availability state. For example, the WTRU sends a wake-up request to the network to request that the network modify the availability state to include available resources that meet the WTRU requirements. The wake-up request may include a transmission that a low-complexity receiver may decode at the gNB. In some cases, the wake-up request transmission may require a minimum energy consumption requirement to be decoded. It should be noted that the wake-up request, turn-on request, or switch-on WTRU assistance information may be used interchangeably as described herein. In one or more availability states (e.g., "microsleep" or "deep sleep"), the WTRU may use the wake-up request exclusively. Furthermore, the wake-up request may refer to a physical uplink signal transmitted by the WTRU to request a change in the availability state. A physical layer design of the wake-up request signal is further detailed in U.S. Patent Application No. 63 / 275,207, the entirety of which is incorporated herein by reference. In one or more other cases, the switch-on request may be a physical layer or L2 indication from the WTRU to the network. The WTRU may deliver the L2 indication, for example, but not limited to, as one or more of MAC CE, UCI, RRC signaling, PUCCH, RACH indication, etc. Additionally or alternatively to the foregoing, the WTRU may include switch-on WTRU assistance information and / or positioning reports.

[0076] In one or more cases, the WTRU determines the availability state, for example, from receiving an availability state indication from L1 / L2 signaling (e.g., a group-common DCI or indication). In one or more other cases, the WTRU determines the availability state implicitly from receiving periodic DL signaling or not receiving periodic DL signaling. In one or more cases, the WTRU determines whether resources are available for transmission / reception and / or measurement for the determined network availability state if the WTRU determines that the resources are applicable in an active availability state. The availability state may be applicable to at least one transmission resource, reception resource, or measurement resource. The availability state may be applicable to at least one time period, such as a time slot or a time symbol. The availability state may be applicable to one or more of, for example, but not limited to, a serving cell, a cell group, a frequency band, a bandwidth portion, a TRP, a set of spatial elements, and a range of frequencies within a bandwidth portion, etc.

[0077] In one or more cases, network energy consumption may be very significant and may be unnecessary in many cases, for example, during quiet times. In some cases, to reduce energy consumption, the network may turn off small cells or FR2 power consuming cells during quiet times and rely on macro cells for coverage. In one or more cases, the gNB may combine information, including but not limited to WTRU measurements, WTRU assistance information, interference conditions, load information, ownership information, to determine which cells to turn off and which cells to rely on. In one or more cases, turning off a gNB informs neighboring cells whether they should be turned on / off. However, in some cases, the network may not be aware of a sudden increase in demand for network access, for example, when the number of active WTRUs changes or when the concentration of WTRUs increases. Furthermore, some WTRUs may experience coverage loss when capacity boosting cells are turned off. In some cases, the WTRU may want to inform the network about the coverage loss. However, during busy hours, network power consumption may be very significant, especially when all or a large number of bands, carriers, antenna chains, beamforming antennas are used. Thus, network access capabilities may be adapted during busy hours to reduce energy consumption. In one or more cases, the power consumed related to MIMO may be proportional to one or more of the number of active chains, the number of active TRPs, the number of SSBs, the number of spatial multiplexing streams and MU-MIMO schemes used, and whether narrow beams are used. Thus, the disclosure provided herein provides a solution that allows the network to know when it can turn off transmission and reception or use a reduced number of antenna ports for such resources without compromising the quality of service of the served WTRUs.

[0078] In one or more cases, the WTRU may be configured to receive a dormant cell presence indication. In some cases, the WTRU monitors a presence indication associated with a sleep / off gNB. Additionally or alternatively, the WTRU may monitor a presence indication associated with a sleep / off gNB after satisfying a condition for transmitting switch-on request / assistance information. In one or more cases, the WTRU may monitor for reception of a presence indication or signal associated with a gNB configured in one or more availability states. The availability state may be, for example, on, off, dormant, or deep sleep. The presence indication may be a physical downlink signal transmitted by an associated cell or gNB that is sleeping. For example, a gNB may be sleeping in several availability states (e.g., deep sleep, microsleep, dormant, or off). Alternatively, the presence indication may be a downlink information bit delivered to the WTRU. For example, the downlink information bit may be delivered to the WTRU via broadcast signaling (e.g., SIB). In another embodiment, the downlink information bits may be delivered to the WTRU via dedicated signaling (e.g., RRC signaling or MAC CE). The WTRU may conditionally monitor for a presence indication occasion if either the trigger / condition for sending the activation WTRU assistance information or the switch-on request is met.

[0079] In one or more cases, the WTRU may receive a presence indication via different serving cells and / or different TRPs within a cell. In some cases, different serving gNBs may monitor or deliver a presence indication when an associated gNB is configured in a certain availability state (e.g., off or dormant). In some cases, the WTRU may monitor a presence indication per TRP. In such cases, a presence indication may be associated with a particular TRP. In some cases, different TRPs may transmit a presence indication associated with a certain TRP.

[0080] In one or more cases, the WTRU may determine the availability state of the cell from at least one property of an availability state indication of a received presence indication associated with the cell. The presence indication may indicate an availability state associated with the cell related to the presence indication occasion. In some cases, the determined or indicated availability state may be applicable until the next presence indication occasion.

[0081] In one or more cases, the WTRU is configured with monitoring occasions. The WTRU may be configured with monitoring occasions to detect a presence indication associated with a cell, a TRP, or a carrier. In some cases, the carriers may be located on different cells. In some cases, the WTRU may be configured with presence indication occasions to monitor DL ​​signals and / or indications related to the presence indication. The WTRU may be configured with a periodicity associated with the presence indication per cell. The WTRU may be configured to monitor an occasion pattern to detect a presence indication for a cell in addition to or instead of the periodicity association. In one or more cases, the presence signal may be a DL signal or channel. In some cases, the presence signal is a DL signal or channel including an SSB signal, a reference signal, a PDCCH transmission, and / or a PDCSCH transmission. For each cell or carrier, the WTRU may be configured with an association between one or more of an SSB, RS, or other DL signal and a presence signal for the cell.

[0082] In one or more cases, the WTRU transmits one or more of a switch-on request, WTRU assistance information, or RA after successful presence signal detection. The WTRU may transmit and / or trigger one or more of a wake-up request, a switch-on request, and wake-up WTRU assistance information transmission. For example, the WTRU may transmit and / or trigger one or more of a wake-up request, a switch-on request, and wake-up WTRU assistance information transmission upon successful presence signal detection. In some cases, the WTRU may initiate a new random access procedure on the cell. For example, a WRTU initiates a new random access procedure on the cell when the WTRU successfully detects a presence indication associated with the cell. In some cases, the WTRU may start a timer upon successful presence signal detection and / or transmit a wake-up request upon expiration of the timer. In some cases, the WTRU may assume that an availability state is applicable for the associated cell while the timer is running. In some cases, the WTRU may fall back to a different availability state or a default availability state after expiration of the timer.

[0083] In one or more cases, the WTRU may determine or change the active availability to a predefined or configured value when the WTRU detects or does not detect a presence signal. In some cases, the WTRU may assume that an availability state is not active when the WTRU does not detect a presence signal associated with the state. For example, the WTRU assumes that the availability state is off, microsleep, or deep sleep when the WTRU does not detect or receive a presence signal associated with the availability state "on."

[0084] In some cases, the WTRU determines that a gNB response to a presence indication signal or wake-up signal is not detected or received based on the signal being measured having a channel quality metric (e.g., RSRP or SINR) below a configured threshold. The WTRU may determine that a presence signal is detected based on the WTRU synchronizing to a PSS / SSS signal transmitted as part of the presence signal. The WTRU may sleep, activate DRX, or change its DRX cycle until the next presence signal indication. In some cases, the WTRU sleeps, activates DRX, or changes its DRX cycle based on the WTRU not successfully receiving and detecting a presence signal and / or if the WTRU is unable to connect to other serving cells. In some cases, the WTRU may monitor a presence signal of another serving cell if a presence signal was not successfully detected in the serving cell or the last serving cell (e.g., the last serving cell index before performing a handover).

[0085] In some cases, the WTRU may use a counter or presence indication detection timer before changing the availability state to active based on receiving a presence indication. In some cases, the WTRU may use a counter or presence indication detection timer before making an availability state decision based on receiving a presence indication. In some cases, the WTRU changes the availability state if the detection timer expires. In other cases, the WTRU changes the availability state if the WTRU counts a consecutive number of missing samples of a presence indication. For example, the WTRU may be configured with a period for measuring presence indication samples. The WTRU may consider a presence indication to be not detected if the WTRU does not measure a presence indication. For example, the WTRU considers a presence indication to be not detected if the WTRU determines that the channel measurement is below a threshold before the end of the detection window.

[0086] In one or more cases, the WTRU may change the availability state of a cell. For example, the WTRU changes the availability state of a cell after successfully receiving a response from a requested cell to a transmitted request or switch-on request. In some cases, the WTRU may change the availability state associated with detecting a presence signal (e.g., the WTRU assumes an "on" state) after the WTRU successfully receives a response from a requested cell to a transmitted WTRU assistance information or switch-on request. In some cases, the received response may be a DL signal or channel or an L2 message. The DL signal or channel may be, for example, but not limited to, SSB, CSI-RS, PRS, PDCCH, DCI, PDSCH, HARQ-ACK. The L2 message may be, for example, an RRC message, DL MAC CE, Msg2, MsgB, or Msg4.

[0087] In one or more cases, the WTRU may monitor additional SSB and / or CSI-RS resources. For example, the WTRU may monitor additional SSB and / or CSI-RS resources after a transmission switch-on request. In another embodiment, the WTRU may monitor additional SSB and / or CSI-RS resources after receiving a response to the switch-on request. In some cases, the WTRU may start monitoring additional TRP, SSB, and / or CSI-RS resources after transmitting activation WTRU assistance information and / or a switch-on request. In some cases, the WTRU may start monitoring additional TRP, SSB, and / or CSI-RS resources after successfully receiving a response to the switch-on request. The WTRU may change the availability state associated with the detection of a presence signal (e.g., on) after successfully measuring channel conditions (e.g., RSRP, SINR) on the measurement resources of the associated cell that are measured above a configured threshold.

[0088] In some cases, the physical layer structure of the presence indication signal may include one or more structures described herein. For example, the presence indication signal may be a simplified or stripped down SSB signal, such as a PSS / SSS, wide beam SSB, or omnidirectional SSB without multiplexed PBCH. In some cases, the WTRU may attempt to monitor and synchronize to the simplified or stripped SSB signal on a synchronization raster that is different from the synchronization raster used / configured for the legacy WTRU. In another embodiment, the presence indication signal may be a PRS. In some cases, the WTRU may receive a PRS from a different cell or TRP. In some cases, the WTRU may receive a PRS on a configured subset of PRS resources. In another embodiment, the presence indication signal may be a CSI-RS. In some cases, the WTRU may receive a CSI-RS from a different cell or TRP. In some cases, the WTRU may receive a CSI-RS on a configured subset of CSI-RS resources. In another embodiment, the WTRU may detect a presence indication based on energy sensing the ether. For example, the WTRU may detect a DL signal associated with the wake-up radio. In yet another embodiment, the presence indication signal may be a signal generated from one or more sequences, such as, but not limited to, a Zadoff-Chu sequence, an M sequence, or a Gold sequence. In another embodiment, the presence indication signal may be a PDSCH or a PDCCH received on a different cell or TRP. In some cases, the WTRU may receive a PDSCH or a PDCCH on a configured subset of resources, a core set, or a search space. In another embodiment, the presence indication signal may be one or more SSBs received from a different cell or TRP. In some cases, the WTRU may receive one or more SSBs on a configured subset of SSB occasions.

[0089] In one or more cases, the WTRU may monitor a synchronization relationship between the presence indication and the SSB. In one or more cases, the WTRU may monitor the presence indication during configured or predefined occasions. For example, the predefined occasions may be tied to an SSB transmission time or a subset of SSB transmission times for a serving cell associated with the indication according to a defined timing relationship. The timing of the presence indication occasions or their timing relationship with the SSB may be indicated by higher layers, such as, but not limited to, system information.

[0090] In some cases, the WTRU may perform a time-frequency synchronization procedure before attempting to detect a presence indication signal. The WTRU may use the presence indication signal to perform time-frequency synchronization. In some cases, the WTRU may monitor a presence indication on the same cell associated with the presence indication if the presence indication is time-frequency synchronized to that cell. The WTRU may monitor and / or detect a presence signal based on SSB transmissions using a new subset of the synchronization raster (or a different base sequence).

[0091] In one or more cases, upon the WTRU successfully receiving a presence indication or a gNB response to a subsequent wake-up or switch-on request, the WTRU assumes a different set of available SSBs in the cell. For example, the WTRU may assume a different set of available SSBs in the cell, such as, but not limited to, legacy SSBs associated with an "on" availability state. In some cases, the WTRU may perform a different synchronization and / or initial access procedure upon detecting a set of available SSBs. In one or more cases, the WTRU may assume a different SSB pattern and / or periodicity upon detection of a stripped-down SSB or extended SSB format. In one or more cases, the WTRU may read the RMSI for the alternative SSB pattern / configuration upon reception of a stripped-down SSB / presence signal.

[0092] In one or more cases, the WTRU receives a presence indication having an L2 structure. In some cases, the WTRU receives the presence indication as information. In some cases, the WTRU receives the presence indication from different cells, carriers, and / or TRPs. In some cases, the presence indication may be an RRC message or a DL MAC CE. The presence indication L2 signal / information may include a variety of information. For example, the presence indication L2 signal / information may include an associated cell index for which the presence indication is applicable. In another embodiment, the presence indication L2 signal / information may include an associated TRP index for which the presence indication is applicable. In another embodiment, the presence indication L2 signal / information may include an associated carrier or frequency band for which the presence indication is applicable. In another embodiment, the presence indication L2 signal / information may include an availability state associated with the indicated cell, TRP, or carrier. In another embodiment, the presence indication L2 signal / information may include associated synchronization, cell search, or initial access information that may be used on the indicated cell (e.g., PRACH resources). In another embodiment, the presence indication L2 signal / information may include a duration associated with the availability state. In some cases, the duration associated with the availability state may be implicitly implied from the receipt of an L2 presence indication. In one or more cases, the WTRU may assume that the cell is no longer available (or the indicated / implied availability state is no longer applicable) after expiration of such a timer. In some cases, the WTRU may assume that the indicated / implied availability state is no longer applicable. In another embodiment, the presence indication L2 signal / information may include an RRC message or additional configuration. In another embodiment, the presence indication L2 signal / information may include a MAC CE subheader or identifier.

[0093] In one or more cases, the WTRU may be configured with a UL availability window. In some cases, during the UL availability window, the WTRU transmits a UL signal after detecting a presence indication and / or at preconfigured periodic occasions. In some cases, the WTRU may maintain a "gNB activity timer". In some cases, the activity timer starts after the WTRU receives a response to the WTRU's wake-up request signal, WTRU assistance information, or a switch-on request. In some cases, the WTRU starts the "gNB activity timer" after receiving a presence indication (e.g., SSB) or an indication by a DCI or MAC CE (e.g., a WTRU-specific scheduling DCI). The WTRU may start the gNB activity timer at a predefined periodic occasion. In some cases, the configuration of the predefined periodic occasions may be given by broadcast or dedicated signaling. In some cases, the periodicity between UL windows may be configured per availability state. In some cases, the WTRU applies the periodicity according to the active availability state. In one or more cases, the WTRU may independently maintain gNB activity times for the DL and UL directions, e.g., the WTRU may maintain a DL gNB activity timer and a separate UL gNB activity timer.

[0094] While the gNB activity timer is running or during gNB active time (e.g., availability period of an availability state), the WTRU may transmit UL signals, UCI, or data (e.g., PUSCH, PUCCH, PRACH, SRS, UCI, CQI reports, and / or measurement reports) and / or monitor DL ​​signals and channels (e.g., PDSCH, PDCCH, CSI-RS, SSB, PRS, or channel measurement signals). Upon expiration of the "gNB activity timer", the WTRU may switch to a different availability state. In some cases, the WTRU extends the gNB activity timer after a UL transmission or DL ​​reception. Upon expiration of the "gNB activity timer", the WTRU falls back to a less periodic gNB activity cycle or availability state. In some cases, in a less periodic gNB activity cycle or availability state, the UL availability occasion window and / or presence indication may occur at a different configured periodicity.

[0095] In one or more cases, the WTRU monitors a presence indication prior to the UL availability window. In some cases, the WTRU monitors a presence indication prior to the UL availability window in a subset of the gNB activity cycle or availability state. In one or more cases, the WTRU may determine that the UL availability window applies conditionally upon successful reception of a presence indication or indication from the network by DCI or MAC CE. In some cases, the WTRU may determine that the UL availability window applies conditionally upon successful reception of a presence indication based on a subset of the gNB activity cycle or availability state. For example, the WTRU initiates a UL availability window based on the WTRU receiving a presence indication while the WTRU is in a "deep sleep", "dormant", or "off" availability state. The WTRU assumes the UL availability window to be automatically initiated on preconfigured periodic occasions in the "on" or "microsleep" availability state.

[0096] In one or more cases, the WTRU may be configured with a switch-on request and activation WTRU assistance information. In some cases, the WTRU may be configured as a "capacity boosting cells / band" by broadcast or dedicated signaling with a subset of cells, carriers, or bands. In some cases, based on the configuration, the WTRU may send a switch-on / activation request and / or activation WTRU assistance information. For a given cell (e.g., PCI), the WTRU may be configured with complementary / associated "capacity boosting cells or carriers." The capacity boosting cells or carriers may be, for example, small cells associated with a macro cell. In some cases, the WTRU may consider cells of an SCG / SN as capacity boosting cells associated with one or more cells in the MCG / MN. The WTRU may consider carriers of the same gNB (e.g., SCell) as capacity boosting cells associated with a primary carrier on that same gNB (e.g., PCell). The WTRU may implicitly determine a capacity boosting cell as any cell configured with a presence indication, which may be sent from the same cell or a different cell.

[0097] In case of a capacity boosting cell associated with another cell, the WTRU may monitor a presence indication on the associated cell and / or transmit an activation WTRU assistance information or request using uplink resources of the associated cell. In one or more cases, the WTRU triggers and / or transmits a switch-on request or activation WTRU assistance information. For example, the WTRU triggers and / or transmits a switch-on request or activation WTRU assistance information to indicate a change in the availability state of a cell designated as capacity boosting. In some cases, the WTRU triggers and / or transmits a switch-on request or activation WTRU assistance information to indicate a change in the availability state of a cell designated as capacity boosting based on a condition or trigger being met. In one or more cases, the condition or trigger may include detecting a cell presence signal. For example, detecting a cell presence signal may include detecting a cell presence signal in a past time period associated with measuring a presence indication. In another example, detecting a cell presence signal may include detecting a cell presence signal after a trigger condition related to transmitting activation assistance information is met. For example, a trigger condition associated with transmitting the activation assistance information may be satisfied by detecting a presence signal associated with the requested cell accompanied by a channel quality metric above a threshold. In one or more cases, the condition or trigger may include not detecting a presence signal associated with the cell. For example, not detecting a presence signal associated with the cell may correspond to not detecting a presence signal in a past time period associated with measuring a presence indication. In one or more cases, the condition or trigger may be based on a channel measurement, where the condition or trigger is satisfied if the channel measurement is above or below a configured threshold. In one embodiment, the channel measurement may be a measured RSSI or RS-SINR. In another embodiment, the channel measurement may be a lack of SSB samples to measure on the requested cell or the serving cell.In another example, the channel measurements may include not detecting the configured SSB and / or CSI-RS of the cell or measuring the CSI-RS below a configured threshold. In one or more cases, the WTRU measurements may be physical layer measurements or L3 measurements. The physical layer measurements may be, for example, but not limited to, SINR / RSRP, CQI, channel occupancy, RSSI, power headroom, exposed headroom, etc. The L3 measurements may be, for example, but not limited to, RSRP, RSRQ, etc. The WTRU may include such measurements in the WTRU assistance information content. In one or more cases, the condition or trigger may be based on the channel measurements and the condition or trigger is met if the WTRU detects high loading or interference, if the WTRU does not detect an SSB, or if the WTRU does not detect a PSS / SSS on the requested cell or any cell. In one or more cases, the condition or trigger may be based on the channel measurements and the condition or trigger is met if the WTRU detects channel availability in the unlicensed spectrum. For example, the WTRU may detect channel availability in the unlicensed spectrum when the channel is occupied based on the determination of the LBT procedure. In another embodiment, the WTRU may detect channel availability in the unlicensed spectrum when the channel is deemed to have experienced consistent LBT failures. For example, the WTRU may trigger an activation WTRU assistance information after detecting consistent UL LBT failures.

[0098] In one or more cases, the condition or trigger may include the arrival of new data. For example, the WTRU may determine that the condition or trigger is met if data arrives from one or more of a subset of the DRB, SRB, LCH, LCG, etc. In another embodiment, the WTRU may determine that the condition or trigger is met if the arriving data is associated with a certain priority level or index. The WTRU may reflect such data in the assistance information content.

[0099] In one or more cases, the condition or trigger may include triggering an RRC state change or an RRC procedure, such as, but not limited to, RRC resumption, RRC establishment, RRC re-establishment, etc. In one or more cases, the condition or trigger may include triggering receipt of an RRC message (e.g., RRC release).

[0100] In one or more cases, the conditions or triggers may include one or more of performing a positioning procedure, transmitting a positioning report, and determining a location within the coverage of a cell as a best server. For example, the WTRU triggers the wake-up WTRU assistance information when the WTRU determines that the WTRU's location is within the best server coverage of a capacity boosting cell. The best server coverage may be, for example, an area where the WTRU measures the capacity cell as having the best channel condition compared to other cells in the same frequency. In one or more cases, the WTRU may include the WTRU's location in the WTRU assistance information. In one or more cases, the WTRU may be allowed to transmit the wake-up WTRU assistance information based on the WTRU's determined location being within a particular area or predefined coverage of the requested cell, or may be adjusted to do so. The particular area may include a configured area per cell, such as, but not limited to, a coverage area of ​​another alternative serving cell, or a distance from a known location of the requested gNB. In one or more cases, the condition or trigger may include an amount of buffered data above a threshold. The WTRU may trigger a wake-up request based on the amount of buffered data exceeding a configured or predefined threshold. For example, based on a configured subset of DRBs, LCHs, or LCGs, the WTRU triggers a wake-up request if the amount of buffered data exceeds a configured or predefined threshold. The WTRU may include the data volume in the WTRU assistance information (e.g., a BSR or modified BSR for a subset of LCHs / RBs / LCGs). The WTRU may be configured with a list of RBs or priorities that may trigger the inclusion / transmission of the WTRU assistance information.

[0101] In one or more cases, the condition or trigger may include triggering a BSR and / or a SR. For example, the WTRU may trigger the activation WTRU assistance information based on a new BSR and / or a new SR being triggered. In some cases, the WTRU may trigger the activation WTRU assistance information based on a new BSR and / or a new SR being triggered if a new SR is for a given SR configuration. In one embodiment, triggering transmission of the activation assistance information may trigger a new BSR.

[0102] In one or more cases, the condition or trigger may include the availability of UCI or data (e.g., HARQ ACK, CSI, or PMI) to transmit, a priority associated with the UCI, or an LCH or DRB associated with the UCI. For example, the WTRU may trigger transmission of the activate WTRU assistance information based on the availability of UCI or data to transmit, a priority associated with the UCI, or an LCH or DRB associated with the UCI.

[0103] In one or more cases, the condition or trigger may include detection of a beam failure or an RLM event (e.g., an RLF). For example, the WTRU may trigger transmission of wake-up WTRU assistance information based on the WTRU detecting a beam failure or an RLF on a capacity boosting cell and / or a cell associated with the WTRU's currently active serving cell.

[0104] In one or more cases, the condition or trigger may include triggering an L3 or mobility event. The WTRU may include such a trigger in the WTRU assistance information. For example, the WTRU may include the trigger as a WTRU mobility state in the WTRU assistance information.

[0105] In one or more cases, the condition or trigger may include entering a DRX state, cycle, or power saving mode, including short or long connected mode DRX, In one or more cases, the condition or trigger may include deactivation of DRX, including entering a DRX active timer.

[0106] In one or more cases, the condition or trigger may include the current time of day or night. For example, the WTRU may transmit the wake-up assistance information at a subset of times that may be set by the network.

[0107] In one or more cases, the condition or trigger may include triggering a tracking area update or a RAN paging area update. For example, the condition or trigger is met when the WTRU determines that mobility to a cell does not have a WTRU context outside the serving RAN paging area. The WTRU may include the tracking area in the WTRU assistance information. In another embodiment, the condition or trigger is met when the WTRU determines expiration of a "keep-alive" timer. For example, the WTRU may start a keep-alive timer upon sending a first switch-on request or activation WTRU assistance information. The WTRU may send a second switch-on request or activation WTRU assistance information upon expiration of that timer. In some cases, the WTRU restarts the timer upon expiration of the timer for the second switch-on request or activation WTRU assistance information. In one or more cases, the duration of the keep alive timer and / or whether the WTRU retransmits the switch on request or retransmits the wake up WTRU assistance information may be predefined or may be explicitly signaled by the system information or in another RRC message, such as RRC connection release. In one or more cases, the duration of the timer may be a function of the periodicity of a signal broadcast by the cell, such as, but not limited to, an SSB. For example, the duration may be a predefined or configured multiple of the cell's SSB periodicity.

[0108] In one or more cases, the WTRU may be configured to transmit the wake-up WTRU assistance information or switch-on request. For example, the WTRU transmits the wake-up WTRU assistance information or switch-on request in a subset of RRC states (e.g., RRC inactive or RRC idle). In another embodiment, the WTRU may transmit the wake-up WTRU assistance information or switch-on request in a subset of availability states associated with the requested cell. For example, the WTRU may transmit the wake-up WTRU assistance information or switch-on request in a subset of availability states associated with the requested cell, such as whether the requested cell is configured in a low availability state, such as an "off," "deep sleep," or "microsleep" availability state. In another embodiment, the WTRU transmits the wake-up WTRU assistance information or switch-on request in a subset of availability states associated with cells for which uplink resources are used. In another embodiment, the WTRU transmits the wake-up WTRU assistance information or switch-on request in a subset of availability states associated with cells from which the WTRU receives a presence indication.

[0109] In one or more cases, the WTRU may perform measurements on the capacity boosting cell. In one or more cases, the WTRU may provide feedback and / or measurement results to an already-on macro cell / current serving cell. The WTRU may acquire SI, perform initial access, or perform cell search (e.g., for the requested cell). The WTRU may acquire SI, perform initial access, or perform cell search (e.g., for the requested cell) after sending the turn-on request or upon receiving a response from the gNB. In some cases, the requested cell includes a cell index indicated as part of the WTRU assistance information or switch-on request. When the WTRU is in an RRC idle or inactive state, the WTRU may monitor paging following transmission of the activation WTRU assistance information or switch-on request to receive an activation WTRU assistance information or gNB response. In some cases, the WTRU may monitor paging following transmission of the activation WTRU assistance information or switch-on request to receive a gNB response on a subset of paging occasions, P-RNTIs, or PDCCH resources.

[0110] In one or more cases, the WTRU may be configured to transmit the activation WTRU assistance information, for example, as part of one or more of an RRC message, a UL MAC CE report indicating cell / carrier / BWP information, a measurement report, a BSR MAC CE, SR, or a positioning report.

[0111] In one or more cases, the WTRU may include at least one of the following as part of the wake-up WTRU assistance information. For example, as part of the wake-up WTRU assistance information, the WTRU may include a cell index for which wake-up is requested, a change in availability state is requested or desired, or a presence indication is detected, or a combination thereof. In some cases, the wake-up WTRU assistance information may include one or more of a gNB ID, PCI, SN id, or carrier ID. In another embodiment, as part of the wake-up WTRU assistance information, the WTRU may include a TRP index for which wake-up is requested, a change in availability state is requested or desired, or a presence indication is detected, or a combination thereof. In another embodiment, as part of the wake-up WTRU assistance information, the WTRU may include an associated carrier or frequency band for which wake-up is requested, a change in availability state is requested or desired, or a presence indication is applicable, or a combination thereof. In another embodiment, as part of the wake-up WTRU assistance information, the WTRU may include a desired availability state associated with one or more of the indicated cell, carrier, TRP, or frequency band. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include an RRC message (e.g., a DCCH or CCCH message) that may include a WTRU identity. The RRC message may be, for example, a DCCH message, a CCCH message, etc. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include a MAC CE subheader or identifier. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include a request to activate / deactivate an antenna chain or increase the number of antenna chains. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include a request to activate / deactivate an SSB or increase the number of SSBs in the monitored set. For example, the request may be a request to receive an on-demand SSB.In another embodiment, as part of the activation WTRU assistance information, the WTRU may include a request to activate / deactivate a CSI-RS, a PRS, or associated resources. For example, the request may be a request to receive an on-demand CSI-RS. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include a request to activate / deactivate a transmission or reception point in a coordinated multipoint system. The coordinated multipoint system may include, for example, but is not limited to, one or a combination of a cell, a group of cells, or a group of TRPs. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include a request to activate / deactivate one or more of an antenna panel, a chain, a spatial multiplexing stream, and / or associated measurement resources. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include the WTRU's location, a positioning report, or a positioning related measurement. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include a radio link failure report or associated measurement. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include a beam failure report or related measurements, such as a beam failure MAC CE. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include a WTRU power consumption profile, metrics, or statistics, including one or more of an active DRX mode, power headroom, and MPE related measurements. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include a request for one or more of a wider BWP, a BWP change, an SUL activation, a BWP index to activate, a carrier index to activate, and related measurement resources. In another embodiment, as part of the activation WTRU assistance information, the WTRU may include a request to receive on-demand SSB and / or CSI-RS associated with one or more cells, TRPs, or spatial elements.In another embodiment, as part of the activation WTRU assistance information, the WTRU may include an indication of the WTRU's newly arrived data type (eg, RB type or index) and associated latency metric.

[0112] In one or more cases, the WTRU may monitor cell-specific DL resources when sending an activation WTRU assistance information or switch-on request to measure channel conditions and perform initial access, synchronization, and / or control and / or data reception. Such resources may be provided on different carriers or different BWPs. In such cases, the WTRU may activate such carriers or BWPs. For example, the WTRU may monitor a PSS / SSS or CSI-RS when sending a request for an on-demand SSB or on-demand RS.

[0113] In one or more cases, the WTRU may transmit the activation assistance information. For example, the WTRU transmits the activation WTRU assistance information in an available grant. In some cases, the WTRU transmits the activation WTRU assistance information in an available grant that is limited to transmitting on a different serving cell. The different serving cell may be, for example, but not limited to, a different cell or carrier than that requested or indicated in the WTRU assistance information or switch-on request. In some cases, the WTRU initiates a RACH / SR procedure based on the WTRU not having resources to transmit the assistance information. In some cases, the WTRU may trigger a new SR or BSR based on the WTRU not having a grant and / or at least one condition for transmitting the WTRU assistance information being met.

[0114] In one or more cases, the WTRU may perform a mobility, cell search, or synchronization procedure following transmission of the activation WTRU assistance information. For example, the WTRU may perform a mobility, cell search, or synchronization procedure following transmission of the activation WTRU assistance information on the requested cell. In another embodiment, the WTRU may perform a mobility, cell search, or synchronization procedure following transmission of the activation WTRU assistance information on the requested cell after receiving a response from the network in response to transmission of the WTRU assistance information. The response may be a HARQ ACK for the PUSCH transmission including the WTRU assistance information.

[0115] In one or more cases, the WTRU may perform a positioning procedure, PRS measurements, or transmit a pSRS upon triggering an activation WTRU assistance information.

[0116] In one or more cases, the WTRU may transmit another WTRU assistance information after a previous activate WTRU assistance information has been acknowledged. In one or more cases, the WTRU may transmit another WTRU assistance information after a timer has elapsed before receiving a response to the WTRU assistance information from the gNB.

[0117] In one or more cases, the WTRU may start an inhibit timer upon transmission of the activation WTRU assistance information. The WTRU may rely on an appropriate HARQ retransmission mechanism for retransmission based on the WTRU assistance information being transmitted as part of the uplink transport block. In one or more cases, the WTRU may retransmit the WTRU assistance information after expiration of the inhibit timer.

[0118] In one or more cases, the WTRU may retransmit the WTRU assistance information on one or more of a different serving cell, a different carrier, a different uplink (e.g., SUL), or a different TRP. For example, the WTRU may retransmit the WTRU assistance information on one or more of a different serving cell, a different carrier, a different uplink (e.g., SUL), or a different TRP after one or a combination of the WTRU performing a configured number of retransmission attempts, the WTRU not receiving a response from the network to the activate WTRU assistance information, and expiration of a prohibition timer.

[0119] In one or more cases, the WTRU may be configured with a maximum number of permitted wake-up WTRU assistance information transmissions. In some cases, the WTRU maintains a counter, and the WTRU increments the counter by, for example, but not limited to, one after transmitting the wake-up WTRU assistance information. In some cases, the WTRU may transmit multiple wake-up request signals. For example, the WTRU may transmit multiple wake-up request signals up to a configured value for the maximum number of permitted wake-up request transmissions. For example, the WTRU resets the counter upon receiving a response to the wake-up assistance information from the gNB. In some cases, the WTRU transitions to an RRC IDLE or inactive state after expiration of an inhibit timer. In some cases, the WTRU transitions to an RRC IDLE or inactive state after reaching a maximum number of retransmission attempts.

[0120] In one or more cases, the wake-up indication includes two configuration elements transmitted in succession by the WTRU. In some cases, the WTRU may transmit the two configuration elements in succession with a timing gap in between. In some cases, the first configuration element may be a signal and the second configuration element may be a channel. In one or more cases, the signal may be a sequence, such as, but not limited to, a random-access preamble. In other cases, the signal may be received using a relatively low power, such as, but not limited to, a signal using ON-OFF keying. In other cases, the signal may set a particular signature that may trigger a change in activity level (e.g., availability state) at the receiving node. For example, in some cases, the receiving node activates some RF / baseband configuration elements. Following the signal, the WTRU monitors a particular set of monitoring occasions to receive signaling for resource allocation. The WTRU transmits PUCCH and / or PUSCH in the assigned resources, which may include further wake-up assistance information.

[0121] In one or more cases, the WTRU may be configured to determine a network energy saving state of a cell. In one or more cases, the WTRU considers the active availability state associated with a cell, carrier, TRP, BWP, or frequency band to be in an "OFF", "Deep Sleep", or "Micro Sleep" state after receiving DL signaling that changes the availability state of the cell or TRP. For example, the WTRU may receive a turn-off command on broadcast signaling, RRC signaling, DCI (e.g., group-common DCI), or DL ​​MAC CE. The WTRU may determine the availability state from receiving an availability state indication from L1 / L2 signaling (e.g., group-common DCI or indication).

[0122] In one or more cases, the WTRU implicitly assumes a particular availability state (e.g., "off", "deep sleep", "microsleep", or "dormant") associated with a cell, carrier, TRP, BWP, or frequency band from at least one of the following: For example, the WTRU implicitly assumes a particular availability state associated with a cell, carrier, TRP, or frequency band based on receipt of an instruction or signal indicating a change in the availability state. The instruction or signal may be provided, for example, in a group-common DCI or RRC signaling in connected mode. The WTRU may implicitly determine the availability state from receipt of periodic DL signaling. The WTRU may configure or specify an availability state to be associated with one or more DL signal types. For example, the DL signal types may include SSB, partial SSB, and / or one or more periodicities. In another embodiment, the WTRU implicitly assumes an availability state associated with a cell, carrier, TRP, or frequency band based on a gNB DTX state. That is, the WTRU implicitly assumes a particular availability state associated with a cell, carrier, TRP, or frequency band based on whether the gNB is in active time or an associated activity timer is running. In another embodiment, the WTRU implicitly assumes a particular availability state associated with a cell, carrier, TRP, or frequency band based on receiving a paging message, a paging DCI, a paging PDSCH, or a paging related signal. The paging related signal may be, for example, a Paging Early Indication (PEI). The paging related signal may be provided on a subset of POs. The subset of POs may be, for example, aligned with the NES DRX cycle or a configured subset of PDCCH resources. The WTRU may assume a particular availability state after receiving a paging message with a particular P-RNTI, a separately configured NES P-RNTI, or a NES group RNTI. The WTRU may assume a particular availability state after receiving a paging message with a particular P-RNTI.The WTRU may configure one or more PEI subgroups for the NES. In one or more cases, the PEI subgroups may be associated with one or more availability states. The WTRU may assume an availability state after receiving a PEI with an NES subgroup. For example, the WTRU assumes an availability state after receiving a PEI with an NES subgroup based on the subgroup being configured and / or associated with an availability state. An indication of the availability state or availability state switch may be indicated in the paging payload. For example, an indication of the availability state or availability state switch may be indicated in the paging payload as a flag part of a paging message or short message. Such a paging indication may further indicate an alternative cell to monitor for paging while the cell where the signaling is received is in an off, sleep, or NES state. Such a paging indication may further indicate or signal applicable reconfiguration parameters. The reconfiguration parameters may correspond to, for example, but are not limited to, one or more of the following: initial access, applicable PRACH resources, applicable SSB / RS occasions, applicable SI cycles, and applicable cell and associated availability states.

[0123] The WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on the lack of detection of a presence indication. For example, the WTRU may determine an availability state associated with a cell (e.g., an “off” or “deep sleep” state) if a presence indication is not detected for one or more presence indication occasions. In another case, the WTRU may assume or change the availability state of a cell after several consecutive false detections or after a timer expires following the absence of detection of a presence signal. The WTRU may determine that an availability state is active or inactive after expiration of a timer associated with the availability state. In another case, the WTRU may implicitly determine an availability state from the lack of reception of periodic DL signaling. For example, the WTRU may be configured with a signal quality threshold (e.g., an RSRP threshold). If the WTRU does not detect a signal associated with an availability state (e.g., a presence signal or SSB) having a signal strength above the threshold, the WTRU may assume that the availability state is not active or may assume a different availability state. This criterion may also be combined with the lack of detection of an identifying sequence of the presence signal (eg, detection of a PSS sequence).

[0124] The WTRU implicitly assumes a particular availability state associated with a cell, carrier, TRP, or frequency band based on the time of day. For example, the WTRU may be configured to automatically assume a certain availability state (e.g., off, sleep, or hibernate) for a configured subset of cells (e.g., capacity boosting cells) depending on the time of day. For example, the WTRU may determine that a capacity boosting cell has an availability state indicated as "on" during a certain time of day, has an availability state indicated as "deep sleep" during other configured times, and has an availability state indicated as "off" during a third set of configured times during the day or night. For example, the WTRU implicitly assumes a particular availability state associated with a cell, carrier, TRP, or frequency band based on the availability state of an associated cell. The associated cell may be, for example, another carrier of the same MAC entity, another carrier in the same cell group, another carrier in the same gNB, another sector in the same gNB, or a configured associated cell or capacity boosting cell. In another embodiment, the WTRU implicitly assumes an availability state associated with a cell, carrier, TRP, or frequency band based on detection of a PSS signal or a simplified / stripped-down SSB signal. In another embodiment, the WTRU implicitly assumes an availability state associated with a cell, carrier, TRP, or frequency band based on detection of a PSS-only signal. In another embodiment, the WTRU implicitly assumes a particular availability state associated with a cell, carrier, TRP, or frequency band based on detection or lack thereof of an RS signal (e.g., CSI-RS, PRS, TRS). In another embodiment, the WTRU implicitly assumes an availability state associated with a cell, carrier, TRP, or frequency band based on the WTRU's RRC state. The WTRU's RRC state may be, for example, an idle state, an inactive state, or a connected mode.In another embodiment, the WTRU implicitly assumes a particular availability state associated with a cell, carrier, TRP, or frequency band based on, for example, but not limited to, whether a paging is received within a configured time window. In another embodiment, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on, for example, but not limited to, whether system information (e.g., a subset of periodic SIs or SIBs) is received within a configured time window.

[0125] In one or more cases, the WTRU may stop measurements (e.g., SSB and / or CSI-RS) when it determines that the cell is configured in an "off" or "deep sleep" state. In other cases, the WTRU may stop measurements when the WTRU determines that there is a clear configured measurement gap. The WTRU may assume that some configured UL and DL resources, including configured downlink assignments, configured uplink grants, PUSCH resources for semi-persistent CSI reporting, and / or measurement gaps, are cleared or are not available in certain availability states (e.g., "off", "dormant", or "deep sleep" states). In some cases, the WTRU may autonomously disable CSI reporting in certain availability states (e.g., "off", "dormant", or "deep sleep" states). For example, the WTRU may autonomously disable CSI reporting during non-availability periods in some availability states. In one or more cases, the WTRU decides to use a coverage extension method and / or resources (e.g., msg3 repetition, PUSCH repetition, default start of RA with selected extended PUCCH coverage resources) depending on the cell availability state and / or channel measurements (e.g., RSRP is below a threshold).

[0126] In one or more cases, the WTRU may be configured to determine applicable transmission, reception, and / or measurement resources for each availability state. The WTRU may determine that uplink or downlink resources or signals are available for transmission / reception and / or measurement for the determined network availability state based on which are applicable in the active availability state. The WTRU may determine that a subset of measurement resource and / or signal (e.g., SSB, CSI-RS, TRS, PRS) occasions are not applicable in some availability states. Thus, the WTRU may not measure reference signals in such measurement occasions during non-availability periods. For example, the WTRU may be configured such that a first set of RS or RS configurations (e.g., CSI-RS) are monitored during non-availability periods of the availability state. Additionally or alternatively, the WTRU may be configured such that a second set of RS or RS configurations (e.g., CSI-RS) are not monitored during non-availability periods of the availability state. The WTRU may determine that a subset of uplink or downlink resources (e.g., PRACH, PUSCH, PUCCH) is not applicable in some availability states. The WTRU may transmit some uplink signals (e.g., SRS, pSRS, PRACH, UCI) in the subset of NW availability states.

[0127] In one or more cases, if the WTRU determines that the network did not transmit applicable signals in one or more measurement occasions for RLM measurements for a given RLM process, e.g., due to NES (e.g., during an unavailability period of an availability state), the WTRU may decide to refrain from using measurements corresponding to those skipped reference signal occasions for purposes of determining Qin / Qout and in-sync / out-of-sync. The WTRU may not measure measurement resources and / or occasions for RLM during an unavailability period of some availability states. In some cases, the WTRU may not modify or increment associated RLM counters and timers, for example, based on the skipped measurements. In some cases, the WTRU may not modify or increment measurements / quantities during skipped measurement occasions (e.g., during an unavailability period of an availability state), including RLM, BFD, and CSI measurements. The WTRU may be configured with an alternative set of values ​​for the RLM timers and / or counters (e.g., RLM-Periodic-Timer, RLM-Occurrence-Counter, RLM-Trigger-Quantity-Counter, RLM-Trigger-Time-Counter). In some cases, the WTRU may apply the alternative set of values ​​for the RLM timers and / or counters when certain availability states are active.

[0128] In one or more cases, if the WTRU determines that the network did not transmit applicable reference signals for some occasions for the BFD process (e.g., during a non-availability period of an availability state), e.g., due to an NES, the WTRU may decide to refrain from measuring measurement resources and / or occasions for BFI determination when applicable CSI-RS signals are not transmitted. The WTRU may not modify or increment relevant BFD counters and timers, e.g., based on the skipped measurement occasions. If the BFI counter exceeds a configured threshold for triggering beam failure, the WTRU may wait or delay the triggering of a BFR until a CSI-RS occasion occurs that is associated with a NW activity state (i.e., availability state) that is associated with an NES (e.g., sleep, or dormant). In one or more cases, the WTRU may cancel a triggered BFR upon reception of a CSI-RS with a quality metric above a configured threshold. For example, the WTRU cancels a triggered BFR upon reception of a CSI-RS with a quality metric above a configured threshold, such as Qin / RSRP>threshold. In one or more other cases, the WTRU may cancel a triggered BFR upon reception of a CSI-RS with a quality metric above a configured threshold (e.g., Qin / RSRP>threshold) when the CSI-RS occasion is associated with an availability state (e.g., NES mode or on). The WTRU may be configured with an alternative set of values ​​for BFD timers and / or counters (e.g., BFD counters, BFD timers, etc.). In some cases, the WTRU may apply an alternative set of values ​​for BFD timers and / or counters when an availability state is active.

[0129] In one or more cases, the NW may indicate that a subset of past measurements or measurement occasions are not valid when the WTRU wakes up. The WTRU may then retroactively correct the RLM or BFD accumulated metric. The RLM or BFD accumulated metric may be, for example, the number of BFIs, the number of out-of-sync, etc. In one or more cases, the WTRU may decide to remove one or more past measurements based on the WTRU receiving a NW signal (e.g., SSB, RS, or CSI-RS) being measured that has a significant signal strength difference. The WTRU may consider the measurement if it recognizes the sequence embedded in the SSB or CSI-RS, otherwise it may skip the measurement occasion and consider it not to be transmitted due to the NES. For example, the WTRU may skip the measurement occasion by not performing channel measurements on the SSB or CSI-RS occasion.

[0130] In one or more cases, the WTRU may mute (e.g., not use, deactivate, etc.) some uplink and / or downlink resources for data and / or control information exchange that do not overlap or are not within the time period of a configured SSB or RS occasion of an active SSB / RS pattern or the availability period of an availability state. The WTRU may assume multiple muting patterns / resource periodicities based on the active SSB periodicity from the active availability state from the configured pattern / periodicity.

[0131] In one or more cases, the WTRU may be configured or predefined to determine that in some cell availability states (e.g., "off", "dormant", or "deep sleep" states), at least one of the following is applicable: For example, the WTRU determines that configured SSBs and / or CSI-RS are not transmitted by the gNB for this serving cell. In another embodiment, the WTRU determines that a presence indication is transmitted by a cell in such availability state. In another embodiment, the WTRU determines that SI and PBCH signaling may not be transmitted by a cell in such availability state. For example, the WTRU may transmit a subset of SI or SIB.

[0132] In one or more cases, the WTRU is configured to determine that in a subset of the availability states (e.g., a microsleep state), reference symbols, synchronization signals, and / or system information are transmitted from the cell. In one or more other cases, the WTRU is configured to determine that in another availability state (e.g., a deep sleep state, a hibernate state, or an off state), reference signals, synchronization signals, and / or system information are not transmitted from the cell.

[0133] In one or more cases, the WTRU may avoid performing procedures related to SI acquisition, reacquisition, PBCH reception, cell search, mobility, and / or SSB reception from cells in availability states including "off", "dormant", or "deep sleep". A WTRU in RRC_IDLE or RRC_INACTIVE may stop monitoring SI change indications in the WTRU's paging occasions in DRX cycles that correspond to the cell's availability state being in the "off", "dormant", or "deep sleep" states. The WTRU may extend the modification period associated with the SI change indication while the cell is in a particular availability state (e.g., off, dormant, or deep sleep state). In some cases, the WTRU may not perform RLM or RLF procedures for such cells in such availability states (e.g., "off", "dormant", or "deep sleep"). In some cases, the WTRU may suspend beam failure detection on some cells in some availability states (e.g., "off", "dormant", or "deep sleep" states).

[0134] In one or more cases, the WTRU may be configured for SSB / RS adaptation. In one or more cases, for cases where the WTRU is configured in idle or inactive mode, the WTRU may attempt to decode a simplified SSB (e.g., PSS only) when the network is configured in a NES state or a given availability state. The WTRU may determine modified timing of the remaining synchronization signals or SSB occasions. The WTRU may detect the remaining synchronization signals or SSB occasions based on properties of the PSS. The properties of the PSS may be, for example, but not limited to, the PSS sequence or timing of the PSS. In one or more cases, the PSS may have the same periodicity as legacy (i.e., the periodicity broadcast in system information block (SIB) signaling), but may vary the periodicity of the SSS and PBCH. In one or more cases, the PSS may refer to an alternative SSB periodicity.

[0135] The WTRU may be configured with multiple values ​​of the field ssb-periodicityServingCell. The value may be configured using RMSI, secondary SIB, in broadcast signaling, etc. For a WTRU in connected mode, L1 signaling (e.g., group-common DCI) or L2 signaling (e.g., MAC CE) may indicate one or more of switching between configured SSB periodicities, switching to a different availability state, and / or activating or deactivating a particular availability state. Upon receiving such an instruction, the WTRU may assume different periodicities of the SSB and associated RACH resources. For example, the WTRU may assume different periodicities of the SSB and associated RACH resources based on receiving an instruction, such as, but not limited to, an SSB periodicity change instruction or an instruction associated with changing an availability state.

[0136] In one or more cases, for cases where the WTRU is configured in idle mode, the WTRU may determine the SSB or RS periodicity and / or whether an SSB or RS occasion is missing (i.e., whether an SSB or RS occasion is transmitted from the gNB) based on past measurements. For example, the WTRU may determine that an SSB or RS is not transmitted based on a current measurement of a measurement net occasion that differs from a past measurement (or a running average of past measurements) of X having a difference greater than a predetermined or configured value. X may be predefined or preconfigured. The WTRU may read, acquire, or reacquire system information based on a change between the current measurement and the past measurement being greater than a threshold value.

[0137] In one or more cases, for the case where the WTRU is configured in connected mode, the WTRU may be configured with one or more RS periodicities / patterns (e.g., for CSI-RS, PRS, TRS, etc.). In one or more cases, the WTRU may determine the periodicity of the active RS pattern from one or more of the following: a) a difference or comparison between the current RS measurement occasion and a number of past measurement occasions, b) the overall signal quality of the cell (e.g., based on measurements of L3 RSRP or presence signals), c) an active availability state, and d) the mobility state of the WTRU. The WTRU may ignore measurements of RS occasions that are not transmitted in the active RS pattern (e.g., during non-availability periods of an availability state). The WTRU may send an activation request or assistance information to request a change in the RS periodicity / pattern. The gNB may signal the change in the RS or SSB pattern / periodicity in an indication (e.g., MAC CE, DCI, etc.).

[0138] In one or more cases, the WTRU may use a RACH occasion associated with an active periodicity of the SSB and / or a CSI-RS pattern. For example, the WTRU may use a RACH occasion associated with an active periodicity of the SSB and / or a CSI-RS pattern, such as a PRACH occasion that aligns with a transmitted SSB, immediately follows a transmitted SSB, or is transmitted within a time window from SSB reception. The WTRU may assume that the remaining PRACH occasions are not available. The WTRU may be configured with a PRACH occasion mask associated with one or more SSB patterns or CSI-RS patterns. The WTRU may activate the PRACH occasion mask according to the active SSB or RS pattern. For example, the WTRU may activate the PRACH occasion mask based on receiving a switch command to use a given RS or SSB periodicity or pattern. In one or more cases, the WTRU may assume that only ROs that overlap with a transmitted SSB occasion (or are within a period from the last transmitted SSB) are valid. In one or more cases, the WTRU may not send msg1 on an invalid RO.

[0139] In one or more cases, the WTRU monitors paging from a cell. For example, the WTRU may be configured to monitor paging from a cell when the cell is in one availability state (e.g., on or sleep). The WTRU may skip waking up in a DRX cycle for that cell that coincides with when the cell is in any other availability state (e.g., off, deep sleep, or dormant). In some cases, the WTRU may monitor gNB wake-up signaling associated with DRX or paging (e.g., DCP) in a subset of the cell's availability states (e.g., on or sleep).

[0140] In one or more cases, the WTRU may be configured to transmit a Tracking Area Update (TAU) on a subset of cells that are in some availability state. For example, the WTRU transmits a TAU on a subset of cells, e.g., macro cells, depending on the availability state. In some cases, the WTRU may avoid transmitting a TAU on capacity boosting cells and / or cells that have a determined availability state set, e.g., in an off state, a dormant state, or a sleep state.

[0141] In one or more cases, the WTRU may be configured to perform cell reselection and / or mobility procedures. For example, the WTRU performs cell reselection and / or mobility procedures after receiving a turn-off indication or a sleep transition signal. In some cases, the WTRU may receive the turn-off indication or the sleep transition signal in a subset of the RRC states. In one or more cases, the WTRU may perform mobility procedures in connected mode following receipt of an off indication. The WTRU may perform cell reselection, initial access, and / or RRC re-establishment based on the WTRU being configured in an inactive or idle mode. If the WTRU is configured in a connected or inactive state, the WTRU transitions to idle mode following receipt of a turn-off indication.

[0142] The WTRU may be configured or predefined with an alternative serving cell to perform initial access, mobility, or cell reselection when the current serving cell or capacity boosting cell is turned off or certain conditions are met. The WTRU may be configured per broadcast or dedicated signaling with a list of fallback or alternative serving cells. In one embodiment, the WTRU may be configured per serving cell or per gNB per broadcast or dedicated signaling with a list of fallback or alternative serving cells. For example, the WTRU initiates a cell reselection or mobility procedure to an alternative serving cell associated with the cell or gNB from which the turn-off indication was received. In one embodiment, the turn-off indication or sleep state transition indication may dynamically indicate to the WTRU which cell to fall back to or connect to, for example, by dedicated or broadcast signaling. In another embodiment, the fallback cell may be predefined as a master node cell based on the WTRU being configured with dual connectivity. The fallback / alternate cell may be configured or predefined to be a cell associated with a different RAT or frequency band. For example, the WTRU may fall back to an LTE cell or an FR1 cell associated with the cell or gNB where the turn-off instruction was received. For example, the WTRU may fall back to an LTE or FR1 cell associated with the cell or gNB where the turn-off instruction was received based on whether the WTRU is in CA or DC using multiple RATs or multiple frequency bands.

[0143] In one or more cases, the WTRU may perform initial access / RA, mobility, and / or initiate associated measurements on an alternate cell or a capacity boosting cell based on one or more of the following conditions being met: (a) the latency associated with the new data arrival, BSR, or buffered data is strict (e.g., lower or higher than a threshold); (b) the data associated with the new data arrival, BSR, or buffered data includes data from one or more “NES” RBs or LCHs (based on RB id), including the condition that all data is from a configured NES DRB / SRB; (c) the buffered data or NES (d) the amount of buffered data from the RB is higher or lower than a configured threshold; (e) one or more conditional handover conditions are satisfied; (e) the WTRU is configured in an RRC state (e.g., idle, inactive, or connected); (f) measured channel conditions associated with an alternative cell and / or best serving cell; and (g) indicated or measured cell resource load (utilization) metrics associated with the alternative cell and / or best serving cell.

[0144] In one or more cases, the WTRU may stop using initial access, measurement procedures / resources (e.g., the indicated or measured cell resource load metric is associated with the best serving cell) on the previous serving cell if one or more of the above triggers are met and / or the WTRU initiates an initial access procedure on an alternative cell. In one or more cases, the WTRU may be configured with a subset of DRBs and / or SRBs as NES RBs (or LCHs) that the WTRU may use in the NES state. In one or more cases, the WTRU may send a wake-up request, a switch-on request, or WTRU assistance information based on the WTRU having buffered data from such RBs or new data arriving from such RBs.

[0145] In one or more cases, the WTRU may be configured to correlate the availability of one cell from the availability state of another cell. The WTRU may be predefined or configured with the cell associations. The cell associations may be, for example, but not limited to, cells belonging to the same gNB, cells of the same cell group, cells in a CA, cells of the same frequency band, cells of the same RAT, etc. The WTRU may change the availability state of one cell based on the WTRU changing the state of another associated cell. For example, if the WTRU determines that one cell is turned off, in a dormant state, or in a sleep / power saving state, the WTRU changes the availability states associated with all of the cells associated with the cell that is turned off, in a dormant state, or in a sleep / power saving state. The WTRU may simultaneously activate, deactivate, and / or change the availability states for a group of cells when an associated gNB changes its availability state.

[0146] In one or more cases, the WTRU may be configured to determine which sectors, TRPs, and / or antennas of a gNB are available or activated depending on an availability state associated with the gNB. For example, the WTRU may determine that the gNB operates with a single sector in a power-saving availability state (e.g., sleep, hibernate, or off state). When the gNB is in another availability state (e.g., on or micro-sleep state), the WTRU may determine that the gNB operates with a different number of active cells / PCIs, or several cells that are part of the same gNB.

[0147] In one or more cases, the WTRU may be configured to monitor indications that may characterize a level of network activity (e.g., availability state). In one embodiment, the network activity may be associated with a gNB and / or a cell. The WTRU may assume the same availability state for all cells that are part of the same gNB, e.g., cells of the same MAC entity. The network activity indication (e.g., presence indication) may include a channel (e.g., PDCCH) and / or a signal (e.g., a sequence). The activity indication may indicate a level of activity (e.g., reduced activity) that the WTRU may expect from the gNB and / or cell with which it is associated. In some cases, the activity indication may include activity information of other gNBs / cells.

[0148] In one or more cases, the activity indication may be a PDCCH that includes group-common signaling. For example, the NW may transmit a group-common DCI to a group of WTRUs (e.g., WTRUs in a serving cell) indicating a change in activity state or activity level in the UL and / or DL. The group of WTRUs may be, for example, WTRUs in a serving cell. The CRC of the PDCCH may be scrambled with a dedicated "activity indication RNTI." The WTRUs may be configured with at least one search space associated with a monitoring occasion of the activity indication PDCCH.

[0149] In one or more cases, the signaling or activity indication in the PDCCH may include one or more of the following. For example, the signaling or activity indication in the PDCCH may include an expected activity level of the associated gNB / cell over a particular time interval (e.g., a time interval for an availability state). In some cases, the WTRU may configure and / or pre-determine the activity level, which may include, for example, normal activity and reduced activity. In some cases, the signaling may indicate an activity level. For example, a "1" bit may indicate normal activity. In another example, a "0" bit may indicate reduced activity.

[0150] In another embodiment, the signaling or activity indication in the PDCCH may include defined transmission and reception attributes for each activity level (e.g., availability state). For example, during reduced activity, the WTRU may not be expected to monitor a particular PDCCH search space (e.g., including one, multiple, or all SSs), receive a particular type of PDSCH (e.g., including one, multiple, or all PDSCHs), transmit PUCCH / PUSCH, and / or perform certain measurements. In one or more cases, the WTRU may determine a scheduling cell (e.g., for cross-carrier scheduling) depending on the availability state associated with the activated carrier. For example, the WTRU may stop monitoring a PDCCH for cross-carrier scheduling based on the availability state that has been changed or activated on such carrier, and in another embodiment, the WTRU may stop monitoring a PDCCH for cross-carrier scheduling based on the availability state that has been changed or activated on such carrier while the WTRU is monitoring a PDCCH from another carrier (e.g., in or not in NES state).

[0151] In another embodiment, the signaling or activity indication in the PDCCH may include a set of settings associated with an activity level and that may be used / applied when that activity level is indicated. For example, the set of settings may include SS settings, CSI reporting settings, an index of transmitted SSBs, etc. In one or more cases, each set of settings may have an attribute associated with the activity level. For example, an attribute such as a tag may be set to "reduced activity."

[0152] In another embodiment, the signaling in the PDCCH or the activity indication may include the time interval during which the activity level is assumed. In such a case, the WTRU may signal in the PDCCH or as part of the activity indication the time interval during which the activity level is assumed. In some cases, the time interval may be indicated using a bitmap where each bit in the bitmap may be associated with a particular duration, e.g., slot or frame. For example, a bit "1" may indicate normal activity. In another embodiment, a bit "0" may indicate reduced activity on the associated frame. In some other cases, the time interval may be indicated with a start time and a length of the interval. The start time may be defined. For example, the start time may be determined by adding a fixed offset to the time the indication is received. The length of the interval may be configured or signaled in the indication PDCCH.

[0153] In another embodiment, the signaling or activity indication in the PDCCH may include a predetermined time interval during which the activity level is assumed.

[0154] In one or more cases, the indication may include a sleep transition signal, e.g., a predefined sequence. For example, if the WTRU detects a go-to-sleep signal, the WTRU may expect a reduced activity level for a particular duration. In one or more cases, the WTRU may activate C-DRX for the indicated period of time. Alternatively, in another embodiment, two sequences may be used to indicate normal activity and reduced activity.

[0155] In one or more cases, the WTRU may be configured to transmit a "leave indication" signal prior to or during cell reselection to a new cell. The "leave indication" signal may have the same structure as a "switch-on request" signal. The "switch-on request" signal and the "leave indication" signal may be generated using a first parameter and a second parameter, respectively. The first parameter and the second parameter may be related by a predefined relationship or higher layer signaling. For example, the WTRU may receive RRC signaling (e.g., system information or RRC connection release) indicating whether to transmit a "leave indication" signal prior to or upon cell reselection, and a setting of parameters for generation of the signal. The generation parameters may include, for example, a scrambling identity or a base sequence based on the structure of the signal.

[0156] In one or more cases, the parameter settings for the "leave indication" signal may depend on the identity of the serving cell prior to cell reselection. In one or more other cases, the parameter settings for the "leave indication" signal may depend on the identity of the serving cell after cell reselection. In the latter case, the "leave indication" signal may correspond to a "new cell indication" signal.

[0157] In some cases, the "switch-on request", "leave indication", or "new cell indication" signal may include a PRACH transmission. In such a case, the WTRU is configured to perform a RACH procedure to indicate the switch-on request (e.g., the RACH preamble may include the switch-on signal). The RACH procedure may be considered successful based on the WTRU receiving a random access response corresponding to the PRACH.

[0158] In other cases, the WTRU may be configured to initiate an RRC connection request to a new cell after reselection, possibly with a new cause indication. The RRC connection request may be signaled by RRC (e.g., system information or RRC connection release). RRC may be indicated separately for each source serving cell (e.g., before cell reselection). RRC may be indicated separately for each target serving cell (e.g., after cell reselection). RRC may be indicated separately for each source and target serving cell pair (e.g., for cell reselection from a particular source cell to a particular target cell). In one or more cases, transmission of a "Leave indication" or "New cell indication" signal by a WTRU in idle mode may determine when a cell may be turned off. For example, transmission of a "Leave indication" or "New cell indication" signal by a WTRU in idle mode may determine that a cell may be turned off when there are no or few WTRUs camped on the cell.

[0159] In one or more cases, the WTRU may be configured to operate in the frequency domain and the spatial domain. For example, the WTRU may turn off the NUL and rely on the SUL. The WTRU may turn off the NUL and rely on the SUL, for example, based on the associated cell being turned off or configured in a power saving state.

[0160] In one or more cases, the WTRU may be configured, predefined, or indicated to turn off the NUL uplink carrier. In one or more cases, the WTRU may be configured, predefined, or indicated to depend on the SUL in one or more availability states. For example, the WTRU may deactivate the NUL carrier and / or the UL carrier.

[0161] In some cases, the WTRU may be configured, predefined, or indicated to deactivate one or more uplink carriers, such as, but not limited to, a secondary SCell. In some cases, the WTRU may be configured, predefined, or indicated to depend on the PCell based on an associated serving gNB being configured in one or more availability states. For example, the WTRU deactivates an SCell when the gNB is in a certain availability state. For example, the WTRU deactivates an SCell when the associated cell is turned off or set to a power saving state when the gNB is in a certain availability state.

[0162] In some cases, the WTRU may be configured, predefined, or indicated to switch the WTRU's active UL and / or DL ​​bandwidth portions to an initial or default BWP. For example, the WTRU switches the WTRU's active UL and / or DL ​​bandwidth portions to an initial or default BWP when the associated serving cell is configured in one or more availability states. For example, the WTRU deactivates the SCell when the gNB is in an availability state. For example, the WTRU deactivates the SCell when the associated cell is turned off or configured in a power saving state. In one or more cases, the WTRU may be configured with a specific NW power saving BWP. In some cases, the WTRU may be configured with a specific NW power saving BWP (e.g., NES BWP). In some cases, the WTRU may be configured with a specific NW power saving BWP (e.g., NES BWP) for each availability state. In some cases, the WTRU may switch to the NW power-saving BWP based on the associated cell being (or being determined to be) in an availability state (e.g., "off", "sleep", and other similar states). In some cases, the WTRU may be configured to switch its active UL and / or DL ​​active BWP to the NW power-saving BWP. For example, the WTRU switches its active UL and / or DL ​​active BWP to the NW power-saving BWP if the WTRU does not receive an availability signal in the current BWP. In some cases, the WTRU switches its active UL and / or DL ​​active BWP to the NW power-saving BWP if the WTRU does not receive an availability signal in the current BWP after some false detections. In some cases, the WTRU switches its active UL and / or DL ​​active BWP to the NW power-saving BWP if the WTRU does not receive an availability signal in the current BWP after expiration of a timer. For example, the WTRU may receive an indication (eg, common L1 signaling or L2 signaling such as DCI or MAC CE) indicating a switch to the NES BWP based on reception of a common cell signal, or lack thereof.The WTRU may transmit HARQ feedback or an acknowledgment for receiving the NES BWP switching command / indication. The WTRU may switch to the NES BWP after transmitting such feedback and / or upon receiving a second confirmed DL signal on the existing active BWP. In another embodiment, the WTRU may implicitly switch to another BWP (e.g., NES BWP) if no DL signal is detected. In another embodiment, the WTRU may implicitly switch to another BWP (e.g., NES BWP) if no DL signal is detected within a period of time and / or based on measured channel conditions. In another embodiment, the WTRU may implicitly switch to another BWP (e.g., NES BWP) if the DL signal does not include measured channel conditions above a threshold. In another embodiment, the WTRU may implicitly switch to another BWP (e.g., NES BWP) if no DL signal is detected (e.g., DL signal does not include measured channel conditions above a threshold) within a period of time and / or based on measured channel conditions. The WTRU may switch to the NES BWP upon expiration of the BWP inactivity timer or another NES BWP inactivity timer, which may be reset upon reception of a DL signal associated with a gNB availability / NES state.

[0163] In one or more cases, a presence indication associated with a cell may indicate which carrier to activate. In some cases, the WTRU may initiate measuring resources (e.g., CSI resources or channel quality) upon receiving a presence indication associated with a carrier. The WTRU may activate an SCell or associated gNB upon receiving a presence indication associated with the SCell. The WTRU may deactivate a carrier or SCell if it does not receive a presence indication associated with the SCell or associated gNB. In some cases, the WTRU may deactivate a carrier or SCell if a presence indication associated with the SCell or associated gNB is not received following several failures to receive a detected presence indication or after expiration of a timer (e.g., an SCell deactivation timer).

[0164] In one or more cases, the WTRU may be configured to receive signaling from the network to deactivate a cell, carrier, and / or BWP on a frequency band or carrier. For example, the WTRU may turn off or deactivate a cell on the FR2 frequency band. In some embodiments, the WTRU may turn off or deactivate a cell on the FR2 frequency band if it receives an off instruction to turn off or deactivate a cell on the FR2 frequency band. In some embodiments, the WTRU may turn off or deactivate a cell on the FR2 frequency band if the WTRU does not detect a presence indication associated with such frequency band. In other embodiments, the WTRU may turn off or deactivate a cell on a carrier or frequency band if the WTRU determines that the cell is in an availability state (e.g., off or dormant).

[0165] In one or more cases, the WTRU may be configured to provide assistance information requesting changes / modifications to gNB availability status and / or spatial resource allocation. Spatial resources may include, but are not limited to, for example, TRPs, antennas, ports, sectors, etc. In one or more cases, the WTRU may request additional and / or different sets of antennas, ports, beams, etc. based on certain measurements (e.g., SSB, PRS, CSI-RS). For example, if SSB measurements (e.g., SS-RSRP, SS-RSRPB, SS-RSRQ, SS-SINR, etc.) fall below a certain threshold, the WTRU indicates a need for additional SSB beams from the gNB. SSB measurements below a certain threshold may indicate poor path loss / channel quality. In some cases, the additional SSB beam may be a narrower beam within the same wide SSB beam. In other cases, the additional beam may be a narrower beam within a new SSB beam. The new SSB beam may be, for example, a wide beam and / or a narrow beam.

[0166] In some cases, the gNB may use periodic or aperiodic CSI reporting from the WTRU to help select the set of beams to activate. In some cases, the gNB may use periodic or aperiodic CSI reporting from the WTRU to help select which beams the gNB can turn off. In some cases, the gNB may turn off beams that are not useful from a WTRU coverage perspective.

[0167] In one or more cases, the gNB may utilize WTRU-specific SRS transmissions to estimate UL channel quality. The gNB may use WTRU-specific SRS transmissions when determining whether the gNB may need to change its availability state and / or spatial domain resource allocation. For example, the gNB may utilize WTRU-specific SRS transmissions to switch / modify the gNB's current TRP antenna / beam / port configuration when the WTRU or a set of WTRU SRS transmissions indicate insufficient channel quality over a portion of frequencies, the entire frequency, and / or antenna port / beam assignment. In one or more cases, the WTRU may transmit SRS transmissions in a subset of availability states. In one or more other cases, the WTRU may transmit SRS transmissions using different periodicities or configurations depending on the availability state of the serving cell.

[0168] In one or more cases, the WTRU may indicate a need for additional number of antennas, ports, beams, etc., when CSI-RS related measurements (e.g., RSRP, RSRQ, SINR, etc.) are below a certain threshold. When the CSI-RS related measurements are below a certain threshold, the TRP configuration at the gNB may be suboptimal. In another embodiment, the WTRU may indicate a preference for a particular set of spatial resources, such as, but not limited to, ports, beams, and TRPs (i.e., when multiple TRPs are associated with this WTRU), based on measurements associated with these resources. Each set of spatial resources may be abstracted by an index configured by RRC signaling. The WTRU may report such preferred index as part of the UCI or MAC CE. In one embodiment, if measurements on a certain "bset" "k" of resources are above a threshold (i.e., "k" is the strongest resource "o" of "n" resources), the WTRU may indicate a preference for this subset of resources. In one or more cases, the gNB may utilize the indicated preference to modify the gNB availability state. For example, the gNB may utilize the indicated preferences to modify the gNB availability state by turning off spatial resources that are below a threshold.

[0169] In one or more cases, the WTRU may indicate the need for a change in gNB availability state and / or a change in spatial resource allocation when reference signal measurements (e.g., RSRP, RSRQ, etc.) are above one threshold but below another threshold. For example, if the serving cell is above a threshold (e.g., an Event A1 threshold that does not trigger mobility procedures) but below another threshold that is greater than the Event A1 threshold, the WTRU may determine the cell availability state (e.g., beam, antenna / port, etc.) based on the serving cell being above the Event A1 threshold but below another threshold in conjunction with information on the network availability state and / or cell / TRP presence indication information by the WTRU. In one or more cases, the WTRU may signal an indication to the gNB to request a change in additional spatial resources.

[0170] In one or more cases, the WTRU may request additional or changed spatial resource allocation based on the quality of the WTRU's CSI reporting. In some cases, this indication may be triggered based on insufficient CQI and / or rank measurements.

[0171] In one or more cases, the WTRU may utilize positioning-based measurements to request a change in the gNB's availability state and / or spatial resource allocation. In one embodiment, the WTRU may request a change if the DL PRS-RSRP or TRP per beam falls below a certain threshold. In another embodiment, the WTRU may request to switch the current spatial resource allocation if the DL RSTD of the PRS between the other TRP and the current serving (reference) TRP exceeds a threshold. In another embodiment, the WTRU may utilize rx-tx measurements from multiple TRPs (e.g., the serving TRP and additional TRPs) to trigger a request for additional spatial resources. The WTRU may use the rx-tx measurements in conjunction with information on the network availability state and / or cell / TRP presence indication information. The WTRU may use the rx-tx measurements in conjunction with information on the network availability state and / or cell / TRP presence indication information when indicating a preference for a change in the cell's availability state and / or the current spatial resource allocation (e.g., beams, antennas / ports, and other similar resources).

[0172] In one or more cases, the WTRU may request a change in the gNB spatial resource allocation when there is a change in the status of buffered data at the WTRU. In some cases, this change in the gNB spatial resource allocation may be an increase in buffered data. For example, an increase in buffered data may indicate an insufficient wasting rate of the buffered data. In some cases, this change in the gNB spatial resource allocation may correspond to a change in the characteristics of the buffered data. For example, the change in the characteristics of the buffered data may be a change in the priority level / QoS of the traffic being served, the amount of data, the number of LCGs active, etc.

[0173] In one or more cases, the gNB may utilize the indicated WTRU assistance information to optimize network side power consumption. In some cases, optimizing network side power consumption may include prioritizing macro TRP energy savings via one or more of antenna / port muting, adaptive sectorization, and selective SSB adaptation (e.g., wider beam width or reduced number of beams) when appropriate (e.g., in low load scenarios). Optimizing network side power consumption via including prioritized macro TRP energy savings may result in the greatest network side savings (i.e., in PA and BB power consumption). In other embodiments, it may be beneficial to activate more cells / TRPs. For example, under high load scenarios that require the macro TRP to be in a full availability state, it may also be beneficial to bring multiple small cells into a full availability state. It may be beneficial to bring multiple small cells into a full availability state, especially in the case of NR micro deployments where the small cells operate in dense urban deployments. In such scenarios, the added capacity of multiple small cells may result in more rapid transmissions, allowing more time for sleep, thereby reducing network side power consumption.

[0174] FIG. 4A is a diagram illustrating an example of an SSB transmission configuration for an anchor cell and a non-anchor cell. The anchor cell 432 may be in an active state. The anchor cell 432 may be configured to transmit discovery signals (e.g., SSB transmission, SIB transmission, RS transmission, etc.) at periodic intervals. The non-anchor cell 434 may be in a low availability state (e.g., "off", "deep sleep", or "microsleep" availability state). The non-anchor cell 434 may be configured to transmit discovery signals (e.g., SSB transmission, SIB transmission, RS transmission, etc.) at smaller (e.g., slower) periodic intervals than the anchor cell.

[0175] FIG. 4B shows an example diagram illustrating WTRU assistance information transmitted based on detection of a presence indication. FIG. 4B shows a WTRU procedure 400 for a switch-on request for a cell configured with a presence indication. Although illustrated with steps 403-422, in some embodiments, the procedure 400 may include only a portion of steps 430-422 (e.g., one or more of steps 403-422 may be omitted). In one embodiment, the WTRU 404 uses the presence indication to access resources in a cell, a gNB, such as gNB 402, or a TRP. For example, the WTRU 404 determines at 403 that a non-anchor cell (e.g., non-anchor cell 434) may be configured in a DTX state. To access resources, the WTRU 404 may be configured with a monitoring occasion to detect a presence indication associated with the cell, TRP, or carrier. Thus, the WTRU 404 monitors at 406 for discovery signals and / or presence indications from another cell (e.g., anchor cell 432). In some cases, the carriers may be associated with different cells. In some cases, the presence indication may be a DL signal, such as, but not limited to, a stripped down SSB, PRS, wake-up signal, CSI-RS, DCI, and other similar DL signals. In some cases, the presence indication may be an L2 message, such as, but not limited to, a MAC CE or RRC message. In some cases, the L2 message may be from a different cell or TRP. In one or more cases, the WTRU 404 may be configured to monitor 406 for discovery signals and / or presence indications associated with another cell, such as an anchor cell, such as the gNB 402. The gNB 402 may monitor 408a for presence indication information. For example, the gNB 402 may monitor for presence signals / information transmitted from the anchor cell. The presence indication (i.e., presence signal) may be, for example, but not limited to, an SSB, CSI-RS, etc. The presence information may be, for example, but not limited to, system information including resources for accessing a non-anchor cell.The anchor cell may be, for example, but not limited to, an SpCell, a PCell, a primary SCell, etc. The UL availability window 410a (as well as the UL availability window 410b) may correspond to a period during which a presence signal or information reception is detected and / or a period after a WTRU transmission of a wake-up request or assistance information. During the UL availability window, the WTRU may transmit uplink signals and channels. For example, the WTRU may transmit uplink signals and channels on configured UL channel resources on the non-anchor cell where the wake-up request was transmitted. In one or more cases, the gNB sleep opportunity 412 may correspond to a cell DTX / DRX duration during which the cell is not expected to transmit a subset of DL signals / channels and / or receive on UL channels / signals. The cell DTX / DRX duration may be in an availability state associated with gNB sleep, for example. In one or more cases, the WTRU triggers transmission of the wake-up request or information if the measured channel conditions are below a threshold (e.g., RSRP) and / or if an SSB associated with a non-anchor cell or an anchor cell is not detected, at 414. In one embodiment, an SSB associated with a non-anchor cell or an anchor cell may not be detected if the WTRU measures channel conditions below a threshold.

[0176] In one or more cases, the gNB 402 may be configured in a sleep state or an off state. For example, the WTRU 404 may be configured to monitor a presence indication associated with the sleeping / off gNB 402 after meeting a condition for transmitting a switch-on request and / or assistance information at 416. The assistance information may correspond to, for example, data arrival, lack of permission, insufficient coverage, high load, and the like. In one or more cases, the WTRU 404 is configured to successfully receive a presence indication, such as a gNB presence indication 408b. For example, the WTRU 404 may receive a gNB presence indication and / or information from the anchor cell 432. In such a case, the WTRU may assume an availability state associated with the cell (e.g., an “off” or “deep sleep” state). In one or more cases, the WTRU is configured to transmit one or more switch-on requests, WTRU assistance information, or initiate a random access (RA) procedure (e.g., a RACH or PRACH procedure) at 418 after successfully detecting a presence signal. Following detection, the WTRU may transmit one or more of a switch-on request, WTRU assistance information, or an RA within the UL availability window 410b. The WTRU may transmit an RA, for example, to initiate an RA on a non-anchor cell.

[0177] At 419, the gNB 402 may transmit an SSB on a non-anchor cell (e.g., non-anchor cell 434). The gNB 402 may transmit additional RS, SSB, Msg4, and / or CSI-RS resources at 420. In one or more cases, the gNB 402 may transmit the additional RS, SSB, Msg4, and / or CSI-RS resources in response to receiving the assistance information and / or switch-on request at 420. In one or more cases, the WTRU is configured to monitor the additional RS, SSB, Msg4, and / or CSI-RS resources after receiving the transmission switch-on request or a response to the switch-on request. In one or more cases, the WTRU is configured to change the availability state of the cell (e.g., to an “on” or “microsleep” state) at 422. For example, the WTRU is configured to change the availability state of the non-anchor cell. The WTRU may change the availability state of a cell, for example, after successfully receiving a response from the requested cell to the transmitted switch-on request.

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

Claims

1. 1. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: monitoring a presence indication signal in a second cell, the presence indication signal indicating that the first cell is in a low availability state; determining to transmit a wake-up signal for the first cell based on detecting the presence indication signal in the second cell and based on a measurement performed on a synchronization signal block (SSB) of the second cell being below a threshold, wherein the wake-up signal is transmitted prior to expiration of a predetermined time period after receiving the presence indication signal via the second cell; transmitting said activation signal; monitoring transmission of an SSB of the first cell after transmitting the wake-up signal; receiving information indicating that the first cell has transitioned to an active state after transmitting the wake-up signal; and transmitting data via the first cell after receiving the information indicating that the first cell has transitioned to the active state.

2. 10. The method of claim 1, further comprising: determining a discontinuous transmission (DTX) pattern for transmitting signals to the first cell based on the presence indicator signal received at the second cell.

3. The method of claim 1 , wherein resources for receiving the SSB of the first cell are determined based on resources used to receive the presence indication signal in the second cell.

4. 2. The method of claim 1, further comprising: determining that the first cell has returned to the low availability state after the predetermined period of time has elapsed since receiving the presence indication signal via the second cell.

5. 2. The method of claim 1, wherein the predetermined period of time comprises an uplink availability window, and the wake-up signal is part of a MAC control element (MAC CE) or WTRU assistance information.

6. The method of claim 1 , wherein the presence indication signal is indicated via a WTRU-specific DCI, a group common DCI, a MAC CE, or a paging message.

7. 2. The method of claim 1, further comprising adapting beam failure detection (BFD) measurements, radio link monitoring (RLM) measurements, or channel state information (CSI) measurements on the second cell as a function of an availability state of the second cell.

8. 2. The method of claim 1, further comprising: determining an SSB pattern for the second cell based on whether the second cell is in the low availability state or the active state.

9. 1. A wireless transmit / receive unit (WTRU), comprising: a processor, the processor comprising: monitoring a presence indication signal in a second cell, the presence indication signal being configured to monitor a presence indication signal in the second cell indicating that the first cell is in a low availability state; determining to transmit a wake-up signal for the first cell based on detecting the presence indication signal in the second cell and based on a measurement performed on a synchronization signal block (SSB) of the second cell being below a threshold, wherein the wake-up signal is transmitted prior to expiration of a predetermined time period after receiving the presence indication signal via the second cell; configured to transmit the wake-up signal; configured to monitor transmission of an SSB of the first cell after transmitting the wake-up signal; configured to receive information indicating that the first cell has transitioned to an active state after transmitting the wake-up signal; A wireless transmit / receive unit (WTRU) configured to transmit data via the first cell after receiving the information indicating that the first cell has transitioned to the active state.

10. The processor, 10. The WTRU of claim 9, further configured to determine a discontinuous transmission (DTX) pattern for transmitting signals to the first cell based on the presence indication signal received in the second cell.

11. The WTRU of claim 9 , wherein resources for receiving the SSB of the first cell are determined based on resources used to receive the presence indication signal in the second cell.

12. The processor, 10. The WTRU of claim 9, further configured to determine that the first cell has returned to the low availability state after the predetermined period of time has elapsed since receiving the presence indication signal via the second cell.

13. 10. The WTRU of claim 9, wherein the predetermined period of time comprises an uplink availability window, and the wake-up signal is part of a MAC Control Element (MAC CE) or WTRU assistance information.

14. The WTRU of claim 9 , wherein the presence indication signal is indicated via a WTRU-specific DCI, a group common DCI, a MAC CE, or a paging message.

15. The processor, 10. The WTRU of claim 9, further configured to adapt beam failure detection (BFD) measurements, radio link monitoring (RLM) measurements, or channel state information (CSI) measurements on the second cell as a function of an availability state of the second cell.

16. The processor, 10. The WTRU of claim 9, further configured to determine an SSB pattern for the second cell based on whether the second cell is in the low availability state or the active state.

Images