CN114679417A - Vehicle-mounted data distribution method, system and device and readable storage medium - Google Patents
Vehicle-mounted data distribution method, system and device and readable storage medium Download PDFInfo
- Publication number
- CN114679417A CN114679417A CN202210247970.6A CN202210247970A CN114679417A CN 114679417 A CN114679417 A CN 114679417A CN 202210247970 A CN202210247970 A CN 202210247970A CN 114679417 A CN114679417 A CN 114679417A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- data
- mounted data
- management platform
- message queue
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
- H04L47/2433—Allocation of priorities to traffic types
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/50—Queue scheduling
- H04L47/62—Queue scheduling characterised by scheduling criteria
- H04L47/622—Queue service order
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/90—Buffering arrangements
- H04L49/9063—Intermediate storage in different physical parts of a node or terminal
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application relates to the technical field of vehicle-mounted data processing, and discloses a method, a system and a device for distributing vehicle-mounted data and a readable storage medium. The method comprises the following steps: acquiring vehicle-mounted data returned by at least one vehicle-mounted system; buffering the vehicle-mounted data in a message queue; and acquiring at least part of vehicle-mounted data from the front end of the message queue, and distributing the vehicle-mounted data to the corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data. By the mode, the persistence of the vehicle-mounted data can be guaranteed, the data volume of the vehicle management platform for receiving the vehicle-mounted data is reduced, and the processing efficiency of the vehicle management platform for the vehicle-mounted data is improved.
Description
Technical Field
The present application relates to the field of vehicle-mounted data processing technologies, and in particular, to a method, a system, an apparatus, and a readable storage medium for distributing vehicle-mounted data.
Background
At present, with the rapid development of the internet and the rapid popularization of 5G, the era of interconnection of everything is coming, vehicles can return various data collected by sensors in real time through a network, all departments of a company need to analyze the data and perform iterative evolution of an algorithm, and all departments of the company develop corresponding platforms in order to rapidly process the data and accurately analyze the data, but the vehicle-mounted data needed by the management platforms are different, if a user feels like to directly transmit all the vehicle-mounted data to all the management platforms for processing, the time is very long, and the processing efficiency is low.
For example, management platforms of different departments have different requirements on data, for example, a vehicle state monitoring platform needs the online condition of a vehicle, the automatic driving mileage of each vehicle, abnormal vehicle reporting information, vehicle order information and the like, has higher requirements on the real-time state of the vehicle, and needs to send the data to the vehicle in real time; the hardware research and development platform needs to know the state information of each piece of hardware of the vehicle; the route planning platform needs to know the position information of the vehicle running; the algorithm platform requires vehicle history data and the like.
Disclosure of Invention
The application provides a distribution method, a distribution system, a distribution device and a readable storage medium of vehicle-mounted data, which can ensure the persistence of the vehicle-mounted data, reduce the data volume of the vehicle management platform for receiving the vehicle-mounted data and improve the processing efficiency of the vehicle management platform for the vehicle-mounted data.
In order to solve the technical problem, the application adopts a technical scheme that: provided is a method for distributing vehicle-mounted data, comprising the following steps: acquiring vehicle-mounted data returned by at least one vehicle-mounted system; buffering the vehicle-mounted data in a message queue; and acquiring at least part of vehicle-mounted data from the front end of the message queue, and distributing the vehicle-mounted data to a corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data.
Before vehicle-mounted data is cached in a message queue, the method comprises the following steps: packaging the vehicle-mounted data according to a preset field; buffering the vehicle-mounted data in a message queue, wherein the buffering comprises the following steps: and buffering the packaged vehicle-mounted data in a message queue.
Wherein, encapsulate vehicle data according to preset field, include: and encapsulating the vehicle-mounted data according to the context field, the event type field, the metadata field, the priority field and the payload field.
The method for acquiring at least part of vehicle-mounted data from the front end of the message queue comprises the following steps: and monitoring the vehicle-mounted data of the message queue, and acquiring at least part of the vehicle-mounted data from the front end of the message queue when the vehicle-mounted data is monitored.
Before vehicle-mounted data is cached in a message queue, the method comprises the following steps: packaging the vehicle-mounted data according to the event type field; acquiring at least part of vehicle-mounted data from the front end of the message queue, and distributing the vehicle-mounted data to a corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data, wherein the method comprises the following steps: determining whether the event type of target vehicle-mounted data in at least part of vehicle-mounted data is matched with a preset event type of a vehicle management platform; if the matching is carried out, carrying out data encapsulation on the target vehicle-mounted data again, and distributing the data to the corresponding vehicle management platform; and if not, discarding the target vehicle-mounted data.
And the target vehicle-mounted data is subjected to data packaging again and is distributed to the corresponding vehicle management platform, and the method comprises the following steps: filtering at least part of the packaged vehicle-mounted data; and distributing at least part of the filtered vehicle-mounted data to the corresponding vehicle management platform.
Wherein, distribute at least part on-vehicle data after filtering to corresponding vehicle management platform, include: judging whether the data format of at least part of the vehicle-mounted data meets the requirement or not; if not, the data format of at least part of the vehicle-mounted data is converted into the data format of the vehicle management platform and then distributed to the vehicle management platform.
Wherein, the method also comprises: determining a publisher and a publisher state corresponding to the vehicle management platform; and if the state of the publisher is in the activated state, at least part of the vehicle-mounted data is published to the vehicle management platform through the publisher.
Wherein, the method also comprises: and when at least part of the vehicle-mounted data is successfully published to the vehicle management platform, resetting the publisher state and sending feedback information to the message queue.
Wherein, the method also comprises: and when at least part of vehicle-mounted data fails to be issued to the vehicle management platform, counting the continuous failure times of the issuer, and performing fusing processing based on the continuous failure times.
Wherein, the method also comprises: establishing a list of items to be processed according to at least part of the vehicle-mounted data; checking whether a to-be-processed item list of the consumer needing to be recovered exists; if yes, consuming from the starting position of the list of the items to be processed; if not, consuming from the unconsumed location of the list of pending entries.
In order to solve the above technical problem, another technical solution adopted by the present application is: there is provided an in-vehicle data distribution system including: the data interface module is used for acquiring vehicle-mounted data returned by at least one vehicle-mounted system; the message queue module is connected with the data interface module and used for caching the vehicle-mounted data by using the message queue; and the data distribution module is connected with the message queue module and used for acquiring at least part of vehicle-mounted data from the front end of the message queue and distributing the vehicle-mounted data to the corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data.
Wherein, the data distribution system further comprises: and the remote configuration module is used for carrying out remote system configuration on the data distribution system.
In order to solve the above technical problem, another technical solution adopted by the present application is: the distribution device of the vehicle-mounted data comprises a processor and a memory coupled with the processor; wherein the memory is used for storing computer programs, and the processor is used for executing the computer programs so as to realize the method provided by the technical scheme.
In order to solve the technical problem, the other technical scheme adopted by the application is as follows: a computer-readable storage medium is provided for storing a computer program for implementing the method as provided in the above solution when the computer program is executed by a processor.
The beneficial effects of the embodiment of the application are that: different from the prior art, the method, the system, the device and the readable storage medium for distributing the vehicle-mounted data provided by the application comprise the following steps: acquiring vehicle-mounted data returned by at least one vehicle-mounted system; buffering the vehicle-mounted data in a message queue; and acquiring at least part of vehicle-mounted data from the front end of the message queue, and distributing the vehicle-mounted data to a corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data. Through the mode, on one hand, the vehicle-mounted data are cached through the message queue, the persistence of the vehicle-mounted data can be guaranteed, on the other hand, the vehicle-mounted data are distributed to the corresponding vehicle management platform according to the type of at least part of the vehicle-mounted data, the data volume of the vehicle management platform for receiving the vehicle-mounted data can be reduced, and the processing efficiency of the vehicle management platform for the vehicle-mounted data is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts. Wherein:
Fig. 1 is a schematic flowchart of an embodiment of a method for distributing vehicle-mounted data provided in the present application;
FIG. 2 is a schematic view of an application scenario of the vehicle-mounted data distribution method provided in the present application;
FIG. 3 is a schematic flow chart diagram illustrating another embodiment of a method for distributing vehicle-mounted data provided by the present application;
FIG. 4 is a schematic flow chart diagram illustrating another embodiment of a method for distributing vehicle-mounted data provided by the present application;
FIG. 5 is a schematic flow chart diagram illustrating one embodiment of step 45 provided herein;
FIG. 6 is a schematic flow chart diagram illustrating an embodiment of step 452 provided herein;
FIG. 7 is a schematic flow chart diagram illustrating another embodiment of a method for distributing vehicle-mounted data provided by the present application;
FIG. 8 is a schematic flow chart diagram illustrating another embodiment of a method for distributing vehicle-mounted data provided by the present application;
FIG. 9 is a schematic structural diagram of an embodiment of an in-vehicle data distribution system provided by the present application;
FIG. 10 is a schematic view of an application scenario of the vehicle-mounted data distribution system provided in the present application;
FIG. 11 is a schematic workflow diagram of a data interface module provided herein;
FIG. 12 is a schematic workflow diagram of a data distribution module provided herein;
FIG. 13 is another schematic workflow diagram of a data distribution module provided herein;
FIG. 14 is a schematic view of another workflow of a data distribution module provided herein;
FIG. 15 is a schematic view of another workflow of a data distribution module provided herein;
FIG. 16 is a schematic view of another workflow of a data distribution module provided herein;
FIG. 17 is another schematic workflow diagram of a data distribution module provided herein;
FIG. 18 is a schematic structural diagram of another embodiment of an in-vehicle data distribution system provided by the present application;
FIG. 19 is a schematic structural diagram of an embodiment of a device for distributing vehicle-mounted data provided in the present application;
FIG. 20 is a schematic structural diagram of an embodiment of a computer-readable storage medium provided in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some of the structures related to the present application are shown in the drawings, not all of the structures. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
Referring to fig. 1, fig. 1 is a schematic flowchart of an embodiment of a distribution method of vehicle-mounted data provided in the present application. The method comprises the following steps:
step 11: and acquiring vehicle-mounted data returned by at least one vehicle-mounted system.
In some embodiments, the vehicle-mounted data returned by at least one vehicle-mounted system can be acquired by means of wireless transmission. For example, a plurality of data interfaces are provided, each distributed hierarchically. Each data interface is used for acquiring vehicle-mounted data returned by a vehicle-mounted system.
In some embodiments, the vehicle-mounted data returned by at least one vehicle-mounted system can be acquired according to a preset period.
In some embodiments, the vehicle data returned by at least one vehicle system can be received in real time.
The vehicle-mounted data can include the online condition of the vehicle, the driving mileage, abnormal data of the vehicle, vehicle order information, state information of each piece of hardware of the vehicle, position information of the vehicle in running, historical data of the vehicle and the like.
Step 12: and buffering the vehicle-mounted data in a message queue.
In some embodiments, the message queue may be a redis stream message queue. The stream message queue provides the functions of message persistence and main copied, can allow any client to access data at any moment, memorizes the access position of each client and can also ensure that the data is not lost. The writing speed is very fast, and the method is very suitable for being used as the middleware of the real-time distribution system.
In some embodiments, the message queue may also be at least one of zeroMQ, RabbitMQ, ActiveMQ, and Kafka/Jafka.
Step 13: and acquiring at least part of vehicle-mounted data from the front end of the message queue, and distributing the vehicle-mounted data to a corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data.
The types of at least part of the vehicle-mounted data can be classified into vehicle online conditions, driving mileage, vehicle abnormal data, vehicle order information, vehicle hardware state information, vehicle driving position information, vehicle historical data and the like.
In some embodiments, the vehicle-mounted data of the message queue is monitored, and when the vehicle-mounted data is monitored, at least part of the vehicle-mounted data is obtained from the front end of the message queue and is distributed to the corresponding vehicle management platform according to the type of at least part of the vehicle-mounted data.
In an application scenario, the following is explained with reference to fig. 2:
and (5) acquiring the vehicle-mounted data returned by the vehicle-mounted system A, the vehicle-mounted system B and the vehicle-mounted system C in real time through the step 11.
After the vehicle-mounted data returned by the vehicle-mounted system A, the vehicle-mounted system B and the vehicle-mounted system C are obtained, the vehicle-mounted data are sent to a message queue for caching.
After the vehicle-mounted data are cached in the message queue, at least part of the vehicle-mounted data are obtained from the front end of the message queue and are distributed to the corresponding vehicle management platform D, the vehicle management platform E and the vehicle management platform F according to the type of the at least part of the vehicle-mounted data.
For example, there are 100 pieces of vehicle data in the message queue. And acquiring 20 pieces of vehicle-mounted data from the front end of the message queue, and distributing the 20 pieces of vehicle-mounted data to a corresponding vehicle management platform D, a corresponding vehicle management platform E or a corresponding vehicle management platform F according to the types of the 20 pieces of vehicle-mounted data. After the distribution is successful, the feedback is sent to the message queue module 20. The message queue module 20 clears the 20 pieces of in-vehicle data. The data distribution module 30 acquires 20 pieces of vehicle-mounted data from the remaining 80 pieces of vehicle-mounted data in the message queue in sequence again, and distributes the 20 pieces of vehicle-mounted data to the corresponding vehicle management platform D, the corresponding vehicle management platform E and the corresponding vehicle management platform F according to the types of the 20 pieces of vehicle-mounted data. After the distribution is successful, the feedback is sent to the message queue module 20. And sequentially distributing all the vehicle-mounted data in the message queue.
For example, vehicle management platform D needs vehicle-mounted data corresponding to the vehicle online condition, vehicle management platform E needs vehicle-mounted data corresponding to driving mileage, and vehicle management platform F needs vehicle-mounted data corresponding to vehicle abnormal data. The data distribution module 30 distributes the data to the corresponding vehicle management platform D, vehicle management platform E and vehicle management platform F according to the type of at least part of the vehicle-mounted data.
In the embodiment, vehicle-mounted data returned by at least one vehicle-mounted system is acquired; buffering the vehicle-mounted data in a message queue; the method comprises the steps of obtaining at least part of vehicle-mounted data from the front end of a message queue, and distributing the vehicle-mounted data to a corresponding vehicle management platform according to the type of the at least part of the vehicle-mounted data.
Referring to fig. 3, fig. 3 is a schematic flowchart of another embodiment of a distribution method of vehicle-mounted data provided by the present application. The method comprises the following steps:
Step 31: and acquiring vehicle-mounted data returned by at least one vehicle-mounted system.
Step 32: and packaging the vehicle-mounted data according to the preset field.
Wherein the preset field may be set in advance. For example, the preset field configuration may be performed in the configuration file in advance. Thus, the packaging requirements are preset in the configuration file.
In some embodiments, the in-vehicle data may be encapsulated by a context field, an event type field, a metadata field, a priority field, and a payload field.
The context field context can contain context information, and is very important for link tracking and cross-platform link tracking and troubleshooting. For example, the context field may be set to "fact { }".
The event type field event _ type and the path parameter topic have the same value, which is very important for subsequent distribution. For example, the event type field may be set to a string type.
The metadata field metadata is used for recording information conditions of some vehicle-mounted data and is filled in according to needs. The metadata field may be set to "dit".
The priority field priority is sample by default, and is not modified in general, which is important for what notification processing is adopted for subsequent distribution. The priority field may be set to "sample".
The payload field payload is used to house the body of the message. The payload field may be set to "dit".
Step 33: and buffering the packaged vehicle-mounted data in a message queue.
Step 34: and acquiring at least part of vehicle-mounted data from the front end of the message queue, and distributing the vehicle-mounted data to a corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data.
In step 34, a determination may be made further using the event type of the vehicle-mounted data to determine whether the vehicle-mounted data conforms to the target vehicle management platform. If the vehicle data are matched, the vehicle data are distributed to the corresponding vehicle management platform according to the type of at least part of the vehicle data.
In this embodiment, the vehicle-mounted data is encapsulated according to the preset fields, so that subsequent data distribution can be facilitated, the vehicle-mounted data is cached by using the message queue, and persistence of the vehicle-mounted data can be ensured.
Referring to fig. 4, fig. 4 is a schematic flow chart of another embodiment of the distribution method of the vehicle-mounted data provided by the present application. The method comprises the following steps:
Step 41: and acquiring vehicle-mounted data returned by at least one vehicle-mounted system.
Step 42: and packaging the vehicle-mounted data according to the event type field.
Step 43: and buffering the packaged vehicle-mounted data in a message queue.
Step 44: and determining whether the event type of the target vehicle-mounted data in at least part of the vehicle-mounted data is matched with a preset event type of the vehicle management platform.
If so, go to step 45, and if not, go to step 46.
Step 45: and carrying out data encapsulation on the target vehicle-mounted data again, and distributing the data to the corresponding vehicle management platform.
Since the data type of the vehicle-mounted data is a character string type in the message queue, data encapsulation needs to be performed again before distribution so as to encapsulate the data type required by the vehicle management platform.
In some embodiments, referring to fig. 5, step 45 may be the following flow:
step 451: and carrying out filtering operation on at least part of the packaged vehicle-mounted data.
In step 451, filtering is performed according to at least a portion of the type of the in-vehicle data. If the vehicle management platform needs the vehicle-mounted data of the online condition of the vehicle, other vehicle-mounted data are filtered, and the vehicle-mounted data of the online condition of the vehicle are reserved.
Step 452: and distributing at least part of the filtered vehicle-mounted data to the corresponding vehicle management platform.
In some embodiments, referring to fig. 6, step 452 may be the following flow:
step 61: and judging whether the data format of at least part of the vehicle-mounted data meets the requirement.
It can be understood that different data formats exist in different vehicle management platforms, and therefore, whether the data format of at least part of the vehicle-mounted data meets the requirement is judged.
If yes, the vehicle management platform is directly distributed, and if not, step 62 is executed.
Step 62: and converting the data format of at least part of the vehicle-mounted data into the data format of the vehicle management platform, and then distributing the data format to the vehicle management platform.
Step 46: and discarding the target vehicle-mounted data.
It is understood that discarding target vehicle-mounted data is not a distribution to one of the vehicle management platforms, but the target vehicle-mounted data may be distributed to the other vehicle management platforms.
In this embodiment, firstly, the vehicle-mounted data is encapsulated according to the event type field, so that subsequent data distribution can be conveniently matched according to the event type, the vehicle-mounted data of the corresponding vehicle management platform is preliminarily determined, secondly, the vehicle-mounted data is filtered, the requirement of the corresponding vehicle-mounted management platform on the data is met, and further, the vehicle-mounted data can be conveniently and smoothly issued to the vehicle management platform through data format conversion. Based on the above, the vehicle-mounted data are cached by using the message queue, the persistence of the vehicle-mounted data can be ensured, at least part of the vehicle-mounted data are distributed to the corresponding vehicle management platform, the data volume of the vehicle management platform for receiving the vehicle-mounted data can be reduced, and the processing efficiency of the vehicle management platform for the vehicle-mounted data is improved.
Referring to fig. 7, fig. 7 is a schematic flowchart of another embodiment of a distribution method of vehicle-mounted data provided by the present application. The method comprises the following steps:
step 71: and determining a publisher and a publisher state corresponding to the vehicle management platform.
Here, the publisher may be understood as a URL (Uniform resource Locator) of the vehicle management platform. Through the URL, the status of the corresponding vehicle management platform, i.e., the publisher status, can be determined.
For example, the publisher status is detected by way of a ping URL.
Step 72: and if the state of the publisher is in the activated state, at least part of the vehicle-mounted data is published to the vehicle management platform through the publisher.
If the publisher state is in the activated state, which indicates that the vehicle management platform is in normal communication, data can be published to the publisher state.
In some embodiments, upon successful publication of at least a portion of the in-vehicle data to the vehicle management platform, the publisher status is reset and feedback information is sent to the message queue.
It can be appreciated that resetting the publisher status upon successful publication facilitates real-time detection of the vehicle management platform status, i.e., the publisher status.
If the publisher state is in the inactive state last time but the publisher state is in the active state this time, the publisher state is reset when at least part of the vehicle data is successfully published to the vehicle management platform, so that the publisher state is in the active state.
In some embodiments, when at least part of the vehicle-mounted data fails to be published to the vehicle management platform, the number of continuous failures of a publisher is counted, and fusing processing is performed based on the number of continuous failures.
It can be understood that if the issuing is failed, it indicates that the current vehicle management platform is in the abnormal stage, and if the number of continuous failures exceeds the threshold value, it indicates that the time that the vehicle management platform is in the abnormal stage is longer, and the data cannot be issued to the vehicle management platform in a short period, the fusing processing is performed, and the data issuing to the vehicle management platform is stopped, so as to save system resources.
Wherein, a fusing time can be set, and the publisher state is determined again after the fusing time is reached.
In the embodiment, whether to distribute at least part of vehicle-mounted data to the vehicle management platform is determined according to the state of the publisher, so that system resources are saved, and the problems of repeated distribution and unsuccessful are avoided.
Referring to fig. 8, fig. 8 is a schematic flow chart of another embodiment of a distribution method of vehicle-mounted data provided by the present application. The method comprises the following steps:
step 81: and acquiring vehicle-mounted data returned by at least one vehicle-mounted system.
Step 82: and buffering the vehicle-mounted data in a message queue.
Step 83: and acquiring at least part of vehicle-mounted data from the front end of the message queue, and establishing a list of items to be processed according to the at least part of vehicle-mounted data.
Step 84: it is checked whether there is a list of pending entries for the consumer that needs to be restored.
When a consumer is normal, the consumer can distribute the data to the corresponding vehicle management platform according to the distribution mode in any embodiment.
If the current consumer dies, namely the process is interrupted, another process needs to be activated again, namely a consumer is newly built, and data distribution is continued.
In step 84, if it is checked that there is a list of pending entries for the consumer that needs to be restored, step 85 is performed. If it is checked that there is no pending entry list for the consumer that needs to be restored, step 86 is performed. If not, the consumer is normal.
Step 85: from the beginning of the list of pending entries.
The pattern of consumption in the list of pending entries is to start processing from scratch and to purge each entry once it is processed. Therefore, when the pending entry list needs to be restored, it needs to be consumed from the start position.
Step 86: consumed from an unconsumed location of the list of pending entries.
Step 87: and distributing the vehicle-mounted data to the corresponding vehicle management platform according to the type of at least part of the vehicle-mounted data.
In the embodiment, the consumer is monitored, when the consumer dies, a new consumer is established, and the new consumer is utilized to process the vehicle-mounted data in the item list to be processed, so that the processing efficiency of the vehicle-mounted data is improved.
Referring to fig. 9, fig. 9 is a schematic structural diagram of an embodiment of the vehicle-mounted data distribution system provided by the present application. The in-vehicle data distribution system 100 includes: a data interface module 10, a message queue module 20 and a data distribution module 30.
The data interface module 10 is configured to obtain vehicle-mounted data returned by at least one vehicle-mounted system.
In some embodiments, the data interface module 10 may have a plurality of sub data interfaces, each distributed hierarchically. Each subdata interface is used for obtaining vehicle-mounted data returned by a vehicle-mounted system.
In some embodiments, the data interface module 10 may obtain the vehicle data returned by at least one vehicle system according to a preset period.
In some embodiments, the data interface module 10 may receive the vehicle data transmitted back from at least one vehicle system in real time.
The vehicle-mounted data can include the online condition of the vehicle, the driving mileage, abnormal data of the vehicle, vehicle order information, state information of each piece of hardware of the vehicle, position information of the vehicle in running, historical data of the vehicle and the like.
The message queue module 20 is connected to the data interface module 10, and is configured to buffer the vehicle data with a message queue.
In some embodiments, the message queue in message queue module 20 can be a redis stream message queue. The stream message queue provides the functions of message persistence and main copied, can allow any client to access data at any moment, memorizes the access position of each client and can also ensure that the data is not lost. The writing speed is very fast, and the method is very suitable for being used as the middleware of the real-time distribution system.
In some embodiments, the message queue in the message queue module 20 may also be at least one of zeroMQ, RabbitMQ, ActiveMQ, and Kafka/Jafka.
The data distribution module 30 is connected to the message queue module 20, and is configured to obtain at least part of the vehicle-mounted data from the front end of the message queue, and distribute the vehicle-mounted data to a corresponding vehicle management platform according to the type of the at least part of the vehicle-mounted data.
In an application scenario, the following is explained with reference to fig. 10:
The data interface module 10 can obtain the vehicle data transmitted back by the vehicle system a, the vehicle system B and the vehicle system C in real time.
After acquiring the vehicle-mounted data returned by the vehicle-mounted system a, the vehicle-mounted system B, and the vehicle-mounted system C, the data interface module 10 sends the vehicle-mounted data to the message queue module 20.
The message queue module 20 buffers the in-vehicle data using a message queue.
After the message queue module 20 caches the vehicle-mounted data, the data distribution module 30 obtains at least part of the vehicle-mounted data from the front end of the message queue, and distributes the vehicle-mounted data to the corresponding vehicle management platform D, vehicle management platform E and vehicle management platform F according to the type of at least part of the vehicle-mounted data.
For example, there are 100 pieces of onboard data in the message queue. The data distribution module 30 obtains 20 pieces of vehicle-mounted data from the front end of the message queue, and distributes the 20 pieces of vehicle-mounted data to the corresponding vehicle management platform D, vehicle management platform E or vehicle management platform F according to the types of the 20 pieces of vehicle-mounted data. After the distribution is successful, the information is fed back to the message queue module 20. The message queue module 20 clears the 20 pieces of in-vehicle data. The data distribution module 30 acquires 20 pieces of vehicle-mounted data from the remaining 80 pieces of vehicle-mounted data in the message queue in sequence again, and distributes the 20 pieces of vehicle-mounted data to the corresponding vehicle management platform D, the corresponding vehicle management platform E and the corresponding vehicle management platform F according to the types of the 20 pieces of vehicle-mounted data. After the distribution is successful, the feedback is sent to the message queue module 20. And sequentially distributing all the vehicle-mounted data in the message queue.
For example, vehicle management platform D needs vehicle-mounted data corresponding to the vehicle online condition, vehicle management platform E needs vehicle-mounted data corresponding to driving mileage, and vehicle management platform F needs vehicle-mounted data corresponding to vehicle abnormal data. The data distribution module 30 distributes the data to the corresponding vehicle management platform D, vehicle management platform E and vehicle management platform F according to the type of at least part of the vehicle-mounted data.
In this embodiment, the in-vehicle data distribution system includes: the data interface module is used for acquiring vehicle-mounted data returned by at least one vehicle-mounted system; the message queue module is connected with the data interface module and used for caching the vehicle-mounted data by using the message queue; and the data distribution module is connected with the message queue module and used for acquiring at least part of vehicle-mounted data from the front end of the message queue and distributing the vehicle-mounted data to the corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data. Through the mode, the data interface module and the data distribution module are separated by the message queue module, on one hand, the message queue module provides a vehicle-mounted data caching function and can guarantee persistence of vehicle-mounted data, on the other hand, the separated data interface module and the separated data distribution module can avoid the condition that the vehicle-mounted data is lost due to failure of the data interface module in sending the vehicle-mounted data caused by restarting of logic change of the data distribution module, so that the safety of the vehicle-mounted data is guaranteed, the maintenance difficulty of a vehicle-mounted data distribution system is greatly reduced, on the other hand, the data are distributed to a corresponding vehicle management platform according to the type of at least part of the vehicle-mounted data, the data volume of the vehicle management platform for receiving the vehicle-mounted data can be reduced, and the processing efficiency of the vehicle management platform for the vehicle-mounted data is improved.
In some embodiments, the data interface module 10 is further configured to package the vehicle-mounted data according to preset configuration parameters; the message queue module 20 is further configured to buffer the packaged vehicle data by using a message queue.
In some embodiments, the parameters may be configured in a configuration file corresponding to the data interface module 10 in advance. For example, the data type corresponding to the data interface module 10, and the event type that the vehicle data needs to be encapsulated. Thus, the packaging requirements are preset in the configuration file. After receiving the vehicle-mounted data, the data interface module 10 encapsulates the vehicle-mounted data according to preset configuration parameters. And then buffering the packaged vehicle-mounted data in a message queue of a message queue module.
In an application scenario, with reference to fig. 11, a workflow of the data interface module 10 is described:
and the data source sends the data to the dispatcher-api service, and the dispatcher-api service encapsulates the data and writes the encapsulated data into a redis message queue. The dispatcher-api corresponds to the data interface module 10. The data corresponds to the above-mentioned vehicle-mounted data.
The dispatcher-api service acquires a corresponding config file in the nacos configuration, encapsulates the vehicle-mounted data according to configuration information in the config file, and then caches the encapsulated vehicle-mounted data in a redis message queue.
The configuration information in the config file may include context, event _ type, metadata, priority, and payload fields.
context: this field contains context information, which is very important for link tracking and cross-platform link tracking, troubleshooting issues.
event _ type: the event type is consistent with the value of the path parameter topic, and is very important for filtering the following dispatcher-server service pipeline.
metadata: the field records the information condition of some messages and fills in the messages according to the requirement.
priority: the priority field defaults to sample, and is generally not modified, which is important for the dispatcher-server service to employ.
payload: what is stored here is the message body.
In some embodiments, the configuration information used by the dispatcher-api service is obtained from the nacos service while monitoring the nacos configuration, and if the nacos configuration is manually updated, the dispatcher-api service synchronizes the configuration and dynamically updates the service.
In the embodiment, the vehicle-mounted data in different formats or types are unified by packaging the vehicle-mounted data, so that the subsequent distribution efficiency is improved conveniently.
In some embodiments, the data distribution module 30 is further configured to monitor the vehicle-mounted data of the message queue, and obtain at least part of the vehicle-mounted data from the front end of the message queue when the vehicle-mounted data is monitored.
In some embodiments, the data interface module 10 is further configured to encapsulate the vehicle data according to the event type field; the data distribution module 30 is further configured to determine whether an event type of target vehicle-mounted data in at least part of the vehicle-mounted data matches a preset event type of the vehicle management platform; if the matching is carried out, carrying out data encapsulation on the target vehicle-mounted data again, and distributing the data to the corresponding vehicle management platform; and if not, discarding the target vehicle-mounted data.
The data distribution module 30 is further configured to perform a filtering operation on at least part of the encapsulated vehicle-mounted data; and distributing at least part of the filtered vehicle-mounted data to the corresponding vehicle management platform.
The data distribution module 30 is further configured to determine whether a data format of at least part of the vehicle-mounted data meets a requirement; if not, the data format of at least part of the vehicle-mounted data is converted into the data format of the vehicle management platform and then distributed to the vehicle management platform.
In an application scenario, the following is explained with reference to fig. 12:
the method comprises the steps that a dispatcher-server service monitors a redis queue, reads data from the redis queue, then sends the data into a corresponding pipeline, filters the data through an event filter, packages the data after filtering, filters the data according to customized filtering conditions after packaging is completed, and selects publishers configured by users according with the conditions to publish the data. The dispatcher-server service corresponds to the data distribution module 30.
The publisher can be a management platform such as kafka, es, http, test and the like. The customized filtering condition can be determined according to the publisher, for example, data required by the management platform corresponding to the publisher, and if a vehicle operation log is required, the customized filtering condition is set as the filtering condition.
The dispatch-server service configuration problem is also that the configuration can be updated by acquiring from the nacos, monitoring the nacos configuration and performing hot update.
In some embodiments, the following is described in connection with FIG. 13:
the data distribution module 30 monitors the vehicle-mounted data in the message queue, when the vehicle-mounted data is monitored, the vehicle-mounted data encapsulated in the message queue is taken out in batch, the thread pool is used for processing the batch of vehicle-mounted data in parallel, the thread processing process is to analyze the message first, traverse all endpoints, judge whether event _ types are matched, select a corresponding priority function to process the vehicle-mounted data if the event _ types are matched, encapsulate the vehicle-mounted data, judge whether a filtering condition is met or not, directly discard the vehicle-mounted data if the filtering condition is not met, judge whether format conversion is needed if the filtering condition is met or not (different requirements are required for adapting to different vehicle-mounted management platforms for data formats), and directly release the vehicle-mounted data if the format conversion is needed.
In some embodiments, the publication flow is described in connection with FIG. 14:
the issuing process firstly judges whether the issuer is activated, only the activated issuer can issue the message, the state of the issuer is checked if the issuer is not activated, whether the fusing waiting time exceeds the dynamically set fusing duration is judged, if the fusing waiting time exceeds the dynamically set fusing duration, the issuer is activated, the fusing duration is reset, an exponential growth mode is adopted, but the upper limit is 5 minutes. And after the publisher sends the message, judging whether the publication is successful, if so, resetting the state of the publisher, otherwise, counting the failure times, and performing fusing processing when the failure times exceed 5 times.
Wherein the pipeline configuration uses a yaml file. The yaml file can define sources, sinks and transfers, wherein sources and sinks must be defined.
Each source must define name, meters and sinks, where meters defines the data information of the resource, for example, a sensor-source will filter out all data with topic as sensor, and send them to kafka through publisher of kafka _ sink. For another example, hardware-source requires filtering finer data, which can be defined in detail in filters, and the data source sink defines two publishers, which both require data format conversion, which can be defined in transfers. Wherein, a URL corresponding to the publisher is also required to be defined.
Filtering conditions are added according to needs, filtered data are sent out through the publisher, if the data formats required by the target platform are different, transfer can be defined according to needs, and by analogy, the vehicle monitoring platform, the hardware research and development platform, the positioning module, the sensing module and the PNC module can define the filtered data and corresponding format converters according to needs, and the distribution of the required data is completed.
In some embodiments, the data distribution module 30 is further configured to check whether there is a pending entry list of the consumer needing to be recovered, if so, consume from a starting position of the pending entry list, and if not, consume from an unconsumed position of the pending entry list, where the pending entry list corresponds to a portion of the vehicle-mounted data in the message queue.
In some embodiments, described in connection with fig. 15-17:
the redis driver developed by the system data distribution module 30 mainly has three threads, each of which is a thread for maintaining the heartbeat of a consumer, as shown in fig. 15; threads of data recovery, as shown in FIG. 16; the thread is consumed normally, as shown in FIG. 17.
In the normal consumption process, whether there is a dead (dead) consumer's PEL (Pending Entries List) that needs to be recovered is checked, if so, the consumption is started from the PEL, and if not, the consumption is started from the latest PEL position. And reading a batch of vehicle-mounted data from the PEL every time, wherein the batch size can be controlled through parameters, and after the batch of vehicle-mounted data is taken, distributing the vehicle-mounted data, wherein the distributing of the vehicle-mounted data adopts a thread pool and is executed concurrently, so that the consumption speed is accelerated. And the message distribution thread executes the execution callback function ack, confirms that the vehicle-mounted data is processed to the PEL, and removes the vehicle-mounted data from the list by the PEL.
If the consumer dead, the recovery process is followed, and PELs which are not processed by the consumer are distributed to other consumers for continuous consumption. If the dead consumer loses heartbeat timeout, the dead consumer can be cleaned up, and another dead consumer can be regenerated for data distribution.
Referring to fig. 18, fig. 18 is a schematic structural diagram of another embodiment of the vehicle-mounted data distribution system provided in the present application. The in-vehicle data distribution system 100 includes: a data interface module 10, a message queue module 20, a data distribution module 30, and a remote configuration module 40.
The remote configuration module 40 is used for performing remote system configuration on the data distribution system 100.
In some embodiments, remote configuration module 40 may be in the form of a web page. The user performs system configuration of the data distribution system 100 by logging in the web page. Therefore, a user does not need to directly operate the data distribution system 100, the influence on the data distribution system 100 is reduced, and the convenience of system configuration is improved. Wherein, the remote configuration module 40 may adopt a nacos configuration. And then monitoring the update of the nacos configuration, and remotely controlling the update of the service configuration and the like.
To sum up, any of the above embodiments provided by the application can solve the problem that multi-vehicle data source data is distributed to different platforms in a many-to-many relationship, and is sent in real time, transparent to users, supports various different types of service interfaces, can be remotely configured at will as required, takes effect immediately after configuration, is convenient and fast to expand, and the like.
The data distribution system 100 adopts a structure that the data interface module 10 and the data distribution module 30 are separated, the data interface module 10 can monitor multi-node arrangement of input/output flow information according to a message queue, and meanwhile, dynamic routing is adopted, path parameters are variable, different data sources can be identified according to the path parameters, and the maintenance is convenient. The data distribution module 30 can monitor the multi-node deployment of input/output flow information according to the message queue, and can frequently change according to the service requirement, and the buffer structure of the separated message queue adding module 20 can avoid the data loss caused by the data source data sending failure due to the change and restart service of the data distribution module 30, so that the data security is improved, and the platform maintenance difficulty is reduced.
In some embodiments, the data distribution system 100 may use a newly added stream message queue of redis v5.0 and above, which provides message persistence and main copied function, allows any client to access data at any time, and keeps track of the access location of each client, and also ensures that data is not lost. The writing speed is very fast, and the method is very suitable for being used as the middleware of the real-time distribution system.
Meanwhile, flow statistical information such as input and output is added to the data distribution system 100, and the data distribution system 100 is monitored in real time by combining Prometheus collection and Grafana visual display.
Referring to fig. 19, fig. 19 is a schematic structural diagram of an embodiment of a vehicle-mounted data distribution device provided in the present application. The distribution device 190 comprises a processor 191 and a memory 192 coupled to the processor 191; wherein the memory 192 is adapted to store a computer program and the processor 191 is adapted to execute the computer program to implement the following method:
acquiring vehicle-mounted data returned by at least one vehicle-mounted system; buffering the vehicle-mounted data in a message queue; and acquiring at least part of vehicle-mounted data from the front end of the message queue, and distributing the vehicle-mounted data to the corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data.
It will be appreciated that the processor 191 is also operative to execute a computer program to implement the method of any of the above embodiments.
Referring to fig. 20, fig. 20 is a schematic structural diagram of an embodiment of a computer-readable storage medium provided in the present application. The computer-readable storage medium 200 is for storing a computer program 201, the computer program 201, when being executed by a processor, is for implementing the method of:
acquiring vehicle-mounted data returned by at least one vehicle-mounted system; buffering the vehicle-mounted data in a message queue; and acquiring at least part of vehicle-mounted data from the front end of the message queue, and distributing the vehicle-mounted data to a corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data.
It will be appreciated that the computer program 201, when executed by a processor, is also for implementing the method of any of the embodiments described above.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other manners. For example, the above-described device embodiments are merely illustrative, and for example, the division of the circuits or units is only one type of logical function division, and other division manners may exist in actual implementation, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The above description is only an embodiment of the present application, and is not intended to limit the scope of the present application, and all equivalent structures or equivalent processes performed according to the contents of the specification and the drawings, or applied directly or indirectly to other related technical fields, are all included in the scope of the present application.
Claims (14)
1. A method for distributing vehicle-mounted data, the method comprising:
acquiring vehicle-mounted data returned by at least one vehicle-mounted system;
caching the vehicle-mounted data in a message queue;
and acquiring at least part of vehicle-mounted data from the front end of the message queue, and distributing the vehicle-mounted data to a corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data.
2. The method of claim 1, wherein prior to buffering the in-vehicle data in a message queue, the method comprises:
packaging the vehicle-mounted data according to a preset field;
the caching of the vehicle-mounted data in a message queue comprises the following steps:
and buffering the packaged vehicle-mounted data in the message queue.
3. The method according to claim 2, wherein the encapsulating the vehicle data according to the preset field comprises:
And encapsulating the vehicle-mounted data according to a context field, an event type field, a metadata field, a priority field and a payload field.
4. The method of claim 1, wherein the obtaining at least a portion of the vehicle data from the front end of the message queue comprises:
and monitoring the vehicle-mounted data of the message queue, and acquiring at least part of the vehicle-mounted data from the front end of the message queue when the vehicle-mounted data is monitored.
5. The method of claim 1, wherein prior to buffering the vehicle data in a message queue, comprising:
packaging the vehicle-mounted data according to the event type field;
the step of acquiring at least part of vehicle-mounted data from the front end of the message queue and distributing the vehicle-mounted data to the corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data comprises the following steps:
determining whether the event type of target vehicle-mounted data in the at least part of vehicle-mounted data is matched with a preset event type of the vehicle management platform;
if the matching is carried out, carrying out data packaging on the target vehicle-mounted data again, and distributing the data to the corresponding vehicle management platform;
And if not, discarding the target vehicle-mounted data.
6. The method according to claim 5, wherein the step of data packaging the target vehicle-mounted data again and distributing the target vehicle-mounted data to the corresponding vehicle management platform comprises the following steps:
filtering the at least part of the packaged vehicle-mounted data;
and distributing the at least part of the filtered vehicle-mounted data to the corresponding vehicle management platform.
7. The method of claim 6, wherein the distributing the at least partial filtered in-vehicle data to the corresponding vehicle management platform comprises:
judging whether the data format of the at least part of the vehicle-mounted data meets the requirement or not;
if not, the data format of at least part of the vehicle-mounted data is converted into the data format of the vehicle management platform, and then the data format is distributed to the vehicle management platform.
8. The method of claim 1, further comprising:
determining a publisher and a publisher state corresponding to the vehicle management platform;
and if the publisher state is in an activated state, publishing the at least part of the vehicle-mounted data to the vehicle management platform through the publisher.
9. The method of claim 8, further comprising:
and when at least part of the vehicle-mounted data is successfully published to the vehicle management platform, resetting the publisher state and sending feedback information to the message queue.
10. The method of claim 8, further comprising:
and when the at least part of vehicle-mounted data is failed to be published to the vehicle management platform, counting the continuous failure times of the publisher, and performing fusing processing based on the continuous failure times.
11. The method of claim 1, further comprising:
establishing a list of items to be processed according to at least part of the vehicle-mounted data;
checking whether a to-be-processed item list of the consumer needing to be recovered exists;
if yes, consuming from the starting position of the list of the items to be processed;
if not, consuming from the unconsumed location of the pending entry list.
12. An in-vehicle data distribution system characterized by comprising:
the data interface module is used for acquiring vehicle-mounted data returned by at least one vehicle-mounted system;
the message queue module is connected with the data interface module and used for caching the vehicle-mounted data by using a message queue;
And the data distribution module is connected with the message queue module and used for acquiring at least part of vehicle-mounted data from the front end of the message queue and distributing the vehicle-mounted data to the corresponding vehicle management platform according to the type of the at least part of vehicle-mounted data.
13. The distribution device of the vehicle-mounted data is characterized by comprising a processor and a memory coupled with the processor; wherein the memory is adapted to store a computer program and the processor is adapted to execute the computer program to implement the method according to any of claims 1-11.
14. A computer-readable storage medium, characterized in that the computer-readable storage medium is used to store a computer program which, when being executed by a processor, is used to carry out the method according to any one of claims 1-11.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210247970.6A CN114679417A (en) | 2022-03-14 | 2022-03-14 | Vehicle-mounted data distribution method, system and device and readable storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210247970.6A CN114679417A (en) | 2022-03-14 | 2022-03-14 | Vehicle-mounted data distribution method, system and device and readable storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
CN114679417A true CN114679417A (en) | 2022-06-28 |
Family
ID=82074353
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202210247970.6A Pending CN114679417A (en) | 2022-03-14 | 2022-03-14 | Vehicle-mounted data distribution method, system and device and readable storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114679417A (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110288107A (en) * | 2019-06-04 | 2019-09-27 | 北京汽车股份有限公司 | The method and system of more new trip, car-mounted terminal, mobile terminal and cloud platform |
CN111324815A (en) * | 2020-03-05 | 2020-06-23 | 奇瑞汽车股份有限公司 | Automobile information processing method and device and storage medium |
CN111723139A (en) * | 2020-06-15 | 2020-09-29 | 北京首汽智行科技有限公司 | Data reporting method |
CN111740953A (en) * | 2020-05-13 | 2020-10-02 | 南斗六星系统集成有限公司 | Data access forwarding method and system for vehicle supervision platform |
CN112199210A (en) * | 2020-09-21 | 2021-01-08 | 中国建设银行股份有限公司 | Data processing method and device based on Internet of things, computer equipment and medium |
-
2022
- 2022-03-14 CN CN202210247970.6A patent/CN114679417A/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110288107A (en) * | 2019-06-04 | 2019-09-27 | 北京汽车股份有限公司 | The method and system of more new trip, car-mounted terminal, mobile terminal and cloud platform |
CN111324815A (en) * | 2020-03-05 | 2020-06-23 | 奇瑞汽车股份有限公司 | Automobile information processing method and device and storage medium |
CN111740953A (en) * | 2020-05-13 | 2020-10-02 | 南斗六星系统集成有限公司 | Data access forwarding method and system for vehicle supervision platform |
CN111723139A (en) * | 2020-06-15 | 2020-09-29 | 北京首汽智行科技有限公司 | Data reporting method |
CN112199210A (en) * | 2020-09-21 | 2021-01-08 | 中国建设银行股份有限公司 | Data processing method and device based on Internet of things, computer equipment and medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN105357038B (en) | Monitor the method and system of cluster virtual machine | |
US9621441B2 (en) | Methods and computer program products for analysis of network traffic by port level and/or protocol level filtering in a network device | |
CN110399271B (en) | Log processing device, method, electronic device, and computer-readable storage medium | |
US10127092B1 (en) | Method and apparatus for monitoring a message transmission frequency in a robot operating system | |
JP6427260B2 (en) | Vehicle real-time travel data processing method and apparatus therefor | |
CN115640110B (en) | Distributed cloud computing system scheduling method and device | |
CN111970195A (en) | Data transmission method and streaming data transmission system | |
CN111694645B (en) | Task processing method and related device in distributed task scheduling system | |
CN113190524A (en) | Industrial big data acquisition method and system | |
CN117082102A (en) | Service-oriented architecture-based vehicle data processing method, device and equipment | |
CN114679417A (en) | Vehicle-mounted data distribution method, system and device and readable storage medium | |
US20190109886A1 (en) | Selected data exchange | |
CN115495500A (en) | Data processing method and device, electronic equipment and storage medium | |
CN105592143B (en) | A kind of file loading method and device | |
CN110032131A (en) | Electric vehicle state monitoring processing system and monitoring system based on Storm | |
CN114598944A (en) | Periodic signal processing system, method, computer device and storage medium | |
CN113873033A (en) | Intelligent edge computing gateway platform with fault-tolerant function | |
CN113254097A (en) | Configuration information issuing method and device, electronic equipment and storage medium | |
CN112230968A (en) | Firmware updating method, device, server and computer readable storage medium | |
CN116471298B (en) | Data acquisition method, data acquisition system based on distributed architecture and vehicle | |
CN115277675B (en) | Data stream processing method, device, electronic equipment and readable storage medium | |
CN112506735B (en) | Service quality monitoring method, system, server and storage medium | |
CN116010063A (en) | Interaction method and device of vehicle-mounted application program and electronic equipment | |
CN117119014A (en) | Method, device and equipment for processing communication data between domain controllers | |
KR101231933B1 (en) | System and method for managing error of electronic devices |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |