Method and apparatus for acquiring on-demand information in wireless networks

Abstract

A User Equipment (UE) for acquiring on-demand system information 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 (UL) Wake-Up Signal (WUS) configuration, the UL WUS configuration including a Physical Cell Identity (PCI) value, a frequency location, and a first resource configuration; receive, from a second cell associated with the PCI value, a Synchronization Signal Block (SSB) on the frequency location; and transmit, to the second cell, an On-Demand System Information Block 1 (OD-SIB1) request based on the first resource configuration. In addition, a method and a Base Station (BS) are also provided.

Description

METHOD AND APPARATUS FOR ACQUIRING ON-DEMAND INFORMATION IN WIRELESS NETWORKS

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

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

[0003] The present disclosure is directed to a User Equipment (UE), a Base Station (BS), and a method for acquiring on-demand information in the wireless communication networks.

[0004] In a first aspect of the present disclosure, a UE for acquiring on-demand system information 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 (UL) Wake-Up Signal (WUS) configuration, the UL WUS configuration including a Physical Cell Identity (PCI) value, a frequency location, and a first resource configuration; receive, from a second cell associated with the PCI value, a Synchronization Signal Block (SSB) on the frequency location; and transmit, to the second cell, an On-Demand System Information Block 1 (OD-SIB1) request based on the first resource configuration.

[0005] In an implementation of the first aspect, the first resource configuration includes a preamble index.

[0006] In another implementation of the first aspect, transmitting, to the second cell, the OD-SIB1 request based on the first resource configuration includes: transmitting, to the second cell, a preamble based on the preamble index.

[0007] In another implementation of the first aspect, the first resource configuration includes a Physical Random-Access CHannel (PRACH) configuration index.

[0008] In another implementation of the first aspect, the UL WUS configuration further includes a second resource configuration, and the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: monitor, on the second cell, a response to the OD-SIB1 request based on the second resource configuration; and receive, from the second cell, SIB1 in response to a reception of the response.

[0009] In another implementation of the first aspect, the second resource configuration includes a search space configuration.

[0010] In another implementation of the first aspect, the second cell includes a Network Energy Saving (NES) cell.

[0011] In a second aspect of the present disclosure, a BS for providing configuration information to a UE to facilitating on-demand system information acquisition is provided. The BS 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 BS to: transmit, to the UE, an UL WUS configuration, the UL WUS configuration including a PCI value, a frequency location, and a first resource configuration. The UL WUS configuration causes the UE to: receive, from a cell associated with the PCI value, an SSB on the frequency location; and transmit, to the cell, an OD-SIB1 request based on the first resource configuration.

[0012] In an implementation of the second aspect, the first resource configuration includes a preamble index.

[0013] In another implementation of the second aspect, the preamble index causes the UE to: transmit, to the cell, a preamble based on the preamble index.

[0014] In another implementation of the second aspect, the first resource configuration includes a PRACH configuration index.

[0015] In another implementation of the second aspect, the UL WUS configuration further includes a second resource configuration, and the second resource configuration causes the UE to: monitor, on the cell, a response to the OD-SIB1 request based on the second resource configuration; and receive, from the cell, SIB1 in response to a reception of the response.

[0016] In another implementation of the second aspect, the second resource configuration includes a search space configuration.

[0017] In another implementation of the second aspect, the cell includes a NES cell.

[0018] In a third aspect of the present disclosure, a method performed by a UE for acquiring on-demand system information is provided. The method includes: receiving, from a first cell, an UL WUS configuration, the UL WUS configuration including a PCI value, a frequency location, and a first resource configuration; 　　　　receiving, from a second cell associated with the PCI value, an SSB on the frequency location; and transmitting, to the second cell, an OD-SIB1 request based on the first resource configuration.

[0019] Aspects of the present disclosure are best understood from the following detailed disclosure and the corresponding figures. Various features are not drawn to scale and dimensions of various features may be arbitrarily increased or reduced for clarity of discussion.

[0020] FIG. 1 is a flowchart illustrating a method / process performed by a User Equipment (UE) for acquiring on-demand system information, according to an example implementation of the present disclosure.

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

[0022] Some of the abbreviations used in the present disclosure include: Abbreviation　　　　Full name 3GPP　　　　3rd Generation Partnership Project 5G　　　　5th Generation A-CSI　　　　Aperiodic Channel State Information ACK　　　　Acknowledgment AI　　　　Artificial Intelligence ARFCN　　　　Absolute Radio-Frequency Channel Number BA　　　　Bandwidth Adaptation BFR　　　　Beam Failure Recovery BM　　　　Beam Management BS　　　　Base Station BWP　　　　Bandwidth Part CA　　　　Carrier Aggregation CD-SSB　　　　Cell-Defining Synchronization Signal Block CE　　　　Control Element CN　　　　Core Network CORESET　　　　Control resource set COT　　　　Channel Occupancy Time C-RNTI　　　　Cell-Radio Network Temporary Identifier CSI　　　　Channel State Information CSI-RS　　　　Channel State Information-Reference Signal CSS　　　　Common Search Space DC　　　　Dual Connectivity DCI　　　　Downlink Control Information DCP　　　　DCI with CRC scrambled by PS-RNTI DL　　　　Downlink DL-AOA　　　　Downlink Angle-Of-Arrival DL-TDOA　　　　Downlink Time-Difference-Of-Arrival DRX　　　　Discontinuous Reception E-UTRA　　　　Evolved Universal Terrestrial Radio Access FDM　　　　Frequency-Division Multiplexing FR　　　　Frequency Range FR1　　　　Frequency Range 1 FR1-2　　　　Frequency Range 1-2 FR2　　　　Frequency Range 2 FR2-2　　　　Frequency Range 2-2 GNSS　　　　Global Navigation Satellite System GSCN　　　　Global Synchronization Channel Number GSO　　　　GeoSynchronous Orbit GW　　　　GateWay HARQ　　　　Hybrid Automatic Repeat Request HARQ-ACK　　　　HARQ Acknowledgement ID　　　　Identifier IE　　　　Information Element LCM　　　　Life Cycle Management LMF　　　　Location Management Function LTE　　　　Long Term Evolution L1 / L2 / L3　　　　Layer 1 / Layer 2 / Layer 3 MAC　　　　Medium Access Control MAC CE　　　　MAC Control Element MCG　　　　Master Cell Group MCS　　　　Modulation and Coding Scheme MIB　　　　Master Information Block MIMO　　　　Multiple Input Multiple Output ML　　　　Machine Learning Msg1　　　　Message 1 MsgA　　　　Message A MsgB　　　　Message B NACK　　　　Negative Acknowledgment NAS　　　　Non-Access Stratum NCGI　　　　NR Cell Global Identifier NGSO　　　　Non-GeoSynchronous Orbit NES　　　　Network Energy Saving NG-RAN　　　　Next Generation RAN NR　　　　New Radio NTN　　　　Non-Terrestrial Network NW　　　　Network OAM　　　　Operations, Administration and Maintenance OFDM　　　　Orthogonal Frequency Division Multiplexing OSI　　　　Other SI / On-demand SI OTT　　　　Over the Top PBCH　　　　Physical Broadcast Channel PCell　　　　Primary Cell PCI　　　　Physical Cell Identity PDCCH　　　　Physical Downlink Control Channel PDSCH　　　　Physical Downlink Shared Channel PDU　　　　Protocol Data Unit PHY　　　　Physical (layer) PL-RS　　　　Path-Loss Reference Signal PRACH　　　　Physical Random Access Channel PRS　　　　Positioning Reference Signal PS　　　　Power Saving PSS　　　　Primary Synchronization Signal PSCell　　　　Primary Secondary Cell PUCCH　　　　Physical Uplink Control Channel PUSCH　　　　Physical Uplink Shared Channel QCL　　　　Quasi Co-Location RA　　　　Random Access RACH　　　　Random Access Channel RAN　　　　Radio Access Network RAR　　　　Random Access Response Rel　　　　Release RLF　　　　Radio Link Failure RNA　　　　RAN Notification Area RNAU　　　　RAN Notification Area Update RNTI　　　　Radio Network Temporary Identifier RRC　　　　Radio Resource Control RRM　　　　Radio Resource Management RS　　　　Reference Signal RSRP　　　　Reference Signal Received Power RTT　　　　Round-Trip Time RV　　　　Redundancy Version Rx　　　　Reception SCell　　　　Secondary Cell SCG　　　　Secondary Cell Group SCS　　　　Subcarrier Spacing SFN　　　　System Frame Number SI　　　　System Information SIB　　　　System Information Block SIB1　　　　System Information Block 1 SMTC　　　　SSB Measurement Timing Configuration SpCell　　　　Special Cell SP-CSI　　　　Semi-Persistent Channel State Information SR　　　　Scheduling Request SRS　　　　Sounding Reference Signal SRI　　　　SRS Resource Indicator SS　　　　Synchronization Signal SSB　　　　Synchronization Signal Block SSS　　　　Secondary Synchronization Signal TA　　　　Timing Advance TAG　　　　Timing Advance Group TB　　　　Transport Block TBS　　　　Transport Block Size TCI　　　　Transmission Configuration Indicator TNL　　　　Transport Network Layer TR　　　　Technical Report TS　　　　Technical Specification Tx　　　　Transmission UCI　　　　Uplink Control Information UE　　　　User Equipment UL　　　　Uplink URLLC　　　　Ultra-Reliable and Low-Latency Communication WUS　　　　Wake-Up Signal 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 the purposes of consistency and ease of understanding, like features may be identified (although, in some examples, not illustrated) by the same numerals in the drawings. However, the features in different implementations may be different in other respects and may not be narrowly confined to what is illustrated in the drawings.

