WO2014163379A1

WO2014163379A1 - Method for supporting multi-frequency mbms in view of nct carrier, and device therefor

Info

Publication number: WO2014163379A1
Application number: PCT/KR2014/002793
Authority: WO
Inventors: 안재현; 허강석; 권기범
Original assignee: 주식회사 팬택
Priority date: 2013-04-02
Filing date: 2014-04-01
Publication date: 2014-10-09
Also published as: KR20140120221A

Abstract

The present invention relates to a method for supporting a multi-frequency MBMS in a wireless communication system in view of an NCT carrier and a device therefor, characterized in that the base station according to the present invention, which supports an MBMS in a wireless communication system which supports carrier aggregation for NCT and LCT carriers, comprises a processor unit for generating MSI about a second cell using the NCT carrier and a transmission unit for transmitting the MSI on a first cell, wherein the processor unit generates an MAC CE including the MSI with regard to the MSI and the transmission unit maps the MAC CE to a PDCCH on the first cell and transmits same to a terminal.

Description

Method and device for supporting multi-frequency MBMS considering NCT carrier

The present invention relates to wireless communication, and more particularly, to a method and apparatus for supporting multi-frequency MBMS in consideration of NCT carriers in a wireless communication system.

Cellular is a concept proposed to overcome the limitations of coverage area, frequency and subscriber capacity. This is a method of providing a call right by replacing a high power single base station with a plurality of low power base stations. In other words, by dividing the mobile communication service area into several small cells, adjacent cells are assigned different frequencies, and two cells that are sufficiently far apart from each other and do not cause interference can use the same frequency band to spatially reuse frequencies. To make it possible.

The multi-component carrier system refers to a wireless communication system capable of supporting carrier aggregation (CA). Carrier aggregation is a technique for efficient use of small fragmented bands. Its effect is to combine multiple bands that are physically continuous or non-continuous in the frequency domain and use logically large bands. It is to make it. However, the CC (Component Carrier) used in the existing LTE system emphasizes the versatility of the physical layer, and since the control region redundancy and the common signal overhead still exist, the data area to be sent is reduced, resulting in spectral efficiency. Problems such as unnecessary loss in efficiency have been emphasized. Accordingly, in order to efficiently operate such a multi-carrier system, it is required to introduce a new carrier type (NCT: New Carrier Type) constituting a multi-carrier system. In the NCT, signaling for control signaling or channel estimation may be removed or reduced within a range in which there is no degradation or minimization of performance as compared to the legacy carrier type (LCT). Through this, the maximum data transmission efficiency can be obtained.

MBMS (Multimedia Broadcast / Multicast Service) is a service that transmits the same data packet from multiple base stations to multiple users at the same time, similar to the existing CBS (Cell Broadcast Service). However, while CBS is a low-speed message-based service, MBMS is intended for high-speed multimedia data transmission. In addition, CBS is not based on IP (internet protocol), but MBMS is based on IP multicast. When a certain level of users exists in the same cell, the necessary resources (or channels) are shared when they are transmitted to each user so that multiple users receive the same multimedia data to improve the efficiency of radio resources and to provide multimedia services from the user's point of view. It is an advantage of MBMS that it is available cheaply.

The MBMS uses a common channel called a multicast channel to efficiently receive data from a plurality of terminals in one service. That is, not one dedicated channel is allocated to one service data, but only one shared channel, as many as the number of terminals to receive the service in one cell. A plurality of terminals simultaneously receive the shared channel, thereby improving the efficiency of radio resources. In relation to the MBMS, the terminal may receive the MBMS after receiving system information about the corresponding cell. MBMS service is designed for LCT, but not for NCT. Currently, since the UE cannot know the information on the MBMS serviced in the NCT cell, it is difficult to correctly receive the MBMS service through the NCT cell.

An object of the present invention is to provide a method and apparatus for supporting multi-frequency MBMS considering the NCT carrier.

Another object of the present invention is to provide a method and apparatus for transmitting and receiving information on an MBMS serviced in an NCT cell in providing an MBMS service to a terminal.

Another technical problem of the present invention is to provide MBMS service related information to a terminal in consideration of an NCT carrier.

Another technical problem of the present invention is to provide a structure of a medium access control control element (MAC CE) including multicast channel (MCH) scheduling information.

Another technical problem of the present invention is to provide a MAC CE structure of a secondary LCT cell including MCH scheduling information for an MBMS serviced in an NCT cell.

Another technical problem of the present invention is to provide a MAC CE structure including MCH scheduling information for an MBMS serviced in an NCT cell and mapped to an EPDCCH of an NCT cell.

According to an aspect of the present invention, there is provided a terminal supporting a multimedia broadcast multicast service (MBMS) in a wireless communication system supporting carrier aggregation (CA). The terminal may include a receiver configured to receive MCH Scheduling Information (MSI) for MCH on a first cell; And a processor configured to control the receiver to receive the MBMS on the second cell based on the MSI, wherein the second cell is configured with a New Carrier Type (NCT) carrier, and the receiver receives the MSI. Characterized in that it is received through a medium access control (MAC) control element (MAC) relating to an MSI mapped to a physical downlink control channel (PDCCH) on one cell.

According to another aspect of the present invention, there is provided a base station supporting a multimedia broadcast multicast service (MBMS) in a wireless communication system supporting carrier aggregation (CA). The base station includes a processor for generating an MSI for a second cell and a transmitter for transmitting the multicast channel scheduling information (MSI) on a first cell, wherein the second cell is an NCT carrier. The processor unit generates a MAC CE for the MSI including the MSI, and the transmitting unit maps the MAC CE to the PDCCH on the first cell to transmit to the terminal.

According to another aspect of the present invention, there is provided a method for receiving a multimedia broadcast multicast service (MBMS) by a terminal in a wireless communication system supporting carrier aggregation (CA). The method includes receiving MCH scheduling information (MSI) for a second cell on a first cell, and performing the MBMS reception on the second cell based on the MSI. The second cell is configured with a New Carrier Type (NCT) carrier, and the MSI is included in a MAC CE and is received on the first cell.

According to the present invention, even in the case of an NCT carrier that cannot transmit system information and an RRC message, MBMS service configuration information for an NCT cell may be transmitted to a terminal through a secondary LCT cell, and an MBMS service may be provided to a terminal through the NCT cell. have.

When the terminal receives the MBMS service for the NCT cell, the terminal may receive the relevant configuration information through the auxiliary LCT, MBMS support is possible in the NCT cell.

In addition, even when the NCT cell does not support PDCCH transmission, the MAC CE regarding MCH scheduling information may be received through the secondary LCT cell, and in this case, the MAC CE is transmitted through the carrier identifier included in the MAC CE. Since the UE can determine that the MBMS service is in, it can support a smooth MBMS service through the NCT cell.

1 is a block diagram illustrating a wireless communication system.

2 shows mapping between a downlink logical channel, a downlink transport channel, and a downlink physical channel.

3 is a diagram illustrating an MBSFN based communication system to which the present invention is applied.

4 shows an example of a configuration for performing an MBMS service.

5 shows an MBMS service configuration according to an embodiment of the present invention.

6 shows a structure of a MAC message to which the present invention is applied.

7 shows an example of a MAC CE structure for an MSI including a carrier index according to the present invention.

8 shows another example of a MAC CE structure for an MSI including a carrier index according to the present invention.

9 shows a MBMS service configuration according to another example of the present invention.

10 is a flowchart of a base station supporting an MBMS service based on an NCT carrier according to the present invention.

11 is a flowchart of a terminal supporting an MBMS service based on an NCT carrier according to the present invention.

12 is a block diagram of a terminal and a base station supporting an MBMS service based on an NCT carrier according to the present invention.

Hereinafter, some embodiments will be described in detail with reference to the accompanying drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In addition, in describing the embodiments of the present specification, when it is determined that a detailed description of a related well-known configuration or function may obscure the gist of the present specification, the detailed description thereof will be omitted.

In addition, the present specification describes a wireless communication network, the operation performed in the wireless communication network is performed in the process of controlling the network and transmitting data in the system (for example, the base station) that is in charge of the wireless communication network, or the corresponding wireless Work may be done at the terminal coupled to the network.

1 is a block diagram illustrating a wireless communication system. This may be a network structure of an Evolved-Universal Mobile Telecommunications System (E-UMTS). The E-UMTS system may be referred to as Long Term Evolution (LTE) or LTE-A (Advanced) system. Wireless communication systems are widely deployed to provide various communication services such as voice, packet data, and the like.

On the other hand, there is no limitation on the multiple access scheme applied to the wireless communication system. Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier-FDMA (SC-FDMA), OFDM-FDMA, OFDM-TDMA For example, various multiple access schemes such as OFDM-CDMA may be used.

Here, the uplink transmission and the downlink transmission may use a time division duplex (TDD) scheme that is transmitted using different times, or may use a frequency division duplex (FDD) scheme that is transmitted using different frequencies. .

Referring to FIG. 1, the E-UTRAN includes at least one base station (BS) 20 that provides a control plane and a user plane to the terminal. The UE 10 may be fixed or mobile and may have other mobile stations, advanced MSs (AMS), user terminals (UTs), subscriber stations (SSs), wireless devices (Wireless Devices), and the like. It may be called a term.

The base station 20 generally refers to a fixed station communicating with the terminal 10, and includes an evolved-NodeB (eNodeB), a base transceiver system (BTS), an access point, and a femto base station. Other terms may be referred to as an eNB, a pico-eNB, a home eNB, a relay, and the like. The base station 20 may provide at least one cell to the terminal. The cell may mean a geographic area where the base station 20 provides a communication service or may mean a specific frequency band. The cell may mean a downlink frequency resource and an uplink frequency resource. Alternatively, the cell may mean a combination of a downlink frequency resource and an optional uplink frequency resource. In addition, in general, when carrier aggregation (CA) is not considered, one cell always has a pair of uplink and downlink frequency resources.

The base stations 20 may be connected to each other through an X2 interface, which is used to exchange messages between the base stations 20. The base station 20 is connected to an evolved packet system (EPS), more specifically, a mobility management entity (MME) / serving gateway (S-GW) 30 through an S1 interface. The S1 interface supports a many-to-many-relation between base station 20 and MME / S-GW 30. The PDN-GW is used to provide packet data service to the MME / S-GW 30. The PDN-GW depends on the purpose or service of communication, and the PDN-GW supporting a specific service can be found using APN information.

Referring to FIG. 2, a paging control channel (PCCH) is mapped to a paging channel (PCH), and a broadcast control channel (BCCH) is mapped to a broadcast channel (BCH) or a downlink shared channel (DL-SCH). Common Control Channel (CCCH), Dedicated Control Channel (DCCH), and Dedicated Traffic Channel (DTCH) are mapped to DL-SCH. Multicast Control Channel (MCCH) and Multicast Traffic Channel (MTCH) are mapped to Multicast Channel (MCH).

Each logical channel type is defined by what kind of information is transmitted. There are two types of logical channels: control channels and traffic channels.

The control channel is used for transmission of control plane information. BCCH is a downlink channel for broadcasting system control information. PCCH is a downlink channel that transmits paging information and is used when the network does not know the location of the terminal. CCCH is a channel for transmitting control information between the terminal and the network, and is used when the terminal does not have a radio resource control (RRC) connection with the network. The MCCH is a point-to-multipoint downlink channel used for transmitting MBMS control information, and is used for terminals receiving MBMS. The DCCH is a point-to-point one-way channel for transmitting dedicated control information between the terminal and the network, and is used by a terminal having an RRC connection.

The traffic channel is used for transmission of user plane information. DTCH is a point-to-point channel for transmitting user information and exists in both uplink and downlink. MTCH is a point-to-multipoint downlink channel for transmission of traffic data, and is used for a terminal receiving an MBMS.

Transport channels are classified according to how and with what characteristics data is transmitted over the air interface. The BCH has a predefined transmission format that is broadcast and fixed in the entire cell area. DL-SCH supports hybrid automatic repeat request (HARQ). Support for dynamic link adaptation by changing modulation, coding and transmission power, possibility of broadcast, possibility of beamforming, support for dynamic / semi-static resource allocation, and support for discontinuous reception (DRX) to save terminal power And MBMS transmission support. PCH is characterized by DRX support for terminal power saving and broadcast to the entire cell area. The MCH is characterized by broadcast to the entire cell and MBMS Single Frequency Network (MBSFN) support. MBSFN uses a common scrambling code and spreading code to simultaneously broadcast the same MBMS channel in a plurality of cells forming an MBMS cell group.

Meanwhile, the BCH is mapped to a physical broadcast channel (PBCH), the MCH is mapped to a physical multicast channel (PMCH), and the PCH and DL-SCH are mapped to a PDSCH. PBCH carries the BCH transport block, PMCH carries the MCH, and PDSCH carries the DL-SCH and PCH.

MBMS uses two logical channels. MCCH as a control channel and MTCH as a traffic channel. User data such as real voice or video is transmitted on the MTCH, and configuration information for receiving the MTCH is transmitted on the MCCH. MTCH and MCCH are a point-to-many downlink channel for a plurality of terminals, and may be referred to as a shared channel. The MBMS does not allocate radio resources as many as the number of terminals receiving a service, but allocates only radio resources for a shared channel, and simultaneously receives a shared channel from a plurality of terminals, thereby improving efficiency of radio resources.

Referring to FIG. 3, the MBSFN-based communication system 300 includes a multi-cell coordination entity (hereinafter referred to as MCE 310), an MBMS gateway (MBMS GW 315) and a base station (eNB) 320. do.

The MCE 310 is a main entity controlling the MBMS and performs a role of session management, radio resource allocation, or admission control of the base station 320 in the MBSFN region. . The MBMS gateway 315 is an entity that transmits MBMS service data and performs MBMS packet transmission and broadcast to the base station 320. MBMS gateway 315 uses Packet Data Convergence Protocol (PDCP) and Internet Protocol (IP) multicast to transmit user data to base station 320.

MBMS service may be provided by setting different MBSFN areas even though they are geographically different locations or the same location. For example, MBSFN region # 1 may support a specific MBMS service A by assigning an MBSFN subframe to frequency f1. At this time, in the MBSFN region, the MBSFN subframe may be allocated to the same frequency f1 to support the MBMS service A. For example, MBMSN region # 2 may support MBMS service A, but MBMS service A may be supported using f3 different from frequency resource f1 in MBSFN region # 1.

The MBSFN based communication system 300 uses the MBSFN subframe for providing MBMS service. For example, in FIG. 3, the second and fifth subframes from the left are MBSFN subframes, the second subframe supports MBMS service of MBSFN region # 1, and the fifth subframe supports MBMS service of MBSFN region # 2. Support. A subframe providing a general communication service other than the MBSFN is called a normal subframe separately from the MBSFN subframe.

The MBSFN subframe may be defined as a subframe that can be used to perform an MBMS service on one frequency carrier. The MBSFN subframe has a special type of slot structure for performing MBMS. For example, the MBSFN subframe uses antenna port 4 for transmission of MBSFN RS, which is a reference signal (RS) for channel estimation for PMCH transmission.

4 shows an example of a configuration for performing an MBMS service.

Referring to FIG. 4, the terminal acquires MBSFN subframe configuration information, MBSFN notification configuration information, and MBSFN area information list to perform MBMS service.

The UE may know the MBSFN subframe configuration information, that is, the location of the MBSFN subframe, through System Information Block 2 (SIB2) and RRC dedicated signaling. For example, the MBSFN subframe configuration information may be included in an MBSFN-SubframeConfig information element (IE).

In addition, the UE needs to acquire MBMS control information associated with one or more MBSFN regions capable of performing MBMS services through the system information block 13 (SIB13), and includes an MBSFN region information list and an MBMS notification. Configuration information can be obtained. The MBSFN region information list is the MBSFN region ID for each MBSFN region, the information on the MBSFN region in the MBSFN subframe in the MBSFN region, and the MBSFN subframe position where the MCCH transmission, which is the MBMS control information channel, is generated. Information may be included. For example, the MBSFN area information list may be included in the MBSFN-AreaInfoList information element. On the other hand, MBSFN notification configuration information is the configuration information for the subframe location in which the MBMS notification that informs that there is a change in the MBSFN region configuration information transmitted to the terminal through the MCCH. For example, the MBSFN notification configuration information may be included in the MBMS-NotificationConfig information element. The MBSFN notification configuration information includes time information used for change notification of the MCCH applicable to all MBSFN regions. For example, the time information may include a notification repetition coefficient (notificationRepetitionCoeff), a notification offset (notificationOffset) and a notification subframe index (notificationSF-Index). Here, the notification repetition coefficient means a common change notification repetition period for all MCCHs. The notification offset indicates an offset of a radio frame for which MCCH change notification information is scheduled. The notification subframe index is a subframe index used for transmitting an MCCH change notification on a physical downlink control channel (PDCCH).

The UE may obtain MBSFN region configuration information through the MCCH corresponding to each of the MBSFN regions obtained through SIB13. The MBSFN region configuration information may be included in the MBSFNAreaconfiguration message, and includes information on physical multicast channels (PMCHs) used by the corresponding MBSFN region. For example, the information on each PMCH includes the location of the MBSFN subframe in which the PMCH is located, Modulation and Coding Scheme (MCS) level information used for data transmission in the subframe, and the MBMS transmitted by the PMCH. Service information and the like.

UE receives MCH data through MTCH based on PMCH. Scheduling on time for the corresponding MCH data can be known through MCH Scheduling Information (MSI) coming down through PMCH. The MCH scheduling information includes information on how long the corresponding MCH data transmission lasts.

As such, the UE may receive the MBMS after receiving the system information about the corresponding cell in relation to the MBMS. The MBMS service is designed for the legacy carrier type (LCT), but in order to remove or reduce signaling for control signaling or channel estimation within a range that does not reduce or minimize performance as compared to LCT. There is no design for services in the configured new carrier type (NCT). That is, since the current UE cannot know the information on the MBMS serviced in the NCT cell, it is difficult to correctly receive the MBMS service through the NCT cell.

Hereinafter, a new carrier type (NCT) to which the technical spirit of the present invention is applied will be described in detail. When the terminal aggregates the carrier, for example, the legacy carrier type (set as the primary serving cell) and the NCT may be aggregated. In the NCT, for example, signals such as PBCH, PDCCH, PHICH, and PCFICH may not be transmitted. In the LTE-A standard, various transmission modes (TM) are defined to control the type of a multi-antenna transmission scheme, and NCT supports transmission modes (TM) 1 to 8. It may not be. That is, TM9 or TM10 may be supported in NCT. In NCT, downlink control information (DCI) formats 1A and 2D may be used for PDSCH transmission on the NCT. The DCI format 1A and / or 2D may be indicated through a PDCCH or an enhanced PDCCH (ePDCCH) on an NCT, or may be indicated through cross-carrier scheduling from an LCT.

Specifically, the NCT may include a non-standalone NCT and a macro-assisted standalone NCT.

First, a non-standalone NCT carrier may mean an NCT carrier associated with an LCT carrier. That is, the non-standalone NCT carrier may mean a carrier that can be connected as a secondary serving cell (Scell) in a situation where the UE is connected to the LCT carrier as a primary serving cell (Pcell). In other words, the UE cannot be connected using the non-standalone NCT carrier as the main serving cell.

Non-standalone NCT carriers can be classified into a synchronous (synchronized) NCT carrier and an unsynchronized NCT carrier.

A synchronous NCT carrier refers to an NCT carrier that operates by referring to synchronization of another carrier (eg, LCT carrier). In other words, the synchronous NCT carrier may be synchronized with other carriers in time and frequency so that a separate synchronization procedure is not required at the terminal. The synchronous NCT carrier may not include PSS, SSS, and CRS (or TRS). This allows for overhead reduction of common RSs. In the synchronous NCT carrier, due to the overhead reduction, there may be advantages such as interference mitigation, energy saving, and improved spectral efficiency for neighboring cells. As a result, network providers can utilize frequency bands more flexibly.

An asynchronous NCT carrier refers to an NCT carrier capable of acquiring and operating independent synchronization regardless of other carriers (eg, LCT carriers). In this case, the asynchronous NCT carriers transmit PSS and SSS in the same manner as the legacy carrier type, but the CRS transmission frequency may be low. For example, in an asynchronous NCT carrier, the CRS may be transmitted with a certain period and / or a predetermined bandwidth, in which case the CRS may be called a reduced CRS or a tracking RS. In more detail, for example, the TRS has a 5 ms period on a time axis and may be transmitted based on the CRS antenna port 0. The TRS may be transmitted in the entire system band on the frequency axis, or may be transmitted only in some system bands. Meanwhile, even in this case, the CSI-RS may be transmitted.

Second, the macro-assisted standalone NCT carrier refers to a carrier that can be connected as a main serving cell, unlike the non-standalone NCT carrier. However, even in this case, it may be limited differently from an LCT cell configured with an LCT carrier in system information for cell operation or signaling for radio resource control. The macro auxiliary standalone NCT carrier may be referred to as a standalone NCT carrier.

In order for the NCT-based wireless communication system to normally support the MBSFN, the MBSFN subframe is provided on the NCT. The MBMS service on the NCT is transmitted through an MBSFN subframe, and signaling information similar to that of the MBMS service on a backward compatible carrier type (BCCT) is required. However, due to the characteristics of the NCT, the structure of the MBSFN subframe on the NCT is different from that of the MBSFN subframe of the BCCT. In addition, other NCT-specific operations, for example, signaling structures and signaling methods, must be different from those of the existing MBSFN.

Hereinafter, the MBMS service configuration for the NCT carrier according to the present invention is as follows.

1. When a UE receives MBMS service configuration information for an NCT carrier in a connected mode

5 shows an MBMS service configuration according to an embodiment of the present invention. 5 illustrates an example in which a UE receives MBMS service configuration information on an NCT carrier in a connected mode and a PDCCH cannot be transmitted on an MBSFN subframe of an NCT carrier. Instead, transmission of EPDCCH (EPDCCH) is allowed on the MBSFN subframe of the NCT carrier. The MBMS service configuration information includes at least one of MBSFN subframe configuration information, MBSFN notification configuration information, and MBSFN area information list required to perform the MBMS service. Hereinafter, the LCT cell or the NCT cell transmitting information or a message to the terminal means that the LCT cell or the base station configuring the NCT cell transmits the information or message to the terminal through the LCT cell or the NCT cell. Can be. In addition, the following LCT cell may be represented by the LCT carrier, NCT cell may be represented by the NCT carrier.

Referring to FIG. 5, the assisting LCT cell transmits an RRC connection reconfiguration message including MBMS service configuration information for the NCT cell to the terminal (S500). In other words, the secondary LCT cell performs cross-carrier configuration for MBMS service for the NCT cell. Here, the secondary LCT cell refers to an LCT cell that assists the NCT cell. For example, when the carrier aggregation (CA) is configured in the terminal, the secondary LCT cell may mean an LCT cell that is a main serving cell. In another example, it may mean a macro LCT cell that assists macro-assisted stand-alone NCT. In this case, the secondary LCT cell and the NCT cell may be configured in the same base station or may be configured in different base stations.

In more detail, the RRC connection reconfiguration message may include, for example, at least one of MBSFN subframe configuration information, MBSFN notification configuration information, and MBSFN region information list for an NCT carrier. For example, at least one of the MBSFN subframe configuration information, the MBSFN notification configuration information, and the MBSFN region information list is broken into an information element for adding a secondary cell (Scell) in an RRC connection reconfiguration message. It may be included as one component of a cell or may be included in another information element. Specifically, for example, as shown in Table 1 below, the RRC connection reconfiguration message may include a ScellToAddMod field, and the ScellToAddMod field may include a radioResourceConfigCommonScell subfield. At least one of the MBSFN subframe configuration information, the MBSFN notification configuration information, and the MBSFN region information list may be information included in the radioResourceConfigCommonScell subfield.

Table 1

On the other hand, since the secondary LCT cell performs cross-carrier configuration (MB) service for the MBMS service for the NCT cell, in this case, the classification of the corresponding NCT carrier should be performed. That is, an indicator for identifying the corresponding NCT carrier may be included in the RRC connection reconfiguration message.

For example, based on the notificationIndicator information allocated to the MBSFN region of the NCT carrier, the corresponding NCT carrier can be distinguished.

TABLE 2

Referring to Table 2, the MBSFN-AreaInfolList information element includes an MBSFN AreaInfo field, and the MBSFN AreaInfo field includes notificationIndicator information. The value configured in the notificationIndicator information indicates a bit position in the PDCCH that notifies the MCCH change. The PDCCH may contain 8-bit bitmap information. For example, if the notificationIndicator information is set to 0 for one MBSFN region, information corresponding to the first bit of the 8-bit bitmap indicates an MCCH change notification of the region. Therefore, when NCT carriers are divided and allocated based on the corresponding bits, confusion may be avoided in MCCH change notification between carriers. That is, the NCT carriers can be distinguished by allocating some of the 8 bits to the LCT carriers and allocating the rest to the NCT carriers. Specifically, for example, in the LCT carrier, if the

values

0, 1, 2, and 3 are set as values of the notificationIndicator information for four MBSFN regions, the network selects any one of the remaining values of 4 to 7 for the NCT carrier. The MBSFN region corresponding to the NCT carrier may be set by selecting.

As another example, an MBSFN carrier index may be assigned to an NCT carrier. That is, the RRC connection reconfiguration message may include an MBSFN carrier index. The index may mean an index for carriers providing MBMS service in an eNB providing a service to a UE. Considering Carrier Aggregation (CA), the MBSFN carrier index may be any one of values corresponding to 0 to 7. FIG. In this case, the number of carriers capable of performing MBMS for one UE may be up to eight. However, the MBSFN carrier index is not limited to a value corresponding to 0 to 7, and the range of the index may be defined differently in consideration of the service situation in the system.

The secondary LCT cell transmits the PDCCH including the MBMS notification to the terminal (S510). In this embodiment, since the NCT cell cannot transmit the PDCCH to the terminal, the secondary LCT cell may transmit the PDCCH including the MBMS notification for the corresponding NCT cell to the terminal through cross-carrier scheduling. The PDCCH may be configured by MBMS-Radio Network Temporary ID (M-RNTI). At this time, the UE monitors the PDCCH scrambled with the M-RNTI in the common search space. In this case, the MBMS notification has occurred, indicating that there is a change in the MBSFN region configuration (information).

The NCT cell transmits the MCCH including the MBSFN region configuration information to the terminal (S520). The MBSFN region configuration message is transmitted in a subframe configured by the MCCH configuration information included in the MBSFN region information list. The MBSFN region configuration message may include PMCH configuration information and the like in the MBSFN region.

Meanwhile, in order for the terminal to receive the MBMS service, MCH scheduling information (MSI) must be further transmitted to the terminal. The MSI includes a duration of the MBMS service data transmission configured on each MTCH transmitted on the MBSFN subframe set by the PMCH configuration. The MBSFN subframe may carry MBMS service data, PMCH or MTCH, and MTCH is a point-to-multipoint downlink logical channel for transmission of traffic data, which is used for a terminal receiving an MBMS service. That is, the terminal receives PMCH information for receiving the MTCH, which is the traffic channel, through the MCCH, the MBMS control channel received in S520, and based on this, scheduling information (ie, MSI) for MBMS service data mapped to the MTCH. Can be obtained. The MSI may be included in a MAC message, specifically, a MAC CE (Medium Access Control Control Element), and may be transmitted to the terminal. It can be set so that they do not overlap. In this case, the information about the LCID may be included in the PMCH configuration information and transmitted to the terminal.

The MAC message including the MAC CE carrying the MSI may be configured as follows, for example.

6 shows a structure of a MAC message to which the present invention is applied.

Referring to FIG. 6, the MAC message 600 includes a MAC header 610, at least one

MAC CE

620, 625, and at least one MAC Service Data Unit (SDU). 630-1,..., 630-m and padding 640.

The MAC header 610 includes at least one subheader 610-1, 610-2,..., 610-k, each subheader 610-1, 610-2 ... .610-k corresponds to one MAC SDU or one MAC CE 620,..., 625 or padding 640. The order of subheaders 610-1, 610-2,..., 610-k is corresponding MAC SDU, MAC CE 620,..., 625 or padding 640 in MAC message 600. They are arranged in the same order.

Each subheader 610-1, 610-2, ..., 610-k contains four fields: R, R, E, LCID, or 6 R, R, E, LCID, F, L Field may be included. Subheaders containing four fields are subheaders corresponding to MAC CE 620, ..., 625 or padding 640, and subheaders containing six fields are subheaders corresponding to MAC SDU.

The LCID field is an identification field for identifying a logical channel corresponding to a MAC SDU, or for identifying a type of padding or a CE CE (620, ..., 625), and each subheader 610-1, 610-2. When ..., 610-k) has an octet structure, the LCID field may be 5 bits.

MAC CE (620, ..., 625) is a control message generated by the MAC layer. Padding 640 is a predetermined number of bits added to make the size of the MAC message constant. The MAC control elements 620,... 625, MAC SDUs 630-1,..., 630-m, and padding 640 together are also referred to as MAC payloads.

The MSI according to the present invention may be included in at least one of the above MAC CE (620, ..., 625), in this case, the terminal through the at least one of the two alternatives (alternative) as follows: It may receive a containing MAC CE.

First, referring back to FIG. 5, the secondary LCT cell transmits a MAC CE including MCH scheduling information (MSI) for the NCT cell to the terminal (S530-1). This is a case where the secondary LCT cell transmits the MAC CE including the MSI for the corresponding NCT cell to the terminal through cross carrier scheduling. In this case, it should inform the terminal that the MAC CE is for the corresponding NCT cell.

For example, the UE may indicate that the corresponding MAC CE is a MAC CE for the NCT cell through a Carrier Indication Field (CIF) of the PDCCH indicating the MAC CE in the secondary LCT cell. The CIF of the PDCCH means an index of a cell referred to by the corresponding PDCCH. When cross carrier scheduling is introduced, the CIF includes one cell including an index of a cell to include scheduling information of another cell in the PDCCH.

As another example, the LCID value of the MAC CE may be configured to form a division according to a carrier. That is, the LCID value may be given differently for each carrier according to the setting in step S500. In this case, the UE may know which carrier indicates the MTCH of the MSI based on the LCID value included in the MAC CE, and may determine whether the MS is the MAC CE for the corresponding NCT cell (or MTCH).

As another example, a new MAC CE may be configured. The MAC CE is a MAC CE for the MSI and may further include a carrier index. The MAC CE may be referred to as a MAC CE for an MSI including a carrier index. In this case, for example, as shown in Table 3, the MAC CE refers to an MSI including a carrier index. It may be identified whether the MAC CE.

TABLE 3

Index	LCID value (vlaue)
00000	MCCH
00001-11100	MTCH
11101	MSI (MCH Scheduling Information with carrier index)
11110	MCH Scheduling Information (MSI)
11111	Padding

Referring to Table 3, if the index of the LCID field is 11101, the corresponding MAC CE indicates the MAC CE for the MSI including the carrier index. In this case, the LCID index 11101 may be used as another LCID index to indicate the MAC CE for the MSI including the carrier index. If there is no MCCH in the MCH (not mapped), the MTCH may further use the LCID index 00000.

Meanwhile, an E-UTRA Absolute Radio Frequency Channel Number (EARFCN) value may be used as the carrier index included in the MAC CE of the MSI including the carrier index.

7 shows an example of a MAC CE structure for an MSI including a carrier index according to the present invention. 7 is a case where an EARFCN value is used as the carrier index.

Referring to FIG. 7, a MAC CE for an MSI including a carrier index includes an LCID field, a Stop MTCH field, and an EARFCN field. The EARFCN field may be called a carrier identifier field.

Where the LCID field indicates the logical channel ID of the MTCH (signaled in the upper layer). The length of the LCID field may be 5 bits.

The Stop MTCH field indicates the ordinal number of the subframe within the MCH scheduling period. In this case, the ordinal counts only in the subframe allocated to the MCH (corresponding MTCH is stopped). A value 0 of the Stop MTCH field corresponds to the first subframe. The length of the Stop MTCH field may be 11 bits. The Stop MTCH field may, for example, have a value of 2047 and indicate that a corresponding MTCH is not scheduled.

The EARFCN field represents a carrier identifier. The EARFCN field may indicate a carrier (eg, an NCT carrier) targeted by the MSI. The EARFCN may include two octets assuming 16 bits of information (ie, 0,..., 2047). If the extended EARFCN is assumed, the corresponding number of bits can be larger.

Alternatively, an MBSFN carrier index value may be used as the carrier index included in the MAC CE including a carrier index.

8 shows another example of a MAC CE structure for an MSI including a carrier index according to the present invention. 8 illustrates a case in which an MBSFN carrier index value is used as the carrier index.

Referring to FIG. 8, a MAC CE for an MSI including a carrier index includes an LCID field, a Stop MTCH field, and an MBSFN carrier index field. The MBSFN carrier index field may be called a carrier identifier field.

The MBSFN carrier index field indicates a carrier identifier. The MBSFN carrier index may be signaled to the terminal in step S500, for example. Assuming that the MBSFN carrier index is 8-bit information (ie, 0,... 127), it may include one octet. However, as an example, in some cases, the MBSFN carrier index may include more or less bit information.

Referring back to FIG. 5, as a second method for transmitting to the UE of the MAC CE including the MSI, when the NCT cell supports the EPDCCH, the NCT cell transmits the MAC CE including the MSI to the UE through the EPDCCH. It may be (S530-2). In this case, since the MAC CE is transmitted to the terminal on the corresponding NCT cell (carrier), there is no need for a separator to separate a separate carrier. Therefore, the MAC CE structure of the existing MSI can be used as it is.

Thereafter, the terminal may receive an MBMS service through the NCT cell (S540). The terminal may receive the MBMS service on the NCT cell including user data such as voice or video.

Although S510, S520, and S530 are shown to be sequentially performed in FIG. 5, this is merely an example, and S510, S520, and S530 may be performed simultaneously or in any other order. Or in some cases, the S510 may be omitted.

