WO2019071650A1 - 一种安全元件中的应用的升级方法及相关设备 - Google Patents

一种安全元件中的应用的升级方法及相关设备 Download PDF

Info

Publication number
WO2019071650A1
WO2019071650A1 PCT/CN2017/107016 CN2017107016W WO2019071650A1 WO 2019071650 A1 WO2019071650 A1 WO 2019071650A1 CN 2017107016 W CN2017107016 W CN 2017107016W WO 2019071650 A1 WO2019071650 A1 WO 2019071650A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
upgraded
upgrade
mobile terminal
management server
Prior art date
Application number
PCT/CN2017/107016
Other languages
English (en)
French (fr)
Inventor
李卓斐
李辉
邓太生
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201780065391.7A priority Critical patent/CN109863475A/zh
Publication of WO2019071650A1 publication Critical patent/WO2019071650A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method for upgrading an application in a secure component and related devices.
  • TEE is a secure operating environment running on the main processor. The TEE's secure boot process needs to be verified, and its secure boot process is separate from the REE.
  • the applications running under the TEE are independent of each other, and each application cannot be accessed by each other without authorization, ensuring that the resources and data processing of the application under the TEE are in a trusted environment.
  • SE Mobile Security Element
  • SE Mobile Security Element
  • the existing solution provides two solutions: the first way is: no upgrade direct replacement, such as financial IC card, once the application applet is found to be problematic, the financial integrated circuit (IC) card service provider recycles and destroys Old cards and new cards are distributed; the second way is to remove the old version and related data from the phone with the Applet, and then install the new version of Applet.
  • no upgrade direct replacement such as financial IC card
  • IC integrated circuit
  • the security of the applet will be reduced, which will bring security risks. If you upgrade, the important data will be deleted during the upgrade of the applet in the SE, and cannot be restored after the upgrade is completed. Lead to the corresponding loss.
  • important data can be defined according to business needs. For example, the bus card applet can define the amount as important data, and the electronic identity eID defines the identity information as important data.
  • the embodiment of the present application provides an upgrade method and related device for an application in a secure component, which is used to improve the security of an application in a secure component, and to ensure that user data is not lost during an application upgrade process in the secure component.
  • the first aspect of the present application provides a method for upgrading an application in a security component, including: a mobile terminal receiving an upgrade command corresponding to an application to be upgraded, the upgrade command may be triggered by a trusted service management server or a user; and the mobile terminal responds to the The upgrade command sends an upgrade request corresponding to the to-be-upgraded application to the trusted service management server, where the upgrade request may carry version information of the to-be-upgraded application; the mobile terminal sends the upgrade information to the trusted service management server.
  • the mobile terminal Determining the important data of the upgraded application; the mobile terminal deleting the current version of the application to be upgraded in the secure element SE, the current version of the application to be upgraded includes the important data; and the mobile terminal receives and installs the trusted The updated version of the application to be upgrade sent by the service management server according to the upgrade request; the mobile terminal receives the important data sent by the trusted service management server, and loads the received important data into the to-be-upgraded In the updated version of the app.
  • the mobile terminal upgrades the application in the security component, improves the security of the security component application, and ensures that the user data is not lost during the security component application upgrade process.
  • the upgrading method before the sending the important data of the to-be-upgraded application to the trusted service management server, the upgrading method further includes:
  • the current version of the application to be upgraded is set to a read-only mode by the SE.
  • the process of setting the application to be upgraded to the read-only mode is added, so that the embodiment of the present application is more complete in the steps.
  • the mobile terminal includes a trusted execution environment TEE and a rich execution environment REE, where the security application TA is running, The client application CA is run in the REE; and before the upgrade request is sent to the trusted service management server, the method further includes: generating, by the TA, the upgrade request of the application to be upgraded, The upgrade request for the upgraded application includes the identifier of the application to be upgraded, or includes the identifier of the application to be upgraded and the current version of the application to be upgraded.
  • a process of generating an upgrade request of the application to be upgraded is added, so that the embodiment of the present application is more logical.
  • the upgrade command corresponding to the application to be upgraded is input by the user; and the upgrade corresponding to the application to be upgraded is sent to the trusted service management server.
  • the method further includes: receiving, by the TA or the CA, an input of the user for verifying an identity; and using, by the TA, the user The input of the verification identity is authenticated and the authentication is passed.
  • the process of authenticating the input of the user for verifying the identity is added, and the implementation manner of the embodiment of the present application is added.
  • the upgrade method further includes: receiving, by the SE, an upload data command sent by the serviceable management server; and sending the to-be-upgraded application to the trusted service management server
  • the important data includes, in response to the uploading data command, transmitting important data of the to-be-upgraded application to the trusted service management server.
  • the process of receiving the upload data command by the mobile terminal is added, so that the embodiment of the present application is more complete in the steps.
  • the second aspect of the present application provides a method for upgrading an application in a security element, which is performed by a trusted service management server, where the upgrade method includes: the trusted service management server receives an upgrade request sent by the mobile terminal corresponding to the application to be upgraded; Receiving, by the trusted service management server, important data of the to-be-upgraded application sent by the mobile terminal; the trusted service management server saves important data of the to-be-upgraded application; and the trusted service management server moves to the mobile according to the upgrade request
  • the terminal sends the updated version of the application to be upgraded; the trusted service management server sends the important data of the application to be upgraded to the mobile terminal.
  • the trusted service management server upgrades the application in the security component, improves the security of the security component application, and ensures that the user data is not lost during the security component application upgrade process.
  • the upgrading method further comprises: comparing all data of the important data with corresponding data stored in the trusted service management server, and comparing the success.
  • the process of verifying all the data of the important data is added, which increases the achievability and operability of the embodiment of the present application.
  • the upgrading method further comprises: comparing the portion of the important data with the corresponding data stored in the trusted service management server, and comparing the success.
  • the process of verifying part of the data of the important data is added, which increases the achievability and operability of the embodiment of the present application.
  • the upgrade method further includes: sending an upload data command to the mobile terminal, where the upload data command is used to instruct the mobile terminal to upload the important data.
  • the process of sending an upload data command is added, so that the embodiment of the present application is more logical.
  • the upgrade request of the to-be-upgraded application includes version information, and before sending the updated version of the to-be-upgraded application,
  • the upgrade method further includes: determining, according to the version information of the application to be upgraded, whether the application to be upgrade needs to be updated, and determining that the result is an updated version.
  • a process of determining whether an application to be upgraded needs to be updated is added, and an implementation manner of the embodiment of the present application is added.
  • the upgrading method before the receiving the upgrade request corresponding to the application to be upgrade sent by the mobile terminal, the upgrading method further includes: moving to the mobile The terminal sends an application upgrade command, where the application upgrade command is used to instruct the mobile terminal to upgrade the application to be upgraded in the secure element.
  • the process of sending an application upgrade command to the mobile terminal by the trusted service management server is added, and the implementation manner of the embodiment of the present application is added.
  • a third aspect of the present application provides a mobile terminal, where the mobile terminal has a security component, the security component is installed with at least one application, and the mobile terminal includes: a first receiving unit, configured to receive an upgrade corresponding to the application to be upgraded a first sending unit, configured to send, to the trusted service management server, an upgrade request corresponding to the to-be-upgraded application, in response to the upgrade command, and a second sending unit, configured to send, to the trusted service management server, An important data of the application to be upgraded; a deletion unit, configured to delete the current version of the application to be upgraded in the security element SE, where the current version of the application to be upgraded includes the important data; Receiving and installing an updated version of the to-be-upgraded application sent by the trusted service management server according to the upgrade request; the second processing unit is configured to receive the important data sent by the trusted service management server, and The received important data is loaded into an updated version of the application to be upgraded.
  • the mobile terminal upgrades the application in the security component, improves the security
  • the mobile terminal further includes: a setting unit, configured to send, to the trusted service management server, an important of the application to be upgraded Data before The SE sets the current version of the application to be upgraded to a read-only mode.
  • a setting unit configured to send, to the trusted service management server, an important of the application to be upgraded Data before The SE sets the current version of the application to be upgraded to a read-only mode.
  • the process of setting the application to be upgraded to the read-only mode is added, so that the embodiment of the present application is more complete in the steps.
  • the mobile terminal includes a trusted execution environment TEE and a rich execution environment REE, where the security application TA is running.
  • a client application CA is run in the REE; the mobile terminal further includes: a generating unit, configured to generate, by the TA, the to-be-upgraded before sending an upgrade request corresponding to the to-be-upgraded application to the trusted service management server
  • the upgrade request of the application includes the identifier of the application to be upgraded, or the identifier of the application to be upgraded and the current version of the application to be upgraded.
  • a process of generating an upgrade request of the application to be upgraded is added, so that the embodiment of the present application is more logical.
  • the upgrade command corresponding to the application to be upgraded is input by the user;
  • the mobile terminal further includes: a second receiving unit, configured to Before the trusted service management server sends the upgrade request corresponding to the application to be upgraded and the important data of the application to be upgraded, the input of the user for verifying the identity is received by the TA or the CA; the authentication unit And for authenticating, by the TA, the input of the user for verifying identity, and authenticating is passed.
  • the process of authenticating the input of the user for verifying the identity is added, and the implementation manner of the embodiment of the present application is added.
  • the mobile terminal further includes: a third receiving unit, configured to send the corresponding to the trusted service management server After the upgrade request of the application is upgraded, before the important data of the application to be upgraded is sent to the trusted service management server, the upload data command sent by the serviceable management server is received by the SE; the second sending unit is specific And transmitting, in response to the uploading data command, important data of the to-be-upgraded application to the trusted service management server.
  • the process of receiving the upload data command by the mobile terminal is added, so that the embodiment of the present application is more complete in the steps.
  • the fourth aspect of the present application provides a trusted service management server, where the trusted service management server includes: a first receiving unit, configured to receive an upgrade request sent by the mobile terminal corresponding to the application to be upgraded; and a second receiving unit, Receiving the important data of the to-be-upgraded application sent by the mobile terminal; the saving unit is configured to save the important data of the to-be-upgraded application; the first sending unit is configured to send, according to the upgrade request, the mobile terminal The updated version of the application to be upgraded; the second sending unit is configured to send important data of the application to be upgraded to the mobile terminal.
  • the trusted service management server upgrades the application in the security component, improves the security of the security component application, and ensures that the user data is not lost during the security component application upgrade process.
  • the trusted service management server further includes: a first comparison unit, configured to receive, by the mobile terminal, After saving the important data of the application to be upgraded, comparing all the data of the important data with the corresponding data stored in the trusted service management server, and comparing the important data of the application to be upgraded success.
  • a first comparison unit configured to receive, by the mobile terminal, After saving the important data of the application to be upgraded, comparing all the data of the important data with the corresponding data stored in the trusted service management server, and comparing the important data of the application to be upgraded success.
  • the process of verifying all the data of the important data is added, which increases the achievability and operability of the embodiment of the present application.
  • the trusted service management server further includes: a second comparison unit, configured to receive, by the mobile terminal, After saving the important data of the application to be upgraded, comparing the partial data of the important data with the corresponding data stored in the trusted service management server, and comparing the important data of the application to be upgraded success.
  • the embodiment of the application has been added The process of verifying partial data of important data increases the achievability and operability of the embodiments of the present application.
  • the trusted service management server further includes: a third sending unit, configured to receive, according to the mobile terminal, a corresponding to be upgraded After receiving the upgrade request of the application, before receiving the important data of the to-be-upgraded application sent by the mobile terminal, sending an upload data command to the mobile terminal, where the upload data command is used to instruct the mobile terminal to upload the important data. .
  • a third sending unit configured to receive, according to the mobile terminal, a corresponding to be upgraded After receiving the upgrade request of the application, before receiving the important data of the to-be-upgraded application sent by the mobile terminal, sending an upload data command to the mobile terminal, where the upload data command is used to instruct the mobile terminal to upload the important data.
  • the process of sending an upload data command is added, so that the embodiment of the present application is more logical.
  • the upgrade request of the to-be-upgraded application includes version information
  • the trusted service management server further includes: a determining unit, Before the update version of the to-be-upgraded application is sent, determining whether the to-be-upgraded application needs to be updated according to the version information of the to-be-upgraded application, and determining that the result is an updated version.
  • a process of determining whether an application to be upgraded needs to be updated is added, and an implementation manner of the embodiment of the present application is added.
  • the trusted service management server further includes: a fourth sending unit, configured to receive, in the receiving mobile terminal, a corresponding to be upgraded Before the application of the upgrade request, the application upgrade command is sent to the mobile terminal, where the application upgrade command is used to instruct the mobile terminal to upgrade the application to be upgraded in the secure element.
  • a fourth sending unit configured to receive, in the receiving mobile terminal, a corresponding to be upgraded Before the application of the upgrade request, the application upgrade command is sent to the mobile terminal, where the application upgrade command is used to instruct the mobile terminal to upgrade the application to be upgraded in the secure element.
  • a fifth aspect of the present application provides a mobile terminal, comprising: a memory, a transceiver, and at least one processor, wherein the memory stores program code, and the memory, the transceiver, and the at least one processor pass A line interconnect, the processor running the code to instruct the mobile terminal to perform the method of any of the first aspects above.
  • a sixth aspect of the present application provides a trusted service management server, including: a memory, a transceiver, and at least one processor, wherein the memory stores program code, the memory, the transceiver, and the at least one The processor is interconnected by a line, the processor running the code to instruct the trusted service management server to perform the method of any of the above second aspects.
  • a seventh aspect of the present application provides a computer readable storage medium having program code stored therein that, when executed on a computer, causes the computer to perform the method of the first aspect described above.
  • An eighth aspect of the present application provides a computer readable storage medium having program code stored therein that, when executed on a computer, causes the computer to perform the method of the second aspect described above.
  • a ninth aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the first aspect described above.
  • a tenth aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the second aspect described above.
  • FIG. 1 is a schematic diagram of a network architecture applied to an embodiment of the present application
  • FIG. 2A is a schematic structural diagram of a mobile terminal according to an embodiment of the present application.
  • 2B is a schematic structural diagram of a trusted service management server according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of an embodiment of an upgrade method of an application in a security element according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of another embodiment of an upgrade method of an application in a security element according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of an embodiment of a mobile terminal according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of another embodiment of a mobile terminal according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of an embodiment of a trusted service management server according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of another embodiment of a trusted service management server according to an embodiment of the present application.
  • the embodiment of the present application provides an upgrade method and related device for an application in a secure component, which is used to improve the security of an application in a secure component, and to ensure that user data is not lost during an application upgrade process in the secure component.
  • the embodiment of the present application can be applied to the network architecture shown in FIG. 1 , where the network architecture includes a mobile terminal and a trusted service management (TSM) server, wherein the global platform is organized according to the global platform (GP).
  • TSM servers are divided into two categories: secure element issuer trusted service management (SEI-TSM) server and service provider trusted service management (service provider trusted service). Management, SP-TSM).
  • SEI-TSM secure element issuer trusted service management
  • SP-TSM service provider trusted service management
  • SEI-TSM is responsible for providing SE lifecycle and security domain management services for SE providers
  • SP-TSM is responsible for providing application lifecycle services to service providers.
  • the mobile terminal has three application environments: a rich execution environment (REE), a trusted execution environment (TEE), and a secure element (SE).
  • REE rich execution environment
  • TEE trusted execution environment
  • SE secure element
  • the mobile terminal and the server implement interaction through a secure channel to implement an upgrade of an application (Applet) in the secure element SE in the mobile terminal, wherein the secure channel is a secure and trusted transmission environment for transmitting interactive data.
  • the mobile terminal encapsulates the important data defined by the service provider of the applet to be upgraded into an important data packet and sends it to the TSM server, and the mobile terminal deletes the current version of the applet to be upgraded, and downloads the applet to be upgraded from the server.
  • the latest version or a specific version it can be understood that the specific version is newer than the current version (that is, the specific version is updated).
  • the mobile terminal downloads the important data packet uploaded from the server, and imports the important data in the important data package into the latest version of the applet or the specific version of the applet that has been downloaded and installed, thereby completing the upgrade. Applet version update.
  • the TA is an application running in the TEE, and can access the processor and memory of the mobile terminal, Applet For SE applications, the Secure Element SE can take many forms, including a SIM card (usually used by mobile operators as a security module), a chip embedded in the handset, and a direct connection to a near field communication (NFC) chip. MicroSD card etc.
  • the SE is a separate chip in the mobile terminal.
  • a secure channel can also be established between the TEE and the SE. The data interaction between the TA and the applet can be transmitted through the secure channel.
  • TEE has its own execution space, which is higher than the security level of the REE operating system, and TEE is not a separate physical security chip, but a security architecture that overlaps with the hardware architecture of the currently used application processor.
  • the hardware and software resources that TEE can access are separate from the REE operating system and provide hardware-supported isolation.
  • the application in SE can be applied to mobile phone shield, eID, bank card, bus card, etc.
  • the TEE Client API and TEE Internal API can adopt TEE Client API V1.0 standard and TEE Internal API V1.0 standard respectively, as shown in Figure 2A.
  • the hardware portion thereof may include: a memory, a processor, and a communication unit.
  • the memory is used to store program code and data of the mobile terminal, for example, the protected area in the memory can store a trusted execution environment operating system (TEE OS) and an application in the TEE (TEE application, TA)
  • the non-protected area of the memory can store a rich execution environment operating system (REE OS) and a TEE application (REE application, CA)
  • the memory in the SE can store a card operating system (card operating system) , COS) and various applications.
  • the processor may be, for example, a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), or an application-specific integrated circuit (ASIC).
  • the processor may include a processor in an application processor chip, and an SE
  • the processor in the above is used to run various program codes as described above to instruct the mobile terminal to perform various operations described in the embodiments of the present invention.
  • the communication unit may be a radio frequency circuit or the like for interaction with a trusted service management server.
  • the embodiment of the present application further provides a mobile terminal, which does not include an SE, where the mobile terminal has a memory, a processor, and a communication unit, and the memory program code and data, for example, the protected area in the memory can store the TEE OS and TA, the non-protected area of the memory may be REE OS and CA, the processor executing program code in the memory to instruct the mobile terminal to perform operations in the following method embodiments to implement with the SE and the trusted service management server Interaction.
  • the trusted service management server 200 may generate a large difference due to different configurations or performances, and may include one or more processors (central Processing units (CPU) 201 (eg, one or more processors) and storage medium 208, one or more storage media 208 (eg, one or one of the Shanghai quantity storage devices) that store application 207 or data 206.
  • processors central Processing units (CPU) 201
  • storage medium 208 can be short-term storage or persistent storage.
  • the program stored on storage medium 208 may include one or more modules (not shown), each of which may include a series of codes in a trusted service management server.
  • the processor 201 can be configured to communicate with a storage medium 208, which is a control center of the trusted service management server, and can connect various parts of the entire trusted service management server by using various interfaces and lines, by running or Implementing software programs and/or modules stored in storage medium 208, as well as invoking data stored in storage medium 208, performing various functions and processing data of the trusted service management server for security An upgrade to the application in the component.
  • a storage medium 208 which is a control center of the trusted service management server, and can connect various parts of the entire trusted service management server by using various interfaces and lines, by running or Implementing software programs and/or modules stored in storage medium 208, as well as invoking data stored in storage medium 208, performing various functions and processing data of the trusted service management server for security An upgrade to the application in the component.
  • the storage medium 208 can be used to store software programs and modules, and the processor 201 executes various functional applications and data processing of the trusted service management server 200 by running software programs and modules stored in the storage medium 208.
  • the storage medium 208 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as determining whether an applet needs to be updated, etc.), and the like; the storage data area may be stored. Data created according to the use of the trusted service management server (such as uploading data commands, etc.).
  • storage medium 208 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
  • the program of the upgrade method of the secure element application and the received data stream provided in the embodiment of the present application are stored in a memory, and the processor 201 calls from the storage medium 208 when it is needed.
  • the trusted service management server 200 may also include one or more power sources 202, one or more wired or wireless network interfaces 203, one or more input and output interfaces 204, and/or one or more operating systems 205, such as Windows. Serve, Mac OS X, Unix, Linux, FreeBSD, etc. It will be understood by those skilled in the art that the trusted service management server structure shown in FIG. 2B does not constitute a limitation to the trusted service management server, and may include more or less components than those illustrated, or may combine certain components. Or different parts arrangement.
  • the mobile terminal described in the present application may be a mobile terminal, a tablet computer, or the like, which has three security environments: REE, TEE, and SE.
  • the server described in the present application is a trusted service management server, and the trusted service management server may specifically include Secure element issuer trusted service management (SEI-TSM) system and service provider trusted service management (SP-TSM) system; application in the embodiment of the present application
  • SEI-TSM Secure element issuer trusted service management
  • SP-TSM service provider trusted service management
  • the upgrade command (the Applet upgrade command) may be triggered by the user or generated by the trusted service management server and sent to the mobile terminal.
  • the first application upgrade request (Applet upgrade request) in the embodiment of the present application is determined by the CA according to the application.
  • the upgrade command is generated, and the second application to be upgraded is generated by the TA according to the first application to be upgraded, and the second application to be upgraded may carry the version information of the application to be upgraded.
  • Send as a message to the trusted service management service The version of the application to be upgraded that is downloaded by the mobile terminal from the trusted service management server may be the latest version or a specific version of the update, and the specific version can meet the special security requirements of the service provider of the application to be upgraded.
  • the embodiment is described by taking the latest version as an example.
  • the important data in the embodiment of the present application is defined by the service provider of the application to be upgraded. For different application applets, the important data defined may be the same or different. For example, the service provider of the bus card applet may define the amount as important. Data, the service provider of the electronic identity eID can define identity information as important data.
  • the Applet upgrade request may be triggered by the user, or may be triggered by the server.
  • an embodiment of the method for upgrading the application in the security element in the embodiment of the present application includes:
  • the CA receives an application upgrade command of the user.
  • the user finds that at least one application applet in the security component needs to be upgraded (that is, the applet to be upgraded needs to be upgraded), and the user triggers the target applet upgrade in the CA. command.
  • the user finds that the version of the bus card may need to be updated by the notification information sent by the bus company, and the user finds the bus card application in the setting interface of the mobile terminal, and selects Upgrade the bus card.
  • the applet upgrade command may be received and parsed by the CA, and the parsing result is forwarded to the TA.
  • the CA may also forward the applet upgrade command to the TA, and the CA only serves as a forwarding function, and the TA receiving is received.
  • the applet upgrade command is parsed after the applet upgrade command.
  • the mobile terminal keeps the network connection function enabled and can perform network downloading.
  • the mobile terminal can The user's operation of turning off the network connection function is not performed to ensure that the mobile terminal can smoothly upgrade the applet to be upgraded.
  • the CA sends the first to be upgraded application upgrade request to the TA.
  • the CA in the REE of the mobile terminal sends the first application to be upgraded to the TA in the TEE according to the application upgrade command of the user.
  • the first application to be upgraded carries the identifier of the application to be upgraded, and is used by the TA to determine the applet to be upgraded.
  • the bus card CA sends a bus card application upgrade request to the TA through the transmission channel between the REE and the TEE according to the user's upgrade command, and the bus card application upgrade request carries at least the identification information for distinguishing other applets.
  • the TA authenticates the first to be upgraded application upgrade request.
  • the TA of the mobile terminal authenticates the user, and the means used include, but not limited to, personal identification number (PIN), fingerprint, iris, face recognition, etc., to verify that the applet upgrade operation is the owner of the mobile terminal.
  • PIN personal identification number
  • I trigger for example, when using the PIN code for verification, when the PIN code pre-stored in the mobile terminal is the same as the PIN code input by the user, it is determined that the first to-be-upgraded application upgrade request operation is triggered by the owner of the mobile terminal, TA It is determined that the generated first to be upgraded application upgrade request is valid, and the TA obtains version information of the corresponding applet according to the first to be upgraded application upgrade request.
  • TA can take advantage of the security capabilities of TEE, including but not limited to trusted user interface (TUI), secure storage, secure biometrics, trusted clocks, and more.
  • TEE trusted user interface
  • the TA After the user inputs the upgrade command through the CA, the TA provides the authentication interface to the user after the TA obtains the corresponding upgrade request generated by the CA. For example, the TA prompts the user to verify the fingerprint information, and the user performs the prompt according to the prompt.
  • the TA calls the mobile terminal to identify the fingerprint entered by the user.
  • the fingerprint can be directly collected by the fingerprint collection device on the mobile terminal or collected through the touch screen; the TA collects the collected fingerprint information and the stored information in the mobile terminal. The fingerprint information is matched. If the matching is performed, it is determined that the applet upgrade operation is triggered by the owner of the mobile terminal.
  • the TA determines that the generated applet upgrade request is legal, and the TA obtains the version information of the corresponding applet according to the applet upgrade request. It will be appreciated that information such as PIN and fingerprint information used as a matching template is already stored in the memory of the mobile terminal prior to matching, and the TA is called from memory when needed.
  • the mobile terminal has a function module for performing fingerprint collection.
  • the PIN code authentication is used as an example.
  • the TA After the user enters the upgrade command through the CA, the TA provides a trusted input box for the user to collect the user after obtaining the corresponding first application upgrade request generated by the CA.
  • the entered PIN code the TA determines whether the PIN code input by the user is correct; if it is correct, it can confirm that the upgrade operation is an applet upgrade operation actively performed by the owner of the mobile terminal, and the TA determines the first upgrade application upgrade generated by the CA.
  • Request is If the data is correct, the TA obtains the version information of the application to be upgraded according to the first application to be upgraded. If not, perform other operations, for example, verifying again, or terminating the applet upgrade. limited.
  • the PIN code is stored and verified by the TA.
  • the PIN code can be modified according to the needs of the user.
  • the TA obtains the version information of the application to be upgraded from the applet.
  • the TA sends the Applet version (GET APPLET VERSION) command to the applet, and the applet encrypts and signs the upgrade data with the agreed key and returns it to the TA.
  • the upgrade data includes the SE ID, current version information of the application to be upgraded, and the like.
  • the agreed key may be a secure storage key (SSK).
  • SSK secure storage key
  • the value of the SSK in different mobile terminal devices is different.
  • the hash-based message authentication code (HMAC) calculates the value of the SSK, where both the HUK and the chip ID are preset in the chip of the mobile terminal.
  • HMAC hash-based message authentication code
  • It can also be another key such as a trusted application storage key (TASK), which is not limited herein.
  • TASK trusted application storage key
  • a public key and a private key When encrypting a file using an asymmetric encryption algorithm, it is necessary to use two pairs of matching public and private keys to complete the process of encrypting and decrypting the plaintext.
  • the target public key When the data is encrypted, the target public key is used for encryption.
  • the private key matching the target public key is used to complete the encryption and decryption process.
  • the mobile terminal signs the data, the target private key is used for signature, and after receiving the data, the trusted service management server identifies the signature by using a public key matching the target private key. Before transmitting the encrypted and signed data, the mobile terminal must send the private key matching the target public key and the public key matching the target private key to the trusted service management server, and retain the target private key and the target public. key.
  • the TA sends the second upgrade application update request and the version information of the application to be upgraded to the trusted service management server.
  • the TA sends the version information of the application to be upgraded and the version of the application to be upgraded to the trusted service management (TSM) server, where the version information of the application to be upgraded may be carried in the second application upgrade request to be upgraded. It can also be sent to the TSM server as a separate message, and the version information with the upgraded application has been encrypted and signed by the TA.
  • TSM trusted service management
  • the TSM server determines whether the application to be upgrade needs to be updated.
  • the TSM server analyzes the second application to be upgraded and obtains the identification information of the application to be upgraded.
  • the TSM server determines whether the application to be upgraded needs to be updated according to the identification information of the applet and the version information of the application to be upgraded; If it is the latest, it does not need to be updated, and the mobile terminal is notified that the update does not need to be updated. For example, the user is notified that the current applet version is up-to-date, and no upgrade is required, or the mobile terminal is notified that the application to be upgraded has no new version that can be updated. If the current applet version is not up to date, you need to update the applet version and go to step 307.
  • the service providers corresponding to different applets can also adopt other business strategies for their own TSM servers.
  • the business strategy is the execution standard set by the service provider according to its own business needs, for example, the service provider of the bus card.
  • the business strategy may be: if the version of the bus card application is not up-to-date, the user is prompted to upgrade when the mobile terminal uses the bus card function; the business strategy of the bus card service provider may also be: if the version of the bus card application is not The latest is to prompt the user to upgrade the bus card application when the mobile terminal is connected to the wireless network.
  • the TSM server notifies the CA via the TA, and terminates the upgrade. Specifically, the TSM may issue a command to terminate the upgrade, so that the mobile terminal stops the applet upgrade process.
  • the TSM server establishes a secure channel with the applet, and issues an upload data command for instructing the mobile terminal to upload important data.
  • Applet locks itself to BLOCK.
  • Applet locks itself to BLOCK.
  • the specific form can be to change the properties of the applet to read-only mode.
  • the data of the applet cannot be modified so that important data can no longer be updated.
  • the applet packs and summarizes each important data according to the agreed format to form an important data packet.
  • the important data package may include important data and installation information of the application to be upgraded.
  • the agreed format may take various forms, for example, it may be a commonly used IP.
  • the format of the data packet can also be other formats, which is not limited herein.
  • the bus card applet can be used as the important data according to the amount defined by the service provider of the bus card. After the bus card applet is BLOCK, the amount cannot be changed any more, and the mobile terminal cannot use the bus card service function, for example, can no longer Use the bus card function to perform the card payment service.
  • the service provider needs to define important data and its format for its own applet, and its TSM server can recognize the same important data and its format.
  • the applet sends important data to the TSM server.
  • the Applet sends a response to the TSM server via the secure channel to the TSM server, the response of the upload data command containing the important data.
  • the secure channel is a mature and available transmission channel established between the TSM server and the SE.
  • the security channel provides necessary security for important data.
  • the specific establishment process of the security channel is the same as the prior art. For example, it can be utilized.
  • the Secure Sockets Layer (SSL) protocol and/or the Transport Layer Security (TLS) protocol establish a secure channel, which is not mentioned here.
  • SSL Secure Sockets Layer
  • TLS Transport Layer Security
  • Applets can choose to encrypt and sign important packets with a specific key to further increase security.
  • the TSM server also needs to perform decryption and signature verification according to the corresponding logic.
  • the TSM server verifies important data.
  • the TSM server verifies important data.
  • select partial data in the data in the important data packet according to the preset rule, and verify the partial data with the data stored in the TSM server for example, The IP verification algorithm is used to select data with a length of 20 bytes from the data and a corresponding data stored on the trusted service management.
  • the TSM server does not receive the upload data command response within the preset duration, for example, does not receive the upload data command response within 3 minutes, or terminates the upgrade according to the policy (for example, the important packet comparison is unsuccessful, it is considered serious)
  • the TSM server can issue the UNBLOCK command to the applet and notify the CA that the version update fails. After receiving the UNBLOCK command, the mobile unlocks the applet.
  • the applet is Attributes from read-only mode Set to read-write mode; or the TSM server does not issue the UNBLOCK command to maintain the BLOCK state of the applet, the property of the applet is always read-only mode, other devices can only read the data of the applet, and can not modify the data.
  • the mobile terminal when the data on the trusted service management server is not synchronized with the data in the mobile terminal, the mobile terminal performs the above steps 308 and 309; when the data on the trusted service management server is synchronized with the data in the mobile terminal The mobile terminal does not need to upload important data, only needs to upload the important data list (ie, replace steps 308 and 309 with the step of reporting the important data list), and after the mobile terminal downloads the updated version of the application to be upgraded, the trusted service management server The important data corresponding to the important data list is delivered to the mobile terminal.
  • the TSM server sends an updated version of the application to be upgraded to the mobile terminal.
  • the TSM server sends an updated version of the application to be upgraded to the mobile terminal. Specifically, the TSM server sends a DELETE command to the SE, and the SE deletes the current version of the applet. After completing the deletion of the current version of the applet, the TSM server issues a LOAD, INSTALL command to the SE, and the LOAD and INSTALL commands are executed by the SE, and the SE downloads the updated version of the application to be upgraded from the server and installs it.
  • the applet in the SE is different from the CA in the REE when the upgrade is updated.
  • the SE must delete the old version of the applet before downloading the new version of the applet.
  • the TSM server performs data synchronization on the updated version of the applet.
  • the TSM server issues a STORE DATA command to the new version of the applet and synchronizes important data and other related information (eg, information related to the unpacking of the upgraded application) to the new version of the applet.
  • the TSM server can issue other commands to the applet, such as downloading commands, so that the download function of the applet is completely enabled. For example, sending a download certificate command to the U shield applet of the mobile terminal, so that the U shield applet can complete the download of the security certificate, or Other orders are not limited here.
  • the TSM server notifies the update of the applet successfully.
  • the TSM server After loading the important data in the important data package into the updated version of the application to be upgraded, the TSM server receives the updated version of the Applet feedback message to confirm that the update applet is successful.
  • the TSM server displays the result to the user via the CA, prompting the user to update the applet successfully.
  • the mobile terminal packages and uploads the important data to the TSM server, and synchronizes the important data previously uploaded to the updated version of the applet after the new version of the applet is successfully installed, thereby improving the secure component application applet.
  • the data is secure and the user data is protected from loss during the Applet upgrade process.
  • another embodiment of an upgrade method for an application in a secure element in an embodiment of the present application includes:
  • the CA receives an application upgrade command sent by the TSM server.
  • the TSM server determines, according to the specific policy of the service provider, that at least one application in the security element needs to be upgraded, the TSM server sends an application upgrade command to the CA, and the mobile terminal receives the Applet upgrade command sent by the TSM server through the CA.
  • the service provider bus card company
  • the service provider for the bus card function of the mobile terminal, determines, according to a specific policy, for example, to upgrade the service platform or find a major security hole in the original version of the applet, the corresponding bus card Applet also needs to be upgraded to meet the requirements of the upgraded service platform.
  • Bus card The company sends an application upgrade command to the CA of the mobile terminal through the TSM server, and triggers the bus card application upgrade in the CA at a specific timing (for example, when the mobile phone is in an idle state). It should be noted that the service providers corresponding to different applets can also adopt other strategies for their own TSM servers.
  • the mobile terminal keeps the network connection function enabled and can perform network downloading, for example, the mobile terminal.
  • the user's operation of turning off the network connection function may not be performed to ensure that the mobile terminal can smoothly upgrade the upgraded applet.
  • the CA sends the first to be upgraded application upgrade request to the TA.
  • Step 402 is similar to step 302, and details are not described herein again.
  • the TA determines whether to perform verification according to a preset service provider policy.
  • the TA determines whether to verify according to the preset service provider policy. If the service provider policy needs to be verified, the verification is performed. If the service provider policy does not need to be verified, step 404 is performed.
  • the TA obtains version information of the application to be upgraded from the applet.
  • the TA sends the second to-be-upgraded application upgrade request and the version information of the application to be upgraded to the trusted service management server.
  • Step 404 to step 405 are similar to steps 304 to 305, and details are not described herein again.
  • the applet locks itself to BLOCK.
  • the applet sends important data to the TSM server.
  • the TSM server verifies important data.
  • the TSM server sends an updated version of the application to be upgraded to the mobile terminal.
  • the TSM server performs data synchronization on the updated version of the applet.
  • the TSM server notifies the update of the applet successfully.
  • Steps 406 to 411 are similar to steps 307 to 312, and details are not described herein.
  • the mobile terminal applet packages and uploads the important data to the TSM server during the upgrade process, and after the new version of the applet is successfully installed, the previously uploaded important data is synchronized to In the updated version of the Applet, the data security of the secure component application applet is improved, and the user data of the secure component application applet upgrade process is not lost.
  • the foregoing describes the method for upgrading the application in the security element in the embodiment of the present application.
  • the following describes the mobile terminal and the trusted service management server in the embodiment of the present application. Referring to FIG. 5, an implementation of the mobile terminal in the embodiment of the present application is described. Examples include:
  • the first receiving unit 501 is configured to receive an upgrade command corresponding to the application to be upgraded
  • the first sending unit 502 is configured to send, to the trusted service management server, an upgrade request corresponding to the to-be-upgraded application, in response to the upgrade command;
  • a second sending unit 503, configured to send important data of the to-be-upgraded application to the trusted service management server;
  • a deleting unit 504 configured to delete a current version of the to-be-upgraded application in the security element SE, where the current version of the to-be-upgraded application includes the important data;
  • a first processing unit 505 configured to receive and install, by the trusted service management server, send according to the upgrade request An updated version of the application to be upgraded;
  • the second processing unit 506 is configured to receive the important data sent by the trusted service management server, and load the received important data into an updated version of the application to be upgraded.
  • the mobile terminal upgrades the application in the security component, improves the security of the security component application, and ensures that the user data is not lost during the security component application upgrade process.
  • FIG. 6 another embodiment of the mobile terminal in the embodiment of the present application includes:
  • the first receiving unit 601 is configured to receive an upgrade command corresponding to the application to be upgraded
  • the first sending unit 602 is configured to send, to the trusted service management server, an upgrade request corresponding to the to-be-upgraded application, in response to the upgrade command;
  • a second sending unit 603, configured to send important data of the to-be-upgraded application to the trusted service management server;
  • a deleting unit 604 configured to delete a current version of the to-be-upgraded application in the security element SE, where the current version of the to-be-upgraded application includes the important data;
  • the first processing unit 605 is configured to receive and install an updated version of the to-be-upgraded application that is sent by the trusted service management server according to the upgrade request.
  • the second processing unit 606 is configured to receive the important data sent by the trusted service management server, and load the received important data into an updated version of the application to be upgraded.
  • the mobile terminal may further include:
  • the setting unit 607 is configured to set the current version of the to-be-upgraded application to a read-only mode by using the SE before sending the important data of the to-be-upgraded application to the trusted service management server.
  • the mobile terminal may further include:
  • the generating unit 608 is configured to generate, by the TA, an upgrade request of the to-be-upgraded application, and the upgrade request of the to-be-upgraded application includes the to-be-upgraded application
  • the mobile terminal may further include:
  • the second receiving unit 609 is configured to receive, by the TA or the CA, an input of the user for verifying an identity before sending the upgrade request corresponding to the to-be-upgraded application to the trusted service management server;
  • the authentication unit 610 is configured to authenticate the input of the user for verifying the identity by using the TA, and pass the authentication.
  • the mobile terminal may further include:
  • the third receiving unit 611 is configured to: after sending the upgrade request corresponding to the to-be-upgraded application to the trusted service management server, send the important data of the to-be-upgraded application to the trusted service management server, and pass the SE Receiving an upload data command sent by the serviceable management server;
  • the second sending unit 609 is specifically configured to send, according to the upload data command, important data of the to-be-upgraded application to the trusted service management server.
  • the mobile terminal after receiving the Applet upgrade command, packages and uploads important data to the TSM server during the Applet upgrade process, and synchronizes the previously uploaded important data to the update after the Applet update version is successfully installed. Version of Applet, improves the security of the application applet in the secure element, and guarantees User data in the secure element is not lost during the Applet upgrade process.
  • an embodiment of a trusted service management server in this embodiment of the present application includes:
  • the first receiving unit 701 is configured to receive, by the mobile terminal, an upgrade request corresponding to the application to be upgraded;
  • the second receiving unit 702 is configured to receive important data of the to-be-upgraded application sent by the mobile terminal;
  • a saving unit 703 configured to save important data of the application to be upgraded
  • the first sending unit 704 is configured to send, according to the upgrade request, an updated version of the application to be upgraded to the mobile terminal;
  • the second sending unit 705 is configured to send important data of the application to be upgraded to the mobile terminal.
  • the trusted service management server upgrades the application in the secure component, improves the security of the secure component application, and ensures that the user data is not lost during the application upgrade process in the secure component.
  • another embodiment of the trusted service management server in the embodiment of the present application includes:
  • the first receiving unit 801 is configured to receive an upgrade request that is sent by the mobile terminal and is corresponding to the application to be upgraded;
  • the second receiving unit 802 is configured to receive important data of the to-be-upgraded application sent by the mobile terminal;
  • a saving unit 803, configured to save important data of the application to be upgraded
  • the first sending unit 804 is configured to send, according to the upgrade request, an updated version of the application to be upgraded to the mobile terminal;
  • the second sending unit 805 is configured to send important data of the to-be-upgraded application to the mobile terminal.
  • the trusted service management server may further include:
  • the first comparison unit 806 is configured to: after receiving the important data of the to-be-upgraded application sent by the mobile terminal, save all the data of the important data and the trusted service before saving the important data of the application to be upgraded The data stored in the management server is compared and the comparison is successful.
  • the verification unit 805 is specifically configured to:
  • a second comparison unit 807 configured to: after receiving the important data of the to-be-upgraded application sent by the mobile terminal, save the partial data of the important data and the trusted service before saving the important data of the to-be-upgraded application The data stored in the management server is compared and the comparison is successful.
  • the trusted service management server may further include:
  • the third sending unit 808 is configured to send an upload data command to the mobile terminal before receiving the upgrade request of the to-be-upgraded application sent by the mobile terminal after receiving the upgrade request of the to-be-upgraded application sent by the mobile terminal,
  • the upload data command is used to instruct the mobile terminal to upload the important data.
  • the trusted service management server may further include:
  • the determining unit 809 is configured to determine, according to the version information of the to-be-upgraded application, whether the updated application needs to be updated, before sending the updated version of the to-be-upgraded application.
  • the trusted service management server may further include:
  • the fourth sending unit 810 is configured to send an application upgrade command to the mobile terminal, where the application upgrade command is used to indicate that the mobile terminal is in the security element, before receiving the upgrade request corresponding to the application to be upgrade sent by the mobile terminal.
  • the application to be upgraded is upgraded.
  • the trusted service management server receives the heavy weight sent by the mobile terminal during the upgrade process of the applet.
  • the important data received is synchronized to the updated version of the applet, which improves the security of the application applet in the secure component, and ensures that the user data in the security device is not lost during the Applet upgrade process.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.).
  • wired eg coaxial cable, fiber optic, digital subscriber line (DSL)
  • wireless eg infrared, wireless, microwave, etc.
  • the computer readable storage medium can be any available media that can be stored by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

