CN116963017A - Vehicle information acquisition method, device and storage medium - Google Patents
Vehicle information acquisition method, device and storage medium Download PDFInfo
- Publication number
- CN116963017A CN116963017A CN202310842300.3A CN202310842300A CN116963017A CN 116963017 A CN116963017 A CN 116963017A CN 202310842300 A CN202310842300 A CN 202310842300A CN 116963017 A CN116963017 A CN 116963017A
- Authority
- CN
- China
- Prior art keywords
- vehicle information
- vehicle
- verification
- abnormal
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 230000002159 abnormal effect Effects 0.000 claims abstract description 72
- 230000005856 abnormality Effects 0.000 claims abstract description 32
- 238000012545 processing Methods 0.000 claims abstract description 24
- 238000012795 verification Methods 0.000 claims description 60
- 238000013506 data mapping Methods 0.000 claims description 44
- 238000004590 computer program Methods 0.000 claims description 9
- 208000018777 Vulvar intraepithelial neoplasia Diseases 0.000 description 24
- 230000008569 process Effects 0.000 description 11
- 238000004891 communication Methods 0.000 description 8
- RGVBVVVFSXWUIM-UHFFFAOYSA-M bromo(dimethyl)sulfanium;bromide Chemical compound [Br-].C[S+](C)Br RGVBVVVFSXWUIM-UHFFFAOYSA-M 0.000 description 7
- 230000006870 function Effects 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000013523 data management Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 239000000306 component Substances 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
- H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0808—Diagnosing performance data
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0841—Registering performance data
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application provides a vehicle information acquisition method, a device and a storage medium, wherein the vehicle information acquisition method comprises the following steps: acquiring a vehicle information set, wherein each piece of vehicle information included in the vehicle information set corresponds to one vehicle; determining, for each piece of vehicle information, whether the vehicle information is abnormal vehicle information; deleting the vehicle information and sending an alarm signal carrying an abnormality reason corresponding to the vehicle information to an abnormality processing platform under the condition that the vehicle information is abnormal vehicle information aiming at each piece of vehicle information; for each piece of vehicle information, in the case where the vehicle information is normal vehicle information, the vehicle information is stored and transmitted to the car remote service provider platform. The application can find out abnormal vehicle information and the abnormal reasons thereof in time, is convenient for a user to correct the abnormal vehicle information, and can also improve the data quality of the vehicle information acquired by the TSP platform.
Description
Technical Field
The present application relates to the field of automotive technologies, and in particular, to a method and apparatus for collecting vehicle information, and a storage medium.
Background
With the development of intelligent automobiles and the continuous improvement of application scene demands of owner users, a TSP (Telematics Service Provider, remote service provider) platform is used as a vehicle networking core component to play a role of a bridge between a producer and a consumer, and the source of vehicle information in the TSP platform can be a plurality of different vehicle systems, so that abnormal data can exist in the vehicle information in the TSP platform, and a large amount of manpower is required to be consumed for checking the abnormal data in the TSP platform.
Disclosure of Invention
The embodiment of the application provides a vehicle information acquisition method, a device and a storage medium, which are used for solving the problem of how to improve the data quality of vehicle information in a TSP platform.
In a first aspect, an embodiment of the present application provides a vehicle information collecting method, including:
acquiring a vehicle information set, wherein each piece of vehicle information included in the vehicle information set corresponds to one vehicle;
determining, for each piece of vehicle information, whether the vehicle information is abnormal vehicle information;
deleting the vehicle information and sending an alarm signal carrying an abnormality reason corresponding to the vehicle information to an abnormality processing platform when the vehicle information is abnormal vehicle information aiming at each piece of vehicle information;
And storing the vehicle information and sending the vehicle information to an automobile remote service provider platform for each piece of vehicle information when the vehicle information is normal vehicle information.
In a second aspect, an embodiment of the present application further provides a vehicle information acquisition apparatus, including:
a first acquisition module configured to acquire a set of vehicle information, each piece of vehicle information included in the set of vehicle information corresponding to one vehicle;
a determining module configured to determine, for each piece of vehicle information, whether the vehicle information is abnormal vehicle information;
the first processing module is used for deleting the vehicle information and sending an alarm signal carrying an abnormality reason corresponding to the vehicle information to the abnormality processing platform when the vehicle information is abnormal vehicle information aiming at each piece of vehicle information;
and the second processing module is used for storing the vehicle information and sending the vehicle information to an automobile remote service provider platform when the vehicle information is normal vehicle information aiming at each piece of vehicle information.
In a third aspect, an embodiment of the present application provides an electronic device, where the electronic device includes a processor, a memory, and a computer program stored in the memory and executable on the processor, where the computer program when executed by the processor implements the steps in the vehicle information collecting method described above.
In a fourth aspect, an embodiment of the present application further provides a computer readable storage medium, where a computer program is stored, where the computer program is executed by a processor to implement the steps in the vehicle information collecting method described above.
The embodiment of the application at least comprises the following technical effects:
according to the technical scheme, whether the vehicle information is abnormal is determined by checking each vehicle information in the acquired vehicle information set, when the vehicle information is the abnormal vehicle information, the vehicle information is deleted, the warning signal carrying the abnormality cause is sent to the abnormality processing platform, and meanwhile, when the vehicle information is the normal vehicle information, the vehicle information is stored and sent to the TSP platform of the automobile remote service provider, so that the abnormal vehicle information and the abnormality cause thereof can be found in time, a user can correct the abnormal vehicle information conveniently, and the data quality of the vehicle information acquired by the TSP platform can be improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
Fig. 1 is a schematic flow chart of a vehicle information acquisition method according to an embodiment of the present application;
FIG. 2 is a second flow chart of a vehicle information collection method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a vehicle information acquisition device according to an embodiment of the present application;
fig. 4 is a block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
In various embodiments of the present application, it should be understood that the sequence numbers of the following processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
The embodiment of the application provides a vehicle information acquisition method, which is applied to a vehicle information acquisition system, wherein the system is respectively in communication connection with a plurality of systems storing vehicle information and a TSP platform, the vehicle information set can be acquired from the plurality of systems storing the vehicle information, each vehicle information in the acquired vehicle information set is verified, the vehicle information passing the verification is sent to the TSP platform, the vehicle information failing the verification is returned, and the reason of the verification failure is fed back, so that the data quality of the vehicle information in the TSP platform can be improved. As shown in fig. 1, the vehicle information acquisition method includes:
step 101, a set of vehicle information is acquired, each piece of vehicle information included in the set of vehicle information corresponding to one vehicle.
Specifically, the vehicle information set includes a plurality of pieces of vehicle information, each piece of vehicle information corresponds to one vehicle, and then the vehicle information set includes vehicle information corresponding to a plurality of vehicles respectively. The categories to which the vehicle information corresponds include, but are not limited to, at least one of: vehicle ECU (Electronic Control Unit ) information category, vehicle basic information category, vehicle type information category, equipment information category, dealer post information category, E-call emergency rescue call system information category, and the like.
It should be noted that the vehicle information collection system may periodically pull vehicle data from at least one vehicle information storage system, and then process the collected vehicle data, and combine the vehicle data belonging to the same vehicle to obtain a plurality of pieces of vehicle information, where each piece of vehicle information corresponds to a vehicle, and the vehicle information storage system includes, but is not limited to, at least one of the following: an End of Line (EOL) system, a manufacturing execution system (Manufacturing Execution System, MES), etc.
Step 102, determining, for each piece of vehicle information, whether the vehicle information is abnormal vehicle information.
After the vehicle information set is acquired, in order to avoid including abnormal data in the vehicle information, it is necessary to determine, for each piece of vehicle information in the vehicle information set, whether the vehicle information is abnormal vehicle information, that is, whether abnormal data is included in the vehicle information, where the abnormal data includes, but is not limited to, at least one of the following: a field is null, a significant error exists in the value of the field, a mapping relation is not satisfied among some fields with a mapping relation, and some devices are bound with a plurality of vehicles at the same time.
Step 103, deleting the vehicle information and sending an alarm signal carrying an abnormality reason corresponding to the vehicle information to an abnormality processing platform when the vehicle information is abnormal vehicle information according to each piece of vehicle information.
Specifically, when the vehicle information is determined to be abnormal vehicle information, the vehicle information is deleted, an alarm signal carrying an abnormality cause is sent to an abnormality processing platform, the abnormality processing platform determines the abnormality cause of the abnormality and the corresponding abnormal vehicle information based on the received alarm signal, and the abnormality processing platform further feeds back the abnormality cause and the corresponding abnormal vehicle information to a system for acquiring the abnormal vehicle information, so that a user can process the abnormal vehicle information in time.
Step 104, for each piece of vehicle information, storing the vehicle information and sending the vehicle information to an automobile remote service provider platform when the vehicle information is normal vehicle information.
Specifically, in the case where it is determined that the vehicle information is normal vehicle information, the vehicle information is stored and transmitted to the TSP platform.
According to the embodiment of the application, whether the vehicle information is abnormal is determined by checking each vehicle information in the acquired vehicle information set, when the vehicle information is abnormal, the vehicle information is deleted, the alarm signal carrying the reason of the abnormality is sent to the abnormality processing platform, and meanwhile, when the vehicle information is normal, the vehicle information is stored and sent to the TSP platform, so that the abnormal vehicle information and the reason of the abnormality can be found in time, a user can conveniently correct the abnormal vehicle information, the data quality of the vehicle information acquired by the TSP platform can be improved, and the subsequent labor cost caused by low data quality of the vehicle information is reduced.
In an alternative embodiment of the present application, acquiring a set of vehicle information includes:
respectively acquiring a subset of the vehicle information from at least one vehicle information storage system;
and merging the vehicle information corresponding to the same vehicle in at least one vehicle information subset to obtain the vehicle information set.
Specifically, the vehicle information collection system may periodically pull vehicle data, that is, vehicle information subsets, from at least one vehicle information storage system, respectively, and then combine the vehicle information corresponding to the same vehicle in the at least one vehicle information subset, so as to obtain a plurality of pieces of vehicle information, where each piece of vehicle information corresponds to one vehicle, and the vehicle information storage system includes, but is not limited to, at least one of the following: an End of Line (EOL) system, a manufacturing execution system (Manufacturing Execution System, MES), etc.
It should be noted that, for different vehicle information storage systems, different collection periods may be set, for example, vehicle data may be pulled from the EOL system every 15 minutes, vehicle data may be pulled from the MES every 10 minutes, and a specific collection period may be set according to features and update frequency of the vehicle data stored in a specific vehicle information storage system.
According to the embodiment of the application, the vehicle information subsets are respectively acquired from at least one vehicle information storage system, and the vehicle information subsets are combined to obtain the vehicle information sets, so that the integrity of fields contained in the vehicle information is higher, and the vehicle information received by the vehicle terminal platform is richer.
In an alternative embodiment of the present application, determining whether the vehicle information is abnormal vehicle information includes:
performing non-empty verification and service attribute boundary value verification and data mapping relation verification on the vehicle information;
when the vehicle information passes through the non-empty verification, the business attribute boundary value verification and the data mapping relation verification, determining that the vehicle information is normal vehicle information;
and when the vehicle information does not pass at least one of the non-empty check, the business attribute boundary value check and the data mapping relation check, determining that the vehicle information is abnormal vehicle information.
When determining whether the vehicle information is abnormal vehicle information, the embodiment of the application can determine that the vehicle information is abnormal vehicle information by carrying out non-empty check and business attribute boundary value check and data mapping relation check on the vehicle information, and only when the non-empty check and business attribute boundary value check and data mapping relation check are passed, the vehicle information is normal vehicle information, and when at least one of the non-empty check and business attribute boundary value check and data mapping relation check is not passed, the vehicle information is abnormal vehicle information.
According to the embodiment of the application, by checking each piece of vehicle information in the vehicle information set, the abnormal vehicle information and the normal vehicle information can be identified, and the abnormal reason corresponding to the abnormal vehicle information can be determined, so that the abnormal vehicle information can be found in time while the data quality of the vehicle information received by the vehicle terminal platform is improved, and the abnormal vehicle information can be corrected.
In an optional embodiment of the present application, performing non-empty verification on the vehicle information includes:
acquiring a preset field list;
judging whether the vehicle information comprises each field in the preset field list or not;
if yes, determining that the vehicle information passes the non-empty verification;
if not, determining that the vehicle information does not pass the non-empty verification.
Specifically, when the non-empty verification is performed, a preset field list may be obtained, where a field in the preset field list is a necessary field of the vehicle information, that is, when at least one field in the preset field list is absent in the vehicle information, it is determined that the vehicle information does not pass the non-empty verification, and when the vehicle information includes each field in the preset field list, it is determined that the vehicle information passes the non-empty verification.
According to the embodiment of the application, the preset field list is obtained, whether the vehicle information comprises each field in the preset field list is judged, so that the non-empty verification is carried out on the vehicle information, the specific field which is absent in the piece of vehicle information when the vehicle information does not pass the non-empty verification can be identified, the abnormal reason corresponding to the vehicle information is determined, and further, the abnormal vehicle information is found out in time, so that the abnormal vehicle information is corrected.
In an optional embodiment of the present application, performing service attribute boundary value verification on the vehicle information includes:
acquiring service attribute boundary value conditions corresponding to each field in the vehicle information respectively;
when each field in the vehicle information meets the corresponding service attribute boundary value condition, determining that the vehicle information passes the service attribute boundary value verification;
and when at least one field in the vehicle information does not meet the corresponding service attribute boundary value condition, determining that the vehicle information fails to pass the service attribute boundary value verification.
Specifically, when the service attribute boundary value verification is performed, a service attribute boundary value condition corresponding to each field in the vehicle information can be obtained, wherein the service attribute boundary value condition corresponding to each field in the vehicle information can be preset for each field, and after the vehicle information set is obtained, the service attribute boundary value verification operation is performed for the fields included in the vehicle information. For different fields, the specific content of the corresponding service attribute boundary value condition is different according to the service to which the different fields belong, for example, the corresponding service attribute boundary value condition is 4600 beginning for the field of the IMSI (international mobile subscriber identity) value, and the corresponding service attribute boundary value condition is 8986 beginning for the field of the ICCID (integrated circuit card identity) value. Likewise, not all fields in the vehicle information have corresponding service attribute boundary value conditions, and here, the verification operation is performed only for the field corresponding to the acquired service attribute boundary value condition.
According to the embodiment of the application, the service attribute boundary value conditions respectively corresponding to the fields included in the vehicle information are obtained, whether the fields included in the vehicle information meet the corresponding service attribute boundary value conditions is judged, so that the service attribute boundary value verification is carried out on the vehicle information, when the vehicle information fails the service attribute boundary value verification, the specific fields which do not meet the service attribute boundary value conditions in the vehicle information can be identified, the abnormal reason corresponding to the vehicle information is determined, and further the abnormal vehicle information is found out in time, so that the abnormal vehicle information is corrected.
In an optional embodiment of the present application, the verifying the data mapping relationship of the vehicle information includes:
aiming at least one group of fields with data mapping relations in the vehicle information, acquiring a data mapping relation list corresponding to each group of fields;
based on each data mapping relation list, judging whether the corresponding relation between fields corresponding to the data mapping relation list in the vehicle information is correct or not;
if yes, determining that the vehicle information passes the data mapping relation verification;
if not, determining that the vehicle information does not pass the data mapping relation verification.
Specifically, when the data mapping relation verification is performed, a data mapping relation list corresponding to each group of fields can be obtained for at least one group of fields with data mapping relation in the vehicle information, then based on each data mapping relation list, whether the corresponding relation between the fields corresponding to the data mapping relation list in the vehicle information is correct or not is judged, if the corresponding relation is correct, the vehicle information is determined to pass the data mapping relation verification, and if not, the data mapping relation verification is not passed.
According to the embodiment of the application, the data mapping relation list corresponding to each group of fields is obtained, whether the corresponding relation between the fields corresponding to the data mapping relation list in the vehicle information is correct or not is judged, so that the data mapping relation verification is carried out on the vehicle information, when the vehicle information fails the data mapping relation verification, the field with the wrong mapping relation in the vehicle information can be identified, the abnormal reason corresponding to the vehicle information is determined, and further the abnormal vehicle information is found in time, so that the abnormal vehicle information is corrected.
In an optional embodiment of the application, in case the vehicle information is normal vehicle information, the method further comprises:
Acquiring configuration information matched with vehicle type information included in the vehicle information, wherein the configuration information at least comprises: model capability, home platform and equipment provider;
the configuration information is added to the vehicle information.
Specifically, in the case where it is determined that the vehicle information is normal vehicle information, the configuration information that matches the vehicle information may be acquired based on the vehicle type information included in the vehicle information, and the configuration information may be added to the vehicle information, where the configuration information includes, but is not limited to: vehicle model capability, home platform, equipment provider, etc. Where vehicle model capability refers to a related description of some function specific to the vehicle model. The home platform refers to a TSP platform, and the corresponding TSP platform may be different for different vehicle types. The equipment provider refers to a provider that provides equipment for the vehicle corresponding to the vehicle type information, and the equipment provider may be plural and correspond to different equipment, respectively.
It should be noted that, the model information in the vehicle information may be a model corresponding to the model, and the model capability may include a name corresponding to the model. For example, the name corresponding to the vehicle type before the vehicle is off line may not be determined, the vehicle information collected by the vehicle information collection system includes the vehicle type information as a string of digital codes, and the embodiment of the application may obtain the vehicle type capability (including the name corresponding to the vehicle type) matched with the vehicle type information based on the vehicle type information and add the vehicle type capability to the vehicle information, so that the vehicle information received by the TSP platform includes the corresponding vehicle type capability.
According to the embodiment of the application, the configuration information matched with the vehicle type information is added to the vehicle information, so that the content of the vehicle data in the vehicle information received by the TSP platform can be further enriched.
In an optional embodiment of the application, before determining, for each piece of vehicle information, whether the vehicle information is abnormal vehicle information, the method further includes:
judging whether a vehicle identification code (Vehicle Identification Number, VIN) list corresponding to a stored vehicle information set comprises VINs included in the vehicle information or not;
detecting the state of the stored vehicle information corresponding to the VIN under the condition that the VIN list corresponding to the stored vehicle information set comprises the VIN included in the vehicle information;
under the condition that the state corresponding to the stored vehicle information is to be detected offline, replacing the stored vehicle information with the vehicle information;
deleting the vehicle information when the state corresponding to the stored vehicle information is detected by offline;
and setting a state corresponding to the vehicle information to be detected offline under the condition that the VIN list corresponding to the stored vehicle information set does not comprise VINs included in the vehicle information.
Specifically, in order to avoid acquiring duplicate vehicle information, the number of times of checking the vehicle information of the same vehicle may be reduced, and the acquired vehicle information may be tagged, that is, a state, and in consideration of that the vehicle may be reassembled during the vehicle assembling process before the offline detection is passed, the corresponding vehicle information may change accordingly, so that after each acquisition of the vehicle information set and before checking for each vehicle information, it is necessary to determine whether the VIN included in the vehicle information is included in the VIN list corresponding to the stored vehicle information set, that is, it is necessary to determine whether the vehicle information in the vehicle information set is the vehicle information in the stored vehicle information set, that is, if not, it is a new vehicle information that needs to be added, that is, if the VIN included in the vehicle information is not included in the VIN list corresponding to the stored vehicle information set, the state corresponding to be set to be detected offline. If so, the vehicle information of the vehicle is collected before, and the state corresponding to the vehicle information needs to be checked, namely, if the VIN list corresponding to the stored vehicle information set includes VINs included in the vehicle information, the state of the stored vehicle information corresponding to the VINs is detected, if the state is to be detected offline, the stored vehicle information is replaced by the vehicle information, and if the state is to be detected offline, the piece of vehicle information is deleted.
According to the embodiment of the application, whether the vehicle information is stored or not is detected, if the vehicle information is not stored, the state is set to be detected offline, if the vehicle information is stored and the state is detected offline, the stored vehicle information is replaced by the received vehicle information, and if the vehicle information is stored and the state is detected offline, the piece of vehicle information is deleted, so that repeated vehicle information can be prevented from being acquired, and meanwhile, the number of times of checking the vehicle information of the same vehicle can be reduced.
The overall implementation flow of the embodiment of the present application is described below, in which the vehicle information collection system includes two parts, namely, a data synchronization system (XDATA) and a basic data management system (Base Data Management System, BDMS), the XDATA being responsible for pulling vehicle data from MES and EOL, and pushing the vehicle information to the TSP platform, and the BDMS being responsible for processing the vehicle data.
As shown in fig. 2, includes:
at step 201, XDATA timing pulls vehicle data from MES and EOL. The vehicle data, i.e., the subset of vehicle information described above, may be set to different acquisition cycles, such as pulling vehicle data from the EOL system every 15 minutes and from the MES every 10 minutes.
At step 202, MES and EOL return the vehicle data to XDATA.
In step 203, xdata merges the vehicle data of the same vehicle to obtain a vehicle information set, and sends the vehicle information set to the BDMS. In other words, the vehicle information corresponding to the same vehicle in the vehicle information subsets respectively corresponding to the MES and the EOL is combined to obtain the vehicle information set.
The bdms checks whether the necessary field has been filled in, step 204. In other words, the BDMS performs non-empty verification of the vehicle information in the vehicle information set. If yes, go to step 206, otherwise go to step 205.
In step 205, the BDMS rejects the data and feeds back the cause of the anomaly to XDATA.
The BDMS checks whether the VIN is present, step 206. The method can be realized by judging whether the VIN list corresponding to the stored vehicle information set comprises VINs included in the vehicle information. If yes, step 207 is performed, otherwise step 208 is performed.
Step 207, determining whether the stored vehicle information status is to be checked off-line. If yes, step 208 is performed, otherwise step 205 is performed.
Step 208 determines whether the vehicle information is abnormal vehicle information. If yes, go to step 209, otherwise go to step 205. And determining whether the vehicle information is abnormal vehicle information or not through checking the service attribute boundary value and the data mapping relation.
In step 209, the bdms sets the state corresponding to the vehicle information to be detected offline.
In step 210, the bdms generates a preset field value according to the rule. The preset field values include, but are not limited to, at least one of: vehicle type four-code, vehicle exterior color, power type, vehicle state, etc.
In step 211, XDATA receives the error cause and feeds back to the exception handling platform.
The xdata periodically pulls the vehicle information from the BDMS, step 212.
In step 213, XDATA sends the vehicle information to the TSP platform.
In step 214, the tsp platform receives the vehicle information and stores the vehicle information.
According to the embodiment, the abnormal vehicle information and the abnormal reason thereof can be found in time, so that a user can conveniently correct the abnormal vehicle information, and the data quality of the vehicle information acquired by the TSP platform can be improved.
Having described the method for acquiring vehicle information provided by the embodiment of the present application, the device for acquiring vehicle information provided by the embodiment of the present application will be described with reference to the accompanying drawings.
As shown in fig. 3, an embodiment of the present application further provides a vehicle information collecting device, where the device includes:
a first obtaining module 301, configured to obtain a set of vehicle information, where each piece of vehicle information included in the set of vehicle information corresponds to one vehicle;
A determining module 302, configured to determine, for each piece of vehicle information, whether the vehicle information is abnormal vehicle information;
a first processing module 303, configured to delete, for each piece of vehicle information, the vehicle information and send an alarm signal carrying an abnormality cause corresponding to the vehicle information to an abnormality processing platform when the vehicle information is abnormal vehicle information;
the second processing module 304 is configured to store the vehicle information and send the vehicle information to the TSP platform, where the vehicle information is normal vehicle information, for each piece of vehicle information.
Optionally, the first obtaining module 301 includes:
an acquisition sub-module for respectively acquiring the vehicle information subsets from at least one vehicle information storage system;
and the merging sub-module is used for merging the vehicle information corresponding to the same vehicle in at least one vehicle information subset to obtain the vehicle information set.
Optionally, the determining module 302 includes:
the verification sub-module is used for carrying out non-empty verification on the vehicle information, verifying the business attribute boundary value and verifying the data mapping relation;
the first determining submodule is used for determining that the vehicle information is normal vehicle information when the vehicle information passes through the non-empty verification, the business attribute boundary value verification and the data mapping relation verification;
And the second determining submodule is used for determining that the vehicle information is abnormal vehicle information when the vehicle information does not pass at least one of the non-empty check, the service attribute boundary value check and the data mapping relation check.
Optionally, the verification sub-module includes:
the first acquisition unit is used for acquiring a preset field list;
a first judging unit configured to judge whether each field in the preset field list is included in the vehicle information;
the first determining unit is used for determining that the vehicle information passes the non-empty verification if yes;
and the first determining unit is used for determining that the vehicle information does not pass the non-empty verification if not.
Optionally, the verification sub-module includes:
the second acquisition unit is used for acquiring service attribute boundary value conditions corresponding to each field in the vehicle information respectively;
a third determining unit, configured to determine that the vehicle information passes the service attribute boundary value verification when each field in the vehicle information meets a corresponding service attribute boundary value condition;
and a fourth determining unit, configured to determine that the vehicle information fails the service attribute boundary value check when at least one field in the vehicle information does not satisfy a corresponding service attribute boundary value condition.
Optionally, the verification sub-module includes:
a third obtaining unit, configured to obtain, for at least one set of fields having a data mapping relationship in the vehicle information, a data mapping relationship list corresponding to each set of fields;
the second judging unit is used for judging whether the corresponding relation between the fields corresponding to the data mapping relation list in the vehicle information is correct or not based on each data mapping relation list;
a fifth determining unit, configured to determine, if yes, that the vehicle information passes the data mapping relationship verification;
and a sixth determining unit, configured to determine that the vehicle information fails the data mapping relationship verification if not.
Optionally, in the case that the vehicle information is normal vehicle information, the apparatus further includes:
the second obtaining module is configured to obtain configuration information matched with vehicle type information included in the vehicle information, where the configuration information at least includes: model capability, home platform and equipment provider;
and the adding module is used for adding the configuration information to the vehicle information.
Optionally, before determining, for each piece of vehicle information, whether the vehicle information is abnormal vehicle information, the apparatus further includes:
The judging module is used for judging whether the VIN list corresponding to the stored vehicle information set comprises VINs included in the vehicle information or not;
the detection module is used for detecting the state of the stored vehicle information corresponding to the VIN under the condition that the VIN list corresponding to the stored vehicle information set comprises the VIN included in the vehicle information;
a third processing module, configured to replace the stored vehicle information with the vehicle information when the state corresponding to the stored vehicle information is to be detected offline;
a deleting module, configured to delete the vehicle information when the state corresponding to the stored vehicle information is detected offline;
and the fourth processing module is used for setting the state corresponding to the vehicle information to be detected offline under the condition that the VIN list corresponding to the stored vehicle information set does not comprise VINs included in the vehicle information.
According to the vehicle information acquisition device, whether the vehicle information is abnormal is determined by checking each vehicle information in the acquired vehicle information set, when the vehicle information is the abnormal vehicle information, the vehicle information is deleted, the warning signal carrying the abnormality cause is sent to the abnormality processing platform, and meanwhile, when the vehicle information is the normal vehicle information, the vehicle information is stored and sent to the TSP platform, so that the abnormal vehicle information and the abnormality cause thereof can be found in time, a user can conveniently correct the abnormal vehicle information, and the data quality of the vehicle information acquired by the TSP platform can be improved.
The embodiment of the application also provides electronic equipment, which comprises: the processor, the memory, store on the memory and can be on the computer program of the operation of the said processor, this computer program realizes each process of the above-mentioned vehicle information acquisition method embodiment when being carried out by the processor, and can reach the same technical result, in order to avoid repetition, will not be repeated here.
For example, fig. 4 shows a schematic physical structure of an electronic device.
As shown in fig. 4, the electronic device may include: processor 410, communication interface (Communications Interface) 420, memory 430 and communication bus 440, wherein processor 410, communication interface 420 and memory 430 communicate with each other via communication bus 440. The processor 410 may call logic instructions in the memory 430, the processor 410 being configured to perform the steps of: acquiring a vehicle information set, wherein each piece of vehicle information included in the vehicle information set corresponds to one vehicle; determining, for each piece of vehicle information, whether the vehicle information is abnormal vehicle information; deleting the vehicle information and sending an alarm signal carrying an abnormality reason corresponding to the vehicle information to an abnormality processing platform when the vehicle information is abnormal vehicle information aiming at each piece of vehicle information; and storing the vehicle information and sending the vehicle information to an automobile remote service provider platform for each piece of vehicle information when the vehicle information is normal vehicle information.
Further, the logic instructions in the memory 430 described above may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as a stand-alone product. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The application is trueEmbodiments also provide a computer readable storage medium having a computer program stored thereon, which when executed by a processor, implements the above Vehicle information acquisition The processes of the method embodiment can achieve the same technical effects, and in order to avoid repetition, the description is omitted here.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.
The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.
Claims (10)
1. A vehicle information acquisition method, characterized by comprising:
acquiring a vehicle information set, wherein each piece of vehicle information included in the vehicle information set corresponds to one vehicle;
determining, for each piece of vehicle information, whether the vehicle information is abnormal vehicle information;
deleting the vehicle information and sending an alarm signal carrying an abnormality reason corresponding to the vehicle information to an abnormality processing platform when the vehicle information is abnormal vehicle information aiming at each piece of vehicle information;
and storing the vehicle information and sending the vehicle information to an automobile remote service provider platform for each piece of vehicle information when the vehicle information is normal vehicle information.
2. The vehicle information collection method according to claim 1, characterized in that obtaining a set of vehicle information includes:
respectively acquiring a subset of the vehicle information from at least one vehicle information storage system;
and merging the vehicle information corresponding to the same vehicle in at least one vehicle information subset to obtain the vehicle information set.
3. The vehicle information collection method according to claim 1, characterized in that determining whether the vehicle information is abnormal vehicle information includes:
Performing non-empty verification and service attribute boundary value verification and data mapping relation verification on the vehicle information;
when the vehicle information passes through the non-empty verification, the business attribute boundary value verification and the data mapping relation verification, determining that the vehicle information is normal vehicle information;
and when the vehicle information does not pass at least one of the non-empty check, the business attribute boundary value check and the data mapping relation check, determining that the vehicle information is abnormal vehicle information.
4. The vehicle information collection method according to claim 3, wherein performing non-empty verification of the vehicle information includes:
acquiring a preset field list;
judging whether the vehicle information comprises each field in the preset field list or not;
if yes, determining that the vehicle information passes the non-empty verification;
if not, determining that the vehicle information does not pass the non-empty verification.
5. The vehicle information collection method according to claim 3, wherein performing service attribute boundary value verification on the vehicle information includes:
acquiring service attribute boundary value conditions corresponding to each field in the vehicle information respectively;
When each field in the vehicle information meets the corresponding service attribute boundary value condition, determining that the vehicle information passes the service attribute boundary value verification;
and when at least one field in the vehicle information does not meet the corresponding service attribute boundary value condition, determining that the vehicle information fails to pass the service attribute boundary value verification.
6. The vehicle information collection method according to claim 3, wherein the checking of the data mapping relationship for the vehicle information includes:
aiming at least one group of fields with data mapping relations in the vehicle information, acquiring a data mapping relation list corresponding to each group of fields;
based on each data mapping relation list, judging whether the corresponding relation between fields corresponding to the data mapping relation list in the vehicle information is correct or not;
if yes, determining that the vehicle information passes the data mapping relation verification;
if not, determining that the vehicle information does not pass the data mapping relation verification.
7. The vehicle information collection method according to claim 1, characterized in that in the case where the vehicle information is normal vehicle information, the method further comprises:
Acquiring configuration information matched with vehicle type information included in the vehicle information, wherein the configuration information at least comprises: model capability, home platform and equipment provider;
the configuration information is added to the vehicle information.
8. The vehicle information collection method according to claim 1, characterized in that before determining whether the vehicle information is abnormal vehicle information for each piece of vehicle information, the method further comprises:
judging whether a vehicle identification code list corresponding to the stored vehicle information set comprises a vehicle identification code contained in the vehicle information or not;
detecting the state of the stored vehicle information corresponding to the vehicle identification code under the condition that the vehicle identification code included in the vehicle information is included in the vehicle identification code list corresponding to the stored vehicle information set;
under the condition that the state corresponding to the stored vehicle information is to be detected offline, replacing the stored vehicle information with the vehicle information;
deleting the vehicle information when the state corresponding to the stored vehicle information is detected by offline;
and setting a state corresponding to the vehicle information to be detected offline in the case that the vehicle identification code included in the vehicle information is not included in the vehicle identification code list corresponding to the stored vehicle information set.
9. A vehicle information acquisition apparatus, characterized by comprising:
a first acquisition module configured to acquire a set of vehicle information, each piece of vehicle information included in the set of vehicle information corresponding to one vehicle;
a determining module configured to determine, for each piece of vehicle information, whether the vehicle information is abnormal vehicle information;
the first processing module is used for deleting the vehicle information and sending an alarm signal carrying an abnormality reason corresponding to the vehicle information to the abnormality processing platform when the vehicle information is abnormal vehicle information aiming at each piece of vehicle information;
and the second processing module is used for storing the vehicle information and sending the vehicle information to an automobile remote service provider platform when the vehicle information is normal vehicle information aiming at each piece of vehicle information.
10. A computer-readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the vehicle information collection method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310842300.3A CN116963017A (en) | 2023-07-10 | 2023-07-10 | Vehicle information acquisition method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310842300.3A CN116963017A (en) | 2023-07-10 | 2023-07-10 | Vehicle information acquisition method, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116963017A true CN116963017A (en) | 2023-10-27 |
Family
ID=88459643
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310842300.3A Pending CN116963017A (en) | 2023-07-10 | 2023-07-10 | Vehicle information acquisition method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116963017A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117312880A (en) * | 2023-11-28 | 2023-12-29 | 交通运输部科学研究院 | Method and device for processing basic information data of vehicle |
-
2023
- 2023-07-10 CN CN202310842300.3A patent/CN116963017A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117312880A (en) * | 2023-11-28 | 2023-12-29 | 交通运输部科学研究院 | Method and device for processing basic information data of vehicle |
| CN117312880B (en) * | 2023-11-28 | 2024-02-23 | 交通运输部科学研究院 | Method and device for processing basic information data of vehicle |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2680534B1 (en) | Logging for telematic systems | |
| CN102262404B (en) | End-of-line configuration system and configuration method for finished vehicle | |
| US8050811B2 (en) | Method for controlling the distribution of vehicle-related data | |
| US7917253B2 (en) | Method for making vehicle-related data available to an authorized third party | |
| CN116963017A (en) | Vehicle information acquisition method, device and storage medium | |
| CN105589719A (en) | System for remotely upgrading full vehicle-mounted controller softwares and upgrading method thereof | |
| CN104036559A (en) | System for performing vehicle diagnostics | |
| CN109050248B (en) | Vehicle carbon emission monitoring method and related equipment | |
| CN110602702A (en) | Function detection method and system for T-BOX in whole vehicle | |
| CN108228379B (en) | Log statistical method, collecting server, distributed server and summarizing server | |
| CN113282072A (en) | Vehicle remote diagnosis method, device, storage medium and system | |
| CN111225350B (en) | Intelligent routing method and device for short messages | |
| CN106557085A (en) | Data processing method and device | |
| CN102970279A (en) | Adaptive communication system of automobile electronic device based on serial ports | |
| DE102019119784B4 (en) | Method and system for detecting manipulation of a vehicle | |
| CN111309696A (en) | Log processing method and device, electronic equipment and readable medium | |
| CN112131554B (en) | Vehicle-mounted terminal installation identification method and device and vehicle-mounted terminal | |
| US20210264383A1 (en) | Method and system of providing cloud-based vehicle history session | |
| CN114415646B (en) | Remote vehicle diagnosis method, system and terminal equipment based on DoIP protocol | |
| CN114490713A (en) | Fault code management method, device, equipment and readable storage medium | |
| CN102236875B (en) | Traffic violation information processing method and system | |
| CN113806131A (en) | Access control method and device for fault code library, electronic equipment and storage medium | |
| CN112003867A (en) | Communication method of vehicle-mounted T-BOX and cloud server and related equipment | |
| CN116795584B (en) | Verification method, verification device, electronic equipment and storage medium | |
| CN115664737B (en) | Intrusion detection system and method |
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 |