Authorization authentication method, device, equipment and computer storage medium

By implementing permission authentication methods on terminal devices, we ensure that only legal diagnostic connector equipment can diagnose vehicles, solving the problems of inaccurate detection results and vehicle safety hazards caused by pirated or failed equipment, and achieving efficient and safe vehicle diagnosis.

CN113806722BActive Publication Date: 2025-03-25LAUNCH SOFTWARE DEV
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202111126401.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-09-24
Publication Date
2025-03-25
Estimated Expiration
2041-09-24

AI Technical Summary

Technical Problem

How to effectively prevent the use of pirated or failed diagnostic connector equipment to diagnose vehicles, and solve the problems of inaccurate detection results and vehicle safety hazards caused by pirated or failed equipment.

Method used

By implementing permission authentication methods on terminal devices, detecting the software and external devices logged in by users, sending an identifier to the server to obtain a list of available devices, and opening the usage permissions after matching the device, ensuring that only legal devices can perform vehicle diagnosis.

Benefits of technology

It effectively prevents the use of pirated or failed equipment for vehicle diagnosis, improves the accuracy of diagnostic results and vehicle safety, and protects the reputation and benefits of manufacturers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113806722B_ABST
    Figure CN113806722B_ABST
Patent Text Reader

Abstract

The present application is applicable to the field of vehicle technology, and provides a method, device, equipment and computer storage medium for authentication of rights. The above-mentioned authentication method of rights includes: when detecting that a user logs into a first software, obtaining the identification of the first software, sending the identification of the first software to a server, and receiving a first response message sent by the server, the first response message including a list of available external devices corresponding to the identification of the first software; after detecting that communication is established with the first external device, matching the first external device with the list of available external devices; if the match is successful, opening the use right of the first external device. In this way, the first external device has the use right only when it is an external device in the list of available external devices corresponding to the pre-stored identification of the first software. Therefore, the present application can effectively solve the problem of using pirated or invalid external devices to perform related permission operations.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application belongs to the field of vehicle technology, and in particular, relates to an authority authentication method, device, equipment and computer storage medium. Background Art

[0002] Choosing reliable and effective diagnostic connector equipment can shorten the time for automobile maintenance personnel to diagnose vehicle faults and speed up the detection of vehicle fault locations and causes. In daily life, consumers or some maintenance personnel often use pirated or expired diagnostic connector equipment to diagnose vehicles in order to reduce the cost of purchasing effective diagnostic connector equipment. Although this reduces expenses, pirated or expired diagnostic equipment is of poor quality and the test results may be inaccurate, resulting in safety hazards in the tested vehicles, which affects the reputation and profits of manufacturers.

[0003] Therefore, how to effectively prevent the use of pirated or expired diagnostic connector equipment to diagnose vehicles has become an urgent problem to be solved. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a permission authentication method, apparatus, device and computer storage medium, aiming to solve the problem of using pirated or invalid external devices to perform related permission operations.

[0005] The embodiment of the present application is implemented as follows. In a first aspect, the embodiment of the present application provides a permission authentication method, which is applied to a terminal device. The method includes: when detecting that a user logs into a first software, obtaining an identifier of the first software;

[0006] Sending an identifier of the first software to the server;

[0007] Receiving first response information sent by the server, the first response information including a list of available external devices corresponding to the identifier of the first software;

[0008] When it is detected that communication is established with the first external device, the first external device is matched with available external devices recorded in the available external device list;

[0009] If the matching is successful, the use permission of the first external device is opened.

[0010] In one embodiment, before obtaining the identifier of the first software, the method further includes:

[0011] When detecting that a user logs into the first software, obtaining the user's login information;

[0012] Send login information to the server;

[0013] receiving second response information sent by the server, the second response information including a list of available software corresponding to the login information;

[0014] Matching the first software with the available software recorded in the available software list;

[0015] If the match is successful, the use permission of the first software is opened, and the steps of obtaining the identification of the first software and subsequent steps are executed.

[0016] In one embodiment, after sending the login information to the server, the method further includes:

[0017] The third response information sent by the server is received, where the third response information is used to prompt that the login information authentication fails.

[0018] In one embodiment, the method further comprises:

[0019] The association information is sent to the server, where the association information includes an association relationship between the first software and the list of available external devices.

[0020] In a second aspect, an embodiment of the present application provides a permission authentication method, which is applied to a server, and the method includes: receiving an identifier of a first software sent by a terminal device;

[0021] Acquire a corresponding list of available external devices according to the identifier of the first software, and generate first response information, wherein the first response information includes the list of available external devices corresponding to the identifier of the first software;

[0022] Sending first response information to the terminal device.

[0023] In one embodiment, before receiving the identifier of the first software sent by the terminal device, the method further includes:

[0024] Receiving login information sent by the terminal device;

