Managing configurations for requesting transmission of system information blocks

Abstract

The disclosure provides systems, devices, apparatuses, and methods, for managing configuration for requesting transmission of SIB, for example on-demand SIB1 transmission. A UE (102) receives (304), from a candidate cell (126B) supporting on-demand SIB, an indication that periodic SIB transmission is deactivated for the candidate cell (126B). The UE (102) transmits (310), to the candidate cell (126B) based on an UL WUS configuration list with a first UL WUS configuration for the candidate cell, a WUS on uplink resources to request an on-demand SIB transmission from the candidate cell (126B). Based on the UL WUS configuration list being inapplicable to the candidate cell, the UE (102) bars (309) access to the candidate cell (126B) and selects (311) a different candidate cell (124) to access.

Description

MANAGING CONFIGURATIONS FOR REQUESTING TRANSMISSION OF SYSTEM INFORMATION BLOCKSCROSS REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 698,484, entitled “MANAGING CONFIGURATIONS FOR REQUESTING TRANSMISSION OF SYSTEM INFORMATION BLOC KS ' and filed on September 24, 2024, which is expressly incorporated by reference herein in its entirety'.FIELD OF THE DISCLOSURE

[0002] This disclosure relates to wireless communications and. more particularly, to managing configuration for requesting transmission of one or more system information blocks (SIBs) such as SIB1.BACKGROUND

[0003] The Third Generation Partnership Project (3GPP) specifies a radio interface referred to as fifth generation (5G) new radio (NR) (5G NR). An architecture for a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), a user equipment (5G UE), etc. The 5GNR architecture seeks to provide increased data rates, decreased latency, and / or increased capacity compared to prior generation cellular communication systems.

[0004] Wireless communication systems, in general, provide various telecommunication services (e.g., telephony, video, data, messaging, etc.) based on multiple-access technologies, such as orthogonal frequency division multiple access (OFDMA) technologies, that support communication with multiple UEs. Improvements in mobile broadband continue the progression of such wireless communication technologies. For example, a network entity of a cell (e.g.. a radio access network (RAN)) periodically broadcasts a master information block (MIB) and a SIB1 for UEs to connect. The MIB provides essential physical layer information of the cell required to receive the SIB1 and other system information blocks (SIBs). The SIB1 defines scheduling of other system information blocks (SIBs) and contains information required for UEs to perform initial access to the cell. In some implementations, the RAN entity broadcasts the MIB and deactivates periodic broadcast of the SIB1 and the1G114380 2870WOother SIBs to reduce power consumption. Thus, in the absence of a received SIB1 for the cell, the UE may have to select a different, less desirable cell.BRIEF SUMMARY

[0005] To enable network energy savings (NES) in 5G networks, a cell of a base station (BS) broadcasts the MIB but stops transmitting SIB1 when there is reduced demand (e.g., during a non-peak period). However, because SIB1 carries certain essential information for accessing the cell, disabling the SIB1 transmission in one cell hinders UEs currently camping on other neighboring cells from reselecting to that cell as well as UEs not camping on any cell (e.g.. the UEs just being powered on) from selecting that cell. As a result, these UEs may end up selecting / reselecting other sub-optimal cells, which can compromise UE performance as well as the overall system performance. Therefore, UEs benefit from a mechanism to request the SIB1 transmission from a cell that has paused its transmission of SIB1. When a cell responds to the request with a SIB1 transmission, this SIB1 transmission is referred to as on-demand SIB1.

[0006] To support on-demand SIB1 transmissions for UEs. a network entity provides the UE with an uplink (UL) wake-up-signal (WUS) configuration to allow the UE to transmit a cell WUS to a candidate cell whose SIB1 transmission is deactivated (e.g., turned off or paused). Based on a received MIB, the UE selects or reselects the candidate cell operating in the NES mode. Then, the UE transmits an UL WUS to the network entity via the candidate cell in accordance with the UL WUS configuration. In response to receiving the UL WUS, the network entity broadcasts the on-demand SIB1. However, it is unclear how the UE manages UL WUS configurations when the UE switches between cells or when there are multiple potential target NES cells.

[0007] An aspect of the present disclosure provides techniques for a UE to use a MIB to detect the absence of SIB1 in a candidate cell, and to request the SIB1 transmission from the candidate cell using the UL resource configuration indicated in the UL WUS configuration. From a turn-on state, a UE selects a candidate cell based on a cell selection procedure. From an idle or inactive state, a UE reselects to a candidate call based on a cell reselection procedure. During any of these non-RRC_connected states (tum-on, RRC idle, or RRC inactive), the UE receives, from a base station connected to a core network, a MIB indicating the base station is not currently broadcasting SIB1 in the candidate cell (i.e.. SIB1 transmission is deactivated or paused) and that the candidate cell supports on-demand SIB12G114380 2870WOtransmission. The UE determines whether it has stored an UL WUS configuration used for requesting transmission of an on-demand SIB1 from the candidate cell. If an UL WUS configuration is available for that candidate cell, the UE transmits a UL WUS to the candidate cell on resources indicated by the corresponding UL WUS configuration to request SIB1 transmission. The UE monitors and receives the SIB1 from the candidate cell. The SIB1 contains information for the UE to access the candidate cell.

[0008] The UE may have received the UL WUS configuration for the candidate cell from a prior cell, the candidate cell, or a cell other than the prior cell or the candidate cell. If the UE does not have a stored UL WUS configuration for the candidate cell, the UE may avoid measuring a synchronization signal block (SSB) (e.g., carrier frequency barring) of the candidate cell to avoid selecting the candidate cell or may perform measurement of the SSB but does not select the candidate cell (e.g.. cell barring). The UE then performs a cell search or selects a different cell that is not in the NES mode (e.g., non-NES cell). When the UE accesses the non-NES cell, the UE may maintain one or more UL WUS configuration(s) for other candidate cell(s) or may release one or more UL WUS configuration(s) for the other candidate cell(s).

[0009] Another aspect of the present disclosure provides techniques for a UE to determine whether the candidate cell is out of coverage while the UE is accessing the cell or camped on another cell. Upon determining that the candidate cell is out of coverage, the UE may maintain the UL WUS configuration for the candidate cell so that the UE may request an on- demand SIB1 from the cell when the UE comes back within coverage. Alternatively, when the UE is out of coverage, the UE may release the UL WUS configuration for the candidate cell.

[0010] Another aspect of the present disclosure provides techniques for a UE to start a validity timer associated with the on-demand S1B1 when the UE receives the SIB1 from the candidate cell in response to the UL WUS. When the validity’ time expires, the UE designates the received SIB1 as invalid. The UE may transmit another UL WUS to the candidate cell based on the UL WUS configuration to request another SIB1. The UE stores time-limited on-demand SIB1 information for each NES cell so the UE may go back and forth between the NES cells.

[0011] Another aspect of the present disclosure provides techniques for a UE to manage multiple UL WUS configurations for requesting on-demand SIB1 transmission from one or3G114380 2870WOmore candidate cells. If the UE receives a first UL WUS configuration and later receives a second UL WUS configuration for requesting on-demand SIB1 transmission from the same candidate cell, the UE may replace or modify the first UL WUS configuration using the second UL WUS configuration. If the two UL WUS configurations are for different candidate cells, the UE may retain both UL WUS configurations. Alternatively, the UE mayrelease the first (older or oldest) UL WUS configuration and may only retain the second (newer or newest) UL WUS configuration.

[0012] According to some aspects, a UE receives, from a candidate cell supporting on- demand SIB, an indication that periodic SIB transmission is deactivated for the candidate cell. The UE transmits, to the candidate cell based on an UL WUS configuration list with a first UL WUS configuration for the candidate cell, a WUS on uplink resources to request an on-demand SIB transmission from the candidate cell. Based on the UL WUS configuration list being inapplicable to the candidate cell, the UE bars access to the candidate cell and selects a different candidate cell to access.

[0013] According to some aspects, a candidate cell that supports on-demand SIB transmits an indication that periodic SIB transmission is deactivated for the candidate cell. The candidate cell receives, from a UE, a WUS on uplink resources indicated by an UL WUS configuration to request an on-demand SIB transmission from the candidate cell. In response to the WUS, the candidate cell transmits the on-demand SIB.

[0014] According to some aspects, a first cell that is different from a candidate cell transmits, to a UE, an UL WUS configuration indicating UL resources for requesting an on- demand SIB transmission from the candidate cell.BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Fig. 1 A is a block diagram of an example system that includes a plurality of user equipments (UEs) and network entities in communication over one or more cells according to an embodiment.

[0016] Fig. IB is a block diagram of an example base station including a central unit (CU) and a distributed unit (DU) that can operate in the system of Fig. 1A.

[0017] Fig. 2 is a block diagram of an example protocol stack according to which the UE of Fig. 1A communicates with a CU and a DU.4G114380 2870WO

[0018] FIG. 3 is a signaling diagram illustrating an example of a UE requesting a SIB 1 from a candidate NES cell that supports on-demand SIB1 transmission based on an uplink wake-up signal (UL WUS) configuration or the UE selecting a non-NES cell when the UE does not have a UL WUS configuration for that candidate NES cell.

[0019] FIG. 4A is a signaling diagram illustrating an example of a UE retaining the UL WUS configuration for a candidate NES cell when the UE accesses a non-NES cell and the UE subsequently requesting a SIB1 from the candidate NES cell based on the retained UL WUS configuration.

[0020] FIG. 4B is a signaling diagram illustrating an example of a UE releasing the UL WUS configuration for a candidate NES cell when the UE accesses a non-NES cell and the UE subsequently attempting to perform an on-demand SIB1 request procedure with the candidate NES cell.

[0021] FIG. 4C is a signaling diagram illustrating an example of a UE releasing the UL WUS configuration for a candidate NES cell when the UE accesses a non-NES cell and the UE refraining from performing an on-demand SIB1 request procedure with the candidate NES cell.

[0022] FIG. 5A is a signaling diagram illustrating an example of a UE retaining the UL WUS configuration for a candidate NES cell when the UE moves out of coverage of the candidate NES cell and the UE subsequently requesting a SIB 1 from the candidate NES cell based on the retained UL WUS configuration when the UE moves back into coverage of the candidate NES cell.

[0023] FIG. 5B is a signaling diagram illustrating an example of a UE releasing the UL WUS configuration for a candidate NES cell when the UE moves out of the coverage of the candidate NES cell and the UE subsequently attempting to perform an on-demand SIB1 request procedure with the candidate NES cell when the UE moves back into coverage of the candidate NES cell.

[0024] FIG. 5C is a signaling diagram illustrating an example of a UE releasing the UL WUS configuration for a candidate NES cell when the UE moves out of the coverage of the candidate NES cell and the UE refraining from performing an on-demand SIB1 request procedure with the candidate NES cell when the UE moves back into coverage of the candidate NES cell.5G114380 2870WO

[0025] FIG. 6A is a flow diagram of an example method that can be implemented by a UE for requesting a SIB1 from a candidate NES cell that supports on-demand SIB1 transmission based on a UL WUS configuration or the UE selecting another cell when the UL WUS configuration is not available.

[0026] FIG. 6B is a flow diagram of an example method that can be implemented by a UE for requesting a SIB1 from a candidate NES cell that supports on-demand SIB1 transmission based on a UL WUS configuration or the UE selecting another cell when the NES cell does not support on-demand SIB1 transmission or when the UL WUS configuration is not available.

[0027] FIG. 7A is a flow diagram of an example method that can be implemented by a UE for retaining the UL WUS configuration for a candidate NES cell when the UE accesses another cell and the UE subsequently requesting a SIB1 from the candidate NES cell based on the retained UL WUS configuration.

[0028] FIG. 7B is a flow diagram of an example method that can be implemented by a UE for releasing the UL WUS configuration for a candidate NES cell when the UE accesses another cell and the UE subsequently attempting to perform an on-demand SIB1 request procedure with the candidate NES cell or the UE refraining from performing an on-demand SIB1 request procedure with the candidate NES cell.

[0029] FIG. 7C is a flow diagram of an example method that can be implemented by a UE for retaining or releasing the UL WUS configuration for a candidate NES cell depending on whether the candidate NES cell and a second cell use the same radio access technology’ (RAT) when the UE accesses the second cell.

[0030] FIG. 7D is a flow diagram of an example method that can be implemented by a UE for retaining or releasing the UL WUS configuration for a candidate NES cell depending on whether the candidate NES cell and a second cell have the same configured area ID when the UE accesses the second cell.

[0031] FIG. 7E is a flow diagram of an example method that can be implemented by a UE for retaining or releasing the UL WUS configuration for a candidate NES cell depending on whether the UE receives from a second cell a message to release the UL WUS configuration when the UE accesses the second cell.

[0032] FIG. 8A is a flow diagram of an example method that can be implemented by a UE for retaining the UL WUS configuration for a candidate NES cell when the candidate NES6G114380 2870WOcell is out of coverage and the UE subsequently requesting a SIB1 from the candidate NES cell based on the retained UL WUS configuration when the candidate NES cell is back in coverage.

[0033] FIG. 8B is a flow diagram of an example method that can be implemented by a UE for releasing the UL WUS configuration for a candidate NES cell when the candidate NES cell is out of coverage and the UE subsequently attempting to perform an on-demand SIB1 request procedure with the candidate NES cell when the candidate NES cell is back in coverage or the UE refraining from performing an on-demand SIB 1 request procedure with the candidate NES cell.

[0034] FIG. 9 is a flow diagram of an example method that can be implemented by a UE for using a validity timer to measure the validity period of a first on-demand SIB 1 from a candidate NES cell and for performing an on-demand SIB1 request procedure with the candidate NES cell to request a second on-demand SIB1 when the first on-demand SIB1 is no longer valid.

[0035] FIG. 10 is a flow diagram of an example method that can be implemented by a network entity of a candidate NES cell for determining that a validity period for a first on- demand SIB1 from the candidate NES cell expires and for transmitting a second on-demand SIB1 in response to the invalidity of the first on-demand SIB1.

