Patent Description:
Wireless communication standards may define common search space configurations of the unified air interface. As part of configuring a common search space, the base station may schedule resources of a bandwidth part (BWP) of the unified air interface to follow a wireless communication standard. Knowing the common search space configuration, as a result of the wireless communication standard, the UE can acquire SIBs that enable the UE to communicate successfully with the base station.

Today, wireless communication standards define common search space configuration techniques for a UE to acquire a system information block type <NUM> (SIB1) or a master information block (MIB). However, common search space configuration techniques for acquiring a SIB that is other than the SIB1 and the MIB (e.g., another system information block, or OSIB) are currently undefined.

<NPL>) generally refers to notifying an RRC_CONNECTED state UE with a configured active downlink bandwidth part that system information (SI) will be updated (or that ETWS/CMAS information has been activated). This reference also discusses facilitating retrieval of the updated SI or ETWS/CMAS information by the UE.

<NPL>) generally relates to handling of paging for SI Change/ETWS/CMAS etc. when the UE is in a connected mode configured with multiple bandwidth parts.

In accordance with an aspect of the present invention, there is provided: a communication method performed by a user equipment, as defined in claim <NUM>; and a user equipment, as defined in claim <NUM>. This summary is provided to introduce subject matter that is further described in the Detailed Description and Drawings. Accordingly, this Summary should not be considered to describe essential features nor used to limit the scope of the claimed subject matter.

In some aspects described herein but not explicitly claimed, a method is described. The method is performed by a base station wirelessly communicating with a UE that is in an engaged mode. The method includes determining to configure a common search space through which the UE can receive an OSIB. As part of the method, the base station transmits a first message that includes a set of common search space configuration parameters for the UE to receive the OSIB. The method also includes the base station transmitting, in accordance with the common search space parameters, a second message that includes the OSIB and the base station transmitting additional messages in accordance with system information parameters contained in the OSIB.

In other aspects, a method is described. The method is performed by a UE wirelessly communicating with a base station according to a 3GPP communication protocol or standard, the user equipment being in an engaged mode. The method includes the UE receiving a first message that includes a set of common search space configuration parameters for the UE to receive an OSIB and further includes an additional set of common search space configuration parameters for the user equipment to receive an SIB1. As part of the method, the UE configures a transceiver of the UE to monitor a common search space for the OSIB in accordance with the set of common search space configuration parameters. The method also includes the UE receiving a second message that includes the OSIB and the UE receiving additional messages in accordance with system information parameters acquired from OSIB.

In yet other aspects described herein but not explicitly claimed, a base station is described. The base station includes a wireless transceiver, a processor, and a computer-readable storage medium having a search space configuration manager application. When executed by the processor, the search space configuration manager application directs the base station to perform operations that include (i) determining to configure a common search space for a UE to receive an OSIB (ii) transmitting, over an active bandwidth part (BWP), a first message that includes a set of common search space configuration parameters for the UE to receive the OSIB, (iii) transmitting a second message that includes the OSIB, and (iv) wirelessly communicating with the UE in accordance with system information parameters contained in the OSIB.

The details of one or more implementations of common search space configuration and system information acquisition are set forth in the accompanying drawings and the following description. This summary is provided to introduce subject matter that is further described in the Detailed Description and Drawings. Accordingly, a reader should not consider the summary to describe essential features nor limit the scope of the claimed subject matter.

This document describes details of one or more aspects of common search space configuration and system information acquisition. The use of the same reference numbers in other instances in the description and the figures may indicate like elements:.

This document describes methods and systems for common search space configuration and system information acquisition. As part of the methods and systems, a base station wirelessly communicating with a UE that is in an engaged state determines to configure a common search space through which the UE can receive an OSIB. The base station transmits a first message that includes a set of common search space configuration parameters for the UE to receive the OSIB and further includes an additional set of common search space configuration parameters for the user equipment to receive an SIB1. The base station then transmits, in accordance with the set of common search space configuration parameters, a second message that includes the OSIB.

The base station includes an executable search space manager application and the UE includes an executable system information block (SIB) manager application. When executed, the respective applications direct the base station and the UE to perform complementary operations as described herein.

<FIG> illustrates an example environment <NUM>, which includes multiple UE <NUM> (UE <NUM>), illustrated as UE <NUM>, UE <NUM>, and UE <NUM>. Each UE <NUM> can communicate with base stations <NUM> (illustrated as base stations <NUM>, <NUM>, <NUM>, and <NUM>) through one or more wireless communication links <NUM> (wireless link <NUM>), illustrated as wireless links <NUM> and <NUM>. For simplicity, the UE <NUM> is implemented as a smartphone but may be implemented as any suitable computing or electronic device, such as a mobile communication device, modem, cellular phone, gaming device, navigation device, media device, laptop computer, desktop computer, tablet computer, smart appliance, vehicle-based communication system, or an Internet-of-Things (IoT) device such as a sensor or an actuator. The base stations <NUM> (e.g., an Evolved Universal Terrestrial Radio Access Network Node B, E-UTRAN Node B, evolved Node B, eNodeB, eNB, Next Generation Node B, gNode B, gNB, ng-eNB, or the like) may be implemented in a macrocell, microcell, small cell, picocell, or the like, or any combination thereof.

The base stations <NUM> communicate with the UE <NUM> using the wireless links <NUM> and <NUM>, which may be implemented as any suitable type of wireless link. The wireless links <NUM> and <NUM> include control and data communication, such as downlink of data and control information communicated from the base stations <NUM> to the UE <NUM>, uplink of other data and control information communicated from the UE <NUM> to the base stations <NUM>, or both. The wireless links <NUM> may include one or more wireless links (e.g., radio links) or bearers implemented using any suitable communication protocol or standard, or combination of communication protocols or standards, such as 3rd Generation Partnership Project Long-Term Evolution (3GPP LTE), Fifth Generation New Radio (<NUM> NR), and so forth. Multiple wireless links <NUM> may be aggregated in a carrier aggregation to provide a higher data rate for the UE <NUM>. Multiple wireless links <NUM> from multiple base stations <NUM> may be configured for Coordinated Multipoint (CoMP) communication with the UE <NUM>.

The base stations <NUM> are collectively a Radio Access Network <NUM> (e.g., RAN, Evolved Universal Terrestrial Radio Access Network, E-UTRAN, <NUM> NR RAN or NR RAN). The RANs <NUM> are illustrated as an NR RAN <NUM> and an E-UTRAN <NUM>. The base stations <NUM> and <NUM> in the NR RAN <NUM> are connected to a Fifth Generation Core <NUM> (5GC <NUM>) network. The base stations <NUM> and <NUM> in the E-UTRAN <NUM> are connected to an Evolved Packet Core <NUM> (EPC <NUM>). Optionally or additionally, the base station <NUM> may connect to both the 5GC <NUM> and EPC <NUM> networks.

The base stations <NUM> and <NUM> connect, at <NUM> and <NUM> respectively, to the 5GC <NUM> through an NG2 interface for control-plane signaling and using an NG3 interface for user-plane data communications. The base stations <NUM> and <NUM> connect, at <NUM> and <NUM> respectively, to the EPC <NUM> using an S1 interface for control-plane signaling and user-plane data communications. Optionally or additionally, if the base station <NUM> connects to the 5GC <NUM> and EPC <NUM> networks, the base station <NUM> connects to the 5GC <NUM> using an NG2 interface for control-plane signaling and through an NG3 interface for user-plane data communications, at <NUM>.

In addition to connections to core networks, the base stations <NUM> may communicate with each other. For example, the base stations <NUM> and <NUM> communicate through an Xn interface at <NUM>, the base stations <NUM> and <NUM> communicate through an Xn interface at <NUM>, and the base stations <NUM> and <NUM> communicate through an X2 interface at <NUM>.

The 5GC <NUM> includes an Access and Mobility Management Function <NUM> (AMF <NUM>), which provides control-plane functions, such as registration and authentication of multiple UE <NUM>, authorization, and mobility management in the <NUM> NR network. The EPC <NUM> includes a Mobility Management Entity <NUM> (MME <NUM>), which provides control-plane functions, such as registration and authentication of multiple UE <NUM>, authorization, or mobility management in the E-UTRA network. The AMF <NUM> and the MME <NUM> communicate with the base stations <NUM> in the RANs <NUM> and also communicate with multiple UE <NUM>, using the base stations <NUM>.

Furthermore, within the environment <NUM>, the UE <NUM> and the base station <NUM> may be in an engaged state with each other. While in the engaged state, the base station <NUM> may determine to configure a common search space through which the UE <NUM> can receive an OSIB (e.g., a system information block that is other than a SIB1 or a MIB).

A portion of a wireless communication protocol (e.g., a protocol as specified in 3GPP TS <NUM> section <NUM>. <NUM>) may specify techniques associated with the UE <NUM> acquiring the OSIB. The wireless communication protocol may specify an expected behavior of the UE <NUM>, such as monitoring (e.g., monitoring a common search space for a message containing the OSIB) or sequencing of system information block acquisition (e.g., acquiring the OSIB prior to acquiring a SIB1 or a MIB).

In general, different types of OSIBs may indicate different changes to system information (SI) needed for different types of wireless communication between the base station <NUM> and the UE <NUM>. As an example of different types of OSIBs indicating different changes to system information, system information relative to changing paging from a base station may be contained in an OSIB that is a system information block type <NUM> (e.g., a SIB6), a system information block type <NUM> (e.g., a SIB7), or system information block type <NUM> (e.g., a SIB8). Examples of paging include the base station <NUM> transmitting information as part of a public warning system (PWS), an earthquake and tsunami warning system (ETWS), and a commercial mobile alert system (CMAS).

<FIG> illustrates an example device diagram <NUM> of a UE (e.g., the UE <NUM> of <FIG>) and a base station (e.g., the base stations <NUM> of <FIG>). The UE <NUM> and the base station <NUM> may include additional functions and interfaces that are omitted from <FIG> for the sake of clarity. The UE <NUM> includes antennas <NUM>, a radio frequency front end <NUM> (RF front end <NUM>), an LTE transceiver <NUM>, and a <NUM> NR transceiver <NUM> for communicating with base stations <NUM>. The RF front end <NUM> of the UE <NUM> can couple or connect the LTE transceiver <NUM>, and the <NUM> NR transceiver <NUM> to the antennas <NUM> to facilitate various types of wireless communication. The antennas <NUM> of the UE <NUM> may include an array of multiple antennas that are configured similar to or differently from each other. The antennas <NUM> and the RF front end <NUM> can be tuned to, and/or be tunable to, one or more frequency bands defined by the 3GPP LTE and <NUM> NR communication standards and implemented by the LTE transceiver <NUM>, and/or the <NUM> NR transceiver <NUM>. Additionally, the antennas <NUM>, the RF front end <NUM>, the LTE transceiver <NUM>, and/or the <NUM> NR transceiver <NUM> may be configured to support beamforming for the transmission and reception of communications with the base stations <NUM>. By way of example and not limitation, the antennas <NUM> and the RF front end <NUM> can be implemented for operation in sub-gigahertz bands, sub-<NUM> bands, and/or above <NUM> bands that are defined by the 3GPP LTE and <NUM> NR communication standards.

The UE <NUM> also includes processor(s) <NUM> and computer-readable storage media <NUM> (CRM <NUM>). The processor <NUM> may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. The computer-readable storage media described herein excludes propagating signals. CRM <NUM> may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory.

