WO2017133467A1

WO2017133467A1 - Method for implementing internet of vehicles service and localized network architecture

Info

Publication number: WO2017133467A1
Application number: PCT/CN2017/071647
Authority: WO
Inventors: 吴蕴璐; 陈琳
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-02-04
Filing date: 2017-01-19
Publication date: 2017-08-10
Also published as: CN107040898A

Abstract

Disclosed are a method for implementing an Internet of Vehicles service and a localized network architecture, comprising the distinction of broadcast areas for a V2X message: if the V2X message is broadcasted in a cell under an adjacent base station governed by a local MBMS, the establishment of an MBMS bearer to the adjacent base station is triggered; and when the MBMS bearer for the V2X broadcast areas is established, a downlink user-side data path broadcasted by the cell under the adjacent base station and governed by the local MBMS for the V2X message is: a local V2X server -> a first entity > the adjacent base station. Embodiments of the present invention satisfy a latency requirement of an Internet of Vehicles service, particularly a V2V/V2I/V2P service.

Description

Method for realizing vehicle networking business and localized network architecture

Technical field

Embodiments of the present invention relate to, but are not limited to, modern vehicle technologies, and in particular, to a method for implementing a car networking service and a localized network architecture.

Background technique

With the rapid development of economy and society, China's automobile ownership has grown rapidly, and road traffic accidents have occurred frequently. It has become one of the important factors affecting China's public security in recent years. Road traffic safety has become a basic factor affecting social harmony and improving people's livelihood. One of the problems. China urgently needs to improve traffic safety from various aspects such as technology, policy and education. Among them, improving vehicle safety design is an important part of it. The technologies to improve vehicle safety are mainly divided into passive safety technology and active safety technology. Among them, passive safety technology is used to protect people and objects inside and outside the vehicle after an accident; active safety technology is used to prevent and reduce accidents in vehicles and to avoid injury. Active safety technology is the focus and trend of modern vehicle safety technology development.

Communication-based collision warning system has become a new way of thinking for countries to solve road traffic safety problems. The communication-based collision warning system realizes real-time information interaction between the vehicle, the vehicle and the roadside infrastructure by using advanced wireless communication technology and a new generation of information processing technology, and informs each other of the current state (including the position and speed of the vehicle, Acceleration, driving route, etc.) and the knowledge of road environment information, collaboratively aware of road hazard conditions, in order to provide a variety of collision warning information in time to prevent road traffic safety accidents.

V2X (Vehicle-to-Everything Communications) refers to the provision of vehicle information through sensors, vehicle terminals and electronic tags mounted on vehicles, and uses various communication technologies to realize vehicle-to-vehicle communication (V2V, Vehicle-to-Vehicle). Communication), Vehicle-to-Pedestrian Communications (V2P), Vehicle-to-Infrastructure Communications (V2I, Vehicle-to-Network Communications), V2N (Vehicle-to-Network Communications) communication, And on the information network platform, the information is extracted and shared effectively, and the vehicle is effectively controlled and provided with comprehensive services.

Currently, 3GPP is discussing V2X based on Long Term Evolution (LTE). According to the current definition of 3GPP, a V2X service is a kind of transmitting or receiving user equipment (UE) participating in a V2V application. Communication services through 3GPP transmission. Based on the other party participating in the communication, the V2X service can be further divided into a V2V service, a V2I service, a V2P service, and a V2N service. among them,

The V2P service refers to a service that uses V2P application communication between UEs. The V2N service refers to a service in which a UE and a serving entity communicate with each other through an LTE network entity using a V2N application.

The V2I service refers to a service in which a UE and a Roadside Unit (RSU) use V2I applications to interact. The RSU is an entity that supports V2I services, and can send V2I services to UEs that use V2I applications, or can receive V2I services from UEs that use V2I services. The RSU can be implemented by a base station (eNB) or a stationary UE. If the RSU is implemented by a base station, that is, an eNB type RSU, if the RSU is implemented by a UE, it is called a UE type RSU.

A V2V service refers to a service that uses V2V application communication between UEs. The V2V includes the V2V-related application information directly interacted between the UEs, or the V2V-related application information exchanges between the UEs through the infrastructure supporting the V2X services, such as the RSU and the application server.

In addition, 3GPP also discusses three scenarios of V2V, as shown in scenario 1 of Figure 1 (a), supporting V2V communication based only on the PC5 interface. The UE sends the V2X message to the multiple UEs in the local area through the PC5 interface; in scenario 2 as shown in FIG. 1(b), the V2V communication based on the Uu port is supported: the UE transmits the V2X message to the E through the uplink (UL) uplink. - UTRAN, the E-UTRAN then downlinks the V2X message to multiple UEs in the local area via the downlink (DL). Scenario 3 supports V2V communication using Uu and PC5 interfaces. As shown in Figure 1(c), the UE sends a V2X message to other UEs through the PC5 interface. After receiving the V2X message from the PC5 interface, the UE type RSU transmits the V2X message to the UE. An evolved Evolved Universal Terrestrial Radio Access Network (E-UTRAN), which broadcasts V2X messages received from the UE type RSU to a plurality of UEs in a local area; or, as shown in FIG. 1 (d), the UE uplinks the V2X message to the E-UTRAN, and the E-UTRAN transmits the V2X message to the one or more UE type RSUs after receiving the V2X message from the Uu port, and the UE type RSU will be from the E-UTRAN. The received V2X message is sent to multiple UEs in the local area through the PC5 interface.

According to the current 3GPP discussion, the V2N service delay requirement is 500 milliseconds. As shown in FIG. 2, the UE sends a V2X message to the E-UTRAN through the LTE cellular network (the specific path is: UE->eNB->S-GW->V2X). Server), E-UTRAN through existing broadcast multicast services (MBMS, Multimedia Broadcast Multicast Service) or single-cell point-to-multipoint (SC-PTM) technology to broadcast V2X messages to multiple UEs in a local area to meet the delay requirement of. The delay requirement of the V2V/V2I/V2P service is 100 milliseconds, and the current LTE cellular network (ie, UE->eNB->S-GW->V2X server) as shown in FIG. 2 is used for uplink V2X message transmission and current Some MBMS technologies or SC-PTM technologies broadcast V2X messages downstream to multiple car-networking user equipments (V-UEs) in the local area (hereinafter referred to as UEs), which cannot meet the delay requirements of V2V/V2I/V2P services. .

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides a method for realizing the vehicle networking service and a localized network architecture, which can meet the delay requirement of the vehicle networking service.

In order to achieve the object of the present invention, an embodiment of the present invention provides a method for implementing a car networking service, including: distinguishing a broadcast area of a car network communication V2X message;

If the V2X message is a cell broadcast under the base station under the jurisdiction of the adjacent local broadcast multicast service MBMS, triggering the MBMS bearer setup to the adjacent base station;

After the MBMS bearer of the V2X broadcast area is established, the downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is: local V2X server->first entity->adjacent base station.

Optionally, if the V2X message is a cell broadcast under a base station under the jurisdiction of the local MBMS, the method further includes:

Triggering the establishment of the MBMS bearer of the local MBMS;

After the MBMS bearer of the V2X broadcast area is established, the downlink user plane data path of the V2X message broadcasted by the cell under the local MBMS-managed base station is: local V2X server->local broadcast multicast service center BM-SC->local MBMS GW-> Base station.

Optionally, when the local V2X server receives the V2X message, the local V2X server triggers an active MBMS bearer process to the local BM-SC; the local BM-SC triggers to The MBMS session start process of the local MBMS GW;

The distinguishing the broadcast area of the V2X message includes: the MBMS GW distinguishes the broadcast area of the V2X message during the start of the MBMS session.

Optionally, when the local V2X server receives the V2X message, the local V2X server triggers an active MBMS bearer process to the local BM-SC;

The distinguishing the broadcast area of the V2X message includes: when the local BM-SC receives the activated MBMS bearer request message triggered by the local V2X server, the local BM-SC distinguishes the broadcast area of the V2X message and determines whether to Trigger the MBMS session start process to the neighboring local MBMS GW.

Optionally, the distinguishing the broadcast area of the V2X message includes:

When the local V2X server receives the V2X message, the local V2X server distinguishes the broadcast area of the V2X message and determines whether to trigger an active MBMS bearer process to the adjacent local BM-SC.

Optionally, the distinguishing the broadcast area of the V2X message includes:

When the local V2X server receives the V2X message, the local V2X server distinguishes the broadcast area of the V2X message and determines whether to send a message to the neighboring local V2X server.

Optionally, the triggering the MBMS bearer establishment of the local MBMS includes:

The local MBMS GW acquires an IP unicast address of the base station, and a user plane transmission GTP tunnel endpoint identifier GTP-TEID between the base station and the local MBMS GW.

Optionally, the acquiring the IP unicast address of the base station, and the user plane transmission GTP-TEID between the base station and the local MBMS GW includes:

The local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE initiates an MBMS session start request message to the base station; the base station returns an MBMS session start response message to the MCE, and the MCE sends the message to the MME. Returning an MBMS session start response message, and the MME returns a session start response message to the local MBMS GW;

The base station is carried in both the session start response message and the MBMS session start response message. The IP unicast address, the user plane transmission GTP-TEID between the base station and the local MBMS GW.

Optionally, the determining whether to trigger an MBMS session start process to an adjacent local MBMS GW includes:

The local BM-SC determines whether to trigger an MBMS session start procedure to an adjacent local MBMS GW according to the MBMS related information learned through the non-UE related signaling process between the base stations.

Optionally, the determining whether to trigger an active MBMS bearer process to an adjacent local BM-SC includes:

The local V2X server determines whether to trigger an MBMS session start process to an adjacent local BM-SC according to the MBMS related information learned through the non-UE related signaling process between the base stations.

Optionally, the process of the non-UE related signaling interaction includes one or more of the following: an X2 establishment process and an eNB configuration update process.

Optionally, the MBMS related information includes one or more of the following information: whether there is local MBMS network element, routing information of the local MBMS network element.

Optionally, whether the local MBMS network element is indicated by one or more of the following manners: including indication information to display whether local MBMS network element, routing information including a local MBMS network element is displayed to implicitly indicate the local MBMS Network element

The routing information of the local MBMS network element includes one or more of the following information: an identifier of the MBMS network element, and an IP address of the MBMS network element.

Optionally, the local MBMS network element includes one or more of the following: a local MBMS GW, a local BM-SC.

Optionally, the determining whether to send the message to the neighboring local V2X server includes:

The local V2X server determines whether to send a message to an adjacent local V2X server according to the V2X server related related information learned through the non-UE related signaling process between the base stations.

Optionally, the local V2X server related information includes one or more of the following information: whether there is local V2X server, routing information of the local V2X server.

Optionally, whether the local V2X server indicates by one or more of the following manners: including indication information to display whether there is a local V2X server, routing information including the local V2X server, to implicitly indicate whether there is a local V2X server ;

The routing information of the local V2X server includes one or more of the following information: an identifier of the local V2X server, and an IP address of the local V2X server.

Optionally, when the local V2X server receives the V2X message, the method further includes:

Determining, by the local V2X server, whether the MBMS bearer that has been established and the temporary mobile group identifier TMGI that identifies the MBMS bearer can be reused according to the geographic area and/or the V2X service type of the V2X message broadcast; or if the local V2X server gives the V2X service Assigning a new TMGI, the local BM-SC determines whether the MBMS bearer that has been established and the TMGI that identifies the MBMS bearer can be reused according to the geographic area and/or the V2X service type of the V2X message broadcast;

If not reusable, the local V2X server sends an activate MBMS bearer request message to the local BM-SC to activate the MBMS bearer of the V2X message broadcast cell; and includes the quality of service QoS parameter and the MBMS broadcast area in the activated MBMS bearer request message.

Optionally, the activated MBMS bearer request message further carries a TMGI.

Optionally, the allocation of the TMGI is based on each area: the TMGI is allocated according to different V2X message broadcast areas and/or V2X message types; at this time, the MBMS is carried in different V2X message broadcast areas and/or V2X message types. Time established;

Or, the allocation of the TMGI is based on each UE: a TMGI is allocated to each UE that has a V2X message transmission requirement; in this case, the MBMS bearer is established when the UE needs to send a V2X message;

Alternatively, the allocation of the TMGI is performed based on the V2X service: the TMGI is allocated for the service of the specific V2X message, and the MBMS broadcast area is a virtual broadcast area; at this time, the MBMS bearer only needs to be established once in the virtual broadcast area.

Optionally, if the allocation of the TMGI is based on V2X services;

The MBMS related information further includes: a TMGI or V2X service class supported by a local MBMS network element. Type information, used to configure the MBMS bearer corresponding to the supported V2X service.

Optionally, the local V2X server is a function body of an application layer.

Optionally, the local V2X server is disposed on the base station or outside the base station.

Optionally, the function body of the application layer is a logical function roadside unit RSU or an independent physical entity.

Optionally, the MBMS bearer establishment triggered to the neighboring base station includes:

The local MBMS GW allocates an IP multicast address of the base station and the neighboring base station according to the V2X message broadcast area, and a user plane transmission GTP-TEID between the base station corresponding to the IP multicast address and the neighboring base station and the local MBMS GW.

Optionally, the allocating includes:

The local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, where the MCE sends an MBMS session start request message to the base station;

Both the session start request message and the MBMS session start request message carry: an IP multicast address of the base station and the neighboring base station, a base station corresponding to the IP multicast address, and a user plane transmission GTP between the neighboring base station and the local MBMS GW. A list of cell identifiers for V2X message broadcasts under the TEID, base station, and neighboring base stations.

Optionally, the first entity includes: a local BM-SC, a local MBMS GW;

The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->local BM-SC->local MBMS GW->neighboring base station.

The local BM-SC triggers an MBMS session start procedure to the local MBMS GW of the neighboring base station.

Optionally, the MBMS session starting process that the local BM-SC triggers to the local MBMS GW of the neighboring base station includes:

The local BM-SC carries in a session request message sent to an adjacent local MBMS GW With: a cell identifier list of V2X message broadcasts under neighboring base stations;

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, and the MCE The MME returns an MBMS session start response message, and the MME returns a session start response message to the neighboring local MBMS GW;

The session start response message and the MBMS session start response message both carry the IP unicast address of the neighboring base station, the user plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station.

Optionally, the first entity includes a local BM-SC, an adjacent local MBMS GW;

The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->local BM-SC->adjacent local MBMS GW->neighboring base station.

Optionally, the MBMS session process of triggering the adjacent local MBMS includes:

The local V2X server triggers an active MBMS bearer procedure to an adjacent local BM-SC that triggers an MBMS session start procedure to an adjacent local MBMS GW.

Optionally, the local V2X server triggers an active MBMS bearer process to a local BM-SC of a neighboring base station, and the local BM-SC of the neighboring base station triggers an MBMS session start process to a local MBMS GW of the neighboring base station, including :

The local V2X server carries, in the activated MBMS bearer request message sent to the neighboring local BM-SC, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The neighboring local BM-SC carries, in the session request message sent to the neighboring local MBMS GW, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, The MCE returns an MBMS Session Start Response message to the MME, and the MME returns a session to the neighboring local MBMS GW. Start a response message;

Both the session start response message and the MBMS session start response message carry: an IP unicast address of the neighboring base station, a user plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station.

Optionally, the first entity includes: an adjacent local BM-SC, an adjacent local MBMS GW;

The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->adjacent local BM-SC->adjacent local MBMS GW->adjacent Base station.

The local V2X server sends a message to an adjacent local V2X server to trigger an active MBMS bearer process initiated by the neighboring local V2X server to the neighboring local BM-SC and a subsequent adjacent local BM-SC to the phase The MBMS session of the neighboring local MBMS GW starts the process.

Optionally, the sending, by the local V2X server, the message to the neighboring local V2X server includes:

The local V2X server carries the V2X message type and the cell identifier list of the V2X message broadcast of the neighboring base station in the message sent to the neighboring local V2X server; the neighboring local V2X server returns a response to the local V2X server to confirm the pair. Receiving of a message;

The neighboring local V2X server carries, in the activated MBMS bearer request message sent to the neighboring local BM-SC, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, The MCE returns an MBMS session start response message to the MME, and the MME returns a session start response message to the neighboring local MBMS GW;

Both the session start response message and the MBMS session start response message carry: neighboring base stations The IP unicast address, the user plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station.

Optionally, the first entity includes: a neighboring local V2X server, an adjacent local BM-SC, and an adjacent local MBMS GW;

The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->adjacent local V2X server->adjacent local BM-SC->adjacent Local MBMS GW-> neighboring base stations.

The embodiment of the present invention further discloses a localized network architecture, which includes at least a local V2X server and an MBMS bearer establishing entity;

a local V2X server for distinguishing a broadcast area of a car network communication V2X message;

An MBMS bearer setup entity is configured to trigger an MBMS bearer setup to an adjacent base station when the V2X message is a cell broadcast under a neighboring local MBMS-managed base station; after the MBMS bearer of the V2X broadcast area is established, the V2X message is in the phase The downlink user plane data path broadcast by the cell under the neighboring local MBMS-managed base station is: local V2X server -> first entity > neighboring base station.

Optionally, the MBMS bearer establishing entity is further configured to: when the V2X message is a cell broadcast under a base station under the local MBMS, trigger an MBMS bearer setup of the local MBMS; after the MBMS bearer of the V2X broadcast area is established, the V2X The downlink user plane data path of the cell broadcast under the base station under the local MBMS jurisdiction is: local V2X server->local broadcast multicast service center BM-SC->local MBMS GW->base station.

Optionally, the MBMS bearer establishment entity includes a local BM-SC;

The local V2X server is further configured to: when receiving the V2X message, trigger an activated MBMS bearer process to the local BM-SC; the local BM-SC triggers an MBMS session start process to the local MBMS GW;

or,

The MBMS bearer establishment entity includes a local V2X server;

The local V2X server is further configured to: when receiving the V2X message, trigger an activated MBMS bearer process to the local BM-SC;

Or,

The MBMS bearer establishment entity includes a local V2X server;

The local V2X server is further configured to: when receiving the V2X message, distinguish the broadcast area of the V2X message and determine whether to trigger an active MBMS bearer process to the adjacent local BM-SC;

or,

The MBMS bearer establishment entity includes a local V2X server;

The local V2X server is further configured to: when receiving the V2X message, distinguish the broadcast area of the V2X message and determine whether to send a message to the neighboring local V2X server.

The local MBMS GW acquires an IP unicast address of the base station, and a user plane transmission GTP-TEID between the base station and the local MBMS GW.

Optionally, the MBMS bearer establishment entity is specifically configured to:

The session start response message and the MBMS session start response message both carry the IP unicast address of the base station, and the user plane transmission GTP-TEID between the base station and the local MBMS GW.

Determining, by the local BM-SC, whether to trigger an MBMS session start process to an adjacent local MBMS GW according to MBMS related information learned through a non-UE related signaling process between the base stations;

Alternatively, the determining whether to trigger an active MBMS bearer process to an adjacent local BM-SC includes:

Determining, by the local V2X server, whether to trigger an MBMS session start process to an adjacent local BM-SC according to MBMS related information learned through a non-UE related signaling process between the base stations;

or,

The determining whether to send a message to an adjacent local V2X server includes:

Optionally, the MBMS bearer establishment entity is specifically configured to:

The local MBMS GW allocates an IP multicast address of the base station and the neighboring base station according to the V2X message broadcast area, and a user plane transmission GTP-TEID between the base station corresponding to the IP multicast address and the neighboring base station and the local MBMS GW; or

The local BM-SC triggers an MBMS session start procedure to a local MBMS GW of a neighboring base station; or

The local V2X server triggers an active MBMS bearer procedure to an adjacent local BM-SC, and the neighboring local BM-SC triggers an MBMS session start procedure to an adjacent local MBMS GW; or

Optionally, the MBMS bearer establishment entity is more specifically used for:

The local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the base station; wherein, in the session start request message and the MBMS session start request message, Carrying: an IP multicast address of the base station and the neighboring base station, a base station corresponding to the IP multicast address, and a user plane transmission GTP-TEID between the neighboring base station and the local MBMS GW, and a cell broadcasted by the base station and the V2X message under the neighboring base station List of identifiers;

or,

The session request message sent by the local BM-SC to the neighboring local MBMS GW carries: a cell identity list broadcasted by the V2X message under the neighboring base station;

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MCE to the MCE. Sending an MBMS Session Start Request message, the MCE sends an MBMS Session Start Request message to the neighboring base station; the neighboring base station returns an MBMS Session Start Response message to the MCE, and the MCE returns an MBMS Session Start Response message to the MME, and the MME returns to the adjacent local MBMS GW. a session start response message; wherein the session start response message and the MBMS session start response message both carry an IP unicast address of the neighboring base station, a user plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station ;

or,

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, The MCE returns an MBMS session start response message to the MME, and the MME returns a session start response message to the neighboring local MBMS GW. The session start response message and the MBMS session start response message both carry: an IP unicast address of the neighboring base station. User plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station;

or,

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session to the neighboring base station. The start request message; the neighboring base station returns an MBMS session start response message to the MCE, the MCE returns an MBMS session start response message to the MME, and the MME returns a session start response message to the neighboring local MBMS GW; wherein, the session start response message and the MBMS session The start response message carries: an IP unicast address of the neighboring base station, a user plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station.

Optionally, the first entity includes: a local BM-SC, a local MBMS GW; and the downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: a local V2X server- >Local BM-SC->Local MBMS GW->Neighboring base station;

or,

The first entity includes a local BM-SC, a local MBMS GW of the neighboring base station, and a downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is: a local V2X server-> Local BM-SC->local MBMS GW of the neighboring base station->neighboring base station;

or,

The first entity includes: a neighboring local BM-SC, and a neighboring local MBMS GW; the downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is: local V2X Server->local BM-SC of the neighboring base station>local MBMS GW of the neighboring base station->adjacent base station;

or,

The first entity includes: a local V2X server of a neighboring base station, an adjacent local BM-SC, and an adjacent local MBMS GW;

The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->local V2X server of the neighboring base station->local BM-SC of the neighboring base station-> Local MBMS GW of the neighboring base stations -> neighboring base stations.

Optionally, the localized network architecture is set in the base station or is disposed outside the base station.

An embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions for performing the method for implementing a car networking service according to any of the above.

Compared with the prior art, the technical solution of the present application includes: a broadcast area for a local V2X message. Differentiate: if the V2X message is a cell broadcast under the neighboring local MBMS-managed base station, triggering the MBMS bearer setup to the neighboring base station; after the MBMS bearer of the V2X broadcast area is established, the V2X message is in the neighboring local MBMS jurisdiction. The downlink user plane data path of the cell broadcast under the base station is: local V2X server -> first entity > neighboring base station. The method for implementing the Internet of Vehicle service provided by the embodiment of the present invention, on the one hand, sets related entities that implement the Internet of Vehicle service, such as a V2X server, a BM-SC, an MBMS GW, etc., in the base station, thereby shortening the transmission time of the message; The cell broadcast category of the V2X message is distinguished, and the manner of completely adopting the broadcast multicast service is avoided. Thereby meeting the delay requirements of the car networking business, especially the V2V/V2I/V2P service.

Other features and advantages of the embodiments of the invention will be set forth in the description in the description which The objectives and other advantages of the invention may be realized and obtained by means of the structure particularly pointed in the appended claims.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1(a) to (d) are schematic diagrams of four scenarios of a V2V service in the related art;

2 is a schematic diagram of using LTE cellular uplink and MBMS/SC-PTM downlink transmission in the related art;

3 is a flowchart of a method for implementing a car networking service according to an embodiment of the present invention;

4(a) is a schematic diagram of a localized network architecture for transmitting a V2V/V2I/V2P service according to a first embodiment of the present invention;

4(b) is a schematic diagram of another localized network architecture for transmitting a V2V/V2I/V2P service according to the first embodiment of the present invention;

FIG. 5 is a schematic flowchart of a MBMS session start process for V2X message transmission according to the first embodiment of the present invention; FIG.

6 is a schematic diagram of a network architecture for transmitting a V2V/V2I/V2P service according to a second embodiment of the present invention;

FIG. 7 is a schematic flowchart of a MBMS session start process for V2X message transmission according to a second embodiment of the present invention; FIG.

8 is a schematic diagram of a network architecture for transmitting a V2V/V2I/V2P service according to a third embodiment of the present invention;

FIG. 9 is a schematic flowchart of a MBMS session start process for V2X message transmission according to a third embodiment of the present invention; FIG.

10 is a schematic diagram of an embodiment of inter-base station interaction MBMS related information according to the present invention;

11 is a schematic diagram of a network architecture for transmitting a V2V/V2I/V2P service according to a fourth embodiment of the present invention;

12 is a schematic flowchart of a MBMS session start process for V2X message transmission according to a fourth embodiment of the present invention;

13 is a schematic diagram of a network architecture for transmitting a V2V/V2I/V2P service according to a fifth embodiment of the present invention;

FIG. 14 is a schematic flowchart of a MBMS session start process for V2X message transmission in a fifth embodiment of the present invention.

FIG. 15 is a schematic flowchart diagram of an embodiment of information related to a local V2X server exchanged between base stations according to the present invention.