[0025] Authenticate the login information;

[0026] After the authorization of the login information is authenticated, a corresponding list of available software is obtained according to the login information, and a second response information is generated, wherein the second response information includes the list of available software corresponding to the login information;

[0027] Send second response information to the terminal device.

[0028] In a third aspect, an embodiment of the present application provides a permission authentication device, which is applied to a terminal device, and the device includes: an acquisition unit, which is used to acquire an identification of the first software when detecting that a user logs in to the first software;

[0029] A first sending unit, used for sending an identifier of the first software to the server;

[0030] A first receiving unit, configured to receive first response information sent by the server, wherein the first response information includes a list of available external devices corresponding to the identifier of the first software;

[0031] A first matching unit, configured to match the first external device with an available external device recorded in the available external device list after detecting that communication is established with the first external device;

[0032] The permission opening unit is used to open the use permission of the first external device if the matching is successful.

[0033] In a fourth aspect, an embodiment of the present application provides a permission authentication device, which is applied to a server, and the device includes: a second receiving unit, which is used to receive an identifier of a first software sent by a terminal device;

[0034] A generating unit, configured to obtain a corresponding list of available external devices according to the identifier of the first software, and generate first response information, wherein the first response information includes the list of available external devices corresponding to the identifier of the first software;

[0035] The second sending unit is used to send first response information to the terminal device.

[0036] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the device executes any one of the methods in the first aspect or the second aspect.

[0037] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the processor executes the method described in any one of the first aspect or the second aspect.

[0038] In a seventh aspect, an embodiment of the present application provides a computer program product, comprising: a computer program code, when the computer program code is executed by a computer, the computer executes any one of the methods in the first aspect or the second aspect.

[0039] It can be understood that the beneficial effects of the second to seventh aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here.

[0040] It can be seen from the above technical solutions that the beneficial effects achieved by the embodiments of the present application are as follows: the present application provides a permission authentication method, after the terminal device detects that the user has logged into the first software, the terminal device uses the identifier corresponding to the first software to obtain the list of available external devices corresponding to the first software identifier from the server, and when it is detected that the first external device has established communication with the terminal device, if the first external device is a device in the above-mentioned list of available external devices, then the first external device has the permission to use, and the permission to use the first external device is opened. In this way, only when the first external device is an external device in the list of available external devices corresponding to the pre-stored first software identifier, the first external device has the permission to use, therefore, the present application can effectively solve the problem of using pirated or invalid external devices to perform related permission operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 It is a schematic diagram of a permission authentication system provided in an embodiment of the present application;

[0042] Figure 2 This is a flowchart of a permission authentication method provided by an embodiment of the present application;

[0043] Figure 3 is a flowchart of another permission authentication method provided in an embodiment of the present application;

[0044] Figure 4 The embodiment of the present application provides Figure 2 Flow chart of the corresponding server-side permission authentication method;

[0045] Figure 5 It is a schematic diagram of a usage scenario of the permission authentication method provided in an embodiment of the present application;

[0046] Figure 6 It is a structural diagram of a permission authentication device provided in an embodiment of the present application;

[0047] Figure 7 It is a structural diagram of another permission authentication device provided in an embodiment of the present application;

[0048] Figure 8 It is a structural diagram of a terminal device provided in an embodiment of the present application;

[0049] Fig. 9 It is a schematic diagram of the composition of a server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0051] Choosing reliable and effective vehicle diagnostic connector equipment can shorten the time for automobile maintenance personnel to diagnose vehicle faults and speed up the detection of vehicle fault locations and causes. In daily life, in order to reduce the cost of purchasing genuine diagnostic connector equipment, consumers or some maintenance personnel use pirated or expired diagnostic connector equipment to diagnose vehicles. Although this reduces expenses, pirated or expired diagnostic connector equipment is of poor quality or incomplete functions, and the test results may be inaccurate, resulting in safety hazards in the tested vehicles, affecting the reputation and profits of the manufacturer. Therefore, how to effectively prevent the use of pirated and expired diagnostic connector equipment to diagnose vehicles has become an urgent problem to be solved.

[0052] In order to solve the problem of using pirated and invalid diagnostic connector devices to diagnose vehicles, the present application provides a permission authentication method, which authenticates the use authority of the diagnostic connector device. Only when the authentication is passed can the user use the diagnostic connector device with the use authority to diagnose the vehicle. Therefore, it can effectively solve the problem of using pirated diagnostic software and invalid diagnostic connector devices to diagnose vehicles.

[0053] The system architecture involved in the embodiments of the present application is described below.

[0054] Figure 1 Schematic diagram of a permission authentication system provided by an embodiment of the present application. Figure 1 The system includes a terminal device 101 and a server 102. The terminal device 101 is a device installed with a first software, and the server 102 is a cloud that provides the first software and / or the first external device for authorization authentication services. The terminal device 101 and the server 102 can establish communication, and the authorization authentication method can be implemented by using the data interaction between the terminal device 101 and the server 102.

