Information processing method, device and system, electronic equipment and readable storage medium

Abstract

The embodiment of the invention provides an information processing method, device and system, electronic equipment and a readable storage medium, and relates to the technical fields of traffic, vehicle-road cooperation, cloud technology and the like. The method adopts a scheme of realizing a V2X application layer on MEC equipment or an edge cloud, and the method comprises the following steps: in response to first V2X messages related to OBUs and respectively sent by at least one RSU, analyzing at least one first V2X message by the V2X application layer included in the MEC equipment or the edge cloud; under the condition that the V2X application layer determines the response content for the OBU, determining a target RSU currently corresponding to the OBU according to the at least one first V2X message; and the response content is sent to the target RSU, so that the target RSU forwards the response content to the OBU, namely, a set of unified V2X application service logic is realized on the MEC equipment or the edge cloud side, and the system efficiency is effectively improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle-road collaborative technology. Specifically, the present application relates to an information processing method, device, system, electronic device and readable storage medium. Background Art

[0002] The vehicle-road cooperative system is an intelligent transportation system that uses information interaction between vehicles and roads to establish integrated and coordinated operation of people, vehicles and roads. It is of great significance to improving the efficiency and safety of the transportation system and achieving the sustainable development of the transportation system.

[0003] In the vehicle-road cooperative system proposed in the related art, the RSU mainly has a three-layer protocol stack, including the application layer, the network layer and the access layer, among which the RSU can respond to the vehicle's request through the application layer. However, for some information interaction scenarios between vehicles and roads, such a request response process is inefficient, resulting in reduced efficiency of the entire system. Summary of the invention

[0004] The purpose of the embodiments of the present application is to solve the problem of low efficiency of the vehicle-road cooperative system.

[0005] In a first aspect, an embodiment of the present application provides an information processing method, which is applied to an MEC device or an edge cloud, where the MEC device or the edge cloud includes a V2X application layer, and the method includes:

[0006] In response to a first V2X message related to the OBU sent by at least one RSU respectively, the V2X application layer parses the at least one first V2X message;

[0007] When the V2X application layer determines the response content for the OBU, determine the target RSU currently corresponding to the OBU according to at least one first V2X message;

[0008] The response content is sent to the target RSU so that the target RSU forwards the response content to the OBU.

[0009] In an optional implementation, the MEC device or edge cloud further includes a V2X message middleware, which sends the response content to the target RSU, including:

[0010] The V2X message middleware determines a first data field corresponding to the response content, packages the first data field and the response content according to a predetermined message format, generates a corresponding second V2X message, and sends the second V2X message to the target RSU;

[0011] The V2X application layer parses at least one first V2X message, including:

[0012] The V2X message middleware parses at least one first V2X message, obtains a second data field respectively included in the at least one first V2X message, and stores the second data field.

[0013] In an optional implementation, the first data field includes at least one of the following: a first sender identifier, a first receiver identifier, a network layer protocol identifier, a first message content type identifier, a first message length, a message priority, a network layer sending mode, a message sending cycle, and a first actual message content;

[0014] The first sender identifier is used to identify the MEC device or edge cloud;

[0015] The first receiver identifier is used to identify the target RSU.

[0016] In an optional implementation, the second data field includes at least one of the following: a second sender identifier, a second receiver identifier, a second message content type identifier, a second message length, and a second actual message content;

[0017] The second sender identifier is used to identify the RSU that sends the first V2X message;

[0018] The second receiver identifier is used to identify the MEC device or edge cloud.

[0019] In an optional implementation, the V2X application layer includes a codec, and sends the response content to the target RSU, including:

[0020] Encoding the response content into a corresponding second V2X message through a codec;

[0021] Sending a second V2X message to a target RSU, where the target RSU includes at least one V2X link;

[0022] The V2X application layer parses at least one first V2X message, including:

[0023] At least one first V2X message is decoded into corresponding first service data content through a codec.

[0024] In an optional implementation, if the first V2X message includes a request message, the response content includes second service data content obtained after performing service logic processing on the first V2X message;

[0025] If the first V2X message includes a non-request message, the response content includes a third business data content determined based on at least one of the roadside perception information sent by the roadside perception unit and the traffic digitization information sent by the cloud control platform.

[0026] In an optional implementation, if the information processing method is applied to the edge cloud, determining the target RSU currently corresponding to the OBU according to at least one first V2X message includes:

[0027] The V2X application layer obtains, according to the at least one first V2X message, a second sender identifier corresponding to at least one RSU;

[0028] Determine a target second sender identifier corresponding to the latest first V2X message from at least one second sender identifier;

[0029] The RSU corresponding to the target second sender identifier is determined as the target RSU.

[0030] In an optional embodiment, the method further includes:

[0031] If at least one of the first V2X messages does not include the second sender identifier, the target RSU currently corresponding to the OBU is determined in at least one of the following ways:

[0032] Determine multiple RSUs corresponding to the target range as target RSUs;

[0033] Among the RSUs that have recently sent a predetermined number of first V2X messages, an RSU whose number of first V2X messages sent is greater than a predetermined threshold is determined as a target RSU.

[0034] In a second aspect, an embodiment of the present application provides an information processing method, which is applied to an RSU, and the method includes:

[0035] Receiving a first V2X message related to the OBU;

[0036] Sending a first V2X message to an MEC device or an edge cloud, where the MEC device or the edge cloud includes a V2X application layer, so that the V2X application layer parses the first V2X message;

[0037] Receive the response content for the OBU determined by the V2X application layer;

[0038] Forward the response content to the OBU.

[0039] In a third aspect, an embodiment of the present application provides an information processing device, which is applied to an MEC device or an edge cloud, wherein the MEC device or the edge cloud includes a V2X application layer, and the device includes:

[0040] A parsing module, configured to, in response to a first V2X message related to the OBU respectively sent by at least one RSU, parse the at least one first V2X message by the V2X application layer;

[0041] A target determination module, configured to determine a target RSU currently corresponding to the OBU according to at least one first V2X message when the V2X application layer determines the response content for the OBU;

[0042] The information sending module is used to send the response content to the target RSU, so that the target RSU forwards the response content to the OBU.

[0043] In an optional implementation, the MEC device or edge cloud further includes V2X message middleware, and the information sending module, when used to send the response content to the target RSU, is specifically used to:

[0044] The V2X message middleware determines a first data field corresponding to the response content, packages the first data field and the response content according to a predetermined message format, generates a corresponding second V2X message, and sends the second V2X message to the target RSU;

[0045] When the parsing module is used for the V2X application layer to parse at least one first V2X message, it is specifically used for: the V2X message middleware parses at least one first V2X message, obtains the second data field respectively included in the at least one first V2X message, and stores the second data field.

[0046] In an optional implementation, the first data field includes at least one of the following: a first sender identifier, a first receiver identifier, a network layer protocol identifier, a first message content type identifier, a first message length, a message priority, a network layer sending mode, a message sending cycle, and a first actual message content;

[0047] The first sender identifier is used to identify the MEC device or edge cloud;

[0048] The first receiver identifier is used to identify the target RSU.

[0049] In an optional implementation, the second data field includes at least one of the following: a second sender identifier, a second receiver identifier, a second message content type identifier, a second message length, and a second actual message content;

[0050] The second sender identifier is used to identify the RSU that sends the first V2X message;

[0051] The second receiver identifier is used to identify the MEC device or edge cloud.

[0052] In an optional implementation, the V2X application layer includes a codec, and the information sending module, when used to send the response content to the target RSU, is specifically used to:

[0053] Encoding the response content into a corresponding second V2X message through a codec;

[0054] Sending a second V2X message to a target RSU, where the target RSU includes at least one V2X link;

[0055] When the parsing module is used for parsing at least one first V2X message at the V2X application layer, it is specifically used to: decode the at least one first V2X message into corresponding first service data content through a codec.

[0056] In an optional implementation, if the first V2X message includes a request message, the response content includes second service data content obtained after performing service logic processing on the first V2X message;

[0057] If the first V2X message includes a non-request message, the response content includes a third business data content determined based on at least one of the roadside perception information sent by the roadside perception unit and the traffic digitization information sent by the cloud control platform.

[0058] In an optional implementation, if the information processing method is applied to the edge cloud, the target determination module is used to determine the target RSU currently corresponding to the OBU according to at least one first V2X message, specifically for:

[0059] The V2X application layer obtains, according to the at least one first V2X message, a second sender identifier corresponding to at least one RSU;

[0060] Determine a target second sender identifier corresponding to the latest first V2X message from at least one second sender identifier;

[0061] The RSU corresponding to the target second sender identifier is determined as the target RSU.

[0062] In an optional implementation, the target determination module is further configured to:

[0063] If at least one of the first V2X messages does not include the second sender identifier, the target RSU currently corresponding to the OBU is determined in at least one of the following ways:

[0064] Determine multiple RSUs corresponding to the target range as target RSUs;

[0065] Among the RSUs that have recently sent a predetermined number of first V2X messages, an RSU whose number of first V2X messages sent is greater than a predetermined threshold is determined as a target RSU.

[0066] In a fourth aspect, an embodiment of the present application provides an information processing device, which is applied to a road RSU, and the device includes:

[0067] A first receiving module, configured to receive a first V2X message related to the OBU;

[0068] A first forwarding module, configured to send a first V2X message to an MEC device or an edge cloud, where the MEC device or the edge cloud includes a V2X application layer, so that the V2X application layer parses the first V2X message;

[0069] A second receiving module is used to receive the response content for the OBU determined by the V2X application layer;

[0070] The second forwarding module is used to forward the response content to the OBU.

[0071] In a fifth aspect, an embodiment of the present application provides a V2X system, the system comprising:

[0072] The first aspect of the embodiment of the present application provides a MEC device or an edge cloud; and

[0073] The second aspect of the embodiments of the present application provides an RSU.

[0074] In a sixth aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the information processing method provided in the first aspect of the embodiment of the present application.

[0075] In a seventh aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the information processing method provided in the second aspect of the embodiment of the present application.

[0076] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the information processing method provided in the first aspect or the second aspect of the embodiment of the present application is implemented.

[0077] In a ninth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the information processing method provided in the first aspect or the second aspect of the embodiment of the present application.

[0078] The information processing method, apparatus, system, electronic device and readable storage medium provided in the embodiments of the present application adopt a solution of implementing the V2X application layer in an MEC device or an edge cloud, and can respond to the first V2X message related to the OBU sent by at least one RSU respectively, and the V2X application layer included in the MEC device or the edge cloud parses the at least one first V2X message; when the V2X application layer determines the response content for the OBU, the target RSU currently corresponding to the OBU is determined according to the at least one first V2X message; the response content is sent to the target RSU, so that the target RSU forwards the response content to the OBU. The embodiments of the present application implement a unified V2X application business logic on the MEC device or edge cloud side. For example, when the V2X system needs to support multiple links, the unified V2X application business logic and the V2X message encoding and decoding of the primary application layer on the MEC device or edge cloud side can be used to standardize the adaptation of different V2X links without repeated encoding and decoding for different V2X links, thereby effectively improving the system efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] Figure 1 A flowchart of an information processing method provided in an embodiment of the present application;

[0080] Figure 2 A schematic diagram of a MEC device supporting multiple V2X links provided in an embodiment of the present application;

[0081] Figure 3 A schematic diagram of edge cloud supporting multiple V2X links provided in an embodiment of the present application;

[0082] Figure 4 A schematic diagram of the structure of a C-V2X RSU provided in an embodiment of the present application;

[0083] Figure 5a A schematic diagram of a C-V2X system architecture supporting different V2X links for existing technologies;

[0084] Figure 5b A schematic diagram of a C-V2X system architecture supporting different V2X links when implementing V2X application business logic based on a roadside MEC device provided in an embodiment of the present application;

[0085] Figure 5c A schematic diagram of a C-V2X system architecture supporting different V2X links when implementing V2X application business logic based on edge cloud according to an embodiment of the present application;

[0086] Figure 6a This is a schematic diagram of the architecture of the roadside MEC equipment in traditional technology;

[0087] Figure 6bA schematic diagram of the architecture of a roadside MEC device or edge cloud edge of an embodiment of the present application provided for an embodiment of the present application;

[0088] Figure 7 A schematic diagram of spanning different RSUs provided in an embodiment of the present application;

[0089] Figure 8 A schematic diagram of implementing cross-RSU request-response in the edge cloud provided in an embodiment of the present application;

[0090] Fig. 9 A flowchart of another information processing method provided in an embodiment of the present application;

[0091] Fig.10a A schematic diagram of a C-V2X system architecture in the prior art;

[0092] Fig.10b A schematic diagram of a C-V2X system architecture for implementing V2X application business logic based on a roadside MEC device provided in an embodiment of the present application;

[0093] Fig.10c A schematic diagram of a C-V2X system architecture for implementing V2X application business logic based on edge cloud preparation provided in an embodiment of the present application;

[0094] Fig.11 A schematic diagram of the structure of an information processing device provided in an embodiment of the present application;

[0095] Fig.12 A schematic diagram of the structure of another information processing device provided in an embodiment of the present application;

[0096] Fig.13 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0097] The embodiments of the present application are described below in conjunction with the drawings in the present application. It should be understood that the implementation methods described below in conjunction with the drawings are exemplary descriptions for explaining the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions of the embodiments of the present application.

[0098] It will be understood by those skilled in the art that, unless specifically stated, the singular forms "one", "an" and "the" used herein may also include plural forms. It should be further understood that the terms "including" and "comprising" used in the embodiments of the present application refer to that the corresponding features can be implemented as the information, data, steps, operations, elements and / or components presented, but do not exclude the implementation as other information, data, steps, operations, elements, components and / or combinations thereof supported by the technical field, etc. It should be understood that when we call an element "connected" or "coupled" to another element, the one element can be directly connected or coupled to the other element, or it can refer to that the one element and the other element establish a connection relationship through an intermediate element. In addition, the "connection" or "coupling" used here may include wireless connection or wireless coupling. The term "and / or" used here indicates at least one of the items defined by the term, for example, "A and / or B" can be implemented as "A", or as "B", or as "A and B".

[0099] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0100] First, several terms involved in this application are introduced and explained:

[0101] (1) Intelligent Traffic System (ITS), also known as Intelligent Transportation System (ITS), is an effective and integrated application of advanced science and technology (information technology, computer technology, data communication technology, sensor technology, electronic control technology, automatic control theory, operations research, artificial intelligence, etc.) to transportation, service control and vehicle manufacturing, strengthening the connection between vehicles, roads and users, thus forming a comprehensive transportation system that ensures safety, improves efficiency, improves the environment and saves energy.

[0102] (2) Intelligent Vehicle Infrastructure Cooperative Systems (IVICS), also known as IVICS, is a development direction of the Intelligent Transportation System (ITS). IVICS uses advanced wireless communications and the new generation of Internet technologies to implement all-round dynamic real-time information interaction between vehicles and roads, and conducts active vehicle safety control and road cooperative management based on the collection and integration of dynamic traffic information in all time and space, fully realizing the effective coordination of people, vehicles and roads, ensuring traffic safety, and improving traffic efficiency, thus forming a safe, efficient and environmentally friendly road traffic system.

