Data calling method, device and terminal equipment

Abstract

This specification provides a data calling method, apparatus and terminal device. When a third-party application detects that a user's operation meets a preset trigger condition and needs to call a target service, it generates a target calling request and generates a third-party signature using the private key of the third-party application; then sends the target calling request and the third-party signature to the authorization plug-in; the authorization plug-in signs the target calling request and sends the signed target calling request and the third-party signature to the open API platform of the associated target business party; the platform responds to the target calling request based on the signed target calling request and the third-party signature, and calls the target service to obtain the corresponding target result if the preset verification passes. Therefore, under the premise of protecting the security of user data, when the user operates in a third-party application, the target service of the required target business party can be automatically and securely called, thereby improving the user experience and reducing the intrusion into third-party applications.

Description

Technical Field

[0001] This specification belongs to the field of Internet technology, and in particular to data calling methods, devices and terminal equipment. Background Art

[0002] Based on the open API platform (Open API) technology, the website platform can encapsulate the website services provided into multiple APIs (Application Programming Interface) and open them up for third-party calls.

[0003] However, based on the existing methods, when third parties call the above website services, in order to protect the user's data privacy and security, they often need to perform cumbersome and complex user authorization verification, which increases the complexity of user operations and affects the user experience. In addition, based on the existing methods, it is inevitable that changes must be made to the third party internally, which may intrude on the third party.

[0004] To address the above problems, no effective solution has been proposed yet. Summary of the invention

[0005] This specification provides a data calling method, apparatus and terminal device, which can automatically and securely call the target service provided by the target business party required for the operation when the user operates in a third-party application, while protecting the privacy and security of user data, so as to improve the user experience and reduce the intrusion into the third-party application.

[0006] The embodiment of this specification provides a data calling method, which is applied to a third-party application, the third-party application is deployed in a terminal device, the terminal device is also deployed with an authorization plug-in associated with an open API platform of a target business party, the open API platform of the target business party provides multiple API interfaces, and the API interfaces respectively correspond to a business service provided by the target business party, the method includes:

[0007] When it is detected that the user's operation in the third-party application meets the preset trigger condition, a target call request for the target service of the target business party is generated, and a third-party signature is generated using the private key of the third-party application;

[0008] Wake up the authorization plug-in, and send the third-party signature and the target call request to the authorization plug-in; wherein the authorization plug-in signs the target call request to obtain the signed target call request; the authorization plug-in sends the signed target call request and the third-party signature to the open API platform of the target business party; the open API platform of the target business party calls the target service to obtain the corresponding target result according to the signed target call request and the third-party signature, if the preset verification passes;

[0009] The target result is received.

[0010] In some embodiments, after receiving the target result, the method further includes:

[0011] According to the target result, corresponding target data processing is performed.

[0012] In some embodiments, the third-party application includes: an APP of a third-party shopping platform; the target business party includes: an open bank.

[0013] In some embodiments, the target result includes: account credit data of the user;

[0014] Accordingly, according to the target result, corresponding target data processing is performed, including:

[0015] Determine the user's transaction risk level based on the user's account credit data;

[0016] Provide users with matching transaction services based on their transaction risk level.

[0017] In some embodiments, when it is detected that the user's operation in the third-party application meets a preset trigger condition, the method further includes:

[0018] Displaying prompt information about calling the target service of the target business party to the user;

[0019] When it is determined that a confirmation instruction of the user for the prompt information is received, a target call request for the target service of the target business party is generated, and a third-party signature is generated using a private key of the third-party application.

[0020] In some embodiments, the method further comprises:

[0021] Receiving and responding to a first registration instruction sent by the authorization plug-in, registering a third-party application through the authorization plug-in; wherein the authorization plug-in obtains an application identity certificate and an identity identifier of the third-party application;

[0022] The application identity certificate and identity identifier of the third-party application are sent to the open API platform of the target business party for registration and storage.

[0023] The embodiment of this specification also provides a data calling method, which is applied to an authorization plug-in, the authorization plug-in is associated with an open API platform of a target business party, the authorization plug-in is deployed on a terminal device, and the terminal device is also deployed with a third-party application, the method comprising:

[0024] Receive third-party signature and target call request sent by third-party application;

[0025] Signing the target call request to obtain a signed target call request;

[0026] The signed target call request and the third-party signature are sent to the open API platform of the target business party; wherein, the open API platform of the target business party calls the target service to obtain the corresponding target result based on the signed target call request and the third-party signature, if the preset verification passes.

[0027] In some embodiments, the method further comprises:

[0028] Display the user registration interface to the user;

[0029] Obtaining user registration information through the user registration interface;

[0030] According to the user's registration information, obtain the user's user identity certificate and identity identification;

[0031] The user's user identity certificate and identity identifier are sent to the target business party's open API platform for registration and storage.

[0032] In some embodiments, the method further comprises:

[0033] Generate a user private key based on the user's registration information; and save the user private key locally;

[0034] Accordingly,

[0035] The target call request is signed using the user private key to obtain a signed target call request.

[0036] In some embodiments, the method further comprises:

[0037] Check whether there are any unregistered third-party applications among the applications installed on the terminal device;

[0038] In the case where an unregistered third-party application is retrieved, a first registration instruction is sent to the third-party application.

[0039] In some embodiments, after sending the first registration instruction to the third-party application, the method further includes:

[0040] Registration information of third-party applications for receiving feedback from third-party applications;

[0041] Obtaining an application identity certificate and an identity identifier of the third-party application according to the registration information of the third-party application;

[0042] The application identity certificate and identity identifier of the third-party application are sent to the open API platform of the target business party for registration and storage.

[0043] In some embodiments, the method further comprises:

[0044] Respond to the user's authorization instruction and display the authorization setting interface to the user;

[0045] Obtain authorization parameters through the authorization setting interface;

[0046] Generate an authorization file based on the authorization parameters; and send the authorization file to the open API platform of the target business party for storage.

[0047] In some embodiments, the authorization parameter includes at least one of the following: an identity of an authorized application, a service identity of a service authorized to be called, an authorized operation type, an authorization time, and an authorization authority.

[0048] In some embodiments, after receiving the third-party signature and the target call request sent by the third-party application, the method further includes:

[0049] Verify third-party signatures;

[0050] When the third-party signature verification is passed, the target call request is signed to obtain a signed target call request.

[0051] The embodiment of this specification also provides a data calling method, which is applied to an open API platform of a target business party, wherein the open API platform of the target business party provides multiple API interfaces, and the API interfaces respectively correspond to a business service provided by the target business party, and the method includes:

[0052] Receiving the signed target call request and the third-party signature sent by the authorization plug-in; wherein the authorization plug-in is deployed on the terminal device; and the authorization plug-in is associated with the open API platform of the target business party;

[0053] Performing preset verification according to the signed target call request and the third-party signature;

[0054] When the preset verification passes, respond to the target call request and call the target service to obtain the corresponding target result.

[0055] In some embodiments, after obtaining the corresponding target result, the method further includes:

[0056] The target result is sent to a third-party application; wherein the third-party application is deployed on the terminal device where the authorization plug-in is located.

[0057] In some embodiments, a preset verification is performed based on the signed target call request and the third-party signature, including:

[0058] Performing a first verification on the third-party signature according to the saved application identity certificate and identity identifier of the third-party application;

