CN112187873A - Internet of vehicles data intelligent distribution method, device and system - Google Patents
Internet of vehicles data intelligent distribution method, device and system Download PDFInfo
- Publication number
- CN112187873A CN112187873A CN202010938400.2A CN202010938400A CN112187873A CN 112187873 A CN112187873 A CN 112187873A CN 202010938400 A CN202010938400 A CN 202010938400A CN 112187873 A CN112187873 A CN 112187873A
- Authority
- CN
- China
- Prior art keywords
- data
- event
- distribution
- configuration file
- internet
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Abstract
The invention provides an intelligent distribution method of Internet of vehicles data, which comprises the following steps: step S10, the Internet of vehicles cloud platform collects ECU data of various vehicle types, forms Internet of vehicles data and stores the Internet of vehicles data; step S11, extracting Internet of vehicles data from the Internet of vehicles cloud platform according to a preset sampling frequency or event type, and storing the Internet of vehicles data into a title data list; step S12, according to the type of the pre-generated configuration file, obtaining the Internet of vehicles data corresponding to the configuration file from the title; determining a corresponding data distribution type according to the configuration file and distributing the data distribution type to a data consumption end corresponding to the configuration file; step S13, checking that the data distribution is unsuccessful this time, and performing retransmission processing on the distributed data. The invention also provides a corresponding device and a corresponding system. The invention can flexibly configure the data to be distributed and has the advantages of high reliability, high availability and the like.
Description
Technical Field
The invention relates to the technical field of data distribution of Internet of vehicles, in particular to an intelligent data distribution method, device and system of the Internet of vehicles.
Background
With the development of the internet of vehicles and the standard requirements of new energy vehicles on the market, more and more vehicles are equipped with the internet of vehicles function. Based on the Internet of vehicles, the vehicle owner can realize the functions of positioning, remotely controlling the vehicle and the like, and even can access the Internet at the vehicle machine. The automobile factory can also collect signals of each ECU node of the automobile by defining a signal receiving module, and the currently collected signals with different frequencies reach hundreds. The signals can be used for constructing platforms such as whole vehicle working condition analysis, new energy national standard data forwarding, new energy platform monitoring, automatic driving system monitoring, remote fault diagnosis, driving behavior analysis and OTA (over the air) upgrading. Therefore, it is urgently needed to intelligently distribute data of various vehicle types to a plurality of consumption terminals, such as a plurality of automobile host plants, according to needs through an intelligent vehicle networking data distribution system.
In practical application, an automobile factory can collect various body ECU signals (such as EMS, BCS, ICM, BCM and the like) through the Internet of vehicles, and the body signals can be uploaded to the Internet of vehicles cloud platform according to a defined frequency as long as the vehicles are started or charged. In order to quickly meet the data requirements of various service departments of a consumer end, such as an automobile factory, the data distribution system is responsible for transmitting the received vehicle data to various sub-modules subscribing the vehicle data in real time through an internal protocol after the data organization and the data verification. In order to enable the system to have the characteristics of high reliability, high availability, elastic capacity expansion and the like, the system needs to adopt a scheme of micro-service framework development and multi-movable-node deployment, and meanwhile, flexible configuration of service demand parties (namely data consumers, including a plurality of automobile host plants and a plurality of enterprise client platforms), required automobile types and required data types is realized on the basis of configuration files.
However, the data distribution system in the prior art has some disadvantages, for example, it is impossible to intelligently distribute the car networking data of each vehicle type to a plurality of car host plants on demand in the same car networking platform; and the rapid data distribution to different business departments of an automobile factory cannot be realized.
Disclosure of Invention
The technical problem to be solved by the invention is to provide an intelligent data distribution method, device and system for the internet of vehicles, which can realize flexible configuration of data to be distributed, have high reliability and high availability, and can quickly meet the data distribution requirements of different data consumption ends (such as different automobile host factories and different business departments of the same automobile host factory).
In order to solve the technical problem, as an aspect of the present invention, an intelligent distribution method for data in internet of vehicles is provided, which includes the following steps:
step S10, the Internet of vehicles cloud platform collects ECU data of various vehicle types to form Internet of vehicles data, and the Internet of vehicles data is stored in a basic data module;
step S11, extracting corresponding Internet of vehicles data from the basic data storage module according to a preset sampling frequency or event type, and storing the Internet of vehicles data into a corresponding title data list;
step S12, according to the type of the pre-generated configuration file, obtaining the Internet of vehicles data corresponding to the configuration file from the stored title; determining a corresponding data distribution type according to the configuration file, and distributing the obtained Internet of vehicles data to a data consumption end corresponding to the configuration file, wherein the data consumption end comprises each automobile host factory and a client platform;
step S13, it is checked whether the data distribution is successful, and if not, the distributed data is retransmitted.
Wherein the step S12 further includes:
if the type of the configuration file is a periodic signal data distribution configuration file, analyzing the configuration file, determining a distribution object and an address, obtaining title data list data corresponding to the configuration file, and sending the title data list data to each data consumption end in a message pushing mode through the distribution address;
and if the type of the configuration file is an event signal data configuration file, analyzing the configuration file to obtain the title data list data corresponding to the configuration file, distributing the event data by calling a related event service interface, and distributing the title data list data to a data consumption end.
Wherein the step S13 further includes:
after the periodic signal data fails to be distributed, storing the data to be supplemented into a header data cache corresponding to a corresponding data consumption end; starting a timing task, regularly distributing the data to be supplemented in the title data cache to a data consumption end, and stopping the supplementing operation of the data to be supplemented after the number of times of the supplementing exceeds a preset supplementing number;
and after the event signal data fails to be distributed, storing the push message which is not successfully pushed into a database, starting a timing task, and regularly acquiring the push message which is not successfully pushed from the database and retransmitting the push message.
Wherein, the periodic signal data distribution configuration file comprises the following contents:
at least one set of data consumer content, each set of data consumer content comprising: the name of the data consumption end corresponding to each data consumption end, the kafka proxy address of the data consumption end, a title data list of basic data to be received and a vehicle series set.
Wherein, the event signal data configuration file comprises the following contents:
the system comprises event lists, a server and a server, wherein each event list comprises at least one event;
each event is configured with: event ID, event description, title data list to be pushed and event consumption group;
each event consumption group comprises at least one event consumption object; each event consumption object contains: describing the event type, the type of event push, and whether to push a mark; the event type comprises a kafka message or an http message; the types of event pushing comprise kafka-based message distribution mode pushing and http-based message distribution mode pushing; the push is carried with a network address and a push mode based on an http message distribution mode, wherein the push mode comprises the following steps: access to microservices and access to extranets.
Correspondingly, in another aspect of the present invention, an intelligent data distribution device for internet of vehicles is further provided, which includes:
the extraction unit is used for extracting corresponding Internet of vehicles data from the basic data storage module according to a preset sampling frequency or event type and storing the corresponding Internet of vehicles data into a corresponding title data list;
the distribution unit is used for obtaining the Internet of vehicles data corresponding to the configuration file from the stored title according to the type of the pre-generated configuration file; determining a corresponding data distribution type according to the configuration file, and distributing the obtained Internet of vehicles data to a data consumption end corresponding to the configuration file, wherein the data consumption end comprises each automobile host factory and a client platform;
and the distribution failure processing unit is used for checking whether the data distribution is successful or not, and carrying out retransmission processing on the distributed data when the data distribution is unsuccessful.
Wherein the distribution unit further comprises:
the periodic signal data distribution unit is used for analyzing the configuration file, determining a distribution object and an address when the type of the configuration file is a periodic signal data distribution configuration file, obtaining the title data list data corresponding to the configuration file, and sending the title data list data to each data consumption end in a message pushing mode through the distribution address;
and the event signal data distribution unit is used for analyzing the configuration file to obtain the title data list data corresponding to the configuration file when the type of the configuration file is the event signal data configuration file, distributing the event data by calling a related event service interface and distributing the title data list data to a data consumption end.
Wherein the distribution failure processing unit further includes:
a periodic signal data distribution failure processing unit, comprising:
the cache unit is used for storing the data to be supplemented into the title data cache corresponding to the corresponding data consumption end after the periodic signal data fails to be distributed;
the timing reissue unit is used for starting a timing task and distributing data to be reissued in the title data cache to a data consumption end at regular time;
the device comprises a hair compensation stopping unit, a hair compensation stopping unit and a hair compensation stopping unit, wherein the hair compensation stopping unit is used for stopping the hair compensation operation of the data to be compensated after the preset hair compensation times are exceeded;
an event signal data distribution failure processing unit including:
the temporary storage unit is used for storing the push message which is not successfully pushed into the database after the event signal data fails to be distributed;
and the timing retransmission unit is used for starting a timing task, and acquiring the push message which is not successfully pushed from the database at regular time and retransmitting the push message.
Wherein, the periodic signal data distribution configuration file comprises the following contents:
at least one set of data consumer content, each set of data consumer content comprising: the name of the data consumption end corresponding to each data consumption end, the kafka proxy address of the data consumption end, a title data list of basic data to be received and a vehicle series set.
Wherein, the event signal data configuration file comprises the following contents:
the system comprises event lists, a server and a server, wherein each event list comprises at least one event;
each event is configured with: event ID, event description, title data list to be pushed and event consumption group;
each event consumption group comprises at least one event consumption object; each event consumption object contains: describing the event type, the type of event push, and whether to push a mark; the event type comprises a kafka message or an http message; the types of event pushing comprise kafka-based message distribution mode pushing and http-based message distribution mode pushing; the push is carried with a network address and a push mode based on an http message distribution mode, wherein the push mode comprises the following steps: access to microservices and access to extranets.
Correspondingly, in still another aspect of the present invention, there is provided an intelligent data distribution system for internet of vehicles, including:
the vehicle networking cloud platform is used for collecting ECU data of various vehicle types, forming vehicle networking data and storing the vehicle networking data in the basic data module; and
the intelligent data distribution device for the Internet of vehicles.
The embodiment of the invention has the following beneficial effects:
according to the method, the device and the system for intelligently distributing the data of the internet of vehicles, provided by the invention, the data of each vehicle type can be intelligently distributed to a plurality of data consumption ends (such as a plurality of automobile host plants) as required through the intelligent distribution device of the data of the internet of vehicles by setting the configuration file;
in the invention, the data distribution system supports two different data distribution modes of periodic signal data forwarding and event signal data forwarding; two data distribution network approaches of kafka and http are supported simultaneously; therefore, the flexible configuration of the data consumption end, the required vehicle type and the required data type can be realized based on the configuration file;
in addition, the invention is provided with an active push data retry strategy, thereby further improving the flexibility and the safety of the application.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is within the scope of the present invention for those skilled in the art to obtain other drawings based on the drawings without inventive exercise.
Fig. 1 is a main flow diagram of an embodiment of an intelligent multi-consumer-end-oriented data distribution method in an internet of vehicles according to the present invention;
FIG. 2 is a schematic diagram of the data format of the periodic signal acquisition referred to in FIG. 1;
FIG. 3 is a data format schematic of the event signal acquisition referred to in FIG. 1;
FIG. 4 is a schematic illustration of a profile for the distribution of periodic signal data referred to in FIG. 1;
FIG. 5 is a profile diagram of the event signal data distribution referred to in FIG. 1;
FIG. 6 is a schematic structural diagram of an embodiment of a multi-consumer-end-oriented intelligent data distribution system in the Internet of vehicles according to the present invention;
FIG. 7 is a schematic diagram of the dispensing unit of FIG. 6;
FIG. 8 is a schematic diagram of the dispatch failure handling unit of FIG. 6;
fig. 9 is a schematic structural diagram of the periodic signal data distribution failure processing unit in fig. 8;
fig. 10 is a schematic structural diagram of the event signal data distribution failure processing unit in fig. 8.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings.
As shown in fig. 1, a main flow diagram of an embodiment of a multi-consumer-end-oriented intelligent distribution method of internet of vehicles data is shown. Referring to fig. 2 to 5 together, in the present embodiment, the method includes the following steps:
step S10, the Internet of vehicles cloud platform collects ECU data of various vehicle types to form Internet of vehicles data, and the Internet of vehicles data is stored in a basic data module (kafka); specifically, various body ECU signals (such as EMS, BCS, ICM, BCM and the like) can be collected through the Internet of vehicles, and the body signals can be uploaded to the Internet of vehicles cloud platform according to a predefined frequency as long as the vehicles are started or charged;
step S11, extracting corresponding Internet of vehicles data from the basic data storage module according to a preset sampling frequency or event type, and storing the corresponding Internet of vehicles data into a corresponding title data list (topic);
two data format examples of the collected internet of vehicles data are respectively shown in fig. 2 and fig. 3; fig. 2 corresponds to a preset sampling frequency, wherein a sampling frequency (tbox _ period) for collecting to the t _ box device is shown, and examples of the sampling frequency show 1s, 5s, 30s, 60s and the like; the sampling time (sampleTime), the vehicle serial number (vehicleSeries), the vehicle model number (vehicleModelCode), the sampling vehicle (vin), and the data related to each ECU (such as the corresponding related parameters of BCM, BCS, BMS, etc.) are further recorded therein, which can be seen in detail in fig. 2;
similarly, the data format corresponding to the event signal acquisition in fig. 3 shows the event type (msgType), the sampling time (sampleTime), the vehicle serial number (vehicleSeries), the vehicle model number (vehicleModelCode), the sampling vehicle (vin), and the data related to each ECU (e.g., related parameters corresponding to BCM, BCS, BMS, etc.), as detailed in fig. 3;
these collected data are each stored in a corresponding title data list (topic).
Step S12, according to the type of the pre-generated configuration file, obtaining the Internet of vehicles data corresponding to the configuration file from the stored title; determining a corresponding data distribution type according to the configuration file, and distributing the obtained Internet of vehicles data to a data consumption end corresponding to the configuration file, wherein the data consumption end comprises each automobile host factory and a client platform;
specifically, the step S12 further includes:
if the type of the configuration file is a periodic signal data distribution configuration file, analyzing the configuration file, determining a distribution object and an address, obtaining title data list data corresponding to the configuration file, and sending the title data list data to each data consumption end in a message pushing mode through the distribution address;
and if the type of the configuration file is an event signal data configuration file, analyzing the configuration file to obtain the title data list data corresponding to the configuration file, distributing the event data by calling a related event service interface, and distributing the title data list data to a data consumption end.
More specifically, as shown in fig. 4 and 5, examples of a periodic signal data distribution profile and an event signal data profile are shown, respectively; wherein:
as shown in fig. 4, the periodic signal data distribution profile includes the following contents:
at least one set of data consumer content (factorary), each set of data consumer content comprising: the name of the data consumption end corresponding to each data consumption end, the Kafka proxy address of the data consumption end, a title data list of basic data to be received and a vehicle series set. In fig. 4, one of the data consumers is "guangxin" and "boststrapserver" is the kafka proxy address of the car manufacturer, which is in the form of a comma separated list of host and port pairs; "topics" is a topic list of basic data to be received, and specific contents can be seen in fig. 2; and the vehicle series set corresponding to the sendKeys. If a newly added truck factory distributes, only a new addition is needed below the "guangxin", and another data consuming terminal "mic-closed" is shown in fig. 4, and the specific content of the data consuming terminal is similar to that of the "guangxin".
As shown in fig. 5, the event signal data configuration file includes the following contents:
the system comprises event lists (eventlists), wherein each event list comprises at least one event (event), and the number of the events is configured according to needs;
each event is configured with:
event ID (eventid), and existing event ID cannot be duplicated;
an event description (descriptor), which is specific description information of an event;
a list of title data to be pushed (topic);
event consumption groups (consumers);
each event consumption group contains at least one event consumption object (consumer); each event consumption object contains:
event consumption object id (consumerid);
an event type description (descriptor), wherein the event type comprises kafka messages or http messages; for example, "1 represents Kafka message" or "0 represents http message";
the type (type) of event pushing, wherein the type of event pushing comprises pushing based on kafka message distribution mode and pushing based on http message distribution mode; for example: 1 denotes push based on kafka message distribution mode; 0 represents push based on http message distribution mode;
the push is carried with a network address and a push mode based on an http message distribution mode, wherein the push mode comprises the following steps: accessing micro-services and accessing an extranet; wherein, the flage is 0 for accessing the micro service, and the flage is 1 for accessing the external network;
whether to push a mark (keys) is a mark for whether to push the consumer, and when a keys field in the monitored message is contained in the keys of the consumer, the corresponding message is pushed.
It can be seen from the above that the data distribution system of the present invention supports two different data distribution modes, namely, periodic signal data distribution and event signal data distribution, and can implement flexible configuration of a service demand party (i.e., a data consumption end), a required vehicle type and a required data type based on a configuration file.
Step S13, it is checked whether the data distribution is successful, and if not, the distributed data is retransmitted.
Wherein the step S13 further includes:
after the periodic signal data fails to be distributed, storing the data to be supplemented into a header data cache corresponding to a corresponding data consumption end; starting a timing task, regularly distributing the data to be supplemented in the title data cache to a data consumption end, and stopping the supplementing operation of the data to be supplemented after the number of times of the supplementing exceeds a preset supplementing number; for example, in some examples, if a certain type of data, such as tbox _ period _1s, fails to be sent, then the present dispatch of the instance is cancelled, the next time a timed task is initiated, the dispatch is attempted, and the next time a timed task is initiated, the dispatch continues for multiple days or until the store reaches a certain limit and is not reissued;
and after the event signal data fails to be distributed, storing the push message which is not successfully pushed into a database, starting a timing task, and regularly acquiring the push message which is not successfully pushed from the database and retransmitting the push message.
As shown in fig. 6, a schematic structural diagram of an embodiment of the multi-consumer-end-oriented intelligent data distribution system in the internet of vehicles according to the present invention is shown; referring to fig. 7 to 10 together, in the present embodiment, the system includes:
the vehicle networking cloud platform 2 is used for collecting ECU data of various vehicle types, forming vehicle networking data and storing the vehicle networking data in a basic data module (kafka); and
the multi-consumer-end-oriented intelligent car networking data distribution device 1 is used for obtaining corresponding car networking data from basic data modules of the car networking cloud platform 2 according to configuration files and distributing the car networking data to different data consumer ends 3, wherein the data consumer ends 3 can be different car host factories or different departments of the car host factories and other consumer ends.
Specifically, the car networking cloud platform 2 includes:
the ECU data collection module 20 is configured to collect various body ECU signals (such as EMS, BCS, ICM, BCM, and the like) through the internet of vehicles, and in some embodiments, the body signals may be uploaded to the internet of vehicles cloud platform according to a predefined frequency whenever the vehicle is started or charging;
a basic data module 21 for storing the body ECU signals collected by the ECU data collection module 20.
More specifically, the intelligent distribution device 1 for vehicle networking data for multiple consumers comprises:
the extracting unit 10 is configured to extract corresponding internet-of-vehicles data from the basic data storage module according to a preset sampling frequency or an event type, and store the corresponding internet-of-vehicles data in a corresponding title data list;
the distribution unit 11 is used for obtaining the Internet of vehicles data corresponding to the configuration file from the stored title according to the type of the configuration file generated in advance; determining a corresponding data distribution type according to the configuration file, and distributing the obtained Internet of vehicles data to a data consumption end corresponding to the configuration file, wherein the data consumption end comprises each automobile host factory and each enterprise end client platform;
the distribution failure processing unit 12 checks whether the data distribution is successful or not, and if not, performs retransmission processing on the distributed data.
Specifically, in some examples, the dispensing unit 11 further includes:
the periodic signal data distribution unit 110 is configured to, when the type of the configuration file is a periodic signal data distribution configuration file, parse the configuration file, determine a distribution object and an address, obtain title data list data corresponding to the configuration file, and send the title data list data to each data consuming end in a message push manner through a distribution address;
and the event signal data distribution unit 111 is configured to, when the type of the configuration file is an event signal data configuration file, parse the configuration file to obtain header data list data corresponding to the configuration file, perform event data distribution by calling a relevant event service interface, and distribute the header data list data to a data consuming end.
Specifically, in some examples, the distribution failure processing unit 12 further includes:
the periodic signal data distribution failure processing unit 120 includes:
the cache unit 122 is configured to store, after the periodic signal data fails to be distributed, data to be reissued into a header data cache corresponding to a corresponding data consuming end;
the timing reissue unit 123 is configured to start a timing task, and periodically distribute the data to be reissued in the header data cache to the data consuming end;
a complementary sending stopping unit 124, configured to stop the complementary sending operation on the data to be complementary sent after a predetermined number of complementary sending times is exceeded;
the event signal data distribution failure processing unit 121 includes:
the temporary storage unit 125 is configured to store the push message that is not successfully pushed into the database after the event signal data fails to be distributed;
and a timing retransmission unit 126, configured to start a timing task, and periodically obtain the unsuccessfully pushed message from the database and retransmit the unsuccessfully pushed message.
Specifically, in some examples, the periodic signal data distribution profile includes the following:
at least one set of data consumer content, each set of data consumer content comprising: the name of the data consumption end corresponding to each data consumption end, the Kafka proxy address of the data consumption end, a title data list of basic data to be received and a vehicle series set.
Wherein, the event signal data configuration file comprises the following contents:
the system comprises event lists, a server and a server, wherein each event list comprises at least one event;
each event is configured with: event ID, event description, title data list to be pushed and event consumption group;
each event consumption group comprises at least one event consumption object; each event consumption object contains: describing the event type, the type of event push, and whether to push a mark; the event type comprises a kafka message or an http message; the types of event pushing comprise kafka-based message distribution mode pushing and http-based message distribution mode pushing; the push is carried with a network address and a push mode based on an http message distribution mode, wherein the push mode comprises the following steps: access to microservices and access to extranets.
In some embodiments of the invention, the background running program of the multi-consumer-side internet-of-vehicle data intelligent distribution device 1 adopts the SpringBoot Java application, service release and operation and maintenance management are performed based on the flight TSF standard operation flow, and the running load condition of the system can be monitored in real time to dynamically expand capacity as required (up to minute-level capacity expansion capacity) so as to meet the continuously increasing data demand of customers, so that the system is a typical cloud computing and micro service implementation mechanism, and has the advantages of high availability, high reliability and flexible capacity expansion.
The embodiment of the invention has the following beneficial effects:
according to the method, the device and the system for intelligently distributing the data of the internet of vehicles facing to the multiple consumption ends, the data of each vehicle type can be intelligently distributed to the multiple data consumption ends (such as multiple automobile host factories) as required through the intelligent distribution device of the data of the internet of vehicles by setting the configuration file;
in the invention, the data distribution system supports two different data distribution modes of periodic signal data forwarding and event signal data forwarding; two data distribution network approaches of kafka and http are supported simultaneously; therefore, the flexible configuration of the data consumption end, the required vehicle type and the required data type can be realized based on the configuration file;
in addition, the invention is provided with an active push data retry strategy, thereby further improving the flexibility and the safety of the application.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (11)
1. The method for intelligently distributing the data in the Internet of vehicles is characterized by comprising the following steps of:
step S10, the Internet of vehicles cloud platform collects ECU data of various vehicle types to form Internet of vehicles data, and stores the Internet of vehicles data in a basic data module;
step S11, extracting corresponding Internet of vehicles data from the basic data storage module according to a preset sampling frequency or event type, and storing the Internet of vehicles data into a corresponding title data list;
step S12, according to the type of the pre-generated configuration file, obtaining the Internet of vehicles data corresponding to the configuration file from the stored title; determining a corresponding data distribution type according to the configuration file, and distributing the obtained Internet of vehicles data to a data consumption end corresponding to the configuration file;
step S13, it is checked whether the data distribution is successful, and if not, the distributed data is retransmitted.
2. The method of claim 1, wherein the step S12 further comprises:
if the type of the configuration file is a periodic signal data distribution configuration file, analyzing the configuration file, determining a distribution object and an address, obtaining title data list data corresponding to the configuration file, and sending the title data list data to each data consumption end in a message pushing mode through the distribution address;
and if the type of the configuration file is an event signal data configuration file, analyzing the configuration file to obtain the title data list data corresponding to the configuration file, distributing the event data by calling a related event service interface, and distributing the title data list data to a data consumption end.
3. The method of claim 2, wherein the step S13 further comprises:
after the periodic signal data fails to be distributed, storing the data to be supplemented into a header data cache corresponding to a corresponding data consumption end; starting a timing task, regularly distributing the data to be supplemented in the title data cache to a data consumption end, and stopping the supplementing operation of the data to be supplemented after the number of times of the supplementing exceeds a preset supplementing number;
and after the event signal data fails to be distributed, storing the push message which is not successfully pushed into a database, starting a timing task, and regularly acquiring the push message which is not successfully pushed from the database and retransmitting the push message.
4. A method according to any one of claims 1 to 3, wherein the periodic signal data distribution profile comprises the following:
at least one set of data consumer content, each set of data consumer content comprising: the name of the data consumption end corresponding to each data consumption end, the kafka proxy address of the data consumption end, a title data list of basic data to be received and a vehicle series set.
5. A method according to any one of claims 1 to 3, wherein the event signal data profile includes the following:
the system comprises event lists, a server and a server, wherein each event list comprises at least one event;
each event is configured with: event ID, event description, title data list to be pushed and event consumption group;
each event consumption group comprises at least one event consumption object; each event consumption object contains: describing the event type, the type of event push, and whether to push a mark; the event type comprises a kafka message or an http message; the types of event pushing comprise kafka-based message distribution mode pushing and http-based message distribution mode pushing; the push is carried with a network address and a push mode based on an http message distribution mode, wherein the push mode comprises the following steps: access to microservices and access to extranets.
6. The utility model provides a car networking data intelligence dispensing device which characterized in that includes:
the extraction unit is used for extracting corresponding Internet of vehicles data from the basic data storage module according to a preset sampling frequency or event type and storing the corresponding Internet of vehicles data into a corresponding title data list;
the distribution unit is used for obtaining the Internet of vehicles data corresponding to the configuration file from the stored title according to the type of the pre-generated configuration file; determining a corresponding data distribution type according to the configuration file, and distributing the obtained Internet of vehicles data to a data consumption end corresponding to the configuration file;
and the distribution failure processing unit is used for checking whether the data distribution is successful or not, and carrying out retransmission processing on the distributed data when the data distribution is unsuccessful.
7. The apparatus of claim 6, wherein the distribution unit further comprises:
the periodic signal data distribution unit is used for analyzing the configuration file, determining a distribution object and an address when the type of the configuration file is a periodic signal data distribution configuration file, obtaining the title data list data corresponding to the configuration file, and sending the title data list data to each data consumption end in a message pushing mode through the distribution address;
and the event signal data distribution unit is used for analyzing the configuration file to obtain the title data list data corresponding to the configuration file when the type of the configuration file is the event signal data configuration file, distributing the event data by calling a related event service interface and distributing the title data list data to a data consumption end.
8. The apparatus of claim 7, wherein the distribution failure processing unit further comprises:
a periodic signal data distribution failure processing unit, comprising:
the cache unit is used for storing the data to be supplemented into the title data cache corresponding to the corresponding data consumption end after the periodic signal data fails to be distributed;
the timing reissue unit is used for starting a timing task and distributing data to be reissued in the title data cache to a data consumption end at regular time;
the device comprises a hair compensation stopping unit, a hair compensation stopping unit and a hair compensation stopping unit, wherein the hair compensation stopping unit is used for stopping the hair compensation operation of the data to be compensated after the preset hair compensation times are exceeded;
an event signal data distribution failure processing unit including:
the temporary storage unit is used for storing the push message which is not successfully pushed into the database after the event signal data fails to be distributed;
and the timing retransmission unit is used for starting a timing task, and acquiring the push message which is not successfully pushed from the database at regular time and retransmitting the push message.
9. The apparatus of any of claims 6 to 8, wherein the periodic signal data distribution profile comprises:
at least one set of data consumer content, each set of data consumer content comprising: the name of the data consumption end corresponding to each data consumption end, the kafka proxy address of the data consumption end, a title data list of basic data to be received and a vehicle series set.
10. An apparatus according to any one of claims 6 to 8, wherein the event signal data profile includes the following:
the system comprises event lists, a server and a server, wherein each event list comprises at least one event;
each event is configured with: event ID, event description, title data list to be pushed and event consumption group;
each event consumption group comprises at least one event consumption object; each event consumption object contains: describing the event type, the type of event push, and whether to push a mark; the event type comprises a kafka message or an http message; the types of event pushing comprise kafka-based message distribution mode pushing and http-based message distribution mode pushing; the push is carried with a network address and a push mode based on an http message distribution mode, wherein the push mode comprises the following steps: access to microservices and access to extranets.
11. The utility model provides a car networking data intelligence distribution system which characterized in that includes:
the vehicle networking cloud platform is used for collecting ECU data of various vehicle types, forming vehicle networking data and storing the vehicle networking data in the basic data module; and
the intelligent distribution device of the vehicle networking data as claimed in any one of claims 6-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010938400.2A CN112187873B (en) | 2020-09-09 | 2020-09-09 | Intelligent distribution method, device and system for Internet of vehicles data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010938400.2A CN112187873B (en) | 2020-09-09 | 2020-09-09 | Intelligent distribution method, device and system for Internet of vehicles data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112187873A true CN112187873A (en) | 2021-01-05 |
| CN112187873B CN112187873B (en) | 2023-08-08 |
Family
ID=73920073
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010938400.2A Active CN112187873B (en) | 2020-09-09 | 2020-09-09 | Intelligent distribution method, device and system for Internet of vehicles data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112187873B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113792016A (en) * | 2021-09-15 | 2021-12-14 | 阿波罗智联(北京)科技有限公司 | Method, device, equipment and medium for extracting driving data |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017067230A1 (en) * | 2015-10-21 | 2017-04-27 | 中兴通讯股份有限公司 | Software function expansion method and apparatus based on micro service architecture |
| CN110430277A (en) * | 2019-08-13 | 2019-11-08 | 山东浪潮人工智能研究院有限公司 | It is a kind of based on cloud computing, big data, the car networking application system of technology of Internet of things |
-
2020
- 2020-09-09 CN CN202010938400.2A patent/CN112187873B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017067230A1 (en) * | 2015-10-21 | 2017-04-27 | 中兴通讯股份有限公司 | Software function expansion method and apparatus based on micro service architecture |
| CN110430277A (en) * | 2019-08-13 | 2019-11-08 | 山东浪潮人工智能研究院有限公司 | It is a kind of based on cloud computing, big data, the car networking application system of technology of Internet of things |
Non-Patent Citations (1)
| Title |
|---|
| 李连杰: "基于微服务的车联网车辆数据采集与分发系统", 《中国优秀硕士论文全文数据库 工程科技Ⅱ辑》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113792016A (en) * | 2021-09-15 | 2021-12-14 | 阿波罗智联(北京)科技有限公司 | Method, device, equipment and medium for extracting driving data |
| CN113792016B (en) * | 2021-09-15 | 2024-04-26 | 阿波罗智联(北京)科技有限公司 | Method, device, equipment and medium for extracting driving data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112187873B (en) | 2023-08-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103781100B (en) | The policy control method and device of terminal peripheral hardware | |
| CN113452486B (en) | Vehicle information uploading method, device, equipment and storage medium | |
| CN101502144A (en) | Element management system in wireless communication network | |
| CN103795580A (en) | Data monitoring method, system and related equipment | |
| CN102591991A (en) | Train data acquisition and management method and train data acquisition and management system | |
| CN103986608A (en) | J2EE application virtualization management method based on Itanium Linux application containers | |
| CN111159031B (en) | Method for automatically testing application mobile terminal, computer device and computer readable storage medium | |
| CN109547240B (en) | Intelligent device based on edge calculation and access and device analysis method | |
| CN102196373A (en) | Short message alarm system and short message alarm method | |
| US20120191665A1 (en) | Integrated Distribution Management System Channel Adapter | |
| CN111897718A (en) | Vehicle machine automatic test method based on big data and storage medium | |
| CN111890933A (en) | Battery management method and system for vehicle, vehicle and server | |
| CN111131082A (en) | Charging facility data transmission dynamic control method and system | |
| CN109189427A (en) | Using update method, device, system and storage medium | |
| CN111127250B (en) | Power data monitoring event analysis system and method | |
| CN110011843A (en) | Alarm information processing method, electronic equipment and storage medium | |
| CN112187873A (en) | Internet of vehicles data intelligent distribution method, device and system | |
| CN109495546B (en) | Data processing method, system and server | |
| CN113162942A (en) | Method for forwarding self-adaptive protocol | |
| CN210804735U (en) | Intelligent electric meter | |
| CN112140936A (en) | Charging monitoring method, system and storage medium | |
| CN116155720A (en) | CAN data acquisition remote configuration method in T-BOX | |
| CN114422386B (en) | Monitoring method and device for micro-service gateway | |
| CN113965447B (en) | Online cloud diagnosis method, device, system, equipment and storage medium | |
| CN116010388A (en) | Data verification method, data acquisition server and data verification system |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |