WO2017036343A1

WO2017036343A1 - Data processing method and device

Info

Publication number: WO2017036343A1
Application number: PCT/CN2016/096733
Authority: WO
Inventors: 汪颖
Original assignee: 电信科学技术研究院
Priority date: 2015-08-31
Filing date: 2016-08-25
Publication date: 2017-03-09
Also published as: CN106488386A; CN106488386B

Abstract

Embodiments of the present application relate to the technical field of wireless communications, and particularly relate to a data processing method and device, realizing Internet of vehicle data processing. In embodiments of the present application, an RSU determines, according to service type indication information or bearer associated information, a service type of corresponding data. The RSU selects, according to the service type of the data, between directly processing data received on an air interface broadcast or processing the received data in an application layer. Since an RSU can determine, according to a service type of data, to directly process data received on an air interface broadcast or process the received data in an application layer, Internet of vehicle data processing can be achieved.

Description

Method and device for data processing

The present application claims priority to Chinese Patent Application No. 201510549375.8, entitled "A Method and Apparatus for Data Processing", filed on August 31, 2015, the entire contents of which is incorporated herein by reference. In the application.

Technical field

The present application relates to the field of wireless communication technologies, and in particular, to a method and an apparatus for performing data processing.

Background technique

In the Long Term Evolution (LTE) system, the centralized control mode of the network is adopted, that is, the uplink and downlink data of the user equipment (UE, which may also be referred to as a terminal) are transmitted and received under the control of the network. The communication between the UE and the UE is forwarded and controlled by the network. There is no direct communication link between the UE and the UE, and the UE is also not allowed to send uplink data by itself, see FIG. 1A.

Device-to-device (D2D), that is, user equipment pass-through technology, refers to a way in which neighboring user equipment can transmit data through a direct link in a short range without passing through a central node (ie, a base station). ) Forwarding, as shown in Figure 1B.

The communication between the car and anything (Vehicle-to-Everything, V2X) was formally established at the 2015 3GPP RAN #67 meeting. V2X communication mainly includes three aspects:

Vehicle-to-Vehicle (V2V): communication between On-Board Units (OBUs) on the vehicle;

Vehicle-to-Infrastructure (V2I): communication between the vehicle and the Road Side Unit (RSU);

Vehicle-to-Pedestrian (V2P): Communication between a car and a pedestrian.

Through V2X's car networking method, with the car and car, the car and the roadside equipment, and the wireless communication between the vehicles, the vehicle can realize the real-time perception of the surrounding conditions of the vehicle for timely warning, and become the current problem of solving road traffic safety problems in the world. A research hotspot.

In the vehicle networking application scenario, some are based on V2I/V2V services. Some of these services are that the vehicle terminal needs to terminate the data transmission to the RSU for service analysis, and then the RSU sends the data to other vehicle terminals, such as the vehicle automatic parking system, the queuing system, the road safety service system, and some of the RSU/eNB direct transparent forwarding. Received data, such as V2I vehicle emergency call notification service. There is no solution for how to specifically process the Internet of Vehicles data.

Summary of the invention

The embodiment of the present application provides a method and device for performing data processing to implement processing of vehicle network data.

A method for performing data processing provided by an embodiment of the present application, the method includes:

The roadside unit RSU determines the service type of the corresponding data according to the service type indication information or the bearer association information.

The RSU selects to directly receive the received data in the air interface or process the received data at the application layer according to the service type of the data.

Optionally, the RSU selects, according to the service type of the data, directly broadcasts the received data in the air interface or processes the received data at the application layer, including:

If the service type is the car-to-vehicle V2V of the in-vehicle service, the RSU selects to directly broadcast the received data in the air interface;

If the service type is the car-to-network V2I of the in-vehicle service, the RSU processes the received data at the application layer.

Optionally, the V2X application can be implemented in the RSU.

Optionally, the method further includes: after supporting the V2V and/or V2I service, the RSU broadcasts service capability indication information used to indicate that the RSU supports V2V and/or V2I services.

Optionally, if the RSU determines the service type indication information, the corresponding data is data received together with the service type indication information;

If the RSU determines the bearer association information, the corresponding data is the data transmitted on the corresponding bearer.

Optionally, before the RSU determines the service type of the corresponding data according to the service type indication information, the RSU further includes:

The RSU determines the service type indication information by parsing the information of the PC5 interface medium access control MAC layer or the application layer.

Optionally, the RSU supports a local gateway L-GW function, and the RSU establishes a connection between a user plane local bearer and an Application;

Before determining, by the RSU, the service type of the corresponding data, the RSU further includes: determining, by the RSU, the information of the Uu interface application layer or the MAC layer or the radio link control RLC layer or the packet data aggregation protocol PDCP layer. Service type indication information;

Before the RSU determines the service type of the corresponding data according to the bearer association information, the method further includes: determining, by the RSU, the bearer association information by using the S1 interface.

Optionally, before the RSU determines the bearer association information by using the S1 interface, the RSU further includes:

If the RSU supports V2V and/or V2I services in the in-vehicle service, the RSU sends an S1 application protocol initial terminal message S1-AP Initial UE message and/or uplink non-transmission to the mobility management entity MME in the bearer setup process. The access layer transmits the Internet Protocol IP address of the L-GW in the UpLink NAS Transport message and supports it. In-vehicle service indication information or access point name APN information; or

If the RSU supports V2V and/or V2I services in the in-vehicle service, the RSU carries an IP matching the supported in-vehicle service in the S1 setup request S1Setup Reuqest and/or the evolved base station configuration upgrade eNB Configuration Update message of the S1 interface. Address information.

The RSU establishes an internal direct tunnel of the user plane evolved base station eNB to the L-GW according to the received bearer association indication information from the mobility management entity MME.

Another method for performing data processing provided by the application includes:

The terminal determines data of the in-vehicle service that needs to be sent;

Transmitting, by the terminal, the service type indication information corresponding to the data to the RSU, or sending the data to the RSU by using the bearer corresponding to the data, so that the RSU determines the service type corresponding to the received data, and according to the data service Type, choose to broadcast the received data directly on the air interface or process the received data at the application layer.

Optionally, the terminal sends, to the RSU, the service type indication information used to indicate the data, including:

The terminal sends the service type indication information for indicating data to the RSU through the MAC layer or the application layer of the PC5 interface.

Optionally, before the sending, by the terminal, the data to the RSU by using the bearer corresponding to the data, the method further includes:

The terminal selects an RSU that supports the in-vehicle service according to the broadcast message in the bearer establishment process, and carries the in-vehicle service indication information or the APN information in the NAS message or the RRC message.

Optionally, the terminal sends the data to the RSU by using the bearer corresponding to the data, including:

If the in-vehicle service is a V2V, the terminal sends the V2V service data on the bearer of the Uu port corresponding to the V2V;

If the in-vehicle service is V2I, the terminal sends V2I service data on the bearer of the Uu port corresponding to the V2I.

Another method for performing data processing provided by the embodiment of the present application, the method includes:

The MME determines, according to the subscription information of the UE and the service support capability of the RSU, that the bearer corresponding to the in-vehicle service is established for the terminal;

The MME notifies the RSU of the bearer association information in the bearer establishment process, so that the RSU determines the service type of the corresponding data according to the bearer association information, and selects the data directly received in the air interface according to the service type of the data or The received data is processed at the application layer.

Optionally, the method further includes:

The MME selects the L-GW in the RSU as the P-GW connected to the PDN in the bearer setup process, and connects to the Application in the RSU;

The MME notifies the IP address of the L-GW and the TEID of the tunnel in the Initial Context Setup Request and/or the E-RAB SETUP REQUEST message of the S1-AP, and carries the bearer association information.

An RSU for performing data processing according to an embodiment of the present application, the RSU includes:

a first determining module, configured to determine a service type of the corresponding data according to the service type indication information or the bearer association information;

The processing module is configured to: according to the service type of the data, select to directly receive the received data in the air interface or process the received data at the application layer.

Optionally, the processing module is specifically configured to:

If the service type is V2V of the in-vehicle service, the data selected to be directly broadcasted on the air interface is selected;

If the service type is V2I of the in-vehicle service, the received data is processed at the application layer.

Optionally, the V2X application can be implemented in the RSU.

Optionally, the processing module is further configured to: after supporting the V2V and/or the V2I service, broadcast service capability indication information used to indicate that the RSU supports V2V and/or V2I services.

Optionally, if the first determining module determines the service type indication information, the corresponding data is data received together with the service type indication information;

If the first determining module determines the bearer association information, the corresponding data is data transmitted on the corresponding bearer.

Optionally, the first determining module is further configured to: determine service type indication information by parsing information of a MAC layer or an application layer of the PC5 interface.

Optionally, the RSU supports the L-GW function, and the RSU establishes a connection between the user plane local bearer and the Application; the first determining module is further configured to:

The service type indication information is determined by parsing the information of the Uu interface application layer or the MAC layer or the RLC layer or the PDCP layer; or the bearer association information is determined through the S1 interface.

Optionally, the first determining module is further configured to:

Before the bearer association information is determined by the S1 port, if the RSU supports the V2V and/or V2I service in the in-vehicle service, the S1-AP Initial UE message and/or the UpLink NAS Transport message sent to the MME in the bearer setup process. Carry the IP address of the L-GW and the supported in-vehicle service indication information or APN information; or

Before the bearer association information is determined through the S1 port, if the RSU supports the V2V and/or V2I service in the in-vehicle service, the S1Setup Reuqest and/or the eNB Configuration Update message of the S1 interface carries the IP matching the supported in-vehicle service. Address information.

Optionally, the first determining module is further configured to: before determining the bearer association information by using the S1 interface, establish an internal direct tunnel of the user plane eNB to the L-GW according to the received bearer association indication information from the MME.

A terminal for performing data processing according to an embodiment of the present application, the terminal includes:

a second determining module, configured to determine data of an in-vehicle service that needs to be sent;

a sending module, configured to send the service type indication information corresponding to the data to the RSU, or send the data to the RSU by using the bearer corresponding to the data, so that the RSU determines the service type corresponding to the received data, and according to the data The type of service that chooses to broadcast the received data directly on the air interface or to process the received data at the application layer.

Optionally, the sending module is specifically configured to: send, by using a PC5 interface, a MAC layer or an application layer, service type indication information for indicating data to the RSU.

Optionally, the sending module is further configured to: before the data is sent to the RSU by using the bearer corresponding to the data, select an RSU that supports the in-vehicle service according to the broadcast message in the bearer establishment process, in the NAS message or the RRC message. Carrying in-vehicle service indication information or APN information.

Optionally, the sending module is specifically configured to:

If the in-vehicle service is V2V, the V2V service data is sent on the bearer of the Uu port corresponding to the V2V;

If the in-vehicle service is V2I, the V2I service data is sent on the bearer of the Uu port corresponding to the V2I.

An MME that performs data processing according to an embodiment of the present application, the MME includes:

a third determining module, configured to determine, according to the subscription information of the UE and the service support capability of the RSU, the bearer corresponding to the in-vehicle service established by the terminal;

The notification module is configured to notify the RSU of the bearer association information in the bearer establishment process, so that the RSU determines the service type of the corresponding data according to the bearer association information, and selects the data directly broadcasted in the air interface according to the service type of the data. Or the received data will be processed at the application layer.

Optionally, the notification module is further configured to:

Selecting the L-GW in the RSU as the P-GW of the PDN connection in the bearer establishment process, and connecting to the Application in the RSU;

The IP address of the L-GW and the TEID of the tunnel are notified in the Initial Context Setup Request and/or the E-RAB SETUP REQUEST message of the S1-AP, and bearer association information is carried.

Another RSU for data processing provided by the embodiment of the present application includes:

A processor for reading a program in the memory, performing the following process:

Determining the service type of the corresponding data according to the service type indication information or the bearer association information; selecting, according to the service type of the data, directly receiving the data received in the air interface or processing the received data at the application layer;

A transceiver for receiving and transmitting data under the control of the processor.

Another terminal for performing data processing provided by the embodiment of the present application includes:

Determining data of the in-vehicle service to be transmitted; controlling the transceiver to send the service type indication information corresponding to the data to the RSU or transmitting the data to the RSU by using the bearer corresponding to the data, so that the RSU determines that the received data corresponds to Type of service, and according to the type of service of the data, choose to directly receive the data received in the air interface or process the received data at the application layer;

Another MME for performing data processing provided by the embodiment of the present application includes:

Determining, according to the subscription information of the terminal and the service support capability of the RSU, the bearer corresponding to the in-vehicle service for the terminal; and notifying the RSU of the bearer association information in the bearer setup process, so that the RSU determines the corresponding data according to the bearer association information. The service type, and according to the service type of the data, choose to directly broadcast the received data in the air interface or process the received data at the application layer;

In the embodiment of the present application, the RSU determines the service type of the corresponding data according to the service type indication information or the bearer association information. According to the service type of the data, the data received by the air interface is directly broadcasted or the received data is processed at the application layer. Because the RSU can choose to directly broadcast the received data in the air interface or process the received data at the application layer according to the service type of the data, the RSU can process the vehicle network data.

DRAWINGS

1A is a schematic diagram of data of user equipment communication in a cellular network in the background art;

1B is a schematic diagram of data of direct connection communication of user equipment in the background art;

2 is a schematic structural diagram of a system for performing data processing according to an embodiment of the present application;

3 is a schematic structural diagram of a first type of RSU according to an embodiment of the present application;

4 is a schematic structural diagram of a first terminal according to an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a first MME according to an embodiment of the present application;

6 is a schematic structural diagram of a second RSU according to an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a second terminal according to an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a second MME according to an embodiment of the present application;

FIG. 9 is a schematic flowchart of a first method for performing data processing according to an embodiment of the present application;

10 is a schematic flowchart of a second method for performing data processing according to an embodiment of the present application;

11 is a schematic flowchart of a third method for performing data processing according to an embodiment of the present application;

FIG. 12 is a schematic diagram of data processing performed by using a PC5 interface according to an embodiment of the present application;

13 is a schematic diagram of a user plane protocol stack of a PC5 interface according to an embodiment of the present application;

FIG. 14 is a schematic diagram of data processing using a Uu interface according to an embodiment of the present application.

detailed description

The embodiments of the present application are further described in detail below with reference to the accompanying drawings.

As shown in FIG. 2, the system for performing data processing in the embodiment of the present application includes: an RSU 10 and a terminal 20.

The RSU 10 is configured to determine a service type of the corresponding data according to the service type indication information or the bearer association information, and select, according to the service type of the data, the data directly received by the air interface or the received data to be processed at the application layer.

The terminal 20 is configured to determine data of the in-vehicle service that needs to be sent, send the service type indication information corresponding to the data to the RSU, or send the data to the RSU by using the bearer corresponding to the data.

In the embodiment of the present application, the RSU 10 selects the data received directly in the air interface broadcast or processes the received data in the application layer for different service types.

Optionally, if the service type is V2V of the in-vehicle service, the RSU selects to directly broadcast the received data in the air interface;

If the service type is V2I of the in-vehicle service, the RSU processes the received data at the application layer.

It should be noted that the above two in-vehicle services are only examples, and other types of services that need to directly broadcast the data received in the air interface or the data to be received at the application layer are applicable to the embodiments of the present application.

Optionally, the V2X application (application) can be implemented in the RSU; that is, the solution of the embodiment of the present application is implemented by using the V2X application in the RSU.

In an implementation, the RSU may further broadcast service capability indication information for indicating that the RSU supports V2V and/or V2I services after supporting V2V and/or V2I services;

Correspondingly, after determining that the RSU can also support V2V and/or V2I services, the terminal can initiate V2V and/or V2I services.

The specific judgment manners of the different information received by the terminal in the embodiment of the present application are also different, and are respectively described below.

Method 1: Service type indication information

The first mode is that the terminal notifies the service type of the data corresponding to the RSU by using the service type indication information; the RSU determines the specific data processing mode according to the service type.

For the first mode, the terminal may send the service type indication information for indicating data to the RSU through the PC5 interface.

If the packet is sent through the PC5 interface, the service type indication information for indicating data can be sent to the RSU through the Medium Access Control (MAC) layer or the application layer of the PC5 interface.

Correspondingly, the RSU receives the service type indication information through the MAC layer or the application layer of the PC5 interface.

For the first mode, if the RSU supports the local gateway (L-GW) function, and the RSU establishes a connection between the user plane local bearer and the application, the terminal may also use the Uu interface to indicate a service type indication for the data. The information is sent to the RSU.

Optionally, the RSU establishes a connection between the user plane local bearer and the Application, which may be locally carried by the user plane. Connect to the Application.

If it is sent through the Uu interface, it can be used to indicate data services through the Uu interface application layer or the MAC layer or the Radio Link Control (RLC) layer or the Packet Data Convergence Protocol (PDCP) layer. Type indication information is sent to the RSU.

Correspondingly, the RSU determines the service type indication information by parsing the information of the Uu interface application layer or the MAC layer or the RLC layer or the PDCP layer.

For mode 1, the terminal may send the data corresponding to the service type indication information to the RSU along with the service type indication information.

Correspondingly, the RSU receives the data and the service type indication information together, and the RSU uses the data received together with the service type indication information as the data corresponding to the service indication information.

That is, after receiving the service type indication information, the RSU processes the data received together with the service type indication information according to the determined data processing manner.

For example, the RSU receives the service type indication information and the data A at the same time, and determines that the received data is directly broadcasted on the air interface, and the RSU directly broadcasts the data A on the air interface.

For the first mode, if the terminal sends the service type indication information for indicating the data to the RSU through the Uu interface, the embodiment of the present application may also be in the process of establishing a service, and establishing a packet data network (PDN) connection. Make some adaptive improvements.

For example, before the terminal sends the data to the RSU by using the bearer corresponding to the data, the RSU that supports the in-vehicle service is selected according to the broadcast message in the bearer establishment process, and the non-access layer (Non Access Stratum, NAS) message or The Radio Resource Control (RRC) message carries the in-vehicle service indication information or the Access Point Name (APN) information (which may be carried in the NAS message or the RRC message).

Correspondingly, the Mobility Management Entity (MME) selects the L-GW in the RSU as the P-GW connected to the PDN in the bearer setup process, and connects to the Application of the RSU.

Notifying the L-GW in the Initial Context Setup Request and/or E-RAB SETUP REQUEST message of the S1 Application Protocol (S1-AP) The Internet Protocol (IP) address and the Tunnel End Point Identifier (TEID) of the tunnel.

Correspondingly, if the RSU supports V2V and/or V2I services in the in-vehicle service, the RSU sends an S1-AP Initial UE message (S1 Application Protocol Initial Terminal Message) and/or UpLink to the MME in the bearer setup process. The NAS Transport (uplink non-access stratum transmission) message carries the IP address of the L-GW and the supported in-vehicle service indication information; or

If the RSU supports V2V and/or V2I services in the in-vehicle service, the RSU is carried in an S1 Setup Reuqest (S1 Setup Request) and/or an eNB Configuration Update (Evolved Base Station Configuration Upgrade) message of the S1 interface. IP address information that matches the supported in-vehicle service.

Method 2: Carrying associated information

The second mode is that the bearer differentiates the service type, and different bearers correspond to data of different service types. For example, if V2V corresponds to bearer 1, the data of V2V is sent through bearer 1.

After receiving data through a bearer, the RSU determines the service type corresponding to the bearer according to the bearer association information, and processes the data received by the bearer according to the processing manner corresponding to the service type.

