METHOD AND APPARATUS TO AVOID IN-DEVICE COEXISTENCE INTERFERENCE IN A WIRELESS COMMUNICATION SYSTEM

Abstract

A method and apparatus are disclosed to avoid in-device coexistence interference in a wireless communication system. In one embodiment, the method includes receiving at a user equipment (UE) a MBMS service via a Point-To-Multipoint (PTM) transmission, and initiating a Time Division Multiplexing (TDM) solution in the UE for coexistence interference avoidance, wherein the TDM solution defines one or more scheduling periods and one or more unscheduled periods, and the UE stops receiving the MBMS service via the PTM transmission when the TDM solution is initiated in the UE.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

The present Application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/438,539, filed on Feb. 1, 2011, the entire disclosure of which is incorporated herein by reference.

FIELD

This disclosure generally relates to wireless communication networks, and more particularly, to a method and apparatus to avoid in-device coexistence interference in a wireless communication system.

BACKGROUND

With the rapid rise in demand for communication of large amounts of data to and from mobile communication devices, traditional mobile voice communication networks are evolving into networks that communicate with Internet Protocol (IP) data packets. Such IP data packet communication can provide users of mobile communication devices with voice over IP, multimedia, multicast and on-demand communication services.

An exemplary network structure for which standardization is currently taking place is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput in order to realize the above-noted voice over IP and multimedia services. The E-UTRAN system's standardization work is currently being performed by the 3GPP standards organization. Accordingly, changes to the current body of 3GPP standard are currently being submitted and considered to evolve and finalize the 3GPP standard.

SUMMARY

A method and apparatus are disclosed to avoid in-device coexistence interference in a wireless communication system. In one embodiment, the method includes receiving at a user equipment (UE) a MBMS service via a Point-To-Multipoint (PTM) transmission, and initiating a Time Division Multiplexing (TDM) solution in the UE for coexistence interference avoidance, wherein the TDM solution defines one or more scheduling periods and one or more unscheduled periods, and the UE stops receiving the MBMS service via the PTM transmission when the TDM solution is initiated in the UE.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a diagram of a wireless communication system according to one exemplary embodiment.

FIG. 2 is a block diagram of a transmitter system (also known as access network) and a receiver system (also known as user equipment or UE) according to one exemplary embodiment.

FIG. 3 is a functional block diagram of a communication system according to one exemplary embodiment.

FIG. 4 is a functional block diagram of the program code of FIG. 3 according to one exemplary embodiment.

FIG. 5 is a diagram of an exemplary Time Division Multiplexing (TDM) pattern according to one exemplary embodiment.

FIG. 6 illustrates a message sequence chart to stop the Point-To-Multipoint (PIM) Multimedia Broadcast Multicast Service (MBMS) reception according to one exemplary embodiment.

FIG. 7 shows a message sequence chart to perform a Point-To-Point (PIP) MBMS service transmission according to one exemplary embodiment.

DETAILED DESCRIPTION

The exemplary wireless communication systems and devices described below employ a wireless communication system, supporting a broadcast service. Wireless communication systems are widely deployed to provide various types of communication such as voice, data, and so on. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP LTE (Long Term Evolution) wireless access, 3GPP LTE-A or LTE-Advanced (Long Term Evolution Advanced), 3GPP2 UMB (Ultra Mobile Broadband). WiMax, or some other modulation techniques.

In particular, The exemplary wireless communication systems devices described below may be designed to support one or more standards such as the standard offered by a consortium named “3rd Generation Partnership Project” referred to herein as 3GPP, including Document Nos. 3GPP TR 36.816 v1.0.0, “Study on signalling and procedure for interference avoidance for in-device coexistence (Release 10)”; R2-106399, “Potential mechanism to realize TDM pattern”; 3GPP TS 36.331. v.10.0.0. “RRC protocol specification (Release 10)”: R2-106882. “Stage-3 CR for MBMS Enhancement”: and TS 25.346 v9.1.0, “Introduction of the MBMS in the RAN; Stage 2 (Release 9)”. The standards and documents listed above are hereby expressly incorporated herein.

