WO2017133277A1

WO2017133277A1 - Method and device for processing internet of vehicles service identity

Info

Publication number: WO2017133277A1
Application number: PCT/CN2016/103608
Authority: WO
Inventors: 许辉; 马子江; 吴蕴璐; 陈琳; 王亚英
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-02-04
Filing date: 2016-10-27
Publication date: 2017-08-10
Also published as: CN107040996B; CN107040996A

Abstract

Provided are a method and device for processing an Internet of Vehicles service identity. The method comprises: a network element receives a Temporary Mobile Group Identity (TGMI) used for identifying an MBMS bearer; the network element transmits indication information used for indicating a local activated TMGI to a broadcast multicast service center (BM-SC), or determines whether the received TGMI is an activated TMGI, and transmits, on the basis of the determination result, indication information used for indicating whether a TMGI conflict is present to the BM-SC, where the indication information is either transmitted directly by the network element to the BM-SC or forwarded to the BM-SC via other network elements. The present invention solves the problem in the prior art of TMGI conflict found in multiple BM-SC logical network elements assigning TMGIs when an MBMS bearer is employed for broadcasting a V2X service.

Description

Method and device for processing vehicle network service identification

Technical field

The present invention relates to the field of vehicle networking, and in particular to a method and apparatus for processing a service identifier of a vehicle network.

Background technique

Vehicle to Everything (V2X) refers to providing vehicle information through sensors, vehicle terminals and electronic tags mounted on vehicles, and adopts various communication technologies to realize Vehicle to Vehicle (V2V) and vehicles. Communicate with people (Vehicle to Pedestrian, V2P for short), Vehicle to Infrastructure (V2I), and use information on the information network platform to extract and share information. Conduct effective management and provide integrated services. The Road Side Unit (RSU) can receive vehicle requests, ensure that the vehicle accesses the Internet, and has the function of a gateway. In addition, it also has the functions of data calculation, storage, and forwarding.

In order to effectively utilize mobile network resources, 3GPP proposes a Multimedia Broadcast Multicast Service (MBMS), which is a technology for transmitting data from one data source to multiple target mobile terminals. The sharing of resources (including core network and access network) improves the utilization of network resources (especially air interface resources). 3GPP proposes a research topic of single-cell MBMS in LTE-A of R13, in which a single-cell MBMS service is transmitted on a physical downlink shared channel PDSCH. In the 3GPP network, the MBMS service uses the Temporary Mobile Group Identity (TMGI) identifier, and the TMGI is allocated by the network element BM-SC. The application server notifies the UE of relevant service description information through application layer signaling: such as TMGI, service start time, and the like.

For the security V2X service, the delay requirement is less than 100ms. The 3GPP is studying the localized core network, that is, the eNB itself or its vicinity is placed in the core network element. For the uplink, the localized eNB may use the LIPA or SIPTO function in the existing 3GPP protocol, and the downlink broadcast may place the core network of the MBMS (eg, MBMS-GW and BM-SC) in the eNB or in the vicinity of the eNB.

The 3GPP adopts the MBMS bearer broadcast V2X service Broadcast Multicast Service Centre. In order to ensure the delay requirement, the network element of the MBMS can be implemented locally, for example, the broadcast multicast service center (abbreviated as BM-SC) is implemented in the base station eNB. That is, multiple BM-SC logical network elements exist, and different BM-SCs may collide when assigning Temporary Mobile Group Identity (TMGI), for example, multiple BM-SCs allocate the same TMGI to the same area. . If a TMGI conflict occurs, the in-vehicle terminal in the conflict zone cannot determine the required TMGI, which may cause the V2X service to fail to receive.

In view of the above problems in the related art, there is currently no effective solution.

Summary of the invention

The embodiment of the present invention provides a method and a device for processing a service identifier of a vehicle network, so as to solve at least a TMGI conflict in the allocation of a temporary mobile group identifier by multiple BM-SC logical network elements when the MBMS bearer broadcast V2X service is used in the related art. The problem.

According to an aspect of the embodiments of the present invention, a method for processing a service identifier of a car network is provided, including: receiving, by a network element, a temporary mobility group identifier TMGI for identifying an MBMS bearer; and the network element to a broadcast multicast service center BM - the SC sends the indication information indicating the locally activated TMGI, or determines whether the received TMGI is the activated TMGI, and sends indication information indicating whether there is a TMGI conflict to the BM-SC according to the determination result, wherein The indication information is directly sent by the network element to the BM-SC or forwarded to the BM-SC by using other network elements.

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

Optionally, before the determining, by the network element, that the TMGI used to identify the MBMS bearer is an activated TMGI, the method includes: the network element acquiring an activated TMGI list; and determining, by the network element, a TMGI for identifying an MBMS bearer Whether it is an activated TMGI, the network element determines whether the TMGI used to identify the MBMS bearer matches the TMGI in the TMGI list; when the judgment result is yes, the network element is used to identify the MBMS bearer. The BM-SC of the TMGI transmits indication information indicating that there is a TMGI collision.

Optionally, the network element includes at least one of the following: an application server AS, a 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.

Optionally, when the network element is an AS, the acquiring, by the network element, the activated TMGI list includes: the AS respectively receiving a plurality of TMGI lists notified by the BM-SC, and saving the TMGI list, where The TMGI in the TMGI list is an activated TMGI; the AS sends indication information indicating the activated TMGI list to the BM-SC through an interface with the BM-SC.

Optionally, when the network element is a plurality of ASs, the acquiring, by the network element, the activated TMGI list in the multiple BM-SCs connected to the network element, the AS receiving the multiple BMs respectively a TMGI list notified by the SC, wherein the TMGI in the TMGI list is an activated TMGI; the TMGI list is shared among a plurality of the ASs.

Optionally, when the network element is an MME, the acquiring, by the network element, the activated TMGI list in the multiple BM-SCs connected to the network element, the MME receiving the multiple BM-SCs respectively a notified TMGI list, wherein the TMGI in the TMGI list is an activated TMGI; the MME sends indication information indicating the activated TMGI list to the BM-SC through the MBMS-GW.

