Multi-source data processing method, system, device and equipment and storage medium

Abstract

The invention provides a multi-source data processing method, system and device, equipment and a storage medium. The method comprises the steps of obtaining multi-source signal lamp data, performing data standardization processing on the signal lamp data according to a preset standardization protocol to obtain standardized signal lamp data, making the standardization protocol based on business application of a vehicle end, eliminating the difference of the signal lamp data among the multiple sources through data standardization processing, and obtaining the standardized signal lamp data. The flow of signal lamp data application is ensured, and the data processing flow of the vehicle end is simplified; and performing quality verification on the standardized signal lamp data to determine whether the standardized signal lamp data quality is qualified, and if the standardized signal lamp data quality is qualified, sending the standardized signal lamp data to the vehicle end for application of the vehicle end. According to the method, the development and maintenance cost of the application program is reduced while the safety of the vehicle end is improved.

Description

Technical Field

[0001] The present application relates to the field of intelligent vehicle networking technology, and in particular to a multi-source data processing method, system, device, equipment and storage medium. Background Art

[0002] With the rapid development of smart car networking technology, the application of traffic light data will become more extensive and in-depth. Traffic light data comes from many sources. For example, the data structure of traffic light data provided by different roadside equipment manufacturers is different, which is not completely consistent with the data structure required by vehicle-side services. How to apply multi-source traffic light data to the vehicle side in a simple and efficient manner and ensure the normal operation of vehicle-side services has become a hot topic in this field.

[0003] In the traditional way, developers develop corresponding vehicle-side applications for each type of multi-source traffic light data to adapt to the traffic light data provided by different data sources. However, the above method has the problem of high application development and maintenance costs. Summary of the invention

[0004] The present application provides a multi-source data processing method, system, device, equipment and storage medium to achieve the effect of reducing application development and maintenance costs.

[0005] In a first aspect, the present application provides a multi-source data processing method, comprising:

[0006] Get traffic light data from multiple sources;

[0007] According to the preset standardized protocol, the traffic light data is standardized to obtain standardized traffic light data. The standardized protocol is formulated based on the business application of the vehicle end.

[0008] Perform quality check on the standardized signal light data to determine whether the quality of the standardized signal light data is qualified;

[0009] If the quality of the standardized signal light data is qualified, the standardized signal light data will be sent to the vehicle end for application by the vehicle end.

[0010] In a possible implementation, the multi-source data processing method further includes:

[0011] If the quality of the standardized traffic light data is unqualified, an alarm message will be issued to prompt relevant personnel to conduct an abnormal investigation of the traffic light data.

[0012] In a possible implementation, quality verification of the standardized traffic light data includes:

[0013] Perform data uniqueness check on standardized traffic light data to determine whether the traffic light data corresponding to the same intersection code, the same road direction and the same lane turn is unique;

[0014] Perform data integrity check on standardized traffic light data to determine whether the traffic light data corresponding to all road directions and lane turns under the same intersection coding is complete;

[0015] Verify the data accuracy of standardized traffic light data.

[0016] In a possible implementation, the multi-source data processing method further includes:

[0017] Obtain static road network information, including intersection codes, road directions, and lane turns;

[0018] Verifying the data accuracy of the standardized signal light data, including: based on the static road network information, determining whether the intersection coding, lane turning, road direction and signal light control conditions in the standardized signal light data match the static road network information, so as to complete the data accuracy verification;

[0019] The standardized signal light data is checked for data integrity, including: based on the static road network information, the standardized signal light data is traversed, and for each intersection code, it is determined whether the signal light data for all road directions and all lane turns are included to complete the data integrity check.

[0020] In a possible implementation, the signal light data is subjected to data standardization processing according to a preset standardization protocol to obtain standardized signal light data, including:

[0021] Parsing the data structure of the traffic light data to obtain a plurality of first data field names;

[0022] Based on the mapping relationship between traffic light data and data field names of standardized protocols, the value corresponding to the first data field name is stored in the second data field name to obtain standardized traffic light data. The second data field name is the data field name that has a mapping relationship with the first data field name in the standardized protocol.

[0023] In a second aspect, the present application provides a multi-source data processing system, including: a cloud server, a roadside device, and a vehicle terminal, wherein the cloud server communicates with the roadside device and the vehicle terminal respectively;

[0024] Roadside equipment, used to provide signal light data from multiple sources;

[0025] A cloud server, used to execute the multi-source data processing method as described in any one of the first aspects;

[0026] On the vehicle side, it is used to apply standardized signal light data.

[0027] In a third aspect, the present application provides a multi-source data processing device, comprising:

[0028] An acquisition module is used to acquire traffic light data from multiple sources;

[0029] The standardization module is used to perform data standardization processing on the signal light data according to the preset standardization protocol to obtain the standardized signal light data. The standardization protocol is formulated based on the business application of the vehicle end;

[0030] A verification module is used to perform quality verification on the standardized signal light data to determine whether the quality of the standardized signal light data is qualified;

[0031] The sending module is used to send the standardized signal light data to the vehicle end for application by the vehicle end when the quality of the standardized signal light data is qualified.

[0032] In a possible implementation, the sending module is further used to: when the quality of the standardized traffic light data is unqualified, send out an alarm message, and the alarm message is used to prompt relevant personnel to conduct an abnormality check on the traffic light data.

[0033] In one possible implementation, the verification module is specifically used to: perform data uniqueness verification on standardized signal light data to determine whether the signal light data corresponding to the same intersection code, the same road direction, and the same lane turn are unique; perform data integrity verification on standardized signal light data to determine whether the signal light data corresponding to all road directions and lane turns under the same intersection code are complete; and perform data accuracy verification on standardized signal light data.

[0034] In a possible implementation, the acquisition module is also used to: acquire static road network information, which includes intersection codes, road directions, and lane turns. Accordingly, the verification module is also used to: determine whether the intersection codes, lane turns, road directions, and signal light control conditions in the standardized signal light data match the static road network information based on the static road network information, so as to complete the data accuracy verification; and, based on the static road network information, traverse the standardized signal light data, and determine whether each intersection code contains signal light data for all road directions and all lane turns, so as to complete the data integrity verification.

[0035] In one possible implementation, the standardization module is specifically used to: parse the data structure of the traffic light data to obtain multiple first data field names; based on the mapping relationship between the traffic light data and the data field names of the standardized protocol, store the values ​​corresponding to the first data field names in the second data field names to obtain standardized traffic light data, wherein the second data field names are data field names that have a mapping relationship with the first data field names in the standardized protocol.

[0036] In a fourth aspect, the present application provides a multi-source data processing device, including: a memory, a processor;

[0037] The memory stores computer-executable instructions;

[0038] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the above first aspect and / or various possible implementations of the first aspect.

[0039] In a fifth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed, they are used to implement the above first aspect and / or various possible implementations of the first aspect.

[0040] In a sixth aspect, the present application provides a computer program product, including a computer program, which, when executed, implements the above first aspect and / or various possible implementations of the first aspect.

[0041] The multi-source data processing method, system, device, equipment and storage medium provided by the present application perform data standardization processing on the obtained multi-source signal light data according to a preset standardized protocol to obtain standardized signal light data, thereby eliminating the differences in signal light data between multiple sources, ensuring the process-based application of signal light data, and simplifying the data processing process on the vehicle side; performing quality verification on the standardized signal light data to ensure the quality of the standardized signal light data, and sending the standardized signal light data of qualified quality to the vehicle side for application on the vehicle side; therefore, the present application can reduce the cost of application development and maintenance while improving the safety of the vehicle side. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0043] Figure 1 A schematic diagram of a scenario of the multi-source data processing method provided in this application;

[0044] Figure 2 A flowchart of the multi-source data processing method provided in this application;

[0045] Figure 3 A schematic diagram of the structure of the multi-source data processing system provided by this application;

[0046] Figure 4 A schematic diagram of the structure of the multi-source data processing device provided by this application;

[0047] Figure 5 This is a schematic diagram of the structure of the multi-source data processing device provided in this application.

[0048] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0049] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0050] In the related technology, since the traffic information light data formats provided by different roadside equipment manufacturers are not unified, the data processing flow is complicated when the vehicle side applies the above traffic information light data. Developers are usually required to develop corresponding vehicle-side applications separately for each type of data in the multi-source traffic light data to adapt to the traffic light data provided by different data sources, which leads to high application development and maintenance costs.

[0051] In response to the technical problems existing in the above-mentioned related technologies, the multi-source data processing method, system, device, equipment and storage medium provided in the present application standardize the signal light data from multiple sources, eliminate the differences in signal light data between multiple sources, ensure the process of signal light data application, simplify the data processing process on the vehicle side, and perform quality verification on the standardized signal light data, and send the qualified standardized signal light data to the vehicle side for application on the vehicle side, thereby ensuring the quality of the standardized signal light data and improving the safety of the vehicle side.

[0052] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0053] Figure 1 The following is a schematic diagram of a scenario of the multi-source data processing method provided in this application. Figure 1 As shown, the application scenario of the present application may include a cloud 11, a traffic light 12-1, a traffic light 12-2, a roadside device 13-1, a roadside device 13-2, and a vehicle 14, wherein the formats of the traffic light data reported by different roadside devices are not uniform, and the business operation on the vehicle 14 requires the cloud 11 to provide traffic light data support, such as assisted driving functions, system navigation, or traffic planning. Specifically, the roadside devices 13-1 and 13-2 respectively collect the traffic light data of the traffic lights 12-1 and 12-2, and send them to the cloud 11. After receiving the traffic light data reported by each roadside device, the cloud 11 performs data standardization processing, and then sends the processed standardized traffic light data to the vehicle 14. The vehicle 14 makes corresponding driving decisions based on the standardized traffic light data provided by the cloud 11.

[0054] Combine the following Figure 1 For application scenarios, refer to Figure 2 The multi-source data processing method provided by an embodiment of the present application is described below. Figure 1 It should be noted that the above application scenarios are only shown to facilitate understanding of the spirit and principles of this application, and the implementation methods of this application are not affected by Figure 1 Limitations of the application scenario shown.

[0055] Figure 2 A flowchart of the multi-source data processing method provided in this application is shown in FIG. Figure 2 As shown, the method includes:

[0056] S201. Acquire traffic light data from multiple sources.

[0057] Multi-source traffic light data can be understood as traffic light status and related information obtained from multiple different sources, providing more comprehensive and accurate traffic signal control and management.

[0058] Traffic light data includes traffic light control mode, intersection number, lane turn, road direction, real-time signal status, signal cycle and phase, etc.

[0059] For example, multiple sources include public transportation systems, traffic information platforms, API interfaces or roadside equipment, etc., where the roadside equipment is, for example, a traffic signal controller. Multiple sources may also include roadside equipment from different manufacturers. Usually, the data formats or data structures collected by roadside equipment from different manufacturers are not unified.

[0060] For example, the traffic signal controller collects the traffic light data of the traffic light 12 - 1 in real time, wireless communication is established between the cloud 11 and the traffic signal controller, the cloud 11 subscribes to the traffic light data on the traffic signal controller, and the traffic signal controller sends the collected traffic light data to the cloud 11 in real time.

[0061] S202. Perform data standardization processing on the traffic light data according to a preset standardized protocol to obtain standardized traffic light data. The standardized protocol is formulated based on the business application of the vehicle end.

[0062] The standardized protocol stipulates that data with the same meaning from various sources will be converted into the format and structure corresponding to the standardized protocol. The standardized protocol can be compatible with all business applications on the vehicle side, or it can be formulated separately for business types or business scenarios. After the standardized protocol is formulated, it will be stored in the server or database where the cloud is located.

[0063] Data standardization includes converting traffic light data from different sources or formats into a consistent format and structure to improve data usability.

[0064] For example, when the cloud 11 obtains the traffic light data for the traffic light 12-1 reported by the traffic signal controller, the data standardization processing interface is automatically called to perform data standardization processing on the traffic light data to obtain standardized traffic light data. The data standardization processing interface can be developed based on a standardized protocol and integrated in the server system of the cloud.

[0065] Optionally, for each of the multiple sources, a mapping relationship between traffic light data and a standardized protocol is pre-established and stored in the cloud 11. Manufacturer information tags, platform tags or system tags can also be added during storage to distinguish between the sources. When the cloud 11 obtains the traffic light data for the traffic light 12-1 reported by the traffic signal controller, for example, the mapping relationship corresponding to the traffic signal controller is automatically matched according to the manufacturer information of the traffic signal controller, and the traffic light data is standardized according to the mapping relationship.

[0066] For example, suppose the traffic light data format reported by the traffic signal controller is as follows:

[0067] ```json{"id":"signal_123","status":"green","timestamp":"2023-10-01T12:34:56Z"}```

[0068] Assume that the pre-defined standardized protocol requires the following fields:

[0069] - `signal_id`: the unique identifier of the signal

[0070] - `state`: the state of the traffic light (red, yellow, green)

[0071] - `time`: timestamp, ISO 8601 format

[0072] According to the standardized protocol, the signal light data reported by the traffic signal controller is converted into a standardized format to obtain standardized signal light data. For example, the standardized signal light data is as follows:

[0073] ```json{"signal_id":"signal_123","state":"green","time":"2023-10-01T12:34:56Z"}```

[0074] S203: Perform quality verification on the standardized traffic light data to determine whether the quality of the standardized traffic light data is qualified.

[0075] Quality verification includes setting verification rules to verify the quality of data. The verification rules are not limited to consistency verification, integrity verification, rationality verification, and accuracy verification.

[0076] For example, the state consistency check is performed on the standardized traffic light data to determine whether the change of the traffic light state complies with traffic regulations. For example, a red light should be followed by a green light or a yellow light instead of jumping directly to another red light.

[0077] For example, integrity check is performed on standardized traffic light data to determine whether field names such as traffic light status, traffic light time, phase, countdown, and the values ​​corresponding to the field names all exist.

[0078] For example, a rationality check is performed on the standardized traffic light data to determine whether the traffic light data is within a reasonable range. For example, the status of a traffic light can only be red, yellow, or green, and other statuses are considered abnormal.

[0079] For example, the standardized traffic light data is checked for accuracy to determine whether the standardized traffic light data is consistent with other data sources (such as cameras, sensors, static road network information, etc.).

[0080] S204: If the quality of the standardized signal light data is qualified, the standardized signal light data is sent to the vehicle end for application by the vehicle end.

[0081] When the standardized traffic light data meets all the verification rules of quality verification, the standardized traffic light data is considered to be of qualified quality.

[0082] For example, when the quality of standardized signal light data is monitored to be qualified, the vehicle-side and the cloud-side can transmit data through V2X communication technology, such as Dedicated Short Range Communications (DSRC) and Cellular Vehicle-to-Everything (C-V2X). The cloud-side sends standardized signal light data to the vehicle-side. Optionally, the standardized signal light data can also be encrypted and sent to the vehicle-side, such as using symmetric encryption algorithm AES and asymmetric encryption algorithm RSA, to ensure security during data transmission.

[0083] The vehicle receives and processes standardized traffic light data for functions such as navigation and autonomous driving.

[0084] In the embodiment of the present application, data standardization is performed on signal light data from multiple sources to eliminate differences in signal light data between multiple sources, ensure the process-based application of signal light data, and simplify the data processing process on the vehicle side; quality verification is performed on the standardized signal light data to ensure the quality of the standardized signal light data, and the standardized signal light data with qualified quality is sent to the vehicle side, which can improve the safety of the vehicle side while reducing the cost of application development and maintenance.

[0085] In another case, the multi-source data processing method further includes: if the quality of the standardized traffic light data is unqualified, an alarm message is issued, and the alarm message is used to prompt relevant personnel to conduct an abnormality check on the traffic light data.

[0086] It can be understood that when the standardized traffic light data does not meet any quality verification rule, it is considered that the quality of the standardized traffic light data is unqualified.

[0087] For example, when the quality of standardized traffic light data is detected to be unqualified, the alarm module is automatically triggered to issue an alarm message, which can be sent to operation and maintenance personnel via SMS, email, phone call, etc., prompting the operation and maintenance personnel to check for abnormal traffic light data from the source of the traffic light data.

[0088] The embodiments of the present application effectively monitor the quality of traffic light data and ensure the quality of traffic light data required for vehicle-side services, thereby ensuring the safe and stable operation of vehicle-side services.

[0089] For example, the standardized traffic light data obtained after data standardization processing based on the standardized protocol is shown below:

[0090]

[0091]

[0092] Among them, control_mode includes: 0-multi-period timing control, 1-adaptive control, 2-manual control, 3-sensing control. This field is used to distinguish the control modes so that the vehicle side can take different measures; map_cross_id consists of the city postal code and the specific intersection code, and is unique; the vehicle side can do countdown deduction through the green_time, red_time, yellow_time and next_lamp_status fields.

[0093] Accordingly, in some embodiments, performing quality verification on the standardized signal light data may include the following steps:

[0094] Step 1.1: Perform data uniqueness verification on the standardized traffic light data to determine whether the traffic light data corresponding to the same intersection code, the same road direction, and the same lane turn are unique.

[0095] In this step, the data uniqueness verification of the standardized traffic light data can be performed based on a duplicate elimination algorithm, setting a uniqueness check unit, or building a data quality verification model.

[0096] For example, by traversing the standardized traffic light data, for the case where the intersection code is 310000-300023, the road direction is from east to west, and the lane turn is straight, determine whether the traffic light data corresponding to the same traffic light time in this case is unique. The traffic light data includes real-time signal status (current light color), countdown, next light color, phase number, stage number, signal cycle (green light duration, red light duration, yellow light duration), green light time in the next stage, and so on.

[0097] Step 1.2: Perform data integrity check on the standardized traffic light data to determine whether the traffic light data corresponding to all road directions and lane turns under the same intersection coding are complete.

[0098] In this step, the data integrity of the standardized traffic light data can be verified by setting an integrity check unit or building a data quality verification model.

[0099] For example, if the intersection codes 310000-300023 include four road directions from east to west, from west to tunnel, from south to north, and from north to south, and each road direction includes two lane turns, then the real-time signal status (current light color), countdown, next light color, phase number, stage number, signal cycle (green light duration, red light duration, yellow light duration), next stage green light time and other field names and the values ​​corresponding to the field names are determined whether they exist under these four road directions and the two lane turns contained in each road direction.

[0100] Step 1.3: Verify the accuracy of the standardized traffic light data.

[0101] In this step, the accuracy of the standardized traffic light data can be verified by setting an accuracy check unit or building a data quality verification model.

[0102] For example, the standardized traffic light data may be compared with other data sources (eg, cameras, sensors, static road network information, etc.) to determine whether the data are consistent.

[0103] The embodiment of the present application performs quality verification on standardized traffic light data to ensure data quality, provide a reliable data foundation for vehicle-side business applications, and thereby ensure the normal operation of vehicle-side business and improve vehicle-side safety.

[0104] Based on the above embodiments, in a possible implementation manner, the multi-source data processing method further includes: acquiring static road network information, the static road network information including intersection codes, road directions and lane turns.

[0105] Among them, static road network information can be obtained through a variety of channels, including but not limited to: open data platforms, map data download software and third-party platforms, such as geographic information system departments or commercial map service providers.

[0106] Correspondingly, the standardized traffic light data is checked for data integrity, including: based on the static road network information, the standardized traffic light data is traversed, and for each intersection code, it is determined whether the traffic light data for all road directions and all lane turns are included to complete the data integrity check.

[0107] The standardized signal light data are traversed to ensure that each piece of standardized signal light data contains signal light data for all road directions and all lane turns encoded at this intersection.

[0108] Correspondingly, the standardized traffic light data is verified for data accuracy, including: based on the static road network information, determining whether the intersection coding, lane turning, road direction and traffic light control status in the standardized traffic light data match the static road network information to complete the data accuracy verification.

[0109] For example, the intersection code, lane turn, road direction field name and the corresponding value of the field name in the standardized traffic light data are extracted respectively, and each field name and the corresponding value of the field name are matched with the corresponding field in the static road network information. If they are consistent, it means that the matching relationship is accurate. For example, when the intersection code in the standardized traffic light data is 310000-300023 and the road direction is from east to west, the lane turn includes left turn, straight and right turn, while when the intersection code in the static road network information is 310000-300023 and the road direction is from east to west, the lane turn includes straight and right turn. At this time, the judgment result is mismatch, and the data is regarded as abnormal data.

[0110] In some embodiments, data standardization is performed on the traffic light data according to a preset standardization protocol to obtain standardized traffic light data, which specifically includes the following steps:

[0111] Step 2.1, parse the data structure of the traffic light data to obtain multiple first data field names.

[0112] For example, the signal light data is obtained from the signal light control system or the traffic information platform. Assume that the signal light data format is as follows:

[0113] ```json{"id":"310000-300023","status":"green","timestamp":"2023-10-0112:34:56"}```

[0114] Parse the acquired traffic light data and extract the required multiple first field names: id, status, and timestamp.

[0115] Step 2.2: Based on the mapping relationship between the traffic light data and the data field names of the standardized protocol, the value corresponding to the first data field name is stored in the second data field name to obtain standardized traffic light data. The second data field name is the data field name that has a mapping relationship with the first data field name in the standardized protocol.

[0116] The first data field name and the second data field name have the same meaning, and mapping can be performed only when the signal light data from each source contains a field name with the same meaning as the standardized protocol.

