WO2025035795A1

WO2025035795A1 - On-demand sib1

Info

Publication number: WO2025035795A1
Application number: PCT/CN2024/086259
Authority: WO
Inventors: Xiaoying Xu; Mingzeng Dai; Lianhai WU; Yuantao Zhang
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2024-04-05
Filing date: 2024-04-05
Publication date: 2025-02-20
Anticipated expiration: 2026-10-05

Abstract

Various aspects of the present disclosure relate to on-demand SIB1. In one aspect, a first network node determines at least one configuration of an UL WUS for at least one NES cell, and the configuration is related to a request for SIB1 of the at least one NES cell. In turn, the first network node transmits the at least one configuration of the UL WUS to a second network node, wherein the first network node provides the at least one NES cell.

Description

ON-DEMAND SIB1

TECHNICAL FIELD

The present disclosure relates to wireless communications, and more specifically to user equipment (UE) , network nodes and methods for supporting on-demand system information block type 1 (SIB1) .

BACKGROUND

A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as UE, or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .

It has been discussed and suggested to research on-demand SIB1 in network energy saving (NES) for NR. Study procedures and signaling methods to support on-demand SIB1 for UEs in idle or inactive mode may comprise at least one of the following: triggering method by uplink (UL) wake up signal (WUS) using an existing signal or channel; WUS configuration provisioning to UE; or information exchange between gNBs at least for the configuration of WUS, if necessary. There is a need to study which node determines the UL WUS configuration of an NES Cell in case of CU-DU split case.

SUMMARY

The present disclosure relates to UE, network nodes and methods that support on-demand SIB1. With the UE, network nodes and methods, on-demand SIB1 may be achieved.

Some implementations of a first network node described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: determine at least one configuration of a UL WUS for at least one NES cell, the configuration is related to a request for SIB1 of the at least one NES cell; and transmit the at least one configuration of the UL WUS via the transceiver to a second network node, wherein the first network node provides the at least one NES cell.

In some implementations, the processor is configured to transmit the at least one configuration of the UL WUS by: receiving a request for the at least one configuration of the UL WUS via the transceiver from the second network node; and transmitting the at least one configuration of the UL WUS based on the request.

In some implementations, the request for the at least one configuration of the UL WUS comprises information about the at least one NES cell.

In some implementations, the processor is further configured to: transmit a first indication via the transceiver to the second network node, wherein the first indication indicates whether the first network node is broadcasting the SIB1.

In some implementations, the processor is further configured to: transmit a second indication via the transceiver to the second network node, wherein the second indication indicates whether the first network node is broadcasting the at least one configuration of the UL WUS.

In some implementations, the processor is further configured to: receive a third indication via the transceiver from the second network node, wherein the third indication indicates the first network node to use on-demand SIB1 in one of the at least one NES cell, or the third indication indicates the first network node is allowed to use on-demand SIB1 in one of the at least one NES cell.

In some implementations, the processor is further configured to: receive a fourth indication via the transceiver from the second network node, wherein the fourth indication indicates the first network node to broadcast the at least one configuration of the UL WUS, or the fourth indication indicates the first network node is allowed to broadcast the at least one configuration of the UL WUS.

Some implementations of a second network node described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver from a first network node, at least one configuration of a UL WUS for at least one NES cell, wherein the first network node provides the at least one NES cell; transmit the at least one configuration of the UL WUS via the transceiver to a third network node of a first cell or a fourth network node of the first cell.

In some implementations, the processor is further configured to: receive an indication from the third network node of the first cell or the fourth network node of the first cell, wherein the indication indicates whether to accept the at least one configuration of the UL WUS or whether to stop providing the at least one configuration of the UL WUS to a user equipment (UE) .

In some implementations, the processor is further configured to: transmit a request for the at least one configuration of the UL WUS via the transceiver to the first network node.

In some implementations, the processor is further configured to: receive a request for the at least one configuration of the UL WUS via the transceiver from one of the following: a user equipment (UE) , the third network node, or the fourth network node.

In some implementations, the request for the at least one configuration of the UL WUS comprises information used to indicate the at least one NES cell.

In some implementations, the processor is further configured to: transmit a third indication via the transceiver to the first network node, wherein the third indication indicates the first network node to use on-demand system information block type 1 (SIB1) in one of the at least one NES cell, or the third indication indicates the first network node is allowed to use on-demand SIB1 in one of the at least one NES cell.

In some implementations, the processor is further configured to: transmit a fourth indication via the transceiver to the first network node, wherein the fourth indication indicates the first network node to broadcast the at least one configuration of the UL WUS, or the fourth indication indicates the first network node is allowed to broadcast the at least one configuration of the UL WUS.

Some implementations of a UE described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: obtain a configuration of a UL WUS for a cell; transmit, via the transceiver to the cell, the UL WUS for requesting SIB1based on the configuration of the UL WUS; and receive the SIB1 from the cell.

In some implementations, the processor is further configured to: determine to obtain the configuration of the UL WUS from a first cell after the UE camps on the first cell; determine to obtain the configuration of the UL WUS from the first cell after the UE camps on the first cell and based on channel condition of the first cell; or determine to obtain the configuration of the UL WUS from the first cell after the UE camps on the first cell and based on channel conditions of the first cell and the cell.

In some implementations, the processor is further configured to: receive a fifth indication via the transceiver from the cell, wherein the fifth indication indicates whether the cell supports on-demand SIB1.

In some implementations, the processor is further configured to: receive a sixth indication via the transceiver from the cell, wherein the sixth indication indicates whether the cell is broadcasting the configuration of the UL WUS.

In some implementations, the processor is configured to obtain the configuration of the UL WUS by: based on determining that the sixth indication indicates that the cell is broadcasting the configuration of the UL WUS, obtaining the configuration of the UL WUS from the cell.

In some implementations, the processor is further configured to: receive a seventh indication via the transceiver from the cell, wherein the seventh indication indicates whether the cell is broadcasting the SIB1.

In some implementations, the processor is configured to receive the seventh indication by: monitoring the seventh indication for a time duration after transmitting the UL WUS; or monitoring the SIB1 for the time duration after transmitting the UL WUS.

In some implementations, the processor is further configured to: based on determining that the SIB1 is not received during the time duration, consider a request for the SIB1 fails.

In some implementations, the processor is further configured to: based on determining that the seventh indication is not received during the time duration, consider a request for the SIB1 fails.

In some implementations, the processor is configured to obtain the configuration of the UL WUS based on one of the following: a first physical downlink control channel (PDCCH) resource in a first PDCCH configuration received from the cell, a first physical downlink shared channel (PDSCH) resource in a first PDSCH configuration received from the cell, a second PDCCH resource in a second PDCCH configuration received from a first cell, a second PDSCH resource in a second PDSCH configuration received from the first cell, a third PDCCH resource associated with a common control resource set (CORESET) and a common search space indicated in master information block (MIB) of the cell, a first physical broadcast channel (PBCH) resource for transmitting the MIB of the cell, or a second PBCH resource different from the first PBCH resource,

In some implementations, the configuration of the UL WUS comprises at least one of the following: a random access channel (RACH) resource configuration, a preamble resource configuration, a first physical downlink control channel (PDCCH) resource configuration for scheduling a first response to the UL WUS or a second response to a UL message, wherein the UL message is transmitted based on the first response, a second PDCCH resource configuration for scheduling the SIB1, a physical uplink shared channel (PUSCH) configuration for the UL message, a physical uplink control channel (PUCCH) configuration for the second response, or a period for requesting the SIB1.

In some implementations, the processor is configured to transmit the UL WUS based on a period for requesting the SIB1.

In some implementations, the processor is further configured to: consider the cell supporting on-demand SIB1 as if a cell status of the cell is barred based on determining that the UE is unable to obtain the configuration of the UL WUS.

In some implementations, the processor is configured to consider the cell supporting on-demand SIB1 as if the cell status of the cell is barred based on determining that the UE is unable to obtain the configuration of the UL WUS from the cell and a first cell.

In some implementations, the processor is configured to consider the cell supporting on-demand SIB1 as if the cell status of the cell is barred based on determining that the UE is unable to obtain the configuration of the UL WUS from the cell and has not obtained the configuration of the UL WUS from a first cell.

In some implementations, the processor is configured to consider the cell supporting on-demand SIB1 as if the cell status of the cell is barred based on determining the following: the UE is unable to obtain the configuration of the UL WUS from the cell and a first cell; and there is a second cell meeting cell selection criteria.

In some implementations, the processor is further configured to: determine to receive the SIB1 from the cell before the UE camps on the serving cell; or determine to receive the SIB1 from the cell after the UE camps on the cell; or determine to receive the SIB1 from the cell after the UE camps on the cell and based on determining that a random access procedure towards the cell is triggered.

Some implementations of a method described herein may include: determining at least one configuration of a UL WUS for at least one NES cell, the configuration is related to a request for SIB1 of the at least one NES cell; and transmitting the at least one configuration of the UL WUS to a second network node, wherein the first network node provides the at least one NES cell.

Some implementations of a method described herein may include: receiving, from a first network node, at least one configuration of a UL WUS for at least one NES cell, wherein the first network node provides the at least one NES cell; transmitting the at least one configuration of the UL WUS to a third network node of a first cell or a fourth network node of the first cell.

Some implementations of a method described herein may include: obtaining a configuration of a UL WUS for a cell; transmitting, to the cell, the UL WUS for requesting SIB1 based on the configuration of the UL WUS; and receiving the SIB1 from the cell.

Some implementations of a processor described herein may include at least one memory and a controller coupled with the at least one memory and configured to cause the controller to: obtain a configuration of a UL WUS for a cell; transmit, via the transceiver to the cell, the UL WUS for requesting SIB1 based on the configuration of the UL WUS; and receive the SIB1 from the cell.

It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Fig. 1 illustrates an example of a wireless communications system that supports on-demand SIB1 in accordance with aspects of the present disclosure;

Figs. 2A and 2B illustrate another example of a wireless communications system that supports on-demand SIB1 in accordance with aspects of the present disclosure, respectively;

Figs. 3 to 12 illustrate a signaling diagram illustrating an example process that supports on-demand SIB1 in accordance with aspects of the present disclosure, respectively;

Fig. 13 illustrates an example on-demand SIB1 transmission procedure 1300 in accordance with aspects of the present disclosure;

Fig. 14 illustrates an example of a device that supports on-demand SIB1 in accordance with some aspects of the present disclosure;

