RU2575258C2 - Multimedia broadcast multicast service counting method and system - Google Patents

Abstract

FIELD: radio engineering, communication.

SUBSTANCE: invention relates to wireless communication systems, which provide multimedia services to mobile users, and provides timely and accurate collection of statistics of receiving the current multimedia broadcast multicast service (MBMS) by user equipment (UE). The invention discloses a MBMS counting method, which includes: after receiving MBMS counting initiation information sent by a network side, a base station sending MBMS counting indication information to UE via an air interface; the base station reporting the counting information about the MBMS to the network side according to a received MBMS counting result reported by the UE. The present invention also provides a multimedia broadcast multicast service counting system for implementing the method.

EFFECT: invention can timely and accurately count the MBMS, which can enable the network side to timely and accurately learn the application situation of the current MBMS and make it convenient for the network side to make relevant deployment regarding the MBMS.

18 cl, 1 tbl, 9 dwg

Description

FIELD OF THE INVENTION

The present invention relates to a technology for counting a Multimedia Broadcast Multicast Service (MBMS) and, in particular, to a method and system for counting an MBMS service.

BACKGROUND OF THE INVENTION

With the rapid development of the Internet and the popularization of multifunctional mobile phones with large screens, a large number of multimedia services of a mobile data transmission system and various broadband multimedia services, such as video conferencing, television, video on demand, video advertising, interactive education, interactive games, etc. All these multimedia services of the mobile data transmission system and various broadband multimedia services not only fulfill the increasing requirements for the services of mobile users, but also bring new points of increase in services for mobile operators. These multimedia services of a mobile data transmission system and various broadband multimedia services require that many users be able to receive the same data at the same time, and compared with conventional data services, they have features such as a large amount of data, long duration, delay sensitivity and so on.

To efficiently use the resources of the mobile network, the Third Generation Partnership Project (3GPP) offers a multicast / multimedia broadcast service (MBMS), and this MBMS service is a technology for transferring data from a data source to multiple destinations which provides the sharing of network resources (consisting of a core network and an access network) and improves the utilization of network resources (especially air interface). The MBMS service defined by the 3GPP organization can not only achieve multicast and broadcast transmission of a clear-text and low-speed message class, but also can achieve multicast and broadcast transmission of high-speed multimedia services and provide various surround video, audio and multimedia services, which undoubtedly corresponds to the development trend of the future mobile data transmission system and provides the prospect of a better service for the development of 3rd generation mobile communication systems (3rd Genera tion, 3G).

Currently, the MBMS service has been introduced in the Long Term Evolution (LTE) system of release 9 (standard version) (Release 9, R9), and it is optimized in the LTE system of release 10 (R10). The MBMS service is implemented by joint transmission in a control signaling system (also called MBMS control signaling) and user data (also called MBMS service). In this case, the control signaling will notify the receiving terminal (such as the terminal, User Equipment (UE)) of the respective control parameters to instruct the UE to receive the MBMS service in which the UE is interested in the corresponding position, i.e. the corresponding user data . Such MBMS control signaling (control information including configuration information regarding the MBMS service and the like) is transmitted in the LTE system via a multicast control channel (MCCH), and the MBMS service is transmitted through a multicast traffic channel, MTCH).

In particular, the MBMS control signaling (i.e., MCCH information) transmitted on the MCCH logical channel mainly comprises:

MBMS Single Frequency Network (MBSFN) multicast resource corresponding to MCCH information, all ongoing MBMS services (or called started MBMS services, or called started session MBMS services) in the MBSFN and configuration and properties of ongoing services MBMS and what is carried on the MTCH logical channel is MBMS service data, and usually the MBMS service corresponds to the MTCH channel, for example, the MBMS service 1 corresponds to MTCH1, the MBMS service 2 corresponds to MTCH2, that is, the UE reading the MBMS service expresses the same value as the UE equipment reading the MTCH channel. On the network, the MBMS service is uniquely determined by the Temporary Mobile Group Identity (TMGI), and each MBMS service has its own corresponding TMGI, which is convenient for identifying the network side and the UE equipment.

In this case, the MCCH information corresponding to the MBSFN will be transmitted according to some rule (repetition period and modification period), in particular, as shown in FIG. FIG. 1 is a schematic diagram of sending MCCH information about the MBSFN in the relevant technical field, and, as shown in FIG. 1, MCCH information will be transmitted one or more times repeatedly within the modification period (in FIG. 1, it is transmitted 3 times repeatedly) ; the interval between retransmissions of MCCH information is called the MCCH repetition period; typically, the first transmission of MCCH information is referred to as the first transmission in the MCCH modification period, the transmission in each repetition period is referred to as retransmission of the MCCH information, and the repeatedly transmitted MCCH information is identical to the content of the MCCH information transmitted for the first time; the MCCH modification period indicates that the content of the transmitted MCCH information may be different in different MCCH modification periods; as shown in FIG. 1, the content of the (n + 1) th modification period of the MCCH is different from the content of the nth period (in FIG. 1, slanted hatch blocks and unfilled blocks are used to represent various content of MCCH information); and it should be noted that within the MCCH modification period, the content of the MCCH information should not be changed and can only be retransmitted according to the repetition period. The content of the MCCH information is allowed to change only at the boundary of the start of the MCCH modification period, that is, the change of MCCH information can only occur during the first transmission of MCCH information during the MCCH modification period, which is also referred to as the MCCH change time. This regulation ensures compatibility of the MCCH information transmission in the MBSFN (multiple evolved Node Bs (base stations) (evolved Node B, eNB)).

The configuration parameters of the repetition period and the modification period of the MCCH are configured by the network side, and the network side sends the configuration parameters for the UE by means of a system information block type 13 (System Information Block 13, SIB13) in the Broadcast Control Channel (BCCH); the UE can learn the configuration parameters of the repetition period and the MCCH modification period by reading the SIB13 in the BCCH, and the UE can read the MCCH information in the corresponding position.

With respect to the relevant technical field, control signaling and user data in the MBSFN will be transmitted synchronously using MBSFN technology in a cell unit or base station eNB (the goal is to enable the UE to receive the corresponding combining gain upon reception). MBSFN technology requires each cell in the MBSFN zone to send the same data content on the same time-frequency resources, which requires the same resource allocation and scheduling in each cell. Currently, an element called a Multi-cell / multicast Coordination Entity (MCE) transmission coordination module (object) is used to perform the same distribution and scheduling of radio resources, which, in particular, can be referred to international 3GPP 36.300 v910 standards.

Figure 2 is a diagram of the architecture of MBMS in a long-term evolution (LTE) system in the relevant technical field. As shown in FIG. 2, in a modern LTE system, the network elements related to the MBMS service are an eNB base station, an MCE module, an MBMS gateway (MBMS Gateway, MBMS GW, a Broadcast Multicast Service Center, BM- SC)) and a Mobility Management Entity (MME), the BM-SC being used as a network element to start a transmission session, end a transmission session, update a transmission session, or provide MBMS services with data; the MBMS Gateway (MBMS Gateway, MBMS GW) sends the MBMS service data to the corresponding eNB base station via the M1 interface; the GMS MBMS gateway sends control plane information such as a Session Start Request message, a Session Stop Request message, a Session Updated Request message generated by a BM-SC element for an object MME the MME is fully used as the forwarding element of the network and sends the control plane information sent by the MBMS GW to the MCE module via the M3 interface; and the MCE sends the corresponding control plane information to the corresponding base station eNB via the M2 interface, and through their processing, the base station eNB receives MBMS service data and the corresponding control plane information. In general, the control plane information sent by the MME to the eNB base station via the M2 interface contains the following: a start of a transmission session request message, a transmission session end request message, a transmission session update request message, an MBMS resource allocation information message, a restart message, a request message M2 settings and corresponding messages sent to the MCE via the M2 interface, such as a response message to a request to start a transmission session, a response message to a request to complete a transmission session, with summarizing the response to the request to update the communication session, the response message to the request for MBMS resource allocation information, the reset confirmation message, and the response message to the configuration request of the M2 interface. The aforementioned signaling or process between the MCE and the eNB base station, which is carried on the M2 interface, is called the Application Protocol (AP) of the M2 interface, i.e., M2AP.

From the above content, it may be known that the MBMS service will be transmitted throughout the MBSFN area. To further optimize the transmission of MBMS services, the industry has introduced an uplink feedback mechanism for UE equipment, and in particular, an uplink feedback mechanism is applied mainly to the network side to collect data on the number of users (or the number of pieces of equipment of the UE) who are interested in each MBMS service / accept it; by collecting data on the number of users, the network side optimizes the transmission of the MBMS service, for example, deactivating (or referred to as non-transmitting) MBMS service with fewer users who are interested in / accepting this service, and activating (or referred to as transmitted) service MBMS with a large number of users who are interested in / accept this service. To find the number of pieces of equipment of the UE (if any) that are interested in some MBMS service / receive it, the network side can allow the equipment of the UE that is interested in some MBMS / service to receive it, provide feedback on the uplink, sending a counting command, so that the UE reports the current reception status of the MBMS. The network side can apply information acquired through feedback on the uplink (that is, how many units of the UE are interested in / receive one MBMS service) for the operation of activating or deactivating the MBMS service, and, in other words, the network side may decide to transmit (activate) or not transmit (deactivate) the MBMS service via the air interface according to information acquired through uplink feedback.

However, after the UE equipment has reported the MBMS service in which it is interested or accepts to the eNB base station via the air interface (from the UE equipment to the eNB base station), in the relevant technical field there is no practically possible implementation of how the network performs the control activation / deactivation of the MBMS service according to the received report information.

SUMMARY OF THE INVENTION

In view of this, the main objective of the present invention is to propose a method and system for calculating a multicast / broadcast multimedia information transmission service that can timely and accurately collect statistics on the reception situation of the current MBMS service by the UE equipment.

In order to achieve the above goal, the technical solution in this invention is implemented as follows.

A method for counting multicast / broadcast multimedia information services includes:

after receiving the information for initiating counting of the multicast / broadcast multimedia information service (MBMS) service sent by the network side, the base station sends the MBMS count indication indication information to the user equipment (UE) via the air interface and

presenting the base station to the network side of the report with MBMS service count information according to the received MBMS count result reported by the UE.

Preferably, the base station receives MBMS count triggering information from the network side, including:

receiving, by the base station, MBMS count initiating information sent by the network side via the M2 interface, and sending a confirmation message or failure to receive the request message to the network side.

Preferably, the base station receives MBMS count triggering information from the network side, including:

receiving, by the base station, MBMS counting initiation information sent by the network side via the M2 interface, wherein the MBMS counting initiation information comprises a list of MBMS services and at least one of the following: start time, duration, interval and number of repetitions.

Preferably, the base station receives MBMS count triggering information from the network side, including:

receiving, by the base station, MBMS counting initiation information sent by the network side, wherein the MBMS counting initiation information comprises an MBMS list and at least one of the following: start time, duration, and report time.

Preferably, the MBMS count initiating information comprises a counting procedure with respect to at least one MBMS service, wherein each counting procedure includes at least one counting report procedure.

Preferably, the MBMS service list contains at least one MBMS service.

Preferably, the MBMS count initiation information comprises at least one counting procedure.

Preferably, the MBMS count initiation information comprises more than two MBMS count procedures, and when the network side decides to complete the incomplete MBMS count procedure among more than two MBMS count procedures, the network side sends an end message to the base station regarding the incomplete MBMS count procedure.

Preferably, the MBMS count initiating information comprises more than two MBMS counting procedures, and when the network side decides to update the incomplete MBMS counting procedure among more than two MBMS counting procedures, the network side sends an update message regarding the incomplete MBMS counting procedure to the base station.

Preferably, one MBMS counting procedure includes: a counting procedure with respect to the air interface and reporting to the base station on the result of this counting.

Preferably, counting procedures in which the number of MBMS services is identical and the content of MBMS services are identical are the same counting procedure, and different identifiers are provided for the same counting procedure.

The system for counting multicast / broadcast multimedia information services comprises: a receiving unit, a first transmitting unit and a reporting unit, with a receiving unit, a first transmitting unit and a reporting unit located in the base station,

a receiving unit is configured to receive multicast / multimedia broadcast service (MBMS) counting initiation information sent by the network side, and receive an MBMS count result reported by a user equipment (UE);

the first transmitting unit is configured to transmit MBMS count indication information to the UE through the air interface and

the reporting unit is configured to report MBMS count information to the network side according to the received MBMS count result reported by the UE.

Preferably, the base station receives MBMS counting initiation information sent by the network side via the M2 interface, wherein the MBMS counting initiation information contains an MBMS list and at least one of the following: start time, duration, interval and number of repetitions.

