CN103621118B

CN103621118B - Data communication method, device and system

Info

Publication number: CN103621118B
Application number: CN201280001087.3A
Authority: CN
Inventors: 陈道来; 邴立东
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2012-05-17
Filing date: 2012-05-17
Publication date: 2017-02-22
Anticipated expiration: 2032-05-17
Also published as: WO2013170472A1; CN103621118A

Abstract

The present invention relates to the field of communications. Disclosed are a data communication method, device and system, comprising: a first eNodeB transmits a first request message to an MCE, so that the MCE establishes a relationship between the first eNodeB and a second eNodeB according to the identifier of the first eNodeB and the identifier of the second eNodeB, the first request message being used to request the establishment of an interface M2 between the first eNodeB and the MCE; the first eNodeB receives a first response message transmitted by the MCE, the first response message being used to indicate the successful establishment of the interface M2 between the first eNodeB and the MCE, and carrying the identifier of the first eNodeB and the identifier of the second eNodeB; the first eNodeB transmits the first response message to the second eNodeB; the first eNodeB receives the data transmitted by the MCE, and transmits the data from the MCE to the second eNodeB. The present invention can ensure normal communication between an eNodeB and an MCE even if the interface M2 between the eNodeB and the MCE fails.

Description

Data communication method, device and system

Technical Field

The present invention relates to the field of communications, and in particular, to a method, an apparatus, and a system for data communication.

Background

In an existing eMBMS (evolved Multicast broadcast service) system, an MCE (multi cell/multi broadcast Coordination Entity) uniformly controls a plurality of enodebs (E-UTRAN enodebs, evolved network base stations) to ensure that each eNodeB under the control of the MCE can send service data for a cell managed by itself without interfering with each other. The MCE sends configuration information to each eNodeB over an M2 interface to allocate time-frequency resources to each eNodeB, each eNodeB having an M2 interface for data transmission with the MCE. However, when the M2 interface between an eNodeB and an MCE fails, the latest configuration information sent by the MCE cannot be received by the eNodeB. In this case, the eNodeB is a problem eNodeB.

Currently, the processing method for the problem eNodeB is as follows:

when the eNodeB detects that an M2 interface between the eNodeB and the MCE has a fault, the eNodeB sends service data to the cell managed by the eNodeB according to the time-frequency resource allocated to the MCE by the MCE which is received last time until the M2 interface of the eNodeB is detected to be recovered to normal, and sends the service data to the cell managed by the eNodeB according to the latest time-frequency resource when the latest time-frequency resource sent by the MCE is received;

as can be seen, in the conventional processing method, when an M2 interface of an eNodeB fails, the eNodeB cannot normally communicate with an MCE because the eNodeB cannot receive the latest time-frequency resource allocated to the eNodeB by the MCE.

Disclosure of Invention

The invention discloses a method, a device and a system for data communication, which can ensure that an eNodeB and an MCE can still carry out normal communication when an M2 interface between the eNodeB and the MCE goes wrong.

The invention provides a data communication method on the one hand, and the technical scheme is as follows:

the first base station sends a first request message to the MCE, so that the MCE establishes a relationship between the first base station and the second base station according to an identifier of the first base station and an identifier of the second base station, the first request message is used for requesting to establish an M2 interface between the first base station and the MCE, and the first request message carries the identifier of the first base station and the identifier of the second base station;

the first base station receives a first response message sent by the MCE, wherein the first response message is used for indicating that the establishment of an M2 interface between the first base station and the MCE is successful, and the first response message carries an identifier of the first base station and an identifier of the second base station;

the first base station sends a first response message to the second base station;

and the first base station receives the data sent by the MCE and sends the data from the MCE to the second base station.

The invention also provides a data communication method, which adopts the following technical scheme:

the second base station sends a first request message or an indication message to the first base station, so that the MCE receives the first request message forwarded by the first base station or the first request message generated according to the indication message, and establishes a relationship between the first base station and the second base station according to the identifier of the first base station and the identifier of the second base station; the first request message is used for requesting to establish an M2 interface between the first base station and the MCE, the first request message carries an identifier of the first base station and an identifier of the second base station, and the indication message is used for indicating to establish an M2 interface between the first base station and the MCE;

the second base station receives an M2 first response message from the MCE, wherein the M2 first response message is sent by the first base station and is used for indicating that the establishment of an M2 interface between the first base station and the MCE is successful, and the first response message carries an identifier of the first base station and an identifier of the second base station;

and the second base station receives the data from the MCE sent by the first base station.

Another aspect of the present invention provides another data communication method, which specifically adopts the following technical solutions:

the method comprises the steps that the MCE receives a first request message sent by a first base station, wherein the first request message is received by the first base station from a second base station or generated according to an indication message received by the first base station from the second base station, the first request message is used for requesting to establish an M2 interface between the first base station and the MCE, the first request message carries an identifier of the first base station and an identifier of the second base station, and the indication message is used for indicating to establish an M2 interface between the first base station and the MCE;

the MCE establishes a relation between the first base station and the second base station according to the identification of the first base station and the identification of the second base station;

the MCE sends a first response message to the second base station through the first base station, wherein the first response message is used for indicating that the establishment of an M2 interface between the first base station and the MCE is successful, and the first response message carries the identifier of the first base station and the identifier of the second base station;

the MCE transmits data to the second base station via the first base station according to the relationship between the first base station and the second base station.

Another aspect of the present invention provides a first device, which specifically includes a sending unit and a receiving unit, where:

the sending unit is configured to send a first request message to the MCE, so that the MCE can establish a relationship between the device and the second base station according to the identifier of the device and the identifier of the second base station, where the first request message is used to request an M2 interface between the device and the MCE, and the identifier of the device and the identifier of the second base station are carried in the first request message;

the receiving unit is configured to receive a first response message sent by the MCE, where the first response message is used to indicate that the establishment of an M2 interface between the device and the MCE is successful, and the first response message carries an identifier of the device and an identifier of the second base station;

the sending unit is further configured to send the first response message to the second base station after the receiving unit receives the first response message sent by the MCE;

the receiving unit is further configured to receive data sent by the MCE after the sending unit sends the first response message to the second base station;

the sending unit is further configured to send the data from the MCE to the second base station after the receiving unit receives the data sent by the MCE.

Another aspect of the present invention further provides a second device, which specifically includes a sending unit and a receiving unit, where:

the sending unit is configured to send a first request message or an indication message to the first base station, so that the MCE receives the first request message forwarded by the first base station or the first request message generated according to the indication message, and establishes a relationship between the first base station and the device according to the identifier of the first base station and the identifier of the device; the first request message is used for requesting to establish an M2 interface between the first base station and the MCE, the first request message carries an identifier of the first base station and an identifier of the equipment, and the indication message is used for indicating to establish an M2 interface between the first base station and the MCE;

the receiving unit is configured to receive an M2 first response message from the MCE sent by the first base station, where the first response message is used to indicate that the M2 interface between the first base station and the MCE is successfully established, and the first response message carries an identifier of the first base station and an identifier of the device;

the receiving unit is further configured to receive the data from the MCE sent by the first base station after receiving the M2 first response message from the MCE sent by the first base station.

Another aspect of the present invention further provides a third device, specifically including a receiving unit, a processing unit, and a sending unit, where:

the receiving unit is configured to receive a first request message sent by a first base station, where the first request message is received by the first base station from a second base station or generated according to an indication message received from the second base station, where the first request message is used to request establishment of an M2 interface between the first base station and a device, the first request message carries an identifier of the first base station and an identifier of the second base station, and the indication message is used to indicate establishment of an M2 interface between the first base station and an MCE;

the processing unit is used for establishing the relationship between the first base station and the second base station according to the identification of the first base station and the identification of the second base station;