CRM <NUM> also includes an executable application (e.g., SIB manager <NUM>) for directing the UE <NUM> to perform operations relative to receiving an OSIB. In at least some aspects, the SIB manager <NUM>, when executed by the processor <NUM>, may direct the UE <NUM> to perform operations that include receiving a set of configuration parameters for a common search space, configuring the UE to monitor the common search space for the OSIB in accordance with the set of configuration parameters, receiving the OSIB, and wirelessly communicating with the base station in accordance with system information parameters contained in the OSIB. Furthermore, and in some instances, the SIB manager <NUM> may direct the UE <NUM> to perform operations relative to receiving a SIB1 or a MIB.

The device diagram for the base station <NUM>, shown in <FIG>, includes a single network node (e.g., a gNode B). The functionality of the base station <NUM> may be distributed across multiple network nodes or devices and may be distributed in any fashion suitable to perform the functions described herein. The base stations <NUM> include antennas <NUM>, a radio frequency front end <NUM> (RF front end <NUM>), one or more LTE transceivers <NUM>, and/or one or more <NUM> NR transceivers <NUM> for communicating with the UE <NUM>. The RF front end <NUM> of the base stations <NUM> can couple or connect the LTE transceivers <NUM> and the <NUM> NR transceivers <NUM> to the antennas <NUM> to facilitate various types of wireless communication. The antennas <NUM> of the base stations <NUM> may include an array of multiple antennas that are configured similar to or differently from each other. The antennas <NUM> and the RF front end <NUM> can be tuned to, and/or be tunable to, one or more frequency bands defined by the 3GPP LTE and <NUM> NR communication standards, and implemented by the LTE transceivers <NUM>, and/or the <NUM> NR transceivers <NUM>. Additionally, the antennas <NUM>, the RF front end <NUM>, the LTE transceivers <NUM>, and/or the <NUM> NR transceivers <NUM> may be configured to support beamforming, such as Massive-MIMO, for the transmission and reception of communications with the UE <NUM>.

The base station <NUM> also includes processor(s) <NUM> and computer-readable storage media <NUM> (CRM <NUM>). The processor <NUM> may be a single core processor or a multiple core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. CRM <NUM> may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory.

The CRM <NUM> also includes a base station manager <NUM>. Alternately or additionally, the base station manager <NUM> may be implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the base station <NUM>.

The base station manager <NUM> includes an executable application (e.g., search space manager <NUM>) for configuring a common search space and transmitting an OSIB. In at least some aspects the search space manager <NUM>, when executed by the processor <NUM>, directs the base station <NUM> to perform operations that include determining to configure a common search space through which the UE <NUM> can receive a system information block (e.g., an OSIB), transmitting a message to the UE <NUM> that includes a set of configuration parameters for the common search space, transmitting the OSIB to the UE in accordance with the set of configuration parameters for the common search space, and wirelessly communicating with the UE in accordance with system information parameters contained in the OSIB.

<FIG> illustrates an example unified air interface <NUM> in accordance with aspects of techniques described herein. <FIG> illustrates an example interface <NUM> that extends between a UE (e.g., the UE <NUM>) and a base station (e.g., the base station <NUM>). The example interface <NUM> includes unified air interface resources <NUM> that can be divided into resource units <NUM>, each of which occupies some intersection of a frequency spectrum and elapsed time. A portion of the unified air interface resources <NUM> is illustrated graphically in a grid or matrix having multiple resource blocks <NUM>, including example resource blocks <NUM>, <NUM>, <NUM>, <NUM>. An example of a resource unit <NUM>, therefore, includes at least one resource block <NUM>. As shown, time is depicted along the horizontal dimension as the abscissa axis, and frequency is depicted along the vertical dimension as the ordinate axis. The unified air interface resources <NUM>, as defined by a given communication protocol or standard, may span any suitable specified frequency range, and/or may be divided into intervals of any specified duration. Increments of time can correspond to, for example, milliseconds (mSec). Increments of frequency can correspond to, for example, megahertz (MHz).