[0059] Performing a second verification on the signed target call request according to the stored user identity certificate and identity identifier of the user;

[0060] When it is determined that the first verification is passed and the second verification is passed, it is determined that the preset verification is passed.

[0061] In some embodiments, when it is determined that the preset verification is passed, the method further includes:

[0062] According to the authorization document, the request content of the target call request is verified.

[0063] The embodiment of this specification also provides a data calling device, including:

[0064] A generation module, used to generate a target call request for a target service of a target business party and generate a third-party signature using a private key of the third-party application when detecting that an operation of a user in a third-party application meets a preset trigger condition;

[0065] A sending module is used to wake up the authorization plug-in and send the third-party signature and the target call request to the authorization plug-in; wherein the authorization plug-in signs the target call request to obtain the signed target call request; the authorization plug-in sends the signed target call request and the third-party signature to the open API platform of the target business party; the open API platform of the target business party calls the target service to obtain the corresponding target result according to the signed target call request and the third-party signature, if the preset verification passes;

[0066] A receiving module is used to receive the target result.

[0067] The embodiment of this specification also provides a data calling device, including:

[0068] A receiving module, used for receiving a third-party signature and a target call request sent by a third-party application;

[0069] A signature module, used to sign the target call request to obtain a signed target call request;

[0070] A sending module is used to send the signed target call request and the third-party signature to the open API platform of the target business party; wherein, the open API platform of the target business party calls the target service to obtain the corresponding target result based on the signed target call request and the third-party signature, if the preset verification passes.

[0071] The embodiment of this specification also provides a data calling device, including:

[0072] A receiving module, used to receive the signed target call request and the third-party signature sent by the authorization plug-in; wherein the authorization plug-in is deployed in the terminal device; and the authorization plug-in is associated with the open API platform of the target business party;

[0073] A verification module, used to perform preset verification according to the signed target call request and the third-party signature;

[0074] The calling module is used to respond to the target calling request and call the target service to obtain the corresponding target result when the preset verification is passed.

[0075] The embodiment of the present specification also provides a terminal device, including a processor and a memory for storing processor executable instructions, and the processor implements the relevant steps of the data calling method when executing the instructions.

[0076] The embodiments of the present specification also provide a computer-readable storage medium on which computer instructions are stored, and when the instructions are executed, the relevant steps of the data calling method are implemented.

[0077] Based on the data calling method, device and terminal device provided in this specification, when a user operates in a third-party application deployed in the terminal device, the third-party application can automatically generate a target calling request for the target service of the target business party when it detects that the user's operation meets the preset trigger condition and needs to call the target service provided by the target business party, and use the private key of the third-party application to generate a third-party signature; further, the third-party application can wake up the authorization plug-in deployed in the same terminal device, and send the above target calling request and the third-party signature to the authorization plug-in; the authorization plug-in signs the target calling request to obtain the signed target calling request; then sends the signed target calling request and the third-party signature to the open API platform of the associated target business party; the open API platform performs preset verification according to the signed target calling request and the third-party signature; when the preset verification passes, respond to the target calling request, call the target service to obtain the corresponding target result, and feed the target result back to the third-party application. Therefore, under the premise of protecting the privacy and security of user data, when the user operates in the third-party application, the target service provided by the target business party required for the operation can be automatically and safely called, which improves the user experience and reduces the intrusion into the third-party application. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] In order to more clearly illustrate the embodiments of this specification, the drawings required for use in the embodiments will be briefly introduced below. The drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0079] Figure 1 It is a schematic diagram of an embodiment of an interface of a terminal device to which the data calling method provided in the embodiments of this specification is applied;

[0080] Figure 2 It is a schematic diagram of an embodiment of applying the data calling method provided by the embodiments of this specification in a scenario example;

[0081] Figure 3 It is a schematic diagram of an embodiment of applying the data calling method provided by the embodiments of this specification in a scenario example;

[0082] Figure 4 is a flowchart of a data calling method provided by an embodiment of this specification;

[0083] Figure 5 is a flowchart of a data calling method provided by an embodiment of this specification;

[0084] Figure 6is a flowchart of a data calling method provided by an embodiment of this specification;

[0085] Figure 7 is a schematic diagram of the structure of a terminal device provided by an embodiment of this specification;

[0086] Figure 8 It is a schematic diagram of the structure of a data calling device provided by an embodiment of this specification. DETAILED DESCRIPTION

[0087] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.