[0036] FIG. 11 A is a flow diagram of an example method that can be implemented by a UE for replacing a first UL WUS configuration by a second UL WUS configuration when both UL WUS configurations are for the same candidate NES cell or for retaining both UL WUS configurations when the first UL WUS configurations and the second UL WUS configuration are for different candidate NES cells.

[0037] FIG. 1 IB is a flow diagram of an example method that can be implemented by a UE for modifying a first UL WUS configuration based on a second UL WUS configuration when both UL WUS configurations are for the same candidate NES cell or for retaining both UL WUS configurations when the first UL WUS configurations and the second UL WUS configuration are for different candidate NES cells.

[0038] FIG. 11C is a flow diagram of an example method that can be implemented by a UE for modifying a first UL WUS configuration based on a second UL WUS configuration when both UL WUS configurations are for the same candidate NES cell or for changing a list7G114380 2870WOof UL WUS configurations when the first UL WUS configuration and the second UL WUS configuration are for different candidate NES cells.

[0039] FIG. 12 is a flow diagram of an example method that can be implemented by a UE for detecting an event for invalidating a UL WUS configuration and for invalidating the UL WUS configuration in response to detecting the event.

[0040] FIG. 13 is a flow diagram of an example method that can be implemented by a network entity of a candidate NES cell for configuring a UE to detect an event to invalidate a UL WUS configuration for the candidate NES cell.

[0041] FIG. 14 is a flowchart of a method of wireless communication at a UE for requesting a SIB1 from a candidate NES cell that supports on-demand SIB1 transmission based on a UL WUS configuration for the candidate NES cell according to an embodiment.

[0042] FIG. 15 is a flowchart of a method of wireless communication at a candidate NES cell for transmitting on-demand SIB1 according to an embodiment.

[0043] FIG. 16 is a flowchart of a method of wireless communication at a first cell for transmitting a UL WUS configuration for requesting on-demand SIB1 from a different candidate NES cell that supports on-demand SIB1 transmission according to an embodiment.

[0044] FIG. 17 is a diagram illustrating a hardware implementation for an example UE apparatus.

[0045] FIG. 18 is a diagram illustrating a hardware implementation for one or more example network entities.DETAILED DESCRIPTION OF THE DRAWINGS

[0046] FIG. 1 A a block diagram of an example system that includes a plurality of user equipments (UEs) and network entities in communication over one or more cells according to an embodiment. The wireless communications system includes user UEs 102 and base stations / network entities 104. Some base stations may include an aggregated base station architecture and other base stations may include a disaggregated base station architecture. The aggregated base station architecture utilizes a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node. A disaggregated base station architecture utilizes a protocol stack that is physically or logically distributed among two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108. central unit (CU) 1 10). For example, a CU 1 10 is implemented within a RAN node, and one or more DUs 1088G114380 2870WOmay be co-located with the CU 110, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs 108 communicates with one or more RUs 106. Any of the RU 106, the DU 108 and the CU 110 can be implemented as virtual units, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). The base station / network entity 104 (e.g., an aggregated base station or disaggregated units of the base station, such as the RU 106 or the DU 108), may be referred to as a transmission reception point (TRP).

[0047] In some implementations, operations of the base station 104 and / or network designs are on aggregation characteristics of base station functionality. For example, disaggregated base station architectures are utilized in an integrated access backhaul (IAB) network, an open-radio access network (O-RAN) network, or a virtualized radio access network (vRAN), which may also be referred to a cloud radio access network (C-RAN). Disaggregation includes distributing functionality across the two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network designs. The various units of the disaggregated base station architecture, or the disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit. For example, the base stations 104b, 104d, 104e and / or the RUs 106a, 106b, 106c, 106d communicate with the UEs 102a, 102b, 102c, 102d, 102e, and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. Multiple RUs 106 and / or base stations 104 may simultaneously serve the UEs 102, such as by intra-cell and / or inter-cell access links between the UEs 102 and the RUs 106 / base stations 104. In examples, the RUs 106 of the base stations 104b. 104e share the same DU 108. In other examples, the base stations 104b, 104e have independent DUs 108. Likewise, the DU(s) 108 of the base stations 104b, 104e may share the same CU 110. In other examples, the base stations 104b, 104e have independent CUs 110. The base stations 104b. 104e may also be in communication with each other over a backhaul link 164.

[0048] In some implementations, the RU 106, the DU 108. and the CU 110 include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via a wired or wireless transmission medium. For example, a wired interface can be configured to transmit or receive the information / signals over a wired transmission medium, such as via the fronthaul link 160 between the RU 106d and the baseband unit (BBU) 112 of the base station 104d associated with the cell 190d. The BBU 1 12 includes a DU 108 and a CU 110, which may also have a wired interface (e g., midhaul9G114380 2870WOlink) configured between the DU 108 and the CU 110 to transmit or receive the information / signals between the DU 108 and the CU 110. In further examples, a wireless interface includes a receiver, a transmitter, or a transceiver, such as an RF transceiver, configured to transmit and / or receive the information / signals via the wireless transmission medium, such as for information communicated betw een the RU 106a of the cell 190a and the base station 104e of the cell 190e via cross-cell communication beams 136-138 of the RU 106a and the base station 104e.

[0049] The RUs 106 are configured to implement lower layer functionality. For example, the RU 106 is controlled by the DU 108 and corresponds to a logical node that hosts RF processing functions, or lower layer PHY functionality, such as execution of fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functionality of the RU 106 may be based on the functional split, such as a functional split of lower layers.

[0050] The RUs 106 transmit or receive over-the-air (OTA) communication with one or more UEs 102. For example, the RU 106b of the cell 190b communicates with the UE 102b of the cell 190b via a first set of communication beams 132 of the RU 106b and a second set of communication beams 134b of the UE 102b, which may correspond to inter-cell communication beams or, in some examples, cross-cell communication beams. For instance, the UE 102b of the cell 190b communicates with the RU 106a of the cell 190a via a third set of communication beams 134a of the UE 102b and a fourth set of communication beams 136 of the RU 106a. DUs 108 can control both real-time and non-real-time features of control plane and user plane communications of the RUs 106.

[0051] Any combination of the RU 106, the DU 108, and the CU 110, or reference thereto individually, may correspond to a base station 104. Thus, the base station 104 may include at least one of the RU 106. the DU 108, or the CU 110. The base stations 104 provide the UEs 102 with access to a core network. The base stations 104 relay communications between the UEs 102 and the core network (not shown). The base stations 104 may be associated with macrocells for higher-power cellular base stations and / or small cells for lower-power cellular base stations. For example, the cell 190e corresponds to a macrocell, whereas the cells 190a- 190d correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network that includes at least one macrocell and at least one small cell may be referred to as a “heterogeneous network.” ioG114380 2870WO

[0052] Transmissions from a UE 102 to a base station 104 / RU 106 are referred to as uplink (UL) transmissions, whereas transmissions from the base station 104 / RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions and downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106d utilizes antennas of the base station 104d of cell 190d to transmit a downlink / forward link communication to the UE 102d or receive an uplink / reverse link communication from the UE 102d based on the Uu interface associated with the access link between the UE 102d and the base station 104d / RU 106d.

[0053] In some implementations, communication links between the UEs 102 and the base stations 104 / RUs 106 are based on multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be associated with one or more carriers. In some implementations, the UEs 102 and the base stations 104 / RUs 106 utilize a spectrum bandwidth of T MHz (e.g., 5, 10, 15, 20, 100, 400, 800, 1600, 2000, etc. MHz) per carrier allocated in a carrier aggregation of up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along a frequency spectrum. In examples, uplink and downlink earners are allocated in an asymmetric manner, with more or fewer carriers allocated to either the uplink or the downlink. In some implementations, a primary component carrier and one or more secondary component carriers are included in the component carriers. In some implementations, the primary component carrier is associated with a primary cell (PCell) and a secondary component carrier is associated with a secondary cell (SCell).

[0054] In some implementations, the UEs 102 and the base stations 104 / RUs 106 each includes a pl ural i ty of antennas. The plurality of antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that facilitate beamforming operations. For example, the RU 106b transmits a downlink beamformed signal based on a first set of communication beams 132 to the UE 102b in one or more transmit directions of the RU 106b. In some implementations, the UE 102b receives the downlink beamformed signal based on a second set of communication beams 134b from the RU 106b in one or more receive directions of the UE 102b. In a further example, the UE 102b also transmits an uplink beamformed signal (e.g., sounding reference signal (SRS)) to the RU 106b based on the second set of communication beams 134b in one or more transmit directions of the UE 102b. The RU 106b receives the uplink beamformed signal from the UE 102b in one or more11G114380 2870WOreceive directions of the RU 106b. The UE 102b performs beam training to determine the best receive and transmit directions for the beamformed signals. The transmit and receive directions for the UEs 102 and the base stations 104 / RUs 106 may or may not be the same.

[0055] In further examples, beamformed signals are communicated between a first base station / RU 106a and a second base station 104e. For instance, the base station 104e of the cell 190e transmits a beamformed signal to the RU 106a based on the communication beams 138 in one or more transmit directions of the base station 104e. The RU 106a receives the beamformed signal from the base station 104e of the cell 190e based on the RU communication beams 136 in one or more receive directions of the RU 106a. In further examples, the base station 104e transmits a downlink beamformed signal to the UE 102e based on the communication beams 138 in one or more transmit directions of the base station 104e. The UE 102e receives the downlink beamformed signal from the base station 104e based on UE communication beams 130 in one or more receive directions of the UE 102e. In some implementations, the UE 102e also transmits an uplink beamformed signal to the base station 104e based on the UE communication beams 130 in one or more transmit directions of the UE 102e, such that the base station 104e receives the uplink beamformed signal from the UE 102e in one or more receive directions of the base station 104e.