Preferably, the base station receives MBMS counting initiation information sent by the network side via the M2 interface, wherein the MBMS counting initiation information comprises an MBMS list and at least one of the following: start time, duration, and report time.

Preferably, the MBMS count initiating information comprises a counting procedure with respect to at least one MBMS service, wherein each counting procedure includes at least one counting report procedure.

Preferably, the MBMS list contains at least one MBMS service, and the MBMS count initiation information comprises at least one counting procedure.

Preferably, the system further comprises: a determining unit and a second transmitting unit located on a network side; moreover

the determination unit is configured so that when the MBMS count initiation information comprises more than two MBMS counting procedures, decide to complete the incomplete MBMS counting procedure among more than two MBMS counting procedures and start the second transmitting block; and

the second transmitting unit is configured to send an end message regarding the incomplete MBMS counting procedure to the base station.

Preferably, the determination unit is further configured so that when the MBMS count initiation information comprises more than two MBMS counting procedures, decide to update the incomplete MBMS counting procedure among more than two MBMS counting procedures and start a second transmitting unit for transmitting an update message regarding the incomplete procedure to the base station counting MBMS.

In the present invention, when the network side decides that it is necessary to count the number of units of the current receiving equipment UE for the MBMS service, the network side will send the MBMS count initiation information to the MCE module, and the MCE module sends the MBMS count initiation information to the base station via the M2 interface. After receiving the MBMS count initiation information sent by the network side, the base station sends the MBMS count initiation information to the UE via the air interface; the UE receiving the MBMS counting indication information will report the counting result according to the indication information, for example, when counting the number of UEs receiving some MBMS service, if the UE is currently receiving this MBMS service, then the UE reports its own information; and the base station reports the MBMS count information to the network side according to the received MBMS count result reported by the UE. The present invention can timely and accurately calculate MBMS accordingly, which can allow the network side to timely and accurately study the situation of applying the current MBMS service and make it convenient for the network side to perform relevant deployment with respect to MBMS.

Brief Description of the Drawings

Figure 1 - schematic diagram of the transmission of MCCH information of the MBSFN zone in the relevant field of technology.

Figure 2 is a diagram of the MBMS architecture of an LTE system in the relevant field of technology.

Figure 3 is a block diagram of the initiation of counting MBMS on the M2 interface in this invention.

4 is a flowchart of reporting a count result over a Uu interface in the present invention.

5 is a flowchart of reporting a counting result over an M2 interface in the present invention.

6 is a block diagram of updating the count result over the M2 interface in this invention.

7 is a block diagram of the stop counting on the M2 interface in this invention.

Fig. 8 is a schematic diagram of the transmission of MBMS count initiation information in the present invention.

Fig.9 is a structural diagram of the composition of the components of the counting system services multicast / broadcast multimedia information in this invention.

DETAILED DESCRIPTION OF EMBODIMENTS

The basic concept of the present invention is as follows: when the network side decides that it is necessary to count the number of UE units currently receiving for the MBMS service, the network side will send the MBMS count initiation information to the MCE module, and the MCE module will send the MBMS count initiation information to the base station via the M2 interface, and after receiving the MBMS count initiation information sent by the network side, the base station sends MBMS count indication information to the UE via the air interface; The UE receiving the MBMS tally indication information will report the counting result according to the tally information, for example, when counting the number of receiving units of the UE of a certain MBMS service, if the UE is currently receiving this MBMS service, the UE reports its own information; and the base station reports the counting information regarding the MBMS to the network side according to the received MBMS counting result reported by the UE.

To make the purpose, technical solution and advantages of the present invention more clear, the invention will be further described in detail in the form of implementation with reference to the drawings.

First, the network side (which in this invention mainly means MCE and eNB) starts the procedure for initiating the counting on the M2 interface, i.e. the procedure for initiating the MBMS counting on the M2 (M2 MBMS Counting Initiation Procedure - the procedure for initiating the counting on the M2 interface, which can also referred to as the start counting procedure MBMS), for configuring one or more counting procedures.

To save signaling overhead in the M2 interface, the counting initialization procedure may include several identical or different counting procedures, each counting procedure may include one or more of the following information elements: a list of services (i.e., a list of counting MBMS services, which is mainly MBMS identifying information), start time, duration, interval and number of repetitions. When the number of repetitions of the counting procedure is more than 1, this is equivalent to the fact that this procedure for initiating MBMS counting by M2 requires performing this counting procedure many times, and is also equivalent to the fact that it will be configured with many identical counting procedures.

In each counting procedure, 3 steps must be included, that is, in step 1, the base station eNB must configure the count indication information about the aforementioned MBMS service for the cell under the control of the base station eNB; in step 2, the UE should also select the MBMS service in which it is interested or which it accepts from the above list of services configured in this counting procedure and report this MBMS service to the eNB; and in step 3, the base station eNB then counts the number of units of the UE that are interested in or accepting each service from the list of services, and reports this number to the MCE. That is, one counting procedure contains one step 1, one step 2 and one step 3.

Steps 1 and 2 correspond to the UMS MBMS counting procedure (Uu MBMS Counting procedure - MBMS counting procedure over the air interface). Step 3 corresponds to the procedure for reporting the result of counting the MBMS no M2 (M2 MBMS Counting Report procedure - the procedure for reporting the result of counting the MBMS M2 interface). That is, each counting procedure includes one MBMS counting procedure by Uu and one reporting procedure of the MBMS counting result by M2.

In this case, since each counting procedure can take a relatively long time, or the procedure for initiating counting via the M2 interface can include numerous identical counting procedures (such as the number of repetitions equal to 5, etc.), the MCE module is probably will update or cancel the counting procedure during counting. If the network side has decided whether to activate / deactivate one or more MBMS services according to the current counting procedure, the MCE module will update or cancel the subsequent counting procedure. The invention will be described in detail by the following procedure for updating MBMS counting on M2 (M2 MBMS Counting Update procedure - procedure for finishing counting MBMS on M2 interface) and procedure for finishing MBMS counting on M2 (M2 MBMS Counting Stop procedure - procedure for ending counting on M2 interface). Of course, the MCE module can also restart the M2 MBMS Counting Initiation procedure to update or cancel the count of several MBMS services.

Exercise form I

FIG. 3 is a flowchart for triggering an MBMS count by an M2 interface in the present invention, and as shown in FIG. 3, an initiation procedure of an MBMS count by M2 (an MBMS count triggering procedure by an M2 interface) includes, in particular, the following steps.

Step 301: the MCE sends a message including MBMS count triggering information to the base station eNB.

In this step, MBMS counting initiation information can be provided in a newly installed message, that is, to implement the technical solution in this invention, a corresponding new message will be provided to initiate an MBMS counting procedure between the MCE and the base station, for example, an MBMS Counting Initiation request message Request), designed to notify the base station to initiate the MBMS counting procedure. Of course, the aforementioned MBMS count initiation information can also be provided in an existing message, such as an MBMS Scheduling Information message. That is, provided that the MBMS counting initiation information is carried in the corresponding message and sent to the base station, this invention does not limit the format and type of the message. A new message and an existing message must be generated in the M2 interface. The content of the MBMS count initiation information in this invention is shown in Table 1:

Table 1 Counting procedure list 1 ... maxCounting Number (maximum number of counts) > start time INTEGER (WHOLE NUMBER) (0 ... 255) > duration time > counting number > interval time > Service list for counting 1 ... maxnoofServiceforcounting (maximum number of services to calculate)

In this case, the list of counting procedures (number of counting procedures): MBMS counting initiation information can contain numerous different counting procedures (1, ..., maxCounting Number). In general, one counting procedure can be configured all the time, and at this moment, the MBMS counting initiation does not contain the information block of the Counting procedure list.

The start time may also be referred to as the start time or MCCH update time, which indicates when the base station eNB configures counting indication information for several services in one or more counting procedures for MCCH information. Any of the following methods may be used.

Method 1: no configuration will be performed and the default configuration will be used, that is, the MBMS counting initiation information does not include the “start time” information block, that is, after receiving the counting request from the MCE module (such as the MBMS counting initiation request message) basic the eNB always configures the count indication in the MCCH during the MCCH update of the next MCCH modification period (or the default period).

Method 2: the MCE module configures the absolute time for each counting procedure, that is, the base station eNB configures the indication of the counting of some counting procedure in the MCCH in some subsequent modification period (Modification Period, MP) of the MCCH channel, and the start time of the various counting procedures can be identical or different, but the start time of all services in one counting procedure is identical.

Method 3: The MCE module configures the absolute time for all counting procedures. That is, only one start time is configured in the MBMS counting initiation information and is used for all counting procedures in the MBMS counting initiation information, or, in other words, the same start time is configured for all counting procedures in the MBMS counting initiation information.

The duration indicates for the MCE module the length of time to request the eNB to count several services in one counting procedure, i.e. the period from the start of counting to the end of counting of some service (services) by the eNB base station, which is indicated in the air interface (Uu interface, the interface between the eNB and by the UE) due to the length of time from the configuration of the indication of the counting of some service (services) in the MCCH information of the base station eNB to the removal of the indication of the counting of some service (services) in the MCCH information of the base station eNB. One way or another, the duration is equal to the duration of step 1 in one previously mentioned counting procedure (that is, the time for configuring the list of services in the MCCH), but does not include the duration of steps 2 and 3 in the previously mentioned counting procedure.

The duration corresponding to the different counting procedures included in the MBMS counting initiation information (for example, counting procedures for different MBMSs services) may be identical or different, but the duration of all services within the same counting procedure must be identical. Any of the following methods may be used for presentation.

Method 1: no configuration will be performed, and at that moment the MBMS counting initiation information does not include a “duration” information block, for example, the duration corresponding to all counting procedures can always last for several MPCH MCCH periods (for example, it can be set as N periods of MPs MCCH).

Method 2: the MCE module configures the duration for each counting procedure, for example, the duration of one counting procedure is configured as lasting several periods of MCCH MPs.

Method 3: the MCE module configures only one duration, which is used for all counting procedures in the MBMS counting initiation information for all counting procedures, or all services of all counting procedures in the MBMS counting initiation information are configured with the same duration number.

The number of repetitions is also referred to as the number of counts, which indicates the number of identical counting procedures in a single procedure for initiating counting MBMS by M2.

The interval indicates the time interval between the end of step 1 of the previous counting procedure and the beginning of step 1 of the next counting procedure, when the MCE module configures many identical counting procedures for the eNB (i.e., the number of repetitions is multiple). Any of the following methods can be used to represent an interval.

Method 1: the interval is configured for each counting procedure sequentially.

Method 2: one interval is configured for all counting procedures, that is, all counting procedures in the MBMS counting initiation information are configured with the same interval in the same way.

Method 3: no configuration will be performed and the default configuration will be used, and at this point the MBMS counting initiation information does not include this parameter. For example, the interval is always 0, that is, each counting procedure is configured and continues continuously, or each counting procedure is located with a fixed time interval.

It should be noted that when the counting procedure has been configured for several times and the interval is 0, the next counting procedure should not be performed until the last counting procedure is completed, instead, step 1 of the next counting procedure can be started after it is finished step 1 of the last counting procedure, that is, when the next counting procedure begins to be executed, step 2 or 3 of the last counting procedure should not be completed.

The maxCounting Number block is the maximum number of counting procedures, and when only one counting procedure can be configured in one counting initiation procedure, this information block is not required. The maxnoofServiceforcounting block is the maximum of MBMS services in each counting procedure, that is, the list of services configured in the MCCH by the eNB base station.

Step 302: The base station eNB sends a message including MBMS count initiating response / failure information to the MCE.

If the base station eNB can implement a request message including MBMS count initiation information (such as an MBMS count initiation request message), then the base station eNB sends an acknowledgment message including a response to the MBMS count initiation request to the MCE; and if the base station eNB cannot make the request message, then the eNB sends a failure message including failure information of the MBMS count initiation to the MCE module. In addition, the MBMS count initiation response / failure information can not only be configured into a new response message (such as the MBMS count initiation response / failure message shown in FIG. 3), but can also be configured into an existing response message.

If the MCE could not receive the eNB confirmation message, a request message to initiate the counting must be sent to the eNB again until the eNB responds to the confirmation message.

Form II

FIG. 4 is a flowchart of a Uu interface count result message in the present invention, and as shown in FIG. 4, a UMS MBMS counting procedure (UMS MBMS Counting procedure — an air interface MBMS counting procedure) includes, in particular, the following Steps.

Step 401: the base station eNB sends a count indication message via the air interface (corresponds to step 1 of the counting procedure).

After receiving the count initiation message from the MCE module and transmitting back the confirmation to the MCE module (that is, after the MBMS no M2 count initiation procedure is completed), the base station eNB sends count indication information via the air interface (as shown in FIG. 4, this count indication information is transferred in the count request message) so as to require the UE equipment to transmit back to the eNB the MBMS service in which the UE is interested or receives.

The Uu MBMS counting procedure refers to steps 1 and 2 in the above counting procedure, but does not include step 3.

This count indication information is carried on a point-to-many-point transmission control channel, and point-to-many-point transmission control channel may be an MCCH or BCCH, and each MBMS service is represented using a TMGI. With respect to each received counting procedure, the eNB configures the count indication information about one or more MBMS services in the MCCH at its desired start time, duration, interval and number of repetitions (i.e., the number of counts), and the aforementioned MBMS service is sent to the eNB using the MCE module by request counting MBMS.

For example, according to the start time of the counting procedure configured by the MCE, the base station eNB configures a list of services (i.e., count indication information) in the MCCH during the MCCH change and lasts for a “duration” time.

After the duration of one counting procedure is reached, the base station eNB deletes the counting indication of all services of this counting procedure during the MCCH update, and the UE will not read the counting indication of these services when reading the MCCH and will no longer respond to the counting.

Step 402: the UE reads the MCCH to get a list of TMGIs that need counting, and sends back to the eNB the MBMS service that the UE is interested in or accepts (corresponding to step 2 in the counting procedure).

In particular, during one counting procedure, the “duration” can always appear in the list of services configured in the MCCH, and after reading the MCCH and receiving the list of services, the UE can transfer back to the eNB the MBMS service in which the UE is interested or is receiving.

Implementation Form III

FIG. 5 is a flowchart for reporting an M2 interface counting result report in the present invention, and as shown in FIG. 5, an MBMS counting report procedure for M2 (M2 MBMS Counting Report procedure — an M2 interface counting report report procedure, corresponds to step 3 in the counting procedure) includes, in particular, the following steps.

Step 501: The base station eNB sends a message to the MCE including MBMS count information (MBMS count report message).

After completing the MBMS no Uu counting procedure, the eNB base station reports the result of counting the service on the MCE. When the counting result is received correctly, the MCE sends a confirmation message to the eNB; otherwise, the MCE sends a failure message.

The MBMS counting report information includes the counting results of all services in one counting procedure, and the information can be transferred not only in a new message, but also in an existing message. Counting results can be obtained in one of the following ways.

Method 1: the number of UE units that are interested in or accept the service (for example, the number of service users 1, the number of service users 2, ..., and the number of service users N).

Method 2: the maximum value of the number of units of equipment of the UE is limited based on the aforementioned method 1, that is, when the number of users is greater than the maximum value, reporting will be performed using the maximum value (the advantage of this method is that it is convenient to come to an agreement on service information report, and when the number of UE units reaches its maximum value, report that more users will no longer matter).

Method 3: the number of UE units that are interested in or accepting the service is essentially classified, for example, there are few users, the number of users is normal, there are many users, and although the calculation result is relatively crude, it is simple and there is less overhead when presenting the report .

Step 502: the MCE module sends an eNB message including MBMS Counting Report Response / Failure Information (MBMS Counting Report Response / Failure message - MBMS Counting Report Response / Failure message).

The response / failure information of the MBMS counting report can be carried not only in a new message, but can also be carried in an existing message. In particular, if the MCE module correctly receives a message including MBMS counting report information, then the MCE transmits a confirmation message containing information on the response to the MBMS counting report request back to the eNB, otherwise MCE sends back a failure message containing a report failure about counting MBMS.

Form IV

6 is a flowchart of updating the counting result over the M2 interface in the present invention, and as shown in FIG. 6, the MBMS counting update procedure for M2 (M2 MBMS Counting Update procedure) may update some procedure ( s) counting and may also add or remove a list of services, start time, duration, number of repetitions, interval, etc. in several counting procedures; and, in addition, the addition or deletion of several counting procedures can be realized by restarting the procedure for initiating MBMS counting in M2 or the procedure for ending MBMS counting in M2.

In particular, it includes the following steps.

Step 601: the MCE sends a relevant message including MBMS count update information to the eNB base station.

This count update information can be carried not only in a new message, but can also be carried in an existing message (such as an MBMS count update message). In this MCE count update information, you may need to update some count procedure (s), i.e. add or remove several count procedures or change configuration information about several count procedures, such as service list, start time, duration, number of repetitions, interval and etc., in some calculation procedure (s).

For example, in relation to some calculation procedure, a service can be added or reduced in it, or time parameters, etc. in it are subject to change.

Step 602: the base station eNB sends a relevant message including the response information to the MBMS count update request to the MCE.

If the base station eNB receives the count update request correctly and executes it, the eNB sends a count update confirmation to the MCE; and if the eNB cannot accept the count update request correctly, the eNB sends the MBMS count update failure to the MCE. Similarly, this count update confirmation / failure information can be configured not only into a new response message as an information block, but can also be configured into an existing response message. In particular, a request for updating count information is configured in a new message, such as an MBMS count update message or an MBMS count update response / confirmation message, and an MBMS count update failure message will be sent to the MCE module.

This procedure is very similar to the procedure for initiating the calculation of MBMS by M2 in the form of implementation I. That is, the MCE module can reconfigure the procedure of counting by restarting the procedure for initiating the calculation of MBMS by M2.

Form exercise V

In a counting initiation procedure, the MCE can also cancel (i.e. stop) several counting procedures. As soon as some counting procedure (s) is deleted, all services in it or these counting procedures will no longer need to be counted. FIG. 7 is a flowchart of a counting end in an M2 interface in the present invention, and as shown in FIG. 7, an MB2 counting end procedure for M2 (end counting procedure for an M2 interface) includes, in particular, the following steps.

Step 701: The MCE sends a message containing the MBMS end count information for M2 to the eNB.

This information to complete one or more counting procedures can be carried not only in a new message, but can also be carried in an existing message. The MCE module can send an end counting command to the eNB during one counting procedure or during the same counting procedure, that is, at any time during one or more identical counting procedures.

Step 702: the base station eNB sends a message to the MCE module including information (acknowledgment) / failure to respond to the MBMS count completion request for M2.

Information (confirmations) / failure of a response to a request for an MBMS calculation report for M2 can be carried not only in a new message, but can also be carried in an existing message. If the base station eNB can receive it correctly, then the eNB responds with a confirmation message to the MCE, otherwise the eNB responds with a failure message. At this point, the eNB deletes the count indication of the mentioned service in the MCCH at the beginning of the MCCH MP period and no longer counts the count result of the mentioned service and does not send the count result to the MCE module.

