Patent Description:
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).

In some wireless systems, system information may be communicated via one or more broadcast messages. In some cases, different system information may be used by different devices to receive or decode these messages. For example, machine type communications (MTC) devices may utilize different system information than other UEs; and the system information for MTC devices may be broadcast with a particular timing, according to a particular schedule, or with certain frequency resources. If a device is unaware of such timing, scheduling, or frequency resources, the device may not be able to connect to a wireless network.

The <NPL>, discusses common message transmission including SIB, paging and RAR for Rel-<NUM> low complexity UEs and UEs in enhanced coverage with the following proposals: Proposal <NUM>: New SIB(s) are transmitted in one subband only within the entire system bandwidth. Proposal <NUM>: The subframes for "MTC SIB1" transmission are fixed in the specification and "MTC SIB1" indicates the subframes for subsequent "MTC SIs". Proposal <NUM>: The frequency location of "MTC SIB1" can be predefined in the specification and "MTC SIB1" indicates the frequency location of subsequent "MTC SIs". Proposal <NUM>: The MCS/TBS of "MTC SIB1" is indicated in MIB and "MTC SIB1" indicates the MCS/TBS of subsequent "MTC SIs".

The scope of protection of the present invention is defined in the independent claims.

A wireless device (such as a machine type communications (MTC) device) may determine one or more scheduling parameters for a system information block (SIB) based on the bandwidth or duplexing configuration of a communication link. The scheduling parameters may depend on signaling in a broadcast communication (e.g., a master information block (MIB)) or a frequency hopping configuration, or both. In some cases, a broadcast channel is scheduled during a transmission time interval (TTI) within a narrowband region of a system bandwidth. Available resources within the TTI, which may be fewer than all resources of the narrowband region within the TTI, may be identified, and the SIB may be mapped to the available resources. A determination of available resources for a SIB may be based on the location of broadcast information; for instance, the SIB may be mapped so as to avoid collisions with a broadcast channel.

A method of wireless communication is described, as defined in claim <NUM>.

An apparatus for wireless communication is described, as defined in claim <NUM>.

A corresponding computer program for wireless communication is described, as defined in claim <NUM>. The explanations in the following referring to a computer-readable medium likewise apply to the computer program - and vice versa.

A further method of wireless communication is described, as defined in claim <NUM>.

A further apparatus for wireless communication is described, as defined in claim <NUM>.

A further computer program for wireless communication is described, as defined in claim <NUM>.

Aspects of the disclosure are described in reference to the following figures:.

Some wireless systems support data communication technologies that allow devices to communicate with one another or a base station without human intervention. Such communication may be referred to as Machine Type Communication (MTC). In some cases, systems may support MTC by using techniques or features tailored for MTC devices. Techniques or features employed for the purpose of improving MTC may be referred to as enhanced MTC (eMTC). To support eMTC, systems may be configured to account for operating characteristics of MTC devices, which may be different from other user equipment (UE). This may include broadcasting certain MTC-specific system information using various repetition levels, transport block sizes, and the like.

An MTC device or MTC UE may be a low complexity, low cost device-relative to other UEs-and may be characterized by features such as low power operation, limited duplexing capability, and operation in environments with poor radio link conditions. Additionally, some MTC UEs are configured to operate using a narrow bandwidth, as compared with bandwidth used by other UEs or as compared with a total available system bandwidth. Systems supporting eMTC may be configured with these MTC UE characteristics in mind. In particular, in some examples and as described below, systems may support eMTC by supporting narrowband operation within a larger system bandwidth.

In some cases, systems may broadcast and MTC devices may utilize MTC-specific system information, including System Information Blocks (SIBs) tailored for MTC. As discussed below, various SIBs convey different information that may be necessary or helpful for UE operation within the system. For instance, a system may broadcast a SIB called SIB1, which may include certain necessary system information. Systems employing eMTC may broadcast MTC-specifics SIBs, which may convey necessary or useful system information for MTC operation. In some cases, systems broadcast an MTC-specific version of SIB1 (MTC SIB1).

The contents of MTC SIB1 may assist MTC UEs to evaluate cell access procedures and may define the scheduling of other system information for MTC SIBs other than MTC SIB1. Scheduling parameters for MTC SIB1 may be determined by a MTC UE based on an identifier in a separate broadcast message (e.g., in the master information block (MIB)). An MTC UE may read the broadcast message, interpret the identifier, and ascertain SIB1 scheduling parameters. The scheduling parameters may include a SIB repetition level, the transport block size (TBS), the subframe index, or the number of allocated resource blocks (RBs). The scheduling parameters may depend on a duplexing configuration, bandwidth, or frequency hopping configuration. In some cases, the repetition level may change based on the TBS or the hopping configuration. Additionally, an MTC UE's interpretation of the identifier contained in a broadcast message may depend on the duplexing configuration or bandwidth, or both.

As described below, the identifier may be a multi-bit field in the MIB. This identifier may be used to determine the scheduling parameters for SIB1. In some cases, a frequency hopping configuration may also be signaled with an additional bit in MIB. Thus, the repetition schedule may change depending on the hopping configuration. The multi-bit identifier may also correspond to the TBS, hopping configuration, subframes index, repetition level, and the number of resources. In other cases, the same TBS may be signaled, but the repetition level may change.

In some cases, a particular instance of SIB1 may be scheduled such that it overlaps with a scheduled broadcast channel transmission. That is, due to the resource constraints of narrowband operation, an anticipated transmission of SIB1 and another anticipated broadcast transmission may collide with one another. For example, an anticipated SIB1 transmission may overlap (e.g., collide) with a Physical Broadcast Channel (PBCH), primary synchronization signal (PSS), secondary synchronization signal (SSS), or the like within a <NUM> band. In such cases, the collision may be avoided by adjusting the anticipated SIB1 transmission by, for instance, mapping SIB1 to resources not occupied by the broadcast transmission.

By way of example, it may not be suitable to map SIB1 to a physical resource block (PRB) that contains a PBCH in the same subframe or to a subcarrier that contains PBCH in the same subframe. In other examples, SIB1 may be mapped to subcarriers that contain PBCH in the same subframe; however, SIB1 may be mapped to resource elements (RE) other than those that contain PBCH, PSS, or SSS. In some cases, it may be appropriate to apply rate matching or puncturing to support mapping to available resources. In other examples, it may not be suitable to map SIB1 to any RE that may potentially include PBCH (or its repetitions). For instance, it may not be suitable to map SIB1 to REs for PBCH repetitions even when repetitions are off. In other cases, MTC devices may or may not establish a configuration for using cell-specific reference signal (CRS) for <NUM>-antenna ports.

Aspects of the disclosure are described below in the context of a wireless communication system. Specific examples are then described for determining SIB <NUM> scheduling resources and parameters based on the system configuration and the location of broadcast signals. These and other aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to system information for eMTC.

<FIG> illustrates an example of a wireless communications system <NUM> that supports system information for eMTC in accordance with various aspects of the present disclosure. The wireless communications system <NUM> includes base stations <NUM>, user equipment (UEs) <NUM>, and a core network <NUM>. In some examples, the wireless communications system <NUM> may be a Long Term Evolution (LTE)/LTE-Advanced (LTE-A) network. Wireless communications system <NUM> may support communication of system information for MTC devices based on system properties and the location of broadcast signals.

Each base station <NUM> may provide communication coverage for a respective geographic coverage area <NUM>. Communication links <NUM> shown in wireless communications system <NUM> may include uplink (UL) transmissions from a UE <NUM> to a base station <NUM>, or downlink (DL) transmissions, from a base station <NUM> to a UE <NUM>. A UE <NUM> may also be referred to as a mobile station, a subscriber station, a remote unit, a wireless device, an access terminal, a handset, a user agent, a client, or some other suitable terminology. Each of the various UEs <NUM> may be an MTC device, a cellular phone, a wireless modem, a handheld device, a personal computer, a tablet, a personal electronic device, or the like.

As mentioned, MTC devices or MTC UEs <NUM> may provide for automated communication, which may include those implementing communications referred to as Machine-to-Machine (M2M) communication, MTC, eMTC, or the like. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, transaction-based business charging, and wearable devices. In some cases, scheduling of system information for MTC UEs <NUM> may be different from system information for other UEs <NUM> within the system. A repetition level, transport block size (TBS), subframe index, etc. for an MTC-specific SIB1 may be different from a SIB1 intended for other UEs <NUM>. This MTC-specific system information may account for MTC-specific characteristics. For example, an MTC UE <NUM> may operate using half-duplex (one-way) communications at a reduced peak rate. MTC UEs <NUM> may also be configured to enter a power saving "deep sleep" mode when not engaging in active communications. An MTC UE <NUM> may also operate in narrowband regions of a larger system bandwidth.

LTE systems, including some examples of system <NUM>, may utilize OFDMA on the DL and single carrier frequency division multiple access (SC-FDMA) on the UL. OFDMA and SC-FDMA partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones or bins. Each subcarrier may be modulated with data. For example, K may be equal to <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> with a subcarrier spacing of <NUM> kilohertz (KHz) for a corresponding system bandwidth (with guardband) of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> megahertz (MHz), respectively. The system bandwidth may also be partitioned into sub-bands. For example, a sub-band may cover <NUM>, and there may be <NUM>, <NUM>, <NUM>, <NUM> or <NUM> sub-bands. A narrowband region used by an MTC UE <NUM> may be a portion of the overall system bandwidth.

A frame structure may be used to organize time resources of wireless communications system <NUM>. A frame may be a <NUM> interval that may be further divided into <NUM> equally sized sub-frames. Each sub-frame may include two consecutive time slots. Each slot may include <NUM> or <NUM> OFDMA symbol periods. A resource element consists of one symbol period and one subcarrier (a <NUM> frequency range). A resource block may contain <NUM> consecutive subcarriers in the frequency domain and, for a normal cyclic prefix in each OFDM symbol, <NUM> consecutive OFDM symbols in the time domain (<NUM> slot), or <NUM> resource elements. Some resource elements may include DL reference signals (DL-RS). The DL-RS may include a CRS and a UE-specific RS (UE-RS), which may also be referred to as a demodulation reference signal (DM-RS). UE-RS may be transmitted on the resource blocks associated with PDSCH. (Additional details of CRS and UE-RS are described below. ) The number of bits carried by each resource element may depend on the modulation scheme (the configuration of symbols that may be selected during each symbol period). Thus, the more resource blocks that a UE receives and the higher the modulation scheme, the higher the data rate may be.

In some cases, time intervals may be expressed in multiples of a basic time unit (e.g., the sampling period, Ts= <NUM>/<NUM>,<NUM>,<NUM> seconds in LTE). Frames may have a length of <NUM> (Tf = <NUM>·Ts), and may be identified by an SFN ranging from <NUM> to <NUM>. Each frame may include ten <NUM> subframes numbered (e.g., indexed) from <NUM> to <NUM>. A subframe may be further divided into two <NUM> slots, each of which contains a number symbol periods depending on the length of the cyclic prefix prepended to each symbol. Excluding the cyclic prefix, each symbol contains <NUM> sample periods. In some cases the subframe may be the smallest scheduling unit, also known as a transmission time interval (TTI). In other cases, a TTI may be shorter than a subframe or may be dynamically selected (e.g., in short TTI bursts or in selected component carriers using short TTIs).

Data, which may be transmitted according to the resource structures describe above, may be divided into logical channels, transport channels, and physical layer channels. Channels may also be classified into Control Channels and Traffic Channels. Logical control channels may include paging control channel (PCCH) for paging information, broadcast control channel (BCCH) for broadcast system control information, multicast control channel (MCCH) for transmitting multimedia broadcast multicast service (MBMS) scheduling and control information, dedicated control channel (DCCH) for transmitting dedicated control information, common control channel (CCCH) for random access information, DTCH for dedicated UE data, and multicast traffic channel (MTCH), for multicast data. DL transport channels may include broadcast channel (BCH) for broadcast information, a downlink shared channel (DL-SCH) for data transfer, paging channel (PCH) for paging information, and multicast channel (MCH) for multicast transmissions. uplink (UL) transport channels may include RACH for access and uplink shared channel (UL-SCH) for data. DL physical channels may include PBCH for broadcast information, physical control format indicator channel (PCFICH) for control format information, physical downlink control channel (PDCCH) for control and scheduling information, PHICH for hybrid automatic repeat request (HARQ) status messages, physical downlink shared channel (PDSCH) for user data and physical multicast channel (PMCH) for multicast data. UL physical channels may include physical random access channel (PRACH) for access messages, PUCCH for control data, and PUSCH for user data.

Carriers of system <NUM>, which may be illustrated by communication links <NUM>, may transmit bidirectional communications using frequency division duplex (FDD) (e.g., using paired spectrum resources) or TDD operation (e.g., using unpaired spectrum resources). Frame structures for FDD (e.g., frame structure type <NUM>) and TDD (e.g., frame structure type <NUM>) may be defined. For TDD frame structures, each subframe may carry UL or DL traffic, and special subframes may be used to switch between DL and UL transmission. Allocation of UL and DL subframes within radio frames may be symmetric or asymmetric and may be statically determined or may be reconfigured semi-statically. Special subframes may carry DL or UL traffic and may include a Guard Period (GP) between DL and UL traffic. Switching from UL to DL traffic may be achieved by setting a timing advance at the UE <NUM> without the use of special subframes or a guard period. UL-DL configurations with switch-point periodicity equal to the frame period (e.g., <NUM>) or half of the frame period (e.g., <NUM>) may also be supported. For example, TDD frames may include one or more special frames, and the period between special frames may determine the TDD DL-to-UL switch-point periodicity for the frame.

Use of TDD may offer flexible deployments without requiring paired UL-DL spectrum resources. In some TDD network deployments, interference may be caused between UL and DL communications (e.g., interference between UL and DL communication from different base stations, interference between UL and DL communications from base stations and UEs, etc.). For example, where different base stations <NUM> serve different UEs <NUM> within overlapping coverage areas according to different TDD UL-DL configurations, a UE <NUM> attempting to receive and decode a DL transmission from a serving base station <NUM> can experience interference from UL transmissions from other, proximately located UEs <NUM>. In some examples, system <NUM> may utilize either or both TDD or FDD configurations. The scheduling parameters for SIB <NUM> may depend on the communication duplexing configuration (FDD or TDD).