[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 some implementations,” or “in an example implementation,” “an implementation,” do not necessarily refer to the same implementation, although they may. Moreover, any use of phrases like “implementations” in connection with “the present application” are never meant to characterize that all implementations of the present application must include the particular feature, structure, or characteristic, and should instead be understood to mean “at least some implementations of the present application” includes the stated particular feature, structure, or characteristic. The term “coupled” is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to physical connections. The term “comprising,” when utilized, means “including, but not necessarily limited to”; it specifically indicates open-ended inclusion or membership in the so-described combination, group, series, and the equivalent.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0048] Network (NW): The NW may be 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.

[0049] Serving Cell: For a UE in the RRC_CONNECTED state, that is not configured with CA / DC, there is only one serving cell which is a primary cell. For a UE in the RRC_CONNECTED state, that is configured with CA / DC, the term ‘serving cells’ is used to denote a set of cells including the Special Cell(s) and all secondary cells.

[0050] Special Cell (SpCell): For a Dual Connectivity operation, the term Special Cell may include the PCell of the MCG or the PSCell of the SCG depending on whether the MAC entity is associated with the MCG or the SCG, respectively. Otherwise, the term Special Cell may include the PCell. A Special Cell may support the PUCCH transmission and the contention-based Random Access and may be always activated.

[0051] UE: The UE may be referred to as the PHY / MAC / RLC / PDCP / SDAP entity. The PHY / MAC / RLC / PDCP / SDAP entity may also be referred to as the UE.

[0052] Network energy saving (NES) is of great importance for environmental sustainability, as the NES helps reduce environmental impact (e.g., greenhouse gas emissions) and operational costs. As 5G becomes pervasive across industries and geographic areas, supporting more advanced services and applications requiring very high data rates (e.g., XR), networks are becoming denser, utilizing more antennas, larger bandwidths, and additional frequency bands. The environmental impact of 5G needs to be kept under control, and novel solutions to improve network energy savings must be developed.

[0053] One identified key technique is on-demand SIB1. In legacy systems, SIB1 is always transmitted by at least every PCell and cannot be turned off. If SIB1 in a cell can be turned off, the cell can enter a deep sleep mode, significantly reducing power consumption. If a UE in the RRC_IDLE or RRC_INACTIVE state requires SIB1 (e.g., to access the cell), the UE may send an UL WUS to the network, for example, through the cell, prompting the cell to transmit SIB1. This technique is referred to as “on-demand SIB1.”

[0054] In the following disclosure, the technical aspects supporting on-demand SIB1 are described.

[0055] In some implementations, a Cell A may be defined as a cell that periodically transmits at least the SIB1 of that Cell A and may also be referred to as an “anchor cell.”

[0056] In some implementations, an NES cell may be defined as a cell that transmits SIB1 in response to a UL WUS from a UE and may also be referred to as a “non-anchor cell.”

[0057] In some implementations, if a UE needs assistance from a Cell A, e.g., to obtain necessary information for on-demand SIB1 procedure to access an NES cell, the NES cell or the on-demand SIB1 feature may be considered to operate in a multi-cell scenario.

[0058] In a multi-cell scenario, the UE may obtain information, from a detected Cell A or a detected NES cell, on how to transmit an UL WUS. The UE may then transmit the UL WUS to the Cell A or the NES cell and subsequently receive on-demand SIB1 from the Cell A or the NES cell.

[0059] In a multi-cell scenario, the UE may obtain the SIB1 of one or more NES cells from the SIBs of a Cell A. Based on information from the SIB1 of a corresponding NES cell, the UE may access that NES cell.

[0060] In some implementations, if a UE does not need assistance from a Cell A or other NES cells to access an NES cell, the NES cell or the on-demand SIB1 feature may be considered to operate in a single-cell scenario.

[0061] In a single-cell scenario, the UE may obtain information on how to transmit an UL WUS from a detected NES cell. The UE may then transmit the UL WUS to request on-demand SIB1 from the NES cell and receive the (on-demand) SIB1 from the NES cell.

[0062] In some implementations, a UE may transmit an UL WUS to a Cell A or an NES cell to request on-demand SIB1 and receive the SIB1 from the NES cell. A key challenge may be how the UE obtains UL WUS configuration(s) for requesting the on-demand SIB1.

[0063] If the UE detects an SSB and identifies the SSB as originating from an NES cell, the UE may determine from which cell, e.g., the NES cell or a Cell A, the UE may obtain the UL WUS configuration(s). Once the UE obtains the UL WUS configuration(s), the UE may transmit the UL WUS to a Cell A or a NES cell (e.g., based on the UL WUS configuration(s)).

[0064] In some implementations, an NES cell may be associated with a Cell A, and a Cell A may be associated with only one NES cell.

[0065] In some implementations, a UE may detect / monitor / decode an SSB / PBCH / MIB from an NES cell to obtain, from a Cell A, UL WUS configuration(s) for requesting on-demand SIB1.

[0066] In some implementations, a UE may detect / monitor / decode an SSB / PBCH / MIB from an NES cell to obtain, from the same NES cell, UL WUS configuration(s) for requesting on-demand SIB1.

[0067] In some implementations, an NES cell may be associated with a Cell A, and a Cell A may be associated with multiple NES cells. In some implementations, one NES cell may be associated with one or more Cell A. In some implementations, a SIB from a Cell A may indicate details such as the PCIs, SSB frequencies, and / or cell selection / re-selection parameters of the associated NES cells.

[0068] In the following implementations, identifications of the cell type upon the detection of an SSB are described.

[0069] In some implementations, an NES cell may transmit / broadcast one or more SSBs. A UE may receive the one or more SSBs. The SSB(s) may include PSS, SSS, and PBCH. The PBCH may include an 8-bit PHY PBCH payload and a 23-bit MIB.

[0070] In some implementations, the 23-bit MIB may include the following parameters / fields, listed in order: 　　　　- 　　　　systemFrameNumber: a bit string with six bits; 　　　　- 　　　　subCarrierSpacingCommon: an enumerated data type with a value of either ‘scs15or60’ or ‘scs30or120’; 　　　　　　　　- ssb-SubcarrierOffset: a four-bit integer with a value ranging from 0 to 15; 　　　　　　　　- dmrs-TypeA-Position: an enumerated data type with a value of either ‘pos2’ or ‘pos3’; 　　　　　　　　- pdcch-ConfigSIB1: eight bits, with the four most significant bits (MSBs) as controlResourceSetZero and the four least significant bits (LSBs) as searchSpaceZero: 　　　　　　　　　　　　i) controlResourceSetZero: four bits; and 　　　　　　　　　　　　ii) searchSpaceZero: four bits; 　　　　　　　　- cellBarred: an enumerated data type with a value of either ‘barred’ or ‘notBarred’; 　　　　　　　　- intraFreqReselection: an enumerated data type with a value of either ‘allowed’ or ‘notAllowed’; and 　　　　　　　　- spare: one bit, a spare bit.

[0071] In some implementations, the 8-bit PHY PBCH payload may include the following bits, listed in order: 　　　　　　　　- Four bits indicating the four LSBs of the SFN where the SSB is transmitted; 　　　　　　　　- One half-frame bit indicating whether SSBs are transmitted in the first half-frame (e.g., front half-frame) or the second half-frame (e.g., rear half-frame); 　　　　　　　　- For an SSB the UE received in FR1: 　　　　　　　　　　　　i) One bit that the UE may use, together with ssb-SubcarrierOffset provided in the MIB, to determine the value of kSSB; and 　　　　　　　　　　　　ii) Two bits, which are reserved. 　　　　　　　　- For an SSB the UE received in FR2: 　　　　　　　　　　　　i) Three bits indicating the three MSBs of the SSB index of the SSB.

[0072] In some implementations, kSSBmay represent a value determined based on information indicated by PBCH. The value kSSBmay denote the subcarrier offset from subcarrier 0 in common resource block NCRBSSBto subcarrier 0 of the SS / PBCH block.

[0073] In some implementations, in FR1 operation, kSSBmay be determined by the fifth bit in the PHY PBCH payload and ssb-SubcarrierOffset in the MIB. The value range of kSSBmay be 0 ≦ kSSB≦ 31.

[0074] In some implementations, in FR2 operation, kSSBmay be determined by ssb-SubcarrierOffset in the MIB. The value range of kSSBmay be 0 ≦ kSSB≦ 15.

[0075] In some implementations, if kSSBsatisfies 0 ≦ kSSB≦ 23 for FR1 or 0 ≦ kSSB≦ 11 for FR2, the UE may consider the SSB to be a CD-SSB.

[0076] In some implementations, the CD-SSB may (always) be transmitted on a frequency layer defined by a GSCN. In some implementations, a UE may (always) receive the CD-SSB on a frequency layer defined by a GSCN.

[0077] IMPLEMENTATIONS FOR A UE TO IDENTIFY A CELL IS A CELL A AND TO OBTAIN UL WUS CONFIGURATIONS

[0078] In some implementations, if kSSBsatisfies 24 ≦ kSSB≦ 31 for FR1 or 12 ≦ kSSB≦ 15 for FR2, the UE may consider the SSB not to be a CD-SSB, and pdcch-ConfigSIB1 may indicate information about where, in the frequency domain, the UE can or cannot find a CD-SSB.

[0079] An issue that needs resolution may be how a UE identifies / determines whether an SSB is transmitted from a Cell A (Case 1) or an NES cell (Case 2). Another issue that needs resolution may be how the UE obtains UL WUS configuration(s) for Case 1 and Case 2, respectively.

[0080] In some implementations, an SSB may indicate whether the cell defined by the SSB is a Cell A or an NES cell. If the cell is an NES cell, the SSB may further indicate whether the NES cell operates in a single-cell scenario or a multi-cell scenario. For example, in a multi-cell scenario, a UE may detect an SSB from a Cell A but, due to reasons such as unified access control (UAC) barring, may not enter a connected mode with or access the Cell A; then the UE may detect an SSB from an NES cell. For example, in a single-cell scenario, a UE may detect only an SSB from a single NES cell.

[0081] In some implementations, if the cell is an NES cell operating in a single-cell scenario, the SSB may further indicate information about the UL WUS configuration(s) that the UE may use to transmit the UL WUS to request on-demand SIB1. In some implementations, if the cell is an NES cell operating in a multi-cell scenario, the SSB may further indicate information about the associated Cell A.

[0082] It should be noted that the definition of CD-SSB in legacy technical specifications may be modified.

[0083] In some implementations, a UE may receive one or more SSBs indicating a first PCI value on a first frequency location / grid defined by a first GSCN. If kSSBindicated by the SSB satisfies kSSB≦ 23 for FR1 or kSSB≦ 11 for FR2, and / or if cellBarred is set to ‘notBarred’, the UE may consider the cell (e.g., defined by the SSB) to be a Cell A. The UE may then receive DCI (e.g., a DCI format 1_0 with CRC scrambled by SI-RNTI) on a PDCCH according to CORESET#0 and search space#0, which are provided by pdcch-ConfigSIB1 indicated by the SSB(s). The DCI may schedule a PDSCH reception. The UE may then receive the PDSCH scheduled by the DCI, and the PDSCH may carry SIB1. The UE may acquire SIBX from the cell following legacy OSI behaviors. If the SIB1 and / or the SIBX include one or more specific parameters / configurations, the UE may consider the cell (e.g., defined by the SSB) to be a Cell A with one or more associated NES cells.

[0084] In some implementations, if the SIB1 and / or SIBX include one or more specific parameters, the UE may consider the cell (e.g., defined by the SSB) to be a Cell A that has / supports one or more associated NES cells.

[0085] In some implementations, the UE may receive a SIB that provides UL WUS configuration(s) of the (associated) NES cells. In some implementations, the UE may receive SIB1 and another SIB that provides all or part of the UL WUS configuration(s) of the (associated) non-anchor cells (e.g., NES cells). The SIB may be SIB1, SIB2, SIB3, SIB4, SIB5, or another type.

[0086] <ONE-TO-ONE MAPPING>

[0087] In some implementations, the SIB1 and / or SIBX may include UL WUS configuration(s) for the associated NES cell.

[0088] In some implementations, the UL WUS may be a PRACH / preamble.

[0089] In some implementations, the UL WUS configuration(s) may include one or more of the following: 　　　　　　　　- PCI information, which may be a PCI value; 　　　　　　　　- Absolute frequency of the SSBs of the corresponding non-anchor cell (e.g., NES cell,) which may be represented by ARFCN or GSCN; 　　　　　　　　- NCGI of the associated NES cell; 　　　　　　　　- The number of SSBs per RACH occasion; 　　　　　　　　- The number of preambles per SSB; 　　　　　　　　- PRACH (or preamble) periodicity; 　　　　　　　　- Starting offset relative to a timing reference, e.g., SFN 0; 　　　　　　　　- Preamble index; 　　　　　　　　- PRACH (or preamble) format; 　　　　　　　　- Total number of RA preambles; 　　　　　　　　- PRACH configuration index 　　　　　　　　- Number of PRACH (or preamble) transmission occasions Frequency-Division Multiplexed (FDMed) in one time instance; 　　　　　　　　- Offset of lowest PRACH (or preamble) transmission occasion in frequency domain with respect to PRB 0; 　　　　　　　　- Power ramping steps for PRACH (or preamble); 　　　　　　　　- The target power level at the network receiver side or PRACH transmit power; 　　　　　　　　- CORESET configuration for CORESET for Type0-PDCCH CSS set or CORESET#0; and 　　　　　　　　- Search space configuration for Type0-PDCCH CSS set for CORESET#0 or search space#0.

[0090] In some implementations, some of the above contents of UL WUS configuration(s) may be carried by SIB1, and / or some of the above contents of UL WUS configuration(s) may be carried by SIBX.

[0091] In some implementations, the contents of UL WUS configuration(s) may be distributed across SIB1 and SIBX (e.g., some content appended in SIB1 and some in SIBX). A label may be provided if the content is configured for UL WUS configuration(s). For example, a new field WUS-info (e.g., 1 bit) may be configured as “true.” If the field is absent or configured as “false,” the UE may recognize the content / information as for legacy purposes. In some implementations, all contents of UL WUS configuration(s) may be provided via an existing SIBX or a new SIBX. The field may not be needed if a new SIBX is used.

[0092] In some implementations, SIB1 may provide scheduling information for SIBX, which includes the UL WUS configuration(s) and other parameters for network energy-saving functionality. Only the UE supporting the on-demand SIB1 request procedure or (Rel-19) NES functionality may be configured / enabled to detect and receive the SIBX for UL WUS configuration reception.

[0093] In some implementations, a UE that does not support the on-demand SIB1 request procedure or (Rel-19) NES functionality does not need to receive SIBX.

[0094] In some implementations, the SIBX may be associated with a system information area ID (e.g., with areascope={true}), meaning that the UL WUS configuration(s) or other NES-related parameters may be reusable when the UE reselects to other cell(s).

[0095] In some implementations, the SIBX may be broadcast by the RAN via (e.g., continuous) broadcasting, via an SI on-demand procedure, or via UE-specific control signaling (e.g., RRC signaling).

[0096] In some implementations, the above contents of UL WUS configuration(s) may be carried by SIBX.

[0097] <ONE-TO-MANY MAPPING, CELL A-SPECIFIC CONFIGRATION>

[0098] In some implementations, the SIB1 and / or SIBX may include Cell A-specific UL WUS configuration(s) that the UE may use to request on-demand SIB1 for all associated NES cells.

[0099] In some implementations, the UL WUS may be a PRACH / preamble.

