A data processing method, apparatus, device and medium

Abstract

This application discloses a data processing method, apparatus, device, and medium in the field of computer technology. The diagnostic client provided in this application, after obtaining access parameters based on a user's access to a third-party server, queries its own internal database for the third-party server's access token based on these parameters. If an access token is found and valid, an access signature is obtained based on the access token and the access parameters. The access signature and access parameters are then sent to the third-party server. The third-party server verifies the access signature based on the access parameters and its stored access token, and returns response data containing the access parameters to the diagnostic client. This allows the diagnostic client to automatically log in to the third-party server and complete the access process, simplifying the process and improving efficiency. The data processing apparatus, medium, and device provided in this application also possess the aforementioned technical effects.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a data processing method, apparatus, device, and medium. Background Technology

[0002] Currently, in addition to using diagnostic servers to diagnose vehicle faults, diagnostic clients also update vehicle ECU firmware and other programs. Updating programs requires obtaining program packages and other data from third-party servers. Therefore, diagnostic clients need to be able to access both diagnostic servers and third-party servers.

[0003] Typically, when using a diagnostic client, users first log in to the diagnostic server using an account and password. After logging in, vehicle diagnostics can be performed. If access to a third-party server is required during or after the diagnostic process, the user must log in to the third-party server using an account and password. This requires the user to repeatedly perform the login operation, making the access process cumbersome, affecting access efficiency, and potentially causing user misunderstandings. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide a data processing method, apparatus, device, and medium that enables users to be unaware of the process of logging into a third-party server. That is, when a diagnostic client needs to access a third-party server, the diagnostic client automatically logs into the third-party server and completes the access process without requiring manual login from the user. The specific solution is as follows:

[0005] To achieve the above objectives, this application provides a data processing method applied to a diagnostic client corresponding to a diagnostic server, comprising:

[0006] Retrieve access parameters generated based on the user's actions when accessing a third-party server;

[0007] Based on the access parameters, query the access token of the third-party server within itself;

[0008] If the access token is found and is available, then the access signature is obtained based on the access token and the access parameters;

[0009] The access signature and access parameters are sent to the third-party server, so that the third-party server verifies the access signature based on the access parameters and the access token stored in itself, and then returns the response data of the access parameters to the diagnostic client.

[0010] Optionally, the access token may be available, including:

[0011] The access token is valid within the access period.

[0012] Optionally, it also includes:

[0013] If the access token is found but is unavailable, then query the refresh parameters for refreshing the access token within itself.

[0014] If the refresh parameters are found and are available, the refresh parameters are sent to the third-party server, so that after verifying that the refresh parameters are valid, the third-party server returns a new token and its access validity period, as well as new parameters for refreshing the new token and their refresh validity period to the diagnostic client; the refresh validity period is longer than the access validity period.

[0015] Optionally, it also includes:

[0016] Store the new token and its access validity period, and the new parameters and their refresh validity period;

[0017] If the access parameters are obtained, the new token is used as the access token, and the process of querying the access token of the third-party server in itself based on the access parameters is executed; if the access token is found and the access token is available, an access signature is obtained based on the access token and the access parameters; the access signature and the access parameters are sent to the third-party server, so that the third-party server verifies the access signature based on the access parameters and the access token stored in itself, and then returns the response data of the access parameters to the diagnostic client.

[0018] Optionally, the refresh parameters may include:

[0019] The refresh parameters are within the refresh time limit.

[0020] Optionally, it also includes:

[0021] If the access token is not found, or the refresh parameter for refreshing the access token is not found, or the refresh parameter for refreshing the access token is found but the refresh parameter is unavailable, then the connector serial number and connector identifier corresponding to the diagnostic client, and the device identifier of the diagnostic device where the diagnostic client is located are determined.

[0022] An identity signature is obtained based on the device identifier, the connector serial number, and the connector identifier;

[0023] The identity signature, the device identifier, and the connector serial number are sent to the third-party server, so that the third-party server verifies the identity signature based on the device identifier, the connector serial number stored in itself, and the connector identifier stored in itself, and then returns the access token and its access validity period, as well as the refresh parameters for refreshing the access token and their refresh validity period to the diagnostic client.

[0024] The access token and its access validity period, and the refresh parameters and their refresh validity period are stored.

[0025] Furthermore, this application also provides a data processing method applied to a third-party server, including:

[0026] The diagnostic client receives an access signature and access parameters sent by the diagnostic server; wherein, the access parameters are generated by the diagnostic client based on the user's access to the third-party server; and the access signature is obtained by the diagnostic client based on the access token and the access parameters when it determines that its stored access token is available.

[0027] The access signature is verified based on the access parameters and the access token corresponding to the diagnostic client stored within itself.

[0028] If the access signature verification passes, the response data of the access parameters is returned to the diagnostic client.

[0029] Optionally, verifying the access signature based on the access parameters and the access token corresponding to the diagnostic client stored within itself includes:

[0030] Search within itself for the access token corresponding to the diagnostic client;

[0031] A signature is generated based on the retrieved access token and the access parameters;

[0032] If the currently generated signature matches the access signature, the access signature verification passes; otherwise, the access signature verification fails.

