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

Abstract

A User Equipment (UE) for supporting on-demand system information block 1 (OD-SIB1) 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, a master information block (MIB), the MIB including a cellBarred indication; ignore the cellBarred indication; determine a k_SSB; determine whether the k_SSB falls within a first range; and in response to determining that the k_SSB falls within the first range, determine that the first cell is barred. In addition, a method and a Base Station (BS) are also provided.

Description

METHOD AND APPARATUS FOR SUPPORTING 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 supporting 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 supporting on-demand information in the wireless communication networks.

[0004] According to a first aspect of the present disclosure, a User Equipment (UE) for supporting on-demand system information block 1 (OD-SIB1) in a wireless communication system 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. When executed by the at least one processor, the instructions cause the UE to: receive, from a first cell, a master information block (MIB), the MIB including a cellBarred indication; ignore the cellBarred indication; determine a k_SSB; determine whether the k_SSB falls within a first range; and in response to determining that the k_SSB falls within the first range, determine that the first cell is barred. In a case that the UE is operating in the frequency range 1 (FR1), the k_SSB is determined based on an ssb-SubcarrierOffset field and a physical broadcast channel (PBCH) payload, and the first range includes 30 and 31. In a case that the UE is operating in frequency range 2 (FR2), the k_SSB is determined based on the ssb-SubcarrierOffset field, and the first range includes 14 and 15.

[0005] In an implementation of the first aspect, in response to determining that the k_SSB falls within the first range, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: perform a cell (re)selection procedure to a second cell.

[0006] In another implementation 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 whether the k_SSB falls within a second range. The second range spans from 0 to 23 in a case that the UE is operating in FR1, and from 0 to 11 in a case that the UE is operating in FR2. In response to determining that the k_SSB falls within the second range, the instructions cause the UE to: determine that a system information block 1 (SIB1) of the first cell is on-demand and that the SIB1 is currently broadcast by the first cell; and in response to determining that the SIB1 is currently broadcast by the first cell, receive the SIB1 based on at least one of the ssb-SubcarrierOffset field and a pdcch-ConfigSIB1 field.

[0007] In another implementation of the first aspect, the MIB is received via a PBCH and includes the ssb-SubcarrierOffset field and the pdcch-ConfigSIB1 field. The one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: apply the ssb-SubcarrierOffset field, the PBCH payload associated with the PBCH, and the pdcch-ConfigSIB1 field.

[0008] In another implementation 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 whether the k_SSB falls within a third range. The third range spans from 24 to 29 in a case that the UE is operating in FR1, and from 12 to 13 in a case that the UE is operating in FR2. In response to determining that the k_SSB falls within the third range, the instructions cause the UE to: determine that a system information block 1 (SIB1) of the first cell is on-demand and that the SIB1 is not currently broadcast by the first cell; and in response to determining that the SIB1 is not currently broadcast by the first cell, monitor an SSB for a second cell based on at least one of the ssb-SubcarrierOffset field, the PBCH payload, and a pdcch-ConfigSIB1 field.

[0009] In another implementation of the first aspect, the second cell periodically provides SIB1 broadcasting.

[0010] In another implementation of the first aspect, the first cell is a network energy saving (NES) cell.

[0011] According to a second aspect of the present disclosure, a Base Station (BS) for supporting on-demand system information block 1 (OD-SIB1) in a wireless communication system 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. When executed by the at least one processor, the instructions cause the BS to: generate a master information block (MIB) for a first cell, the MIB including a cellBarred indication; and broadcast the MIB. The MIB is configured to cause the UE to: ignore the cellBarred indication; determine a k_SSB; determine whether the k_SSB falls within a first range; and in response to determining that the k_SSB falls within the first range, determine that the first cell is barred. In a case that the UE is operating in the FR1, the k_SSB is determined based on an ssb-SubcarrierOffset field and a PBCH payload, and the first range includes 30 and 31. In a case that the UE is operating in FR2, the k_SSB is determined based on the ssb-SubcarrierOffset field, and the first range includes 14 and 15.

[0012] In an implementation of the second aspect, the MIB is configured to further cause the UE to: in response to determining that the k_SSB falls within the first range, perform a cell (re)selection procedure to a second cell.

[0013] In another implementation of the second aspect, the MIB is configured to further cause the UE to: determine whether the k_SSB falls within a second range. The second range spans from 0 to 23 in a case that the UE is operating in FR1, and from 0 to 11 in a case that the UE is operating in FR2. In response to determining that the k_SSB falls within the second range, the instructions cause the UE to: determine that a system information block 1 (SIB1) of the first cell is on-demand and that the SIB1 is currently broadcast by the first cell; and in response to determining that the SIB1 is currently broadcast by the first cell, receive the SIB1 based on at least one of the ssb-SubcarrierOffset field and a pdcch-ConfigSIB1 field.

[0014] In another implementation of the second aspect, the MIB is received via a PBCH and includes the ssb-SubcarrierOffset field and the pdcch-ConfigSIB1 field. The MIB is configured to further cause the UE to: apply the ssb-SubcarrierOffset field, the PBCH payload associated with the PBCH, and the pdcch-ConfigSIB1 field.

[0015] In another implementation of the second aspect, the MIB is configured to further cause the UE to: determine whether the k_SSB falls within a third range. The third range spans from 24 to 29 in a case that the UE is operating in FR1, and from 12 to 13 in a case that the UE is operating in FR2. In response to determining that the k_SSB falls within the third range, the instructions cause the UE to: determine that a system information block 1 (SIB1) of the first cell is on-demand and that the SIB1 is not currently broadcast by the first cell; and in response to determining that the SIB1 is not currently broadcast by the first cell, monitor an SSB for a second cell based on at least one of the ssb-SubcarrierOffset field, the PBCH payload, and a pdcch-ConfigSIB1 field.

[0016] In another implementation of the second aspect, the second cell periodically provides SIB1 broadcasting.

[0017] In another implementation of the second aspect, the first cell is a network energy saving (NES) cell.

[0018] According to a third aspect of the present disclosure, a method performed by a User Equipment (UE) for supporting on-demand system information block 1 (OD-SIB1) is provided. The method includes: receiving, from a first cell, a master information block (MIB), the MIB including a cellBarred indication; ignoring the cellBarred indication; determining a k_SSB; determining whether the k_SSB falls within a first range; and in response to determining that the k_SSB falls within the first range, determining that the first cell is barred. In a case that the UE is operating in the FR1, the k_SSB is determined based on an ssb-SubcarrierOffset field and a PBCH payload, and the first range includes 30 and 31. In a case that the UE is operating in FR2, the k_SSB is determined based on the ssb-SubcarrierOffset field, and the first range includes 14 and 15.

