Method and apparatus for requesting on-demand-system information block 1

Abstract

A method performed by a user equipment (UE) for requesting an on-demand (OD)-system information block 1 (SIB1) is provided. The method receives, from a first cell, an uplink-wake-up signal (UL-WUS) configuration. The method transmits, to the first cell or a second cell, a WUS for requesting a target SIB1 based on the UL-WUS configuration. The method receives, from the first cell or the second cell, a response associated with WUS. The method receives, from the first cell or the second cell, the target SIB1 in response to receiving the response.

Description

METHOD AND APPARATUS FOR REQUESTING ON-DEMAND-SYSTEM INFORMATION BLOCK 1

[0001] The present disclosure is related to wireless communication and, more specifically, to a User Equipment (UE), Base Station (BS), and method for requesting an on-demand (OD)-system information block 1 (SIB1) in the wireless communication networks.

[0002] Various efforts have been made to improve different aspects of wireless communication for the cellular wireless communication systems, such as the 5thGeneration (5G) New Radio (NR), by improving data rate, latency, reliability, and mobility. The 5G NR system is designed to provide flexibility and configurability to optimize network services and types, accommodating various use cases, such as enhanced Mobile Broadband (eMBB), massive Machine-Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC). As the demand for radio access continues to grow, however, there exists a need for further improvements in the next-generation wireless communication systems, such as improvements in a beam management procedure.

[0003] The present disclosure is related to a UE, a BS, and a method for requesting an on-demand (OD)-system information block 1 (SIB1) in the wireless communication networks.

[0004] In a first aspect of the present disclosure, a UE for requesting an on-demand (OD)-system information block 1 (SIB1) is provided. The UE includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The computer-executable instructions, when executed by the at least one processor, cause the UE to: receive, from a first cell, an uplink-wake-up signal (UL-WUS) configuration; transmit, to the first cell or a second cell, a WUS for requesting a target SIB1 based on the UL-WUS configuration; receive, from the first cell or the second cell, a response associated with WUS; and receive, from the first cell or the second cell, the target SIB1 in response to receiving the response.

[0005] In some implementations of the first aspect, transmitting, to the first cell or the second cell, the WUS includes transmitting, to the second cell, the WUS; receiving, from the first cell or the second cell, the response includes receiving, from the second cell, the response; receiving, from the first cell or the second cell, the target SIB1 includes receiving, from the second cell, the target SIB 1, and the target SIB1 is associated with the second cell.

[0006] In some implementations of the first aspect, receiving, from the first cell, the UL-WUS configuration includes receiving, from the first cell of a first mode, the UL-WUS configuration; transmitting, to the first cell or the second cell, the WUS includes transmitting, to the first cell of a second mode, the WUS; receiving, from the first cell or the second cell, the response includes receiving, from the first cell of the second mode, the response; receiving, from the first cell or the second cell, the target SIB1 includes receiving, from the first cell of the second mode, the target SIB1; the target SIB1 is associated with the first cell of the second mode, and the second mode includes a network energy saving (NES) mode.

[0007] In some implementations of the first aspect, transmitting, to the first cell or the second cell, the WUS includes transmitting, to the first cell, the WUS; receiving, from the first cell or the second cell, the response includes receiving, from the first cell, the response; receiving, from the first cell or the second cell, the target SIB1 includes receiving, from the first cell, the target SIB1; and the target SIB1 is associated with the second cell.

[0008] In some implementations of the first aspect, transmitting, to the first cell or the second cell, the WUS includes transmitting, to the first cell, the WUS; receiving, from the first cell or the second cell, the response includes receiving, from the first cell, the response; receiving, from the first cell or the second cell, the target SIB1 includes receiving, from the second cell, the target SIB1, and the target SIB1 is associated with the second cell.

[0009] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: determine, based on a network identity (ID) included in the UL-WUS configuration, whether to transmit to the first cell or the second cell, the WUS, and the network ID includes a public land mobile network (PLMN) ID, a standalone non-public network (SNPN) ID, or a closed access group (CAG) ID associated with the first cell or the second cell.

[0010] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: determine, based on the network ID included in the UL-WUS configuration associated with the first cell or the second cell, whether the first cell or the second cell is a suitable cell or an acceptable cell.

[0011] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: store the target SIB1 after receiving the target SIB1; determine, based on a pre-define period, whether the stored SIB 1 is valid; determine that the stored SIB 1 is valid during the pre-define period; and determine that the stored SIB 1 is invalid and release the stored SIB 1 after the pre-define period.

[0012] In a second aspect of the present disclosure, a method performed by a user equipment (UE) for requesting an on-demand (OD)-system information block 1 (SIB1) is provided. The method includes: receiving, from a first cell, an uplink-wake-up signal (UL-WUS) configuration; transmitting, to the first cell or a second cell, a WUS for requesting a target SIB1 based on the UL-WUS configuration; receiving, from the first cell or the second cell, a response associated with WUS; and receiving, from the first cell or the second cell, the target SIB1 in response to receiving the response.

[0013] In a third aspect of the present application, a BS for managing an on-demand (OD)-system information block 1 (SIB1) request is provided. The BS includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The computer-executable instructions, when executed by the at least one processor, cause the BS to: transmit, via a first cell, an uplink-wake-up signal (UL-WUS) configuration; receive, via the first cell or a second cell, a WUS for requesting a target SIB1 based on the UL-WUS configuration; transmit, via the first cell or the second cell, a response associated with WUS; and transmit, via the first cell or the second cell, the target SIB1 in response to transmitting the response.

[0014] In some implementations of the third aspect, receiving, via the first cell or the second cell, the WUS includes receiving, via the second cell, the WUS; transmitting, via the first cell or the second cell, the response includes transmitting, via the second cell, the response; transmitting, via the first cell or the second cell, the target SIB 1 includes transmitting, via the second cell, the target SIB 1; and the target SIB1 is associated with the second cell.

[0015] In some implementations of the third aspect, transmitting, via the first cell, the UL-WUS configuration includes transmitting, via the first cell of a first mode, the UL-WUS configuration; receiving, via the first cell or the second cell, the WUS includes receiving, via the first cell of a second mode, the WUS; transmitting, via the first cell or the second cell, the response includes transmitting, via the first cell of the second mode, the response; transmitting, via the first cell or the second cell, the target SIB1 includes transmitting, via the first cell of the second mode, the target SIB1; the target SIB1 is associated with the first cell of the second mode, and the second mode includes a network energy saving (NES) mode.

[0016] In some implementations of the third aspect, receiving, via the first cell or the second cell, the WUS includes receiving, via the first cell, the WUS; transmitting, via the first cell or the second cell, the response includes transmitting, via the first cell, the response; transmitting, via the first cell or the second cell, the target SIB1 includes transmitting, via the first cell, the target SIB1; and the target SIB1 is associated with the second cell.

[0017] In some implementations of the third aspect, receiving, via the first cell or the second cell, the WUS includes receiving, via the first cell, the WUS; transmitting, via the first cell or the second cell, the response includes transmitting, via the first cell, the response; transmitting, via the first cell or the second cell, the target SIB1 includes transmitting, via the second cell, the target SIB1; and the target SIB1 is associated with the second cell.

[0018] In some implementations of the third aspect, the UL-WUS configuration includes a network identity (ID), and the network ID includes a public land mobile network (PLMN) ID, a standalone non-public network (SNPN) ID, or a closed access group (CAG) ID associated with the first cell or the second cell.

[0019] Aspects of the present disclosure are best understood from the following detailed disclosure when read with the accompanying drawings. Various features are not drawn to scale. Dimensions of various features may be arbitrarily increased or reduced for clarity of discussion.

[0020] FIG. 1 is a diagram illustrating a multi-carrier scenario, according to an example implementation of the present disclosure.

[0021] FIG. 2 is a diagram illustrating a standalone scenario, according to an example implementation of the present disclosure.

[0022] FIG. 3 is a diagram illustrating a network list of the Cell A and a network list of the NES Cell, according to an example implementation of the present disclosure.

[0023] FIG. 4 is a diagram illustrating a mapping relationship between a network identity list and a bitmap, according to an example implementation of the present disclosure.

[0024] FIG. 5 is a diagram illustrating an on-demand SIB1 request procedure, according to an example implementation of the present disclosure.

[0025] FIG. 6 is a flowchart illustrating a method / process performed by a UE for requesting an on-demand (OD)-system information block 1 (SIB1), according to an example implementation of the present disclosure.

[0026] FIG. 7 is a flowchart illustrating a method / process performed by a BS for managing an on-demand (OD)-system information block 1 (SIB1) request, according to an example implementation of the present disclosure.

[0027] FIG. 8 is a block diagram illustrating a node for wireless communication, according to an example implementation of the present disclosure.

