Method and apparatus for system information block type 1 (SIB1) request operation

Abstract

A method performed by a User Equipment (UE) for performing a System Information Block Type 1 (SIB1) request operation is provided. The method camps on a first cell. The method receives, from the first cell, a Wake-Up Signal (WUS) configuration including a threshold. The method receives, from a first Network Energy Saving (NES) cell, a first Synchronization Signal Block (SSB). The method measures a first Reference Signal Received Power (RSRP) corresponding to the first SSB. The method transmits, to the first NES cell, an Uplink (UL) WUS based on the WUS configuration to request an On-Demand (OD) SIB1 in response to determining that the first RSRP is greater than the threshold. The method monitors a Physical Downlink Control Channel (PDCCH) monitoring occasion associated with the first SSB for control signaling related to the OD-SIB1.　

Description

METHOD AND APPARATUS FOR SYSTEM INFORMATION BLOCK TYPE 1 (SIB1) REQUEST OPERATION

[0001] The present disclosure is related to wireless communication and, more specifically, to a User Equipment (UE), Base Station (BS), and method for a System Information Block Type 1 (SIB1) request operation 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 network energy saving (NES).

[0003] The present disclosure is related to a UE, a BS, and a method for performing a SIB1 request operation in the wireless communication networks.

[0004] In a first aspect of the present disclosure, a UE for performing a SIB1 request operation is provided. The UE includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The computer-executable instructions, when executed by the at least one processor, cause the UE to: camp on a first cell; receive, from the first cell, a Wake-Up Signal (WUS) configuration including a threshold; receive, from a first Network Energy Saving (NES) cell, a first Synchronization Signal Block (SSB); measure a first Reference Signal Received Power (RSRP) corresponding to the first SSB; transmit, to the first NES cell, an Uplink (UL) WUS based on the WUS configuration to request an On-Demand (OD) SIB1 in response to determining that the first RSRP is greater than the threshold; and monitor a Physical Downlink Control Channel (PDCCH) monitoring occasion associated with the first SSB for control signaling related to the OD-SIB1.

[0005] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: receive, from the first NES cell, a second SSB; and measure a second RSRP corresponding to the second SSB. The second RSRP is less than the threshold, and the PDCCH monitoring occasion is not associated with the second SSB.

[0006] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to determine the PDCCH monitoring occasion associated with the first SSB based on information in the WUS configuration.

[0007] In some implementations of the first aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to determine the PDCCH monitoring occasion associated with the first SSB based on information in the first SSB.

[0008] In some implementations of the first aspect, the WUS configuration further includes a Physical Cell Identity (PCI) indicating the first NES cell and a Random Access Channel (RACH) occasion for transmission of the UL WUS.

[0009] In some implementations of the first aspect, the WUS configuration includes a first sub-configuration and a second sub-configuration. The first sub-configuration is associated with the first NES cell and includes the threshold. The second sub-configuration is associated with a second NES cell.

[0010] In some implementations of the first aspect, the WUS configuration further includes multiple PCIs indicating multiple NES cells associated with the first cell. The threshold is common to the NES cells associated with the first cell.

[0011] In a second aspect of the present application, a BS configured to support a SIB1 request operation is provided. The BS includes at least one processor and at least one non-transitory computer-readable medium that is coupled to the at least one processor and that stores one or more computer-executable instructions. The computer-executable instructions, when executed by the at least one processor, cause the BS to: transmit, to a UE via a first NES cell, a first SSB; and receive, from the UE via the first NES cell, a UL WUS based on a WUS configuration including a threshold. The UE camps on a first cell and receives the WUS configuration from the first cell. A first RSRP of the first SSB measured by the UE is greater than the threshold. The UL WUS requests an OD-SIB1. The UE monitors a PDCCH monitoring occasion associated with the first SSB for control signaling related to the OD-SIB1.

[0012] In some implementations of the second aspect, the one or more computer-executable instructions, when executed by the at least one processor, further cause the BS to transmit, to the UE via the first NES cell, a second SSB. A second RSRP of the second SSB measured by the UE is less than the threshold, and the PDCCH monitoring occasion is not associated with the second SSB.

[0013] In some implementations of the second aspect, the UE determines the PDCCH monitoring occasion associated with the first SSB based on information in the WUS configuration.

[0014] In some implementations of the second aspect, the UE determines the PDCCH monitoring occasion associated with the first SSB based on information in the first SSB.

[0015] In some implementations of the second aspect, the WUS configuration further includes a PCI indicating the first NES cell and a RACH occasion for transmission of the UL WUS.

[0016] In some implementations of the second aspect, the WUS configuration includes a first sub-configuration and a second sub-configuration. The first sub-configuration is associated with the first NES cell and includes the threshold. The second sub-configuration is associated with a second NES cell.

[0017] In some implementations of the second aspect, the WUS configuration further includes multiple PCIs indicating multiple NES cells associated with the first cell. The threshold is common to the NES cells associated with the first cell.

[0018] In a third aspect of the present application, a method performed by a UE for performing a SIB1 request operation is provided. The method includes camping on a first cell; receiving, from the first cell, a WUS configuration including a threshold; receiving, from a first NES cell, a first SSB; measuring a first RSRP corresponding to the first SSB; transmitting, to the first NES cell, a UL WUS based on the WUS configuration to request an OD-SIB1 in response to determining that the first RSRP is greater than the threshold; and monitoring a PDCCH monitoring occasion associated with the first SSB for control signaling related to the OD-SIB1.

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

[0020] FIG. 1 is a flowchart illustrating a method / process performed by a UE for performing a SIB1 request operation, according to an example implementation of the present disclosure.

[0021] FIG. 2 is a flowchart illustrating a method / process performed by a BS for supporting a SIB1 request operation, according to an example implementation of the present disclosure.

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

[0023] Some of the abbreviations used in the present disclosure include: 3GPP　　　　　　　　　　　　3rd Generation Partnership Project 5G　　　　　　　　　　　　5th generation 5GC　　　　　　　　　　　　5G Core Network ACK　　　　　　　　　　　　Acknowledgment BWP　　　　　　　　　　　　Bandwidth Part BS　　　　　　　　　　　　Base Station CA　　　　　　　　　　　　Carrier Aggregation CBRA　　　　　　　　　　　　Contention-Based RA CC　　　　　　　　　　　　Component Carrier CE　　　　　　　　　　　　Control Element CFRA　　　　　　　　　　　　Contention-Free RA CN　　　　　　　　　　　　Core Network CORESET　　　　　　　　　　　　Control resource set CRC　　　　　　　　　　　　Cyclic Redundancy Check CSS　　　　　　　　　　　　Common search space DC　　　　　　　　　　　　Dual Connectivity DCI　　　　　　　　　　　　Downlink Control Information DL　　　　　　　　　　　　Downlink EPC　　　　　　　　　　　　Evolved Packet Core E-UTRA　　　　　　　　　　　　Evolved Universal Terrestrial Radio Access FDM　　　　　　　　　　　　Frequency-Division Multiplexing FR　　　　　　　　　　　　Frequency Range GSCN　　　　　　　　　　　　Global Synchronization Channel Number HARQ　　　　　　　　　　　　Hybrid Automatic Repeat reQuest ID　　　　　　　　　　　　Identifier IE　　　　　　　　　　　　Information Element L1 / L2 / L3　　　　　　　　　　　　Layer 1 / Layer 2 / Layer 3 LTE　　　　　　　　　　　　Long Term Evolution MAC　　　　　　　　　　　　Medium Access Control MCG　　　　　　　　　　　　Master Cell Group MIB　　　　　　　　　　　　Master Information Block MN　　　　　　　　　　　　Master Node MR-DC　　　　　　　　　　　　Multi-RAT Dual Connectivity Msg　　　　　　　　　　　　Message NACK　　　　　　　　　　　　Negative Acknowledgment NAS　　　　　　　　　　　　Non-Access Stratum NDI　　　　　　　　　　　　New Data Indicator NES　　　　　　　　　　　　Network Energy Saving NR　　　　　　　　　　　　New RAT / Radio NW　　　　　　　　　　　　Network OD-SIB1　　　　　　　　　　　　On-Demand SIB1 PBCH　　　　　　　　　　　　Physical Broadcast Channel PCell　　　　　　　　　　　　Primary Cell PCI　　　　　　　　　　　　Physical Cell Identity PDCP　　　　　　　　　　　　Packet Data Convergence Protocol PDCCH　　　　　　　　　　　　Physical Downlink Control Channel PDSCH　　　　　　　　　　　　Physical Downlink Shared Channel PHY　　　　　　　　　　　　Physical PLMN　　　　　　　　　　　　Public Land Mobile Network PRACH　　　　　　　　　　　　Physical Random Access Channel PRB　　　　　　　　　　　　Physical Resource Block PSCell　　　　　　　　　　　　Primary SCG Cell PUCCH　　　　　　　　　　　　Physical Uplink Control Channel PUSCH　　　　　　　　　　　　Physical Uplink Shared Channel RA　　　　　　　　　　　　Random Access RACH　　　　　　　　　　　　Random Access Channel RAN　　　　　　　　　　　　Radio Access Network RAR　　　　　　　　　　　　Random Access Response RAT　　　　　　　　　　　　Radio Access Technology RF　　　　　　　　　　　　Radio Frequency RLC　　　　　　　　　　　　Radio Link Control RNTI　　　　　　　　　　　　Radio Network Temporary Identifier RO　　　　　　　　　　　　RACH Occasion RRC　　　　　　　　　　　　Radio Resource Control RS　　　　　　　　　　　　Reference Signal RSRP　　　　　　　　　　　　Reference Signal Received Power SCell　　　　　　　　　　　　Secondary Cell SCG　　　　　　　　　　　　Secondary Cell Group SDAP　　　　　　　　　　　　Service Data Adaptation Protocol SI　　　　　　　　　　　　System Information SIB　　　　　　　　　　　　System Information Block SIB1　　　　　　　　　　　　System Information Block Type 1 SN　　　　　　　　　　　　Secondary Node SpCell　　　　　　　　　　　　Special Cell SR　　　　　　　　　　　　Scheduling Request SS　　　　　　　　　　　　Synchronization Signal SSB　　　　　　　　　　　　Synchronization Signal Block TA　　　　　　　　　　　　Tracking Area TRP 　　　　　　　　　　　　Transmission Reception Point TS　　　　　　　　　　　　Technical Specification UAC　　　　　　　　　　　　Unified Access Control UE　　　　　　　　　　　　User Equipment UL　　　　　　　　　　　　Uplink URLLC　　　　　　　　　　　　Ultra Reliable Low Latency Communication WUS　　　　　　　　　　　　Wake-Up Signal XR　　　　　　　　　　　　eXtended Reality

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

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

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

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

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

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

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

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

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

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

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

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

[0036] The BS may include, but is not limited to, a node B (NB) in the UMTS, an evolved node B (eNB) in LTE or LTE-A, a radio network controller (RNC) in UMTS, a BS controller (BSC) in the GSM / GERAN, an ng-eNB in an Evolved Universal Terrestrial Radio Access (E-UTRA) BS in connection with 5GC, a next generation Node B (gNB) in the 5G-RAN, or any other apparatus capable of controlling radio communication and managing radio resources within a cell. The BS may serve one or more UEs via a radio interface. 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.

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

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

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

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

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

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

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

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

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

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

[0047] According to any two or more than two of the following sentences, paragraphs, (sub)-bullets, points, actions, behaviors, terms, alternatives, aspects, examples, embodiments, or claims described in the present disclosure, “X / Y” includes the meaning of “X or Y”, “X and Y”, and “X and / or Y”.

[0048] Implementations in the present disclosure may be used, for example, in a communication equipment (e.g., a mobile telephone apparatus, ad base station apparatus, a wireless LAN apparatus, and / or a sensor device, etc.), and integrated circuit (e.g., a communication chip) and / or a program, etc.

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

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