2. When the UE receives the MBMS service configuration information for the NCT carrier in the idle mode as well as the connection mode

In some cases, the UE may need to receive all or part of the MBMS service through the NCT carrier in not only a connected mode but also an idle mode. In order to support this, the present invention can be performed by the following MBMS service related signaling structure and method.

9 shows a MBMS service configuration according to another example of the present invention. 9 shows an example in which the UE may receive MBMS service configuration information for an NCT cell not only in a connected mode but also in a dormant mode, and a PDCCH may not be transmitted on an MBSFN subframe of an NCT carrier. Instead, transmission of the EPDCCH is allowed on the MBSFN subframe of the NCT carrier.

Referring to FIG. 9, the secondary LCT cell transmits MBSFN subframe configuration information among MBMS service configuration information for the NCT cell to the terminal through SIB2 (S900), and the MBSFN notification configuration information and the MBSFN region information list are transmitted through the SIB13 terminal. To transmit (S905).

In this case, since the secondary LCT cell performs cross-carrier configuration for the MBMS service for the NCT cell, it should be distinguished whether the MBSFN subframe configuration information included in the SIB2 is for the NCT carrier and included in the SIB13. It should be distinguished whether the MBSFN notification configuration information and the MBSFN region information list are for NCT carriers. In other words, the classification of the corresponding NCT carrier should be performed through the delimiter.

First, a separator for an NCT carrier of MBSFN subframe configuration information included in SIB2 may be needed.

As an example of the delimiter, an EARFCN value may be signaled. The carrier frequency is designed by the EARFCN value. Based on the EARFCN value, the MBSFN subframe configuration may indicate to which frequency the EARFCN value is applied. Based on this, the UE may distinguish a corresponding NCT carrier.

As another example of the separator, the MBSFN carrier index value may be indicated. In this case, the MBSFN carrier index value may be signaled together with the EARFCN value to indicate what frequency the MBSFN carrier index means. The MBSFN carrier index may mean an index for carriers providing MBMS service in an eNB that provides a service to a UE.

Next, a separator may be needed for the NSF carrier of the MBSFN notification configuration information and MBSFN region information list included in SIB13.

According to one embodiment of the NCT carrier identifier for the MBSFN notification configuration information, the same may be applied to all MBSFN regions signaled by SIB13. In this case, no separate delimiter is applied.

In another embodiment of the NCT carrier identifier for the MBSFN notification configuration information, the separator may be given differently for each carrier. In this case, the EARFCN value may be used as a separator, and the MBSFN carrier index signaled through SIB2 in S900 may be used.

In addition, as an example of the NCT carrier identifier for the MBSFN region information list, the EARFCN value may be used, and in this case, the MBSFN carrier index signaled through SIB2 in S900 may be used.

The remaining steps S910, S920, S930 (S930-1, S930-2) and S940 may be performed in the same manner as the procedures of S510, S520, S530 (S530-1, S530-2) and S540 in FIG. Is omitted.

Although S900 and S905 are illustrated as being sequentially performed in FIG. 9, this is only an example and S900 and S905 may be performed simultaneously, and S905 may be performed before S900.

According to the present invention described above, even in the case of an NCT carrier that cannot transmit system information and an RRC message, MBMS service configuration information for an NCT cell is transmitted to a terminal through a secondary LCT cell, and the terminal provides an MBMS service through the NCT cell. Can be provided.

10 is a flowchart of a base station supporting an MBMS service based on an NCT carrier according to the present invention. 10 illustrates a case where an NCT cell and a secondary LCT cell are CAs in the same base station.

Referring to FIG. 10, the base station transmits MBMS service configuration information for the NCT cell (or for the NCT cell) on the secondary LCT cell, that is, the MBSFN subframe configuration information, the MBSFN notification configuration information, and the MBSFN region information list to the terminal. (S1000).

For example, the base station may transmit the MBSFN subframe configuration information, the MBSFN notification configuration information and the MBSFN region information list to the terminal through an RRC connection reconfiguration message on a secondary LCT cell. In this case, the terminal may receive the MBMS service configuration information in the RRC connection mode. In this case, it is possible to distinguish whether the information is on the corresponding NCT carrier based on notificationIndicator information allocated to the MBSFN region of the NCT carrier, or whether the information is on the corresponding NCT carrier based on the MBSFN carrier index.

As another example, the base station may transmit the MBSFN subframe configuration information to the terminal through SIB2 on the secondary LCT cell, and transmit the MBSFN notification configuration information and the MBSFN region information list to the terminal through SIB13. In this case, the UE may receive the MBMS service configuration information not only in the RRC connection mode but also in the idle mode. In the case of MBSFN subframe configuration information, whether the information on the corresponding NCT carrier can be distinguished based on the EARFCN value, or whether the information on the corresponding NCT carrier can be distinguished based on the MBSFN carrier index. In the case of MBSFN notification configuration information, it may be applied to all the signaled MBSFN regions in the same manner, or may be applied differently for each carrier based on the EARFCH value to distinguish whether it is information on a corresponding NCT carrier. The MBSFN region information list may be classified as information on the corresponding NCT carrier based on the EARFCN value or the MBSFN carrier index.

The base station transmits the PDCCH including the MBMS notification for the NCT cell to the terminal on the secondary LCT cell (S1010). In this case, even when the PDCCH transmission is not allowed on the MBSFN subframe of the NCT cell, the base station may transmit (ie, cross-carrier scheduling) the PDCCH including the MBMS notification for the NCT cell on the secondary LCT cell.

When the MBMS notification occurs, the base station may perform PDCCH transmission indicating the MBMS notification in a subframe configured by the MBSFN notification configuration information.

The base station transmits the MCCH including the MBSFN region configuration information for the corresponding NCT cell to the terminal on the NCT cell (S1020). The MBSFN region configuration message is transmitted in a subframe configured by the MCCH configuration information included in the MBSFN region information list.

The base station transmits the MAC CE regarding MCH scheduling information (MSI) for the NCT cell to the terminal on the secondary LCT cell or NCT cell (S1030). The base station may transmit the MAC CE including the MSI to the terminal on the NCT cell, or may be transmitted to the terminal on the secondary LCT cell.

For example, the base station may transmit the MAC CE including the MSI to the terminal through cross-carrier scheduling on a secondary LCT cell. This is a case where transmission of PDCCH and EPDCCH is not allowed on an NCT cell. In this case, the MAC CE may further include an EARFCN value or an MBSFN carrier index as a carrier separator as described above with reference to FIGS. 7 and 8. This is to inform the terminal that the MAC CE is for the NCT cell (carrier) since the MAC CE is transmitted to the terminal on the secondary LCT cell.

As another example, the base station may transmit the MAC CE for the MSI for the corresponding NCT cell to the terminal through the EPDCCH on the NCT cell. This is a case where EPDCCH transmission is allowed on an NCT cell. In this case, since the MAC CE is transmitted to the terminal on the corresponding NCT cell (carrier), there is no need for a separator to separate a separate carrier. Therefore, the MAC CE structure of the existing MSI can be used as it is.