[0028] Some of the abbreviations used in the present disclosure include: Abbreviation　　　　Full name 3GPP　　　　3rdGeneration Partnership Project 5G　　　　5thGeneration 5GC　　　　5G Core ARFCN　　　　Absolute Radio-Frequency Channel Number AS　　　　Access Stratum BS　　　　Base Station BWP　　　　Bandwidth Part CA　　　　Carrier Aggregation CAG　　　　Closed Access Group CN　　　　Core Network CU　　　　Central Unit DAPS　　　　Dual Active Protocol Stack DC　　　　Dual Connectivity DCI　　　　Downlink Control Information DL　　　　Downlink DU　　　　Distributed Unit E-UTRA(N)　　　　Evolved Universal Terrestrial Radio Access (Network) EN-DC　　　　E-UTRA NR Dual Connectivity EPC　　　　Evolved Packet Core FR　　　　Frequency Range IAB　　　　Integrated Access and Backhaul ID　　　　Identifier IE　　　　Information Element LAN　　　　Local Area Network LTE　　　　Long Term Evolution MAC　　　　Medium Access Control MAC CE　　　　MAC Control Element MCG　　　　Master Cell Group MIB　　　　Master Information Block MN　　　　Master Node MSG　　　　Message MT　　　　Mobile Termination NAS　　　　Non-Access Stratum NE-DC　　　　NR - E-UTRA Dual Connectivity NES　　　　Network Energy Saving NPN　　　　Non-Public Network NR　　　　New Radio NR-U　　　　NR Unlicensed NW　　　　Network NSSAI　　　　Network Slice Selection Assistance Information PCell　　　　Primary Cell PCI　　　　Physical Cell Identity PDCCH　　　　Physical Downlink Control Channel PDSCH　　　　Physical Downlink Shared Channel PDU　　　　Protocol Data Unit PHY　　　　Physical (layer) PLMN　　　　Public Land Mobile Network PNI-NPN　　　　Public Network Integrated Non-Public Network PRACH　　　　Physical Random Access Channel PSCell　　　　Primary SCG Cell / Primary Secondary Cell PUCCH　　　　Physical Uplink Control Channel PUSCH　　　　Physical Uplink Shared Channel RA　　　　Random Access RAN　　　　Radio Access Network RAR　　　　Random Access Response RAT　　　　Radio Access Technology RF　　　　Radio Frequency RNTI　　　　Radio Network Temporary Identifier RRC　　　　Radio Resource Control RS　　　　Reference Signal RSRP　　　　Reference Signal Received Power SCell　　　　Secondary Cell SCG　　　　Secondary Cell Group SI　　　　System Information SIB　　　　System Information Block SL　　　　Sidelink SN　　　　Secondary Node SNPN　　　　Stand-alond Non-Public Network SSB　　　　Synchronization Signal Block TS　　　　Technical Specification UE　　　　User Equipment UL　　　　Uplink V2X　　　　Vehicle-to-Everything WUS　　　　Wake-Up-Signal / Wake-Up-Signaling

[0029] The following contains specific information related to implementations of the present disclosure. The drawings and their accompanying detailed disclosure are merely directed to implementations. However, the present disclosure is not limited to these implementations. Other variations and implementations of the present disclosure will be obvious to those skilled in the art.

[0030] Unless noted otherwise, like or corresponding elements among the drawings may be indicated by like or corresponding reference numerals. Moreover, the drawings and illustrations in the present disclosure are generally not to scale and are not intended to correspond to actual relative dimensions.

[0031] For the purposes of consistency and ease of understanding, like features may be identified (although, in some examples, not illustrated) by the same numerals in the drawings. However, the features in different implementations may be different in other respects and may not be narrowly confined to what is illustrated in the drawings.

[0032] References to “one implementation,” “an implementation,” “example implementation,” “various implementations,” “some implementations,” “implementations of the present application,” etc., may indicate that the implementation(s) of the present application so described may include a particular feature, structure, or characteristic, but not every possible implementation of the present application necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “In some implementations,” or “in an example implementation,” “an implementation,” do not necessarily refer to the same implementation, although they may. Moreover, any use of phrases like “implementations” in connection with “the present application” are never meant to characterize that all implementations of the present application must include the particular feature, structure, or characteristic, and should instead be understood to mean “at least some implementations of the present application” includes the stated particular feature, structure, or characteristic. The term “coupled” is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to physical connections. The term “comprising,” when utilized, means “including, but not necessarily limited to”; it specifically indicates open-ended inclusion or membership in the so-described combination, group, series, and the equivalent.

[0033] The expression “at least one of A, B and C” or “at least one of the following: A, B and C” means “only A, or only B, or only C, or any combination of A, B and C.” The terms “system” and “network” may be used interchangeably. The term “and / or” is only an association relationship for describing associated objects and represents that three relationships may exist such that A and / or B may indicate that A exists alone, A and B exist at the same time, or B exists alone. The character “ / ” generally represents that the associated objects are in an “or” relationship.

[0034] For the purposes of explanation and non-limitation, specific details, such as functional entities, techniques, protocols, and standards, are set forth for providing an understanding of the disclosed technology. In other examples, detailed disclosure of well-known methods, technologies, systems, and architectures are omitted so as not to obscure the present disclosure with unnecessary details.

[0035] Persons skilled in the art will immediately recognize that any network function(s) or algorithm(s) disclosed may be implemented by hardware, software, or a combination of software and hardware. Disclosed functions may correspond to modules which may be software, hardware, firmware, or any combination thereof.

[0036] A software implementation may include computer executable instructions stored on a computer-readable medium, such as memory or other type of storage devices. One or more microprocessors or general-purpose computers with communication processing capability may be programmed with corresponding executable instructions and perform the disclosed network function(s) or algorithm(s).

[0037] The microprocessors or general-purpose computers may include Application-Specific Integrated Circuits (ASICs), programmable logic arrays, and / or one or more Digital Signal Processor (DSPs). Although some of the disclosed implementations are oriented to software installed and executing on computer hardware, alternative implementations implemented as firmware, as hardware, or as a combination of hardware and software are well within the scope of the present disclosure. The computer-readable medium includes but is not limited to Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash memory, Compact Disc Read-Only Memory (CD-ROM), magnetic cassettes, magnetic tape, magnetic disk storage, or any other equivalent medium capable of storing computer-readable instructions.

[0038] A radio communication network architecture such as a Long-Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a 5G NR Radio Access Network (RAN) typically includes at least one base station (BS), at least one UE, and one or more optional network elements that provide connection within a network. The UE communicates with the network such as a Core Network (CN), an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial RAN (E-UTRAN), a 5G Core (5GC), a 6G Core (6GC), or an internet via a RAN established by one or more BSs.

[0039] A UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. The UE may be a portable radio equipment that includes, but is not limited to, a mobile phone, a tablet, a wearable device, a sensor, a vehicle, or a Personal Digital Assistant (PDA) with wireless communication capability. The UE is configured to receive and transmit signals over an air interface to one or more cells in a RAN.

[0040] The BS may be configured to provide communication services according to at least a Radio Access Technology (RAT) such as Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM) that is often referred to as 2G, GSM Enhanced Data rates for GSM Evolution (EDGE) RAN (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunication System (UMTS) that is often referred to as 3G based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), LTE, LTE-A, evolved LTE (eLTE) that is LTE connected to 5GC, NR (often referred to as 5G), and / or LTE-A Pro. However, the scope of the present disclosure is not limited to these protocols.

[0041] The BS may include, but is not limited to, a node B (NB) in the UMTS, an evolved node B (eNB) in LTE or LTE-A, a radio network controller (RNC) in UMTS, a BS controller (BSC) in the GSM / GERAN, an ng-eNB in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS in connection with 5GC, a next generation Node B (gNB) in the 5G-RAN, or any other apparatus capable of controlling radio communication and managing radio resources within a cell. The BS may serve one or more UEs via a radio interface. Although the gNB is used as an example in some implementations within the present disclosure, it should be noted that the disclosed implementations may also be applied to other types of base stations.

[0042] The BS may be operable to provide radio coverage to a specific geographical area using multiple cells forming the RAN. The BS may support the operations of the cells. Each cell may be operable to provide services to at least one UE within its radio coverage.

[0043] Each cell (may often referred to as a serving cell) may provide services to one or more UEs within the cell’s radio coverage, such that each cell schedules the DL (and optionally UL resources) to at least one UE within its radio coverage for DL (and optionally UL packet transmissions from the UE). The BS may communicate with one or more UEs in the radio communication system via the cells.

[0044] A cell may allocate sidelink (SL) resources for supporting the Proximity Services (ProSe) or Vehicle to Everything (V2X) services. Each cell may have overlapped coverage areas with other cells.

[0045] In Multi-RAT Dual Connectivity (MR-DC) cases, the primary cell of a Master Cell Group (MCG) or a Secondary Cell Group (SCG) may be referred to as a Special Cell (SpCell). A Primary Cell (PCell) may include the SpCell of an MCG. A Primary SCG Cell (PSCell) may include the SpCell of an SCG. MCG may include a group of serving cells associated with the Master Node (MN), including the SpCell and optionally one or more Secondary Cells (SCells). An SCG may include a group of serving cells associated with the Secondary Node (SN), including the SpCell and optionally one or more SCells.

[0046] As discussed above, the frame structure for NR may support flexible configurations for accommodating various next generation (e.g., 5G) communication requirements, such as Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC), while fulfilling high reliability, high data rate, and low latency requirements. The Orthogonal Frequency-Division Multiplexing (OFDM) technology in the 3GPP may serve as a baseline for an NR waveform. The scalable OFDM numerology, such as adaptive sub-carrier spacing, channel bandwidth, and Cyclic Prefix (CP), may also be used.

[0047] Two coding schemes may be considered for NR, specifically, Low-Density Parity-Check (LDPC) code and Polar Code. The coding scheme adaption may be configured based on channel conditions and / or service applications.

[0048] At least the DL transmission data, a guard period, and UL transmission data should be included in a transmission time interval (TTI) of a single NR frame. The respective portions of the DL transmission data, the guard period, and the UL transmission data should also be configurable based on, for example, the network dynamics of NR. SL resources may also be provided in an NR frame to support ProSe services or V2X services.

[0049] Any two or more than two of the following paragraphs, (sub)-bullets, points, actions, behaviors, terms, or claims described in the present disclosure may be combined logically, reasonably, and properly to form a specific method.

[0050] Any sentence, paragraph, (sub)-bullet, point, action, behaviors, terms, or claims described in the present disclosure may be implemented independently and separately to form a specific method.

[0051] Dependency, e.g., “based on”, “more specifically”, “preferably”, “in one embodiment”, “in some implementations”, etc., in the present disclosure is just one possible example which would not restrict the specific method.

[0052] In some implementations, all the designs / embodiment / implementations introduced within this disclosure are not limited to be applied for dealing with the problems discussed within this disclosure. For example, the described embodiments may be applied to solve other problems that exist in the RAN of wireless communication systems. In some implementations, all of the numbers listed within the designs / embodiment / implementations introduced within this disclosure are just examples and for illustration, for example, of how the described methods are executed.

