Search

CN-116028120-B - Application calling method and device

CN116028120BCN 116028120 BCN116028120 BCN 116028120BCN-116028120-B

Abstract

The invention discloses an application calling method and device, and relates to the technical field of computers. The method comprises the steps of uploading signature elements of a first application to a background system of an organization to carry out signature to obtain first signature information, calling a second application to execute first business processing through a calling application jump protocol request, calling parameters of the application jump protocol to comprise the first signature information, responding to a calling request of the second application to the first application initiated by the second application through a back application jump protocol to obtain parameters of the back application jump protocol, wherein the parameters comprise second signature information generated by the background system of the organization, verifying the second signature information through the background system of the organization, and calling the first application to execute second business processing after verification is passed. The method and the device can be suitable for mobile application mutual call under a double-layer operation architecture system, and ensure the safety and the non-tamper property of data transmission in the application call process.

Inventors

  • FAN XIN
  • ZHAO TIANWU
  • JIANG ZHIHUA
  • XU KEFENG

Assignees

  • 中国人民银行数字货币研究所

Dates

Publication Date
20260508
Application Date
20211027

Claims (16)

  1. 1. An application invocation method, comprising: Uploading signature elements of the first application to a background system of an organization to carry out signature to obtain first signature information; The method comprises the steps of initiating a call request for a second application through a call application jump protocol, wherein parameters of the call application jump protocol comprise first signature information, verifying the first signature information through a mechanism background system, and calling the second application to execute first business processing after the first signature information is verified; Responding to a call request of the second application to the first application initiated by a pull-back application jump protocol, and acquiring parameters of the pull-back application jump protocol, wherein the parameters of the pull-back application jump protocol comprise second signature information, and the second signature information is generated by a mechanism background system; And verifying the second signature information through the mechanism background system, and after the second signature information is verified, arousing the first application to execute second business processing, wherein the mechanism background system is a background system associated with the first application or the second application.
  2. 2. The method of claim 1, wherein uploading the signature element of the first application to an institution back office system for signing comprises: uploading a first element set formed by signature elements of the first application to the mechanism background system for encryption and signing, wherein the first element set comprises a first public element, a first parameter set and service custom parameters of the first application; The first public element comprises a time stamp and a validity period of the first signature information; In the case where the first application is a digital currency application and the second application is a third party application, the first set of parameters includes a service identifier; In the case where the first application is a third party application and the second application is a digital money application, the first parameter set includes the service identifier and an identification of the institution backend system, where the service identifier is used for the second application to perform the first service process corresponding to the service identifier.
  3. 3. The method of claim 2, wherein the first set of parameters further comprises first custom additional information if the first application is a digital money application and the second application is a third party application; In the case where the first application is a third party application and the second application is a digital money application, the first parameter set further includes a unique identification of the first application and/or second custom additional information; The first custom additional information or the second custom additional information comprises encryption signing algorithm information, and the second application utilizes the encryption signing algorithm information to verify and decrypt the first signature information.
  4. 4. A method according to any of claims 2 to 3, wherein the parameters evoking an application jump protocol further comprise a signature element of the first application, the first set of parameters.
  5. 5. The method of claim 1, wherein prior to requesting the second application to be invoked by the invoke application jump protocol, comprising constructing the invoke application jump protocol, the invoke application jump protocol comprising a protocol name, a host name, a path, and a parameter; In the case where the first application is a third party application and the second application is a digital money application, the protocol name, the host name, the path are provided by the second application; In the case where the first application is a digital currency application and the second application is a third party application, the protocol name, the host name, and the path are provided by the institution backend system, which is associated with the third party application.
  6. 6. The method of claim 1, wherein the parameters of the pull-back application jump protocol further comprise a second set of parameters, the second signature information being generated by the facility background system encrypting and signing a second set of elements, the second set of elements comprising the second set of parameters, the second set of parameters comprising a service identifier and an identity of the facility background system in the case where the first application is a digital currency application and the second application is a third party application; The verifying, by the institution backend system, the second signature information includes: And sending the parameters of the pull-back application jump protocol to a mechanism background system, checking and decrypting the second signature information by the mechanism background system, and checking and passing the second signature information when the second parameter set in the second element set obtained by decryption is consistent with the second parameter set obtained from the parameters of the pull-back application jump protocol.
  7. 7. An application invocation method, comprising: in response to a call request to a second application initiated by a first application through a call application jump protocol, acquiring parameters of the call application jump protocol, wherein the parameters of the call application jump protocol comprise first signature information, the first signature information is generated in an organization background system, and the organization background system is a background system associated with the first application or the second application; Verifying the first signature information through the mechanism background system, and after the first signature information is verified, invoking the second application to execute first business processing; signing the result of the first service processing through the mechanism background system to obtain second signature information; initiating a call request to the first application through a pull-back application jump protocol, wherein parameters of the pull-back application jump protocol comprise the second signature information; and verifying the second signature information through the mechanism background system, and after the second signature information is verified, calling the first application to execute second business processing.
  8. 8. The method of claim 7, wherein the parameters that evoke the application jump protocol further comprise a first set of parameters, the first signature information being generated by the facility back office system encrypting and signing a first set of elements, the first set of elements comprising the first set of parameters, the first set of parameters comprising a business identifier if the first application is a digital currency application and the second application is a third party application, the first set of parameters comprising the business identifier and an identification of the facility back office system if the first application is a third party application and the second application is a digital currency application, the business identifier being used by the second application to perform the first business process corresponding to the business identifier; the verifying, by the institution back-office system, the first signature information includes: And sending the parameters of the evoked application jump protocol to a background system of the mechanism, checking and decrypting the first signature information by the background system of the mechanism, and checking and passing the first signature information when a first parameter set in the first element set obtained by decryption is consistent with a first parameter set obtained from the parameters of the evoked application jump protocol.
  9. 9. The method of claim 7, wherein signing the result of the first business process by the facility back-office system comprises: Taking the result of the first service processing as a service custom parameter of the second application, and carrying out encryption and signature on a second element set through the mechanism background system, wherein the second element set comprises a second public element, a second parameter set and the service custom parameter of the second application; The second public element includes a time stamp and a validity period of the second signature information; In the case where the first application is a digital currency application and the second application is a third party application, the second set of parameters includes a service identifier and an identification of the institution's backend system; in the case where the first application is a third party application and the second application is a digital money application, the second set of parameters includes the service identifier; Wherein the service identifier is used for the first application to execute the second service processing corresponding to the service identifier.
  10. 10. The method according to claim 9, wherein in case the first application is a digital money application and the second application is a third party application, the second parameter set further comprises a unique identification of the second application and/or a first preset custom information; In the case that the first application is a third party application and the second application is a digital currency application, the second parameter set further includes second preset custom information; the first preset custom information or the second preset custom information comprises encryption signing algorithm information, and the first application uses the encryption signing algorithm information to check and decrypt the second signature information.
  11. 11. The method according to any of claims 9 to 10, wherein the parameters of the pull-back application jump protocol further comprise the second set of elements, the second set of parameters.
  12. 12. The method of claim 7, wherein prior to invoking the first application by a pull-back application-hopping protocol request, constructing the pull-back application-hopping protocol, the pull-back application-hopping protocol comprising a protocol name, a hostname, a path, and a parameter; In the case where the first application is a third party application and the second application is a digital money application, the protocol name, the host name, and the path are provided by the facility back-office system, the facility back-office system being associated with the third party application; In the case where the first application is a digital money application and the second application is a third party application, the protocol name, the host name, the path are provided by the first application.
  13. 13. An application invocation device, comprising: The signature element uploading module is used for uploading the signature element of the first application to the background system of the organization to carry out signature so as to obtain first signature information; A second application evoked module for requesting to evoke a second application by evoked application jump protocol to execute a first business process by the second application, the parameters of the evoked application jump protocol including the first signature information; The callback application parameter acquisition module is used for responding to a call request of the second application to the first application initiated by a callback application jump protocol, acquiring parameters of the callback application jump protocol, wherein the parameters of the callback application jump protocol comprise second signature information, and the second signature information is generated by the mechanism background system; And the first application arousing module is used for verifying the second signature information through the mechanism background system, and arousing the first application to execute second business processing after the second signature information passes the verification, wherein the mechanism background system is a background system associated with the first application or the second application.
  14. 14. An application invocation device, comprising: A evoked application parameter acquisition module, configured to acquire parameters of an evoked application jump protocol in response to an evoked request for a second application initiated by a first application through the evoked application jump protocol, where the parameters of the evoked application jump protocol include first signature information, the first signature information is generated in an organization background system, and the organization background system is a background system associated with the first application or the second application; The second application arousing execution module is used for verifying the first signature information through the mechanism background system, and arousing the second application to execute first business processing after the first signature information is verified; The signature information acquisition module is used for signing the result of the first service processing through the mechanism background system to obtain second signature information; And the first application arousal execution module is used for arousing the first application through a pull-back application jump protocol request so as to execute second business processing by the first application, and the parameters of the pull-back application jump protocol comprise the second signature information.
  15. 15. An electronic device, comprising: One or more processors; A memory for storing one or more programs, The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-12.
  16. 16. A computer readable medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method according to any of claims 1-12.