[0100] In some implementations, the UL WUS configuration(s) may include one or more of the following: 　　　　　　　　- PCI information, which may be a PCI value or a logical index of a PCI list provided in a SIB of the Cell A; 　　　　　　　　- Absolute frequency of the SSBs of the corresponding NES cell, which may be represented by ARFCN or GSCN; 　　　　　　　　- NCGI of the associated NES cell(s), NCGI list(s), or physical cell identity list(s) of the associated cell(s); 　　　　　　　　- The number of SSBs per RACH occasion; 　　　　　　　　- The number of preambles per SSB; 　　　　　　　　- PRACH periodicity; 　　　　　　　　- Starting offset relative to a timing reference, e.g., SFN 0; 　　　　　　　　- Preamble index; 　　　　　　　　- PRACH format; 　　　　　　　　- Total number of RA preambles; 　　　　　　　　- PRACH (or preamble) configuration index; 　　　　　　　　- Number of PRACH (or preamble) transmission occasions FDMed in one time instance; 　　　　　　　　- Offset of lowest PRACH (or preamble) transmission occasion in frequency domain with respect to PRB 0; 　　　　　　　　- Power ramping steps for PRACH (or preamble); 　　　　　　　　- The target power level at the network receiver side or PRACH (or preamble) transmit power; 　　　　　　　　- CORESET configuration for CORESET for Type0-PDCCH CSS set or CORESET#0; 　　　　　　　　- Search space configuration for Type0-PDCCH CSS set for CORESET#0 or search space#0; 　　　　　　　　- Tolerance timer configuration; 　　　　　　　　- Prohibit timer configuration; and 　　　　　　　　- (Revised) prohibit timer.

[0101] The tolerance timer configuration may include settings for the tolerance timer used by the UE to prevent the UE from spending excessive time requesting the on-demand SIB1. In some implementations, the tolerance timer configuration may include the duration of the tolerance timer. In some implementations, the tolerance timer may start if the UE receives the tolerance timer configuration. In some implementations, the tolerance timer may start if the UE transmits the UL WUS to the NES cell. In some implementations, the UE performs (re)cell search if the tolerance timer expires. In some implementations, the UL WUS / tolerance timer configuration(s) may be released if the tolerance timer expires.

[0102] The prohibit timer configuration may include settings for the prohibit timer used by the UE to prevent the UE from transmitting the UL WUS too frequently. In some implementations, the prohibit timer configuration may include the duration of the prohibit timer. When the prohibit timer starts, the UE may not transmit the UL WUS to the Cell A or the NES cell for the configured duration. In some implementations, the UE may transmit the UL WUS to the NES cell, and the prohibit timer may start if the UE receives the prohibit timer configuration from the NES cell. In some implementations, the UE may transmit the UL WUS to the NES cell, and the prohibit timer may start if the prohibit timer has expired or has not yet started. In some implementations, the prohibit timer may stop if the UE receives a response associated with the previous UL WUS from the NES cell. The response may refer to the requested SIB1 or a reply indicating successful decoding of the UL WUS. In some implementations, the UL WUS / tolerance timer / prohibit timer configuration may be released if the UE successfully detects the requested SIB1. In some implementations, the UL WUS / tolerance timer / prohibit timer configuration may be released if the tolerance timer expires.

[0103] In some implementations, a (revised) prohibit timer exists. If the UE transmits the UL WUS to the Cell A or an NES cell (e.g., as indicated by the PCI or the PCI list), the UE may start the prohibit timer. While the prohibit timer is running, the UE may not transmit another UL WUS to the Cell A or the NES cell(s) associated with the Cell A. Additionally, the UE may monitor PDCCH / DCI scheduling based on CORESET#0 and search space#0 provided by the SIB1 of the Cell A or by the UL WUS configuration(s), and / or the UE may monitor on-demand SIB1 transmitted by the Cell A or the NES cell. If the prohibit timer expires and the UE has not received the on-demand SIB1, the UE may transmit the UL WUS to the Cell A, the NES cell, another NES cell, or any Cell A again. If the UE receives the on-demand SIB1 while the prohibit timer is running, the UE may stop the prohibit timer and / or consider the on-demand SIB1 procedure or the RA procedure successfully completed.

[0104] In some implementations, some of the above contents of UL WUS configuration(s) may be carried by SIB1, and some of the above contents of UL WUS configuration(s) may be carried by SIBX.

[0105] In some implementations, the contents of UL WUS configuration(s) may be distributed across SIB1 and SIBX (e.g., some content appended in SIB1 and some in SIBX). A label may be provided if the content is configured for the UL WUS configuration(s). For example, a new field WUS-info (e.g., 1 bit) may be configured as “true.” If the field is absent or configured as “false,” the UE may recognize the content / information as for legacy purposes. In some implementations, all contents of UL WUS configuration(s) may be provided via an existing SIBX or a new SIBX. The field may not be needed if a new SIBX is used.

[0106] In some implementations, the contents of UL WUS configuration(s) may be carried by SIBX.

[0107] <ONE-TO-MANY MAPPING, NES CELL-SPECIFIC CONFIGRATION>

[0108] In some implementations, if the SIB1 and / or SIBX includes a number of UL WUS configurations for on-demand SIB1 (e.g., Nwus), the UE may consider the cell to be a Cell A with that number of associated NES cells. Each UL WUS configuration for on-demand SIB1 may correspond to an associated NES cell or a group of associated NES cell(s).

[0109] In some implementations, the number of UL WUS configurations (e.g., Nwus) may be one.

[0110] In some implementations, the number of UL WUS configurations may be a positive integer, e.g., one, two, or three.

[0111] In some implementations, the number of UL WUS configurations may range from one to a pre-defined maximum number of NES cells associated with the Cell A.

[0112] In some implementations, the pre-defined maximum numbers of associated NES cells in FR1 and FR2 may differ.

[0113] In some implementations, a single intra-frequency associated NES cell may exist.

[0114] In some implementations, the number Nwusmay be configurable by the serving RAN.

[0115] In some implementations, the number of UL WUS configurations may range from one to four.

[0116] In some implementations, the number of UL WUS configurations may range from one to six.

[0117] In some implementations, the number of UL WUS configurations may range from one to eight.

[0118] In some implementations, the UL WUS may be one or more PRACHs / preambles, which, in some implementations, may also be a subset of the RACH configuration(s) of the (serving) Cell A.

[0119] In some implementations, each UL WUS configuration may be the SIB1 of the corresponding NES cell.

[0120] In some implementations, an UL WUS configuration for on-demand SIB1 may include one or more of the following: 　　　　　　　　- PCI information, which may be a PCI value or a logical index of a PCI list provided in a SIB of the Cell A; 　　　　　　　　- Absolute frequency of the SSBs of the corresponding NES cell, which may be represented by (NR / E-UTRA) ARFCN or GSCN; 　　　　　　　　- Configuration index; 　　　　　　　　- NCGI of the associated Cell A; 　　　　　　　　- The number of SSBs per RACH occasion; 　　　　　　　　- The number of preambles per SSB; 　　　　　　　　- PRACH (or preamble) periodicity; 　　　　　　　　- Starting offset relative to a timing reference, e.g., SFN 0; 　　　　　　　　- Preamble index; 　　　　　　　　- PRACH (or preamble) format; 　　　　　　　　- Total number of RA preambles; 　　　　　　　　- PRACH (or preamble) configuration index; 　　　　　　　　- Number of PRACH (or preamble) transmission occasions FDMed in one time instance; 　　　　　　　　- Offset of lowest PRACH (or preamble) transmission occasion in frequency domain with respect to PRB 0; 　　　　　　　　- Power ramping steps for PRACH (or preamble); 　　　　　　　　- The target power level at the network receiver side or PRACH transmit power; 　　　　　　　　- CORESET configuration for CORESET for Type0-PDCCH CSS set or CORESET#0; 　　　　　　　　- Search space configuration for Type0-PDCCH CSS set for CORESET#0 or search space#0; 　　　　　　　　- Tolerance timer configuration; and 　　　　　　　　- Prohibit timer configuration.

[0121] The configuration index may correspond to each NES cell-specific UL WUS configuration, and the NES cell may indicate the index under the MIB by reinterpreting some existing information fields (allowing the UE to determine which NES cell the UL WUS configuration applies to). In some implementations, only a UE, that supports or is capable of the NES or on-demand SIB1 request procedures, may reinterpret the (predefined) existing information fields to obtain useful information (e.g., for NES / on-demand SIB1). A UE not supporting or not capable of the NES or on-demand SIB1 request procedures may choose not to reinterpret or ignore these existing information fields. In some implementations, a UE may switch between interpretation approaches if the UE’s capabilities are changed / updated / modified.

[0122] The tolerance timer configuration may include settings for the tolerance timer used by the UE to prevent the UE from spending excessive time requesting the on-demand SIB1. In some implementations, the tolerance timer configuration may include the duration of the tolerance timer. In some implementations, the tolerance timer may start if the UE receives the tolerance timer configuration. In some implementations, the tolerance timer may start if the UE transmits the UL WUS to the NES cell. In some implementations, the UE may perform (re)cell search if the tolerance timer expires. In some implementations, the UL WUS / tolerance timer configuration may be released if the tolerance timer expires.

