HK1207234B - Multicast/broadcast service continuity in multi-carrier networks - Google Patents

Description

Multicast/broadcast service continuity in multi-carrier networks

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Patent Application No. 13/531,848, filed on June 25, 2012, entitled “MULTICAST/BROADCAST SERVICE CONTINUITY IN MULTI-CARRIER NETWOR-KS,” which claims priority to U.S. Provisional Patent Application No. 61/542,086, filed on September 30, 2011, entitled “ADVANCED WIRELESS COMMUNICATION SYSTEMS AND TECH-NIQUES,” the entire disclosures of which are incorporated herein by reference.

Technical Field

Embodiments of the present invention generally relate to the field of communications, and more particularly to multicast/broadcast service continuity in wireless communication networks.

Background Art

Some wireless communication networks employ Multimedia Broadcast Multicast Services (MBMS) to broadcast media and/or other transmissions to multiple user equipments (UEs). In some cases, MBMS may only be available on some carriers in a multi-carrier network. Maintaining service continuity for UEs in such networks can be challenging.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments will be readily understood by the following detailed description taken in conjunction with the accompanying drawings. To facilitate this description, like reference numerals refer to like structural elements. The embodiments are illustrated in the figures of the accompanying drawings by way of example and not limitation.

FIG1 schematically illustrates a wireless communication network according to various embodiments.

FIG2 is a block diagram illustrating a user equipment according to various embodiments.

FIG3 is a block diagram illustrating a base station according to various embodiments.

4 is a flow chart illustrating a method for supporting a Multimedia Broadcast Multicast Service (MBMS), which may be performed by a user equipment, according to various embodiments.

FIG5 is a flow chart illustrating a method for managing MBMS services (which may be performed by a base station) according to various embodiments.

FIG6 schematically depicts an example system in accordance with various embodiments.

DETAILED DESCRIPTION

Illustrative embodiments of the present disclosure include, but are not limited to, methods, systems, computer-readable media, and apparatus for Multimedia Broadcast Multicast Service (MBMS) service continuity in a wireless communication network.

The various aspects of the illustrative embodiments will be described using the terms typically employed by those skilled in the art to convey the essence of their work to others skilled in the art. However, alternative embodiments may be practiced using only some of the described aspects, as will be apparent to those skilled in the art. For purposes of explanation, specific numbers, materials, and configurations are set forth to provide a comprehensive understanding of the illustrative embodiments. However, alternative embodiments may be practiced without the specific details, as will be apparent to those skilled in the art. In other instances, well-known features are omitted or simplified so as not to obscure the illustrative embodiments.

Furthermore, various operations will be described as multiple discrete operations in a manner that is most helpful for understanding the illustrative embodiments; however, the order of description should not be understood as implying that these operations are necessarily order-dependent. In particular, these operations do not need to be performed in the order presented.

The phrase "in some embodiments" is used repeatedly. This phrase generally does not refer to the same embodiment; however, it may refer to the same embodiment. The terms "including," "having," and "comprising" are synonymous unless the context indicates otherwise. The phrase "A and/or B" means (A), (B), or (A and B). The phrase "A/B" means (A), (B), or (A and B), similar to the phrase "A and/or B." The phrase "at least one of A, B, and C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C). The phrase "(A)B" means (B) or (A and B), i.e., A is optional.

Although specific embodiments have been illustrated and described herein, those skilled in the art will appreciate that many alternative and/or equivalent implementations may be substituted for the specific embodiments shown and described without departing from the scope of the embodiments of the present disclosure. This application is intended to cover any adaptation or variation of the embodiments discussed herein. Therefore, it is expressly intended that the embodiments of the present disclosure be limited only by the claims and their equivalents.

As used herein, a "module" may refer to, be part of, or include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.

FIG1 schematically illustrates a wireless communication network 100 according to various embodiments. The wireless communication network 100 (hereinafter “network 100”) may be an access network of a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) network, such as an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN). The network 100 may include a base station, such as an enhanced node base station (eNB) 104, configured to wirelessly communicate with a user equipment (UE).

At least initially, eNB 104 may have an established wireless connection with UE 108. Network 100 may further include one or more additional eNBs, such as eNB 112. Each of the eNBs may have substantially the same transmit power capability as the others, or alternatively, some of the eNBs may have relatively lower transmit power capabilities. For example, in one embodiment, eNB 104 may be a relatively low-power base station, such as a pico eNB, a femto eNB, and/or a home eNB (HeNB), configured to communicate with UE 108 within a first area 116, while eNB 112 may be a relatively high-power base station, such as a macro eNB, configured to communicate within a second area 120 that is larger than first area 116. In some embodiments, eNB 104 may be a closed subscriber group eNB.

2 , the UE 108 may include a communication module 224 and an MBMS module 228. The communication module 224 may further be coupled with one or more of the plurality of antennas 232 of the UE 108 for wireless communications over the network 100.

UE 108 may include any suitable number of antennas 232. In various embodiments, UE 108 may include at least as many antennas 232 as the number of simultaneous spatial layers or streams that UE 108 receives from eNBs 104 and/or 112, although the scope of the present disclosure may not be limited in this respect. The number of simultaneous spatial layers or streams may also be referred to as a transmission rank, or simply, rank.

One or more of antennas 232 may be used interchangeably as a transmit or receive antenna. Alternatively or in addition, one or more of antennas 232 may be a dedicated receive antenna or a dedicated transmit antenna.

As shown in FIG3 , eNB 104 may include a communication module 336 and an MBMS module 340 coupled to each other, at least as shown. Communication module 336 may further be coupled to one or more of a plurality of antennas 344 of eNB 104. Communication module 336 may communicate (e.g., transmit and/or receive) with one or more UEs (e.g., UE 108). In various embodiments, eNB 104 may include at least as many antennas 344 as the number of simultaneous transmit streams transmitted to UE 108, although the scope of the present disclosure may not be limited in this respect. One or more of antennas 344 may alternately function as transmit or receive antennas. Alternatively or additionally, one or more of antennas 344 may be dedicated receive antennas or dedicated transmit antennas. Alternatively or additionally, one or more of antennas 344 may alternate between communications in one or more cells 116a-c.

In some embodiments, eNB 112 may have similar modules/components as eNB 104.

In various embodiments, the MBMS module 340 of the eNB 104 may transmit the MBMS assistance information to the UE 108 via the communication module 336. In some embodiments, the MBMS assistance information may be included in a system information block (SIB) transmission. The MBMS assistance information may identify the carrier on which one or more upcoming MBMS services will be provided. In some embodiments, the MBMS assistance information may include a frequency indicator to identify the carrier. The frequency indicator may be a numerical value of the frequency of the carrier and/or an index corresponding to the carrier.

The MBMS assistance information may further include an indicator of a carrier selection mode to be used by UE 108. In some embodiments, the carrier selection mode may be a first selection mode that prioritizes carrier selection based on MBMS service, or a second selection mode that prioritizes carriers based on signal quality (e.g., regardless of whether a carrier provides MBMS service). The carrier selection mode indicator may be used to manage carrier loading. Using either selection mode, UE 108 may receive MBMS services on a best-effort basis.

For example, if there is low congestion on an MBMS bearer carrier, the carrier selection mode may be set to a first selection mode and the UE 108 may prioritize the MBMS bearer carrier if the UE 108 desires to receive MBMS services. The UE 108 may also receive unicast services on the MBMS bearer carrier. If there is high congestion, the carrier selection mode may be set to a second selection mode such that the UE 108 prioritizes carriers based on signal quality, regardless of whether the carrier transmits MBMS. In this case, the UE 108 may select an MBMS bearer carrier or a non-MBMS carrier for unicast services, for example, based on relative signal quality. For example, if the UE 108 selects an MBMS bearer carrier for unicast services and/or the UE 108 has another receiver that receives MBMS services, the UE 108 may still receive the MBMS services on a "best effort" basis.

In some embodiments, the MBMS assistance information may further include a non-MBMS restriction indicator indicating whether the carrier is restricted for non-MBMS access. If a carrier is restricted for non-MBMS access, UE 108 may receive MBMS transmissions on that carrier, but may not interact with the cell transmitting MBMS on that carrier (e.g., eNB 112). This may facilitate management of loading on the MBMS bearer carrier and/or coordination between the serving eNB (e.g., eNB 104) and the MBMS transmitting eNB (e.g., eNB 112).

In some embodiments, the MBMS assistance information transmitted by eNB 104 may include information about MBMS services being delivered by another eNB (e.g., eNB 112). In one embodiment, network 100 may include a higher-power eNB (e.g., eNB 112 in FIG. 1 ) that delivers MBMS services (in addition to providing unicast services), and a lower-power eNB (e.g., eNB 104 in FIG. 1 ) that provides unicast services but does not deliver MBMS services. UE 108 may receive MBMS assistance information from any of the eNBs in network 100, regardless of whether the eNB provides MBMS services. For example, UE 108 may receive MBMS assistance information from the serving eNB currently associated with UE 108. This may facilitate service continuity for UE 108.