A UE <NUM>, including an MTC UE <NUM>, attempting to access a wireless network may perform an initial cell search by detecting a primary synchronization signal (PSS) from a base station <NUM>. The PSS may enable synchronization of slot timing and may indicate a physical layer identity value. The UE <NUM> may then receive a secondary synchronization signal (SSS). The SSS may enable radio frame synchronization, and may provide a cell identity value, which may be combined with the physical layer identity value to identify the cell. The SSS may also enable detection of a duplexing mode and a cyclic prefix length. Some systems, including certain examples of system <NUM> operating in TDD configuration, may transmit an SSS but not a PSS. Both the PSS and the SSS may be located in the central <NUM> and <NUM> subcarriers of a carrier, respectively. After receiving the PSS and SSS, the UE <NUM> may receive a master information block (MIB), which may be transmitted in the physical PBCH. The MIB may contain system bandwidth information, a system frame number (SFN), and a PHICH configuration. After decoding the MIB, the UE <NUM> may receive one or more SIBs. For example, SIB1 may contain cell access parameters and scheduling information for other SIBs. Decoding SIB1 may enable the UE <NUM> to receive SIB2. SIB2 may contain radio resource control (RRC) configuration information related to RACH procedures, paging, PUCCH, PUSCH, power control, SRS, and cell barring. In some cases, the MIB may include a bitfield that usable by an MTC UE <NUM> to identify scheduling parameters for an MTC-specific SIB.

After completing initial cell synchronization, a UE <NUM> may decode the MIB, SIB1 and SIB2 prior to accessing the network. As mentioned, the MIB may be transmitted on PBCH, and it may utilize the first <NUM> OFDM symbols of the second slot of the first subframe of each radio frame. In some cases, PBCH might be repeated in other resources (e.g. other resource elements in the same subframe, or a different subframe). It may use the middle <NUM> resource block (RBs) (<NUM> subcarriers) in the frequency domain, which, as described below, may introduce some constraints related to SIB mapping for MTC UEs <NUM> operating in a narrowband region. But because the MIB carries a few important pieces of information for UE initial access-including: downlink (DL) channel bandwidth in term of RBs, PHICH configuration (duration and resource assignment), and SFN-the system <NUM> may seek to avoid collisions between a SIB and the MIB. A new MIB may be broadcast every fourth radio frame (SFN mod <NUM> = <NUM>) at and rebroadcast every frame (<NUM>). Each repetition is scrambled with a different scrambling code. After reading a MIB (either a new version or a copy), the UE <NUM> may can try different phases of a scrambling code until it gets a successful cyclic redundancy check (CRC) check. The phase of the scrambling code (<NUM>, <NUM>, <NUM> or <NUM>) may enable the UE <NUM> to identify which of the four repetitions has been received. Thus, the UE <NUM> may determine the current SFN by reading the SFN in the decoded transmission and adding the scrambling code phase.

After receiving the MIB, a UE may receive one or more SIBs. Different SIBs may be defined according to the type of system information conveyed. A new SIB1 may be transmitted in the fifth subframe of every eighth frame (SFN mod <NUM> = <NUM>) and rebroadcast every other frame (<NUM>). SIB1 includes access information, including cell identity information, and it may indicate whether a UE is allowed to camp on a cell of a base station <NUM>. SIB1 also includes cell selection information (or cell selection parameters). Additionally, SIB1 includes scheduling information for other SIBs. SIB2 may be scheduled dynamically according to information in SIB1, and includes access information and parameters related to common and shared channels. The periodicity of SIB2 can be dynamic, (e.g., it may be set to <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> or <NUM> radio frames). Additionally, MTC-specific SIBs, including MTC SIB1, may be transmitted according to different repetition levels based on various system configurations.

After receiving synchronization information and a MIB, a UE <NUM> may receive one or more SIBs. Different SIBs may be defined according to the type of system information conveyed. SIB1 includes access information such as cell identity information, and may also indicate whether a UE <NUM> is allowed to camp on a cell. SIB1 also includes cell selection information (or cell selection parameters). Additionally, SIB1 includes scheduling information for other SIBs. SIB2 includes access information and parameters related to common and shared channels. SIB3 includes cell reselection parameters. SIB4 and SIB5 include reselection information about neighboring Long Term Evolution (LTE) cells. SIB6 through SIB8 include reselection information about non-LTE (e.g., Universal Mobile Telecommunications System (UMTS), GERAN, and code division multiple access (CDMA)) neighboring cells). SIB9 includes the name of a Home evolved node B (eNB). SIB10 through SIB12 include emergency notification information (e.g., tsunami and earthquake warnings). And SIB13 includes information related to MBMS configuration. In some cases, a SIB may be scheduled to overlap with PSS or SSS, and instead, the SIB may be mapped to resources identified to be available within the TTI. MTC-specific SIBs may include various combinations of information conveyed in the SIBs identified above; and the contents of MTC-specific SIBs may be tailored to MTC operation.

In some cases, wireless communications system <NUM> may utilize coverage enhancement (CE) techniques to improve the quality of a communication link <NUM> for UEs <NUM>, including MTC UEs <NUM>, located at a cell edge, operating with low power transceivers, or experiencing high interference or path loss. CE techniques may include repeated transmissions, TTI bundling, HARQ retransmission, PUSCH hopping, beamforming, power boosting, or other techniques. The CE techniques used may depend on the specific needs of UEs <NUM> in different circumstances. For example, TTI bundling may involve sending multiple copies of the same information in a group of consecutive TTIs rather than waiting for a negative acknowledgement (NACK) before retransmitting redundancy versions. This may be effective for users engaging in voice over Long Term evolution (VoLTE) or VOIP communications, as well as for MTC UEs <NUM> operating with coverage limitations. In other cases, the number of HARQ retransmissions may also be increased. Uplink data transmissions may be transmitted using frequency hopping to achieve frequency diversity. Beamforming may be used to increase the strength of a signal in a particular direction, or the transmission power may simply be increased. In some cases, one or more CE options may be combined and CE levels may be defined based on a number of decibels the techniques are expected to improve a signal (e.g., no CE, 5dB CE, 10dB CE, 15dB CE, etc.). In some cases, the scheduling parameters for SIB1 may depend on the frequency hopping configuration. This configuration may be explicitly signaled in the bitfield contained within the MIB, for example.

A base station <NUM> may insert periodic pilot symbols such as CRS to aid UEs <NUM> in channel estimation and coherent demodulation. CRS may include one of <NUM> different cell identities. They may be modulated using quadrature phase shift keying (QPSK) and power boosted (e.g., transmitted at 6dB higher than the surrounding data elements) to make them resilient to noise and interference. CRS may be embedded in <NUM> to <NUM> resource elements in each resource block based on the number of antenna ports or layers (up to <NUM>) of the receiving UEs <NUM>. In addition to CRS, which may be utilized by all UEs <NUM> in the geographic coverage area <NUM> of the base station <NUM>, UE-RS (or DMRS) may be directed toward specific UEs <NUM> and may be transmitted only on resource blocks assigned to those UEs <NUM>. In some cases, a UE may refrain from monitoring for the SIB for resource elements of the TTI that are available for CRS transmission.

As described in this disclosure, UE <NUM> (such as an MTC UE <NUM>) may determine one or more scheduling parameters for a SIB based on the bandwidth or duplexing configuration of a communication link. The scheduling parameter may depend on signaling in a broadcast communication (e.g., a MIB) or a frequency hopping configuration. In some cases, a broadcast channel may be scheduled during a TTI within a narrowband region of a system bandwidth. Available resources within the TTI may be identified and the SIB may be mapped to the available resources within the narrowband region based on the location of the broadcast information.

<FIG> illustrates an example of a wireless communications system <NUM> for system information for eMTC in accordance with various aspects of the present disclosure. Wireless communications system <NUM> may include a UE <NUM>-a and base station <NUM>-a, which may be examples of a UE <NUM> and base station <NUM> described with reference to <FIG>. In some cases, UE <NUM>-a is an MTC device, and may determine SIB1 scheduling parameters based on system properties broadcast by base station <NUM>-a. UE <NUM>-a may also determine the resources available for SIB1 transmission based on the location of broadcast signals from base station <NUM>-a.

Wireless communications system <NUM> may support MTC operations to enable operation of low cost and low complexity devices. For example, in the context of LTE systems, such low cost UEs or MTC UEs <NUM> may be referred to as category <NUM> UEs, which may be characterized by reduced peak data rates (e.g., a possible maximum of <NUM> bits for a transport block size), rank one transmission, one receive antenna, and, if half-duplex, relaxed switching timing (from transmission to reception or vice versa) from, for example, <NUM> for regular UEs to <NUM> for MTC UEs. These MTC UEs <NUM> may monitor DL control channels in manner similar to other UEs <NUM>, including PDCCH) and enhanced PDCCH (ePDCCH)).

Additional MTC enhancements (referred to as eMTC) may be supported as well. For example, narrowband operation may be supported, such that MTC UE <NUM>-a may be able to operate in a wider system bandwidth. The system <NUM> may support operation in multiple system bandwidth ranges (e.g., <NUM>/<NUM>/<NUM>/<NUM>/<NUM>/<NUM>) via <NUM> or <NUM> RBs, as described above. Additionally, system <NUM> may support coverage enhancements up to 15dB.

The system <NUM> may transmit (e.g., broadcast on PDSCH) MTC SIB1 with a contents that assists UE <NUM>-a in cell access, and which may define the scheduling of other system information, for example, MTC SIBs other than MTC SIB1. In some cases, the number of resource blocks used for MTC SIB transmission may be fixed to <NUM> Physical PRBs. The Transport Block Size (TBS) of MTC SIB1 may be based on a configuration of system <NUM>, and may be indicated the MIB. The frequency location of MTC SIB1 may be derived, for example, from a Physical Cell Identification (PCID), which may be provided in the MIB. Additionally, the time location (e.g., as indicated in the MIB) for MTC SIB1 may include subframes (SFs) indexed: {<NUM>, <NUM>, <NUM>, <NUM>} for FDD and {<NUM>, <NUM>, <NUM>, <NUM>} for TDD. In some cases, the time location may depend on whether the subframes and frames are signaled in MIB or may be fixed in specification. Scheduling information for MTC SIBs other than MTC SIB1 may be given in MTC SIB1. The number of repetitions for MTC SIBs other than MTC SIB1 may be configurable by the network. Alternatively, some wireless systems (including system <NUM>, in some cases) may establish a configuration for signaling the number of repetitions for MTC SIB1 via a wireless network.

According to the invention, scheduling parameters for SIB1 are determined by UE <NUM>-a. An identifier is contained in a broadcast message sent by base station <NUM>-a, for example, in the MIB. SIB1 scheduling parameters are then determined based on the identifier. The scheduling parameters may include the SIB1 repetition level, the TB), or the subframe index. The scheduling parameters may depend on the communication duplexing configuration, bandwidth, or frequency hopping configuration, or the like.

The identifier may contain a multi-bit field, which UE <NUM>-a uses to determine the scheduling parameters for SIB1. By way of example, the following tables illustrate possible multi-bit field identifiers that may be provided in a MIB. For instance, Table <NUM> shows how the identifier may be used to determine the scheduling parameters and how those parameters may depend on the duplexing configuration and bandwidth:.

In other cases, the hopping configuration may be signaled with an extra bit (e.g., with a total of three bits) in MIB as shown in Table <NUM>:.

The repetition schedule may change depending on the hopping configuration. The multi-bit identifier may also correspond to the TBS, hopping configuration, subframes index, repetition level, and the number of resources:.

In other cases, the same TBS may be signaled, but the repetition level may change, as seen in Table <NUM>:.

In some cases, an anticipated transmission of SIB1 may overlap with another anticipated broadcast signal. This may be due to a narrowband operation of system <NUM>. That is, UE <NUM>-a may be a narrowband MTC device. Certain critical broadcast information may be restricted to resources within the narrowband region. Thus, additional resource for other transmissions, such as SIB1, may be scarce. For example, an anticipated SIB1 transmission may overlap with (e.g., be expected to collide with) PBCH, PSS, or SSS in certain subframes when system <NUM> operates with a <NUM> bandwidth to communicate with UE <NUM>-a. In order to avoid a collision, SIB1 may be mapped to resources within the narrowband that are not occupied by PBCH, PSS, or SSS.

<FIG>illustrate examples of scheduling schemes <NUM>-a, <NUM>-b, <NUM>-c, and <NUM>-d that support system information for eMTC in accordance with various aspects of the present disclosure. Scheduling schemes <NUM>-a, <NUM>-b, <NUM>-c, and <NUM>-d may include scheduling consistent with the present disclosure, and illustrate a resource mapping to avoid collisions, as described above.

Resource elements <NUM> may represent time and frequency units for transmission of individual symbols. For example, a resource element <NUM> may cover one subcarrier (e.g., <NUM> subcarrier) and <NUM> symbol period (e.g., approximately <NUM>/<NUM> seconds). CRS elements <NUM> may represent time and frequency units which may be used for the transmission of reference signals for channel estimation as described in <FIG>. In some cases, the number of CRS elements <NUM> that are used may depend on the number of antenna ports used for communication (e.g., <NUM> ports, as illustrated in <FIG>). PBCH elements <NUM> may represent time and frequency units for transmission of parameters that may be used for PBCH. In some cases, PBCH may be used for initial access of the cell (e.g., for the transmission of a MIB). PSS or SSS elements <NUM> may represent time and frequency units for transmission of information that may be used for cell synchronization.

Scheduling scheme <NUM>-a is an example in which the scheduling of a MTC SIB <NUM> may depend on, or be determined, based on the presence of CRS elements <NUM>-a, PBCH elements <NUM>-a, and PSS or SSS elements <NUM>-a within a TTI. For example, in some cases the scheduling of an MTC SIB1 may be based on region <NUM>-a. As illustrated, region <NUM>-a may include the resource blocks monitored by a UE <NUM> (such as an MTC device) during a TTI including PBCH elements <NUM>-a or PSS or SSS elements <NUM>-a. Thus, MTC SIB1 may be mapped to resources exclusive of (e.g., outside of) region <NUM>-a.

Scheduling scheme <NUM>-b is an example in which the scheduling of a MTC SIB1 may depend on the presence of CRS elements <NUM>-b, PBCH elements <NUM>-b, and PSS or SSS elements <NUM>-b. For example, in some cases, the scheduling of a MTC SIB1 may be based on an region <NUM>-b. As illustrated, in some examples, region <NUM>-b may include those subcarriers monitored by a UE <NUM> (such as an MTC device) during a TTI that include PBCH elements <NUM>-b or PSS or SSS elements <NUM>-b. Thus, MTC SIB1 may be mapped to resources exclusive of (e.g., outside of) region <NUM>-b.

Scheduling scheme <NUM>-c is an example in which the scheduling of a MTC SIB <NUM> may depend on the presence of CRS elements <NUM>-c, PBCH elements <NUM>-c, and PSS or SSS elements <NUM>-c. For example, in some cases the scheduling of a MTC SIB1 may be based on an region <NUM>-c. As illustrated in some examples, region <NUM>-c may include PBCH elements <NUM>-c or PSS or SSS elements <NUM>-c. Additionally, region <NUM>-c may or may not include the RE available for CRS transmission but not currently in use. Thus, MTC SIB1 may be mapped to resources exclusive of (e.g., outside of) region <NUM>-c.

Scheduling scheme <NUM>-d is an example in which the scheduling of a MTC SIB1 may depend on the presence of CRS elements <NUM>-d, PBCH elements <NUM>-d, and PSS or SSS elements <NUM>-d. For example, in some cases the scheduling of a MTC SIB1 may be based on an region <NUM>-d. As illustrated in some examples, region <NUM>-d may include PBCH elements <NUM>-d, or PSS or SSS elements <NUM>-d, as well as PBCH repetition resource elements <NUM>-d. PBCH repetition resource elements <NUM>-d may be those resource elements available for PBCH repetition. Additionally, region <NUM>-d may or may not include the RE available for CRS transmission but not currently in use. Thus, MTC SIB1 may be mapped to resources exclusive of (e.g., outside of) region <NUM>-d.

<FIG> illustrates an example of a process flow <NUM> in a system that supports system information for eMTC in accordance with various aspects of the present disclosure. Process flow <NUM> may include a UE <NUM>-b and base station <NUM>-b, which may be examples of a UE <NUM> and base station <NUM> described with reference to <FIG>. For example, UE <NUM>-b may be an MTC device. Process flow <NUM> may illustrate aspects of SIB coordination and provisioning in a wireless communication system between base station <NUM>-b and UE <NUM>-b. The described method of wireless communication may include determining a bandwidth or duplexing configuration (e.g. a frequency hopping configuration). In some examples, the bandwidth and duplexing configuration may be determined based on broadcast communication, and the broadcast communication may include a MIB, PSS, or SSS.

Thus, at <NUM>, base station <NUM>-b may transmit the PSS or SSS, which may be received by UE <NUM>-b. In some cases, UE <NUM>-b may determine aspects of the system properties based on the PSS or SSS, or both. For example, UE <NUM>-b may determine whether the duplexing configuration for the system is TDD or FDD based on the SSS.

At <NUM>, base station <NUM>-b may transmit (e.g., broadcast on PBCH) a MIB, which may be received by UE <NUM>-b. That is, UE <NUM>-b may receive the MIB, which may include a signal (e.g. a bit field) indicative of the scheduling parameter for a SIB as well as information about system bandwidth. This determination may be based on the bandwidth or duplexing configuration of the system. In some cases, the broadcast communication may include a MIB transmitted in a PBCH.

At block <NUM>, UE <NUM>-b may determine a scheduling parameter for a SIB based on the bandwidth or duplexing configuration of the system. In some examples, the scheduling parameter for the SIBs is determined and may be based on the frequency hopping configuration. In other examples, the scheduling parameter for the SIB may include a repetition level, a transport block size, a subframe index, a number of assigned resource blocks, or the like. For example, UE <NUM>-b may determine scheduling parameters based on a bit field in the MIB, and interpret the bit field based on the duplexing configuration and the bandwidth (i.e., the portion of the system bandwidth used for MTC communications). In some cases, the SIB may be an MTC SIB1.

At <NUM> , UE <NUM>-b may receive SIB1 according to the scheduling parameters. At <NUM>, UE <NUM>-b may receive SIB2 according to the information received in SIB1.

In some examples, a broadcast channel, such as PBCH is scheduled during the same TTI as the SIB and within the narrowband region of a system bandwidth occupied by the broadcast channel. In such cases, base station <NUM>-b may map the SIB to resources within the narrowband region based on identifying available resources of the TTI. For example, <FIG> illustrate possible scheduling schemes consistent with such mapping. In some cases, base station <NUM>-b may refrain from mapping the SIB to resources blocks within the TTI that include the broadcast channel. In some examples, the resources available for receiving the SIB may include subcarriers that exclude the broadcast channel and base station <NUM>-b may map the SIB within the TTI onto subcarriers that exclude the broadcast channel. In other examples, the resources available for receiving the SIB include available portions of subcarriers within the narrowband region, where the subcarriers include the broadcast channel, the available portions include resource elements that exclude the broadcast channel, and base station <NUM>-b may map the SIB within the TTI onto the available portions of the subcarriers.

UE <NUM>-b may identify resources available for receiving a SIB during the TTI and may monitor for the SIB within the narrowband region based on identifying the available resources. The available resources may include resource blocks of the TTI that exclude the broadcast channel. In such examples, UE <NUM>-b may monitor for the SIB on the resource blocks of the TTI that exclude the broadcast channel.

In some examples, the resources available for receiving the SIB include subcarriers of the narrowband region that exclude the broadcast channel. In such cases, UE <NUM>-b may monitor for the SIB during the TTI on the subcarriers that exclude the broadcast channel. In other examples, the resources available for receiving the SIB include available portions of subcarriers within the narrowband region and UE <NUM>-b may monitor for the SIB during the TTI on the available portions of the subcarriers. In other examples, UE <NUM>-b may identify a first set of resource elements available for a broadcast channel repetition and monitor for the SIB during the TTI on a second set of resource elements that excludes resource elements of the first set.

In some cases, monitoring for the SIB includes monitoring on resource elements of the TTI that are available for and exclude a CRS transmission. In some cases, UE <NUM>-b may refrain from monitoring resource elements available for CRS transmission.

At <NUM>, base station <NUM>-b and UE <NUM>-b may establish a Random Access Channel (RACH) link to facilitate communication via the wireless network based on information received in SIB1 and SIB2.

<FIG> shows a block diagram of a wireless device <NUM> configured for system information for eMTC in accordance with various aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a UE <NUM> described with reference to <FIG>. Wireless device <NUM> may include a receiver <NUM>, an eMTC SIB module <NUM>, or a transmitter <NUM>. Wireless device <NUM> may also include a processor. Each of these components may be in communication with each other.

The 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 for eMTC, etc.). Information may be passed on to the eMTC SIB module <NUM>, and to other components of wireless device <NUM>.

The eMTC SIB module <NUM> may determine a bandwidth or duplexing configuration for communication with a base station, determine a scheduling parameter for a SIB based on the bandwidth or duplexing configuration, and receive the SIB according to the scheduling parameter.

The transmitter <NUM> may transmit signals received from other components of wireless device <NUM>. In some examples, the transmitter <NUM> may be collocated with the receiver <NUM> in a transceiver module. The transmitter <NUM> may include a single antenna, or it may include a plurality of antennas.

<FIG> shows a block diagram of a wireless device <NUM> for system information for eMTC 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> described with reference to <FIG>. Wireless device <NUM> may include a receiver <NUM>-a, an eMTC SIB module <NUM>-a, or a transmitter <NUM>-a. Wireless device <NUM> may also include a processor. Each of these components may be in communication with each other. The eMTC SIB module <NUM>-a may also include a system properties module <NUM>, a SIB scheduling parameter module <NUM>, and a SIB monitoring module <NUM>.