Preferred embodiment of the invention

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

FIG. 3 is a flowchart of a method for implementing a car networking service according to an embodiment of the present invention. As shown in FIG. 3, the method includes:

Step 300: Differentiate the broadcast area of the V2X message.

In this step, according to the V2X message broadcast area information of the V2X message, it can be determined whether the V2X message is a cell broadcast under the base station under the local MBMS jurisdiction or a cell broadcast under the base station under the neighboring local MBMS.

Manner 1: When the local V2X server receives the V2X message, the local V2X server triggers the active MBMS bearer process to the local broadcast multicast service center (BM-SC); the local BM-SC triggers the MBMS session start process to the local MBMS GW. The step specifically includes: during the start of the MBMS session, the local MBMS GW distinguishes the broadcast area of the V2X message.

Manner 2: When the local V2X server receives the V2X message, the local V2X server triggers the active MBMS bearer process to the local BM-SC. The step specifically includes: when the local BM-SC receives the activated MBMS bearer request message triggered by the local V2X server, the local BM-SC distinguishes the broadcast area of the V2X message and determines whether to trigger the MBMS to the neighboring local MBMS GW. The beginning of the session.

Manner 3: The step specifically includes: when the local V2X server receives the V2X message, the local V2X server distinguishes the broadcast area of the V2X message and determines whether to trigger the active MBMS bearer process to the local BM-SC of the neighboring base station.

Manner 4: The step specifically includes: when the local V2X server receives the V2X message, the local V2X server distinguishes the broadcast area of the V2X message and determines whether to send a message to the local V2X server of the neighboring base station.

The process of determining whether to trigger the MBMS session of the local MBMS GW of the neighboring base station in the second step of the step includes:

The local MBMS related information may be acquired between the base stations in the process of non-UE related signaling interaction;

The process of non-UE related signaling interaction includes but is not limited to one or more of the following: an X2 Setup process (eNB Setup Update).

The MBMS related information includes, but is not limited to, one or more of the following information: whether there is a local MBMS network element, and routing information of the local MBMS network element;

Whether the local MBMS network element can be indicated by one or more of the following means: including indication information to indicate whether there is a local MBMS network element, including a local MBMS network element. Routing information to implicitly indicate whether there is a local MBMS network element;

The routing information of the local MBMS network element includes, but is not limited to, one or more of the following information: an identifier of the MBMS network element, and an IP address of the MBMS network element.

The local MBMS network element includes but is not limited to one or more of the following: a local MBMS GW, a local BM-SC.

The determining whether to trigger the active MBMS bearer process to the neighboring local BM-SC includes:

The process of non-UE related signaling interaction includes but is not limited to one or more of the following: an X2 setup process, an eNB configuration update process.

Whether the local MBMS network element can be indicated by one or more of the following means: including indication information to display whether there is a local MBMS network element, routing information including the local MBMS network element, to implicitly indicate whether there is a local MBMS Network element

The built-in MBMS network element includes but is not limited to one or more of the following: a local MBMS GW, a local BM-SC.

Further, the allocation of the TMGI is based on the V2X service, and the MBMS related information may further include: the TMGI or the V2X service type information supported by the local MBMS network element, configured to configure the MBMS bearer corresponding to the supported V2X service.

The determining whether to send the message to the neighboring local V2X server includes: the local V2X server can learn the related information of the V2X server through the non-UE related signaling process between the base stations, thereby determining whether to send to the phase. Neighboring local V2X server messages. More specifically:

The local V2X server related information may be acquired between the base stations in the process of non-UE related signaling interaction;

The information about the local V2X server includes, but is not limited to, one or more of the following information: whether there is routing information of the local V2X server and the local V2X server;

Whether there is a local V2X server may be indicated by one way or more of the following: including indication information to display whether there is a local V2X server, routing information including the local V2X server to implicitly indicate whether there is a local V2X server.

The routing information of the local V2X server includes but is not limited to one or more of the following information: an identifier of the local V2X server, and an IP address of the local V2X server.

In the embodiment of the present invention, the local V2X server may be a function body of the application layer. The local V2X server is set up on or off the base station (near). The local V2X server is a logical functional roadside unit RSU or physical entity.

When the local V2X server receives the V2X message, the method further includes:

The local V2X server determines whether the established MBMS bearer and the temporary mobile group identifier TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast; or if the local V2X server allocates a new TMGI to the V2X service. The local BM-SC determines whether the MBMS bearer that has been established and the TMGI that identifies the MBMS bearer can be reused according to the geographic area and/or the V2X service type of the V2X message broadcast;

If not reusable, the local V2X server sends an active MBMS bearer request message to the local BM-SC to activate the MBMS bearer of the V2X message broadcast cell; the active MBMS bearer request message carries the quality of service QoS parameter and the MBMS broadcast area. Further, the activated MBMS bearer request message further carries a TMGI. among them,

The allocation of TMGI is based on each area: the TMGI is allocated according to different V2X message broadcast areas and/or V2X message types; at this time, the MBMS is carried in different V2X message broadcast areas and/or V2X message types;

Or, the allocation of the TMGI is performed based on the V2X service: the TMGI is allocated for the service of the specific V2X message, and the MBMS broadcast area is a large virtual broadcast area, such as a broadcast area at the city level; in this case, the MBMS bearer only needs to be in the The virtual broadcast area is established once. That is, when the local BM-SC receives the V2X message sent by the UE, the local BM-SC determines whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the service type of the V2X message. Here, other technical means may be employed to ensure that the V2X message is broadcast in a partial area of the virtual broadcast area.

Further, if the allocation of the Temporary Mobile Group Identity (TMGI) is based on the V2X service, the MBMS related information may further include: TMGI or V2X service type information supported by the local MBMS network element, configured to configure the MBMS corresponding to the supported V2X service. Hosted.

According to the judgment of step 300, in one case, if the V2X message is a cell broadcast under the base station under the jurisdiction of the local MBMS, then,

Step 3011: Trigger the establishment of the MBMS bearer of the local MBMS.

The local MBMS GW obtains the IP unicast address of the base station and the GTP Tunnel Endpoint Identifier (GTP Tunnel Endpoint Identifier) between the base station and the local MBMS GW. Specifically include:

The local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE initiates an MBMS session start request message to the base station; the base station returns an MBMS session start response message to the MCE, and the MCE returns the MBMS to the MME. The session start response message, the MME returns a session start response message to the local MBMS GW; wherein the session start response message and the MBMS session start response message both carry the IP unicast address of the base station, the base station and the local MBMS User plane transmission GTP-TEID between GWs;

Thus, when a V2X message is sent to the local MBMS GW, the local MBMS GW sends the V2X message to the corresponding base station using the IP unicast address.

Step 3021: After the MBMS bearer of the V2X broadcast area is established, the downlink user plane data path of the V2X message broadcasted by the cell under the base station is: local V2X server->local BM-SC->local MBMS GW->base station.

or,

According to the judgment of step 300, another case is: if the V2X message is in the adjacent local Cell broadcast under the base station under the jurisdiction of MBMS, then,

Step 3012: Trigger an MBMS bearer setup to an adjacent base station.

Correspondingly, in the first mode, the local MBMS GW allocates an IP multicast address of the base station and the neighboring base station according to the V2X message broadcast area, and a user plane transmission GTP between the base station corresponding to the IP multicast address and the neighboring base station and the local MBMS GW. -TEID. Specifically include:

The local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the base station, where both the session start request message and the MBMS session start request message are carried. : IP multicast address of the base station and the neighboring base station, the base plane corresponding to the IP multicast address, the user plane transmission GTP-TEID between the neighboring base station and the local MBMS GW, and the cell identifier list of the V2X message broadcast by the base station and the neighboring base station .

Thus, when a V2X message is sent to the local MBMS GW, the local MBMS GW transmits the V2X message to the corresponding base station and the adjacent base station using the IP multicast address of the base station and the neighboring base station.

Correspondingly, in the second mode, if the V2X message is a cell broadcast under the jurisdiction of the adjacent local MBMS, the local BM-SC triggers the MBMS session start procedure to the neighboring local MBMS GW. Specifically include:

The local BM-SC carries, in the session request message sent to the neighboring local MBMS GW, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The session start response message and the MBMS session start response message both carry the IP unicast address of the neighboring base station, the user plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station;

Thus, when a V2X message is sent to the local MBMS GW of the neighboring base station, the local MBMS GW of the neighboring base station transmits the V2X message to the corresponding adjacent base using the IP unicast address of the neighboring base station. stand on.

Correspondingly, in the third mode, if the V2X message is a cell broadcast under the jurisdiction of the adjacent local MBMS, the local V2X server triggers an active MBMS bearer process to the adjacent local BM-SC, and the adjacent local BM-SC triggers the phase to the phase. The MBMS session of the neighboring local MBMS GW starts the process. Specifically include:

Thus, when a V2X message is sent to the local MBMS GW of the neighboring base station, the local MBMS GW of the neighboring base station transmits the V2X message to the corresponding neighboring base station using the IP unicast address of the neighboring base station.

Correspondingly, in the fourth method, if the V2X message is broadcasted by the cell under the adjacent local V2X server, the local V2X server sends a message to the adjacent local V2X server to trigger the initial local V2X server to be adjacent to the adjacent one. The active MBMS bearer process of the local BM-SC and the subsequent MBMS session start process of the neighboring local BM-SC to the neighboring local MBMS GW. Specifically include:

The local V2X server carries the V2X message type and the cell identity list of the V2X message broadcast by the neighboring base station in the message sent to the neighboring local V2X server; the neighboring local V2X server returns a response to the local V2X server to confirm the message. Receive

Step 3022: After the MBMS bearer of the V2X broadcast area is established, the downlink user plane data path of the V2X broadcasted by the cell under the neighboring base station is: local V2X server->first entity>adjacent base station.

Correspondingly, in the first method, the first entity includes: a local BM-SC, and a local MBMS GW. The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is: local V2X server->local BM-SC->local MBMS GW->neighbor base station.

Correspondingly, in the second mode, the first entity includes: a local BM-SC, and a local MBMS GW of the neighboring base station. The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->local BM-SC->adjacent local MBMS GW->neighboring base station.

Correspondingly, in the third manner, the first entity includes: a local BM-SC of the neighboring base station, and a local MBMS GW of the neighboring base station. The downlink user plane data path of the V2X message broadcasted by the cell under the local MBMS jurisdiction of the base station of the neighboring local MBMS is specifically: local V2X server->adjacent local BM-SC->adjacent local MBMS GW-> Adjacent base stations.

Correspondingly, in the fourth method, the first entity includes: an adjacent local V2X server, an adjacent local BM-SC, and an adjacent local MBMS GW. The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring MBMS-managed base station is specifically: local V2X server->adjacent local V2X server->adjacent local BM-SC->adjacent local MBMS GW-> neighboring base stations.

In the technical solution provided by the embodiment of the present invention, in the local MBMS architecture, the allocation of the TMGI is performed on a per-UE basis, that is, the UE is allocated to each UE that has a V2X message transmission requirement. At this time, the MBMS bearer is established when the UE has a V2X message to be sent. The local BM-SC may determine the broadcast cell list of the V2X message by the geographic location of the UE.

The allocation of TMGI may also be based on the cell in which the UE is located, that is, each cell is regarded as a V2X message source, and TMGI is allocated in units of cells. At this time, the MBMS bearer is established only when a cell first sends a V2X message to the UE. The MBMS broadcast area is a collection of the cell and all neighboring cells. That is, when the local BM-SC receives the V2X message sent by the UE, the local BM-SC determines whether the established MBMS bearer can be reused and the TMGI that identifies the MBMS bearer according to the service type of the cell and/or the V2X message in which the UE is located. .

The allocation of TMGI may also be based on the V2X service, that is, the TMGI is allocated for the service of the specific V2X message, and the MBMS broadcast area is a large virtual broadcast area, such as a broadcast area at the city level. At this time, the MBMS bearer only needs to be established once in the virtual broadcast area. That is, when the local BM-SC receives the V2X message sent by the UE, the local BM-SC determines whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the service type of the V2X message. Here, other technical means may be employed to ensure that the V2X message is broadcast in a partial area of the virtual broadcast area.

The method for implementing the Internet of Vehicle service provided by the embodiment of the present invention, on the one hand, sets related entities that implement the Internet of Vehicle service, such as a V2X server, a BM-SC, an MBMS GW, etc., in the base station or in the vicinity of the base station, thereby shortening the transmission time of the message; On the one hand, the broadcast area of the V2X message is distinguished, and the manner of completely adopting the broadcast multicast service is avoided. Thereby meeting the delay requirements of the car networking business, especially the V2V/V2I/V2P service.