Optionally, the determining, by the network element, whether the TMGI of the MBMS bearer is an activated TMGI, the MME receiving the 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; the MME determines whether the TMGI used to identify the MBMS bearer matches the TMGI in the locally saved TMGI list; When the judgment result is yes and is a session start request message, the MME sends indication information indicating that there is a TMGI conflict to the BM-SC; otherwise, the MME indicates the locally activated TMGI to the BM-SC. List.

Optionally, when the network element is a UE, the acquiring, by the network element, the activated TMGI list includes: Receiving, by the layer signaling, the TMGI list sent by the AS and saving the TMGI list, where the TMGI in the TMGI list is an activated TMGI; the UE sending the indication information of the activated TMGI to the AS by using application layer signaling The AS forwards the indication information to the BM-SC through an interface with the BM-SC.

Optionally, the determining, by the network element, whether the TMGI is an activated TMGI, and sending, to the BM-SC, the indication information for indicating whether the TMGI conflicts, according to the determination result, includes: determining, by the UE, that the MBMS is used to identify the MBMS. Whether the bearer TMGI matches the TMGI in the locally saved TMGI list; when the judgment result is yes, the UE sends the indication information indicating that the TMGI conflict exists to the BM-SC through the AS.

According to an aspect of the present invention, a device for processing a service identifier of a vehicle network is provided, which is applied to a network element side, and includes: a receiving module, configured to receive a temporary mobile group identifier TMGI for identifying an MBMS bearer; and a processing module And sending, by the network element, the indication information indicating the locally activated TMGI to the broadcast multicast service center BM-SC, or determining whether the received TMGI is the activated TMGI, and according to the determination result to the BM-SC The indication information for indicating whether there is a TMGI conflict is sent, where the indication information is directly sent by the network element to the BM-SC or is forwarded to the BM-SC by using another network element.

Optionally, the receiving module includes at least one of the following units: a first receiving unit configured to receive the TMGI sent by the application server AS, and a second receiving unit configured to receive the TMGI sent by the BM-SC.

Optionally, the device further includes: an obtaining module, configured to acquire an activated TMGI list before determining whether the TMGI for identifying the MBMS bearer is an activated TMGI; the processing module includes: a first determining unit, Set to determine whether the TMGI used to identify the MBMS bearer matches the TMGI in the TMGI list; the first sending unit is configured to send to the BM-SC for identifying the TMGI of the MBMS bearer when the judgment result is yes for Indicates that there is an indication of a TMGI conflict.

Optionally, the network element includes at least one of the following: an application server AS, a 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.

Optionally, when the network element is an AS, the acquiring module includes: a first acquiring unit, configured to respectively receive a plurality of BM-SC notified TMGI lists and save the TMGI list, where the TMGI list is The TMGI is an activated TMGI; the second transmitting unit is configured to use the interface with the BM-SC to indicate the indication information of the activated TMGI list to the BM-SC.

Optionally, when the network element is a plurality of ASs, the acquiring module includes: a second acquiring unit, configured to respectively receive a plurality of BM-SC notified TMGI lists, where the TMGI in the TMGI list is Activated TMGI; shared unit, set to share the TMGI list between multiple ASs.

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

Optionally, the processing module includes: a first receiving unit, configured to receive a session start sent by the BM-SC The request/session update request/session stop request message, wherein the session start request/session update request/session stop request message carries a TMGI for identifying the MBMS bearer; the first determining unit is configured to determine for identification Whether the TMGI carried by the MBMS matches the TMGI in the locally saved TMGI list; and the fourth sending unit is configured to send, to the BM-SC, a TMGI conflict when the judgment result is yes and is a session start request message. The indication information; otherwise, the BM-SC is indicated to the locally activated TMGI list.

Optionally, when the network element is a UE, the acquiring module includes: a fourth acquiring unit, configured to receive, by using application layer signaling, a TMGI list sent by the AS and save the TMGI list, where the TMGI list The TMGI is the activated TMGI; the fifth sending unit sends the indication information of the activated TMGI to the AS through the application layer signaling, wherein the AS forwards the information to the BM-SC through the interface between the AS and the BM-SC. Instructions.

Optionally, the processing module includes: a second determining unit, configured to determine whether the TMGI used to activate the MBMS bearer matches the TMGI in the locally saved TMGI list; and the sixth sending unit is configured to determine that the result is And transmitting, to the BM-SC, indication information indicating that there is a TMGI conflict.

According to still another aspect of the embodiments of the present invention, there is provided an apparatus comprising: the apparatus of any of the above.

According to still another embodiment of the present invention, a storage medium is also provided. The storage medium is arranged to store program code for performing the following steps:

Receiving a temporary mobile group identity TMGI for identifying an MBMS bearer; transmitting, to the broadcast multicast service center BM-SC, indication information indicating a locally activated TMGI, or determining whether the received TMGI is an activated TMGI, and And transmitting, to the BM-SC, indication information for indicating whether there is a TMGI conflict, where the indication information is directly sent by the network element to the BM-SC or forwarded to the BM-SC by using another network element. .

Optionally, the storage medium is further arranged to store program code for performing the following steps:

Obtaining the activated TMGI list; determining whether the TMGI used to identify the MBMS bearer is an activated TMGI, including: determining whether the TMGI used to identify the MBMS bearer matches the TMGI in the TMGI list; when the judgment result is yes, The indication information indicating that there is a TMGI collision is transmitted to the BM-SC for identifying the TMGI of the MBMS bearer.

In the embodiment of the present invention, in the process of activating the MBMS bearer request of the multimedia broadcast multicast service by using the TMGI, the network element receives the TMGI sent by the broadcast multicast service center BM-SC for activating the MBMS bearer, and further determines the network element. Whether the TMGI of the activated MBMS is the activated TMGI, and sends indication information for indicating whether there is a TMGI conflict to the BM-SC according to the judgment result, and the indication information is directly sent by the network element to the BM-SC or through other network elements. Forward to BM-SC. It can be seen that, in this embodiment, when the MBMS bearer broadcast V2X service is used in the related art, the BM-SC logical network element allocates a temporary mobile group identifier to have a TMGI conflict.

