CN107041016B - Method, equipment and system for forwarding message - Google Patents

Method, equipment and system for forwarding message Download PDF

Info

Publication number
CN107041016B
CN107041016B CN201610080014.8A CN201610080014A CN107041016B CN 107041016 B CN107041016 B CN 107041016B CN 201610080014 A CN201610080014 A CN 201610080014A CN 107041016 B CN107041016 B CN 107041016B
Authority
CN
China
Prior art keywords
enb
message
mbms session
target enb
target
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.)
Active
Application number
CN201610080014.8A
Other languages
Chinese (zh)
Other versions
CN107041016A (en
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
Priority to CN201610080014.8A priority Critical patent/CN107041016B/en
Priority to PCT/CN2017/072700 priority patent/WO2017133629A1/en
Publication of CN107041016A publication Critical patent/CN107041016A/en
Application granted granted Critical
Publication of CN107041016B publication Critical patent/CN107041016B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/40Connection management for selective distribution or broadcast

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The embodiment of the invention discloses a method, equipment and a system for forwarding messages; the method can comprise the following steps: a source evolution type base station eNB establishes a transmission channel with a target eNB according to a preset establishment strategy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel; the source eNB transmits V2X messages or ordinary V2X messages carried in the MBMS session to the target eNB through the transmission channel.

Description

Method, equipment and system for forwarding message
Technical Field
The present invention relates to wireless communication technologies, and in particular, to a method, a device, and a system for forwarding a message.
Background
With the rapid development of social economy, the road traffic safety problem is increasingly prominent. With the development of information communication technology, people can judge the surrounding environment of vehicles through the communication between vehicles and infrastructure, and when the dangerous road condition is detected, timely early warning is provided for drivers to avoid traffic collision, so that the technology is a research hotspot of current domestic and foreign research institutions and enterprises, and is called as internet of vehicles (V2X, Vehicle to X).
V2X provides Vehicle information through sensors, Vehicle terminals, and electronic tags mounted on vehicles, and implements Vehicle-to-Vehicle Communication (V2V), Vehicle-to-human Communication (V2P), Vehicle-to-Network Infrastructure Communication (V2I), Vehicle-to-Network Communication (V2N), and information extraction and sharing on an information Network platform, thereby effectively controlling vehicles and providing comprehensive services.
Currently, the third Generation Partnership Project (3 GPP) is discussing V2X based on Long Term Evolution (LTE) network architecture. And in the present discussion, it is considered that an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) may Broadcast a V2X message downstream to a plurality of User Equipments (UEs) in a local area through a Multimedia Broadcast/Multicast Service (MBMS) technology or a Single-cell-point-to-multiple-point (SC-PTM) technology.
It should be noted that, in the downlink broadcast process of the MBMS, the V2X message cannot be forwarded between adjacent evolved Node bs (enbs).
Disclosure of Invention
In order to solve the technical problem, embodiments of the present invention desirably provide a method, an apparatus, and a system for forwarding a message, which can implement forwarding of a V2X message between adjacent enbs.
The technical scheme of the invention is realized as follows:
in a first aspect, an embodiment of the present invention provides a method for forwarding a message, where the method includes:
a source evolution type base station eNB establishes a transmission channel with a target eNB according to a preset establishment strategy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
and the source eNB transmits the vehicle networking V2X message or the common vehicle networking V2X message carried in the multimedia broadcast/multicast service MBMS session to the target eNB through the transmission channel.
In the foregoing scheme, the establishing, by the source eNB, a transmission channel with the target eNB according to a preset establishment policy specifically includes:
the source eNB receives control plane signaling or user plane data from an upper network element;
when the control plane signaling or the user plane data comprises the cell identification of the target eNB, the source eNB sends a first channel establishing request to the target eNB;
and the source eNB receives a first confirmation establishment channel reply sent by the target eNB.
In the foregoing solution, when the V2X message is a V2X message carried in an MBMS session, the sending, by the source eNB, a first request to establish a channel to the target eNB specifically includes:
the source eNB sends an X2Setup Request message to the target eNB; wherein the X2Setup Request message comprises at least one of the MBMS session identity and the MBMS session performance parameters;
correspondingly, the receiving, by the source eNB, the first acknowledgement setup channel reply sent by the target eNB specifically includes:
the source eNB receives an X2Setup Response message sent by the target eNB after receiving the X2Setup Request message; wherein, the X2Setup Response message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the MBMS session for the target eNB to receive.
In the foregoing solution, when the V2X message is a V2X message carried in an MBMS session, the sending, by the source eNB, a first request to establish a channel to the target eNB specifically includes:
the source eNB sends an eNB Configuration Update message to the target eNB; wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter;
correspondingly, the receiving, by the source eNB, the first acknowledgement setup channel reply sent by the target eNB specifically includes:
the source eNB receives an eNB Configuration Update acknowledgement message sent by the target eNB after the target eNB accepts the eNB Configuration Update message; wherein the eNB Configuration Update acknowledgement message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
In the above scheme, when the V2X message is a general vehicle networking V2X message, the first channel establishment Request includes an X2Setup Request message or an eNB Configuration Update message; wherein, the X2Setup Request message or the eNB Configuration Update message is used for instructing the target eNB to establish a GTP tunnel for forwarding the common vehicle networking V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction;
correspondingly, the first acknowledgement channel establishment reply correspondingly comprises an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of the service type, performance parameter, and GTP tunnel identity.
In the foregoing scheme, the establishing, by the source eNB, a transmission channel with the target eNB according to a preset establishment policy specifically includes:
the source eNB receives a second channel establishment request sent by the target eNB;
the source eNB sends a second acknowledgement setup channel reply to the target eNB.
In the foregoing scheme, the receiving, by the source eNB, the second request for establishing the channel sent by the target eNB specifically includes:
the source eNB receives a Data Fetch Request message sent by the target eNB; the Data Fetch Request message comprises at least one of the MBMS session identifier, a GTP tunnel identifier corresponding to the MBMS session and a User Equipment (UE) identifier corresponding to the MBMS session, wherein the target eNB is used for receiving the MBMS session identifier;
correspondingly, the sending, by the source eNB, a second acknowledgement to establish a channel reply to the target eNB specifically includes:
the source eNB sends a Data Fetch Response message to the target eNB; wherein the Data Fetch Response message includes at least one of the MBMS session identity and the MBMS session performance parameter.
In a second aspect, an embodiment of the present invention provides a method for forwarding a message, where the method includes:
according to a preset establishing strategy, a transmission channel is established between a target evolution type base station eNB and a source eNB; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
and the target eNB receives the vehicle networking V2X message or the common vehicle networking V2X message carried in the multimedia broadcast/multicast service MBMS session transmitted by the source eNB through the transmission channel.
In the foregoing scheme, according to a preset establishment policy, establishing a transmission channel between the target eNB and the source eNB specifically includes:
the target eNB receives a first channel establishment request sent by the source eNB;
the target eNB sends a first acknowledgement setup channel reply to the source eNB.
In the foregoing solution, when the V2X message is a V2X message carried in an MBMS session, the receiving, by the target eNB, a first request to establish a channel sent by the source eNB specifically includes:
the target eNB receives an X2Setup Request message sent by the source eNB; wherein the X2Setup Request message comprises at least one of the MBMS session identity and the MBMS session performance parameters;
correspondingly, the sending, by the target eNB, a first acknowledgement setup channel reply to the source eNB specifically includes:
after receiving the X2Setup Request message, the target eNB sends an X2Setup Response message to the source eNB; wherein, the X2Setup Response message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the MBMS session for the target eNB to receive.
In the foregoing solution, when the V2X message is a V2X message carried in an MBMS session, the receiving, by the target eNB, a first request to establish a channel sent by the source eNB specifically includes:
the target eNB receives an eNB Configuration Update message sent by the source eNB; wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter;
correspondingly, the sending, by the target eNB, a first acknowledgement setup channel reply to the source eNB specifically includes: after receiving the eNB Configuration Update message, the target eNB sends an eNB Configuration Update Acknowledgemessage to the source eNB; wherein the eNB Configuration Update acknowledgement message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
In the above scheme, when the V2X message is a general vehicle networking V2X message, the first channel establishment Request includes an X2Setup Request message or an eNB Configuration Update message; wherein, the X2Setup Request message or the eNB Configuration Update message is used for instructing the target eNB to establish a GTP tunnel for forwarding the common vehicle networking V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction;
correspondingly, the first acknowledgement channel establishment reply correspondingly comprises an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of the service type, performance parameter, and GTP tunnel identity.
In the foregoing scheme, according to a preset establishment policy, establishing a transmission channel between the target eNB and the source eNB specifically includes:
the target eNB sends a second channel establishment request to the source eNB;
the target eNB receives a second acknowledgement setup channel reply sent by the source eNB.
In the foregoing scheme, the sending, by the target eNB, the second request for establishing the channel to the source eNB specifically includes:
the target eNB sends a Data Fetch Request message to the source eNB; the Data Fetch Request message comprises the MBMS session identifier, a GTP tunnel identifier corresponding to the MBMS session and a User Equipment (UE) identifier corresponding to the MBMS session, wherein the target eNB is used for receiving the GTP tunnel identifier corresponding to the MBMS session;
correspondingly, the receiving, by the target eNB, the second acknowledgement setup channel reply sent by the source eNB specifically includes:
the target eNB receives a Data Fetch Response message sent by the source eNB; wherein the Data Fetch Response message includes at least one of the MBMS session identity and the MBMS session performance parameter.
In a third aspect, an embodiment of the present invention provides a source eNB, where the source eNB includes: the device comprises a first establishing module and a transmission module; wherein the content of the first and second substances,
the first establishing module is used for establishing a transmission channel with the target eNB according to a preset establishing strategy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
the transmission module is configured to transmit a vehicle networking V2X message or a general vehicle networking V2X message carried in a multimedia broadcast/multicast service MBMS session to the target eNB through the transmission channel.
In the foregoing scheme, the first establishing module specifically includes: a first receiving unit, a first transmitting unit and a second receiving unit; wherein the content of the first and second substances,
the first receiving unit is configured to receive a control plane signaling or user plane data from an upper network element;
the first sending unit is configured to send a first request for establishing a channel to the target eNB when the control plane signaling or the user plane data includes the cell identifier of the target eNB;
the second receiving unit is configured to receive a first acknowledgement setup channel reply sent by the target eNB.
In the foregoing solution, when the V2X message is a V2X message carried in an MBMS session, the first sending unit is specifically configured to: sending an X2Setup Request message to the target eNB;
wherein the X2Setup Request message comprises at least one of the MBMS session identity and the MBMS session performance parameters;
correspondingly, the second receiving unit is specifically configured to:
receiving an X2Setup Response message sent by the target eNB after receiving the X2Setup Request message; wherein, the X2Setup Response message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the MBMS session for the target eNB to receive.
In the foregoing solution, when the V2X message is a V2X message carried in an MBMS session, the first sending unit is specifically configured to: sending an eNB Configuration Update message to the target eNB;
wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter;
correspondingly, the second receiving unit is specifically configured to:
receiving an eNB Configuration Update Acknowledgemessage sent by the target eNB after accepting the eNB Configuration Update message; wherein the eNB Configuration Update acknowledgement message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
In the above scheme, when the V2X message is a general vehicle networking V2X message, the first channel establishment Request includes an X2Setup Request message or an eNB Configuration Update message; wherein, the X2Setup Request message or the eNB Configuration Update message is used for instructing the target eNB to establish a GTP tunnel for forwarding the common vehicle networking V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction;
correspondingly, the first acknowledgement channel establishment reply correspondingly comprises an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of the service type, performance parameter, and GTP tunnel identity.
In the foregoing scheme, the first establishing module specifically includes: a third receiving unit and a second transmitting unit; wherein the content of the first and second substances,
the third receiving unit is configured to receive a second request for establishing a channel sent by the target eNB;
the second sending unit is configured to send a second acknowledgement channel setup reply to the target eNB.
In the foregoing scheme, the third receiving unit is specifically configured to receive a Data Fetch Request message sent by the target eNB; the Data Fetch Request message comprises the MBMS session identifier, a GTP tunnel identifier corresponding to the MBMS session and a User Equipment (UE) identifier corresponding to the MBMS session, wherein the target eNB is used for receiving the GTP tunnel identifier corresponding to the MBMS session;
correspondingly, the second sending unit is specifically configured to send a Data Fetch Response message to the target eNB; wherein the Data Fetch Response message includes at least one of the MBMS session identity and the MBMS session performance parameter.
In a fourth aspect, an embodiment of the present invention provides a target eNB, where the target eNB includes: the second establishing module and the receiving module; wherein the content of the first and second substances,
the second establishing module is used for establishing a transmission channel with the source eNB according to a preset establishing strategy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
the receiving module is configured to receive, through the transmission channel, a vehicle networking V2X message or a general vehicle networking V2X message carried in a multimedia broadcast/multicast service MBMS session transmitted by the source eNB.
In the foregoing solution, the second establishing module includes: a fourth receiving unit and a third transmitting unit; wherein the content of the first and second substances,
the fourth receiving unit is configured to receive a first request for establishing a channel sent by the source eNB;
the third sending unit is configured to send a first acknowledgement channel setup reply to the source eNB.
In the foregoing solution, when the V2X message is a V2X message carried in an MBMS session, the fourth receiving unit is specifically configured to: receiving an X2Setup Request message sent by the source eNB; wherein the X2Setup Request message comprises at least one of the MBMS session identity and the MBMS session performance parameters;
correspondingly, the third sending unit is specifically configured to send an X2Setup Response message to the source eNB; wherein, the X2Setup Response message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the MBMS session for the target eNB to receive.
In the foregoing solution, when the V2X message is a V2X message carried in an MBMS session, the fourth receiving unit is specifically configured to: receiving an eNB Configuration Update message sent by the source eNB; wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter;
correspondingly, the third sending unit is specifically configured to send an eNB Configuration Update acknowledgement message to the source eNB; wherein the eNB Configuration Update acknowledgement message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
In the above scheme, when the V2X message is a general vehicle networking V2X message, the first channel establishment Request includes an X2Setup Request message or an eNB Configuration Update message; wherein, the X2Setup Request message or the eNB Configuration Update message is used for instructing the target eNB to establish a GTP tunnel for forwarding the common vehicle networking V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction;
correspondingly, the first acknowledgement channel establishment reply correspondingly comprises an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of the service type, performance parameter, and GTP tunnel identity.
In the foregoing scheme, the second establishing module specifically includes: a fourth transmitting unit and a fifth receiving unit; wherein the content of the first and second substances,
the fourth sending unit is configured to send a second request for establishing a channel to the source eNB;
the fifth receiving unit is configured to receive a second acknowledgement channel setup reply sent by the source eNB.
In the foregoing scheme, the fourth sending unit is specifically configured to send a Data Fetch Request message to the source eNB; the Data Fetch Request message comprises the MBMS session identifier, a GTP tunnel identifier corresponding to the MBMS session and a User Equipment (UE) identifier corresponding to the MBMS session, wherein the target eNB is used for receiving the GTP tunnel identifier corresponding to the MBMS session;
correspondingly, the fifth receiving unit is specifically configured to receive a Data Fetch Response message sent by the source eNB; wherein the Data Fetch Response message includes at least one of the MBMS session identity and the MBMS session performance parameter.
In a fifth aspect, an embodiment of the present invention provides a system for forwarding a message, where the system includes: a source eNB and a target eNB; wherein the content of the first and second substances,
the source eNB is used for establishing a transmission channel with the target eNB according to a preset establishment strategy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
and transmitting the vehicle networking V2X message or the common vehicle networking V2X message carried in the multimedia broadcast/multicast service MBMS session to the target eNB through the transmission channel;
the target eNB is used for establishing a transmission channel with the source eNB according to a preset establishment strategy;
and receiving the V2X message or the common Internet of vehicles V2X message carried in the MBMS session transmitted by the source eNB through the transmission channel.
The embodiment of the invention provides a method, equipment and a system for forwarding a message. Forwarding of V2X messages is achieved between neighboring enbs by establishing a transport channel, such as a GTP tunnel, between the source eNB and the target eNB, and the source eNB transporting the MBMS session carrying the V2X messages to the target eNB through the transport tunnel.
Drawings
Fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a method for forwarding a message according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a method for establishing a transmission channel according to an embodiment of the present invention;
fig. 4 is a schematic flow chart of another method for establishing a transmission channel according to an embodiment of the present invention;
fig. 5 is a schematic flowchart of a specific implementation manner provided in an embodiment of the present invention;
fig. 6 is a schematic flow chart of another specific implementation manner provided in the embodiment of the present invention;
fig. 7 is a schematic flowchart of another specific implementation manner provided by the embodiment of the present invention;
FIG. 8 is a schematic flow chart of a complete solution provided by an embodiment of the present invention;
fig. 9 is a schematic flowchart of a method for forwarding a message applied to a source eNB side according to an embodiment of the present invention;
fig. 10 is a flowchart illustrating a method for forwarding a message applied to a target eNB according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of a source eNB according to an embodiment of the present invention;
fig. 12 is a schematic structural diagram of another source eNB according to an embodiment of the present invention;
fig. 13 is a schematic structural diagram of another source eNB according to an embodiment of the present invention;
fig. 14 is a schematic structural diagram of a target eNB according to an embodiment of the present invention;
fig. 15 is a schematic structural diagram of another target eNB according to an embodiment of the present invention;
fig. 16 is a schematic structural diagram of another target eNB according to an embodiment of the present invention;
fig. 17 is a schematic structural diagram of a message forwarding system according to an embodiment of the present invention.
Detailed Description
The technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.
Referring to the schematic diagram of the network architecture used in the embodiment of the present invention shown in fig. 1, the local E-TRAN server (local V2X E-UTRAN server), the local MBMS broadcast multicast service center (local MBMS BM-SC) and the MBMS gateway (MBMS GW) are all built in or coupled to the eNB. As shown in FIG. 1, the embodiment of the present invention is described by taking the example that local V2X E-UTRAN server, local MBMS BM-SC and MBMS GW are all built in eNB. Other Network element devices, such as a Mobility Management Entity (MME), a Packet Data Network GateWay (P-GW), a Serving GateWay (S-GW), a Multi-cell/Multicast Coordination Entity (MCE), etc., are common Network element devices for implementing MBMS in an LTE architecture, and their functions and connection interfaces are not described herein again. Based on the network architecture shown in fig. 1, application scenarios in which V2X messages are forwarded between enbs over an X2 interface may illustratively include, but are not limited to, the following three scenarios:
scene one: the V2X message is sent through MBMS bearer, and its diffusion area includes neighboring base stations, so eNB1 needs to forward the data to eNB2 through X2 port;
scene two: the V2X message is delivered by the eNB1 through an MBMS bearer, when a certain UE under the eNB1 is switched to the eNB2, the eNB2 requests the eNB1 to send data delivered by the MBMS bearer after the UE is switched to the eNB2 through the X2 interface, and then the eNB2 delivers the data to the UE through a unicast. At this time, eNB1 also needs to forward data to eNB2 through X2 port;
scene three: when the V2X message arrives at the eNB in a manner other than MBMS bearer, if the eNB1 decides to forward the V2X message based on some information, such as the geographical location or target area in the message. Such a V2X message is defined as a normal V2X message in the present invention. The means other than MBMS bearer may include, but is not limited to, from the UE.
It should be noted that the application scenarios related to the embodiments of the present invention are only used for illustrating the technical solutions. Those skilled in the art can understand that, besides the three scenarios, other scenarios that require forwarding the V2X message between enbs are all applicable to the technical solution of the embodiment of the present invention, and are not described herein again.
In fig. 1, V2X messages need to be forwarded by eNB1 to eNB2 over the X2 interface; thus, eNB1 may be referred to as a source eNB and eNB2 may be referred to as a target eNB. Embodiments of the present invention are presented based on the network architecture shown in fig. 1.
Example one
Referring to fig. 2, it illustrates a method for forwarding a message according to an embodiment of the present invention, where the method may include:
s210: the source eNB establishes a transmission channel with the target eNB according to a preset establishment strategy;
s220: the source eNB transmits the V2X message or the general V2X message carried in the MBMS session to the target eNB through a transmission channel.
It should be noted that the transmission tunnel mentioned in this embodiment may include a general packet radio service Tunneling Protocol (GTP) tunnel, and the source eNB may transmit the V2X message or the normal V2X message carried in the MBMS session to the target eNB through the GTP tunnel.
It is understood that step S210 may include at least two of the following cases:
in the first case, a source eNB actively sends a request to a target eNB to establish a transmission channel;
in case two, the source eNB passively receives the request sent by the target eNB to establish the transport tunnel.
For example, for the case one, after the source eNB receives the control plane signaling or the user plane data through the upper network element, it may determine whether to establish a transmission channel with the target eNB according to the received control plane signaling or the received user plane data. Taking the network architecture shown in fig. 1 as an example, if the eNB1 receives a cell list indicated by a request for establishing an MBMS session sent by an upper layer network element, where the cell list includes a cell ID of the eNB 2; or if the header of the user plane data received by the eNB1 includes the cell ID of the eNB2, the eNB1 needs to establish a GTP tunnel for transmitting the MBMS session with the eNB 2. Thus, referring to fig. 3, for step S210: the method for establishing the transmission channel with the target eNB by the source eNB according to the preset establishment policy may specifically include:
s310: the source eNB receives control plane signaling or user plane data from an upper network element;
s320: when control plane signaling or user plane data comprises a cell identifier of a target eNB, a source eNB sends a first channel establishment request to the target eNB;
s330: the target eNB sends a first acknowledgement setup channel reply to the source eNB.
For example, for the case two, after the source eNB receives the channel establishment request sent by the target eNB, the source eNB may establish a transmission channel with the target eNB according to the request. Taking the network architecture shown in fig. 1 as an example, after the UE1 is handed over from eNB1 to eNB2, the UE1 has a continuity requirement for the V2X message of the MBMS bearer, and therefore, the UE1 may initiate a request to eNB2 for not receiving a full V2X message on eNB1 through the MBMS bearer before desiring to obtain the handover. At this point, the eNB2 may ask the eNB1 to forward a V2X message on the MBMS bearer that the UE1 has not yet received in its entirety. Thus, referring to fig. 4, for step S210: the method for establishing the transmission channel with the target eNB by the source eNB according to the preset establishment policy may specifically include:
s410: the target eNB sends a second channel establishment request to the source eNB;
s420: the source eNB sends a second acknowledgement setup channel reply to the target eNB.
Through the technical scheme, the source eNB can establish a transmission channel such as a GTP tunnel with the target eNB, and the source eNB can transmit the MBMS session carrying the V2X message to the target eNB through the transmission channel, so that the forwarding of the V2X message is realized between adjacent eNBs.
Further, the embodiment of the present invention further provides specific implementation manners for the two cases.
For situation one
The first channel establishment Request in step S320 may be an X2Setup Request message or an eNB Configuration Update message in a specific implementation process; correspondingly, the first acknowledgement channel Setup reply corresponds to an X2Setup Response message or an eNB Configuration Update acknowledgement message in the specific implementation process. For the specific implementation of the two pairs of the first establishment channel request and the first confirmation establishment channel reply, for the step S320 and the step S330 in fig. 3 corresponding to the case one, the embodiment of the present invention also provides two specific implementation manners correspondingly.
Referring to fig. 5, when the V2X message is a V2X message carried in an MBMS session, a first specific implementation may include:
S320A: the source eNB sends an X2Setup Request message to the target eNB;
wherein, the X2Setup Request message comprises at least one item of MBMS conversation identification and MBMS conversation performance parameter; specifically, when the source eNB and the target eNB satisfy the first condition, the X2Setup Request message includes: an MBMS session identifier; when the source eNB and the target eNB satisfy the second condition, the X2Setup Request message includes: MBMS session identity and MBMS session performance parameters;
S330A: after receiving the X2Setup Request message, the target eNB sends an X2Setup Response message to the source eNB;
the X2Setup Response message includes an MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
It should be noted that, in the embodiment of the present invention, the MBMS session identifier may specifically be a Temporary Mobile Group Identifier (TMGI) or a session identifier (session ID); the GTP tunnel identifier corresponding to the source eNB for transmitting the MBMS session may specifically be a GTP tunnel endpoint corresponding to the source eNB for transmitting the MBMS session; the MBMS session performance parameter may be Quality of Service (QoS) configuration information of the MBMS session.
As to the aforementioned first condition and second condition, it should be further noted that, if joint configuration is used when the source eNB and the target eNB perform MBMS configuration, for example, the source eNB and the target eNB coordinate through Operation and Maintenance Administration (OAM), that is, the source eNB and the target eNB know QoS configuration information of an MBMS session corresponding to a TMGI or a session ID of each other, when the source eNB and the target eNB establish a GTP tunnel for the MBMS session, the first Data Fetch Request message may only carry the TMGI or the session ID;
if the source eNB and the target eNB use independent configuration when performing MBMS configuration, for example, the two enbs are connected to different MBMS control nodes respectively and there is no coordination between the MBMS control nodes, that is, the source eNB and the target eNB do not know the QoS configuration information of the MBMS session corresponding to the TMGI or the session ID of the other eNB, when the source eNB and the target eNB establish a GTP tunnel for the MBMS session, the first Data Fetch Request message needs to carry the QoS configuration information of the MBMS session.
Furthermore, if the target eNB does not accept the X2Setup Request message, i.e., the target eNB2 rejects the source eNB-initiated X2Setup Request, the target eNB may send an X2Setup Failure message to the source eNB.
Referring to fig. 6, when the V2X message is a V2X message carried in an MBMS session, a second specific implementation may include:
S320B: a source eNB sends an eNB Configuration Update message to a target eNB;
wherein the eNB Configuration Update message includes at least one of the MBMS session identity and the MBMS session performance parameter; specifically, when the source eNB and the target eNB satisfy the first condition, the eNB Configuration Update message includes: an MBMS session identifier; when the source eNB and the target eNB satisfy the second condition, the eNB Configuration Update message includes: MBMS session identity and MBMS session performance parameters;
S330B: after receiving the eNB Configuration Update message, the target eNB sends an eNB Configuration Update acknowledgement message to the source eNB;
the eNB Configuration Update acknowledgement message includes an MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
It can be understood that, in the process of this specific implementation manner, the specific contents of the MBMS session identifier, the MBMS session performance parameter, the GTP tunnel identifier, and the first condition and the second condition are the same as those in the first specific implementation manner, and are not described herein again.
In addition, if the target eNB does not accept the eNB Configuration Update message, i.e. the target eNB2 rejects the eNB Configuration Update initiated by the source eNB, the target eNB may send an eNB Configuration Update Failure message to the source eNB.
It should be additionally noted that, when the V2X message is an ordinary V2X message, as to step S320 and step S330 in fig. 3, the implementation may still be implemented in the specific implementation manners of fig. 5 and fig. 6, but at this time, the first Request for establishing a channel includes an X2Setup Request message or an eNB Configuration Update message; wherein, the X2Setup Request message or the eNB Configuration Update message is used for indicating the target eNB to establish a GTP tunnel for forwarding the common V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction;
correspondingly, the first acknowledgement channel establishment reply correspondingly comprises an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of a service type, a performance parameter, and a GTP tunnel identity.
It is understood that when the V2X message is a normal V2X message, the traffic type may be a V2X message or subdivided into V2X messages of different priorities; the performance parameter may be a delay requirement of the message, etc.; the GTP Tunnel identity may be a GTP Tunnel Endpoint.
For case two
For step S410 and step S420 in fig. 4 corresponding to the case two, as shown in fig. 7, a specific implementation manner provided by the embodiment of the present invention may include:
S410A: the target eNB sends a Data Fetch Request message to the source eNB;
the Data Fetch Request message comprises an MBMS conversation identifier, a GTP tunnel identifier corresponding to the MBMS conversation and a User Equipment (UE) identifier corresponding to the MBMS conversation, wherein the target eNB is used for receiving the GTP tunnel identifier corresponding to the MBMS conversation;
S420A: the source eNB sends a Data Fetch Response message to the target eNB;
the Data Fetch Response message comprises the MBMS session identification and at least one item of the MBMS session performance parameters; specifically, when the source eNB and the target eNB satisfy the first condition, the Data Fetch Response message includes: an MBMS session identifier; when the source eNB and the target eNB meet the second condition, the Data Fetch Response message comprises: MBMS session identity and MBMS session performance parameters.
It can be understood that, in the process of this specific implementation manner, the specific contents of the MBMS session identifier, the MBMS session performance parameter, the GTP tunnel identifier, and the first condition and the second condition are the same as the specific implementation manner one in case one, and are not described herein again. In case two, however, the target eNB sending the second setup channel request to the source eNB is due to the handover eNB of the UE, resulting in the UE needing to initiate a request to eNB2 that the full V2X message has not been received over the MBMS bearer on eNB1 before the handover can be obtained. Therefore, the Data Fetch Request message further needs to include a UE identity corresponding to the MBMS session, and specifically, the UE identity may include: the UE may be identified in the target eNB2 by a Cell Radio Network Temporary Identifier (C-RTNI) or short MAC-I.
In addition, if the source eNB does not accept the first Data Fetch Request message, i.e. the source eNB refuses to establish the GTP tunnel with the target eNB, the source eNB may send a Data Fetch Request message to the target eNB to refuse the first Data Fetch Request message sent by the target eNB. Wherein, the Cause value in the Data Fetch Reject message may include, but is not limited to, no Data buffered.
Since the UE handover results in the target eNB sending the second request for establishing the channel to the source eNB, referring to fig. 8, on the basis of the scheme shown in fig. 7, a complete scheme of the specific implementation may include:
s401: the UE moves to the edge of a cell of a source eNB and triggers Measurement Report;
s402: a source eNB sends a handover HO request message to a target eNB;
s403: the target eNB returns a switching HO request ACK message to the source eNB;
s404: the source eNB sends the switching information returned by the target eNB to the UE through an RRC connection configuration message;
s405: after accessing a target eNB, the UE sends an MBMS Service Continuity Request message to the target eNB;
wherein, the MBMS Service Continuity Request message at least comprises TMGI or session ID of MBMS session;
S410A: the target eNB sends a Data Fetch Request message to the source eNB;
the Data Fetch Request message at least comprises TMGI or session ID information of the MBMS session and GTP tunnel endpoint and UE ID of the target eNB;
S420A: the source eNB sends a Data Fetch Response message to the target eNB;
wherein, the Data Fetch Response message carries the TMGI or session ID of the MBMS session; or additionally carries QoS configuration information of the MBMS session.
S430: the source eNB forwards the V2X message sent by the MBMS session after the UE handover to the target eNB through the established GTP tunnel.
The embodiment provides a message forwarding method, a source eNB can establish a transmission channel such as a GTP tunnel with a target eNB, and the source eNB can transmit an MBMS session carrying a V2X message to the target eNB through the transmission channel, so that forwarding of the V2X message is realized between adjacent eNBs.
Example two
Based on the same technical concept of the foregoing embodiment, referring to fig. 9, it shows a method for message forwarding applied to a source eNB side according to an embodiment of the present invention, where the method may include:
s901: the source eNB establishes a transmission channel with the target eNB according to a preset establishment strategy;
wherein the transmission tunnel comprises a GTP tunnel;
s902: the source eNB transmits the V2X message or the general V2X message carried in the MBMS session to the target eNB through a transmission channel.
Exemplarily, the establishing, by the source eNB, a transmission channel with the target eNB according to a preset establishment policy specifically includes:
the source eNB receives control plane signaling or user plane data from an upper network element;
when the control plane signaling or the user plane data comprises the cell identification of the target eNB, the source eNB sends a first channel establishing request to the target eNB;
and the source eNB receives the first confirmation establishment channel reply sent by the target eNB.
In a specific implementation manner, when the V2X message is a V2X message carried in an MBMS session, the sending, by the source eNB, the first request to establish a channel to the target eNB includes: the source eNB sends an X2Setup Request message to the target eNB;
wherein the X2Setup Request message comprises at least one of the MBMS session identity and the MBMS session performance parameters; specifically, when the source eNB and the target eNB satisfy the first condition, the X2Setup Request message includes: an MBMS session identifier; when the source eNB and the target eNB satisfy the second condition, the X2Setup Request message includes: MBMS session identity and MBMS session performance parameters;
correspondingly, the receiving, by the source eNB, the first acknowledgement setup channel reply sent by the target eNB specifically includes:
the source eNB receives an X2Setup Response message sent by the target eNB after receiving the X2Setup Request message; the X2Setup Response message includes an MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
In another specific implementation, the sending, by the source eNB, the first request to establish the channel to the target eNB specifically includes: a source eNB sends an eNB Configuration Update message to a target eNB;
wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter; specifically, when the source eNB and the target eNB satisfy the first condition, the eNB Configuration Update message includes: an MBMS session identifier; when the source eNB and the target eNB satisfy the second condition, the eNB Configuration Update message includes: MBMS session identity and MBMS session performance parameters;
correspondingly, the receiving, by the source eNB, the first acknowledgement setup channel reply sent by the target eNB specifically includes:
the source eNB receives an eNB Configuration Update acknowledgement message sent by the target eNB after receiving the eNB Configuration Update message; the eNB Configuration Update acknowledgement message includes an MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
Exemplarily, the establishing, by the source eNB, a transmission channel with the target eNB according to a preset establishment policy specifically includes:
the source eNB receives a second channel establishment request sent by the target eNB;
and the source eNB sending a second acknowledgement setup channel reply to the target eNB.
In a specific implementation manner, the receiving, by the source eNB, the second request for establishing the channel sent by the target eNB specifically includes: a source eNB receives a Data Fetch Request message sent by a target eNB;
the Data Fetch Request message comprises an MBMS conversation identifier, a GTP tunnel identifier corresponding to the MBMS conversation and a User Equipment (UE) identifier corresponding to the MBMS conversation, wherein the target eNB is used for receiving the GTP tunnel identifier corresponding to the MBMS conversation;
correspondingly, the sending, by the source eNB, the second acknowledgement channel setup reply to the target eNB specifically includes:
the source eNB sends a Data Fetch Response message to the target eNB; wherein the Data Fetch Response message comprises at least one of the MBMS session identity and the MBMS session performance parameter; specifically, when the source eNB and the target eNB satisfy the first condition, the Data Fetch Response message includes: an MBMS session identifier; when the source eNB and the target eNB meet the second condition, the Data Fetch Response message comprises: MBMS session identity and MBMS session performance parameters.
The embodiment provides a method applied to message forwarding on the source eNB side, wherein the source eNB can establish a transmission channel such as a GTP tunnel with a target eNB, and the source eNB can transmit an MBMS session carrying a V2X message to the target eNB through the transmission channel, so that the forwarding of the V2X message is realized between adjacent eNBs.
EXAMPLE III
Based on the same technical concept of the foregoing embodiment, referring to fig. 10, it shows a method for message forwarding applied to a target eNB side according to an embodiment of the present invention, where the method may include:
s1001: according to a preset establishing strategy, a target eNB and a source eNB establish a transmission channel;
wherein the transmission tunnel comprises a GTP tunnel;
s1002: the target eNB receives the car networking V2X message or the general V2X message carried in the MBMS session transmitted by the source eNB through the transmission channel.
Illustratively, according to a preset establishment policy, the establishing, by the target eNB, a transmission channel with the source eNB specifically includes:
a target eNB receives a first channel establishment request sent by a source eNB;
and the target eNB sends a first confirmation establishment channel reply to the source eNB.
In a specific implementation manner, the receiving, by the target eNB, the first request to establish the channel sent by the source eNB specifically includes: the target eNB receives an X2Setup Request message sent by the source eNB;
wherein the X2Setup Request message comprises at least one of the MBMS session identity and the MBMS session performance parameters; specifically, when the source eNB and the target eNB satisfy the first condition, the X2Setup Request message includes: an MBMS session identifier; when the source eNB and the target eNB satisfy the second condition, the X2Setup Request message includes: MBMS session identity and MBMS session performance parameters;
correspondingly, the target eNB sending a first acknowledgement channel setup reply to the source eNB specifically includes:
after receiving the X2Setup Request message, the target eNB sends an X2Setup Response message to the source eNB; the X2Setup Response message includes an MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
In another specific implementation manner, the receiving, by the target eNB, the first request to establish the channel sent by the source eNB specifically includes: the target eNB receives an eNB Configuration Update message sent by the source eNB;
wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter; specifically, when the source eNB and the target eNB satisfy the first condition, the eNB Configuration Update message includes: an MBMS session identifier; when the source eNB and the target eNB satisfy the second condition, the eNB Configuration Update message includes: MBMS session identity and MBMS session performance parameters;
correspondingly, the target eNB sending a first acknowledgement channel setup reply to the source eNB specifically includes:
after receiving the eNB Configuration Update message, the target eNB sends an eNB Configuration Update acknowledgement message to the source eNB; the eNB Configuration Update acknowledgement message includes an MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
It should be additionally noted that, when the V2X message is a normal V2X message, the first tunnel establishment Request includes an X2Setup Request message or an eNB Configuration Update message; wherein, the X2Setup Request message or the eNB Configuration Update message is used for indicating the target eNB to establish a GTP tunnel for forwarding the common V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction;
correspondingly, the first acknowledgement channel establishment reply correspondingly comprises an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of the service type, performance parameter, and GTP tunnel identity.
Illustratively, according to a preset establishment policy, the establishing, by the target eNB, a transmission channel with the source eNB specifically includes:
the target eNB sends a second channel establishment request to the source eNB;
and the target eNB receiving a second acknowledgement setup channel reply sent by the source eNB.
In a specific implementation manner, the sending, by the target eNB, the second request for establishing the channel to the source eNB specifically includes: the target eNB sends a Data Fetch Request message to the source eNB;
the Data Fetch Request message comprises an MBMS conversation identifier, a GTP tunnel identifier corresponding to the MBMS conversation and a User Equipment (UE) identifier corresponding to the MBMS conversation, wherein the target eNB is used for receiving the GTP tunnel identifier corresponding to the MBMS conversation;
correspondingly, the receiving, by the target eNB, the second acknowledgement setup channel reply sent by the source eNB specifically includes:
the target eNB receives a Data Fetch Response message sent by the source eNB; wherein the Data Fetch Response message comprises at least one of the MBMS session identity and the MBMS session performance parameter; specifically, when the source eNB and the target eNB satisfy the first condition, the Data Fetch Response message includes: an MBMS session identifier; when the source eNB and the target eNB meet the second condition, the Data Fetch Response message comprises: MBMS session identity and MBMS session performance parameters.
Example four
Based on the same technical concept of the foregoing embodiments, referring to fig. 11, a source eNB110 provided in an embodiment of the present invention is shown, where the source eNB110 may include: a first setup module 1101 and a transmission module 1102; wherein the content of the first and second substances,
the first establishing module 1101 is configured to establish a transmission channel with a target eNB according to a preset establishing policy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
the transmission module 1102 is configured to transmit the V2X message or the normal V2X message carried in the MBMS session to the target eNB through the transmission channel.
Exemplarily, referring to fig. 12, the first establishing module 1101 specifically includes: a first receiving unit 11011, a first transmitting unit 11012, and a second receiving unit 11013; wherein the content of the first and second substances,
the first receiving unit 11011 is configured to receive control plane signaling or user plane data from an upper network element;
the first sending unit 11012 is configured to send a first channel setup request to the target eNB when the control plane signaling or the user plane data includes the cell identifier of the target eNB;
the second receiving unit 11013 is configured to receive a first acknowledgement setup channel reply sent by the target eNB.
When the V2X message is a V2X message carried in an MBMS session, in a specific implementation manner, the first sending unit 11012 is specifically configured to: sending an X2Setup Request message to the target eNB;
wherein the X2Setup Request message comprises at least one of the MBMS session identity and the MBMS session performance parameters; specifically, when the source eNB and the target eNB satisfy a first condition, the X2Setup Request message includes: the MBMS conversation mark; when the source eNB and the target eNB satisfy a second condition, the X2Setup Request message includes: the MBMS session identity and the MBMS session performance parameter;
accordingly, the second receiving unit 11013 is specifically configured to:
receiving an X2Setup Response message sent by the target eNB after receiving the X2Setup Request message; wherein, the X2Setup Response message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the MBMS session for the target eNB to receive.
When the V2X message is a V2X message carried in an MBMS session, in another specific implementation manner, the first sending unit 11012 is specifically configured to: sending an eNB Configuration Update message to the target eNB;
wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter; specifically, when the source eNB and the target eNB satisfy a first condition, the eNB Configuration Update message includes: the MBMS conversation mark; when the source eNB and the target eNB satisfy a second condition, the eNB Configuration Update message includes: the MBMS session identity and the MBMS session performance parameter;
accordingly, the second receiving unit 11013 is specifically configured to:
receiving an eNB Configuration Update Acknowledgemessage sent by the target eNB after accepting the eNB Configuration Update message; wherein the eNB Configuration Update acknowledgement message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
It should be additionally noted that, when the V2X message is a normal V2X message, the first tunnel establishment Request includes an X2Setup Request message or an eNB Configuration Update message; wherein, the X2Setup Request message or the eNB Configuration Update message is used for indicating the target eNB to establish a GTP tunnel for forwarding the common V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction;
correspondingly, the first acknowledgement channel establishment reply correspondingly comprises an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of the service type, performance parameter, and GTP tunnel identity.
Exemplarily, referring to fig. 13, the first establishing module 1101 specifically includes: third receiving unit 11014 and second transmitting unit 11015; wherein the content of the first and second substances,
the third receiving unit 11014 is configured to receive a second request for establishing a channel sent by the target eNB;
the second sending unit 11015 is configured to send a second acknowledgement setup channel reply to the target eNB.
In a specific implementation manner, the third receiving unit 11014 is specifically configured to receive a Data Fetch Request message sent by the target eNB; the Data Fetch Request message comprises the MBMS session identifier, a GTP tunnel identifier corresponding to the MBMS session and a User Equipment (UE) identifier corresponding to the MBMS session, wherein the target eNB is used for receiving the GTP tunnel identifier corresponding to the MBMS session;
correspondingly, the second sending unit 11015 is specifically configured to send a Data Fetch Response message to the target eNB; wherein the Data Fetch Response message comprises at least one of the MBMS session identity and the MBMS session performance parameter; specifically, when the source eNB and the target eNB satisfy a first condition, the Data Fetch Response message includes: the MBMS conversation mark; when the source eNB and the target eNB meet a second condition, the Data Fetch Response message comprises: the MBMS session identity and the MBMS session performance parameter.
EXAMPLE five
Based on the same technical concept of the foregoing embodiments, referring to fig. 14, which shows a structure of a target eNB140 provided by an embodiment of the present invention, the target eNB140 may include: a second establishing module 1401 and a receiving module 1402; wherein the content of the first and second substances,
the second establishing module 1401 is configured to establish a transmission channel with the source eNB according to a preset establishing policy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
the receiving module 1402 is configured to receive, through the transmission channel, a V2X message or a normal V2X message carried in an MBMS session transmitted by the source eNB.
Exemplarily, referring to fig. 15, the second establishing module 1401 comprises: a fourth receiving unit 14011 and a third transmitting unit 14012; wherein the content of the first and second substances,
the fourth receiving unit 14011, configured to receive the first request to establish a tunnel sent by the source eNB;
the third sending unit 14012 is configured to send a first acknowledgement setup channel reply to the source eNB.
When the V2X message is a V2X message carried in an MBMS session, in a specific implementation, the fourth receiving unit 14011 is specifically configured to: receiving an X2Setup Request message sent by the source eNB; wherein the X2Setup Request message comprises at least one of the MBMS session identity and the MBMS session performance parameters; specifically, when the source eNB and the target eNB satisfy a first condition, the X2Setup Request message includes: the MBMS conversation mark; when the source eNB and the target eNB satisfy a second condition, the X2Setup Request message includes: the MBMS session identity and the MBMS session performance parameter;
accordingly, the third sending unit 14012 is specifically configured to send an X2Setup Response message to the source eNB; wherein, the X2Setup Response message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the MBMS session for the target eNB to receive.
When the V2X message is a V2X message carried in an MBMS session, in another specific implementation manner, the fourth receiving unit 14011 is specifically configured to: receiving an eNB Configuration Update message sent by the source eNB; wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter; specifically, when the source eNB and the target eNB satisfy a first condition, the eNB Configuration Update message includes: the MBMS conversation mark; when the source eNB and the target eNB satisfy a second condition, the eNB Configuration Update message includes: the MBMS session identity and the MBMS session performance parameter;
correspondingly, the third sending unit 14012 is specifically configured to send an eNB Configuration Update acknowledgement message to the source eNB; wherein the eNB Configuration Update acknowledgement message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
It should be additionally noted that, when the V2X message is a normal V2X message, the first tunnel establishment Request includes an X2Setup Request message or an eNB Configuration Update message; wherein, the X2Setup Request message or the eNB Configuration Update message is used for indicating the target eNB to establish a GTP tunnel for forwarding the common V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction;
correspondingly, the first acknowledgement channel establishment reply correspondingly comprises an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of the service type, performance parameter, and GTP tunnel identity.
Exemplarily, referring to fig. 16, the second establishing module 1401 specifically includes: a fourth transmitting unit 14013 and a fifth receiving unit 14014; wherein the content of the first and second substances,
the fourth sending unit 14013, configured to send a second request to establish a tunnel to the source eNB;
the fifth receiving unit 14014, configured to receive a second acknowledgement setup channel reply sent by the source eNB.
In a specific implementation manner, the fourth sending unit 14013 is specifically configured to send a Data Fetch Request message to the source eNB; the Data Fetch Request message comprises the MBMS session identifier, a GTP tunnel identifier corresponding to the MBMS session and a User Equipment (UE) identifier corresponding to the MBMS session, wherein the target eNB is used for receiving the GTP tunnel identifier corresponding to the MBMS session;
accordingly, the fifth receiving unit 14014 is specifically configured to receive a Data Fetch Response message sent by the source eNB; wherein the Data Fetch Response message comprises at least one of the MBMS session identity and the MBMS session performance parameter; specifically, when the source eNB and the target eNB satisfy a first condition, the Data Fetch Response message includes: the MBMS conversation mark; when the source eNB and the target eNB meet a second condition, the Data Fetch Response message comprises: the MBMS session identity and the MBMS session performance parameter.
EXAMPLE six
Based on the same technical concept as the foregoing embodiment, referring to fig. 17, a message forwarding system 170 according to an embodiment of the present invention is shown, where the message forwarding system 170 may include: source eNB110 and target eNB 140; wherein the content of the first and second substances,
the source eNB110 is configured to establish a transmission channel with the target eNB140 according to a preset establishment policy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
and transmitting the V2X message or the normal V2X message carried in the MBMS session to the target eNB140 through the transmission channel;
the target eNB140 is configured to establish a transmission channel with the source eNB110 according to a preset establishment policy;
and, receiving the V2X message or the general V2X message carried in the MBMS session transmitted by the source eNB110 through the transmission channel.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims (17)

1. A method of message forwarding, the method comprising:
a source evolution type base station eNB establishes a transmission channel with a target eNB according to a preset establishment strategy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
the source eNB transmits a vehicle networking V2X message or a common vehicle networking V2X message carried in a multimedia broadcast/multicast service (MBMS) session to the target eNB through the transmission channel;
the method for establishing the transmission channel between the source eNB and the target eNB according to the preset establishment strategy specifically comprises the following steps:
the source eNB receives control plane signaling or user plane data from an upper network element; when the control plane signaling or the user plane data comprises the cell identification of the target eNB, the source eNB sends a first channel establishing request to the target eNB; the source eNB receives a first confirmation establishment channel reply sent by the target eNB; alternatively, the first and second electrodes may be,
the source eNB receives a second channel establishment request sent by the target eNB; the source eNB sends a second acknowledgement setup channel reply to the target eNB;
the receiving, by the source eNB, the second request for establishing the channel sent by the target eNB specifically includes:
the source eNB receives a Data Fetch Request message sent by the target eNB; the Data Fetch Request message comprises at least one of the MBMS session identifier, a GTP tunnel identifier corresponding to the MBMS session and a User Equipment (UE) identifier corresponding to the MBMS session, wherein the target eNB is used for receiving the MBMS session identifier;
correspondingly, the sending, by the source eNB, a second acknowledgement to establish a channel reply to the target eNB specifically includes:
the source eNB sends a Data Fetch Response message to the target eNB; wherein the Data Fetch Response message includes at least one of the MBMS session identity and the MBMS session performance parameter.
2. The method of claim 1, wherein when the V2X message is a V2X message carried in an MBMS session, the sending, by the source eNB, a first setup channel request to the target eNB comprises:
the source eNB sends an X2Setup Request message to the target eNB; wherein the X2Setup Request message includes at least one of the MBMS session identity and the MBMS session performance parameters;
correspondingly, the receiving, by the source eNB, the first acknowledgement setup channel reply sent by the target eNB specifically includes:
the source eNB receiving an X2Setup Response message sent by the target eNB after accepting the X2Setup Request message; wherein, the X2Setup Response message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
3. The method of claim 1, wherein when the V2X message is a V2X message carried in an MBMS session, the sending, by the source eNB, a first setup channel request to the target eNB comprises:
the source eNB sends an eNB Configuration Update message to the target eNB; wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter;
correspondingly, the receiving, by the source eNB, the first acknowledgement setup channel reply sent by the target eNB specifically includes:
the source eNB receives an eNB Configuration Update acknowledgement message sent by the target eNB after the target eNB accepts the eNB Configuration Update message; wherein the eNB Configuration Update acknowledgement message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
4. The method according to claim 1, wherein when the V2X message is a general internet of vehicles V2X message, the first Setup channel Request comprises an X2Setup Request message or an eNB Configuration Update message; wherein the X2Setup Request message or eNB Configuration Update message is used to instruct the target eNB to establish a GTP tunnel for forwarding the common vehicle networking V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction data;
correspondingly, the first acknowledgement channel establishment reply correspondence includes an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of the traffic type, performance parameter, and GTP tunnel identification.
5. A method of message forwarding, the method comprising:
according to a preset establishing strategy, a transmission channel is established between a target evolution type base station eNB and a source eNB; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
the target eNB receives a vehicle networking V2X message or a common vehicle networking V2X message carried in a multimedia broadcast/multicast service (MBMS) session transmitted by the source eNB through the transmission channel;
according to a preset establishment strategy, the target eNB and the source eNB establish a transmission channel, and the method specifically comprises the following steps:
the target eNB receives a first channel establishment request sent by the source eNB; the target eNB sends a first acknowledgement setup channel reply to the source eNB; alternatively, the first and second electrodes may be,
the target eNB sends a second channel establishment request to the source eNB; the target eNB receiving a second acknowledgement setup channel reply sent by the source eNB;
the sending, by the target eNB, the second request to establish the channel to the source eNB specifically includes:
the target eNB sends a Data Fetch Request message to the source eNB; the Data Fetch Request message comprises the MBMS session identifier, a GTP tunnel identifier corresponding to the MBMS session and a User Equipment (UE) identifier corresponding to the MBMS session, wherein the target eNB is used for receiving the GTP tunnel identifier corresponding to the MBMS session;
correspondingly, the receiving, by the target eNB, the second acknowledgement setup channel reply sent by the source eNB specifically includes:
the target eNB receives a Data Fetch Response message sent by the source eNB; wherein the Data Fetch Response message includes at least one of the MBMS session identity and the MBMS session performance parameter.
6. The method of claim 5, wherein when the V2X message is a V2X message carried in an MBMS session, the receiving, by the target eNB, the first request to establish the channel sent by the source eNB comprises:
the target eNB receiving an X2Setup Request message sent by the source eNB; wherein the X2Setup Request message includes at least one of the MBMS session identity and the MBMS session performance parameters;
correspondingly, the sending, by the target eNB, a first acknowledgement setup channel reply to the source eNB specifically includes:
the target eNB sends an X2Setup Response message to the source eNB after accepting the X2Setup Request message; wherein, the X2Setup Response message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
7. The method of claim 5, wherein when the V2X message is a V2X message carried in an MBMS session, the receiving, by the target eNB, the first request to establish the channel sent by the source eNB comprises:
the target eNB receives an eNB Configuration Update message sent by the source eNB; wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter;
correspondingly, the sending, by the target eNB, a first acknowledgement setup channel reply to the source eNB specifically includes: after receiving the eNB Configuration Update message, the target eNB sends an eNB Configuration Update Acknowledgemessage to the source eNB; wherein the eNB Configuration Update acknowledgement message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
8. The method of claim 5, wherein when the V2X message is a common Internet of vehicles V2X message, the first Setup channel Request comprises an X2Setup Request message or an eNB Configuration Update message; wherein the X2Setup Request message or eNB Configuration Update message is used to instruct the target eNB to establish a GTP tunnel for forwarding the common vehicle networking V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction data;
correspondingly, the first acknowledgement Setup channel reply correspondence includes an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of the traffic type, performance parameter, and GTP tunnel identification.
9. A source evolved base station, eNB, comprising: the device comprises a first establishing module and a transmission module; wherein the content of the first and second substances,
the first establishing module is used for establishing a transmission channel with the target eNB according to a preset establishing strategy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
the transmission module is used for transmitting the Internet of vehicles V2X message or the common Internet of vehicles V2X message carried in the multimedia broadcast/multicast service MBMS session to the target eNB through the transmission channel;
the first establishing module specifically includes: a first receiving unit, a first transmitting unit and a second receiving unit; the first receiving unit is configured to receive control plane signaling or user plane data from an upper network element; the first sending unit is configured to send a first request for establishing a channel to the target eNB when the control plane signaling or the user plane data includes the cell identifier of the target eNB; the second receiving unit is configured to receive a first acknowledgement setup channel reply sent by the target eNB; alternatively, the first and second electrodes may be,
the first establishing module specifically includes: a third receiving unit and a second transmitting unit; the third receiving unit is configured to receive a second request for establishing a channel, which is sent by the target eNB; the second sending unit is configured to send a second acknowledgement channel setup reply to the target eNB;
the third receiving unit is specifically configured to receive a Data Fetch Request message sent by the target eNB; the Data Fetch Request message comprises the MBMS session identifier, a GTP tunnel identifier corresponding to the MBMS session and a User Equipment (UE) identifier corresponding to the MBMS session, wherein the target eNB is used for receiving the GTP tunnel identifier corresponding to the MBMS session;
correspondingly, the second sending unit is specifically configured to send a Data Fetch Response message to the target eNB; wherein the Data Fetch Response message includes at least one of the MBMS session identity and the MBMS session performance parameter.
10. The source eNB of claim 9, wherein when the V2X message is a V2X message carried in an MBMS session, the first sending unit is specifically configured to: sending an X2Setup Request message to the target eNB;
wherein the X2Setup Request message includes at least one of the MBMS session identity and the MBMS session performance parameters;
correspondingly, the second receiving unit is specifically configured to:
receiving an X2Setup Response message sent by the target eNB after accepting the X2Setup Request message; wherein, the X2Setup Response message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
11. The source eNB of claim 9, wherein when the V2X message is a V2X message carried in an MBMS session, the first sending unit is specifically configured to: sending an eNB Configuration Update message to the target eNB;
wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter;
correspondingly, the second receiving unit is specifically configured to:
receiving an eNB Configuration Update Acknowledgemessage sent by the target eNB after accepting the eNB Configuration Update message; wherein the eNB Configuration Update acknowledgement message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
12. The source eNB of claim 9, wherein when the V2X message is a general internet of vehicles V2X message, the first Setup channel Request comprises an X2Setup Request message or an eNB Configuration Update message; wherein the X2Setup Request message or eNB Configuration Update message is used to instruct the target eNB to establish a GTP tunnel for forwarding the common vehicle networking V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction data;
correspondingly, the first acknowledgement Setup channel reply correspondence includes an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of the traffic type, performance parameter, and GTP tunnel identification.
13. A target evolved node B (eNB), the target eNB comprising: the second establishing module and the receiving module; wherein the content of the first and second substances,
the second establishing module is used for establishing a transmission channel with the source eNB according to a preset establishing strategy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
the receiving module is configured to receive, through the transmission channel, a vehicle networking V2X message or a general vehicle networking V2X message carried in a multimedia broadcast/multicast service MBMS session transmitted by the source eNB;
the second establishing module comprises: a fourth receiving unit and a third transmitting unit; the fourth receiving unit is configured to receive a first request for establishing a channel, which is sent by the source eNB; the third sending unit is configured to send a first acknowledgement setup channel reply to the source eNB; alternatively, the first and second electrodes may be,
the second establishing module specifically includes: a fourth transmitting unit and a fifth receiving unit; the fourth sending unit is configured to send a second request for establishing a channel to the source eNB; the fifth receiving unit is configured to receive a second acknowledgement setup channel reply sent by the source eNB;
the fourth sending unit is specifically configured to send a Data Fetch Request message to the source eNB; the Data Fetch Request message comprises the MBMS session identifier, a GTP tunnel identifier corresponding to the MBMS session and a User Equipment (UE) identifier corresponding to the MBMS session, wherein the target eNB is used for receiving the GTP tunnel identifier corresponding to the MBMS session;
correspondingly, the fifth receiving unit is specifically configured to receive a Data Fetch Response message sent by the source eNB; wherein the Data Fetch Response message includes at least one of the MBMS session identity and the MBMS session performance parameter.
14. The target eNB of claim 13, wherein when said V2X message is a V2X message carried in an MBMS session, said fourth receiving unit is specifically configured to: receiving an X2Setup Request message sent by the source eNB; wherein the X2Setup Request message includes at least one of the MBMS session identity and the MBMS session performance parameters;
correspondingly, the third sending unit is specifically configured to send an X2Setup Response message to the source eNB; wherein, the X2Setup Response message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
15. The target eNB of claim 13, wherein when said V2X message is a V2X message carried in an MBMS session, said fourth receiving unit is specifically configured to: receiving an eNB Configuration Update message sent by the source eNB; wherein the eNB Configuration Update message comprises at least one of the MBMS session identity and the MBMS session performance parameter;
correspondingly, the third sending unit is specifically configured to send an eNB Configuration Update acknowledgement message to the source eNB; wherein the eNB Configuration Update acknowledgement message includes the MBMS session identifier and a GTP tunnel identifier corresponding to the target eNB for receiving the MBMS session.
16. The target eNB of claim 13, wherein when said V2X message is a general internet of vehicles V2X message, said first Setup channel Request comprises an X2Setup Request message or an eNB Configuration Update message; wherein the X2Setup Request message or eNB Configuration Update message is used to instruct the target eNB to establish a GTP tunnel for forwarding the common vehicle networking V2X message; the X2Setup Request message or the eNB Configuration Update message comprises at least one of a service type, a performance parameter and a data forwarding instruction data;
correspondingly, the first acknowledgement Setup channel reply correspondence includes an X2Setup Response message or an eNB Configuration Update acknowledgement message; wherein, the X2Setup Response message or eNB Configuration Update acknowledgement message is used to indicate GTP tunnel information established by the target eNB for the service; and the X2Setup Response message or eNB Configuration Update acknowledgement message includes at least one of the traffic type, performance parameter, and GTP tunnel identification.
17. A system for message forwarding, the system comprising: the source eNB of any of claims 9-12 and the target eNB of any of claims 13-16; wherein the content of the first and second substances,
the source eNB is used for establishing a transmission channel with the target eNB according to a preset establishment strategy; wherein the transport tunnel comprises a general packet radio service technology tunneling protocol, GTP, tunnel;
and transmitting the vehicle networking V2X message or the common vehicle networking V2X message carried in the multimedia broadcast/multicast service MBMS session to the target eNB through the transmission channel;
the target eNB is used for establishing a transmission channel with the source eNB according to a preset establishment strategy;
and receiving the V2X message or the common Internet of vehicles V2X message carried in the MBMS session transmitted by the source eNB through the transmission channel.
CN201610080014.8A 2016-02-04 2016-02-04 Method, equipment and system for forwarding message Active CN107041016B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201610080014.8A CN107041016B (en) 2016-02-04 2016-02-04 Method, equipment and system for forwarding message
PCT/CN2017/072700 WO2017133629A1 (en) 2016-02-04 2017-01-25 Message forwarding method, device, system, and computer storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610080014.8A CN107041016B (en) 2016-02-04 2016-02-04 Method, equipment and system for forwarding message

Publications (2)

Publication Number Publication Date
CN107041016A CN107041016A (en) 2017-08-11
CN107041016B true CN107041016B (en) 2021-02-02

Family

ID=59499354

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610080014.8A Active CN107041016B (en) 2016-02-04 2016-02-04 Method, equipment and system for forwarding message

Country Status (2)

Country Link
CN (1) CN107041016B (en)
WO (1) WO2017133629A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109672708B (en) * 2017-10-16 2022-03-11 华为技术有限公司 Communication method, device and system
EP3621274B1 (en) * 2018-09-04 2022-04-20 Volkswagen Aktiengesellschaft Method for predicting a quality of service for a communication between at least two moving communication partners, apparatus for performing steps of the method, vehicle, backend server and computer program
WO2021189458A1 (en) * 2020-03-27 2021-09-30 Oppo广东移动通信有限公司 Data forwarding method and apparatus, and communication device
WO2022041976A1 (en) * 2020-08-26 2022-03-03 Telefonaktiebolaget Lm Ericsson (Publ) Methods, entities, application server and computer readable media for local mbms based mbms data delivery

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101998336A (en) * 2009-08-21 2011-03-30 中兴通讯股份有限公司 System and method for synchronizing closed subscriber group list
CN102083006A (en) * 2011-01-17 2011-06-01 大唐移动通信设备有限公司 Data transmission method, device and system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102076054A (en) * 2011-02-18 2011-05-25 电信科学技术研究院 Direct forwarding tunnel setup and using method, system and equipment

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101998336A (en) * 2009-08-21 2011-03-30 中兴通讯股份有限公司 System and method for synchronizing closed subscriber group list
CN102083006A (en) * 2011-01-17 2011-06-01 大唐移动通信设备有限公司 Data transmission method, device and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
General discussion RAN3 Impacts on LTE-based V2X,R3-152464;Samsung;<3GPP TSG-RAN WG3 Meeting #90>;20151120;2.Discussion,图3 *

