US 12,242,596 B2
Electronic device, trusted application calling method and apparatus, device, and medium
Fen Zou, Shanghai (CN); Chengqian Chen, Shanghai (CN); Dingzhou Li, Shanghai (CN); and Xin Wang, Shanghai (CN)
Assigned to CHINA UNIONPAY CO., LTD., Shanghai (CN)
Appl. No. 18/689,281
Filed by CHINA UNIONPAY CO., LTD., Shanghai (CN)
PCT Filed Aug. 15, 2022, PCT No. PCT/CN2022/112599
§ 371(c)(1), (2) Date Mar. 5, 2024,
PCT Pub. No. WO2023/071423, PCT Pub. Date May 4, 2023.
Claims priority of application No. 202111275919.8 (CN), filed on Oct. 29, 2021.
Prior Publication US 2025/0005135 A1, Jan. 2, 2025
Int. Cl. G06F 21/53 (2013.01)
CPC G06F 21/53 (2013.01) [G06F 2221/033 (2013.01)] 6 Claims
OG exemplary drawing
 
1. An electronic device, comprising: a client application (CA), and at least one processor configured to execute program code to implement a trusted application development platform; wherein:
the CA is configured to initiate a first access request for a native trusted application of a trusted execution environment operating system linked with the trusted application development platform and corresponding to the CA, the first access request carries first identification information of the electronic device and second identification information of a bytecode trusted application of any application;
the trusted application development platform is configured to receive the first access request, determine a native trusted application corresponding to the first identification information from native trusted applications respectively corresponding to at least two trusted execution environment operating systems linked with the trusted application development platform according to the first identification information, and send the first access request to the native trusted application corresponding to the first identification information;
the native trusted application corresponding to the first identification information is configured to receive the first access request and determine whether the native trusted application corresponding to the first identification information is installed with a bytecode trusted application with the second identification information, and when the native trusted application corresponding to the first identification information is installed with the bytecode trusted application with the second identification information, return confirmation information to the CA;
the CA is further configured to send a calling command to the native trusted application corresponding to the first identification information after receiving the confirmation information;
the native trusted application corresponding to the first identification information is further configured to forward the calling command received from the CA to the bytecode trusted application with the second identification information;
wherein the native trusted application corresponding to the first identification information is further configured to return prompt information of non-installation to the CA when determining that the native trusted application corresponding to the first identification information is not installed with the bytecode trusted application corresponding to the second identification information;
the CA is further configured to send an installation instruction for installing the bytecode trusted application with the second identification information to the native trusted application corresponding to the first identification information;
the native trusted application corresponding to the first identification information is further configured to install the bytecode trusted application with the second identification information at a set position of the native trusted application corresponding to the first identification information according to the installation instruction and based on an open trust protocol (OTRP), and send return information of successful installation to the CA after installation is successful;
the CA is further configured to initiate a second access request after receiving the return information.