WO2012151915A1

WO2012151915A1 - Method, system, mce, and base station for activating multiple mbms counting processes

Info

Publication number: WO2012151915A1
Application number: PCT/CN2011/082475
Authority: WO
Inventors: 许辉; 马子江; 王亚英; 谢玉堂
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-08-19
Filing date: 2011-11-18
Publication date: 2012-11-15
Also published as: CN102957999A; CN102957999B

Abstract

Disclosed is a method for activating multiple MBMS counting processes, comprising: a multi-cell/multicast coordination entity (MCE) activating within a correction cycle of a multicast control channel (MCCH) more than two different MBMS counting processes; the different MBMS counting processes having in an MBMS service counting request transmitted by the MCE either a different MBSFN area identity and/or a different MCCH update time. Also disclosed are a system, the MCE, and a base station for implementing the method for activating the multiple MBMS counting processes. The technical solution of the present invention provides the MBMS counting process in existing MBMS system with improved supplement, thereby improving the quality of service of the MBMS system, and improving experience of UE user.

Description

Method and system for starting multiple MBMS counting processes, MCE and base station

The present invention relates to a counting technology of a suspended Multimedia Broadcast Multicast Service (MBMS), and more particularly to a method and system for starting a plurality of MBMS counting processes in a Long Term Evolution (LTE) system. MCE and base station. Background technique

With the rapid development of the Internet and the popularity of large-screen multi-function mobile terminals, a large number of mobile data multimedia services and various high-bandwidth multimedia services, such as video conferencing, television broadcasting, video on demand, advertising, online education, interactive games, etc., have emerged. This aspect meets the needs of mobile users for multiple services, and also brings new business growth points for mobile operators. These mobile data multimedia services require multiple users to receive the same data at the same time. Compared with general data services, they have the characteristics of large data volume, long duration, and delay sensitivity.

In order to effectively utilize mobile network resources, the 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project) proposes Multimedia Broadcast Multicast Service (MBMS), which is a data source to multiple The technology for transmitting data by the target mobile terminal 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 plain text low-rate message class multicast and broadcast, but also realize high-speed multimedia service broadcast and multicast, 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 3G.

Currently, in the Long Term Evolution (LTE, Long Term Evolution) system version 9 ( Release 9) The MBMS technology was introduced in the system and optimized in LTE Release 10 (RIO, Release 10). The MBMS service is implemented in the system by carrying a common transmission requiring control signaling (also called MBMS control signaling) and user data (also called 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 control signaling is transmitted in the LTE R9 and R10 systems through a Multicast Control Channel (MCCH), a Broadcast Control Channel (BCCH), and MCH Scheduling Information (MSI, MCH Scheduling Information). The MBMS service is transmitted through a Multicast Traffic Channel (MTCH).

The MBMS control signaling and the MBMS service are transmitted in the MBSFN Area (MBSFN Area). The MBSFN Area is composed of a series of areas, and generally includes one or more cells controlled by an evolved base station (eNB). 1 is a schematic diagram of a logical structure of an existing MBSFN area. As shown in FIG. 1, the MBSFN area (such as in a circle) includes 19 cells, where eNB1 controls cell 1, cell 2 cell 6; eNB2 controls cell 7, cell 8 cell 13; eNB3 controls cell 14, cell 15 cell 19.

Alternatively, eNB1 controls cell 1 and cell 2 cell 13, wherein cell 1 and cell 2 cell 6 belong to MBSFN area 1, and cell 7 and cell 8 cell 13 belong to MBSFN area 2, that is, different cells in eNB1 belong to different MBSFN areas.

Considering the prior art, sending control signaling and user data in the MBSFN Area will use the MBSFN technology for synchronous transmission (the purpose is to enable the UE to obtain a corresponding combining gain when receiving), and the MBSFN technology requires each cell in the MBSFN area to 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 using multi-cell/multicast coordination entities (MCE, Multi-cell/multicast Coordination) Entity) The network element is used for unified scheduling and planning of radio resources. For details, refer to the international standard 3GPP 36.300.

2 is a schematic structural diagram of an existing MBMS control system. As shown in FIG. 2, in an existing MBMS system, an MBMS-related network element includes an eNB, an MCE, an MBMS Gateway (MBMS Gateway), and a broadcast multicast service center (BM-). SC, Broadcast Multicast Service Centre) and Mobility Management Entity (MME), where BM-SC is used as Session Start, Session Stop, Session Updated or MBMS Service Data. The provided network element; the MBMS GW sends the MBMS service data to the corresponding eNB through the M1 interface; the MBMS GW sends the control plane information (such as the Session Start message, the Session Stop message, the Session Updated message) generated by the BM-SC to the Sm interface. The MME is used as a forwarding network element to forward the control plane information sent by the MBMS GW to the MCE through the M3 interface. The MCE sends the corresponding control plane information to the corresponding eNB. Through such processing, the eNB obtains the MBMS service data. And corresponding control surface information.

