A data standard design method and design system for Internet of Vehicles data

Abstract

The present application discloses a data standard design method and design system for vehicle networking data, relating to the technical field of automotive data processing. The method includes comparing the vehicle type data of multiple instance vehicle types with the vehicle type data of a basic vehicle type respectively to obtain configuration changes; acquiring the operating conditions of each instance vehicle type and the vehicle networking data standard under the corresponding operating conditions; and updating the basic data standard of the basic vehicle type, where the update includes adding sub-standard items to the data standard items in the basic data standard that are associated with the configuration changes and / or operating conditions, and the sub-standard items define the vehicle networking data standard of the corresponding operating data under a single configuration and a single operating condition. The present application can add sub-standard items to the data standard items in the basic data standard that are associated with the configuration changes and / or operating conditions, thereby increasing the data standards for vehicle networking data affected by the configuration changes and / or operating conditions, so as to achieve data constraint and data verification.

Description

Technical Field

[0001] This application relates to the technical field of automotive data processing, and specifically relates to a data standard design method and design system for vehicle networking data. Background Art

[0002] As the automotive industry pays more and more attention to issues such as automotive safety and intelligence, it has greatly promoted the development of new technologies. More and more electronic technologies are applied to automobiles, such as the application of controllers, a large number of sensors, network devices, etc. on automobiles, which has greatly improved the safety, comfort, intelligence and other performances of automobiles, and improved the overall performance and level of automobiles. In particular, the trend of automotive intelligence and networking is particularly significant, from which a vehicle networking system is derived.

[0003] A vehicle networking system refers to a system that can collect, store and transmit all working conditions inside and outside the vehicle through in-vehicle terminal devices installed on the vehicle instrument panel, so as to realize real-time information interaction between vehicles and between vehicles and roadside infrastructure, inform each other of the current state, and obtain the current road environment information, so as to realize collaborative perception of road dangerous situations, timely provide various collision warning information, and prevent the occurrence of road traffic safety accidents. The in-vehicle terminal device is an important part of the vehicle networking system and is responsible for collecting vehicle networking data. Among them, vehicle networking data specifically refers to data information such as vehicle running status and fuel consumption status collected by using an in-vehicle data acquisition system such as an image acquisition system and sensors; the processing of the collected data mainly relies on a background data processing system. This part of the data that changes during the operation of the vehicle collected by the vehicle networking system is dynamic data. In practical applications, in addition to being able to collect this part of dynamic data, the vehicle networking system can also collect static data. Static data refers to data that has been determined and unchanged during the vehicle design process. For example, the engines adopted by different vehicle models are determined during vehicle design, so the engine data of different vehicle models belongs to static data. Dynamic data is based on static data, and different static data leads to different dynamic data.

[0004] In order to standardize and unify the data formats and definitions of intelligent connected vehicles after collection and processing, solve the problem of data silos in the field of intelligent connected vehicles, realize the interaction and sharing of desensitized data, provide a basic guarantee for the circulation of data elements and the release of data value, ensure that intelligent connected vehicle data generates more application value, and promote the formation of an industrial data ecosystem for intelligent connected vehicles, there have emerged basic data standards for vehicle networking data based on national standards, industry standards, and enterprise standards, such as "Data Formats and Definitions for Intelligent Connected Vehicles". Each data standard item in the basic data standard corresponds to an operating data in vehicle networking data, and the data standard type defines the basic format of the corresponding vehicle networking data. For example, it includes: a) Field Name: Data Name Information; b) English Field Name: English expression of the data name information; c) Definition Description: Specific definition of the field; d) Data Type: In this specification, the attribute values are divided into two data types, string and number, used to describe and distinguish different data types; e) Description and Requirements: Specific content description and format definition requirements for this field; f) Unit: Measurement unit of the data; g) Valid Range: Number of digits and value boundaries of the data. The valid range is also the value range, which can be used to constrain the data value range of vehicle networking data; h) Data Security Level: Classify the data according to the risk situations in domestic data interaction and outbound activities.

[0005] Existing basic data standards cannot cover the vehicle networking data of more and more vehicle models under different working conditions, and cannot define and verify the vehicle networking data generated by different vehicle configurations under different working conditions. Summary of the Invention