The embodiment of the present invention further provides a localized network architecture, including at least a local V2X server and an MBMS bearer establishment entity;

The local V2X server is set to distinguish the broadcast area of the V2X message;

An MBMS bearer setup entity is configured to trigger an MBMS bearer setup to a neighboring base station when the V2X message is a cell broadcast under a base station under the adjacent local broadcast multicast service MBMS; after the MBMS bearer of the V2X broadcast area is established, The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is: local V2X server -> first entity > neighboring base station.

Further, the MBMS bearer establishment entity is further configured to: when the V2X message is a cell broadcast under the base station under the local MBMS, trigger the MBMS bearer establishment of the local MBMS; after the MBMS bearer of the V2X broadcast area is established, the V2X message is localized. The downlink user plane data path of the cell broadcast under the base station under the MBMS jurisdiction is: local V2X server -> local broadcast multicast service center BM-SC -> local MBMS GW -> base station.

When the MBMS bearer establishment entity includes a local BM-SC;

The local V2X server is further configured to: when receiving the V2X message, trigger an active MBMS bearer process to the local BM-SC; the local BM-SC triggers an MBMS session start process to the local MBMS GW;

or,

When the MBMS bearer establishment entity includes a local V2X server;

The local V2X server is further configured to: when receiving the V2X message, trigger an active MBMS bearer process to the local BM-SC;

or,

When the MBMS bearer establishment entity includes a local V2X server;

The local V2X server is further configured to: when receiving the V2X message, distinguish the broadcast area of the V2X message and determine whether to trigger an active MBMS bearer process to the local BM-SC of the neighboring base station;

or,

When the MBMS bearer establishment entity includes a local V2X server;

The local V2X server is further configured to: when receiving the V2X message, distinguish the broadcast area of the V2X message and determine whether to send a message to the local V2X server of the neighboring base station.

among them,

The MBMS bearer establishment that triggers the local MBMS includes:

The local MBMS GW acquires the IP unicast address of the base station and the user plane transmission GTP-TEID between the base station and the local MBMS GW. specifically,

The MBMS bearer establishment entity is specifically set to:

The local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE initiates an MBMS session start request message to the base station; the base station returns an MBMS session start response message to the MCE, and the MCE returns the MBMS to the MME. a session start response message, the MME returns a session start response message to the local MBMS GW;

among them,

The process of determining whether to trigger an MBMS session to an adjacent local MBMS GW includes:

The local BM-SC determines whether to trigger the MBMS session start process to the neighboring local MBMS GW according to the MBMS related information obtained through the non-UE related signaling process between the base stations; or

The process of determining whether to trigger an active MBMS bearer to an adjacent local BM-SC includes:

Determining, by the local V2X server, the MBMS related information according to the non-UE related signaling process between the base stations, whether to trigger an MBMS session start process to the adjacent local BM-SC; or

The local V2X server determines whether to send a message to an adjacent local V2X server according to the information related to the V2X server through the non-UE related signaling process between the base stations.

When the V2X message is a cell broadcast under a neighboring local MBMS-managed base station,

The MBMS bearer establishment entity is specifically configured as:

The local MBMS GW allocates an IP multicast address of the base station and the neighboring base station according to the V2X message broadcast area, and a base station corresponding to the IP multicast address and a neighboring base station and the local MBMS GW User plane transport GTP-TEID; or,

More specifically, the MBMS bearer setup entity is set to:

The local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the base station, where both the session start request message and the MBMS session start request message are carried. : IP multicast address of the base station and the neighboring base station, the base plane corresponding to the IP multicast address, the user plane transmission GTP-TEID between the neighboring base station and the local MBMS GW, and the cell identifier list of the V2X message broadcast by the base station and the neighboring base station ;

or,

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, and the MCE The MME returns an MBMS session start response message, and the MME returns a session start response message to the neighboring local MBMS GW. The session start response message and the MBMS session start response message both carry the IP unicast address of the neighboring base station, and the neighboring User plane transmission GTP-TEID between the local MBMS GW and the neighboring base station;

Or,

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, and the MCE The MME returns an MBMS session start response message, and the MME returns a session start response message to the neighboring local MBMS GW. The session start response message and the MBMS session start response message both carry: an IP unicast address of the neighboring base station, and a phase User plane transmission GTP-TEID between the neighboring local MBMS GW and the neighboring base station;

or,

The local V2X server carries the V2X message type and the cell identity list of the V2X message broadcast by the neighboring base station in the message sent to the neighboring local V2X server; the neighboring local V2X server returns a response to the local V2X server to confirm the message. receive;

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, and the MCE The MME returns an MBMS session start response message, and the MME returns a session start response message to the neighboring local MBMS GW. The session start response message and the MBMS session start response message both carry: an IP unicast address of the neighboring base station, and a phase The user plane between the neighboring local MBMS GW and the neighboring base station transmits the GTP-TEID.

When the first entity includes the local BM-SC and the local MBMS GW, the downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X Server->Local BM-SC->Local MBMS GW->Neighboring Base Station;

or,

When the first entity includes the local BM-SC and the local MBMS GW of the neighboring base station, the downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->local BM -SC->local MBMS GW of the neighboring base station -> neighboring base station;

or,

When the first entity includes the local BM-SC of the neighboring base station and the local MBMS GW of the neighboring base station, the downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server -> local BM-SC of the neighboring base station -> local MBMS GW of the neighboring base station -> neighboring base station;

or,

When the first entity includes a local V2X server of a neighboring base station, a local BM-SC of a neighboring base station, and a local MBMS GW of a neighboring base station, the V2X message is a downlink user broadcasted by the cell under the neighboring local MBMS-managed base station. The polygon data path is specifically: local V2X server -> local V2X server of the neighboring base station -> local BM-SC of the neighboring base station -> local MBMS GW of the neighboring base station -> neighboring base station.

The localized network architecture in the embodiment of the present invention may be set in the base station as shown in FIG. 4(a), or may be disposed outside the base station (near) as shown in FIG. 4(b).

4(a) is a schematic diagram of a localized network architecture for transmitting V2V/V2I/V2P services in the first embodiment of the present invention, and FIG. 4(b) is used for transmitting V2V/V2I in the first embodiment of the present invention. Another localized network architecture diagram for the /V2P service. 4(a) shows that the local V2X server, the local MBMS GW, and the BM-SC are deployed on the eNB, and FIG. 4(b) shows that the local V2X server, the MBMS GW, and the BM-SC can also be deployed. It is deployed in the vicinity of the eNB. In the first embodiment, it is assumed that the broadcast area of the V2X message is a cell under a single base station. For uplink unicast, it can be based on existing Local IP Access (LIPA)/Selected IP Traffic Offload (SIPTO) technology. For downlink broadcasts, the core network elements of the MBMS/SC-PTM, such as MBMS GW and BM-SC, are localized. Localized MBMS GW and BM-SC It can be built in the eNB or deployed in the vicinity of the eNB. The local V2X E-UTRAN Server can be built in the eNB or deployed in the vicinity of the eNB. In the first embodiment, the local BM-SC, the local MBMS GW, and the local V2X server are all built in on the eNB. It is also assumed that UE1 is a terminal that transmits a V2X message under the eNB, and UE2 is a terminal that receives a V2X message under the eNB. The uplink user plane data channel for V2X message transmission is: UE1->SIPTO GW->local V2X server; the downlink user plane data channel for V2X message transmission is: local V2X server->local BM-SC->local MBMS GW->eNB ->UE2.

FIG. 5 is a schematic flowchart of a process of starting an MBMS session for V2X message transmission according to the first embodiment of the present invention. As shown in FIG. 5, the method includes:

Step 501: When the local V2X server receives the V2X message sent by the UE1, the local V2X server determines whether the established MBMS bearer and the MBMS bearer (TMGI) can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast.

If it is not reusable, the local V2X server sends an Active MBMS Bearer Request message to the local BM-SC of the base station through the MB2 interface to activate the MBMS bearer of the V2X message broadcast cell. The activated MBMS bearer request message carries information such as TMGI (optional), quality of service (QoS) parameters, MBMS broadcast area, and the like. The QoS parameter is matched to the appropriate MBMS bearer parameter; the MBMS broadcast area may refer to the cell identifier list of the V2X message broadcast under the eNB.

In this embodiment, the allocation of TMGI is based on each region, ie, the TMGI is allocated according to different V2X message broadcast areas and/or V2X message types. MBMS is only established when it is carried in different V2X message broadcast areas and/or V2X message types.

The allocation of TMGI may also be based on each UE, ie, a TMGI is allocated for each UE that has a V2X messaging requirement. The MBMS bearer is established when the UE needs to send a V2X message.

The allocation of TMGI may also be based on the V2X service, that is, the TMGI is allocated for the service of the specific V2X message, and the MBMS broadcast area is a large virtual broadcast area, such as a broadcast area at the city level. At this time, the MBMS bearer only needs to be established once in the virtual broadcast area. That is, when the local BM-SC receives the V2X message sent by the UE, the local BM-SC determines whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the service type of the V2X message. Here, other technical means can be used to ensure that the V2X message is in the virtual broadcast area. Broadcast within the area.

Step 502: The local BM-SC returns an Activate MBMS Bearer Response message to the local V2X server. The MBMS bearer response message carries the TMGI, the service description, and the IP address and port number of the BM-SC for the user plane.

If the local V2X server does not judge whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type broadcasted by the V2X message in step 501, a new TMGI is allocated to the V2X service. Then, the local BM-SC can determine whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast. If it can be reused, the local BM-SC rejects the step 501. Activate the MBMS Bearer Request and proceed directly to step 512.

If the local V2X server does not carry the TMGI in the activated MBMS bearer request sent in step 501, the local BM-SC may determine whether the already established MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast. The TMGI of the MBMS bearer is identified, and if not reusable, the local BM-SC allocates a new TMGI value.

Also, the allocation of TMGI in this embodiment is based on each region, that is, the TMGI is allocated according to different V2X message broadcast areas and/or V2X message types. MBMS is only established when it is carried in different V2X message broadcast areas and/or V2X message types.

Step 503: The local BM-SC sends a Session Start Request message to the MBMS GW built in the base station to trigger a local MBMS session start process. The session request message carries a TMGI, a QoS parameter, a cell identity list of the V2X message broadcast under the eNB, and an MBMS control plane node of the MBMS GW, such as an MME.

Step 504: The local MBMS GW returns a Session Start Response (Session Start Response) message to the local BM-SC.

Step 505: The local MBMS GW establishes an MBMS bearer context.

The local MBMS GW stores the session parameters and the MBMS Control Plane Node List into the MBMS Bearer Context.

The local MBMS GW sends a session start request message to the MME in the MBMS control plane node list, where the session start request message carries the TMGI, the QoS parameter, and the V2X eNB under the eNB. The cell identification list of the broadcast, the transmission network IP unicast address, the C-TEID, and the like.

Step 506: The MME sends an MBMS session start request (MBMS session start request) message to a module control unit (MCE, Module Control Element) that controls the base station.

In the MBMS session start request message, the GTP Tunnel Endpoint Identifier (GTP Tunnel Endpoint Identifier) carrying the TMGI, the transport network IP unicast address, the user plane transmission between the eNB and the MBMS GW, and the V2X message under the eNB are carried. A list of cell IDs broadcast.

Step 507: The MCE sends an MBMS Session Start Request message to the eNB. The MBMS session start request message carries the TMGI, the cell identity list of the V2X message broadcast by the eNB, and the QoS parameter of the MBMS bearer.

Step 508: The eNB returns an MBMS Session Start Response (MBMS Session Start Response) message to the MCE to confirm the reception of the MBMS Session Start Request. The MBMS session start response message carries: an IP unicast address of the eNB and a user plane transmission GTP-TEID between the eNB and the local MBMS GW.

Step 509: After receiving the MBMS Session Start Response message from the eNB, the MCE returns an MBMS Session Start Response message to the MME to confirm the reception of the MBMS Session Start Request. The MBMS session start response message carries: an IP unicast address of the eNB and a user plane transmission GTP-TEID between the eNB and the local MBMS GW.

Step 510: The MME stores the session parameter and the eNB identity as the downstream node in the MBMS bearer context, and returns an MBMS Session Start Response message to the local MBMS GW. The MBMS session start response message carries: an IP unicast address of the eNB and a user plane transmission GTP-TEID between the eNB and the local MBMS GW.

Step 511: The eNB establishes a necessary radio resource to transmit a V2X message to the UE of interest. In the first embodiment, the UE of interest is UE2.

Step 512: The local V2X server sends a V2X message to the local BM-SC built in the eNB. The local BM-SC sends the V2X message to the local MBMS GW built in the eNB. The local MBMS GW sends the V2X message to the eNB by using the IP unicast address. .

6 is a schematic diagram of a network architecture for transmitting a V2V/V2I/V2P service according to a second embodiment of the present invention. As shown in FIG. 6, in the second embodiment, a broadcast area of a V2X message is assumed to be two adjacent bases. The cell under the station (as shown in Figure 6, eNB1 and eNB2). It is also assumed that UE1 is a terminal that transmits a V2X message under eNB1, UE2 is a terminal that receives a V2X message under eNB1, and UE3 is a terminal that receives a V2X message under eNB2. In the second embodiment, the uplink user plane data channel of the V2X message transmission is: UE1->SIPTO GW1->local V2X server 1; the V2X message to UE2 downlink transmission channel is: local V2X server 1->BM-SC1-> MBMS GW1->eNB1->UE2; V2X message to UE3 downlink transmission channel is: local V2X server 1->BM-SC1->MBMS GW1->eNB2->UE3.

FIG. 7 is a schematic flowchart of a MBMS session start process for V2X message transmission according to a second embodiment of the present invention. As shown in FIG. 7, the method includes:

Step 701: When the local V2X server 1 receives the V2X message sent by the UE1, the local V2X server 1 determines whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast.

If not reusable, the local V2X server 1 sends an Activate MBMS Bearer Request message to the BM-SC1 built in the eNB1 through the MB2 interface to activate the MBMS bearer of the cell broadcasted by the V2X message. The activated MBMS bearer request message carries information such as TMGI (optional), QoS parameters, MBMS broadcast area, and the like. The QoS parameters are matched to the appropriate MBMS bearer parameters; the MBMS broadcast area may refer to the cell identity list of the V2X message broadcasts under eNB1 and eNB2.

Step 702: The BM-SC1 sends an Activate MBMS Bearer Response message to the local V2X server 1. The MBMS bearer response message carries the TMGI, the service description, and the IP address and port number of the BM-SC1 for the user plane.

If the activated MBMS bearer request message of step 701 carries the TMGI, the BM-SC1 needs to decide whether the local V2X server 1 is authorized to use the TMGI. If the TMGI is not authorized, the BM-SC1 will reject the active MBMS bearer request of step 701.

If the activated MBMS bearer request message of step 701 does not carry the TMGI, the BM-SC1 allocates the value of the TMGI.

If the local V2X server 1 does not judge whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type broadcasted by the V2X message in step 701, a new V2X service is allocated. TMGI, then, BM-SC1 can judge whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast, and if it can be reused, the BM-SC1 rejects the step 701. Activate the MBMS bearer request.

If the local V2X server 1 does not carry the TMGI in the activated MBMS bearer request sent in step 701, the BM-SC1 can determine whether the already established MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast. The TMGI of the MBMS bearer is identified, and if it is not reusable, the BM-SC1 allocates a new TMGI value. The allocation of TMGI in this embodiment is based on each area, that is, the TMGI is allocated according to different V2X message broadcast areas and/or V2X message types. MBMS is only established when it is carried in different V2X message broadcast areas and/or V2X message types.

Step 703: The BM-SC1 sends a session request message to the MBMS GW1 built in the eNB1 to trigger the MBMS session start process. The session request message carries a TMGI, a QoS parameter, a cell identity list of V2X message broadcasts under eNB1 and eNB2, an MBMS control plane node of the MBMS GW1, such as an MME, and the like.

Step 704: The MBMS GW1 sends a session start response message to the BM-SC1.

Step 705: The MBMS GW1 establishes an MBMS bearer context.

The MBMS GW1 stores the session parameters and the MBMS Control Plane Node List into the MBMS Bearer Context and allocates the Transport Network IP Multicast Address and the User Plane Transport GTP-TEID between the base stations (eNB1 and eNB2) and the MBMS GW1. The IP multicast address is used for user plane transmission. In the second embodiment, it is a specific multicast address of eNB1 and eNB2. The MBMS GW1 sends a Session Start Request message to the MME in the MBMS Control Plane Node List. The session start request message includes TMGI, QoS, a cell identity list of V2X message broadcasts under eNB1 and eNB2, a transport network IP multicast address, and a user plane transport GTP-TEID between the base stations (eNB1 and eNB2) and MBMS GW1.

Step 706: The MME sends an MBMS Session Start Request message to the MCEs of the serving eNB1 and the eNB2, where the MBMS Session Start Request message carries the user plane between the TMGI, the IP multicast address, and the base station (ie, eNB1 and eNB2) and the MBMS GW1. A cell identity list for transmitting V2X message broadcasts under GTP-TEID, eNB1, and eNB2.

Step 707: The MCE sends an MBMS Session Start Request message to eNB1 and eNB2, respectively. The MBMS session start request message carries the TMGI, the IP multicast address, the user plane transmission GTP-TEID between the base station (ie, eNB1 and eNB2) and the MBMS GW1, the cell identifier list of the V2X message broadcast under the eNB1 and the eNB2, and the MBMS. The QoS parameters carried.

Step 708: eNB1 and eNB2 return an MBMS Session Start Response message to the MCE to confirm receipt of the MBMS Session Start Request.

Step 709: The MCE returns an MBMS Session Start Response message to the MME to confirm receipt of the MBMS Session Start Request.

Step 710: The MME stores the session parameters and the identifiers of the eNB1 and the eNB2 as the downstream nodes in the MBMS bearer context, and returns an MBMS Session Start Response message to the MBMS GW1.

Step 711: The eNB1 establishes the necessary radio resources to transmit the V2X message to the UE of interest, that is, the UE2 in the second embodiment. The eNB2 establishes the necessary radio resources to transmit the V2X message to the UE of interest, UE3 in the second embodiment.

Step 712: The local V2X server 1 sends a V2X message to the BM-SC1 built in the eNB1, and the BM-SC1 sends a V2X message to the MBMS GW1 built in the eNB1, and the MBMS GW1 sends the V2X message to the eNB1 and the eNB2 using the IP multicast address. .

FIG. 8 is a schematic diagram of a network architecture for transmitting a V2V/V2I/V2P service according to a third embodiment of the present invention. As shown in FIG. 8, in the third embodiment, it is assumed that a broadcast area of a V2X message is two adjacent base stations ( As shown in FIG. 8, the cells under eNB1 and eNB2). It is also assumed that UE1 is a terminal that transmits a V2X message under eNB1, UE2 is a terminal that receives a V2X message under eNB1, and UE3 is a terminal that receives a V2X message under eNB2. In the third embodiment, the uplink user plane data channel of the V2X message transmission is: UE1->SIPTO GW1->local V2X server 1; the V2X message to UE2 downlink transmission channel is: local V2X server 1->BM-SC1-> MBMS GW1->eNB1->UE2; V2X message to UE3 downlink transmission channel is: local V2X server 1->BM-SC1->MBMS GW2->eNB2->UE3. FIG. 7 is a schematic diagram of a network architecture of this embodiment.

The third embodiment takes the example that the local MBMS network element is built in the base station. However, the solution in this embodiment is also applicable to a scenario in which local MBMS network elements are deployed in the vicinity of the base station. If the local MBMS network element is deployed in the vicinity of the base station, the MBMS network element (including BM-SC1 and MBMS GW1) built in the eNB1 in this embodiment may be understood as a local MBMS network element that administers several nearby base stations. The MBMS network elements (including BM-SC2 and MBMSGW2) built in eNB2 can be understood as local MBMS network elements that govern several nearby base stations. The V2X message broadcast area is eNB1 and the neighbor base station eNB2, and eNB1 can understand that the V2X message broadcast area is a certain base station under the local MBMS gateways (BM-SC1 and MBMS GW1), and the neighbor base station eNB2 can be understood as a local MBMS gateway ( A base station under BM-SC2 and MBMS GW2).

FIG. 9 is a schematic flowchart of a MBMS session start process for V2X message transmission according to a third embodiment of the present invention. As shown in FIG. 9, the method includes:

Step 901: When the local V2X server 1 receives the V2X message sent by the UE1, the local V2X server 1 determines whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast.

If it is not reusable, the local V2X server 1 sends an Activate MBMS Bearer Request message to the BM-SC1 built in the eNB1 through the MB2 interface to activate the MBMS bearer of the V2X message broadcast cell. The activated MBMS bearer request message carries information such as TMGI (optional), QoS parameters, MBMS broadcast area, and the like. The QoS parameters are matched to the appropriate MBMS bearer parameters; the MBMS broadcast area may refer to the cell identity list of the V2X message broadcasts under eNB1 and eNB2.

In this embodiment, the allocation of TMGI is based on each region, that is, according to different V2X consumption. TMGI is allocated for the broadcast area and/or V2X message type. MBMS is only established when it is carried in different V2X message broadcast areas and/or V2X message types.

Step 902: The BM-SC1 sends an Activate MBMS Bearer Response message to the local V2X Server 1. The MBMS bearer response message carries the TMGI, the service description, and the IP address and port number of the BM-SC1 for the user plane.

If the local V2X server 1 does not judge whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type broadcasted by the V2X message in step 901, a new V2X service is allocated. TMGI, then, BM-SC1 can judge whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area V2X service type of the V2X message broadcast, and if it can be reused, the BM-SC1 rejects the activated MBMS of step 901. Bear the request.

If the local V2X server 1 does not carry the TMGI in the activated MBMS bearer request sent in step 901, the BM-SC1 may determine whether the MBMS bearer that has been established and the MBMS may be re-used according to the geographic area V2X service type broadcasted by the V2X message. The bearer TMGI, if not reusable, allocates a new TMGI value to the BM-SC1. In this embodiment, the allocation of TMGI is based on each region, ie, the TMGI is allocated according to different V2X message broadcast areas and/or V2X message types. MBMS is only established when it is carried in different V2X message broadcast areas and/or V2X message types.

Step 903: The BM-SC1 determines, according to the cell identifier list of the V2X message broadcasted in the activated MBMS bearer request message sent by the local V2X server 1 in step 901, that the BM-SC1 is to be sent. The session request message is sent to the MBMS GW1 built in the eNB1 and the MBMS GW2 built in the eNB2 to trigger the start of the two MBMS sessions, respectively.

First, the BM-SC1 can determine that the cell broadcasted by the V2X message belongs to the eNB1 and the eNB2 according to the cell identity list of the V2X message broadcast in the active MBMS bearer request message sent by the local server 1 in step 901. The BM-SC1 can know that it is built in the eNB1, and knows that the MBMS GW1 is also built in the eNB1. The BM-SC1 can learn that the eNB2 has the built-in MBMS GW2 and the routing information of the MBMS GW2 by using the MBMS related information that is exchanged during the non-UE related signaling interaction between the base stations.

The inter-base station can obtain the MBMS-related information in the process of the non-UE-related signaling interaction. FIG. 10 is a schematic diagram of an embodiment of the inter-base station inter-MBMS-related information in the embodiment of the present invention. As shown in FIG. 10, the non-UE related signaling interaction is performed. The process includes, but is not limited to, one or more of the following: an X2 Setup process, an eNB Configuration Update process.

The MBMS related information includes, but is not limited to, one or more of the following information: whether there is local MBMS network element, routing information of the local MBMS network element. among them,

Whether the local MBMS network element can be indicated by one or more of the following means: including indication information to display whether the local MBMS network element is included in the base station, and routing information including the local MBMS network element is implicitly indicated in the base station. Is there a local MBMS network element?

In the embodiment shown in FIG. 10, eNB1 sends an X2 Setup Request (X2 Setup Request) to eNB2 to initiate an X2 setup procedure. The eNB 2 replies to the eNB 1 with an X2 Setup Response message (X2 Setup Response). The eNB1 may carry the MBMS related information 1 in the X2 setup request message, and the eNB2 may carry the MBMS related information 2 in the X2 setup response message.

The MBMS-related information 1 included in the eNB 1 may be: indication information indicating that the MBMS GW1 ID of the radio network layer identifier of the built-in MBMS GW1 indicating that the eNB 1 has the built-in MBMS GW1, and the transport network layer identifier of the built-in MBMS GW1 are built-in. IP of MBMS GW1 address. The MBMS-related information 2 included in the eNB 2 may be: indication information indicating that the MBMS GW2 ID of the radio network layer identifier of the built-in MBMS GW 2 indicating that the eNB 2 has the built-in MBMS GW 2, and the transport network layer identifier of the built-in MBMS GW 2 are built-in The IP address of the MBMS GW2.

Then, the BM-SC1 transmits a session request message to the MBMS GW2 built in the eNB2 to trigger the MBMS session start procedure. The session request message carries a TMGI, a QoS parameter, a cell identity list of V2X message broadcasts under eNB2, an MBMS control plane node of the MBMS GW1, such as an MME, and the like.

