WO2017133467A1 - 一种实现车联网业务的方法及本地化网络架构 - Google Patents

一种实现车联网业务的方法及本地化网络架构 Download PDF

Info

Publication number
WO2017133467A1
WO2017133467A1 PCT/CN2017/071647 CN2017071647W WO2017133467A1 WO 2017133467 A1 WO2017133467 A1 WO 2017133467A1 CN 2017071647 W CN2017071647 W CN 2017071647W WO 2017133467 A1 WO2017133467 A1 WO 2017133467A1
Authority
WO
WIPO (PCT)
Prior art keywords
local
mbms
message
base station
server
Prior art date
Application number
PCT/CN2017/071647
Other languages
English (en)
French (fr)
Inventor
吴蕴璐
陈琳
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017133467A1 publication Critical patent/WO2017133467A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • 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.
  • 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
  • V2V Vehicle-to-Vehicle
  • Communication Vehicle-to-Pedestrian Communications
  • V2P Vehicle-to-Pedestrian Communications
  • V2I Vehicle-to-Infrastructure Communications
  • V2N Vehicle-to-Network Communications
  • 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.
  • 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.
  • UL uplink
  • 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.
  • the UE sends a V2X message to other UEs through 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.
  • the V2N service delay requirement is 500 milliseconds.
  • 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.
  • MBMS Broadcast Multicast Multicast Service
  • SC-PTM single-cell point-to-multipoint
  • 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. .
  • V-UEs car-networking user equipments
  • 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.
  • 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;
  • 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;
  • 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 further includes:
  • 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 local V2X server 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.
  • the local V2X server 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.
  • the distinguishing the broadcast area of the V2X message includes:
  • the local V2X server 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 distinguishing the broadcast area of the V2X message includes:
  • the local V2X server 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 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the local MBMS network element includes one or more of the following: a local MBMS GW, a local BM-SC.
  • 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.
  • 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.
  • 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.
  • 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 further includes:
  • the local V2X server 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;
  • 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 activated MBMS bearer request message further carries a TMGI.
  • 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;
  • 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;
  • 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 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.
  • the local V2X server is a function body of an application layer.
  • the local V2X server is disposed on the base station or outside the base station.
  • the function body of the application layer is a logical function roadside unit RSU or an independent physical entity.
  • 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.
  • 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.
  • 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 MBMS bearer establishment triggered to the neighboring base station includes:
  • the local BM-SC triggers an MBMS session start procedure to the local MBMS GW of the neighboring base station.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 MBMS session process of triggering the adjacent local MBMS includes:
  • 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 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 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: neighboring base stations The IP unicast address, the user plane transmission GTP-TEID between the adjacent local MBMS GW and the neighboring base station.
  • 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.
  • 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.
  • 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;
  • 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;
  • 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;
  • 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 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-TEID between the base station and the local MBMS GW.
  • 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. 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 determining whether to trigger an MBMS session start process to an adjacent local MBMS GW includes:
  • the determining whether to trigger an active MBMS bearer process to an adjacent local BM-SC includes:
  • 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 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;
  • 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 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 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;
  • 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 ;
  • 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.
  • the session start response message and the MBMS session start response message both carry: an IP unicast address of the neighboring base station.
  • 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 to the neighboring base station.
  • 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.
  • 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;
  • 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;
  • 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;
  • 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 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.
  • 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.
  • FIG. 2 is a schematic diagram of using LTE cellular uplink and MBMS/SC-PTM downlink transmission in the related art
  • FIG. 3 is a flowchart of a method for implementing a car networking service according to an embodiment of the present invention
  • FIG. 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.
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the local V2X server 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.
  • 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.
  • 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 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, 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 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 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 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 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.
  • the allocation of the TMGI is based on the V2X service
  • 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 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.
  • 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.
  • 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.
  • 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;
  • 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.
  • 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;
  • 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;
  • 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.
  • other technical means may be employed to ensure that the V2X message is broadcast in a partial area of the virtual broadcast area.
  • 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.
  • TMGI Temporary Mobile Group Identity
  • 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;
  • the local MBMS GW 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.
  • 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.
  • 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 .
  • 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.
  • 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 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 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.
  • 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:
  • 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, 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;
  • 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 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.
  • 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.
  • 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, 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;
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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.
  • 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.
  • 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;
  • 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;
  • 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;
  • 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.
  • 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;
  • 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 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:
  • the local V2X server 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 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 information related to the V2X server through the non-UE related signaling process between the base stations.
  • 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,
  • the local BM-SC triggers an MBMS session start procedure to a local MBMS GW of a neighboring base station;
  • 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 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 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.
  • 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 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;
  • 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, 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;
  • 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 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, 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.
  • 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 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;
  • 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;
  • 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).
  • FIG. 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
  • 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
  • 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.
  • the broadcast area of the V2X message is a cell under a single base station.
  • LIPA Local IP Access
  • SIPTO Select IP Traffic Offload
  • 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.
  • 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.
  • TMGI established MBMS bearer and the MBMS bearer
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Session Start Response Session Start Response
  • 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.
  • 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.
  • MCE module control unit
  • 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.
  • GTP Tunnel Endpoint Identifier GTP Tunnel Endpoint Identifier
  • 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.
  • 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. .
  • 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.
  • 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).
  • UE1 is a terminal that transmits a V2X message under eNB1
  • UE2 is a terminal that receives a V2X message under eNB1
  • UE3 is a terminal that receives a V2X message under eNB2.
  • 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.
  • 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.
  • 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.
  • 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.
  • other technical means can be used to ensure that the V2X message is in the virtual broadcast area. Broadcast within the area.
  • 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.
  • 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.
  • the BM-SC1 allocates the value of the TMGI.
  • 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.
  • 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.
  • a broadcast area of a V2X message is two adjacent base stations ( As shown in FIG. 8, the cells under eNB1 and eNB2).
  • UE1 is a terminal that transmits a V2X message under eNB1
  • UE2 is a terminal that receives a V2X message under eNB1
  • UE3 is a terminal that receives a V2X message under eNB2.
  • 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.
  • 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.
  • 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).
  • BM-SC1 and MBMS GW1 local MBMS gateways
  • MBMS GW1 local MBMS gateways
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • other technical means may be employed to ensure that the V2X message is broadcast in a partial area of the virtual broadcast area.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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,
  • 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?
  • 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.
  • 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.
  • 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.
  • step 903 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.
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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:
  • 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.
  • 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,
  • the allocation of the TMGI is based on the V2X service allocation
  • 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.
  • 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?
  • 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 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.
  • 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.
  • 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.
  • 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.
  • other technical means may be employed to ensure that the V2X message is broadcast in a partial area of the virtual broadcast area.
  • 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.
  • 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.
  • 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.
  • 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.
  • the 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.
  • a broadcast area of a V2X message is two adjacent base stations ( As shown in Figure 13, the cells under eNB1 and eNB2).
  • UE1 is a terminal that transmits a V2X message under eNB1
  • UE2 is a terminal that receives a V2X message under eNB1
  • UE3 is a terminal that receives a V2X message under eNB2.
  • 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.
  • the local MBMS network element is built in the base station as an example.
  • 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.
  • 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).
  • BM-SC1 and MBMS GW1 local MBMS gateways
  • MBMS GW1 local MBMS gateways
  • 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 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 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.
  • 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.
  • 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,
  • 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.
  • the built-in local V2X server may be the logical function RSU on the eNB.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • other technical means may be employed to ensure that the V2X message is broadcast in a partial area of the virtual broadcast area.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • RAM random access memory
  • ROM read-only memory
  • magnetic disk or an optical disk.
  • optical disk A medium that can store program code.
  • 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.
  • 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.
  • 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 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本文公布了一种实现车联网业务的方法及本地化网络架构，包括对V2X消息的广播区域进行区分：如果V2X消息是在相邻的本地MBMS管辖的基站下的小区广播，触发到相邻的基站的MBMS承载建立；V2X广播区域的MBMS承载建立后，V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->第一实体>相邻基站。本发明实施例满足了车联网业务，特别是V2V/V2I/V2P业务的延迟需求。

Description

