Discontinuous network access

Abstract

The disclosure relates to devices, methods, and systems implemented for discontinuous network access. The implementation includes monitoring a presence indication signal in the second cell. The implementation includes determining to transmit a wake-up signal for the first cell based on detecting a 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. This implementation includes transmitting a wake-up signal. The implementation includes monitoring transmission of the 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 the information indicating that the first cell has transitioned to the active state.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 327,557 filed on April 5, 2022 and U.S. Provisional Application No. 63 / 391,357 filed on July 22, 2022, the entireties of which are incorporated herein by reference. Background Art

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

[0004] The present disclosure relates to devices, methods and systems for discontinuous network access. In one or more specific implementations, when a non-anchor cell is in a network energy saving (NES) state, the WTRU monitors discovery signals and presence information in the anchor cell to access the non-anchor cell. For example, based on receiving the presence information, the WTRU sends a wake-up request to access the non-anchor cell. For example, after sending the wake-up request, the WTRU monitors the transmission from the non-anchor cell. When a response is received from the non-anchor cell, the WTRU changes the availability state of the non-anchor cell. In one or more specific implementations, the WTRU determines the active availability state associated with a given cell when receiving, for example, WTRU-specific or group-common downlink control information (DCI), a media access control (MAC) control element (MAC CE) or a paging. In one or more specific implementations, the WTRU adjusts beam failure detection (BFD), radio link monitoring (RLM), reference signaling / synchronization signal block (RS / SSB) monitoring, and channel state information (CSI) measurement on the cell according to the active availability state of the cell. In one or more implementations, upon receiving the group common indication, the WTRU switches the active bandwidth part (BWP) to the group common BWP configured for the NES. In one or more implementations, the WTRU includes one or more of the following NES WTRU assistance information: the cell index for which the state change is requested, the desired availability state, and the request for an on-demand SSB.

[0005] In one or more implementations, the WTRU may access resources in a cell, gNB, or transmit / receive point (TRP) with a presence indication. In one or more implementations, the WTRU may monitor the presence indication associated with a sleeping / 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 associated with the cell (e.g., "off" or "deep sleep"). In one or more cases, the WTRU may send a connection 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 blocks (SSBs) and / or CSI-RS resources after sending a connection request or receiving a response to the connection request. In one or more implementations, the WTRU may change the availability state of a cell after successfully receiving a response to a sent or connection request from the requested cell.

[0006] Devices, methods and systems for discontinuous network access may include SSB and CSI-RS adjustments. In one or more specific implementations, devices, methods and systems for determining the NES state of a cell are provided. In one or more cases, the devices, methods and systems discussed herein may provide effects on synchronization, initial access procedures, BFD and random access channels (RACH) based on discontinuous network transmission of common signals. In one or more cases, the devices, methods and systems discussed herein may be used so that the WTRU knows whether to measure MO. In one or more cases, the devices, methods and systems discussed herein may be used so that the WTRU knows whether to measure MO. In one or more cases, the devices, methods and systems discussed herein may be used so that the WTRU knows whether common cell signals (e.g., synchronization or reference signals) are sent as usual, rather than not receiving common cell signals based on poor channel conditions. In one or more cases, the devices, methods and systems discussed herein may be used to determine measurements associated with cells in an NES state (including RLM and BFD). In one or more cases, the devices, methods and systems discussed herein may be used so that the WTRU determines which resources are suitable for data, control or measurement based on the availability status. In one or more cases, the devices, methods and systems discussed herein may be used to determine initial access on an alternative cell.

[0007] A method for discontinuous network access is provided herein. In one or more specific implementations, the method includes monitoring the presence of an indication signal in a second cell. In one example, the presence of an indication signal indicates that the first cell is in a low availability state. In one or more specific implementations, the method includes determining to send a wake-up signal for the first cell based on the presence of an indication signal detected in the second cell and based on the measurement performed on the synchronization signal block (SSB) of the second cell being less than a threshold. In one example, the wake-up signal is sent before the expiration of a predetermined time period after the presence of the indication signal is received via the second cell. In one or more specific implementations, the method includes sending a wake-up signal. In one or more specific implementations, the method includes monitoring the sending of the SSB of the first cell after sending the wake-up signal. In one or more specific implementations, the method includes, after sending the wake-up signal, receiving information indicating that the first cell has transitioned to an active state. In one or more specific implementations, the method includes sending data via the first cell after receiving information indicating that the first cell has transitioned to an active state.

[0008] A wireless transmit / receive unit (WTRU) for discontinuous network access is provided herein. In one or more specific implementations, the WTRU includes a processor. In one or more specific implementations, the processor is configured to monitor the presence indication signal in the second cell. In one example, the presence indication signal indicates that the first cell is in a low availability state. In one or more specific implementations, the processor is configured to determine that a wake-up signal for the first cell is to be sent based on the detection of the presence indication signal in the second cell and based on the measurement performed on the synchronization signal block (SSB) of the second cell being less than a threshold. In one example, the wake-up signal is sent before the expiration of a predetermined time period after the presence indication signal is received via the second cell. In one or more specific implementations, the processor is configured to send the wake-up signal. In one or more specific implementations, the processor is configured to monitor the transmission of the SSB of the first cell after sending the wake-up signal. In one or more specific implementations, the processor is configured to receive information indicating that the first cell has transitioned to an active state after sending the wake-up signal. In one or more specific implementations, the processor is configured to send data via the first cell after receiving information indicating that the first cell has transitioned to an active state. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A more detailed understanding may be obtained from the following description given by way of example with reference to the accompanying drawings in which like reference numerals indicate similar elements.

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

[0011] Figure 1B It shows that Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) for use within a communication system is shown.

[0012] Figure 1C It shows that Figure 1A A system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) for use within a communication system is shown.

[0013] Figure 1D It shows that Figure 1A A system diagram of another exemplary RAN and another exemplary CN used within the communication system shown.

[0014] Figure 2 is an example time-frequency structure of a synchronization signal block (SSB).

[0015] Figure 3 is an illustration of an example beam scan.

[0016] Figure 4A is a diagram illustrating an example structure of SSB transmission of an anchor cell and a non-anchor cell.

[0017] Figure 4B are diagrams illustrating example aspects of the disclosure that may be implemented. DETAILED DESCRIPTION

[0018] Figure 1A 1 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, broadcast, 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 communication system 100 may employ one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0019] like Figure 1AAs shown, the communication 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, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of 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 send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a WTRU.

[0020] 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 that is 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, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0021] 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 send and / or receive wireless signals on one or more carrier frequencies (which may be referred to as cells (not shown)). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrums. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.

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

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

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

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

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

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

[0028] Figure 1AThe base station 114b in the 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 local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology (such as IEEE 802.11) to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology (such as IEEE 802.15) to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or a femtocell. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0029] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as 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 advanced security functions, such as user authentication. Although not described in detail in the text, the CN 106 / 115 may be configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as 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 advanced security functions, such as user authentication. Figure 1A Although not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ 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 be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0030] The CN 106 / 115 may also serve 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 that provides 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) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks 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 employ the same RAT as the RAN 104 / 113 or a different RAT.

[0031] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication 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 via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0032] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, 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 appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0033] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors 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 decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

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

[0035] Although the transmit / receive element 122 Figure 1B 1 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.

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

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

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

[0039] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information 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 acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0040] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules 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 video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (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, etc. Peripheral device 138 may include one or more sensors, which may be one or more of the following: 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.

[0041] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit 139 for reducing and / or substantially eliminating self-interference via signal processing performed by hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

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

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

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

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

[0046] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, 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.

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

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

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

[0050] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communications interface with a communications network.

[0051] In a representative embodiment, the other network 112 may be a WLAN.

[0052] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be transmitted between the source STA and the destination STA (e.g., directly between them) using a direct link establishment (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0053] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons 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 dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is listened / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0054] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0055] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by the transmitter STA. At the receiver of the receiver STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).

[0056] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support instrument type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0057] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only a 1MHz operating mode) is sending to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.

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

[0059] Figure 1D 1 is a system diagram illustrating the RAN 113 and the CN 115 in accordance with an embodiment. As noted 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 be in communication with the CN 115.

[0060] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated 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 one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and the gNB 180b (and / or the gNB 180c).

[0061] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. For example, 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 varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths over time).

[0062] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the evolved Node-B 160a, 160b, 160c. For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRU 102a, 102b, 102c.

[0063] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0064] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0065] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 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 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.

[0066] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 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 type may be IP-based, non-IP-based, Ethernet-based, etc.

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

[0068] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may 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. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks 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 via the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and the N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0069] Given that Figures 1A to 1D as well as Figures 1A to 1D , one or more or all of the functions described herein for one or more of the following may be performed by one or more simulation devices (not shown): WTRU 102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW 164, PGW 166, gNB 180a-180c, AMF 182a-182ab, UPF 184a-184b, SMF 183a-183b, DN 185a-185b and / or any other device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

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

[0071] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which can include one or more antennas) can be used by the simulation device to send and / or receive data.

[0072] The following abbreviations and acronyms are used herein, inter alia: 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); Configuration Grant or Cell Group (CG); Cyclic Prefix (CP); Conventional OFDM (Cyclic Prefix Dependent) (CP-OFDM); Channel Quality Indicator (CQI); Cyclic Redundancy Check (CRC); Channel State Information (CSI); Contention 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 License Assisted Access (eLAA); Further Enhanced License Assisted Access (FeLAA); Hybrid Automatic Repeat Request (HARQ); License Assisted Access (LAA); Listen Before Talk (LBT); Long Term Evolution (LTE), e.g. from 3GPP LTE R8 and higher; 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 (PID); Paging Occasion (PO); Physical Random Access Channel (PRACH); Primary Synchronization Signal (PSS); Random Access (or Procedure) (RA); Random Access Channel (RACH); Random Access Response (RAR) Radio Access Network Central Unit (RCU); Radio Front End (RF); Radio Link Failure (RLF); Radio Link Monitoring (RLM); Remaining System Information (RMSI); Radio Network Identifier (RNTI); RACH Occasion (RO); Radio Resource Control (RRC); None 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 (in independent subframe) (SWG); semi-persistent scheduling (SPS); supplementary uplink (SUL); secondary node (SN); transport block (TB); transport block size (TBS); transmit / receive point (TRP); time-sensitive communication (TSC); time-sensitive networking (TSN); uplink (UL); ultra-reliable low latency communication (URLLC); wide bandwidth part (WBWP); and wireless local area networks and related technologies (IEEE 802.xx domain) (WLAN).