It should be noted that, in the third embodiment, the subsequent steps from step 903 are described by taking the BM-SC1 to establish an MBMS session start process to the MBMS GW2 as an example. The start process of the MBMS session established by the BM-SC1 to the MBMS GW1 is similar, and will not be described here.

Step 904: The MBMS GW2 returns a session start response message to the BM-SC1.

Step 905: The MBMS GW2 establishes an MBMS bearer context.

MBMS GW2 stores the session parameters and the MBMS Control Plane Node List into the MBMS Bearer Context.

The MBMS GW2 transmits a session start request message to the MME in the MBMS Control Plane Node List. The session start request message carries a TMGI, a QoS parameter, a cell identifier list of V2X message broadcasts under eNB2, and the like.

Step 906: The MME sends an MBMS Session Start Request message to the MCE of the serving eNB2. The MBMS session start request message carries a cell identity list of the V2X message broadcast under TMGI and eNB2.

Step 907: The MCE sends an MBMS Session Start Request message to the eNB2. The MBMS session start request message carries the TMGI, the cell identity list of the V2X message broadcast under the eNB2, and the QoS parameter of the MBMS bearer.

Step 908: The eNB2 returns an MBMS Session Start Response message to the MCE to confirm receipt of the MBMS Session Start Request. The MBMS session start response message carries: an IP unicast address of eNB2 and a user plane transmission GTP-TEID between eNB2 and MBMS GW2.

Step 909: The MCE returns an MBMS Session Start Response message to the MME to confirm the reception of the MBMS Session Start Request. The MBMS session start response message carries: an IP unicast address of eNB2 and a user plane transmission GTP-TEID between eNB2 and MBMS GW2.

Step 910: The MME stores the session parameter and the identifier of the eNB2 as the downstream node in the MBMS bearer context, and sends an MBMS Session Start Response message to the MBMS GW2. The MBMS session start response message carries: an IP unicast address of eNB2 and a user plane transmission GTP-TEID between eNB2 and MBMS GW2.

Step 911: The eNB2 establishes the necessary radio resources to transmit the V2X message to the UE of interest, that is, the UE3 in the third embodiment.

Step 912: The local V2X server 1 sends a V2X message to the BM-SC1 built in the eNB1, and the BM-SC1 sends a V2X message to the MBMS GW2 built in the eNB2, and the MBMS GW2 transmits the V2X message to the eNB2 using the IP unicast address.

11 is a schematic diagram of a network architecture for transmitting a V2V/V2I/V2P service according to a fourth embodiment of the present invention. As shown in FIG. 11, in the fourth embodiment, a broadcast area of a V2X message is assumed to be two adjacent base stations ( As shown in FIG. 11, cells under eNB1 and eNB2). It is also assumed that UE1 is a terminal that transmits a V2X message under eNB1, UE2 is a terminal that receives a V2X message under eNB1, and UE3 is a terminal that receives a V2X message under eNB2. In the third embodiment, the uplink user plane data channel of the V2X message transmission is: UE1->SIPTO GW1->local V2X server 1; the V2X message to UE2 downlink transmission channel is: local V2X server 1->BM-SC1-> MBMS GW1->eNB1->UE2; V2X message to UE3 downlink transmission channel is: local V2X server 1->BM-SC2->MBMS GW2->eNB2->UE3.

The fourth embodiment takes the example that the local MBMS network element is built in the base station. However, the solution in this embodiment is also applicable to a scenario in which local MBMS network elements are deployed in the vicinity of the base station. If the local MBMS network element is deployed in the vicinity of the base station, the MBMS network element (including BM-SC1 and MBMS GW1) built in the eNB1 in this embodiment may be understood as a local MBMS network element that administers several nearby base stations. The MBMS network elements (including BM-SC2 and MBMS GW2) built in eNB2 can be understood as local MBMS network elements that govern several nearby base stations. The V2X message broadcast area is eNB1 and the neighbor base station eNB2, and eNB1 can understand that the V2X message broadcast area is a certain base station under the local MBMS gateway (BM-SC1 and MBMS GW1), and the neighbor base station eNB2 It can be understood as a base station under the local MBMS gateways (BM-SC2 and MBMS GW2).

FIG. 12 is a schematic flowchart of a MBMS session start process for V2X message transmission according to a fourth embodiment of the present invention. As shown in FIG. 12, the method includes:

Step 1201: When the local V2X server 1 receives the V2X message sent by the UE1, the local V2X server 1 determines whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast.

If it is not reusable, the local V2X server 1 sends an Activate MBMS Bearer Request message through the MB2 interface to activate the MBMS bearer of the V2X message broadcast cell.

The local V2X server 1 determines, according to the area broadcasted by the V2X message, that an active MBMS bearer request message is to be sent to the BM-SC1 built in the eNB1 and the BM-SC2 built in the eNB2 to respectively initiate two active MBMS bearer processes:

First, the local V2X server 1 determines that the cell in which the V2X message is broadcast belongs to the eNB1 and the eNB2 according to the area broadcasted by the V2X message. The local V2X server 1 can know that it is built in eNB1, and knows that BM-SC1 and MBMS GW1 are also built in eNB1. The local V2X server 1 can learn that the eNB2 has the built-in BM-SC2 through the MBMS related information that is exchanged during the non-UE related signaling interaction between the base stations, and can also obtain the routing information of the BM-SC2.

In this embodiment, it is assumed that the allocation of the TMGI is based on the V2X service allocation, and the MBMS related information may further include the TMGI or V2X service type information supported by the local MBMS network element, and configured to configure the MBMS bearer corresponding to the supported V2X service.

In the embodiment shown in FIG. 10, the eNB1 may carry the MBMS related information 1 in the X2 setup request message sent to the eNB2. The eNB 2 may carry the MBMS related information 2 in the X2 setup response message replied to the eNB1. The MBMS-related information 1 may be: indication information to display a BM-SC1ID, which is a built-in BM-SC1, and a built-in BM-SC1, which has a built-in BM-SC1, and a built-in BM-SC1 transport network layer identifier. That is, the IP address of the built-in BM-SC1. The MBMS-related information 2 may be: indication information indicating that the BM-SC2 ID of the built-in BM-SC2 of the built-in BM-SC2 in the eNB 2, and the transport network layer identifier of the built-in BM-SC2 The IP address of the built-in BM-SC2.

Then, the local V2X server 1 transmits an Activate MBMS Bearer Request message to the BM-SC2 built in the eNB2 to initially activate the MBMB bearer procedure. The activated MBMS bearer request message carries information such as TMGI (optional), QoS parameters, MBMS broadcast area, and the like. The QoS parameters are matched to the appropriate MBMS bearer parameters. The MBMS broadcast area may refer to a cell identity list of V2X message broadcasts under eNB2.

It should be noted that, in the fourth embodiment, the subsequent steps starting from step 1201 are all taking the active MBMS bearer process of the local V2X server 1 to BM-SC2 and the MBMS session start process of the BM-SC2 to MBMS GW2 as an example. Described. The active MBMS bearer process of the V2X server 1 to the BM-SC1 and the MBMS session start process of the BM-SC1 to the MBMS GW1 are similar, and are not described here.

Step 1202: The BM-SC2 returns an active MBMS bearer response message to the local V2X server 1. The MBMS bearer response message carries the TMGI, the service description, and the IP address and port number of the BM-SC2 for the user plane.

If the local V2X server 1 does not judge whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type broadcasted by the V2X message in step 1201, a new V2X service is allocated. TMGI, then, BM-SC2 can judge whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast, and if it can be reused, the BM-SC2 rejects the step 1201. Activate the MBMS bearer request.

If the local V2X server 1 does not carry the TMGI in the activated MBMS bearer request sent in step 1201, the BM-SC2 may determine whether the already established MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast. The TMGI of the MBMS bearer is identified, and if it is not reusable, the BM-SC2 allocates a new TMGI value. In this embodiment, the allocation of TMGI is based on each region, ie, the TMGI is allocated according to different V2X message broadcast areas and/or V2X message types. MBMS is only established when it is carried in different V2X message broadcast areas and/or V2X message types.

Step 1203: The BM-SC2 sends a session request message to the MBMS GW2 built in the eNB2 to trigger the MBMS session start process. The session request message carries a TMGI, a QoS parameter, a cell identity list of V2X message broadcasts under eNB2, an MBMS control plane node of the MBMS GW, such as an MME, and the like.

Step 1204: The MBMS GW2 sends a session start response message to the BM-SC2.

Step 1205: The MBMS GW2 establishes an MBMS bearer context. MBMS GW2 stores the session parameters and the MBMS Control Plane Node List into the MBMS Bearer Context.

MBMS GW2 sends a session start request to the MME in the MBMS control plane node list interest. The session start request message carries a TMGI, a QoS parameter, a cell identifier list of V2X message broadcasts under eNB2, and the like.

Step 1206: The MME sends an MBMS Session Start Request message to the MCE of the serving eNB2. The MBMS session start request message carries a cell identity list of the V2X message broadcast under TMGI and eNB2.

Step 1207: The MCE sends an MBMS Session Start Request message to the eNB2. The MBMS session start request message carries the TMGI, the cell identity list of the V2X message broadcast under the eNB2, and the QoS parameter of the MBMS bearer.

Step 1208: The eNB2 returns an MBMS Session Start Response message to the MCE to confirm receipt of the MBMS Session Start Request. The MBMS session start response message carries: an IP unicast address of eNB2 and a user plane transmission GTP-TEID between eNB2 and MBMS GW2.

Step 1209: The MCE sends an MBMS Session Start Response message to the MME to confirm the reception of the MBMS Session Start Request. The MBMS session start response message carries: an IP unicast address of eNB2 and a user plane transmission GTP-TEID between eNB2 and MBMS GW2.

Step 1210: The MME stores the session parameters and the identifier of the eNB2 as the downstream node in the MBMS bearer context, and sends an MBMS Session Start Response message to the MBMS GW2. The MBMS session start response message carries: an IP unicast address of eNB2 and a user plane transmission GTP-TEID between eNB2 and MBMS GW2.

Step 1211: The eNB2 establishes the necessary radio resources to transmit the V2X message to the UE of interest, that is, the UE3 in this embodiment.

Step 1212: The local V2X server 1 transmits a V2X message to the BM-SC2 built in the eNB2. The BM-SC 2 transmits a V2X message to the MBMS GW2 built in the eNB2. MBMS GW2 sends a V2X message to eNB2 using the IP unicast address.

FIG. 13 is a schematic diagram of a network architecture for transmitting a V2V/V2I/V2P service according to a fifth embodiment of the present invention. As shown in FIG. 13, in the fifth embodiment, it is assumed that a broadcast area of a V2X message is two adjacent base stations ( As shown in Figure 13, the cells under eNB1 and eNB2). It is also assumed that UE1 is a terminal that transmits a V2X message under eNB1, UE2 is a terminal that receives a V2X message under eNB1, and UE3 is a terminal that receives a V2X message under eNB2. In the fifth embodiment, the number of uplink user planes for V2X message transmission According to the channel: UE1->SIPTO GW1->local V2X server 1; V2X message to UE2 downlink transmission channel is: local V2X server 1->BM-SC1->MBMS GW1->eNB1->UE2; V2X message to UE3 downlink The transmission channel is: local V2X server 1-> local V2X server 2->BM-SC2->MBMS GW2->eNB2->UE3.

In the fifth embodiment, the local MBMS network element is built in the base station as an example. However, the solution in this embodiment is also applicable to a scenario in which local MBMS network elements are deployed in the vicinity of the base station. If the local MBMS network element is deployed in the vicinity of the base station, the MBMS network element (including BM-SC1 and MBMS GW1) built in the eNB1 in this embodiment may be understood as a local MBMS network element that administers several nearby base stations. The MBMS network elements (including BM-SC2 and MBMS GW2) built in eNB2 can be understood as local MBMS network elements that govern several nearby base stations. The V2X message broadcast area is eNB1 and the neighbor base station eNB2, and eNB1 can understand that the V2X message broadcast area is a certain base station under the local MBMS gateways (BM-SC1 and MBMS GW1), and the neighbor base station eNB2 can be understood as a local MBMS gateway ( A base station under BM-SC2 and MBMS GW2).

FIG. 14 is a schematic flowchart of a process for starting an MBMS session for V2X message transmission according to a fifth embodiment of the present invention. As shown in FIG. 14, the method includes:

Step 1401: When the local V2X server 1 receives the V2X message sent by the UE1, the local V2X server 1 determines whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast.

The local V2X server 1 determines to send an activated MBMS bearer request message to the BM-SC1 built in the eNB1 according to the area broadcasted by the V2X message to initially activate the MBMS bearer process. At the same time, the local V2X server 1 determines to send a message to the local V2X server 2 according to the area broadcasted by the V2X message, and triggers the local V2X server 2 to send an MBMS bearer process to activate the MBMS bearer request message to the BM-SC2 built in the eNB2 to initially activate the MBMS bearer process.

First, the local V2X server 1 determines that the cell in which the V2X message is broadcast belongs to the eNB1 and the eNB2 according to the area broadcasted by the V2X message. The local V2X server 1 can know that it is built in eNB1, and knows that BM-SC1 and MBMS GW1 are also built in eNB1. The local V2X server 1 can exchange local V2X services through non-UE related signaling interaction between base stations. The server-related information is learned that the eNB 2 has the built-in local V2X server 2, and the routing information of the local V2X server 2 can also be known.

The local V2X server related information may be obtained between the base stations in the process of non-UE related signaling interaction. FIG. 15 is a schematic flowchart of the embodiment of the local V2X server related information exchanged between the base stations in the embodiment of the present invention, as shown in FIG. The process of UE related signaling interaction includes but is not limited to one or more of the following: an X2 Setup process (eNB Setup Update).

The local V2X server related information includes but is not limited to one or more of the following information: whether there is routing information of the local V2X server and the local V2X server. among them,

The built-in local V2X server may be the logical function RSU on the eNB.

In the embodiment shown in FIG. 15, the eNB1 may carry the local V2X server related information 1 in the X2 setup request message sent to the eNB2. The eNB2 may carry the local V2X server related information 2 in the X2 setup response message replied to the eNB1. The local V2X server related information 1 included in the eNB1 may be: indication information to display a local V2X server 1ID of the built-in local V2X server 1 having the built-in local V2X server 1 in the eNB1, that is, a local V2X server 1ID, built-in The transport network layer identifier of the local V2X server 1 is the IP address of the built-in local V2X server 1. The local V2X server related information 2 included in the eNB2 may be: indication information to display a wireless network layer identifier of the built-in local V2X server 2 indicating that the eNB 2 has the built-in local V2X server 2, that is, the local V2X server 2 ID, built-in local. The transport network layer identifier of the V2X server 2 is the IP address of the built-in local V2X server 2.

Then, the local V2X server 1 sends a message to the local V2X server 2 to trigger the local V2X server 2 to send an Activate MBMS Bearer Request message to the BM-SC2 built in the eNB2 to initially activate the MBMS bearer procedure. The message sent by the local V2X server 1 to the local V2X server 2 may carry parameters such as a V2X message type and an MBMS broadcast area. Among them, MBMS is wide The broadcast area may refer to a cell identifier list of V2X message broadcasts under eNB2. The local V2X server 2 will send a message to the local V2X server 1 to confirm receipt of the message.

It should be noted that, in the fifth embodiment, the subsequent steps starting from step 1401 are to send a message to the local V2X server 1 to trigger the active MBMS bearer process of the local V2X server 2 to the BM-SC2 and the BM-SC2 to MBMS. The MBMS session start process of GW2 is described as an example. The active MBMS bearer process of the V2X server 1 to the BM-SC1 and the MBMS session start process of the BM-SC1 to MBMSGW1 are similar, and are not described here.

Step 1402: The local V2X server 2 determines whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type broadcasted by the V2X message received in step 1401.

If it is not reusable, the local V2X server 2 sends an Activate MBMS Bearer Request message to the BM-SC2 built in the eNB2 through the MB2 interface to activate the MBMS bearer of the V2X message broadcast cell. The activated MBMS bearer request message carries TMGI (optional), QoS parameters, MBMS broadcast area, and the like. The QoS parameters are matched to the appropriate MBMS bearer parameters. The MBMS broadcast area may refer to a cell identity list of V2X message broadcasts under eNB2.

In this embodiment, the allocation of TMGI is region-based, that is, the TMGI is allocated according to different V2X message broadcast areas and/or V2X message types. MBMS is only established when it is carried in different V2X message broadcast areas and/or V2X message types.

Step 1403: The BM-SC2 returns an Activate MBMS Bearer Response message to the local V2X Server 2. The MBMS bearer response message carries the TMGI, the service description, and the BM-SC2 for the user. IP address and port number.

If the local V2X server 2 does not judge whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type broadcasted by the V2X message in step 1402, a new V2X service is allocated. TMGI, then, BM-SC2 can judge whether the established MBMS bearer and the TMGI of the MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast, and if it can be reused, the BM-SC2 rejects the step 1402. Activate the MBMS bearer request.

If the activated MBMS bearer request message sent by the local V2X server 2 in step 1402 does not carry the TMGI, the BM-SC2 may determine whether the already established MBMS bearer can be reused according to the geographical area and/or the V2X service type of the V2X message broadcast. The TMGI of the MBMS bearer is identified, and if it is not reusable, the BM-SC2 allocates a new TMGI value. In this embodiment, the allocation of TMGI is based on each region, ie, the TMGI is allocated according to different V2X message broadcast areas and/or V2X message types. MBMS is only established when it is carried in different V2X message broadcast areas and/or V2X message types.

Steps 1404-1413: The specific implementation is consistent with steps 1203-1212 in the fourth embodiment, and details are not described herein again.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to the program instructions. The foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing storage medium includes: a mobile storage device, a random access memory (RAM), a read-only memory (ROM), a magnetic disk, or an optical disk. A medium that can store program code.

Alternatively, the above-described integrated unit of the embodiment of the present invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a stand-alone product. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product, which is stored in a storage medium and includes a plurality of instructions for making A computer device (which may be a personal computer, server, or network device, etc.) performs all or part of the methods described in various embodiments of the present invention. And The foregoing storage medium includes various media that can store program codes, such as a mobile storage device, a RAM, a ROM, a magnetic disk, or an optical disk.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Industrial applicability

The method for implementing a car networking service and the localized network architecture proposed by the embodiments of the present invention include: distinguishing a broadcast area of a V2X message: if the V2X message is a cell broadcast under a neighboring local MBMS-managed base station, triggering to the neighboring After the MBMS bearer of the V2X broadcast area is established, the downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is: local V2X server->first entity>adjacent Base station. The invention satisfies the delay requirement of the vehicle networking business, especially the V2V/V2I/V2P service.

Claims

A method for implementing a car networking service, comprising: distinguishing a broadcast area of a car network communication V2X message;

If the V2X message is a cell broadcast under the base station under the jurisdiction of the adjacent local broadcast multicast service MBMS, triggering the MBMS bearer setup to the adjacent base station;

After the MBMS bearer of the V2X broadcast area is established, the downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is: local V2X server->first entity->adjacent base station.
The method of claim 1, wherein if the V2X message is a cell broadcast under a base station under local MBMS jurisdiction, the method further comprises:

Triggering the establishment of the MBMS bearer of the local MBMS;

After the MBMS bearer of the V2X broadcast area is established, the downlink user plane data path of the V2X message broadcasted by the cell under the local MBMS-managed base station is: local V2X server->local broadcast multicast service center BM-SC->local MBMS GW-> Base station.
The method according to claim 1 or 2, wherein when the local V2X server receives the V2X message, the local V2X server triggers an active MBMS bearer procedure to the local BM-SC; the local BM-SC triggers to The MBMS session start process of the local MBMS GW;

The distinguishing the broadcast area of the V2X message includes: the MBMS GW distinguishes the broadcast area of the V2X message during the start of the MBMS session.
The method according to claim 1 or 2, wherein when the local V2X server receives the V2X message, the local V2X server triggers an active MBMS bearer procedure to the local BM-SC;

The distinguishing the broadcast area of the V2X message includes: when the local BM-SC receives the activated MBMS bearer request message triggered by the local V2X server, the local BM-SC distinguishes the broadcast area of the V2X message and determines whether to Trigger the MBMS session start process to the neighboring local MBMS GW.
The method of claim 1 or 2, wherein the distinguishing the broadcast area of the V2X message comprises:

When the local V2X server receives the V2X message, the local V2X server distinguishes the broadcast area of the V2X message and determines whether to trigger an active MBMS bearer process to the adjacent local BM-SC.
The method of claim 1 or 2, wherein the distinguishing the broadcast area of the V2X message comprises:

When the local V2X server receives the V2X message, the local V2X server distinguishes the broadcast area of the V2X message and determines whether to send a message to the neighboring local V2X server.
The method of claim 2, wherein the triggering the MBMS bearer establishment of the local MBMS comprises:

The local MBMS GW acquires an IP unicast address of the base station, and a user plane transmission GTP tunnel endpoint identifier GTP-TEID between the base station and the local MBMS GW.
The method according to claim 7, wherein the acquiring the IP unicast address of the base station and the user plane transmission GTP-TEID between the base station and the local MBMS GW comprises:

The local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE initiates an MBMS session start request message to the base station; the base station returns an MBMS session start response message to the MCE, and the MCE sends the message to the MME. Returning an MBMS session start response message, and the MME returns a session start response message to the local MBMS GW;

The session start response message and the MBMS session start response message both carry the IP unicast address of the base station, and the user plane transmission GTP-TEID between the base station and the local MBMS GW.
The method of claim 4, wherein the determining whether to trigger an MBMS session start procedure to an adjacent local MBMS GW comprises:

The local BM-SC determines whether to trigger an MBMS session start procedure to an adjacent local MBMS GW according to the MBMS related information learned through the non-UE related signaling process between the base stations.
The method of claim 5 wherein said determining whether to trigger to an adjacent one The active MBMS bearer process of the local BM-SC includes:

The local V2X server determines whether to trigger an MBMS session start process to an adjacent local BM-SC according to the MBMS related information learned through the non-UE related signaling process between the base stations.
The method according to claim 9 or 10, wherein the process of the non-UE related signaling interaction comprises one or more of the following: an X2 setup process, an eNB configuration update process.
The method according to claim 9 or 10, wherein the MBMS related information comprises one or more of the following information: whether there is local MBMS network element, routing information of a local MBMS network element.
The method according to claim 12, wherein the local MBMS network element is indicated by one or more of the following means: including indication information to display whether a local MBMS network element, a route including a local MBMS network element is displayed. Information to implicitly indicate a local MBMS network element;

The routing information of the local MBMS network element includes one or more of the following information: an identifier of the MBMS network element, and an IP address of the MBMS network element.
The method of claim 12, wherein the local MBMS network element comprises one or more of the following: a local MBMS GW, a local BM-SC.
The method of claim 6 wherein said determining whether to send a message to an adjacent local V2X server comprises:

The local V2X server determines whether to send a message to an adjacent local V2X server according to the V2X server related related information learned through the non-UE related signaling process between the base stations.
The method of claim 15, wherein the process of the non-UE related signaling interaction comprises one or more of the following: an X2 setup procedure, an eNB configuration update procedure.
The method of claim 15, wherein the local V2X server related information comprises one or more of the following information: whether there is local V2X server, routing information of the local V2X server.
The method of claim 17, wherein the local V2X server indicates by one or more of the following means: including indication information to display whether to indicate whether there is a local V2X server, including routing information of the local V2X server. Indicates whether there is a local V2X server;

The routing information of the local V2X server includes one or more of the following information: an identifier of the local V2X server, and an IP address of the local V2X server.
The method according to claim 1 or 2, wherein when the local V2X server receives the V2X message, the method further includes:

Determining, by the local V2X server, whether the MBMS bearer that has been established and the temporary mobile group identifier TMGI that identifies the MBMS bearer can be reused according to the geographic area and/or the V2X service type of the V2X message broadcast; or if the local V2X server gives the V2X service Assigning a new TMGI, the local BM-SC determines whether the MBMS bearer that has been established and the TMGI that identifies the MBMS bearer can be reused according to the geographic area and/or the V2X service type of the V2X message broadcast;

If not reusable, the local V2X server sends an activate MBMS bearer request message to the local BM-SC to activate the MBMS bearer of the V2X message broadcast cell; and includes the quality of service QoS parameter and the MBMS broadcast area in the activated MBMS bearer request message.
The method according to claim 19, wherein the activated MBMS bearer request message further carries a TMGI.
The method of claim 20, wherein

The allocation of the TMGI is based on each area: the TMGI is allocated according to different V2X message broadcast areas and/or V2X message types; at this time, the MBMS bearer is established in different V2X message broadcast areas and/or V2X message types;

Or, the allocation of the TMGI is based on each UE: a TMGI is allocated to each UE that has a V2X message transmission requirement; in this case, the MBMS bearer is established when the UE needs to send a V2X message;

Alternatively, the allocation of the TMGI is performed based on the V2X service: the TMGI is allocated for the service of the specific V2X message, and the MBMS broadcast area is a virtual broadcast area; at this time, the MBMS bearer only needs to be established once in the virtual broadcast area.
The method of claim 20, wherein if the allocation of the TMGI is based on V2X traffic;

The MBMS related information further includes: a TMGI or V2X service class supported by a local MBMS network element. Type information, used to configure the MBMS bearer corresponding to the supported V2X service.
The method of claim 1 or 2, wherein the local V2X server is a functional body of an application layer.
The method of claim 23 wherein said local V2X server is located on or outside said base station.
The method of claim 23, wherein the functional layer of the application layer is a logical functional roadside unit RSU or an independent physical entity.
The method according to claim 1 or 2, wherein the triggering the MBMS bearer establishment to the adjacent base station comprises:

The local MBMS GW allocates an IP multicast address of the base station and the neighboring base station according to the V2X message broadcast area, and a user plane transmission GTP-TEID between the base station corresponding to the IP multicast address and the neighboring base station and the local MBMS GW.
The method of claim 26 wherein said assigning comprises:

The local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, where the MCE sends an MBMS session start request message to the base station;

Both the session start request message and the MBMS session start request message carry: an IP multicast address of the base station and the neighboring base station, a base station corresponding to the IP multicast address, and a user plane transmission GTP between the neighboring base station and the local MBMS GW. A list of cell identifiers for V2X message broadcasts under the TEID, base station, and neighboring base stations.
The method of claim 26, wherein the first entity comprises: a local BM-SC, a local MBMS GW;

The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->local BM-SC->local MBMS GW->neighboring base station.
The method according to claim 1 or 2, wherein the triggering the MBMS bearer establishment to the adjacent base station comprises:

The local BM-SC triggers an MBMS session to the local MBMS GW of the neighboring base station The beginning process.
The method of claim 29, wherein the local BM-SC triggers an MBMS session start procedure to a local MBMS GW of a neighboring base station, including:

The session request message sent by the local BM-SC to the neighboring local MBMS GW carries: a cell identity list broadcasted by the V2X message under the neighboring base station;

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, and the MCE The MME returns an MBMS session start response message, and the MME returns a session start response message to the neighboring local MBMS GW;

The session start response message and the MBMS session start response message both carry the IP unicast address of the neighboring base station, the user plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station.
The method of claim 29, wherein the first entity comprises a local BM-SC, an adjacent local MBMS GW;

The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->local BM-SC->adjacent local MBMS GW->neighboring base station.
The method according to claim 1 or 2, wherein the MBMS session process of triggering the adjacent local MBMS comprises:

The local V2X server triggers an active MBMS bearer procedure to an adjacent local BM-SC that triggers an MBMS session start procedure to an adjacent local MBMS GW.
The method of claim 32, wherein the local V2X server triggers an active MBMS bearer procedure to a local BM-SC of a neighboring base station, the local BM-SC of the neighboring base station triggers a local MBMS to a neighboring base station The starting process of the GW MBMS session includes:

The local V2X server carries, in the activated MBMS bearer request message sent to the neighboring local BM-SC, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The neighboring local BM-SC carries, in the session request message sent to the neighboring local MBMS GW, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, The MCE returns an MBMS session start response message to the MME, and the MME returns a session start response message to the neighboring local MBMS GW;

Both the session start response message and the MBMS session start response message carry: an IP unicast address of the neighboring base station, a user plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station.
The method of claim 32, wherein the first entity comprises: an adjacent local BM-SC, an adjacent local MBMS GW;

The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->adjacent local BM-SC->adjacent local MBMS GW->adjacent Base station.
The method according to claim 1 or 2, wherein the MBMS session process of triggering the adjacent local MBMS comprises:

The local V2X server sends a message to an adjacent local V2X server to trigger an active MBMS bearer process initiated by the neighboring local V2X server to the neighboring local BM-SC and a subsequent adjacent local BM-SC to the phase The MBMS session of the neighboring local MBMS GW starts the process.
The method of claim 35, wherein the sending, by the local V2X server, a message to an adjacent local V2X server comprises:

The local V2X server carries the V2X message type and the cell identifier list of the V2X message broadcast of the neighboring base station in the message sent to the neighboring local V2X server; the neighboring local V2X server returns a response to the local V2X server to confirm the pair. Receiving of a message;

The neighboring local V2X server carries, in the activated MBMS bearer request message sent to the neighboring local BM-SC, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The neighboring local BM-SC carries, in the session request message sent to the neighboring local MBMS GW, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, The MCE returns an MBMS session start response message to the MME, and the MME returns a session start response message to the neighboring local MBMS GW;

Both the session start response message and the MBMS session start response message carry: an IP unicast address of the neighboring base station, a user plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station.
The method of claim 35, wherein the first entity comprises: a neighboring local V2X server, an adjacent local BM-SC, and an adjacent local MBMS GW;

The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->adjacent local V2X server->adjacent local BM-SC->adjacent Local MBMS GW-> neighboring base stations.
A localized network architecture, including a local V2X server and an MBMS bearer establishment entity;

a local V2X server, configured to distinguish between broadcast areas of the car network communication V2X message;

An MBMS bearer setup entity is configured to trigger an MBMS bearer setup to an adjacent base station when the V2X message is a cell broadcast under a neighboring local MBMS-managed base station; after the MBMS bearer of the V2X broadcast area is established, the V2X message is in the phase The downlink user plane data path broadcast by the cell under the neighboring local MBMS-managed base station is: local V2X server -> first entity > neighboring base station.
The localized network architecture according to claim 38, wherein the MBMS bearer establishment entity is further configured to: when the V2X message is a cell broadcast under a base station under the local MBMS jurisdiction, triggering an MBMS bearer setup of the local MBMS; After the MBMS bearer of the V2X broadcast area is established, the downlink user plane data path of the V2X message broadcasted by the cell under the local MBMS-managed base station is: local V2X server->local broadcast multicast service center BM-SC->local MBMS GW-> Base station.
The localized network architecture according to claim 38 or 39, wherein the MBMS bearer establishment entity comprises a local BM-SC;

The local V2X server is further configured to: when receiving the V2X message, trigger an activated MBMS bearer process to the local BM-SC; the local BM-SC triggers an MBMS session start process to the local MBMS GW;

or,

The MBMS bearer establishment entity includes a local V2X server;

The local V2X server is further configured to: when receiving the V2X message, trigger an activated MBMS bearer process to the local BM-SC;

or,

The MBMS bearer establishment entity includes a local V2X server;

The local V2X server is further configured to: when receiving the V2X message, distinguish the broadcast area of the V2X message and determine whether to trigger an active MBMS bearer process to the adjacent local BM-SC;

or,

The MBMS bearer establishment entity includes a local V2X server;

The local V2X server is further configured to: when receiving the V2X message, distinguish the broadcast area of the V2X message and determine whether to send a message to the neighboring local V2X server.
The localized network architecture of claim 40, wherein the triggering the MBMS bearer establishment of the local MBMS comprises:

The local MBMS GW acquires an IP unicast address of the base station, and a user plane transmission GTP-TEID between the base station and the local MBMS GW.
The localized network architecture of claim 40, wherein the MBMS bearer establishment entity is specifically configured to:

The local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE initiates an MBMS session start request message to the base station; the base station returns an MBMS session start response message to the MCE, and the MCE sends the message to the MME. Return The MBMS session starts a response message, and the MME returns a session start response message to the local MBMS GW;

The session start response message and the MBMS session start response message both carry the IP unicast address of the base station, and the user plane transmission GTP-TEID between the base station and the local MBMS GW.
The localized network architecture of claim 40, wherein the determining whether to trigger an MBMS session start procedure to an adjacent local MBMS GW comprises:

Determining, by the local BM-SC, whether to trigger an MBMS session start process to an adjacent local MBMS GW according to MBMS related information learned through a non-UE related signaling process between the base stations;

Alternatively, the determining whether to trigger an active MBMS bearer process to an adjacent local BM-SC includes:

Determining, by the local V2X server, whether to trigger an MBMS session start process to an adjacent local BM-SC according to MBMS related information learned through a non-UE related signaling process between the base stations;

or,

The determining whether to send a message to an adjacent local V2X server includes:

The local V2X server determines whether to send a message to an adjacent local V2X server according to the V2X server related related information learned through the non-UE related signaling process between the base stations.
The localized network architecture of claim 38, wherein the MBMS bearer establishment entity is specifically configured to:

The local MBMS GW allocates an IP multicast address of the base station and the neighboring base station according to the V2X message broadcast area, and a user plane transmission GTP-TEID between the base station corresponding to the IP multicast address and the neighboring base station and the local MBMS GW; or

The local BM-SC triggers an MBMS session start procedure to a local MBMS GW of a neighboring base station; or

The local V2X server triggers an active MBMS bearer procedure to an adjacent local BM-SC, and the neighboring local BM-SC triggers an MBMS session start procedure to an adjacent local MBMS GW; or

The local V2X server sends a message to an adjacent local V2X server to trigger the The neighboring local V2X server initiates an active MBMS bearer procedure to the neighboring local BM-SC and an MBMS session start procedure of the subsequent neighboring local BM-SC to the neighboring local MBMS GW.
The localized network architecture of claim 44, wherein the MBMS bearer establishment entity is more specifically for:

The local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the base station; wherein, in the session start request message and the MBMS session start request message, Carrying: an IP multicast address of the base station and the neighboring base station, a base station corresponding to the IP multicast address, and a user plane transmission GTP-TEID between the neighboring base station and the local MBMS GW, and a cell broadcasted by the base station and the V2X message under the neighboring base station List of identifiers;

or,

The session request message sent by the local BM-SC to the neighboring local MBMS GW carries: a cell identity list broadcasted by the V2X message under the neighboring base station;

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, and the MCE The MME returns an MBMS session start response message, and the MME returns a session start response message to the neighboring local MBMS GW. The session start response message and the MBMS session start response message both carry the IP unicast address of the neighboring base station, and the neighboring User plane transmission GTP-TEID between the local MBMS GW and the neighboring base station;

or,

The local V2X server carries, in the activated MBMS bearer request message sent to the neighboring local BM-SC, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The neighboring local BM-SC carries, in the session request message sent to the neighboring local MBMS GW, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session to the neighboring base station. The start request message; the neighboring base station returns an MBMS session start response message to the MCE, the MCE returns an MBMS session start response message to the MME, and the MME returns a session start response message to the neighboring local MBMS GW; wherein, the session start response message and the MBMS session The start response message carries: an IP unicast address of the neighboring base station, a user plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station;

or,

The local V2X server carries the V2X message type and the cell identifier list of the V2X message broadcast of the neighboring base station in the message sent to the neighboring local V2X server; the neighboring local V2X server returns a response to the local V2X server to confirm the pair. Receiving of a message;

The neighboring local V2X server carries, in the activated MBMS bearer request message sent to the neighboring local BM-SC, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The neighboring local BM-SC carries, in the session request message sent to the neighboring local MBMS GW, a cell identifier list broadcasted by the V2X message under the neighboring base station;

The neighboring local MBMS GW sends a session start request message to the MME, and the MME sends an MBMS session start request message to the MCE, and the MCE sends an MBMS session start request message to the neighboring base station; the neighboring base station returns an MBMS session start response message to the MCE, The MCE returns an MBMS session start response message to the MME, and the MME returns a session start response message to the neighboring local MBMS GW. The session start response message and the MBMS session start response message both carry: an IP unicast address of the neighboring base station. The user plane between the adjacent local MBMS GW and the neighboring base station transmits the GTP-TEID.
The localized network architecture of claim 44, wherein the first entity comprises: a local BM-SC, a local MBMS GW; and a downlink user of the V2X message broadcasted by a cell under a neighboring local MBMS-managed base station The specific data path is specifically: local V2X server -> local BM-SC -> local MBMS GW -> neighboring base station;

or,

The first entity includes a local BM-SC, a local MBMS GW of the neighboring base station, and a downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is: a local V2X server-> Local BM-SC->Local MBMS GW->phase of neighboring base stations Neighboring base station

or,

The first entity includes: a neighboring local BM-SC, and a neighboring local MBMS GW; the downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is: local V2X Server->local BM-SC of the neighboring base station>local MBMS GW of the neighboring base station->adjacent base station;

or,

The first entity includes: a local V2X server of a neighboring base station, an adjacent local BM-SC, and an adjacent local MBMS GW;

The downlink user plane data path of the V2X message broadcasted by the cell under the neighboring local MBMS-managed base station is specifically: local V2X server->local V2X server of the neighboring base station->local BM-SC of the neighboring base station-> Local MBMS GW of the neighboring base stations -> neighboring base stations.
The localized network architecture of claim 38 or 39, wherein the localized network architecture is disposed in a base station or disposed outside of a base station.
A computer readable storage medium storing computer executable instructions for performing the method of implementing a car networking service of any of claims 1-37.