WO2015131638A1 - 一种数据发送方法、设备和存储介质 - Google Patents

一种数据发送方法、设备和存储介质 Download PDF

Info

Publication number
WO2015131638A1
WO2015131638A1 PCT/CN2014/095194 CN2014095194W WO2015131638A1 WO 2015131638 A1 WO2015131638 A1 WO 2015131638A1 CN 2014095194 W CN2014095194 W CN 2014095194W WO 2015131638 A1 WO2015131638 A1 WO 2015131638A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
mcch
system information
enb
configuration
Prior art date
Application number
PCT/CN2014/095194
Other languages
English (en)
French (fr)
Inventor
桑健
马子江
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to JP2017516884A priority Critical patent/JP6346710B2/ja
Priority to US15/514,015 priority patent/US10869168B2/en
Priority to EP14885021.7A priority patent/EP3203763B1/en
Publication of WO2015131638A1 publication Critical patent/WO2015131638A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource

Definitions

  • the present invention relates to signal processing technologies in mobile communications, and in particular, to a data transmitting method, device, and storage medium.
  • multimedia information services have the characteristics of high bandwidth occupation, long duration, sensitive time delay, and relatively fixed transmission content.
  • 3GPP 3rd Generation Partnership Project
  • MBMS Multimedia Broadcast Multicast Service
  • the MBMS service is called an evolved-Multimedia Broadcast Multicast Service (eMBMS).
  • eMBMS evolved-Multimedia Broadcast Multicast Service
  • the Multicast Control Channel (MCCH) and the Multicast Transmission Channel (MTCH) on the evolved NodeB (eNB) side are multiplexed at multiple points.
  • MCH Multicast Channel
  • PMCH Physical Multicast Channel
  • the MCCH and the MTCH are multiplexed on the PMCH.
  • the embodiment of the present invention is to provide a data transmission method, a device, and a storage medium.
  • the PMCH carrying the MCCH on the eNB side does not exist, the data of the MCCH can be normally transmitted.
  • the embodiment of the present invention provides a data sending method, including: when an eNB confirms that a PMCH carrying an MCCH does not exist, it sends a System Information Block message; and configures a multicast/multicast single frequency network according to the System Information Block message.
  • MBSFN Multimedia Broadcast multicast service Single Frequency Network
  • the acknowledgment that the PMCH carrying the MCCH does not exist including: the eNB receives the SETUP RESPONSE message, and does not receive the PMSCH scheduling information indication (SCHEDULING INFORMATION) message, confirming that the PMCH carrying the MCCH does not exist. Or, the eNB receives the MBMS SCHEDULING INFORMATION message, and confirms that the PMCH carrying the MCCH does not exist according to the MBMS SCHEDULING INFORMATION message.
  • the eNB receives the SETUP RESPONSE message, and does not receive the PMSCH scheduling information indication (SCHEDULING INFORMATION) message, confirming that the PMCH carrying the MCCH does not exist.
  • the eNB receives the MBMS SCHEDULING INFORMATION message, and confirms that the PMCH carrying the MCCH does not exist according to the MBMS SCHEDULING INFORMATION message.
  • the method before the sending the System Information Block message, further includes: receiving, by the eNB, a Multi-cell/Multicast Coordination Entity (MCE) configuration update (CONFIGURATION UPDATE) message;
  • MCE Multi-cell/Multicast Coordination Entity
  • the sending the System Information Block message includes: sending a System Information Block message through an air interface; wherein the content of the System Information Block message is according to the M2SET UP RESPONSE message, the eNB configuration update response (CONFIGURATION UPDATE)
  • the ACKNOWLEDGE message is configured with a newer message time in the MCE CONFIGURATION UPDATE message.
  • An embodiment of the present invention further provides a data sending method, including: receiving, by a UE, a System Information Block message and an MBSFN Area Configuration message;
  • the content of the MBSFN Area Configuration message is configured by the UE according to the System Information Block message, where the MBSFN Area Configuration message indicates that the number of PMCHs is N+1, where one PMCH carries the MCCH, and the PMCH that carries the MCCH includes The number of MBMS sessions is 0.
  • the embodiment of the present invention further provides a data sending method, including: sending, by the MCE, a message indicating that the PMCH carrying the MCCH does not exist; and receiving the response message of the message.
  • the message indicating that the PMCH carrying the MCCH does not exist is: an MBMS SCHEDULING INFORMATION message; correspondingly, the response message of the message is: an MBMS SCHEDULING INFORMATION RESPONSE message.
  • the method before the MCE sends a message indicating that the PMCH carrying the MCCH does not exist, the method further includes: the MCE receives the M2SET UP REQUEST message, and sends the M2SET UP RESPONSE message; the MCE receives the eNB configuration update message, and sends the eNB configuration update response.
  • the message or MCE sends an MCE CONFIGURATION UPDATE message to receive the MCE CONFIGURATION UPDATE ACKNOWLEDGE message.
  • the embodiment of the present invention further provides an eNB, where the eNB includes: an acknowledgment module, a first sending module, a configuration module, a processing module, and a second sending module;
  • the confirmation module is configured to confirm whether a PMCH carrying the MCCH exists
  • the first sending module is configured to send a System Information Block message when the acknowledgment module confirms that the PMCH carrying the MCCH does not exist;
  • the configuration module is configured to configure an MBSFN Area Configuration message according to the System Information Block message;
  • the processing module is configured to perform data scheduling according to the configuration according to the System Information Block message or the configuration of an MBSFN Area Configuration message;
  • the second sending module is configured to send the MBSFN Area Configuration message.
  • the eNB further includes a first receiving module, where the confirming module confirms that the PMCH carrying the MCCH does not exist, the first receiving module is configured to receive the M2SET UP RESPONSE message; or, the first The receiving module is further configured to receive an MBMS SCHEDULING INFORMATION message, where the MBMS SCHEDULING INFORMATION message indicates that the PMCH carrying the MCCH does not exist.
  • the first receiving module is further configured to receive an MCECONFIGURATION UPDATE message; correspondingly, the first sending module is configured to send a System Information Block message by using an air interface;
  • the content of the System Information Block is configured according to the M2SETUP RESPONSE message, the eNB CONFIGURATION UPDATE ACKNOWLEDGE message, and the newer message time in the MCE CONFIGURATION UPDATE.
  • the embodiment of the present invention further provides a UE, where the UE includes: a second receiving module and a third receiving module;
  • the second receiving module is configured to receive a System Information Block message
  • the third receiving module is configured to receive an MBSFN Area Configuration message
  • the content of the MBSFN Area Configuration message is configured by the UE according to the System Information Block message, where the MBSFN Area Configuration message indicates that the number of PMCHs is N+1, where one PMCH carries the MCCH, and the MBCH that carries the MCCH carries the MBMS session. The number is 0.
  • the embodiment of the present invention further provides an MCE, where the MCE includes: a third sending module and a fourth receiving module, where
  • the third sending module is configured to send a message indicating that the PMCH carrying the MCCH does not exist interest
  • the fourth receiving module is configured to receive a response message of the message.
  • the message indicating that the PMCH carrying the MCCH does not exist is: an MBMS SCHEDULING INFORMATION message; correspondingly, the response message of the message is: an MBMS SCHEDULING INFORMATION RESPONSE message.
  • the multi-cell/multicast coordination entity further includes: a fourth sending module and a fifth receiving module;
  • the fourth sending module is configured to send an M2 SET UP RESPONSE message; the fifth receiving module is configured to receive an M2 SET UP REQUEST message; or the fourth sending module is configured to send an eNB CONFIGURATION UPDATE ACKNOWLEDGE message;
  • the fifth receiving module is configured to receive a CONFIGURATION UPDATE message; or the fourth sending module is configured to send an MCE CONFIGURATION UPDATE message; the fifth receiving module is configured to receive an MCE CONFIGURATION UPDATE ACKNOWLEDGE 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 MCE sends a message indicating that the PMCH carrying the MCCH does not exist to the eNB; when the eNB confirms that the PMCH carrying the MCCH does not exist, the eNB sends a response message of the message to the MCE. And sending a System Information Block message to the UE; the UE receives the System Information Block message; the eNB configures the MBSFN Area Configuration message according to the System Information Block message, performs data scheduling according to the configuration of the System Information Block message or the MBSFN Area Configuration message, and performs the The MBSFN Area Configuration message is sent to the UE.
  • the eNB when the eNB confirms that the PMCH carrying the MCCH does not exist, the eNB adopts the MCCH default.
  • a sending mechanism that is, sending a System Information Block message and an MBSFN Area Configuration message to the UE, where the MBSFN Area Configuration message indicates that the number of PMCHs is N+1, where the first to the Nth PMCHs do not carry the MCCH, the Nth The number of MBMS sessions included in the +1 PMCH is 0, so that when the PMCH carrying the MCCH does not exist, the data of the MCCH can be normally transmitted.
  • FIG. 1 is a schematic diagram of deployment of a service area, a synchronization area, and an MBSFN area of an LTE eMBMS service;
  • FIG. 2 is a logical architecture diagram of an LTE eMBMS service
  • FIG. 3 is a schematic diagram of a basic processing flow of an eNB side data sending method according to an embodiment of the present invention
  • 4 is a schematic structural diagram of scheduling indication information of an LTE eMBMS service
  • FIG. 5 is a schematic diagram of a basic processing flow of a method for transmitting data on a UE side according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of a basic processing process of a data transmission method on an MCE side according to an embodiment of the present invention
  • FIG. 7 is a schematic flowchart of detailed processing of a data sending method according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of detailed processing of a data sending method according to Embodiment 2 of the present invention.
  • FIG. 9 is a schematic flowchart of detailed processing of a data sending method according to Embodiment 3 of the present invention.
  • FIG. 10 is a schematic flowchart of detailed processing of a data sending method according to Embodiment 4 of the present invention.
  • FIG. 11 is a schematic structural diagram of a structure of an eNB according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of a structure of a UE according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of a structure of an MCE according to an embodiment of the present invention.
  • the MCE sends a message indicating that the PMCH carrying the MCCH does not exist to the eNB; when the eNB confirms that the PMCH carrying the MCCH does not exist, the eNB sends a response message of the message to the MCE, and sends a System Information Block message to the UE; Receive System Information Block message; eNB configures MBSFN according to System Information Block message
  • the area configuration message is configured to perform data scheduling according to the configuration of the System Information Block message or the MBSFN Area Configuration message, and send the MBSFN Area Configuration message to the UE.
  • 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.
  • 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.
  • 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.
  • 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 (Mobility, MME) and the MCE
  • the M2 interface is an interface 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;
  • the Information Block Type 13 message indicates the MCCH-related configuration of the cell and the allocation information of the MBSFN subframe in which the MCCH is located.
  • the MBSFN Area Configuration message indicates the specific content of the MCCH, including: allocation information of the common subframe of the MBSFN area in the cell, configuration information of the PMCH, Information of each MTCH, etc.
  • 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 includes: 1. The establishment of the M2 port is completed in the eNB and the MCE. Before the eNB receives the MBMS SCHEDULING INFORMATION sent by the MCE; 2. When 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; the MCCH data cannot be sent because the PMCH carrying the MCCH on the eNB side does not exist.
  • the MBMS SCHEDULING INFORMATION message sent through the M2 interface does not support the case where the number of MBMS sessions on the PMCH is 0; it is assumed that the MCCH bearer is transmitted on a certain PMCH, but the PMCH If there is no MBMS session, the MCE needs to carry the PMCH in the MBMS SCHEDULING INFORMATION message, and the number of MTCHs in the PMCH is 0; but it is included in the MBMS SCHEDULING INFORMATION in the 3GPP TS36443-b30 protocol.
  • the specified number of sessions has a minimum of one. 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 eNB side data sending method in the embodiment of the present invention, as shown in FIG. 3, includes the following steps:
  • Step 101 The eNB sends a System Information Block message when it confirms that the PMCH carrying the MCCH does not exist.
  • the PMCH carrying the MCCH does not exist, and the number of the PMCHs is N, but the N PMCHs do not carry the MCCH, and N is an integer greater than or equal to zero;
  • the eNB confirms that the PMCH carrying the MCCH does not exist: the eNB receives the M2SETUP RESPONSE message sent by the MCE, and does not confirm that the PMCH carrying the MCCH does not exist when the MBMS scheduling information indication message is not received; or the eNB receives the MBMS SCHEDULING INFORMATION message sent by the MCE.
  • the MBMS SCHEDULING INFORMATION message indicates that the PMCH carrying the MCCH does not exist.
  • the eNB sends a System Information Block message to the UE through the air interface, and receives the M2SETUP RESPONSE message sent by the MCE, and does not receive the MBMS scheduling information indication message. Confirming that the PMCH carrying the MCCH does not exist, and the content of the System Information Block message is configured according to the M2SETUP RESPONSE message;
  • the content of the System Information Block message is configured according to the MCE CONFIGURATION UPDATE message;
  • the UE reads the MCCH in the modification period of each MCCH.
  • the MCCH modification period in the System Information Block message is set to the maximum allowed by the protocol on the eNB side;
  • the eNB sends an MCE CONFIGURATION UPDATE message, where the eNB updates the MCCH modification period to a maximum allowed by the protocol;
  • the System Information Block message may be a System Information Block Type 13 message; the following embodiments of the present invention take the System Information Block message as a System Information Block Type 13 message as an example.
  • Step 102 Configure an MBSFN Area Configuration message according to the System Information Block message.
  • the setting of the common subframe configuration information of the MBSFN area in the MBSFN Area Configuration message is, for example, commonSF-Alloc, commonSF-AllocPeriod is the same as the System Information Block;
  • the number of PMCHs in the MBSFN Area Configuration message is N+1, the added The configuration of the PMCH is the same as the System Information Block message, and the added PMCH includes the number of MBMS sessions being 0;
  • the scheduling period of the PMCH carrying the MCCH in the MBSFN Area Configuration message cannot be greater than the MCCH repetition period indicated in the System Information Block message; therefore, in order to ensure that the messages sent by the eNBs served by the same MCE are consistent, the PMCH is The scheduling period is set to the minimum allowed by the protocol, or the scheduling period of the PMCH is set to the MCCH repetition period indicated in the System Information Block message. The same value; in this way, the scheduling resources on the eNB side can be saved to the utmost extent.
  • Step 103 The eNB performs data scheduling according to the configuration of the System Information Block message or the MBSFN Area Configuration message.
  • Step 104 The eNB sends the MBSFN Area Configuration message.
  • the eNB sends the MBSFN Area Configuration message to the UE through an air interface, where the scheduling indication information is a structural diagram, as shown in FIG. 4 .
  • the detailed processing flow of the UE side data sending method in the embodiment of the present invention, as shown in FIG. 5, includes the following steps:
  • Step 201 The UE receives a System Information Block message.
  • the UE receives a System Information Block message sent by the eNB through the air interface;
  • the content of the System Information Block message is configured according to the newer one of the M2SETUP RESPONSE message, the eNB CONFIGURATION UPDATE ACKNOWLEDGE message, and the MCE CONFIGURATION UPDATE message; the MCCH modification period in the System Information Block message The maximum allowed for the 3GPP TS36331 protocol;
  • the System Information Block message may be a System Information Block Type 13 message.
  • Step 202 The UE receives an MBSFN Area Configuration message.
  • the UE receives an MBSFN Area Configuration message sent by the eNB through the air interface;
  • the common sub-frame configuration information of the MBSFN area in the MBSFN Area Configuration message is set to be the same as the common information, such as commonSF-Alloc, commonSF-AllocPeriod, and the system information block Type13;
  • a PMCH carries the MCCH.
  • the configuration of the PMCH carrying the MCCH is the same as that of the System Information Block.
  • the PMCH carrying the MCCH includes the number of MBMS sessions being 0.
  • the scheduling period of the PMCH in the MBSFN Area Configuration message is 3GPP.
  • the minimum value allowed by the TS36331 protocol, or the scheduling period of the PMCH is the same as the MCCH repetition period indicated in the System Information Block message.
  • the detailed processing flow of the MCE side data sending method in the embodiment of the present invention, as shown in FIG. 6, includes the following steps:
  • Step 301 The MCE sends a message indicating that the PMCH carrying the MCCH does not exist.
  • the message indicating that the PMCH carrying the MCCH does not exist is: an MBMS SCHEDULING INFORMATION message;
  • the absence of the PMCH carrying the MCCH means that the number of PMCHs is N, but none of the N PMCHs carry the MCCH, and N is an integer greater than or equal to zero.
  • Step 302 The MCE receives a response message of the message.
  • the response message of the message is: MBMS SCHEDULING INFORMATION RESPONSE message.
  • the method further includes:
  • Step 300 The MCE sends an M2SET UP REQUEST message to receive the M2SET UP RESPONSE message. Alternatively, the MCE sends an MCE CONFIGURATION UPDATE message to receive the MCE CONFIGURATION UPDATE ACKNOWLEDG message.
  • a schematic diagram of a detailed processing flow of a data sending method according to Embodiment 1 of the present invention, as shown in FIG. 7, includes the following steps:
  • step 401 the eNB sends an M2SET UP REQUEST message to the MCE.
  • Step 402 The MCE returns an M2SET UP RESPONSE message to the eNB.
  • the eNB does not receive the MBMS scheduling information indication message, and confirms that the PMCH carrying the MCCH does not exist;
  • the PMCH carrying the MCCH does not exist, and the number of PMCHs is N, but none of the N PMCHs carry the MCCH, and N is an integer greater than or equal to zero.
  • Step 403 The eNB sends a System Information Block Type 13 message to the UE.
  • the eNB sends a System Information Block Type 13 message to the UE through the air interface;
  • the content of the System Information Block Type 13 message is configured according to the M2SET UP RESPONSE message
  • the UE reads the MCCH in the modification period of each MCCH.
  • the MCCH modification period in the System Information Block Type 13 message is set to the maximum allowed by the protocol on the eNB side; Sending an MCE CONFIGURATION UPDATE message to the eNB for the eNB to update the MCCH modification period to the maximum allowed by the protocol.
  • Step 404 The eNB configures an MBSFN Area Configuration message according to the System Information Block message.
  • the setting of the common subframe configuration information of the MBSFN area in the MBSFN Area Configuration message such as commonSF-Alloc, commonSF-AllocPeriod and System Information Block Type13
  • the number of PMCHs in the MBSFN Area Configuration message is N+1, increasing The configuration of the PMCH is the same as the System Information Block Type 13, and the added PMCH includes the number of MBMS sessions being 0;
  • the scheduling period of the PMCH carrying the MCCH in the MBSFN Area Configuration message cannot be greater than the MCCH repetition period indicated in the System Information Block Type 13 message; therefore, in order to ensure that the messages sent by the eNBs served by the same MCE are consistent,
  • the PMCH scheduling period is set to the minimum allowed by the protocol, or the scheduling period of the PMCH is set to the same value as the MCCH repetition period indicated in the System Information Block Type 13 message; thus, the scheduling resources on the eNB side can be saved to the utmost extent.
  • Step 405 The eNB performs data scheduling according to the configuration of the System Information Block Type 13 message or the MBSFN Area Configuration message, and sends the MBSFN. Area Configuration message;
  • the eNB sends the MBSFN Area Configuration message to the UE by using an air interface.
  • a schematic diagram of a detailed processing flow of a data sending method according to Embodiment 2 of the present invention, as shown in FIG. 8, includes the following steps:
  • step 501 the eNB sends an M2SET UP REQUEST message to the MCE.
  • Step 502 The MCE sends an M2SET UP RESPONSE message to the eNB.
  • Step 503 The MCE sends an MBMS SCHEDULING INFORMATION message to the eNB.
  • the MBMS SCHEDULING INFORMATION message indicates that the PMCH carrying the MCCH does not exist
  • the absence of the PMCH carrying the MCCH means that the number of PMCHs is zero.
  • Step 504 The eNB sends an MBMS SCHEDULING INFORMATION RESPONSE message to the MCE.
  • the eNB confirms that the PMCH carrying the MCCH does not exist.
  • Step 505 The eNB sends a System Information Block Type 13 message to the UE.
  • the eNB sends a System Information Block Type 13 message to the UE through the air interface;
  • the content of the System Information Block Type 13 message is configured according to the M2SET UP RESPONSE message
  • the UE reads the MCCH in the modification period of each MCCH.
  • the MCCH modification period in the System Information Block Type 13 message is set to the maximum allowed by the protocol on the eNB side; Sending an MCE CONFIGURATION UPDATE message to the eNB for the eNB to update the MCCH modification period to the maximum allowed by the protocol.
  • Step 506 The eNB configures an MBSFN Area Configuration message according to the System Information Block message.
  • the setting of the common subframe configuration information of the MBSFN area in the MBSFN Area Configuration message is, for example, commonSF-Alloc, commonSF-AllocPeriod is the same as the System Information Block Type13; the number of PMCHs in the MBSFN Area Configuration message is 1, the PMCH The configuration is the same as the System Information Block Type 13.
  • the PMCH contains 0 MBMS sessions.
  • the scheduling period of the PMCH carrying the MCCH in the MBSFN Area Configuration message cannot be greater than the MCCH repetition period indicated in the System Information Block Type 13 message; therefore, in order to ensure that the messages sent by the eNBs served by the same MCE are consistent,
  • the PMCH scheduling period is set to the minimum allowed by the protocol, or the scheduling period of the PMCH is set to the same value as the MCCH repetition period indicated in the System Information Block Type 13 message; thus, the scheduling resources on the eNB side can be saved to the utmost extent.
  • Step 507 The eNB performs data scheduling according to the configuration of the System Information Block Type 13 message or the MBSFN Area Configuration message, and sends the MBSFN Area Configuration message.
  • the eNB sends the MBSFN Area Configuration message to the UE by using an air interface.
  • a schematic diagram of a detailed processing flow of a data sending method according to Embodiment 3 of the present invention, as shown in FIG. 9, includes the following steps:
  • Step 601 The MCE sends an MCE CONFIGURATION UPDATE message to the eNB.
  • step 602 the eNB sends an MCE CONFIGURATION UPDATE ACKNOLNOWLEDGE message to the MCE.
  • Step 603 The MCE sends an MBMS SCHEDULING INFORMATION message to the eNB.
  • the MBMS SCHEDULING INFORMATION message indicates that the number of PMCHs is N, and N is a positive integer, but none of the N PMCHs carry the MCCH.
  • Step 604 the eNB sends an MBMS SCHEDULING INFORMATION RESPONSE message to the MCE.
  • the eNB confirms that the PMCH carrying the MCCH does not exist.
  • Step 605 The eNB sends a System Information Block Type 13 message to the UE.
  • the eNB sends a System Information Block Type 13 message to the UE through the air interface;
  • the content of the System Information Block Type 13 message is configured according to an MCE CONFIGURATION UPDATE message.
  • Step 606 The eNB configures an MBSFN Area Configuration message according to the System Information Block Type 13 message.
  • the number of PMCHs in the MBSFN Area Configuration message is N+1
  • the configuration of the added PMCH is the same as the System Information Block Type 13
  • the added PMCH includes the number of MBMS sessions is 0;
  • the scheduling period of the PMCH carrying the MCCH in the MBSFN Area Configuration message cannot be greater than the MCCH repetition period indicated in the System Information Block Type 13 message; therefore, in order to ensure that the messages sent by the eNBs served by the same MCE are consistent,
  • the PMCH scheduling period is set to the minimum allowed by the protocol, or the scheduling period of the PMCH is set to the same value as the MCCH repetition period indicated in the System Information Block Type 13 message; thus, the scheduling resources on the eNB side can be saved to the utmost extent.
  • Step 607 The eNB performs data scheduling according to the configuration of the System Information Block Type 13 message or the MBSFN Area Configuration message, and sends the MBSFN Area Configuration message.
  • the eNB sends the MBSFN Area Configuration message to the UE by using an air interface.
  • a schematic diagram of a detailed processing flow of a data transmission method according to Embodiment 4 of the present invention, as shown in FIG. 10, includes the following steps:
  • step 701 the eNB sends an eNB CONFIGURATION UPDATE message to the MCE.
  • step 702 the MCE sends an eNB CONFIGURATION UPDATE ACKNOLNOWLEDGE message to the eNB.
  • Step 703 The MCE sends an MBMS SCHEDULING INFORMATION message to the eNB.
  • the MBMS SCHEDULING INFORMATION message indicates that the number of PMCHs is N, and N is a positive integer, but none of the N PMCHs carry the MCCH.
  • Step 704 the eNB sends an MBMS SCHEDULING INFORMATION RESPONSE message to the MCE.
  • the eNB confirms that the PMCH carrying the MCCH does not exist.
  • Step 705 The eNB sends a System Information Block Type 13 message to the UE.
  • the eNB sends a System Information Block Type 13 message to the UE through the air interface;
  • the content of the System Information Block Type 13 message is configured according to an eNB CONFIGURATION UPDATE ACKNOWLEDGE message.
  • Step 706 The eNB configures an MBSFN Area Configuration message according to the System Information Block Type 13 message.
  • the setting of the common subframe configuration information of the MBSFN area in the MBSFN Area Configuration message such as commonSF-Alloc, commonSF-AllocPeriod and System Information Block Type13
  • the number of PMCHs in the MBSFN Area Configuration message is N+1, increasing The configuration of the PMCH is the same as the System Information Block Type 13, and the added PMCH includes the number of MBMS sessions being 0;
  • the scheduling period of the PMCH carrying the MCCH in the MBSFN Area Configuration message cannot be greater than the MCCH repetition period indicated in the System Information Block Type 13 message; therefore, in order to ensure that the messages sent by the eNBs served by the same MCE are consistent,
  • the PMCH scheduling period is set to the minimum allowed by the protocol, or the scheduling period of the PMCH is set to the same value as the MCCH repetition period indicated in the System Information Block Type 13 message; thus, the scheduling resources on the eNB side can be saved to the utmost extent.
  • Step 707 The eNB performs data scheduling according to the configuration of the System Information Block Type 13 message or the MBSFN Area Configuration message, and sends the MBSFN Area Configuration message.
  • the eNB sends the MBSFN Area Configuration message to the UE by using an air interface.
  • the embodiment of the present invention further provides an eNB, and a schematic structural diagram of the eNB, as shown in FIG. 11 , includes: a determining module 11 , a first sending module 12 , a configuration module 13 , and a processing module 14 . And a second sending module 15; wherein
  • the determining module 11 is configured to determine whether a PMCH carrying the MCCH exists
  • the first sending module 12 is configured to send a System Information Block message when the acknowledgment module confirms that the PMCH carrying the MCCH does not exist;
  • the configuration module 13 is configured to configure an MBSFN Area Configuration message according to the System Information Block message.
  • the processing module 14 is configured to perform data scheduling according to the configuration according to the System Information Block message or the MBSFN Area Configuration message;
  • the second sending module 15 is configured to send the MBSFN Area Configuration message.
  • the base station further includes: a first receiving module 16, when the confirming module confirms that the PMCH carrying the MCCH does not exist,
  • the first receiving module 16 is configured to receive an M2SETUP RESPONSE message; or
  • the first receiving module 16 is further configured to receive an MBMS SCHEDULING INFORMATION message, where the MBMS SCHEDULING INFORMATION message indicates that the PMCH carrying the MCCH does not exist.
  • the first receiving module 16 is further configured to receive an MCE configuration update message.
  • the first sending module 12 is configured to send a System Information Block message by using an air interface.
  • the M2SETUP RESPONSE message indicates that the content of the System Information Block message is according to the M2 SETUP when the PMCH carrying the MCCH does not exist. RESPONSE message is configured;
  • the content of the System Information Block message is compared according to the message time in the MBMS SCHEDULING INFORMATION RESPONSE message, the eNB CONFIGURATION UPDATE ACKNOWLEDGE message, and the MCE CONFIGURATION UPDATE message.
  • the new one is configured.
  • the UE reads the MCCH in the modification period of each MCCH.
  • the MCCH modification period in the System Information Block message is set to the protocol permission on the eNB side.
  • the MCE sends an MCE CONFIGURATION UPDATE message to the eNB for the eNB to update the MCCH modification period to the maximum allowed by the protocol.
  • the scheduling period of the PMCH carrying the MCCH in the MBSFN Area Configuration message cannot be greater than the MCCH repetition period indicated in the System Information Block message; therefore, in order to ensure that the messages sent by the eNBs served by the same MCE are consistent, the PMCH is The scheduling period is set to the minimum value allowed by the protocol, or the scheduling period of the PMCH is set to the same value as the MCCH repetition period indicated in the System Information Block message; thus, the scheduling resources on the eNB side can be saved to the utmost extent.
  • the embodiment of the present invention further provides a UE, a schematic structural diagram of the UE, as shown in FIG. 12, including: a second receiving module 21 and a third receiving module 22;
  • the second receiving module 21 is configured to receive a System Information Block message.
  • the third receiving module 22 is configured to receive an MBSFN Area Configuration message
  • the content of the MBSFN Area Configuration message is configured by the UE according to the system information broadcast message, indicating that the number of PMCHs is N+1, where one PMCH carries the MCCH, and the PMCH carrying the MCCH includes the number of MBMS sessions.
  • the UE receives a System Information Block message and an MBSFN Area Configuration message sent by the eNB through the air interface;
  • the content of the System Information Block message is configured according to the M2SETUP RESPONSE message, the eNB CONFIGURATION UPDATE ACKNOWLEDGE message, and the message time in the MEC CONFIGURATION UPDATE message; the MCCH of the System Information Block message
  • the modification period is the maximum allowed by the 3GPP TS36331 protocol;
  • the setting of the common subframe configuration information of the MBSFN area in the MBSFN Area Configuration message for example, commonSF-Alloc, commonSF-AllocPeriod is the same as the System Information Block message; the number of PMCHs in the MBSFN Area Configuration message is N+1, the added PMCH The configuration is the same as the System Information Block message, the increased PMCH includes the number of MBMS sessions is 0; the scheduling period of the PMCH in the MBSFN Area Configuration message is the minimum allowed by the 3GPP TS36331 protocol, or the scheduling period of the PMCH and the System Information Block
  • the MCCH repetition period indicated in the Type13 message has the same value.
  • the embodiment of the present invention further provides an MCE, and a schematic structural diagram of the MCE, as shown in FIG. 13, includes: a third sending module 31 and a fourth receiving module. 32.
  • the third sending module 31 is configured to send a message indicating that the PMCH carrying the MCCH does not exist;
  • the fourth receiving module 32 is configured to receive a response message of the message
  • the fourth sending module 33 is configured to send an M2SET UP RESPONSE message
  • the fifth receiving module 34 is configured to receive an M2SET UP REQUEST message
  • the fourth sending module 33 is configured to send an eNB CONFIGURATION UPDATE ACKNOWLEDGE message
  • the fifth receiving module 34 is configured to receive an eNB CONFIGURATION UPDATE message
  • the fourth sending module 33 is configured to send an MCE CONFIGURATION UPDATE message
  • the fifth receiving module 34 is configured to receive an MCE CONFIGURATION UPDATE ACKNOWLEDGE message.
  • the response message of the message is: MBMS SCHEDULING INFORMATION RESPONSE message.
  • the third receiving module 22, the third sending module 31, the fourth receiving module 32, the fourth sending module 33, and the fifth receiving module 34 in the MCE can all be implemented by a processor, and of course, can also be implemented by a specific logic circuit;
  • the processor may be a processor on a mobile terminal or a server. In practical applications, the processor may be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP), or a field programmable gate. Array (FPGA), etc.
  • 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.
  • program codes such as a USB flash drive, a mobile hard disk, a read only memory (ROM), a magnetic disk, or an optical disk.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种数据发送的方法，所述方法包括：基站确认承载多点控制信道的物理多播信道不存在时，发送系统信息广播消息；根据所述系统信息广播消息配置多播/组播单频网络(MBSFN)区域配置消息；根据所述系统信息广播消息或所述MBSFN区域配置消息的配置进行数据调度；发送所述MBSFN区域配置消息。本发明还同时公开了另两种数据发送的方法、基站、用户设备、多小区/多播协调实体及存储介质。