The base station transmits the MBMS service to the terminal on the NCT cell (S1040). The base station transmits the MBMS service including user data such as voice or video to the terminal on the NCT cell.

Referring to FIG. 11, a terminal receives MBMS service configuration information for an NCT cell (or for an NCT cell) from a base station on a secondary LCT cell, that is, MBSFN subframe configuration information, MBSFN notification configuration information, and MBSFN region information list. (S1100).

For example, the UE may receive the MBSFN subframe configuration information, the MBSFN notification configuration information, and the MBSFN region information list from a base station on an auxiliary LCT cell through an RRC connection reconfiguration message. In this case, the terminal may receive the MBMS service configuration information in the RRC connection mode. In this case, the terminal may distinguish whether the information is on the corresponding NCT carrier based on notificationIndicator information allocated to the MBSFN region of the NCT carrier, or may distinguish whether the information is on the corresponding NCT carrier based on the MBSFN carrier index.

As another example, the terminal may receive the MBSFN subframe configuration information from the base station through SIB2 on the secondary LCT cell, and receive the MBSFN notification configuration information and the MBSFN region information list from the base station through SIB13. In this case, the UE may receive the MBMS service configuration information not only in the RRC connection mode but also in the idle mode. In the case of MBSFN subframe configuration information, the UE may identify whether the information is on the corresponding NCT carrier based on the EARFCN value, or may distinguish whether the information is on the corresponding NCT carrier based on the MBSFN carrier index. In the case of the MBSFN notification configuration information, the UE may determine that it is applied to all the signaled MBSFN regions in the same manner, or may distinguish whether the information on the corresponding NCT carrier is applied differently for each carrier based on the EARFCH value. In the case of the MBSFN region information list, the UE may distinguish whether the information is about the corresponding NCT carrier based on the EARFCN value or the MBSFN carrier index.

The PDCCH including the MBMS notification for the NCT cell is received from the base station on the secondary LCT cell (S1110). In this case, even when the PDCCH transmission is not allowed on the MBSFN subframe of the NCT cell, the UE may receive the PDCCH including the MBMS notification for the NCT cell on the secondary LCT cell.

When the MBMS notification occurs, the UE receives a PDCCH transmission indicating the MBMS notification in a subframe configured by the MBSFN notification configuration information. The PDCCH is configured by M-RNTI. At this time, the UE monitors the PDCCH scrambled with the M-RNTI in the common search space. In this case, the MBMS notification has occurred, indicating that there is a change in the MBSFN region configuration (information).

The terminal receives the MCCH including MBSFN region configuration information for the corresponding NCT cell from the base station on the NCT cell (S1120). The MBSFN region configuration message is transmitted in a subframe configured by the MCCH configuration information included in the MBSFN region information list.

The terminal receives a MAC CE regarding MCH scheduling information (MSI) for the NCT cell from the base station on the secondary LCT cell or the NCT cell (S1130). The terminal may receive the MAC CE for the MSI on the secondary LCT cell, or may be received on the NCT cell.

As an example, the terminal may receive the MAC CE for the MSI through cross-carrier scheduling on a secondary LCT cell. This is a case where transmission of PDCCH and EPDCCH is not allowed on an NCT cell. In this case, the MAC CE may further include an EARFCN value or an MBSFN carrier index as a carrier separator as described above with reference to FIGS. 7 and 8. The UE may know that the corresponding MAC CE is for the NCT cell (carrier) based on the carrier identifier included in the MAC CE.

As another example, the base station may transmit the MAC CE for the MSI for the corresponding NCT cell to the terminal through the EPDCCH on the NCT cell. This is a case where EPDCCH transmission is allowed on an NCT cell. In this case, since the MAC CE is transmitted to the terminal on the corresponding NCT cell (carrier), the terminal can know that the MAC CE is for the corresponding NCT cell without a separate carrier identifier.

The terminal receives the MBMS service from the base station on the NCT cell (S1140). The terminal may receive the MBMS service on the NCT cell including user data such as voice or video.

Referring to FIG. 12, the terminal 1200 according to the present invention may receive an MBMS service from the base station 1250. The terminal 1200 includes a receiver 1205 and a terminal processor 1210. The terminal processor 1210 performs functions and controls necessary for implementing the above-described features of the present invention. The terminal processor 1200 includes an RRC processor 1211 and an MBMS processor 1212.

The receiver 1205 receives MBMS service configuration information for the NCT cell from the base station 1250. The receiver 1205 receives the MBMS service configuration information on the secondary LCT cell. The secondary LCT cell may be a primary serving cell, or may be a macro LCT cell that assists macro secondary standalone NCT. The MBMS service configuration information includes MBSFN subframe configuration information, MBSFN notification configuration information, and MBSFN region information list. For example, the receiver 1205 may receive all of the MBSFN subframe configuration information, the MBSFN notification configuration information, and the MBSFN region information list through an RRC connection reconfiguration message. As another example, the receiver 1205 may receive the MBSFN subframe configuration information through SIB2, and receive the MBSFN notification configuration information and the MBSFN region information list through SIB13.

The RRC processor 1211 interprets the MBMS service configuration information, that is, the MBSFN subframe configuration information, the MBSFN notification configuration information, and the MBSFN region information list, extracts information fields included therein, and in accordance with the instruction of the extracted information field. Perform (or change) the MBMS related configuration at the RRC layer level. As an example, the RRC processing unit 1211 may interpret the RRC connection reconfiguration message, perform MBMS related configuration at the RRC layer level, and as another example, interpret the SIB2 and SIB13, and perform MBMS related configuration at the RRC layer level. It may be. In addition, the RRC processing unit 1211 may determine that the MBMS related information is for the corresponding NCT based on the separator for the NCT cell.

Meanwhile, in order to receive the MBMS notification, the reception unit 1205 monitors a subframe in which the MBMS notification occurs based on the MBSFN notification configuration information, and receives a PDCCH including the MBMS notification. For example, the receiver 1205 may receive (ie, cross-schedule) the PDCCH including the MBMS notification for the NCT cell on a secondary LCT cell. The RRC processor 1211 may control the receiver 1205 to monitor the subframe in which the MBMS notification occurs.

In addition, the receiver 1205 receives an MCCH including MBSFN region configuration information for the corresponding NCT cell on the NCT cell.

In addition, the receiver 1205 receives a MAC CE including MCH scheduling information (MSI) for an NCT cell, that is, a MAC CE for an MSI. For example, the receiver 1205 may receive the MAC CE cross-scheduling through a PDCCH on a secondary LCT cell. In this case, the MAC CE may further include an EARFCN value or an MBSFN carrier index as a carrier separator as described above with reference to FIGS. 7 and 8, and the MAC CE (specifically, the MAC CE (specifically, based on the carrier identifier)) is used. MSI) is for the corresponding NCT cell. As another example, the receiver 1205 may receive the MAC CE through an EPDCCH on an NCT cell. In this case, since the MAC CE is transmitted on the corresponding NCT cell, the MBMS processor 1212 may recognize that the MAC CE is for the corresponding NCT cell without a separate delimiter.

The MBMS processing unit 1212 performs MBMS related configuration at the terminal 1200 based on the MBSFNS notification, MBSFN region configuration information, MSI, and the like. If the MBMS notification exists, the MBMS processing unit 1212 may recognize that the MCCH configuration in a specific MBSFN region is to be changed, and may acquire new MCCH information based on the changed MCCH configuration information from the next modification period. have.

The receiver 1205 receives an MBMS service on an NCT cell based on the MBMS related configuration. The receiver 1205 may receive the MBMS service including the user data such as voice or video on the NCT cell.

The base station 1250 includes a transmitter 1255 and a base station processor 1260. The base station processor 1260 performs functions and controls necessary to implement the features of the present invention as described above. The base station processor 1260 includes an RRC processor 1261 and an MBMS processor 1262.

The RRC processor 1261 generates the MBSFN subframe configuration information for the NCT cell, the MBSFN notification configuration information, and the MBSFN region information list as information or message syntax and transmits the information to the terminal 1200 through the transmission unit 1255. For example, the RRC processor 1261 generates the RRC connection reconfiguration message including the MBSFN subframe configuration information, the MBSFN notification configuration information, and the MBSFN region information list for the NCT cell, and transmits the terminal through the transmission unit 1255. (1200). As another example, the RRC processing unit 1261 may generate an SIB2 including the MBSFN subframe configuration information for an NCT cell and send it to the terminal 1200 through the transmission unit 1255, and the MBSFN notification configuration information for an NCT cell. And an SIB13 including the MBSFN region information list and may be sent to the terminal 1200 through the transmitter 1255. In this case, the MBMS-related information for the NCT cell may further include a separator for the corresponding NCT cell.

The transmitter 1255 may transmit the RRC connection reconfiguration message to the terminal 1200 on a secondary LCT cell. Alternatively, the transmitter 1255 may transmit the SIB2 and the SIB13 to the terminal 1200 on the auxiliary LCT cell.

The MBMS processor 1262 performs MBMS related configuration at the base station 1250 end. The MBMS processor 1262 also determines whether the MCCH configuration for the MBSFN region for the NCT cell is changed. The MBSFN region in which the MCCH configuration is changed is informed to the terminal 1200 through the transmitter 1255. The MBMS processor 1262 may generate MBMS notification, MBSFN region configuration, and information on MSI for the NCT cell.

The transmitter 1255 may transmit (ie, cross-schedule) the MBMS notification to the terminal 1200 through the PDCCH on the secondary LCT cell. The transmitter 1255 may transmit the MCCH including the MBSFN region configuration information to the terminal 1200 on the NCT cell.

The transmitter 1255 may transmit the MSI to the terminal 1200 through the MAC CE of the MSI on the LCT cell. In this case, the above-described carrier identifier may be included in the MAC CE for the MSI. Alternatively, the transmitter 1255 may transmit the MSI to the terminal 1200 through the MAC CE of the MSI on the NCT cell.

In addition, the transmitter 1255 transmits an MBMS service including user data such as voice or video to the terminal 1200 on the NCT cell.

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention but to describe the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

Claims

As a terminal supporting multimedia broadcast multicast service (MBMS) in a wireless communication system supporting carrier aggregation (CA),

A receiver configured to receive MCH Scheduling Information (MSI) for MCH on a first cell; And

And a processor controlling the receiver to receive the MBMS on the second cell based on the MSI,

The second cell is configured with a new carrier type (NCT) carrier,

The receiving unit is characterized in that for receiving the MSI through a medium access control (MAC) control element (MAC) for the MSI mapped to the physical downlink control channel (PDCCH) on the first cell, the terminal.
The method of claim 1,

The processor recognizes that the corresponding MAC CE is the MAC CE for the second cell through a Carrier Indication Field (CIF) of the PDCCH indicating the MAC CE.
The method of claim 1,

LCID (Logical Channel ID) value of the MAC CE is configured to form a classification according to the carrier,

The processor recognizes that the corresponding MAC CE is the MAC CE for the NCT-based second cell based on the LCID value.
The method of claim 1,

MAC CE for the MSI includes a carrier identifier,

The processor unit, based on the carrier identifier, characterized in that the MAC CE for the MSI for the NCT carrier, characterized in that the terminal.
The method of claim 4, wherein

The carrier identifier is characterized in that the E-UTRA Absolute Radio Frequency Channel Number (EARFCN) value, the terminal
The method of claim 4, wherein

The carrier separator is characterized in that the MBSFN carrier index, the terminal.
As a base station that supports multimedia broadcast multicast service (MBMS) in a wireless communication system supporting carrier aggregation (CA),

A processor unit generating an MSI for the second cell;

On the first cell, including a transmitter for transmitting the multicast channel scheduling information (MSI),

The second cell is configured with a New Carrier Type (NCT) carrier, the processor unit generates a MAC CE for the MSI including the MSI,

The transmitter base station, characterized in that for mapping the MAC CE to the PDCCH on the first cell to transmit to the terminal.
The method of claim 7, wherein

The processor indicates that the corresponding MAC CE is a MAC CE for the second cell through a carrier indicator field of the PDCCH indicating the MAC CE.
The method of claim 7, wherein

The processor unit, characterized in that configured to form the LCID value of the MAC CE according to the carrier.
The method of claim 7, wherein

The processor unit, characterized in that for generating a MAC CE for the MSI including a carrier identifier.
The method of claim 10,

And the processor unit generates the MAC CE including an EARFCN value as the carrier separator.
The method of claim 10,

And the processor unit generates the MAC CE including an MBSFN carrier index as the carrier separator.
A method of receiving a multimedia broadcast multicast service (MBMS) by a terminal in a wireless communication system supporting carrier aggregation (CA),

Receiving MCH scheduling information (MSI) for a second cell on a first cell; And

Performing the MBMS reception on the second cell based on the MSI,

The second cell is configured with a New Carrier Type (NCT) carrier, and the MSI is included in the MAC CE, characterized in that received on the first cell, MBMS receiving method.
The method of claim 13,

The MBMS receiving method, characterized in that the corresponding MAC CE recognizes the MAC CE for the second cell through a carrier indicator field of the PDCCH indicating the MAC CE.
The method of claim 13,

A Logical Channel ID (LCID) value of the MAC CE is configured to form a distinction according to a carrier, and recognizes that the corresponding MAC CE is a MAC CE for the second cell based on the LCID value. .
The method of claim 13,

MAC CE for the MSI includes a carrier identifier,

MBMS receiving method, characterized in that the MAC CE for the second cell based on the carrier identifier.
The method of claim 16,

The carrier separator is characterized in that the EARFCN value, MBMS receiving method.
The method of claim 16,

The carrier identifier is characterized in that the MBSFN carrier index, MBMS receiving method.