Also Published As

Publication number Publication date
CN107041016A (en) 2017-08-11
WO2017133629A1 (en) 2017-08-10

Similar Documents

Publication Publication Date Title
WO2017133624A1 (en) Method and device for broadcasting vehicle-to-everything communications (v2x) message and method for establishing mbms bearer
US10327252B2 (en) Method and apparatus for receiving V2X message
CN106341839B (en) A kind of information reporting, reception, carry the method and device of foundation
CN109155949A (en) Interoperability methods and its device in wireless communication between networks
CN110198556B (en) Radio Resource Control (RRC) message processing method, device and system
WO2017133467A1 (en) Method for implementing internet of vehicles service and localized network architecture
CN111436115B (en) PDU session activation method, paging method and device thereof
CN106341848B (en) Switching method and device
EP2928220A1 (en) Method, system, base station and cluster epc for establishing group call context
CN104602344B (en) A kind of group of communication information notifying method and equipment
CN106341794B (en) A kind of method for sending information and device
US20230179958A1 (en) Multicast/broadcast information transmission method and device, storage medium, and electronic device
CN107041016B (en) Method, equipment and system for forwarding message
CN106341813B (en) Information sending and receiving method and device
CN109328472B (en) Switching method and device
WO2016020019A1 (en) Network sharing for multimedia broadcast multicast service
CN104869659A (en) Path establishment method, path establishment device, path establishment system and core network device
CN104283602A (en) Cluster relay method, device and system
CN107135485B (en) Method and device for establishing vehicle-to-everything session request and determining transmission cell
CN110446274B (en) Tunnel establishment method and device
WO2017166900A1 (en) Method for receiving multimedia broadcast multicast service, and terminal, base station and storage medium
WO2016061791A1 (en) Method and apparatus for establishing interface
US10993083B2 (en) Method and apparatus for notifying information about MBMS network
CN108243394B (en) LTE broadband trunking communication method and device
CN109155785B (en) V2X message transmission method and related network element

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant