CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims the benefit of US Provisional Application No.

62/417,927 (P111789Z) filed November 4, 2016. Said Application No. 62/417,927 is hereby incorporated herein by reference in its entirety.

BACKGROUND

[0002] Evolved Multimedia Broadcast Multicast Service (eMBMS) provides an efficient way to deliver download data as well as streaming content to multiple users. Mobile video streaming especially is foreseen to generate a major volume of network data traffic in the future. Commercial deployments of eMBMS, also known as LTE Broadcast, are generating increasing interest. In order to meet the industry and operators' demand, eMBMS may be enhanced even further.

[0003] The Third Generation Partnership Project (3 GPP) is currently endeavoring to provide enhancements for television (TV) application support wherein 3 GPP networks can provide unicast and broadcast transport to support distribution of TV programs. It can support the three types of TV services including Free-to-air (FTA), Free-to- view (FTV), and Subscribed services. Each type of TV service has different requirements in order to meet regulatory obligations and public service and commercial broadcaster' s requirements regarding content distribution.

[0004] Some LTE specifications support a downlink orthogonal frequency-division multiplexing (OFDM) mode using 7.5 kHz subcarrier spacing and a long cyclic prefix (CP) of 33.3 microseconds (μ8). There is, however, no signaling defined indicating the use of this mode and hence it cannot be implemented. Even longer CP is required to support multicast-broadcast single-frequency networks (MBSFNs) with a higher spectral efficiency of two bits per second per Hertz (bps/Hz) in areas with large inter-site distances (ISDs), for example ISDs of 15 kilometers (km) or larger, in particular in low frequency bands as in the 700 MHz and 800 MHz bands and rural scenarios where indoor losses are smaller or for outdoor rooftop antennas as they are used for TV reception in many countries.

DESCRIPTION OF THE DRAWING FIGURES

[0005] Claimed subject matter is particularly pointed out and distinctly claimed in the concluding portion of the specification. However, such subject matter may be understood by reference to the following detailed description when read with the accompanying drawings in which: [0006] FIG. 1 is a diagram of a network to implement a further evolved multimedia multibroadcast system (FeMBMS) in accordance with one or more embodiments;

[0007] FIG. 2 is a diagram of a one-hundred percent multicast-broadcast single-frequency network (MBSFN) configuration including a cell acquisition subframe in accordance with one or more embodiments;

[0008] FIG. 3 is a diagram of a system information acquisition processing including a

System Information Block (SIB) Type 1 adapted for a further evolved multimedia multibroadcast system (FeMBMS) in accordance with one or more embodiments;

[0009] FIG. 4 is a diagram of a cell acquisition subframe resource block structure in accordance with one or more embodiments;

[00010] FIG. 5 illustrates an architecture of a system of a network in accordance with some embodiments;

[00011 ] FIG. 6 illustrates example components of a device in accordance with some embodiments; and

[00012] FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments.

[00013] It will be appreciated that for simplicity and/or clarity of illustration, elements illustrated in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, if considered appropriate, reference numerals have been repeated among the figures to indicate corresponding and/or analogous elements.

DETAILED DESCRIPTION

[00014] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of claimed subject matter. It will, however, be understood by those skilled in the art that claimed subject matter may be practiced without these specific details. In other instances, well-known methods, procedures, components and/or circuits have not been described in detail.

[00015] Referring now to FIG. 1, a diagram of a network to implement a further evolved multimedia multibroadcast system (FeMBMS) in accordance with one or more embodiments will be discussed. As shown in FIG. 1, network 100 may implement a further evolved multimedia multibroadcast system (FeMBMS) which is a further enhancement to an evolved multimedia multibroadcast MBMS (eMBMS) system. In such an FeMBMS system, an Evolved Universal Terrestrial Radio Access Network (EUTRAN) 110 may include one or more evolved NodeB (eNB) devices such as eNB 112 and eNB 114 operating in accordance with a Third Generation Partnership Project (3GPP) standard. In such an MB MS system implemented by network 100, the one or more eNBs such as eNB 112 and eNB 114 transmit the same content to one or more user equipment (UE) devices such as UE 116, UE 118, and UE 120 via broadcast or multicast transmission. Such an arrangement of network 100 may comprise a multicast-broadcast single - frequency network (MBSFN) in which multicast or broadcast information is transmitted to the UE devices in a synchronized manner using a single frequency by using a sufficient cyclic prefix (CP) to avoid inter-symbol interference (ISI) such that the transmissions from the multiple eNBs of EUTRAN 110 appear to be transmitted from a single cell. An example of a frame structure for an MBSFN configuration for FeMBMS systems is shown in and described with respect to FIG. 2, below.