the sending unit is configured to send a first response message to the second base station via the first base station, where the first response message is used to indicate that the M2 interface between the first base station and the device is successfully established, and the first response message carries an identifier of the first base station and an identifier of the second base station;

the sending unit is further configured to send the data to the second base station via the first base station according to a relationship between the first base station and the second base station after sending the first response message to the second base station via the first base station.

Another aspect of the present invention provides a system for data communication, which specifically includes the first device, the second device, and the third device.

According to the data communication method, device and system provided by the invention, when the M2 interface between the second base station and the MCE fails to cause that the second base station cannot directly communicate with the MCE, the first base station sends the first request message to the MCE, and after receiving the first request message, the MCE establishes the relationship between the first base station and the second base station and sends the first response message to the second base station through the first base station. In subsequent communications, the MCE may send data to be sent to the second base station to the first base station according to a relationship between the first base station and the second base station, and the first base station forwards the data from the MCE to the second base station. Similarly, the first base station can also send the data to be sent to the MCE to the first base station, and then the first base station sends the data from the first base station to the MCE, so that when the M2 interface between the second base station and the MCE fails, the second base station can still be ensured to perform normal communication with the MCE, thereby avoiding the second base station from causing interference to cells managed by other normal base stations, and avoiding the waste of time-frequency resources allocated by the MCE for the second base station.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a flow chart of a method for data communication according to an embodiment of the present invention;

fig. 2 is a flow chart of a method of communicating second data according to an embodiment of the present invention;

fig. 3 is a flow chart of a third method for data communication according to an embodiment of the present invention;

fig. 4 is a flow chart of a method of data communication according to another embodiment of the present invention;

FIG. 5 is a flow chart of a method of data communication according to yet another embodiment of the present invention;

fig. 6 is a flow chart of a method of data communication according to another embodiment of the present invention;

FIG. 7 is a block diagram of a first device provided in accordance with an embodiment of the present invention;

FIG. 8 is a block diagram of a second first device provided in accordance with an embodiment of the present invention;

fig. 9 is a block diagram of a third first device provided in an embodiment of the present invention;

FIG. 10 is a block diagram of a second device provided in accordance with one embodiment of the present invention;

FIG. 11 is a block diagram of a third device provided in accordance with an embodiment of the present invention;

fig. 12 is a system configuration diagram for data communication according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

For convenience of understanding, in the embodiment of the present invention, the first base station and the second base station may take the first eNodeB and the second eNodeB as an example for description.

The second eNodeB is an eNodeB with a failure at the M2 interface, the second eNodeB uses the first eNodeB as a backup eNodeB of the second eNodeB, before the M2 interface fails, for example, when the second eNodeB is started, a person skilled in the art configures the first eNodeB as the backup eNodeB of the second eNodeB by issuing a configuration message, where the configuration message includes attribute information of the first eNodeB, where the attribute information may be an identifier, and the second eNodeB may know the first eNodeB according to the configuration message. The backup eNodeB of each eNodeB may be one or multiple, and each eNodeB may also be a backup eNodeB of one or multiple other enodebs.

Referring to fig. 1, an embodiment of the present invention provides a flowchart of a data communication method, where an execution subject of the method is a first base station, and the method specifically includes the following steps:

101: the first base station sends a first request message to the MCE, so that the MCE establishes a relationship between the first base station and the second base station according to the identifier of the first base station and the identifier of the second base station, the first request message is used for requesting to establish an M2 interface between the first base station and the MCE, and the first request message carries the identifier of the first base station and the identifier of the second base station.

102: the first base station receives a first response message sent by the MCE, where the first response message is used to indicate that the M2 interface between the first base station and the MCE is successfully established, and the first response message carries an identifier of the first base station and an identifier of the second base station.

103: the first base station sends a first response message to the second base station.

104: and the first base station receives the data sent by the MCE and sends the data from the MCE to the second base station.

For example, in the method provided in this embodiment, the first base station may be a first eNodeB.

Optionally, the data of the MCE may be time-frequency resource information allocated by the MCE to the second base station.

In the method for data communication provided in this embodiment, the first base station sends the first request message to the MCE, so that the MCE establishes a relationship between the first base station and the second base station according to the identifier of the first base station and the identifier of the second base station, and sends the first response message sent by the MCE to the second base station. The first base station may forward data intended for the second base station by the MCE to the second base station in subsequent communications. Similarly, the first base station may also send data to be sent by the second base station to the MCE. When the M2 interface between the second base station and the MCE fails, the second base station can still be ensured to normally communicate with the MCE, meanwhile, the second base station can be prevented from interfering with cells managed by other normal base stations, and waste of time-frequency resources allocated to the second base station by the MCE is also avoided.

Referring to fig. 2, an embodiment of the present invention provides a flowchart of a second data communication method, where an execution subject of the method is a second base station, and the method specifically includes the following steps:

201: the second base station sends a first request message or an indication message to the first base station, so that the MCE receives the first request message forwarded by the first base station or the first request message generated according to the indication message, and establishes a relationship between the first base station and the second base station according to the identifier of the first base station and the identifier of the second base station; the first request message is used for requesting to establish an M2 interface between the first base station and the MCE, the first request message carries an identifier of the first base station and an identifier of the second base station, and the indication message is used for indicating to establish an M2 interface between the first base station and the MCE.

202: the second base station receives an M2 first response message from the MCE, which is sent by the first base station, wherein the first response message is used for indicating that the establishment of the M2 interface between the first base station and the MCE is successful, and the first response message carries the identifier of the first base station and the identifier of the second base station.

203: and the second base station receives the data from the MCE sent by the first base station.

For example, in the method provided in this embodiment, the first base station may be a second eNodeB different from the first eNodeB.

In the above data communication method provided in this embodiment, the second base station may send the first request message or the indication message to the first base station, so that the first base station directly sends the received first request message to the MCE, or sends the first request message generated according to the indication message to the MCE. And when the MCE successfully establishes the relationship between the first base station and the second base station, the second base station receives an M2 first response message from the MCE, which is sent by the first base station. In subsequent communications, the second base station may receive, through the first base station, data sent by the MCE, and similarly, the second base station may also send, through the first base station, data to be sent to the MCE. When the M2 interface between the second base station and the MCE fails, the second base station can still be ensured to normally communicate with the MCE, meanwhile, the second base station can be prevented from interfering with cells managed by other normal base stations, and waste of time-frequency resources allocated to the second base station by the MCE is also avoided.

Referring to fig. 3, an embodiment of the present invention provides a flowchart of a third method for data communication, where an execution subject of the method is an MCE, and the method specifically includes the following steps:

301: the MCE receives a first request message sent by a first base station, wherein the first request message is received by the first base station from a second base station or generated according to an indication message received from the second base station, the first request message is used for requesting to establish an M2 interface between the first base station and the MCE, the first request message carries an identifier of the first base station and an identifier of the second base station, and the indication message is used for indicating to establish an M2 interface between the first base station and the MCE.

302: and the MCE establishes the relationship between the first base station and the second base station according to the identification of the first base station and the identification of the second base station.

303: the MCE sends a first response message to the second base station through the first base station, wherein the first response message is used for indicating that the establishment of the M2 interface between the first base station and the MCE is successful, and the first response message carries the identifier of the first base station and the identifier of the second base station.

304: the MCE transmits data to the second base station via the first base station according to the relationship between the first base station and the second base station.

Optionally, the data sent by the MCE to the first base station may be time-frequency resource information allocated by the MCE to the second base station.

In the method for data communication provided in this embodiment, after receiving a first request message sent by a first base station, an MCE establishes a relationship between the first base station and a second base station, and sends a first response message to the second base station through the first base station. In subsequent communications, the MCE may transmit data to be transmitted to the second base station through the first base station to the second base station. Similarly, the MCE may also receive data transmitted by the second base station through the first base station. When an M2 interface between the second eNodeB and the MCE fails, the second eNodeB can still be ensured to normally communicate with the MCE, meanwhile, the second eNodeB can be prevented from interfering with cells managed by other normal eNodeBs, and waste of time-frequency resources allocated by the MCE for the second eNodeB is also avoided.

Referring to fig. 4, another embodiment of the present invention provides a flowchart of a data communication method, which specifically includes the following steps:

401: and the second eNodeB sends a third request message to the first eNodeB, wherein the third request message is used for establishing a specific message forwarding channel.

Optionally, the third request message carries an identifier of the second eNodeB.

Optionally, when the second eNodeB sends an X2 channel establishment request message to the first eNodeB to trigger establishment of an X2 channel between the second eNodeB and the first eNodeB, the second eNodeB may carry the third request message in an X2 channel establishment request message sent to the first eNodeB;

optionally, when the second eNodeB sends a private message channel setup message to the first eNodeB to trigger the setup of the private message channel between the second eNodeB and the first eNodeB, the second eNodeB may carry the third request message in the private message channel setup message sent to the first eNodeB;

optionally, after the X2 channel has been successfully established between the second eNodeB and the first eNodeB, the second eNodeB may also send the third request message to the first eNodeB in the X2 channel.

Optionally, after the private message channel has been successfully established between the second eNodeB and the first eNodeB, the second eNodeB may also send the third request message to the first eNodeB in the private message channel.

In this embodiment, the X2 channel and the private message channel are channels for performing communication between the second eNodeB and the first eNodeB, the X2 channel is a channel established through an X2 interface, the private message channel is a channel established through a private interface, and the establishment of the X2 channel and the private message channel is also the prior art, which is not described herein again.

402: and the first eNodeB receives the third request message, and establishes a specific message forwarding channel between the first eNodeB and the second eNodeB.

Optionally, when the X2 channel has not been established between the first eNodeB and the second eNodeB, and the first eNodeB obtains the third request message from the X2 channel establishment request message sent by the second eNodeB, the first eNodeB establishes the specific message forwarding channel during the process of establishing the X2 channel. At this time, the specific message forwarding channel is carried in the X2 channel established directly through the X2 interface between the first eNodeB and the second eNodeB.

Optionally, when the private message channel is not established between the first eNodeB and the second eNodeB, and the first eNodeB obtains the third request message from the private message channel establishment request message sent by the second eNodeB, the first eNodeB establishes the specific message forwarding channel during the process of establishing the private message channel. At this time, the specific message forwarding channel is carried in a private message channel directly established through a private interface between the first eNodeB and the second eNodeB.

Optionally, after the X2 channel between the first eNodeB and the second eNodeB is successfully established, when the first eNodeB receives the third request message from the established X2 channel, the first eNodeB establishes the specific message forwarding channel in the X2 channel, and at this time, the specific message forwarding channel is carried in the X2 channel directly established through the X2 interface between the first eNodeB and the second eNodeB;

optionally, after the private message channel between the first eNodeB and the second eNodeB is successfully established, when the first eNodeB receives the third request message from the established private message channel, the first eNodeB establishes the specific message forwarding channel in the private message channel, and at this time, the specific message forwarding channel is carried in the private message channel directly established through the private interface between the first eNodeB and the second eNodeB.

It should be noted that, after the specific message forwarding channel is successfully established, the specific message forwarding channel is initially in an unopened state, and when the second eNodeB needs to communicate with the MCE through the first eNodeB, the second eNodeB sends a second request message to the first eNodeB, where the second request message is used to activate the specific message forwarding channel, so that after the specific message forwarding channel is successfully activated, the second eNodeB can communicate with the first eNodeB through the specific message forwarding channel, and further the second eNodeB can communicate with the MCE through the first eNodeB.

403: the second eNodeB sends a fourth request message to the MCE, where the fourth request message is used to request establishment of an M2 interface between the second eNodeB and the MCE.

In this embodiment, the fourth request message is an M2 interface setup request message in the existing protocol.

Optionally, the fourth request message carries an identifier of the second eNodeB.

Optionally, when the second eNodeB does not establish the M2 tunnel with the MCE, the second eNodeB may send the fourth request message to the MCE through the M2 interface.

Optionally, after the second eNodeB and the MCE have established the M2 channel and the second eNodeB and the MCE are communicating, the second eNodeB detects that its underlying physical link is broken, or detects that data of the MCE is not received within the first preset time, the second eNodeB sends a fourth request message to the MCE through the M2 interface, so as to reestablish the M2 channel between the second eNodeB and the MCE.

404: and when the second eNodeB does not receive the response of the MCE or receives error information returned by the MCE within second preset time, sending a second request message to the first eNodeB, wherein the second request message is used for activating a specific message forwarding channel.

For example, when the second eNodeB does not receive the response of the MCE or does not receive the error information returned by the MCE within the second preset time, it indicates that the M2 interface between the second eNodeB and the MCE is in the failure state, and at this time, the second eNodeB sends the second request message to the first eNodeB.

Optionally, the second eNodeB may send the second request message to the first eNodeB through the above-mentioned X2 channel or the above-mentioned private message channel, but is not limited thereto.

In the method of this embodiment, the operation of establishing the specific message forwarding channel between the second eNodeB and the first eNodeB may also be performed after the second eNodeB does not receive the response of the MCE or does not receive the error information returned by the MCE within the second preset time, and after the specific message forwarding channel is successfully established, the second eNodeB sends the second request message to the first eNodeB to activate the specific message forwarding channel. That is, step 401 and step 402 in this embodiment may also be executed after step 404, when the second eNodeB does not receive the response of the MCE or receives the error information returned by the MCE within the second preset time, and then the second eNodeB continues to execute step 404 to send the second request message to the first eNodeB.

405: and after receiving the second request message, the first eNodeB activates a specific message forwarding channel.

406: and the first eNodeB sends a second response message to the second eNodeB, wherein the second response message is used for indicating that the activation of the specific message forwarding channel is successful.

Optionally, the first eNodeB may send the second response message to the second eNodeB through the above-mentioned X2 channel or the above-mentioned private message channel, but is not limited thereto.

407: and after receiving the second response message, the second eNodeB sends a first request message to the first eNodeB through a specific message forwarding channel, wherein the first request message is used for requesting to establish an M2 interface between the first eNodeB and the MCE.

In this embodiment, the first request message is an M2 interface setup request message in an existing protocol.

Optionally, the first request message carries an identifier of the first eNodeB and an identifier of the second eNodeB.

Optionally, the second eNodeB sends the first request message to the second eNodeB through a specific message forwarding channel carried in the X2 channel;

optionally, the second eNodeB sends the first request message to the second eNodeB through a specific message forwarding channel carried in the private message channel.

408: after receiving the first request message sent by the second eNodeB, the first eNodeB sends the first request message to the MCE through the M2 interface of the first eNodeB.

409: after receiving the M2 first request message, the MCE establishes a relationship between the first eNodeB and the second eNodeB according to the identifier of the first eNodeB and the identifier of the second eNodeB.

For example, the relationship of the first eNodeB and the second eNodeB may include: the first eNodeB is a forwarding node when the second eNodeB communicates with the MCE.

410: the MCE sends a first response message to the first eNodeB, where the first response message is used to indicate that the M2 interface between the first eNodeB and the MCE was successfully established.

Optionally, the first response message carries an identifier of the first eNodeB and an identifier of the second eNodeB.

Optionally, the MCE sends a first response message to be sent to the second eNodeB to the corresponding first eNodeB according to the established relationship between the first eNodeB and the second eNodeB.

411: the first eNodeB sends the first response message to the second eNodeB through a specific message forwarding channel.

Optionally, the first eNodeB sends the first response message to the second eNodeB through a specific message forwarding channel carried in the X2 channel;

optionally, the first eNodeB sends the first response message to the second eNodeB through a specific message forwarding channel carried in the private message channel.

412: the MCE transmits data to be transmitted to the second eNodeB to the first eNodeB.

Optionally, the data may be time-frequency resource information allocated by the MCE to the second eNodeB.

Optionally, the MCE sends the data to be sent to the second eNodeB to the corresponding first eNodeB according to the established relationship between the first eNodeB and the second eNodeB.

413: the first eNodeB transmits the received data from the MCE to the second eNodeB through a specific message forwarding channel.

Optionally, the first eNodeB sends the data from the MCE to the second eNodeB through a specific message forwarding channel carried in the X2 channel;

optionally, the first eNodeB sends the data from the MCE to the second eNodeB through a specific message forwarding channel carried in the private message channel.

In this embodiment, in the process that the second eNodeB communicates with the MCE through the first eNodeB, when the second eNodeB detects that its M2 interface returns to normal, the second eNodeB stops communicating with the MCE through the first eNodeB, and at this time, the second eNodeB directly communicates with the MCE through its M2 interface.

In the method for data communication provided by this embodiment, a first eNodeB establishes a specific message forwarding channel between a second eNodeB and the first eNodeB, when an M2 interface between the second eNodeB and an MCE fails and the second eNodeB cannot directly communicate with the MCE, the MCE may send data sent to the second eNodeB to the first eNodeB, and after receiving the data from the MCE, the first eNodeB sends the data from the MCE to the second eNodeB through the specific message forwarding channel established between the first eNodeB and the second eNodeB. Similarly, the second eNodeB may also send the data to be sent to the MCE to the first eNodeB through the specific message forwarding channel, and the first eNodeB forwards the data sent by the second eNodeB to the MCE. It is realized that when the M2 interface between the second eNodeB and the MCE fails, the second eNodeB and the MCE can still be guaranteed to be normally on. Therefore, the interference of the second eNodeB to the cells managed by other normal eNodeBs is avoided, and the waste of the time-frequency resources distributed by the MCE to the second eNodeB is also avoided.

In the processing mode in the prior art, when the latest time-frequency resource allocated by the MCE changes, the second eNodeB cannot receive the latest time-frequency resource allocated by the MCE due to the failure of the M2 interface, and other normal enodebs can receive the latest time-frequency resource information allocated by the MCE, and if the second eNodeB still sends service data to the cell managed by the second eNodeB according to the last received time-frequency resource before the failure of the M2 interface, the time-frequency resource used by the second eNodeB is different from that of the other normal enodebs, so that interference is caused to the cell managed by the other normal enodebs. By the method in the embodiment, the second eNodeB can be ensured to receive the latest time-frequency resource information from the MCE, so that interference to cells managed by other normal enodebs is not caused. The second eNodeB can receive the time-frequency resource information distributed by the MCE, and simultaneously, the problem of time-frequency resource waste of MCE distribution is avoided.

Referring to fig. 5, a flowchart of a data communication method is provided in a further embodiment of the present invention, which specifically includes the following steps:

501: and the second eNodeB sends a third request message to the first eNodeB, wherein the third request message is used for establishing a specific message forwarding channel.

Optionally, when the second eNodeB sends an indirect channel setup request message to the first eNodeB to trigger setup of an indirect channel between the second eNodeB and the first eNodeB, the second eNodeB may carry the third request message in the setup request message sent to the first eNodeB to setup the indirect channel;

optionally, after the indirect channel has been successfully established between the second eNodeB and the first eNodeB, the second eNodeB may also send the third request message to the first eNodeB through the indirect channel.

In this embodiment, the indirect channel is a channel for performing communication between the second eNodeB and the first eNodeB, and the indirect channel includes a first channel established between another node and the first eNodeB through an X2 interface, a private interface, or an S1 interface, and a second channel established between another node and the second eNodeB through an X2 interface, a private interface, or an S1 interface.

The other node may comprise a mobility management entity MME or a third eNodeB in addition to the first eNodeB and the second eNodeB. When the other nodes are MMEs, the indirect path includes a first path established between the MME and the first eNodeB through an S1 interface and a second path established between the second eNodeB and the MME through an S1 interface. The establishment of the first channel and the second channel is the prior art, and is not described herein again.

Specifically, the present step can be implemented by the following substeps:

501-1: the second eNodeB sends a third request message to the other nodes.

Optionally, when the other node is a third eNodeB, the second eNodeB sends the third request message to the third eNodeB.

Optionally, when the other node is an MME, the second eNodeB sends the third request message to the MME.

501-2: and after receiving the third request message, the other nodes send the third request message to the first eNodeB.

Optionally, when the other node is a third eNodeB, the third eNodeB sends the third request message to the first eNodeB.

Optionally, when the other node is an MME, the MME sends the third request message to the first eNodeB.

502: and the first eNodeB receives the third request message, and establishes a specific message forwarding channel between the first eNodeB and the second eNodeB.

Optionally, when an indirect channel is not established between the first eNodeB and the second eNodeB and the first eNodeB obtains the third request message from the indirect channel establishment request message sent by the second eNodeB, the first eNodeB establishes the specific message forwarding channel during the process of establishing the indirect channel. At this time, the specific message forwarding channel is carried in a first channel established between the other node and the first eNodeB through an X2 interface, a private interface, or an S1 interface, and a second channel established between the second eNodeB and the other node through an X2 interface, a private interface, or an S1 interface.

Optionally, after the indirect path between the first eNodeB and the second eNodeB is successfully established, when the first eNodeB receives the third request message from the established indirect path, the first eNodeB establishes the specific message forwarding path in the indirect path, and at this time, the specific message forwarding path is carried on a first path established between the other node and the first eNodeB through the X2 interface, the private interface, or the S1 interface, and a second path established between the second eNodeB and the other node through the X2 interface, the private interface, or the S1 interface.

Optionally, the specific message forwarding channel includes two parts, which are a first forwarding sub-channel between the other node and the first eNodeB and a second forwarding sub-channel between the second eNodeB and the other node, respectively, where the first forwarding sub-channel is carried in a first channel established through an X2 interface, a private interface, or an S1 interface between the other node and the first eNodeB, and the second forwarding sub-channel is carried in a second channel established through an X2 interface, a private interface, or an S1 interface between the second eNodeB and the other node.

When the other nodes are MMEs, the first forwarding sub-channel is carried in a first channel established between the MME and the first eNodeB through an S1 interface, and the second forwarding sub-channel is carried in a second channel established between the second eNodeB and the MME through an S1 interface. Namely, the specific message forwarding channel is carried in a first channel established between the MME and the first eNodeB through the S1 interface and a second channel established between the second eNodeB and the MME through the S1 interface.

503: the second eNodeB sends a fourth request message to the MCE, where the fourth request message is used to request establishment of an M2 interface between the second eNodeB and the MCE.

Optionally, after the second eNodeB and the MCE have established the M2 channel and the second eNodeB and the MCE are communicating, when the second eNodeB detects that its underlying physical link is broken, or detects that data of the MCE is not received within a first preset time, the second eNodeB sends a fourth request message to the MCE through its M2 interface, so as to reestablish the M2 channel between the second eNodeB and the MCE.

504: and when the second eNodeB does not receive the response of the MCE or receives error information returned by the MCE within second preset time, sending a second request message to the first eNodeB, wherein the second request message is used for activating a specific message forwarding channel.

Optionally, the step may specifically include the following sub-steps:

504-1: and when the second eNodeB does not receive the response of the MCE or receives error information returned by the MCE within second preset time, the second eNodeB sends a second request message to other nodes through a second channel between the second eNodeB and other nodes.

Optionally, when the other node is a third eNodeB, the second eNodeB sends the second request message to the third eNodeB through a second channel between the second eNodeB and the third eNodeB. Wherein the second channel is established through any one of an X2 interface, a private interface or an S1 interface.

Optionally, when the other node is an MME, the second eNodeB sends the second request message to the MME through a second channel between the second eNodeB and the MME. Wherein the second channel is established through an S1 interface.

504-2: the other node sends the second request message to the first eNodeB through a first channel between the other node and the first eNodeB.

Optionally, when the other node is a third eNodeB, the third eNodeB sends the second request message to the first eNodeB through a first channel between the third eNodeB and the first eNodeB. Wherein the first channel is a first channel established through any one of an X2 interface, a private interface or an S1 interface.

Optionally, when the other node is an MME, the MME sends the second request message to the first eNodeB through a first channel between the MME and the first eNodeB. Wherein the first channel is a first channel established through an S1 interface.

The foregoing is the substeps embodied in step 504, but is not limited thereto.

In the method of this embodiment, the operation of establishing the specific message forwarding channel between the second eNodeB and the first eNodeB may also be performed after the second eNodeB does not receive the response of the MCE or does not receive the error information returned by the MCE within the second preset time, and after the specific message forwarding channel is successfully established, the second eNodeB sends the second request message to the first eNodeB to activate the specific message forwarding channel. That is, step 501 and step 502 in this embodiment may also be performed after the second eNodeB does not receive the response of the MCE or receives the error information returned by the MCE within the second preset time in step 504, and then the second eNodeB continues to perform the operation of step 504 to send the second request message to the first eNodeB.

505: and after receiving the second request message, the first eNodeB activates a specific message forwarding channel.

506: and the first eNodeB sends a second response message to the second eNodeB, wherein the second response message is used for indicating that the activation of the specific message forwarding channel is successful.

Optionally, the step may specifically include the following sub-steps:

506-1: and the first eNodeB sends a second response message to the other nodes through the first channel between the other nodes and the first eNodeB, wherein the second response message is used for indicating that the activation of the specific message forwarding channel is successful.

506-2: and the other nodes send the second response message to the second eNodeB through a second channel between the second eNodeB and the other nodes.

The foregoing is the sub-step of step 506, but is not limited thereto.

507: and after receiving the second response message, the second eNodeB sends a first request message to the first eNodeB through a specific message forwarding channel, wherein the first request message is used for requesting to establish an M2 interface between the first eNodeB and the MCE.

Optionally, the step may specifically include the following sub-steps:

507-1: and after receiving the second response message, the second eNodeB sends a first request message to the other node through a second forwarding sub-channel between the second eNodeB and the other node, where the first request message is used to request establishment of an M2 interface between the first eNodeB and the MCE.

Optionally, when the other node is a third eNodeB, the second eNodeB may send the first request message to the third eNodeB through a second forwarding sub-channel carried in a second channel between the second eNodeB and the third eNodeB.

Optionally, when the other node is an MME, the second eNodeB may send the first request message to the MME through a second forwarding sub-channel carried in a second channel between the second eNodeB and the MME.

507-2: the other node sends the first request message to the first eNodeB through a first forwarding sub-channel between the other node and the first eNodeB.

Optionally, when the other node is a third eNodeB, the third eNodeB may send the first request message to the first eNodeB through a first forwarding sub-channel carried in a first channel between the third eNodeB and the first eNodeB.

Optionally, when the other node is an MME, the MME may send the first request message to the first eNodeB through a first forwarding sub-channel carried in a first channel between the MME and the first eNodeB.

508: after receiving the first request message sent by other nodes, the first eNodeB sends the first request message to the MCE through an M2 interface of the first eNodeB.

509: and after receiving the first request message, the MCE establishes the relationship between the first eNodeB and the second eNodeB according to the identifier of the first eNodeB and the identifier of the second eNodeB.

510: the MCE sends a first response message to the first eNodeB, where the first response message is used to indicate that the M2 interface between the first eNodeB and the MCE was successfully established.

511: the first eNodeB sends the first response message to the second eNodeB through a specific message forwarding channel.

Optionally, the step may specifically include the following sub-steps:

511-1: the first eNodeB sends the first response message to the other nodes through a first forwarding sub-channel between the other nodes and the first eNodeB.

Optionally, when the other node is a third eNodeB, the first eNodeB may send the first response message to the third eNodeB through a first forwarding sub-channel carried in a first channel between the third eNodeB and the first eNodeB.

Optionally, when the other node is an MME, the first eNodeB may send the first response message to the MME through the first forwarding sub-channel carried in the first channel between the MME and the first eNodeB.

511-2: and the other nodes send the first response message to the second eNodeB through a second forwarding sub-channel between the second eNodeB and the other nodes.

Optionally, when the other node is a third eNodeB, the third eNodeB may send the first response message to the second eNodeB through a second forwarding sub-channel carried in a second channel between the second eNodeB and the third eNodeB.

Optionally, when the other node is an MME, the MME may send the first response message to the second eNodeB through a second forwarding sub-channel carried in a second channel between the second eNodeB and the MME.

512: the MCE transmits data to be transmitted to the second eNodeB to the first eNodeB.

513: the first eNodeB transmits the received data from the MCE to the second eNodeB through a specific message forwarding channel.

Specifically, the step may specifically include the following sub-steps:

513-1: the first eNodeB forwards the received data from the MCE to other nodes through a first forwarding sub-channel between the other nodes and the first eNodeB.

Optionally, when the other node is a third eNodeB, the first eNodeB may send the data from the MCE to the third eNodeB through a first forwarding sub-channel carried in a first channel between the third eNodeB and the first eNodeB.

Optionally, when the other node is an MME, the first eNodeB may send the data from the MCE to the MME through the first forwarding sub-channel carried in the first channel between the MME and the first eNodeB.

513-2: and the other nodes send the data from the MCE to the second eNodeB through a second forwarding sub-channel between the second eNodeB and the forwarding node.

Optionally, when the other node is a third eNodeB, the third eNodeB may send the data from the MCE to the second eNodeB through a second forwarding sub-channel carried in a second channel between the second eNodeB and the third eNodeB.

Optionally, when the other node is an MME, the MME may send the data from the MCE to the second eNodeB through a second forwarding sub-channel carried in a second channel between the second eNodeB and the MME.

In the above data communication method provided in this embodiment, a first eNodeB establishes a specific message forwarding channel between a second eNodeB and the first eNodeB, and when an M2 interface between the second eNodeB and an MCE fails and the second eNodeB cannot directly communicate with the MCE, the MCE may send latest time-frequency resource information sent to the second eNodeB to the first eNodeB, and after receiving the time-frequency resource information from the MCE, the first eNodeB sends the latest time-frequency resource information from the MCE to the second eNodeB through the specific message forwarding channel established between the first eNodeB and the second eNodeB. Similarly, the second eNodeB can also send the data to be sent to the MCE to the first eNodeB through the specific message forwarding channel, and the first eNodeB forwards the data sent by the second eNodeB to the MCE, so that when the M2 interface between the second eNodeB and the MCE fails, the second eNodeB and the MCE can still be guaranteed to perform normal communication, thereby avoiding the second eNodeB from interfering with cells managed by other normal enodebs, and also avoiding the waste of time-frequency resources allocated by the MCE for the second eNodeB.

Referring to fig. 6, another embodiment of the present invention provides a flowchart of a data communication method, which specifically includes the following steps:

601: the second eNodeB sends a fourth request message to the MCE, where the fourth request message is used to request establishment of an M2 interface between the second eNodeB and the MCE.

602: and when the second eNodeB does not receive the response of the MCE or receives error information returned by the MCE within a second preset time, sending an indication message to the first eNodeB, wherein the indication message is used for indicating that an M2 interface between the first eNodeB and the MCE is established.

Optionally, the indication message carries an identifier of the second eNodeB.

603: and after receiving the indication message sent by the second eNodeB, the first eNodeB generates a first request message according to the indication message.

604: the first eNodeB sends a first request message to the MCE.

605: after receiving the first request message sent by the first eNodeB, the MCE establishes the relationship between the first eNodeB and the second eNodeB according to the identifier of the first eNodeB and the identifier of the second eNodeB.

Optionally, the relationship between the first eNodeB and the second eNodeB may include: the first eNodeB is a forwarding node when the second eNodeB communicates with the MCE.

606: the MCE sends a first response message to the first eNodeB, where the first response message is used to indicate that the M2 interface between the first eNodeB and the MCE was successfully established.

607: the first eNodeB sends the first response message to the second eNodeB.

Optionally, the first eNodeB may send the first response message to the second eNodeB through an existing X2 channel established over an X2 interface between the first eNodeB and the second eNodeB, a private message channel established over a private interface, or an indirect channel.

For example, when the first eNodeB sends the first response message to the second eNodeB through an X2 channel established between the first eNodeB and the second eNodeB through an X2 interface, the step specifically includes:

the first eNodeB analyzes the received first response message, recombines the analyzed first response message into a first response cell conforming to the X2 interface protocol, and then sends the first response cell to the second eNodeB through an X2 channel established between the first eNodeB and the second eNodeB through an X2 interface.

In this embodiment, the form in which the first eNodeB sends the first response message to the second eNodeB is not limited to this, and is not illustrated here.

608: the MCE transmits data to be transmitted to the second eNodeB to the first eNodeB.

609: the first eNodeB transmits the received data from the MCE to the second eNodeB.

Optionally, a manner in which the first eNodeB sends the received data from the MCE to the second eNodeB in this step is the same as the manner in which the first eNodeB sends the first response message to the second eNodeB in step 607, and details are not repeated here.

In the method for data communication provided in this embodiment, when an M2 interface between the second eNodeB and the MCE fails to cause the second eNodeB to be unable to directly communicate with the MCE, the second eNodeB sends an indication message to the first eNodeB, the first eNodeB generates a first request message according to the indication message and sends the first request message to the MCE, and the MCE establishes a relationship between the first eNodeB and the second eNodeB according to an identifier of the first eNodeB and an identifier of the second eNodeB. In subsequent communication, the MCE may send data to be sent to the second eNodeB to the first eNodeB, and the first eNodeB parses the received data, reassembles the parsed data into a data cell conforming to a communication interface protocol between the first eNodeB and the second eNodeB, and sends the data cell to the second eNodeB. Similarly, the first eNodeB may also send the data sent by the second eNodeB to the MCE. It is realized that when the M2 interface between the second eNodeB and the MCE fails, the second eNodeB and the MCE can still be guaranteed to be normally on. Therefore, the interference of the second eNodeB to the cells managed by other normal eNodeBs is avoided, and the waste of the time-frequency resources distributed by the MCE to the second eNodeB is also avoided.

Another embodiment of the present invention provides an apparatus, which may be used to perform the steps performed by the first base station in the foregoing method embodiments, which are illustrated below. For example, referring to fig. 7, the first device 700 comprises a transmitting unit 701 and a receiving unit 702, wherein:

the sending unit 701 is configured to send a first request message to the MCE, so that the MCE can establish a relationship between the device and the second base station according to the identifier of the device and the identifier of the second base station, where the first request message is used to request an M2 interface between the device and the MCE, and the first request message carries the identifier of the device and the identifier of the second base station;

the receiving unit 702 is configured to receive a first response message sent by the MCE, where the first response message is used to indicate that the establishment of the M2 interface between the device and the MCE is successful, and the first response message carries an identifier of the device and an identifier of the second base station;

the sending unit 701 is further configured to send a first response message to the second base station after the receiving unit 702 receives the first response message sent by the MCE;

the receiving unit 702 is further configured to receive data sent by the MCE after the sending unit 701 sends the first response message to the second base station;

the sending unit 701 is further configured to send the data from the MCE to the second base station after the receiving unit 702 receives the data sent by the MCE.

Optionally, the receiving unit 702 is further configured to receive the first request message sent by the second base station before the sending unit 701 sends the first request message to the MCE.

Optionally, the receiving unit 702 is specifically configured to receive, through a specific message forwarding channel, a message sent by the second base station; the sending unit 701 is specifically configured to send a message and data to the second base station through a specific message forwarding channel; the receiving unit 702 is further specifically configured to receive data sent by the MCE through the M2 interface, and send the data from the MCE to the second base station through a specific message forwarding channel; the specific message forwarding channel is a channel which is dedicated to sending messages and data communicated between the second base station and the MCE between the equipment and the second base station.

Optionally, referring to fig. 8, the first device 700 provided in this embodiment further includes: an activating unit 703, configured to activate the specific message forwarding channel after the receiving unit 702 receives the second request message sent by the second base station, where the second request message is used to activate the specific message forwarding channel; moreover, the sending unit 701 is further configured to send a second response message to the second base station after the activating unit 703 activates the specific message forwarding channel, where the second response message is used to indicate that the specific message forwarding channel is successfully activated.

Optionally, the receiving unit 702 is further configured to receive a third request message sent by the second base station, where the third request message is used to establish a specific message forwarding channel;

optionally, referring to fig. 9, the first device 700 provided in this embodiment further includes: a establishing unit 704, configured to establish a specific message forwarding channel between the device and the second base station after the receiving unit 702 receives the third request message sent by the second base station.

Optionally, the receiving unit 702 is further configured to receive an indication message sent by the second base station before the sending unit 701 sends the first request message to the MCE, where the indication message is used to indicate an M2 interface between the established device and the MCE; the sending unit 701 is further configured to generate a first request message according to the indication message after the receiving unit 702 receives the indication message sent by the second base station.

Optionally, the first device is a base station.

Another embodiment of the present invention provides an apparatus, which may be used to perform the steps performed by the second base station in the foregoing method embodiments, which are illustrated below. For example, referring to fig. 10, the second device 800 includes a transmitting unit 801 and a receiving unit 802, in which:

the sending unit 801 is configured to send a first request message or an indication message to the first base station, so that the MCE receives the first request message forwarded by the first base station or the first request message generated according to the indication message, and establishes a relationship between the first base station and the device according to the identifier of the first base station and the identifier of the device; the first request message is used for requesting to establish an M2 interface between the first base station and the MCE, the first request message carries an identifier of the first base station and an identifier of the equipment, and the indication message is used for indicating to establish an M2 interface between the first base station and the MCE;

the receiving unit 802 is configured to receive an M2 first response message from the MCE sent by the first base station, where the first response message is used to indicate that the M2 interface between the first base station and the MCE is successfully established, and the first response message carries an identifier of the first base station and an identifier of the device;

the receiving unit 802 is further configured to receive data from the MCE sent by the first base station after receiving the M2 first response message from the MCE sent by the first base station.

Optionally, the receiving unit 802 is specifically configured to receive, through a specific message forwarding channel, a message sent by a device; the sending unit 801 is specifically configured to send a message and data to a device through a specific message forwarding channel; the specific message forwarding channel is a channel between the first base station and the equipment, which is dedicated for communication between the equipment to be sent and the MCE, and is used for transmitting messages and data.

Optionally, the sending unit 801 is further configured to send a second request message to the first base station before sending the first request message to the first base station, where the second request message is used to activate the specific message forwarding channel; the receiving unit 802 is further configured to receive a second response message sent by the first base station after the sending unit 801 sends the second request message to the first base station, where the second response message is used to indicate that the specific message forwarding channel is successfully activated.

Optionally, the sending unit 801 is further configured to send a third request message to the first base station before sending the second request message to the first base station, where the third request message is used to establish a specific message forwarding channel.

Optionally, the sending unit 801 is further configured to send a fourth request message to the MCE before sending the first request message to the first base station, where the fourth request message is used to establish an M2 interface between the device and the MCE, and the fourth request message carries an identifier of the device; the sending unit 801 is further configured to send a first request message to the first base station when the receiving unit 802 receives error information returned by the MCE or does not receive a response message of the MCE within a preset time.

Optionally, the second device in this embodiment is a base station.

Another embodiment of the present invention provides an apparatus, which can be used to perform the steps performed by the MCE in the above method embodiments, as exemplified below. Referring to fig. 11, the third device 900 specifically includes a receiving unit 901, a processing unit 902 and a sending unit 903, where:

the receiving unit 901 is configured to receive a first request message sent by a first base station, where the first request message is received by the first base station from a second base station or generated according to an indication message received from the second base station, where the first request message is used to request to establish an M2 interface between the first base station and a device, the first request message carries an identifier of the first base station and an identifier of the second base station, and the indication message is used to indicate to establish an M2 interface between the first base station and an MCE;

the processing unit 902 is configured to establish a relationship between the first base station and the second base station according to the identifier of the first base station and the identifier of the second base station;

the sending unit 903 is configured to send a first response message to the second base station through the first base station, where the first response message is used to indicate that the M2 interface between the first base station and the device is successfully established, and the first response message carries an identifier of the first base station and an identifier of the second base station;

the sending unit 903 is further configured to send data to the second base station via the first base station according to a relationship between the first base station and the second base station after sending the first response message to the second base station via the first base station.

Optionally, the processing unit 902 is specifically configured to establish a correspondence between an identifier of the first base station and an identifier of the second base station, where the correspondence indicates that the first base station is a forwarding node when the second base station communicates with the device.

Optionally, the third device in this embodiment is an MCE.

Referring to fig. 12, a system structure diagram for data communication according to another embodiment of the present invention is provided, where the system for data communication includes the first device 700, the second device 800, and the third device 900.

In the device provided in the foregoing embodiment, the sending unit and the receiving unit may be a sender and a receiver connected to an antenna or a cable, or may be combined into a transmitter connected to an antenna or a cable, and the present invention is not limited thereto.

In the apparatus and system for data communication provided in this embodiment, when the M2 interface between the second eNodeB and the MCE fails, and the second eNodeB cannot directly communicate with the MCE, the MCE may send data sent to the second eNodeB to the first eNodeB, and the first eNodeB sends data from the MCE to the second eNodeB after receiving the data from the MCE. Similarly, the second eNodeB can also send the data to be sent to the MCE to the first eNodeB, and the first eNodeB sends the data sent by the second eNodeB to the MCE, so that when the M2 interface between the second eNodeB and the MCE fails, the second eNodeB and the MCE can still be guaranteed to perform normal communication, thereby avoiding the second eNodeB from interfering with the cell managed by other normal enodebs, and also avoiding the waste of the time-frequency resources allocated by the MCE for the second eNodeB.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.

Claims

1. A method of data communication, comprising:

a first base station sends a first request message to a multi-cell/Multicast Coordination Entity (MCE) so that the MCE establishes a relationship between the first base station and a second base station according to an identifier of the first base station and an identifier of the second base station, wherein the first request message is used for requesting to establish an M2 interface between the first base station and the MCE, and the first request message carries the identifier of the first base station and the identifier of the second base station;

the first base station receives a first response message sent by the MCE, where the first response message is used to indicate that the M2 interface between the first base station and the MCE is successfully established, and the first response message carries an identifier of the first base station and an identifier of the second base station;

the first base station sends the first response message to the second base station;

2. The method of claim 1, wherein before the first base station sends the first request message to the MCE, the method further comprises:

and the first base station receives the first request message sent by the second base station.

3. The method of claim 2,

the first base station receives the first request message sent by the second base station through a specific message forwarding channel;

the first base station sends the first response message to the second base station through the specific message forwarding channel;

the first base station receives the data sent by the MCE through the M2 interface, and sends the data from the MCE to the second base station through the specific message forwarding channel;

wherein the specific message forwarding channel is a channel dedicated to sending messages and data communicated between the second base station and the MCE between the first base station and the second base station.

4. The method of claim 3, before the first base station receives the first request message sent by the second base station, further comprising:

the first base station receives a second request message sent by the second base station, wherein the second request message is used for activating the specific message forwarding channel;

and the first base station activates the specific message forwarding channel and sends a second response message to the second base station, wherein the second response message is used for indicating that the specific message forwarding channel is successfully activated.

5. The method of claim 4, wherein before the first base station receives the second request message sent by the second base station, the method further comprises:

the first base station receives a third request message sent by the second base station, wherein the third request message is used for establishing the specific message forwarding channel;

the first base station establishes the specific message forwarding channel between the first base station and the second base station.

6. The method according to any of claims 3-5, wherein the specific message forwarding channel is carried in an X2 channel established between the first base station and the second base station over an X2 interface; or,

the specific message forwarding channel is carried in a private message channel established between the first base station and the second base station through a private interface.

7. The method according to any of claims 3-5, wherein when the message is sent between the first base station and the second base station via another node, the specific message forwarding channel is carried in a first channel established between the other node and the first base station over an S1 interface, an X2 interface, or a private interface, and a second channel established between the second base station and the other node over an S1 interface, an X2 interface, or a private interface.

8. The method of claim 1, wherein before the first base station sends the first request message to the MCE, the method further comprises:

the first base station receives an indication message sent by the second base station, wherein the indication message is used for indicating that an M2 interface between the first base station and the MCE is established;

and the first base station generates a first request message according to the indication message.

9. The method of any one of claims 1, 2 or 8, wherein the relationship between the first base station and the second base station comprises: the first base station is a forwarding node when the second base station communicates with the MCE.

10. A method of data communication, comprising:

the second base station sends a first request message or an indication message to the first base station, so that a multi-cell/Multicast Coordination Entity (MCE) receives the first request message forwarded by the first base station or a first request message generated according to the indication message, and establishes a relationship between the first base station and the second base station according to an identifier of the first base station and an identifier of the second base station; the first request message is used for requesting to establish an M2 interface between the first base station and the MCE, the first request message carries an identifier of the first base station and an identifier of the second base station, and the indication message is used for indicating to establish an M2 interface between the first base station and the MCE;

the second base station receives an M2 first response message from the MCE sent by the first base station, where the first response message is used to indicate that the establishment of an M2 interface between the first base station and the MCE is successful, and the first response message carries an identifier of the first base station and an identifier of the second base station;

11. The method of claim 10, wherein when the second base station sends the first request message to the first base station, the second base station sends the first request message to the first base station through a specific message forwarding channel;

the second base station receives a first response message from the MCE, which is sent by the first base station through the specific message forwarding channel;

the second base station receives data from the MCE, which is sent by the first base station through the specific message forwarding channel;

12. The method of claim 11, wherein the relationship between the first base station and the second base station comprises: the first base station is a forwarding node when the second base station communicates with the MCE.

13. The method of claim 11, wherein before the second base station sends the first request message to the first base station, the method further comprises:

the second base station sends a second request message to the first base station, wherein the second request message is used for activating the specific message forwarding channel;

and the second base station receives a second response message sent by the first base station, wherein the second response message is used for indicating that the specific message forwarding channel is successfully activated.

14. The method of claim 13, prior to the second base station sending the second request message to the first base station, further comprising:

and the second base station sends a third request message to the first base station, wherein the third request message is used for establishing the specific message forwarding channel.

15. The method according to any of claims 11-14, wherein the specific message forwarding channel is carried in an X2 channel established between the first base station and the second base station over an X2 interface; or,

the specific message forwarding channel is carried in a channel established between the first base station and the second base station through a private interface.

16. The method according to any of claims 11-14, wherein when said message is sent between said first base station and said second base station via another node, said specific message forwarding channel is carried in a first channel established between said another node and said first base station over an S1 interface, an X2 interface, or a private interface, and a second channel established between said second base station and said another node over an S1 interface, an X2 interface, or a private interface.

17. The method of claim 10, wherein before the second base station sends the first request message to the first base station, the method further comprises: the second base station sends a fourth request message to the MCE, where the fourth request message is used to establish an M2 interface between the second base station and the MCE, and the fourth request message carries an identifier of the second base station;

and if the second base station receives the error information returned by the MCE or does not receive the response message of the MCE within the preset time, the second base station sends a first request message to the first base station.

18. A method of data communication, comprising:

a multi-cell/Multicast Coordination Entity (MCE) receives a first request message sent by a first base station, wherein the first request message is received by the first base station from a second base station or generated according to an indication message received from the second base station, the first request message is used for requesting to establish an M2 interface between the first base station and the MCE, the first request message carries an identifier of the first base station and an identifier of the second base station, and the indication message is used for indicating to establish an M2 interface between the first base station and the MCE;

the MCE establishes the relationship between the first base station and the second base station according to the identification of the first base station and the identification of the second base station;

the MCE sends a first response message to the second base station via the first base station, where the first response message is used to indicate that the establishment of the M2 interface between the first base station and the MCE is successful, and the first response message carries an identifier of the first base station and an identifier of the second base station;

and the MCE sends data to the second base station through the first base station according to the relation between the first base station and the second base station.

19. The method of claim 18, wherein the MCE establishes the relationship between the first base station and the second base station according to the identifier of the first base station and the identifier of the second base station, and specifically comprises:

and the MCE stores the corresponding relation between the identifier of the first base station and the identifier of the second base station, wherein the corresponding relation indicates that the first base station is a forwarding node when the second base station communicates with the MCE.

20. An apparatus for data communication, comprising a transmitting unit and a receiving unit, wherein:

the sending unit is configured to send a first request message to a multi-cell/multicast coordination entity MCE, so that the MCE establishes a relationship between the device and a second base station according to an identifier of the device and an identifier of the second base station, where the first request message is used to request establishment of an M2 interface between the device and the MCE, and the first request message carries the identifier of the device and the identifier of the second base station;

the receiving unit is configured to receive a first response message sent by the MCE, where the first response message is used to indicate that establishment of an M2 interface between the device and the MCE is successful, and the first response message carries an identifier of the device and an identifier of the second base station;

21. The apparatus for data communication according to claim 20, wherein the receiving unit is further configured to receive the first request message sent by the second base station before the sending unit sends the first request message to the MCE.

22. The apparatus for data communication according to claim 21,

the receiving unit is specifically configured to receive, through a specific message forwarding channel, a message sent by the second base station;

the sending unit is specifically configured to send a message and data to the second base station through the specific message forwarding channel;

the receiving unit is further specifically configured to receive data sent by the MCE through the M2 interface;

the sending unit is further specifically configured to send the data from the MCE to the second base station through the specific message forwarding channel after the receiving unit receives the data sent by the MCE;

wherein the specific message forwarding channel is a channel dedicated to sending messages and data communicated between the second base station and the MCE between the apparatus and the second base station.

23. The apparatus for data communication according to claim 22, wherein said apparatus further comprises:

an activating unit, configured to activate the specific message forwarding channel after the receiving unit receives a second request message sent by the second base station, where the second request message is used to activate the specific message forwarding channel;

the sending unit is further configured to send a second response message to the second base station after the activating unit activates the specific message forwarding channel, where the second response message is used to indicate that the specific message forwarding channel is successfully activated.

24. The apparatus for data communication according to claim 23, wherein the receiving unit is further configured to receive a third request message sent by the second base station, where the third request message is used to establish the specific message forwarding channel;

the device further comprises:

and the establishing unit is used for establishing the specific message forwarding channel between the device and the second base station after the receiving unit receives the third request message sent by the second base station.

25. The apparatus for data communication according to claim 20, wherein the receiving unit is further configured to receive an indication message sent by the second base station before the sending unit sends the first request message to the MCE, where the indication message is used to indicate that an M2 interface between the apparatus and the MCE is established;

the sending unit is further configured to generate a first request message according to the indication message after the receiving unit receives the indication message sent by the second base station.

26. A data communication device according to any of claims 20-25, wherein said device is a base station.

27. An apparatus for data communication, comprising a transmitting unit and a receiving unit, wherein:

the sending unit is configured to send a first request message or an indication message to a first base station, so that a multi-cell/multicast coordination entity MCE receives the first request message forwarded by the first base station or a first request message generated according to the indication message, and establishes a relationship between the first base station and the device according to an identifier of the first base station and an identifier of the device; the first request message is used to request to establish an M2 interface between the first base station and the MCE, the first request message carries an identifier of the first base station and an identifier of the device, and the indication message is used to indicate to establish an M2 interface between the first base station and the MCE;

the receiving unit is configured to receive an M2 first response message from the MCE sent by the first base station, where the first response message is used to indicate that an M2 interface between the first base station and the MCE is successfully established, and the first response message carries an identifier of the first base station and an identifier of the device;

28. The apparatus for data communication according to claim 27,

the receiving unit is specifically configured to receive, through a specific message forwarding channel, a message sent by the first base station;

the sending unit is specifically configured to send a message and data to the first base station through the specific message forwarding channel;

wherein, the specific message forwarding channel is a channel dedicated to sending messages and data communicated between the device and the MCE between the first base station and the device.

29. The apparatus for data communication according to claim 28, wherein the sending unit is further configured to send a second request message to the first base station before sending the first request message to the first base station, where the second request message is used to activate the specific message forwarding channel;

the receiving unit is further configured to receive a second response message sent by the first base station after the sending unit sends a second request message to the first base station, where the second response message is used to indicate that the specific message forwarding channel is successfully activated.

30. The apparatus for data communication according to claim 29, wherein the sending unit is further configured to send a third request message to the first base station before sending the second request message to the first base station, and the third request message is used to establish the specific message forwarding channel.

31. The apparatus for data communication according to claim 27, wherein the sending unit is further configured to send a fourth request message to the MCE before sending the first request message to the first base station, where the fourth request message is used to establish an M2 interface between the apparatus and the MCE, and the fourth request message carries an identifier of the apparatus;

the sending unit is further configured to send a first request message to the first base station when the receiving unit receives the error information returned by the MCE or does not receive the response message of the MCE within a preset time.

32. A data communication device according to any of claims 27 to 31, wherein the device is a base station.

33. An apparatus for data communication, comprising a receiving unit, a processing unit and a transmitting unit, wherein:

the receiving unit is configured to receive a first request message sent by a first base station, where the first request message is received by the first base station from a second base station or generated according to an indication message received from the second base station, where the first request message is used to request establishment of an M2 interface between the first base station and the apparatus, the first request message carries an identifier of the first base station and an identifier of the second base station, and the indication message is used to indicate establishment of an M2 interface between the first base station and a multi-cell/multicast coordination entity MCE;

the processing unit is used for establishing the relationship between the first base station and the second base station according to the identifier of the first base station and the identifier of the second base station;

the sending unit is configured to send a first response message to the second base station via the first base station, where the first response message is used to indicate that the M2 interface between the first base station and the apparatus is successfully established, and the first response message carries an identifier of the first base station and an identifier of the second base station;

the sending unit is further configured to send data to the second base station via the first base station according to a relationship between the first base station and the second base station after sending the first response message to the second base station via the first base station.

34. The apparatus for data communication according to claim 33,

the processing unit is specifically configured to establish a correspondence between the identifier of the first base station and the identifier of the second base station, where the correspondence indicates that the first base station is a forwarding node when the second base station communicates with the device.

35. Device for data communication according to any of the claims 33-34, wherein said device is a multi-cell/multicast coordination entity, MCE.

36. A system for data communication, comprising the apparatus of claims 20-26, the apparatus of claims 27-32 and the apparatus of claims 33-35.