[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 supporting on-demand system information block 1 (OD-SIB1), according to an example implementation of the present disclosure.

[0021] FIG. 2 is a flowchart illustrating a method / process 200 performed by a UE for supporting OD-SIB1, 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: Abbreviation　　　　Full name ACK　　　　Acknowledgment ARFCN　　　　Absolute Radio-Frequency Channel Number ATG　　　　Air-to-ground BA　　　　Bandwidth Adaptation BFR　　　　Beam Failure Recovery BS　　　　Base Station BWP　　　　Bandwidth Part CA　　　　Carrier Aggregation CD-SSB　　　　Cell-Defining Synchronization Signal Block CE　　　　Control Element CORESET　　　　Control resource set COT　　　　Channel Occupancy Time C-RNTI　　　　Cell-Radio Network Temporary Identifier CSI　　　　Channel State Information CSS　　　　Common Search Space DC　　　　Dual Connectivity DCI　　　　Downlink Control Information DCP　　　　DCI with CRC scrambled by PS-RNTI DL　　　　Downlink DRX　　　　Discontinuous Reception DTX　　　　Discontinuous Transmission 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 IE　　　　Information Element L1 / L2 / L3　　　　Layer 1 / Layer 2 / Layer 3 MAC　　　　Medium Access Control MIB　　　　Master Information Block MIMO　　　　Multiple Input Multiple Output Msg1　　　　Message 1 MsgA　　　　Message A MsgB　　　　Message B NACK　　　　Negative Acknowledgment NCGI　　　　NR Cell Global Identifier NGSO　　　　Non-GeoSynchronous Orbit NTN　　　　Non-Terrestrial Network NW　　　　Network OSI　　　　Other SI / On-demand SI PBCH　　　　Physical Broadcast Channel PCell　　　　Primary Cell PCI　　　　Physical Cell Identity PDCCH　　　　Physical Downlink Control Channel PDSCH　　　　Physical Downlink Shared Channel PHY　　　　Physical (layer) PL-RS　　　　Path-Loss Reference Signal PRACH　　　　Physical Random Access Channel PS　　　　Power Saving PSS　　　　Primary Synchronization Signal PUCCH　　　　Physical Uplink Control Channel PUSCH　　　　Physical Uplink Shared Channel RA　　　　Random Access RACH　　　　Random Access Channel RAR　　　　Random Access Response Rel　　　　Release RLF　　　　Radio Link Failure RNTI　　　　Radio Network Temporary Identifier RRC　　　　Radio Resource Control RRM　　　　Radio Resource Management RSRP　　　　Reference Signal Received Power RTT　　　　Round-Trip Time 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 SR　　　　Scheduling Request SS　　　　Synchronization Signal SSB　　　　Synchronization Signal Block SSS　　　　Secondary Synchronization Signal TA　　　　Timing Advance TNL　　　　Transport Network Layer UCI　　　　Uplink Control Information UE　　　　User Equipment UL　　　　Uplink 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] 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.

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

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

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

[0051] Serving cell: The Serving cell may refer to the cell on which the UE is camped.

[0052] Special Cell (SpCell): The SpCell may refer to the Primary Cell (PCell) of the Master Cell Group (MCG) or the Primary Secondary Cell (PSCell) of the Secondary Cell Group (SCG), depending on whether the Medium Access Control (MAC) entity is associated with the MCG or the SCG, respectively. Otherwise, the SpCell may refer to the PCell. The SpCell may support Physical Uplink Control Channel (PUCCH) transmission and contention-based Random Access, and may be always activated.

[0053] In some implementations, a Cell A may be defined as a cell that is periodically transmitting at least its own System Information Block 1 (SIB1). In some implementations, a Cell A may transmit Wake-Up Signal (WUS) configuration(s) which include one or more following information in Table 1.

[0054] In some implementations, a Network Energy Saving (NES) cell may be defined as a cell that may transmit SIB1 transmission in response to an Uplink (UL) WUS from a UE. In some implementations, the NES cell may transmit Synchronization Signal Block (SSB), which may be referred to as an “NES SSB”.

[0055] In some implementations, a UE which does not support on-demand SIB1 (OD-SIB1) should be barred by the NES cell, which may be referred to as an “OD-SIB1 cell”. An “OD-SIB1 cell” may be defined as a cell in which the SIB1 is not always being broadcast, or the SIB1 is on-demand. When the SIB1 is not being broadcast (or the SIB1 is off), a UE that supports on-demand SIB1 may transmit a UL WUS to acquire or request SIB1. Cell A may not expect that the SIB1 can be dynamically turned on or off. In the present disclosure, implementations about how to bar a UE which does not support on-demand SIB1 (OD-SIB1) but not to bar a UE which supports on-demand SIB1 (OD-SIB1) may be provided.

[0056] In some implementations, a first method may bar a UE which does not support OD-SIB1 (e.g., a legacy UE) by setting the cellBarred field in Master Information Block (MIB) to “barred”. In some implementations, a second method may provide a “no SIB1 indication” via a k_SSB (e.g., which may be determined by the ssb-SubcarrierOffset field in MIB and / or a Physical Broadcast Channel (PBCH) payload).

[0057] Considering the first method, even if a UE supporting OD-SIB1 (e.g., an OD-SIB1 capable UE) ignores the cellBarred bit in MIB, or if the OD-SIB1 capable UE still acquires SIB1 when a k_SSB (or the ssb-SubcarrierOffset field) indicates that SIB1 is transmitted, the mechanisms for how a network (e.g., a next-generation Node B (gNB)) can bar OD-SIB1 capable UE(s) may need further design.

[0058] Considering the second method, a legacy UE may be barred while a k_SSB is set to 30. However, how OD-SIB1 capable UE(s) determine the k_SSB in MIB (and / or PBCH payload) and perform relevant behaviors may need further design.

[0059] In the present disclosure, a design is provided for how to respectively perform access control for at least one of a legacy UE (e.g., a non-NES-capable UE that may not ignore the cellBarred bit in the MIB), a legacy UE that may ignore the cellBarred bit in the MIB but is not a NES-capable UE, and a NES-capable UE.

[0060] A “Legacy UE” may be defined as a UE which may not ignore the cellBarred bit in the MIB and is not an OD-SIB1 capable UE. A “UE ignoring cellBarred” may be defined as a UE that may ignore the cellBarred bit in the MIB but is not a NES-capable UE. An “OD-SIB1 capable UE” may be defined as a UE that supports OD-SIB1 capability. More specifically, the “UE ignoring cellBarred” may be a UE that supports at least one of Non-Terrestrial Networks (NTN), Air-to-Ground (ATG), Reduced Capability (RedCap), 2Rx Extended Reality (XR), cell Discontinuous Transmission (DTX), and cell Discontinuous Reception (DRX).