[0033] Optionally, it also includes:

[0034] Receive refresh parameters sent by the diagnostic client to refresh the access token;

[0035] Query the refresh parameters corresponding to the diagnostic client within itself;

[0036] If the refresh parameters found are consistent with the refresh parameters sent by the diagnostic client, a new token and its access validity period, new parameters for refreshing the new token and their refresh validity period are returned to the diagnostic client, so that the diagnostic client stores the new token and its access validity period, the new parameters and their refresh validity period; the refresh validity period is greater than the access validity period.

[0037] Optionally, it also includes:

[0038] The diagnostic client sends an identity signature, a device identifier, and a connector serial number; wherein the device identifier is the identifier of the diagnostic device on which the diagnostic client resides; the diagnostic client corresponds to the connector serial number and the connector identifier; the identity signature is obtained based on the device identifier, the connector serial number, and the connector identifier.

[0039] The identity signature is verified based on the device identifier, the connector serial number stored in the device, and the connector identifier stored in the device.

[0040] If the identity signature verification passes, the access token and its access validity period, as well as the refresh parameters and their refresh validity period for refreshing the access token, are returned to the diagnostic client, so that the diagnostic client stores the access token and its access validity period, and the refresh parameters and their refresh validity period.

[0041] Optionally, before receiving the identity signature, device identifier, and connector serial number sent by the diagnostic client, the method further includes:

[0042] The connector serial number and connector identifier are obtained and stored from the diagnostic server.

[0043] Optionally, it also includes:

[0044] It records the access tokens and corresponding refresh parameters for multiple diagnostic clients within itself.

[0045] Furthermore, this application also provides a data processing apparatus, applied to a diagnostic client corresponding to a diagnostic server, comprising:

[0046] The acquisition module is used to acquire access parameters generated based on the user's actions when accessing a third-party server.

[0047] The query module is used to query the access token of the third-party server in itself based on the access parameters;

[0048] The signature module is used to obtain an access signature based on the access token and the access parameters if the access token is found and the access token is available.

[0049] The sending module is used to send the access signature and the access parameters to the third-party server, so that after the third-party server verifies the access signature based on the access parameters and the access token stored in itself, it returns the response data of the access parameters to the diagnostic client.

[0050] Furthermore, this application also provides a data processing apparatus for use on a third-party server, comprising:

[0051] The receiving module is used to receive the access signature and access parameters sent by the diagnostic client corresponding to the diagnostic server; wherein, the access parameters are generated by the diagnostic client based on the user's operation of accessing the third-party server; the access signature is obtained by the diagnostic client based on the access token and the access parameters when it determines that its stored access token is available;

[0052] The verification module is used to verify the access signature based on the access parameters and the access token corresponding to the diagnostic client stored in its own memory;

[0053] The return module is used to return response data of the access parameters to the diagnostic client if the access signature verification passes.

[0054] In another aspect, this application also provides an electronic device, the electronic device including a processor and a memory; wherein the memory is used to store a computer program, the computer program being loaded and executed by the processor to implement the method described in any of the foregoing.

[0055] In another aspect, this application also provides a storage medium storing computer-executable instructions, which, when loaded and executed by a processor, implement the method described in any of the preceding claims.

[0056] The diagnostic client provided in this application obtains access parameters based on the user's access to a third-party server. It then queries the third-party server's access token within its own database based on these parameters. If an access token is found and valid, an access signature is obtained based on the token and the access parameters. The access signature and access parameters are then sent to the third-party server. The third-party server verifies the access signature using the access parameters and its stored access token, and returns response data containing the access parameters to the diagnostic client. This allows the user to be unaware of the login process to the third-party server. The diagnostic client can automatically log in to the third-party server and complete the access process based on the user's access, eliminating the need for manual login and simplifying the process, thus improving access efficiency.

[0057] Correspondingly, the data processing apparatus, medium, and equipment provided in this application also have the aforementioned technical effects. Attached Figure Description

[0058] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0059] Figure 1 A flowchart of a data processing method provided in this application;

[0060] Figure 2 Flowchart of another data processing method provided in this application;

[0061] Figure 3 Flowchart of another data processing method provided in this application;

[0062] Figure 4 A flowchart of another data processing method provided in this application;

[0063] Figure 5 A schematic diagram of a data processing device provided in this application;

[0064] Figure 6 A schematic diagram of another data processing apparatus provided in this application;

[0065] Figure 7 A server architecture diagram provided for this application;

[0066] Figure 8 A terminal structure diagram provided for this application. Detailed Implementation

[0067] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Furthermore, in the embodiments of this application, terms such as "first" and "second" are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0068] The existing solution requires users to log in to a third-party server using their account and password during or after the diagnosis process. This requires users to repeatedly log in, making the access process cumbersome, affecting access efficiency, and easily causing user misunderstanding.

[0069] In view of the above-mentioned problems, this application proposes a data processing scheme that enables users to be unaware of the process of logging into a third-party server. The diagnostic client can automatically log into the third-party server and complete the access process based on the user's operation of accessing the third-party server, without the user having to manually repeat the login operation, making the access process simpler and improving access efficiency.