DRAWINGS

The drawings described herein are provided to provide a further understanding of the invention, which form a part of this application, The illustrative embodiments and the description thereof are illustrative of the invention and are not to be construed as limiting the invention. In the drawing:

1 is a flowchart of a method for processing a car network service identification according to an embodiment of the present invention;

2 is a structural block diagram of a processing apparatus for a vehicle network service identification according to an embodiment of the present invention;

3 is a schematic diagram of an application server connecting to two MBMS core networks according to an alternative embodiment of the present invention;

4 is a schematic structural view of an alternative embodiment 1 of the present invention;

Figure 5 is a schematic structural view of an alternative embodiment 2 of the present invention;

Figure 6 is a schematic structural view of an alternative embodiment 3 of the present invention;

Figure 7 is a schematic structural view of an alternative embodiment 4 according to the present invention;

FIG. 8 is a schematic structural diagram of a vehicle network service identification distribution system according to an alternative embodiment of the present invention.

detailed description

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

It is to be understood that the terms "first", "second" and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

In addition, the device involved in the embodiment includes: a terminal, a core network side device, an application server, and an access network side device; wherein the terminal may include at least one of the following: an on-board unit (On On-Board Unit, short for It is an OBU), a Roadside Unit (RSU), and a user equipment UE; the core network side equipment includes at least: BM-SC, MBMS-GW, and Mobility Management Entity (MME); - The SC is mainly responsible for allocating the TMGI, initiating the process of starting, updating, and stopping the MBMS session; the MBMS-GW is mainly responsible for establishing the control plane bearer to the MME and the user plane bearer to the eNB; the MME is responsible for establishing the multi-cell/multicast coordination entity ( Multi-cell/multicast Coordination Entity (MCE) is the control plane bearer. The core network can be deployed separately or locally in addition to the MME. The application server is used to request to activate the MBMS bearer, request the TMGI, and send/receive the V2X service. The application server and the BM-SC have an interface (such as an MB2 interface), and the application server communicates with the terminal through the application layer, and the application server can be separately used. Deployment or local deployment (as implemented through the application layer in the RSU). The access network side device includes at least an eNB and an MCE, wherein the eNB is mainly responsible for radio resource allocation of the V2X service, and receives/transmits the V2X service in the air interface, and the MCE is responsible for configuring the radio resource of the V2X service and determining the MBMS transmission mode (MBSFN or SC-PTM). ).

In this embodiment, a method for processing a vehicle network service identifier is provided. FIG. 1 is a flowchart of a method for processing a vehicle network service identifier according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:

Step S102: The network element receives the temporary mobility group identifier TMGI for identifying the MBMS bearer.

Step S104: The network element sends an indication to the broadcast multicast service center BM-SC for indicating the locally activated TMGI. Information, or determining whether the received TMGI is an activated TMGI, and transmitting, according to the determination result, indication information indicating whether there is a TMGI conflict to the BM-SC, where the indication information is directly sent or passed by the network element to the BM-SC Other network elements are forwarded to the BM-SC.

In the process of activating the MBMS bearer request of the multimedia broadcast multicast service by using the TMGI, the network element receives the TMGI sent by the broadcast multicast service center BM-SC for activating the MBMS bearer, and then the step S102 and the step S104. Determining, by the network element, whether the TMGI used to activate the MBMS bearer is an activated TMGI, and sending, according to the determination result, indication information indicating whether there is a TMGI conflict to the BM-SC, where the indication information is directly sent by the network element to the BM-SC or Forward to other BM-SCs through other network elements. It can be seen that, in this embodiment, when the MBMS bearer broadcast V2X service is used in the related art, the BM-SC logical network element allocates a temporary mobile group identifier to have a TMGI conflict.

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

Step S102-1: The network element acquires the activated TMGI list.

Step S102-2: The network element determines whether the TMGI used to identify the MBMS bearer is an activated TMGI, and includes: the network element determines whether the TMGI used to identify the MBMS bearer matches the TMGI in the TMGI list; when the judgment result is yes, The network element sends indication information indicating that there is a TMGI collision to the BM-SC of the TMGI for identifying the MBMS bearer.

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

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

Manner 1: The network element receives the TMGI sent by the application server AS.

Manner 2: The network element receives the TMGI sent by the BM-SC.

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

When the network element is an AS, the manner in which the network element involved in step S102-1 of the embodiment obtains the activated TMGI list can be implemented as follows:

Step S11: The AS receives the TMGI list notified by the multiple BM-SCs and saves the TMGI list, where the TMGI in the TMGI list is the activated TMGI;

Step S12: The AS sends indication information indicating the activated TMGI list to the BM-SC through the interface with the BM-SC.

When the network element is a plurality of ASs, the manner in which the network element involved in the step S102-1 of the embodiment obtains the activated TMGI list in the plurality of BM-SCs connected to the network element may be implemented as follows:

Step S13: The AS receives a plurality of TMGI lists notified by the BM-SC, where the TMGI in the TMGI list is an activated TMGI;

Step S14: Sharing the TMGI list among the plurality of ASs.

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

Step S15: The MME receives a plurality of TMGI lists notified by the BM-SC, where the TMGI in the TMGI list is an activated TMGI;

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

In another optional implementation manner of this embodiment, the method for determining, by the network element involved in the step S104, whether the TMGI of the MBMS bearer is the 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, where the session start request/session update request/session stop request message carries a TMGI for identifying the MBMS bearer.

Step S104-2: The MME determines whether the TMGI used to identify the MBMS bearer matches the TMGI in the locally saved TMGI list.

Step S104-3: When the judgment result is yes and is a session start request message, the MME sends indication information indicating that there is a TMGI collision to the BM-SC; otherwise, the MME indicates to the BM-SC the locally activated TMGI list.

