Method and apparatus for uplink wake-up signal based on-demand system information acquisition in wireless communication

Abstract

Methods and apparatus for uplink wake-up signal based on-demand system information acquisition in wireless communication are provided. The method includes receiving an UL WUS configuration with RNTI values, timers, preamble identifier, and RSRP threshold from a first cell; receiving SSBs from a second cell; selecting an SSB above the RSRP threshold; starting a first timer and monitoring for a first PDCCH with beam-specific RNTI. If detected, the method monitors for a second PDCCH with SI-RNTI to receive OD-SIB1. If the first timer expires without detection, the method transmits an UL WUS using the preamble identifier and monitors for network response with a second timer.

Description

METHOD AND APPARATUS FOR UPLINK WAKE-UP SIGNAL BASED ON-DEMAND SYSTEM INFORMATION ACQUISITION IN WIRELESS COMMUNICATION

[0001] The present disclosure relates to wireless communication, and in particular, to methods and apparatus for uplink wake-up signal based on-demand system information acquisition in wireless communication.

[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) system, 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 increase, however, there exists a need for further improvements in the art.Summery of Invention

[0003] The present disclosure relates to wireless communication, and in particular, to methods and apparatus for uplink wake-up signal based on-demand system information acquisition in wireless communication.

[0004] According to a first aspect of the present disclosure, a User Equipment (UE) is provided. The UE includes at least one processor and at least one non-transitory computer-readable medium coupled to the 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 associated with a second cell, where the UL WUS configuration includes one or more Radio Network Temporary Identifier (RNTI) values, a first timer, a second timer, a third timer, a preamble identifier, and a Reference Signal Received Power (RSRP) threshold, receive, from the second cell, one or more first Synchronization Signal Blocks (SSBs), each first SSB of the one or more first SSBs corresponding to one of the one or more RNTI values, select a first SSB from the one or more first SSBs with an RSRP value above the RSRP threshold, start the first timer, monitor for a first Physical Downlink Control Channel (PDCCH) with Cyclic Redundancy Check (CRC) scrambled by the RNTI value corresponding to the selected first SSB while the first timer is running, in a case where the first PDCCH is detected before the first timer expires, stop the first timer, start the third timer, and monitor for a second PDCCH with CRC scrambled by a System Information-RNTI (SI-RNTI) while the third timer is running, and in a case where the first timer expires and the first PDCCH has not been received, transmit an UL WUS using the preamble identifier in a Physical Random Access Channel (PRACH) occasion associated with the selected first SSB, start the second timer, and monitor for the first PDCCH while the second timer is running.

[0005] In some implementations of the first aspect of the present disclosure, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to receive an on-demand System Information Block 1 (OD-SIB1) via a Physical Downlink Shared Channel (PDSCH) scheduled by the second PDCCH when the second PDCCH is detected.

[0006] In some implementations of the first aspect of the present disclosure, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to, in response to detecting the first PDCCH while the second timer is running, stop the second timer, start the third timer, and monitor for the second PDCCH.

[0007] In some implementations of the first aspect of the present disclosure, the UL WUS configuration further includes a maximum number of preamble transmissions, and where the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to maintain a counter, retransmit the UL WUS when the second timer expires without detecting the first PDCCH and the counter has not reached the maximum number, and indicate a Random Access Channel (RACH) problem to upper layers when the counter reaches the maximum number.

[0008] In some implementations of the first aspect of the present disclosure, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to receive, from the second cell, a Master Information Block (MIB) including a field, where the field indicates a broadcasting status of an on-demand System Information Block 1 (OD-SIB1) when a predetermined condition related to a subcarrier offset parameter is met, and determine the broadcasting status of the OD-SIB1 based on the field.

[0009] In some implementations of the first aspect of the present disclosure, the predetermined condition includes the subcarrier offset parameter exceeding a threshold value, where the threshold value is different for different frequency ranges.

[0010] In some implementations of the first aspect of the present disclosure, the UL WUS configuration further includes a bitmap for one or more second SSBs of the second cell, where each bit of the bitmap indicates a broadcasting status of an on-demand System Information Block 1 (OD-SIB1) associated with a corresponding second SSB of the one or more second SSBs.

[0011] In some implementations of the first aspect of the present disclosure, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to determine that the second cell is a Network Energy Saving (NES) cell based on a subcarrier offset parameter exceeding a frequency range-specific threshold.

[0012] In some implementations of the first aspect of the present disclosure, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to consider the second cell as barred when the third timer expires without receiving an on-demand System Information Block 1 (OD-SIB1).

[0013] According to a second aspect of the present disclosure, a method performed by a User Equipment (UE) is provided. The method includes receiving, from a first cell, an uplink wake-up signal (UL WUS) configuration associated with a second cell, where the UL WUS configuration includes one or more Radio Network Temporary Identifier (RNTI) values, a first timer, a second timer, a third timer, a preamble identifier, and a Reference Signal Received Power (RSRP) threshold, receiving, from the second cell, one or more first Synchronization Signal Blocks (SSBs), each first SSB of the one or more first SSBs corresponding to one of the one or more RNTI values, selecting a first SSB from the one or more first SSBs with an RSRP value above the RSRP threshold, starting the first timer, monitoring for a first Physical Downlink Control Channel (PDCCH) with Cyclic Redundancy Check (CRC) scrambled by the RNTI value corresponding to the selected first SSB while the first timer is running, in a case where the first PDCCH is detected before the first timer expires, stopping the first timer, starting the third timer, and monitoring for a second PDCCH with CRC scrambled by a System Information-RNTI (SI-RNTI) while the third timer is running, and in a case where the first timer expires and the first PDCCH has not been received, transmitting an UL WUS using the preamble identifier in a Physical Random Access Channel (PRACH) occasion associated with the selected first SSB, starting the second timer, and monitoring for the first PDCCH while the second timer is running.

[0014] According to a third aspect of the present disclosure, a base station is provided. The base station includes at least one processor and at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the base station to transmit, via a first cell to a User Equipment (UE), an uplink wake-up signal (UL WUS) configuration associated with a second cell, where the UL WUS configuration includes one or more Radio Network Temporary Identifier (RNTI) values, a first timer, a second timer, a third timer, a preamble identifier, and a Reference Signal Received Power (RSRP) threshold, transmit, via the second cell, one or more first Synchronization Signal Blocks (SSBs), each first SSB of the one or more first SSBs being associated with one of the one or more RNTI values, monitor, via the second cell, for an UL WUS from the UE in a Physical Random Access Channel (PRACH) occasion associated with one of the one or more first SSBs, and in response to detecting the UL WUS with the preamble identifier associated with a specific first SSB, transmit, via the second cell, a first Physical Downlink Control Channel (PDCCH) with Cyclic Redundancy Check (CRC) scrambled by the RNTI value corresponding to the specific first SSB, and transmit, via the second cell, an on-demand System Information Block 1 (OD-SIB1) via a Physical Downlink Shared Channel (PDSCH) scheduled by a second PDCCH with CRC scrambled by System Information-RNTI (SI-RNTI).

[0015] In some implementations of the third aspect of the present disclosure, the UL WUS configuration further includes a maximum number of preamble transmissions, and where the one or more computer-executable instructions, when executed by the at least one processor, further cause the base station to monitor, via the second cell, for retransmissions of the UL WUS from the UE up to the maximum number of preamble transmissions.

[0016] In some implementations of the third aspect of the present disclosure, the one or more computer-executable instructions, when executed by the at least one processor, further cause the base station to transmit, via the second cell, a Master Information Block (MIB) including a field, where the field indicates a broadcasting status of an on-demand System Information Block 1 (OD-SIB1) when a predetermined condition related to a subcarrier offset parameter is met.

[0017] In some implementations of the third aspect of the present disclosure, the predetermined condition includes the subcarrier offset parameter exceeding a threshold value, where the threshold value is different for different frequency ranges.

[0018] In some implementations of the third aspect of the present disclosure, the UL WUS configuration further includes a bitmap for one or more second SSBs of the second cell, where each bit of the bitmap indicates a broadcasting status of an on-demand System Information Block 1 (OD-SIB1) associated with a corresponding second SSB of the one or more second SSBs.

[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 flowchart illustrating a method / process for uplink wake-up signal based on-demand system information acquisition in wireless communication, according to an example implementation of the present disclosure.

[0021] FIG. 2 is a block diagram illustrating a node for wireless communications, in accordance with various aspects of the present disclosure.

[0022] Some of the abbreviations in the present application are defined as follows and, unless otherwise specified, the abbreviations have the following meanings: Abbreviation　　　　　　　　Full name 3GPP　　　　　　　　　　　　3rd Generation Partnership Project 5G　　　　　　　　　　　　　　　　5th Generation 5GC　　　　　　　　　　　　　　　　5G Core 6G　　　　　　　　　　　　　　　　Sixth Generation ACK　　　　　　　　　　　　Acknowledgement AI　　　　　　　　　　　　　　　　Artificial Intelligence AN-PDB　　　　　　　　　　　　Access Network Packet Delay Budget ARFCN　　　　　　　　　　　　Absolute Radio Frequency Channel Number AS　　　　　　　　　　　　　　　　Access Stratum ASN.1　　　　　　　　　　　　Abstract Syntax Notation One BFRQ　　　　　　　　　　　　Beam Failure Recovery Request BS　　　　　　　　　　　　　　　　Base Station BSR　　　　　　　　　　　　　　　　Buffer Status Report BWP　　　　　　　　　　　　Bandwidth Part C-RNTI　　　　　　　　　　　　Cell Radio Network Temporary Identifier CA　　　　　　　　　　　　　　　　Carrier Aggregation CAG　　　　　　　　　　　　Closed Access Group CB　　　　　　　　　　　　　　　　Codebook-Based CC　　　　　　　　　　　　　　　　Component Carrier CG　　　　　　　　　　　　　　　　Configured Grant CIF　　　　　　　　　　　　　　　　Carrier Indicator Field CJT　　　　　　　　　　　　　　　　Coherent Joint Transmission CN　　　　　　　　　　　　　　　　Core Network CN-PDB　　　　　　　　　　　　Core Network Packet Delay Budget CORESET　　　　　　　　Control Resource Set CPE　　　　　　　　　　　　　　　　Customer Premises Equipment CQI　　　　　　　　　　　　　　　　Channel Quality Indication CRC　　　　　　　　　　　　Cyclic Redundancy Check CSI　　　　　　　　　　　　　　　　Channel State Information CSI-RS　　　　　　　　　　　　Channel State Information Reference Signal CS-RNTI　　　　　　　　　　　　Configured Scheduling Radio Network Temporary Identifier CSS　　　　　　　　　　　　　　　　Common Search Space CU　　　　　　　　　　　　　　　　Central Unit DAPS　　　　　　　　　　　　Dual Active Protocol Stack DC　　　　　　　　　　　　　　　　Dual Connectivity DCI　　　　　　　　　　　　　　　　Downlink Control Information DG　　　　　　　　　　　　　　　　Dynamic Grant DI　　　　　　　　　　　　　　　　Delay Information DL　　　　　　　　　　　　　　　　Downlink DL-SCH　　　　　　　　　　　　Downlink Shared Channel DMRS　　　　　　　　　　　　Demodulation Reference Signal DR　　　　　　　　　　　　　　　　Delay Report DRB　　　　　　　　　　　　Data Radio Bearer DRX　　　　　　　　　　　　Discontinuous Reception DTCH　　　　　　　　　　　　Dedicated Traffic Channel DTX　　　　　　　　　　　　Discontinuous Transmission DU　　　　　　　　　　　　　　　　Distributed Unit ETSI　　　　　　　　　　　　European Telecommunications Standards Institute E-UTRA　　　　　　　　　　　　Evolved Universal Terrestrial Radio Access EN-DC　　　　　　　　　　　　E-UTRA NR Dual Connectivity EPC　　　　　　　　　　　　　　　　Evolved Packet Core eMBB　　　　　　　　　　　　Enhanced Mobile BroadBand eMTC　　　　　　　　　　　　Enhanced Machine Type Communication eNB　　　　　　　　　　　　　　　　Evolved Node B FDD　　　　　　　　　　　　Frequency Division Duplexing FDRA　　　　　　　　　　　　Frequency Domain Resource Allocation FR　　　　　　　　　　　　　　　　Frequency Range FR1　　　　　　　　　　　　　　　　Frequency Range 1 FR2　　　　　　　　　　　　　　　　Frequency Range 2 FWA　　　　　　　　　　　　Fixed Wireless Access GEO　　　　　　　　　　　　Geostationary Equatorial Orbit gNB　　　　　　　　　　　　　　　　Next Generation Node B GNSS　　　　　　　　　　　　Global Navigation Satellite System GPS　　　　　　　　　　　　　　　　Global Positioning System GW　　　　　　　　　　　　　　　　Gateway HARQ　　　　　　　　　　　　Hybrid Automatic Repeat Request HO　　　　　　　　　　　　　　　　Handover FR　　　　　　　　　　　　　　　　Frequency Range IAB　　　　　　　　　　　　　　　　Integrated Access and Backhaul ID　　　　　　　　　　　　　　　　Identity IE　　　　　　　　　　　　　　　　Information Element IoT　　　　　　　　　　　　　　　　Internet of Things ITS　　　　　　　　　　　　　　　　Intelligent Transportation System ITU　　　　　　　　　　　　　　　　International Telecommunication Union L1　　　　　　　　　　　　　　　　　　　　Layer 1 L2　　　　　　　　　　　　　　　　Layer 2 L3　　　　　　　　　　　　　　　　Layer 3 LAN　　　　　　　　　　　　Local Area Network LCH　　　　　　　　　　　　Logical Channel LCID　　　　　　　　　　　　Logical Channel Identity LEO　　　　　　　　　　　　　　　　Low Earth Orbit LTE 　　　　　　　　　　　　Long Term Evolution LTM　　　　　　　　　　　　Layer 1 / Layer 2 Triggered Mobility LSB　　　　　　　　　　　　　　　　Least Significant Bit MAC　　　　　　　　　　　　Medium Access Control MAC CE　　　　　　　　　　　　MAC Control Element MCG　　　　　　　　　　　　Master Cell Group MCS　　　　　　　　　　　　Modulation and Coding Scheme MEO　　　　　　　　　　　　Medium Earth Orbit MIB　　　　　　　　　　　　　　　　Master Information Block MIMO　　　　　　　　　　　　Multi-Input Multi-Output ML　　　　　　　　　　　　　　　　Machine Learning mMTC　　　　　　　　　　　　Massive Machine Type Communications MN　　　　　　　　　　　　　　　　Master Node MSG　　　　　　　　　　　　Message MTC　　　　　　　　　　　　Machine Type Communication NACK　　　　　　　　　　　　Negative Acknowledgement NAS　　　　　　　　　　　　Non-Access Stratum NB-IoT　　　　　　　　　　　　Narrow Band Internet of Things NCB　　　　　　　　　　　　Non-Codebook-Based NDI　　　　　　　　　　　　　　　　New Data Indicator NES　　　　　　　　　　　　　　　　Network Energy Saving NPN　　　　　　　　　　　　Non-Public Network NR　　　　　　　　　　　　　　　　New Radio NR-U　　　　　　　　　　　　NR Unlicensed NTN　　　　　　　　　　　　Non-Terrestrial Network OD-SIB1　　　　　　　　　　　　On-Demand System Information Block 1 OD-SSB　　　　　　　　　　　　On-Demand Synchronization Signal Block PA　　　　　　　　　　　　　　　　Power Amplifier PBCH　　　　　　　　　　　　Physical Broadcast Channel PCell　　　　　　　　　　　　Primary Cell PCI　　　　　　　　　　　　　　　　Physical Cell Identity PDB　　　　　　　　　　　　　　　　Packet Delay Budget PDCCH　　　　　　　　　　　　Physical Downlink Control Channel PDCP　　　　　　　　　　　　Packet Data Convergence Protocol PDSCH　　　　　　　　　　　　Physical Downlink Shared Channel PDU　　　　　　　　　　　　Protocol Data Unit PHY　　　　　　　　　　　　Physical PLMN 　　　　　　　　　　　　Public Land Mobile Network PMI　　　　　　　　　　　　　　　　Precoding Matrix indicator PNI-NPN　　　　　　　　　　　　Public Network Integrated Non-Public Network PRACH　　　　　　　　　　　　Physical Random Access Channel PSDB　　　　　　　　　　　　PDU Set Delay Budget PUCCH　　　　　　　　　　　　Physical Uplink Control Channel PUSCH　　　　　　　　　　　　Physical Uplink Shared Channel QCL　　　　　　　　　　　　Quasi-CoLocation QoS　　　　　　　　　　　　　　　　Quality of Service RA　　　　　　　　　　　　　　　　Random Access RACH　　　　　　　　　　　　Random Access Channel RAN　　　　　　　　　　　　Radio Access Network RAR　　　　　　　　　　　　Random Access Response RAT　　　　　　　　　　　　　　　　Radio Access Technology RE　　　　　　　　　　　　　　　　Resource Element Rel-15　　　　　　　　　　　　Release 15 Rel-16　　　　　　　　　　　　Release 16 Rel-17 　　　　　　　　　　　　Release 17 Rel-18　　　　　　　　　　　　Release 18 Rel-19　　　　　　　　　　　　Release 19 RF　　　　　　　　　　　　　　　　Radio Frequency RLC　　　　　　　　　　　　　　　　Radio Link Control RS　　　　　　　　　　　　　　　　Reference Signal RLF　　　　　　　　　　　　　　　　Radio Link Failure RSTD　　　　　　　　　　　　Reference Signal Time Difference Measurement RNTI　　　　　　　　　　　　Radio Network Temporary Identifier RO　　　　　　　　　　　　　　　　RACH Occasion RRC　　　　　　　　　　　　Radio Resource Control RRM　　　　　　　　　　　　Radio Resource Management RS　　　　　　　　　　　　　　　　Reference Signal RSRP　　　　　　　　　　　　Reference Signal Received Power RSRQ　　　　　　　　　　　　Reference Signal Receiving Quality RV　　　　　　　　　　　　　　　　Redundancy Version RX　　　　　　　　　　　　　　　　Reception SCell　　　　　　　　　　　　Secondary Cell SCG　　　　　　　　　　　　　　　　Secondary Cell Group SDT　　　　　　　　　　　　　　　　Small Data Transmission SI　　　　　　　　　　　　　　　　System Information SIB　　　　　　　　　　　　　　　　System Information Block SL　　　　　　　　　　　　　　　　Sidelink SLIV　　　　　　　　　　　　Start and Length Indicator Value SN　　　　　　　　　　　　　　　　Secondary Node SNPN　　　　　　　　　　　　Stand-alone Non-Public Network SpCell　　　　　　　　　　　　Special Cell SR　　　　　　　　　　　　　　　　Scheduling Request SRB　　　　　　　　　　　　　　　　Signaling Radio Bearer SRS　　　　　　　　　　　　　　　　Sounding Reference Signal SRI　　　　　　　　　　　　　　　　SRS Resource Indicator SSB　　　　　　　　　　　　　　　　Synchronization Signal Block SSS　　　　　　　　　　　　　　　　Secondary Synchronization Signal SS-RSRP　　　　　　　　　　　　Synchronization Signal-Reference Signal Received Power SUL　　　　　　　　　　　　　　　　Supplementary Uplink TA　　　　　　　　　　　　　　　　Timing Advance TAG　　　　　　　　　　　　　　　　Timing Advance Group TAT 　　　　　　　　　　　　Time Alignment Timer TAU　　　　　　　　　　　　　　　　Tracking Area Update TB　　　　　　　　　　　　　　　　Transport Block TCI　　　　　　　　　　　　　　　　Transmission Configuration Indication TDD　　　　　　　　　　　　Time Division Duplexing TDRA　　　　　　　　　　　　Time Domain Resource Allocation TN　　　　　　　　　　　　　　　　Terrestrial Network TPC　　　　　　　　　　　　　　　　Transmission Power Control TPMI　　　　　　　　　　　　Transmit Precoder Matrix Indication TRP　　　　　　　　　　　　　　　　Transmission Reception Point TRS 　　　　　　　　　　　　Tracking Reference Signal TRX　　　　　　　　　　　　Transmission / Reception TS　　　　　　　　　　　　　　　　Technical Specification TX　　　　　　　　　　　　　　　　Transmission UCI　　　　　　　　　　　　　　　　Uplink Control Information UE　　　　　　　　　　　　　　　　User Equipment UL　　　　　　　　　　　　　　　　Uplink UL-CG　　　　　　　　　　　　Uplink-Configured Grant UPF　　　　　　　　　　　　　　　　User Plane Function URLLC　　　　　　　　　　　　Ultra-Reliable and Low-Latency Communications USIM　　　　　　　　　　　　Universal Subscriber Identity Module USS 　　　　　　　　　　　　UE-specific Search Space UTC　　　　　　　　　　　　Coordinated Universal Time V2X　　　　　　　　　　　　　　　　Vehicle-to-Everything VSAT　　　　　　　　　　　　Very Small Aperture Terminal WUS　　　　　　　　　　　　Wake-Up Signaling XR　　　　　　　　　　　　　　　　Extended Reality

[0023] 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.

[0024] 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.

[0025] For 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 shall not be narrowly confined to what is illustrated in the drawings.

[0026] 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 one implementation,” 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.

[0027] 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.

[0028] 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.

[0029] 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.

[0030] 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.

[0031] 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).

[0032] 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.

[0033] 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), or an internet via a RAN established by one or more BSs.

[0034] 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. A UE may be referred to as a PHY / MAC / RLC / PDCP / SDAP entity. The PHY / MAC / RLC / PDCP / SDAP entity may be referred to as the UE.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] A software implementation of the technical solutions provided in the present disclosure may include computer-executable instructions and / or Artificial Intelligence (AI) / Machine Learning (ML) module(s) stored on a computer-readable medium, such as a memory or other type of storage devices. One or more microprocessors or general-purpose computers with communication processing capability may be programmed with the corresponding computer-executable instructions and may perform the disclosed network function(s), AI / ML module(s), or algorithm(s). The AI / ML module(s) may be implemented with a supervised learning approach, a semi-supervised learning approach, an unsupervised learning approach (e.g., a Transductive approach and an Inductive approach), a federated learning approach, or a Reinforcement Learning (RL) approach, but the present disclosure is not limited thereto. The computer-executable instructions associated with the AI module(s) and / or the ML module(s) may include but are not limited to, data management instructions (e.g., collection instructions, validation instructions, etc.), model monitoring and management instructions (e.g., network (NW) Key Performance Indicators (KPIs) monitoring, model input / output monitoring, model selection / switching / update / upload / download, model (de)activation, model identification, functionality selection, etc.), and / or pre-process input instructions.

[0039] In some implementations, the UE may be an AI / ML-enabled device and / or an AI / ML capable device that may be equipped with AI module(s) and / or ML module(s).

[0040] In some implementations, the BS may be an AI / ML-enabled device and / or an AI / ML capable device that may be equipped with AI module(s) and / or ML module(s).

[0041] Each cell (often referred to as a serving cell) may provide services to serve one or more UEs within its 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 plurality of cells.

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

[0043] 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.

[0044] As described above, the frame structure for NR supports 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.

[0045] 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.

[0046] 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.

[0047] Any two or more 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.

[0048] 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.

[0049] 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.

[0050] “A and / or B” in the present disclosure may refer to either A or B, both A and B, or at least one of A and B.

[0051] In this disclosure, “X / Y” may encompass the meanings of “X or Y,” “X and Y,” and “X and / or Y,” as indicated by two or more of the sentences, paragraphs, sub-bullets, points, actions, behaviors, terms, alternatives, aspects, examples, embodiments, or claims described in the following invention(s).

[0052] One aspect of the present disclosure may be applied in various contexts, including communications, communication equipment (such as mobile telephone apparatus, base station apparatus, wireless LAN apparatus, and / or sensor devices), integrated circuits (such as communication chips), and software programs, among others.

[0053] The terms “an antenna port” and “antenna ports,” as discussed in the present disclosure, may refer to “an antenna port used for transmission of PUSCH(s) / PUCCH(s)” and “antenna ports used for transmission of PUSCH(s) / PUCCH(s),” respectively.

[0054] Some of the terms, definitions, and / or abbreviations included in the present disclosure may either be sourced from existing documents (such as those from ETSI, ITU, or other sources) or may be newly created by experts from the 3GPP whenever there was a need for a precise vocabulary.

[0055] In the present disclosure, although the term “gNB” may have been used throughout the document, it should be understood that the term “gNB” may be replaced by any other type of BS (e.g., an eNB). Multiple PLMNs may operate on the unlicensed spectrum. Multiple PLMNs may share the same unlicensed carrier. The PLMNs may be public or private. Public PLMNs may include the operators or virtual operators, which may provide radio services to the public subscribers. Public PLMNs may own the licensed spectrum and may support the radio access technology on the licensed spectrum as well. Private PLMNs may include the micro-operators, factories, or enterprises, which may provide radio services to the private users (e.g., employees or machines). In some implementations, public PLMNs may support more deployment scenarios, such as carrier aggregation between licensed band NR (PCell) and NR-U (SCell), dual connectivity between licensed band LTE (PCell) and NR-U (PSCell), stand-alone NR-U, an NR cell with DL in unlicensed band and UL in licensed band, and dual connectivity between licensed band NR (PCell) and NR-U (PSCell). In some implementations, private PLMNs may mainly support the stand-alone unlicensed radio access technology (e.g., stand-alone NR-U).

[0056] Additionally, in the present disclosure, the term “reference signal” may broadly encompass various types of signals. When referring to “the sequence of signals” or “the sequence of reference signals,” these terms may be used interchangeably. The reference signal may be used for measurement, synchronization, and / or cell identification purposes. The reference signal may include, but may not be limited to, synchronization signals, discovery signals, tracking signals, measurement signals, pilot signals, beacon signals, or any other signals that may be transmitted by the cell for the UE to detect, measure, and / or decode. In some implementations, the reference signal may refer to any signal that may enable the UE to identify whether a cell may support AI / ML features, 6G and beyond RAT, or specific AI / ML use cases. The reference signal may also include composite signals that may combine multiple signal types or signal components for enhanced detection and measurement capabilities. Furthermore, the reference signal may include both periodic signals and aperiodic signals, where the periodic signals may be transmitted at regular intervals and the aperiodic signals may be transmitted based on specific triggers or conditions. The flexibility in signal types may allow the network to optimize the signaling overhead while providing sufficient information for AI / ML-capable UEs to perform efficient cell selection and reselection procedures.

[0057] Examples of some selected terms in the present disclosure are provided as follows.