[0103] (3) V2X (vehicle to X, wireless communication technology for vehicles): It can also be understood as Vehicle To Everything, that is, the exchange of information between vehicles and the outside world, including but not limited to V2V (Vehicle to Vehicle) and V2I (Vehicle to Infrastructure). The Internet of Vehicles has laid a new direction for the development of automotive technology by integrating global positioning system navigation technology, vehicle-to-vehicle communication technology, wireless communication and remote sensing technology, and has achieved the compatibility of manual driving and autonomous driving. In short, models equipped with this system can automatically select the best driving route in terms of road conditions by analyzing real-time traffic information in autonomous driving mode, thereby greatly alleviating traffic congestion. In addition, by using on-board sensors and camera systems, it can also perceive the surrounding environment and make rapid adjustments, greatly reducing traffic accidents. For example, if a pedestrian suddenly appears, it can automatically slow down to a safe speed or stop.

[0104] (4) C-V2X (Cellular vehicle to X, cellular vehicle wireless communication technology), that is, V2X technology based on cellular communication technology. Among them, C-V2X technology may include V2X technology based on Long Term Evolution (LTE) (abbreviated as LTE-V2X) and V2X technology based on New Radio (NR) (abbreviated as NR-V2X). LTE-V2X is applicable to 4G networks, and NR-V2X is applicable to 5G networks. With the development and iteration of communication technology, it can also be applied to future higher-level communication networks such as 6G and 7G.

[0105] (5) RSU (Road Side Unit): Usually installed on the roadside, it uses DSRC (Dedicated Short Range Communication) technology to communicate with vehicles to achieve functions such as vehicle identity recognition, safety risk warning, and vehicle guidance.

[0106] (6) OBU (On board Unit): A microwave device that uses DSRC to communicate with the RSU. The OBU can be installed on a vehicle, and when the vehicle passes the RSU installed on the roadside at high speed, it can communicate with the RSU via microwave.

[0107] (7) MEC (Mobile Edge Computing) devices, also known as roadside computing devices in V2X systems, allow computing, network, and mobile services to move some computing and cloud-based processes to the edge of the network environment, thereby achieving better performance, latency, and security. Unlike data centers, this network architecture provides the services and cloud computing operations required by users at the edge of the network, closer to the end user.

[0108] (8) ASN.1 (Abstract Syntax Notation One): describes a data format for representing, encoding, transmitting, and decoding data. ASN.1 can be used to send various forms of information (audio, video, data, etc.) wherever information needs to be sent digitally.

[0109] The embodiment of the present application proposes a solution for implementing the V2X application layer on a roadside MEC device or an edge cloud, thereby implementing a unified V2X application business logic and improving system efficiency.

[0110] The following describes several exemplary embodiments to illustrate the technical solutions of the embodiments of the present application and the technical effects produced by the technical solutions of the present application. It should be noted that the following embodiments can refer to, draw on or combine with each other, and the same terms, similar features and similar implementation steps in different embodiments will not be described repeatedly.

[0111] An information processing method is provided in an embodiment of the present application, which is applied to an MEC device or an edge cloud, wherein the MEC device or the edge cloud includes a V2X application layer, such as Figure 1 As shown, the method may include:

[0112] S101: In response to a first V2X message related to an OBU respectively sent by at least one RSU, the V2X application layer parses at least one first V2X message;

[0113] In the embodiment of the present application, the first V2X message refers to the message data of the vehicle-side OBU, which is received by the RSU and then transmitted from the RSU to the MEC device or edge cloud. Optionally, the type of the first V2X message includes but is not limited to BSM (Basic Safety Message, vehicle status message), VIR (Vehicle Inspection Report, vehicle intention and request message), etc.

[0114] In the embodiment of the present application, the roadside MEC device supports network and terminal access of multiple standards (which can be called different V2X links), such as C-V2X, EUHT (Enhanced Ultra-High Throughput), DSRC (Dedicated Short Range Communication) and other dedicated roadside communication RSUs, but not limited to them. Each standard RSU is connected to the terminal through the corresponding network, such as Figure 2 shown.

[0115] When multiple roadside MECs are interconnected, virtualization and pooling can be performed to form an edge cloud. The edge cloud supports RSUs of different nodes. Each RSU node can include one or more standard RSUs, such as Figure 3 shown.

[0116] In an embodiment of the present application, the MEC device or the edge cloud may receive a first V2X message transmitted by at least one RSU, where the at least one RSU may refer to an RSU of a different standard on the same node, or may refer to an RSU of a different node.

[0117] In the embodiment of the present application, the MEC device or edge cloud includes a V2X application layer, which can perform relevant business logic processing based on the data of the lower layer, and the message layer of the application layer can parse the corresponding business data content from the first V2X message. In addition, the V2X application layer can execute specific user applications of safety warning or efficiency.

[0118] S102: When the V2X application layer determines the response content for the OBU, determine the target RSU currently corresponding to the OBU according to at least one first V2X message;

[0119] In the embodiment of the present application, the MEC device or edge cloud supports the request-response V2X service mechanism, that is, the MEC device or edge cloud can receive the request information (the first V2X message includes the request message) of a vehicle OBU, such as a lane change request. The MEC device or edge cloud determines whether to accept the request and sends guidance information to the vehicle, such as assisting the vehicle to change lanes safely.

[0120] That is, in the embodiment of the present application, if the first V2X message includes a request message, the response content includes the second service data content obtained after performing service logic processing on the first V2X message.

[0121] In the embodiment of the present application, the MEC device or edge cloud also supports data input based on the roadside perception unit (including but not limited to cameras, millimeter wave radars, laser radars, etc.), and perceives traffic participants (including but not limited to motor vehicles, non-motor vehicles, pedestrians, etc.) and traffic events on the road through fusion calculation, and sends the perceived roadside perception information to the C-V2X RSU (or RSU for short) at a certain frequency (for example: 10Hz, but not limited to this), and the RSU then broadcasts it to the C-V2X OBU (or OBU for short) at a certain frequency for the OBU to perform corresponding processing. For example, the OBU receives the roadside perception information broadcast by the RSU, performs local calculations, sees whether the surrounding traffic participants or traffic events pose a threat to it, and warns the driver of safety risks.

[0122] In the embodiment of the present application, the MEC device or edge cloud also supports traffic digitization information (such as traffic signs such as speed limit and dangerous road section prompts, but not limited to this) input based on the cloud control platform, and sends it to the RSU, which is broadcasted externally for the OBU to perform corresponding processing. For example, the OBU receives the traffic digitization information broadcast by the RSU, performs local calculations, and gives traffic sign prompts to the driver.

[0123] That is, in the embodiment of the present application, regardless of whether the first V2X message is an unsolicited message or an unsolicited message, the response content can include a third business data content determined based on at least one of the roadside perception information sent by the roadside perception unit and the traffic digitization information sent by the cloud control platform.

[0124] In the embodiment of the present application, when the V2X application layer determines the response content for the OBU, the target RSU currently corresponding to the OBU is determined according to at least one first V2X message. The target RSU may refer to one or more RSUs connected to the MEC device or the edge cloud, which are used to transmit the response content to the OBU.

[0125] S103: Send the response content to the target RSU, so that the target RSU forwards the response content to the OBU.

[0126] In the present application embodiment, Figure 4As shown, C-V2X RSU mainly has two layers of protocol stack, including network layer and access layer. Among them, the network layer is composed of two parts: data sublayer and management sublayer. The data sublayer mainly includes adaptation layer and DSMP (Dedicated Short Message Protocol) layer. The data sublayer can transmit data streams between MEC devices or V2X application layers of edge cloud, and can also transmit data streams between management layer entities of different devices or between management layer entities and applications; the management sublayer mainly includes DME (Dedicated Management Entity), which can complete system configuration and maintenance functions, and transmit management data streams between different devices by using data sublayer services. The access layer is used to handle the physical transmission of data packets between RSU and OBU, and LTE-V2X direct communication can be used, but is not limited to this.

[0127] Therefore, after the MEC device or edge cloud sends the response content to the target RSU, the target RSU can forward the response content to the OBU.

[0128] The information processing method, apparatus, system, electronic device and readable storage medium provided in the embodiments of the present application implement a unified V2X application business logic on the MEC device or edge cloud side, effectively improving system efficiency.

[0129] As an example, when the V2X system needs to support multiple links, through the unified V2X application business logic and the V2X message encoding and decoding of the primary application layer of the MEC device or edge cloud side, different V2X links can be adapted in a standardized manner without the need for repeated encoding and decoding for different V2X links, effectively improving system efficiency.

[0130] For the embodiment of the present application, the V2X application layer of the MEC device or edge cloud may include a codec. Optionally, the codec may use an ASN.1 codec, but is not limited thereto, and other encoders such as JSON (JavaScript Object Notation, JS object notation) may also be used. Among them, ASN.1 has advantages in RSU-OBU transmission. In the embodiment of the present application, the codec (such as the V2X message ASN.1 codec) is placed in the roadside MEC device or edge cloud to support different V2X links.

[0131] Specifically, step S103 may include: encoding the response content into a corresponding second V2X message through a codec; and sending the second V2X message to a target RSU, where the target RSU includes at least one V2X link.

[0132] In the embodiment of the present application, the second V2X message is message data to be sent to the vehicle-side OBU, received by the RSU, and then transmitted from the RSU to the vehicle-side OBU. Optionally, the types of the second V2X message include but are not limited to RSM (Road Safety Message), RSI (Road Side Information), MAP (Map Message), SPAT (Signal Phase Timing Message), RSC (Road Side Coordination), etc.

[0133] In order to more intuitively see the differences and advantages of the embodiments of the present application and the prior art, Figure 5a The C-V2X system architecture diagram of the prior art supporting different V2X links is shown. Figure 5b The C-V2X system architecture diagram supporting different V2X links when implementing V2X application business logic based on roadside MEC devices is shown. Figure 5c The diagram shows the C-V2X system architecture that supports different V2X links when implementing V2X application business logic based on edge cloud.

[0134] It can be seen that in the prior art, C-V2X RSU mainly has a three-layer protocol stack, namely, the application layer, network layer, and access layer are all implemented in RSU. This also means that when the existing V2X application or system needs to support multi-standard networks and terminals, the application layer needs to be repeatedly packaged and unpacked on different network-side devices to achieve the encoding and decoding of V2X messages. As an example, if there is currently a roadside MEC device with a V2X message generated by data from a roadside perception unit or a cloud control platform that needs to be sent to multi-standard terminals such as C-V2X OBU, EUHT terminal, DSRC, etc., it needs to be packaged separately on network-side devices such as C-V2X RSU, EUHT base station, DSRC RSU, etc., and a total of 3 packages are required.

[0135] In the embodiment of the present application, when the existing V2X application or system needs to support multi-standard networks and terminals, the V2X application layer only needs to be packaged once on the roadside MEC device or edge cloud, and then transmitted to C-V2X OBU, EUHT terminal, DSRC and other multi-standard terminals through network-side devices such as C-V2X RSU, EUHT base station, DSRC RSU, etc., effectively reducing encoding and decoding operations and improving system efficiency.

[0136] Similarly, step S101 may specifically include: decoding at least one first V2X message into corresponding first service data content through a codec, and further, the V2X application layer may perform related service logic processing according to the first service data content.

[0137] In an embodiment of the present application, using a codec, the V2X application layer of a roadside MEC device or an edge cloud can implement encoding and decoding of V2X messages such as RSM, RSI, MAP, SPAT, VIR, and RSC.

[0138] In order to more intuitively see the differences and advantages of the embodiments of the present application and the prior art, Figure 6a The architecture diagram of the roadside MEC device in the traditional technology is shown. Figure 6b The architecture diagram of the roadside MEC device or edge cloud edge of an embodiment of the present application is shown.

[0139] It can be seen that traditional roadside MEC equipment mainly includes a fusion perception computing module, a road-cloud data transceiver module, and a roadside data transceiver module. Among them, the fusion perception computing module is mainly used to perform fusion perception calculation on the original perception data input by roadside perception units such as cameras, millimeter-wave radars, and lidars; the road-cloud data transceiver module is mainly used to report roadside perception data, V2X business data, and operation and maintenance data to the cloud control platform; the roadside data transceiver module is mainly used to send the perception structured data after fusion perception calculation to different roadside communication equipment.

[0140] In the roadside MEC device or edge cloud provided in the embodiment of the present application, the fusion perception computing module and the road-cloud data transceiver module are consistent with the traditional roadside MEC module. The application business logic module and the V2X message ASN.1 codec in the original roadside communication equipment (RSU) are placed in the roadside MEC implementation. At the same time, the roadside data transceiver module is changed to the V2X message middleware to adapt to different roadside communication equipment such as C-V2X, EUHT, and DSRC in a standardized manner.

[0141] Combined with the introduction above, it can be seen that when sending business data content, the V2X message ASN.1 codec encodes the business data content into corresponding RSM, RSI, MAP, SPAT, RSC and other V2X messages, for example, ASN.1 encoding can be used; when receiving V2X messages, the BSM, VIR and other messages transmitted from the RSU (the data sent by the vehicle-side OBU is received by the RSU) are decoded into corresponding business data content, for example, ASN.1 decoding can be used.

[0142] In an embodiment of the present application, the V2X application layer is implemented on the roadside MEC device or edge cloud, and includes an application business logic module and a V2X message ASN.1 codec, implementing a unified V2X application business logic and a V2X message codec of the primary application layer, supporting different V2X links.

[0143] In the embodiment of the present application, after the V2X application layer is implemented on the roadside MEC device or edge cloud, the data transmission between the application layer and the network layer can no longer be privately implemented as before in the roadside communication device, but requires a standardized data transmission interface between the roadside MEC device or edge cloud and the roadside communication device, that is, the data field transmitted by the V2X message middleware needs to be determined. That is, in the embodiment of the present application, the V2X application layer of the MEC device or edge cloud can include the V2X message middleware.

[0144] Specifically, step S103 may include: the V2X message middleware determines a first data field corresponding to the response content, packages the first data field and the response content according to a predetermined message format, generates a corresponding second V2X message, and sends the second V2X message to the target RSU.

[0145] In an embodiment of the present application, the first data field includes at least one of the following: a first sender identifier, a first receiver identifier, a network layer protocol identifier, a first message content type identifier, a first message length, a message priority, a network layer sending mode, a message sending cycle, and a first actual message content; wherein the first sender identifier is used to identify the MEC device or the edge cloud; the first receiver identifier is used to identify the target RSU; the network layer protocol identifier is used to indicate the network layer protocol used, including but not limited to DSMP, TCP (Transmission Control Protocol), UDP (User Datagram Protocol), etc.; the first message content type identifier is used to identify the content type of the V2X message transmitted this time, including but not limited to RSM, RSI, MAP, SPAT, RSC, etc.; the first actual message content refers to the above-mentioned response content.

[0146] In order to more clearly illustrate the role of each first data field, the data content sent by the roadside MEC or edge cloud to the RSU is shown in Table 1:

[0147]

[0148] Table 1

[0149] Similarly, step S101 may specifically include: the V2X message middleware parses at least one first V2X message, obtains the second data field respectively included in the at least one first V2X message, and stores the second data field.

