Disclosure of Invention
The embodiment of the application provides a vehicle type diagnosis authority management method and related equipment, which improve the control strength of a host factory on subordinate clients and improve the working efficiency of the host factory.
In a first aspect, an embodiment of the present application provides a vehicle type diagnosis authority management method, which may include:
acquiring a vehicle type diagnosis authority list corresponding to identification information from a server according to the identification information of a client, wherein the vehicle type diagnosis authority list comprises authority data of N vehicle types, and N is an integer greater than or equal to 0; determining M vehicle types which have diagnosis authority and correspond to the client side in the N vehicle types according to the authority data of the N vehicle types, wherein M is an integer larger than or equal to 0, and M is smaller than or equal to N; and providing diagnosis entries corresponding to the M vehicle types in the client according to the M vehicle types with the diagnosis authority, wherein the diagnosis entries are used for providing diagnosis services for vehicles of the corresponding vehicle types.
According to the embodiment of the application, different devices of the operating client are identified through the server of the host factory, and the corresponding diagnosis authority is accurately distributed according to the device information; the client receives the authority data from the server, confirms the information such as the number and the category of the vehicle type diagnosis authority owned by the client, and provides a diagnosis entrance using a corresponding diagnosis software package for the user after confirming the diagnosis authority. The host factory can set the use authority of the client to the diagnosis software package through the server of the host factory, controls the user to diagnose the vehicle of the corresponding vehicle type through the vehicle type diagnosis authority owned by the client, effectively manages the diagnosis authority of the client, and improves the working efficiency of the host factory.
In one possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes check data of a corresponding vehicle type; the determining, according to the authority data of the N vehicle types, M vehicle types having diagnosis authority corresponding to the client in the N vehicle types may include: verifying the verification data of the N vehicle types; and determining the vehicle types corresponding to the M verification data which are successfully verified as M vehicle types which are corresponding to the client and have the diagnosis authority.
In one possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes authority indication information of a corresponding vehicle type; the determining, according to the authority data of the N vehicle types, M vehicle types having diagnosis authority corresponding to the client in the N vehicle types may include: determining authority indicating information of the N vehicle types according to the authority data of the N vehicle types, wherein the authority indicating information is used for indicating whether the client side has the diagnosis authority of the corresponding vehicle type; and determining M vehicle types with diagnosis authorities corresponding to the client side in the N vehicle types according to the authority indication information of the N vehicle types.
In one possible implementation, the method further includes:
storing the vehicle type diagnosis authority list; under the condition that the client is in networking failure, determining M vehicle types with diagnosis permission corresponding to the client in the N vehicle types according to permission data of the N vehicle types in the vehicle type diagnosis permission list; wherein M is an integer greater than or equal to 0, and M is less than or equal to N; and providing diagnosis entries corresponding to the M vehicle types in the client according to the M vehicle types with the diagnosis authority, wherein the diagnosis entries are used for providing diagnosis services for vehicles of the corresponding vehicle types.
In a possible implementation manner, the identification information of the client includes an identity code of a device where the client is located.
In a second aspect, an embodiment of the present application provides a vehicle type diagnosis authority management apparatus, which may include:
the system comprises an acquisition unit, a storage unit and a processing unit, wherein the acquisition unit is used for acquiring a vehicle type diagnosis authority list corresponding to identification information from a server according to the identification information of a client, the vehicle type diagnosis authority list comprises authority data of N vehicle types, and N is an integer greater than or equal to 0; the first confirming unit is used for determining M vehicle types which have diagnosis authorities and correspond to the client side in the N vehicle types according to authority data of the N vehicle types, wherein M is an integer larger than or equal to 0, and M is smaller than or equal to N; the first diagnosis unit is used for providing diagnosis entries corresponding to the M vehicle types in the client according to the M vehicle types with the diagnosis authority, and the diagnosis entries are used for providing diagnosis services for vehicles of the corresponding vehicle types.
According to the embodiment of the application, different devices of the operating client are identified through the server of the host factory, and the corresponding diagnosis authority is accurately distributed according to the device information; the client receives the authority data from the server and confirms the number, the category and other information of the vehicle type diagnosis authority owned by the client; after confirming the diagnostic authority, the client provides a diagnostic portal to the user for using the corresponding diagnostic software package. The host factory can set the use authority of the client to the diagnosis software package through the server, namely, a user can only diagnose vehicles of corresponding vehicle types on the client with the diagnosis authority of certain vehicle types, the diagnosis authority of the client is effectively managed, and the working efficiency of the host factory is improved.
In one possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes check data of a corresponding vehicle type; the first confirming unit is specifically configured to: verifying the verification data of the N vehicle types; and determining the vehicle types corresponding to the M verification data which are successfully verified as M vehicle types which are corresponding to the client and have the diagnosis authority.
In one possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes authority indication information of a corresponding vehicle type; the first confirming unit is specifically configured to: determining authority indicating information of the N vehicle types according to the authority data of the N vehicle types, wherein the authority indicating information is used for indicating whether the client side has the diagnosis authority of the corresponding vehicle type; and determining M vehicle types with diagnosis authorities corresponding to the client side in the N vehicle types according to the authority indication information of the N vehicle types.
In one possible implementation, the apparatus further includes:
the storage unit is used for storing the vehicle type diagnosis authority list; the second confirmation unit is used for determining M vehicle types with diagnosis authorities corresponding to the client side from the N vehicle types according to authority data of the N vehicle types in the vehicle type diagnosis authority list under the condition that the client side fails in networking; wherein M is an integer greater than or equal to 0, and M is less than or equal to N; and the second diagnosis unit is used for providing diagnosis entries corresponding to the M vehicle types in the client according to the M vehicle types with the diagnosis authority, and the diagnosis entries are used for providing diagnosis services for vehicles of the corresponding vehicle types.
In a possible implementation manner, the identification information of the client includes an identity code of a device where the client is located.
In a third aspect, the present application provides a vehicle type diagnosis authority management device, which may include a storage component, a communication component, and a processing component, where the storage component, the communication component, and the processing component are connected to each other, where the storage component is used to store data processing codes, and the communication component is used to perform information interaction with an external device; the processing element is configured to invoke the program code to perform the method according to the first aspect, which is not described herein in detail.
In a fourth aspect, the present application provides a computer storage medium for storing computer software instructions for the vehicle type diagnosis authority management device provided in the second aspect, which may include a program designed to execute the above aspects.
In a fifth aspect, the present application provides a computer program, which may include instructions, when the computer program is executed by a computer, the computer may execute the procedures described in any one of the methods in the first aspect.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
The terms "first," "second," and the like in the description and claims of the present application and in the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments. The technical scheme of the embodiment of the application can be applied to the fields of data processing, cluster analysis and the like. When the fields and the scenes of the method and the device are different, the names of specific equipment and places in the embodiment of the application are also different.
First, some terms in the present application are explained so as to be easily understood by those skilled in the art.
(1) A host computer factory, also called an automobile complete vehicle or a complete machine manufacturing enterprise, refers to an automobile manufacturing factory on a table, such as the public, a bmw, and the like, relative to a part supplier behind the scenes; such manufacturers generally have the engine core technology in hand and outsource other non-core services to other companies within the automotive industry chain; to distinguish from other common manufacturers in the automotive industry, the automotive industry is referred to as a host factory, but the host factory is not just an engine factory but rather an automotive company in the true sense.
(2) A Client (Client), or called Client, refers to a program corresponding to a server and providing local services to clients. Except some application programs which only run locally, the application programs are generally installed on common clients and need to be operated with a server side in a matched mode, such as a web browser used by the world wide web, an email client used for receiving and sending emails, client software for instant messaging and the like; for this kind of application, a corresponding server and a service program in the network are required to provide a corresponding service; thus, at the client and server sides, a specific communication connection needs to be established to ensure the normal operation of the application program.
(3) String (String), is a String of characters consisting of numbers, letters, underlines. Which is the type of data representing text in a programming language. In programming, a string is a continuous sequence of symbols or values, such as a string of symbols (a string of characters) or a string of binary digits (a string of binary digits). Usually, the whole string is used as an operation object, such as: searching a certain substring in the string, obtaining a substring, inserting a substring at a certain position of the string, deleting a substring and the like. The two most basic storage modes for strings are sequential storage and linked storage.
In the following, a description is first given of one of the system architectures on which the embodiments of the present application are based, and the vehicle type diagnosis authority management method proposed in the present application can be applied to the system architecture. Referring to fig. 1, fig. 1 is a schematic diagram of a system architecture for vehicle type diagnosis authority management according to an embodiment of the present disclosure, as shown in fig. 1, the system architecture includes a server, a client, and a vehicle corresponding to a vehicle type; in fig. 1, a group of servers and K clients are taken as an example, where K is an integer greater than or equal to 1; the embodiment of the application does not limit the equipment for operating the client and the number of the clients; wherein,
the client can provide a diagnosis entrance of a corresponding vehicle type for a user according to the diagnosis authority, and can execute the content of the method embodiment in any one of the first aspect; for example: acquiring a vehicle type diagnosis authority list corresponding to identification information from a server according to the identification information of a client, wherein the vehicle type diagnosis authority list comprises authority data of N vehicle types; determining M vehicle types with diagnosis authority corresponding to the client side in the N vehicle types according to the authority data of the N vehicle types; and providing diagnosis entries corresponding to the M vehicle types in the client according to the M vehicle types with the diagnosis authority.
The server may be a single server or a group of servers. The number of servers is not limited in the embodiments of the present application. The server can receive the vehicle type diagnosis software package uploaded by the host factory and can provide the vehicle type diagnosis software package to the client through the network under the condition of network connection; the server can determine authority data of N vehicle types in the vehicle type diagnosis authority list; determining M vehicle types with diagnosis authority corresponding to the client side in the N vehicle types according to the identification information of the client side; and configuring the authority data of the M vehicle types according to the related authority information of the client. Examples of application scenarios are, for example: the user can run the client on the personal computer PC, and select and download the required vehicle type diagnosis software package from the server to diagnose the corresponding vehicle. The server of the host factory can conveniently push the latest diagnosis software package to the client through the network, so that after-sale service can be better carried out.
The vehicle type corresponds to a vehicle, in the figure, for example, one vehicle corresponds to one vehicle type, each client side can have diagnosis authorities of a plurality of vehicle types, and the diagnosis authorities of the vehicle types of different client sides can be configured by a server. The vehicle type diagnosis authority owned by different clients may be the same or different. In the figure, one client side has one or more vehicle type diagnosis authorities as an example, and the number of vehicle types of which the client side has the diagnosis authorities is not limited in the embodiment of the application. Specific vehicle types, such as: small-sized vehicle, mini-sized vehicle, compact vehicle, medium vehicle, high-grade vehicle, luxury vehicle, sedan vehicle, CDV vehicle, MPV vehicle, SUV vehicle, etc. Among them, for example, the gallop brand includes the following models: gallop viano (mpv), gallop CLS (sports car), gallop SLK (sports car), gallop CLK convertible sports car (sports car), gallop S class car (car), gallop E class car (car), gallop C class car (car), etc.
It is to be understood that the illustration in fig. 1 is merely an exemplary implementation of the embodiments of the present application. The system architecture in the embodiments of the present application may include, but is not limited to, the above system architecture.
The following specifically analyzes and solves the technical problems proposed in the present application in combination with the above system architecture and the embodiments of the vehicle type diagnosis authority management method provided in the present application.
Referring to fig. 2, fig. 2 is a schematic flowchart of a vehicle type diagnosis authority management method according to an embodiment of the present disclosure, where the vehicle type diagnosis authority management method can be applied to a vehicle type diagnosis authority management system (including the above-mentioned architecture). The vehicle type diagnosis authority management system includes a client and a server, which will be described below with reference to fig. 2, taking the client as an execution subject as an example, from a single side of the client, and the method may include the following steps S201 to S203.
Step S201: and acquiring a vehicle type diagnosis authority list corresponding to the identification information from a server according to the identification information of the client, wherein the vehicle type diagnosis authority list comprises authority data of N vehicle types.
Specifically, the client acquires a vehicle type diagnosis authority list corresponding to identification information from the server according to the identification information of the client; different clients correspond to different identification information, and the obtained authority data of N vehicle types in the authority list are configured by the server; wherein N is an integer greater than or equal to 0. Optionally, the vehicle type diagnosis permission list may further include a vehicle type name and a vehicle type version number corresponding to the vehicle type name. Optionally, the client acquires the diagnosis permission list from the server in real time under the networking condition, and updates the diagnosis permission list stored in the local server, so that the diagnosis permission of the client in the offline state can be accurately controlled.
In a possible implementation manner, the identification information of the client may include an identification code of a device where the client is located, a Media Access Control (MAC) address of the device where the client is located, and the like. For example: installing the client on a computer, wherein the client uploads a local area network address, a hardware identity Identification (ID) number and the like of the computer where the client is located to a server and serves as identification information of the client; the hardware ID may include an ID of a motherboard, an ID of a Central Processing Unit (CPU), and the like.
Step S202: and determining M vehicle types with diagnosis authority corresponding to the client side in the N vehicle types according to the authority data of the N vehicle types.
Specifically, after acquiring authority data of N vehicle types in the vehicle type diagnosis authority list, the client determines which of the N vehicle types the client has the diagnosis authority according to the authority data of the N vehicle types. Wherein M represents the number of vehicle types with diagnosis authority, M is an integer greater than or equal to 0, and M is less than or equal to N. Alternatively, the rights data may be an encrypted string.
Four ways of confirming the vehicle type diagnosis authority owned by the client are listed below.
In a possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes check data of a corresponding vehicle type. The determining, according to the authority data of the N vehicle types, M vehicle types having diagnosis authority corresponding to the client in the N vehicle types may include: verifying the verification data of the N vehicle types; and determining the vehicle types corresponding to the M verification data which are successfully verified as M vehicle types which are corresponding to the client and have the diagnosis authority. Taking the authority data as a character string as an example: the server encrypts a character string containing the vehicle type information corresponding to the client and the diagnosis authority of the vehicle type and sends the encrypted character string to the corresponding client; the client decrypts the character string (obtains the vehicle type information), and confirms the vehicle type diagnosis authority (confirms the legal authority of the corresponding vehicle type). Optionally, when the encrypted character string is decrypted successfully to obtain the version number or the name of a certain vehicle type, determining that the vehicle type has the diagnosis authority; and when the value obtained by decrypting the encrypted character string is false, determining that the vehicle model does not have the diagnosis authority.
In one possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes authority indication information of a corresponding vehicle type; the determining, according to the authority data of the N vehicle types, M vehicle types having diagnosis authority corresponding to the client in the N vehicle types may include: determining authority indicating information of the N vehicle types according to the authority data of the N vehicle types, wherein the authority indicating information is used for indicating whether the client side has the diagnosis authority of the corresponding vehicle type; and determining M vehicle types with diagnosis authorities corresponding to the client side in the N vehicle types according to the authority indication information of the N vehicle types. Taking the authority data as a character string as an example: the client obtains information of all current vehicle types of the host factory sent by the server, wherein the vehicle type information comprises vehicle type information and character strings corresponding to the vehicle types. The authority indication information is a character of a certain bit of the character string, and if the character is 1, the diagnostic authority of the corresponding vehicle type is confirmed; if the character is 0, it is confirmed that there is no diagnosis authority of the corresponding vehicle type. The embodiment of the present application does not limit the form of the authority indication information.
In a possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes an encryption manner and authority information; the determining, according to the authority data of the N vehicle types, M vehicle types having diagnosis authority corresponding to the client in the N vehicle types may include: decrypting and acquiring the qualification of acquiring the authority information of the N vehicle types according to the encryption modes of the N vehicle types; and determining M vehicle types which have diagnosis authority and correspond to the client side in the N vehicle types according to the qualification. Taking the authority data as a character string as an example: the client decrypts the authority data to obtain the qualification of obtaining the vehicle type information; and determining the diagnostic authority of the vehicle type owned by the user according to the qualification.
In a possible implementation manner, the client directly confirms that the client has the diagnosis permission of the N vehicle types according to the permission data of the N vehicle types received from the server, that is, the server only sends the permission data corresponding to the vehicle types which can be diagnosed by the client to the client.
Step S203: and providing diagnosis entries corresponding to the M vehicle types in the client according to the M vehicle types with the diagnosis authority.
Specifically, after confirming M vehicle types with diagnosis authority, the client may provide a diagnosis entry corresponding to a vehicle conforming to any one of the M vehicle types to the user, where the diagnosis entry is used to provide a diagnosis service for the vehicle of the corresponding vehicle type, and includes instructing the client to call a diagnosis software package of the corresponding vehicle type to perform vehicle diagnosis, and the like. For example: and the client displays diagnosis entries of the M vehicle types, and the user selects the diagnosis entries to perform diagnosis operation according to the vehicle which needs to be diagnosed actually.
By implementing the embodiment of the application, the host factory identifies different devices of the operating client by using the server, and accurately allocates the corresponding diagnosis authority according to the device information; the client receives the authority data from the server and confirms the number, the category and other information of the vehicle type diagnosis authority owned by the client; after confirming the diagnostic authority, the client provides a diagnostic portal to the user for using the corresponding diagnostic software package. The host factory can set the use authority of the client to the diagnosis software package through the server, namely, a user can only diagnose vehicles of corresponding vehicle types on the client with the diagnosis authority of certain vehicle types, the diagnosis authority of the client is effectively managed, and the working efficiency of the host factory is improved.
Fig. 3 is a schematic flow diagram of another vehicle type diagnosis authority management method provided in an embodiment of the present application, where the vehicle type diagnosis authority management method may be applied to a vehicle type diagnosis authority management system (including the above-mentioned architecture). The vehicle type diagnosis authority management system comprises a client and a server, and will be described from a single side of the client by taking the client as an execution subject as an example with reference to fig. 3, the method may include the following steps S301 to S306; optionally, step S304, step S305, and step S306 may be further included. The specific contents and corresponding descriptions of step S301, step S302, and step S303 refer to step S201, step S202, and step S203 in the embodiment shown in fig. 2; the contents of the execution of step S305 and step S306 can also be referred to step S202 and step S203, respectively.
Step S301: and acquiring a vehicle type diagnosis authority list corresponding to the identification information from a server according to the identification information of the client, wherein the vehicle type diagnosis authority list comprises authority data of N vehicle types.
Step S302: and determining M vehicle types with diagnosis authority corresponding to the client side in the N vehicle types according to the authority data of the N vehicle types.
Step S303: and providing diagnosis entries corresponding to the M vehicle types in the client according to the M vehicle types with the diagnosis authority.
Step S304: and storing the vehicle type diagnosis authority list.
Specifically, under the condition that a client is connected with a network, when the client obtains the vehicle type diagnosis permission list, the vehicle type diagnosis permission list is stored. In the case that the client cannot normally connect to the network, since the vehicle type diagnosis authority list obtained from the server is saved immediately before the network connection is disconnected, the confirmation of the vehicle type diagnosis authority and the provision of the diagnosis entry are performed according to the list. The condition that the network cannot be normally connected may include: the client cannot be connected with the network; the client can be connected with the network but the uploading and downloading speed cannot meet the requirement and the like.
Optionally, the client may store the vehicle type diagnosis permission list through the configuration file.
Step S305: and under the condition that the client is in networking failure, determining M vehicle types with diagnosis authority corresponding to the client in the N vehicle types according to the authority data of the N vehicle types in the vehicle type diagnosis authority list.
Specifically, in the case of networking failure, the client side is controlled by authority data in a saved vehicle type diagnosis authority list. And determining M vehicle types of which the client has the diagnosis authority according to the authority data of the N vehicle types in the vehicle type diagnosis authority list, namely the client can possibly diagnose part or all of the vehicle types in the N vehicle types.
Step S306: and providing diagnosis entries corresponding to the M vehicle types in the client according to the M vehicle types with the diagnosis authority.
Specifically, the client may provide a diagnosis portal corresponding to a vehicle type to the user through an output device such as a display, and the diagnosis portal is used for providing a diagnosis service for a vehicle of the corresponding vehicle type. Wherein M is an integer greater than or equal to 0, and M is less than or equal to N.
By implementing the embodiment of the application, the host factory identifies different devices of the operating client by using the server, and accurately allocates the corresponding diagnosis authority according to the device information; the client receives the authority data from the server and confirms the number, the category and other information of the vehicle type diagnosis authority owned by the client; after confirming the diagnostic authority, the client provides a diagnostic portal to the user for using the corresponding diagnostic software package. The host factory can set the use authority of the client to the diagnosis software package through the server, namely, a user can only diagnose vehicles of corresponding vehicle types on the client with the diagnosis authority of certain vehicle types, the diagnosis authority of the client is effectively managed, and the working efficiency of the host factory is improved.
The method of the embodiments of the present application is explained in detail above, and the related apparatus of the embodiments of the present application is provided below.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a vehicle type diagnosis authority management device according to an embodiment of the present application, where the log uploading device 04 may include: an acquisition unit 401, a first confirmation unit 402 and a first diagnosis unit 403.
The obtaining unit 401 is configured to obtain, from a server, a vehicle type diagnosis permission list corresponding to identification information according to the identification information of a client, where the vehicle type diagnosis permission list includes permission data of N vehicle types, where N is an integer greater than or equal to 0.
A first determining unit 402, configured to determine, according to the authority data of the N vehicle types, M vehicle types that have diagnosis authority and correspond to the client, from the N vehicle types, where M is an integer greater than or equal to 0, and M is less than or equal to N.
A first diagnosing unit 403, configured to provide, in the client, diagnosis entries corresponding to M vehicle types according to the M vehicle types with diagnosis permissions, where the diagnosis entries are used to provide diagnosis services for vehicles of the corresponding vehicle types.
In a possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes check data of a corresponding vehicle type. The first confirming unit 402 is specifically configured to: verifying the verification data of the N vehicle types; and determining the vehicle types corresponding to the M verification data which are successfully verified as M vehicle types which are corresponding to the client and have the diagnosis authority.
In one possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes authority indication information of a corresponding vehicle type; the first confirming unit 402 is specifically configured to: determining authority indicating information of the N vehicle types according to the authority data of the N vehicle types, wherein the authority indicating information is used for indicating whether the client side has the diagnosis authority of the corresponding vehicle type; and determining M vehicle types with diagnosis authorities corresponding to the client side in the N vehicle types according to the authority indication information of the N vehicle types.
By implementing the embodiment of the application, the host factory identifies different devices of the operating client by using the server, and accurately allocates the corresponding diagnosis authority according to the device information; the client receives the authority data from the server and confirms the number, the category and other information of the vehicle type diagnosis authority owned by the client; after confirming the diagnostic authority, the client provides a diagnostic portal to the user for using the corresponding diagnostic software package. The host factory can set the use authority of the client to the diagnosis software package through the server, namely, a user can only diagnose vehicles of corresponding vehicle types on the client with the diagnosis authority of certain vehicle types, the diagnosis authority of the client is effectively managed, and the working efficiency of the host factory is improved.
It should be noted that, for the functions of each functional unit of the vehicle type diagnosis authority management apparatus 04 described in the embodiment of the apparatus of the present application, reference may be made to the description related to the vehicle type diagnosis authority management method in the embodiment of the method described in fig. 2, and details are not described here again. When the execution sequence of each unit is changed, the novelty and the novelty of the application are not influenced, the execution sequence of each unit of the classification device of the maintenance factory is not limited by the application.
In the above description of a related apparatus of the embodiment of the present application shown in fig. 4, another related apparatus of the embodiment of the present application is described below, please refer to fig. 5, fig. 5 is a schematic structural diagram of another vehicle type diagnosis authority management apparatus provided in the embodiment of the present application, and the log uploading apparatus 05 may include: an acquisition unit 501, a first confirmation unit 502, a first diagnosis unit 503, a storage unit 504, a second confirmation unit 505, and a second diagnosis unit 506. Among them, the storage unit 504, the second confirmation unit 505, and the second diagnosis unit 506 are optional units.
The obtaining unit 501 is configured to obtain a vehicle type diagnosis permission list corresponding to identification information from a server according to the identification information of a client, where the vehicle type diagnosis permission list includes permission data of N vehicle types, where N is an integer greater than or equal to 0.
A first determining unit 502, configured to determine, according to the authority data of the N vehicle types, M vehicle types that have diagnosis authorities and correspond to the client among the N vehicle types, where M is an integer greater than or equal to 0, and M is less than or equal to N.
A first diagnosing unit 503, configured to provide, in the client, diagnosis entries corresponding to the M vehicle types according to the M vehicle types with the diagnosis authority, where the diagnosis entries are used to provide a diagnosis service for vehicles of the corresponding vehicle types.
In a possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes check data of a corresponding vehicle type. The first confirming unit 502 is specifically configured to: verifying the verification data of the N vehicle types; and determining the vehicle types corresponding to the M verification data which are successfully verified as M vehicle types which are corresponding to the client and have the diagnosis authority.
In one possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes authority indication information of a corresponding vehicle type; the first confirming unit 502 is specifically configured to: determining authority indicating information of the N vehicle types according to the authority data of the N vehicle types, wherein the authority indicating information is used for indicating whether the client side has the diagnosis authority of the corresponding vehicle type; and determining M vehicle types with diagnosis authorities corresponding to the client side in the N vehicle types according to the authority indication information of the N vehicle types.
In one possible implementation, the apparatus 05 may further include:
a storage unit 504, configured to store the vehicle type diagnosis authority list; a second confirming unit 505, configured to determine, according to authority data of the N vehicle types in the vehicle type diagnosis authority list, M vehicle types having diagnosis authorities corresponding to the client from among the N vehicle types when the client fails to perform networking; wherein M is an integer greater than or equal to 0, and M is less than or equal to N; a second diagnosing unit 506, configured to provide, according to the M vehicle models with the diagnosis authority, diagnosis entries corresponding to the M vehicle models in the client, where the diagnosis entries are used to provide diagnosis services for vehicles of corresponding vehicle models.
In a possible implementation manner, the identification information of the client may include an identity code of a device where the client is located.
By implementing the embodiment of the application, the host factory identifies different devices of the operating client by using the server, and accurately allocates the corresponding diagnosis authority according to the device information; the client receives the authority data from the server and confirms the number, the category and other information of the vehicle type diagnosis authority owned by the client; after confirming the diagnostic authority, the client provides a diagnostic portal to the user for using the corresponding diagnostic software package. The host factory can set the use authority of the client to the diagnosis software package through the server, namely, a user can only diagnose vehicles of corresponding vehicle types on the client with the diagnosis authority of certain vehicle types, the diagnosis authority of the client is effectively managed, and the working efficiency of the host factory is improved.
It should be noted that, for the functions of each functional unit of the vehicle type diagnosis authority management device 05 described in the embodiment of the device of the present application, reference may be made to the description related to the vehicle type diagnosis authority management method in the embodiment of the method described in fig. 3, and details are not described herein again. When the execution sequence of each unit is changed, the novelty and the novelty of the application are not influenced, the execution sequence of each unit of the classification device of the maintenance factory is not limited by the application.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a general-purpose device 06 provided in the embodiment of the present application, and as shown in fig. 6, both the vehicle type diagnosis authority management device 04 and the vehicle type diagnosis authority management device 05 can be implemented in the structure of fig. 6, and the general-purpose device 06 may include at least one storage component 601, at least one communication component 602, and at least one processing component 603. In addition, the device may also include general components such as an antenna, a power supply, etc., which will not be described in detail herein.
The storage component 601 may be a Read-Only Memory (ROM) or other types of static storage devices that can store static information and instructions, a Random Access Memory (RAM) or other types of dynamic storage devices that can store information and instructions, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a compact disc Read-Only Memory (CD-ROM) or other optical disc storage, optical disc storage (which may include compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.
The communication component 602 may be a device for communicating with other devices or communication networks, such as an upgrade server, a key server, a device inside a vehicle, and the like.
The processing component 603, which may be a general purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs according to the above schemes.
The processing unit 603 is configured to call the instruction stored in the storage unit 601 to perform the following operations:
acquiring a vehicle type diagnosis authority list corresponding to identification information from a server according to the identification information of a client, wherein the vehicle type diagnosis authority list comprises authority data of N vehicle types, and N is an integer greater than or equal to 0; determining M vehicle types which have diagnosis authority and correspond to the client side in the N vehicle types according to the authority data of the N vehicle types, wherein M is an integer larger than or equal to 0, and M is smaller than or equal to N; and providing diagnosis entries corresponding to the M vehicle types in the client according to the M vehicle types with the diagnosis authority, wherein the diagnosis entries are used for providing diagnosis services for vehicles of the corresponding vehicle types.
In one possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes check data of a corresponding vehicle type;
the processing component 603 is specifically configured to: verifying the verification data of the N vehicle types; and determining the vehicle types corresponding to the M verification data which are successfully verified as M vehicle types which are corresponding to the client and have the diagnosis authority.
In one possible implementation manner, the authority data of each vehicle type in the authority data of the N vehicle types includes authority indication information of a corresponding vehicle type;
the processing component 603 is specifically configured to: determining authority indicating information of the N vehicle types according to the authority data of the N vehicle types, wherein the authority indicating information is used for indicating whether the client side has the diagnosis authority of the corresponding vehicle type; and determining M vehicle types with diagnosis authorities corresponding to the client side in the N vehicle types according to the authority indication information of the N vehicle types.
In one possible implementation, the processing component 603 is further configured to:
storing the vehicle type diagnosis authority list; under the condition that the client is in networking failure, determining M vehicle types with diagnosis permission corresponding to the client in the N vehicle types according to permission data of the N vehicle types in the vehicle type diagnosis permission list; wherein M is an integer greater than or equal to 0, and M is less than or equal to N; and providing diagnosis entries corresponding to the M vehicle types in the client according to the M vehicle types with the diagnosis authority, wherein the diagnosis entries are used for providing diagnosis services for vehicles of the corresponding vehicle types.
In a possible implementation manner, the identification information of the client includes an identity code of a device where the client is located.
The embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a program, and when the program is executed, the program may include some or all of the steps of any one of the method embodiments described above. The computer storage medium may include: various media that can store program codes, such as a usb disk, a removable hard disk, a magnetic disk, an optical disk, a Read-only Memory (ROM) or a Random Access Memory (RAM).
Embodiments of the present application also provide a computer program, which may include instructions that, when executed by a computer, cause the computer to perform some or all of the steps including any one of the method embodiments described above.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the above-described division of the units is only one type of division of logical functions, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. The elements of the above device embodiments may or may not be physically separated, and some or all of the elements may be selected according to actual needs to achieve the purpose of the embodiments of the present application.
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 unit may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as a separate product.
Based on such understanding, the technical solutions of the present application may be embodied in the form of software products, in essence, or as a part of or all of the technical solutions contributing to the prior art; the computer software product is stored in a storage medium and may include several instructions to enable a computer device (which may be a personal computer, a server, a network device, or the like, and may specifically be a processor in the computer device) to perform all or part of the steps of the above-described method according to various embodiments of the present application. The above 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; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.