[0058] User Equipment (UE): The UE may be referred to as a PHY / MAC / RLC / PDCP / SDAP entity. The PHY / MAC / RLC / PDCP / SDAP entity may be referred to as the UE.

[0059] Network (NW): The Network (NW) may include a network node, a TRP, a cell (e.g., SpCell (Special Cell), PCell, PSCell, and / or SCell), an eNB, a gNB, and / or a base station.

[0060] Serving Cell: A Serving Cell may be a PCell (Primary Cell), a PSCell, or an SCell (Secondary Cell). The serving cell may be an activated or a deactivated serving cell.

[0061] Special Cell (SpCell): A Special Cell (SpCell) for Dual Connectivity operation may refer to the PCell of the MCG (Master Cell Group) or the PSCell of the SCG (Secondary Cell Group) depending on whether the MAC entity is associated with the MCG or the SCG, respectively. Otherwise, the term Special Cell may refer to the PCell. A Special Cell may support PUCCH (Physical Uplink Control CHannel) transmission and contention-based Random Access and may always be activated.

[0062] DCI: The DCI may include downlink control information, and there may be various DCI formats used in a PDCCH. The DCI format may be a predefined format in which the downlink control information may be packed / formed and transmitted in a PDCCH.

[0063] BWP: A BWP may be a subset of the total cell bandwidth of a cell, and a Bandwidth Adaptation (BA) may be achieved by configuring the UE with BWP(s) and instructing the UE which of the configured BWPs is currently the active one. To enable a BA on the PCell, the gNB may configure the UE with UL and DL BWP(s). To enable the BA on SCells, in case of CA, the gNB may configure the UE with one or more DL BWPs (e.g., there may be no BWP in the UL). For the PCell, the initial BWP may be the BWP used for an initial access. For the SCell(s), the initial BWP may be the BWP configured for the UE to operate after an SCell activation. The UE may be configured with a first active uplink BWP by the firstActiveUplinkBWP IE. If the first active uplink BWP is configured for an SpCell, the firstActiveUplinkBWP IE field may contain the ID of the UL BWP to be activated upon performing the RRC (re)configuration. If the field is absent, the RRC (re)configuration may not impose a BWP switching. If the first active uplink BWP is configured for an SCell, the firstActiveUplinkBWP IE field may contain the ID of the uplink bandwidth part to be used upon the MAC-activation of an SCell.

[0064] The network, cell, camped cell, serving cell, base station, gNB, eNB and ng-eNB may be used interchangeably. In some implementations, some of these items may refer to the same network entity.

[0065] The RAT may include NR, LTE, E-UTRA connected to 5GC, LTE connected to 5GC, E-UTRA connected to EPC, LTE connected to EPC, and 6G RAT. The proposed mechanism may be applied for UEs in public networks, or in private networks, e.g., NPN, SNPN, or PNI-NPN.

[0066] The proposed mechanism may be used for licensed frequency and / or unlicensed frequency.

[0067] System information may refer to MIB, SIB1, and other SI. Minimum SI may include MIB and SIB1. Other SI may refer to SIB3, SIB4, SIB5, and other SIBs.

[0068] Dedicated signaling may refer to (but not limited to) RRC message(s). For example, RRC (Connection) Setup Request message, RRC (Connection) Setup message, RRC (Connection) Setup Complete message, RRC (Connection) Reconfiguration message, RRC Connection Reconfiguration message including the mobility control information, RRC Connection Reconfiguration message without the mobility control information inside, RRC Reconfiguration message including the configuration with sync, RRC Reconfiguration message without the configuration with sync inside, RRC (Connection) Reconfiguration Complete message, RRC (Connection) Resume Request message, RRC (Connection) Resume message, RRC (Connection) Resume Complete message, RRC (Connection) Reestablishment Request message, RRC (Connection) Reestablishment message, RRC (Connection) Reestablishment Complete message, RRC (Connection) Reject message, RRC (Connection) Release message, RRC System Information Request message, UE Assistance Information message, UE Capability Enquiry message, and UE Capability Information message.The RRC_CONNECTED UE, RRC_INACTIVE UE, and RRC_IDLE UE may apply the proposed implementations.

[0069] The UE may be served by a cell, e.g., a serving cell. The serving cell may serve an RRC_CONNECTED UE. The serving cell may be a suitable cell.

[0070] The PCell may be the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

[0071] The PSCell may be, for dual connectivity operation, the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure.

[0072] For a UE in RRC_CONNECTED not configured with CA / DC, there may be only one serving cell including the primary cell. For a UE in RRC_CONNECTED configured with CA / DC, the serving cells may be used to denote the set of cells including the Special Cell and all secondary cells.

[0073] The Secondary Cell may be, for a UE configured with CA, a cell providing additional radio resources on top of the Special Cell.

[0074] The Special Cell may refer to the PCell of the MCG or the PSCell of the SCG for Dual Connectivity operation, otherwise the Special Cell may refer to the PCell.

[0075] The serving cell, TRP associated with the PCI of the serving cell, TRP associated with the serving cell, TRP of a serving cell and TRP of the serving cell may be applied interchangeably.

[0076] The target cell, target serving cell, TRP associated with a PCI different from the PCI of the serving cell, and TRP associated with the target cell may be applied interchangeably. A target serving cell may be identified by a PCI or a PCI index. A UE may be configured with at most 1, 4, 8, or 32 PCI indices. Each PCI index may identify a target serving cell of the UE.

[0077] The candidate cell, neighboring cell and candidate target cell may be applied interchangeably.

[0078] The serving cell in the implementations may be a PCell, SCell or PSCell.

[0079] The target cell in the implementations may be a PCell, SCell or PSCell.

[0080] An inter-cell to the serving cell of the UE may be a neighboring cell, a cell other than the serving cell or a cell with PCI different from the PCI of the serving cell. If the UE can perform the inter-cell beam management, the UE may be in coverage of the inter-cell.

[0081] The reference signal may refer to SSB, CSI-RS, TRS, PT-RS, SRS, and DM-RS.

[0082] A timer may be running once the timer is started, until the timer is stopped or until the timer expires; otherwise the timer may not be running. A timer may be started if the timer is not running or restarted if the timer is running. A timer may always be started or restarted from the initial value of the timer. The duration of a timer may not be updated until the timer is stopped or expires, e.g., due to BWP switching. When the MAC entity applies zero value for a timer, the timer may be started and immediately expire unless explicitly stated otherwise.

[0083] Network energy saving

[0084] Network energy saving may be of great importance for environmental sustainability, to reduce environmental impact (greenhouse gas emissions), and for operational cost savings. As 5G may be becoming pervasive across industries and geographical areas, handling more advanced services and applications requiring very high data rates (e.g., XR), networks may be becoming denser, may use more antennas, larger bandwidths and more frequency bands. The environmental impact of 5G may need to stay under control, and novel solutions to improve network energy savings may need to be developed.

[0085] One of the identified key techniques may be on-demand SIB1. In legacy systems, SIB1 may always be transmitted by at least every PCell and may not be turned off. If SIB1 in a cell can be turned off, the cell may go to deep sleep mode, which may save substantial power. In some implementations, when a cell enters the deep sleep mode, the cell may deactivate certain transmission and reception functions to minimize energy consumption. If there appears a UE in RRC_IDLE / RRC_INACTIVE state that may need SIB1, for example, for accessing the cell, the UE may send an UL WUS to the NW through the cell, and the cell may then transmit SIB1. This technique may be called "on-demand SIB1" or "OD-SIB1". In some implementations, the OD-SIB1 mechanism may allow the network to dynamically control when and where to broadcast system information, thereby optimizing power consumption based on actual demand.

[0086] Timers

[0087] A timer may be running once the timer is started, until the timer is stopped or until the timer expires; otherwise, the timer may not be running. A timer may be started if the timer is not running or may be restarted if the timer is running. A timer may always be started or restarted from the initial value of the timer. The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). In some implementations, when the MAC entity applies a zero value for a timer, the timer may be started and may immediately expire unless explicitly stated otherwise.

[0088] In some implementations, when the UE applies a zero value for a timer, the timer may be started and may immediately expire unless explicitly stated otherwise. The timer mechanism may provide precise control over various procedures in the OD-SIB1 acquisition process, ensuring that the UE and the network remain synchronized in the timing aspects.

[0089] Cell selection criterion

[0090] A UE may perform cell selection according to TS 38.304 V18.3.0. In some implementations, the cell selection criterion may determine whether a cell is suitable for the UE to camp on based on measured signal quality and other parameters.

[0091] Cell reselection criterion

[0092] A UE may perform cell reselection according to TS 38.304 V18.3.0. In some implementations, the cell reselection criterion may determine when the UE may need to move from a current serving cell to a neighbor cell based on signal quality measurements and configured thresholds.

[0093] Issue description

[0094] Cell-specific on / off of SIB1 transmission has been proven to have NES gain. However, because the beamforming concept has been considered since the very first version of NR, where SIB1 may be broadcast with each SSB beam, SSB-beam-specific on / off of SIB1 transmission may provide additional NES gain.

[0095] In some implementations, consider a scenario where there may be four SSB beams, specifically SSB beams #1 to #4, being transmitted in a cell. First, the UE may receive the SSBs and may determine that the best SSB beam with the highest DL-RSRP / SS-RSRP measured by the UE is SSB beam #2. Next, the UE may find that the SIB1 or OD-SIB1 is not transmitted in the direction of the SSB beam. Then, the UE may send a request for OD-SIB1 for the SSB beam to the cell. Finally, the NES cell may start broadcasting or transmitting OD-SIB1 for SSB beam #2 while still not broadcasting or transmitting OD-SIB1 for SSB beams #1, #3 and #4. Without this beam-specific UL WUS transmission and OD-SIB transmission, the NW may have to broadcast OD-SIB1 for the directions of all the SSB beams, specifically beams #1, #2, #3 and #4, which may be unnecessary and power-consuming in some scenarios.

[0096] In some implementations, the beam-specific approach may enable more granular control over system information broadcasting, allowing the network to activate only the necessary beams based on actual UE distribution and requirements. The problem formulation and technical solutions for supporting beam-specific OD-SIB1 transmission and UL WUS transmission may be described in this disclosure.

[0097] Regarding the timing relationship between UEs sending OD-SIB1 requests and the NW starting to broadcast OD-SIB1, there may be three phases that characterize different operational states of the system: Phase 1, Phase 2, and Phase 3.

[0098] Phase 1 may represent a state where the NES cell is not broadcasting OD-SIB1, and no UE has sent UL WUS.

[0099] Phase 2 may represent a state where the NES cell is not broadcasting OD-SIB1, and some UEs have sent UL WUS.

[0100] Phase 3 may represent a state where the NES cell is broadcasting OD-SIB1.

[0101] The above problem formulation may be applied to both cell-specific and beam-specific cases, with different granularity of control.

[0102] For the cell-specific case, the three phases for each cell may be as follows. Phase 1 may occur when the NES cell is not broadcasting OD-SIB1, and no UE has sent UL WUS. Phase 2 may occur when the NES cell is not broadcasting OD-SIB1, and some UEs have sent UL WUS. Phase 3 may occur when the NES cell is broadcasting OD-SIB1.

[0103] For the beam-specific case, the three phases for each SSB may be as follows. Phase 1 may occur when the NES cell is not broadcasting OD-SIB1 for the SSB, and no UE has sent UL WUS for the SSB. Phase 2 may occur when the NES cell is not broadcasting OD-SIB1 for the SSB, and some UEs have sent UL WUS for the SSB. Phase 3 may occur when the NES cell is broadcasting OD-SIB1 for the SSB.

[0104] In some implementations, one critical issue may be how a UE knows the broadcasting status of OD-SIB1 for the cell or for the beam in Phases 1, 2 and 3. The UE may need this information to determine whether the UE needs to send a UL WUS or can directly receive the OD-SIB1.

[0105] In some implementations, another critical issue may be how a UE knows there is another UE having requested OD-SIB1 for the cell or for the beam in Phase 2. This knowledge may help the UE avoid sending redundant UL WUS requests and may improve overall system efficiency.

[0106] Solutions for beam-specific OD-SIB transmission and UL WUS transmission

[0107] For the beam-specific case, the three phases for each SSB may be characterized as follows. Phase 1 may occur when the NES cell is not broadcasting OD-SIB1 for the SSB, and no UE has sent UL WUS for the SSB. Phase 2 may occur when the NES cell is not broadcasting OD-SIB1 for the SSB, and some UEs have sent UL WUS for the SSB. Phase 3 may occur when the NES cell is broadcasting OD-SIB1 for the SSB.

[0108] In some implementations, the system may employ different alternatives to address the challenges in each phase. Alternative A may indicate the broadcasting status of OD-SIB1 corresponding to each SSB or each group of SSBs via MIB using the pdcch-ConfigSIB1 field. This alternative may be used in phases 1, 2 and 3 to provide real-time status information to UEs.

[0109] In some implementations, Alternative B may indicate the broadcasting status of OD-SIB1 corresponding to each SSB via UL WUS configuration. This alternative may also be used in phases 1, 2 and 3 and may provide status information through dedicated configuration messages.

[0110] In some implementations, Alternative C may involve monitoring from time instance X, where the UE monitors responses of UL WUS transmitted by other UEs during a specific period. This approach may help UEs detect ongoing OD-SIB1 request procedures initiated by other UEs.

[0111] In some implementations, a Cell A may be defined as a cell that may be periodically transmitting at least the SIB1 of the Cell A, which may be beam-specific or cell-specific. The Cell A may serve as an anchor cell that provides continuous service and configuration information to UEs.