[0061] In some implementations, a k_SSB (or the ssb-SubcarrierOffset IE) may be defined or configured into four ranges as follows: 　　　　- Range 1: The k_SSB (or the ssb-SubcarrierOffset IE) is set to 0-23 in a case of FR1 and / or is set to 0-11 in a case of FR2. 　　　　- Range 2: The k_SSB (or the ssb-SubcarrierOffset IE) is set to 24-29 in a case of FR1 and / or is set to 12-13 in a case of FR2. 　　　　- Range 3: The k_SSB (or the ssb-SubcarrierOffset IE) is set to 30 in a case of FR1 and / or is set to 14 in a case of FR2. 　　　　- Range 4: The k_SSB (or the ssb-SubcarrierOffset IE) is set to 31 in a case of FR1 and / or is set to 15 in a case of FR2.

[0062] In some implementations, upon detection of an SSB, the UE may determine, from the MIB, that a CORESET for a Type0-PDCCH CSS set is present if the k_SSB < 24 for FR1, or if the k_SSB < 12 for FR2. The UE may determine, from the MIB (e.g., and a PBCH payload), that the CORESET for the Type0-PDCCH CSS set is not present if the k_SSB > 23 for FR1 or if the k_SSB > 11 for FR2. The CORESET for the Type0-PDCCH CSS set may be provided by the PDCCH-ConfigCommon IE.

[0063] Four cases will be described in the following.

[0064] Case 1: When a UE finds the cellBarred bit in the MIB is set to “barred,” a legacy UE and an OD-SIB1 capable UE may be barred. That is, the legacy UE and the OD-SIB1 capable UE may consider that the cell is barred and may not monitor the cell again for a time period, e.g., 300 seconds. A UE ignoring cellBarred may ignore the cellBarred bit in the MIB (e.g., during a MIB reception process and / or a decoding process).

[0065] In some implementations, upon receiving the MIB, the UE ignoring cellBarred may perform at least one of the following procedures: (1) storing the acquired MIB, (2) checking if the UE is in RRC_IDLE or in RRC_INACTIVE, or if the UE is in RRC_CONNECTED while a T311 is running, and (3) applying the received systemFrameNumber, pdcch-ConfigSIB1, subCarrierSpacingCommon, ssb-SubcarrierOffset and dmrs-TypeA-Position IEs. The UE may not check whether the cellBarred bit in the MIB is set to “barred” or “not barred”.

[0066] In some implementations, if the UE ignoring cellBarred determines that the k_SSB is set to Range 1, the UE may find a CORESET#0 (or a CORESET for a Type0-PDCCH CSS) and a Search space #0 (or a Type0-PDCCH CSS set) according to the ssb-SubcarrierOffset IE and / or the pdcch-ConfigSIB1 IE. After the UE finds the CORESET#0 and the Search space #0, the UE may find SIB1 according to the CORESET#0 and the Search space #0.

[0067] In some implementations, if the cell is an OD-SIB1 cell, the OD-SIB1 of the OD-SIB1 cell may provide cellBarred information which is set to “barred”, may not provide the cellBarred information, or may provide the cellBarred information and set to “not barred”. The cellBarred information may include at least one of the cellBarred2RxXR, cellBarredATG, cellBarred-eRedCap1Rx, cellBarred-eRedCap2Rx, cellBarredFixedVSAT, cellBarredMobileVSAT, cellBarredNES, cellBarredNTN, cellBarredRedCap1Rx, and cellBarredRedCap2Rx IEs.

[0068] In some implementations, if the UE ignoring cellBarred determines that the k_SSB is set to Range 2, the UE may find a second SSB according to the ssb-SubcarrierOffset IE, a PBCH payload, and / or the pdcch-ConfigSIB1 IE. If the UE detects the second SSB and the second SSB does not provide a CORESET for a Type0-PDCCH CSS set, the UE may ignore the information related to a GSCN of SSB locations for performing cell search.

[0069] In some implementations, if the cell is an OD-SIB1 cell, the cell may provide information of an SSB of Cell A to the UE via the ssb-SubcarrierOffset IE and / or the pdcch-ConfigSIB1 IE.

[0070] In some implementations, if the UE ignoring cellBarred determines that the k_SSB is set to Range 3, the UE may not understand (e.g., as the k_SSB is undefined to the UE), and the UE may perform a cell (re)selection procedure.

[0071] In some implementations, if the UE ignoring cellBarred determines that the k_SSB is set to Range 4, the UE may determine that there is no SSB having an associated CORESET#0 and / or search space #0 within a GSCN range. The UE may then perform a cell (re)selection procedure outside the GSCN range.

[0072] In some implementations, if a UE does not detect any SSB providing a CORESET for a Type0-PDCCH CSS set within a time period, the UE may ignore information related to the GSCN of SSB locations when performing a cell search procedure. The time period may be determined by the UE itself or pre-configured by the gNB.

[0073] From the perspective of a gNB or the network, setting the cellBarred field in the MIB to “barred” may prioritize access by UEs that ignore the cellBarred field in the MIB. A legacy gNB may further support the barring mechanism for OD-SIB capable (or NES-capable) UEs, regardless of whether SIB1 is broadcast.

[0074] Case 2: When the UE finds cellBarred in the MIB is set to barred, only a legacy UE may be barred. A UE ignoring cellBarred and an OD-SIB1 capable UE may ignore the cellBarred bit in the MIB.

[0075] In some implementations, if the UE is an OD-SIB1 capable UE, the UE may ignore the cellBarred bit in the MIB. In some implementations, if the UE is an OD-SIB1 capable UE and the ssb-SubcarrierOffset IE (or a k_SSB) indicates that an OD-SIB1 is transmitted in the cell, the UE may ignore the cellBarred bit in the MIB. Otherwise, the UE may not ignore the cellBarred bit and may follow the cellBarred bit to determine the cell to be barred if the value of the cellBarred bit is set to 1 (or is set to “barred”).

[0076] Barring OD-SIB1 capable UE(s) by setting k_SSB to a specific value (e.g., 30 or 31)

[0077] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB (or an ssb-SubcarrierOffset IE) set to a specific value (e.g., 30 or 31), the UE may determine the cell to be barred. In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB (or an ssb-SubcarrierOffset IE) not set to the specific value (e.g., 30 or 31), the UE may determine that the cell is not barred.

