WO2017133467A1 - Procédé de mise en œuvre de service internet des véhicules et architecture de réseau localisée - Google Patents

Procédé de mise en œuvre de service internet des véhicules et architecture de réseau localisée 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
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/071647
Other languages
English (en)
Chinese (zh)
Inventor
吴蕴璐
陈琳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2017133467A1 publication Critical patent/WO2017133467A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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

L'invention concerne un procédé de mise en œuvre d'un service Internet des véhicules et une architecture de réseau localisée, faisant appel à la distinction de zones de diffusion pour un message V2X : si le message V2X est diffusé dans une cellule sous une station de base adjacente régie par un MBMS local, l'établissement d'une porteuse de MBMS vers la station de base adjacente est déclenché ; et lorsque la porteuse de MBMS pour les zones de diffusion V2X est établie, un chemin de données côté utilisateur de liaison descendante diffusé par la cellule sous la station de base adjacente et régie par le MBMS local pour le message V2X est comme suit : un serveur V2X local -> une première entité -> la station de base adjacente. Des modes de réalisation de la présente invention satisfont à une exigence de latence d'un service Internet des véhicules, notamment un service V2V/V2I/V2P.
PCT/CN2017/071647 2016-02-04 2017-01-19 Procédé de mise en œuvre de service internet des véhicules et architecture de réseau localisée Ceased WO2017133467A1 (fr)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=59499405

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/071647 Ceased WO2017133467A1 (fr) 2016-02-04 2017-01-19 Procédé de mise en œuvre de service internet des véhicules et architecture de réseau localisée

Country Status (2)

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

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 (fr) * 2019-01-11 2022-08-10 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de planification et de priorité pour transmission de données

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112087722B (zh) * 2017-10-24 2022-03-29 华为技术有限公司 一种通信系统、通信方法及其装置
CN109842854B (zh) * 2017-11-29 2021-01-05 华为技术有限公司 一种报文组播、报文广播方法及设备
CN110557831B (zh) * 2018-06-04 2022-11-04 成都鼎桥通信技术有限公司 一种同播sc-ptm系统中控制面信息的传输方法和设备
CN112313922B (zh) 2018-06-26 2022-01-07 华为技术有限公司 用于在5g网络中提供多播/广播服务的实体和方法
CN111278169B (zh) * 2018-12-27 2022-05-17 维沃移动通信有限公司 切换方法、第一终端及第二终端
CN114501341A (zh) 2019-06-17 2022-05-13 华为技术有限公司 通信方法及装置
CN111556539B (zh) * 2020-05-13 2024-05-17 腾讯科技（深圳）有限公司 Ue执行的方法及ue、以及smf实体执行的方法及smf实体
EP4193613A4 (fr) * 2020-08-06 2024-04-17 Lenovo (Beijing) Limited Procédé et appareil pour services de diffusion et de multidiffusion

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 (fr) * 2014-03-19 2015-09-24 Lg Electronics Inc. Procédé et appareil pour configurer un rapport d'état de tampon pour une transmission de sûreté publique ou une transmission relative à un véhicule dans un système de communication sans fil
WO2015147615A1 (fr) * 2014-03-28 2015-10-01 Lg Electronics Inc. Procédé et appareil pour classer par ordre de priorité une transmission de dispositif à dispositif (d2d) et une réception d2d dans un système de communication sans fil
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 (fr) * 2014-03-19 2015-09-24 Lg Electronics Inc. Procédé et appareil pour configurer un rapport d'état de tampon pour une transmission de sûreté publique ou une transmission relative à un véhicule dans un système de communication sans fil
WO2015147615A1 (fr) * 2014-03-28 2015-10-01 Lg Electronics Inc. Procédé et appareil pour classer par ordre de priorité une transmission de dispositif à dispositif (d2d) et une réception d2d dans un système de communication sans fil
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 (fr) * 2019-01-11 2022-08-10 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de planification et de priorité pour transmission de données
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 (fr) Procédé de mise en œuvre de service internet des véhicules et architecture de réseau localisée
US11700552B2 (en) Method and device for switching a serving cell and method and device supporting on-demand system information message
US12477407B2 (en) Method and device for switching a serving cell and method and device supporting on-demand system information message
US9088967B2 (en) Wireless communication system and connection method between user equipment and a mobility management entity
CN107295454B (zh) 资源的配置方法及装置
CN106341848B (zh) 一种切换方法及装置
CN106973356B (zh) 传输v2x消息的方法和装置
CN109565785B (zh) 一种寻呼方法和寻呼设备
CN110035472A (zh) 一种传输方法和网络设备
US10728712B2 (en) Methods and apparatuses for supporting wireless communication of vehicle
JP2019520765A (ja) 無線通信システムにおけるネットワークスライスベースのｎｒのためのセル特定手順を実行する方法及び装置
WO2017133624A1 (fr) Procédé et dispositif pour diffuser un message de communication véhicule-tout (v2x) et procédé pour établir une porteuse mbms
WO2017076037A1 (fr) Procédé et appareil d'envoi de service de réseau de véhicule v2x
CN108632888A (zh) 一种车辆群组的建立、更新方法及其装置
CN107027105A (zh) 车联网通信v2x消息的传输方法、装置及系统
WO2015004142A1 (fr) Procédé pour décider de transférer un équipement utilisateur dans un réseau de communication mobile
WO2016161853A1 (fr) Procédé et système de commutation de noeud relais
KR20180102221A (ko) 무선 통신 시스템에서 v2x 메시지 전송을 위한 자원의 할당을 위한 방법 및 장치
CN104717714A (zh) 路由信息发送、接收的方法、装置及路由信息处理系统
WO2017076056A1 (fr) Procédé et appareil de transfert de service
CN106211188A (zh) 更换中继节点的方法及系统、d2d用户设备及控制节点
CN106341813B (zh) 一种信息发送接收方法及装置
WO2018028458A1 (fr) Procédé et dispositif de configuration de service internet de véhicules, et procédé, dispositif et système d'acquisition de service
WO2017076055A1 (fr) Procédé permettant de transmettre un paquet de données de service de l'internet des véhicules et dispositif correspondant
CN107041016B (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