Implementation Form VI

Hereinafter, the essence of the technical solution in this invention will be further described by taking the completed counting procedure as an example, and this counting procedure includes that the MCE module initiates the counting, then the base station eNB configures the list of counting services in the MCCH, and finally, the counting procedure ends.

In particular, the procedure includes the following steps.

Step a, the MCE sends an MBMS count initiation message to the eNB.

When the network side must calculate how many UE units are interested in or accepts one or more services (count how many UE units accept those services that have not started yet, and count how many UE units are interested in those services that have not started yet), the module The MCE sends a count initiation message to the eNB. A message may include one or more counting procedures, and each counting procedure includes: list of services, start time, duration, interval, number of repetitions, etc.

Step b, the base station eNB sends a response message to the MBMS count initiation request to the MCE.

If the base station eNB can receive the start message correctly, then the eNB sends back a response message, otherwise the eNB sends back a failure message.

When the eNB base station sends a failure message back to the MCE, the MCE must again send the MBMS count initiating message to the eNB until the eNB can receive it correctly and send back the success message.

Step c, the eNB base station begins to configure the list of services that need to be counted in the MCCH for all cells under the control of the eNB.

At a specific start time, the base station eNB configures a list of services that need to be counted in the MCCH, and lasts for a duration time, and each counting procedure has an identifier (such as a serial number). The UE may send back the service in which it is interested or received by the UE during the current counting procedure according to this identifier.

Step d, the base station eNB sends an MBMS count report message to the MCE.

After the counting procedure is completed, the eNB reports the counting result of this counting procedure to the MCE.

Step e, the MCE sends an MBMS count report confirmation message to the eNB.

If the MCE module can receive the counting report message correctly, then it sends back the response message, otherwise the MCE module sends back the failure message.

When the eNB base station sends a failure message back to the MCE, the eNB must again send the counting report to the MCE until the MCE can receive it correctly and send back the success message.

When the MCE module configures the counting procedure many times through the MBMS counting initiation procedure, and for all services of this counting procedure, if the MCE decides that subsequent counting procedures will no longer be necessary (that is, it no longer requires all the services to be counted during this procedure counting, of course, the list of services during this counting procedure can just have one service) according to this counting report (there may also be other factors), then the MCE module sends an MBMS counting end message to the eNB, Rich message end MBMS counting is used to remove one or more of the counting procedures. The base station eNB sends an MBMS end-of-count confirmation message to the MCE module and no longer configures this counting procedure in the MCCH, that is, the MCCH no longer contains an indication of counting all services during this counting procedure.

Alternatively, for several services during this counting procedure, if the MCE module decides that subsequent services will no longer be necessary according to this counting report (there may also be other factors), then the MCE module sends an MBMS counting update message to the eNB, the message can delete several services during one counting procedure (which is equivalent to adjusting the list of services of this counting procedure), and can also reconfigure other configuration parameters during one procedure dscheta (such as start time, duration, interval, number of repetitions, etc.).

The base station eNB sends an MBMS count update update confirmation message to the MCE module, and the eNB responds with an acknowledgment message to the MCE module and no longer configures several services during this counting procedure in the MCCH, that is, the MCCH will no longer contain a counting indication of part of the services during this procedure counting.

Form exercise VII

FIG. 8 is a schematic diagram of sending MBMS count triggering information in the present invention, and as shown in FIG. 8, MBMS count triggering information in this example contains only one counting procedure, and furthermore, each counting procedure includes several reporting procedures counting. This counting procedure includes at least an indication of counting several services, each counting report procedure also includes counting reports of several services, and these services are all services or part of the services during the counting procedure.

The MBMS service counting initiation procedure in the M2 interface (the MBMS counting initiation procedure for M2) includes, in particular, the following steps.

Step A, the MCE sends an MBMS count start request message to the eNB.

The MCE module sends an MBMS count start request message to all eNBs in its MBSFN, and this message includes: one or more MBMS services that need to be counted, and, with respect to the above services, may or may not contain one or more of The following data: start time, duration, time of the counting report.

When this message includes a message time, the next step, such that “the eNB sends an MBMS counting report request message to the MCE module,” cannot be executed, that is, the MCE module no longer has to configure the counting report result for the eNB by means of the request message.

The method for configuring message time can be {Service 1, Report Time 1; Service 2, Report Time 2, ..., Service n, Report time n,} ({service 1, report time 1; service 2, report time 2, ..., service n, report time n,}), and one report time can be configured the same for these services, i.e. {Report Time; Service 1, Service 2, ..., Service n} ({report time; service 1, service 2, ..., service n}).

A set of report times can be configured for each service, for example {Service 1, Report Time 1, Report Time 2, ..., Report Time k} ({service 1, report time 1, report time 2, ..., report time k}), which indicates that the base station eNB reports the counting result to the MCE at these times of the report.

The base station eNB sends a response message to an MBMS count report request to the MCE according to the report time of each service or the same report time of all services.

Step B, the base station eNB sends a response message to the MBMS count start request to the MCE module.

The base station eNB receives the MBMS count start request message and can configure the count indication and relevant information about the above service in the air interface, then the eNB sends back an MBMS count start request response message to the MCE.

Step C, the base station eNB configures the count indication of the above services in the MCCH.

Step C may also be performed prior to step B or be performed simultaneously with it.

In this step, the base station eNB configures the above service list on the MCCH during the MCCH update, according to the MCCH modification period indicated by the start counting time configured in step 1. If the start time of the counting is not configured in step A, then the above list of services can be configured in MCCH during MCCH update of the next MCCH modification period.

In this step, the base station eNB configures the list of the above services in the MCCH all the time according to the counting duration configured in step A. If the counting duration is not configured in step A, the list of the above services will be configured in the MCCH all the time.

Step D, the UE reads the MCCH message and reports to the eNB about the MBMS service that the UE is interested in or accepts.

This step is performed after step C. The UE in the cell under the control of the eNB reads the MCCH message and reports the MBMS service in which the UE is interested or receives, on the eNB according to the list of service counting needs configured in the MCCH message.

Each counting service in an MCCH message may also include a counting identifier (such as a sequence number or sequential number (SN)) to distinguish between different steps D.

For example, some UE reads the MCCH, the list of services on this MCCH for counting is presented as: {Service 1, SN1}, {Service 2, SN2}, ..., {Service n, SNn} ({service 1, SN1}, {service 2 , SN2}, ..., {service n, SNn}), and with respect to the counting SN of each service, the UE reports the counting result only once, which can prevent the base station eNB from recounting the counting result of one UE and can also reduce overhead information uplink signaling caused by multiple UE reports.

The MBMS service counting report procedure in the M2 interface (MBMS counting report procedure for M2) includes, in particular, the following steps.

Step A1, the base station eNB sends an MBMS count report request message to the MCE module.

If the MBMS count start request message on the MCE by the eNB includes “report time”, then this step is no longer needed.

The MCE module sends an MBMS count report request message to all eNBs in its MBSFN, the message may or may not contain one or more MBMS services that should report the count. All or part of these MBMS services that report counting may be services configured during the MBMS counting initiation procedure, and may also include (or not include) the time when the report on the counting result (report time) is submitted (i.e. after what period of modification of the MCCH to report the counting result); and may also include (or not include) an updated counting identifier (SN) of those services that reported the result.

If this message does not contain a list of MBMS services for reporting the counting result, then this message indicates that the MCE requests the eNB to report all services configured during the "MBMS Counting Initiation Procedure".

If this message does not contain "report time", that is, the default report time is used, then this message indicates that after receiving this request message, the base station eNB counts the result of the service counting in this message during the MCCH update in the next MCCH modification period and reports it to the MCE module.

If this message contains an “updated counting identifier” of each service, then this message indicates that the UE does not need to report the counting result to the eNB again. That is, the UE reports the counting result to the eNB according to the counting identifier of a certain service in the MCCH, and the counting identifier of the service is used to report the counting result of this service to the eNB once.

Step B1, the base station eNB sends an MBMS count report request message to the MCE.

The eNB base station calculates the service counting result in the “MBMS counting report request message” according to the “report time” defined in the “MBMS counting report request message” or according to the message time configured in the “MBMS counting start message message sent by the eNB to MCE ", that is, the counting result is reported to the MCE module at a specific time of the report.

The counting identifiers (SN) of those services that reported the results cannot be updated, and in addition, the counting identifiers (SN) of those services that reported the results can be updated simultaneously as new counting identifiers (such as SN + 1). The time when updating the MCCH multiple service count identifiers should be at the time the MCCH is updated. That is, during the report defined in step 1, the base station eNB, on the one hand, reports the counting results of these services and simultaneously updates the counting identifiers of these services during the MCCH update so that after reading the MCCH, the UE can receive new counting identifiers of these services and again inform about the service in which the UE is interested and / or accepted, that is, this is a new count for the UE.

For example, the list of MCCH counting services read by the UE is {Service 1, SN1}, {Service 2, SN2}, {Service 3, SN3}, ..., {Service n, SNn} ({service 1, SN1}, {service 2, SN2}, {service 3, SN3}, ..., {service n, SNn}), and the UE reports the service in which it is interested and / or which the UE receives, once; and after the base station eNB once reported the count result to the MCE module, the eNB updates the MCCH content during the MCCH modification period, the content including the updated count identifier: {Service 1, SN1 + 1}, {Service 2, SN2 + 1}, {Service 3, SN3 + 1}, ..., {Service n, SNn + 1} ({service 1, SN1 + 1}, {service 2, SN2 + 1}, {service 3, SN3 + 1}, ..., { service n, SNn + 1}), and at this point, after reading the MCCH, the UE finds that the counting identifiers of these services have been updated, then the UE must report the service in which it is interested and / or which it receives, again.

After the MCE may decide to activate / deactivate the counting of one or more services according to the above counting report procedure, the MCE module may delete the counting requests of these services to the eNB.

The procedure for completing the MBMS service count in the M2 interface (the procedure for completing the MBMS count for M2) includes, in particular, the following steps.

Step A2, the MCE module sends an MBMS end count message to the eNB.

This message contains several services in the list of services originally configured on the MCCH for counting, to indicate that these services no longer require the UE to report the counting result.

Step B2, the base station eNB sends an MBMS count end confirmation message to the MCE.

After receiving the request message in step A2, the base station eNB sends an acknowledgment message to the MCE.

Step C3, the base station eNB removes the count indication and the relevant information about several services in the MCCH.

When the "MBMS service count initiation procedure in the M2 interface" includes the duration of several services, steps A2 and B2 are not required for these services, that is, after reaching the duration of this / these services, step C3 will be executed directly.

According to several service lists configured with an “MBMS end count message”, or when the “MBMS service count initiation procedure in the M2 interface” includes a duration of several services and a duration time is reached, the base station eNB changes the content of the MCCH during the MCCH update, i.e., the eNB deletes the count indication and relevant information about these services.

This step can be performed simultaneously with step B2 or before step B2, but it should be after step A2, that is, this step can be performed as soon as the base station eNB receives the end count message.

For example, after the "MCE sends a message requesting the start of counting MBMS on eNB", the counting services configured by the eNB in the MCCH are: {service 1, relevant information 1}, {service 2, relevant information 2}, {service 3, relevant information 3}, ..., {service n, relevant information n} ({service 1, relevant information 1}, {service 2, relevant information 2}, {service 3, relevant information 3}, ..., {service n, relevant information n}), and this relevant information may be: start time, duration, report time, etc.

When the "MCE sends an MBMS count end message to the eNB" and service 2 is included in it (which indicates that service 2 should no longer be reported by the UE, that is, the base station eNB should no longer count the count result of service 2), services for counting, Configurable eNBs in the MCCH are: {service 1, relevant information 1}, {service 3, relevant information 3}, ..., {service n, relevant information n} ({service 1, relevant information 1}, {service 3, relevant information 3}, ..., {service n, relevant information n}); the counting result that the UE reports after reading the MCCH no longer contains the service 2.

The MBMS service count update procedure in the M2 interface (the MBMS count update procedure for M2) is similar to the MBMS service count initiation procedure in the M2 interface, that is, the count indication and relevant information about each service can be configured by the MBMS service count start procedure in the M2 interface (relevant information includes: start time, duration, report time, etc.).

Fig. 9 is a structural diagram of the components of a multicast / multimedia broadcast service counting system in the present invention, and as shown in Fig. 9, the multicast / multimedia broadcast service counting system in the present invention comprises a receiving unit 90, a first transmitting unit 91 and a reporting unit 92, the receiving unit 90, the first transmitting unit 91, and the reporting unit 92 are located in the base station.

The receiving unit 90 is configured to receive MBMS count indication information sent by the network side, and receive the MBMS count result reported by the UE.

The transmitting unit 91 is configured to transmit MBMS count indication information to the UE through the air interface.

The reporting unit 92 is configured to report MBMS service count information to the network side according to the received MBMS count result reported by the UE.

The network side sends MBMS counting initiation information to the base station via the M2 interface, wherein the MBMS counting initiation information contains an MBMS list and at least one of the following: start time, duration, interval and number of repetitions.

The network side sends MBMS counting initiation information to the base station via the M2 interface, wherein the MBMS counting initiation information contains an MBMS list and at least one of the following: start time, duration, and report time.

The MBMS count initiating information comprises a counting procedure with respect to the at least one MBMS service, each counting procedure comprising at least one counting reporting procedure.

The MBMS list contains at least the MBMS service, and the MBMS count indication information comprises at least one counting procedure.

Based on the system shown in FIG. 9, the multicast / multimedia broadcast service counting system of the present invention further comprises a determination unit (not shown) and a second transmitting unit (not shown) located on the network side, wherein

the determining unit is configured so that when the MBMS count initiation information comprises more than two MBMS counting processes, decide to complete the incomplete MBMS counting process among more than two MBMS counting processes and start the second transmitting block; and

the second transmitting unit is configured to send an end message regarding the incomplete MBMS counting process to the base station.

The aforementioned determination unit is further configured so that when the MBMS count initiation information comprises more than two MBMS counting processes, it is decided to update the incomplete MBMS counting process among more than two MBMS counting processes and start a second transmitting unit for transmitting an update message regarding the incomplete process to the base station counting MBMS.

Those skilled in the art will understand that the multicast / multimedia broadcast service counting system shown in Fig. 9 in this invention is for implementing the aforementioned multicast / multimedia broadcast service counting service and the implementation functions of the various processing units can be understood from the relevant description of the above exercise III. The functions of the various processing units in the figure can be implemented by programs running in the processor, and can also be implemented in the form of a specialized logic circuit.

The above are merely preferred embodiments of the present invention, not intended to limit the scope of protection of the present invention.

Claims (18)

1. A method of counting multicast / broadcast multimedia information services, characterized in that it includes:
after receiving the information for initiating counting of the multicast / broadcast multimedia information service (MBMS) service sent by the network side, the base station sends the MBMS count indication indication information to the user equipment (UE) via the air interface and
presenting the base station to the network side of the report with MBMS service count information according to the received MBMS count result reported by the UE. 2. The method according to claim 1, characterized in that the base station receives MBMS count initiation information from the network side, including:
receiving, by the base station, MBMS count initiating information sent by the network side via the M2 interface, and sending a confirmation message or failure to receive the request message to the network side. 3. The method according to claim 1 or 2, characterized in that the base station receives MBMS counting initiation information from the network side, and includes receiving, by the base station, MBMS counting initiation information sent by the network side via the M2 interface, wherein the MBMS counting initiation information contains a list of MBMS services and at least one of the following: start time, duration, interval, and number of repetitions. 4. The method according to claim 1 or 2, characterized in that the base station receives MBMS counting initiation information from the network side, the base station receives MBMS counting initiation information sent by the network side, wherein the MBMS counting initiation information contains an MBMS list and at least one from the following: start time, duration and time of the report. 5. The method according to claim 4, characterized in that the MBMS counting initiation information comprises a counting procedure for at least one MBMS service, wherein each counting procedure includes at least one counting report procedure. 6. The method according to claim 3, characterized in that the list of MBMS services contains at least one MBMS service. 7. The method according to claim 1 or 2, characterized in that the information for initiating counting MBMS contains at least one counting procedure. 8. The method according to claim 7, characterized in that the MBMS count initiation information comprises more than two MBMS count procedures, and when the network side decides to complete the incomplete MBMS count procedure among more than two MBMS count procedures, the network side sends an end message to the base station with respect to incomplete MBMS counting procedure. 9. The method according to claim 7, characterized in that the MBMS count initiation information comprises more than two MBMS count procedures, and when the network side decides to update the incomplete MBMS count procedure among more than two MBMS count procedures, the network side sends an update message to the base station with respect to incomplete MBMS counting procedure. 10. The method according to claim 7, characterized in that one MBMS counting procedure includes a counting procedure with respect to the air interface and a report to the base station about the result of this counting. 11. The method according to claim 7, characterized in that the counting procedures in which the number of MBMS services is identical and the content of the MBMS services are identical are the same counting procedure and different identifiers are provided for the same counting procedure. 12. A system for counting multicast / broadcast multimedia information services, characterized in that it comprises: a receiving unit, a first transmitting unit and a reporting unit, wherein the receiving unit, the first transmitting unit and the reporting unit are located in the base station,
a receiving unit is configured to receive multicast / multimedia broadcast service (MBMS) counting initiation information sent by the network side, and receive an MBMS count result reported by a user equipment (UE);
the first transmitting unit is configured to transmit MBMS count indication information to the UE through the air interface and
the reporting unit is configured to report MBMS count information to the network side according to the received MBMS count result reported by the UE. 13. The system of claim 12, wherein the base station receives MBMS count initiation information sent by the network side via the M2 interface, wherein the MBMS count initiation information comprises an MBMS list and at least one of the following: start time, duration, interval, and number of repetitions. 14. The system of claim 12, wherein the base station receives MBMS count triggering information sent by the network side via the M2 interface, wherein the MBMS count triggering information contains an MBMS list and at least one of the following: start time, duration and time of the report . 15. The system of claim 14, wherein the MBMS counting initiation information comprises a counting procedure for at least one MBMS service, each counting procedure including at least one counting report procedure. 16. The system according to any one of paragraphs.13-15, characterized in that the MBMS list contains at least one MBMS service and the MBMS count initiation information contains at least one counting procedure. 17. The system according to clause 16, wherein the system further comprises: a determination unit and a second transmitting unit located on the network side; moreover
the determining unit is configured so that when the MBMS count initiation information comprises more than two MBMS counting procedures, decide to complete the incomplete MBMS counting procedure among more than two MBMS counting procedures and start the second transmitting block; and
the second transmitting unit is configured to send an end message regarding the incomplete MBMS counting procedure to the base station. 18. The system of claim 17, wherein the determining unit is further configured so that when the MBMS count initiation information comprises more than two MBMS counting procedures, decide to update the incomplete MBMS counting procedure among more than two MBMS counting procedures and start a second transmitting block for transmitting an update message regarding the incomplete MBMS counting procedure to the base station.

Images