[0112] In some implementations, an NES cell may be defined as a cell that may transmit SIB1 transmission in response to UL WUS from a UE. The NES cell may operate in an energy-saving mode and may activate SIB1 transmission only when requested.

[0113] In some implementations, a Cell A may broadcast the UL WUS configurations of the neighbor NES cells of the Cell A, or the NES cells that are associated with the Cell A, via system information, such as in a new SIB. Each UL WUS configuration may be associated with one or more NES cells. This broadcast mechanism may enable UEs to obtain necessary configuration information for accessing NES cells.

[0114] In some implementations, an NES cell may broadcast the UL WUS configuration of the NES cell itself and / or the UL WUS configurations of the neighbor NES cells of the NES cell via system information, such as in a new SIB, or via dedicated signaling. Each UL WUS configuration may be associated with one or more NES cells.

[0115] In some implementations regarding SSB structure, a cell, such as a Cell A or an NES cell, may transmit / broadcast one or more SSBs. An SSB transmitted by a cell, such as a Cell A or an NES cell, may include PSS, SSS and PBCH. The PBCH may include an 8-bit PHY PBCH payload and a 23-bit MIB.

[0116] In some implementations, the 23-bit MIB may include the following parameters / fields, where the fields may be listed in order: a systemFrameNumber field, a subCarrierSpacingCommon field, a ssb-SubcarrierOffset field, a dmrs-TypeA-Position field, and a pdcch-ConfigSIB1 field.

[0117] The systemFrameNumber field may be a bit string with six bits. The subCarrierSpacingCommon field may be an enumerated data type with a value as either 'scs15or60' or 'scs30or120'. The ssb-SubcarrierOffset field may be a four-bit integer with a value ranging from 0 to 15. The dmrs-TypeA-Position field may be an enumerated data type with a value as either 'pos2' or 'pos3'. The pdcch-ConfigSIB1 field may include eight bits.

[0118] In some implementations, the four MSBs of the pdcch-ConfigSIB1 field may be interpreted as controlResourceSetZero and the four LSBs may be interpreted as searchSpaceZero.

[0119] In some implementations, if kSSBequals 30 for FR1 or kSSBequals 14 for FR2, the eight bits of the pdcch-ConfigSIB1 field may be used to represent the broadcasting status of OD-SIB1 of each group of SSBs. This reuse of the pdcch-ConfigSIB1 field may provide an efficient signaling mechanism without requiring additional overhead.

[0120] In some implementations, if the maximum number of SSBs is 4 according to the band where the NES cell is located, each group of SSBs may only include one SSB. The first (leftmost / MSB) bit may correspond to the SSB with SSB index 0, the second bit may correspond to the SSB with SSB index 1, the third bit may correspond to the SSB with SSB index 2, the fourth bit may correspond to the SSB with SSB index 3, and the fifth to eighth bits may be reserved.

[0121] In some implementations, if the maximum number of SSBs is 8 according to the band where the NES cell is located, each group of SSBs may only include one SSB. The first (leftmost / MSB) bit may correspond to the SSB with SSB index 0, the second bit may correspond to the SSB with SSB index 1, the third bit may correspond to the SSB with SSB index 2, the fourth bit may correspond to the SSB with SSB index 3, the fifth bit may correspond to the SSB with SSB index 4, the sixth bit may correspond to the SSB with SSB index 5, the seventh bit may correspond to the SSB with SSB index 6, and the eighth bit may correspond to the SSB with SSB index 7.

[0122] In some implementations, if the maximum number of SSBs is 64 according to the band where the NES cell is located, each group of SSBs may include 8 SSBs. The grouping approach may allow efficient representation of a large number of SSBs within the limited bit space. The first (leftmost / MSB) bit may correspond to the SSBs with SSB indices 0 to 7, the second bit may correspond to the SSBs with SSB indices 8 to 15, the third bit may correspond to the SSBs with SSB indices 16 to 23, the fourth bit may correspond to the SSBs with SSB indices 24 to 31, the fifth bit may correspond to the SSBs with SSB indices 32 to 39, the sixth bit may correspond to the SSBs with SSB indices 40 to 47, the seventh bit may correspond to the SSBs with SSB indices 48 to 55, and the eighth bit may correspond to the SSBs with SSB indices 56 to 63.

[0123] In some implementations, if the maximum number of SSBs is equal to or more than 8, each group of SSBs may only include one SSB. The first (leftmost / MSB) bit may correspond to the SSB with the current SSB index, the second bit may correspond to the SSB with the current SSB index plus 1, the third bit may correspond to the SSB with the current SSB index plus 2, the fourth bit may correspond to the SSB with the current SSB index plus 3, the fifth bit may correspond to the SSB with the current SSB index plus 4, the sixth bit may correspond to the SSB with the current SSB index plus 5, the seventh bit may correspond to the SSB with the current SSB index plus 6, and the eighth bit may correspond to the SSB with the current SSB index plus 7. This approach means that only eight SSBs whose corresponding OD-SIB1 / SIB1 broadcast status will be provided even when the maximum number of SSBs is more than 8, and the selected SSBs may be arranged by ascending order of the current (camped) SSB index.

[0124] In some implementations, if a bit is set to '1', the bit may represent that the OD-SIB1 associated with the group of SSBs corresponding to the bit is being broadcast. If a bit is set to '0', the bit may represent that the OD-SIB1 associated with the group of SSBs corresponding to the bit is not being broadcast.

[0125] In some implementations, the MIB may further include additional fields. The cellBarred field may be an enumerated data type with a value as either 'barred' or 'notBarred'. The intraFreqReselection field may be an enumerated data type with a value as either 'allowed' or 'notAllowed'. A spare field may include one bit as a spare bit.

[0126] In some implementations, the 8-bit PHY PBCH payload may include the following bits, where the bits may be listed in order. Four bits may indicate the four LSBs of the SFN where the SSB is transmitted. One Half-frame bit may indicate whether SSBs are transmitted in the first half-frame (front half-frame) or the second half-frame (rear half-frame).

[0127] For an SSB that the UE received in FR1, one bit may be used by the UE, together with the ssb-SubcarrierOffset field provided in MIB, to determine the value of kSSB. Two bits may be reserved for future use.

[0128] For an SSB that the UE received in FR2, three bits may indicate the 3 MSBs of the SSB index of the SSB.

[0129] In some implementations, kSSBmay be a value determined based on the information indicated by PBCH. The quantity kSSBmay be the subcarrier offset from subcarrier 0 in common resource block NSSBCRBto subcarrier 0 of the SS / PBCH block.

[0130] In some implementations, in FR1 operation, kSSBmay be determined by the fifth bit in the PHY PBCH payload and the ssb-SubcarrierOffset field in the MIB. The value range of kSSBmay be from 0 to 31, inclusive.

[0131] In some implementations, in FR2 operation, kSSBmay be determined by the ssb-SubcarrierOffset field in the MIB. The value range of kSSBmay be from 0 to 15, inclusive.

[0132] In some implementations, if kSSBis between 0 and 23 (inclusive) for FR1, or if kSSBis between 0 and 11 (inclusive) for FR2, the UE may consider that the SSB is a CD-SSB (Cell-Defining SSB). The CD-SSB may be used for initial cell access and cell selection procedures.

[0133] In some implementations, a CD-SSB may always be transmitted on a frequency layer defined by a GSCN. A UE may always receive a CD-SSB on a frequency layer defined by a GSCN. This alignment with GSCN may ensure that UEs can efficiently search for and detect CD-SSBs during initial access.

[0134] In some implementations, if kSSBis between 24 and 31 (inclusive) for FR1, or if kSSBis between 12 and 15 (inclusive) for FR2, the UE may consider that the SSB is not a CD-SSB, and the pdcch-ConfigSIB1 field may indicate information about where, in the frequency domain, the UE can or cannot find a CD-SSB. This indication may help the UE locate the appropriate resources for system information acquisition.

[0135] UL WUS configuration

[0136] In some implementations, one UL WUS configuration of an NES cell may include one or more of the following parameters 1 to 16 to enable efficient OD-SIB1 acquisition:

[0137] 1. The UL WUS configuration may include the PCI of the NES cell. The PCI may uniquely identify the NES cell within a local area and may be used by the UE to distinguish between different cells.

[0138] 2. The UL WUS configuration may include the absolute frequency location of the SSBs transmitted by the NES cell. This frequency information may enable the UE to tune to the correct frequency for receiving the SSBs from the NES cell.

[0139] 3. The UL WUS configuration may include a first timer (or a duration of the first timer), denoted as timer #1, which may be used for monitoring the response of the NW to an OD-SIB1 request (UL WUS). In some implementations, timer #1 may be used for monitoring the response of the NW to an OD-SIB1 request before the UE itself sends an OD-SIB1 request or transmits a UL WUS to request OD-SIB1. This monitoring capability may allow the UE to detect whether another UE has already initiated an OD-SIB1 request procedure. In some implementations, the timer may be started and restarted when the UE successfully receives the WUS configuration and may be stopped if the UE decides to send an OD-SIB1 request by itself. In some implementations, timer #1 may be started and restarted when the UE determines that the cell reselection criterion for the NES cell is met. In some implementations, timer #1 may also be used for monitoring the response of the NW to an OD-SIB1 request after the UE itself sends an OD-SIB1 request or transmits a UL WUS to request OD-SIB1.

[0140] 4. The UL WUS configuration may include a second timer (or a duration of the second timer), denoted as timer #2, which may be used for monitoring the response of the NW to an OD-SIB1 request. In some implementations, timer #2 may be used for monitoring the response of the NW to an OD-SIB1 request after the UE itself sends an OD-SIB1 request or transmits a UL WUS to request OD-SIB1. The timer may start and restart when the UE sends an OD-SIB1 request and may be stopped if the UE receives the corresponding acknowledgement after sending the OD-SIB1 request.

[0141] 5. The UL WUS configuration may include a third timer (or a duration of the third timer), denoted as timer #3, which may be used for monitoring OD-SIB1 after the UE receives, from the NW or the NES cell, the response to an OD-SIB1 request. Timer #3 may provide a bounded waiting period for the actual OD-SIB1 transmission following the acknowledgement.

[0142] In some implementations, the proposed timer #1, timer #2, or timer #3 may be stopped upon or after the UE receives the OD-SIB1 from the NES cell. This stopping condition may ensure that the timers do not continue running unnecessarily once the desired information has been obtained.

[0143] In some implementations, the proposed timer #1, timer #2, or timer #3 may be associated with the current serving beam of the UE. In addition, timer #1, timer #2, or timer #3 may be reset if the current serving beam of the UE changes. This beam-specific timer management may ensure that the timing relationships remain appropriate for the current beam context. In some other implementations, the proposed timer #1, timer #2, or timer #3 may not be reset if the current serving beam of the UE changes, allowing for continuity in the OD-SIB1 acquisition procedure across beam changes.

[0144] 6. The UL WUS configuration may include a CORESET configuration for CORESET for Type0-PDCCH CSS set or CORESET#0. This configuration may define the time-frequency resources where the UE may monitor for control information.

[0145] 7. The UL WUS configuration may include a search space configuration for Type0-PDCCH CSS set for CORESET#0 or search space#0. The search space configuration may specify the monitoring occasions and aggregation levels for PDCCH detection.

[0146] 8. The UL WUS configuration may include a CORESET configuration for the CORESET that the UE may use for monitoring the response of the NW to an OD-SIB1 request. In some implementations, if the CORESET configuration is not provided, the UE may use CORESET#0 for monitoring the response of the NW to an OD-SIB1 request.

[0147] 9. The UL WUS configuration may include a search space configuration for the search space set that the UE may use for monitoring the response of the NW to an OD-SIB1 request. In some implementations, if the search space configuration is not provided, the UE may use search space#0 for monitoring the response of the NW to an OD-SIB1 request.

[0148] 10. The UL WUS configuration may include a downlink RSRP threshold, which may be used for selecting an SSB. In some implementations, this information may be provided by the rsrp-ThresholdSSB IE. The RSRP threshold may enable the UE to select an SSB with sufficient signal quality for reliable communication.

[0149] 11. The UL WUS configuration may include a preamble ID, which may be used for transmitting an OD-SIB1 request. In some implementations, the UE may determine the preamble ID of the OD-SIB1 request as the preamble ID provided by this information field. The specific preamble ID may allow the network to distinguish OD-SIB1 requests from other random access attempts.

[0150] 12. The UL WUS configuration may include the maximum preamble transmission times. In some implementations, this information may be provided by the preambleTransMax IE. In some implementations, the maximum preamble transmission times may be a cell-specific parameter. In some other implementations, the preambleTransMax IE may be associated with one specific beam direction (e.g., the current serving beam of the UE, which is associated with one SSB or CSI-RS). In addition, the UE may reset the maximum preamble transmission counter associated with the current serving beam upon or after the UE changes the current serving beam.

[0151] 13. The UL WUS configuration may include the number of transmitted SSBs in the NES cell and the SSB indices of the transmitted SSBs. In some implementations, the number of transmitted SSBs may be indicated by the ssb-PositionsInBurst IE. This information may help the UE understand the SSB transmission pattern of the NES cell.

[0152] 14. The UL WUS configuration may include the periodicity of SSB transmission in the NES cell. In some implementations, the periodicity of SSB transmission in the NES cell may be indicated by the ssb-periodicityServingCell IE. The periodicity information may allow the UE to align the measurement and access procedures of the UE with the SSB transmission pattern.