Fig. 15 illustrates an example of a processor that supports on-demand SIB1 in accordance with aspects of the present disclosure; and

Figs. 16, 17 and 18 illustrate a flowchart of a method that supports on-demand SIB1 in accordance with aspects of the present disclosure, respectively.

DETAILED DESCRIPTION

Principles of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein may be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first” and “second” or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

As described above, there is a need to study which node determines the UL WUS configuration of an NES Cell in case of CU-DU split case.

In view of the above, the present disclosure provides a solution that supports on-demand SIB1. In this solution, a first network node determines at least one configuration of a UL WUS for at least one NES cell, and the configuration is related to a request for SIB1 of the at least one NES cell. In turn, the first network node transmits the at least one configuration of the UL WUS to a second network node, wherein the first network node provides the at least one NES cell. With this solution, on-demand SIB1 may be achieved.

Aspects of the present disclosure are described in the context of a wireless communications system.

Fig. 1 illustrates an example of a wireless communications system 100 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one at least one of network entities 102 (also referred to as network equipment (NE) ) , one or more terminal devices or UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.

The network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station (BS) , a network element, a radio access network (RAN) node, a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface. The network entities 102 may be collectively referred to as network entities 102 or individually referred to as a network entity 102. Hereinafter, some implementations of the present disclosure will be described by taking a gNB as an example of the network entity 102. Thus, the network entity 102 may be used interchangeably with the gNB 102. For example, the gNBs 102 may comprise a gNB 102-1 and a gNB 102-2, as shown in Fig. 1.

A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an internet-of-things (IoT) device, an internet-of-everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.

The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in Fig. 1. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in Fig. 1. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.

A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) . In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .

In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open radio access network (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN intelligent controller (RIC) (e.g., a near-real time RIC (Near-RT RIC) , a non-real time RIC (Non-RT RIC) ) , a service management and orchestration (SMO) system, or any combination thereof.

An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) . In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .

Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., radio resource control (RRC) , service data adaption protocol (SDAP) , packet data convergence protocol (PDCP) ) . The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU.

Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs) . In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .

A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.

The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a packet data network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.

The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) . The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .

In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.

One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.

Fig. 2A illustrates another example of a wireless communications system 200A that supports on-demand SIB1 in accordance with aspects of the present disclosure. As shown in Fig. 2A, the wireless communications system 200A may comprise a first network node 210, a second network node 220, a third network node 230, a fifth network node 250 and the UE 104.

In some implementations, the first network node 210, the second network node 220, the third network node 230, and the fifth network node 250 may be collectively implemented as a gNB. For example, the second network node 220 may be implemented as a gNB-CU, and each of the first network node 210, the third network node 230, and the fifth network node 250 may be implemented as a gNB-DU. The gNB-CU and the gNB-DU may be connected via F1 interface. In such implementations, the first network node 210, the second network node 220, and the fifth network node 250 may be referred to as a gNB-DU 210, a gNB-CU 220 and a gNB-DU 250.

In some implementations, the gNB-CU may be a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected with the gNB-DU.

In some implementations, the gNB-DU may be a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected with the gNB-CU.

In some implementations, each of the gNB-DU 210 and the gNB-DU 250 may provide an NES cell, and the gNB-DU 230 may provide a first cell. Hereinafter, a first cell is also referred to as a Cell A. Cell A may refer to a cell that is periodically transmitting at least its own SIB1.

In some implementations, the NES cell is a cell that may transmit SIB1 in response to a UL WUS from a UE. For example, the UL WUS may be a preamble, a MAC CE or an RRC message. In some implementations, the NES cell is a cell that may transmit UL WUS configuration to the UE. In some implementations, the UL WUS configuration includes the resources and/or configuration to send SIB1 request. In some implementations, the Cell A is a cell that periodically transmits at least its own SIB1. For example, the Cell A may broadcast its own SIB1 to a UE.

In some implementations, the Cell A is a cell that may transmit SIB1 of a NES cell. For example, the Cell A may broadcast SIB1 of a NES cell to a UE. For example, the Cell A may transmit SIB1 of a NES cell in response to a UL WUS from a UE.

In some implementations, the Cell A is a cell that may transmit UL WUS configuration of an NES cell. For example, the Cell A may broadcast UL WUS configuration of an NES cell to the UE 104. For example, the Cell A may transmit UL WUS configuration of an NES cell in response to a request for the UL WUS configuration from the UE 104.

In some implementations, the first network node 210 and the third network node 230 may be connected to different network nodes, as shown in Fig. 2B.

Fig. 2B illustrates another example of a wireless communications system 200B that supports on-demand SIB1 in accordance with aspects of the present disclosure. As shown in Fig. 2B, the wireless communications system 200B may comprise the first network node 210, the second network node 220, the third network node 230, a fourth network node 240 and the UE 104.

It shall be noted that the wireless communications system 200B may further comprise the fifth network node 250 which is connected to the second network node 220 as shown in Fig. 2A. For the purpose of illustration, the fifth network node 250 is not shown in Fig. 2B.

In some implementations, the first network node 210 and the second network node 220 may be collectively implemented as a gNB. For example, the second network node 220 may be implemented as a gNB-CU, and the first network node 210 may be implemented as a gNB-DU. The gNB-CU and the gNB-DU may be connected via F1 interface. In such implementations, the first network node 210 and the second network node 220 may be referred to as a gNB-DU 210 and a gNB-CU 220.

In some implementations, the third network node 230 and the fourth network node 240 may be collectively implemented as another gNB. For example, the fourth network node 240 may be implemented as a gNB-CU, and the third network node 230 may be implemented as a gNB-DU. The gNB-CU and the gNB-DU may be connected via F1 interface. In such implementations, the third network node 230 and the fourth network node 240 may be referred to as a gNB-DU 230 and a gNB-CU 240.

In some implementations, the second network node 220 may communicate with the fourth network node 240 via Xn interface therebetween.

In some implementations, the gNB-DU 210 may provide an NES cell, and the gNB-DU 230 may provide a Cell A.

Fig. 3 illustrates a signaling diagram illustrating an example process 300 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The process 300 may involve the first network node 210, the second network node 220 and the third network node 230 in Fig. 2A or 2B as well as the fourth network node 240 in Fig. 2B. For the purpose of discussion, the process 300 will be described with reference to Fig. 2B.

As shown in Fig. 3, the first network node 210 determines 310 at least one configuration of a UL WUS for at least one NES cell. The at least one configuration is related to a request for SIB1 of the at least one NES cell. Hereinafter, for brevity, a configuration of a UL WUS for an NES cell or at least one configuration of a UL WUS for at least one NES cell is also referred to as a UL WUS configuration.

In turn, the first network node 210 transmits 320 the at least one configuration of the UL WUS to the second network node 220. The first network node 210 provides the at least one NES cell.

In some implementations, the UL WUS configuration and the NES Cell information (i.e., the cell information of the UL WUS configuration) may be included in an F1 SETUP REQUEST message. In such implementations, the first network node 210 may transmit the F1 SETUP REQUEST message to the second network node 220. The F1 SETUP REQUEST message may comprise information element (IE) as shown in Table 1.

Table 1

Alternatively, in some implementations, the UL WUS configuration and the NES Cell information may be included in a gNB-DU CONFIGURATION UPDATE message. In such implementations, the first network node 210 may transmit the gNB-DU CONFIGURATION UPDATE message to the second network node 220. The gNB-DU CONFIGURATION UPDATE message may comprise IE as shown in Table 2.

Table 2

Alternatively, in some implementations, the UL WUS configuration and the NES Cell information may be included in a dedicated or new F1 message. In such implementations, the first network node 210 may transmit the dedicated F1 UL WUS configuration Report message in a gNB-DU WUS configuration Report procedure to the second network node 220. The purpose of the gNB-DU WUS configuration Report procedure is to report the UL WUS configuration and the NES Cell information from a gNB-DU to a gNB-CU. The gNB-DU WUS configuration Report procedure may use non-UE associated signalling.

In some implementations, the UL WUS configuration of an NES cell may comprise a random access channel (RACH) resource configuration. In some implementations, the RACH resource configuration may comprise dedicated RACH resource (s) for requesting SIB1. In some implementations, the RACH resource configuration may comprise common RACH resource (s) for requesting SIB1. In some implementations, the RACH resource configuration may comprise at least one of the following: ra-PreambleStartIndex, ra-occationsC, or other RACH configuration.

In some implementations, ra-PreambleStartIndex represents one or more random access preamble indexs. For example, they may be ra-preamble index range from a ra-PreambleStartIndex. For example, If N SSBs are associated with a RACH occasion, where N > = 1, for the i-th SSB (i=0, …, N-1) the preamble with preamble index = ra-PreambleStartIndex + i is used for charging request; For N < 1, the preamble with preamble index = ra-PreambleStartIndex is used for charging request.

In some implementations, ra-occationsC may indicate a configuration of dedicated RACH Occasions for SIB1 request as shown in Table 3.

Table 3

In some implementations, other RACH configuration may indicate at least one parameter as shown in Table 4.

Table 4

Alternatively or additionally, in some implementations, the UL WUS configuration may comprise a preamble resource configuration.

Alternatively or additionally, in some implementations, the UL WUS configuration may comprise a first physical downlink control channel (PDCCH) resource configuration for scheduling a first response to the UL WUS or a second response to a UL message. The UL message is transmitted based on the first response. For example, the PDCCH resource configuration may indicate a control resource set (CORSET) and a search space of PDCCH.

Hereinafter, for brevity, the first response to the UL WUS is also referred to as message 2 (MSG2) or message B (MSGB) , the UL message is also referred to as message 3 (MSG3) , and the second response to the UL message is also referred to as message 4 (MSG4) .

Alternatively or additionally, in some implementations, the UL WUS configuration may comprise a second PDCCH resource configuration for scheduling the SIB1.

Alternatively or additionally, in some implementations, the UL WUS configuration may comprise a physical uplink shared channel (PUSCH) configuration for MSG3.

Alternatively or additionally, in some implementations, the UL WUS configuration may comprise a physical uplink control channel (PUCCH) configuration for MSG4.

Alternatively or additionally, in some implementations, the UL WUS configuration may comprise a period for requesting the SIB1. Hereinafter, the period for requesting the SIB1 is represented by “SIB1-RequestPeriod” . “SIB1-RequestPeriod” may be in number of association periods or in number of RACH period. The association period of SSB-to-RO mapping is defined as the completion of at least one round of SSB-to-RO mapping in that period, such that each SSB sent is mapped to at least one RO.