[0150] In an embodiment of the present application, the second data field includes at least one of the following: a second sender identifier, a second receiver identifier, a second message content type identifier, a second message length, and a second actual message content; wherein the second sender identifier is used to identify the RSU that sends the first V2X message; the second receiver identifier is used to identify the MEC device or edge cloud; the second message content type identifier is used to identify the content type of the V2X message transmitted this time, including but not limited to BSM, VIR, etc.; the second actual message content refers to the business data content sent by the vehicle-side OBU.

[0151] In order to more clearly illustrate the role of each first data field, the data content sent by the RSU to the roadside MEC or edge cloud is shown in Table 2:

[0152]

[0153] Table 2

[0154] In the embodiment of the present application, the V2X application layer is implemented uniformly on the roadside MEC device or edge cloud, and includes an application business logic module, a V2X message ASN.1 codec and a V2X message middleware, to implement a unified V2X application business logic, a primary application layer V2X message codec and a standardized data transmission interface, support different V2X links, and improve the flexibility, efficiency and security of V2X message transmission.

[0155] From the above introduction, we can know that MEC devices or edge clouds support sending the perceived roadside perception information and traffic digitization information input by the cloud control platform to RSU, which is broadcasted externally for OBU to process accordingly. That is, RSU broadcasts information more in one direction, and this application can be called the first stage application (DAY I).

[0156] In addition, MEC devices or edge clouds support the request-response mechanism of V2X services, and this application can be called the second stage application (DAY II).

[0157] In the embodiment of the present application, a solution is provided to improve the efficiency in some scenarios when using DAY II. As an example, a possible scenario is that the coverage of an RSU is generally about 400 meters. When providing full network coverage, different RSUs have overlapping coverage. When an OBU sends a request, it can carry the RSU ID of the requested target so that the RSU can respond. When an OBU initiates a request near the overlapping coverage area, such as Figure 7 The RSU1 shown in the figure may initiate a request, but may not receive a response from RSU1, that is, it has already left the coverage area of ​​RSU1, resulting in a request-response failure at the application layer, and the request-response needs to be re-initiated. In high-speed scenarios, due to the high speed of the vehicle, the OBU may continuously cross different RSUs in a short period of time. This inefficient application layer request-response process will be more prominent, resulting in reduced efficiency of the entire system.

[0158] The inventors of the present application realized that if each RSU in the system works independently and has its own supporting MEC equipment and roadside sensing equipment, in the absence of a necessary coordination mechanism, it is impossible for the OBU to initiate a request to RSU1 and obtain a response from RSU2 or RSU3.

[0159] Based on this, an embodiment of the present application provides a solution for implementing the V2X application layer in the roadside edge cloud. When the roadside MEC is virtualized and pooled to form an edge cloud after being interconnected, the V2X application layer is uniformly implemented in the edge cloud, which can effectively support the rapid switching of OBU between different RSU nodes, and enable the OBU to initiate a request at one RSU and obtain a response at another RSU, thereby solving the problem of request-response failure in the above-mentioned OBU fast-moving scenario.

[0160] Specifically, if the information processing method is applied to the edge cloud, S102 may specifically include:

[0161] S1021: The V2X application layer obtains, according to at least one first V2X message, a second sender identifier corresponding to at least one RSU;

[0162] In an embodiment of the present application, in a fast-moving OBU scenario, the edge cloud may receive a first V2X message transmitted by multiple RSUs, and the V2X application layer may obtain the ID (second sender identifier) ​​of the RSU of the multiple transmitted first V2X messages.

[0163] S1022: Determine a target second sender identifier corresponding to the latest first V2X message from at least one second sender identifier;

[0164] In the embodiment of the present application, the edge cloud may receive the first V2X messages transmitted by multiple RSUs in sequence, and can determine the target second sender identifier corresponding to the last (most recent) first V2X message received, that is, the OBU is currently most likely within the coverage range of the RSU corresponding to the target second sender identifier.

[0165] S1023: Determine the RSU corresponding to the target second sender identifier as the target RSU.

[0166] Furthermore, the response content can be sent to the target RSU. Since the OBU is likely to be within the coverage of the target RSU, the success rate of the target RSU forwarding the response content to the OBU can be improved.

[0167] Among them, a first V2X message received by the edge cloud is a request message, and the response content is the business logic processing result of the request message. Other first V2X messages received by the edge can be request messages or non-request messages.

[0168] In the present application embodiment, Figure 8 As shown in the figure, for the request-response service of DAY II, placing the V2X application layer on the edge cloud to implement a complete process of request-response that supports cross-RSUs includes:

[0169] S801: When the edge cloud receives a request message (such as VIR) transmitted by the RSU, it obtains the ID of the sending RSU;

[0170] S802: The V2X application layer of the edge cloud parses the request message and obtains the vehicle ID that sends the request and the request content;

[0171] S803: The V2X application layer of the edge cloud continuously receives and parses the V2X messages sent by each RSU to continuously determine the messages sent by each vehicle (determined by the vehicle ID, not necessarily a request message, but other V2X messages sent by the vehicle, such as a BSM message) and the RSU ID from which each vehicle message comes.

[0172] S804: When the V2X application layer of the edge cloud determines to give a response message to the vehicle according to the V2X application business logic, it determines the RSU ID from which the latest V2X message of the vehicle comes (which may be different from the RSU ID from which the request message comes)

[0173] S805: Forward the response message to the RSU for sending to the vehicle OBU.

[0174] In the embodiment of the present application, considering that some V2X messages (such as non-request V2X messages such as BSM messages) may not carry the RSU ID, a feasible implementation method is also provided for step S102, which may include: if at least one first V2X message does not include the second sender identifier, determining the target RSU currently corresponding to the OBU in at least one of the following ways:

[0175] (1) Determine multiple RSUs corresponding to the target range as target RSUs;

[0176] For example, in an overlapping coverage area, two or more RSUs may forward V2X messages of the same vehicle ID to the edge cloud. The edge cloud can then forward the response messages to multiple RSUs for them to send.

[0177] For another example, the target range of vehicle movement may be estimated, and multiple RSUs corresponding to the target range, such as multiple RSUs covering the target range, or multiple RSUs within the target range, may be determined as target RSUs.

[0178] (2) Select one or more RSUs from the RSUs according to a predetermined rule as target RSUs and let them forward the response message;

[0179] Optionally, among the RSUs that have recently sent a predetermined number of first V2X messages, an RSU whose number of first V2X messages sent is greater than a predetermined threshold is determined as a target RSU.

[0180] That is, assuming that the predetermined number is N and the predetermined threshold is M, the rule can be defined as looking at the RSUIDs from which the most recent N messages come, and the number of messages from each RSU ID should be greater than M. The values ​​of N and M can be determined according to the specific deployment scenario, and the embodiments of the present application are not limited here.

[0181] (3) Determine the target RSU among each RSU through the neural network model.

[0182] Optionally, the vehicle-related message is encoded into an attribute vector, the attribute vector is input into the neural network model, and the neural network model outputs the target RSU, or the neural network model outputs the probability value of each RSU as the target RSU. In other embodiments, the input of the neural network model may also include other information, such as environment-related information, road condition-related information, etc., which is not limited in the embodiments of the present application. Among them, those skilled in the art can set the specific neural network model and its training method according to actual conditions, which is not limited in the embodiments of the present application.

[0183] The vehicle information processing method provided in the embodiment of the present application can more efficiently support the sending of multi-link V2X service messages through the V2X application layer solution of the roadside MEC device or the edge cloud, and realize the V2X message encoding and decoding through a set of unified V2X application business logic and a primary application layer, that is, support different V2X links.

[0184] The vehicle information processing method provided in the embodiment of the present application can effectively support request-response V2X services across RSUs through the V2X application layer solution of the edge cloud, and realize efficient transmission of request-response V2X services, especially in fast-moving vehicle scenarios such as highways.

