WO2012075829A1 - Method and system for counting multimedia broadcast multicast services - Google Patents

Abstract

The present invention provides a method and a system for counting multimedia broadcast multicast services. The method comprises: an MCE configuring an MBMS service counting parameter, wherein the MBMS service counting parameter comprises an identifier of an MBMS service to be counted in one or more MBSFN regions and update time of an MCCH corresponding to each MBSFN region; the MCE sending a message carrying the MBMS service counting parameter to an eNB; and the eNB starting to count the MBMS services corresponding to the identifiers of the MBMS services in each MBSFN region according to the update time of the MCCH corresponding to each MBSFN region. The present invention solves the problem in the prior art that counting the MBMS services in multiple MBSFN regions cannot be started, and implements synchronous sending of the MBMS counting request message.

Description

TECHNICAL FIELD The present invention relates to the field of Multimedia Broadcast Multicast Service (MBMS), and in particular, to a method and system for counting multimedia broadcast multicast services. BACKGROUND With the rapid development of the Internet and the popularization of large-screen multi-function mobile phones, a large number of mobile data multimedia services and various high-bandwidth multimedia services, such as video conferencing, television broadcasting, video on demand, video advertising, online education, and interactive games, have emerged. Wait. These mobile data multimedia services and various high-bandwidth multimedia services not only meet the rising business demands of mobile users, but also bring new business growth points to mobile operators. These mobile data multimedia services and various high-bandwidth multimedia services require multiple users to receive the same data at the same time, and have the characteristics of large data volume, long duration, and delay sensitivity compared with general data services. In order to effectively utilize mobile network resources, the 3rd Generation Partnership Project (3GPP) proposes Multimedia Broadcast Multicast Service (MBMS), which is a data source from a data source. The technology of transmitting data to multiple targets realizes the sharing of resources of the network (including the core network and the access network) and improves the utilization of network resources (especially air interface resources). The MBMS service defined by 3GPP can not only realize the multicast and broadcast of plain text low-rate message classes, but also realize the broadcast and multicast of high-speed multimedia services, and provide a variety of rich video, audio and multimedia services, which undoubtedly conforms to the future. The trend of mobile data development provides a better business prospect for the development of third-generation (3G) digital communications. Currently, the MBMS service is introduced in the LTE Release 9 (R9) system and optimized in LTE Release 10 (R10). The MBMS service is implemented in the system by carrying a common transmission of control signaling (also referred to as MBMS control signaling) and user data (also known as MBMS service). The control signaling will inform the receiving end (such as the terminal, User Equipment (UE)) corresponding control parameters, and direct the UE to the corresponding location to receive the MBMS service (ie, corresponding user data) of interest. The MBMS control signaling (control information, including: MBMS service configuration information, etc.) is transmitted in the LTE system through a Multicast Control Channel (MCCH), and the MBMS service is through a multicast service. The Multicast Traffic Channel (MTCH) is used for transmission. Specifically, the MBMS control signaling (ie, MCCH information) transmitted on the logical channel MCCH mainly includes: a multicast single frequency network corresponding to the MCCH information (MBMS over a Single Frequency Network, Multicast resources in the MBSFN area, all MBMS services in the MBSFN area (or MBMS services that have already started, or MBMS services that have already been session start), and ingoing MBMS services. Configuration and attribute information; In the logical channel MTCH, the MBMS service data is carried, and the MBMS service is generally associated with the MTCH (for example: MBMS service 1 corresponds to MTCH1, MBMS service 2 corresponds to MTCH2), that is, the UE reads the MBMS. The service has the same meaning as the UE reads the MTCH expression. In the network, each MBMS service is uniquely identified by using the TMGK Temporary Mobile Group Identity, and each MBMS service has its corresponding TMGI, which is convenient for the network side and the UE to identify. The MCCH information corresponding to the MBSFN area (domain) will be sent according to a certain rule (repetition period, modification period), as shown in FIG. 1 . As shown in Figure 1, the MCCH information will be sent one or more times during the modification period (repeated 3 times in Figure 1); the time interval between repeated transmission of MCCH information is called MCCH repetition period; MCCH is generally During the modification period, the first transmission of MCCH information is called first transmission, and the transmission of each repetition period is called MCCH information repeated transmission. The MCCH information of repeated transmission is exactly the same as the MCCH information content of the first transmission; the MCCH modification period indicates that The content of the transmitted MCCH information may be different in different MCCH modification periods; the content of the n+1 period of the MCCH modification period in FIG. 1 is different from the content of the n-cycle (the slashed squares and the blank squares are shown in FIG. 1) Different contents of the MCCH information); It should be noted that during the MCCH modification period, the content of the MCCH information cannot be changed, and only the repetition period can be repeated. The content of the MCCH information is only allowed to change at the boundary of the beginning of the MCCH modification period; that is, the MCCH information change can only occur when the MCCH information is sent for the first time in the MCCH modification period, also known as the MCCH change time ( MCCH change time). Such a provision guarantees the consistency of MCCH information transmission within the MBSFN area (multiple eNB (evolved Node B)). In the present invention, if the counting of several MBMS services is added or updated or deleted on the MCCH, the MCCH information change is triggered. Therefore, in the present invention, the eNB adds a WMS service list to be counted/updated on the current MCCH. , can only change the moment in the MCCH.

The configuration parameters of the MCCH repetition period and the modification period are configured by the network side, and the network side sends the UE to the UE through the SIB13 (System Information Block 13) in the BCCH. The UE can learn by reading the SIB13 in the BCCH. The configuration parameters of the MCCH repetition period and the modification period, the UE may read the MCCH information at the corresponding location. Considering the related art, sending control signaling (MCCH) and user data in the MBSFN Area

(MTCH) The MBSFN technology will be used for synchronous transmission in units of cells or eNBs (the purpose is to enable the UE to obtain the corresponding combining gain when receiving), and the MBSFN technology requires each cell in the MBSFN area to be in phase. The same data content is sent on the same time-frequency resource, so that the resources of each cell need to be uniformly scheduled and planned. Currently, the MCE (Multi-cell/Multicast Coordination Entity) network element is used for unified scheduling and planning of radio resources. For details, refer to the international standard 3GPP 36.300 v910. 2 is a schematic structural diagram of an MBMS control system in the related art. As shown in FIG. 2, in the system, an MBMS-related network element includes an eNB, an MCE, an MBMS Gateway, and a Broadcast Multicast Service Center. Service Centre (BM-SC) and Mobility Management Entity (MME), where BM-SC is used as a Service Start, Session Stop, Session Updated or MBMS Service Data The provided network element; the MBMS GW sends the MBMS service data to the corresponding e B through the M1 interface; the MBMS GW sends the control plane information generated by the BM-SC through the Sm interface (for example, Session Start Request message Session Stop Request message Session Updated Request message) Sending to the MME; the MME is completely used as a forwarding network element, and the control plane information sent by the MBMS GW is forwarded to the MCE through the M3 interface; the MCE sends the corresponding control plane information to the corresponding eNB through the M2 interface; by such processing, the eNB will MBMS business data and corresponding control plane information will be obtained. Generally, the MCE sends the control plane information to the eNB through the M2 interface, that is, the signaling and the process are carried on the M2 interface, which is called the M2 application protocol, and the BP: M2 Application Protocol (M2AP), including: Session Start Request Message (session start message), Session Stop Request message (session stop request message), MBMS SCHEDULING INFORMATION message, Rest message, M2 SETUP REQUEST message ( The M2 setup request message), and the corresponding message sent by the M2 interface eNB to the MCE, for example: Session Start Response message, Session Stop Response message, Session Updated Response message ( Session update response message), MBMS SCHEDULING INFORMATION Response message, Rest ACKNOWLEDGE message, M2 SETUP Response message. From the above, we can see that the MBMS service will be transmitted in the entire MBSFN area, and each MBSFN area will correspond to one MCCH. In order to further optimize the transmission of the MBMS service, the industry intends to introduce the UE uplink feedback mechanism. Specifically, the uplink feedback mechanism is mainly applied to the number of users (or the number of UEs) that are interested in receiving/receiving each MBMS service on the network side; The side optimizes the transmission of the MBMS service by obtaining the number of users, for example: deactivation, or not sending. Interested/receiving MBMS services with a small number of users, activation (or called transmission) / Receiving MBMS services with a large number of users. In order to know the number of UEs (or yes/no) that are interested in receiving/receiving a certain MBMS service, the network side may send a counting command (counting command) to enable the UE that is interested in receiving/receiving the MBMS service to perform uplink feedback to inform the network. The UE currently receives the status of the MBMS. Network side can Obtaining information through the uplink feedback of the UE (ie, how many interested/receiving UEs are available for a certain MBMS); the network side applies the obtained information (Counting result) to the activation or deactivation of the MBMS service. (deactivation) operation; in other words, the network side may determine, according to the information obtained by the uplink feedback, whether the MBMS service is deactivated on the air interface for transmission. According to the related art: The MBMS counting process includes a counting request process and a counting report process on the M2 interface and a counting process on the Uu interface. As shown in FIG. 3, the foregoing process specifically includes:

1) The MCE sends a message (referred to as message 1 in the present invention) to the eNB on the M2 interface, and is used to indicate the related eNB starting counting process under the control (ie, performing the MBMS service Uu counting process on the Uu interface);

2) After receiving the message 1, the eNB sends a message 2, also called a counting request message (Counting Request message), on one or more MCCHs, and the message 2 sent on each MCCH carries the corresponding one in the message respectively.

The MBMS service in the MBSFN area, that is, the service carried in each message 2 is the MBMS service of the MBSFN area in Message 1 that needs to be counted. When there are multiple MBMS services in the MBSFN area that need to be counted in the message 1, the eNB sends a message 2 that is the same as the number of MBFN areas.

The UE in the cell reads the MCCH, and if it finds that it is interested in the MBMS service configured on the MCCH, it sends a count response message (referred to as message 3 in the present invention) to the eNB, and the message carries the sense. Interest or MBMS service being received.