Upon receiving the at least one configuration of the UL WUS, the second network node 220 transmits 330 the at least one configuration of the UL WUS to the third network node 230. Alternatively, the second network node 220 transmits 340 the at least one configuration of the UL WUS to the fourth network node 240.

In some implementations, the second network node 220 may receive UL WUS configuration from each of one or more network nodes which provide NES cell. For example, the second network node 220 may receive UL WUS configuration from each of the first network node 210 and the fifth network node 250.

In some implementations, the second network node 220 may generate a gNB-CU UL WUS configuration for a Cell A based on the at least one configuration of the UL WUS and transmits the gNB-CU UL WUS configuration and the Cell A information to the third network node 230.

In some implementations, the second network node 220 may transmit an F1 message to the third network node 230. The F1 message may comprise the gNB-CU UL WUS configuration and the Cell A information as shown in Table 5. In some implementations, the gNB-CU UL WUS configuration may be an RRC container with UL WUS configuration.

Table 5

In some implementations, the gNB-CU UL WUS configuration may be included in a new SIB, in SIB1 or in other legacy SIB to the third network node 230. The second network node 220 may generate system Information to include gNB-CU UL WUS configuration, transmit the system Information and Cell A information to the third network node 230.

In some implementations, the UL WUS configuration and the NES Cell information may be included in a gNB-CU CONFIGURATION UPDATE message or SYSTEM INFORMATION DELIVERY COMMAND message. For example, the gNB-CU CONFIGURATION UPDATE message or SYSTEM INFORMATION DELIVERY COMMAND message may comprise gNB-CU System Information IE or gNB-CU UL WUS configuration as shown in Table 6.

Table 6

Fig. 4 illustrates a signaling diagram illustrating an example process 400 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The process 400 may be considered as an example implementation of the process 300. The process 400 may involve the first network node 210 and the second network node 220 in Fig. 2A or 2B. For the purpose of discussion, the process 400 will be described with reference to Fig. 2A or 2B.

As shown in Fig. 4, the first network node 210 may transmit 410 an indication to the second network node 220. The indication may indicate whether the first network node 210 supports on-demand SIB1. Alternatively, this indication may indicate whether the first network node 210 supports at least one NES cell supporting on-demand SIB1. Thus, this indication may be referred to as on-demand SIB1 indication or NES cell indication.

In some implementations, the first network node 210 may transmit the on-demand SIB1 indication per cell or per RNA per DU to the second network node 220.

For example, the first network node 210 may transmit the on-demand SIB1 indication as shown in Table 7.

Table 7

In some implementations, the first network node 210 may transmit 420 a first indication to the second network node 220. The first indication may indicate whether the first network node 210 is broadcasting the SIB1. Alternatively, the first indication may indicate whether the SIB1 is present. Alternatively, the first indication may indicate an on-demand SIB1 status. For example, the first indication may indicate whether the on-demand SIB1 function is enabled, i.e., whether the SIB1 can be on-demand triggered.

In some implementations, the first network node 210 may transmit the on-demand SIB1 status per cell or per DU to the second network node 220. For example, the first network node 210 may transmit the on-demand SIB1 status in a similar way to Table 7.For example, the first indication may indicate whether the on-demand SIB1 function of an NES cell is enabled, i.e., whether the SIB1 of an NES cell can be on-demand triggered.

In some implementations, the second network node 220 may transmit 430 a third indication to the first network node 210. The third indication indicates the first network node 210 to use on-demand SIB1 in one of the at least one NES cell. In this regard, the third indication may be referred to as on-demand SIB1 used indication. The on-demand SIB1 used indication may be of a value of {start, stop} . The on-demand SIB1 used indication may further indicate a period to use or not use the on-demand SIB1. Alternatively, the third indication indicates the first network node 210 is allowed to use on-demand SIB1 in one of the at least one NES cell. In this regard, the third indication may be referred to as on-demand SIB1 allowed indication.

In some implementations, the cells in the first network node 210 determines whether to use on-demand SIB1 based on the on-demand SIB1 used indication. If receiving the third indication of an NES cell, e.g., set to “start” , the NES cell uses the on-demand SIB1, e.g., notify UE SIB1 of the NES cell can be on-demand triggered, monitor on-demand SIB1 request, not broadcast SIB1. If receiving the third indication of an NES cell e.g., set to “stop” , the NES cell does not use or stops using the on-demand SIB1, e.g., notify UE SIB1 of the NES cell cannot be on-demand triggered. If the third indication indicates a period to use the on-demand SIB1 of an NES cell, the NES cell starts using the on demand SIB1 for a period e.g., from the timing of receiving the indication. If the third indication indicates a period to stop using the on-demand SIB1 of an NES cell, the NES cell does not use or stops using the on demand SIB1 for a period e.g., from the timing of receiving the indication.

In some implementations, the cells in the first network node 210 will take the third indication into account when to use on-demand SIB1, i.e., notify UE the SIB1 of the NES cell can be on-demand triggered, monitor on-demand SIB1 request, not broadcast SIB1. In this case, the first network node 210 determines whether to use on-demand SIB1. If the third indication of an NES cell is set to be “allowed” , the NES cell further determines whether to use the on-demand SIB1. If the indication of an NES cell is set to be “not allowed” , the NES cell does not use the on-demand SIB1.

In some implementations, the third indication may act as an implicit request for the at least one configuration of the UL WUS. In such implementations, the second network node 220 may not transmit an explicit request for the at least one configuration of the UL WUS to the first network node 210, which will be described with reference to Fig. 6 later.

It shall be noted that at least one of the actions in the process 400 may be performed in combination with the process 300.

Fig. 5 illustrates a signaling diagram illustrating an example process 500 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The process 500 may be considered as an example implementation of the process 300. The process 500 may involve the first network node 210 and the second network node 220 in Fig. 2A or 2B. For the purpose of discussion, the process 500 will be described with reference to Fig. 2A or 2B.

As shown in Fig. 5, the second network node 220 transmit 510 a fourth indication to the first network node 210. The fourth indication indicates the first network node 210 to broadcast the at least one configuration of the UL WUS. In this regard, the fourth indication may be referred to as UL WUS broadcast indication. Alternatively, the fourth indication indicates the first network node 210 is allowed to broadcast the at least one configuration of the UL WUS. In this regard, the fourth indication may be referred to as UL WUS broadcast allowed indication.

In some implementations, the cells in the first network node 210 will broadcast UL WUS configuration if receiving UL WUS broadcast indication. An NES cell broadcasts the UL WUS configuration if receiving broadcast indication e.g., set to “start” . An NES cell does not broadcast or stops broadcasting the UL WUS configuration if receiving broadcast indication e.g., set to “stop” .

In some implementations, the cells in the first network node 210 will take the UL WUS broadcast allowed indication into account when to broadcast UL WUS configuration. The first network node 210 can further determine whether to broadcast the UL WUS configuration of the NES cell if receiving the UL WUS broadcast allowed indication of the NES cell is set to be “allowed” . An NES cell does not broadcast or stop broadcasting the UL WUS configuration if receiving the UL WUS broadcast allowed indication e.g., set to be “not allowed” .

The first network node 210 may transmit 520 a second indication to the second network node 220. The second indication indicates whether the first network node 210 is broadcasting the at least one configuration of the UL WUS. Alternatively, the second indication may indicate whether the at least one configuration of the UL WUS is present. Alternatively, the second indication may indicate UL WUS configuration transmission status e.g., broadcasting or not broadcasting.

In some implementations, the first network node 210 may transmit the second indication per cell or per DU to the second network node 220. For example, the first network node 210 may transmit the second indication in a similar way to Table 7.

It shall be noted that at least one of the actions in the process 500 may be performed in combination with the process 300.

Fig. 6 illustrates a signaling diagram illustrating an example process 600 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The process 600 may be considered as an example implementation of the process 300. The process 600 may involve the first network node 210 and the second network node 220 in Fig. 2A or 2B. For the purpose of discussion, the process 600 will be described with reference to Fig. 2A or 2B.

As shown in Fig. 6, the second network node 220 transmits 610 a request for the UL WUS configuration to the first network node 210.

In some implementations, the request for the UL WUS configuration may comprise information about the at least one NES cell. In other words, the second network node 220 may transmit the request for the UL WUS configuration per cell. For example, the request for the UL WUS configuration may be associated with a served cell information as shown in Table 8.

Table 8

In some implementations, the second network node 220 may transmit the request for the UL WUS configuration per DU or per RNA (RAN-based Notification Area) .

In some implementations, the request for the UL WU configuration may be included in a legacy non-UE associated F1 message, e.g., GNB-CU CONFIGURATION UPDATE message.

In some implementations, the request for the UL WUS configuration may be included in a dedicated or new F1 message. The purpose of the UL WUS configuration request procedure is to command the first network node 210 to transmit the UL WUS configuration to the second network node 220. The procedure may use non-UE associated signalling.

In some implementations, the request for the UL WUS configuration may comprise {periodicity, one shot} . Periodicity indicates that the first network node 210 may transmit the UL WUS configuration and the NES Cell information to the second network node 220 periodically as indicated by the periodicity. One shot indicates that the first network node 210 may transmit the UL WUS configuration and the NES Cell information to the second network node 220 once.

In some implementations, if the first network node 210 supports to provide the UL WUS configuration, the first network node 210 transmits 620 the UL WUS configuration and the NES Cell information to the second network node 220.

In some implementations, the first network node 210 may transmit the UL WUS configuration and the NES Cell information to the second network node 220 if receiving the request for the UL WUS configuration, e.g., which comprises “one shot” . For example, if receiving the request for the UL WUS configuration which comprises “one shot” , the first network node 210 may transmit the UL WUS configuration and the NES Cell information to the second network node 220. For another example, if receiving the request for the UL WUS configuration which does not comprise “one shot” or “periodicity” , the first network node 210 may transmit, by default, the UL WUS configuration and the NES Cell information to the second network node 220.

In some implementations, the first network node 210 may transmit the UL WUS configuration and the NES Cell information to the second network node 220 periodically if receiving the request for the UL WUS configuration which comprises “periodicity” .

In some implementations, if the first network node 210 does not provide or cannot provide the UL WUS configuration for one or more cells in the first network node 210, the first network node 210 transmits a response to the request for the UL WUS configuration. The response indicates the failure cause to the second network node 220, and the failure cause indicates the first network node 210 does not provide the UL WUS configuration for the one or more cells in the first network node 210.

It shall be noted that at least one of the actions in the process 600 may be performed in combination with the process 300.

