CN113703868A - Vehicle diagnostic software configuration method, electronic device and readable storage medium - Google Patents
Vehicle diagnostic software configuration method, electronic device and readable storage medium Download PDFInfo
- Publication number
- CN113703868A CN113703868A CN202111002191.1A CN202111002191A CN113703868A CN 113703868 A CN113703868 A CN 113703868A CN 202111002191 A CN202111002191 A CN 202111002191A CN 113703868 A CN113703868 A CN 113703868A
- Authority
- CN
- China
- Prior art keywords
- data
- acquisition request
- configuration data
- diagnostic software
- target
- 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 69
- 230000004044 response Effects 0.000 claims description 22
- 230000006870 function Effects 0.000 claims description 21
- 238000004590 computer program Methods 0.000 claims description 19
- 238000010586 diagram Methods 0.000 description 11
- 238000012545 processing Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 6
- 238000003745 diagnosis Methods 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 244000064864 Sorghum bicolor var. caffrorum Species 0.000 description 1
- 239000008280 blood Substances 0.000 description 1
- 210000004369 blood Anatomy 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000036541 health Effects 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
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
- B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
- B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
- B60R16/0231—Circuits relating to the driving or the functioning of the vehicle
- B60R16/0232—Circuits relating to the driving or the functioning of the vehicle for measuring vehicle parameters and indicating critical, abnormal or dangerous conditions
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Automation & Control Theory (AREA)
- Mechanical Engineering (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application is applicable to the technical field of control, and provides a vehicle diagnosis software configuration method, electronic equipment and a readable storage medium. The method comprises the following steps: receiving a first diagnostic software acquisition request from a terminal device, wherein the first diagnostic software acquisition request contains first identification information of a first target vehicle; responding to the first diagnosis software acquisition request, sending general data to the terminal equipment, and searching first target configuration data corresponding to the first identification information, wherein the first target configuration data comprises system data and functional data applicable to a vehicle type corresponding to a first target vehicle; and sending the first target configuration data to the terminal equipment. According to the method and the device, the data which are stored in the terminal equipment and used for configuring the diagnostic software in the prior art are stored in the server, so that the data quantity stored in the terminal equipment can be reduced, and the hardware cost can be reduced.
Description
Technical Field
The present application relates to the field of control technologies, and in particular, to a vehicle diagnostic software configuration method, an electronic device, and a readable storage medium.
Background
With the continuous development of the automobile electronic industry, the vehicle type brands of the host computer factory are continuously increased, the host computer factory can develop different automobile diagnosis software according to different vehicle type brands, and the data of the automobile diagnosis software is stored in the terminal equipment. However, since these data are stored in the terminal device, the data volume of the database is increased, and the hardware cost is increased accordingly.
Disclosure of Invention
The embodiment of the application provides a vehicle diagnosis software configuration method and device, electronic equipment and a readable storage medium, and can solve the problems of large storage data volume and high hardware cost of terminal equipment.
In a first aspect, an embodiment of the present application provides a vehicle diagnostic software configuration method, which is applied to a server, and includes:
receiving a first diagnostic software acquisition request from a terminal device, wherein the first diagnostic software acquisition request contains first identification information of a first target vehicle;
responding to the first diagnostic software acquisition request, and sending general data to the terminal equipment;
searching first target configuration data corresponding to the first identification information, wherein the first target configuration data comprise system data and function data applicable to a vehicle type corresponding to the first target vehicle;
and sending the first target configuration data to the terminal equipment.
Further, searching for the first target configuration data corresponding to the first identification information includes:
determining the vehicle type of the first target vehicle according to the first identification information;
and searching first target configuration data corresponding to the vehicle type of the first target vehicle based on the corresponding relation between the preset vehicle type and the configuration data.
Further, before searching for the first target configuration data corresponding to the first identification information, the method further includes:
identifying first identification information in the first diagnostic software acquisition request;
and if the first identification information cannot be identified, sending prompt information to the terminal equipment, wherein the prompt information is used for indicating the terminal equipment to prompt a user to input the first identification information.
Further, before receiving the first diagnostic software acquisition request from the terminal device, the method further includes:
acquiring the configuration data;
and establishing a corresponding relation between the configuration data and the vehicle type.
Further, after sending the first target configuration data to the terminal device, the method further includes:
receiving new user information from the terminal equipment;
judging whether the new user information meets a preset condition or not;
if yes, adding a new user.
Further, the first diagnostic software acquisition request further includes an identifier of the terminal device;
correspondingly, after responding to the first diagnostic software acquisition request, the method further comprises the step of storing the identification;
after sending the first target configuration data to the terminal device, the method further comprises:
receiving a second diagnostic software acquisition request from the terminal equipment, wherein the second diagnostic software acquisition request comprises an identifier of the terminal equipment and second identifier information of a second target vehicle;
searching the storage record of the identifier in response to the second diagnostic software acquisition request;
if the storage record is found, second target configuration data corresponding to the second identification information is found, wherein the second target configuration data comprises system data and functional data applicable to a vehicle type corresponding to the second target vehicle;
and sending the second target configuration data to the terminal equipment.
In a second aspect, an embodiment of the present application provides a vehicle diagnostic software configuration method, which is applied to a terminal device, and includes:
sending a first diagnostic software acquisition request to a server, wherein the first diagnostic software acquisition request comprises first identification information of a first target vehicle;
receiving general data returned by the server in response to the first diagnostic software acquisition request;
receiving first target configuration data from the server, wherein the first target configuration data comprises system data and function data applicable to a vehicle type corresponding to the first target vehicle;
and generating first diagnosis software according to the general data and the first target configuration data, wherein the first diagnosis software is suitable for the vehicle type of the first target vehicle.
Further, the first diagnostic software acquisition request further includes an identifier of the terminal device, and the identifier is stored by the server after responding to the first diagnostic software acquisition request;
after receiving the first target configuration data from the server, the method further comprises:
sending a second diagnostic software acquisition request to a server, wherein the second diagnostic software acquisition request comprises the identifier of the terminal equipment and second identifier information of a second target vehicle;
receiving second target configuration data returned by the server in response to the second diagnostic software acquisition request, wherein the second target configuration data comprises system data and function data applicable to a vehicle type corresponding to the second target vehicle;
and generating second diagnosis software according to the general data and the second target configuration data, wherein the second diagnosis software is suitable for the vehicle type of the second target vehicle.
Further, after receiving the target configuration data from the server, the method further comprises:
acquiring new user information;
and sending the new user information to the server.
In a third aspect, an embodiment of the present application provides a vehicle diagnostic software configuration apparatus, including:
a first receiving unit, configured to receive a first diagnostic software acquisition request from a terminal device, where the first diagnostic software acquisition request includes first identification information of a first target vehicle;
the first sending unit is used for responding to the first diagnosis software acquisition request and sending general data to the terminal equipment;
the searching unit is used for searching first target configuration data corresponding to the first identification information, and the first target configuration data comprises system data and function data applicable to a vehicle type corresponding to the first target vehicle;
a second sending unit, configured to send the first target configuration data to the terminal device.
In a fourth aspect, an embodiment of the present application provides a vehicle diagnostic software configuration apparatus, including:
a third sending unit, configured to send a first diagnostic software acquisition request to a server, where the first diagnostic software acquisition request includes first identification information of a first target vehicle;
the second receiving unit is used for receiving the general data returned by the server in response to the first diagnostic software acquisition request; the system comprises a server, a first target configuration data acquisition module, a second target configuration data acquisition module, a first target configuration data processing module and a second target configuration data processing module, wherein the first target configuration data acquisition module is used for acquiring first target configuration data of a corresponding vehicle type of a first target vehicle;
and the generating unit is used for generating first diagnostic software according to the general data and the first target configuration data, wherein the first diagnostic software is diagnostic software suitable for the vehicle type of the first target vehicle.
In a fifth aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the method as described in any of the first or second aspects above when executing the computer program.
In a sixth aspect, the present application provides a computer-readable storage medium, which stores a computer program, and when executed by a processor, the computer program implements the method according to any one of the first aspect or the second aspect.
In a seventh aspect, this application embodiment provides a computer program product, which when run on a terminal device, causes the terminal device to execute the method of any one of the first aspect and the second aspect.
It is to be understood that, the beneficial effects of the second to seventh aspects may be referred to the relevant description of the first aspect, and are not repeated herein.
Compared with the prior art, the embodiment of the application has the advantages that:
the method comprises the steps that a first diagnosis software obtaining request from terminal equipment is received, wherein the first diagnosis software obtaining request comprises first identification information of a first target vehicle; responding to a first diagnostic software acquisition request, and sending general data to the terminal equipment; searching first target configuration data corresponding to the first identification information, wherein the first target configuration data comprise system data and functional data applicable to a vehicle type corresponding to a first target vehicle; and sending the first target configuration data to the terminal equipment. The data for configuring the diagnostic software stored in the terminal equipment in the prior art are stored in the server, and the data for configuring the diagnostic software are designed into general data and configuration data. When the terminal equipment uses the diagnostic software, the server issues data for configuring the diagnostic software according to the diagnostic software acquisition request sent by the terminal equipment, so that the terminal equipment does not need to store the data for configuring the diagnostic software, the data quantity stored by the terminal equipment is reduced, and the hardware cost is reduced. And the data for configuring the diagnostic software is designed into general data and configuration data, which is beneficial to the management of various types of data.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
FIG. 1 is a system diagram of a vehicle diagnostic software configuration application function provided by an embodiment of the present application;
FIG. 2 is a schematic flow chart diagram of a vehicle diagnostic software configuration method provided by an embodiment of the present application;
FIG. 3 is a schematic flow chart diagram of a vehicle diagnostic software configuration method provided by another embodiment of the present application;
FIG. 4 is a schematic structural diagram of a vehicle diagnostic software configuration device provided in an embodiment of the present application;
FIG. 5 is a schematic structural diagram of a vehicle diagnostic software configuration apparatus according to another embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device provided in an 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. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. 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 also be 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.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.
Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.
With the continuous development of the automobile electronic industry, the vehicle type brands of the host computer factory are continuously increased, the host computer factory can develop different automobile diagnosis software according to different vehicle type brands, and the data of the automobile diagnosis software is stored in the terminal equipment. However, since these data are stored in the terminal device, the data volume of the database is increased, and the hardware cost is increased accordingly. In order to avoid the problems of large amount of data stored in a terminal device and high hardware cost, the embodiment of the application provides a vehicle diagnostic software configuration method, a vehicle diagnostic software configuration device, an electronic device and a readable storage medium. When the terminal equipment uses the diagnostic software, the server issues data for configuring the diagnostic software according to the diagnostic software acquisition request sent by the terminal equipment, so that the terminal equipment does not need to store the data for configuring the diagnostic software, the data quantity stored by the terminal equipment is reduced, and the hardware cost is reduced.
FIG. 1 is a system diagram of a vehicle diagnostic software configuration application function provided in an embodiment of the present application. By way of example and not limitation, as shown in fig. 1, the system includes a user 10, a terminal device 20, a vehicle 30, and a server 40. It should be noted that the user 10 is a user who sends a diagnostic software acquisition request through the terminal device 20, and the terminal device 20 is a device that can store and use diagnostic software and is used for collecting bus data of the vehicle 30 to perform fault diagnosis or acquiring driving data to perform driving analysis; the vehicle 30 is a target vehicle diagnosed by the diagnostic software, and includes at least one target vehicle; the server 40 is a server 40 storing data for configuring the diagnostic software, the data includes general data and configuration data, the general data includes general interface data and general protocol data of the diagnostic software, and the configuration data includes system data and function data of a vehicle type corresponding to the applicable target vehicle.
In this embodiment, when the user 10 uses the terminal device 20 for the first time and wants to diagnose one of the target vehicles, first, a diagnostic software acquisition request is sent to the server 40 through the terminal device 20, after receiving the diagnostic software acquisition request, the server 40 issues general data to the terminal device 20 in response to the diagnostic software acquisition request, then searches for corresponding target configuration data according to the identification information of the target vehicle in the diagnostic software acquisition request, and then issues the target configuration data to the terminal device 20; the terminal device 20 combines the received generic data with the target configuration data to generate corresponding diagnostic software, and the user 10 uses the diagnostic software on the terminal device 20 to diagnose the target vehicle.
When the user 10 wants to diagnose another target vehicle, firstly, a diagnosis software acquisition request is sent to the server 40 through the terminal device 20, and the server 40 receives the diagnosis software acquisition request; responding to the diagnostic software acquisition request, searching a storage record of the identifier of the terminal device 20, wherein the identifier is stored when the server receives the diagnostic software acquisition request sent by the terminal device for the first time; if the storage record is found, it indicates that the server 40 has issued the general module to the terminal device 20, and the server 40 only needs to find corresponding target configuration data according to the identification information of the target vehicle in the diagnostic software acquisition request, and then issues the corresponding target configuration data to the terminal device 20; the terminal device 20 combines the previously received generic module with the currently received target configuration data to generate corresponding diagnostic software, which the user 10 then uses on the terminal device 20 to diagnose another target vehicle.
When the family member of the user 10 also wants to use the terminal device 20, first the user 10 inputs new user information on the terminal device 20, the terminal device 20 acquires the new user information, and sends the new user information to the server 40; after receiving the new user information, the server 40 determines whether the new user information meets a preset condition, and if the new user information meets the preset condition, the new user is added to establish a new account for the new user; the family member can then use the terminal device 20 to diagnose the vehicle that he or she uses.
FIG. 2 is a flowchart illustrating a vehicle diagnostic software configuration method according to an embodiment of the present application. By way of example and not limitation, as shown in fig. 2, the method is specifically applied to a server, and includes:
s201: a first diagnostic software acquisition request is received from a terminal device, the first diagnostic software acquisition request including first identification information of a first target vehicle.
As one implementation, the first identification information is in the form of a vehicle serial number.
Specifically, after receiving a first diagnostic software acquisition request, the first diagnostic software acquisition request is analyzed to obtain first identification information of the first target vehicle.
S202: and responding to the first diagnosis software acquisition request, and sending the general data to the terminal equipment.
The universal data comprises universal interface data and universal protocol data of the diagnostic software, and the universal protocol data comprises international standard protocols such as a CAN protocol, a KWP protocol, a VPW protocol and a CANFD protocol. These international standard protocols are applicable to any vehicle type.
S203: and searching first target configuration data corresponding to the first identification information, wherein the first target configuration data comprises system data and functional data applicable to a vehicle type corresponding to the first target vehicle.
The system data comprises engine information, gearbox information, airbag information, ABS information and the like, the functional data comprises code reading information, code clearing information, data flow information, action test information, online programming information, oil nozzle matching information and the like, and each system data has corresponding functional data.
S204: and sending the first target configuration data to the terminal equipment.
Illustratively, the server receives a first diagnostic software acquisition request from the terminal device, responds to the first diagnostic software acquisition request, and analyzes the request to obtain first identification information of a first target vehicle, where the first identification information includes a vehicle type: junwei LSGGA54Y6 DHXXXXXXX in 2013, wherein X represents 0-9. Then the server sends the general data to the terminal device; and then recognizing the vehicle type of the first target vehicle from the first identification information as follows: in 2013, Junwei LSGGA54Y6 DHXXXXXXX, then, according to a vehicle type, namely a vehicle serial number, target configuration data corresponding to the vehicle type, namely first target configuration data is searched, the first target configuration data comprises all system data corresponding to the vehicle type, specifically comprises engine information, gearbox information, airbag information and ABS information, and functional data corresponding to each system, specifically comprises code reading information, code clearing information, data flow information, action test information, online programming information and oil nozzle matching information, and then the first target configuration data is sent to the terminal equipment.
The embodiment receives a first diagnostic software acquisition request from a terminal device, wherein the first diagnostic software acquisition request contains first identification information of a first target vehicle; responding to a first diagnostic software acquisition request, and sending general data to the terminal equipment; searching first target configuration data corresponding to the first identification information, wherein the first target configuration data comprise system data and functional data applicable to a vehicle type corresponding to a first target vehicle; and sending the first target configuration data to the terminal equipment. The present embodiment stores data for configuring diagnostic software stored in a terminal device in a server, and designs data for configuring diagnostic software into general data and configuration data. When the terminal equipment uses the diagnostic software, the server issues data for configuring the diagnostic software according to the diagnostic software acquisition request sent by the terminal equipment, so that the terminal equipment does not need to store the data for configuring the diagnostic software, the data quantity stored by the terminal equipment is reduced, and the hardware cost is reduced. And the data for configuring the diagnostic software is designed into general data and configuration data, which is beneficial to the management of various types of data.
In another embodiment, the step 203 of searching for the first target configuration data corresponding to the first identification information includes:
and determining the vehicle type of the first target vehicle according to the first identification information.
And searching first target configuration data corresponding to the vehicle type of the first target vehicle based on the corresponding relation between the preset vehicle type and the configuration data.
Specifically, the server stores in advance a correspondence between the vehicle type and the configuration data. As one implementation, the correspondence may be made in the form of a relationship table.
Illustratively, the first identification information includes a vehicle type: and in 2013, Junwei LSGGA54Y6 DHXXXXXXX, and then according to the vehicle type, searching target configuration data corresponding to the vehicle type in a corresponding relation table: system data and function data corresponding to the system data.
According to the embodiment, the target configuration data corresponding to the vehicle type of the target vehicle is searched based on the corresponding relation between the preset vehicle type and the configuration data, so that the target configuration data corresponding to the vehicle type of the target vehicle can be quickly and accurately searched.
In another embodiment, before step S201 of receiving a first diagnostic software acquisition request from a terminal device, the method further includes:
configuration data is obtained.
And establishing a corresponding relation between the configuration data and the vehicle type.
Specifically, data for configuring the diagnostic software is designed into general data and configuration data, and then the general data and the configuration data are obtained and packaged and stored in a database. And obtaining identification information of the vehicle, wherein the identification information comprises the vehicle type, and then establishing a corresponding relation between the configuration data and the vehicle type.
The embodiment provides a basis for quickly and accurately finding the target module data of the vehicle type corresponding to the target vehicle after the server receives the diagnostic software acquisition request by pre-establishing the corresponding relationship between the configuration data and the vehicle type.
In another embodiment, the first diagnostic software acquisition request further includes an identifier of the terminal device;
correspondingly, after responding to the first diagnostic software acquisition request, the method also comprises the step of storing identification.
As one implementation, the identification is in the form of a serial number.
The server can subsequently determine whether the terminal equipment issues the universal module according to the storage record through the storage identifier so that the server can correspondingly select different processing modes.
After step S204 of sending the first target configuration data to the terminal device, the method further includes:
and receiving a second diagnosis software acquisition request from the terminal equipment, wherein the second diagnosis software acquisition request comprises the identification of the terminal equipment and second identification information of the second target vehicle.
Specifically, after receiving the second diagnostic software acquisition request, the second diagnostic software acquisition request is analyzed to obtain the identifier of the terminal device and the second identifier information of the second target vehicle.
And searching the identified storage record in response to the second diagnosis software acquisition request.
Specifically, the server searches for a storage record corresponding to the identifier in the database through the identifier, so that the server correspondingly selects different processing modes according to the storage record.
If the storage record is found, second target configuration data corresponding to the second identification information is found, and the second target configuration data comprises system data and functional data applicable to the vehicle type corresponding to the second target vehicle;
and sending the second target configuration data to the terminal equipment.
Wherein the terminal device that transmitted the second diagnostic software acquisition request and the terminal device that transmitted the first diagnostic software acquisition request are the same device. Correspondingly, when the first diagnostic software acquisition request is received, the server stores the identifier of the terminal device. Then the server searches the storage record of the identifier in a database, if the storage record of the identifier is found, the server determines that the universal data is issued to the terminal equipment, and only the target configuration data corresponding to the second identifier information, namely the second target configuration data, is searched without issuing the universal data; and then the server transmits the second target configuration data to the terminal equipment.
If the server does not successfully store the identifier of the terminal device when receiving the first diagnostic software acquisition request, and correspondingly, the server cannot search the storage record of the identifier in the database, namely cannot search the storage record, the server sends the general data to the terminal device again and stores the identifier.
For example, the server receives a second diagnostic software acquisition request from the same terminal device, and in response to the second diagnostic software acquisition request, analyzes the request to obtain a serial number of the terminal device and second identification information of a second target vehicle, where the second identification information includes a vehicle type: 2009 kouz LSGPC52U89 fxxxxxxx, wherein X represents 0-9. Then the server searches the storage record of the identifier of the terminal equipment, and then directly identifies the vehicle type of the second target vehicle from the second identifier information as follows: 2009 Cruze LSGPC52U89FXXXXX, then according to the vehicle type, searching target configuration data corresponding to the vehicle type, namely second target configuration data, wherein the second target configuration data comprises all system data corresponding to the vehicle type, specifically engine information, gearbox information, airbag information and ABS information, and functional data corresponding to each system, specifically code reading information, code clearing information, data flow information, action test information, online programming information and oil nozzle matching information, and then sending the second target configuration data to the terminal equipment.
In the embodiment, the storage record of the identifier is searched in response to the second diagnostic software acquisition request, and if the storage record is searched, the second target configuration data corresponding to the second identifier information is searched, so that the server can be prevented from repeatedly issuing the general data to the terminal equipment, the terminal equipment only needs to receive the configuration data corresponding to the target vehicle type, the data amount stored by the terminal equipment is further reduced, and the hardware cost of the terminal equipment is further reduced.
In another embodiment, before the step S203 of searching for the first target configuration data corresponding to the first identification information, the method further includes:
identifying first identification information in a first diagnostic software acquisition request;
and if the first identification information cannot be identified, sending prompt information to the terminal equipment, wherein the prompt information is used for indicating the terminal equipment to prompt a user to input the first identification information.
Generally, the server can identify the identification information of the target vehicle from the diagnostic software acquisition request, but sometimes the identification information cannot be identified, and at the moment, the user needs to input the identification information again, so that the failure of acquiring the diagnostic software data by the terminal equipment is avoided.
Specifically, when the identification information of the target vehicle cannot be recognized, the server sends prompt information to the terminal device, then the terminal device receives the prompt information, displays the prompt information, and then the user inputs the identification information again.
For example, the user may input the identification information by uploading a car logo picture or a parking space picture, or by handwriting.
In the embodiment, if the identification information cannot be recognized, the prompt information is sent to the terminal device, and the prompt information is used for indicating the terminal device to prompt the user to input the first identification information.
In another embodiment, after the step S204 of sending the first target configuration data to the terminal device, the method further includes:
receiving new user information from the terminal equipment;
judging whether the new user information meets a preset condition or not;
if yes, adding a new user.
The preset conditions are that the age of the new user is within a preset range, and the relationship between the new user and the user is a family member relationship.
Specifically, receiving new user information, analyzing the new user information to obtain the age of the new user and the relationship between the new user and the user, and then judging whether the age of the new user is within a preset range and whether the relationship between the new user and the user is a family member relationship by the server; and if the preset conditions are met, adding the new user by the server, and correspondingly establishing an account. And if the preset condition is not met, the server does not add the new user.
Illustratively, the predetermined range is 18 years (inclusive) to 65 years (inclusive), and the family membership includes an affinity, a blood affinity, or a health care relationship. The age of the new user is 25 years, the relationship with the user is a parent-child relationship, and correspondingly, the new user information comprises the identity card information of the new user and the relationship with the user. After receiving the new user information, the server analyzes the new user information to obtain the age of the new user and the relation between the new user and the user; and then judging that the age of the new user is between 18 years (inclusive) and 65 years (inclusive) according to a pre-stored auditing rule, wherein the relationship between the new user and the user is a family membership relationship, namely a preset condition is met, and adding the new user by the server.
The embodiment judges whether the new user information meets the preset condition by receiving the new user information from the terminal equipment; if yes, new users are added, information stored in the terminal equipment users can be protected, the new users are all people trusted by the users, meanwhile, data of each user are separately managed in a mode of adding the new users, and privacy of each user is protected.
FIG. 3 is a schematic flow chart diagram illustrating a vehicle diagnostic software configuration method according to another embodiment of the present application. By way of example and not limitation, the method is applied to a terminal device, and the terminal device can be a vehicle diagnosis device, and the method comprises the following steps:
s301: a first diagnostic software acquisition request is sent to the server, the first diagnostic software acquisition request including first identification information of the first target vehicle.
Specifically, when a user uses the terminal device to diagnose one target vehicle, a first diagnostic software acquisition request is sent to the server, so that the server performs corresponding processing according to the first diagnostic software acquisition request.
S302: and receiving the general data returned by the server in response to the diagnostic software acquisition request.
The generic data includes generic interface data and generic protocol data for the diagnostic software.
S303: and receiving first target configuration data from the server, wherein the first target configuration data comprises system data and function data applicable to a vehicle type corresponding to the first target vehicle.
The first target configuration data includes all system data corresponding to the model of the first target vehicle and function data corresponding to the system data.
S304: and generating first diagnosis software according to the general data and the first target configuration data, wherein the first diagnosis software is diagnosis software suitable for the vehicle type of the first target vehicle.
Specifically, the terminal device combines the general data with the first target configuration data to generate corresponding diagnosis software, the diagnosis software is a single-vehicle type diagnosis device and is only suitable for the vehicle type of the target vehicle, and then a user can use the diagnosis device on the terminal device to diagnose the target vehicle.
For example, the user has a vehicle as a first target vehicle, and the identification information of the target vehicle is kaffir LSGGA54Y6DHXXXXXX in 2013, which is the first identification information. The user inputs first identification information on the terminal device, the terminal device forms a first diagnosis software obtaining request according to the first identification information, and the first diagnosis software obtaining request is sent to the server, so that the server carries out corresponding processing according to the first diagnosis software obtaining request.
In the embodiment, the first diagnostic software acquisition request is sent to the server, the general data sent by the server and the system data and the functional data corresponding to the vehicle type of the target vehicle are received, and the corresponding diagnostic software is generated according to the general data and the target configuration data. The present embodiment stores data for configuring diagnostic software stored in a terminal device in a server, and designs data for configuring diagnostic software into general data and configuration data. When the terminal equipment uses the diagnosis software, the server issues data for configuring the diagnosis software according to the diagnosis software acquisition request sent by the terminal equipment, so that the terminal equipment only needs to store the data for configuring the diagnosis software corresponding to the identification information, the data quantity stored by the terminal equipment is reduced, and the hardware cost is reduced. And the data for configuring the diagnostic software is designed into general data and configuration data, which is beneficial to the management of various types of data.
In another embodiment, the first diagnostic software acquisition request further includes an identifier of the terminal device, the identifier being stored by the server after responding to the first diagnostic software acquisition request;
illustratively, the terminal device forms a first diagnostic software acquisition request according to the first target information and the identifier.
After the step S304 of generating the first diagnostic software, the method further includes:
and sending a second diagnosis software acquisition request to the server, wherein the second diagnosis software acquisition request comprises the identifier of the terminal equipment and second identification information of the second target vehicle.
Specifically, when the user continues to use the terminal device to diagnose another target vehicle, a second diagnostic software acquisition request is sent to the server, so that the server performs corresponding processing according to the second diagnostic software acquisition request.
And receiving second target configuration data returned by the server in response to the second diagnosis software acquisition request, wherein the second target configuration data comprises system data and function data applicable to the vehicle type corresponding to the second target vehicle.
The second target configuration data includes all system data corresponding to the vehicle type of the second target vehicle and function data corresponding to the system data.
And generating second diagnosis software according to the general data and the second target configuration data, wherein the second diagnosis software is suitable for the vehicle type of the second target vehicle.
Specifically, the terminal device combines the general data with the second target configuration data to generate corresponding diagnosis software, and then the user can use the diagnosis device on the terminal device to diagnose the target vehicle.
For example, the user has another vehicle, which is a second target vehicle, and the identification information of the target vehicle is 2009 kruetz LSGPC52U89fxxxxx, which is second identification information. And the terminal equipment forms a second diagnosis software acquisition request according to the second identification information and the identification of the terminal equipment, and sends the second diagnosis software acquisition request to the server so that the server performs corresponding processing according to the second diagnosis software acquisition request.
In the embodiment, the second diagnostic software acquisition request is sent to the server, the second diagnostic software acquisition request includes the identifier of the terminal device and the second identifier information of the second target vehicle, the second target configuration data returned by the server in response to the second diagnostic software acquisition request is received, and the second diagnostic software is generated according to the general data and the second target configuration data, so that after the terminal device receives the general data, the corresponding diagnostic software can be generated only by receiving the target configuration data corresponding to the identifier information, the data amount stored by the terminal device is further reduced, and the hardware cost of the terminal device is further reduced.
In another embodiment, after the step S303 of receiving the first target configuration data from the server, the method further includes:
and acquiring new user information and sending the new user information to the server.
Specifically, the family member of the user wants to use the terminal device, the user inputs the information of the family member on the terminal device, and the terminal device sends new user information to the server, so that the server performs corresponding processing according to the new user information.
In the embodiment, the new user information is sent to the server, so that the addition of the new user is realized, the information stored in the terminal equipment user can be protected, the new user is a person trusted by the user, and meanwhile, the data of each user is separately managed in a manner of adding the new user, so that the privacy of each user is protected.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Fig. 4 is a schematic structural diagram of a vehicle diagnostic software configuration apparatus provided in an embodiment of the present application, corresponding to the method described in the above embodiment applied to the server, and only the part related to the embodiment of the present application is shown for convenience of explanation.
As shown in fig. 4, the apparatus includes:
a first receiving unit 40 configured to receive a first diagnostic software acquisition request from a terminal device, the first diagnostic software acquisition request including first identification information of a first target vehicle;
a first sending unit 41, configured to send the general data to the terminal device in response to the first diagnostic software acquisition request;
the searching unit 42 is configured to search for first target configuration data corresponding to the first identification information, where the first target configuration data includes system data and function data applicable to a vehicle type corresponding to the first target vehicle;
a second sending unit 43, configured to send the first target configuration data to the terminal device.
In another embodiment, the search unit is specifically configured to determine a vehicle type of the first target vehicle according to the first identification information;
and searching first target configuration data corresponding to the vehicle type of the first target vehicle based on the corresponding relation between the preset vehicle type and the configuration data.
In another embodiment, the apparatus further comprises an identification unit,
the identification unit is used for identifying first identification information in the first diagnostic software acquisition request;
and the second sending unit is also used for sending prompt information to the terminal equipment, wherein the prompt information is used for indicating the terminal equipment to prompt the user to input the first identification information.
In another embodiment, the apparatus further comprises a setup unit,
the establishing unit is used for acquiring configuration data; and establishing a corresponding relation between the configuration data and the vehicle type.
In another embodiment, the apparatus further comprises a determining unit,
the first receiving unit is also used for receiving new user information from the terminal equipment;
the judging unit is used for judging whether the new user information meets the preset conditions or not; if yes, adding a new user.
In another embodiment, the first diagnostic software acquisition request further includes an identification of the terminal device.
The first receiving unit is further used for receiving a second diagnostic software acquisition request from the terminal equipment, wherein the second diagnostic software acquisition request comprises the identifier of the terminal equipment and second identifier information of a second target vehicle;
the searching unit is also used for storing the identification of the first diagnosis software acquisition request; and in response to a second diagnostic software acquisition request, searching for a storage record of the identifier;
the second target configuration data corresponding to the second identification information is searched if the storage record is searched, and the second target configuration data comprises system data and functional data applicable to the vehicle type corresponding to the second target vehicle;
and the second sending unit is also used for sending second target configuration data to the terminal equipment.
Fig. 5 is a schematic structural diagram of a vehicle diagnostic software configuration apparatus provided in an embodiment of the present application, corresponding to the method described in the above embodiment applied to the terminal device, and only the relevant parts to the embodiment of the present application are shown for convenience of explanation.
As shown in fig. 5, the apparatus includes:
a third sending unit 50, configured to send a first diagnostic software acquisition request to the server, where the first diagnostic software acquisition request includes first identification information of the first target vehicle;
a second receiving unit 51, configured to receive general data returned by the server in response to the first diagnostic software acquisition request; the system comprises a server, a first target configuration data acquisition module, a second target configuration data acquisition module, a first display module and a second display module, wherein the first target configuration data acquisition module is used for acquiring first target configuration data from the server;
the generating unit 52 is configured to generate first diagnostic software according to the general data and the first target configuration data, where the first diagnostic software is diagnostic software suitable for a vehicle type of the first target vehicle.
In another embodiment, the first diagnostic software acquisition request further includes an identification of the terminal device.
The third sending unit is further used for sending a second diagnosis software obtaining request to the server, wherein the second diagnosis software obtaining request comprises the identification of the terminal equipment and second identification information of a second target vehicle;
the second receiving unit is further used for receiving second target configuration data returned by the server in response to the second diagnostic software acquisition request, wherein the second target configuration data comprises system data and function data applicable to a vehicle type corresponding to a second target vehicle;
and the generating unit is also used for generating second diagnosis software according to the general data and the second target configuration data, wherein the second diagnosis software is diagnosis software suitable for the vehicle type of a second target vehicle.
In another embodiment, the apparatus further comprises an acquisition unit;
an acquisition unit configured to acquire new user information;
and the third sending unit is also used for sending the new user information to the server.
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 6, the electronic apparatus 6 of this embodiment includes: at least one processor 60 (only one shown in fig. 6), a memory 61, and a computer program 62 stored in the memory 61 and executable on the at least one processor 60, the steps of any of the various method embodiments described above being implemented when the computer program 62 is executed by the processor 60.
The electronic device 6 may be a vehicle terminal device or a computing device such as a cloud server, and the vehicle terminal device is a vehicle diagnostic device. The electronic device 6 may include, but is not limited to, a processor 60, a memory 61. Those skilled in the art will appreciate that fig. 6 is merely an example of the electronic device 6, and does not constitute a limitation of the electronic device 6, and may include more or less components than those shown, or combine some of the components, or different components, such as an input-output device, a network access device, etc.
The Processor 60 may be a Central Processing Unit (CPU), and the Processor 60 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 61 may in some embodiments be an internal storage unit of the electronic device 6, such as a hard disk or a memory of the electronic device 6. The memory 61 may also be an external storage device of the electronic device 6 in other embodiments, 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, which are provided on the electronic device 6. Further, the memory 61 may also include both an internal storage unit and an external storage device of the electronic device 6. The memory 61 is used for storing an operating system, an application program, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer program. The memory 61 may also be used to temporarily store data that has been output or is to be output.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.
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.
The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps in the above-mentioned method embodiments.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement 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 at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.
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/network device and method may be implemented in other ways. For example, the above-described apparatus/network device 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 implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. 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.
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. A vehicle diagnostic software configuration method is applied to a server, and comprises the following steps:
receiving a first diagnostic software acquisition request from a terminal device, wherein the first diagnostic software acquisition request contains first identification information of a first target vehicle;
responding to the first diagnostic software acquisition request, and sending general data to the terminal equipment;
searching first target configuration data corresponding to the first identification information, wherein the first target configuration data comprise system data and function data applicable to a vehicle type corresponding to the first target vehicle;
and sending the first target configuration data to the terminal equipment.
2. The method of claim 1, wherein finding the first target configuration data corresponding to the first identification information comprises:
determining the vehicle type of the first target vehicle according to the first identification information;
and searching first target configuration data corresponding to the vehicle type of the first target vehicle based on the corresponding relation between the preset vehicle type and the configuration data.
3. The method of claim 1, wherein prior to finding the first target configuration data corresponding to the first identification information, the method further comprises:
identifying first identification information in the first diagnostic software acquisition request;
and if the first identification information cannot be identified, sending prompt information to the terminal equipment, wherein the prompt information is used for indicating the terminal equipment to prompt a user to input the first identification information.
4. The method of claim 1, wherein prior to receiving the first diagnostic software acquisition request from the terminal device, the method further comprises:
acquiring the configuration data;
and establishing a corresponding relation between the configuration data and the vehicle type.
5. The method of any of claims 1-4, wherein after sending the first target configuration data to the terminal device, the method further comprises:
receiving new user information from the terminal equipment;
judging whether the new user information meets a preset condition or not;
if yes, adding a new user.
6. The method of any of claims 1-4, wherein the first diagnostic software acquisition request further includes an identification of the terminal device;
correspondingly, after responding to the first diagnostic software acquisition request, the method further comprises the step of storing the identification;
after sending the first target configuration data to the terminal device, the method further includes:
receiving a second diagnostic software acquisition request from the terminal equipment, wherein the second diagnostic software acquisition request comprises an identifier of the terminal equipment and second identifier information of a second target vehicle;
searching the storage record of the identifier in response to the second diagnostic software acquisition request;
if the storage record is found, second target configuration data corresponding to the second identification information is found, wherein the second target configuration data comprises system data and functional data applicable to a vehicle type corresponding to the second target vehicle;
and sending the second target configuration data to the terminal equipment.
7. A vehicle diagnosis software configuration method is applied to a terminal device, and comprises the following steps:
sending a first diagnosis software acquisition request to a server, wherein the first diagnosis software acquisition request comprises first identification information of a first target vehicle;
receiving general data returned by the server in response to the first diagnostic software acquisition request;
receiving first target configuration data from the server, wherein the first target configuration data comprises system data and function data applicable to a vehicle type corresponding to the first target vehicle;
and generating first diagnosis software according to the general data and the first target configuration data, wherein the first diagnosis software is suitable for the vehicle type of the first target vehicle.
8. The method of claim 7, wherein the first diagnostic software acquisition request further includes an identification of the terminal device, the identification being stored by the server after responding to the first diagnostic software acquisition request;
after receiving the first target configuration data from the server, the method further comprises:
sending a second diagnostic software acquisition request to a server, wherein the second diagnostic software acquisition request comprises the identifier of the terminal equipment and second identifier information of a second target vehicle;
receiving second target configuration data returned by the server in response to the second diagnostic software acquisition request, wherein the second target configuration data comprises system data and function data applicable to a vehicle type corresponding to the second target vehicle;
and generating second diagnosis software according to the general data and the second target configuration data, wherein the second diagnosis software is suitable for the vehicle type of the second target vehicle.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of any of claims 1 to 6 or claims 7 to 8 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 6 or 7 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111002191.1A CN113703868A (en) | 2021-08-30 | 2021-08-30 | Vehicle diagnostic software configuration method, electronic device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111002191.1A CN113703868A (en) | 2021-08-30 | 2021-08-30 | Vehicle diagnostic software configuration method, electronic device and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113703868A true CN113703868A (en) | 2021-11-26 |
Family
ID=78656621
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111002191.1A Pending CN113703868A (en) | 2021-08-30 | 2021-08-30 | Vehicle diagnostic software configuration method, electronic device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113703868A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114090133A (en) * | 2021-11-30 | 2022-02-25 | 深圳市元征科技股份有限公司 | Application program configuration method and device, electronic equipment and storage medium |
| CN114425999A (en) * | 2021-12-27 | 2022-05-03 | 深圳市元征科技股份有限公司 | Resistance configuration method and apparatus for diagnostic device, electronic device, and medium |
| CN114615105A (en) * | 2022-04-02 | 2022-06-10 | 深圳市元征科技股份有限公司 | Data transmission method, device, electronic equipment, system and storage medium |
| CN116300780A (en) * | 2022-09-07 | 2023-06-23 | 广州汽车集团股份有限公司 | Component configuration method, device, electronic equipment and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104932480A (en) * | 2015-04-29 | 2015-09-23 | 深圳市元征软件开发有限公司 | Automobile diagnostic system design method and apparatus |
| CN109471652A (en) * | 2018-10-24 | 2019-03-15 | 北汽福田汽车股份有限公司 | Method for updating program and its system, the car-mounted terminal and electronic equipment of vehicle |
| CN109491671A (en) * | 2018-10-19 | 2019-03-19 | 深圳市轱辘汽车维修技术有限公司 | Diagnostic software method for down loading, device, terminal device and storage medium |
| US20190347876A1 (en) * | 2018-05-10 | 2019-11-14 | Mahle International Gmbh | Apparatuses, systems, and methods for remotely capturing automotive vehicle diagnostic information, monitoring, and controlling |
| US20190367042A1 (en) * | 2018-05-31 | 2019-12-05 | Hyundai Autron Co., Ltd. | System for diagnosing software for vehicle and operating method thereof |
| CN111177168A (en) * | 2019-12-26 | 2020-05-19 | 优信拍（北京）信息科技有限公司 | Vehicle detection method and device |
| CN111474921A (en) * | 2020-04-29 | 2020-07-31 | 深圳市元征科技股份有限公司 | Configuration method of automobile diagnosis software and related equipment |
| CN112034824A (en) * | 2020-09-04 | 2020-12-04 | 深圳市云伽智能技术有限公司 | Automobile diagnosis method, device, equipment and computer readable storage medium |
| CN112181411A (en) * | 2020-09-25 | 2021-01-05 | 深圳市元征科技股份有限公司 | Menu generation method, menu generation device and diagnosis equipment |
-
2021
- 2021-08-30 CN CN202111002191.1A patent/CN113703868A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104932480A (en) * | 2015-04-29 | 2015-09-23 | 深圳市元征软件开发有限公司 | Automobile diagnostic system design method and apparatus |
| US20190347876A1 (en) * | 2018-05-10 | 2019-11-14 | Mahle International Gmbh | Apparatuses, systems, and methods for remotely capturing automotive vehicle diagnostic information, monitoring, and controlling |
| US20190367042A1 (en) * | 2018-05-31 | 2019-12-05 | Hyundai Autron Co., Ltd. | System for diagnosing software for vehicle and operating method thereof |
| CN109491671A (en) * | 2018-10-19 | 2019-03-19 | 深圳市轱辘汽车维修技术有限公司 | Diagnostic software method for down loading, device, terminal device and storage medium |
| CN109471652A (en) * | 2018-10-24 | 2019-03-15 | 北汽福田汽车股份有限公司 | Method for updating program and its system, the car-mounted terminal and electronic equipment of vehicle |
| CN111177168A (en) * | 2019-12-26 | 2020-05-19 | 优信拍（北京）信息科技有限公司 | Vehicle detection method and device |
| CN111474921A (en) * | 2020-04-29 | 2020-07-31 | 深圳市元征科技股份有限公司 | Configuration method of automobile diagnosis software and related equipment |
| CN112034824A (en) * | 2020-09-04 | 2020-12-04 | 深圳市云伽智能技术有限公司 | Automobile diagnosis method, device, equipment and computer readable storage medium |
| CN112181411A (en) * | 2020-09-25 | 2021-01-05 | 深圳市元征科技股份有限公司 | Menu generation method, menu generation device and diagnosis equipment |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114090133A (en) * | 2021-11-30 | 2022-02-25 | 深圳市元征科技股份有限公司 | Application program configuration method and device, electronic equipment and storage medium |
| CN114425999A (en) * | 2021-12-27 | 2022-05-03 | 深圳市元征科技股份有限公司 | Resistance configuration method and apparatus for diagnostic device, electronic device, and medium |
| CN114425999B (en) * | 2021-12-27 | 2024-04-26 | 深圳市元征科技股份有限公司 | Resistance configuration method and device of diagnostic equipment, electronic equipment and medium |
| CN114615105A (en) * | 2022-04-02 | 2022-06-10 | 深圳市元征科技股份有限公司 | Data transmission method, device, electronic equipment, system and storage medium |
| CN114615105B (en) * | 2022-04-02 | 2024-04-02 | 深圳市元征科技股份有限公司 | Data transmission method, device, electronic equipment, system and storage medium |
| CN116300780A (en) * | 2022-09-07 | 2023-06-23 | 广州汽车集团股份有限公司 | Component configuration method, device, electronic equipment and storage medium |
| CN116300780B (en) * | 2022-09-07 | 2024-01-23 | 广州汽车集团股份有限公司 | Component configuration method, device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113703868A (en) | Vehicle diagnostic software configuration method, electronic device and readable storage medium | |
| CN110162009B (en) | Fault diagnosis method, information determination method, corresponding device and equipment | |
| 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 | |
| CN109885037B (en) | Vehicle diagnosis method and related equipment | |
| CN111813095A (en) | Vehicle diagnosis method, device and medium | |
| CN111598850A (en) | Data auditing method and system | |
| CN111211929A (en) | Fault positioning method, fault positioning device, control equipment and intelligent equipment | |
| CN109636424A (en) | A kind of management method and relevant device of information of vehicles | |
| CN113642575A (en) | Vehicle function detection method and device, electronic equipment and storage medium | |
| CN108228744B (en) | Vehicle diagnosis data management method and device | |
| CN113872967A (en) | Vehicle information transmission method and device, electronic equipment and storage medium | |
| CN113114659A (en) | Diagnostic equipment detection method and device, terminal equipment and storage medium | |
| CN112184946A (en) | Vehicle data reading method and related equipment | |
| CN111693294A (en) | Vehicle detection method and device, terminal equipment and storage medium | |
| CN110189434B (en) | Vehicle safety checking method and related equipment thereof | |
| CN112306041A (en) | Vehicle configuration information writing method and device and electronic equipment | |
| CN114531340B (en) | Log acquisition method and device, electronic equipment, chip and storage medium | |
| CN109962895B (en) | Method and system for updating automobile instrument interface, server and storage medium | |
| CN113934198A (en) | Vehicle diagnosis method, vehicle diagnosis device, electronic device, and storage medium | |
| CN111242256B (en) | Information verification method, device and terminal | |
| CN113395316B (en) | Information processing apparatus and information processing system | |
| CN113886302A (en) | Serial port number obtaining method and device of application equipment, terminal equipment and storage medium | |
| CN113342430A (en) | Fault code processing method and device, terminal equipment and readable 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 |