一种安全元件中的应用的升级方法及相关设备，用于提高安全元件中的应用的安全性，并保障安全元件中的应用升级过程中用户数据不丢失。该方法包括：接收对应待升级应用的升级命令；响应于所述升级命令，向可信服务管理服务器发送对应所述待升级应用的升级请求；向所述可信服务管理服务器发送所述待升级应用的重要数据；删除所述安全元件SE中的所述待升级应用的当前版本，所述待升级应用的当前版本包括所述重要数据；接收并安装所述可信服务管理服务器根据所述升级请求发送的所述待升级应用的更新版本；接收所述可信服务管理服务器发送的所述重要数据，并将接收的所述重要数据加载到所述待升级应用的更新版本中。

Description

一种安全元件中的应用的升级方法及相关设备
本申请要求于2017年10月9日提交中国专利局、申请号为201710931301.X、发明名称为“一种安全元件应用的升级方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种安全元件中的应用的升级方法及相关设备。
背景技术
随着移动终端的快速发展，移动终端的功能越来越多，对移动终端的安全性的要求也越来越高。主流的移动终端有三种应用环境，按安全性由低到高依次为：富执行环境(rich execution environment，REE)、可信执行环境(trusted execution environment，TEE)和安全元件(secure element，SE)，其中运行的应用依次叫做：客户应用(client application，CA)、可信应用(TEE application，TA)和SE中的应用(Applet)。TEE是运行在主处理器中的一种安全运行环境，TEE的安全启动过程是需要通过验证的，并且它的安全启动过程是与REE分离的。运行在TEE下的各个应用程序之间是相互独立的，而且各个应用程序之间不能在未授权的情况下互相访问，保证TEE下的应用程序的资源和数据的处理过程是在一个可信环境下执行的，从而为REE操作系统提供安全服务。安装在手机安全元件(SE)中的很多应用(Applet)都比较重要，与个人资金或身份绑定，例如银行电子现金支付、一卡通支付、电子身份标识(electronic identity，eID)等。一些SE应用本身会存储用户身份、金额等重要信息。
由于版本缺陷，业务场景变化等原因，SE中的Applet也有升级的需要。现有方案提供了两种解决方式：第一种方式是：不升级直接更换，例如金融IC卡，一旦发现应用Applet有问题，则金融集成电路(integrated circuit，IC)卡的业务提供方回收销毁旧卡片并分发新卡片；第二种方式是：安装有Applet的手机删除旧版本及相关数据，然后安装新版本Applet。
现有的解决方案中，若不升级，则会降低Applet的安全性，带来安全隐患；若升级，对SE中的Applet进行升级的过程中，重要数据被删除，在升级结束后不能恢复，导致相应的损失。对于不同的Applet，可以根据业务需要定义重要数据，例如，公交卡Applet可以将金额定义为重要数据，电子身份标识eID将身份信息定义为重要数据。
发明内容
本申请实施例提供了一种安全元件中的应用的升级方法及相关设备，用于提高安全元件中的应用的安全性，并保障安全元件中的应用升级过程中用户数据不丢失。
本申请第一方面提供了一种安全元件中的应用的升级方法，包括：移动终端接收对应待升级应用的升级命令，该升级命令可以由可信服务管理服务器或用户触发；移动终端响应于所述升级命令，向可信服务管理服务器发送对应所述待升级应用的升级请求，该升级请求中可以携带所述待升级应用的版本信息；移动终端向所述可信服务管理服务器发送所 述待升级应用的重要数据；移动终端删除所述安全元件SE中的所述待升级应用的当前版本，所述待升级应用的当前版本包括所述重要数据；移动终端接收并安装所述可信服务管理服务器根据所述升级请求发送的所述待升级应用的更新版本；移动终端接收所述可信服务管理服务器发送的所述重要数据，并将接收的所述重要数据加载到所述待升级应用的更新版本中。本申请实施例，移动终端对安全元件中的应用进行升级，提高安全元件应用的安全性，并保障安全元件应用升级过程中用户数据不丢失。
在一种可能的设计中，在本申请实施例第一方面的第一种实现方式中，所述向可信服务管理服务器发送所述待升级应用的重要数据之前，所述升级方法还包括：通过所述SE将所述待升级应用的当前版本设置为只读模式。本申请实施例中，增加了将所述待升级应用设置为只读模式的过程，使本申请实施例在步骤上更完善。
在一种可能的设计中，在本申请实施例第一方面的第二种实现方式中，所述移动终端包括可信执行环境TEE和富执行环境REE，所述TEE中运行有安全应用TA，所述REE中运行有客户端应用CA；向可信服务管理服务器发送对应所述待升级应用的升级请求之前，所述方法还包括：通过所述TA生成所述待升级应用的升级请求，所述待升级应用的升级请求包括所述待升级应用的标识，或者，包括所述待升级应用的标识和所述待升级应用的当前版本的信息。本申请实施例，增加了生成所述待升级应用的升级请求的过程，使本申请实施例更具有逻辑性。
在一种可能的设计中，在本申请实施例第一方面的第三种实现方式中，对应待升级应用的升级命令由用户输入；向可信服务管理服务器发送对应所述待升级应用的升级请求和发送所述待升级应用的重要数据之前，所述方法还包括：通过所述TA或所述CA接收所述用户的用于验证身份的输入；通过所述TA对所述用户的用于验证身份的输入进行鉴权，并且鉴权通过。本申请实施例，增加了对用户的用于验证身份的输入进行鉴权的过程，增加了本申请实施例的实现方式。
在一种可能的设计中，在本申请实施例第一方面的第四种实现方式中，在向可信服务管理服务器发送对应所述待升级应用的升级请求之后，向所述可信服务管理服务器发送所述待升级应用的重要数据之前，所述升级方法还包括：通过所述SE接收所述可服务管理服务器发送的上传数据命令；向所述可信服务管理服务器发送所述待升级应用的重要数据包括，响应于所述上传数据命令，向所述可信服务管理服务器发送所述待升级应用的重要数据。本申请实施例中，增加了移动终端接收上传数据命令的过程，使本申请实施例在步骤上更完善。
本申请第二方面提供了一种安全元件中的应用的升级方法，由可信服务管理服务器执行，所述升级方法包括：可信服务管理服务器接收移动终端发送的对应待升级应用的升级请求；可信服务管理服务器接收所述移动终端发送的所述待升级应用的重要数据；可信服务管理服务器保存所述待升级应用的重要数据；可信服务管理服务器根据所述升级请求向所述移动终端发送所述待升级应用的更新版本；可信服务管理服务器向所述移动终端发送所述待升级应用的重要数据。本申请实施例，可信服务管理服务器对安全元件中的应用进行升级，提高安全元件应用的安全性，并保障安全元件应用升级过程中用户数据不丢失。
在一种可能的设计中，在本申请实施例第二方面的第一种实现方式中，在接收所述移动终端发送的所述待升级应用的重要数据之后，保存所述待升级应用的重要数据之前，所述升级方法还包括：将所述重要数据的全部数据与所述可信服务管理服务器中存储的对应的数据进行比对，并且比对成功。本申请实施例，增加了对重要数据的全部数据进行验证的过程，增加了本申请实施例的可实现性和可操作性。
在一种可能的设计中，在本申请实施例第二方面的第二种实现方式中，在接收所述移动终端发送的所述待升级应用的重要数据之后，保存所述待升级应用的重要数据之前，所述升级方法还包括：将所述重要数据的部分与所述可信服务管理服务器中存储的对应的数据进行比对，并且比对成功。本申请实施例，增加了对重要数据的部分数据的进行验证的过程，增加了本申请实施例的可实现性和可操作性。
在一种可能的设计中，在本申请实施例第二方面的第三种实现方式中，在接收移动终端发送的对应待升级应用的升级请求之后，接收所述移动终端发送的所述待升级应用的重要数据之前，所述升级方法还包括：向所述移动终端发送上传数据命令，所述上传数据命令用于指示所述移动终端上传所述重要数据。本申请实施例，增加了发送上传数据命令的过程，使本申请实施例更具有逻辑性。
在一种可能的设计中，在本申请实施例第二方面的第四种实现方式中，所述待升级应用的升级请求包括版本信息，在发送所述待升级应用的更新版本之前，所述升级方法还包括：根据所述待升级应用的版本信息判断所述待升级应用是否需要进行更新版本，并且判断结果为更新版本。本申请实施例，增加了判断待升级应用是否需要进行更新版本的过程，增加了本申请实施例的实现方式。
在一种可能的设计中，在本申请实施例第二方面的第五种实现方式中，在接收移动终端发送的对应待升级应用的升级请求之前，所述升级方法还包括：向所述移动终端发送应用升级命令，所述应用升级命令用于指示所述移动终端对安全元件中的待升级应用进行升级。本申请实施例，增加了可信服务管理服务器向所述移动终端发送应用升级命令的过程，增加了本申请实施例的实现方式。
本申请第三方面提供了一种移动终端，所述移动终端具有安全元件，所述安全元件安装有至少一个应用，所述移动终端包括：第一接收单元，用于接收对应待升级应用的升级命令；第一发送单元，用于响应于所述升级命令，向可信服务管理服务器发送对应所述待升级应用的升级请求；第二发送单元，用于向所述可信服务管理服务器发送所述待升级应用的重要数据；删除单元，用于删除所述安全元件SE中的所述待升级应用的当前版本，所述待升级应用的当前版本包括所述重要数据；第一处理单元，用于接收并安装所述可信服务管理服务器根据所述升级请求发送的所述待升级应用的更新版本；第二处理单元，用于接收所述可信服务管理服务器发送的所述重要数据，并将接收的所述重要数据加载到所述待升级应用的更新版本中。本申请实施例，移动终端对安全元件中的应用进行升级，提高安全元件应用的安全性，并保障安全元件应用升级过程中用户数据不丢失。
在一种可能的设计中，在本申请实施例第三方面的第一种实现方式中，所述移动终端还包括：设置单元，用于向可信服务管理服务器发送所述待升级应用的重要数据之前，通 过所述SE将所述待升级应用的当前版本设置为只读模式。本申请实施例中，增加了将所述待升级应用设置为只读模式的过程，使本申请实施例在步骤上更完善。
在一种可能的设计中，在本申请实施例第三方面的第二种实现方式中，所述移动终端包括可信执行环境TEE和富执行环境REE，所述TEE中运行有安全应用TA，所述REE中运行有客户端应用CA；所述移动终端还包括：生成单元，用于向可信服务管理服务器发送对应所述待升级应用的升级请求之前，通过所述TA生成所述待升级应用的升级请求，所述待升级应用的升级请求包括所述待升级应用的标识，或者，包括所述待升级应用的标识和所述待升级应用的当前版本的信息。本申请实施例，增加了生成所述待升级应用的升级请求的过程，使本申请实施例更具有逻辑性。
在一种可能的设计中，在本申请实施例第三方面的第三种实现方式中，对应待升级应用的升级命令由用户输入；所述移动终端还包括：第二接收单元，用于向可信服务管理服务器发送对应所述待升级应用的升级请求和发送所述待升级应用的重要数据之前，通过所述TA或所述CA接收所述用户的用于验证身份的输入；鉴权单元，用于通过所述TA对所述用户的用于验证身份的输入进行鉴权，并且鉴权通过。本申请实施例，增加了对用户的用于验证身份的输入进行鉴权的过程，增加了本申请实施例的实现方式。
在一种可能的设计中，在本申请实施例第三方面的第四种实现方式中，所述移动终端还包括：第三接收单元，用于在向可信服务管理服务器发送对应所述待升级应用的升级请求之后，向所述可信服务管理服务器发送所述待升级应用的重要数据之前，通过所述SE接收所述可服务管理服务器发送的上传数据命令；所述第二发送单元具体用于，响应于所述上传数据命令，向所述可信服务管理服务器发送所述待升级应用的重要数据。本申请实施例中，增加了移动终端接收上传数据命令的过程，使本申请实施例在步骤上更完善。
本申请第四方面提供了一种可信服务管理服务器，所述可信服务管理服务器包括：第一接收单元，用于接收移动终端发送的对应待升级应用的升级请求；第二接收单元，用于接收所述移动终端发送的所述待升级应用的重要数据；保存单元，用于保存所述待升级应用的重要数据；第一发送单元，用于根据所述升级请求向所述移动终端发送所述待升级应用的更新版本；第二发送单元，用于向所述移动终端发送所述待升级应用的重要数据。本申请实施例，可信服务管理服务器对安全元件中的应用进行升级，提高安全元件应用的安全性，并保障安全元件应用升级过程中用户数据不丢失。
在一种可能的设计中，在本申请实施例第四方面的第一种实现方式中，所述可信服务管理服务器还包括：第一比对单元，用于在接收所述移动终端发送的所述待升级应用的重要数据之后，保存所述待升级应用的重要数据之前，将所述重要数据的全部数据与所述可信服务管理服务器中存储的对应的数据进行比对，并且比对成功。本申请实施例，增加了对重要数据的全部数据进行验证的过程，增加了本申请实施例的可实现性和可操作性。
在一种可能的设计中，在本申请实施例第四方面的第二种实现方式中，所述可信服务管理服务器还包括：第二比对单元，用于在接收所述移动终端发送的所述待升级应用的重要数据之后，保存所述待升级应用的重要数据之前，将所述重要数据的部分数据与所述可信服务管理服务器中存储的对应的数据进行比对，并且比对成功。本申请实施例，增加了 对重要数据的部分数据的进行验证的过程，增加了本申请实施例的可实现性和可操作性。
在一种可能的设计中，在本申请实施例第四方面的第三种实现方式中，所述可信服务管理服务器还包括：第三发送单元，用于在接收移动终端发送的对应待升级应用的升级请求之后，接收所述移动终端发送的所述待升级应用的重要数据之前，向所述移动终端发送上传数据命令，所述上传数据命令用于指示所述移动终端上传所述重要数据。本申请实施例，增加了发送上传数据命令的过程，使本申请实施例更具有逻辑性。
在一种可能的设计中，在本申请实施例第四方面的第四种实现方式中，所述待升级应用的升级请求包括版本信息，所述可信服务管理服务器还包括：判断单元，用于在发送所述待升级应用的更新版本之前，根据所述待升级应用的版本信息判断所述待升级应用是否需要进行更新版本，并且判断结果为更新版本。本申请实施例，增加了判断待升级应用是否需要进行更新版本的过程，增加了本申请实施例的实现方式。
在一种可能的设计中，在本申请实施例第四方面的第五种实现方式中，所述可信服务管理服务器还包括：第四发送单元，用于在接收移动终端发送的对应待升级应用的升级请求之前，向所述移动终端发送应用升级命令，所述应用升级命令用于指示所述移动终端对安全元件中的待升级应用进行升级。本申请实施例，增加了可信服务管理服务器向所述移动终端发送应用升级命令的过程，增加了本申请实施例的实现方式。
本申请的第五方面提供了一种移动终端，包括，存储器、收发器和至少一个处理器，所述存储器中存储有程序代码，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述处理器运行所述代码以指令所述移动终端执行上述第一方面中任一项所述的方法。
本申请的第六方面提供了一种可信服务管理服务器，包括：存储器、收发器和至少一个处理器，所述存储器中存储有程序代码，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述处理器运行所述代码以指令所述可信服务管理服务器执行上述第二方面中任一项所述的方法。
本申请的第七方面提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有程序代码，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
本申请的第八方面提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有程序代码，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
本申请的第九方面提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
本申请的第十方面提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
附图说明
图1为本申请实施例应用的网络架构示意图；
图2A为本申请实施例中移动终端的一个结构示意图；
图2B为本申请实施例中可信服务管理服务器的一个结构示意图；
图3为本申请实施例中安全元件中的应用的升级方法一个实施例示意图；
图4为本申请实施例中安全元件中的应用的升级方法另一个实施例示意图；
图5为本申请实施例中移动终端的一个实施例示意图；
图6为本申请实施例中移动终端的另一个实施例示意图；
图7为本申请实施例中可信服务管理服务器的一个实施例示意图；
图8为本申请实施例中可信服务管理服务器的另一个实施例示意图。
具体实施方式
本申请实施例提供了一种安全元件中的应用的升级方法及相关设备，用于提高安全元件中的应用的安全性，并保障安全元件中的应用升级过程中用户数据不丢失。
为了使本技术领域的人员更好地理解本申请方案，下面将结合本申请实施例中的附图，对本申请实施例进行描述。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”或“具有”及其任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例可应用于如图1所示的网络架构，在该网络架构中，包括移动终端和可信服务管理(trusted service management，TSM)服务器，其中，根据全球平台组织(Global Platform，GP)在相关标准中的定义，TSM服务器分为两类：安全元件提供商的可信服务器管理(secure element issuer trusted service management，SEI-TSM)服务器和服务供应商可信服务管理(service provider trusted service management，SP-TSM)。SEI-TSM负责为SE提供商提供SE生命周期和安全域管理服务，而SP-TSM负责为服务提供商提供应用生命周期服务。移动终端有三种应用环境，分别为：富执行环境(rich execution environment，REE)、可信执行环境(trusted execution environment，TEE)和安全元件(secure element，SE)。
移动终端与服务器之间通过安全通道实现交互，实现对移动终端中的安全元件SE中的应用(Applet)的升级，其中，安全通道是用于传输交互数据的安全可信的传输环境。移动终端将待升级的Applet的业务提供方所定义重要数据封装成重要数据包并发送至TSM服务器，移动终端再将该待升级的Applet的当前版本删除，并从服务器下载该待升级的Applet的最新版本或特定版本，可以理解的是，特定版本比当前版本的版本更新(即特定版本更新)。当Applet的最新版本安装完成后，移动终端从服务器下载之前上传的重要数据包，将重要数据包中的重要数据导入已经下载安装的最新版本Applet中或特定版本的Applet中，从而完成对待升级的Applet的版本更新。
需要说明的是，TA为运行在TEE中的应用，可以访问移动终端的处理器和内存，Applet 为SE中的应用，安全元件SE可以有多种形态，包括SIM卡(通常被移动运营商用作安全模块)、手机中嵌入的芯片以及直接与近距离无线通信(near field communication，NFC)芯片连接的microSD卡等。SE为移动终端中的一块独立的芯片，TEE与SE之间也可以建立安全通道，TA与Applet之间的数据交互可以通过安全通道进行传输。TEE具有其自身的执行空间，比REE操作系统的安全级别更高，并且TEE并不是独立的物理安全芯片，而是与目前使用的应用处理器的硬件架构重叠在一起的安全架构。TEE所能访问的软硬件资源是与REE操作系统分离的，提供硬件支持的隔离。SE中的应用可以为手机盾、eID、银行卡、公交卡等应用，该TEE Client API和TEE Internal API可以分别采用TEE Client API V1.0标准和TEE Internal API V1.0标准，如图2A所示为本申请实施例的一种移动终端的组成示意图。其中的硬件部分可以包括：存储器，处理器和通信单元。该存储器用于存储移动终端的程序代码和数据，例如该存储器中的受保护区域可以存储可信执行环境操作系统(trusted execution environment operating system，TEE OS)和TEE中的应用(TEE application，TA)，该存储器的非受保护区域可以存储富执行环境操作系统(rich execution environment operating system，REE OS)和TEE中的应用(REE application，CA)，SE中的存储器可以存储卡操作系统(card operating system，COS)和各种应用等。处理器(或控制器)，例如可以是中央处理器(central processing unit，CPU)，通用处理器，数字信号处理器(digital signal processor，DSP)，专用集成电路(application-specific integrated circuit，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合，例如，该处理器可以包括应用处理器芯片中的处理器，和SE中的处理器，分别用于运行前述的各种程序代码以指令移动终端完成本发明实施例描述的各种操作。该通信单元可以为射频电路等，用于与可信服务管理服务器之间进行交互。
可选的，本申请实施例还提供一种移动终端，不包括SE，该移动终端具有存储器，处理器和通信单元，该存储器程序代码和数据，例如该存储器中受保护区域可以存储TEE OS和TA，该存储器的非受保护区域可以REE OS和CA，该处理器执行该存储器中的程序代码以指令该移动终端完成下述方法实施例中的操作，以实现与SE和可信服务管理服务器的交互。
图2B是本申请实施例提供的一种可信服务管理服务器的结构示意图，该可信服务管理服务器200可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上处理器(central processing units，CPU)201(例如，一个或一个以上处理器)和存储介质208，一个或一个以上存储应用程序207或数据206的存储介质208(例如一个或一个以上海量存储设备)。其中，存储介质208可以是短暂存储或持久存储。存储在存储介质208的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对可信服务管理服务器中的一系列代码。更进一步地，处理器201可以设置为与存储介质208通信，处理器201是可信服务管理服务器的控制中心，可利用各种接口和线路连接整个可信服务管理服务器的各个部分，通过运行或执行存储在存储介质208内的软件程序和/或模块，以及调用存储在存储介质208内的数据，执行可信服务管理服务器的各种功能和处理数据，从而实现安全 元件中的应用的升级。
存储介质208可用于存储软件程序以及模块，处理器201通过运行存储在存储介质208的软件程序以及模块，从而执行可信服务管理服务器200的各种功能应用以及数据处理。存储介质208可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如判断Applet是否需要进行更新版本等)等；存储数据区可存储根据可信服务管理服务器的使用所创建的数据(比如上传数据命令等)等。此外，存储介质208可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。在本申请实施例中提供的安全元件应用的升级方法的程序和接收到的数据流存储在存储器中，当需要使用时，处理器201从存储介质208中调用。
可信服务管理服务器200还可以包括一个或一个以上电源202，一个或一个以上有线或无线网络接口203，一个或一个以上输入输出接口204，和/或，一个或一个以上操作系统205，例如Windows Serve，Mac OS X，Unix，Linux，FreeBSD等等。本领域技术人员可以理解，图2B中示出的可信服务管理服务器结构并不构成对可信服务管理服务器的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
为了便于描述，对本申请实施例中涉及的术语进行说明。本申请中描述的移动终端可以为手机、平板电脑等同时具备REE、TEE和SE三种安全环境的移动终端；本申请中描述的服务器为可信服务管理服务器，可信服务管理服务器具体可以包括安全元件发行商的可信服务管理(secure element issuer trusted service management，SEI-TSM)系统和服务供应商可信服务管理(Service Provider trusted service management，SP-TSM)系统；本申请实施例中的应用升级命令(Applet升级命令)可以由用户进行操作触发或者是由可信服务管理服务器生成并发送至移动终端；本申请实施例中的第一待升级应用升级请求(Applet升级请求)由CA根据应用升级命令生成，第二待升级应用升级请求由TA根据第一待升级应用升级请求生成，并且该第二待升级应用升级请求可以携带待升级应用的版本信息，待升级应用的版本信息也可以单独作为一个消息发送至可信服务管理服务器；移动终端从可信服务管理服务器下载的待升级应用的版本可以是最新版本，也可以是更新的特定版本，该特定版本可以满足待升级应用的业务提供方的特殊安全要求，本申请实施例以最新版本为例进行说明。本申请实施例中的重要数据由待升级应用的业务提供方来定义，对于不同的应用Applet，定义的重要数据可以相同也可以不同，例如，公交卡Applet的业务提供方可以将金额定义为重要数据，电子身份标识eID的业务提供方可以将身份信息定义为重要数据。本申请实施例中，Applet升级请求可以由用户进行触发，还可以是由服务器进行触发。
为便于理解，下面对本申请实施例的具体流程进行描述，请参阅图3，本申请实施例中安全元件中的应用的升级方法的一个实施例包括：
301、CA接收用户的应用升级命令。
用户根据自身的需要，在使用移动终端的过程中，发现安全元件中的至少一个应用Applet需要升级(即待升级Applet需要进行升级)，则用户在CA中触发目标Applet升级 命令。举例说明，用户在使用移动终端的公交卡功能过程中，通过公交公司发送的通知信息，发现公交卡的版本可能需要进行更新版本，则用户在移动终端的设置界面中找到公交卡应用，并选择升级公交卡。需要说明的是，Applet升级命令可以由CA进行接收和解析，并将解析结果转发给TA；还可以是由CA将该Applet升级命令进行转发给TA，CA只起转发作用，TA接收在接收到该Applet升级命令后对该Applet升级命令进行解析。
可以理解的是，用户在移动终端上触发升级命令后，在移动终端完成待升级应用的更新版本和重要数据之前，移动终端保持网络连接功能处于开启状态并可以进行网络下载，例如，移动终端可以不执行用户关闭网络连接功能的操作，以确保移动终端能够对待升级Applet的升级过程顺利进行。
302、CA将第一待升级应用升级请求发送给TA。
移动终端的REE中CA根据用户的应用升级命令，向TEE中TA发送第一待升级应用升级请求，该第一待升级应用请求中携带有待升级应用的标识，用于TA确定需要升级的Applet。例如，在REE中公交卡CA根据用户的升级命令，通过REE与TEE之间的传输通道向TA发送公交卡应用升级请求，该公交卡应用升级请求中至少携带有用于区别其他Applet的标识信息。
303、TA对第一待升级应用升级请求进行鉴权。
移动终端的TA对用户进行身份认证，利用的手段包括但不限于个人识别码(personal identification number，PIN)、指纹、虹膜、人脸识别等验证，以核实该Applet升级操作为移动终端的机主本人触发，例如，当使用PIN码进行验证，当移动终端中预先存储的PIN码与用户输入的PIN码相同，则确定该第一待升级应用升级请求操作为移动终端的机主本人触发，TA确定生成的该第一待升级应用升级请求是合法的，TA根据该第一待升级应用升级请求获取对应Applet的版本信息。TA可以利用TEE所具有的安全能力，包括但不限于可信用户接口(trusted user interface，TUI)、安全存储、安全生物识别能力、可信时钟等。
以指纹认证为例，具体的，在用户通过CA输入升级命令之后，TA在获取到CA生成的相应升级请求后，TA向用户提供验证界面，例如，TA提醒用户验证指纹信息，用户根据提示进行指纹录入操作，TA调用移动终端对用户录入的指纹进行识别，例如，可以通过移动终端上的指纹采集装置直接采集或者是通过触摸屏进行采集；TA将采集到的指纹信息与移动终端内已存储的指纹信息进行匹配，若匹配，则确定Applet升级操作为移动终端的机主本人触发，TA确定生成的该Applet升级请求是合法的，TA根据该Applet升级请求获取对应Applet的版本信息。可以理解的是，用作匹配模板的PIN和指纹信息等信息在进行匹配之前，已存储在移动终端的存储器内，当需要使用时，TA从存储器中调用。其中，移动终端具有用于进行指纹采集的功能模块。
以PIN码认证为例，具体的，在用户通过CA输入升级命令之后，TA在获取到CA生成的相应的第一待升级应用升级请求后，TA向用户提供一个可信输入框用以采集用户输入的PIN码，TA判断用户输入的PIN码是否正确；若正确，则可以确认该升级操作为移动终端的机主本人主动进行的Applet升级操作，TA确定CA生成的该第一待升级应用升级请求是 合法的，TA根据该第一待升级应用升级请求获取对应待升级应用的版本信息；若不正确，则执行其他操作，例如，再验证一次，或者终止本次Applet升级操作，具体此处不做限定。
可以理解的是，PIN码由TA进行存储并验证。该PIN码可以根据用户的需要进行修改。
304、TA向Applet获取待升级应用的版本信息。
TA向Applet发送获取Applet版本(GET APPLET VERSION)命令，Applet用约定的密钥对升级数据进行加密和签名，并返回给TA。升级数据包括SE ID、待升级应用的当前版本信息等。具体的，约定的密钥可以是安全存储密钥(secure storage key，SSK)，例如，不同的移动终端设备中的SSK的值不一样，在TEE启动的时候会使用chip ID和HUK经过哈希运算消息认证码(hash-based message authentication code，HMAC)计算获取SSK的值，其中，HUK和chip ID都预置在移动终端的芯片中。还可以是可信应用存储密钥(trusted applicant storage key，TASK)等其他密钥，具体此处不做限定。
可以理解的是，一般情况下，通过不对称加密算法得到两把完全不同但又是完全匹配的一对钥匙：公钥和私钥。在使用不对称加密算法加密文件时，需要使用匹配的两对公钥和私钥，完成对明文的加密和解密过程。对数据进行加密时采用目标公钥加密，对数据进行解密时需要使用与目标公钥匹配的私钥，从而完成加密解密过程。当移动终端对数据进行签名时，采用目标私钥进行签名，可信服务管理服务器在接收到数据后，采用与目标私钥匹配的公钥识别该签名。在发送加密和签名后的数据之前，移动终端必须将与目标公钥相匹配的私钥、与目标私钥相匹配的公钥发送给可信服务管理服务器，而自己保留目标私钥和目标公钥。
305、TA将第二待升级应用升级请求和待升级应用的版本信息发送至可信服务管理服务器。
TA将第二待升级应用升级请求和待升级应用的版本信息发送至可信服务管理(trusted service management，TSM)服务器，其中，待升级应用的版本信息可以携带于第二待升级应用升级请求中，还可以单独作为一个消息发送至TSM服务器，带升级应用的版本信息已经被TA进行过加密和签名。
306、TSM服务器判断待升级应用是否需要进行更新版本。
TSM服务器对第二待升级应用升级请求进行分析，获取到待升级应用的标识信息，TSM服务器根据Applet的标识信息和待升级应用的版本信息判断待升级应用是否需要进行更新版本；若当前Applet版本已是最新，则不需要更新，通知移动终端不需要进行更新，例如，通知用户当前Applet版本已是最新，不需要进行升级，或者是，通知移动终端该待升级应用没有可更新的新版本；若当前Applet版本不是最新的，则需要对Applet进行更新版本，执行步骤307。可以理解的是，不同的Applet对应的业务提供方还可以对自己的TSM服务器采用其他的商业策略，商业策略是业务提供方根据自身业务需要制定的执行标准，例如，公交卡的业务提供方的商业策略可以为：若公交卡应用的版本不为最新的，则在移动终端使用公交卡功能时提示进行升级；公交卡的业务提供方的商业策略还可以为：若公交卡应用的版本不为最新的，则在移动终端连接到无线网络的情况下，提示用户对公交卡应用进行升级。
具体的，当Applet不需要进行更新时，TSM服务器经由TA通知CA，终止升级，具体的，TSM可以下发终止升级的命令，以使得移动终端停止Applet升级过程。当Applet需要进行更新时，TSM服务器同Applet建立安全通道，下发上传数据命令，用于指示移动终端上传重要数据。
307、Applet将自身锁定BLOCK。
Applet将自身锁定BLOCK，具体的形式可以是，将Applet的属性修改为只读模式，Applet的数据不能进行修改，以使重要数据不能再被更新。Applet按约定格式对各个重要数据进行打包汇总，形成重要数据包，其中，重要数据包可以包括重要数据及待升级应用的安装信息等，约定格式可以采用多种形式，例如，可以是常用的IP数据包格式，还可以是其他格式，具体此处不做限定。
例如，公交卡Applet可以根据公交卡的业务提供方定义的金额作为重要数据，公交卡Applet在被BLOCK后，其中的金额不能再发生改变，移动终端也不能使用公交卡业务功能，例如，不能再使用公交卡功能进行刷卡付费业务。
需要说明的是，业务提供方需要为自己的Applet定义重要数据及其格式，并使其TSM服务器可以识别处理同样的重要数据及其格式。
可以理解的是，重要数据包在SE内部进行数据的收集、汇总和打包，具体处理过程此处不做限定。
308、Applet向TSM服务器发送重要数据。
Applet通过安全通道向TSM服务器发送上传数据(UPLOAD DATA)命令的响应，该上传数据命令的响应包含该重要数据。
需要说明的是，安全通道为TSM服务器与SE之间建立的成熟可用的传输通道，安全通道为重要数据提供了必要的安全保障，安全通道的具体建立过程与现有技术相同，例如，可以利用安全套接层(Secure Sockets Layer，SSL)协议和/或传输层安全(Transport Layer Security，TLS)协议建立安全通道，此处不再赘述。除了安全通道传输重要数据包，Applet可以选择再用特定的密钥对重要数据包进行加密签名，以进一步增加安全性。在这种情况下，TSM服务器也需按相应的逻辑进行解密和签名验证。
309、TSM服务器对重要数据进行验证。
TSM服务器对重要数据进行验证。当TSM服务器接收Applet发送的上传数据命令响应，并获取到该上传数据命令响应中携带的重要数据包时，对该重要数据包中的部分或全部数据与预先存储在TSM服务器上的数据进行比对以确认重要数据的正确性，例如，在进行部分数据比对时，在重要数据包中数据中按照预置规则选择部分数据，并将该部分数据与TSM服务器中存储的数据进行验证，例如，采用IP校验算法，从数据中选择出20字节长度的数据与可信服务管理上存储的对应数据进行比对的数据。当TSM服务器在预置时长内未接收到上传数据命令响应，例如，在3分钟之内没有接收到上传数据命令响应，或根据策略终止升级(例如，重要数据包比对不成功，认为有严重安全问题，确定重要数据包不正确)，则TSM服务器可以向Applet下发解封UNBLOCK命令，并通知CA更新版本失败，移动在接收到UNBLOCK命令之后，解除对Applet的锁定，具体的，将Applet的属性从只读模式设 置为读写模式；或TSM服务器不发UNBLOCK命令，保持该Applet的BLOCK状态，Applet的属性一直为只读模式，其他设备只能对Applet的数据进行读取，并不能对数据进行修改。
需要说明的是，当可信服务管理服务器上的数据与移动终端内的数据不同步时，移动终端执行上述步骤308和309；当可信服务管理服务器上的数据与移动终端内的数据同步时，移动终端不需要上传重要数据，只需上传重要数据清单(即，将步骤308和309替换为上报重要数据清单的步骤)，在移动终端下载待升级应用的更新版本后，可信服务管理服务器将重要数据清单对应的重要数据下发至移动终端。
310、TSM服务器向移动终端发送待升级应用的更新版本。
TSM服务器向移动终端发送该待升级应用的更新版本。具体的，TSM服务器向SE下发DELETE命令，SE删除该Applet的当前版本。在完成Applet的当前版本的删除后，TSM服务器向SE下发LOAD、INSTALL命令，LOAD、INSTALL命令由SE进行执行，SE从服务器下载待升级应用的更新版本并安装。
需要说明的是，SE中的Applet在进行升级更新时，区别于REE中的CA，SE必须将旧版本的Applet删除之后，才可以下载新版本的Applet。
311、TSM服务器对更新版本的Applet进行数据同步。
TSM服务器向新版本的Applet下发STORE DATA命令，并将重要数据和其他相关信息(例如，用于对待升级应用进行解封的相关信息)同步到新版本的Applet。TSM服务器可以向Applet下发其他命令，比如下载命令，使Applet的下载功能完全开通，例如，向移动终端的U盾Applet发送下载证书命令，以使得U盾Applet完成安全证书的下载，还可以是其他命令，具体此处不做限定。
需要说明的是，将重要数据包中的重要数据下载移动终端的过程中，同样需要利用SE和TSM服务器之间的安全通道，充分保障数据迁移的安全。
312、TSM服务器通知更新Applet成功。
TSM服务器在将重要数据包中重要数据的加载到待升级应用的更新版本中后，会接收到更新版本的Applet反馈的消息，以确认更新Applet成功。TSM服务器经由CA向用户显示结果，提示用户更新Applet成功。
本申请实施例中，用户选择触发Applet升级后，移动终端将重要数据打包上传至TSM服务器，在Applet新版本安装成功后将之前上传的重要数据同步至更新版本的Applet，提高了安全元件应用Applet的数据安全性，并保障安全元件应用Applet升级过程中用户数据不丢失。
请参阅图4，本申请实施例中安全元件中的应用的升级方法的另一个实施例包括：
401、CA接收TSM服务器发送的应用升级命令。
TSM服务器根据业务提供方的特定策略，确定安全元件中的至少一个应用Applet需要升级后，TSM服务器向CA发送应用升级命令，移动终端通过CA接收TSM服务器发送的Applet升级命令。举例说明，对于移动终端的公交卡功能，该公交卡功能的业务提供方(公交卡公司)根据特定策略，例如，确定对服务平台进行升级或发现原版本Applet存在重大安全漏洞，相应的公交卡Applet也需要进行升级以满足升级后的服务平台的使用要求。公交卡 公司通过TSM服务器向移动终端的CA发送应用升级命令，并在特定的时机(例如，手机处于空闲状态时)在CA中触发公交卡应用升级。需要说明的是，不同的Applet对应的业务提供方还可以对自己的TSM服务器采用其他的策略。
可以理解的是，TSM服务器在移动终端上触发升级命令后，在移动终端完成待升级应用的更新版本和重要数据之前，移动终端保持网络连接功能处于开启状态并可以进行网络下载，例如，移动终端可以不执行用户关闭网络连接功能的操作，以确保移动终端能够对待升级Applet的升级过程顺利进行。
402、CA将第一待升级应用升级请求发送给TA。
步骤402与步骤302类似，具体此处不再赘述。
403、TA根据预置的业务提供方策略决定是否进行验证。
TA根据预置的业务提供方策略决定是否进行验证。若业务提供方策略需要进行验证，则进行验证，若业务提供方策略不需要进行验证，则执行步骤404。
404、TA向Applet获取待升级应用的版本信息。
405、TA将第二待升级应用升级请求和待升级应用的版本信息发送至可信服务管理服务器。
步骤404至步骤405与步骤304至步骤305类似，具体此处不再赘述。
406、Applet将自身锁定BLOCK。
407、Applet向TSM服务器发送重要数据。
408、TSM服务器对重要数据进行验证。
409、TSM服务器向移动终端发送待升级应用的更新版本。
410、TSM服务器对更新版本的Applet进行数据同步。
411、TSM服务器通知更新Applet成功。
步骤406至步骤411与步骤307至步骤312类似，具体此处不再赘述。
本申请实施例中，TSM服务器下发Applet升级命令至移动终端后，移动终端Applet在升级过程中将重要数据打包上传至TSM服务器，在Applet新版本安装成功后，将之前上传的重要数据同步至更新版本的Applet中，提高了安全元件应用Applet的数据安全性，并保障安全元件应用Applet升级过程中用户数据不丢失。
上面对本申请实施例中安全元件中的应用的升级方法进行了描述，下面对本申请实施例中的移动终端和可信服务管理服务器进行描述，请参阅图5，本申请实施例中移动终端的一个实施例包括：
第一接收单元501，用于接收对应待升级应用的升级命令；
第一发送单元502，用于响应于所述升级命令，向可信服务管理服务器发送对应所述待升级应用的升级请求；
第二发送单元503，用于向所述可信服务管理服务器发送所述待升级应用的重要数据；
删除单元504，用于删除所述安全元件SE中的所述待升级应用的当前版本，所述待升级应用的当前版本包括所述重要数据；
第一处理单元505，用于接收并安装所述可信服务管理服务器根据所述升级请求发送 的所述待升级应用的更新版本；
第二处理单元506，用于接收所述可信服务管理服务器发送的所述重要数据，并将接收的所述重要数据加载到所述待升级应用的更新版本中。
本申请实施例，移动终端对安全元件中的应用进行升级，提高安全元件应用的安全性，并保障安全元件应用升级过程中用户数据不丢失。
请参阅图6，本申请实施例中移动终端的另一个实施例包括：
第一接收单元601，用于接收对应待升级应用的升级命令；
第一发送单元602，用于响应于所述升级命令，向可信服务管理服务器发送对应所述待升级应用的升级请求；
第二发送单元603，用于向所述可信服务管理服务器发送所述待升级应用的重要数据；
删除单元604，用于删除所述安全元件SE中的所述待升级应用的当前版本，所述待升级应用的当前版本包括所述重要数据；
第一处理单元605，用于接收并安装所述可信服务管理服务器根据所述升级请求发送的所述待升级应用的更新版本；
第二处理单元606，用于接收所述可信服务管理服务器发送的所述重要数据，并将接收的所述重要数据加载到所述待升级应用的更新版本中。
在一个示例中，移动终端还可以进一步包括：
设置单元607，用于向可信服务管理服务器发送所述待升级应用的重要数据之前，通过所述SE将所述待升级应用的当前版本设置为只读模式。
在一个示例中，移动终端还可以进一步包括：
生成单元608，用于向可信服务管理服务器发送对应所述待升级应用的升级请求之前，通过所述TA生成所述待升级应用的升级请求，所述待升级应用的升级请求包括所述待升级应用的标识，或者，包括所述待升级应用的标识和所述待升级应用的当前版本的信息。
在一个示例中，移动终端还可以进一步包括：
第二接收单元609，用于向可信服务管理服务器发送对应所述待升级应用的升级请求之前，通过所述TA或所述CA接收所述用户的用于验证身份的输入；
鉴权单元610，用于通过所述TA对所述用户的用于验证身份的输入进行鉴权，并且鉴权通过。
在一个示例中，移动终端还可以进一步包括：
第三接收单元611，用于在向可信服务管理服务器发送对应所述待升级应用的升级请求之后，向所述可信服务管理服务器发送所述待升级应用的重要数据之前，通过所述SE接收所述可服务管理服务器发送的上传数据命令；
所述第二发送单元609具体用于，响应于所述上传数据命令，向所述可信服务管理服务器发送所述待升级应用的重要数据。
本申请实施例中，移动终端在接收到Applet升级命令后，移动终端在Applet的升级过程中将重要数据打包上传至TSM服务器，在Applet的更新版本安装成功后将之前上传的重要数据同步至更新版本的Applet，提高了安全元件中的应用Applet的安全性，并保障 安全元件中的应用Applet升级过程中用户数据不丢失。
请参阅图7，本申请实施例中可信服务管理服务器的一个实施例包括：
第一接收单元701，用于接收移动终端发送的对应待升级应用的升级请求；
第二接收单元702，用于接收所述移动终端发送的所述待升级应用的重要数据；
保存单元703，用于保存所述待升级应用的重要数据；
第一发送单元704，用于根据所述升级请求向所述移动终端发送所述待升级应用的更新版本；
第二发送单元705，用于向所述移动终端发送所述待升级应用的重要数据。
本申请实施例，可信服务管理服务器对安全元件中的应用进行升级，提高安全元件应用的安全性，并保障安全元件中的应用升级过程中用户数据不丢失。
请参阅图8，本申请实施例中可信服务管理服务器的另一个实施例包括：
第一接收单元801，用于接收移动终端发送的对应待升级应用的升级请求；
第二接收单元802，用于接收所述移动终端发送的所述待升级应用的重要数据；
保存单元803，用于保存所述待升级应用的重要数据；
第一发送单元804，用于根据所述升级请求向所述移动终端发送所述待升级应用的更新版本；
第二发送单元805，用于向所述移动终端发送所述待升级应用的重要数据。
在一个示例中，可信服务管理服务器还可以进一步包括：
第一比对单元806，用于在接收所述移动终端发送的所述待升级应用的重要数据之后，保存所述待升级应用的重要数据之前，将所述重要数据的全部数据与可信服务管理服务器中存储的数据进行比对，并且比对成功。
在一个示例中，验证单元805具体用于：
第二比对单元807，用于在接收所述移动终端发送的所述待升级应用的重要数据之后，保存所述待升级应用的重要数据之前，将所述重要数据的部分数据与可信服务管理服务器中存储的数据进行比对，并且比对成功。
在一个示例中，可信服务管理服务器还可以进一步包括：
第三发送单元808，用于在接收移动终端发送的对应待升级应用的升级请求之后，接收所述移动终端发送的所述待升级应用的重要数据之前，向所述移动终端发送上传数据命令，所述上传数据命令用于指示所述移动终端上传所述重要数据。
在一个示例中，可信服务管理服务器还可以进一步包括：
判断单元809，用于在发送所述待升级应用的更新版本之前，根据所述待升级应用的版本信息判断所述待升级应用是否需要进行更新版本。
在一个示例中，可信服务管理服务器还可以进一步包括：
第四发送单元810，用于在接收移动终端发送的对应待升级应用的升级请求之前，向所述移动终端发送应用升级命令，所述应用升级命令用于指示所述移动终端对安全元件中的待升级应用进行升级。
本申请实施例中，可信服务管理服务器在Applet的升级过程中接收移动终端发送的重 要数据，在Applet完成升级后，将接收到的重要数据同步至更新版本的Applet，提高了安全元件中的应用Applet的安全性，并保障安全元件中的应用Applet升级过程中用户数据不丢失。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (26)

  1. 一种安全元件中的应用的升级方法，所述安全元件安装有至少一个应用，所述方法由具有所述安全元件的移动终端执行，其特征在于，所述方法包括：
    接收对应待升级应用的升级命令；
    响应于所述升级命令，向可信服务管理服务器发送对应所述待升级应用的升级请求；
    向所述可信服务管理服务器发送所述待升级应用的重要数据；
    删除所述安全元件SE中的所述待升级应用的当前版本，所述待升级应用的当前版本包括所述重要数据；
    接收并安装所述可信服务管理服务器根据所述升级请求发送的所述待升级应用的更新版本；
    接收所述可信服务管理服务器发送的所述重要数据，并将接收的所述重要数据加载到所述待升级应用的更新版本中。
  2. 根据权利要求1所述的升级方法，其特征在于，所述向可信服务管理服务器发送所述待升级应用的重要数据之前，所述升级方法还包括：
    通过所述SE将所述待升级应用的当前版本设置为只读模式。
  3. 根据权利要求1或2所述的升级方法，其特征在于，所述移动终端包括可信执行环境TEE和富执行环境REE，所述TEE中运行有安全应用TA，所述REE中运行有客户端应用CA；
    向可信服务管理服务器发送对应所述待升级应用的升级请求之前，所述方法还包括：
    通过所述TA生成所述待升级应用的升级请求，所述待升级应用的升级请求包括所述待升级应用的标识，或者，包括所述待升级应用的标识和所述待升级应用的当前版本的信息。
  4. 根据权利要求3所述的升级方法，其特征在于，对应待升级应用的升级命令由用户输入；
    向可信服务管理服务器发送对应所述待升级应用的升级请求和发送所述待升级应用的重要数据之前，所述方法还包括：
    通过所述TA或所述CA接收所述用户的用于验证身份的输入；
    通过所述TA对所述用户的用于验证身份的输入进行鉴权，并且鉴权通过。
  5. 根据权利要求1至4中任一项所述的升级方法，其特征在于，在向可信服务管理服务器发送对应所述待升级应用的升级请求之后，向所述可信服务管理服务器发送所述待升级应用的重要数据之前，所述升级方法还包括：
    通过所述SE接收所述可服务管理服务器发送的上传数据命令；
    向所述可信服务管理服务器发送所述待升级应用的重要数据包括，响应于所述上传数据命令，向所述可信服务管理服务器发送所述待升级应用的重要数据。
  6. 一种安全元件应用的升级方法，由可信服务管理服务器执行，其特征在于，所述升级方法包括：
    接收移动终端发送的对应待升级应用的升级请求；
    接收所述移动终端发送的所述待升级应用的重要数据；
    保存所述待升级应用的重要数据；
    根据所述升级请求向所述移动终端发送所述待升级应用的更新版本；
    向所述移动终端发送所述待升级应用的重要数据。
  7. 根据权利要求6所述的升级方法，其特征在于，在接收所述移动终端发送的所述待升级应用的重要数据之后，保存所述待升级应用的重要数据之前，所述升级方法还包括：
    将所述重要数据的全部数据与所述可信服务管理服务器中存储的对应的数据进行比对，并且比对成功。
  8. 根据权利要求6所述的升级方法，其特征在于，在接收所述移动终端发送的所述待升级应用的重要数据之后，保存所述待升级应用的重要数据之前，所述升级方法还包括：
    将所述重要数据的部分数据与所述可信服务管理服务器中存储的对应的数据进行比对，并且比对成功。
  9. 根据权利要求6至8中任一项所述的升级方法，其特征在于，在接收移动终端发送的对应待升级应用的升级请求之后，接收所述移动终端发送的所述待升级应用的重要数据之前，所述升级方法还包括：
    向所述移动终端发送上传数据命令，所述上传数据命令用于指示所述移动终端上传所述重要数据。
  10. 根据权利要求6至9中任一项所述的升级方法，其特征在于，所述待升级应用的升级请求包括版本信息，在发送所述待升级应用的更新版本之前，所述升级方法还包括：
    根据所述待升级应用的版本信息判断所述待升级应用是否需要进行更新版本，并且判断结果为更新版本。
  11. 根据权利要求6至9中任一项所述的升级方法，其特征在于，在接收移动终端发送的对应待升级应用的升级请求之前，所述升级方法还包括：
    向所述移动终端发送应用升级命令，所述应用升级命令用于指示所述移动终端对安全元件中的待升级应用进行升级。
  12. 一种移动终端，所述移动终端具有安全元件，所述安全元件安装有至少一个应用，其特征在于，所述移动终端包括：
    第一接收单元，用于接收对应待升级应用的升级命令；
    第一发送单元，用于响应于所述升级命令，向可信服务管理服务器发送对应所述待升级应用的升级请求；
    第二发送单元，用于向所述可信服务管理服务器发送所述待升级应用的重要数据；
    删除单元，用于删除所述安全元件SE中的所述待升级应用的当前版本，所述待升级应用的当前版本包括所述重要数据；
    第一处理单元，用于接收并安装所述可信服务管理服务器根据所述升级请求发送的所述待升级应用的更新版本；
    第二处理单元，用于接收所述可信服务管理服务器发送的所述重要数据，并将接收的所述重要数据加载到所述待升级应用的更新版本中。
  13. 根据权利要求12所述的移动终端，其特征在于，所述移动终端还包括：
    设置单元，用于向可信服务管理服务器发送所述待升级应用的重要数据之前，通过所述SE将所述待升级应用的当前版本设置为只读模式。
  14. 根据权利要求12或13所述的移动终端，其特征在于，所述移动终端包括可信执行环境TEE和富执行环境REE，所述TEE中运行有安全应用TA，所述REE中运行有客户端应用CA；
    所述移动终端还包括：
    生成单元，用于向可信服务管理服务器发送对应所述待升级应用的升级请求之前，通过所述TA生成所述待升级应用的升级请求，所述待升级应用的升级请求包括所述待升级应用的标识，或者，包括所述待升级应用的标识和所述待升级应用的当前版本的信息。
  15. 根据权利要求14所述的移动终端，其特征在于，对应待升级应用的升级命令由用户输入；
    所述移动终端还包括：
    第二接收单元，用于向可信服务管理服务器发送对应所述待升级应用的升级请求和发送所述待升级应用的重要数据之前，通过所述TA或所述CA接收所述用户的用于验证身份的输入；
    鉴权单元，用于通过所述TA对所述用户的用于验证身份的输入进行鉴权，并且鉴权通过。
  16. 根据权利要求12至15中任一项所述的移动终端，其特征在于，所述移动终端还包括：
    第三接收单元，用于在向可信服务管理服务器发送对应所述待升级应用的升级请求之后，向所述可信服务管理服务器发送所述待升级应用的重要数据之前，通过所述SE接收所述可服务管理服务器发送的上传数据命令；
    所述第二发送单元具体用于，响应于所述上传数据命令，向所述可信服务管理服务器发送所述待升级应用的重要数据。
  17. 一种可信服务管理服务器，其特征在于，所述可信服务管理服务器包括：
    第一接收单元，用于接收移动终端发送的对应待升级应用的升级请求；
    第二接收单元，用于接收所述移动终端发送的所述待升级应用的重要数据；
    保存单元，用于保存所述待升级应用的重要数据；
    第一发送单元，用于根据所述升级请求向所述移动终端发送所述待升级应用的更新版本；
    第二发送单元，用于向所述移动终端发送所述待升级应用的重要数据。
  18. 根据权利要求17所述的可信服务管理服务器，其特征在于，所述可信服务管理服务器还包括：
    第一比对单元，用于在接收所述移动终端发送的所述待升级应用的重要数据之后，保存所述待升级应用的重要数据之前，将所述重要数据的全部数据与所述可信服务管理服务器中存储的对应的数据进行比对，并且比对成功。
  19. 根据权利要求17所述的可信服务管理服务器，其特征在于，所述可信服务管理服 务器还包括：
    第二比对单元，用于在接收所述移动终端发送的所述待升级应用的重要数据之后，保存所述待升级应用的重要数据之前，将所述重要数据的部分数据与所述可信服务管理服务器中存储的对应的数据进行比对，并且比对成功。
  20. 根据权利要求17至19中任一项所述的可信服务管理服务器，其特征在于，所述可信服务管理服务器还包括：
    第三发送单元，用于在接收移动终端发送的对应待升级应用的升级请求之后，接收所述移动终端发送的所述待升级应用的重要数据之前，向所述移动终端发送上传数据命令，所述上传数据命令用于指示所述移动终端上传所述重要数据。
  21. 根据权利要求17至20中任一项所述的可信服务管理服务器，其特征在于，所述待升级应用的升级请求包括版本信息，所述可信服务管理服务器还包括：
    判断单元，用于在发送所述待升级应用的更新版本之前，根据所述待升级应用的版本信息判断所述待升级应用是否需要进行更新版本，并且判断结果为更新版本。
  22. 根据权利要求17至20中任一项所述的可信服务管理服务器，其特征在于，所述可信服务管理服务器还包括：
    第四发送单元，用于在接收移动终端发送的对应待升级应用的升级请求之前，向所述移动终端发送应用升级命令，所述应用升级命令用于指示所述移动终端对安全元件中的待升级应用进行升级。
  23. 一种移动终端，其特征在于，包括：存储器、收发器和至少一个处理器，所述存储器中存储有程序代码，所述存储器、所述收发器和所述至少一个处理器通过线路通信，所述处理器运行所述代码以指令所述移动终端执行如权利要求1-5任一项所述的方法。
  24. 一种可信服务管理服务器，其特征在于，包括：存储器、收发器和至少一个处理器，所述存储器中存储有程序代码，所述存储器、所述收发器和所述至少一个处理器通过线路通信，所述处理器运行所述代码以指令所述可信服务管理服务器执行如权利要求6-11任一项所述的方法。
  25. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-5任意一项所述的方法。
  26. 一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如权利要求1-5任意一项所述的方法。