[0006] Aiming at the defects existing in the prior art, the purpose of this application is to provide a data standard design method and design system for vehicle networking data, which can add sub-standard items to the data standard items in the basic data standard that are associated with configuration changes and / or operating conditions, so as to increase the data standards for vehicle networking data affected by configuration changes and / or operating conditions, in order to achieve data constraint and data verification.

[0007] To achieve the above objectives, the technical solutions adopted are as follows:

[0008] The first aspect of this application provides a data standard design method for vehicle networking data, including:

[0009] Compare the vehicle data of multiple instance vehicle models with the vehicle data of the basic vehicle model respectively to obtain the configuration changes of each instance vehicle model relative to the basic vehicle model;

[0010] Obtain the operating conditions of each instance vehicle model and the vehicle networking data standard under the corresponding operating conditions;

[0011] Update the basic data standard of the basic vehicle model to add the vehicle networking data standard for all configurations and all working conditions, and obtain the overall data standard; the update includes adding sub-standard items to the data standard items in the basic data standard that are associated with configuration changes and / or operating conditions, and the sub-standard items define the vehicle networking data standard of the corresponding operating data under a single configuration and a single working condition.

[0012] In some embodiments, the vehicle networking data standard includes a data value range.

[0013] In some embodiments, the configuration change includes a change in the components that generate vehicle data.

[0014] In some embodiments, the operating conditions include driving conditions, parking conditions, charging conditions, and discharging conditions.

[0015] In some embodiments, the method further includes:

[0016] Associate each overall data standard with the vehicle model information of the corresponding example vehicle model;

[0017] Associate each sub-standard item associated with a configuration change with the configuration information of the corresponding configuration;

[0018] Associate each sub-standard item associated with an operating condition with the condition information of the corresponding operating condition;

[0019] Associate each sub-standard item associated with a configuration change and an operating condition with the configuration information of the corresponding configuration and the condition information of the corresponding operating condition;

[0020] Construct a verification query file according to all the association relationships of all example vehicle models, so as to retrieve the corresponding overall data standard when receiving the vehicle model data and condition information of the example vehicle model.

[0021] A data standard design system for vehicle networking data, comprising:

[0022] An information extraction module, which is used to compare the vehicle model data of multiple example vehicle models with the vehicle model data of the basic vehicle model respectively to obtain the configuration changes of each example vehicle model relative to the basic vehicle model; it is also used to obtain the operating conditions of each example vehicle model and the vehicle networking data standard under the corresponding operating conditions;

[0023] A standard design module, which is used to update the basic data standard of the basic vehicle model to add the vehicle networking data standard for all configurations and all working conditions, and obtain the overall data standard; the update includes adding sub-standard items to the data standard items in the basic data standard that are associated with configuration changes and / or operating conditions, and the sub-standard items define the vehicle networking data standard of the corresponding operating data under a single configuration and a single working condition.

[0024] In some embodiments, the vehicle networking data standard includes a data value range.

[0025] In some embodiments, the configuration change includes a change in components that generate vehicle data.

[0026] In some embodiments, the operating conditions include driving conditions, parking conditions, charging conditions, and discharging conditions.

[0027] In some embodiments, the system further includes:

[0028] A standard application module, which is used to associate each overall data standard with the vehicle model information of the corresponding instance vehicle model; associate each sub-standard item associated with the configuration change with the configuration information of the corresponding configuration; associate each sub-standard item associated with the operating condition with the condition information of the corresponding operating condition; associate each sub-standard item associated with the configuration change and the operating condition with the configuration information of the corresponding configuration and the condition information of the corresponding operating condition; and is further used to construct a verification query file according to all the association relationships of all instance vehicle models, so as to retrieve the corresponding overall data standard when receiving the vehicle model data and condition information of the instance vehicle model.

[0029] The beneficial effects brought by the technical solution provided in this application include:

[0030] It is possible to add sub-standard items to the data standard items in the basic data standard that are associated with the configuration change and / or the operating condition, so as to increase the data standard for vehicle networking data affected by the configuration change and / or the operating condition, so as to realize data constraint and data verification. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 It is a flowchart of a method for designing a data standard for vehicle networking data in an embodiment of the present invention.

[0032] Figure 2 It is one of the application schematic diagrams of the overall data standard in an embodiment of the present invention.

[0033] Figure 3 It is another application schematic diagram of the overall data standard in an embodiment of the present invention.

[0034] Figure 4 It is a functional module schematic diagram of a data standard design system for vehicle networking data in an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0035] The following further describes this application in detail with reference to the drawings and embodiments.

[0036] As Figure 1As shown in the figure, an embodiment of the present invention provides a method for designing data standards for vehicle networking data, including comparing the vehicle type data of multiple instance vehicle models with the vehicle type data of the basic vehicle model respectively to obtain configuration changes. Obtain the operating conditions of each instance vehicle model and the vehicle networking data standards under the corresponding operating conditions. Update the basic data standards of the basic vehicle model, and the update includes adding sub-standard items to the data standard items in the basic data standards that are associated with the configuration changes and / or operating conditions, and the sub-standard items define the vehicle networking data standards of the corresponding operating data under a single configuration and a single operating condition.

[0037] The traditional definition of vehicle networking refers to a system in which electronic tags installed on vehicles use identification technologies such as radio frequency to extract and effectively utilize the attribute information and static and dynamic information of all vehicles on the information network platform, and effectively supervise the operating states of all vehicles according to different functional requirements and provide comprehensive services.

[0038] In the field of vehicle networking, since the relevant parameters of each vehicle model are different, using a general basic data standard to constrain and verify the vehicle networking data generated by each vehicle model may result in errors. Therefore, it is necessary to further refine some data standards. After the previously established general basic data standards are established, they only play a role in display as part of the data assets, and there is not much effective linkage with data verification activities, and their due value is not reflected.

[0039] The present invention can add sub-standard items to the data standard items in the basic data standards that are associated with the configuration changes and / or operating conditions, so as to increase the data standards for vehicle networking data affected by the configuration changes and / or operating conditions, in order to achieve data constraint and data verification.

[0040] Such as Figure 1 and Figure 2 As shown in the figure, in a specific embodiment, the above method for designing data standards for vehicle networking data includes:

[0041] Step S1: Compare the vehicle type data of multiple instance vehicle models with the vehicle type data of the basic vehicle model respectively to obtain the configuration changes of each instance vehicle model relative to the basic vehicle model.

[0042] Obtain the operating conditions of each instance vehicle model and the vehicle networking data standards under the corresponding operating conditions.

[0043] Step S2: Update the basic data standards of the basic vehicle model to add vehicle networking data standards for all configurations and all operating conditions to obtain the overall data standards. The above update includes adding sub-standard items to the data standard items in the basic data standards that are associated with the configuration changes and / or operating conditions, and the sub-standard items define the vehicle networking data standards of the corresponding operating data under a single configuration and a single operating condition.

[0044] In this embodiment, by comparing the vehicle type data of all example vehicle types that need to apply data standards for vehicle networking data limitation and calibration with the vehicle type data of the basic vehicle type, the configuration changes of each example vehicle type relative to the basic vehicle type can be obtained. Such configuration changes will cause changes in the vehicle networking data generated thereby. For example, from the vehicle type data of the basic vehicle type, it can be obtained that the engine model adopted in the basic vehicle type is Engine D, while from the vehicle type data of the three example vehicle types, it can be obtained that the engine models adopted in the three example vehicle types are Engine A, Engine B, and Engine C respectively.

[0045] Then, in the standard data items of the vehicle networking data generated by the engine in the existing basic data standard, the data value range of the vehicle networking data for Engine D model will be defined. When the value range of the vehicle networking data generated by the vehicle using Engine D model conforms to the value range limited in the data standard, it indicates that the data is okay. However, when the engine model is changed in other example vehicle types, the data value range of the vehicle networking data generated by different engine models will change, and the value range in the corresponding standard should also change in order to adopt a suitable value range judgment standard for different models. If the data value range limited for Engine D model in the original basic data standard is still used to judge the vehicle networking data of, for example, Engine A model, it may be considered that the vehicle networking data generated by Engine A model is incorrect, which will lead to misjudgment of the data standard. Therefore, when adding sub-standard items corresponding to the changed configurations to the existing basic data standard for example vehicle types with different configurations, when using the overall data standard to limit and verify the vehicle networking data of example vehicle types, different sub-standard items can be used for different configurations for limitation and verification, so as to improve the applicable range and pertinence of the overall data standard.

[0046] Analyze the operating conditions of all example vehicle types that need to apply data standards for vehicle networking data limitation and calibration, and obtain the vehicle networking data standards of the same example vehicle type under each operating condition. For example, the value range of the Internet of Things data generated by the engine of a certain example vehicle type under the parking condition. Different operating conditions will result in different applicable value ranges of the Internet of Things data and will also cause changes in the vehicle networking data generated thereby. For example, the same type of Internet of Things data generated by the same example vehicle type under the three operating conditions of Operating Condition 1, Operating Condition 2, and Operating Condition 3 should apply different data judgment standards, that is, different sub-standard items.

[0047] As can be seen from the above, when the vehicle model configuration changes, for example, for a component such as an engine, if different models are used, the IoT data generated by the engine (which can be engine speed or engine fuel consumption, etc.) will be different. Correspondingly, the value range judgment criteria for different models of engines are different, that is, the applicable sub - standard items are different. When the operating conditions of the vehicle model are different, for example, for the same example vehicle model under different operating conditions, even if the engine model is the same, the IoT data generated will also be different. Correspondingly, the value range criteria for the IoT data generated by the engine under different operating conditions are different, that is, the applicable sub - standard items.

[0048] In addition to the above - described cases where IoT data is different only due to configuration changes, thus requiring different sub - standard items, and IoT data is different only due to different operating conditions, thus requiring different sub - standard items. There is also a situation where the example vehicle model, compared with the basic vehicle model, not only has a configuration change but also different operating conditions, that is, the change in the IoT data generated by the example vehicle model is related not only to the configuration change but also to the operating conditions. At this time, when setting the value range of the corresponding sub - standard items for the example vehicle model, it is necessary to combine the configuration and operating conditions to set the value range. For example, the sub - standard items required for engine model A under the first operating condition, the sub - standard items required for engine model A under the second operating condition, the sub - standard items required for engine model B under the first operating condition, the sub - standard items required for engine model B under the second operating condition, the sub - standard items required for engine model C under the first operating condition, and the sub - standard items required for engine model C under the second operating condition are all different.

[0049] In summary, in the general basic data standard, adding different sub - standard items for different configurations and different operating conditions can comprehensively and accurately limit and calibrate the vehicle - networking data generated under various configurations and various operating conditions, thereby improving the applicable range and accuracy of the data standard.

[0050] As Figure 2 shown, in a specific embodiment, the vehicle data of a vehicle includes static data and dynamic data. According to the static data, that is, the vehicle model data and component data, the verification rules, that is, the overall data standard, are retrieved from the data standard library, and the vehicle - networking data is calibrated using this standard. The data that meets the standard is normal data, and the data that does not meet the standard is dirty data.

[0051] In a preferred embodiment, the above - mentioned vehicle - networking data standard includes a data value range.

[0052] In this embodiment, in addition to the data value range, the vehicle - networking data may also include Chinese field names, English field names, definition descriptions, data types, descriptions and requirements, units, and data security levels.

[0053] Chinese field names are used to define data name information. English field names are used to define the English expressions of data name information. Definition descriptions are used to define the specific definitions of fields. Data types are used to define that there are two data types for attribute values in this specification, namely strings and numbers, which are used to describe and distinguish different data types. Descriptions and requirements are used to define the specific content descriptions and format definition requirements for this field. Units are used to define the measurement units of data. Data security levels are used to define the security level division of data according to the risk situations in domestic data interactions and outbound activities.

[0054] According to the general basic data standard, adding different Chinese field names for different configurations and working conditions can comprehensively and accurately define and calibrate the Chinese field names of vehicle networking data generated under various configurations and working conditions, thereby improving the scope of application and accuracy of the data standard.

[0055] According to the general basic data standard, adding different English field names for different configurations and working conditions can comprehensively and accurately define and calibrate the English field names of vehicle networking data generated under various configurations and working conditions, thereby improving the scope of application and accuracy of the data standard.

[0056] According to the general basic data standard, adding different definition descriptions for different configurations and working conditions can comprehensively and accurately define and calibrate the definition descriptions of vehicle networking data generated under various configurations and working conditions, thereby improving the scope of application and accuracy of the data standard.

[0057] According to the general basic data standard, adding different data types for different configurations and working conditions can comprehensively and accurately define and calibrate the data types of vehicle networking data generated under various configurations and working conditions, thereby improving the scope of application and accuracy of the data standard.

[0058] According to the general basic data standard, adding different descriptions and requirements for different configurations and working conditions can comprehensively and accurately define and calibrate the descriptions and requirements of vehicle networking data generated under various configurations and working conditions, thereby improving the scope of application and accuracy of the data standard.

[0059] According to the general basic data standard, adding different units for different configurations and working conditions can comprehensively and accurately define and calibrate the units of vehicle networking data generated under various configurations and working conditions, thereby improving the scope of application and accuracy of the data standard.

[0060] According to the general basic data standard, different data security levels are added for different configurations and different working conditions, which can comprehensively and accurately limit and calibrate the data security levels of vehicle networking data generated under various configurations and various working conditions, thereby improving the applicable scope and accuracy of the data standard.

[0061] In a preferred embodiment, the above configuration change includes a change in the components that generate vehicle data.

[0062] In this embodiment, the component change mainly includes a change in the component model, and may also be a change in the component quantity.

[0063] According to the general basic data standard, different data security levels are added for different component models, different component quantities, and different working conditions, which can comprehensively and accurately limit and calibrate the data security levels of vehicle networking data generated under various configurations and various working conditions, thereby improving the applicable scope and accuracy of the data standard.

[0064] In a preferred embodiment, the above operating conditions include driving conditions, parking conditions, charging conditions, and discharging conditions.

[0065] In this embodiment, the vehicle networking data includes relevant data generated during the processes of vehicle design, production, sales, use, and operation and maintenance. The vehicle condition is divided into a driving state and a parking state according to the vehicle speed (the vehicle speed can be the vehicle speed obtained by the sensor or the change of the GPS), and is divided into a charging state and a discharging state according to the charging and discharging power (there will also be a small-power charging action during vehicle driving).

[0066] In a preferred embodiment, the above method further includes:

[0067] Associating each overall data standard with the vehicle model information of the corresponding example vehicle model.

[0068] Associating each sub-standard item associated with the configuration change with the configuration information of the corresponding configuration.

[0069] Associating each sub-standard item associated with the operating condition with the condition information of the corresponding operating condition.

[0070] Associating each sub-standard item associated with the configuration change and the operating condition with the configuration information of the corresponding configuration and the condition information of the corresponding operating condition.

[0071] Construct a verification query file according to all the above association relationships of all example vehicle models, so as to retrieve the corresponding overall data standard when receiving the vehicle model data and condition information of the example vehicle model.

[0072] In this embodiment, the general basic data standard is combined with the actual situation of vehicle networking data, so that in addition to providing the function of display and query, the overall data standard can be more conveniently provided for the data verification process to call.

[0073] In a preferred embodiment, when using the overall data standard to verify vehicle networking data, it is possible to set which types of operation data in the vehicle networking data need to call sub-standard items according to the working conditions and configurations, and it is also possible to set which types of operation data in the vehicle networking data do not need to specifically call sub-standard items according to the public and configurations, but use the original general standard type.

[0074] Such as Figure 4 As shown, the embodiment of the present invention provides a data standard design system for vehicle networking data, including an information extraction module 1, a standard design module 2, and a standard application module 3.

[0075] The information extraction module 1 is used to compare the vehicle type data of multiple instance vehicle types with the vehicle type data of the basic vehicle type respectively to obtain the configuration changes of each instance vehicle type relative to the basic vehicle type. It is also used to obtain the operating conditions of each instance vehicle type and the vehicle networking data standard under the corresponding operating conditions.