In example operations generally, the base station <NUM> schedules and allocates portions (e.g., resource units <NUM>) of the unified air interface resources <NUM> for uplink and downlink communications. Each resource block <NUM> of network access resources may be allocated to support a wireless link <NUM> of the UE <NUM>. In the lower-left corner of the grid, the resource block <NUM> may span, as defined by a given communication protocol, a specified frequency range <NUM> and comprise multiple subcarriers or frequency sub-bands. The resource block <NUM> may include any suitable number of subcarriers (e.g., <NUM>) that each correspond to a respective portion (e.g., <NUM>) of the specified frequency range <NUM> (e.g., <NUM>). The resource block <NUM> may also span, as defined by the given communication protocol, a specified time interval <NUM> or time slot (e.g., lasting approximately one-half millisecond or <NUM> orthogonal frequency-division multiplexing (OFDM) symbols). The time interval <NUM> includes subintervals that may each correspond to a symbol, such as an OFDM symbol. As shown in <FIG>, each resource block <NUM> may include multiple resource elements <NUM> (REs) that correspond to, or are defined by, a subcarrier of the frequency range <NUM> and a subinterval (or symbol) of the time interval <NUM>. Alternatively, a given resource element <NUM> may span more than one frequency subcarrier or symbol. Thus, a resource unit <NUM> may include at least one resource block <NUM>, at least one resource element <NUM>, and so forth.

As part of wireless communications between the UE <NUM> and the base station <NUM>, configuring a common search space may include the base station scheduling resources of the unified air interface resources <NUM> (e.g., the processor <NUM> executing code of the base station manager <NUM> including the search space manager <NUM>). The base station <NUM> schedules resources of the unified air interface resources <NUM> in an active bandwidth part (e.g., BWP <NUM>) being used as the UE <NUM> and the base station <NUM> wirelessly communicate while the UE is in an engaged state.

These resources (e.g., the BWP <NUM>) may be used for wirelessly communicating messages that enable search space configuration and OSIB acquisition. Messages transmitted using the BWP <NUM> may also include the OSIB. Transmission and reception of the message that includes the OSIB may in some instances use dedicated signaling (e.g., radio resource control signaling) and a message (e.g., an RRCReconfiguration message) associated with a wireless communication protocol.

<FIG> illustrates example user equipment states <NUM> between a UE (e.g., the UE <NUM>) and a base station (e.g., the base station <NUM>). Generally, a wireless network operator provides telecommunication services to user equipment through a wireless network. To communicate wirelessly with the network, a UE <NUM> utilizes a radio resource control (RRC) procedure to establish a connection to the network via a cell (e.g., the base station, a serving cell). Upon establishing the connection to the network through the base stations <NUM>, the UE <NUM> enters a connected mode (e.g., RRC-connected mode, RRC_CONNECTED state, NR-RRC CONNECTED state, or E-UTRA RRC CONNECTED state).

The UE <NUM> operates according to different resource control states <NUM>. Different situations may occur that cause the UE <NUM> to transition between different resource control states <NUM> as determined by the radio access technology. Example resource control states <NUM> illustrated in <FIG> include a connected mode <NUM>, an idle mode <NUM>, and an inactive mode <NUM>. A UE <NUM> is either in the connected mode <NUM> or in the inactive mode <NUM> when an RRC connection is active. If an RRC connection is not active, then the UE <NUM> is in the idle mode <NUM>.