[0153] 15. The UL WUS configuration may include a number of RNTI values. In some implementations, this information may be indicated by a list of RNTI values. Each RNTI value in the list may serve a specific purpose in the beam-specific OD-SIB1 procedure.

[0154] In some implementations, the number of RNTI values may be the same as the number of transmitted SSBs in the NES cell. For example, if the number of transmitted SSBs is 4, the number of RNTI values may also be 4. In some implementations, each RNTI value may correspond to or be associated with an SSB. The one-to-one mapping between RNTI values and SSBs may enable beam-specific control signaling. In some implementations, the first RNTI may correspond to or be associated with the SSB with the lowest SSB index among the transmitted SSBs, as indicated by the number of transmitted SSBs in the NES cell and the SSB indices of the transmitted SSBs, such as indicated by the ssb-PositionsInBurst IE.

[0155] In some implementations, the RNTI values may be used to scramble the CRC of PDCCH / DCI. The PDCCH / DCI may be used to schedule RAR after the UE transmits an OD-SIB1 request. The beam-specific RNTI usage may allow the network to provide beam-specific responses to OD-SIB1 requests.

[0156] In some implementations, the RNTI list and the association of SSBs when different numbers of SSBs are applied (e.g., SSB number could be 4, 8, 16, 32) may be pre-defined via technical specifications. In some other implementations, the RNTI list and the association of SSBs when different numbers of SSBs are applied may be provided in the UL WUS configuration (e.g., by referring to the UL WUS configuration in 3GPP Release-19 NES working item) transmitted by a Cell A or an NES cell. The Cell A or the NES cell may then broadcast the UL WUS configuration via broadcasting or SI on-demand procedure. In some other implementations, the RNTI list and the association of SSBs when different numbers of SSBs are applied may be transmitted via UE-specific signaling (e.g., RRC signaling such as an RRCRelease message from a serving Cell A or an NES cell).

[0157] 16. The UL WUS configuration may include the broadcasting status of OD-SIB1 associated with each SSB of the NES cell. In some implementations, the broadcasting status may be represented as a bitmap. The bitmap representation may provide an efficient way to indicate the status of multiple SSBs.

[0158] In some implementations, the length of the bitmap may be equal to the number of SSBs transmitted in the cell. Each bit position in the bitmap may correspond to a specific SSB index.

[0159] In some implementations, if a bit is set to '1', the bit may represent that the OD-SIB1 associated with the SSB corresponding to the bit is being broadcast. If a bit is set to '0', the bit may represent that the OD-SIB1 associated with the SSB corresponding to the bit is not being broadcast.

[0160] Solution 1: The UE selects an SSB before checking the broadcasting status of OD-SIB1 corresponding to all SSBs

[0161] Solution 1: 1. Camping on Cell A

[0162] In some implementations, a UE may detect SSBs transmitted by a Cell A by blind detection and may then receive the SIB1 of the Cell A and may then camp on the Cell A. The camping procedure may establish the Cell A as the serving cell for the UE. Then, the UE may acquire one or more UL WUS configurations and / or one or more cell reselection configurations via system information from the Cell A. Each UL WUS configuration may be associated with one or more NES cells. The acquisition of these configurations may prepare the UE for potential access to NES cells in the vicinity.

[0163] Solution 1: 2. When the cell reselection criteria to an NES cell is met, the UE (e.g., the RRC entity of the UE) initiates OD-SIB1 acquisition procedure

[0164] After the UE acquires the one or more UL WUS configurations and the cell reselection configuration, the UE may detect and receive SSBs transmitted by an NES cell, according to the cell reselection configuration and / or a UL WUS configuration. The detection process may involve measuring the signal quality of the received SSBs. The UE may select one or more SSBs to derive the signal quality of the NES cell. The UE may then determine that the cell reselection criterion for the NES cell is met, where the cell reselection criterion may be based on the quality of the Cell A and the NES cell.

[0165] In some implementations, the UE may determine to initiate an OD-SIB1 procedure towards the NES cell to acquire the SIB1 of the NES cell and / or to determine whether the UE can camp on the NES cell or not, based on at least the PLMN identity list and the UAC information associated with the NES cell. The kSSBindicated by the one or more SSBs transmitted by the NES cell may be larger than 23 for FR1 or larger than 11 for FR2, indicating that the SSBs are not CD-SSBs. In some implementations, the kSSBindicated by the one or more SSBs transmitted by the NES cell may be 30 for FR1 or 14 for FR2. In some implementations, the OD-SIB1 procedure may be an RRC procedure managed by the RRC layer of the UE.

[0166] In some implementations, upon initiation of the OD-SIB1 procedure, the UE may determine the broadcasting status of OD-SIB1 of the NES cell. This determination may guide the subsequent actions of the UE in the OD-SIB1 acquisition process.

[0167] In some implementations, if the quality of the NES cell was derived by a single SSB, the UE may check the broadcasting status of OD-SIB1 corresponding to the SSB by checking an indication in the MIB indicated by the SSB transmitted by the NES cell or an indication in the UL WUS configuration associated with the NES cell. The indication in the MIB may be the pdcch-ConfigSIB1 field, as described in this disclosure. The indication in the UL WUS configuration may be a bitmap, as described in this disclosure.

[0168] In some implementations, if the OD-SIB1 corresponding to the SSB is being broadcast, as indicated by the broadcasting status in the MIB or the UL WUS configuration, the UE may perform the behaviors for monitoring OD-SIB1. The direct monitoring approach may be used when the OD-SIB1 is already available.

[0169] In some implementations, if the OD-SIB1 corresponding to the SSB is not being broadcast, as indicated by the broadcasting status in the MIB or the UL WUS configuration, the UE may perform the behaviors for requesting OD-SIB1. Alternatively, the UE may perform the behaviors for monitoring the response of the NW to OD-SIB1 requests sent by other UEs using Alternative 1 or Alternative 2 approaches.

[0170] In some implementations, if the OD-SIB1 corresponding to the SSB is changed to broadcast status, as indicated by the broadcasting status in the MIB or the UL WUS configuration, the UE may stop the ongoing behaviors for requesting OD-SIB1 or monitoring responses to OD-SIB1 requests sent by other UEs, and may perform the behaviors for monitoring OD-SIB1.

[0171] In some implementations, if the quality of the NES cell was derived by more than one SSB, the UE may check the broadcasting status of OD-SIB1 corresponding to the more than one SSB based on an indication in the MIB indicated by the SSB transmitted by the NES cell or an indication in the UL WUS configuration associated with the NES cell. The multi-SSB scenario may require more comprehensive status checking.

[0172] In some implementations, if there is any SSB among the more than one SSB whose corresponding OD-SIB1 is being broadcast, as indicated by the broadcasting status, the UE may perform the behaviors for monitoring OD-SIB1.

[0173] In some implementations, if no SSB among the more than one SSB has a corresponding OD-SIB1 being broadcast, as indicated by the broadcasting status in the MIB or the UL WUS configuration, the UE may perform the behaviors for requesting OD-SIB1 or for monitoring the response of the NW to OD-SIB1 requests sent by other UEs.

[0174] In some implementations, the UE may check the broadcasting status of OD-SIB1 corresponding to one or more or a subset of SSBs which are used by the UE to determine the cell quality. The selective checking approach may optimize the processing requirements.

[0175] In some implementations, the UE may check the broadcasting status of OD-SIB1 corresponding to the SSB which has the strongest DL-RSRP / SS-RSRP measurement results. In some other implementations, the UE may check the broadcasting status of OD-SIB1 corresponding to the SSB which has the strongest DL-RSRP / SS-RSRP measurement results and the nearby SSBs (e.g., the left-side SSB and right-side SSB of the strongest SSB in terms of SSB index). In some additional implementations, the UE may check the broadcasting status of OD-SIB1 corresponding to the SSBs which have the N strongest DL-RSRP / SS-RSRP measurement results, where N may be a pre-defined value or a configurable value which may be pre-configured by the serving RAN.

[0176] Solution 1: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 1

[0177] In some implementations, the UE may monitor the response of the NW before or until the first or next PRACH / RACH occasion for RA preamble transmission comes in the time domain. This monitoring period may allow the UE to detect whether another UE has already triggered OD-SIB1 transmission. If the UE receives the response of the NW before the first PRACH / RACH occasion for RA preamble transmission comes, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 1: Monitor OD-SIB1”) for monitoring OD-SIB1. If the UE has not received the response of the NW when the first PRACH / RACH occasion for RA preamble transmission comes, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 1: Request OD-SIB1”) for requesting OD-SIB1.

[0178] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by the RNTI value corresponding to the selected SSB, or a PDCCH addressed to the RNTI value corresponding to the selected SSB, or a PDCCH for RAR identified by the RNTI value corresponding to the selected SSB.

[0179] In some implementations, the response of the NW may be an RAR including a MAC subPDU with RAPID only. The RAPID-only MAC subPDU may serve as an acknowledgement without resource allocation.

[0180] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by RA-RNTI. The RA-RNTI may be calculated based on the PRACH / RACH occasion and the preamble ID used for RA preamble transmission and whether the NUL or SUL is used for RA preamble transmission.

[0181] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by SI-RNTI. The SI-RNTI may be a hexadecimal value FFFF.

[0182] In some implementations, the response of the NW may be an OD-SIB1 or SIB1 reception, such as a PDSCH carrying OD-SIB1 or SIB1.

[0183] In some implementations, the UE may receive the response of the NW in CORESET#0 provided in the UL WUS configuration and the search space set provided in the UL WUS configuration (SS#0 or the search space set for monitoring the response of the NW).

[0184] Solution 1: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 2

[0185] In some implementations, the UE may start timer #1 or timer #2 and may monitor the response of the NW when timer #1 or timer #2 is running. The timer-based approach may provide a bounded waiting period for detecting responses to other UEs' requests. If the UE receives the response of the NW when timer #1 or timer #2 is running, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 1: Monitor OD-SIB1”) for monitoring OD-SIB1. If timer #1 or timer #2 expires and the UE has not received the response of the NW, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 1: Request OD-SIB1”) for requesting OD-SIB1.

[0186] The possible formats of the response of the NW in Alternative 2 may be the same as those described for Alternative 1, including PDCCH with various RNTI scrambling options, RAR messages, and direct OD-SIB1 / SIB1 transmission. For example, in some implementations, the NW’s response may be a PDCCH with CRC scrambled by the RNTI value corresponding to the selected SSB, or a PDCCH addressed to the RNTI value corresponding to the selected SSB, or a PDCCH for RAR(s) identified by the RNTI value corresponding to the selected SSB. In some implementations, the NW’s response may be an RAR including a MAC subPDU with RAPID only. In some implementations, the NW’s response may be a PDCCH with CRC scrambled by RA-RNTI. The RA-RNTI may calculated based on the PRACH / RACH occasion and the preamble ID used for RA preamble transmission (UL WUS) and whether the NUL or SUL is used for RA preamble transmission. In some implementations, the NW’s response may be a PDCCH with CRC scrambled by SI-RNTI. The SI-RNTI may be a hexadecimal value FFFF. In some implementations, the NW’s response may be an OD-SIB1 or SIB1 reception, e.g., a PDSCH carrying OD-SIB1 or SIB1. In some implementations, the UE may receive (the) NW’s response in CORESET#0 provided in the UL WUS configuration and the search space set provided in the UL WUS configuration (SS#0 or the search space set for monitoring NW’s response),

[0187] Solution 1: Request OD-SIB1

[0188] In some implementations, the UE may initiate an RA procedure for OD-SIB1 acquisition / request on the NES cell, or the UE may transmit a preamble for OD-SIB1 acquisition / request on the NES cell. The UE may set the preamble transmission counter to 1. The initialization of the counter may track the number of transmission attempts. The UE may then perform the behaviors for UL WUS transmission.

[0189] Solution 1: UL WUS transmission

[0190] In some implementations, the UE may select an SSB among the one or more SSBs used for deriving the quality of the NES cell during the cell reselection process. The SSB selection may determine the beam direction for the UL WUS transmission. The UE may transmit an RA preamble serving as UL WUS to the NES cell. The RA preamble may be transmitted in a PRACH / RACH occasion associated with the selected SSB. The RA preamble may be transmitted using the preamble ID indicated by the UL WUS configuration associated with the NES cell, as described in this disclosure. Then, the UE may perform the behaviors for monitoring the response of the NW.

[0191] In some implementations, the SSB selection may be based on the RSRP threshold indicated by the UL WUS configuration associated with the NES cell. The RSRP-based selection may ensure adequate signal quality for successful communication.

[0192] In some implementations, if at least one of the SSBs among the one or more SSBs used for deriving the quality of the NES cell during the cell reselection process has an SS-RSRP above the rsrp-ThresholdSSB IE, the UE may select an SSB among those SSBs with SS-RSRP above the RSRP threshold; otherwise, the UE may select any SSB among the one or more SSBs used for deriving the quality of the NES cell during the cell reselection process.

[0193] In some implementations, if at least one of the SSBs has an SS-RSRP above the rsrp-ThresholdSSB IE, the UE may select an SSB above the RSRP threshold; otherwise, the UE may select any SSB.

[0194] Solution 1: Monitor response of the NW