[0088] The embodiments of the present specification provide a data calling method, which can be specifically applied to a terminal device (eg, a user's mobile phone).

[0089] For details, please refer to Figure 1 As shown, at least a third-party application (e.g., XX shopping website APP) and an authorization plug-in (e.g., YY authorization APP) associated with the open API platform of the target business party (e.g., YY open bank) are deployed in the terminal device (e.g., smart phone, etc.). The authorization plug-in can communicate and interact with the open API platform of the target business party.

[0090] Among them, the open API platform of the target business party can be specifically understood as an open platform built by the target business party based on Open API technology. Through this open platform, the target business party can encapsulate the services provided into multiple corresponding API interfaces and open the above API interfaces to the outside world so that third-party applications can call the corresponding services through the above API interfaces. The open API platform of the target business party can be specifically deployed on a cloud server or on a terminal device.

[0091] The above authorization plug-in can be specifically understood as an application associated with the open API platform of the target business party, which participates in the registration, authorization and other data processing related to the open API platform of the target business party on the terminal device. The authorization plug-in can communicate and interact with the open API platform of the target business party. Specifically, the above authorization plug-in can be an independent APP installed in the user's smartphone (for example, YY authorization APP), or it can be a plug-in module integrated in the APP related to the target business party (for example, the authorization module in the YY bank APP), etc.

[0092] The third-party application can be specifically understood as an application program of a third party that is deployed on the terminal device and is different from the target service provider. Specifically, the third-party application can be an application provided by a service provider that has a cooperative relationship with the target service provider.

[0093] The terminal device may specifically include a front-end electronic device applied to the user side and capable of realizing functions such as data collection and data transmission. Specifically, the terminal device may be, for example, a desktop computer, a tablet computer, a laptop computer, a smart phone, etc.

[0094] In some embodiments, before specific implementation, the user may use a terminal device to download and install the authorization plug-in through a website or link provided by the target business party.

[0095] In some embodiments, after the user has installed the authorization plug-in on the terminal device, the user can first start the authorization plug-in for the first time by clicking. Accordingly, the authorization plug-in will display the corresponding user registration interface to the user. Figure 2 As shown, the authorization plug-in can obtain the registration information input by the user through the user registration interface; and generate the user's user identity certificate and identity identifier based on the user's registration information. The above-mentioned user identity identifier (for example, it can be recorded as u) can specifically be the user's name, the user's account name, the user's identity number, or the user's registered mobile phone number and other identification information that can correspond to the user.

[0096] Specifically, the user registration interface can be an encrypted user registration interface based on a privacy protection mechanism. Accordingly, the user can complete the registration operation in a desensitized registration manner through the encrypted user registration interface. In this way, the authorization plug-in can smoothly obtain the required user registration information; at the same time, it can also effectively prevent the user's personal privacy information from being leaked, protecting the user's data security.

[0097] When generating a user identity certificate, the authorization plug-in can first generate the user's public key (which can be recorded as PK(u)) and user private key (which can be recorded as SK(u)) for the user based on the user's registration information. Then, based on the user's private key and user's identity, generate a user identity certificate for the user, which can be expressed as the following formula to generate the corresponding user identity certificate: [u, SK(u), CA] Sk(CA) The CA may be the identity of the authorized plug-in, and SK (CA) may be the plug-in private key of the authorized plug-in. At the same time, the authorized plug-in may store the user private key SK (u) locally.

[0098] Next, the authorization plug-in can send the user's user identity certificate and identity identifier to the target business party's open API platform. The target business party's open API platform can specifically register and save the user's user identity certificate and identity identifier for subsequent use. Figure 2 shown.

[0099] In some embodiments, the authorization plug-in deployed on the terminal device can receive and respond to retrieval instructions initiated by the user, or the authorization plug-in is automatically triggered when it detects that a new application has been installed on the terminal device, and searches for the applications currently installed on the terminal device to determine whether there is a cooperative relationship and unregistered third-party applications.

[0100] When the authorization plug-in retrieves an unregistered third-party application, it may generate and send a first registration instruction to the third-party application.

[0101] The third-party application can respond to the first registration instruction and feedback the registration information of the third-party application to complete the registration of the third-party application. During the specific registration, the third-party application can also complete the above registration by means of desensitized registration.

[0102] Accordingly, see Figure 2 As shown, the authorization plug-in can receive the registration information of the third-party application fed back by the third-party application (for example, the identity of the third-party application, the public key PK (v) of the third-party application, etc.); then generate the application identity certificate of the third-party application according to the registration information of the third-party application, and obtain the identity of the third-party application.

[0103] Next, the authorization plug-in can send the application identity certificate and identity identifier of the third-party application to the open API platform of the target business party. The open API platform of the target business party can specifically register and save the application identity identifier and identity certificate of the third-party application for subsequent use. Figure 2 shown.

[0104] In some embodiments, the user can use the authorization plug-in to perform corresponding authorization settings according to specific circumstances and processing requirements. Specifically, the user can initiate an authorization instruction in the authorization plug-in.

[0105] The authorization plug-in can respond to the authorization instruction and display the corresponding authorization setting interface to the user. The user can enter and set authorization parameters such as the identity of the authorized application (for example, the identity of XX shopping website XX), the service identifier of the service (for example, the account credit inquiry of the user of YY Open Bank, the credit risk prediction of the user, etc.), the authorized operation type (for example, the proxy signature operation, the proxy payment operation, etc.), the authorization time (for example, the effective duration of the authorization, the effective time period of the authorization, etc.), the authorization authority (for example, read-only, rewrite, callable interface function, etc.), etc. in the authorization setting interface.

[0106] Furthermore, the authorization plug-in can generate an authorization file that can describe the authorization relationship based on the above authorization parameters. The authorization file contains the above authorization parameters. Then the authorization file is sent to the open API platform of the target business party for storage for subsequent use. Figure 2 shown.

[0107] In some embodiments, during specific implementation, when a user performs an operation in a third-party application, the third-party application will detect in real time or at preset intervals (for example, every 5 seconds) whether the user's operation in the third-party application meets a preset trigger condition.

[0108] Specifically, the third-party application can determine whether the preset trigger condition is met by detecting whether the user's operation in the third-party application requires the use of the target result obtained by the target business party by calling the target service.

[0109] For example, when a third-party application detects that a user applies for an installment purchase service in the XX shopping app and needs to use the account credit data obtained by the account credit inquiry service of the user of YY Open Bank, it determines that the user's operation in the third-party application meets the preset trigger conditions.

[0110] When it is detected that the user's operation in the third-party application meets the preset trigger condition, the third-party application can automatically generate a target call request for the target server.

[0111] The target call request at least carries the identity of the third-party application. The target call request may further carry the identity of the user, the service identifier of the target service requested to be called, or the interface identifier of the API interface corresponding to the target service requested to be called.

[0112] At the same time, the third-party application can use the private key of the third-party application (which can be recorded as SK(v)) to generate a third signature.

[0113] In some embodiments, see Figure 3 As shown, the third-party application can first wake up the authorization plug-in, and then send the third-party signature and target call request to the authorization plug-in.

[0114] During specific implementation, the authorization plug-in may be in a dormant state, and the third-party application may wake up the authorization plug-in by sending preset trigger information to the authorization plug-in.

[0115] In some embodiments, after receiving the above-mentioned third-party signature and target call request, the authorization plug-in can first use the user private key (SK(u)) held to sign the target call request to obtain the signed target call request; and then send the signed target call request together with the third-party signature to the open API platform of the target business party.

[0116] The authorization plug-in can also first use the saved registration information of the third-party application to verify the third-party signature; if the third-party signature verification is passed, then sign the target call request to obtain the signed target call request; then send the signed target call request together with the third-party signature to the open API platform of the target business party. This can better protect the user's data privacy security.

[0117] In some embodiments, the open API platform of the target business party may receive the signed target call request and the third-party signature sent by the authorization plug-in. The open API platform of the target business party may first perform a preset verification based on the signed target call request and the third-party signature. The preset verification may specifically include: a first verification of the application identity of the third-party application, and a second verification of the user identity of the user.

[0118] When performing the preset verification, the open API platform of the target business party can first use the saved application identity certificate and identity identifier that the third party should use to perform a first verification on the third-party signature; at the same time, use the saved user identity certificate and identity identifier of the user to perform a second verification on the signed target call request.

[0119] If it is determined that both the first verification and the second verification have passed, it is determined that the preset verification has passed. Conversely, if it is determined that at least one of the first verification and the second verification has failed, it is determined that the preset verification has failed.

[0120] When it is determined that the preset verification fails, in order to protect the user's data security and prevent a third party from impersonating the user or other data party to call the target service using user information, the target business party's open API platform can refuse to respond to the target call request and generate a call prompt message, which will be sent to the terminal device to provide relevant reminders to the user, so as to better protect the user's data privacy security.

[0121] In some embodiments, when it is determined that the preset verification has passed, the open API platform of the target business party may further verify the request content of the target call request according to the saved authorization file.

[0122] Specifically, for example, the open API platform of the target business party can perform content verification on the specific request content of the target call request based on the authorization parameters and authorization relationship contained in the authorization file to determine whether the target service requested by the target call request complies with the authorization authority and whether it is within the authorization time, etc.

[0123] When the request content of the target call request is verified, the target call request is responded to, and the requested target service is called through the corresponding API interface to obtain the corresponding target result.

[0124] For example, the API interface corresponding to the user's account credit query is called to query the database of YY Bank to obtain the user's account credit data.

[0125] In some embodiments, during specific implementation, the target business party's open API platform can directly send the obtained target results to the third-party application. Figure 3 shown.

[0126] Of course, in some scenarios, the open API platform of the target business party may first send the target result to the authorization plug-in; and then the authorization plug-in forwards the target result to the third-party application.

[0127] In some embodiments, after receiving the target result, the third-party application may perform corresponding target data processing according to the target result.

[0128] Specifically, for example, XX Shopping APP can determine the transaction risk level of the user based on the user's account credit data provided by YY Open Bank; and further, based on the user's transaction risk level, determine whether to provide the user with the requested installment purchase service.

[0129] Through the above scenario examples, based on the data call method provided by the implementation of this specification, when the user operates in a third-party application deployed on the terminal device, the third-party application can automatically generate a target call request for the target service of the target business party when detecting that the user's operation meets the preset trigger condition, and generate a third-party signature using the private key of the third-party application; then wake up the authorization plug-in deployed on the same terminal device, and send the above target call request and the third-party signature to the authorization plug-in; the authorization plug-in signs the target call request to obtain the signed target call request; then send the signed target call request and the third-party signature to the open API platform of the associated target business party; the open API platform performs preset verification based on the signed target call request and the third-party signature; if the preset verification passes, respond to the target call request, call the target service to obtain the corresponding target result, and feed the target result back to the third-party application. Therefore, under the premise of protecting the privacy and security of user data, when the user operates in the third-party application, it can automatically and safely call the target service provided by the target business party required for the operation in a user-weakly perceived manner, reducing user operations and improving user experience; at the same time, since there is no need to make a lot of changes to the third-party application, the intrusion into the third-party application is also reduced.

[0130] See also Figure 4 As shown, an embodiment of this specification provides a data calling method. Among them, the method is specifically applied to a third-party application. The third-party application is deployed on a terminal device, and the terminal device is also equipped with an authorization plug-in associated with the open API platform of the target business party. The open API platform of the target business party provides multiple API interfaces, and the API interfaces correspond to a business service provided by the target business party. In specific implementation, the method may include the following contents.

[0131] S401: When it is detected that the operation of the user in the third-party application meets the preset triggering condition, a target call request for the target service of the target business party is generated, and a third-party signature is generated using the private key of the third-party application.

[0132] S402: Wake up the authorization plug-in, and send the third-party signature and the target call request to the authorization plug-in; wherein the authorization plug-in signs the target call request to obtain the signed target call request; the authorization plug-in sends the signed target call request and the third-party signature to the open API platform of the target business party; the open API platform of the target business party calls the target service to obtain the corresponding target result based on the signed target call request and the third-party signature, if the preset verification passes.

[0133] S403: Receive the target result.

[0134] In some embodiments, the third-party application may be an application of a third party that has a cooperative relationship with the target business party. Alternatively, the third-party application may be an application of a third party that does not have a cooperative relationship with the target business party but the target business party allows the third party to call the provided service.

[0135] In some embodiments, the above situation where the preset trigger condition is met can be specifically understood as a situation where the relevant operation (or instruction) of the user in the third-party application needs to call the target service provided by the target business party.

[0136] In some embodiments, after receiving the target result, the method may further include: performing corresponding target data processing according to the target result.

[0137] In some embodiments, the third-party application may specifically include: an APP of a third-party shopping platform, etc.; the target business party may specifically include: an open bank, etc.

[0138] In some embodiments, the target result may specifically include: user's account credit data, etc.; accordingly, according to the target result, corresponding target data processing is performed, which may specifically include: determining the user's transaction risk level based on the user's account credit data; and providing matching transaction services to the user based on the user's transaction risk level.

[0139] Of course, it should be noted that the third-party applications, target business parties, target results, and target data processing listed above are only schematic illustrations. In specific implementation, according to specific application scenarios and processing requirements, the third-party applications, target business parties, target results, and target data processing may also include other types of applications, business parties, result data, data processing, etc.

[0140] For example, in the user's health management scenario, the third-party application can be a health management app installed on the user's mobile phone, and the target business party can be a hospital platform that stores and manages the user's physical examination data. Correspondingly, the target result can be the user's physical examination data, and the target data processing can be to predict the user's current health status based on the user's physical examination data and generate a health management plan that matches the user's current health status.

[0141] In some embodiments, when it is detected that the user's operation in the third-party application meets the preset trigger conditions, the method may also include the following when implemented: displaying prompt information about calling the target service of the target business party to the user; when it is determined that a confirmation instruction from the user for the prompt information is received, generating a target call request for the target service of the target business party, and generating a third-party signature using the private key of the third-party application.

[0142] When it is determined that no confirmation instruction is received from the user for the prompt information, the third-party application will not automatically generate a target call request and a third-party signature for the target service of the target business party.

[0143] Through the above embodiments, explicit authentication can be performed in an active prompting manner, so as to protect the user's control over private data while simplifying user operations.

[0144] In some embodiments, the method may further include the following when implemented:

[0145] S1: receiving and responding to a first registration instruction sent by an authorization plug-in, and registering a third-party application through the authorization plug-in; wherein the authorization plug-in obtains an application identity certificate and an identity identifier of the third-party application;

[0146] S2: Send the application identity certificate and identity identifier of the third-party application to the open API platform of the target business party for registration and storage.

[0147] Through the above embodiment, it is possible to avoid modifying the third-party application, so that the third-party application can automatically complete the relevant registration.

[0148] As can be seen from the above, the data calling method provided by the embodiment of this specification, when the user operates in a third-party application deployed on the terminal device, the third-party application can automatically generate a target calling request for the target service of the target business party when detecting that the user's operation meets the preset triggering condition, and use the private key of the third-party application to generate a third-party signature; then wake up the authorization plug-in deployed on the same terminal device, and send the above target calling request and the third-party signature to the authorization plug-in; the authorization plug-in signs the target calling request to obtain the signed target calling request; then send the signed target calling request and the third-party signature to the open API platform of the associated target business party; the open API platform performs preset verification according to the signed target calling request and the third-party signature; if the preset verification passes, respond to the target calling request, call the target service to obtain the corresponding target result, and feed the target result back to the third-party application. Therefore, under the premise of protecting the privacy and security of user data, when the user operates in the third-party application, the target service provided by the target business party required for the operation can be automatically and safely called, thereby improving the user's experience and reducing the intrusion into the third-party application.

[0149] See also Figure 5 As shown, the embodiment of this specification also provides a data calling method, which is applied to an authorization plug-in, the authorization plug-in is associated with the open API platform of the target business party, the authorization plug-in is deployed on a terminal device, and the terminal device is also deployed with a third-party application. Among them, when the method is specifically implemented, it can include the following contents.

[0150] S501: receiving a third-party signature and a target calling request sent by a third-party application.

[0151] S502: Sign the target call request to obtain a signed target call request.

[0152] S503: Send the signed target call request and the third-party signature to the open API platform of the target business party; wherein, the open API platform of the target business party calls the target service to obtain the corresponding target result based on the signed target call request and the third-party signature, if the preset verification passes.

[0153] In some embodiments, when the method is implemented, it may also include: displaying a user registration interface to the user; obtaining the user's registration information through the user registration interface; obtaining the user's user identity certificate and identity identifier based on the user's registration information; and sending the user's user identity certificate and identity identifier to the open API platform of the target business party for registration and storage.

[0154] In some embodiments, when the method is implemented, it may also include: generating a user private key based on the user's registration information; and saving the user private key locally; correspondingly, using the user private key to sign the target call request to obtain a signed target call request.

[0155] In some embodiments, when the method is specifically implemented, it may also include: searching whether there is an unregistered third-party application among the applications installed on the terminal device; when an unregistered third-party application is retrieved, sending a first registration instruction to the third-party application.

[0156] In some embodiments, after sending the first registration instruction to the third-party application, the method may also include: receiving registration information of the third-party application fed back by the third-party application; obtaining an application identity certificate and identity identifier of the third-party application based on the registration information of the third-party application; and sending the application identity certificate and identity identifier of the third-party application to the open API platform of the target business party for registration and storage.

[0157] In some embodiments, when the method is implemented, it may also include: responding to the user's authorization instruction and displaying the authorization setting interface to the user; obtaining authorization parameters through the authorization setting interface; generating an authorization file based on the authorization parameters; and sending the authorization file to the open API platform of the target business party for storage.

[0158] In some embodiments, the authorization parameters may specifically include at least one of the following: an identity identifier of an authorized application, a service identifier of a service authorized to be called, an authorized operation type, an authorization time, an authorization authority, and the like.

[0159] Of course, it should be noted that the authorization parameters listed above are only a schematic illustration. In specific implementation, according to specific application scenarios and processing requirements, the authorization parameters may also include other types of attribute parameters. This specification does not limit this.

[0160] In some embodiments, after receiving a third-party signature and a target call request sent by a third-party application, the method may also include: verifying the third-party signature; if the third-party signature verification passes, signing the target call request to obtain a signed target call request.

[0161] See also Figure 6As shown, the embodiment of this specification also provides a data calling method, which is applied to the open API platform of the target business party, and the open API platform of the target business party provides multiple API interfaces, and the API interfaces respectively correspond to a business service provided by the target business party. Among them, when the method is specifically implemented, it can include the following contents.

[0162] S601: receiving a signed target call request and a third-party signature sent by an authorization plug-in; wherein the authorization plug-in is deployed in a terminal device; and the authorization plug-in is associated with an open API platform of a target business party.

[0163] S602: Perform preset verification according to the signed target call request and the third-party signature.

[0164] S603: When the preset verification is passed, respond to the target call request and call the target service to obtain the corresponding target result.

[0165] In some implementations, after obtaining the corresponding target result, the method may further include: sending the target result to a third-party application; wherein the third-party application is deployed on the terminal device where the authorization plug-in is located.

[0166] In some implementations, the preset verification is performed based on the signed target call request and the third-party signature. When implemented specifically, the following contents may be included:

[0167] S1: Performing a first verification on the third-party signature according to the saved application identity certificate and identity identifier of the third-party application;

[0168] S2: Performing a second verification on the signed target call request according to the saved user identity certificate and identity identifier;

[0169] S3: When it is determined that the first verification is passed and the second verification is passed, it is determined that the preset verification is passed.

[0170] In some embodiments, when it is determined that the preset verification is passed, the method, when implemented, may further include: verifying the request content of the target call request according to the authorization file.

[0171] In some embodiments, the open API platform of the target business party begins to accumulate authorization time from the time the authorization file is received and saved; and at every preset time period, based on the authorization parameters in the saved authorization file, determines whether the authorization file is invalid by detecting whether the accumulated authorization time exceeds the authorization time.

[0172] When it is detected that the accumulated authorization time exceeds the authorization time and the authorization file is determined to be invalid, authorization update prompt information can be generated and sent to the authorization plug-in.

[0173] The authorization plug-in can display the authorization update prompt to the user through the terminal device, and receive the user's operation instruction for the authorization prompt information, and determine whether to update the authorization file according to the user's operation instruction for the authorization prompt information.

[0174] Specifically, when the received operation instruction is to confirm the update, the authorization plug-in can generate confirmation update information and send the confirmation update information to the open API platform of the target business party. The open API platform of the target business party can respond to the confirmation update information and re-accumulate the authorization time for the original authorization file. In this way, the user does not need to perform too many operations, and the original authorization file can be used efficiently and practically to update the authorization file.

[0175] On the contrary, if the received operation instruction is to determine not to update, the authorization plug-in can generate deletion information and send the deletion information to the open API platform of the target business party. The open API platform of the target business party can respond to the deletion information and delete the saved authorization file.

[0176] It can be seen from the above that based on the data calling method provided in the embodiments of this specification, while protecting the security of user data, when the user operates in a third-party application, it can automatically and securely call the target service of the required target business party, thereby improving the user experience and reducing the intrusion into third-party applications.

[0177] The embodiment of this specification also provides a terminal device, including a processor and a memory for storing processor executable instructions. When the processor is implemented, it can perform the following steps according to the instructions: when it is detected that the user's operation in the third-party application meets the preset trigger condition, generate a target call request for the target service of the target business party, and use the private key of the third-party application to generate a third-party signature; wake up the authorization plug-in, and send the third-party signature and the target call request to the authorization plug-in; wherein the authorization plug-in signs the target call request to obtain the signed target call request; the authorization plug-in sends the signed target call request and the third-party signature to the open API platform of the target business party; the open API platform of the target business party calls the target service according to the signed target call request and the third-party signature, and obtains the corresponding target result when the preset verification passes; and receives the target result.

[0178] In order to complete the above instructions more accurately, refer to Figure 7As shown, the embodiment of this specification also provides another specific terminal device, wherein the terminal device includes a network communication port 701, a processor 702 and a memory 703, and the above structures are connected through internal cables so that each structure can perform specific data interaction.

[0179] Among them, the network communication port 701 can be specifically used to generate a target call request for the target service of the target business party when it is detected that the user's operation in the third-party application meets the preset trigger condition, and generate a third-party signature using the private key of the third-party application.

[0180] The processor 702 can be specifically used to wake up the authorization plug-in and send the third-party signature and the target call request to the authorization plug-in; wherein the authorization plug-in signs the target call request to obtain the signed target call request; the authorization plug-in sends the signed target call request and the third-party signature to the open API platform of the target business party; the open API platform of the target business party calls the target service to obtain the corresponding target result based on the signed target call request and the third-party signature, if the preset verification passes; and receives the target result.

[0181] The memory 703 may be specifically used to store corresponding instruction programs.

[0182] In this embodiment, the network communication port 701 can be a virtual port that is bound to different communication protocols so that different data can be sent or received. For example, the network communication port can be a port responsible for web data communication, a port responsible for FTP data communication, or a port responsible for email data communication. In addition, the network communication port can also be a physical communication interface or communication chip. For example, it can be a wireless mobile network communication chip, such as GSM, CDMA, etc.; it can also be a Wifi chip; it can also be a Bluetooth chip.

[0183] In this embodiment, the processor 702 may be implemented in any appropriate manner. For example, the processor may take the form of a microprocessor or a processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) executable by the (micro)processor, a logic gate, a switch, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, etc. This specification does not limit this.