As described above, in some implementations, the first network node 210 and the third network node 230 may be connected to the second network node 220 and the fourth network node 240 respectively, as shown in Fig. 2B. In such implementations, the fourth network node 240 may reject the UL WUS configuration from the first network node 210. This will be described with reference to Fig. 7.

Fig. 7 illustrates a signaling diagram illustrating an example process 700 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The process 700 may be considered as an example implementation of the process 300. The process 700 may involve the second network node 220 and the fourth network node 240 and in Fig. 2B. For the purpose of discussion, the process 700 will be described with reference to Fig. 2B.

Generally, in the process 700, the second network node 220 may be implemented as a gNB-CU of an NES cell, and the fourth network node 240 may be implemented as a gNB-CU of a Cell A.

As shown in Fig. 7, the fourth network node 240 transmits 710 an indication to the second network node 220. The indication indicates that the fourth network node 240 supports transmission of the UL WUS configuration. Alternatively, the indication may indicate that capability of the fourth network node 240 to transmit the UL WUS configuration.

If receiving the indication, the second network node 220 transmits 720 the UL WUS configuration to the fourth network node 240. For example, the second network node 220 transmits 720 the UL WUS configuration and the cell information of the UL WUS configuration to the fourth network node 240. For another example, the second network node 220 transmits 720, to the fourth network node 240, the UL WUS configuration, cell information of the UL WUS configuration and cell information to receive the UL WUS configuration.

In turn, the fourth network node 240 transmits 730 an indication to the second network node 220. The indication indicates whether to accept or reject the UL WUS configuration or whether to stop providing the UL WUS configuration to the UE 104. In some implementations, the fourth network node 240 may reject the UL WUS configuration of at least one NES cell. In such implementations, the indication may indicate a failure cause to the second network node 220.

In some implementations, if the fourth network node 240 rejects the UL WUS configuration, it means the fourth network node 240 does not transmit the UL WUS configuration for the at least one NES cell. The indication may include the accepted cells information of the UL WUS configuration or rejected cells information of the UL WUS configuration.

The fourth network node 240 may transmit 740 an indication to the second network node 220. The indication indicates whether at least one Cell A in the fourth network node 240 does not provide the UL WUS configuration to the UE 104 for at least one NES cell in the second network node 220. For example, the fourth network node 240 accepted the UL WUS configuration, thus it determines to not provide the UL WUS configuration to the UE 104 for at least one NES cell. The indication may indicate which cell A does not provide the UL WUS configuration to the UE 104. The indication may indicate the NES cells for which it does not provide the UL WUS configuration to the UE 104.

It shall be noted that at least one of the actions in the process 700 may be performed in combination with the process 300.

In some implementations, the fourth network node 240 may request the UL WUS configuration to the second network node 220. This will be described with reference to Fig. 8.

Fig. 8 illustrates a signaling diagram illustrating an example process 800 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The process 800 may be considered as an example implementation of the process 300. The process 800 may involve the second network node 220 and the fourth network node 240 and in Fig. 2B. For the purpose of discussion, the process 800 will be described with reference to Fig. 2B.

Generally, in the process 800, the second network node 220 may be implemented as a gNB-CU of an NES cell, and the fourth network node 240 may be implemented as a gNB-CU of a Cell A.

As shown in Fig. 8, the second network node 220 transmits 810 an indication of at least one NES cell supporting on-demand SIB1 to the fourth network node 240. This indication is also referred to as NES cell indication.

The fourth network node 240 transmits 820 a request for UL WUS configuration of at least one NES cell to the second network node 220.

In some implementations, if the fourth network node 240 receives a request for UL WUS configuration of at least one NES cell from the UE 104, the fourth network node 240 determines to trigger a request for the UL WUS configuration to the second network node 220. The fourth network node 240 may receive the request for UL WUS configuration of at least one NES cell from the UE 104, and the request may include information used to indicate the at least one NES cell. For example, the information may comprise information of the at least one NES cell or random access (RA) resource associated with the at least one NES cell.

The second network node 220 transmits 830 the UL WUS configuration and the NES cell information to the fourth network node 240. The second network node 220 may further transmits 830 the Cell A information to transmit the UL WUS configuration and the NES cell information to the fourth network node 240, wherein the Cell A and the UL WUS configuration of the NES cell is mapped.

It shall be noted that at least one of the actions in the process 800 may be performed in combination with the process 300.

In some implementations, the first network node 210 may receive a request for UL WUS configuration of at least one specific cell from the UE 104 and transmits the UL WU configuration to the UE 104. This will be described with reference to Fig. 9.

Fig. 9 illustrates a signaling diagram illustrating an example process 900 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The process 900 may be considered as an example implementation of the process 300. The process 900 may involve the first network node 210 and the UE 104 and in Fig. 2A or 2B. For the purpose of discussion, the process 900 will be described with reference to Fig. 2A or 2B.

Generally, in the process 900, the first network node 210 receives a request for the UL WUS configuration from the UE 104 and transmits the UL WUS configuration to the UE 104 based on the request.

As shown in Fig. 9, the first network node 210 transmits 910 an indication to the UE 104. The indication indicates whether the UL WUS configuration is being broadcasted and/or whether to support request for the UL WUS configuration (e.g., for another cell) .

The first network node 210 receives 920 a request for the UL WUS configuration from the UE 104.

In some implementations, the request may be based on MSG1. For example, the UE 104 initiates a random access procedure, and transmits a preamble as the request on the allowed occasion to the first network node 210. For example, the UL WUS configuration and the information to indicate the cell of the UL WUS configuration is included in a new SIB, and RACH resource configuration associated with the new SIB is transmitted to the UE 104 in SIB1. In some implementations, the request may be based on MSG3. For example, the UE 104 initiates a random access procedure, and transmits a MAC CE as the request in MSG3 to the first network node 210.

In some implementations, the request for the UL WUS configuration may comprise information used to indicate at least one NES cell. In such implementations, the UE 104 may transmit the request for at least one specific cell based on MSG1. For example, the UE 104 receives a RACH resource configuration for the request of the UL WUS configuration from the first network node 210, the RACH resource configuration and PDCCH configuration for MSG2/MSG4. One RACH resource configuration is associated with at least one NES cell.

The first network node 210 transmits 930 the UL WUS configuration to the UE 104. The first network node 210 may transmit 930 the information used to indicate at least one NES cell of the UL WUS configuration to the UE 104. In some implementations, if the first network node 210 receives the request for the UL WUS configuration which comprises information used to indicate at least one NES cell, the first network node 210 may take it into account when transmitting the UL WUS configuration for the requested cells to the UE 104.

It shall be noted that at least one of the actions in the process 900 may be performed in combination with the process 300.

In some implementations, the second network node 220 (such as gNB-CU of an NES cell) may receive a request from the UE 104, and the second network node 220 may command the third network node 230 (such as gNB-DU of a Cell A) to broadcast the UL WUS configuration and the information to indicate the cell of the UL WUS configuration to the UE 104. Fig. 10 illustrates a signaling diagram illustrating an example process 1000 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The process 1000 may be considered as an example implementation of the process 300. The process 1000 may involve the second network node 220 and the third network node 230 in Fig. 2A or 2B. For the purpose of discussion, the process 1000 will be described with reference to Fig. 2A or 2B.

As shown in Fig. 10, the second network node 220 receives 1010 an indication from the first network node 210. The indication indicates the UL WUS configuration is not being broadcasted from the first network node 210. The indication indicates the UL WUS configuration is not being broadcasted for which NES cell from the first network node 210.

The second network node 220 receives 1020 a request for the UL WUS configuration from the UE 104.

The second network node 220 transmits the UL WUS configuration or an indication to the third network node 230. The indication indicates the third network node 230 to transmit the UL WUS configuration.

In some implementations, the UE 104 may transmit the request for the UL WUS configuration per NES cell or per RAN Notification Area. The UE 104 may indicate information of one or more cells for requesting the UL WUS configuration in an RRC message. If the second network node 220 receives the request for the UL WUS configuration including information of one or more cells, the second network node 220 may take it into account when transmitting the UL WUS configuration to the third network node 230. The second network node 220 initiates the procedure by sending a new F1 message or legacy F1 message (e.g., gNB-CU CONFIGURATION UPDATE) including the UL WUS configuration and the information to indicate the NES cell and cell A information to the third network node 230. For example, the UL WUS configuration and the information to indicate the cell of the UL WUS configuration may be included in an SIB. The second network node 220 initiates the procedure by sending a SYSTEM INFORMATION DELIVERY COMMAND message to the third network node 230.

If reception of the UL WUS configuration, the third network node 230 broadcasts 1040 the UL WUS configuration.

For example, upon reception of the SYSTEM INFORMATION DELIVERY COMMAND message, the third network node 230 shall broadcast the requested other system information (SI) including the UL WUS configuration and the information to indicate the NES cell.

In some embodiment, the UL WUS config configuration may be included in SIB1 or other SIB of a first cell.

It shall be noted that at least one of the actions in the process 1000 may be performed in combination with the process 300.

In some implementations, the second network node 220 (such as gNB-CU of an NES cell) may determine UL WUS configuration for at least one NES cell. This will be described with reference to Fig. 11.

Fig. 11 illustrates a signaling diagram illustrating an example process 1100 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The process 1100 may involve the second network node 220 and the third network node 230 in Fig. 2A or 2B. For the purpose of discussion, the process 1100 will be described with reference to Fig. 2A or 2B.

As shown in Fig. 11, the second network node 220 determines 1110 a UL WUS configuration for an NES cell. For example, the second network node 220 may determine the UL WUS configuration based on SIB1 received from the first network node 210 providing the NES Cell.

In turn, the second network node 220 transmits 1120 the UL WUS configuration to the third network node 230 providing a first cell (i.e., Cell A) . The UL WUS configuration is used to indicate information used to request SIB1 (i.e., on-demand SIB1) of the NES Cell.

In some implementations, the second network node 220 may transmit the UL WUS configuration to the first network node 210 providing the NES Cell. The first network node 210 may update SIB1 based on the UL WUS configuration. For example, totalNumberofRA-Preambles in SIB1 indicates a total number of preambles used for contention based and contention free 4-step or 2-step random access in the RACH resources defined in RACH-ConfigCommon, excluding preambles used for other purposes (e.g. for SI request) . If the UL WUS configuration is used for MSG1 based on-demand SIB1 solution, the second network node 220 may use a preamble used for contention based and contention free 4-step or 2-step random access, the first network node 210 may need update the RACH-ConfigCommon config.

Alternatively, the second network node 220 may update SIB1 based on the UL WUS configuration and transmits the updated SIB1 to the first network node 210 providing the NES cell.

The second network node 220 transmits 1130 a command or the UL WUS configuration and the information to indicate which NES cell to the first network node 210 providing the NES cell. The first network node 210 enables the on-demand SIB1, i.e., the first network node 210 broadcasts an indication to indicate the cell supports on-demand SIB1 based on the command. The first network node 210 may further broadcast the UL WUS configuration based on the received UL WUS configuration. If the UL WUS configuration is used for MSG3 based on-demand SIB1 solution, that means the US WUS configuration indicates the common RACH resource. The UE 104 transmits a UL WUS for requesting SIB1 in MSG3 in contention based random access procedure. The first network node 210 providing the NES cell needs not be aware which dedicated RACH resource is used for UL WUS configuration. If the second network node 220 receives the request, the second network node 220 commands the first network node 210 to broadcast SIB1, e.g., by using an indication of SIB1 type or SIB1 configuration in an RRC container as shown in Table 9.

Table 9

Fig. 12 illustrates a signaling diagram illustrating an example process 1200 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The process 1200 may involve the first network node 210 and the UE 104 in Fig. 2A or 2B. For the purpose of discussion, the process 1200 will be described with reference to Fig. 2B.

As shown in Fig. 12, the UE 104 obtains 1210 a configuration of a UL WUS for a cell. Hereinafter, a configuration of an UL WUS is also referred to as a UL WUS configuration. A serving cell refers to a cell on which the UE 104 camps. If the UE 104 camps on an NES cell, the NES cell is also referred to as a serving cell for the UE 104, e.g., after obtaining SIB1 of the NES cell.

The UE 104 transmits 1220, to the cell, the UL WUS for requesting SIB1 based on the UL WUS configuration.

In some implementations, if the cell is provided by the first network node 210, the UE 104 transmits 1220 the UL WUS to the first network node 210.

In turn, the UE 104 receives 1230 the SIB1 from the cell.

In some implementations, if the cell is provided by the first network node 210, the UE 104 receives 1230 the SIB1 from the first network node 210.

In some implementations, the UE 104 may obtain the UL WUS configuration from the cell. For example, the UE 104 may obtain the UL WUS configuration from the first network node 210 providing the serving cell. This will be described with reference to Fig. 13.

Fig. 13 illustrates an example on-demand SIB1 transmission procedure 1300 in accordance with aspects of the present disclosure. The procedure 1300 may be considered as an example implementation of the process 1200. The procedure 1300 may involve the first network node 210 and the UE 104 in Fig. 2A or 2B. For the purpose of discussion, the procedure 1300 will be described with reference to Fig. 2B.

As shown in Fig. 13, the first network node 210 providing the cell may transmit 1305 a fifth indication to the UE 104. The fifth indication indicates whether the cell supports on-demand SIB1, i.e., whether the SIB1 of the cell can be on-demand triggered. Hereinafter, the fifth indication is also referred to as on-demand SIB1 indication.

Alternatively or additionally, the first network node 210 providing the cell may transmit 1310 a sixth indication to the UE 104. The sixth indication may indicate whether the cell is broadcasting the UL WUS configuration. Alternatively, the sixth indication may indicate whether the UL WUS configuration is present. In this regard, the sixth indication is also referred to as UL WUS configuration present indication.

In some implementations, the first network node 210 may use a first value of ssb-SubcarrierOffset and/or a reserved bit (e.g., value 1) in the MIB of the cell to indicate that the cell is not broadcasting the SIB1 (i.e., absence of the SIB1) and/or indicate that the cell supports on-demand SIB1. For example, the first network node 210 may use a value of ssb-SubcarrierOffset which is equal to or greater than 12 for FR1 and which is equal to or greater than 24 for FR2. For another example, the first network node 210 may use a value of ssb-SubcarrierOffset which is less than 12 for FR1 and which is greater than 24 for FR2, and a reserved bit (e.g., value 1) .

In some implementations, the first network node 210 may use a second value of ssb-SubcarrierOffset and/or a reserved bit (e.g., value 0) in the MIB to indicate that the cell is broadcasting the UL WUS configuration (i.e., presence of the UL WUS configuration) . For example, the first network node 210 may use a value of ssb-SubcarrierOffset which is greater than 12 for FR1 and which is greater than 24 for FR2. Table 10 gives examples of possible values of ssb-SubcarrierOffset and the corresponding meaning.

In some implementations, the first network node 210 may use a value of ssb-SubcarrierOffset and cellBarred set to “barred” in the MIB to indicate that the cell is broadcasting the UL WUS configuration (i.e., presence of the UL WUS configuration) .

Table 10

In some implementations, optionally, the first network node 210 may transmit an indication indicating the cell is barred in MIB. A legacy UE considers the cell is barred based on the barred indication. The NES UE supporting on-demand SIB1 does not consider the cell is barred according to the barred indication, and determines whether the cell is barred or not further based on another information indicating the cell is barred in SIB1.

In some implementations, the first network node 210 may transmit 1320 (e.g., broadcast) the UL WUS configuration for the cell to the UE 104.

In some implementations, the UE 104 may receive the UL WUS configuration for the cell based on a first PDCCH resource in a first PDCCH configuration received from the cell. In some implementations, the first PDCCH configuration is predefined.

Alternatively, the UE 104 may receive the UL WUS configuration for the cell based on a first PDSCH resource in a first PDSCH configuration received from the cell. In some implementations, the first PDSCH configuration is predefined.

Alternatively, the UE 104 may receive the UL WUS configuration for the cell based on a second PDCCH resource in a second PDCCH configuration received from a first cell (i.e., Cell A) . In some implementations, the second PDCCH configuration is predefined.

Alternatively, the UE 104 may receive the UL WUS configuration for the cell based on a second PDSCH resource in a second PDSCH configuration received from the first cell. In some implementations, the second PDSCH configuration is predefined.

Alternatively, the UE 104 may receive the UL WUS configuration for the cell based on a third PDCCH resource associated with a common control resource set (CORESET) and a common search space indicated in MIB of the cell. The third PDCCH resource may be different from that for SIB1 transmission even they are both called as CORSET#0 and searchspace#0.

Alternatively, the UE 104 may receive the UL WUS configuration for the cell based on a first physical broadcast channel (PBCH) resource for transmitting the MIB of the cell. In such implementations, the UE 104 may receive the UL WUS configuration by reusing legacy PBCH resource. For example, the first network node 210 may use Time Division Multiplexing for transmitting MIB and UL WUS configuration.

Alternatively, the UE 104 may receive the UL WUS configuration for the cell based on a second PBCH resource different from the first PBCH resource. In some implementations, the second PBCH resource is predefined.

In some implementations, the first network node 210 may transmit the UL WUS configuration for the cell by PDCCH using a new radio network temporary identifier (RNTI) or system information radio network temporary identifier (SI-RNTI) .

In some implementations, periodicity for transmitting the UL WUS configuration may be different from periodicity for transmitting the SIB1 or MIB. A period for transmitting the UL WUS configuration may be more than 160ms. The period may be predefined.

As described above, in some implementations, the second network node 220 may transmit the third indication to the first network node 210. The third indication indicates the first network node 210 to use on-demand SIB1 in one of the at least one NES cell. In this regard, the third indication may be referred to as NES cell used indication. The NES cell transmits an indication to UE that the SIB1 of the NES cell in the first network node 210 can be on demand triggered if receiving the used indication e.g., set to use. The NES cell transmits an indication to UE that the SIB1 of the NES cell in the first network node 210 cannot be on demand triggered if receiving the used indication e.g., set to not use. Or, the third indication indicates the first network node 210 is allowed to use on-demand SIB1 in one of the at least one NES cell. In this regard, the third indication may be referred to as NES cell allowed indication. In such implementations, the cells in the first network node 210 will take the NES cell allowed indication into account when to use on-demand SIB1.

As described above, in some implementations, the second network node 220 transmit the fourth indication to the first network node 210. The fourth indication indicates the first network node 210 to broadcast the at least one configuration of the UL WUS. In this regard, the fourth indication may be referred to as NES cell broadcast indication. The NES cell transmits an indication to the UE 104 that the WUS config of the NES cell in the first network node 210 is present and transmits (e.g. broadcasts) the WUS configuration to the UE 104 if receiving the used indication e.g., set to broadcast/present. The NES cell transmits an indication to the UE 104 that the WUS config of the NES cell in the first network node 210 is not present and does not transmit (e.g., broadcasts) the WUS config if receiving the used indication e.g., set to not broadcast/present and does not transmit the WUS config to UE. The fourth indication may indicate the transmission periodicity of the WUS config. The fourth indication may indicate how long to transmit for the WUS configuration. Or, the fourth indication indicates the first network node 210 is allowed to broadcast the at least one configuration of the UL WUS. In this regard, the fourth indication may be referred to as UL WUS broadcast indication. In such implementations, the cells in the first network node 210 will take the UL WUS broadcast indication into account when to broadcast UL WUS configuration.

Accordingly, the UE 104 receives the fifth indication from the cell. For example, the UE 104 may determine, based on the fifth indication, that the cell supports on-demand SIB1 (i.e., the SIB1 of the cell can be triggered) .

Alternatively or additionally, the UE 104 may receive the sixth indication from the cell. For example, the UE 104 may determine, based on the sixth indication, that the cell is broadcasting the UL WUS configuration or the WUS configuration is present in the cell.

If the sixth indication indicates that the cell is broadcasting the UL WUS configuration or the WUS config is present, the UE 104 obtains the UL WUS configuration from the cell.

In turn, the UE 104 transmits 1330, to the cell, the UL WUS for requesting SIB1 of the cell based on the UL WUS configuration.

The configurations included in the UL WUS configuration has been described above with reference to Fig. 3. Details of the UL WUS configuration are omitted for brevity.

In some implementations, the UE 104 may transmit the UL WUS for requesting SIB1 by transmitting a preamble or an RRC message. In some implementations, UL WUS presents a signal or message for requesting SIB1. In some implementations, UL WUS configuration/config presents that resource and configuration which UE transmits UL WUS based on.