Description

一种数据发送方法、设备和存储介质 技术领域
本发明涉及移动通信中的信号处理技术，尤其涉及一种数据发送方法、设备和存储介质。
背景技术
随着移动互联网和大屏移动终端的发展，越来越多的移动终端用户选择在移动终端侧进行多媒体信息业务的处理，如：视频会议、赛事直播、网上教育等。多媒体信息业务与普通的数据业务相比具有带宽占用高、持续时间长、时延要求灵敏、传输内容相对固定等特点。为了有效地利用频谱资源，第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)组织提出了多媒体广播和组播业务(Multimedia Broadcast Multicast Service，MBMS)，MBMS业务是一种点对多的业务，即：数据源为一个、数据接收目标为多个；MBMS业务可实现网络资源共享，提高无线接入网频域资源的利用率。
在长期演进(Long Term Evolution，LTE)系统中，MBMS业务被称为演进的多媒体广播和组播业务(evoluted-Multimedia Broadcast Multicast Service，eMBMS)。
在eMBMS业务中，根据3GPP TS36300协议规范，演进基站(evolved NodeB，eNB)侧的多点控制信道(Multicast Control Channel，MCCH)和多点传输信道(Multicast Transmission Channel，MTCH)是复用在多点信道(Multicast Channel，MCH)上的，而MCH映射在物理多点信道(Physical Multicast Channel，PMCH)上的，因此MCCH和MTCH复用在PMCH上；当eNB侧承载MCCH的PMCH不存在时，会导致eNB侧停止PMCH的数 据发送，进而导致MCCH的数据无法发送。
发明内容
有鉴于此，本发明实施例期望提供一种数据发送方法、设备和存储介质，在eNB侧承载MCCH的PMCH不存在时，能够实现MCCH的数据正常发送。
本发明实施例的技术方案是这样实现的：
本发明实施例提供一种数据发送方法，包括：eNB确认承载MCCH的PMCH不存在时，发送系统信息广播(System Information Block)消息；根据所述System Information Block消息配置多播/组播单频网络(Multimedia Broadcast multicast service Single Frequency Network，MBSFN)区域配置(Area Configuration)消息；根据所述System Information Block消息的配置或所述MBSFN Area Configuration消息的配置进行数据调度；发送所述MBSFN Area Configuration消息。
在一实施例中，所述确认承载MCCH的PMCH不存在，包括：eNB接收M2建立响应(SETUP RESPONSE)消息，未接收到MBMS调度信息指示(SCHEDULING INFORMATION)消息时，确认承载MCCH的PMCH不存在；或，eNB接收MBMS SCHEDULING INFORMATION消息，根据所述MBMS SCHEDULING INFORMATION消息确认承载MCCH的PMCH不存在。
在一实施例中，发送System Information Block消息前，所述方法还包括：eNB接收多小区/多播协调实体(Multi-cell/multicast Coordination Entity，MCE)配置更新(CONFIGURATION UPDATE)消息；相应的，所述发送System Information Block消息包括：通过空口发送System Information Block消息；其中，所述System Information Block消息的内容根据所述M2SET UP RESPONSE消息、所述eNB配置更新响应(CONFIGURATION UPDATE  ACKNOWLEDGE)消息和所述MCE CONFIGURATION UPDATE消息中消息时间较新的一个进行配置。
本发明实施例还提供一种数据发送方法，包括：UE接收System Information Block消息和MBSFN Area Configuration消息；
其中，所述MBSFN Area Configuration消息的内容由UE根据所述System Information Block消息进行配置，所述MBSFN Area Configuration消息指示PMCH的数量为N+1，其中，一个PMCH承载MCCH，承载MCCH的PMCH包含的MBMS会话数量为0。
本发明实施例还提供一种数据发送方法，包括：MCE发送指示承载MCCH的PMCH不存在的消息；接收所述消息的响应消息。
在一实施例中，所述指示承载MCCH的PMCH不存在的消息为：MBMS SCHEDULING INFORMATION消息；相应的，所述消息的响应消息为：MBMS SCHEDULING INFORMATION RESPONSE消息。
在一实施例中，MCE发送指示承载MCCH的PMCH不存在的消息前，所述方法还包括：MCE接收M2SET UP REQUEST消息，发送M2SET UP RESPONSE消息；MCE接收eNB配置更新消息，发送eNB配置更新响应消息或，MCE发送MCE CONFIGURATION UPDATE消息，接收MCE CONFIGURATION UPDATE ACKNOWLEDGE消息。
本发明实施例还提供一种eNB，所述eNB包括：确认模块、第一发送模块、配置模块、处理模块和第二发送模块；其中，
所述确认模块，配置为确认承载MCCH的PMCH是否存在；
所述第一发送模块，配置为确认模块确认承载MCCH的PMCH不存在时，发送System Information Block消息；
所述配置模块，配置为根据System Information Block消息配置MBSFN Area Configuration消息；
所述处理模块，配置为根据所述根据所述System Information Block消息的配置或MBSFN Area Configuration消息的配置进行数据调度；
所述第二发送模块，配置为发送所述MBSFN Area Configuration消息。
在一实施例中，所述eNB还包括第一接收模块，所述确认模块确认承载MCCH的PMCH不存在时，所述第一接收模块，配置为接收M2SET UP RESPONSE消息；或，所述第一接收模块，还配置为接收MBMS SCHEDULING INFORMATION消息，所述MBMS SCHEDULING INFORMATION消息指示承载MCCH的PMCH不存在。
在一实施例中，所述第一接收模块，还配置为接收MCECONFIGURATION UPDATE消息；相应的，所述第一发送模块，具体配置为通过空口发送System Information Block消息；其中，
所述System Information Block的内容根据所述M2SETUP RESPONSE消息、所述eNB CONFIGURATION UPDATE ACKNOWLEDGE消息和所述MCE CONFIGURATION UPDATE中消息时间较新的一个进行配置。
本发明实施例还提供一种UE，所述UE包括：第二接收模块和第三接收模块；其中，
所述第二接收模块，配置为接收System Information Block消息；
所述第三接收模块，配置为接收MBSFN Area Configuration消息；
所述MBSFN Area Configuration消息的内容由UE根据所述System Information Block消息进行配置，所述MBSFN Area Configuration消息指示PMCH的数量为N+1，其中，一个PMCH承载MCCH，承载MCCH的PMCH包含的MBMS会话数量为0。
本发明实施例还提供一种MCE，所述MCE包括：第三发送模块和第四接收模块，其中，
所述第三发送模块，配置为发送指示承载MCCH的PMCH不存在的消 息；
所述第四接收模块，配置为接收所述消息的响应消息。
在一实施例中，所述指示承载MCCH的PMCH不存在的消息为：MBMS SCHEDULING INFORMATION消息；相应的，所述消息的响应消息为：MBMS SCHEDULING INFORMATION RESPONSE消息。
在一实施例中，所述多小区/多播协调实体还包括：第四发送模块和第五接收模块；其中，
所述第四发送模块，配置为发送M2SET UP RESPONSE消息；所述第五接收模块，配置为接收M2SET UP REQUEST消息；或，所述第四发送模块，配置为发送eNB CONFIGURATION UPDATE ACKNOWLEDGE消息；所述第五接收模块，配置为接收CONFIGURATION UPDATE消息；或，所述第四发送模块，配置为发送MCE CONFIGURATION UPDATE消息；所述第五接收模块，配置为接收MCE CONFIGURATION UPDATE ACKNOWLEDGE消息。
本发明实施例还提供了一种计算机存储介质，所述计算机存储介质存储有计算机程序，该计算机程序用于执行本发明实施例的上述数据发送方法。
本发明实施例所提供的数据发送方法、设备及存储介质，MCE向eNB发送指示承载MCCH的PMCH不存在的消息；eNB确认承载MCCH的PMCH不存在时，向MCE发送所述消息的响应消息，并向UE发送System Information Block消息；UE接收System Information Block消息；eNB根据System Information Block消息配置MBSFN Area Configuration消息，根据所述System Information Block消息或MBSFN Area Configuration消息的配置进行数据调度，并将所述MBSFN Area Configuration消息发送至UE。本发明实施例中，eNB确认承载MCCH的PMCH不存在时，采用MCCH默认 发送机制，即：向UE发送System Information Block消息和MBSFN Area Configuration消息，所述MBSFN Area Configuration消息指示PMCH的数量为N+1，其中，第一个至第N个PMCH均不承载MCCH，第N+1个PMCH包含的MBMS会话的数量为0，使得承载MCCH的PMCH不存在时，MCCH的数据能够正常发送。
附图说明
图1为LTE eMBMS业务的服务区、同步区、MBSFN区的部署示意图；
图2为LTE eMBMS业务的逻辑构架图；
图3为本发明实施例eNB侧数据发送方法的基本处理流程示意图；
图4为LTE eMBMS业务的调度指示信息结构示意图；
图5为本发明实施例UE侧数据发送方法的基本处理流程示意图；
图6为本发明实施例MCE侧数据发送方法的基本处理流程示意图；
图7为本发明实施例一数据发送方法的详细处理流程示意图；
图8为本发明实施例二数据发送方法的详细处理流程示意图；
图9为本发明实施例三数据发送方法的详细处理流程示意图；
图10为本发明实施例四数据发送方法的详细处理流程示意图；
图11为本发明实施例eNB的组成结构示意图；
图12为本发明实施例UE的组成结构示意图；
图13为本发明实施例MCE的组成结构示意图。
具体实施方式
本发明实施例中，MCE向eNB发送指示承载MCCH的PMCH不存在的消息；eNB确认承载MCCH的PMCH不存在时，向MCE发送所述消息的响应消息，并向UE发送System Information Block消息；UE接收System Information Block消息；eNB根据System Information Block消息配置MBSFN  Area Configuration消息，根据所述System Information Block消息或MBSFN Area Configuration消息的配置进行数据调度，并将所述MBSFN Area Configuration消息发送至UE。
为更好地理解本发明实施例的技术方案，下面详细介绍LTE eMBMS业务。LTE eMBMS业务的服务区、同步区、MBSFN区的部署示意图，如图1所示；LTE eMBMS业务的逻辑构架图，如图2所示，其中，M1为用户面接口，M2为E-UTRAN内部控制面接口，M3为E-UTRAN和EPC控制面接口，MBMS GW为MBMS网关；MCE负责MBMS会话的管理，包括：MBMS会话的接纳控制、时域上的无线资源分配、MBSFN区域内各小区的MBMS数据的协调发送、各信道的调制编码方式参数等的无线配置等。
LTE eMBMS业务中，每个MBSFN区域有一个MCCH，零个或多个MTCH，MTCH复用在相同或不同的MCH上；其中，每个MTCH对应着一个MBMS会话。
LTE eMBMS业务中，控制面相关的接口包括M3口和M2口；其中，M3口是移动性管理实体(Mobility，MME)与MCE之间的接口，M2口是MCE与eNB之间间的接口；MCE通过M2口将相关配置参数传递给eNB，eNB根据接收到的相关参数进行System Information Block Type2消息、System Information Block Type13消息、MBSFN Area Configuration消息的填写，以及MBMS数据的调度与发送；其中，System Information Block Type13消息指示小区的MCCH相关的配置以及MCCH所在的MBSFN子帧的分配信息；MBSFN Area Configuration消息指示MCCH的具体内容，包括：小区内MBSFN区域公共子帧的分配信息、PMCH的配置信息、各MTCH的信息等。
LTE eMBMS业务中，由于eNB侧承载MCCH的PMCH不存在导致MCCH的数据无法发送的场景包括：1、在eNB和MCE完成M2口的建立， eNB收到MCE发送的MBMS SCHEDULING INFORMATION之前；2、MCE侧承载MCCH的PMCH上没有任何MBMS会话、或MCE侧没有任何MBMS会话时；由于eNB侧承载MCCH的PMCH不存在导致MCCH的数据无法发送的的原因为：根据3GPP TS36443-b309.1.7章节规范，通过M2口发送的MBMS SCHEDULING INFORMATION消息不支持PMCH上MBMS会话个数为0的情况；假设MCCH承载在某一PMCH上进行发送，但是该PMCH上不存在任何MBMS会话，MCE将此信息通知eNB时，需在MBMS SCHEDULING INFORMATION消息中携带该PMCH，且该PMCH中的MTCH个数为0；但是与3GPP TS36443-b30协议中MBMS SCHEDULING INFORMATION包含的会话个数最小为1的规定冲突；因此，在MCE侧承载MCCH的PMCH上没有任何MTCH时，通过M2口发送的MBMS SCHEDULING INFORMATION消息无法携带该PMCH。
本发明实施例eNB侧数据发送方法的基本处理流程，如图3所示，包括以下步骤：
步骤101，eNB确认承载MCCH的PMCH不存在时，发送System Information Block消息；
其中，承载MCCH的PMCH不存在包括指PMCH的个数为N，但N个PMCH均不承载MCCH，N为大于等于零的整数；
具体地，eNB确认承载MCCH的PMCH不存在包括：eNB接收MCE发送的M2SETUP RESPONSE消息，未接收到MBMS调度信息指示消息时，确认承载MCCH的PMCH不存在；或eNB接收MCE发送的MBMS SCHEDULING INFORMATION消息，所述MBMS SCHEDULING INFORMATION消息指示承载MCCH的PMCH不存在。
eNB通过空口向UE发送System Information Block消息，接收MCE发送的M2SETUP RESPONSE消息，未接收到MBMS调度信息指示消息时， 确认承载MCCH的PMCH不存在，所述System Information Block消息的内容根据所述M2SETUP RESPONSE消息进行配置；
所述MBMS SCHEDULING INFORMATION消息指示承载MCCH的PMCH不存在时，所述System Information Block消息的内容根据所述MCE CONFIGURATION UPDATE消息进行配置；
根据3GPP TS36331协议规范，UE在每个MCCH的修改周期均会读取MCCH，为节省UE用电，在eNB侧将System Information Block消息中MCCH的修改周期设置为协议允许的最大值；由MCE向eNB发送MCE CONFIGURATION UPDATE消息，用于eNB更新MCCH修改周期为协议允许的最大值；
这里，所述System Information Block消息可以为System Information Block Type13消息；本发明的下述实施例均以System Information Block消息为System Information Block Type13消息为例。
步骤102，根据所述System Information Block消息配置MBSFN Area Configuration消息；
这里，MBSFN Area Configuration消息中的MBSFN区域的公共子帧配置信息的设置，如：commonSF-Alloc，commonSF-AllocPeriod与System Information Block相同；MBSFN Area Configuration消息中PMCH的个数为N+1，增加的PMCH的配置与System Information Block消息相同，所述增加的PMCH包含MBMS会话个数为0；
根据3GPP TS36331协议规范，MBSFN Area Configuration消息中承载MCCH的PMCH的调度周期不能大于System Information Block消息中指示的MCCH重复周期；因此，为了保证被同一MCE服务的各eNB发送的消息内容一致，将PMCH调度周期设置为协议允许的最小值，或将PMCH的调度周期设置为与System Information Block消息中指示的MCCH重复周期 相同的值；如此，可最大程度地节省eNB侧的调度资源。
步骤103，eNB根据所述System Information Block消息或MBSFN Area Configuration消息的配置进行数据调度。
步骤104，eNB发送所述MBSFN Area Configuration消息；
具体地，eNB通过空口向UE发送所述MBSFN Area Configuration消息，所述调度指示信息的结构图，如图4所示。
本发明实施例UE侧数据发送方法的详细处理流程，如图5所示，包括以下步骤：
步骤201，UE接收System Information Block消息；
具体地，UE接收eNB通过空口发送的System Information Block消息；
其中，所述System Information Block消息的内容根据所述M2SETUP RESPONSE消息、所述eNB CONFIGURATION UPDATE ACKNOWLEDGE消息和MCE CONFIGURATION UPDATE消息中消息时间较新的一个进行配置；所述System Information Block消息中MCCH的修改周期为3GPP TS36331协议允许的最大值；
这里，所述System Information Block消息可以为System Information Block Type13消息。
步骤202，UE接收MBSFN Area Configuration消息；
具体地，UE接收eNB通过空口发送的MBSFN Area Configuration消息；
其中，MBSFN Area Configuration消息中的MBSFN区域的公共子帧配置信息的设置，如：commonSF-Alloc，commonSF-AllocPeriod与System Information Block Type13相同；MBSFN Area Configuration消息中PMCH的个数为N+1，其中，一个PMCH承载MCCH，承载MCCH的PMCH的配置与System Information Block相同，承载MCCH的PMCH包含MBMS会话个数为0；MBSFN Area Configuration消息中PMCH的调度周期为3GPP  TS36331协议协议允许的最小值，或PMCH的调度周期与System Information Block消息中指示的MCCH重复周期相同的值。
本发明实施例MCE侧数据发送方法的详细处理流程，如图6所示，包括以下步骤：
步骤301，MCE发送指示承载MCCH的PMCH不存在的消息；
其中，所述指示承载MCCH的PMCH不存在的消息为：MBMS SCHEDULING INFORMATION消息；
承载MCCH的PMCH不存在指PMCH的个数为N，但N个PMCH均不承载MCCH，N为大于等于零的整数。
步骤302，MCE接收所述消息的响应消息；
这里，所述消息的响应消息为：MBMS SCHEDULING INFORMATION RESPONSE消息。
在执行步骤301前，所述方法还包括：
步骤300，MCE发送M2SET UP REQUEST消息，接收M2SET UP RESPONSE消息；或，MCE发送MCE CONFIGURATION UPDATE消息，接收MCE CONFIGURATION UPDATE ACKNOWLEDG消息。
实施例一
本发明实施例一一种数据发送方法的详细处理流程示意图，如图7所示，包括以下步骤：
步骤401，eNB向MCE发送M2SET UP REQUEST消息。
步骤402，MCE向eNB回复M2SET UP RESPONSE消息；
这里，eNB未接收到MBMS调度信息指示消息，则确认承载MCCH的PMCH不存在；
其中，承载MCCH的PMCH不存在指PMCH的个数为N，但N个PMCH均不承载MCCH，N为大于或等于零的整数。
步骤403，eNB向UE发送System Information Block Type13消息；
具体地，eNB通过空口向UE发送System Information Block Type13消息；
其中，所述System Information Block Type13消息的内容根据M2SET UP RESPONSE消息进行配置；
根据3GPP TS36331协议规范，UE在每个MCCH的修改周期均会读取MCCH，为节省UE用电，在eNB侧将System Information Block Type13消息中MCCH的修改周期设置为协议允许的最大值；由MCE向eNB发送MCE CONFIGURATION UPDATE消息，用于eNB更新MCCH修改周期为协议允许的最大值。
步骤404，eNB根据System Information Block消息配置MBSFN Area Configuration消息；
这里，MBSFN Area Configuration消息中的MBSFN区域的公共子帧配置信息的设置，如：commonSF-Alloc，commonSF-AllocPeriod与System Information Block Type13相同；MBSFN Area Configuration消息中PMCH的个数为N+1，增加的PMCH的配置与System Information Block Type13相同，所述增加的PMCH包含MBMS会话个数为0；
根据3GPP TS36331协议规范，MBSFN Area Configuration消息中承载MCCH的PMCH的调度周期不能大于System Information Block Type13消息中指示的MCCH重复周期；因此，为了保证被同一MCE服务的各eNB发送的消息内容一致，将PMCH调度周期设置为协议允许的最小值，或将PMCH的调度周期设置为与System Information Block Type13消息中指示的MCCH重复周期相同的值；如此，可最大程度地节省eNB侧的调度资源。
步骤405，eNB根据所述System Information Block Type13消息或MBSFN Area Configuration消息的配置进行数据调度，发送所述MBSFN  Area Configuration消息；
具体地，eNB通过空口向UE发送所述MBSFN Area Configuration消息。
实施例二
本发明实施例二一种数据发送方法的详细处理流程示意图，如图8所示，包括以下步骤：
步骤501，eNB向MCE发送M2SET UP REQUEST消息。
步骤502，MCE向eNB发送M2SET UP RESPONSE消息。
步骤503，MCE向eNB发送MBMS SCHEDULING INFORMATION消息；
这里，所述MBMS SCHEDULING INFORMATION消息指示承载MCCH的PMCH不存在；
这里，承载MCCH的PMCH不存在指PMCH的个数为0。
步骤504，eNB向MCE发送MBMS SCHEDULING INFORMATION RESPONSE消息；
这里，eNB确认承载MCCH的PMCH不存在。
步骤505，eNB向UE发送System Information Block Type13消息；
具体地，eNB通过空口向UE发送System Information Block Type13消息；
其中，所述System Information Block Type13消息的内容根据M2SET UP RESPONSE消息进行配置；
根据3GPP TS36331协议规范，UE在每个MCCH的修改周期均会读取MCCH，为节省UE用电，在eNB侧将System Information Block Type13消息中MCCH的修改周期设置为协议允许的最大值；由MCE向eNB发送MCE CONFIGURATION UPDATE消息，用于eNB更新MCCH修改周期为协议允许的最大值。
步骤506，eNB根据System Information Block消息配置MBSFN Area Configuration消息；
这里，MBSFN Area Configuration消息中的MBSFN区域的公共子帧配置信息的设置，如：commonSF-Alloc，commonSF-AllocPeriod与System Information Block Type13相同；MBSFN Area Configuration消息中PMCH的个数为1，该PMCH的配置与System Information Block Type13相同，该PMCH包含MBMS会话个数为0；
根据3GPP TS36331协议规范，MBSFN Area Configuration消息中承载MCCH的PMCH的调度周期不能大于System Information Block Type13消息中指示的MCCH重复周期；因此，为了保证被同一MCE服务的各eNB发送的消息内容一致，将PMCH调度周期设置为协议允许的最小值，或将PMCH的调度周期设置为与System Information Block Type13消息中指示的MCCH重复周期相同的值；如此，可最大程度地节省eNB侧的调度资源。
步骤507，eNB根据所述System Information Block Type13消息或MBSFN Area Configuration消息的配置进行数据调度，发送所述MBSFN Area Configuration消息；
具体地，eNB通过空口向UE发送所述MBSFN Area Configuration消息。
实施例三
本发明实施例三一种数据发送方法的详细处理流程示意图，如图9所示，包括以下步骤：
步骤601，MCE向eNB发送MCE CONFIGURATION UPDATE消息。
步骤602，eNB向MCE发送MCE CONFIGURATION UPDATE ACKNOLNOWLEDGE消息。
步骤603，MCE向eNB发送MBMS SCHEDULING INFORMATION消息；
这里，所述MBMS SCHEDULING INFORMATION消息指示PMCH的个数为N，N为正整数，但是N个PMCH均不承载MCCH。
步骤604，eNB向MCE发送MBMS SCHEDULING INFORMATION RESPONSE消息；
这里，eNB确认承载MCCH的PMCH不存在。
步骤605，eNB向UE发送System Information Block Type13消息；
具体地，eNB通过空口向UE发送System Information Block Type13消息；
其中，所述System Information Block Type13消息的内容根据MCE CONFIGURATION UPDATE消息进行配置。
步骤606，eNB根据System Information Block Type13消息配置MBSFN Area Configuration消息；
这里，MBSFN Area Configuration消息中PMCH的个数为N+1，增加的PMCH的配置与System Information Block Type13相同，所述增加的PMCH包含MBMS会话个数为0；
根据3GPP TS36331协议规范，MBSFN Area Configuration消息中承载MCCH的PMCH的调度周期不能大于System Information Block Type13消息中指示的MCCH重复周期；因此，为了保证被同一MCE服务的各eNB发送的消息内容一致，将PMCH调度周期设置为协议允许的最小值，或将PMCH的调度周期设置为与System Information Block Type13消息中指示的MCCH重复周期相同的值；如此，可最大程度地节省eNB侧的调度资源。
步骤607，eNB根据所述System Information Block Type13消息或MBSFN Area Configuration消息的配置进行数据调度，发送所述MBSFN Area Configuration消息；
具体地，eNB通过空口向UE发送所述MBSFN Area Configuration消息。
实施例四
本发明实施例四一种数据发送方法的详细处理流程示意图，如图10所示，包括以下步骤：
步骤701，eNB向MCE发送eNB CONFIGURATION UPDATE消息。
步骤702，MCE向eNB发送eNB CONFIGURATION UPDATE ACKNOLNOWLEDGE消息。
步骤703，MCE向eNB发送MBMS SCHEDULING INFORMATION消息；
这里，所述MBMS SCHEDULING INFORMATION消息指示PMCH的个数为N，N为正整数，但是N个PMCH均不承载MCCH。
步骤704，eNB向MCE发送MBMS SCHEDULING INFORMATION RESPONSE消息；
这里，eNB确认承载MCCH的PMCH不存在。
步骤705，eNB向UE发送System Information Block Type13消息；
具体地，eNB通过空口向UE发送System Information Block Type13消息；
其中，所述System Information Block Type13消息的内容根据eNB CONFIGURATION UPDATE ACKNOWLEDGE消息进行配置。
步骤706，eNB根据System Information Block Type13消息配置MBSFN Area Configuration消息；
这里，MBSFN Area Configuration消息中的MBSFN区域的公共子帧配置信息的设置，如：commonSF-Alloc，commonSF-AllocPeriod与System Information Block Type13相同；MBSFN Area Configuration消息中PMCH的个数为N+1，增加的PMCH的配置与System Information Block Type13相同，所述增加的PMCH包含MBMS会话个数为0；
根据3GPP TS36331协议规范，MBSFN Area Configuration消息中承载MCCH的PMCH的调度周期不能大于System Information Block Type13消息中指示的MCCH重复周期；因此，为了保证被同一MCE服务的各eNB发送的消息内容一致，将PMCH调度周期设置为协议允许的最小值，或将PMCH的调度周期设置为与System Information Block Type13消息中指示的MCCH重复周期相同的值；如此，可最大程度地节省eNB侧的调度资源。
步骤707，eNB根据所述System Information Block Type13消息或MBSFN Area Configuration消息的配置进行数据调度，发送所述MBSFN Area Configuration消息；
具体地，eNB通过空口向UE发送所述MBSFN Area Configuration消息。
为实现上述数据发送方法，本发明实施例还提供一种eNB，所述eNB的组成结构示意图，如图11所示，包括：确定模块11、第一发送模块12、配置模块13、处理模块14和第二发送模块15；其中，
所述确定模块11，配置为确定承载MCCH的PMCH是否存在；
所述第一发送模块12，配置为确认模块确认承载MCCH的PMCH不存在时，发送System Information Block消息；
所述配置模块13，配置为根据System Information Block消息配置MBSFN Area Configuration消息；
所述处理模块14，配置为根据所述根据所述System Information Block消息或MBSFN Area Configuration消息的配置进行数据调度；
所述第二发送模块15，配置为发送所述MBSFN Area Configuration消息。
在一实施例中，所述基站还包括：第一接收模块16，所述确认模块确认承载MCCH的PMCH不存在时，
所述第一接收模块16，配置为接收M2SETUP RESPONSE消息；或，
所述第一接收模块16，还配置为接收MBMS SCHEDULING INFORMATION消息，所述MBMS SCHEDULING INFORMATION消息指示承载MCCH的PMCH不存在。
在一实施例中，所述第一接收模块16，还配置为接收MCE配置更新消息；
相应的，所述第一发送模块12，具体配置为通过空口发送System Information Block消息；其中，所述M2SETUP RESPONSE消息指示承载MCCH的PMCH不存在时，所述System Information Block消息的内容根据所述M2SETUP RESPONSE消息进行配置；
所述MBMS SCHEDULING INFORMATION消息指示承载MCCH的PMCH不存在时，所述System Information Block消息的内容根据所述MBMS SCHEDULING INFORMATION RESPONSE消息、所述eNB CONFIGURATION UPDATE ACKNOWLEDGE消息和所述MCE CONFIGURATION UPDATE消息中消息时间较新的一个进行配置。
在一实施例中，根据3GPP TS36331协议规范，UE在每个MCCH的修改周期均会读取MCCH，为节省UE用电，在eNB侧将System Information Block消息中MCCH的修改周期设置为协议允许的最大值；由MCE向eNB发送MCE CONFIGURATION UPDATE消息，用于eNB更新MCCH修改周期为协议允许的最大值。
根据3GPP TS36331协议规范，MBSFN Area Configuration消息中承载MCCH的PMCH的调度周期不能大于System Information Block消息中指示的MCCH重复周期；因此，为了保证被同一MCE服务的各eNB发送的消息内容一致，将PMCH调度周期设置为协议允许的最小值，或将PMCH的调度周期设置为与System Information Block消息中指示的MCCH重复周期相同的值；如此，可最大程度地节省eNB侧的调度资源。
为实现上述数据发送方法，本发明实施例还提供一种UE，所述UE的组成结构示意图，如图12所示，包括：第二接收模块21和第三接收模块22；其中，
所述第二接收模块21，配置为接收System Information Block消息；
所述第三接收模块22，配置为接收MBSFN Area Configuration消息；
所述MBSFN Area Configuration消息的内容由UE根据所述系统信息广播消息进行配置，指示PMCH的数量为N+1，其中，一个PMCH承载MCCH，承载MCCH的PMCH包含的MBMS会话数量为0。
在一实施例中，UE接收eNB通过空口发送的System Information Block消息和MBSFN Area Configuration消息；
其中，所述System Information Block消息的内容根据所述M2SETUP RESPONSE消息、所述eNB CONFIGURATION UPDATE ACKNOWLEDGE消息和所述MEC CONFIGURATION UPDATE消息中消息时间较新的一个进行配置；所述System Information Block消息中MCCH的修改周期为3GPPTS36331协议允许的最大值；
MBSFN Area Configuration消息中的MBSFN区域的公共子帧配置信息的设置，如：commonSF-Alloc，commonSF-AllocPeriod与System Information Block消息相同；MBSFN Area Configuration消息中PMCH的个数为N+1，增加的PMCH的配置与System Information Block消息相同，所述增加的PMCH包含MBMS会话个数为0；MBSFN Area Configuration消息中PMCH的调度周期为3GPP TS36331协议协议允许的最小值，或PMCH的调度周期与System Information Block Type13消息中指示的MCCH重复周期相同的值。
为实现上述数据发送方法，本发明实施例还提供一种MCE，所述MCE的组成结构示意图，如图13所示，包括：第三发送模块31、第四接收模块 32、第四发送模块33和第五接收模块34，其中，
所述第三发送模块31，配置为发送指示承载MCCH的PMCH不存在的消息；
所述第四接收模块32，配置为接收所述消息的响应消息；
所述第四发送模块33，配置为发送M2SET UP RESPONSE消息；
所述第五接收模块34，配置为接收M2SET UP REQUEST消息；或，
所述第四发送模块33，配置为发送eNB CONFIGURATION UPDATE ACKNOWLEDGE消息；
所述第五接收模块34，配置为接收eNB CONFIGURATION UPDATE消息；或，
所述第四发送模块33，配置为发送MCE CONFIGURATION UPDATE消息；
所述第五接收模块34，配置为接收MCE CONFIGURATION UPDATE ACKNOWLEDGE消息。
在一实施例中，所述消息的响应消息为：MBMS SCHEDULING INFORMATION RESPONSE消息。
本发明实施例中提出的eNB中的确定模块11、第一发送模块12、配置模块13、处理模块14、第二发送模块15和第一接收模块16，UE中的第二接收模块21和第三接收模块22，MCE中的第三发送模块31、第四接收模块32、第四发送模块33和第五接收模块34都可以通过处理器来实现，当然也可通过具体的逻辑电路实现；其中所述处理器可以是移动终端或服务器上的处理器，在实际应用中，处理器可以为中央处理器(CPU)、微处理器(MPU)、数字信号处理器(DSP)或现场可编程门阵列(FPGA)等。
本发明实施例中，如果以软件功能模块的形式实现上述数据发送方法，并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介 质中。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read Only Memory，ROM)、磁碟或者光盘等各种可以存储程序代码的介质。这样，本发明实施例不限制于任何特定的硬件和软件结合。
相应地，本发明实施例还提供一种计算机存储介质，该计算机存储介质中存储有计算机程序，该计算机程序用于执行本发明实施例的上述数据发送方法。
以上所述仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。