[0184] In this embodiment, the memory 703 may include multiple levels. In a digital system, anything that can store binary data can be a memory; in an integrated circuit, a circuit with a storage function that has no physical form is also called a memory, such as RAM, FIFO, etc.; in a system, a storage device with a physical form is also called a memory, such as a memory stick, TF card, etc.

[0185] The embodiments of the present specification also provide another terminal device, including a processor and a memory for storing processor executable instructions. When the processor is implemented, it can perform the following steps according to the instructions: receiving a third-party signature and a target call request sent by a third-party application; signing the target call request to obtain a signed target call request; sending the signed target call request and the third-party signature to the open API platform of the target business party; wherein, the open API platform of the target business party calls the target service to obtain the corresponding target result based on the signed target call request and the third-party signature, if a preset verification is passed.

[0186] The embodiments of this specification also provide another terminal device, including a processor and a memory for storing processor executable instructions. When the processor is implemented, it can perform the following steps according to the instructions: receiving a signed target call request and a third-party signature sent by an authorization plug-in; wherein the authorization plug-in is deployed in the terminal device; the authorization plug-in is associated with the open API platform of the target business party; performing a preset verification based on the signed target call request and the third-party signature; if the preset verification passes, responding to the target call request, calling the target service to obtain the corresponding target result.