[0123] The prohibit timer configuration may include settings for the prohibit timer used by the UE to prevent the UE from transmitting UL WUS too frequently. In some implementations, the prohibit timer configuration may include the duration of the prohibit timer. When the prohibit timer starts, the UE may not transmit UL WUS to the NES cell for the configured duration. In some implementations, the UE may transmit the UL WUS to the NES cell, and the prohibit timer may start if the UE receives the prohibit timer configuration from the NES cell. In some implementations, the UE may transmit the UL WUS to the NES cell, and the prohibit timer may start if the prohibit timer has expired. In some implementations, the prohibit timer may stop if the UE receives a response associated with the previous UL WUS from the NES cell. The response may refer to the requested SIB1 or a reply indicating successful decoding of the UL WUS. In some implementations, the UL WUS / tolerance timer / prohibit timer configuration may be released if the UE successfully detects the requested SIB1. In some implementations, the UL WUS / tolerance timer / prohibit timer configuration may be released if the tolerance timer expires.

[0124] In some implementations, some of the above contents of UL WUS configuration(s) may be carried by SIB1, and some of the above contents of UL WUS configuration(s) may be carried by SIBX.

[0125] In some implementations, if (multiple) UL WUS configurations are provided in SIB1 and (multiple) UL WUS configurations are provided in SIBX, the first UL WUS configuration in SIB1 may be associated with the first UL WUS configuration in SIBX, the second UL WUS configuration in SIB1 may be associated with the second UL WUS configuration in SIBX, and so on. In some implementations, the numbers of UL WUS configurations provided in SIB1 and SIBX may be the same.

[0126] In some implementations, the above contents of UL WUS configuration(s) may be carried by SIBX.

[0127] IMPLEMENTATIONS FOR A UE TO IDENTIFY A CELL AS AN NES CELL OPERATING IN MULTI-CELL OR SINGLE-CELL SCENARIO AND OBTAIN INFORMATION OF THE ASSOCIATED CELL A

[0128] In some implementations, a UE may receive one or more SSBs indicating a first PCI value on a first frequency location / grid defined by a first GSCN. If the spare bit is set to ‘1’, the UE may consider the cell to be an NES cell with an associated Cell A and / or may consider the SSB(s) as a CD-SSB and may select the NES cell during cell selection / reselection procedures. The UE may determine that information about the associated Cell A is indicated by kSSB, cellBarred, pdcch-ConfigSIB1, the last two or three bits in the PHY PBCH payload, and / or intraFreqReselection.

[0129] In some implementations, a UE may receive one or more SSBs indicating a first PCI value on a first frequency location / grid defined by a first GSCN. If the spare bit is set to ‘1’ and kSSB= 30 for FR1 or kSSB= 14 for FR2, the UE may consider the cell to be an NES cell with an associated Cell A and / or may consider the SSB(s) as a CD-SSB and may select the NES cell during cell selection / reselection procedures. The UE may determine that information about the associated Cell A is indicated by cellBarred, pdcch-ConfigSIB1, the last two or three bits in the PHY PBCH payload, and / or intraFreqReselection.

[0130] In some implementations, a UE may receive one or more SSBs indicating a first PCI value on a first frequency location / grid defined by a first GSCN. If cellBarred is set to ‘barred’ and the spare bit is set to ‘1’, the UE may consider the cell to be an NES cell with an associated Cell A and / or may consider the SSB(s) as a CD-SSB and may select the NES cell during cell selection / reselection procedures. The UE may determine that information about the associated Cell A is indicated by kSSB, pdcch-ConfigSIB1, ssb-SubcarrierOffset, the last two or three bits in the PHY PBCH payload, and / or intraFreqReselection.

[0131] In some implementations, a UE may receive one or more SSBs indicating a first PCI value on a first frequency location / grid defined by a first GSCN. If kSSB= 30 for FR1 or kSSB= 14 for FR2, the UE may consider the cell to be an NES cell with an associated Cell A and / or may consider the SSB(s) as a CD-SSB and may select the NES cell during cell selection / reselection procedures. The UE may determine that information about the associated Cell A is indicated by the spare bit, cellBarred, pdcch-ConfigSIB1, the two reserved PHY PBCH payload bits for FR1, and / or intraFreqReselection.

[0132] In some implementations, a UE may receive one or more SSBs indicating a first PCI value on a first frequency location / grid defined by a first GSCN. If cellBarred is set to ‘barred’ and kSSB= 30 for FR1 or kSSB= 14 for FR2, the UE may consider the cell to be an NES cell with an associated Cell A and / or may consider the SSB(s) as a CD-SSB and may select the NES cell during cell selection / reselection procedures. The UE may determine that information about the associated Cell A is indicated by the spare bit, pdcch-ConfigSIB1, the two reserved PHY PBCH payload bits for FR1, and / or intraFreqReselection.

[0133] In some implementations, a UE may receive one or more SSBs indicating a first PCI value on a first frequency location / grid defined by a first GSCN. If cellBarred is set to ‘barred’, the spare bit is set to ‘1’, and the LSB / MSB of pdcch-ConfigSIB1 is set to ‘0’, the UE may consider the cell to be an NES cell with an associated Cell A and / or may consider the SSB(s) as a CD-SSB and may select the NES cell during cell selection / reselection procedures. The UE may determine that information about the associated Cell A is indicated by the seven LSBs / MSBs of pdcch-ConfigSIB1, kSSB, ssb-SubcarrierOffset, the last two or three bits of the PHY PBCH payload, and / or intraFreqReselection. In some implementations, if cellBarred is set to ‘barred’, the spare bit is set to ‘1’, and the LSB / MSB of pdcch-ConfigSIB1 is set to ‘1’, the UE may consider the cell to be an NES cell without an associated Cell A and / or may consider the SSB(s) as a CD-SSB and may select the NES cell during cell selection / reselection procedures. The UE may determine that the UL WUS configuration(s) for on-demand SIB1 are indicated by the seven LSBs / MSBs of pdcch-ConfigSIB1, kSSB, ssb-SubcarrierOffset, and / or the last two or three bits of the PHY PBCH payload.

[0134] In some implementations, a UE may receive one or more SSBs indicating a first PCI value on a first frequency location / grid defined by a first GSCN. If cellBarred is set to ‘barred’, the spare bit is set to ‘1’, and the LSB / MSB of pdcch-ConfigSIB1 is set to ‘1’, the UE may consider the cell to be an NES cell with an associated Cell A and / or may consider the SSB(s) as a CD-SSB and may select the NES cell during cell selection / reselection procedures. The UE may determine that information about the associated Cell A is indicated by the seven LSBs / MSBs of pdcch-ConfigSIB1, kSSB, ssb-SubcarrierOffset, the last two or three bits of the PHY PBCH payload, and / or intraFreqReselection. In some implementations, if cellBarred is set to ‘barred’, the spare bit is set to ‘1’, and the LSB / MSB of pdcch-ConfigSIB1 is set to ‘0’, the UE may consider the cell to be an NES cell without an associated Cell A and / or may consider the SSB(s) as a CD-SSB and may select the NES cell during cell selection / reselection procedures. The UE may determine that the UL WUS configuration(s) for on-demand SIB1 are indicated by the seven LSBs / MSBs of pdcch-ConfigSIB1, kSSB, ssb-SubcarrierOffset, and / or the last two or three bits of the PHY PBCH payload.

[0135] In some implementations, if cellBarred is set to ‘barred’ and the spare bit is set to ‘0’, the UE may consider the cell to be barred. In some implementations, the UE may perform intra-frequency and / or inter-frequency cell reselection if intraFreqReselection is set to ‘allowed’. In some implementations, the UE may perform inter-frequency cell reselection if intraFreqReselection is set to ‘notAllowed’. The kSSBmay be used to indicate information about the GSCN on which the UE may or may not find a CD-SSB.

[0136] In some implementations, an NES cell and the associated Cell A may operate in different frequency ranges, e.g., FR1, FR2, FR2-2, or FR3.

[0137] In some implementations, information about the associated Cell A, indicated by an SSB transmitted by an NES cell in a multi-cell scenario, may include one or more of the following (a) to (f):

[0138] (a) The PCI of the associated Cell A.

[0139] In some implementations, the PCI may be determined by combining kSSB, cellBarred, ssb-SubcarrierOffset, the spare bit, pdcch-ConfigSIB1, intraFreqReselection, and / or the last two or three bits of the PHY PBCH payload and interpreting it / them as a PCI value. The PCI value may range from 0 to 1007 and may consist of ten bits.

[0140] (b) One or more frequency range indicator bit(s).

[0141] In some implementations, the frequency range indicator bit may be one bit.

[0142] In some implementations, if the frequency range indicator bit is set to ‘0’, the UE may determine that the associated Cell A operates in FR1. If the frequency range indicator bit is set to ‘1’, the UE may determine that the associated Cell A operates in FR2.

[0143] In some implementations, if the frequency range indicator bit is set to ‘1’, the UE may determine that the associated Cell A operates in FR1. If the frequency range indicator bit is set to ‘0’, the UE may determine that the associated Cell A operates in FR2.

[0144] In some implementations, if the frequency range indicator bit is set to ‘0’, the UE may determine that the associated Cell A operates in the same frequency range as where the SSB of the NES cell is received. If the frequency range indicator bit is set to ‘1’, the UE may determine that the associated Cell A operates in a different frequency range from where the SSB of the NES cell is received.

[0145] For example, if the SSB of the NES cell is received in FR1 and the frequency range indicator bit is set to ‘0’, the UE may determine that the associated Cell A operates in FR1.

[0146] For example, if the SSB of the NES cell is received in FR1 and the frequency range indicator bit is set to ‘1’, the UE may determine that the associated Cell A operates in FR2.

[0147] For example, if the SSB of the NES cell is received in FR2 and the frequency range indicator bit is set to ‘0’, the UE may determine that the associated Cell A operates in FR2.

[0148] For example, if the SSB of the NES cell is received in FR2 and the frequency range indicator bit is set to ‘1’, the UE may determine that the associated Cell A operates in FR1.

[0149] In some implementations, if the frequency range indicator bit is set to ‘1’, the UE may determine that the associated Cell A operates in the same frequency range as where the SSB of the NES cell is received. If the frequency range indicator bit is set to ‘0’, the UE may determine that the associated Cell A operates in a different frequency range from where the SSB of the NES cell is received.

[0150] For example, if the SSB of the NES cell is received in FR1 and the frequency range indicator bit is set to ‘0’, the UE may determine that the associated Cell A operates in FR2.

[0151] For example, if the SSB of the NES cell is received in FR1 and the frequency range indicator bit is set to ‘1’, the UE may determine that the associated Cell A operates in FR1.

[0152] For example, if the SSB of the NES cell is received in FR2 and the frequency range indicator bit is set to ‘0’, the UE may determine that the associated Cell A operates in FR1.

[0153] For example, if the SSB of the NES cell is received in FR2 and the frequency range indicator bit is set to ‘1’, the UE may determine that the associated Cell A operates in FR2.

[0154] In some implementations, the frequency range indicator bits may be two bits.

[0155] In some implementations, if the frequency range indicator bits indicate a first codepoint (e.g., ‘00’) or a first value (e.g., 0), the UE may determine that the associated Cell A operates in a first frequency range (e.g., FR1).

[0156] In some implementations, if the frequency range indicator bits indicate a second codepoint (e.g., ‘01’) or a second value (e.g., 1), the UE may determine that the associated Cell A operates in a second frequency range (e.g., FR2).

[0157] In some implementations, if the frequency range indicator bits indicate a third codepoint (e.g., ‘10’) or a third value (e.g., 2), the UE may determine that the associated Cell A operates in a third frequency range (e.g., FR3).

[0158] In some implementations, if the frequency range indicator bits indicate a fourth codepoint (e.g., ‘11’) or a fourth value (e.g., 3), the UE may determine that the associated Cell A operates in a fourth frequency range (e.g., FR2-2).

[0159] (c) A second GSCN.

[0160] In some implementations, the second GSCN may be relative to the first frequency location / grid (e.g., on which the UE receives the SSB of the NES cell).

[0161] In some implementations, the UE may determine that SSBs transmitted by the associated Cell A exist on a second frequency location / grid defined by the second GSCN.

[0162] (d) A GSCN range.

[0163] In some implementations, the GSCN range may be relative to the first frequency location / grid (on which the UE receives the SSB of the NES cell).

[0164] In some implementations, the UE may determine that SSBs transmitted by the associated Cell A exist on a second frequency location / grid on a second GSCN within the GSCN range.

[0165] (e) An index to several tables containing several pre-defined (relative) GSCNs or GSCN ranges.

[0166] In some implementations, the GSCN range may be relative to the first frequency location / grid (on which the UE receives the SSB of the NES cell).

[0167] In some implementations, the UE may determine that SSBs transmitted by the associated Cell A exist on a second frequency location / grid on a second GSCN within the GSCN range.

[0168] (f) An SSB time and / or frequency offset between Cell A and NES cell.

[0169] In some implementations, the SSB frequency offset may be a number of PRBs between the first / last PRB of the SSB transmitted by the NES cell and the first / last PRB of the SSB transmitted by the Cell A.

[0170] In some implementations, the UE may determine the SSB transmitted by the associated Cell A by adding and / or subtracting the SSB frequency offset.

[0171] In some implementations, the SSB time offset may be a number of symbols, slots, or SFNs between the first / last symbol / slot / SFN of the SSB transmitted by the NES cell and the first / last symbol / slot / SFN of the SSB transmitted by the Cell A.

[0172] In some implementations, the SSB time offset may be a number of basic time units between the start / end of the first symbol of the SSB transmitted by the NES cell and the start / end of the last symbol of the SSB transmitted by the Cell A.

[0173] In some implementations, the UE may determine the SSB transmitted by the associated Cell A by adding and / or subtracting the SSB time offset.

[0174] In some implementations, the UL WUS configuration(s) indicated by an SSB transmitted by an NES cell in a single-cell scenario may include one or more of the following (a) to (f):

[0175] (a) Time Division Duplex (TDD) configuration of the NES cell, which may indicate the slot format, including which slots are used for downlink (e.g., DL slots), which slots are used for uplink (e.g., UL slots), which slot(s) is / are flexible slot(s), which symbols in a flexible slot are used for downlink (e.g., DL symbols), and which symbols in a flexible slot are used for uplink (e.g., UL symbols). All symbols in a DL slot may be used for downlink (e.g., DL symbols), and all symbols in a UL slot may be used for uplink (e.g., UL symbols).

[0176] It should be noted that, in legacy systems, the UE may obtain the TDD configuration of the cell only from SIB1. After knowing the slot format (i.e., which slots and symbols are used for downlink and uplink), the UE may determine that PRACH transmission is possible only in UL slots and / or UL symbols. However, at this stage, the UE may lack knowledge of SIB1. If the cell operates in TDD and the UE transmits the UL WUS arbitrarily (e.g., in DL slots / symbols or UL slots / symbols), interference may occur. Providing the TDD configuration or slot format to the UE before transmitting the UL WUS may thus be beneficial.

[0177] (b) Tolerance timer configuration, which may include settings for the tolerance timer used by the UE to prevent the UE from spending excessive time requesting on-demand SIB1. In some implementations, the tolerance timer configuration may include the duration of the tolerance timer. In some implementations, the tolerance timer may start if the UE receives the tolerance timer configuration. In some implementations, the tolerance timer may start if the UE transmits the UL WUS to the NES cell. In some implementations, the UE may perform (re)cell search if the tolerance timer expires. In some implementations, the UL WUS / tolerance timer configuration may be released if the tolerance timer expires.

[0178] (c) Prohibit timer configuration, which may include settings for the prohibit timer used by the UE to prevent the UE from transmitting the UL WUS too frequently. In some implementations, the prohibit timer configuration may include the duration of the prohibit timer. When the prohibit timer starts, the UE may not transmit the UL WUS to the NES cell for the configured duration. In some implementations, the UE may transmit the UL WUS to the NES cell, and the prohibit timer may start if the UE receives the prohibit timer configuration from the NES cell. In some implementations, the UE may transmit the UL WUS to the NES cell, and the prohibit timer may start if the prohibit timer has expired. In some implementations, the prohibit timer may stop if the UE receives a response associated with the previous UL WUS from the NES cell. The response may refer to the requested SIB1 or a reply indicating successful decoding of the UL WUS. In some implementations, the UL WUS / tolerance timer / prohibit timer configuration may be released if the UE successfully detects the requested SIB1. In some implementations, the UL WUS / tolerance timer / prohibit timer configuration may be released if the tolerance timer expires.

[0179] (d) An UL WUS configuration from a set of pre-defined UL WUS configurations (e.g., pre-defined in technical specifications).

[0180] In some implementations, a set of pre-defined UL WUS configurations or a pre-defined table of UL WUS configurations may be specific to each frequency range.

[0181] In some implementations, the number of pre-defined UL WUS configurations in the set may be two.

[0182] (e) An index from a pre-defined table containing multiple UL WUS configurations, where two, three, or four pre-defined tables may exist, each corresponding to a frequency range.

[0183] In some implementations, if the number of pre-defined tables is two, one table may apply to FR1 and one to FR2.

[0184] In some implementations, if the number of pre-defined tables is three, one table applies to FR1, one to FR2, and one to FR2-2.

[0185] In some implementations, if the number of pre-defined tables is four, one table may apply to FR1, one to FR2, one to FR2-2, and one to FR1-2.

[0186] In some implementations, the UE may determine to use the table corresponding to the frequency range where the SSB is detected / received and may use the UL WUS configuration in the table as indicated by the index.

[0187] In some implementations, a RACH configuration associated with a corresponding index of the pre-defined table that the UE may use to determine how to transmit an UL WUS for requesting on-demand SIB1. In some implementations, the RACH configuration may include one or more of the following: 　　　　　　　　- The number of SSBs per RACH occasion; 　　　　　　　　- The number of preambles per SSB; 　　　　　　　　- PRACH (or preamble) periodicity; 　　　　　　　　- Starting offset relative to a timing reference, e.g., SFN 0; 　　　　　　　　- Preamble index; 　　　　　　　　- PRACH (or preamble) format; 　　　　　　　　- Total number of RA preambles; 　　　　　　　　- PRACH (or preamble) configuration index; 　　　　　　　　- Number of PRACH transmission occasions FDMed in one time instance; 　　　　　　　　- Offset of lowest PRACH transmission occasion in frequency domain with respect to PRB 0; 　　　　　　　　- Power ramping steps for PRACH (or preamble); 　　　　　　　　- The target power level at the network receiver side or PRACH (or preamble) transmit power; 　　　　　　　　- CORESET configuration for CORESET for Type0-PDCCH CSS set or CORESET#0; and 　　　　　　　　- Search space configuration for Type0-PDCCH CSS set for CORESET#0 or search space#0.

[0188] (f) A RACH configuration, which may be appended with or without the indicated index of a pre-defined table and may be used by the UE to determine how to transmit an UL WUS for requesting on-demand SIB1.

[0189] In some implementations, the RACH configuration may include one or more of the following: 　　　　　　　　- The number of SSBs per RACH occasion; 　　　　　　　　- The number of preambles per SSB; 　　　　　　　　- PRACH periodicity; 　　　　　　　　- Starting offset relative to a timing reference, e.g., SFN 0; 　　　　　　　　- Preamble index; 　　　　　　　　- PRACH format; 　　　　　　　　- Total number of RA preambles; 　　　　　　　　- PRACH configuration index; 　　　　　　　　- Number of PRACH transmission occasions FDMed in one time instance; 　　　　　　　　- Offset of lowest PRACH transmission occasion in frequency domain with respect to PRB 0; 　　　　　　　　- Power ramping steps for PRACH; 　　　　　　　　- The target power level at the network receiver side or PRACH transmit power; 　　　　　　　　- CORESET configuration for CORESET for Type0-PDCCH CSS set or CORESET#0; and 　　　　　　　　- Search space configuration for Type0-PDCCH CSS set for CORESET#0 or search space#0.

[0190] In some implementations, the UE may receive one or more SSBs and determine whether the cell defined by these SSBs or associated with these SSBs is a Cell A, an NES cell operating in a single-cell scenario, or an NES cell operating in a multi-cell scenario.

[0191] In some implementations, if the cell is a Cell A, the UE may obtain one or more SIBs (e.g., SIB1 and / or SIBX) from the Cell A. These SIBs may include one or more UL WUS configurations, each corresponding to an NES cell. If the SIB1 and / or SIBX include at least one UL WUS configuration, the UE may determine whether to transmit an UL WUS to an NES cell or to the Cell A based on specific criteria, such as RSRP criteria.

[0192] In some implementations, the UE may measure the downlink (DL) RSRP of the SSBs transmitted by the NES cell(s) and / or the Cell A. The UE may select an SSB with an RSRP above an RSRP threshold or the RSRP threshold configured in the corresponding UL WUS configuration, or the UE may select an SSB with the largest RSRP. The UE may then transmit an UL WUS to the corresponding NES cell or the Cell A using the PRACH / preamble occasion(s) / resource(s) corresponding to the selected SSB.

[0193] In some implementations, the UE may measure the RSRP of the SSBs transmitted by the NES cell(s) and / or the Cell A. The UE may select an SSB among the SSBs transmitted by the NES cell(s) and / or the Cell A based on a criterion. If the UE selects an SSB transmitted by an NES cell, the UE may transmit an UL WUS to the corresponding NES cell using the PRACH / preamble occasion(s) / resource(s) provided by the corresponding UL WUS configuration. If the UE selects an SSB transmitted by the Cell A, the UE may initiate an RA procedure for the Cell A and / or transmit PRACH / preamble to the Cell A using the PRACH / preamble occasion(s) / resource(s) provided by the SIB1 of the Cell A.

[0194] In some implementations, the criterion may be “the RSRP of the selected SSB must be above an RSRP threshold.” If more than one SSB satisfies this criterion, the UE may select any SSB satisfying this criterion (e.g., based on UE implementation).

[0195] In some implementations, the criterion may be “the RSRP of the selected SSB must be above the RSRP threshold configured in the corresponding UL WUS configuration.” If more than one SSB satisfies this criterion, the UE may select any SSB satisfying this criterion (e.g., based on UE implementation).

[0196] In some implementations, the criterion may be “the RSRP of the selected SSB must have the largest RSRP value.”

[0197] In some implementations, if the cell is an NES cell operating in a single-cell scenario, the UE may obtain the UL WUS configuration from the SSB transmitted by this NES cell. The UE may determine whether to transmit an UL WUS to the NES cell based on specific criteria, such as RSRP criteria.

[0198] In some implementations, the UE may measure the RSRP of the SSB(s) transmitted by the NES cell. The UE may select an SSB with an RSRP above an RSRP threshold or the RSRP threshold configured in the corresponding UL WUS configuration. The UE may then transmit an UL WUS to the NES cell using the PRACH / preamble occasion(s) / resource(s) corresponding to the selected SSB.

[0199] In some implementations, if the cell is an NES cell operating in a multi-cell scenario, the UE may obtain information about the Cell A from the SSB transmitted by this NES cell. The UE may then obtain one or more SIBs (e.g., SIB1 and / or SIBX) from the associated Cell A. The UE may determine whether to transmit an UL WUS to the NES cell or to the Cell A based on specific criteria, such as RSRP criteria.

[0200] In some implementations, the UE may measure the RSRP of the SSBs transmitted by the NES cell(s) and / or the Cell A. The UE may select an SSB with an RSRP above an RSRP threshold or the RSRP threshold configured in the corresponding UL WUS configuration. The UE may then transmit an UL WUS to the corresponding NES cell or the Cell A using the PRACH / preamble occasion(s) / resource(s) corresponding to the selected SSB.

[0201] In some implementations, the UE may measure the RSRP of the SSBs transmitted by the NES cell(s) and / or the Cell A. The UE may select an SSB among the SSBs transmitted by the NES cell(s) and / or the Cell A based on a criterion. If the UE selects an SSB transmitted by an NES cell, the UE may transmit an UL WUS to the corresponding NES cell using the PRACH / preamble occasion(s) / resource(s) provided by the corresponding UL WUS configuration. If the UE selects an SSB transmitted by the Cell A, the UE may initiate an RA procedure for the Cell A and / or transmit PRACH / preamble to the Cell A using the PRACH / preamble occasion(s) / resource(s) provided by the SIB1 of the Cell A.

[0202] In some implementations, the criterion may be “the RSRP of the selected SSB must be above an RSRP threshold.” If more than one SSB satisfies this criterion, the UE may select any SSB satisfying this criterion (e.g., based on UE implementation).

[0203] In some implementations, the criterion may be “the RSRP of the selected SSB must be above the RSRP threshold configured in the corresponding UL WUS configuration.” If more than one SSB satisfies this criterion, the UE may select any SSB satisfying this criterion (e.g., based on UE implementation).

[0204] In some implementations, the criterion may be “the RSRP of the selected SSB must have the largest RSRP value.”

[0205] Multiple implementations to support on-demand SIB1 are described. With the techniques described, NES functionalities may be achieved.

[0206] In some implementations, for the case where the first SSB a UE detects (after being powered on) is from a Cell A, action(s) executed by the UE may include: 　　　　　　　　receiving, from a first cell (e.g., Cell A), a first plurality of SSBs; 　　　　　　　　receiving, from the first cell (e.g., Cell A), DCI scheduling a PDSCH reception; 　　　　　　　　receiving, from the first cell (e.g., Cell A), a first message including an UL WUS configuration of a second cell (e.g., NES cell); 　　　　　　　　receiving, from the second cell (NES cell), a second plurality of SSBs; and / or 　　　　　　　　determining whether to transmit an UL WUS to the first cell (e.g., Cell A) or the second cell (e.g., NES cell) based on the measurement result of the first plurality of SSBs and the second plurality of SSBs and based on the UL WUS configuration corresponding to the second cell.

[0207] In some implementations, for the case where the first SSB the UE detects (after being powered on) is from an NES cell, action(s) executed by the UE may include: 　　　　　　　　receiving, from a first cell (e.g., NES cell), a first plurality of SSBs; 　　　　　　　　in the case where the first plurality of SSBs indicates the presence of a second cell, the first plurality of SSBs further indicates information about the second cell (e.g., Cell A), and: 　　　　　　　　　　　　receiving, from the second cell (e.g., Cell A), a second plurality of SSBs; 　　　　　　　　　　　　determining whether to transmit an UL WUS to the first cell (e.g., NES cell) based on the measurement result of the first plurality of SSBs and the second plurality of SSBs and based on the UL WUS configuration; 　　　　　　　　in the case where the first plurality of SSBs indicates the absence of a second cell, the first plurality of SSBs further indicates an UL WUS configuration, and: 　　　　　　　　　　　　determining whether to transmit an UL WUS to the first cell (e.g., NES cell) based on the measurement result of the first plurality of SSBs and based on the UL WUS configuration.

[0208] FIG. 1 is a flowchart illustrating a method / process 100 performed by a UE for acquiring on-demand system information, according to an example implementation of the present disclosure.

[0209] In the action 102, the process 100 may start by receiving, from a first cell, UL WUS configuration(s), the UL WUS configuration(s) may include a PCI value, a frequency location, and a first resource configuration. Specifically, the UL WUS configuration(s) may include information of a second cell, and resource-related information for acquiring On-Demand System Information Block 1 (OD-SIB1) from the second cell. From an aspect of the first cell, the first cell, which served as an anchor cell of the UE, may transmit the UL WUS configuration(s) to the UE.

[0210] In some implementations, the first cell may be an anchor cell. In some implementations, the first cell may be a Cell A that periodically transmits at least the SIB1.

[0211] In some implementations, the first resource configuration may be used for requesting the OD-SIB1 from the second cell. In some implementations, the first resource configuration may include a preamble index. In some implementations, the first resource configuration may include a Physical Random-Access CHannel (PRACH) configuration index.

[0212] In some implementations, the UE may receive, from the first cell, the UL WUS configuration(s) in an idle mode (e.g., RRC_IDLE) or an inactive mode (e.g., RRC_INACTIVE).

[0213] In the action, 104, the process 100 may receive, from a second cell associated with the PCI value, SSB on the frequency location. Specifically, the UE may receive SSB from a second cell based on information carried in the US WUS configuration(s) received from the first cell.

[0214] In some implementations, the second cell may be a non-anchor cell. In some implementations, the second cell may be an NES cell that transmits SIB1 in response to a UL WUS from a UE.

[0215] Upon receiving the SSB from the second cell, the UE may complete synchronization with the second cell (e.g., in both time and frequency domains).

[0216] In the action, 106, the process 100 may transmit, to the second cell, an OD-SIB1 request based on the first resource configuration.

[0217] In some implementations, transmitting the OD-SIB1 request based on the first resource configuration include transmitting a preamble based on the preamble index provided in the first resource configuration. In some implementations, the OD-SIB1 request may include a random access (RA) preamble (e.g., generated by the UE based on the preamble index provided in the first resource configuration).

[0218] In some implementations, the OD-SIB1 request may be transmitted on a PRACH occasion (e.g., determined by the UE based on the PRACH configuration index provided in the first resource configuration), enabling the second cell to identify and respond with the OD-SIB1 transmission.

[0219] In some implementations, the OD-SIB1 request may be considered to be an UL WUS configured by the UL WUS configuration(s) received in the action 102.

[0220] In some implementations, the UL WUS configuration(s) received in action 102 may further include a second resource configuration, which may be used for monitoring a response of the OD-SIB1 from the second cell l, enabling the subsequent reception of the SIB1. In some implementations, the second resource configuration may include a search space configuration.

[0221] In some implementations, the second resource configuration may be obtained by the UE from other resource(s) (e.g., from other cell than the first cell, from other message(s), etc.)

[0222] Once the UE obtains the second resource configuration, the process 100 may further include actions 108 and 110.

[0223] In the action, 108, the process 100 may monitor, on the second cell, a response to the OD-SIB1 request based on the second resource configuration.

[0224] In some implementations, upon reception of the OD-SIB1 request, the second cell may be triggered by the OD-SIB1 request and transmit a response to the OD-SIB1 request for providing information on the subsequent transmission of the SIB1.

[0225] In some implementations, the response may include resource-related information of the SIB1. In some implementations, the response may include DCI. In some implementations, the response may include an RA response (RAR).

[0226] In some implementations, the UE may monitor the response to the OD-SIB1 request based on the search space configuration (e.g., search space ID, CORESET, etc.) provided in the second resource configuration.

[0227] In the action, 110, the process 100 may receive, from the second cell, SIB1 in response to a reception of the response. The process 100 may then end.

[0228] In some implementations, the second cell may transmit SIB1 to the UE according to the resource-related information provided in the response. As such, the UE may receive, from the second cell, SIB1 in response to a reception of the response, and the SIB1 may be referred to as an OD-SIB1.

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

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

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

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

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

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

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

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

[0237] The 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. The processor 228 may include memory. The processor 228 may process the data 230 and the instructions 232 received from the memory 234, and information transmitted and received via the transceiver 220, the baseband communications module, and / or the network communications module. The processor 228 may also process information to send to the transceiver 220 for transmission via the antenna 236 to the network communications module for transmission to a CN.

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

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

Claims

1. A User Equipment (UE) for acquiring on-demand system information, the 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 (UL) Wake-Up Signal (WUS) configuration, the UL WUS configuration comprising a Physical Cell Identity (PCI) value, a frequency location, and a first resource configuration; 　　　　　　　　receive, from a second cell associated with the PCI value, a Synchronization Signal Block (SSB) on the frequency location; and 　　　　　　　　transmit, to the second cell, an On-Demand System Information Block 1 (OD-SIB1) request based on the first resource configuration.

2. The UE of claim 1, wherein the first resource configuration comprises a preamble index.

3. The UE of claim 2, wherein transmitting, to the second cell, the OD-SIB1 request based on the first resource configuration comprises: 　　　　transmitting, to the second cell, a preamble based on the preamble index.

4. The UE of claim 1, wherein the first resource configuration comprises a Physical Random-Access CHannel (PRACH) configuration index.

5. The UE of claim 1, wherein: 　　　　the UL WUS configuration further comprises a second resource configuration, and 　　　　the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　　　　　monitor, on the second cell, a response to the OD-SIB1 request based on the second resource configuration; and 　　　　　　　　receive, from the second cell, SIB1 in response to a reception of the response.

6. The UE of claim 5, wherein the second resource configuration comprises a search space configuration.

7. The UE of claim 1, wherein the second cell comprises a Network Energy Saving (NES) cell.

8. A Base Station (BS) for providing configuration information to a User Equipment (UE) to facilitating on-demand system information acquisition, the BS 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 BS to: 　　　　　　　　transmit, to the UE, an Uplink (UL) wake-up signal (WUS) configuration, the UL WUS configuration comprising a physical cell identity (PCI) value, a frequency location, and a first resource configuration, 　　　　wherein the UL WUS configuration causes the UE to: 　　　　　　　　receive, from a cell associated with the PCI value, a synchronization signal block (SSB) on the frequency location; and 　　　　　　　　transmit, to the cell, an On-Demand System Information Block 1 (OD-SIB1) request based on the first resource configuration.

9. The BS of claim 8, wherein the first resource configuration comprises a preamble index.

10. The BS of claim 9, wherein the preamble index causes the UE to: 　　　　transmit, to the cell, a preamble based on the preamble index.

11. The BS of claim 8, wherein the first resource configuration comprises a Physical Random-Access CHannel (PRACH) configuration index.

12. The BS of claim 8, wherein: 　　　　the UL WUS configuration further comprises a second resource configuration, and 　　　　the second resource configuration causes the UE to: 　　　　　　　　monitor, on the cell, a response to the OD-SIB1 request based on the second resource configuration; and 　　　　　　　　receive, from the cell, SIB1 in response to a reception of the response.

13. The BS of claim 12, wherein the second resource configuration comprises a search space configuration.

14. The BS of claim 8, wherein the cell comprises a Network Energy Saving (NES) cell.

15. A method performed by a User Equipment (UE) for acquiring on-demand system information, the method comprising: 　　　　receiving, from a first cell, an Uplink (UL) Wake-Up Signal (WUS) configuration, the UL WUS configuration comprising a Physical Cell Identity (PCI) value, a frequency location, and a first resource configuration; 　　　　receiving, from a second cell associated with the PCI value, a Synchronization Signal Block (SSB) on the frequency location; and 　　　　transmitting, to the second cell, an On-Demand System Information Block 1 (OD-SIB1) request based on the first resource configuration.

Images