That is to say, the data corresponding to the bearer associated information is the data transmitted on the corresponding bearer.

For example, according to the bearer association information, it is determined that the service type corresponding to the bearer 1 is V2V, and the data received by the bearer 1 is directly broadcast on the air interface.

Optionally, the RSU may receive the bearer association information by using an Evolved Packet System (EPS) bearer configuration information on the S1 interface.

For the second method, the system of the embodiment of the present application may further include:

The MME is configured to determine, according to the subscription information of the terminal and the service support capability of the RSU, the bearer corresponding to the in-vehicle service, and notify the RSU of the bearer association information in the bearer establishment process, so that the RSU determines the corresponding information according to the bearer association information. The service type of the data, and according to the service type of the data, choose to directly broadcast the received data in the air interface or process the received data at the application layer.

For the second method, the embodiment of the present application can perform some adaptive improvement in the process of establishing a service, establishing a PDN connection, and the like.

For example, before the terminal sends the data to the RSU by using the bearer corresponding to the data, the RSU that supports the in-vehicle service is selected according to the broadcast message in the bearer establishment process, and the in-vehicle service indication information is carried in the NAS message or the RRC message. APN information.

Correspondingly, the MME selects the L-GW in the RSU as the P-GW of the PDN connection in the bearer setup process, and connects to the Application of the RSU;

Correspondingly, if the RSU supports V2V and/or V2I services in the in-vehicle service, the RSU carries the L-GW in the S1-AP Initial UE message and/or the UpLink NAS Transport message sent to the MME in the bearer setup process. IP address and supported in-vehicle service instructions; or

If the RSU supports V2V and/or V2I services in the in-vehicle service, the RSU carries IP address information matching the supported in-vehicle service in the S1 Setup Reuqest and/or eNB Configuration Update message of the S1 interface.

In implementation, the RSU can also be placed in a base station or terminal.

If the RSU is placed in the base station, both the first mode and the second mode are applicable. If the RSU is placed in the terminal, then The PC5 port in the first mode is applicable.

As shown in FIG. 3, the first type of RSU in this embodiment of the present application includes:

The first determining module 300 is configured to determine, according to the service type indication information or the bearer association information, a service type of the corresponding data.

The processing module 301 is configured to: according to the service type of the data, select to directly broadcast the received data in the air interface or process the received data at the application layer.

Optionally, the processing module 301 is specifically configured to:

Optionally, the V2X Application can be implemented in the RSU.

Optionally, the processing module 301 is further configured to:

After supporting the V2V and/or V2I services, the service capability indication information indicating that the RSU supports the V2V and/or V2I services is broadcasted.

Optionally, the first determining module 300 is further configured to:

The service type indication information is determined by parsing the information of the MAC layer or the application layer of the PC5 interface.

Optionally, the RSU supports an L-GW function, and the RSU establishes a connection between a user plane local bearer and an Application;

The first determining module 300 is further configured to: determine the service type indication information by parsing the information of the Uu interface application layer or the MAC layer or the RLC layer or the PDCP layer; or determine the bearer association information by using the S1 interface.

Optionally, the first determining module 300 is further configured to:

Optionally, the first determining module 300 is further configured to: before determining the bearer association information by using the S1 interface, establish an internal direct tunnel of the user plane eNB to the L-GW according to the received bearer association indication information from the MME.

As shown in FIG. 4, the first terminal in this embodiment of the present application includes:

a second determining module 400, configured to determine data of an in-vehicle service that needs to be sent;

The sending module 401 is configured to send the service type indication information corresponding to the data to the RSU, or send the data to the RSU by using the bearer corresponding to the data, so that the RSU determines the service type corresponding to the received data, and according to The type of data service, choose to broadcast the received data directly on the air interface or process the received data at the application layer.

Optionally, the sending module 401 is specifically configured to:

The service type indication information for indicating data is sent to the RSU through the MAC layer or the application layer of the PC5 interface.

Optionally, the sending module 401 is further configured to:

Before the data is sent to the RSU by using the bearer corresponding to the data, the RSU supporting the in-vehicle service is selected according to the broadcast message in the bearer establishment process, and the in-vehicle service indication information or the APN information is carried in the NAS message or the RRC message.

Optionally, the sending module 401 is specifically configured to:

As shown in FIG. 5, the first MME in this embodiment of the present application includes:

The third determining module 500 is configured to determine, according to the subscription information of the terminal and the service support capability of the RSU, the bearer corresponding to the in-vehicle service established by the terminal;

The notification module 501 is configured to notify the RSU of the bearer association information in the bearer setup process, so that the RSU determines the service type of the corresponding data according to the bearer association information, and selects the broadcast directly received in the air interface according to the service type of the data. Data or data to be received is processed at the application layer.

Optionally, the notification module 501 is further configured to:

As shown in FIG. 6, the second RSU of the embodiment of the present application includes:

The processor 601 is configured to read a program in the memory 604 and perform the following process:

The service type of the corresponding data is determined according to the service type indication information or the bearer association information. According to the service type of the data, the data received by the air interface is directly broadcasted or the received data is processed at the application layer.

The transceiver 602 is configured to receive and transmit data under the control of the processor 601.

Optionally, the processor 601 is specifically configured to:

Optionally, the V2X application can be implemented in the RSU.

Optionally, the processor 601 is further configured to: after supporting the V2V and/or V2I service, broadcast to indicate the The RSU supports the service capability indication information of the V2V and/or V2I services.

Optionally, the processor 601 is further configured to: determine service type indication information by parsing information of a MAC layer or an application layer of the PC5 interface.

Optionally, the RSU supports the L-GW function, and the RSU establishes a connection between the user plane local bearer and the Application; the processor 601 is further configured to: parse the Uu interface application layer or the MAC layer or the RLC layer Or the information of the PDCP layer determines the service type indication information; or determines the bearer association information through the S1 interface.

Optionally, the processor 601 is further configured to:

Optionally, the processor 601 is further configured to: before determining the bearer association information by using the S1 interface, establish an internal direct tunnel of the user plane eNB to the L-GW according to the received bearer association indication information from the MME.

In FIG. 6, a bus architecture (represented by bus 600), bus 600 may include any number of interconnected buses and bridges, and bus 600 will include one or more processors represented by processor 601 and memory represented by memory 604. The various circuits are linked together. The bus 600 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein. Bus interface 603 provides an interface between bus 600 and transceiver 602. Transceiver 602 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium. Data processed by processor 601 is transmitted over wireless medium via antenna 605. Further, antenna 605 also receives the data and transmits the data to processor 601.

The processor 601 is responsible for managing the bus 600 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 604 can be used to store data used by the processor 601 in performing operations.

Optionally, the processor 601 may be a CPU (Central Embedded Device), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device). , complex programmable logic devices).

As shown in FIG. 7, the second terminal in this embodiment of the present application includes:

The processor 701 is configured to read a program in the memory 704 and perform the following process:

Determining data of the in-vehicle service to be transmitted; the control transceiver 702 sends the service type indication information corresponding to the data to the RSU or sends the data to the RSU through the bearer corresponding to the data, so that the RSU determines the received data. Corresponding service type, and according to the service type of the data, choose to directly broadcast the received data in the air interface or process the received data at the application layer.

The transceiver 702 is configured to receive and transmit data under the control of the processor 701.

Optionally, the processor 701 is specifically configured to: control the transceiver 702 to send, by using a PC5 interface MAC layer or an application layer, service type indication information for indicating data to the RSU.

Optionally, the processor 701 is further configured to: before the transceiver 702 sends the data to the RSU by using the bearer corresponding to the data, select an RSU supporting the in-vehicle service according to the broadcast message in the bearer setup process, in the NAS. The message or the RRC message carries the activated in-vehicle service indication information or the APN information.

Optionally, the processor 701 is specifically configured to:

If the in-vehicle service is V2V, the control transceiver 702 sends V2V service data on the bearer of the Uu port corresponding to the V2V;

If the in-vehicle service is V2I, the control transceiver 702 sends V2I service data on the bearer of the Uu port corresponding to the V2I.

In FIG. 7, a bus architecture (represented by bus 700), which may include any number of interconnected buses and bridges, will include one or more processors and memory 704 represented by general purpose processor 701. The various circuits of the memory are linked together. The bus 700 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art and, therefore, will not be further described herein. Bus interface 703 provides an interface between bus 700 and transceiver 702. Transceiver 702 can be an element or a plurality of elements, such as multiple receivers and transmitters, providing means for communicating with various other devices on a transmission medium. For example, transceiver 702 receives external data from other devices. The transceiver 702 is configured to send the processed data of the processor 701 to other devices. Depending on the nature of the computing system, a user interface 705 can also be provided, such as a keypad, display, speaker, microphone, joystick.

The processor 701 is responsible for managing the bus 700 and the usual processing, running a general purpose operating system as described above. The memory 704 can be used to store data used by the processor 701 in performing operations.

Optionally, the processor 701 can be a CPU, an ASIC, an FPGA, or a CPLD.

As shown in FIG. 8, the second MME in this embodiment of the present application includes:

The processor 801 is configured to read a program in the memory 804 and perform the following process:

Determining, according to the subscription information of the terminal and the service support capability of the RSU, the bearer corresponding to the in-vehicle service for the terminal; and notifying the RSU of the bearer association information in the bearer setup process, so that the RSU determines the corresponding data according to the bearer association information. The type of service, and depending on the type of service of the data, choose to broadcast the data directly on the air interface or to receive it. The data arrived is processed at the application layer.

The transceiver 802 is configured to receive and transmit data under the control of the processor 801.

Optionally, the processor 801 is further configured to:

In FIG. 8, a bus architecture (represented by bus 800), bus 800 may include any number of interconnected buses and bridges, and bus 800 will include one or more processors represented by processor 801 and memory represented by memory 804. The various circuits are linked together. The bus 800 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein. Bus interface 803 provides an interface between bus 800 and transceiver 802. Transceiver 802 can be an element or a plurality of elements, such as multiple receivers and transmitters, providing means for communicating with various other devices on a transmission medium. The data processed by the processor 801 is transmitted over the wireless medium via the antenna 805. Further, the antenna 805 also receives the data and transmits the data to the processor 801.

The processor 801 is responsible for managing the bus 800 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 804 can be used to store data used by the processor 801 when performing operations.

Optionally, the processor 801 can be a CPU, an ASIC, an FPGA, or a CPLD.

Based on the same inventive concept, a method for performing data processing is also provided in the embodiment of the present application. The device corresponding to the method is a device in a system for performing data processing in the embodiment of the present application, and the method solves the problem and the method The devices are similar, so the implementation of the method can be referred to the implementation of the device, and the details are not repeated here.

As shown in FIG. 9, the first method for performing data processing in the embodiment of the present application includes:

Step 900: The RSU determines, according to the service type indication information or the bearer association information, a service type of the corresponding data.

Step 901: The RSU selects, according to the service type of the data, directly broadcasts the received data in the air interface or processes the received data at the application layer.

Optionally, the V2X application can be implemented in the RSU.

Before the RSU determines the service type of the corresponding data according to the service type indication information, the RSU further includes:

The RSU determines service type indication information by parsing information of a Uu interface application layer or a MAC layer or a radio link control RLC layer or a packet data aggregation protocol PDCP layer;

Before the RSU determines the service type of the corresponding data according to the bearer association information, the RSU further includes:

The RSU determines the bearer association information through the S1 port.

If the RSU supports V2V and/or V2I services in the in-vehicle service, the RSU sends an S1 application protocol initial terminal message S1-AP Initial UE message and/or uplink non-transmission to the mobility management entity MME in the bearer setup process. The access layer transmits an Internet Protocol IP address of the L-GW and the supported in-vehicle service indication information or the access point name APN information in the UpLink NAS Transport message; or

If the RSU supports V2V and/or V2I services in the in-vehicle service, the RSU carries the matching in-vehicle service in the S1 setup request S1 Setup Reuqest and/or the evolved base station configuration upgrade eNB Configuration Update message of the S1 interface. IP address information.

As shown in FIG. 10, the second method for performing data processing in the embodiment of the present application includes:

Step 1000: The terminal determines data of the in-vehicle service that needs to be sent;

Step 1001: The terminal sends the service type indication information corresponding to the data to the RSU, or sends the data to the RSU by using the bearer corresponding to the data, so that the RSU determines the service type corresponding to the received data, and according to The type of data service, choose to broadcast the received data directly on the air interface or process the received data at the application layer.

Transmitting, by the terminal, a service type indication information for indicating data by using a MAC layer or an application layer of the PC5 interface To the RSU.

As shown in FIG. 11, the third method for performing data processing in the embodiment of the present application includes:

Step 1100: The MME determines, according to the subscription information of the UE and the service support capability of the RSU, that the bearer corresponding to the in-vehicle service is established for the terminal.

Step 1101: The MME notifies the RSU of the bearer association information in the bearer setup process, so that the RSU determines the service type of the corresponding data according to the bearer association information, and selects the broadcast directly received in the air interface according to the service type of the data. Data or data to be received is processed at the application layer.

Optionally, the method further includes:

The scheme of the present application will be described in detail below by way of a few examples.

Embodiment 1 As shown in FIG. 12, the RSU in the embodiment of the present application is located in an eNB, and the PC5 interface protocol is adopted between the UE and the RSU, and the RSU determines that the data packet is transparently forwarded by analyzing the indication information carried in the MAC layer of the PC5 data packet. Still the application layer termination method.

The PC5 interface user plane protocol stack is shown in Figure 13. Optionally, a new service type indication information may be added to the MAC layer of the PC5 interface, indicating a service type or a data processing mode of the data packet, and the UE fills in the MAC layer service type indication information according to the initiated service type.

Correspondingly, after receiving the data packet on the PC5 interface, the RSU parses the service type indication information of the MAC layer. If it is a transparent forwarding mode, the RSU forwards the data packet transparently and broadcasts the information on the air interface. In the case of the application layer termination mode, the RSU will terminate the packet and hand it over to the application layer for processing.

If the service type indication information indicates the service type of the data packet, the base station determines, according to the correspondence between the set service type and the data processing mode, the data processing mode corresponding to the received service type, and correspondingly according to the determined data processing manner. The data packet is processed. For example, if the service type is V2V of the in-vehicle service, the data processing mode is to directly receive the data received in the air interface; if the service type is the V2I of the in-vehicle service, the data processing mode is to perform the received data at the application layer. deal with.

If the service type indication information indicates the data processing mode of the data packet, the base station directly determines the received data processing mode, and processes the corresponding data packet according to the determined data processing manner.

Embodiment 2: As shown in FIG. 12, the RSU is located in the eNB, and the PC5 interface protocol is adopted between the UE and the RSU. The RSU determines the service type indication information carried in the application layer of the PC5 data packet, and determines that the processing of the data packet is transparent forwarding mode. Still the application layer termination method.

The UE carries the service type indication information at the application layer, indicating the service type or the data processing mode of the data packet, and the UE fills in the service type indication information of the application layer according to the initiated service type.

Correspondingly, after receiving the data packet on the PC5 interface, the RSU parses the service type indication information of the application layer. If it is a transparent forwarding mode, the RSU forwards the data packet transparently and broadcasts the information on the air interface. In the case of application layer termination, the RSU will terminate the packet and hand it over to the application layer for processing.

Embodiment 3: As shown in FIG. 14, the RSU is located in the eNB, and the Uu interface protocol is adopted between the UE and the RSU. The RSU supports the L-GW function, and the user plane local bearer is connected to the Application on the RSU, and the RSU establishes the V2V through the Uu interface. The /V2I bearer information determines whether the packet processing is transparent forwarding or application layer termination.

For the third embodiment, some adaptive changes can be made in the process of establishing a service, establishing a PDN connection, etc., and the specific changes are as follows.

1. The UE needs to know whether the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) network supports the V2V/V2I service characteristics, and the E-UTRAN network can broadcast related service capability indication information and broadcast messages in the system. Added relevant indication information in the System Information Block (SIB).

2. The UE selects an eNB that supports the V2V/V2I service feature according to the broadcast message, and requests the network to activate the related service. The UE carries the V2V/V2I service indication information or the APN (Access Point Name) in the NAS message or the RRC message. information.

The NAS signaling may generally include one or more of the following signaling:

Attach Request, service request, PDN connection request, bearer resource allocation request, Bearer resource modification request, Bearer resource modification request.

The RRC message may include one or more of the following signaling: an RRC Connection Request, an RRC Connection Complete message.

3. If the eNB supports the V2V/V2I service, the eNB may carry the relevant IP address in the S1-APInitial UE message (original UE message) and/or the UpLink NAS Transport (uplink non-access layer transmission) message sent to the MME. Information, and V2V/V2I service indication information. or

The eNB carries the IP address information matching the V2V/V2I service in the S1Setup Reuqest (S1 Setup Request) and/or the eNB Configuration Update (Ethernet Basement Configuration Upgrade) message of the S1 interface. After receiving the information, the MME needs to save the information. .

4. The MME determines to establish V2V/ for the UE according to the subscription information of the UE and the service support capability of the eNB (whether or not there is IP address information of the L-GW) and the APN or V2V/V2I service indication information in the NAS or S1-AP message. After the V2I service is carried, the L-GW in the eNB is selected as the P-GW of the PDN connection, and is connected to the Application of the RSU. The MME notifies the IP address of the L-GW and the TEID of the tunnel in the Initial Context Setup Request and/or the E-RAB SETUP REQUEST message of the S1-AP, and carries the bearer. The associated information indicates the special V2V/V2I bearer.

5. The eNB establishes internal direct tunnel information of the user plane eNB to the L-GW according to the bearer association indication information carried by the MME, and saves the bearer association information.

After the control plane signaling connection is completed, the UE sends the relevant V2V/V2I service on the corresponding V2V/V2I bearer of the Uu interface, and the eNB determines whether the data packet is transparent forwarding or application layer termination processing according to the saved bearer association information.

If it is transparent forwarding mode, the data packet will be forwarded transparently and broadcasted on the air interface. In the case of the application layer termination mode, the RSU will terminate the packet and hand it over to the application layer for processing.

Embodiment 4: As shown in FIG. 14, the RSU is located in the eNB, and the Uu interface protocol is adopted between the UE and the RSU. The RSU supports the L-GW function, and the user plane local bearer is connected to the Application on the RSU, and the RSU transmits the data by analyzing the Uu interface. The information carried in the application layer or the MAC layer/RLC layer/PDCP layer is used to determine whether the processing of the data packet is transparent forwarding mode or application layer termination mode.

1. The UE needs to know whether the E-UTRAN supports the V2V/V2I service feature, and the E-UTRAN can broadcast related service capability indication information, and add relevant indication information to the SIB in the system broadcast message.

2. The UE selects an eNB that supports the V2V/V2I service feature according to the broadcast message, and requests the network to activate the related service. The UE carries the V2V/V2I service indication information or the APN information in the NAS message or the RRC message.

The NAS signaling may generally include one or more of the following signaling:

Attach Request, service request, PDN connection request, bearer resource allocation request, Bearer resource modification request.

3. If the eNB supports the V2V/V2I service, the eNB may carry the relevant IP address information and the V2V/V2I service indication information in the S1-APInitial UE message and/or the UpLink NAS Transport message sent to the MME; or the eNB is on the S1 interface. The S1Setup Reuqest and/or eNB Configuration Update message carries the IP address information that matches the V2V/V2I service. After receiving the information, the MME needs to save the information.