[0195] In some implementations, the UE may start timer #2 and may monitor the response of the NW when timer #2 is running. If the UE receives the response of the NW when timer #2 is running, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 1: Monitor OD-SIB1”) for monitoring OD-SIB1. If timer #2 expires and the UE has not received the response of the NW, and if the preamble transmission counter is not equal to the maximum preamble transmission times plus one, where the maximum preamble transmission times is indicated by the UL WUS configuration associated with the NES cell, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 1: UL WUS transmission”) for UL WUS transmission again. The retransmission mechanism may provide robustness against transmission failures.

[0196] If timer #2 expires and the UE has not received the response of the NW, and if the preamble transmission counter is equal to the maximum preamble transmission times plus one, the UE may indicate a RACH problem to upper layers within the UE. If the UE or the upper layers receive the indication of RACH problem, the UE or the upper layers may consider the NES cell as barred.

[0197] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by the RNTI value corresponding to the selected SSB, or a PDCCH addressed to the RNTI value corresponding to the selected SSB, or a PDCCH for RAR identified by the RNTI value corresponding to the selected SSB.

[0198] In some implementations, the response of the NW may be an RAR including a MAC subPDU with RAPID only.

[0199] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by RA-RNTI. The RA-RNTI may be calculated based on the PRACH / RACH occasion and the preamble ID used for RA preamble transmission and whether the NUL or SUL is used for RA preamble transmission.

[0200] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by SI-RNTI. The SI-RNTI may be a hexadecimal value FFFF.

[0201] In some implementations, the response of the NW may be an OD-SIB1 or SIB1 reception, such as a PDSCH carrying OD-SIB1 or SIB1.

[0202] In some implementations, the upper layers may include the RRC layer.

[0203] Solution 1: Monitor OD-SIB1

[0204] In some implementations, the UE may start timer #3 and monitor PDCCH with CRC scrambled by SI-RNTI, following the CORESET#0 and the SS#0 provided in the UL WUS configuration. The monitoring procedure may enable the UE to receive the requested OD-SIB1. If the UE receives a PDCCH with CRC scrambled by SI-RNTI and / or correspondingly receives a PDSCH carrying SIB1, the OD-SIB1 procedure may end successfully.

[0205] In some implementations, the UE may determine whether the UE can camp on the NES cell based on the information indicated by the SIB1 of the NES cell, such as based on the PLMN identity list and UAC information. If the UE determines that the UE can camp on the NES cell, the UE may camp on the NES cell. If timer #3 expires and the UE has not received PDCCH with CRC scrambled by SI-RNTI and / or the UE has not received the SIB1 of the NES cell, the UE may consider the NES cell as barred, and the OD-SIB1 procedure may end.

[0206] In some implementations, SI-RNTI may be set to a default value, such as FFFF in hexadecimal notation.

[0207] Solution 2: The UE checks the broadcasting status of OD-SIB1 corresponding to all or a subset of SSBs before selecting an SSB

[0208] Solution 2: 1. Camping on Cell A

[0209] In some implementations, a UE may detect SSBs transmitted by a Cell A by blind detection and may then receive the SIB1 of the Cell A and may then camp on the Cell A. The camping procedure may establish the initial serving cell relationship. Then, the UE may acquire one or more UL WUS configurations and / or one or more cell reselection configurations via system information from the Cell A. Each UL WUS configuration may be associated with one or more NES cells. This configuration acquisition may prepare the UE for potential access to energy-saving cells in the vicinity.

[0210] Solution 2: 2. When the cell reselection criteria to an NES cell is met, the UE (e.g., the RRC entity of the UE) initiates OD-SIB1 acquisition procedure

[0211] After the UE acquires the one or more UL WUS configurations and the cell reselection configuration, the UE may detect and receive SSBs transmitted by an NES cell, according to the cell reselection configuration and / or a UL WUS configuration. The UE may select one or more SSBs to derive the signal quality of the NES cell. The UE may then determine that the cell reselection criterion for the NES cell is met, where the cell reselection criterion may be based on the quality of the Cell A and the NES cell.

[0212] In some implementations, the UE may then determine to initiate an OD-SIB1 procedure towards the NES cell to acquire the SIB1 of the NES cell and / or determine whether the UE can camp on the NES cell or not, based on at least the PLMN / SNPN / CSG identity list and the UAC information associated with the NES cell and / or the results of the OD-SIB1 procedure. The comprehensive evaluation may ensure that the UE camps on a suitable cell. The kSSBindicated by the one or more SSBs transmitted by the NES cell may be larger than 23 for FR1 or larger than 11 for FR2. In some implementations, the kSSBindicated by the one or more SSBs transmitted by the NES cell may be 30 for FR1 or 14 for FR2. In some implementations, the OD-SIB1 procedure may be an RRC procedure managed by the RRC layer.

[0213] In some implementations, upon initiation of the OD-SIB1 procedure, the UE may determine the broadcasting status of OD-SIB1 of the NES cell. This determination may involve checking multiple SSBs to obtain comprehensive status information.

[0214] In some implementations, the UE may check the broadcasting status of OD-SIB1 corresponding to all SSBs transmitted by the NES cell by checking an indication in the MIB indicated by the SSB transmitted by the NES cell or an indication in the UL WUS configuration associated with the NES cell. The comprehensive checking approach in Solution 2 differs from Solution 1 by examining all SSBs before making a selection decision.

[0215] In some implementations, if at least one of the SSBs with SS-RSRP above an RSRP threshold is available, the UE may first select one or more SSBs with SS-RSRP above the RSRP threshold; otherwise, the UE may select any SSB. If at least one of the selected one or more SSBs has a corresponding OD-SIB1 being broadcast, the UE may select an SSB from the selected one or more SSBs whose corresponding OD-SIB1 is being broadcast, and / or may perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor OD-SIB1”) for monitoring OD-SIB1. Otherwise, in some implementations, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Request OD-SIB1”) for requesting OD-SIB1, or the UE may perform the behaviors for monitoring the response of the NW to OD-SIB1 requests sent by other UEs using Alternative 1 or Alternative 2 (e.g., the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 1” or the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 2”).

[0216] In some implementations, if at least one of the SSBs whose corresponding OD-SIB1 is being broadcast is available, the UE may first select one or more SSBs whose corresponding OD-SIB1 is being broadcast; otherwise, the UE may not select any SSB at this stage. In the latter case, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Request OD-SIB1”) for requesting OD-SIB1 or for monitoring the response of the NW to OD-SIB1 requests sent by other UEs (e.g., by performing the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 1” or the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 2”). If at least one of the SSBs with SS-RSRP above an RSRP threshold among the one or more SSBs whose corresponding OD-SIB1 is being broadcast is available, the UE may select an SSB with SS-RSRP above the RSRP threshold from the one or more SSBs, and / or may perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor OD-SIB1”) for monitoring OD-SIB1; otherwise, the UE may select any SSB from the one or more SSBs whose corresponding OD-SIB1 is being broadcast and / or may perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor OD-SIB1”) for monitoring OD-SIB1.

[0217] In some implementations, an SSB being available may mean that an SSB is measurable according to 3GPP RAN4 specifications. The measurability criteria may ensure that only SSBs with sufficient quality are considered.

[0218] In some implementations, the indication in the MIB may be the pdcch-ConfigSIB1 field, as described in this disclosure. The indication in the UL WUS configuration may be a bitmap, as described in this disclosure.

[0219] Solution 2: SSB selection option 1

[0220] In some implementations, the UE may select an SSB according to a prioritized selection strategy that considers both signal quality and OD-SIB1 availability.

[0221] In some implementations, if at least one of the SSBs whose SS-RSRP is above an RSRP threshold and whose corresponding OD-SIB1 is being broadcast is available, the UE may select an SSB whose SS-RSRP is above an RSRP threshold and whose corresponding OD-SIB1 is being broadcast. This optimal selection may ensure both good signal quality and immediate OD-SIB1 availability. The UE may then perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor OD-SIB1”) for monitoring OD-SIB1.

[0222] In some implementations, if no SSB whose SS-RSRP is above an RSRP threshold and whose corresponding OD-SIB1 is being broadcast is available, and if at least one of the SSBs whose SS-RSRP is above an RSRP threshold and whose corresponding OD-SIB1 is not being broadcast exists, the UE may select an SSB whose SS-RSRP is above an RSRP threshold and whose corresponding OD-SIB1 is not being broadcast. The UE may then perform the behaviors (e.g., the behaviors described in section “Solution 2: Request OD-SIB1”) for requesting OD-SIB1 or for monitoring the response of the NW to OD-SIB1 requests sent by other UEs (e.g., the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 1” or the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 2”).

[0223] In some implementations, if no SSB whose SS-RSRP is above an RSRP threshold is available, and if at least one of the SSBs whose corresponding OD-SIB1 is being broadcast is available, the UE may select an SSB whose corresponding OD-SIB1 is being broadcast, and may perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor OD-SIB1”) for monitoring OD-SIB1.

[0224] In some implementations, if no SSB whose SS-RSRP is above an RSRP threshold exists and no SSB whose corresponding OD-SIB1 is being broadcast exists, the UE may select any SSB. The UE may then perform the behaviors (e.g., the behaviors described in section “Solution 2: Request OD-SIB1”) for requesting OD-SIB1 or for monitoring the response of the NW to OD-SIB1 requests sent by other UEs (e.g., the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 1” or the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 2”).

[0225] In some implementations, an SSB being available may mean that an SSB is measurable according to 3GPP RAN4 specifications.

[0226] In some implementations, the broadcasting status of each SSB may be determined by the indication in the MIB, such as the pdcch-ConfigSIB1 field, or the indication in the UL WUS configuration, such as a bitmap, as described in this disclosure.

[0227] In some implementations, the RSRP threshold may be provided in the UL WUS configuration associated with the NES cell. The RSRP threshold may be different for different SSBs, for example, in case the network vendor would like to have power saving on specific SSBs, and the respective RSRP thresholds may be provided in the WUS configuration together with the respective RNTI value.

[0228] Solution 2: SSB selection option 2-1 and 2-2

[0229] In some implementations, the UE may select an SSB according to an alternative prioritized selection strategy.

[0230] In some implementations, if at least one of the SSBs whose SS-RSRP is above an RSRP threshold is available, the UE may select an SSB whose SS-RSRP is above an RSRP threshold. If the OD-SIB1 corresponding to the selected SSB is being broadcast, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor OD-SIB1”) for monitoring OD-SIB1. If the OD-SIB1 corresponding to the selected SSB is not being broadcast, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Request OD-SIB1”) for requesting OD-SIB1 or for monitoring the response of the NW to OD-SIB1 requests sent by other UEs using Alternative 1 or Alternative 2 (e.g., the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 1” or the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 2”).

[0231] In some implementations, if no SSB whose SS-RSRP is above an RSRP threshold is available and if at least one of the SSBs whose corresponding OD-SIB1 is being broadcast is available, the UE may select an SSB whose SS-RSRP is the highest among the available SSBs and whose corresponding OD-SIB1 is being broadcast, and the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor OD-SIB1”) for monitoring OD-SIB1. If no SSB whose SS-RSRP is above an RSRP threshold and whose corresponding OD-SIB1 is being broadcast is available, the UE may select any SSB, and the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Request OD-SIB1”) for requesting OD-SIB1 or for monitoring the response of the NW to OD-SIB1 requests sent by other UEs (e.g., the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 1” or the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 2”).

[0232] In some implementations, if no SSB whose SS-RSRP is above an RSRP threshold is available and if at least one of the SSBs whose corresponding OD-SIB1 is being broadcast is available, the UE may select an SSB whose OD-SIB1 is being broadcast, and the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor OD-SIB1”) for monitoring OD-SIB1. If no SSB whose SS-RSRP is above an RSRP threshold and whose corresponding OD-SIB1 is being broadcast is available, the UE may select any SSB, and the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Request OD-SIB1”) for requesting OD-SIB1 or for monitoring the response of the NW to OD-SIB1 requests sent by other UEs (e.g., the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 1” or the behaviors described in section “Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 2”).

[0233] In some implementations, an SSB being available may mean that an SSB is measurable according to 3GPP RAN4 specifications.

[0234] In some implementations, the broadcasting status of each SSB may be determined by the indication in the MIB, such as the pdcch-ConfigSIB1 field, or the indication in the UL WUS configuration, such as a bitmap, as described in this disclosure.

[0235] In some implementations, the RSRP threshold may be provided in the UL WUS configuration associated with the NES cell. The RSRP threshold may be different for different SSBs, and the respective RSRP thresholds may be provided in the WUS configuration together with the respective RNTI value.

[0236] Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 1

[0237] In some implementations, the UE may monitor the response of the NW before the first PRACH / RACH occasion for RA preamble transmission comes in the time domain. This pre-emptive monitoring may detect ongoing OD-SIB1 procedures initiated by other UEs. If the UE receives the response of the NW before the first PRACH / RACH occasion for RA preamble transmission comes, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor OD-SIB1”) for monitoring OD-SIB1. If the UE has not received the response of the NW when the first PRACH / RACH occasion for RA preamble transmission comes, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Request OD-SIB1”) for requesting OD-SIB1.

[0238] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by the RNTI value corresponding to the selected SSB, or a PDCCH addressed to the RNTI value corresponding to the selected SSB, or a PDCCH for RAR identified by the RNTI value corresponding to the selected SSB.

[0239] In some implementations, the response of the NW may be an RAR including a MAC subPDU with RAPID only.

[0240] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by RA-RNTI. The RA-RNTI may be calculated based on the PRACH / RACH occasion and the preamble ID used for RA preamble transmission and whether the NUL or SUL is used for RA preamble transmission.

[0241] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by SI-RNTI. The SI-RNTI may be a hexadecimal value FFFF.