[0078] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine that the cell is an OD-SIB1 cell and the OD-SIB1 is being broadcast (or OD-SIB1 is on or an OD-SIB1 transmission status associated with the cell is “activated” or “on”). The UE may find a CORESET#0 (or a CORESET for a Type0-PDCCH CSS) and a Search space #0 (or a Type0-PDCCH CSS set) for the OD-SIB1 according to the ssb-SubcarrierOffset IE, a PBCH payload, and / or the pdcch-ConfigSIB1 IE. After the UE finds the CORESET#0 and the Search space #0, the UE may find the OD-SIB1 according to the CORESET#0 and the Search space #0.

[0079] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine the CORESET#0 and / or the Search space #0 for the OD-SIB1 via the ssb-SubcarrierOffset IE, the PBCH payload, and / or the pdcch-ConfigSIB1 IE.

[0080] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine the CORESET#0 and / or the Search space #0 for the OD-SIB1 rather than determining a SSB, a CORESET#0, and / or a Search space #0 for Cell A or a second SSB via the ssb-SubcarrierOffset IE, the PBCH payload, and / or the pdcch-ConfigSIB1 IE.

[0081] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may skip the WUS configuration reception or the WUS transmission even though the UE has received the configuration from a Cell A or a NES Cell, and the UE may acquire the SIB1 followed by legacy operations (e.g., the operations defined in 3GPP Rel-15 technical specifications such as TS 38.213 V15.15.0).

[0082] In some implementations, if the UE is an OD-SIB1 capable UE, the UE detects or monitors an SSB with a k_SSB set to Range 1, and the UE has stored a WUS configuration, the UE may apply the CORESET#0 (or CORESET for Type0-PDCCH CSS) and the Search space #0 (or Type0-PDCCH CSS set) information configured in the WUS configuration to acquire the SIB1 without transmitting the UL WUS.

[0083] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 2, the UE may determine that the cell is an OD-SIB1 cell and the OD-SIB1 is not being broadcast (or OD-SIB1 is off, or OD-SIB1 is now on-demand or an OD-SIB1 transmission status associated with the cell is “de-activated” or “off”).

[0084] In some implementations, (e.g., if the UE does not store a WUS configuration,) the UE may find, determine, detect, or monitor an SSB for Cell A or a second SSB via the ssb-SubcarrierOffset IE, the PBCH payload, and / or the pdcch-ConfigSIB1 IE.

[0085] In some implementations, if the UE has stored a WUS configuration and the WUS configuration includes OD-SIB1 CORESET#0 and / or Search space #0 information, the UE may detect the CORESET#0 and / or the Search space #0 for OD-SIB1 via the CORESET#0 and / or Search space #0 information in the WUS configuration, and may not detect, determine, or monitor a second SSB or cell via the pdcch-ConfigSIB1 IE. In a case where the UE can find, detect, monitor, or receive OD-SIB1, the UE may not need to detect, determine, or monitor a second SSB or cell via the pdcch-ConfigSIB1 IE. In a case where the UE cannot find, detect, monitor, or receive OD-SIB1, the UE may detect, determine, or monitor a second SSB or cell via the pdcch-ConfigSIB1 IE or the UE may transmit a UL WUS according to the WUS configuration.

[0086] In some implementations, if a Cell A coordinates with a NES Cell and the Cell A knows the NES Cell would like to bar the OD-SIB1 capable UE, the Cell A may not provide the relevant information of that NES Cell in a WUS configuration. In some implementations, no matter whether a NES Cell will or will not bar an OD-SIB1 capable UE, the NES Cell may always provide the relevant information of the NES Cell in a WUS configuration. For example, a UE may not always assume that the NES Cells provided in the WUS configuration are not barred.

[0087] Barring OD-SIB1 capable UE(s) by introducing a cellBarred-ODSIB1 IE into OD-SIB1 and setting the value of the cellBarred-ODSIB1 IE to “barred”

[0088] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine that the cell is an OD-SIB1 cell and the OD-SIB1 is being broadcast (or OD-SIB1 is on). The UE may find a CORESET#0 (or a CORESET for a Type0-PDCCH CSS) and a Search space #0 (or a Type0-PDCCH CSS set) for OD-SIB1 according to the ssb-SubcarrierOffset IE, a PBCH payload, and / or the pdcch-ConfigSIB1 IE. After the UE finds the CORESET#0 and the Search space #0, the UE may find the OD-SIB1 according to the CORESET#0 and the Search space #0.

[0089] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine the CORESET#0 and / or the Search space #0 for OD-SIB1 via the ssb-SubcarrierOffset IE, the PBCH payload, and / or the pdcch-ConfigSIB1 IE.

[0090] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine the CORESET#0 and / or the Search space #0 for OD-SIB1 rather than determine an SSB, a CORESET#0, and / or a Search space #0 for a Cell A or a second SSB via the ssb-SubcarrierOffset IE and / or the pdcch-ConfigSIB1 IE.

[0091] In some implementations, the UE may receive an OD-SIB1 including a cellBarred-ODSIB1 IE according to the CORESET#0 and / or the Search space #0 for the OD-SIB1 (or according to a WUS configuration). The cellBarred-ODSIB1 IE may be used to indicate whether the cell bars the OD-SIB1 capable UE. If the cellBarred-ODSIB1 IE is set to “barred” or the cellBarred-ODSIB1 IE is not provided, the UE may determine that the cell is barred for an OD-SIB1 capable UE. If the cellBarred-ODSIB1 IE is set to “not barred”, the UE may determine that the cell is not barred for an OD-SIB1 capable UE.

[0092] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 2, the UE may determine that the cell is an OD-SIB1 cell and the OD-SIB1 is not broadcasting (or OD-SIB1 is off, or OD-SIB1 is now on-demand).

[0093] In some implementations, (e.g., if the UE does not store a WUS configuration,) the UE may find, determine, detect, or monitor an SSB for a Cell A or a second SSB via the ssb-SubcarrierOffset IE and / or the pdcch-ConfigSIB1 IE.

[0094] In some implementations, if the UE has stored a WUS configuration and the WUS configuration includes OD-SIB1 CORESET#0 and / or Search space #0 information, the UE may detect the CORESET#0 and / or the Search space #0 for the OD-SIB1 via the CORESET#0 and / or Search space #0 information in the WUS configuration, and may not detect, determine, or monitor a second SSB or cell via the pdcch-ConfigSIB1 IE. In a case where the UE can find, detect, monitor, or receive OD-SIB1, the UE may not need to detect, determine, or monitor a second SSB or cell via the pdcch-ConfigSIB1 IE. In a case where the UE cannot find, detect, monitor, or receive OD-SIB1, the UE may detect, determine, or monitor a second SSB or cell via the pdcch-ConfigSIB1 IE or the UE may transmit UL WUS according to the WUS configuration.

[0095] In some implementations, if the UE receives an OD-SIB1 after transmitting a UL WUS and the OD-SIB1 includes a cellBarred-ODSIB1 IE, the cellBarred-ODSIB1 IE may be used to indicate whether the cell bars the OD-SIB1 capable UE. If the cellBarred-ODSIB1 IE is set to “barred” or the cellBarred-ODSIB1 IE is not provided, the UE may determine that the cell is barred for an OD-SIB1 capable UE. If the cellBarred-ODSIB1 IE is set to “not barred,” the UE may determine that the cell is not barred for an OD-SIB1 capable UE.

[0096] In some implementations, if a Cell A coordinates with a NES Cell and the Cell A knows the NES Cell would like to bar the OD-SIB1 capable UE, the Cell A may not provide the relevant information of that NES Cell in a WUS configuration. In some implementations, no matter whether a NES Cell will or will not bar an OD-SIB1 capable UE, the NES Cell may always provide the relevant information of the NES Cell in a WUS configuration. For example, a UE may not always assume that the NES Cells provided in the WUS configuration are not barred.

[0097] Barring OD-SIB1 capable UE(s) by setting k_SSB to Range 2, 3, or 4

[0098] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine that the cell is an OD-SIB1 cell and the OD-SIB1 is being broadcast (or OD-SIB1 is on). The UE may find a CORESET#0 (or a CORESET for a Type0-PDCCH CSS) and a Search space #0 (or a Type0-PDCCH CSS set) for the OD-SIB1 according to the ssb-SubcarrierOffset IE, a PBCH payload, and / or the pdcch-ConfigSIB1 IE. After the UE finds the CORESET#0 and the Search space #0, the UE may find the OD-SIB1 according to the CORESET#0 and the Search space #0.

[0099] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine the CORESET#0 and / or Search space #0 for the OD-SIB1 via the ssb-SubcarrierOffset IE, the PBCH payload, and / or the pdcch-ConfigSIB1 IE.

[0100] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine the CORESET#0 and / or the Search space #0 for the OD-SIB1 rather than determine an SSB, a CORESET#0, and / or a Search space #0 for a Cell A or a second SSB via the ssb-SubcarrierOffset IE, the PBCH payload, and / or the pdcch-ConfigSIB1 IE.

[0101] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 2, 3, or 4, the UE may determine that the cell is barred for an OD-SIB1 UE. The UE may perform a cell (re)selection procedure.

[0102] In some implementations, if a UE does not detect any SSB providing a CORESET for a Type0-PDCCH CSS set within a time period determined by the UE, the UE may ignore the information related to the GSCN of SSB locations in performing a cell search procedure. The UE may determine the time period by itself. Alternatively, the value of the time period may be pre-configured by the gNB.

[0103] Case 3: When the cellBarred bit in the MIB is set to “not barred,” a legacy UE, a UE ignoring cellBarred, and an OD-SIB1 capable UE may need to check the k_SSB.

[0104] In some implementations, if a legacy UE detects, monitors, receives, or finds the value of a k_SSB is set to 30 (or the k_SSB is set to Range 3), the UE cannot understand the value and may perform a cell (re)selection procedure or may determine that the cell is barred.

[0105] In some implementations, if the UE ignoring cellBarred detects, monitors, receives, or finds the value of a k_SSB is set to 30, the UE cannot understand the value and may perform a cell (re)selection procedure or may determine that the cell is barred.

[0106] In some implementations, if the OD-SIB1 capable UE detects, monitors, receives, or finds the value of a k_SSB is set to 30, the UE may determine that the cell is an OD-SIB1 cell. The UE may not determine whether the OD-SIB1 is being broadcast or not.

[0107] In some implementations, (e.g., if the UE does not store a WUS configuration,) the UE may find, determine, detect, or monitor an SSB for a Cell A or a second SSB (via the pdcch-ConfigSIB1 IE) to acquire or receive a WUS configuration from the Cell A and transmit a UL WUS to acquire SIB1.

[0108] In some implementations, if the UE has stored a WUS configuration and the WUS configuration includes OD-SIB1 CORESET#0 and / or Search space #0 information, the UE may detect or receive the CORESET#0 and / or the Search space #0 for the OD-SIB1 via the CORESET#0 and / or Search space #0 information in the WUS configuration, and may not detect, determine, or monitor a second SSB or Cell A via the pdcch-ConfigSIB1 IE. In a case where the UE can find, detect, monitor, or receive the CORESET#0 and / or the Search space #0 for the OD-SIB1 according to the OD-SIB1 CORESET#0 and / or Search space #0 information in the WUS configuration, the UE may not detect, determine, or monitor a second SSB or Cell A via the pdcch-ConfigSIB1 IE. In a case where the UE cannot find, detect, monitor, or receive the CORESET#0 and / or the Search space #0 for OD-SIB1 according to the OD-SIB1 CORESET#0 and / or Search space #0 information in the WUS configuration, the UE may detect, determine, or monitor a second SSB or cell via the pdcch-ConfigSIB1 IE or the UE may transmit a UL WUS according to the WUS configuration. After acquiring the SIB1, the UE may check whether the UE is barred by checking the cellBarred-ODSIB1 IE in the OD-SIB1.

[0109] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine that the cell is an OD-SIB1 cell and the OD-SIB1 is being broadcast (or OD-SIB1 is on, or an OD-SIB1 transmission status associated with the cell is “activated” or “on”). The UE may find a CORESET#0 (or a CORESET for a Type0-PDCCH CSS) and a Search space #0 (or a Type0-PDCCH CSS set) for the OD-SIB1 according to the ssb-SubcarrierOffset IE, a PBCH payload, and / or the pdcch-ConfigSIB1 IE. After the UE finds the CORESET#0 and the Search space #0, the UE may find the OD-SIB1 according to the CORESET#0 and the Search space #0.

[0110] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine the CORESET#0 and / or Search space #0 for the OD-SIB1 via the ssb-SubcarrierOffset IE, the PBCH payload, and / or the pdcch-ConfigSIB1 IE.

[0111] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may determine the CORESET#0 and / or the Search space #0 for the OD-SIB1 rather than determine an SSB, a CORESET#0, and / or a Search space #0 for a Cell A or a second SSB via the ssb-SubcarrierOffset IE, the PBCH payload, and / or the pdcch-ConfigSIB1 IE.

[0112] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 1, the UE may skip the WUS configuration reception or WUS transmission even though the UE has received the configuration from a Cell A or a NES Cell, and the UE may acquire the SIB1 followed by legacy operations (e.g., the operations defined in 3GPP Rel-15 technical specifications such as TS 38.213 V15.15.0).