[0051] User Equipment (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 (NW): The NW may be a network node, a TRP, a cell (e.g., SpCell, PCell, PSCell, and / or SCell), an eNB, a gNB, and / or a base station.

[0053] Camped on a cell: The UE has completed the cell selection / reselection process and has chosen a cell. The UE monitors system information and, in most cases, paging information from the cell.

[0054] Camped on any cell: The UE is in the idle mode and has completed the cell selection / reselection process and has chosen a cell irrespective of the PLMN identity.

[0055] Equivalent PLMN list: List of PLMNs considered as equivalent by the UE for cell selection, cell reselection, and handover according to the information provided by the NAS.

[0056] Registration Area: A registration area (or a NAS registration area) is an area in which the UE may roam without a need to perform location registration, which is a NAS procedure.

[0057] Registered PLMN: The registered PLMN is the PLMN on which certain Location Registration outcomes have occurred.

[0058] Reserved Cell: A reserved cell is a cell on which camping is not allowed, except for particular UEs, if so indicated in the system information.

[0059] Selected PLMN: The selected PLMN is the PLMN that has been selected by the NAS, either manually or automatically.

[0060] Serving cell: The serving cell is the cell on which the UE is camped.

[0061] Strongest cell: The strongest cell is the cell on a particular frequency that is considered strongest according to the layer-1 cell search procedure.

[0062] Suitable Cell: A suitable cell is a cell on which a UE may camp. A suitable cell may satisfy the following conditions: The cell is part of either the selected PLMN or the registered PLMN or PLMN of the Equivalent PLMN list; The cell selection criteria are fulfilled; The cell is not barred according to the last information provided by NAS; The cell is part of at least one Tracking Area (TA) that is not part of the list of “Forbidden Tracking Areas”, which belongs to a PLMN that fulfils the first condition described above.

[0063] Barred cell: A barred cell is a cell that a UE is not allowed to camp on.

[0064] Cell A: The term “Cell A” may represent a cell that is periodically transmitting at least its own SIB1.

[0065] NES Cell: The term “NES cell” may represent a cell that transmits the SIB1 in response to the UL WUS from a UE.

[0066] NES-Capable UE: A NES-capable UE is a UE that supports the NES function.

[0067] Network energy saving (NES) is of great importance for environmental sustainability, to reduce environmental impact (e.g., greenhouse gas emissions), and for operational cost savings. As 5G is becoming pervasive across industries and geographical areas, handling more advanced services and applications requiring very high data rates (e.g., XR), networks are becoming denser and are using more antennas, larger bandwidths and more frequency bands. Novel solutions may be needed to improve network energy savings and mitigate the environmental impact of 5G

[0068] A SIB1 may provide a UE with essential information to perform basic operation, where the SIB1 associated with SSB may be broadcast by a gNB / NW. In legacy, a cell that is a candidate for PCell must always transmit the SIB1, which causes additional power consumption. Thus, for the purpose of energy saving, the cell may transmit the SIB1 only in response to a request sent by the UE. This technique may be referred to as “on-demand SIB1” or OD-SIB1, and may be typically used when the UE is in the RRC_IDLE or RRC_INACTIVE state.

[0069] Scenario Description

[0070] Single-Cell Scenario: An NES-capable UE may only detect SSB(s) from an NES cell, obtain a WUS configuration from the NES cell, and send the UL WUS based on the WUS configuration to the NES cell to acquire the corresponding SIB1.

[0071] In some implementations, the NES-capable UE may determine whether the detected cell is a legacy cell or an NES Cell by using either an explicit method or an implicit method.

[0072] Multi-Cell Scenario: An NES-capable UE may detect SSB(s) from NES cell(s) and the Cell A, obtain assistance information (e.g., a WUS configuration) for performing an on-demand SIB1 operation from the Cell A, and send the UL WUS based on the assistance information to a detected NES cell or the Cell A to acquire the corresponding SIB1.

[0073] In some implementations, the NES-capable UE may camp on the Cell A if the Cell A is considered as a suitable cell by the NES-capable UE during a cell (re)selection procedure.

[0074] In some implementations, the NES-capable UE may determine whether the detected cell is a legacy cell, the Cell A, or an NES Cell by using either an explicit method (e.g., a spare bit in the MIB) or an implicit method.

[0075] In some implementations, the NES-Capable UE may not camp on an NES Cell before receiving the corresponding SIB1 based on the on-demand SIB1 operation.

[0076] In some implementations, the NES-Capable camped on the Cell A may not establish RRC connection due to UAC indicated by the Cell A. In other words, the NES-Capable may be barred by the Cell A via UAC.

[0077] In some implementations, the Cell A may be associated with one or more NES cells, where the association may be provided by an explicit method (e.g., a PCI list in the WUS configuration, a PCI list in the requested SIBx) or an implicit method (e.g., redirecting information).

[0078] In some implementations, the NES-capable UE camped on the Cell A may expect to establish RRC connection with an NES cell, where the NES cell may be associated with the Cell A providing the assistance information.

[0079] It should be noted that a non-NES-capable UE (e.g., a legacy UE) may operate according to the 3GPP specifications, which may refer to versions prior to Release 19.

[0080] Acquisition of SIB1

[0081] A UE in the RRC_INACTIVE / RRC_IDLE state, which may also be referred to as an RRC_INACTIVE / RRC_IDLE UE, may obtain the SIB1 of a cell detected by the UE according to the following procedure. The UE may try to decode the MIB from the detected SSB of the cell, if any. The UE may obtain the resource information (e.g., the PDCCH-ConfigSIB1 IE) for scheduling resources (e.g., Type0-PDCCH CSS sets) to receive the SIB1. For each SSB with index i, the UE may specify the CORESET and the monitoring occasion for scheduling resources according to the resource information.

[0082] RACH Procedure and Acquisition of Other System Information (SI)

[0083] A RACH procedure performed by the UE may be applicable for different purposes (e.g., UL synchronization, request of other SI). When the RACH procedure is initiated by the UE, the UE may transmit a preamble (e.g., Msg1) to a gNB / NW on a RACH occasion (RO) based on the fundamental system information (e.g., SIB1). Then, the UE may wait for a response (e.g., Msg2) within a configured window, where the configured window may be indicated in the fundamental system information. When the UE successfully receives the response from the gNB / NW, the UE may perform UL transmission (e.g., Msg3) based on the content of the response. If the initiated procedure is a contention-based RA, the UE may wait for a contention resolution (e.g., Msg4) from the gNB / NW until a configured timer expires.

[0084] Other SI may refer to the system information other than the MIB and SIB1. The UE may acquire other SI by sending a request to the gNB / NW in one of the following two methods. First, the UE may initiate a RACH procedure and transmit a preamble, which corresponds to the required set of SIBs, on a RO to the gNB / NW. Second, the UE may send the RRCSystemInfoRequest message to the gNB / NW. In the first method, the UE may request a specific set of SIBs by transmitting the corresponding preamble on the RO to the gNB / NW.

[0085] The number of preambles used to perform the RACH procedure for a serving cell may be 64, where the preambles may be generated by the UE based on a configured root index (e.g., the field prach-RootSequenceIndex) in the fundamental system information. These preambles may be divided into several groups for different usages (e.g., CBRA, CFRA, Other SI acquisition). The UE may generate PRACH resources for different purposes according to the corresponding PRACH configuration (e.g., the RACH-ConfigGeneric IE). On the other hand, the UE may specify the association between RO(s) and SSB(s) for different purposes according to a field (e.g., ssb-perRACH-Occasion, ssb-perRACH-OccasionAndCB-PreamblesPerSSB) belonging to the corresponding RACH configuration (e.g., the RACH-ConfigCommon IE, the RACH-ConfigDedicated IE, the SI-SchedulingInfo IE). The UE may also specify the association between the preamble index(es) and the SSB(s) according to the corresponding RACH configuration.

[0086] When a RACH procedure is initiated, the UE may select a SSB from the SSB burst based on the corresponding measurement results. If a set of SSBs have SS-RSRP above a configured threshold (e.g., the field rsrp-ThresholdSSB), the UE may select a SSB from the corresponding set. If none of the SSBs has SS-RSRP above the configured threshold, the UE may select any SSB from the SSB burst.

[0087] Cell Selection and Cell Reselection

[0088] When a UE attempts to camp on a cell, the cell may need to be selected based on a cell selection procedure / cell reselection procedure. If the UE does not camp on any cell yet, a cell selection procedure may be applied by the UE to find a suitable cell. If the UE has camped on a cell, a cell reselection procedure may be applied by the UE to find a more suitable cell.

[0089] The cell selection procedure may be performed either without prior knowledge (e.g., an initial cell search) or by leveraging stored information. For the initial cell search, the UE may scan all RF channels in the NR bands according to its capabilities to find a suitable cell. On each frequency, the UE may search only for the strongest cell, and once a suitable cell is found, the UE may select that cell. For cell selection based on the stored information, the UE may scan cells by leveraging the stored information. Once the UE has found a suitable cell, the UE may select the cell. It should be noted that the initial cell selection procedure may be started if no suitable cell is found.

[0090] Each cell, searched by the UE during cell selection / cell reselection, may include at least one PLMN equal to the selected PLMN / the registered PLMN / a PLMN of the equivalent PLMN list, where the selected PLMN / the registered PLMN / a PLMN of the equivalent PLMN list may be informed from the NAS to the UE. Moreover, the selected PLMN / the registered PLMN / the equivalent PLMN list may be provided according to a PLMN selection procedure. For the PLMN selection procedure, the NAS may obtain a list of available PLMNs based on a cell search procedure performed by the UE, where the UE may report to the NAS all high-quality PLMNs (e.g., measured RSRP higher than the configured RSRP threshold) or all acceptable PLMNs with their RSRP values. It should be noted that the UE may perform a cell search procedure on a frequency / a RAT based on UE capability.

[0091] Possible Issues

[0092] In multi-cell scenarios, an NES-capable UE may obtain the WUS configuration from the Cell A and may send the UL WUS to an NES cell to acquire on-demand SIB1 from the NES cell. Some issues may need to be addressed from the perspective of the NES-capable UE. The issues may include, for example, how to identify whether a detected cell is an NES cell or Cell A, how to obtain the WUS configuration from the cell A, how to perform the UL WUS transmission, and how to acquire the on-demand SIB1. Implementations addressing the above issues are provided in the present disclosure.

[0093] Cell Type Identification

[0094] An NES-capable UE may identify the cell type of a detected cell according to information from the detected cell and / or another cell. For example, the NES-capable UE may identify the cell type based only on information from the currently detected cell. For example, the NES-capable UE may identify the cell type based only on information from another cell (e.g., Cell A). For example, the NES-capable UE may identify the cell type based on information from the currently detected cell and another cell. On the other hand, if a legacy UE detected Cell A or an NES cell, it may be unable to distinguish whether the detected cell is Cell A, an NES cell, or a cell that does not support the NES feature.

[0095] Acquisition of WUS Configuration

[0096] An NES-capable UE may obtain the WUS configuration from the Cell A, where the WUS configuration may include at least the content used to transmit the UL WUS to an NES cell. For example, the content may include time-frequency domain information and / or power domain information used to transmit the UL WUS to the NES cell.

[0097] In some implementations, the WUS configuration may be included in the SIB1 of the Cell A. The NES-capable UE may transmit the UL WUS to a dedicated NES cell associated with the Cell A, any one of the NES cells associated with the Cell A, or all the NES cells associated with the Cell A.

[0098] In some implementations, the WUS configuration may be included in SIBx, where the NES-capable UE may send a request to the Cell A for acquiring SIBx based on the on-demand SI acquisition. More specifically, information needed for acquisition of SIBx may be included in the SIB1 of the Cell A. For example, the scheduling information list within the SI-SchedulingInfo IE may include a SchedulingInfo IE associated with a SIB-Mapping IE. The SIB-Mapping IE may include a SIB-TypeInfo IE including the field “type”, which may be set to SIBx (e.g., ENUMERATED {..., sibTypex, ..., spare3, spare2, spare1, ...}). Moreover, the NES-capable UE may transmit the UL WUS to a dedicated NES cell associated with the Cell A, any one of the NES cells associated with the Cell A, or all the NES cells associated with the Cell A. In other words, the WUS configuration may be applied to a specific NES cell associated with the Cell A, or may be common to all NES cells associated with the Cell A.

[0099] In some implementations, the NES-capable UE may send a request to the Cell A to acquire the WUS configuration applied to a dedicated NES cell based on the on-demand SI acquisition. For example, the NES-capable UE may send a request to the Cell A to acquire the WUS configuration applied for one of the NES cells associated with the Cell A.

[0100] Preamble Sequence Design

[0101] One of the UL WUS types may be a preamble, such as the Msg1 in a RACH procedure. Thus, the NES-capable UE may generate one or more preamble sequences based on a configuration from the Cell A.

[0102] In some implementations, the UL WUS may be a preamble generated based on the WUS configuration, where the WUS configuration may include one or more PRACH root sequence indices used to generate one or more sets of preambles based on clause 6.3.3.1 in the 3GPP TS 38.211 V15.10.0. It should be noted that the preamble may be short format (e.g., LRA=139) or long format (e.g., LRA=879). In some implementations, the number of preambles belonging to a set may be less than or equal to 64. In some implementations, the format of the preambles used for the UL WUS may be short format only.

[0103] In some implementations, the NES-capable UE camping on the Cell A may be configured with a root index to generate a set of preambles. The set may be divided into one or more subsets, where each subset may be used for UL WUS transmission corresponding to a specific NES cell. For example, each WUS configuration applicable to the specific NES cell may include an IE RA-NES, where the IE RA-NES may include information related to the corresponding subset (e.g., preamble index(es)) and / or the power offset configuration. For example, each IE RA-NES may include an IE RACH-ConfigGeneric-NES, where the IE RACH-ConfigGeneric-NES may provide information related to the resources used to perform the UL WUS transmission. The resources for the RA procedure on the Cell A and for the UL WUS transmission on the NES cell(s) may be non-overlapping. Thus, a non-NES-capable UE may perform the RA procedure on the Cell A based on the entire preamble set without making collision. Furthermore, each preamble sequence used to perform the UL WUS transmission on a specific NES cell may have low correlation with the others if all subsets are mutually disjoint. The number of preambles in the set may be 64, but not limited thereto.

[0104] In some implementations, the NES-capable UE camping on the Cell A may be configured with one or more root indices to generate one or more sets of preambles, where each set used for the UL WUS transmission may correspond to a specific NES cell. The number of preambles in the set may be 64, but not limited thereto. For example, the NES-capable UE may be configured by the Cell A with a list included in the WUS configuration, where the list may include one or more IEs RACH-ConfigNES. Moreover, each IE RACH-ConfigNES may include the field prach-RootSequenceIndex applicable to a specific NES cell. In other words, the NES-capable UE may generate a set of preambles for an NES cell based on the corresponding root index.

[0105] Association between Cell A and NES Cell(s)

[0106] In some implementations, the Cell A may be associated with one or more NES cells, where the NES-capable UE may obtain the association from the Cell A based on an explicit method or an implicit method. For example, the Cell A may provide a PCI list to the NES-capable UE via RRC signaling, where the PCI list may correspond to a set of NES cells. Thus, the NES-capable UE may identify an NES cell according to the provided PCI list. In some implementations, the PCI list may be included in the WUS configuration, the SIB1 of the Cell A, and / or SIBx of the Cell A.

[0107] RACH Occasion(s) of NES Cell(s)

[0108] In some implementations, an NES-capable UE may be configured by the Cell A with one or more resources (e.g., time-frequency domain, power domain) corresponding to one or more specific NES cells. The NES-capable UE may perform the UL WUS transmission on one or more resources to the specific NES cell if the specific NES cell is indicated or selected. On the other hand, the specific NES cell may monitor these configured resources for reception of the UL WUS.

[0109] In some implementations, the NES-capable UE may be configured by the Cell A with a mapping rule (e.g., the field ssb-perRACH-OccasionAndCB-PreamblesPerSSB-NES, the field ssb-perRACH-Occasion-NES) applicable to one of the NES cells. The mapping rule may indicate the association between the configured resource(s) and SSB(s) in an SSB burst. Each NES cell may be associated with the Cell A, but not limited thereto. For example, each mapping rule may be associated with a PCI in the PCI list configured by the Cell A. In other words, there may be a one-to-one mapping between each mapping rule and an NES cell. The field ssb-perRACH-OccasionAndCB-PreamblesPerSSB-NES may indicate the number of resources associated with one SSB in an SSB burst and the number of preambles associated with one SSB in the SSB burst. The field ssb-perRACH-Occasion-NES may indicate the number of resources associated with one SSB in an SSB burst.

[0110] In some implementation, the NES-capable UE may be configured by the Cell A with a common mapping rule (e.g., the field ssb-perRACH-OccasionAndCB-PreamblesPerSSB-NES, the field ssb-perRACH-Occasion-NES) applicable to all NES cells. The mapping rule may indicate the association between the configured resource(s) and SSB(s) in an SSB burst. All NES cells may be associated with the Cell A, but not limited thereto. For example, the mapping rule may be associated with all PCIs in the PCI list configured by the Cell A. In other words, there may be a one-to-many mapping between the mapping rule and the NES cells. For example, the NES-capable UE may be configured by the Cell A with a WUS configuration, where the WUS configuration may include a list including one or more IEs RACH-ConfigNES and a common mapping rule for all associated NES cells. The field ssb-perRACH-OccasionAndCB-PreamblesPerSSB-NES may indicate the number of resources associated with one SSB in an SSB burst and the number of preambles associated with one SSB in the SSB burst. The field ssb-perRACH-Occasion-NES may indicate the number of resources associated with one SSB in an SSB burst.

[0111] In some implementations, the NES-capable UE may be configured by the Cell A with a set of parameters (e.g., the IE RACH-ConfigGeneric-NES), which may specify time-frequency domain information and / or power domain information for the configured resources applicable to one of the NES cells. For example, the IE RACH-ConfigGeneric-NES may be associated with a PCI in the PCI list configured by the Cell A. In other words, there may be a one-to-one mapping between each RACH-ConfigGeneric-NES and an NES cell. Each NES cell may be associated with the Cell A, but not limited thereto.

[0112] In some implementations, the NES-capable UE may be configured by the Cell A with a set of parameters (e.g., the IE RACH-ConfigGeneric-NES), which may specify time-frequency domain information and / or power domain information for the configured resources applicable to all NES cells. For example, the IE RACH-ConfigGeneric-NES may be associated with all PCIs in the PCI list configured by the Cell A. In other words, there may be a one-to-many mapping between the IE RACH-ConfigGeneric-NES and the NES cells. All NES cells may be associated with the Cell A, but not limited thereto.

[0113] In some implementations, the IE RACH-ConfigGeneric-NES may include at least one of the following parameters:

[0114] - prach-ConfigurationIndex: PRACH configuration index.

[0115] - msg1-FDM: The number of PRACH transmission occasions FDMed in one time instance.

[0116] - msg1-FrequencyStart: Offset of the lowest PRACH transmission occasion in frequency domain with respective to PRB 0.

[0117] - powerRampingStep: Power ramping steps for PRACH.

[0118] - preambleReceivedTargetPower: The target power level at the network receiver side.

[0119] - preambleTransMax: The maximum number of RA preamble transmissions performed before declaring a failure.

[0120] - ra-ResponseWindow: Msg2 (e.g., RAR) window length in number of slots.

[0121] - zeroCorrelationZoneConfig: N-CS configuration, as specified in Table 6.3.3.1-5 in the 3GPP TS 38.211.

[0122] In some implementations, the information related to the configured resources used to perform the UL WUS transmission may be included in the corresponding WUS configuration. For example, the WUS configuration may include information corresponding to each NES cell. For example, the WUS configuration may include information corresponding to all NES cells.

[0123] UL WUS Transmission

[0124] An NES-capable UE camped on the Cell A may perform UL WUS transmission to one or more NES cells based on the WUS configuration provided by the Cell A and / or based on the stored information. The stored information may be related to the measurement results (e.g., L1-RSRP), the corresponding PCI, and / or the corresponding frequency domain information of an NES cell detected before camping on the Cell A. The stored information may include, but is not limited to, the information described above. In some implementations, the NES-capable UE camped on the Cell A may, for some reasons (e.g., access restriction), attempt to find another cell to camp.

[0125] NES Cell Indication / Selection

[0126] In some implementations, if the NES-capable UE camped on the Cell A does not have the stored information, the NES-capable UE may perform UL WUS transmission to an NES cell based on only the WUS configuration provided by the Cell A.

[0127] In some implementations, the NES-capable UE camped on the Cell A may search for a suitable cell or an NES cell on an intra-frequency, inter-frequency, and / or inter-RAT basis, based on the priority provided by dedicated signaling (e.g., the RRCRelease message) or system information. For example, once a suitable cell has been successfully detected, the NES-capable UE may camp on the suitable cell. For example, once an NES cell has been successfully detected, the NES-capable UE may perform the UL WUS transmission to the NES cell based on the WUS configuration.

[0128] In some implementations, the NES-capable UE camped on the Cell A may search for an NES cell based on the WUS configuration. For example, the NES-capable UE may search for an NES cell based on the corresponding GSCN included in the WUS configuration. For example, the NES-capable UE may obtain the priority of NES cells included in the WUS configuration. The NES-capable UE may search for an NES cell based on the obtained priority. Once an NES cell is successfully detected, the NES-capable UE may perform UL WUS transmission to the NES cell based on the WUS configuration.

[0129] In some implementations, if the NES-capable UE camped on the Cell A has the stored information, the NES-capable UE may perform UL WUS transmission to an NES cell based on the WUS configuration and the stored information.

[0130] In some implementations, the NES-capable UE camped on the Cell A may search for an NES cell on an intra-frequency, inter-frequency, and / or inter-RAT basis, based on the stored information and / or the WUS configuration. For example, the NES-capable UE may search for an NES cell based on the stored information and / or the WUS configuration. Once an NES cell has been successfully detected, the NES-capable UE may perform UL WUS transmission to the NES cell based on the WUS configuration.

[0131] In some implementations, an NES cell may be considered successfully detected if at least one of the following conditions is satisfied.

[0132] In some implementations, the NES-capable UE may detect an NES cell that fulfills a criterion (e.g., L1-RSRP / L3-RSRP threshold, cell selection criterion S applicable for NES cell and / or criterion R applicable for NES cell). For example, the NES-capable UE may be configured by the Cell A with a set of parameters to calculate the criteria, where the set of parameters may be common to all NES cells associated with the Cell A. For example, the NES-capable UE may be configured by the Cell A with one or more sets of parameters to calculate the criteria, where each set of the parameters may be applicable to a specific NES cell. In some implementations, a set of parameters may be included in the WUS configuration. In some implementations, a set of parameters may be associated with a specific NES cell by the corresponding PCI. For example, the WUS configuration may include one or more sub-configurations, where each sub-configuration may be applicable to a specific NES cell to perform UL WUS transmission. Each sub-configuration may include at least the corresponding PCI and the set of parameters used to calculate the criteria. The criterion S applicable for NES cell and / or criterion R applicable for NES cell may be calculated in a manner similar to that defined in the 3GPP TS 38.304.

[0133] In some implementations, the NES-capable UE may detect SSB(s) in an SSB burst of the NES cell. One of the corresponding measurement results (e.g., L1-RSRP) may be greater than a configured threshold (e.g., the field rsrp-ThresholdSSB-NES). For example, the NES-capable UE may be configured by the Cell A with a threshold. The NES-capable UE may then measure SSB(s) of the NES cell and compare the measurement result(s) with the configured threshold. For example, the NES-capable UE may be configured by the Cell A with a threshold, where the threshold may be common to all NES cells associated with the Cell A. In some implementations, a configured threshold may be associated with a specific NES cell by the corresponding PCI. For example, the WUS configuration may include one or more sub-configurations, where each sub-configuration may be applicable to a specific NES cell to perform UL WUS transmission. Each sub-configuration may include at least the corresponding PCI and the configured threshold. For example, the WUS configuration may include a first sub-configuration and a second sub-configuration associated with a first NES cell and a second NES cell, respectively. The first sub-configuration may include a first threshold applicable to the first NES cell. The second sub-configuration may include a second threshold applicable to the second NES cell. In some implementations, the NES-capable UE may be configured by the Cell A with a threshold applicable to each frequency carrier.

[0134] In some implementations, the NES-capable UE may select an NES cell from a ranking list, where the NES-capable UE may generate the ranking list based on the measurement results of the detected NES cell(s). For example, the NES-capable UE may have one or more NES cells that have been successfully detected. The NES-capable UE may rank these detected NES cells based on the corresponding measurement results. It should be noted that the measurement results may include averaged RSRPs or L1-RSRPs, but not limited thereto. For example, the NES-capable UE may rank the detected NES cells based on the value of L1-RSRPs corresponding to the measured SSBs. For example, the NES-capable UE may rank the detected NES cells based on the value of corresponding averaged RSRPs. For example, the NES-capable UE may rank the detected NES cells based on the number of measured SSBs with an L1-RSRP value greater than the configured threshold. In some implementations, if two or more detected NES cells have the same number, the UE may randomly order these NES cells. For example, the NES-capable UE may select the highest ranked NES cell.

[0135] In some implementations, the NES-capable UE may be configured by the Cell A with time-domain positions of SSBs in an SSB burst of an NES cell (e.g., the IE ssb-PositionsInBurst-NES), where the time-domain positions of SSBs in an SSB burst may represent the corresponding SSB(s) that the NES cell may actually transmit. For example, the NES-capable UE may be configured by the Cell A with a time-domain positions of SSBs in an SSB burst, where the configured time-domain positions may be common to all NES cells associated with the Cell A. In some implementations, a configured time-domain position may be associated with a specific NES cell by the corresponding PCI. For example, the WUS configuration may include one or more sub-configurations, where each sub-configuration may be applicable to a specific NES cell to perform the UL WUS transmission. Each sub-configuration may include at least the corresponding PCI and the configured time-domain positions. For example, the NES-capable UE may be configured by the Cell A with a bitmap corresponding to the configured time-domain positions, where a value of one in the bitmap may indicate that the corresponding SSB may be transmitted by the associated NES cell.

[0136] Resource(s) for UL WUS Transmission

[0137] In some implementations, the NES-capable UE may perform UL WUS transmission on the configured resource(s) corresponding to the indicated / selected NES cell based on the WUS configuration. For example, the NES-capable UE may perform UL WUS transmission on the configured resource associated with an SSB of the detected NES cell, where the value of L1-RSRP corresponding to the SSB may be greater than the configured threshold. For example, the NES-capable UE may perform UL WUS transmission on the configured resource associated with an SSB of the detected NES cell, where the value of L1-RSRP corresponding to the SSB may be the highest in the SSB burst.

[0138] In some implementations, when the NES-capable UE is configured by the Cell A with the IE(s) ssb-PositionsInBurst-NES, the NES-capable UE may perform UL WUS transmission on a configured resource associated with one or more transmitted SSBs of a detected NES cell, where the transmitted SSBs may be indicated by elements set to one within the IE(s) ssb-PositionsInBurst-NES. For example, the NES-capable UE may not expect to perform UL WUS transmission on a configured resource corresponding to an SSB not transmitted by the NES cell.

[0139] On-demand SIB1 Acquisition

[0140] An NES-capable UE may obtain a WUS configuration from the Cell A. The NES-capable UE may transmit a UL WUS to an NES cell based on the WUS configuration. The NES-capable UE may receive the on-demand SIB1 from the NES cell.

[0141] In some implementations, the NES-capable UE may obtain the WUS configuration from the Cell A when the NES-capable UE is camping on the Cell A and being barred due to UAC barring. In some implementations, the NES-capable UE may send a request to acquire the WUS configuration from the Cell A. In some implementations, the NES-capable UE may not send a request to acquire the WUS configuration from the Cell A.

[0142] UE Behaviors after Performing UL WUS Transmission

[0143] In some implementations, if an NES-capable UE performs UL WUS transmission to a specific NES cell, the NES-capable UE may monitor the SSB(s) associated with the specific NES cell for a duration, where the duration may be a fixed value / provided via RRC signaling (e.g., WUS configuration, SIB1 / SIB2 / SIBx from the Cell A). For example, the NES-capable UE may start a timer with the duration when the NES-capable UE performs UL WUS transmission to the specific NES cell. The NES-capable UE may stop the timer when the NES-capable UE receives a response to the UL WUS or a RAR from the specific NES cell or when the timer with the duration expires.

[0144] The response to the UL WUS may include ACK, NACK, and / or a change in the PBCH payload. In some implementations, if the NES-capable UE receives ACK, the NES-capable UE may expect to receive on-demand SIB1 after the PBCH payload is changed by the specific NES cell. In some implementations, the NES-capable UE may expect to receive, from the gNB, an ACK RAR including the random access preamble identifier used to transmit the UL WUS, if the gNB successfully detects the UL WUS transmitted by the NES-capable UE. In some implementations, the NES-capable UE may expect to receive, from the gNB, a NACK RAR including the random access preamble identifier used to transmit the UL WUS, if the gNB fails to detect the UL WUS transmitted by the NES-capable UE and / or rejects the provision of the on-demand SIB1. In some implementations, the RAR received by the NES-capable UE may indicate ACK / NACK in a field. For example, if the NES-capable UE receives a RAR indicating ACK, the NES-capable UE may expect to receive the on-demand SIB1 from the NES cell. For example, if the NES-capable UE receives a RAR indicating NACK, the NES-capable UE may not expect to receive the on-demand SIB1 from the NES cell.

[0145] In some implementations, if the NES-capable UE monitors the change in PBCH payload, the NES-capable UE may expect to receive the on-demand SIB1 based on the updated PBCH payload. The NES-capable UE may determine a CORESET and a search space for Type0-PDCCH based on the updated PBCH payload. The NES-capable UE may monitor the DCI format (e.g., the DCI format 1_0) with CRC scrambled by SI-RNTI based on the CORESET and the search space for Type0-PDCCH. The NES-capable UE may expect to decode the on-demand SIB1 from the PDSCH indicated by the DCI format.

[0146] In some implementations, if the NES-capable UE receives NACK, the NES-capable UE may perform UL WUS transmission again and the timer may be restarted. In some implementations, if the timer expires, the NES-capable UE may not expect to camp on the specific NES cell. In some implementations, if the timer expires, the NES-capable UE may perform UL WUS transmission again and the timer may be restarted, where the timer can be restarted N times, where N is a positive integer. In some implementations, if the timer has been restarted N times and the NES-capable UE still fails to obtain the on-demand SIB1, the NES-capable UE may not expect to camp on the specific NES cell. The value N may be provided by the WUS configuration and / or SIB1 / SIBx from the Cell A. In some implementations, the value N may be a fixed value (e.g., a predefined value). In some implementations, the NES-capable UE may be configured by the Cell A with a timer (e.g., with a duration and a value N) per frequency (e.g., band, FR1, FR2). As such, the NW may control the loading for each cell more flexibly.

[0147] In some implementations, if an NES-capable UE performs UL WUS transmission to a specific NES cell and does not expect to camp on the specific NES cell (e.g., due to failure to obtain the on-demand SIB1 or failure to receive a response from the specific NES cell), the NES-capable UE may perform UL WUS transmission to another NES cell that has a lower rank than the specific NES cell but is the highest-ranked among the remaining candidate NES cells. In some implementations, if the NES-capable UE does not expect to camp on all of the ranking NES cell(s), the NES-capable UE may try to check UAC barring by the Cell A, send a request to acquire the updated WUS configuration, and / or perform a cell reselection procedure. In some implementations, if the NES-capable UE obtains the WUS configuration from the Cell A, the NES-capable UE may first perform UL WUS transmission to acquire the on-demand SIB1 other than performing a cell reselection procedure. It should be noted that ACKs and NACKs, as used in this disclosure, stand for Acknowledgments and Negative Acknowledgments, respectively, which help ensure reliable data transmission. If a message / signal is successfully decoded by the receiver, the receiver may send an ACK. If the message / signal is lost or corrupted, the receiver may send a NACK.

[0148] In some implementations, when the NES-capable UE performs UL WUS transmission to a detected NES cell, the NES-capable UE may expect to receive the on-demand SIB1 based on any SSB in the SSB burst if the detected NES cell transmits the on-demand SIB1. It should be noted that any SSB may include, but is not limited to, SSB(s) transmitted by the detected NES cell. In some implementations, the NES-capable UE may transmit the UL WUS to a detected NES cell. The NES-capable UE may wait for receiving the on-demand SIB1 with / without the response from the detected NES cell. The NES-capable UE may decode the PBCH payload from any SSB in the SSB burst. The NES-capable UE may obtain the information related to Type0-PDCCH. The NES-capable UE may obtain the on-demand SIB1 based on the corresponding Type0-PDCCH.

[0149] In some implementations, the NES-capable UE may transmit the UL WUS to a detected NES cell. The NES-capable UE may wait to receive the on-demand SIB1 with the response from the detected NES cell. The NES-capable UE may obtain the information related to PDCCH (e.g., CORESET and / or search space) scheduling PDSCH to receive the on-demand SIB1 from the response. The NES-capable UE may obtain the on-demand SIB1 based on PDCCH associated with any SSB in the SSB burst.

[0150] In some implementations, the NES-capable UE may transmit the UL WUS to a detected NES cell. The NES-capable UE may wait to receive the on-demand SIB1 with / without the response from the detected NES cell. The NES-capable UE may obtain the information related to PDCCH (e.g., CORESET and / or search space) scheduling PDSCH to receive the on-demand SIB1 from the WUS configuration. The NES-capable UE may obtain the on-demand SIB1 based on PDCCH associated with any SSB in the SSB burst.

[0151] In some implementations, when the NES-capable UE performs UL WUS transmission to a detected NES cell, the NES-capable UE may expect to receive the on-demand SIB1 based on any transmitted SSB in the SSB burst if the detected NES cell transmits the on-demand SIB1. In some implementations, the NES-capable UE may transmit the UL WUS to a detected NES cell. The NES-capable UE may wait for receiving the on-demand SIB1 with / without the response from the detected NES cell. The NES-capable UE may decode the PBCH payload from any transmitted SSB in the SSB burst. The NES-capable UE may obtain the information related to Type0-PDCCH. The NES-capable UE may obtain the on-demand SIB1 based on the corresponding Type0-PDCCH.

[0152] In some implementations, the NES-capable UE may transmit the UL WUS to a detected NES cell. The NES-capable UE may wait to receive the on-demand SIB1 with the response from the detected NES cell. The NES-capable UE may obtain the information related to PDCCH (e.g., CORESET and / or search space) scheduling PDSCH to receive the on-demand SIB1 from the response. The NES-capable UE may obtain the on-demand SIB1 based on PDCCH associated with any transmitted SSB in the SSB burst.

[0153] In some implementations, the NES-capable UE transmit the UL WUS to a detected NES cell. The NES-capable UE may wait to receive on-demand SIB1 with / without the response from the detected NES cell. The NES-capable UE may obtain the information related to PDCCH (e.g., CORESET and / or search space) scheduling PDSCH to receive the on-demand SIB1 from the WUS configuration. The NES-capable UE may obtain the on-demand SIB1 based on PDCCH associated with any transmitted SSB in the SSB burst.

[0154] In some implementations, when the NES-capable UE performs UL WUS transmission to a detected NES cell based on a selected SSB (e.g., selected because its corresponding RSRP is greater than a threshold), the NES-capable UE may expect to receive the on-demand SIB1 based on the selected SSB in the SSB burst if the detected NES cell transmits the on-demand SIB1. For example, the on-demand SIB1 may be associated with the selected SSB.

[0155] In some implementations, the NES-capable UE may transmit the UL WUS to a detected NES cell based on a selected SSB. The NES-capable UE may wait for receiving the on-demand SIB1 with / without the response from the detected NES cell. The NES-capable UE may decode the PBCH payload from the selected SSB in the SSB burst. The NES-capable UE may obtain the information related to Type0-PDCCH. The NES-capable UE may obtain the on-demand SIB1 based on the corresponding Type0-PDCCH. The information related to the Type0-PDCCH may be specifically associated with the selected SSB. The control signaling related to the on-demand SIB1 may be associated only with the selected SSB. This characteristic may be referred to as beam-specific, where the NES-capable UE may expect to receive the control signaling only in the PDCCH associated with the selected SSB (e.g., selected because its corresponding RSRP is greater than a threshold).

[0156] In some implementations, the NES-capable UE may transmit the UL WUS to a detected NES cell based on a selected SSB. The NES-capable UE may wait to receive the on-demand SIB1 with the response from the detected NES cell. The NES-capable UE may obtain the information related to PDCCH (e.g., CORESET and / or search space) scheduling PDSCH to receive the on-demand SIB1 from the response. The NES-capable UE may obtain the on-demand SIB1 based on PDCCH associated with the selected SSB in the SSB burst.

[0157] In some implementations, the NES-capable UE may transmit the UL WUS to a detected NES cell based on a selected SSB. The NES-capable UE may wait to receive the on-demand SIB1 with / without the response from the detected NES cell. The NES-capable UE may obtain the information related to PDCCH (e.g., CORESET and / or search space) scheduling PDSCH to receive the on-demand SIB1 from the WUS configuration. The NES-capable UE may obtain the on-demand SIB1 based on PDCCH associated with the selected SSB in the SSB burst.

[0158] FIG. 1 is a flowchart illustrating a method / process 100 performed by a UE for performing a SIB1 request operation, according to an example implementation of the present disclosure. In the action 102, the process 100 may start by camping on a first cell. The first cell may be the Cell A in the present disclosure. In the action 104, the process 100 may receive, from the first cell, a WUS configuration including a threshold.

[0159] In the action 106, the process 100 may receive, from a first NES cell, a first SSB. In the action 108, the process 100 may measure a first RSRP corresponding to the first SSB. In the action 110, the process 100 may transmit, to the first NES cell, a UL WUS based on the WUS configuration to request an OD-SIB1 in response to determining that the first RSRP is greater than the threshold. In the action 112, the process 112 may monitor a PDCCH monitoring occasion associated with the first SSB for control signaling related to the OD-SIB1. This characteristic may be referred to as beam-specific, where the UE may receive the control signaling in the PDCCH associated only with the first SSB. The process 100 may then end.

[0160] The steps / actions shown in FIG. 1 should not be construed as necessarily order dependent. The order in which the process is described is not intended to be construed as a limitation. Moreover, some of the actions shown in FIG. 1 may be omitted in some implementations and one or more actions shown in FIG. 1 may be combined.

[0161] The technical problem addressed by the method illustrated in FIG. 1 is inefficient and power-consuming PDCCH monitoring by a UE during an OD-SIB1 request procedure. The present disclosure provides a beam-specific approach in which the UE transmits an UL WUS based on an SSB having a RSRP greater than a configured threshold, and subsequently monitors only the PDCCH monitoring occasion associated with that same SSB for control signaling related to the OD-SIB1. This beam-specific association enhances energy efficiency and improves the reliability of system information acquisition for the NES cells.

[0162] In some implementations, the UE may receive, from the first NES cell, a second SSB different from the first SSB. The UE may measure a second RSRP corresponding to the second SSB. The first RSRP is greater than the threshold, while the second RSRP may be less than the threshold. The UL WUS transmitted by the UE is based on the first SSB, which has the first RSRP greater than the threshold. The PDCCH monitoring occasion associated with the first SSB may not be associated with the second SSB. In other words, the PDCCH monitoring occasion may be beam-specific. The UE may monitor for the control signaling related to the OD-SIB1 in only the PDCCH monitoring occasion that is associated with the first SSB, but not associated with the second SSB.

[0163] In some implementations, the UE may determine the PDCCH monitoring occasion associated with the first SSB based on information in the WUS configuration. For example, the WUS may indicate a CORESET and / or a search space associated with the PDCCH monitoring occasion.

[0164] In some implementations, the UE may determine the PDCCH monitoring occasion associated with the first SSB based on information in the first SSB. For example, the UE may decode the PBCH payload from the first SSB to obtain the PDCCH monitoring occasion. In some implementations, the PBCH payload may indicate a PDCCH configuration related to the SIB1.

[0165] In some implementations, the WUS configuration may also include a PCI indicating the first NES cell and a RACH occasion for transmission of the UL WUS. In some implementations, the WUS configuration may include a PCI list indicating multiple NES cells, one of which may be the first NES cell.

[0166] In some implementations, the WUS configuration may include a first sub-configuration and a second sub-configuration. The first sub-configuration may be associated with the first NES cell and include the threshold. The second sub-configuration may be associated with a second NES cell. The second NES cell may be different from the first NES cell. The first and second NES cells may be included in a PCI list in the WUS configuration. In some implementations, the WUS configuration may include multiple sub-configurations, each of which may be applicable to a respective NES cell included in the PCI list in the WUS configuration.

[0167] In some implementations, the WUS configuration may also include multiple PCIs indicating multiple NES cells associated with the first cell (e.g., the Cell A). The threshold may be common to the NES cells associated with the first cell. For example, the threshold used for evaluating the first RSRP associated with the first SSB transmitted by the first NES cell may be applicable to all NES cells that are associated with the first cell (e.g., the Cell A).

[0168] FIG. 2 is a flowchart illustrating a method / process 200 performed by a BS for supporting a SIB1 request operation, according to an example implementation of the present disclosure. In the action 202, the process 200 may start by transmitting, to a UE via a first NES cell, a first SSB. In the action 204, the process 200 may receive, from the UE via the first NES cell, a UL WUS based on a WUS configuration including a threshold. The UL WUS may request an OD-SIB1. The method illustrated in FIG. 2 is similar to that in FIG. 1, except that it is described from the perspective of the BS (instead of the UE).

[0169] In some implementations, the UE may have camped on a first cell (e.g., Cell A) and received the WUS configuration from the first cell. The UE may measure a first RSRP of the first SSB after receiving the first SSB (e.g., in the action 202). In some implementations, the UE may transmit, to the BS via the first NES cell, the UL WUS (e.g., in the action 204) in response to determining that the first RSRP of the first SSB is greater than the threshold. The UE may monitor a PDCCH monitoring occasion associated with the first SSB for control signaling related to the OD-SIB1.

[0170] FIG. 3 is a block diagram illustrating a node 300 for wireless communication in accordance with various aspects of the present disclosure. As illustrated in FIG. 3, a node 300 may include a transceiver 320, a processor 328, a memory 334, one or more presentation components 338, and at least one antenna 336. The node 300 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. 3).

