Wireless transmitting / receiving unit and method performed by same

Abstract

The present disclosure relates to a wireless transmit / receive unit and a method performed by the same. Particular implementations include monitoring a presence indication signal in a 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] This divisional application is a divisional application of the application with the filing date of April 3, 2023, application number 202380038217.9, and invention title "Discontinuous Network Access".

[0002] Cross - reference to related applications

[0003] This application claims the priority of 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, and the entire contents of these U.S. Provisional Applications are incorporated herein by reference. Background art

[0004] Network energy consumption can be quite significant or unnecessary under low cell loads. Thus, the network can turn off frequent periodic transmissions (e.g., synchronization signal block 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 a sudden increase in the demand for wireless transmit / receive units (WTRUs) for network access. Summary of the invention

[0005] The present disclosure relates to devices, methods, and systems for discontinuous network access. In one or more specific embodiments, when a non - anchor cell is in a network energy saving (NES) state, a WTRU monitors discovery signals and presence information in an 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 transmissions 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 embodiments, 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), media access control (MAC) control element (MAC CE), or paging. In one or more specific embodiments, 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 a cell according to the active availability state of the cell. In one or more specific embodiments, when receiving a group - common indication, the WTRU switches the active bandwidth part (BWP) to a group - common BWP configured for NES. In one or more specific embodiments, the WTRU includes one or more of the following NES WTRU - assisted information: cell index for which a state change is requested, desired availability state, and request for SSB on demand.

[0006] In one or more embodiments, a WTRU may access resources in a cell, gNB, or transmit / receive point (TRP) with a presence indication. In one or more embodiments, a WTRU may monitor a presence indication associated with a sleeping / shutdown gNB. In one or more embodiments, a WTRU may receive a presence indication. In one or more cases, a WTRU may assume an availability state associated with a cell (e.g., "off" or "deep sleep"). In one or more cases, a WTRU may send an access request, WTRU assistance information, or random access (RA) after successfully detecting a presence signal. In one or more embodiments, a WTRU may monitor additional synchronization signal blocks (SSBs) and / or CSI-RS resources after sending an access request or receiving a response to the access request. In one or more embodiments, a WTRU may change the availability state of a cell after successfully receiving a response to the sent or access request from the requested cell.

[0007] Devices, methods, and systems for discontinuous network access may include SSB and CSI-RS adjustment. In one or more embodiments, 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 an impact on synchronization, initial access procedures, BFD, and random access channel (RACH) based on discontinuous network transmissions of common signals. In one or more cases, the devices, methods, and systems discussed herein may be used such that a WTRU knows whether to measure MO. In one or more cases, the devices, methods, and systems discussed herein may be used such that a WTRU knows whether a common cell signal (e.g., synchronization or reference signal) is being transmitted as normal rather than not receiving the common cell signal 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 a cell in an NES state (including RLM and BFD). In one or more cases, the devices, methods, and systems discussed herein may be used such that a WTRU determines which resources are applicable for data, control, or measurement based on the availability state. In one or more cases, the devices, methods, and systems discussed herein may be used to determine initial access on an alternative cell.

[0008] This document provides a method for discontinuous network access. In one or more specific embodiments, the method includes monitoring a presence indication signal in a second cell. In one example, the presence indication signal indicates that a first cell is in a low availability state. In one or more specific embodiments, the method includes 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 measurements 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 a predetermined period expires after receiving the presence indication signal via the second cell. In one or more specific embodiments, the method includes sending the wake-up signal. In one or more specific embodiments, the method includes monitoring the transmission of the SSB of the first cell after sending the wake-up signal. In one or more specific embodiments, 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 embodiments, the method includes sending data via the first cell after receiving the information indicating that the first cell has transitioned to an active state.

[0009] This document provides a wireless transmit / receive unit (WTRU) for discontinuous network access. In one or more specific embodiments, the WTRU includes a processor. In one or more specific embodiments, the processor is configured to monitor a presence indication signal in a second cell. In one example, the presence indication signal indicates that a first cell is in a low availability state. In one or more specific embodiments, the processor is configured to determine to send a wake-up signal for the first cell based on detecting the presence indication signal in the second cell and based on measurements 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 a predetermined period expires after receiving the presence indication signal via the second cell. In one or more specific embodiments, the processor is configured to send the wake-up signal. In one or more specific embodiments, 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 embodiments, the processor is configured to, after sending the wake-up signal, receive information indicating that the first cell has transitioned to an active state. In one or more specific embodiments, the processor is configured to send data via the first cell after receiving the information indicating that the first cell has transitioned to an active state. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] A more detailed understanding can be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate like elements.

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

[0012] Figure 1B is a system diagram showing an exemplary wireless transmit / receive unit (WTRU) that can be used within the Figure 1A illustrated communication system.

[0013] Figure 1C is a system diagram showing an exemplary radio access network (RAN) and an exemplary core network (CN) that can be used within the Figure 1A illustrated communication system.

[0014] Figure 1D is a system diagram showing another exemplary RAN and another exemplary CN that can be used within the Figure 1A illustrated communication system.

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

[0016] Figure 3 is an illustration of an example beam sweep.

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

[0018] Figure 4B is a diagram showing an example aspect of the present disclosure that can be implemented. Detailed Description

[0019] Figure 1A is a diagram illustrating an example communication system 100 in which one or more of the disclosed embodiments can be implemented. The communication system 100 can be a multi-access system that provides content such as voice, data, video, messages, broadcasts, etc. to a plurality of wireless users. The communication system 100 can enable the plurality of wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communication system 100 can 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.

[0020] As Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104 / 113, a core network (CN) 106 / 115, a public switched telephone network (PSTN) 108, the 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 transmit 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 computer, 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, a medical device and application (e.g., remote surgery), an industrial device and application (e.g., robots and / or other wireless devices operating in an industrial and / or automated processing chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs in the UE 102a, 102b, 102c, and 102d may be interchangeably referred to as a WTRU.

[0021] The communication system 100 may further include base stations 114a and / or base stations 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be transceiver base stations (BTSs), Node Bs, evolved Node Bs, Home Node Bs, Home evolved Node Bs, gNBs, NR Node Bs, site controllers, access points (APs), wireless routers, etc. Although the base stations 114a, 114b are each depicted as a single element, it should be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

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

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

[0024] More specifically, as noted above, 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, base station 114a in RAN 104 / 113 and 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 air interfaces 115 / 116 / 117. WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

[0025] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as evolved UMTS terrestrial radio access (E-UTRA), which may use Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-A Pro to establish the air interface 116.

[0026] 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 use New Radio (NR) to establish the air interface 116.

[0027] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together using, for example, 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 to / from multiple types of base stations (e.g., eNBs and gNBs).

[0028] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., 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 Rate for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0029] Figure 1AThe base station 114b therein may be, for example, a wireless router, a home Node B, a home evolved Node B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area such as a commercial premise, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for drones), a road, etc. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In 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 pico cell or a femto cell. As Figure 1A shown, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106 / 115.

[0030] The RAN 104 / 113 may communicate 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, location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although not shown in Figure 1A it should be understood that the RAN 104 / 113 and / or the CN 106 / 115 may communicate directly or indirectly with other RANs employing the same RAT or a different RAT as the RAN 104 / 113. For example, in addition to being connected to the RAN 104 / 113 that may utilize NR radio technology, the CN 106 / 115 may also communicate with another RAN (not shown) employing GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0031] CN 106 / 115 can also be used as a gateway for WTRU 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 Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) in the TCP / IP Internet protocol suite. The network 112 may include a wired communication network and / or a wireless communication network owned and / or operated by other service providers. For example, the network 112 may include another CN connected to one or more RANs, and the one or more RANs may employ the same RAT or a different RAT as the RAN 104 / 113.

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

[0033] Figure 1B is a system diagram illustrating an example WTRU 102. As Figure 1B shown, the WTRU 102 may include elements such as a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, a non-removable memory 130, a removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138. It should be understood that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0034] The processor 118 can be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 can 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 can be coupled to a transceiver 120, which can be coupled to a transmit / receive element 122. Although Figure 1B the processor 118 and the transceiver 120 are depicted as separate components, it should be understood that the processor 118 and the transceiver 120 can be integrated together in an electronic package or chip.

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

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

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

[0038] The processor 118 of the WTRU 102 may be coupled to the speaker / microphone 124, keypad 126, and / or the 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, keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from any type of suitable memory (such as non-removable memory 130 and / or removable memory 132) and store data in any type of suitable memory. The non-removable memory 130 may include random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In other embodiments, the processor 118 may access information from a memory that is not physically located on the WTRU 102 (such as on a server or a home computer (not shown)) and store data in that memory.

[0039] The processor 118 may receive power from a 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 battery packs (e.g., nickel cadmium (NiCd), nickel zinc (NiZn), nickel metal hydride (NiMH), lithium ion (Li-ion), etc.), a solar cell, a fuel cell, etc.

[0040] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or instead of the information from the GPS chipset 136, the WTRU 102 may receive location information via an air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of signals received from two or more nearby base stations. It should be understood that the WTRU 102 may obtain location information by any suitable location determination method while remaining consistent with the embodiments.

[0041] The processor 118 may also be coupled to other peripheral devices 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 peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, Bluetooth® Modules, FM radio units, digital music players, media players, video game player modules, Internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. The peripheral device 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geographical location sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0042] The WTRU 102 may include a full-duplex radio, for which the 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, which is used to reduce and / or substantially eliminate self-interference through signal processing via hardware (e.g., chokes) 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 the 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)).

[0043] Figure 1C FIG. is an illustration of a system diagram of the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ E-UTRA radio technology to communicate with the WTRU 102a, 102b, 102c via the air interface 116. The RAN 104 may also communicate with the CN 106.

[0044] The RAN 104 may include evolved Node Bs 160a, 160b, 160c, but it should be understood that the RAN 104 may include any number of evolved Node Bs while remaining consistent with the embodiment. Each of the evolved Node Bs 160a, 160b, 160c may include one or more transceivers for communicating with the WTRU 102a, 102b, 102c via 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.

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

[0046] Figure 1C The CN 106 shown may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. Although each of the foregoing elements is depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0047] The MME 162 may be connected via the S1 interface to each of the evolved Node Bs 162a, 162b, 162c in the RAN 104 and may act 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 specific serving gateway during the initial attachment of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide control plane functions for exchanges between the RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0048] The SGW 164 may be connected via the S1 interface to each of the evolved Node Bs 160a, 160b, 160c in the RAN 104. 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 handover between evolved Node Bs, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, etc.

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

[0050] CN 106 can facilitate communication with other networks. For example, CN 106 can provide the WTRUs 102a, 102b, 102c with access to a circuit-switched network, such as the PSTN 108, to facilitate communication between the WTRUs 102a, 102b, 102c and traditional landline communication devices. For example, CN 106 can include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and the PSTN 108 or can communicate with the IP gateway. Additionally, CN 106 can provide the WTRUs 102a, 102b, 102c with access to other networks 112, which can include other wired and / or wireless networks owned and / or operated by other service providers.

[0051] Although the WTRU is described in Figures 1A to 1D as a wireless terminal, it is contemplated that in some representative embodiments, such a terminal can (e.g., temporarily or permanently) use a wired communication interface with a communication network.

[0052] In a representative embodiment, the other network 112 can be a WLAN.

[0053] A WLAN in infrastructure basic service set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or from the BSS. Traffic originating outside the BSS and destined for an STA can reach the STA through the AP and can be delivered to the STA. Traffic originating from an STA and destined for a destination outside the BSS can be delivered to the AP for delivery to the corresponding destination. Traffic between STAs within the BSS can be delivered through the AP, e.g., where the source STA can deliver traffic to the AP and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be delivered between the source STA and the destination STA (e.g., directly between them) using direct link setup (DLS). In some representative embodiments, DLS can 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 the IBSS or using the IBSS (e.g., all STAs in the IBSS) can communicate directly with each other. The IBSS communication mode can sometimes be referred to in this document as an "ad hoc" communication mode.

[0054] When operating in an 802.11ac infrastructure mode or a similar mode, the AP may send beacons on a fixed channel, such as the primary channel. The primary channel may be of a fixed width (e.g., 20 MHz bandwidth) or a width dynamically set via signaling. The primary channel may be the operating channel of the BSS and may be used by the STA to establish a connection with the AP. In some representative embodiments, for example, Carrier Sense Multiple Access / Collision Avoidance (CSMA / CA) may be implemented in an 802.11 system. For CSMA / CA, the STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. Only one STA (e.g., only one station) may transmit at any given time in a given BSS.

[0055] High Throughput (HT) STAs may communicate using a 40 MHz wide channel, e.g., by combining the primary 20 MHz channel with an adjacent or non - adjacent 20 MHz channel to form a 40 MHz wide channel.

[0056] Very High Throughput (VHT) STAs may support channels that are 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide. The 40 MHz channel and / or 80 MHz channel may be formed by combining contiguous 20 MHz channels. The 160 MHz channel may be formed by combining eight contiguous 20 MHz channels, or by combining two non - contiguous 80 MHz channels (which may be referred to as an 80 + 80 configuration). For the 80 + 80 configuration, after channel coding, the data may pass through a segment parser that divides the data into two streams. Each stream may be separately subjected to Inverse Fast Fourier Transform (IFFT) processing and time - domain processing. These streams may be mapped to two 80 MHz channels, and the data may be transmitted by the transmitting STA. At the receiver of the receiving STA, the operations for the 80 + 80 configuration described above may be reversed, and the combined data may be delivered to the Media Access Control (MAC).

[0057] 802.11af and 802.11ah support operation modes below 1 GHz. Compared to those used in 802.11n and 802.11ac, the channel operation bandwidth and carriers are reduced in 802.11af and 802.11ah. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine type communication, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, such as limited capabilities, including supporting (e.g., only supporting) certain bandwidths and / or limited bandwidths. MTC devices may include a battery with a battery life higher than a threshold (e.g., to maintain a very long battery life).

[0058] A WLAN system that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) includes channels that can be designated as the primary channel. The primary channel may have a bandwidth equal to the maximum common operation bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or restricted by the STA (which supports the minimum bandwidth operation mode) from all STAs operating in the BSS. In the example of 802.11ah, for an STA that supports (e.g., only supports) the 1 MHz mode (e.g., an MTC type device), the primary channel may be 1 MHz wide, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operation 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 an STA (only supporting the 1 MHz operation mode) is sending to the AP, the entire available frequency band may be considered busy even if most of the frequency band remains idle and may be available.

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

[0060] Figure 1D FIG. is a system diagram illustrating RAN 113 and CN 115 according to an embodiment. As noted above, RAN 113 may employ NR radio technology to communicate with WTRUs 102a, 102b, 102c via air interface 116. RAN 113 may also communicate with CN 115.

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

[0062] WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a parameter set that can be extended. For example, the OFDM symbol interval and / or the OFDM subcarrier interval may vary for different transmissions, different cells, and / or different parts of the radio transmission spectrum. WTRUs 102a, 102b, 102c may use subframes or transmission time intervals (TTIs) of various or extendable lengths (e.g., containing different numbers of OFDM symbols and / or having an absolute time length that continuously varies) to communicate with gNBs 180a, 180b, 180c.

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

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

[0065] 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 possibly data networks (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of 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.

[0066] 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 WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selection of a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing in order to customize CN support for the WTRUs 102a, 102b, 102c based on the type of service utilized by the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services that rely on ultra-reliable low-latency (URLLC) access, services that rely on enhanced mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. The AMF 162 may provide control plane functions for handover 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.

[0067] 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 the 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 notifications, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0068] UPF 184a and 184b can be connected to one or more gNBs among gNBs 180a, 180b, and 180c in RAN 113 via the N3 interface. The one or more gNBs can provide access to a packet switched network (such as the Internet 110) for WTRU 102a, 102b, and 102c to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions, such as routing and forwarding packets, implementing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0069] CN 115 can facilitate communication with other networks. For example, CN 115 can include an IP gateway (such as an IP Multimedia Subsystem (IMS) server) that serves as an interface between CN 115 and the PSTN 108 or can communicate with the IP gateway. In addition, CN 115 can provide access to other networks 112 for WTRU 102a, 102b, and 102c. The other networks can include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRU 102a, 102b, and 102c can be connected to DN 185a and 185b via UPF 184a and 184b through the N3 interface to UPF 184a and 184b and the N6 interface between UPF 184a and 184b and the local data network (DN) 185a and 185b.

[0070] In view of Figures 1A to 1D and Figures 1A to 1D In view of the corresponding descriptions, one or more or all of the functions described herein for one or more of the following can be performed by one or more simulation devices (not shown): WTRU 102a - 102d, base stations 114a - 114b, evolved Node Bs 160a - 160c, MME 162, SGW 164, PGW 166, gNBs 180a - 180c, AMF 182a - 182ab, UPF 184a - 184b, SMF 183a - 183b, DN 185a - 185b, and / or any other devices described herein. The simulation device(s) can be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device(s) can be used to test other devices and / or simulate network and / or WTRU functions.

[0071] The simulation device can 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 can 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 to test other devices within the communication network. One or more simulation devices can 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 can be directly coupled to another device for testing purposes and / or can use over-the-air wireless communication to perform tests.

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

[0073] The following abbreviations and acronyms are used in particular in this document: Acknowledgement (ACK); Block Error Rate (BLER); Bandwidth Part (BWP); Channel Access Priority (CAP); Channel Access Priority Class (CAPC); Clear Channel Assessment (CCA); Control Channel Element (CCE); Control Element (CE); Configured Grant or Cell Group (CG); Cyclic Prefix (CP); Conventional OFDM (with Cyclic Prefix) (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 Licensed-Assisted Access (eLAA); Further Enhanced Licensed-Assisted Access (FeLAA); Hybrid Automatic Repeat reQuest (HARQ); Licensed-Assisted Access (LAA); Listen Before Talk (LBT); Long Term Evolution (LTE), e.g. from 3GPP LTE R8 and above; 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 Temporary Identifier (RNTI); RACH Occasion (RO); Radio Resource Control (RRC); Radio Resource Management (RRM); Reference Signal (RS); Reference Signal Received Power (RSRP); Received Signal Strength Indicator (RSSI); Service Data Unit (SDU); System Information SI; System Information Block (SIB); Sounding Reference Signal (SRS); Synchronization Signal (SS); Synchronization Signal Block (SSB); Secondary Synchronization Signal (SSS); Switching Gap (in stand-alone 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 Network (TSN); Uplink (UL); Ultra-Reliable Low-Latency Communication (URLLC); Wide Bandwidth Part (WBWP); and Wireless Local Area Network and related technologies (IEEE 802.xx domain) (WLAN).

[0074] Network energy saving is being studied in Rel-18 so that the network can attempt to minimize the power consumption for device transmission and / or reception. Such minimization is beneficial for reducing operating costs and environmental sustainability. Compared with traditional systems, when there is no data, the Rel-15 NR design minimizes transmission from the network more efficiently. For example, the always-on cell-specific reference signal (CRS) is not used in NR. However, there is still potential to reduce energy consumption. For example, the network may consume energy when it is not transmitting during other activities such as baseband (i.e., digital) processing for reception or beamforming. In addition, even when the network is not serving a WTRU during a given time period, such "idle" power consumption may also be non-negligible in a dense network. If the network can turn off these activities when it is not transmitting to a WTRU, energy consumption can be reduced. Additionally, NR can support beamforming with many ports (e.g., up to 64 transmit and receive ports), where the 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 the required or minimum number of ports, energy consumption can be reduced.

[0075] In one or more instances, the CSI may include at least one of the following: Channel Quality Indicator (CQI), Rank Indicator (RI), Precoding Matrix Indicator (PMI), L1 channel measurements (e.g., RSRP such as L1 - RSRP, or SINR), CSI - RS Resource Indicator Identity (CRI), SS / PBCH Block Resource Indicator (SSBRI), Layer Indicator (LI), and / or any other measurement quantity measured by the WTRU from the configured CSI - RS or SS / PBCH block. In one or more instances, the UCI may include: CSI, HARQ feedback for one or more HARQ processes, Scheduling Request (SR), Link Recovery Request (LRR), CG - UCI, and / or other control information bits that may be sent on the PUCCH or PUSCH. In one or more instances, 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 state, and / or channel availability in the unlicensed spectrum. For example, the WTRU may determine the channel condition 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 the channel condition 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 the channel condition based on the channel availability in the unlicensed spectrum. For example, the WTRU may determine whether the channel is occupied based on the determination of the LBT process. In another case, the WTRU may determine whether the channel has experienced consistent LBT failures. In one or more instances, PRACH resources may be provided, for example but not limited to, in frequency. In one or more instances, PRACH opportunity (RO) may be provided, for example but not limited to, in time measurements. In one or more instances, preamble formats may be provided, for example but not limited to, according to the total preamble duration, sequence length, guard time duration, and / or according to the length of the cyclic prefix. In one or more instances, a certain preamble sequence may be used to transmit the preamble in the random access procedure. In one or more instances, PRACH resources may be characterized based on one or more of frequency resources, time resources, preamble formats, etc. Frequency resources may include, for example but not limited to, sub - carriers, RBs, etc. Time resources may include, for example but not limited to, PRACH opportunity, symbols, sub - frames, etc. Preamble formats may include, for example but not limited to, one or more of the total preamble duration, sequence length, guard time duration, and the length of the cyclic prefix.

[0076] In one or more cases, the attributes of 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 configured grant type 1, type 2, or dynamic grant. In one or more cases, the indication by DCI may include one or more of the following: explicit indication by a DCI field or an RNTI used to mask the CRC of the PDCCH; and implicit indication of the attributes such as, but not limited to, DCI format, DCI size, CORESET or search space, aggregation level, identity 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 attributes and the values may be signaled by RRC or MAC. For example, the WTRU may signal the mapping between the attributes and the values via RRC or MAC.

[0077] In one or more cases, the NR system information (SI) may include the 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 the information required for initial access and for obtaining any other SI. In one or more cases, the minimum SI may include the MIB and SIB1. For a WTRU permitted to camp on a cell, the WTRU may obtain the content of the minimum SI of that cell. In one or more cases, the other SI may include all SIBs not broadcast in the minimum SI. In one or more cases, the WTRU may not receive these SIBs before accessing the cell. In one or more cases, the other SI may also be 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.

[0078] In one or more cases, the MIB may include cell barred 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 period of 80 ms, and within 80 ms, repeated transmissions may occur. 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 the Remaining Minimum SI (RMSI). In one or more cases, SIB1 may be broadcast periodically on the DL-SCH, or sent in a dedicated manner to a UE in the RRC_CONNECTED state on the DL-SCH.

[0079] 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 a Primary Synchronization Signal and a Secondary Synchronization Signal (PSS, SSS respectively) 202, 204. Each of PSS 202 and SSS 204 occupies 1 symbol and 127 subcarriers. The SSB may include a PBCH 206 spanning 3 OFDM symbols and 240 subcarriers, but on one symbol, an unused portion is left in the middle for SSS 204, as Figure 2 shown. In one or more cases, the possible time positions of the SSB within a half-frame may be determined by the subcarrier spacing, and the periodicity of the half-frame in which the SSB is transmitted is 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 the cell.

[0080] Within the frequency width of a carrier, multiple SSBs may be transmitted. In some cases, the PCI of the SSBs transmitted at 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 the RMSI, the SSB may be referred to as a Cell Definition SSB (CD-SSB). In one or more cases, the PCell may be associated with a CD-SSB located on the synchronization raster. In one or more other cases, the PCell may always be associated with a CD-SSB located on the synchronization raster.

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

[0082] In one or more cases, a number of beams may be associated with a given cell. In one or more cases, multiple SSBs may be transmitted within a given cell on different beams (i.e., for the case of beam scanning). Figure 3 An example of beam scanning performed between a gNB 306 and multiple WTRUs (e.g., a first WTRU1 and a second WTRU2) is illustrated. As Figure 3 shown, multiple SSBs 302 may be transmitted 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 transmitted 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 positions around the gNB 306. As Figure 3 shown, the WTRU may measure the signal strength of each SSB detected by the WTRU over a certain period (e.g., the period of a set of SSBs). In addition, based on the measurement results, the WTRU may identify the SSB index with the strongest signal strength. For example, as Figure 3 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. In another example, as Figure 3 shown, beam #7 is the best beam for the second WTRU2. That is, beam #2 provides the strongest signal strength for the second WTRU2.

[0083] 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. The SSB burst set may be, for example but not limited to, the 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.

[0084] In one or more instances, a WTRU may determine whether the WTRU may transmit or receive on certain resources. For example, the WTRU may determine whether the WTRU may transmit or receive on certain resources based on a network availability state. The network availability state may include information that implies and / or indicates an energy saving state of a gNB. In one or more instances, the availability state may correspond to a network energy saving state or a gNB activity level. In one or more instances, the availability state may be uplink specific (e.g., DRX) or downlink specific (e.g., DTX). Additionally or alternatively, the availability state may change from symbol to symbol, time slot to time slot, frame to frame, or over a longer granularity duration. In one or more instances, the WTRU may determine the availability state. In one or more other instances, the network may indicate the availability state. The availability state may be, for example but not limited to, "on", "off", "sleep", "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. A "sleep" availability state may indicate that the gNB wakes up periodically to transmit certain signals (e.g., but not limited to presence signals, synchronization, reference signals, etc.) or receive certain UL signals. The availability state may be configured, for example, 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). Accordingly, the network may turn off baseband processing and other activities. In one or more instances, some measurement resources (e.g., SSB or CSI-RS) are available in certain availability states.

[0085] In one or more instances, 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 can be decoded at the gNB by a low complexity receiver. In some cases, the wake-up request transmission may require decoding with minimal energy consumption requirements. Note that the wake-up request, turn-on request, or 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 the wake-up request. Additionally, 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 instances, the turn-on request may be a physical layer or L2 indication from the WTRU to the network. The WTRU may deliver the L2 indication as one or more of, for example but not limited to, MAC CE, UCI, RRC signaling, PUCCH, RACH indication, etc. As a supplement or alternative to the foregoing, the WTRU may include WTRU assistance information and / or a positioning report.

[0086] In one or more instances, the WTRU determines the availability state based on receipt of an availability state indication from, for example, L1 / L2 signaling (e.g., group common DCI or indication). In one or more other instances, the WTRU implicitly determines the availability state from receipt of periodic DL signaling or non-receipt of periodic DL signaling. In one or more instances, if the WTRU determines that a resource is available in the active availability state, the WTRU determines whether the resource is suitable for transmission / reception and / or measurement for the determined network availability state. The availability state applies to at least one transmission, reception, or measurement resource. The availability state may apply to at least one time period, such as a time slot or time symbol. The availability state may apply to one or more of, for example but not limited to, a serving cell, cell group, frequency band, bandwidth part, TRP, set of spatial elements, and frequency range within a bandwidth part, etc.

[0087] In one or more scenarios, network power consumption can be quite significant and, in many cases, unnecessary, such as during quiet hours. In some cases, to reduce power consumption, the network may turn off small cells or cells with high FR2 power consumption and rely on macro cells for coverage during quiet hours. In one or more scenarios, the gNB may combine information including but not limited to WTRU measurements, WTRU assistance information, interference status, load information, and proprietary information to determine which cells to turn off and which cells to rely on. In one or more scenarios, the gNB that is turned off notifies adjacent cells whether they should be turned on / off. However, in some cases, for example, when the number of active WTRUs changes or the concentration of WTRUs increases, the network may not be aware of a sudden increase in network access demand. Additionally, when capacity-boosting cells are turned off, some WTRUs may experience coverage loss. In some cases, a WTRU may want to notify the network about coverage loss. Additionally, during busy hours, network power consumption can be quite significant, especially when using all or a large number of frequency bands, carriers, antenna chains, and beamforming antennas. Therefore, network access capabilities can be adjusted during busy hours to reduce power consumption. In one or more scenarios, the power consumption associated with MIMO can 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 being used, and the number of MU-MIMO schemes, as well as whether narrow beams are used. Thus, the disclosure provided herein provides solutions that enable the network to know when it can turn off transmission and reception or use a reduced number of antenna ports for such resource usage without degrading the quality of service of the served WTRUs.

[0088] In one or more instances, a WTRU may be configured to receive a dormant cell presence indication. In some instances, the WTRU monitors a presence indication associated with a sleeping / shutdown gNB. Additionally or alternatively, the WTRU may monitor a presence indication associated with a sleeping / shutdown gNB after a condition for transmitting a wake-up request / assist information is met. In one or more instances, the WTRU may monitor the receipt 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 transmitted by an associated cell or gNB that is sleeping. For example, the gNB may sleep in a certain availability state (e.g., deep sleep, micro-sleep, dormant, or off). Alternatively, the presence indication may be downlink information bits delivered to the WTRU. For example, the downlink information bits may be delivered to the WTRU via broadcast signaling (e.g., SIB). In another example, the downlink information bits may be delivered to the WTRU via dedicated signaling (e.g., RRC signaling or MAC CE). If any trigger / condition for transmitting wake-up WTRU assist information or a wake-up request is met, the WTRU may conditionally monitor the presence indication occasion.

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

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

[0091] In one or more cases, the WTRU is configured with monitoring occasions. The WTRU may be configured with monitoring occasions to detect presence indications associated with a cell, TRP, or carrier. In some cases, the carrier may be on a different cell. In some cases, the WTRU may be configured with presence indication occasions to monitor DL signals and / or indications associated with the presence indication. The WTRU may be configured with a periodicity associated with the presence indication for each cell. In addition to or as an alternative to the periodic association, the WTRU may be configured with a monitoring occasion pattern to detect the presence indication of a 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, reference signal, PDCCH transmission, and / or PDSCH transmission. For each cell or carrier, the WTRU may be configured with an association between one or more of an SSB, RS, or other DL signal and the presence signal of the cell.

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

[0093] 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 a 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.

[0094] In some cases, based on a channel quality metric of the measured signal having a value below a configured threshold (e.g., RSRP or SINR), the WTRU determines that there is an indication that the presence signal or the gNB's response to the wake-up signal has not been detected or received. The WTRU may determine that the presence signal has been detected based on the synchronization of the WTRU with the PSS / SSS signal transmitted 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, based on the WTRU not successfully receiving and detecting the presence signal, and / or if the WTRU cannot connect to another serving cell, the WTRU sleeps, activates DRX, or changes the WTRU's DRX cycle. 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.

[0095] 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 the consecutive number of missed samples of the presence indication, the WTRU changes the availability state. For example, the WTRU may be configured with a period for measuring presence indication samples. If the WTRU does not measure a presence indication, the WTRU may consider that the presence indication has not been detected. For example, if the WTRU determines that the channel measurement value is less than the threshold before the end of the detection window, the WTRU considers that the presence indication has not been detected.

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

[0097] 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 transmitting 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 transmitting the wake-up WTRU assistance information and / or the connection request, the WTRU may start monitoring additional TRP, SSB, and / or CSI-RS resources. In some cases, after successfully receiving a response to the connection request, the WTRU may start monitoring additional TRP, SSB, and / or CSI-RS resources. After the WTRU has successfully measured channel conditions (e.g., RSRP, SINR) on measurement resources of an associated cell that are above a configured threshold, the WTRU may change the availability state associated with detecting the presence of a signal (e.g., being on).

[0098] In some cases, the physical layer structure indicating the presence of a signal may include one or more of the structures described herein. For example, the presence indication signal may be a simplified or stripped SSB signal, such as PSS / SSS without PBCH multiplexing, a wide beam SSB, or an 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 legacy WTRUs. 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 waking up the 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 Zadoff-Chu sequences, M sequences, or Gold sequences. 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, coresets, or search spaces. In another example, the presence indication signal may be one or more SSBs received from a different cell or TRP. In some cases, the WTRU may receive one or more SSBs on a configured subset of SSB occasions.

[0099] In one or more cases, the WTRU may monitor the presence indication for synchronization relationship with the SBS. In one or more cases, the WTRU may monitor the presence indication during a configured or predefined occasion. For example, according to the defined timing relationship, the predefined occasion may be bound to the SSB transmission time of the serving cell associated with the indication or a subset of the SSB transmission time. The timing of the presence indication occasion or their timing relationship with the SSB may be indicated by a higher layer, such as but not limited to system information.

[0100] In some cases, the WTRU may perform a time-frequency synchronization process before attempting to detect the 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 the presence indication on the same cell associated with the presence indication. The WTRU may use a new subset of synchronization raster (or different base sequence) to monitor and / or detect the presence signal based on the SSB transmission.

[0101] In one or more cases, when the WTRU successfully receives the presence indication or the response from the gNB to a subsequent wake-up request or connection request, the WTRU assumes different available SSB sets in the cell. For example, the WTRU may assume different available SSB sets in the cell, such as but not limited to the legacy SSB associated with the "on" availability state. In some cases, the WTRU may perform another synchronization and / or initial access process when detecting the available SSB set. In one or more cases, when detecting the stripped SSB or enhanced SSB format, the WTRU may assume different SSB patterns and / or periodicities. In one or more cases, when receiving the stripped SSB / presence signal, the WTRU may read the RMSI for the alternative SSB pattern / configuration.

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

[0103] In one or more cases, the WTRU may be configured with a UL availability window. In some cases, during the UL available window, the WTRU transmits a UL signal after detecting the presence indication and / or at a pre-configured periodic timing. In some cases, the WTRU may maintain a "gNB activity timer". In some cases, the activity timer starts after the WTRU receives a response to a wake-up request signal, WTRU assistance information, or connection request for the WTRU. In some cases, the WTRU starts the "gNB activity timer" after receiving a presence indication (e.g., SSB) or an indication of DCI or MAC CE (e.g., 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 UL windows may be configured according to the availability state. In some cases, the WTRU applies periodicity according to the active availability state. In one or more cases, the WTRU may independently maintain the 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.

[0104] When the gNB activity timer is running or during the gNB activity time (e.g., during the availability period of the availability state), the WTRU may transmit a UL signal, UCI, or data (e.g., PUSCH, PUCHH, PRACH, SRS, UCI, CQI report, and / or measurement report) and / or monitor DL signals and channels (e.g., PDSCH, PDCCH, CSI-RS, SSB, PRS, or channel measurement signal). When the "gNB activity timer" expires, the WTRU may switch to a different availability state. In some cases, the WTRU extends the gNB activity timer after UL transmission or DL reception. When the "gNB activity timer" expires, the WTRU falls back to a less periodic gNB activity cycle or availability state. In some cases, in the less periodic gNB activity cycle or availability state, the UL availability opportunity window and / or the presence indication may occur with a different configured periodicity.

[0105] In one or more cases, the WTRU monitors a presence indication prior to a UL availability window. In some cases, the WTRU monitors a presence indication prior to a UL availability window within a subset of gNB active cycles or available states. In one or more cases, the WTRU may determine to conditionally apply the UL availability window upon successfully receiving a presence indication or an indication from the network via DCI or MAC CE. In some cases, based on a subset of gNB active cycles or availability states, the WTRU may determine to conditionally apply the UL availability window upon successfully receiving 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", "hibernation", or "off" availability state. The WTRU assumes that the UL availability window automatically starts at a pre-configured periodic timing in an "on" or "micro-sleep" availability state.

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

[0107] For a capacity-boosting 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 wake-up WTRU assistance information or requests. 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 wake-up WTRU assistance information to indicate a change in the availability status of the cell designated as capacity-boosting. In some cases, the WTRU triggers and / or sends a connection request or wake-up WTRU assistance information to indicate a change in the availability status of the cell designated as capacity-boosting based on a satisfied condition or trigger. 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 the cell presence signal in a past period associated with measuring the presence indication. In another example, detecting a cell presence signal may include detecting the cell presence signal after a trigger condition associated with sending wake-up assistance information is satisfied. For example, the trigger condition associated with sending wake-up assistance information may be satisfied by detecting that the presence signal associated with the requested cell having a channel quality metric is above a threshold. In one or more cases, the condition or trigger may include not detecting a cell presence signal associated with the cell. For example, not detecting a cell presence signal associated with the cell may correspond to not detecting the cell 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 channel measurements, where the condition or trigger is satisfied when the channel measurements measure 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 the 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 not detecting CSI-RS or detecting CSI-RS below a configured threshold. In one or more cases, the WTRU measurement may be a physical layer measurement or an L3 measurement. Physical layer measurements may be, for example but not limited to, SINR / RSRP, CQI, channel occupancy, RSSI, power headroom, exposure headroom, etc. L3 measurements may be, for example but not limited to, RSRP, RSRQ, etc. The WTRU may include such measurements in the WTRU assistance information content. In one or more cases, the condition or trigger may be based on channel measurements, where the condition or trigger is satisfied when the WTRU detects high load or interference, when the WTRU does not detect an 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 measurements, where the condition or trigger is satisfied when the WTRU detects the availability of a channel in unlicensed spectrum. For example, when the channel is occupied, the WTRU may detect the availability of a channel in unlicensed spectrum based on the determination of the LBT process.In another example, when the channel is considered to have experienced a consistent LBT failure, the WTRU may detect the channel availability in the unlicensed spectrum. For example, the WTRU may trigger the wake-up WTRU assistance information after detecting a consistent UL LBT failure.

[0108] In one or more cases, the condition or trigger may include the arrival of new data. For example, when data arrives from one or more of a subset of DRBs, SRBs, LCHs, LCGs, etc., the WTRU may determine that the condition or trigger is met. In another example, when the arriving data is associated with a certain priority or index, the WTRU may determine that the condition or trigger is met. The WTRU may reflect such data in the assistance information content.

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

[0110] In one or more cases, the condition or trigger may include one or more of performing a positioning procedure, sending a positioning report, and determining the location within the coverage of a cell as the best server. For example, if the WTRU determines that its 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 to have the best channel conditions compared to other cells in the same frequency. In one or more cases, the WTRU may include its location in the WTRU assistance information. In one or more cases, the WTRU may be allowed or adjusted to send the wake-up WTRU assistance information within a certain area or within a 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 a distance from a known location of the requested gNB. In one or more cases, the condition or trigger may include that the buffered data volume is higher than a threshold. The WTRU may trigger a wake-up request based on the buffered data volume being higher than a configured or predefined threshold. For example, based on a configured subset of DRBs, LCHs, or LCGs, if the buffered data volume is higher than the configured or predefined threshold, the WTRU triggers a wake-up request. The WTRU may include the data volume in the WTRU assistance information (e.g., a BSR or a 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 / sending of the WTRU assistance information.

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

[0112] In one or more cases, the condition or trigger may include the availability of UCI or data to be transmitted (e.g., HARQ ACK, CSI, or PMI), the priority associated with the UCI, or the LCH or DRB associated with the UCI. For example, the WTRU may trigger the transmission of wake-up WTRU assistance information based on the availability of UCI or data to be transmitted, the priority associated with the UCI, or the LCH or DRB associated with the UCI.

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

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

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

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

[0117] In one or more instances, the condition or trigger may include triggering a Tracking Area Update (TAU) or a RAN Paging Area Update. For example, the condition or trigger is met when the WTRU determines that the mobility to a cell does not have 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 has expired. For example, the WTRU may start the 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, the WTRU restarts the timer when the timer for the second connection request or waking up the WTRU assistance information expires. In one or more instances, the duration of the keep-alive timer and / or whether the WTRU retransmits the connection request or wakes up the WTRU assistance information may be predefined or signaled explicitly via system information or in another RRC message (such as an RRC connection release). In one or more instances, the duration of the timer may be a function of the periodicity of a signal broadcast by the cell (such as but not limited to an SSB). For example, the duration may be a predefined or configured multiple of the SSB periodicity of the cell.

[0118] In one or more instances, 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 "microsleep" 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 a cell that uses 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 a cell where the WTRU receives a presence indication.

[0119] In one or more instances, the WTRU may perform measurements on the capacity enhanced cell. In one or more instances, 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 turn-on request. If the WTRU is in the RRC idle or inactive state, the WTRU may monitor paging to receive a gNB response after sending the wake-up WTRU assistance information or turn-on request. In some cases, the WTRU may monitor paging after sending the wake-up WTRU assistance information or turn-on request to receive a gNB response on a subset of the paging occasion, P-RNTI, or PDCCH resources.

[0120] In one or more instances, 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.

[0121] 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 indexes for which there is one or a combination of the following: a request to wake up, a request or desire to change the availability state, or a detected presence indication. In some cases, the wake-up WTRU assistance information may include one or more of a gNB ID, a PCI, an SN id, or a carrier ID. In another example, as part of the wake-up WTRU assistance information, the WTRU may include TRP indexes for which there is one or a combination of the following: a request to wake up, a request or desire to change the availability state, or a detected presence indication. In another example, as part of the wake-up WTRU assistance information, the WTRU may include associated carriers or frequency bands for which there is one or a combination of the following: a request to wake up, a request or desire to change the availability state, or a presence indication is applicable. In another example, as part of the wake-up WTRU assistance information, the WTRU may include an expected 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) that may contain a WTRU identifier. 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 sub-header 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 SSBs on demand. In another example, as part of the wake-up WTRU assistance information, the WTRU may include a request to activate / deactivate CSI-RS, PRS, or related resources. For example, the request may be a request to receive CSI-RS on demand. In another example, as part of the wake-up WTRU assistance information, the WTRU may include a request or activation / deactivation of 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, metric, or statistic, including one or more of an 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, BWP change, SUL activation, BWP index to be activated, 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 SSB 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 a WTRU new arrival data type (e.g., RB type or index) and related latency metrics.

[0122] In one or more cases, the WTRU may monitor a cell-specific DL source when sending wake-up WTRU assistance information or a connection request - 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 on-demand SSB or on-demand RS.

[0123] 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 transmissions on different serving cells. The different serving cells may be, for example but not limited to, cells or carriers different from the cells or carriers requested or indicated in the WTRU assistance information or connection request. In some cases, the WTRU initiates a RACH / SR procedure based on the WTRU not having resources for sending the assistance information. In some cases, the WTRU may trigger a new SR or BSR based on the WTRU not having a grant and / or at least one condition for sending the WTRU assistance information being met.

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

[0125] In one or more instances, when the wake-up WTRU assistance information is triggered, the WTRU may perform a positioning procedure, PRS measurement, or may transmit a pSRS.

[0126] In one or more instances, the WTRU may transmit another wake-up WTRU assistance information after a previous wake-up WTRU assistance information has been acknowledged. In one or more instances, the WTRU may transmit another wake-up WTRU assistance information after a timer has expired and before receiving a response to the wake-up WTRU assistance information from the gNB.

[0127] In one or more instances, when transmitting the wake-up WTRU assistance information, the WTRU may start a prohibition timer. Based on the wake-up WTRU assistance information transmitted as part of an uplink transport block, the WTRU may appropriately rely on the HARQ retransmission mechanism for retransmission. In one or more instances, the WTRU may retransmit the wake-up WTRU assistance information after the prohibition timer has expired.

[0128] In one or more instances, the WTRU may retransmit the wake-up WTRU assistance information on one or more of different serving cells, different carriers, different uplinks (e.g., SUL), or different TRPs. For example, after one or a combination of the following, the WTRU may retransmit the wake-up WTRU assistance information on one or more of different serving cells, different carriers, different uplinks (e.g., SUL), or different TRPs: the WTRU performs a configured number of retransmission attempts, the WTRU does not receive a response to the wake-up WTRU assistance information from the network, and the prohibition timer has expired.

[0129] In one or more cases, the WTRU may be configured with a maximum number that allows the transmission of wake-up WTRU assistance information. In some cases, the WTRU maintains a counter, and after the transmission of 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 of the maximum number configured to allow the transmission of wake-up requests. In some cases, the WTRU resets the counter when receiving 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 expiry of a prohibited timer. In some cases, the WTRU moves to the RRC idle or inactive state or moves to the RRC idle or inactive state after reaching the maximum number of retransmission attempts.

[0130] In one or more cases, the wake-up indication includes two components transmitted continuously by the WTRU. In some cases, the WTRU may transmit these two components continuously with a timing gap therebetween. 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, a relatively low power may be used to receive the signal, such as (but not limited to) a signal using on-off keying. In other cases, the signal may constitute a specific signature that can 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. After this signal, the WTRU monitors a specific set of monitoring opportunities to receive signaling for resource allocation. The WTRU transmits PUCCH and / or PUSCH in the allocated resources, and the PUCCH and / or PUSCH may contain further wake-up assistance information.

[0131] In one or more cases, the WTRU may be configured to determine the network energy saving state of the cell. In one or more cases, after receiving DL signaling that changes the availability state of the cell or TRP, the WTRU considers the active availability state associated with the cell, carrier, TRP, BWP, or frequency band to be in the "off", "deep sleep", or "micro sleep" state. For example, the WTRU may receive a shutdown 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.

[0132] 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 group common DCI or RRC signaling in the connected mode. The WTRU may implicitly determine the availability state based on the receipt of periodic DL signaling. The WTRU may be configured or designated to associate the availability state with one or more DL signal types. For example, the DL signal types 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 the active time or whether the associated active 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 receipt of a paging message, paging DCI, paging PDSCH, or 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, the subset of Pos may be a subset of POs aligned with the NES DRX cycle or a configured subset of PDCCH resources. After receiving a paging message with a certain P-RNTI, separately configured NESP-RNTI, or 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, the 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 assumes a certain availability state after receiving a PEI with an NES subgroup based on the subgroup being configured and / or associated with an availability state. An indication of the availability state or availability state transition may be indicated in the paging payload. For example, an indication of the availability state or availability state transition may be indicated as a flag portion of the paging message or short message in the paging payload. Such paging indication may also indicate alternative cell monitoring for paging when the cell from which the signaling is received is in the off, sleep, or NES state. Such 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 the following: initial access, applicable PRACH resources, applicable SSB / RS occasions, applicable SI cycles, and applicable cells and associated availability states.

[0133] Based on the lack of detection of a presence indication, the WTRU implicitly assumes a certain availability state associated with a cell, carrier, TRP, or frequency band. For example, if no presence indication is detected on one or more presence indication occasions, the WTRU may determine the availability state associated with the cell (e.g., "off" or "deep sleep" state). In another case, the WTRU may assume or change the availability state of the cell after multiple consecutive error 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 a case where the WTRU does not detect a signal associated with an availability state having a signal strength higher than the threshold (e.g., a presence signal or an 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 of a presence signal (e.g., detection of a PSS sequence).

[0134] 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 dormant state) for a configured subset of cells (e.g., capacity-boost cells) based on the time of day. For example, the WTRU may determine that a capacity-boost 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 the 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-boost 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 or lack of an RS signal (e.g., CSI-RS, PRS, TRS). 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 paging has been received, e.g., 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., a subset of periodic SI or SIB) has been received, e.g., but not limited to, within a configured time window.

[0135] In one or more cases, the WTRU may stop measuring (e.g., SSB and / or CSI-RS) when it determines that the cell is configured to be in an "off" or "deep sleep" state. In other cases, the WTRU may stop measuring when it determines that there is a clearly configured measurement gap. The WTRU may assume that some configured UL and DL resources are cleared or unavailable in certain availability states (e.g., "off", "hibernate", 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", "hibernate", 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 of the cell and / or channel measurements (e.g., RSRP is less than a threshold).

[0136] In one or more cases, the WTRU may be configured to determine applicable transmit, receive, 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 transmit / receive 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) timing is not applicable in certain availability states. Thus, during non-availability periods, the WTRU may not measure reference signals at such measurement timings. For example, the WTRU may be configured such that a first set of RS or RS configuration (e.g., CSI-RS) is monitored during non-availability periods of the availability state. Additionally or alternatively, the WTRU may be configured such that a second set of RS or RS configuration (e.g., CSI-RS) is not monitored during non-availability periods of the availability state. The WTRU may determine that a subset of uplink or downlink resources (e.g., PRACH, PUSCH, PUCCH) is not applicable in certain availability states. The WTRU may transmit some uplink signals (e.g., SRS, pSRS, PRACH, UCI) in a subset of NW availability states.

[0137] In one or more instances, 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 procedure, e.g., 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 purposes of determining Qin / Qout and determining synchronization / desynchronization. During non-availability periods of some availability states, the WTRU may not measure measurement resources and / or RLM occasions. In some cases, the WTRU may not change or increment relevant RLM counters and timers based on, e.g., but not limited to, skipped measurements. In some cases, the WTRU may not change or increment measurement values / quantities, including RLM, BFD, and CSI measurements, during skipped measurement occasions (e.g., during non-availability periods of an availability state). 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 quantity counter, RLM trigger time counter). In some cases, if a certain availability state is active, the WTRU may apply the alternative set of values for RLM timers and / or counters.

[0138] In one or more instances, if the WTRU determines that the network does not transmit an applicable reference signal at some instances for the BFD procedure, e.g., due to NES (e.g., during a non-availability period in the availability state), then when the applicable CSI-RS signal is not transmitted, the WTRU may determine to prohibit measuring measurement resources and / or instances for determining the BFI. The WTRU may not change or increment the relevant BFD counters and timers based on, e.g., skipped measurement instances. For cases where the BFI counter is higher than the configured threshold for triggering beam failure, the WTRU may wait or delay the triggering of the BFR until the CSI-RS instance associated with the NW activity state (i.e., availability state) associated with NES (e.g., sleep or hibernate) occurs. In one or more instances, upon receiving a CSI-RS with a quality metric higher than the configured threshold, the WTRU may cancel a triggered BFR. For example, upon receiving a CSI-RS with a quality metric higher than the configured threshold (such as Qin / RSRP > threshold), the WTRU cancels the triggered BFR. In one or more other instances, if the CSI-RS instance is associated with a certain availability state (e.g., NES mode or on), the WTRU may cancel a triggered BFR upon receiving a CSI-RS with a quality metric higher than the configured threshold (e.g., Qin / RSRP > threshold). The WTRU may be configured with an alternative set of values for the BFD timer and / or counters (e.g., BFD counter, BFD timer, etc.). In some cases, if a certain availability state is active, the WTRU may apply the alternative set of values for the BFD timer and / or counters.

[0139] In one or more instances, once the WTRU wakes up, the NW may indicate that a subset of past measurements or measurement instances are not valid. The WTRU may in turn retrospectively correct the metrics accumulated for RLM or BFD. The metrics accumulated for RLM or BFD may be, e.g., the number of BBIs, the number of out-of-syncs, etc. In one or more instances, 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 significant signal strength difference. If the WTRU identifies a sequence embedded within the SSB or CSI-RS, the WTRU may consider the measurement, otherwise it may skip the measurement instance and consider it not transmitted due to NES. For example, the WTRU may skip the measurement instance by not performing channel measurements on the SSB or CSI-RS instance.

[0140] In one or more instances, the WTRU may mute (e.g., not use, deactivate, etc.) some uplink and / or downlink resources for data and / or control information exchange that does not overlap with the configured time period or availability period of the availability state of an active SSB / RS pattern's SSB or RS occasion, or within the configured time period or availability period of the availability state. The WTRU may assume multiple silent mode / resource periodicities based on the active SSB periodicity and active availability state from the configured mode / periodicity.

[0141] In one or more instances, the WTRU may be configured or predefined to determine that in some cell availability states (e.g., "off", "sleep", 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 is not sent by the gNB for the serving cell. In another example, the WTRU determines that there is an indication that it is sent by a cell in such an availability state. In another example, the WTRU determines that the 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 SIB.

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

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

[0144] In one or more cases, a WTRU may be configured for SSB / RS adjustment. In one or more cases, for the case where the WTRU is configured to be in an idle mode or an inactive mode, when the network is configured to be in a NES state or a given availability state, the WTRU may attempt to decode a simplified SSB (e.g., only the PSS). The WTRU may determine a modified timing of the remaining synchronization signal or SSB occasion. The WTRU may detect the remaining synchronization signal or SSB occasion based on the attributes of the PSS. The attributes 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 conventional (i.e., the periodicity broadcast in the system information block (SIB) signaling), but may change the periodicity of the SSS and PBCH. In one or more cases, the PSS may point to an alternative SSB periodicity.

[0145] The WTRU may be configured with multiple values of the field ssb - periodicityServingCell. These values may be configured, for example, using RMSI, secondary SIB, in broadcast signaling, etc. For a WTRU in a connected mode, L1 signaling (e.g., group common DCI) or L2 signaling (e.g., MAC CE) may indicate one or more of the following: a handover between the configured SSB periods, a handover to a different availability state, and / or activation or deactivation of certain availability states. Upon receiving such a command, the WTRU may assume different periodicities of the SSB and the associated RACH resources. For example, the WTRU may assume different periodicities of the SSB and the 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 the availability state).

[0146] In one or more cases, for the case where the WTRU is configured to be in an idle mode, the WTRU may determine whether the SSB or RS periodicity and / or the SSB or RS occasion is lost (i.e., whether the SSB or RS occasion is sent from the gNB) based on past measurements. For example, the WTRU may determine that no SSB or RS is sent based on the current measurement in the measured net occasion, which is different from the X past measurement (or the moving average of the past measurements), and the difference between the X past measurement and the current measurement is greater than a predetermined or configured value. X may be predetermined or configured. The WTRU may read, obtain, or re - obtain the system information based on the change between the current measurement and the past measurement being greater than a threshold.

[0147] In one or more cases, for the case where the WTRU is configured to be in the connected mode, the WTRU may be configured with one or more RS periods / modes (e.g., for CSI-RS, PRS, TRS, etc.). In one or more cases, the WTRU may determine the periodicity of the active RS mode based on one or more of the following: a) the difference or comparison between the current RS measurement occasion and multiple past measurements, b) the overall signal quality of the cell (e.g., based on L3 RSRP or measurements of the presence of signals), c) the active availability state, and d) the mobility state of the WTRU. The WTRU may ignore measurements of RS occasions that are not transmitted in the active RS mode (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 the RS periodicity / mode. The gNB may signal a change in the RS or SSB mode / period in an indication (e.g., MAC CE, DCI, etc.).

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

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

[0150] In one or more instances, a WTRU may be configured to send a Tracking Area Update (TAU) on a subset of cells 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 capacity enhanced cells and / or cells with a determined availability state configured to be, for example, in a closed, dormant, or sleep state.

[0151] In one or more instances, a 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 instances, the WTRU may perform a mobility procedure in the connected mode after receiving a shutdown indication. The WTRU may perform cell reselection, initial access, and / or RRC reestablishment 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 transitions to the idle mode after receiving a shutdown indication.

[0152] In the case where the current serving cell or a capacity enhanced cell is shut down or meets a certain condition, 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 procedure to an alternative serving cell associated with the cell or gNB from which it received the shutdown indication. In one example, the shutdown or sleep indication may be dynamically indicated to the WTRU, for example, via dedicated or broadcast signaling, as to which cell to fallback to or connect to. In another example, the fallback cell may be predefined as the primary 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 fallback to an LTE or FR1 cell associated with the cell or gNB from which it received the shutdown indication. For example, based on whether the WTRU is in CA or DC using multiple RATs or multiple frequency bands, the WTRU may fallback to an LTE or FR1 cell associated with the cell or gNB from which it received the shutdown indication.

[0153] In one or more instances, the WTRU may perform initial access / RA, mobility, and / or initiate related measurements on an alternative cell or capacity enhancement cell based on meeting one or more of the following conditions: (a) the latency associated with new data arrival, BSR, or buffered data is strict (e.g., below or above a threshold); (b) the data associated with new data arrival, BSR, or buffered data includes data from one or more "NES" RBs or LCHs (based on RB id), including the condition that all data is from a configured NES DRB / SRB; (c) the amount of buffered data or buffered data from NES RBs is greater than or less than a configured threshold; (d) one or more conditional handover 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) the measured channel conditions associated with the alternative cell and / or the best or serving cell; and (g) the indicated or measured cell resource load (utilization) metric associated with the alternative cell and / or the best serving cell.

[0154] In one or more instances, 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 instances, the WTRU may be configured with a subset of DRBs and / or SRBs that are NES RBs (or LCHs), and the WTRU may use these NES RBs in the NES state. In one or more instances, 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 having arrived from such RBs.

[0155] In one or more instances, the WTRU may be configured to associate the availability of one cell with the availability state of another cell. The WTRU may be predefined or configured with an association between cells. The association 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 in the same frequency band, cells of the same RAT, etc. The WTRU may change the availability state of one cell based on the WTRU changing the state of another associated cell. For example, if the WTRU determines that a cell is closed, in a dormant state, or in a sleep / energy saving state, the WTRU changes the availability state associated with all cells associated with the cell that is closed, 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.

[0156] In one or more instances, a WTRU may be configured to determine which sectors, TRPs, and / or antennas of a gNB are available or active based on an availability state associated with the gNB. For example, the WTRU may determine that the gNB operates with a single sector in an energy saving availability state (e.g., sleep, hibernation, 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 operates with a different number of active cells / PCIs or multiple cells that are part of the same gNB.

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

[0158] In one or more instances, the activity indication may be a PDCCH that contains group common signaling. For example, the NW may send group common DCI to a group of WTRUs (e.g., WTRUs in a serving cell) to indicate a change in the 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 the monitoring occasion of the activity indication PDCCH.

[0159] In one or more instances, 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 an associated gNB / cell over a particular time interval (e.g., a time interval for an availability state). In some instances, the WTRU may configure and / or pre-determine an activity level, which may include, for example, regular activity and reduced activity. In some instances, the signaling may indicate the activity level. For example, a bit "1" may indicate regular activity. In another example, a bit "0" may indicate reduced activity.

[0160] In another example, for each activity level (e.g., availability state), the signaling or activity indication within the PDCCH may include defined transmit and receive attributes. For example, during periods of reduced activity, it may not be desirable for the WTRU to monitor certain PDCCH search spaces (including, e.g., one, multiple, or all SSs), receive certain types of PDSCHs (including, e.g., one, multiple, or all PDSCHs), transmit PUCCH / PUSCH, and / or perform certain measurements. In one or more cases, the WTRU may determine the 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 changed or activated on such a carrier. In another example, the WTRU may stop monitoring the PDCCH for cross-carrier scheduling based on the availability state changed or activated on such a carrier, while the WTRU monitors the PDCCH from another carrier (e.g., on or not on the NES state).

[0161] 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 set of configurations may include SS configuration, CSI report configuration, index of the SBS transmitted, etc. In one or more cases, each set of configurations may have an attribute associated with the activity level. For example, an attribute such as a label may be set to "reduced activity".

[0162] In another example, the signaling or activity indication within the PDCCH may include the time interval on which the activity level is assumed. In such cases, the WTRU may signal the time interval on which the activity level is assumed in a part of the PDCCH or the activity indication. In some cases, a bitmap may be used to indicate the time interval, where each bit in the bitmap may be associated with a specific duration (e.g., a time slot or a frame). For example, a bit "1" may indicate normal 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 the 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 when the indication is received. The length of the interval may be configured or signaled in the indicating PDCCH.

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

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

[0165] In one or more instances, the WTRU may be configured to send a "departure indication" signal before or upon cell reselection to a new cell. The "departure indication" signal may have the same structure as the "setup request" signal. A first parameter and a second parameter may be used to generate the "setup request" signal and the "departure indication" signal, respectively. The first parameter and the second parameter may be related by a predefined relationship or signaled by a higher layer. For example, the WTRU may receive: RRC signaling (e.g., system information or RRC connection release) that indicates whether to send the "departure indication" signal before or upon cell reselection; and configuration of the parameters for generating the signal. Based on the structure of the signal, the generation parameters may include, for example, a scrambling identity or a base sequence.

[0166] In one or more instances, the parameter configuration of the "departure indication" signal may depend on the identity of the serving cell before cell reselection. In one or more other instances, the parameter configuration of the "departure indication" signal may depend on the identity of the serving cell after cell reselection. In the latter case, the "departure indication" signal may correspond to a "new cell indication" signal.

[0167] In some cases, the "setup request", "departure 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 a setup request (e.g., the RACH preamble may include a setup signal). Based on the random access response received by the WTRU corresponding to the PRACH, the RACH procedure may be considered successful.

[0168] In other cases, the WTRU may be configured to initiate an RRC connection request to a 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 transmission of a "departure indication" or "new cell indication" signal of the WTRU in idle mode may determine when a cell may be shut down. For example, the transmission of a "departure indication" or "new cell indication" signal of the WTRU in idle mode may determine that a cell may be shut down when no or few WTRUs are camped on the cell.

[0169] 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, e.g., based on the associated cell being shut down or being configured to be in an energy saving state.

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

[0171] In some cases, the WTRU may be configured, predefined, or indicated to deactivate one or more uplink carriers, such as but not limited to a secondary SCell. In some cases, based on the associated serving gNB configured in one or more availability states, the WTRU may be configured, predefined, or indicated to rely on the PCell. For example, if the gNB is in a certain availability state, the WTRU deactivates the SCell. For example, if the associated cell is shut down or is configured to be in an energy saving state and if the gNB is in a certain availability state, the WTRU deactivates the SCell.

[0172] In some cases, the WTRU may be configured, predefined, or indicated to switch the active UL and / or DL bandwidth part of the WTRU to the initial BWP or the default BWP. For example, if the associated serving cell is configured to be in one or more availability states, the WTRU switches the active UL and / or DL bandwidth part of the WTRU 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 shut down 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, depending 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 (or being 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 active UL and / or DL active BWP of the WTRU 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 active UL and / or DL active BWP of the WTRU to the NW energy saving BWP. In some cases, if the WTRU does not receive an availability signal in the current BWP after multiple error detections, the WTRU switches the active UL and / or DL active BWP of the WTRU 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 active UL and / or DL active BWP of the WTRU 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 a MAC CE) that indicates a switch to the NES BWP based on the reception or lack of reception of a common cell signal. The WTRU may send HARQ feedback or an acknowledgement of the reception of the NES BWP switch command / indication. The WTRU may switch to the NES BWP after sending such feedback and / or when a second acknowledgement DL signal is received 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 over 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, if no DL signal is detected over 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 implicitly switch to another BWP (e.g., the NES BWP). The WTRU may switch to the NES BWP when a BWP inactivity timer or another NES BWP inactivity timer expires. The BWP inactivity timer or another NES BWP inactivity timer may be reset upon receipt of a DL signal associated with the availability state / NES state of the gNB.

[0173] In one or more cases, a presence indication associated with a cell may indicate which carriers are active. In some cases, the WTRU may start measuring resources (e.g., CSI resources or channel quality) upon receipt of a presence indication associated with a certain carrier. The WTRU may activate a Scell upon receipt of a presence indication associated with a certain Scell or the associated gNB. If the WTRU does not receive a presence indication associated with the SCell or the associated gNB, the WTRU may deactivate the carrier or the SCell. In some cases, if no presence indication associated with the SCell or the associated gNB is received after a number of failed attempts to detect a received presence indication or after a timer (e.g., the Scell deactivation timer) expires, the WTRU may deactivate the carrier or the SCell.

[0174] 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 certain 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 that frequency band. In other examples, if the WTRU determines that the cell is in a certain availability state (e.g., shutdown or sleep state), the WTRU may shut down or deactivate the cell on a certain carrier or frequency band.

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

[0176] 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 deactivate. In some cases, the gNB may deactivate beams that are not useful from the perspective of WTRU coverage.

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

[0178] 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 a need for an additional number of antennas, ports, beams, etc. For cases where CSI-RS related measurements are below a certain threshold, the TRP configuration at the gNB may be sub-optimal. In another example, the WTRU may indicate a preference for a certain set of spatial resources based on measurements associated with those resources, such as but not limited to ports, beams, and TRPs (i.e., in cases where multiple TRPs are associated with the WTRU). Each set of spatial resources may be abstracted by an index configured by RRC signaling. The WTRU may report such a preferred index as part of the UCI or MAC CE. In one example, if the measurement of a certain "k" subset "k" of resources is above a threshold (i.e., "k" is the strongest of "n" resources "o" t), the WTRU may indicate a preference for that subset of resources. In one or more cases, the gNB may utilize the indicated preference to modify the gNB availability state. For example, the gNB may utilize the indicated preference to modify the gNB availability state by turning off spatial resources below the threshold.

[0179] In one or more cases, if reference signal measurements (e.g., RSRP, RSRQ, etc.) are above a certain threshold but below another threshold, the WTRU may indicate a 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., the event A1 threshold, which does not trigger a mobility procedure), but below another threshold 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.

[0180] In one or more cases, the WTRU may request an additional spatial resource allocation or a change in the spatial resource allocation 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.

[0181] In one or more scenarios, the WTRU may utilize location-based measurements to request a change in the availability state of the gNB and / or the spatial resource allocation. 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 the rx-tx measurements in conjunction with information regarding the network availability state and / or cell / TRP presence indication information. When indicating a preference for a change in the availability state of the cell and / or the current spatial resource allocation (e.g., beam, antenna / port, and other similar resources), the WTRU may use the rx-tx measurements in conjunction with information regarding the network availability state and / or cell / TRP presence indication information.

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

[0183] In one or more scenarios, the gNB may utilize the indicated WTRU assistance information to optimize network-side power consumption. In some cases, optimizing network-side power consumption may include prioritizing macro TRP energy savings via one or more of antenna / port muting, adaptive sectorization, and selective SSB 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 savings may result in the greatest network-side savings (i.e., in terms of PA and BB power consumption). In other examples, having more cell / TRP activity may be beneficial. For example, in high-load scenarios where the macro TRP needs to be in a fully available state, it may be beneficial to have multiple small cells also in a fully available state. Specifically, if the small cells are NR microdeployments operating in a dense urban deployment, it may be beneficial to have multiple small cells in a fully available state. In such scenarios, the increased capacity of multiple small cells may result in faster transmissions, thereby allowing for more sleep time and thus reducing network-side power consumption.

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

[0185] Figure 4B An example diagram is illustrated, which illustrates WTRU assistance information for detection transmissions based on presence indications. Figure 4BIllustrates a WTRU process 400 for a connection request for a cell configured with a presence indication. Although shown as steps 403 to 422, in some examples, process 400 may only include 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, 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 the DTX state. To access resources, the WTRU 404 may be configured with monitoring opportunities to detect a presence indication associated with a cell, TRP, or carrier. Thus, at 406, the WTRU 404 monitors a discovery signal and / or a presence indication from another cell (e.g., anchor cell 432). In some cases, a carrier may be associated with different cells. In some cases, the presence indication may be a DL signal, such as but not limited to a stripped 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 gNB 402). At 408a, the gNB 402 may monitor presence indication information. For example, the gNB 402 may monitor a 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, CSI-RS, etc. The presence information may be, for example but not limited to, system information, including resources for accessing the non-anchor cell. The anchor cell may be, for example but not limited to, a SpCell, PCell, primary SCell, etc. The UL availability window 410a (and the UL availability window 410b) may correspond to a period of time when a presence signal or information reception is detected and / or a period of time after the WTRU sends a wake-up request or auxiliary information. During the UL availability window, the WTRU may send uplink signals and channels. For example, the WTRU may send uplink signals and channels on a configured UL channel resource on the non-anchor cell where the wake-up request is sent. In one or more cases, the gNB sleep opportunity 412 may correspond to the cell DTX / DRX duration during which it is not expected that the cell sends a subset of DL signals / channels and / or receives on the UL channel / signal. The cell DTX / DRX duration may be, for example, an availability state associated with gNB sleep.In one or more cases, for the measured channel conditions being less than a threshold (e.g., RSRP) and / or in the case of SBS associated with a non-anchor cell or no detected anchor cell, at 414, the WTRU triggers the transmission of a wake-up request or information. In one example, if the channel conditions measured by the WTRU are less than the threshold, the SSB associated with the non-anchor cell or the anchor cell may not be detected.

[0186] 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 sleeping / off gNB 402 after meeting the conditions for sending an access request and / or assistance information. 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 the gNB presence indication and / or information from the anchor cell 432. In such cases, the WTRU may assume the availability state associated with the cell (e.g., the "off" or "deep sleep" state). In one or more cases, the WTRU is configured to send one or more of an access request, WTRU assistance information, or initiate a random access (RA) process (e.g., RACH or PRACH process) at 418 after successfully detecting a presence signal. The WTRU may send one or more of an access request, WTRU assistance information, or RA within the UL availability window 410b after detection). The WTRU may send RA to initiate RA on, for example, a non-anchor cell.

[0187] 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 assistance information and / or an access request. In one or more cases, the WTRU is configured to monitor additional RS, SSB, Msg4, and / or CSI-RS resources after sending an access request or receiving a response to the access request. In one or more cases, at 422, the WTRU is configured to change the availability state of the cell (e.g., change to the "on" or "micro-sleep" state). For example, the WTRU is configured to change the availability state of a non-anchor cell. The WTRU may change the availability state of the cell, for example, after successfully receiving a response to the sent access request from the requested cell.

[0188] Although the features and elements have been described above in particular combinations, one of ordinary skill in the art will understand that each feature or element can be used separately or in any combination with other features and elements. In addition, the methods described herein can be implemented in a computer program, software or firmware that is incorporated into a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (sent via wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as internal hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with the software can be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU) comprising: A processor, the processor being configured to: Receive configuration information, wherein the configuration information indicates a first periodicity and a second periodicity, wherein the first periodicity is associated with a reduced uplink cell activity level or a reduced downlink cell activity level of a first cell, and the second periodicity is associated with a reduced uplink cell activity level or a reduced downlink cell activity level of a second cell; Receive downlink control information (DCI), wherein the DCI indicates whether to activate the reduced uplink cell activity level or the reduced downlink cell activity level of the first cell, and indicates whether to activate the reduced uplink cell activity level or the reduced downlink cell activity level of the second cell, and wherein the cyclic redundancy check (CRC) of the DCI is scrambled using a dedicated radio network temporary identifier (RNTI); Based on the first periodicity and based on the DCI indicating activation of the reduced uplink cell activity level or the reduced downlink cell activity level of the first cell, start a first activity timer for the first cell; Based on the second periodicity and based on the DCI indicating activation of the reduced uplink cell activity level or the reduced downlink cell activity level of the second cell, start a second activity timer for the second cell; Based on the DCI indicating that the reduced uplink cell activity level of the first cell is active, transmit one or more uplink signals via the first cell during a first availability period, or based on the DCI indicating that the reduced downlink cell activity level of the first cell is active, receive one or more downlink signals via the first cell during the first availability period, wherein the first availability period is based on the first activity timer for the first cell; And Based on the DCI indicating that the reduced uplink cell activity level of the second cell is active, transmit one or more uplink signals via the second cell during a second availability period, or based on the DCI indicating that the reduced downlink cell activity level of the second cell is active, receive one or more downlink signals via the second cell during the second availability period, wherein the second availability period is based on the second activity timer for the first cell.

2. The WTRU according to claim 1, wherein the processor is configured to monitor a specific search space of the PDCCH using the dedicated RNTI.

3. The WTRU according to claim 1, wherein the dedicated RNTI is associated with energy saving operations.

4. The WTRU according to claim 1, wherein the one or more uplink signals include a scheduling request.

5. The WTRU according to claim 1, wherein the one or more uplink signals include a channel quality indicator (CQI) report.

6. The WTRU according to claim 1, wherein the one or more downlink signals are physical downlink control channel (PDCCH) transmissions.

7. The WTRU according to claim 1, wherein the DCI corresponds to group common signaling.

8. The WTRU according to claim 1, wherein a single bit in the DCI indicates the activity level.

9. The WTRU according to claim 1, wherein the processor is configured to independently manage the activity levels of the reduced downlink activity level and the reduced uplink activity level.

10. The WTRU according to claim 1, wherein the DCI corresponds to a presence indication.

11. A method performed by a wireless transmit / receive unit (WTRU), the method comprising: Receive configuration information, wherein the configuration information indicates a first periodicity and a second periodicity, wherein the first periodicity is associated with a reduced uplink cell activity level or a reduced downlink cell activity level of a first cell, and the second periodicity is associated with a reduced uplink cell activity level or a reduced downlink cell activity level of a second cell; Receive downlink control information (DCI), where the DCI indicates whether to activate the reduced uplink cell activity level or the reduced downlink cell activity level of the first cell, and indicates whether to activate the reduced uplink cell activity level or the reduced downlink cell activity level of the second cell, and where the cyclic redundancy check (CRC) of the DCI is scrambled using a dedicated radio network temporary identifier (RNTI); Based on the first periodicity and based on the DCI indicating to activate the reduced uplink cell activity level or the reduced downlink cell activity level of the first cell, start a first activity timer for the first cell; Based on the second periodicity and based on the DCI indicating to activate the reduced uplink cell activity level or the reduced downlink cell activity level of the second cell, start a second activity timer for the second cell; Based on the DCI indicating that the reduced uplink cell activity level of the first cell is active, transmit one or more uplink signals via the first cell during a first availability period, or based on the DCI indicating that the reduced downlink cell activity level of the first cell is active, receive one or more downlink signals via the first cell during the first availability period, where the first availability period is based on the first activity timer for the first cell; And Based on the DCI indicating that the reduced uplink cell activity level of the second cell is active, transmit one or more uplink signals via the second cell during a second availability period, or based on the DCI indicating that the reduced downlink cell activity level of the second cell is active, receive one or more downlink signals via the second cell during the second availability period, where the second availability period is based on the second activity timer for the first cell.

12. The method according to claim 11, wherein the WTRU is configured to monitor a specific search space for the PDCCH using the dedicated RNTI.

13. The method according to claim 11, wherein the dedicated RNTI is associated with power saving operations.

14. The method according to claim 11, wherein the one or more uplink signals include a scheduling request.

15. The method according to claim 11, wherein the one or more uplink signals include a channel quality indicator (CQI) report.

16. The method according to claim 11, wherein the one or more downlink signals are physical downlink control channel (PDCCH) transmissions.

17. The method according to claim 11, wherein the DCI corresponds to group common signaling.

18. The method according to claim 11, wherein a single bit in the DCI indicates the activity level.

19. The method according to claim 11, wherein the activity levels of the reduced downlink activity level and the reduced uplink activity level are managed independently.

20. The method according to claim 11, wherein the DCI corresponds to a presence indication.

21. A wireless transmit / receive unit (WTRU) comprising: A processor, the processor being configured to: Monitor a presence indication signal in a second cell, the presence indication signal indicating that a first cell is in a low availability state; Based on detecting the presence indication signal in the second cell and based on measurements performed on a synchronization signal block (SSB) of the second cell being less than a threshold, determine to send a wake-up signal for the first cell, where the wake-up signal is sent before the expiration of a predetermined period after receiving the presence indication signal via the second cell; Send the wake-up signal; After sending the wake-up signal, monitor the transmission of the SSB of the first cell; After sending the wake-up signal, receive information indicating that the first cell has transitioned to an active state; And After receiving the information indicating that the first cell has transitioned to the active state, transmit data via the first cell.

22. The WTRU according to claim 21, wherein the processor is further configured to: Determine a discontinuous transmission (DTX) mode for transmitting signals to the first cell based on the presence indication signal received in the second cell.

23. The WTRU according to claim 21, wherein the resources for receiving the SSB of the first cell are determined based on the resources for receiving the presence indication signal in the second cell.

24. The WTRU according to claim 21, 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.

25. The WTRU according to claim 21, wherein the predetermined time period includes an uplink availability window, and wherein the wake-up signal is part of a MAC control element (MAC CE) or WTRU assistance information.

26. The WTRU according to claim 21, wherein the presence indication signal is indicated via a WTRU-specific DCI, a group common DCI, a MAC CE, or a paging message.

27. The WTRU according to claim 21, wherein the processor is further configured to: Adjust beam failure detection (BFD) measurements, radio link monitoring (RLM) measurements, or channel state information (CSI) measurements on the second cell according to the availability state of the second cell.

28. The WTRU according to claim 21, wherein the processor is further configured to: Determine the SSB mode of the second cell based on whether the second cell is in the low availability state or the active state.

Images