Patent Description:
The following relates generally to wireless communication, and more specifically to system information block transmission.

Examples of such multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, and orthogonal frequency division multiple access (OFDMA) systems, (e.g., a Long Term Evolution (LTE) system). A wireless multiple-access communications system may include a number of base stations, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE).

By way of example, a wireless multiple-access communication system may include a number of base stations, each simultaneously supporting communication for multiple communication devices (e.g., UEs). A base station may communicate with UEs on downlink channels (e.g., for transmissions from a base station to a UE) and uplink channels (e.g., for transmissions from a UE to a base station).

Certain wireless systems may use short synchronization symbols, which may result in increased complexity for the device searching for the wireless system. To reduce this complexity, the synchronization and possibly broadcast signals (such as signals broadcast on a physical broadcast channel (PBCH) as used in some wireless systems) may be sent on a coarse frequency raster, which may limit the number of raster points to be searched. However, the system bandwidth may be allocated over a finer raster to enable flexible spectrum allocation in multiple frequency bands, geographical locations, and across both licensed and shared spectrum. This may imply an offset, also referred to as a raster offset, between the center of the bandwidth occupied by the synchronization information (such as primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH signals, etc.) and the system bandwidth over which the remaining data traffic, including broadcast system-information messages (such as system information blocks (SIBs)) may be transmitted. Non-zero raster offsets, together with a need for wireless systems to support UEs with different bandwidth capabilities, may support a need for improved procedures for transmitting SIB messages.

The 3GPP draft "Single beam synchronization design", R1-<NUM>, discusses various aspects of NR synchronization. It first provides an overview on synchronization and then discusses the synchronization raster design and synchronization signal design with focus on the single beam synchronization.

There still exists a need for a more efficient way if exchanging control information.

The present invention provides a solution according to the subject matter of the independent claims.

Certain wireless communication systems may be configured such that the channelization used for all downlink and uplink channels, with the exception of channels (or frequencies) used for synchronization information, is defined for a user equipment (UE) once the UE knows the system bandwidth and raster offset. The channelization may refer to the tone mapping in systems based on variants of orthogonal frequency division multiplexing (OFDM) techniques, based on scrambling sequences, based on a defined search space in which the UE knows to look to receive the downlink control channel (such as common control information), etc. Such wireless communications systems may use base stations broadcasting on a channel (such as a physical broadcast channel (PBCH)) a portion of the system information, such as system bandwidth, raster offset, etc. The UE may determine the remaining portion of the system information using multiple-hypothesis blind decoding, for example. Such broadcast signals, however, may be associated with increased overhead, for example in systems that support beamformed transmissions (e.g., which may be used to compensate for signal attenuation in a millimeter wave (mmW) wireless communication system). Such systems may use narrow beams to broadcast the signals which may require beam sweeping and/or increased coding redundancy to compensate for reduced penetration of the signals. Also, multiple hypothesis blind decoding for the UE may contribute to increased UE complexity.

Aspects of the disclosure are initially described in the context of a wireless communication system. A network entity and a UE may know a frequency range that is used for transmission of synchronization information (e.g., a first frequency range). The network entity may select a frequency range to be used for transmission of common control information (e.g., a second frequency range) based on the frequency range used for the transmission of the synchronization information. For example, the first frequency range may convey a location of a PBCH in a time-frequency grid, and the location of the PBCH may inform the location of the second frequency range. Thus, a UE performing an initial search and synchronization may know the second frequency range based on or as a function of the first frequency range.

<FIG> illustrates an example of a wireless communications system <NUM> in accordance with various aspects of the present disclosure. The wireless communications system <NUM> includes base stations <NUM>, UEs <NUM>, and a core network <NUM>. In some examples, the wireless communications system <NUM> may be a Long Term Evolution (LTE) or LTE-Advanced (LTE-A) network.

Each base station <NUM> may provide communication coverage for a respective geographic coverage area <NUM>. A UE <NUM> may also be referred to as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. A UE <NUM> may also be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a personal electronic device, a handheld device, a personal computer, a wireless local loop (WLL) station, an Internet of things (IoT) device, an Internet of Everything (IoE) device, a machine type communication (MTC) device, an appliance, an automobile, or the like.

Core network <NUM>, or a component thereof, may be an example of a network entity configured to support aspects of the described techniques. Example components of a core network <NUM> may include, but are not limited to, a mobility management entity (MME), a home subscriber server (HSS), one or more gateways, and the like, which may be configured to support the described techniques.

In some cases, wireless communication system <NUM> may utilize different portions of the radio frequency spectrum band. In some examples, wireless communication system <NUM> may utilize one or more of an unlicensed spectrum, a licensed spectrum, a lightly licensed spectrum, licensed assisted access (e.g., licensed plus unlicensed spectrum), sub-<NUM> spectrum, millimeter-wave (mmW) spectrum, etc..

In some aspects, a network entity (such as core network <NUM> (or a component of core network <NUM>) and/or a base station <NUM>) may be configured for SIB transmission in accordance with aspects of the present disclosure. For example, the network entity may identify a first frequency range of a system bandwidth that is used for transmission of synchronization information. The network entity may select a second frequency range of the system bandwidth that is used for transmission of common control information. The second frequency range of the system bandwidth may be based on or a function of the first frequency range of the system bandwidth. The first and second frequency ranges may be less than the system bandwidth. The network entity may transmit the common control information at a frequency within the selected second frequency range of the system bandwidth.

A receiving device, such as a UE <NUM>, may identify a first frequency range of a system bandwidth that is used for transmission of synchronization information. The UE <NUM> may identify a second frequency range of the system bandwidth that is used for transmission of a common control information. The second frequency range of the system bandwidth may be based on or a function of the first frequency range of the system bandwidth. The first and second frequency ranges may be less than the system bandwidth. The UE <NUM> may receive the common control information at a frequency within the identified second frequency range of the system bandwidth.

<FIG> illustrates an example of a process flow <NUM> for system information block transmission. Process flow <NUM> may implement one or more aspects of wireless communication system <NUM> of <FIG>. Process flow <NUM> may include a UE <NUM> and a network entity <NUM>, which may be examples of the corresponding devices of <FIG>.

Broadly, process flow <NUM> may implement an example process where the channelization of the downlink grants and definition of the common search space (e.g., second frequency range) is based on or a function of the bandwidth occupancy (e.g., first frequency range) of the synchronization signals. The common search space may occupy the same frequency range as the synchronization signals. For example, the frequency range of the common search space could be a function of the bandwidth occupied by the synchronization signals and of any broadcast information already decoded (e.g., broadcast signals from a PBCH). Examples of the earlier decoded information may include, but is not limited to, a frame or a subframe index.

At <NUM>, the network entity <NUM> may identify the first frequency range of a system bandwidth used for transmission of synchronization information. The first frequency range of the system bandwidth may be known or preconfigured for the wireless communication system. The synchronization information may include one or more of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a broadcast signal, a physical broadcast channel (PBCH), and the like.

In some aspects, the synchronization information may be encoded to convey an indication or information associated with the SIB, the information being a function of the synchronization information. For example, network entity <NUM> may avoid scheduling grants for SIBs by pre-configuring information in those grants to be a function of broadcast information that UE <NUM> has previously decoded, e.g., prior to reading the SIBs.

At <NUM>, the network entity <NUM> may select the second frequency range of the system bandwidth that is used for the transmission of the common control information. The second frequency range may be selected based on the first frequency range. For example, the second frequency range may be the same frequency range as the first frequency range, may be offset a predetermined distance up or down from the first frequency range, may include a subset or superset of frequencies selected based on the first frequency range, and the like.

In some aspects, the common control information may include a downlink grant that is transmitted on a physical downlink control channel (PDCCH). Alternatively, the downlink grant may be for a physical downlink shared channel (PDSCH) carrying the system information. The downlink grant may provide an indication of a resource used to convey a SIB. The SIB may contain additional information associated with the wireless communication system, such as the system bandwidth, the raster offset, and the like. Thus, network entity <NUM> may configure the common control information to convey an indication of the SIB grant.

In some aspects, the common control information may include the SIB that indicates or otherwise includes information associated with the system bandwidth and the raster offset. In this example, the SIB may be transmitted according to a fixed frequency allocation, using a known modulation order, using a known scrambling sequence or order, or the like. In some aspects, the SIB included in the common control information may include all information traditionally conveyed in a downlink grant. In some aspects, the SIB included in the common control information may be transmitted in a fixed set of subframes or slots. In various examples, a subframe or a slot may be used (in some cases interchangeably) to illustrate a basic transmission time interval (TTI). In some aspects, the information included in the SIB of the common control information may be time-varying rather than fixed, provided that the time-variation may be a function of parameters already decoded from the synchronization information. This information may be preconfigured such that UE <NUM> and network entity <NUM> know which frequency allocation, modulation order, etc., are associated with the SIB included in the common control information. In some aspects, the SIB included in the common control information may be broadcast.

At <NUM>, the UE <NUM> may identify the first frequency range that is used for transmission of synchronization information. As discussed above, the first frequency range may be preconfigured and therefore UE <NUM> may know the first frequency range a priori.

At <NUM>, the UE <NUM> may identify the second frequency range that is used for the transmission of common control information. As discussed above, the second frequency range is based on the first frequency range, e.g., is a function of the first frequency range. Generally, UE <NUM> may have preconfigured information associated with the relationship between the first frequency range and the second frequency range, e.g., information that may be used to derive the second frequency range based at least in part on the first frequency range. UE <NUM> may use this preconfigured information to identify the second frequency range.

At <NUM>, the network entity <NUM> may transmit (and UE <NUM> may receive) the common control information, e.g., via a base station. As discussed, the common control information may include a downlink grant, may include a SIB that indicates the system bandwidth and raster offset, etc..

In some aspects, the common control information may include a downlink grant and use a scrambling scheme on a reference signal that is used to decode the common control information. The scrambling scheme is a function of the first frequency range. The scrambling scheme may be different from a system scrambling scheme (e.g., the scrambling scheme used to scramble other reference signals associated with frequencies outside of the second frequency range). As the second frequency range is based on or a function of the first frequency range, the scrambling scheme may also be said to be associated with the first frequency range of the system bandwidth.

Broadly, the scrambling of the reference signals used to decode the downlink grant (e.g., the downlink grant carried in the PDCCH that identifies the resource allocation for SIB) may be done beginning from the center of the second frequency range and then proceed out towards the edges of the system bandwidth. As another alternative approach, a scrambling scheme may be defined across the system bandwidth, with the exception that the portion of the system bandwidth within the second frequency range may use a different scrambling scheme. Each of these approaches may provide for descrambling common control information without UE <NUM> knowing the system bandwidth or raster offset yet.

In some aspects, the scrambling scheme may use scrambling sequences to scramble the reference signals associated with the second frequency range that are different from a scrambling sequence used to scramble other reference signals associated with frequencies outside of the second frequency range. For example, the scrambling sequence used for reference signals within the second frequency range may be different (e.g., use a different range, use different lengths of scrambling codes, etc.).

In some aspects, the scrambling scheme may be a mid-tone scrambling sequence that begins at the center frequency of the second frequency range and proceeds outward (e.g., upward and downward) from the center frequency through the system bandwidth. Thus, UE <NUM> may know a priori which scrambling sequence is used on the reference signals used to decode the common control information.

Certain UEs whose bandwidth capability equals or is less than the bandwidth of the first frequency range may be referred to as minimum bandwidth UEs. The described techniques support the UE processing of the common control information without knowing the system bandwidth or raster offset, e.g., support handling of these minimum bandwidth UEs.

For UEs with larger bandwidth capabilities, the downlink SIB broadcast messages may be transmitted over a wider bandwidth, which includes the above-mentioned minimum bandwidth. This may apply to every beam on which the downlink SIB messages are sent, e.g., both in the beam-sweeping case and in the case of a fixed beam identified via the UE's pre-random access channel (RACH) transmission (discussed with reference to <FIG> and <FIG>). The minimum bandwidth UEs may receive just the portions of the downlink SIB messages that lie within their bandwidth capability. However, the SIB messages may be repeated multiple times. By ensuring that different subsets of the encoded bits are modulated into the minimum bandwidth subset at different repetitions, this may support lower bandwidth UEs to also read these downlink SIB messages. The described techniques may thus support minimum bandwidth UEs by using different redundancy versions at different repetitions. In aspects, minimum bandwidth UEs may be supported by using the same redundancy version with a cyclic shift of blocks of tones applied after modulation, e.g., so that a different set of modulation symbols are mapped into the minimum bandwidth at each repetition.

Thus, in some aspects a cyclic shift pattern may be used to convey the common control information. For example, a cyclic shift pattern may be selected for block(s) of tones used to convey the common control information. Such an approach may ensure that minimum bandwidth UEs receive the common control information.

While the above techniques may work for OFDM based systems, concerns may arise for DFT-s-OFDM based systems due to DFT-spreading across the system bandwidth, which makes it difficult for a UE to receive information over a subset of that bandwidth. The described techniques may be extended to the case of multi-cluster DFT-s-OFDM transmissions, where each cluster has its own DFT-spreading. In this case the clusters could define the blocks of tones to be cyclically shifted. Thus, in some aspects a set of clusters for a multi-cluster DFT-s-OFDM scheme may be selected. Each cluster in the multi-cluster DFT-s-OFDM scheme may be associated with a different DFT spreading function. The set of clusters may identify the one or more blocks of tones. Thus, in some aspects, the common control information may be transmitted according to the cyclic shift pattern and/or according to the set of clusters.

At <NUM>, UE <NUM> may optionally identify a downlink grant for a SIB. The downlink grant may be conveyed or otherwise carried on a PDCCH. The downlink grant may provide a pointer to resources allocated for transmission of a SIB, e.g., resources associated with a PDSCH.

At <NUM>, the network entity <NUM> may optionally transmit a SIB, e.g., via a base station, to the UE <NUM>. The SIB may be transmitted via PDSCH, in some aspects. Additionally or alternatively, the SIB may be transmitted via PDCCH. At <NUM>, the UE <NUM> may optionally identify a system bandwidth and a raster offset based at least in part on the SIB. For example, the SIB may convey the system bandwidth and raster offset and/or may include a pointer to a table that can be used to identify the system bandwidth and raster offset.

Some wireless communications systems may support multiple SIB types. For example, a first SIB type (e.g., which may in some cases be referred to as remaining minimum system information (RMSI)) may convey the minimum information (e.g., in addition to system information conveyed via a master information block (MIB)) which a UE <NUM> needs before it can participate in a RACH procedure. A second SIB type (e.g., other system information (OSI)) may carry complementary information that is not required to participate in a RACH procedure. OSI may be carried via SIB or may be conveyed via radio resource control (RRC) signaling. By way of example, the RMSI may be carried over the same frequency range as the synchronization signals (e.g., such that bandwidth-limited UEs <NUM> may decode the RMSI and synchronization information). Accordingly, the first frequency range (e.g., associated with the synchronization information) may in some cases be the same as the second frequency range, as described further below.