[0053] The term “A and / or B” within the present disclosure means “A”, “B”, or “A and B”. The term “A and / or B and / or C” within the present disclosure means “A”, “B”, “C”, “A and B”, “A and C”, “B and C”, or “A and B and C”. The term “A / B” within the present disclosure means “A” or “B”.

[0054] FIG. 1 is a diagram illustrating a multi-carrier scenario, according to an example implementation of the present disclosure. In FIG. 1, the Cell#1 may work as an anchor cell / Cell A in the multi-carrier scenario. In the present disclosure, the Cell A may be defined as the cell which may broadcast its system information (e.g., SIB1, SIB2-SIB5, or other system information) periodically. The Cell#2-Cell#4 may be defined as Network Energy Saving (NES) cells in the present disclosure. The Cell#2-Cell#4 may be operated on different component carriers (e.g., the Cell#2-Cell#4 may operate on the CC#2-CC#4 respectively).

[0055] In some implementations, the (DL / UL) radio coverage of the NES Cells (e.g., Cell#2-Cell#4) may (partially) overlap with the Cell A (e.g., the Cell#1). In some implementations, the (DL / UL) radio coverage of the NES Cells may not overlap with the Cell A for the UE to support the on-demand SIB1 request procedure. In some implementations, the NES Cell may also be known as non-anchor cell, which may mean that the cell may not transmit its system information (e.g., MIB, SIB1, SIB2-SIB5, or other SI) periodically or its system information broadcasting may be limited in a (one shot) time period or a periodical time pattern / cycle.

[0056] FIG. 2 is a diagram illustrating a standalone scenario, according to an example implementation of the present disclosure. In some implementations, the Cell A (e.g., the Cell#A) may not overlap with the NES Cell (e.g., the Cell#B) or the overlapped area between the Cell#A and the Cell#B may be neglectable (e.g., in this condition, the UE may only be capable to camp on both the Cell#A and the Cell#B in the overlapped area. In contrast, the UE may need to switch its camped cell from Cell#A to Cell#B or vice versa). In FIG. 2, the Cell#A (e.g., which acts as an anchor cell) and the Cell#B (e.g., which acts as an (non-anchor) NES Cell) may also support network energy saving function.

[0057] In some implementations, the NES Cell may also be configured to support the on-demand SIB1 request procedure associated with the neighbor cells or other cells in the same radio access network. In some implementations, the NES Cell which also supports the SIB1 transmission of other cells may be defined as “Cell A” (for the simplification of discussion, the “Cell A’” may be used in the present disclosure). In some implementations, the Cell A’ may also transmit its own SIB1 via an on-demand manner (e.g., based on the NES Cell behavior as described in the present disclosure). The Cell A’ may also support the on-demand SIB1 service of other cells in the RAN. In some implementations, a “NES cell” may be configured as a mode or type to a cell and so the UE may switch between a “NES mode” or “cell A” mode at different timing. In some implementations, both modes may not be activated / implemented to one cell simultaneously. In some implementations, both Cell A and Cell A’ may be deployed / configured in a RAN to support on-demand SIB1 service. Some system-level issues may be addressed for the Core Network (CN), the Radio Access Network (RAN), and the User Equipment (UE).

[0058] In some implementations, the UE may camp on a cell (e.g., an anchor cell, Cell A, Cell_A, or Cell A’) first. Then, the Cell_A may be capable of providing the system information of the neighbor (NES) cell(s) observed / detected / found by the UE.

[0059] In some implementations, the Cell A / Cell A’ (e.g., the Cell#1 as illustrated in FIG. 1 or the Cell#A as illustrated in FIG. 2) may be an accessible cell for the UE, which may mean that the Cell_A may transmit / deliver / broadcast the system information to UE even if the Cell_A is just an acceptable cell for the UE (or the UE has not yet determined the cell type of the Cell A ). In some implementations, the UE may be allowed to initiate an on-demand SIB1 request procedure, transmit a WUS, or initiate a WUS transmission with an acceptable cell (e.g., Cell A / Cell A’). In some implementations, the UE may only be allowed to initiate an on-demand SIB1 request procedure with a suitable cell. In some implementations, the UE may not be allowed to initiate a no-demand SIB1 request procedure with an acceptable cell.

[0060] In some implementations, the definitions of the acceptable cell and the suitable cell may be referred to the definitions of the acceptable cell and the suitable cell as specified in the 3GPP TS.

[0061] In some implementations, the Cell_A may have to be a suitable cell for the UE to support the on-demand SIB1 delivery service. In some implementations, the UE may not be allowed to transmit an on-demand SIB1 request message (e.g., by using wake-up signaling, such as the waveform same with preamble used for random access procedure in NR / E-UTRA protocols or using signaling transmitted via the PUCCH, PUSCH, SR configured by the serving RAN) to the camped cell if the cell is an acceptable cell for the UE (e.g., the UE may receive synchronization signal burst / PBCH from an acceptable cell).

[0062] In some implementations, the on-demand SIB1 request procedure (and / or WUS configuration provision) may be considered as a service that can be supported only by a suitable cell.

[0063] In some implementations, the Cell A / A’ may be an acceptable cell for the UE. The UE may still be enabled / allowed to initiate an on-demand SIB1 request procedure associated with the Cell A / Cell A’, even when the cell is only an acceptable cell for the UE. In other words, the on-demand SIB1 request procedure or the SIB acquisition may be considered as a service that can be supported by an acceptable cell.

[0064] In some implementations, the Cell A may support one or more PLMNs, and the NES Cell may also support one or more PLMNs.

[0065] Both Cell A / A’ and NES Cell may deliver / transmit / broadcast the network identities (e.g., PLMN IDs) supported by the Cell A / A’ and NES Cell respectively. However, to an NES Cell, the UE may not know the networks supported by the NES Cell unless the UE obtain the system information of the target NES Cell.

[0066] In some implementations, the UE may need to obtain the information about the network(s)(e.g., PLMN / SNPN) supported by a target NES Cell before the UE initiates the on-demand SIB1 procedure to request the SIB1 of the target NES Cell. In some implementations, the Cell A / A’ may need to broadcast the network ID (e.g., PLMN ID, SNPN ID, and / or CAG ID) supported by one or more NES Cells to the UE. In other words, the UE may need to determine the cell type of the target NES Cell (e.g., an acceptable cell, a suitable cell, or an accessible cell).

[0067] In some implementations, the Cell A may need to provide the information about the networks supported by one or more NES Cells (e.g., supported by the concerned Cell A for on-demand SIB1) via implicit approach or via explicit signaling.

[0068] In some implementations, the Cell A and supported NES Cell may belong to the same network (e.g., same PLMN / SNPN). In some implementations, all of the networks supported by the Cell A may also be supported by the NES Cells supported by the concerned Cell A (e.g., for on-demand SIB1 request procedure). In other words, the UE may receive / obtain / refer / store the NW information about the networks supported by the NES Cell based on the network list supported and transmitted by the serving Cell A. In addition, the UE may determine whether the NES Cell is a suitable cell or an acceptable cell based on the cell type of Cell A. For example, if the Cell A is a suitable cell for the UE, the UE may determine that the NES Cells supported by Cell A are also suitable cells for the UE even if the UE has not yet obtained the SIB1 of those NES Cells. If the Cell A is an acceptable cell for the UE, the UE may determine that the NES Cells supported by Cell A are also acceptable cells for the UE even if the UE has not yet obtained the SIB1 of those NES Cells.

[0069] In some implementations, the first NW ID shown in the network identity list of the Cell A may be a default NW for the NES Cells supported by the Cell A. In other words, the NES cells supported by the Cell A may, by default, support the network shown in the network identity list (e.g., PLMN list, SNPN list supported by the Cell A). In some implementations, the default NW of the NES Cell may be the only NW supported by the NES Cell.

[0070] In some implementations, the Cell A / A’ may indicate the NW identity list supported by the NES Cell to the UEs directly (e.g., via the broadcasting SIB or the UE-specific control signaling, along with the PCI of the cell A / A’ itself or some or all NES Cells supported by the concerned Cell A / A’).

[0071] In some implementations, the NES Cell may belong to the PLMN(s) supported by the Cell A. In some implementations, the NW list (e.g., PLMN ID list / SNPN ID list) supported by the Cell A may partially overlap with the NW list supported by the NES Cell, as illustrated in FIG. 3. FIG. 3 is a diagram illustrating a network list of the Cell A and a network list of the NES Cell, according to an example implementation of the present disclosure. In some implementations, an additional bitmap may be configured by the Cell A (e.g., as part of the on-demand SIB1 request configuration or part of the WUS configuration). The additional bitmap may inform the UE of the NW(s) supported by the one or more NES Cells. The NES Cells may be supported by the Cell A.

[0072] In some implementations, the NES Cell may also provide a bitmap to indicate which NW is supported by the NES Cell based on the NW ID list (e.g., PLMN ID list / SNPN ID list) supported by the Cell A (e.g., that supports the NES Cell for SIB1 enquiry).

[0073] In some implementations, the NES Cell may indicate the target Cell A information that supports the NES Cell. For example, the NES Cell may broadcast the PCI and / or the operating frequency carrier of the target cell A in the MIB or the broadcasting system information (e.g., the SIB1 of the NES Cell).

[0074] In some implementations, the Cell A may provide information (e.g., a bitmap) to inform the NWs supported by the NES Cell(s). In addition, a NW ID (e.g., PLMN ID, SNPN ID) in the network identity list may have a one-to-one mapping relationship with each bit of the bitmap (e.g., following the ascending order). The bit value “1” or “true” may mean that the associated NW is also supported by the NES Cell. The bit value “0” or “false” may mean that the associated NW is not supported by the NES Cell. FIG. 4 is a diagram illustrating a mapping relationship between a network identity list and a bitmap, according to an example implementation of the present disclosure. To support RAN sharing scenario, a cell may support one or more networks (e.g., PLMN, SNPN, or CAG). In some implementations, each network may be configured with an explicit identifier (e.g., PLMN ID / SNPN ID / CAG ID respectively, which are configured by serving RAN explicitly). In some implementations, each network may be associated with an implicit indicator. For example, the first PLMN shown in the network identity list , which may be configured by the RAN via SIB1 transmission, may be determined by the UE as the first network (with an implicit ID PLMN ID#1 determined by the UE) and so the second PLMN shown in the network identity list may be determined by the UE as the second network (with an implicit ID PLMN ID#2 determined by the UE). So, the UE may determine / identify the remaining networks provided in the same network identity list based on the descending order. Based on this given rule (pre-defined by the technical specification or pre-configured by the serving RAN), the serving RAN (e.g., Cell A) may configure the bitmap to inform the NWs supported by the NES Cell(s).

[0075] As shown in FIG. 4, the PLMN ID#1-PLMN ID#4 may be determined by the UE via the implicit / explicit rules. Then, each network may be further associated a bit in the bitmap (e.g., PLMN ID#1 is associated with the first bit, which is shown as the Bit#1 in the bitmap and the PLMN ID#2 is associated with the second bit, which is shown as the Bit#2 in the bitmap) and so the UE may determine the network supported by a target NES cell selected by the UE based on the bitmap. In some implementations, an NES Cell may be associated with a unique bitmap and so all of the networks associated with the bitmap may be supported by the NES Cell. An NES Cell may be configured to be associated with a specific NW_Bitmap (e.g., Physical cell identity to NW_Bitmap association). In some implementations, one NW_Bitmap may be explicitly configured with one or more cell identity lists (e.g., PCI list) of NES cells. In some implementations, each NES Cell may be configured with the network index list (e.g. PLMN ID#1 / PLMN ID#2) to indicate supported by the NES Cell directly without the bitmap. In some implementations, a bitmap may be common / shared by all of the NES cells configured in the same UL-WUS configuration. In some implementations, a bitmap may be applicable across different UL-WUS configurations, where each UL-WUS configuration may be associated with an NES cell). In some implementations, the proposed methods may not be limited to PLMN but also be applicable to other network types (e.g., SNPN, CAG) and the combinations of different network types.

[0076] In some implementations, an NES Cell may be uniquely associated with a proposed NW_Bitmap. In some implementations, a NW_Bitmap may be associated with one or more (or all of) the NES Cells supported by the concerned Cell A.

[0077] In some implementations, the UE may store the supported network information associated with the NES Cell(s) (e.g., the UE may store the supported NW list or NW_Bitmap associated with one or more NES Cells) that the UE receives from the Cell A even after the UE re-selects to another Cell A / A’ or another NES Cell. In some implementations, such information (e.g., the supported network information associated with the NES Cell(s)) may be provided by the Cell A (e.g., the Cell#1 as illustrated in FIG. 1) via system information (e.g., via broadcasting SI, on-demand procedure, or UE-specific control signaling). The UE may release (part of) the information not related to the NES Cells and store (part of) the information related to the NES Cells after the UE reselects / camps to another Cells in the serving RAN.

[0078] In some implementations, after a cell reselection from a Cell A (e.g., Cell A1) to another cell, the UE may keep the on-demand SIB1 configuration or the WUS configuration associated with the Cell A1 for a time period. The length of the time period may be configured by a serving RAN (e.g., by counting a timer to zero, where the initial value of the timer may be configured by the serving RAN).

[0079] In some implementations, the supported network information associated with the NES Cell(s) may be removed along with the on-demand SIB1 configuration or the WUS configuration (e.g., after the cell (re)selection). In some implementations, the supported network information associated with the NES Cell(s) may not be removed along with the on-demand SIB1 configuration or the WUS configuration (e.g., after the cell (re)selection). In addition, the UE may store such information as UE-stored information for the cell (re)selection procedure.

[0080] In some implementations, the proposed solutions provided based on the PMNN / PLMN ID may also be applicable to the SNPN / SNPN ID.

[0081] In some implementations, the UE may not obtain the NWs (e.g., the PLMN and / or SNPN) supported by a target NES Cell before the UE successfully obtains the SIB1 of the NES Cell.

[0082] In some implementations, the UE may still be able to camp on the NES Cell for the on-demand SIB1 request procedure.

[0083] In some implementations, the mechanism that allows / enables the UE to camp on the target NES Cell before receiving the network list supported by the target NES Cell may be considered as an NES-specific camping procedure. In some implementations, the NES-specific camping procedure may only be applicable to the (3GPP Release-19) NES-capable UE or the UE that has the UE capability to perform the on-demand SIB1 request procedure (e.g., during the standalone scenario, as illustrated in FIG. 2).

[0084] In some implementations, the UE may determine the target NES Cell as a suitable cell during the NES-specific camping procedure (e.g., even if the UE does not know whether the target cell supports the registered / selected NW of the UE). In some implementations, the UE may determine the target NES Cell as an acceptable cell during the NES-specific camping procedure (e.g., even if the UE does not know whether the target cell supports the registered / selected NW of the UE). In some implementations, the (NES) Cell selected by the UE during the NES-specific camping procedure may be treated as a “selected cell” for the UE, and the UE may not determine the selected cell as a “suitable cell” or an “acceptable cell.

[0085] In some implementations, the UE may determine that its state is a “Camped Normally state” while the UE remains in the NES-specific camping condition / procedure. In some implementations, the UE may determine that its state is a “camped on any cell state” while the UE remains in the NES-specific camping condition / procedure. In some implementations, the UE may determine that its state as a “any cell selection state” while the UE remains in the NES-specific camping condition / procedure.

[0086] In some implementations, after the UE successfully obtains the SIB1 of the target NES Cell (e.g., via the on-demand SIB1 request procedure towards the target cell or the Cell A), the UE may also successfully obtain / access the networks supported by the target NES Cell successfully. In this condition, the UE may need to determine whether the cell is a suitable cell or an acceptable cell for the UE based on the received SIB1. In some implementations, the UE may switch from the NES-specific camping state / procedure to the (conventional) camping state / procedure. In addition, the UE may also need to reconsider whether to move to (or remain in) the camped normally state / camped on any cell state / any cell selection state after the UE obtains and stores the SIB1 successfully.

[0087] In some implementations, the stored SIB1 of a camped NES Cell may become invalid / out of date (e.g., after a time period, where the duration of the time period may be pre-configured by the serving RAN). In this condition, the UE may maintain its state (e.g., camped normally state, camped on any cell state, or any cell selection state). In addition, the UE may not initiate the on-demand SIB1 request procedure towards the camped cell to re-obtain a valid SIB1 if the camped cell is only an acceptable cell for the UE.

[0088] In some implementations, the Cell A may not operate in the SNPN mode to support the on-demand SIB1 procedure. Therefore, the Cell A / A’ may only support the PLMNs. In addition, the neighboring cells (e.g., the Cell#2 / 3 / 4 as illustrated in FIG. 1) may operate in the SNPN access mode.

[0089] In some implementations, the Cell A may operate in the SNPN mode to support the on-demand SIB1 procedure for NES Cells which support the SNPN.

[0090] In some implementations, the Cell A may transmit an explicit indicator (e.g., an SNPN indicator) to the UE to indicate that an NES Cell (or multiple NES Cells) supports the SNPN or the PLMN. To achieve this. One or more cell identities (e.g., PCIs) may be associated with the SNPN indicator.

[0091] In some implementations, the NES Cells may be defined to support the PLMN by default. Otherwise, the SNPN indicator may be provided by the Cell A to further indicate that a concerned NES Cell supports the SNPN.

[0092] In some implementations, an NES Cell may transmit an indicator to UEs to indicate that the NES Cell supports SNPN(s) or PLMN(s). For the NES Cell, such indicator (referred to as the SNPN_indicatorNES) may be transmitted via the MIB of the NES Cell. After detecting the PBCH / MIB broadcasted by the NES Cell, the UE may determine whether it should initiate the on-demand SIB1 request procedure to the target NES Cell. For example, the UE operating in the SNPN access mode may not be allowed to initiate the on-demand SIB1 request procedure (e.g., the WUS transmission to the target NES Cell) if the target cell does not support the SNPN. In other words, the UE operating in the SNPN access mode may be allowed / enabled to initiate the on-demand SIB1 request procedure to the NES Cell only when the UE determines that the target NES Cell supports the SNPN.

[0093] In some implementations, the UE not operating in the SNPN access mode may not be allowed to initiate the on-demand SIB1 request procedure (e.g., the WUS transmission to the target NES Cell) if the target cell supports the SNPN. In other words, the UE not operating in the SNPN access mode may be allowed / enabled to initiate the on-demand SIB1 request procedure to the NES Cell only when the UE determines that the target NES Cell supports the PLMN.

[0094] In some implementations, the cell A that (only) supports the SNPN may only support the NES Cells that (only) support the SNPNs. The Cell A that (only) supports the PLMN may only support the NES Cells that (only) support PLMNs. The UE may determine the NW type supported by the NES Cells based on the NW type supported by the Cell A.

[0095] In some implementations, the information (e.g., the NW type supported by the Cell A, the cell type of the Cell A for the UE, and / or the NES Cells supported by the Cell A) may be stored by the UE as part of the UE’s stored information. The UE may perform the cell (re)selection procedure based on the stored information.

[0096] In other words, the UE operating in the SNPN access mode may not monitor the Cell A (and the NES Cells supported by the Cell A) if the Cell A does not support the SNPN and only supports the PLMN). In some implementations, the UE not operating in the SNPN access mode may not monitor the Cell A (and the NES Cells supported by the Cell A) if the Cell A does not support the PLMN and only supports the SNPN.

[0097] In some implementations, the Cell A / A’ may support only the PLMN and may not support the SNPN. The Cell A / A’ may support the on-demand SIB1 for one or more NES Cells that support one or more SNPNs. In this condition, the Cell A may further indicate the SNPN information associated with those NES Cells to UEs (e.g., via broadcasting system information or UE specific control signaling, such the RRCReconfiguration message or the RRCRelease message).

[0098] In some implementations, the UE operating in the SNPN access mode may still be able / configured / allowed / enabled to camp on the Cell A / A’ for the on-demand SIB1 request procedure even if the Cell A / A’ does not support the SNPN but supports one or more NES Cells that support one or more SNPNs. In this condition, the Cell A / A’ may transmit the SNPN ID(s) supported by the one or more NES Cells to the UE(s) via broadcasting system information (e.g., as part of the WUS configuration or as part of the on-demand SIB1 configuration associated with one or more NES Cells). In some implementations, the Cell A / A’ may transmit the SNPN ID(s) supported by one or more NES Cells (e.g., along with the PCI of those NES Cells) to the UE(s) via UE-specific control signaling (e.g., via the RRC reconfiguration message or the RRC Release message, which instructs the UE to transition from the RRC Connected state to the RRC Inactive / Idle state).

[0099] In some implementations, the UE not operating in the SNPN access mode may still be able / configured / allowed / enabled to camp on the Cell A / A’ for the on-demand SIB1 request procedure if the Cell A / A’ does support the SNPN but supports one or more NES Cells that supports one or more PLMNs. In this condition, the Cell A / A’ may transmit the PLMN ID(s) supported by the one or more NES Cells to the UE(s) via broadcasting system information (e.g., as part of the WUS configuration or as part of the on-demand SIB1 configuration associated with one or more NES Cells). In some implementations, the Cell A / A’ may transmit the PLMN ID(s) supported by one or more NES Cells to the UE(s) via UE-specific control signaling (e.g., via the RRC reconfiguration message or the RRC Release message, which instructs the UE to transition from the RRC Connected state to the RRC Inactive / Idle state).

[0100] In some implementations, the UE may temporarily ignore whether it is operating in the SNPN access mode during the on-demand SIB1 request procedure associated with a Cell A. In some implementations, the UE may temporarily ignore whether it is operating in the SNPN access mode during the on-demand SIB1 request procedure associated with an NES Cell. In some implementations, the UE may be allowed / enabled to initiate the on-demand SIB1 request procedure to the NES Cell / Cell A regardless of whether the UE is operating in the SNPN access mode. In some implementations, the UE may be allowed / enabled to initiate the on-demand SIB1 request procedure to the NES Cell / Cell A regardless of whether the receiving entity of the WUS transmission supports the SNPN or the PLMN.

[0101] In some implementations, the UE may not know the cell type (e.g., whether the cell is an accessible cell or a suitable cell) of the NES Cell for the UE before the UE obtains the system information (e.g., the SIB1) successfully. In this condition, the UE may determine the NES Cell as an “acceptable cell” or a “suitable cell” for the UE before the UE obtains the target SIB1 associated with the target NES Cell.

[0102] In some other implementations, the UE may obtain the networks supported by an NES Cell with the assistance from another Cell (e.g., the Cell#1 acting as an anchor cell as illustrated in FIG. 1). Based on this information, the UE may understand / determine the NES Cell’s cell type for the UE (e.g., an acceptable cell or a suitable cell).

[0103] In some implementations, the UE may initiate the on-demand SIB1 request procedure associated with the target NES Cell (e.g., the UE may transit the WUS to the NES Cell directly for the on-demand SIB1 request) only when the target NES Cell is a suitable cell for the UE. In some implementations, this may mean that the UE may need to know the networks supported by the NES Cell (e.g., the PLMN ID(s), the SNPN ID(s), the CAG ID(s)) before the UE initiates the on-demand SIB1 request procedure with the target NES Cell.

[0104] In some implementations, the UE may initiate the on-demand SIB1 request procedure associated with the target NES Cell (e.g., the UE may transmit the WUS to the NES Cell directly for the on-demand SIB1 request) when the target NES Cell is an acceptable cell for the UE. In this scenario, the UE may know the networks supported by the NES Cell (e.g., the PLMN ID(s), the SNPN ID(s), the CAG ID(s)) before the UE initiates the on-demand SIB1 request procedure with the target NES Cell. In some implementations, the UE may not know the networks supported by the NES Cell (e.g., the PLMN ID(s), the SNPN ID(s), the CAG ID(s)) before the UE initiates the on-demand SIB1 request procedure with the target NES Cell.

[0105] In some implementations, the UE may initiate the on-demand SIB1 request procedure associated with the target NES Cell (e.g., the UE may transmit the WUS to the NES Cell directly for the on-demand SIB1 request) without having information about the networks supported by the target NES Cell (e.g., the PLMN ID(s), the SNPN ID(s), the CAG ID(s)). In some implementations, it may mean that the target NES may be neither an acceptable cell nor a suitable cell for the UE. In some implementations, after the UE obtains the SIB1 associated with the target NES Cell, the UE may determine / identify whether the target NES Cell is an acceptable Cell or suitable cell for the UE.

[0106] In some implementations, the UE may be barred by the NES Cell. If the UE is barred by the NES Cell, the UE may not initiate the on-demand SIB1 request procedure for a time period (e.g., a barring time period). In addition, the UE may determine the duration of the barring time period based on the value of the timer T390’. The value of timer T390’ may be configured based on the following formula: T390’ = (0.7+ 0.6 * rand) * uac-BarringTime.

[0107] In some implementations, the UE may successfully obtain the SIB1 of a target NES Cell via an on-demand SIB1 request procedure (or via UE-specific control signaling). The UE may determine that the received SIB1 is valid within a default valid period of the received SIB1, and the UE may store and maintain the SIB1 during the default valid period.

[0108] In some implementations, the default valid period of the SIB1 may be pre-defined in the 3GPP TS (e.g., 3 hours or 180 minutes). For example, the UE may store the received SIB1 for up to 180 minutes after the UE successfully receives the SIB1. After 180 minutes (e.g., the default valid period), the UE may drop / release the stored SIB1.

[0109] In some implementations, the UE may not try to update the stored SIB1 automatically during the default valid period of the stored SIB1.

[0110] In some implementations, the serving RAN may further configure the valid SIB1 period of the SIB1 along with the target SIB1 (e.g., during the on-demand SIB1 request procedure or upon the reception of the same UE-specific control signaling). The UE may store the received SIB1 (and start counting the valid period of the SIB1 down to zero) for as long as the valid SIB1 period after the UE successfully receives the SIB1. After valid SIB1 period, the UE may drop / release the stored SIB1.

[0111] In some implementations, the serving RAN (e.g., the camped Cell A or the camped NES Cell) may transmit one or more explicit instructions to further instruct the UE to initiate another on-demand SIB1 request procedure when the stored SIB1 becomes invalid. In some implementations, the serving RAN (e.g., the camped Cell A or the camped NES Cell) may transmit one or more explicit instructions to further instruct the UE not to initiate another on-demand SIB1 request procedure when the stored SIB1 becomes invalid. In some implementations, the one or more explicit instructions may be transmitted along with the SIB1 reception procedure. In some implementations, the one or more explicit instructions may not be transmitted along with the SIB1 reception procedure. In some implementations, such instructions may be broadcasted via system information or short messages during the paging message transmission.

[0112] The information on cell access restrictions associated with Access Categories and Identities may be broadcast in SIB1 as part of Unified Access Control as specified in the 3GPP TS 38.331.

[0113] The UE may ignore the Access Category and Identity-related cell access restrictions for the cell reselection. The change of the indicated access restriction may not trigger the cell reselection by the UE.

[0114] In some implementations, the UE may determine the Access Category and Identity-related cell access restrictions for the NAS-initiated access attempts, the RNAU / TAU, and the on-demand SIB1 request procedure (e.g., as specified in the 3GPP TS 38.331). The L2 U2N Relay UE may not need to perform the Unified Access Control as specified in the 3GPP TS 38.331, due to the U2N Remote UE access attempt.

[0115] In some implementations, the UE may not implement / apply the unified access control (UAC) when initiating the on-demand SIB1 request procedure. In some implementations, the serving RAN may indicate that whether the UAC mechanism is applied. The on-demand SIB1 request procedure may be performed only when the UAC result is not “barred,” or the UE may initiate the on-demand SIB1 request procedure without applying the UAC.

[0116] In some implementations, the UAC mechanism may be applied to the on-demand SIB1 request procedure associated with the Cell A or / and the NES Cell.

[0117] In some implementations, the UE may initiate the on-demand SIB1 request procedure due to mobile-initiated / mobile-originated traffic. In this condition, the UE may be configured with a given access category and one or more access identities.

[0118] In some implementations, the UE may determine whether to initiate the on-demand SIB1 request procedure based on the access category / access identities provided by the NAS layer, which may also serve as the triggering event for the on-demand SIB1 request procedure.

[0119] In some implementations, the UE may determine the on-demand SIB1 request procedure as an access attempt. Therefore, the on-demand SIB1 request procedure may be barred for the UE if the UAC result is “barred” for the UE.

[0120] In some implementations, the UE may need to follow / obey the unified access control (UAC) mechanism associated with Cell A / A’ if the UE initiates the on-demand SIB1 request procedure associated with the Cell A / A’ (e.g., the Cell#1 as illustrated in FIG. 1, or the Cell#A as illustrated in FIG. 2).

[0121] In some implementations, the UE may determine the on-demand SIB1 request procedure as barred based on the UAC result. In addition, the timer (e.g., T390) may be started and counted down to zero.

[0122] In some implementations, the UE may be configured with more than one access category / access identity. In addition, the UE may implement / apply the UAC for each given access category / access identity (in parallel) to determine whether the on-demand SIB1 request procedure is barred.

[0123] In some implementations, the UE may be configured / pre-configured / defined (e.g., by the RAN or by the 3GPP TS) not to apply the unified access control mechanism for the WUS transmission (e.g., or for the on-demand SIB1 request procedure) regardless of whether the UE is configured with the access category or access identity. In some implementations, the UE may be configured with the access category / access identities (e.g., based on the access category / access identity as specified in the 3GPP TS) for the access attempt (or for the WUS transmission / on-demand SIB1 request procedure), but the UE may not implement / apply the UAC mechanism for the WUS transmission / on-demand SIB1 request procedure. The UE may implement / apply the UAC for the following mobile-originated (mo) traffic initiation after the UE successfully receives the SIB1 of the target NES Cell.

[0124] In some implementations, the UE may apply the UAC mechanism based on the (target) SIB1 that has been received and stored by the UE during the on-demand SIB1 request procedure. In other words, the UE may apply the UAC only after the UE successfully receives SIB1 from the serving RAN. For example, when the UE camps on the Cell A, the UE may initiate / apply the UAC mechanism based on the SIB1 broadcasted by the Cell A to initiate the on-demand SIB1 request procedure (for the SIB1 of the target NES Cell supported by the Cell A). In some implementations, the UE may camp on a NES Cell and may have stored the valid SIB1 associated with the NES Cell, the UE may need to apply the UAC (e.g., based on the UAC configuration included in the stored SIB1) when the UE initiates the on-demand SIB1 request procedure to the NES Cell for the SIB1 update.

[0125] In some implementations, the UAC may be still valid after the stored SIB1 becomes invalid. In some implementations, in the standalone scenario, even if the stored SIB1 becomes invalid, the stored UAC parameters may still be determined valid to the UE / RAN. Therefore, the UE may still be required / defined to implement / apply the UAC to initiate a new on-demand SIB request procedure for the SIB1 update procedure (after the stored SIB1 associated with the NES Cell becomes invalid).

[0126] In some implementations, the UE may not apply the UAC mechanism to the on-demand SIB1 request procedure while the UE is camping on the NES Cell (e.g., in the standalone scenario as illustrated in FIG. 2).

[0127] In some implementations, the UE may not apply the UAC mechanism to the on-demand SIB1 request procedure while the UE is camping on the NES Cell (e.g., in the standalone scenario as illustrated in FIG. 2) only when the UE has not yet obtained the SIB1 associated with the NES Cell. In some implementations, the UE may need to apply the UAC mechanism (only) after the UE successfully obtains the SIB1 of the target NES Cell. In some implementations, the UE may need to apply the UAC for the on-demand SIB1 request procedure if the UE already has a valid SIB1 and the newly initiated on-demand SIB1 request procedure is for the SIB1 update associated with the NES Cell.

[0128] In some implementations, when the on-demand SIB1 request procedure is initiated (associated with the Cell A or the NES Cell), the UE may also be informed that the SIB1 of the Cell A will be updated (e.g., via the short message transmitted by the Cell A). In this condition, the UE may be triggered to receive the updated SIB1 transmitted by the Cell A.

[0129] In some implementations, the SI modification / SI update of the Cell A may not affect the on-demand SIB1 request procedure if the on-demand SIB1 request procedure was initiated before the SI update indication was received (e.g., via the short message).

[0130] In some implementations, the UE may terminate / postpone / interrupt an ongoing on-demand SIB1 request procedure (associated with the Cell A or the NES Cell) after receiving the SI modification / SI update indication from the concerned Cell A / NES Cell. In some implementations, the serving NES Cell may inform its serving UEs that the SIB1 of the NES Cell will be broadcasted later.

[0131] In some implementations, the UE may re-initiate the on-demand SIB1 request procedure after the concerned Cell A / NES Cell finishes its SI update procedure (e.g., the UE may initiate the on-demand SIB1 request procedure after the SI modification period).

[0132] In some implementations, the UE may have to receive the latest SIB1 each time when the Cell A / NES Cell transmits / broadcasts / indicates the latest SIB1 (or an indication indicating that the SIB1 is available / updated) or the latest on-demand SIB1 (request) configuration.

[0133] In some implementations, the UE may start the timer T390 when the access attempt (e.g., the WUS transmission / on-demand SIB1 request procedure or the access attempt which triggers the WUS transmission / on-demand SIB1 request procedure) is barred by access barring check for an Access Category. The UE may maintain an instance of this timer per Access Category.

[0134] In some implementations, the UE may stop the timer T390 upon the cell (re)selection, upon the relay (re)selection, upon entering the RRC_CONNECTED, upon the reception of the RRCReconfiguration including the reconfigurationWithSync, upon the change of the PCell while in the RRC_CONNECTED state, upon the reception of the MobilityFromNRCommand, upon the reception of the RRCRelease, when the UE determines to initiate the on-demand SIB1 request procedure with another cell / base station, or when the UE has already obtained the target SIB1.

[0135] In some implementations, the value of the timer T390 may be configured based on the following formula: T390 = (0.7+ 0.6 * rand) * uac-BarringTime Where rand is a random value determined by the UE (0 ≦ rand < 1).

[0136] In some implementations, when the timer T390 expires, the UE may determine that the barring for this access category (for the WUS transmission / on-demand SIB1 request procedure) is alleviated. Therefore, the UE may initiate / apply another UAC mechanism again for the WUS transmission / on-demand SIB1 request procedure.

[0137] In some implementations, the UE may determine the initial value of the timer T390 based on different implementations if the UAC is triggered due to the on-demand SIB1 request procedure / WUS transmission.

[0138] In some implementations, the UE may reuse the timer T390 counting mechanism triggered by the UAC mechanism before the UE initiates the on-demand SIB1 request procedure.

[0139] The IE UAC-BarringPerPLMN-List may provide access category-specific access control parameters, which are configured per PLMN / SNPN.

[0140] In some implementations, the UE may determine the access category-specific access control parameters for the WUS transmission / on-demand SIB1 request procedure initialization based on the selected / registered PLMN / SNPN of the UE.

[0141] The IE UAC-BarringPerPLMN-List associated with the NES Cell may be configured / transmitted by the Cell A as part of the on-demand SIB1 request configuration or part of the WUS configuration. The UE may implement / apply the UAC mechanism based on the IE UAC-BarringPerPLMN-List associated with the NES Cell before the UE initiates the on-demand SIB1 Request procedure.

[0142] In some implementations, UE may determine, based on the (supported) PLMN of the Cell A (or the registered NW of the UE), the UAC parameters associated with the target NES Cell (e.g., by referring to the IE UAC-BarringPerPLMN-List and the first PLMN ID shown in the PLMN list supported by the Cell A).

[0143] In some implementations, the IE UAC-BarringPerPLMN-List may be configured as part of the WUS configuration / on-demand SIB1 request configuration provided by the Cell A / Cell A’ / NES Cell.

[0144] In some implementations, the UE may receive and store a valid SIB1 of the target NES Cell via the on-demand SIB1 request procedure. In addition, the UE may also receive a validity indicator (e.g., first indicator) associated with the received SIB1. The UE may receive the SIB1 and validity indicator associated with the SIB1 from the Cell A or from the NES Cell.

[0145] In some implementations, the target cell may broadcast the validity indicator (e.g., second indicator) in the MIB, which may be broadcast periodically by the NES Cell. In addition, the UE may keep monitoring the second indicator broadcasted by the NES Cell. The UE may determine that the stored SIB1 is still valid if the stored first indicator aligns with or is the same as the second indicator. Otherwise, the UE may determine that the stored SIB1 becomes invalid if the stored first indicator does not align with or is different from the second indicator. In this condition, the UE may be triggered to initiate the on-demand SIB1 request procedure to update the stored SIB1. In some implementations, the UE may release / remove the stored SIB1 immediately after determining that the second indictor is different from the first indicator.

[0146] In some implementations, the UE may still keep the stored SIB1 (and the stored SIB1 may be still valid for the UE) even if the second indicator does not align with the first indicator. The stored SIB1 (or part of the parameters of the stored SIB1) may still be valid before the UE successfully receives a valid SIB1 associated with the target NES Cell.

[0147] In some implementations, the first indicator and / or the second indicator may be the value tag associated with different versions of SIB1 broadcasted by the NES Cell. Different versions of the SIB1 may be provided by the NES Cell, the Cell A, or the serving RAN at different timings.

[0148] In some implementations, the legacy UE (e.g., or the UE which is not NES-capable) may ignore the validity indicator associated with the SIB1. In some implementations, the legacy UE may ignore one or more SIB1 and its associated NES Cell(s) / validity indicator received from the serving cell A.

[0149] FIG. 5 is a diagram illustrating an on-demand SIB1 request procedure, according to an example implementation of the present disclosure. The on-demand SIB1 request procedure may be divided into several steps (e.g., as illustrated in FIG. 5).

[0150] Step A: WUS configuration, which may include any combinations of Step A-1 and Step A-2. Step A-1: WUS configuration_NES transmission (from the NES Cell) and WUS configuration_NES reception (at the UE side). Step A-2: WUS configuration_A transmission (from the Cell A) and WUS configuration_A reception (at the UE side).

[0151] In some implementations, the UE may be able to receive the WUS configurations from the NES Cell (e.g., via the WUS configuration_NES reception) and WUS configuration from the Cell A (e.g., via the WUS configuration_A reception). The UE may store both the WUS configuration from the NES Cell and the WUS configuration from the Cell A. In some implementations, the UE may only store a WUS configuration received via the WUS configuration_NES reception or the WUS configuration_A reception even if the UE is capable of receiving both WUS configurations. In some implementations, the UE may only choose to store the latest / up to date WUS configuration, and a new WUS configuration (e.g., received via the WUS configuration_NES reception or the WUS configuration_A reception) may overwrite a stored WUS configuration (e.g., received via the WUS configuration_NES or the WUS configuration_A). In some implementations, the UE may always only receive and store the WUS configuration from a network node (e.g., the NES Cell or the Cell A). In some implementations, different priorities may be provided to the WUS configuration from different network nodes.

[0152] Step B: On-Demand SIB1 Request, which may include any combinations of Step B-1 and Step B-2. Step B-1: WUS Transmission_NES transmission (from the UE to the NES Cell) and WUS Transmission_NES reception (at the NES Cell). Step B-2: WUS Transmission_A transmission (from the UE to Cell A) and WUS Transmission_A reception (at Cell A).

[0153] In some implementations, the UE may be able to transmit one or more WUSs to the NES Cell (e.g., via the WUS Transmission_NES transmission) and / or one or more WUSs to the Cell A (e.g., via the WUS Transmission_A transmission). In some implementations, a WUS transmission (e.g., on a common uplink radio resource) from the UE may be detectable by both NES Cell and Cell A. In addition, both nodes may exchange their detection results via a backhaul connection to support / trigger NES Cells in broadcasting the SIB after receiving a UE’s request. In some implementations, one common configuration may be shared among more than one Cell A / Cell A’ / NES Cell.

[0154] In some implementations, the WUS configuration may include the Wake-Up-Signal configuration (e.g., which may be referred to as one or more preambles as specified in the 3GPP TS) and / or uplink resource configuration (e.g., which may be referred to as the RACH configuration as specified in the 3GPP TS).

[0155] Step C: On-Demand SIB1 Response, which may include any combinations of Step C-1 and Step C-2. Step C-1: WUS Response_NES transmission (from the NES Cell to the UE) and WUS Response_NES reception (at the UE side). Step C-2: WUS Response_A transmission (from the Cell A to the UE) and WUS Response_A reception (at the UE side).

[0156] In some implementations, the UE may be configured with the DL resource (e.g., based on the Random Access Response message reception during a (2-step / 4-step) RA procedure as specified in the 3GPP TS) to receive the WUS message. The WUS message may be part of the WUS Response_NES reception or WUS Response_A reception.

[0157] In some implementations, the UE may monitor the WUS Response based on the Random Access Response (RAR) reception (e.g., the UE may try to monitor and decode DCI within a given time period TWUS after transmitting the WUS. The DCI may be scrambled by a RA-RNTI or another WUS-RNTI, which may be specified for the on-demand SIB1 request procedure. In some implementations, the UE may determine the duration of the TWUS based on the Random Access Response window time period).

[0158] Step D: On-Demand SIB1 Transmission, which may include any combinations of Step D-1 and Step D-2. Step D-1: SIB1 Transmission_NES_transmission (from the NES Cell to UE) and SIB1 Transmission_NES reception (at the UE side). Step D-2: SIB1 Transmission_A transmission (from the Cell A to the UE) and SIB1 Transmission _A reception (at the UE side).

[0159] In some implementations, an on-demand SIB1 procedure may (not) include all of the indicated steps as illustrated in FIG. 5. For example, the NES Cell / Cell A may not transmit the on-demand SIB1 response to the UE after receiving the on-demand SIB1 request message from the UE. In some implementations, the NES Cell / Cell A may transmit the on-demand SIB1 to the UE directly (e.g., via broadcasting system information of the NES Cell / Cell A).

[0160] In some other implementations, the NES Cell / Cell A may transmit a NACK message to the UE if the on-demand SIB1 request message is not successfully received. In such a case, the on-demand SIB1 transmission may not occur.

[0161] In some implementations, the UE may be configured with an “on-demand SIB1 request timer (T3XX)”. In addition, the UE may start counting the “on-demand SIB1 request timer (T3XX)” down to zero while / upon / after the UE transmits the WUS to the Cell A or the (target) NES Cell (e.g., Step B). The timer may be started upon the first WUS transmission while retransmissions, repetitions, or multiple WUS transmissions are performed during the on-demand SIB1 request procedure. In some implementations, the UE may continue counting the “on-demand SIB1 request timer (T3XX)” down to zero unless the UE receives one (or more) ACK response or receives the target SIB1 from the serving RAN (e.g., the Cell A / NES Cell). The T3XX may be stopped upon performing Step C or Step D). Otherwise, the UE may determine that the ongoing on-demand SIB1 request procedure has failed upon the T3XX expires.

[0162] FIG. 6 is a flowchart illustrating a method / process 600 performed by a UE for requesting an on-demand (OD)-system information block 1 (SIB1), according to an example implementation of the present disclosure.

[0163] In the action 602, the process 600 may start by receiving, from a first cell, an uplink-wake-up signal (UL-WUS) configuration.

[0164] In the action 604, the process 600 may transmit, to the first cell or a second cell, a WUS for requesting a target SIB1 based on the UL-WUS configuration.

[0165] In the action 606, the process 600 may receive, from the first cell or the second cell, a response associated with WUS.

[0166] In the action 608, the process 600 may receive, from the first cell or the second cell, the target SIB1 in response to receiving the response. The process 600 may then end.

[0167] In some implementations, the process 600 may transmit, to the second cell, the WUS in the action 604, the process 600 may receive, from the second cell, the response in the action 606, and the process 600 may receive, from the second cell, the target SIB 1 in the action 608. The target SIB1 may be associated with the second cell.

[0168] In some implementations, the process 600 may receive, from the first cell of a first mode, the UL-WUS configuration in the action 602, the process 600 may transmit, to the first cell of a second mode, the WUS in the action 604, the process 600 may receive, from the first cell of the second mode, the response in the action 606, and the process 600 may receive, from the first cell of the second mode, the target SIB1 in the action 608. The target SIB1 may be associated with the first cell of the second mode, and the second mode may include a network energy saving (NES) mode.

[0169] In some implementations, the process 600 may transmit, to the first cell, the WUS in the action 604, the process 600 may receive, from the first cell, the response in the action 606, and the process 600 may receive, from the first cell, the target SIB1 in the action 608. The target SIB1 may be associated with the second cell.

[0170] In some implementations, the process 600 may transmit, to the first cell, the WUS in the action 604, the process 600 may receive, from the first cell, the response in the action 606, and the process 600 may receive, from the second cell, the target SIB1 in the action 608. The target SIB1 may be associated with the second cell.

[0171] In some implementations, the UE may determine, based on a network identity (ID) included in the UL-WUS configuration, whether to transmit to the first cell or the second cell, the WUS. The network ID may include a public land mobile network (PLMN) ID, a standalone non-public network (SNPN) ID, or a closed access group (CAG) ID associated with the first cell or the second cell.

[0172] In some implementations, the UE may determine, based on the network ID included in the UL-WUS configuration associated with the first cell or the second cell, whether the first cell or the second cell is a suitable cell or an acceptable cell.

[0173] In some implementations, the UE may store the target SIB1 after receiving the target SIB1, and determine, based on a pre-define period, whether the stored SIB 1 is valid. The UE may determine that the stored SIB 1 is valid during the pre-define period, and determine that the stored SIB 1 is invalid and release the stored SIB 1 after the pre-define period.

[0174] The steps / actions shown in FIG. 6 should not be construed as necessarily order dependent. The order in which the process is described is not intended to be construed as a limitation. Moreover, some of the actions shown in FIG. 6 may be omitted in some implementations and one or more actions shown in FIG. 6 may be combined. The proposed mechanism may not be limited to SIB1 but also be applicable to other essential system information or system information for the specific feature (e.g., NTN, sidelink, or MBS).

[0175] The technical problem addressed by the method illustrated in FIG. 6 is how to efficiently request and acquire an on-demand system information block 1 (OD-SIB1) while minimizing power consumption and signaling overhead. In conventional systems, system information is periodically broadcasted, leading to unnecessary energy consumption for user equipment (UE) that may not require frequent updates. By utilizing UL-WUS, the UE can selectively activate communication only when necessary, reducing idle power consumption and unnecessary signaling exchanges. Furthermore, allowing the WUS to be transmitted to either the first cell or a second cell increases the flexibility of network selection, improving system responsiveness and reducing delays in receiving OD-SIB1. This method ultimately enhances network efficiency while maintaining reliable and timely system information delivery.

[0176] FIG. 7 is a flowchart illustrating a method / process 700 performed by a BS for managing an on-demand (OD)-system information block 1 (SIB1) request, according to an example implementation of the present disclosure.

[0177] In the action 702, the process 700 may start by transmitting, via a first cell, an uplink-wake-up signal (UL-WUS) configuration.

[0178] In the action 704, the process 700 may receive, via the first cell or a second cell, a WUS for requesting a target SIB1 based on the UL-WUS configuration.

[0179] In the action 706, the process 700 may transmit, via the first cell or the second cell, a response associated with WUS.

[0180] In the action 708, the process 700 may transmit, via the first cell or the second cell, the target SIB1 in response to transmitting the response. The process 700 may then end.

[0181] In some implementations, the process 700 may receive, via the second cell, the WUS in the action 704, the process 700 may transmit, via the second cell, the response in the action 706, and the process 700 may transmit, via the second cell, the target SIB 1 in the action 708. The target SIB1 may be associated with the second cell.

[0182] In some implementations, the process 700 may transmit, via the first cell of a first mode, the UL-WUS configuration in the action 702, the process 700 may receive, via the first cell of a second mode, the WUS in the action 704, the process 700 may transmit, via the first cell of the second mode, the response in the action 706, and the process 700 may transmit, via the first cell of the second mode, the target SIB1 in the action 708. The target SIB1 may be associated with the first cell of the second mode, and the second mode may include a network energy saving (NES) mode.

[0183] In some implementations, the process 700 may receive, via the first cell, the WUS in the action 704, the process 700 may transmit, via the first cell, the response in the action 706, and the process 700 may transmit, via the first cell, the target SIB1 in the action 708. The target SIB1 may be associated with the second cell.

[0184] In some implementations, the process 700 may receive, via the first cell, the WUS in the action 704, the process 700 may transmit, via the first cell, the response in the action 706, and the process 700 may transmit, via the second cell, the target SIB1 in the action 708. The target SIB1 may be associated with the second cell.

[0185] In some implementations, the UL-WUS configuration may include a network identity (ID), and the network ID may include a public land mobile network (PLMN) ID, a standalone non-public network (SNPN) ID, or a closed access group (CAG) ID associated with the first cell or the second cell.

[0186] The method illustrated in FIG. 7 is similar to that in FIG. 6, except that it is described from the perspective of the BS (instead of the UE).

[0187] FIG. 8 is a block diagram illustrating a node 800 for wireless communication in accordance with various aspects of the present disclosure. As illustrated in FIG. 8, a node 800 may include a transceiver 820, a processor 828, a memory 834, one or more presentation components 838, and at least one antenna 836. The node 800 may also include a radio frequency (RF) spectrum band module, a BS communications module, a network communications module, and a system communications management module, Input / Output (I / O) ports, I / O components, and a power supply (not illustrated in FIG. 8).

[0188] Each of the components may directly or indirectly communicate with each other over one or more buses 840. The node 800 may be a UE or a BS that performs various functions disclosed with reference to FIGS. 6 through 7.

[0189] The transceiver 820 has a transmitter 822 (e.g., transmitting / transmission circuitry) and a receiver 824 (e.g., receiving / reception circuitry) and may be configured to transmit and / or receive time and / or frequency resource partitioning information. The transceiver 820 may be configured to transmit in different types of subframes and slots including, but not limited to, usable, non-usable, and flexibly usable subframes and slot formats. The transceiver 820 may be configured to receive data and control channels.

[0190] The node 800 may include a variety of computer-readable media. Computer-readable media may be any available media that may be accessed by the node 800 and include volatile (and / or non-volatile) media and removable (and / or non-removable) media.

[0191] The computer-readable media may include computer-storage media and communication media. Computer-storage media may include both volatile (and / or non-volatile media), and removable (and / or non-removable) media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or data.

[0192] Computer-storage media may include RAM, ROM, EPROM, EEPROM, flash memory (or other memory technology), CD-ROM, Digital Versatile Disks (DVD) (or other optical disk storage), magnetic cassettes, magnetic tape, magnetic disk storage (or other magnetic storage devices), etc. Computer-storage media may not include a propagated data signal. Communication media may typically embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transport mechanisms and include any information delivery media.

[0193] The term “modulated data signal” may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Communication media may include wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above listed components should also be included within the scope of computer-readable media.

[0194] The memory 834 may include computer-storage media in the form of volatile and / or non-volatile memory. The memory 834 may be removable, non-removable, or a combination thereof. Example memory may include solid-state memory, hard drives, optical-disc drives, etc. As illustrated in FIG. 8, the memory 834 may store a computer-readable and / or computer-executable instructions 832 (e.g., software codes) that are configured to, when executed, cause the processor 828 to perform various functions disclosed herein, for example, with reference to FIGS. 6 through 7. Alternatively, the instructions 832 may not be directly executable by the processor 828 but may be configured to cause the node 800 (e.g., when compiled and executed) to perform various functions disclosed herein.

[0195] The processor 828 (e.g., having processing circuitry) may include an intelligent hardware device, e.g., a Central Processing Unit (CPU), a microcontroller, an ASIC, etc. The processor 828 may include memory. The processor 828 may process the data 830 and the instructions 832 received from the memory 834, and information transmitted and received via the transceiver 820, the baseband communications module, and / or the network communications module. The processor 828 may also process information to send to the transceiver 820 for transmission via the antenna 836 to the network communications module for transmission to a CN.

[0196] One or more presentation components 838 may present data indications to a person or another device. Examples of presentation components 838 may include a display device, a speaker, a printing component, a vibrating component, etc.

[0197] In view of the present disclosure, it is obvious that various techniques may be used for implementing the disclosed concepts without departing from the scope of those concepts. Moreover, while the concepts have been disclosed with specific reference to certain implementations, a person of ordinary skill in the art may recognize that changes may be made in form and detail without departing from the scope of those concepts. As such, the disclosed implementations are to be considered in all respects as illustrative and not restrictive. It should also be understood that the present disclosure is not limited to the particular implementations disclosed and many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

1. A user equipment (UE) for requesting an on-demand (OD)-system information block 1 (SIB1), the UE comprising: 　　　　at least one processor; and 　　　　at least one non-transitory computer-readable medium coupled to at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the UE to: 　　　　　　　　receive, from a first cell, an uplink-wake-up signal (UL-WUS) configuration; 　　　　　　　　transmit, to the first cell or a second cell, a WUS for requesting a target SIB1 based on the UL-WUS configuration; 　　　　　　　　receive, from the first cell or the second cell, a response associated with WUS; and 　　　　　　　　receive, from the first cell or the second cell, the target SIB1 in response to receiving the response.

2. The UE of claim 1, wherein: 　　　　transmitting, to the first cell or the second cell, the WUS comprises transmitting, to the second cell, the WUS, 　　　　receiving, from the first cell or the second cell, the response comprises receiving, from the second cell, the response, 　　　　receiving, from the first cell or the second cell, the target SIB1 comprises receiving, from the second cell, the target SIB 1, and 　　　　the target SIB1 is associated with the second cell.

3. The UE of claim 1, wherein: 　　　　receiving, from the first cell, the UL-WUS configuration comprises receiving, from the first cell of a first mode, the UL-WUS configuration, 　　　　transmitting, to the first cell or the second cell, the WUS comprises transmitting, to the first cell of a second mode, the WUS, 　　　　receiving, from the first cell or the second cell, the response comprises receiving, from the first cell of the second mode, the response, 　　　　receiving, from the first cell or the second cell, the target SIB1 comprises receiving, from the first cell of the second mode, the target SIB1, 　　　　the target SIB1 is associated with the first cell of the second mode, and 　　　　the second mode includes a network energy saving (NES) mode.

4. The UE of claim 1, wherein: 　　　　transmitting, to the first cell or the second cell, the WUS comprises transmitting, to the first cell, the WUS, 　　　　receiving, from the first cell or the second cell, the response comprises receiving, from the first cell, the response, 　　　　receiving, from the first cell or the second cell, the target SIB1 comprises receiving, from the first cell, the target SIB1, and 　　　　the target SIB1 is associated with the second cell.

5. The UE of claim 1, wherein: 　　　　transmitting, to the first cell or the second cell, the WUS comprises transmitting, to the first cell, the WUS, 　　　　receiving, from the first cell or the second cell, the response comprises receiving, from the first cell, the response, 　　　　receiving, from the first cell or the second cell, the target SIB1 comprises receiving, from the second cell, the target SIB1, and 　　　　the target SIB1 is associated with the second cell.

6. The UE of claim 1, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　determine, based on a network identity (ID) included in the UL-WUS configuration, whether to transmit to the first cell or the second cell, the WUS, wherein 　　　　the network ID comprises a public land mobile network (PLMN) ID, a standalone non-public network (SNPN) ID, or a closed access group (CAG) ID associated with the first cell or the second cell.

7. The UE of claim 6, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　determine, based on the network ID included in the UL-WUS configuration associated with the first cell or the second cell, whether the first cell or the second cell is a suitable cell or an acceptable cell.

8. The UE of claim 1, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　store the target SIB1 after receiving the target SIB1; 　　　　determine, based on a pre-define period, whether the stored SIB 1 is valid; 　　　　determine that the stored SIB 1 is valid during the pre-define period; and 　　　　determine that the stored SIB 1 is invalid and release the stored SIB 1 after the pre-define period.

9. A method performed by a user equipment (UE) for requesting an on-demand (OD)-system information block 1 (SIB1), the method comprising: 　　　　receiving, from a first cell, an uplink-wake-up signal (UL-WUS) configuration; 　　　　transmitting, to the first cell or a second cell, a WUS for requesting a target SIB1 based on the UL-WUS configuration; 　　　　receiving, from the first cell or the second cell, a response associated with WUS; and 　　　　receiving, from the first cell or the second cell, the target SIB1 in response to receiving the response.

10. A base station (BS) for managing an on-demand (OD)-system information block 1 (SIB1) request, the BS comprising: 　　　　at least one processor; and 　　　　at least one non-transitory computer-readable medium coupled to at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the BS to: 　　　　　　　　transmit, via a first cell, an uplink-wake-up signal (UL-WUS) configuration; receive, via the first cell or a second cell, a WUS for requesting a target SIB1 based on the UL-WUS configuration; 　　　　　　　　transmit, via the first cell or the second cell, a response associated with WUS; and 　　　　　　　　transmit, via the first cell or the second cell, the target SIB1 in response to transmitting the response.

11. The BS of claim 10, wherein: 　　　　receiving, via the first cell or the second cell, the WUS comprises receiving, via the second cell, the WUS, 　　　　transmitting, via the first cell or the second cell, the response comprises transmitting, via the second cell, the response, 　　　　transmitting, via the first cell or the second cell, the target SIB 1 comprises transmitting, via the second cell, the target SIB 1, and 　　　　the target SIB1 is associated with the second cell.

12. The BS of claim 10, wherein: 　　　　transmitting, via the first cell, the UL-WUS configuration comprises transmitting, via the first cell of a first mode, the UL-WUS configuration, 　　　　receiving, via the first cell or the second cell, the WUS comprises receiving, via the first cell of a second mode, the WUS, 　　　　transmitting, via the first cell or the second cell, the response comprises transmitting, via the first cell of the second mode, the response, 　　　　transmitting, via the first cell or the second cell, the target SIB1 comprises transmitting, via the first cell of the second mode, the target SIB1, 　　　　the target SIB1 is associated with the first cell of the second mode, and the second mode includes a network energy saving (NES) mode.

13. The BS of claim 10, wherein: 　　　　receiving, via the first cell or the second cell, the WUS comprises receiving, via the first cell, the WUS, 　　　　transmitting, via the first cell or the second cell, the response comprises transmitting, via the first cell, the response, 　　　　transmitting, via the first cell or the second cell, the target SIB1 comprises transmitting, via the first cell, the target SIB1, and 　　　　the target SIB1 is associated with the second cell.

14. The BS of claim 10, wherein: 　　　　receiving, via the first cell or the second cell, the WUS comprises receiving, via the first cell, the WUS, 　　　　transmitting, via the first cell or the second cell, the response comprises transmitting, via the first cell, the response, 　　　　transmitting, via the first cell or the second cell, the target SIB1 comprises transmitting, via the second cell, the target SIB1, and 　　　　the target SIB1 is associated with the second cell.

15. The BS of claim 10, wherein: 　　　　the UL-WUS configuration comprises a network identity (ID), and 　　　　the network ID comprises a public land mobile network (PLMN) ID, a standalone non-public network (SNPN) ID, or a closed access group (CAG) ID associated with the first cell or the second cell.

Images