[0185] The vehicle information processing method provided in the embodiment of the present application, through at least one of the above-mentioned schemes, the data interaction between the roadside computing device or edge cloud and the roadside communication device is flexible and efficient.

[0186] The present application also provides an information processing method, which is applied to RSU, such as Fig. 9 As shown, the method may include:

[0187] S901: receiving a first V2X message related to the OBU;

[0188] In the embodiment of the present application, the first V2X message refers to the message data related to the vehicle-side OBU, which is received by the RSU and then transmitted from the RSU to the MEC device or edge cloud. Optionally, the type of the first V2X message includes but is not limited to BSM, VIR, etc.

[0189] S902: Send a first V2X message to an MEC device or an edge cloud, where the MEC device or the edge cloud includes a V2X application layer, so that the V2X application layer parses the first V2X message;

[0190] In the embodiment of the present application, the roadside MEC device supports network and terminal access of multiple standards (which can be called different V2X links), such as C-V2X, EUHT, DSRC and other dedicated roadside communication RSUs, but not limited thereto. Each standard RSU is connected through the corresponding network and terminal.

[0191] When multiple roadside MECs are interconnected, virtualization and pooling can be performed to form an edge cloud. The edge cloud supports RSUs of different nodes, and each RSU node can include one or more standard RSUs.

[0192] In the embodiment of the present application, the MEC device or edge cloud includes a V2X application layer, which can perform relevant business logic processing based on the data of the lower layer, and the message layer of the application layer can parse the corresponding business data content from the first V2X message. In addition, the V2X application layer can execute specific user applications of safety warning or efficiency.

[0193] S903: Receive the response content for the OBU determined by the V2X application layer;

[0194] In the embodiment of the present application, the MEC device or edge cloud supports the request-response V2X service mechanism, that is, the MEC device or edge cloud can receive the request information (the first V2X message includes the request message) of a vehicle OBU, such as a lane change request. The MEC device or edge cloud determines whether to accept the request and sends guidance information to the vehicle, such as assisting the vehicle to change lanes safely.

[0195] That is, in the embodiment of the present application, if the first V2X message includes a request message, the response content includes the second service data content obtained after performing service logic processing on the first V2X message.

[0196] In the embodiment of the present application, the MEC device or edge cloud also supports data input based on the roadside perception unit (including but not limited to cameras, millimeter wave radars, laser radars, etc.), and perceives traffic participants (including but not limited to motor vehicles, non-motor vehicles, pedestrians, etc.) and traffic events on the road through fusion calculation, and sends the perceived roadside perception information to the C-V2X RSU (or RSU for short) at a certain frequency (for example: 10Hz, but not limited to this), and the RSU then broadcasts it to the C-V2X OBU (or OBU for short) at a certain frequency for the OBU to perform corresponding processing. For example, the OBU receives the roadside perception information broadcast by the RSU, performs local calculations, sees whether the surrounding traffic participants or traffic events pose a threat to it, and warns the driver of safety risks.

[0197] In the embodiment of the present application, the MEC device or edge cloud also supports traffic digitization information (such as traffic signs such as speed limit and dangerous road section prompts, but not limited to this) input based on the cloud control platform, and sends it to the RSU, which is broadcasted externally for the OBU to perform corresponding processing. For example, the OBU receives the traffic digitization information broadcast by the RSU, performs local calculations, and gives traffic sign prompts to the driver.

[0198] That is, in the embodiment of the present application, regardless of whether the first V2X message is an unsolicited message or an unsolicited message, the response content can include a third business data content determined based on at least one of the roadside perception information sent by the roadside perception unit and the traffic digitization information sent by the cloud control platform.

[0199] Optionally, the V2X application layer of the MEC device or edge cloud encodes the response content into a corresponding second V2X message through a codec, and the RSU receives the second V2X message for the OBU determined by the V2X application layer.

[0200] In the embodiment of the present application, the second V2X message is message data to be sent to the vehicle-side OBU, received by the RSU, and then transmitted from the RSU to the vehicle-side OBU. Optionally, the type of the second V2X message includes but is not limited to RSM, RSI, MAP, SPAT, RSC, etc.

[0201] S904: Forward the response content to the OBU.

[0202] In the embodiment of the present application, the C-V2X RSU mainly has two layers of protocol stack, including a network layer and an access layer. Among them, the network layer is composed of two parts: a data sublayer and a management sublayer. The data sublayer mainly includes an adaptation layer and a DSMP layer. The data sublayer can transmit data flows between the V2X application layer of the MEC device or the edge cloud, and can also transmit data flows between different device management layer entities or between management layer entities and applications; the management sublayer mainly includes DME, which can complete functions such as system configuration and maintenance, and transmit management data flows between different devices by using data sublayer services. The access layer is used to handle the physical transmission of data packets between the RSU and the OBU, and LTE-V2X direct communication can be used, but is not limited to this. Therefore, after receiving the response content (or the second V2X message), the RSU can forward the response content (or the second V2X message) to the OBU.

[0203] In order to more intuitively see the difference and advantages between the embodiments of the present application and the prior art, in the embodiments of the present application, the RSU is a C-V2X RSU as an example. Fig.10a The C-V2X system architecture diagram of the prior art is shown. Fig.10b The C-V2X system architecture diagram based on the roadside MEC device to implement V2X application business logic is shown. Fig.10c The C-V2X system architecture diagram based on edge cloud to implement V2X application business logic is shown.

[0204] It can be seen that in the prior art, C-V2X RSU mainly has a three-layer protocol stack, that is, the application layer, network layer, and access layer are all implemented in RSU, and a C-V2X OBU can connect to one or more C-V2X RSU. In the embodiment of the present application, unlike the prior art, the V2X application layer solution is implemented in the roadside MEC device or edge cloud, and the C-V2X RSU only deploys the network layer and access layer, which can improve the system efficiency. Among them, the specific execution method corresponds to the roadside MEC device or edge cloud execution method. The detailed functional description and the beneficial effects produced can be specifically referred to the description of the roadside MEC device or edge cloud execution method, which will not be repeated here.

[0205] The present application also provides a V2X system, which may include the MEC device or edge cloud provided in the present application, and the RSU provided in the present application. The detailed functional description and beneficial effects thereof may be specifically referred to in the above description, and the system architecture may be referred to in Figure 2 , Figure 3 , Figure 5b , Figure 5c , Figure 6b , Fig.10b , Fig.10c etc., will not be elaborated here.

[0206] From the above introduction, it can be seen that the V2X system provided in the embodiment of the present application may include a cloud control platform, wherein the cloud control platform can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as big data and artificial intelligence platforms.

[0207] In the embodiments of the present application, a V2X system based on an edge cloud can be implemented through cloud technology, including but not limited to cloud storage, cloud IoT, etc.

[0208] Among them, cloud storage is a new concept extended and developed from the concept of cloud computing. A distributed cloud storage system (hereinafter referred to as storage system) refers to a storage system that uses cluster applications, grid technology, and distributed storage file systems to bring together a large number of different types of storage devices (storage devices are also called storage nodes) in the network through application software or application interfaces to work together and provide external data storage and business access functions.

[0209] At present, the storage method of the storage system is: create a logical volume, and when creating a logical volume, allocate physical storage space for each logical volume. The physical storage space may be composed of disks of a storage device or several storage devices. The client stores data on a logical volume, that is, stores the data on the file system. The file system divides the data into many parts, each of which is an object. The object contains not only data but also additional information such as data identification (ID, ID entity). The file system writes each object into the physical storage space of the logical volume, and the file system records the storage location information of each object, so that when the client requests to access the data, the file system can allow the client to access the data according to the storage location information of each object.