[0070] Figure 1This is a flowchart of a data processing method provided in an embodiment of this application. Figure 1 The provided data processing method is applied to the diagnostic client corresponding to the diagnostic server. The diagnostic client is an application installed on the diagnostic device.

[0071] The method provided in this application embodiment may specifically include the following steps:

[0072] S101. Obtain access parameters generated based on the user's access to the third-party server.

[0073] In this embodiment, the user can input an operation to access a third-party server through the human-machine interface provided by the diagnostic client, thereby enabling the diagnostic client to obtain corresponding access parameters based on the operation. For example, if the user inputs an operation to obtain an in-vehicle software update package from a third-party server through the human-machine interface, the access parameters may include, but are not limited to: the IP address and port of the third-party server, the name and version number of the in-vehicle software update package, the vehicle model, and the manufacturer.

[0074] S102. Query the access token of the third-party server in itself based on the access parameters.

[0075] S103. If an access token is found and is available, the access signature is obtained based on the access token and access parameters.

[0076] S104. Send the access signature and access parameters to the third-party server so that the third-party server can verify the access signature based on the access parameters and its own stored access token, and then return the response data of the access parameters to the diagnostic client.

[0077] After obtaining the corresponding access parameters, the diagnostic client queries the third-party server's access token (i.e., access token) within itself. If the access token is found and is valid, the client obtains an access signature based on the access token and access parameters, and then sends the access signature and access parameters to the third-party server. The third-party server then verifies the access signature based on the access parameters and its stored access token, and returns the access parameter response data to the diagnostic client. Thus, the access process to the third-party server is completed without the user's awareness of logging in.

[0078] The process of obtaining an access signature based on the access token and access parameters includes performing an MD5 (Message Digest algorithm 5) operation on the access token and access parameters to obtain the access signature. Alternatively, other algorithms can be used to process the access token and access parameters to obtain the access signature.

[0079] In one implementation, the access token is considered available if it is within its validity period. That is, the access token stored on the diagnostic client by the third-party server has an expiration date; if this expiration date is exceeded, the access token becomes invalid. If the access token is within its validity period, it is considered that its validity period has not expired; conversely, if the access token is not within its validity period, it is considered that its validity period has expired. After the access token's validity period expires, the diagnostic client needs to refresh the access token from the third-party server. The access validity period of the access token is set or modified by the third-party server, which sends its validity period along with the access token to the diagnostic client.

[0080] In one implementation, if an access token is found but is unavailable, the system queries its own database for refresh parameters (i.e., refresh tokens) to refresh the access token. If refresh parameters are found and are available, they are sent to a third-party server. The third-party server, after verifying the refresh parameters, returns a new token and its access validity period, along with new parameters for refreshing the new token and their refresh validity period, to the diagnostic client. The refresh validity period is longer than the access validity period. Therefore, even with an invalid access token, the diagnostic client can use the valid refresh parameters of the currently invalid access token to obtain a new token and corresponding refresh parameters from the third-party server. Furthermore, refresh parameters also have an expiration period. If the refresh parameters are within their expiration period, they are considered valid; otherwise, if they are not, they are considered expired. After the refresh parameters expire, the diagnostic client can no longer use them to refresh the access token from the third-party server and must reapply for an access token and refresh parameters. The refresh validity period of the refresh parameters is set or modified by a third-party server. When sending the refresh parameters to the diagnostic client, the third-party server also sends the refresh validity period. The access validity periods of the corresponding refresh parameters and access tokens are unequal, and the access validity period of the refresh parameters is longer than that of the access token. In one implementation, the refresh parameters are available when they are within their refresh validity period.

[0081] After the diagnostic client obtains the access token and its access validity period, and the refresh parameters and their access validity period from the third-party server, the diagnostic client stores the access token and its access validity period, and the refresh parameters and their access validity period, for use by the user when accessing the third-party server later. Therefore, in one embodiment, the method further includes: storing a new token and its access validity period, and new parameters and their refresh validity period; if access parameters are obtained, using the new token as the access token and querying the third-party server's access token based on the access parameters; if the access token is found and is available, obtaining an access signature based on the access token and access parameters; and sending the access signature and access parameters to the third-party server, so that the third-party server verifies the access signature based on the access parameters and its stored access token, and then returns response data of the access parameters to the diagnostic client.

[0082] In this embodiment, when the diagnostic client requests an access token and refresh parameters, the connector serial number, connector identifier, and device identifier of the diagnostic device where the diagnostic client is located are used as the basic information for identity authentication, and an identity signature is formed. The identity signature, device identifier, and connector serial number are then sent to a third-party server for identity authentication. The third-party server then returns the access token and its access validity period, and the refresh parameters and their refresh validity period. In one implementation, if no access token is found, or no refresh parameters for refreshing the access token are found, or refresh parameters for refreshing the access token are found but are unavailable, the connector serial number and connector identifier of the diagnostic client, and the device identifier of the diagnostic device where the diagnostic client is located are determined. An identity signature is obtained based on the device identifier, connector serial number, and connector identifier. The identity signature, device identifier, and connector serial number are sent to the third-party server, so that the third-party server verifies the identity signature based on the device identifier, its own stored connector serial number, and its own stored connector identifier. After successful verification, the third-party server returns the access token and its access validity period, and the refresh parameters and their refresh validity period to the diagnostic client. The access token and its access validity period, and the refresh parameters and their refresh validity period are stored. Device identifiers, such as the MAC (Medium / Media Access Control) address of diagnostic devices.