一种实现车联网业务的方法及本地化网络架构 技术领域
本发明实施例涉及但不限于现代车辆技术，尤指一种实现车联网业务的方法及本地化网络架构。
背景技术
随着经济社会的高速发展，中国汽车保有量迅速增长，道路交通事故频繁发生，已成为近年来影响我国公众安全感的重要因素之一，道路交通安全问题已经成为影响社会和谐和改善民生的基本问题之一。中国迫切需要从技术、政策、教育等各方面改善交通安全，其中提升车辆安全设计是其中的重要组成部分。提升车辆安全的技术主要分为被动安全技术和主动安全技术。其中，被动安全技术用于在事故发生后，对车内、车外人员及物品的保护；主动安全技术则用于防止和减少车辆发生事故，避免人员受到伤害。主动安全技术是现代车辆安全技术发展的重点和趋势。
基于通信的碰撞预警***已成为当前各国试图解决道路交通安全问题的一种新的思路。基于通信的碰撞预警***通过利用先进的无线通信技术和新一代信息处理技术，实现车与车、车与路侧基础设施间的实时信息交互，告知彼此目前的状态(包括车辆的位置、速度、加速度、行驶路径等)及获知的道路环境信息，协作感知道路危险状况，以便及时提供多种碰撞预警信息，从而防止道路交通安全事故的发生。
车联网通信(V2X，Vehicle-to-Everything Communications)是指通过装载在车辆上的传感器、车载终端及电子标签提供车辆信息，采用各种通信技术实现车与车通信(V2V，Vehicle-to-Vehicle Communication)、车与人通信(V2P，Vehicle-to-Pedestrian Communications)、车与网络基础设施通信(V2I，Vehicle-to-Infrastructure Communications)，车与网络(V2N，Vehicle-to-Network Communications)通信，并在信息网络平台上对信息进行提取、共享等有效利用，对车辆进行有效的管控和提供综合服务。
目前，3GPP正在讨论基于长期演进(LTE)的V2X。根据当前3GPP的定义，V2X业务是一种使用V2V应用的发送或接收用户设备(UE)参与 的通过3GPP传输的通信业务。基于参与通信的另一方，V2X业务可以进一步分为V2V业务、V2I业务、V2P业务和V2N业务。其中，
V2P业务是指UE之间使用V2P应用通信的业务。V2N业务是指UE和服务实体使用V2N应用通过LTE网络实体进行相互通信的业务。
V2I业务是指UE和路边单元(RSU，Road Side Unit)使用V2I应用进行交互的业务。RSU是支持V2I业务的实体，可以发送V2I业务到使用V2I应用的UE，也可以从使用V2I业务的UE接收V2I业务。RSU可以通过基站(eNB)或者静止的UE实现。如果RSU是通过基站实现的即称为eNB type RSU，如果RSU是通过UE实现的即称为UE type RSU。
V2V业务是指UE之间使用V2V应用通信的业务。V2V包括UE之间直接交互V2V相关应用信息，或者由于V2V直接通信范围的限制，UE之间通过支持V2X业务的基础设施如RSU，应用服务器等，进行V2V相关应用信息交互。
此外，3GPP还讨论了V2V的三种场景，如图1(a)所示的场景1，支持仅仅基于PC5接口的V2V通信。UE通过PC5接口发送V2X消息给局部区域的多个UE；如图1(b)所示的场景2，支持仅仅基于Uu口的V2V通信：UE通过上行链路(UL)上行传输V2X消息到E-UTRAN，E-UTRAN再将该V2X消息通过下行链路(DL)下行广播给局部区域的多个UE。场景3支持使用Uu和PC5接口的V2V通信：如图1(c)所示，UE通过PC5接口发送V2X消息给其他UE，UE type RSU从PC5接口接收到V2X消息后将该V2X消息上行传输给进化型的统一陆地接入网(E-UTRAN，Evolved Universal Terrestrial Radio Access Network)，E-UTRAN将从UE type RSU处接收到的V2X消息下行广播给局部区域的多个UE；或者，如图1(d)所示，UE上行传输V2X消息到E-UTRAN，E-UTRAN从Uu口接收到V2X消息后将该V2X消息传输到一个或者多个UE type RSU，UE type RSU将从E-UTRAN处接收到的V2X消息通过PC5接口发送给局部区域的多个UE。
根据当前的3GPP讨论，V2N业务延迟需求是500毫秒，如图2所示，UE通过LTE蜂窝网络上行发送V2X消息到E-UTRAN(具体路径为：UE->eNB->S-GW->V2X服务器)，E-UTRAN通过现有的广播多播业务 (MBMS，Multimedia Broadcast Multicast Service)技术或者单小区点到多点(SC-PTM，Single-cell point-to multiple point)技术来将V2X消息下行广播给局部区域的多个UE是可以满足时延需求的。而V2V/V2I/V2P业务的延迟需求是100毫秒，使用如图2所示的当前的LTE蜂窝网络(即UE->eNB->S-GW->V2X服务器)进行上行的V2X消息传输和现有的MBMS技术或SC-PTM技术将V2X消息下行广播给局部区域的多个车联网用户设备(V-UE)(下文中简称为UE)，是无法满足V2V/V2I/V2P业务的延迟需求的。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供了一种实现车联网业务的方法及本地化网络架构，能够满足车联网业务的延迟需求。
为了达到本发明目的，本发明实施例提供了一种实现车联网业务的方法，包括：对车联网通信V2X消息的广播区域进行区分；
如果V2X消息是在相邻的本地广播多播业务MBMS管辖的基站下的小区广播，触发到相邻的基站的MBMS承载建立；
V2X广播区域的MBMS承载建立后，V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->第一实体->相邻基站。
可选地，如果所述V2X消息是在本地MBMS管辖的基站下的小区广播，该方法还包括：
触发本地MBMS的MBMS承载建立；
V2X广播区域的MBMS承载建立后，V2X消息在本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->本地广播组播业务中心BM-SC->本地MBMS GW->基站。
可选地，当所述本地V2X服务器接收到V2X消息时，所述本地V2X服务器触发到本地BM-SC的激活MBMS承载过程；所述本地BM-SC触发到 本地MBMS GW的MBMS会话开始过程；
所述对V2X消息的广播区域进行区分包括：在MBMS会话开始过程中，所述MBMS GW对V2X消息的广播区域进行区分。
可选地，当所述本地V2X服务器接收到V2X消息时，所述本地V2X服务器触发到本地BM-SC的激活MBMS承载过程；
所述对V2X消息的广播区域进行区分包括：所述本地BM-SC接收到本地V2X服务器触发的激活MBMS承载请求消息时，所述本地BM-SC对V2X消息的广播区域进行区分并判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程。
可选地，所述对V2X消息的广播区域进行区分包括：
当所述本地V2X服务器接收到V2X消息时，所述本地V2X服务器对V2X消息的广播区域进行区分并判断是否要触发到相邻的本地BM-SC的激活MBMS承载过程。
可选地，所述对V2X消息的广播区域进行区分包括：
当所述本地V2X服务器接收到V2X消息时，所述本地V2X服务器对V2X消息的广播区域进行区分并判断是否要向相邻的本地V2X服务器发送消息。
可选地，所述触发本地MBMS的MBMS承载建立包括：
所述本地MBMS GW获取所述基站的IP单播地址，以及所述基站与本地MBMS GW之间的用户面传输GTP隧道端点标识GTP-TEID。
可选地，所述获取基站的IP单播地址，以及基站与本地MBMS GW之间的用户面传输GTP-TEID包括：
所述本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发起MBMS会话开始请求消息；所述基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向所述本地MBMS GW返回会话开始响应消息；其中，
在会话开始响应消息和MBMS会话开始响应消息中均携带有所述基站 的IP单播地址、所述基站与本地MBMS GW之间的用户面传输GTP-TEID。
可选地，所述判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程包括：
所述本地BM-SC根据通过基站间非UE相关信令过程获知的MBMS相关信息，判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程。
可选地，所述判断是否要触发到相邻的本地BM-SC的激活MBMS承载过程包括：
所述本地V2X服务器根据通过基站间非UE相关信令过程获知的MBMS相关信息，判断是否要触发到相邻的本地BM-SC的MBMS会话开始过程。
可选地，所述非UE相关信令交互的过程包括以下的一种或多种：X2建立过程、eNB配置更新过程。
可选地，所述MBMS相关信息包括以下的一种或多种信息：是否有本地MBMS网元、本地MBMS网元的路由信息。
可选地，所述是否有本地MBMS网元通过以下的一种或多种方式指示：包括指示信息来显示指示是否有本地MBMS网元、包括本地MBMS网元的路由信息来隐式指示本地MBMS网元；
所述本地MBMS网元的路由信息包括以下的一种或多种信息：MBMS网元的标识、MBMS网元的IP地址。
可选地，所述本地MBMS网元包括以下一种或多种：本地MBMS GW、本地BM-SC。
可选地，所述判断是否要向相邻的本地V2X服务器发送消息包括：
所述本地V2X服务器根据通过基站间非UE相关信令过程获知的V2X服务器相关相关信息，判断是否要发送到相邻的本地V2X服务器的消息。
可选地，所述非UE相关信令交互的过程包括以下的一种或多种：X2建立过程、eNB配置更新过程。
可选地，所述本地V2X服务器相关信息包括以下的一种或多种信息：是否有本地V2X服务器、本地V2X服务器的路由信息。
可选地，所述是否有本地V2X服务器通过以下的一种或多种方式指示：包括指示信息来显示指示是否有本地V2X服务器、包括本地V2X服务器的路由信息来隐式指示是否有本地V2X服务器；
所述本地V2X服务器的路由信息包括以下的一种或多种信息：本地V2X服务器的标识、本地V2X服务器的IP地址。
可选地，所述当所述本地V2X服务器接收到V2X消息时，该方法还包括：
所述本地V2X服务器根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的临时移动组标识TMGI；或者，如果所述本地V2X服务器给V2X业务分配新的TMGI，则所述本地BM-SC根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI；
如果不可以重用，所述本地V2X服务器向本地BM-SC发送激活MBMS承载请求消息，以激活V2X消息广播小区的MBMS承载；在激活MBMS承载请求消息中包括服务质量QoS参数、MBMS广播区域。
可选地，所述激活MBMS承载请求消息中还携带有TMGI。
可选地，所述TMGI的分配是基于每个区域的：根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI；此时，MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时建立；
或者，所述TMGI的分配是基于每个UE的：分别为每个有V2X消息发送需求的UE分配TMGI；此时，MBMS承载在UE需要发送V2X消息时建立；
或者，所述TMGI的分配是基于V2X业务进行的：为特定的V2X消息的业务分配TMGI，MBMS广播区域是一个虚拟广播区域；此时，MBMS承载只需要在虚拟广播区域建立一次。
可选地，如果所述TMGI的分配是基于V2X业务的；则，
所述MBMS相关信息还包括：本地MBMS网元支持的TMGI或V2X业务类 型信息，用于配置所支持的V2X业务对应的MBMS承载。
可选地，所述本地V2X服务器是应用层的功能体。
可选地，所述本地V2X服务器设置在所述基站上或者基站外。
可选地，所述应用层的功能体是逻辑功能体路边单元RSU或者独立物理实体。
可选地，所述触发到相邻的基站的MBMS承载建立包括：
所述本地MBMS GW根据V2X消息广播区域分配基站和相邻基站的IP多播地址，以及IP多播地址对应的基站和相邻基站与本地MBMS GW之间的用户面传输GTP-TEID。
可选地，所述分配具体包括：
所述本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发送MBMS会话开始请求消息；其中，
在会话开始请求消息和MBMS会话开始请求消息中均携带有：基站和相邻基站的IP多播地址、IP多播地址对应的基站和相邻基站与本地MBMS GW之间的用户面传输GTP-TEID、基站和相邻基站下V2X消息广播的小区标识列表。
可选地，所述第一实体包括：本地BM-SC，本地MBMS GW；
所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->本地BM-SC->本地MBMS GW->相邻基站。
可选地，所述触发到相邻的基站的MBMS承载建立包括：
所述本地BM-SC触发到相邻基站的本地MBMS GW的MBMS会话开始过程。
可选地，所述本地BM-SC触发到相邻基站的本地MBMS GW的MBMS会话开始过程包括：
所述本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携 带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，
在会话开始响应消息和MBMS会话开始响应消息中均携带有相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID。
可选地，所述第一实体包括本地BM-SC，相邻的本地MBMS GW；
所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->本地BM-SC->相邻的本地MBMS GW->相邻基站。
可选地，所述触发相邻的本地MBMS的MBMS会话过程包括：
所述本地V2X服务器触发到相邻的本地BM-SC的激活MBMS承载过程，所述相邻的本地BM-SC触发到相邻的本地MBMS GW的MBMS会话开始过程。
可选地，所述本地V2X服务器触发到相邻基站的本地BM-SC的激活MBMS承载过程，所述相邻基站的本地BM-SC触发到相邻基站的本地MBMS GW的MBMS会话开始过程包括：
所述本地V2X服务器在发送给相邻的本地BM-SC的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
所述相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
所述相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话 开始响应消息；其中，
在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID。
可选地，所述第一实体包括：相邻的本地BM-SC，相邻的本地MBMS GW；
所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻的本地BM-SC->相邻的本地MBMS GW->相邻基站。
可选地，所述触发相邻的本地MBMS的MBMS会话过程包括：
所述本地V2X服务器发送消息给相邻的本地V2X服务器，以触发所述相邻的本地V2X服务器初始到相邻的本地BM-SC的激活MBMS承载过程和后续相邻的本地BM-SC到相邻的本地MBMS GW的MBMS会话开始过程。
可选地，所述本地V2X服务器发送消息给相邻的本地V2X服务器包括：
所述本地V2X服务器在向相邻的本地V2X服务器发送的消息中携带有V2X消息类型、相邻基站下V2X消息广播的小区标识列表；相邻的本地V2X服务器向本地V2X服务器返回响应以确认对消息的接收；
所述相邻的本地V2X服务器在向相邻的本地BM-SC发送的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
所述相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
所述相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，
在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站 的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID。
可选地，所述第一实体包括：相邻的本地V2X服务器，相邻的本地BM-SC以及相邻的本地MBMS GW；
所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻的本地V2X服务器->相邻的本地BM-SC->相邻的本地MBMS GW->相邻基站。
本发明实施例还公开了一种本地化网络架构，至少包括本地V2X服务器、MBMS承载建立实体；其中，
本地V2X服务器，用于对车联网通信V2X消息的广播区域进行区分；
MBMS承载建立实体，用于当V2X消息是在相邻的本地MBMS管辖的基站下的小区广播时，触发到相邻的基站的MBMS承载建立；V2X广播区域的MBMS承载建立后，V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->第一实体>相邻基站。
可选地，所述MBMS承载建立实体还用于：当所述V2X消息是在本地MBMS管辖的基站下的小区广播时，触发本地MBMS的MBMS承载建立；V2X广播区域的MBMS承载建立后，V2X消息在本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->本地广播组播业务中心BM-SC->本地MBMS GW->基站。
可选地，所述MBMS承载建立实体包括有本地BM-SC；
所述本地V2X服务器还用于：接收到V2X消息时，触发到本地BM-SC的激活MBMS承载过程；本地BM-SC触发到本地MBMS GW的MBMS会话开始过程；
或者，
所述MBMS承载建立实体包括有本地V2X服务器；
所述本地V2X服务器还用于：接收到V2X消息时，触发到本地BM-SC的激活MBMS承载过程；
或者，
所述MBMS承载建立实体包括有本地V2X服务器；
所述本地V2X服务器还用于：接收到V2X消息时，对V2X消息的广播区域进行区分并判断是否要触发到相邻的本地BM-SC的激活MBMS承载过程；
或者，
所述MBMS承载建立实体包括有本地V2X服务器；
所述本地V2X服务器还用于：接收到V2X消息时，对V2X消息的广播区域进行区分并判断是否要向相邻的本地V2X服务器发送消息。
可选地，所述触发本地MBMS的MBMS承载建立包括：
所述本地MBMS GW获取所述基站的IP单播地址，以及所述基站与本地MBMS GW之间的用户面传输GTP-TEID。
可选地，所述MBMS承载建立实体具体用于：
所述本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发起MBMS会话开始请求消息；所述基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向所述本地MBMS GW返回会话开始响应消息；其中，
在会话开始响应消息和MBMS会话开始响应消息中均携带有所述基站的IP单播地址、所述基站与本地MBMS GW之间的用户面传输GTP-TEID。
可选地，所述判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程包括：
所述本地BM-SC根据通过基站间非UE相关信令过程获知的MBMS相关信息，判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程；
或者，所述判断是否要触发到相邻的本地BM-SC的激活MBMS承载过程包括：
所述本地V2X服务器根据通过基站间非UE相关信令过程获知的MBMS相关信息，判断是否要触发到相邻的本地BM-SC的MBMS会话开始过程；
或者，
所述判断是否要向相邻的本地V2X服务器发送消息包括：
所述本地V2X服务器根据通过基站间非UE相关信令过程获知的V2X服务器相关相关信息，判断是否要发送到相邻的本地V2X服务器的消息。
可选地，所述MBMS承载建立实体具体用于：
所述本地MBMS GW根据V2X消息广播区域分配基站和相邻基站的IP多播地址，以及IP多播地址对应的基站和相邻基站与本地MBMS GW之间的用户面传输GTP-TEID；或者，
所述本地BM-SC触发到相邻基站的本地MBMS GW的MBMS会话开始过程；或者，
所述本地V2X服务器触发到相邻的本地BM-SC的激活MBMS承载过程，所述相邻的本地BM-SC触发到相邻的本地MBMS GW的MBMS会话开始过程；或者，
所述本地V2X服务器发送消息给相邻的本地V2X服务器，以触发所述相邻的本地V2X服务器初始到相邻的本地BM-SC的激活MBMS承载过程和后续相邻的本地BM-SC到相邻的本地MBMS GW的MBMS会话开始过程。
可选地，所述MBMS承载建立实体更具体用于：
所述本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发送MBMS会话开始请求消息；其中，在会话开始请求消息和MBMS会话开始请求消息中均携带有：基站和相邻基站的IP多播地址、IP多播地址对应的基站和相邻基站与本地MBMS GW之间的用户面传输GTP-TEID、基站和相邻基站下V2X消息广播的小区标识列表；
或者，
所述本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE 发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，在会话开始响应消息和MBMS会话开始响应消息中均携带有相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID；
或者，
所述本地V2X服务器在发送给相邻的本地BM-SC的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
所述相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
所述相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID；
或者，
所述本地V2X服务器在向相邻的本地V2X服务器发送的消息中携带有V2X消息类型、相邻基站下V2X消息广播的小区标识列表；相邻的本地V2X服务器向本地V2X服务器返回响应以确认对消息的接收；
所述相邻的本地V2X服务器在向相邻的本地BM-SC发送的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
所述相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
所述相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开 始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID。
可选地，所述第一实体包括：本地BM-SC，本地MBMS GW；所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->本地BM-SC->本地MBMS GW->相邻基站；
或者，
所述第一实体包括本地BM-SC，相邻基站的本地MBMS GW；所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->本地BM-SC->相邻基站的本地MBMS GW->相邻基站；
或者，
所述第一实体包括：相邻的本地BM-SC，相邻的本地MBMS GW；所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻基站的本地BM-SC->相邻基站的本地MBMS GW->相邻基站；
或者，
所述第一实体包括：相邻基站的本地V2X服务器，相邻的本地BM-SC以及相邻的本地MBMS GW；
所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻基站的本地V2X服务器->相邻基站的本地BM-SC->相邻基站的本地MBMS GW->相邻基站。
可选地，所述本地化网络架构设置在基站中，或者设置在基站外。
本发明实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项的实现车联网业务的方法。
与现有技术相比，本申请技术方案包括：对本地的V2X消息的广播区域 进行区分：如果V2X消息是在相邻的本地MBMS管辖的基站下的小区广播，触发到相邻的基站的MBMS承载建立；V2X广播区域的MBMS承载建立后，V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->第一实体>相邻基站。本发明实施例提供的实现车联网业务的方法，一方面将实现车联网业务的相关实体如V2X服务器、BM-SC、MBMS GW等设置在基站中，缩短了消息的传输时间；另一方面对V2X消息的小区广播类别进行区分，避免了完全统一采用广播多播业务的方式。从而满足了车联网业务，特别是V2V/V2I/V2P业务的延迟需求。
本发明实施例的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本发明而了解。本发明的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1(a)～图(d)为相关技术中V2V业务的四种场景示意图；
图2为相关技术中使用LTE蜂窝上行和MBMS/SC-PTM下行传输的示意图；
图3为本发明实施例实现车联网业务的方法的流程图；
图4(a)为本发明第一实施例中用于传输V2V/V2I/V2P业务的一种本地化网络架构示意图；
图4(b)为本发明第一实施例中用于传输V2V/V2I/V2P业务的另一种本地化网络架构示意图；
图5为本发明第一实施例中用于V2X消息传输的MBMS会话开始过程的流程示意图；
图6为本发明第二实施例中用于传输V2V/V2I/V2P业务的网络架构示意图；
图7为本发明第二实施例中用于V2X消息传输的MBMS会话开始过程的流程示意图；
图8为本发明第三实施例中用于传输V2V/V2I/V2P业务的网络架构示意图；
图9为本发明第三实施例中用于V2X消息传输的MBMS会话开始过程的流程示意图；
图10为本发明基站间交互MBMS相关信息的实施例的示意图；
图11为本发明第四实施例中用于传输V2V/V2I/V2P业务的网络架构示意图；
图12为本发明第四实施例中用于V2X消息传输的MBMS会话开始过程的流程示意图；
图13为本发明第五实施例中用于传输V2V/V2I/V2P业务的网络架构示意图；
图14为本发明第五实施例中用于V2X消息传输的MBMS会话开始过程的流程示意图。
图15为本发明基站间交互本地V2X服务器相关信息的实施例的流程示意图。
本发明的较佳实施方式
以下结合附图及实施例，对本发明进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
为使本发明的目的、技术方案和优点更加清楚明白，下文中将结合附图对本发明的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
图3为本发明实施例实现车联网业务的方法的流程图，如图3所示，包括：
步骤300：对V2X消息的广播区域进行区分。
本步骤中，根据V2X消息的V2X消息广播区域信息可以确定出V2X消息是在本地MBMS管辖的基站下的小区广播，还是在相邻的本地MBMS管辖的基站下的小区广播。
方式一：当本地V2X服务器接收到V2X消息时，本地V2X服务器触发到本地广播组播业务中心(BM-SC)的激活MBMS承载过程；本地BM-SC触发到本地MBMS GW的MBMS会话开始过程。本步骤具体包括：在MBMS会话开始过程中，本地MBMS GW会对V2X消息的广播区域进行区分。
方式二：当本地V2X服务器接收到V2X消息时，本地V2X服务器触发到本地BM-SC的激活MBMS承载过程。本步骤具体包括：本地BM-SC接收到本地V2X服务器触发的激活MBMS承载请求消息时，本地BM-SC会对V2X消息的广播区域进行区分并判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程。
方式三：本步骤具体包括：当本地V2X服务器接收到V2X消息时，本地V2X服务器对V2X消息的广播区域进行区分并判断是否要触发到相邻基站的本地BM-SC的激活MBMS承载过程。
方式四：本步骤具体包括：当本地V2X服务器接收到V2X消息时，本地V2X服务器对V2X消息的广播区域进行区分并判断是否要向相邻基站的本地V2X服务器发送消息。
其中，本步骤方式二中的判断是否要触发到相邻基站的本地MBMS GW的MBMS会话开始过程具体包括：
基站间可以在非UE相关信令交互的过程中获取本地MBMS相关信息；
非UE相关信令交互的过程包括但不限于以下的一种或多种：X2建立过程(X2 Setup)、eNB配置更新过程(eNB Configuration Update)。
MBMS相关信息包括但不限于以下的一种或多种信息：是否有本地MBMS网元、本地MBMS网元的路由信息；其中，
是否有本地MBMS网元可以通过但不限于以下的一种或多种方式指示：包括指示信息来显示指示是否有本地MBMS网元、包括本地MBMS网元的 路由信息来隐式指示是否有本地MBMS网元；
本地MBMS网元的路由信息包括但不限于以下的一种或多种信息：MBMS网元的标识、MBMS网元的IP地址。
本地MBMS网元包括但不限于以下一种或多种：本地MBMS GW、本地BM-SC。
其中，本步骤方式三中的判断是否要触发到相邻的本地BM-SC的激活MBMS承载过程具体包括：
基站间可以在非UE相关信令交互的过程中获取本地MBMS相关信息；
非UE相关信令交互的过程包括但不限于以下的一种或多种：X2建立过程、eNB配置更新过程。
MBMS相关信息包括但不限于以下的一种或多种信息：是否有本地MBMS网元、本地MBMS网元的路由信息；其中，
是否有本地MBMS网元可以通过但不限于以下的一种或多种方式指示：包括指示信息来显示指示是否有本地MBMS网元、包括本地MBMS网元的路由信息来隐式指示是否有本地MBMS网元；
本地MBMS网元的路由信息包括但不限于以下的一种或多种信息：MBMS网元的标识、MBMS网元的IP地址。
内置的MBMS网元包括但不限于以下一种或多种：本地MBMS GW、本地BM-SC。
进一步地，在TMGI的分配是基于V2X业务的，MBMS相关信息还可以包括：本地MBMS网元支持的TMGI或V2X业务类型信息，用于配置所支持的V2X业务对应的MBMS承载。
其中，本步骤方式四中的判断是否要向相邻的本地V2X服务器发送消息具体包括：本地V2X服务器可以通过基站间非UE相关信令过程获知V2X服务器相关相关信息，从而判断是否要发送到相邻的本地V2X服务器的消息。更具体地：
基站间可以在非UE相关信令交互的过程中获取本地V2X服务器相关信息；
非UE相关信令交互的过程包括但不限于以下的一种或多种：X2建立过程、eNB配置更新过程。
本地V2X服务器相关信息包括但不限于以下的一种或多种信息：是否有本地V2X服务器、本地V2X服务器的路由信息；其中，
是否有本地V2X服务器可以通过但不限于以下的一种或多种方式指示：包括指示信息来显示指示是否有本地V2X服务器、包括本地V2X服务器的路由信息来隐式指示是否有本地V2X服务器。
本地V2X服务器的路由信息包括但不限于以下的一种或多种信息：本地V2X服务器的标识、本地V2X服务器的IP地址。
本发明实施例中，本地V2X服务器可以是应用层的功能体。本地V2X服务器设置在基站上或者基站外(附近)。本地V2X服务器是逻辑功能体路边单元RSU或者物理实体。
当本地V2X服务器接收到V2X消息时，该方法还包括：
本地V2X服务器根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的临时移动组标识TMGI；或者，如果本地V2X服务器给V2X业务分配新的TMGI，则本地BM-SC根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI；
如果不可以重用，本地V2X服务器向本地BM-SC发送激活MBMS承载请求消息，以激活V2X消息广播小区的MBMS承载；在激活MBMS承载请求消息中，携带有服务质量QoS参数、MBMS广播区域。进一步地，激活MBMS承载请求消息中还携带有TMGI。其中，
TMGI的分配是基于每个区域的：根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI；此时，MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时才会建立；
或者，TMGI的分配是基于每个UE的：分别为每个有V2X消息发送需求的UE分配TMGI；此时，MBMS承载在UE需要发送V2X消息时才会建立；
或者，TMGI的分配是基于V2X业务进行的：为特定的V2X消息的业务分配TMGI，MBMS广播区域是一个很大的虚拟广播区域，比如城市级别的广播区域等；此时，MBMS承载只需要在虚拟广播区域建立一次。也就是说，当本地BM-SC接收到UE发送的V2X消息，本地BM-SC根据V2X消息的业务类型判断是否可以重用已建立的MBMS承载以及标识MBMS承载的TMGI。这里可采用其他技术手段保证V2X消息在虚拟广播区域的部分区域内广播。
进一步地，如果临时移动组标识(TMGI)的分配是基于V2X业务的，MBMS相关信息还可以包括：本地MBMS网元支持的TMGI或V2X业务类型信息，用于配置所支持的V2X业务对应的MBMS承载。
根据步骤300的判断，一种情况是：如果V2X消息是本地MBMS管辖的基站下的小区广播，那么，
步骤3011：触发本地MBMS的MBMS承载建立。
本地MBMS GW获取基站的IP单播地址，以及基站与本地MBMS GW之间的用户面传输GTP隧道端点标识(GTP-TEID，GTP Tunnel Endpoint Identifier)。具体包括：
本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发起MBMS会话开始请求消息；所述基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向所述本地MBMS GW返回会话开始响应消息；其中，在会话开始响应消息和MBMS会话开始响应消息中均携带有所述基站的IP单播地址、所述基站与本地MBMS GW之间的用户面传输GTP-TEID；
这样，当V2X消息发送到本地MBMS GW时，本地MBMS GW使用IP单播地址将V2X消息发送到相应基站上。
步骤3021：V2X广播区域的MBMS承载建立后，V2X消息在基站下的小区广播的下行用户面数据路径是：本地V2X服务器->本地BM-SC->本地MBMS GW->基站。
或者，
根据步骤300的判断，另一种情况是：如果V2X消息是在相邻的本地 MBMS管辖的基站下的小区广播，那么，
步骤3012：触发到相邻的基站的MBMS承载建立。
相应地，方式一中，本地MBMS GW根据V2X消息广播区域分配基站和相邻基站的IP多播地址，以及IP多播地址对应的基站和相邻基站与本地MBMS GW之间的用户面传输GTP-TEID。具体包括：
本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发送MBMS会话开始请求消息；其中，在会话开始请求消息和MBMS会话开始请求消息中均携带有：基站和相邻基站的IP多播地址、IP多播地址对应的基站和相邻基站与本地MBMS GW之间的用户面传输GTP-TEID、基站和相邻基站下V2X消息广播的小区标识列表。
这样，当V2X消息发送到本地MBMS GW时，本地MBMS GW使用基站和相邻基站的IP多播地址将V2X消息发送到相应的基站和相邻的基站上。
相应地，方式二中，如果V2X消息是相邻的本地MBMS管辖下的小区广播，本地BM-SC触发到相邻的本地MBMS GW的MBMS会话开始过程。具体包括：
本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，
在会话开始响应消息和MBMS会话开始响应消息中均携带有相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID；
这样，当V2X消息发送到相邻基站的本地MBMS GW时，相邻基站的本地MBMS GW使用相邻基站的IP单播地址将V2X消息发送到相应相邻基 站上。
相应地，方式三中，如果V2X消息是相邻的本地MBMS管辖下的小区广播，本地V2X服务器触发到相邻的本地BM-SC的激活MBMS承载过程，相邻的本地BM-SC触发到相邻的本地MBMS GW的MBMS会话开始过程。具体包括：
本地V2X服务器在发送给相邻的本地BM-SC的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，
在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID。
这样，当V2X消息发送到相邻基站的本地MBMS GW时，相邻基站的本地MBMS GW使用相邻基站的IP单播地址发送V2X消息到相应相邻基站上。
相应地，方式四中，如果V2X消息是在相邻的本地V2X服务器下的小区广播的，本地V2X服务器发送消息给相邻的本地V2X服务器，以触发相邻的本地V2X服务器初始到相邻的本地BM-SC的激活MBMS承载过程和后续相邻的本地BM-SC到相邻的本地MBMS GW的MBMS会话开始过程。具体包括：
本地V2X服务器在向相邻的本地V2X服务器发送的消息中携带有V2X消息类型、相邻基站下V2X消息广播的小区标识列表；相邻的本地V2X服务器向本地V2X服务器返回响应以确认对消息的接收；
相邻的本地V2X服务器在向相邻的本地BM-SC发送的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，
在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID。
这样，当V2X消息发送到相邻基站的本地MBMS GW时，相邻基站的本地MBMS GW使用相邻基站的IP单播地址发送V2X消息到相应相邻基站上。
步骤3022：V2X广播区域的MBMS承载建立后，V2X在相邻基站下的小区广播的下行用户面数据路径是：本地V2X服务器->第一实体>相邻基站。
相应地，方式一中，第一实体包括：本地BM-SC，本地MBMS GW。V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->本地BM-SC->本地MBMS GW->相邻基站。
相应地，方式二中，第一实体包括：本地BM-SC，相邻基站的本地MBMS GW。V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->本地BM-SC->相邻的本地MBMS GW->相邻基站。
相应地，方式三中，第一实体包括：相邻基站的本地BM-SC，相邻基站的本地MBMS GW。V2X消息在相邻的本地MBMS管辖的基站的本地MBMS管辖下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻的本地BM-SC->相邻的本地MBMS GW->相邻基站。
相应地，方式四中，第一实体包括：相邻的本地V2X服务器，相邻的本地BM-SC以及相邻的本地MBMS GW。V2X消息在相邻的MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻的本地V2X服务器->相邻的本地BM-SC->相邻的本地MBMS GW->相邻基站。
本发明实施例提供的技术方案中，在本地MBMS架构中，TMGI的分配是基于每个UE进行的，即为每个有V2X消息发送需求的UE均分配TMGI。此时，MBMS承载在UE有V2X消息需要发送时才会建立。本地BM-SC可以通过UE的地理位置确定V2X消息的广播小区列表。
TMGI的分配也可以是基于UE所在小区进行的，即将每个小区看成V2X消息源，以小区为单位分配TMGI。此时，MBMS承载只有在某个小区首次有UE发送V2X消息时才会建立。MBMS广播区域是该小区和所有相邻小区的集合。也就是说，当本地BM-SC接收到UE发送的V2X消息时，本地BM-SC根据UE所在的小区和/或V2X消息的业务类型判断是否可以重用已建立的MBMS承载以及标识MBMS承载的TMGI。
TMGI的分配还可以是基于V2X业务进行的，即为特定的V2X消息的业务分配TMGI，MBMS广播区域是一个很大的虚拟广播区域，比如城市级别的广播区域等。此时，MBMS承载只需要在虚拟广播区域建立一次。也就是说，当本地BM-SC接收到UE发送的V2X消息，本地BM-SC根据V2X消息的业务类型判断是否可以重用已建立的MBMS承载以及标识MBMS承载的TMGI。这里可采用其他技术手段保证V2X消息在虚拟广播区域的部分区域内广播。
本发明实施例提供的实现车联网业务的方法，一方面将实现车联网业务的相关实体如V2X服务器、BM-SC、MBMS GW等设置在基站中或基站附近，缩短了消息的传输时间；另一方面对V2X消息的广播区域进行区分，避免了完全统一采用广播多播业务的方式。从而满足了车联网业务，特别是V2V/V2I/V2P业务的延迟需求。
本发明实施例还提供一种本地化网络架构，至少包括本地V2X服务器、MBMS承载建立实体；其中，
本地V2X服务器，设置为对V2X消息的广播区域进行区分；
MBMS承载建立实体，设置为当V2X消息是在相邻的本地广播多播业务MBMS管辖的基站下的小区广播时，触发到相邻的基站的MBMS承载建立；V2X广播区域的MBMS承载建立后，V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->第一实体>相邻基站。
进一步地，MBMS承载建立实体还设置为：当所述V2X消息是在本地MBMS管辖的基站下的小区广播时，触发本地MBMS的MBMS承载建立；V2X广播区域的MBMS承载建立后，V2X消息在本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->本地广播组播业务中心BM-SC->本地MBMS GW->基站。
当MBMS承载建立实体包括有本地BM-SC；
本地V2X服务器还设置为：接收到V2X消息时，触发到本地BM-SC的激活MBMS承载过程；本地BM-SC触发到本地MBMS GW的MBMS会话开始过程；
或者，
当MBMS承载建立实体包括有本地V2X服务器；
本地V2X服务器还设置为：接收到V2X消息时，触发到本地BM-SC的激活MBMS承载过程；
或者，
当MBMS承载建立实体包括有本地V2X服务器；
本地V2X服务器还设置为：接收到V2X消息时，对V2X消息的广播区域进行区分并判断是否要触发到相邻基站的本地BM-SC的激活MBMS承载过程；
或者，
当MBMS承载建立实体包括有本地V2X服务器；
本地V2X服务器还设置为：接收到V2X消息时，对V2X消息的广播区域进行区分并判断是否要向相邻基站的本地V2X服务器发送消息。
其中，
触发本地MBMS的MBMS承载建立包括：
本地MBMS GW获取基站的IP单播地址，以及基站与本地MBMS GW之间的用户面传输GTP-TEID。具体地，
MBMS承载建立实体具体设置为：
本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发起MBMS会话开始请求消息；所述基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向所述本地MBMS GW返回会话开始响应消息；其中，
在会话开始响应消息和MBMS会话开始响应消息中均携带有所述基站的IP单播地址、所述基站与本地MBMS GW之间的用户面传输GTP-TEID。
其中，
判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程包括：
本地BM-SC根据通过基站间非UE相关信令过程获知MBMS相关信息，判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程；或者，
判断是否要触发到相邻的本地BM-SC的激活MBMS承载过程包括：
所述本地V2X服务器根据通过基站间非UE相关信令过程获知MBMS相关信息，判断是否要触发到相邻的本地BM-SC的MBMS会话开始过程；或者，
所述判断是否要向相邻的本地V2X服务器发送消息包括：
所述本地V2X服务器根据通过基站间非UE相关信令过程获知V2X服务器相关相关信息，判断是否要发送到相邻的本地V2X服务器的消息。
当V2X消息是在相邻的本地MBMS管辖的基站下的小区广播时，
所述MBMS承载建立实体具体设置为：
所述本地MBMS GW根据V2X消息广播区域分配基站和相邻基站的IP多播地址，以及IP多播地址对应的基站和相邻基站与本地MBMS GW之间 的用户面传输GTP-TEID；或者，
所述本地BM-SC触发到相邻基站的本地MBMS GW的MBMS会话开始过程；或者，
所述本地V2X服务器触发到相邻的本地BM-SC的激活MBMS承载过程，所述相邻的本地BM-SC触发到相邻的本地MBMS GW的MBMS会话开始过程；或者，
所述本地V2X服务器发送消息给相邻的本地V2X服务器，以触发所述相邻的本地V2X服务器初始到相邻的本地BM-SC的激活MBMS承载过程和后续相邻的本地BM-SC到相邻的本地MBMS GW的MBMS会话开始过程。
更具体地，MBMS承载建立实体设置为：
本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发送MBMS会话开始请求消息；其中，在会话开始请求消息和MBMS会话开始请求消息中均携带有：基站和相邻基站的IP多播地址、IP多播地址对应的基站和相邻基站与本地MBMS GW之间的用户面传输GTP-TEID、基站和相邻基站下V2X消息广播的小区标识列表；
或者，
本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，在会话开始响应消息和MBMS会话开始响应消息中均携带有相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID；
或者，
本地V2X服务器在发送给相邻的本地BM-SC的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID；
或者，
本地V2X服务器在向相邻的本地V2X服务器发送的消息中携带有V2X消息类型、相邻基站下V2X消息广播的小区标识列表；相邻的本地V2X服务器向本地V2X服务器返回响应以确认对消息的接收；
相邻的本地V2X服务器在向相邻的本地BM-SC发送的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID。
当第一实体包括本地BM-SC，本地MBMS GW时，V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地 V2X服务器->本地BM-SC->本地MBMS GW->相邻基站；
或者，
当第一实体包括本地BM-SC，相邻基站的本地MBMS GW时，V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->本地BM-SC->相邻基站的本地MBMS GW->相邻基站；
或者，
当第一实体包括相邻基站的本地BM-SC，相邻基站的本地MBMS GW时，V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻基站的本地BM-SC->相邻基站的本地MBMS GW->相邻基站；
或者，
当第一实体包括相邻基站的本地V2X服务器，相邻基站的本地BM-SC以及相邻基站的本地MBMS GW时，V2X消息在相邻的的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻基站的本地V2X服务器->相邻基站的本地BM-SC->相邻基站的本地MBMS GW->相邻基站。
本发明实施例中的本地化网络架构可以设置在基站中如图4(a)所示，也可以设置在基站外(附近)如图4(b)所示。
图4(a)为本发明第一实施例中用于传输V2V/V2I/V2P业务的一种本地化网络架构示意图，图4(b)为本发明第一实施例中用于传输V2V/V2I/V2P业务的另一种本地化网络架构示意图。其中，图4(a)所示的是本地V2X服务器、本地MBMS GW和BM-SC是部署在eNB上的，图4(b)所示的是本地V2X服务器、MBMS GW和BM-SC也可以部署在eNB的附近。第一实施例中，假设V2X消息的广播区域是单个基站下的小区。对于上行的单播，可基于现有的本地IP接入(LIPA，Local IP Access)/选择的IP业务分流(SIPTO，Selected IP Traffic Offload)技术。对于下行的广播，将MBMS/SC-PTM的核心网网元如MBMS GW和BM-SC本地化。本地化的MBMS GW和BM-SC 可以内置在eNB上，也可以部署在eNB的附近。本地V2X服务器(Local V2X E-UTRAN Server)可以内置在eNB上，也可以部署在eNB的附近。在第一实施例中，本地BM-SC、本地MBMS GW和本地V2X服务器都是内置在eNB上的。并假设UE1是eNB下发送V2X消息的终端，UE2是eNB下接收V2X消息的终端。V2X消息传输的上行用户面数据通道是：UE1->SIPTO GW->本地V2X服务器；V2X消息传输的下行用户面数据通道是：本地V2X服务器->本地BM-SC->本地MBMS GW->eNB->UE2。
图5为本发明第一实施例中用于V2X消息传输的MBMS会话开始过程的流程示意图，如图5所示，包括：
步骤501：当本地V2X服务器接收到UE1发送的V2X消息，本地V2X服务器根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的(TMGI)。
如果不可以重用，本地V2X服务器通过MB2接口向基站的本地BM-SC发送激活MBMS承载请求(Active MBMS Bearer Request)消息，以激活V2X消息广播小区的MBMS承载。在激活MBMS承载请求消息中，携带有TMGI(可选地)、服务质量(QoS)参数、MBMS广播区域等信息。其中，QoS参数匹配到合适的MBMS承载参数；MBMS广播区域可以是指eNB下V2X消息广播的小区标识列表。
在本实施例中，TMGI的分配是基于每个区域的，即根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI。MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时才会建立。
TMGI的分配也可以是基于每个UE的，即分别为每个有V2X消息发送需求的UE分配TMGI。MBMS承载在UE需要发送V2X消息时才会建立。
TMGI的分配还可以是基于V2X业务进行的，即为特定的V2X消息的业务分配TMGI，MBMS广播区域是一个很大的虚拟广播区域，比如城市级别的广播区域等。此时，MBMS承载只需要在虚拟广播区域建立一次。也就是说，当本地BM-SC接收到UE发送的V2X消息，本地BM-SC根据V2X消息的业务类型判断是否可以重用已建立的MBMS承载以及标识MBMS承载的TMGI。这里可采用其他技术手段保证V2X消息在虚拟广播区域的部分 区域内广播。
步骤502：本地BM-SC向本地V2X服务器返回激活MBMS承载响应(Activate MBMS Bearer Response)消息。在MBMS承载响应消息中，携带有TMGI、服务描述、BM-SC用于用户面的IP地址和端口号。
如果本地V2X服务器并未在步骤501中根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，而是给V2X业务分配了新的TMGI，那么，本地BM-SC可以根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，如果可以重用，本地BM-SC会拒绝步骤501的激活MBMS承载请求并直接进入步骤512。
如果本地V2X服务器在步骤501中发送的激活MBMS承载请求中没有携带TMGI，那么，本地BM-SC可以根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，如果不可以重用，则本地BM-SC分配新的TMGI值。
同样，本实施例中的TMGI的分配是基于每个区域的，即根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI。MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时才会建立。
步骤503：本地BM-SC向基站内置的MBMS GW发送会话请求(Session Start Request)消息，以触发本地MBMS会话开始过程。在会话请求消息中，携带有TMGI、QoS参数、eNB下V2X消息广播的小区标识列表、MBMS GW的MBMS控制面节点如MME等。
步骤504：本地MBMS GW向本地BM-SC返回会话开始响应(Session Start Response)消息。
步骤505：本地MBMS GW建立MBMS承载上下文。
本地MBMS GW将会话参数和MBMS控制面节点列表存储到MBMS承载上下文中。
本地MBMS GW向MBMS控制面节点列表中的MME发送会话开始请求消息，在会话开始请求消息中，携带有TMGI、QoS参数、eNB下V2X消 息广播的小区标识列表、传输网络IP单播地址、C-TEID等。
步骤506：MME向控制该基站的模块控制单元(MCE，Module Control Element)发送MBMS会话开始请求(MBMS session start request)消息。
在MBMS会话开始请求消息中，携带有TMGI、传输网路IP单播地址、eNB和MBMS GW之间的用户面传输的GTP隧道端点标识(GTP-TEID，GTP Tunnel Endpoint Identifier)、eNB下V2X消息广播的小区标识列表。
步骤507：MCE向eNB发送MBMS会话开始请求消息。在MBMS会话开始请求消息中，携带有TMGI、eNB下V2X消息广播的小区标识列表、MBMS承载的QoS参数。
步骤508：eNB向MCE返回MBMS会话开始响应(MBMS Session Start Response)消息，以确认对MBMS会话开始请求的接收。在MBMS会话开始响应消息中携带有：eNB的IP单播地址和eNB与本地MBMS GW之间的用户面传输GTP-TEID。
步骤509：在从eNB处接收到MBMS会话开始响应消息后，MCE向MME返回MBMS会话开始响应消息，以确认对MBMS会话开始请求的接收。在MBMS会话开始响应消息中携带有：eNB的IP单播地址和eNB与本地MBMS GW之间的用户面传输GTP-TEID。
步骤510：MME将会话参数和作为下游节点的eNB标识存储在MBMS承载上下文中，并向本地MBMS GW返回MBMS会话开始响应(MBMS Session Start Response)消息。在MBMS会话开始响应消息中携带有：eNB的IP单播地址和eNB与本地MBMS GW之间的用户面传输GTP-TEID。
步骤511：eNB建立必要无线资源来传输V2X消息给感兴趣的UE，在第一实施例中，感兴趣的UE即UE2。
步骤512：本地V2X服务器发送V2X消息到内置在eNB上的本地BM-SC，本地BM-SC发送V2X消息到内置在eNB上的本地MBMS GW，本地MBMS GW使用IP单播地址发送V2X消息到eNB。
图6为本发明第二实施例中用于传输V2V/V2I/V2P业务的网络架构示意图，如图6所示，在第二实施例中，假设V2X消息的广播区域是两个相邻基 站(如图6所示，eNB1和eNB2)下的小区。并假设UE1是eNB1下发送V2X消息的终端，UE2是eNB1下接收V2X消息的终端，UE3是eNB2下接收V2X消息的终端。在第二实施例中，V2X消息传输的上行用户面数据通道是：UE1->SIPTO GW1->本地V2X服务器1；V2X消息到UE2下行传输通道是：本地V2X服务器1->BM-SC1->MBMS GW1->eNB1->UE2；V2X消息到UE3下行传输通道是：本地V2X服务器1->BM-SC1->MBMS GW1->eNB2->UE3。
图7为本发明第二实施例中用于V2X消息传输的MBMS会话开始过程的流程示意图，如图7所示，包括：
步骤701：当本地V2X服务器1接收到UE1发送的V2X消息，本地V2X服务器1根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI。
如果不可以重用，本地V2X服务器1通过MB2接口向eNB1内置的BM-SC1发送激活MBMS承载请求消息，以激活V2X消息广播的小区的MBMS承载。在激活MBMS承载请求消息中，携带有TMGI(可选地)、QoS参数、MBMS广播区域等信息。QoS参数匹配到合适的MBMS承载参数；MBMS广播区域可以是指eNB1和eNB2下V2X消息广播的小区标识列表。
在本实施例中，TMGI的分配是基于每个区域的，即根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI。MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时才会建立。
TMGI的分配也可以是基于每个UE的，即分别为每个有V2X消息发送需求的UE分配TMGI。MBMS承载在UE需要发送V2X消息时才会建立。
TMGI的分配还可以是基于V2X业务进行的，即为特定的V2X消息的业务分配TMGI，MBMS广播区域是一个很大的虚拟广播区域，比如城市级别的广播区域等。此时，MBMS承载只需要在虚拟广播区域建立一次。也就是说，当本地BM-SC接收到UE发送的V2X消息，本地BM-SC根据V2X消息的业务类型判断是否可以重用已建立的MBMS承载以及标识MBMS承载的TMGI。这里可采用其他技术手段保证V2X消息在虚拟广播区域的部分 区域内广播。
步骤702：BM-SC1向本地V2X服务器1发送激活MBMS承载响应消息。在MBMS承载响应消息中，携带有TMGI、服务描述、BM-SC1用于用户面的IP地址和端口号。
如果步骤701的激活MBMS承载请求消息中携带有TMGI，BM-SC1需要决定是否本地V2X服务器1是被授权使用该TMGI的。如果TMGI不被授权，则BM-SC1会拒绝步骤701的激活MBMS承载请求。
如果步骤701的激活MBMS承载请求消息中没有携带TMGI，BM-SC1会分配TMGI的值。
如果本地V2X服务器1并未在步骤701中根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，而是给V2X业务分配了新的TMGI，那么，BM-SC1可以根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，如果可以重用，BM-SC1会拒绝步骤701的激活MBMS承载请求。
如果本地V2X服务器1在步骤701中发送的激活MBMS承载请求中没有携带TMGI，那么，BM-SC1可以根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，如果不可以重用，则BM-SC1分配新的TMGI值。本实施例中的TMGI的分配是基于每个区域的，即根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI。MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时才会建立。
步骤703：BM-SC1向eNB1内置的MBMS GW1发送会话请求消息，以触发MBMS会话开始过程。在会话请求消息中，携带有TMGI、QoS参数、eNB1和eNB2下V2X消息广播的小区标识列表、MBMS GW1的MBMS控制面节点如MME等。
步骤704：MBMS GW1向BM-SC1发送会话开始响应消息。
步骤705：MBMS GW1建立MBMS承载上下文。
MBMS GW1将会话参数和MBMS控制面节点列表存储到MBMS承载上下文中，并分配传输网络IP多播地址和基站(eNB1和eNB2)与MBMS GW1之间的用户面传输GTP-TEID。其中，IP多播地址用于用户面传输，在第二实施例中，是eNB1和eNB2的一个特定的多播地址。MBMS GW1发送会话开始请求消息给MBMS控制面节点列表中的MME。会话开始请求消息中包括TMGI、QoS、eNB1和eNB2下的V2X消息广播的小区标识列表、传输网络IP多播地址、基站(eNB1和eNB2)与MBMS GW1之间的用户面传输GTP-TEID。
步骤706：MME向服务eNB1和eNB2的MCE发送MBMS会话开始请求消息，在MBMS会话开始请求消息中，携带有TMGI、IP多播地址、基站(即eNB1和eNB2)与MBMS GW1之间的用户面传输GTP-TEID、eNB1和eNB2下的V2X消息广播的小区标识列表。
步骤707：MCE分别向eNB1和eNB2发送MBMS会话开始请求消息。在MBMS会话开始请求消息中，携带有TMGI、IP多播地址、基站(即eNB1和eNB2)与MBMS GW1之间的用户面传输GTP-TEID、eNB1和eNB2下V2X消息广播的小区标识列表、MBMS承载的QoS参数。
步骤708：eNB1和eNB2向MCE返回MBMS会话开始响应消息，以确认对MBMS会话开始请求的接收。
步骤709：MCE向MME返回MBMS会话开始响应消息，以确认对MBMS会话开始请求的接收。
步骤710：MME将会话参数和作为下游节点的eNB1和eNB2的标识存储在MBMS承载上下文中，并向MBMS GW1返回MBMS会话开始响应消息。
步骤711：eNB1建立必要无线资源来传输V2X消息给感兴趣的UE即第二实施例中的UE2。eNB2建立必要无线资源来传输V2X消息给感兴趣的UE即第二实施例中的UE3。
步骤712：本地V2X服务器1发送V2X消息到内置在eNB1上的BM-SC1，BM-SC1发送V2X消息到内置在eNB1上的MBMS GW1，MBMS GW1使用IP多播地址将V2X消息发送到eNB1和eNB2。
图8为本发明第三实施例中用于传输V2V/V2I/V2P业务的网络架构示意图，如图8所示，在第三实施例中，假设V2X消息的广播区域是两个相邻基站(如图8所示，eNB1和eNB2)下的小区。并假设UE1是eNB1下发送V2X消息的终端，UE2是eNB1下接收V2X消息的终端，UE3是eNB2下接收V2X消息的终端。在第三实施例中，V2X消息传输的上行用户面数据通道是：UE1->SIPTO GW1->本地V2X服务器1；V2X消息到UE2下行传输通道是：本地V2X服务器1->BM-SC1->MBMS GW1->eNB1->UE2；V2X消息到UE3下行传输通道是：本地V2X服务器1->BM-SC1->MBMS GW2->eNB2->UE3。图7是本实施例的网络架构示意图。
第三实施例以本地MBMS网元都内置在基站上为例。但是，本实施例的方案也同样适用于本地MBMS网元都部署在基站附近的场景。如果本地MBMS网元是部署在基站附近的，那么，本实施例中内置在eNB1中的MBMS网元(包括BM-SC1和MBMS GW1)可以理解为管辖若干个其附近基站的本地MBMS网元，而内置在eNB2中的MBMS网元(包括BM-SC2和MBMSGW2)可以理解为管辖若干个其附近基站的本地MBMS网元。V2X消息广播区域为eNB1和相邻基站eNB2，eNB1可以理解为V2X消息广播区域是在本地MBMS网关(BM-SC1和MBMS GW1)下的某个基站，相邻基站eNB2可以理解为本地MBMS网关(BM-SC2和MBMS GW2)下的某个基站。
图9为本发明第三实施例中用于V2X消息传输的MBMS会话开始过程的流程示意图，如图9所示，包括：
步骤901：当本地V2X服务器1接收到UE1发送的V2X消息，本地V2X服务器1根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI。
如果不可以重用，本地V2X服务器1会通过MB2接口向eNB1内置的BM-SC1发送激活MBMS承载请求消息，以激活V2X消息广播小区的MBMS承载。在激活MBMS承载请求消息中，携带有TMGI(可选地)、QoS参数、MBMS广播区域等信息。QoS参数匹配到合适的MBMS承载参数；MBMS广播区域可以是指eNB1和eNB2下V2X消息广播的小区标识列表。
在本实施例中，TMGI的分配是基于每个区域的，即根据不同的V2X消 息广播区域和/或V2X消息类型分配TMGI。MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时才会建立。
TMGI的分配也可以是基于每个UE的，即分别为每个有V2X消息发送需求的UE分配TMGI。MBMS承载在UE需要发送V2X消息时才会建立。
TMGI的分配还可以是基于V2X业务进行的，即为特定的V2X消息的业务分配TMGI，MBMS广播区域是一个很大的虚拟广播区域，比如城市级别的广播区域等。此时，MBMS承载只需要在虚拟广播区域建立一次。也就是说，当本地BM-SC接收到UE发送的V2X消息，本地BM-SC根据V2X消息的业务类型判断是否可以重用已建立的MBMS承载以及标识MBMS承载的TMGI。这里可采用其他技术手段保证V2X消息在虚拟广播区域的部分区域内广播。
步骤902：BM-SC1向本地V2X服务器1发送激活MBMS承载响应消息。在MBMS承载响应消息中，携带有TMGI、服务描述、BM-SC1用于用户面的IP地址和端口号。
如果本地V2X服务器1并未在步骤901中根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，而是给V2X业务分配了新的TMGI，那么，BM-SC1可以根据V2X消息广播的地理区域V2X业务类型和判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，如果可以重用，BM-SC1会拒绝步骤901的激活MBMS承载请求。
如果本地V2X服务器1在步骤901中发送的激活MBMS承载请求中没有携带TMGI，那么，BM-SC1可以根据V2X消息广播的地理区域V2X业务类型和判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，如果不可以重用，则BM-SC1分配新的TMGI值。在本实施例中，TMGI的分配是基于每个区域的，即根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI。MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时才会建立。
步骤903：BM-SC1根据本地V2X服务器1在步骤901中发送的激活MBMS承载请求消息中携带的V2X消息广播的小区标识列表，判断出要发 送会话请求消息到eNB1内置的MBMS GW1和eNB2内置的MBMS GW2来分别触发两个MBMS会话开始过程。
首先，BM-SC1根据本地服务器1在步骤901中发送的激活MBMS承载请求消息中携带的V2X消息广播的小区标识列表，可以判断出V2X消息广播的小区是属于eNB1和eNB2的。BM-SC1可以知道自身是内置在eNB1上，并且知道eNB1上还内置有MBMS GW1。BM-SC1可以通过基站间非UE相关信令交互过程中交互的MBMS相关信息获知eNB2是有内置MBMS GW2的，也可以获知MBMS GW2的路由信息。
基站间可以在非UE相关信令交互的过程中获取MBMS相关信息，图10为本发明实施例中基站间交互MBMS相关信息的实施例的示意图，如图10所示，非UE相关信令交互的过程包括但不限于以下的一种或多种：X2建立过程(X2 Setup)、eNB配置更新过程(eNB Configuration Update)。
MBMS相关信息包括但不限于以下的一种或多种信息：是否有本地MBMS网元、本地MBMS网元的路由信息。其中，
是否有本地MBMS网元可以通过但不限于以下的一种或多种方式指示：包括指示信息来显示指示基站中是否有本地MBMS网元、包括本地MBMS网元的路由信息来隐式指示基站中是否有本地MBMS网元。
本地MBMS网元的路由信息包括但不限于以下的一种或多种信息：MBMS网元的标识、MBMS网元的IP地址。
本地MBMS网元包括但不限于以下一种或多种：本地MBMS GW、本地BM-SC。
如图10所示的实施例中，eNB1向eNB2发送X2建立请求消息(X2 Setup Request)来初始X2建立过程。eNB2向eNB1回复X2建立响应消息(X2 Setup Response)。eNB1可以在X2建立请求消息中携带MBMS相关信息1，eNB2可以在X2建立响应消息中携带MBMS相关信息2。
eNB1包含的MBMS相关信息1可以是：指示信息来显示指示eNB1中是有内置的MBMS GW1的、内置的MBMS GW1的无线网络层标识即MBMS GW1 ID、内置的MBMS GW1的传输网络层标识即内置的MBMS GW1的IP 地址。eNB2包含的MBMS相关信息2可以是：指示信息来显示指示eNB2中是有内置的MBMS GW2的、内置的MBMS GW2的无线网络层标识即MBMS GW2 ID、内置的MBMS GW2的传输网络层标识即内置的MBMS GW2的IP地址。
然后，BM-SC1向eNB2内置的MBMS GW2发送会话请求消息来触发MBMS会话开始过程。在会话请求消息中携带有TMGI、QoS参数、eNB2下V2X消息广播的小区标识列表、MBMS GW1的MBMS控制面节点如MME等。
需要说明的是，在第三实施例中，从步骤903开始的之后的步骤都是以BM-SC1建立到MBMS GW2的MBMS会话开始过程为例进行描述的。BM-SC1建立到MBMS GW1的MBMS会话开始过程与之类似，这里不再赘述。
步骤904：MBMS GW2向BM-SC1返回会话开始响应消息。
步骤905：MBMS GW2建立MBMS承载上下文。
MBMS GW2将会话参数和MBMS控制面节点列表存储到MBMS承载上下文中。
MBMS GW2向MBMS控制面节点列表中的MME发送会话开始请求消息。在会话开始请求消息中携带有TMGI、QoS参数、eNB2下的V2X消息广播的小区标识列表等。
步骤906：MME向服务eNB2的MCE发送MBMS会话开始请求消息。在MBMS会话开始请求消息中携带有TMGI、eNB2下的V2X消息广播的小区标识列表。
步骤907：MCE向eNB2发送MBMS会话开始请求消息。在MBMS会话开始请求消息中携带有TMGI、eNB2下V2X消息广播的小区标识列表、MBMS承载的QoS参数。
步骤908：eNB2向MCE返回MBMS会话开始响应消息来确认对MBMS会话开始请求的接收。在MBMS会话开始响应消息中携带有：eNB2的IP单播地址和eNB2与MBMS GW2之间的用户面传输GTP-TEID。
步骤909：MCE向MME返回MBMS会话开始响应消息来确认对MBMS会话开始请求的接收。在MBMS会话开始响应消息中携带有：eNB2的IP单播地址和eNB2与MBMS GW2之间的用户面传输GTP-TEID。
步骤910：MME将会话参数和作为下游节点的eNB2的标识存储在MBMS承载上下文中，并向MBMS GW2发送MBMS会话开始响应消息。在MBMS会话开始响应消息中携带有：eNB2的IP单播地址和eNB2与MBMS GW2之间的用户面传输GTP-TEID。
步骤911：eNB2建立必要无线资源来传输V2X消息给感兴趣的UE即第三实施例中的UE3。
步骤912：本地V2X服务器1发送V2X消息到内置在eNB1上的BM-SC1，BM-SC1发送V2X消息到内置在eNB2上的MBMS GW2，MBMS GW2使用IP单播地址将V2X消息发送到eNB2上。
图11为本发明第四实施例中用于传输V2V/V2I/V2P业务的网络架构示意图，如图11所示，在第四实施例中，假设V2X消息的广播区域是两个相邻基站(如图11中所示，eNB1和eNB2)下的小区。并假设UE1是eNB1下发送V2X消息的终端，UE2是eNB1下接收V2X消息的终端，UE3是eNB2下接收V2X消息的终端。在第三实施例中，V2X消息传输的上行用户面数据通道是：UE1->SIPTO GW1->本地V2X服务器1；V2X消息到UE2下行传输通道是：本地V2X服务器1->BM-SC1->MBMS GW1->eNB1->UE2；V2X消息到UE3下行传输通道是：本地V2X服务器1->BM-SC2->MBMS GW2->eNB2->UE3。
第四实施例以本地MBMS网元都内置在基站上为例。但是，本实施例的方案也同样适用于本地MBMS网元都部署在基站附近的场景。如果本地MBMS网元是部署在基站附近的，那么，本实施例中内置在eNB1中的MBMS网元(包括BM-SC1和MBMS GW1)可以理解为管辖若干个其附近基站的本地MBMS网元，而内置在eNB2中的MBMS网元(包括BM-SC2和MBMS GW2)可以理解为管辖若干个其附近基站的本地MBMS网元。V2X消息广播区域为eNB1和相邻基站eNB2，eNB1可以理解为V2X消息广播区域是在本地MBMS网关(BM-SC1和MBMS GW1)下的某个基站，相邻基站eNB2 可以理解为本地MBMS网关(BM-SC2和MBMS GW2)下的某个基站。
图12为本发明第四实施例中用于V2X消息传输的MBMS会话开始过程的流程示意图，如图12所示，包括：
步骤1201：当本地V2X服务器1接收到UE1发送的V2X消息，本地V2X服务器1根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI。
如果不可以重用，本地V2X服务器1会通过MB2接口发送激活MBMS承载请求消息来激活V2X消息广播小区的MBMS承载。
本地V2X服务器1根据V2X消息广播的区域判断出要发送激活MBMS承载请求消息到eNB1内置的BM-SC1和eNB2内置的BM-SC2来分别初始两个激活MBMS承载过程：
首先，本地V2X服务器1根据V2X消息广播的区域判断出V2X消息广播的小区是属于eNB1和eNB2的。本地V2X服务器1可以知道自己是内置在eNB1上的，并且知道eNB1上还内置有BM-SC1和MBMS GW1。本地V2X服务器1可以通过基站间非UE相关信令交互过程中交互的MBMS相关信息获知eNB2是有内置的BM-SC2的，也可以获知BM-SC2的路由信息。
基站间可以在非UE相关信令交互的过程中获取MBMS相关信息，图10为本发明实施例中基站间交互MBMS相关信息的实施例的示意图，如图10所示，非UE相关信令交互的过程包括但不限于以下的一种或多种：X2建立过程(X2 Setup)、eNB配置更新过程(eNB Configuration Update)。
MBMS相关信息包括但不限于以下的一种或多种信息：是否有本地MBMS网元、本地MBMS网元的路由信息。其中，
本实施例中，假设TMGI的分配是基于V2X业务分配的，MBMS相关信息还可以包括本地MBMS网元支持的TMGI或V2X业务类型信息，用于配置所支持的V2X业务对应的MBMS承载。
是否有本地MBMS网元可以通过但不限于以下的一种或多种方式指示：包括指示信息来显示指示基站中是否有本地MBMS网元、包括本地MBMS网元的路由信息来隐式指示基站中是否有本地MBMS网元。
本地MBMS网元的路由信息包括但不限于以下的一种或多种信息：MBMS网元的标识、MBMS网元的IP地址。
本地MBMS网元包括但不限于以下一种或多种：本地MBMS GW、本地BM-SC。
如图10所示的实施例中，eNB1可以在向eNB2发送的X2建立请求消息中携带MBMS相关信息1。eNB2可以在向eNB1回复的X2建立响应消息中携带MBMS相关信息2。其中，MBMS相关信息1可以是：指示信息来显示指示eNB1中是有内置的BM-SC1的、内置的BM-SC1的无线网络层标识即BM-SC1ID、内置的BM-SC1的传输网络层标识即内置的BM-SC1的IP地址。MBMS相关信息2可以是：指示信息来显示指示eNB2中是有内置的BM-SC2的、内置的BM-SC2的无线网络层标识即BM-SC2 ID、内置的BM-SC2的传输网络层标识即内置的BM-SC2的IP地址。
然后，本地V2X服务器1向eNB2内置的BM-SC2发送激活MBMS承载请求消息来初始激活MBMB承载过程。在激活MBMS承载请求消息中携带有TMGI(可选地)、QoS参数、MBMS广播区域等信息。其中，QoS参数匹配到合适的MBMS承载参数。MBMS广播区域可以是指eNB2下V2X消息广播的小区标识列表。
在本实施例中，TMGI的分配是基于每个区域的，即根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI。MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时才会建立。
TMGI的分配也可以是基于每个UE的，即分别为每个有V2X消息发送需求的UE分配TMGI。MBMS承载在UE需要发送V2X消息时才会建立。
TMGI的分配还可以是基于V2X业务进行的，即为特定的V2X消息的业务分配TMGI，MBMS广播区域是一个很大的虚拟广播区域，比如城市级别的广播区域等。此时，MBMS承载只需要在虚拟广播区域建立一次。也就是说，当本地BM-SC接收到UE发送的V2X消息，本地BM-SC根据V2X消息的业务类型判断是否可以重用已建立的MBMS承载以及标识MBMS承载的TMGI。这里可采用其他技术手段保证V2X消息在虚拟广播区域的部分区域内广播。
需要说明的是，在第四实施例中，从步骤1201开始的之后的步骤都是以本地V2X服务器1到BM-SC2的激活MBMS承载过程和BM-SC2到MBMS GW2的MBMS会话开始过程为例进行描述的。V2X服务器1到BM-SC1的激活MBMS承载过程和BM-SC1到MBMS GW1的MBMS会话开始过程与之类似，这里不再赘述。
步骤1202：BM-SC2向本地V2X服务器1返回激活MBMS承载响应消息。在MBMS承载响应消息中携带有TMGI、服务描述、BM-SC2用于用户面的IP地址和端口号。
如果本地V2X服务器1并未在步骤1201中根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，而是给V2X业务分配了新的TMGI，那么，BM-SC2可以根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，如果可以重用，BM-SC2会拒绝步骤1201的激活MBMS承载请求。
如果本地V2X服务器1在步骤1201中发送的激活MBMS承载请求中没有携带TMGI，那么，BM-SC2可以根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，如果不可以重用，则BM-SC2分配新的TMGI值。在本实施例中，TMGI的分配是基于每个区域的，即根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI。MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时才会建立。
步骤1203：BM-SC2向eNB2内置的MBMS GW2发送会话请求消息来触发MBMS会话开始过程。在会话请求消息中携带有TMGI、QoS参数、eNB2下V2X消息广播的小区标识列表、MBMS GW的MBMS控制面节点如MME等。
步骤1204：MBMS GW2向BM-SC2发送会话开始响应消息。
步骤1205：MBMS GW2建立MBMS承载上下文。MBMS GW2将会话参数和MBMS控制面节点列表存储到MBMS承载上下文中。
MBMS GW2向MBMS控制面节点列表中的MME发送会话开始请求消 息。在会话开始请求消息中携带有TMGI、QoS参数、eNB2下的V2X消息广播的小区标识列表等。
步骤1206：MME向服务eNB2的MCE发送MBMS会话开始请求消息。在MBMS会话开始请求消息中携带有TMGI、eNB2下的V2X消息广播的小区标识列表。
步骤1207：MCE向eNB2发送MBMS会话开始请求消息。在MBMS会话开始请求消息中携带有TMGI、eNB2下V2X消息广播的小区标识列表、MBMS承载的QoS参数。
步骤1208：eNB2向MCE返回MBMS会话开始响应消息来确认对MBMS会话开始请求的接收。在MBMS会话开始响应消息中携带有：eNB2的IP单播地址和eNB2与MBMS GW2之间的用户面传输GTP-TEID。
步骤1209：MCE向MME发送MBMS会话开始响应消息来确认对MBMS会话开始请求的接收。在MBMS会话开始响应消息中携带有：eNB2的IP单播地址和eNB2与MBMS GW2之间的用户面传输GTP-TEID.
步骤1210：MME将会话参数和作为下游节点的eNB2的标识存储在MBMS承载上下文中，并向MBMS GW2发送MBMS会话开始响应消息。在MBMS会话开始响应消息中携带有：eNB2的IP单播地址和eNB2与MBMS GW2之间的用户面传输GTP-TEID。
步骤1211：eNB2建立必要无线资源来传输V2X消息给感兴趣的UE即本实施例中的UE3。
步骤1212：本地V2X服务器1向内置在eNB2上的BM-SC2发送V2X消息。BM-SC2向内置在eNB2上的MBMS GW2发送V2X消息。MBMS GW2使用IP单播地址将V2X消息发送到eNB2上。
图13为本发明第五实施例中用于传输V2V/V2I/V2P业务的网络架构示意图，如图13所示，在第五实施例中，假设V2X消息的广播区域是两个相邻基站(如图13中所示，eNB1和eNB2)下的小区。并假设UE1是eNB1下发送V2X消息的终端，UE2是eNB1下接收V2X消息的终端，UE3是eNB2下接收V2X消息的终端。在第五实施例中，V2X消息传输的上行用户面数 据通道是：UE1->SIPTO GW1->本地V2X服务器1；V2X消息到UE2下行传输通道是：本地V2X服务器1->BM-SC1->MBMS GW1->eNB1->UE2；V2X消息到UE3下行传输通道是：本地V2X服务器1->本地V2X服务器2->BM-SC2->MBMS GW2->eNB2->UE3。
第五实施例以本地MBMS网元都内置在基站上为例。但是，本实施例的方案也同样适用于本地MBMS网元都部署在基站附近的场景。如果本地MBMS网元是部署在基站附近的，那么，本实施例中内置在eNB1中的MBMS网元(包括BM-SC1和MBMS GW1)可以理解为管辖若干个其附近基站的本地MBMS网元，而内置在eNB2中的MBMS网元(包括BM-SC2和MBMS GW2)可以理解为管辖若干个其附近基站的本地MBMS网元。V2X消息广播区域为eNB1和相邻基站eNB2，eNB1可以理解为V2X消息广播区域是在本地MBMS网关(BM-SC1和MBMS GW1)下的某个基站，相邻基站eNB2可以理解为本地MBMS网关(BM-SC2和MBMS GW2)下的某个基站。
图14为本发明第五实施例中用于V2X消息传输的MBMS会话开始过程的流程示意图，如图14所示，包括：
步骤1401：当本地V2X服务器1接收到UE1发送的V2X消息，本地V2X服务器1根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI。
如果不可以重用，本地V2X服务器1会通过MB2接口发送激活MBMS承载请求消息来激活V2X消息广播小区的MBMS承载。
本地V2X服务器1根据V2X消息广播的区域判断出要发送激活MBMS承载请求消息到eNB1内置的BM-SC1来初始激活MBMS承载过程。同时，本地V2X服务器1根据V2X消息广播的区域判断出要发送消息给本地V2X服务器2，触发本地V2X服务器2发送激活MBMS承载请求消息到eNB2内置的BM-SC2来初始激活的MBMS承载过程。
首先，本地V2X服务器1根据V2X消息广播的区域判断出V2X消息广播的小区是属于eNB1和eNB2的。本地V2X服务器1可以知道自己是内置在eNB1上的，并且知道eNB1上还内置有BM-SC1和MBMS GW1。本地V2X服务器1可以通过基站间非UE相关信令交互过程中交互的本地V2X服 务器相关信息获知eNB2是有内置的本地V2X服务器2的，也可以获知本地V2X服务器2的路由信息。
基站间可以在非UE相关信令交互的过程中获取本地V2X服务器相关信息，图15为本发明实施例中基站间交互本地V2X服务器相关信息的实施例的流程示意图，如图15所示，非UE相关信令交互的过程包括但不限于以下的一种或多种：X2建立过程(X2 Setup)、eNB配置更新过程(eNB Configuration Update)。
本地V2X服务器相关信息包括但不限于以下的一种或多种信息：是否有本地V2X服务器、本地V2X服务器的路由信息。其中，
是否有本地V2X服务器可以通过但不限于以下的一种或多种方式指示：包括指示信息来显示指示是否有本地V2X服务器、包括本地V2X服务器的路由信息来隐式指示是否有本地V2X服务器。
本地V2X服务器的路由信息包括但不限于以下的一种或多种信息：本地V2X服务器的标识、本地V2X服务器的IP地址。
内置的本地V2X服务器可能是eNB上的逻辑功能体RSU。
如图15所示的实施例中，eNB1可以在向eNB2发送的X2建立请求消息中携带本地V2X服务器相关信息1。eNB2可以在向eNB1回复的X2建立响应消息中携带本地V2X服务器相关信息2。其中，eNB1包含的本地V2X服务器相关信息1可以是：指示信息来显示指示eNB1中是有内置的本地V2X服务器1的、内置的本地V2X服务器1的无线网络层标识即本地V2X服务器1ID、内置的本地V2X服务器1的传输网络层标识即内置的本地V2X服务器1的IP地址。eNB2包含的本地V2X服务器相关信息2可以是：指示信息来显示指示eNB2中是有内置的本地V2X服务器2的、内置的本地V2X服务器2的无线网络层标识即本地V2X服务器2 ID、内置的本地V2X服务器2的传输网络层标识即内置的本地V2X服务器2的IP地址。
然后，本地V2X服务器1向本地V2X服务器2发送消息，以触发本地V2X服务器2向eNB2内置的BM-SC2发送激活MBMS承载请求消息来初始激活MBMS承载过程。本地V2X服务器1发送给本地V2X服务器2的消息中可以携带有V2X消息类型、MBMS广播区域等参数。其中，MBMS广 播区域可以是指eNB2下V2X消息广播的小区标识列表。本地V2X服务器2会向本地V2X服务器1发送消息以确认消息的接收。
需要说明的是，在第五实施例中，从步骤1401开始的之后的步骤都是以本地V2X服务器1发消息来触发本地V2X服务器2到BM-SC2的激活MBMS承载过程和BM-SC2到MBMS GW2的MBMS会话开始过程为例进行描述的。V2X服务器1到BM-SC1的激活MBMS承载过程和BM-SC1到MBMSGW1的MBMS会话开始过程与之类似，这里不再赘述。
步骤1402：本地V2X服务器2根据从步骤1401中接收到的V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI。
如果不可以重用，本地V2X服务器2会通过MB2接口向eNB2内置的BM-SC2发送激活MBMS承载请求消息来激活V2X消息广播小区的MBMS承载。在激活MBMS承载请求消息中携带有TMGI(可选地)、QoS参数、MBMS广播区域等。其中，QoS参数匹配到合适的MBMS承载参数。MBMS广播区域可以是指eNB2下V2X消息广播的小区标识列表。
在本实施例中，TMGI的分配是基于区域的，即根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI。MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时才会建立。
TMGI的分配也可以是基于每个UE的，即分别为每个有V2X消息发送需求的UE分配TMGI。MBMS承载在UE需要发送V2X消息时才会建立。
TMGI的分配还可以是基于V2X业务进行的，即为特定的V2X消息的业务分配TMGI，MBMS广播区域是一个很大的虚拟广播区域，比如城市级别的广播区域等。此时，MBMS承载只需要在虚拟广播区域建立一次。也就是说，当本地BM-SC接收到UE发送的V2X消息，本地BM-SC根据V2X消息的业务类型判断是否可以重用已建立的MBMS承载以及标识MBMS承载的TMGI。这里可采用其他技术手段保证V2X消息在虚拟广播区域的部分区域内广播。
步骤1403：BM-SC2向本地V2X服务器2返回激活MBMS承载响应消息。在MBMS承载响应消息中携带有TMGI、服务描述、BM-SC2用于用户 面的IP地址和端口号。
如果本地V2X服务器2并未在步骤1402中根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，而是给V2X业务分配了新的TMGI，那么，BM-SC2可以根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，如果可以重用，BM-SC2会拒绝步骤1402的激活MBMS承载请求。
如果本地V2X服务器2在步骤1402中发送的激活MBMS承载请求消息没有携带TMGI，那么，BM-SC2可以根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI，如果不可以重用，则BM-SC2分配新的TMGI值。在本实施例中，TMGI的分配是基于每个区域的，即根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI。MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时才会建立。
步骤1404-1413：具体实现与第四实施例中的步骤1203-1212一致，这里不再赘述。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：移动存储设备、随机存取存储器(RAM，Random Access Memory)、只读存储器(ROM，Read-Only Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
或者，本发明实施例上述集成的单元如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明实施例的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而 前述的存储介质包括：移动存储设备、RAM、ROM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。
工业实用性
本发明实施例提出的实现车联网业务的方法及本地化网络架构，包括对V2X消息的广播区域进行区分：如果V2X消息是在相邻的本地MBMS管辖的基站下的小区广播，触发到相邻的基站的MBMS承载建立；V2X广播区域的MBMS承载建立后，V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->第一实体>相邻基站。本发明满足了车联网业务，特别是V2V/V2I/V2P业务的延迟需求。

Claims (48)

  1. 一种实现车联网业务的方法，包括：对车联网通信V2X消息的广播区域进行区分；
    如果V2X消息是在相邻的本地广播多播业务MBMS管辖的基站下的小区广播，触发到相邻的基站的MBMS承载建立；
    V2X广播区域的MBMS承载建立后，V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->第一实体->相邻基站。
  2. 根据权利要求1所述的方法，其中，如果所述V2X消息是在本地MBMS管辖的基站下的小区广播，该方法还包括：
    触发本地MBMS的MBMS承载建立；
    V2X广播区域的MBMS承载建立后，V2X消息在本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->本地广播组播业务中心BM-SC->本地MBMS GW->基站。
  3. 根据权利要求1或2所述的方法，其中，当所述本地V2X服务器接收到V2X消息时，所述本地V2X服务器触发到本地BM-SC的激活MBMS承载过程；所述本地BM-SC触发到本地MBMS GW的MBMS会话开始过程；
    所述对V2X消息的广播区域进行区分包括：在MBMS会话开始过程中，所述MBMS GW对V2X消息的广播区域进行区分。
  4. 根据权利要求1或2所述的方法，其中，当所述本地V2X服务器接收到V2X消息时，所述本地V2X服务器触发到本地BM-SC的激活MBMS承载过程；
    所述对V2X消息的广播区域进行区分包括：所述本地BM-SC接收到本地V2X服务器触发的激活MBMS承载请求消息时，所述本地BM-SC对V2X消息的广播区域进行区分并判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程。
  5. 根据权利要求1或2所述的方法，其中，所述对V2X消息的广播区域进行区分包括：
    当所述本地V2X服务器接收到V2X消息时，所述本地V2X服务器对V2X消息的广播区域进行区分并判断是否要触发到相邻的本地BM-SC的激活MBMS承载过程。
  6. 根据权利要求1或2所述的方法，其中，所述对V2X消息的广播区域进行区分包括：
    当所述本地V2X服务器接收到V2X消息时，所述本地V2X服务器对V2X消息的广播区域进行区分并判断是否要向相邻的本地V2X服务器发送消息。
  7. 根据权利要求2所述的方法，其中，所述触发本地MBMS的MBMS承载建立包括：
    所述本地MBMS GW获取所述基站的IP单播地址，以及所述基站与本地MBMS GW之间的用户面传输GTP隧道端点标识GTP-TEID。
  8. 根据权利要求7所述的方法，其中，所述获取基站的IP单播地址，以及基站与本地MBMS GW之间的用户面传输GTP-TEID包括：
    所述本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发起MBMS会话开始请求消息；所述基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向所述本地MBMS GW返回会话开始响应消息；其中，
    在会话开始响应消息和MBMS会话开始响应消息中均携带有所述基站的IP单播地址、所述基站与本地MBMS GW之间的用户面传输GTP-TEID。
  9. 根据权利要求4所述的方法，其中，所述判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程包括：
    所述本地BM-SC根据通过基站间非UE相关信令过程获知的MBMS相关信息，判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程。
  10. 根据权利要求5所述的方法，其中，所述判断是否要触发到相邻的 本地BM-SC的激活MBMS承载过程包括：
    所述本地V2X服务器根据通过基站间非UE相关信令过程获知的MBMS相关信息，判断是否要触发到相邻的本地BM-SC的MBMS会话开始过程。
  11. 根据权利要求9或10所述的方法，其中，所述非UE相关信令交互的过程包括以下的一种或多种：X2建立过程、eNB配置更新过程。
  12. 根据权利要求9或10所述的方法，其中，所述MBMS相关信息包括以下的一种或多种信息：是否有本地MBMS网元、本地MBMS网元的路由信息。
  13. 根据权利要求12所述的方法，其中，所述是否有本地MBMS网元通过以下的一种或多种方式指示：包括指示信息来显示指示是否有本地MBMS网元、包括本地MBMS网元的路由信息来隐式指示本地MBMS网元；
    所述本地MBMS网元的路由信息包括以下的一种或多种信息：MBMS网元的标识、MBMS网元的IP地址。
  14. 根据权利要求12所述的方法，其中，所述本地MBMS网元包括以下一种或多种：本地MBMS GW、本地BM-SC。
  15. 根据权利要求6所述的方法，其中，所述判断是否要向相邻的本地V2X服务器发送消息包括：
    所述本地V2X服务器根据通过基站间非UE相关信令过程获知的V2X服务器相关相关信息，判断是否要发送到相邻的本地V2X服务器的消息。
  16. 根据权利要求15所述的方法，其中，所述非UE相关信令交互的过程包括以下的一种或多种：X2建立过程、eNB配置更新过程。
  17. 根据权利要求15所述的方法，其中，所述本地V2X服务器相关信息包括以下的一种或多种信息：是否有本地V2X服务器、本地V2X服务器的路由信息。
  18. 根据权利要求17所述的方法，其中，所述是否有本地V2X服务器通过以下的一种或多种方式指示：包括指示信息来显示指示是否有本地V2X服务器、包括本地V2X服务器的路由信息来隐式指示是否有本地V2X服务器；
    所述本地V2X服务器的路由信息包括以下的一种或多种信息：本地V2X服务器的标识、本地V2X服务器的IP地址。
  19. 根据权利要求1或2所述的方法，其中，所述当所述本地V2X服务器接收到V2X消息时，该方法还包括：
    所述本地V2X服务器根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的临时移动组标识TMGI；或者，如果所述本地V2X服务器给V2X业务分配新的TMGI，则所述本地BM-SC根据V2X消息广播的地理区域和/或V2X业务类型判断是否可以重用已经建立好的MBMS承载以及标识MBMS承载的TMGI；
    如果不可以重用，所述本地V2X服务器向本地BM-SC发送激活MBMS承载请求消息，以激活V2X消息广播小区的MBMS承载；在激活MBMS承载请求消息中包括服务质量QoS参数、MBMS广播区域。
  20. 根据权利要求19所述的方法，其中，所述激活MBMS承载请求消息中还携带有TMGI。
  21. 根据权利要求20所述的方法，其中，
    所述TMGI的分配是基于每个区域的：根据不同的V2X消息广播区域和/或V2X消息类型分配TMGI；此时，MBMS承载在不同的V2X消息广播区域和/或V2X消息类型时建立；
    或者，所述TMGI的分配是基于每个UE的：分别为每个有V2X消息发送需求的UE分配TMGI；此时，MBMS承载在UE需要发送V2X消息时建立；
    或者，所述TMGI的分配是基于V2X业务进行的：为特定的V2X消息的业务分配TMGI，MBMS广播区域是一个虚拟广播区域；此时，MBMS承载只需要在虚拟广播区域建立一次。
  22. 根据权利要求20所述的方法，其中，如果所述TMGI的分配是基于V2X业务的；则，
    所述MBMS相关信息还包括：本地MBMS网元支持的TMGI或V2X业务类 型信息，用于配置所支持的V2X业务对应的MBMS承载。
  23. 根据权利要求1或2所述的方法，其中，所述本地V2X服务器是应用层的功能体。
  24. 根据权利要求23所述的方法，其中，所述本地V2X服务器设置在所述基站上或者基站外。
  25. 根据权利要求23所述的方法，其中，所述应用层的功能体是逻辑功能体路边单元RSU或者独立物理实体。
  26. 根据权利要求1或2所述的方法，其中，所述触发到相邻的基站的MBMS承载建立包括：
    所述本地MBMS GW根据V2X消息广播区域分配基站和相邻基站的IP多播地址，以及IP多播地址对应的基站和相邻基站与本地MBMS GW之间的用户面传输GTP-TEID。
  27. 根据权利要求26所述的方法，其中，所述分配具体包括：
    所述本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发送MBMS会话开始请求消息；其中，
    在会话开始请求消息和MBMS会话开始请求消息中均携带有：基站和相邻基站的IP多播地址、IP多播地址对应的基站和相邻基站与本地MBMS GW之间的用户面传输GTP-TEID、基站和相邻基站下V2X消息广播的小区标识列表。
  28. 根据权利要求26所述的方法，其中，所述第一实体包括：本地BM-SC，本地MBMS GW；
    所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->本地BM-SC->本地MBMS GW->相邻基站。
  29. 根据权利要求1或2所述的方法，其中，所述触发到相邻的基站的MBMS承载建立包括：
    所述本地BM-SC触发到相邻基站的本地MBMS GW的MBMS会话开 始过程。
  30. 根据权利要求29所述的方法，其中，所述本地BM-SC触发到相邻基站的本地MBMS GW的MBMS会话开始过程包括：
    所述本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
    相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，
    在会话开始响应消息和MBMS会话开始响应消息中均携带有相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID。
  31. 根据权利要求29所述的方法，其中，所述第一实体包括本地BM-SC，相邻的本地MBMS GW；
    所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->本地BM-SC->相邻的本地MBMS GW->相邻基站。
  32. 根据权利要求1或2所述的方法，其中，所述触发相邻的本地MBMS的MBMS会话过程包括：
    所述本地V2X服务器触发到相邻的本地BM-SC的激活MBMS承载过程，所述相邻的本地BM-SC触发到相邻的本地MBMS GW的MBMS会话开始过程。
  33. 根据权利要求32所述的方法，其中，所述本地V2X服务器触发到相邻基站的本地BM-SC的激活MBMS承载过程，所述相邻基站的本地BM-SC触发到相邻基站的本地MBMS GW的MBMS会话开始过程包括：
    所述本地V2X服务器在发送给相邻的本地BM-SC的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
    所述相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
    所述相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，
    在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID。
  34. 根据权利要求32所述的方法，其中，所述第一实体包括：相邻的本地BM-SC，相邻的本地MBMS GW；
    所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻的本地BM-SC->相邻的本地MBMS GW->相邻基站。
  35. 根据权利要求1或2所述的方法，其中，所述触发相邻的本地MBMS的MBMS会话过程包括：
    所述本地V2X服务器发送消息给相邻的本地V2X服务器，以触发所述相邻的本地V2X服务器初始到相邻的本地BM-SC的激活MBMS承载过程和后续相邻的本地BM-SC到相邻的本地MBMS GW的MBMS会话开始过程。
  36. 根据权利要求35所述的方法，其中，所述本地V2X服务器发送消息给相邻的本地V2X服务器包括：
    所述本地V2X服务器在向相邻的本地V2X服务器发送的消息中携带有V2X消息类型、相邻基站下V2X消息广播的小区标识列表；相邻的本地V2X服务器向本地V2X服务器返回响应以确认对消息的接收；
    所述相邻的本地V2X服务器在向相邻的本地BM-SC发送的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
    所述相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
    所述相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，
    在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID。
  37. 根据权利要求35所述的方法，其中，所述第一实体包括：相邻的本地V2X服务器，相邻的本地BM-SC以及相邻的本地MBMS GW；
    所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻的本地V2X服务器->相邻的本地BM-SC->相邻的本地MBMS GW->相邻基站。
  38. 一种本地化网络架构，包括本地V2X服务器、MBMS承载建立实体；其中，
    本地V2X服务器，设置为对车联网通信V2X消息的广播区域进行区分；
    MBMS承载建立实体，设置为当V2X消息是在相邻的本地MBMS管辖的基站下的小区广播时，触发到相邻的基站的MBMS承载建立；V2X广播区域的MBMS承载建立后，V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->第一实体>相邻基站。
  39. 根据权利要求38所述的本地化网络架构，其中，所述MBMS承载建立实体还设置为：当所述V2X消息是在本地MBMS管辖的基站下的小区广播时，触发本地MBMS的MBMS承载建立；V2X广播区域的MBMS承载建立后，V2X消息在本地MBMS管辖的基站下的小区广播的下行用户面数据路径是：本地V2X服务器->本地广播组播业务中心BM-SC->本地MBMS GW->基站。
  40. 根据权利要求38或39所述的本地化网络架构，其中，所述MBMS承载建立实体包括有本地BM-SC；
    所述本地V2X服务器还设置为：接收到V2X消息时，触发到本地BM-SC的激活MBMS承载过程；本地BM-SC触发到本地MBMS GW的MBMS会话开始过程；
    或者，
    所述MBMS承载建立实体包括有本地V2X服务器；
    所述本地V2X服务器还设置为：接收到V2X消息时，触发到本地BM-SC的激活MBMS承载过程；
    或者，
    所述MBMS承载建立实体包括有本地V2X服务器；
    所述本地V2X服务器还设置为：接收到V2X消息时，对V2X消息的广播区域进行区分并判断是否要触发到相邻的本地BM-SC的激活MBMS承载过程；
    或者，
    所述MBMS承载建立实体包括有本地V2X服务器；
    所述本地V2X服务器还设置为：接收到V2X消息时，对V2X消息的广播区域进行区分并判断是否要向相邻的本地V2X服务器发送消息。
  41. 根据权利要求40所述的本地化网络架构，其中，所述触发本地MBMS的MBMS承载建立包括：
    所述本地MBMS GW获取所述基站的IP单播地址，以及所述基站与本地MBMS GW之间的用户面传输GTP-TEID。
  42. 根据权利要求40所述的本地化网络架构，其中，所述MBMS承载建立实体具体设置为：
    所述本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发起MBMS会话开始请求消息；所述基站向MCE返回MBMS会话开始响应消息，MCE向MME返回 MBMS会话开始响应消息，MME向所述本地MBMS GW返回会话开始响应消息；其中，
    在会话开始响应消息和MBMS会话开始响应消息中均携带有所述基站的IP单播地址、所述基站与本地MBMS GW之间的用户面传输GTP-TEID。
  43. 根据权利要求40所述的本地化网络架构，其中，所述判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程包括：
    所述本地BM-SC根据通过基站间非UE相关信令过程获知的MBMS相关信息，判断是否要触发到相邻的本地MBMS GW的MBMS会话开始过程；
    或者，所述判断是否要触发到相邻的本地BM-SC的激活MBMS承载过程包括：
    所述本地V2X服务器根据通过基站间非UE相关信令过程获知的MBMS相关信息，判断是否要触发到相邻的本地BM-SC的MBMS会话开始过程；
    或者，
    所述判断是否要向相邻的本地V2X服务器发送消息包括：
    所述本地V2X服务器根据通过基站间非UE相关信令过程获知的V2X服务器相关相关信息，判断是否要发送到相邻的本地V2X服务器的消息。
  44. 根据权利要求38所述的本地化网络架构，其中，所述MBMS承载建立实体具体用于：
    所述本地MBMS GW根据V2X消息广播区域分配基站和相邻基站的IP多播地址，以及IP多播地址对应的基站和相邻基站与本地MBMS GW之间的用户面传输GTP-TEID；或者，
    所述本地BM-SC触发到相邻基站的本地MBMS GW的MBMS会话开始过程；或者，
    所述本地V2X服务器触发到相邻的本地BM-SC的激活MBMS承载过程，所述相邻的本地BM-SC触发到相邻的本地MBMS GW的MBMS会话开始过程；或者，
    所述本地V2X服务器发送消息给相邻的本地V2X服务器，以触发所述 相邻的本地V2X服务器初始到相邻的本地BM-SC的激活MBMS承载过程和后续相邻的本地BM-SC到相邻的本地MBMS GW的MBMS会话开始过程。
  45. 根据权利要求44所述的本地化网络架构，其中，所述MBMS承载建立实体更具体用于：
    所述本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向所述基站发送MBMS会话开始请求消息；其中，在会话开始请求消息和MBMS会话开始请求消息中均携带有：基站和相邻基站的IP多播地址、IP多播地址对应的基站和相邻基站与本地MBMS GW之间的用户面传输GTP-TEID、基站和相邻基站下V2X消息广播的小区标识列表；
    或者，
    所述本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
    相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，在会话开始响应消息和MBMS会话开始响应消息中均携带有相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID；
    或者，
    所述本地V2X服务器在发送给相邻的本地BM-SC的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
    所述相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
    所述相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开 始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID；
    或者，
    所述本地V2X服务器在向相邻的本地V2X服务器发送的消息中携带有V2X消息类型、相邻基站下V2X消息广播的小区标识列表；相邻的本地V2X服务器向本地V2X服务器返回响应以确认对消息的接收；
    所述相邻的本地V2X服务器在向相邻的本地BM-SC发送的激活MBMS承载请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
    所述相邻的本地BM-SC在向相邻的本地MBMS GW发送的会话请求消息中携带有：相邻基站下V2X消息广播的小区标识列表；
    所述相邻的本地MBMS GW向MME发送会话开始请求消息，MME向MCE发送MBMS会话开始请求消息，MCE向相邻基站发送MBMS会话开始请求消息；相邻基站向MCE返回MBMS会话开始响应消息，MCE向MME返回MBMS会话开始响应消息，MME向相邻的本地MBMS GW返回会话开始响应消息；其中，在会话开始响应消息和MBMS会话开始响应消息中均携带有：相邻基站的IP单播地址、相邻的本地MBMS GW和相邻基站之间的用户面传输GTP-TEID。
  46. 根据权利要求44所述的本地化网络架构，其中，所述第一实体包括：本地BM-SC，本地MBMS GW；所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->本地BM-SC->本地MBMS GW->相邻基站；
    或者，
    所述第一实体包括本地BM-SC，相邻基站的本地MBMS GW；所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->本地BM-SC->相邻基站的本地MBMS GW->相 邻基站；
    或者，
    所述第一实体包括：相邻的本地BM-SC，相邻的本地MBMS GW；所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻基站的本地BM-SC->相邻基站的本地MBMS GW->相邻基站；
    或者，
    所述第一实体包括：相邻基站的本地V2X服务器，相邻的本地BM-SC以及相邻的本地MBMS GW；
    所述V2X消息在相邻的本地MBMS管辖的基站下的小区广播的下行用户面数据路径具体是：本地V2X服务器->相邻基站的本地V2X服务器->相邻基站的本地BM-SC->相邻基站的本地MBMS GW->相邻基站。
  47. 根据权利要求38或39所述的本地化网络架构，其中，所述本地化网络架构设置在基站中，或者设置在基站外。
  48. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-37任一项的实现车联网业务的方法。
PCT/CN2017/071647 2016-02-04 2017-01-19 一种实现车联网业务的方法及本地化网络架构 WO2017133467A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610079310.6 2016-02-04
CN201610079310.6A CN107040898A (zh) 2016-02-04 2016-02-04 一种实现车联网业务的方法及本地化网络架构

Publications (1)

Publication Number Publication Date
WO2017133467A1 true WO2017133467A1 (zh) 2017-08-10

Family

ID=59499405

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/071647 WO2017133467A1 (zh) 2016-02-04 2017-01-19 一种实现车联网业务的方法及本地化网络架构

Country Status (2)

Country Link
CN (1) CN107040898A (zh)
WO (1) WO2017133467A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108667668A (zh) * 2018-05-21 2018-10-16 同济大学 一种城市道路场景下基于车联网连通基的通达性路由方法
US11330401B2 (en) 2019-02-06 2022-05-10 At&T Intellectual Property I, L.P. Centrally assisted associations with a local manager by peers in a peer to peer wireless network
EP3909268A4 (en) * 2019-01-11 2022-08-10 Telefonaktiebolaget Lm Ericsson (Publ) SCHEDULING AND PRIORITY MANAGEMENT FOR DATA TRANSMISSION

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109699013B (zh) 2017-10-24 2020-08-25 华为技术有限公司 一种通信***、通信方法及其装置
CN109842854B (zh) * 2017-11-29 2021-01-05 华为技术有限公司 一种报文组播、报文广播方法及设备
CN110557831B (zh) * 2018-06-04 2022-11-04 成都鼎桥通信技术有限公司 一种同播sc-ptm***中控制面信息的传输方法和设备
WO2020002374A1 (en) 2018-06-26 2020-01-02 Huawei Technologies Co., Ltd. Entities and methods for providing multicast/broadcast services in 5g networks
CN111278169B (zh) * 2018-12-27 2022-05-17 维沃移动通信有限公司 切换方法、第一终端及第二终端
CN112104982B (zh) * 2019-06-17 2021-12-31 华为技术有限公司 通信方法及装置
CN111556539B (zh) * 2020-05-13 2024-05-17 腾讯科技（深圳）有限公司 Ue执行的方法及ue、以及smf实体执行的方法及smf实体

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102044145A (zh) * 2009-10-20 2011-05-04 通用汽车环球科技运作公司 车辆与实体通信
WO2015142082A1 (en) * 2014-03-19 2015-09-24 Lg Electronics Inc. Method and apparatus for configuring buffer status report for public safety transmission or vehicle-related transmission in wireless communication system
WO2015147615A1 (en) * 2014-03-28 2015-10-01 Lg Electronics Inc. Method and apparatus for prioritizing d2d transmission and d2d reception in wireless communication system
CN105282688A (zh) * 2015-10-30 2016-01-27 东莞酷派软件技术有限公司 一种信息传输的方法及路侧单元

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102044145A (zh) * 2009-10-20 2011-05-04 通用汽车环球科技运作公司 车辆与实体通信
WO2015142082A1 (en) * 2014-03-19 2015-09-24 Lg Electronics Inc. Method and apparatus for configuring buffer status report for public safety transmission or vehicle-related transmission in wireless communication system
WO2015147615A1 (en) * 2014-03-28 2015-10-01 Lg Electronics Inc. Method and apparatus for prioritizing d2d transmission and d2d reception in wireless communication system
CN105282688A (zh) * 2015-10-30 2016-01-27 东莞酷派软件技术有限公司 一种信息传输的方法及路侧单元

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Consideration on the issues for LTE-based V2X", 3GPP TSG-RAN WG3 MEETING #90 R3-152577, 7 November 2015 (2015-11-07), XP051007449 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108667668A (zh) * 2018-05-21 2018-10-16 同济大学 一种城市道路场景下基于车联网连通基的通达性路由方法
CN108667668B (zh) * 2018-05-21 2020-12-29 同济大学 一种城市道路场景下基于车联网连通基的通达性路由方法
EP3909268A4 (en) * 2019-01-11 2022-08-10 Telefonaktiebolaget Lm Ericsson (Publ) SCHEDULING AND PRIORITY MANAGEMENT FOR DATA TRANSMISSION
US11330401B2 (en) 2019-02-06 2022-05-10 At&T Intellectual Property I, L.P. Centrally assisted associations with a local manager by peers in a peer to peer wireless network

Also Published As

Publication number Publication date
CN107040898A (zh) 2017-08-11

Similar Documents

Publication Publication Date Title
WO2017133467A1 (zh) 一种实现车联网业务的方法及本地化网络架构
US11700552B2 (en) Method and device for switching a serving cell and method and device supporting on-demand system information message
WO2017076037A1 (zh) 车联网v2x业务的发送方法及装置
US9088967B2 (en) Wireless communication system and connection method between user equipment and a mobility management entity
WO2017133624A1 (zh) 车联网通信v2x消息的广播方法及装置、mbms承载的建立方法
CN109892003B (zh) 经由具有中继能力的用户装备ue在远程ue和电信网络之间建立连接的方法和***
WO2017133290A1 (zh) 车联网通信v2x消息的传输方法、装置及***
CN106162777B (zh) 中继节点切换方法及***
CN109417695A (zh) 一种通信路径转换方法及设备
CN106973356B (zh) 传输v2x消息的方法和装置
JP2019520765A (ja) 無線通信システムにおけるネットワークスライスベースのｎｒのためのセル特定手順を実行する方法及び装置
JP2019520766A (ja) 無線通信システムにおけるネットワークスライスベースのｎｒのためのセル特定手順または移動性手順を実行する方法及び装置
WO2017076056A1 (zh) 业务转发方法及装置
CN109565785B (zh) 一种寻呼方法和寻呼设备
CN106341848B (zh) 一种切换方法及装置
US20160374139A1 (en) Method and Device for Mode Switching
KR20180102221A (ko) 무선 통신 시스템에서 v2x 메시지 전송을 위한 자원의 할당을 위한 방법 및 장치
US10728712B2 (en) Methods and apparatuses for supporting wireless communication of vehicle
WO2015004142A1 (en) Method for deciding to handover user equipment in a mobile communicaton network
WO2018028458A1 (zh) 车联网业务配置方法及装置，业务获取方法、装置及***
WO2017076055A1 (zh) 车联网业务数据包传输方法及装置
CN110235514A (zh) 支持本地化无线通信业务的基站和通信设备
CN106341813B (zh) 一种信息发送接收方法及装置
US20230354110A1 (en) Method and device for switching a serving cell and method and device supporting on-demand system information message
WO2017166900A1 (zh) 多媒体广播多播业务的接收方法及终端、基站、存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17746787

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17746787

Country of ref document: EP

Kind code of ref document: A1