In establishing the RRC connection, the UE <NUM> may transition from the idle mode <NUM> to the connected mode <NUM>. After establishing the connection, the UE <NUM> may transition (e.g., upon connection inactivation) from the connected mode <NUM> to an inactive mode <NUM> (e.g., RRC-inactive mode, RRC_INACTIVE state, NR-RRC INACTIVE state) and the UE <NUM> may transition (e.g., via an RRC connection resume procedure) from the inactive mode <NUM> to the connected mode <NUM>. After establishing the connection, the UE <NUM> may transition between the connected mode <NUM> to an idle mode <NUM> (e.g., RRC-idle mode, RRC_IDLE state, NR-RRC IDLE state, E-UTRA RRC IDLE state), for instance upon the network releasing the RRC connection. Further, the UE <NUM> may transition between the inactive mode <NUM> and the idle mode <NUM>.

The UE <NUM> may be in an engaged mode <NUM> or may be in a disengaged mode <NUM>. As used herein, an engaged mode <NUM> is a connected mode (e.g., connected mode <NUM>) and a disengaged mode <NUM> is an idle, disconnected, connected-but-inactive, or connected-but-dormant mode (e.g., idle mode <NUM>, inactive mode <NUM>). In some cases, in the disengaged mode <NUM>, the UE <NUM> may still be registered at a Non-Access Stratum (NAS) layer with an active radio bearer (e.g., in inactive mode <NUM>).

Each of the different resource control states <NUM> may have different quantities or types of resources available, which may affect power consumption within the UE <NUM>. In general, the connected mode <NUM> represents the UE <NUM> actively connected to (engaged with) the base stations <NUM>. In the inactive mode <NUM>, the UE <NUM> suspends connectivity with the base station <NUM> and retains information that enables connectivity with the base station <NUM> to be quickly re-established. In the idle mode <NUM>, the UE <NUM> releases the connection with the base stations <NUM>.

Some of the resource control states <NUM> may be limited to certain radio access technologies. For example, the inactive mode <NUM> may be supported in LTE Release <NUM> (eLTE) and <NUM> NR, but not in <NUM> or previous generations of <NUM> standards. Other resource control states may be common or compatible across multiple radio access technologies, such as the connected mode <NUM> or the idle mode <NUM>.

In the context of the present application, if the UE <NUM> is in an engaged mode corresponding to the connected mode <NUM> (e.g., the RRC_Connected state), a BWP of an air interface may actively support wireless communications between the UE <NUM> and the base station <NUM> (e.g., radio resource control wireless communications). Such a BWP may be the BWP <NUM> of <FIG>.

<FIG> illustrates an example method <NUM> performed by a base station in accordance with aspects of techniques described herein. The method, illustrated by a series of operational blocks <NUM>-<NUM>, may be performed by one or more elements of the base station <NUM> of <FIG> as directed by the processor <NUM> executing the search space manager <NUM>. The method may also include elements of <FIG>. Sequencing of the operational blocks <NUM>-<NUM>, including underlying or detailed elements of the operational blocks <NUM>-<NUM>, is not limited by the illustration of <FIG> or by the description of <FIG> hereafter. The operational blocks <NUM>-<NUM>, or portions of the operational blocks <NUM>-<NUM>, may also be performed by entities other than the base station <NUM> (e.g., the 5GCN <NUM>). The method may occur while the UE <NUM> of <FIG> is in an engaged state with the base station <NUM>.

At block <NUM> the base station <NUM> determines to configure a common search space for the UE <NUM> to receive an OSIB (e.g., a SIB other than a SIB1 or a MIB). The UE <NUM> may be in an engaged mode that corresponds to engaged mode <NUM> (e.g., an RCC_CONNECTED state).

At block <NUM> the base station <NUM> transmits, to the UE <NUM>, a first message that includes a set of common search space configuration parameters for the UE <NUM> to receive the OSIB. The set of common search space configuration parameters may identify resources of an active BWP (e.g., the BWP <NUM> of the unified air interface <NUM>) through which the UE <NUM> may receive the OSIB. In some instances, the base station <NUM> (e.g., the search space manager <NUM>) may determine the set of common search space configuration parameters, while in other instances the base station <NUM> may receive the set of common search space configuration parameters from a core network (e.g., the 5GCN <NUM>). The base station <NUM> may also receive, from the core network, another set of common search space configuration parameters for a SIB1.

In some instances, transmitting the first message that includes the set of common search space configuration parameters may use dedicated signaling (e.g., radio resource control signaling) to transmit a dedicated message (e.g., an RRCReconfiguration message). Furthermore, the first message includes an additional set of common search space configuration parameters for a SIB1.

At block <NUM>, the base station <NUM> transmits, to the UE <NUM> and through the common search space in accordance with the first set of common search space configuration parameters, a second message that includes the OSIB. In some instances, the OSIB may contain system information parameters that correspond to a paging operation of the base station <NUM> (e.g., PWS, ETWS, or CMAS). In such an instance, the OSIB may be a SIB6, SIB7, or SIB8.

At block <NUM>, the base station <NUM> transmits, to the UE <NUM>, additional messages in accordance with system information parameters contained in the OSIB. In an instance where the OSIB contains parameters that correspond to a paging operation, transmitting the additional messages may include transmitting a PWS message, an ETWS message, or a CMAS message.

Although method <NUM> describes examples of the OSIB containing system information parameters that enable the base station <NUM> to transmit messages to the UE <NUM> (e.g., block <NUM>), other permutations are possible. For instance, different OSIBs may contain different system information parameters that enable the UE to transmit messages to the base station <NUM> (and the base station <NUM> may receive additional messages in accordance with the different system information parameters).

<FIG> illustrates an example method <NUM> performed by a user equipment accordance with aspects of techniques described herein. The method, illustrated by a series of operational blocks <NUM>-<NUM>, may be performed by one or more elements of the UE <NUM> of <FIG> as directed by the processor <NUM> executing the SIB manager <NUM>. The method may also include elements of <FIG>. Sequencing of the operational blocks <NUM>-<NUM>, including underlying or detailed elements of the operational blocks <NUM>-<NUM>, is not limited by the illustration of <FIG> or by the description of <FIG> hereafter. The operational blocks <NUM>-<NUM>, or operations of the operational blocks <NUM>-<NUM>, may also be performed by entities other than the UE <NUM>. The method may be performed by the UE <NUM> while it is in an engaged mode that corresponds to the engaged mode <NUM> (e.g., an RRC_CONNECTED state).

At block <NUM> the UE <NUM> receives a first message that includes a set of common search space configuration parameters for the UE <NUM> to receive an OSIB (e.g., a SIB that is other than a SIB1 or a MIB). The UE <NUM> may be in an engaged mode that corresponds to engaged mode <NUM> (e.g., an RCC_CONNECTED state).

In some instances, the first message may be a dedicated message that is received through dedicated signaling (e.g., an RRCReconfiguration message). Furthermore, the first message includes an additional set of common search space configuration parameters for the UE to receive a SIB1.

At block <NUM> the UE <NUM> configures its transceiver to monitor a common search space for the OSIB in accordance with the set of common search space configuration parameters.

At block <NUM> the UE <NUM> receives, from the base station, a second message that includes the OSIB. The second message is received through the common search space in accordance with the set of common search space configuration parameters. As examples, the OSIB may be a system information block type <NUM> (SIB2), a system information block type <NUM> (SIB3), a system information block type <NUM> (SIB4), or a system information block type <NUM> (SIB5).

At block <NUM> the UE transmits additional messages in accordance with system information parameters acquired from the OSIB.

Although method <NUM> describes examples of the OSIB containing system information parameters that enable the UE <NUM> to transmit additional messages to the base station <NUM> (e.g., block <NUM>), other permutations are possible. For instance, different OSIBs may contain different system information parameters that the UE <NUM> may use to receive messages from the base station <NUM>.