Description

Application calling method and device Technical Field The present invention relates to the field of computer technologies, and in particular, to an application calling method and apparatus. Background The double-layer operation architecture system is that legal digital currency is issued to a designated operation organization by a central bank in a digital currency system, and the designated operation organization is responsible for exchange and circulation transactions. In electronic payment consumption, especially in a dual-layer operation architecture system, the operation of calling each other between mobile applications is to be realized due to the service requirement. Existing application invocation schemes require key exchanges by both parties to be performed by the respective background to verify the signature and utilize the H5 middle page to invoke the application. In the process of implementing the present invention, the inventor finds that at least the following problems exist in the prior art: The existing scheme cannot be suitable for mobile application mutual call under a double-layer operation architecture system, and cannot ensure the safety and the non-tamper property of data transmission in the application call process. Disclosure of Invention In view of the above, the embodiments of the present invention provide an application invoking method and apparatus, which are suitable for mobile applications invoking each other in a dual-layer operation architecture system, and ensure security and non-tamper-resistance of data transmission during the application invoking process. To achieve the above object, according to one aspect of an embodiment of the present invention, there is provided an application calling method. An application calling method comprises the steps of uploading signature elements of a first application to a mechanism background system to conduct signature to obtain first signature information, calling a second application through an application calling jump protocol request to execute first service processing by the second application, calling the first application to execute second service processing after the second signature information is verified, responding to the first application calling request initiated by the second application through a pull-back application jump protocol, obtaining the parameters of the pull-back application jump protocol, wherein the parameters of the pull-back application jump protocol comprise second signature information, the second signature information is generated through the mechanism background system, the second signature information is verified through the mechanism background system, and the first application is called to execute second service processing after the second signature information is verified, and the mechanism background system is a background system associated with the first application or the second application. Optionally, uploading the signature element of the first application to a background system of an organization for signature comprises uploading a first element set formed by the signature element of the first application to the background system of the organization for encryption and then signing, wherein the first element set comprises a first public element, a first parameter set and a service custom parameter of the first application. Optionally, the first public element comprises a time stamp and a validity period of the first signature information, the first parameter set comprises a service identifier in the case that the first application is a digital currency application and the second application is a third party application, and the first parameter set comprises the service identifier and an identifier of the agency background system in the case that the first application is a third party application and the second application is a digital currency application, and the service identifier is used for the second application to execute the first service processing corresponding to the service identifier. Optionally, the first parameter set further comprises first customized additional information in case the first application is a digital money application and the second application is a third party application, and the first parameter set further comprises a unique identification of the first application and/or the second customized additional information in case the first application is a third party application and the second application is a digital money application. Optionally, the first custom additional information or the second custom additional information includes encryption signing algorithm information, and the second application uses the encryption signing algorithm information to sign and decrypt the first signature information. Optionally, the parameters evoking the application jump protocol further comprise a signature element of the first application, the first parameter set. Optiona