In order to further optimize the MBMS service transmission, the industry introduces the UE uplink feedback mechanism. Specifically, the uplink feedback mechanism is mainly applied to the network side to obtain the number of interested/receiving users (or the number of UEs) for each MBMS service; The acquisition of the MBMS service is optimized by acquiring the number of users. For example, the suspension is receiving an MBMS service with a small number of users, and resuming the MBMS service that is receiving 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 the MBMS service to perform uplink feedback, and notify The UE currently receives the status of the MBMS. The network side may obtain information about the number of UEs through uplink feedback (ie, how many interested/received UEs are available for a certain MBMS), and apply to the suspension or recovery operation of the MBMS service; in other words, the network side may The number of UEs obtained by the uplink feedback determines that the MBMS service is empty. Whether to send MBSFN on the port.

Figure 3 is a complete flow chart of the MBMS service count. As shown in Figure 3, when the MBMS service needs to be counted, these MBMS services are referred to as the service to be counted, or the service, or the MBMS service.

Step 1 : The MCE first passes the MBMS service count request message (MBMS SERVICE)

COUNTING REQUEST) Configure the to-be-counted service of the MBSFN area for the eNB (the service in this specification refers to the MBMS service unless otherwise specified), and each MBMS SERVICE COUNTING REQUEST message can only contain one MBSFN area to be counted, and the service The total number is up to 16.

The MBMS SERVICE COUNTING REQUEST message definition is shown in Table 1:

Table 1

The MCCH Update Time is defined as shown in Table 2:

Table 2

That is, the MCCH Update Time indicates the time when the eNB sends an updated MCCH message (including the MBMSCountingRequest message) on the air interface, which is represented by a multiple of the MCCH Modification Period (MP).

Step 2: The eNB sends an MBMS service count response message (MBMS SERVICE COUNTING RESPONSE message) to the MCE to receive a count request from the MCE; If the eNB fails to perform step 1 correctly, the MBMS service count failure message is sent to the MCE.

(MBMS SERVICE COUNTING failure message ).

Step 3: The eNB sends a counting request on the MCCH corresponding to the MBSFN area.

(MBMSCountingRequest) message, the UE receives the MBMSCountingRequest message carried on the MCCH, and learns that the eNB is counting the number of users of certain MBMS services.

Step 4: The corresponding UE (ie, the UE that is interested in and/or receiving the MBMS service for counting) feeds back to the eNB by using a count response (MBMSCountingResponse) message; considering that the number of corresponding UEs under the eNB may be large, the eNB The corresponding feedback information will be collected over a period of time, which can be an MCCH Modification Period, such as 5.12 seconds, or 10.24 seconds.

The MBMSCountingResponse message definition is shown in Table 3:

MBMSCountingResponse-r 10::: SEQUENCE { criticalExtensions CHOICE {

Cl CHOICE {

countingResponse-r 10

MBMSCountingResponse-r 10-IEs,

Spare3 NULL, spare2 NULL, spare 1 NULL criticalExtensionsFuture SEQUENCE {}

}

MBMSCountingResponse-r 10-IEs: := SEQUENCE {

mbsfh-Arealndex-rlO INTEGER

( 0..maxMBSFN-Area-l ) OPTIONAL, countingResponseList-rl 0 CountingResponseList-r 10

OPTIONAL,

lateNonCriticalExtension OCTET STRING

OPTIONAL,

nonCriticalExtension SEQUENCE {}

OPTIONAL

}

CountingResponseList-rl 0 ::= SEQUENCE ( SIZE

( 1..maxServiceCount ) ) OF CountingResponselnfo-r 10

CountingResponselnfo-rl 0 ::= SEQUENCE {

countingResponseService-rl 0 INTEGER

( 0.. maxServiceCount- 1 ),

}

table 3

As you can see from Table 3, there are two key information elements ( IE , Information Element ) in the MBMSCountingResponse message: mbsfii-Arealndex-rl 0 and countingResponseService-rl 0 , which are the MBSFN area index and the MBMS counting service index.

Step 5: When the eNB completes the collection of the UE feedback information, the eNB reports the corresponding statistical result to the MCE, that is, the eNB sends an MBMS Service Counting Results Report to the MCE.

The foregoing step 1 and step 2 are performed by using an M2 interface between the MCE and the eNB, and are used to start the MBMS service counting process. In step 3 and step 4, the Uu interface between the eNB and the UE is used to complete the eNB in the MCCH. Configure the service to be counted, and the UE receives the service to be counted. And the UE feeds back the counting result to the eNB, and the step 5 uses the M2 interface between the MCE and the eNB, and is used by the eNB to report the result to the MCE 4. A complete MBMS Service Counting process should include the MBMS service count initiation process in steps 1 and 2, the MBMS service counting process in the hollow port in steps 3 and 4, and the MBMS service counting result in step 5. Reporting process. That is to say, the MCE starts an MBMS service counting process, and obtains the counting result of the MBMS service, and then completes an MBMS service counting process.

It can be seen from the above analysis that when the MFE-triggered service to be counted belongs to multiple MBSFN areas, the MCE must send multiple MBMS SERVICE COUNTING REQUEST messages to count (each request message includes only one MBSFN area to be counted) Or when the MCE-triggered service to be counted belongs to an MBSFN area but the number of services is greater than 16, the MCE needs to send multiple MBMS SERVICE COUNTING REQUEST information to count (each request message includes up to 16 services). That is to say, in many cases, when the MCE receives multiple (more than 16) services that need to be counted from the carrier or services that need to be counted in multiple MBSFN areas, the MCE needs to send multiple pieces. The MBMS SERVICE COUNTING REQUEST message is used to count, that is, the MCE needs to start multiple MBMS SERVICE COUNTING processes.

The current problems include the following:

1. If the MCE indicates that the eNB initiates multiple MBMS counting processes in one MCCH modification period, the MBMS CountingResponse message sent by the UE only includes the MBSFN area index and the MBMS service index, instead of the specific ID value, so the eNB may not be able to distinguish the counting response. The message, such as: UE1 sends the MBMSCountingResponse message to mbsfh-Arealndex-rl 0=000 (3bits, indicating MBSFN area 1) and countingResponseService-r 10=0001 (4bits, indicating MBMS counting service 2); UE2 sends the MBMSCountingResponse message to mbsfn-Arealndex -r 10=000 ( 3bits , Indicates MBSFN area 1) and countingResponseService-rl 0=0001 (4bits, indicating MBMS counting service 3). When UE1 and UE2 belong to eNB1, when eNB1 receives the above count response message, it cannot correctly distinguish the MBMS service corresponding to the count response.

2. If the result of some services is not fed back to the MCE due to wireless network problems or other faults, according to the existing specifications, the MCE cannot determine whether the counting process is successful.

3. If eNB1 belongs to MCE1 and MCE2 (partial cell of eNB1 belongs to MBSFN areal and another part of cell belongs to MBSFN area2), since there is no interface between MCEl and MCE2, MCE1 initiates a counting request in MBSFN areal, and MCE2 initiates counting request in MBSFN area2. UE1 is in the MBSFN areal, UE1 sends the MBMSCountingResponse message to mbsf -Arealndex-r 10=000 (3bits, indicating MBSFN area 1) and countingResponseService-r 10=0001 (4bits, indicating MBMS counting service 2); UE2 is in MBSFN area 2 In the UE2, the UE sends the MBMSCountingResponse message to mbsfh-Arealndex-rl 0=000 (3bits, indicating MBSFN area 2) and countingResponseService-r 10=0001 (4bits, indicating MBMS counting service 3). Since UE1 and UE2 belong to the same eNB1, when the eNB1 receives the above count response message, the MBSFN area and the MBMS service of the count response should not be correctly distinguished. Summary of the invention

In view of this, the main object of the present invention is to provide a method and system for starting a plurality of MBMS counting processes, an MCE and a base station, which can effectively manage multiple MBMS counting processes, and enable the MCE to judge whether the counting process fails. Therefore, take corresponding measures.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A method of initiating a plurality of MBMS counting processes, including:

The MCE initiates two or more different MBMS counting processes in one MCCH modification period; wherein the different MBMS counting process is the MBSFN area identifier in the MBMS service count request message MBMS SERVICE COUNTING REQUEST sent by the MCE Same and / or MCCH update time is different from MCCH Update Time

Preferably, the method further comprises: not receiving the counting result report in the interval, determining that the MBMS counting process fails.

Preferably, the method further includes:

When the two or more MBMS SERVICE COUNTING REQUESTs received by the base station eNB are required to complete the same MBMS counting process in the same MCCH modification period, only the first received MBMS SERVICE COUNTING REQUEST or the currently received MBMS SERVICE COUNTING REQUEST; The same MBMS counting process is the same as the MBSFN area identifier and the MCCH Update Time in the MBMS service count request message MBMS SERVICE COUNTING REQUEST sent by the MCE.

Preferably, the method further includes:

In the MBMS SERVICE COUNTING REQUEST message sent by the MCE, the sending order is set in ascending order.

Preferably, the method further includes:

When the eNB receives more than two identical MBMS SERVICE COUNTING REQUESTs, it only processes the first received MBMS SERVICE COUNTING REQUEST or the currently received MBMS SERVICE COUNTING REQUEST.

Preferably, the starting of more than two MBMS counting processes in one MCCH modification period is:

During an MCCH modification period, the MCE simultaneously sends two or more different MBMS SERVICE COUNTING REQUESTs or sequentially sends two or more different MBMS SERVICE COUNTING REQUESTs; The MCCH Update Time in the two or more MBMS counting processes is different: MCCH in the two or more MBMS SERVICE COUNTING REQUEST

Update Time is a different value.

A system for initiating a plurality of MBMS counting processes, including an MCE and an eNB, wherein an MCE is configured to initiate two or more different MBMS counting processes in one MCCH modification period; wherein, the different MBMS counting process is MBMS sent by MCE

The MBSFN area identifier in the SERVICE COUNTING REQUEST is different and/or the MCCH update time is different from the MCCH Update Time.

Preferably, the MCE is further used to send MBMS SERVICE COUNTING

When the count result report is not received within the set period of REQUEST, it is determined that the MBMS count process has failed.

Preferably, in the MBMS SERVICE COUNTING REQUEST message sent by the MCE, the MCCH UpdateTime value is set in ascending order according to the sending order of the MBMS SERVICE COUNTING REQUEST.

Preferably, the eNB is configured to: after receiving the MBMS SERVICE COUNTING REQUEST, determine that the MCCH Update Time value in the MBMS SERVICE COUNTING REQUEST message is smaller than the MCCH Update Time value in the previously received MBMS SERVICE COUNTING REQUEST message, and discard Currently received MBMS SERVICE COUNTING REQUEST.

Preferably, the eNB is configured to process only the first received MBMS SERVICE COUNTING REQUEST or the currently received MBMS SERVICE COUNTING REQUEST when more than two identical MBMS SERVICE COUNTING REQUESTs are received.

A multi-cell/multicast coordination entity, including:

a start unit, configured to start more than two during a MCCH modification period of a multicast control channel Different MBMS counting processes; wherein the different MBMS counting process is different for the MBSFN area identifier and/or the MCCH update time MCCH Update Time in the MBMS service count request message MBMS SERVICE COUNTING REQUEST sent by the MCE.

Preferably, the multi-cell/multicast coordination entity further includes:

The determining unit is configured to determine that the MBMS counting process fails when the counting result report is not received within a set period of time when the MBMS SERVICE COUNTING REQUEST is sent.

A base station includes a receiving unit and a processing unit, where:

a receiving unit, configured to receive MBMS SERVICE COUNTING REQUEST;

The processing unit, for receiving more than two MBMS SERVICE COUNTING REQUEST, requires only the first received MBMS SERVICE COUNTING REQUEST or the currently received MBMS SERVICE when the same MBMS counting process is completed within the same MCCH modification period. COUNTING REQUEST; wherein, the same MBMS counting process is the same as the MBSFN area identifier and the MCCH Update Time in the MBMS service count request message MBMS SERVICE COUNTING REQUEST sent by the MCE.

Preferably, the base station further includes a determining unit and a discarding unit, where:

a determining unit, configured to: after receiving the MBMS SERVICE COUNTING REQUEST, determine that the MCCH Update Time value in the MBMS SERVICE COUNTING REQUEST message is smaller than the MCCH Update Time value in the previously received MBMS SERVICE COUNTING REQUEST message, triggering the discarding unit ;

A discard unit that discards the current or previously received MBMS SERVICE COUNTING REQUEST.

In the present invention, the multi-cell/multicast coordination entity MCE may initiate two or more different MBMS counting processes in one multicast control channel MCCH modification period, where the different counting process refers to the MBMS service counting request message MBMS SERVICE COUNTING REQUEST of The MBSFN area identifier is different or the MCCH update time is different from the MCCH Update Time. When the MCE does not receive the counting result report within a period of time after the MCE sends the count MBMS request message, the MCE considers that the counting process fails; when the counting MBMS request message received by the eNB requires completion of multiple counting request processes within one MCCH modification period The eNB only processes the first received MBMS request message or the currently received MBMS count request message, ignoring the subsequent counting request or the previous counting request. And after receiving the count MBMS request message, determining that the MCCH Update Time value in the count MBMS request message is smaller than the MCCH Update Time value in the previously received count MBMS request message, discarding the currently received count MBMS request message. The invention realizes effective management of multiple MBMS counting processes; enables the MCE to determine whether the MBMS counting process fails, and accordingly takes corresponding measures; and can effectively process multiple parallel MBMS counting request messages. The invention effectively improves the existing MBMS counting process, improves the service quality of the MBMS system, and improves the experience effect of the UE user. DRAWINGS

1 is a schematic diagram of a logical structure of an existing MBSFN area;

2 is a schematic structural diagram of an existing MBMS control system;

Figure 3 is a complete MBMS service count flow chart;

4 is a flowchart of a method for starting a plurality of MBMS counting processes according to Embodiment 1 of the present invention; FIG. 5 is a flowchart of a method for starting a plurality of MBMS counting processes according to Embodiment 2 of the present invention; Method flow diagram of multiple MBMS counting processes; FIG. 7 is a schematic structural diagram of a multi-cell/multicast coordination entity according to the present invention;

FIG. 8 is a schematic structural diagram of a base station of the present invention. detailed description

The basic idea of the invention is that the multi-cell/multicast coordination entity MCE can initiate two or more different MBMS counting processes within one multicast control channel MCCH modification period, the difference The counting process means that the MBSFN area identifiers in the MBMS service count request message MBMS SERVICE COUNTING REQUEST are different or the MCCH update time MCCH Update Time is different. When the MCE sends the count MBMS request message and does not receive the count result report within a period of time, the MCE considers that the counting process fails; when the counted MBMS request message received by the eNB requires completion of multiple identical count request processes in one MCCH modification period When the eNB processes only the first received MBMS request message or the currently received MBMS count request message, ignoring the subsequent counting request or the previous counting request, the same counting process refers to the MBMS service counting request message MBMS SERVICE COUNTING REQUEST The MBSFN area identifier in the same is the same as the MCCH update time MCCH Update Time. And after receiving the count MBMS request message, determining that the MCCH Update Time value in the count MBMS request message is smaller than the MCCH Update Time value in the previously received count MBMS request message, discarding the currently received count MBMS request message.

In the present invention, the MCE is a logical entity, and the MCE can exist as a single network element or a part of other network elements. The same MCE is logically the same MCE, that is, the MCE can be located in multiple network elements. But have the same logo;

The MBMS service count request message sent by the MCE to the eNB further includes an activation time, that is, the time when the eNB updates the MCCH message (MCCH Update Time); the MCCH Update Time is an absolute value, and the value ranges from 0 to 255. The integer is in the MCCH modification period. In the present invention, starting a plurality of MBMS counting processes in one MCCH modification period means: in an MCCH modification period, the MCE simultaneously starts sending multiple counting request messages or sequentially sending multiple counting requests. The message that the MCCH Update Time cannot be the same means that the MCCH Update Time in each count request message must be a different value.

In the present invention, the period of time is: MCCH Update Time ΜΡ+Τ; wherein MCCH Update Time is the MCCH Update Time set by the MCE in the MBMS Service Counting Request message, where MP (Modification period) refers to the MCCH modification period, Both the MCE and the related eNB are aware of the value of the MP; where T is the time when the eNB counts and sends the MBMS Service Counting Results Report, and the T can take values according to the network status or the operator policy, such as: Is, 2s, ..., 10s, Ν 任意 any of the MPs, where N is an integer, N=0, 1 , 2, .. , 255; MP is the MCCH modification period; after the MCE considers that the counting request process fails, the MCE may resend or stop sending the counting request Message. Unless otherwise stated, the MPs in this specification are MCCH modification cycles.

Embodiment 1

FIG. 4 is a flowchart of a method for starting a plurality of MBMS counting processes according to Embodiment 1 of the present invention. As shown in FIG. 4, the method for starting a plurality of MBMS counting processes in this example specifically includes the following steps: Step 101: The MCE starts multiple MBMSs. Business counting process.

When the MCE needs to initiate multiple MBMS service counting procedures, the MCE sends an MBMS Service Counting Request message to a plurality of eNBs under its control.

It should be noted that: the foregoing multiple MBMS counting process corresponds to multiple MBMS Service Counting Request messages, and the value of the MCCH Update Time in each MBMS counting request message cannot be the same, and different values must be used.

Step 102: The eNB determines whether the content of the MBMS Service Counting Request message can be correctly obtained. If yes, step 103 is performed; otherwise, step 109 is performed.

The content of the MBMS Service Counting Request message cannot be correctly obtained. It may cause the eNB to not correctly decode the MBMS Service Counting Request message due to network reasons (such as link failure) or other reasons (such as hardware failure).

Step 103: The eNB sends an MBMS Service Counting Response to the MCE. If the eNB correctly decodes the MBMS Service Counting Request message, the MBMS Service Counting Response message is sent to the MCE.

Step 104: The eNB sends an MBMSCountingRequest message on the air interface. The eNB determines the time at which the counting request (MBMSCountingRequest) message is sent on the air interface according to the value of the MCCH Update Time in the MBMS Counting Request message.

When the eNB receives the MBMS Counting Request message of multiple MCEs, the eNB sends a corresponding counting request message on the air interface.

The air interface MBMS count request message is sent through the MCCH.

Step 105: The UE sends an MBMS Counting Response (MBMSCountingResponse) message. The UE that is interested and/or is receiving the count MBMS service feeds back to the eNB by a Count Response (MBMSCountingResponse) message.

Step 106: The eNB receives the MBMS count response, and counts the number of UEs.

Considering that the number of corresponding UEs in the eNB may be large, the eNB will collect corresponding feedback information for a period of time, which is an MCCH Modification Period, such as 5.12 seconds or 10.24 seconds.

Step 107: The eNB sends the statistics to the MCE.

When the eNB completes the collection of the UE feedback information, the eNB will upload the corresponding statistics to the MCE, that is, the eNB sends an MBMS Service Counting Results Report to the MCE.

Step 108: The MCE determines to suspend or resume the MBSFN transmission of the MBMS service according to the counting statistics, and the process ends.

The suspension means that the eNB deletes the MBMS resource on the air interface, stops sending the MCCH change notification, reserves the MBMS service context, and reserves or leaves the IP multicast group.

The recovery means that the eNB restores the MBMS resource on the air interface, resumes sending the MCCH change notification, and then leaves the IP multicast grou to re-enter the port.

Step 109: The eNB sends an MBMS Service Counting Failure message to the MCE. Step 110: The MCE determines whether to resend the count request message, if yes, execute step 111, otherwise perform step 112. If the MCE receives the MBMS service counting failure message of one or more eNBs, it indicates that the MCE has not successfully started the MBMS service counting process, and the MCE can:

a) The MCE repeatedly restarts the MBMS service counting process until it succeeds; b) the MCE restarts several MBMS service counting processes, and if it fails, it gives up; c) The MCE abandons the MBMS service counting process.