[0055] The technical solution of the present application is described in detail with specific embodiments. The embodiments described below with reference to the accompanying drawings are exemplary and intended to be used to explain the present application, but should not be construed as limiting the present application.

[0056] like Figure 2 The flowchart of a method for authentication of permissions provided in an embodiment of the present application is shown in FIG. Figure 2 The method is applied to a terminal device and includes the following steps.

[0057] Step 201: When it is detected that a user logs into a first software, an identifier of the first software is obtained.

[0058] The first software is the software requested by the terminal device, and the identifier of the first software is used to uniquely identify the first software. Software with different names, versions or models have different first software identifiers. For example, when the first software is diagnostic software, the identifier of the first software may be the software name corresponding to the diagnostic software.

[0059] Step 202: Send the identifier of the first software to the server.

[0060] After the terminal device obtains the identifier corresponding to the first software, the terminal device sends the obtained first software identifier to the server.

[0061] Step 203: receiving first response information sent by the server, where the first response information includes a list of available external devices corresponding to the identifier of the first software.

[0062] After receiving the identifier of the first software sent by the terminal device, the server obtains a list of available external devices corresponding to the first software according to the identifier of the first software, and generates a corresponding first response message. The list of available external devices may include at least one available external device, and the available external device is an external device associated with the first software that is allowed to be used. Exemplarily, the list of available external devices includes one or more external device information associated with the first software. The external device information includes, but is not limited to, a device name and a device identifier, which are used to identify the external device.

[0063] Step 204: When it is detected that communication is established with the first external device, the first external device is matched with available external devices recorded in the available external device list.

[0064] The first external device is an external device connected to the terminal device. Detecting that communication is established with the first external device may be that the terminal device establishes a communication connection with the first external device, and is ready to use the terminal device and the first external device to perform related permission operations.

[0065] According to the first response information sent by the server, it is determined whether there is an external device matching the first external device in the list of available external devices corresponding to the first software. If so, the matching is successful, otherwise the matching fails.

[0066] Step 205: If the match is successful, the use permission of the first external device is opened.

[0067] If there is an external device matching the first external device in the list of available external devices corresponding to the first software, the matching is successful and the corresponding first external device has the usage permission, that is, the user is allowed to use the first external device to perform relevant permission operations.

[0068] In some embodiments, the terminal device may be a diagnostic device, the first software may be a diagnostic software, and the external device may be a diagnostic connector.

[0069] The present application provides a permission authentication method. After the terminal device detects that a user has logged into the first software, the terminal device uses the identifier corresponding to the first software to obtain the list of available external devices corresponding to the identifier of the first software from the server. When it is detected that the first external device has established communication with the terminal device, if the first external device is a device in the above-mentioned list of available external devices, the first external device has the permission to use, and the permission to use the first external device is opened. In this way, the first external device has the permission to use only when it is an external device in the list of available external devices corresponding to the identifier of the first software. The problem of using pirated or expired external devices to perform related permission operations is solved.

[0070] In one possible implementation, Figure 3 FIG. 1 is a flowchart of another method for authentication of permissions provided in an embodiment of the present application. Figure 3 Before obtaining the identifier of the first software, the method further includes steps 301 to 303.

[0071] Step 301: When it is detected that a user logs into the first software, the user's login information is obtained.

[0072] The method of obtaining the login information may include: when the user wants to start the first software, the user needs to input the login information, thereby obtaining the user's login information.

[0073] Step 302: Send login information to the server; receive second response information sent by the server, the second response information including a list of available software corresponding to the login information.

[0074] After the terminal device obtains the login information input by the user, it sends the corresponding login information to the server. After receiving the login information, the server searches for the available software list corresponding to the login information according to the login information and generates a second response information. The available software list may include information of at least one available software, and the above-mentioned available software is the available software corresponding to the login information, that is, the available software corresponding to this account. Exemplarily, the available software list includes the available software information associated with the user name in the login information, wherein the available software information includes but is not limited to the software name, software serial number and version, which is used to identify the available software.

[0075] In the embodiment of the present application, after receiving the login information, the server uses the login information to search for the list of available software corresponding to the login information. When the login information changes, the information for searching the list of available software corresponding to the login information also changes accordingly. For example, when the login information includes face data, the list of available software corresponding to the face data can be searched by matching the face data in the login information with the face data stored in the server database.

[0076] Step 303: Match the first software with the available software recorded in the available software list; if the match is successful, the use permission of the first software is opened, and the steps of obtaining the identification of the first software and subsequent steps are executed.

[0077] The terminal device receives the second response information sent by the server, and matches the first software with the available software list corresponding to the login information in the second response information. If the first software exists in the available software list, the match is successful and the first software has the right to use it; if the first software does not exist in the available software list, the match is unsuccessful and the first software does not have the right to use it.

[0078] In the above embodiment, after the terminal device detects that the user logs into the first software, it obtains the user's login information, and uses the user's login information to obtain the list of available software corresponding to the login information from the server. When the available software in the available software list matches the first software, the first software has the right to use it, and then further obtains the identifier of the first software, and uses the identifier of the first software to obtain the list of available external devices corresponding to the identifier of the first software from the server. When the terminal device detects that the first external device has established communication with the terminal device, if the first external device matches the external device in the above-mentioned list of available external devices, the first external device has the right to use it, and the right to use the first external device is opened. In this way, it can be determined whether the first software is a software that the current login account has the right to use. This application not only verifies the right to use the first software, but also verifies the first external device corresponding to the first software, so as to effectively solve the problem of using pirated or expired first software and first external devices to perform related permission operations, and further ensure the safety of using the first software and the first external device to diagnose the vehicle. In this embodiment, the first software can be a diagnostic software.

[0079] It is not difficult to understand that after sending the login information to the server in step 302, the process may also include: receiving third response information sent by the server, where the third response information is used to prompt that the login information authentication fails.

[0080] In actual applications, in order to ensure the security of the use of the first software, when the terminal device detects that the user logs into the first software, the user may be required to enter corresponding login information to verify the user identity information of the first software.

[0081] It is easy to understand that the user's login information includes but is not limited to a user name and a password, wherein the user name can not only be used to verify the user's identity, but also can be used to search for available software with usage rights corresponding to the user name.

[0082] In some possible embodiments, the login information may also be other information used to uniquely identify the user. For example, in addition to the user name and password, the login information may also include facial data, ID number, contact number or custom account number, etc. For another example, the login information may also include fingerprint information, iris information, etc. In some embodiments, verifying the login information includes: determining whether the user name and password match, and if so, determining that the verification is successful. In other embodiments, it may also be determining whether the facial data matches the pre-stored facial data, or determining whether the fingerprint information matches the pre-entered fingerprint information, and if so, determining that the verification is successful.

[0083] After the terminal device obtains the login information entered by the user, it sends the corresponding login information to the server. After receiving the login information, the server verifies the received login information. If there is an error in the login information, the server generates a third response information to prompt that the login information authentication fails, and sends the third response information to the terminal device.

[0084] By verifying the user login information, illegal accounts or illegal users can be prevented from using the first software to perform related permission operations, thereby improving the security of the terminal device or the first software.

[0085] Similarly, in the above embodiment, when the first software fails to match the available software list, or the first external device fails to match the external device in the external device list corresponding to the first software, a prompt message may be returned to indicate that the first software or the first external device does not have permission to use.

[0086] It should be understood that the specific content of the prompt information can be set accordingly according to different authentication results. For example, when there is an error in the login information, a prompt information can be returned, and the prompt information is used to prompt that the login information authentication fails. When the first software and the list of available software do not match successfully, a corresponding prompt information can be returned, and the prompt information is used to indicate that the first software does not have permission to use. When the first software and the list of available software match successfully, the first external device is further authenticated. When the first external device and the external device in the external device list corresponding to the first software do not match successfully, a corresponding prompt information can also be returned to indicate that the first software has permission to use, but the first external device does not have permission to use; or a prompt information indicating that the verification failed is directly returned.

[0087] In order to speed up the verification of the usage rights of the first software and the first external device corresponding to the first software and save the time of separate verification of the first hardware, in a possible embodiment, when the terminal device detects that the first software is not an available software, it will not further verify the first external device, because even if the first external device is successfully verified, the user still cannot use the unavailable first software to interact with the terminal through the first external device.

[0088] In a possible implementation, the permission authentication method further includes: sending association information to a server, where the association information includes an association relationship between the first software and the list of available external devices.

[0089] Exemplarily, when a user purchases or renews the right to use the first software and the first external device through an application or a web page, the user name corresponding to the user and the association relationship between the first software and the first external device can be sent to the server. In order to improve the user experience, after the user purchases the first software and the first external device, the server can automatically store the user name corresponding to the user and the association relationship between the first software and the first external device in the server. Of course, considering practicality, after the user purchases the first software and the first external device, the user can associate the first software with the first external device through prompts, etc., and then store the association relationship between the user name, the first software and the first external device in the server.

[0090] The first software or the first external device does not have the right to use, which may include the following two situations: one situation is that the first software or the first external device is not produced by a genuine manufacturer. For example, the serial numbers of the software developed by a manufacturer are abc, def, etc. When the first software does not have a serial number or the serial number does not match the serial number of the software developed by the manufacturer, it is judged that the first software does not have the right to use. Another situation is that the use period of the first software or the first external device is not within the valid use period. For example, the valid use period of the first software is two years. When the first software is still in use after more than two years, then the use period of the first software is not within the valid use period, so it can be judged that the first software does not have the right to use.