[0056] The base station 104 may include and / or be referred to as a network entity. That is, “network entity ’ may refer to the base station 104 or at least one unit of the base station 104, such as the RU 106, the DU 108, and / or the CU 110. The base station 104 may also include and / or be referred to as a next generation evolved Node B (ng-eNB), a next generation NB (gNB), an evolved NB (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic sendee set (BSS), an extended service set (ESS), a TRP, a network node, network equipment, or other related terminology. The base station 104 or an entity at the base station 104 can be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station, or a disaggregated base station including one or more RUs 106, DUs 108. and / or CUs 110. A set of aggregated or disaggregated base stations may be referred to as a next generation-radio access network (NG-RAN). In some examples, the UE 102a operates in dual connectivity (DC) with the base station 104e and the base station / RU 106a. In such cases, the base station 104e can be a master node and the base station / RU 160a can be a secondary node.

[0057] Still referring to FIG. 1A, in certain aspects, any of the UEs 102 includes an on- demand SIB requester component 140 configured to: receive, from a candidate cell12G114380 2870WOsupporting on-demand SIB, an indication that periodic SIB transmission is deactivated for the candidate cell; transmit, to the candidate cell, a WUS on uplink resources to request an on- demand SIB transmission from the candidate cell when the UE has an available UL WUS configuration for that candidate cell. The UL WUS configuration indicates the uplink resources for the WUS. When the UE does not have a UL WUS configuration for that candidate cell, the on-demand SIB requester component 140 is configured to select a different candidate cell to access.

[0058] In certain aspects, any of the base stations 104 or a network entity of the base stations 104 includes an on-demand SIB transmission component 150 configured to: transmit an indication that periodic SIB transmission is deactivated for the candidate cell of the base station; receive, from a UE, a WUS on uplink resources indicated by an UL WUS configuration to request an on-demand SIB transmission from the candidate cell; and transmit the on-demand SIB in response to the WUS.

[0059] In certain aspects, any of the base stations 104 or a network entity of the base stations 104 includes a candidate cell on-demand SIB assistor component 155 configured to: transmit, to a UE, an UL WUS configuration indicating UL resources for requesting an on- demand SIB transmission from the candidate cell.

[0060] Accordingly, FIG. 1 A describes a wireless communication system that may be implemented in connection with aspects of one or more other figures described herein. Further, although the following description is focused on 5G NR. the concepts described herein may be applicable to other similar areas, such as 5G- Advanced and future versions, LTE, LTE-advanced (LTE-A), and other wireless technologies, such as 6G.

[0061] Fig. IB is a block diagram of an example base station including a central unit (CU) and a distributed unit (DU) that can operate in the system of Fig. 1A. The base station in this implementation can include a CU 110 and one or more DUs 108. The CU 110 (e.g., CU for control plane(s) (CU-CP(s)) 110A and CU for user plane(s) (CU-UP(s) HOB) is equipped with processing hardware that can include one or more general-purpose processors such as CPUs and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. In one example, the processing hardware of the CU 110 includes a protocol controller configured to manage or control operations of one or more protocols. For example, the protocols include radio resource control (RRC), Packet Data Convergence Protocol (PDCP),13G114380 2870WOand / or Service Data Adaptation Protocol (SDAP). In another example, the protocols include Internet protocol (IP), Fl application protocol (AP). X2 AP, Xn AP, X6G AP, SI AP, NG AP, and / or N6G AP. The DU 108 is also equipped with processing hardware that can include one or more general-purpose processors such as CPUs and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general- purpose processors, and / or special-purpose processing units. In some examples, the processing hardware is the process hardware 130. In other example, the process hardware includes a protocol controller configured to manage or control operations of one or more protocols. For example, the protocols include IP and / or Fl AP. In some other examples, the processing hardware in an example implementation includes a medium access control (MAC) controller configured to manage or control one or more MAC operations or procedures (e.g.. a random access procedure) and a radio link control (RLC) controller configured to manage or control one or more RLC operations or procedures when the base station 106 operates as master node (MN) or a secondary7node (SN). In some implementations, the process hardware includes further a physical layer controller configured to manage or control one or more physical layer operations or procedures.

[0062] Fig. 2 is a block diagram of an example protocol stack according to which the UE of Fig. 1A communicates with a CU 1 10 and a DU 108. The radio protocol stack is functionally split as shown by the radio protocol stack 250 in Fig. 2. The CU 110 at any of the base stations 104 or 106 can hold all the control and upper layer functionalities (e.g., RRC 214, SDAP 212, NR PDCP 210), while the lower layer operations (e.g., NR RLC 206B, NR MAC 204B, and NR PHY 202B) are delegated to the DU 108. To support connection to a 5GC, NR PDCP 210 provides signaling radio bearers (SRBs) to RRC 214, and NR PDCP 210 provides data radio bearers (DRBs) to SDAP 212 and SRBs to RRC 214.

[0063] To enable network energy savings (NES) in 5G networks, a cell (i.e., NES cell) of a base station broadcasts the MIB but stop transmitting SIB1 when there is reduced demand (e.g., during a non-peak period). An on-demand SIB1 refers to a SIB1 that is no longer an always-on (periodically broadcast) SIB1 and can be turned off by the network entity for NES purposes. Upon receiving an uplink (cell) wake-up-signal from the UE 102, the network entity can turn on the SIB 1 transmission in a cell for a predetermined period of time. This temporary SIB1 transmission can be a broadcast transmission and might be broadcast in a unidirectional manner toward a detected source of the uplink wake-up-signal. The UE 102 is provided with an uplink wake-up-signal (UL WUS) configuration in order to transmit the UL14G114380 2870WOWUS in the cell with a deactivated periodic SIB1 broadcast transmission. The UL WUS configuration may be configured only for one NES cell. Alternatively, the UL WUS configuration may be configured multiple NES cells.

[0064] Next, several examples show scenarios in which the base station operating in the system of Fig. 1 A transmits a UL WUS configuration to the UE 102 and the UE 102 transmitting an UL WUS to request on-demand SIB1 from an NES cell of the base station based on the UL WIS configuration. Generally speaking, events in that are similar are labeled with similar reference numbers (e.g., event 311 of Fig. 3 is similar to event 411 of Figs. 4A-4C, block 611 of Figs. 6A and 6B, event 401 of Figs. 4A-4C is similar to block 701 of Figs. 7A-8B and 9 and block 1001 of Fig. 10 and block 1101 of Figs. 11A-11C), with differences discussed below where appropriate. With the exception of the differences show n in the figures and discussed below, any of the alternative implementations discussed with respect to a particular event (e.g., for messaging and processing) may apply to events labeled with similar reference numbers in other figures.

[0065] FIG. 3 is a signaling diagram 300 illustrating an example of a UE 102 requesting a SIB1 from a candidate NES cell 126B that supports on-demand SIB1 transmission based on a UL WUS configuration or the UE selecting a non-NES cell when the UE does not have a UL WUS configuration for that candidate NES cell.

[0066] Referring first to Fig. 3, in a scenario 300, the RAN 105 includes a non-NES cell 124, a NES cell 126B, and a third cell 126A. The third cell 126A may be operating in non- NES or NES mode. In some implementations, the cells 124, 126B, and 126A are operated by BSs as described with respect to Fig. 1 A. In other implementations, the cells 124, 126B, and 126A are operated by the same base station in the RAN 105. The UE 102 is initially in the idle / inactive state (e.g., RRC IDLE / RRC INACTIVE state) or is recently tumed-on. In one embodiment, the RAN 105 transmits 401-1. to the UE 102. an UL WUS configuration (e.g.. UL WUS configuration 1) via cell 126B. The UL WUS configuration includes (e.g., indicates) UL resources (e.g., PRACH resources) for requesting on-demand SIB1 from cell 126B. In the following discussions, an UL WUS configuration may also be referred to as an UL configuration.

[0067] The UE 102 initially selects or reselects 302 the cell 126B and then receives 304 a M1B from the cell 126B. The MIB may indicate or include a system frame number (SFN) or a portion of a SFN. In some implementations, the MIB includes a first indication (e.g., set to15G114380 2870WOa first value or an invalid value) indicating that SIB1 is not periodically broadcast. In some implementations, the first indication is a SSB subcarrier offset configuration (e.g., ssb- SubcarrierOffset) set to a first value or an invalid value. In some implementations, the MIB includes a second indication indicating support of on-demand SIB1. In some implementations, the UE 102 is powered on, performs a cell search, finds the cell 126B during the cell search, and selects the cell 126B. In other implementations, the UE 102 reselects the cell 126B when the UE 102 is camped on a first cell (not shown in Fig. 3). When the UE 102 selects or reselects the cell 126B, the UE 102 then determines 308 whether the UE has an UL WUS configuration used to request transmission of on-demand SIB1 from the cell 126B. In some implementations, the UL WUS configuration configures or indicates time and / or frequency resources for transmitting the UL WUS. For example, the UL WUS is a random access preamble and the time and / or frequency resources are or include one or more PRACH occasions. In some implementations, the UE 102 maintains a list of UL WUS configurations, where each UL WUS configuration is applicable for requesting an on-demand SIB 1 transmission from a corresponding one or more NES cells.

[0068] If the UE 102 has an UL WUS configuration used to request transmission of an on- demand SIB1 from the cell 126B, the UE 102 transmits 310, to the cell 126B, a UL WUS to request transmission of an on-demand SIB1. In some embodiments, if the UL WUS is a random access preamble, the RAN 105 transmits a random access response 312 corresponding to the random access preamble. In response to the UL WUS, the RAN 105 transmits (e.g., broadcasts) 314 a first SIB1 on the cell 126B. The UE 102 receives 314 the first SIB from the cell 126B. In some implementations, the RAN 105 additionally transmits 316 one or more other SIB(s) on the cell 126B in response to the UL WUS. In such cases, the RAN 105 indicates broadcast of the other SIB(s) in the first SIB1. In some implementations, the first SIB1 includes scheduling information indicating broadcast of the other SIB(s) on the cell 126B. In some implementations, the UE 102 transmits a specific UL WUS that indicates the UE 102 is requesting not only the transmission of on-demand SIB1 transmission but also the transmission of other on-demand SIB(s). Such a specific UL WUS may be specific random access preamble(s) within the RACH Occasion (RO) configured for requesting the on-demand SIB1 transmission, or specific RO(s) configured for such a purpose (i.e., requesting not only on-demand SIB1 but also other on-demand SIBs).

[0069] In some implementations, the RAN 105 does not transmit an updated MIB in response to the UL WUS. In some implementations, after transmitting 310 the UL WUS or16G114380 2870WOreceiving 312 the random access response, the UE 102 attempts to receive or receives 314 the first SIB1 in accordance with a PDCCH configuration (e.g.. pdcch-ConflgSIBl). In some implementations, the RAN 105 preconfigures the UE 102 with the PDCCH configuration before event 302. In other implementations, the UE 102 receives the PDCCH configuration when the UE 102 receives 304 the MIB.

[0070] In some implementations, the RAN 105 transmits an updated MIB in response to the UL WUS. In some implementations, the RAN 105 excludes the first indication from the updated MIB to indicate a SIB1 (e.g., the first SIB1) will be broadcast on the cell 126B. In other implementations, the RAN 105 sets the first indication to a second value (different from a first value indicating SIB1 is not broadcast) or a valid value in the updated MIB to indicate that a SIB1 (e.g., the first SIB1) will be broadcast on the cell 126B. In such cases, the UE 102 attempts to receive or receive the updated MIB after (e.g., in response to) transmitting 310 the UL WUS or receiving 312 the random access response. After receiving the updated MIB, the UE 102 determines that a SIB1 (e.g., the first SIB1) is broadcast on the cell 126B based on the updated MIB where the first indication is excluded or set to the second value or the valid value. In response to the determination, the UE 102 attempts to receive or receives 314 the first SIB1, e.g., in accordance with configuration parameters in the updated MIB. In some implementations, the updated MIB includes a PDCCH configuration (e.g.. pdcch- ConfigSIB 1) and the UE 102 uses the PDCCH configuration to receive the first SIB1 314.

[0071] In some implementations, the RAN 105 transmits 401-2 UL WUS configuration associated with cell 126B (e.g., UL WUS configuration 2) to the UE 102 via non-NES cell 124 before event 302. In some implementations, the RAN 105 transmits 401-3 the UL WUS configuration associated with cell 126B (e.g., UL WUS configuration 3) to the UE 102 via cell 126A before event 302. The UE 102 receives the UL WUS configuration from the cell 124 or the cell 126A. For example, the RAN 105 transmits (e.g., broadcasts) a SIB including the UL WUS configuration on the cell 124 or 126 A, and the UE 102 receives the SIB while camping on the cell 124 or 126A. The UL WUS configurations associated with cell 126B received from cells 126B, 124, and 126A may be the same or may be different. In some implementations, the UE 102 stores only one copy of the UL WUS configuration per one or more associated cells. For example, if the UL WUS configurations are different, the UE 102 may replace or modify its stored UL WUS configuration with the most recently received UL WUS configuration. In some implementations, the SIB or the UL WUS configuration includes a first physical cell identity (PCI) of the cell 126B to indicate that the UL WUS17G114380 2870WOconfiguration is associated with the first PCI or the cell 126B. In some implementations, the SIB or the UL WUS configuration indicates that the UL WUS configuration is associated with one or multiple carrier frequencies. The SIB may be an existing SIB or a new SIB. For example, the SIB is SIB x, where x is one of 1, 2, 3.. . ., 35.

[0072] In other implementations, the RAN 105 periodically transmits (e.g., broadcasts) a new SIB (e.g., SIB0.5) including the UL WUS configuration associated with cell 126B on the cell 126B itself. The UE 102 receives the new SIB from the cell 126B before event 308 and after event 302. In some implementations, the new SIB or the UL WUS configuration includes a first physical cell identity (PCI) of the cell 126B to indicate that the UL WUS configuration is associated with the first PCI or the cell 126B. In yet other implementations, before event 302, the UE 102 camped on the cell 126B and received the UL WUS configuration in a SIB from the cell 126B. The SIB may be the SIB0.5, SIB1, or another SIB. In yet other implementations, the UE 102 is preconfigured with the UL WUS configuration associated with the first PCI of the cell 126B.

[0073] In some implementations, the RAN 105 transmits 401-1 the UL WUS configuration (called first UL WUS configuration) associated with the cell 126B via cell 126B through a SIB1 similar to the first SIB1 314. Thus, while the RAN 105 is broadcasting the SIB1 on the cell 126B, the UE 102 and / or other UEs camping on the cell 126B obtain the first UL WUS configuration from the SIB1. Alternatively, the RAN 105 includes the UL WUS configuration in a second SIB instead of the SIB1, similar to one of the other SIB(s) 316. Thus, while the RAN 105 is broadcasting the second SIB on the cell 126B, other UEs camping on the cell 126B obtain the first UL WUS configuration from the second SIB. In other implementations, the first SIB1 (e.g., 314) from the cell 126B in response to the UL WUS includes a second UL WUS configuration for requesting transmission of an on-demand SIB1 from the cell 126B instead of the first UL WUS configuration. Thus, while the RAN 105 is broadcasting 314 the first SIB1 on the cell 126B, the UE 102 and / or other UEs camping on the cell 126B obtain the second UL WUS configuration from the first SIB1. Alternatively, the RAN 105 includes the second UL WUS configuration in a second SIB of the other SIB(s) (e.g., 316) instead of the first SIB1. Thus, while the RAN 105 is broadcasting 316 the second SIB on the cell 126B, the UE 102 and / or other UEs camping on the cell 126B obtain the second UL WUS configuration from the second SIB. In some implementations, the second UL WUS configuration augments or modifies the first UL WUS configuration. Thus, the UE 102 augments or modifies the first UL WUS configuration with18G114380 2870WOthe second UL WUS configuration. In other implementations, the second UL WUS configuration replaces the first UL WUS configuration. Thus, the UE 102 replaces the first UL WUS configuration with the second UL WUS configuration.

[0074] In some implementations, the RAN 105 includes, in the SIB1 or the second SIB of event 401-1 314, or 316, a third UL WUS configuration for requesting transmission of an on- demand SIB1 from a third cell (not show n in Fig. 3). In the case of the SIB1, the SIB1 may include a second physical cell identity (PCI) of the third cell to indicate that the third UL WUS configuration is associated with the second PCI or the third cell. Alternatively, the third UL WUS configuration may include the second PCI. In the case of the second SIB, the second SIB may include the second PCI to indicate that the third UL WUS configuration is associated with the second PCI or the third cell. Alternatively, the third UL WUS configuration includes the second PCI to indicate that the third UL WUS configuration is associated with the second PCI or the third cell.

[0075] In some implementations, the RAN 105 neither transmits (e.g., broadcasts) the first UL WUS configuration nor the second UL WUS configuration on the cell 126B. In such cases, the first SIB1 314 and the other SIB(s) 316 neither include the first UL WUS configuration nor the second UL WUS configuration. In some implementations, the UE 102 maintains (e.g., keeps or retains) the first UL WUS configuration, the second UL WUS configuration, and / or the third UL WUS configuration, e.g.. while staying in the cell 124, the cell 126A and / or the cell 126B or moving among the cell 124, the cell 126A and / or the cell 126B.

[0076] As mentioned, in some implementations, the UL WUS is a random access preamble and the RAN 105 transmits 312 a random access response to the UE 102 via the cell 126B. In the random access response, the RAN 105 includes a random access preamble identity / identifier (ID) indicating the random access preamble. When the UE 102 receives the random access response and retrieves the random access preamble ID, the UE 102 determines that the RAN 105 received the random access preamble based on the random access preamble ID.

[0077] After receiving the MIB, the first SIB1 and / or the other SIB(s) from the cell 126B, the UE 102 may access 318 cell 126B in accordance with configuration parameters in the first S1B1. In some implementations, the configuration parameters include a random access channel (RACH) configuration, a physical downlink control channel (PDCCH) configuration,19G114380 2870WOa control resource set configuration, and / or a search space configuration. In some implementations, the UE 102 performs a random access procedure to access the cell 126B in accordance with the configuration parameters. In the random access procedure, the UE 102 transmits a random access preamble on the cell 126B to the RAN 105 based on the RACH configuration and receives a random access response on the cell 126B form the RAN 105 based on the PDCCH configuration, the control resource set configuration, and / or the search space configuration.

[0078] In some implementations, the other SIB(s) 316 includes a SIB2, a SIB3, a SIB4, SIB5, SIB9 and / or SIBpos. In some implementations, the SIB2 contains cell re-selection information, mainly related to the cell 126B. In some implementations, the SIB3 contains information about the serving frequency and intra-frequency neighboring cells relevant for cell re-selection (e.g., including cell re-selection parameters common for a frequency as well as cell specific reselection parameters). In some implementations, the SIB4 contains information about other NR frequencies and inter-frequency neighboring cells relevant for cell re-selection (e.g., including cell re-selection parameters common for a frequency as well as cell specific reselection parameters). In some implementations, the SIB5 contains information about E-UTRA frequencies and E-UTRA neighboring cells relevant for cell reselection (e.g., including cell re-selection parameters common for a frequency as well as cell specific re-selection parameters). In some implementations, the SIB9 contains information related to GPS time and Coordinated Universal Time (UTC). In some implementations, SIBpos contains positioning assistance data.

[0079] In some alternative implementations, the RAN 105 refrains from transmitting the other SIB(s) upon receiving the UL WUS. i.e., event 316 is omitted. In such cases for some implementations, the first SIB1 includes a SIB request configuration. The UE 102 transmits a SIB request to the RAN 105 via the cell 126B to request some or all of the other SIB(s), in accordance with the SIB request configuration. In other alternative implementations, the RAN 105 transmits a portion of the other SIB(s) and refrains from transmitting the rest of the other SIB(s) in response to the UL WUS. In such cases for some implementations, the first SIB1 includes a SIB request configuration. The UE 102 transmits a SIB request to the RAN 105 via the cell 126B to request some or all of the rest of the other SIB(s), in accordance with the SIB request configuration.

[0080] In some implementations, if the UE 102 does not have a valid UL WUS configuration for requesting transmission of on-demand SIB1 from the cell 126B, the UE 10220G114380 2870WOmay bar 309A the cell 126B and / or perform 311 a cell search. In cell barring, the UE 102 measures the SSB of the cell 126B but does not select the cell 126B. Alternatively, the UE 102 may bar 309B the carrier frequency used by the cell 126B. In carrier frequency barring, the UE 102 avoids synchronizing and / or measuring a SSB of the cell 126B to avoid selecting the cell 126B. In some implementations, the UE 102 bars the cell 126B or the carrier frequency for a predetermined time duration (e.g.. 300 seconds). In other implementations, the UE 102 bars the cell 126B or the carrier frequency until receiving a UL WUS configuration for requesting transmission of an on-demand SIB1 from the cell 126B. During the cell search, the UE 102 may find cell 124 and select 311 the cell 124. After selecting the cell 124, the UE 102 receives 320 a MIB from the cell 124. In some implementations, the MIB of the cell 124 indicates (e.g., includes) a SFN or a portion of the SFN. The MIB of the cell 124 may indicate SIB1 is broadcast (e.g., non-NES) or does not indicate support of on- demand SIB1. The MIB includes neither the first indication (i.e., cell 124 is broadcasting SIB1) nor the second indication (i.e., cell 124 does not support on-demand SIB1). After receiving the MIB of the cell 124, the UE 102 receives 324 a second SIB1 and optionally receives 326 one or more other SIB(s) from the cell 124. In some implementations, examples and implementations described for the first SIB1 on cell 126B can apply to the second SIB1 on cell 124. In other implementations, the second SIB1 contains information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of the other SIB(s) 326.

[0081] While barring the cell 126B or the carrier frequency, the UE 102 may receive, from a cell (e.g.. cell 126A, cell 126B, or cell 124). a UL WUS configuration for requesting transmission of an on-demand SIB1 from the cell 126B. If the UE 102 receives the UL WUS configuration, the UE 102 stops barring the cell 126B or the carrier frequency.

[0082] In some implementations, examples and implementations described for the other SIB(s) 316 on cell 126B can apply to the other SIB(s) 326 on cell 124. In other implementations, the other SIB(s) 326 includes a SIB2, a SIB3. a SIB4, and / or a SIB5. In some implementations, the SIB2 contains common and shared channel information. In some implementations, the SIB3 contains cell re-selection information. In some implementations, the SIB4 contains information about the serving frequency and intra-frequency neighboring cells relevant for cell re-selection (e.g., including cell re-selection parameters common for a frequency as well as cell specific re-selection parameters). In some implementations, the SIB5 contains information about other E-UTRA frequencies and inter-frequency neighboring21G114380 2870WOcells relevant for cell re-selection (e.g., including cell re-selection parameters common for a frequency as well as cell specific re-selection parameters).

[0083] After receiving the MIB, the second SIB1 and / or the other SIB(s) from the cell 124, the UE 102 may access 328 cell 124 in accordance with configuration parameters in the second SIB1 and / or the STB2 of the other SIB(s), similar to event 318.

[0084] The events 302, 304, 308, 309A (optional), 309B (optional), 31 1, 310, 312 (optional), 314, 316 (optional), and 318 (optional) are collectively referred to in Fig. 3 as an on-demand SIB1 request procedure 390. The events 320, 324, 326 (optional), and 328 (optional) are collectively referred to in Fig. 3 as a non-NES cell selection procedure 392.

[0085] In one aspect, when the UE 102 moves among cells, the UE 102 decides how to manage UL WUS configurations that are not applicable to a currently accessed cell, as discussed in Figs. 4A-4C.

[0086] FIG. 4A is a signaling diagram 400A illustrating an example of a UE 102 retaining the UL WUS configuration for a candidate NES cell 126B when the UE 102 accesses a non- NES cell 124 and the UE 102 subsequently requesting a SIB1 from the candidate NES cell 126B based on the retained UL WUS configuration. The NES cell 126B supports on-demand SIB1. The RAN 105 includes the non-NES cell 124, the NES cell 126B, and a third cell 126 A. The third cell 126 A may be operating in non-NES or NES mode.

[0087] The UE 102 initially camps on the cell 126 A. The RAN 105 transmits 401-3 the UL WUS configuration associated with cell 126B to the UE 102 via cell 126A. The UL WUS configuration includes (e.g., indicates) UL resources (e.g., PRACH resources) for requesting on-demand SIB1 from cell 126B.

[0088] The UE 102 attempts to access 490-1 the cell 126B and determines whether to perform an on-demand SIB1 request procedure with the cell 126B. The on-demand SIB1 request procedure 390 of Fig. 3 may apply here. For example, the UE 102 transmits a UL WUS to request on-demand SIB 1 from cell 126B based on the UL WUS configuration, receives a SIB1 from the cell 126B, and accesses the cell 126B in accordance with configuration parameters in the SIB 1.

[0089] The UE 102 then selects or reselects 411 the cell 124. The non-NES cell selection procedure 392 of Fig. 3 may apply here. For example, the UE 102 receives the MIB from the cell 124, receives a SIB1 from the cell 124, and accesses 492 the cell 124 in accordance with configuration parameters in the SIB similar to the non-NES cell selection procedure 392.22G114380 2870WO

[0090] The UE 102 maintains (e.g., retains or keeps) 430 the UL WUS configuration associated with the cell 126B in response to the selection or reselection of the cell 124 or when accessing 492 the cell 124 while the UE 102 camps on the cell 124, where the cell 124 in this example does not provide the UL WUS configuration associated with the cell 126B. The UE 102 may later use the retained UL WUS configuration when reselecting the cell 126B. The RAN 105 may transmit, on the cell 124, one or more other UL WUS configurations associated with one or more other cells in similar ways as described above.

[0091] The UE 102 subsequently accesses 490-2 the cell 126B and determines whether to perform an on-demand SIB1 request procedure with the cell 126B. The UE 102 uses the retained UL WUS configuration to transmit a UL WUS to request on-demand SIB1 from the cell 126B.

[0092] FIG. 4B is a signaling diagram 400B illustrating an example of a UE 102 releasing the UL WUS configuration for a candidate NES cell 126B when the UE 102 accesses a non- NES cell 124 and the UE 102 subsequently attempting to perform an on-demand SIB1 request procedure with the candidate NES cell 126B. As in Fig. 4A, the NES cell 126B supports on-demand SIB1. The RAN 105 includes the non-NES cell 124, the NES cell 126B, and a third cell 126A. The third cell 126A may be operating in non-NES or NES mode.

[0093] Operations 401-3, 490-1, 411, and 492 are the same as those in Fig. 4A. However, in contrast to Fig. 4A, the UE 102 releases 431 the UL WUS configuration associated with the cell 126B in response to the selection or reselection of the cell 124 or when accessing 492 the cell 124 while the UE 102 camps on the cell 124, where the cell 124 does not provide the UL WUS configuration associated with the cell 126B. In some implementations, the UE 102 releases the UL WUS configuration associated with the cell 126B regardless of whether the cell 124 and the cell 126B utilize the same radio access technology (RAT) or different RATs. In other implementations, the UE 102 releases the UL WUS configuration associated with the cell 126B if the cell 124 and the cell 126B utilize different RATs. If the cell 124 and the cell 126B utilize the same RAT, the UE 102 may retain the UL configuration as described for Fig. 4A. When released, the UE 102 is no longer able to use the UL WUS configuration to access the cell 126B.

[0094] The UE 102 subsequently attempts to access 490-2 the cell 126B and determines whether to perform an on-demand SIB1 request procedure with the cell 126B. Because the UL WUS configuration has been released, the UE 102 does not have a UL WUS23G114380 2870WOconfiguration for requesting transmission of on-demand SIB1 from the cell 126B. As a consequence, the UE 102 performs a cell search and / or select another cell, such as cell 126 A. In some implementations, the UE 102 does so, if the cell 126B is not broadcasting on- demand SIB1 at the time when the UE 102 is attempting 490-2 to access the cell 126B.

[0095] FIG. 4C is a signaling diagram 400C illustrating an example of a UE 102 releasing the UL WUS configuration for a candidate NES cell 126B when the UE 102 accesses a non- NES cell 124 and the UE 102 refraining from performing an on-demand SIB1 request procedure with the candidate NES cell 126B.

[0096] Fig. 4C is similar to Fig. 4B. except that after releasing the UL WUS configuration associated with the cell 126B, the UE 102 refrains 433 from measuring SSB or PBCH of the cell 126B so that selection or reselection of cell 126B will not occur (e.g., carrier frequency barring). In some implementations, the UE 102 does so if the UE 102 determines that the cell 126B does not transmit the on-demand SIB1. Alternatively, the UE 102 may measure the SSB or PBCH but does not select / reselect (e.g., cell barring) the cell 126B. In some implementations, the UE 102 does so if the UE 102 determines that the cell 126B does not transmit the on-demand SIB1.

[0097] In one aspect, while accessing a NES cell, the UE 102 may move out of the coverage of the NES cell. The UE 102 then decides how to manage the UL WUS configuration of the NES cell in this scenario, as discussed in Figs. 5A-5C.

[0098] FIG. 5A is a signaling diagram 500A illustrating an example of a UE 102 retaining the UL WUS configuration for a candidate NES cell 126B when the UE 102 moves out of coverage of the candidate NES cell 126B and the UE 102 subsequently requesting a SIB1 from the candidate NES cell 126B based on the retained UL WUS configuration when the UE 102 moves back into coverage of candidate NES cell 126B. The NES cell 126B supports on-demand SIB1. The RAN 105 includes the NES cell 126B and a second cell 126A. The cell 126A may be operating in non-NES or NES mode.

[0099] The UE 102 initially camps on the cell 126 A. The RAN 105 transmits 401-3 the UL WUS configuration associated with cell 126B to the UE 102 via cell 126A. The UL WUS configuration includes (e g., indicates) UL resources (e g., PRACH resources) for requesting on-demand SIB1 from cell 126B.

[0100] The UE 102 attempts to access 490-1 the cell 126B and determines whether to perform an on-demand SIB1 request procedure with the cell 126B. The on-demand SIB124G114380 2870WOrequest procedure 390 of Fig. 3 may apply here. For example, the UE 102 transmits a UL WUS to request on-demand SIB1 from cell 126B based on the UL WUS configuration, receives a SIB1 from the cell 126B, and accesses the cell 126B in accordance with configuration parameters in the SIB1.

[0101] While camping on the cell 126B, the UE 102 detects 532 out of coverage of the cell 126B, such as due to movement of the UE 102. The UE 102 maintains (e.g., retains or keeps) 430 the UL WUS configuration associated with the cell 126B in response to detecting the out of coverage condition. The UE 102 may later use the retained UL WUS configuration when reselecting the cell 126B.

[0102] The UE 102 subsequently accesses 490-2 the cell 126B and determines whether to perform an on-demand SIB1 request procedure with the cell 126B. The UE 102 uses the retained UL WUS configuration to transmit a UL WUS to request on-demand SIB1 from the cell 126B when the UE 102 moves back into coverage of the cell 126B. In some implementations, the UE 102 does so when the UE 102 determines that the cell 126B is not broadcasting the on-demand SIB1.

[0103] FIG. 5B is a signaling diagram 500B illustrating an example of a UE 102 releasing the UL WUS configuration for a candidate NES cell 126B when the UE 102 moves out of the coverage of the candidate NES cell 126B and the UE 102 subsequently attempting to perform an on-demand SIB1 request procedure with the candidate NES cell 126B when the UE moves back into coverage of the candidate NES cell. As in Fig. 5A, the NES cell 126B supports on- demand SIB1. The RAN 105 includes the NES cell 126B and a second cell 126A. The cell 126 A may be operating in non-NES or NES mode.

[0104] Operations 401-3, 490-1, and 532 are the same as those in Fig. 5A. However, in contrast to Fig. 5A, the UE 102 releases 531 the UL WUS configuration associated with the cell 126B in response to detecting the out of coverage condition. When released, the UE 102 is no longer able to use the UL WUS configuration to access the cell 126B.

[0105] The UE 102 subsequently attempts to access 490-2 the cell 126B and determines whether to perform an on-demand SIB1 request procedure with the cell 126B when the UE 102 moves back into coverage of the cell 126B. Because the UL WUS configuration has been released, the UE 102 does not have a UL WUS configuration for requesting transmission of on-demand SIB1 from the cell 126B. The UE 102 performs a cell search25G114380 2870WOand / or select another cell, such as cell 126A. In some implementations, the UE 102 does so if the cell 126B is not broadcasting the on-demand SIB1.

[0106] FIG. 5C is a signaling diagram 500C illustrating an example of a UE 102 releasing the UL WUS configuration for a candidate NES cell 126B when the UE 102 moves out of the coverage of the candidate NES cell 126B and the UE 102 refraining from performing an on- demand SIB1 request procedure with the candidate NES cell 126B when the UE 102 moves back into coverage of the candidate NES cell 126B.

[0107] Fig. 5C is similar to Fig. 5B, except that after releasing the UL WUS configuration associated with the cell 126B, the UE 102 refrains 433 from measuring SSB or PBCH of the cell 126B so selection or reselection of cell 126B will not occur (e.g.. carrier frequency barring). Alternatively, the UE 102 measures the SSB or PBCH but does not select / reselect (e.g., cell barring) the cell 126B.

[0108] Next, several example methods, which can be implemented in a UE (e.g., the UE 102 in Figs. 1A, 2, and 3-5C) or a network (e.g., the RAN 105, the base station 104, or the base station 106 in Figs. 1A, IB. 2, and 3-5C), are discussed next with reference to Figs. 6A- 11C. Descriptions described for Figs. 3-5C can apply to Figs. 6A-11C.

[0109] FIG. 6A is a flow diagram of an example method 600A that can be implemented by a UE for requesting a SIB1 from a candidate NES cell that supports on-demand SIB1 transmission based on a UL WUS configuration or the UE selecting another cell when the UL WUS configuration is not available. The method 600 A may correspond to the signaling diagram 300 of Fig. 3.

[0110] The method 600A begins at block 602, where the UE selects or reselects a first cell (e.g., the NES cell 126B described with respect to Figs. 3A-5C). At block 604, the UE receives a first indication and a second indication from the first cell, where the first indication indicates SIB1 is not periodically broadcast on the first cell and the second indication indicates that on-demand SIB1 is supported on the first cell. At block 608, the UE determines whether the UE has a UL WUS configuration for requesting transmission of an on-demand SIB1 from the first cell. If the UE has an UL WUS configuration for requesting on-demand SIB1 of the first cell (i.e., ‘'Yes” branch of block 608), the flow proceeds to block 610. At block 610, the UE transmits an UL WUS on the first cell to request a SIB1 based on the UL WUS configuration. At block 614. the UE receives a SIB1 from the first cell. Otherwise, if the UE does not have a UL WUS configuration for requesting transmission of an on-demand26G114380 2870WOSIB1 from the first cell (i.e., “No’' branch of block 608), the flow proceeds to block 609. At block 609, the UE may bar the first cell or may bar a carrier frequency of the first cell. At block 611, the UE performs a cell search and / or a cell selection or reselection to a second cell. In some implementations, the UE 102 finds the second cell in the cell search and selects or reselects the second cell.[OHl] FIG. 6B is a flow diagram of an example method 600B that can be implemented by a UE for requesting a SIB1 from a candidate NES cell that supports on-demand SIB1 transmission based on a UL WUS configuration or the UE selecting another cell when the NES cell does not support on-demand SIB1 transmission or when the UL WUS configuration is not available. The method 600B may correspond to the signaling diagram 300 of Fig. 3.

[0112] The example method 600B is similar to the method 600 A, except that the method 600B includes blocks 603 and 607 instead of block 604. At block 603, the UE receives a first indication from the first cell, where the first indication indicates SIB 1 is not transmitted on the first cell. At block 607. the UE determines whether the UE receives a second indication indicating that on-demand SIB 1 is supported on the first cell. If the UE receives a second indication indicating that on-demand SIB1 is supported on the first cell (i.e., “Yes” branch of block 607), the flow proceeds to block 608. Otherwise, if the UE does not receive a second indication indicating that on-demand SIB1 is supported on the first cell (i.e., “No” branch of block 607). the flow proceeds to block 609.

[0113] FIG. 7A is a flow diagram of an example method 700A that can be implemented by a UE for retaining the UL WUS configuration for a candidate NES cell when the UE accesses (e.g., selects or reselects and / or communicates with) another cell and the UE subsequently requesting a SIB1 from the candidate NES cell based on the retained UL WUS configuration. The method 700A may correspond to the signaling diagram 400A of Fig. 4A.

[0114] The method 700 A begins at block 701, where the UE receives, from a first cell or a second cell, a UL WUS configuration for requesting transmission of an on-demand SIB1 from the first cell. At block 740, the UE selects or reselects a third cell, where the UL WUS configuration is not transmitted on the third cell. At block 730A, the UE maintains the UL WUS configuration in response to selecting or reselecting the third cell. At block 702, the UE optionally selects or reselects the first cell after blocks 740 and 730A. The flow optionally proceeds to blocks 610 (transmit an UL WUS request on the first cell to request a S1B1 based27G114380 2870WOon the UL WUS configuration; see FIG. 6A) and 614 (receive a SIB1 from the first cell; see Fig. 6A).

[0115] In some implementations, the third cell supports the NES mode as described above. In such cases, the third cell may be operated in the NES mode or in a non-NES mode. In other implementations, the third cell is a legacy cell not supporting the NES mode.

[0116] In some implementations, the third cell and the first cell are NR cells. In other implementations, the third cell and the first cell are a LTE cell and a NR cell respectively. In yet other implementations, the third cell and the first cell are 6G cells. In yet other implementations, one of the third cell and the first cell is a 6G cell and the other is a NR cell.

[0117] In some implementations, the UE receives one or more additional configurations, e.g., in a SIB or a RRC message, from the first cell or the second cell. The UE releases the one or more additional configurations in response to selecting or reselecting the third cell.

[0118] FIG. 7B is a flow diagram of an example method 700B that can be implemented by a UE for releasing the UL WUS configuration for a candidate NES cell when the UE accesses another cell and the UE subsequently attempting to perform an on-demand SIB1 request procedure with the candidate NES cell or the UE refraining from performing an on-demand SIB1 request procedure with the candidate NES cell. The method 700B may correspond to the signaling diagram 400B of Fig. 4B.

[0119] The example method 700B is similar to the method 700 A, except that the method 700B includes blocks 731B, 702, 609, 61 1 and 733 instead of blocks 730A, 702, 610 and 614. At block 731B, the UE releases the UL WUS configuration in response to selecting or reselecting the third cell. The flow then proceeds to blocks 702 (select or reselect the first cell; see Fig. 7A), 609 (optionally bar the first cell or bar a carrier frequency of the first cell; see Fig. 6B) and 611 (perform a cell search and / or a cell selection or reselection of a second cell; see Fig. 6B) and / or optional block 733. At block 733, the UE refrains from measuring or selecting or reselecting the first cell. The UE at block 733 does so because the UE releases the UL WUS configuration.

[0120] FIG. 7C is a flow diagram of an example method 700C that can be implemented by a UE for retaining or releasing the UL WUS configuration for a candidate NES cell depending on whether the candidate NES cell and a second cell use the same radio access technology (RAT) when the UE accesses the second cell. The method 700C may be a variant of the methods 700 A and 700B.28G114380 2870WO

[0121] The example method 700C is similar to the methods 700A and 700B, except that the method 700C includes block 742. At block 742. the UE determines whether the third cell and the first cell utilize the same radio access technology (RAT). If the third cell and the first cell utilize the same RAT (i.e., “Yes” branch of block 742), the flow proceeds to block 730A and optionally proceeds to blocks 702, 610 and / or 614 (see Fig. 7A). Otherwise, if the third cell and the first cell utilize different RATs (i.e., “No” branch of block 742), the flow proceeds to block 73 IB. The flow may then proceed to blocks 702, 609 (optional), and 61 1 and / or optional block 733 (see Fig. 7B).

[0122] FIG. 7D is a flow diagram of an example method 700D that can be implemented by a UE for retaining or releasing the UL WUS configuration for a candidate NES cell depending on whether the candidate NES cell and a second cell have the same configured area ID when the UE accesses the second cell. The method 700D may be another variant of the methods 700 A and 700B.

[0123] The example method 700D is similar to the methods 700A. 700B and 700C, except that the method 700D includes block 743 instead of block 742. At block 743, the UE determines whether the third cell and the first cell are configured with the same area (ID). If the third cell and the first cell are configured with the same area (ID) (i.e., “Yes” branch of block 743). the flow proceeds to block 730A (see Fig. 7C). Otherwise, if the third cell and the first cell are not configured with the same area (ID) (e.g., the third cell and the first cell are configured with different areas or area IDs), the flow proceeds to block 731B (see Fig. 7C).

[0124] In some implementations, the UE receives an area configuration associated with the UL WUS configuration from the first cell or the second cell. In some implementations, the area configuration includes a first area ID. The UE may receive a second area ID from the third cell. The UE determines whether the first area ID and the second area ID are the identical or not. If the first area ID (value) and the second area ID (value) are the same, the flow proceed to block 730A. Otherw ise, if the first area ID (value) and the second area ID (value) are different, the flow proceed to block 73 IB. In other implementations, the area configuration includes a list of cell IDs. If a cell ID of the third cell is included in the list of cell IDs, the flow proceeds to block 730A. Otherwise, if the cell ID of the third cell is not included in the list of cell IDs, the flow proceeds to block 73 IB.

[0125] In some implementations, the area(s) is / are Public Land Mobile Network(s) (PLMN(s)). In some implementations, the area(s) is / are tracking area(s). In yet other29G114380 2870WOimplementations, the area(s) is / are RAN notification area(s). In yet other implementations, the area(s) includes a list of cells. In some implementations, the area ID(s) is / are Public Land Mobile Network (PLMN) ID(s). In other implementations, the area ID(s) is / are tracking area ID(s). In yet other implementations, the area ID(s) is / are RAN notification area ID(s).

[0126] FIG. 7E is a flow diagram of an example method 700E that can be implemented by a UE for retaining or releasing the UL WUS configuration for a candidate NES cell depending on whether the UE receives from a second cell a message to release the UL WUS configuration when the UE accesses the second cell. The method 700E may be yet another variant of the methods 700A and 700B.

[0127] The example method 700E is similar to the methods 700A, 700B, 700C and 700D. except that the method 700E includes blocks 744, 746, 730E and 73 IE instead of blocks 743, 730A and 731B. At block 744, the UE receives a message (e.g., a SIB or a RRC release message) from the third cell. At block 746, the UE determines whether the message indicates releasing the UL WUS configuration. If the message does not indicate releasing the UL WUS configuration (i.e., '‘No” branch of block 746), the flow proceeds to block 730E. At block 730E, the UE maintains the UL WUS configuration in response to an absence of an explicit instruction to release the UL WUS configuration. The flow optionally proceeds to blocks 702, 610 and 614 (see Figs. 7A, 7C, or 7D) from block 730E. Otherwise, if the message indicates releasing the UL WUS configuration (i.e.. “Yes” branch of block 746). the flow proceeds to block 73 IE. At block 731E, the UE releases the UL WUS configuration in response to the explicit instruction to release the UL WUS configuration. The flow proceeds to blocks 702, 609 (optional) and 611 and / or optional block 733 (see Fig. 7B, 7C, or 7D) from block 73 IE.

[0128] FIG. 8A is a flow diagram of an example method 800A that can be implemented by a UE for retaining the UL WUS configuration for a candidate NES cell when the candidate NES cell is out of coverage and the UE subsequently requesting a SIB 1 from the candidate NES cell based on the retained UL WUS configuration when the candidate NES cell is back in coverage. The method 800A may correspond to the signaling diagram 500A of Fig. 5 A.

[0129] The method 800A is similar to the method 700A, except that the method 800A includes blocks 832 and 830 instead of blocks 740 and 730A. At block 832, the UE detects out of coverage. At block 830. the UE maintains the UL WUS configuration in response to detecting out of coverage. At block 840, the UE determines if it is back in coverage. If the30G114380 2870WOUE is still out of coverage, the UE keeps maintaining the UL WUS configuration. If the UE is back in coverage, the flow then optionally proceeds to block 702 (see Fig. 7A).

[0130] FIG. 8B is a flow diagram of an example method 800B that can be implemented by a UE for releasing the UL WUS configuration for a candidate NES cell when the candidate NES cell is out of coverage and the UE subsequently attempting to perform an on-demand SIB1 request procedure with the candidate NES cell when the candidate NES cell is back in coverage or the UE refraining from performing an on-demand SIB1 request procedure with the candidate NES cell. The method 800B may correspond to the signaling diagrams 500B and 500C of Fig. 5B and Fig. 5C.

[0131] The method 800B is similar to the methods 700B and 800 A, except that the method 800B includes block 831 instead of blocks 740 and 73 IB. At block 832, the UE detects out of coverage. At block 831, the UE releases the UL WUS configuration in response to detecting out of coverage. At block 840, the UE determines if it is back in coverage. If the UE is back in coverage, the flow then proceeds to blocks 702, 609 (optional) and 611 and / or optional block 733 (see Fig. 7B).

[0132] In one aspect, a UE stores a time-limited on-demand SIB1 for each NES cell. The time-limited on-demand SIB1 for a NES cell has a validity period to enable the UE to access the NES cell without having to request transmission of a new SIB1 when the UE moves back and forth between a NES cell and another cell. An example method for determining validity of the on-demand SIB1 is described as FIG. 9.

[0133] FIG. 9 is a flow diagram of an example method 900 that can be implemented by a UE for using a validity timer to measure the validity period of a first on-demand SIB1 from a candidate NES cell and for performing an on-demand SIB1 request procedure with the candidate NES cell to request a second on-demand SIB1 when the first on-demand SIB1 is no longer valid.

[0134] The method 900 begins at block 701 as described with respect to Fig. 7A. At block 910, the UE transmits a UL WUS to the first cell to request transmission of an on-demand SIB1, based on the UL WUS configuration. At block 914, the UE receives a SIB1 from the first cell after (e g., in response to) the UL WUS. At block 934, the UE starts a validity timer for determining validity of the SIB1. At block 936, the UE detects expiry of the validity timer. At block 938, the UE designates the SIB1 as invalid in response to detecting expiry of the validity timer. In response to the UE detecting expiry of the validity timer or designating31G114380 2870WOthe SIB1 as invalid, the flow optionally proceeds to block 910 so that the UE can retransmit the UL WUS to the first cell to request transmission of an on-demand SIB1.

[0135] In some implementations, while the validity timer is running, the UE maintains the SIB1 and the validity timer running regardless of whether the UE stays in the first cell or moves to a fourth cell. The fourth cell may be the second cell, the third cell, or an additional cell which is none of the first, second, or third cell. In other implementations, the UE releasees the UL WUS configuration as described in the previous figures. In response to releasing the UL WUS configuration, the UE invalidates or releases the SIB1 and thus stops the validity timer.

[0136] In some implementations, the UE receives and maintains a list of UL WUS configurations, where each UL WUS configuration is applicable for requesting an on-demand SIB 1 transmission from a corresponding one or more NES cells. The UE may maintain a corresponding validity timer for each UL WUS configuration as described above.

[0137] FIG. 10 is a flow diagram of an example method 1000 that can be implemented by a network entity of a candidate NES cell for determining that a validity period for a first on- demand SIB1 from the candidate NES cell expires and for transmitting a second on-demand SIB1 in response to the invalidity of the first on-demand SIB1. In some implementations, the BS-side validity timer and the UE-side validity timer have different values.

[0138] The method 1000 begins at block 1001, where the network entity transmits, via a first cell or a second cell, a UL WUS configuration for requesting transmission of an on- demand SIB1 from the first cell. At block 1010, the network entity receives a UL WUS via the first cell to request transmission of a SIB1 from the first cell, based on the UL WUS configuration. At block 1014, the network entity transmits a first SIB1 via the first cell in response to the UL WUS. Upon transmitting the first SIB1, at block 1034, the network entity starts a BS-side validity' timer for determining the validity of the SIB1. At block 1036, the network entity detects that the validity period for the first SIB1 passes when the BS-side validity’ timer expires. At block 1052, the network entity transmits a second SIB1 via the first cell in response to detecting that the validity period passes. The network entity' may restart the BS-side validity timer in response to transmitting the second SIB1. In some implementations, the first SIB1 includes information for the UE to determine the validity period. In some implementations, the first SIB1 and the second SIB1 are the same. In other implementations, the first SIB1 and the second SIB1 are different. In some implementations,32G114380 2870WOthe BS-side validity timer for the SIB1 runs in parallel with the validity timer for the SIB1 at the UE side.

[0139] In one aspect, a UE maintains a list of UL WUS configurations, where each UL WUS configuration is applicable for requesting an on-demand SIB 1 transmission from a corresponding one or more NES cells. In one aspect, a UE receives more than one UL WUS configuration associated with the corresponding one or more NES cell from one or more cells. The UE manages the UL WUS configurations associated with multiple NES cells or manages updates to the UL WUS configuration associated with a NES cell as discussed in Figs. 11A-11C.

[0140] FIG. 11 A is a flow diagram of an example method 1100A that can be implemented by a UE for replacing a first UL WUS configuration by a second UL WUS configuration when both UL WUS configurations are for the same candidate NES cell or for retaining both UL WUS configurations when the first UL WUS configurations and the second UL WUS configuration are for different candidate NES cells. The operation 430 of Fig. 4A, operation 431 of Figs. 4B / 4C, operation 530 of Fig. 5A, or operation 531 of Fig. 5B / 5C may include the method 1100 A.

[0141] The method 1100A begins at block 1101, where the UE receives, from a first cell or a second cell, a first UL WUS configuration for requesting an on-demand SIB1 of a first cell. At block 740, the UE selects or reselects a third cell. At block 1144, the UE receives, from a third cell, a second UL WUS configuration for requesting an on-demand SIB1. At block 1 154, the UE determines whether the second UL WUS configuration is configured for requesting an on-demand SIB1 of the first cell. If the second UL WUS configuration is configured for requesting an on-demand SIB1 of the first cell (i.e., ‘‘Yes’' branch of block 1154), the flow proceeds to block 1156. At block 1156, the UE replaces the first UL WUS configuration with the second UL WUS configuration. Otherwise, if the second UL WUS configuration is configured for requesting an on-demand SIB1 of a different cell (i.e., “No” branch of block 1154), the flow proceeds to block 1130. At block 1130, the UE maintains the first UL WUS configuration. At block 1158, the UE stores the second UL WUS configuration. The UE thus stores a separate UL WUS configuration for each NES cell.

[0142] FIG. 1 IB is a flow diagram of an example method 1100B that can be implemented by a UE for modifying a first UL WUS configuration based on a second UL WUS configuration when both UL WUS configurations are for the same candidate NES cell or for33G114380 2870WOretaining both UL WUS configurations when the first UL WUS configurations and the second UL WUS configuration are for different candidate NES cells. The operation 430 of Fig. 4A, operation 431 of Figs. 4B / 4C, operation 530 of Fig. 5A, or operation 531 of Fig. 5B / 5C may include the method 1100B.

[0143] The method 1 100B similar to the method 1 100 A, except that the method 1 100B includes block 1157 instead of block 1156. At block 1157, the UE modifies (e.g., augments) the first UL WUS configuration based on the second UL WUS configuration. Similar to the method 1100 A, the method 1100B stores a separate UL WUS configuration for each NES cell.

[0144] FIG. 11C is a flow diagram of an example method 1100C that can be implemented by a UE for modifying a first UL WUS configuration based on a second UL WUS configuration when both UL WUS configurations are for the same candidate NES cell or for changing a list of UL WUS configurations when the first UL WUS configurations and the second UL WUS configuration are for different candidate NES cells. The operation 430 of Fig. 4A, operation 431 of Figs. 4B / 4C, operation 530 of Fig. 5A, or operation 531 of Fig. 5B / 5C may include the method 1100C.

[0145] The method 1100C similar to the method 1100B, except that the method 1100C includes block 1131 instead of block 1130. At block 1131, the UE releases the first UL WUS configuration. In some embodiments, the UE stores a list of up to N UL WUS configurations associated with their associated NES cells. When the UE receives an (N+l)thUL WUS configuration, the UE decides which one of the N stored UL WUS configurations to release at block 1131. In some embodiments, the UE releases the oldest stored UL WUS configuration. In some embodiments, the UE releases the UL WUS configuration for the geographically furthest cell. In some embodiments, the UE releases the least used UL WUS configuration. In some embodiments, the UE releases the UL WUS configuration associated with an area ID different from an area ID associated with the (N+l)* UL WUS configuration.

[0146] In one aspect, a UE invalidates an UL WUS configuration based on an event. For example, as discussed, a UE releases an UL WUS configuration associated with an NES cell during cell selection / reselection, when the UE is out of coverage of an NES cell, when the UE receives an explicit instruction from the network entity to release the UL WUS configuration, when the number of UL WUS configurations reaches a storage limit, etc. In some embodiments, an UL WUS configuration for an NES cell is time-limited, similar to the34G114380 2870WOtime-limited SIB1 for an NES cell. For example, an UL WUS configuration may have a validity period. In some implementations, an UE invalidates an UL WUS configuration based on the expiration of the validity period.

[0147] FIG. 12 is a flow diagram of an example method 1200 that can be implemented by a UE for detecting an event for invalidating a UL WUS configuration and for invalidating the UL WUS configuration in response to detecting the event.

[0148] The method 1200 begins at block 701 as described with respect to Fig. 7A. At block 1260, the UE detects an event for invalidating the UL WUS configuration. At block 1262, the UE invalidates the UL WUS configuration in response to detecting the event. In some implementations, the UE releases the UL WUS configuration in response to invalidating the UL WUS configuration or detecting the event. In some implementations, the event is an ex pin- of a timer (e.g., validity timer described above) which the UE starts upon receiving the UL WUS configuration. In one implementation, the UE receive, from the first or second cell, a timer value of the timer in a SIB including the UL WUS configuration. In another implementation, the UL WUS configuration includes the timer value. In yet another implementation, the UE is preconfigured with the timer value. In other implementations, the event is a cell selection or a cell reselection. In yet other implementations, the event is a state transition (e.g.. from an idle state or inactive state to a connected).

[0149] FIG. 13 is a flow diagram of an example method 1300 that can be implemented by a network entity of a candidate NES cell for configuring a UE to detect an event to invalidate a UL WUS configuration for the candidate NES cell.

[0150] The method 1300 begins at block 1001 as described with respect to Fig. 10. At block 1364, the network configures the UE to detect an event to invalidate the UL WUS configuration. Examples and implementations described for FIGs. 3-11 can apply to FIGs. 12 and 13.

[0151] FIGs. 14-16 show further methods for implementing one or more aspects of FIGs. 3-13. In particular, FIG. 14 shows an implementation by the UE 102 of the one or more aspects of FIGs. 3-13. FIG. 15 shows an implementation by a network entity 104 of a candidate cell of the one or more aspects of FIGs. 3-13. FIG. 16 shows an implementation by a network entity 104 of a first cell, which is different from the candidate cell, of the one or more aspects of FIGs. 3-13.35G114380 2870WO

[0152] FIG. 14 is a flowchart of a method 1400 of wireless communication at a UE 102 for requesting a SIB1 from a candidate NES cell that supports on-demand SIB1 transmission based on a UL WUS configuration for the candidate NES cell according to an embodiment.

[0153] The UE 102 optionally receives 1401. from a network entity 104. one or more UL WUS configurations. For example, referring to FIG. 3, the UE 102 receives 401 -1 , from the RAN 105, an UL WUS configuration (e.g., UL WUS configuration 1) via cell 126B. The UL WUS configuration includes (e.g., indicates) UL resources (e g., PRACH resources) for requesting on-demand SIB1 from cell 126B.

[0154] The UE 102 receives 1404 , from a candidate cell supporting on-demand SIB, an indication that SIB transmission is deactivated for the candidate cell. For example, referring to FIG. 3, the UE 102 receives 304 a MIB from the cell 126B. The MIB may include a first indication (e.g., set to a first value or an invalid value) indicating that SIB1 is not periodically broadcast. In some implementations, the first indication is a S SB subcarrier offset configuration (e.g.. ssb-SubcarrierOffsef) set to a first value or an invalid value. The MIB may include a second indication indicating support of on-demand SIB1.

[0155] The UE 102 transmits 1410. to the candidate cell based on an UL WUS configuration list with a first UL WUS configuration for the candidate cell, a WUS on uplink resources to request an on-demand SIB transmission from the candidate cell. For example, referring to FIG. 3. if the UE 102 has a UL WUS configuration used to request transmission of an on-demand SIB1 from the cell 126B, the UE 102 transmits 310, to the cell 126B. a UL WUS to request transmission of an on-demand SIB1. In some embodiments, the UL WUS is a random access preamble.

[0156] The UE 102 receives 1414 the on-demand SIB from the candidate cell. For example, referring to FIG. 3, the UE 102 receives 314 the first SIB from the cell 126B. The UE 102 attempts to receive or receives 314 the first SIB1 in accordance with a PDCCH configuration (e.g.. pdcch-ConfigSIB 1).

[0157] The UE 102 optionally selects 1411 a different candidate cell to access when the WUS uplink configuration list is inapplicable to the candidate cell. For example, referring to FIG. 3, if the UE 102 does not have a UL WUS configuration for requesting transmission of on-demand SIB1 from the cell 126B, the UE 102 may bar the cell 126B or a carrier frequency of the cell 126B and / or perform 311 a cell search.36G114380 2870WO

[0158] Fig. 14 describes a method from a UE-side of a wireless communication link for requesting on-demand SIB transmission, whereas FIG. 15 and FIG. 16 describe a method from a network-side of the wireless communication link for on-demand SIB transmission.

[0159] FIG. 15 is a flowchart of a method 1500 of wireless communication at a candidate NES cell for transmitting on-demand SIB1 according to an embodiment. The method 1500 is performed by one or more network entities 104, which may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, and / or the CU 110.

[0160] The candidate NES cell optionally transmits 1501, to a UE 102, an UL WUS configuration. For example, referring to FIG. 3, the RAN 105 transmits 401-1. to the UE 102, an UL WUS configuration (e.g., UL WUS configuration 1) via cell 126B. The UL WUS configuration includes (e.g., indicates) UL resources (e g., PRACH resources) for requesting on-demand SIB1 from cell 126B.

[0161] The candidate NES cell transmits 1504 an indication that SIB transmission is deactivated for the candidate cell. For example, referring to FIG. 3, the cell 126B transmits 304 a MIB. The MIB may include a first indication (e.g., set to a first value or an invalid value) indicating that SIB1 is not periodically broadcast. In some implementations, the first indication is a SSB subcarrier offset configuration (e g., ssb-SubcarrierOffset) set to a first value or an invalid value. The MIB may include a second indication indicating support of on-demand SIB1.

[0162] The candidate NES cell receives 1510, from the UE 102, a WUS on UL resources indicated by an UL WUS configuration to request an on-demand SIB transmission from the candidate NES cell. For example, referring to FIG. 3. the cell 126B receives 310, from the UE 102, a UL WUS to request transmission of an on-demand SIB1. In some embodiments, the UL WUS is a random access preamble.

[0163] The candidate NES cell transmits 1514 the on-demand SIB. For example, referring to FIG. 3, the cell 126B transmits 314, to the UE 102, the first SIB in response to the WUS. The cell 126B may transmit 314 the first SIB1 in accordance with a PDCCH configuration (e.g.. pdcch-ConflgSIBl .

[0164] FIG. 15 describes a method of wireless communication at a candidate NES cell of a network entity for transmitting SIB on demand during a cell selection procedure by a UE, whereas FIG. 16 describes a method of wireless communication at a first cell of a network37G114380 2870WOentity to enable on-demand SIB transmission from a different cell of the network entity during a cell re-selection procedure by a UE.

[0165] FIG. 16 is a flowchart of a method 1600 of wireless communication at a first cell for transmitting a UL WUS configuration for requesting on-demand SIB1 from a different candidate NES cell that supports on-demand SIB1 transmission according to an embodiment. In some implementations, the UE 102 is camped on the first cell when the UE 102 is in the idle or inactive mode. The UE 102 requests on-demand SIB transmission from the candidate NES cell to re-select the candidate NES cell. The method 1600 is performed by one or more network entities 104, which may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, and / or the CU 110.

[0166] The first cell transmits 1 01, to a UE 102, an UL WUS configuration indicating UL resources for requesting an on-demand SIB transmission from a candidate cell that supports on-demand SIB transmission. For example, referring to FIG. 3, the RAN 105 transmits 401-2 UL WUS configuration associated with cell 126B (e.g., UL WUS configuration 2) to the UE 102 via non-NES cell 124. In some implementations, the RAN 105 transmits 401-3 the UL WUS configuration associated with cell 126B (e.g., UL WUS configuration 3) to the UE 102 via cell 126A. For example, the RAN 105 transmits (e.g., broadcasts) a SIB including the UL WUS configuration on the cell 124 or 126 A while the UE 102 camps on the cell 124 or 126 A.

[0167] The first cell optionally transmits 1624 periodic SIB. For example, referring to FIG. 3, the cell 124 transmits 324 the second SIB1. The cell 124 may transmit 324 the second SIB1 in accordance with a PDCCH configuration (e.g., pdcch-ConfigSIBl).

[0168] The first cell optionally receives 1 28, from the UE, a request to reestablish connection based on the periodic SIB. For example, referring to FIG. 3, the cell 124 receives 328 a request from the UE 102 to access the cell 124 in accordance with configuration parameters in the second SIB1.

[0169] A UE apparatus 1702, as described in FIG. 17, may perform the method of flowchart 1400. The one or more network entities 104, as described in FIG. 18, may perform the method of flow charts 1500-1600.

[0170] FIG. 17 is a diagram 1700 illustrating a hardware implementation for an example UE apparatus 1702. The UE apparatus 1702 may be the UE 102, a component of the UE 102, or may implement UE functionality'. The UE apparatus 1702 may include an application38G114380 2870WOprocessor 1706, which may have on-chip memory 1706’. In examples, the application processor 1706 may be coupled to a secure digital (SD) card 1708 and / or a display 1710. The application processor 1706 may also be coupled to a sensor(s) module 1712, a power supply 1714, an additional module of memory 1716, a camera 1718, and / or other related components. For example, the sensor(s) module 1712 may control a barometric pressure sensor / altimeter, a motion sensor such as an inertial management unit (IMU), a gyroscope. accelerometer(s), a light detection and ranging (LIDAR) device, a radio-assisted detection and ranging (RADAR) device, a sound navigation and ranging (SONAR) device, a magnetometer, an audio device, and / or other technologies used for positioning.

[0171] The UE apparatus 1702 may further include a wireless baseband processor 1726, which may be referred to as a modem. The wireless baseband processor 1726 may have on- chip memory 1726'. Along with, and similar to. the application processor 1706, the wireless baseband processor 1726 may also be coupled to the sensor(s) module 1712, the power supply 1714, the additional module of memory 1716, the camera 1718, and / or other related components. The wireless baseband processor 1726 may be additionally coupled to one or more subscriber identity module (SIM) card(s) 1720 and / or one or more transceivers 1730 (e.g., wireless RF transceivers).

[0172] Within the one or more transceivers 1730. the UE apparatus 1702 may include a Bluetooth module 1732, a WLAN module 1734, a satellite positioning system (SPS) module 1736 (e.g., global navigation satellite system (GNSS) module), and / or a cellular module 1738. The Bluetooth module 1732, the WLAN module 1734, the SPS module 1736, and the cellular module 1738 may each include an on-chip transceiver (TRX), or in some cases, just a transmitter (TX) or just a receiver (RX). The Bluetooth module 1732, the WLAN module 1734, the SPS module 1736, and the cellular module 1738 may each include dedicated antennas and / or utilize antennas 1740 for communication with one or more other nodes. For example, the UE apparatus 1702 can communicate through the transceiver(s) 1730 via the antennas 1740 with another UE (e.g., sidelink communication) and / or with a network entity 104 (e.g., uphnk / downlink communication), where the network entity 104 may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, or the CU 110.

[0173] The wireless baseband processor 1726 and the application processor 1706 may each include a computer-readable medium / memory 1726', 1706', respectively. The additional module of memory 1716 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1726', 1706', 1716 may be non- transitory. The39G114380 2870WOwireless baseband processor 1726 and the application processor 1706 may each be responsible for general processing, including execution of software stored on the computer- readable medium I memory 1726', 1706', 1716. The software, when executed by the wireless baseband processor 1726 / application processor 1706, causes the wireless baseband processor 1726 / application processor 1706 to perform the various functions described herein. The computer-readable medium / memory’ may also be used for storing data that is manipulated by the wireless baseband processor 1726 / application processor 1706 when executing the software. The wireless baseband processor 1726 / application processor 1706 may be a component of the UE 102. The UE apparatus 1702 may be a processor chip (e.g., modem and / or application) and include just the wireless baseband processor 1726 and / or the application processor 1706. In other examples, the UE apparatus 1702 may be the entire UE 102 and include the additional modules of the apparatus 1702.

[0174] As discussed in FIG. 1 A and implemented with respect to FIG. 14, the on-demand SIB requester component 140 is configured to: receive, from a candidate cell supporting on- demand SIB, an indication that periodic SIB transmission is deactivated for the candidate cell; transmit, to the candidate cell, a WUS on uplink resources to request an on-demand SIB transmission from the candidate cell when the UE has an available UL WUS configuration for that candidate cell. The UL WUS configuration indicates the uplink resources for the WUS. When the UE does not have a UL WUS configuration for that candidate cell, the on- demand SIB requester component 140 is configured selects a different candidate cell to access. The on-demand SIB requester component 140 may be within the wireless baseband processor 1726 (e.g.. at 140). The on-demand SIB requester component 140 may be one or more hardware components specifically configured to cany7out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by the one or more processors, or a combination thereof.

[0175] FIG. 18 is a diagram 1800 illustrating a hardware implementation for one or more example network entities. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include, or may correspond to, at least one of the RU 106, the DU, 108, or the CU 110. The CU 110 may include a CU processor 1846, which may have on-chip memory 1846'. In some aspects, the CU 110 may further include an additional module of memory 1856 and / or a communications interface 1848, both of which may be coupled to the40G114380 2870WOCU processor 1846. The CU 110 can communicate with the DU 108 through a midhaul link 162, such as an Fl interface between the communications interface 1848 of the CU 110 and a communications interface 1828 of the DU 108.

[0176] The DU 108 may include a DU processor 1826. which may have on-chip memory 1826'. In some aspects, the DU 108 may further include an additional module of memory 1836 and / or the communications interface 1828, both of which may be coupled to the DU processor 1826. The DU 108 can communicate with the RU 106 through a fronthaul link 160 between the communications interface 1828 of the DU 108 and a communications interface 1808 of the RU 106.

[0177] The RU 106 may include an RU processor 1806, which may have on-chip memory 1806'. In some aspects, the RU 106 may further include an additional module of memory 1816, the communications interface 1808, and one or more transceivers 1830, all of which may be coupled to the RU processor 1806. The RU 106 may further include antennas 1840, which may be coupled to the one or more transceivers 1830, such that the RU 106 can communicate through the one or more transceivers 1830 via the antennas 1840 with the UE 102.

[0178] The on-chip memory 1806', 1826', 1846' and the additional modules of memory 1816, 1836, 1856 may each be considered a computer-readable medium / memory. Each computer-readable medium I memory may be non-transitory. Each of the processors 1806, 1826, 1846 is responsible for general processing, including execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor(s) 1806, 1826, 1846 causes the processor(s) 1806, 1826, 1846 to perform the various functions described herein. The computer-readable medium / memory may also be used for storing data that is manipulated by the processor(s) 1806, 1826. 1846 when executing the software. In examples, the on-demand SIB transmission component 150 and / or the candidate cell on-demand SIB assistor component 155 may sit at any of the one or more network entities 104, such as at the CU 110; both the CU 110 and the DU 108; each of the CU 110, the DU 108, and the RU 106; the DU 108; both the DU 108 and the RU 106; or the RU 106.

[0179] As discussed in FIG. 1 A and implemented with respect to FIG. 15, the on-demand SIB transmission component 150 is configured to: transmit an indication that periodic SIB transmission is deactivated for the candidate cell of the base station; receive, from a UE, a41G114380 2870WOWUS on uplink resources indicated by an UL WUS configuration to request an on-demand SIB transmission from the candidate cell; and transmit the on-demand SIB in response to the WUS. As discussed in FIG. 1 A and implemented with respect to FIG. 15, the candidate cell on-demand SIB assistor component 155 is configured to: transmit, to a UE, an UL WUS configuration indicating UL resources for requesting an on-demand SIB transmission from the candidate cell. The on-demand SIB transmission component 150 and / or the candidate cell on-demand SIB assistor component 155 may be within one or more processors of the one or more network entities 104, such as the RU processor 1806 (e.g., at 150a, 155a), and / or the DU processor 1826 (e.g., at 150b, 155b). The on-demand SIB transmission component 150 and / or the candidate cell on-demand SIB assistor component 155 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors 1806 and 1826 configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by the one or more processors 1806 and 1826, or a combination thereof.

[0180] Generally speaking, description for one of the above figures can apply to another of the above figures. Examples, implementations and methods described above can be combined, if there is no conflict. An event or block described above can be optional or omitted. For example, an event or block with dashed lines in the figures can be optional.The description described from the perspective of the receiving node also applies to the sending node. For example, a description that a receiving node (e g., DU) receives a message from a sending node (e.g., CU) may be replaced by the sending node sending a message to the receiving node. Similarly, a description that a receiving node (e.g.. CU) receives a message from a sending node (e.g., DU) may be replaced by the sending node sending a message to the receiving node.

[0181] In some implementations, “message” is used and can be replaced by “information element (IE)”, and vice versa. In some implementations, “IE” is used and can be replaced by “field”, and vice versa. In some implementations, “configuration” can be replaced by “configurations” or “configuration parameters”, and vice versa. In some implementations, the “on-demand SIB1” can be replaced by “SIB1”. In some implementations, the “UL configuration” can be replaced by “UL WUS configuration” by “RACH configuration for SIB1 request” or “SIB1 request configuration”. In some implementations, the “UL WUS” can be replaced by “on-demand SIB1 request”. In some implementations, the “indication” can be replaced by “indicator”.42G114380 2870WO

[0182] The specific order or hierarchy of blocks in the processes and flowcharts disclosed herein is an illustration of example approaches. Hence, the specific order or hierarchy of blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. Dashed lines may indicate optional elements of the diagrams. The accompanying method claims present elements of the various blocks in an example order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0183] The detailed description set forth herein describes various configurations in connection with the drawings and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough explanation of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0184] Aspects of wireless communication systems, such as telecommunication systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0185] An element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems-on-chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software, which may be referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software shall be construed broadly to mean instructions, instruction sets, code, code43G114380 2870WOsegments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0186] If the functionality described herein is implemented in software, the functions may be stored on, or encoded as, one or more instructions or code on a computer-readable medium, such as a non -Iran si lory computer-readable storage medium. Computer-readable media includes computer storage media and can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer. Storage media may be any available media that can be accessed by a computer.

[0187] Aspects, implementations, and / or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (Al)-enabled devices, machine learning (ML)-enabled devices, etc. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques described herein.

[0188] Devices incorporating the aspects and features described herein may also include additional components and features for the implementation and practice of the claimed and described aspects and features. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes, such as hardware components, antennas, RF-chains, power amplifiers, modulators, buffers, processor(s), interleavers, adders / summers, etc. Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of varying configurations.44G114380 2870WO

[0189] The description herein is provided to enable a person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be interpreted in view of the full scope of the present disclosure consistent with the language of the claims.

[0190] Reference to an element in the singular does not mean “one and only one” unless specifically stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The terms “may", “might”, and “can”, as used in this disclosure, often carry certain connotations. For example, “may” refers to a permissible feature that may or may not occur, “might” refers to a feature that probably occurs, and “can” refers to a capability (e.g., capable of). The phrase “For example” often carries a similar connotation to “may” and, therefore, “may” is sometimes excluded from sentences that include “for example” or other similar phrases.

[0191] Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B. or C” or “one or more of A, B. or C” include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiples of A, multiples of B, and / or multiples of C, or may include A only, B only, or C only. Sets should be interpreted as a set of elements where the elements number one or more. Terms or articles such as “a”, “an”, and / or “the” may refer to one of an item, feature, element, etc., that the term or article precedes, or may refer to more than one of said item, feature, element, etc. that the term or article precedes. For example, the recitation “a widget” does not preclude reference to multiples of said widget, as “multiple widgets” necessarily includes “a widget”. Hence, the recitation “a widget” may be interpreted as “at least one widget” or, similarly, interpreted as “one or more widgets”.

[0192] Unless otherwise specifically indicated, ordinal terms such as “first” and “second” do not necessarily imply an order in time, sequence, numerical value, etc., but are used to distinguish between different instances of a term or phrase that follows each ordinal term.45G114380 2870WO

[0193] Reference numbers, as used in the specification and figures, are sometimes cross- referenced among drawings to denote same or similar features. A feature that is exactly the same in multiple drawings may be labeled with the same reference number in the multiple drawings. A feature that is similar among the multiple drawings, but not exactly the same, may be labeled with reference numbers that have different leading numbers but have one or more of the same trailing numbers (e.g., 206, 306. 406, etc., may refer to similar features in the drawings). Hence, like numbers may refer to like actions.

[0194] Structural and functional equivalents to elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. The words “module,'’ “mechanism,’" “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be constmed as a means plus function unless the element is expressly recited using the phrase “means for.” As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A”, where “A” may be information, a condition, a factor, or the like, shall be construed as “based at least on A” unless specifically recited differently.

[0195] The following examples are illustrative only and may be combined with other examples or teachings described herein, without limitation.

[0196] Example 1 is a method of wireless communication at a UE comprising: receiving, from a candidate cell supporting on-demand SIB transmission, an indication that periodic SIB transmission is deactivated for the candidate cell; transmitting, to the candidate cell based on an UL WUS configuration list with a first UL WUS configuration for the candidate cell, a WUS on uplink resources to request an on-demand SIB transmission from the candidate cell; and based on the UL WUS configuration list being inapplicable to the candidate cell: barring access, by the UE, to the candidate cell, and selecting a different candidate cell to access.

[0197] Example 2 may be combined with Example 1, further comprising after the transmitting the WUS: receiving the on-demand SIB transmission from the candidate cell.

[0198] Example 3 may be combined with any of Examples 1-2, further comprising prior to the transmitting: receiving, from aNE of the candidate cell, the different candidate cell, or a serving cell of the UE, at least one UL WUS configuration for the UL WUS configuration list.46G114380 2870WO

[0199] Example 4 may be combined with Example 3, further comprising: detecting an event for invalidating the at least one UL WUS configuration; and invaliding the at least one UL WUS configuration in response to the detecting the event.

[0200] Example 5 may be combined with Example 3, wherein the receiving the at least one UL WUS configuration comprises: receiving, from the NE, the first UL WUS configuration indicating the uplink resources for requesting the on-demand SIB transmission from the candidate cell; and receiving, from the NE, a second UL WUS configuration indicating second uplink resources for requesting a second on-demand SIB transmission from the candidate cell or third uplink resources for requesting a third on-demand SIB transmission from a second candidate cell supporting on-demand SIB transmission.

[0201] Example 6 may be combined with Example 5, further comprising: determining that the second UL WUS configuration indicates the second uplink resources for requesting the second on-demand SIB transmission from the candidate cell; and replacing, in the UL WUS configuration list, the first UL WUS configuration with the second uplink WUS configuration.

[0202] Example 7 may be combined with Example 5, further comprising: determining that the second UL WUS configuration indicates the second uplink resources for requesting the second on-demand SIB transmission from the candidate cell; and modifying, in the UL WUS configuration list, a first indicator for the first UL WUS resources with a second indicator for the second UL WUS resources.

[0203] Example 8 may be combined with Example 5, further comprising: determining that the second UL WUS configuration indicates the third uplink resources for requesting the third on-demand SIB transmission from the second candidate cell supporting on-demand SIB transmission; retaining the first UL WUS configuration in the UL WUS configuration list; and storing the second UL WUS configuration in the UL WUS configuration list.

[0204] Example 9 may be combined with Example 5, further comprising: determining that the second UL WUS configuration indicates the third uplink resources for requesting the third on-demand SIB transmission from the second candidate cell supporting on-demand SIB; and replacing, in the UL WUS configuration list, the first UL WUS configuration with the second uplink WUS configuration.47G114380 2870WO

[0205] Example 10 may be combined with any of Examples 1-9, wherein selecting a different candidate cell to access comprises at least one of: preventing, by the UE, access to the candidate cell; or barring, by the UE, a carrier frequency of the candidate cell.

[0206] Example 11 may be combined with any of Examples 1-10, further comprising: accessing, by the UE, a second cell that periodically transmits SIB; and retaining, in the UE WUS configuration list, the first UL WUS configuration for the candidate cell.

[0207] Example 12 may be combined with Example 11, wherein the retaining the first UL WUS configuration comprises at least one of: determining that the candidate cell and the second cell use a same radio access technology (RAT); or determining that the candidate cell and the second cell are configured with a same area ID.

[0208] Example 13 may be combined with Example 11, further comprising: receiving a message from the second cell; and wherein the retaining the first UL WUS configuration comprises: determining that the message indicates a non-release of the first UL WUS configuration.

[0209] Example 14 may be combined with any of Examples 1-10, further comprising: accessing, by the UE, a second cell that periodically transmits SIB; and at least one of releasing or barring, from the UL WUS configuration list, the first UL WUS configuration for the candidate cell.

[0210] Example 15 may be combined with Example 14, wherein the releasing the first UL WUS configuration comprises at least one of: determining that the candidate cell and the second cell use a different RAT; or determining that the candidate cell and the second cell are configured with a different area ID.

[0211] Example 16 may be combined with Example 14, further comprising: receiving a message from the second cell; and wherein the releasing the first UL WUS configuration comprises: determining that the message indicates releasing of the first UL WUS configuration.

[0212] Example 17 may be combined with any of Examples 1-16, further comprising, after the transmitting the WUS: receiving the on-demand SIB transmission from the candidate cell; accessing the candidate cell; detecting the candidate cell is out of coverage; and retaining, in the UL WUS configuration list, the first UL WUS configuration for the candidate cell.48G114380 2870WO

[0213] Example 18 may be combined with any of Examples 1-16, further comprising, after the transmitting the WUS: receiving the on-demand SIB transmission from the candidate cell; accessing the candidate cell; detecting the candidate cell is out of coverage; and releasing, from the UL WUS configuration list, the first UL WUS configuration for the candidate cell.

[0214] Example 19 may be combined with Example 2, further comprising: starting a validity timer for the on-demand SIB; detecting an expiration of the validity timer; and transmitting, to the candidate cell in response to the detecting, a second WUS on the uplink resources to request a second on-demand SIB transmission.

[0215] Example 20 may be combined with Example 2, further comprising: starting a validity timer for the on-demand SIB; detecting an expiration of the validity timer; and releasing, in response to the detecting, the first UL WUS configuration for the candidate cell.

[0216] Example 21 is a method of wireless communication at a candidate cell supporting on-demand system information block, SIB, transmission, comprising: transmitting an indication that periodic SIB transmission is deactivated for the candidate cell; receiving, from a UE, a WUS on UL resources indicated by an UL WUS configuration to request an on- demand SIB transmission from the candidate cell; and transmitting the on-demand SIB.

[0217] Example 22 may be combined with Example 21, further comprising: transmitting to the UE, the UL WUS configuration.

[0218] Example 23 may be combined with Example 22, further comprising: transmitting, to the UE, a second configuration to detect an event for invalidating the UL WUS configuration.

[0219] Example 24 may be combined with any of Examples 21-23, further comprising: detecting that a validity period for the on-demand SIB expired; and transmitting, to the UE in response to the detecting, a second on-demand SIB.

[0220] Example 25 is a method of wireless communication at a first cell, which is different from a candidate cell, comprising: transmitting, to a UE, an UL WUS configuration indicating uplink resources for requesting an on-demand system information block, SIB, transmission from the candidate cell.

[0221] Example 26 is an apparatus for wireless communication for implementing a method as in any of Examples 1-25.49G114380 2870WO

[0222] Example 27 is an apparatus for wireless communication including means for implementing a method as in any of Examples 1-25.

[0223] Example 28 is a non-transitory computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to implement a method as in any of Examples 1 -25.

[0224] Example 29 is a computer program product for implementing a method as in any of Examples 1-25.50G114380 2870WO

Claims

What is claimed is:

1. A method of wireless communication at a user equipment, UE, (102), comprising: receiving (304, 604), from a candidate cell (126B) supporting on-demand system information block, SIB, transmission, an indication that periodic SIB transmission is deactivated for the candidate cell (126B); transmitting (310, 610), to the candidate cell (126B) based on an uplink wake-up signal, UL WUS, configuration list with a first UL WUS configuration for the candidate cell, a WUS on uplink resources to request an on-demand SIB transmission from the candidate cell (126B); and based on the UL WUS configuration list being inapplicable to the candidate cell: barring (309) access, by the UE, to the candidate cell (126B), and selecting (311, 611) a different candidate cell (124) to access.

2. The method of any of claim 1, further comprising prior to the transmitting: receiving (401, 701), from a network entity (NE) ( 105) of the candidate cell ( 126B), the different candidate cell (124), or a serving cell of the UE, at least one UL WUS configuration for the UL WUS configuration list.

3. The method of claim 2, further comprising: detecting (1260) an event for invalidating the at least one UL WUS configuration; and invaliding (1262) the at least one UL WUS configuration in response to the detecting the event.

4. The method of claim 2, wherein the receiving the at least one UL WUS configuration comprises: receiving (1101). from the NE, the first UL WUS configuration indicating the uplink resources for requesting the on-demand SIB transmission from the candidate cell (126B); and receiving (1144), from the NE, a second UL WUS configuration indicating second uplink resources for requesting a second on-demand SIB transmission from the candidate cell (126B) or third uplink resources for requesting a third on-demand SIB transmission from a second candidate cell supporting on-demand SIB transmission.

5. The method of claim 4, further comprising:51G114380 2870WOdetermining (1154) that the second UL WUS configuration indicates the second uplink resources for requesting the second on-demand SIB transmission from the candidate cell (126B); and performing one of: replacing (1156), in the UL WUS configuration list, the first UL WUS configuration with the second uplink WUS configuration, or modifying (1157), in the UL WUS configuration list, a first indicator for the first UL WUS resources with a second indicator for the second UL WUS resources.

6. The method of claim 4, further comprising: determining (1154) that the second UL WUS configuration indicates the third uplink resources for requesting the third on-demand SIB transmission from the second candidate cell supporting on-demand SIB transmission; retaining (1130) the first UL WUS configuration in the UL WUS configuration list; and storing (1158) the second UL WUS configuration in the UL WUS configuration list.

7. The method of claim 4, further comprising: determining (1154) that the second UL WUS configuration indicates the third uplink resources for requesting the third on-demand SIB transmission from the second candidate cell supporting on-demand SIB; and replacing (1131. 1158). in the UL WUS configuration list, the first UL WUS configuration with the second uplink WUS configuration.

8. The method of any of claims 1-7, further comprising: accessing (492), by the UE, a second cell that periodically transmits SIB; and performing one of: retaining (430), releasing (431), or barring, in the UL WUS configuration list, the first UL WUS configuration for the candidate cell (126B).

9. The method of claim 8: wherein the retaining the first UL WUS configuration comprises at least one of: determining (742) that the candidate cell (126B) and the second cell use a same radio access technology7(RAT), or determining (743) that the candidate cell (126B) and the second cell are configured with a same area ID;52G114380 2870WOwherein the releasing the first UL WUS configuration comprises at least one of: determining (742) that the candidate cell (126B) and the second cell use a different radio access technology (RAT), or determining (743) that the candidate cell (126B) and the second cell are configured with a different area ID.

10. The method of claim 8: wherein the retaining the first UL WUS configuration further comprises: receiving a message from the second cell, and determining (746) that the message indicates a non-release of the first UL WUS configuration; wherein the releasing the first UL WUS configuration further comprises: receiving another message from the second cell, and determining (746) that the another message indicates releasing of the first UL WUS configuration.1 1. The method of any of claims 1-10, further comprising, after the transmitting the WUS: receiving (314) the on-demand SIB transmission from the candidate cell (126B); accessing (490-1) the candidate cell (126B); detecting (532. 832) the candidate cell (126B) is out of coverage; and performing one of: retaining (530, 830) or releasing (532, 831), in the UL WUS configuration list, the first UL WUS configuration for the candidate cell (126B).

12. The method of claim 1, further comprising: receiving (314) the on-demand SIB transmission from the candidate cell (126B); starting (934) a validity timer for the on-demand SIB; detecting (936) an expiration of the validity7timer; and in response to the detecting, performing one of: transmitting (910), to the candidate cell (126B). a second WUS on the uplink resources to request a second on-demand SIB transmission, or releasing the first UL WUS configuration for the candidate cell (126B).

13. A method of wireless communication at a candidate cell (126B) supporting on-demand system information block, SIB, transmission, comprising:53G114380 2870WOtransmitting (304) an indication that periodic SIB transmission is deactivated for the candidate cell (126B); receiving (310, 610, 1010), from a user equipment, UE, (102), a wake-up signal, WUS, on uplink, UL, resources indicated by an UL WUS configuration to request an on-demand SIB transmission from the candidate cell (126B); and transmitting (314, 1014) the on-demand SIB.

14. The method of claim 13, further comprising: transmitting (401B, 701, 1001), to the UE (102), the UL WUS configuration; transmitting (1364), to the UE (102). a second configuration to detect an event for invalidating the UL WUS configuration; detecting (1036) that a validity period for the on-demand SIB expired; and transmitting (1052), to the UE (102) in response to the detecting, a second on-demand SIB.

15. A method of wireless communication at a first cell (126A), which is different from a candidate cell (126B), comprising: transmitting (401), to auser equipment, UE, (102), an uplink wake-up signal, UL WUS, configuration indicating uplink resources for requesting an on-demand system information block, SIB. transmission from the candidate cell.54G114380 2870WO

Images