4. The MME determines to establish V2V/ for the UE according to the subscription information of the UE and the service support capability of the eNB (whether or not there is IP address information of the L-GW) and the APN or V2V/V2I service indication information in the NAS or S1-AP message. After the V2I service is carried, the L-GW in the eNB is selected as the P-GW of the PDN connection, and is connected to the Application of the RSU. The MME notifies the IP address of the L-GW and the TEID of the tunnel in the Initial Context Setup Request and/or the E-RAB SETUP REQUEST message of the S1-AP.

After the control plane signaling connection is completed, the UE sends the relevant V2V/V2I service on the corresponding V2V/V2I bearer of the Uu interface, and the RSU determines the data packet by analyzing the service type indication information carried by the application layer of the transport packet on the Uu interface. Whether the processing is transparent forwarding or application layer termination. If it is transparent forwarding mode, the data packet will be forwarded transparently and broadcasted on the air interface. In the case of the application layer termination mode, the RSU will terminate the packet and hand it over to the application layer for processing.

Embodiment 5: The RSU is located in the UE, and the PC5 interface protocol is adopted between the UE and the RSU. The RSU determines whether the processing of the data packet is transparent forwarding or application layer termination by parsing the service type indication information carried in the MAC layer of the PC5 data packet.

If the service type indication information indicates the service type of the data packet, the RSU determines the data processing mode corresponding to the received service type according to the correspondence between the set service type and the data processing mode, and correspondingly according to the determined data processing manner. The data packet is processed. For example, if the service type is V2V of the in-vehicle service, the data processing mode is to directly receive the data received in the air interface; if the service type is the V2I of the in-vehicle service, the data processing mode is to perform the received data at the application layer. deal with.

If the service type indication information indicates the data processing mode of the data packet, the RSU directly determines the received data processing mode, and processes the corresponding data packet according to the determined data processing manner.

Embodiment 6: The RSU is located in the UE, and the PC5 interface protocol is adopted between the UE and the RSU. The RSU determines that the processing of the data packet is transparent by analyzing the service type indication information carried in the application layer or the MAC layer/RLC/PDCP layer of the PC5 data packet. Forwarding is also the application layer termination method.

The UE carries the service type indication information at the application layer, indicating the service type or data processing mode of the data packet. The UE fills in the service type indication information of the application layer according to the type of the service that is initiated.

It can be seen from the above that the RSU according to the embodiment of the present application determines the service type of the corresponding data according to the service type indication information or the bearer association information; and according to the service type of the data, selects the data directly received by the air interface or the received data. The application layer processes. Because the RSU can choose to directly broadcast the received data in the air interface or process the received data at the application layer according to the service type of the data, the RSU can process the vehicle network data.

It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims

A method for performing data processing, the method comprising:

The roadside unit RSU determines the service type of the corresponding data according to the service type indication information or the bearer association information.

The RSU selects to directly receive the received data in the air interface or process the received data at the application layer according to the service type of the data.
The method according to claim 1, wherein the RSU selects to directly broadcast the received data in the air interface or process the received data at the application layer according to the service type of the data, including:

If the service type is the car-to-vehicle V2V of the in-vehicle service, the RSU selects to directly broadcast the received data in the air interface;

If the service type is the car-to-network V2I of the in-vehicle service, the RSU processes the received data at the application layer.
The method of claim 2, wherein the V2X application is implemented in the RSU.
The method of claim 2, further comprising:

After supporting the V2V and/or V2I services, the RSU broadcasts service capability indication information indicating that the RSU supports V2V and/or V2I services.
The method according to claim 1, wherein if the RSU determines service type indication information, the corresponding data is data received together with the service type indication information;

If the RSU determines bearer association information, the corresponding data is data transmitted on the corresponding bearer.
The method according to claim 1, wherein the RSU further includes: before determining the service type of the corresponding data according to the service type indication information:

The RSU determines the service type indication information by parsing the information of the PC5 interface medium access control MAC layer or the application layer.
The method of claim 1, wherein the RSU supports a local gateway L-GW function, and the RSU establishes a connection between a user plane local bearer and an Application;

Before the RSU determines the service type of the corresponding data according to the service type indication information, the RSU further includes:

The RSU determines service type indication information by parsing information of a Uu interface application layer or a MAC layer or a radio link control RLC layer or a packet data aggregation protocol PDCP layer;

Before the RSU determines the service type of the corresponding data according to the bearer association information, the RSU further includes:

The RSU determines the bearer association information through the S1 port.
The method of claim 7, wherein the RSU before the determining the bearer association information by using the S1 port further includes:

If the RSU supports V2V and/or V2I services in the in-vehicle service, the RSU sends an S1 application protocol initial terminal message S1-AP Initial UE message and/or to the mobility management entity MME during bearer setup. The uplink non-access stratum transmits the Internet Protocol IP address of the L-GW and the supported in-vehicle service indication information or the access point name APN information in the UpLink NAS Transport message; or

If the RSU supports V2V and/or V2I services in the in-vehicle service, the RSU carries an IP matching the supported in-vehicle service in the S1 setup request S1Setup Reuqest and/or the evolved base station configuration upgrade eNB Configuration Update message of the S1 interface. Address information.
The method according to claim 7 or 8, wherein before the RSU determines the bearer association information through the S1 port, the RSU further includes:

The RSU establishes an internal direct tunnel of the user plane evolved base station eNB to the L-GW according to the received bearer association indication information from the mobility management entity MME.
A method for performing data processing, the method comprising:

The terminal determines data of the in-vehicle service that needs to be sent;

Transmitting, by the terminal, the service type indication information corresponding to the data to the RSU, or sending the data to the RSU by using the bearer corresponding to the data, so that the RSU determines the service type corresponding to the received data, and according to the data service Type, choose to broadcast the received data directly on the air interface or process the received data at the application layer.
The method of claim 10, wherein the terminal sends the service type indication information for indicating data to the RSU, including:

The terminal sends the service type indication information for indicating data to the RSU through the MAC layer or the application layer of the PC5 interface.
The method according to claim 10, wherein before the terminal sends the data to the RSU by using the bearer corresponding to the data, the method further includes:

The terminal selects an RSU that supports the in-vehicle service according to the broadcast message in the bearer establishment process, and carries the in-vehicle service indication information or the APN information in the NAS message or the RRC message.
The method of claim 10, wherein the terminal sends the data to the RSU by using a bearer corresponding to the data, including:

If the in-vehicle service is a V2V, the terminal sends the V2V service data on the bearer of the Uu port corresponding to the V2V;

If the in-vehicle service is V2I, the terminal sends V2I service data on the bearer of the Uu port corresponding to the V2I.
A method for performing data processing, the method comprising:

The MME determines, according to the subscription information of the terminal and the service support capability of the RSU, that the bearer corresponding to the in-vehicle service is established for the terminal;

The MME notifies the RSU of the bearer association information in the bearer establishment process, so that the RSU determines the service type of the corresponding data according to the bearer association information, and selects the data directly received in the air interface according to the service type of the data or The received data is processed at the application layer.
The method of claim 14 further comprising:

The MME selects the L-GW in the RSU as the P-GW connected to the PDN in the bearer setup process, and connects to the Application in the RSU;

The MME notifies the IP address of the L-GW and the TEID of the tunnel in the Initial Context Setup Request and/or the E-RAB SETUP REQUEST message of the S1-AP, and carries the bearer association information.
An RSU for performing data processing, characterized in that the RSU comprises:

a first determining module, configured to determine a service type of the corresponding data according to the service type indication information or the bearer association information;

The processing module is configured to: according to the service type of the data, select to directly receive the received data in the air interface or process the received data at the application layer.
The RSU of claim 16, wherein the processing module is specifically configured to:

If the service type is V2V of the in-vehicle service, the data selected to be directly broadcasted on the air interface is selected;

If the service type is V2I of the in-vehicle service, the received data is processed at the application layer.
The RSU of claim 17 wherein a V2X application is implemented within said RSU.
The RSU of claim 17 wherein said processing module is further configured to:

After supporting the V2V and/or V2I services, the service capability indication information indicating that the RSU supports the V2V and/or V2I services is broadcasted.
The RSU according to claim 16, wherein if the first determining module determines the service type indication information, the corresponding data is data received together with the service type indication information;

If the first determining module determines the bearer association information, the corresponding data is data transmitted on the corresponding bearer.
The RSU of claim 16, wherein the first determining module is further configured to:

The service type indication information is determined by parsing the information of the MAC layer or the application layer of the PC5 interface.
The RSU of claim 16, wherein the RSU supports an L-GW function, and the RSU establishes a connection between a user plane local bearer and an Application;

The first determining module is further configured to:

The service type indication information is determined by parsing the information of the Uu interface application layer or the MAC layer or the RLC layer or the PDCP layer; or the bearer association information is determined through the S1 interface.
The RSU of claim 22, wherein the first determining module is further configured to:

Before the bearer association information is determined by the S1 port, if the RSU supports the V2V and/or V2I service in the in-vehicle service, the S1-AP Initial UE message and/or the UpLink NAS Transport message sent to the MME in the bearer setup process. Carry the IP address of the L-GW and the supported in-vehicle service indication information or APN information; or

Before the bearer association information is determined through the S1 port, if the RSU supports the V2V and/or V2I service in the in-vehicle service, the S1Setup Reuqest and/or the eNB Configuration Update message of the S1 interface carries the IP matching the supported in-vehicle service. Address information.
The RSU of claim 22 or 23, wherein the first determining module is further configured to:

Before the bearer association information is determined through the S1 interface, the internal direct tunnel of the user plane eNB to the L-GW is established according to the received bearer association indication information from the MME.
A terminal for performing data processing, characterized in that the terminal comprises:

a second determining module, configured to determine data of an in-vehicle service that needs to be sent;

a sending module, configured to send the service type indication information corresponding to the data to the RSU, or send the data to the RSU by using the bearer corresponding to the data, so that the RSU determines the service type corresponding to the received data, and according to the data The type of service that chooses to broadcast the received data directly on the air interface or to process the received data at the application layer.
The terminal according to claim 25, wherein the sending module is specifically configured to:

The service type indication information for indicating data is sent to the RSU through the MAC layer or the application layer of the PC5 interface.
The terminal according to claim 25, wherein the sending module is further configured to:

Before the data is sent to the RSU by using the bearer corresponding to the data, the RSU supporting the in-vehicle service is selected according to the broadcast message in the bearer establishment process, and the in-vehicle service indication information or the APN information is carried in the NAS message or the RRC message.
The terminal according to claim 25, wherein the sending module is specifically configured to:

If the in-vehicle service is V2V, the V2V service data is sent on the bearer of the Uu port corresponding to the V2V;

If the in-vehicle service is V2I, the V2I service data is sent on the bearer of the Uu port corresponding to the V2I.
An MME for performing data processing, where the MME includes:

a third determining module, configured to determine, according to the subscription information of the UE and the service support capability of the RSU, the bearer corresponding to the in-vehicle service established by the terminal;

The notification module is configured to notify the RSU of the bearer association information in the bearer establishment process, so that the RSU determines the service type of the corresponding data according to the bearer association information, and selects the data directly broadcasted in the air interface according to the service type of the data. Or the received data will be processed at the application layer.
The MME according to claim 29, wherein the notification module is further configured to:

Selecting the L-GW in the RSU as the P-GW of the PDN connection in the bearer establishment process, and connecting to the Application in the RSU;

The IP address of the L-GW and the TEID of the tunnel are notified in the Initial Context Setup Request and/or the E-RAB SETUP REQUEST message of the S1-AP, and bearer association information is carried.
An RSU for performing data processing, characterized in that the RSU comprises:

The processor is configured to read a program in the memory, and perform the following process: determining a service type of the corresponding data according to the service type indication information or the bearer association information; and selecting, according to the service type of the data, directly receiving the data received in the air interface or The received data is processed at the application layer;

A transceiver for receiving and transmitting data under the control of the processor.
A terminal for performing data processing, characterized in that the terminal comprises:

a processor, configured to read a program in the memory, and perform the following process: determining data of the in-vehicle service to be sent; and controlling the transceiver to send the service type indication information corresponding to the data to the RSU or by using the bearer corresponding to the data The data is sent to the RSU, so that the RSU determines the service type corresponding to the received data, and according to the service type of the data, selects to directly broadcast the received data in the air interface or process the received data at the application layer;

A transceiver for receiving and transmitting data under the control of the processor.
An MME for performing data processing, where the MME includes:

The processor is configured to read the program in the memory, and perform the following process: determining, according to the subscription information of the terminal and the service support capability of the RSU, the bearer corresponding to the in-vehicle service established by the terminal; and notifying the bearer associated information in the bearer establishment process The RSU is configured to determine, according to the bearer association information, the service type of the corresponding data, and according to the service type of the data, select to directly broadcast the received data in the air interface or process the received data at the application layer;

A transceiver for receiving and transmitting data under the control of the processor.