[0091] In actual application, the conditions for whether the available software or available external device has the right to use can be set based on whether the use of the first software and the first external device will cause security risks during the user's use or whether the reputation and revenue of the equipment and software manufacturers will be damaged. This application does not impose any restrictions on this.

[0092] For example, considering that the accuracy of the use of external devices will be reduced due to wear and tear of various components after long-term use, when the user uses an inaccurate external device to detect vehicle faults, it may cause inaccurate fault detection, so that the vehicle after detection is still at risk of failure. In order to avoid the above situation and improve safety, when the external device exceeds the effective use period, the association between the available external device in the available external device list in the server and the available software in the available software list is deleted.

[0093] like Figure 4 FIG. 1 is a flowchart of another method for authentication of permissions provided in an embodiment of the present application. Figure 4 ,and Figure 2 The corresponding method applied to the server includes the following steps.

[0094] Step 401: Receive an identifier of a first software sent by a terminal device.

[0095] After the terminal device detects that the user has logged into the first software, it obtains the identifier of the first software and sends it to the server. The server receives the identifier of the first software sent by the terminal device. The identifier of the first software sent by the terminal device corresponds one-to-one to the identifier of the first software received by the server. When the identifier of the first software changes, the corresponding identifier of the first software sent by the terminal device to the server and the identifier of the first software received by the server also change accordingly.

[0096] Step 402: Obtain a corresponding list of available external devices according to the identifier of the first software, and generate first response information, wherein the first response information includes the list of available external devices corresponding to the identifier of the first software.

[0097] The server obtains a list of available external devices corresponding to the first software according to the received identifier of the first software, and generates a first response message. When the first software includes a software requested by the terminal device, at least one list of available external devices corresponding to the software can be obtained; when the first software includes multiple software requested by the terminal device, at least one list of available external devices corresponding to each software can be obtained according to the multiple software requested.

[0098] Step 403: Send first response information to the terminal device.

[0099] The server sends the generated first response information to the terminal device, so that when the terminal device detects that communication is established with the first external device, it matches the first external device with the list of available external devices in the first response information to obtain the use authority of the first external device.

[0100] In the embodiment of the present application, the server stores the first software information and the list of available external devices corresponding to the first software information. When the user uses the first software and the first external device, the user needs to pass the verification of the server before using the first software and the first external device to perform vehicle diagnosis. This reduces the pressure of storing the above information in the terminal device, avoids the security issues caused by the terminal device performing permission verification on the first software and the first external device, and improves the effectiveness and security of verification.

[0101] In a possible implementation, before step 401, the method further includes: receiving login information sent by the terminal device; performing permission authentication on the login information; after the permission authentication of the login information is passed, obtaining a corresponding list of available software based on the login information, and generating a second response information, the second response information including a list of available software corresponding to the login information; and sending the second response information to the terminal device.

[0102] It is worth noting that, in order to reduce the storage pressure of the terminal device, the user's login information record is optionally stored in the server for verifying the login information sent by the receiving terminal device.

[0103] After the terminal device obtains the login information entered by the user, it sends the corresponding login information to the server. After receiving the login information, the server first verifies the received login information, that is, compares the received login information with the login information pre-stored on the server. If the comparison result is consistent, the login information verification is successful. After the login information verification is passed, the server searches for a list of available software corresponding to the login information based on the login information (such as the user name in the login information) to authenticate the authority of the first software used by the terminal device.

[0104] In order to improve fault tolerance, when the server verifies the login information sent by the terminal device, it sets a preset threshold for allowing verification failure as needed, that is, the user is allowed to re-enter the login information within the preset threshold range. For example, if the first verification fails, a prompt message can be returned to the terminal device to indicate that the user's login information is incorrect, allowing the user to re-enter the login information. It is also possible to set a preset time to suspend the user from re-entering the login information after reaching the preset threshold as needed.

[0105] In one of the embodiments, in order to ensure the accuracy of permission authentication, the server periodically checks the permission list corresponding to the user name; when there is a first software without permission to use in the permission list, the first software and the external device list corresponding to the first software are deleted; when there is a first external device without permission to use in the external device list corresponding to the available software in the permission list, the first external device in the external device list is deleted.

[0106] In the above example, after the account password in the login information is authenticated, the list of available software corresponding to the login information is obtained according to the login information. If the first software successfully matches the available software in the available software list, the list of available external devices associated with the first software is further determined based on the first software. If the external device in the available external device list successfully matches the first external device, it is determined that the first external device has the right to use. In this way, both the first software and the first external device have the right to use, and the user can use the first software and the first external device with the right to use to diagnose the vehicle. When the first software is diagnostic software and the first external device is a diagnostic connector device, the problem of using pirated diagnostic software and invalid diagnostic connector devices to diagnose the vehicle can be effectively solved.

[0107] The following uses a vehicle diagnosis scenario as an example to illustrate the authority authentication method provided in the embodiment of the present application. Figure 5 FIG. 1 is a schematic diagram of a usage scenario of a permission authentication method provided in an embodiment of the present application. Figure 5 , the terminal device is a diagnostic device, the first software is a diagnostic software, the first software is installed in the terminal device, that is, the diagnostic software is an application installed in the diagnostic device, and the first external device is a diagnostic connector device.

[0108] In some embodiments, the diagnostic connector device can be a USB cable, a device with Bluetooth connection function, or a device with wireless communication technology function. The diagnostic connector device can be determined according to actual needs, and this application does not impose any limitations on this.

[0109] Taking the diagnostic connector device as a USB cable as an example, the basic usage process is: one end of the diagnostic connector device is connected to the vehicle's on-board automatic diagnostic system (OBD) interface, and the other end is connected to the diagnostic device. The user (such as a vehicle diagnostician or maintenance personnel) performs fault detection on the vehicle by operating the diagnostic software installed in the diagnostic device.

[0110] In a possible implementation, when a user wants to use diagnostic software and diagnostic connector equipment to perform fault detection or diagnosis on a vehicle, the diagnostic software and diagnostic connector equipment should have permission to use. The application of the permission authentication method in this usage scenario is as follows: first, when it is detected that a user has logged into the diagnostic software, the terminal device obtains the identifier of the diagnostic software and sends it to the server. Then, after the server receives the identifier of the diagnostic software, it generates a first response message including a list of available external devices corresponding to the diagnostic software according to the identifier of the diagnostic software, and sends the first response message to the terminal device; then the terminal device receives the first response message; when the terminal device detects that communication has been established with the diagnostic connector equipment, it matches the diagnostic connector equipment with the external device in the received list of available external devices. If the match is successful, the user is given permission to use the diagnostic connector equipment.

[0111] Alternatively, when the terminal device detects that the user logs in to the diagnostic software, the user's login information is first obtained and sent to the server; then, the server receives the login information sent by the terminal device and authenticates the login information; when the authentication of the login information is passed, the second response information is generated by obtaining the list of available software corresponding to the login information according to the login information, and the second response information is sent to the terminal device; then the terminal device receives the list of available software corresponding to the login information sent by the server, matches the diagnostic software with the available software in the list of available software, and if the match is successful, the user is given the right to use the diagnostic software, and finally obtains the list of available external devices corresponding to the identifier of the diagnostic software from the server according to the identifier of the diagnostic software, matches the diagnostic connector device with the external device in the list of available external devices, and when the match is successful, the user is given the right to use the diagnostic connector device, so that the user's login information, diagnostic software and diagnostic connector device are all verified, further ensuring that the user uses the verified software and hardware to diagnose the vehicle, thereby improving the effectiveness and safety of the diagnosis. Optionally, the above-mentioned authentication of the login information can be the verification of the account password, or the verification of the face information or fingerprint information, etc., which is not limited in this application.

[0112] Optionally, when the diagnostic software and the available software list fail to match successfully, or the diagnostic connector device and the external device in the external device list corresponding to the diagnostic software fail to match successfully, a prompt message is displayed to the vehicle diagnostic personnel or maintenance personnel through the display screen of the terminal device. The prompt message is used to prompt the vehicle diagnostic personnel or maintenance personnel to use the diagnostic software or diagnostic connector device with which they have permission to use to detect vehicle faults.

[0113] It is worth noting that the specific prompt information content can be set according to different situations. When the diagnostic software or diagnostic connector device has the use authority, the vehicle diagnostic personnel or maintenance personnel can understand the reason why the diagnostic software and diagnostic connector device cannot be used.

[0114] It is not difficult to understand that in order to improve the fault tolerance of the permission authentication method, the above method can be repeatedly executed multiple times to provide accurate usage permission results for vehicle diagnostic personnel or maintenance personnel. It should be noted that the number of repeated executions can be set according to actual conditions. Of course, other methods that can improve the fault tolerance of the test can also be adopted, and this application does not make any limitation on this.

[0115] like Figure 6 As shown, an embodiment of the present application also provides an authority authentication device, which is applied to a terminal device. The authority authentication device 500 includes: an acquisition unit 501, a first sending unit 502, a first receiving unit 505, a first matching unit 504 and a authority opening unit 505.

[0116] The acquisition unit 501 is used to acquire the identifier of the first software when it is detected that a user logs into the first software.

[0117] The first sending unit 502 is used to send the identifier of the first software to the server.

[0118] The first receiving unit 503 is configured to receive first response information sent by the server, where the first response information includes a list of available external devices corresponding to the identifier of the first software.

[0119] The first matching unit 504 is configured to match the first external device with available external devices recorded in the available external device list after detecting that communication is established with the first external device.

[0120] The permission opening unit 505 is used to open the use permission of the first external device if the match is successful.

[0121] In one embodiment, the acquisition unit 501 is further configured to:

[0122] When detecting that a user logs into the first software, obtaining the user's login information;

[0123] Send login information to the server;

[0124] receiving second response information sent by the server, the second response information including a list of available software corresponding to the login information;

[0125] Matching the first software with the available software recorded in the available software list;

[0126] If the match is successful, the use permission of the first software is opened, and the steps of obtaining the identification of the first software and subsequent steps are executed.

[0127] In one embodiment, the acquisition unit 501 is further configured to:

[0128] The third response information sent by the server is received, where the third response information is used to prompt that the login information authentication fails.

[0129] In one embodiment, the method further comprises:

[0130] The association unit is used to send association information to the server, where the association information includes an association relationship between the first software and the list of available external devices.

[0131] like Figure 7 As shown, an embodiment of the present application further provides another authority authentication device, which is applied to a server. The authority authentication device 600 includes: a second receiving unit 601, a generating unit 602 and a second sending unit 603.

[0132] The second receiving unit 601 is configured to receive an identifier of a first software sent by a terminal device.

[0133] The generating unit 602 is used to obtain a corresponding list of available external devices according to the identifier of the first software, and generate first response information, wherein the first response information includes the list of available external devices corresponding to the identifier of the first software.

[0134] The second sending unit 603 is used to send first response information to the terminal device.

[0135] In one embodiment, the second receiving unit 601 is further configured to:

[0136] Receiving login information sent by the terminal device;

[0137] Authenticate the login information;

[0138] After the authorization of the login information is authenticated, a corresponding list of available software is obtained according to the login information, and a second response information is generated, wherein the second response information includes the list of available software corresponding to the login information;

[0139] Send second response information to the terminal device.

[0140] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0141] Based on the same inventive concept, the embodiment of the present application further provides an electronic device, the electronic device comprising: Figure 8 The terminal device 700 shown in FIG. Fig. 9 Server 800 is shown.

[0142] like Figure 8 As shown, the terminal device 700 of this embodiment includes: a processor 701, a memory 702, and a computer program 703 stored in the memory 702 and executable on the processor 701. The computer program 703 can be executed by the processor 701 to generate instructions, and the processor 701 can implement the steps in the above-mentioned various rights authentication method embodiments according to the instructions. Alternatively, when the processor 701 executes the computer program 703, the functions of each module / unit in the above-mentioned device embodiments are implemented.

[0143] Exemplarily, the computer program 703 may be divided into one or more modules / units, one or more modules / units are stored in the memory 702, and are executed by the processor 701 to complete the present application. One or more modules / units may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program 703 in the terminal device 700.

[0144] Those skilled in the art will understand that Figure 8 It is only an example of the terminal device 700 and does not constitute a limitation of the terminal device 700. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the terminal device 700 may also include input and output devices, network access devices, buses, etc.

[0145] The processor 701 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0146] The memory 702 may be an internal storage unit of the terminal device 700, such as a hard disk or memory of the terminal device 700. The memory 702 may also be an external storage device of the terminal device 700, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card (FlashCard), etc. equipped on the terminal device 700. Further, the memory 702 may also include both an internal storage unit of the terminal device 700 and an external storage device. The memory 702 is used to store computer programs and other programs and data required by the terminal device 700. The memory 702 may also be used to temporarily store data that has been output or is to be output.

[0147] The terminal device provided in this embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, which will not be repeated here.

[0148] like Fig. 9 FIG. 1 is a schematic diagram showing the composition of a server provided in an embodiment of the present application. Fig. 9 The server 800 includes: a processor 801 , a memory 802 , a communication interface 803 and a communication bus 804 .

[0149] The processor 801 is the control center of the server 800, and can be a processor or a general term for multiple processing elements. For example, the processor 801 is a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as one or more DSPs, or one or more field-programmable gate arrays (FPGAs).

[0150] The processor 801 can execute various functions of the server 800 by running or executing software programs stored in the memory 802 and calling data stored in the memory 802. For example, the processor 801 is used to execute Figure 4 402 in, and / or other processes for the techniques described herein.

[0151] In a specific implementation, as an embodiment, the processor 801 may include one or more CPUs. As an embodiment, the server 800 may include multiple processors, each of which may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor here may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0152] The memory 802 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, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical 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 the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 802 may exist independently and be connected to the processor 801 via a communication bus 804. The memory 802 may also be integrated with the processor 801.

[0153] The memory 802 is used to store the software program for executing the solution of the present application, and the execution is controlled by the processor 801 .

[0154] The communication interface 803 uses any transceiver-like device to communicate with other devices or communication networks, such as a subscription client, a publishing client, a radio access network (RAN), a wireless local area network (WLAN), etc. In a specific implementation, the server can receive attribute information of a tag of a subscription client sent by a subscription client, and attribute information of a tag of a publishing client sent by a publishing client through the communication interface 803. The communication interface 803 may include a receiving unit to implement a receiving function, and a sending unit to implement a sending function.

[0155] The communication bus 804 may be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig. 9 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0156] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method of the above method embodiment is implemented.

[0157] The embodiment of the present application also provides a computer program product, which, when executed on a terminal device, enables the terminal device to implement the method of the above method embodiment.

[0158] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of the above-mentioned method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable storage medium may at least include: any entity or device that can carry the computer program code to the camera / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a disk or an optical disk.

[0159] References to "one embodiment" or "some embodiments" etc. described in this application mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear at different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0160] In the description of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features.

[0161] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some or all of the technical features thereof may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for authentication of authority, characterized in that: A diagnostic device applied to a vehicle field, the method comprising: When detecting that a user logs into the diagnostic software, obtaining the login information of the user; Sending the login information to the server; receiving second response information sent by the server, wherein the second response information includes a list of available software corresponding to the login information; Matching the diagnostic software with the available software recorded in the available software list; If the match is successful, the use permission of the diagnostic software is opened and the identification of the diagnostic software is obtained; Sending an identifier of the diagnostic software to a server; receiving a first response message sent by the server, wherein the first response message includes a list of available diagnostic connectors corresponding to the identifier of the diagnostic software; When it is detected that communication is established with the first diagnostic connector, matching the first diagnostic connector with an available diagnostic connector recorded in the available diagnostic connector list; If the match is successful, the use permission of the first diagnostic connector is released.

2. The method according to claim 1, characterized in that After sending the login information to the server, the method further includes: A third response message sent by the server is received, where the third response message is used to prompt that the login information authentication fails.

3. The method according to claim 2, characterized in that The method further comprises: The association information is sent to a server, wherein the association information includes an association relationship between the diagnostic software and the available diagnostic connector list.

4. A method for authentication of authority, characterized in that: Applied to a server, the method comprises: receiving login information sent by the diagnostic device; Performing authority authentication on the login information; After the authority authentication of the login information is passed, obtaining a corresponding available software list according to the login information, and generating second response information, wherein the second response information includes the available software list corresponding to the login information; sending the second response information to the diagnostic device; Receiving the identification of the diagnostic software sent by the diagnostic device; Acquire a corresponding list of available diagnostic connectors according to the identifier of the diagnostic software, and generate first response information, wherein the first response information includes the list of available diagnostic connectors corresponding to the identifier of the diagnostic software; The first response information is sent to the diagnostic device.

5. A permission authentication device, characterized in that: A diagnostic device for use in the field of vehicles, the device comprising: an acquisition unit, configured to acquire the login information of the user when detecting that the user logs into the diagnostic software; send the login information to a server; receive a second response message sent by the server, the second response message including a list of available software corresponding to the login information; match the diagnostic software with the available software recorded in the list of available software; if the match is successful, grant the use permission of the diagnostic software and acquire the identifier of the diagnostic software; A first sending unit, used for sending the identification of the diagnostic software to a server; A first receiving unit, configured to receive first response information sent by the server, wherein the first response information includes a list of available diagnostic connectors corresponding to the identifier of the diagnostic software; a first matching unit, configured to match the first diagnostic connector with an available diagnostic connector recorded in the available diagnostic connector list after detecting that communication is established with the first diagnostic connector; The permission opening unit is used to open the use permission of the first diagnostic connector if the matching is successful.

6. A permission authentication device, characterized in that: Applied to a server, the device comprises: a second receiving unit, configured to receive login information sent by the diagnostic device; perform authority authentication on the login information; after the authority authentication on the login information is passed, obtain a corresponding list of available software according to the login information, and generate a second response information, wherein the second response information includes a list of available software corresponding to the login information; send the second response information to the diagnostic device; and receive an identifier of the diagnostic software sent by the diagnostic device; A generating unit, configured to obtain a corresponding list of available diagnostic connectors according to the identifier of the diagnostic software, and generate first response information, wherein the first response information includes the list of available diagnostic connectors corresponding to the identifier of the diagnostic software; The second sending unit is configured to send the first response information to the diagnostic device.

7. An electronic device, characterized in that: The electronic device comprises: a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the device executes the method of claims 1 to 3 or claim 4.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor executes the method of claims 1 to 3 or claim 4.

Citation Information

Patent Citations

  • Multifunctional remote fault diagnosis system for electric control automobile

    CN102183945A

  • Method for carrying out domain user verification by enterprise software management tool

    CN109309669A