[0083] The connector serial number and connector identifier (such as connector ID) are information embedded in the connector. This information is determined during connector manufacturing and stored in the diagnostic server. The connector is a physical communication device that can wirelessly communicate with diagnostic equipment and has a pluggable ODB (On-Board Diagnostic) interface for communication between the diagnostic equipment and the vehicle's ECU (Electronic Control Unit / vehicle computer) to perform vehicle diagnostic procedures. Generally, the diagnostic client's account and password are bound to the connector.

[0084] Before the diagnostic client requests an access token and refreshes parameters, the third-party server pre-stores the connector serial number and connector identifier corresponding to the diagnostic client. The diagnostic server can provide an access interface to the third-party server, allowing the third-party server to obtain the connector serial number and connector identifier corresponding to the diagnostic client from the diagnostic server; alternatively, the diagnostic server can proactively send the connector serial number and connector identifier corresponding to the diagnostic client to the third-party server.

[0085] As can be seen, the diagnostic client provided in this embodiment, after obtaining access parameters based on the user's access to the third-party server, queries its own internal database for the third-party server's access token based on the access parameters. If an access token is found and is valid, an access signature is obtained based on the access token and access parameters. The access signature and access parameters are then sent to the third-party server, which verifies the access signature based on the access parameters and its own stored access token. After successful verification, the third-party server returns response data of the access parameters to the diagnostic client. This allows the user to be unaware of the login process to the third-party server. The diagnostic client can automatically log in to the third-party server and complete the access process based on the user's access to the third-party server, eliminating the need for the user to manually repeat the login process. This simplifies the access process and improves access efficiency.

[0086] Figure 2 This is a flowchart of another data processing method provided in an embodiment of this application. Figure 2 The provided data processing method is applied to a third-party server, which can be a server itself. This embodiment can be referenced in conjunction with the implementation steps of other embodiments.

[0087] The method provided in this application embodiment may specifically include the following steps:

[0088] S201. Receive the access signature and access parameters sent by the diagnostic client corresponding to the diagnostic server.

[0089] The access parameters are generated by the diagnostic client based on the user's access to the third-party server; the access signature is obtained by the diagnostic client based on the access token and access parameters when it determines that its stored access token is available.

[0090] S202. Verify the access signature based on the access parameters and the access token corresponding to the diagnostic client stored in its own database.

[0091] S203. If the access signature verification passes, return the response data of the access parameters to the diagnostic client.

[0092] It should be noted that after the third-party server sends an access token and its access validity period, refresh parameters and their refresh validity period to a diagnostic client, it stores the currently sent access token and its validity period, refresh parameters, and the unique identifier information of the current diagnostic client. If it subsequently receives an access request or token update request from the same diagnostic client, the third-party server can respond based on the previously stored information. The unique identifier information of the diagnostic client can be the interface identifier corresponding to the diagnostic client, the connector sequence number, or a unique sequence number assigned to the diagnostic client by the third-party server. Therefore, in one implementation, the third-party server also records access tokens and corresponding refresh parameters for multiple diagnostic clients within itself.

[0093] In this embodiment, the access signature is verified based on the access parameters and the access token corresponding to the diagnostic client stored in the system. This includes: querying the access token corresponding to the diagnostic client in the system; generating a signature based on the queried access token and access parameters; if the currently generated signature matches the access signature, the access signature verification passes; otherwise, the access signature verification fails.

[0094] In one implementation, the third-party server may further perform the following steps: receive refresh parameters sent by the diagnostic client for refreshing the access token; query the corresponding refresh parameters of the diagnostic client in its own database; if the queried refresh parameters are consistent with the refresh parameters sent by the diagnostic client, return the new token and its access validity period, the new parameters used to refresh the new token and their refresh validity period to the diagnostic client, so that the diagnostic client stores the new token and its access validity period, the new parameters and their refresh validity period; the refresh validity period is greater than the access validity period.

[0095] In one implementation, the third-party server may further perform the following steps: receiving an identity signature, device identifier, and connector serial number sent by the diagnostic client; wherein the device identifier is the identifier of the diagnostic device where the diagnostic client resides; the diagnostic client has a corresponding connector serial number and connector identifier; the identity signature is obtained based on the device identifier, connector serial number, and connector identifier; the identity signature is verified based on the device identifier, its own stored connector serial number, and its own stored connector identifier; if the identity signature verification passes, an access token and its access validity period, and refresh parameters and their refresh validity period are returned to the diagnostic client, so that the diagnostic client stores the access token and its access validity period, refresh parameters, and their refresh validity period. The signature algorithm used to generate the identity signature can be any algorithm such as MD5.

[0096] In this embodiment, the third-party server pre-stores the connector serial number and connector identifier corresponding to the diagnostic client. The diagnostic server can provide an access interface to the third-party server, enabling the third-party server to obtain the connector serial number and connector identifier corresponding to the diagnostic client from the diagnostic server; alternatively, the diagnostic server can proactively send the connector serial number and connector identifier corresponding to the diagnostic client to the third-party server. Before receiving the identity signature, device identifier, and connector serial number sent by the diagnostic client, the process further includes: obtaining and storing the connector serial number and connector identifier from the diagnostic server.

[0097] As can be seen, this embodiment allows users to be unaware of the process of logging into the third-party server. The diagnostic client can automatically log into the third-party server and complete the access process based on the user's operation of accessing the third-party server, without the user having to manually repeat the login operation, making the access process simpler and improving access efficiency.

[0098] Based on the above embodiments, a feasible implementation plan may include the following, please refer to the following for details. Figure 3 .

[0099] 1. Store the connector serial number and connector ID on a third-party server.

[0100] 2. When the diagnostic client needs to access a third-party server, it obtains the MAC address of its own diagnostic device, the connector serial number (SN) corresponding to the currently logged-in account, and the connector ID. The diagnostic client then uses the MAC address and connector serial number to perform an MD5 signature on the connector ID, and sends the signature, MAC address, and connector SN serial number to the third-party server. The connector SN (serial number) is the same as the product serial number.

[0101] 3. Upon receiving the data, the third-party server uses the received MAC address and the previously stored connector sequence number to sign the previously stored connector ID in the same way. It then compares its calculated signature with the received signature. If the two signatures match, the server considers the diagnostic client to have sent legitimate identity information and sends an access token and a refresh token to the diagnostic client; otherwise, it returns an error message.

[0102] 4. After receiving the access token and refresh token from the third-party server, the diagnostic client records both the access token and refresh token, as well as their effective dates. The access token can be used for subsequent access processes. If the diagnostic client receives an error message from the third-party server, it displays a failure message and the reason for the error.

[0103] The diagnostic client's access process using an access token includes: obtaining access parameters based on the user's input of the operation to access the third-party server; encrypting the access token and access parameters using MD5 to obtain an access signature string; and then transmitting the access signature string and access parameters to the third-party server for verification. Upon receiving the access signature string, the third-party server performs an MD5 signature in the same way and compares its calculated signature with the received access signature. If the two signatures match, the access parameters are processed normally, and the corresponding response data is returned; if the two signatures differ, an error message is returned.

[0104] Please see Figure 4 Before using an access token, the diagnostic client checks if the access token has expired. If it hasn't expired, it uses it normally; otherwise, it updates the access token using a refresh token. The update process is as follows: the diagnostic client sends the refresh token to the third-party server. The third-party server confirms that it sent the refresh token to the diagnostic client and then resends both the access token and refresh token to the diagnostic client, allowing the client to access the third-party server using the newly obtained access token. The refresh token has a longer validity period than the access token; it acts as a key to obtain a new access token. Furthermore, the third-party server maintains a table that records the corresponding refresh token and its expiration time, as well as the access token and its expiration time, based on the connector sequence number.

[0105] Therefore, when the validity period of the access token exceeds its expiration date (e.g., 7 days), a new access token is obtained by refreshing the token. For more information, please refer to [link to relevant documentation]. Figure 4 Before obtaining a new access token by refreshing the token, you need to check if the refresh token has expired. If the refresh token has not expired, you can obtain a new access token by refreshing the token; otherwise, you need to reapply for an access token and refresh token according to step 2. The refresh token has a longer validity period than the access token.

[0106] As can be seen, according to this embodiment, users do not need to manage multiple sets of accounts and passwords, and it also prevents unauthorized users from accessing third-party servers. When the diagnostic client needs to access a third-party server, the diagnostic client can determine whether it has an expired access token. If so, the diagnostic client automatically uses the access token to access the third-party server, so that the user is unaware that they need to log in to the third-party server and can successfully access it. This embodiment can also automatically refresh the access token, providing a seamless authentication solution.

[0107] The following describes a data processing apparatus provided in an embodiment of this application. The implementation steps of the data processing apparatus described below can be referred to in conjunction with those of the above embodiments.

[0108] Please see Figure 5 This embodiment provides a data processing device applied to a diagnostic client corresponding to a diagnostic server, including:

[0109] Module 501 is used to obtain access parameters generated based on the user's access to the third-party server.

[0110] The query module 502 is used to query the access token of the third-party server in itself based on the access parameters;

[0111] The signature module 503 is used to obtain an access signature based on the access token and access parameters if an access token is found and is available.

[0112] The sending module 504 is used to send the access signature and access parameters to the third-party server, so that the third-party server can verify the access signature based on the access parameters and its own stored access token, and then return the response data of the access parameters to the diagnostic client.

[0113] In one implementation, the signature module is specifically used for:

[0114] The access token is valid within the access period.

[0115] In one implementation, it further includes:

[0116] The first refresh module is used to query the refresh parameters for refreshing the access token if an access token is found but is unavailable. If the refresh parameters are found and are available, the refresh parameters are sent to the third-party server so that the third-party server can return a new token and its access validity period, as well as new parameters for refreshing the new token and their refresh validity period, to the diagnostic client after verifying that the refresh parameters are valid. The refresh validity period is longer than the access validity period.