[0117] The mapping relationship is established and stored in advance. The data structure and format of traffic lights from different sources are not unified, resulting in different mapping relationships between traffic light data from different sources and the data field names of the standardized protocol. For easy distinction, corresponding labels can be added when establishing the mapping relationship. Figure 1As shown, the mapping relationship is stored in the cloud 11. When storing, roadside equipment manufacturer information tags, platform tags or system tags can also be added to distinguish between sources. For example, when the cloud 11 obtains the traffic light data for the traffic light 12-1 reported by the traffic signal controller, the mapping relationship corresponding to the traffic signal controller is automatically matched according to the manufacturer information of the traffic signal controller, and the traffic light data is standardized according to the mapping relationship.

[0118] Optionally, the format of the value corresponding to the first data field name may also be constrained, for example, the length and type of the value may be constrained.

[0119] For example, assuming that the preset standardized protocol requires the following fields, that is, the second data field name includes:

[0120] - `map_cross_id`: intersection code, unique identifier of the traffic light

[0121] - `lamp_status`: current lamp color (red, yellow, green)

[0122] - `create_time`: semaphore time

[0123] The first field names obtained by parsing in step 2.1 include: id, status, and timestamp.

[0124] According to the mapping relationship, the traffic light data is converted into a standardized format to obtain standardized traffic light data. For example:

[0125] ```json{"map_cross_id":"310000-300023","lamp_status":"green","create_time":"1696134896"}```

[0126] In the embodiments of the present application, standard signal light data with a unified structure or format is formed by performing data standardization processing on the signal light data, thereby eliminating the differences in signal light data between multiple sources. Data standardization processing is performed on the signal light data before it is applied to the vehicle side, thereby ensuring the process-based application of the signal light data, thereby simplifying the data processing process on the vehicle side, avoiding the related technology of developing a separate vehicle-side application for each of the multiple sources, and reducing development and maintenance costs.

[0127] Figure 3 A schematic diagram of the structure of the multi-source data processing system provided in this application, such as Figure 3 As shown, the multi-source data processing system 30 provided by the present application includes: a cloud server 31, a roadside device 32 and a vehicle end 33, wherein the cloud server 31 communicates with the roadside device 32 and the vehicle end 33 respectively;

[0128] Roadside equipment 32, used to provide signal light data from multiple sources;

[0129] A cloud server 31, configured to execute the multi-source data processing method as described in any one of the above embodiments;

[0130] The vehicle end 33 is used to apply standardized signal light data.

[0131] In this embodiment, the multi-source data processing system 30 can execute the technical solution shown in the above method embodiment, and its implementation principle and beneficial effects are similar, which will not be described again.

[0132] Figure 4 A schematic diagram of the structure of the multi-source data processing device provided in this application, such as Figure 4 As shown, the multi-source data processing device 40 provided in this embodiment includes: an acquisition module 41, a standardization module 42, a verification module 43 and a sending module 44. Among them:

[0133] An acquisition module 41 is used to acquire traffic light data from multiple sources;

[0134] A standardization module 42 is used to perform data standardization processing on the signal light data according to a preset standardization protocol to obtain standardized signal light data, wherein the standardization protocol is formulated based on the business application of the vehicle end;

[0135] A verification module 43, used to perform quality verification on the standardized signal light data to determine whether the quality of the standardized signal light data is qualified;

[0136] The sending module 44 is used to send the standardized signal light data to the vehicle end for application by the vehicle end when the quality of the standardized signal light data is qualified.

[0137] In a possible implementation manner, the sending module 44 is further used to: when the quality of the standardized traffic light data is unqualified, send out an alarm message, and the alarm message is used to prompt relevant personnel to conduct an abnormality check on the traffic light data.

[0138] In one possible implementation, the verification module 43 is specifically used to: perform data uniqueness verification on the standardized signal light data to determine whether the signal light data corresponding to the same intersection code, the same road direction, and the same lane turn are unique; perform data integrity verification on the standardized signal light data to determine whether the signal light data corresponding to all road directions and lane turns under the same intersection code are complete; and perform data accuracy verification on the standardized signal light data.

[0139] In a possible implementation, the acquisition module 41 is also used to: acquire static road network information, which includes intersection codes, road directions, and lane turns. Accordingly, the verification module 43 is also used to: determine whether the intersection codes, lane turns, road directions, and signal light control conditions in the standardized signal light data match the static road network information based on the static road network information, so as to complete the data accuracy verification; and, based on the static road network information, traverse the standardized signal light data, and determine whether each intersection code contains signal light data for all road directions and all lane turns, so as to complete the data integrity verification.

