WO2016041441A1 - Method for sending data, device and storage medium - Google Patents

Abstract

Disclosed is a method for sending data. The method comprises: when a multi-cell/multicast coordination entity (MCE) confirms that a physical multicast channel does not exist, forming a multimedia broadcast multicast service (MBMS) pseudo session, the MBMS pseudo session being used for sending data by a base station (eNB). Also disclosed are another method for sending data, an eNB, an MCE and a storage medium.

Description

Data transmitting method, device and storage medium Technical field

The present invention relates to signal processing technologies in mobile communications, and in particular, to a data transmission method, device, and storage medium.

Background technique

With the development of mobile Internet and large-screen mobile terminals, more and more mobile terminal users choose to process multimedia information services on the mobile terminal side, such as video conferences, live events, and online education. Compared with ordinary data services, multimedia information services have the characteristics of high bandwidth occupation, long duration, sensitive time delay, and relatively fixed transmission content. In order to effectively utilize spectrum resources, the 3rd Generation Partnership Project (3GPP) organization proposed Multimedia Broadcast Multicast Service (MBMS), which is a point-to-multiple service. That is, the data source is one and the data receiving target is multiple; the MBMS service can realize network resource sharing and improve the utilization rate of the frequency domain resource of the wireless access network.

In the Long Term Evolution (LTE) system, the MBMS service is called an evolved-Multimedia Broadcast Multicast Service (eMBMS).

In the eMBMS service, according to the 3GPP TS36300 protocol specification, a Multicast Control Channel (MCCH) and a Multicast Transmission Channel (MTCH) on an evolved NodeB (eNB) side are multiplexed in multicast. On the Multicast Channel (MCH), the MCH is mapped on the Physical Multicast Channel (PMCH), so the MCCH and the MTCH are multiplexed on the PMCH. When the PMCH carrying the MCCH on the eNB side does not exist, The number of PMCHs that cause the eNB side to stop According to the transmission, the data of the MCCH cannot be sent.

Summary of the invention

In view of the above, the embodiment of the present invention is to provide a data transmission method, a device, and a storage medium. When the PMCH carrying the MCCH on the eNB side does not exist, the data of the MCCH can be normally transmitted.

The technical solution of the embodiment of the present invention is implemented as follows:

An embodiment of the present invention provides a data sending method, including: a Multi-cell/Multicast Coordination Entity (MCE), when an PMCH carrying a MCCH does not exist, forming an MBMS pseudo session; the MBMS pseudo The session is used by the eNB for data transmission.

In an embodiment, the confirming that the PMCH carrying the MCCH does not exist includes: when the MCE receives the MBS Session Stop Request (SESSION STOP REQUEST) message or the MCCH update, the MCE checks that the PMCH carrying the MCCH does not have the MTCH, and confirms the PMCH carrying the MCCH. does not exist.

In an embodiment, the forming an MBMS pseudo session includes:

After the MCE deletes the context of the MBMS session or the MCCH update according to the received MBMS SESSION STOP REQUEST message, the MCE constructs an MBMS pseudo session and sets a Temporary Mobile Group ID (TMGI) of the MBMS pseudo session; Or, when the MCE receives the MBMS SESSION STOP REQUEST message or the MCCH update, the MCE keeps an MBMS session from being suspended, and sets the TMGI of the reserved MBMS session.

In an embodiment, when the forming an MBMS pseudo session to construct an MBMS pseudo session for the MCE, the method further includes: the MCE transmitting an MBMS scheduling information indication (SCHEDULING INFORMATION) message including the TMGI of the MBMS pseudo session, and receiving MBMSSCHEDULING INFORMATION RESPONSE message; or, MCE sends a packet The MBS Session START REQUEST message of the TMGI containing the MBMS pseudo session receives an SMSSION START REQUEST RESPONSE message.

In an embodiment, when the forming an MBMS pseudo session to reserve an MBMS session for the MCE is not suspended, the method further includes: the MCE receiving the MBMS SESSION START REQUEST message; wherein the MBMS SESSION START REQUEST message is When the MBMS session and the MCCH are carried on the same PMCH, the MCE performs context update processing on the reserved MBMS session; the MBMS session in the MBMS SESSION START REQUEST message is carried on a different PMCH, and the MBMS SESSION When the TMGI of the MBMS in the START REQUEST message is the same as the TMGI of the reserved MBMS session, the MCE replaces the TMGI of the reserved MBMS session with the TMGI of an idle MBMS session for the reserved MBMS session and the MBMS. The MBMS session in the SESSION START REQUEST message performs context update processing.

In an embodiment, before the sending the MBMS SCHEDULING INFORMATION message, the method further includes: the MCE sends an MBMS SESSION START REQUEST message, and receives an MBMS SESSION START RESPONSE message; the MBMSSESSION START REQUEST message includes the MBMS pseudo session TMGI.

The embodiment of the present invention further provides a data sending method, including: receiving, by an eNB, a message including a TMGI of an MBMS pseudo session, and establishing a context of an MBMS pseudo session according to the MTCH corresponding to the MBMS pseudo session in the received message; During the scheduling, configure and send a Media Access Control Scheduling Instructions (MSI) message; and send a Multicast/Multicast Single Frequency Network (MBSFN) Area Configuration message. .

In an embodiment, before the eNB configures the MSI message, the method further includes: the eNB sending a response message of the message of the TMGI including the MBMS pseudo session.

In an embodiment, the configuring the MSI message includes: configuring an MTCH indication value corresponding to the MBMS pseudo session, indicating that the MTCH is not scheduled.

In an embodiment, before the eNB receives the MBMS SCHEDULING INFORMATION message, the method further includes: receiving, by the eNB, an MBS Session START REQUEST message, and transmitting an MBMS SESSION START RESPONSE message.

An embodiment of the present invention further provides an MCE, including: a confirmation module and a formation module; wherein

The confirmation module is configured to confirm whether a PMCH carrying the MCCH exists;

The forming module is configured to form an MBMS pseudo session when the acknowledgment module confirms that the PMCH carrying the MCCH does not exist; and the MBMS pseudo session is used by the eNB to perform data transmission.

In an embodiment, the acknowledgment module is configured to: when receiving the MBMS SESSION STOP REQUEST message or the MCCH update, check that the PMCH carrying the MCCH does not have an MTCH, and confirm that the PMCH carrying the MCCH does not exist.

In an embodiment, the forming module is configured to construct an MBMS pseudo session after setting the MBMS session status or the MCCH update according to the received MBMS SESSION STOP REQUEST, and set the TMGI of the MBMS pseudo session. Or, when receiving the MBMS to SESSION STOP REQUEST message or MCCH update, keep an MBMS session unsuspended and set the TMGI of the reserved MBMS session.

In an embodiment, the MCE further includes: a first sending module and a first receiving module; wherein

The first sending module is configured to send an MBMS SCHEDULING INFORMATION message of the TMGI including the MBMS pseudo session; the first receiving module is configured to receive an MBMS SCHEDULING INFORMATION RESPONSE message; or the first sending module, configured To send an MBMS SESSION START REQUEST message of the TMGI containing the MBMS pseudo session; the first receiving module is configured to receive an MBMS SESSION START RESPONSE message.

In an embodiment, the MCE further includes: a second receiving module and a first processing module; wherein

The second receiving module is configured to receive an MBMS SESSION START REQUEST message;

The first processing module is configured to perform context update processing on the reserved MBMS session when the MBMS session in the MBMS SESSION START REQUEST message is carried on the same PMCH; the MBMS SESSION START REQUEST message When the MBMS session and the MCCH are carried on different PMCHs, and the TMGI of the MBMS session in the MBMS SESSION START REQUEST message is the same as the TMGI of the reserved MBMS session, the reservation is replaced with the TMGI of an idle MBMS session. The TMGI of the MBMS session performs context update processing on the reserved MBMS session and the MBMS session in the MBMS SESSION START REQUEST message.

In an embodiment, the MCE further includes: a second sending module and a third receiving module; wherein

The second sending module is configured to send an MBMS SESSION START REQUEST message;

The third receiving module is configured to receive an MBMS SESSION START RESPONSE message.

An embodiment of the present invention further provides an eNB, including: a fourth receiving module, an establishing module, a second processing module, and a third sending module;

The fourth receiving module is configured to receive a message including a TMGI of the MBMS pseudo session;

The establishing module is configured to establish a context of the MBMS pseudo session according to the MTCH corresponding to the MBMS pseudo session in the received message;

The second processing module is configured to configure and send an MSI message when scheduling the MBMS pseudo session;

The third sending module is configured to send an MBSFN Area Configuration message.

In an embodiment, the third sending module is further configured to send a response message of the message of the TMGI including the MBMS pseudo session.

In an embodiment, the second processing module is configured to configure an MTCH indication value corresponding to the MBMS pseudo session, indicating that the MTCH is not scheduled.

In an embodiment, the eNB further includes: a fourth sending module and a fifth receiving module; wherein

The fifth receiving module is configured to receive an MBMS SESSION START REQUEST message;

The fourth sending module is configured to send an MBMS SESSION START RESPONSE message.

The embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores a computer program, and the computer program is used to execute the data sending method of the embodiment of the present invention.

The data transmission method, device, and storage medium provided by the embodiment of the present invention, when the MCE confirms that the bearer MCCH does not exist, forms an MBMS pseudo session; the MBMS pseudo session is used for eNB to perform data transmission; and the eNB receives the MBMS pseudo session. The message of the TMGI, the context of the MBMS pseudo session is established according to the MTCH corresponding to the MBMS pseudo session in the received message; when the MBMS pseudo session is scheduled, the MSI message is configured, and the MSI message and the MBSFN Area Configuration message are sent to the UE; In the embodiment, when the MCE confirms that the PMCH carrying the MCCH does not exist, the MCE constructs an MBMS pseudo session or keeps an MBMS session from being suspended, so that an MBMS session exists on the PMCH, and the MCCH data can be normally transmitted.

DRAWINGS

FIG. 1 is a schematic diagram of deployment of a service area, a synchronization area, and an MBSFN area of an LTE eMBMS service;

2 is a logical architecture diagram of an LTE eMBMS service;

3 is a schematic flowchart of a basic processing procedure of a data transmission method on an MCE side according to an embodiment of the present invention;

4 is a schematic flowchart of a basic processing process of an eNB side data sending method according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart of detailed processing of a data sending method according to an embodiment of the present invention; FIG.

6 is a schematic flowchart of detailed processing of a data sending method according to Embodiment 2 of the present invention;

FIG. 7 is a schematic flowchart of detailed processing of a data sending method according to Embodiment 3 of the present invention; FIG.

FIG. 8 is a schematic structural diagram of a structure of an MCE according to an embodiment of the present invention; FIG.

FIG. 9 is a schematic structural diagram of a structure of an eNB according to an embodiment of the present invention.

detailed description

To better understand the technical solution of the embodiment of the present invention, the LTE eMBMS service is described in detail below. Schematic diagram of the deployment of the service area, the synchronization area, and the MBSFN area of the LTE eMBMS service is shown in Figure 1. The logical architecture diagram of the LTE eMBMS service is shown in Figure 2, where M1 is the user plane interface and M2 is the E-UTRAN internal. Control plane interface, M3 is E-UTRAN and EPC control plane interface, MBMS GW is MBMS gateway; MCE is responsible for management of MBMS session, including: admission control of MBMS session, radio resource allocation in time domain, and cells in MBSFN area Coordinated transmission of MBMS data, wireless configuration of modulation and coding mode parameters of each channel, and the like.

In the LTE eMBMS service, each MBSFN area has one MCCH, zero or more MTCHs, and the MTCHs are multiplexed on the same or different MCHs; wherein each MTCH corresponds to one MBMS session.

In the LTE eMBMS service, the interface related to the control plane includes the M3 interface and the M2 interface. The M3 interface is an interface between the Mobility Management Entity (MME) and the MCE, and the M2 interface is between the MCE and the eNB. The MCE transmits the relevant configuration parameters to the eNB through the M2 interface, and the eNB performs the System Information Block Type 2 message, the System Information Block Type 13 message, the MBSFN Area Configuration message, and the scheduling and sending of the MBMS data according to the received related parameters; , System Information Block Type 13 message indicates the MCCH related configuration of the cell and the MCCH The allocation information of the MBSFN subframe in the MBSFN Area Configuration message indicates the specific content of the MCCH, including: allocation information of the common subframe in the MBSFN area in the cell, configuration information of the PMCH, information of each MTCH, and the like.

In the LTE eMBMS service, the scenario in which the data of the MCCH cannot be transmitted due to the absence of the PMCH carrying the MCCH on the eNB side is that there is no MBMS session on the PMCH carrying the MCCH on the MCE side, or there is no MBMS session on the MCE side, according to 3GPP TS36443-b309. Section 1.7 specifies that the MBMS SCHEDULING INFORMATION message sent through the M2 port does not support the case where the number of MBMS sessions on the PMCH is 0. It is assumed that the MCCH bearer is sent on a certain PMCH, but there is no MBMS session on the PMCH. When the information is notified to the eNB, the PMCH needs to be carried in the MBMS SCHEDULING INFORMATION message, and the number of MTCHs in the PMCH is 0; however, the requirement that the number of sessions included in the MBMS SCHEDULING INFORMATION in the 3GPP TS36443-b30 protocol is at least 1 is conflicted; Therefore, when there is no MTCH on the PMCH carrying the MCCH on the MCE side, the MBMS SCHEDULING INFORMATION message sent through the M2 port cannot carry the PMCH.

The basic processing flow of the MCE side data sending method in the embodiment of the present invention, as shown in FIG. 3, includes the following steps:

Step 101: The MCE confirms that the PMCH carrying the MCCH does not exist.

Specifically, when the MCE receives the MBMS Session Stop Request message or the MCCH update sent by the MME, the MCE checks that the PMCH carrying the MCCH does not have an MTCH, and confirms that the PMCH carrying the MCCH does not exist.

Step 102, forming an MBMS pseudo session;

Specifically, after the MCE deletes the context of the MBMS session or the MCCH update according to the received MBMS session stop request message, the MCE constructs an MBMS pseudo session, and sets the temporary mobile group identifier TMGI of the MBMS pseudo session to TMGI-FAKE;

When the MCE receives the MBMS Session Stop Request message or the MCCH update, the MCE keeps an MBMS session from being suspended, and sets the TMGI of the reserved MBMS session to TMGI-RESEVED.

In the embodiment of the present invention, when the forming an MBMS pseudo session is an MCE to construct an MBMS pseudo session, the method further includes:

Step 103: The MCE sends an MBMS SCHEDULING INFORMATION message containing the TMGI of the MBMS pseudo session, and receives an MBMS SCHEDULING INFORMATION RESPONSE message. Alternatively, the MCE sends an MBMS SESSION START REQUEST message containing the TMGI of the MBMS pseudo session, and receives the MBS session SESSION START. RESPONSE message.

In the embodiment of the present invention, when the forming an MBMS pseudo session to reserve an MBMS session for the MCE is not suspended, the method further includes:

Step 103, after the MCE receives the MBMS SESSION START REQUEST message sent by the MME, where

When the MBMS session in the MBMS SESSION START REQUEST message is carried on the same PMCH as the MCCH, the MCE performs context update processing on the reserved MBMS session; and the implementation process of performing the context update processing on the reserved MBMS session includes:

The MCE sends an MBMS SESSION STOP REQUEST message to the eNB, where the MBMS SESSION STOP REQUEST message carries the context of the reserved session; receives the MBS Session Stop Response (SESSION STOP RESPONSE) message sent by the eNB; and sends an MBMS SESSION START REQUEST message to the eNB, The MBMS SESSION START REQUEST message carries the context of the new session and receives the MBMS SESSION START RESPONSE message.

The MBMS session in the MBS session SESSION START REQUEST When the MCCH is carried on different PMCHs, and the TMGI of the MBMS session in the MBMS Session Start Request message is the same as the TMGI of the reserved MBMS session, the MCE replaces the reserved MBMS session with the TMGI of an idle MBMS session. TMGI, performing context update processing on the reserved MBMS session and the MBMS session in the MBMS Session Start Request message; performing context update processing on the MBMS session in the MBMS session and the MBMS session in the MBMS Session Start Request message The implementation process includes:

The MCE sends an MBMS SESSION STOP REQUEST message to the eNB, where the MBMS SESSION STOP REQUEST message carries the context of the reserved MBMS session; receives the MBMS SESSION STOP RESPONSE message sent by the eNB; and sends an MBMS SESSION START REQUEST message to the eNB, the MBMS SESSION START The REQUEST message carries the context of the idle MBMS session, receives the MBMS SESSION START RESPONSE message sent by the eNB, and sends an MBMS SESSION START REQUEST message to the eNB, where the MBMS SESSION START REQUEST message carries the context of the new session, and receives the MBMS SESSION START RESPONSE message.

The basic processing flow of the eNB side data sending method in the embodiment of the present invention, as shown in FIG. 4, includes the following steps:

Step 201: The eNB receives a message including a TMGI of an MBMS pseudo session.

Specifically, the eNB receives the MBMS SCHEDULING INFORMATION message sent by the MCE through the M2 interface, where the MBMS SCHEDULING INFORMATION message includes the TMGI of the MBMS pseudo session; or the eNB receives the MBMS SESSION START REQUEST message sent by the MCE through the M2 interface, where the MBMS SESSION The START REQUEST message contains the TMGI of the MBMS pseudo session.

Step 202: The eNB establishes a context of the MBMS pseudo session according to the MTCH corresponding to the MBMS pseudo session in the received message.

Step 203: When scheduling the MBMS pseudo session, the eNB configures and sends the MSI cancellation. interest;

Specifically, the scheduler in the eNB sets the STOP indication value in the logical channel corresponding to the MBMS pseudo session in the MSI message to 2047 when performing data scheduling, indicating that the MTCH is not scheduled, and sends the configured MSI message to the UE. .

In step 204, the eNB sends an MBSFN Area Configuration message.

Embodiment 1

The detailed processing flow of the data sending method in the first embodiment of the present invention, as shown in FIG. 5, includes the following steps:

Step 301, the MCE confirms that the PMCH carrying the MCCH does not exist, forming a pseudo session;

Specifically, after deleting the context of the MBMS session or the MCCH update according to the received MBMS SESSION STOP REQUEST message, the MCE checks that the PMCH carrying the MCCH does not have an MTCH, and confirms that the PMCH carrying the MCCH does not exist; constructs an MBMS pseudo session, and The TMGI of the MBMS pseudo session is set to TMGI-FAKE.

Step 302: The MCE sends an MBMS SCHEDULING INFORMATION message to the eNB.

Here, the TMGI including the MBMS pseudo session in the MBMS SCHEDULING INFORMATION message is TMGI-FAKE.

In step 303, the eNB sends an MBMS SCHEDULING INFORMATION RESPONSE message to the MCE.

Step 304: The eNB establishes a context of the MBMS pseudo session according to the MTCH corresponding to the MBMS pseudo session in the MBMS SCHEDULING INFORMATION.

Step 305, the eNB configures and sends an MSI message.

Specifically, the scheduler in the eNB sets the STOP indication value in the logical channel corresponding to the MBMS pseudo session in the MSI message to 2047 when performing data scheduling, indicating that the MTCH is not Scheduling, sending the configured MSI message to the UE.

In step 306, the eNB sends an MBSFN Area Configuration message to the UE.

Embodiment 2

A schematic flowchart of the detailed processing of the data sending method in the second embodiment of the present invention, as shown in FIG. 6, includes the following steps:

Step 401: The MCE confirms that the PMCH carrying the MCCH does not exist, forming a pseudo session.

Specifically, after deleting the context of the MBMS session or the MCCH update according to the received MBMS MBMS SESSION STOP REQUEST message, the MCE checks that the PMCH carrying the MCCH does not have an MTCH, and confirms that the PMCH carrying the MCCH does not exist; constructs an MBMS pseudo session, And setting the TMGI of the MBMS pseudo session to TMGI-FAKE.

Step 402: The MCE sends an MBMS SESSION START REQUEST message to the eNB.

Here, the TMGI including the MBMS pseudo session in the MBMS SESSION START REQUEST message is TMGI-FAKE.

In step 403, the eNB sends an MBMS SESSION START RESPONSE message to the MCE.

Step 404: The MCE sends an MBMS SCHEDULING INFORMATION message to the eNB.

Here, the PMCH for carrying the MCCH in the MBMS SCHEDULING INFORMATION message includes the MTCH corresponding to the MBMS pseudo session.

In step 405, the eNB sends an MBMS SCHEDULING INFORMATION RESPONSE message to the MCE.

Step 406: The eNB establishes a context of the MBMS pseudo session according to the MTCH corresponding to the MBMS pseudo session in the MBMS SCHEDULING INFORMATION message.

Step 407, the eNB configures and sends an MSI message.

Specifically, the MAC scheduler in the eNB will perform the MBMS pseudo session in the MSI message when scheduling. The STOP indication value in the corresponding logical channel is set to 2047, indicating that the MTCH is not scheduled, and the configured MSI message is sent to the UE.

In step 408, the eNB sends an MBSFN Area Configuration message to the UE.

Embodiment 3

A detailed processing flow diagram of the data transmission method in the third embodiment of the present invention, as shown in FIG. 7, includes the following steps:

In step 501, the MME sends an MBMS SESSION STOP REQUEST message to the MCE.

Step 502: The MCE confirms that the PMCH carrying the MCCH does not exist, forming a pseudo session.

Specifically, the MCE checks that the PMCH carrying the MCCH does not have an MTCH, and confirms that the PMCH carrying the MCCH does not exist; keeps one MBMS session from being suspended, and sets the TMGI of the reserved MBMS session to TMGI-RESEVED.

In step 503, the MCE sends an MBMS SESSION STOP RESPONSE message to the MME.

In step 504, the MME sends an MBMS SESSION START REQUEST message to the MCE.

Step 505: The MCE sends an MBMS SESSION START RESPONSE message to the MME.

When the MBMS session in the MBMS SESSION START request message is on the same PMCH as the MCCH, the MCE performs context update processing on the reserved MBMS session, that is, step 506, step 507, step 508, and step 509 are sequentially performed;

When the MBMS session and the MCCH in the MBMS SESSION START request message are carried on different PMCHs, and the TMGI of the MBMS in the MBMS Session Start Request message is the same as the TMGI of the reserved MBMS session, the MCE uses one idle. The TMGI replacement TMGI-RESEVED of the MBMS session performs context update processing on the MBMS session and the MBMS session in the MBMS session start request message, that is, step 506, step 507, step 508', and step 509 are sequentially performed. ', step 508 and step 509.

Step 506: The MCE sends an MBMS SESSION STOP REQUEST message to the eNB.