[00016] Referring now to FIG. 2, a diagram of a one-hundred percent multicast-broadcast single-frequency network (MBSFN) configuration including a cell acquisition subframe in accordance with one or more embodiments will be discussed. The allocation of MBSFN subframes for an evolved multimedia multibroadcast system (eMBMS) system is shown in the structure of frame 200. In the current eMBMS system, allocation of MBSFN subframes 212 is limited to subframe 1, subframe 2, subframe 3, subframe 6, subframe 7, and subframe 8 of frame 200. The other subframes of frame 200 may be used for paging and/or sync paging. In some instances, there may be scenarios in which a larger allocation of MBSFN subframes 212 may be used. One such example is the use of eMBMS deployed on a supplementary downlink (SDL) carrier which may be utilized to avoid wasting uplink capacity on a frequency division duplex (FDD) uplink/downlink carrier pair. In such a scenario, eMBMS traffic may be concentrated on as few SDL carriers as possible. Such MBSFN subframes 212 for an eMBMS system have a unicast control region of one or two orthogonal frequency-division multiplexing (OFDM) symbols. These unicast control symbols, however, present a large overhead.

[00017] In one or more embodiments, a further evolved multimedia multibroadcast system (FeMBMS) may be implemented by providing a one-hundred percent configuration of MBSFN subframes 216 in frame 214 in which all subframes 0 through 9 of frame 214 are configured as MBSFN subframes 216. In such an arrangement, subframe 0 may comprise a cell acquisition subframe (CAS) subframe 218 in which system information may be transmitted as discussed in further detail herein. Details of such a CAS subframe 218 are shown in and described with respect to FIG. 4, below. The transmission of system information using CAS subframe 218 via a modified system information block (SIB) is shown in and described with respect to FIG. 3, below.

[00018] Referring now to FIG. 3, a diagram of a system information acquisition processing including a System Information Block (SIB) Type 1 adapted for a further evolved multimedia multibroadcast system (FeMBMS) in accordance with one or more embodiments will be discussed. As shown in FIG. 3, in a system information acquisition process 200, EUTRAN 110 may transmit a Master Information Block (MIB) to UE 116 at operation 310. EUTRAN 110 also may transmit a System Information Block (SIB) Typel to UE 116 at operation 312. System Information (SI) may be transmitted from EUTRAN 110 to UE 116 at operation 314. Additional SIBs may be transmitted from EUTRAN 110 to UE 116.

[00019] In one or more embodiments, the first SI may be a combination of multiple SIBs. Alternatively, information for the MBSFN carrier inside SIB1, SIB2, and SIB 13 may be provided on the FeMBMS carrier. Furthermore, SIB 15 and SIB 16 may be delivered on the FeMBMS carrier in addition to SIB10, SIB11, and SIB12. In one or more embodiments as discussed herein, a new SIB1 adapted for FeMBMS may be transmitted as SystemlnformationBlockTypel operation 312 wherein the new SIB 1 may comprise a combination of eMBMS related information included in any of the legacy SIBs such as SIB1, SIB2, SIB13, SIB15, and/or SIB16. In one embodiment, the new SIB1 includes information contained in SIB1 and SIB2 including information relevant to eMBMS. In another embodiment, the new SIB1 may include information contained in the legacy SIB1 which is relevant to eMBMS. In another embodiment, the new SIB1 may be identical or substantially identical to the legacy SIB 1. Other types of information and other combinations of system information also may be included in the new SIB1.

[00020] In one or more embodiments, to determine which information from legacy SIB messages are capable of being included in the new SIB1, the size of the legacy SIB messages may be estimated as follows. A legacy SIB1 message that only contains optional information that is relevant for the FeMBMS carrier has a size of approximately 42 bytes when describing six public land mobile networks (PLMNs) and scheduling of six different SI messages. A legacy SIB2 message that only contains optional information that is relevant for the FeMBMS carrier has a size of approximately 57 bytes when describing eight different MBSFN frame allocations. A legacy SIB13 message describing eight different MBSFN areas has a size of approximately 34 bytes. Given these estimates for the sizes of the legacy SIBs that may be included in the new SIB1, a proposed structure of a cell acquisition subframe resource block structure may be provided as discussed, below.

[00021 ] Referring now to FIG. 4, a diagram of a cell acquisition subframe resource block structure in accordance with one or more embodiments will be discussed. The resource blocks for the CAS subframe 218 are shown in FIG. 4. In one embodiment, the system information may be provided by the physical downlink shared channel (PDSCH) in one or more CAS subframes 218 transmitted in subframe 0 and used for a one-hundred percent MBSFN configuration as shown for example in FIG. 2. As shown in FIG. 4, CAS subframe 218 supports the primary synchronization signal (PSS), the secondary synchronization signal (SSS), the cell-specific reference signal (CRS), the physical broadcast channel (PBCH), the physical downlink control channel (PDCCH), and the physical downlink shared channel (PDSCH) for transmission of system information. Example resource blocks are shown, for example CRS antenna ports (APs) 0/1 resource blocks 410, CRS APs 2/3 resource blocks 412, PSS/SSS resource blocks 414, PBCH symbol 1 resource blocks 416, PBCH symbol 2 resource blocks 418, PBCH symbol 3 resource blocks 420, and PBCH symbol 4 resource blocks 422. The PDSCH resource blocks are indicated by the white resource blocks in CAS subframe 218. It should be noted that the arrangement of the resource blocks shown is merely one example, and the scope of the claimed subject matter is not limited in this respect.

[00022] In some embodiments, a system bandwidth of 1.4 MHz may be used. As illustrated in FIG. 4, by leaving aside the first two symbols for PDCCH, which is the minimum for 1.4 MHz system bandwidth, symbol 2 and symbol 3 in slot 0 and symbol 4 and symbol 5 in slot 1 are available for PDSCH transmission. Considering the CRS resource elements (REs), the total number of REs available for PDSCH is 44 per RB, which results in 264 REs over 6 RBs. Therefore, with quadrature phase-shift keying (QPSK) modulation for SI, a total 582 bits, or 66 bytes, can be transmitted in CAS PDSCH. In some embodiments, the FeMBMS carrier may be configured for a carrier bandwidth equal to or larger than 3 MHz, and in another embodiment, FeMBMS carrier may be configured for carrier bandwidth equal to or larger than 5 MHz, although the scope of the claimed subject matter is not limited in this respect.

[00023] In another embodiment, the CAS subframe 218 may indicate the presence of a periodic subframe other than a CAS subframes in which system information may be transmitted. For example, the CAS subframe 218 may indicate periodicity T and/or X, for example subframe number (SFN) mod T = X with a subframe offset Y. As an example, if T is 4, X is 1, and Y = 5, then the periodic subframe occurs every 40 milliseconds (ms) at 15 ms, 55 ms, 95 ms, and so on. In some embodiments T, X, and/or Y may be hard coded and therefore would not need to be signaled. In one embodiment, if the indicated periodic transmissions are at subframe 0 or subframe 5, the PSS/SSS may be transmitted. In another embodiment, if the indicated periodic transmissions are at subframe 0 or subframe 5, PSS/SSS may not be transmitted.

[00024] I the case of large system bandwidth, for example 10 MHz, 15 MHz, or 20 MHz, the CAS subframe 218 may not be used as there is no unicast transmission with the one-hundred percent MBSFN configuration as shown in FIG. 2. In the legacy LTE mechanism, the SI messages are transmitted within periodically occurring Si-windows and the Si-windows of different SI messages do not overlap with each other. In other words, within one Si-window only the corresponding SI is transmitted, which may be inefficient and may not be an optimal utilization of the CAS subframe 218 resource for large system bandwidth. As a result, in one embodiment, the transmission of multiple different SI messages within one CAS subframe 218 may be utilized.