[0113] In some implementations, if the UE is an OD-SIB1 capable UE, the UE detects or monitors an SSB with a k_SSB set to Range 1, and the UE has stored a WUS configuration, the UE may apply the CORESET#0 (or a CORESET for a Type0-PDCCH CSS) and a Search space #0 (or a Type0-PDCCH CSS set) information configured in the WUS configuration to acquire the SIB1 without transmitting the UL WUS.

[0114] In some implementations, if the UE is an OD-SIB1 capable UE and the UE detects or monitors an SSB with a k_SSB set to Range 2, the UE may determine that the cell is an OD-SIB1 cell and the OD-SIB1 is not being broadcast (or OD-SIB1 is off, or OD-SIB1 is now on-demand, or an OD-SIB1 transmission status associated with the cell is “de-activated” or “off”).

[0115] In some implementations, (e.g., if the UE does not store a WUS configuration,) the UE may find, determine, detect, or monitor an SSB for a Cell A or a second SSB via the ssb-SubcarrierOffset IE, a PBCH payload, and / or the pdcch-ConfigSIB1 IE.

[0116] In some implementations, if the UE has stored a WUS configuration and the WUS configuration includes OD-SIB1 CORESET#0 and / or Search space #0 information, the UE may detect the CORESET#0 and / or the Search space #0 for the OD-SIB1 via the CORESET#0 and / or Search space #0 information in the WUS configuration, and may not detect, determine, or monitor a second SSB or cell via the pdcch-ConfigSIB1 IE. In a case where the UE can find, detect, monitor, or receive the OD-SIB1, the UE may not need to detect, determine, or monitor a second SSB or cell via the pdcch-ConfigSIB1 IE. In a case where the UE cannot find, detect, monitor, or receive the OD-SIB1, the UE may detect, determine, or monitor a second SSB or cell via the pdcch-ConfigSIB1 IE or the UE may transmit a UL WUS according to the WUS configuration.

[0117] Case 4: When a UE ignoring cellBarred also supports OD-SIB1

[0118] In some implementations, if a UE supports at least one of NTN, ATG, RedCap, 2Rx XR, cell DTX, and cell DRX, and also supports the OD-SIB1, the UE may ignore the cellBarred bit. When the UE detects that a k_SSB is set to Range 1, the UE may determine that the cell is an OD-SIB1 cell and the OD-SIB1 is broadcasting (or OD-SIB1 is on).

[0119] In some implementations, if a UE supports at least one of NTN, ATG, RedCap, 2Rx XR, cell DTX, and cell DRX, and also supports the OD-SIB1, when the UE detects that a k_SSB is set to Range 1, the UE may determine that the cell is not an OD-SIB1 cell. The UE may find a CORESET#0 (or a CORESET for a Type0-PDCCH CSS) and a Search space #0 (or a Type0-PDCCH CSS set) according to the ssb-SubcarrierOffset IE, a PBCH payload, and / or the pdcch-ConfigSIB1 IE. After the UE finds the CORESET#0 and the Search space #0, the UE may find a SIB1 according to the CORESET#0 and the Search space #0. If the SIB1 includes a cellBarred bit and the value is set to “not barred,” the UE may determine that the cell is an OD-SIB1 cell. If the SIB1 includes a cellBarred bit and the value is set to “barred,” the UE may determine that the cell is barred.

[0120] In some implementations, if a UE supports at least one of NTN, ATG, RedCap, 2Rx XR, cell DTX, and cell DRX, and also supports the OD-SIB1, when the UE detects that a k_SSB is set to Range 2, the UE may determine that the cell is an OD-SIB1 cell and the OD-SIB1 is not broadcasting (or OD-SIB1 is off, or OD-SIB1 is now on-demand).

[0121] In some implementations, if a UE supports at least one of NTN, ATG, RedCap, 2Rx XR, cell DTX, and cell DRX, and also supports the OD-SIB1, when the UE detects that a k_SSB is set to Range 2, the UE may determine that the cell is not an OD-SIB1 cell. The UE may find a second SSB according to the ssb-SubcarrierOffset IE, a PBCH payload, and / or the pdcch-ConfigSIB1 IE (e.g., rather than find a Cell A according to the ssb-SubcarrierOffset IE, the PBCH payload, and / or the pdcch-ConfigSIB1 IE).

[0122] Several implementations for supporting barring of the on-demand SIB1 capable UE(s) are described above. Based on these implementations, on-demand SIB(s) for network energy saving may be achieved.

[0123] In some implementations, a method performed by a UE may include one or more of the following operations: 　　　　- If the UE is an OD-SIB1 capable UE, the UE may ignore the cellBarred bit in the MIB and may apply at least one of the received ssb-SubcarrierOffset IE, PBCH payload, and pdcch-ConfigSIB1 IE. 　　　　- The UE may determine a k_SSB based on the ssb-SubcarrierOffset IE and a PBCH payload for FR1 and may determine the k_SSB based on the ssb-SubcarrierOffset IE for FR2. 　　　　- In a case the k_SSB is set to a specific value (e.g., 30 or 31), the UE may determine that the cell is barred for the OD-SIB1 capable UE. 　　　　- In a case the k_SSB is set to 0-23 in FR1 and / or 0-11 in FR2, the UE may determine that the SIB1 of the cell is on-demand and the SIB1 is currently broadcasting, and the UE may receive the SIB1 according to at least one of the received ssb-SubcarrierOffset IE and pdcch-ConfigSIB1 IE. 　　　　- In a case the k_SSB is set to 24-29 in FR1 and / or 12-13 in FR2, the UE may determine that the SIB1 of the cell is on-demand and the SIB1 is currently not broadcasting, and the UE may find a Cell A according to at least one of the received ssb-SubcarrierOffset IE, PBCH payload, and pdcch-ConfigSIB1 IE.

[0124] In some implementations, a method performed by a UE may include one or more of the following operations: 　　　　- If the UE is an OD-SIB1 capable UE, the UE may ignore the cellBarred bit in the MIB and may apply at least one of the received ssb-SubcarrierOffset IE, PBCH payload, and pdcch-ConfigSIB1 IE. 　　　　- The UE may determine a k_SSB based on the ssb-SubcarrierOffset IE and a PBCH payload for FR1 and may determine the k_SSB based on the ssb-SubcarrierOffset IE for FR2. 　　　　- In a case the k_SSB is set to 0-23 in FR1 and / or 0-11 in FR2, the UE may determine that the SIB1 of the cell is on-demand and the SIB1 is currently broadcasting, and the UE may receive the SIB1 according to at least one of the received ssb-SubcarrierOffset IE and pdcch-ConfigSIB1 IE. 　　　　- If the SIB1 includes a cellBarred-ODSIB1 IE and the value of the cellBarred-ODSIB1 IE is set to “barred,” the UE may determine that the cell is barred for the OD-SIB1 capable UE. 　　　　- In a case the k_SSB is set to 24-29 in FR1 and / or 12-13 in FR2, the UE may determine that the SIB1 of the cell is on-demand and the SIB1 is currently not broadcasting, and the UE may find a Cell A according to at least one of the received ssb-SubcarrierOffset IE, PBCH payload, and pdcch-ConfigSIB1 IE.

[0125] FIG. 1 is a flowchart illustrating a method / process 100 performed by a UE for supporting OD-SIB1, according to an example implementation of the present disclosure.

[0126] In the action 102, the process 100 may start by receiving, from a first cell, a master information block (MIB) that includes a cellBarred indication. The cellBarred indication may be, for example, one cellBarred bit.

[0127] In some implementations, a base station (BS) associated with the first cell may generate the MIB for the first cell and configure an SSB to indicate a k_SSB (e.g., a subcarrier offset) through a PBCH. The PBCH may include the MIB and a PBCH payload, in which the MIB may include an ssb-SubcarrierOffset field (e.g., IE) and a pdcch-ConfigSIB1 field (e.g., IE). In the present disclosure, the PBCH payload may refer to a portion of the PBCH distinct from the MIB. For example, the PBCH payload may include additional bit(s) beyond the MIB in the PBCH. In some implementations, the UE may receive, from the first cell, the SSB broadcast from the BS and thus receiving the MIB via the PBCH included in the SSB.

[0128] In some implementations, the BS may configure the SSB such that the k_SSB is indicated by the ssb-SubcarrierOffset field and the PBCH payload when the BS is operating in FR1, and that the k_SSB is indicated by the ssb-SubcarrierOffset field when the BS is operating in FR2.

[0129] In some implementations, the first cell may be a network energy saving (NES) cell that supports OD-SIB1.

[0130] In the action 104, the process 100 may ignore the cellBarred indication and determine the k_SSB. For example, the UE may be an OD-SIB1 capable UE.

[0131] In some implementations, in a case that the UE is operating in FR1, the UE may determine the k_SSB based on the ssb-SubcarrierOffset field included in the MIB and the PBCH payload; in a case that the UE is operating in FR2, the UE may determine the k_SSB based on the ssb-SubcarrierOffset field included in the MIB.

[0132] In some implementations, the UE may apply the ssb-SubcarrierOffset field, the PBCH payload associated with the PBCH, and the pdcch-ConfigSIB1 field upon receiving the SSB from the first cell.

[0133] In the action 106, the process 100 may determine whether the k_SSB falls within a first range. In some implementations, the first range may indicate a range larger than or equal to 30 for FR1, and / or a range larger than or equal to 14 for FR2.

[0134] In action 108, in response to determining that the k_SSB falls within the first range, the process 100 may determine that the first cell is barred, and the process 100 may then end. In action 110, in response to determining that the k_SSB does not fall within the first range, the process 100 may determine that the first cell is not barred.

[0135] In some implementations, the first range may include 30 and 31 for FR1, and the UE operating in FR1 may determine that the first cell is barred for the UE when the k_SSB is determined to be 30 or 31.

[0136] In some implementations, the first range may include 14 and 15 for FR2, and the UE operating in FR2 may determine that the first cell is barred for the UE when the k_SSB is determined to be 14 or 15.

[0137] In some implementations, in a case that the UE determines that the first cell is barred, the UE may perform a cell (re)selection procedure to another cell (e.g., a second cell). The another cell may be, for example, a Cell A that periodically provides SIB1 broadcasting.

[0138] In some implementations, in a case that the UE determines that the first cell is not barred, the process 100 may proceed to process 200, as shown in FIG. 2.

[0139] FIG. 2 is a flowchart illustrating a method / process 200 performed by a UE for supporting OD-SIB1, according to an example implementation of the present disclosure.

[0140] In action 202, the process 200 may determine whether the k_SSB falls within a second range or a third range. In some implementations, the second range may indicate a range from 0 to 23 for FR1, and / or a range from 0 to 11 for FR2. In some implementations, the third range may indicate a range from 24 to 29 for FR1, and / or a range from 12 to 13 for FR2.

[0141] In action 204, in response to determining that the k_SSB falls within the second range, the process 200 may determine that a SIB1 of the first cell is on-demand and that the SIB1 is currently broadcast by the first cell. In action 206, in response to determining that the SIB1 is currently broadcast by the first cell, the process 200 may receive the SIB1 based on at least one of the ssb-SubcarrierOffset field and the pdcch-ConfigSIB1 field.

[0142] In some implementations, the second range may be from 0 to 23 for FR1, and the UE operating in FR1 may determine that the SIB1 of the first cell is on-demand and that the SIB1 is currently broadcast by the first cell when the k_SSB falls within the second range. Then, the UE may receive the SIB1 based on at least one of the ssb-SubcarrierOffset field and the pdcch-ConfigSIB1 field included in the MIB.

[0143] In some implementations, the second range may be from 0 to 11 for FR2, and the UE operating in FR2 may determine that the SIB1 of the first cell is on-demand and that the SIB1 is currently broadcast by the first cell when the k_SSB falls within the second range. Then, the UE may receive the SIB1 based on at least one of the ssb-SubcarrierOffset field and the pdcch-ConfigSIB1 field included in the MIB.

[0144] In action 208, in response to determining that the k_SSB falls within the third range, the process 200 may determine that a SIB1 of the first cell is on-demand and that the SIB1 is not currently broadcast by the first cell. In action 210, in response to determining that the SIB1 is not currently broadcast by the first cell, the process 200 may monitor an SSB for another cell (e.g., a second cell) based on at least one of an ssb-SubcarrierOffset field, a PBCH payload, and a pdcch-ConfigSIB1 field.

[0145] In some implementations, the third range may be from 24 to 29 for FR1, and the UE operating in FR1 may determine that the SIB1 of the first cell is on-demand and that the SIB1 is not currently broadcast by the first cell when the k_SSB falls within the third range. Then, the UE may monitor an SSB for another cell based on at least one of an ssb-SubcarrierOffset field, a PBCH payload, and a pdcch-ConfigSIB1 field.

[0146] In some implementations, the second range may be from 12 to 13 for FR2, and the UE operating in FR2 may determine that the SIB1 of the first cell is on-demand and that the SIB1 is not currently broadcast by the first cell when the k_SSB falls within the third range. Then, the UE may monitor an SSB for another cell based on at least one of an ssb-SubcarrierOffset field, a PBCH payload, and a pdcch-ConfigSIB1 field.

[0147] In some implementations, the ssb-SubcarrierOffset field, the PBCH payload, and the pdcch-ConfigSIB1 field may be received from the first cell. In some implementations, the ssb-SubcarrierOffset field, the PBCH payload, and the pdcch-ConfigSIB1 field may be received from the second cell.

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