When the network element is the UE, the manner in which the network element involved in step S102-1 in the embodiment obtains the activated TMGI list may be implemented as follows:

Step S17: The UE receives the TMGI list sent by the AS through the application layer signaling, and saves the TMGI list, where the TMGI in the TMGI list is the 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 the interface between the AS and the BM-SC.

In another optional implementation manner of this embodiment, the network element involved in step S104 in this embodiment determines whether the TMGI is an activated TMGI, and sends an indication to the BM-SC to indicate whether the TMGI conflicts according to the determination result. The way of information can be achieved by:

Step S104-4: The UE determines whether the TMGI used to identify the MBMS bearer matches the TMGI in the locally saved TMGI list.

Step S104-5: When the determination result is YES, the UE sends indication information indicating that there is a TMGI conflict to the BM-SC through the AS.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods of various embodiments of the present invention.

In the embodiment, a processing device for the vehicle network service identifier is provided, and the device is used to implement the foregoing embodiments and the preferred embodiments, and details are not described herein. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

2 is a structural block diagram of a processing apparatus for a vehicle network service identifier according to an embodiment of the present invention. The apparatus is applied to a network element side. As shown in FIG. 2, the apparatus includes: a receiving module 22 configured to receive an identifier for receiving MBMS. The temporary mobility group identifier TMGI is carried; the processing module 24 is coupled to the receiving module 22, and is configured to send, by the network element, indication information indicating the locally activated TMGI to the broadcast multicast service center BM-SC, or determine the received information. Whether the TMGI is the activated TMGI, and according to the judgment result, the indication information for indicating whether there is a TMGI conflict is sent to the BM-SC, where the indication information is directly sent by the network element to the BM-SC or through other network elements to the BM-SC. Forward.

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

Based on the obtaining module, the processing module 24 in this embodiment includes: a first determining unit, configured to determine whether the TMGI used to identify the MBMS bearer matches the TMGI in the TMGI list; and the first sending unit is configured to determine that the result is Yes, the indication information indicating that there is a TMGI collision is sent to the BM-SC for identifying the TMGI of the MBMS bearer.

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

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

When the network element is an AS, the acquiring module 22 in this embodiment includes: a first acquiring unit, configured to respectively receive a plurality of BM-SC notified TMGI lists and save the TMGI list, where the TMGI in the TMGI list is The activated TMGI; the second transmitting unit is configured to use the interface with the BM-SC to indicate to the BM-SC the indication information of the activated TMGI list.

When the network element is a plurality of ASs, the acquiring module 22 in this embodiment includes: a second acquiring unit, configured to respectively receive a plurality of BM-SC notified TMGI lists, where the TMGI in the TMGI list is activated. TMGI; shared unit, set to share a TMGI list between multiple ASs.

When the network element is the MME, the obtaining module 22 in this embodiment includes: a third acquiring unit, configured to respectively receive a plurality of BM-SC notified TMGI lists and save the TMGI list, where the TMGI in the TMGI list is The activated TMGI; the third sending unit is configured to send, by the MBMS-GW, indication information indicating the activated TMGI list to the BM-SC.

In addition, the processing module 24 in this embodiment 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 The request message carries a TMGI for identifying the MBMS bearer. The first determining unit is configured to determine whether the TMGI used to identify the MBMS bearer matches the TMGI in the locally saved TMGI list. The fourth sending unit is configured to determine that the result is yes. And when it is a session start request message, the indication information indicating that there is a TMGI conflict is sent to the BM-SC; otherwise, the MME indicates to the BM-SC the locally activated TMGI list.

The locally activated TMGI does not include the TMGI deleted according to the received session stop request, that is, the updated TMGI list.

It should be noted that the session update is used to indicate the 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 no longer used.

When the network element is the UE, the acquiring module involved in the embodiment includes: a fourth acquiring unit, configured to receive the TMGI list sent by the AS by using application layer signaling, and save the TMGI list, where the TMGI in the TMGI list is The activated TMGI; the fifth sending unit sends the indication information of the activated TMGI to the AS through the application layer signaling, wherein the AS forwards the indication information to the TMGI through the interface between the AS and the BM-SC.

Optionally, the processing module 24 involved in this embodiment includes: a second determining unit, configured to determine whether the TMGI used to activate the MBMS bearer matches the TMGI in the locally saved TMGI list; and the sixth sending unit is configured to be in When the determination result is YES, the same AS is sent to the BM-SC to indicate that there is a TMGI collision.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.

In another embodiment of the present embodiment, the present embodiment further provides an apparatus, including: the apparatus and/or the optional apparatus of any one of the foregoing embodiments of FIG.

The invention is exemplified below in conjunction with an alternative embodiment of the invention;

The present invention provides a method for processing a TMGI conflict based on the foregoing apparatus. The following describes the optional embodiment in the following three manners;

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 know which TMGI or TMGIs have been activated. The following describes the optional embodiment in combination with the application scenario of the mode;

Application scenario 1:

When an application server is connected to one or more MBMS core networks, that is, one AS is connected to one or more BM-SCs, and each AS and BM-SC are connected through an MB2 interface, and each BM- There is no connection between the SCs (or two MBMS core networks are not connected), and the signaling interaction between the AS and multiple BM-SCs is used to avoid the conflict of TMGI; it should be noted that in this mode, the MBMS core The network does not include the MME because the MME is generally deployed separately.

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

Step S302: Each BM-SC notifies the AS of the already assigned TMGI list;

Wherein, the list includes one or more allocated TMGIs, so that when the AS connects one or more BM-SCs, the AS can know all the allocated TMGIs.

3 is a schematic diagram of an application server connecting to two MBMS core networks according to an alternative embodiment of the present invention. As shown in FIG. 3, one AS is connected to two BM-SCs, and the BM-SC1 is assigned TMGI list 1, BM. If the SCGI is assigned to the TMGI list 2, the AS can know that the TMGIs that have been allocated are the TMGI list 1 and the TMGI list 2; based on this, the method steps of this embodiment may be,