[0242] In some implementations, the response of the NW may be an OD-SIB1 or SIB1 reception, such as a PDSCH carrying OD-SIB1 or SIB1.

[0243] In some implementations, the response of the NW may be a PDCCH configured by SS#0 and / or CORESET#0.

[0244] In some implementations, the UE may receive the response of the NW in CORESET#0 provided in the UL WUS configuration and the search space set provided in the UL WUS configuration, such as SS#0 or the search space set for monitoring the response of the NW.

[0245] Solution 2: Monitor response of the NW to OD-SIB1 request sent by other UEs - Alternative 2

[0246] In some implementations, the UE may start timer #1 or timer #2 and may monitor the response of the NW when timer #1 or timer #2 is running. The timer-based monitoring may provide a bounded waiting period. If the UE receives the response of the NW when timer #1 or timer #2 is running, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor OD-SIB1”) for monitoring OD-SIB1. If timer #1 or timer #2 expires and the UE has not received the response of the NW, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Request OD-SIB1”) for requesting OD-SIB1.

[0247] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by the RNTI value corresponding to the selected SSB, or a PDCCH addressed to the RNTI value corresponding to the selected SSB, or a PDCCH for RAR identified by the RNTI value corresponding to the selected SSB.

[0248] In some implementations, the response of the NW may be an RAR including a MAC subPDU with RAPID only. In some other implementations, the RAR may include a NACK / ACK message for the OD-SIB1 request procedure, providing explicit feedback on the request status.

[0249] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by RA-RNTI. The RA-RNTI may be calculated based on the PRACH / RACH occasion and the preamble ID used for RA preamble transmission and whether the NUL or SUL is used for RA preamble transmission.

[0250] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by SI-RNTI. The SI-RNTI may be a hexadecimal value FFFF.

[0251] In some implementations, the response of the NW may be an OD-SIB1 or SIB1 reception, such as a PDSCH carrying OD-SIB1 or SIB1.

[0252] In some implementations, the UE may receive the response of the NW in CORESET#0 provided in the UL WUS configuration and the search space set provided in the UL WUS configuration, such as SS#0 or the search space set for monitoring the response of the NW.

[0253] Solution 2: Request OD-SIB1

[0254] In some implementations, the UE may initiate an RA procedure for OD-SIB1 acquisition / request on the NES cell, or the UE may transmit a preamble for OD-SIB1 acquisition / request on the NES cell. The UE may set the preamble transmission counter to 1. The counter initialization may track the number of transmission attempts. The UE may then perform the behaviors for UL WUS transmission.

[0255] Solution 2: UL WUS transmission

[0256] In some implementations, the UE may select an SSB among the one or more SSBs used for deriving the quality of the NES cell during the cell reselection process. The SSB selection in Solution 2 may be more informed than in Solution 1, as the UE has already checked the broadcasting status of all or a subset of SSBs. The UE may transmit an RA preamble serving as UL WUS to the NES cell. The RA preamble may be transmitted in a PRACH / RACH occasion associated with the selected SSB. The RA preamble may be transmitted using the preamble ID indicated by the UL WUS configuration associated with the NES cell, as described in this disclosure. Then, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor response of the NW”) for monitoring the response of the NW.

[0257] In some implementations, the SSB selection may be based on the RSRP threshold indicated by the UL WUS configuration associated with the NES cell and / or based on the latest broadcast status of the SSBs. The consideration of the latest broadcast status may allow the UE to adapt to dynamic changes in OD-SIB1 availability.

[0258] In some implementations, if at least one of the SSBs among the one or more SSBs used for deriving the quality of the NES cell during the cell reselection process has an SS-RSRP above the rsrp-ThresholdSSB IE, the UE may select an SSB among the one or more SSBs with SS-RSRP above the RSRP threshold; otherwise, the UE may select any SSB among the one or more SSBs used for deriving the quality of the NES cell during the cell reselection process.

[0259] In some implementations, if at least one of the SSBs has an SS-RSRP above the rsrp-ThresholdSSB IE, the UE may select an SSB above the RSRP threshold; otherwise, the UE may select any SSB.

[0260] In some implementations, if at least one of the SSBs has an SS-RSRP above the rsrp-ThresholdSSB IE, the UE may select an SSB above the RSRP threshold; otherwise, the UE may select an SSB with the highest SS-RSRP. If the OD-SIB1 corresponding to the selected SSB is being broadcast according to the broadcast status indicated by the MIB or UL WUS configuration, the UE may consider the RA procedure successfully completed and / or may indicate the SSB index of the selected SSB to upper layers of the UE, such as the RRC layer. Then, the UE may perform the behaviors for monitoring OD-SIB1.

[0261] Solution 2: Monitor response of the NW

[0262] In some implementations, the UE may start timer #2 and may monitor the response of the NW when timer #2 is running. If the UE receives the response of the NW when timer #2 is running, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: Monitor OD-SIB1”) for monitoring OD-SIB1. If timer #2 expires and the UE has not received the response of the NW, and if the preamble transmission counter is not equal to the maximum preamble transmission times plus one, where the maximum preamble transmission times is indicated by the UL WUS configuration associated with the NES cell, the UE may perform the behaviors (e.g., the behaviors described in section “Solution 2: UL WUS transmission”) for UL WUS transmission again. The retransmission mechanism may provide robustness against transmission failures.

[0263] If timer #2 expires and the UE has not received the response of the NW, and if the preamble transmission counter is equal to the maximum preamble transmission times plus one, the UE may indicate a RACH problem to upper layers within the UE. If the UE or the upper layers receive the indication of RACH problem, the UE or the upper layers may consider the NES cell as barred.

[0264] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by the RNTI value corresponding to the selected SSB, or a PDCCH addressed to the RNTI value corresponding to the selected SSB, or a PDCCH for RAR identified by the RNTI value corresponding to the selected SSB.

[0265] In some implementations, the response of the NW may be an RAR including a MAC subPDU with RAPID only.

[0266] In some implementations, the response of the NW may be a PDCCH with CRC scrambled by RA-RNTI. The RA-RNTI may be calculated based on the PRACH / RACH occasion and the preamble ID used for RA preamble transmission and whether the NUL or SUL is used for RA preamble transmission.

[0267] In some implementations, the upper layers may include the RRC layer.

[0268] Solution 2: Monitor OD-SIB1

[0269] In some implementations, the UE may start timer #3 and monitor PDCCH with CRC scrambled by SI-RNTI, following the CORESET#0 and the SS#0 provided in the UL WUS configuration and / or using the SSB that the UE selected. The monitoring procedure may be aligned with the selected SSB to ensure proper beam alignment. If the UE receives a PDCCH with CRC scrambled by SI-RNTI and / or correspondingly receives a PDSCH carrying SIB1, the OD-SIB1 procedure may end successfully.

[0270] In some implementations, the UE may determine whether the UE can camp on the NES cell based on the information indicated by the SIB1 of the NES cell, such as based on the PLMN identity list and UAC information. If the UE determines that the UE can camp on the NES cell, the UE may camp on the NES cell. If timer #3 expires and the UE has not received PDCCH with CRC scrambled by SI-RNTI and / or the UE has not received the SIB1 of the NES cell, the UE may consider the NES cell as barred, and the OD-SIB1 procedure may end.

[0271] In some implementations, SI-RNTI may be set to a default value, such as FFFF in hexadecimal notation.

[0272] FIG. 1 is a flowchart illustrating method / process 100 for uplink wake-up signal based on-demand system information acquisition in wireless communication, according to an example implementation of the present disclosure. Although actions 102, 104, 106, 108, 110, 112, and 114 are illustrated, as separate actions, represented as independent blocks in FIG. 1, these separately illustrated actions should not be construed as to be necessarily order-dependent. The order in which the actions are performed in FIG. 1 is not intended to be construed as a limitation, and any number of the disclosed blocks may be combined in any order to implement the method, or an alternative method. Each of actions 102, 104, 106, 108, 110, 112, and 114 may be performed independent of the other actions, and may be omitted in some implementations of the present disclosure. Moreover, method / process 100 may be combined with other procedures / methods described in the present disclosure. Process 100 may be performed by a UE, with each action of process 100 corresponding to an operation executed by the UE.

[0273] In action 102, the UE may receive, from a first cell, an UL WUS configuration associated with a second cell, where the UL WUS configuration includes one or more RNTI values, a first timer, a second timer, a third timer, a preamble identifier, and an RSRP threshold. The first cell may be a Cell A that periodically transmits SIB1, while the second cell may be an NES cell operating in an energy-saving mode. The UL WUS configuration may provide the necessary parameters for the UE to request OD-SIB1 from the second cell.

[0274] In action 104, the UE may receive, from the second cell, one or more first SSBs, where each first SSB of the one or more first SSBs corresponds to one of the one or more RNTI values. The reception of the SSBs may enable the UE to measure the signal quality of different beams transmitted by the second cell. Each SSB may be associated with a specific RNTI value to enable beam-specific signaling.

[0275] In action 106, the UE may select a first SSB from the one or more first SSBs with an RSRP value above the RSRP threshold. The selection process may ensure that the UE chooses an SSB with sufficient signal quality for reliable communication. If no SSB has an RSRP value above the threshold, the UE may select any available SSB.

[0276] In action 108, the UE may start the first timer. The first timer may be used to monitor whether other UEs have already initiated an OD-SIB1 request procedure, potentially eliminating the need for the UE to send a redundant request.

[0277] In action 110, the UE may monitor for a first PDCCH with CRC scrambled by the RNTI value corresponding to the selected first SSB while the first timer is running. The monitoring may detect whether the network has already responded to an OD-SIB1 request from another UE for the same SSB.

[0278] In action 112, in a case where the first PDCCH is detected before the first timer expires, the UE may stop the first timer, start the third timer, and monitor for a second PDCCH with CRC scrambled by an SI-RNTI while the third timer is running. The detection of the first PDCCH may indicate that the network is preparing to transmit OD-SIB1, and the UE may then monitor for the actual system information transmission.

[0279] In action 114, in a case where the first timer expires and the first PDCCH has not been received, the UE may transmit an UL WUS using the preamble identifier in a PRACH occasion associated with the selected first SSB, start the second timer, and monitor for the first PDCCH while the second timer is running. The transmission of the UL WUS may serve as an explicit request for OD-SIB1 from the network. The second timer may provide a bounded waiting period for the network's response to the UE's own OD-SIB1 request.

[0280] In some implementations, the UE may receive an on-demand System Information Block 1 (OD-SIB1) via a Physical Downlink Shared Channel (PDSCH) scheduled by the second PDCCH when the second PDCCH is detected. For example, when the second PDCCH with CRC scrambled by SI-RNTI is detected, the UE may receive the OD-SIB1 via a PDSCH scheduled by the second PDCCH. The SI-RNTI may have a predetermined value, such as hexadecimal FFFF, which uniquely identifies system information transmissions. The OD-SIB1 may contain essential system information including PLMN identity list, UAC information, and cell access parameters that the UE needs to determine whether the UE can camp on the NES cell. This beam-specific OD-SIB1 transmission mechanism may allow the NES cell to activate only the necessary beam for system information delivery, thereby maintaining energy efficiency. In some implementations, the UE may, in response to detecting the first PDCCH while the second timer is running, stop the second timer, start the third timer, and monitor for the second PDCCH. For example, if the UE detects the first PDCCH while the second timer is running, this may indicate that the network has acknowledged the UE’s UL WUS transmission. The UE may then stop the second timer to terminate the waiting period for the initial response, start the third timer to establish a new monitoring window, and monitor for the second PDCCH that schedules the actual OD-SIB1 transmission. This state transition may ensure proper sequencing of the OD-SIB1 acquisition procedure, where the first PDCCH serves as an acknowledgement and the second PDCCH delivers the actual system information.

[0281] In some implementations, the UL WUS configuration may further include a maximum number of preamble transmissions. The UE may maintain a counter, retransmit the UL WUS when the second timer expires without detecting the first PDCCH and the counter has not reached the maximum number, and indicate a Random Access Channel (RACH) problem to upper layers when the counter reaches the maximum number. For example, the UL WUS configuration may include a preambleTransMax parameter that specifies the maximum number of preamble transmissions. The UE may maintain a preamble transmission counter that increments with each UL WUS transmission attempt. When the second timer expires without detecting the first PDCCH, the UE may compare the counter value with the maximum number. If the counter has not reached the maximum, the UE may retransmit the UL WUS in the next available PRACH occasion associated with the selected SSB. This retransmission mechanism may provide robustness against random access failures due to collision or poor channel conditions. When the counter reaches the maximum number, the UE may indicate a RACH problem to the RRC layer, which may then consider the NES cell as barred for a certain period.

[0282] In some implementations, the UE may receive, from the second cell, a Master Information Block (MIB) including a field, where the field indicates a broadcasting status of an on-demand System Information Block 1 (OD-SIB1) when a predetermined condition related to a subcarrier offset parameter is met, and determine the broadcasting status of the OD-SIB1 based on the field. For example, the MIB transmitted by the NES cell may include the pdcch-ConfigSIB1 field, which conventionally carries CORESET#0 and search space#0 configuration. However, when the subcarrier offset parameter kSSBexceeds a certain threshold (such as greater than 23 for FR1 or greater than 11 for FR2), this field may be repurposed to indicate the broadcasting status of OD-SIB1. For example, when kSSBequals 30 for FR1 or 14 for FR2, each bit in the 8-bit pdcch-ConfigSIB1 field may correspond to a specific SSB or group of SSBs, where a bit value of '1' may indicate that OD-SIB1 is being broadcast for the corresponding SSB(s), and '0' may indicate no broadcasting. This repurposing may provide an efficient signaling mechanism without requiring additional overhead in the MIB structure.

[0283] In some implementations, the predetermined condition includes the subcarrier offset parameter exceeding a threshold value, where the threshold value is different for different frequency ranges.

[0284] In some implementations, the UL WUS configuration may further include a bitmap for one or more second SSBs of the second cell, where each bit of the bitmap indicates a broadcasting status of an on-demand System Information Block 1 (OD-SIB1) associated with a corresponding second SSB of the one or more second SSBs. For example, the UL WUS configuration may include a bitmap where the length equals the number of SSBs transmitted by the NES cell. For instance, if the NES cell transmits 4 SSBs, the bitmap may be 4 bits long, with each bit position corresponding to an SSB index. This bitmap may be updated dynamically as the broadcasting status changes, allowing UEs to have current information about which beams are actively transmitting OD-SIB1. The bitmap approach may enable fine-grained control over beam-specific system information broadcasting, supporting scenarios where different beams serve different coverage areas with varying UE populations.

[0285] In some implementations, the UE may determine that the second cell is a Network Energy Saving (NES) cell based on a subcarrier offset parameter exceeding a frequency range-specific threshold. In some implementations, the UE may consider the second cell as barred when the third timer expires without receiving an on-demand System Information Block 1 (OD-SIB1).

[0286] For example, the UE may identify an NES cell by examining the kSSBvalue derived from the received SSB. When kSSBexceeds frequency range-specific thresholds (such as greater than 23 for FR1 or greater than 11 for FR2), the UE may determine that the transmitting cell is an NES cell rather than a conventional cell. This identification may trigger the UE to apply NES-specific procedures, including the UL WUS mechanism for OD-SIB1 acquisition. The different threshold values for FR1 and FR2 may account for the different subcarrier spacing and frequency characteristics in these frequency ranges. If the third timer expires without the UE successfully receiving OD-SIB1, the UE may consider the NES cell as barred. The third timer may be started after the UE receives the first PDCCH (acknowledgement) and may define the maximum waiting period for the actual OD-SIB1 transmission. The timer expiry may indicate a failure in the OD-SIB1 delivery process, possibly due to beam misalignment, interference, or network malfunction. When the cell is considered barred, the UE may not attempt to camp on or access the cell for a certain period, which may be defined by specifications or network configuration. This barring mechanism may prevent continuous failed access attempts that would waste UE power and network resources.

[0287] Process 100 provides an efficient mechanism for on-demand system information acquisition in network energy saving scenarios. The process enables beam-specific OD-SIB1 transmission control, allowing NES cells to activate system information broadcasting only for SSBs where UEs have indicated need, significantly reducing power consumption. The multi-timer structure prevents redundant UL WUS transmissions by detecting ongoing procedures initiated by other UEs, while ensuring bounded waiting periods and proper error handling. The association between RNTI values and individual SSBs enables precise beam-level control, improving upon cell-level mechanisms. Process 100 incorporates retransmission mechanisms with configurable parameters, providing resilience against access failures while maintaining backward compatibility through existing signaling mechanisms. This comprehensive approach coordinates multiple UE access attempts while achieving energy efficiency objectives.

[0288] It should also be noted that the network device, such as the base station, may perform methods / actions corresponding to those performed by the UE. For example, the receiving actions performed by the UE may correspond to the transmitting / configuring actions of the network device; the transmitting actions performed by the UE may correspond to the receiving actions of the network device. That is, the network device and the UE may have reciprocally aligned roles in transmission and reception. For example, the base station may transmit, via a first cell to a UE, an UL WUS configuration associated with a second cell, where the UL WUS configuration includes one or more RNTI values, a first timer, a second timer, a third timer, a preamble identifier, and an RSRP threshold. The base station may further transmit, via the second cell, one or more first SSBs. Each first SSB of the one or more first SSBs may be associated with one of the one or more RNTI values. The base station may also monitor, via the second cell, for an UL WUS from the UE in a PRACH occasion associated with one of the one or more first SSBs. In response to detecting the UL WUS with the preamble identifier associated with a specific first SSB, the base station may transmit, via the second cell, a first PDCCH with CRC scrambled by the RNTI value corresponding to the specific first SSB, and transmit, via the second cell, an OD-SIB1 via a PDSCH scheduled by a second PDCCH with CRC scrambled by SI-RNTI. For example, upon detecting the UL WUS, the first PDCCH with beam-specific RNTI scrambling may serve as an acknowledgment to the requesting UE. The second PDCCH with SI-RNTI scrambling may schedule the actual OD-SIB1 transmission, maintaining compatibility with standard system information procedures while enabling on-demand delivery.

[0289] FIG. 2 is a block diagram illustrating node 200 for wireless communications, in accordance with various aspects of the present disclosure. As illustrated in FIG. 2, node 200 may include transceiver 220, processor 228, memory 234, one or more presentation components 238, and at least one antenna 236. Node 200 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. 2).

[0290] Each of the components may directly or indirectly communicate with each other over one or more buses 240. Node 200 may be a UE or a BS that performs various functions disclosed with reference to FIG. 1.

[0291] Transceiver 220 has transmitter 222 (e.g., transmitting / transmission circuitry) and receiver 224 (e.g., receiving / reception circuitry) and may be configured to transmit and / or receive time and / or frequency resource partitioning information. Transceiver 220 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. Transceiver 220 may be configured to receive data and control channels.

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

[0293] 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.

[0294] 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.

[0295] 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 aforementioned listed components should also be included within the scope of computer-readable media.

[0296] Memory 234 may include computer-storage media in the form of volatile and / or non-volatile memory. Memory 234 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. 2, memory 234 may store a computer-readable and / or computer-executable instructions 232 (e.g., software codes) that are configured to, when executed, cause processor 228 to perform various functions disclosed herein, for example, with reference to FIG. 1. Alternatively, instructions 232 may not be directly executable by processor 228 but may be configured to cause node 200 (e.g., when compiled and executed) to perform various functions disclosed herein.

[0297] Processor 228 (e.g., having processing circuitry) may include an intelligent hardware device, e.g., a Central Processing Unit (CPU), a microcontroller, an ASIC, etc. Processor 228 may include memory. Processor 228 may process data 230 and instructions 232 received from memory 234, and information transmitted and received via transceiver 220, the baseband communications module, and / or the network communications module. Processor 228 may also process information to send to transceiver 220 for transmission via antenna 236 to the network communications module for transmission to a CN.

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

[0299] 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

A User Equipment (UE), comprising:　　　　at least one processor; and　　　　at least one non-transitory computer-readable medium coupled to the 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 associated with a second cell, wherein the UL WUS configuration comprises one or more Radio Network Temporary Identifier (RNTI) values, a first timer, a second timer, a third timer, a preamble identifier, and a Reference Signal Received Power (RSRP) threshold;　　　　receive, from the second cell, one or more first Synchronization Signal Blocks (SSBs), each first SSB of the one or more first SSBs corresponding to one of the one or more RNTI values;　　　　select a first SSB from the one or more first SSBs with an RSRP value above the RSRP threshold;　　　　start the first timer;　　　　monitor for a first Physical Downlink Control Channel (PDCCH) with Cyclic Redundancy Check (CRC) scrambled by the RNTI value corresponding to the selected first SSB while the first timer is running;　　　　in a case where the first PDCCH is detected before the first timer expires:　　　　　　　　stop the first timer,　　　　　　　　start the third timer, and　　　　　　　　monitor for a second PDCCH with CRC scrambled by a System Information-RNTI (SI-RNTI) while the third timer is running; andin a case where the first timer expires and the first PDCCH has not been received:　　　　　　　　transmit an UL WUS using the preamble identifier in a Physical Random Access Channel (PRACH) occasion associated with the selected first SSB,　　　　　　　　start the second timer, and　　　　　　　　monitor for the first PDCCH while the second timer is running.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:　　　　receive an on-demand System Information Block 1 (OD-SIB1) via a Physical Downlink Shared Channel (PDSCH) scheduled by the second PDCCH when the second PDCCH is detected.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:　　　　in response to detecting the first PDCCH while the second timer is running:　　　　　　　　stop the second timer,　　　　　　　　start the third timer, and　　　　　　　　monitor for the second PDCCH.The UE of claim 1, wherein the UL WUS configuration further comprises a maximum number of preamble transmissions, and wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to:　　　　maintain a counter;　　　　retransmit the UL WUS when the second timer expires without detecting the first PDCCH and the counter has not reached the maximum number; and　　　　indicate a Random Access Channel (RACH) problem to upper layers when the counter reaches the maximum number.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:　　　　receive, from the second cell, a Master Information Block (MIB) comprising a field, wherein the field indicates a broadcasting status of an on-demand System Information Block 1 (OD-SIB1) when a predetermined condition related to a subcarrier offset parameter is met; and　　　　determine the broadcasting status of the OD-SIB1 based on the field.The UE of claim 5, wherein the predetermined condition comprises the subcarrier offset parameter exceeding a threshold value, wherein the threshold value is different for different frequency ranges.The UE of claim 1, wherein the UL WUS configuration further comprises a bitmap for one or more second SSBs of the second cell, wherein each bit of the bitmap indicates a broadcasting status of an on-demand System Information Block 1 (OD-SIB1) associated with a corresponding second SSB of the one or more second SSBs.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 that the second cell is a Network Energy Saving (NES) cell based on a subcarrier offset parameter exceeding a frequency range-specific threshold.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:　　　　consider the second cell as barred when the third timer expires without receiving an on-demand System Information Block 1 (OD-SIB1).A method performed by a User Equipment (UE), comprising:　　　　receiving, from a first cell, an uplink wake-up signal (UL WUS) configuration associated with a second cell, wherein the UL WUS configuration comprises one or more Radio Network Temporary Identifier (RNTI) values, a first timer, a second timer, a third timer, a preamble identifier, and a Reference Signal Received Power (RSRP) threshold;　　　　receiving, from the second cell, one or more first Synchronization Signal Blocks (SSBs), each first SSB of the one or more first SSBs corresponding to one of the one or more RNTI values;　　　　selecting a first SSB from the one or more first SSBs with an RSRP value above the RSRP threshold;　　　　starting the first timer;　　　　monitoring for a first Physical Downlink Control Channel (PDCCH) with Cyclic Redundancy Check (CRC) scrambled by the RNTI value corresponding to the selected first SSB while the first timer is running;　　　　in a case where the first PDCCH is detected before the first timer expires:　　　　　　　　stopping the first timer,　　　　　　　　starting the third timer, and　　　　　　　　monitoring for a second PDCCH with CRC scrambled by a System Information-RNTI (SI-RNTI) while the third timer is running; and　　　　in a case where the first timer expires and the first PDCCH has not been received:　　　　　　　　transmitting an UL WUS using the preamble identifier in a Physical Random Access Channel (PRACH) occasion associated with the selected first SSB,　　　　　　　　starting the second timer, and　　　　　　　　monitoring for the first PDCCH while the second timer is running.A base station, comprising:　　　　at least one processor; and　　　　at least one non-transitory computer-readable medium coupled to the at least one processor and storing one or more computer-executable instructions that, when executed by the at least one processor, cause the base station to:　　　　transmit, via a first cell to a User Equipment (UE), an uplink wake-up signal (UL WUS) configuration associated with a second cell, wherein the UL WUS configuration comprises one or more Radio Network Temporary Identifier (RNTI) values, a first timer, a second timer, a third timer, a preamble identifier, and a Reference Signal Received Power (RSRP) threshold;　　　　transmit, via the second cell, one or more first Synchronization Signal Blocks (SSBs), each first SSB of the one or more first SSBs being associated with one of the one or more RNTI values;　　　　monitor, via the second cell, for an UL WUS from the UE in a Physical Random Access Channel (PRACH) occasion associated with one of the one or more first SSBs; and　　　　in response to detecting the UL WUS with the preamble identifier associated with a specific first SSB:　　　　　　　　transmit, via the second cell, a first Physical Downlink Control Channel (PDCCH) with Cyclic Redundancy Check (CRC) scrambled by the RNTI value corresponding to the specific first SSB, and　　　　　　　　transmit, via the second cell, an on-demand System Information Block 1 (OD-SIB1) via a Physical Downlink Shared Channel (PDSCH) scheduled by a second PDCCH with CRC scrambled by System Information-RNTI (SI-RNTI).The base station of claim 11, wherein the UL WUS configuration further comprises a maximum number of preamble transmissions, and wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the base station to:　　　　monitor, via the second cell, for retransmissions of the UL WUS from the UE up to the maximum number of preamble transmissions.The base station of claim 11, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the base station to:　　　　transmit, via the second cell, a Master Information Block (MIB) comprising a field, wherein the field indicates a broadcasting status of an on-demand System Information Block 1 (OD-SIB1) when a predetermined condition related to a subcarrier offset parameter is met.The base station of claim 13, wherein the predetermined condition comprises the subcarrier offset parameter exceeding a threshold value, wherein the threshold value is different for different frequency ranges.The base station of claim 11, wherein the UL WUS configuration further comprises a bitmap for one or more second SSBs of the second cell, wherein each bit of the bitmap indicates a broadcasting status of an on-demand System Information Block 1 (OD-SIB1) associated with a corresponding second SSB of the one or more second SSBs.

Images