CN107040996B - Processing method and device for Internet of vehicles service identification - Google Patents

Abstract

The invention provides a processing method and a device for a service identifier of the Internet of vehicles, wherein the method comprises the following steps: the network element receives a temporary mobile group identifier TMGI for identifying the MBMS bearer; the network element sends indication information for indicating the locally activated TMGI to the broadcast multicast service center BM-SC, or judges whether the received TMGI is the activated TMGI, and sends indication information for indicating whether TMGI conflict exists to the BM-SC according to the judging result, wherein the indication information is directly sent to the BM-SC by the network element or forwarded to the BM-SC by other network elements. The invention solves the problem that TMGI conflict exists when a plurality of BM-SC logic network elements distribute temporary mobile group identifiers when MBMS bearing broadcast V2X service is adopted in the related technology.

Description

Processing method and device for Internet of vehicles service identification

Technical Field

The invention relates to the field of Internet of vehicles, in particular to a processing method and device of Internet of vehicles service identifiers.

Background

The internet of vehicles (Vehicle to Everything, abbreviated as V2X) is to provide vehicle information through sensors, vehicle terminals and electronic tags mounted on vehicles, adopt various communication technologies to realize interconnection and intercommunication of vehicles and vehicles (Vehicle to Vehicle, abbreviated as V2V), vehicles and people (Vehicle to Pedestrian, abbreviated as V2P), vehicles and roads (infrastructure (Vehicle to Infrastructure, abbreviated as V2I)), extract and share information on an information network platform, and effectively manage and control the vehicles and provide comprehensive services. A Road Side Unit (RSU) can receive a vehicle request, ensure that the vehicle accesses the Internet and has a gateway function; in addition, it also has the functions of data operation, store and forward.

In order to effectively utilize mobile network resources, 3GPP proposes a multimedia broadcast multicast service (Multimedia Broadcast Multicast Service, abbreviated as MBMS), which is a technology for transmitting data from one data source to a plurality of target mobile terminals, thereby realizing the sharing of network resources (including a core network and an access network) and improving the utilization rate of network resources (especially air interface resources). The 3GPP has proposed a study topic of single cell MBMS in LTE-a of R13, where a single cell MBMS service is transmitted on a physical downlink shared channel PDSCH. In 3GPP network, MBMS service adopts temporary mobile group identifier (Temporary Mobile Group Identity, TMGI) which is distributed by network element BM-SC. The application server informs the UE of related service description information through an application layer signaling: such as TMGI, traffic start time, etc.

For security-class V2X services, the latency requirement is within 100ms, and 3GPP is researching the adoption of localized core networks, namely: the eNB itself or its vicinity is placed in a core network element. For uplink, the localized eNB may employ LIPA or SIPTO functionality in existing 3GPP protocols, while the downlink broadcast may place the core network of MBMS (e.g., MBMS-GW and BM-SC) in or near the eNB.

In order to ensure the time delay requirement, the 3GPP adopts MBMS to bear broadcast V2X service, the network element of MBMS can be realized locally, such as a broadcast multicast service center (Broadcast Multicast Service Centre, BM-SC for short) is realized in a base station eNB, namely, a plurality of BM-SC logic network elements exist, different BM-SCs can collide when allocating temporary mobile group identifiers (Temporary Mobile Group Identity, TMGI for short), and for example, a plurality of BM-SCs allocate the same TMGI for the same area. If the TMGI conflict occurs, the vehicle-mounted terminal in the conflict area can not determine the required TMGI, and the V2X service can fail to receive.

There is currently no effective solution to the above-described problems in the related art.

Disclosure of Invention

The invention provides a processing method and a processing device for a vehicle networking service identifier, which at least solve the problem that a temporary mobile group identifier allocated by a plurality of BM-SC logic network elements has TMGI conflict when MBMS bearing broadcast V2X service is adopted in the related technology.

According to one aspect of the invention, there is provided a method for processing a service identifier of internet of vehicles, comprising: the network element receives a temporary mobile group identifier TMGI for identifying the MBMS bearer; the network element sends indication information for indicating the locally activated TMGI to a broadcast multicast service center BM-SC, or judges whether the received TMGI is the activated TMGI, and sends indication information for indicating whether TMGI conflict exists to the BM-SC according to the judging result, wherein the indication information is directly sent to the BM-SC by the network element or forwarded to the BM-SC by other network elements.

Further, the manner in which the network element receives the TMGI includes at least one of: the network element receives the TMGI sent by an application server AS; and the network element receives the TMGI sent by the BM-SC.

Further, before the network element determines whether the TMGI for identifying the MBMS bearer is an activated TMGI, the method includes: the network element acquires an activated TMGI list; the network element determining whether the TMGI used for identifying the MBMS bearer is an activated TMGI includes: the network element judges whether the TMGI used for marking the MBMS bearer is matched with the TMGI in the TMGI list; and when the judgment result is yes, the network element sends indication information for indicating that the TMGI conflict exists to the BM-SC for identifying the TMGI of the MBMS bearing.

Further, the network element comprises at least one of: an application server AS, user equipment UE, a mobility management entity MME, a multimedia broadcast multicast service gateway MBMS-GW, a multi-cell/multicast coordination entity MCE and a base station eNB.

Further, when the network element is an AS, the network element obtaining the activated TMGI list includes: the AS respectively receives a plurality of TMGI lists notified by the BM-SC and stores the TMGI lists, wherein the TMGI in the TMGI lists is an activated TMGI; the AS sends indication information for indicating the activated TMGI list to the BM-SC through an interface with the BM-SC.

Further, when the network element is a plurality of ases, the network element obtaining an activated TMGI list in a plurality of BM-SCs connected with the network element includes: the AS respectively receives a plurality of TMGI lists notified by the BM-SC, wherein TMGI in the TMGI list is an activated TMGI; the TMGI list is shared among a plurality of the ases.

Further, when the network element is an MME, the network element obtaining an activated TMGI list in a plurality of BM-SCs connected to the network element includes: the MME receives a plurality of TMGI lists notified by the BM-SC respectively, wherein TMGI in the TMGI list is activated TMGI; the MME sends indication information for indicating the activated TMGI list to the BM-SC through the MBMS-GW.

Further, the network element determining whether the TMGI used for identifying the MBMS bearer is an activated TMGI includes: the MME receives a session start request/session update request/session stop request message sent by the BM-SC, wherein the session start request/session update request/session stop request message carries a TMGI for marking the MBMS bearer; the MME judges whether the TMGI used for identifying the MBMS bearer is matched with the TMGI in a TMGI list stored locally; when the judging result is that the message is session start request, the MME sends indication information for indicating that TMGI conflict exists to the BM-SC; otherwise, the MME indicates to the BM-SC a locally activated TMGI list.

Further, when the network element is a UE, the network element obtaining the activated TMGI list includes: the UE receives a TMGI list sent by an AS through an application layer signaling and stores the TMGI list, wherein the TMGI in the TMGI list is an activated TMGI; the UE sends the indication information of the activated TMGI to the AS through the application layer signaling, and the AS forwards the indication information to the BM-SC through an interface between the AS and the BM-SC.

Further, the network element determining whether the TMGI is an activated TMGI, and sending, to the BM-SC, indication information for indicating whether the TMGI collides according to a determination result includes: the UE judges whether the TMGI used for identifying the MBMS bearer is matched with the TMGI in a TMGI list stored locally; and when the judgment result is yes, the UE sends indication information for indicating that TMGI conflict exists to the BM-SC through the AS.

According to one aspect of the present invention, there is provided a processing device for a service identifier of internet of vehicles, applied to a network element side, including: a receiving module, configured to receive a temporary mobile group identifier TMGI for identifying an MBMS bearer; the processing module is configured to send, to a broadcast multicast service center BM-SC, indication information for indicating a locally activated TMGI, or determine whether the received TMGI is an activated TMGI, and send, to the BM-SC, indication information for indicating whether there is a TMGI collision according to a determination result, where the indication information is sent, by the network element, to the BM-SC directly or forwarded, by the network element, to the BM-SC through another network element.

Further, the receiving module comprises a unit of at least one of: a first receiving unit, configured to receive the TMGI sent by the application server AS; and the second receiving unit is used for receiving the TMGI sent by the BM-SC.

Further, the apparatus further comprises: an acquiring module, configured to acquire an activated TMGI list before determining whether a TMGI for identifying an MBMS bearer is an activated TMGI; the processing module comprises: a first judging unit, configured to judge whether a TMGI for identifying an MBMS bearer matches a TMGI in the TMGI list; and the first sending unit is used for sending indication information for indicating that the TMGI conflict exists to the BM-SC for identifying the TMGI of the MBMS bearing when the judging result is yes.

Further, the network element comprises at least one of: an application server AS, user equipment UE, a mobility management entity MME, a media broadcast multicast service gateway MBMS-GW, a multi-cell/multicast coordination entity MCE and a base station eNB.

Further, when the network element is an AS, the acquiring module includes: a first obtaining unit, configured to receive TMGI lists notified by a plurality of BM-SCs and store the TMGI lists, where a TMGI in the TMGI list is an activated TMGI; and the second sending unit is used for sending indication information for indicating the activated TMGI list to the BM-SC through an interface with the BM-SC.

Further, when the network element is a plurality of ases, the obtaining module includes: a second obtaining unit, configured to receive TMGI lists notified by a plurality of BM-SCs, where a TMGI in the TMGI list is an activated TMGI; and the sharing unit is used for sharing the TMGI list among a plurality of AS.

Further, when the network element is an MME, the acquiring module includes: a third obtaining unit, configured to receive the TMGI lists notified by the BM-SC and store the TMGI lists, where a TMGI in the TMGI list is an activated TMGI; and a third sending unit, configured to send, to the BM-SC through the MBMS-GW, indication information for indicating the activated TMGI list.

Further, the processing module includes: a first receiving unit, configured to receive a session start request/session update request/session stop request message sent by the BM-SC, where the session start request/session update request/session stop request message carries a TMGI for identifying the MBMS bearer; a first judging unit, configured to judge whether a TMGI used for identifying the MBMS bearer matches a TMGI in a locally stored TMGI list; a fourth sending unit, configured to send, when the determination result is yes and is a session start request message, indication information for indicating that there is a TMGI collision to the BM-SC; otherwise, a locally activated TMGI list is indicated to the BM-SC.

Further, when the network element is UE, the acquiring module includes: a fourth obtaining unit, configured to receive a TMGI list sent by an AS through an application layer signaling and store the TMGI list, where a TMGI in the TMGI list is an activated TMGI; and a fifth sending unit, configured to send, through application layer signaling, indication information of the activated TMGI to an AS, where the AS forwards the indication information to the BM-SC through an interface between the AS and the BM-SC.

Further, the processing module includes: a second judging unit, configured to judge whether a TMGI used for activating the MBMS bearer matches with a TMGI in a locally stored TMGI list; and a sixth sending unit, configured to send, when the determination result is yes, indication information for indicating that there is a TMGI collision to the same AS the AS to the BM-SC.

According to a further aspect of the present invention there is provided an apparatus comprising: the device of any one of the above.

In the invention, in the process of activating a MBMS bearing request through TMGI, a network element receives TMGI which is sent by a BM-SC of a broadcast multicast service center and used for activating the MBMS bearing, and then the network element judges whether the TMGI used for activating the MBMS bearing is the activated TMGI or not, and sends indication information which is used for indicating whether TMGI conflict exists or not to the BM-SC according to a judging result, wherein the indication information is directly sent to the BM-SC by the network element or forwarded to the BM-SC through other network elements. It can be seen that the present embodiment solves the problem that when the MBMS bearer broadcast V2X service is adopted in the related art, the temporary mobile group identifier is allocated by the multiple BM-SC logic network elements, and there is a TMGI collision.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

FIG. 1 is a flow chart of a method of processing a vehicle networking service identification in accordance with an embodiment of the present application;

FIG. 2 is a block diagram of a processing device for Internet of vehicles service identification according to an embodiment of the present application;

fig. 3 is a schematic diagram of an application server connected to 2 MBMS core networks according to an alternative embodiment of the application;

FIG. 4 is a schematic view of a structure according to a first alternative embodiment of the present application;

FIG. 5 is a schematic diagram of a structure according to a second alternative embodiment of the application;

FIG. 6 is a schematic diagram of a structure according to a third alternative embodiment of the application;

FIG. 7 is a schematic diagram of a structure according to a fourth alternative embodiment of the application;

fig. 8 is a schematic structural diagram of an internet of vehicles service identification distribution system according to an alternative embodiment of the present application.

Detailed Description

The application will be described in detail hereinafter with reference to the drawings in conjunction with embodiments. It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.

Furthermore, the apparatus referred to in the present embodiment includes: the system comprises a terminal, core network side equipment, an application server and access network side equipment; wherein the terminal may include at least one of: an On-Board Unit (OBU), a Road-Side Unit (RSU), and a User Equipment (UE); the core network side device at least comprises: BM-SC, MBMS-GW, mobility management entity (Mobility Management Entity, MME); wherein BM-SC is mainly responsible for distributing TMGI, initiating MBMS session start, update, stop and other processes; the MBMS-GW is mainly responsible for establishing control plane bearing to MME and user plane bearing to eNB; the MME is responsible for setting up control plane bearers to a Multi-cell/multicast coordination entity (Multi-cell/multicast Coordination Entity, abbreviated MCE). The core network may be deployed separately or locally except for the MME. The application server is used for requesting to activate the MBMS bearer, requesting TMGI and transmitting/receiving V2X service, an interface (such as MB2 interface) is arranged between the application server and BM-SC, the application server and the terminal communicate through an application layer, and the application server can be deployed independently or locally (such as through an application layer in an RSU). The access network side device at least comprises: and the MCE is used for allocating the radio resources of the V2X service and determining an MBMS transmission mode (MBSFN or SC-PTM).

In this embodiment, a method for processing a service identifier of internet of vehicles is provided, fig. 1 is a flowchart of a method for processing a service identifier of internet of vehicles according to an embodiment of the present invention, as shown in fig. 1, where the flowchart includes the following steps:

step S102: the network element receives a temporary mobile group identifier TMGI for identifying the MBMS bearer;

step S104: the network element sends indication information for indicating the locally activated TMGI to the broadcast multicast service center BM-SC, or judges whether the received TMGI is the activated TMGI, and sends indication information for indicating whether TMGI conflict exists to the BM-SC according to the judging result, wherein the indication information is directly sent to the BM-SC by the network element or forwarded to the BM-SC by other network elements.

Through step S102 and step S104 of this embodiment, in the process of activating the MBMS bearer request through the TMGI, the network element receives the TMGI for activating the MBMS bearer sent by the BM-SC of the broadcast-multicast service center, so that the network element determines whether the TMGI for activating the MBMS bearer is an activated TMGI, and sends, to the BM-SC according to the determination result, indication information for indicating whether there is a TMGI collision, where the indication information is sent by the network element directly to the BM-SC or forwarded to the BM-SC through other network elements. It can be seen that the present embodiment solves the problem that when the MBMS bearer broadcast V2X service is adopted in the related art, the temporary mobile group identifier is allocated by the multiple BM-SC logic network elements, and there is a TMGI collision.

In an optional implementation manner of this embodiment, before the network element determines whether the TMGI for identifying the MBMS bearer is an activated TMGI, the method of this embodiment may further include:

step S102-1: the network element acquires an activated TMGI list;

step S102-2: the network element determining whether the TMGI used to identify the MBMS bearer is an activated TMGI includes: the network element judges whether the TMGI used for identifying the MBMS bearer is matched with the TMGI in the TMGI list; and when the judgment result is yes, the network element sends indication information for indicating that the TMGI conflict exists to the BM-SC for identifying the TMGI of the MBMS bearer.

Based on this, the network element involved in this embodiment includes at least one of the following: an application server AS, user equipment UE, a mobility management entity MME, a multimedia broadcast multicast service gateway MBMS-GW, a multi-cell/multicast coordination entity MCE and a base station eNB.

The manner of receiving the TMGI for the network element involved in step S102 of this embodiment includes at least one of the following:

mode one: the network element receives TMGI sent by an application server AS;

mode two: the network element receives the TMGI sent by the BM-SC.

It should be noted that the method is applicable to the first mode when the network element is an application server AS and a user equipment UE, and is applicable to the second mode when the network element is an application server AS, a mobility management entity MME, a multimedia broadcast multicast service gateway MBMS-GW, a multi-cell/multicast coordination entity MCE, and a base station eNB.

When the network element is an AS, the method for the network element to acquire the activated TMGI list in step S102-1 of this embodiment may be implemented AS follows:

step S11: the AS respectively receives TMGI lists notified by a plurality of BM-SCs and stores the TMGI lists, wherein TMGI in the TMGI lists is activated TMGI;

step S12: the AS sends indication information for indicating the activated TMGI list to the BM-SC through an interface with the BM-SC.

When the network element is a plurality of ases, the method for the network element in step S102-1 of this embodiment to obtain the activated TMGI list in the plurality of BM-SCs connected to the network element may be implemented AS follows:

step S13: the AS respectively receives TMGI lists notified by a plurality of BM-SCs, wherein TMGI in the TMGI list is activated TMGI;

step S14: the TMGI list is shared among multiple ases.

When the network element is an MME, the manner in which the network element in step S102-1 of this embodiment obtains the activated TMGI list from the multiple BM-SCs connected to the network element may be implemented as follows:

step S15: the MME receives TMGI lists notified by a plurality of BM-SCs respectively, wherein TMGI in the TMGI list is activated TMGI;

step S16: the MME sends indication information for indicating the activated TMGI list to the BM-SC through the MBMS-GW.

In another optional implementation manner of this embodiment, for the network element involved in step S104 in this embodiment, the manner of determining whether the TMGI for identifying the MBMS bearer is an activated TMGI may be implemented by:

step S104-1: the MME receives a session start request/session update request/session stop request message sent by the BM-SC, wherein the session start request/session update request/session stop request message carries a TMGI for identifying the MBMS bearer;

step S104-2: MME judges whether the TMGI used for marking MBMS load is matched with TMGI in a TMGI list stored locally;

step S104-3: when the judging result is that the message is session start request, the MME sends indication information for indicating that TMGI conflict exists to the BM-SC; otherwise the MME indicates to the BM-SC the locally activated TMGI list.

When the network element is UE, the method of acquiring the activated TMGI list by the network element in step S102-1 in this embodiment may be implemented as follows:

step S17: the UE receives a TMGI list sent by an AS through an application layer signaling and stores the TMGI list, wherein the TMGI in the TMGI list is an activated TMGI;

Step S18: the UE sends the indication information of the activated TMGI to the AS through the application layer signaling, and the AS forwards the indication information to the BM-SC through an interface between the AS and the BM-SC.

In another optional implementation manner of this embodiment, the manner of determining, for the network element involved in step S104 of this embodiment, whether the TMGI is an activated TMGI and sending, according to the determination result, indication information for indicating whether the TMGI collides to the BM-SC may be implemented as follows:

step S104-4: the UE judges whether the TMGI used for identifying the MBMS bearer is matched with the TMGI in a locally stored TMGI list;

step S104-5: and if the judgment result is yes, the UE sends indication information for indicating that the TMGI conflict exists to the BM-SC through the AS.

From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method of the various embodiments of the present invention.

The embodiment also provides a processing device for the internet of vehicles service identifier, which is used for implementing the foregoing embodiment and the preferred implementation manner, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

Fig. 2 is a block diagram of a processing device of a service identifier of internet of vehicles according to an embodiment of the present invention, where the device is applied to a network element side, as shown in fig. 2, and the device includes: a receiving module 22, configured to receive a temporary mobile group identity TMGI for identifying an MBMS bearer; and the processing module 24 is coupled to the receiving module 22, and is configured to send, to the broadcast multicast service center BM-SC, indication information for indicating the locally activated TMGI, or determine whether the received TMGI is an activated TMGI, and send, to the BM-SC, indication information for indicating whether there is a TMGI collision according to a determination result, where the indication information is sent, by the network element, to the BM-SC directly or forwarded, by the network element, to the BM-SC through another network element.

Optionally, the apparatus in this embodiment further includes: an acquiring module, configured to acquire an activated TMGI list before determining whether a TMGI for identifying an MBMS bearer is an activated TMGI;

based on the acquisition module, the processing module 24 in the present embodiment includes: a first judging unit, configured to judge whether a TMGI for identifying an MBMS bearer matches a TMGI in a TMGI list; and the first sending unit is used for sending indication information for indicating that the TMGI conflict exists to the BM-SC for identifying the TMGI of the MBMS bearing when the judging result is yes.

It should be noted that, the network element in this embodiment includes at least one of the following: an application server AS, user equipment UE, a mobility management entity MME, a media broadcast multicast service gateway MBMS-GW, a multi-cell/multicast coordination entity MCE and a base station eNB.

Based on the network elements mentioned in the foregoing embodiment, the receiving module in this embodiment may further include: a first receiving unit, configured to receive a TMGI sent by an application server AS; and/or a second receiving unit, configured to receive the TMGI sent by the BM-SC. The first receiving unit is applied to a mobility management entity MME, a media broadcast multicast service gateway MBMS-GW, a multi-cell/multicast coordination entity MCE and a base station eNB side, and the second receiving unit is applied to an application server AS and user equipment UE.

When the network element is an AS, the acquiring module 22 in this embodiment includes: a first obtaining unit, configured to receive the TMGI lists notified by the multiple BM-SCs and store the TMGI lists, where a TMGI in the TMGI list is an activated TMGI; and a second sending unit, configured to send, to the BM-SC, indication information for indicating the activated TMGI list through an interface with the BM-SC.

In the case of a plurality of ases, the acquiring module 22 in this embodiment includes: a second obtaining unit, configured to receive TMGI lists notified by the multiple BM-SCs, where a TMGI in the TMGI list is an activated TMGI; and the sharing unit is used for sharing the TMGI list among the plurality of AS.

And when the network element is an MME, the acquiring module 22 in this embodiment includes: a third obtaining unit, configured to receive the TMGI lists notified by the multiple BM-SCs and store the TMGI lists, where a TMGI in the TMGI list is an activated TMGI; and a third transmitting unit for transmitting indication information for indicating the activated TMGI list to the BM-SC through the MBMS-GW.

Further, the processing module 24 in the present embodiment includes: a first receiving unit, configured to receive a session start request/session update request/session stop request message sent by a BM-SC, where the session start request/session update request/session stop request message carries a TMGI for identifying an MBMS bearer; a first judging unit, configured to judge whether a TMGI for identifying an MBMS bearer matches a TMGI in a locally stored TMGI list; a fourth sending unit, configured to send, when the determination result is yes and is a session start request message, indication information for indicating that there is a TMGI collision to the BM-SC; otherwise, the MME indicates to the BM-SC the locally activated TMGI list.

Wherein the locally activated TMGI does not include a TMGI deleted according to received session stop request, i.e., an updated TMGI list.

It should be noted that, the session update is used to indicate a service area or QoS update corresponding to the TMGI, and the session stop is used to indicate that the session is stopped, that is, the corresponding TMGI is not used any more.

And when the network element is UE, the acquiring module related in this embodiment includes: a fourth obtaining unit, configured to receive a TMGI list sent by the AS through an application layer signaling and store the TMGI list, where a TMGI in the TMGI list is an activated TMGI; and a fifth sending unit, configured to send, through application layer signaling, indication information of the activated TMGI to the AS, where the AS forwards the indication information to the TMGI through an interface with the BM-SC.

Optionally, the processing module 24 involved in this embodiment includes: a second judging unit, configured to judge whether a TMGI for activating an MBMS bearer matches a TMGI in a locally stored TMGI list; and a sixth sending unit, configured to send, to the same AS, indication information for indicating that there is a TMGI collision to the BM-SC when the determination result is yes.

It should be noted that each of the above modules may be implemented by software or hardware, and for the latter, it may be implemented by, but not limited to: the modules are all located in the same processor; alternatively, the modules are located in a plurality of processors, respectively.

In yet another embodiment of the present invention, the present embodiment further provides an apparatus comprising: the apparatus and/or alternative apparatus of any of the embodiments described above in relation to fig. 2.

The invention is illustrated below in connection with alternative embodiments of the invention;

the present optional embodiment provides a method for processing TMGI collision based on the above apparatus, and the following three ways are used to describe the present optional embodiment;

mode 1

In this manner, each BM-SC connected to the AS feeds back its assigned/released TMGI information to the AS so that the AS can learn which TMGI or TMGIs have been activated. The following describes this alternative embodiment in connection with an application scenario of this mode;

application scenario 1:

when a certain application server is connected to 1 or more MBMS core networks, namely: one AS is connected to 1 or more BM-SCs, each AS is connected with the BM-SCs through MB2 interfaces, each BM-SC is not connected (or two MBMS core networks are not connected), and the signaling interaction between the AS and the BM-SCs is performed to avoid the conflict of TMGIs; in this manner, the MBMS core network does not include the MME, because the MME is typically deployed separately.

In this application scenario, the steps of the method of this alternative embodiment include:

step S302: each BM-SC informs the AS of the list of TMGIs that have been allocated;

wherein the list comprises one or more allocated TMGIs in such a way that when an AS is connected to 1 or more BM-SCs, the AS can know all the allocated TMGIs.

Fig. 3 is a schematic diagram of an application server connected to 2 MBMS core networks according to an alternative embodiment of the present invention, where, AS shown in fig. 3, an AS is connected to 2 BM-SCs, BM-SC1 is allocated to TMGI list 1, BM-SC2 is allocated to TMGI list2, and the AS may learn that the allocated TMGIs are TMGI list 1 and TMGI list 2; based on this, the method steps of the present embodiment may be,

step S304: when the AS requests the BM-SC to allocate TMGIs again, carrying the allocated TMGI list and indicating the TMGIs AS allocated TMGIs;

step S306: BM-SC feeds back the allocated TMGI list;

the list may include only the TMGI list allocated this time, or may include all the TMGI lists allocated this time, that is, allocated this time and allocated before.

The release procedure in this alternative embodiment may also be that the BM-SC informs the AS of the released TMGI list after MBMS Session stop, so that the AS knows.

Application scenario 2:

when a certain MBMS core network is connected to a plurality of application servers, the BM-SC may directly allocate TMGIs and may operate according to the existing MBMS procedure.

Application scenario 3:

when multiple MBMS core networks are connected to multiple application servers, similar to application scenario 1 above, the activated TMGI is indicated to the BM-SC mainly by the AS, and it should be noted that: here, the TMGI collision means that it occurs in the same or partially the same broadcast area (service area, cell list), and if it is a different broadcast area, it is not in the scope of this alternative embodiment.

In addition, there is an interface between the plurality of ases through which signaling interactions (including the activated TMGIs) are performed to avoid TMGI collisions.

Mode 2

In this manner, there are multiple ases, and/or multiple MBMS core networks, but only one MME in a certain area, collision can be avoided by interaction between the BMSC and the MME. Such as: MME- - > TMGI list already allocated by BM-SC (this TMGI list has TMGI list allocated by BM-SC of all MBMS core networks).

But in a certain region MME: considering that the MME cannot generally localize, the other network elements of the MBMS (MBMS-GW/MCE) are generally connected to only one specific MME within a certain area, the MME receives the session start request message sent by the MBMS-GW, if the message contains an activated TMGI (including the same flow ID), the same broadcast area (including part of the same) and the same QoS, the MME sends a reject message response and indicates the reject reason in the response message: TMGI collision. Further MME may indicate the locally activated TMGI in a reject message, which is sent all the way to BM-SC, which reassigns the TMGI after receiving the reject message.

In this alternative embodiment, there are three ways for MME processing:

1) The MME receives MBMS session start request message, indicates the locally activated TMGI to all BM-SCs (via MBMS-GW) in a response message;

2) The MME receives MBMS session start request message and detects TMGI collision, then sends a rejection message and indicates the locally activated TMGI to all BM-SCs (via MBMS-GW) in the rejection message;

3) The MME periodically indicates to all BM-SCs (via MBMS-GW) the locally activated TMGI.

The MME determining that the TMGI collision is: the same TMGI (possibly including a flow ID), the same broadcast region (or part of the same), the same QoS, different MBMS session start request messages; if 1) the same TMGI, disparate broadcast regions (no partial or total overlap), are considered non-conflicting; 2) The MME may initiate MBMS session update procedure with the same TMGI, the same broadcast area, different QoS.

Mode 3

The terminal obtains information such AS TMGI, service start/end time, wireless frequency, service area, etc. through USD (user service description), if collision is found, if the same TMGI (same frequency, same service area) has different start time, the terminal sends indication information to the application server AS through the application layer: the TMGI collides and indicates the conflicted TMGI, and the AS sends indication information to all BM-SCs: the TMGI collide and indicate the TMGI where the collision occurred.

The method of this alternative embodiment includes the steps of:

step S402: some application server device requests TMGI allocation to 1 or more BM-SCs;

if an application server AS is connected to a plurality of BM-SCs, the AS may send a request message to one or more BM-SCs. The request includes at least: TMGI number. And a second step of: BM-SC distributes TMGI and feeds back to application server;

step S404: the BM-SC allocates the required TMGI for the AS, if the allocation cannot be performed, the BM-SC sends a rejection message response to the AS, otherwise, the BM-SC sends the allocated TMGI and the optional flow ID to the AS.

Wherein, 1) BM-SC can reserve a certain number of TMGIs for V2X service, then BM-SC selects a required number of TMGIs from reserved TMGIs and informs AS; the TMGI reserved in advance can be determined through signaling interaction between OAM or AS and BM-SC;

2) If there is an interface between BM-SCs, the BM-SCs are informed of the allocated TMGIs through interface signaling interaction, so that the TMGIs in the feedback message sent to the AS by each BM-SC are the TMGIs which are not allocated yet.

3) If the AS is connected to multiple BM-SCs, the AS may place the acquired TMGI in the request TMGI message when requesting a TMGI from each BM-SC, thereby avoiding the BM-SC from using an already allocated TMGI. Such as: when the AS applies for the TMGI to the other BM-SC2, the request message carries the allocated TMGI (TMGI 1, TIMG 2), and the BM-SC2 does not allocate the TMGI1 and the TMGI 2;

4) If the BM-SC determines that the requirement of the AS cannot be met, if the number of TMGIs does not meet the requirement or the BM-SC determines that the AS is not authorized, the BM-SC sends a rejection message response to the AS and indicates a rejection reason in the message: such AS an AS with a limited number of TMGIs or unauthorized.

The AS may multiplex multiple V2X services on one TMGI, and the AS informs the terminal through application layer signaling: and V2X service corresponding to the TMGI. If the terminal finds the TMGI conflict, the AS is indicated by the application layer.

Step S406: the application server initiates a request for activating MBMS bearing;

the AS sends a request message for activating MBMS bearing to the BM-SC, wherein the request message at least comprises: TMGI, further may include: broadcast area, V2X service start time, etc.

Step S408: judging whether the TMGIs conflict, if so, returning to the step S404 to reassign the TMGIs, otherwise, continuing to the step S410;

wherein the judging operation can be performed in one or more network elements, and the network elements capable of performing the judging include: AS, BM-SC, MBMS-GW, MME, MCE, eNB, terminal;

1) MBMS-GW: if the MBMS-GW has received a session start session start request message containing an activated TMGI (including the same flow ID), the same broadcast area (or part of the same) and the same QoS, the MBMS-GW sends a reject message response and indicates the reject reason in the response message: TMGI collision. The further MBMS-GW may indicate the locally activated TMGI in a reject message, and the BM-SC reassigns the TMGI after receiving the reject message.

2) MME: considering that the MME cannot generally localize, the other network elements of the MBMS (MBMS-GW/MCE) are generally connected to only one specific MME within a certain area, the MME receives the session start request message sent by the MBMS-GW, if the message contains an activated TMGI (including the same flow ID), the same broadcast area (including part of the same) and the same QoS, the MME sends a reject message response and indicates the reject reason in the response message: TMGI collision. Further MME may indicate the locally activated TMGI in a reject message, which is sent all the way to BM-SC, which upon receipt of the reject message reassigns the tmgi.mme may indicate to BM-SC (via MBM-GW) the activated TMGI upon receipt of MBMS session start request, or send an indication periodically.

3) MCE: the MCE includes both centralized and distributed deployments, regardless of which deployment the MCE has the same MBMS bearer context, then the MCE receives session start request message sent by the MME, if the message contains an activated TMGI (including the same flow ID), the same broadcast area (including part of the same), and the same QoS, then the MCE sends a reject message response and indicates the reject reason in the response message: TMGI collision. The further MCE may indicate in the reject message that the locally activated TMGI. Reject message is sent all the way to the BM-SC, which reassigns the TMGI after receiving the reject message.

4) eNB: receiving session start request message sent by MCE, if the message contains activated TMGI (including same flow ID) and same broadcast area (including partially same), eNB sends reject message response and indicates reject reason in response message: TMGI collision. The further eNB may indicate in a reject message that the locally activated TMGI.

5) And (3) a terminal: the terminal receives a V2X service description, such AS an ESG or USD, from the AS through application layer signaling, where the method at least includes: TMGI, V2X service start time. If the terminal receives the same TMGI but different service starting time, the terminal judges that TMGI conflict occurs, the terminal indicates the occurrence of TMGI conflict to the AS, and the AS reallocates the TMGI through the BM-SC.

6) AS: assuming that the AS is connected to a plurality of BM-SCs, the AS determines whether it is an activated MBMS bearer (through TMGI, broadcast area and QoS identification) according to the newly allocated TMGI (including flow ID) of the BM-SC, if so, determines that it is a TMGI collision, and then the AS requests to reallocate the TMGI to the BM-SC.

Step S410: and establishing the MBMS bearer.

Wherein the MBMS bearer comprises at least one of: MBSFN bearer, SC-PTM bearer.

Step S412: AS sends V2X service through MBMS bearer.

The terminal receives the required V2X service, and if a plurality of V2X services are multiplexed on one TMGI, the terminal application layer parses data corresponding to the TMGI and obtains the required V2X service therefrom.

The present alternative embodiments are further described and illustrated below in conjunction with specific embodiments of the present invention;

example 1

Fig. 4 is a schematic structural diagram of an alternative embodiment according to the present invention, AS shown in fig. 4, in this embodiment, only Local V2X AS is introduced to reuse existing MBMS and RAN network elements, and in addition, in several methods related to this embodiment, eNB may introduce LIPA/SIPTO functions, but in this embodiment, only downlink MBMS transmission is introduced, so that uplink enhancement possibly introduced in eNB is not involved.

In this alternative embodiment, (1) a Local V2X AS (also referred to AS: local Application layer, local V2X Application layer) is deployed in proximity to one or more closely located eNBs; (2) Local V2X AS connects to Global BM-SC through MB2 interface; (3) Local V2X AS may be RSU, AS may be configured on a fixed UE or eNB;

by means of this alternative embodiment, the network modification of reusing existing MBMS core networks and RANs is relatively small

Based on this, the method steps of this alternative embodiment include:

step S502: the local AS requests allocation of TMGI for V2X service;

step S504: BM-SC allocates TMGI for V2X and informs AS;

the TMGI here may be a reserved TMGI dedicated to the V2X service of the internet of vehicles, where the BM-SC allocates a required TMGI in the reserved TMGI according to the received AS request.

If no TMGI dedicated to V2X service is reserved, the BM-SC allocates TMGI which is not used yet;

if the BM-SC determines that the requirement of the AS cannot be met, if the number of TMGIs does not meet the requirement or the BM-SC determines that the AS does not use the TMGI authorized, the BM-SC sends a rejection message response to the AS and indicates a rejection reason in the message: such AS an AS with a limited number of TMGIs or unauthorized.

Step S506: the AS sends a request message for activating the MBMS bearer.

Step S508: and establishing the MBMS bearer.

Example two

Local V2X AS and Local MBMS core network thereof, and reuse of existing RAN

Fig. 5 is a schematic structural diagram according to a second alternative embodiment of the present invention, as shown in fig. 5, not only Local Application layer but also a Local MBMS core network node (including a Local BM-SC and a Local MBMS GW, but no Local MME is deployed anymore). From the perspective of RAN, there are two sets of MBMS core network elements, one set is the original Global MBMS providing a large area; one set is a localized Local MBMS core network that provides small areas.

In this optional embodiment, (1) a set of Local V2X AS and Local MBMS core networks are deployed near one or more enbs that are close in distance; (2) The set of Local V2X AS and Local MBMS core network control and send MBMS service to one or more eNBs with similar distances; (3) The set of Local V2X AS and Local MBMS core network reuses the existing MME; (4) Local V2X AS and Local MBMS core network provide V2X service; the Global AS and Global MBMS core network provide common MBMS service;

the method according to this alternative embodiment comprises the steps of:

step S602: the local AS requests allocation of TMGI for V2X service;

step S604: BM-SC allocates TMGI for V2X and informs AS;

the TMGI here may be a reserved TMGI dedicated to the V2X service of the internet of vehicles, where the BM-SC allocates a required TMGI in the reserved TMGI according to the received AS request.

If no TMGI dedicated to V2X service is reserved, the BM-SC allocates TMGI which is not used yet;

if the BM-SC determines that the requirement of the AS cannot be met, if the number of TMGIs does not meet the requirement or the BM-SC determines that the AS does not use the TMGI authorized, the BM-SC sends a rejection message response to the AS and indicates a rejection reason in the message: such AS an AS with a limited number of TMGIs or unauthorized.

Step S606: the AS sends a request message for activating the MBMS bearer.

Step S608: judging whether the TMGIs conflict, if so, returning to the step S604 to reassign the TMGIs, otherwise, continuing to the step S610;

the determination may be made at one or more network elements, where the network elements capable of making the determination include: AS, BM-SC, MBMS-GW, MME, MCE, eNB, terminal;

step S610: and establishing the MBMS bearer.

Example III

Introducing a set of Local V2X AS and a plurality of sets of Local MBMS core networks, and reusing the existing RAN

Fig. 6 is a schematic structural diagram of an alternative embodiment of the present invention, AS shown in fig. 6, in which a set of MBMS core networks (Local BM-SC and Local MBMS GW) is introduced into each eNB, and Local V2X AS is placed near 1 or more nearby enbs, where the Local V2X AS can control one or more enbs that are close in distance (the eNB has a set of independent MBMS core networks inside).

Existing MMEs and MCEs are reused, and a plurality of MBMS GWs are connected to each MME. Reuse of an existing MCE refers to: if the original MCE is centralized or distributed, it is still a centralized or distributed MCE, i.e.: the original MCE architecture is preserved.

In this alternative embodiment, (1) one set of Local V2X AS and multiple sets of Local MBMS core networks; (2) The set of Local V2X AS is connected with the plurality of sets of Local MBMS core networks through MB2 interfaces; (3) A Local V2X AS may control and send V2X packets to 1 or more neighboring enbs; (4) Reuse of existing MME and MCE

The method according to this alternative embodiment comprises the steps of:

step S702: the local AS requests allocation of TMGI for V2X service;

step S704: BM-SC allocates TMGI for V2X and informs AS;

the TMGI here may be a reserved TMGI dedicated to the V2X service of the internet of vehicles, where the BM-SC allocates a required TMGI in the reserved TMGI according to the received AS request.

If no TMGI dedicated to V2X service is reserved, the BM-SC allocates TMGI which is not used yet;

if the BM-SC determines that the requirement of the AS cannot be met, if the number of TMGIs does not meet the requirement or the BM-SC determines that the AS does not use the TMGI authorized, the BM-SC sends a rejection message response to the AS and indicates a rejection reason in the message: such AS an AS with a limited number of TMGIs or unauthorized.

Step S706: the AS sends a request message for activating the MBMS bearer.

Step S708: judging whether the TMGIs conflict, if so, returning to the step S704 to reassign the TMGIs, otherwise, continuing to the step S710;

the determination may be made at one or more network elements, where the network elements capable of making the determination include: AS, BM-SC, MBMS-GW, MME, MCE, eNB, terminal;

step S710: and establishing the MBMS bearer.

Example IV

Multiple Local AS+multiple Local MBMS core networks

Fig. 7 is a schematic diagram of a structure according to a fourth alternative embodiment of the present invention, AS shown in fig. 7, a set of MBMS core networks (Local BM-SC and Local MBMS GW) and Local V2X AS are introduced inside each eNB, and the Local V2X AS can only control one eNB. Existing MMEs and MCEs are reused, and a plurality of MBMS GWs are connected to each MME. Reuse of an existing MCE refers to: if the original MCE is centralized or distributed, it is still a centralized or distributed MCE, i.e.: the original MCE architecture is preserved.

In this alternative embodiment, (1) multiple sets of Local V2X AS and multiple sets of Local MBMS core networks; (2) Each eNB is provided with a set of Local V2X AS and a set of MBMS core network; (3) Reuse of existing MME and MCE

The method according to this alternative embodiment comprises the steps of:

step S802: local AS request allocation TMGI for V2X traffic;

step S804: BM-SC allocates TMGI for V2X and informs AS;

the TMGI here may be a reserved TMGI dedicated to the V2X service of the internet of vehicles, where the BM-SC allocates a required TMGI in the reserved TMGI according to the received AS request.

If no TMGI dedicated to V2X service is reserved, the BM-SC allocates TMGI which is not used yet;

if the BM-SC determines that the requirement of the AS cannot be met, if the number of TMGIs does not meet the requirement or the BM-SC determines that the AS does not use the TMGI authorized, the BM-SC sends a rejection message response to the AS and indicates a rejection reason in the message: such AS an AS with a limited number of TMGIs or unauthorized.

Step S806: AS sends request message for activating MBMS bearing;

step S808: judging whether the TMGIs conflict, if so, returning to the step S804 to reassign the TMGIs, otherwise, continuing to the step S810;

the determination may be made at one or more network elements, where the network elements capable of making the determination include: AS, BM-SC, MBMS-GW, MME, MCE, eNB, terminal;

step S810: and establishing the MBMS bearer.

Example five

Fig. 8 is a schematic structural diagram of a service identifier distribution system for internet of vehicles according to an alternative embodiment of the present invention, as shown in fig. 8, the system includes: an application server 801, a core network side device 802, a radio access network side device 803, and a terminal 804;

the core network side device 802 includes: BM-SC module 8021, MBMS-GW module 8022 and MME module 8023; the radio access network measurement device 803 includes: a base station module 8031 and an MCE module 8032; the terminal 804 includes a terminal receiving module 8041, a judging/processing module 8042, and a transmitting module 8043, wherein the terminal receiving module 8041 is configured to receive V2X service related information from the application server 801 through an application layer; the judging/processing module 8042 of the terminal 804 is configured to judge whether the TMGI collides; the sending module 8043 of the terminal 804 is configured to send TMGI collision indication information to the AS device 801. At least one of the above devices is responsible for detecting TMGI collisions and indicating collisions, and BM-SC module 8021 is responsible for the allocation of TMGIs.

Embodiments of the invention also a storage medium is provided. Alternatively, in the present embodiment, the above-described storage medium may be configured to store program code for performing the steps of:

step S1: in the process of activating a Multimedia Broadcast Multicast Service (MBMS) bearer, a network element receives a Temporary Mobile Group Identifier (TMGI) which is sent by an Application Server (AS) through a broadcast multicast service center (BM-SC) and used for identifying the MBMS bearer;

step S2: the network element sends indication information for indicating the locally activated TMGI to the BM-SC, or judges whether the TMGI for identifying the MBMS bearer is the activated TMGI, and sends indication information for indicating whether the TMGI conflict exists to the BM-SC according to the judging result, wherein the indication information is directly sent to the BM-SC by the network element or forwarded to the BM-SC by other network elements.

Alternatively, specific examples in this embodiment may refer to examples described in the foregoing embodiments and optional implementations, and this embodiment is not described herein.

It will be appreciated by those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a memory device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps within them may be fabricated into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (18)

1. A processing method of a service identifier of the Internet of vehicles, characterized by comprising the following steps:

the network element receives a temporary mobile group identifier TMGI for identifying the MBMS bearer;

the network element sends indication information for indicating a locally activated TMGI to a broadcast multicast service center (BM-SC), or judges whether the received TMGI is the activated TMGI, and sends indication information for indicating whether TMGI conflict exists to the BM-SC according to a judging result, wherein the indication information is directly sent to the BM-SC by the network element or forwarded to the BM-SC by other network elements;

before the network element determines whether the TMGI for identifying the MBMS bearer is an activated TMGI, the method includes: the network element acquires an activated TMGI list;

the network element determining whether the TMGI used for identifying the MBMS bearer is an activated TMGI includes: the network element judges whether the TMGI used for marking the MBMS bearer is matched with the TMGI in the TMGI list; and when the judgment result is yes, the network element sends indication information for indicating that the TMGI conflict exists to the BM-SC for identifying the TMGI of the MBMS bearing.

2. The method of claim 1, wherein the manner in which the network element receives the TMGI comprises at least one of:

the network element receives the TMGI sent by an application server AS;

and the network element receives the TMGI sent by the BM-SC.

3. The method of claim 1, wherein the step of determining the position of the substrate comprises, the network element comprises at least one of the following: an application server AS, user equipment UE, a mobility management entity MME, a multimedia broadcast multicast service gateway MBMS-GW, a multi-cell/multicast coordination entity MCE and a base station eNB.

4. The method of claim 3, wherein when the network element is an AS, the network element obtaining the activated TMGI list comprises:

the AS respectively receives a plurality of TMGI lists notified by the BM-SC and stores the TMGI lists, wherein the TMGI in the TMGI lists is an activated TMGI;

the AS sends indication information for indicating the activated TMGI list to the BM-SC through an interface with the BM-SC.

5. The method of claim 3, wherein when the network element is a plurality of ases, the network element obtaining an activated TMGI list of a plurality of BM-SCs connected to the network element comprises:

The AS respectively receives a plurality of TMGI lists notified by the BM-SC, wherein TMGI in the TMGI list is an activated TMGI;

the TMGI list is shared among a plurality of the ases.

6. The method of claim 1, wherein when the network element is an MME, the network element obtaining an activated TMGI list of a plurality of BM-SCs connected to the network element comprises:

the MME receives a plurality of TMGI lists notified by the BM-SC respectively, wherein TMGI in the TMGI list is activated TMGI;

the MME sends indication information for indicating the activated TMGI list to the BM-SC through the MBMS-GW.

7. The method of claim 6, wherein the network element determining whether the TMGI used to identify the MBMS bearer is an activated TMGI comprises:

the MME receives a session start request/session update request/session stop request message sent by the BM-SC, wherein the session start request/session update request/session stop request message carries a TMGI for marking the MBMS bearer;

the MME judges whether the TMGI used for identifying the MBMS bearer is matched with the TMGI in a TMGI list stored locally;

When the judging result is that the message is session start request, the MME sends indication information for indicating that TMGI conflict exists to the BM-SC; otherwise, the MME indicates to the BM-SC a locally activated TMGI list.

8. The method of claim 1, wherein when the network element is a UE, the network element obtaining the activated TMGI list comprises:

the UE receives a TMGI list sent by an AS through an application layer signaling and stores the TMGI list, wherein the TMGI in the TMGI list is an activated TMGI;

the UE sends the indication information of the activated TMGI to the AS through the application layer signaling, and the AS forwards the indication information to the BM-SC through an interface between the AS and the BM-SC.

9. The method of claim 8, wherein the network element determining whether the TMGI is an activated TMGI, and sending indication information to the BM-SC for indicating whether a TMGI collision is indicated according to a determination result comprises:

the UE judges whether the TMGI used for identifying the MBMS bearer is matched with the TMGI in a TMGI list stored locally;

and when the judgment result is yes, the UE sends indication information for indicating that TMGI conflict exists to the BM-SC through the AS.

10. The processing device of the service identifier of the internet of vehicles is applied to a network element side and is characterized by comprising the following components:

a receiving module, configured to receive a temporary mobile group identifier TMGI for identifying an MBMS bearer;

the processing module is used for sending indication information for indicating the locally activated TMGI to the broadcast multicast service center BM-SC by the network element, or judging whether the received TMGI is the activated TMGI, and sending indication information for indicating whether TMGI conflict exists to the BM-SC according to a judging result, wherein the indication information is directly sent to the BM-SC by the network element or forwarded to the BM-SC by other network elements;

the apparatus further comprises: an acquiring module, configured to acquire an activated TMGI list before determining whether a TMGI for identifying an MBMS bearer is an activated TMGI;

the processing module comprises: a first judging unit, configured to judge whether a TMGI for identifying an MBMS bearer matches a TMGI in the TMGI list;

and the first sending unit is used for sending indication information for indicating that the TMGI conflict exists to the BM-SC for identifying the TMGI of the MBMS bearing when the judging result is yes.

11. The apparatus of claim 10, wherein the receiving means comprises means for at least one of:

A first receiving unit, configured to receive the TMGI sent by the application server AS;

and the second receiving unit is used for receiving the TMGI sent by the BM-SC.

12. The apparatus of claim 10, wherein the network element comprises at least one of: an application server AS, user equipment UE, a mobility management entity MME, a media broadcast multicast service gateway MBMS-GW, a multi-cell/multicast coordination entity MCE and a base station eNB.

13. The apparatus of claim 12, wherein when the network element is an AS, the obtaining module comprises:

a first obtaining unit, configured to receive TMGI lists notified by a plurality of BM-SCs and store the TMGI lists, where a TMGI in the TMGI list is an activated TMGI;

and the second sending unit is used for sending indication information for indicating the activated TMGI list to the BM-SC through an interface with the BM-SC.

14. The apparatus of claim 12, wherein when the network element is a plurality of ases, the obtaining module comprises:

a second obtaining unit, configured to receive TMGI lists notified by a plurality of BM-SCs, where a TMGI in the TMGI list is an activated TMGI;

and the sharing unit is used for sharing the TMGI list among a plurality of AS.

15. The apparatus of claim 12, wherein when the network element is an MME, the obtaining module comprises:

a third obtaining unit, configured to receive the TMGI lists notified by the BM-SC and store the TMGI lists, where a TMGI in the TMGI list is an activated TMGI;

and a third sending unit, configured to send, to the BM-SC through the MBMS-GW, indication information for indicating the activated TMGI list.

16. The apparatus of claim 15, wherein the processing module comprises:

a first receiving unit, configured to receive a session start request/session update request/session stop request message sent by the BM-SC, where the session start request/session update request/session stop request message carries a TMGI for identifying the MBMS bearer;

a first judging unit, configured to judge whether a TMGI used for identifying the MBMS bearer matches a TMGI in a locally stored TMGI list;

a fourth sending unit, configured to send, when the determination result is yes and is a session start request message, indication information for indicating that there is a TMGI collision to the BM-SC; otherwise, a locally activated TMGI list is indicated to the BM-SC.

17. The apparatus of claim 12, wherein when the network element is a UE, the obtaining module comprises:

a fourth obtaining unit, configured to receive a TMGI list sent by an AS through an application layer signaling and store the TMGI list, where a TMGI in the TMGI list is an activated TMGI;

and a fifth sending unit, configured to send, through an application layer signaling, indication information of the activated TMGI to an AS, where the AS forwards the indication information to a BM-SC through an interface between the AS and the BM-SC.

18. The apparatus of claim 17, wherein the processing module comprises:

a second judging unit, configured to judge whether a TMGI used for activating the MBMS bearer matches with a TMGI in a locally stored TMGI list;

and a sixth sending unit, configured to send, when the determination result is yes, indication information for indicating that there is a TMGI collision to the same AS the AS to the BM-SC.