FIG. 1 shows a multiple access wireless communication system according to one embodiment of the invention. An access network 100 (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and an additional including 112 and 114. In FIG. 1, only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group. Access terminal 116 (AT) is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 over forward link 120 and receive information from access terminal 116 over reverse link 118. Access terminal (AT) 122 is in communication with antennas 106 and 108, where antennas 106 and 108 transmit information to access terminal (AT) 122 over forward link 126 and receive information from access terminal (AT) 122 over reverse link 124. In a FDD system, communication links 118, 120, 124 and 126 may use different frequency for communication. For example, forward link 120 may use a different frequency then that used by reverse link 118.

Each group of antennas and/or the area in which they are designed to communicate is often referred to as a sector of the access network. In the embodiment, antenna groups each are designed to communicate to access terminals in a sector of the areas covered by access network 100.

In communication over forward links 120 and 126, the transmitting antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of forward links for the different access terminals 116 and 122. Also, an access network using beamforming to transmit to access terminals scattered randomly through its coverage causes less interference to access terminals in neighboring cells than an access network transmitting through a single antenna to all its access terminals.

An access network (AN) may be a fixed station or base station used for communicating with the terminals and may also be referred to as an access point, a Node B, a base station, an enhanced base station, an eNodeB, or some other terminology. An access terminal (AT) may also be called user equipment (UE), a wireless communication device, terminal, access terminal or some other terminology.

FIG. 2 is a simplified block diagram of an embodiment of a transmitter system 210 (also known as the access network) and a receiver system 250 also known as access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

In one embodiment, each data stream is transmitted over a respective transmit antenna. TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions performed by processor 230.

The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g. for OFDM). TX MIMO processor 220 then provides N_T modulation symbol streams to N_T transmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. N_T modulated signals from transmitters 222a through 222t are then transmitted from N_T antennas 224a through 224t, respectively.

At receiver system 250, the transmitted modulated signals are received by N_R antennas 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g. filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.

An RX data processor 260 then receives and processes the N_R received symbol streams from N_R receivers 254 based on a particular receiver processing technique to provide N_T “detected” symbol streams. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 260 is complementary to that performed by TX MIMO processor 220 and TX data processor 214 at transmitter system 210.

A processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message is then processed by a TX data processor 238, which also receives traffic data for a number of data streams from a data source 236, modulated by a modulator 280, conditioned by transmitters 254a through 254r, and transmitted back to transmitter system 210.

At transmitter system 210, the modulated signals from receiver system 250 are received by antennas 224, conditioned by receivers 222, demodulated by a demodulator 240, and processed by a RX data processor 242 to extract the reserve link message transmitted by the receiver system 250. Processor 230 then determines which pre-coding matrix to use for determining the beamforming weights then processes the extracted message.

Turning to FIG. 3, this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the invention. As shown in FIG. 3, the communication device 300 in a wireless communication system can be utilized for realizing the UEs (or ATs) 116 and 122 in FIG. 1, and the wireless communications system is preferably the LIE system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling an operation of the communications device 300. The communications device 300 can receive signals input by a user through the input device 302, such as a keyboard or keypad, and can output images and sounds through the output device 304, such as a monitor or speakers. The transceiver 314 is used to receive and transmit wireless signals, delivering received signals to the control circuit 306, and outputting signals generated by the control circuit 306 wirelessly.

FIG. 4 is a simplified block diagram of the program code 312 shown in FIG. 3 in accordance with one embodiment of the invention. In this embodiment, the program code 312 includes an application layer 400, a Layer 3 portion 402, and a Layer 2 portion 404, and is coupled to a Layer 1 portion 406. The Layer 3 portion 402 generally performs radio resource control. The Layer 2 portion 404 generally performs link control. The Layer 1 portion 406 generally performs physical connections.

In order to allow users to access various networks and services ubiquitously, an increasing number of UEs are equipped with multiple radio transceivers. For example, a UE may be equipped with LIE, WiFi, Bluetooth transceivers, and Global Navigation Satellite System (GNSS) receivers. Transmissions from each of these radio transceivers may interfere with the reception by another one of these transceivers. Thus, these radio transceivers may interfere with each other's operations. 3GPP TR 36.816 v.1.0.0 (2010-11) addresses the issue of coexistence interference between multiple different radio transceivers in a UE. For example, 2.4 GHz industrial, scientific and medical (ISM) band is currently allocated for WiFi and Bluetooth channels, and 3GPP frequency bands around 2.4 GHz ISM band includes Band 40 for time division duplex (TDD) Mode and Band 7 UL for frequency division duplex (FDD) mode. Thus, the transceiver that operates with the ISM band and the transceiver that operates with the 3GPP frequency band may interfere with each other.

3GPP TR 36.816 v1.0.0 also addresses potential solutions for resolving the noted interference issue, which are Frequency Division Multiplexing (FDM) solution and Time Division Multiplexing (TDM) solution. The potential TDM solutions according to 3GPP TR 36.816 v1.0.0 are a TDM solution without UE suggested patterns and a TDM solution with the UE suggested patterns. In the TDM solution without UE suggested patterns, the UE signals the necessary information, which is also referred to as assistant information, e.g. interferer type, mode and possibly the appropriate offset in subframes, to the eNB, based on which the TDM patterns (scheduling period and/or the unscheduled period) are configured by the eNB. In the TDM solution without UE suggested patterns, UE suggests the patterns to the eNB, and it is up to the eNB to decide the final TDM patterns.

FIG. 5 shows a TDM cycle having a scheduling period and an unscheduled period. Scheduling period is a period in the TDM cycle during which the LIE UE may be scheduled to transmit or receive as shown by the TDM pattern 500. Unscheduled period is a period during which the LTE UE is not scheduled to transmit or receive as shown by the TDM pattern 500, thereby allowing the ISM radio to operate without interference. Table 1 summarizes exemplary pattern requirements for main usage scenarios:

TABLE 1
	Scheduling	Unscheduled
Usage scenarios	period (ms)	period (ms)
LTE + BT earphone	Less than [60] ms	Around [15-60] ms
(Multimedia service)
LTE + WiFi portable	No more than	No more than
router	[20-60] ms	[20-60] ms
LTE + WiFi offload	No more than	No more than
	[40-100] ms	[40-100] ms

R2-106399 proposed to adopt the Rel-8 discontinuous reception (DRX) mechanism as baseline for TDM solution. With the DRX mechanism as baseline. LTE uplink (UL) transmission and downlink (DL) reception may be performed during an Active Time and are not allowed during a sleeping time. Therefore, both UL transmission and DL reception are treated equally.

As discussed in 3GPP TS 36.331 v10.0.0, MBSFN (MBMS Single Frequency Network) subframes are pre-reserved for Point-To-Multipoint (PIM) transmissions of MBMS (Multimedia Broadcast Multicast Service) services in an MBSFN area. The PTM MBMS services are supposed to be received by all UEs in the MBSFN area. Thus, the MBSFN subframes cannot be adapted to any specific UE.

Therefore, a UE would not be able to receive a PTM MBMS service during the unscheduled period of a TDM solution active in the UE. In this situation, the MBMS service reception would be interrupted from time to time, which disrupts the user experience. As such, it does not seem proper for the UE to continue receiving an MBMS service via PTM transmission if a TDM solution is active in the UE.

To avoid disrupting the user experience, it would be better for a UE to stop receiving an MBMS service via PTM transmission on a serving cell when a TDM solution is initiated on the serving cell. In addition, the UE should not start receiving an MBMS service via PTM transmission upon session start of the MBMS service. In one embodiment, the UE would not monitor the MCCH on the serving cell. Alternatively, it is also feasible that the UE notifies the upper layers allowing the upper layers to instruct the Radio Resource Control (RRC) layer to stop receiving the MBMS service. The upper layers may do this with the consent of the user.

In one embodiment, the UE does not initiate reception of an MBMS service via PTM transmission on the serving cell if there is a TDM solution active in the UE. In another embodiment, the UE does not monitor an MCCH on the serving cell if there is a TDM solution active in the UE.