Step 111: The MCE resends the counting request message, and step 102 is performed.

Step 112: The MCE stops sending the count request message, and the process ends.

Embodiment 2

FIG. 5 is a flowchart of a method for starting a plurality of MBMS counting processes according to Embodiment 2 of the present invention. As shown in FIG. 5, the method for starting multiple MBMS counting processes in this example specifically includes the following steps: Step 201: The MCE sends on the M2 interface. MBMS Service Counting Request message. Step 202: The eNB sends an MBMS Service Counting Response response to the MCE. Step 203: The MCE determines whether the MBMS counting process is successful. If yes, the process ends. Otherwise, step 204 is performed.

Step 204: After the MCE does not receive the MBMS Service Counting Results Report message, the counting process fails.

The time period is specifically: MCCH Update Time MCCH ΜΡ+Τ; wherein the MCCH Update Time is the value in the MBMS Service Counting Request message, the MCCH MP is the MCCH modification period, and T is the eNB statistics UE number and the transmission count report time, T It can be based on network status or carrier policy, such as: Is, 2s, ..., 5s, Ν χ MP, etc., where N is an integer, N=0, 1 , 2, ..·, 255.

Step 205: The MCE retransmits or sends a new or stops sending the MBMS Counting Request message. Embodiment 3 FIG. 6 is a flowchart of a method for starting a plurality of MBMS counting processes according to Embodiment 3 of the present invention. As shown in FIG. 6, the method for starting a plurality of MBMS counting processes in this example specifically includes the following steps: Step 301: MCE1 is in MBSFN areal Send the MBMS Service Counting Request message, MCCH Update Time=N.

MCE2 sends an MBMS Service Counting Request message in MBSFN area2.

MCCH Update Time=N.

Step 302: The eNB1 receives the MBMS count request message of the MCE1 and the MCE2.

The eNB1 sends an MBMS Service Counting Response message to the MCE1 and the MCE2, respectively, indicating that the MBMS count request information is correctly received.

Step 303: The eNB1 determines, according to the sequence of receiving the MBMS count request message, which MBMS count request message is sent in the air interface. If the MBMS count request message of the MCE1 is received first, the process proceeds to step 304. Otherwise, step 306 is performed.

It should be noted that: if the eNB receives the MBMS Counting Request message of multiple MCEs, and requires the eNB to complete the MBMS counting in the same MCCH modification period, the eNB according to the sequence of the received MBMS counting request messages of the multiple MCEs, Only the first received MBMS count request message is sent, and the subsequently received MBMS count request message is ignored.

Of course, in the present invention, the eNB may only send the currently received MBMS count request message according to the sequence of the received MBMS count request messages of the multiple MCEs, and ignore the previously received MBMS count request message.

Step 304: The eNB1 sends an MBMS Counting Request message of the MCE1 on the air interface.

MBMSCountingRequesto

Step 305: The UE in the MBSFN areal sends an MBMS count response message, and the eNB counts the number of UEs and sends a count result report to the MCE1, and the process ends.

Step 306: The eNB1 sends an MBMS Counting Request message MBMSCountingRequesto of the MCE2 on the air interface. Step 307: The UE in the MBSFN area2 sends an MBMS count response message, and the eNB counts the number of UEs and sends a count result report to the MCE2, and the process ends.

The present invention also describes a system for initiating a plurality of MBMS counting processes, including an MCE and an eNB. Since the present invention does not improve the existing network architecture, but only improves the function of the network element therein, The inventive system for initiating multiple MBMS counting processes can still be understood with reference to the existing network architecture, as understood with reference to the network architecture shown in FIG. 2. The following describes the related functions of the improved network element in detail.

The MCE is configured to start two or more different MBMS counting processes in a multicast control channel MCCH modification period, where the different processes refer to different MBSFN area identifiers in the MBMS service count request message MBMS SERVICE COUNTING REQUEST or MCCH update time MCCH Update Time is different.

The MCE is further configured to determine that the MBMS counting process fails when the counting result report is not received within a set period of time when the MBMS SERVICE COUNTING REQUEST is sent.

The eNB is configured to process only the first received MBMS SERVICE COUNTING REQUEST or the currently received MBMS SERVICE COUNTING REQUEST when the received two or more MBMS SERVICE COUNTING REQUEST requests to complete the MBMS counting process in the same MCCH modification period. .