<FIG> illustrates an example of a bandwidth diagram <NUM> for system information block transmission. Diagram <NUM> may implement one or more aspects of wireless communications system <NUM> and/or process flow <NUM> of <FIG> and <FIG>. Aspects of diagram <NUM> may be implemented by a network entity and/or a UE, which may be examples of the corresponding devices described above.

Diagram <NUM> may include an example of a system bandwidth <NUM> that includes a plurality of frequencies <NUM>, which may also be referred to as tones, bins, channels, hops, etc. Although twenty frequencies <NUM> are illustrated in <FIG>, it is to be understood that the system bandwidth <NUM> is not limited to twenty frequencies <NUM> and may, instead, include fewer or more frequencies <NUM>.

Diagram <NUM> may include a first frequency range <NUM>, a second frequency range <NUM>, and a set of frequencies <NUM>. The first frequency range <NUM> may be associated with transmission of synchronization information, as is discussed above. The first frequency range <NUM> may include a subset off frequencies <NUM> from the system bandwidth <NUM>. Diagram <NUM> also illustrates a raster offset <NUM> which may be the offset between the center frequency of the system bandwidth <NUM> and the center frequency within the first frequency range <NUM>.

The second frequency range <NUM> is associated with transmission of common control information. The second frequency range <NUM> is based on the first frequency range <NUM>. In the example of <FIG>, the second frequency range <NUM> occupies the same subset of frequencies as the first frequency range <NUM>. The second frequency range is a function of the first frequency range <NUM>. For example, the second frequency range <NUM> may be offset above or below the first frequency range <NUM> by a predetermined distance or number of frequencies <NUM>. In another example, the second frequency range <NUM> may be a predetermined distance above or below the first frequency range <NUM>. Other techniques may also be used such that the second frequency range <NUM> is a function of the first frequency range <NUM>.

Generally, the set of frequencies <NUM> (identified as frequencies <NUM>-a and <NUM>-b) generally illustrate the frequencies <NUM> within the system bandwidth that are outside of the second frequency range <NUM>, e.g., used for channelization of downlink and/or uplink transmissions (e.g., transmissions using PDSCH).

<FIG> illustrates an example of a process flow <NUM> for system information block transmission. Process flow <NUM> may implement one or more aspects of wireless communication system <NUM>, a process flow <NUM>, and/or a diagram <NUM> of <FIG>. Process flow <NUM> may include a UE <NUM> and a network entity <NUM>, which may be examples of the corresponding devices discussed with reference to <FIG>.

Broadly, process flow <NUM> may implement aspects of the described techniques that also include a RACH procedure. For example, even with fixed parameters that avoid the need for scheduling the SIBs, the SIB messages themselves may still be broadcast. In particular for mmW systems, broadcasting SIB messages may mean beam-sweeping the broadcast signals and/or using very low code-rates. Such constraints may be avoided by allowing the UE <NUM> to go through a RACH procedure after decoding as few SIB messages as possible. UE <NUM> may then receive the remaining system information via unicast signalling (e.g., via RRC signalling) instead. In particular, the minimum information needed for RACH may be contained in the synchronization information transmissions (e.g., the first frequency range). However, RACH procedures conventionally use knowledge of the system bandwidth and the raster offset in order to distribute the RACH messages over the system bandwidth. To enable UE <NUM> to perform a RACH procedure without this knowledge, the bandwidth of the RACH messages may be restricted to be related to that of first frequency range, similar to the feature discussed above with respect to the second frequency range.

At <NUM>, the network entity <NUM> may identify the synchronization frequency range of a system bandwidth used for transmission of synchronization information. The synchronization frequency range may correspond to the first frequency range discussed above.

At <NUM>, the network entity <NUM> may select the RACH frequency range of the system bandwidth that is used for the transmission of the RACH messages. The RACH frequency range may correspond to a third frequency range, in some aspects. The RACH frequency range may be a function of the synchronization frequency range, e.g., may be the same as the synchronization frequency range or may be based on (or a function of) the synchronization frequency range.

At <NUM>, the UE <NUM> may identify the synchronization frequency range that is used for transmission of synchronization information. As discussed above, the synchronization frequency range may correspond to the first frequency range discussed above and may be preconfigured. Therefore, UE <NUM> may know the synchronization frequency range a priori.

At <NUM>, the network entity <NUM> may transmit (and UE <NUM> may receive) the synchronization information, e.g., via a base station.

At <NUM>, the UE <NUM> may identify the RACH frequency range that is used for the transmission of RACH messages. The RACH frequency range may be based on the synchronization frequency range, e.g., may be the same frequency range, may be a function of the synchronization frequency range, and the like. Generally, UE <NUM> may have preconfigured information associated with the relationship between the synchronization frequency range and the RACH frequency range, e.g., information that may be used to derive the RACH frequency range based at least in part on the synchronization frequency range.

At <NUM>, UE <NUM> may transmit a pre-RACH message to the network entity (e.g., via a base station). The pre-RACH message may be transmitted at a frequency within the RACH frequency range. In some aspects, the pre-RACH message may include information associated with the location of the UE <NUM> and/or directional information for UE <NUM> with respect to the base station.

At <NUM>, network entity <NUM> (via a base station) may transmit, responsive to the pre-RACH message, the remaining system information to the UE <NUM>. The remaining system information (e.g., and/or common control information) may be transmitted in a beamforming direction that is indicated in the pre-RACH message.

<FIG> illustrates an example of a bandwidth diagram <NUM> for system information block transmission. Diagram <NUM> may implement one or more aspects of wireless communications system <NUM> and/or process flows <NUM> or <NUM> of <FIG>, <FIG>, and <FIG>. Aspects of diagram <NUM> may be implemented by a network entity and/or a UE, which may be examples of the corresponding devices described above.

Diagram <NUM> may include an example of a system bandwidth <NUM> that includes a plurality of frequencies <NUM>, which may also be referred to as tones, or bins, or channels, etc. Although <NUM> frequencies <NUM> are illustrated in <FIG>, it is to be understood that the system bandwidth <NUM> is not limited to <NUM> frequencies <NUM> and may, instead, include fewer or more frequencies <NUM>.

Diagram <NUM> may include a first frequency range <NUM> (also referred to as a synchronization frequency range) and a second frequency range <NUM> (also referred to as a RACH frequency range). The first frequency range <NUM> may include a subset of frequencies <NUM> from the set of available frequencies that make up the system bandwidth <NUM>. The second frequency range <NUM> may be associated with transmission of RACH messages as a part of a RACH procedure. The second frequency range <NUM> is based on the first frequency range <NUM>. In the example of <FIG>, the second frequency range <NUM> occupies more frequencies <NUM> than the frequencies of the first frequency range <NUM>. The second frequency range <NUM> is a function of the first frequency range <NUM>. For example, the second frequency range <NUM> may be offset above or below the first frequency range <NUM> by a predetermined distance or number of frequencies <NUM>. In another example, the second frequency range <NUM> may be a predetermined amount of frequencies larger or smaller than the first frequency range <NUM>. Other techniques may also be used such that the second frequency range <NUM> is based on or otherwise a function of the first frequency range <NUM>.

<FIG> shows a block diagram <NUM> of a wireless device <NUM> that supports system information block transmission in accordance with various aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a network entity, as described with reference to <FIG>. Wireless device <NUM> may include receiver <NUM>, network entity SIB transmission manager <NUM>, and transmitter <NUM>. Wireless device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

Receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to system information block transmission, etc.). Information may be passed on to other components of the device. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>.

Network entity SIB transmission manager <NUM> may be an example of aspects of the network entity SIB transmission manager <NUM> described with reference to <FIG>. Network entity SIB transmission manager <NUM> may identify a first frequency range of a system bandwidth used for transmission of synchronization information, select a second frequency range of the system bandwidth used for transmission of common control information, and transmit the common control information within the selected second frequency range of the system bandwidth. The second frequency range of the system bandwidth is a function of the first frequency range of the system bandwidth, and the first frequency range and the second frequency range may each be less than the system bandwidth.

<FIG> shows a block diagram <NUM> of a wireless device <NUM> that supports system information block transmission in accordance with various aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a wireless device <NUM> or a network entity, as described with reference to <FIG>. Wireless device <NUM> may include receiver <NUM>, network entity SIB transmission manager <NUM>, and transmitter <NUM>. Wireless device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

Network entity SIB transmission manager <NUM> may be an example of aspects of the corresponding components described with reference to <FIG>, <FIG>, and <FIG>. Network entity SIB transmission manager <NUM> may also include first frequency manager <NUM>, second frequency manager <NUM>, and information communication manager <NUM>.

First frequency manager <NUM> identifies a first frequency range of a system bandwidth used for transmission of synchronization information and encode the synchronization information to convey information associated with a SIB, where the information is a function of the synchronization information. In some cases, the synchronization information includes at least one of a PSS, a SSS, a broadcast signal, a PBCH, or combinations thereof.

Second frequency manager <NUM> may select a second frequency range of the system bandwidth used for transmission of common control information, the second frequency range of the system bandwidth being a function of the first frequency range of the system bandwidth, and the first frequency range and the second frequency range each being less than the system bandwidth.