As discussed in R2-106882, the network uses a MBMS counting procedure to count the number of RRC_CONNECTED mode UEs which are receiving or interested in the specified MBMS services. If the number exceeds certain threshold, the network will start an MBMS session via p-t-m transmission, as specified in 3GPP TS 25.346 v9.1.0. Otherwise, a Point-To-Point (PTP) transmission will be used to start the MBMS session. In this situation, it would not be proper for a UE to respond to the counting if a TDM solution has been initiated in the UE because the UE would not receive an MBMS service via a PTM transmission.

On the other hand, the eNB may initiate the PTP transmission of an MBMS service to a UE interested in the MBMS service and having an active TDM solution even if the PTP transmission is being applied for the MBMS service. The eNB may initiate the PTP transmission of an MBMS service by configuring PTP radio bearer(s) to the UE for the MBMS service. This PTP transmission may be initiated or triggered due to UE request or by the eNB autonomously.

FIG. 6 illustrates a message sequence chart to stop a PIM MBMS service reception according to one exemplary embodiment. In step 610, the UE 602 is receiving a MBMS service via a PTM transmission. The eNB 604 sends a Radio Resource Control (RRC) Connection Reconfiguration message (with a TDM solution for in-device coexistence interference avoidance) to the UE 602 in step 612. Following the receipt of the RRC Connection Reconfiguration message, the UE 602 signals the RRC Connection Reconfiguration complete in step 614. In step 616, the UE stops receiving the MBMS service via PTM transmission. In addition, the UE stops monitoring the Multicast Control Channel (MCCH) in step 620.

FIG. 7 shows a message sequence chart to perform a Point-To-Point (PIP) MBMS service transmission according to one exemplary embodiment. In step 710, the PTM transmission of a MBMS service is on-going in the serving cell. The eNB 704 sends a Radio Resource Control (RRC) Connection Reconfiguration message (with a TDM solution for in-device coexistence interference avoidance) to the UE 702 in step 712. Following the receipt of the RRC Connection Reconfiguration message, the UE 702 signals the RRC Connection Reconfiguration complete in step 714. In step 716, the UE shows interest in the MBMS service. In one embodiment, the UE may send an RRC message to the eNB to show the interest. In step 718, the eNB 704 sends to the UE 702 a RRC Connection Reconfiguration message with radio bearer(s) for a PTP MBMS service transmission. Following the receipt of the RRC Connection Reconfiguration message, the UE 702 signals the RRC Connection Reconfiguration complete in step 720. In one embodiment, the UE 702 does not perform downlink reception during an unscheduled period.

Referring back to FIGS. 3 and 4, the UE 300 includes a program code 312 stored in memory 310. In one embodiment, the CPU 308 can execute the program code 312 to receive at a user equipment (UE) a MBMS service via a Point-To-Multipoint (PTM) transmission, and to initiate a Time Division Multiplexing (TDM) solution in the UE for coexistence interference avoidance, wherein the TDM solution defines one or more scheduling periods and one or more unscheduled periods, and the UE stops receiving the MBMS service via the PTM transmission when the TDM solution is initiated in the UE.

In another embodiment, the CPU 308 can execute the program code 312 (1) to have an eNB initiates a TDM solution to a UE for coexistence interference avoidance such that the TDM solution defines one or more scheduling periods as well as one or more unscheduled periods; (2) to have the eNB receives a message from the VIE such that the message indicates the UE's interest in an MBMS service that is transmitted via a PTM transmission; and (3) to have the eNB initiates a PTP transmission of the MBMS service to the UE.

The CPU 308 can also execute the program code 312 to perform all of the above-described actions and steps or others described herein.

Various aspects of the disclosure have been described above. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative. Based on the teachings herein one skilled in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein. As an example of some of the above concepts, in some aspects concurrent channels may be established based on pulse repetition frequencies. In some aspects concurrent channels may be established based on pulse position or offsets. In some aspects concurrent channels may be established based on time hopping sequences. In some aspects concurrent channels may be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.

Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of skill would further appreciate that the various illustrative logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source coding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as “software” or a “software module”), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated circuit (“IC”), an access terminal, or an access point. The IC may comprise a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute codes or instructions that reside within the IC, outside of the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

It is understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The steps of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module (e.g., including executable instructions and related data) and other data may reside in a data memory such as RAM memory, flash memory. ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. A sample storage medium may be coupled to a machine such as, for example, a computer/processor (which may be referred to herein, for convenience, as a “processor”) such the processor can read information (e.g., code) from and write information to the storage medium. A sample storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in user equipment. In the alternative, the processor and the storage medium may reside as discrete components in user equipment. Moreover, in some aspects any suitable computer-program product may comprise a computer-readable medium comprising codes relating to one or more of the aspects of the disclosure. In some aspects a computer program product may comprise packaging materials.

While the invention has been described in connection with various aspects, it will be understood that the invention is capable of further modifications. This application is intended to cover any variations, uses or adaptation of the invention following, in general, the principles of the invention, and including such departures from the present disclosure as come within the known and customary practice within the art to which the invention pertains.

Claims

1. A method for Multimedia Broadcast Multicast Service (MBMS) reception, comprising:

receiving at a user equipment (UE) a MBMS service via a Point-To-Multipoint (PTM) transmission; and

initiating a Time Division Multiplexing (TDM) solution in the UE for coexistence interference avoidance;

wherein the TDM solution defines one or more scheduling periods and one or more unscheduled periods, and

the UE stops receiving the MBMS service via the PTM transmission when TDM solution is initiated in the UE.

2. The method of claim 1, wherein the UE stops monitoring an MCCH when a TDM solution is initiated on the UE.

3. The method of claim 1, wherein the PTM transmission of the MBMS service is a transmission in Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN) mode.

4. The method of claim 1, wherein the TDM solution is configured by a Radio Resource Control (RRC) Connection Reconfiguration message.

5. The method of claim 1, wherein the UE does not perform downlink reception during the unscheduled period defined by the TDM solution.

6. A communication device for use in a user equipment (UE) of a wireless communication system, the communication device comprising:

a control circuit coupled to the first and second radios;

a processor installed in the control circuit;

a memory installed in the control circuit and coupled to the processor;

wherein the processor is configured to execute a program code stored in memory to perform: receiving at the communication device a MBMS service via a Point-To-Multipoint (PTM) transmission; and initiating a Time Division Multiplexing (TDM) solution in the communication device for coexistence interference avoidance; wherein the TDM solution defines one or more scheduling periods and one or more unscheduled periods, and the communication device stops receiving the MBMS service via the PTM transmission when the TDM solution is initiated in the communication device.

7. The communication device of claim 6, wherein the communication device stops monitoring an MCCH when a TDM solution is initiated on the communication device.

8. The communication device of claim 6, wherein the PTM transmission of the MBMS service is a transmission in Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN) mode.

9. The communication device of claim 6, wherein the TDM solution is configured by a Radio Resource Control (RRC) Connection Reconfiguration message.

10. The communication device of claim 6, wherein the UE does not perform downlink reception during the unscheduled period defined by the TDM solution.

11. A method for Multimedia Broadcast Multicast Service (MBMS) transmission comprising:

initiating by an evolved Node B (eNB) a Time Division Multiplexing (TDM) solution to a user equipment (UE) for coexistence interference avoidance, wherein the TDM solution defines one or more scheduling periods and one or more unscheduled periods,

receiving by the eNB a message from the UE, wherein the message indicates the UE's interest in an MBMS service which is being transmitted via a Point-to-MultiPoint (PTM) transmission; and

initiating by the eNB a Point-to-Point (PIP) transmission of the MBMS service to the UE.

12. The method of claim 11, wherein the TDM solution is configured by a Radio Resource Control (RRC) Connection Reconfiguration message.

13. The method of claim 11, wherein the PIM transmission of the MBMS service is a transmission in Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN) mode.

14. The method of claim 11, wherein the PTP transmission of the MBMS service is configured by a RRC Connection Reconfiguration message.