[0073] Network energy conservation is being studied in Rel-18 to enable the network to attempt to minimize the power consumption used for device transmission and / or reception. Such minimization is beneficial for reducing operating costs and environmental sustainability. Compared with traditional systems, the NR design of Rel-15 minimizes transmissions from the network more efficiently when there is no data. For example, the cell-specific reference signal (CRS) that is always turned on is not used in NR. However, there is still potential for reducing energy consumption. For example, when the network is not transmitting during other activities such as baseband (i.e., digital) processing for reception or beamforming, the network may consume energy. In addition, even when the network is not serving the WTRU during a given period, such "idle" power consumption may be non-negligible in dense networks. If the network can turn off these activities when the network is not transmitting to the WTRU, energy consumption can be reduced. Additionally, NR can support beamforming with many ports (e.g., up to 64 transmit and receive ports), where energy consumption increases as the number of ports being utilized increases. However, the network may not have to use the maximum number of ports for all WTRUs. In one or more cases, if the network can adjust the number of ports to a required or minimum number of ports, power consumption can be reduced.

[0074] In one or more cases, the CSI may include at least one of the following: a channel quality index (CQI), a rank indicator (RI), a precoding matrix index (PMI), an L1 channel measurement (e.g., RSRP such as L1-RSRP, or SINR), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), and / or any other measurement quantity measured by the WTRU from a configured CSI-RS or SS / PBCH block. In one or more cases, the UCI may include: CSI, HARQ feedback for one or more HARQ processes, a scheduling request (SR), a link recovery request (LRR), a CG-UCI, and / or other control information bits that may be sent on the PUCCH or PUSCH. In one or more cases, any channel condition related to the state of the radio / channel may be determined by the WTRU based on one or more of WTRU measurements, L3 / mobility-based measurements, RLM status, and / or channel availability in unlicensed spectrum. For example, the WTRU may determine 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 example, the WTRU determines channel conditions based on one or more L3 / mobility based measurements (such as but not limited to RSRP, RSRQ, etc.). In yet another example, the WTRU determines channel conditions based on channel availability in an unlicensed spectrum. For example, the WTRU may determine whether a channel is occupied based on a determination of an LBT process. In another case, the WTRU may determine whether a channel has experienced consistent LBT failures. In one or more cases, PRACH resources may be provided, for example, but not limited to, in frequency. In one or more cases, PRACH opportunities (RO) may be provided, for example, but not limited to, in time measurements. In one or more cases, the preamble format may be provided, for example, but not limited to, in terms of total preamble duration, sequence length, guard time duration, and / or in terms of the length of a cyclic prefix. In one or more cases, a certain preamble sequence may be used to send a preamble in a random access procedure. In one or more cases, the PRACH resources may be characterized based on one or more of frequency resources, time resources, preamble format, etc. Frequency resources may include, for example, but not limited to, subcarriers, RBs, etc. Time resources may include, for example, but not limited to, PRACH opportunities, symbols, subframes, etc. Preamble format may include, for example, but not limited to, one or more of total preamble duration, sequence length, guard time duration, and length per cyclic prefix.

[0075] In one or more cases, the attributes of the scheduling information (e.g., uplink grant or downlink allocation) 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 to be carried; TCI state or SRI; number of repetitions; and determination 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; and an implicit indication of the attribute, such as, but not limited to, the DCI format, DCI size, CORESET or search space, aggregation level, identification of the first control channel resource of the DCI (e.g., index of the first CCE). In one or more cases, the mapping between the attribute and the value may be signaled by RRC or MAC. For example, the WTRU may signal the mapping between the attribute and the value via RRC or MAC.

[0076] In one or more cases, NR system information (SI) may include a MIB (Master Information Block) and multiple SIBs (System Information Blocks). In one or more cases, the SIBs may be divided into minimum SI and other SI. In one or more cases, the minimum SI may carry information required for initial access and acquisition of any other SI. In one or more cases, the minimum SI may include MIB and SIB1. For a WTRU that is allowed to reside on a cell, the WTRU may obtain the contents of the minimum SI of the cell. In one or more cases, 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, other SI may also be referred to as on-demand SI because the gNB may send / broadcast these SIBs when explicitly requested by the WTRU. When explicitly requested by the WTRU, the gNB may send / broadcast these SIBs for network energy saving purposes.