PCT/CN2017/107016 2017-10-09 2017-10-20 一种安全元件中的应用的升级方法及相关设备 WO2019071650A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201780065391.7A CN109863475A (zh) 2017-10-09 2017-10-20 一种安全元件中的应用的升级方法及相关设备

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710931301 2017-10-09
CN201710931301.X 2017-10-09

Publications (1)

Publication Number Publication Date
WO2019071650A1 true WO2019071650A1 (zh) 2019-04-18

Family

ID=66101219

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/107016 WO2019071650A1 (zh) 2017-10-09 2017-10-20 一种安全元件中的应用的升级方法及相关设备

Country Status (2)

Country Link
CN (1) CN109863475A (zh)
WO (1) WO2019071650A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111898151A (zh) * 2020-08-20 2020-11-06 捷德(中国)科技有限公司 数据传输辅助方法、系统、终端设备和存储介质
CN112381538A (zh) * 2020-11-12 2021-02-19 深圳市欢太科技有限公司 一种数据处理方法、终端设备及存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111177701B (zh) * 2019-12-11 2022-09-13 北京握奇智能科技有限公司 基于可信执行环境和安全芯片的密码功能服务实现方法和设备
CN112052023B (zh) * 2020-09-14 2024-01-26 艾体威尔电子技术(北京)有限公司 一种智能终端升级策略管理方法
CN112732288B (zh) * 2020-12-11 2024-05-28 北京握奇智能科技有限公司 一种数字货币硬件钱包应用升级的方法和装置
CN113347620B (zh) * 2021-08-05 2021-11-12 深圳市深圳通有限公司 兼容多版本应用空发卡方法、装置、设备及存储介质
CN117369854A (zh) * 2023-12-07 2024-01-09 浪潮云洲工业互联网有限公司 一种主动标识工业设备ota升级方法、设备及介质
CN117424893A (zh) * 2023-12-19 2024-01-19 深圳竹云科技股份有限公司 数据传输方法、装置、计算机设备、存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140031024A1 (en) * 2012-02-05 2014-01-30 Rfcyber Corporation Method and system for providing controllable trusted service manager
CN104717198A (zh) * 2013-12-13 2015-06-17 恩智浦有限公司 更新安全元件上的软件
CN104769554A (zh) * 2012-04-05 2015-07-08 阿苏兰特公司 用于提供移动设备支持服务的系统、方法、设备以及计算机程序产品
CN105324752A (zh) * 2013-05-21 2016-02-10 谷歌公司 用于管理服务升级的系统、方法和计算机程序产品

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101216771A (zh) * 2007-12-29 2008-07-09 宇龙计算机通信科技(深圳)有限公司 一种通过个人电脑实现手机软件升级的方法、系统及装置
CN102981811A (zh) * 2011-09-05 2013-03-20 北大方正集团有限公司 用户选项数据的处理方法和装置
US9594899B2 (en) * 2011-12-30 2017-03-14 Intel Corporation Apparatus and method for managing operation of a mobile device
CN102609281B (zh) * 2012-02-24 2016-01-27 中国电子科技集团公司第十五研究所 分布式软件补丁更新方法及系统
FR3031613B1 (fr) * 2015-01-09 2018-04-06 Ingenico Group Procede de traitement d'une transaction a partir d'un terminal de communication.
CN105760777B (zh) * 2016-02-16 2018-07-17 上海斐讯数据通信技术有限公司 一种基于智能平台的安全信息管理方法及系统
CN105843653B (zh) * 2016-04-12 2017-11-24 恒宝股份有限公司 一种安全应用配置方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140031024A1 (en) * 2012-02-05 2014-01-30 Rfcyber Corporation Method and system for providing controllable trusted service manager
CN104769554A (zh) * 2012-04-05 2015-07-08 阿苏兰特公司 用于提供移动设备支持服务的系统、方法、设备以及计算机程序产品
CN105324752A (zh) * 2013-05-21 2016-02-10 谷歌公司 用于管理服务升级的系统、方法和计算机程序产品
CN104717198A (zh) * 2013-12-13 2015-06-17 恩智浦有限公司 更新安全元件上的软件

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111898151A (zh) * 2020-08-20 2020-11-06 捷德(中国)科技有限公司 数据传输辅助方法、系统、终端设备和存储介质
CN111898151B (zh) * 2020-08-20 2024-03-29 捷德(中国)科技有限公司 数据传输辅助方法、系统、终端设备和存储介质
CN112381538A (zh) * 2020-11-12 2021-02-19 深圳市欢太科技有限公司 一种数据处理方法、终端设备及存储介质

Also Published As

Publication number Publication date
CN109863475A (zh) 2019-06-07

Similar Documents

Publication Publication Date Title
JP6262278B2 (ja) アクセス制御クライアントの記憶及び演算に関する方法及び装置
WO2019071650A1 (zh) 一种安全元件中的应用的升级方法及相关设备
US9843585B2 (en) Methods and apparatus for large scale distribution of electronic access clients
US8064598B2 (en) Apparatus, method and computer program product providing enforcement of operator lock
US11552807B2 (en) Data processing method and apparatus
CN112632573B (zh) 智能合约执行方法、装置、系统、存储介质及电子设备
TWI469655B (zh) 電子存取用戶端之大規模散佈之方法及裝置
US20230079795A1 (en) Device to device migration in a unified endpoint management system
WO2020177116A1 (zh) 仿冒app识别方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17928152

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17928152

Country of ref document: EP

Kind code of ref document: A1