[0171] Each of the components may directly or indirectly communicate with each other over one or more buses 340. The node 300 may be a UE or a BS that performs various functions disclosed with reference to FIGS. 1 through 2.

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

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

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

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

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

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

[0178] The processor 328 (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 328 may include memory. The processor 328 may process the data 330 and the instructions 332 received from the memory 334, and information transmitted and received via the transceiver 320, the baseband communications module, and / or the network communications module. The processor 328 may also process information to send to the transceiver 320 for transmission via the antenna 336 to the network communications module for transmission to a CN.

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

[0180] 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 performing a System Information Block Type 1 (SIB1) request operation, 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: 　　　　　　　　camp on a first cell; 　　　　　　　　receive, from the first cell, a Wake-Up Signal (WUS) configuration comprising a threshold; 　　　　　　　　receive, from a first Network Energy Saving (NES) cell, a first Synchronization Signal Block (SSB); 　　　　　　　　measure a first Reference Signal Received Power (RSRP) corresponding to the first SSB; 　　　　　　　　transmit, to the first NES cell, an Uplink (UL) WUS based on the WUS configuration to request an On-Demand (OD) SIB1 in response to determining that the first RSRP is greater than the threshold; and 　　　　　　　　monitor a Physical Downlink Control Channel (PDCCH) monitoring occasion associated with the first SSB for control signaling related to the OD-SIB1.

2. The UE of claim 1, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　receive, from the first NES cell, a second SSB; and 　　　　measure a second RSRP corresponding to the second SSB, wherein: 　　　　　　　　the second RSRP is less than the threshold, and 　　　　　　　　the PDCCH monitoring occasion is not associated with the second SSB.

3. The UE of claim 1, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　determine the PDCCH monitoring occasion associated with the first SSB based on information in the WUS configuration.

4. The UE of claim 1, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　determine the PDCCH monitoring occasion associated with the first SSB based on information in the first SSB.

5. The UE of claim 1, wherein: 　　　　the WUS configuration further comprises a Physical Cell Identity (PCI) indicating the first NES cell and a Random Access Channel (RACH) occasion for transmission of the UL WUS.

6. The UE of claim 1 wherein: 　　　　the WUS configuration comprises a first sub-configuration and a second sub-configuration, 　　　　the first sub-configuration is associated with the first NES cell and comprises the threshold, and 　　　　the second sub-configuration is associated with a second NES cell.

7. The UE of claim 1, wherein: 　　　　the WUS configuration further comprises a plurality of Physical Cell Identities (PCIs) indicating a plurality of NES cells associated with the first cell, and 　　　　the threshold is common to the plurality of NES cells associated with the first cell.

8. A Base Station (BS) configured to support a System Information Block Type 1 (SIB1) request operation, 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 a User Equipment (UE) via a first Network Energy Saving (NES) cell, a first Synchronization Signal Block (SSB); and 　　　　　　　　receive, from the UE via the first NES cell, an Uplink (UL) Wake-Up Signal (WUS) based on a WUS configuration comprising a threshold, wherein: 　　　　　　　　the UE camps on a first cell and receives the WUS configuration from the first cell, 　　　　　　　　a first Reference Signal Received Power (RSRP) of the first SSB measured by the UE is greater than the threshold, 　　　　　　　　the UL WUS requests an On-Demand (OD) SIB1, and 　　　　　　　　the UE monitors a Physical Downlink Control Channel (PDCCH) monitoring occasion associated with the first SSB for control signaling related to the OD-SIB1.

9. The BS of claim 8, wherein the one or more computer-executable instructions, when executed by the at least one processor, further cause the BS to: 　　　　transmit, to the UE via the first NES cell, a second SSB, wherein: 　　　　　　　　a second RSRP of the second SSB measured by the UE is less than the threshold, and 　　　　　　　　the PDCCH monitoring occasion is not associated with the second SSB.

10. The BS of claim 8, wherein: 　　　　the UE determines the PDCCH monitoring occasion associated with the first SSB based on information in the WUS configuration.

11. The BS of claim 8, wherein: 　　　　the UE determines the PDCCH monitoring occasion associated with the first SSB based on information in the first SSB.

12. The BS of claim 8, wherein: 　　　　the WUS configuration further comprises a Physical Cell Identity (PCI) indicating the first NES cell and a Random Access Channel (RACH) occasion for transmission of the UL WUS.

13. The BS of claim 8, wherein: 　　　　the WUS configuration comprises a first sub-configuration and a second sub-configuration, 　　　　the first sub-configuration is associated with the first NES cell and comprises the threshold, and 　　　　the second sub-configuration is associated with a second NES cell.

14. The BS of claim 8, wherein: 　　　　the WUS configuration further comprises a plurality of Physical Cell Identities (PCIs) indicating a plurality of NES cells associated with the first cell, and 　　　　the threshold is common to the plurality of NES cells associated with the first cell.

15. A method performed by a User Equipment (UE) for performing a System Information Block Type 1 (SIB1) request operation, the method comprising: 　　　　camping on a first cell; 　　　　receiving, from the first cell, a Wake-Up Signal (WUS) configuration comprising a threshold; 　　　　receiving, from a first Network Energy Saving (NES) cell, a first Synchronization Signal Block (SSB); 　　　　measuring a first Reference Signal Received Power (RSRP) corresponding to the first SSB; 　　　　transmitting, to the first NES cell, an Uplink (UL) WUS based on the WUS configuration to request an On-Demand (OD) SIB1 in response to determining that the first RSRP is greater than the threshold; and 　　　　monitoring a PDCCH monitoring occasion associated with the first SSB for control signaling related to the OD-SIB1.

Images