[0076] The standard design module 2 is used to update the basic data standard of the basic vehicle type to add the vehicle networking data standard for all configurations and all working conditions to obtain the overall data standard. The above update includes adding sub-standard items to the data standard items in the basic data standard that are associated with the configuration changes and / or operating conditions, and the sub-standard items define the vehicle networking data standard of the corresponding operating data under a single configuration and a single working condition.

[0077] The standard application module 3 is used to associate each overall data standard with the vehicle type information of the corresponding instance vehicle type. Associate each sub-standard item associated with the configuration change with the configuration information of the corresponding configuration. Associate each sub-standard item associated with the operating condition with the condition information of the corresponding operating condition. Associate each sub-standard item associated with the configuration change and the operating condition with the condition information of the corresponding configuration and the corresponding operating condition. It is also used to construct a verification query file according to all the above association relationships of all instance vehicle types, so as to retrieve the corresponding overall data standard when receiving the vehicle type data and condition information of the instance vehicle type.

[0078] In this embodiment, by comparing the vehicle type data of all example vehicle types that need to apply data standards for vehicle networking data limitation and calibration with the vehicle type data of the basic vehicle type, the configuration changes of each example vehicle type relative to the basic vehicle type can be obtained. Such configuration changes will cause changes in the vehicle networking data generated thereby. For example, from the vehicle type data of the basic vehicle type, it can be obtained that the engine model adopted in the basic vehicle type is Engine D, while from the vehicle type data of the three example vehicle types, it can be obtained that the engine models adopted in the three example vehicle types are Engine A, Engine B, and Engine C respectively.

[0079] Then, in the standard data items of the vehicle networking data generated by the engine in the existing basic data standard, the data value range for the vehicle networking data of Engine D model will be defined. When the value range of the vehicle networking data generated by a vehicle with Engine D model conforms to the value range limited in the data standard, it indicates that the data is correct. However, when the engine model is changed in other example vehicle types, the data value range of the vehicle networking data generated by different engine models will change, and the value range in the corresponding standard should also change in order to adopt a suitable value range judgment standard for different models. If the data value range limited for Engine D model in the original basic data standard is still used to judge the vehicle networking data of, for example, Engine A model, it may be considered that the vehicle networking data generated by Engine A model is incorrect, which will lead to misjudgment of the data standard. Therefore, when adding sub-standard items corresponding to the changed configurations to the existing basic data standard for example vehicle types with different configurations, when using the overall data standard to limit and verify the vehicle networking data of example vehicle types, different sub-standard items can be used for different configurations for limitation and verification, so as to improve the applicable range and pertinence of the overall data standard.

[0080] Analyze the operating conditions of all example vehicle types that need to apply data standards for vehicle networking data limitation and calibration, and obtain the vehicle networking data standard of the same example vehicle type under each operating condition. For example, the value range of the Internet of Vehicles data generated by the engine of a certain example vehicle type under the parking condition. Different operating conditions will result in different applicable value ranges of the Internet of Vehicles data and will also cause changes in the vehicle networking data generated thereby. For example, the same kind of Internet of Vehicles data generated by the same example vehicle type under three operating conditions, namely Operating Condition 1, Operating Condition 2, and Operating Condition 3, should apply different data judgment standards, that is, different sub-standard items.

[0081] As can be seen from the above, when the vehicle model configuration changes, for example, for a component such as an engine, if different models are used, the IoT data generated by the engine (which can be engine speed or engine fuel consumption, etc.) will be different. Correspondingly, the value range judgment criteria for different models of engines are different, that is, the applicable sub - standard items are different. When the operating conditions of the vehicle model are different, for example, for the same example vehicle model under different operating conditions, even if it is the same engine model, the IoT data generated will also be different. Correspondingly, the value range criteria for the IoT data generated by the engine under different operating conditions are also different, that is, the applicable sub - standard items.

[0082] In addition to the above - described situation where the IoT data is different only due to configuration changes, thus requiring different sub - standard items, and the IoT data is different only due to different operating conditions, thus requiring different sub - standard items. There is also a situation where the example vehicle model, compared with the basic vehicle model, not only has a configuration change but also different operating conditions, that is, the change in the IoT data generated by the example vehicle model is related not only to the configuration change but also to the operating conditions. At this time, when setting the value range of the corresponding sub - standard items for the example vehicle model, it is necessary to combine the configuration and operating conditions to set the value range. For example, the sub - standard items required for engine model A under the first operating condition, the sub - standard items required for engine model A under the second operating condition, the sub - standard items required for engine model B under the first operating condition, the sub - standard items required for engine model B under the second operating condition, the sub - standard items required for engine model C under the first operating condition, and the sub - standard items required for engine model C under the second operating condition are all different.

[0083] In summary, in the general basic data standard, adding different sub - standard items for different configurations and different operating conditions can comprehensively and accurately limit and calibrate the vehicle - networking data generated under various configurations and various operating conditions, thereby improving the applicable range and accuracy of the data standard.

[0084] In a preferred embodiment, the above - mentioned vehicle - networking data standard includes a data value range.

[0085] In this embodiment, in addition to the data value range, the vehicle - networking data may also include Chinese field names, English field names, definition descriptions, data types, descriptions and requirements, units, and data security levels.

[0086] Chinese field names are used to define data name information. English field names are used to define the English expressions of data name information. Definition descriptions are used to define the specific definitions of fields. Data types are used to define that there are two data types for attribute values in this specification, namely strings and numbers, which are used to describe and distinguish different data types. Descriptions and requirements are used to define the specific content descriptions and format requirements for this field. Units are used to define the measurement units of data. Data security levels are used to define the security level classification of data according to the risk situations in domestic data interactions and outbound activities.

[0087] In the general basic data standard, by adding different Chinese field names for different configurations and working conditions, the Chinese field names of vehicle networking data generated under various configurations and working conditions can be comprehensively and accurately defined and calibrated, thereby improving the applicable scope and accuracy of the data standard.

[0088] In the general basic data standard, by adding different English field names for different configurations and working conditions, the English field names of vehicle networking data generated under various configurations and working conditions can be comprehensively and accurately defined and calibrated, thereby improving the applicable scope and accuracy of the data standard.

[0089] In the general basic data standard, by adding different definition descriptions for different configurations and working conditions, the definition descriptions of vehicle networking data generated under various configurations and working conditions can be comprehensively and accurately defined and calibrated, thereby improving the applicable scope and accuracy of the data standard.

[0090] In the general basic data standard, by adding different data types for different configurations and working conditions, the data types of vehicle networking data generated under various configurations and working conditions can be comprehensively and accurately defined and calibrated, thereby improving the applicable scope and accuracy of the data standard.

[0091] In the general basic data standard, by adding different descriptions and requirements for different configurations and working conditions, the descriptions and requirements of vehicle networking data generated under various configurations and working conditions can be comprehensively and accurately defined and calibrated, thereby improving the applicable scope and accuracy of the data standard.

[0092] In the general basic data standard, by adding different units for different configurations and working conditions, the units of vehicle networking data generated under various configurations and working conditions can be comprehensively and accurately defined and calibrated, thereby improving the applicable scope and accuracy of the data standard.

[0093] According to the general basic data standard, different data security levels are added for different configurations and different working conditions, which can comprehensively and accurately limit and calibrate the data security levels of vehicle networking data generated under various configurations and various working conditions, thereby improving the applicable scope and accuracy of the data standard.

[0094] In a preferred embodiment, the above configuration change includes a change in the components that generate vehicle data.

[0095] In this embodiment, the component change mainly includes a change in the component model, and may also be a change in the number of components.

[0096] According to the general basic data standard, different data security levels are added for different component models, different numbers of components, and different working conditions, which can comprehensively and accurately limit and calibrate the data security levels of vehicle networking data generated under various configurations and various working conditions, thereby improving the applicable scope and accuracy of the data standard.

[0097] In a preferred embodiment, the above operating conditions include driving conditions, parking conditions, charging conditions, and discharging conditions.

[0098] In this embodiment, vehicle networking data includes relevant data generated during the processes of vehicle design, production, sales, use, and operation and maintenance. The vehicle condition is divided into a driving state and a parking state according to the vehicle speed (the vehicle speed can be the speed obtained by the sensor or the change of the GPS), and is divided into a charging state and a discharging state according to the charging and discharging power (there will also be a small-power charging action during vehicle driving).

[0099] In a preferred embodiment, when using the overall data standard to verify vehicle networking data, it is possible to set which types of operating data in the vehicle networking data need to call sub-standard items according to the working conditions and configurations, and it is also possible to set which types of operating data in the vehicle networking data do not need to specifically call sub-standard items according to the disclosure and configurations, but instead adopt the original general standard type.

[0100] The data standard design system of this embodiment is applicable to the above various data standard design methods.

[0101] This application is not limited to the above embodiments. For those of ordinary skill in the art in this technical field, without departing from the principle of this application, several improvements and refinements can be made, and these improvements and refinements are also regarded as within the protection scope of this application.

Claims

1. A data standard design method for vehicle networking data, characterized in that, Including: Comparing the vehicle type data of multiple instance vehicle types with the vehicle type data of the base vehicle type respectively to obtain the configuration changes of each instance vehicle type relative to the base vehicle type; Obtaining the operating conditions of each instance vehicle type and the vehicle networking data standards under the corresponding operating conditions; Updating the base data standards of the base vehicle type to add vehicle networking data standards for all configurations and all operating conditions to obtain overall data standards; the update includes adding sub-standard items to the data standard items in the base data standards that are associated with configuration changes and / or operating conditions, and the sub-standard items define the vehicle networking data standards for the corresponding operating data under a single configuration and a single operating condition; The method further includes: Associating each overall data standard with the vehicle type information of the corresponding instance vehicle type; Associating each sub-standard item associated with a configuration change with the configuration information of the corresponding configuration; Associating each sub-standard item associated with an operating condition with the condition information of the corresponding operating condition; Associating each sub-standard item associated with a configuration change and an operating condition with the configuration information of the corresponding configuration and the condition information of the corresponding operating condition; Constructing a verification query file based on all the association relationships of all instance vehicle types to retrieve the corresponding overall data standards when receiving the vehicle type data and condition information of an instance vehicle type.

2. The data standard design method for vehicle networking data according to claim 1, characterized in that The vehicle networking data standards include data value ranges.

3. The data standard design method for vehicle networking data according to claim 1, characterized in that, The configuration changes include changes in components that generate vehicle data.

4. The data standard design method for vehicle networking data according to claim 1, wherein, The operating conditions include driving conditions, parking conditions, charging conditions, and discharging conditions.

5. A data standard design system for vehicle networking data, characterized in that, Including: An information extraction module, which is used to compare the vehicle type data of multiple instance vehicle types with the vehicle type data of the base vehicle type respectively to obtain the configuration changes of each instance vehicle type relative to the base vehicle type; and is also used to obtain the operating conditions of each instance vehicle type and the vehicle networking data standards under the corresponding operating conditions; A standard design module, which is used to update the base data standards of the base vehicle type to add vehicle networking data standards for all configurations and all operating conditions to obtain overall data standards; the update includes adding sub-standard items to the data standard items in the base data standards that are associated with configuration changes and / or operating conditions, and the sub-standard items define the vehicle networking data standards for the corresponding operating data under a single configuration and a single operating condition; A standard application module, which is used to associate each overall data standard with the vehicle type information of the corresponding instance vehicle type; associate each sub-standard item associated with a configuration change with the configuration information of the corresponding configuration; associate each sub-standard item associated with an operating condition with the condition information of the corresponding operating condition; associate each sub-standard item associated with a configuration change and an operating condition with the configuration information of the corresponding configuration and the condition information of the corresponding operating condition; And is also used to construct a verification query file based on all the association relationships of all instance vehicle types to retrieve the corresponding overall data standards when receiving the vehicle type data and condition information of an instance vehicle type.

6. The data standard design system for vehicle networking data according to claim 5, wherein The vehicle networking data standards include data value ranges.

7. The data standard design system for vehicle networking data according to claim 5, characterized in that The configuration changes include changes in components that generate vehicle data.

8. The data standard design system for vehicle networking data according to claim 5, characterized in that The operating conditions include driving conditions, parking conditions, charging conditions, and discharging conditions.

Images