[00025] With a one-hundred percent MBSFN configuration, since SI will be transmitted in CAS subframe 218, there is no need to signal SI- window related information in SIB1. Such information may include schedulinglnfoList and si_WindowLength. Instead for SIBs other than the first SI message, the scheduled periodic CAS subframe 218 may be indicated. For example, if CAS subframe 218 is transmitted SFN mod4 = 0 and the first SI is transmitted SFN mod8 = 0, then the transmission periodicity of other SIBs may be indicated as for example as SFN mod8 = 4 or SFN modl6=4, SFN modl6=12, or SFN mod32=4, and so on. Periodicity longer than 32 is also possible. Then the first SI message may indicate X and Y where SFN modX = Y, for each SIB other than the first SIB.

[00026] In one or more embodiments, the CAS subframe 218 is always transmitted in subframe 0 with a period of 40 milliseconds (ms). The master information block (MIB) may be provided by the physical broadcast channel (PBCH) in every CAS subframe 218, and the MIB may be transmitted in system frame number (SFN) mod 4 = 0 and may change in SFN mod 16 = 0. The MIB may indicate additional subframes other than the CAS subframe 218. The MIB may contain a system frame number systemFrameN umber equal to the six most significant bits of the SFN. Furthermore, in some embodiments, the first system information may be a combination of two or more SIBs, and multiple system information messages may be transmitted in the same subframe by using different radio network temporary identifiers (RNTIs).

[00027] FIG. 5 illustrates an architecture of a system of a network in accordance with some embodiments. The system 500 is shown to include a user equipment (UE) 501 and a UE 502. The UEs 501 and 502 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non- mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.

[00028] In some embodiments, any of the UEs 501 and 502 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

[00029] The UEs 501 and 502 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 510— the RAN 510 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E- UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 501 and 502 utilize connections 503 and 504, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 503 and 504 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3 GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.

[00030] In this embodiment, the UEs 501 and 502 may further directly exchange communication data via a ProSe interface 505. The ProSe interface 505 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[00031 ] The UE 502 is shown to be configured to access an access point (AP) 506 via connection 507. The connection 507 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 506 would comprise a wireless fidelity (WiFi®) router. In this example, the AP 506 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[00032] The RAN 510 can include one or more access nodes that enable the connections 503 and 504. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN 510 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 511, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 512.

[00033] Any of the RAN nodes 511 and 512 can terminate the air interface protocol and can be the first point of contact for the UEs 501 and 502. In some embodiments, any of the RAN nodes 511 and 512 can fulfill various logical functions for the RAN 510 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[00034] In accordance with some embodiments, the UEs 501 and 502 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 511 and 512 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC- FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[00035] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 511 and 512 to the UEs 501 and 502, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time- frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[00036] The physical downlink shared channel (PDSCH) may carry user data and higher- layer signaling to the UEs 501 and 502. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 501 and 502 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 511 and 512 based on channel quality information fed back from any of the UEs 501 and 502. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 501 and 502.

[00037] The PDCCH may use control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=l, 2, 4, or 8).

[00038] Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.

[00039] The RAN 510 is shown to be communicatively coupled to a core network (CN) 520 — via an SI interface 513. In embodiments, the CN 520 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the SI interface 513 is split into two parts: the Sl-U interface 514, which carries traffic data between the RAN nodes 511 and 512 and the serving gateway (S-GW) 522, and the Sl-mobility management entity (MME) interface 515, which is a signaling interface between the RAN nodes 511 and 512 and MMEs 521.

[00040] In this embodiment, the CN 520 comprises the MMEs 521, the S-GW 522, the Packet Data Network (PDN) Gateway (P-GW) 523, and a home subscriber server (HSS) 524. The MMEs 521 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 521 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 524 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 520 may comprise one or several HSSs 524, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 524 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[00041 ] The S-GW 522 may terminate the SI interface 513 towards the RAN 510, and routes data packets between the RAN 510 and the CN 520. In addition, the S-GW 522 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[00042] The P-GW 523 may terminate an SGi interface toward a PDN. The P-GW 523 may route data packets between the EPC network 523 and external networks such as a network including the application server 530 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 525. Generally, the application server 530 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 523 is shown to be communicatively coupled to an application server 530 via an IP communications interface 525. The application server 530 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 501 and 502 via the CN 520.

[00043] The P-GW 523 may further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF) 526 is the policy and charging control element of the CN 520. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 526 may be communicatively coupled to the application server 530 via the P-GW 523. The application server 530 may signal the PCRF 526 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF 526 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 530.

[00044] FIG. 6 illustrates example components of a device in accordance with some embodiments. In some embodiments, the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown. The components of the illustrated device 600 may be included in a UE or a RAN node. In some embodiments, the device 600 may include less elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 600 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud- RAN (C-RAN) implementations).

[00045] The application circuitry 602 may include one or more application processors. For example, the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 600. In some embodiments, processors of application circuitry 602 may process IP data packets received from an EPC.

[00046] The baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606. Baseband processing circuity 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606. For example, in some embodiments, the baseband circuitry 604 may include a third generation (3G) baseband processor 604 A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 604 (e.g., one or more of baseband processors 604A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 606. In other embodiments, some or all of the functionality of baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 604 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[00047] In some embodiments, the baseband circuitry 604 may include one or more audio digital signal processor(s) (DSP) 604F. The audio DSP(s) 604F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 may be implemented together such as, for example, on a system on a chip (SOC).

[00048] In some embodiments, the baseband circuitry 604 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[00049] RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 606 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604. RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission. [00050] In some embodiments, the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c. In some embodiments, the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a. RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 606a of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d. The amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c may be a low-pass filter (LPF) or band- pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 604 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[00051 ] In some embodiments, the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608. The baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.

[00052] In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super-heterodyne operation.

[00053] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to- analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.

[00054] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect. In some embodiments, the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[00055] The synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606d may be a fractional N/N+l synthesizer.

[00056] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 604 or the applications processor 602 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a lookup table based on a channel indicated by the applications processor 602.

[00057] Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[00058] In some embodiments, synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 606 may include an IQ/polar converter.

[00059] FEM circuitry 608 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing. FEM circuitry 608 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.

[00060] In some embodiments, the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606). The transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).

[00061 ] In some embodiments, the PMC 612 may manage power provided to the baseband circuitry 604. In particular, the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 612 may often be included when the device

600 is capable of being powered by a battery, for example, when the device is included in a UE.

The PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[00062] While FIG. 6 shows the PMC 612 coupled only with the baseband circuitry 604.

However, in other embodiments, the PMC 6 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.

[00063] In some embodiments, the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power. [00064] If there is no data traffic activity for an extended period of time, then the device 600 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 600 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 600 may not receive data in this state, in order to receive data, it must transition back to RRC_Connected state.

[00065] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[00066] Processors of the application circuitry 602 and processors of the baseband circuitry 604 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 604, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 604 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[00067] FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors. Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory 604G.

[00068] The baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 712 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604), an application circuitry interface 714 (e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6), an RF circuitry interface 716 (e.g., an interface to send/receive data to/from RF circuitry 606 of FIG. 6), a wireless hardware connectivity interface 718 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 720 (e.g., an interface to send/receive power or control signals to/from the PMC 612.

[00069] The following are example implementations of the subject matter described herein. It should be noted that any of the examples and the variations thereof described herein may be used in any permutation or combination of any other one or more examples or variations, although the scope of the claimed subject matter is not limited in these respects.

[00070] In example one, an apparatus of a user equipment (UE) comprises one or more baseband processors to configure a SystemlnformationBlockTypel (SIBl) message for further evolved multimedia broadcast multicast service (FeMBMS), wherein the SIBl message for FeMBMS includes eMBMS information from any one or more SIBs and wherein the SIBl message for FeMBMS information is configured in a cell acquisition subframe (CAS) subframe to be transmitted in subframe 0 of a frame configured for one -hundred percent multicast-broadcast single-frequency network (MBSFN) transmission, a memory to store the SIBl message for FeMBMS. Example two may include the subject matter of example one or any of the examples described herein, wherein the one or more baseband processors are to configure the SIB 1 message for FeMBMS to include a combination of eMBMS information from one or more eMBMS system information blocks including SIBl, SIB2, SIB13, SIB15, or SIB16, or a combination thereof. Example three may include the subject matter of example one or any of the examples described herein, wherein the SIBl message for FeMBMS is identical to the eMBMS SIBl. Example four may include the subject matter of example one or any of the examples described herein, wherein the CAS subframe indicates the presence of a periodic subframe other than the CAS subframe in which system information is to be transmitted. Example five may include the subject matter of example one or any of the examples described herein, wherein the periodic subframe has a periodicity of T or X such that SFN mod T = X with a subframe offset of Y. Example six may include the subject matter of example one or any of the examples described herein, wherein T, X, or Y, or a combination thereof are fixed. Example seven may include the subject matter of example one or any of the examples described herein, wherein the one or more baseband processors are to configure a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5. Example eight may include the subject matter of example one or any of the examples described herein, wherein the one or more base band processors are to configure a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to not be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5. Example nine may include the subject matter of example one or any of the examples described herein, wherein the one or more baseband processors are to configure multiple different system information messages to be included in one CAS subframe. Example ten may include the subject matter of example one or any of the examples described herein, wherein the one or more baseband processors are to configure the CAS subframe to not include system information window related information for the SIB1 message for FeMBMS. Example eleven may include the subject matter of example one or any of the examples described herein, wherein the one or more baseband processors are to configure the CAS subframe to include information on additional periodic subframes for system information transmission.

[00071 ] In example twelve, one or more machine-readable media may have instructions thereon that, if executed by an apparatus of a user equipment (UE), result in configuring a SystemlnformationBlockTypel (SIB1) message for further evolved multimedia broadcast multicast service (FeMBMS), wherein the SIB1 message for FeMBMS includes eMBMS information from any one or more SIBs and wherein SIB1 message for FeMBMS information is configured in a cell acquisition subframe (CAS) subframe to be transmitted in subframe 0 of a frame configured for one-hundred percent multicast-broadcast single-frequency network (MBSFN) transmission, and storing the SIB1 message for FeMBMS. Example thirteen may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configuring the SIB 1 message for FeMBMS to include a combination of eMBMS information from one or more eMBMS system information blocks including SIB1, SIB2, SIB13, SIB15, or SIB16, or a combination thereof. Example fourteen may include the subject matter of example twelve or any of the examples described herein, wherein the SIB1 message for FeMBMS is identical to the eMBMS SIB1. Example fifteen may include the subject matter of example twelve or any of the examples described herein, wherein the CAS subframe indicates the presence of a periodic subframe other than the CAS subframe in which system information is to be transmitted. Example sixteen may include the subject matter of example twelve or any of the examples described herein, wherein the periodic subframe has a periodicity of T or X such that SFN mod T = X with a subframe offset of Y. Example seventeen may include the subject matter of example twelve or any of the examples described herein, wherein T, X, or Y, or a combination thereof are fixed. Example eighteen may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configurating a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5. Example nineteen may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configuring a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to not be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5. Example twenty may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configuring multiple different system information messages to be included in one CAS subframe. Example twenty-one may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configuring the CAS subframe to not include system information window related information for the SIB1 message for FeMBMS. Example twenty-two may include the subject matter of example twelve or any of the examples described herein, wherein the instructions, if executed, further result in configuring the CAS subframe to include information on additional periodic subframes for system information transmission.

[00072] In example twenty-three, an apparatus of a user equipment (UE) comprises means for configuring a SystemlnformationBlockTypel (SIB1) message for further evolved multimedia broadcast multicast service (FeMBMS), wherein the SIB1 message for FeMBMS includes eMBMS information from any one or more SIBs and wherein SIB1 message for FeMBMS information is configured in a cell acquisition subframe (CAS) subframe to be transmitted in subframe 0 of a frame configured for one -hundred percent multicast-broadcast single-frequency network (MBSFN) transmission, and means for storing the SIB1 message for FeMBMS. Example twenty-four may include the subject matter of example twenty-three or any of the examples described herein, means for configuring the SIB1 message for FeMBMS to include a combination of eMBMS information from one or more eMBMS system information blocks including SIB1, SIB2, SIB13, SIB15, or SIB16, or a combination thereof. Example twenty-five may include the subject matter of example twenty-three or any of the examples described herein, wherein the SIB 1 message for FeMBMS is identical to the eMBMS SIB1. Example twenty-six may include the subject matter of example twenty-three or any of the examples described herein, wherein the CAS subframe indicates the presence of a periodic subframe other than the CAS subframe in which system information is to be transmitted. Example twenty-seven may include the subject matter of example twenty-three or any of the examples described herein, wherein the periodic subframe has a periodicity of T or X such that SFN mod T = X with a subframe offset of Y. Example twenty- eight may include the subject matter of example twenty-three or any of the examples described herein, wherein T, X, or Y, or a combination thereof are fixed. Example twenty-nine may include the subject matter of example twenty-three or any of the examples described herein, further comprising means for configurating a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5. Example thirty may include the subject matter of example twenty-three or any of the examples described herein, further comprising means for configuring a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) or a combination thereof to not be transmitted if a periodic subframe is configured to be transmitted as subframe 0 or subframe 5. Example thirty-one may include the subject matter of example twenty-three or any of the examples described herein, further comprising means for configuring multiple different system information messages to be included in one CAS subframe. Example thirty-two may include the subject matter of example twenty-three or any of the examples described herein, further comprising means for configuring the CAS subframe to not include system information window related information for the SIB1 message for FeMBMS. Example thirty-three may include the subject matter of example twenty-three or any of the examples described herein, further comprising means for configuring the CAS subframe to include information on additional periodic subframes for system information transmission. In example thirty-four, machine-readable storage may include machine-readable instructions, when executed, to realize an apparatus as claimed in any preceding claim.

[00073] In the description herein and/or claims, the terms coupled and/or connected, along with their derivatives, may be used. In particular embodiments, connected may be used to indicate that two or more elements are in direct physical and/or electrical contact with each other. Coupled may mean that two or more elements are in direct physical and/or electrical contact. Coupled, however, may also mean that two or more elements may not be in direct contact with each other, but yet may still cooperate and/or interact with each other. For example, "coupled" may mean that two or more elements do not contact each other but are indirectly joined together via another element or intermediate elements. Finally, the terms "on," "overlying," and "over" may be used in the following description and claims. "On," "overlying," and "over" may be used to indicate that two or more elements are in direct physical contact with each other. It should be noted, however, that "over" may also mean that two or more elements are not in direct contact with each other. For example, "over" may mean that one element is above another element but not contact each other and may have another element or elements in between the two elements. Furthermore, the term "and/or" may mean "and", it may mean "or", it may mean "exclusive-or", it may mean "one", it may mean "some, but not all", it may mean "neither", and/or it may mean "both", although the scope of claimed subject matter is not limited in this respect. In the description herein and/or claims, the terms "comprise" and "include," along with their derivatives, may be used and are intended as synonyms for each other. [00074] Although the claimed subject matter has been described with a certain degree of particularity, it should be recognized that elements thereof may be altered by persons skilled in the art without departing from the spirit and/or scope of claimed subject matter. It is believed that the subject matter pertaining to enhancements for system information transmission in further evolved multimedia broadcast multicast services and many of its attendant utilities will be understood by the forgoing description, and it will be apparent that various changes may be made in the form, construction and/or arrangement of the components thereof without departing from the scope and/or spirit of the claimed subject matter or without sacrificing all of its material advantages, the form herein before described being merely an explanatory embodiment thereof, and/or further without providing substantial change thereto. It is the intention of the claims to encompass and/or include such changes.