Step S304: When the AS requests the BM-SC to allocate the TMGI again, it carries the already allocated TMGI list, and indicates that the TMGI is the allocated TMGI;

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

The list may include only the TMGI list allocated this time, and may also include all the allocated TMGI lists, that is, the current allocation and the previously allocated.

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

Application scenario 2:

When an MBMS core network is connected to multiple application servers, the BM-SC can directly allocate TMGI and work according to the existing MBMS process.

Application scenario 3:

When a plurality of MBMS core networks are connected to multiple application servers, similar to the above application scenario 1, the ASs are mainly indicated to the BM-SC by the AS. It should be noted that the TMGI conflicts herein are the same or partially the same. What happens in the broadcast area (service area, cell list), if it is a different broadcast area, is not in the scope of this alternative embodiment.

In addition, there are interfaces between multiple ASs through which signaling interactions (including activated TMGI) are performed to avoid TMGI collisions.

Mode 2

In this manner, there are multiple ASs, and/or multiple MBMS core networks, but only one MME in a certain area can avoid collision by the interaction between the BMSC and the MME. For example: MME--> BM-SC has allocated TMGI list (the TMGI list has TMGI list allocated by all BM-SCs of MBMS core network).

However, in a certain area MME: considering that the MME is generally not localized, the other network elements (MBMS-GW/MCE) of the MBMS are generally connected to only one specific MME in a certain area, and the MME receives the session sent by the MBMS-GW. Start request message, if the message contains the activated TMGI (including the same flow ID), the same broadcast area (including partial same) and the same QoS, the MME sends a rejection message response, and indicates the reason for rejection in the response message: TMGI conflict. The further MME may indicate the locally activated TMGI in the reject message, the reject message is sent to the BM-SC all the time, and the BM-SC re-allocates the TMGI after receiving the reject message.

In this alternative embodiment, there are three ways to process the MME:

1) The MME receives the MBMS session start request message, and indicates to the BM-SC (through the MBMS-GW) the locally activated TMGI in the response message;

2) The MME receives the MBMS session start request message and detects the TMGI collision, sends a reject message, and indicates to the BM-SC (through the MBMS-GW) the locally activated TMGI in the reject message;

3) The MME periodically indicates to the local BM-SC (through the MBMS-GW) the locally activated TMGI.

It should be noted that the MME determines that the TMGI conflict refers to: the same TMGI (may include the flow ID), the same broadcast area (or part of the same), the same QoS, different MBMS session start request messages; if 1) the same TMGI The completely different broadcast areas (without partial or full overlap) are considered to be non-conflicting; 2) the same TMGI, the same broadcast area, and different QoS, the MME may initiate the MBMS session update procedure.

Mode 3

The terminal obtains TMGI, service start/end time, radio frequency, service area and other information through USD (user service description). If a conflict is found, such as the same TMGI (same frequency, same service area) has different start times, the terminal The application server AS sends the indication information through the application layer: TMGI conflict, and indicates the conflicting TMGI, the AS sends indication information to all BM-SCs: TMGI conflict, and indicates the conflicting TMGI.

In combination with the above three methods, the method steps of the alternative embodiment include:

Step S402: an application server device requests TMGI allocation from one or more BM-SCs;

If the application server AS is connected to multiple BM-SCs, the AS may send a request message to one or more BM-SCs. The request includes at least: a number of TMGIs. Step 2: BM-SC allocates TMGI and feeds back the application server;

Step S404: The BM-SC allocates the required TMGI to the AS, and if it cannot be allocated, the BM-SC sends a rejection to the AS. The message responds, otherwise the BM-SC sends the assigned TMGI and optional flow ID to the AS.

1) BM-SC can reserve a certain number of TMGIs for V2X services, then BM-SC selects the required number of TMGIs in the reserved TMGI and notifies the AS; the reserved TMGI can pass OAM or AS and BM-SC The signaling interaction between the two is determined;

2) If there is an interface between the BM-SCs, the BM-SCs notify the allocated TMGI through the interface signaling interaction, so that the TMGI in the feedback message sent by each BM-SC to the AS is the TMGI that has not been allocated.

3) If the AS is connected to multiple BM-SCs, the AS may place the acquired TMGI in the request TMGI message when requesting TMGI from each BM-SC, thereby preventing the BM-SC from using the already allocated TMGI. For example, an AS is connected to both BM-SC1 and BMS-SC2. BM-SC1 has already allocated several TMGIs (eg TMGI1, TMGI2) and fed back to the AS through the MB2 interface, when the AS is directed to another BM-SC2. When the TMGI is applied, if the allocated TMGI (TMGI1, TIMG2) is carried in the request message, the BM-SC2 no longer allocates the TMGI1 and the TMGI2;

4) If the BM-SC determines that the requirements of the AS cannot be met, such as if the number of TMGI does not meet the requirement or the BM-SC determines that the AS is not authorized, the BM-SC sends a reject message response to the AS, and indicates the reason for the rejection in the message: such as the number of TMGIs Limited or unlicensed AS.

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

Step S406: The application server initiates an activation of the MBMS bearer request.

The AS sends an activated MBMS bearer request message to the BM-SC, where the request message includes at least: TMGI, and may further include: a broadcast area, a V2X service start time, and the like.

Step S408: determining whether the TMGI conflicts, and if so, returning to step S404 to re-allocate the TMGI, otherwise proceeding to step S410;

The determining may be performed on one or more network elements, where the network elements that can be determined include: AS, BM-SC, MBMS-GW, MME, MCE, eNB, and terminal;

1) MBMS-GW: If the MBMS-GW has received a session start session start request message containing the activated TMGI (including the same flow ID), the same broadcast area (or part of the same) and the same QoS, the MBMS-GW sends Reject the message response and indicate the reason for the rejection in the response message: TMGI conflict. Further MBMS-GW may indicate the locally activated TMGI in the reject message, and the BM-SC re-allocates the TMGI after receiving the reject message.

2) MME: Considering that the MME is generally not localized, the other network elements (MBMS-GW/MCE) of the MBMS are generally connected to only one specific MME in a certain area, and the MME receives the session start request message sent by the MBMS-GW. If the message contains the activated TMGI (including the same flow ID), the same broadcast area (including partial same), and the same QoS, the MME sends a reject message response and indicates the reason for the rejection in the response message: TMGI conflict. The further MME may indicate the locally activated TMGI in the reject message, and the reject message is sent all the way to BM-SC, the BM-SC re-allocates the TMGI after receiving the reject message. The MME may indicate the activated TMGI to the BM-SC (via the MBM-GW) upon receiving the MBMS session start request, or periodically send an indication.

3) MCE: MCE includes both centralized and distributed deployment. Regardless of the deployment, the MCE has the same MBMS bearer context. The MCE receives the session start request message sent by the MME. If the message contains the activated TMGI (including the same Flow ID), the same broadcast area (including partial same) and the same QoS, the MCE sends a reject message response, and indicates the reason for the rejection in the response message: TMGI conflict. The further MCE may indicate in the reject message that the locally activated TMGI. The reject message is sent to the BM-SC all the time, and the BM-SC re-allocates the TMGI after receiving the reject message.

4) eNB: Receive the session start request message sent by the MCE. If the message includes the activated TMGI (including the same flow ID) and the same broadcast area (including the same part), the eNB sends a reject message response, and in the response message. Indicate the reason for rejection: TMGI conflict. Further eNB may indicate in the reject message that the locally activated TMGI. The reject message is sent to the BM-SC all the time, and the BM-SC re-allocates the TMGI after receiving the reject message.

5) Terminal: The terminal receives the V2X service description, such as ESG or USD, from the AS through application layer signaling, where at least: TMGI, V2X service start time. If the terminal receives the same TMGI but different service start times, the terminal determines that a TMGI collision occurs, the terminal indicates to the AS that a TMGI collision occurs, and the AS re-allocates the TMGI through the BM-SC.

6) AS: Assume that the AS is connected to multiple BM-SCs, and the AS determines whether it is an activated MBMS bearer (via TMGI, broadcast area, and QoS identifier) according to the newly allocated TMGI (including flow ID) of the BM-SC. Determined to be a TMGI conflict, then the AS requests the BM-SC to reassign the TMGI.

Step S410: Establish an MBMS bearer.

The MBMS bearer includes at least one of the following: an MBSFN bearer, and an SC-PTM bearer.

Step S412: The AS sends the V2X service through the MBMS bearer.

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

The present optional embodiment is further illustrated and explained below in conjunction with the specific embodiments of the present invention;

Embodiment 1

FIG. 4 is a schematic structural diagram of an alternative embodiment of the present invention. As shown in FIG. 4, only the Local V2X AS is introduced in the embodiment, and the existing MBMS and RAN network elements are reused. In addition, the present embodiment relates to In several methods, the eNB may introduce functions such as LIPA/SIPTO, but only the downlink MBMS transmission is introduced in this embodiment, so the uplink enhancement that may be introduced in the eNB is not involved.

In this alternative embodiment, (1) deploying a Local V2X AS (also referred to as: Local Application Layer, Local V2X Application layer) in the vicinity of one or more eNBs having similar distances; (2) Local V2X AS passing MB2 The interface is connected to the Global BM-SC; (3) the Local V2X AS may be an RSU, such as may be configured on a fixed UE or an eNB;

By means of this alternative embodiment, the reuse of the existing MBMS core network and the RAN are relatively small changes to the network.

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

Step S502: The local AS requests to allocate a TMGI for the V2X service;

Step S504: The BM-SC allocates a TMGI for the V2X and notifies the AS;

The TMGI here may be a TMGI dedicated to the Internet of Vehicles V2X service reserved in advance, and the BM-SC allocates the required TMGI in the reserved TMGI according to the received AS request.

If the TMGI dedicated to the V2X service is not reserved, the BM-SC allocates the unused TMGI;

If the BM-SC determines that the requirements of the AS cannot be met, such as if the number of TMGI does not meet the requirement or the BM-SC determines that the AS is not authorized to use the TMGI, the BM-SC sends a reject message response to the AS, and indicates the reason for the rejection in the message: such as the number of TMGIs Limited or unlicensed AS.

Step S506: The AS sends an Activate MBMS Bearer Request message.

Step S508: Establish an MBMS bearer.

Embodiment 2

A set of Local V2X AS and its Local MBMS core network, reuse existing RAN

FIG. 5 is a schematic structural diagram of an optional embodiment 2 of the present invention. As shown in FIG. 5, not only a Local Application layer but also a Local MBMS core network node (including: Local BM-SC and Local MBMS GW, but not Then deploy Local MME). From the perspective of the RAN, there are two sets of MBMS core network elements, one is the original Global MBMS that provides large areas; and the other is a localized Local MBMS core network that provides small areas.

In this alternative embodiment, (1) deploying a set of Local V2X AS and Local MBMS core networks in the vicinity of one or more eNBs with similar distances; (2) controlling a set of Local V2X AS and Local MBMS core networks Sending MBMS services to one or more eNBs with similar distances; (3) the local V2X AS and Local MBMS core networks reuse existing MMEs; (4) Local V2X AS and Local MBMS core networks provide V2X services; Global AS And the Global MBMS core network provides common MBMS services;

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

Step S602: The local AS requests to allocate a TMGI for the V2X service.

Step S604: The BM-SC allocates a TMGI for the V2X and notifies the AS;

If the BM-SC determines that the requirements of the AS cannot be met, such as the number of TMGI does not meet the demand or the BM-SC determines that the AS is not Authorized to use TMGI, the BM-SC sends a reject message response to the AS and indicates the reason for the rejection in the message: such as a limited number of TMGIs or an unauthorized AS.

Step S606: The AS sends an Activate MBMS Bearer Request message.