<FIG> illustrates details of example signaling and control transactions <NUM> of a UE and a base station in accordance with various aspects of common search space configuration and system information acquisition. The UE (e.g., the UE <NUM> of <FIG>) and the base station (e.g., the base station <NUM> of <FIG>) may wirelessly communicate and format the signaling and control transactions in accordance with data frames or subframes of wireless communication protocols. Furthermore, the example signaling and control actions may occur while the UE <NUM> is in an engaged mode. The engaged mode may correspond to the engaged mode <NUM> (e.g., an RRC_CONNECTED state) of <FIG>.

The example signaling and control transactions <NUM> are directed to common search space configuration and system information acquisition techniques using multiple SIBs (e.g., a SIB1 and an OSIB). In at least some aspects, portions of the signaling and control transactions in <FIG> (e.g., portions of the signaling and control transactions that are directed to the OSIB) correspond to signaling and control transactions that support previously described example methods <NUM> and <NUM>.

Prior to initiating signaling and control transactions, and at operation <NUM>, the base station <NUM> determines to configure a common search space for the UE <NUM> to receive an OSIB. At operation <NUM>, the base station <NUM> determines to configure the common search space for the UE <NUM> to receive the SIB1.

At operation <NUM>, the base station <NUM> sends a first message to the UE <NUM>. The first message includes a first set of common search space configuration parameters for the UE <NUM> to receive the SIB1.

At operation <NUM> the base station <NUM> transmits a second message to the UE <NUM>. The second message includes a second set of common search space configuration parameters for the UE <NUM> to receive the OSIB. In some instances, the second message may be transmitted using an active BWP (e.g., the BWP <NUM>) and the second message may be a message that corresponds with a wireless communication protocol (e.g., an RRCReconfiguration message).

After receiving the first and second messages, and at operation <NUM>, the UE <NUM> the configures its transceiver to monitor a common search space for the OSIB in accordance with the second set of common search space configuration parameters (e.g., the second set of common search space configuration parameters included in the second message at operation <NUM>).

At operation <NUM>, the UE <NUM> receives, from base station <NUM>, a third message that includes the OSIB. At operation <NUM>, and after receiving the third message that includes the OSIB, the UE <NUM> configures its transceiver to monitor the common search space for the SIB1 in accordance with the first set of common search space configuration parameters. At operation <NUM>, the UE <NUM> receives a fourth message that includes the SIB1.

At operation <NUM>, the UE <NUM> and the base station <NUM> wirelessly communicate additional messages in accordance with system information parameters contained in the OSIB and the SIB1.

Note that, as illustrated by the example operations <NUM>-<NUM>, the UE <NUM> prioritizes receiving the OSIB prior to receiving the SIB1. In general, sequences of transceiver configuration, monitoring the common search space for SIBs (e.g., OSIB, SIB1), and receiving SIBs may vary. The described signaling and control transactions are by way of example only and are not constrained by the sequence or order of presentation.

Claim 1:
A communication method performed by a user equipment (<NUM>) wirelessly communicating with a base station (<NUM>) according to a 3GPP communication protocol or standard, the user equipment in an engaged mode and the method comprising:
receiving (<NUM>), by the user equipment (<NUM>) and from the base station (<NUM>), a first message that includes a set of common search space configuration parameters for the user equipment to receive an other system information block, the first message further including an additional set of common search space configuration parameters for the user equipment (<NUM>) to receive a system information block type <NUM>;
configuring (<NUM>), by the user equipment (<NUM>), a wireless transceiver (<NUM>, <NUM>) of the user equipment to monitor a common search space for the other system information block in accordance with the set of common search space configuration parameters;
receiving (<NUM>), by the user equipment (<NUM>) and from the base station (<NUM>), a second message that includes the other system information block, the second message received through monitoring the common search space; and
receiving (<NUM>), by the user equipment (<NUM>) and from the base station (<NUM>), additional messages in accordance with system information parameters acquired from the other system information block.