[0149] 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 and 2.

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

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

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

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

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

[0155] 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 and 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.

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

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

[0158] 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 supporting on-demand system information block 1 (OD-SIB1) in a wireless communication system, 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, a master information block (MIB), the MIB comprising a cellBarred indication; 　　　　　　　　ignore the cellBarred indication; 　　　　　　　　determine a k_SSB; 　　　　　　　　determine whether the k_SSB falls within a first range; and 　　　　　　　　in response to determining that the k_SSB falls within the first range, determine that the first cell is barred, wherein: 　　　　　　　　　　　　in a case that the UE is operating in the FR1, the k_SSB is determined based on an ssb-SubcarrierOffset field and a physical broadcast channel (PBCH) payload, and the first range comprises 30 and 31,and 　　　　　　　　　　　　in a case that the UE is operating in FR2, the k_SSB is determined based on the ssb-SubcarrierOffset field, and the first range comprises 14 and 15.

2. The UE of claim 1, wherein in response to determining that the k_SSB falls within the first range, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　perform a cell (re)selection procedure to a second cell.

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 whether the k_SSB falls within a second range, the second range ranging from 0 to 23 in a case that the UE is operating in FR1, and from 0 to 11 in a case that the UE is operating in FR2; 　　　　in response to determining that the k_SSB falls within the second range, determine that a system information block 1 (SIB1) of the first cell is on-demand and that the SIB1 is currently broadcast by the first cell; and 　　　　in response to determining that the SIB1 is currently broadcast by the first cell, receive the SIB1 based on at least one of the ssb-SubcarrierOffset field and a pdcch-ConfigSIB1 field.

4. The UE of claim 3, wherein the MIB is received via a physical broadcast channel (PBCH) and comprises the ssb-SubcarrierOffset field and the pdcch-ConfigSIB1 field, the one or more computer-executable instructions, when executed by the at least one processor, further cause the UE to: 　　　　apply the ssb-SubcarrierOffset field, the PBCH payload associated with the PBCH, and the pdcch-ConfigSIB1 field.

5. 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 whether the k_SSB falls within a third range, the third range ranging from 24 to 29 in a case that the UE is operating in FR1, and from 12 to 13 in a case that the UE is operating in FR2; 　　　　in response to determining that the k_SSB falls within the third range, determine that a system information block 1 (SIB1) of the first cell is on-demand and that the SIB1 is not currently broadcast by the first cell; and 　　　　in response to determining that the SIB1 is not currently broadcast by the first cell, monitor an SSB for a second cell based on at least one of the ssb-SubcarrierOffset field, the PBCH payload, and a pdcch-ConfigSIB1 field.

6. The UE of claim 5, wherein the second cell periodically provides SIB1 broadcasting.

7. The UE of claim 1, wherein the first cell is a network energy saving (NES) cell.

8. A Base Station (BS) for supporting on-demand system information block 1 (OD-SIB1) in a wireless communication system, 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: 　　　　　　　　generate a master information block (MIB) for a first cell, the MIB comprising a cellBarred indication; and 　　　　　　　　broadcast the MIB, 　　　　wherein the MIB is configured to cause the UE to: 　　　　　　　　ignore the cellBarred indication; 　　　　　　　　determine a k_SSB; 　　　　　　　　determine whether the k_SSB falls within a first range; and 　　　　　　　　in response to determining that the k_SSB falls within the first range, determine that the first cell is barred, wherein: 　　　　　　　　　　　　in a case that the UE is operating in the FR1, the k_SSB is determined based on an ssb-SubcarrierOffset field and a physical broadcast channel (PBCH) payload, and the first range comprises 30 and 31,and 　　　　　　　　　　　　in a case that the UE is operating in FR2, the k_SSB is determined based on the ssb-SubcarrierOffset field, and the first range comprises 14 and 15.

9. The BS of claim 8, wherein the MIB is configured to further cause the UE to: 　　　　in response to determining that the k_SSB falls within the first range, perform a cell (re)selection procedure to a second cell.

10. The BS of claim 8, wherein the MIB is configured to further cause the UE to: 　　　　determine whether the k_SSB falls within a second range, the second range ranging from 0 to 23 in a case that the UE is operating in FR1, and from 0 to 11 in a case that the UE is operating in FR2; 　　　　in response to determining that the k_SSB falls within the second range, determine that a system information block 1 (SIB1) of the first cell is on-demand and that the SIB1 is currently broadcast by the first cell; and 　　　　in response to determining that the SIB1 is currently broadcast by the first cell, receive the SIB1 based on at least one of the ssb-SubcarrierOffset field and a pdcch-ConfigSIB1 field.

11. The BS of claim 10, wherein the MIB is received via a physical broadcast channel (PBCH) and comprises the ssb-SubcarrierOffset field and the pdcch-ConfigSIB1 field, and the MIB is configured to further cause the UE to: 　　　　apply the ssb-SubcarrierOffset field, the PBCH payload associated with the PBCH, and the pdcch-ConfigSIB1 field.

12. The BS of claim 8, wherein the MIB is configured to further cause the UE to: 　　　　determine whether the k_SSB falls within a third range, the third range ranging from 24 to 29 in a case that the UE is operating in FR1, and from 12 to 13 in a case that the UE is operating in FR2; 　　　　in response to determining that the k_SSB falls within the third range, determine that a system information block 1 (SIB1) of the first cell is on-demand and that the SIB1 is not currently broadcast by the first cell; and 　　　　in response to determining that the SIB1 is not currently broadcast by the first cell, monitor an SSB for a second cell based on at least one of the ssb-SubcarrierOffset field, the PBCH payload, and a pdcch-ConfigSIB1 field.

13. The BS of claim 12, wherein the second cell periodically provides SIB1 broadcasting.

14. The BS of claim 8, wherein the first cell is a network energy saving (NES) cell.

15. A method performed by a User Equipment (UE) for supporting on-demand system information block 1 (OD-SIB1), the method comprising: 　　　　receiving, from a first cell, a master information block (MIB), the MIB comprising a cellBarred indication; 　　　　ignoring the cellBarred indication; 　　　　determining a k_SSB; 　　　　determining whether the k_SSB falls within a first range; and 　　　　in response to determining that the k_SSB falls within the first range, determining that the first cell is barred, wherein: 　　　　in a case that the UE is operating in the FR1, the k_SSB is determined based on an ssb-SubcarrierOffset field and a physical broadcast channel (PBCH) payload, and the first range comprises 30 and 31,and 　　　　in a case that the UE is operating in FR2, the k_SSB is determined based on the ssb-SubcarrierOffset field, and the first range comprises 14 and 15.

Images