Claims (17)

  1. 一种数据发送方法，所述方法包括：
    基站eNB确认承载多点控制信道MCCH的物理多播信道PMCH不存在时，发送系统信息广播消息；
    根据所述系统信息广播消息配置多播/组播单频网络MBSFN区域配置消息；
    根据所述系统信息广播消息的配置或所述MBSFN区域配置消息的配置进行数据调度；
    发送所述MBSFN区域配置消息。
  2. 根据权利要求1所述数据发送方法，其中，所述确认承载MCCH的PMCH不存在，包括：
    eNB接收M2建立请求响应消息，未接收到MBMS调度信息指示消息时，确认承载MCCH的PMCH不存在；或，
    eNB接收MBMS调度信息指示消息，根据所述MBMS调度信息指示消息确认承载MCCH的PMCH不存在。
  3. 根据权利要求2所述数据发送方法，其中，发送系统信息广播消息前，所述方法还包括：eNB接收多小区/多播协调实体MCE配置更新消息；
    相应的，所述发送系统信息广播消息包括：通过空口发送系统信息广播消息；其中，
    所述系统信息广播消息的内容根据所述M2建立请求响应消息、eNB配置更新响应消息和所述MCE配置更新消息中消息时间较新的一个进行配置。
  4. 一种数据发送方法，所述方法包括：
    用户设备UE接收系统信息广播消息和MBSFN区域配置消息；
    其中，所述MBSFN区域配置消息的内容由UE根据所述系统信息广播消息进行配置，所述MBSFN区域配置消息指示PMCH的数量为N+1，其中，第一个至第N个PMCH均不承载MCCH，第N+1个PMCH包含的MBMS会话的数量为0。
  5. 一种数据发送方法，所述方法包括：
    MCE发送指示承载MCCH的PMCH不存在的消息；
    接收所述消息的响应消息。
  6. 根据权利要求5所述数据发送方法，其中，所述指示承载MCCH的PMCH不存在的消息为：MBMS调度信息指示消息；
    相应的，所述消息的响应消息为：MBMS调度信息指示响应消息。
  7. 根据权利要求5所述数据发送方法，其中，MCE发送指示承载MCCH的PMCH不存在的消息前，所述方法还包括：
    MCE接收M2建立请求消息，发送M2建立请求响应消息；或，
    MCE接收eNB配置更新消息，发送eNB配置更新响应消息；或
    MCE发送MCE配置更新消息，接收MCE配置更新响应消息。
  8. 一种基站，所述基站包括：确认模块、第一发送模块、配置模块、处理模块和第二发送模块；其中，
    所述确认模块，配置为确认承载MCCH的PMCH是否存在；
    所述第一发送模块，配置为确认模块确认承载MCCH的PMCH不存在时，发送系统信息广播消息；
    所述配置模块，配置为根据所述系统信息广播消息配置MBSFN区域配置消息；
    所述处理模块，配置为根据所述系统信息广播消息的配置或MBSFN区域配置消息的配置进行数据调度；
    所述第二发送模块，配置为发送所述MBSFN区域配置消息。
  9. 根据权利要求8所述基站，其中，所述基站还包括第一接收模块，所述确认模块确认承载MCCH的PMCH不存在时，
    所述第一接收模块，配置为接收M2建立请求响应消息；或，
    所述第一接收模块，还配置为接收MBMS调度信息指示消息，所述MBMS调度信息指示消息指示承载MCCH的PMCH不存在。
  10. 根据权利要求9所述基站，其中，所述第一接收模块，还配置为接收MCE配置更新消息；相应的，所述第一发送模块，配置为通过空口发送系统信息广播消息；其中，
    所述系统信息广播消息的内容根据所述M2建立请求响应消息、eNB配置更新响应消息和所述MCE配置更新消息中消息时间较新的一个进行配置。
  11. 一种用户设备，所述用户设备包括：第二接收模块和第三接收模块；其中，
    所述第二接收模块，配置为接收系统信息广播消息；
    所述第三接收模块，配置为接收MBSFN区域配置消息；
    所述MBSFN区域配置消息的内容由UE根据所述系统信息广播消息进行配置，所述MBSFN区域配置消息指示PMCH的数量为N+1，其中，第一个至第N个PMCH均不承载MCCH，第N+1个PMCH包含的MBMS会话的数量为0。
  12. 一种多小区/多播协调实体，所述多小区/多播协调实体包括：第三发送模块和第四接收模块，其中，
    所述第三发送模块，配置为发送指示承载MCCH的PMCH不存在的消息；
    所述第四接收模块，配置为接收所述消息的响应消息。
  13. 根据权利要求12所述多小区/多播协调实体，其中，所述指示承载 MCCH的PMCH不存在的消息为：MBMS调度信息指示消息；
    相应的，所述消息的响应消息为：MBMS调度信息指示响应消息。
  14. 根据权利要求12所述多小区/多播协调实体，其中，所述多小区/多播协调实体还包括：第四发送模块和第五接收模块；其中，
    所述第四发送模块，配置为发送M2建立请求响应消息；
    所述第五接收模块，配置为接收M2建立请求消息；或，
    所述第四发送模块，配置为发送eNB配置更新响应消息；
    所述第五接收模块，配置为接收eNB配置更新消息；或，
    所述第四发送模块，配置为发送MCE配置更新消息；
    所述第五接收模块，配置为接收MCE配置更新响应消息。
  15. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，该计算机可执行指令用于执行权利要求1至6任一项所述的数据发送方法。
  16. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，该计算机可执行指令用于执行权利要求4所述的数据发送方法。
  17. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，该计算机可执行指令用于执行权利要求5至7任一项所述的数据发送方法。