[0187] The embodiment of this specification also provides a computer storage medium based on the above-mentioned data calling method, and the computer storage medium stores computer program instructions, which are implemented when executed: when it is detected that the user's operation in the third-party application meets the preset trigger condition, a target calling request for the target service of the target business party is generated, and a third-party signature is generated using the private key of the third-party application; the authorization plug-in is awakened, and the third-party signature and the target calling request are sent to the authorization plug-in; wherein the authorization plug-in signs the target calling request to obtain the signed target calling request; the authorization plug-in sends the signed target calling request and the third-party signature to the open API platform of the target business party; the open API platform of the target business party calls the target service according to the signed target calling request and the third-party signature, and obtains the corresponding target result when the preset verification passes; and receives the target result.

[0188] The embodiments of this specification also provide a computer storage medium based on the above-mentioned data calling method, wherein the computer storage medium stores computer program instructions, which, when executed, implement: receiving a third-party signature and a target calling request sent by a third-party application; signing the target calling request to obtain a signed target calling request; sending the signed target calling request and the third-party signature to the open API platform of the target business party; wherein the open API platform of the target business party calls the target service to obtain the corresponding target result based on the signed target calling request and the third-party signature, if a preset verification is passed.

[0189] The embodiment of this specification also provides a computer storage medium based on the above-mentioned data calling method, wherein the computer storage medium stores computer program instructions, which, when executed, implement: receiving a signed target calling request and a third-party signature sent by an authorization plug-in; wherein the authorization plug-in is deployed on a terminal device; the authorization plug-in is associated with an open API platform of a target business party; performing a preset verification based on the signed target calling request and the third-party signature; and when the preset verification passes, responding to the target calling request, calling the target service, and obtaining a corresponding target result.

[0190] In this embodiment, the storage medium includes but is not limited to a random access memory (RAM), a read-only memory (ROM), a cache, a hard disk (HDD) or a memory card. The memory may be used to store computer program instructions. The network communication unit may be an interface for network connection communication set in accordance with the standard specified by the communication protocol.

[0191] In this embodiment, the functions and effects specifically implemented by the program instructions stored in the computer storage medium can be explained in comparison with other implementations and will not be described in detail here.

[0192] See also Figure 8 As shown, at the software level, the embodiment of this specification also provides a data calling device, which may specifically include the following structural modules:

[0193] The generation module 801 may be specifically configured to generate a target call request for a target service of a target business party and generate a third-party signature using a private key of the third-party application when it is detected that the operation of the user in the third-party application meets a preset trigger condition;

[0194] The sending module 802 may be specifically used to wake up the authorization plug-in and send the third-party signature and the target call request to the authorization plug-in; wherein the authorization plug-in signs the target call request to obtain the signed target call request; the authorization plug-in sends the signed target call request and the third-party signature to the open API platform of the target business party; the open API platform of the target business party calls the target service to obtain the corresponding target result according to the signed target call request and the third-party signature, if the preset verification passes;

[0195] The receiving module 803 may be specifically configured to receive the target result.

[0196] It should be noted that the units, devices or modules described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. For the convenience of description, the above devices are described separately by functions divided into various modules. Of course, when implementing this specification, the functions of each module can be implemented in the same or more software and / or hardware, or the modules that implement the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0197] The embodiments of this specification also provide another data calling device, which may specifically include: a receiving module, which may be specifically used to receive a third-party signature and a target calling request sent by a third-party application; a signing module, which may be specifically used to sign the target calling request to obtain a signed target calling request; a sending module, which may be specifically used to send the signed target calling request and the third-party signature to the open API platform of the target business party; wherein the open API platform of the target business party calls the target service to obtain the corresponding target result based on the signed target calling request and the third-party signature, if a preset verification is passed.

[0198] The embodiments of this specification also provide another data calling device, which may specifically include: a receiving module, which may be specifically used to receive a signed target calling request and a third-party signature sent by an authorization plug-in; wherein the authorization plug-in is deployed on a terminal device; the authorization plug-in is associated with an open API platform of a target business party; a verification module, which may be specifically used to perform a preset verification based on the signed target calling request and the third-party signature; and a calling module, which may be specifically used to respond to a target calling request and call a target service to obtain a corresponding target result when the preset verification passes.

[0199] It can be seen from the above that the data calling device provided in the embodiment of this specification can, under the premise of protecting the privacy and security of user data, automatically and securely call the target service provided by the target business party required for the operation when the user operates in a third-party application, thereby improving the user experience and reducing the intrusion into third-party applications.

[0200] Although the present specification provides method operation steps as described in the embodiments or flow charts, more or fewer operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only order of execution. When the device or client product in practice is executed, it can be executed in sequence or in parallel according to the method shown in the embodiments or the drawings (for example, a parallel processor or a multi-threaded processing environment, or even a distributed data processing environment). The terms "include", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, product or device including a series of elements includes not only those elements, but also other elements that are not explicitly listed, or also includes elements inherent to such a process, method, product or device. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or device including the elements. The words first, second, etc. are used to represent the name, and do not represent any particular order.

[0201] Those skilled in the art also know that, in addition to implementing the controller in a purely computer-readable program code, the controller can be made to implement the same function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the devices for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules for implementing the method and structures within the hardware component.

[0202] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, classes, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media including storage devices.

[0203] Through the description of the above embodiments, it can be known that those skilled in the art can clearly understand that the present specification can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present specification can essentially be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a mobile terminal, a server, or a network device, etc.) to execute the methods described in each embodiment of the present specification or some parts of the embodiments.

[0204] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. This specification can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld devices or portable devices, tablet devices, multi-processor systems, microprocessor-based systems, set-top boxes, programmable electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc.

[0205] Although the present specification is described through embodiments, those skilled in the art will appreciate that there are many modifications and changes to the present specification without departing from the spirit of the present specification, and it is intended that the appended claims include these modifications and changes without departing from the spirit of the present specification.

Claims