The eNB is configured to: after receiving the MBMS SERVICE COUNTING REQUEST, determine that the MCCH Update Time value in the MBMS SERVICE COUNTING REQUEST is smaller than the MCCH Update Time value in the previously received MBMS SERVICE COUNTING REQUEST, and discard the currently received MBMS. SERVICE COUNTING REQUEST.

The MCE is a logical entity, and the MCE can exist as a single network element or part of other network elements. The same MCE refers to the same MCE, that is, MCE. Can be located in multiple network elements, but with the same identity;

The MBMS service count request message sent by the MCE to the eNB includes an activation time, that is, the time when the eNB updates the MCCH message (MCCH Update Time); the MCCH Update Time is an absolute value, and the value ranges from 0 to 255. The unit is the MCCH modification period; the initiating the multiple MBMS counting process in one MCCH modification period means: in an MCCH modification period, the MCE simultaneously starts sending multiple counting request messages or sequentially sending multiple counting request messages, The MCCH Update Time cannot be the same: the MCCH Update Time in each count request message must be a different value.

The period of time is: MCCH Update Time χ ΜΡ + Τ; where MCCH Update Time refers to the MCCH Update Time set by the MCE in the MBMS Service Counting Request message, where MP (Modification period) refers to the MCCH modification period, MCE and related The eNB is known to take the value of the MP; where T is the time when the eNB counts and sends the MBMS Service Counting Results Report, and can take values according to the network status or the carrier policy, such as: Is, 2s, ..., 10s, N Any one of MPs, where N is an integer, N=0, 1, 2, .., 255; MP is the MCCH modification period; after the MCE considers that the counting request process fails, the MCE may resend or stop sending the counting request message. . Unless otherwise stated, the MPs below are all MCCH modification cycles.

FIG. 7 is a schematic structural diagram of a multi-cell/multicast coordination entity according to the present invention. As shown in FIG. 7, the multi-cell/multicast coordination entity of the present invention includes:

The initiating unit 70 is configured to start two or more different MBMS counting processes in a multicast control channel MCCH modification period, where the different MBMS counting process is an MBMS service counting request message sent by the MCE, MBMS SERVICE COUNTING REQUEST The MBSFN area identifiers in the different and/or MCCH update time MCCH Update Time are different.

As shown in FIG. 7, the multi-cell/multicast coordination entity of the present invention further includes:

Determination unit 71, When the count result report is not received within the set time period, it is determined that the MBMS count process has failed.

It will be understood by those skilled in the art that the determining unit 71 is provided for optimizing the technical solution of the multi-cell/multicast coordination entity of the present invention, and is not a necessary technical feature for implementing the technical solution of the multi-cell/multicast coordination entity of the present invention.

Those skilled in the art will appreciate that the implementation functions of the various units in the multi-cell/multicast coordination entity illustrated in Figure 7 can be understood with reference to the related description of the methods and systems for initiating a plurality of MBMS counting procedures. The functions of the units in the multi-cell/multicast coordination entity shown in Figure 7 can be implemented by programs running on the processor, or by specific logic circuits.

FIG. 8 is a schematic structural diagram of a base station according to the present invention. As shown in FIG. 8, the base station of the present invention includes a receiving unit 80 and a processing unit 81, where:

The receiving unit 80 is configured to receive the MBMS SERVICE COUNTING REQUEST; the processing unit 81 is configured to receive more than two MBMS SERVICE COUNTING REQUEST requests to complete the same MBMS counting process in the same MCCH modification period, and only process the first receiving The MBMS SERVICE COUNTING REQUEST or the currently received MBMS SERVICE COUNTING REQUEST; wherein the same MBMS counting process is the same as the MBSFN area identifier and the MCCH Update Time in the MBMS service count request message MBMS SERVICE COUNTING REQUEST sent by the MCE .

As shown in FIG. 8, the base station of the present invention further includes a determining unit 82 and a discarding unit 83, wherein: the determining unit 82 is configured to determine the MCCH in the MBMS SERVICE COUNTING REQUEST message after receiving the MBMS SERVICE COUNTING REQUEST

When the Update Time value is less than the MCCH Update Time value in the previously received MBMS SERVICE COUNTING REQUEST message, the discard unit is triggered;

A discarding unit 83, for discarding the current or previously received MBMS SERVICE

COUNTING REQUEST. It should be understood by those skilled in the art that the determining unit 82 and the discarding unit 83 are provided for optimizing the technical solution of the multi-cell/multicast coordination entity of the present invention, and are not the technical solution for implementing the multi-cell/multicast coordination entity of the present invention. Necessary technical features.

It will be understood by those skilled in the art that the implementation functions of the processing units in the base station shown in FIG. 8 can be understood by referring to the related description of the method and system for initiating a plurality of MBMS counting processes. The functions of the units in the base station shown in Fig. 7 can be realized by a program running on the processor, or can be realized by a specific logic circuit.

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

Claims

Claim

A method for initiating a plurality of MBMS counting processes, the method comprising:

The multi-cell/multicast coordination entity MCE initiates two or more different MBMS counting processes in a multicast control channel MCCH modification period; wherein the different MBMS counting process is an MBMS service counting request message MBMS SERVICE sent by the MCE The MBSFN area identifiers in the COUNTING REQUEST are different and/or the MCCH update time MCCH Update Time is different.

2. The method according to claim 1, wherein the method further comprises: not receiving a count result report in the interval, determining that the MBMS counting process fails.

The method according to claim 1 or 2, wherein the method further comprises: two or more MBMS SERVICE COUNTING received by the base station eNB

REQUEST requires that only the first received MBMS SERVICE COUNTING REQUEST or the currently received MBMS SERVICE COUNTING REQUEST is processed when the same MBMS counting process is completed within the same MCCH modification period; wherein the same MBMS counting process is The MBSFN area identifier in the MBMS service count request message MBMS SERVICE COUNTING REQUEST sent by the MCE is the same as the MCCH Update Time.

The method according to claim 1 or 2, wherein the method further comprises: in the MBMS SERVICE COUNTING REQUEST message sent by the MCE, the sending order is set in ascending order.

The method according to claim 4, wherein the method further comprises: receiving, by the eNB, two or more identical MBMS SERVICE COUNTING For REQUEST, only the first received MBMS SERVICE COUNTING REQUEST or the currently received MBMS SERVICE COUNTING REQUEST.

The method according to any one of claims 1 to 4, wherein the starting of the two or more MBMS counting processes in one MCCH modification period is:

During an MCCH modification period, the MCE simultaneously sends two or more different MBMS SERVICE COUNTING REQUESTs or sequentially sends two or more different MBMS SERVICE COUNTING REQUESTs;

The MCCH Update Time in the two or more MBMS counting processes is different: the MCCH Update Time in the two or more MBMS SERVICE COUNTING REQUESTs are different values.

7. A system for initiating a plurality of MBMS counting processes, comprising an MCE and an eNB, wherein:

The MCE is configured to start two or more different MBMS counting processes in one MCCH ί 爹周期 cycle; wherein the different MBMS counting process is different for the MBSFN area identifier in the MBMS SERVICE COUNTING REQUEST sent by the MCE Or MCCH update time is different for MCCH Update Time.

8. The system of claim 7 wherein:

9. A system according to claim 7 or claim 8 wherein:

10. The system of claim 9 wherein: The eNB is configured to: after receiving the MBMS SERVICE COUNTING REQUEST, determine that the MCCH Update Time value in the MBMS SERVICE COUNTING REQUEST message is smaller than the MCCH Update Time value in the previously received MBMS SERVICE COUNTING REQUEST message, discarding the current reception MBMS SERVICE COUNTING REQUEST.

11. A system according to claim 7 or claim 8 wherein:

The eNB is configured to process only the first received MBMS SERVICE COUNTING REQUEST or the currently received MBMS SERVICE COUNTING REQUEST when more than two identical MBMS SERVICE COUNTING REQUESTs are received.

12. A multi-cell/multicast coordination entity, wherein the multi-cell/multicast coordination entity comprises:

And a starting unit, configured to start two or more different MBMS counting processes in a multicast control channel MCCH modification period, where the different MBMS counting process is an MBMS service counting request message MBMS SERVICE COUNTING REQUEST sent by the MCE The MBSFN area identifier is different and/or the MCCH update time is different from the MCCH Update Time.

The multi-cell/multicast coordination entity according to claim 12, wherein the multi-cell/multicast coordination entity further comprises:

A base station, comprising: a receiving unit and a processing unit, wherein:

a receiving unit, configured to receive MBMS SERVICE COUNTING REQUEST;

The processing unit, for receiving more than two MBMS SERVICE COUNTING REQUEST requests to process only the first received MBMS SERVICE COUNTING REQUEST or current when completing the same MBMS counting process in the same MCCH modification period The received MBMS SERVICE COUNTING REQUEST; wherein the same MBMS counting process is the same as the MBSFN area identifier and the MCCH Update Time in the MBMS service count request message MBMS SERVICE COUNTING REQUEST sent by the MCE.

The base station according to claim 14, wherein the base station further comprises a determining unit and a discarding unit, wherein: