CN113779036A - Access control method and device for fault code library, server and storage medium - Google Patents
Access control method and device for fault code library, server and storage medium Download PDFInfo
- Publication number
- CN113779036A CN113779036A CN202111101930.2A CN202111101930A CN113779036A CN 113779036 A CN113779036 A CN 113779036A CN 202111101930 A CN202111101930 A CN 202111101930A CN 113779036 A CN113779036 A CN 113779036A
- Authority
- CN
- China
- Prior art keywords
- fault
- information
- access
- fault information
- vehicle
- 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 62
- 230000002159 abnormal effect Effects 0.000 claims abstract description 82
- 238000004590 computer program Methods 0.000 claims description 20
- 238000003745 diagnosis Methods 0.000 claims description 13
- 230000007717 exclusion Effects 0.000 claims description 6
- 230000005856 abnormality Effects 0.000 description 10
- 238000001514 detection method Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- GOLXNESZZPUPJE-UHFFFAOYSA-N spiromesifen Chemical compound CC1=CC(C)=CC(C)=C1C(C(O1)=O)=C(OC(=O)CC(C)(C)C)C11CCCC1 GOLXNESZZPUPJE-UHFFFAOYSA-N 0.000 description 2
- 238000007405 data analysis Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2291—User-Defined Types; Storage management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24553—Query execution of query operations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computational Linguistics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application is applicable to the technical field of vehicles and provides a fault code library access control method, a fault code library access control device, a server and a storage medium. The access control method comprises the following steps: when an access request to a fault code library sent by user equipment is received, acquiring at least one fault code in the access request; obtaining at least one fault information according to the at least one fault code; judging whether the access request is abnormal access or not according to the at least one fault information; and if the access request is abnormal access, the user equipment is prohibited from accessing the fault code library. According to the method and the device, abnormal access to the fault code library can be forbidden, and the safety of the fault code library is improved.
Description
Technical Field
The application belongs to the technical field of vehicles, and particularly relates to a fault code library access control method, a fault code library access control device, a server and a storage medium.
Background
With the development of automotive electronics, electronic control units have become more and more complex, and thus vehicle fault diagnosis has become more and more important. The fault code of the vehicle is a fault code diagnosed by an Electronic Control Unit (ECU) after the vehicle has a fault. The fault code and the fault information corresponding to the fault code are usually stored in a fault code library, and the user equipment needs to access the fault code library each time when reading the fault information represented by the fault code, so that the risk of maliciously acquiring data in the fault code library exists in the prior art, and the safety of the fault code library is low.
Disclosure of Invention
The embodiment of the application provides a fault code library access control method, a fault code library access control device, a server and a storage medium, so that abnormal access to the fault code library is forbidden, and the safety of the fault code library is improved.
A first aspect of an embodiment of the present application provides an access control method for a fault code library, where the access control method includes:
when an access request to a fault code library sent by user equipment is received, acquiring at least one fault code in the access request;
obtaining at least one fault information according to the at least one fault code;
judging whether the access request is abnormal access or not according to the at least one fault information;
and if the access request is abnormal access, prohibiting the user equipment from accessing the fault library.
Based on the first aspect of the embodiment of the present application, in a first possible implementation manner, before determining whether the access request is an abnormal access according to the at least one piece of failure information, the method further includes:
acquiring vehicle information of a target vehicle carried by the access request;
judging the current vehicle condition of the target vehicle according to the vehicle information;
the determining whether the access request is an abnormal access according to the at least one fault information includes:
detecting whether reference fault information exists in the at least one piece of fault information according to the current vehicle condition of the target vehicle, wherein the reference fault information corresponds to a fault which does not exist under the current vehicle condition of the target vehicle;
and if the reference fault information exists in the at least one piece of fault information, determining that the access request is abnormal access.
Based on the first aspect of the embodiment of the present application, in a second possible implementation manner, the vehicle information includes vehicle type information, ECU system information, mileage information, and historical diagnosis information of the target vehicle.
Based on the first aspect of the embodiment of the present application, in a third possible implementation manner, the determining, according to the at least one piece of failure information, whether the access request is an abnormal access includes:
detecting whether specific fault information of a reference vehicle type exists in the at least one piece of fault information;
if the at least one fault information contains the specific fault information of the reference vehicle type, acquiring a positioning area corresponding to the user equipment;
and if the reference vehicle type does not exist in the positioning area, determining that the access request is abnormal access.
Based on the first aspect of the embodiment of the present application, in a fourth possible implementation manner, when the number of pieces of failure information is at least two, the determining, according to the at least one piece of failure information, whether the access request is an abnormal access includes:
detecting whether mutual exclusion fault information exists in at least two pieces of fault information, wherein the mutual exclusion fault information refers to different fault information of the same fault category belonging to the same vehicle component;
and if the mutual exclusion fault information exists in the at least two pieces of fault information, determining that the access request is abnormal access.
Based on the first aspect of the embodiment of the present application, in a fifth possible implementation manner, when the number of the pieces of failure information is at least two, the determining, according to the at least one piece of failure information, whether the access request is an abnormal access includes:
detecting whether fault information of mutually exclusive ECU systems belonging to the same vehicle exists in at least two pieces of fault information, wherein the mutually exclusive ECU systems refer to different ECU systems which do not have faults in the same vehicle at the same time, and the fault information of the mutually exclusive ECU systems refers to the fault information of each ECU system in the mutually exclusive ECU systems;
and if the fault information of the mutually exclusive ECU system belonging to the same vehicle exists in at least two pieces of fault information, determining that the access request is abnormal access.
Based on the first aspect of the embodiment of the present application, in a sixth possible implementation manner, when the number of the pieces of failure information is at least two, the determining, according to the at least one piece of failure information, whether the access request is an abnormal access includes:
detecting whether at least two pieces of fault information have specific fault information belonging to different vehicle types;
and if the at least two pieces of fault information have special fault information belonging to different vehicle types, determining that the access request is abnormal access.
A second aspect of the embodiments of the present application provides an access control device for a fault code library, where the access control device includes:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring at least one fault code in an access request when the access request to a fault code library sent by user equipment is received;
the second acquisition module is used for acquiring at least one fault message according to the at least one fault code;
the abnormal judgment module is used for judging whether the access request is abnormal access or not according to the at least one fault information;
and the access forbidding module is used for forbidding the user equipment to access the fault library if the access request is abnormal access.
Based on the second aspect of the embodiment of the present application, in a first possible implementation manner, the access control apparatus further includes:
the third acquisition module is used for acquiring the vehicle information of the target vehicle carried by the access request;
the vehicle condition judging module is used for judging the current vehicle condition of the target vehicle according to the vehicle information;
the abnormality determination module includes:
a first detecting unit, configured to detect whether there is reference fault information in the at least one fault information according to a current vehicle condition of the target vehicle, where the reference fault information corresponds to a fault that does not exist under the current vehicle condition of the target vehicle;
a first determining unit, configured to determine that the access request is an abnormal access if the reference fault information exists in the at least one piece of fault information.
In a second possible implementation manner, based on the second aspect of the embodiment of the application, the vehicle information includes vehicle type information, ECU system information, mileage information, and historical diagnosis information of the target vehicle.
Based on the second aspect of the embodiment of the present application, in a third possible implementation manner, the abnormality determining module includes:
a second detection unit for detecting whether there is specific fault information of a reference vehicle type in the at least one fault information;
the area acquisition unit is used for acquiring a positioning area corresponding to the user equipment if the specific fault information of the reference vehicle type exists in the at least one fault information;
a second determining unit, configured to determine that the access request is an abnormal access if the reference vehicle type does not exist in the positioning area.
Based on the second aspect of the embodiment of the present application, in a fourth possible implementation manner, when the number of the pieces of failure information is at least two, the abnormality determining module includes:
the third detection unit is used for detecting whether mutually exclusive fault information exists in at least two pieces of fault information, wherein the mutually exclusive fault information refers to different fault information of the same fault category belonging to the same vehicle component;
a third determining unit, configured to determine that the access request is an abnormal access if mutually exclusive failure information exists in at least two pieces of the failure information.
Based on the second aspect of the embodiment of the present application, in a fifth possible implementation manner, when the number of the pieces of failure information is at least two, the abnormality determining module includes:
a fourth detecting unit, configured to detect whether there is fault information of a mutually exclusive ECU system belonging to the same vehicle in at least two pieces of fault information, where the mutually exclusive ECU systems are different ECU systems that do not have faults in the same vehicle at the same time, and the fault information of the mutually exclusive ECU system is fault information of each ECU system in the mutually exclusive ECU system;
and the fourth determining unit is used for determining that the access request is abnormal access if the fault information of the mutually exclusive ECU system belonging to the same vehicle exists in at least two pieces of fault information.
Based on the second aspect of the embodiment of the present application, in a sixth possible implementation manner, when the number of the pieces of failure information is at least two, the abnormality determining module includes:
the fifth detection unit is used for detecting whether specific fault information belonging to different vehicle types exists in at least two pieces of fault information;
and the fifth determining unit is used for determining that the access request is abnormal access if the at least two pieces of fault information have special fault information belonging to different vehicle types.
A third aspect of embodiments of the present application provides a server, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the access control method for a fault code library according to the first aspect when executing the computer program.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the steps of the access control method for a fault code library according to the first aspect.
A fifth aspect of the present application provides a computer program product comprising a computer program which, when executed by one or more processors, performs the steps of the method for access control of a fault code repository as described in the first aspect above.
According to the scheme, when an access request to the fault code library sent by user equipment is received, at least one fault code in the access request can be obtained, at least one fault message is obtained according to the at least one fault code, whether the access request is abnormal access or not can be judged according to the at least one fault message, and when the access request is abnormal access, the user equipment is forbidden to access the fault code library, so that the abnormal access to the fault code library can be forbidden, the safety of the fault code library is improved, and the risk of maliciously obtaining data in the fault code library is reduced.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the description of the prior art will be briefly described below.
Fig. 1 is a schematic structural diagram of an access control system for a fault code library according to an embodiment of the present application;
fig. 2 is a schematic flow chart illustrating an implementation of the access control method for a fault code library according to the second embodiment of the present application;
fig. 3 is a schematic flow chart illustrating an implementation of an access control method for a fault code library according to a third embodiment of the present application;
fig. 4 is a schematic flow chart illustrating an implementation of the access control method for a fault code library according to the fourth embodiment of the present application;
fig. 5 is a schematic flow chart illustrating an implementation of the access control method for a fault code library according to the fifth embodiment of the present application;
fig. 6 is a schematic flow chart illustrating an implementation of the access control method for a fault code library according to a sixth embodiment of the present application;
fig. 7 is a schematic flow chart illustrating an implementation of an access control method for a fault code library according to a seventh embodiment of the present application;
fig. 8 is a schematic structural diagram of an access control device for a fault code library according to an eighth embodiment of the present application;
fig. 9 is a schematic structural diagram of a server according to a ninth embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
It should be understood that, the sequence numbers of the steps in this embodiment do not mean the execution sequence, and the execution sequence of each process should be determined by the function and the inherent logic of the process, and should not constitute any limitation to the implementation process of the embodiment of the present application.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
Fig. 1 is a schematic structural diagram of an access control system for a fault code library according to an embodiment of the present application.
As shown in fig. 1, the access control system includes a user device 11 and a server 12. Wherein, the user equipment 11 and the server 12 can be connected through the internet, thereby realizing the interaction of data and/or signaling.
The user equipment 11 may be a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), an intelligent wearable device (such as an intelligent watch, an intelligent bracelet), a vehicle-mounted terminal, and other various terminal devices, which is not limited in this embodiment.
In this embodiment, when reading the fault information stored in the server 12, the user equipment 11 may send an access request to the fault code library to the server 12, when receiving the access request to the fault code library sent by the user equipment 11, the server 12 may obtain at least one fault code in the access request, obtain at least one fault information according to the at least one fault code, and may determine whether the access request to the fault code library by the user equipment 11 is an abnormal access according to the at least one fault information, and when the access request is an abnormal access, by prohibiting the user equipment 11 from accessing the fault code library, the security of the fault code library may be improved. The user device 11 may be installed with vehicle diagnosis software, and during the process of performing fault diagnosis on a certain vehicle by using the vehicle diagnosis software, it may be necessary to read fault information stored in the server 12.
Fig. 2 is a schematic view of an implementation flow of the access control method for a fault code library provided in the second embodiment of the present application. As shown in fig. 2, the access control method may include the steps of:
When the user equipment needs to read the fault information stored in the server, the user equipment can send an access request to the fault code library to the server, and when the server receives the access request, the server can acquire the fault code in the access request. Wherein the number of fault codes in the access request is at least one.
The fault code library at least comprises a mapping relation between the fault codes in the access request and the corresponding fault information. One fault code corresponds to at least one fault message, for example, the fault code is P0180, then the fault code corresponds to the fault message: and the circuit of the fuel temperature sensor A fails.
The access request to the fault code library sent by the user equipment comprises at least one fault code, and when the server receives the access request, the server can search the fault information corresponding to each fault code in the at least one fault code from the fault code library stored in the server, so that the at least one fault information is obtained.
The server can judge whether the access request is abnormal access or not by detecting the relevance of at least one piece of fault information in the vehicle diagnosis process, so that the setting of the access authority of the fault code library is realized, if the access request is judged to be abnormal access, the authority that the user equipment does not access the fault code library is determined, and the step 204 is executed; and if the access request is judged to be normal access, determining that the user equipment has the authority of accessing the fault code library, and allowing the user equipment to access the fault code library.
The relevance of the at least one fault information in the vehicle diagnosis process includes, but is not limited to, relevance between the at least one fault information and the current vehicle condition of the target vehicle respectively, and the like. The target vehicle may refer to a device associated with the user device, e.g., a vehicle that is troubleshooting using vehicle diagnostic software on the user device.
And step 204, if the access request is abnormal access, prohibiting the user equipment from accessing the fault code library.
When the server judges that the access request is abnormal access, the server can forbid the abnormal access to the fault code library by forbidding the user equipment to access the fault code library, thereby improving the safety of the fault code library. The server prohibits abnormal access, so the number of accesses to the fault code database is reduced, and the congestion condition of the fault code data line can be relieved.
Optionally, in a case that the access request is an abnormal access, the method further includes:
and sending the warning information to the user equipment.
When the server determines that the access request is abnormal access, the server may also send warning information to the user equipment to warn the user that the access is illegal.
According to the method and the device, when an access request for the fault code library sent by user equipment is received, at least one fault code in the access request can be obtained, at least one fault message is obtained according to the at least one fault code, whether the access request is abnormal access or not can be judged according to the at least one fault message, and when the access request is abnormal access, the user equipment is forbidden to access the fault code library, abnormal access to the fault code library can be forbidden, so that the safety of the fault code library is improved, and the risk of maliciously obtaining data in the fault code library is reduced.
Fig. 3 is a schematic diagram of an implementation flow of the access control method for the fault code library provided in the third embodiment of the present application. As shown in fig. 3, the access control method may include the steps of:
The step is the same as step 201, and reference may be made to the related description of step 201, which is not described herein again.
The step is the same as step 202, and reference may be made to the related description of step 202, which is not repeated herein.
And step 303, acquiring the vehicle information of the target vehicle carried by the access request.
The vehicle information includes, but is not limited to, vehicle type information, ECU system information, mileage information, and historical diagnosis information of the target vehicle. The target vehicle may refer to a vehicle associated with the user device, e.g., a vehicle that is diagnosed for faults using vehicle diagnostic software on the user device.
And step 304, judging the current vehicle condition of the target vehicle according to the vehicle information.
The current vehicle condition of the target vehicle can be determined according to vehicle information such as vehicle type information, ECU system information, mileage information and historical diagnosis information of the target vehicle.
And 305, detecting whether reference fault information exists in the at least one fault information according to the current vehicle condition of the target vehicle.
Wherein the reference failure information corresponds to a failure that does not exist under the current vehicle condition of the target vehicle.
Detecting whether reference fault information exists in the at least one fault information may be understood as analyzing a vehicle condition correlation of the at least one fault information.
For example, if the current vehicle condition of the target vehicle is a low mileage, if there is fault information indicating that the oil level is too low in at least one of the fault information, it may be determined that the access request is an abnormal access because a fault in which the oil level is too low does not generally occur in the low mileage.
In an embodiment, a first corresponding relationship may be stored in the server in advance, where the first corresponding relationship at least includes a mapping relationship between a current vehicle condition of the target vehicle and corresponding reference fault information, and after the current vehicle condition of the target vehicle is analyzed, reference fault information corresponding to the current vehicle condition of the target vehicle may be searched from the first corresponding relationship, and then it may be detected whether the reference fault information exists in at least one fault information.
The vehicle condition and the corresponding reference fault information in the first corresponding relation can be obtained through big data analysis. Specifically, historical diagnostic information of a large number of vehicles is collected, and for each vehicle condition, a fault which does not occur under the vehicle condition is analyzed from the historical diagnostic information, and information representing the fault is reference fault information corresponding to the vehicle condition.
In another embodiment, whether reference fault information exists in the at least one fault information may be detected according to historical diagnostic information of the target vehicle carried in the access request. The historical diagnosis information of the target vehicle usually comprises fault information corresponding to faults which may occur under different vehicle conditions of the target vehicle, the fault information corresponding to the faults which may occur under the current vehicle conditions can be acquired from the historical diagnosis information of the target vehicle, whether fault information except the fault information corresponding to the faults which may occur under the current vehicle conditions exists in at least one piece of fault information is detected, and if the fault information except the fault information corresponding to the faults which may occur under the current vehicle conditions exists in the at least one piece of fault information, it is determined that reference fault information exists in the at least one piece of fault information; and if the at least one piece of fault information is fault information corresponding to faults which may occur under the current vehicle condition, determining that reference fault information does not exist in the at least one piece of fault information.
The step is the same as the step 204, and the same parts may specifically refer to the related description of the step 204, which is not described herein again.
On the basis of the second embodiment, according to the at least one piece of failure information, whether reference failure information exists in the at least one piece of failure information can be detected, so that whether the access request is abnormal access or not can be accurately judged.
Fig. 4 is a schematic view of an implementation flow of the access control method for a fault code library provided in the fourth embodiment of the present application. As shown in fig. 4, the access control method may include the steps of:
The step is the same as step 201, and reference may be made to the related description of step 201, which is not described herein again.
And 402, obtaining at least one fault information according to the at least one fault code.
The step is the same as step 202, and reference may be made to the related description of step 202, which is not repeated herein.
And step 403, detecting whether the at least one fault information has the specific fault information of the reference vehicle type.
The specific fault information of the reference vehicle type refers to the specific fault information of the reference vehicle type, and the fault information does not exist in other vehicle types. The reference vehicle type is preset and can be modified according to actual needs.
Whether the specific fault information of the reference vehicle type exists in the at least one piece of fault information or not can be detected, and the detection of the vehicle type and region relevance of the at least one piece of fault information can be understood.
In an embodiment, the second correspondence may be stored in the server in advance, and the second correspondence includes at least a correspondence between the reference vehicle type and the corresponding unique fault information. After the vehicle type information corresponding to the at least one fault information is acquired, whether a reference vehicle type exists in the vehicle type corresponding to the at least one fault information can be detected according to the vehicle type information corresponding to the at least one fault information, if the reference vehicle type exists, the specific fault information corresponding to the reference vehicle type is searched from the second corresponding relation, and whether the specific fault information exists in the at least one fault information is detected.
The positioning area corresponding to the user equipment refers to an area where the user equipment is currently located. The location area corresponding to the user equipment may be included in the access request, or the server may send the location request to the user equipment, and after receiving the location request, the user equipment obtains its location area and sends the location area to the server.
Step 405, if the reference vehicle type does not exist in the positioning area, determining that the access request is abnormal access.
For example, if it is detected that specific fault information (e.g., a power balance related fault) of the ford vehicle model exists in the at least one fault information and the location area of the user equipment is the chinese area, it may be determined that the access is an abnormal access because the power balance related fault of the ford vehicle model generally occurs in the north american area.
At step 406, the user device is prohibited from accessing the trouble code repository.
The step is the same as the step 204, and the same parts may specifically refer to the related description of the step 204, which is not described herein again.
In this embodiment, on the basis of the second embodiment, whether the access request is an abnormal access can be more accurately determined by detecting whether the specific fault information of the reference vehicle type exists in the at least one piece of fault information and detecting whether the reference vehicle type exists in the positioning area corresponding to the user equipment when the specific fault information of the reference vehicle type exists.
Fig. 5 is a schematic view of an implementation flow of the access control method for a fault code library provided in the fifth embodiment of the present application. As shown in fig. 5, the access control method may include the steps of:
The step is partially the same as step 201, and the same parts may specifically refer to the related description of step 201, which is not described herein again.
The step is the same as the step 202, and the same parts may be referred to the related description of the step 202, which is not repeated herein.
The mutually exclusive fault information refers to different fault information belonging to the same fault category of the same vehicle component.
In this embodiment, the vehicle component identifier and the fault category corresponding to the at least two pieces of fault information may be obtained first, and then whether mutually exclusive fault information exists in the at least two pieces of fault information may be detected according to the vehicle component identifier and the fault category corresponding to the at least two pieces of fault information.
Different vehicle component identifications differ in the vehicle component they characterize.
Detecting whether mutually exclusive fault information of the same fault category belonging to the same vehicle component exists in the at least one fault information may be understood as detecting a component relevance of the at least one fault information.
For the same fault category of the same vehicle component, fault information corresponding to different faults does not generally appear, that is, for the same fault category of the same vehicle component, one fault generally appears at the same time. For example, if the vehicle component corresponding to the fault information a and the fault information B in the at least one fault information is an engine, and the fault categories are temperature faults, the fault information a indicates that the engine temperature is too high, and the fault information B indicates that the engine temperature is too low, it may be determined that the fault information a and the fault information B are mutually exclusive fault information.
In one embodiment, after the vehicle component identifier and the fault category corresponding to each of the at least one piece of fault information are obtained, whether the fault information with the same vehicle component identifier and fault category exists in the at least one piece of fault information may be detected, and if the fault information with the same vehicle component identifier and fault category exists, the fault information with the same vehicle component identifier and fault category is determined to be mutually exclusive fault information.
The step is the same as the step 204, and the same parts may specifically refer to the related description of the step 204, which is not described herein again.
On the basis of the second embodiment, whether the access request is an abnormal access can be more accurately determined by detecting whether the mutual exclusion fault information exists in the at least two pieces of fault information.
Fig. 6 is a schematic view of an implementation flow of the access control method for the fault code library provided in the sixth embodiment of the present application. As shown in fig. 6, the access control method may include the steps of:
The step is partially the same as step 201, and the same parts may specifically refer to the related description of step 201, which is not described herein again.
The step is the same as the step 202, and the same parts may be referred to the related description of the step 202, which is not repeated herein.
In this embodiment, the vehicle identifier and the ECU system information corresponding to at least two pieces of failure information may be obtained first, and then, according to the vehicle identifier and the ECU system information corresponding to at least two pieces of failure information, whether failure information of mutually exclusive ECU systems belonging to the same vehicle exists in the at least two pieces of failure information may be detected.
Wherein different vehicle identifications are different for the vehicles they characterize. Mutually exclusive ECU systems of the same vehicle may refer to different ECU systems that do not normally fail simultaneously in the same vehicle, i.e., mutually exclusive ECU systems do not normally fail simultaneously. The failure information of the mutually exclusive ECU system refers to the failure information of each ECU system in the mutually exclusive ECU system.
Detecting whether fault information of mutually exclusive ECU systems belonging to the same vehicle exists in at least two pieces of fault information can be understood as detecting the relevance of the ECU systems of at least two pieces of fault information.
In one embodiment, information for the mutex ECU system may be stored in a server. After the vehicle identification and the ECU system information corresponding to the at least two pieces of fault information are obtained, whether fault information belonging to the same vehicle exists in the at least two pieces of fault information may be detected according to the vehicle identification corresponding to the at least two pieces of fault information, and if fault information belonging to the same vehicle exists, whether fault information belonging to the same vehicle belongs to fault information of the mutually exclusive ECU system is detected according to the ECU system information corresponding to the fault information belonging to the same vehicle and information of the mutually exclusive ECU system stored in the server.
And step 604, if the fault information of the mutually exclusive ECU systems belonging to the same vehicle exists in at least two pieces of fault information, determining that the access request is abnormal access.
The step is the same as the step 204, and the same parts may specifically refer to the related description of the step 204, which is not described herein again.
On the basis of the second embodiment, whether the access request is abnormal access can be accurately judged by detecting whether fault information of the mutually exclusive ECU system belonging to the same vehicle exists in at least one piece of fault information.
Fig. 7 is a schematic view of an implementation flow of the access control method for a fault code library provided in the seventh embodiment of the present application. As shown in fig. 7, the access control method may include the steps of:
The step is partially the same as step 201, and the same parts may specifically refer to the related description of step 201, which is not described herein again.
The step is the same as the step 202, and the same parts may be referred to the related description of the step 202, which is not repeated herein.
In this embodiment, vehicle type information corresponding to at least two pieces of fault information may be obtained first, and then, according to the vehicle type information corresponding to at least two pieces of fault information, it may be detected whether there is unique fault information belonging to different vehicle types in the at least two pieces of fault information.
Whether the at least two pieces of fault information have the specific fault information belonging to different vehicle types or not is detected, and the detection of the vehicle type relevance of the at least two pieces of fault information can be understood.
In one embodiment, a third correspondence relationship may be stored in advance in the server, the third correspondence relationship including at least a correspondence relationship between different vehicle type information and corresponding unique failure information. After the vehicle type information corresponding to the at least two pieces of fault information is acquired, whether unique fault information belonging to different vehicle types exists in the at least two pieces of fault information can be detected according to the vehicle type information corresponding to the at least two pieces of fault information and the third corresponding relation.
For example, at least two pieces of fault information include fault information C and fault information D, where the fault information C is specific fault information of a model of a bmw and the fault information D is specific fault information of a model of a public vehicle, and since the model of the bmw and the model of the public vehicle are not usually diagnosed at the same time in a vehicle diagnosis process, it can be determined that the access is an abnormal access.
The step is the same as the step 204, and the same parts may specifically refer to the related description of the step 204, which is not described herein again.
On the basis of the second embodiment, by detecting whether the at least two pieces of fault information have the specific fault information belonging to different vehicle types, whether the access request is abnormal access can be more accurately judged.
It should be noted that, when determining whether the access request is an abnormal access, the server may determine through at least one of the five schemes such as the third to seventh embodiments, and if it is not determined that the access request is an abnormal access through none of the five schemes such as the third to seventh embodiments, the server may determine that the access request is a normal access, and the server may allow the user equipment to access the fault code library.
Fig. 8 is a schematic diagram of an access control device for a fault code library according to an eighth embodiment of the present application, and only a part related to the embodiment of the present application is shown for convenience of description.
The access control device includes:
a first obtaining module 81, configured to obtain at least one fault code in an access request when receiving the access request for a fault code library sent by a user equipment;
a second obtaining module 82, configured to obtain at least one fault information according to the at least one fault code;
an abnormal judgment module 83, configured to judge whether the access request is an abnormal access according to the at least one piece of fault information, and judge whether the access request is an abnormal access;
and an access forbidding module 84, configured to forbid the user equipment from accessing the fault code library if the access request is an abnormal access.
Optionally, the access control apparatus further includes:
the third acquisition module is used for acquiring the vehicle information of the target vehicle carried by the access request;
and the vehicle condition judging module is used for judging the current vehicle condition of the target vehicle according to the vehicle information.
Optionally, the abnormality determining module 83 includes:
the first detection unit is used for detecting whether reference fault information exists in at least one piece of fault information according to the current vehicle condition of the target vehicle, and the reference fault information corresponds to a fault which does not exist under the current vehicle condition of the target vehicle;
the first determining unit is used for determining that the access request is abnormal access if the reference fault information exists in the at least one piece of fault information.
Optionally, the vehicle information includes vehicle type information, ECU system information, mileage information, and historical diagnosis information of the target vehicle.
Optionally, the abnormality determining module 83 includes:
a second detection unit for detecting whether there is specific fault information of the reference vehicle type in the at least one fault information;
the area acquisition unit is used for acquiring a positioning area corresponding to the user equipment if the specific fault information of the reference vehicle type exists in the at least one fault information;
and the second determining unit is used for determining that the access request is abnormal access if the reference vehicle type does not exist in the positioning area.
Optionally, when the number of the fault information is at least two, the abnormality determining module 83 includes:
the third detection unit is used for detecting whether mutually exclusive fault information exists in the at least two pieces of fault information, wherein the mutually exclusive fault information refers to different fault information of the same fault category belonging to the same vehicle component;
and the third determining unit is used for determining that the access request is abnormal access if the mutual exclusion fault information exists in the at least two fault information.
Optionally, when the number of the fault information is at least two, the abnormality determining module 83 includes:
the fourth detection unit is used for detecting whether fault information of mutually exclusive ECU systems belonging to the same vehicle exists in at least two pieces of fault information, wherein the mutually exclusive ECU systems refer to different ECU systems which do not have faults in the same vehicle at the same time, and the fault information of the mutually exclusive ECU systems refers to the fault information of each ECU system in the mutually exclusive ECU systems;
and the fourth determining unit is used for determining that the access request is abnormal access if the fault information of the mutually exclusive ECU system belonging to the same vehicle exists in the at least two pieces of fault information.
Optionally, when the number of the fault information is at least two, the abnormality determining module 83 includes:
the fifth detection unit is used for detecting whether specific fault information belonging to different vehicle types exists in the at least two pieces of fault information;
and the fifth determining unit is used for determining the access request as abnormal access if the at least two pieces of fault information have special fault information belonging to different vehicle types.
The access control device provided in the embodiment of the present application can be applied to the second to seventh embodiments of the method, and for details, reference is made to the description of the second to seventh embodiments of the method, and details are not repeated here.
Fig. 9 is a schematic diagram of a server provided in the ninth embodiment of the present application. As shown in fig. 9, the server 9 of this embodiment includes: a processor 90, a memory 91 and a computer program 92 stored in said memory 91 and executable on said processor 90. The processor 90, when executing the computer program 92, implements the steps in the above-described embodiments of the access control method for the fault code library, such as the steps 201 to 204 shown in fig. 2. Alternatively, the processor 90, when executing the computer program 92, implements the functions of the modules/units in the above-described device embodiments, such as the functions of the modules 81 to 84 shown in fig. 8.
Specifically, the processor 90 implements the method steps of the second to seventh embodiments by running the computer program 92 stored in the memory 91. The server 9 may include, but is not limited to, a processor 90, a memory 91. Those skilled in the art will appreciate that fig. 9 is merely an example of a server 9 and does not constitute a limitation of server 9 and may include more or fewer components than shown, or some components in combination, or different components, e.g., the server may also include input output devices, network access devices, buses, etc.
The Processor 90 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 91 may be an internal storage unit of the server 9, such as a hard disk or a memory of the server 9. The memory 91 may also be an external storage device of the server 9, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) and the like provided on the server 9. Further, the memory 91 may also include both an internal storage unit of the server 9 and an external storage device. The memory 91 is used for storing the computer program and other programs and data required by the server. The memory 91 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
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 implementation. 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 application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/server and method may be implemented in other ways. For example, the above-described apparatus/server embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. An access control method for a fault code library, the access control method comprising:
when an access request to a fault code library sent by user equipment is received, acquiring at least one fault code in the access request;
obtaining at least one fault information according to the at least one fault code;
judging whether the access request is abnormal access or not according to the at least one fault information;
and if the access request is abnormal access, the user equipment is prohibited from accessing the fault code library.
2. The access control method according to claim 1, before determining whether the access request is an abnormal access based on the at least one failure information, further comprising:
acquiring vehicle information of a target vehicle carried by the access request;
judging the current vehicle condition of the target vehicle according to the vehicle information;
the determining whether the access request is an abnormal access according to the at least one fault information includes:
detecting whether reference fault information exists in the at least one piece of fault information according to the current vehicle condition of the target vehicle, wherein the reference fault information corresponds to a fault which does not exist under the current vehicle condition of the target vehicle;
and if the reference fault information exists in the at least one piece of fault information, determining that the access request is abnormal access.
3. The access control method according to claim 2, wherein the vehicle information includes vehicle type information, ECU system information, mileage information, and historical diagnosis information of the target vehicle.
4. The access control method according to claim 1, wherein the determining whether the access request is an abnormal access according to the at least one failure information includes:
detecting whether specific fault information of a reference vehicle type exists in the at least one piece of fault information;
if the at least one fault information contains the specific fault information of the reference vehicle type, acquiring a positioning area corresponding to the user equipment;
and if the reference vehicle type does not exist in the positioning area, determining that the access request is abnormal access.
5. The access control method according to claim 1, wherein when the number of the failure information is at least two, said determining whether the access request is an abnormal access based on the at least one failure information includes:
detecting whether mutually exclusive fault information exists in at least two pieces of fault information, wherein the mutually exclusive fault information refers to different fault information of the same fault category belonging to the same vehicle component;
and if the mutual exclusion fault information exists in the at least two pieces of fault information, determining that the access request is abnormal access.
6. The access control method according to claim 1, wherein when the number of the failure information is at least two, said determining whether the access request is an abnormal access based on the at least one failure information includes:
detecting whether fault information of mutually exclusive ECU systems belonging to the same vehicle exists in at least two pieces of fault information, wherein the mutually exclusive ECU systems refer to different ECU systems which do not have faults in the same vehicle at the same time, and the fault information of the mutually exclusive ECU systems refers to the fault information of each ECU system in the mutually exclusive ECU systems;
and if the fault information of the mutually exclusive ECU system belonging to the same vehicle exists in at least two pieces of fault information, determining that the access request is abnormal access.
7. The access control method according to claim 1, wherein when the number of the failure information is at least two, said determining whether the access request is an abnormal access based on the at least one failure information includes:
detecting whether at least two pieces of fault information have specific fault information belonging to different vehicle types;
and if the at least two pieces of fault information have special fault information belonging to different vehicle types, determining that the access request is abnormal access.
8. An access control device for a trouble code repository, the access control device comprising:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring at least one fault code in an access request when the access request to a fault code library sent by user equipment is received;
the second acquisition module is used for acquiring at least one fault message according to the at least one fault code;
the abnormal judgment module is used for judging whether the access request is abnormal access or not according to the at least one fault information;
and the access forbidding module is used for forbidding the user equipment to access the fault code library if the access request is abnormal access.
9. A server comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the steps of the access control method according to any of claims 1 to 7 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the access control method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111101930.2A CN113779036A (en) | 2021-09-18 | 2021-09-18 | Access control method and device for fault code library, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111101930.2A CN113779036A (en) | 2021-09-18 | 2021-09-18 | Access control method and device for fault code library, server and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113779036A true CN113779036A (en) | 2021-12-10 |
Family
ID=78852268
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111101930.2A Pending CN113779036A (en) | 2021-09-18 | 2021-09-18 | Access control method and device for fault code library, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113779036A (en) |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101094097A (en) * | 2006-06-23 | 2007-12-26 | 联想(北京)有限公司 | Hardwware access control system and method |
| US20080161994A1 (en) * | 2006-12-28 | 2008-07-03 | Detroit Diesel Corporation | Method and system for autogenerating static fault code data based on a unified summary table for heavy duty diesel engines |
| US20080215806A1 (en) * | 2007-03-01 | 2008-09-04 | Feather Stanley S | Access control management |
| KR20090030664A (en) * | 2007-09-20 | 2009-03-25 | 성균관대학교산학협력단 | Active database based total management system and method for diagnostic information and positioning information of vehicle |
| US20100122120A1 (en) * | 2008-11-12 | 2010-05-13 | Lin Yeejang James | System And Method For Detecting Behavior Anomaly In Information Access |
| JP2010128858A (en) * | 2008-11-28 | 2010-06-10 | Mizuho Information & Research Institute Inc | Fault information providing system, fault information providing method and fault information providing program |
| US9224006B1 (en) * | 2015-07-29 | 2015-12-29 | KGSS, Inc. | System and method of secure data access |
| US20160378664A1 (en) * | 2015-06-26 | 2016-12-29 | Intel Corporation | Supporting fault information delivery |
| CN106557082A (en) * | 2015-09-26 | 2017-04-05 | 广州汽车集团股份有限公司 | DTC detection and recording method and the vehicle electrically controlling unit of vehicle electrically controlling unit |
| CN110062350A (en) * | 2018-01-19 | 2019-07-26 | 通用汽车环球科技运作有限责任公司 | Secure access to the vehicle peripheral equipment connected |
| CN111917606A (en) * | 2020-07-28 | 2020-11-10 | 青岛海尔科技有限公司 | Method and device for processing fault information, storage medium and electronic equipment |
| CN112243014A (en) * | 2019-07-17 | 2021-01-19 | 青岛海尔洗衣机有限公司 | Fault information processing method and device, electronic equipment and storage medium |
| CN112291258A (en) * | 2020-11-12 | 2021-01-29 | 杭州比智科技有限公司 | Gateway risk control method and device |
| CN113311807A (en) * | 2021-05-28 | 2021-08-27 | 重庆长安新能源汽车科技有限公司 | Method, system and storage medium for online diagnosis and active offer handling of vehicle faults |
-
2021
- 2021-09-18 CN CN202111101930.2A patent/CN113779036A/en active Pending
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101094097A (en) * | 2006-06-23 | 2007-12-26 | 联想(北京)有限公司 | Hardwware access control system and method |
| US20080161994A1 (en) * | 2006-12-28 | 2008-07-03 | Detroit Diesel Corporation | Method and system for autogenerating static fault code data based on a unified summary table for heavy duty diesel engines |
| US20080215806A1 (en) * | 2007-03-01 | 2008-09-04 | Feather Stanley S | Access control management |
| KR20090030664A (en) * | 2007-09-20 | 2009-03-25 | 성균관대학교산학협력단 | Active database based total management system and method for diagnostic information and positioning information of vehicle |
| US20100122120A1 (en) * | 2008-11-12 | 2010-05-13 | Lin Yeejang James | System And Method For Detecting Behavior Anomaly In Information Access |
| JP2010128858A (en) * | 2008-11-28 | 2010-06-10 | Mizuho Information & Research Institute Inc | Fault information providing system, fault information providing method and fault information providing program |
| US20160378664A1 (en) * | 2015-06-26 | 2016-12-29 | Intel Corporation | Supporting fault information delivery |
| US9224006B1 (en) * | 2015-07-29 | 2015-12-29 | KGSS, Inc. | System and method of secure data access |
| CN106557082A (en) * | 2015-09-26 | 2017-04-05 | 广州汽车集团股份有限公司 | DTC detection and recording method and the vehicle electrically controlling unit of vehicle electrically controlling unit |
| CN110062350A (en) * | 2018-01-19 | 2019-07-26 | 通用汽车环球科技运作有限责任公司 | Secure access to the vehicle peripheral equipment connected |
| CN112243014A (en) * | 2019-07-17 | 2021-01-19 | 青岛海尔洗衣机有限公司 | Fault information processing method and device, electronic equipment and storage medium |
| CN111917606A (en) * | 2020-07-28 | 2020-11-10 | 青岛海尔科技有限公司 | Method and device for processing fault information, storage medium and electronic equipment |
| CN112291258A (en) * | 2020-11-12 | 2021-01-29 | 杭州比智科技有限公司 | Gateway risk control method and device |
| CN113311807A (en) * | 2021-05-28 | 2021-08-27 | 重庆长安新能源汽车科技有限公司 | Method, system and storage medium for online diagnosis and active offer handling of vehicle faults |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110300686B (en) | Data analysis device and storage medium | |
| CN108700875A (en) | Vehicular diagnostic method, system, equipment and computer readable storage medium | |
| CN109814524B (en) | Vehicle diagnosis method, device and system | |
| CN113127338A (en) | Firmware testing method, server and computer readable storage medium | |
| CN111552267B (en) | Vehicle diagnosis method and device and vehicle diagnosis equipment | |
| CN112558584B (en) | Diagnostic data acquisition method and device and diagnostic equipment | |
| CN113778557B (en) | Vehicle diagnosis software configuration method, device, server and storage medium | |
| CN113114659B (en) | Diagnostic equipment detection method and device, terminal equipment and storage medium | |
| CN110325410B (en) | Data analysis device and storage medium | |
| CN109885037A (en) | A kind of method and relevant device of vehicle diagnostics | |
| CN112184946A (en) | Vehicle data reading method and related equipment | |
| CN108228744B (en) | Vehicle diagnosis data management method and device | |
| CN113779036A (en) | Access control method and device for fault code library, server and storage medium | |
| CN113655776B (en) | Vehicle detection method and device, electronic equipment and storage medium | |
| CN108763053B (en) | Method for generating buried point name and terminal equipment | |
| CN114625106B (en) | Method, device, electronic equipment and storage medium for vehicle diagnosis | |
| CN115757107A (en) | Embedded point detection method, device, server and storage medium | |
| Buquerin et al. | Digital forensics investigation of the tesla autopilot file system,” | |
| US11544408B2 (en) | Method and system for managing vehicle generated data | |
| CN113806131A (en) | Access control method and device for fault code library, electronic equipment and storage medium | |
| CN112859805A (en) | Engine controller online diagnosis method and related device | |
| CN112687030A (en) | Vehicle condition information processing method and device | |
| CN112327800A (en) | Vehicle detection method and device and diagnosis equipment | |
| CN111145386A (en) | Method, equipment and medium for managing vehicle computer data based on block chain | |
| CN111369790A (en) | Vehicle passing record correction method, device, equipment and storage medium |
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 |