[0140] In one possible implementation, the standardization module 42 is specifically used to: parse the data structure of the traffic light data to obtain multiple first data field names; based on the mapping relationship between the traffic light data and the data field names of the standardized protocol, store the values ​​corresponding to the first data field names in the second data field names to obtain standardized traffic light data, where the second data field names are the data field names that have a mapping relationship with the first data field names in the standardized protocol.

[0141] The multi-source data processing device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0142] Figure 5 This is a schematic diagram of the structure of the multi-source data processing device provided by this application. Figure 5 As shown, the multi-source data processing device 50 provided in this embodiment includes: at least one processor 501 and a memory 502. Optionally, the multi-source data processing device 50 also includes a communication component 503. The processor 501, the memory 502 and the communication component 503 are connected via a bus 504.

[0143] In a specific implementation process, at least one processor 501 executes the computer-executable instructions stored in the memory 502, so that at least one processor 501 executes the above method.

[0144] The specific implementation process of the processor 501 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0145] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0146] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-volatile Memory, NVM), such as at least one disk memory.

[0147] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0148] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0149] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0150] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0151] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0152] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0153] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0154] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0155] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0156] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0157] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A multi-source data processing method, characterized in that: include: Get traffic light data from multiple sources; According to a preset standardized protocol, the signal light data is subjected to data standardization processing to obtain standardized signal light data, wherein the standardized protocol is formulated based on a business application of the vehicle end; Performing quality verification on the standardized signal light data to determine whether the standardized signal light data is of qualified quality; If the quality of the standardized signal light data is qualified, the standardized signal light data is sent to the vehicle end for application by the vehicle end.

2. The method according to claim 1, characterized in that: Also includes: If the quality of the standardized traffic light data is unqualified, an alarm message is issued, and the alarm message is used to prompt relevant personnel to conduct abnormality inspection of the traffic light data.

3. The method according to claim 1 or 2, characterized in that: The quality verification of the standardized signal light data includes: Performing data uniqueness check on the standardized signal light data to determine whether the signal light data corresponding to the same intersection code, the same road direction and the same lane turn are unique; Performing a data integrity check on the standardized signal light data to determine whether the signal light data corresponding to all road directions and lane turns under the same intersection code are complete; The standardized signal light data is verified for data accuracy.

4. The method according to claim 3, characterized in that Also includes: Obtaining static road network information, wherein the static road network information includes intersection codes, road directions, and lane turns; The data accuracy verification of the standardized signal light data includes: based on the static road network information, determining whether the intersection coding, lane turning, road direction and signal light control status in the standardized signal light data match the static road network information to complete the data accuracy verification; The data integrity check of the standardized signal light data includes: based on the static road network information, traversing the standardized signal light data, and determining for each intersection code whether it contains signal light data for all road directions and all lane turns, so as to complete the data integrity check.

5. The method according to claim 1 or 2, characterized in that: The step of performing data standardization processing on the signal light data according to a preset standardization protocol to obtain standardized signal light data includes: Parsing the data structure of the signal light data to obtain a plurality of first data field names; Based on the mapping relationship between the traffic light data and the data field names of the standardized protocol, the value corresponding to the first data field name is stored in the second data field name to obtain standardized traffic light data, and the second data field name is the data field name that has a mapping relationship with the first data field name in the standardized protocol.

6. A multi-source data processing system, characterized in that: include: A cloud server, a roadside device and a vehicle terminal, wherein the cloud server communicates with the roadside device and the vehicle terminal respectively; The roadside equipment is used to provide signal light data from multiple sources; The cloud server is used to execute the multi-source data processing method according to any one of claims 1 to 5; The vehicle end is used to apply the standardized signal light data.

7. A multi-source data processing device, characterized in that: include: An acquisition module is used to acquire traffic light data from multiple sources; A standardization module, used for performing data standardization processing on the signal light data according to a preset standardization protocol to obtain standardized signal light data, wherein the standardization protocol is formulated based on a business application of the vehicle end; A verification module, used for performing quality verification on the standardized signal light data to determine whether the quality of the standardized signal light data is qualified; The sending module is used to send the standardized signal light data to the vehicle end for application by the vehicle end when the quality of the standardized signal light data is qualified.

8. A multi-source data processing device, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 5.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 5 when executed.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 5 when being executed.

Images