1. A data calling method, characterized in that: Applied to a third-party application, the third-party application is an application program of a third party deployed on a terminal device, the terminal device is further deployed with an authorization plug-in associated with an open API platform of a target business party, the authorization plug-in is an application program participating in registration and authorization processing related to the open API platform of the target business party on the terminal device, the open API platform of the target business party provides a plurality of API interfaces, the API interfaces respectively correspond to a type of business service provided by the target business party, the method comprises: When it is detected that the user's operation in the third-party application meets the preset trigger condition, a target call request for the target service of the target business party is generated, and a third-party signature is generated using the private key of the third-party application; Wake up the authorization plug-in, and send the third-party signature and the target call request to the authorization plug-in; wherein the authorization plug-in signs the target call request to obtain the signed target call request; the authorization plug-in sends the signed target call request and the third-party signature to the open API platform of the target business party; the open API platform of the target business party calls the target service to obtain the corresponding target result according to the signed target call request and the third-party signature, if the preset verification passes; receiving the target result; Wherein, when the authorization plug-in participates in the registration and authorization processing of the user based on the open API platform of the target business party, it generates a user public key and a user private key for the user according to the user's registration information; the authorization plug-in generates a user identity certificate according to the user's user private key, the user's identity identifier, the identity identifier of the authorization plug-in and the plug-in private key of the authorization plug-in; the authorization plug-in sends the user identity certificate and the identity identifier to the open API platform of the target business party, and saves the user private key locally; the open API platform of the target business party registers and saves the user's user identity certificate and identity identifier for preset verification; the authorization plug-in signs the target call request with the user private key it holds, and obtains the signed target call request; The method further includes: receiving and responding to a first registration instruction sent by the authorization plug-in, registering a third-party application through the authorization plug-in; wherein the authorization plug-in obtains an application identity certificate and an identity identifier of the third-party application; and sending the application identity certificate and the identity identifier of the third-party application to the open API platform of the target business party for registration and storage; Among them, the preset verification includes: performing a first verification on the third-party signature based on the saved application identity certificate and identity identifier of the third-party application; performing a second verification on the signed target call request based on the saved user identity certificate and identity identifier of the user; and determining that the preset verification is passed when it is determined that the first verification passes and the second verification passes.

2. The method according to claim 1, characterized in that After receiving the target result, the method further includes: According to the target result, corresponding target data processing is performed.

3. The method according to claim 2, characterized in that The third-party application includes: the APP of the third-party shopping platform; the target business party includes: open banking.

4. The method according to claim 3, characterized in that: The target results include: user's account credit data; According to the target result, corresponding target data processing is performed, including: Determine the user's transaction risk level based on the user's account credit data; Provide users with matching transaction services based on their transaction risk level.

5. The method according to claim 1, characterized in that When it is detected that the user's operation in the third-party application meets a preset trigger condition, the method further includes: Displaying prompt information about calling the target service of the target business party to the user; When it is determined that a confirmation instruction of the user for the prompt information is received, a target call request for the target service of the target business party is generated, and a third-party signature is generated using a private key of the third-party application.

6. A data calling method, characterized in that: Applied to an authorization plug-in, the authorization plug-in is associated with an open API platform of a target business party, the authorization plug-in is deployed on a terminal device, the authorization plug-in is an application participating in registration and authorization processing related to the open API platform of the target business party on the terminal device, the terminal device is also deployed with a third-party application, the method includes: When it is detected that the user's operation in the third-party application meets the preset trigger condition, a target call request for the target service of the target business party is generated, and a third-party signature is generated using the private key of the third-party application; Receive third-party signature and target call request sent by third-party application; Signing the target call request to obtain a signed target call request; Send the signed target call request and the third-party signature to the open API platform of the target business party; wherein, the open API platform of the target business party calls the target service to obtain the corresponding target result according to the signed target call request and the third-party signature, if the preset verification passes; Wherein, when the authorization plug-in participates in the registration and authorization processing of the user based on the open API platform of the target business party, it generates a user public key and a user private key for the user according to the user's registration information; the authorization plug-in generates a user identity certificate according to the user's user private key, the user's identity identifier, the identity identifier of the authorization plug-in and the plug-in private key of the authorization plug-in; the authorization plug-in sends the user identity certificate and the identity identifier to the open API platform of the target business party, and saves the user private key locally; the open API platform of the target business party registers and saves the user's user identity certificate and identity identifier for preset verification; the authorization plug-in signs the target call request with the user private key to obtain the signed target call request; The method further includes: searching whether there is an unregistered third-party application among the applications installed on the terminal device; in the case of searching for an unregistered third-party application, sending a first registration instruction to the third-party application; receiving registration information of the third-party application fed back by the third-party application; obtaining an application identity certificate and an identity identifier of the third-party application according to the registration information of the third-party application; sending the application identity certificate and the identity identifier of the third-party application to the open API platform of the target business party for registration and storage; Among them, the preset verification includes: performing a first verification on the third-party signature based on the saved application identity certificate and identity identifier of the third-party application; performing a second verification on the signed target call request based on the saved user identity certificate and identity identifier of the user; and determining that the preset verification is passed when it is determined that the first verification passes and the second verification passes.

7. The method according to claim 6, characterized in that The method further comprises: Display the user registration interface to the user; Obtaining user registration information through the user registration interface; According to the user's registration information, obtain the user's user identity certificate and identity identification; The user's user identity certificate and identity identifier are sent to the target business party's open API platform for registration and storage.

8. The method according to claim 6, characterized in that The method further comprises: Respond to the user's authorization instruction and display the authorization setting interface to the user; Obtain authorization parameters through the authorization setting interface; Generate an authorization file based on the authorization parameters; and send the authorization file to the open API platform of the target business party for storage.

9. The method according to claim 8, characterized in that The authorization parameter includes at least one of the following: an identity of the authorized application, a service identity of the service authorized to be called, an authorized operation type, an authorization time, and an authorization authority.

10. The method according to claim 6, characterized in that After receiving the third-party signature and the target call request sent by the third-party application, the method further includes: Verify third-party signatures; When the third-party signature verification is passed, the target call request is signed to obtain a signed target call request.

11. A data calling method, characterized in that: An open API platform applied to a target business party, wherein the open API platform of the target business party provides a plurality of API interfaces, wherein the API interfaces respectively correspond to a business service provided by the target business party, and the method comprises: When it is detected that the user's operation in the third-party application meets the preset trigger condition, a target call request for the target service of the target business party is generated, and a third-party signature is generated using the private key of the third-party application; Receive the signed target call request and the third-party signature sent by the authorization plug-in; wherein the authorization plug-in is deployed on the terminal device; the authorization plug-in is associated with the open API platform of the target business party; the authorization plug-in is an application that participates in the registration and authorization processing related to the open API platform of the target business party on the terminal device; the third-party application is deployed on the terminal device where the authorization plug-in is located; Performing preset verification according to the signed target call request and the third-party signature; If the preset verification is passed, respond to the target call request, call the target service to obtain the corresponding target result; Wherein, when the authorization plug-in participates in the registration and authorization processing of the user based on the open API platform of the target business party, it generates a user public key and a user private key for the user according to the user's registration information; the authorization plug-in generates a user identity certificate according to the user's user private key, the user's identity identifier, the identity identifier of the authorization plug-in and the plug-in private key of the authorization plug-in; the authorization plug-in sends the user identity certificate and the identity identifier to the open API platform of the target business party, and saves the user private key locally; the open API platform of the target business party registers and saves the user's user identity certificate and identity identifier for preset verification; the signed target call request is obtained by the authorization plug-in signing the target call request using the user private key it holds; The method further includes: receiving and responding to a first registration instruction sent by the authorization plug-in, registering a third-party application through the authorization plug-in; wherein the authorization plug-in obtains an application identity certificate and an identity identifier of the third-party application; and sending the application identity certificate and the identity identifier of the third-party application to the open API platform of the target business party for registration and storage; Among them, according to the signed target call request and the third-party signature, a preset verification is performed, including: a first verification of the third-party signature is performed according to the saved application identity certificate and identity identifier of the third-party application; according to the saved user identity certificate and identity identifier of the user, a second verification is performed on the signed target call request; when it is determined that the first verification passes and the second verification passes, it is determined that the preset verification passes.

12. The method according to claim 11, characterized in that After obtaining the corresponding target result, the method further includes: The target result is sent to a third-party application.

13. The method according to claim 11, characterized in that When it is determined that the preset verification is passed, the method further includes: According to the authorization document, the request content of the target call request is verified.

14. A data calling device, characterized in that: Applied to a third-party application, the third-party application is an application program of a third party deployed on a terminal device, the terminal device is also deployed with an authorization plug-in associated with an open API platform of a target business party, the authorization plug-in is an application program participating in registration and authorization processing related to the open API platform of the target business party on the terminal device, the open API platform of the target business party provides multiple API interfaces, the API interfaces respectively correspond to a business service provided by the target business party, the device comprises: A generation module, used to generate a target call request for a target service of a target business party and generate a third-party signature using a private key of the third-party application when detecting that an operation of a user in a third-party application meets a preset trigger condition; A sending module is used to wake up the authorization plug-in and send the third-party signature and the target call request to the authorization plug-in; wherein the authorization plug-in signs the target call request to obtain the signed target call request; the authorization plug-in sends the signed target call request and the third-party signature to the open API platform of the target business party; the open API platform of the target business party calls the target service to obtain the corresponding target result according to the signed target call request and the third-party signature, if the preset verification passes; A receiving module, used for receiving the target result; Wherein, when the authorization plug-in participates in the registration and authorization processing of the user based on the open API platform of the target business party, it generates a user public key and a user private key for the user according to the user's registration information; the authorization plug-in generates a user identity certificate according to the user's user private key, the user's identity identifier, the identity identifier of the authorization plug-in and the plug-in private key of the authorization plug-in; the authorization plug-in sends the user identity certificate and the identity identifier to the open API platform of the target business party, and saves the user private key locally; the open API platform of the target business party registers and saves the user's user identity certificate and identity identifier for preset verification; the authorization plug-in signs the target call request with the user private key it holds, and obtains the signed target call request; The device is also used to: receive and respond to a first registration instruction sent by the authorization plug-in, and register a third-party application through the authorization plug-in; wherein the authorization plug-in obtains an application identity certificate and an identity identifier of the third-party application; and sends the application identity certificate and the identity identifier of the third-party application to the open API platform of the target business party for registration and storage; Among them, the preset verification includes: performing a first verification on the third-party signature based on the saved application identity certificate and identity identifier of the third-party application; performing a second verification on the signed target call request based on the saved user identity certificate and identity identifier of the user; and determining that the preset verification is passed when it is determined that the first verification passes and the second verification passes.

15. A data calling device, characterized in that: Applied to an authorization plug-in, the authorization plug-in is associated with the open API platform of the target business party, the authorization plug-in is deployed on a terminal device, the authorization plug-in is an application participating in the registration and authorization processing related to the open API platform of the target business party on the terminal device, the terminal device is also deployed with a third-party application, the device generates a target call request for a target service of the target business party when detecting that the operation of the user in the third-party application meets a preset trigger condition, and generates a third-party signature using the private key of the third-party application, the device includes: A receiving module, used for receiving a third-party signature and a target call request sent by a third-party application; A signature module, used to sign the target call request to obtain a signed target call request; A sending module, used to send the signed target call request and the third-party signature to the open API platform of the target business party; wherein, the open API platform of the target business party calls the target service to obtain the corresponding target result according to the signed target call request and the third-party signature, if the preset verification passes; Wherein, when the authorization plug-in participates in the registration and authorization processing of the user based on the open API platform of the target business party, it generates a user public key and a user private key for the user according to the user's registration information; the authorization plug-in generates a user identity certificate according to the user's user private key, the user's identity identifier, the identity identifier of the authorization plug-in and the plug-in private key of the authorization plug-in; the authorization plug-in sends the user identity certificate and the identity identifier to the open API platform of the target business party, and saves the user private key locally; the open API platform of the target business party registers and saves the user's user identity certificate and identity identifier for preset verification; the authorization plug-in signs the target call request with the user private key to obtain the signed target call request; The device is also used to: retrieve whether there is an unregistered third-party application among the applications installed in the terminal device; in the case of retrieving an unregistered third-party application, send a first registration instruction to the third-party application; receive registration information of the third-party application fed back by the third-party application; obtain an application identity certificate and an identity identifier of the third-party application according to the registration information of the third-party application; send the application identity certificate and the identity identifier of the third-party application to the open API platform of the target business party for registration and storage; Among them, the preset verification includes: performing a first verification on the third-party signature based on the saved application identity certificate and identity identifier of the third-party application; performing a second verification on the signed target call request based on the saved user identity certificate and identity identifier of the user; and determining that the preset verification is passed when it is determined that the first verification passes and the second verification passes.

16. A data calling device, characterized in that: An open API platform applied to a target business party, the open API platform of the target business party provides multiple API interfaces, each of which corresponds to a business service provided by the target business party. When the device detects that an operation of a user in a third-party application meets a preset trigger condition, it generates a target call request for a target service of the target business party, and generates a third-party signature using a private key of the third-party application. The device includes: A receiving module, used for receiving the signed target call request and the third-party signature sent by the authorization plug-in; wherein the authorization plug-in is deployed on the terminal device; the authorization plug-in is associated with the open API platform of the target business party; the authorization plug-in is an application participating in the registration and authorization processing related to the open API platform of the target business party on the terminal device; the third-party application is deployed on the terminal device where the authorization plug-in is located; A verification module, used to perform preset verification according to the signed target call request and the third-party signature; The calling module is used to respond to the target calling request and call the target service to obtain the corresponding target result when the preset verification passes; Wherein, when the authorization plug-in participates in the registration and authorization processing of the user based on the open API platform of the target business party, it generates a user public key and a user private key for the user according to the user's registration information; the authorization plug-in generates a user identity certificate according to the user's user private key, the user's identity identifier, the identity identifier of the authorization plug-in and the plug-in private key of the authorization plug-in; the authorization plug-in sends the user identity certificate and the identity identifier to the open API platform of the target business party, and saves the user private key locally; the open API platform of the target business party registers and saves the user's user identity certificate and identity identifier for preset verification; the signed target call request is obtained by the authorization plug-in signing the target call request using the user private key it holds; The device is also used to: receive and respond to a first registration instruction sent by the authorization plug-in, and register a third-party application through the authorization plug-in; wherein the authorization plug-in obtains an application identity certificate and an identity identifier of the third-party application; and sends the application identity certificate and the identity identifier of the third-party application to the open API platform of the target business party for registration and storage; Among them, according to the signed target call request and the third-party signature, a preset verification is performed, including: a first verification of the third-party signature is performed according to the saved application identity certificate and identity identifier of the third-party application; according to the saved user identity certificate and identity identifier of the user, a second verification is performed on the signed target call request; when it is determined that the first verification passes and the second verification passes, it is determined that the preset verification passes.

17. A terminal device, characterized in that: The method comprises a processor and a memory for storing processor-executable instructions, wherein the processor implements the steps of the method according to any one of claims 1 to 13 when executing the instructions.

18. A computer-readable storage medium, characterized in that: Computer instructions are stored thereon, and when the instructions are executed, the steps of the method according to any one of claims 1 to 13 are implemented.

Images