Step S608: determining whether the TMGI is in conflict, if yes, returning to step S604 to re-allocate the TMGI, otherwise proceeding to step S610;

The determining may be performed on one or more network elements, and the network elements that can be judged include: AS, BM-SC, MBMS-GW, MME, MCE, eNB, and terminal;

Step S610: Establish an MBMS bearer.

Embodiment 3

Introduce a set of Local V2X AS and multiple sets of Local MBMS core networks to reuse existing RANs

6 is a schematic structural diagram of an optional embodiment 3 of the present invention. As shown in FIG. 6, a set of MBMS core networks (Local BM-SC and Local MBMS GW) are introduced in each eNB, and a Local V2X AS is placed in one. Or near a plurality of similar eNBs, the Local V2X AS can control one or more eNBs with similar distances (the eNB has a set of independent MBMS core networks).

The existing MME and MCE are reused, and multiple MBMS GWs are connected to each MME. Reusing an existing MCE means that if the original MCE is centralized or distributed, it is still a centralized or distributed MCE, that is, the original MCE architecture is retained.

In this alternative embodiment, (1) a set of Local V2X AS and multiple sets of Local MBMS core networks; (2) a set of Local V2X AS and multiple sets of Local MBMS core networks are connected through MB2 interfaces; (3) a set of Local The V2X AS can control and send V2X packets to one or more neighboring eNBs; (4) reuse existing MMEs and MCEs

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

Step S702: The local AS requests to allocate a TMGI for the V2X service.

Step S704: The BM-SC allocates a TMGI for the V2X and notifies the AS;

Step S706: The AS sends an Activate MBMS Bearer Request message.

Step S708: determining whether the TMGI is in conflict, if yes, returning to step S704 to re-allocate the TMGI, otherwise proceeding to step S710;

Step S710: Establish an MBMS bearer.

Embodiment 4

Multiple sets of local AS+ multiple sets of Local MBMS core network

FIG. 7 is a schematic structural diagram of an optional embodiment 4 of the present invention. As shown in FIG. 7, each eNB internally introduces a set of MBMS core networks (Local BM-SC and Local MBMS GW) and Local V2X AS, the Local V2X. The AS can only control one eNB. The existing MME and MCE are reused, and multiple MBMS GWs are connected to each MME. Reusing an existing MCE means that if the original MCE is centralized or distributed, it is still a centralized or distributed MCE, that is, the original MCE architecture is retained.

In this alternative embodiment, (1) multiple sets of Local V2X AS and multiple sets of Local MBMS core networks; (2) a set of Local V2X AS and a set of MBMS core networks are deployed on each eNB; (3) reuse Existing MME and MCE

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

Step S802: The local AS requests to allocate a TMGI for the V2X service;

Step S804: The BM-SC allocates a TMGI for the V2X and notifies the AS;

Step S806: The AS sends an activate MBMS bearer request message.

Step S808: determining whether the TMGI is in conflict, if yes, returning to step S804 to re-allocate the TMGI, otherwise proceeding to step S810;

Step S810: Establish an MBMS bearer.

Embodiment 5

FIG. 8 is a schematic structural diagram of a car network service identification distribution system 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: a BM-SC module 8021, an MBMS-GW module 8022, and an 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. The determining/processing module 8042 and the sending module 8043, the terminal receiving module 8041 is configured to receive V2X service related information from the application server 801 through the application layer; the determining/processing module 8042 of the terminal 804 is configured to determine whether the TMGI conflicts; the sending module 8043 of the terminal 804 It is set to transmit TMGI conflict indication information to the AS device 801. At least one of the above devices is responsible for detecting TMGI collisions and indicating collisions, and the BM-SC module 8021 is responsible for the allocation of TMGIs.

Embodiments of the present invention also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

Step S1: In the process of activating the MBMS bearer of the multimedia broadcast multicast service, the network element receives the temporary mobile group identifier TMGI sent by the application server AS through the broadcast multicast service center BM-SC for identifying the MBMS bearer;

Step S2: The network element sends the indication information indicating the locally activated TMGI to the BM-SC, or determines whether the TMGI used to identify the MBMS bearer is the activated TMGI, and sends the indication to the BM-SC according to the determination result. Whether there is indication of TMGI collision, wherein the indication information is directly sent by the network element to the BM-SC or forwarded to the BM-SC by other network elements.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

In the process of activating the MBMS bearer request of the multimedia broadcast multicast service by the TMGI in the embodiment of the present invention, the network element receives the TMGI sent by the broadcast multicast service center BM-SC for activating the MBMS bearer, and then the network element determines to activate the MBMS. Whether the bearer TMGI is the activated TMGI, and according to the judgment result, the indication information for indicating whether there is a TMGI conflict is sent to the BM-SC, and the indication information is directly sent by the network element to the BM-SC or through other network elements to the BM- SC Forward. It can be seen that, in this embodiment, when the MBMS bearer broadcast V2X service is used in the related art, the BM-SC logical network element allocates a temporary mobile group identifier to have a TMGI conflict.

Claims

A method for processing a vehicle network service identifier, comprising:

The network element receives the temporary mobility group identifier TMGI for identifying the MBMS bearer;

Sending, by the network element, the indication information indicating the locally activated TMGI to the broadcast multicast service center BM-SC, or determining whether the received TMGI is the activated TMGI, and sending the used information to the BM-SC according to the determination result. The indication information indicating whether there is a TMGI conflict, wherein the indication information is directly sent by the network element to the BM-SC or forwarded to the BM-SC by using another network element.
The method of claim 1, wherein the manner in which the network element receives the TMGI comprises at least one of the following:

Receiving, by the network element, the TMGI sent by the application server AS;

The network element receives the TMGI sent by the BM-SC.
The method of claim 2, wherein

Before the determining, by the network element, that the TMGI for the MBMS bearer is the activated TMGI, the method includes: obtaining, by the network element, the activated TMGI list;

Determining, by the network element, whether the TMGI of the MBMS bearer is an activated TMGI, the determining, by the network element, whether the TMGI used to identify the MBMS bearer matches the TMGI in the TMGI list; The network element sends indication information indicating that there is a TMGI collision to the BM-SC of the TMGI for identifying the MBMS bearer.
The method according to claim 3, wherein the network element comprises at least one of: an application server AS, a user equipment UE, a mobility management entity MME, a multimedia broadcast multicast service gateway MBMS-GW, multi-cell/multicast coordination Entity MCE, base station eNB.
The method of claim 4, wherein when the network element is an AS, the acquiring, by the network element, the activated TMGI list comprises:

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

The AS sends indication information indicating the activated TMGI list to the BM-SC through an interface with the BM-SC.
The method of claim 4, wherein when the network element is a plurality of ASs, the acquiring, by the network element, the activated TMGI list in the plurality of BM-SCs connected to the network element comprises:

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

The TMGI list is shared among a plurality of the ASs.
The method according to claim 3, wherein, when the network element is an MME, the acquiring, by the network element, the activated TMGI list in the plurality of BM-SCs connected to the network element comprises:

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

The MME sends indication information indicating the activated TMGI list to the BM-SC through the MBMS-GW.
The method according to claim 7, wherein the determining, by the network element, whether the TMGI for the MBMS bearer is an activated TMGI comprises:

The MME receives the 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 the identifier for identifying the MBMS bearer. TMGI;

Determining, by the MME, whether the TMGI used to identify the MBMS bearer matches the TMGI in the locally saved TMGI list;

When the judgment result is yes and is a session start request message, the MME sends indication information indicating that there is a TMGI conflict to the BM-SC; otherwise, the MME indicates the locally activated TMGI to the BM-SC. List.
The method of claim 3, wherein when the network element is a UE, the acquiring, by the network element, the activated TMGI list comprises:

Receiving, by the application layer signaling, the TMGI list sent by the AS and saving the TMGI list, where 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 the interface between the AS and the BM-SC.
The method according to claim 9, wherein the network element determines whether the TMGI is an activated TMGI, and sends indication information for indicating whether the TMGI conflicts to the BM-SC according to the determination result, including:

Determining, by the UE, whether the TMGI used to identify the MBMS bearer matches the TMGI in the locally saved TMGI list;

When the determination result is yes, the UE sends, by using the AS, indication information indicating that there is a TMGI conflict to the BM-SC.
A processing device for a vehicle network service identifier is applied to a network element side, and includes:

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

a processing module, configured to send, to the broadcast multicast service center BM-SC, the network element to indicate that the local activation is performed. The indication information of the TMGI, or whether the received TMGI is an activated TMGI, and sending, according to the determination result, indication information indicating whether there is a TMGI conflict to the BM-SC, where the indication information is directly from the network element Sending to the BM-SC or forwarding to the BM-SC through other network elements.
The apparatus of claim 11, wherein 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;

The second receiving unit is configured to receive the TMGI sent by the BM-SC.
The device according to claim 12, wherein

The device further includes: an obtaining module, configured to obtain an activated TMGI list before determining whether the TMGI for identifying the MBMS bearer is an activated TMGI;

The processing module includes: a first determining unit, configured to determine whether a TMGI used to identify an MBMS bearer matches a TMGI in the TMGI list;

The first transmitting unit is configured to, when the determination result is YES, transmit indication information indicating that there is a TMGI collision to the BM-SC for identifying the TMGI of the MBMS bearer.
The apparatus according to claim 13, wherein said network element comprises at least one of: an application server AS, a user equipment UE, a mobility management entity MME, a media broadcast multicast service gateway MBMS-GW, a multi-cell/multicast coordination entity MCE, base station eNB.
The apparatus according to claim 14, wherein when the network element is an AS, the obtaining module comprises:

a first acquiring unit, configured to receive a plurality of BM-SC notified TMGI lists and save the TMGI list, wherein the TMGI in the TMGI list is an activated TMGI;

The second sending unit is configured to use the interface with the BM-SC to indicate the indication information of the activated TMGI list to the BM-SC.
The apparatus according to claim 14, wherein when the network element is a plurality of ASs, the obtaining module comprises:

a second acquiring unit, configured to receive a plurality of BM-SC notified TMGI lists, wherein the TMGI in the TMGI list is an activated TMGI;

A shared unit, configured to share the TMGI list between a plurality of ASs.
The apparatus according to claim 14, wherein when the network element is an MME, the acquiring module comprises:

a third acquiring unit, configured to receive a plurality of TMGI lists notified by the BM-SC and save the TMGI list, where the TMGI in the TMGI list is an activated TMGI;

The third sending unit is configured to send, by the MBMS-GW, indication information indicating the activated TMGI list to the BM-SC.
The apparatus of claim 17 wherein said processing module comprises:

The first receiving unit is 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 an identifier for The TMGI carried by the MBMS;

a first determining unit, configured to determine whether the TMGI used to identify the MBMS bearer matches the TMGI in the locally saved TMGI list;

a fourth sending unit, configured to: when the determination result is yes and is a session start request message, send indication information indicating that a TMGI conflict exists to the BM-SC; otherwise, indicate to the BM-SC that the local activation is TMGI list.
The apparatus according to claim 14, wherein when the network element is a UE, the acquiring module comprises:

a fourth acquiring unit, configured to receive, by using application layer signaling, a TMGI list sent by the AS and save the TMGI list, where the TMGI in the TMGI list is an activated TMGI;

The fifth sending unit sends the indication information of the activated TMGI to the AS through the application layer signaling, where the AS forwards the indication information to the BM-SC through an interface between the AS and the BM-SC.
The apparatus of claim 19, wherein the processing module comprises:

a second determining unit, configured to determine whether the TMGI used to activate the MBMS bearer matches the TMGI in the locally saved TMGI list;

The sixth transmitting unit is configured to, when the determination result is YES, send the indication information indicating that the TMGI conflict exists to the BM-SC to the AS.
An apparatus comprising: the apparatus of any one of claims 11 to 20.