Information communication manager <NUM> may transmit the common control information and a reference signal within the selected second frequency range of the system bandwidth, configure the common control information to convey an indication of a SIB grant, and transmit the SIB in the common control information using a fixed frequency allocation, a known modulation order, a known scrambling order, or a combination thereof. In some cases, the common control information includes a downlink grant received on a PDCCH, the downlink grant providing a resource allocation for a SIB, the SIB indicating the system bandwidth and a raster offset. In some cases, the common control information includes a SIB, the SIB indicating the system bandwidth and a raster offset. Information control manager <NUM> may select a scrambling scheme for the reference signal used to decode the common control information.

<FIG> shows a block diagram <NUM> of a network entity SIB transmission manager <NUM> that supports system information block transmission in accordance with various aspects of the present disclosure. The network entity SIB transmission manager <NUM> may be an example of aspects of a network entity SIB transmission manager <NUM>, a network entity SIB transmission manager <NUM>, or a network entity SIB transmission manager <NUM> described with reference to <FIG>, <FIG>, and <FIG>. The network entity SIB transmission manager <NUM> may include first frequency manager <NUM>, second frequency manager <NUM>, information communication manager <NUM>, scrambling manager <NUM>, RACH manager <NUM>, cyclic shift manager <NUM>, and cluster manager <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

First frequency manager <NUM> may identify a first frequency range of a system bandwidth used for transmission of synchronization information and encode the synchronization information to convey information associated with a SIB, where the information is a function of the synchronization information. In some cases, the synchronization information includes at least one of a PSS, a SSS, a broadcast signal, or combinations thereof.

Information communication manager <NUM> transmits the common control information and a reference signal within the selected second frequency range of the system bandwidth, configure the common control information to convey an indication of a SIB grant, and transmit the SIB in the common control information using a fixed frequency allocation, a known modulation order, a known scrambling order, or combinations thereof. In some cases, the common control information includes a downlink grant received on a PDCCH, the downlink grant providing a resource allocation for a SIB, the SIB indicating the system bandwidth and a raster offset. In some cases, the common control information includes a SIB, the SIB indicating the system bandwidth and a raster offset.

Scrambling manager <NUM> may select a scrambling scheme for the reference signal used to decode the common control information, the scrambling scheme being a function of the first frequency range of the system bandwidth, and the common control information including a downlink grant. In some cases, the scrambling scheme includes use of a scrambling sequence to scramble the reference signals associated with the second frequency range that is different from a system scrambling sequence to scramble other reference signals associated with frequencies outside of the second frequency range. In some cases, the scrambling scheme includes use of a mid-tone scrambling sequence that begins at a center frequency of the second frequency range and proceeds outward through the system bandwidth.

RACH manager <NUM> may select a third frequency range of the system bandwidth used for transmissions of one or more messages associated with a RACH procedure, the third frequency range being a function of the first frequency range of the system bandwidth, receive a pre-RACH transmission from a UE at a frequency within the third frequency range, and transmit, responsive to receiving the pre-RACH transmission, the common control information to the UE. In some cases, the common control information is transmitted according to a beamforming direction that is indicated by the pre-RACH transmission.

Cyclic shift manager <NUM> may select a cyclic shift pattern for one or more blocks of tones conveying the common control information and transmit the common control information according to the cyclic shift pattern.

Cluster manager <NUM> may select a set of clusters for a multi-cluster DFT-s-OFDM scheme, where each cluster in the multi-cluster DFT-s-OFDM scheme is associated with a different DFT spreading function, where the set of clusters identify the one or more blocks of tones and transmit the common control information according to the set of clusters.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports system information block transmission in accordance with various aspects of the present disclosure. Device <NUM> may be an example of or include the components of wireless device <NUM>, wireless device <NUM>, or a network entity, as described above, e.g., with reference to <FIG>. Device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including network entity SIB transmission manager <NUM>, processor <NUM>, memory <NUM>, software <NUM>, transceiver <NUM>, and I/O controller <NUM>. These components may be in electronic communication via one or more buses (e.g., bus <NUM>).

Processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a digital signal processor (DSP), a central processing unit (CPU), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor <NUM> may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into processor <NUM>. Processor <NUM> may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting system information block transmission).

Software <NUM> may include code to implement aspects of the present disclosure, including code to support system information block transmission. Software <NUM> may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software <NUM> may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

Transceiver <NUM> may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above (e.g., with one or more UEs <NUM>).

<FIG> shows a block diagram <NUM> of a wireless device <NUM> that supports system information block transmission in accordance with various aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a UE <NUM> as described with reference to <FIG>. Wireless device <NUM> may include receiver <NUM>, UE SIB transmission manager <NUM>, and transmitter <NUM>. Wireless device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

UE SIB transmission manager <NUM> may be an example of aspects of the UE SIB transmission manager <NUM> described with reference to <FIG>. UE SIB transmission manager <NUM> may identify a first frequency range of a system bandwidth used for transmission of a synchronization information, identify a second frequency range of a system bandwidth used for transmission of common control information, and receive the common control information and a reference signal within the identified second frequency range of the system bandwidth. The second frequency range of the system bandwidth is a function of the first frequency range of the system bandwidth, and the first frequency range and the second frequency range are each less than the system bandwidth. In some cases, the scrambling scheme is a function of the first frequency range of the system bandwidth.

<FIG> shows a block diagram <NUM> of a wireless device <NUM> that supports system information block transmission in accordance with various aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a wireless device <NUM> or a UE <NUM> as described with reference to <FIG> and <FIG>. Wireless device <NUM> may include receiver <NUM>, UE SIB transmission manager <NUM>, and transmitter <NUM>. Wireless device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

UE SIB transmission manager <NUM> may be an example of aspects of the corresponding component described with reference to <FIG>, <FIG>, and <FIG>. UE SIB transmission manager <NUM> may also include first frequency manager <NUM>, second frequency manager <NUM>, and information communication manager <NUM>. First frequency manager <NUM> may identify a first frequency range of a system bandwidth used for transmission of a synchronization information. Second frequency manager <NUM> may identify a second frequency range of a system bandwidth used for transmission of common control information, the second frequency range of the system bandwidth being a function of the first frequency range of the system bandwidth, and the first frequency range and the second frequency range each being less than the system bandwidth.

Information communication manager <NUM> receives the common control information and a reference signal within the identified second frequency range of the system bandwidth. Information communication manager <NUM> descrambles the reference signal used to decode the common control information according to a scrambling scheme.

<FIG> shows a block diagram <NUM> of a UE SIB transmission manager <NUM> that supports system information block transmission in accordance with various aspects of the present disclosure. The UE SIB transmission manager <NUM> may be an example of aspects of a UE SIB transmission manager <NUM> described with reference to <FIG>, <FIG>, and <FIG>. The UE SIB transmission manager <NUM> may include first frequency manager <NUM>, second frequency manager <NUM>, information communication manager <NUM>, scrambling manager <NUM>, RACH manager <NUM>, and cyclic shift manager <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

First frequency manager <NUM> may identify a first frequency range of a system bandwidth used for transmission of a synchronization information.

Second frequency manager <NUM> may identify a second frequency range of a system bandwidth used for transmission of common control information, the second frequency range of the system bandwidth being a function of the first frequency range of the system bandwidth, and the first frequency range and the second frequency range each being less than the system bandwidth.

Information communication manager <NUM> receives the common control information and a reference signal within the identified second frequency range of the system bandwidth.

Scrambling manager <NUM> may descramble a reference signal used to decode the common control information according to a scrambling scheme, the scrambling scheme being a function of the first frequency range of the system bandwidth, and the common control information including a downlink grant.

RACH manager <NUM> may identify a third frequency range of the system bandwidth used for transmission of one or more messages associated with a RACH procedure, the third frequency range being a function of the first frequency range of the system bandwidth, transmit a pre-RACH transmission to a base station at a frequency within the third frequency range, and receive, responsive to the transmission of the pre-RACH transmission, the common control information from the base station. In some cases, the common control information is received according to a beamforming direction that is indicated by the pre-RACH transmission.

Cyclic shift manager <NUM> may receive the common control information according to a cyclic shift pattern, where the cyclic shift pattern includes one or more blocks of tones conveying the common control information.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports system information block transmission in accordance with various aspects of the present disclosure. Device <NUM> may be an example of or include the components of UE <NUM> as described above, e.g., with reference to <FIG>. Device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including UE SIB transmission manager <NUM>, processor <NUM>, memory <NUM>, software <NUM>, transceiver <NUM>, antenna <NUM>, and I/O controller <NUM>. These components may be in electronic communication via one or more buses (e.g., bus <NUM>). Device <NUM> may communicate wirelessly with one or more base stations <NUM>.

Processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor <NUM> may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into processor <NUM>. Processor <NUM> may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting system information block transmission).

<FIG> shows a flowchart illustrating a method <NUM> for system information block transmission in accordance with various aspects of the present disclosure. The operations of method <NUM> may be implemented by a network entity or its components as described herein. For example, the operations of method <NUM> may be performed by a network entity SIB transmission manager as described with reference to <FIG>. In some examples, a network entity may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the network entity may perform aspects the functions described below using special-purpose hardware.

At <NUM> the network entity may identify a first frequency range of a system bandwidth used for transmission of synchronization information. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a first frequency manager as described with reference to <FIG>.

At <NUM> the network entity may select a second frequency range of the system bandwidth used for transmission of common control information, the second frequency range of the system bandwidth being a function of the first frequency range of the system bandwidth, and the first frequency range and the second frequency range each being less than the system bandwidth. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a second frequency manager as described with reference to <FIG>.

At <NUM> the network entity may select a cyclic shift pattern for one or more blocks of tones conveying the common control information. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a cyclic shift manager as described with reference to <FIG>.

At <NUM> the network entity may transmit the common control information at a frequency within the selected second frequency range of the system bandwidth. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by an information communication manager as described with reference to <FIG>.

At <NUM> the network entity may transmit the common control information according to the cyclic shift pattern. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a cyclic shift manager as described with reference to <FIG>.

At <NUM> the network entity may select a scrambling scheme for a reference signal used to decode the common control information, the scrambling scheme being a function of the first frequency range of the system bandwidth, and the common control information comprising a downlink grant. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a scrambling manager as described with reference to <FIG>.

At <NUM> the network entity may transmit the common control information and the reference signal within the selected second frequency range of the system bandwidth. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by an information communication manager as described with reference to <FIG>.

At <NUM> the network entity may select a third frequency range of the system bandwidth used for transmissions of one or more messages associated with a random access channel (RACH) procedure, the third frequency range being a function of the first frequency range of the system bandwidth. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a RACH manager as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> for system information block transmission in accordance with various aspects of the present disclosure. The operations of method <NUM> may be implemented by a UE <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a UE SIB transmission manager as described with reference to <FIG>. In some examples, a UE <NUM> may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the UE <NUM> may perform aspects the functions described below using special-purpose hardware.

At <NUM> the UE <NUM> may identify a first frequency range of a system bandwidth used for transmission of a synchronization information. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a first frequency manager as described with reference to <FIG>.

At <NUM> the UE <NUM> may identify a second frequency range of a system bandwidth used for transmission of common control information, the second frequency range of the system bandwidth being a function of the first frequency range of the system bandwidth, and the first frequency range and the second frequency range each being less than the system bandwidth. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by a second frequency manager as described with reference to <FIG>.

At <NUM> the UE <NUM> may receive the common control information and a reference signal within the identified second frequency range of the system bandwidth. The UE <NUM> may descramble the reference signal used to decode the common control information according to a scrambling scheme. The operations of <NUM> may be performed according to the methods described with reference to <FIG>. In certain examples, aspects of the operations of <NUM> may be performed by an information communication manager as described with reference to <FIG>.

Furthermore, aspects from two or more of the methods <NUM>, <NUM>, <NUM>, or <NUM> described with reference to <FIG>, <FIG>, <FIG>, or <FIG> may be combined.

Techniques described herein may be used for various wireless communications systems such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier FDMA (SC-FDMA), DFT-s-OFDM, and other systems. The terms "system" and "network" are often used interchangeably. A code division multiple access (CDMA) system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-<NUM>, IS-<NUM>, and IS-<NUM> standards. A time division multiple access (TDMA) system may implement a radio technology such as Global System for Mobile Communications (GSM).

An orthogonal frequency division multiple access (OFDMA) system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications system (UMTS). 3GPP LTE and LTE-A are releases of Universal Mobile Telecommunications System (UMTS) that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from the organization named "3rd Generation Partnership Project" (3GPP). While aspects an LTE system may be described for purposes of example, and LTE terminology may be used in much of the description, the techniques described herein are applicable beyond LTE applications.

In LTE/LTE-A networks, including such networks described herein, the term eNB may be generally used to describe the base stations. The wireless communications system or systems described herein may include a heterogeneous LTE/LTE-A network in which different types of eNBs provide coverage for various geographical regions. For example, each eNB or base station may provide communication coverage for a macro cell, a small cell, or other types of cell. The term "cell" may be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., sector, etc.) of a carrier or base station, depending on context.

Base stations may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, eNB, Home NodeB, a Home eNodeB, or some other suitable terminology. The geographic coverage area for a base station may be divided into sectors making up only a portion of the coverage area. The wireless communications system or systems described herein may include base stations of different types (e.g., macro or small cell base stations). The UEs described herein may be able to communicate with various types of base stations and network equipment including macro eNBs, small cell eNBs, relay base stations, and the like. There may be overlapping geographic coverage areas for different technologies.

A UE may be able to communicate with various types of base stations and network equipment including macro eNBs, small cell eNBs, relay base stations, and the like.

Each communication link described herein-including, for example, wireless communications system <NUM> of <FIG>-may include one or more carriers, where each carrier may be a signal made up of multiple sub-carriers (e.g., waveform signals of different frequencies).

Features implementing functions may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Also, as used herein, including in the claims, "or" as used in a list of items (for example, a list of items prefaced by a phrase such as "at least one of" or "one or more of') indicates an inclusive list such that, for example, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of: A, B, or C" is intended to cover A, B, C, A-B, A-C, B-C, and A-B-C. , as well as any combination with multiples of the same element (e.g., A-A, A-A-A, A-A-B, A-A-C, A-B-B, A-C-C, B-B, B-B-B, B-B-C, C-C, and C-C-C or any other ordering of A, B, and C).

Claim 1:
A method for wireless communication, comprising:
identifying (<NUM>) a first frequency range of a system bandwidth used for transmission of a synchronization information;
identifying (<NUM>), by applying a first function of the first frequency range of the system bandwidth, a second frequency range of the system bandwidth used for transmission of common control information, and the first frequency range and the second frequency range each being less than the system bandwidth;
receiving (<NUM>) the common control information within the identified second frequency range of the system bandwidth; and
descrambling a reference signal transmitted in the second frequency range and used to decode the common control information according to a scrambling scheme, the scrambling scheme being a second function of the first frequency range of the system bandwidth.