The receiver <NUM>-a may receive information which may be passed on to eMTC SIB module <NUM>-a, and to other components of wireless device <NUM>. The eMTC SIB module <NUM>-a may perform the operations described with reference to <FIG>. The transmitter <NUM>-a may transmit signals received from other components of wireless device <NUM>.

The system properties module <NUM> may determine a bandwidth or duplexing configuration for communication with a base station as described with reference to <FIG>. In some examples, the bandwidth and duplexing configuration may be determined based on a broadcast communication. In some examples, the broadcast communication includes as least one of a MIB, a PSS, or an SSS.

The SIB scheduling parameter module <NUM> may determine a scheduling parameter for a SIB based on the bandwidth or duplexing configuration as described with reference to <FIG>. In some examples, the scheduling parameter for the SIB includes at least one of a repetition level, a transport block size, or a subframe index. In some examples, the scheduling parameter for the SIB includes a number of assigned resource blocks. In some examples, the SIB includes an MTC SIB1.

The SIB monitoring module <NUM> may receive the SIB according to the scheduling parameter as described with reference to <FIG>. The SIB monitoring module <NUM> may also monitor for the SIB within the narrowband region based on identifying the available resources. The SIB monitoring module <NUM> may also refrain from monitoring for the SIB during the TTI based on the determination that the broadcast channel is scheduled during the TTI. In some examples, the resources available for receiving the SIB include subcarriers of the narrowband region that exclude the broadcast channel, and monitoring for the SIB includes monitoring for the SIB during the TTI on the subcarriers that exclude the broadcast channel. In some examples, the resources available for receiving the SIB include available portions of subcarriers within the narrowband region, the subcarriers include the broadcast channel and the available portions include resource elements that exclude the broadcast channel, and monitoring for the SIB includes monitoring for the SIB during the TTI on the available portions of the subcarriers. The SIB monitoring module <NUM> may also refrain from monitoring resource elements available for CRS transmission.

<FIG> shows a block diagram <NUM> of an eMTC SIB module <NUM>-b which may be a component of a wireless device <NUM> or a wireless device <NUM> for system information for eMTC in accordance with various aspects of the present disclosure. The eMTC SIB module <NUM>-b may be an example of aspects of an eMTC SIB module <NUM> described with reference to <FIG>. The eMTC SIB module <NUM>-b may include a system properties module <NUM>-a, a SIB scheduling parameter module <NUM>-a, and a SIB monitoring module <NUM>-a. Each of these modules may perform the functions described with reference to <FIG>. The eMTC SIB module <NUM>-b may also include a MIB interpretation module <NUM>, a frequency hopping module <NUM>, a PBCH scheduling module <NUM>, and a SIB resource identification module <NUM>.

The MIB interpretation module <NUM> may receive signaling indicative of the scheduling parameter for the SIB in a broadcast communication, and determining the scheduling parameter may include interpreting the received signaling based on the determined bandwidth or duplexing configuration as described with reference to <FIG>. In some examples, the broadcast communication includes a MIB. In some examples, the signaling includes a bit field indicative of the scheduling parameter for the SIB.

The frequency hopping module <NUM> may determine a frequency hopping configuration for communication with the base station, and the scheduling parameter for the SIB may be determined based on the frequency hopping configuration as described with reference to <FIG>.

The PBCH scheduling module <NUM> may determine that a broadcast channel is scheduled during a TTI within a narrowband region of a system bandwidth as described with reference to <FIG>.

The SIB resource identification module <NUM> may identify resources available for receiving a SIB during the TTI based on the determination as described with reference to <FIG>. In some examples, the available resources include resource blocks of the TTI that exclude the broadcast channel, and monitoring for the SIB includes monitoring for the SIB on the resource blocks of the TTI that exclude the broadcast channel. The SIB resource identification module <NUM> may also identify a first set of resource elements available for a broadcast channel repetition, and monitoring for the SIB may include monitoring for the SIB during the TTI on a second set of resource elements that excludes resource elements of the first set. In some examples, monitoring for the SIB includes monitoring on resource elements of the TTI that are available for a CRS transmission. The SIB resource identification module <NUM> may identify a one or more sets of resource elements of the TTI available for a broadcast channel repetition.

<FIG> shows a diagram of a system <NUM> including a UE <NUM> configured for system information for eMTC in accordance with various aspects of the present disclosure. System <NUM> may include UE <NUM>-c, which may be an example of a wireless device <NUM>, a wireless device <NUM>, or a UE <NUM> described with reference to <FIG>, <FIG> and <FIG>. UE <NUM>-c may include an eMTC SIB module <NUM>, which may be an example of an eMTC SIB module <NUM> described with reference to <FIG>. UE <NUM>-c may also include a MTC module <NUM>. The MTC module <NUM> may enable MTC communications as described in the present disclosure. For example, MTC module <NUM> may enable narrowband communications, frequency hopping, monitoring of MTC specific system information, or other power conservation techniques. UE <NUM>-c may also include components for bi-directional voice and data communications including components for transmitting communications and components for receiving communications. For example, UE <NUM>-c may communicate bi-directionally with base station <NUM>-c.

UE <NUM>-c may also include a processor <NUM>, and memory <NUM> (including software (SW) <NUM>), a transceiver <NUM>, and one or more antenna(s) <NUM>, each of which may communicate, directly or indirectly, with one another (e.g., via buses <NUM>). The transceiver <NUM> may communicate bi-directionally, via the antenna(s) <NUM> or wired or wireless links, with one or more networks, as described above. For example, the transceiver <NUM> may communicate bi-directionally with a base station <NUM> or another UE <NUM>. The transceiver <NUM> may include a modem to modulate the packets and provide the modulated packets to the antenna(s) <NUM> for transmission, and to demodulate packets received from the antenna(s) <NUM>. While UE <NUM>-c may include a single antenna <NUM>, UE <NUM>-c may also have multiple antennas <NUM> capable of concurrently transmitting or receiving multiple wireless transmissions.

The memory <NUM> may include random access memory (RAM) and read only memory (ROM). The memory <NUM> may store computer-readable, computer-executable software/firmware code <NUM> including instructions that, when executed, cause the processor <NUM> to perform various functions described herein (e.g., system information for eMTC, etc.). Alternatively, the software/firmware code <NUM> may not be directly executable by the processor <NUM> but cause a computer (e.g., when compiled and executed) to perform functions described herein. The processor <NUM> may include an intelligent hardware device, (e.g., a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), etc.).

<FIG> shows a block diagram of a wireless device <NUM> configured for system information for eMTC in accordance with various aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a base station <NUM> described with reference to <FIG>. Wireless device <NUM> may include a receiver <NUM>, a base station eMTC SIB module <NUM>, or a transmitter <NUM>. Wireless device <NUM> may also include a processor. Each of these components may be in communication with each other.

The 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 for eMTC, etc.). Information may be passed on to the base station eMTC SIB module <NUM>, and to other components of wireless device <NUM>.

The base station eMTC SIB module <NUM> may determine a bandwidth or duplexing configuration for communication with a UE or group of UEs, determine a scheduling parameter for a SIB based on the bandwidth or duplexing configuration, and transmit the SIB according to the scheduling parameter.