[0077] In one or more cases, the MIB may include cell barring status information and basic physical layer information of the cell required to receive further system information (e.g., 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 80ms, and repeated transmissions may occur within 80ms. In one or more cases, SIB1 may define the scheduling of other system information blocks. In addition, SIB1 may include information required for initial access. In one or more cases, SIB1 may also be referred to as residual 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 a UE in the RRC_CONNECTED state.

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

[0079] Multiple SSBs may be sent within the frequency width of a carrier. In some cases, the PCIs of SSBs sent in different frequency positions 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.

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

[0081] In one or more cases, several beams may be associated with a given cell. In one or more cases, multiple SSBs may be transmitted on different beams within a given cell (ie, for beam scanning cases). Figure 3 An example of beam scanning performed between the gNB 306 and multiple WTRUs (e.g., a first WTRU1 and a second WTRU2) is illustrated. Figure 3 As shown, multiple SSBs 302 may be sent at a certain interval. In addition, 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 sent via a specific beam radiating in a certain direction. Multiple WTRUs (e.g., a first WTRU1 and a second WTRU2) may be located at different locations around the gNB 306. Figure 3 As shown, the WTRU may measure the signal strength of each SSB detected by the WTRU within a certain period of time (e.g., a period of a SSB set). In addition, based on the measurement results, the WTRU may identify the SSB index with the strongest signal strength. For example, Figure 3 As shown, beam #1 is the best beam (i.e., the selected beam) for the first WTRU1. That is, beam #1 provides the strongest signal strength for the first WTRU1. Figure 3 As shown, beam #7 is the best beam for the second WTRU2. That is, beam #2 provides the strongest signal strength for the second WTRU2.

[0082] In one or more cases, the number of different beams transmitted may be determined based on the number of SSBs transmitted within an SSB burst set. An SSB burst set 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 within an SSB set may be 4 or 8, while for FR2, the maximum number of SSBs within an SSB set may be 64.

[0083] In one or more cases, the WTRU may determine whether the WTRU can transmit or receive on certain resources. For example, the WTRU may determine whether the WTRU can transmit or receive on certain resources based on the network availability status. The network availability status may include information suggesting and / or indicating the power saving state of the gNB. In one or more cases, the availability status may correspond to the network power saving state or the gNB activity level. In one or more cases, the availability status may be uplink specific (e.g., DRX) or downlink specific (e.g., DTX). Additionally or alternatively, the availability status may change from symbol to symbol, slot to slot, frame to frame, or over a longer granularity duration. In one or more cases, the WTRU may determine the availability status. In one or more other cases, the network may indicate the availability status. The availability status may be, for example, but not limited to, "on", "off", "dormant", "micro-sleep", "deep sleep", or other similar states. 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. The "sleep" availability state may indicate that the gNB wakes up periodically to send certain signals (e.g., but not limited to presence signals, synchronization, reference signals, etc.) or receive certain UL signals. The availability states may, for example, be configured with periodic availability periods and non-availability periods. In some availability states, one or more DL or UL resources may not be available during certain time periods (e.g., during non-availability periods). As a result, the network may shut down baseband processing and other activities. In one or more cases, some measurement resources (e.g., SSB or CSI-RS) are available in certain availability states.

[0084] 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 will meet the WTRU's needs. The wake-up request may include a transmission that a low-complexity receiver can decode at the gNB. In some cases, the wake-up request transmission may require decoding with minimal energy consumption requirements. Note that wake-up requests, turn-on requests, or turn-on WTRU assistance information may be used interchangeably as discussed herein. In one or more availability states (e.g., "micro-sleep" or "deep sleep"), the WTRU may exclusively use wake-up requests. In addition, the wake-up request may refer to a physical uplink signal sent by the WTRU to request a change in the availability state. The physical layer design of the wake-up request signal is further described in detail in U.S. application No. 63 / 275,207, which is incorporated herein by reference in its entirety. In one or more other cases, the turn-on request may be a physical layer or L2 indication from the WTRU to the network. The WTRU may deliver an L2 indication as one or more of, for example but not limited to, a MAC CE, UCI, RRC signaling, PUCCH, RACH indication, etc. Additionally or alternatively to the above, the WTRU may include on-WTRU assistance information and / or positioning reports.

[0085] In one or more cases, the WTRU determines the availability state based on the receipt of an availability state indication from, for example, 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, if the WTRU determines that the resources are available in the active availability state, the WTRU determines whether the resources are applicable for transmission / reception and / or measurement of the determined network availability state. The availability state is applicable to at least one transmission, reception 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, for example, but not limited to, one or more of a serving cell, a cell group, a frequency band, a bandwidth portion, a TRP, a set of spatial elements, and a frequency range within a bandwidth portion.

[0086] In one or more cases, network energy consumption may be significant and in many cases, such as during quiet hours, unnecessary. In some cases, to reduce energy consumption, the network may turn off small cells or FR2 power-hungry cells and rely on macro cells for coverage during quiet hours. In one or more cases, the gNB may combine information including, but not limited to, WTRU measurements, WTRU assistance information, interference status, load information, proprietary information to determine which cells to turn off and which cells to rely on. In one or more cases, the gNB turns off to inform neighboring cells whether the neighboring cells should be turned on / off. However, in some cases, such as when the number of active WTRUs changes, or the concentration of WTRUs increases, the network may not be aware of the sudden increase in network access demand. In addition, when the capacity boosting cell is turned off, some WTRUs may experience coverage loss. In some cases, the WTRU may want to notify the network about the coverage loss. Additionally, during busy hours, network power consumption may be quite significant, especially when all or a large number of frequency bands, carriers, antenna chains, beamforming antennas are used. Therefore, the network access capacity may be adjusted during busy hours to reduce energy consumption. In one or more cases, the consumed power associated with 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 being used, and whether narrow beams are used. Therefore, the disclosure provided herein provides solutions that enable the network to know when the network 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 WTRU being served.

[0087] 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 sleeping / off gNB. Additionally or alternatively, the WTRU may monitor a presence indication associated with a sleeping / off gNB after the conditions for sending a connection request / assistance information are met. In one or more cases, the WTRU may monitor the reception of a presence indication or signal associated with a gNB configured with 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 sent by an associated cell or gNB that is sleeping. For example, a gNB may sleep in a certain availability state (e.g., deep sleep, micro sleep, 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 example, the downlink information bit may be delivered to the WTRU via dedicated signaling (e.g., RRC signaling or MAC CE). The WTRU may conditionally monitor the presence indication occasion if any trigger / condition for sending wake-up WTRU assistance information or connection request is met.

[0088] In one or more cases, the WTRU may receive presence indications via different serving cells and / or different TRPs in a cell. In some cases, if the associated gNB is configured to be in a certain availability state (e.g., off or dormant), different serving gNBs may monitor or deliver presence indications. In some cases, the WTRU may monitor the presence indication of each TRP. In such cases, the presence indication may be associated with a specific TRP. In some cases, different TRPs may send presence indications associated with a certain TRP.

[0089] In one or more cases, the WTRU may determine the availability state of the cell based on at least one attribute of the availability state indication of the received presence indication associated with the cell. The presence indication may indicate the availability state associated with the cell belonging to the presence indication occasion. In some cases, the determined or indicated availability state may be applicable until the next presence indication occasion.

[0090] In one or more cases, the WTRU is configured with monitoring opportunities. The WTRU may be configured with monitoring opportunities to detect presence indications associated with a cell, TRP, or carrier. In some cases, carriers may be located on different cells. In some cases, the WTRU may be configured with presence indication opportunities to monitor DL ​​signals and / or indications associated with presence indications. The WTRU may be configured with periodicity associated with the presence indication of each cell. In addition to or as an alternative to the periodic association, the WTRU may be configured to monitor the presence indication of the cell. 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 the SSB, RS, or other DL signals and the presence signal of the cell.

[0091] In one or more cases, the WTRU sends one or more of a connection request, WTRU assistance information, or RA after successfully detecting the presence of a signal. The WTRU may send and / or trigger one or more of a wake-up request, a connection request, and the sending of wake-up WTRU assistance information. For example, when the presence of a signal is successfully detected, the WTRU may send and / or trigger one or more of a wake-up request, a connection request, and the sending of wake-up WTRU assistance information. In some cases, the WTRU may initiate a new random access procedure on the cell. For example, if the WTRU successfully detects a presence indication associated with a cell, the WTRU initiates a new random access procedure on the cell. In some cases, the WTRU may start a timer when the presence of a signal is successfully detected, and / or send a wake-up request when the timer expires. In some cases, when the timer is running, the WTRU may assume that the availability state is applicable to the associated cell. In some cases, the WTRU may fall back to a different or default availability state after the timer expires.

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

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

[0094] In some cases, the WTRU may use a counter or a presence indication detection timer before changing the active availability state based on the reception of a presence indication. In some cases, the WTRU may use a counter or a presence indication detection timer before making an availability state determination based on the reception of a presence indication. In some cases, if the detection timer expires, the WTRU changes the availability state. In other cases, if the WTRU counts a consecutive number of lost samples of the presence indication, the WTRU changes the availability state. For example, the WTRU may be configured with a time period for measuring presence indication samples. If the WTRU does not measure a presence indication, the WTRU may consider that no presence indication is detected. For example, if the WTRU determines that the channel measurement value is less than a threshold before the end of the detection window, the WTRU considers that no presence indication is detected.

[0095] 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 to a sent or connected request from a requested cell. In some cases, after the WTRU successfully receives a response to a sent WTRU assistance information or connected request from a requested cell, the WTRU may change the availability state associated with the detection of the presence of a signal (e.g., the WTRU assumes an "on" state). 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, an SSB, a CSI-RS, a PRS, a PDCCH, a DCI, a PDSCH, a HARQ-ACK. The L2 message may be, for example, an RRC message, a DL MAC CE, a Msg2, a MsgB, or a Msg4.

[0096] 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 sending a connection request. In another example, the WTRU may monitor additional SSB and / or CSI-RS resources after receiving a response to the connection request. In some cases, after the sending of wake-up WTRU assistance information and / or a connection request, the WTRU may begin monitoring additional TRP, SSB and / or CSI-RS resources. In some cases, after successfully receiving a response to the connection request, the WTRU may begin monitoring additional TRP, SSB and / or CSI-RS resources. After the WTRU successfully measures the channel conditions (e.g., RSRP, SINR) on the measurement resources of the associated cell that are above the configured threshold, the WTRU may change the availability state associated with the detection of the presence of a signal (e.g., turned on).

[0097] 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 SSB signal, such as PSS / SSS without PBCH multiplexing, wide beam SSB, or omnidirectional SSB. In some cases, the WTRU may monitor and attempt to synchronize to the simplified or stripped SSB signal on a synchronization raster different from the synchronization raster used / configured for the traditional WTRU. In another example, the presence indication signal may be a PRS. In some cases, the WTRU may receive the PRS from a different cell or TRP. In some cases, the WTRU may receive the PRS on a configured subset of PRS resources. In another example, the presence indication signal may be a CSI-RS. In some cases, the WTRU may receive the CSI-RS from a different cell or TRP. In some cases, the WTRU may receive the CSI-RS on a configured subset of CSI-RS resources. In another example, the WTRU may detect the presence indication based on ether energy sensing. For example, the WTRU may detect a DL signal associated with a wake-up radio. In yet another example, 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 example, the presence indication signal may be a PDSCH or PDCCH received on a different cell or TRP. In some cases, the WTRU may receive the PDSCH or PDCCH on a configured subset of resources, coreset, or search space. In another example, the presence indication signal may be one or more SSBs received from different cells or TRPs. In some cases, the WTRU may receive one or more SSBs on a configured subset of SSB opportunities.

[0098] In one or more cases, the WTRU may monitor the synchronization relationship between the presence indication and the SBS. In one or more cases, the WTRU may monitor the presence indication during configured or predefined occasions. For example, the predefined occasions may be bound to the SSB transmission time or a subset of the SSB transmission time of the serving cell associated with the indication according to the 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.

[0099] 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, if the presence indication is time-frequency synchronized with the cell, the WTRU may monitor for presence indications on the same cell associated with the presence indication. The WTRU may monitor and / or detect a presence signal based on SSB transmission using a new synchronization raster subset (or a different base sequence).

[0100] In one or more cases, when the WTRU successfully receives a presence indication or a gNB response to a subsequent wake-up request or connection 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 the legacy SSBs associated with the "on" availability state. In some cases, the WTRU may perform another synchronization and / or initial access procedure upon detecting an available SSB set. In one or more cases, when a stripped SSB or enhanced SSB format is detected, the WTRU may assume a different SSB pattern and / or periodicity. In one or more cases, when a stripped SSB / presence signal is received, the WTRU may read the RMSI for an alternative SSB pattern / configuration.

[0101] 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 various information. For example, the presence indication L2 signal / information may include an associated cell index to which the presence indication applies. In another example, the presence indication L2 signal / information may include an associated TRP index to which the presence indication applies. In another example, the presence indication L2 signal / information may include an associated carrier or frequency band to which the presence indication applies. In another example, the presence indication L2 signal / information may include an availability status associated with the indicated cell, TRP or carrier. In another example, the presence indication L2 signal / information may include relevant synchronization, cell search or initial access information that may be used on the indicated cell (e.g., PRACH resources). In another example, the presence indication L2 signal / information may include a duration associated with the availability status. In some cases, the duration associated with the availability status may be implicitly implied from the reception of the L2 presence indication. In one or more cases, the WTRU may assume that the cell is no longer available (or the indicated / implied availability status is no longer available) after such timer expires. In some cases, the WTRU may assume that the indicated / implied availability status is no longer applicable. In another example, the presence indication L2 signal / information may include an RRC message or additional configuration. In another example, the presence indication L2 signal / information may include a MAC CE subheader or identifier.

[0102] In one or more cases, the WTRU may be configured with an UL availability window. In some cases, during the UL availability window, the WTRU sends an UL signal after detecting the presence indication and / or at a preconfigured periodic timing. In some cases, the WTRU may maintain a "gNB activity timer". In some cases, the activity timer is started after the WTRU receives a response to a wake-up request signal, WTRU assistance information, or a connection request to the WTRU. In some cases, the WTRU starts a "gNB activity timer" after the WTRU receives an indication of the presence (e.g., SSB) or an indication of a DCI or MAC CE (e.g., a WTRU-specific scheduling DCI). The WTRU may start the gNB activity timer at a predefined periodic timing. In some cases, the configuration of the predefined periodic timing may be provided by broadcast or dedicated signaling. In some cases, the periodicity between the UL windows may be configured based on the availability status. In some cases, the WTRU applies the periodicity based on the activity availability status. In one or more cases, the WTRU may independently maintain gNB activity times for the DL and UL directions. For example, the WTRU may maintain a DL gNB activity timer and another UL gNB activity timer.

[0103] While the gNB Active Timer is running or during the gNB Active Time (e.g., during the availability period of an availability state), the WTRU may send 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). When the "gNB Active Timer" expires, the WTRU may switch to a different availability state. In some cases, the WTRU extends the gNB Active Timer after UL transmission or DL ​​reception. When the "gNB Active Timer" expires, the WTRU falls back to a less periodic gNB active cycle or availability state. In some cases, in a less periodic gNB active cycle or availability state, the UL availability opportunity window and / or presence indication may occur with different configuration periodicities.

[0104] In one or more cases, the WTRU monitors for a presence indication prior to a UL availability window. In some cases, the WTRU monitors for a presence indication prior to a UL availability window in a subset of gNB activity cycles or availability states. In one or more cases, the WTRU may determine to conditionally apply the UL availability window upon successful receipt of a presence indication or an indication from the network via a DCI or MAC CE. In some cases, based on a subset of gNB activity cycles or availability states, the WTRU may determine to conditionally apply the UL availability window upon successful receipt of a presence indication. For example, the WTRU starts the UL availability window based on the WTRU receiving a presence indication, and the WTRU is in a "deep sleep", "dormant" or "off" availability state. The WTRU assumes that the UL availability window automatically starts at a pre-configured periodic occasion in the "on" or "micro sleep" availability state.

[0105] In one or more cases, the WTRU may be configured with a connection request and wake-up WTRU assistance information. In some cases, the WTRU may be configured with a subset of cells, carriers, or frequency bands as "capacity-enhancing cells / frequency bands" through broadcast or dedicated signaling. In some cases, based on the configuration, the WTRU may transmit a connection / wake-up request and / or wake-up WTRU assistance information. For a given cell (e.g., PCI), the WTRU may be configured with a complementary / associated "capacity-enhancing cell or carrier". The capacity-enhancing cell or carrier may be, for example, a small cell associated with a macro cell. In some cases, the WTRU may consider a cell of an SCG / SN as a capacity-enhancing cell associated with one or more cells in an MCG / MN. The WTRU may consider a carrier of the same gNB (e.g., SCell) as a capacity-enhancing cell associated with a primary carrier (e.g., PCell) on the same gNB. The WTRU may implicitly determine a capacity-enhancing cell as any cell configured with an existence indication, where the indication is sent from the same cell or a different cell.

[0106] For a capacity enhancement cell associated with another cell, the WTRU may monitor the presence indication on the associated cell and / or use the uplink resources of the associated cell to send a wake-up WTRU assistance information or request. In one or more cases, the WTRU triggers and / or sends a connection request or wake-up WTRU assistance information. For example, the WTRU triggers and / or sends a connection request or wakes up WTRU assistance information to indicate a change in the availability state of a cell designated as capacity enhancement. In some cases, the WTRU triggers and / or sends a connection request or wakes up WTRU assistance information to indicate a change in the availability state of a cell designated as capacity enhancement based on a condition or trigger that is 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 period associated with a measurement presence indication. In another example, detecting a cell presence signal may include detecting a cell presence signal after a trigger condition associated with sending wake-up assistance information is met. For example, the trigger condition associated with sending wake-up assistance information may be met by detecting that a presence signal associated with a requested cell with a channel quality metric is above a threshold. In one or more cases, the condition or trigger may include the absence of detection of a presence signal associated with the cell. For example, the absence of detection of a presence signal associated with the cell may correspond to the absence of detection of the presence signal in a past period associated with measuring the presence indication. In one or more cases, the condition or trigger may be based on a channel measurement, wherein the condition or trigger is satisfied when the channel measurement is above or below a configured threshold. In one example, the channel measurement may be a measured RSSI or RS-SINR. In another example, the channel measurement may be a lack of SSB samples to be measured on the requested cell or serving cell. In another example, the channel measurement may include the configured SSB of the cell and / or the absence of detection of CSI-RS or measurement of CSI-RS below a configured threshold. In one or more cases, the WTRU measurement may be a physical layer measurement or an L3 measurement. The physical layer measurement may be, for example, but not limited to, SINR / RSRP, CQI, channel occupancy, RSSI, power headroom, exposure headroom, etc. The L3 measurement 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 channel measurement, where the condition or trigger is satisfied when the WTRU detects high load or interference, when the WTRU does not detect SSB, or when the WTRU does not detect PSS / SSS on the requested cell or any cell. In one or more cases, the condition or trigger may be based on channel measurement, where the condition or trigger is satisfied when the WTRU detects channel availability in the unlicensed spectrum. For example, when the channel is occupied, the WTRU may detect channel availability in the unlicensed spectrum based on the determination of the LBT process.In another example, the WTRU may detect channel availability in the unlicensed spectrum when the channel is considered to have experienced consistent LBT failures. For example, the WTRU may trigger a wake-up WTRU assistance information after detecting consistent UL LBT failures.

[0107] 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 when data arrives from one or more of a subset of DRBs, SRBs, LCHs, LCGs, etc. In another example, the WTRU may determine that the condition or trigger is met when the arriving data is associated with a certain priority or index. The WTRU may reflect such data in the assistance information content.

[0108] In one or more cases, the condition or trigger may include a triggering of an RRC state change or an RRC procedure. The RRC procedure may be, for example, but not limited to, RRC recovery, RRC establishment, RRC reestablishment, etc. In one or more cases, the condition or trigger may include triggering the reception of an RRC message (e.g., RRC release).

[0109] In one or more cases, the condition or trigger may include one or more of performing a positioning process, sending a positioning report, and determining a location within the coverage of a cell as the best server. For example, if the WTRU determines that the WTRU's location is within the best server coverage of a capacity boosting cell, the WTRU triggers the wake-up WTRU assistance information. For example, the best server coverage may be an area where the WTRU measures the capacity cell as having the best channel conditions compared to other cells in the same frequency. In one or more cases, the WTRU may include the location of the WTRU in the WTRU assistance information. In one or more cases, the WTRU may be allowed or regulated to send the wake-up WTRU assistance information within a certain area or within the predetermined coverage of the requested cell based on the determined location of the WTRU. The certain area may include the coverage area of ​​another replacement serving cell or a configured area of ​​each cell, such as but not limited to the distance from the known location of the requested gNB. In one or more cases, the condition or trigger may include the amount of buffered data being above a threshold. The WTRU may trigger a wake-up request based on the amount of buffered data being above a configured or predefined threshold. For example, based on a configured subset of DRB, LCH, or LCG, the WTRU triggers a wake-up request if the amount of buffered data is above a configured or predefined threshold. The WTRU may include the data amount in the WTRU assistance information (eg, BSR or modified BSR for a subset of LCH / RB / LCG). The WTRU may be configured with a list of RBs or priorities that may trigger the inclusion / transmission of the WTRU assistance information.

[0110] In one or more cases, the condition or trigger may include triggering a BSR and / or a SR. For example, the WTRU may trigger waking up the WTRU assistance information based on a new BSR and / or a new SR being triggered. In some cases, the WTRU may trigger waking up the WTRU assistance information based on a new BSR and / or a new SR if a new SR is used for a given SR configuration. In one example, the triggering of the sending of the wake-up assistance information may trigger a new BSR.

[0111] 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 be sent, a priority associated with the UCI, or an LCH or DRB associated with the UCI. For example, the WTRU may trigger the sending of wake-up WTRU assistance information based on the availability of UCI or data to be sent, the priority associated with the UCI, or the LCH or DRB associated with the UCI.

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

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

[0114] In one or more cases, the condition or trigger may include entering a certain DRX state, cycle or energy 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 activity timer.

[0115] In one or more cases, the condition or trigger may include the current time during the day or night.For example, the WTRU may send wake-up assistance information in a subset of hours that may be configurable by the network.

[0116] 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 the mobility to the 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 example, the condition or trigger is met when the WTRU determines that a "keep alive" timer expires. For example, the WTRU may start a keep alive timer when sending a first connection request or waking up the WTRU assistance information. The WTRU may send a second connection request or wake up the WTRU assistance information when the timer expires. In some cases, when the timer for the second connection request or wake up the WTRU assistance information expires, the WTRU restarts the timer. In one or more cases, the duration of the keep alive timer and / or whether the WTRU retransmits the connection request or wake up the WTRU assistance information may be predefined or explicitly signaled through 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 a cell (such as but not limited to SSB). For example, the duration may be a predefined or configured multiple of the SSB periodicity of the cell.

[0117] In one or more cases, the WTRU may be configured to send wake-up WTRU assistance information or a connection request. For example, the WTRU sends the wake-up WTRU assistance information or the connection request in a subset of RRC states (e.g., RRC inactive or RRC idle). In another example, the WTRU may send the wake-up WTRU assistance information or the connection request in a subset of availability states associated with the requested cell. For example, the WTRU may send the wake-up WTRU assistance information or the connection request in a subset of availability states associated with the requested cell, such as whether the requested cell is configured to be in a low availability state, such as an "off", "deep sleep" or "micro sleep" availability state. In another example, the WTRU sends the wake-up WTRU assistance information or the connection request in a subset of availability states associated with cells using uplink resources. In another example, the WTRU sends the wake-up WTRU assistance information or the connection request in a subset of availability states associated with cells where the WTRU receives a presence indication.

[0118] In one or more cases, the WTRU may perform measurements on the capacity enhancement cell. In one or more cases, the WTRU may provide feedback and / or measurement results to the macro cell / current serving cell that has been turned on. The WTRU may obtain SI, perform initial access or cell search (e.g., on the requested cell). The WTRU may obtain SI, perform initial access or cell search (e.g., on 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 the connection request. If the WTRU is in RRC idle or inactive state, the WTRU may monitor paging to receive a gNB response after sending the wake-up WTRU assistance information or the connection request. In some cases, the WTRU may monitor paging after sending the wake-up WTRU assistance information or the connection request to receive a gNB response on a paging occasion, P-RNTI, or a subset of PDCCH resources.

[0119] In one or more cases, the WTRU may be configured to send wake-up WTRU assistance information. For example, the WTRU sends the wake-up WTRU assistance information as part of one or more of the following: an RRC message, a UL MAC CE report indicating cell / carrier / BWP information, a measurement report, a BSR MAC CE, an SR, or a positioning report.

[0120] 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 cell indices for which one or a combination of the following exists: wake-up is requested, change of availability state is requested or expected, or presence indication is detected. In some cases, the wake-up WTRU assistance information may include one or more of the gNB ID, PCI, SN id, or carrier ID. In another example, as part of the wake-up WTRU assistance information, the WTRU may include TRP indices for which one or a combination of the following exists: wake-up is requested, change of availability state is requested or expected, or presence indication is detected. In another example, as part of the wake-up WTRU assistance information, the WTRU may include associated carriers or frequency bands for which one or a combination of the following exists: wake-up is requested, change of availability state is requested or expected, or presence indication is applicable. In another example, as part of the wake-up WTRU assistance information, the WTRU may include the desired availability state associated with one or more of the indicated cells, carriers, TRPs, or frequency bands. In another example, as part of the wake-up WTRU assistance information, the WTRU may include an RRC message (e.g., a DCCH or CCCH message), and the RRC message may include a WTRU identity. The RRC message may be a DCCH message, a CCCH message, etc. In another example, as part of the wake-up WTRU assistance information, the WTRU may include a MAC CE subheader or identifier. In another example, as part of the wake-up WTRU assistance information, the WTRU may include a request to activate / deactivate an antenna chain or increase the number of antenna chains. In another example, as part of the wake-up 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 example, as part of the wake-up WTRU assistance information, the WTRU may include a request to activate / deactivate a CSI-RS, a PRS, or related resources. For example, the request may be a request to receive an on-demand CSI-RS. In another example, as part of the wake-up WTRU assistance information, the WTRU may include a request to activate / deactivate a transmit or receive point in a coordinated multi-point system. The coordinated multi-point system may include, for example, but not limited to, one or a combination of a cell, a cell group, or a TRP group. In another example, as part of the wake-up 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 related measurement resources. In another example, as part of the wake-up WTRU assistance information, the WTRU may include the location of the WTRU, a positioning report, or positioning related measurements.In another example, as part of the wake-up WTRU assistance information, the WTRU may include a radio link failure report or related measurements. In another example, as part of the wake-up WTRU assistance information, the WTRU may include a beam failure report or related measurements, such as a beam failure MAC CE. In another example, as part of the wake-up WTRU assistance information, the WTRU may include a WTRU power consumption profile, metrics or statistics, including one or more of active DRX mode, power headroom and MPE related measurements. In another example, as part of the wake-up WTRU assistance information, the WTRU may include a request for one or more of a wider BWP, a BWP change, a SUL activation, a BWP index to be activated, a carrier index to be activated, and related measurement resources. In another example, as part of the wake-up WTRU assistance information, the WTRU may include a request to receive on-demand SSBs and / or CSI-RS associated with one or more cells, TRPs, or spatial elements. In another example, as part of the wake-up WTRU assistance information, the WTRU may include an indication of the WTRU's newly arrived data type (e.g., RB type or index) and related latency metrics.

[0121] In one or more cases, the WTRU may monitor cell-specific DL sources when sending wake-up WTRU assistance information or connection requests - to measure channel conditions, perform initial access, synchronization, and / or receive control and / or information. 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 certain PSS / SSS or CSI-RS when sending a request for an on-demand SSB or on-demand RS.

[0122] In one or more cases, the WTRU may send wake-up assistance information. For example, the WTRU sends the wake-up WTRU assistance information on an available grant. In some cases, the WTRU sends the wake-up WTRU assistance information on an available grant that is limited to transmission on a different serving cell. The different serving cell may be, for example, but not limited to, a cell or carrier that is different from the cell or carrier requested or indicated in the WTRU assistance information or the connection request. In some cases, the WTRU initiates a RACH / SR procedure based on the WTRU not having resources for sending 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 sending WTRU assistance information being met.

[0123] In one or more cases, the WTRU may perform a mobility, cell search, or synchronization procedure after sending the wake-up WTRU assistance information. For example, the WTRU may perform a mobility, cell search, or synchronization procedure after sending the wake-up WTRU assistance information on the requested cell. In another example, after receiving a response from the network in response to the sending of the WTRU assistance information, the WTRU may perform a mobility, cell search, or synchronization procedure after sending the wake-up WTRU assistance information on the requested cell. The response may be a HARQ ACK sent to a PUSCH containing the WTRU assistance information.

[0124] In one or more cases, upon triggering the wake-up of WTRU assistance information, the WTRU may perform a positioning procedure, a PRS measurement, or may send a pSRS.

[0125] In one or more cases, the WTRU may send another WTRU assistance information after the previous wake-up WTRU assistance information is acknowledged. In one or more cases, the WTRU may send another WTRU assistance information after the timer has elapsed and before a response to the WTRU assistance information is received from the gNB.

[0126] In one or more cases, the WTRU may start an inhibit timer when sending the wake-up WTRU assistance information. Based on the WTRU assistance information sent as part of the uplink transmission block, the WTRU may appropriately rely on the HARQ retransmission mechanism for retransmission. In one or more cases, the WTRU may retransmit the WTRU assistance information after the inhibit timer expires.

[0127] 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 following: the WTRU performs a configured number of retransmission attempts, the WTRU does not receive a response from the network to wake up the WTRU assistance information, and an inhibit timer expires.

[0128] In one or more cases, the WTRU may be configured with a maximum number of wake-up WTRU assistance information transmissions allowed. In some cases, the WTRU maintains a counter, and after the transmission of the wake-up WTRU assistance information, the WTRU increments the counter by, for example but not limited to, 1. In some cases, the WTRU may send multiple wake-up request signals. For example, the WTRU may send multiple wake-up request signals until the value configured for the maximum number of wake-up request transmissions allowed. In some cases, the WTRU resets the counter when it receives a response to the wake-up assistance information from the gNB. In some cases, the WTRU moves to the RRC idle or inactive state after the prohibit timer expires. In some cases, the WTRU moves to the RRC idle or inactive state or moves to the RRC idle or inactive state after the maximum number of retransmission attempts is reached.

[0129] In one or more cases, the wake-up indication includes two components sent continuously by the WTRU. In some cases, the WTRU may send the two components continuously with a timing gap in between. In some cases, the first component may be a signal and the second component 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 relatively low power, such as (but not limited to) a signal using on-off keying. In other cases, the signal may constitute a specific signature that may trigger a change in the activity level (e.g., availability state) at the receiving node. For example, in some cases, the receiving node activates certain RF / baseband components. Following the signal, the WTRU monitors a specific set of monitoring opportunities to receive signaling for resource allocation. The WTRU sends PUCCH and / or PUSCH in the allocated resources, and the PUCCH and / or PUSCH may contain further wake-up assistance information.

[0130] In one or more cases, the WTRU may be configured to determine the network power saving state of a cell. In one or more cases, after receiving DL signaling that changes the availability state of a cell or TRP, the WTRU considers the active availability state associated with the cell, carrier, TRP, BWP, or band to be in "off", "deep sleep", or "micro sleep" state. For example, the WTRU may receive an 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 (e.g., group common DCI or indication) from L1 / L2 signaling.

[0131] In one or more cases, the WTRU implicitly assumes a certain availability state (e.g., "off", "deep sleep", "micro sleep", or "dormant") associated with a cell, carrier, TRP, BWP, or frequency band based on at least one of the following. For example, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on the receipt of a command or signal indicating a change in the availability state. For example, the command or signal may be provided in a group common DCI or RRC signaling in connected mode. The WTRU may implicitly determine the availability state based on the receipt of periodic DL signaling. The WTRU may be configured or specified to associate the availability state with one or more DL signal types. For example, the DL signal type may include SSB, partial SSB, and / or one or more periods. In another example, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on the gNB DTX state. That is, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on whether the gNB is in active time or whether the associated activity timer is running. In another example, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on the reception of 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. For example, a subset of POs may be a subset of POs aligned with a NESDRX cycle or a configured subset of PDCCH resources. After receiving a paging message with a certain P-RNTI, a separately configured NESP-RNTI, or a NES group RNTI, the WTRU may assume a certain availability state. After receiving a paging message with a certain P-RNTI, the WTRU may assume a certain availability state. The WTRU may be configured with one or more PEI subgroups for NES. In one or more cases, a PEI subgroup may be associated with one or more availability states. After receiving a PEI with an NES subgroup, the WTRU may assume a certain availability state. For example, the WTRU, upon receiving a PEI with an NES subgroup, assumes a certain availability state based on the subgroup being configured and / or associated with an availability state. An indication of the availability state or an availability state switch may be indicated in a paging payload. For example, an indication of the availability state or an availability state switch may be indicated in a paging payload as a flag portion of a paging message or a short message. Such a paging indication may also indicate an alternative cell monitoring paging when the cell from which the signaling is received is in an off, sleep, or NES state. Such a paging indication may also indicate or signal applicable reconfiguration parameters.The reconfiguration parameters may correspond to, for example, but not limited to, one or more of: initial access, applicable PRACH resources, applicable SSB / RS opportunities, applicable SI periodicity, and applicable cells and associated availability status.

[0132] Based on the lack of detection of a presence indication, the WTRU implicitly assumes a certain availability state associated with the cell, carrier, TRP, or frequency band. For example, if no presence indication is detected at one or more presence indication occasions, the WTRU may determine an availability state associated with the cell (e.g., an "off" or "deep sleep" state). In another case, the WTRU may assume or change the availability state of the cell after multiple consecutive false detections or after a timer expires after no presence signal is detected. After the timer associated with the availability state expires, the WTRU may determine that the availability state is active or deactivated. In another case, the WTRU may implicitly determine the availability state based on 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). For situations where the WTRU does not detect a signal associated with an availability state with a signal strength above a threshold (e.g., a presence signal or SSB), the WTRU may assume that the availability state is not active and may assume a different availability state. The criterion may also be combined with the lack of detection of an identification sequence for a presence signal (e.g., detection of a PSS sequence).

[0133] The WTRU implicitly assumes a certain 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 hibernation state) for a configured subset of cells (e.g., capacity boosting cells) based on the time of day. For example, the WTRU may determine that a capacity boosting cell has an availability state indicated as "on" during certain hours of the day, an availability state indicated as "deep sleep" during other configured hours, and an availability state indicated as "off" during a third set of configured hours during the day or night. For example, the WTRU implicitly assumes a certain 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 example, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on the detection of a PSS signal or a simplified / stripped SSB signal. In another example, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on the detection of only a PSS signal. In another example, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on the detection of an RS signal (e.g., CSI-RS, PRS, TRS) or its lack thereof. In another example, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on the RRC state of the WTRU. The RRC state of the WTRU may be, for example, an idle state, an inactive state, or in a connected mode. In another example, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on whether a paging has been received, for example, but not limited to, within a configured time window. In another example, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band based on whether system information (e.g., periodic SI or a subset of SIBs) has been received, for example but not limited to within a configured time window.

[0134] In one or more cases, the WTRU may stop measuring (e.g., SSB and / or CSI-RS) when it determines that a cell is configured to be in an "off" or "deep sleep" state. In other cases, the WTRU may stop measuring when the WTRU determines that there are clearly configured measurement gaps. The WTRU may assume that some configured UL and DL resources are cleared or unavailable in certain availability states (e.g., "off", "dormant" or "deep sleep" states), including configured downlink allocations, configured uplink grants, PUSCH resources for semi-persistent CSI reporting, and / or measurement gaps. 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 of some availability states. In one or more cases, the WTRU determines to use coverage extension methods and / or resources (e.g., default initiation of RA with msg3 repetition, PUSCH repetition, selection of enhanced PUCCH coverage resources) based on the availability state and / or channel measurements of the cell (e.g., RSRP is less than a threshold).

[0135] In one or more cases, the WTRU may be configured to determine applicable transmission, reception and / or measurement resources based on the availability state. Based on the uplink or downlink resources or signals available in the active availability state, the WTRU may determine that the uplink or downlink resources or signals are applicable for transmission / reception and / or measurement for the determined network availability state. The WTRU may determine that a subset of measurement resource and / or signal (e.g., SSB, CSI-RS, TRS, PRS) opportunities are not applicable in certain availability states. Therefore, during the non-availability period, the WTRU may not measure reference signals on such measurement opportunities. For example, the WTRU may be configured so that a first set of RS or RS configurations (e.g., CSI-RS) is monitored during the non-availability period of the availability state. Additionally or alternatively, the WTRU may be configured so that a second set of RS or RS configurations (e.g., CSI-RS) is not monitored during the non-availability period 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 certain availability states. The WTRU may send some uplink signals (eg, SRS, pSRS, PRACH, UCI) in a subset of NW availability states.

[0136] In one or more cases, for a case where the WTRU determines that the network does not send an applicable signal on one or more measurement occasions for RLM measurements for a given RLM process, for example due to NES (e.g., during a non-availability period of an availability state), the WTRU may determine to prohibit the use of measurements corresponding to those skipped reference signal occasions for the purpose of determining Qin / Qout and determining synchronization / desynchronization. During the non-availability period of some availability states, the WTRU may not measure measurement resources and / or RLM occasions. In some cases, the WTRU may not change or increase related RLM counters and timers based on, for example, but not limited to, skipped measurements. In some cases, the WTRU may not change or increase measurement values / quantities during skipped measurement occasions (e.g., during a non-availability period of an availability state), including RLM, BFD, and CSI measurements. The WTRU may be configured with an alternative set of values ​​for RLM timers and / or counters (e.g., RLM periodic timer, RLM occurrence counter, RLM trigger number counter, RLM trigger time counter). In some cases, if a certain availability state is active, the WTRU may apply an alternative set of values ​​for RLM timers and / or counters.

[0137] In one or more cases, if the WTRU determines that the network does not send applicable reference signals at some occasions for the BFD process, such as due to NES (e.g., during a non-availability period of an availability state), the WTRU may determine to prohibit measuring measurement resources and / or occasions for determining BFI when applicable CSI-RS signals are not sent. The WTRU may not change or increase related BFD counters and timers based on, for example, skipped measurement opportunities. For the case where the BFI counter is above the configured threshold for triggering beam failure, the WTRU may wait or delay the triggering of BFR until a CSI-RS opportunity associated with an NW active state (i.e., an availability state) associated with NES (e.g., sleep or hibernation) occurs. In one or more cases, the WTRU may cancel the triggered BFR upon receiving a CSI-RS with a quality metric above a configured threshold. For example, upon receiving a CSI-RS with a quality metric above a configured threshold (such as Qin / RSRP>threshold), the WTRU cancels the triggered BFR. In one or more other cases, if the CSI-RS opportunity is associated with a certain availability state (e.g., NES mode or on), the WTRU may cancel the triggered BFR upon receiving a CSI-RS with a quality metric above a configured threshold (e.g., Qin / RSRP>threshold). The WTRU may be configured with an alternative set of values ​​for BFD timers and / or counters (e.g., BFD counter, BFD timer, etc.). In some cases, if a certain availability state is active, the WTRU may apply an alternative set of values ​​for BFD timers and / or counters.

[0138] In one or more cases, once the WTRU wakes up, the NW may indicate that a subset of past measurements or measurement opportunities are not valid. The WTRU may, in turn, retroactively correct the RLM or BFD accumulated metrics. The RLM or BFD accumulated metrics may be, for example, the number of BBIs, the number of desynchronizations, etc. In one or more cases, the WTRU may determine to remove one or more past measurements based on the WTRU receiving a measured NW signal (e.g., SSB, RS, or CSI-RS) with a considerable signal strength difference. If the WTRU identifies a sequence embedded within the SSB or CSI-RS, the WTRU may consider the measurement, otherwise the measurement opportunity may be skipped and considered not to have been sent due to the NES. For example, the WTRU may skip the measurement opportunity by not performing channel measurements on the SSB or CSI-RS opportunities.

[0139] 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 with or are within a configured time period of SSB or RS opportunities of an active SSB / RS pattern or an availability period of an availability state. The WTRU may assume multiple silent patterns / resource periodicities based on the active SSB periodicity and active availability state from the configured patterns / periodicities.

[0140] 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 the configured SSB and / or CSI-RS are not sent by the gNB for the serving cell. In another example, the WTRU determines that the presence indication is sent by a cell in such an availability state. In another example, the WTRU determines that SI and PBCH signaling may not be sent by a cell in such an availability state. For example, the WTRU may send a subset of SI or SIBs.

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

[0142] 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 a cell in an availability state including "off", "dormant" or "deep sleep". A WTRU in RRC_IDLE or in RRC_INACTIVE may stop monitoring SI change indications in the paging occasions of the WTRU in the DRX cycle consistent with the availability state of the cell in the "off", "dormant" or "deep sleep" state. When the cell is in certain availability states (e.g., off, dormant, or deep sleep state), the WTRU may extend the modification period related to the SI change indication. In some cases, in such availability states (e.g., "off", "dormant", or "deep sleep"), the WTRU may not perform RLM or RLF procedures on such cells. In some cases, the WTRU may suspend beam failure detection for some cells in some availability states (e.g., "off", "dormant", or "deep sleep" state).

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

[0144] The WTRU may be configured with multiple values ​​for the field ssb-periodicityServingCell. These values ​​may be configured, for example, using RMSI, secondary SIB, in broadcast signaling, and the like. 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 periods, switching to different availability states, and / or activating or deactivating certain availability states. Upon receiving such a command, the WTRU may assume different periodicities for the SSB and associated RACH resources. For example, the WTRU may assume different periodicities for the SSB and associated RACH resources based on receiving a command such as, but not limited to, an SSB periodicity change command or a command associated with changing an availability state.

[0145] In one or more cases, for the case where the WTRU is configured to be in idle mode, the WTRU may determine whether SSB or RS periodicity and / or SSB or RS opportunity is lost (i.e., whether the SSB or RS opportunity is sent from the gNB) based on past measurements. For example, the WTRU may determine that the SSB or RS is not sent based on measuring a current measurement in a net opportunity, the current measurement being different from X past measurements (or a moving average of past measurements), the X past measurements having a difference greater than a predetermined or configured value. X may be predetermined or configured. 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.

[0146] In one or more cases, for the case where the WTRU is configured to be 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 based on one or more of: a) the difference or comparison between the current RS measurement opportunity and multiple past measurements, b) the overall signal quality of the cell (e.g., based on L3 RSRP or presence signal measurements), c) the active availability state, and d) the mobility state of the WTRU. The WTRU may ignore measurements of RS occasions that are not sent in the active RS pattern (e.g., during non-availability periods of the availability state). The WTRU may send a wake-up request or assistance information to request a change in RS periodicity / pattern. The gNB may signal the change in RS or SSB pattern / period in an indication (e.g., MAC CE, DCI, etc.).

[0147] In one or more cases, the WTRU may use RACH opportunities associated with the activity periodicity and / or CSI-RS pattern of the SBS. For example, the WTRU may use RACH opportunities associated with the activity periodicity and / or CSI-RS pattern of the SSB, such as PRACH opportunities that are aligned with the transmitted SSB, immediately following the transmitted SSB, or transmitted within a time window from the SSB reception. The WTRU may assume that the remaining PRACH opportunities are unavailable. The WTRU may be configured with a PRACH opportunity mask associated with one or more SSB patterns or CSI-RS patterns. The WTRU may activate the PRACH opportunity mask based on the active SSB or RS pattern. For example, the WTRU may activate the PRACH opportunity mask based on the receipt of a switching 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 the transmitted SSB opportunities (or within a period starting from the last transmitted SSB) are valid. In one or more cases, the WTRU may not send msg1 on an invalid RO.

[0148] In one or more cases, the WTRU monitors for paging from a cell. For example, if a cell is in a certain availability state (e.g., on or asleep), the WTRU may be configured to monitor for paging from the cell. The WTRU may skip waking up on DRX cycles of the cell that coincide with the cell being in other availability states (e.g., off, deep sleep, or dormant). In some cases, the WTRU may monitor for gNB wake-up signaling associated with DRX or paging (e.g., DCP) in a subset of the availability states (e.g., on or asleep) of the cell.

[0149] In one or more cases, the WTRU may be configured to send a Tracking Area Update (TAU) on a subset of cells that are in certain availability states. For example, the WTRU sends a TAU on a subset of cells (e.g., macro cells) based on the availability state. In some cases, the WTRU may avoid sending a TAU on a capacity boost cell and / or a cell with a determined availability state that is configured, for example, in an off, dormant, or sleeping state.

[0150] 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 shutdown indication or a sleep signal. In some cases, the WTRU may receive a shutdown indication or a sleep signal in a subset of RRC states. In one or more cases, the WTRU may perform mobility procedures in connected mode after receiving a shutdown indication. The WTRU may perform cell reselection, initial access and / or RRC reconstruction based on the WTRU being configured to be in an inactive or idle mode. If the WTRU is configured to be in a connected state or an inactive state, the WTRU switches to idle mode after receiving a shutdown indication.

[0151] In the event that the current serving cell or capacity enhancement cell is turned off or a certain condition is met, the WTRU may be configured or predefined with an alternative serving cell to perform initial access, mobility or cell reselection. The WTRU may be configured according to each broadcast or dedicated signaling with a list of fallback or alternative serving cells. In one example, the WTRU may be configured according to each broadcast or dedicated signaling with a list of fallback or alternative serving cells, according to each serving cell or according to each gNB. For example, the WTRU initiates a cell reselection or mobility process to an alternative serving cell associated with the cell or gNB from which the shutdown indication is received. In one example, the shutdown or sleep indication may dynamically indicate to the WTRU which cell to fall back or connect to, for example, through dedicated or broadcast signaling. In another example, the fallback cell may be predefined as a master node cell based on the WTRU being configured to be in dual connectivity. The fallback / alternative cell may be configured or predefined as a cell associated with a different RAT or frequency band. For example, the WTRU may fall back to an LTE or FR1 cell associated with the cell or gNB from which the shutdown indication is received. For example, based on whether the WTRU is in CA or DC using multiple RATs or multiple frequency bands, the WTRU may fall back to the LTE or FR1 cell associated with the cell or gNB from which the shutdown indication was received.

[0152] In one or more cases, the WTRU may perform initial access / RA, mobility and / or start related measurements on an alternative cell or capacity enhancement cell based on satisfying one or more of the following conditions: (a) the latency associated with the arrival of new data, BSR or buffered data is strict (e.g., below or above a threshold); (b) the data associated with the arrival of new data, BSR or buffered data includes data from one or more "NES" RBs or LCHs (based on RB id), including the condition that all data comes from configured NESDRBs / SRBs; (c) the amount of buffered data or buffered data from NES RBs is greater than or less than a configured threshold; (d) one or more conditional switching conditions are met; (e) the WTRU is configured to be in a certain RRC state (e.g., idle state, inactive state or connected mode); (f) measured channel conditions associated with the alternative cell and / or best or serving cell; and (g) indicated or measured cell resource load (utilization) metrics associated with the alternative cell and / or best serving cell.

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

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

[0155] 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 based on an availability state associated with the gNB. For example, the WTRU may determine that the gNB is operating with a single sector in an energy-saving availability state (e.g., sleep, hibernate, or off state). If the gNB is in another availability state (e.g., on or micro-sleep state), the WTRU may determine that the gNB is operating with a different number of active cells / PCIs or multiple cells that are part of the same gNB.

[0156] In one or more cases, the WTRU may be configured to monitor for indications that may characterize a level of network activity (e.g., an availability status). In one example, network activity may be associated with a gNB and / or cell. The WTRU may assume the same availability status for all cells that are part of the same gNB (e.g., cells of the same MAC entity). A network activity indication (e.g., a presence indication) may include a channel (e.g., a 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 associated gNB and / or cell. In some cases, the activity indication may include activity information for other gNBs / cells.

[0157] In one or more cases, the activity indication may be a PDCCH containing group common signaling. For example, the NW may send a group common DCI to a group of WTRUs (e.g., WTRUs in a serving cell) to indicate 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 WTRU may be configured with at least one search space associated with a monitoring opportunity for the activity indication PDCCH.

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

[0159] In another example, for each activity level (e.g., availability state), the signaling or activity indication within the PDCCH may include defined transmission and reception attributes. For example, during a period of reduced activity, it may not be desirable for the WTRU to monitor certain PDCCH search spaces (including, for example, one, multiple, or all SSs), receive certain types of PDSCH (including, for example, one, multiple, or all PDSCHs), send 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) based on the availability state associated with the activated carrier. For example, the WTRU may stop monitoring the PDCCH for cross-carrier scheduling based on the availability state that is changed or activated on such carrier. In another example, the WTRU may stop monitoring the PDCCH for cross-carrier scheduling based on the availability state that is changed or activated on such carrier, while the WTRU monitors the PDCCH from another carrier (e.g., on or not in the NES state).

[0160] In another example, the signaling or activity indication within the PDCCH may contain a set of configurations that may be associated with the activity level and used / applied when indicating the activity level. For example, the configuration set may include SS configurations, CSI report configurations, indices of SBSs transmitted, etc. In one or more cases, each configuration set may have attributes associated with the activity level. For example, an attribute such as a label may be set to "reduced activity".

[0161] In another example, the signaling or activity indication within the PDCCH may include a time interval over which the activity level is assumed. In such a case, the WTRU may signal the time interval over which the activity level is assumed in a portion of the PDCCH or activity indication. In some cases, a bitmap may be used to indicate the time interval, wherein each bit in the bitmap may be associated with a specific duration (e.g., a time slot or frame). For example, a bit "1" may indicate regular activity. In another example, a bit "0" may indicate reduced activity on the associated frame. In some other cases, the time interval may be indicated by the start time and 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.

[0162] In another example, the signaling or activity indication within the PDCCH may include a predetermined time interval over which the activity level is assumed.

[0163] In one or more cases, the indication may include a go to sleep signal, such as a predefined sequence. For example, when the WTRU detects the go to sleep signal, the WTRU may expect a reduced activity level for a specific duration. In one or more cases, the WTRU may activate C-DRX for the indicated time period. Alternatively, in another example, two sequences may be used to indicate normal activity and reduced activity.

[0164] In one or more cases, the WTRU may be configured to send a "leave indication" signal before or when the cell is reselected to a new cell. The "leave indication" signal may have the same structure as the "connection request" signal. The "connection 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 a higher layer notified by a signal. For example, the WTRU may receive: RRC signaling (e.g., system information or RRC connection release) indicating whether to send a "leave indication" signal before or when the cell is reselected; and a configuration of parameters for generating the signal. Based on the structure of the signal, the generated parameters may include, for example, a scrambling identifier or a base sequence.

[0165] In one or more cases, the parameter configuration of the "Leave Indication" signal may depend on the identity of the serving cell before the cell reselection. In one or more other cases, the parameter configuration of the "Leave Indication" signal may depend on the identity of the serving cell after the cell reselection. In the latter case, the "Leave Indication" signal may correspond to the "New Cell Indication" signal.

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

[0167] In other cases, the WTRU may be configured to initiate an RRC connection request to the new cell after reselection, which may have a new cause indication. The RRC connection request may be signaled by the RRC (e.g., system information or RRC connection release). The RRC may be indicated separately for each source serving cell (e.g., before cell reselection). The RRC may be indicated separately for each target serving cell (e.g., after cell reselection). The RRC may be indicated separately for each pair of source serving cell and target serving cell (e.g., for cell reselection from a specific source cell to a specific target cell). In one or more cases, the sending of a "leave indication" or "new cell indication" signal by a WTRU in idle mode may determine when a cell may be shut down. For example, the sending of a "leave indication" or "new cell indication" signal by a WTRU in idle mode may determine that a cell may be shut down when there are no or few WTRUs camping on the cell.

[0168] 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 to be in a power saving state.

[0169] In one or more cases, the WTRU may be configured, predefined, or instructed to shut down the NUL uplink carrier. In one or more cases, the WTRU may be configured, predefined, or instructed to rely on the SUL being in one or more availability states. For example, the WTRU may deactivate the NUL carrier and / or the UL carrier.

[0170] In some cases, the WTRU may be configured, predefined or instructed 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 instructed to rely on the PCell based on the associated serving gNB configured in one or more availability states. For example, if the gNB is in a certain availability state, the WTRU deactivates the SCell. For example, if the associated cell is turned off or configured to be in a power saving state, the WTRU deactivates the SCell if the gNB is in a certain availability state.

[0171] In some cases, the WTRU may be configured, predefined, or indicated to switch the WTRU's active UL and / or DL ​​bandwidth portion to an initial BWP or a default BWP. For example, if the associated serving cell is configured to be in one or more availability states, the WTRU switches the WTRU's active UL and / or DL ​​bandwidth portion to the initial BWP or the default BWP. For example, if the gNB is in a certain availability state, the WTRU deactivates the SCell. For example, if the associated cell is turned off or configured to be in an energy saving state, the WTRU deactivates the SCell. In one or more cases, the WTRU may be configured with a specific NW energy saving BWP. In some cases, the WTRU may be configured with a specific NW energy saving BWP (e.g., NES BWP). In some cases, based on the availability state, the WTRU may be configured with a specific NW energy saving BWP (e.g., NES BWP). In some cases, the WTRU may switch to the NW energy saving BWP based on the associated cell being in (or determined to be in) a certain availability state (e.g., "off", "sleep", and other similar states). In some cases, the WTRU may be configured to switch the WTRU's active UL and / or DL ​​active BWP to the NW Energy Saving BWP. For example, if the WTRU does not receive an availability signal in the current BWP, the WTRU switches the WTRU's active UL and / or DL ​​active BWP to the NW Energy Saving BWP. In some cases, if the WTRU does not receive an availability signal in the current BWP after multiple false detections, the WTRU switches the WTRU's active UL and / or DL ​​active BWP to the NW Energy Saving BWP. In some cases, if the WTRU does not receive an availability signal in the current BWP after a timer expires, the WTRU switches the WTRU's active UL and / or DL ​​active BWP to the NW Energy Saving BWP. For example, the WTRU may receive an indication (e.g., common L1 signaling or DCI or L2 signaling, such as MAC CE) that indicates a switch to the NES BWP based on the reception of a common cell signal or the lack of a common cell signal. The WTRU may send HARQ feedback or an acknowledgement of the receipt of the NES BWP switch command / indication. The WTRU may switch to the NES BWP after sending such feedback and / or upon receiving a second confirmation DL signal on the existing active BWP. In another example, if no DL signal is detected, the WTRU may implicitly switch to another BWP (e.g., NES BWP). In another example, if no DL signal is detected for a period of time and / or based on measured channel conditions, the WTRU may implicitly switch to another BWP (e.g., NES BWP). In another example, if the DL signal does not include measured channel conditions above a threshold, the WTRU may implicitly switch to another BWP (e.g., NES BWP).In another example, the WTRU may implicitly switch to another BWP (e.g., NES BWP) if no DL signal is detected for a period of time and / or based on measured channel conditions (e.g., the DL signal does not include measured channel conditions above a threshold). The WTRU may switch to the NES BWP upon expiration of the BWP inactivity timer or another NES BWP inactivity timer. Upon receiving a DL signal associated with the availability status / NES status of the gNB, the BWP inactivity timer or another NES BWP inactivity timer may be reset.

[0172] In one or more cases, a presence indication associated with a cell may indicate which carriers are activated. In some cases, the WTRU may start measuring resources (e.g., CSI resources or channel quality) upon receiving a presence indication associated with a carrier. The WTRU may activate a Scell ​​upon receiving a presence indication associated with the Scell ​​or an associated gNB. If the WTRU does not receive a presence indication associated with an SCell or an associated gNB, the WTRU may deactivate the carrier or SCell. In some cases, if no presence indication associated with an SCell or an associated gNB is received after a number of failed receptions of detected presence indications or after a timer (e.g., a Scell ​​deactivation timer) has expired, the WTRU may deactivate the carrier or SCell.

[0173] In one or more cases, the WTRU may be configured to receive signaling from the network to deactivate a cell, a carrier, and / or a BWP on a frequency band or carrier. For example, the WTRU may shut down or deactivate a cell on the FR2 frequency band. In some examples, if the WTRU receives a shutdown indication to shut down or deactivate a cell on the FR2 frequency band, the WTRU may shut down or deactivate the cell on the FR2 frequency band. In some examples, if the WTRU does not detect a presence indication associated with the FR2 frequency band, the WTRU may shut down or deactivate the cell on the frequency band. In other examples, if the WTRU determines that the cell is in a certain availability state (e.g., a shut down or dormant state), the WTRU may shut down or deactivate a cell on a carrier or frequency band.

[0174] In one or more cases, the WTRU may be configured to provide auxiliary information requesting a change / modification of the gNB availability status and / or spatial resource allocation. The spatial resources may include, for example, but not limited to, TRP, 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 the SSB measurement (e.g., SS-RSRP, SS-RSRPB, SS-RSRQ, SS-SINR, etc.) drops below a certain threshold, the WTRU indicates that an additional SSB beam is needed from the gNB. SSB measurements that drop below a certain threshold may indicate low 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. For example, the new SSB beam may be a wide beam and / or a narrow beam.

[0175] In some cases, the gNB may utilize periodic or aperiodic CSI reports from the WTRU to assist in selecting the set of beams to activate. In some cases, the gNB may utilize periodic or aperiodic CSI reports from the WTRU to assist in selecting which beams the gNB may switch off. In some cases, the gNB may switch off beams that are not useful from a WTRU coverage perspective.

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

[0177] In one or more cases, if CSI-RS related measurements (e.g., RSRP, RSRQ, SINR, etc.) are below a certain threshold, the WTRU may indicate that an additional number of antennas, ports, beams, etc. are needed. For cases where CSI-RS related measurements are below a certain threshold, the TRP configuration at the gNB may be suboptimal. In another example, the WTRU may indicate a preference for a certain set of spatial resources, such as but not limited to ports, beams, and TRPs (i.e., in the case where multiple TRPs are associated with the 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 example, if the measurement for a certain "k"bset "k" of resources is above a threshold (i.e., "k" is the strongest resource "o"t among "n" resources), the WTRU may indicate a preference for this subset of resources. In one or more cases, the gNB may modify the gNB availability state using the indicated preference. For example, the gNB may modify the gNB availability state using the indicated preference by shutting down the spatial resources below the threshold.

[0178] In one or more cases, if the reference signal measurement (e.g., RSRP, RSRQ, etc.) is above a certain threshold but below another threshold, the WTRU may indicate the need for a change in the gNB availability state and / or a change in the spatial resource allocation. For example, if the serving cell is above a threshold (e.g., an Event A1 threshold, which does not trigger a mobility procedure), 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 combination with information about the network availability state and / or the WTRU's cell / TRP presence indication information. In one or more cases, the WTRU may signal an indication to the gNB to request a change in additional spatial resources or to request additional spatial resources.

[0179] In one or more cases, the WTRU may request additional spatial resource allocations or changes in spatial resource allocations based on the quality of the WTRU's CSI report. In some cases, this indication may be triggered based on poor CQI and / or rank measurements.

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

[0181] In one or more cases, if there is a change in the status of buffered data at the WTRU, the WTRU may request a change in the spatial resource allocation of the gNB. In some cases, this change in the spatial resource allocation of the gNB may be an increase in buffered data. For example, the increase in buffered data may indicate an insufficient consumption rate of buffered data. In some cases, this change in the spatial resource allocation of the gNB 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 service being served, the amount of data, the number of activities of the LCG, etc.

[0182] 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 saving via one or more of antenna / port muting, adaptive sectorization, and selective SSB adjustment (e.g., wider beamwidth or reduced number of beams) when appropriate (e.g., in low-load scenarios). Optimizing network-side power consumption by including prioritizing macro TRP energy saving may result in the greatest network-side savings (i.e., in terms of PA and BB power consumption). In other examples, it may be beneficial to have more cell / TRP activity. For example, in high-load scenarios where the macro TRP is required to be in a full availability state, it may be beneficial to have multiple small cells also in a full availability state. Specifically, if the small cell is a NR micro-deployment operating in a dense urban deployment, it may be beneficial to have multiple small cells in a full availability state. In such scenarios, the increased capacity of multiple small cells may result in faster transmissions, allowing more sleep time, and thereby reducing network-side power consumption.

[0183] Figure 4A 4 is a diagram illustrating an example structure of SSB transmission of an anchor cell and a non-anchor cell. An anchor cell 432 may be in an active state. An anchor cell 432 may be configured to transmit a discovery signal (e.g., SSB transmission, SIB transmission, RS transmission, etc.) at a periodic interval. A non-anchor cell 434 may be in a low availability state (e.g., "off", "deep sleep", or "micro sleep" availability state). The non-anchor cell 434 may be configured to transmit a discovery signal (e.g., SSB transmission, SIB transmission, RS transmission, etc.) at a periodic interval that is less than (e.g., slower than) that of the anchor cell.

[0184] Figure 4B An example diagram is illustrated illustrating WTRU assistance information sent based on detection of a presence indication. Figure 4BA WTRU process 400 is illustrated for a connection request for a cell configured with a presence indication. Although illustrated with steps 403 to 422, in some examples, the process 400 may include only sub-steps of steps 430 to 422 (e.g., one or more of steps 403 to 422 may be omitted). In one example, the WTRU 404 accesses resources in a cell, a gNB (such as gNB 402), or a TRP with a presence indication. For example, at 403, the WTRU 404 determines that a non-anchor cell (e.g., non-anchor cell 434) may be configured to be in a DTX state. In order to access the resources, the WTRU 404 may be configured with a monitoring opportunity to detect a presence indication associated with a cell, a TRP, or a carrier. Thus, at 406, the WTRU 404 monitors for a discovery signal and / or a presence indication from another cell (e.g., anchor cell 432). In some cases, the carrier may be associated with a different cell. In some cases, the presence indication may be a DL signal, such as, but not limited to, a stripped 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 an RRC message. In some cases, the L2 message may come from a different cell or TRP. In one or more cases, at 406, the WTRU 404 may be configured to monitor a discovery signal and / or a presence indication associated with another cell (such as an anchor cell, such as the gNB 402). At 408a, the gNB 402 may monitor the presence indication information. For example, the gNB 402 may monitor the presence signal / information sent from the anchor cell. The presence indication (i.e., the presence signal) may be, for example, but not limited to, an SSB, a 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, a SpCell, a PCell, a primary SCell, etc. The UL availability window 410a (and UL availability window 410b) may correspond to a time period during which the presence of signal or information reception is detected and / or a time period after the WTRU transmits 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 a configured UL channel resource on a non-anchor cell that transmits the wake-up request. 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, for example, an availability state associated with gNB sleep.In one or more cases, for the case where the measured channel condition is less than a threshold (e.g., RSRP) and / or in the case where the SBS associated with the non-anchor cell or the anchor cell is not detected, the WTRU triggers the sending of a wake-up request or information at 414. In one example, if the channel condition measured by the WTRU is less than a threshold, the SSB associated with the non-anchor cell or the anchor cell may not be detected.

[0185] In one or more cases, the gNB 402 may be configured to be in a sleep or off state. For example, at 416, the WTRU 404 may be configured to monitor a presence indication associated with the sleep / off gNB 402 after conditions for sending an on request and / or assistance information are met. The assistance information may correspond to information such as data arrival, lack of authorization, poor coverage, high load, etc. In one or more cases, the WTRU 404 is configured to successfully receive a presence indication, such as the 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 cases, 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 send one or more of an on request, WTRU assistance information, or initiate a random access (RA) procedure (e.g., a RACH or PRACH procedure) after successfully detecting a presence signal. The WTRU may send one or more of an attach request, WTRU assistance information, or a RA within the UL availability window 410b after detection. The WTRU may send a RA to initiate a RA on a non-anchor cell, for example.

[0186] At 419, the gNB 402 may send an SSB on a non-anchor cell (e.g., non-anchor cell 434). At 420, the gNB 402 may send additional RS, SSB, Msg4, and / or CSI-RS resources. In one or more cases, at 420, the gNB 402 may send additional RS, SSB, Msg4, and / or CSI-RS resources in response to receiving the auxiliary information and / or the connection request. In one or more cases, the WTRU is configured to monitor the additional RS, SSB, Msg4, and / or CSI-RS resources after sending the connection request or receiving a response to the connection request. In one or more cases, at 422, the WTRU is configured to change the availability state of the cell (e.g., to an "on" or "micro-sleep" state). For example, the WTRU is configured to change the availability state of the non-anchor cell. The WTRU may change the availability state of the cell, for example, after successfully receiving a response to the sent connection request from the requested cell.

[0187] Although features and elements are described above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (sent via a wired or wireless connection) 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 built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: monitoring a second cell for a presence indication signal, the presence indication signal indicating that the first cell is in a low availability state; determining to send 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 less than a threshold, wherein the wake-up signal is sent before expiration of a predetermined time period after receiving the presence indication signal via the second cell; sending the wake-up signal; After sending the wake-up signal, monitoring the transmission of the SSB of the first cell; After sending the wake-up signal, receiving information indicating that the first cell has transitioned to an active state; as well as After receiving the information indicating that the first cell has transitioned to the active state, data is sent via the first cell.

2. The method according to claim 1, further comprising: A discontinuous transmission (DTX) mode for transmitting signals to the first cell is determined based on the presence indication signal received in the second cell.

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

4. The method according to claim 1, further comprising: After expiration of the predetermined time period after receiving the presence indication signal via the second cell, it is determined that the first cell has returned to the low availability state.

5. The method of claim 1 , wherein the predetermined time period comprises an uplink availability window, and wherein 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. The method according to claim 1, further comprising: A beam failure detection (BFD) measurement, a radio link monitoring (RLM) measurement, or a channel state information (CSI) measurement on the second cell is adjusted according to an availability status of the second cell.

8. The method according to claim 1, further comprising: The SSB mode of the second cell is determined based on whether the second cell is in the low availability state or in the active state.

9. A wireless transmit / receive unit (WTRU), comprising: A processor, the processor being configured to: monitoring a second cell for a presence indication signal, the presence indication signal indicating that the first cell is in a low availability state; determining to send 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 less than a threshold, wherein the wake-up signal is sent before expiration of a predetermined time period after receiving the presence indication signal via the second cell; sending the wake-up signal; After sending the wake-up signal, monitoring the transmission of the SSB of the first cell; After sending the wake-up signal, receiving information indicating that the first cell has transitioned to an active state; as well as After receiving the information indicating that the first cell has transitioned to the active state, data is sent via the first cell.

10. The WTRU of claim 9, wherein the processor is further configured to: A discontinuous transmission (DTX) mode for transmitting signals to the first cell is determined based on the presence indication signal received in the second cell.

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

12. The WTRU of claim 9, wherein the processor is further configured to: After expiration of the predetermined time period after receiving the presence indication signal via the second cell, it is determined that the first cell has returned to the low availability state.

13. The WTRU of claim 9, wherein the predetermined time period comprises an uplink availability window, and wherein 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 WTRU of claim 9, wherein the processor is further configured to: A beam failure detection (BFD) measurement, a radio link monitoring (RLM) measurement, or a channel state information (CSI) measurement on the second cell is adjusted according to an availability status of the second cell.

16. The WTRU of claim 9, wherein the processor is further configured to: The SSB mode of the second cell is determined based on whether the second cell is in the low availability state or in the active state.

Images