PCT/CN2014/095194 2014-09-19 2014-12-26 一种数据发送方法、设备和存储介质 WO2015131638A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2017516884A JP6346710B2 (ja) 2014-09-19 2014-12-26 データ送信方法、装置及び記憶媒体
US15/514,015 US10869168B2 (en) 2014-09-19 2014-12-26 Method, device, and storage medium for data transmission
EP14885021.7A EP3203763B1 (en) 2014-09-19 2014-12-26 Data transmission methods, devices, and storage medium

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201410484504 2014-09-19
CN201410514103.XA CN104284300B (zh) 2014-09-19 2014-09-29 一种数据发送方法和设备
CN201410514103.X 2014-09-29

Publications (1)

Publication Number Publication Date
WO2015131638A1 true WO2015131638A1 (zh) 2015-09-11

Family

ID=52258682

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/095194 WO2015131638A1 (zh) 2014-09-19 2014-12-26 一种数据发送方法、设备和存储介质

Country Status (5)

Country Link
US (1) US10869168B2 (zh)
EP (1) EP3203763B1 (zh)
JP (1) JP6346710B2 (zh)
CN (1) CN104284300B (zh)
WO (1) WO2015131638A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108781389B (zh) * 2016-01-27 2021-01-01 诺基亚通信公司 用于实现移动边缘应用会话连接性和移动性的方法和装置
EP3461192B1 (en) * 2016-06-23 2021-07-28 LG Electronics Inc. Method for receiving mbms service and device for supporting same
TWI627872B (zh) * 2017-09-05 2018-06-21 財團法人工業技術研究院 具有基地台網管伺服器之網路通訊系統的控制方法與邊緣運算裝置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003055256A1 (de) * 2001-12-05 2003-07-03 Siemens Aktiengesellschaft Verfahren zur zuweisung von übertragungskanälen in einer mobilfunkzelle für einen multicast-dienst
CN101888591A (zh) * 2009-05-12 2010-11-17 大唐移动通信设备有限公司 一种更新多播信道配置信息的方法及系统
CN102264033A (zh) * 2010-05-27 2011-11-30 中兴通讯股份有限公司 一种mbms统计消息的处理方法和装置
JP5310598B2 (ja) * 2010-02-24 2013-10-09 日本電気株式会社 携帯端末装置及びそれに用いる消費電力削減方法並びにそのプログラム
CN103888956A (zh) * 2012-12-19 2014-06-25 中兴通讯股份有限公司 配置信息的处理方法及系统
WO2014119847A1 (ko) * 2013-02-01 2014-08-07 엘지전자 주식회사 Mbsfn 서브프레임 송신 및 수신 방법 및 장치

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102118694B (zh) * 2010-01-11 2014-05-28 电信科学技术研究院 确定组播单频网区域与业务区域映射关系的方法和系统
EP2389019A3 (en) * 2010-03-31 2012-08-01 HTC Corporation Method for realizing MBMS under bandwidth aggregation, CoMP and relay operation
CN102348162A (zh) * 2010-07-28 2012-02-08 中兴通讯股份有限公司 一种发送mbms控制信息的方法及系统
DK2705685T3 (en) * 2011-05-03 2015-04-27 Ericsson Telefon Ab L M The measurements made by means of a wireless device
US20130235783A1 (en) * 2012-03-09 2013-09-12 Qualcomm Incorporated Evolved multimedia broadcast multicast service capacity enhancements
US9781649B2 (en) * 2012-08-02 2017-10-03 Qualcomm Incorporated MBMS support in heterogeneous network and in-venue
JP2015142225A (ja) * 2014-01-28 2015-08-03 ソニー株式会社 装置
US20170180952A1 (en) * 2014-08-04 2017-06-22 Lg Electronics Inc. Method and apparatus for supporting broadcast mobile convergence in wireless communication system

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003055256A1 (de) * 2001-12-05 2003-07-03 Siemens Aktiengesellschaft Verfahren zur zuweisung von übertragungskanälen in einer mobilfunkzelle für einen multicast-dienst
CN101888591A (zh) * 2009-05-12 2010-11-17 大唐移动通信设备有限公司 一种更新多播信道配置信息的方法及系统
JP5310598B2 (ja) * 2010-02-24 2013-10-09 日本電気株式会社 携帯端末装置及びそれに用いる消費電力削減方法並びにそのプログラム
CN102264033A (zh) * 2010-05-27 2011-11-30 中兴通讯股份有限公司 一种mbms统计消息的处理方法和装置
CN103888956A (zh) * 2012-12-19 2014-06-25 中兴通讯股份有限公司 配置信息的处理方法及系统
WO2014119847A1 (ko) * 2013-02-01 2014-08-07 엘지전자 주식회사 Mbsfn 서브프레임 송신 및 수신 방법 및 장치

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3203763A4 *

Also Published As

Publication number Publication date
EP3203763B1 (en) 2019-10-16
US10869168B2 (en) 2020-12-15
US20170280303A1 (en) 2017-09-28
JP2017532902A (ja) 2017-11-02
CN104284300A (zh) 2015-01-14
JP6346710B2 (ja) 2018-06-20
EP3203763A1 (en) 2017-08-09
CN104284300B (zh) 2020-12-11
EP3203763A4 (en) 2017-10-04

Similar Documents

Publication Publication Date Title
US12015967B2 (en) Method, system and apparatus for multicast session management in 5G communication network
EP3282725B1 (en) Base station and user terminal
US11071089B2 (en) Dynamic switching of streaming service between broadcast and unicast delivery
JP6334005B2 (ja) 基地局、ユーザ端末、及び通信制御方法
WO2017028580A1 (zh) 单小区多播控制信道的资源配置方法、系统及装置
EP3324666B1 (en) Sc-mcch resource configuration method and apparatus
WO2011147237A1 (zh) 多媒体广播组播业务控制信息的发送方法及装置
JP5199310B2 (ja) Ｍｂｍｓ動的スケジューリング情報を処理する方法および装置
TW201438493A (zh) 致能無線通信器件以自一個本地網路切換至用於高優先權多播群組通信之不同廣域網路
US20150063188A1 (en) METHOD FOR DETERMINING DELAY PARAMETERS FOR USER DATA FLOW SYNCHRONIZATION FOR eMBMS
WO2021063215A1 (zh) 一种网络切片的组播方法及装置
JP2017532928A (ja) セルラー・ネットワークにおけるマルチキャストのためのカバレッジの強化
JPWO2016121671A1 (ja) 基地局及びユーザ端末
WO2015168985A1 (zh) 更新多媒体广播多播控制信道信息的方法及设备
WO2017070838A1 (zh) 资源调度方法、基站、调度器、节目源服务器和系统
US20150358785A1 (en) Transmitting embms control information to wireless devices in a wireless telecommunications network
WO2015131638A1 (zh) 一种数据发送方法、设备和存储介质
WO2018059410A1 (zh) 业务回话发送、接收方法、装置、系统及存储介质
WO2016041441A1 (zh) 一种数据发送方法、设备及存储介质
WO2016175255A1 (ja) 無線端末及びネットワーク装置
US10819802B2 (en) Enabling transmission of streaming content using point to multipoint delivery
CN102572702B (zh) Mbms的计数处理方法及系统
WO2015139748A1 (en) Transmissions in wireless systems
WO2012122952A1 (zh) 激活控制方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14885021

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15514015

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2017516884

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014885021

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014885021

Country of ref document: EP