[0117] In one implementation, it further includes:

[0118] The first storage module is used to store the new token and its access validity period, new parameters and their refresh validity period; if the access parameters are obtained, the new token is used as the access token, and the module queries the third-party server's access token in its own memory according to the access parameters; if the access token is found and is available, the access signature is obtained based on the access token and access parameters; the access signature and access parameters are sent to the third-party server, so that the third-party server verifies the access signature based on the access parameters and the access token stored in its own memory, and then returns the response data of the access parameters to the diagnostic client.

[0119] In one implementation, the refresh module is specifically used for:

[0120] The refresh parameters are within the refresh period.

[0121] In one implementation, it further includes:

[0122] The application module is used to determine the connector serial number and connector identifier corresponding to the diagnostic client, and the device identifier of the diagnostic device where the diagnostic client is located, if no access token is found, no refresh parameters for refreshing the access token are found, or the refresh parameters for refreshing the access token are found but the refresh parameters are unavailable; obtain an identity signature based on the device identifier, connector serial number, and connector identifier; send the identity signature, device identifier, and connector serial number to the third-party server, so that the third-party server can verify the identity signature based on the device identifier, its own stored connector serial number, and its own stored connector identifier, and return the access token and its access validity period, the refresh parameters for refreshing the access token, and their refresh validity period to the diagnostic client; and store the access token and its access validity period, and the refresh parameters and their refresh validity period.

[0123] As can be seen, the data processing device provided in this embodiment allows users to be unaware of the process of logging into a third-party server. The diagnostic client can automatically log into the third-party server and complete the access process based on the user's operation of accessing the third-party server, without the user having to manually repeat the login operation, making the access process simpler and improving access efficiency.

[0124] The following describes another data processing apparatus provided in the embodiments of this application. The implementation steps of the data processing apparatus described below can be referred to each other with those of the above embodiments.

[0125] Please see Figure 6 This embodiment provides a data processing device applied to a third-party server, including:

[0126] The receiving module 601 is used to receive the access signature and access parameters sent by the diagnostic client corresponding to the diagnostic server; wherein, the access parameters are generated by the diagnostic client based on the user's operation of accessing the third-party server; the access signature is obtained by the diagnostic client based on the access token and access parameters when it determines that its stored access token is available;

[0127] The verification module 602 is used to verify the access signature based on the access parameters and the access token corresponding to the diagnostic client stored in its own memory;

[0128] Return module 603 is used to return response data of access parameters to the diagnostic client if the access signature verification is successful.

[0129] In one implementation, the verification module is specifically used for:

[0130] Query the access token corresponding to the diagnostic client within itself;

[0131] Generate a signature based on the retrieved access token and access parameters;

[0132] If the generated signature matches the access signature, the access signature verification passes; otherwise, the access signature verification fails.

[0133] In one implementation, it further includes:

[0134] The second refresh module is used to receive refresh parameters sent by the diagnostic client for refreshing the access token; query the corresponding refresh parameters of the diagnostic client in itself; if the refresh parameters found are consistent with the refresh parameters sent by the diagnostic client, it returns the new token and its access validity period, the new parameters used to refresh the new token and their refresh validity period to the diagnostic client, so that the diagnostic client stores the new token and its access validity period, the new parameters and their refresh validity period; the refresh validity period is greater than the access validity period.

[0135] In one implementation, it further includes:

[0136] The authentication module receives the identity signature, device identifier, and connector serial number sent by the diagnostic client. The device identifier is the identifier of the diagnostic device where the diagnostic client is located. The diagnostic client has a corresponding connector serial number and connector identifier. The identity signature is obtained based on the device identifier, connector serial number, and connector identifier. The identity signature is verified based on the device identifier, the connector serial number stored in the module, and the connector identifier stored in the module. If the identity signature verification is successful, the module returns an access token and its access validity period, as well as refresh parameters and their refresh validity period for refreshing the access token, to the diagnostic client so that the diagnostic client can store the access token and its access validity period, refresh parameters, and their refresh validity period.

[0137] In one implementation, it further includes:

[0138] The second storage module is used to obtain and store the connector serial number and connector identifier from the diagnostic server.

[0139] In one implementation, it further includes:

[0140] The logging module is used to record the access tokens and corresponding refresh parameters for multiple diagnostic clients.

[0141] As can be seen, the data processing device provided in this embodiment allows users to be unaware of the process of logging into a third-party server. The diagnostic client can automatically log into the third-party server and complete the access process based on the user's operation of accessing the third-party server, without the user having to manually repeat the login operation, making the access process simpler and improving access efficiency.

[0142] The following describes an electronic device provided by an embodiment of this application. The implementation steps of the electronic device described below can be referred to in conjunction with those of the above embodiments.

[0143] Furthermore, embodiments of this application also provide an electronic device. The aforementioned electronic device can be, for example,... Figure 7 The server 50 shown can also be as follows: Figure 8 Terminal 60 is shown. Figure 7 and Figure 8 These are all diagrams illustrating the structure of an electronic device according to an exemplary embodiment. The content in the diagrams should not be considered as any limitation on the scope of this application.