<FIG> shows a block diagram of a wireless device <NUM> for system information for eMTC 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 base station <NUM> described with reference to <FIG>. Wireless device <NUM> may include a receiver <NUM>-a, a base station eMTC SIB module <NUM>-a, or a transmitter <NUM>-a. Wireless device <NUM> may also include a processor. Each of these components may be in communication with each other. The base station eMTC SIB module <NUM>-a may also include a BS system properties module <NUM>, a BS SIB scheduling parameter module <NUM>, a SIB transmission module <NUM>, a BS PBCH scheduling module <NUM>, a BS SIB resource identification module <NUM>, and a SIB mapping module <NUM>.

The receiver <NUM>-a may receive information which may be passed on to base station eMTC SIB module <NUM>-a, and to other components of wireless device <NUM>. The base station eMTC SIB module <NUM>-a may perform the operations described with reference to <FIG>. The transmitter <NUM>-a may transmit signals received from other components of wireless device <NUM>. The BS system properties module <NUM> may determine a bandwidth or duplexing configuration for communication with a UE or group of UEs as described with reference to <FIG>. The BS SIB scheduling parameter module <NUM> may determine a scheduling parameter for a SIB based on the bandwidth or duplexing configuration as described with reference to <FIG>.

The SIB transmission module <NUM> may transmit the SIB according to the scheduling parameter as described with reference to <FIG>. The BS PBCH scheduling module <NUM> may determine that a broadcast channel is scheduled during a TTI within a narrowband region of a system bandwidth as described with reference to <FIG>. The BS SIB resource identification module <NUM> may identify resources available for a SIB during the TTI based on the determination as described with reference to <FIG>.

The SIB mapping module <NUM> may map the SIB to resources within the narrowband region based on identifying available resources of the TTI as described with reference to <FIG>. The SIB mapping module <NUM> may also refrain from mapping the SIB to resources within the TTI. In some examples, the resources available for receiving the SIB include subcarriers that exclude the broadcast channel, and mapping the SIB includes mapping the SIB within the TTI onto subcarriers that exclude the broadcast channel. In some examples, the resources available for receiving the SIB include available portions of subcarriers within the narrowband region; the subcarriers may include the broadcast channel and the available portions include resource elements that exclude the broadcast channel, and mapping the SIB includes mapping the SIB within the TTI onto the available portions of the subcarriers. In some examples, mapping the SIB includes mapping the SIB onto a second set of resource elements of the TTI that excludes resource elements of the first set. In some examples, mapping the SIB includes mapping the SIB onto resource elements available for a CRS transmission. In some examples, mapping the SIB includes mapping the SIB onto resource elements excluding those available for a CRS transmission.

<FIG> shows a block diagram <NUM> of a base station eMTC SIB module <NUM>-b which may be a component of a wireless device <NUM> or a wireless device <NUM> for system information for eMTC in accordance with various aspects of the present disclosure. The base station eMTC SIB module <NUM>-b may be an example of aspects of a base station eMTC SIB module <NUM> described with reference to <FIG>. The base station eMTC SIB module <NUM>-b may include a BS system properties module <NUM>-a, a BS SIB scheduling parameter module <NUM>-a, a SIB transmission module <NUM>-a, a BS PBCH scheduling module <NUM>-a, a BS SIB resource identification module <NUM>-a, and a SIB mapping module <NUM>-a. Each of these modules may perform the functions described with reference to <FIG>. The base station eMTC SIB module <NUM>-b may also include a MIB transmission module <NUM>, and a BS frequency hopping module <NUM>.

The MIB transmission module <NUM> may transmit signaling indicative of the scheduling parameter for the SIB in a broadcast communication, such that the scheduling parameter for the SIB may be indicated based on the bandwidth or duplexing configuration as described with reference to <FIG>. In some examples, the broadcast communication includes a MIB or synchronization signals PSS or SSS. In some examples, the signaling includes a bit field indicative of the scheduling parameter.

The BS frequency hopping module <NUM> may determine a frequency hopping configuration; the scheduling parameter may be determined based on the frequency hopping configuration as described with reference to <FIG>.

<FIG> shows a diagram of a system <NUM> including a base station <NUM> configured for system information for eMTC in accordance with various aspects of the present disclosure. System <NUM> may include base station <NUM>-d, which may be an example of a wireless device <NUM>, a wireless device <NUM>, or a base station <NUM> described with reference to <FIG>, <FIG> and <FIG>. Base Station <NUM>-d may include a base station eMTC SIB module <NUM>, which may be an example of a base station eMTC SIB module <NUM> described with reference to <FIG>. Base Station <NUM>-d may also include components for bi-directional voice and data communications including components for transmitting communications and components for receiving communications. For example, base station <NUM>-d may communicate bi-directionally with UE <NUM>-d or UE <NUM>-e.

In some cases, base station <NUM>-d may have one or more wired backhaul links. Base station <NUM>-d may have a wired backhaul link (e.g., S1 interface, etc.) to the core network <NUM>. Base station <NUM>-d may also communicate with other base stations <NUM>, such as base station <NUM>-e and base station <NUM>-f via inter-base station backhaul links (e.g., an X2 interface). Each of the base stations <NUM> may communicate with UEs <NUM> using the same or different wireless communications technologies. In some cases, base station <NUM>-d may communicate with other base stations such as <NUM>-e or <NUM>-f utilizing base station communications module <NUM>. In some examples, base station communications module <NUM> may provide an X2 interface within an LTE/LTE-A wireless communication network technology to provide communication between some of the base stations <NUM>. In some examples, base station <NUM>-d may communicate with other base stations through core network <NUM>. In some cases, base station <NUM>-d may communicate with the core network <NUM> through network communications module <NUM>.

Base station <NUM>-d may include a processor <NUM>, memory <NUM> (including software (SW) <NUM>), transceiver <NUM>, and antenna(s) <NUM>, which each may be in communication, directly or indirectly, with one another (e.g., over bus system <NUM>). The transceivers <NUM> may be configured to communicate bi-directionally, via the antenna(s) <NUM>, with the UEs <NUM>, which may be multi-mode devices. The transceiver <NUM> (or other components of the base station <NUM>-d) may also be configured to communicate bi-directionally, via the antennas <NUM>, with one or more other base stations (not shown). The transceiver <NUM> may include a modem configured to modulate the packets and provide the modulated packets to the antennas <NUM> for transmission, and to demodulate packets received from the antennas <NUM>. The base station <NUM>-d may include multiple transceivers <NUM>, each with one or more associated antennas <NUM>. The transceiver may be an example of a combined receiver <NUM> and transmitter <NUM> of <FIG>.

The memory <NUM> may include RAM and ROM. The memory <NUM> may also store computer-readable, computer-executable software code <NUM> containing instructions that are configured to, when executed, cause the processor <NUM> to perform various functions described herein (e.g., system information for eMTC, selecting coverage enhancement techniques, call processing, database management, message routing, etc.). Alternatively, the software code <NUM> may not be directly executable by the processor <NUM> but be configured to cause the computer, e.g., when compiled and executed, to perform functions described herein. The processor <NUM> may include an intelligent hardware device, e.g., a CPU, a microcontroller, an ASIC, etc. The processor <NUM> may include various special purpose processors such as encoders, queue processing modules, base band processors, radio head controllers, digital signal processor (DSPs), and the like.

The base station communications module <NUM> may manage communications with other base stations <NUM>. In some cases, a communications management module may include a controller or scheduler for controlling communications with UEs <NUM> in cooperation with other base stations <NUM>. For example, the base station communications module <NUM> may coordinate scheduling for transmissions to UEs <NUM> for various interference mitigation techniques such as beamforming or joint transmission.

The components of wireless device <NUM>, wireless device <NUM>, eMTC SIB module <NUM>, system <NUM>, wireless device <NUM>, wireless device <NUM>, BS eMTC SIB module <NUM>, and system <NUM> may, individually or collectively, be implemented with at least one ASIC adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on at least one IC. In other examples, other types of integrated circuits may be used (e.g., Structured/Platform ASICs, a field programmable gate array (FPGA), or another semi-custom IC), which may be programmed in any manner known in the art. The functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.

<FIG> shows a flowchart illustrating a method <NUM> for system information for eMTC 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 with reference to <FIG>. For example, the operations of method <NUM> may be performed by the eMTC SIB module <NUM> 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 UE <NUM> to perform the functions described below. Additionally or alternatively, the UE <NUM> may perform aspects the functions described below using special-purpose hardware.

At block <NUM>, the UE <NUM> may determine a bandwidth or duplexing configuration for communication with a base station as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the system properties module <NUM> as described with reference to <FIG>.

At block <NUM>, the UE <NUM> may determine a scheduling parameter for a SIB based on the bandwidth or duplexing configuration as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the SIB scheduling parameter module <NUM> as described with reference to <FIG>.

At block <NUM>, the UE <NUM> may receive the SIB according to the scheduling parameter as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the SIB monitoring module <NUM> as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> for system information for eMTC 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 with reference to <FIG>. For example, the operations of method <NUM> may be performed by the eMTC SIB module <NUM> 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 UE <NUM> to perform the functions described below. Additionally or alternatively, the UE <NUM> may perform aspects the functions described below using special-purpose hardware. The method <NUM> may also incorporate aspects of method <NUM> of <FIG>.

At block <NUM>, UE <NUM> may receive signaling indicative of the scheduling parameter for the SIB in a broadcast communication as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the MIB interpretation module <NUM> as described with reference to <FIG>.

At block <NUM>, UE <NUM> may determine a bandwidth or duplexing configuration for communication with a base station as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the system properties module <NUM> as described with reference to <FIG>.

At block <NUM>, the UE <NUM> may determine a scheduling parameter for a SIB by interpreting the received signaling based on the bandwidth or duplexing configuration as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the SIB scheduling parameter module <NUM> as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> for system information for eMTC 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 with reference to <FIG>. For example, the operations of method <NUM> may be performed by the eMTC SIB module <NUM> 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 UE <NUM> to perform the functions described below. Additionally or alternatively, the UE <NUM> may perform aspects the functions described below using special-purpose hardware. The method <NUM> may also incorporate aspects of methods <NUM>, and <NUM> of <FIG>.

At block <NUM>, UE <NUM> may determine a frequency hopping configuration for communication with the base station. In certain examples, the operations of block <NUM> may be performed by the frequency hopping module <NUM> as described with reference to <FIG>.

At block <NUM>, the UE <NUM> may determine a scheduling parameter for a SIB based on the frequency hopping configuration or bandwidth or duplexing configuration as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the SIB scheduling parameter module <NUM> as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> for system information for eMTC 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 with reference to <FIG>. For example, the operations of method <NUM> may be performed by the eMTC SIB module <NUM> 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 UE <NUM> to perform the functions described below. Additionally or alternatively, the UE <NUM> may perform aspects the functions described below using special-purpose hardware. The method <NUM> may also incorporate aspects of methods <NUM>, <NUM>, and <NUM> of <FIG>.

At block <NUM>, the UE <NUM> may determine that a broadcast channel is scheduled during a TTI within a narrowband region of a system bandwidth as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the PBCH scheduling module <NUM> as described with reference to <FIG>.

At block <NUM>, the UE <NUM> may identify resources available for receiving a SIB during the TTI based on the determination as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the SIB resource identification module <NUM> as described with reference to <FIG>.

At block <NUM>, the UE <NUM> may monitor for the SIB within the narrowband region based on identifying the available resources as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the SIB monitoring module <NUM> as described with reference to <FIG>.

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

At block <NUM>, the base station <NUM> may determine a bandwidth or duplexing configuration for communication with a UE or group of UEs as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the BS system properties module <NUM> as described with reference to <FIG>.

At block <NUM>, the base station <NUM> may determine a scheduling parameter for a SIB based on the bandwidth or duplexing configuration as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the SIB scheduling parameter module <NUM> as described with reference to <FIG>.

At block <NUM>, the base station <NUM> may transmit the SIB according to the scheduling parameter as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the SIB transmission module <NUM> as described with reference to <FIG>.

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

At block <NUM>, the base station <NUM> may determine that a broadcast channel is scheduled during a TTI within a narrowband region of a system bandwidth as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the PBCH scheduling module <NUM> as described with reference to <FIG>.

At block <NUM>, the base station <NUM> may identify resources available for a SIB during the TTI based on the determination as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the BS SIB resource identification module <NUM> as described with reference to <FIG>.

At block <NUM>, the base station <NUM> may map the SIB to resources within the narrowband region based on identifying available resources of the TTI as described with reference to <FIG>. In certain examples, the operations of block <NUM> may be performed by the SIB mapping module <NUM> as described with reference to <FIG>.

Thus, methods <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may provide for system information for eMTC. It should be noted that methods <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> describe possible implementation, and that the operations and the steps may be rearranged or otherwise modified such that other implementations are possible. In some examples, aspects from two or more of the methods <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may be combined.

The description herein provides examples, and is not limiting of the scope, applicability, or examples set forth in the claims.

The terms "system" and "network" are often used interchangeably. IS-<NUM> Releases <NUM> and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-<NUM> (TIA-<NUM>) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A time division multiple access (TDMA) system may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), 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 Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of Universal Mobile Telecommunications System (UMTS) that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and Global System for Mobile communications (GSM) are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). The description herein, however, describes an LTE system for purposes of example, and LTE terminology is used in much of the description above, although the techniques are applicable beyond LTE applications.

In LTE/LTE-A networks, including such networks described herein, the term evolved node B (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" is a 3GPP term that can 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, eNodeB (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 modulated signal may be sent on a different sub-carrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, user data, etc. The communication links described herein (e.g., communication links <NUM> of <FIG>) may transmit bidirectional communications using frequency division duplex (FDD) (e.g., using paired spectrum resources) or TDD operation (e.g., using unpaired spectrum resources). Frame structures may be defined for FDD (e.g., frame structure type <NUM>) and TDD (e.g., frame structure type <NUM>).

A processor may also be implemented as a combination of computing devices (e.g., a combination of a digital signal processor (DSP) and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

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 list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

By way of example, and not limitation, non-transitory computer-readable media can comprise RAM, ROM, electrically erasable programmable read only memory (EEPROM), compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.

Claim 1:
A method of wireless communication performed by a user equipment, UE (<NUM>), comprising:
determining a bandwidth or duplexing configuration for communication with a base station (<NUM>);
receiving, in a broadcast communication from the base station, signaling indicative of a scheduling parameter for a system information block, SIB, wherein the signaling comprises a bit field indicative of the scheduling parameter;
interpreting the received signaling for determining the scheduling parameter for the SIB;
wherein determining the scheduling parameter for the SIB is based at least in part on a mapping that maps the bandwidth or duplexing configuration and the bit field to possible scheduling parameters comprising the scheduling parameter; and
receiving the SIB according to the scheduling parameter.