The MBMS SESSION STOP REQUEST message carries the context of the reserved MBMS session.

Step 507: The MCE receives the MBMS SESSION STOP RESPONSE message sent by the eNB.

Step 508', the MCE sends an MBMS SESSION START REQUEST message to the eNB;

The MBMS SESSION START REQUEST message carries the context of the idle MBMS session.

In step 509', the MCE receives the MBMS SESSION START RESPONSE message sent by the eNB.

Step 508: The MCE sends an MBMS SESSION START REQUEST message to the eNB.

The MBMS SESSION START REQUEST message carries the context of the new session.

In step 509, the MCE receives the MBMS SESSION START RESPONSE message.

The embodiment of the present invention further provides an MCE, and a schematic structural diagram of the MCE, as shown in FIG. 8, includes: a confirmation module 11 and a forming module 12;

The confirmation module 11 is configured to confirm whether a PMCH carrying the MCCH exists;

The forming module 12 is configured to: when it is confirmed that the PMCH carrying the MCCH does not exist, form an MBMS pseudo session; and the MBMS pseudo session is used by the eNB to perform data transmission.

In an embodiment, the acknowledgment module 11 is configured to check that the PMCH carrying the MCCH does not exist after the MBMS SESSION STOP REQUEST message is received or the MCCH is updated.

In an embodiment, the forming module 12 is configured to construct an MBMS pseudo session and set the MBMS pseudo session after deleting the context of the MBMS session or MCCH update according to the received MBMS session SESSION STOP REQUEST message. TMGI; or, when receiving MBMS to session stop request message or MCCH update, keep an MBMS will The words are not suspended and the TMGI of the reserved MBMS session is set.

In an embodiment, the MCE further includes: a first sending module 13 and a first receiving module 14; wherein the first sending module 13 is configured to send an MBMS SCHEDULING INFORMATION message of the TMGI including the MBMS pseudo session. The first receiving module 14 is configured to receive an MBMS SCHEDULING INFORMATION RESPONSE message; or

The first sending module 13 is configured to send an MBMS SESSION START REQUEST message of the TMGI containing the MBMS pseudo session; the first receiving module 14 is configured to receive an MBMS SESSION START RESPONSE message.

In an embodiment, the MCE further includes: a second receiving module 16 and a first processing module 17; wherein

The second receiving module 16 is configured to receive an MBMS SESSION START REQUEST message;

The first processing module 17 is configured to perform context update processing on the reserved MBMS session when the MBMS session in the MBMS SESSION START request message is on the same PMCH as the MBMS session; the MBMS SESSION START REQUEST message When the MBMS session is carried on a different PMCH than the MCCH, and the TMGI of the MBMS session in the MBMS Session Start Request message is the same as the TMGI of the reserved MBMS session, the TMGI of the idle MBMS session is replaced with the TMGI of the MBMS session. The TMGI of the reserved MBMS session performs context update processing on the reserved MBMS session and the MBMS session in the MBMS Session Start Request message.

In an embodiment, the MBMS SESSION START REQUEST message is sent by the MME;

In an embodiment, the MCE further includes: the second sending module 15 and the third receiving module 18;

The second sending module 15 is configured to send the MBMS SESSION START REQUEST message;

The third receiving module 18 is configured to receive an MBMS SESSION START RESPONSE message.

In an embodiment, the first processing module 17 performs a context update process on the reserved MBMS session, including: sending an MBMS SESSION STOP REQUEST message to the eNB, where the MBMS SESSION STOP REQUEST message carries a context of the reserved session; Receiving an MBMS SESSION STOP RESPONSE message sent by the eNB; sending an MBMS SESSION START REQUEST message to the eNB, where the MBMS SESSION START REQUEST message carries the context of the new session, and receives the MBMS SESSION START RESPONSE message;

In an embodiment, the first processing module 17 performs a context update process on the MBMS session in the MBMS session and the MBMS session start request message, including: sending an MBMS SESSION STOP REQUEST message to the eNB, where The MBMS SESSION STOP REQUEST message carries the context of the reserved MBMS session; receives the MBMS SESSION STOP RESPONSE message sent by the eNB; sends an MBMS SESSION START REQUEST message to the eNB, where the MBMS SESSION START REQUEST message carries the context of the idle MBMS session. And receiving an MBMS SESSION START RESPONSE message sent by the eNB; sending an MBMS SESSION START REQUEST message to the eNB, where the MBMS SESSION START REQUEST message carries the context of the new session, and receives the MBMS SESSION START RESPONSE message.

The embodiment of the present invention further provides an eNB, and a schematic structural diagram of the eNB, as shown in FIG. 9, includes: a fourth receiving module 21, an establishing module 22, and a second processing module 23, and a third sending module 24; wherein

The fourth receiving module 21 is configured to receive a message including a TMGI of the MBMS pseudo session;

The establishing module 22 is configured to establish a context of the MBMS pseudo session according to the MTCH corresponding to the MBMS pseudo session in the received message;

The second processing module 23 is configured to configure and send an MBSFN area configuration message when scheduling the MBMS pseudo session.

The third sending module 24 is configured to send an MBSFN Area Configuration message.

In an embodiment, the third sending module 24 is further configured to send a response message of a message including a TMGI of the MBMS pseudo session.

In an embodiment, the second processing module 23 is configured to configure an MTCH indication value corresponding to the MBMS pseudo session in the MSI, indicating that the MTCH is not scheduled.

In an embodiment, the eNB further includes: a fourth sending module 25 and a fifth receiving module 26; wherein

The fifth receiving module 26 is configured to receive an MBMS SESSION START REQUEST message;

The fourth sending module 25 is configured to send an MBMS SESSION START RESPONSE message.

The confirmation module 11, the formation module 12, the first transmission module 13, the first receiving module 14, the second sending module 15, the second receiving module 16, the first processing module 17, and the first in the MCE proposed in the embodiment of the present invention The third receiving module 18, the fourth receiving module 21, the establishing module 22, the second processing module 23, the third sending module 24, the fourth sending module 25, and the fifth receiving module 26 in the eNB can all be implemented by a processor, of course It can also be implemented by a specific logic circuit; wherein the processor can be a mobile terminal or a processor on a server. In practical applications, the processor can be a central processing unit (CPU), a microprocessor (MPU), and a digital signal. Processor (DSP) or field programmable gate array (FPGA).

In the embodiment of the present invention, if the above data transmission method is implemented in the form of a software function module, and is sold or used as an independent product, it may also be stored in a computer readable storage medium. Quality. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions. A computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention. The foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.

Correspondingly, the embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores a computer program, and the computer program is used to execute the data sending method of the embodiment of the present invention.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims (22)

A data transmitting method, the method comprising: When the multi-cell/multicast coordination entity MCE confirms that the physical multicast channel PMCH carrying the multi-point control channel MCCH does not exist, it forms a multimedia broadcast and multicast service MBMS pseudo-session; the MBMS pseudo-session is used by the base station eNB for data transmission. The data transmitting method according to claim 1, wherein the confirming that the PMCH carrying the MCCH does not exist comprises: When the MCE receives the MBMS Session Stop Request message or the MCCH update, the MCE checks that the PMCH carrying the MCCH does not have the multicast transport channel MTCH, and confirms that the PMCH carrying the MCCH does not exist. The data transmitting method according to claim 1, wherein said forming an MBMS pseudo session comprises: After the MCE deletes the context of the MBMS session or the MCCH update according to the received MBMS session stop request message, the MCE constructs an MBMS pseudo session and sets the temporary mobile group identifier TMGI of the MBMS pseudo session; or When the MCE receives the MBMS Session Stop Request message or the MCCH update, the MCE keeps an MBMS session from being suspended and sets the TMGI of the reserved MBMS session. The data transmitting method according to claim 1, wherein when the forming an MBMS pseudo session to construct an MBMS pseudo session for the MCE, the method further includes: The MCE sends an MBMS scheduling information indication message including the TMGI of the MBMS pseudo session, Receiving an MBMS scheduling information indication response message; or, The MCE sends an MBMS Session Start Request message containing the TMGI of the MBMS pseudo session, Receive an MBMS Session Start Request Response message. The data transmitting method according to claim 3, wherein the method further comprises: the MCE receiving the MBMS session start request message, wherein the forming an MBMS pseudo session to reserve an MBMS session for the MCE is not suspended; wherein, the method further comprises: the MCE receiving the MBMS session start request message; When the MBMS session in the MBMS session start request message is carried on the same PMCH as the MCCH, the MCE performs context update processing on the reserved MBMS session; When the MBMS session in the MBMS Session Start Request message and the MCCH are carried on different PMCHs, and the TMGI of the MBMS in the MBMS Session Start Request message is the same as the TMGI of the reserved MBMS session, the MCE uses an idle MBMS. The TMGI of the session replaces the TMGI of the reserved MBMS session, and performs context update processing on the reserved MBMS session and the MBMS session in the MBMS Session Start Request message. The data transmitting method according to claim 4, wherein before the sending the MBMS scheduling information indication message, the method further comprises: The MCE sends an MBMS Session Start Request message, and receives an MBMS Session Start Request Response message; the MBMS Session Start Request message includes the TMGI of the MBMS pseudo session. A data transmitting method, the method comprising: The eNB receives the message of the TMGI including the MBMS pseudo session, and establishes the context of the MBMS pseudo session according to the MTCH corresponding to the MBMS pseudo session in the received message; When the MBMS pseudo session is scheduled, the medium access control scheduling indication MSI message is configured and sent; Send the multicast/multicast single-frequency network MBSFN area configuration message. The data transmitting method according to claim 7, wherein before the eNB configures the MSI message, the method further includes: The eNB sends a response message containing a message of the TMGI of the MBMS pseudo session. The data transmitting method according to claim 7, wherein said configuring an MSI message, a packet The MTCH indication value corresponding to the MBMS pseudo session is configured to indicate that the MTCH is not scheduled. The data transmitting method according to claim 7, wherein before the eNB receives the MBMS scheduling information indication message, the method further includes: The eNB receives the MBMS Session Start Request message and sends an MBMS Session Start Request Response message. A multi-cell/multicast coordination entity, the multi-cell/multicast coordination entity comprising: an acknowledgment module and a forming module; The confirmation module is configured to confirm whether a PMCH carrying the MCCH exists; The forming module is configured to form an MBMS pseudo session when the acknowledgment module confirms that the PMCH carrying the MCCH does not exist; and the MBMS pseudo session is used by the eNB to perform data transmission. The multi-cell/multicast coordination entity according to claim 11, wherein the confirmation module is configured to: when receiving the MBMS session stop request message or the MCCH update, check that the PMCH carrying the MCCH does not have an MTCH, and confirm that the PMCH carrying the MCCH is not presence. The multi-cell/multicast coordination entity according to claim 11, wherein said forming module is configured to construct an MBMS pseudo session after deleting a context of said MBMS session according to a received MBMS Session Stop Request message or MCCH update And setting the TMGI of the MBMS pseudo session; or, When receiving the MBMS to Session Stop Request message or MCCH update, one MBMS session is reserved and is not suspended, and the TMGI of the reserved MBMS session is set. The multi-cell/multicast coordination entity according to claim 11, wherein the multi-cell/multicast coordination entity further comprises: a first sending module and a first receiving module; The first sending module is configured to send an MBMS scheduling information indication message of the TMGI that includes the MBMS pseudo session; the first receiving module is configured to receive an MBMS scheduling information indication response message; or The first sending module is configured to send an MBMS session start request message of the TMGI including the MBMS pseudo session; the first receiving module is configured to receive an MBMS session start request response message. The multi-cell/multicast coordination entity according to claim 13, wherein the multi-cell/multicast coordination entity further comprises: a second receiving module and a first processing module; The second receiving module is configured to receive an MBMS session start request message; The first processing module is configured to perform a context update process on the reserved MBMS session when the MBMS session in the MBMS session start request message and the MCCH are carried on the same PMCH; the MBMS session start request message When the MBMS session is carried on a different PMCH than the MCCH, and the TMGI of the MBMS session in the MBMS Session Start Request message is the same as the TMGI of the reserved MBMS session, the reservation is replaced with the TMGI of an idle MBMS session. The TMGI of the MBMS session performs context update processing on the reserved MBMS session and the MBMS session in the MBMS Session Start Request message. The multi-cell/multicast coordination entity according to claim 14, wherein the multi-cell/multicast coordination entity further comprises: a second sending module and a third receiving module; The second sending module is configured to send an MBMS session start request message; The third receiving module is configured to receive an MBMS session start request response message. A base station, the base station includes: a fourth receiving module, an establishing module, a second processing module, and a third sending module; The fourth receiving module is configured to receive a message including a TMGI of the MBMS pseudo session; The establishing module is configured to establish a context of the MBMS pseudo session according to the MTCH corresponding to the MBMS pseudo session in the received message; The second processing module is configured to configure and send an MSI message when scheduling the MBMS pseudo session; The third sending module is configured to send an MBSFN area configuration message. The base station according to claim 17, wherein said third transmitting module is further configured to transmit a response message of a message including a TMGI of the MBMS pseudo session. The base station according to claim 17, wherein the second processing module is configured to configure an MTCH indication value corresponding to the MBMS pseudo session, indicating that the MTCH is not scheduled. The base station according to claim 17, wherein the base station further comprises: a fourth sending module and a fifth receiving module; wherein The fifth receiving module is configured to receive an MBMS session start request message; The fourth sending module is configured to send an MBMS session start request response message. A computer storage medium having stored therein computer executable instructions for performing the data transmission method of any one of claims 1 to 6. A computer storage medium storing computer executable instructions for performing the data transmission method according to any one of claims 7 to 10.

Images