[0144] Figure 7 This is a schematic diagram of a server structure provided in an embodiment of this application. The server 50 may specifically include: at least one processor 51, at least one memory 52, a power supply 53, a communication interface 54, an input / output interface 55, and a communication bus 56. The memory 52 stores a computer program, which is loaded and executed by the processor 51 to implement the relevant steps in the access process disclosed in any of the foregoing embodiments.

[0145] In this embodiment, the power supply 53 is used to provide operating voltage for each hardware device on the server 50; the communication interface 54 can create a data transmission channel between the server 50 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 55 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0146] In addition, the memory 52, as a carrier for resource storage, can be a read-only memory, random access memory, disk, or optical disk, etc. The resources stored on it include operating system 521, computer program 522, and data 523, etc., and the storage method can be temporary storage or permanent storage.

[0147] The operating system 521 manages and controls the various hardware devices and computer programs 522 on the server 50 to enable the processor 51 to perform operations and processing on the data 523 in the memory 52. ​​The operating system 521 can be Windows Server, Netware, Unix, Linux, etc. The computer program 522, in addition to including computer programs capable of performing the data processing methods disclosed in any of the foregoing embodiments, may further include computer programs capable of performing other specific tasks. The data 523 may include application update information and application developer information, among other things.

[0148] Figure 8 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application. The terminal 60 may specifically include, but is not limited to, a smartphone, tablet computer, laptop computer, or desktop computer.

[0149] Typically, the terminal 60 in this embodiment includes a processor 61 and a memory 62.

[0150] The processor 61 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 61 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 61 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 61 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 61 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0151] The memory 62 may include one or more computer-readable storage media, which may be non-transitory. The memory 62 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In this embodiment, the memory 62 is used to store at least the following computer program 621, which, after being loaded and executed by the processor 61, is capable of implementing the relevant steps in the data processing method executed by the terminal side as disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 62 may also include an operating system 622 and data 623, and the storage method may be temporary storage or permanent storage. The operating system 622 may include Windows, Unix, Linux, etc. The data 623 may include, but is not limited to, application update information.

[0152] In some embodiments, the terminal 60 may further include a display screen 63, an input / output interface 64, a communication interface 65, a sensor 66, a power supply 67, and a communication bus 68.

[0153] Those skilled in the art will understand that Figure 8 The structure shown does not constitute a limitation on terminal 60 and may include more or fewer components than shown.

[0154] The following describes a storage medium provided in an embodiment of this application. The implementation steps of the storage medium described below can be referred to in conjunction with those of the above embodiments.

[0155] Furthermore, this application also discloses a storage medium storing computer-executable instructions. When these instructions are loaded and executed by a processor, they implement the data processing method disclosed in any of the foregoing embodiments. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0156] It should be noted that the above are merely preferred embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

[0157] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0158] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A data processing method, characterized in that, The diagnostic client applied to the diagnostic server includes: Retrieve access parameters generated based on the user's actions when accessing a third-party server; Based on the access parameters, query the access token of the third-party server within itself; If the access token is found and is available, then the access signature is obtained based on the access token and the access parameters; The access signature and the access parameters are sent to the third-party server, so that the third-party server verifies the access signature based on the access parameters and the access token stored in itself, and then returns the response data of the access parameters to the diagnostic client. If the access token is not found, or the refresh parameter for refreshing the access token is not found, or the refresh parameter for refreshing the access token is found but the refresh parameter is unavailable, then the connector serial number and connector identifier corresponding to the diagnostic client, and the device identifier of the diagnostic device where the diagnostic client is located are determined. An identity signature is obtained based on the device identifier, the connector serial number, and the connector identifier; The identity signature, device identifier, and connector serial number are sent to the third-party server. The third-party server verifies the identity signature based on the device identifier, its stored connector serial number, and its stored connector identifier. Upon successful verification, the server returns the access token and its access validity period, along with refresh parameters and their validity period, to the diagnostic client. Alternatively, the diagnostic server provides an access interface to the third-party server, allowing the third-party server to obtain the connector serial number and connector identifier corresponding to the diagnostic client from the diagnostic server. The diagnostic server may also proactively send the connector serial number and connector identifier corresponding to the diagnostic client to the third-party server. The access token and its access validity period, and the refresh parameters and their refresh validity period are stored.

2. The method according to claim 1, characterized in that, Also includes: If the access token is found but is unavailable, then query the refresh parameters for refreshing the access token within the query function itself. If the refresh parameters are found and are available, the refresh parameters are sent to the third-party server, so that after verifying that the refresh parameters are valid, the third-party server returns a new token and its access validity period, as well as new parameters for refreshing the new token and their refresh validity period to the diagnostic client; the refresh validity period is longer than the access validity period.

3. A data processing method, characterized in that, Applied to third-party servers, including: The diagnostic client receives an access signature and access parameters sent by the diagnostic server; wherein, the access parameters are generated by the diagnostic client based on the user's access to the third-party server; and the access signature is obtained by the diagnostic client based on the access token and the access parameters when it determines that its stored access token is available. The access signature is verified based on the access parameters and the access token corresponding to the diagnostic client stored within itself. If the access signature verification passes, the response data of the access parameters is returned to the diagnostic client; The diagnostic client sends an identity signature, a device identifier, and a connector serial number; wherein the device identifier is the identifier of the diagnostic device on which the diagnostic client resides; the diagnostic client corresponds to the connector serial number and the connector identifier; the identity signature is obtained based on the device identifier, the connector serial number, and the connector identifier. The identity signature is verified based on the device identifier, the connector serial number stored in the device, and the connector identifier stored in the device; wherein, the diagnostic server provides an access interface to the third-party server so that the third-party server can obtain the connector serial number and connector identifier corresponding to the diagnostic client from the diagnostic server; or, the diagnostic server actively sends the connector serial number and connector identifier corresponding to the diagnostic client to the third-party server. If the identity signature verification passes, the access token and its access validity period, as well as the refresh parameters and their refresh validity period for refreshing the access token, are returned to the diagnostic client, so that the diagnostic client stores the access token and its access validity period, and the refresh parameters and their refresh validity period.

4. The method according to claim 3, characterized in that, Also includes: Receive refresh parameters sent by the diagnostic client to refresh the access token; Query the refresh parameters corresponding to the diagnostic client within itself; If the refresh parameters found are consistent with the refresh parameters sent by the diagnostic client, a new token and its access validity period, new parameters for refreshing the new token and their refresh validity period are returned to the diagnostic client, so that the diagnostic client stores the new token and its access validity period, the new parameters and their refresh validity period; the refresh validity period is greater than the access validity period.

5. A data processing apparatus, characterized in that, The diagnostic client applied to the diagnostic server includes: The acquisition module is used to acquire access parameters generated based on the user's actions when accessing a third-party server. The query module is used to query the access token of the third-party server in itself based on the access parameters; The signature module is used to obtain an access signature based on the access token and the access parameters if the access token is found and the access token is available. The sending module is used to send the access signature and the access parameters to the third-party server, so that after the third-party server verifies the access signature based on the access parameters and the access token stored in itself, it returns the response data of the access parameters to the diagnostic client. The application module is used to determine the connector serial number and connector identifier corresponding to the diagnostic client, and the device identifier of the diagnostic device where the diagnostic client is located, if the access token is not found, or the refresh parameters for refreshing the access token are not found, or the refresh parameters for refreshing the access token are found but the refresh parameters are unavailable; obtain an identity signature based on the device identifier, the connector serial number, and the connector identifier; send the identity signature, the device identifier, and the connector serial number to the third-party server, so that the third-party server verifies the identity signature based on the device identifier, the connector serial number stored in its own memory, and the connector identifier stored in its own memory, and then returns the access token and its access validity period, and the refresh parameters for refreshing the access token and their refresh validity period to the diagnostic client; wherein, the diagnostic server provides an access interface to the third-party server so that the third-party server can obtain the connector serial number and connector identifier corresponding to the diagnostic client from the diagnostic server; or, the diagnostic server actively sends the connector serial number and connector identifier corresponding to the diagnostic client to the third-party server; and stores the access token and its access validity period, and the refresh parameters and their refresh validity period.

6. A data processing apparatus, characterized in that, Applied to third-party servers, including: The receiving module is used to receive the access signature and access parameters sent by the diagnostic client corresponding to the diagnostic server; wherein, the access parameters are generated by the diagnostic client based on the user's operation of accessing the third-party server; the access signature is obtained by the diagnostic client based on the access token and the access parameters when it determines that its stored access token is available; The verification module is used to verify the access signature based on the access parameters and the access token corresponding to the diagnostic client stored in its own memory; The return module is used to return response data of the access parameters to the diagnostic client if the access signature verification passes. The authentication module is used to receive an identity signature, device identifier, and connector serial number sent by the diagnostic client; wherein the device identifier is the identifier of the diagnostic device where the diagnostic client is located; the diagnostic client has a corresponding connector serial number and connector identifier; the identity signature is obtained based on the device identifier, the connector serial number, and the connector identifier; the identity signature is verified based on the device identifier, the connector serial number stored in the module, and the connector identifier stored in the module; wherein the diagnostic server provides an access interface to the third-party server so that the third-party server can obtain the connector serial number and connector identifier corresponding to the diagnostic client from the diagnostic server; or, the diagnostic server actively sends the connector serial number and connector identifier corresponding to the diagnostic client to the third-party server; if the identity signature verification is successful, the access token and its access validity period, and refresh parameters and their refresh validity period are returned to the diagnostic client so that the diagnostic client can store the access token and its access validity period, and the refresh parameters and their refresh validity period.

7. An electronic device, characterized in that, The electronic device includes a processor and a memory; wherein the memory is used to store a computer program, which is loaded and executed by the processor to implement the method as claimed in any one of claims 1 to 4.

8. A storage medium, characterized in that, The storage medium stores computer-executable instructions, which, when loaded and executed by a processor, implement the method as described in any one of claims 1 to 4.

Images