[0210] The process of the storage system allocating physical storage space to a logical volume is as follows: based on the estimated capacity of the objects stored in the logical volume (this estimate often has a large margin relative to the actual capacity of the objects to be stored) and the grouping of independent redundant disk arrays (RAID, Redundant Array of Independent Disks), the physical storage space is pre-divided into stripes. A logical volume can be understood as a stripe, thereby allocating physical storage space to the logical volume.

[0211] The Internet of Things (IOT) refers to the use of various information sensors, radio frequency identification technology, global positioning system, infrared sensor, laser scanner and other devices and technologies to collect any objects or processes that need to be detected, connected and interacted in real time, collect their sound, light, heat, electricity, mechanics, chemistry, biology, location and other required information, and realize ubiquitous connection between objects and objects and between objects and people through various possible network access, and realize intelligent perception, identification and management of objects and processes. The Internet of Things is an information carrier based on the Internet, traditional telecommunications network, etc. It allows all ordinary physical objects that can be independently addressed to form an interconnected network.

[0212] Cloud IOT aims to connect the information sensed and instructions received by sensor devices in traditional IoT to the Internet, truly realize networking, and achieve massive data storage and computing through cloud computing technology. Due to the characteristics of IoT, objects are connected to each other and the current operating status of each "object" is perceived in real time. A large amount of data information will be generated in this process. How to aggregate this information and how to filter out useful information from the massive information to support decision-making for subsequent development have become key issues affecting the development of IoT. IoT cloud based on cloud computing and cloud storage technology has therefore become a strong support for IoT technology and applications.

[0213] The V2X system provided in the embodiment of the present application can be partially processed based on AI (Artificial Intelligence) technology, such as determining the target RSU for transmitting V2X messages to the OBU. AI is a theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results. In other words, artificial intelligence is a comprehensive technology in computer science that attempts to understand the essence of intelligence and produce a new intelligent machine that can respond in a similar way to human intelligence. Artificial intelligence is to study the design principles and implementation methods of various intelligent machines so that the machines have the functions of perception, reasoning and decision-making. The basic technologies of artificial intelligence generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, mechatronics, etc. The artificial intelligence software technology involved in the embodiment of the present application mainly includes computer vision technology, and machine learning / deep learning and other major directions. With the research and progress of artificial intelligence technology, artificial intelligence technology has been studied and applied in many fields. It is believed that with the development of technology, artificial intelligence technology will be applied in more fields and play an increasingly important role.

[0214] The embodiment of the present application provides an information processing device, which is applied to an MEC device or an edge cloud. The MEC device or the edge cloud includes a V2X application layer, such as Fig.11 As shown, the information processing device 110 may include: a parsing module 1101, a target determination module 1102 and an information sending module 1103, wherein:

[0215] The parsing module 1101 is configured to respond to a first V2X message related to the OBU respectively sent by at least one RSU, and the V2X application layer parses at least one first V2X message;

[0216] The target determination module 1102 is used to determine the target RSU currently corresponding to the OBU according to at least one first V2X message when the V2X application layer determines the response content for the OBU;

[0217] The information sending module 1103 is used to send the response content to the target RSU, so that the target RSU forwards the response content to the OBU.

[0218] In an optional implementation, the MEC device or edge cloud further includes V2X message middleware, and the information sending module 1103, when used to send the response content to the target RSU, is specifically used to:

[0219] The V2X message middleware determines a first data field corresponding to the response content, packages the first data field and the response content according to a predetermined message format, generates a corresponding second V2X message, and sends the second V2X message to the target RSU;

[0220] When the parsing module 1101 is used for the V2X application layer to parse at least one first V2X message, it is specifically used for: the V2X message middleware parses at least one first V2X message, obtains the second data field respectively included in the at least one first V2X message, and stores the second data field.

[0221] In an optional implementation, the first data field includes at least one of the following: a first sender identifier, a first receiver identifier, a network layer protocol identifier, a first message content type identifier, a first message length, a message priority, a network layer sending mode, a message sending cycle, and a first actual message content;

[0222] The first sender identifier is used to identify the MEC device or edge cloud;

[0223] The first receiver identifier is used to identify the target RSU.

[0224] In an optional implementation, the second data field includes at least one of the following: a second sender identifier, a second receiver identifier, a second message content type identifier, a second message length, and a second actual message content;

[0225] The second sender identifier is used to identify the RSU that sends the first V2X message;

[0226] The second receiver identifier is used to identify the MEC device or edge cloud.

[0227] In an optional implementation, the V2X application layer includes a codec, and the information sending module 1103, when used to send the response content to the target RSU, is specifically used to:

[0228] Encoding the response content into a corresponding second V2X message through a codec;

[0229] Sending a second V2X message to a target RSU, where the target RSU includes at least one V2X link;

[0230] When the parsing module 1101 is used for parsing at least one first V2X message at the V2X application layer, it is specifically used to: decode the at least one first V2X message into corresponding first service data content through a codec.

[0231] In an optional implementation, if the first V2X message includes a request message, the response content includes second service data content obtained after performing service logic processing on the first V2X message;

[0232] If the first V2X message includes a non-request message, the response content includes a third business data content determined based on at least one of the roadside perception information sent by the roadside perception unit and the traffic digitization information sent by the cloud control platform.

[0233] In an optional implementation, if the information processing method is applied to the edge cloud, the target determination module 1102 is used to determine the target RSU currently corresponding to the OBU according to at least one first V2X message, specifically for:

[0234] The V2X application layer obtains, according to the at least one first V2X message, a second sender identifier corresponding to at least one RSU;

[0235] Determine a target second sender identifier corresponding to the latest first V2X message from at least one second sender identifier;

[0236] The RSU corresponding to the target second sender identifier is determined as the target RSU.

[0237] In an optional implementation, the target determination module 1102 is further configured to:

[0238] If at least one of the first V2X messages does not include the second sender identifier, the target RSU currently corresponding to the OBU is determined in at least one of the following ways:

[0239] Determine multiple RSUs corresponding to the target range as target RSUs;

[0240] Among the RSUs that have recently sent a predetermined number of first V2X messages, an RSU whose number of first V2X messages sent is greater than a predetermined threshold is determined as a target RSU.

[0241] The present application also provides an information processing device, which is applied to RSU, such as Fig.12 As shown, the information processing device 120 may include: a first receiving module 1201, a first forwarding module 1202, a second receiving module 1203 and a second forwarding module 1204, wherein:

[0242] The first receiving module 1201 is used to receive a first V2X message related to the OBU;

[0243] The first forwarding module 1202 is used to send the first V2X message to the MEC device or the edge cloud 1203. The MEC device or the edge cloud includes a V2X application layer, so that the V2X application layer parses the first V2X message;

[0244] The second receiving module 1203 is used to receive the response content for the OBU determined by the V2X application layer;

[0245] The second forwarding module 1204 is used to forward the response content to the OBU.

[0246] The device of the embodiments of the present application can execute the method provided by the embodiments of the present application, and the implementation principles are similar. The actions performed by each module in the device of each embodiment of the present application correspond to the steps in the method of each embodiment of the present application. For the detailed functional description of each module of the device, please refer to the description in the corresponding method shown in the previous text, which will not be repeated here.

[0247] An electronic device is provided in an embodiment of the present application, including a memory, a processor, and a computer program stored in the memory, and the processor executes the computer program to implement the steps of the aforementioned method embodiments. Optionally, the electronic device may refer to the MEC device or edge cloud provided in an embodiment of the present application, or the electronic device may refer to the RSU provided in an embodiment of the present application.

[0248] In an alternative embodiment, an electronic device is provided, such as Fig.13 As shown, Fig.13The electronic device 1300 shown includes: a processor 1301 and a memory 1303. The processor 1301 and the memory 1303 are connected, such as through a bus 1302. Optionally, the electronic device 1300 may also include a transceiver 1304, which may be used for data interaction between the electronic device and other electronic devices, such as data transmission and / or data reception. It should be noted that in actual applications, the transceiver 1304 is not limited to one, and the structure of the electronic device 1300 does not constitute a limitation on the embodiments of the present application.

[0249] Processor 1301 may be a CPU (Central Processing Unit), a general purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. Processor 1301 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0250] The bus 1302 may include a path to transmit information between the above components. The bus 1302 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus 1302 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.13 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0251] The memory 1303 may be a ROM (Read Only Memory) or other types of static storage devices that can store static information and instructions, a RAM (Random Access Memory) or other types of dynamic storage devices that can store information and instructions, or an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium that can be used to carry or store computer programs and can be read by a computer, without limitation herein.

[0252] The memory 1303 is used to store the computer program for executing the embodiment of the present application, and the execution is controlled by the processor 1301. The processor 1301 is used to execute the computer program stored in the memory 1303 to implement the steps shown in the above method embodiment.

[0253] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps and corresponding contents of the aforementioned method embodiment can be implemented.

[0254] The embodiment of the present application also provides a computer program product, including a computer program, which can implement the steps and corresponding contents of the aforementioned method embodiment when executed by a processor.

[0255] The terms "first", "second", "third", "fourth", "1", "2", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than that shown or described in the drawings.

[0256] It should be understood that, although each operation step is indicated by arrows in the flowchart of the embodiment of the present application, the implementation order of these steps is not limited to the order indicated by the arrows. Unless clearly stated herein, in some implementation scenarios of the embodiment of the present application, the implementation steps in each flowchart can be performed in other orders according to demand. In addition, some or all of the steps in each flowchart may include multiple sub-steps or multiple stages based on actual implementation scenarios. Some or all of these sub-steps or stages may be executed at the same time, and each sub-step or stage in these sub-steps or stages may also be executed at different times respectively. In different scenarios of execution time, the execution order of these sub-steps or stages may be flexibly configured according to demand, and the embodiment of the present application does not limit this.

[0257] The above are only optional implementation methods for some implementation scenarios of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the technical concept of the scheme of the present application, other similar implementation methods based on the technical ideas of the present application are also within the protection scope of the embodiments of the present application.

Claims

1. An information processing method, characterized in that: Applied to a multi-access edge computing MEC device or an edge cloud, the MEC device or the edge cloud includes a vehicle wireless communication technology V2X application layer, and the method includes: In response to a first V2X message related to an on-board unit OBU respectively sent by at least one roadside unit RSU, the V2X application layer parses at least one first V2X message; When the V2X application layer determines the response content for the OBU, determining a target RSU currently corresponding to the OBU according to at least one first V2X message; The response content is sent to the target RSU, so that the target RSU forwards the response content to the OBU.

2. The information processing method according to claim 1, characterized in that: The MEC device or the edge cloud further includes a V2X message middleware, and sending the response content to the target RSU includes: The V2X message middleware determines a first data field corresponding to the response content, packages the first data field and the response content according to a predetermined message format, generates a corresponding second V2X message, and sends the second V2X message to the target RSU; The V2X application layer parses at least one first V2X message, including: The V2X message middleware parses at least one first V2X message, obtains a second data field respectively included in the at least one first V2X message, and stores the second data field.

3. The information processing method according to claim 2, characterized in that: The first data field includes at least one of the following: a first sender identifier, a first receiver identifier, a network layer protocol identifier, a first message content type identifier, a first message length, a message priority, a network layer sending mode, a message sending cycle, and a first actual message content; Wherein, the first sender identifier is used to identify the MEC device or the edge cloud; The first receiver identifier is used to identify the target RSU.

4. The information processing method according to claim 2, characterized in that: The second data field includes at least one of the following: a second sender identifier, a second receiver identifier, a second message content type identifier, a second message length, and a second actual message content; The second sender identifier is used to identify the RSU that sends the first V2X message; The second receiver identifier is used to identify the MEC device or the edge cloud.

5. The information processing method according to claim 1, characterized in that: The V2X application layer includes a codec, and sending the response content to the target RSU includes: encoding the response content into a corresponding second V2X message by the codec; Sending the second V2X message to the target RSU, where the target RSU includes at least one V2X link; The V2X application layer parses at least one first V2X message, including: At least one first V2X message is decoded into corresponding first service data content through the codec.

6. The information processing method according to any one of claims 1 to 5, characterized in that: If the first V2X message includes a request message, the response content includes second service data content obtained after performing service logic processing on the first V2X message; If the first V2X message includes a non-request message, the response content includes a third business data content determined based on at least one of the roadside perception information sent by the roadside perception unit and the traffic digitization information sent by the cloud control platform.

7. The information processing method according to any one of claims 1 to 5, characterized in that: If the information processing method is applied to the edge cloud, determining the target RSU currently corresponding to the OBU according to at least one first V2X message includes: The V2X application layer obtains, according to at least one first V2X message, a second sender identifier corresponding to each of the at least one RSU; Determining a target second sender identifier corresponding to the latest first V2X message from at least one second sender identifier; The RSU corresponding to the target second sender identifier is determined as the target RSU.

8. The information processing method according to claim 7, characterized in that: Also includes: If at least one first V2X message does not include the second sender identifier, the target RSU currently corresponding to the OBU is determined in at least one of the following ways: Determine multiple RSUs corresponding to the target range as target RSUs; Among the RSUs that have recently sent a predetermined number of first V2X messages, an RSU whose number of first V2X messages sent is greater than a predetermined threshold is determined as a target RSU.

9. An information processing method, characterized in that: Applied to a roadside unit RSU, the method comprises: Receiving a first V2X message related to the on-board unit OBU; Sending the first V2X message to a multi-access edge computing MEC device or an edge cloud, wherein the MEC device or the edge cloud includes a vehicle-to-vehicle wireless communication technology V2X application layer, so that the V2X application layer parses the first V2X message; Receiving a response content for the OBU determined by the V2X application layer; The response content is forwarded to the OBU.

10. An information processing device, characterized in that: Applied to a multi-access edge computing MEC device or an edge cloud, the MEC device or the edge cloud includes a vehicle wireless communication technology V2X application layer, and the device includes: A parsing module, configured to respond to a first V2X message related to an on-board unit OBU respectively sent by at least one roadside unit RSU, wherein the V2X application layer parses at least one first V2X message; a target determination module, configured to determine, when the V2X application layer determines the response content for the OBU, a target RSU currently corresponding to the OBU according to at least one first V2X message; The information sending module is used to send the response content to the target RSU, so that the target RSU forwards the response content to the OBU.

11. An information processing device, characterized in that: Applied to a roadside unit RSU, the device comprises: A first receiving module, configured to receive a first V2X message related to the on-board unit OBU; A first forwarding module is configured to send the first V2X message to a multi-access edge computing MEC device or an edge cloud, where the MEC device or the edge cloud includes a vehicle wireless communication technology V2X application layer, so that the V2X application layer parses the first V2X message; A second receiving module is used to receive the response content determined by the V2X application layer for the OBU; The second forwarding module is used to forward the response content to the OBU.

12. A vehicle-to-vehicle wireless communication technology V2X system, characterized in that: include: A multi-access edge computing MEC device or edge cloud as described in any one of claims 1 to 8; A roadside unit RSU as claimed in claim 9.

13. An electronic device comprising a memory, a processor and a computer program stored in the memory, characterized in that: The processor executes the computer program to implement the method of any one of claims 1 to 8 or claim 9.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 8 or claim 9 is implemented.

Images