Acquisition of synchronization and system information in energy-saving networks associated with reduced synchronization signals

Abstract

Systems, methods, and tools are described herein for obtaining synchronization and system information in an energy-saving network associated with a reduced synchronization of a WUS and a WUS that results in SSB measurements. Synchronization acquisition of a wireless transmit / receive unit (WTRU) may start by detecting a synchronization signal (SS). The WTRU may determine timing and / or resource information of the pre-synchronized or DL-WUS type signal (s), e.g., based on the reduced synchronization indication. Pre-synchronization or WUS signaling may provide an indication of timing of network energy saving (NES) configuration information and system information.

Description

[0001] Cross-reference to related applications This application claims the benefit of U.S. Provisional Application No. 63 / 526,323, filed July 12, 2023, the contents of which are incorporated herein by reference in their entirety. Background Technology

[0002] Mobile communications, which utilize wireless communication, are constantly evolving. The fifth-generation mobile radio access technology (RAT) can be referred to as 5G New Radio (NR). For example, the previous generation (legacy) mobile RAT could be fourth-generation (4G) Long Term Evolution (LTE). Summary of the Invention

[0003] This document describes systems, methods, and tools for acquiring synchronization and system information in energy-efficient networks associated with WUS that leads to slim synchronization and SSB measurements. Wireless Transmit / Receive Unit (WTRU) synchronization acquisition can be initiated by detecting a synchronization signal (SS). The WTRU can determine the timing and / or resource information of (multiple) pre-synchronization or DL-WUS-like signals, for example, based on a slim synchronization indication. Pre-synchronization or WUS signaling can provide timing indications of network energy-efficient (NES) configuration information and system information.

[0004] The WTRU can receive a first signal. The first signal may include a simplified SS. The simplified SS may be a compressed SS. The first signal may indicate information associated with a second signal. The second signal may include a pre-synchronization signal (e.g., a wake-up signal (WUS), downlink WUS (DL-WUS)). The information associated with the second signal may be indicated based on one or more attributes or characteristics associated with the simplified SS (e.g., timing information, frequency information, phase information, sequence selection information). The first signal may indicate a simplified sequence that may indicate information associated with the second signal. The first signal may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), or a PSS and SSS (e.g., PSS and SSS only). In the example, the first signal may avoid including a physical broadcast channel (PBCH) block. The WTRU can determine the resources associated with receiving the second signal (e.g., the pre-synchronization signal, WUS, DL-WUS), for example, based on information associated with the second signal (e.g., indicated by the first signal). The WTRU can receive the second signal, for example, by using resources determined using information associated with the second signal. The second signal may include an indication associated with receiving an SSB. The SSB may include a PBCH block. The WTRU may determine information associated with receiving the SSB, for example, based on an indication associated with receiving the SSB (e.g., indicated by a second signal). The information associated with receiving the SSB may include one or more of the following: NES state, SSB periodicity, the presence of a complete SSB at a potential time of complete SSB transmission, etc. The WTRU may receive the SSB, for example, based on the determined information associated with receiving the SSB. Attached Figure Description

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

[0006] Figure 1B The illustration shows that, according to the embodiment, it is possible to... Figure 1A The diagram shows a system diagram of an example wireless transmit / receive unit (WTRU) used in a communication system.

[0007] Figure 1C The illustration shows that, according to the embodiment, it is possible to... Figure 1A The diagram shows a system diagram of an example radio access network (RAN) and an example core network (CN) used within the communication system.

[0008] Figure 1D The illustration shows that, according to the embodiment, it is possible to... Figure 1A The system diagram shows a further example RAN and a further example CN used within the communication system shown.

[0009] Figure 2The illustration shows an example time-frequency structure of SSB.

[0010] Figure 3 An example of SSB beam scanning with SSB burst concentration is further illustrated.

[0011] Figure 4 The illustration shows an example of simplified synchronization signal transmission and SSB transmission.

[0012] Figure 5 Examples of PSS, SSS, and PBCH are illustrated, which are limited to 11 PRBs (R-15PSS / SSS length) with an additional PBCH symbol, with 44 PRBs on the left-hand side for PBCH and 55 PRBs on the right-hand side for PBCH.

[0013] Figure 6 Examples of PSS, SSS, and PBCH are illustrated, which are limited to 11 PRBs (R-15PSS / SSS length) with an additional (N)PBCH symbol.

[0014] Figure 7 The illustration shows the SSB structure of Example 2, where the PSS / SSS is stacked with the PBCH.

[0015] Figure 8 An example of a time-frequency compact structure with only one instance of SS and only one instance of PBCH is illustrated.

[0016] Figure 9 The illustration shows an example of a 1SSB-3SS based transmission.

[0017] Figure 10 The illustration shows an example of a 1SSB-2SS based transmission.

[0018] Figure 11 An example synchronization design with TDM architecture for SSB and PSS / SS is illustrated.

[0019] Figure 12 The illustration shows example designs for different SS lengths and periodicities.

[0020] Figure 13 The illustration shows an example compact MSI structure with separate encodings for PBCH and compact SIB-1.

[0021] Figure 14 The illustration shows an example compact MSI structure with separate encodings for PBCH and RMSI, plus a smaller frequency coverage (footprint).

[0022] Figure 15 The illustration shows an example compact MSI structure with joint encoding of PBCH and compact SIB-1.

[0023] Figure 16 The illustration shows an example compact MSI structure with joint encoding of PBCH and compact SIB-1. Detailed Implementation

[0024] Figure 1A This diagram illustrates an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content (such as voice, data, video, messaging, broadcasting, etc.) to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Zero-Tail Unique Word DFT Extended OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0025] like Figure 1AAs shown, the communication system 100 may include wireless transceiver units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110, and other networks 112. Although it will be appreciated, the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d can be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain scenarios), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

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

[0027] 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 radio 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 for a specific geographic area for radio services, 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. Therefore, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology, and multiple transceivers may be used for each sector of the cell. For example, beamforming can be used to transmit and / or receive signals in a desired spatial direction.

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

[0029] More specifically, as noted above, the communication system 100 can be a multiple access system and can 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, and 102c, can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117. WCDMA can include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​UL Packet Access (HSUPA).

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

[0031] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use a new radio (NR) to establish an air interface 116.

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

[0033] In other embodiments, base station 114a and WTRUs 102a, 102b, 102c can implement the following radio technologies, such as IEEE 802.11 (i.e., WiFi), IEEE 802.16 (i.e., WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSMEDGE (GERAN), etc.

[0034] Figure 1ABase station 114b can be, for example, a wireless router, a home node B, a home eNode B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a commercial area, home, vehicle, campus, industrial facility, air corridor (e.g., for drone use), road, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or femtocell. Figure 1A As shown, base station 114b can have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0035] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. 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. CN 106 / 115 can 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... Figure 1A Although not shown, it will be understood that RAN104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as RAN 104 / 113 or a different RAT. For example, in addition to being connected to RAN 104 / 113, which can utilize NR radio technology, CN106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0036] CN 106 / 115 can also act as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT.

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

[0038] Figure 1B This is a system diagram illustrating example WTRU 102. (Example:) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmitting / receiving element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138, etc. It will be appreciated that WTRU 102 may include any sub-combination of the above-described elements while remaining consistent with the embodiments.

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

[0040] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmitting / receiving 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, transmitting / receiving element 122 can be configured to transmit and / or receive both RF and optical signals. It will be appreciated that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

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

[0042] Transceiver 120 can be configured to modulate signals to be transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As noted above, WTRU 102 can have multi-mode capability. Thus, for example, transceiver 120 may include multiple transceivers for enabling WTRU 102 to communicate, for example, via multiple RATs (such as NR and IEEE 802.11).

[0043] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keyboard 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data from them. The processor 118 can also output user data to the speaker / microphone 124, keyboard 126, and / or display / touchpad 128. Additionally, the processor 118 can access information from any type of suitable memory (such as non-removable memory 130 and / or removable memory 132) and store data in that memory. 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. Removable memory 132 may include a subscriber identity module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 can access information from memory that is not physically located on WTRU 102 (such as on a server or home computer (not shown)) and store data in that memory.

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

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

[0046] The processor 118 may be further coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, 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. Peripheral devices 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, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0047] 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 both 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 to reduce and / or substantially eliminate self-interference via signal processing performed via hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via processor 118). In one embodiment, WTRU 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)) may be concurrent and / or simultaneous.

[0048] Figure 1C The diagram illustrates a system diagram of RAN 104 and CN 106 according to one embodiment. As indicated above, RAN 104 employs E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 can also communicate with CN 106.

[0049] RAN 104 may include eNode-Bs 160a, 160b, and 160c, although it will be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, eNode-B 160a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a.

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

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

[0052] The MME 162 can connect to each of the eNode-Bs 162a, 162b, and 162c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies (such as GSM and / or WCDMA).

[0053] The SGW 164 can connect to each of the eNode Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during eNode B handover, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0054] SGW 164 can be connected to PGW 166, which can provide WTRU 102a, 102b, 102c with access to a packet-switched network (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

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

[0056] Despite WTRU in Figures 1A to 1D While described as a wireless terminal, it is envisioned that, in some representative embodiments, such a terminal may use (e.g., temporarily or permanently) a wired communication interface with a communication network.

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

[0058] In Infrastructure Basic Services Set (BSS) mode, a WLAN may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating outside the BSS destined for a STA can be reached via the AP and delivered to the STA. Traffic from a STA to a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via the AP, for example, where a source STA can send 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 sent between source and destination STAs (e.g., directly between them) using a direct link setup (DLS). In some representative embodiments, the DLS may use 802.11e DLS or 802.11z Tunneled DLS (TDLS). A WLAN using the Standalone BSS (IBSS) mode can exist without an access point (AP), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as the "ad-hoc" communication mode in this document.

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

[0060] High-throughput (HT) STAs can communicate using a 40MHz wide channel, for example, by combining a primary 20MHz channel with adjacent or non-adjacent 20MHz channels to form a 40MHz wide channel.

[0061] Very High Throughput (VHT) STAs can support channels with widths of 20MHz, 40MHz, 80MHz, and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining consecutive 20MHz channels. A 160MHz channel can be formed by combining eight consecutive 20MHz channels or by combining two non-consecutive 80MHz channels (which can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, data is passed through a segment resolver that divides the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing can be performed separately on each stream. The streams can be mapped onto two 80MHz channels, and the data can be transmitted by the STA performing the transmission. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0062] Operating modes below 1 GHz are supported by 802.11af and 802.11ah. The channel operating bandwidth and carrier used in 802.11af and 802.11ah are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to representative embodiments, 802.11ah can support instrument-type control / machine-type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support) certain and / or limited bandwidths. MTC devices may include batteries with a lifespan exceeding a threshold (e.g., to maintain a very long battery life).

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

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

[0065] Figure 1D The diagram illustrates a system diagram of RAN 113 and CN 115 according to one embodiment. As indicated above, RAN 113 may employ NR radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 113 may also communicate with CN 115.

[0066] RAN 113 may include gNBs 180a, 180b, and 180c, although it will be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. gNBs 180a, 180b, and 180c may each include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, gNB 180a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers can be on unlicensed spectrum, while the remaining component carriers can be on licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c can implement Cooperative Multipoint (CoMP) technology. For example, WTRU 102a can receive cooperative transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0067] WTRUs 102a, 102b, and 102c can use transmissions associated with scalable digitization. For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary depending on different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes of various or scalable lengths or transmission time intervals (TTIs) (e.g., containing different numbers of OFDM symbols and / or absolute times of varying durations).

[0068] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without access to other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate with / connect to gNBs 180a, 180b, and 180c, and simultaneously communicate with / connect to another RAN (such as eNode-Bs 160a, 160b, and 160c). For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c and one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-B 160a, 160b, and 160c can act as mobility anchors for WTRU 102a, 102b, and 102c, and gNB 180a, 180b, and 180c can provide additional coverage and / or throughput to serve WTRU 102a, 102b, and 102c.

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

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

[0071] AMF 182a and 182b can connect to one or more of the gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting specific SMF183a and 183b, managing registration areas, terminating NAS signaling, mobility management, etc. Network slices can be used by AMF 182a and 182b to customize CN support for WTRU 102a, 102b, and 102c based on the service types utilized by WTRU 102a, 102b, and 102c. For example, different network slices can be built for different use cases, such as services that rely on Ultra Reliable Low Latency (URLLC) access, services that rely on Enhanced Massive Mobile Broadband (eMBB) access, and services for Machine Type Communication (MTC) access. AMF 162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) employing other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[0072] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure service routes through UPFs 184a and 182b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

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

[0074] CN 115 can facilitate communication with other networks. For example, CN 115 may include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 115 and PSTN 108. Additionally, CN 115 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c can connect to local data networks (DNs) 185a and 185b via the N3 interface to UPFs 184a and 184b and the N6 interface between UPFs 184a and 184b and DNs 185a and 185b.

[0075] Given Figures 1A to 1D as well as Figures 1A to 1D The corresponding description may be performed by one or more emulation devices (not shown) to perform one or more of the functions described in the text with respect to one or more of the following: WTRU 102a to 102d, base stations 114a to 114b, eNode-B 160a to 160c, MME 162, SGW 164, PGW 166, gNB 180a to 180c, AMF 182a to 182b, UPF 184a to 184b, SMF 183a to 183b, DN 185a to 185b, and / or any other devices described herein. An emulation device may be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0076] Simulation devices can be designed to perform tests on one or more other devices in a laboratory environment and / or a carrier network environment. For example, one or more simulation devices can perform one or more or all of their 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 or all of their functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices can be directly coupled to another device for testing purposes and / or can use over-the-air wireless communication to perform tests.

[0077] One or more emulation devices may perform one or more functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, emulation devices may be used to test scenarios in a laboratory and / or non-deployed (e.g., testing) wired and / or wireless communication networks to enable testing of one or more components. One or more emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0078] This document describes systems, methods, and tools for acquiring synchronization and system information in energy-efficient networks associated with simplified synchronization leading to WUS and WUS leading to SSB measurements. Wireless Transmit / Receive Unit (WTRU) synchronization acquisition can be initiated by detecting a synchronization signal (SS). The WTRU can determine the timing and / or resource information of (multiple) pre-synchronization or DL-WUS-like signals, for example, based on simplified synchronization indications. Pre-synchronization or WUS signaling can provide indications of the timing of Network Energy Saving (NES) configuration information and system information.

[0079] The WTRU can receive a first signal. The first signal may include a simplified SS. The simplified SS may be a compressed SS. The first signal may indicate information associated with a second signal. The second signal may include a pre-synchronization signal (e.g., a wake-up signal (WUS), downlink WUS (DL-WUS)). The information associated with the second signal may be indicated based on one or more attributes or characteristics associated with the simplified SS (e.g., timing information, frequency information, phase information, sequence selection information). The first signal may indicate a simplified sequence that may indicate information associated with the second signal. The first signal may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), or a PSS and SSS (e.g., PSS and SSS only). In the example, the first signal may avoid including a physical broadcast channel (PBCH) block. The WTRU can determine the resources associated with receiving the second signal (e.g., the pre-synchronization signal, WUS, DL-WUS), for example, based on information associated with the second signal (e.g., indicated by the first signal). The WTRU can receive the second signal, for example, by using resources determined using information associated with the second signal. The second signal may include an indication associated with receiving an SSB. The SSB may include a PBCH block. The WTRU may determine information associated with receiving the SSB, for example, based on an indication associated with receiving the SSB (e.g., indicated by a second signal). The information associated with receiving the SSB may include one or more of the following: NES state, SSB periodicity, the presence of a complete SSB at a potential time of complete SSB transmission, etc. The WTRU may receive the SSB, for example, based on the determined information associated with receiving the SSB.

[0080] The WTRU can receive a synchronization signal (SS). The SS can be a simplified SS (e.g., a compressed SS). The SS can indicate a pre-synchronization signal. The SS can include a primary SS, a secondary SS, or a primary SS and a secondary SS. The WTRU can determine pre-synchronization signal information associated with the pre-synchronization signal (e.g., timing and / or resource information), for example, based on characteristics associated with the SS. The WTRU can receive the pre-synchronization signal based on the pre-synchronization signal information. The WTRU can determine SS and Physical Broadcast Channel Block (SSB) information, for example, based on the pre-synchronization signal. The WTRU can receive the SSB based on the SSB information. The WTRU can determine System Information Block (SIB) information. The WTRU can determine Random Access Channel (RACH) parameters, for example, based on SIB information.

[0081] Network energy saving (NES) processes can be used and / or enabled. Enhancements can be provided to enable the network to minimize its power consumption from transmission and reception. This minimization can help reduce operating costs and environmental sustainability.

[0082] When no data is available, NES designs can be (e.g., very) efficient (compared to earlier systems) from the perspective of minimizing transmissions from the network. For example, the use of (e.g., not using) a cell-specific reference signal (CRS) that is always on can be avoided. However, energy consumption can be reduced (e.g., there may still be potential for energy consumption reduction).

[0083] For example, a network can still consume energy when it avoids transmitting from other activities, such as baseband (e.g., digital) processing or waveform formation for reception (e.g., no transmission). In dense networks, this useless power consumption may not be negligible, for example, even when no WTRU is served during a given period (e.g., when no WTRU is served during a given period). If the network can shut down these activities when not transmitting to WTRUs, energy consumption can be reduced.

[0084] The transmission of always-on synchronization signals (e.g., synchronization signals or reference signals) can be avoided (e.g., it may not be necessary). Adaptable bandwidth and MIMO capabilities can be supported. Adaptation to network resources can achieve higher efficiency.

[0085] The following terms may be used.

[0086] Channel state information (CSI) may include at least one of the following: channel quality indicator (CQI), rank indicator (RI), precoding matrix indicator (PMI), L1 channel measurement (e.g., reference signal received power (RSRP) (such as L1-RSRP or SINR), CSI-RS resource indicator (CRI), synchronization signal (SS) / physical broadcast channel (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. The WTRU can report a subset of Channel State Information (CSI) components, which may correspond at least to the CSI-RS Resource Indicator (CRI), SSB Resource Indicator (SSBRI), indications of the receiving panel at the WTRU (such as panel identifier or group identifier), measurements such as L1-RSRP, L1-SINR obtained from the SSB or CSI-RS (e.g., cri-RSRP, cri-SINR, ssb-Index-RSRP, ssb-Index-SINR), and / or other channel state information such as at least rank indicator (RI), channel quality indicator (CQI), precoding matrix indicator (PMI), layer indicator (LI), etc.

[0087] Uplink control information (UCI) may include one or more of the following: 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 PUCCH or PUSCH.

[0088] Channel conditions may include (e.g., any) conditions related to the state of the radio / channel, which may be determined by the WTRU from one or more of the following: WTRU measurements (e.g., L1 / SINR / RSRP, CQI / MCS, channel occupancy, Received Signal Strength Indicator (RSSI), power margin, exposure margin), L3 / mobility-based measurements (e.g., RSRP, RSRQ, s-measure), radio link monitoring (RLM) status, and / or channel availability in unlicensed spectrum (e.g., whether the channel is occupied based on the determination of the LBT process, or whether the channel is considered to have experienced a sustained LBT failure).

[0089] Physical random access channel (PRACH) resources (e.g., in frequency), PRACH timing (RO) (e.g., in time), preamble format (e.g., in terms of total preamble duration, sequence length, guard time duration, and / or cyclic prefix length) and / or a preamble sequence may be used for preamble transmission during random access.

[0090] 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, Transport Configuration Indicator (TCI) status or Probe Reference Signal Resource Indicator (SRI), number of repetitions, whether the grant is configured grant type 1, type 2 or dynamic grant, etc.

[0091] The indication given by the downlink control information (DCI) (e.g., or indication) may include one or more of the following: explicit indication given by the DCI field or radio network temporary identifier (RNTI) (e.g., used to mask the cyclic redundancy check (CRC) of the PDCCH), implicit indication given by attributes (e.g., such as DCI format, DCI size, coreset or search space, aggregation level, identifier of the first control channel resource for the DCI (e.g., index of the first control channel element (CCE), wherein the mapping between attributes and values ​​may be signaled by RRC or MAC), explicit indication given by DL MAC CE, etc.

[0092] The terms “network availability status,” “cell shutdown,” “cell DTX mode / configuration,” or “NES status” are used interchangeably. WTRU can implicitly determine the cell DTX / DRX status from the determined active availability status, and vice versa.

[0093] In the following text, “a (a and an)” and similar phrases should be understood as “one or more” and “at least one”. Similarly, any term ending with the suffix “(s)” should be understood as “one or more” and “at least one”. The term “may” should be understood as “may, for example”.

[0094] The symbol “ / ” (e.g., a forward slash) can be used in this article to mean “and / or”, where, for example, “A / B” can mean “A and / or B”.

[0095] Beams can be defined.

[0096] A WTRU can transmit or receive a physical channel or reference signal, for example, based on at least one spatial filter. The term "beam" can be used to refer to a spatial filter.

[0097] The WTRU can use the same spatial filter used to receive RS (e.g., such as CSI-RS) or SS blocks to transmit physical channels or signals. The WTRU transmission can be referred to as the target. The received RS or SS block can be referred to as the reference block or source. In this case, the WTRU can (e.g., is considered to) transmit the target physical channel or signal based on the spatial relationship of the reference RS or SS block.

[0098] The WTRU can transmit the first physical channel or signal using the same spatial filter as the spatial filter used to transmit the second physical channel or signal. The first transmission and the second transmission can be referred to as the target and the reference (or source), respectively. In this case, the WTRU can (e.g., is considered to) transmit the first (e.g., target) physical channel or signal based on the spatial relationship of the reference second (e.g., reference) physical channel or signal.

[0099] Spatial relationships can be implicit or signaled (e.g., configured by RRC signaling, or signaled by MAC CE or DCI). For example, a WTRU can implicitly transmit PUSCH transmissions and PUSCH DM-RS based on the same spatial filter as the SRI indication indicated in the DCI or the SRS configured by RRC. In the example, the spatial relationship can be configured for the SRS resource indicator (SRI) (e.g., via RRC signaling) or signaled for the PUCCH (e.g., via MAC CE). This spatial relationship can also be referred to as a "beam indication".

[0100] The WTRU can receive a first (e.g., target) downlink channel or signal based on the same spatial filter or spatial reception parameters as the second (e.g., reference) downlink channel or signal. For example, this association can exist between a physical channel (such as PDCCH or PDSCH) and its respective DM-RS. This association can exist if the first and second signals are reference signals (e.g., at least when the first and second signals are reference signals), and if the WTRU is configured with Quasi-Co-location (QCL) assumption type D between the corresponding antenna ports (e.g., when the WTRU is configured with Quasi-Co-location (QCL) assumption type D between the corresponding antenna ports). This association can be configured as a TCI (Transmission Configuration Indicator) state. The WTRU can receive an indication (e.g., indicated) – the association between the CSI-RS or SS block and the DM-RS – via an index to a set of TCI states (e.g., configured by RRC signaling and / or signaled by the MAC CE). This indication can also be referred to as a “beam indication”.

[0101] In this document, SSB can refer to one or more SSB beams (e.g., spatial relationships) within an SSB set (e.g., an SSB burst). SSB can refer to a beam, or vice versa, or a CSI-RS associated with a beam. SSB, SSB, and / or SSB burst can refer to one or more beams transmitted from a transmit and receive point (TRP).

[0102] A TRP can be used interchangeably with one or more of a Transmitting Point (TP), Receiver Point (RP), Radio Remote Header (RRP), Distributed Antenna (DA), Base Station (BS), Sector (e.g., a sector of a BS), and / or Cell (e.g., a geographic cell area served by a BS). Multiple TRPs can be used interchangeably with one or more of MTRPs, M-TRPs, and multiple TRPs.

[0103] Discontinuous transmission (DTX) and discontinuous reception (DRX) can be performed and / or enabled.

[0104] A BS (e.g., a gNB) can use reduced downlink transmit / uplink receive activity without having restricted cell DTX / DRX modes (e.g., explicit cell DTX / DRX modes), for example, due to WTRU DRX configuration and any configured transmit / receive (e.g., common channels / signals). C-DRX can be configured per WTRU. Alignment of DRX periods or offsets for different WTRUs can be (e.g., only) done via RRC. During periods when WTRU DRX is off (e.g., inactive), the WTRU may not expect to monitor the PDCCH, but the WTRU can (e.g., is permitted) initiate UL transmissions based on configured resources (e.g., using PUCCH, RACH, SR, or CG-PUSCH). Alignment / omission of DRX modes across multiple WTRUs can be implemented, for example, via a gNB.

[0105] Cell DTX / DRX can provide (e.g., is intended to provide) a mechanism that notifies the WTRU whether the cell remains inactive. This can include enhancements to the WTRU DRX configuration for WTRUs in connected or idle / inactive modes (e.g., aligning / omitting DRX periods or DRX start offsets), which can allow for longer periods of cell inactivity. During cell DTX / DRX, the cell may not have transmit / receive or (e.g., only) maintain limited transmit / receive. For example, the cell may avoid transmitting or receiving (e.g., does not need to transmit or receive) certain periodic signals / channels (e.g., such as common channels / signals or WTRU-specific signals / channels).

[0106] Cell DTX / DRX can be applied at least to WTRUs in the RRC_CONNECTED state. Periodic cell DTX / DRX (e.g., active and inactive periods) can be configured by the gNB according to the serving cell via WTRU-specific RRC signaling. Cell DTX / DRX modes can be activated / deactivated via dynamic L1 / L2 signaling and WTRU-specific RRC signaling. WTRU-specific and / or general L1 / L2 signaling can be considered for activating / deactivating cell DTX / DRX modes. Cell DTX and DRX modes can be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). Cell DTX / DRX can also be configured and operated together. One or more of the following parameters can be configured according to the cell DTX / DRX configuration: periodicity, start timeslot / offset, activation duration, etc. In the example, the cell DTX indication can be part of an SI update or SIB signaling. There can be a common time for (e.g., all) WTRUs to determine the cell DTX state.

[0107] A WTRU can be configured with multiple cell DRX and / or cell DTX configurations (e.g., simultaneously in a given serving cell). A WTRU can be configured with a primary or default cell DTX and / or cell DRX configuration, which it can apply by default. Based on receiving signaling to activate one cell DTX and / or cell DRX configuration, a WTRU can deactivate another configuration (e.g., or all other configurations). Based on receiving signaling to deactivate one cell DTX and / or cell DRX configuration, a WTRU can activate another configuration or activate the default cell DTX / DRX configuration. Based on determining that a duration has elapsed (e.g., a timer expires), a WTRU can fall back to the default cell DRX and / or cell DTX configuration. A WTRU can reset this duration (e.g., via a timer), for example, based on receiving DL signaling or data or an indication from the NW, to maintain a given non-default cell DTX or cell DRX state.

[0108] Network availability status, cell DTX mode, and / or NES status can be considered and / or used.

[0109] NES status or availability status can refer to cell status in which at least one NES technology has been activated in the cell or TRP. NES technology may include one or more of the following: cell DTX, cell DRX, spatial domain adaptation (e.g., where a subset of antenna ports and / or components are turned off), power domain adaptation (e.g., where a subset of channels are transmitted at reduced power or muted), and / or the cell or TRP has been turned off.

[0110] The WTRU can determine whether it can transmit or receive on certain resources, for example, depending on network availability status (e.g., it can imply the gNB's power-saving status). Availability status can correspond to network power-saving status, cell DTX mode, cell DRX mode, and / or gNB activity level. Availability status can be uplink or downlink specific and can vary from symbol to symbol, from time slot to time slot, from frame to frame, or according to longer duration granularities. Availability status can be determined by the WTRU or indicated by the network. For example, availability status can be one or more of the following: “On,” “DL and UL active,” “UL active only,” “Off,” “Reduced Tx power,” “Sleep,” “Micro sleep,” “Light sleep,” or “Deep sleep.” Such states can be abstracted through NW configuration parameters and / or values. Dynamic indications can indicate the availability status of activity (e.g., via DCI or MAC CE signaling). A “Off” availability status can mean that the gNB's baseband hardware is completely off. A “Sleep” availability status can mean that the gNB periodically wakes up to transmit certain signals (e.g., presence signals, synchronization signals, or reference signals) or receive certain UL signals. In certain availability states, some DL or UL resources may be unavailable for certain time periods, which may allow the network to shut down baseband processing and other activities. For example, WTRUs may be configured with periodic active and inactive periods based on availability (e.g., via RRC signaling). Some measurement resources (e.g., SSB or CSI-RS) (e.g., only) may be available in certain availability states, such as, for example, RLM, BFD, RRM measurements, CSI-RS feedback configuration, and / or different power offsets for CSI feedback.

[0111] WTRU can send a request (e.g., a wake-up request) to the network (e.g., based on met conditions) to modify the availability state to a state for which resources that can satisfy the WTRU's requirements are available.

[0112] The WTRU can determine the availability status by receiving an availability status indication (e.g., via L1 / L2 signaling (e.g., group general DCI or indication)) or implicitly by receiving periodic DL signaling or the absence of such periodic DL signaling.

[0113] The WTRU can determine whether resources are available for transmission / reception and / or measurement in a determined network availability state (e.g., whether they are applicable in an active availability state). The WTRU can adapt its active C-DRX cycle, active spatial elements (e.g., antennas or logical ports), active TRPs, and paging timings according to the signaled or determined availability state. The WTRU can be configured with one or more sets of NES transmission and / or reception parameters according to the availability state, for example, via broadcast or dedicated configuration signaling. The WTRU can apply a set of NES parameters according to the determined or signaled availability state. The WTRU can apply one or more applicable configurations according to the determined NES state. The NES parameter set may include one or more of the following: number of antenna ports, C-DRX configuration, measurement configuration (e.g., for RRM, RLM, and / or BFD), CSI feedback, CSI-RS configuration, SSB configuration, CHO or mobility candidate, a set of active TRPs, etc.

[0114] Availability status can apply to at least one transmit, receive, or measure resource. Availability status can apply to at least one time period, such as a time slot or time symbol. Availability status can apply to a serving cell, cell group, frequency band, bandwidth portion, TRP, a set of spatial elements, or a series of frequencies within a bandwidth portion. For example, if the NES status changes in a cell (e.g., when the NES status changes in a cell), the WTRU can receive an availability status change indication that indicates that the change applies only to that cell, to all cells on the same frequency, and / or to the same RAT.

[0115] The WTRU can treat the active availability state associated with a cell, carrier, TRP, or frequency band as "off," "deep sleep," or "micro sleep," for example, after receiving DL signaling that changes the availability state of a cell or TRP. For example, the WTRU can receive a shutdown command on broadcast signaling, RRC signaling, DCI (e.g., group-general DCI), or DL ​​MAC CE (e.g., the indication portion of PDSCH). The WTRU can determine the availability state based on (e.g., via) availability state indications received from (e.g., via) L1 / L2 signaling (e.g., group-general DCI or indication) or broadcast signaling associated with the availability state.

[0116] For example, an availability status change indication could be part of an SI update or SIB signaling (e.g., in a separate SIB, which is not read by the WTRU). WTRUs within a cell (e.g., all WTRUs) may have a common time to determine the availability status.

[0117] The WTRU can determine a change in NES state by receiving group-general command L1 signaling (e.g., group-general DCI, multi-level DCI, specific DCI format, or DCI scrambled by a configured or specified NES-specific RNTI). The L1 signaling can indicate one of the sets of configured NES parameters to apply, or, after determining an NES state change, can determine an incremental (delta) configuration from the current parameter set. The WTRU can send feedback / acknowledgment to the gNB (e.g., possibly multiplexed with UL data (e.g., as part of a UL TB indicated by a MAC CE or subheader), for example, after receiving an NES state change indication.

[0118] The WTRU can determine a change in NES status by receiving broadcast signaling associated with an NES status indication or change (e.g., including signaling in (multiple) SIBs or portions of a broadcast or multicast PDSCH). Within the SIB, the WTRU can be indicated with the NES status (e.g., explicitly indicated). The WTRU can receive configuration information, including (e.g., configured with) one or more SIBs exclusively associated with NES parameters. The WTRU can receive configuration information (e.g., configured) to periodically receive such broadcast or multicast indications. The WTRU can determine that an indication has been falsely detected, for example, if the indication was not received at the expected periodic timing, if the number of false detections is counted, and / or if a certain amount of time has elapsed since the last NES status indication was received (e.g., via a timer). The WTRU can initiate inter-cell measurements, inter-frequency measurements, and / or inter-RAT measurements, initiate mobility procedures, and / or begin evaluating configured CHO candidates, for example, based on a determination made based on false detections of the NES status indication (e.g., after this determination).

[0119] The WTRU may implicitly assume an availability state (e.g., "off", "deep sleep", "micro sleep", or "dormant") associated with a cell, carrier, TRP, or frequency band by one or more of the following: receiving a command or signal indicating a change in availability state; receiving a paging message, paging DCI, paging PDSCH, or paging-related signal; gNB DTX status; no presence indication detected; based on time of day; based on the availability state of the relevant cell; detection of a PSS (e.g., PSS only) signal or a simplified / reduced SSB signal; detection of an RS signal or lack thereof; the WTRU's RRC status; whether a paging has been received (e.g., within a configured time window); whether system information has been received (e.g., within a configured time window); (multiple) measured channel conditions below or above a threshold, etc.

[0120] Based on, for example, receiving commands or signals indicating changes in availability status (e.g., group general DCI or RRC signaling or presence signals in connected mode), the WTRU can implicitly assume an availability status associated with a cell, carrier, TRP, or frequency band (e.g., "off", "deep sleep", "micro sleep", or "dormant"). The WTRU can implicitly determine the availability status by receiving periodic DL signaling. The WTRU can be configured (e.g., receiving configuration information indicating this) or specified to associate the availability status with one or more DL signal types (e.g., SSB, partial SSB, and / or one or more periodic signals).

[0121] Based on receiving, for example, a paging message, paging DCI, paging PDSCH, or paging-related signal (e.g., PEI), such as on a subset of POs (e.g., a configured subset of POs or PDCCH resources aligned with the NES DRX cycle), the WTRU may implicitly assume an availability state (e.g., "off", "deep sleep", "micro sleep", or "dormant") associated with a cell, carrier, TRP, or frequency band. Upon receiving an indication portion of a DCI or PDCCH scheduling paging, the WTRU may assume an availability state (e.g., based on a P-RNTI, NES-RNTI, or based on receiving an explicit indication, such as on a reserved bit). Upon receiving a paging message with a certain P-RNTI, a separately configured NES P-RNTI, or an NES group RNTI, the WTRU may assume an availability state. The WTRU may be configured with one or more PEI subgroups for NES, where each subgroup may be associated with one or more availability states. Upon receiving a PEI with an NES subgroup, for example, if the subgroup is configured with an availability state and / or associated with it, the WTRU may assume a certain availability state. An indication of the availability state or availability state switching may be indicated in the paging payload, for example, as a marker portion of the paging message or short message. This paging indication may further indicate an alternative cell to monitor paging when the cell receiving the signaling is in a closed, sleep, or NES state. This paging indication may further indicate or signal applicable reconfiguration parameters (e.g., for initial access, applicable PRACH resources, applicable SSB / RS timing, applicable SI period, and / or (multiple) applicable cells and associated availability states).

[0122] Based on, for example, the gNB DTX status (e.g., whether the gNB is active or the relevant activity timer is running), the WTRU can implicitly assume the availability status associated with the cell, carrier, TRP, or frequency band (e.g., "off", "deep sleep", "micro sleep", or "dormant").

[0123] Based on, for example, the absence of a presence indication, such as, for example, one or more of the following, the WTRU may implicitly assume an availability state associated with a cell, carrier, TRP, or frequency band (e.g., "off", "deep sleep", "micro sleep", or "dormant").

[0124] WTRU can determine the availability state associated with a cell (e.g., "off" or "deep sleep"), for example, if no presence indication is detected at one or more presence indication times.

[0125] After multiple consecutive false detections or after a period of time following the absence of a detected signal (e.g., timer expiration), the WTRU can assume or change the cell's availability state. The WTRU can determine whether the availability state is active or inactive (e.g., deactivated) after the duration associated with the availability state (e.g., timer expiration). This duration (e.g., via a timer) can be configured and / or maintained in connected mode (e.g., connected only), or it can be configured and / or maintained in other states (e.g., idle and inactive states).

[0126] The WTRU can implicitly determine the availability state, for example, by not receiving periodic DL signaling (e.g., for a given duration). For example, the WTRU may receive configuration information indicating (e.g., the WTRU may be configured to have) a signal quality threshold (e.g., an RSRP threshold). If the WTRU does not detect a signal with a signal strength above the threshold associated with the availability state (e.g., a presence signal or SSB), the WTRU can assume that the availability state is not active and can assume a different availability state. This criterion can also be coupled with an identification sequence of no presence signal detected (e.g., a detected PSS sequence).

[0127] Based on, for example, the time of day, the WTRU can implicitly assume an availability state (e.g., "off", "deep sleep", "micro sleep", or "dormant") associated with a cell, carrier, TRP, or frequency band. The WTRU can receive configuration information that instructs (e.g., the WTRU can be configured to) assume a certain availability state (e.g., off, sleep, or dormant) for a subset of cell configurations (e.g., capacity-enhancing cells) based on the time of day. For example, the WTRU can determine that a capacity-enhancing cell has an availability state such as "on" during certain hours of the day, "deep sleep" during other configured hours, and "off" during a third set of configured hours of the day or night.

[0128] Based on, for example, the availability status of the relevant cell (e.g., another carrier in the same MAC entity, another carrier in the same cell group, another carrier in the same gNB, another sector in the same gNB, or the configured relevant cell or capacity-enhancing cell), the WTRU may implicitly assume the availability status associated with the cell, carrier, TRP, or frequency band (e.g., "off", "deep sleep", "micro sleep", or "dormant").

[0129] Based on, for example, the detection of a PSS (PSS only) signal or a simplified / reduced SSB signal, the WTRU can implicitly assume the availability status associated with the cell, carrier, TRP, or frequency band (e.g., "off", "deep sleep", "micro sleep", or "dormant").

[0130] Based on, for example, the detection of an RS signal (e.g., CSI-RS, PRS, TRS) or the absence of such an RS signal, the WTRU may implicitly assume an availability state associated with a cell, carrier, TRP, or frequency band (e.g., "off", "deep sleep", "micro sleep", or "dormant").

[0131] Based on, for example, the RRC state of the WTRU (e.g., idle mode, inactive mode, or connected mode), the WTRU may implicitly assume an availability state associated with a cell, carrier, TRP, or frequency band (e.g., "off", "deep sleep", "micro sleep", or "dormant").

[0132] Based on, for example, whether a paging has been received (e.g., possibly within a configured time window), the WTRU may implicitly assume the availability state associated with a cell, carrier, TRP, or frequency band (e.g., "off", "deep sleep", "micro sleep", or "hibernate").

[0133] Based on whether system information has been received (e.g., periodic SI or SIB subsets) (e.g., possibly within a configured time window), the WTRU may implicitly assume the availability state associated with a cell, carrier, TRP, or frequency band (e.g., "off", "deep sleep", "micro sleep", or "dormant").

[0134] Based on, for example, multiple measured channel conditions being below or above a threshold, the WTRU can implicitly assume an availability state (e.g., "off", "deep sleep", "micro sleep", or "dormant") associated with a cell, carrier, TRP, or frequency band. The WTRU can assume a change in the NES state based on changes in measured channel conditions or causing channel measurements to be below or above a threshold. For example, the WTRU can use a degradation of SSB or CSI-RS measurements (e.g., possibly in conjunction with other signaling) to determine the NES state. For example, a configured window after DCI reception can be used to measure the degraded SSB and / or CSI-RS. If an increment in the SSB-RSRP is measured, the WTRU can determine that the NES state has changed and assume a relevant action for this NES state (e.g., triggering CHO candidate selection or group scheduling of mobility commands).

[0135] The WTRU can receive configuration information (e.g., be configured) to monitor indications that can characterize the level of network activity (e.g., availability status). Network activity can be associated with gNBs and / or cells. The WTRU can assume the same availability status for all cell portions of the same gNB (e.g., cells of the same MAC entity). Network activity indications (e.g., presence indications) can include channels (e.g., PDCCH) and / or signals (e.g., sequences). Activity indications or NES status change indications / commands can indicate an activity level that the WTRU can anticipate from the relevant gNB and / or cell, such as decreased activity. Activity indications can contain activity information from other gNBs / cells. Activity indications can be PDCCHs containing group-general signaling. For example, an NW can send a group-general DCI to a group of WTRUs (e.g., WTRUs in the serving cell) to indicate changes in activity status or activity level in the UL and / or DL. The CRC of the PDCCH can be scrambled using a dedicated activity indication RNTI or NES-RNTI. The WTRU can be configured with at least one search space associated with the monitoring timing of the activity indication PDCCH. Indicators may include sleep signals, such as predefined sequences. If the WTRU detects the sequence (e.g., when the WTRU detects the sequence), the WTRU can anticipate a reduction in activity levels over a specific duration. The WTRU can then activate C-DRX during the indicated time period. Multiple (e.g., two) sequences can be used to indicate both regular and reduced activity.

[0136] Signaling or activity indications within the PDCCH may include (for example, include) one or more of the following.

[0137] Signaling or activity indications within the PDCCH may include (e.g., contain) the expected activity level (e.g., availability status) of the relevant gNB / cell within a specific time interval. Activity levels can be predetermined and / or configured, and may include, for example, regular activity and degraded activity. Signaling can indicate activity levels. For example, a bit "1" can indicate regular activity, and a bit "0" can indicate degraded activity.

[0138] Signaling or activity indications within a PDCCH may include (e.g., contain) send and / or receive attributes for each activity level (e.g., availability status) (e.g., send and receive attributes may be defined). For example, during periods of reduced activity, the WTRU may avoid monitoring (e.g., not be expected to monitor) certain PDCCH search spaces (e.g., including all SS), and / or receive a certain type of PDSCH transport (e.g., including all PDSCH transports), and / or send PUCCH / PUSCH transports, and / or perform certain measurements. The WTRU may begin or stop monitoring PDCCH and / or TCI states associated with determined NES states, including PDCCH resources or TCI states associated with activated (deactivated) TRPs or space elements.

[0139] Signaling or activity indications within the PDCCH may include (e.g., contain) a set of configurations that may be associated with an activity level and can be used / applied when that activity level is indicated (e.g., NES parameter sets), such as, for example, SS configuration, CSI report configuration, index of the SSBs sent, etc. Each set of configurations may have attributes associated with the activity level, such as, for example, a label that can be set to "Decreased Activity".

[0140] The activity level, within which an assumed time interval can be transmitted via signaling, can be indicated using a bitmap, where each bit in the bitmap can be associated with a specific duration (e.g., a time slot or frame). For example, a bit "1" can indicate regular activity, and a bit "0" can indicate reduced activity on the relevant frame. The time interval can be indicated using a start time and an interval length. The start time can be defined, for example, by adding a fixed offset to the time the indication is received. The interval length can be configured in the indication PDCCH transmission or transmitted via signaling.

[0141] The time interval assumed within an activity level can be predetermined. WTRU can assume an interruption delay (e.g., the time until the NES state changes) after the NES state change command is received (e.g., after the last symbol or time slot on which the command was received). The interruption time can be expressed as absolute time, number of symbols, or number of time slots.

[0142] The WTRU can determine whether uplink or downlink resources or signals are available for transmission / reception and / or measurement in a determined network availability state, such as whether they are applicable in an active availability state. The WTRU can determine that a subset of measurement resources and / or signals (e.g., SSB, CSI-RS, TRS, PRS) are not applicable in certain availability states. The WTRU can determine that a subset of uplink or downlink resources (e.g., PRACH, PUSCH, PUCCH) are not applicable in certain availability states. The WTRU can (e.g., only) transmit some uplink signals in a subset of NW availability states (e.g., SRS, pSRS, PRACH, UCI).

[0143] Synchronization signals and processes can be enabled and / or provided.

[0144] Downlink synchronization can be performed.

[0145] Downlink synchronization may include: WTRU detecting radio frame boundaries (e.g., the exact timing at the start of a radio frame) and OFDM symbol boundaries (e.g., the exact timing at the start of an OFDM symbol). This process can be accomplished by detecting and analyzing synchronization signal blocks (SSBs).

[0146] The synchronization signal block and / or PBCH block may include a primary synchronization signal and a secondary synchronization signal (PSS, SSS). For example, these signals may occupy (e.g., each occupying) 1 symbol and 127 subcarriers, and the PBCH may span 3 OFDM symbols and 240 subcarriers, but on one symbol, an unused portion is reserved in the middle for the SSS, such as... Figure 2 As shown. The possible temporal location of an SSB within a half-frame can be determined by the subcarrier spacing, and the periodicity of the half-frame in which the SSB is transmitted can be indicated by the network (e.g., configured). During a half-frame, different SSBs can be transmitted in different spatial directions (e.g., using different beams, spanning the coverage area of ​​the cell).

[0147] Multiple SSBs can be transmitted within a carrier frequency span. The Physical Cell Identifier (PCI) of an SSB transmitted at different frequency locations may not be unique (e.g., it doesn't necessarily have to be unique); for example, different SSBs in the frequency domain can have different PCIs. However, if an SSB is associated with an RMSI (e.g., when an SSB is associated with an RMSI), the SSB can be referred to as the cell-defining SSB (CD-SSB). A PCell can be associated with a CD-SSB located on a synchronization grid.

[0148] Figure 2 The illustration shows an example time-frequency structure of SSB.

[0149] Polar coding can be used in PBCH.

[0150] WTRU can assume band-specific subcarrier spacing for SSB, for example, unless the network has configured WTRU to assume different subcarrier spacing.

[0151] PBCH transmission symbols can carry their own frequency-reused DMRS.

[0152] Quadrature phase shift keying (QPSK) modulation can be used for PBCH transmission.

[0153] Cell search can be performed and / or enabled.

[0154] Cell search can include: the WTRU acquiring time and frequency synchronization with the cell and detecting the cell ID. Cell search can be based on the primary synchronization signal, the secondary synchronization signal, and the PBCH DMRS located on the synchronization grid.

[0155] System information (SI) can be divided into a main information block (MIB) and multiple system information blocks (SIBs). The MIB can (e.g., always) be transmitted on the BCH (e.g., periodically every 80 ms and repeating within 80 ms) and can include parameters that can be used (e.g., are needed) to acquire SIB1 from the cell. SIB1 can be transmitted on the DL-SCH (e.g., periodically every 160 ms and with variable transmission repetition). The default transmission repetition period of SIB1 can be 20 ms. (e.g., in practice) The transmission repetition period can be determined by the network (e.g., depending on the network implementation).

[0156] MIB and / or SIB1 can constitute the minimum system information (MSI) for (e.g., required) operation on a cell.

[0157] For SSB and CORESET multiplexing mode 1, the SIB1 retransmission period can be 20 ms. For SSB and CORESET multiplexing modes 2 / 3, the SIB1 retransmission period can be the same as the SSB period. SIB1 can include information about the availability and scheduling of other SIBs (e.g., SIB-to-SI message mapping, periodicity, SI window size) and indications as to whether one or more SIBs are provided only as needed (e.g., the configuration used to perform SI requests for WTRUs in this case). SIB1 can be a cell-specific SIB.

[0158] SIB1 can be received.

[0159] The Master Information Block (MIB) on the PBCH transmission can provide parameters (e.g., CORESET#0 configuration information) to the WTRU for monitoring the PDCCH to schedule (multiple) PDSCH transmissions carrying System Information Block 1 (SIB1). PBCH transmissions can also indicate the absence of an associated SIB1. For example, in this case, the WTRU can be directed to another frequency from which to search for an SSB associated with SIB1, and a frequency range from which the WTRU can assume no SSB associated with SIB1. The indicated frequency range can be limited to consecutive spectrum allocations within the same operator where an SSB has been detected.

[0160] SSB indexes and SSB bursts can be executed and / or enabled.

[0161] Within an SSB burst set (e.g., all SSBs within a 5 ms period of SSB transmission), each SSB can be assigned a unique number (e.g., starting from 0 and incrementing by 1). This number can be reset to 0 in the next SSB burst set (e.g., after the SSB transmission period (e.g., after the default 20 ms period) for the next 5 ms time span). This unique number (e.g., the SSB index) can be indicated to the WTRU via the PBCH DMRS and via the PBCH payload (e.g., notification). Candidate SSBs in a half-frame can be indexed in ascending time order (e.g., from 0 to L-1). The WTRU can determine the 2 LSB bits (for L = 4) or 3 LSB bits (for L > 4) of the SSB index for each half-frame via a one-to-one mapping to the index of the DMRS sequence transmitted in the PBCH. For L = 64, the WTRU can determine the 3 MSB bits of the SS / PBCH block index for each half-frame via the PBCH payload bits.

[0162] Figure 3 The illustration shows an example SSB burst with a period of 20 ms. Figure 3 An example of SSB beam scanning within an SSB burst set is further illustrated.

[0163] Network power consumption can occur with SSB transmission.

[0164] A network may consume (e.g., is consuming) energy (e.g., unnecessary energy) when transmitting SSBs, for example, if this might be unnecessary (e.g., when this might be unnecessary) (e.g., especially in low-load scenarios where the network might save some energy if it does not transmit SSBs according to a fixed pattern and periodically). This can become more serious if the network is using a large number of beams (e.g., when the network is using a large number of beams). SSBs may (e.g., need to) be scanned in (e.g., all) beams along with necessary system information, for example, if the network is using a large number of beams.

[0165] SSB periodic broadcast requirements can limit (e.g., may disallow) gNBs from sleeping at longer intervals.

[0166] A gNB can avoid using (e.g., not use) long sleep cycles for its Tx and power amplifiers (e.g., which can consume a lot of power), for example, if cell / TRP transmissions (e.g., must be transmitted) have a fixed pattern and periodicity of SSBs. This situation can be problematic if network traffic allows for longer sleep cycles (e.g., when network traffic permits longer sleep cycles), but the network must keep the Tx and PA up and running to conform to the SSB pattern and periodicity.

[0167] The fixed broadcast periodic transmissions of SSB and SIB-1 can use (e.g., require) longer wake-ups of gNB, for example, even if there is no traffic / minimum traffic (e.g., when there is no traffic / minimum traffic).

[0168] System information transmission and retrieval can follow (multiple) fixed patterns for SSB and SIB-1. These patterns can simplify system information retrieval for WTRUs (e.g., after power-on). Patterns can lead to a burden on network power consumption (e.g., a very large burden) and / or make it difficult for gNBs to have a sufficiently long DTx.

[0169] System information can be obtained using WTRU power consumption.

[0170] SSB and SIB-1 transmission modes may (e.g., require) a longer time for the WTRU to acquire minimum system information. In some cases, the WTRU may have information that may have already been provided by other cells (e.g., partially), but it may (e.g., require) to acquire system information from the cells.

[0171] Longer cell search times for broadband carriers can be enabled and / or provided.

[0172] Networks can (e.g., are permitted) transmit SSBs across (e.g., any) frequency span of a carrier. This flexibility can be advantageous for network scheduling and operation. Wideband carriers and flexible SSB transmission locations in the frequency domain can result in very long initial cell searches for the WTRU. Since carrier bandwidth can be extremely large in the FR2 and sub-GHz bands, the time required to locate / detect an SSB (e.g., which can be a fraction of the carrier bandwidth in the frequency domain) can be considerably long, which can negatively impact user experience.

[0173] Simplified synchronization signal reception can lead to the monitoring and / or reception of pre-synchronization signals (e.g., wake-up signals (WUS)). Pre-synchronization signal (e.g., WUS) reception can lead to (multiple) SSB measurements (e.g., SSB reception).

[0174] Figure 4 Examples of simplified synchronization signal (e.g., PSS and / or SSS) transmission and SSB transmission are illustrated.

[0175] WTRU synchronization acquisition may include (e.g., starting with): detection (e.g., receiving) of a simplified SS (e.g., a first signal, which may include a PSS or a PSS and an SSS), for example, (e.g., as...) Figure 4 As shown, for example, rows 2 through 4 illustrate examples of PSS / SSS transmissions, compared to row 1, which illustrates an example SSB design (e.g., a legacy SSB design) (where (multiple) SSBs can be sent according to a given periodicity).

[0176] The WTRU can determine information (e.g., timing and / or resource information, such as resources) for pre-synchronization or DL-WUS type signals (e.g., for receiving a second signal, such as a pre-synchronization signal or a DL-WUS type signal). This information can be determined based on simplified synchronization (SS) indications (e.g., implicit or explicit indications).

[0177] Pre-synchronization or WUS signaling (e.g., a second signal) can provide an indication of receiving the synchronization signal block (SSB), such as NES configuration information and / or timing for complete system information.

[0178] Using a lower power Tx / PA to send to a simplified synchronous / pre-synchronous network can save power (e.g., additional power).

[0179] WTRU can receive a reduced version of SS (e.g., a compressed SS). The reduced version of SS may include PSS (e.g., alone) or PSS and SSS (e.g., as...). Figure 4As shown, row 2 illustrates an example where two simplified SSs (e.g., PSS / SSS) can be sent within an SSB period, and each simplified SS can be associated with a WUS signal; row 3 illustrates an example where a simplified SS and associated WUS transmission follow an SSB transmission; and row 4 illustrates an example of a simplified SS transmission within an extended SSB period.

[0180] The WTRU can decode the simplified synchronization signal (e.g., the first signal). The simplified SS can indicate (e.g., the simplified sequence associated with the simplified SS, such as PSS and / or SSS, and can indicate (e.g., by attributes associated with the simplified sequence)) the second signal (e.g., the pre-synchronization signal, such as the DL-WUS signal).

[0181] The WTRU can determine information associated with the second signal (e.g., timing and / or resources for the pre-synchronization signal, such as a DL-WUS signal), for example, based on a simplified SS indication (e.g., determining resources associated with receiving the second signal based on information associated with the second signal indicated by the first signal). The WTRU can determine whether to receive the second signal at the same or different frequencies based on indications received via the first signal. For example, the time, frequency, phase, or sequence selection associated with the simplified synchronization signal can be provided explicitly or implicitly with information associated with the second signal (e.g., the pre-synchronization or DL-WUS signal). In examples (e.g., where explicit information is provided), attributes of the simplified synchronization signal (e.g., suitable attributes) can include and / or indicate a mapping to physical resources or attributes of the second signal. For example, a first sequence used in the simplified sequence can indicate (e.g., to the WTRU) a first periodicity and a first offset for transmission to the second signal. A second sequence (e.g., if used) can indicate a second periodicity and a second offset. In example designs with implicitly provided information, attributes (e.g., reduced sequence time resources, frequency resources, phase or sequence selection) can indicate the active NES state of the cell. The WTRU can know the periodicity and offset for the second signal transmission (e.g., through (pre-)configuration or specification), and therefore, based on the indicated NES state, can determine the information required to receive DL-WUS (e.g., resources and configuration, etc.).

[0182] The WTRU can receive (e.g., detect) a pre-synchronization signal (e.g., DL-WUS), for example, based on a second signal indicated by a first signal (e.g., such as...). Figure 4Information associated with the data (as shown in rows 2 through 4) (e.g., timing information, resource information, frequency information, sequence information) (e.g., based on determined timing and / or frequency resources (e.g., by determined resources)). The WTRU can decode pre-synchronization (e.g., DL-WUS) signals, which may indicate information associated with the received SSB (e.g., cell NES state, SSB periodicity, and / or the presence of a complete SSB at a potential full SSB transmission time) (e.g., providing an indication of this information to the WTRU).

[0183] The WTRU can locate and / or receive the SSB, for example, based on an indication indicated by a second signal (e.g., a pre-synchronization signal indication, such as a DL-WUS signal indication). The WTRU can decode the PBCH transmission associated with the SSB, for example, based on information determined from the indication indicated by the second signal.

[0184] The WTRU can determine the timing and resources (e.g., information) for SIB-1 transmissions, such as based on PBCH information (e.g., indicated by the decoded PBCH transmission).

[0185] WTRU can be based on the identified resources (e.g., based on information indicated in the SSB, such as...). Figure 4 The WTRU decodes SIB-1 (e.g., multiple additional system information blocks). The WTRU can determine the RACH parameters (e.g., for RACH transmission). The WTRU can then send a RACH preamble based on the determined RACH parameters (e.g., to network nodes), for example, as part of the initial access procedure.

[0186] WUS signals can provide information and transmission modes for simplified synchronization signals and / or SSB transmissions.

[0187] WTRU synchronization acquisition can begin by receiving WUS signals from the network (e.g., initially).

[0188] WTRU can determine the SSB structure (e.g., structure type, such as simplified SSB or full SSB) during a network NES state (e.g., inactive state) based on the attributes of the received DL-WUS, such as based on the received pre-synchronization sequence (e.g., DL-WUS) indication.

[0189] After detecting / decoding the pre-synchronization signal (e.g., successful detection / decoding of the pre-synchronization signal (e.g., WUS), the WTRU can determine (e.g., know) the SSB timing, periodicity, transmit power, frequency allocation, number of SSB beams in each burst, and / or the content of the SSB (e.g., PSS, SSS, PBCH, SIB1), for example, at least during the NES sleep cycle, and / or the NES state of the cell.

[0190] Pre-synchronization (WUS) can be transmitted across multiple frequency spans within a carrier (e.g., for a wideband carrier), which can, for example, accelerate the initial cell search.

[0191] WTRU can monitor and receive DL signals from the network (e.g., DL-WUS).

[0192] The WTRU can determine that one or more SSBs (e.g., a simplified SSB or a full SSB) are sent and / or may be received at an upcoming SSB transmission time in the first SSB cycle (e.g., the NES cycle), for example, based on the receipt of DL-WUS.

[0193] The WTRU can determine the SSB structure type (e.g., a simplified SSB structure or a full SSB structure) for monitoring and / or reception during the first SSB cycle, for example, based on at least one attribute of the received or decoded DL-WUS.

[0194] The attributes of DL-WUS may include one or more of the following: modulation type (e.g., OOK and OFDM), timing or frequency of receiving DL-WUS, sequence type (e.g., ZC or M), sequence index, channel coding type, or the content of the embedded message.

[0195] SSB structure types may include at least one of the following: time-compressed SSB (e.g., with PBCH / SIB1 multiplexed in the frequency domain), power-reduced SSB, narrowband SSB, SSB burst with reduced number of SSB beams per burst, SSB without PBCH, or SSB with a second periodicity compared to the first SIB-1 periodicity (for accompanying SIB-1).

[0196] The WTRU can receive the SSB during the transmission of the first SSB cycle, for example, based on the determined SSB structure.

[0197] The WTRU can receive PBCH transmissions and / or one or more SIBs (e.g., at least one of which), for example, based on the receipt of an SSB.

[0198] The WTRU can send a preamble (e.g., based on the received SSB and information received in the PBCH and / or at least one SIB).

[0199] WTRU can assume the same SSB structure during the first cycle until another DL-WUS is received.

[0200] The first SSB cycle can be nondeterministic and / or used when the cell is in NES state.

[0201] The second SSB cycle can be deterministic and / or used when the cell is not in NES state.

[0202] Information from a compact minimum system can be received, signaled, provided, and / or used.

[0203] The network can send minimal system information (e.g., compact minimal system information), which may include at least an SSB (e.g., PSS + SSS + MIB (PBCH block / transmission)) or an SI digest.

[0204] SI summaries can include {MSI summaries (MIB+SIB-1), other SI summaries}.

[0205] An SI summary may include a value or a set of values.

[0206] The WTRU can connect to the serving cell. The serving cell can provide the WTRU with system information about the neighboring cell Cx and a corresponding SI summary of the system information provided to the WTRU (e.g., the WTRU can receive the SI and / or first SI summary associated with the neighboring cell). The SI summary may include a value or a set of values.

[0207] WTRU can perform cell reselection on cell Cx (e.g., neighboring cells).

[0208] The WTRU can receive and / or decode transmissions in cell Cx. Transmissions associated with cell Cx may include the C-MSI of cell Cx. The WTRU can determine the SI digest (e.g., a second SI digest) from the C-MSI.

[0209] C-MSI may include SSB (e.g., PSS, SSS, PBCH block / transfer) and / or SI digest.

[0210] CMSI may include an SI summary and at least one of the PSS, SSS, and PBCH blocks.

[0211] The WTRU can compare SI digests to verify whether they match the stored SI digests of cell Cx (e.g., to determine whether a first SI digest received from the serving cell matches a second SI digest indicated by a transmission received from a neighboring cell (e.g., cell Cx)) (e.g., to determine whether a new SIB-1 and / or other SIBs are needed (e.g., based on the determination that the first SI digest does not match the second SI digest)).

[0212] The WTRU can receive / decode SIB-1 from cell Cx (e.g., neighboring cells) to obtain the RACH parameters of cell Cx, for example, if the SI digest does not match the stored SI digest of cell Cx.

[0213] If the SI digests match, the WTRU may already have the RACH parameters for cell Cx (e.g., the WTRU can determine the RACH parameters based on the first SI digest and the second SI digest (e.g., if the two digests match each other)).

[0214] The WTRU can use the RACH on cell Cx for transmission, for example, based on RACH parameters. The WTRU can indicate other stored SI digests, so that the network knows what system information the WTRU has (e.g., in Msg1 / 3 / MsgA).

[0215] The network can provide incremental system information related to the "other SI summaries" indicated by WTRU.

[0216] C-MSI reception can be based on a first SSB period, which can be nondeterministic or NES period.

[0217] SIB-1 reception can be based on a second SSB cycle, which can be deterministic, complete, or non-NESSSB cycle.

[0218] A cell DTX activity period can include a time period during which the cell DTX mode is configured to be active (e.g., the time period during which the cell DTX mode is enabled). The WTRU can receive configuration information indicating the cell DTX activity period and can monitor the PDCCH and other DL signals and channels during this time. This may be applicable (e.g., only after the cell DTX configuration has been indicated as active by the NW).

[0219] Cell DTX inactivity periods can include a time period during which the cell DTX mode is configured to be inactive / inactive (e.g., a period outside the periodic on duration of the cell DTX mode). This may apply (e.g., only after the cell DTX configuration has been indicated as active by the NW).

[0220] A cell DRX activity period can include a time period during which the cell DRX mode is configured to be active (e.g., the time period during which the cell DRX mode is enabled). The WTRU can receive configuration information that instructs (e.g., predefined as allowed) to transmit a UL signal on the UL channel during this time. This may apply (e.g., only after the cell DRX configuration has been indicated as active by the NW).

[0221] A cell DRX inactivity period can include a time period during which the cell DRX mode is configured to be inactive / inactive (e.g., a period outside the periodic on duration of the cell DRX mode). This may apply (e.g., only after the cell DRX configuration has been indicated as active by the NW).

[0222] Activated cell DRX / DTX may include the state of configuring cell DRX or cell DTX mode, for example, where such state has been activated by L1 / L2 DL signaling, RRC (re)configuration and / or cell general configuration and has not been deactivated.

[0223] The deactivated cell DRX / DTX can include the state of the cell DRX or cell DTX mode, where such state has been deactivated by L1 / L2 DL signaling, RRC (re)configuration and / or cell general configuration.

[0224] There may be relationships between availability status, NES status, and cell DTX / DRX, for example, so that the terminology can be used interchangeably. The WTRU can implicitly determine the cell DTX status from the determined active availability status, and vice versa. The WTRU can implicitly determine the cell RTX status from the determined active availability status, and vice versa.

[0225] The terms "alternative cell" and "stable cell" are used interchangeably (e.g., as described herein). The WTRU may receive configuration information indicating (e.g., configured with) a list of stable cells (e.g., alternative cells that may not be shut down, such as macro cells). This list may be a list of each serving cell / campus cell or a general list of PCIs for the entire NW, tracking area, etc. (e.g., either of these lists). The WTRU may also receive configuration information having (e.g., configured with) the measurement object configuration of the alternative cells.

[0226] System information transmission and retrieval can be performed and / or enabled.

[0227] Synchronization signal transmission can use low-power Tx and / or power amplifiers: the gNB can be equipped with a low-power transmitter and / or power amplifier (PA). Synchronization sequences (e.g., including SSBs or sequences as described herein) can be transmitted by the gNB, for example, using low-power Tx and / or PA.

[0228] The gNB transmission of the synchronization signal can use a low-power Tx, and the PA can be associated with the cell's NES state. In the example, the synchronization signal can be transmitted using a low-power Tx and PA, for example, if the relevant cell is in an NES inactive state (e.g., when the relevant cell is in an NES inactive state). The synchronization signal can also be transmitted using a normal Tx and PA, for example, if the relevant cell is in an NES active state (e.g., when the relevant cell is in an NES active state).

[0229] Simplified synchronization structures for NES (e.g., low-power gNB Tx and PA) can be used and / or provided.

[0230] SSB designs for narrowband carriers can be used (e.g., for FR1).

[0231] WTRUs can be predefined or preconfigured to have an SSB structure, such as including PSS, SSS, and / or PBCH blocks. These signals in the structure can occupy the same frequency coverage area; for example, they can span the same number of Physical Resource Blocks (PRBs). The network can use the same structure for all (e.g., all) SSBs in its SSB burst set.

[0232] The synchronization sequences for PSS and SSS can each occupy 11 PRBs in the frequency domain and one OFDM symbol. A frequency span of 11 PRBs can be used (e.g., helpfully) to reuse the same PSS / SSS sequence. To allow the use of MIB / PBCH (e.g., similar to the case where PBCH is mapped via 48 PRBs), the updated SSB structure can use 4 OFDM symbols, resulting in 44 PRBs available for PBCH (e.g., as in the case where PBCH is mapped via 48 PRBs). Figure 5 (As shown on the left-hand side (LHS)). For the same power SSB transmission, a PBCH with 44 PRBs can have almost no coverage reduction (e.g., because it can have lower redundancy for the PBCH for the same number of PBCH information bits and PBCH DMRS).

[0233] Five (5) OFDM symbols can be allocated to the PBCH, for example, to avoid PBCH coverage loss (e.g., compared to legacy designs). This SSB structure (e.g., using 5 OFDM symbols) can result in 55 PRBs available for the PBCH (e.g., as...). Figure 5 (As shown on the right side). For the same number of PBCH information bits and PBCH DMRS, the availability of 55 PRBs for the PBCH can result in improved coverage compared to the legacy design.

[0234] Figure 5 An example of PSS, SSS, and PBCH in 11 PRBs (e.g., PSS / SSS length) with an additional PBCH symbol is illustrated, where there are 44 PRBs for PBCH on the left-hand side and 55 PRBs for PBCH on the right-hand side.

[0235] The proposed design (e.g., as described herein) can leverage the reuse of PBCH processing from other (e.g., legacy) designs. Mapping adjustments for different numbers of PRBs can be easily implemented by limiting updates to rate-matched blocks used for PBCH processing. The polar coding of PBCH can produce 512 bits (e.g., which can be the input to a rate-matched block). Rate-matched blocks can then increase these bits to 864 bits (e.g., 432 QPSK symbols).

[0236] 48 PRB * 12 * ¾ (1 / 4 DMRS) can be equal to 432 resource elements.

[0237] The rate matching block can be updated, for example, to provide for 4 symbols (e.g., Figure 5 (on the left side) or 5 symbols (e.g., on the left side) or 5 symbols. Figure 5 The PBCH bit mapped on the right-hand side.

[0238] The frequency occupancy range of the SSB can differ from that of 11 PRBs. This design allows for the selection of PSS and SSS with lengths different from other (e.g., legacy) SSB designs. For systems operating on narrowband carriers, the frequency span can be reduced, and appropriate PSS and SSS sequences can be selected. The number of symbols used for PBCH transmission can be further increased to achieve a certain level of coverage.

[0239] In the examples, in complementary designs (e.g., more suitable for wideband carriers), the frequency occupancy range of the SSB can be increased to a suitable value greater than 11 PRBs. Longer PSS and SSS sequences can be used with such SSBs. In the examples, the PSS / SSS sequences can be repeated in the frequency domain to achieve an appropriate length. The PBCH can use the same or different numbers of OFDM symbols in such SSB designs.

[0240] In the example, the network can use low-power gNB Tx and PA to transmit the updated structure. This can be beneficial for network energy saving purposes, for example, because the gNB can turn off its normal / high-power Tx and PA for longer time intervals.

[0241] In the example, the WTRU can be predefined or preconfigured to receive SSBs sent from a normal Tx / PA or a low-power Tx / PA.

[0242] In the example, the WTRU can be predefined or preconfigured to receive both legacy SSB structures and proposed SSB structures (e.g., simultaneously). The use of the SSB structure can be associated with the cell's NES state. When the cell is in an NES active state, the SSB can be transmitted using the legacy structure. When the cell is in an NES inactive state, the SSB can be transmitted using the proposed structure.

[0243] If the WTRU knows the cell's NES state (e.g., determines the cell's NES state), it can use an appropriate SSB structure to receive synchronization signals. If the WTRU does not know the NES state of the cell to which it is attempting to decode the SSB, it can attempt to decode the SSB from legacy structures and proposed structures (e.g., blind decoding). The WTRU can deduce whether the cell's NES state is active or inactive, for example, by decoding the SSB structure in use. Detection of the structure, based on predefined or network configurations, can indicate that the network is not applying the NES state or is in an active NES state. Detection of the proposed structure can indicate that the cell is in an inactive NES state.

[0244] In the example, the WTRU can be predefined or preconfigured to receive different SSB structures for different frequency ranges or bands. In this example, different SSB designs could be defined for FR1 and FR2.

[0245] For example, FR1 can maintain longer coverage time (e.g., more OFDM symbols, since fewer beams typically need to be scanned in FR1). The proposed design can be used for FR1, and it is possible to update the SSB burst structure.

[0246] The proposed SSB structure can be used with SSB-SSB burst mapping, for example, by limiting (e.g., only) an SSB transmission to (e.g., one) subframe / slot. For this purpose, the start symbol of the first legacy SSB mapping can be used as the first start symbol of the proposed SSB structure. In the example, the (e.g., new) mapping of SSBs within the SSB burst set can be designed specifically for the proposed SSB structure.

[0247] The proposed design can be used for narrowband carriers and / or reassigned frequencies. These carriers / frequency ranges can be (e.g., typically) low to medium bandwidth. The proposed design with a smaller frequency span (e.g., compared to other (e.g., legacy) designs) can accommodate SSBs in such carriers / frequency ranges (e.g., which may be meaningful). The (e.g., default) SSB structure can be defined in (e.g., per) frequency bands, which the WTRU can take for initial access (e.g., at least). The network can override the (e.g., default) SSB structure, for example, by indicating it in system information or configuration information. This may be feasible for cells that cannot be designed to provide initial access to the WTRU, or if the WTRU is configured (e.g., blindly) to detect and decode the SSB structure (e.g., when the WTRU is configured (e.g., blindly) to detect and decode the SSB structure).

[0248] The SSB design can be used for narrowband carriers and is also applicable to FR1.

[0249] WTRUs can be predefined or preconfigured to have an SSB structure, which may include, for example, PSS, SSS, and PBCH. Signals within the structure can occupy the same frequency coverage area; for example, they can span the same number of Physical Resource Blocks (PRBs). The network can use the same structure for all (e.g., all) SSBs within its SSB burst set.

[0250] The synchronization sequences of PSS and SSS can (e.g., each) occupy 11 PRBs and one OFDM symbol in the frequency domain. To reuse the PSS / SSS sequences (e.g., from other (e.g., legacy) designs), the frequency span can (e.g., remain) 11 PRBs.

[0251] The proposed SSB design can be used by the network for cells in NES state with reduced transmission power. The design can use the repetition of PSS and SSS as part of the SSB structure, for example, to overcome coverage loss. Figure 6 The illustration shows an example SSB design. (Example:) Figure 6As shown, the SSB may include multiple (e.g., two) repetitions of the PSS, (e.g., two) repetitions of the SSS, and six OFDM symbols (e.g., composed of them) for PBCH transmission.

[0252] Figure 6 Examples of PSS, SSS, and PBCH are illustrated, limited to 11 PRBs with an additional (N) PBCH symbol (R-15PSS / SSS length).

[0253] Figure 6 An example of the number of PSS / SSS repetitions and the number of symbols used for PBCH transmission is shown. The appropriate number of PSS / SSS repetitions can be selected for the proposed SSB design. The number of repetitions can depend on the allowable power level of the gNB Tx and the appropriate coverage area that the network expects for SSB transmission coverage of the cell. The number of repetitions can also depend on the frequency occupancy range of the SSB.

[0254] Motivations for the proposed design may include reusing PBCH processing from other (e.g., legacy) designs. Mapping adjustments for different numbers of PRBs (e.g., compared to other (e.g., legacy) designs) can be easily achieved by limiting updates to rate-matching blocks used for PBCH processing. Rate-matching blocks can be updated, for example, by providing PBCH bits for a selected target number of symbols and PRBs.

[0255] In the example, the frequency occupancy range of the SSB can differ from 11 PRBs. This design allows for different PSS and SSS selections for lengths compared to other (e.g., legacy) SSB designs. For systems operating on narrowband carriers, the frequency span can be reduced, and appropriate PSS and SSS sequences can be selected. The number of symbols used for PBCH block transmissions can be further increased to achieve a certain level of coverage.

[0256] In examples (e.g., designs better suited to wideband carriers), the frequency occupancy range of the SSB can be increased to a suitable value greater than 11 PRBs. Longer PSS and SSS sequences can be used with such SSBs. In example designs, legacy PSS / SSS sequences can be repeated in the frequency domain to achieve an appropriate length. The PBCH can use the same or different number of OFDM symbols in such SSB designs.

[0257] In the example, the network can use low-power gNB Tx and PA to transmit the updated structure. This can be beneficial for network energy saving purposes, for example, because the gNB can turn off its normal / high-power Tx and PA for longer time intervals.

[0258] In the example, the WTRU can receive configuration information that indicates (e.g., is predefined or preconfigured) to receive SSBs sent from the Tx / PA (e.g., a normal Tx / PA or a low-power Tx / PA).

[0259] In the example, the WTRU can receive configuration information indicating (e.g., predefined or pre-configured) the reception of another (e.g., legacy) SSB structure and the proposed SSB structure (e.g., simultaneously). The use of the SSB structure can be associated with the cell's NES state. The SSB can be transmitted using other (e.g., legacy) SSB structures, for example, if the cell is in an NES active state (e.g., when the cell is in an NES active state). The SSB can be transmitted using the proposed structure, for example, if the cell is in an NES inactive state (e.g., when the cell is in an NES inactive state).

[0260] The WTRU can use an appropriate SSB structure to receive multiple synchronization signals, for example, if the WTRU knows the cell NES state (e.g., based on a determined cell NES state). The WTRU can (e.g., attempt) decode SSBs from other structures (e.g., legacy structures) and the proposed structure (e.g., blind decoding), for example, if the WTRU does not know the NES state of the cell it is attempting to decode the SSB for. The WTRU can deduce whether the cell NES state is active or inactive, for example, by decoding the SSB structure in use. Detection of other (e.g., legacy) structures can indicate that the network avoids applying (e.g., does not apply) the NES state or is in an NES active state (e.g., according to a predefined or network configuration). Detection of the proposed structure can indicate that the cell is in an NES inactive state.

[0261] The proposed structure (e.g., as described herein) can be used (e.g., is well-suited for) scenarios where the network can employ other (e.g., legacy) or proposed SSB structures, and the WTRU can (e.g., needs) perform blind detection and decoding of SSBs of any structure. This can be based on design similarity, where the first symbol of the SSB carries the PSS and the third symbol carries the SSS. Therefore, the commonality in the transmission of these two signals can (e.g., help) improve blind detection / decoding processing for both legacy and proposed SSB structures.

[0262] In the example, the WTRU can be predefined or preconfigured to receive different SSB structures for different frequency ranges or bands. In this example, different SSB designs could be defined for FR1 and FR2.

[0263] For example, FR1 can maintain a longer coverage time, such as more OFDM symbols, because fewer beams may typically need to be scanned in FR1. The proposed design can be used for FR1 and, for example, it is possible to update the SSB burst structure.

[0264] The proposed SSB structure can be used with (e.g., legacy) SSB-SSB burst mappings, for example, by limiting (e.g., only) a (e.g., one) SSB transmission to (e.g., one) subframe / slot. For this purpose, the start symbol of the first (e.g., legacy) SSB mapping can be used as the first start symbol of the proposed SSB structure. In different designs, (e.g., new) mappings of SSBs within the SSB burst set can be designed specifically for the proposed SSB structure.

[0265] The proposed design can be used for narrowband carriers and / or reallocated or reused spectrum / frequency carriers. These carriers / frequencyes can be (e.g., typically) low to medium bandwidth. The proposed design with a smaller frequency span (e.g., compared to legacy designs) can be used to accommodate SSBs in such carriers / frequencyes. (e.g., default) SSB structures can be defined in (e.g., per) frequency bands, which the WTRU can take for initial access (e.g., at least). The network can override the SSB structure (e.g., the default SSB structure), for example, by indicating it in system information or configuration information. This may be feasible for cells that cannot provide initial access to the WTRU (e.g., cannot be intended to provide initial access to the WTRU), or if the WTRU is configured (e.g., blindly) to detect and decode the SSB structure (e.g., when the WTRU is configured (e.g., blindly) to detect and decode the SSB structure).

[0266] A simplified synchronization structure for NES (e.g., FR2) can be used and / or provided.

[0267] In the example, the network can send a compressed synchronization signal structure. This compressed synchronization signal structure can be referred to as a simplified synchronization. A simplified synchronization signal can include (for example, a time-compressed version of a legacy SSB). Figure 7 The proposed design for simplified synchronization is illustrated. The design can span multiple (e.g., two) OFDM symbols. The PSS can be transmitted in the first OFDM symbol, followed by the SSS in the second OFDM symbol. PBCH transmissions can be transmitted over both OFDM symbols, on the lower and upper frequency portions. Appropriate numbers of PRBs on the lower and upper sides of the PSS / SSS sequence can be used to transmit (multiple) PBCH transmissions.

[0268] To keep the PSS / SSS sequence design and PBCH processing / decoding as close as possible to other designs (e.g., legacy designs), the PSS and SSS can span 11 PRBs (e.g., where the lengths of the PSS and SSS can be 127 (e.g., as in legacy designs)). The top and bottom 12 PRBs (e.g., each) can be dedicated to PBCH transmission. This results in 12*4 = 48 PRBs for PBCH transmission (e.g., as in legacy SSBs). This allows for (e.g., complete) reuse of the transmit / receive chain for PSS / SSS and PBCH transmission, except for minor variations in the mapping to different PRBSs in the proposed design. This can lead to multiple (e.g., 2) symbol-simplified synchronization designs with a frequency span of 35 PRBs.

[0269] 12 (PBCH) + 11 (SS) + 12 (PBCH) can equal 35 PRBs.

[0270] In the example, the frequency span of the simplified synchronization can be adjusted to a certain number (e.g., the required number) of PRBs in the frequency domain, for example, by increasing or decreasing the number of PRBs used for PBCH transmission. This can be handled using updates to PBCH processing (e.g., some updates are required), for example, updates that can be handled (e.g., easily handled) by updating the "rate matching" block of PBCH processing.

[0271] Figure 7 The illustration shows the SSB structure of Example 2, where the PSS / SSS is stacked with the PBCH.

[0272] It may be possible to reuse (e.g., legacy) PSS / SSS sequences in simplified synchronization, for example, based on maintaining 11 PRBs for PSS / SSS.

[0273] In the example, the number of PRBs used for PSS / SSS can be less than 11. In this case, the sequence (e.g., legacy) can be truncated to fit the selected number of PRBs. The PSS / SSS sequence (e.g., a new PSS / SSS sequence) can be designed, for example, to select the number of PRBs for PSS / SSS (e.g., a newly selected one).

[0274] In the example, the number of PRBs used for the PSS / SSS can be greater than 11. In this case, (e.g., legacy) sequences can be sent in a predefined repeating order (e.g., an order known to the WTRU). Longer (e.g., new) PSS / SSS sequences can be designed, for example, to be sent in a simplified synchronization structure.

[0275] A streamlined synchronous design (e.g., spanning only 2 OFDM symbols) can be used for one or more of the following.

[0276] gNB can complete the synchronization signal in 2 OFDM symbols instead of 4 OFDM symbols, and can have a longer sleep time (e.g., from the perspective of NES).

[0277] Time-compression simplified synchronization can provide compact SSB burst structures (e.g., resulting in more efficient synchronization transmission), for example, in FR2 or systems employing a larger number of beams (e.g., future systems). The mapping of SSBs within the time slots of the SSB burst set can be modified, for example, using a 2-symbol simplified synchronization design. In contrast to other (e.g., legacy) SSB burst designs (e.g., designs that restrict the transmission of up to two SSBs to one time slot), simplified synchronization can be used to accommodate four simplified synchronizations per time slot, for example, while still allowing the initial symbol in the time slot for PDCCH as well as subsequent symbols for potential PUCCH transmissions.

[0278] Figure 8 An example of a time-frequency compact structure with only one instance of SS and only one instance of PBCH is illustrated.

[0279] In an example (e.g., for a design used for simplified synchronization), a time-compressed structure can be obtained by separating the transmission of the PSS / SSS sequence from the PBCH transmission (e.g., simplified SS can avoid including (e.g., not including) PBCH transmissions / blocks). In this segmented design of simplified synchronization, the network can send the PSS / SSS in 2-symbol transmissions. In subsequent transmission intervals, 2-symbol PBCH transmissions can be sent on the same resource. The PSS / SSS can use a frequency span of 11 PRBs, for example, to reuse the sequence in a design (e.g., a legacy design). (Multiple) PBCH transmissions can use the same frequency span of 11 PRBs (e.g., resulting in 22 PRBs for PBCH transmissions). This can use (e.g., require) a higher PBCH coding rate compared to other designs (e.g., legacy designs), for example, if the PBCH carries the same number of information bits. This can then lead to low PBCH coverage.

[0280] The frequency span of the simplified synchronization signal can be increased, for example, to expand the coverage of the PBCH. In the example, the PBCH transmission can span a larger number of PRBs. In the example, the PBCH transmission can span 24 PRBs, which can provide 48 PRBs for PBCH transmission (e.g., the same as in legacy designs). This can allow for complete reuse of PBCH for sending and receiving. The PSS / SSS span can remain at 11 PRBs. The coverage of synchronization can be improved, for example, by allowing PSS / SSS transmissions over a larger number of PRBs. Like the PBCH, the PSS / SSS can use a certain number (e.g., the same number) of PRBs, for example, 24 PRBs. The PSS / SSS sequence (e.g., each sequence) can be repeated (e.g., twice) in the frequency domain (e.g., 127*2 = 254 resource elements), while leaving (24*12 – 254 =) 34 resource elements (e.g., these resource elements can be left empty). Multiple (e.g., half) of these resource elements can remain at the top and bottom of the PSS / SSS repeat (e.g., each top and bottom). In the example, (e.g., new) longer PSS / SSS sequences can be designed, which can provide a more efficient design for these sequences.

[0281] In the example, the PSS / SSS sequence can indicate the time or frequency span of PBCH transmission within a configurable number of time-frequency spans (e.g., carrying information related to it). The WTRU (e.g., based on the detection of the PSS / SSS sequence) can determine the appropriate time-frequency coverage of the PBCH and can decode the PBCH (e.g., based on the indication received in the PSS / SSS sequence).

[0282] In the example, the relative periodicity of PSS / SSS and PBCH can be different. The relative periodicity of PSS / SSS and PBCH can be mapped to the cell NES state. The WTRU can derive the relative periodicity of PSS / SSS and PBCH transmissions, for example, based on knowledge of the cell NES state, which can be provided to the WTRU via explicit or implicit signaling.

[0283] In the example, the WTRU can detect the relative periodicity of the PSS / SSS and PBCH. The WTRU can determine the cell NES condition and status, for example, based on the detected relative periodicity of the PSS / SSS and PBCH.

[0284] In the example, the network can provide periodic or time-frequency coverage of the PSS / SSS and PBCH through the transmission of sequences (e.g., special sequences). The WTRU can receive configuration information with (e.g., predefined or pre-configured) time-frequency placement of special sequences, which the network uses to indicate the periodic or time-frequency coverage of the PSS / SSS and PBCH. The WTRU can detect sequences (e.g., special sequences) on known time-frequency resources. Attributes of the (e.g., special) sequence (e.g., one of the attributes) (e.g., such as sequence selection, phase, cyclic shift, power, etc.) can indicate the periodicity and / or time-frequency coverage of the PSS / SSS and PBCH. The WTRU can detect sequences (e.g., special sequences) and can determine the information used for PSS / SSS and PBCH transmission.

[0285] The network can provide indications of cell NES status and simplified synchronization through the same sequence. In the example, the NES status can have a direct mapping to the simplified synchronization periodicity and time-frequency coverage.

[0286] The determination of the simplified synchronization format / mode by the WTRU (e.g., whether it uses a legacy SSB or one of the newly proposed formats / modes for transmission) can be based on one or more of the following: synchronization grid, frequency band (e.g., FR1 / 2 can use a legacy SSB, FR3 / 4 band can use simplified synchronization or one of these types of simplified synchronization), physical cell ID (e.g., the physical cell ID can be determined based on received PSS and / or SSS, which can indicate which format / type of simplified synchronization is used for synchronization and system information transmission / acquisition); subcarrier spacing (e.g., different subcarrier spacings can be associated with different formats / types of simplified synchronization), cell operating mode (e.g., whether it is NES mode or not), etc.

[0287] Each FR SSB structure may have one or more of the following characteristics.

[0288] Different frequency ranges can be assigned different SSB structures (e.g., the default SSB structure). In the example, FR1 can be assigned an SSB structure (e.g., a single SSB structure) with a larger number of OFDM symbols (e.g., because the number of beams is small). FR2 can have a different SSB structure (e.g., the default SSB structure) with a smaller number of OFDM symbols (e.g., to accommodate a larger number of beams and provide NES advantages).

[0289] Whether a cell applies NES technology or not may affect the structure of the SSB, which the cell uses to send synchronization information. For cells that do not apply NES, one structure can be used (e.g., defined), and for cells that apply NES, different SSB structures can be used (e.g., defined). This may have some decoding impact on the WTRU, but this impact can be kept low through the appropriate selection of the two SSB structures. On the other hand, the network can gain the advantages of NES, and the WTRU can connect independently of whether the cell is in an NES state (e.g., it can still connect).

[0290] Dynamic power updates for synchronous / SSB transmissions can be performed and / or enabled.

[0291] The power settings for each SSB can be used, enabled, and / or configured. The WTRU can receive configuration information that has (e.g., configured or defined) one or more "SSB tx assumptions" for each frequency band, carrier, TRP, BWP, NES state, and / or SSB structure. SSB tx assumptions may include at least one of the following: transmission power level, QCL / TCI assumptions, spatial relationship / beam configuration information (e.g., including the beamwidth and / or azimuth of the transmitted SSB), association of RACH with SSB, PSS / SS sequence, path loss reference, multiple transmitted SSBs, whether the SSB is associated with a supplementary carrier (SUL) (e.g., for the purpose of determining path loss reference or measuring channel conditions (e.g., RSRP)), relevant measurement configuration (including gaps, applicable L1 / L3 measurement timing and type), relevant SSBs for measurements for BFD, BFR, RRM and / or RLM purposes, relevant SRI for each SSB or beam, relevant CSI-RS resources for measuring each SSB or beam, CSI-RS tx power or power offset associated with the SSB, relevant power control parameters, SSB structure (as described herein), maximum power reduction (MPR) value of PHR, etc. WTRU can determine the parameters associated with the SSB tx assumption (e.g., any of these parameters), for example, based on (e.g., by) receiving an SSB sent with one of the relevant parameters.

[0292] The WTRU can be configured with SSB bursts according to SSB utilization instructions (e.g., receiving configuration information indicating the SSB burst), such as whether the SSB can be muted or transmitted at reduced power (e.g., referred to herein as an "unstable SSB"). Therefore, the WTRU can identify other SSBs as "stable SSBs".

[0293] SSB silence or power changes can be indicated.

[0294] The WTRU can determine that (e.g., at least one or more) SSBs in an SSB burst are muted or transmitted at reduced power. The WTRU can make this determination or determine the SSB tx assumption associated with the SSB based on one or more of the following.

[0295] The WTRU can determine that (e.g., at least one or more) SSBs in an SSB burst are muted or transmitted at reduced power, for example, based on received dynamic L1 / L2 signaling (e.g., indications made by MAC CE or DCI). The signaling (e.g., MAC CE) can indicate one of the following (e.g., at least one): BWP (on which the SSB is muted or its power has changed), SSB index, cell ID, bwp ID, resource ID, spatial relationship, power change, or indication of a predefined or pre-configured power level.

[0296] The WTRU can determine that (e.g., at least one or more) SSBs in an SSB burst are muted or transmitted at reduced power, for example, based on received broadcast signaling. For example, the WTRU can determine the SSB transmission power and which other SSBs are transmitted at that power by receiving broadcast information, so the SI can indicate such assumptions (e.g., parts of the SIB, MIB, or PBCH).

[0297] The WTRU can determine that (e.g., at least one or more) SSB bursts are muted or transmitted with reduced power, for example, based on the received DL WUS signal. The WTRU can determine the SSB tx hypothesis from attributes associated with the received DL WUS. Attributes of the DL WUS may include at least one of the following: modulation type (e.g., OOK vs. OFDM), time or frequency on which the WUS was received, sequence type (e.g., ZC or M), sequence index, channel coding type, etc. The WTRU can determine the SSB tx hypothesis from explicit information indicated / signaled in the content of the embedded message in the DL-WUS.

[0298] The WTRU can determine whether (e.g., at least one or more) SSBs in an SSB burst are muted or transmitted at reduced power, for example, based on receiving SSBs with specific physical layer properties or structures. SSB structures or physical layer properties can include at least one of the following: time-compressed SSBs (e.g., with PBCH / SIB1 multiplexed in the frequency domain), reduced-power SSBs, narrowband SSBs, SSBs with a reduced number of beams per burst, SSBs without PBCHs, SSBs without SIBs, etc. In the example, the WTRU can determine the SSB transmission power and / or which SSBs are muted from the received PSS and / or SSS sequences.

[0299] The WTRU can determine that (e.g., at least one or more) SSBs in an SSB burst are muted or transmitted at reduced power, for example, based on an indication portion of the received PDSCH payload, such as in msg4 or msgB.

[0300] The WTRU can determine that (e.g., at least one or more) SSBs in an SSB burst are muted or transmitted at reduced power, for example, based on an indication received from RRC signaling (e.g., a DCCH message or CCCH message). The WTRU can receive the applicable SSB tx assumption portion of the RRC signaling and / or changes regarding (e.g., existing) configurations (e.g., incremental reconfiguration).

[0301] The WTRU can determine that (e.g., at least one or more) SSBs in an SSB burst are muted or transmitted at reduced power, for example, based on the receipt of a PDCCH instruction (e.g., for CFRA) or a mobility command. The WTRU can assume an SSB tx assumption associated with the SSB indication portion of the PDCCH instruction.

[0302] The WTRU can determine from the identified active NES state that (e.g., at least one or more) SSBs in an SSB burst are muted or transmitted at reduced power. The WTRU can determine the applicable SSBtx assumptions from the identified or indicated NES state. The WTRU can be configured or predefined with SSBtx power or assumptions or SSB power settings based on the NES state. The WTRU can assume that a subset of SSBs are muted or transmitted at different power levels or with different spatial relationships, for example, based on the active NES state.

[0303] SSB silence or reduced SSB power may affect the WTRU process.

[0304] Path loss can be estimated.

[0305] The WTRU can change its path loss reference (e.g., a portion of the RACH or PHR process), for example, based on determining that the SSB has been muted or that the SSB is being transmitted at reduced power (e.g., based on the activation of the NES state). The WTRU can receive configuration information based on the NES state, which indicates (e.g., is configured) a list of SSBs for use in measurements based on the activation of the relevant NES state (e.g., measuring L1 SS-RSRP by activating the relevant NES state).

[0306] The WTRU can use parameters associated with the SSB tx assumption (e.g., transmit power, spatial relationships) to calculate / estimate path loss, for example, based on determining that the SSB is transmitting at reduced power or based on the SSB tx assumption. The WTRU can exclude previously performed measurements when the SSB is transmitting at full power.

[0307] The random access process may be affected.

[0308] The WTRU can receive configuration information indicating (e.g., configured) a threshold (e.g., rsrp-ThresholdSSB) based on the NES state, the SSB tx assumption, or the SSB transmission power. The WTRU can use the relevant threshold (e.g., rsrp-ThresholdSSB) during the RA process to select the SSB and / or the relevant preamble, for example, based on determining that the SSB is transmitted according to a given SSB tx assumption or that a given NES state is active.

[0309] The WTRU can receive configuration information indicating (e.g., configured) a mapping based on the NES state or based on an SSB tx assumption (e.g., an SSB-to-RO mapping). The WTRU can use the associated, configured SSB-to-RO mapping during the RA process to select SSBs and / or associated preambles, for example, based on determining that an SSB is being transmitted according to a given SSB tx assumption or that a given NES state is active. The WTRU can use alternative SSB-to-RO mappings associated with SSB tx assumptions, for example, based on determining a subset of SSBs or TRPs to be muted. In the example, the WTRU can reallocate the preambles, ROs, and / or PRACH resources mapped to a muted or reduced-power SSB to other transmitted SSBs (e.g., non-mute SSBs, stable SSBs, non-mute TRPs, or SSBs transmitted at full power). In the example, WTRU can redistribute the PRACH resources mapped to the silent SSB evenly to the remaining stable SSBs (e.g., in a sequential order, by time domain priority, or by frequency domain priority).

[0310] The WTRU can receive configuration information indicating (e.g., configured) a list of SSBs (e.g., SSBs in an SSB burst) or TRPs that the WTRU can select during the random access procedure, for example, if the SSB is transmitted according to a given SSB tx assumption (e.g., when the SSB is transmitted according to a given SSB tx assumption) or if the WTRU determines that the cell is in a given NES state (e.g., when the WTRU determines that the cell is in a given NES state). The WTRU can avoid measuring (e.g., ignoring / not measuring) other SSBs that are not transmitted in the full-power portion of the random access procedure. If (e.g., when / once) the WTRU is in connected mode, the WTRU can consider other SSBs (e.g., unstable SSBs). The WTRU can assume one QCL assumption for the SSB during the random access procedure and another QCL assumption after the random access procedure is completed, which can be configured according to the SSB tx assumption. The WTRU may be indicated with an additional list of unstable SSB portions, either msg4 or msgB.

[0311] Based on the NES state or the SSB tx assumption, the WTRU can be configured with individual thresholds for selecting between NUL and SUL, between SULs, between different PRACH partitions with different characteristics, and between 2-step PRACH resources and 4-step PRACH resources. The WTRU can apply relevant thresholds during the RA process, for example, based on determining that a given NES state is active or that the SSB is sent according to a given SSB tx assumption.

[0312] The WTRU can receive configuration information that indicates (e.g., is configured to) a RO mask based on the NES state or based on the SSB tx assumption (e.g., ra-ssb-OccasionMaskIndex). The WTRU can use the relevant RO mask during the RA process to select the RO and / or the relevant SSB based on determining whether the SSB is being sent according to a given SSB tx assumption or determining that a given NES state is active.

[0313] The WTRU can reset the power ramp counter, for example, based on determining that the SSB was transmitted under different SSB tx assumptions (e.g., compared to a previous preamble transmission attempt) or based on activating a given NES state. The WTRU can reset the power ramp counter, for example, if the SSB changes or the SSB power changes or remains constant, but adjusts the counter to account for the power difference (e.g., if the SSB power has not changed, increments it by more than one to achieve the same power level). The WTRU can increment the preamble transmission counter by a value (e.g., >1), for example, so that the increment multiplied by the power ramp step is close to (or equal to) the difference in SSB transmission power or path loss estimate compared to a previous preamble transmission attempt.

[0314] WTRU can restart the RA process or reset the preamble transmission counter, for example, based on determining that the SSB was sent according to a different SSB tx assumption (e.g., compared to a previous preamble transmission attempt) or based on activating a given NES state.

[0315] The WTRU can select the SDT RA or CG resource corresponding to a stable SSB, a non-silent SSB, or a full-power SSB (e.g., as part of the SDT procedure). The WTRU can add or subtract an offset to the measured SS-RSRP threshold to select a given SSB (e.g., thus selecting the associated RO or CG resource), for example, if the SSB is transmitting at reduced power or if the cell is in a given NES state, where such offset can be configured or determined as a power reduction offset for the SSB (e.g., based on the SSB tx assumption).

[0316] The WTRU can apply rollback on a per-SSB basis, for example, based on a received rollback instruction. The rollback instruction can specify a given SSB. The WTRU can avoid selecting such an SSB, for example, while the rollback time is running. The WTRU can receive an instruction in RAR / MsgB that prohibits the selection of a given SSB (e.g., and the associated RO) during or for a period of time during the RA process.

[0317] Mobility and cell (re)selection can be enabled and / or performed.

[0318] The WTRU can initiate (e.g., some) (multiple) measurements (e.g., possibly based on measurement configurations / gapes associated with SSB tx assumptions), such as based on indications of receiving different SSB tx assumptions, SSB power reduction indications, and / or determining different SSB tx assumptions. The WTRU can measure one or more target cells (e.g., configured CHO candidates, CHO candidates configured when the source cell enters NES state).

[0319] The WTRU can initiate (e.g., a new) measurement session, for example, if it is determined that the cell is transmitting SSBs according to a different SSB tx assumption (e.g., when it is determined that the cell is transmitting SSBs according to a different SSB tx assumption) or when the cell is in a given NES state. The WTRU can discard previous measurement samples performed using different SSB tx assumptions, for example, if measurement filtering / averaging is performed (e.g., when measurement filtering / averaging is performed).

[0320] Power control can be used, implemented, and / or enabled.

[0321] The WTRU can receive configuration information indicating (e.g., configured) parameters (e.g., individual power control parameters) to be applied to / associated with a given NES state, or when an SSB is transmitted according to a certain SSBtx assumption. Parameters may include one or more of the following: PCMAX (e.g., maximum allowed transmit power per carrier), P0 (e.g., nominal target receive power), α (e.g., partial path loss compensation parameter), and / or δ (e.g., power adjustment due to closed-loop power control). The WTRU can use alternative α to compensate for path loss, for example, if the WTRU determines that the serving cell is transmitting an SSB at reduced power or is in an NES state. The WTRU can apply alternative power adjustment increments (δ), for example, based on signaling received from the network (e.g., a portion of L1 / L2 signaling) or a TPC command associated with the cell transmitting an SSB according to a non-default SSBtx assumption or being in an NES state.

[0322] WTRU can apply (multiple) alternative power control parameters, for example, if a neighboring cell is in NES state, a neighboring cell is transmitting SSB at reduced power, or when signaling (e.g., L1 / L2 signaling) is received from the serving cell to apply such alternative power control parameters.

[0323] To estimate the uplink path loss for a given beam, the WTRU can use a downlink path loss reference (e.g., which may typically involve the SSB or CSI-RS). If the SSB or CSI-RS is muted or transmitted at low power, the WTRU can add a power difference (e.g., compared to the full SSB power) to the path loss estimate. The WTRU can employ relevant QCL / TCI assumptions to estimate the path loss, for example, if the SSB or CSI-RS is transmitted according to different SSB tx assumptions. The WTRU can use parameters (e.g., any parameters) associated with the determined SSB tx assumptions to estimate the path loss. The WTRU can compute multiple path loss estimates for different beams / SSBs. The WTRU can estimate the path loss for a subset of beams (e.g., only for a subset of beams), for example, if the serving cell is in NES state (e.g., when the serving cell is in NES state) or when some SSBs are transmitted according to non-default SSB assumptions (e.g., estimating path loss only for stable SSBs). The WTRU can be configured with an SRI value corresponding to each SSB or SSB tx assumption, which can be used for uplink transmissions corresponding to the selected SSB. For scheduled PUSCH transmissions, the DCI can further indicate the applicable SSB tx assumption, which can be used by the WTRU to estimate path loss. The WTRU can assume a configured or predefined SRI value for scheduled PUSCH, which can be associated with NES status or SSB tx assumptions.

[0324] CSI reports can be executed.

[0325] CSI-RS tx power can be indicated relative to SSB power; for example, the WTRU may use (e.g., require) some form of indication regarding the tx power used by the gNB for SSB transmission. The WTRU may receive dynamic indications (e.g., absolute or incremental changes) regarding CSI-RS transmit power assumptions. The WTRU may receive configuration information indicating (e.g., configured with) CSI-RS power assumptions based on SSB tx assumptions, and this can be implicitly determined by receiving SSBs based on non-default SSB tx assumptions. The WTRU may determine if CSI-RS is transmitted according to a different QCL or spatial relationship, for example, if the received SSB is transmitted according to a different SSB tx assumption.

[0326] The WTRU can report CSI for the difference between the used SSB tx assumption and the full-power SSB tx assumption, for example, if the SSB is transmitted according to a non-default SSB tx assumption. The WTRU can report multiple (e.g., two) CSI reports, such as one report for the active SSB tx assumption and another report for the assumed SSB tx assumption (e.g., full-power transmission or reduced-power transmission). The WTRU can decode the received PDSCH using adjusted CSI measurements corresponding to the active SSB tx assumption.

[0327] Power headroom reports (PHRs) can be used and / or performed.

[0328] The WTRU can trigger a PHR, for example, if it is determined that the SSB was transmitted according to a different SSB tx assumption or if the serving cell has activated a given NES state. For example, if the SSB is transmitted at low power, the WTRU can trigger a PHR. The WTRU can adjust the path loss estimate for the PHR. If the SSB or CSI-RS is muted or transmitted at low power, the WTRU can add a power difference (e.g., compared to the full SSB power) to the path loss estimate. The WTRU can postpone the triggering or transmission of a PHR (e.g., PHR MACCE), for example, if the network is in an NES state (e.g., until the active period of the cell DRX). The WTRU can be configured with alternative PHR prohibition times (e.g., via a timer) to apply when the network is in a given NES state.

[0329] In the example, the WTRU can include multiple (e.g., two) PHR values ​​in a single report. For instance, one PHR may correspond to the active SSB tx assumption, and the other PHR may correspond to a different SSB tx assumption (e.g., full-power SSB or reduced-power SSB). The WTRU can indicate the SSB(s) used to calculate the path loss estimate, as well as the PHR portion of the signaling (e.g., via MAC CE).

[0330] The WTRU can determine different PCMAX values ​​for PHR calculation, for example, if the serving cell is in NES state or the corresponding SSB is transmitted according to a non-default SSB tx assumption (e.g., when the above occurs), where the PCMAX value can be a value configured for the determined SSB tx assumption. The WTRU can subtract an NES-specific MPR value from the PCMAX, where the NES-specific MPR can be determined based on the power difference between the current SSB tx assumption and a full-power SSB. If the SSB is transmitted at low power (e.g., a non-default SSB tx assumption) or the serving cell is in NES state, the WTRU can consider this MPR value in the PHR calculation.

[0331] Beam failure detection and recovery can be performed.

[0332] The WTRU can receive configuration information indicating (e.g., configured) a list of alternative BFD or RLM candidate beams for measurement, such as if the current cell is in a given NES state (e.g., while the current cell is in a given NES state) or when the SSB is transmitted according to a non-default SSB tx assumption. In the example, the set may correspond to stable SSBs (e.g., only). The WTRU can add offsets to the measured BFD CSI-RS or SSB samples of the BFD or RLM, where the offsets may correspond to the power difference between the measured power-reduced CSI or SSB resources and the full-power setting. The WTRU can be configured with alternative thresholds for declaring a BFI instance when the serving cell is in an NES state or when (multiple) SSBs are transmitted according to a non-default SSB tx assumption.

[0333] The WTRU can receive configuration information indicating (e.g., configured to) an alternative list of BFR candidate beams, for example, to measure when the current cell is in a given NES state or when the SSB is transmitted according to a non-default SSB tx assumption. The WTRU can measure, select, and / or indicate stabilizing SSBs (e.g., stabilizing only SSBs) during the recovery process, for example, based on the detection of beam failure. The WTRU can receive configuration information indicating (e.g., configured to) an alternative threshold for selecting the appropriate recoverable SSB or CSI-RS, for example, when the serving cell is in an NES state or when (multiple) SSBs are transmitted according to a non-default SSB tx assumption.

[0334] NES-adaptive periodicity for simplified synchronization and SSB can be used and / or enabled.

[0335] The WTRU can receive configuration information having (e.g., predefined or configured) a first period (e.g., an NES period) for potential full SSB transmission opportunities and a second period for stable full SSB transmission opportunities. The first SSB (e.g., unstable) period may correspond to non-deterministic SSB transmissions, such as opportunities where backward-incompatible SSB structures are transmitted (e.g., as described herein with respect to simplified synchronization structures for NES and dynamic power updates for synchronization / SSB transmissions) and / or used when the cell is in the NES state. The second SSB (e.g., stable) period may be deterministic and / or used, for example, if the cell is not in the NES state (e.g., when the cell is not in the NES state). For example, the duration of the stable period may be longer than the duration of the unstable period. The presence of SSB transmissions in the unstable period may be limited to a subset of the NES state (e.g., only when the NES state is active). SS may refer to a simplified synchronization opportunity transmitted in the unstable period (e.g., such a period as...). Figure 8 and Figure 9 As shown in the image). Figure 8 and Figure 9 A simplified synchronization including PSS / SSS (e.g., PSS / SSS only) is shown as an example. In the example, it may include (e.g., PSS only), (e.g., SSS only) (e.g., PSS and SSS only), or different synchronization sequences. Figure 8 and Figure 9 The diagram illustrates synchronization signals from a given beam with different periodicities. For cells / TRPs / networks employing multiple beams, the synchronization signal can be scanned / transmitted in each beam direction according to the synchronization burst pattern.

[0336] Figure 9 An example of a 1SSB-3SS based transmission is illustrated.

[0337] Figure 10 An example of a 1SSB-2SS based transmission is illustrated.

[0338] The WTRU can use stable SSB cycles for inter-cell measurements, cell (re)selection measurements, some initial access procedures, and / or in idle mode. The WTRU can monitor and measure SSBs during unstable cycles, for example, based on received complete system information. Configuration information related to unstable cycles can be provided via broadcast signaling (e.g., part of the system information, SIB1, or other SIs). The periodicity of stable cycles can be predefined and can depend on the carrier, BWP, subcarrier spacing, and / or the frequency band on which SSBs are transmitted.

[0339] The periodicity and occurrence of unstable cycles (e.g., along with other relevant configurations) can be determined by the WTRU by reading system information, RRC release messages, or attributes of SSBs received during stable cycles. Attributes of the received SSBs may include the sequence for the PSS or SSS, the SSB structure type (e.g., as described herein), or the SSB tx assumption (e.g., as described herein). System information or RRC release message configuration information can provide one or more of the following configuration information for the expected SSB during unstable cycles: periodicity, start offset, SSB structure, SSB tx assumption, whether the PBCH is multiplexed using the SSB, the associated SIB1 periodicity, and whether it is multiplexed, etc.

[0340] During an unstable period SSB timing, the WTRU may assume that the SSB is transmitted using a low-power transmitter and / or received at the WTRU using a low-power receiver / PA (e.g., in addition to the main radio). During an unstable period SSB timing, the WTRU may receive a subset of {PSS, SSS, PBCH, DL WUS}. For example, the WTRU may assume that a PSS is received (e.g., only), a PSS and SSS are received (e.g., only PSS and SSS), a PSS and SSS and PBCH are received (e.g., only), or a PSS and SSS, as well as PBCH and DL WUS are received. The received SS or SSB can provide an indication of the periodicity of the SSB / the next occurrence of SS and SSB or the periodicity of the SS. During an unstable period SSB timing, the PSS / SSS may be transmitted with DL-WUS instead of PBCH, or DL-WUS may be transmitted at some fixed TF resource / timing. The PSS ( / SSS) sequence may carry an indication of the timing of an upcoming full SSB block or on-demand SSB.

[0341] The WTRU can receive configuration information indicating (e.g., predefined or configured) the timing and frequency at which the WTRU monitors DL wake-up signals (e.g., low-power WUS or SSB definition signals). The configuration can be provided in sections of system information / broadcast signaling or RRC release messages. DL WUS timing can be determined to coincide with (before) and / or after SSB transmission timings during stable and / or unstable periods.

[0342] The WTRU can monitor and receive DL signals (DL-WUS) from the network. The WTRU can determine that one or more SSBs have been transmitted, and that an upcoming SSB transmission opportunity in the first SSB cycle (e.g., a stable cycle / NES cycle) can be received, for example, based on the received DL-WUS. The WTRU can determine the SSB structure type based on at least one attribute of the received or decoded DL-WUS for monitoring and / or reception within the first SSB cycle. DL WUS attributes may include one or more of the following: modulation type (e.g., OOK versus OFDM), time or frequency of DL-WUS reception, sequence type (e.g., ZC or M), sequence index, channel coding type, or the content of an embedded message. The SSB structure type can be (e.g., any) structure (e.g., as described herein) and can be one or more of the following: time-compressed SSB (e.g., with PBCH / SIB1 multiplexed in the frequency domain), reduced-power SSB, narrowband SSB, SSB burst with reduced number of SSB beams per burst, SSB without PBCH, or SSB transmission without SIB. The WTRU can receive the SSB at the transmission time of the first SSB cycle, for example, based on the determined SSB structure. Based on the received SSB, the WTRU can receive (e.g., at least one) PBCH and / or one or more SIBs. The WTRU can transmit (e.g., using determined RACH parameters) a preamble (e.g., based on the received SSB and information received in the PBCH and / or at least one SIB), for example, if it is part of the initial access procedure.

[0343] The WTRU can assume the same SSB structure during the first cycle until another DL-WUS is received. The WTRU can combine SSB receptions from stable and unstable cycles to accumulate the energy of the received signal.

[0344] In the example, the WTRU can determine the active NES state by receiving a DL WUS, for example, based on attributes (e.g., at least one attribute) of the received or decoded DL-WUS. The NES state can be an encoded portion of the DL WUS message content. The DL WUS can provide an indication of the NES state and the relative periodicity for SSBs and SSs (e.g., simplified SS). The WTRU can determine the cell's NES state from periodicity or relative periodicity within stable and unstable SSB periods, for example, based on predefined periodicity or relative periodicity defined in the specification. The WTRU can determine the SSB structure or SSB tx assumption (e.g., a TDM between an SSB and N repeating PSSs / SSSs) by receiving the PBCH or its content or from attributes of the received PSS / SSS sequences. To dynamically switch NES states, the gNB can indicate updates to the NES state via the DL WUS. The DL WUS can further indicate updates to the SSB periodicity or switching to different SSB tx assumptions. The WTRU can (e.g., alternatively) determine the NES cell state from the determined SSB tx assumptions (e.g., SSB type or periodicity).

[0345] SSB periodic changes or on-demand SSBs can be requested (e.g., via UL WUS).

[0346] The WTRU can receive configuration information indicating (e.g., predefined or configured) to send a request (e.g., an uplink wake-up request "UL WUS" or a cell wake-up request "cell WUS") in one or more NES states. The WTRU can send a cell WUS to request one or more of the following: change the active SSB tx assumption (e.g., as described herein); change the active SSB transmission periodicity (e.g., either within a stable period, or within an unstable period, or both); activate SSB transmission (e.g., within an unstable period); change the transmitted SSB structure / type (e.g., as described herein); transmit a complete SSB (e.g., an SSB with a PBCH and an SSB transmitted at full power or an on-demand SSB); activate a given NES state or deactivate an active NES state; request a simplified SSB and / or PBCH transmission; request to receive system information (e.g., SIB1 transmission, other SIs and / or MSIs); indicate the active NES state; activate a given data or control channel (e.g., PDSCH, SPS, CG, PUCCH); configure DL. WUS resources; configuring system access resources for a given cell (e.g., a cell in NES state), such as including PRACH resource configuration and / or a subset of system information for a given cell; any of the above requested for a given carrier, BWP, frequency band, or TRP; etc.

[0347] The WTRU may include a request information portion (e.g., any) of the cell WUS request (e.g., as described herein) (e.g., in the portion accompanying auxiliary data, the RA payload triggered for the cell WUS (e.g., in msgA or msg3)). For example, the WTRU may include indications about the requested SSB tx assumptions, SSB tx power, SSB structure, and / or SSB periodicity in the transmitted portion of a message or procedure accompanied by the cell WUS (e.g., on the PUSCH resource portion of an RA triggered by the cell WUS).

[0348] The WTRU can monitor the PDCCH after transmitting the cell WUS, for example, to receive requested signals, channels, and / or information. The WTRU can monitor requested time-domain periods (e.g., unstable periods), carriers, SSBs on the BWP or TRP, PBCH, and / or SI reception. The WTRU can monitor the DL WUS after transmitting the UL WUS signal. The WTRU can assume a predefined change in the SSB structure after transmitting the cell WUS or after receiving a response to the cell WUS.

[0349] WTRU can trigger the transmission of cell WUS signals, for example, based on meeting at least one of the following conditions: detecting a cell discovery signal; performing channel measurements based on a value above or below a configured threshold; the arrival of new data, possibly from a subset of DRB, SRB, LCH, LCG, or associated with a specific priority level or index; the amount of buffered data exceeding a threshold; triggering BSR and / or SR; detecting beam failure or RLM events (e.g., RLF); triggering L3 or mobility events; detecting SCG or MCG failure; based on the elapsed time (e.g., timer expiration), possibly combined with the absence of SSB or DRS during this period; and so on.

[0350] The WTRU can transmit a cell WUS on the same cell, TRP, or BWP (where the requested signal / channel / information is configured for that cell, TRP, or BWP), or on different serving cells, TRPs, or BWPs. For example, the WTRU can detect that an Scell ​​has not transmitted any SSBs for a period of time, and can then request on-demand SSB transmission or activate an SSB on that cell by transmitting a cell WUS on a different serving cell (e.g., SpCell). The WTRU can transmit only a cell WUS to transmit an SSB on a secondary cell. The WTRU can transmit a cell WUS on a secondary cell (e.g., only on a secondary cell) or on an unstable cell (e.g., only on an unstable cell). The WTRU can assume that an additional SSB transmission period (e.g., an SSB instability period) is activated after transmitting a cell WUS or receiving a DL response to it.

[0351] Periodicity and repetition for thin synchronization and SSB can be used, executed, and / or provided.

[0352] In the example (e.g., for a design used for system information acquisition), the WTRU can receive configuration information indicating (e.g., predefined or pre-configured) the reception of a legacy SSB structure or a proposed SSB structure (e.g., as described herein), and different relative periodicities for full SSB or simplified synchronization. Different synchronization structures, the number of repetitions of PSS / SSS symbols in a full SSB, or independent relative periodicities can have a mapping to the cell's NES state. The WTRU can determine the expected SSB structure, repetitions, and relative periodicities based on the cell's NES state.

[0353] Figure 11 An example synchronization design is shown, where a full synchronization includes (e.g., contains) two symbols for the PSS / SSS (e.g., two symbols for each PSS / SSS) and six symbols for the PBCH. In this full synchronization, the frequency occupancy for PSS / SSS and PBCH transmissions can be the same. For each beam, (e.g., once) a full synchronization can be followed by multiple (e.g., two) reduced synchronizations over several subsequent transmission periods (e.g., two transmission periods). (e.g., each) a reduced synchronization can include (e.g., contains) two symbols for the PSS and two symbols for the SSS.

[0354] Figure 11 An example synchronization design with TDM structures for SSB and PSS / SSS is illustrated.

[0355] The network can send full and / or simplified synchronizations (e.g., PSS / SSS) via low-power Tx and PA. This allows the gNB's normal (high-power) Tx and PA to have longer sleep times, thus adding significant energy-saving advantages to network operation.

[0356] Figure 11 An example of using two OFDM symbols for PSS and SSS transmission within each synchronization period is shown. To compensate for the synchronization coverage loss associated with using low-power Tx and PA, the number of PSS / SSS symbols within a period can be increased.

[0357] In the example, the periodicity of PSS / SSS transmissions can be improved. In the example, full synchronization (e.g., PSS / SSS / PBCH) can use a periodicity of T1. PSS / SSS transmissions without PBCH can use a shorter periodicity T2, thus providing more PSS / SSS opportunities. WTRU can average these opportunities to improve performance and compensate for coverage loss.

[0358] WTRU can be predefined or pre-configured with two sets of configuration information. One configuration information can be for full synchronization (e.g., PSS / SSS / PBCH) transmissions, and the other configuration information can be for PSS / SSS transmissions without a PBCH. In the example, a single configuration with additional parameters may exist. The additional parameters can provide the relative time and relative periodicity of the streamlined PSS / SSS transmission, for example, compared to a full PSS / SSS / PBCH transmission.

[0359] Figure 12 The illustration shows two examples of simplified synchronization, where the number of symbols in each transmission interval is different, and the transmission periodicity is also different.

[0360] like Figure 12 As shown at the top, a design with two PSS / SSS symbols can be used, which repeat every 2 milliseconds.

[0361] like Figure 12 As shown at the bottom, a design with one PSS / SSS symbol and a period of 1 millisecond can be used.

[0362] Figure 12 The illustration shows example designs for different SS lengths and periodicities.

[0363] A simplified SSB design may include multiple (e.g., an appropriate number) PSS and SSS symbols (e.g., PSS / SSS symbols only). Other designs for a simplified SSB may include: PSS (e.g., only) transmission, SSS (e.g., only) transmission, PSS and SSS transmission (e.g., PSS and SSS transmission only), NES-based (e.g., novel) sequences for PSS, SSS, or both, etc.

[0364] For each of these designs, the symbol count / repetition count can be optimized to achieve a trade-off between network energy efficiency, effective coverage, and WTRU synchronization performance. These designs can be further combined with different relative periodicities of full synchronization and simplified synchronization.

[0365] The NES status or SSB position can be indicated via sequence transmission.

[0366] The WTRU can determine the time-frequency location of the SSB by detecting a sequence sent by the network (e.g., a pre-synchronization signal, such as WUS). This sequence can be referred to as the pre-synchronization sequence (e.g., as described herein).

[0367] In the example, the WTRU can anticipate a pre-synchronization sequence to be sent by the network at a known periodicity. The known periodicity can be a fixed value or one of a known set of values.

[0368] WTRU can determine the decoding of pre-synchronization sequences on a set of N consecutive Physical Resource Blocks (PRBs). N can be a known value representing the number of PRBs. N can also be a set of known values ​​from the PRBs. The network can send sequences within each set of N PRBs. The length of the sequence can be a known value or a set of known values.

[0369] In the example, the WTRU can determine the timing and placement of the pre-synchronization sequence, for example, based on information received in the simplified synchronization signal (e.g., information indicated by the simplified synchronization signal) (e.g., as described herein).

[0370] In the example, WTRU can anticipate the pre-synchronization sequence to be sent from a known sequence type (e.g., Zadoff-Chu or M sequence).

[0371] In the example, the pre-synchronization sequence can be a PSS sequence sent at a configured time frequency position and at a given periodicity.

[0372] The WTRU can determine the type / format / mode of the pre-synchronization sequence based on one or more of the following: synchronization grid location; frequency band (e.g., FR1 / 2 can use one type of pre-synchronization sequence, while (e.g., the new) FR3 / 4 band can use a different type of pre-synchronization sequence); physical cell ID (e.g., this physical cell ID can be determined based on received PSS and / or SSS) which can indicate which format / type of pre-synchronization sequence the network will use; subcarrier spacing (e.g., different subcarrier spacings can be associated with different formats / types / periodicities of the pre-synchronization sequence); cell operating mode (e.g., whether it is NES mode or not); and so on.

[0373] The WTRU can detect DL pre-synchronization sequences sent by the network. The WTRU can determine (e.g., based on at least one attribute of the received or detected pre-synchronization sequence) one or more of the following: SSB time position, SSB frequency position (e.g., on a wideband carrier with appropriate granularity), SSB structure, presence / absence of simplified synchronization, structure of simplified synchronization (e.g., as described herein), presence / absence of transmission of compact minimum system information, periodicity of SSB or simplified synchronization, relative periodicity of SSB and simplified synchronization, NES indication of the cell, etc.

[0374] Pre-synchronization sequences can carry information (e.g., indication) in a physical attribute, such as: time position, frequency position, sequence type, sequence selection, sequence phase, initialization parameters, etc.

[0375] Information transmission / acquisition can be performed in a compact, minimal system.

[0376] The WTRU can receive configuration information that indicates (e.g., predefined or pre-configured to receive) a compact format of SSBs (e.g., PSS, SSS, and PBCH) and SIB-1 or RMSI. The compact form of PSS, SSS, and the entire minimal system information (PBCH and SIB-1) can be referred to as SSM.

[0377] SSM can include PSS + SSS + Compact Minimum System Information (PBCH, SIB-1).

[0378] In an SSM, the PBCH may not (e.g., need to) indicate time, frequency resources / parameters to locate SIB-1. The PBCH content in an SSM may differ from the (e.g., legacy) PBCH that is transmitted as part of the (e.g., legacy) SSB.

[0379] A subset of parameters from SIB-1 can be sent as part of the SSM, for example, based on predefined or pre-configured information provided to the WTRU. This set of parameters can be referred to as Compact SIB-1 or Compact RMSI.

[0380] The WTRU can receive configuration information indicating (e.g., being configured to) detect and decode different types of SSMs, such as one or a combination of the following: different subsets of PBCH, SIB-1 (RMSI); different subsets of PBCH, SIB-1, and the following SIB information (e.g., elements taken from SIB-2, SIB-3, SIB-4, SIB-5, etc.); different time / frequency resources for MSI (e.g., offset from PSS / SSS); different channel coding in different types of SSMs; and so on.

[0381] In the example, the WTRU can decode the SSB and / or compact SIB-1 (e.g., RMSI), where the compact SIB-1 can be transmitted on subsequent OFDM symbols on the same frequency resources as the PBCH (e.g., as shown in the example). Figure 12 As shown). Figure 12 As shown, according to the previous configuration, the WTRU can decode the compact SIB-1 of four OFDM symbols following the last OFDM symbol across the PBCH. The WTRU can (e.g., be configured to) decode the compact SIB-1 on two, three, four or more OFDM symbols.

[0382] In the example, the PBCH transport and the compact SIB-1 can be encoded (e.g., independently). The PBCH can use polar coding. The compact SIB-1 can be LDPC coded, for example, according to parameters known to the WTRU or pre-configured. In the example, the compact SIB-1 can be polar coded.

[0383] The design of reference symbols for compact SIB-1 transmission can use the same sequence generation and comb structure as PBCH. Therefore, DMRS for SIB-1 can follow the same comb-type 4 design as that used for PBCH.

[0384] The frequency offset of the DMRS for compact SIB-1 can be the same as that of the PBCH, depending on the cell identifier of the cell transmitting the PBCH. In the example, a compact SIB-1 transmission can use a comb-type 2 DMRS structure in the first OFDM symbol of the SIB-1 transmission. This first symbol in a compact SIB-1 transmission can be accompanied by additional DMRS symbols. The DMRS indication for a compact SIB-1 transmission can be indicated in the PBCH. Therefore, the WTRU can decode (multiple) PBCH transmissions, and the PBCH transmission can provide one or more of the following related to the DMRS structure of compact SIB-1: the comb structure for the DMRS, the number / location of additional DMRS symbols, the resource element offset for the DMRS resources, etc.

[0385] Figure 13 The illustration shows an example compact MSI structure with separate encodings for PBCH and compact SIB-1.

[0386] In the example, the WTRU may already know multiple subsets / formats of legacy SIB-1 information elements through pre-configuration (which the network can send as compact SIB-1). The WTRU can decode the PBCH and determine the format (e.g., a specific subset of SIB-1) that the network can transmit via the PBCH. The WTRU can decode and / or interpret the information elements transmitted in the compact SIB-1 based on the indications received in the PBCH transmission.

[0387] In the example (e.g., for SSM transmission), PBCH transmission and compact SIB-1 can use the same frequency span as PSS / SSS (e.g., as...). Figure 14 (As shown).

[0388] Figure 14 The illustration shows an example compact MSI structure with separate encodings for PBCH and RMSI, plus a smaller frequency coverage.

[0389] Multiple PBCH transmissions can be sent using the same information content as in the current design with minor modifications. PBCH transmissions can provide indications of SIB-1 transmission attributes (e.g., DMRS, the number of symbols used for SIB-1 transmissions, etc.).

[0390] Compact SIB-1 can follow PBCH transmissions based on the instructions provided via PBCH transmissions.

[0391] In the example, PBCH transmission and compact SIB-1 can be encoded (e.g., jointly encoded) and transmitted together with the PSS / SSS sequence (e.g., jointly transmitted) (e.g., as...). Figure 15 (As shown). PBCH transmission and compact SIB-1 (e.g., providing compact MSI) can be mapped over a larger number of PRBs (e.g., a larger number of PRBs compared to PSS / SSS). In the example, compact MSI can span the 20 PRBs that PBCH spans in legacy SSB. Modulation, coding, and DMRS for MSI can follow predefined / pre-configured values ​​or can use one of a predefined / pre-configured set of values.

[0392] In the example, the WTRU can be provided (e.g., received) with an indication of the transmission parameters of the compact MSI via one of the physical properties of the PSS / SSS. In the example, the indication can be provided via a DL-WUS signal transmitted by the network on known time-frequency resources.

[0393] In the example, the WTRU can determine the format and periodicity of the compact MSI (e.g., together with the PSS / SSS sequence) by the NES indication sent by the network.

[0394] In the example, the WTRU can determine the format and periodicity of the compact MSI for the cell (e.g., along with the PSS / SSS sequence) by an indication received from another cell. The other cell providing the indication to the WTRU can be the UE's serving cell.

[0395] Figure 15 The illustration shows an example compact MSI structure with joint encoding of PBCH and compact SIB-1.

[0396] Figure 16 An example design for compact MSI transmission and PSS / SSS sequence is shown, wherein the jointly encoded compact MSI can be transmitted over the same frequency span as the PSS / SSS.

[0397] Figure 16 The illustration shows an example compact MSI structure with joint encoding of PBCH and compact SIB-1.

[0398] In the example, the compact MSI may include (e.g., contain) the PBCH and SI digest. The SI digest may include (e.g., contain) a single value or a set of values. In the example, the SI digest may include (e.g., contain) two values, for example, one of which is an MSI digest associated with the MIB and SIB-1. The second value in the SI digest may correspond to other system information. The WTRU can receive system information and SI digests of neighboring cell Cx through its serving cell. The WTRU can acquire the compact MSI (e.g., later), for example, if the WTRU reselects cell Cx. The WTRU can compare the SI digest to verify whether it matches the stored SI digest of cell Cx (e.g., to determine if it needs a new SIB-1 and / or other SIBs). The WTRU can receive / decode the SIB-1 from cell Cx to obtain the RACH parameters of cell Cx, for example, if the SI digest does not match the stored SI digest of cell Cx. The WTRU may already have the RACH parameters of cell Cx (e.g., based on a previously received SI digest), for example, if the SI digest matches. Based on the RACH parameters, the WTRU can transmit RACH on cell Cx. The WTRU can indicate stored "Other SI Digests," so the network knows what system information the WTRU has (e.g., as part of the RACH transmission for the UE in Msg1 / 3 / MsgA). The network can provide incremental system information related to the "Other SI Digests" indicated by the WTRU. C-MSI reception can be based on a first SSB period, which can be nondeterministic or NES. SIB-1 reception can be based on a second SSB period, which can be deterministic, complete, or non-NES SSB period.

[0399] In the example, the (e.g., legacy) SSB time-frequency span (e.g., 20 PRBs – 4 OFDM symbols) can be used to transmit SSMs (e.g., PSS, SSS, and Compact MSI). In the example, the PBCH parameter associated with CORESET-0 can be replaced by the SI digest. This design helps to keep the SSB burst mode consistent with other (e.g., legacy) burst designs.

[0400] In the example, the network may indicate two sets of periods (e.g., periodicity), for example, one set may refer to the period / periodicity transmitted with the full / legacy SSB and SIB-1, and the second set may refer to the period / periodicity of the transmission of the compact MSI transport structure (e.g., according to other designs described herein).

[0401] In the example, the second set of periods / periodicities can have a full SSB / SIB-1 transmission, or a structure from a compact MSI transmission structure based on the cell NES state. The WTRU can receive the cell NES state and determine the compact MSI transmission structure / periodicity based on the cell NES state. The indication can be the NES state itself, which can be mapped to one of the structures, or the NES indication can have an additional indication by which the WTRU determines the compact MSI structure / periodicity.

[0402] The WTRU can (e.g., determine) receive system information sent from the network in one of the following modes / formats: (e.g., legacy) SSB, SIB-1 and additional SIB; SSM (e.g., as described herein); one or more SSM types (e.g., as described herein); (e.g., legacy) SSB / SIB-1 and one or more SSM types (e.g., as described herein); etc.

[0403] The WTRU's determination of the format / mode of system information (i.e., whether it uses the legacy SSB / SIB-1 or the new SSM format) can be based on one or more of the following: synchronization grid location; frequency band (e.g., FR1 / 2 can use (e.g., legacy) SSB, (e.g., the new) frequency band FR3 / 4 can use SSM or one of the types of SSM); physical cell ID (e.g., this physical cell ID can be determined based on received PSS and / or SSS), which can indicate which format / type of SSB / SSM is used for system information transmission / acquisition; subcarrier spacing (e.g., different subcarrier spacings can be associated with different formats / types of SSB / SSM); cell operating mode (e.g., whether it is NES mode or not); and so on.

[0404] The WTRU's determination of the format / mode of system information from one of the types / formats / modes of the SSM can be based on one or more of the following: synchronization grid location; frequency band (e.g., FR1 / 2 can use (e.g., legacy) SSB, (e.g., new) frequency band FR3 / 4 can use SSM or one of the types of SSM); physical cell ID (e.g., this physical cell ID can be determined based on the received PSS and / or SSS), which can indicate which format / type of SSB / SSM is used for system information transmission / acquisition; subcarrier spacing (e.g., different subcarrier spacings can be associated with different formats / types of SSB / SSM); cell operating mode (e.g., whether it is NES mode or not); and so on.

[0405] The WTRU may (e.g., determine) perform one or more of the following (e.g., if the WTRU determines that an SSM format / type or combination with legacy SSB / SIB-1 exists / when the WTRU determines that an SSM format / type or combination with legacy SSB / SIB-1 exists).

[0406] The WTRU can determine whether to perform RACH based on the type / format of the system information it receives. The WTRU can perform RACH using a 4-step RACH procedure, for example, if it receives a legacy SSB / SIB-1. The WTRU can also perform RACH using a 2-step RACH procedure, for example, if it receives an SSM type.

[0407] The WTRU can (e.g., determine) perform RACH power updates in one configuration / definition manner, for example, if it detects an SSB / SIB-1, and if it detects an SSM type / format, it can determine to perform RACH power updates in a second configuration / definition manner.

[0408] The WTRU can (e.g., determine) select RACH sequences from a set, such as if it detects a legacy SSB / SIB-1. The WTRU can determine to select RACH sequences from a second set, such as if it detects an SSM type / format (e.g., where the first set of RACH sequences is associated with the detection of a legacy SSB / SIB-1, and the second set of RACH sequences is associated with an SSM). More than one SSM type and its associated RACH sequences can be defined.

[0409] The WTRU can determine which search space to monitor (e.g., listen for) a RACH response in based on the SSM format / type. In the example, the WTRU may listen to one type 1 search space associated with a legacy SSB / SIB-1 while simultaneously listening to another type 1 search space associated with one SSM type to receive a RACH response. It is possible that more than one type 1 search space is associated with different types / formats of SSMs.

[0410] The WTRU can (e.g., determine) monitor (e.g., listen for) paging in one of the search spaces based on the SSM format / type, and these search spaces can be associated with the same or different sets of control resources. The set of search spaces can have different periodicities, different PDCCH candidates, etc. In the example, the WTRU can (e.g., determine) monitor / decode (e.g., listen for) a paging search space associated with SSB / SIB-1, for example, if the WTRU detects SSB / SIB-1 (e.g., when the WTRU detects SSB / SIB-1). The WTRU can (e.g., determine) decode another paging search space associated with an SSM (e.g., if it detects an SSM / when it detects an SSM). More than one paging search space can be associated with different SSM types / formats.

[0411] Although the above features and elements have been described in specific combinations, each feature or element can be used alone without the other features and elements of the preferred embodiment, or in various combinations with or without the other features and elements.

[0412] While the implementation methods described herein may take into account 3GPP-specific protocols, it should be understood that the implementation methods described herein are not limited to this scenario and can be applied to other wireless systems. For example, while the solutions described herein take into account LTE, LTE-A, New Radio (NR), or 5G-specific protocols, it should be understood that the solutions described herein are not limited to this scenario and can also be applied to other wireless systems.

[0413] The above processes can be implemented in computer programs, software, and / or firmware incorporated in computer-readable media for execution by a computer and / or processor. Examples of computer-readable media include (but are not limited to) electronic signals (transmitted via wired and / or wireless connections) and / or 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, caches, semiconductor memory devices, magnetic media (such as (but not limited to), internal hard disks and removable disks), magneto-optical media, and / or optical media (such as optical discs, CD-ROMs, and / or digital multifunction discs (DVDs)). The processor associated with the software can be used to implement a radio frequency transceiver for WTRUs, terminals, base stations, RNCs, and / or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU), the WTRU comprising: Processor, the processor being configured to: Receive a first signal, wherein the first signal is a simplified synchronization signal (SS), and wherein the first signal indicates information associated with a second signal; Determine the resources associated with receiving the second signal, wherein the resources are determined using information associated with the second signal; The second signal is received by using resources determined by using information associated with the second signal, wherein the second signal includes an indication associated with a receive synchronization signal block (SSB); Information associated with receiving the SSB is determined based on the indication in the second signal; as well as The SSB is received based on determined information associated with receiving the SSB.

2. The WTRU according to claim 1, wherein the simplified SS is a compressed SS.

3. The WTRU of claim 2, wherein the simplified SS is associated with a first primary synchronization signal (PSS) or one of a first PSS and a first secondary synchronization signal (SSS).

4. The WTRU of claim 3, wherein the simplified SS does not include a Physical Broadcast Channel (PBCH) block.

5. The WTRU of claim 1, wherein the SSB includes a Physical Broadcast Channel (PBCH) block.

6. The WTRU according to claim 1, wherein the second signal is a pre-synchronization wake-up signal.

7. The WTRU of claim 1, wherein the second signal is indicated by the first signal by at least one of the following: time associated with the simplified SS, frequency associated with the simplified SS, phase associated with the simplified SS, or sequence selection associated with the simplified SS.

8. The WTRU of claim 1, wherein the information associated with the second signal includes one or more of the following: timing information associated with the second signal or resource information associated with the second signal.

9. The WTRU of claim 1, wherein the information associated with receiving the SSB indicates one or more of the following: Network Energy Saving (NES) status, SSB periodicity, or the presence of a full SSB at a potential full SSB transmission opportunity.

10. A method, the method comprising: Receive a first signal, wherein the first signal is a simplified synchronization signal (SS), and wherein the first signal indicates information associated with a second signal; Determine the resources associated with receiving the second signal, wherein the resources are determined using information associated with the second signal; The second signal is received by using resources determined by using information associated with the second signal, wherein the second signal includes an indication associated with a receive synchronization signal block (SSB); Information associated with receiving the SSB is determined based on the indication in the second signal; as well as The SSB is received based on determined information associated with receiving the SSB.

11. The method of claim 10, wherein the simplified SS is a compressed SS.

12. The method of claim 11, wherein the simplified SS is associated with a first primary synchronization signal (PSS) or one of a first PSS and a first secondary synchronization signal (SSS).

13. The method of claim 12, wherein the simplified SS does not include a Physical Broadcast Channel (PBCH) block.

14. The method of claim 10, wherein the SSB comprises a Physical Broadcast Channel (PBCH) block.

15. The method of claim 10, wherein the second signal is a pre-synchronization wake-up signal.

16. The method of claim 10, wherein the second signal is indicated by the first signal by at least one of: time associated with the simplified SS, frequency associated with the simplified SS, phase associated with the simplified SS, or sequence selection associated with the simplified SS.

17. The method of claim 10, wherein the information associated with the second signal includes one or more of the following: timing information associated with the second signal or resource information associated with the second signal.

18. The method of claim 10, wherein the information associated with receiving the SSB indicates one or more of the following: Network Energy Saving (NES) status, SSB periodicity, or the presence of a full SSB at a potential full SSB transmission opportunity.

Images