WO2017005133A1 - 一种信息发送接收方法及装置 - Google Patents

一种信息发送接收方法及装置 Download PDF

Info

Publication number
WO2017005133A1
WO2017005133A1 PCT/CN2016/087972 CN2016087972W WO2017005133A1 WO 2017005133 A1 WO2017005133 A1 WO 2017005133A1 CN 2016087972 W CN2016087972 W CN 2016087972W WO 2017005133 A1 WO2017005133 A1 WO 2017005133A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
cell
mbsfn area
base station
public key
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2016/087972
Other languages
English (en)
French (fr)
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.)
China Academy of Telecommunications Technology CATT
Original Assignee
China Academy of Telecommunications Technology CATT
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 China Academy of Telecommunications Technology CATT filed Critical China Academy of Telecommunications Technology CATT
Publication of WO2017005133A1 publication Critical patent/WO2017005133A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements

Definitions

  • the present invention relates to the field of wireless communication technologies, and in particular, to a method and an apparatus for transmitting and receiving information.
  • MTC Machine Type Communication
  • MTC system applications will bring new technical challenges to mobile communications, such as real-time cloud computing, virtual reality, online games, telemedicine, intelligent transportation, smart grid, remote real-time control, etc. , put forward higher demand for delay.
  • mobile communications such as real-time cloud computing, virtual reality, online games, telemedicine, intelligent transportation, smart grid, remote real-time control, etc.
  • the application of these services also puts higher requirements on the delay of information interaction.
  • V2X Vehicle to Everything
  • V2V vehicle-to-vehicle information exchange
  • V2I vehicle-to-Infrastructure
  • V2P vehicle-to-person information exchange
  • the active security early warning technology that V2X communication mode senses road safety risks in advance is a new way of thinking about solving road traffic safety problems in various countries. It informs each other's current status through real-time information interaction between vehicles, vehicles, vehicles and roadside infrastructure.
  • Some typical applications include emergency braking alarms, coordinated combined assistance, and traffic signal violation warnings.
  • the MBMS evolved MBMS
  • LTE Long Term Evolution
  • MBMS Multimedia Broadcast/Multicast Service
  • the eMBMS supports the Multicast Broadcast Single Frequency Network (MBSFN) transmission mode, that is, cells belonging to the same MBSFN area simultaneously transmit the same content in multiple cells on the same time and frequency resources.
  • MBSFN Multicast Broadcast Single Frequency Network
  • the receiving user equipment can treat the signals sent by multiple cells as multiple paths of one signal, and process the signals to obtain macro diversity gain, thereby improving the signal receiving quality of the cell edge user.
  • V2X is used to support road safety applications. Usually, it is required that the sending vehicle receives the road safety message from the upper layer to the medium access control (MAC) layer of the receiving vehicle to deliver the road safety message to the upper layer. It is greater than 100ms, and the shortcoming of the prior art is that the total time delay of information interaction is 160ms based on the V2X service implemented by the existing eMBMS technology, which cannot meet the delay requirement for supporting road security applications.
  • MAC medium access control
  • the problem exists not only in the V2X service, but also in other similar environments or applications. That is, the existing information transmission based on the eMBMS technology cannot meet the delay requirements of some services.
  • the embodiment of the invention provides a method and a device for transmitting and receiving information, which are used to reduce the sending and receiving time of information.
  • An embodiment of the present invention provides an information sending method, including:
  • the first cell of the first base station and the second cell belonging to the first base station belonging to the same MBSFN area as the first base station transmit information to the designated terminal device on the time and frequency resources corresponding to the MBSFN area.
  • the method further includes:
  • the information is integrity protected with a private key, which is a private key corresponding to the MBSFN area.
  • the method further comprises:
  • the public key is from the MME and/or the MCE.
  • the information reported by the terminal device under the jurisdiction of the first cell to the first base station is V2X information for the V2X service.
  • one MBSFN area includes one first cell and at least one second cell.
  • An embodiment of the present invention provides an information sending method, including:
  • information is transmitted to the designated terminal device on the time and frequency resources corresponding to the MBSFN area.
  • the information is information for integrity protection with a private key
  • the private key is a private key corresponding to the MBSFN area.
  • the method further comprises:
  • the public key is a public key from an MME and/or an MCE.
  • the information is V2X information for V2X services.
  • one MBSFN area includes one first cell and at least one second cell.
  • An embodiment of the present invention provides an information receiving method, including:
  • the information is processed in accordance with rules corresponding to the MBSFN area.
  • processing the information according to the rule corresponding to the MBSFN area includes:
  • the public key is used to perform integrity verification on the integrity-protected information.
  • the public key is a public key obtained by one or a combination of the following: a public key transmitted by the base station, a public key stored in the terminal device, and a public key obtained by the roadside unit RSU.
  • the information is V2X information for V2X services.
  • one MBSFN area includes one first cell and at least one second cell.
  • An information sending apparatus is provided in the embodiment of the present invention, including:
  • the reporting information receiving module is configured to receive information reported by the terminal device that is managed by the first cell to the first base station, where the first cell is a cell that belongs to the first base station;
  • a distribution module configured to distribute the information to each second base station to which each second cell belonging to the same MBSFN area belongs to the first cell, where the information is to be in the MBSFN area in each second cell under each base station Corresponding time and frequency resources are sent;
  • a first sending module configured to: in the first cell of the first base station and the second cell belonging to the first cell that belongs to the same MBSFN area as the first cell, specify the time and frequency resources corresponding to the MBSFN area
  • the terminal device sends a message.
  • the method further comprises:
  • An integrity protection module configured to perform integrity protection with a private key when distributing information to the second base station and sending information to the designated terminal device, where the private key is associated with the MBSFN area The corresponding private key.
  • the first sending module is further configured to send, to the terminal device, a public key for performing integrity verification on the integrity-protected information, where the public key is a public key corresponding to the MBSFN area.
  • the first sending module is further configured to send the public key from the MME and/or the MCE to the terminal device.
  • the information reported by the terminal device under the jurisdiction of the first cell to the first base station is V2X information for the V2X service.
  • one MBSFN area includes one first cell and at least one second cell.
  • An information sending apparatus is provided in the embodiment of the present invention, including:
  • a distribution information receiving module configured to receive information from a first cell that is sent by the first base station to the second base station, where the first cell is a cell that belongs to the first base station;
  • a cell determining module configured to determine a second cell that belongs to the same MBSFN area as the first cell, where the second cell is a cell that belongs to the second base station;
  • the second sending module is configured to send information to the designated terminal device on the time and frequency resources corresponding to the MBSFN area in the second cell of the second base station.
  • the distribution information receiving module is further configured to receive information for integrity protection with a private key, the private key being a private key corresponding to the MBSFN area.
  • the method further comprises:
  • the second sending module is further configured to send, to the terminal device, a public key for performing integrity verification on the integrity-protected information, where the public key is a public key corresponding to the MBSFN area.
  • the second sending module is further configured to send the public key from the MME and/or the MCE to the terminal device.
  • the information is V2X information for V2X services.
  • one MBSFN area includes one first cell and at least one second cell.
  • An information receiving apparatus is provided in the embodiment of the present invention, including:
  • An information receiving module configured to receive information sent by a base station
  • a region determining module configured to determine a corresponding MBSFN region according to the time and frequency resources of the received information
  • An information processing module is configured to process information according to a rule corresponding to the MBSFN area.
  • the information processing module is further configured to: when the information is integrity-protected with a private key corresponding to the MBSFN area, determine a public key corresponding to the MBSFN area; using the public key Integrity verification of integrity-protected information.
  • the information processing module is further configured to obtain a public key obtained by one of the following methods or a combination thereof: a public key transmitted by the base station, a public key stored in the terminal device, and a public key obtained by the roadside unit RSU.
  • the information is V2X information for V2X services.
  • one MBSFN area includes one first cell and at least one second cell.
  • An embodiment of the present invention provides a first base station, including:
  • a processor for reading a program in the memory performing the following process:
  • a transceiver for transmitting data under the control of a processor performing the following processes:
  • the first cell of the first base station and the second cell belonging to the first base station belonging to the same MBSFN area as the first base station transmit information to the designated terminal device on the time and frequency resources corresponding to the MBSFN area.
  • the transceiver when the transceiver distributes information to the second base stations and sends information to the designated terminal device, the transceiver may further be used to:
  • the information is integrity protected with a private key, which is a private key corresponding to the MBSFN area.
  • the transceiver can be further used to:
  • the public key is from the MME and/or the MCE.
  • the information reported by the terminal device under the jurisdiction of the first cell to the first base station is V2X information for the V2X service.
  • one MBSFN area includes one first cell and at least one second cell.
  • An embodiment of the present invention provides a second base station, including:
  • a processor for reading a program in the memory performing the following process:
  • a transceiver for transmitting data under the control of a processor performing the following processes:
  • information is transmitted to the designated terminal device on the time and frequency resources corresponding to the MBSFN area.
  • the information is information for integrity protection with a private key
  • the private key is a private key corresponding to the MBSFN area.
  • the transceiver can be further used to:
  • the public key may be a public key from an MME and/or an MCE.
  • the information may be V2X information for V2X services.
  • one MBSFN area includes one first cell and at least one second cell.
  • An embodiment of the present invention provides a terminal device, including:
  • a processor for reading a program in the memory performing the following process:
  • a transceiver for transmitting data under the control of a processor performing the following processes:
  • the processor when the information is integrity-protected by using the private key corresponding to the MBSFN area, when the information is processed according to the rule corresponding to the MBSFN area, the processor may be further configured to:
  • the public key is used to perform integrity verification on the integrity-protected information.
  • the public key may be a public key obtained by one or a combination of the following: a public key sent by the base station, a public key stored in the terminal device, and a public key obtained by the roadside unit RSU.
  • the information is V2X information for V2X services.
  • one MBSFN area includes one first cell and at least one second cell.
  • the base station after receiving the information reported by each terminal device of the cell under its own jurisdiction, the base station sends the information to the relevant base station, if the base station is sent.
  • the cell to which the terminal device reporting the information belongs is the first cell
  • the related base stations receiving the information are the second base station, and then some cells in the first cell and the second base station belong to the same MBSFN area. of;
  • the first base station ie, the second base station
  • the information is sent to the required terminal device on the same time and frequency resource on the first base station and the associated second base station, so that the terminal devices in the same MBSFN area receive the same from the same
  • the information reported by the terminal device of the cell, and the transmission resources of each MBSFN area are different, so that each MBSFN area data is not interfered with each other when receiving.
  • the information reported by the terminal device is not reported to the S-GW, the P-GW, the BMSC, etc. of the network side, and then the BMSC indicates that the base station adopts the MBSFN.
  • the mode is transmitted; the information exchanged by the terminal device is directly transmitted between the base stations, and is distributed to each base station to be transmitted in the MBSFN mode after being processed on the base station. Since there is no transit of the core network entities on the network side, the MBSFN mode is reduced.
  • the time-consuming manner of sending the MBMS data makes the technical solution provided in the embodiment of the present invention meet the requirements of some services with specific requirements for delay.
  • the embodiment of the present invention further provides a processing scheme for information integrity protection and verification, and improves information security.
  • FIG. 1 is a schematic structural diagram of an eMBMS system according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a network for implementing V2X communication based on eMBMS according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a network structure for implementing enhanced V2X communication based on eMBMS according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of an implementation process of an information sending method according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of an implementation process of information sending method 2 according to an embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of an implementation process of an information receiving method according to an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of an implementation process of a method for transmitting and receiving information according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of an MBSFN area according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram showing the structure of an MBSFN area in a high speed scene according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a relationship between a cell and an MBSFN area according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a relationship between a cell and an MBSFN area in a highway scene according to an embodiment of the present invention
  • FIG. 12 is a schematic flowchart of an implementation process of establishing a signaling interaction process for an X2 interface MBSFN data transmission channel according to an embodiment of the present invention
  • FIG. 13 is a schematic flowchart of an implementation process of an X2 interface MBSFN data transmission channel configuration update process according to an embodiment of the present invention
  • FIG. 14 is a flowchart showing an implementation process of an X2 interface MBSFN data transmission channel deactivation/release process according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of an EPS bearer according to an embodiment of the present invention.
  • 16 is a schematic flowchart of an implementation process of an information reporting method according to an embodiment of the present invention.
  • FIG. 17 is a schematic flowchart of an implementation process of a bearer establishing method according to an embodiment of the present invention.
  • FIG. 18 is a schematic flowchart of an implementation method of an information receiving method of an access network node according to an embodiment of the present invention.
  • FIG. 19 is a schematic structural diagram of an LTE network according to an embodiment of the present invention.
  • 20 is a schematic diagram of a non-contention random access handover procedure of an LTE system through an X2 interface according to an embodiment of the present invention
  • FIG. 21 is a schematic diagram of a non-contention random access handover procedure of an LTE system through an S1 interface according to an embodiment of the present disclosure
  • FIG. 22 is a schematic flowchart of a method for implementing handover on a source base station side according to an embodiment of the present invention
  • FIG. 23 is a schematic flowchart of a method for implementing handover on a target base station side according to an embodiment of the present invention.
  • 24 is a schematic diagram of an integrity protection process according to an embodiment of the present invention.
  • 25 is a schematic diagram of an information transmission implementation environment for performing security processing according to an embodiment of the present invention.
  • 26 is a schematic diagram of a key processing implementation environment in information security processing according to an embodiment of the present invention.
  • FIG. 27 is a schematic structural diagram of an information sending apparatus according to an embodiment of the present invention.
  • 29 is a schematic structural diagram of an information receiving apparatus according to an embodiment of the present invention.
  • FIG. 30 is a schematic structural diagram of a first base station according to an embodiment of the present invention.
  • FIG. 31 is a schematic structural diagram of a second base station according to an embodiment of the present invention.
  • FIG. 32 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • UMTS Universal Mobile Telecommunication System
  • a user equipment includes but is not limited to a mobile station (Mobile Station, MS), a mobile terminal (Mobile Terminal), a mobile telephone (Mobile Telephone),
  • the user equipment can communicate with one or more core networks via a Radio Access Network (RAN), for example, the user equipment can be a mobile phone (or called a mobile device).
  • RAN Radio Access Network
  • the user devices can also be portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile devices.
  • a base station may refer to a device in an access network that communicates with a wireless terminal over one or more sectors over an air interface.
  • the base station can be used to convert the received air frame to the IP packet as a router between the wireless terminal and the rest of the access network, wherein the remainder of the access network can include an Internet Protocol (IP) network.
  • IP Internet Protocol
  • the base station can also coordinate attribute management of the air interface.
  • the base station may be a Base Transceiver Station (BTS) in GSM or CDMA, or may be a base station (NodeB) in WCDMA, or may be an evolved base station in LTE (NodeB or eNB or e-NodeB, evolutional Node B), the invention is not limited.
  • BTS Base Transceiver Station
  • NodeB base station
  • NodeB evolved base station
  • LTE Long Term Evolutional Node B
  • the V2X service has a total delay of 160 ms.
  • FIG. 1 is a schematic diagram of the eMBMS system architecture.
  • the eMBMS system architecture mainly includes a broadcast multicast service center (BMSC), an MBMS gateway (MBMS Gateway, MBMS GW), and a mobility management entity (Mobility Management). Entity, MME), Multi-cell/Multicast Coordination Entity (MCE), and evolved base station (eNB), where:
  • BMSC Provides MBMS services and initiates an MBMS bearer setup process.
  • MBMS GW The MBMS service data is transmitted to each eNB in an IP multicast manner. Interact with MBMS session control signaling with the MME.
  • MME Implements MBMS session control by communicating with the MCE through the M3 interface according to the session control signaling received from the MBMS GW.
  • MCE responsible for the allocation of MBMS resources of each eNB.
  • the generated MBMS service notification information is sent to the eNB.
  • the MBMS service data packet received from the BMSC is transmitted in a broadcast manner at a set time.
  • the MBMS service notification information received from the MCE is broadcasted.
  • the main parts of the V2X communication scheme based on eMBMS are as follows:
  • FIG. 2 is a schematic diagram of a network structure for implementing V2X communication based on eMBMS. As shown in the figure, the method for implementing V2X communication based on eMBMS is:
  • the vehicle UE uses unicast to report road safety related information such as the position, speed, acceleration, driving route and learned road environment information of the vehicle, and the eNB reports the vehicle.
  • the road safety related information is sent to the BMSC through an entity such as a Serving Gateway (S-GW) and a Packet Data Network Gateway (PDN), and the BMSC uses the road safety related information reported by each vehicle.
  • S-GW Serving Gateway
  • PDN Packet Data Network Gateway
  • the MBSFN method is transmitted to the relevant cells around each vehicle.
  • the MSP is a multicast channel scheduling period (Multicast Channel Scheduling Period).
  • the delay generated on the network side can be reduced.
  • the characteristics of the access network can be utilized as much as possible to reduce the delay.
  • inter-eNBs can directly communicate with other eNBs through an X2 interface or an S1 interface, thereby implementing seamless radio resource management and coordinated data transmission.
  • the technical solution based on the X2 interface is provided in the embodiment of the present invention, that is, in order to reduce the end-to-end delay of the V2X based on the eMBMS technology.
  • An enhanced V2X communication scheme based on eMBMS is proposed. The scheme is mainly designed as follows:
  • FIG. 3 is a schematic diagram of an enhanced network structure for implementing V2X communication based on eMBMS. As shown in the figure, the technical solution based on the X2 interface in the structure is mainly as follows:
  • the vehicle UE uses unicast to report road safety related information to the serving cell, such as the location, speed, acceleration, driving route and learned road environment information of the vehicle.
  • the eNB supports each of the following ( The road safety related information reported by the vehicle in the cell of the V2X service is transmitted to the neighboring eNB through the X2 interface, and the cell in the neighboring eNB transmits the road safety information collected under the MBSFN area data source cell to the UE by using the MBSFN method.
  • the delay analysis of transmitting the road safety information reported by the vehicle on the vehicle to the surrounding vehicle is as follows:
  • the eNB When there is no X2 interface between adjacent eNBs, the eNB exchanges road safety related information reported by the vehicles in the cells supporting the (specific) V2X services with the neighboring eNBs through the S1 interface forwarding mode, and the neighboring eNBs
  • the cell uses the MBSFN method to transmit the road security information collected under the MBSFN area data source cell to the UE.
  • the delay analysis of the road safety information transmitted by the vehicle that reports the road safety information to the surrounding vehicle is transmitted as follows:
  • the embodiments of the present invention respectively provide a solution for implementing the concept on a base station as follows:
  • the first base station is a base station that receives information reported by each terminal device, where the first cell is a cell belonging to the first base station, and each terminal device is a terminal device under the jurisdiction of the first cell;
  • the first base station sends the information to the second base station after receiving the information, and the second base station may have multiple, but the requirement is that the second cell belonging to the second base station belongs to the same MBSFN area as the first cell;
  • the second cell it should be noted that there is also a second cell that belongs to the first base station. Similarly, the requirement of the second cell belongs to the same MBSFN area as the first cell, that is, belongs to the same MBSFN area as the first cell.
  • the other cells are referred to as the second cell in the embodiment.
  • the first base station and the second base station send information to the terminal devices of the first cell and the second cell on the same time and frequency resource, so that the terminal devices in the same MBSFN area are simultaneously received. Information reported by terminal devices from the same cell.
  • the terminal device does not directly belong to the base station, but belongs to the logically divided cell.
  • the reason for the description is that the MBSFN area in the solution is composed of cells, and the foregoing description is for the purpose of understanding. Only physical descriptions are made.
  • the implementation of the cell will also be described below.
  • the terminal device includes not only the mobile terminal device but also various terminal devices used in the MTC, for example, in real-time cloud computing, virtual reality, online games, telemedicine, intelligent transportation, smart grid, remote real-time control, and the like. Sensors, data acquisition devices, etc.
  • the V2X service is mainly used as an example, and the typical representative UE of the terminal device is used as the terminal device, and the representative representative eNB of the base station is used as the base station, and the interactive information is the V2X information in the V2X service. It is easy to know that in the above scheme, in the example, it can be:
  • the first base station is a base station that receives V2X information reported by each UE in the V2X service, each UE is a UE under the jurisdiction of the first cell, and the first cell is a cell belonging to the first base station;
  • the first base station sends the V2X information to the second base station, and the second base station may have multiple, but the requirement is that the second cell belonging to the second base station belongs to the same MBSFN area as the first cell;
  • the first base station and the second base station send V2X information to each UE in the first cell and the second cell on the same time and frequency resource, so that UEs in the same MBSFN area receive the same from the UE.
  • V2X information reported by the UE in the same cell.
  • FIG. 4 is a schematic diagram of an implementation process of an information sending method. As shown in the figure, the following steps may be included:
  • Step 401 Receive information reported by the terminal device that is managed by the first cell to the first base station, where the first cell is a cell that belongs to the first base station.
  • Step 402 Distribute the information to each second base station to which each second cell belonging to the same MBSFN area belongs to the first cell, where the information is to be corresponding to the MBSFN area in each second cell under each base station. Send on time and frequency resources;
  • information is also distributed to each second cell of the MBSFN area with the first cell as the data source cell.
  • Each of the second base stations that belong to, wherein the concept of the data source cell will be described below.
  • Step 403 Send information to the designated terminal device on the time and frequency resources corresponding to the MBSFN area in the first cell of the first base station and the second cell belonging to the first cell that belongs to the same MBSFN area as the first cell. .
  • the information is transmitted in the second cell belonging to the MBSFN area belonging to the first cell as the data source cell, and the concept of the data source cell will be described below.
  • the information sending method 1 in the V2X service may include the following steps:
  • the V2X information is distributed to the second base stations to which the second cells belonging to the same MBSFN area belong to the first cell, and the V2X information is corresponding to the MBSFN area in each second cell under each base station. Send on time and frequency resources;
  • the V2X information is transmitted on the time and frequency resources corresponding to the MBSFN area in the first cell of the first base station and the second cell belonging to the first cell that belongs to the same MBSFN area as the first cell.
  • FIG. 5 is a schematic flowchart of the second embodiment of the information sending method. As shown in the figure, the following steps may be included:
  • Step 501 Receive information from a first cell that is sent by a first base station to a second base station, where the first cell is a cell that belongs to the first base station.
  • Step 502 Determine a second cell that belongs to the same MBSFN area as the first cell, where the second cell is a cell that belongs to the second base station.
  • the second cells belonging to the MBSFN area with the first cell as the data source cell are determined, and the concept of the data source cell will be described below.
  • Step 503 Send information in the second base station with time and frequency resources corresponding to the MBSFN area.
  • the information sending method 2 in the V2X service may include the following steps:
  • the V2X information is transmitted by the second base station with time and frequency resources corresponding to the MBSFN area.
  • FIG. 6 is a schematic diagram of an implementation process of an information receiving method, as shown in the figure, which may include the following steps:
  • Step 601 Receive information sent by a base station.
  • Step 602 Determine a corresponding MBSFN area according to the time and frequency resources of the received information.
  • Step 603 Process information according to a rule corresponding to the MBSFN area.
  • the corresponding relationship between the time and the frequency resource corresponding to each MBSFN area may be determined first, for example, Determining, according to the received system information, a correspondence between time and frequency resources corresponding to each MBSFN area; and then determining, by using the time and frequency resources of the received information, the corresponding MBSFN area; and then, in step In 603, the information received on the time and frequency resources corresponding to each MBSFN area can be processed according to the rule corresponding to each MBSFN area. It is easy to understand that for each piece of received information, the corresponding MBSFN area is determined according to the time and frequency resource of the received information, and then the information is processed according to the rule corresponding to the MBSFN area.
  • the information receiving method in the V2X service may include the following steps:
  • the V2X information received on the time and frequency resources corresponding to the MBSFN areas supporting the V2X services is processed according to rules corresponding to the respective supported MBSFN areas.
  • the corresponding rule is the processing rule of the V2X information, but is not limited thereto.
  • the rule is preset and can be formulated as needed, for example, a rule that can be processed for integrity protection.
  • the rule corresponds to the MBSFN area, for example, when the rule is the processing rule of integrity protection and verification, and the MBSFN area number is MBSFN area 1, the key corresponding to the MBSFN area 1 is used (usually Perform integrity verification for the public key).
  • the time and frequency resources corresponding to the MBSFN area of the transmitted and received information may be preset, for example:
  • the base station needs to send information to the MBSFN area 2 and the MBSFN area 3, respectively, and set the subframes occupied by the MBSFN area 2 and the MBSFN area 3 to be subframe 7 and subframe 8 in each radio frame, respectively, and then determine that the transmission needs to be performed.
  • the V2X information belongs to the MBSFN area 2, it is transmitted and received in accordance with the preset subframe 7, and the MBSFN area 3 is transmitted and received in the subframe 8. It is known to those skilled in the art that the time and frequency resources corresponding to the MBSFN area are well known to each other, and any technical manner that enables each base station to know the corresponding relationship is also applicable in this embodiment. .
  • the MBMS method when the information is transmitted and received in time and frequency resources corresponding to the MBSFN area, the MBMS method may be used, or other communication methods may be used, for example, by unicast mode or device-to-device (D2D). In other ways, as long as the information can be sent to the terminal device.
  • D2D device-to-device
  • the first base station, the second base station, and the terminal are given below. Implementation process between backups.
  • a first cell is a cell belonging to a first base station, and information is to be in a time corresponding to the MBSFN area in each second cell under each base station.
  • the second cell is a cell that belongs to the second base station, and may include:
  • Step 701 Receive information that is reported to the first base station by each terminal device under the jurisdiction of the first cell.
  • Step 702 the information is distributed to each second base station belonging to the second cell belonging to the same MBSFN area as the first cell, and the process proceeds to step 709;
  • Step 703 Receive information from the first cell that is sent by the first base station to the second base station, where the first cell is a cell that belongs to the first base station.
  • Step 704 Determine a second cell that belongs to the same MBSFN area as the first cell.
  • Step 705 Send, in a second cell of the second base station, information to the designated terminal device on a time and frequency resource corresponding to the MBSFN area.
  • Step 706 The terminal device in the second cell of the second base station receives the information sent by the second base station.
  • Step 707 Determine time and frequency resources corresponding to each MBSFN area according to the received system information of the second base station.
  • Step 708 Process information received on time and frequency resources corresponding to each MBSFN area according to a rule corresponding to each MBSFN area.
  • Step 709 Send information to the designated terminal device on the time and frequency resources corresponding to the MBSFN area in the first cell of the first base station and the second cell belonging to the first cell that belongs to the same MBSFN area as the first cell. ;
  • Step 710 The first cell in the first base station and the terminal device in the second cell receive the information sent by the first receiving base station.
  • Step 711 Determine, according to system information of the received first base station, time and frequency resources corresponding to the MBSFN area.
  • Step 712 Process the information received on the time and frequency resources corresponding to the MBSFN area according to a rule corresponding to the MBSFN area.
  • the “designated terminal device” may be a terminal device such as a terminal device supporting a V2X service or a terminal device supporting a certain type of V2X service (such as a road safety related V2X service), or may be a plurality of types.
  • the terminal device such as a terminal device that supports the V2X service or the M2M service, may also be a terminal device that can receive the service sent by the network side.
  • the following definitions and implementations of the "source cell”, “source base station”, “collaborative cell”, and “same MBSFN area” are implemented. Ways and so on.
  • the V2X service, the UE, and the V2X information will be described as an example.
  • one MBSFN area includes one first cell and at least one second cell.
  • these specific areas are called cells, and the concept of a cell is often referred to as serving a user terminal in this specific coverage area.
  • the first cell is a cell in which the UE is in the V2X service, and the V2X information is reported to the cell of the first base station.
  • the first cell in the embodiment is called a “source cell”, and the first cell is called a “source”. Base station”.
  • An MBSFN area has only one first cell, and one MBSFN area has only one corresponding time and frequency resource.
  • one MBSFN area can correspond to multiple time and frequency resources, but at the same time, the MBSFN area corresponds to The time and frequency resources are unique.
  • the second cells may be attributed to other base stations.
  • the second cell in the embodiment may be referred to as a “collaborative cell”. .
  • Source refers to the source of data generated.
  • the data generated by the source is the data sent by the MBSFN area, and the “collaborative” means assisting in sending the data generated by the source.
  • the data in the embodiment is also "V2X information”.
  • the base station for V2X information distribution belongs to each second base station to which each second cell of the MBSFN area in which the first cell is the data source cell belongs, and the first cell is the MBSFN of the data source cell.
  • the area means that the transmission data corresponding to the MBSFN area is generated by the first cell.
  • the V2X information is sent on the time and frequency resources corresponding to the MBSFN area in each second cell under each base station, specifically:
  • the V2X information will be in each of the second cells belonging to the MBSFN area in which the first cell is the data source cell, and each of the second base stations belonging to the second cell belonging to the MBSFN area in which the first cell is the data source cell And transmitting on the time and frequency resource corresponding to the MBSFN area in which the first cell is the data source cell.
  • the V2X information is sent on the time and frequency resources corresponding to the MBSFN area in the first cell and the second cell of the first base station, specifically:
  • the V2X information is sent to each UE in the MBMS manner on the same time and frequency resources on the base station and the adjacent base station, so that the UEs in the same MBSFN area can receive the same from the UE at the same time.
  • the purpose of the V2X service is to enable the UE in the relevant area to obtain the V2X information in time. For example, it is necessary to ensure that all UEs within 300 meters of the UE reporting the V2X information can receive the V2X information.
  • the UEs are in the same MBSFN area as the UE that reports the V2X information, and the V2X information reported by the UE is delivered as the data source of the MBSFN area.
  • the delivery range of the V2X information can be ensured. Since the processing of data is performed according to the MBSFN area, and the MBSFN area is composed of cells, this means that the same MBSFN is determined.
  • the constituent cells of the area are a key part of the implementation. Therefore, the following describes how the cell and each cell form an MBSFN area, so as to better understand the implementation of the technical solution provided by the embodiment of the present invention.
  • FIG. 8 is a schematic diagram of the structure of an MBSFN area
  • FIG. 9 is a schematic diagram of a structure of an MBSFN area in a high-speed scene
  • FIG. 10 is a schematic diagram of a relationship between a cell and an MBSFN area
  • FIG. 11 is a schematic diagram of a relationship between a cell and an MBSFN area in a highway scene, as shown in the figure:
  • one MBSFN area is composed of a plurality of adjacent cells.
  • the MBSFN area 1 is composed of Cell 1-Cell 7, and one data source cell exists in each MBSFN area.
  • the cell is responsible for generating data content that is sent by each cell in the MBSFN area in the MBSFN manner, and the data content is distributed to other cells in the MBSFN area (the cells in the same MBSFN area may belong to different eNBs), as shown in FIG.
  • Cell 1 can be selected as the data source cell of the MBSFN area.
  • the number of cells included in one MBSFN area can be set according to the actual environment. For example, in the highway environment, the MBSFN area can be set along the expressway.
  • the MBSFN area shown in Figure 9 is distributed along the expressway. Cell configuration, Cell 1 serves as the data source cell of the MBSFN area.
  • the numbered circles represent different MBSFN areas, and the number in the circle at the middle position of each cell is the number of the MBSFN area in which the cell is used as the data source cell, if multiple cells are in the cell.
  • the number in the circle at the middle position of each cell is the number of the MBSFN area in which the cell is used as the data source cell, if multiple cells are in the cell.
  • each MBSFN area in the system when each MBSFN area in the system is composed of one cell and six cells around it, and each cell has one MBSFN area centered on itself, each cell will be composed of seven. MBSFN area coverage (such as Cell 1-Cell 7, other cells are not edged, so they are not covered by 7 MBSFN areas).
  • MBSFN area coverage such as Cell 1-Cell 7, other cells are not edged, so they are not covered by 7 MBSFN areas.
  • each MBSFN area when in the highway scene, each MBSFN area is composed of one cell and two surrounding cells, and each cell has one MBSFN area centered on itself, each cell will Covered by three MBSFN areas (such as Cell 1, Cell 2, Cell 3, and Cell 5, other Cell4 and Cell6 are not edged, so they are not covered by three MBSFN areas).
  • step 402 the transmission of information between the first base station and the second base station will be involved, that is, the information is distributed to the second base stations to which the second cells belonging to the same MBSFN area of the first cell belong.
  • the implementation of information distribution in this case will first be described below.
  • the implementation is performed from the first base station and the second base station side respectively, but this does not mean that the two must be implemented together.
  • the problems of the first base station and the second base station side are also respectively solved, but when the two are used in combination, a better technical effect is obtained.
  • the schemes of the first base station and the second base station, the first base station and the second base station are only used to better illustrate the solution provided in the embodiment of the present invention, and do not mean that one base station can only implement one of the solutions.
  • the user data transmission function between the eNBs can be provided on the X2 interface user plane.
  • the transport network layer of the X2 User Plane (X2-UP) is based on the Internet Protocol (IP), and the User Datagram Protocol (UDP)/IP protocol uses the General Packet Radio Service User Plane Tunneling Protocol. (General Packet Radio Service Tunnelling Protocol for User Plane, GTP-U) to transmit user plane data between eNBs.
  • the GTP-U protocol uses a tunneling mechanism to provide services for carrying user data packets.
  • the Tunnel End Point Identifier (TEID) in the GPRS Tunneling Protocol (GTP) packet header indicates the tunnel-protocol data unit (Tunnelling Protocol).
  • T-PDU the tunnel where the Data Unit
  • the X2 user plane transmission between the eNBs is only related to the handover, and the UE-related signaling is used to establish a radio access bearer (RAB) level connection.
  • RAB radio access bearer
  • the first base station side that is, the base station side that receives the information reported by the terminal device, may include the following manners:
  • the information is distributed to the second base stations to which the second cells belonging to the same MBSFN area belong to the first cell through the X2 interface, and the information is to be in the MBSFN area in each second cell under each base station. Transmitting the corresponding time and frequency resources, that is, distributing the information to the second base stations to which the second cells of the MBSFN area with the first cell as the data source cell belong;
  • the second base station side that is, the base station side that receives the information forwarded by the neighboring base station, may include the following manners:
  • the second base station transmits information at a time and frequency resource corresponding to the MBSFN area.
  • the enhanced eMBMS scheme proposed to reduce the V2X delay when the V2X service and the UE are used as an example since other cells except the data source cell in the MBSFN area are only responsible for cooperatively transmitting V2X data, it is not necessary to know the corresponding data.
  • the UE information does not need to know the service type of the data, etc., so a new X2 user plane data channel can be created for the eMBMS data source cell to distribute eMBMS data to other cells in the corresponding MBSFN area.
  • the X2 user plane data channel when the X2 user plane data channel is created, it can be known from the above reasons that it is not required to be created in connection with the handover according to the existing protocol, nor is it required to be created only when the V2X information is transmitted, but may be implemented according to the implementation requirements. Created at the appropriate time.
  • the data channel can be created in advance. When V2X information is generated and V2X information needs to be transmitted, it can be transmitted immediately through the data channel. When the amount of V2X information changes or there is no V2X information transmission, it can be updated. And release the data channel to perform maintenance such as channel maintenance. Of course, you can also create the data channel as needed when you need to transfer V2X information.
  • the implementation of the data channel is mainly: creating, updating, and releasing the data channel, and in the process, the first base station that sends the data and the second base station that receives the data may be as follows:
  • the request for establishing the data channel of the X2 interface is initiated to the second base station, and the request for the second base station includes one or a combination of the following: the resource requirement information of the data channel to be established with the second base station, and the MBSFN area. Identification information, MBSFN area data source cell identification information;
  • the second base station After the second base station establishes an X2 interface data channel that meets the requirement, information is sent from the data channel to the second base station.
  • an X2 interface data channel establishment request initiated by the first base station where the request includes one or a combination of the following: resource requirement information for the data channel, MBSFN area identification information, and MBSFN area data source cell identification information;
  • the information sent by the first base station is received from the data channel.
  • the second base station that establishes the data channel After determining the resource requirements of the data channel or other requirements (such as the MBSFN area identifier, the MBSFN area data source cell identifier), the second base station that establishes the data channel initiates the update request of the data channel according to the changed resource requirement;
  • the information is sent from the data channel to the second base station.
  • the information sent by the first base station is received from the data channel.
  • the second base station that establishes the data channel initiates a request to release the data channel
  • the data channel is released and the information transmitted by the first base station is stopped from the data channel.
  • the update and release of the data channel may be initiated by the first base station or by the second base station.
  • the second base station may Initiate an update or release request for its own needs.
  • the implementation can also be as follows:
  • the source eNB and the target eNB are used instead of the first base station and the second base station.
  • the first base station is the source eNB
  • the second base station is the target eNB.
  • the source eNB performs an MBSFN mode transmission interface on the other cells in the same MBSFN area (referred to as the coordinated cells corresponding to the MBSFN area for convenience of description) according to the obtained resource information required for the user plane data to be exchanged with the target eNB.
  • the resource information is sent to the eNB (target eNB) to which the coordinated cell in the same MBSFN area belongs.
  • the resource information required for the source eNB to exchange user plane data with the target eNB may be determined by the source eNB according to the number of UEs in the data source cell corresponding to each MBSFN area, load information, or the like, or may be indicated by a high-level node (eg, MME, MCE, etc.) can also be configured by Operation and Maintenance (O&M).
  • O&M Operation and Maintenance
  • the other eNB may have multiple data source cells corresponding to different MBSFN areas, which may be different MBSFNs.
  • a data source cell of an area creates a channel independently, and a channel corresponding to a data source cell of a plurality of different MBSFN areas can also be created at the same time.
  • the embodiment A1 will explain the establishment of the MBSFN data channel
  • the embodiment A2 will explain the configuration update process of the data channel
  • the embodiment A3 will perform the deactivation/release process of the data channel. Description.
  • Embodiment A1 Establishing an MBSFN Data Channel
  • FIG. 12 is a schematic diagram of an implementation process of establishing a signaling interaction process for an X2 interface MBSFN data transmission channel.
  • the basic signaling interaction process may include:
  • Step 1201 The eNB1 sends an MBSFN data channel establishment request to the eNB2.
  • Step 1202 The eNB2 sends an MBSFN data channel setup response to the eNB1.
  • a data channel may be used to establish a message by establishing only one data channel, or a data channel may be used to establish a message and simultaneously establish multiple data channels.
  • a data channel setup message establishes only one data channel and one data channel setup message simultaneously establishes multiple data channels will be respectively described.
  • a data channel setup message only establishes a data channel
  • the eNB1 includes two cells, cell 1 and cell 2, and the MBSFN areas, where cell 1 and cell 2 are used as data source cells, are respectively MBSFN area 2 and MBSFN area 3.
  • the subframes occupied by MBSFN area 2 and MBSFN area 3 are respectively Subframe 7 and subframe 8 in each radio frame;
  • eNB2 includes one cell cell3, cell 1 of eNB1 and cell 3 of eNB2 are geographically adjacent cells, and cell 3 of eNB2 belongs to MBSFN area 2 with cell 1 of eNB1 as the data source cell, and cell 3 of eNB2 needs to be in
  • the subframe corresponding to the MBSFN area 2 (subframe 7 in each radio frame) transmits the same data on the subframe corresponding to the MBSFN area 2 in the cell 1 of the eNB1, and the data transmitted on the subframe corresponding to the MBSFN area 2 It is forwarded by eNB1 to eNB2.
  • the establishment process of the X2 interface data transmission channel initiated by the eNB1 as the Source eNB for the MBSFN area 2 in which the cell 1 is the data source cell is as follows:
  • the eNB1 determines the level of bandwidth required for the interactive user plane data according to the number of UEs participating in the V2X and the load information in the data source cell 1 of the corresponding MBSFN area 2, and requests to establish an X2 user plane data channel accordingly.
  • the eNB2 determines that the channel establishment request sent by the eNB1 is satisfied, the eNB2 creates a channel corresponding to the bandwidth according to the bandwidth included in the request message, and sends a channel establishment response to the eNB1.
  • the content of the request message sent by the Source eNB to the Target eNB may include:
  • Source eNB ID ie, the ID of eNB1
  • the MBSFN area identifier (that is, the identifier corresponding to the MBSFN area 2);
  • MBSFN area data source cell identifier ie, cell 1 identifier
  • a list of cells requesting MBSFN coordinated transmission (ie, cell 3);
  • the Target eNB response message content may include:
  • Source eNB ID ie, the ID of eNB1
  • Target eNB ID ie, the ID of eNB2
  • cell 3 a cell list (ie, cell 3) that allows MBSFN cooperative transmission
  • the eNB1 may forward the road safety data reported by the UE collected in the MBSFN area 2 data source cell (ie, cell1) to the eNB2, and the cell3 of the eNB2 sets the time-frequency resource on the set time-frequency resource.
  • the rules are sent. It should be noted that, before the eNB1 forwards the road safety data reported by the UE to the eNB2, the eNB1 may perform some processing operations on the data packet, such as performing integrity protection operations on the data reported by the UE, and then encapsulating the data in the synchronization data.
  • the corresponding data packet received by the UE under the cell 3 of the eNB2 can ensure the validity of the received data through integrity verification, and can enable the cell1 under the eNB1 and the cell3 under the eNB2 to be at the same time.
  • the same data is transmitted on the frequency resource in MBSFN.
  • the MBSFN data channel establishment failure message is sent to the source eNB, and the content may include:
  • a data channel establishes a message and simultaneously establishes multiple data channels.
  • the eNB1 includes two cells, cell 1 and cell 2, and the MBSFN areas, where cell 1 and cell 2 are used as data source cells, are respectively MBSFN area 2 and MBSFN area 3.
  • the subframes occupied by MBSFN area 2 and MBSFN area 3 are respectively Subframe 7 and subframe 8 in each radio frame;
  • eNB2 includes one cell cell3, and cell 1 and cell 2 of eNB1 and cell 3 of eNB2 are geographically adjacent cells, and cell 3 of eNB2 belongs to both MBSFN area 2 in which cell 1 of eNB1 is the data source cell.
  • the cell 2 of the eNB1 is the MBSFN area 3 of the data source cell; the cell 3 of the eNB2 needs to be transmitted in the subframe corresponding to the MBSFN area 2 (subframe 7 in each radio frame) corresponding to the MBSFN area 2 in the cell 1 of the eNB1.
  • the identical data on the subframes also needs to transmit the same data on the subframe corresponding to the MBSFN area 3 in the cell 2 of the eNB1 on the subframe corresponding to the MBSFN area 3 (subframe 8 in each radio frame). ; MBSFN area 2 and The data transmitted on the subframe corresponding to the MBSFN area 3 is forwarded by the eNB1 to the eNB2.
  • the X2 interface data transmission channel establishment for the MBSFN area 2 where the cell 1 is the data source cell and the X2 interface data transmission channel for the MBSFN area 3 of the data source cell initiated by the eNB1 as the source eNB are as follows:
  • the eNB1 determines the level of the bandwidth required for the respective interactive user plane data according to the number of UEs participating in the V2X and the load information in the data source cell 1 of the MBSFN area 2 and the data source cell 2 of the MBSFN area 3, respectively. And establish their own data channel for the X2 user plane.
  • the eNB2 determines that the channel establishment request or part of the request sent by the eNB1 can be satisfied, the channel corresponding to the bandwidth is created according to the bandwidth included in the request message, and the channel establishment response is sent to the eNB1.
  • the channel establishment response is sent to the eNB1.
  • eNB2 can satisfy the request to establish two channels at the same time.
  • the content of the request message sent by the Source eNB to the Target eNB may include:
  • Source eNB ID ie, the ID of eNB1
  • the data transmission channel establishment information of the data source cell 1 of the MBSFN area 2 may include:
  • MBSFN area identifier (MBSFN area 2 identifier);
  • Data source cell identifier ie, cell 1 identifier
  • a list of cells requesting MBSFN coordinated transmission (ie, cell 3);
  • the data transmission channel establishment information of the data source cell 2 of the MBSFN area 3 may include:
  • MBSFN area identifier (MBSFN area 3 identifier);
  • Data source cell identifier ie, cell 2 identifier
  • a list of cells requesting MBSFN coordinated transmission (ie, cell 3);
  • the Target eNB response message content may include:
  • Source eNB ID ie, the ID of eNB1
  • Target eNB ID ie, the ID of eNB2
  • the data transmission channel response information of the data source cell 1 of the MBSFN area 2 may include:
  • cell 3 a cell list (ie, cell 3) that allows MBSFN cooperative transmission
  • the data transmission channel response information of the data source cell 2 of the MBSFN area 3 may include:
  • cell 3 a cell list (ie, cell 3) that allows MBSFN cooperative transmission
  • the eNB1 may forward the road safety data reported by the UE collected in the MBSFN area 2 data source cell (ie, cell1) and the data source cell 2 of the MBSFN area 3 to the road security data respectively.
  • the eNB2 transmits the data generated by the MBSFN area 2 data source cell (ie, cell 1) and the data source cell 2 of the MBSFN area 3 by the cell 3 of the eNB 2 at the set time frequency.
  • the eNB1 may perform some processing operations on the data packet, such as performing integrity protection operations on the data reported by the UE, and then encapsulating the data in the synchronization data.
  • the UE receives the corresponding data packet under the cell3 of the eNB2, and can ensure the validity of the received data through integrity verification, and can enable the cell1 and the cell2 under the eNB1 and the cell3 under the eNB2 respectively.
  • the same data is transmitted in MBSFN on the same time-frequency resource.
  • the MBSFN data channel establishment failure message is sent to the source eNB, and the content may include:
  • Embodiment A2 Updating Data Channel Configuration
  • FIG. 13 is a schematic diagram of an implementation process of an X2 interface MBSFN data transmission channel configuration update process.
  • the basic signaling interaction process may include:
  • Step 1301 eNB1 sends an MBSFN data channel update request to eNB2.
  • Step 1302 The eNB2 sends an MBSFN data channel update confirmation to the eNB1.
  • a data channel update message may be used to update only one data channel, or a data channel update message may be used to simultaneously update multiple data channel configuration information.
  • a data channel update message updates only one data channel and one data channel update message simultaneously updates multiple data channels.
  • a data channel update message updates only one data channel.
  • the eNB1 includes two cells, cell 1 and cell 2, and the MBSFN areas, where cell 1 and cell 2 are used as data source cells, are respectively MBSFN area 2 and MBSFN area 3.
  • the subframes occupied by MBSFN area 2 and MBSFN area 3 are respectively Subframe 7 and subframe 8 in each radio frame;
  • eNB2 includes one cell cell3, and cell 1 of eNB1 and cell 3 of eNB2 are geographically adjacent cells.
  • Cell 3 of eNB2 belongs to MBSFN area 2 in which cell 1 of eNB1 is the data source cell, and cell 3 of eNB2 needs to transmit cell with eNB1 in the subframe corresponding to MBSFN area 2 (subframe 7 in each radio frame).
  • the data in the subframe corresponding to the MBSFN area 2 in 1 is identical, and the data transmitted in the subframe corresponding to the MBSFN area 2 is forwarded by the eNB1 to the eNB 2.
  • An MBSFN data transmission channel (channel identifier: 00000010) has been created between the eNB1 and the eNB2, and is used by the eNB1 to forward data generated by the data source cell (cell 1 of the eNB1) of the MBSFN area 2 to the eNB2, and the cell 3 of the eNB2 adopts the MBSFN. Way to send.
  • eNB1 needs to initiate a data channel configuration update procedure to eNB2.
  • the eNB2 determines that the channel configuration update request transmitted by the eNB1 is satisfied, the eNB2 updates the channel configuration according to the update information included in the request message, and transmits a channel update confirmation to the eNB1.
  • the content of the update request message sent by the Source eNB (eNB1) to the Target eNB (eNB2) may include:
  • MBSFN cooperatively transmitted cell list (cell3, cell4)
  • Source eNB determines the required bandwidth information for user plane data transmission (updatable, optional);
  • the Target eNB response message content may include:
  • cell3 a cell list (cell3, cell4) that allows MBSFN cooperative transmission
  • the MBSFN data channel update failure message is sent to the source eNB, and the content may include:
  • One data channel update message updates multiple data channels simultaneously
  • the eNB1 includes two cells, cell 1 and cell 2, and the MBSFN areas, where cell 1 and cell 2 are used as data source cells, are respectively MBSFN area 2 and MBSFN area 3.
  • the subframes occupied by MBSFN area 2 and MBSFN area 3 are respectively Subframe 7 and subframe 8 in each radio frame;
  • eNB2 includes one cell cell3, and cell 1 and cell 2 of eNB1 and cell 3 of eNB2 are geographically adjacent cells, and cell 3 of eNB2 belongs to both MBSFN area 2 in which cell 1 of eNB1 is the data source cell.
  • the cell 2 of the eNB1 is the MBSFN area 3 of the data source cell; the cell 3 of the eNB2 needs to be transmitted in the subframe corresponding to the MBSFN area 2 (subframe 7 in each radio frame) corresponding to the MBSFN area 2 in the cell 1 of the eNB1.
  • the identical data on the subframes also needs to transmit the same data on the subframe corresponding to the MBSFN area 3 in the cell 2 of the eNB1 on the subframe corresponding to the MBSFN area 3 (subframe 8 in each radio frame).
  • the data transmitted on the subframe corresponding to the MBSFN area 2 and the MBSFN area 3 is forwarded by the eNB1 to the eNB2.
  • Two MBSFN data transmission channels (channel identifiers: 00000010, 00000011) have been created between eNB1 and eNB2, respectively, for eNB1 to use the data source cell of MBSFN area 2 (cell 1 of eNB1) and the data source cell of MBSFN area 3, respectively.
  • eNB1 The generated data of the cell 2 is forwarded to the eNB2, and the cell 3 under the eNB2 is transmitted by using the MBSFN method.
  • eNB1 determines that the bandwidth corresponding to both channels needs to be increased, and eNB1 needs to update the data channel to eNB2.
  • the eNB2 determines that the channel update request transmitted by the eNB1 is satisfied, the eNB2 updates the channel configuration according to the update information included in the request message, and transmits a channel update confirmation to the eNB1.
  • the content of the request message sent by the Source eNB to the Target eNB may include:
  • User plane data channel 1 identifier (00000010) requesting update
  • MBSFN cooperatively transmitted cell list (updable, optional);
  • the required bandwidth information of the user plane data transmission determined by the Source eNB (for example, the bandwidth recalculated according to the number of UEs and the current load condition).
  • User plane data channel 2 identifier (00000011) requesting update
  • MBSFN cooperatively transmitted cell list (updable, optional);
  • the required bandwidth information of the user plane data transmission determined by the Source eNB (for example, the bandwidth recalculated according to the number of UEs and the current load condition).
  • the Target eNB update confirmation message includes:
  • User plane data channel 1 identifier (00000010) requesting update
  • the MBSFN data channel update failure message is sent to the source eNB, and the content includes:
  • Embodiment A3 Deactivating/Deactivating a Data Channel
  • FIG. 14 shows the X2 interface MBSFN data transmission channel de-excitation
  • Step 1401 eNB1 sends an MBSFN data channel deactivation/release message to eNB2.
  • the data channel deactivation or release message can deactivate or release multiple channels
  • the content can be as follows:
  • FIG. 15 is a schematic diagram of an EPS bearer structure.
  • an application layer service is finally embodied in user plane data, and is transmitted using an Evolved Packet System (EPS) bearer, and the EPS bearer is carried by a radio bearer (Data Radio Bearer, RB), S1 bearer, S5/S8 bearer.
  • EPS bearer Data Radio Bearer, RB
  • S1 bearer S5/S8 bearer
  • the corresponding EPS bearers should also be dynamically established, modified and released.
  • the air interface part of the EPS bearer and the data radio bearer (DRB) are managed by the access network node ( For example, the eNB is completed by a Radio Resource Control (RRC) connection reconfiguration process.
  • RRC Radio Resource Control
  • the DRB and the EPS bearer are in one-to-one correspondence.
  • the EPS bearer is controlled by an entity such as a Mobility Management Entity (MME).
  • MME Mobility Management Entity
  • the access network node RRC manages the DRB from the MME to the access network node. S1AP control message.
  • the LTE system allows (partial) admission to the DRB during handover, and the target cell may only accept part of the DRB of the UE.
  • the existing bearer management needs to be modified.
  • the V2X service and the UE are used as an example, and the network side needs to be able to identify the V2X service initiated by the UE, thereby establishing a corresponding bearer for the V2X service reported by the UE. And configure other processing.
  • Figure 16 is a schematic flowchart of the implementation of the information reporting method.
  • the terminal device may include:
  • Step 1601 Send indication information to the access network node, where the indication information is used to indicate that the information reported by the terminal device is information to be sent on time and frequency resources corresponding to the MBSFN area;
  • Step 1602 Receive a notification of the access network node, where the notification carries configuration information of the radio bearer used for reporting the information;
  • Step 1603 After the terminal device collects the information, the information is reported on the radio bearer according to the configuration information.
  • Figure 17 is a schematic diagram of the implementation process of the bearer establishment method. As shown in the figure, for the indication of the terminal device, correspondingly, the network side device can perform the following steps:
  • Step 1701 Receive, by the access network node, request information for establishing a service bearer, where the service bearer is used to transmit information that is to be reported by the terminal device, where the information is information that is to be sent on a time and frequency resource corresponding to the MBSFN area;
  • Step 1702 Establish a service bearer, where the service bearer includes a radio bearer used by the terminal device to report information to the access network node.
  • Step 1703 Notify the configuration information of the service bearer established by the access network node.
  • the network measurement device may be specifically implemented by the MME.
  • the network side device that can implement the allocation of bearer resources for information transmission between the base stations can implement the solution.
  • FIG. 18 is a schematic flowchart of an implementation method of an information receiving method of an access network node.
  • the access network node for example, on the first base station side, that is, the base station side that reports information from the receiving terminal device, establishes a radio resource bearer for transmitting the reporting information. On, you can perform the following steps:
  • Step 1801 Receive indication information sent by the terminal device, where the indication information is used to indicate that the information reported by the terminal device is information that is to be sent on a time and frequency resource corresponding to the MBSFN area;
  • Step 1802 The network side device is requested to establish a service bearer for the reported information by the terminal device.
  • Step 1803 Receive configuration information of a service bearer established by the network side device, and configure, according to the configuration information, the radio bearer to be reported by the terminal device.
  • Step 1804 The terminal device is notified to report the information on the configured radio bearer, and the information reported by the terminal device is received on the configured radio bearer.
  • the implementations are respectively performed from the terminal device, the network side device, and the access network node (the first base station), but this does not mean that they must be implemented together, in fact, when they are implemented separately, They also solve the problems of terminal devices, network side devices, and access network nodes, but they will get better technical effects when they are combined.
  • the V2X service, the UE, and the V2X information are implemented as an example, that is, information that needs to be sent on the time and frequency resources corresponding to the MBSFN area in each cell belonging to the same MBSFN area is V2X information.
  • the UE sends the V2X related indication information to the network side node, and the network side node (including the access network node and the network side device) establishes a bearer for transmitting the V2X service and configures the corresponding resource according to the indication sent by the UE, and may be the The data on the bearer sets a special action.
  • the specific process can be as follows:
  • the UE sends V2X related indication information to the network side node in the implementation:
  • the network side node includes an existing node such as an eNB, a relay, an MME, and a Home eNodeB (HeNB), and also includes an access network node that is subsequently introduced.
  • the V2X service related indication information may be directly carried in the RRC signaling (such as the RRC connection setup request message, the RRC connection setup complete message, and the uplink information transmission message), or may be in the non-
  • the access layer (Non Access Stratum, NAS) signaling carries V2X service related indication information, and the NAS signaling may generally include the following signaling: such as an Attach Request, a service request, and an extended service request ( Extended service request), bearer resource allocation request, bearer resource modification request, and the like.
  • the V2X service-related indication information may be a service quality (QoS) parameter information corresponding to the V2X service, and may be a service information indicating whether the current service is V2X-related service information (specifically, whether the V2V, the V2I, the V2P, the V2C service, etc. are indicated. ), can be information indicating specific business types (such as road safety business, traffic efficiency)
  • the rate type service, the traffic information type service, and the like may be information indicating a service processing manner (such as direct forwarding of the access network, direct forwarding of the access network MBMS, etc.), and may also indicate that the UE is V2X type terminal information.
  • the following are some examples of carrying V2X related indication information in different messages.
  • the following RRC connection request, RRC connection completion, and NAS message are used as examples. Because these types of signaling are typical and commonly used, it is taken as an example. However, in theory, other signaling messages are also possible. In fact, how to transmit information through existing signaling messages is also easily implemented by those skilled in the art, and the RRC connection request and the RRC connection are completed.
  • the NAS message is only used to teach the person skilled in the art how to implement the invention, but it does not mean that only these kinds of messages can be used.
  • the indication information can be carried in reference to the specific situation of the corresponding signaling in combination with the practice.
  • V2X service related identification information such as: V2X service identifier, road safety service identifier, vehicle road safety service identifier, V2X local service identifier, local forwarding service identifier, local MBSFN service identifier, QoS parameter identifier in the NAS message
  • the network side node establishes a bearer for transmitting the V2X service and configures a corresponding resource for the UE according to the V2X service related indication information sent by the UE, and can set a corresponding special operation for the service for the data on the bearer.
  • the network side node When the network side node is an access network node, such as an eNB, a HeNB, and a relay, the network side node allocates a corresponding resource, such as an eNB UE S1AP ID, to the UE according to the V2X service related indication information sent by the UE (the identifier is that the eNB is on the S1 interface. Assigned to the eNB end of each UE connected to the control plane on S1), Radio Network Temporary Identity (RNTI), and the like.
  • a corresponding resource such as an eNB UE S1AP ID
  • the network side node When the network side node is a network side device such as a core network node, such as an MME, the network side node performs one of the following steps according to the V2X service related indication information sent by the UE:
  • the UE Create a corresponding bearer for the UE to transmit the V2X service (determine the service bearer identification information, the special identifier, and the like), and allocate the related resource, such as the MME UE S1AP ID, to the UE.
  • the identifier is allocated by the MME to each UE on S1 on S1.
  • Evolved Radio Access Bearer Evolved Radio Access Bearer (E-RAB ID), GPRS Tunneling Protocol Tunnel End Point Identifier (GTP-TEID), etc.
  • MME Through S1 interface signaling eg, INITIAL CONTEXT SETUP REQUEST, UE CONTEXT MODIFICATION REQUEST, E-RAB SETUP REQUEST, E-RAB modification request (E) -RAB MODIFY REQUEST
  • the UE of the access network node corresponding to the bearer information including the special identifier, such as the local broadcast indication, the local MBSFN forwarding indication, the V2X bearer indication, etc.
  • the allocated related resource information such as eNB
  • the information indication (eg, local broadcast indication, local MBSFN forwarding indication, V2X bearer indication) of the special radio bearer will be created to the eNB.
  • the access network node configures the corresponding radio bearer resource and other related resources for the UE according to the indication of the MME or according to the setting rule, and may further perform specific processing on the data packet received on the bearer, for example, reporting the corresponding bearer on the UE.
  • the data packet is broadcasted to other UEs under the coverage of the access network, and the data packet on the corresponding bearer is forwarded to the neighboring eNB (such as the eNB in which the second cell exists), and the data packets are broadcasted.
  • Other processes such as performing integrity protection, adding a packet header for synchronization, etc., may be performed before being sent to the UE under the coverage of the access network node and being forwarded to the neighboring eNB.
  • the network side node notifies the UE of bearer configuration information created by the UE and configuration information of other resources.
  • the access network node sends the resource configuration information, including the radio bearer configuration, to the UE through RRC signaling, such as RRC Connection Reconfiguration, RRC Connection Setup, DLInformationTransfer, or newly defined RRC signaling.
  • Information such as corresponding configuration parameters carrying the protocol layer entities
  • core network nodes such as MME
  • NAS signaling eg, Attach accept, Authentication request, Security mode command
  • Downlink generic NAS transport Downlink NAS transport
  • Activate dedicated EPS bearer context request Activate default EPS bearer context request
  • NAS signaling sent by the MME to the UE needs to send a signaling to the eNB via the S1 interface, and then sent to the UE
  • the network side node sends the related information of the V2X service through the system broadcast, and the UE receives the system message, and initiates the V2X related service access in the cell supporting the V2X service, which may be:
  • the system broadcast can add a new IE or define a new code point implementation in the existing Master Information Block (MIB) or System Information Block (SIB), or in the newly defined SIB message. Instructions.
  • MIB Master Information Block
  • SIB System Information Block
  • V2X service related information including: supported V2X service type information, supported V2X service mode information, and V2X service (MBSFN) area information.
  • the interaction between the UE, the core network node MME, and the access network node base station will be described below by way of example.
  • the UE sends the V2X indication information to the MME, and the MME establishes a special bearer for transmitting the V2X information (including carrying the special indication identifier (such as the local broadcast indication, the local MBSFN forwarding indication, the V2X bearer indication, and the no-layer bearer (such as the S1 bearer, S5). /S8 bearer, external bearer), etc., special processing operations (such as not creating other bearers above the radio bearer), etc., and indicating the special bearer information to the eNB, and the eNB creates a corresponding radio bearer for the special bearer.
  • the eNB can perform special processing on the data on the special bearer, and the eNB sends the configuration information of the related bearer to the UE.
  • the UE carries the V2X indication information in the Attach Request message.
  • the MME After receiving the indication of the UE, the MME establishes a special bearer for transmitting the V2X service for the UE, and carries the bearer configuration information and the bearer characteristic identifier-local broadcast indication in the INITIAL CONTEXT SETUP REQUEST message sent to the eNB;
  • the eNB After receiving the message sent by the MME, the eNB configures the corresponding radio bearer for the UE, and sends the configuration information to the UE by using an RRC connection reconfiguration message; after that, the eNB receives the data packet from the radio bearer, that is, The V2X information is broadcasted to the UE that sets the cell in the eNB.
  • the cell may be set to be the cell in the eNB, the cell in which the UE reporting the data packet, and the cell satisfying other agreed rules (eg, according to the geographical location and signal status of the UE, the cells in which the reported data packet should be located are determined. broadcast).
  • the UE carries the local MBSFN forwarding indication information in the Bearer resource allocation request message.
  • the MME After receiving the indication from the UE, the MME establishes a special bearer for transmitting the V2X service for the UE, and carries the bearer configuration information and the bearer characteristic identifier-local MBSFN forwarding indication in the E-RAB SETUP REQUEST message sent to the eNB.
  • the eNB After receiving the message sent by the MME, the eNB configures the corresponding radio bearer for the UE, and sends the configuration information to the UE by using an RRC connection reconfiguration message; after that, the eNB receives the data packet from the radio bearer, that is, The V2X information is distributed to the eNBs that meet the requirements (such as the eNB in which the second cell exists), and is transmitted by the eNB that meets the requirements in the eligible cell.
  • the UE carries the V2X indication information in the Service Request message.
  • the MME After receiving the indication from the UE, the MME establishes a special bearer for transmitting the V2X service for the UE, and carries the bearer configuration information and the bearer characteristic identifier-V2X bearer indication in the INITIAL CONTEXT SETUP REQUEST message sent to the eNB.
  • the eNB After receiving the message sent by the MME, the eNB configures the corresponding radio bearer for the UE, and sends the configuration information to the UE through the RRC connection reconfiguration message; after that, the eNB receives the data packet received from the radio bearer through the broadcast mode. Sending to the UE in the eNB to set the cell, and forwarding the data packet received from the radio bearer to the surrounding An eNB that satisfies the requirements (such as an eNB that has a second cell).
  • the UE sends the V2X indication information to the MME, and the MME determines to create a special radio bearer for the UE (does not create another bearer above the radio bearer), and indicates the information of the special radio bearer to the eNB, and the eNB creates a corresponding radio for the special bearer.
  • the bearer can perform special processing on the data on the special bearer, and the eNB sends the configuration information of the related bearer to the UE.
  • the UE carries the V2X service indication in the Attach Request message.
  • the MME determines to create a special radio bearer for the UE, and carries an indication of the special radio bearer-local broadcast indication in the INITIAL CONTEXT SETUP REQUEST message sent to the eNB.
  • the eNB After receiving the message sent by the MME, the eNB configures the corresponding radio bearer for the UE, and sends the configuration information to the UE through the RRC connection reconfiguration message; after that, the eNB receives the data packet received from the radio bearer through the broadcast mode.
  • the cell may be set to be the cell in the eNB, the cell in which the UE reporting the data packet, and the cell satisfying other agreed rules (eg, according to the geographical location and signal status of the UE, the cells in which the reported data packet should be located are determined. broadcast).
  • the UE carries the local MBSFN forwarding service indication in the Bearer resource allocation request message.
  • the MME determines to create a special radio bearer for the UE, and carries an indication for creating a special radio bearer-local MBSFN forwarding indication in the E-RAB SETUP REQUEST message sent to the eNB.
  • the eNB After receiving the message sent by the MME, the eNB configures the corresponding radio bearer for the UE, and sends the configuration information to the UE by using an RRC connection reconfiguration message; after that, the eNB forwards the data packet received on the radio bearer to the surrounding area.
  • the eNB that satisfies the requirement (such as the eNB in which the second cell exists) is sent by the eNB that meets the requirements in the eligible cell.
  • the UE carries the V2X service indication in the Service Request message.
  • the MME determines to create a special radio bearer for the UE, and carries an indication of the special radio bearer-V2X bearer indication in the INITIAL CONTEXT SETUP REQUEST message sent to the eNB.
  • the eNB After receiving the message sent by the MME, the eNB configures the corresponding radio bearer for the UE, and sends the configuration information to the UE through the RRC connection reconfiguration message; after that, the eNB receives the data packet received from the radio bearer through the broadcast mode.
  • the UE that is sent to the eNB to set the cell, and forwards the data packet received from the radio bearer to the eNB that satisfies the requirement.
  • the UE initiates a normal bearer setup process, and the message carries the UE identifier or the QoS parameter.
  • the MME determines to create a special bearer for the UE by using the UE identifier or the QoS parameter, and indicates the information of the special bearer to the eNB, where the eNB is the special bearer.
  • the eNB can perform special processing on the data on the special bearer, and the eNB sends the configuration information of the related bearer to the UE.
  • the UE carries the UE identifier in the Attach Request message.
  • the MME receives the subscription information of the UE to the HSS through the UE identifier in the Attach information, and determines that the UE establishes a special bearer for transmitting the V2X service by using the obtained subscription information, and carries the bearer configuration information in the INITIAL CONTEXT SETUP REQUEST message sent to the eNB. And an indication of the bearer characteristics - a local broadcast indication;
  • the eNB After receiving the message sent by the MME, the eNB configures the corresponding radio bearer for the UE, and sends the configuration information to the UE through the RRC connection reconfiguration message; after that, the eNB receives the data packet received from the radio bearer through the broadcast mode.
  • the cell may be set to be the cell in the eNB, the cell in which the UE reporting the data packet, and the cell satisfying other agreed rules (eg, according to the geographical location and signal status of the UE, the cells in which the reported data packet should be located are determined. broadcast).
  • the UE carries the QoS parameter information in the Bearer resource allocation request message.
  • the MME determines to establish a special bearer for transmitting the V2X service for the UE by using the QoS parameter information carried in the Bearer resource allocation request, and carries the bearer configuration information and the bearer characteristic identifier in the E-RAB SETUP REQUEST message sent to the eNB-local MBSFN forwarding indication.
  • the eNB After receiving the message sent by the MME, the eNB configures the corresponding radio bearer for the UE, and sends the configuration information to the UE by using an RRC connection reconfiguration message; after that, the eNB forwards the data packet received on the radio bearer to the surrounding area.
  • the eNB that meets the requirements.
  • the UE initiates a normal bearer setup process, and the message carries the identifier of the UE or the Qos parameter.
  • the MME determines to create a special radio bearer for the UE by using the identifier of the UE or the QoS parameter, and indicates the information of the special radio bearer to the eNB.
  • a specific radio bearer is created for the special bearer, and the eNB may perform special processing on the data on the special bearer, and the eNB sends the configuration information of the related bearer to the UE.
  • the UE carries the V2X UE identification information in the Attach Request message.
  • the MME receives the subscription information of the V2X UE to the HSS through the UE identifier in the Attach information, determines that the special radio bearer is created for the UE by using the obtained subscription information, and then carries the special wireless in the INITIAL CONTEXT SETUP REQUEST message sent to the eNB. The indication of the bearer.
  • the eNB After receiving the message sent by the MME, the eNB configures the corresponding radio bearer for the UE, and sends the bearer configuration information to the UE through the RRC connection reconfiguration message; according to the agreement, the eNB needs to receive the data packet received from the radio bearer. Local broadcast.
  • the UE carries the QoS parameter information in the Bearer resource allocation request message.
  • the MME determines to create a special radio bearer for the UE by using the QoS parameter information carried in the Bearer resource allocation request, and then carries an indication for creating a special radio bearer in the E-RAB SETUP REQUEST message sent to the eNB.
  • the eNB After receiving the message sent by the MME, the eNB configures the corresponding radio bearer for the UE, and sends the bearer configuration information to the UE through the RRC connection reconfiguration message; according to the agreement, the eNB needs to receive the data packet received from the radio bearer. Local broadcast.
  • the UE sends the V2X indication information to the access network node through the RRC message, and forwards the NAS message to the core network.
  • the core network creates a common bearer for the UE according to the NAS message sent by the UE, and the access network node allocates the core network node to the UE.
  • the bearer is marked to perform special processing on the data reported by the UE on the bearer.
  • the UE adds the V2X indication information to the RRC connection setup complete message, and indicates to the eNB that the current UE initiated service is a V2V road security service.
  • the eNB forwards the NAS message in the RRC connection setup complete message to the MME, and establishes a corresponding radio bearer for the UE according to the MME indication. According to the agreement, the eNB needs to perform local broadcast on the V2V road security service data reported by the UE, and the eNB performs local broadcast marking on the corresponding radio bearer.
  • the eNB sends the data packet uploaded by the UE that is received on the bearer of the local broadcast label to the other UEs in the local cell by using the broadcast mode.
  • the UE adds the V2X indication information to the RRC connection setup complete message, and indicates to the eNB that the UE reporting data corresponding to the UE request service needs to perform local broadcast and local MBSFN forwarding.
  • the eNB forwards the NAS message in the RRC connection setup complete message to the MME, and establishes a corresponding radio bearer for the UE according to the MME indication. According to the agreement, the eNB needs to perform local broadcast and local MBSFN forwarding on the V2V road safety service data reported by the UE, and the eNB marks the corresponding radio bearer.
  • the eNB sends the data packet uploaded by the UE that is received by the UE with the local broadcast flag to the other UEs in the local cell, and forwards the data to the eNBs that meet the requirements through the X2/S1 interface.
  • the embodiment provides a scheme for the UE to send V2X service related indication information to the network side node; the network side node receives the processing scheme of the V2X service related indication information sent by the UE; A scheme in which configuration information is sent to the UE.
  • the UE sends the V2X service related indication information to the network side node;
  • the V2X service related indication information may include: a V2X service identifier, a road safety service identifier, a vehicle road safety service identifier, a V2X local service identifier, a local forwarding service identifier, and a local MBSFN service identifier, V2X access identifier, vehicle access identifier, road security access identifier, and the like.
  • the UE may send the V2X service related indication information to the access network node by using an RRC message, where specifically:
  • Adding a new IE in the RRC connection setup complete message carrying indication information such as a V2X local service identifier, a local forwarding service identifier, a local MBSFN service identifier, and the like;
  • the UE sends the V2X service related indication information to the core network node by using the NAS message;
  • the network side node performs corresponding bearer configuration and setting processing for the UE according to the V2X service related indication information sent by the UE;
  • the network side node notifies the UE of bearer information and other resource information configured by the UE;
  • Sending resource configuration information such as EPS bearer context information, bearer configuration information, a public key used by the UE to decode a V2X-related service, a public key identifier, and a related parameter for generating a public key, to the UE.
  • resource configuration information such as EPS bearer context information, bearer configuration information, a public key used by the UE to decode a V2X-related service, a public key identifier, and a related parameter for generating a public key
  • the network is enabled to identify the V2X service initiated by the UE, and perform allocation processing of the corresponding resource.
  • the terminal device may be switched.
  • the following describes the handover.
  • FIG. 19 is a schematic diagram of an LTE network architecture.
  • an LTE system network side entity is composed of an MME/S-GW and an eNB.
  • the interface between the eNB and the eNB is an X2 interface, and the interface between the MME/S-GW and the eNB is an S1 interface.
  • a handover is required. If there is an X2 connection between the eNBs, the handover process can be completed through the X2 interface; if there is no X2 interface between the eNBs, the S1 interface can be used.
  • FIG. 20 is a schematic diagram of a non-contention random access handover procedure of an LTE system through an X2 interface.
  • the X2 interface is adopted.
  • the switching process mainly includes the following steps:
  • Step 2001 The source eNB sends a handover request message to the target eNB.
  • the handover request information carries information necessary for the UE to prepare for handover to the target eNB, for example, the UE is at the source eNB. Context information, target cell ID, etc.
  • Step 2002 The target eNB returns a handover request acknowledgment message to the source eNB.
  • the handover request ack message includes parameter information required for the UE to switch to the target eNB, such as: system information that may include the target eNB, preamble information when the UE performs random access at the target eNB, and the like;
  • Step 2003 The source eNB sends an RRC connection reconfigurationg message to the UE.
  • the source eNB After receiving the handover request ack message sent by the target eNB, the source eNB sends handover command information to the UE, instructing the UE to perform handover to the target eNB.
  • the content of the handover command sent by the source eNB to the UE is included in the handover request ack message sent by the target eNB to the source eNB;
  • Step 2005 The target eNB returns a random access response (RAR);
  • the UE After receiving the handover command, the UE performs synchronization with the target eNB. If a dedicated random access channel preamble (RACH preamble) is allocated in the handover command, the non-contention random access procedure is used to access the target cell, and if no dedicated RACH preamble is allocated, the competition based on competition is used. The access process accesses the target cell;
  • RACH preamble dedicated random access channel preamble
  • step 2006 the UE sends an RRC connection reconfigurationg complete message to the target eNB.
  • the UE After the UE successfully accesses the target cell, the UE sends a handover complete message, indicating to the target eNB that the handover procedure of the UE is completed.
  • Figure 21 is a schematic diagram of a non-contention random access handover procedure of an LTE system through an S1 interface. As shown in the figure, the handover procedure through the X2 interface is different through the MME. The handover process through the S1 interface mainly includes the following steps:
  • Step 2101 The source eNB sends a handover required message to the MME.
  • Step 2102 The MME sends a handover request message to the target eNB.
  • Step 2103 The target eNB returns a handover request ack message to the MME.
  • Step 2104 The MME returns a handover command message to the source eNB.
  • Step 2105 The source eNB sends an RRC connection reconfigurationg message to the UE.
  • Step 2106 The UE sends a Random Access preamble to the target eNB.
  • Step 2107 The target eNB returns an RAR.
  • Step 2108 The UE sends an RRC connection reconfigurationg complete message to the target eNB.
  • Step 2109 The target eNB sends a handover notify message to the MME.
  • the target eNB does not The UE can be processed correspondingly for the specific information to be sent and received.
  • the current handover signaling does not include information about whether the UE sends and receives V2X services.
  • the target eNB cannot perform special processing on the UE that performs V2X transmission and reception, which may cause the ongoing V2X service interruption of the UE. Causes traffic safety hazards.
  • the embodiment of the present invention further provides a processing solution in the case of a handover, which is used to solve the problem of continuity of information transmission and reception at the network side node during handover.
  • the solution can be specifically used on a network side node such as a base station or a repeater.
  • FIG. 22 is a schematic flowchart of a method for implementing a handover method on a source base station side. As shown in the figure, the following steps may be included:
  • Step 2201 Determine that the terminal device belonging to the first base station will switch to the second base station
  • the information to be reported by the terminal device is information that needs to be sent on time and frequency resources corresponding to the MBSFN area in each cell belonging to the same MBSFN area, and/or the received information is that each base station is The information transmitted on the time and frequency resources corresponding to the MBSFN area in each cell belonging to the same MBSFN area, that is, the information that needs to be transmitted in each cell of the MBSFN area belonging to the cell in which the terminal reports information is the data source cell information;
  • Step 2202 Send a handover request message to the second base station, and indicate, in the handover request message, setting information related to reporting and/or receiving information by the terminal device.
  • the method when the target base station allows the handover, the method further includes:
  • Step 2203 Receive, by the second base station, a handover request acknowledgement message that includes a handover command, where the handover command carries configuration information configured by the second base station according to setting information related to reporting and/or receiving information by the terminal device;
  • Step 2204 Send the handover command to the terminal device.
  • step 2202 indicating, in the handover request message, setting information related to reporting and/or receiving information by the terminal device may be indicated by one of the following manners or a combination thereof:
  • the setting information is added to the information corresponding to the DRB that carries the service for reporting and/or receiving information in the RRC Context.
  • V2X-related indication information of the UE such as a V2X bearer related indication, a V2X frequency-related indication, a V2X service-related indication information, and a V2X specific ID indication (such as an MME UE S1AP ID, an E-RAB ID, a DRB ID, a logical channel ID) Wait for V2X ID related instructions).
  • the specific way can be one of the following or a combination thereof:
  • V2X interest indication (V2Xinterestindication) information in the Access Stratum context (AS-Context) (such as E-UTRAN), such as whether the UE accepts the V2X service, the frequency at which the current UE accepts the V2X service, and the UE accepts
  • AS-Context Access Stratum context
  • the mode of V2X service such as unicast mode, MBMS mode, D2D mode, etc.), the priority of the UE to accept V2X service mode, etc.
  • the V2X specific ID value such as a special MME UE S1AP ID, an E-RAB ID, a DRB ID, and a logical channel ID, is used to notify the target network side node of the information related to the UE and the V2X.
  • FIG. 23 is a schematic flowchart of a method for implementing handover on a target base station side. As shown in the figure, the following steps may be included:
  • Step 2301 Receive a handover request message that is sent by the first base station to switch the terminal device that belongs to the first base station to the second base station, and indicate, in the handover request message, a setting related to reporting and/or receiving information by the terminal device. information;
  • the information to be reported by the terminal device is information that needs to be sent on time and frequency resources corresponding to the MBSFN area in each cell belonging to the same MBSFN area, and/or the received information is that each base station is The information transmitted on the time and frequency resources corresponding to the MBSFN area in each cell belonging to the same MBSFN area, that is, the information that needs to be transmitted in each cell of the MBSFN area belonging to the cell in which the terminal reports information is the data source cell information.
  • Step 2302 After determining that the terminal device that belongs to the first base station is to be handed over to the second base station, configure, by the terminal device, the resource that reports and/or receives information on the second base station, and returns the handover to the first base station.
  • the switching request confirmation message of the command carries the configuration information configured by the second base station according to the setting information related to the reporting and/or receiving information of the terminal device.
  • the resource that the terminal device reports and/or receives information on the second base station is configured, and the packet may include one or a combination of the following configurations:
  • the information may be used for public keys and related services (such as V2X services) required for decoding data corresponding to the MBSFN area.
  • public keys and related services such as V2X services
  • the DRB created for the service for reporting and/or receiving information for the terminal device is associated with the E-RAB corresponding to the service for reporting and/or receiving information by the terminal device;
  • the processing entity of the DRB corresponding to the service reporting and/or receiving the information of the terminal device is associated.
  • the target network side node may perform one or more of the following operations:
  • the corresponding resource is configured for the UE, and the configuration information is carried as the content of the handover command in the handover request ACK message and sent to the source network side node (such as the base station), so that the source network side node sends the handover command to the UE.
  • the content of the configuration operation may specifically include one or more of the following:
  • the UE is configured to the corresponding frequency point and the cell, so that the UE can perform V2X data transmission and reception on the frequency point and the cell, and the network side can configure multiple frequency points and cells for the UE.
  • multiple configurations can be configured as the case may be. Frequency point, etc.
  • Special configuration for UEs that support V2X services such as configuring a special semi-persistent schedule (SPS) period;
  • SPS semi-persistent schedule
  • VMS-related MBMS service information MBSFN area information (for the public key required to decode the data corresponding to the MBSFN area, the MBSFN area identifier corresponding to the related service (such as V2X service), etc.);
  • the DRB established for the UE V2X is associated with the E-RAB; the DRB is associated with the V2X special processing entity to perform special processing on the data packet sent and received on the DRB, for example, the collected data packet is integrity-protected and then forwarded to the surrounding cell. .
  • the handover implementation process when the UE has received the V2X service in the source cell and does not receive the V2X service is described below by way of example.
  • Embodiment C1 The UE has accepted the V2X service in the source cell.
  • the vehicle UE1 receives the V2X road safety service under the source eNB, and the UE1 periodically reports its own state information (such as location, speed, direction of travel, etc.) to the source eNB, and obtains state information of other surrounding UEs by receiving the MBMS service mode;
  • the source eNB determines that UE1 needs to handover from the current eNB to the target eNB.
  • the source eNB adds one or a combination of the following information to the handover request sent to the target eNB:
  • the target eNB After receiving the handover request sent by the source eNB, the target eNB determines that the UE1 is allowed to perform handover, and is performed by the UE1.
  • the target eNB may configure multiple frequency points for UE1 according to the situation, such as the target eNB is in a high vehicle density area or from low vehicle to high. In the excessive area of the vehicle density, the target eNB may configure multiple frequency points for UE1 to perform data transmission and reception to avoid congestion of V2X data transmission;
  • the configuration information is carried as a handover command in a handover request ack message and sent to the source eNB;
  • the DRB created for the UE1V2X service is associated with the E-RAB corresponding to the UE1V2X;
  • the source eNB After receiving the handover request ack message, the source eNB sends the handover command contained therein to the UE1.
  • Embodiment C2 The UE does not accept the V2X service in the source cell.
  • the vehicle UE has not accepted the V2X road safety service under the source eNB, but the UE is interested in the V2X road safety service;
  • the source eNB determines that the UE needs to handover from the current eNB to the target eNB.
  • the source eNB adds the following information to the handover request sent to the target eNB:
  • V2Xinterestindication indication information indicating that the UE can receive the frequency point list of the V2X service, and adopting the MBMS mode in a manner of accepting the V2X service
  • the target eNB After receiving the handover request sent by the source eNB, the target eNB determines that the UE1 is allowed to perform the handover, and can provide the V2X road security service for the UE1, and performs the following configuration and processing for the UE1:
  • the configuration information is carried in the handover request ack message as the content of the handover command and sent to the source eNB.
  • the source eNB After receiving the handover request ack message, the source eNB sends the handover command included in the source eNB to the UE.
  • the V2X service indication information of the UE is carried in the handover request message sent to the target network side node.
  • the target network side node If the UE handover is approved by the target network side node, the target network side node performs a corresponding operation, and notifies the source network side node of the relevant configuration information.
  • the target network side node at the time of handover can perform special processing on the UE supporting the V2X service, and ensure continuity of the V2X service in the UE handover process.
  • the asymmetric key encryption system is also known as a public key cryptosystem and a dual-key cryptosystem. It means that the key used to encrypt and decrypt the information is different, that is, there are two keys, one is public and the other is private. The two keys form a pair of key pairs. Public and private keys. If you use one of the keys to encrypt the data, you can only decrypt it with another key.
  • This encryption system is called an asymmetric key encryption system because the keys used in encryption and decryption are different.
  • the process of encrypting with a public key and decrypting with a private key is called an encryption process.
  • the process of encrypting with a private key and decrypting with a public key is called authentication (also known as integrity protection).
  • the asymmetric cryptographic algorithm has better confidentiality and does not require key exchange between the encryption and decryption users.
  • FIG 24 is a schematic diagram of the integrity protection process.
  • the originator uses the integrity protection key and other parameters and the message that needs integrity protection as the input of the integrity protection algorithm to generate a complete Sex protection check code MAC-I
  • the sender sends the message itself to the receiver together with the MAC-I
  • the receiver uses the integrity protection key and the corresponding parameters and the message itself as input to the integrity protection algorithm to generate an integrity.
  • the protection check code XMAC-I is compared with the received MAC-I.
  • the received message is considered to be consistent with the transmitted message, that is, it has not been tampered with by a third party.
  • the symmetric key mechanism when the symmetric key mechanism is adopted, the originating key and the receiving end key are the same.
  • the asymmetric key mechanism is adopted, the originating key and the receiving end key are different, and the originating end adopts the private key.
  • the receiving end uses a public key.
  • a corresponding data security processing solution is also proposed in the embodiment of the present invention, which is used to solve the problem that the network side node uses the eMBMS method after collecting the information.
  • the information security problem when the terminal device is covered by the network side node, and the solution can be specifically used for the network side node such as the base station and the repeater.
  • the method further includes:
  • the information is integrity protected with a private key, which is a private key corresponding to the MBSFN area.
  • the network side node sends the collected road security related data packet after the integrity protection by the private key to the UE.
  • the road security related data packets collected by the network side node after the integrity protection by the private key are classified into two types: one is that the network side node uses the road security related data packet reported by the UE in the coverage area.
  • the internet The data packet that the side node itself associates with the private key for integrity protection; the other type is the data packet obtained by the network side node from other network side nodes, and the other network side nodes may be existing network side nodes such as eNB, HeNB, and Relay. It may also be a newly added network side node, and these data packets have been integrity protected by other network side nodes using private keys corresponding to other network side nodes before reaching the network side node.
  • the network side node may use the MBSFN mode or the Point To Multipoint (P2M) broadcast or multicast mode.
  • P2M Point To Multipoint
  • the network side node sends the data security related data packet reported by the UE in the coverage area to the other related network side nodes by using the private key associated with the network side node itself for integrity protection. This is because the data source cell in each MBSFN area needs to provide the same data to other cells in the MBSFN area to ensure that all cells in one MBSFN area can transmit the same data on the same time-frequency resource, thereby The receiving UE obtains a receive diversity gain.
  • the network side node needs to determine the cell associated with the network side node, and determines each cell as the other cell in the MBSFN area of the data source cell, and uses the integrity protection of each cell for the road security related data packet reported by the UE under each cell. After the private key performs integrity protection, it is sent to each cell as a network side node corresponding to another cell in the MBSFN area of the data source cell.
  • the processing information according to the rule corresponding to the MBSFN area includes:
  • the public key is used to perform integrity verification on the integrity-protected information.
  • the UE after receiving the road security related data packet sent by the network side, the UE obtains the security public key corresponding to the MBSFN area sent by the network side node to each MBSFN area.
  • the packet is integrity verified.
  • different MBSFN areas use different public keys, since one cell may belong to multiple MBSFN areas, the UE may receive multiple data packets corresponding to the MBSFN area. Therefore, the UE performs integrity on the received data packets. Before the verification, the MBSFN area corresponding to the data packet needs to be determined, and then the integrity of the data packet is verified by using the public key of the MBSFN area.
  • the public key may be a public key sent by the base station, and/or is a public key stored in the terminal device, and/or obtained by other means (for example, by a Road Side Unit (RSU)). Public key.
  • RSU Road Side Unit
  • the base station side may further include:
  • the public key may be from the MME and/or MCE.
  • the UE obtains the integrity-protected road security-related data packet sent by the network-side node, and needs to obtain the public key for integrity verification of the received road safety-related data packet in advance.
  • the UE can learn the public key of integrity verification in two ways:
  • Mode 1 The network side node sends the security public key corresponding to the MBSFN area associated with the UE to the UE.
  • the network side node here may be an existing network side node such as an eNB, a HeNB, or a Relay, or may be a newly added other type of network side node (such as an RSU).
  • the MBSFN area associated with the network side node includes an MBSFN area associated with each cell under the network side node.
  • the network side node may associate one or more MBSFN areas, as shown in Figure 10, Cell 1-Cell 7 associates 7 MBSFN areas.
  • the security public key here is used by the UE to perform integrity verification on the road safety information received from the network side node.
  • the security public key may be generated by the network side node itself or by a higher layer network side node, such as an eNB, an MME, a Multi-cell/multicast Coordination Entity (MCE), and a home subscriber server (Home). Subscriber Server, HSS), broadcast multicast service center (BM-SC), etc.
  • the network side node sends the security public key corresponding to the MBSFN area to the UE in broadcast, multicast, and unicast mode.
  • system broadcast such as carried in the set SIB
  • MBMS broadcast such as in the Multicast Control Channel (MCCH) or as a specific service
  • MTCH multicast traffic channel
  • the target eNB may send the corresponding public key to the UE through the handover command, or may be sent by the target eNB to the UE through the NAS message after the handover is completed, or may be sent by the UE after receiving the handover to the target base station by the target eNB.
  • System information is obtained.
  • the cell under the target eNB may be associated with the new MBSFN area. Therefore, in the specific implementation, the public key corresponding to the MBSFN area associated with the target eNB cell may be notified to the UE during the handover.
  • the security public key corresponding to each MBSFN area may be directly stored in a Subscriber Identity Module (SIM) or a Universal Subscriber Identity Module (USIM) card of the UE.
  • SIM Subscriber Identity Module
  • USIM Universal Subscriber Identity Module
  • the following describes an implementation process of security processing in the process of transmitting information to the UE by the eNB.
  • the eNB1 performs integrity protection on the road security related data packets reported by the UEs in each cell, and then sends the road security related data packets reported by the UEs in each cell to the UE.
  • Related neighbor eNBs the eNB1 performs integrity protection on the road security related data packets reported by the UEs in each cell, and then sends the road security related data packets reported by the UEs in each cell to the UE.
  • the eNB1 includes two cells, cell 1 and cell 2, and the MBSFN areas in which cell 1 and cell 2 are used as data source cells are respectively MBSFN area 2 and MBSFN area 3.
  • the subframes occupied by MBSFN area 2 and MBSFN area 3 are respectively Subframe 7 and subframe 8 in the radio frame;
  • eNB2 includes one cell cell3, cell 1 of eNB1 and cell 3 of eNB2 are geographically adjacent cells, and cell 3 of eNB2 belongs to cell 1 of eNB1 as data source cell In the MBSFN area 2, the cell 3 of the eNB2 needs a subframe corresponding to the MBSFN area 2 (in each radio frame)
  • the subframe 7) transmits the same data on the subframe corresponding to the MBSFN area 2 in the cell 1 of the eNB1, and the data transmitted in the subframe corresponding to the MBSFN area 2 is forwarded by the eNB1 to the eNB2.
  • FIG. 25 is a schematic diagram of an information transmission implementation environment for performing security processing. As shown in the figure, there are UE1 and UE2 under eNB1 shown in FIG. 25, both UEs are under Cell 1 coverage, eNB2 has UE3, and UE3 is under cell3 coverage.
  • the eNB1 forwards the road safety data transmitted in the MBSFN area 2 to the eNB 2 through the X2 interface.
  • the specific process is as follows:
  • the eNB1 collects the road safety data packets reported by the UE1 and the UE2.
  • the road safety data packet collected by the UE1 and the UE2 may be collected periodically (for example, every 30 ms), or may be collected at a set time point. For example, at a set time before the MBSFN subframe corresponding to the MBSFN area of the data source cell, each of the eNB1 may collect the road security data packet reported by the UE at any time as needed;
  • eNB1 uses the private key for integrity protection of the collected data packets. For example, in this example, the data reported by UE1 and UE2 is integrity-protected by using the private key corresponding to the MBSFN area of the data source cell.
  • the eNB1 transmits the integrity-protected data packet to each cell in the eNB1, and transmits the data in the set data format on the MBSFN subframe corresponding to the MBSFN area in which each cell is the data source cell. Specifically, the eNB 1 needs to transmit the data packet reported by the UE in the cell 1 to the subframe occupied by the MBSFN area 2 according to the set data format after being completely protected by the private key. At the same time, the eNB1 forwards the integrity-protected data packet to the network-side node corresponding to the other cells in the MBSFN area of the data source cell. For example, in this example, the cell 3 under the eNB2 belongs to the cell 1 under the eNB1. It is the MBSFN area 2 of the data source cell. Therefore, the eNB1 needs to forward the data of the cell 1 using the private key for integrity protection to the eNB2.
  • the UE1 and the UE2 After decoding the data packet according to the data format specified by the network side in the subframe occupied by the MBSFN area 2, the UE1 and the UE2 perform integrity verification on the received data packet by using the public key corresponding to the data of the decoded MBSFN area 2. If the integrity verification is passed, the data in the data packet is considered to be valid road safety data, and the corresponding data packet is submitted to the upper layer. If the integrity verification fails, the received road safety data is considered unreliable, and the corresponding data is The packet is discarded.
  • the eNB2 sends the integrity-protected road safety related data packet forwarded by the neighboring eNB1 to the UE.
  • UE1 and UE2 there are two UEs under eNB1, namely UE1 and UE2, two UEs are under Cell 1 coverage, and one UE3 is under eNB2, UE3 is under Cell 3 coverage of eNB2, and cell 1 of eNB1 is
  • the cell 3 of the eNB2 is a cell adjacent to the geographical location, and the cell 3 of the eNB2 belongs to the MBSFN area 2 in which the cell 1 of the eNB1 is the data source cell.
  • the cell 3 of the eNB2 needs the subframe corresponding to the MBSFN area 2 (each wireless)
  • the subframe 7) in the frame transmits the same data on the subframe corresponding to the MBSFN area 2 in the cell 1 of the eNB1, and the data transmitted in the subframe corresponding to the MBSFN area 2 is forwarded by the eNB1 to the eNB2 through the X2 interface.
  • the specific process is as follows:
  • the eNB2 collects the road safety data reported by the UE under the cell 1 of the eNB1 forwarded by the eNB1 on the X2 interface of the eNB1.
  • the collection of road safety data forwarded by eNB2 to eNB1 on the X2 interface of eNB1 may be periodic.
  • the collection (for example, every 30ms) may also be collected at a set time point (for example, at a set time before the MBSFN subframe corresponding to the MBSFN area of each data cell of the eNB2), or may be an X2 interface at any time. Collecting road safety data packets on;
  • the data to be collected later is then transmitted in the set data format on the subframe occupied by the MBSFN area 2 at the appointed time.
  • the agreed time is obtained from the synchronization message corresponding to the road safety data forwarded by eNB1 to eNB2.
  • the UE3 After decoding the data packet according to the data format specified by the network side in the subframe occupied by the MBSFN area 2, the UE3 performs integrity verification by using the public key corresponding to the data of the decoded MBSFN area 2 data. If the integrity verification is passed, the data in the data packet is considered to be valid road safety data, and the corresponding data packet is submitted to the upper layer. If the integrity verification fails, the received road safety data is considered unreliable, and the corresponding data is The packet is discarded.
  • FIG. 26 is a schematic diagram of the key processing implementation environment in the information security processing. As shown in the figure, the specific process is as follows:
  • the MME obtains a private key for integrity protection of the road security data transmitted by the eNB by using the MBMS, and a public key for the UE to perform integrity verification on the road security data packet received by the MBMS.
  • the public key and the private key of the integrity protection obtained by the MME may be generated by the MME itself, or may be obtained by the MME from other entities such as an HSS, an MBMS gateway, or the like;
  • the MME notifies the eNB of the private key for integrity protection of the road security data reported by the collected UEs by the eNB under the eNB through the S1 interface signaling.
  • the private key is used by each eNB to perform integrity protection on a data packet sent in an MBSFN area in which the cell is a data source cell.
  • the MME notifies the UE of the public key for integrity verification of the received road safety data packet through NAS signaling.
  • the MME needs to notify the UE to perform integrity on each MBSFN area data, because a cell can belong to multiple MBSFN areas at the same time.
  • the MME needs to notify the UE to perform integrity on each MBSFN area data.
  • the RRC message piggybacking may be adopted, for example, it may be installed in a message container, and the message container is piggybacked in the RRC connection reconfiguration message and sent to the UE.
  • the RRC message carrying the NAS signaling may also be sent to the UE.
  • the UE obtains the public key for integrity verification of the MBSFN area data of each road security message associated with the current cell from the NAS signaling, and uses the public key corresponding to each MBSFN area to receive the road in each MBSFN area. Safety data for integrity verification.
  • the MCE sends the public key of the UE for integrity verification to the UE through MCCH/BCCH signaling.
  • the private key used by the eNB is sent by the MCE to the eNB. The specific process is as follows:
  • the MCE obtains a public key for integrity protection of the road security data transmitted by the eNB by using the MBMS, and a private key for the UE to perform integrity verification on the road security data packet received by the MBMS.
  • the public key and private key of the integrity protection obtained by the MCE may be generated by the MCE itself, or may be obtained by the MCE from other entities such as the MME;
  • the MCE notifies the eNB of the private key for integrity protection of the road safety data by the eNB under the eNB through the M2 interface signaling.
  • the private key is used by each eNB to perform integrity protection on a data packet sent in an MBSFN area in which the cell is a data source cell.
  • the MCE notifies the UE of the public key for integrity verification of the received road safety data packet through MCCH/BCCH signaling.
  • the MCE may be in the MCCH signaling corresponding to each MBSFN area, when the data source cells of the different MBSFN areas use different private keys to perform integrity protection on the data packets sent by the MBSFN area.
  • the public key for informing the UE to perform integrity verification on the corresponding MBSFN area data may also carry the public key for integrity verification of each MBSFN area data in BCCH signaling (such as SIB13 or new SIB); when different MBSFN areas are used
  • BCCH signaling such as SIB13 or new SIB
  • the MCE may carry the same public public key for integrity verification of the road safety data in the MCCH signaling corresponding to each MBSFN area, also in the BCCH.
  • Signaling (such as SIB13 or new SIB) carries a public public key for integrity verification of road safety data.
  • the MCE sends the BCCH or MCCH signaling including the integrity verification public key to the corresponding eNB through the M2 interface.
  • the eNB will include the integrity verification certificate on the BCCH of each cell or the MCCH resource corresponding to the MBSFN area associated with each cell.
  • the BCCH or MCCH signaling of the key is sent to the UE.
  • the UE obtains the public key for integrity verification of the MBSFN area data of each road security message associated with the current cell from the BCCH or the MCCH signaling, and uses the public key corresponding to each MBSFN area to protect the road security in each MBSFN area. The data is integrity verified.
  • the embodiment provides a scheme in which the network side node sends the collected road safety data to the UE and sends it to the neighboring network side node in the MBSFN manner; the UE receives the road security data sent by the network side node.
  • Solution a processing scheme in which the network side node receives the road safety data sent by the neighboring network side node; and the eNB and the UE obtain the integrity protection key.
  • the network side node sends the collected road security related data packet after the integrity protection by the private key to the UE;
  • the network side node of the network side node transmits the data packet related to the road safety report reported by the UE in the coverage area to the other related network side nodes by using the private key associated with the network side node itself for integrity protection;
  • the UE After receiving the road security related data packet sent by the network side, the UE sends the data packet according to the received network side node.
  • the security public key corresponding to the MBSFN area performs integrity verification on the data packets of each MBSFN area;
  • the MME sends the public key of the integrity verification of the UE to the UE through the NAS signaling; or the MCE sends the public key of the integrity verification of the UE to the UE by using the MCCH/BCCH signaling.
  • an embodiment of the present invention further provides an information transmitting apparatus and an information receiving apparatus. Since the principles of solving the problems of these apparatuses are similar to an information transmitting method and an information receiving method, the implementation of these apparatuses can be referred to the method. The implementation, repetitions will not be repeated.
  • FIG. 27 is a schematic structural diagram of an information transmitting apparatus, as shown in the figure, which may include:
  • the report information receiving module 2701 is configured to receive information reported by the terminal device that is managed by the first cell to the first base station, where the first cell is a cell that belongs to the first base station;
  • a distribution module 2702 configured to distribute the information to each second base station to which each second cell belonging to the same MBSFN area belongs to the first cell, where the information is to be in the second cell under each base station and in the MBSFN The time and frequency resources corresponding to the area are sent;
  • the first sending module 2703 is configured to specify the time and frequency resources corresponding to the MBSFN area in the first cell of the first base station and the second cell belonging to the same MBSFN area of the first base station that belongs to the first base station.
  • the terminal device sends the message.
  • it may further include:
  • the integrity protection module 2704 is configured to perform integrity protection on the information when the information is distributed to the second base station and sent to the designated terminal device, where the private key is associated with the MBSFN.
  • the private key corresponding to the zone.
  • the first sending module may be further configured to send, to the terminal device, a public key for performing integrity verification on the integrity-protected information, where the public key is a public key corresponding to the MBSFN area.
  • the first sending module may further be configured to send the public key from the MME and/or the MCE to the terminal device.
  • the information reported by the terminal equipments of the first cell to the first base station may be V2X information for the V2X service.
  • one MBSFN area may include one first cell and at least one second cell.
  • the apparatus may include:
  • the distribution information receiving module 2801 is configured to receive information from the first cell that is sent by the first base station to the second base station, where the first cell is a cell that belongs to the first base station;
  • a cell determining module 2802 configured to determine a second cell that belongs to the same MBSFN area as the first cell, where the second cell is a cell that belongs to the second base station;
  • the second sending module 2803 is configured to send information to the designated terminal device on the time and frequency resources corresponding to the MBSFN area in the second cell of the second base station.
  • the distribution information receiving module may be further configured to receive information for integrity protection with a private key, where the private key is a private key corresponding to the MBSFN area.
  • it may further include:
  • the second sending module is further configured to send, to the terminal device, a public key for performing integrity verification on the integrity-protected information, where the public key is a public key corresponding to the MBSFN area.
  • the second sending module may be further configured to send the public key from the MME and/or the MCE to the terminal device.
  • the information may be V2X information for V2X services.
  • one MBSFN area may include one first cell and at least one second cell.
  • the apparatus may include:
  • the information receiving module 2901 is configured to receive information sent by the base station
  • the area determining module 2902 is configured to determine, according to the time and frequency resources of the received information, a corresponding MBSFN area;
  • the information processing module 2903 is configured to process information according to a rule corresponding to the MBSFN area.
  • the information processing module may be further configured to: when the information is integrity-protected by using a private key corresponding to the MBSFN area, determine a public key corresponding to the MBSFN area; Perform integrity verification on integrity-protected information.
  • the information processing module may further be used for a public key obtained by one or a combination of the following: a public key sent by the base station, a public key stored in the terminal device, and a public key obtained by the roadside unit RSU.
  • the information may be V2X information for V2X services.
  • one MBSFN area may include one first cell and at least one second cell.
  • FIG. 30 is a schematic structural diagram of a first base station. As shown in the figure, the base station includes:
  • the processor 3000 is configured to read a program in the memory 3020 and perform the following process:
  • the transceiver 3010 is configured to send data under the control of the processor 3000, and performs the following processes:
  • the first cell of the first base station and the second cell belonging to the first base station belonging to the same MBSFN area as the first base station transmit information to the designated terminal device on the time and frequency resources corresponding to the MBSFN area.
  • the transceiver 3010 when the transceiver 3010 distributes information to the second base stations and sends information to the designated terminal device, the transceiver 3010 may further be used to:
  • the information is integrity protected with a private key, which is a private key corresponding to the MBSFN area.
  • the transceiver 3010 can be further configured to:
  • the public key is from the MME and/or the MCE.
  • the information reported by the terminal device under the jurisdiction of the first cell to the first base station is V2X information for the V2X service.
  • one MBSFN area includes one first cell and at least one second cell.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 3000 and various circuits of memory represented by memory 3020.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 3010 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 3000 is responsible for managing the bus architecture and general processing, and the memory 3020 can store data used by the processor 3000 when performing operations.
  • FIG. 31 is a schematic structural diagram of a second base station. As shown in the figure, the base station includes:
  • the processor 3100 is configured to read a program in the memory 3120 and perform the following process:
  • the transceiver 3110 is configured to send data under the control of the processor 3100, and performs the following processes:
  • information is transmitted to the designated terminal device on the time and frequency resources corresponding to the MBSFN area.
  • the information is information that is integrity protected with a private key
  • the private key is a private key corresponding to the MBSFN area.
  • the transceiver 3110 can be further configured to:
  • the public key may be a public key from an MME and/or an MCE.
  • the information may be V2X information for V2X services.
  • one MBSFN area includes one first cell and at least one second cell.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 3100 and various circuits of memory represented by memory 3120.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • the transceiver 3110 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 3100 is responsible for managing the bus architecture and general processing, and the memory 3120 can store data used by the processor 3100 in performing operations.
  • the terminal device includes:
  • the processor 3200 is configured to read a program in the memory 3220 and perform the following process:
  • the transceiver 3210 is configured to send data under the control of the processor 3200, and performs the following processes:
  • the processor 3200 when the information is the integrity protection information by using the private key corresponding to the MBSFN area, when the information is processed according to the rule corresponding to the MBSFN area, the processor 3200 may further be configured to:
  • the public key is used to perform integrity verification on the integrity-protected information.
  • the public key may be a public key obtained by one or a combination of the following: a public key sent by the base station, a public key stored in the terminal device, and a public key obtained by the roadside unit RSU.
  • the information is V2X information for V2X services.
  • one MBSFN area includes one first cell and at least one second cell.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 3200 and various circuits of memory represented by memory 3220.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 3210 may be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the user interface 3230 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 3200 is responsible for managing the bus architecture and the usual processing, and the memory 3220 can store the processor 3200 The data used to perform the operation.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

公开了一种信息发送接收方法及装置，包括：在信息接收基站上，接收第一小区所辖的各终端设备上报的信息后分发给与第一小区属于同一多播广播单频网络区域的各第二小区归属的各第二基站；在接到分发信息的基站上，以及第一基站上，在第一小区以及第二小区中，在与多播广播单频网络区域对应的时间与频率资源上向指定的终端设备发送信息。在终端设备上，接收基站发送的信息；根据接收信息的时间与频率资源确定对应的多播广播单频网络区域；按与该多播广播单频网络区域对应的规则处理信息。本发明可以满足一些对时延有特定要求的业务的需求。

Description

一种信息发送接收方法及装置
本申请要求在2015年07月07日提交中国专利局、申请号为201510394342.0、发明名称为“一种信息发送接收方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及无线通信技术领域，特别涉及一种信息发送接收方法及装置。
背景技术
现有的移动通信主要是人与人之间的通信，随着硬件设备的小型化和智能化，未来的移动通信更多“人与物”及“物与物”之间的高速连接应用。以机器通信(Machine Type Communication，MTC)业务为例，MTC应用范围非常广泛，如移动医疗、车联网、智能家居、工业控制、环境监测等将会推动MTC系统应用爆发式增长，大量设备将接入网络，实现真正的“万物互联”，为移动通信带来无限生机。同时，广泛的MTC系统应用范围也会给移动通信带来新的技术挑战，例如实时云计算、虚拟现实、在线游戏、远程医疗、智能交通、智能电网、远程实时控制等业务对时延比较敏感，对时延提出更高的需求。但这些业务的应用也对信息交互的时延提出了较高的要求。
下面以智能交通中的车与外界的信息交换(Vehicle to Everything，V2X)业务为例说明现有技术的不足。
研究表明，80％的公路交通事故是由于驾驶员在事故发生前3秒内的疏忽造成的。如果提前0.5秒示警驾驶员，可以避免60％的追尾事故；若驾驶员能提早1.5秒得到示警并采取措施，则可以避免90％的追尾撞车事故。这些碰撞避免类应用要求在设定范围内(如300米)的车辆之间或车辆与路侧基础设施之间以极短的传输时延(典型值为100ms)进行道路安全相关的信息交换。采用包括车与车的信息交换(vehicle to vehicle，V2V)、车与基础设施的信息交换(Vehicle-to-Infrastructure，V2I)、车与人的信息交换(Vehicle-to-Pedestrian，V2P)等的V2X通信方式提前感知道路安全风险的主动安全预警技术是当前各国试图解决道路交通安全问题一种新的思路，通过车与车、车与路侧基础设施间的实时信息交互，告知彼此目前的状态(包括车辆的位置、速度、加速度、行驶路径)及获知的道路环境信息，协作感知道路危险状况，及时提供前向碰撞告警、盲区告警/换道告警、协作合路辅助、协作合路辅助、交通信号灯违规告警等多类告警信息，从而可以避免大多数道路交通安全事故的发生。一些典型应用有紧急制动告警、协作合路辅助、交通信号灯违规告警等。
现有技术中，在采用V2X方式支持道路安全应用时，是基于eMBMS技术实现的。其中，演进的MBMS(evolved MBMS，eMBMS)技术是指：长期演进(Long Term Evolution，LTE)中的MBMS，多媒体广播\组播服务(Multimedia Broadcast/Multicast Service，MBMS)技术是用于为无线小区中的用户提供多媒体广播和组播服务的。eMBMS支持多播广播单频网络(Multicast Broadcast Single Frequency Network，MBSFN)传输方式，即：属于同一个MBSFN区域中的小区在相同时间和频率资源上在多个小区同时发送完全相同的内容。接收用户设备(User Equipment，UE)可以将多个小区发送的信号看成一个信号的多条路径，对这些信号进行处理，获得宏分集增益，从而提高小区边缘用户的信号接收质量。
采用V2X方式支持道路安全应用，通常情况下要求发送车辆从高层接收到道路安全消息到接收车辆的媒质接入控制(Medium Access Control，MAC)层将道路安全消息递交给高层之间的时延不大于100ms，而现有技术的不足就在于：基于现有eMBMS技术实现的V2X业务，信息交互总时延为160ms，不能满足支持道路安全应用的时延要求。
事实上，该问题不仅存在于V2X业务中，在其他类似的环境、或者应用中，也存在该问题，也即，现有基于eMBMS技术实现的信息传输，不能满足一些业务的时延要求。
发明内容
本发明实施例中提供了一种信息发送接收方法及装置，用以减少信息的发送接收时间。
本发明实施例中提供了一种信息发送方法，包括：
接收第一小区所辖的各终端设备上报至第一基站的信息，所述第一小区是归属于第一基站的小区；
将该信息分发给与第一小区属于同一MBSFN区域的各第二小区归属的各第二基站，所述信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发送；
在第一基站的第一小区以及归属于第一基站的与第一小区属于同一MBSFN区域的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
较佳地，在向所述各第二基站分发信息，以及向指定的终端设备发送信息时，进一步包括：
将所述信息用私钥进行完整性保护，所述私钥是与所述MBSFN区域对应的私钥。
较佳地，进一步包括：
向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
较佳地，所述公钥是来自MME和/或MCE的。
较佳地，第一小区所辖的各终端设备上报至第一基站的信息是用于V2X业务的V2X信息。
较佳地，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
本发明实施例中提供了一种信息发送方法，包括：
接收第一基站发送给第二基站的来自第一小区的信息，所述第一小区是归属于第一基站的小区；
确定与第一小区属于同一MBSFN区域的第二小区，所述第二小区是归属于第二基站的小区；
在第二基站的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
较佳地，所述信息是用私钥进行完整性保护的信息，所述私钥是与所述MBSFN区域对应的私钥。
较佳地，进一步包括：
向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
较佳地，所述公钥是来自MME和/或MCE的公钥。
较佳地，所述信息是用于V2X业务的V2X信息。
较佳地，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
本发明实施例中提供了一种信息接收方法，包括：
接收基站发送的信息；
根据接收信息的时间与频率资源确定对应的MBSFN区域；
按与该MBSFN区域对应的规则处理信息。
较佳地，在所述信息是用与所述MBSFN区域对应的私钥进行完整性保护的信息时，按与该MBSFN区域对应的规则处理信息包括：
确定与所述MBSFN区域对应的公钥；
采用所述公钥进行对完整性保护后的信息进行完整性验证。
较佳地，所述公钥是通过以下方式之一或者其组合来获得的公钥：基站发送的公钥、存储在终端设备中的公钥、通过路侧单元RSU获得的公钥。
较佳地，所述信息是用于V2X业务的V2X信息。
较佳地，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
本发明实施例中提供了一种信息发送装置，包括：
上报信息接收模块，用于接收第一小区所辖的各终端设备上报至第一基站的信息，所述第一小区是归属于第一基站的小区；
分发模块，用于将该信息分发给与第一小区属于同一MBSFN区域的各第二小区归属的各第二基站，所述信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发送；
第一发送模块，用于在第一基站的第一小区以及归属于第一基站的与第一小区属于同一MBSFN区域的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
较佳地，进一步包括：
完整性保护模块，用于在向所述各第二基站分发信息，以及向指定的终端设备发送信息时，将所述信息用私钥进行完整性保护，所述私钥是与所述MBSFN区域对应的私钥。
较佳地，第一发送模块进一步用于向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
较佳地，第一发送模块进一步用于向终端设备发送来自MME和/或MCE的公钥。
较佳地，第一小区所辖的各终端设备上报至第一基站的信息是用于V2X业务的V2X信息。
较佳地，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
本发明实施例中提供了一种信息发送装置，包括：
分发信息接收模块，用于接收第一基站发送给第二基站的来自第一小区的信息，所述第一小区是归属于第一基站的小区；
小区确定模块，用于确定与第一小区属于同一MBSFN区域的第二小区，所述第二小区是归属于第二基站的小区；
第二发送模块，用于在第二基站的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
较佳地，分发信息接收模块进一步用于接收用私钥进行完整性保护的信息，所述私钥是与所述MBSFN区域对应的私钥。
较佳地，进一步包括：
第二发送模块进一步用于向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
较佳地，第二发送模块进一步用于向终端设备发送来自MME和/或MCE的公钥。
较佳地，所述信息是用于V2X业务的V2X信息。
较佳地，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
本发明实施例中提供了一种信息接收装置，包括：
信息接收模块，用于接收基站发送的信息；
区域确定模块，用于根据接收信息的时间与频率资源确定对应的MBSFN区域；
信息处理模块，用于按与该MBSFN区域对应的规则处理信息。
较佳地，信息处理模块进一步用于在所述信息是用与所述MBSFN区域对应的私钥进行完整性保护的信息时，确定与所述MBSFN区域对应的公钥；采用所述公钥进行对完整性保护后的信息进行完整性验证。
较佳地，信息处理模块进一步用于通过以下方式之一或者其组合来获得的公钥：基站发送的公钥、存储在终端设备中的公钥、通过路侧单元RSU获得的公钥。
较佳地，所述信息是用于V2X业务的V2X信息。
较佳地，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
本发明实施例提供了一种第一基站，包括：
处理器，用于读取存储器中的程序，执行下列过程：
确定与第一小区属于同一MBSFN区域的第二小区，以及第二小区归属的基站；
收发机，用于在处理器的控制下发送数据，执行下列过程：
接收第一小区所辖的各终端设备上报至第一基站的信息，所述第一小区是归属于第一基站的小区；
将该信息分发给与第一小区属于同一MBSFN区域的各第二小区归属的各第二基站，所述信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发送；
在第一基站的第一小区以及归属于第一基站的与第一小区属于同一MBSFN区域的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
较佳的，收发机在向所述各第二基站分发信息，以及向指定的终端设备发送信息时，可以进一步用于：
将所述信息用私钥进行完整性保护，所述私钥是与所述MBSFN区域对应的私钥。
较佳的，收发机可以进一步用于：
向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
较佳的，所述公钥是来自MME和/或MCE的。
较佳的，第一小区所辖的各终端设备上报至第一基站的信息是用于V2X业务的V2X信息。
较佳的，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
本发明实施例提供了一种第二基站，包括：
处理器，用于读取存储器中的程序，执行下列过程：
确定与第一小区属于同一MBSFN区域的第二小区，所述第二小区是归属于第二基站的小区；
收发机，用于在处理器的控制下发送数据，执行下列过程：
接收第一基站发送给第二基站的来自第一小区的信息，所述第一小区是归属于第一基站的小区；
在第二基站的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
较佳的，所述信息是用私钥进行完整性保护的信息，所述私钥是与所述MBSFN区域对应的私钥。
较佳的，收发机可以进一步用于：
向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
较佳的，所述公钥可以是来自MME和/或MCE的公钥。
较佳的，所述信息可以是用于V2X业务的V2X信息。
较佳的，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
本发明实施例提供了一种终端设备，包括：
处理器，用于读取存储器中的程序，执行下列过程：
根据接收信息的时间与频率资源确定对应的MBSFN区域；
按与该MBSFN区域对应的规则处理信息；
收发机，用于在处理器的控制下发送数据，执行下列过程：
接收基站发送的信息。
较佳的，在所述信息是用与所述MBSFN区域对应的私钥进行完整性保护的信息时，按与该MBSFN区域对应的规则处理信息时，处理器还可以用于：
确定与所述MBSFN区域对应的公钥；
采用所述公钥进行对完整性保护后的信息进行完整性验证。
较佳的，所述公钥可以是通过以下方式之一或者其组合来获得的公钥：基站发送的公钥、存储在终端设备中的公钥、通过路侧单元RSU获得的公钥。
较佳的，所述信息是用于V2X业务的V2X信息。
较佳的，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
本发明有益效果如下：
在本发明实施例提供的技术方案中，一个方案中，在基站上，当接收到归属自身下辖小区的各终端设备上报的信息后，就向相关的基站发送所述信息，若发送的基站为第一基站，上报信息的终端设备归属的小区为第一小区，接收信息的相关的各个基站为第二基站，那么，第一小区与第二基站下辖的某些小区是属于同一MBSFN区域的；
而在另一个相应的方案中，在另一侧相关的基站(也即第二基站)上，在接收到第一 基站发送的所述信息后，确定自身下辖的小区中与该信息来源的第一小区属于同一MBSFN区域的小区。
然后，在第一基站以及相关的第二基站上，在相同的时间与频率资源上向需要的终端设备下发所述信息，这样，在同一MBSFN区域内的终端设备都同时接收到了来自同一个小区的终端设备上报的信息，且因每个MBSFN区域的发送资源不同，使得各MBSFN区域数据在接收时不受彼此干扰。
在本发明实施例中提供的技术方案中，并未如现有技术般将终端设备上报的信息上报给网络侧的S-GW、P-GW、BMSC等处理后，再由BMSC指示基站采用MBSFN方式发送；而是直接在基站之间进行终端设备上报的信息交互，并在基站上处理后即分发给各基站采用MBSFN方式发送，由于没有网络侧各核心网实体的中转，因此减少了MBSFN方式发送MBMS数据的耗时，使得本发明实施例中提供的技术方案可以满足一些对时延有特定要求的业务的需求。
进一步的，本发明实施例中还提供了信息的完整性保护、验证的处理方案，提高了信息的安全性。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本发明的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1为本发明实施例中eMBMS系统架构示意图；
图2为本发明实施例中基于eMBMS实现V2X通信的网络结构示意图；
图3为本发明实施例中增强的基于eMBMS实现V2X通信的网络结构示意图；
图4为本发明实施例中信息发送方法一实施流程示意图；
图5为本发明实施例中信息发送方法二实施流程示意图；
图6为本发明实施例中信息接收方法实施流程示意图；
图7为本发明实施例中信息收发方法实施流程示意图；
图8为本发明实施例中MBSFN区域构成示意图；
图9为本发明实施例中高速场景中MBSFN区域构成示意图；
图10为本发明实施例中小区与MBSFN区域间关系示意图；
图11为本发明实施例中为高速公路场景下小区与MBSFN区域间关系示意图；
图12为本发明实施例中X2接口MBSFN数据传输通道建立信令交互过程实施流程示意图；
图13为本发明实施例中X2接口MBSFN数据传输通道配置更新过程实施流程示意图；
图14为本发明实施例中X2接口MBSFN数据传输通道去激活/释放过程实施流程示意 图；
图15为本发明实施例中EPS承载构成示意图；
图16为本发明实施例中信息上报方法实施流程示意图；
图17为本发明实施例中承载建立方法实施流程示意图；
图18为本发明实施例中接入网节点的信息接收方法实施流程示意图；
图19为本发明实施例中LTE网络架构示意图；
图20为本发明实施例中LTE系统通过X2接口的非竞争随机接入切换流程示意图；
图21为本发明实施例中LTE系统通过S1接口的非竞争随机接入切换流程示意图；
图22为本发明实施例中源基站侧的切换方法实施流程示意图；
图23为本发明实施例中目标基站侧的切换方法实施流程示意图；
图24为本发明实施例中完整性保护过程示意图；
图25为本发明实施例中进行安全处理的信息传输实施环境示意图；
图26为本发明实施例中信息安全处理中的密钥处理实施环境示意图；
图27为本发明实施例中信息发送装置一结构示意图；
图28为本发明实施例中信息发送装置二结构示意图；
图29为本发明实施例中信息接收装置结构示意图；
图30为本发明实施例中第一基站结构示意图；
图31为本发明实施例中第二基站结构示意图；
图32为本发明实施例中终端设备结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
应理解，本发明的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)等。
还应理解，在本发明实施例中，用户设备(User Equipment，UE)包括但不限于移动台(Mobile Station，MS)、移动终端(Mobile Terminal)、移动电话(Mobile Telephone)、 手机(handset)及便携设备(portable equipment)等，该用户设备可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，例如，用户设备可以是移动电话(或称为“蜂窝”电话)、具有无线通信功能的计算机等，用户设备还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置。
在本发明实施例中，基站(例如，接入点)可以是指接入网中在空中接口上通过一个或多个扇区与无线终端通信的设备。基站可用于将收到的空中帧与IP分组进行相互转换，作为无线终端与接入网的其余部分之间的路由器，其中接入网的其余部分可包括网际协议(IP)网络。基站还可协调对空中接口的属性管理。例如，基站可以是GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB)，还可以是LTE中的演进型基站(NodeB或eNB或e-NodeB，evolutional Node B)，本发明并不限定。
下面结合附图对本发明的具体实施方式进行说明。
发明人在发明过程中注意到，基于现有eMBMS技术实现的应用业务或场景时延不能满足要求，以V2X业务为例，其总时延为160ms的原因如下：
图1为eMBMS系统架构示意图，如图所示，eMBMS系统架构中主要包括广播组播业务中心(broadcast multicast service center，BMSC)、MBMS网关(MBMS Gateway，MBMS GW)、移动性管理实体(Mobility Management Entity，MME)、多小区多播协调实体(Multi-cell/multicast Coordination Entity，MCE)、演进基站(eNB)，其中：
BMSC：提供MBMS业务和发起MBMS承载建立过程。
MBMS GW：采用IP多播方式向各eNB发送MBMS业务数据。与MME交互MBMS会话控制信令。
MME：根据从MBMS GW收到的会话控制信令，通过M3接口与MCE通信实现MBMS会话控制。
MCE：负责各eNB MBMS资源的分配。生成MBMS业务通知信息发送给eNB。
eNB：将从BMSC上接收的MBMS业务数据包，在MCE指定的资源按设定的时间以广播方式发送。将从MCE接收的MBMS业务通知信息以广播方式发送。
基于eMBMS实现V2X通信得方案主要部分如下：
图2为基于eMBMS实现V2X通信的网络结构示意图，如图所示，基于eMBMS实现V2X通信的方式为：
车辆UE(图中用以示意的为UE1、UE2)采用单播(unicast)方式上报道路安全相关信息如本车的位置、速度、加速度、行驶路径及获知的道路环境信息等，eNB将车辆上报的道路安全相关信息经服务网关(Serving Gateway，S-GW)、分组数据网络网关(PDN Gateway，P-GW)等实体发送给BMSC，BMSC再将各车辆上报的道路安全相关信息采用 MBSFN方式发送给各车辆周围相关的小区。
在上述方式下，发送车辆上报道路安全信息到其周围的车辆接收到其发送的道路安全信息的时延分析见下：
表1：基于eMBMS实现V2X通信端到端总时延
数据传输阶段 时延(ms)
发送车辆UE→eNB 10
eNB→S-GW/PGW→BMSC 20
BMSC→eNB 40
MSP 80
eNB→接收车辆UE 10
总时延 160
其中：MSP为多播信道调度周期(Multicast Channel Scheduling Period)。
可见，基于现有eMBMS技术实现的V2X总时延为160ms，而这显然不能满足支持道路安全应用的时延要求。
发明人注意到：
针对在一定区域内进行信息交互的情景，可以减少在网络侧产生的时延，具体的，可以尽量利用接入网的的特点来减少时延。例如，在LTE系统中，eNB间可以通过X2接口或者S1接口直接与其他eNB通信，实现无缝的无线资源管理和协同数据传输。
下面进行具体说明，一种是基于X2接口的技术方案，一种是基于S1接口的技术方案。
一、基于X2接口的技术方案。
当相邻的eNB之间存在X2接口时，为了减少160ms的时延，本发明实施例中将提供基于X2接口的技术方案，也即：为了降低基于eMBMS技术实现V2X的端到端时延，提出了一种增强的基于eMBMS实现V2X通信方案，该方案构思主要为：
图3为增强的基于eMBMS实现V2X通信的网络结构示意图，如图所示，在该结构中基于X2接口的技术方案主要为：
车辆UE采用单播(unicast)方式向服务小区上报道路安全相关信息，如本车的位置、速度、加速度、行驶路径及获知的道路环境信息等，在本方案中，eNB将其下各支持(特定)V2X业务的小区中车辆上报的道路安全相关信息通过X2接口与相邻eNB进行交互，相邻eNB下的小区采用MBSFN方式将所属MBSFN区域数据源小区下收集的道路安全信息发送给UE。
按上述方案，发送车辆上报道路安全信息到其周围的车辆接收到其发送的道路安全信息的时延分析见下：
表2：基于eMBMS实现V2X通信端到端总时延
数据传输阶段 时延(ms)
发送车辆UE→eNB 10
eNB→eNB 10
MSP 80
eNB→接收车辆UE 10
总时延 110
与表1数据相比可以看出，扣除MSP的耗时后，时延由表1指代方案的80ms降低至表2指代的增强方案的30ms，可见，在本方案基础上降低了总时延。进一步的，如果通过降低MSP的时间，如降低到60ms，便可以将UE间道路安全信息交互的总时延降低到100ms以下。
二、基于S1接口的技术方案。
当相邻的eNB间不存在X2接口时，eNB将其下各支持(特定)V2X业务的小区中车辆上报的道路安全相关信息通过S1接口转发方式与相邻eNB间进行交互，相邻eNB下的小区采用MBSFN方式将所属MBSFN区域数据源小区下收集的道路安全信息发送给UE。
上述方式，发送车辆上报道路安全信息到其周围的车辆接收到其发送的道路安全信息的时延分析见下：
表3采用S1接口进行交互时基于eMBMS实现V2X通信端到端总时延
数据传输阶段 时延(ms)
发送车辆UE→eNB 10
eNB→S-GW 10
S-GW→eNB 10
MSP 80
eNB→接收车辆UE 10
总时延 120
与表1数据相比可以看出，扣除MSP的耗时后，时延由表1指代方案的80ms降低至表3指代的增强方案的60ms，可见，在本方案基础上降低了总时延。进一步的，如果通过降低MSP的时间，如降低到50ms，便可以将UE间道路安全信息交互的总时延降低到100ms以下。
基于上述构思，本发明实施例分别提供了在基站上实现该构思的方案如下：
方案中，第一基站为接收各终端设备上报的信息的基站，第一小区是归属于第一基站的小区，各终端设备是第一小区所辖的终端设备；
第一基站在收到信息后发送给第二基站，第二基站可以有多个，但是其要求为：归属于第二基站的第二小区与第一小区属于同一MBSFN区域；
对于第二小区，还需要说明的是，也有归属于第一基站的第二小区，同样，第二小区的要求为与第一小区属于同一MBSFN区域，也即，与第一小区属于同一MBSFN区域的其他小区，在实施例中称为第二小区。
随后，在第一基站以及第二基站在相同的时间与频率资源上向第一小区、第二小区所辖的各终端设备下发信息，这样，在同一MBSFN区域内的终端设备都同时接收到了来自同一个小区的终端设备上报的信息。
实施中，还需说明的是，终端设备并不直接归属基站，而是归属于逻辑上划分的小区，需要说明的原因是本方案中的MBSFN区域是由小区组成的，上述描述是为了便于理解仅从物理上进行的说明。下文还会对小区的实施进行说明。同时，终端设备不仅包括移动终端设备，也包括各种用于MTC中的终端设备，例如用于实时云计算、虚拟现实、在线游戏、远程医疗、智能交通、智能电网、远程实时控制等业务中的传感器、数据采集装置等。
实施例中，将主要以V2X业务为例进行说明，以终端设备的典型代表UE作为终端设备、以基站的典型代表eNB作为基站来进行说明，而交互的信息则是V2X业务中的V2X信息。容易知道，上述方案中，在实例中则可以为：
第一基站为接收各UE在V2X业务中上报的V2X信息的基站，各UE是第一小区所辖的UE，第一小区是归属于第一基站的小区；
第一基站在收到V2X信息后发送给第二基站，第二基站可以有多个，但是其要求为：归属于第二基站的第二小区与第一小区属于同一MBSFN区域；
随后，在第一基站以及第二基站在相同的时间与频率资源上向第一小区、第二小区所辖的各UE下发V2X信息，这样，在同一MBSFN区域内的UE都同时接收到了来自同一个小区的UE上报的V2X信息。
则本发明实施例中提供的信息发送方案如下：
图4为信息发送方法一实施流程示意图，如图所示，可以包括如下步骤：
步骤401、接收第一小区所辖的各终端设备上报至第一基站的信息，所述第一小区是归属于第一基站的小区；
步骤402、将该信息分发给与第一小区属于同一MBSFN区域的各第二小区归属的各第二基站，所述信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发送；
实施中，也即将信息分发给以第一小区作为数据源小区的MBSFN区域的各第二小区 归属的各第二基站，其中，数据源小区的概念将会在下面进行说明。
步骤403、在第一基站的第一小区以及归属于第一基站的与第一小区属于同一MBSFN区域的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
实施中，也即是在归属于第一基站的与属于以第一小区作为数据源小区的MBSFN区域的第二小区中发送信息，其中，数据源小区的概念将会在下面进行说明。
具体实施中，若以V2X业务、V2X信息为例，容易知道，上述方案中，在实例中则V2X业务中的信息发送方法一可以包括如下步骤：
1、接收第一小区所辖的各UE在V2X业务中上报至第一基站的V2X信息，所述第一小区是归属于第一基站的小区；
2、将V2X信息分发给与第一小区属于同一MBSFN区域的各第二小区归属的各第二基站，所述V2X信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发送；
3、在第一基站的第一小区以及归属于第一基站的与第一小区属于同一MBSFN区域的第二小区中，在与MBSFN区域对应的时间与频率资源上发送V2X信息。
图5为信息发送方法二实施流程示意图，如图所示，可以包括如下步骤：
步骤501、接收第一基站发送给第二基站的来自第一小区的信息，所述第一小区是归属于第一基站的小区；
步骤502、确定与第一小区属于同一MBSFN区域的第二小区，所述第二小区是归属于第二基站的小区；
实施中，也即确定属于以第一小区作为数据源小区的MBSFN区域的各第二小区，其中，数据源小区的概念将会在下面进行说明。
步骤503、在第二基站以与MBSFN区域对应的时间与频率资源发送信息。
具体实施中，若以V2X业务、V2X信息为例，容易知道，上述方案中，在实例中则V2X业务中的信息发送方法二可以包括如下步骤：
1、接收第一基站发送给第二基站的来自第一小区的V2X信息，所述第一小区是归属于第一基站的小区；
2、确定与第一小区属于同一MBSFN区域的第二小区，所述第二小区是归属于第二基站的小区；
3、在第二基站以与MBSFN区域对应的时间与频率资源发送V2X信息。
图6为信息接收方法实施流程示意图，如图所示，可以包括如下步骤：
步骤601、接收基站发送的信息；
步骤602、根据接收信息的时间与频率资源确定对应的MBSFN区域；
步骤603、按与该MBSFN区域对应的规则处理信息。
具体实施中，在接收到基站发送的信息后，面对的是接收到若干信息的情况下；那么在步骤602中，首先可以确定各MBSFN区域对应的时间与频率资源的对应关系，例如，可以根据接收的系统信息来确定各MBSFN区域对应的时间与频率资源的对应关系；接着，再通过接收到的信息的时间与频率资源结合上述的对应关系便可确定对应的MBSFN区域；然后，在步骤603中，即可按与各MBSFN区域对应的规则处理在各MBSFN区域对应的时间与频率资源上接收的信息。容易理解，针对每一条接收到的信息，便是根据接收信息的时间与频率资源确定对应的MBSFN区域，然后按与该MBSFN区域对应的规则处理信息即可。
具体实施中，若以V2X业务、V2X信息、确定对应关系是通过系统信息获知的为例，容易知道，上述方案中，在实例中则V2X业务中的信息接收方法可以包括如下步骤：
接收基站发送的V2X信息；
根据接收的系统信息来确定各支持V2X业务的MBSFN区域以及时间与频率资源的对应关系，再根据接收到的信息的时间与频率资源结合对应关系确定对应的MBSFN区域；
按与各支持MBSFN区域对应的规则处理在各支持V2X业务的MBSFN区域对应的时间与频率资源上接收的V2X信息。
本例中，对应的规则即为V2X信息的处理规则，但并不仅限于此，该规则是预设的，是可以根据需要制定的，例如，可以为完整性保护处理的规则。只要该规则是与MBSFN区域相对应的即可，例如，在该规则是完整性保护及验证的处理规则时，MBSFN区域编号为MBSFN区域1，则按与MBSFN区域1相对应的密钥(通常为公钥)进行完整性验证。
在步骤403、步骤503、步骤601，在以与MBSFN区域对应的时间与频率资源发送、接收信息时，对于收发的信息的MBSFN区域对应的时间与频率资源，可以是预先设定的，例如：基站需要在分别为MBSFN区域2和MBSFN区域3发送信息，设定MBSFN区域2和MBSFN区域3占用的子帧分别为每个无线帧中的子帧7和子帧8，则，在确定需要发送的V2X信息属于MBSFN区域2的时，按照预先设定的子帧7收发，属于MBSFN区域3则按照子帧8收发。各基站之间获知MBSFN区域极其对应的时间与频率资源是本领域技术人员容易知悉的，且，凡是可以使各基站均能获知该对应关系的技术方式也都是可以在本实施例中采用的。
实施中，在以与MBSFN区域对应的时间与频率资源收发信息时，可以采用MBMS方式，也可以采用其他的通信方式发送，例如通过单播方式、设备到设备(Device-to-Device，D2D)等方式，只要能够实现将信息发送到终端设备即可。
为从整体理解本发明实施例提供的技术方案，下面给出第一基站、第二基站、终端设 备之间的实施流程。
图7为信息收发方法实施流程示意图，如图所示，其中，第一小区是归属于第一基站的小区，信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发送，所述第二小区是归属于第二基站的小区，可以包括：
步骤701、接收第一小区所辖的各终端设备上报至第一基站的信息；
步骤702、将该信息分发给与第一小区属于同一MBSFN区域的各第二小区归属的各第二基站，转入步骤709；
步骤703、接收第一基站发送给第二基站的来自第一小区的信息，所述第一小区是归属于第一基站的小区；
步骤704、确定与第一小区属于同一MBSFN区域的第二小区；
步骤705、在第二基站的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息；
步骤706、第二基站的第二小区中的终端设备接收第二基站发送的信息；
步骤707、根据接收的第二基站的系统信息确定各MBSFN区域对应的时间与频率资源；
步骤708、按各MBSFN区域对应的规则处理在各MBSFN区域对应的时间与频率资源上接收的信息；
步骤709、在第一基站的第一小区以及归属于第一基站的与第一小区属于同一MBSFN区域的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息；
步骤710、第一基站的第一小区、第二小区中的终端设备接收第一接收基站发送的信息；
步骤711、根据接收的第一基站的系统信息确定MBSFN区域对应的时间与频率资源；
步骤712、按与该MBSFN区域对应的规则处理在该MBSFN区域对应的时间与频率资源上接收的信息。
需要说明的是，“指定的终端设备”可以是一类终端设备如支持V2X业务的终端设备或支持某些种类V2X业务(如道路安全相关的V2X业务等)的终端设备，也可以是多类终端设备如支持V2X业务或M2M业务的终端设备，还可以所有能够接收网络侧发送业务的终端设备。
为便于描述以及更好的理解本发明实施例中提供的技术方案，下面对涉及到的“源小区”、“源基站”、“协同小区”、“同一MBSFN区域”等特征的定义、实施方式等说明。说明中，在需要以实例说明以便于理解时，将以V2X业务、UE、V2X信息为例进行说明。
实施例中，一个MBSFN区域包括一个第一小区以及至少一个第二小区。其中，对于 小区而言，在基站采用单天线或多天线实现对特定区域的无线信号覆盖时，这些特定区域被称为小区，小区这一概念也常常指为这一特定覆盖区域内的用户终端提供服务的包含基站软件和硬件子系统在内的逻辑实体。
第一小区是其所辖的各UE会在V2X业务中，将V2X信息上报至第一基站的小区，则，实施例中的第一小区称为“源小区”，第一基站称为“源基站”。
其中，一个MBSFN区域只有一个第一小区，且，一个MBSFN区域只有一个对应的时间与频率资源，在实际场景中一个MBSFN区域可以对应多份时间与频率资源，但是，在同一时间，MBSFN区域对应的时间与频率资源是唯一的。
一个MBSFN区域中则会有若干个第二小区，这些第二小区可以是归属于其他基站的，当然，也可以是归属于第一基站的，实施例中的第二小区称为“协同小区”。
“源”是指产生数据的源，该源产生的数据即为该MBSFN区域发送的数据，“协同”也即协助发送该源产生的数据。实施例中的数据也即“V2X信息”。
由此，在实施中，V2X信息分发的基站，是属于以第一小区为数据源小区的MBSFN区域的各第二小区归属的各第二基站，同时，以第一小区为数据源小区的MBSFN区域，是指该MBSFN区域对应的发送数据由第一小区产生。
那么，V2X信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发送，具体为：
V2X信息将在属于以第一小区为数据源小区的MBSFN区域的各第二小区归属的各第二基站下的各属于以第一小区为数据源小区的MBSFN区域的各第二小区中，在与所述以第一小区为数据源小区的MBSFN区域对应的时间与频率资源上发送。
如果，在第一基站所属的小区中存在第二小区，那么在第一基站的第一小区和各第二小区中，在与MBSFN区域对应的时间与频率资源上发送V2X信息，具体为：
在第一基站的第一小区和各属于以第一小区为数据源小区的MBSFN区域的第二小区中，在与所述以第一小区为数据源小区的MBSFN区域对应的时间与频率资源上发送V2X信息。
在方案中，在基站以及相邻的基站上，在相同的时间与频率资源上以MBMS方式向各UE下发V2X信息，这样的目的是保证在同一MBSFN区域内的UE都能够同时接收到来自同一个小区的UE上报的V2X信息。而V2X业务的目的是使相关区域内的UE能够及时的获取到该V2X信息，例如，保证与上报V2X信息的UE在300米范围内的所有UE都能接收到该V2X信息，将有必要使得这些UE都与上报V2X信息的UE处于同一MBSFN区域，将该UE上报的V2X信息作为该MBSFN区域的数据源下发。换句话说，通过控制MBSFN区域的小区组成，即可保证V2X信息的下发范围。由于数据的处理过程是根据MBSFN区域来进行的，而MBSFN区域是由小区构成的，这也就意味着确定同一MBSFN 区域的组成小区是实施的关键部分，因此下面对小区以及各小区如何组成MBSFN区域进行说明，以便更好地理解本发明实施例提供的技术方案的实施。
图8为MBSFN区域构成示意图，图9为高速场景中MBSFN区域构成示意图，图10为小区与MBSFN区域间关系示意图，图11为高速公路场景下小区与MBSFN区域间关系示意图，如图所示：
增强的基于eMBMS实现V2X通信方案中，通常情况下一个MBSFN区域由相邻的多个小区构成如图8所示MBSFN区域1由Cell 1-Cell 7构成，每个MBSFN区域中存在一个数据源小区，该小区负责产生本MBSFN区域中各小区以MBSFN方式发送的数据内容，并数据内容分发给本MBSFN区域内的其他小区(同一MBSFN区域中的小区可以属于不同的eNB)，如在图8中可以选择Cell 1作为该MBSFN区域的数据源小区。在不同的场景中，一个MBSFN区域中包含的小区数可以根据实际环境进行设置，如在高速公路环境中MBSFN区域可以沿高速公路进行设置，图9所示的MBSFN区域由沿高速公路分布的3个小区构成，Cell 1作为该MBSFN区域的数据源小区。
为了实现无缝的V2X通信，需要以每个小区作为源小区创建相互重叠的不同的MBSFN区域。图10、11中，是以带有编号的圆圈来表示不同的MBSFN区域的，每个小区中间位置处圆圈内的编号为以该小区作为数据源小区的MBSFN区域的编号，如果多个小区中都有同一编号的圆圈时，则表示这些小区属于同一个以该编号标识的MBSFN区域。
如图10所示，当系统中的每个MBSFN区域由一个小区及其周围的6个小区构成、每个小区都存在一个以自己为中心的一个MBSFN区域时，每个小区将会由7个MBSFN区域覆盖(如Cell 1-Cell 7，其他的小区因处于边缘，图中没有画出，所以没有被7个MBSFN区域覆盖)。如图11所示，当在高速公路场景中，每个MBSFN区域由一个小区及其周围的2个小区构成、每个小区都存在一个以自己为中心的一个MBSFN区域时，每个小区将会由3个MBSFN区域覆盖(如Cell 1、Cell 2、Cell 3、Cell 5，其他的Cell4、Cell6因处于边缘，图中没有画出，所以没有被3个MBSFN区域覆盖)。
在LTE系统中，不同MBSFN区域中的数据占用不同的子帧发送，因此不同MBSFN区域中的数据发送不存在相互干扰。
在步骤402的实施中，将会涉及第一基站与第二基站之间信息的传输，也即：将信息分发给与第一小区属于同一MBSFN区域的各第二小区归属的各第二基站。下面将首先对这种情形下的信息分发的实施进行说明。
在上述说明过程中，是分别从第一基站与第二基站侧的实施进行说明，但这并不意味着二者必须配合实施，实际上，当第一基站与第二基站分开实施时，其也各自解决第一基站与第二基站侧的问题，只是二者结合使用时，会获得更好的技术效果。还需说明的是，对于同一基站，由于在不同的MBSFN区域中解决不同的问题，因此其可能同时需要实施 第一基站以及第二基站的方案，第一基站、第二基站的称谓仅是为了更好的阐述本发明实施例中提供的方案，并不意味一个基站只能实施其中一个方案。
一、接入网节点间通过X2接口传输信息的实施。
针对接入网节点间采用X2接口进行的信息传输，在实施中：
在X2接口用户面可以提供eNB之间的用户数据传输功能。X2用户面(X2User Plane，X2-UP)的传送网络层基于因特网协议(Internet Protocol，IP)，用户数据报协议(User Datagram Protocol，UDP)/IP协议之上采用通用分组无线业务用户平面隧道协议(General Packet Radio Service Tunnelling Protocol for User Plane，GTP-U)来传输eNB之间的用户面数据。GTP-U协议利用隧道机制来提供承载用户数据包的业务，GPRS隧道协议(GPRS Tunnelling Protocol，GTP)包头中的隧道端标识符(Tunnel End Point Identifier，TEID)指示隧道-协议数据单元(Tunnelling Protocol Data Unit，T-PDU)所在的隧道。但现有协议中eNB间的X2用户平面传输只与切换有关，采用UE相关信令，建立无线接入承载(Radio access bearer，RAB)级的连接。
具体实施中，在第一基站侧，也即接收终端设备上报信息的基站侧，可以包括如下方式：
1、接收第一小区所辖的各终端设备上报至第一基站的信息，所述第一小区是归属于第一基站的小区；
2、将该信息通过X2接口分发给与第一小区属于同一MBSFN区域的各第二小区归属的各第二基站，所述信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发送，也即，将该信息通过X2接口分发给以第一小区作为数据源小区的MBSFN区域的各第二小区归属的各第二基站；
3、在第一基站的第一小区以及归属于第一基站的与第一小区属于同一MBSFN区域的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息，也即，在归属于第一基站的与属于以第一小区作为数据源小区的MBSFN区域的第二小区中发送信息。
相应的，在第二基站侧，也即接收相邻基站转发的信息的基站侧，可以包括如下方式：
1、接收第一基站通过X2接口发送给第二基站的来自第一小区的信息，所述第一小区是归属于第一基站的小区；
2、确定与第一小区属于同一MBSFN区域的第二小区，所述第二小区是归属于第二基站的小区，也即，确定属于以第一小区作为数据源小区的MBSFN区域的各第二小区；
3、在第二基站以与MBSFN区域对应的时间与频率资源发送信息。
在以V2X业务、UE为例时，为降低V2X时延提出的增强eMBMS方案中，由于MBSFN区域中除数据源小区外的其他小区只负责协同传输V2X数据，不需要知道该数据对应的 UE信息，也不需要知道数据的业务类型等，因此可以创建新的X2用户面数据通道用于eMBMS数据源小区向对应的MBSFN区域中的其他小区分发eMBMS数据。
实施中，在创建该X2用户面数据通道时，由上述原因可知，其既不需按现有协议在与切换有关时创建，也不需要仅在传输V2X信息时创建，而是可以根据实施需要在合适的时候创建，例如，可以预先创建该数据通道，在产生V2X信息、需要传输V2X信息时便可立即通过该数据通道传输，在V2X信息数量变化或者无V2X信息传输时，则可以通过更新、释放数据通道来进行通道的维护等处理。当然，也可以在需要传输V2X信息时去按需创建该数据通道。
实施中，涉及数据通道的实施主要的分别为：创建、更新、释放数据通道，则在该过程中，针对发送数据的第一基站与接收数据的第二基站之间，可以如下：
1、创建过程。
在第一基站上：
向第二基站分别发起X2接口数据通道的建立请求，对该第二基站发起的请求中包括以下内容的之一或者其组合：需与该第二基站建立的数据通道的资源要求信息、MBSFN区域标识信息、MBSFN区域数据源小区标识信息；
在该第二基站建立满足需求的X2接口数据通道后，从该数据通道向该第二基站发送信息。
在第二基站上：
接收第一基站发起的X2接口数据通道建立请求，所述请求中包括以下内容的之一或者其组合：对数据通道的资源要求信息、MBSFN区域标识信息、MBSFN区域数据源小区标识信息；
在根据第二基站的资源确定建立满足资源需求的X2接口数据通道后，从该数据通道接收第一基站发送的信息。
2、更新过程。
在第一基站上：
在确定数据通道的资源要求或其他需求(如MBSFN区域标识、MBSFN区域数据源小区标识)变化后，根据变化后的资源要求对建立该数据通道的第二基站发起该数据通道的更新请求；
在该第二基站更新数据通道配置满足变化后的资源需求后，从该数据通道向该第二基站发送信息。
在第二基站上：
接收第一基站发起的数据通道更新请求，所述请求中包括更新后的对数据通道的资源要求；
在根据第二基站的资源更新数据通道的配置以满足更新后的资源需求后，从该数据通道接收第一基站发送的信息。
3、释放过程。
在第一基站上：
在确定数据通道上没有信息发送需求时，对建立该数据通道的第二基站发起释放该数据通道的请求；
停止从该数据通道向该第二基站发送信息。
在第二基站上：
接收第一基站发起的释放数据通道的请求；
释放该数据通道，并停止从该数据通道接收第一基站发送的信息。
实施中，对于数据通道的更新以及释放，既可以是由第一基站发起的，也可以是由第二基站发起的，比如，当第二基站判断自身资源不足或者资源状态发生变化时，可以根据自身的需求发起更新或者释放请求。则实施中还可以如下：
根据第二基站的资源向第一基站发起数据通道更新请求，所述请求中包括更新后的对数据通道的资源要求；
或，根据第二基站的资源向第一基站发起释放数据通道的请求。
下面还将以实例对数据通道的创建、更新、释放的具体实施方式进行说明。
为了实现图3中所述的增强的基于eMBMS实现V2X通信，下面对数据通道的实施方案进行说明，该方案用于MBSFN区域的数据源小区向属于同一MBSFN区域但不属于同一eNB的其他小区分发MBMS数据，以便同一MBSFN区域中的所有小区能够在相同的时频资源上发送相同的数据内容。为了更形象的表述数据的传输交互，本处实施例说明中，采用的称呼是源eNB(Source eNB)与目标eNB(Target eNB)，而非第一基站与第二基站，可以理解，当第一基站向第二基站传输UE上报的信息时，第一基站为源eNB、第二基站为目标eNB。则实施时具体可以为：
源eNB根据获得的与目标eNB交互用户面数据所需的资源信息，在请求同一MBSFN区域中的其他小区(为方便描述，将这些小区称为对应MBSFN区域的协同小区)进行MBSFN方式发送的接口消息中将资源信息发送给同一MBSFN区域中的协同小区所属的eNB(目标eNB)。源eNB与目标eNB交互用户面数据所需的资源信息可以由源eNB根据其下各MBSFN区域对应的数据源小区中的UE个数、负荷信息等确定，也可以由高层节点指示(如MME、MCE等)，还可以由运行和维护(Operation and Maintenance，O&M)配置。一个eNB下可能有多个属于同一MBSFN区域的协同小区，这几个协同小区可以共用一个用户面通道，在进行用户面的数据传输时，可以在数据前加上协同小区ID进行标识。另外一个eNB下可能有多个对应不同MBSFN区域的数据源小区，可以为不同MBSFN 区域的数据源小区独立创建通道，也可以同时创建多个不同MBSFN区域的数据源小区对应的通道。
下面以实例来进行说明，其中，实施例A1将对MBSFN数据通道的建立进行说明，实施例A2将对数据通道的配置更新过程进行说明，实施例A3将对数据通道的去激活/释放过程进行说明。
实施例A1：建立MBSFN数据通道
实施例中，将以最常见的资源-带宽为例进行说明。则eNB1(Source eNB)根据其下各MBSFN区域的数据源小区内参与V2X的UE个数、负荷信息确定交互用户面数据所需带宽的等级，据此请求和eNB2(Target eNB)建立X2用户平面数据通道。图12为X2接口MBSFN数据传输通道建立信令交互过程实施流程示意图，如图所示，基本信令交互过程可以包括：
步骤1201、eNB1向eNB2发送MBSFN数据通道建立请求；
步骤1202、eNB2向eNB1发送MBSFN数据通道建立响应。
具体实施中，可以采用一条数据通道建立消息只建立一条数据通道的方式，也可以采用一条数据通道建立消息同时建立多个数据通道的方式。下面将分别说明一条数据通道建立消息只建立一条数据通道、以及一条数据通道建立消息同时建立多个数据通道的实施方式。
1、一条数据通道建立消息只建立一条数据通道
设：eNB1下包含两个小区cell 1和cell 2，以cell 1和cell 2作为数据源小区的MBSFN区域分别为MBSFN区域2和MBSFN区域3，MBSFN区域2和MBSFN区域3占用的子帧分别为每个无线帧中的子帧7和子帧8；
eNB2下包含一个小区cell3，eNB1的cell 1和eNB2的cell 3是地理位置相邻的小区，eNB2的cell 3属于以eNB1的cell 1为数据源小区的MBSFN区域2内，eNB2的cell 3需要在MBSFN区域2对应的子帧(每个无线帧中的子帧7)上发送与eNB1的cell 1中MBSFN区域2对应的子帧上完全相同的数据，MBSFN区域2对应的子帧上发送的数据由eNB1转发给eNB2。
以eNB1为Source eNB发起的针对cell 1为数据源小区的MBSFN区域2的X2接口数据传输通道建立过程如下：
(1)eNB1根据对应MBSFN区域2的数据源小区cell 1内参与V2X的UE个数、负荷信息确定交互用户面数据所需带宽的等级，据此请求建立X2用户平面数据通道。
(2)eNB2判断能够满足eNB1发送的通道建立要求时，根据请求消息中包含的带宽创建对应带宽的通道，并向eNB1发送通道建立响应。
实施中，Source eNB向Target eNB发送的请求消息内容可以包括：
Source eNB ID(即eNB1的ID)；
MBSFN区域标识(即MBSFN区域2对应的标识)；
MBSFN区域数据源小区标识(即cell 1标识)；
请求进行MBSFN协同传输的小区列表(即cell 3)；
Source eNB确定的用户面数据传输的需要的带宽信息等，例如：根据UE数量、当前的负荷状况等确定需要的带宽，如评估该通道需要支持50个UE以平均5kbps的速率进行道路安全数据分发，那么带宽可以设置为50*5＝250kbps。
Target eNB响应消息内容可以包括：
Source eNB ID(即eNB1的ID)；
Target eNB ID(即eNB2的ID)；
允许进行MBSFN协同传输的小区列表(即cell 3)；
用于数据传输的用户面数据通道标识；
可选地，携带不能用于MBSFN传输的小区列表和不能传输的原因。
通道建立完成后，eNB1可以使用上述创建的通道将MBSFN区域2数据源小区(即cell1)中收集的UE上报的道路安全数据转发给eNB2，由eNB2的cell3在设定的时频资源上按设定的规则发送。需要说明的是，当eNB1通过创建的通道将UE上报的道路安全数据转发给eNB2前，可以对数据包进行一些处理操作，如对UE上报的数据先进行完整性保护操作，然后封装在同步数据包中后再转发给eNB2，以便eNB2的cell3下UE接收到对应的数据包能够通过完整性验证来确保所接收数据的有效性，以及能够使eNB1下的cell1和eNB2下的cell3在相同的时频资源上以MBSFN的发送相同的数据。
实施中，当目标eNB不能满足数据通道建立要求时，向源eNB发送MBSFN数据通道建立失败消息，内容可以包括：
失败的原因。
2、一条数据通道建立消息同时建立多个数据通道
设：eNB1下包含两个小区cell 1和cell 2，以cell 1和cell 2作为数据源小区的MBSFN区域分别为MBSFN区域2和MBSFN区域3，MBSFN区域2和MBSFN区域3占用的子帧分别为每个无线帧中的子帧7和子帧8；
eNB2下包含一个小区cell3，eNB1的cell 1、cell 2和eNB2的cell 3均是地理位置相邻的小区，eNB2的cell 3既属于以eNB1的cell 1为数据源小区的MBSFN区域2内又属于以eNB1的cell 2为数据源小区的MBSFN区域3；eNB2的cell 3需要在MBSFN区域2对应的子帧(每个无线帧中的子帧7)上发送与eNB1的cell 1中MBSFN区域2对应的子帧上完全相同的数据，也需要在MBSFN区域3对应的子帧(每个无线帧中的子帧8)上发送与eNB1的cell 2中MBSFN区域3对应的子帧上完全相同的数据；MBSFN区域2和 MBSFN区域3对应的子帧上发送的数据由eNB1转发给eNB2。以eNB1为Source eNB发起的针对cell 1为数据源小区的MBSFN区域2的X2接口数据传输通道建立和针对cell 2为数据源小区的MBSFN区域3的X2接口数据传输通道建立过程如下：
(1)eNB1根据MBSFN区域2的数据源小区cell 1和MBSFN区域3的数据源小区cell 2内参与V2X的UE个数、负荷信息分别确定各自交互用户面数据所需带宽的等级，据此请求和建立各自针对X2用户平面数据通道。
(2)eNB2判断能够满足eNB1发送的通道建立请求或部分请求时，根据请求消息中包含的带宽创建对应带宽的通道，并向eNB1发送通道建立响应。这里设eNB2能够满足同时建立两个通道的请求。
实施中，Source eNB向Target eNB发送的请求消息内容可以包括：
Source eNB ID(即eNB1的ID)；
其中，针对MBSFN区域2的数据源小区cell 1的数据传输通道建立信息可以包括：
MBSFN区域标识(MBSFN区域2标识)；
数据源小区标识(即cell 1标识)；
请求进行MBSFN协同传输的小区列表(即cell 3)；
用于数据转发的用户面数据通道标识；
Source eNB确定的用户面数据传输的需要的带宽信息等，例如：根据UE数量、当前的负荷状况等确定需要的带宽，如评估该通道需要支持30个UE以平均5kbps的速率进行道路安全数据分发，那么带宽可以设置为30*5＝150kbps。
其中，针对MBSFN区域3的数据源小区cell 2的数据传输通道建立信息可以包括：
MBSFN区域标识(MBSFN区域3标识)；
数据源小区标识(即cell 2标识)；
请求进行MBSFN协同传输的小区列表(即cell 3)；
用于数据转发的用户面数据通道标识；
Source eNB确定的用户面数据传输的需要的带宽信息等，例如：根据UE数量、当前的负荷状况等确定需要的带宽，如评估该通道需要支持50个UE以平均5kbps的速率进行道路安全数据分发，那么带宽可以设置为50*5＝250kbps。
Target eNB响应消息内容则可以包括：
Source eNB ID(即eNB1的ID)；
Target eNB ID(即eNB2的ID)；
其中，针对MBSFN区域2的数据源小区cell 1的数据传输通道响应信息可以包括：
允许进行MBSFN协同传输的小区列表(即cell 3)；
用于数据传输的用户面数据通道标识；
可选地，携带不能用于MBSFN传输的小区列表和不能传输的原因；
其中，针对MBSFN区域3的数据源小区cell 2的数据传输通道响应信息可以包括：
允许进行MBSFN协同传输的小区列表(即cell 3)；
用于数据传输的用户面数据通道标识；
可选地，携带不能用于MBSFN传输的小区列表和不能传输的原因。
实施中，通道建立完成后，eNB1可以使用上述创建的两个通道分别将MBSFN区域2数据源小区(即cell1)和MBSFN区域3的数据源小区cell 2中收集的UE上报的道路安全数据转发给eNB2，由eNB2的cell3在设定的时频上按设定的规则分别发送MBSFN区域2数据源小区(即cell 1)和MBSFN区域3的数据源小区cell 2生成的数据。需要说明的是，当eNB1通过创建的通道将UE上报的道路安全数据转发给eNB2前，可以对数据包进行一些处理操作，如对UE上报的数据先进行完整性保护操作，然后封装在同步数据包中后再转发给eNB2，以便eNB2的cell3下UE接收到对应的数据包能够通过完整性验证来确保所接收数据的有效性，以及能够使eNB1下的cell1、cell2分别和eNB2下的cell3在相同的时频资源上以MBSFN的发送相同的数据。
实施中，当目标eNB不能满足数据通道建立要求时，向源eNB发送MBSFN数据通道建立失败消息，内容可以包括：
不能建立的数据通道列表，及建立失败的原因。
实施例A2：更新数据通道配置
实施例中，将以最常见的资源-带宽为例进行说明。则本实施例描述的情况如：当各MBSFN区域的数据源小区中的UE数量信息、负荷信息、MBSFN区域中包含的小区列表发生改变时，需要将对应数据通道的配置更新。图13为X2接口MBSFN数据传输通道配置更新过程实施流程示意图，如图所示，基本信令交互过程可以包括：
步骤1301、eNB1向eNB2发送MBSFN数据通道更新请求；
步骤1302、eNB2向eNB1发送MBSFN数据通道更新确认。
具体实施中，可以采用一条数据通道更新消息只更新一条数据通道的方式，也可以采用一条数据通道更新消息同时更新多个数据通道配置信息的方式。下面将分别说明一条数据通道更新消息只更新一条数据通道、以及一条数据通道更新消息同时更新多个数据通道的实施方式。
1、一条数据通道更新消息只更新一条数据通道
设：eNB1下包含两个小区cell 1和cell 2，以cell 1和cell 2作为数据源小区的MBSFN区域分别为MBSFN区域2和MBSFN区域3，MBSFN区域2和MBSFN区域3占用的子帧分别为每个无线帧中的子帧7和子帧8；
eNB2下包含一个小区cell3，eNB1的cell 1和eNB2的cell 3是地理位置相邻的小区， eNB2的cell 3属于以eNB1的cell 1为数据源小区的MBSFN区域2内，eNB2的cell 3需要在MBSFN区域2对应的子帧(每个无线帧中的子帧7)上发送与eNB1的cell 1中MBSFN区域2对应的子帧上完全相同的数据，MBSFN区域2对应的子帧上发送的数据由eNB1转发给eNB2。eNB1和eNB2间已经创建了MBSFN数据传输通道(通道标识为：00000010)，用于eNB1将MBSFN区域2的数据源小区(eNB1的cell 1)生成的数据转发给eNB2，由eNB2下的cell3采用MBSFN方式发送。
设eNB2下增加了一个新小区cell4，cell4也被配置属于MBSFN区域2，eNB1需要向eNB2发起数据通道配置更新过程。eNB2判断能够满足eNB1发送的通道配置更新要求时，根据请求消息中包含的更新信息对通道配置进行更新，并向eNB1发送通道更新确认。
则，实施中，Source eNB(eNB1)向Target eNB(eNB2)发送的更新请求消息内容可以包括：
请求更新用户面数据通道标识；
MBSFN协同传输的小区列表(cell3、cell4)；
Source eNB确定的用户面数据传输的需要的带宽信息(可更新，可选)；
Target eNB响应消息内容可以包括：
允许进行MBSFN协同传输的小区列表(cell3、cell4)；
不能用于MBSFN传输的小区列表和不能传输的原因(可选)。
实施中，当目标eNB不能满足数据通道更新要求时，向源eNB发送MBSFN数据通道更新失败消息，内容可以包括：
失败的原因。
2、一条数据通道更新消息同时更新多个数据通道
设：eNB1下包含两个小区cell 1和cell 2，以cell 1和cell 2作为数据源小区的MBSFN区域分别为MBSFN区域2和MBSFN区域3，MBSFN区域2和MBSFN区域3占用的子帧分别为每个无线帧中的子帧7和子帧8；
eNB2下包含一个小区cell3，eNB1的cell 1、cell 2和eNB2的cell 3均是地理位置相邻的小区，eNB2的cell 3既属于以eNB1的cell 1为数据源小区的MBSFN区域2内又属于以eNB1的cell 2为数据源小区的MBSFN区域3；eNB2的cell 3需要在MBSFN区域2对应的子帧(每个无线帧中的子帧7)上发送与eNB1的cell 1中MBSFN区域2对应的子帧上完全相同的数据，也需要在MBSFN区域3对应的子帧(每个无线帧中的子帧8)上发送与eNB1的cell 2中MBSFN区域3对应的子帧上完全相同的数据；MBSFN区域2和MBSFN区域3对应的子帧上发送的数据由eNB1转发给eNB2。eNB1和eNB2间已经创建了两个MBSFN数据传输通道(通道标识分别为：00000010、00000011)，分别用于eNB1将MBSFN区域2的数据源小区(eNB1的cell 1)和MBSFN区域3的数据源小区(eNB1 的cell 2)生成的数据转发给eNB2，由eNB2下的cell3采用MBSFN方式发送。
设，随着eNB1的cell1和cell2覆盖下的车辆数增加，eNB1判断需要对两个通道对应的带宽都需要增加，eNB1需要向eNB2数据通道更新过程。eNB2判断能够满足eNB1发送的通道更新要求时，根据请求消息中包含的更新信息对通道配置进行更新，并向eNB1发送通道更新确认。
则，实施中，Source eNB向Target eNB发送的请求消息内容可以包括：
(1)请求更新的用户面数据通道1相关内容：
请求更新的用户面数据通道1标识(00000010)；
MBSFN协同传输的小区列表(可更新，可选)；
Source eNB确定的用户面数据传输的需要的带宽信息(例如是根据UE数量、当前的负荷状况重新计算的带宽)。
(2)请求更新的用户面数据通道2相关内容：
请求更新的用户面数据通道2标识(00000011)；
MBSFN协同传输的小区列表(可更新，可选)；
Source eNB确定的用户面数据传输的需要的带宽信息(例如是根据UE数量、当前的负荷状况重新计算的带宽)。
在更新更多通道内容时，可按上述方式增加内容。
Target eNB更新确认消息内容包括：
(1)针对请求更新的用户面数据通道1的响应信息：
请求更新的用户面数据通道1标识(00000010)；
允许进行MBSFN协同传输的小区列表(可选)；
不能用于MBSFN传输的小区列表和不能传输的原因(可选)。
(2)针对请求更新的用户面数据通道2的响应信息：
请求更新的用户面数据通道1标识(00000011)；
允许进行MBSFN协同传输的小区列表(可选)；
不能用于MBSFN传输的小区列表和不能传输的原因(可选)。
在更新更多通道内容时，可按上述方式增加内容。
实施中，当目标eNB不能满足数据通道更新要求时，向源eNB发送MBSFN数据通道更新失败消息，内容包括：
不能更新的数据通道列表，及更新失败的原因。
实施例A3：去激活/释放数据通道
本实施例描述的情况如：如果Source eNB决定不再需要MBSFN传输，应该请求Target eNB释放预留的资源和释放用户面数据通道。图14为X2接口MBSFN数据传输通道去激 活/释放过程实施流程示意图，如图所示，基本信令交互过程可以包括：
步骤1401、eNB1向eNB2发送MBSFN数据通道去激活/释放消息。
实施中，数据通道去激活或释放消息中可以去激活或释放多个通道，内容可以如下：
去激活/释放X2MBSFN通道的eNB ID，
去激活/释放的用户面数据通道标识或标识列表。
二、终端设备与接入网节点间信息传输的实施。
在解决终端设备与接入网节点间信息传输时，可以按如下方式实施：
图15为EPS承载构成示意图，如图所示，LTE系统中，应用层的业务最终体现为用户平面数据，使用演进分组系统(Evolved Packet System，EPS)承载进行传输，EPS承载由无线承载(Data Radio Bearer，RB)、S1承载、S5/S8承载组成。伴随着业务的建立、修改和释放，相应的EPS承载也要动态地进行建立、修改和释放操作，EPS承载的空口部分及数据无线承载(Data Radio Bearer，DRB)的管理由接入网节点(如eNB)通过无线资源控制(Radio Resource Control，RRC)连接重配置过程完成。DRB与EPS承载是一一对应的，EPS承载由核心网移动性管理实体(Mobility Management Entity，MME)等实体进行控制，接入网节点RRC对DRB的管理源自MME向接入网节点发送的S1AP控制消息。LTE系统允许在切换过程中实施对DRB的(部分)接纳，目标小区可以仅接纳UE的部分DRB。
为了实现增强的基于eMBMS的通信需要对现有的承载管理进行修改，以V2X业务、UE为例，需要使网络侧能够识别UE发起的是V2X业务，从而对UE上报的V2X业务建立相应的承载以及配置其他处理。可以如下：
图16为信息上报方法实施流程示意图，如图所示，在终端设备上，可以包括：
步骤1601、向接入网节点发送指示信息，所述指示信息用以指示终端设备将上报的信息是将在与MBSFN区域对应的时间与频率资源上发送的信息；
步骤1602、接收接入网节点的通知，所述通知携带有上报信息所使用的无线承载的配置信息；
步骤1603、在终端设备收集信息后，根据配置信息在所述无线承载上上报信息。
图17为承载建立方法实施流程示意图，如图所示，针对终端设备的指示，相应的，在网络侧设备可以执行如下步骤：
步骤1701、接收接入网节点建立业务承载的请求信息，所述业务承载用于传输终端设备将上报的信息，所述信息是将在与MBSFN区域对应的时间与频率资源上发送的信息；
步骤1702、建立业务承载，所述业务承载包括终端设备向接入网节点上报信息所用的无线承载；
步骤1703、通知接入网节点建立的业务承载的配置信息。
具体实施中，该网络测设备可以具体由MME来实施，事实上，只要是能够实现为基站之间的信息传输分配承载资源的网络侧设备都可以实现该方案。
图18为接入网节点的信息接收方法实施流程示意图，在接入网节点，例如在第一基站侧，也即接收终端设备上报信息的基站侧，在建立用以传输上报信息的无线资源承载上，可以执行如下步骤：
步骤1801、接收终端设备发送的指示信息，所述指示信息用以指示终端设备将上报的信息是将在与MBSFN区域对应的时间与频率资源上发送的信息；
步骤1802、请求网络侧设备为终端设备将上报的信息建立业务承载；
步骤1803、接收网络侧设备建立的业务承载的配置信息，并根据所述配置信息为终端设备将上报的信息配置无线承载；
步骤1804、通知终端设备在配置的无线承载上上报信息，并在配置的无线承载上接收终端设备上报的信息。
在上述说明过程中，是分别从终端设备、网络侧设备、接入网节点(第一基站)的实施进行说明，但这并不意味着它们必须配合实施，实际上，当它们分开实施时，其也各自解决终端设备、网络侧设备、接入网节点的问题，只是它们结合使用时，会获得更好的技术效果。
具体实施中，以V2X业务、UE、V2X信息实施为例，也即，需要在属于同一MBSFN区域的各小区中在与所述MBSFN区域对应的时间与频率资源上发送的信息是V2X信息，则为：UE向网络侧节点发送V2X相关指示信息，网络侧节点(包括接入网节点与网络侧设备)根据UE发送的指示为UE建立传输V2X业务的承载和配置相应的资源，并可以为该承载上的数据设置特殊的操作。具体过程可以如下：
(1)UE向网络侧节点发送V2X相关指示信息在实施中可以如下：
网络侧节点包括eNB、中继(Relay)、MME、家庭演进基站(Home e NodeB，HeNB)等现有节点，也包括后续引入的接入网节点。UE向网络侧节点发送V2X业务相关指示信息时，可以直接在RRC信令(如RRC连接建立请求消息、RRC连接建立完成消息、上行信息传输消息)中携带V2X业务相关指示信息，也可以在非接入层(Non Access Stratum，NAS)信令中携带V2X业务相关指示信息，NAS信令一般可以包括如下信令：如Attach Request(附着请求)、服务请求(service request)、扩展的服务请求(Extended service request)、承载资源分配请求(bearer resource allocation request)、承载资源修改请求(Bearer resource modification request)等。
V2X业务相关指示信息可以为指示V2X业务对应的服务质量(Quality of Service，QoS)参数信息、可以为指示当前业务是否为V2X相关业务信息(具体可以指示是否为V2V、V2I、V2P、V2C业务等)、可以为指示具体业务类型的信息(如道路安全类业务、交通效 率类业务、交通信息类业务等)、可以为指示业务处理方式的信息(如接入网络直接转发、接入网MBMS直接转发等)、还可以为指示UE为V2X类型终端信息。
下面为在不同消息中携带V2X相关指示信息的一些示例，以下述RRC连接请求、RRC连接完成、NAS消息来作为示例是因为这几种信令具备典型性，也较为常用，所以以之为例；但是，从理论上来说，用其它的信令消息也是可以的，事实上，如何通过现有的信令消息来传输信息对本领域技术人员来说也是容易实现的，RRC连接请求、RRC连接完成、NAS消息仅用于教导本领域技术人员具体如何实施本发明，但不意味仅能使用这几种消息，实施过程中可以结合实践需要参照相应的信令的具体情况来携带指示信息。
(1)、在RRC连接建立请求消息中增加新的RRC连接建立原因，如V2X接入、vehicle接入、道路安全接入等。
(2)、在RRC连接建立完成消息中增加新的信息单元(Information Element，IE)，携带指示信息如V2X本地业务标识、本地转发业务标识、本地MBSFN业务标识等。
(3)、在NAS消息中携带V2X业务相关标识信息(如：V2X业务标识、道路安全业务标识、车辆道路安全业务标识、V2X本地业务标识、本地转发业务标识、本地MBSFN业务标识、QoS参数标识)，可以在当前的NAS消息中增加新的IE，或在现有的IE中定义新的码点(如在Extended service request消息的Service type IE中加入新的码点指示)。
2、网络侧节点根据UE发送的V2X业务相关指示信息为UE建立传输V2X业务的承载、配置相应的资源，并可以为该承载上的数据设置相应的针对该业务的特殊的操作。
当网络侧节点为接入网节点时，如eNB、HeNB、relay，网络侧节点根据UE发送的V2X业务相关指示信息为UE分配对应的资源如eNB UE S1AP ID(该标识是eNB在S1接口上分配给每个UE在S1上的控制面连接的eNB端的标识)、无线网络临时识别(Radio Network Temporary Identity，RNTI)等。
当网络侧节点为核心网节点等网络侧设备时，如MME，网络侧节点根据UE发送的V2X业务相关指示信息执行如下步骤之一：
为UE传输V2X业务创建对应的承载(确定业务承载标识信息、特殊标识等)，并为UE分配相关的资源如MME UE S1AP ID(该标识是MME在S1上分配给每个UE在S1上的控制面连接的MME端的标识)、演进的无线接入承载标识(Evolved Radio Access Bearer，E-RAB ID)、GPRS隧道协议隧道端点标识(GPRS Tunneling Protocol Tunnel End Point Identifier，GTP-TEID)等，MME通过S1接口信令〔如，初始上下文建立请求(INITIAL CONTEXT SETUP REQUEST)、UE上下文修改请求(UE CONTEXT MODIFICATION REQUEST)、E-RAB建立请求(E-RAB SETUP REQUEST)、E-RAB修改请求(E-RAB MODIFY REQUEST)〕将为UE建立的承载信息(包括特殊标识，如本地广播指示、本地MBSFN转发指示、V2X承载指示等)和分配的相关资源信息通知UE对应的接入网节点 (如eNB)；
或，确定为UE创建特殊的无线承载(不创建无线承载以上的其他承载)，并通过S1接口信令(如INITIAL CONTEXT SETUP REQUEST、UE CONTEXT MODIFICATION REQUEST、E-RAB SETUP REQUEST、E-RAB MODIFY REQUEST)将创建特殊无线承载的信息指示(如：本地广播指示、本地MBSFN转发指示、V2X承载指示)给eNB。
接入网节点则根据MME的指示或根据设定规则为UE配置对应的无线承载资源以及其他相关资源，后续也可以对该承载上接收的数据包进行特定的处理，如将对应承载上UE上报的数据包以广播方式发送给本接入网覆盖下的其他UE，将对应承载上的数据包转发给相邻的满足要求eNB(如存在第二小区的eNB)，这些数据包在以广播方式发送给本接入网节点覆盖下的UE和被转发给相邻的eNB前可以进行其他处理，如进行完整性保护、增加用于同步的数据包头等。
网络侧节点将为UE创建的承载配置信息以及其他资源的配置信息通知UE。
接入网节点通过RRC信令〔如RRC连接配置(RRCConnectionReconfiguration)、RRC连接建立(RRCConnectionSetup)、下行信息传输(DLInformationTransfer)等或新定义的RRC信令〕向UE发送资源配置信息，包括无线承载配置信息(如对应承载各协议层实体的配置参数)；核心网节点(如MME)通过NAS信令〔如，附着接受(Attach accept)、验证请求(Authentication request)、安全模式命令(Security mode command)、下行通用NAS传输(Downlink generic NAS transport)、下行NAS传输(Downlink NAS Transport)、激活专用EPS承载上下文请求(Activate dedicated EPS bearer context request)、激活默认EPS承载上下文请求(Activate default EPS bearer context request)、修改EPS承载上下文请求(Modify EPS bearer context request)等或新定义的NAS消息〕向UE发送资源配置信息(如UE解码V2X相关业务使用的公钥、公钥标识、生成公钥的相关参数、EPS承载上下文信息)，MME向UE发送的NAS信令需要先通过S1接口信令发送给eNB，再由eNB通过RRC信令发送给UE。
网络侧节点通过系统广播发送支持V2X业务的相关信息，UE接收系统消息，在支持V2X业务的小区发起V2X相关业务接入，具体可以是：
系统广播可以在现有的控制信息块(Master Information Block，MIB)、系统信息块(System Information Block，SIB)中增加新的IE或定义新的码点实现，也可以在新定义的SIB消息中指示。
支持V2X业务的相关信息，包括：支持的V2X业务类型信息、支持的发送V2X业务方式信息、支持V2X业务(MBSFN)区域信息等。
下面以实例来进行说明UE、核心网节点MME、接入网节点基站之间的交互实施。
实施例B1
UE向MME发送V2X指示信息，由MME建立特殊的用于传输V2X信息的承载(包括携带特殊指示标识(如本地广播指示、本地MBSFN转发指示、V2X承载指示、无高层承载(如S1承载、S5/S8承载、外部承载)指示等)、特殊的处理操作(如不创建无线承载以上的其他承载)等)，并将该特殊承载信息指示给eNB，由eNB为该特殊承载创建对应无线承载，eNB就可以对该特殊承载上的数据进行特殊处理，eNB将相关承载的配置信息发送给UE。
实施例B1.1：
1、UE在Attach Request消息携带V2X指示信息。
2、MME接收到UE的指示后为UE建立传输V2X业务的特殊承载，在向eNB发送的INITIAL CONTEXT SETUP REQUEST消息中携带该承载配置信息以及承载特性的标识-本地广播指示；
3、eNB接收到MME发送的消息后，为UE配置对应的无线承载，并将配置信息通过RRC连接重配置消息发送给UE；之后，eNB将从该无线承载上接收到的数据包，也即V2X信息，通过广播方式发送给本eNB下设定小区的UE。这里设定小区可以为本eNB下的所有小区、上报数据包的UE所在的小区、满足其他约定规则的小区(如根据UE的地理位置、信号状况来确定其上报的数据包应该在哪些小区中广播)。
实施例B1.2：
1、UE在Bearer resource allocation request消息中携带本地MBSFN转发指示信息。
2、MME接收到UE的指示后为UE建立传输V2X业务的特殊承载，在向eNB发送的E-RAB SETUP REQUEST消息中携带该承载配置信息以及承载特性的标识-本地MBSFN转发指示。
3、eNB接收到MME发送的消息后，为UE配置对应的无线承载，并将配置信息通过RRC连接重配置消息发送给UE；之后，eNB将从该无线承载上接收到的数据包，也即V2X信息，分发给周围满足要求的eNB(如存在第二小区的eNB)，由满足要求的eNB在符合条件的小区下进行发送。
实施例B1.3：
1、UE在Service Request消息携带V2X指示信息。
2、MME接收到UE的指示后为UE建立传输V2X业务的特殊承载，在向eNB发送的INITIAL CONTEXT SETUP REQUEST消息中携带该承载配置信息以及承载特性的标识-V2X承载指示。
3、eNB接收到MME发送的消息后，为UE配置对应的无线承载，并将配置信息通过RRC连接重配置消息发送给UE；之后，eNB将从该无线承载上接收到的数据包通过广播方式发送给本eNB下设定小区的UE，同时将从该无线承载上接收到的数据包转发给周围 满足要求的eNB(如存在第二小区的eNB)。
实施例B2
UE向MME发送V2X指示信息，由MME确定为UE创建特殊的无线承载(不创建无线承载以上的其他承载)，并将创建特殊无线承载的信息指示给eNB，由eNB为该特殊承载创建对应无线承载，eNB可以对该特殊承载上的数据进行特殊处理，eNB将相关承载的配置信息发送给UE。
实施例B2.1：
1、UE在Attach Request消息携带V2X业务指示。
2、MME接收到UE的指示后，确定为UE创建特殊的无线承载，在向eNB发送的INITIAL CONTEXT SETUP REQUEST消息中携带创建特殊无线承载的指示-本地广播指示。
3、eNB接收到MME发送的消息后，为UE配置对应的无线承载，并将配置信息通过RRC连接重配置消息发送给UE；之后，eNB将从该无线承载上接收到的数据包通过广播方式发送给本eNB下设定小区的UE。这里设定小区可以为本eNB下的所有小区、上报数据包的UE所在的小区、满足其他约定规则的小区(如根据UE的地理位置、信号状况来确定其上报的数据包应该在哪些小区中广播)。
实施例B2.2：
1、UE在Bearer resource allocation request消息中携带本地MBSFN转发业务指示。
2、MME接收到UE的指示后，确定为UE创建特殊的无线承载，在向eNB发送的E-RAB SETUP REQUEST消息中携带创建特殊无线承载的指示-本地MBSFN转发指示。
3、eNB接收到MME发送的消息后，为UE配置对应的无线承载，并将配置信息通过RRC连接重配置消息发送给UE；之后，eNB将从该无线承载上接收到的数据包转发给周围满足要求的eNB(如存在第二小区的eNB)，由满足要求的eNB在符合条件的小区下进行发送。
实施例B2.3：
1、UE在Service Request消息携带V2X业务指示。
2、MME接收到UE的指示后，确定为UE创建特殊的无线承载，在向eNB发送的INITIAL CONTEXT SETUP REQUEST消息中携带创建特殊无线承载的指示-V2X承载指示。
3、eNB接收到MME发送的消息后，为UE配置对应的无线承载，并将配置信息通过RRC连接重配置消息发送给UE；之后，eNB将从该无线承载上接收到的数据包通过广播方式发送给本eNB下设定小区的UE，同时将从该无线承载上接收到的数据包转发给周围满足要求的eNB。
实施例B3:
UE发起正常的承载建立过程，消息中携带UE标识或QoS参数，MME通过UE标识或QoS参数，确定为UE创建特殊的承载，并将该特殊承载的信息指示给eNB，由eNB为该特殊承载创建对应无线承载，eNB可以对该特殊承载上的数据进行特殊处理，eNB将相关承载的配置信息发送给UE。
实施例B3.1：
1、UE在Attach Request消息携带UE标识。
2、MME接收Attach信息中通过UE标识向HSS查找UE的签约信息，通过获得的签约信息确定为UE建立传输V2X业务的特殊承载，在向eNB发送的INITIAL CONTEXT SETUP REQUEST消息中携带该承载配置信息以及承载特性的标识-本地广播指示；
3、eNB接收到MME发送的消息后，为UE配置对应的无线承载，并将配置信息通过RRC连接重配置消息发送给UE；之后，eNB将从该无线承载上接收到的数据包通过广播方式发送给本eNB下设定小区的UE。这里设定小区可以为本eNB下的所有小区、上报数据包的UE所在的小区、满足其他约定规则的小区(如根据UE的地理位置、信号状况来确定其上报的数据包应该在哪些小区中广播)。
实施例B3.2：
1、UE在Bearer resource allocation request消息携带QoS参数信息。
2、MME通过Bearer resource allocation request中携带的QoS参数信息，确定为UE建立传输V2X业务的特殊承载，在向eNB发送的E-RAB SETUP REQUEST消息中携带该承载配置信息以及承载特性的标识-本地MBSFN转发指示。
3、eNB接收到MME发送的消息后，为UE配置对应的无线承载，并将配置信息通过RRC连接重配置消息发送给UE；之后，eNB将从该无线承载上接收到的数据包转发给周围满足要求的eNB。
实施例B4:
UE发起正常的承载建立过程，消息中携带UE的标识或Qos参数，MME通过UE的标识或Qos参数，确定为UE创建特殊的无线承载，并将该特殊无线承载的信息指示给eNB，由eNB为该特殊承载创建对应无线承载，eNB可以对该特殊承载上的数据进行特殊处理，eNB将相关承载的配置信息发送给UE。
实施例B4.1：
1、UE在Attach Request消息中携带V2X UE标识信息。
2、MME接收Attach信息中通过UE标识向HSS查找V2X UE的签约信息，通过获得的签约信息，确定为UE创建特殊的无线承载，然后在向eNB发送的INITIAL CONTEXT SETUP REQUEST消息中携带创建特殊无线承载的指示。
3、eNB接收到MME发送的消息后，为UE配置对应的无线承载，并将承载配置信息通过RRC连接重配置消息发送给UE；根据约定eNB需要将从该无线承载上接收到的数据包进行本地广播。
实施例B4.2：
1、UE在Bearer resource allocation request消息中携带QoS参数信息。
2、MME通过Bearer resource allocation request中携带的QoS参数信息，确定为UE创建特殊的无线承载，然后在向eNB发送的E-RAB SETUP REQUEST消息中携带创建特殊无线承载的指示。
3、eNB接收到MME发送的消息后，为UE配置对应的无线承载，并将承载配置信息通过RRC连接重配置消息发送给UE；根据约定eNB需要将从该无线承载上接收到的数据包进行本地广播。
实施例B5:
UE通过RRC消息向接入网节点发送V2X指示信息，将其中的NAS消息转发给核心网，核心网根据UE发送的NAS消息为UE创建普通的承载，接入网节点将核心网节点为UE分配的承载做标记，将该承载上UE上报的数据做特殊处理。
实施例B5.1：
1、UE在RRC连接建立完成消息中加入V2X指示信息，向eNB指示当前UE发起业务为V2V道路安全业务。
2、eNB将RRC连接建立完成消息中的NAS消息转发给MME，根据MME指示为UE建立对应的无线承载。根据约定eNB需要对UE上报的V2V道路安全业务数据进行本地广播，eNB将对应的无线承载做本地广播标记。
3、eNB将存在本地广播标记的承载上接收的UE上传的数据包通过广播方式下发给本小区下的其他UE。
实施例B5.2：
1、UE在RRC连接建立完成消息中加入V2X指示信息，向eNB指示UE请求业务对应的UE上报数据需要进行本地广播和本地MBSFN转发。
2、eNB将RRC连接建立完成消息中的NAS消息转发给MME，根据MME指示为UE建立对应的无线承载。根据约定eNB需要对UE上报的V2V道路安全业务数据进行本地广播和本地MBSFN转发，eNB将对应的无线承载进行标记。
3、eNB将存在本地广播标记的承载上接收的UE上传的数据包通过广播方式下发给本小区下的其他UE，并通过X2/S1接口转发给周围满足要求的eNB。
由上述实施例可见，实施例中提供了UE向网络侧节点发送V2X业务相关指示信息的方案；网络侧节点接收到UE发送的V2X业务相关指示信息的处理方案；网络侧节点将相 关配置信息发送给UE的方案。
具体的，UE将V2X业务相关指示信息发送给网络侧节点；V2X业务相关指示信息可以包括：V2X业务标识、道路安全业务标识、车辆道路安全业务标识、V2X本地业务标识、本地转发业务标识、本地MBSFN业务标识、V2X接入标识、vehicle接入标识、道路安全接入标识等。
UE可以通过RRC消息将V2X业务相关指示信息发送给接入网节点，具体可以：
在RRC连接建立请求消息中增加新的RRC连接建立原因，如V2X接入、vehicle接入、道路安全接入等；
在RRC连接建立完成消息中增加新的IE，携带指示信息如V2X本地业务标识、本地转发业务标识、本地MBSFN业务标识等；
UE通过NAS消息将V2X业务相关指示信息发送给核心网节点；
在当前的NAS消息中增加新的IE，或在现有的IE中定义新的码点(如在Extended service request消息的Service type IE中加入新的码点指示)；
网络侧节点根据UE发送的V2X业务相关指示信息为UE执行相应的承载配置和设定的处理；
网络侧节点将为UE配置的承载信息和其他资源信息通知UE；
向UE发送资源配置信息，如EPS承载上下文信息、承载配置信息、UE解码V2X相关业务使用的公钥、公钥标识、生成公钥的相关参数等。
通过本实施例的方案，使网络能够对UE发起的V2X业务进行识别，执行相应资源的分配处理。
三、切换过程中的实施
在图4、5的信息发送方法一、二实施过程中，终端设备会出现切换的情况，下面对切换的情况进行说明。
图19为LTE网络架构示意图，如图所示，LTE系统网络侧实体由MME/S-GW、eNB组成。eNB和eNB间的接口为X2接口，MME/S-GW与eNB间的接口为S1接口。
LTE网络中，当UE从一个eNB移动到另一个eNB时，为了使正在发生的业务不中断，需要进行切换。如果eNB间存在X2连接，那么可以通过X2接口来完成切换过程；如果eNB间没有X2接口，可以通过S1接口来完成。
图20为LTE系统通过X2接口的非竞争随机接入切换流程示意图，如图所示，在源eNB基于UE上报的测量报告和RRM(无线资源管理)信息判断UE需要进行切换后，通过X2接口的切换过程主要包括如下步骤：
步骤2001、源eNB向目标eNB发送切换请求(handover request)消息；
切换请求信息中携带UE向目标eNB进行切换准备所必需的信息，如：UE在源eNB 中的context(上下文)信息，目标cell ID等；
步骤2002、目标eNB向源eNB返回切换请求确认(handover request ack)消息；
如果切换UE所使用的资源在目标eNB被批准，那么目标小区将为该UE配置相应的资源，并向源eNB发送切换请求ack消息。切换请求ack消息包含UE向目标eNB切换时所需的参数信息，如：可能包含目标eNB的系统信息、UE在目标eNB进行随机接入时的preamble(前导码)信息等；
步骤2003、源eNB向UE发送RRC连接配置(RRC connection reconfigurationg)消息；
源eNB在收到目标eNB发送的切换请求ack消息后，向UE发送切换命令信息，指示UE向目标eNB进行切换。源eNB向UE发送的切换命令的内容是包含在目标eNB向源eNB发送的切换请求ack消息中的；
步骤2004、UE向目标eNB发送随机接入前导序列(Random Access preamble)；
步骤2005、目标eNB返回随机接入响应(Random Access Response，RAR)；
收到切换命令以后，UE执行与目标eNB的同步。如果在切换命令中配给了专用随机接入信道前导序列(Random Access Channel preamble，RACH preamble)，则使用无竞争随机接入流程接入目标小区，如果没有配给专用的RACH preamble，则使用基于竞争随机接入流程接入目标小区；
步骤2006、UE向目标eNB发送RRC connection reconfigurationg complete(RRC连接配置完成)消息。
当UE成功接入目标小区后，UE发送切换完成消息，向目标eNB指示UE的切换流程完成。
图21为LTE系统通过S1接口的非竞争随机接入切换流程示意图，如图所示，与通过X2接口进行的切换流程不同在于需要通过MME，通过S1接口的切换过程主要包括如下步骤：
步骤2101、源eNB向MME发送切换需求(handover required)消息；
步骤2102、MME向目标eNB发送handover request消息；
步骤2103、目标eNB向MME返回handover request ack消息；
步骤2104、MME向源eNB返回切换命令(handover command)消息；
步骤2105、源eNB向UE发送RRC connection reconfigurationg消息；
步骤2106、UE向目标eNB发送Random Access preamble；
步骤2107、目标eNB返回RAR；
步骤2108、UE向目标eNB发送RRC connection reconfigurationg complete消息；
步骤2109、目标eNB向MME发送切换通知(handover notify)消息。
由上述两个切换流程可以看出，由于切换中没有涉及到信息的相关内容，目标eNB不 能针对具体的信息收发的UE做相应的处理。以V2X业务为例，当前的切换信令中没有包含UE是否收发V2X业务的相关信息，目标eNB不能针对进行V2X收发的UE做特殊处理，而这可能会导致UE正在进行的V2X业务发生中断，造成交通安全隐患。当然，其他业务也存在同样的问题。
为了实现图4、5中所述的增强的基于eMBMS的通信，本发明实施例中还提出了相应的切换情况下的处理方案，用于解决网络侧节点在切换时保证信息收发的连续性问题，该方案具体可以用于基站、直放站等网络侧节点上。
图22为源基站侧的切换方法实施流程示意图，如图所示，可以包括如下步骤：
步骤2201、确定归属于第一基站的终端设备将切换至第二基站；
实施中，所述终端设备将要上报的信息是需要在属于同一MBSFN区域的各小区中在与所述MBSFN区域对应的时间与频率资源上发送的信息，和/或，接收的信息是各基站在属于同一MBSFN区域的各小区中在与所述MBSFN区域对应的时间与频率资源上发送的信息，也即，需要在属于以终端上报信息的小区作为数据源小区的MBSFN区域的各小区中发送的信息；
步骤2202、向第二基站发送切换请求消息，在所述切换请求消息中指示与该终端设备上报和/或接收信息有关的设置信息。
实施中，当目标基站允许切换时，还可以进一步包括：
步骤2203、接收第二基站返回的包含有切换命令的切换请求确认消息，在所述切换命令中携带有第二基站根据与该终端设备上报和/或接收信息有关的设置信息配置的配置信息；
步骤2204、向终端设备发送所述切换命令。
实施中，对于步骤2202，在所述切换请求消息中指示与该终端设备上报和/或接收信息有关的设置信息，可以是通过以下方式之一或者其组合来指示的：
在AS-Context中添加所述设置信息；
在承载上报和/或接收信息的业务的E-RAB对应的E-RABs To Be Setup Item中添加所述设置信息；
在RRC Context中承载上报和/或接收信息的业务的DRB对应的信息中添加所述设置信息。
同样，当以V2X业务、UE为例时，当源网络侧节点判断正在接受V2X服务和/或对V2X业务感兴趣的UE需要进行切换时，可在向目标网络侧节点发送的切换请求消息中携带该UE的V2X相关指示信息，如：V2X承载相关指示、V2X频点相关指示、V2X业务相关指示信息、V2X specific ID指示(如MME UE S1AP ID、E-RAB ID、DRB ID、逻辑信道ID等V2X ID相关指示)。具体的方式可以为以下之一或者其组合：
1、在接入层上下文(Access Stratum context，AS-Context)(如E-UTRAN)中添加V2X兴趣指示(V2Xinterestindication)信息，如UE是否接受V2X服务、当前UE接受V2X服务的频点、UE接受V2X服务的方式(如通过单播方式、MBMS方式、D2D方式等)、UE接受V2X服务方式的优先级等)；
2、在UE上下文信息(UE Context Information)中添加UE支持的V2X业务类型指示、V2X业务优先级指示；
3、在E-RABs将设置项目(E-RABs To Be Setup Item)中添加V2X业务关联的E-RAB指示、V2X业务类型指示、V2X业务优先级指示；
4、在RRC上下文(RRC Context)中添加V2X业务关联的DRB指示、V2X业务类型指示、V2X业务优先级指示；
5、采用V2X specific的ID值如特殊的MME UE S1AP ID、E-RAB ID、DRB ID、逻辑信道ID通知目标网络侧节点该UE与V2X相关的信息。
图23为目标基站侧的切换方法实施流程示意图，如图所示，可以包括如下步骤：
步骤2301、接收第一基站发送的将归属于第一基站的终端设备切换至第二基站的切换请求消息，在所述切换请求消息中指示有与该终端设备上报和/或接收信息有关的设置信息；
实施中，所述终端设备将要上报的信息是需要在属于同一MBSFN区域的各小区中在与所述MBSFN区域对应的时间与频率资源上发送的信息，和/或，接收的信息是各基站在属于同一MBSFN区域的各小区中在与所述MBSFN区域对应的时间与频率资源上发送的信息，也即，需要在属于以终端上报信息的小区作为数据源小区的MBSFN区域的各小区中发送的信息。
步骤2302、在确定将归属于第一基站的终端设备将切换至第二基站后，对终端设备在第二基站上上报和/或接收信息的资源进行配置，并向第一基站返回包含有切换命令的切换请求确认消息，在所述切换命令中携带有第二基站根据与该终端设备上报和/或接收信息有关的设置信息配置的配置信息。
实施中，对终端设备在第二基站上上报和/或接收信息的资源进行配置，包可以括如下配置之一或者其组合：
为终端设备配置上报和/或接收信息的频点；
对承载上报和/或接收信息的业务的DRB参数进行配置；
为终端设备配置SPS周期；
为终端设备配置与上报和/或接收信息的业务相关的MBMS业务信息和/或MBSFN区域信息，这些信息可以用于如解码MBSFN区域对应的数据所需的公钥、相关业务(如V2X业务)对应的MBSFN区域标识等；
将为终端设备上报和/或接收信息的业务创建的DRB与终端设备上报和/或接收信息的业务对应的E-RAB相关联；
将终端设备上报和/或接收信息的业务对应的DRB的处理实体相关关联。
同样，当以V2X业务、UE为例时，如果UE切换被目标网络侧节点批准，目标网络侧节点可以执行如下操作中的一种或多种为：
为该UE配置相应的资源，并将配置信息作为切换命令的内容携带在切换请求ACK消息中发送给源网络侧节点(如基站)，使源网络侧节点将切换命令发送给UE。配置操作的内容具体可以包括以下一种或多种：
将UE配置到对应的频点、小区上，以便使UE在该频点、小区上进行V2X数据收发，网络侧可以为UE配置多个频点、小区，如在城市区域可以视情况配置多个频点等；
对承载V2X业务的DRB参数进行特殊的配置，如设置特殊的定时器长度；
对支持V2X业务的UE进行特殊的配置，如配置特殊的半持续调度(semi-persistent schedule，SPS)周期；
与V2X相关MBMS业务信息、MBSFN区域信息(用于如解码MBSFN区域对应的数据所需的公钥、相关业务(如V2X业务)对应的MBSFN区域标识等)；
将为UE V2X建立的DRB与E-RAB关联；将DRB关联到V2X特殊处理实体，以便对该DRB上收发的数据包做特殊处理，如将收集的数据包进行完整性保护后转发给周围小区。
下面以实例来进行说明UE在源小区中已接收V2X业务以及未接收V2X业务时的切换实施过程。
实施例C1：UE在源小区中已接受V2X服务。
1、车辆UE1在源eNB下接受V2X道路安全服务，UE1周期性向源eNB上报自己的状态信息(如位置、速度、行驶方向等)，并通过接收MBMS业务方式获得周围其他车辆UE的状态信息；
2、源eNB判断UE1需要从当前的eNB切换到目标eNB。源eNB在向目标eNB发送的切换请求中添加如下信息之一或者其组合：
在AS-Context中添加V2Xinterestindication指示信息，指示UE1接收V2X业务的频点，接受V2X服务的方式优先采用MBMS方式；
在承载V2X业务的E-RAB对应的E-RABs To Be Setup Item中添加V2X业务指示，支持该E-RAB对应V2X道路安全业务以及该业务优先级为高；
在RRC Context中承载V2X业务的DRB对应的信息中添加V2X业务指示，支持该DRB对应V2X道路安全业务以及该业务优先级为高；
3、目标eNB接收到源eNB发送的切换请求后，判断允许UE1进行切换，为UE1执 行以下配置和处理：
将UE1配置到对应的频点上。需要说明的是，不论UE1在源eNB下通过一个频点还是多个频点收发数据，目标eNB可以根据情况为UE1配置多个频点，如目标eNB处于高车辆密度区域或由低车辆向高车辆密度的过度区域，目标eNB可以为UE1配置多个频点进行数据收发，以避免V2X数据传输拥塞；
对承载V2X业务的DRB参数进行特殊的配置，如设置较短的状态报告禁止定时器；
将UE1的SPS周期配置为100ms；
与V2X相关MBMS业务信息、MBSFN区域信息；
将上述配置信息作为切换命令的内容携带在切换请求ack消息中发送给源eNB；
将为UE1V2X业务创建的DRB与UE1V2X对应的E-RAB相关联；
将UE1V2X业务对应的DRB的V2X特殊处理实体相关关联，该实体负责将UE1上报的V2X道路安全相关的数据包进行完整性保护后转发给同一MBSFN区域中的其他小区；
源eNB接收到切换请求ack消息后将其中包含的切换命令发送给UE1。
实施例C2：UE在源小区中未接受V2X服务
1、车辆UE在源eNB下尚未接受V2X道路安全服务，但UE对V2X道路安全服务感兴趣；
2、源eNB判断UE需要从当前的eNB切换到目标eNB。源eNB在向目标eNB发送的切换请求中添加如下信息：
在AS-Context中添加V2Xinterestindication指示信息，指示UE可以接收V2X业务的频点列表，接受V2X服务的方式优先采用MBMS方式；
3、目标eNB接收到源eNB发送的切换请求后，判断允许UE1进行切换，且能够为UE1提供V2X道路安全服务，为UE1执行以下配置和处理：
将UE1配置到对应的频点上；
向UE1发送能够为其提供V2X服务指示；
与V2X相关MBMS业务信息、MBSFN区域信息；
将上述配置信息作为切换命令的内容携带在切换请求ack消息中发送给源eNB。
4、源eNB接收到切换请求ack消息后将其中包含的切换命令发送给UE。
由上述实施例可见，当源网络侧节点判断正在接受V2X服务和/或对V2X业务感兴趣的UE需要进行切换时，在向目标网络侧节点发送切换请求消息中携带该UE的V2X业务指示信息；
如果UE切换被目标网络侧节点批准，目标网络侧节点执行相应的操作，并将相关配置信息通知源网络侧节点。
通过该方案，可以使切换时目标网络侧节点能够对支持V2X业务的UE进行特殊处理，保障V2X业务在UE切换过程中的连续性。
四、传输过程中信息完整性保护的实施。
在图4、5的信息发送方法一、二实施过程中，对信息的安全性也提出了要求，下面对信息安全性的实施情况进行说明。
首先对实施中涉及到的非对称密码体制进行说明。
非对称密钥加密体制，又称为公钥密码体制、双密钥密码体制。它是指对信息加密和解密时所使用的密钥是不同的，即有两个密钥，一个是可以公开的，另一个是私有的，这两个密钥组成一对密钥对，分别为公开密钥和私有密钥。如果使用其中一个密钥对数据进行加密，则只有用另外一个密钥才能解密。由于加密和解密时所使用的密钥不同，这种加密体制称为非对称密钥加密体制。在公开密钥算法中，用公开的密钥进行加密，用私有密钥进行解密的过程，称为加密过程。而用私有密钥进行加密，用公开密钥进行解密的过程称为认证(又称完整性保护)过程。非对称密码算法的保密性比较好，不需要加解密用户间进行密钥交换。
完整性保护的实质是收发两端将明文作为输入参数，计算出校验码，通过收发两端计算出的校验码的一致性来证明两端输入参数的一致性，即明文是一致的。图24为完整性保护过程示意图，如图所示，在完整保护过程中，发端利用完整性保护密钥以及其他参数和需要进行完整性保护的消息本身作为完整性保护算法的输入，生成一个完整性保护校验码MAC-I，发端将消息本身和MAC-I一起发送给接收端；收端利用完整性保护密钥以及相应的参数和消息本身作为完整性保护算法的输入，生成一个完整性保护校验码XMAC-I，与接收到的MAC-I进行比较，如果一致，则认为受到的消息和发送的消息是一致的，即没有被第三方篡改。需要说明的是，当采用对称密钥机制时，发端密钥和收端密钥是相同的，当采用非对称密钥机制时，发端密钥和收端密钥是不同的，发端采用私钥，收端采用公钥。
为了实现图4、5中所述的增强的基于eMBMS的通信，本发明实施例中还提出了相应的数据的安全处理方案，用于解决网络侧节点在收集到信息后，采用eMBMS方式向本网络侧节点覆盖下的终端设备发送时的信息安全性问题，该方案具体可以用于基站、直放站等网络侧节点上。
在向所述各第二基站分发信息，以及向指定的终端设备发送信息时，进一步包括：
将所述信息用私钥进行完整性保护，所述私钥是与所述MBSFN区域对应的私钥。
当以V2X业务、UE为例时，网络侧节点将收集的经过私钥进行完整性保护后的道路安全相关的数据包发送给UE。
具体实施中，网络侧节点收集的经过私钥进行完整性保护后的道路安全相关的数据包分为两类：一类是网络侧节点将覆盖范围内的UE上报的道路安全相关的数据包采用网络 侧节点自己关联的私钥进行完整性保护后的数据包；另一类是网络侧节点从其他网络侧节点获得的数据包，其他网络侧节点可以是eNB、HeNB、Relay等现有网络侧节点，也可以为后续新增加的网络侧节点，这些数据包在到达网络侧节点前已经由其他网络侧节点采用其他网络侧节点对应的私钥进行了完整性保护。其中，网络侧节点发送数据包可以采用MBSFN方式也可以采用点到多点(Point To Multipoint，P2M)广播或组播方式。
网络侧节点将覆盖范围内的UE上报的道路安全相关的数据包采用网络侧节点自己关联的私钥进行完整性保护后的数据包发送给周围相关的其他网络侧节点。这是因为每个MBSFN区域中的数据源小区需要向该MBSFN区域中的其他小区提供相同的数据，以保证一个MBSFN区域中的所有小区能够在相同的时频资源上发送相同的数据，从而使接收UE获得接收分集增益。网络侧节点需要确定该网络侧节点关联的小区，并确定各小区作为数据源小区的MBSFN区域中的其他小区，将各小区下UE上报的道路安全相关的数据包采用各小区对应的完整性保护私钥进行完整性保护后，发送给各小区作为数据源小区的MBSFN区域中的其他小区对应的网络侧节点。
实施中，在信息是用与所述MBSFN区域对应的私钥进行完整性保护的信息时，按与该MBSFN区域对应的规则处理信息包括：
确定与所述MBSFN区域对应的公钥；
采用所述公钥进行对完整性保护后的信息进行完整性验证。
同样，当以V2X业务、UE为例时，UE接收到网络侧发送的道路安全性相关的数据包后，根据接收到的网络侧节点发送的MBSFN区域对应的安全性公钥对各MBSFN区域的数据包进行完整性验证。当不同的MBSFN区域采用不同的公钥时，由于一个小区可能会属于多个MBSFN区域，UE可能会接收到多个MBSFN区域对应的数据包，因此，UE在对接收到的数据包进行完整性验证前需要先确定数据包对应的MBSFN区域，然后采用该MBSFN区域的公钥对数据包进行完整性验证。
实施中，公钥可以是基站发送的公钥，和/或，是存储在终端设备中的公钥，和/或，通过其他方式〔如，通过路侧单元(Road Side Unit，RSU)〕获得的公钥。
相应的，实施中，基站侧可以进一步包括：
向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
实施中，公钥可以是来自MME和/或MCE的。
当以V2X业务、UE为例时，UE在接收网络侧节点发送的完整性保护后的道路安全相关的数据包，需要提前获得对接收的道路安全相关的数据包进行完整性验证的公钥。UE获知完整性验证的公钥可以采用两种方式：
方式1：网络侧节点将自己关联的MBSFN区域对应的安全性公钥发送给UE。
这里的网络侧节点可以是eNB、HeNB、Relay等现有网络侧节点，也可以是后续新增加的其它类型的网络侧节点(如RSU)。网络侧节点关联的MBSFN区域包括网络侧节点下的各小区关联的MBSFN区域。网络侧节点可以关联一个或多个MBSFN区域，如图10中Cell 1-Cell 7关联了7个MBSFN区域。这里的安全性公钥用于UE对从网络侧节点接收到的道路安全信息进行完整性验证。
安全性公钥可以由网络侧节点自身产生，也可以由更高层网络侧节点产生，如eNB、MME、多小区多播协调实体(Multi-cell/multicast Coordination Entity，MCE)、归属用户服务器(Home Subscriber Server，HSS)、广播组播业务中心(broadcast multicast service center，BM-SC)等。网络侧节点将自己关联的MBSFN区域对应的安全性公钥发送给UE可以采用广播、多播、单播方式。当采用广播方式发送时，可以采用系统广播(如在设定的SIB中携带)，也可以采用MBMS广播(如在多播控制信道(Multicast Control Channel，MCCH)中携带或作为特定的业务在多播业务信道(Multicast Traffic Channel，MTCH)中携带)；当采用单播方式发送时，可以在安全模式命令(SecurityModeCommand)信令中携带，也可以在其他RRC信令或NAS信令中携带(通过这种方式获得的公钥能对基站的合法性进行检验)；
切换时，目标eNB可以将对应的公钥通过切换命令发送给UE，也可以在切换完成后由目标eNB通过NAS消息发送给UE，还可以是UE在切换到目标基站后通过接收目标eNB发送的系统信息获得。实施中考虑到在切换后，目标eNB下的小区可能关联了新的MBSFN区域，因此，具体实施中，在切换的时候可以将目标eNB小区关联的MBSFN区域对应的公钥告知UE。
实施中，还可以将各MBSFN区域对应安全性公钥直接存在UE的用户标识模块(Subscribers Identity Module，SIM)或通用用户标识模块(Universal Subscribers Identity Module，USIM)卡中。
下面以实例来进行说明eNB在信息发送给UE过程中安全性处理的实施过程。
实施例D1：
本实施例中描述的是，eNB1将各小区下UE上报的道路安全相关数据包进行完整性保护后发送给UE，并将各小区下UE上报的道路安全相关数据包进行完整性保护后发送给相关的邻eNB。
设eNB1下包含两个小区cell 1和cell 2，以cell 1和cell 2作为数据源小区的MBSFN区域分别为MBSFN区域2和MBSFN区域3，MBSFN区域2和MBSFN区域3占用的子帧分别为每个无线帧中的子帧7和子帧8；eNB2下包含一个小区cell3，eNB1的cell 1和eNB2的cell 3是地理位置相邻的小区，eNB2的cell 3属于以eNB1的cell 1为数据源小区的MBSFN区域2内，eNB2的cell 3需要在MBSFN区域2对应的子帧(每个无线帧中的 子帧7)上发送与eNB1的cell 1中MBSFN区域2对应的子帧上完全相同的数据，MBSFN区域2对应的子帧上发送的数据由eNB1转发给eNB2。图25为进行安全处理的信息传输实施环境示意图，如图所示，图25中所示eNB1下有UE1和UE2，两个UE都在Cell 1覆盖下，eNB2下有UE3，UE3在cell3覆盖下，eNB1向eNB2转发MBSFN区域2中发送的道路安全数据通过X2接口。具体流程如下：
1、eNB1收集UE1和UE2上报的道路安全数据包；具体实施中，对UE1、UE2上报的道路安全数据包收集可以是周期性收集(如每30ms)，也可以是在设定时间点收集，如以eNB1下各小区为数据源小区的MBSFN区域对应的MBSFN子帧前的设定时间处，还可以按照需要随时对UE上报的道路安全数据包进行收集；
2、eNB1将收集到的数据包采用私钥进行完整性保护。例如在本例中，对UE1和UE2上报的数据采用以cell1作为数据源小区的MBSFN区域对应的私钥进行完整性保护；
3、eNB1将完整性保护后的数据包在eNB1下的各小区中，以各小区为数据源小区的MBSFN区域对应的MBSFN子帧上按设定的数据格式发送。具体而言，那么eNB 1需要将cell 1中UE上报的数据包在经私钥进行完整保护后在MBSFN区域2占用的子帧上按照设定的数据格式发送。同时，eNB1将完整性保护后的数据包转发给给各小区作为数据源小区的MBSFN区域中的其他小区对应的网络侧节点，例如在本例中，eNB2下的cell3属于以eNB1下的cell 1为数据源小区的MBSFN区域2，因此，eNB1需要将cell 1采用私钥进行完整性保护后的数据转发给eNB2。
4、UE1和UE2在MBSFN区域2占用的子帧上根据网络侧指定的数据格式解码数据包后，将接收到的数据包采用解码MBSFN区域2数据对应的公钥进行完整性验证。若完整性验证通过则认为数据包中的数据是有效的道路安全数据，将对应数据包递交给高层，若完整性验证未通过，则认为接收到的道路安全数据是不可靠的，将对应数据包丢弃。
实施例D2：
本实施例中描述的是，eNB2将相邻eNB1转发的经完整性保护后的道路安全相关数据包发送给UE。
如图25所示，设eNB1下有两个UE，分别为UE1和UE2，两个UE都在Cell 1覆盖下，eNB2下有一个UE3，UE3在eNB2的Cell 3覆盖下，eNB1的cell 1和eNB2的cell 3是地理位置相邻的小区，eNB2的cell 3属于以eNB1的cell 1为数据源小区的MBSFN区域2内，因此eNB2的cell 3需要在MBSFN区域2对应的子帧(每个无线帧中的子帧7)上发送与eNB1的cell 1中MBSFN区域2对应的子帧上完全相同的数据，MBSFN区域2对应的子帧上发送的数据由eNB1通过X2接口转发给eNB2。具体流程如下：
1、eNB2在与eNB1的X2接口上收集eNB1转发的eNB1的cell 1下UE上报的道路安全数据。eNB2对与eNB1的X2接口上eNB1转发的道路安全数据的收集可以是周期性 收集(如每30ms)，也可以是在设定时间点收集(如以eNB2下各小区为数据源小区的MBSFN区域对应的MBSFN子帧前的设定时间处)，还可以是随时对X2接口上的道路安全数据包进行收集；
2、然后将后将收集的数据在约定的时间在MBSFN区域2占用的子帧上按照设定的数据格式发送。约定的时间由eNB1向eNB2转发的道路安全数据时对应的同步消息中获得。
3、UE3在MBSFN区域2占用的子帧上根据网络侧指定的数据格式解码数据包后，将接收到的数据包采用解码MBSFN区域2数据对应的公钥进行完整性验证。若完整性验证通过则认为数据包中的数据是有效的道路安全数据，将对应数据包递交给高层，若完整性验证未通过，则认为接收到的道路安全数据是不可靠的，将对应数据包丢弃。
实施例D3：
本实施例中描述的是，MME通过NAS信令将UE进行完整性验证的公钥发送给UE。eNB使用的私钥由MME发送给eNB。图26为信息安全处理中的密钥处理实施环境示意图，如图所示，具体流程如下：
1、MME获得eNB对采用MBMS方式发送的道路安全数据进行完整性保护的私钥以及UE对通过MBMS接收的道路安全数据包进行完整性验证的公钥。
MME获得的完整性保护的公钥和私钥可以由MME自己产生，也可以由MME从其他实体如HSS、MBMS网关等获得；
2、MME通过S1接口信令通知eNB该eNB下各小区对收集的UE上报的道路安全数据进行完整性保护的私钥。私钥用于eNB各小区对以该小区作为数据源小区的MBSFN区域中发送的数据包进行完整性保护。
3、MME通过NAS信令通知UE对接收到的道路安全数据包进行完整性验证的公钥。
由于一个小区可以同时属于多个MBSFN区域，当不同的MBSFN区域的数据源小区采用不同私钥对该MBSFN区域发送的数据包进行完整性保护时，MME需要通知UE对各MBSFN区域数据进行完整性验证的多个公钥；当不同的MBSFN区域的数据源小区采用相同私钥对所发送的数据包进行完整性保护时，MME只需通知UE对所有的MBSFN区域发送的道路安全数据进行完整性验证的公共公钥。MME向UE发送包含完整性验证的公钥的NAS信令时，可以采用RRC消息捎带的方式，如可以装在一个消息容器中，将该消息容器捎带在RRC连接重配置消息中发送给UE，也可以采用专门携带NAS信令的RRC消息发送给UE。
4、UE从NAS信令中获得对当前小区所关联的各发送道路安全消息的MBSFN区域数据进行完整性验证的公钥，使用各MBSFN区域对应的公钥对接收到的各MBSFN区域中的道路安全数据进行完整性验证。
实施例D4：
本实施例中描述的是，MCE通过MCCH/BCCH信令将UE进行完整性验证的公钥发送给UE。eNB使用的私钥由MCE发送给eNB。具体流程如下：
1、MCE获得eNB对采用MBMS方式发送的道路安全数据进行完整性保护的公钥以及UE对通过MBMS接收的道路安全数据包进行完整性验证的私钥。MCE获得的完整性保护的公钥和私钥可以由MCE自己产生，也可以由MCE从其他实体如MME等获得；
2、MCE通过M2接口信令通知eNB该eNB下各小区对道路安全数据进行完整性保护的私钥。私钥用于eNB各小区对以该小区作为数据源小区的MBSFN区域中发送的数据包进行完整性保护。
3、MCE通过MCCH/BCCH信令通知UE对接收到的道路安全数据包进行完整性验证的公钥。
由于一个小区可以同时属于多个MBSFN区域，当不同的MBSFN区域的数据源小区采用不同私钥对该MBSFN区域发送的数据包进行完整性保护时，MCE可以在各MBSFN区域对应的MCCH信令中通知UE对对应的MBSFN区域数据进行完整性验证的公钥，也可以在BCCH信令(如SIB13或新SIB)中携带对各MBSFN区域数据进行完整性验证的公钥；当不同的MBSFN区域的数据源小区采用相同私钥对所发送的数据包进行完整性保护时，MCE可以在各MBSFN区域对应的MCCH信令中携带相同的对道路安全数据进行完整性验证的公共公钥，也在BCCH信令(如SIB13或新SIB)中携带对道路安全数据进行完整性验证的公共公钥。
MCE将生成的包含完整性验证公钥的BCCH或MCCH信令，通过M2接口发送给相应的eNB，eNB在各小区的BCCH或各小区关联的MBSFN区域对应的MCCH资源上将包含完整性验证公钥的BCCH或MCCH信令发送给UE。
4、UE从BCCH或MCCH信令中获得对当前小区所关联的各发送道路安全消息的MBSFN区域数据进行完整性验证的公钥，使用各MBSFN区域对应的公钥对各MBSFN区域中的道路安全数据进行完整性验证。
由上述实施例可见，实施例中提供了网络侧节点将收集的道路安全数据采用MBSFN方式发送给UE和发送给相邻网络侧节点的方案；UE接收到网络侧节点发送的道路安全数据的处理方案；网络侧节点接收到相邻网络侧节点发送的道路安全数据的处理方案；eNB和UE获得完整性保护密钥的方案。
具体的，网络侧节点将收集的经过私钥进行完整性保护后的道路安全相关的数据包发送给UE；
网络侧节点网络侧节点将覆盖范围内的UE上报的道路安全相关的数据包采用网络侧节点自己关联的私钥进行完整性保护后的数据包发送给周围相关的其他网络侧节点；
UE接收到网络侧发送的道路安全性相关的数据包后，根据接收到的网络侧节点发送 的MBSFN区域对应的安全性公钥对各MBSFN区域的数据包进行完整性验证；
MME通过NAS信令将UE进行完整性验证的公钥发送给UE；或，MCE通过MCCH/BCCH信令将UE进行完整性验证的公钥发送给UE。
可见，通过本方案，能够在采用增强的eMBMS架构实现低时延V2X通信时，对网络侧节点发送的数据进行完整性验证。
基于同一发明构思，本发明实施例中还提供了一种信息发送装置以及信息接收装置，由于这些装置解决问题的原理与一种信息发送方法、信息接收方法相似，因此这些装置的实施可以参见方法的实施，重复之处不再赘述。
图27为信息发送装置一结构示意图，如图所示，可以包括：
上报信息接收模块2701，用于接收第一小区所辖的各终端设备上报至第一基站的信息，所述第一小区是归属于第一基站的小区；
分发模块2702，用于将该信息分发给与第一小区属于同一MBSFN区域的各第二小区归属的各第二基站，所述信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发送；
第一发送模块2703，用于在第一基站的第一小区以及归属于第一基站的与第一小区属于同一MBSFN区域的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
实施中，还可以进一步包括：
完整性保护模块2704，用于在向所述各第二基站分发信息，以及向指定的终端设备发送信息时，将所述信息用私钥进行完整性保护，所述私钥是与所述MBSFN区域对应的私钥。
实施中，第一发送模块还可以进一步用于向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
实施中，第一发送模块还可以进一步用于向终端设备发送来自MME和/或MCE的公钥。
实施中，第一小区所辖的各终端设备上报至第一基站的信息可以是用于V2X业务的V2X信息。
实施中，一个MBSFN区域可以包括一个第一小区以及至少一个第二小区。
图28为信息发送装置二结构示意图，如图所示，装置中可以包括：
分发信息接收模块2801，用于接收第一基站发送给第二基站的来自第一小区的信息，所述第一小区是归属于第一基站的小区；
小区确定模块2802，用于确定与第一小区属于同一MBSFN区域的第二小区，所述第二小区是归属于第二基站的小区；
第二发送模块2803，用于在第二基站的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
实施中，分发信息接收模块还可以进一步用于接收用私钥进行完整性保护的信息，所述私钥是与所述MBSFN区域对应的私钥。
实施中，还可以进一步包括：
第二发送模块进一步用于向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
实施中，第二发送模块还可以进一步用于向终端设备发送来自MME和/或MCE的公钥。
实施中，所述信息可以是用于V2X业务的V2X信息。
实施中，一个MBSFN区域可以包括一个第一小区以及至少一个第二小区。
图29为信息接收装置结构示意图，如图所示，装置中可以包括：
信息接收模块2901，用于接收基站发送的信息；
区域确定模块2902，用于根据接收信息的时间与频率资源确定对应的MBSFN区域；
信息处理模块2903，用于按与该MBSFN区域对应的规则处理信息。
实施中，信息处理模块还可以进一步用于在所述信息是用与所述MBSFN区域对应的私钥进行完整性保护的信息时，确定与所述MBSFN区域对应的公钥；采用所述公钥进行对完整性保护后的信息进行完整性验证。
实施中，信息处理模块还可以进一步用于通过以下方式之一或者其组合来获得的公钥：基站发送的公钥、存储在终端设备中的公钥、通过路侧单元RSU获得的公钥。
实施中，所述信息可以是用于V2X业务的V2X信息。
实施中，一个MBSFN区域可以包括一个第一小区以及至少一个第二小区。
为了描述的方便，以上所述装置的各部分以功能分为各种模块或单元分别描述。当然，在实施本发明时可以把各模块或单元的功能在同一个或多个软件或硬件中实现。
在实施本发明实施例提供的技术方案时，可以按如下方式实施。
图30为第一基站结构示意图，如图所示，基站中包括：
处理器3000，用于读取存储器3020中的程序，执行下列过程：
确定与第一小区属于同一MBSFN区域的第二小区，以及第二小区归属的基站；
收发机3010，用于在处理器3000的控制下发送数据，执行下列过程：
接收第一小区所辖的各终端设备上报至第一基站的信息，所述第一小区是归属于第一基站的小区；
将该信息分发给与第一小区属于同一MBSFN区域的各第二小区归属的各第二基站，所述信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发 送；
在第一基站的第一小区以及归属于第一基站的与第一小区属于同一MBSFN区域的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
实施中，收发机3010在向所述各第二基站分发信息，以及向指定的终端设备发送信息时，可以进一步用于：
将所述信息用私钥进行完整性保护，所述私钥是与所述MBSFN区域对应的私钥。
实施中，收发机3010可以进一步用于：
向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
实施中，所述公钥是来自MME和/或MCE的。
实施中，第一小区所辖的各终端设备上报至第一基站的信息是用于V2X业务的V2X信息。
实施中，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
其中，在图30中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器3000代表的一个或多个处理器和存储器3020代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机3010可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。处理器3000负责管理总线架构和通常的处理，存储器3020可以存储处理器3000在执行操作时所使用的数据。
图31为第二基站结构示意图，如图所示，基站中包括：
处理器3100，用于读取存储器3120中的程序，执行下列过程：
确定与第一小区属于同一MBSFN区域的第二小区，所述第二小区是归属于第二基站的小区；
收发机3110，用于在处理器3100的控制下发送数据，执行下列过程：
接收第一基站发送给第二基站的来自第一小区的信息，所述第一小区是归属于第一基站的小区；
在第二基站的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
实施中，所述信息是用私钥进行完整性保护的信息，所述私钥是与所述MBSFN区域对应的私钥。
实施中，收发机3110可以进一步用于：
向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述 MBSFN区域对应的公钥。
实施中，所述公钥可以是来自MME和/或MCE的公钥。
实施中，所述信息可以是用于V2X业务的V2X信息。
实施中，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
其中，在图31中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器3100代表的一个或多个处理器和存储器3120代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机3110可以是多个元件，即包括发送机和收发机，提供用于在传输介质上与各种其他装置通信的单元。处理器3100负责管理总线架构和通常的处理，存储器3120可以存储处理器3100在执行操作时所使用的数据。
图32为终端设备结构示意图，如图所示，终端设备包括：
处理器3200，用于读取存储器3220中的程序，执行下列过程：
根据接收信息的时间与频率资源确定对应的MBSFN区域；
按与该MBSFN区域对应的规则处理信息；
收发机3210，用于在处理器3200的控制下发送数据，执行下列过程：
接收基站发送的信息。
实施中，在所述信息是用与所述MBSFN区域对应的私钥进行完整性保护的信息时，按与该MBSFN区域对应的规则处理信息时，处理器3200还可以用于：
确定与所述MBSFN区域对应的公钥；
采用所述公钥进行对完整性保护后的信息进行完整性验证。
实施中，所述公钥可以是通过以下方式之一或者其组合来获得的公钥：基站发送的公钥、存储在终端设备中的公钥、通过路侧单元RSU获得的公钥。
实施中，所述信息是用于V2X业务的V2X信息。
实施中，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
其中，在图32中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器3200代表的一个或多个处理器和存储器3220代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机3210可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，用户接口3230还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器3200负责管理总线架构和通常的处理，存储器3220可以存储处理器3200在 执行操作时所使用的数据。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实施例的精神和范围。这样，倘若本发明实施例的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (34)

  1. 一种信息发送方法，其特征在于，包括：
    接收第一小区所辖的各终端设备上报至第一基站的信息，所述第一小区是归属于第一基站的小区；
    将该信息分发给与第一小区属于同一多播广播单频网络MBSFN区域的各第二小区归属的各第二基站，所述信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发送；
    在第一基站的第一小区以及归属于第一基站的与第一小区属于同一MBSFN区域的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
  2. 如权利要求1所述的方法，其特征在于，在向所述各第二基站分发信息，以及向指定的终端设备发送信息时，进一步包括：
    将所述信息用私钥进行完整性保护，所述私钥是与所述MBSFN区域对应的私钥。
  3. 如权利要求1或2所述的方法，其特征在于，进一步包括：
    向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
  4. 如权利要求3所述的方法，其特征在于，所述公钥是来自移动性管理实体MME和/或多播广播单频网络MCE的。
  5. 如权利要求1至4任一所述的方法，其特征在于，第一小区所辖的各终端设备上报至第一基站的信息是用于车与外界的信息交换V2X业务的V2X信息。
  6. 如权利要求1至5任一所述的方法，其特征在于，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
  7. 一种信息发送方法，其特征在于，包括：
    接收第一基站发送给第二基站的来自第一小区的信息，所述第一小区是归属于第一基站的小区；
    确定与第一小区属于同一MBSFN区域的第二小区，所述第二小区是归属于第二基站的小区；
    在第二基站的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
  8. 如权利要求7所述的方法，其特征在于，所述信息是用私钥进行完整性保护的信息，所述私钥是与所述MBSFN区域对应的私钥。
  9. 如权利要求7或8所述的方法，其特征在于，进一步包括：
    向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
  10. 如权利要求9所述的方法，其特征在于，所述公钥是来自MME和/或MCE的公钥。
  11. 如权利要求7至10任一所述的方法，其特征在于，所述信息是用于V2X业务的V2X信息。
  12. 如权利要求7至11任一所述的方法，其特征在于，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
  13. 一种信息接收方法，其特征在于，包括：
    接收基站发送的信息；
    根据接收信息的时间与频率资源确定对应的MBSFN区域；
    按与该MBSFN区域对应的规则处理信息。
  14. 如权利要求13所述的方法，其特征在于，在所述信息是用与所述MBSFN区域对应的私钥进行完整性保护的信息时，按与该MBSFN区域对应的规则处理信息包括：
    确定与所述MBSFN区域对应的公钥；
    采用所述公钥进行对完整性保护后的信息进行完整性验证。
  15. 如权利要求14所述的方法，其特征在于，所述公钥是通过以下方式之一或者其组合来获得的公钥：基站发送的公钥、存储在终端设备中的公钥、通过路侧单元RSU获得的公钥。
  16. 如权利要求13至15任一所述的方法，其特征在于，所述信息是用于V2X业务的V2X信息。
  17. 如权利要求13至16任一所述的方法，其特征在于，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
  18. 一种信息发送装置，其特征在于，包括：
    上报信息接收模块，用于接收第一小区所辖的各终端设备上报至第一基站的信息，所述第一小区是归属于第一基站的小区；
    分发模块，用于将该信息分发给与第一小区属于同一MBSFN区域的各第二小区归属的各第二基站，所述信息将在各基站下的各第二小区中在与所述MBSFN区域对应的时间与频率资源上发送；
    第一发送模块，用于在第一基站的第一小区以及归属于第一基站的与第一小区属于同一MBSFN区域的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
  19. 如权利要求18所述的装置，其特征在于，进一步包括：
    完整性保护模块，用于在向所述各第二基站分发信息，以及向指定的终端设备发送信息时，将所述信息用私钥进行完整性保护，所述私钥是与所述MBSFN区域对应的私钥。
  20. 如权利要求18或19所述的装置，其特征在于，第一发送模块进一步用于向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
  21. 如权利要求20所述的装置，其特征在于，第一发送模块进一步用于向终端设备发送来自MME和/或MCE的公钥。
  22. 如权利要求18至21任一所述的装置，其特征在于，第一小区所辖的各终端设备上报至第一基站的信息是用于V2X业务的V2X信息。
  23. 如权利要求18至22任一所述的装置，其特征在于，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
  24. 一种信息发送装置，其特征在于，包括：
    分发信息接收模块，用于接收第一基站发送给第二基站的来自第一小区的信息，所述第一小区是归属于第一基站的小区；
    小区确定模块，用于确定与第一小区属于同一MBSFN区域的第二小区，所述第二小区是归属于第二基站的小区；
    第二发送模块，用于在第二基站的第二小区中，在与MBSFN区域对应的时间与频率资源上向指定的终端设备发送信息。
  25. 如权利要求24所述的装置，其特征在于，分发信息接收模块进一步用于接收用私钥进行完整性保护的信息，所述私钥是与所述MBSFN区域对应的私钥。
  26. 如权利要求24或25所述的装置，其特征在于，进一步包括：
    第二发送模块进一步用于向终端设备发送对完整性保护后的信息进行完整性验证的公钥，所述公钥是与所述MBSFN区域对应的公钥。
  27. 如权利要求26所述的装置，其特征在于，第二发送模块进一步用于向终端设备发送来自MME和/或MCE的公钥。
  28. 如权利要求24至27任一所述的装置，其特征在于，所述信息是用于V2X业务的V2X信息。
  29. 如权利要求24至28任一所述的装置，其特征在于，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
  30. 一种信息接收装置，其特征在于，包括：
    信息接收模块，用于接收基站发送的信息；
    区域确定模块，用于根据接收信息的时间与频率资源确定对应的MBSFN区域；
    信息处理模块，用于按与该MBSFN区域对应的规则处理信息。
  31. 如权利要求30所述的装置，其特征在于，信息处理模块进一步用于在所述信息是用与所述MBSFN区域对应的私钥进行完整性保护的信息时，确定与所述MBSFN区域 对应的公钥；采用所述公钥进行对完整性保护后的信息进行完整性验证。
  32. 如权利要求31所述的装置，其特征在于，信息处理模块进一步用于通过以下方式之一或者其组合来获得的公钥：基站发送的公钥、存储在终端设备中的公钥、通过路侧单元RSU获得的公钥。
  33. 如权利要求30至32任一所述的装置，其特征在于，所述信息是用于V2X业务的V2X信息。
  34. 如权利要求30至33任一所述的装置，其特征在于，一个MBSFN区域包括一个第一小区以及至少一个第二小区。
PCT/CN2016/087972 2015-07-07 2016-06-30 一种信息发送接收方法及装置 Ceased WO2017005133A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510394342.0 2015-07-07
CN201510394342.0A CN106341813B (zh) 2015-07-07 2015-07-07 一种信息发送接收方法及装置

Publications (1)

Publication Number Publication Date
WO2017005133A1 true WO2017005133A1 (zh) 2017-01-12

Family

ID=57684814

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/087972 Ceased WO2017005133A1 (zh) 2015-07-07 2016-06-30 一种信息发送接收方法及装置

Country Status (2)

Country Link
CN (1) CN106341813B (zh)
WO (1) WO2017005133A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI787441B (zh) * 2018-03-09 2022-12-21 美商高通公司 基於eNB隧道傳輸的EV2X模式3操作
US11657715B2 (en) * 2017-08-11 2023-05-23 Siemens Mobility GmbH Method for providing a safe operation of subsystems within a safety critical system

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019029824A1 (en) * 2017-08-11 2019-02-14 Huawei Technologies Co., Ltd. APPARATUS FOR ESTABLISHING A V2X ORIENTED LOCAL E2E PATH AND QOS CONTROL
CN111866872B (zh) * 2019-04-29 2023-06-02 华为技术有限公司 一种通信方法及装置
US20220256337A1 (en) * 2019-06-14 2022-08-11 Telefonaktiebolaget Lm Ericsson (Publ) Methods, UE and Network Node for Handling System Information
CN115119164B (zh) 2021-03-18 2025-02-11 深圳引望智能技术有限公司 一种通信方法、装置及设备
CN115484552A (zh) * 2021-05-31 2022-12-16 华为技术有限公司 一种通信方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102143434A (zh) * 2010-01-29 2011-08-03 电信科学技术研究院 发送系统信息和接收mbms的方法、系统及装置
CN102740231A (zh) * 2011-04-02 2012-10-17 中兴通讯股份有限公司 监听多媒体广播多播业务的方法及用户设备
US20130003578A1 (en) * 2011-07-01 2013-01-03 Teck Hu User Equipment Restricted Measurements For Multimedia Broadcast Single Frequency Network Networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102143434A (zh) * 2010-01-29 2011-08-03 电信科学技术研究院 发送系统信息和接收mbms的方法、系统及装置
CN102740231A (zh) * 2011-04-02 2012-10-17 中兴通讯股份有限公司 监听多媒体广播多播业务的方法及用户设备
US20130003578A1 (en) * 2011-07-01 2013-01-03 Teck Hu User Equipment Restricted Measurements For Multimedia Broadcast Single Frequency Network Networks

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11657715B2 (en) * 2017-08-11 2023-05-23 Siemens Mobility GmbH Method for providing a safe operation of subsystems within a safety critical system
TWI787441B (zh) * 2018-03-09 2022-12-21 美商高通公司 基於eNB隧道傳輸的EV2X模式3操作

Also Published As

Publication number Publication date
CN106341813A (zh) 2017-01-18
CN106341813B (zh) 2019-12-13

Similar Documents

Publication Publication Date Title
CN106341848B (zh) 一种切换方法及装置
CN106341839B (zh) 一种信息上报、接收，承载建立的方法及装置
KR102127397B1 (ko) 데이터 유닛을 전송하는 방법 및 사용자기기와, 데이터 유닛을 수신하는 방법 및 사용자기기
CN104811892B (zh) 一种资源分配方法、装置及系统
KR102489759B1 (ko) 무선 통신 시스템에서 방송 자원 혼잡 제어 방법 및 장치
WO2017005133A1 (zh) 一种信息发送接收方法及装置
CN104754522B (zh) 一种保持组通信业务连续性的方法、装置和系统
JP6759362B2 (ja) ブロードキャスト／マルチキャストサービスを提供する方法及び装置
CN106341794B (zh) 一种信息发送方法及装置
CN106470483B (zh) 一种信息发送与控制信息发送的方法及装置
CN107027105A (zh) 车联网通信v2x消息的传输方法、装置及系统
WO2017133624A1 (zh) 车联网通信v2x消息的广播方法及装置、mbms承载的建立方法
JP2018514988A (ja) ポイントツーマルチポイントブロードキャストに支援されたビークルツーｘブロードキャスト
CN106331980A (zh) 车联网中车辆的管理方法及装置
CN107040959A (zh) 车联网业务拥塞控制的方法及装置
US20190349722A1 (en) Method and apparatus for performing prose communication in a wireless communication system
EP3783926B1 (en) Communication method and apparatus
JP7542625B2 (ja) 通信制御方法、ユーザ装置及びプロセッサ
CN105578382A (zh) 资源的获取、配置方法及装置，资源池的配置方法及装置
WO2017133467A1 (zh) 一种实现车联网业务的方法及本地化网络架构
CN107041016B (zh) 一种消息转发的方法、设备和系统
WO2015062474A1 (zh) 一种组通信信息通知方法及设备
CN107135485B (zh) 一种建立车与万物会话请求、确定传输小区的方法及装置
WO2017148212A1 (zh) 无线资源管理rrm的控制方法及装置
CN106470383A (zh) 车联网信息传输方法、装置及系统

Legal Events

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

Ref document number: 16820784

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16820784

Country of ref document: EP

Kind code of ref document: A1