4) Finally, the eNB sends a report message to the MCE (referred to as message 4 in the present invention) for reporting to the MCE the number of UEs that are interested in or receiving each MBMS service. Since the MBMS service that needs to be counted in multiple MBSFN areas can be configured in the message 1, the MCCH update time of each MBSFN area may be different, so that the time when the eNB receives the counting result of the different MBSFN areas of the message 3 is different. However, the prior art does not specify how to initiate the counting process of MBMS services in multiple MBSFN areas, and how to report the counting results of MBMS services in multiple MBSFN areas. SUMMARY OF THE INVENTION The present invention is directed to a method and system for counting transmission of a multimedia broadcast multicast service, which can solve the problem that the MBMS service in multiple MBSFN areas cannot be started in the prior art, or the MBMS in multiple MBSFN areas cannot be performed. The problem of reporting the result of the counting of the business. According to an aspect of the present invention, a method for counting a multimedia broadcast multicast service is provided, including: MCE configuring an MBMS service count parameter, wherein the MBMS service count parameter: one or more MBSFNs The MBMS service identifier to be counted in the area, the update time of the MCCH corresponding to each MBSFN area; the MCE sends a message carrying the MBMS service count parameter to the eNB; and the eNB performs the update time of the MCCH corresponding to each MBSFN area. The counting of the MBMS service corresponding to the MBMS service identifier in each of the MBSFN areas is started. The step of configuring the MBMS service count parameter by the MCE includes: configuring, by the MCE, one or more update times for the MCCH corresponding to each of the foregoing MBSFN areas. MCE above said MBSFN area includes a plurality of corresponding MCCH updated by one of the following steps: a plurality of the above-mentioned MCE is updated MCCH corresponding to the MBSFN area above; or the above-mentioned MCE is arranged above MCCH corresponding to the MBSFN area and an update time Corresponding update time interval, wherein the update time interval indicates a time difference between the last update time of the MCCH and the current update time of the MCCH; or the MCE configures an update time for the MCCH corresponding to the MBSFN area and adopts The default update interval T, Τ = 0, 1, 2, wherein the default update interval indicates the time difference between the previous update time of the MCCH and the current update time of the MCCH. The step of configuring the MBMS service count parameter by the MCE includes: when the number of the MBMS services that need to be counted on one of the MBSFN areas exceeds the maximum number of MBMS services that are initiated by the eNB, the MCE is the one MBSFN. The MCCH corresponding to the area is configured with multiple update times. When the MCE is configured with an update time and a corresponding update time interval for the MCCH corresponding to the MBSFN area, the eNB starts the MBMS corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area. The step of counting the service includes: the foregoing update time interval is configured to be 0, and is used to indicate that the eNB continuously starts counting the MBMS service corresponding to the MBMS service identifier in the MBSFN area; or the update time interval is configured as N, N≥ And indicating that the foregoing eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in the MBSFN area every N MCCH modification periods. After the eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each of the MBSFN areas according to the update time of the MCCH corresponding to each of the MBSFN areas, the eNB further includes: the eNB receives the counting result of the MBMS service sent by the terminal UE. When the eNB receives the count result of all the MBMS services that need to be counted on all the MBSFN areas, the eNB sends the count result of all the MBMS services that need to be counted on all the MBSFN areas to the MCE. After the eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each of the MBSFN areas according to the update time of the MCCH corresponding to each of the MBSFN areas, the eNB further includes: the eNB receives the counting result of the MBMS service sent by the terminal UE. Whenever the above eNB receives one or more When the one or more MBMS services in the MBSFN area are counted as a result of counting the MBMS service, the eNB transmits the received counting result to the MCE. According to an aspect of the present invention, a method for counting a multimedia broadcast multicast service is provided, which includes: an eNB starting an MBMS service corresponding to an MBMS service identifier in each MBSFN area according to an update time of an MCCH corresponding to each MBSFN area. Counting; the eNB receives the counting result of the MBMS service sent by the terminal UE; and the eNB sends the received counting result to the MCE according to a pre-configured policy. The step of the foregoing eNB transmitting the received counting result to the MCE according to the pre-configured policy includes: after the eNB receives the counting result of all the MBMS services that need to be counted on all the MBSFN areas, the eNB performs all the foregoing MBSFN areas. All the count results of the above MBMS services that need to be counted are sent to the above MCE. The step of the foregoing eNB transmitting the received counting result to the MCE according to the pre-configured policy includes: when the eNB receives one or more counting results of the MBMS service that need to be counted on one or more of the foregoing MBSFN areas, The eNB sends the received counting result to the MCE. Before the eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area, the method further includes: the number of all the MBMS services that need to be counted on one of the MBSFN areas When the number of the maximum MBMS services initiated by the eNB is exceeded, the MCE configures a plurality of update times for the MCCH corresponding to the one MBSFN area. Before the eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area, the method further includes: the MCE configuring one or more updates for the MCCH corresponding to each of the MBSFN areas. time. MCE above said MBSFN area includes a plurality of corresponding MCCH updated by one of the following steps: a plurality of the above-mentioned MCE is updated MCCH corresponding to the MBSFN area above; or the above-mentioned MCE is arranged above MCCH corresponding to the MBSFN area and an update time Corresponding update time interval, wherein the update time interval indicates a time difference between the last update time of the MCCH and the current update time of the MCCH; or the MCE configures an update time for the MCCH corresponding to the MBSFN area and adopts The default update interval T, Τ = 0, 1, 2, wherein the default update interval indicates the time difference between the previous update time of the MCCH and the current update time of the MCCH. According to another aspect of the present invention, a counting system for a multimedia broadcast multicast service is provided, including: an MCE and an e B, where the MCE is configured to configure an MBMS service counting parameter, and send the foregoing MBMS to the eNB. The message of the service count parameter, where the above MBMS service count parameter: Or an MBMS service identifier to be counted in the plurality of MBSFN areas, an update time of the MCCH corresponding to each of the MBSFN areas; and the eNB is configured to start the MBMS in each of the MBSFN areas according to an update time of the MCCH corresponding to each of the MBSFN areas. The count of the MBMS service corresponding to the service identifier. The foregoing MCE includes: a configuration unit, configured to configure one or more update times for the MCCH corresponding to each of the foregoing MBSFN areas. The configuration unit includes at least one of the following: a first configuration module, configured to configure a plurality of update times for the MCCH corresponding to the MBSFN area, and a second configuration module configured to configure an update time and corresponding for the MCCH corresponding to the MBSFN area. And an update time interval, where the update time interval indicates a time difference between the last update time of the MCCH and the current update time of the MCCH; or the third configuration module is configured to configure an update for the MCCH corresponding to the MBSFN area. The time is the default update interval T, Τ = 0, 1, 2, wherein the default update interval indicates the time difference between the previous update time of the MCCH and the current update time of the MCCH. The foregoing eNB includes: a first initiating unit, configured to continuously start counting the MBMS service corresponding to the MBMS service identifier in the MBSFN area when the update time interval is configured as 0; and the second initiating unit is configured to be in the update time When the interval is configured as N, the count of MBMS services corresponding to the MBMS service identifier in the MBSFN area is started every N times of the MCCH modification period, where ^N≥Y. The eNB includes: a first receiving unit, configured to receive a counting result of the MBMS service sent by the terminal UE; and a first sending unit, configured to receive, at the first receiving unit, all the MBMSs that need to be counted on all the MBSFN areas. When the service is counted, all the count results of the above-mentioned MBMS services that need to be counted on the MBSFN area are sent to the MCE. The eNB includes: a second receiving unit, configured to receive a counting result of the MBMS service sent by the terminal UE; and a second sending unit, configured to receive, when the second receiving unit receives one or more of the one or more MBSFN areas When a plurality of count results of the MBMS service to be counted are counted, the received count result is transmitted to the MCE. The configuration unit includes: a fourth configuration module, configured to: when the number of the MBMS services that need to be counted on one of the MBSFN areas exceeds the maximum number of MBMS services that are initiated by the eNB, the MBSFN area The corresponding MCCH is configured with multiple update times. In the present invention, by configuring the update time of the MCCH corresponding to each MBSFN area, the problem that the counting of MBMS services in multiple MB SFN areas cannot be started in the prior art is solved, and the MBMS meter is implemented. The number of request messages is sent synchronously. In addition, the eNB reports the MBMS count result to the MCE according to the previous configuration, so that the reporting result of the multiple MBSFN areas is reported. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a schematic diagram of a repetition period and a modification period of an MCCH according to the related art; FIG. 2 is a schematic diagram of an architecture of an LTE MBMS according to the related art; FIG. 3 is a schematic flowchart of an MBMS counting process according to the related art; 4 is a preferred flowchart of a method for counting multimedia broadcast multicast services according to an embodiment of the present invention; FIG. 5 is a schematic diagram of an MCE configuring an eNB for an interval of 0 for each update of the MCCH according to an embodiment of the present invention; FIG. 6 is a schematic diagram of a counting start when an MCE configures an interval of each update of the MCCH for an eNB according to an embodiment of the present invention; FIG. 7 is a schematic diagram of an MBMS counting process according to an embodiment of the present invention; 8 is a preferred flowchart of a method for counting multimedia broadcast multicast services according to an embodiment of the present invention; and FIG. 9 is a schematic structural diagram of a counting system for a multimedia broadcast multicast service according to an embodiment of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings in conjunction with the embodiments. The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. Example 1 FIG. 4 is a preferred flowchart of a method for counting multimedia broadcast multicast services according to an embodiment of the present invention, including:

S402, the MCE configures an MBMS service count parameter, where the MBMS service count parameter: an MBMS service identifier that needs to be counted in one or more MBSFN areas, and an update time of the MCCH corresponding to each MBSFN area;

S404. The MCE sends, to the eNB, a message that carries the MBMS service count parameter.

S406. The eNB starts counting the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area. In the preferred embodiment, by configuring the update time of the MCCH corresponding to each MBSFN area, the problem that the counting of MBMS services in multiple MBSFN areas cannot be started in the prior art is solved, and the synchronization of the MBMS counting request message is realized. send. Preferably, the step of configuring the MBMS service count parameter by the MCE comprises: configuring, by the MCE, one or more update times for each MCCH corresponding to the MBSFN area. In the preferred embodiment, configuration flexibility is increased by configuring an explicit update time for each MBSFN. The MCE configures multiple update times for the MCCH corresponding to the MBSFN area by using one of the following steps:

1) The MCE configures multiple update times for the MCCH corresponding to the MBSFN area; in the preferred embodiment, the configuration flexibility is increased by configuring an explicit update time for each MBSFN. Or 2) the MCE is configured with an update time and a corresponding update time interval for the MCCH corresponding to the MBSFN area, where the update time interval indicates a last update time of the MCCH and a current update time of the MCCH. The time difference between. In the preferred embodiment, the operational flow is simplified and the flexibility of the configuration is increased by configuring an explicit update time interval. Or

3) The MCE configures an update time for the MCCH corresponding to the MBSFN area and adopts a default update time interval T, Τ=0, 1, 2, where the default update time interval indicates the last update time of the MCCH. The time difference from the current update time of the MCCH. In the preferred embodiment, the default update interval is used to improve transmission efficiency and reduce the amount of information transmitted. Preferably, in the above embodiments, the step of configuring the MBMS service count parameter by the MCE comprises: when the number of all the MBMS services that need to be counted on one of the MBSFN areas exceeds the single start of the eNB When the number of MBMS services is the maximum, the MCE configures a plurality of update times for the MCCH corresponding to the one MBSFN area. In the preferred embodiment, the configuration accuracy is ensured by configuring multiple update times for the MCCH corresponding to the one MBSFN area. Preferably, when the MCE is configured with an update time and a corresponding update time interval for the MCCH corresponding to the MBSFN area, the eNB starts the MBSFN area according to the update time of the MCCH corresponding to each MBSFN area. The step of counting the MBMS service corresponding to the MBMS service identifier includes: the update time interval is configured to be 0, and is used to indicate that the eNB continuously starts counting the MBMS service corresponding to the MBMS service identifier in the MBSFN area; or The update time interval is configured as N, where ^{N ≥ is} used to indicate that the eNB starts counting the MBMS service corresponding to the MBMS service identifier in the MBSFN area every N MCCH modification periods. In the preferred embodiment, configuration flexibility is increased by configuring an explicit update interval. Preferably, after the eNB starts counting the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area, the multimedia broadcast multicast according to the embodiment of the present invention is used. The counting method of the service further includes: the eNB receiving a counting result of the MBMS service sent by the terminal UE; when the eNB receives all the counting results of the MBMS service that need to be counted on all the MBSFN areas, The eNB sends the counting result of all the MBMS services that need to be counted on all the MBSFN areas to the MCE. In the preferred embodiment, the eNB reports all the MBMS count results to the MCEs at a time according to the previous configuration, so that the counting results of the multiple MBSFN areas are reported. Preferably, after the eNB starts counting the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area, the multimedia broadcast multicast according to the embodiment of the present invention is used. The counting method of the service further includes: the eNB receiving a counting result of the MBMS service sent by the terminal UE; and each time the eNB receives one or more MBMSs that need to be counted on one or more of the MBSFN areas When the service counts the result, the eNB sends the received count result to the MCE. In the preferred embodiment, the eNB reports the MBMS count result to the MCE in batches according to the pre-configuration, thereby increasing the flexibility of reporting the result of the counting. This embodiment is used for a synchronous transmission method in which an MCE sends a message 1 to an eNB on an M2 interface. The MCE sends a message 1 to the eNB on the M2 interface, and is used to indicate the related eNB to start the counting process under the control (ie, the MBMS service Uu counting process is performed on the Uu interface), and the M2 interface message can be represented as one of the following messages. Kind or more:

1) MBMS Service Counting message; 2) MBMS Service Counting Request message;

3) MBMS Counting message;

4) MBMS Counting Initiation message;

5) M2 Counting Request message, and so on. The message 1 carries one or more MBMS services (indicated by TMGI for each service) that need to be counted in a number of MBSFN areas. Since each MBSFN area uniquely corresponds to one MCCH, the MCE can configure the MBMS service that needs to be counted in different MBSFN areas for each eNB through a message 1. The message 1 needs to include at least two parts: 1. The MBMS service identifier corresponding to each MBSFN area needs to be counted (the service identifier can be represented by TMGI); 2. The update time of the MCCH corresponding to each MBSFN area. MCE sends a message to the eNB through the M2 interface. 1

It should be noted that, in the MBSFN overlapping area, the MCE can configure up to eight MBSFN areas for the eNB, that is, the MCE can configure up to eight MCCHs for the eNB through the M2 interface. However, if there is no MBMS service to be counted in some MBSFN areas, then these MBSFN areas are not included in Message 1. The update time of the MCCH, that is, the MCCH corresponding to these MBSFN areas does not need to be configured on the message 1 sent from the MCE to the e B. Further, it is considered that in the MBMS service Uu counting process, the counting request message 2 (eg, Counting Request message) can only configure a certain number of MBMS service identifiers (eg, up to 16 MBMS service identifiers) to be counted, so each eNB The secondary start MBMS service Uu counting process has the limit of the maximum MBMS service. In the message 1 of the M2 interface sent by the MCE to the eNB, the number of MBMS services to be counted on a certain MCCH (uniquely corresponding to one MBSFN area) is greater than the maximum service of the eNB in starting the MBMS service Uu counting process. If the number of the MBMS services is greater than 16 MBMS services, the eNB needs to start multiple MBMS service Uu counting processes on the Uu interface. Since the MBMS service Uu counting process is started on the Uu interface each time, the MCCH content needs to be modified to configure the MBMS service identifier to be counted on the MCCH (that is, the counting request message is configured on the MCCH), considering the requirement of synchronously updating the MCCH, You need to configure multiple update times for this MCCH. For example, when the counting request message in the MBMS service Uu counting process configures up to 16 counts of the MBMS service, and the MBCH service is configured for the MCCH on the M2 interface message, the MCCH needs to be updated 4 times. (Even: 64 MBMS services are configured in the MCCH in turn, and 16 MBMS services to be counted are configured on the MCCH.) Each time the eNB needs to update the MBMS service that needs to be counted on the MCCH, it needs to be performed in the MCCH modification period, so in the MCE. On the M2 interface message sent to the eNB, four MCCH update times need to be configured. There are several ways to configure it, such as:

1) For each MCCH, configure the time for each update; 2) Configure the time for the first update for this MCCH, and configure the interval for subsequent MCCH updates. As shown in the table below.

Table 2: M2 interface messages sent by the MCE to the eNB

Since the MCCH update can only be performed at the beginning of the MCCH modification period, the interval time is also 0 to multiple MCCH modification times. This interval can be configured by default, that is, the parameter is not configured, but a fixed value known in advance by the network side and the UE is used, indicating that the update time of consecutive MCCHs is sequentially separated by a fixed value, such as: 0, 1, 2 MCCH modification cycles, etc. The fixed value of this silent configuration (default configuration) applies to all MCCHs: that is, all MCCHs use the fixed value of the silent configuration as the update interval of the MCCH. As shown in FIG. 5, if the MME configuration is 0, it indicates that the eNB continuously starts multiple MBMS service Uu counting processes, that is, the eNB starts the next MBMS service Uu counting process immediately after the eNB starts the first MBMS service Uu counting process. Process. As shown in FIG. 6, if the MME interval is 1, it indicates that the eNB interval is one MCCH modification period to continuously start multiple MBMS service Uu counting processes, that is, after the eNB starts the first MBMS service Uu counting process, Interval 1 MCCH modification period, and then start the next MBMS service Uu counting process. Embodiment 2 This embodiment clarifies that on the M2 interface, the eNB reports to the MCE through the message 4 the result of counting the MBMS service that needs to be counted in the message 1. After receiving the message 1, the eNB sends a message 2 (also referred to as a Counting Request message) on one or more MCCHs, and the message 2 sent on each MCCH respectively carries the MBMS service of the corresponding MBSFN area in the message. That is to say, the message 2 carries the MBMS services that need to be counted, and these services are the only MBMS services in the message 1 that need to be counted corresponding to the MBSFN area. Message 2 carried on the MCCH

The UE in the cell reads the MCCH, and if it finds that there is interest in the MBMS service configured on the MCCH, it sends a count response message (referred to as message 3 in the present invention) to the eNB, and the message carries its interest or is in progress. Received MBMS service. The eNB receives the message 3 fed back by multiple UEs in the cell under its control, and can know that each MBMS service configured by the message 2 has multiple UEs interested in or receiving it. Subsequently, the eNB sends a report message (referred to as message 4 in the present invention) to the MCE, and reports to the MCE the number of UEs that are interested in or receiving each MBMS in the message 2. Since a message 1 may include a plurality of MBMS services of a plurality of MBSFN areas that need to be counted, the number of the foregoing services of each MBSFN area may be many. Therefore, after receiving a message 1, the eNB can start multiple messages 2, and each message 2 has a different MCCH update time. That is to say, the MCE sends a message 1 to e B, and the eNB cannot simultaneously obtain the counting result of the MBMS service configured in the message 1. Therefore, the message 4 sent by the eNB to the MCE may be one or more. Case 1: The message 1 sent by the MCE to the eNB includes the number of MBMS services that need to be counted in a number of MBSFN areas, and the number of MBMS services that need to be counted in each MBSFN area is less than or equal to the number of MBMS services that need to be counted in the message 2. Only one MCCH update time is configured for each of the above MBSFN areas. There are two methods for sending the message U: Message 4: Method 1: The eNB sends a message 4 to the MCE. That is to say, the counting result of all the MBMS services that need to be counted on all the MBSFN areas in the message 1 is fed back to the eNB through the message 3. Specifically, the message 1 includes a number of MBMS services that need to be counted in the MBSFN area, and correspondingly, the number of messages 2 sent by the eNB is equal to the number of the MBSFN areas, and each message 2 lasts for one MCCH modification period and each The modification period of the MCCH can be different (for example: it can be 5.12s or 10.24 seconds), correspondingly The time when the UE feeds back the message 3 to the eNB is also different. Therefore, the time at which the eNB obtains the statistical result of the MBMS service that needs to be counted in different MBSFN areas is also different. The eNB can wait until all the counting results of all the MBSFN areas are collected, and then send them to the MCE through a message 4. The eNB sends a message 4 to the MCE. Specifically, the time when the counting result of the MBMS service that needs to be counted in different MBSFN areas arrives at the eNB is different. After the eNB obtains the counting result of several MBSFN areas at a certain time, the eNB does not have to wait for the counting result of other MBSFN areas, and then The MCE sends a message 4, and the message 4 carries the counting result of these MBSFN areas. In particular, according to the current protocol, there are two MCCH modification periods: 5.12s and 10.24s, so the eNB can actually send 2 messages 4 to the MCE. For example, after 5.12 s, the eNB can obtain a number of MBSFN areas configured with a duration of 5.12 s. The eNB sends a message 4 carrying the count results of these MBSFN areas to the MCE, and then goes to the MCE after 10.24 s. Send another message 4. Case 2: Message 1 sent by the MCE to the eNB includes counts of several MBSFN areas that need to be counted.

The MBMS service and the MBMS service that needs to be counted in each MBSFN area are allowed to be larger than the number of MBMS services that need to be counted in the message 2. In this case, each MBSFN area can be configured with one or more MCCH update times. Bay 1J: There are two methods for sending message 4: Method 1: Method 1 of case 1, that is, the eNB always waits until all the MBSFN areas have reached the eNB, and then the eNB sends a message 4 to the MCE. Method 2: Method 2 similar to Case 1, BP: Once the count result of all MBMS services on a certain MBSFN area in message 1 is fed back to the eNB through message 3, the eNB sends a message 4, which is carried in message 4. The counting results of these MBSFN areas without waiting for the counting results of other MBSFN areas. Embodiment 3: Embodiment 3 is as shown in FIG. 7, and is specifically described as follows:

1) The MCE sends an M2 interface message to the eNB, and the third embodiment takes the MBMS Service Counting Request message (ie, the MBMS Service Counting Request message) on the M2 interface as an example; The message includes all the identifiers of the MBMS services that need to be counted, and the MBMS service identifiers belong to one or more MBSFN areas. The message further includes the update time of the MCCH corresponding to the MBSFN area, and the MCCH update time may be MCCH. The modification period is identified, such as: 0, 1, 2, .... 255, 0- indicates that the MCCH is updated in the subsequent MCCH modification period; 1- the next MCCH modification period update, and so on. Preferably, Embodiment 3 describes three MBMS services that need to be counted as an example. The TMGIs of the three MBMS services (MBMS service 1, MBMS service 2 MBMS service3) that need to be counted are {001, 002, 003 }, respectively; Servicel and MBMS service2 correspond to MBSFN area 1 (ie, corresponding MCCH1, MBSFN area identifier is 01), MBMS service3 corresponds to MBSFN area 2 (MCCH2, MBSFN area identifier is 02); The specific MBMS service count request message is: Table 4: MCE transmission M2 interface message to the eNB

 2) After receiving the above message, the eNB successfully receives the message in response to the MCE. Confirm the request message as shown in Figure 7.

3) For the MBMS service that needs to be counted on the different MCCHs configured on the MBMS service count request message, the eNB configures the MBMS service identifier of the MBSFN area corresponding to the MCCH in the MCCH update time set by each eNB. On the MCCH, the count request message is as shown in FIG. Preferably, specifically to Embodiment 1, the eNB will update the MCCH1 information (MCCH update time=0) at the specific update time of the MCCH1, and carry a count request message, where the message includes TMGI={001, 002}; The eNB will update the MCCH2 information (MCCH update time = 1) at the MCCH2 specific update time, and carry the count request message, which contains TMGI={003}.

4) The UE reads the content on the MCCH, and obtains the MBMS service identifier that needs to be counted on each MCCH, and then the UE sends a Counting Response message to the e B, where the response message includes the UE in the MBMS service identifier. The MBMS service identifier that is of interest or receiving, such as the count response message in FIG.

5) The eNB sends an MBMS service counting report to the MCE, where the report message includes the counting result of the MBMS service. Embodiment 4: On the Uu interface, the number of MBMS services that can be counted in the MBS service Uu counting process is up to 16, that is, the counting request message can be configured with up to 16 MBMS services to be counted at a time. . When the MCE sends an M2 interface message to the eNB, the embodiment 4 uses an MBMS Service Counting message (MBMS Service Counting message) carried on the M2 interface as an example, and an MBSFN area (in this embodiment, the MBSFN area 3 is taken as an example, corresponding to In MCCH3), there are more than 16 MBMS services to be counted, and Embodiment 4 takes 64 as an example. In this message, four eNBs need to be configured to start the MCCH update time of the MBU service Uu counting process. Specifically, there are two ways to configure: Method 1: Configure the MCCH update time of the MBMS service Uu counting process by the eNB one by one; Specifically, to the embodiment 2, the MBSFN area corresponding to the MBMS service count message Four MCCH update times will be configured (for example: MCCH update time=l, 3, 5, 7), so that

1) According to the received MCCH update time, the eNB configures the first 16 MBMS services on the MCCH3 at the specified time (such as the first MCCH modification period after receiving the message from the MCE, corresponding to the MCCH update time=l). 2) The eNB after the first MBMS service Uu counting process is completed, at the specified time (if received from

The third MCCH modification period after the message of the MCE, corresponding to the MCCH update time=3), starts an MBMS service Uu counting process, that is, the 17th-32 MBMS service is configured on the MCCH3. 3) The following and so on, BP: After the eNB receives the fifth message from the MCE (corresponding to MCCH update time=5), and after the seventh MCCH modification period (corresponding to MCCH update time=7), the eNB starts multiple times in sequence. MBMS business Uu counting process. Method 2: Configure the first eNB to start the MCCH update time of the MBMS service Uu counting process (for example: MCCH update time=l), and configure the time interval between each eNB to start the counting process (for example: MCCH update interval time: 1 ). such:

1) According to the received MCCH update time, the eNB configures the first 16 MBMS services on the MCCH3 at the specified time (such as the first MCCH modification period after receiving the message from the MCE, corresponding to the MCCH update time=l). ;

2) After the first MBMS service Uu counting process is completed, the eNB is separated by the configured time interval (for example, the interval is 1 MCCH modification period, that is, the third MCCH modification period after receiving the message from the MCE, corresponding to MCCH update interval time=l), and then start an MBMS service Uu counting process, that is, configure the 17-32 MBMS service on the MCCH. 3) The following analogy, that is, after the eNB receives the 5th, 7th MCCH modification period of the message from the MCE, the eNB sequentially starts a plurality of MBMS service Uu counting processes. Example 5

In the message 1 sent by the MCE to the eNB, the MBMS services that need to be counted in the four MBSFN areas (abbreviated as: area 1, area 2, area 3, area 4) are configured, and the MBMS service that needs to be counted in each area is configured. The number is: Area 1 has 60 services, Area 2 has 40 services, Area 3 has 30 services, and Area 4 has 15 services. The update time of all MBSFN areas is the same, such as starting from the next MCCH modification time (MCCH update time=l), and all are separated by one MCCH modification period. It is also assumed that the MCCH update time of MBSFN areas 1 and 2 is 5.12 s, and the MCCH update time of MBSFN areas 3 and 4 is 10.24 s. In message 2: MCCH1 includes 4 MCCH update times, and the MBMS services to be counted on MCCH1 are: 16 services in the first TMGI list-1, and 16 in the second TMGI list-2. Business, 16 services in the third TMGI list-3, and 12 services in the fourth TMGI list-4. The MCCH2 includes three MCCH update times. The MBMS services that need to be counted on each MCCH2 are: 16 services in the first TMGI list-1, 16 services in the second TMGI list-2, and third. 8 businesses in the TMGI list-3.

The MCCH3 includes two MCCH update times. The MBMS services that need to be counted on each MCCH3 are: 16 services in the first TMGI list-1, and 14 services in the second TMGI list-2.

MCCH4 includes 1 MCCH update time and 15 services in the TMGI list. For the eNB to report the counting result, the following two methods are available:

1) After obtaining the counting result of all MBSFN areas, the eNB sends a message 4 to the MCE. That is to say, one message 1 corresponds to one message 4.

2) When using Method 2 of the above embodiment, Table 5: Report contents included in each message 1

 That is, when the message 4 is transmitted for the first time, the message 4 includes the count result of the MBMS service to be counted on the TMGI list-1 of the MBSFN1 and the TMGIlist-1 of the MBSFN2. When the message 4 is sent a second time, the message 4 includes the TMGI list-2 MBSFN2 of MBSFN1.

TMGIlist-2 MBSFN3 TMGIlist-1 and MBSFN4 TMGIlist-Ι The count result of the MBMS service that needs to be counted. At the time of the third transmission of the message 4, the message 4 includes the count result of the MBMS service to be counted on the TMGI list-3 of MBSFN1 and the TMGIlist-3 of MBSFN2. At the fourth time of sending the message 4, the message 4 includes the TMGI list-4 MBSFN3 of MBSFN1.

The count result of the MBMS service that needs to be counted on the TMGIlist-2. Example 5 FIG. 8 is another preferred flowchart of a method for counting multimedia broadcast multicast services according to an embodiment of the present invention, which includes the following steps:

S802, the eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area; S804, the eNB receives the counting result of the MBMS service sent by the terminal UE;

S806. The eNB sends the received counting result to the MCE according to a pre-configured policy. In the preferred embodiment, the eNB reports all the MBMS count results to the MCE according to the pre-configured policy, so that the reporting result of the multiple MBSFN areas is reported. Preferably, the step of the eNB sending the received counting result to the MCE according to the pre-configured policy includes one of the following two situations:

1) after the eNB receives the counting result of all the MBMS services that need to be counted on all the MBSFN areas, the eNB will count all the MBMS services that need to be counted on all the MBSFN areas. The MCE is sent to the MCE; in the preferred embodiment, the eNB reports all the MBMS count results to the MCE in a one-time manner according to the previous configuration, so that the counting result of the multiple MBSFN areas is reported; or

2) When the eNB receives one or more counting results of the MBMS service that need to be counted on one or more of the MBSFN areas, the eNB sends the received counting result to the MCE. In the preferred embodiment, the eNB reports the MBMS count result to the MCE in batches according to the pre-configuration, thereby increasing the flexibility of reporting the result of the counting. Preferably, before the eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area, when all the MBMS services on the MBSFN area need to be counted When the number exceeds the maximum number of MBMS services that are initiated by the eNB, the MCE configures multiple update times for the MCCH corresponding to the one MBSFN area. In the preferred embodiment, by configuring multiple update times for the MCCH corresponding to the one MBSFN area, the accuracy of the configuration is ensured. Preferably, before the eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area, the MCE configures one or more MCCHs corresponding to each of the MBSFN areas. Update time. MCE MBSFN area corresponding to the plurality of updated MCCH by one of the steps of:

1) The MCE configures multiple update times for the MCCH corresponding to the MBSFN area; in the preferred embodiment, the configuration flexibility is increased by configuring an explicit update time for each MBSFN. Or

2) The MCE configures an update time and a corresponding update time interval for the MCCH corresponding to the MBSFN area, where the update time interval indicates between the last update time of the MCCH and the current update time of the MCCH. Time difference. In the preferred embodiment, the operational flow is simplified and the flexibility of the configuration is increased by configuring an explicit update interval. 3) The MCE configures an update time for the MCCH corresponding to the MBSFN area and adopts a default update time interval T, Τ=0, 1, 2, where the default update time interval indicates the last update time of the MCCH. The time difference from the current update time of the MCCH. Preferably, when the MCE is configured with an update time and a corresponding update time interval for the MCCH corresponding to the MBSFN area, the eNB starts the MBSFN area according to the update time of the MCCH corresponding to each MBSFN area. The step of counting the MBMS service corresponding to the MBMS service identifier includes: the update time interval is configured to be 0, and is used to indicate that the eNB continuously starts counting the MBMS service corresponding to the MBMS service identifier in the MBSFN area; or The update time interval is configured as N, where ^{N ≥ is} used to indicate that the eNB starts counting the MBMS service corresponding to the MBMS service identifier in the MBSFN area every N MCCH modification periods. Embodiment 7 FIG. 9 is a schematic structural diagram of a counting system of a multimedia broadcast multicast service according to an embodiment of the present invention, which includes: an MCE 902 and an eNB 904, where the MCE 902 is configured to configure an MBMS service counting parameter. And sending, to the eNB 904, a message that carries the MBMS service count parameter, where the MBMS service count parameter: an MBMS service identifier that needs to be counted in one or more MBSFN areas, where each MBSFN area corresponds to The eNB 904, in communication with the MCE 902, is configured to start counting the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area. In the preferred embodiment, by configuring the update time of the MCCH corresponding to each MBSFN area, the problem that the counting of MBMS services in multiple MBSFN areas cannot be started in the prior art is solved, and the synchronization of the MBMS counting request message is realized. send. Preferably, the MCE 902 includes: a configuration unit, configured to configure one or more update times for the MCCH corresponding to each of the MBSFN areas. Preferably, the configuration unit is in communication with e B 904. In the preferred embodiment, configuration flexibility is increased by configuring explicit update times. Preferably, the configuration unit includes at least one of the following: a first configuration module, configured to configure a plurality of update times for the MCCH corresponding to the MBSFN area, and in the preferred embodiment, by adding an explicit update time, adding The second configuration module is configured to configure an update time and a corresponding update time interval for the MCCH corresponding to the MBSFN area, where the update time interval indicates the last update time of the MCCH. a time difference between the current update time and the current update time of the MCCH; the third configuration module is configured to configure an update time for the MCCH corresponding to the MBSFN area and adopt a default update time interval T, Τ=0, 1, 2, The default update time interval represents a time difference between a last update time of the MCCH and a current update time of the MCCH. In the preferred embodiment, configuration flexibility is increased by configuring an explicit update interval. Preferably, the eNB 904 includes: a first initiating unit, configured to continuously start counting the MBMS service corresponding to the MBMS service identifier in each MBSFN area when the update time interval is configured as 0; The initiating unit is configured to, when the update time interval is configured to be N, start a count of MBMS services corresponding to the MBMS service identifier in an MBSFN area every N MCCH modification periods, where N≥. Preferably, the first starting unit and the second starting unit are in communication with the configuration unit. In the preferred embodiment, configuration flexibility is increased by configuring an explicit update interval. Preferably, the eNB 904 includes: a first receiving unit, configured to receive a counting result of the MBMS service sent by the terminal UE; and a first sending unit, configured to receive all the MBSFN areas at the first receiving unit All the count results of the MBMS service that need to be counted are sent to the MCEs of all the MBMS services that need to be counted on all the MBSFN areas. Preferably, the first receiving unit is in communication with the terminal UE, and the first transmitting unit is in communication with the MCE 902. In the preferred embodiment, the eNB reports all the MBMS count results to the MCE at a time according to the previous configuration, so that the counting result of the multiple MBSFN areas is reported. Preferably, the eNB 904 includes: a second receiving unit, configured to receive a counting result of the MBMS service sent by the terminal UE; and a second sending unit, configured to receive one or more whenever the second receiving unit receives When one or more count results of the MBMS service that need to be counted on the MBSFN area, the received count result is sent to the MCE. Preferably, the second receiving unit is in communication with the terminal UE, and the second transmitting unit is in communication with the MCE 902. In the preferred embodiment, the eNB reports the MBMS count result to the MCE in batches according to the pre-configuration, thereby increasing the flexibility of reporting the result of the counting. Preferably, the configuration unit includes: a fourth configuration module, configured to: the number of all the MBMS services that need to be counted on one of the MBSFN areas exceeds the maximum MBMS service that is initiated by the e B In the case of a number, an update time is configured for the MCCH corresponding to the one MBSFN area. In the preferred embodiment, the configuration accuracy is ensured by configuring multiple update times for the MCCH corresponding to the one MBSFN area. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device so that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim A method for counting multimedia broadcast multicast services, including:  The MCE configures an MBMS service count parameter, where the MBMS service count parameter: an MBMS service identifier that needs to be counted in one or more MBSFN areas, and an update time of the MCCH corresponding to each MBSFN area;  The MCE sends a message carrying the MBMS service count parameter to the eNB; the eNB starts the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area. count. 2. The method according to claim 1, wherein the step of configuring the MBMS service count parameter by the MCE comprises:  The MCE configures one or more update times for the MCCH corresponding to each of the MBSFN areas. 3. The method according to claim 2, wherein the MCE MBSFN area corresponding to a plurality of updated MCCH by one of the steps:  The MCE configures a plurality of update times for the MCCH corresponding to the MBSFN area; or the MCE configures an update time and a corresponding update time interval for the MCCH corresponding to the MBSFN area, where the update time interval indicates the The time difference between the last update time of the MCCH and the current update time of the MCCH; or  The MCE configures an update time for the MCCH corresponding to the MBSFN area and uses a default update time interval T, Τ=0, 1, 2, where the default update time interval indicates the last update time and location of the MCCH. The time difference between the current update times of the MCCH. The method according to any one of claims 1 to 3, wherein the step of configuring the MBMS service count parameter by the MCE comprises: When the number of the MBMS services that need to be counted on one of the MBSFN areas exceeds the maximum number of MBMS services that are initiated by the eNB, the MCE is configured for the MCCH corresponding to the one MBSFN area. Update time. The method according to claim 3, wherein, when the MCE is configured with an update time and a corresponding update time interval for the MCCH corresponding to the MBSFN area, the e B is corresponding to each MBSFN area. The step of starting the counting of the MBMS service corresponding to the MBMS service identifier in each MBSFN area by the update time of the MCCH includes: The update time interval is configured to be 0, and is used to indicate that the e B continuously starts counting the MBMS service corresponding to the MBMS service identifier in the MBSFN area; or the update time interval is configured as N, N≥\ The counting of the MBMS service corresponding to the MBMS service identifier in the MBSFN area is started by the _e B every N MCCH modification period. The method according to claim 1, wherein after the eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area, Also includes:  Receiving, by the eNB, a counting result of the MBMS service sent by the terminal UE; when the eNB receives the counting result of all the MBMS services that need to be counted on all the MBSFN areas, the eNB performs all the MBSFNs. The counting result of all the MBMS services that need to be counted on the area is sent to the MCE. The method according to claim 1, wherein, after the eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area, Also includes:  Receiving, by the eNB, a counting result of the MBMS service sent by the terminal UE; each time the eNB receives one or more counting results of the MBMS service that need to be counted on one or more of the MBSFN areas, The eNB sends the received counting result to the MCE. 8. A method for counting multimedia broadcast multicast services, including:  The eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area; The eNB receives the counting result of the MBMS service sent by the terminal UE; the eNB sends the received counting result to the MCE according to a pre-configured policy. 9. The method according to claim 8, wherein the step of the eNB transmitting the received counting result to the MCE according to the pre-configured policy comprises:  After the eNB receives the counting result of all the MBMS services that need to be counted on all the MBSFN areas, the eNB sends the counting result of all the MBMS services that need to be counted on all the MBSFN areas to the eNB. The MCE. The method according to claim 8, wherein the step of the eNB transmitting the received counting result to the MCE according to the pre-configured policy comprises:  Each time the eNB receives one or more counting results of the MBMS service that need to be counted on one or more of the MBSFN areas, the eNB sends the received counting result to the MCE. The method according to claim 8, wherein before the eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area, the method further includes:  When the number of the MBMS services that need to be counted on one of the MBSFN areas exceeds the maximum number of MBMS services that are initiated by the eNB, the MCE is configured for the MCCH corresponding to the one MBSFN area. Update time. The method according to claim 8, wherein before the eNB starts the counting of the MBMS service corresponding to the MBMS service identifier in each MBSFN area according to the update time of the MCCH corresponding to each MBSFN area, the method further includes:  The MCE configures one or more update times for the MCCH corresponding to each of the MBSFN areas. 13. The method of claim 11 or claim 12, wherein the MCE is MCCH of the MBSFN area corresponding to said plurality of update time by one of the following:  The MCE configures a plurality of update times for the MCCH corresponding to the MBSFN area; or the MCE configures an update time and a corresponding update time interval for the MCCH corresponding to the MBSFN area, where the update time interval indicates the The time difference between the last update time of the MCCH and the current update time of the MCCH; or The MCE configures an update time for the MCCH corresponding to the MBSFN area and uses a default update time interval T, Τ=0, 1, 2, where the default update time interval indicates the last update time and location of the MCCH. The time difference between the current update times of the MCCH. A counting system for a multimedia broadcast multicast service, comprising: an MCE and an e B, wherein  The MCE is configured to configure an MBMS service count parameter, and send a message carrying the MBMS service count parameter to the eNB, where the MBMS service count parameter: an MBMS service identifier that needs to be counted in one or more MBSFN areas The update time of the MCCH corresponding to each MBSFN area;  The eNB is configured to start, according to the update time of the MCCH corresponding to each MBSFN area, a count of MBMS services corresponding to the MBMS service identifier in each MBSFN area. 15. The system of claim 14, wherein the MCE comprises:  The configuration unit is configured to configure one or more update times for the MCCH corresponding to each of the MBSFN areas. 16. The system according to claim 15, wherein the configuration unit comprises at least one of the following:  a first configuration module, configured to configure multiple update times for the MCCH corresponding to the MBSFN area;  a second configuration module, configured to configure an update time and a corresponding update time interval for the MCCH corresponding to the MBSFN area, where the update time interval indicates a last update time of the MCCH and a current update time of the MCCH Time difference between; or  The third configuration module is configured to configure an update time for the MCCH corresponding to the MBSFN area and adopt a default update time interval T, Τ=0, 1, 2, where the default update time interval indicates the previous one of the MCCH The time difference between the update time and the current update time of the MCCH. The system according to claim 16, wherein the eNB comprises:  a first initiating unit, configured to continuously start counting the MBMS service corresponding to the MBMS service identifier in the MBSFN area when the update time interval is configured as 0;  The second initiating unit is configured to, when the update time interval is configured to be N, initiate a count of MBMS services corresponding to the MBMS service identifier in the MBSFN area every N MCCH modification periods, where N≥. The system according to claim 14, wherein the eNB comprises: a first receiving unit, configured to receive a counting result of the MBMS service sent by the terminal UE; a first sending unit, configured to: when the first receiving unit receives all the count results of the MBMS service that need to be counted on all the MBSFN areas, all the counts on the MBSFN area that need to be counted The counting result of the MBMS service is sent to the MCE. The system according to claim 14, wherein the eNB comprises:  a second receiving unit, configured to receive a counting result of the MBMS service sent by the terminal UE, where the second sending unit is configured to receive one or more of the one or more MBSFN areas each time the second receiving unit receives When the count result of the MBMS service needs to be counted, the received count result is sent to the MCE. The system according to claim 15, wherein the configuration unit comprises:  a fourth configuration module, configured to: when the number of the MBMS services that need to be counted on one of the MBSFN areas exceeds the maximum number of MBMS services that are initiated by the eNB, the corresponding one of the MBSFN areas The MCCH is configured with multiple update times.