In some implementations, the UE 104 may monitor the SIB1 for the time duration after transmitting the UL WUS. The UE 104 starts receiving PDCCH using SI_RNTI scheduling SIB1 on the CORESET#0 and search space#0 after transmitting the preamble or from next period for SIB1 transmission. The period may be a timer length. The UE 104 starts a timer after transmitting the preamble to the first network node 210 or further from next period for SIB1 transmission. During the timer running, the UE 104 monitors SIB1 to determine whether SIB1 of the cell is present. The period may be configured in UL WUS configuration or predefined. The value of the timer may be in number for SIB transmission period. Upon the timer expiration, if the SIB1 of the cell has not received, the UE 104 may consider a request for the SIB1 fails. Then, the UE 104 may transmit the UL WUS again.

In some implementations, the UE 104 may initiate a SIB1 request procedure by transmitting the UL WUS based on a period for requesting the SIB1 (represented by SIB1-RequestPeriod) . The UE 104 may initiate one SIB1 request procedure in the SIB1-RequestPeriod.

In some implementations, optionally, the UE 104 receives 1340 a response to the UL WUS after transmitting the UL WUS for requesting SIB1.

In some implementations, if the UE 104 transmits the UL WUS in an RRC message via MSG3 or MSGA, a successful response is determined based on MSG4 or MSGB. If the UE 104 transmits the UL WUS via MSG1, the successful response is determined based on MSG2 (i.e., random access response (RAR) ) .

In some implementations, in order to receive the response to the UL WUS, the UE 104 receives PDCCH scheduling MSG2/MSGB/MSG4 on a CORSET and a search space. The PDCCH configuration may be transmitted in the UL WUS configuration.

In some implementations, in order to receive the response to the UL WUS, the UE 104 receives PDCCH scheduling MSG2/MSGB/MSG4 on a predefined CORSET and a predefined search space. It may be different from CORESET#0 and/or search space#0.

In some implementations, in order to receive the response to the UL WUS, the UE 104 receives PDCCH scheduling MSG2/MSGB/MSG4 on a CORSET#0 and a search space#0 configured in PDCCH-ConfigSIB1.

In some implementations, the PDCCH may be scrambled by an RNTI. For example, the RNTI is calculated based on PRACH occasion, on which the Random-Access Preamble (i.e., the UL WUS) is transmitted. For example, the RNTI may be predefined, which may be same as the SI-RNTI or different from the SI-RNTI.

In some implementations, the UE 104 receives MSG2/MSGB/MSG4 on a predefined PDSCH resource. For example, the MSG2/MSGB/MSG4 is carried on the resource.

In some implementations, the UE 104 may transmit 1350 a UL message (i.e., MSG3) based on the response to the UL WUS. If MSG3 based solution is applied, a configuration of an initial UL bandwidth part (BWP) including PUSCH configuration and PUCCH configuration may be predefined or provided via MSG2, or provided via UL WUS configuration transmitted by the cell (i.e., NES cell) .

Table 11 gives an example of the PUSCH configuration for transmitting MSG3.

Table 11

Table 12 gives an example of the PUCCH configuration for transmitting MSG3.

Table 12

In some implementations, if a successful response to the UL WUS is received at 1340 or a successful response (MGS4) to the UL message (MSG3) is received at 1360, the UE 104 considers the request for the SIB1 is successful. Otherwise, the UE 104 considers the request for the SIB1 fails. Then, the UE 104 may transmit the UL WUS again as done at 1330.

In some implementations, the first network node 210 providing the cell may transmit 1370 a seventh indication to the UE 104. The seventh indication indicates whether the cell (i.e., NES cell) is broadcasting the SIB1. Alternatively, the seventh indication indicates whether the SIB1 of the cell is present.

In some implementations, the first network node 210 may use a value of ssb-SubcarrierOffset in the MIB to indicate the cell (i.e., NES cell) is broadcasting the SIB1 (i.e., presence of SIB1) . For example, the first network node 210 may use a value of ssb-SubcarrierOffset which is less than 12 for FR1. The value of ssb-SubcarrierOffset may be different from the value of ssb-SubcarrierOffset at 1305. Alternatively, the first network node 210 may use a reserved bit (e.g., value 0) to indicate the cell (i.e., NES cell) is broadcasting the SIB1 (i.e., presence of SIB1) .

In some implementations, the UE 104 may monitor the seventh indication in the MIB for a period after transmitting the US WUS. For example, the UE 104 may monitor the seventh indication from next MIB period or after transmitting the UL WUS. The period may be a timer length. The UE 104 starts a timer after transmitting the UL WUS or from next MIB period. During the timer running, the UE 104 monitors the seventh indication to determine whether SIB1 of the cell is present. If the seventh indication indicating SIB1 of the cell is present is received, the UE 104 may perform an action 1380. The period may be configured in UL WUS configuration or predefined. The value of the timer may be in number for MIB transmission period. Upon the timer expiration, if the UE 104 has not received the seventh indication indicating the cell is broadcasting the SIB1, the UE 104 considers a request for the SIB1 fails. Then, the UE 104 may transmit the UL WUS again.

The UE 104 receives 1380 SIB1 of the cell.

In some implementations, the first network node 210 may transmit SIB1 based on PDCCH-ConfigSIB1. The UE 104 starts receiving PDCCH using SI_RNTI scheduling SIB1 on the CORESET#0 and search space#0 in PDCCH-ConfigSIB1.

In some implementations, the UE 104 may determine condition to trigger SIB1 request procedure in the cell (i.e., NES cell) . For example, the UE 104 may determine to obtain the SIB1 from the cell before the UE 104 camps on the cell. For example, the UE 104 may determine to obtain the SIB1 from the cell if the UE 104 needs to check whether to camp on the cell. After UE receives the SIB1, the UE 104 determines whether to camp on the cell based on the selection/reselection parameters in the SIB1. The UE 104 determines whether to camp on the cell based on the PLMN identity of the cell in the SIB1. If the UE 104 camps on a cell, the UE 104 has completed the cell selection/reselection process and has chosen the cell. The UE 104 monitors system information and (in most cases) paging information. The UE 104 may monitor UL WUS configuration for SIB1 request if available. If the UE 104 is in idle mode and has completed the cell selection/reselection process and has chosen a cell irrespective of PLMN identity, the UE 104 may camp on any cell.

For example, if an NES cell is the strongest cell during initial cell selection procedure, the UE 104 may determine to obtain the SIB1 from the cell. For example, if an NES cell is the strongest cell during cell selection procedure by leveraging stored information, the UE 104 may determine to obtain the SIB1 from the cell. Strongest cell presents that the cell on a particular frequency that is considered strongest according to the layer 1 cell search procedure.

For example, if an NES cell is the highest ranked cell or best cell according to cell reselection criteria, the UE 104 may determine to obtain the SIB1 from the cell.

For example, if an NES cell is the highest ranked cell or best cell according to absolute priority reselection rules, the UE 104 may determine to obtain the SIB1 from the cell.

In some embodiments, the PLMN identity of an NES cell may be in the UL WUS configuration of the NES cell.

For another example, the UE 104 may determine to receive the SIB1 from the cell after the UE 104 camps on the cell. In one embodiment, the UE 104 can camp on a NES cell before obtaining the SIB1 if the UL WUS configuration is present.

For a further example, the UE 104 may determine to receive the SIB1 from the cell after the UE 104 camps on the cell and if a random access procedure towards the cell is triggered. For example, if RRC connection setup request procedure or RRC connection resume procedure is triggered, the UE 104 may determine to receive the SIB1 from the cell. This may bring access delay. For example, an emergency call is triggered, or a paging is received from the first network node 210.

In some implementations, the random access procedure may be triggered by a number of events. The events may comprise at least one of the following:

- Initial access from RRC_IDLE;

- RRC Connection Re-establishment procedure;

- DL or UL data arrival during RRC_CONNECTED when UL synchronisation status is "non-synchronised" ;

- UL data arrival during RRC_CONNECTED when there are no PUCCH resources for SR available;

- SR failure;

- Request by RRC upon synchronous reconfiguration (e.g. handover) ;

- RRC Connection Resume procedure from RRC_INACTIVE;

- To establish time alignment for a secondary TAG;

- Request for Other System information;

- Beam failure recovery;

- Consistent UL LBT failure on SpCell;

- Small data transmision in RRC_INACTIVE; or

- Positioning purpose during RRC_INACTIVE.

In some implementations, the UE 104 may determine trigger condition to obtain the UL WUS configuration from the first cell (i.e., Cell A) . If the UL WUS configuration is broadcasting, the UE 104 obtains the UL WUS configuration by receiving it. If the UL WUS configuration is not broadcasting, the UE 104 transmits request to the first cell and then the first cell transmits (e.g., broadcasts) the UL WUS configuration to UE.

In some implementations, the UE 104 may determine to obtain the UL WUS configuration from a Cell A after the UE 104 camps on the Cell A.

In some implementations, the UE 104 may determine to obtain the UL WUS configuration from a Cell A and if the Cell A has UL WUS configuration for the cell. The UE 104 may camp on the Cell A.

In some implementations, the UE 104 may determine to obtain the UL WUS configuration from a Cell A and if there is the neighbour NES Cell supporting on-demand SIB1. If the UL WUS configuration for the NES cell is not broadcasted, the UE 104 may transmit a request for the UL WUS configuration to Cell A. The UE may camp on the Cell A.

Alternatively, in some implementations, the UE 104 may determine to obtain the UL WUS configuration from the Cell A and based on channel condition of the Cell A. In some implementations, the UE 104 may determine to obtain the UL WUS configuration from the Cell A and based on channel condition of the Cell A. The channel condition may include at least one of the following: reference signal receiving power (RSRP) of the Cell A or reference signal received quality (RSRQ) of the Cell A. In such implementations, the UE 104 may determine to obtain the UL WUS configuration from the Cell A and based on the Srxlev threshold and Squal threshold for Intra-measurements. The UE 104 may camp on the Cell A. For example, after the UE 104 camps on the Cell A, the UE 104 determine to obtain the UL WUS configuration from the Cell A by performing a procedure as shown in Table 13.

Table 13

Alternatively, the UE 104 may determine to obtain the UL WUS configuration from the Cell A and based on the Srxlev threshold and Squal threshold for Inter-measurements and/or reselection priority of the frequency. The UE may camp on the Cell A.

For example, after the UE 104 camps on the Cell A, the UE 104 determine to obtain the UL WUS configuration from the Cell A by performing a procedure as shown in Table 14.

Table 14

Alternatively, in some implementations, the UE 104 may determine to obtain the UL WUS configuration from the Cell A and based on channel conditions of the Cell A and the NES cell. In such implementations, the UE 104 may determine to obtain the UL WUS configuration from the Cell A and based on cell reselection criteria.

For example, the UE 104 may determine to obtain the UL WUS configuration from Cell A and if cell reselection criterion is met and tend to reselect to the NES cell.

For example, if an NES cell is the highest ranked cell according to the cell reselection criteria, the UE 104 may determine to obtain the UL WUS configuration from Cell A .

For example, if an NES cell is the highest ranked cell or best cell according to cell reselection criteria, the UE 104 may determine to obtain the UL WUS configuration from Cell A.

For example, if an NES cell is the highest ranked cell or best cell according to absolute priority reselection rules, the UE 104 may determine to obtain the UL WUS configuration from Cell A.

For example, if an NES cell is the strongest cell during initial cell selection procedure, the UE 104 may determine to obtain the UL WUS configuration from Cell A.

For example, if an NES cell is the strongest cell during cell selection procedure by leveraging stored information, the UE 104 may determine to obtain the UL WUS configuration from the Cell A. Strongest cell presents that the cell on a particular frequency that is considered strongest according to layer 1 cell search procedure. In some implementations, the UE 104 may need to determine whether an NES cell is barred or not based on SIB1 before camping on the NES cell and after obtaining UL WUS configuration.

In some implementations, the UE 104 104 may consider the cell (i.e., the NES cell) supporting on-demand SIB1 as if a cell status of the cell is barred if the UE 104 is unable to obtain the UL WUS configuration or before obtaining the UL WUS config.

For example, the UE 104 104 may consider the NES cell supporting on-demand SIB1 as if the cell status of the NES cell is barred if the UE 104 is unable to obtain the UL WUS configuration from the NES cell and the first cell (i.e., the Cell A) .

In some implementations, if the NES cell provides (e.g., broadcasts) the UL WUS configuration for SIB1 request to the UE 104, the UE 104 considers being able to acquire the UL WUS configuration and further considers being able to obtain the SIB1 of the NES cell. Therefore, the UE 104 considers a cell status of the NES cell is not as if barred before obtaining SIB1. SIB1 further indicates whether the NES cell is barred or not.

In some implementations, if the NES cell does not provide the UL WUS configuration for SIB1 request to the UE 104, the UE 104 consider the cell status of the NES cell is as if barred before obtaining the UL WUS configuration for SIB1 request from the Cell A. In such implementations, the UE 104 104 may consider the NES cell supporting on-demand SIB1 as if the cell status of the NES cell is barred if the UE 104 is unable to obtain the UL WUS configuration from the NES cell and has not obtained the UL WUS configuration from the Cell A.

For example, the NES cell is to be treated as if the cell status is "barred" due to not acquiring the UL WUS configuration for SIB1 request and due to being unable to acquire the SIB1. During initial cell selection, the UE 104 considers the cell status of the NES cell with on-demand SIB1 and being not broadcasting the UL WUS configuration is as if barred before obtaining the UL WUS configuration for SIB1 request from the Cell A.The UE 104 is not permitted to select or reselect the cell. For example, in cell selection procedure, if a second cell (i.e., a suitable NES Cell) is found and the NES Cell is not able to provide the UL WUS of the NES Cell to the UE 104, the UE 104 does not select the suitable NES Cell. The UE 104 selects a suitable Cell A if a suitable Cell A is found. For example, the UE 104 may select the second cell if the second cell meets re-selection criteria, and the UE 104 may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds.

In some implementations, a suitable refers to a cell on which the UE 104 may camp.

In some implementations, the UE 104 may further determine whether there is at least one other suitable Cell A found. If yes, the NES cell being not broadcasting the UL WUS configuration is to be treated as if the cell status is "barred" , alternatively UE does not select the NES cell. After the UE 104 obtains UL WUS configuration for requesting SIB1 of an NES cell, the NES cell becomes to be treated as if the cell status is not "barred" . For example, in cell selection procedure, the UE 104 selects a suitable Cell A if a suitable Cell A is found. The UE 104 may further obtain the UL WUS configuration from the Cell A and may reselect the NES cell according to cell reselection criteria.

In some implementations, if the UE 104 is in a Cell A, the UE 104 may transmit a UL WUS for requesting SIB1 of an NES cell to the Cell A. In such implementations, there is a need to define trigger condition for transmitting a UL WUS to the Cell A.

In some implementations, Cell A may transmit SIB1 of the NES cell to the UE 104 if receiving a UL WUS for requesting SIB1 of an NES cell. Cell A may transmit SIB1 of the NES cell via a new SIB. After the UE 104 receives SIB1 corresponding to UL WUS from the Cell A, the UE 104 consider whether a cell status of the NES cell is barred further based on SIB1.

In some implementations, a network node of Cell A (such as the third network node 230) may notify a network node of the NES cell (such as the first network node 210) to transmit SIB1. For example, a gNB-CU of Cell A may notify a gNB-CU of the NES cell to transmit SIB1 for the NES cell, e.g., via a Xn Message indicating which NES cell (s) to transmit SIB1. For example, the message may be Cell Activation message. A gNB-CU of the NES cell (such as the second network node 220) may further command the gNB-DU of the NES cell (such as the first network node 210) to transmit SIB1 for the NES cell, e.g., via an F1 message indicating which cell to transmit SIB1. For example, the message may be SYSTEM INFORMATION DELIVERY COMMAND message or SETUP RESPONSE or gNB-CU CONFIGURATION UPDATE message

In such implementations, after the UE 104 receives successful response corresponding to the UL WUS from Cell A, the UE 104 considers the NES cell is able to obtain SIB1. In other words, the UE 104 go to receive SIB1 from the NES cell.

In some implementations, the UL WUS may be an RRC request indicating one or more requested cell information. In some implementations, the UL WUS may be an RACH resource associated with one or more requested cell information.

In some implementations, the UE 104 may determine to transmit UL WUS based on the channel condition of Cell A and/or NES cell. The channel condition may include the measured RSRP and/or RSRQ of a cell. In some implementations, the UE 104 may determine to transmit UL WUS based on the measured RSRP and/or RSRQ of Cell A and/or NES cell. For example, the UE 104 determines to transmit UL WUS to Cell A based on RSRP threshold and/or RSRQ threshold. The threshold may be same or separate from the RSRP threshold and RSRQ threshold for measurement.

In some implementations, the UE 104 may determine to transmit UL WUS based on the frequency reselection priority of Cell A and NES cell, channel condition of Cell A and/or NES cell.

For example, the UE 104 determines to transmit UL WUS to Cell A based on the RSRP threshold and RSRQ threshold for intra-frequency measurement (e.g., S_IntraSearchP, S_IntraSearchQ) . The threshold is related to measurement rules for reselection.

For example, the UE 104 determines to transmit UL WUS based on the reselection priority of frequency. The UE 104 always performs measurement for higher reselection priority of inter-frequency. Therefore, if there is inter-frequency of higher reselection priority, the UE 104 determines to transmit UL WUS. If there is inter- frequency of lower or same reselection priority, the UE 104 determines to transmit UL WUS further based on RSRP threshold and RSRQ threshold for non-intra-frequency measurement (e.g., S_{nonIntraSearchP}, S_{nonIntraSearchQ}) .

Further, the UE 104 determines to transmit UL WUS for requesting SIB1 of an NES cell.

For example, the UE 104 may determine to transmit UL WUS for requesting SIB1 of the NES cell based on determining whether the UE 104 determines there is a neighbour NES cell (of intra-frequency and/or inter-frequency) .

For example, the UE 104 may determine to transmit UL WUS for requesting SIB1 of the NES cell based on determining whether the UE 104 determines there is a neighbour NES cell belonging to the inter-frequency of higher reselection priority.

In turn, the UE 104 transmits UL WUS for requesting SIB1 to Cell A. For example, the RSRP and/RSRQ of the NES cell is higher than the RSRP and/RSRQ of the Cell A. For example, the UE 104 transmits UL WUS to Cell A further based on the cell reselection and/or selection criterion. The UE 104 transmits UL WUS to Cell A if the UE 104 determines to select the NES cell.

Fig. 14 illustrates an example of a device 1400 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The device 1400 may be an example of a network entity 102 or a UE 104 as described herein. The device 1400 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 1400 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 1402, a memory 1404, a transceiver 1406, and, optionally, an I/O controller 1408. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 1402, the memory 1404, the transceiver 1406, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 1402, the memory 1404, the transceiver 1406, or various combinations or components thereof may support a method for performing one or more of the operations described herein.

In some implementations, the processor 1402, the memory 1404, the transceiver 1406, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 1402 and the memory 1404 coupled with the processor 1402 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 1402, instructions stored in the memory 1404) .

For example, the processor 1402 may support wireless communication at the device 1400 in accordance with examples as disclosed herein. The processor 1402 may be configured to operable to support a means for performing the following: determining at least one configuration of a UL WUS for at least one NES cell, the configuration is related to a request for SIB1 of the at least one NES cell; and transmitting the at least one configuration of the UL WUS to a second network node, wherein the first network node provides the at least one NES cell.

Alternatively, in some implementations, the processor 1402 may be configured to operable to support a means for performing the following: receiving, from a first network node, at least one configuration of a UL WUS for at least one NES cell, wherein the first network node provides the at least one NES cell; transmitting the at least one configuration of the UL WUS to a third network node of a first cell or a fourth network node of the first cell.

Alternatively, in some implementations, the processor 1402 may be configured to operable to support a means for performing the following: obtaining a configuration of a UL WUS for a cell; transmitting, to the cell, the UL WUS for requesting SIB1based on the configuration of the UL WUS; and receiving the SIB1 from the cell.

The processor 1402 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 1402 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 1402. The processor 1402 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1404) to cause the device 1400 to perform various functions of the present disclosure.

The memory 1404 may include random access memory (RAM) and read-only memory (ROM) . The memory 1404 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1402 cause the device 1400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 1402 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 1404 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The I/O controller 1408 may manage input and output signals for the device 1400. The I/O controller 1408 may also manage peripherals not integrated into the device M02. In some implementations, the I/O controller 1408 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 1408 may utilize an operating system such as or another known operating system. In some implementations, the I/O controller 1408 may be implemented as part of a processor, such as the processor 1406. In some implementations, a user may interact with the device 1400 via the I/O controller 1408 or via hardware components controlled by the I/O controller 1408.

In some implementations, the device 1400 may include a single antenna 1410. However, in some other implementations, the device 1400 may have more than one antenna 1410 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1406 may communicate bi-directionally, via the one or more antennas 1410, wired, or wireless links as described herein. For example, the transceiver 1406 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1406 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1410 for transmission, and to demodulate packets received from the one or more antennas 1410. The transceiver 1406 may include one or more transmit chains, one or more receive chains, or a combination thereof.

A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 1410 for transmitting the amplified signal into the air or wireless medium.

A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 1410 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

Fig. 15 illustrates an example of a processor 1500 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The processor 1500 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1500 may include a controller 1502 configured to perform various operations in accordance with examples as described herein. The processor 1500 may optionally include at least one memory 1504, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 1500 may optionally include one or more arithmetic-logic units (ALUs) 1506. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .

The processor 1500 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1500) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .

The controller 1502 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1500 to cause the processor 1500 to support various operations in accordance with examples as described herein. For example, the controller 1502 may operate as a control unit of the processor 1500, generating control signals that manage the operation of various components of the processor 1500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

The controller 1502 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1504 and determine subsequent instruction (s) to be executed to cause the processor 1500 to support various operations in accordance with examples as described herein. The controller 1502 may be configured to track memory address of instructions associated with the memory 1504. The controller 1502 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1502 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1500 to cause the processor 1500 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1502 may be configured to manage flow of data within the processor 1500. The controller 1502 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 1500.

The memory 1504 may include one or more caches (e.g., memory local to or included in the processor 1500 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 1504 may reside within or on a processor chipset (e.g., local to the processor 1500) . In some other implementations, the memory 1504 may reside external to the processor chipset (e.g., remote to the processor 1500) .

The memory 1504 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1500, cause the processor 1500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1502 and/or the processor 1500 may be configured to execute computer-readable instructions stored in the memory 1504 to cause the processor 1500 to perform various functions. For example, the processor 1500 and/or the controller 1502 may be coupled with or to the memory 1504, the processor 1500, the controller 1502, and the memory 1504 may be configured to perform various functions described herein. In some examples, the processor 1500 may include multiple processors and the memory 1504 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

The one or more ALUs 1506 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 1506 may reside within or on a processor chipset (e.g., the processor 1500) . In some other implementations, the one or more ALUs 1506 may reside external to the processor chipset (e.g., the processor 1500) . One or more ALUs 1506 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1506 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1506 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1506 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 1506 to handle conditional operations, comparisons, and bitwise operations.

For example, the processor 1500 may support wireless communication at the device 1400 in accordance with examples as disclosed herein. The processor 1500 may be configured to operable to support a means for performing the following: determining at least one configuration of a UL WUS for at least one NES cell, the configuration is related to a request for SIB1of the at least one NES cell; and transmitting the at least one configuration of the UL WUS to a second network node, wherein the first network node provides the at least one NES cell.

Alternatively, in some implementations, the processor 1500 may be configured to operable to support a means for performing the following: receiving, from a first network node, at least one configuration of a UL WUS for at least one NES cell, wherein the first network node provides the at least one NES cell; transmitting the at least one configuration of the UL WUS to a third network node of a first cell or a fourth network node of the first cell.

Alternatively, in some implementations, the processor 1500 may be configured to operable to support a means for performing the following: obtaining a configuration of a UL WUS for a cell; transmitting, to the cell, the UL WUS for requesting SIB1based on the configuration of the UL WUS; and receiving the SIB1 from the cell.

Fig. 16 illustrates a flowchart of a method 1600 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The operations of the method 1600 may be implemented by a device or its components as described herein. For example, the operations of the method 1600 may be performed by the first network node 210 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1610, the method may include determining at least one configuration of a UL WUS for at least one NES cell, the configuration is related to a request for SIB1of the at least one NES cell. The operations of 1610 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1610 may be performed by a device as described with reference to Fig. 2A or 2B.

At 1620, the method may include transmitting the at least one configuration of the UL WUS to a second network node, wherein the first network node provides the at least one NES cell. The operations of 1620 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1620 may be performed by a device as described with reference to Fig. 2A or 2B.

Fig. 17 illustrates a flowchart of a method 1700 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The operations of the method 1700 may be implemented by a device or its components as described herein. For example, the operations of the method 1700 may be performed by the second network node 220 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1710, the method may include receiving, from a first network node, at least one configuration of a UL WUS for at least one NES cell, wherein the first network node provides the at least one NES cell. The operations of 1710 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1710 may be performed by a device as described with reference to Fig. 2A or 2B.

At 1720, the method may include transmitting the at least one configuration of the UL WUS to a third network node of a first cell or a fourth network node of the first cell. The operations of 1720 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1720 may be performed by a device as described with reference to Fig. 2A or 2B.

Fig. 18 illustrates a flowchart of a method 1800 that supports on-demand SIB1 in accordance with aspects of the present disclosure. The operations of the method 1800 may be implemented by a device or its components as described herein. For example, the operations of the method 1800 may be performed by the second network node 220 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

At 1810, the method may include obtaining a configuration of a UL WUS for a cell. The operations of 1810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1810 may be performed by a device as described with reference to Fig. 2A or 2B.

At 1820, the method may include transmitting, to the cell, the UL WUS for requesting SIB1based on the configuration of the UL WUS. The operations of 1820 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1820 may be performed by a device as described with reference to Fig. 2A or 2B.

At 1830, the method may include receiving the SIB1 from the cell. The operations of 1830 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1830 may be performed by a device as described with reference to Fig. 2A or 2B.

It shall be noted that implementations of the present disclosure which have been described with reference to Figs. 1 to 13 are also applicable to the device 1500, the processor 1600 and the methods 1600, 1700 and 1800.

It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A first network node, comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

determine at least one configuration of an uplink (UL) wake up signal (WUS) for at least one network energy saving (NES) cell, the configuration is related to a request for system information block type 1 (SIB1) of the at least one NES cell; and

transmit the at least one configuration of the UL WUS via the transceiver to a second network node, wherein the first network node provides the at least one NES cell.
The first network node of claim 1, wherein the processor is configured to transmit the at least one configuration of the UL WUS by:

receiving a request for the at least one configuration of the UL WUS via the transceiver from the second network node; and

transmit the at least one configuration of the UL WUS based on the request.
The first network node of claim 1, wherein the processor is further configured to:

transmit a first indication via the transceiver to the second network node, wherein the first indication indicates whether the first network node is broadcasting the SIB1.
The first network node of claim 1, wherein the processor is further configured to:

transmit a second indication via the transceiver to the second network node, wherein the second indication indicates whether the first network node is broadcasting the at least one configuration of the UL WUS.
The first network node of claim 1, wherein the processor is further configured to:

receive a third indication via the transceiver from the second network node, wherein the third indication indicates the first network node to use on-demand SIB1 in one of the at least one NES cell, or the third indication indicates the first network node is allowed to use on-demand SIB1 in one of the at least one NES cell.
The first network node of claim 1, wherein the processor is further configured to:

receive a fourth indication via the transceiver from the second network node, wherein the fourth indication indicates the first network node to broadcast the at least one configuration of the UL WUS, or the fourth indication indicates the first network node is allowed to broadcast the at least one configuration of the UL WUS.
A second network node, comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

receive, via the transceiver from a first network node, at least one configuration of an uplink (UL) wake up signal (WUS) for at least one network energy saving (NES) cell, wherein the first network node provides the at least one NES cell;

transmit the at least one configuration of the UL WUS via the transceiver to a third network node of a first cell or a fourth network node of the first cell.
The second network node of claim 7, wherein the processor is further configured to:

receive an indication from the third network node of the first cell or the fourth network node of the first cell, wherein the indication indicates whether to accept the at least one configuration of the UL WUS or whether to stop providing the at least one configuration of the UL WUS to a user equipment (UE) .
The second network node of claim 7, wherein the processor is further configured to:

transmit a request for the at least one configuration of the UL WUS via the transceiver to the first network node.
The second network node of claim 7, wherein the processor is further configured to:

receive a request for the at least one configuration of the UL WUS via the transceiver from one of the following: a user equipment (UE) , the third network node, or the fourth network node.
The second network node of claim 7, wherein the processor is further configured to:

transmit a third indication via the transceiver to the first network node, wherein the third indication indicates the first network node to use on-demand system information block type 1 (SIB1) in one of the at least one NES cell, or the third indication indicates the first network node is allowed to use on-demand SIB1 in one of the at least one NES cell.
The second network node of claim 7, wherein the processor is further configured to:

transmit a fourth indication via the transceiver to the first network node, wherein the fourth indication indicates the first network node to broadcast the at least one configuration of the UL WUS, or the fourth indication indicates the first network node is allowed to broadcast the at least one configuration of the UL WUS.
A user equipment (UE) , comprising:

a processor; and

a transceiver coupled to the processor,

wherein the processor is configured to:

obtain a configuration of an uplink (UL) wake up signal (WUS) for a cell;

transmit, via the transceiver to the cell, the UL WUS for requesting system information block type 1 (SIB1) based on the configuration of the UL WUS; and

receive the SIB1 from the cell.
The UE of claim 13, wherein the processor is further configured to:

determine to obtain the configuration of the UL WUS from a first cell after the UE camps on the first cell;

determine to obtain the configuration of the UL WUS from the first cell after the UE camps on the first cell and based on channel condition of the first cell; or

determine to obtain the configuration of the UL WUS from the first cell after the UE camps on the first cell and based on channel conditions of the first cell and the cell.
The UE of claim 13, wherein the processor is further configured to:

receive a fifth indication via the transceiver from the cell, wherein the fifth indication indicates whether the cell supports on-demand SIB1.
The UE of claim 13, wherein the processor is further configured to:

receive a sixth indication via the transceiver from the cell, wherein the sixth indication indicates whether the cell is broadcasting the configuration of the UL WUS.
The UE of claim 13, wherein the processor is further configured to receive a seventh indication by:

monitoring the seventh indication for a time duration after transmitting the UL WUS; or

monitoring the SIB1 for the time duration after transmitting the UL WUS, wherein the seventh indication indicates whether the cell is broadcasting the SIB1.
The UE of claim 13, wherein the processor is configured to transmit the UL WUS based on a period for requesting the SIB1.
The UE of claim 13, wherein the processor is further configured to:

consider the cell supporting on-demand SIB1 as if a cell status of the cell is barred based on determining that the UE is unable to obtain the configuration of the UL WUS.
The UE of claim 13, wherein the processor is configured to consider the cell supporting on-demand SIB1 as if the cell status of the cell is barred based on determining that the UE is unable to obtain the configuration of the UL WUS from the cell and has not obtained the configuration of the UL WUS from a first cell.