In some embodiments, the MBMS assistance information may include information of multiple candidate MBMS bearer carriers, which may be transmitted by the same eNB or different eNBs.

In some embodiments, eNB 104 may transmit MBMS assistance information for MBMS services delivered by a wireless communication service provider different from the provider associated with eNB 104. For example, eNB 104 may be associated with a first provider, and eNB 112 may be associated with a second provider. The first provider may have an agreement with the second provider whereby the second provider provides MBMS services to customers of the first provider. Therefore, eNB 104 may transmit MBMS assistance information for MBMS services delivered by the second provider that are available to UE 108.

In some embodiments, the MBMS assistance information transmitted by serving eNB 104 to UE 108 regarding an MBMS service carried by another eNB (e.g., eNB 112) may also include information captured in SIB 13, as defined by LTE Release 9 and LTE Release 10. In this case, using the information obtained from serving eNB 104, UE 108 can directly find the location of the MCH on master eNB 112 and process it without reading any system information from master eNB 112.

In some embodiments, MBMS related information may be broadcast by the serving eNB 104 as an extension to SIB13 by indicating the relevance of the included information to one or more alternative carriers.

In various embodiments, UE 108 (eg, MBMS module 228 in conjunction with communication module 224) may transmit an MBMS interest indication message to eNB 104. In some embodiments, the MBMS interest indication message may be transmitted via radio resource control (RRC) signaling.

The MBMS interest indication message may include information about one or more target MBMS services that the UE wishes to receive. In some embodiments, the UE may receive an electronic service guide that includes information about upcoming MBMS services provided in the network 100. The UE may select one or more target MBMS services from the upcoming MBMS services included in the electronic service guide.

In some embodiments, the MBMS Interest Indication message may include the frequency of the individual target MBMS service. The MBMS Interest Indication message may include a Frequency field that includes the frequency of the target MBMS service. In some embodiments, multiple MBMS services may be provided on the same carrier frequency. Alternatively, if there is no target MBMS service, the Frequency field may include a null value.

In various embodiments, the MBMS Interest Indication message may include information regarding which subframes of the MBMS bearer carrier are used to deliver the MBMS service. For example, the MBMS Interest Indication message may include one or more MBMS identifiers, such as a Multicast-Broadcast Single Frequency Network (MBSFN) area identity, a Temporary Mobile Group Identity (TMGI), and/or a service identity of the target MBMS service. Alternatively, or in addition, the MBMS Interest Indication message may include Multicast Channel (MCH) information to identify the subframes of the carrier frequency on which the target MBMS service is delivered.

The eNB 104 may use the MBMS identifier and/or MCH information to determine which subframes on the carrier frequency are occupied by transmissions of the target MBMS service. The eNB 104 may make scheduling decisions and/or configure inter-frequency measurements based on the contents of the MBMS interest indication message. For example, in some embodiments, the eNB 104 may schedule other transmissions and/or measurements (e.g., inter-frequency measurements) for the UE 108 on subframes of the carrier frequency that are not used for the target MBMS service.

In some embodiments, UE 108 may use the same processor resources to process both MBMS services and unicast services. eNB 104 may take this into account when making scheduling decisions. For example, the MBMS interest indication message may indicate the percentage of UE 108's processing capacity consumed/remaining and/or expected to be consumed/remaining due to the target MBMS service. Additionally or alternatively, UE 108 may indicate how many MBMS services (e.g., one or two) it wishes to receive simultaneously.

In some embodiments, the MBMS interest indication message may include a data processing headroom information element to indicate the level of data processing capability of the UE 108. For example, the data processing headroom information element may include a Boolean value to indicate whether the UE 108 has reached a threshold data processing capability (e.g., due to MCH reception). Alternatively, the data processing headroom information element may include multiple bits to indicate how much data processing capability the UE 108 has left for unicast data.

The eNB 104 may use the data handling capability information to avoid scheduling unicast data to the UE 108 while also scheduling MBMS services that exceed the total data handling capability of the UE 108. In some embodiments, the total data handling capability may be separately signaled to the eNB 104 as part of the UE category/capability.

In some embodiments, the MBMS interest indication message may include an MBMS selection indicator to indicate whether the UE 108 is capable of receiving unicast services on the MBMS bearer carrier frequency. The eNB 104 may use this indicator to make scheduling decisions for the UE 108.

In some embodiments, the MBMS interest indication may include a priority indicator to identify the priority of the UE 108 for receiving the target MBMS service compared to receiving unicast services. In some embodiments, the priority indicator may be set by the user of the UE 108.

In some embodiments, the priority indicator may be a single bit that indicates whether the MBMS service or the unicast service is prioritized. In other embodiments, the priority indicator may include multiple bits to allow for multiple levels of priority. For example, a two-bit priority indicator may be used to indicate one of four levels of priority for the UE 108.

The four levels of priority may include a first level priority where the UE 108 will only receive MBMS services and will be disconnected from all non-MBMS services. Thus, all non-MBMS services may be released by the network 100 and the UE 108 may be considered detached from the network 100. The UE 108 may perform a reconnection procedure to reconnect to the network 100 and resume unicast services.

In the second level of priority, MBMS may be given priority while unicast is idle. Under the second level of priority, all ongoing non-MBMS services may be released by the network 100 and the UE 108 may enter idle mode. Paging messages may still be received by the UE 108 (e.g., for priority services).

In the third level of priority, MBMS may be given priority, but the UE 108 may maintain unicast services on a “best effort” basis. The network 100 may release all guaranteed bit rate (GBR) connections with the UE 108.

In the fourth level of priority, MBMS may be given a low priority (eg, unicast may be given priority over MBMS services). MBMS services (including GBR services) may be provided only when there is no impact on unicast services.

In some embodiments, one priority indicator may be provided in the MBMS Interest Indication message that applies to all of the target MBMS services included in the message.In other embodiments, the MBMS Interest Indication message may include separate priority indicators for individual target MBMS services.

In some embodiments, the MBMS Interest Indication may also indicate relative priorities among multiple target MBMS services. For example, the target services may be listed in the MBMS Interest Indication message in order of their priority.

In various embodiments, UE 108 may transmit an MBMS Interest Indication message to eNB 104 only when one or more conditions are met. For example, if the target MBMS service is not provided on any of one or more serving cells currently serving the UE, UE 108 may transmit an MBMS Interest Indication message, all of the UE's receivers are currently being used to receive transmissions from the serving cell, and unicast is enabled on the carrier frequency of the target MBMS service. If the identity and/or priority of the target MBMS service changes, UE 108 may send another MBMS Interest Indication message. Limiting the frequency of transmission of MBMS Interest Indication messages may reduce signal congestion.

Additionally or alternatively, UE 108 may send an MBMS interest indication message that includes a data processing headroom information element when the remaining data processing capability of UE 108 changes (e.g., if UE 108 stops receiving one or more MBMS transmissions). In some embodiments, UE 108 may only update eNB 104 about changes in the data processing capability of UE 108 if the change is above a threshold amount. Additionally or alternatively, a threshold may be set below which changes in processing capability are not indicated to eNB 104.

In some embodiments, one or more of the parameters indicated by the MBMS Interest Indication message may be passed from the source eNB to the target eNB during handover of the UE 108 from the source eNB to the target eNB.

FIG4 illustrates a method 400 for supporting MBMS services according to various embodiments. The method 400 may be performed by a UE (e.g., UE 108). In some embodiments, the UE may include and/or have access to one or more computer-readable media having instructions stored thereon that, when executed, cause the UE to perform the method 400.

At 404, the UE may receive MBMS assistance information from an eNB (e.g., eNB 104). In some embodiments, the MBMS assistance information may be included in a SIB transmission. The MBMS assistance information may include the frequencies of one or more MBMS carriers on which the MBMS service will be delivered, an indicator of a carrier selection mode to be used by the UE, and an indicator of whether non-MBMS access to the MBMS carriers is permitted. The carrier selection mode may be a first selection mode that prioritizes carrier selection for providing the MBMS service or a second selection mode that prioritizes carriers based on signal quality.

In some embodiments, the MBMS carrier may be transmitted by a different eNB than the one from which the UE receives MBMS assistance information. For example, the UE may receive MBMS assistance information from a serving eNB. The serving eNB may or may not transmit the MBMS carrier. In some embodiments, the serving eNB may be a relatively low-power eNB (e.g., a pico eNB and/or HeNB) and/or a closed subscriber group eNB.

At 408, the UE may receive one or more MBMS services based on the received MBMS assistance information. The UE may select one or more target MBMS services that the UE wishes to receive. For example, these target services may be selected by a user of the UE. The UE may then use the information included in the MBMS assistance information to receive the target MBMS services.

FIG5 illustrates a method 500 for managing MBMS services for a UE (e.g., UE 108) according to various embodiments. The method 500 may be performed by an eNB (e.g., eNB 104). In some embodiments, the eNB may include and/or have access to one or more computer-readable media having instructions stored thereon that, when executed, cause the UE to perform the method 500.

At 504, the eNB may receive an MBMS interest indication message from the UE, which includes information regarding a target MBMS service that the UE wishes to receive. For example, the MBMS interest indication message may include MCH information that identifies resources (e.g., subframes) of an MBMS carrier used for the target MBMS service. The MBMS interest indication message may include a frequency field that identifies the frequency of the MBMS carrier on which the target MBMS service will be transmitted. In some embodiments, the frequency field may include a null value to indicate that the target MBMS service does not exist for the UE or that the UE is no longer interested in any ongoing or upcoming MBMS services.

As discussed herein, the MBMS Interest Indication message may include additional information. For example, the MBMS Interest Indication message may include an MBSFN area identity, a TMGI, and/or a service identity of the target MBMS service. Additionally or alternatively, the MBMS Interest Indication message may include a priority indicator to identify the priority for the UE to receive the target MBMS service compared to receiving a unicast service.

As discussed herein, in some embodiments, an MBMS Interest Indication message may be sent if one or more conditions are met.The MBMS Interest Indication message may be received via RRC signaling.

The eNB may manage communications with the UE based on the MBMS interest indication message at 508. For example, the eNB may schedule transmissions and/or measurements for the UE on resources of an MBMS carrier (on which the MCH of the target MBMS service is not transmitted).

Any suitable hardware and/or software may be used to implement the eNB 104/112 and/or UE 108 described herein into a system configured as desired. For one embodiment, FIG6 illustrates an example system 600 that includes one or more processors 604, system control logic 608 coupled to at least one of the one or more processors 604, a system memory 612 coupled to the system control logic 608, a non-volatile memory (NVM)/storage device 616 coupled to the system control logic 608, a network interface 620 coupled to the system control logic 608, and an input/output (I/O) device 632 coupled to the system control logic 608.

The one or more processors 604 may include one or more single-core or multi-core processors. The one or more processors 604 may include any combination of general-purpose processors and special-purpose processors (eg, graphics processors, application processors, baseband processors, etc.).

The system control logic 608 for one embodiment may include any suitable interface controller for providing any suitable interface to at least one of the one or more processors 604 and/or any suitable device or component in communication with the system control logic 608 .

System control logic 608 for one embodiment may include one or more memory controllers for providing an interface to system memory 612. System memory 612 may be used, for example, to load and store data and/or instructions for system 600. System memory 612 for one embodiment may include any suitable volatile memory, such as, for example, a suitable dynamic random access memory (DRAM).

For example, NVM/storage 616 may include one or more tangible, non-transitory computer-readable media for storing data and/or instructions. For example, NVM/storage 616 may include any suitable non-volatile memory (e.g., flash memory) and/or may include any suitable one or more non-volatile storage devices, such as, for example, one or more hard disk drives (HDDs), one or more compact disk (CD) drives, and/or one or more digital versatile disk (DVD) drives.

NVM/storage 616 may include storage resources that are physically part of the device on which system 600 is installed, or that may be accessible to the device but not necessarily part of the device. For example, NVM/storage 616 may be accessible over a network via network interface 620 and/or through input/output (I/O) devices 632.

The network interface 620 may include a transceiver 622 for providing a radio interface for the system 600 to communicate over one or more networks and/or with any other suitable device. The transceiver 622 may implement the communication module 224. In various embodiments, the transceiver 622 may be integrated with other components of the system 600. For example, the transceiver 622 may include a processor of the one or more processors 604, a memory of the system memory 612, and an NVM/storage device 616. The network interface 620 may include any suitable hardware and/or firmware. The network interface 620 may include multiple antennas to provide a multiple-input, multiple-output radio interface. The network interface 620 of one embodiment may include, for example, a wired network adapter, a wireless network adapter, a telephone modem, and/or a wireless modem.

For one embodiment, at least one of the one or more processors 604 may be packaged together with the logic of one or more controllers of the system control logic 608. For one embodiment, at least one of the one or more processors 604 may be packaged together with the logic of one or more controllers of the system control logic 608 to form a system-in-package (SiP). For one embodiment, at least one of the one or more processors 604 may be integrated on the same die as the logic of one or more controllers of the system control logic 608. For one embodiment, at least one of the one or more processors 604 may be integrated on the same die as the logic of one or more controllers of the system control logic 608 to form a system on a chip (SoC).

In various embodiments, I/O device 632 may include a user interface designed to enable a user to interact with system 600, a peripheral component interface designed to enable peripheral components to interact with system 600, and/or a sensor designed to determine environmental conditions and/or location information related to system 600.

In various embodiments, the user interface may include, but is not limited to, a display (e.g., a liquid crystal display, a touch screen display, etc.), a speaker, a microphone, one or more cameras (e.g., a still camera and/or a video camera), a flash (e.g., an LED flash), and a keyboard.

In various embodiments, the peripheral component interface may include, but is not limited to, a non-volatile memory port, a Universal Serial Bus (USB) port, an audio jack, and a power supply interface.

In various embodiments, sensors may include, but are not limited to, gyroscope sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. The positioning unit may also be part of or interact with the network interface 620 to communicate with components of a positioning network, such as global positioning system (GPS) satellites.

In various embodiments, the system 600 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, a smartphone, etc. In various embodiments, the system 600 may have more or fewer components and/or a different architecture.

Although certain embodiments have been illustrated and described herein for purposes of illustration, many alternative and/or equivalent embodiments or implementations are contemplated for achieving the same purpose and may be substituted for the embodiments shown and described without departing from the scope of this disclosure. This application is intended to cover any adaptation or variation of the embodiments discussed herein. Therefore, it is manifestly intended that the embodiments described herein be limited only by the claims and their equivalents.

Claims (11)

1. An apparatus for use by a base station of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), the apparatus comprising: a communication module, configured to communicate with a user equipment (UE); and Multimedia Broadcast Multicast Service (MBMS) module for: transmitting, via the communication module, to the UE, system information indicating a plurality of carrier frequencies over which corresponding MBMSs of a plurality of MBMSs are to be provided, wherein the system information is included in a system information block transmission; receiving, via the communication module, an MBMS interest indication message from the UE to indicate a plurality of carrier frequencies over which the UE is currently receiving or is interested in receiving two or more of the plurality of MBMS services, wherein the MBMS interest indication message further includes a priority indicator to indicate a priority of the UE receiving the two or more MBMS services compared to a unicast service; and Information indicating how much MBMS the UE is to receive is received from the UE via the communication module. 2. The apparatus of claim 1, wherein the system information comprises numerical values of the plurality of carrier frequencies and/or indices corresponding to the plurality of carrier frequencies. 3. The apparatus of claim 1 , wherein the system information further includes an indicator of a carrier selection mode to be used by the UE, wherein the carrier selection mode is a selected one of a first selection mode that prioritizes selection of carrier frequencies for providing MBMS or a second selection mode that does not prioritize selection of carrier frequencies based on signal quality with respect to whether the corresponding carrier frequencies transmit MBMS. 4. The apparatus of any one of claims 2 to 3, further comprising: One or more antennas coupled to the communication module. 5. An apparatus employed by a user equipment (UE), the apparatus comprising: a communication module for communicating with a base station of an Evolved Universal Terrestrial Radio Access Network (E-UTRAN); and Multimedia Broadcast Multicast Service (MBMS) module for: receiving, via the communication module, system information included in a system information block from the base station, wherein the system information indicates a plurality of carrier frequencies through which corresponding MBMSs are to be provided; and An MBMS interest indication message is transmitted to the base station via the communication module to indicate a plurality of carrier frequencies through which the UE is receiving or is interested in receiving two or more of the MBMSs, wherein the MBMS interest indication message further includes a priority indicator to indicate a priority of the UE receiving the two or more MBMSs compared to a unicast service, and wherein the UE also transmits information indicating how many MBMSs the UE wants to receive. 6. The apparatus of claim 5, wherein the MBMS module is to transmit the MBMS interest indication message via radio resource control (RRC) signaling. 7. The apparatus of claim 5, wherein if the priority of the UE receiving the two or more MBMSs is changed compared to the unicast service, the MBMSs will further transmit another MBMS interest indication message to the base station via the communication module. 8. The apparatus of claim 5, wherein the priority indicator is a single bit. 9. The apparatus according to claim 5, wherein the MBMS interest indication message further comprises: An MBMS identifier of the MBMS service; or A Temporary Mobile Group Identity (TMGI) for the MBMS service. 10. The apparatus according to any one of claims 5 to 9, wherein the MBMS module is further configured to indicate capability information of the UE associated with MBMS reception to the base station via the communication module. 11. The apparatus of any one of claims 5 to 9, further comprising: At least one of a touch screen display and one or more cameras.