WO2021147433A1 - 手机盾状态管理方法、tsm平台服务器及存储介质 - Google Patents

手机盾状态管理方法、tsm平台服务器及存储介质 Download PDF

Info

Publication number
WO2021147433A1
WO2021147433A1 PCT/CN2020/124938 CN2020124938W WO2021147433A1 WO 2021147433 A1 WO2021147433 A1 WO 2021147433A1 CN 2020124938 W CN2020124938 W CN 2020124938W WO 2021147433 A1 WO2021147433 A1 WO 2021147433A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile phone
phone shield
state
terminal device
apdu
Prior art date
Application number
PCT/CN2020/124938
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 中国银联股份有限公司
Publication of WO2021147433A1 publication Critical patent/WO2021147433A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0894—Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
    • H04L9/0897—Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage involving additional devices, e.g. trusted platform module [TPM], smartcard or USB
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H04L9/0877—Generation of secret information including derivation or calculation of cryptographic keys or passwords using additional device, e.g. trusted platform module [TPM], smartcard, USB or hardware security module [HSM]

Definitions

  • This application belongs to the field of data processing, and in particular relates to a mobile phone shield state management method, a TSM platform server and a storage medium.
  • USB shield is a tool for electronic signature and digital authentication of online banking.
  • U-Shield can write the digital certificate into the security device to ensure the security of electronic payment transactions.
  • the traditional USB-Shield cannot meet the business needs of mobile terminals.
  • the mobile terminal is used to realize the functions of the traditional USB shield, that is, the mobile shield is developed.
  • the Trusted Service Manager (TSM) platform Through the communication between the terminal device, the Trusted Service Manager (TSM) platform and the service provider server, the management of the mobile phone shield status is realized. Among them, the state of the mobile phone shield in the TSM platform and the terminal device are synchronized with each other. Specifically, the mobile phone shield status can be as shown in Table 1 below:
  • the embodiments of the present application provide a mobile phone shield state management method, system, TSM platform server, and terminal equipment, which can improve the performance of the mobile phone shield state management system.
  • an embodiment of the present application provides a mobile phone shield state management method, which is applied to a trusted service management TSM platform, and the method includes:
  • the terminal device Receives the first APDU instruction response message sent by the terminal device. If the first APDU instruction response message indicates that the tasks in the first APDU task list are executed successfully, the mobile phone shield status is recorded in the TSM platform as the second state, and the second state represents the mobile phone The shield download is complete.
  • an embodiment of the present application provides a TSM platform server, including:
  • the receiving module is used to receive the mobile phone shield application request of the terminal device
  • the sending module is used to respond to the mobile phone shield application request and send the first application protocol data unit APDU task list corresponding to the mobile phone shield application request to the terminal device;
  • the state storage module is used to record the mobile phone shield state as the first state when the sending module sends the first APDU task list, and the first state indicates that the mobile phone shield is downloading;
  • the receiving module is also used to receive the first APDU instruction request sent by the terminal device;
  • the sending module is further configured to respond to the first APDU instruction request and send the first APDU instruction corresponding to the first APDU task list to the terminal device;
  • the receiving module is also used to receive the first APDU instruction response message sent by the terminal device;
  • the status storage module is also used to record the mobile phone shield status as a second state if the first APDU instruction response message indicates that the tasks in the first APDU task list are successfully executed, and the second state represents the completion of the download of the mobile phone shield.
  • the embodiments of the present application provide a TSM platform server, including a processor, a memory, and a computer program stored in the memory and running on the processor.
  • the computer program is executed by the processor to implement the technical solution of the first aspect
  • the mobile phone shield state management method in.
  • an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the mobile phone shield state management method in the technical solution of the first aspect is implemented, or The mobile phone shield state management method in the technical solution of the second aspect is realized.
  • the embodiment of the application provides a mobile phone shield state management method, TSM platform server and storage medium.
  • the TSM platform sends the first APDU task list corresponding to the mobile phone shield application request to the terminal device, and the TSM platform records the mobile phone shield status as a representative mobile phone shield The first state in downloading.
  • the TSM platform receives the first APDU command response message indicating that all tasks in the first APDU task list are successfully executed, the TSM platform records the mobile phone shield status as the second state that represents the completion of the mobile phone shield download. Therefore, the download-related state management of the mobile phone shield can be realized through the first state and the second state. Once the mobile phone shield is downloaded and installed, the state of the mobile phone shield can be changed at least twice.
  • Figure 1 is a schematic structural diagram of an example of a mobile phone shield state management system
  • FIG. 2 is a flowchart of an embodiment of a mobile phone shield state management method applied to the TSM platform provided by this application;
  • FIG. 3 is a flowchart of another embodiment of the mobile phone shield state management method applied to the TSM platform provided by this application;
  • FIG. 5 is a flowchart of another embodiment of the mobile phone shield state management method applied to the TSM platform provided by this application;
  • FIG. 6 is a schematic diagram of an example of a mobile phone shield identifier in an embodiment of the application.
  • FIG. 7 is a schematic diagram of an example of a state machine of a mobile phone shield state in an embodiment of the application.
  • FIG. 8 is a flowchart of an embodiment of a mobile phone shield state management method applied to a terminal device provided by this application;
  • FIG. 9 is a flowchart of another embodiment of a mobile phone shield state management method applied to a terminal device provided by this application.
  • FIG. 10 is a flowchart of another embodiment of the mobile phone shield state management method applied to terminal equipment provided by this application.
  • FIG. 11 is a schematic structural diagram of an embodiment of a TSM platform server provided by this application.
  • FIG. 12 is a schematic structural diagram of another embodiment of the TSM platform server provided by this application.
  • FIG. 13 is a schematic structural diagram of an example of a terminal device to which the mobile phone shield state management method according to an embodiment of the present application can be applied;
  • FIG. 14 is a schematic diagram of the hardware structure of an embodiment of the TSM platform server provided by this application.
  • Fig. 1 is a schematic structural diagram of an example of a mobile phone shield state management system.
  • the mobile phone shield state management system may include a TSM platform server 10 and a terminal device 20.
  • the TSM platform server 10 is used to manage the mobile phone shield status.
  • One or more TSM platform servers 10 can form a TSM platform, which is not limited here.
  • the terminal device 20 may be a mobile phone, a tablet computer, etc., which is not limited herein.
  • the terminal device can request the mobile phone shield download from the TSM platform, so as to implement the mobile phone shield download of the terminal.
  • the terminal device can also request the deletion of the mobile phone shield from the TSM platform, so as to realize the deletion of the mobile phone shield of the terminal.
  • the TSM platform can change and store the mobile phone shield status in real time.
  • Fig. 2 is a flowchart of an embodiment of a mobile phone shield state management method applied to the TSM platform provided by this application. As shown in FIG. 2, the mobile phone shield state management method may include step S301 to step S305.
  • step S301 a mobile phone shield application request of the terminal device is received.
  • the mobile phone shield application request is used to apply for the mobile phone shield download.
  • the mobile phone shield application request may include the terminal device identification of the terminal device and at least a part of the mobile phone shield identification.
  • Terminal equipment identification can include International Mobile Equipment Identity (IMEI), Mobile Equipment Identifier (MEID), Secure Element Identity (SEID), that is, Near Field Communication (Near Field Communication) , NFC)
  • IMEI International Mobile Equipment Identity
  • MEID Mobile Equipment Identifier
  • SEID Secure Element Identity
  • the serial number of the module, etc. are not limited here.
  • the same terminal device may log in to different users, and different users need to download different mobile shields.
  • the mobile phone shield logo is used to identify the mobile phone shield. Different mobile phone shields have different mobile phone shield logos.
  • step S302 in response to the mobile phone shield application request, the first application protocol data unit (Application Protocol Data Unit, APDU) task list corresponding to the mobile phone shield application request is sent to the terminal device, and the mobile phone shield status is recorded in the TSM platform as The first state.
  • APDU Application Protocol Data Unit
  • the first state may indicate that the phone shield is being downloaded.
  • the TSM sends the first APDU task list corresponding to the mobile phone shield application request to the terminal device, indicating that the mobile phone shield requested by the terminal device is being downloaded.
  • the corresponding mobile phone shield state is the first state.
  • the first APDU task list may include at least one task, and the tasks in the first APDU task list are used to instruct the terminal device to download an instance of the mobile phone shield requested by the mobile phone shield application request to download. If the terminal device needs to execute the task in the first APDU task list, it needs to execute the first APDU instruction corresponding to the first APDU task list.
  • step S303 the first APDU instruction request sent by the terminal device is received.
  • the first APDU instruction request is used to instruct the terminal device to request the first APDU instruction from the TSM platform.
  • the number of first APDU command requests is not limited here. In some examples, one first APDU command request may correspond to one first APDU command.
  • step S304 in response to the first APDU instruction request, the first APDU instruction corresponding to the first APDU task list is sent to the terminal device.
  • first APDU commands There may be one or multiple first APDU commands, and the number of first APDU commands is not limited here. If the terminal device receives all the first APDU instructions corresponding to the first APDU task list, and all the first APDU instructions are executed successfully, it means that the terminal device downloads the instance of the mobile phone shield successfully.
  • step S305 the first APDU instruction response message sent by the terminal device is received. If the first APDU instruction response message indicates that all tasks in the first APDU task list are executed successfully, the mobile phone shield state is recorded as the second state in the TSM platform.
  • first APDU command response messages is not limited here.
  • a first APDU command may correspond to a first APDU command response message.
  • the first APDU instruction response message is used to indicate whether the task corresponding to the first APDU instruction in the first APDU task list is executed successfully.
  • the TSM platform determines whether the first APDU instruction is successfully executed through the first APDU instruction response message sent by the terminal device. If the first APDU instruction is executed successfully, it means that the task corresponding to the first APDU instruction in the first APDU task list has been executed successfully.
  • the TSM platform receives a first APDU instruction request sent by a terminal device, and sends a corresponding first APDU instruction to the terminal device. If the first APDU instruction request sent by the terminal device received by the TSM platform is not the first APDU instruction request sent for the first time corresponding to the first APDU task list, the TSM platform can also receive the first APDU instruction request as the first APDU instruction request is received. A first APDU command response message corresponding to a first APDU command.
  • the tasks in the first APDU task list are all executed successfully, indicating that the mobile shield download is complete.
  • the second state represents the completion of the download of the phone shield.
  • the TSM platform can determine the completion of the download of the mobile phone shield through the first APDU command response message indicating that all tasks in the first APDU task list are successfully executed.
  • the TSM platform sends the first APDU task list corresponding to the mobile phone shield application request to the terminal device, and the TSM platform records the mobile phone shield status as the first state characterizing the mobile phone shield download.
  • the TSM platform receives the first APDU command response message indicating that all tasks in the first APDU task list are successfully executed, the TSM platform records the mobile phone shield status as the second state that represents the completion of the mobile phone shield download. Therefore, the download-related state management of the mobile phone shield can be realized through the first state and the second state. Once the mobile phone shield is downloaded and installed, the state of the mobile phone shield can be changed at least twice.
  • setting up an independent TSM platform to manage the mobile phone shield status can shield service providers from differences in mobile shield management caused by different terminal equipment manufacturers and different built-in chips, and can also shield users or terminal equipment manufacturers from different service providers.
  • the difference in mobile phone shield management improves the applicability of mobile phone shield management.
  • FIG. 3 is a flowchart of another embodiment of the mobile phone shield state management method applied to the TSM platform provided by this application.
  • the difference between the mobile phone shield state management method shown in FIG. 3 and the mobile phone shield state management method shown in FIG. 2 is that the mobile phone shield state management method shown in FIG. 3 may further include steps S306 to S311.
  • step S306 a mobile phone shield deletion request sent by the server is received.
  • the server is the server of the service provider.
  • the terminal device sends a mobile phone shield deletion request to the server, and the server forwards the mobile phone shield deletion request to the TSM platform.
  • the mobile phone shield deletion request is used to request the deletion of the mobile phone shield in the terminal device.
  • the mobile phone shield deletion request may include the terminal device identifier and the mobile phone shield identifier, so as to delete the mobile phone shield corresponding to the terminal device and the user who logs in to the terminal device.
  • step S307 in response to the mobile phone shield deletion request, a delete success response message is sent to the server, and the mobile phone shield state is recorded as the third state in the TSM platform.
  • the TSM platform can send a deletion success response message to the service provider’s server if the terminal device’s mobile phone shield request to delete the mobile phone shield has not been deleted, so that the service provider’s server
  • the mobile phone shield status in is the business invalid status.
  • the service is invalid, all services related to the mobile phone shield are unavailable.
  • the above method of sending a delete success response message to the server of the service provider removes the strong dependency between the service of the service provider’s server and the instance of the mobile phone shield in the on-off device, so as to avoid the terminal device and the mobile phone requesting the deletion.
  • the service provider’s server and the terminal device-related services are blocked, and the service provider’s server can continue to execute the service until the mobile shield instance requested to be deleted in the terminal device is deleted.
  • the business situation related to terminal equipment Thereby reducing or even eliminating business waiting time and improving business processing efficiency.
  • the TSM platform needs to record the actual state of the mobile phone shield in the terminal device, and the TSM platform records the mobile phone shield status as the third state characterizing the deletion of the mobile phone shield.
  • step S308 the second APDU task list corresponding to the mobile phone shield deletion request is sent to the terminal device.
  • the second APDU task list includes at least one task, and the tasks in the second APDU task list instruct the terminal device to delete the instance of the mobile phone shield requested to be deleted by the mobile phone shield deletion request. If the terminal device needs to execute the task in the second APDU task list, it needs to execute the second APDU instruction corresponding to the second APDU task list.
  • step S309 a second APDU instruction request sent by the terminal device is received.
  • the second APDU instruction requests the user to instruct the terminal device to request the second APDU instruction from the TSM platform.
  • the data requested by the second APDU instruction is not limited here.
  • one second APDU instruction request corresponds to one second APDU instruction.
  • step S310 in response to the second APDU instruction request, a second APDU instruction corresponding to the second APDU task list is sent to the terminal device.
  • the terminal device receives all the second APDU instructions corresponding to the second APDU task list, and all the second APDU instructions are executed successfully, it means that the terminal device deletes the instance of the mobile phone shield successfully.
  • step S311 the second APDU command response message sent by the terminal device is received. If the second APDU command response message indicates that all tasks in the second APDU task list are executed successfully, the mobile phone shield status is recorded as the fourth status in the TSM platform.
  • the number of second APDU command response messages is not limited here.
  • one second APDU instruction may correspond to one second APDU instruction response message.
  • the second APDU instruction response message is used to indicate whether the task corresponding to the second APDU instruction in the second APDU task list is executed successfully.
  • the TSM platform determines whether the second APDU instruction is successfully executed through the second APDU instruction response message sent by the terminal device. If the second APDU instruction is executed successfully, it means that the task corresponding to the second APDU instruction in the second APDU task list has been executed successfully.
  • the TSM platform receives a second APDU instruction request sent by the terminal device, and sends a corresponding second APDU instruction to the terminal device. If the second APDU command request sent by the terminal device received by the TSM platform is not the first sent second APDU command request corresponding to the second APDU task list, as the second APDU command request is received, the TSM platform can also receive the second APDU command request. A second APDU command response message corresponding to a second APDU command.
  • the tasks in the second APDU task list are all executed successfully, indicating that the phone shield has been deleted.
  • the fourth state represents the completion of the deletion of the mobile phone shield.
  • the TSM platform may determine the completion of the deletion of the mobile phone shield through a second APDU instruction response message indicating that all tasks in the second APDU task list are successfully executed.
  • the TSM platform only needs to maintain the four mobile phone shield states of the first state, the second state, the third state, and the fourth state.
  • the TSM platform can meet the needs of mobile phone shield state management.
  • the number of times the mobile phone shield state changes can be reduced, and the number of operations on the database is reduced, thereby further improving the performance of the mobile phone shield state management system.
  • first state, the second state, the third state, and the fourth state in the foregoing embodiment can be specifically represented by numbers, letters, special symbols or character strings, which are not limited herein.
  • FIG. 4 is a flowchart of another embodiment of the mobile phone shield state management method applied to the TSM platform provided by this application.
  • the difference between the mobile phone shield state management method shown in FIG. 4 and the mobile phone shield state management method shown in FIG. 2 is that the mobile phone shield state management method shown in FIG. 4 may further include steps S312 to S316.
  • step S312 a data cleaning request sent by the terminal device is received.
  • the TSM platform receives the data cleanup request actively sent by the terminal device.
  • the data cleanup request is used to request the deletion of the mobile phone shield instance whose mobile phone shield state is in the intermediate state.
  • the intermediate state includes the first state or the third state.
  • step S313 in response to the data cleaning request, if there is a mobile phone shield state in the first state or the third state in the TSM platform, a third APDU task list is sent to the terminal device.
  • the third APDU task list may include at least one task, and the task in the third APDU task list indicates to delete an instance of the mobile phone shield whose state is the first state or the third state. If the terminal device needs to execute the tasks in the third APDU task list, it needs to execute the third APDU instruction corresponding to the third APDU task list.
  • the TSM platform does not need to send the third APDU task list to the terminal device.
  • step S314 the third APDU instruction request sent by the terminal device is received.
  • the third APDU instruction request is used to instruct the terminal device to request the third APDU instruction from the TSM platform.
  • the number of third APDU command requests is not limited here. In some examples, one third APDU command request may correspond to one third APDU command.
  • step S315 in response to the third APDU instruction request, a third APDU instruction corresponding to the third APDU task list is sent to the terminal device.
  • the third APDU instruction may be one, or there may be two or more, and the number of the third APDU instruction is not limited here. If the terminal device receives all the third APDU instructions corresponding to the third APDU task list, and all the third APDU instructions are executed successfully, it means that the terminal device successfully deletes the instance of the mobile phone shield with the first state or the third state.
  • step S316 the third APDU command response message sent by the terminal device is received. If the third APDU command response message indicates that the tasks in the third APDU task list are executed successfully, it will be in the first state or the third state in the TSM platform. The mobile shield status is updated to the fourth status.
  • a third APDU command may correspond to a third APDU command response message.
  • the third APDU command response message is used to indicate whether the task corresponding to the third APDU command in the third APDU task list is successfully executed.
  • the TSM platform determines whether the third APDU instruction is successfully executed through the third APDU instruction response message sent by the terminal device. If the third APDU instruction is executed successfully, it means that the task corresponding to the third APDU instruction in the third APDU task list has been executed successfully.
  • the TSM platform receives a third APDU instruction request sent by the terminal device, and sends a third APDU instruction corresponding to the third APDU instruction request to the terminal device. If the third APDU command request sent by the terminal device received by the TSM platform is not the first sent third APDU command request corresponding to the third APDU task list, then as the third APDU command request is received, the TSM platform can also receive the A third APDU command response message corresponding to a third APDU command.
  • the tasks in the third APDU task list are all executed successfully, indicating that the deletion of the mobile phone shield in the first state or the third state is completed.
  • the TSM platform may update the mobile phone shield status in the first state or the third state to the fourth state, so that the mobile phone shield state in the TSM platform is synchronized with the actual state of the mobile phone shield in the terminal device.
  • some useless mobile phone shields in the intermediate state may be generated during the download process or the deletion process.
  • a mobile phone shield in a service unavailable state in the server of the service provider may also be recorded as a mobile phone shield state that is not in the fourth state on the TSM platform.
  • the instance of the mobile phone shield in the terminal device may still exist.
  • the terminal device actively initiates the cleaning of the unavailable mobile phone shield to the TSM platform, and deletes the mobile phone shield whose mobile phone shield status is the first state or the third state, so as to realize the silent deletion of the unavailable mobile phone shield.
  • the TSM platform can notify the service provider's server through notification information. After the mobile phone shield is downloaded and installed, silently delete the unusable mobile phone shield, which can reduce the size of the data package installed by the mobile phone shield, improve the installation efficiency of the mobile phone shield, and increase the utilization of the storage space in the terminal device to avoid dirty data remaining.
  • a breakpoint retry method can be used to continue the download of the mobile phone shield.
  • the breakpoint retry method has some drawbacks.
  • the TSM platform when the download of the mobile phone shield is abnormal, the TSM platform does not receive the first APDU command response message indicating whether the task in the first APDU task list is executed successfully, that is, whether the first APDU command is executed successfully, and the TSM platform cannot determine the direction Whether the last APDU command issued by the terminal device is successfully executed.
  • the TSM platform will determine the location of the breakpoint according to the record of the first APDU command sent, and then send the last first APDU command sent to the terminal device to the terminal The device is issued.
  • the terminal device has executed the last first APDU command issued by the TSM platform, a conflict will occur when the first APDU command is executed again, and a conflict response code will be generated.
  • the conflict response codes are not uniform.
  • the TSM platform cannot handle the inconsistent conflict response code, which causes the download to fail. Even if you try again with a breakpoint and download and install the mobile phone shield, the download will still fail, and the download will be stuck and the download of the mobile phone shield cannot be completed.
  • user A For another example, in the terminal device UE1, user A’s mobile phone shield download is halfway through, for example, only the Applet installation is completed, or only half of the mobile phone shield application is completed, and the mobile shield download process is suspended due to network interruption, and user A For some reasons, I chose to temporarily give up and try again.
  • User B applies for the mobile phone shield on the terminal device UE1, the TSM platform will mistakenly determine that user A and user B are the same user, and retry with a breakpoint. In this way, the mobile phone shield of user A will be downloaded and installed to user B, resulting in leakage of sensitive information.
  • the TSM platform can generate a mobile phone shield identifier corresponding to the terminal device, and store the mapping relationship between the mobile phone shield identifier and the state of the mobile phone shield.
  • the mobile phone shield identifier is used to identify the mobile phone shield, and the state of the mobile phone shield changes as the state of the mobile phone shield changes. If the status of the mobile phone shield changes, the TSM platform will update the mapping relationship between the mobile phone shield ID and the mobile phone shield status.
  • the mobile phone shield identifier stored in the TSM platform is unique.
  • the mobile phone shield identifiers of the mobile phone shields that have a corresponding relationship with the same terminal device stored in the TSM platform are unique. Identifies the phone shield by setting a unique mobile phone shield identifier.
  • Each download of the mobile phone shield can be distinguished by a different mobile phone shield identifier, which can break out of the download stuck state and re-download and install the mobile phone shield; it can also prevent different users from downloading The same mobile phone shield, or multiple service providers corresponding to the same mobile phone shield, avoid the leakage of sensitive information.
  • the mobile phone shield application request includes the first part of the mobile phone shield identifier and the terminal device identifier.
  • FIG. 5 is a flowchart of another embodiment of the mobile phone shield state management method applied to the TSM platform provided by this application. The difference between the mobile phone shield state management method shown in FIG. 5 and the mobile phone shield state management method shown in FIG. 2 is that the mobile phone shield state management method shown in FIG. 5 may further include steps S317 to S322.
  • step S317 for each terminal device corresponding to the terminal device identifier, it is queried in the TSM platform whether there is a mobile phone shield identifier that matches the first part and the terminal device identifier.
  • the mobile phone shield logo can be composed of multiple parts and is not limited here.
  • the first part is one part of the mobile phone shield logo.
  • the first part can be the prefix of the mobile phone shield logo.
  • the mobile phone shield identifier of the mobile phone shield requested by this mobile phone shield application request is generated in the TSM platform.
  • the TSM platform stores the mobile phone shield identifier corresponding to each terminal device. In order to ensure that the generated mobile phone shield identifier is different from the mobile phone shield identifiers of other mobile phone shields in the terminal device, use the terminal device identifier and mobile phone shield identifier in this mobile phone shield application request
  • the first part of the TSM platform is to find whether there is a mobile phone shield identifier that matches the first part and the terminal device identifier.
  • step S318 if there is no mobile phone shield identifier matching the first part and the terminal device identifier in the TSM platform, the second part of the mobile phone shield identifier whose value is the initial value is generated, and based on the first part and the second part, the terminal device corresponding Mobile phone shield logo.
  • the generated second part of the mobile phone shield identifier may be an initial value. Since there is no mobile phone shield identifier matching the first part and the terminal device identifier in the TSM platform, there is no mobile phone shield identifier that is the same as the generated mobile phone shield identifier in the TSM platform.
  • the second part can be recorded in hexadecimal, and the initial value of the second part can be "00".
  • step S319 if the mobile phone shield identifier matching the first part and the terminal device identifier is stored in the TSM platform, the target mobile phone shield identifier is acquired.
  • the target mobile phone shield identifier is obtained from the mobile phone shield identifier matching the first part and the terminal device identifier of the TSM platform.
  • the target mobile phone shield identifier is a recently generated mobile phone shield identifier that matches the first part and the terminal device identifier.
  • step S320 the value of the second part of the target mobile phone shield identifier is increased by a preset step value, and a new target mobile phone shield identifier is generated based on the second part and the first part after the preset step value is increased.
  • the value of the second part of the target mobile phone shield identifier can be increased by a preset step value to Generate a new value for the second part. Based on the new second part and first part, a generative target mobile phone shield identification.
  • the preset step value can be set according to work scenarios and work requirements, and is not limited here.
  • the preset step value can be 1.
  • the value of the second part of the target mobile phone shield identification increases by 1. For example, "00" increases by 1 to get “01”, and "01” increases by 1 to get “02", which will not be illustrated here.
  • step S321 if the mobile phone shield identifier that is the same as the new target mobile phone shield identifier is stored in the TSM platform, and the mobile phone shield status corresponding to the mobile phone shield identifier is not in the fourth state, the second part of the new target mobile phone shield identifier The value of is increased by the preset step value again until there is no mobile phone shield identifier that is the same as the new target mobile phone shield identifier in the TSM platform, and the new target mobile phone shield identifier is used as the mobile phone shield identifier corresponding to the terminal device.
  • step S322 if the mobile phone shield identifier that is the same as the new target mobile phone shield identifier is stored in the TSM platform, and the mobile phone shield status corresponding to the mobile phone shield identifier is not in the fourth state, the second part of the new target mobile phone shield identifier Increase the preset step value again until the TSM platform stores the same mobile phone shield identifier as the new target mobile phone shield identifier and the mobile phone shield status corresponding to the mobile phone shield identifier is in the fourth state, and the new target mobile phone shield identifier is used as The mobile phone shield identifier corresponding to the terminal device.
  • the mobile phone shield with the mobile phone shield status of the fourth state in the TSM platform can be used. If the mobile phone shield status corresponding to the mobile phone shield identifier is changed from the fourth state to the first state, it can be reused.
  • the mobile phone shield identifier stored in the TSM for the same terminal device is always unique and will not cause The download is stuck or sensitive information is leaked.
  • the new target mobile phone shield identifier is different from the mobile phone shield identifier of the mobile phone shield whose mobile phone shield status is not the fourth state in the TSM platform, and the new target mobile phone shield identifier can be used as the mobile phone of the terminal device.
  • step S322 if the new target mobile phone shield identifier is the same as the mobile phone shield identifier of the mobile phone shield in the fourth state in the TSM platform, the mobile phone shield status corresponding to the new target mobile phone shield identifier may be recorded as the first Status, use the new target mobile phone shield ID as the mobile phone shield ID of the mobile phone shield requested by the mobile phone shield application request of the terminal device, and set the mobile phone shield status that is the same as the new target mobile phone shield ID originally stored in the TSM platform as the fourth Delete the mobile phone shield ID of the mobile phone shield in the state; or, if the new target mobile phone shield ID is the same as the mobile phone shield ID of the mobile phone shield in the fourth state in the TSM platform, you can change the mobile phone shield status in the TSM platform to the first
  • the mobile phone shield identifier of the four-state mobile phone shield is used as the new target mobile phone shield identifier, and the state of the mobile phone shield is changed from the fourth state to the first state.
  • the value of the second part of the new target mobile phone shield reaches the preset upper limit during the cycle of increasing the value of the second part by the preset step value, the value of the second part can be changed Update to the initial value, and continue the cycle of increasing the preset step value from the initial value.
  • the preset upper limit value can be set according to work scenarios and work requirements, and is not limited here. For example, if the hexadecimal system is used for counting and the preset upper limit value is "FF", after the value of the second part reaches "FF", the value of the second part is updated to "00" and can be set at "00" On the basis of, the cycle of increasing the preset step value is carried out.
  • the mobile phone shield identifier may be implemented as an application identifier (AID).
  • the AID may include a 5-byte registration identifier (ie RID) and an 11-byte extended application identifier (ie PIX).
  • RID and PIX can be defined by standards organizations.
  • some characters in the AID except RID and PIX can be used as the second part of the mobile phone shield identification in the above embodiment.
  • FIG. 6 is a schematic diagram of an example of a mobile phone shield identifier in an embodiment of the application. As shown in Figure 6, the mobile phone shield identifier includes 16 bytes.
  • the 1st to 5th bytes are the RID
  • the 6th to 8th bytes are the mobile phone shield service identification
  • the 9th byte is the service type identification
  • the 10th to 13th bytes are the service provider code
  • the 14th byte is the service provider code.
  • the second byte is the mobile phone shield type identification
  • the 15th byte is the mobile phone shield identification
  • the 16th byte is the reserved byte. If the number of mobile phone shield identifiers of the mobile phone shield that can be activated by the same user exceeds the capacity of one byte, the 15th and 16th bytes can be used as the mobile phone shield identifier, which is not limited here.
  • the TSM platform can also obtain personalized data corresponding to the user of the terminal device from the server of the service provider, which is not limited here.
  • the mobile phone shield states maintained by the TSM platform may include a first state, a second state, a third state, and a fourth state.
  • the state of the mobile phone shield maintained by the terminal device may include an instance non-existent state and an instance existing state.
  • the status of the mobile phone shield maintained by the server of the service provider may include a service invalid status and a service valid status.
  • the TSM platform maintains four states, the terminal device maintains two states, and the service provider's server maintains two states, so that the mobile phone shield state can be managed in the entire mobile phone shield state management system.
  • the following will illustrate the relationship between the mobile phone shield state maintained by the TSM platform, the mobile phone shield state maintained by the terminal device, and the mobile phone shield state maintained by the server of the service provider.
  • the TMS platform sends the first APDU task list to the terminal device, if the terminal device has performed the mobile phone shield download task, but the mobile phone shield download fails, correspondingly, the mobile phone shield status maintained by the TSM platform is the first state, and the terminal device The status of the mobile phone shield maintained is the instance non-existent state, and the status of the mobile phone shield maintained by the server of the service provider is the business invalid state.
  • the TMS platform sends the first APDU task list to the terminal device, if the terminal device has performed the mobile phone shield download task, and the mobile phone shield download is successful, correspondingly, the mobile phone shield status maintained by the TSM platform is the first state, and the terminal device
  • the maintained state of the mobile phone shield is the instance existence state, and the mobile phone shield state maintained by the server of the service provider is the business invalid state.
  • the TMS platform receives the first APDU instruction response message indicating that the tasks in the first APDU task list are successfully executed, if the status synchronization between the TSM platform and the service provider’s server is successful, the TSM platform maintains accordingly
  • the mobile phone shield status of is the second state
  • the mobile phone shield status maintained by the terminal device is the instance existence status
  • the mobile phone shield status maintained by the server of the service provider is the service valid status.
  • the TMS platform receives the first APDU command response message indicating that the tasks in the first APDU task list are successfully executed, if the synchronization of the mobile phone shield status between the TSM platform and the service provider’s server fails, accordingly, the TSM
  • the mobile phone shield state maintained by the platform is the second state
  • the mobile phone shield state maintained by the terminal device is the instance existing state
  • the mobile phone shield state maintained by the server of the service provider is the business invalid state.
  • the TSM platform responds to the mobile phone shield deletion request, if the terminal device has not executed the mobile phone shield deletion task, correspondingly, the mobile phone shield status maintained by the TSM platform is the third state, and the mobile phone shield status maintained by the terminal device is the instance existing state. , The mobile phone shield status maintained by the server of the service provider is the business invalid status.
  • the TSM platform responds to the mobile phone shield deletion request, if the terminal device fails to perform the task of deleting the mobile phone shield, correspondingly, the mobile phone shield state maintained by the TSM platform is the third state, and the mobile phone shield state maintained by the terminal device is the instance existing state.
  • the mobile phone shield status maintained by the server of the service provider is a business invalid status.
  • the terminal device successfully executes the mobile phone shield deletion task, but the synchronization of the mobile phone shield status between the terminal device and the TSM platform fails, correspondingly, the mobile phone shield status maintained by the TSM platform is the third state, and the mobile phone shield status maintained by the terminal device is an example If there is no state, the mobile phone shield state maintained by the server of the service provider is the business invalid state.
  • the terminal device performs the task of deleting the mobile phone shield successfully, and the mobile phone shield status between the terminal device and the TSM platform is successfully synchronized, correspondingly, the mobile phone shield status maintained by the TSM platform is the fourth state, and the mobile phone shield status maintained by the terminal device is an example If there is no state, the mobile phone shield state maintained by the server of the service provider is the business invalid state.
  • FIG. 7 is a schematic diagram of an example of a state machine of a mobile phone shield state in an embodiment of the application.
  • the TSM platform receives the mobile phone shield application request sent by the terminal device, and the mobile phone shield state maintained by the TSM platform enters the first state 00. If the mobile phone shield is downloaded successfully, the state of the mobile phone shield maintained by the TSM platform is changed from the first state 00 to the second state 01.
  • the mobile phone shield state maintained by the TSM platform is changed from the first state 00 to the third state 02. If the mobile phone shield status is the second state 01, and the TSM platform receives the mobile phone shield deletion request, the mobile phone shield state maintained by the TSM platform is changed from the second state 01 to the third state 02. If the mobile phone shield status is the third state 02, the TSM platform determines that the mobile phone shield has been deleted successfully, and the mobile phone shield state maintained by the TSM platform changes from the third state 02 to the fourth state 03.
  • the TSM platform receives the data cleaning request and deletes the mobile phone shield whose mobile phone shield status is the first state 00, the mobile phone shield state of the mobile phone shield is changed from the first state 00 to the fourth state 03. If the mobile phone shield identifier generated by the TSM platform is the same as the mobile phone shield identifier of the mobile phone shield whose mobile phone shield status is the fourth state 03 in the TSM platform, the mobile phone shield status corresponding to the generated mobile phone shield identifier is changed from the fourth state 03 to the first State 00.
  • FIG. 8 is a flowchart of an embodiment of a mobile phone shield state management method applied to a terminal device provided by this application. As shown in Fig. 8, the mobile phone shield state management method may include step S401 to step S407.
  • step S401 the mobile phone shield control sends a mobile phone shield application request to the TSM platform.
  • step S402 the mobile phone shield control receives the first APDU task list corresponding to the mobile phone shield application request sent by the TSM platform.
  • the tasks in the first APDU task list are used to instruct the secure element to download an instance of the mobile phone shield.
  • the mobile phone shield status of the mobile phone shield corresponding to the mobile phone shield application request in the terminal device is the instance non-existent state.
  • step S403 the mobile phone shield control sends a first APDU instruction request corresponding to the first APDU task list to the TSM platform.
  • step S404 the mobile phone shield control receives the first APDU instruction corresponding to the first APDU task list sent by the TSM platform.
  • step S405 the mobile phone shield control forwards the first APDU instruction to the secure element.
  • step S406 the secure element executes the tasks in the first APDU task list according to the first APDU instruction, and generates a first APDU instruction response message and transmits it to the mobile phone shield control.
  • the secure element executes the tasks in the first APDU task list, downloads and stores an instance of the mobile phone shield.
  • the first APDU instruction response message indicates whether the task in the first APDU task list is executed successfully, that is, it indicates whether the first APDU instruction is executed successfully.
  • the mobile phone shield status of the mobile phone shield corresponding to the mobile phone shield application request in the terminal device is the instance existing state.
  • step S407 the mobile phone shield control sends a first APDU instruction response message to the TSM platform.
  • the first APDU task list, the first APDU instruction request, the first APDU instruction, the first APDU instruction response message, the instance existence status and the instance nonexistence status please refer to the relevant description in the above embodiment. I won't repeat them here.
  • the terminal device and the TSM platform use the first APDU instruction and the first APDU instruction response message to interact to generate or update the mobile phone shield status maintained in the TSM platform, and generate or update it in the terminal device
  • the state of the mobile phone shield maintained in the terminal device The state of the mobile phone shield maintained in the terminal device.
  • the management of the download-related state of the mobile phone shield can be realized through the first state and the second state.
  • One download and installation of the mobile phone shield the number of changes in the state of the mobile phone shield is less than that of related technologies.
  • FIG. 9 is a flowchart of another embodiment of a mobile phone shield state management method applied to a terminal device provided by this application.
  • an application program is also installed in the terminal device, and the application program may specifically be an application program of the service provider.
  • the difference between the mobile phone shield state management method shown in FIG. 9 and the mobile phone shield state management method shown in FIG. 8 is that the mobile phone shield state management method shown in FIG. 9 may further include steps S408 to S415.
  • step S408 the application sends a mobile phone shield deletion request to the server, so that the server forwards the mobile phone shield deletion request to the TSM platform.
  • the mobile phone shield deletion request includes the terminal device identifier and the mobile phone shield identifier.
  • step S409 the application program receives the mobile phone shield deletion response message sent by the server.
  • the mobile phone shield deletion response message is sent by the TSM platform to the server to indicate that the mobile phone shield is successfully deleted.
  • the server here refers to the server of the service provider.
  • the application program receives the mobile phone shield deletion response message sent by the server to make the application program consistent with the mobile phone shield status in the server of the service provider.
  • step S410 the mobile phone shield control receives the second APDU task list corresponding to the TSM platform and the mobile phone shield delete request.
  • the tasks in the second APDU task list are used to instruct the secure element to delete the instance of the mobile phone shield, specifically instructing to delete the instance of the mobile phone shield corresponding to the mobile phone shield deletion request.
  • the mobile phone shield identifier of the mobile phone shield corresponding to the mobile phone shield deletion request in the terminal device is in the instance existence state.
  • step S411 the mobile phone shield control sends a second APDU instruction request corresponding to the second APDU task list to the TSM platform.
  • step S412 the mobile phone shield control receives the second APDU instruction corresponding to the second APDU task list sent by the TSM platform.
  • step S413 the mobile phone shield control forwards the second APDU instruction to the secure element.
  • step S414 the secure element executes the tasks in the second APDU task list according to the second APDU instruction, and generates a second APDU instruction response message and transmits it to the mobile phone shield control.
  • the mobile phone shield identifier of the mobile phone shield corresponding to the mobile phone shield deletion request in the terminal device is in the instance non-existent state.
  • step S415 the mobile phone shield control sends a second APDU instruction response message to the TSM platform.
  • FIG. 10 is a flowchart of another embodiment of a mobile phone shield state management method applied to a terminal device provided by this application.
  • step S416 after the secure element successfully executes the tasks in the first APDU task list, the mobile phone shield control sends a data cleanup request to the TSM platform.
  • step S417 the mobile phone shield control receives the third APDU task list sent by the TSM platform.
  • the tasks in the third APDU task list are used to instruct the secure element to delete the instance of the mobile phone shield.
  • the mobile phone shield status of the mobile phone shield corresponding to the data cleaning request in the terminal device is the instance existing state.
  • step S4108 the mobile phone shield control sends a third APDU instruction request corresponding to the third APDU task list to the TSM platform.
  • step S419 the mobile phone shield control receives the third APDU instruction corresponding to the third APDU task list sent by the TSM platform.
  • step S420 the mobile phone shield control forwards the third APDU instruction to the secure element.
  • step S421 the secure element executes the tasks in the third APDU task list according to the third APDU instruction, reserves the Applet, and generates a third APDU instruction response message and transmits it to the mobile phone shield control.
  • the mobile phone shield status of the mobile phone shield corresponding to the data cleaning request in the terminal device is the instance non-existent state.
  • the terminal device will automatically delete the Applet in the secure element. If you download the phone shield again, you need to download the Applet again.
  • the secure element executes the tasks in the third APDU task list according to the third APDU instruction, silently deletes the instances of the mobile phone shield in the first state and/or the third state, but keeps the Applet. Delete, thereby avoiding frequent deletion and downloading of Applets, thereby avoiding network data packet transmission resources occupied by frequent deletion and downloading of Applets, reducing the size of network transmission data packets, shortening processing time, improving processing efficiency, and saving terminal equipment Resources and network resources.
  • step S422 the mobile phone shield control sends a third APDU instruction response message to the TSM platform.
  • third APDU task list For the contents of the above data cleanup request, third APDU task list, third APDU instruction request, third APDU instruction, third APDU instruction response message, instance existence state and instance non-existence state, please refer to the relevant description in the above embodiment. This will not be repeated here.
  • FIG. 11 is a schematic structural diagram of an embodiment of a TSM platform server provided by this application.
  • the TSM platform server 500 may include a receiving module 501, a sending module 502, and a status storage module 503.
  • the receiving module 501 is configured to receive a mobile phone shield application request from a terminal device.
  • the sending module 502 is configured to respond to the mobile phone shield application request and send the first application protocol data unit APDU task list corresponding to the mobile phone shield application request to the terminal device.
  • the status storage module 503 is configured to record the mobile phone shield status as the first status when the sending module sends the first APDU task list.
  • the first state indicates that the mobile phone shield is being downloaded.
  • the receiving module 501 is also configured to receive the first APDU instruction request sent by the terminal device.
  • the sending module 502 is further configured to respond to the first APDU instruction request and send the first APDU instruction corresponding to the first APDU task list to the terminal device.
  • the receiving module 501 is further configured to receive the first APDU instruction response message sent by the terminal device;
  • the state storage module 503 is also used to record the mobile phone shield state as a second state if the first APDU instruction response message indicates that the tasks in the first APDU task list are executed successfully.
  • the second state represents the completion of the download of the mobile phone shield.
  • the TSM platform server sends the first APDU task list corresponding to the mobile phone shield application request to the terminal device, and the TSM platform server records the mobile phone shield status as the first state in the download of the mobile phone shield.
  • the TSM platform server receives the first APDU command response message indicating that all tasks in the first APDU task list are successfully executed, the TSM platform server records the mobile phone shield status as the second state that indicates the completion of the mobile phone shield download. Therefore, the download-related state management of the mobile phone shield can be realized through the first state and the second state. Once the mobile phone shield is downloaded and installed, the state of the mobile phone shield can be changed at least twice.
  • setting up an independent TSM platform server to manage the mobile phone shield status can shield service providers from differences in mobile shield management caused by different terminal equipment manufacturers and different built-in chips, and can also shield users or terminal equipment manufacturers from different service providers.
  • the difference in the management of mobile phone shields improves the applicability of mobile phone shield management.
  • the above-mentioned receiving module 501 is further configured to receive the mobile phone shield deletion request sent by the server, and receive the second APDU instruction request sent by the terminal device, and receive the second APDU instruction response message sent by the terminal device.
  • the sending module 502 is also used to respond to the mobile phone shield delete request, send a delete success response message to the server, and send the second APDU task list corresponding to the mobile phone shield delete request to the terminal device, and respond to the second APDU command request to the terminal
  • the device sends a second APDU instruction corresponding to the second APDU task list.
  • the state storage module 503 is also used to record the state of the mobile phone shield as the third state when the sending module 502 responds to the mobile phone shield delete request and sends a delete success response message to the server, and if the second APDU command response message indicates the second APDU task The tasks in the list are all executed successfully, and the mobile phone shield status is recorded as the fourth status.
  • the third state indicates that the phone shield is being deleted.
  • the fourth state represents the completion of the deletion of the mobile phone shield.
  • the mobile phone shield deletion request may include the terminal device identifier and the mobile phone shield identifier.
  • the above-mentioned receiving module 501 is further configured to receive a data cleanup request sent by the terminal device, and receive a third APDU instruction request sent by the terminal device, and receive a third APDU instruction response message sent by the terminal device.
  • the above-mentioned sending module 502 is also used to respond to the data cleaning request. If there is a mobile phone shield status in the first state or the third state in the TSM platform, send the third APDU task list to the terminal device, and, in response to the third APDU command request, send the third APDU task list to the terminal device The terminal device sends a third APDU instruction corresponding to the third APDU task list.
  • the task in the third APDU task list indicates to delete the instance of the mobile phone shield whose state is the first state or the third state.
  • the above-mentioned state storage module 503 is further configured to update the mobile phone shield state in the first state or the third state to the fourth state in the TSM platform if the third APDU command response message indicates that the tasks in the third APDU task list are executed successfully.
  • FIG. 12 is a schematic structural diagram of another embodiment of the TSM platform server provided by this application.
  • the difference between the TSM platform server shown in FIG. 12 and the TSM platform server shown in FIG. 11 is that the TSM platform server shown in FIG. 12 may further include an identification generation module 504 and a mapping storage module 505.
  • the identification generating module 504 is used to generate a mobile phone shield identification corresponding to the terminal device.
  • the mapping storage module 505 is used to store the mapping relationship between the mobile phone shield identifier and the mobile phone shield state.
  • the mobile phone shield identifier is unique.
  • the mobile phone shield application request may include the first part of the mobile phone shield identifier and the terminal device identifier.
  • the identification generation module 504 can be specifically used to: for each terminal device corresponding to the terminal device identification, query in the TSM platform whether there is a mobile phone shield identification that matches the first part and the terminal device identification; if there is no mobile phone shield identification that matches the first part and the first part in the TSM platform
  • the mobile phone shield identifier matched by the terminal device identifier generates the second part of the mobile phone shield identifier whose value is the initial value, and the mobile phone shield identifier corresponding to the terminal device is generated based on the first part and the second part.
  • the identification generation module 504 can also be specifically used to: if a mobile phone shield identifier matching the first part and the terminal device identifier is stored in the TSM platform, to obtain the target mobile phone shield identifier, the target mobile phone shield identifier is the most recently generated one that matches the first part and the terminal device.
  • Identify the matching mobile phone shield identifier increase the value of the second part of the target mobile phone shield identifier by a preset step value, and generate a new target mobile phone shield identifier based on the second part and the first part after the preset step value is increased; if The TSM platform stores the same mobile phone shield identifier as the new target mobile phone shield identifier, and the state of the mobile phone shield corresponding to the mobile phone shield identifier is not in the fourth state, so the second part of the new target mobile phone shield identifier is added to the preset value again Step value, until there is no mobile phone shield identifier that is the same as the new target mobile phone shield identifier in the TSM platform, and the new target mobile phone shield identifier is used as the mobile phone shield identifier corresponding to the terminal device, or if the new target mobile phone shield identifier is stored in the TSM platform
  • the mobile phone shield identifier is the same mobile phone shield identifier, and the mobile phone shield status corresponding to the mobile phone shield identifier is not
  • the fourth state indicates that the deletion of the mobile phone shield is completed.
  • the identification generation module 504 may also be specifically configured to: if the value of the second part of the new target mobile phone shield identification reaches the preset upper limit value, update the value of the second part to the initial value.
  • Fig. 13 is a schematic structural diagram of an example of a terminal device to which the mobile phone shield state management method according to an embodiment of the present application can be applied.
  • the terminal device 600 may include a sending module 601, a receiving module 602, a processing module 603, and a state storage module 604.
  • the sending module 601 is used to send a mobile phone shield application request to the trusted service management TSM platform server.
  • the receiving module 602 is configured to receive the first application protocol data unit APDU task list corresponding to the mobile phone shield application request sent by the TSM platform server.
  • the tasks in the first APDU task list are used to instruct the secure element to download the instance of the mobile phone shield.
  • the mobile phone shield status of the mobile phone shield corresponding to the mobile phone shield application request in the terminal device is the instance non-existent state.
  • the sending module 601 is further configured to send the first APDU instruction request corresponding to the first APDU task list to the TSM platform server.
  • the receiving module 602 is further configured to receive the first APDU instruction corresponding to the first APDU task list sent by the TSM platform server.
  • the processing module 603 is configured to execute the tasks in the first APDU task list according to the first APDU instruction, and generate a first APDU instruction response message to transmit to the mobile phone shield control.
  • the mobile phone shield status of the mobile phone shield corresponding to the mobile phone shield application request in the terminal device is the instance existing state.
  • the sending module 601 is further configured to send the first APDU instruction response message to the TSM platform server.
  • the state storage module 604 is used to store the state of the mobile phone shield.
  • the terminal device and the TSM platform server use the first APDU instruction and the first APDU instruction response message to interact to generate or update the mobile phone shield status maintained in the TSM platform server, and generate it in the terminal device Or update the mobile phone shield status maintained in the terminal device.
  • the management of the download-related state of the mobile phone shield can be realized through the first state and the second state.
  • One download and installation of the mobile phone shield the number of changes in the state of the mobile phone shield is less than that of related technologies.
  • the sending module 601 is also used to send a mobile phone shield deletion request to the server, so that the server forwards the mobile phone shield deletion request to the TSM platform server.
  • the receiving module 602 is also configured to receive a mobile phone shield deletion response message sent by the server.
  • the mobile phone shield deletion response message is sent to the server by the TSM platform server to indicate that the mobile phone shield is successfully deleted.
  • the receiving module 602 is further configured to receive the second APDU task list corresponding to the mobile phone shield deletion request, and to receive the second APDU instruction corresponding to the second APDU task list sent by the TSM platform server.
  • the tasks in the second APDU task list are used to instruct the secure element to delete the instance of the mobile phone shield.
  • the mobile phone shield identifier of the mobile phone shield corresponding to the mobile phone shield deletion request in the state storage module 604 is an instance existing state.
  • the sending module 601 is further configured to send a second APDU instruction request corresponding to the second APDU task list to the TSM platform server, and send a second APDU instruction response message to the TSM platform server.
  • the processing module 603 is further configured to execute the tasks in the second APDU task list according to the second APDU instruction, and generate a second APDU instruction response message.
  • the mobile phone shield identifier of the mobile phone shield corresponding to the mobile phone shield deletion request in the state storage module 604 is in the instance non-existent state.
  • the mobile phone shield deletion request includes the terminal device identifier and the mobile phone shield identifier.
  • the sending module 601 is further configured to send a data cleanup request to the TSM platform server after the processing module 603 successfully executes the tasks in the first APDU task list, and send to the TSM platform server a data cleaning request corresponding to the third APDU task list And send a third APDU instruction response message to the TSM platform server.
  • the receiving module 602 is further configured to receive the third APDU task list sent by the TSM platform server, and receive the third APDU instruction corresponding to the third APDU task list sent by the TSM platform server.
  • the task in the third APDU task list is used to instruct the secure element to delete the instance of the mobile phone shield.
  • the mobile phone shield state of the mobile phone shield corresponding to the data cleaning request in the state storage module 604 is the instance existing state.
  • the processing module 603 is further configured to execute the tasks in the third APDU task list according to the third APDU instruction, reserve the Applet, and generate a third APDU instruction response message.
  • the mobile phone shield status of the mobile phone shield corresponding to the data cleaning request in the state storage module 604 is the instance non-existent state.
  • FIG. 14 is a schematic diagram of the hardware structure of an embodiment of the TSM platform server provided by this application.
  • the TSM platform server 700 includes a memory 701, a processor 702, and a computer program stored on the memory 701 and running on the processor 702.
  • the aforementioned processor 702 may include a central processing unit (Central Processing Unit, CPU), or a specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more of the embodiments of the present application integrated circuit.
  • CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • the memory 701 may include a large-capacity memory for data or instructions.
  • the memory 701 may include a hard disk drive (Hard Disk Drive, HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a Universal Serial Bus (USB) drive, or two or more Multiple combinations of these.
  • the storage 701 may include removable or non-removable (or fixed) media.
  • the memory 701 may be inside or outside the integrated gateway disaster recovery device.
  • the memory 701 is a non-volatile solid-state memory.
  • the memory 701 includes a read-only memory (Read-Only Memory, ROM).
  • the ROM can be mask-programmed ROM, programmable ROM (Programmable Read-Only Memory, PROM), erasable PROM (Erasable Programmable Read-Only Memory, EPROM), and electrically erasable PROM ( Electrically Erasable Programmable Read-Only Memory, EEPROM), Electrically Alterable Read-Only Memory (EAROM), or flash memory, or a combination of two or more of these.
  • PROM Programmable ROM
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • EAROM Electrically Alterable Read-Only Memory
  • flash memory or a combination of two or more of these.
  • the processor 702 reads the executable program code stored in the memory 701 to run a computer program corresponding to the executable program code, so as to implement any embodiment of the mobile phone shield state management method applied to the TSM platform.
  • the TSM platform server 700 may further include a communication interface 703 and a bus 704. Wherein, as shown in FIG. 14, the memory 701, the processor 702, and the communication interface 703 are connected through a bus 704 and complete mutual communication.
  • the communication interface 703 is mainly used to implement communication between various modules, devices, units, and/or devices in the embodiments of the present application.
  • the input device and/or output device can also be accessed through the communication interface 703.
  • the bus 704 includes hardware, software, or both, and couples the components of the device together.
  • the bus may include Accelerated Graphics Port (AGP) or other graphics buses, Enhanced Industry Standard Architecture (EISA) bus, Front Side Bus (FSB), Ultra HyperTransport (HT) interconnection, Industrial Standard Architecture (ISA) bus, unlimited bandwidth interconnection, Low pin count (LPC) bus, memory bus, Micro Channel Architecture (Micro Channel Architecture) , MCA) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express (PCI-X) bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standard Association (Video) Electronics Standards Association Local Bus (VLB) bus or other suitable bus or a combination of two or more of these.
  • the bus 704 may include one or more buses.
  • the embodiment of the present application also provides a terminal device, and the hardware structure of the terminal device is basically the same as the structure shown in the schematic diagram of the hardware structure of the TSM platform server in the foregoing embodiment.
  • the processor of the terminal device runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory of the terminal device, so as to implement any of the aforementioned methods for managing the mobile phone shield state applied to the terminal device.
  • the hardware structure of the terminal device will not be repeated here.
  • An embodiment of the present application also provides a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, it can implement any of the aforementioned mobile phone shield state management methods applied to the TSM platform.
  • An embodiment alternatively, implement any embodiment of the above-mentioned mobile phone shield state management method applied to a terminal device.
  • An example of the computer-readable storage medium may be a non-transitory computer-readable storage medium, including ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc.
  • Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic array. It can also be understood that each block in the block diagram and/or flowchart and the combination of the blocks in the block diagram and/or flowchart can also be implemented by dedicated hardware that performs the specified function or action, or can be implemented by dedicated hardware and A combination of computer instructions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请提供了一种手机盾状态管理方法、TSM平台服务器及存储介质，涉及数据处理领域。该方法包括：接收终端设备的手机盾申请请求；响应手机盾申请请求，向终端设备发送与手机盾申请请求对应的第一应用协议数据单元APDU任务列表，并在TSM平台内将手机盾状态记录为第一状态，第一状态表征手机盾下载中；接收终端设备发送的第一APDU指令请求；响应第一APDU指令请求，向终端设备发送与第一APDU任务列表对应的第一APDU指令；接收终端设备发送的第一APDU指令响应消息，若第一APDU指令响应消息指示第一APDU任务列表中任务均执行成功，在TSM平台内将手机盾状态记录为第二状态，第二状态表征手机盾下载完成。根据本申请能够提高手机盾状态管理系统的性能。

Description

手机盾状态管理方法、TSM平台服务器及存储介质
相关申请的交叉引用
本申请要求享有于2020年1月20日提交的名称为“手机盾状态管理方法、TSM平台服务器及存储介质”的中国专利申请202010065933.4的优先权，该申请的全部内容通过引用并入本文中。
技术领域
本申请属于数据处理领域，尤其涉及一种手机盾状态管理方法、TSM平台服务器及存储介质。
背景技术
U盾是用于网上银行电子签名和数字认证的工具。U盾可将数字证书写入安全设备内，从而保证电子支付交易的安全。但传统的U盾无法满足移动终端的业务需求。为了满足移动终端对电子支付交易的安全要求，利用移动终端实现传统U盾的功能，即开发得到了手机盾。
通过终端设备、可信服务管理(Trusted Service Manager，TSM)平台和服务提供方服务器之间的通信，实现手机盾状态的管理。其中，TSM平台与终端设备中的手机盾状态相互同步。具体地，手机盾状态可如下方表一所示：
表一
Figure PCTCN2020124938-appb-000001
如表一所示，手机盾状态共有十二个。一次手机盾的安装，会产生多 次手机盾状态变化，例如，至少会产生六次手机盾状态变化。每次手机盾状态变化均需写入手机盾状态管理系统中的数据库，增加了对数据库的操作次数，从而对手机盾状态管理系统的性能造成不良影响。
发明内容
本申请实施例提供了一种手机盾状态管理方法、系统、TSM平台服务器及终端设备，能够提高手机盾状态管理系统的性能。
第一方面，本申请实施例提供一种手机盾状态管理方法，应用于可信服务管理TSM平台，该方法包括：
接收终端设备的手机盾申请请求；
响应手机盾申请请求，向终端设备发送与手机盾申请请求对应的第一应用协议数据单元APDU任务列表，并在TSM平台内将手机盾状态记录为第一状态，第一状态表征手机盾下载中；
接收终端设备发送的第一APDU指令请求；
响应第一APDU指令请求，向终端设备发送与第一APDU任务列表对应的第一APDU指令；
接收终端设备发送的第一APDU指令响应消息，若第一APDU指令响应消息指示第一APDU任务列表中任务均执行成功，在TSM平台内将手机盾状态记录为第二状态，第二状态表征手机盾下载完成。
第二方面，本申请实施例提供一种TSM平台服务器，包括：
接收模块，用于接收终端设备的手机盾申请请求；
发送模块，用于响应手机盾申请请求，向终端设备发送与手机盾申请请求对应的第一应用协议数据单元APDU任务列表；
状态存储模块，用于在发送模块发送第一APDU任务列表时，将手机盾状态记录为第一状态，第一状态表征手机盾下载中；
接收模块，还用于接收终端设备发送的第一APDU指令请求；
发送模块，还用于响应第一APDU指令请求，向终端设备发送与第一APDU任务列表对应的第一APDU指令；
接收模块还用于接收终端设备发送的第一APDU指令响应消息；
状态存储模块，还用于若第一APDU指令响应消息指示第一APDU任务列表中任务均执行成功，将手机盾状态记录为第二状态，第二状态表征手机盾下载完成。
第三方面，本申请实施例提供一种TSM平台服务器，包括处理器、存储器及存储在存储器上并可在处理器上运行的计算机程序，计算机程序被处理器执行时实现第一方面的技术方案中的手机盾状态管理方法。
第四方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质上存储计算机程序，计算机程序被处理器执行时实现第一方面的技术方案中的手机盾状态管理方法，或者实现第二方面的技术方案中的手机盾状态管理方法。
本申请实施例提供一种手机盾状态管理方法、TSM平台服务器及存储介质，TSM平台向终端设备发送与手机盾申请请求对应的第一APDU任务列表，TSM平台将手机盾状态记录为表征手机盾下载中的第一状态。在TSM平台接收到指示第一APDU任务列表中任务均执行成功的第一APDU指令响应消息的情况下，TSM平台将手机盾状态记录为表征手机盾下载完成的第二状态。从而通过第一状态和第二状态即可实现对手机盾与下载有关的状态的管理。一次手机盾的下载安装，最少可只产生两次手机盾状态的变化。由于每次手机盾状态变化需写入手机盾状态管理系统中的数据库，因此减少了对数据库的操作次数，降低甚至避免了对手机盾状态管理系统的性能的不良影响，从而提高手机盾状态管理系统的性能。
附图说明
从下面结合附图对本申请的具体实施方式的描述中可以更好地理解本申请。其中，相同或相似的附图标记表示相同或相似的特征。
图1为手机盾状态管理系统的示例的结构示意图；
图2为本申请提供的应用于TSM平台的手机盾状态管理方法的实施例的流程图；
图3为本申请提供的应用于TSM平台的手机盾状态管理方法的另一实施例的流程图；
图4为本申请提供的应用于TSM平台的手机盾状态管理方法的又一实施例的流程图；
图5为本申请提供的应用于TSM平台的手机盾状态管理方法的再一实施例的流程图；
图6为本申请实施例中的手机盾标识的示例的示意图；
图7为本申请实施例中的手机盾状态的状态机的示例的示意图；
图8为本申请提供的应用于终端设备的手机盾状态管理方法的实施例的流程图；
图9为本申请提供的应用于终端设备的手机盾状态管理方法的另一实施例的流程图；
图10为本申请提供的应用于终端设备的手机盾状态管理方法的又一实施例的流程图；
图11为本申请提供的TSM平台服务器的实施例的结构示意图；
图12为本申请提供的TSM平台服务器的另一实施例的结构示意图；
图13为可应用本申请实施例的手机盾状态管理方法的终端设备的示例的结构示意图；
图14为本申请提供的TSM平台服务器的实施例的硬件结构示意图。
具体实施方式
下面将详细描述本申请的各个方面的特征和示例性实施例。在下面的详细描述中，提出了许多具体细节，以便提供对本申请的全面理解。但是，对于本领域技术人员来说很明显的是，本申请可以在不需要这些具体细节中的一些细节的情况下实施。下面对实施例的描述仅仅是为了通过示出本申请的示例来提供对本申请的更好的理解。本申请决不限于下面所提出的任何具体配置和算法，而是在不脱离本申请的构思的前提下覆盖了元素、部件和算法的任何修改、替换和改进。在附图和下面的描述中，没有示出公知的结构和技术，以便避免对本申请造成不必要的模糊。
本申请实施例提供一种手机盾状态管理方法、TSM平台服务器及存储介质，可应用于可信服务管理(Trusted Service Manager，TSM)平台、终 端设备和服务提供方服务器之间对手机盾状态的管理的场景中。例如，图1为手机盾状态管理系统的示例的结构示意图。该手机盾状态管理系统可包括TSM平台服务器10和终端设备20。TSM平台服务器10用于管理手机盾状态，一台或多台TSM平台服务器10可组成TSM平台，在此并不限定。终端设备20可为手机、平板电脑等，在此并不限定。其中，终端设备可向TSM平台请求手机盾下载，从而实现终端的手机盾下载。终端设备也可向TSM平台请求手机盾删除，从而实现终端的手机盾删除。在手机盾下载或删除的情况下，TSM平台可实时更改并存储手机盾状态。
本申请实施例提供一种手机盾状态管理方法，该手机盾状态管理方法应用于TSM平台。图2为本申请提供的应用于TSM平台的手机盾状态管理方法的实施例的流程图。如图2所示，该手机盾状态管理方法可包括步骤S301至步骤S305。
在步骤S301中，接收终端设备的手机盾申请请求。
该手机盾申请请求用于申请手机盾下载。在一些示例中，手机盾申请请求可包括终端设备的终端设备标识以及手机盾标识的至少一部分。终端设备标识可包括国际移动设备识别码(International Mobile Equipment Identity，IMEI)、移动设备识别码(Mobile Equipment Identifier，MEID)、安全元件识别码(Secure Element Identity，SEID)即近场通信(Near Field Communication，NFC)模块的序列号等，在此并不限定。同一终端设备可能登陆有不同用户，不同用户需要下载不同的手机盾。手机盾标识用于标识手机盾，不同手机盾的手机盾标识不同。
在步骤S302中，响应手机盾申请请求，向终端设备发送与手机盾申请请求对应的第一应用协议数据单元(Application Protocol Data Unit，APDU)任务列表，并在TSM平台内将手机盾状态记录为第一状态。
第一状态可表征手机盾下载中。TSM向终端设备发送与手机盾申请请求对应的第一APDU任务列表，表示该终端设备申请的手机盾下载中。终端设备申请的手机盾未下载成功前，对应的手机盾状态为第一状态。
第一APDU任务列表中可包括至少一个任务，第一APDU任务列表中的任务用于指示终端设备下载手机盾申请请求请求下载的手机盾的实例。 终端设备若需要执行第一APDU任务列表中的任务，则需要执行与第一APDU任务列表对应的第一APDU指令。
在步骤S303中，接收终端设备发送的第一APDU指令请求。
第一APDU指令请求用于指示终端设备向TSM平台请求第一APDU指令。在此并不限定第一APDU指令请求的数目，在一些示例中，一个第一APDU指令请求可对应一条第一APDU指令。
在步骤S304中，响应第一APDU指令请求，向终端设备发送与第一APDU任务列表对应的第一APDU指令。
第一APDU指令可能为一条，也可能为多条，在此并不限定第一APDU指令的数目。若终端设备接收到与第一APDU任务列表对应的所有第一APDU指令，且所有第一APDU指令执行成功，表示终端设备下载手机盾的实例成功。
在步骤S305中，接收终端设备发送的第一APDU指令响应消息，若第一APDU指令响应消息指示第一APDU任务列表中任务均执行成功，在TSM平台内将手机盾状态记录为第二状态。
在此并不限定第一APDU指令响应消息的数目。在一些示例中，一条第一APDU指令可对应一条第一APDU指令响应消息。第一APDU指令响应消息用于指示第一APDU任务列表中与第一APDU指令对应的任务是否执行成功。TSM平台通过终端设备发送的第一APDU指令响应消息，确定第一APDU指令是否执行成功。若第一APDU指令执行成功，则表示第一APDU任务列表中与第一APDU指令对应的任务被执行成功。
在一些示例中，TSM平台接收终端设备发送的一条第一APDU指令请求，向终端设备发送对应的一条第一APDU指令。若TSM平台接收的终端设备发送的第一APDU指令请求不是与第一APDU任务列表对应的首次发送的第一APDU指令请求，则随着接收该第一APDU指令请求，TSM平台还可接到上一条第一APDU指令对应的第一APDU指令响应消息。
第一APDU任务列表中的任务均执行成功，表示手机盾下载完成。第二状态表征手机盾下载完成。TSM平台可通过指示第一APDU任务列表 中的任务均执行成功的第一APDU指令响应消息，来确定手机盾下载完成。
在本申请实施例中，TSM平台向终端设备发送与手机盾申请请求对应的第一APDU任务列表，TSM平台将手机盾状态记录为表征手机盾下载中的第一状态。在TSM平台接收到指示第一APDU任务列表中任务均执行成功的第一APDU指令响应消息的情况下，TSM平台将手机盾状态记录为表征手机盾下载完成的第二状态。从而通过第一状态和第二状态即可实现对手机盾与下载有关的状态的管理。一次手机盾的下载安装，最少可只产生两次手机盾状态的变化。由于每次手机盾状态变化需写入手机盾状态管理系统中的数据库，因此减少了对数据库的操作次数，降低甚至避免了对手机盾状态管理系统的性能的不良影响，从而提高手机盾状态管理系统的性能。
而且，设置独立的TSM平台管理手机盾状态，可向服务提供方屏蔽终端设备厂商不同、内置芯片不同带来的手机盾管理差异，也可向用户或终端设备厂商屏蔽服务提供方不同带来的手机盾管理差异，提高了手机盾管理的适用性。
图3为本申请提供的应用于TSM平台的手机盾状态管理方法的另一实施例的流程图。图3所示的手机盾状态管理方法与图2所示的手机盾状态管理方法的不同之处在于，图3所示的手机盾状态管理方法还可包括步骤S306至步骤S311。
在步骤S306中，接收服务器发送的手机盾删除请求。
服务器即为服务提供方的服务器。终端设备向服务器发送手机盾删除请求，服务器将手机盾删除请求转发给TSM平台。手机盾删除请求用于请求删除终端设备中的手机盾。在一些示例中，手机盾删除请求可包括终端设备标识和手机盾标识，以删除与终端设备以及登录终端设备的用户对应的手机盾。
在步骤S307中，响应手机盾删除请求，向服务器发送删除成功响应消息，并在TSM平台内将手机盾状态记录为第三状态。
TSM平台在接收到手机盾删除请求后，在终端设备手机盾请求请求删 除的手机盾还未删除完成的情况下，可向服务提供方的服务器发送删除成功响应消息，以使得服务提供方的服务器中的该手机盾状态为业务无效状态。在业务无效状态下，与该手机盾相关的业务均不可用。上述向服务提供方的服务器发送删除成功响应消息的方式，解除了服务提供方的服务器的业务与通断设备中手机盾的实例之间的强依赖关系，以避免终端设备中与请求删除的手机盾的实例还未删除完成时，服务提供方的服务器与该终端设备相关的业务被阻塞，直至终端设备中请求删除的手机盾的实例删除完成后，服务提供方的服务器才可以继续执行与该终端设备相关的业务的情况。从而减少甚至消除业务等待时间，提高业务处理效率。
但由于终端设备中的该手机盾的实例还未删除完成，因此TSM平台需记录终端设备中手机盾的实际状态，TSM平台将手机盾状态记录为表征手机盾删除中的第三状态。
在步骤S308中，向终端设备发送与手机盾删除请求对应的第二APDU任务列表。
第二APDU任务列表包括至少一个任务，第二APDU任务列表中的任务指示终端设备删除手机盾删除请求请求删除的手机盾的实例。终端设备若需要执行第二APDU任务列表中的任务，则需要执行与第二APDU任务列表对应的第二APDU指令。
在步骤S309中，接收终端设备发送的第二APDU指令请求。
第二APDU指令请求用户指示终端设备向TSM平台请求第二APDU指令。在此并不限定第二APDU指令请求的数据，在一些示例中，一个第二APDU指令请求对应一条第二APDU指令。
在步骤S310中，响应第二APDU指令请求，向终端设备发送与第二APDU任务列表对应的第二APDU指令。
第二APDU指令可能为一条，也可能为两条或多条，在此并不限定第二APDU指令的数目。若终端设备接收到与第二APDU任务列表对应的所有第二APDU指令，且所有第二APDU指令执行成功，表示终端设备删除手机盾的实例成功。
在步骤S311中，接收终端设备发送的第二APDU指令响应消息，若 第二APDU指令响应消息指示第二APDU任务列表中任务均执行成功，在TSM平台内将手机盾状态记录为第四状态。
在此并不限定第二APDU指令响应消息的数目。在一些示例中，一条第二APDU指令可对应一条第二APDU指令响应消息。第二APDU指令响应消息用于指示第二APDU任务列表中与第二APDU指令对应的任务是否执行成功。TSM平台通过终端设备发送的第二APDU指令响应消息，确定第二APDU指令是否执行成功。若第二APDU指令执行成功，则表示第二APDU任务列表中与第二APDU指令对应的任务被执行成功。
在一些示例中，TSM平台接收终端设备发送的一条第二APDU指令请求，向终端设备发送对应的一条第二APDU指令。若TSM平台接收的终端设备发送的第二APDU指令请求不是与第二APDU任务列表对应的首次发送的第二APDU指令请求，则随着接收该第二APDU指令请求，TSM平台还可接收到上一条第二APDU指令对应的第二APDU指令响应消息。
第二APDU任务列表中的任务均执行成功，表示手机盾删除完成。第四状态表征手机盾删除完成。TSM平台可通过指示第二APDU任务列表中的任务均执行成功的第二APDU指令响应消息，来确定手机盾删除完成。
在本实施例中，TSM平台只需维护第一状态、第二状态、第三状态和第四状态这四个手机盾状态。通过维护这四个手机盾状态，TSM平台即可满足手机盾状态管理的需求。在手机盾下载安装或手机盾删除的过程中，能够减少手机盾状态变化的次数，减少对数据库的操作次数，从而进一步提高手机盾状态管理系统的性能。
需要说明的是，上述实施例中的第一状态、第二状态、第三状态、第四状态具体可用数字、字母、特殊符号或字符串表示，在此并不限定。
图4为本申请提供的应用于TSM平台的手机盾状态管理方法的又一实施例的流程图。图4所示的手机盾状态管理方法与图2所示的手机盾状态管理方法的不同之处在于，图4所示的手机盾状态管理方法还可包括步骤S312至步骤S316。
在步骤S312中，接收终端设备发送的数据清理请求。
在TSM平台内将手机盾状态记录为第二状态后，表示手机盾下载完成，即终端设备中该手机盾的实例下载完成。TSM平台接收终端设备主动发送的数据清理请求。数据清理请求用于请求删除手机盾状态为中间状态的手机盾的实例。中间状态包括第一状态或第三状态。
在步骤S313中，响应数据清理请求，若TSM平台内具有为第一状态或第三状态的手机盾状态，向终端设备发送第三APDU任务列表。
第三APDU任务列表可包括至少一个任务，第三APDU任务列表中的任务指示删除手机盾状态为第一状态或第三状态的手机盾的实例。终端设备若需要执行第三APDU任务列表中的任务，则需要执行与第三APDU任务列表对应的第三APDU指令。
若TSM平台内不具有第一状态或第三状态的手机盾状态，则TSM平台不需要向终端设备发送第三APDU任务列表。
在步骤S314中，接收终端设备发送的第三APDU指令请求。
第三APDU指令请求用于指示终端设备向TSM平台请求第三APDU指令。在此并不限定第三APDU指令请求的数目，在一些示例中，一个第三APDU指令请求可对应一条第三APDU指令。
在步骤S315中，响应第三APDU指令请求，向终端设备发送与第三APDU任务列表对应的第三APDU指令。
其中，第三APDU指令可能为一条，也可能为两条或多条，在此并不限定第三APDU指令的数目。若终端设备接收到与第三APDU任务列表对应的所有第三APDU指令，且所有第三APDU指令执行成功，表示终端设备删除手机盾状态为第一状态或第三状态的手机盾的实例成功。
在步骤S316中，接收终端设备发送的第三APDU指令响应消息，若第三APDU指令响应消息指示第三APDU任务列表中任务均执行成功，在TSM平台内将为第一状态或第三状态的手机盾状态更新为第四状态。
在此并不限定第三APDU指令响应消息的数目。在一些示例中，一条第三APDU指令可对应一条第三APDU指令响应消息。第三APDU指令响应消息用于指示第三APDU任务列表中与第三APDU指令对应的任务是 否执行成功。TSM平台通过终端设备发送的第三APDU指令响应消息，确定第三APDU指令是否执行成功。若第三APDU指令执行成功，则表示第三APDU任务列表中与第三APDU指令对应的任务被执行成功。
在一些示例中，TSM平台接收终端设备发送的一条第三APDU指令请求，向终端设备发送该第三APDU指令请求对应的一条第三APDU指令。若TSM平台接收的终端设备发送的第三APDU指令请求不是与第三APDU任务列表对应的首次发送的第三APDU指令请求，则随着接收该第三APDU指令请求，TSM平台还可接收到上一条第三APDU指令对应的第三APDU指令响应消息。
第三APDU任务列表中的任务均执行成功，表示手机盾状态为第一状态或第三状态的手机盾删除完成。TSM平台可将为第一状态或第三状态的手机盾状态更新为第四状态，以使TSM平台中的手机盾状态与终端设备中手机盾的实际状态同步。
需要说明的是，在下载过程或删除过程中可能会产生一些无用的、手机盾状态为中间状态，即第一状态或第三状态的手机盾。例如，服务提供方的服务器中处于业务不可用状态的手机盾，在TSM平台可能还记录为非第四状态的手机盾状态。终端设备中手机盾的实例也可能仍然处于存在状态。在手机盾下载完成后，终端设备主动向TSM平台发起不可用手机盾的清理，删除手机盾状态为第一状态或第三状态的手机盾，从而实现不可用的手机盾的静默删除。静默删除不可用的手机盾后，TSM平台可通过通知信息通知服务提供方的服务器。在手机盾下载安装完成后静默删除不可用手机盾，既能够减小手机盾安装的数据包大小，提高手机盾的安装效率，也能够提高终端设备中存储空间的利用率，避免脏数据残留。
在下载手机盾的过程中，可能会发生异常导致下载失败。为了保证异常排除后依然可继续进行手机盾的下载，可采用断点重试的方式继续进行手机盾的下载。但是，断点重试的方式存在一些弊端。
例如，当手机盾的下载发生异常时，TSM平台并没有接收到指示第一APDU任务列表中任务是否执行成功，即第一APDU指令是否执行成功的第一APDU指令响应消息，TSM平台无法确定向终端设备下发的最后一 条APDU指令是否执行成功。此时若进行断点重试，再次下载安装手机盾，TSM平台会根据发送的第一APDU指令的记录，确定断点位置，将之前向终端设备下发的最后一条第一APDU指令再向终端设备下发。若终端设备已执行过TSM平台之前下发的最后一条第一APDU指令，再次执行该第一APDU指令会出现冲突，并生成冲突应答码。但在存在终端设备厂商不同、内置芯片版本不同等差异的情况下，极有可能出现冲突应答码不统一的情况。此时，由于TSM平台中并不维护冲突应答码，TSM平台无法对不统一的冲突应答码进行处理而导致下载失败。即使再次进行断点重试，下载安装手机盾，依然会导致下载失败，从而进入下载卡死状态，无法完成手机盾的下载。
又例如，在终端设备UE1中，用户A的手机盾下载执行到一半，例如只完成了Applet的安装，或者只完成了一半的手机盾申请，由于网络中断中止了手机盾下载流程，且用户A又因某些原因选择暂时放弃重试。用户B在终端设备UE1上申请手机盾，TSM平台会误将用户A和用户B判定为同一用户，并进行断点重试。如此，则会将用户A的手机盾下载安装给用户B，从而造成敏感信息泄露。
为了避免在手机盾下载过程中发生异常所导致的下载卡死或者敏感信息泄露等问题，TSM平台可生成与终端设备对应的手机盾标识，存储手机盾标识与手机盾状态的映射关系。手机盾标识用于标识手机盾，手机盾状态随着手机盾的状态的改变而改变。若手机盾的状态发生改变，TSM平台会更新手机盾标识与手机盾状态的映射关系。
需要说明的是，对于同一终端设备而言，TSM平台中存储的手机盾标识具有唯一性。也就是说，TSM平台中存储的与同一终端设备具有对应关系的手机盾的手机盾标识具有唯一性。通过设置具有唯一性的手机盾标识来标识手机盾，每次手机盾的下载均可通过不同的手机盾标识来区分，可脱离下载卡死状态，重新下载安装手机盾；还可避免不同用户下载相同的手机盾，或者多个服务提供方对应相同的手机盾的情况，避免敏感信息泄露。
下面以一实施例对手机盾标识的生成进行具体说明，在本实施例中， 手机盾申请请求包括手机盾标识的第一部分和终端设备标识。图5为本申请提供的应用于TSM平台的手机盾状态管理方法的再一实施例的流程图。图5所示的手机盾状态管理方法与图2所示的手机盾状态管理方法的不同之处在于，图5所示的手机盾状态管理方法还可包括步骤S317至步骤S322。
在步骤S317中，对于每个终端设备标识对应的终端设备，在TSM平台中查询是否存储有与第一部分和终端设备标识匹配的手机盾标识。
手机盾标识可由多个部分组成，在此并不限定。第一部分是组成手机盾标识的其中一个部分，例如，第一部分可为手机盾标识的前缀。在TSM平台中生成本次手机盾申请请求请求的手机盾的手机盾标识。TSM平台存储有每个终端设备对应的手机盾标识，为了保证生成的手机盾标识与该终端设备中其他手机盾的手机盾标识不同，利用本次手机盾申请请求中终端设备标识和手机盾标识的第一部分，在TSM平台中查找是否存在与第一部分和终端设备标识匹配的手机盾标识。
在步骤S318中，若TSM平台中无与第一部分和终端设备标识匹配的手机盾标识，生成值为初始值的手机盾标识的第二部分，基于第一部分和第二部分，生成终端设备对应的手机盾标识。
若TSM平台中无与第一部分和终端设备标识匹配的手机盾标识，基于第一部分和手机盾标识，生成的该手机盾标识的第二部分可为初始值。由于TSM平台中无与第一部分和终端设备标识匹配的手机盾标识，则TSM平台中不存在与生成的手机盾标识相同的手机盾标识。例如，第二部分可采用十六进制记录，第二部分的初始值可为“00”。
在步骤S319中，若TSM平台中存储有与第一部分和终端设备标识匹配的手机盾标识，获取目标手机盾标识。
若TSM平台中存储有与第一部分和终端设备标识匹配的手机盾标识，则在TSM平台的与第一部分和终端设备标识匹配的手机盾标识中获取目标手机盾标识。目标手机盾标识为最近生成的一个与第一部分和终端设备标识匹配的手机盾标识。
在步骤S320中，将目标手机盾标识的第二部分的值增加预设步长 值，基于增加预设步长值后的第二部分和第一部分，生成新的目标手机盾标识。
为了使得本次生成的手机盾标识与TSM平台中已存在的与第一部分和终端设备标识匹配的手机盾标识不同，可将目标手机盾标识的第二部分的值增加预设步长值，以生成新的第二部分的值。基于新的第二部分和第一部分，生成性的目标手机盾标识。
预设步长值可根据工作场景和工作需求设定，在此并不限定。例如，预设步长值可为1。每次增加预设步长值即目标手机盾标识的第二部分的值增加1。例如，“00”增加1得到“01”，“01”增加1得到“02”，在此不一一举例说明。
在步骤S321中，若TSM平台中存储有与新的目标手机盾标识相同的手机盾标识，且手机盾标识对应的手机盾状态不为第四状态，将新的目标手机盾标识的第二部分的值再次增加预设步长值，直至TSM平台中无与新的目标手机盾标识相同的手机盾标识，将新的目标手机盾标识作为终端设备对应的手机盾标识。
在步骤S322中，若TSM平台中存储有与新的目标手机盾标识相同的手机盾标识，且手机盾标识对应的手机盾状态不为第四状态，将新的目标手机盾标识的第二部分的值再次增加预设步长值，直至TSM平台中存储有与新的目标手机盾标识相同的手机盾标识且手机盾标识对应的手机盾状态为第四状态，将新的目标手机盾标识作为终端设备对应的手机盾标识。
由于手机盾状态为第四状态的手机盾已经删除完成，因此在对手机盾申请请求请求的手机盾进行手机盾标识生成的过程中，可利用TSM平台中手机盾状态为第四状态的手机盾的手机盾标识，将该手机盾标识对应的手机盾状态由第四状态更改为第一状态，则可重新投入利用，TSM中针对同一终端设备存储的手机盾标识始终具有唯一性，不会引起下载卡死或敏感信息泄露。具体地，在步骤S321中，新的目标手机盾标识与TSM平台中手机盾状态为非第四状态的手机盾的手机盾标识不同，则可将该新的目标手机盾标识作为终端设备的手机盾申请请求请求的手机盾的手机盾标识。在步骤S322中，若新的目标手机盾标识与TSM平台中手机盾状态为 第四状态的手机盾的手机盾标识相同，可将该新的目标手机盾标识对应的手机盾状态记录为第一状态，将该新的目标手机盾标识作为终端设备的手机盾申请请求请求的手机盾的手机盾标识，并将TSM平台中原存储的与该新的目标手机盾标识相同的手机盾状态为第四状态的手机盾的手机盾标识删除；或者，若新的目标手机盾标识与TSM平台中手机盾状态为第四状态的手机盾的手机盾标识相同，则可将TSM平台中手机盾状态为第四状态的手机盾的该手机盾标识作为新的目标手机盾标识，并将手机盾状态由第四状态更改为第一状态。
值得一提的是，若在第二部分的值增加预设步长值的循环过程中，新的目标手机盾标识的第二部分的值达到预设上限值，可将第二部分的值更新为初始值，从初始值继续开始增加预设步长值的循环。预设上限值可根据工作场景和工作需求设定，在此并不限定。例如，采用十六进制进行计数，预设上限值为“FF”，则第二部分的值达到“FF”后，将第二部分的值更新为“00”，并可在“00”的基础上进行增加预设步长值的循环。
需要说明的是，若第二部分的值增加预设步长值的循环次数超出最大循环次数阈值，则结束手机盾标识的生成流程。
在一些示例中，手机盾标识可实现为应用标识(Application Identifier，AID)。AID可包括5字节的注册标识符(即RID)和11字节的扩展应用标识符(即PIX)。RID和PIX可由标准组织进行定义。本申请实施例中可利用AID中除RID和PIX外的部分字符作为上述实施例中的手机盾标识第二部分。例如，图6为本申请实施例中的手机盾标识的示例的示意图。如图6所示，该手机盾标识包括16个字节。其中，第1至5个字节为RID，第6至8个字节为手机盾业务标识，第9个字节为业务类型标识，第10至13个字节为服务提供方代码，第14个字节为手机盾类型标识，第15个字节为手机盾标识，第16个字节为保留字节。若存在同一用户可开通的手机盾的手机盾标识的数目超出一个字节可容纳的量，则可使用第15和16个字节共同作为手机盾标识，在此并不限定。
在一些示例中，在TSM平台生成手机盾标识后，TSM平台还可从服务提供方的服务器获取与终端设备的用户对应的个性化数据，在此并不限 定。
TSM平台维护的手机盾状态可包括第一状态、第二状态、第三状态和第四状态。终端设备维护的手机盾状态可包括实例不存在状态和实例存在状态。服务提供方的服务器维护的手机盾状态可包括业务无效状态和业务有效状态。TSM平台维护四个状态，终端设备维护两个状态，服务提供方的服务器维护两个状态，即可实现手机盾状态在整个手机盾状态管理系统中的管理。
下面将举例说明TSM平台维护的手机盾状态、终端设备维护的手机盾状态和服务提供方的服务器维护的手机盾状态之间的关系。
在TMS平台向终端设备发送第一APDU任务列表的情况下，若终端设备已经执行手机盾下载的任务，但手机盾下载失败，相应地，TSM平台维护的手机盾状态为第一状态，终端设备维护的手机盾状态为实例不存在状态，服务提供方的服务器维护的手机盾状态为业务无效状态。
在TMS平台向终端设备发送第一APDU任务列表的情况下，若终端设备已经执行手机盾下载的任务，且手机盾下载成功，相应地，TSM平台维护的手机盾状态为第一状态，终端设备维护的手机盾状态为实例存在状态，服务提供方的服务器维护的手机盾状态为业务无效状态。
在TMS平台接收到指示第一APDU任务列表中任务均执行成功的第一APDU指令响应消息的情况下，若TSM平台与服务提供方的服务器中之间的状态同步成功，相应地，TSM平台维护的手机盾状态为第二状态，终端设备维护的手机盾状态为实例存在状态，服务提供方的服务器维护的手机盾状态为业务有效状态。
在TMS平台接收到指示第一APDU任务列表中任务均执行成功的第一APDU指令响应消息的情况下，若TSM平台与服务提供方的服务器中之间的手机盾状态同步失败，相应地，TSM平台维护的手机盾状态为第二状态，终端设备维护的手机盾状态为实例存在状态，服务提供方的服务器维护的手机盾状态为业务无效状态。
在TSM平台响应手机盾删除请求的情况下，若终端设备还未执行手机盾的删除任务，相应地，TSM平台维护的手机盾状态为第三状态，终端 设备维护的手机盾状态为实例存在状态，服务提供方的服务器维护的手机盾状态为业务无效状态。
在TSM平台响应手机盾删除请求的情况下，若终端设备执行手机盾的删除任务失败，相应地，TSM平台维护的手机盾状态为第三状态，终端设备维护的手机盾状态为实例存在状态，服务提供方的服务器维护的手机盾状态为业务无效状态。
若终端设备执行手机盾的删除任务成功，但终端设备与TSM平台之间的手机盾状态同步失败，相应地，TSM平台维护的手机盾状态为第三状态，终端设备维护的手机盾状态为实例不存在状态，服务提供方的服务器维护的手机盾状态为业务无效状态。
若终端设备执行手机盾的删除任务成功，且终端设备与TSM平台之间的手机盾状态同步成功，相应地，TSM平台维护的手机盾状态为第四状态，终端设备维护的手机盾状态为实例不存在状态，服务提供方的服务器维护的手机盾状态为业务无效状态。
为了更加直观地说明TSM平台维护的手机盾状态的变更情况，下面将以手机盾状态的状态机来进行说明。图7为本申请实施例中的手机盾状态的状态机的示例的示意图。如图7所示，TSM平台接收终端设备发送的手机盾申请请求，TSM平台维护的手机盾状态进入第一状态00。若手机盾下载成功，TSM平台维护的手机盾状态由第一状态00变更为第二状态01。若在手机盾状态为第一状态00的情况下，TSM平台接收到了手机盾删除请求，TSM平台维护的手机盾状态由第一状态00变更为第三状态02。若在手机盾状态为第二状态01的情况下，TSM平台接收到了手机盾删除请求，TSM平台维护的手机盾状态由第二状态01变更为第三状态02。若在手机盾状态为第三状态02的情况下，TSM平台确定手机盾已删除成功，TSM平台维护的手机盾状态由第三状态02变更为第四状态03。若TSM平台接收到数据清理请求，且删除了手机盾状态为第一状态00的手机盾，则该手机盾的手机盾状态由第一状态00变更为第四状态03。若TSM平台生成的手机盾标识与TSM平台中手机盾状态为第四状态03的手机盾的手机盾标识相同，则将生成的手机盾标识对应的手机盾状态由第四 状态03变更为第一状态00。
与应用于TSM平台的手机盾状态管理方法对应，本申请实施例还提供一种手机盾状态管理方法，可应用于终端设备。该终端设备中包括手机盾控件和安全元件(Secure Element，SE)。图8为本申请提供的应用于终端设备的手机盾状态管理方法的实施例的流程图。如图8所示，该手机盾状态管理方法可包括步骤S401至步骤S407。
在步骤S401中，手机盾控件向TSM平台发送手机盾申请请求。
在步骤S402中，手机盾控件接收TSM平台发送的与手机盾申请请求对应的第一APDU任务列表。
第一APDU任务列表中的任务用于指示安全元件下载手机盾的实例。此时，终端设备中与该手机盾申请请求对应的手机盾的手机盾状态为实例不存在状态。
在步骤S403中，手机盾控件向TSM平台发送与第一APDU任务列表对应的第一APDU指令请求。
在步骤S404中，手机盾控件接收TSM平台发送的与第一APDU任务列表对应的第一APDU指令。
在步骤S405中，手机盾控件将第一APDU指令转发至安全元件。
在步骤S406中，安全元件根据第一APDU指令，执行第一APDU任务列表中的任务，并生成第一APDU指令响应消息传输至手机盾控件。
具体地，安全元件执行第一APDU任务列表中的任务，下载并存储手机盾的实例。第一APDU指令响应消息指示第一APDU任务列表中的任务是否执行成功，即指示第一APDU指令是否执行成功。
若第一APDU指令响应消息指示第一APDU任务列表中任务均执行成功，终端设备中与手机盾申请请求对应的手机盾的手机盾状态为实例存在状态。
在步骤S407中，手机盾控件向TSM平台发送第一APDU指令响应消息。
上述手机盾申请请求、第一APDU任务列表、第一APDU指令请求、第一APDU指令、第一APDU指令响应消息、实例存在状态和实例不存在 状态的内容可参见上述实施例中的相关说明，在此不再赘述。
在本申请实施例中，终端设备与TSM平台之间利用第一APDU指令和第一APDU指令响应消息进行交互，以生成或更新TSM平台中维护的手机盾状态，并在终端设备中生成或更新终端设备中维护的手机盾状态。TSM平台中通过第一状态和第二状态即可实现对手机盾与下载有关的状态的管理。一次手机盾的下载安装，手机盾状态的变化次数相对于相关技术更少。由于每次手机盾状态变化需写入手机盾状态管理系统中的数据库，因此减少了对数据库的操作次数，降低甚至避免了对手机盾状态管理系统的性能的不良影响，进而提高手机盾状态管理系统的性能。
图9为本申请提供的应用于终端设备的手机盾状态管理方法的另一实施例的流程图。相应地，终端设备中还安装有应用程序，该应用程序具体可为服务提供方的应用程序。图9所示的手机盾状态管理方法与图8所示的手机盾状态管理方法的不同之处在于，图9所示的手机盾状态管理方法还可包括步骤S408至步骤S415。
在步骤S408中，应用程序向服务器发送手机盾删除请求，以使服务器将手机盾删除请求转发至TSM平台。
在一些示例中，手机盾删除请求包括终端设备标识和手机盾标识。
在步骤S409中，应用程序接收服务器发送的手机盾删除响应消息。
手机盾删除响应消息是TSM平台发送给服务器的，用于表征手机盾删除成功。这里的服务器指的是服务提供方的服务器。应用程序接收服务器发送的手机盾删除响应消息，以使应用程序与服务提供方的服务器中的手机盾状态一致。
在步骤S410中，手机盾控件接收TSM平台与手机盾删除请求对应的第二APDU任务列表。
第二APDU任务列表中的任务用于指示安全元件删除手机盾的实例，具体指示删除与手机盾删除请求对应的手机盾的实例。此时，终端设备中与手机盾删除请求对应的手机盾的手机盾标识为实例存在状态。
在步骤S411中，手机盾控件向TSM平台发送与第二APDU任务列表对应的第二APDU指令请求。
在步骤S412中，手机盾控件接收TSM平台发送的与第二APDU任务列表对应的第二APDU指令。
在步骤S413中，手机盾控件将第二APDU指令转发至安全元件。
在步骤S414中，安全元件根据第二APDU指令，执行第二APDU任务列表中的任务，并生成第二APDU指令响应消息传输至手机盾控件。
若第二APDU响应消息指示第二APDU任务列表中任务均执行成功，终端设备中与手机盾删除请求对应的手机盾的手机盾标识为实例不存在状态。
在步骤S415中，手机盾控件向TSM平台发送第二APDU指令响应消息。
上述手机盾删除请求、手机盾删除响应消息、第二APDU任务列表、第二APDU指令请求、第二APDU指令、第二APDU指令响应消息、实例存在状态和实例不存在状态的内容可参见上述实施例中的相关说明，在此不再赘述。
图10为本申请提供的应用于终端设备的手机盾状态管理方法的又一实施例的流程图。图10所示的手机盾状态管理方法与图8所示的手机盾状态管理方法的不同之处在于，图10所示的手机盾状态管理方法还可包括步骤S416至步骤S422。
在步骤S416中，在安全元件执行成功第一APDU任务列表中的任务后，手机盾控件向TSM平台发送数据清理请求。
在步骤S417中，手机盾控件接收TSM平台发送的第三APDU任务列表。
第三APDU任务列表中的任务用于指示安全元件删除手机盾的实例。此时，终端设备中与数据清理请求对应的手机盾的手机盾状态为实例存在状态。
在步骤S418中，手机盾控件向TSM平台发送与第三APDU任务列表对应的第三APDU指令请求。
在步骤S419中，手机盾控件接收TSM平台发送的与第三APDU任务列表对应的第三APDU指令。
在步骤S420中，手机盾控件将第三APDU指令转发至安全元件。
在步骤S421中，安全元件根据第三APDU指令，执行第三APDU任务列表中的任务，保留Applet，并生成第三APDU指令响应消息传输至手机盾控件。
若第三APDU指令响应消息指示第三APDU任务列表中任务均执行成功，终端设备中与数据清理请求对应的手机盾的手机盾状态为实例不存在状态。
在相关的一些技术方案中，在终端设备的安全元件中不存在手机盾的实例的情况下，终端设备会自动删除安全元件中的Applet。若再次下载手机盾，需要重新下载Applet。在本申请实施例中，安全元件根据第三APDU指令，执行第三APDU任务列表中的任务，静默删除手机盾状态为第一状态和/或第三状态的手机盾的实例，但保留Applet不删除，从而避免频繁删除和下载Applet，从而避免频繁删除和下载Applet占用的网络数据包传输资源，减小了网络传输数据包的大小，缩短了处理时间，提升了处理效率，也节省了终端设备资源和网络资源。
在步骤S422中，手机盾控件向TSM平台发送第三APDU指令响应消息。
上述数据清理请求、第三APDU任务列表、第三APDU指令请求、第三APDU指令、第三APDU指令响应消息、实例存在状态和实例不存在状态的内容可参见上述实施例中的相关说明，在此不再赘述。
本申请实施例还提供了一种TSM平台服务器，该TSM平台服务器可实现上述实施例中TSM平台的功能。图11为本申请提供的TSM平台服务器的实施例的结构示意图。如图11所示，该TSM平台服务器500可包括接收模块501、发送模块502和状态存储模块503。
接收模块501用于接收终端设备的手机盾申请请求。
发送模块502用于响应手机盾申请请求，向终端设备发送与手机盾申请请求对应的第一应用协议数据单元APDU任务列表。
状态存储模块503用于在发送模块发送第一APDU任务列表时，将手机盾状态记录为第一状态。
其中，第一状态表征手机盾下载中。
接收模块501还用于接收终端设备发送的第一APDU指令请求。
发送模块502还用于响应第一APDU指令请求，向终端设备发送与第一APDU任务列表对应的第一APDU指令。
接收模块501还用于接收终端设备发送的第一APDU指令响应消息；
状态存储模块503还用于若第一APDU指令响应消息指示第一APDU任务列表中任务均执行成功，将手机盾状态记录为第二状态.
其中，第二状态表征手机盾下载完成。
在本申请实施例中，TSM平台服务器向终端设备发送与手机盾申请请求对应的第一APDU任务列表，TSM平台服务器将手机盾状态记录为表征手机盾下载中的第一状态。在TSM平台服务器接收到指示第一APDU任务列表中任务均执行成功的第一APDU指令响应消息的情况下，TSM平台服务器将手机盾状态记录为表征手机盾下载完成的第二状态。从而通过第一状态和第二状态即可实现对手机盾与下载有关的状态的管理。一次手机盾的下载安装，最少可只产生两次手机盾状态的变化。由于每次手机盾状态变化需写入手机盾状态管理系统中的数据库，因此减少了对数据库的操作次数，降低甚至避免了对手机盾状态管理系统的性能的不良影响，从而提高手机盾状态管理系统的性能。
而且，设置独立的TSM平台服务器管理手机盾状态，可向服务提供方屏蔽终端设备厂商不同、内置芯片不同带来的手机盾管理差异，也可向用户或终端设备厂商屏蔽服务提供方不同带来的手机盾管理差异，提高了手机盾管理的适用性。
在一些示例中，上述接收模块501还用于接收服务器发送的手机盾删除请求，以及，接收终端设备发送的第二APDU指令请求，以及接收终端设备发送的第二APDU指令响应消息。
上述发送模块502还用于响应手机盾删除请求，向服务器发送删除成功响应消息，以及，向终端设备发送与手机盾删除请求对应的第二APDU任务列表，以及响应第二APDU指令请求，向终端设备发送与第二APDU任务列表对应的第二APDU指令。
上述状态存储模块503还用于在发送模块502响应手机盾删除请求，向服务器发送删除成功响应消息时，将手机盾状态记录为第三状态，以及若第二APDU指令响应消息指示第二APDU任务列表中任务均执行成功，将手机盾状态记录为第四状态。
其中，第三状态表征手机盾删除中。第四状态表征手机盾删除完成。
具体地，手机盾删除请求可包括终端设备标识和手机盾标识。
在一些示例中，上述接收模块501还用于接收终端设备发送的数据清理请求，以及，接收终端设备发送的第三APDU指令请求，以及，接收终端设备发送的第三APDU指令响应消息。
上述发送模块502还用于响应数据清理请求，若TSM平台内具有为第一状态或第三状态的手机盾状态，向终端设备发送第三APDU任务列表，以及，响应第三APDU指令请求，向终端设备发送与第三APDU任务列表对应的第三APDU指令。
其中，第三APDU任务列表中的任务指示删除手机盾状态为第一状态或第三状态的手机盾的实例。
上述状态存储模块503还用于若第三APDU指令响应消息指示第三APDU任务列表中任务均执行成功，在TSM平台内将为第一状态或第三状态的手机盾状态更新为第四状态。
图12为本申请提供的TSM平台服务器的另一实施例的结构示意图。图12所示的TSM平台服务器与图11所示的TSM平台服务器的不同之处在于，图12所示的TSM平台服务器还可包括标识生成模块504和映射存储模块505。
标识生成模块504用于生成终端设备对应的手机盾标识。
映射存储模块505用于存储手机盾标识与手机盾状态的映射关系。
其中，对于同一终端设备，手机盾标识具有唯一性。
在一些示例中，手机盾申请请求可包括手机盾标识的第一部分和终端设备标识。
标识生成模块504可具体用于：对于每个终端设备标识对应的终端设备，在TSM平台中查询是否存储有与第一部分和终端设备标识匹配的手 机盾标识；若TSM平台中无与第一部分和终端设备标识匹配的手机盾标识，生成值为初始值的手机盾标识的第二部分，基于第一部分和第二部分，生成终端设备对应的手机盾标识。
标识生成模块504还可具体用于：若TSM平台中存储有与第一部分和终端设备标识匹配的手机盾标识，获取目标手机盾标识，目标手机盾标识为最近生成的一个与第一部分和终端设备标识匹配的手机盾标识；将目标手机盾标识的第二部分的值增加预设步长值，基于增加预设步长值后的第二部分和第一部分，生成新的目标手机盾标识；若TSM平台中存储有与新的目标手机盾标识相同的手机盾标识，且手机盾标识对应的手机盾状态不为第四状态，将新的目标手机盾标识的第二部分的值再次增加预设步长值，直至TSM平台中无与新的目标手机盾标识相同的手机盾标识，将新的目标手机盾标识作为终端设备对应的手机盾标识，或者，若TSM平台中存储有与新的目标手机盾标识相同的手机盾标识，且手机盾标识对应的手机盾状态不为第四状态，将新的目标手机盾标识的第二部分的值再次增加预设步长值，直至TSM平台中存储有与新的目标手机盾标识相同的手机盾标识且手机盾标识对应的手机盾状态为第四状态，将新的目标手机盾标识作为终端设备对应的手机盾标识。
其中，第四状态表征手机盾删除完成。
在一些示例中，标识生成模块504还可具体用于：若新的目标手机盾标识的第二部分的值达到预设上限值，将第二部分的值更新为初始值。
本申请实施例还提供了一种终端设备。图13为可应用本申请实施例的手机盾状态管理方法的终端设备的示例的结构示意图。如图13所示，该终端设备600可包括发送模块601、接收模块602、处理模块603和状态存储模块604。
发送模块601用于向可信服务管理TSM平台服务器发送手机盾申请请求。
接收模块602用于接收TSM平台服务器发送的与手机盾申请请求对应的第一应用协议数据单元APDU任务列表。
其中，第一APDU任务列表中的任务用于指示安全元件下载手机盾的 实例。终端设备中与手机盾申请请求对应的手机盾的手机盾状态为实例不存在状态。
发送模块601还用于向TSM平台服务器发送与第一APDU任务列表对应的第一APDU指令请求。
接收模块602还用于接收TSM平台服务器发送的与第一APDU任务列表对应的第一APDU指令。
处理模块603用于根据第一APDU指令，执行第一APDU任务列表中的任务，并生成第一APDU指令响应消息传输至手机盾控件。
其中，若第一APDU指令响应消息指示第一APDU任务列表中任务均执行成功，终端设备中与手机盾申请请求对应的手机盾的手机盾状态为实例存在状态。
发送模块601还用于向TSM平台服务器发送第一APDU指令响应消息。
状态存储模块604用于存储手机盾状态。
在本申请实施例中，终端设备与TSM平台服务器之间利用第一APDU指令和第一APDU指令响应消息进行交互，以生成或更新TSM平台服务器中维护的手机盾状态，并在终端设备中生成或更新终端设备中维护的手机盾状态。TSM平台服务器中通过第一状态和第二状态即可实现对手机盾与下载有关的状态的管理。一次手机盾的下载安装，手机盾状态的变化次数相对于相关技术更少。由于每次手机盾状态变化需写入手机盾状态管理系统中的数据库，因此减少了对数据库的操作次数，降低甚至避免了对手机盾状态管理系统的性能的不良影响，进而提高手机盾状态管理系统的性能。
在一些示例中，发送模块601还用于向服务器发送手机盾删除请求，以使服务器将手机盾删除请求转发至TSM平台服务器。
接收模块602还用于接收服务器发送的手机盾删除响应消息。
其中，手机盾删除响应消息是TSM平台服务器发送给服务器的，用于表征手机盾删除成功。
在一些示例中，接收模块602还用于接收与手机盾删除请求对应的第 二APDU任务列表，以及，接收TSM平台服务器发送的与第二APDU任务列表对应的第二APDU指令。
第二APDU任务列表中的任务用于指示安全元件删除手机盾的实例。状态存储模块604中与手机盾删除请求对应的手机盾的手机盾标识为实例存在状态。
发送模块601还用于向TSM平台服务器发送与第二APDU任务列表对应的第二APDU指令请求，以及，向TSM平台服务器发送第二APDU指令响应消息。
处理模块603还用于根据第二APDU指令，执行第二APDU任务列表中的任务，并生成第二APDU指令响应消息。
其中，若第二APDU响应消息指示第二APDU任务列表中任务均执行成功，状态存储模块604中与手机盾删除请求对应的手机盾的手机盾标识为实例不存在状态。
具体地，手机盾删除请求包括终端设备标识和手机盾标识。
在一些示例中，发送模块601还用于在处理模块603执行成功第一APDU任务列表中的任务后，向TSM平台服务器发送数据清理请求，以及，向TSM平台服务器发送与第三APDU任务列表对应的第三APDU指令请求，以及，向TSM平台服务器发送第三APDU指令响应消息。
接收模块602还用于接收TSM平台服务器发送的第三APDU任务列表，以及，接收TSM平台服务器发送的与第三APDU任务列表对应的第三APDU指令。
其中，第三APDU任务列表中的任务用于指示安全元件删除手机盾的实例。状态存储模块604中与数据清理请求对应的手机盾的手机盾状态为实例存在状态。
处理模块603还用于根据第三APDU指令，执行第三APDU任务列表中的任务，保留Applet，并生成第三APDU指令响应消息。
其中，若第三APDU指令响应消息指示第三APDU任务列表中任务均执行成功，状态存储模块604中与数据清理请求对应的手机盾的手机盾状态为实例不存在状态。
图14为本申请提供的TSM平台服务器的实施例的硬件结构示意图。如图14所示，TSM平台服务器700包括存储器701、处理器702及存储在存储器701上并可在处理器702上运行的计算机程序。
在一个示例中，上述处理器702可以包括中央处理器(Central Processing Unit，CPU)，或者特定集成电路(Application Specific Integrated Circuit，ASIC)，或者可以被配置成实施本申请实施例的一个或多个集成电路。
存储器701可以包括用于数据或指令的大容量存储器。举例来说而非限制，存储器701可包括硬盘驱动器(Hard Disk Drive，HDD)、软盘驱动器、闪存、光盘、磁光盘、磁带或通用串行总线(Universal Serial Bus，USB)驱动器或者两个或更多个以上这些的组合。在合适的情况下，存储器701可包括可移除或不可移除(或固定)的介质。在合适的情况下，存储器701可在综合网关容灾设备的内部或外部。在特定实施例中，存储器701是非易失性固态存储器。在特定实施例中，存储器701包括只读存储器(Read-Only Memory，ROM)。在合适的情况下，该ROM可以是掩模编程的ROM、可编程ROM(Programmable Read-Only Memory，PROM)、可擦除PROM(Erasable Programmable Read-Only Memory，EPROM)、电可擦除PROM(Electrically Erasable Programmable Read-Only Memory，EEPROM)、电可改写ROM(Electrically Alterable Read-Only Memory，EAROM)或闪存或者两个或更多个以上这些的组合。
处理器702通过读取存储器701中存储的可执行程序代码来运行与可执行程序代码对应的计算机程序，以用于实现上述应用于TSM平台的手机盾状态管理方法的任一实施例。
在一个示例中，TSM平台服务器700还可包括通信接口703和总线704。其中，如图14所示，存储器701、处理器702、通信接口703通过总线704连接并完成相互间的通信。
通信接口703，主要用于实现本申请实施例中各模块、装置、单元和/或设备之间的通信。也可通过通信接口703接入输入设备和/或输出设备。
总线704包括硬件、软件或两者，将设备的部件彼此耦接在一起。举 例来说而非限制，总线可包括加速图形端口(Accelerated Graphics Port，AGP)或其他图形总线、增强工业标准架构(Enhanced Industry Standard Architecture，EISA)总线、前端总线(Front Side Bus，FSB)、超传输(Hyper Transport，HT)互连、工业标准架构(Industrial Standard Architecture，ISA)总线、无限带宽互连、低引脚数(Low pin count，LPC)总线、存储器总线、微信道架构(Micro Channel Architecture，MCA)总线、外围组件互连(Peripheral Component Interconnect，PCI)总线、PCI-Express(PCI-X)总线、串行高级技术附件(Serial Advanced Technology Attachment，SATA)总线、视频电子标准协会局部(Video Electronics Standards Association Local Bus，VLB)总线或其他合适的总线或者两个或更多个以上这些的组合。在合适的情况下，总线704可包括一个或多个总线。尽管本申请实施例描述和示出了特定的总线，但本申请考虑任何合适的总线或互连。
本申请实施例还提供一种终端设备，该终端设备的硬件结构与上述实施例中TSM平台服务器的硬件结构示意图所示的结构基本相同。其中，终端设备的处理器通过读取终端设备的存储器中存储的可执行程序代码来运行与可执行程序代码对应的计算机程序，以用于实现上述应用于终端设备的手机盾状态管理方法的任一实施例。终端设备的硬件结构在此不再赘述。
本申请一实施例还提供一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时可实现上述应用于TSM平台的手机盾状态管理方法的任一实施例，或者，实现上述应用于终端设备的手机盾状态管理方法的任一实施例。计算机可读存储介质的示例可以是非暂态计算机可读存储介质，包括ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
上面参考根据本申请的实施例的方法、装置(系统)和计算机程序产品的流程图和/或框图描述了本申请的各方面。应当理解，流程图和/或框图中的每个方框以及流程图和/或框图中各方框的组合可以由计算机程序指令实现。这些计算机程序指令可被提供给通用计算机、专用计算机、或其 它可编程数据处理装置的处理器，以产生一种机器，使得经由计算机或其它可编程数据处理装置的处理器执行的这些指令使能对流程图和/或框图的一个或多个方框中指定的功能/动作的实现。这种处理器可以是但不限于是通用处理器、专用处理器、特殊应用处理器或者现场可编程逻辑阵列。还可理解，框图和/或流程图中的每个方框以及框图和/或流程图中的方框的组合，也可以由执行指定的功能或动作的专用硬件来实现，或可由专用硬件和计算机指令的组合来实现。
需要明确的是，本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同或相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。对于TSM平台服务器实施例、终端设备实施例和计算机可读存储介质实施例而言，相关之处可以参见方法实施例的说明部分。本申请并不局限于上文所描述并在图中示出的特定步骤和结构。本领域的技术人员可以在领会本申请的构思之后，作出各种改变、修改和添加，或者改变步骤之间的顺序。并且，为了简明起见，这里省略对已知方法技术的详细描述。
本领域技术人员应能理解，上述实施例均是示例性而非限制性的。在不同实施例中出现的不同技术特征可以进行组合，以取得有益效果。本领域技术人员在研究附图、说明书及权利要求书的基础上，应能理解并实现所揭示的实施例的其他变化的实施例。在权利要求书中，术语“包括”并不排除其他装置或步骤；不定冠词“一个”不排除多个；术语“第一”、“第二”用于标示名称而非用于表示任何特定的顺序。权利要求中的任何附图标记均不应被理解为对保护范围的限制。权利要求中出现的多个部分的功能可以由一个单独的硬件或软件模块来实现。某些技术特征出现在不同的从属权利要求中并不意味着不能将这些技术特征进行组合以取得有益效果。

Claims (11)

  1. 一种手机盾状态管理方法，应用于可信服务管理TSM平台，所述方法包括：
    接收终端设备的手机盾申请请求；
    响应所述手机盾申请请求，向所述终端设备发送与所述手机盾申请请求对应的第一应用协议数据单元APDU任务列表，并在所述TSM平台内将手机盾状态记录为第一状态，所述第一状态表征手机盾下载中；
    接收所述终端设备发送的第一APDU指令请求；
    响应所述第一APDU指令请求，向所述终端设备发送与所述第一APDU任务列表对应的第一APDU指令；
    接收所述终端设备发送的第一APDU指令响应消息，若所述第一APDU指令响应消息指示所述第一APDU任务列表中任务均执行成功，在所述TSM平台内将手机盾状态记录为第二状态，所述第二状态表征手机盾下载完成。
  2. 根据权利要求1所述的方法，还包括：
    接收服务器发送的手机盾删除请求；
    响应所述手机盾删除请求，向所述服务器发送删除成功响应消息，并在所述TSM平台内将手机盾状态记录为第三状态，所述第三状态表征手机盾删除中；
    向所述终端设备发送与所述手机盾删除请求对应的第二APDU任务列表；
    接收所述终端设备发送的第二APDU指令请求；
    响应所述第二APDU指令请求，向所述终端设备发送与所述第二APDU任务列表对应的第二APDU指令；
    接收所述终端设备发送的第二APDU指令响应消息，若所述第二APDU指令响应消息指示所述第二APDU任务列表中任务均执行成功，在TSM平台内将手机盾状态记录为第四状态，所述第四状态表征手机盾删除完成。
  3. 根据权利要求2所述的方法，其中，所述手机盾删除请求包括终端设备标识和手机盾标识。
  4. 根据权利要求2所述的方法，其中，在所述TSM平台内将手机盾状态记录为第二状态之后，还包括：
    接收所述终端设备发送的数据清理请求；
    响应所述数据清理请求，若所述TSM平台内具有为所述第一状态或所述第三状态的手机盾状态，向所述终端设备发送第三APDU任务列表，所述第三APDU任务列表中的任务指示删除手机盾状态为所述第一状态或所述第三状态的手机盾的实例；
    接收所述终端设备发送的第三APDU指令请求；
    响应所述第三APDU指令请求，向所述终端设备发送与所述第三APDU任务列表对应的第三APDU指令；
    接收所述终端设备发送的第三APDU指令响应消息，若所述第三APDU指令响应消息指示所述第三APDU任务列表中任务均执行成功，在TSM平台内将为所述第一状态或所述第三状态的手机盾状态更新为第四状态。
  5. 根据权利要求1所述的方法，其中，在所述接收终端设备的手机盾申请请求之后，还包括：
    生成所述终端设备对应的手机盾标识；
    存储所述手机盾标识与所述手机盾状态的映射关系，其中，对于同一所述终端设备，所述手机盾标识具有唯一性。
  6. 根据权利要求5所述的方法，其中，所述手机盾申请请求包括手机盾标识的第一部分和终端设备标识，
    所述生成所述终端设备对应的手机盾标识，包括：
    对于每个终端设备标识对应的终端设备，在所述TSM平台中查询是否存储有与所述第一部分和终端设备标识匹配的手机盾标识；
    若所述TSM平台中无与所述第一部分和终端设备标识匹配的手机盾标识，生成值为初始值的手机盾标识的第二部分，基于所述第一部分和所述第二部分，生成所述终端设备对应的手机盾标识。
  7. 根据权利要求6所述的方法，其中，所述生成所述终端设备对应的手机盾标识，还包括：
    若所述TSM平台中存储有与所述第一部分和终端设备标识匹配的手机盾标识，获取目标手机盾标识，所述目标手机盾标识为最近生成的一个与所述第一部分和终端设备标识匹配的手机盾标识；
    将所述目标手机盾标识的第二部分的值增加预设步长值，基于增加预设步长值后的所述第二部分和所述第一部分，生成新的目标手机盾标识；
    若所述TSM平台中存储有与新的目标手机盾标识相同的手机盾标识，且手机盾标识对应的手机盾状态不为第四状态，将新的目标手机盾标识的第二部分的值再次增加所述预设步长值，直至所述TSM平台中无与新的目标手机盾标识相同的手机盾标识，将新的目标手机盾标识作为所述终端设备对应的手机盾标识，
    或者，若所述TSM平台中存储有与新的目标手机盾标识相同的手机盾标识，且手机盾标识对应的手机盾状态不为所述第四状态，将新的目标手机盾标识的第二部分的值再次增加所述预设步长值，直至所述TSM平台中存储有与新的目标手机盾标识相同的手机盾标识且手机盾标识对应的手机盾状态为所述第四状态，将新的目标手机盾标识作为所述终端设备对应的手机盾标识；
    其中，所述第四状态表征手机盾删除完成。
  8. 根据权利要求7所述的方法，还包括：
    若新的目标手机盾标识的第二部分的值达到预设上限值，将第二部分的值更新为初始值。
  9. 一种TSM平台服务器，包括：
    接收模块，用于接收终端设备的手机盾申请请求；
    发送模块，用于响应所述手机盾申请请求，向所述终端设备发送与所述手机盾申请请求对应的第一应用协议数据单元APDU任务列表；
    状态存储模块，用于在所述发送模块发送所述第一APDU任务列表时，将手机盾状态记录为第一状态，所述第一状态表征手机盾下载中；
    所述接收模块，还用于接收所述终端设备发送的第一APDU指令请 求；
    所述发送模块，还用于响应所述第一APDU指令请求，向所述终端设备发送与所述第一APDU任务列表对应的第一APDU指令；
    所述接收模块还用于接收所述终端设备发送的第一APDU指令响应消息；
    所述状态存储模块，还用于若所述第一APDU指令响应消息指示所述第一APDU任务列表中任务均执行成功，将手机盾状态记录为第二状态，所述第二状态表征手机盾下载完成。
  10. 一种TSM平台服务器，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至8中任意一项所述的手机盾状态管理方法。
  11. 一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现如权利要求1至8中任意一项所述的手机盾状态管理方法。
PCT/CN2020/124938 2020-01-20 2020-10-29 手机盾状态管理方法、tsm平台服务器及存储介质 WO2021147433A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010065933.4 2020-01-20
CN202010065933.4A CN111314064B (zh) 2020-01-20 2020-01-20 手机盾状态管理方法、tsm平台服务器及存储介质

Publications (1)

Publication Number Publication Date
WO2021147433A1 true WO2021147433A1 (zh) 2021-07-29

Family

ID=71146815

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/124938 WO2021147433A1 (zh) 2020-01-20 2020-10-29 手机盾状态管理方法、tsm平台服务器及存储介质

Country Status (2)

Country Link
CN (1) CN111314064B (zh)
WO (1) WO2021147433A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111314064B (zh) * 2020-01-20 2021-09-17 中国银联股份有限公司 手机盾状态管理方法、tsm平台服务器及存储介质
CN112381541A (zh) * 2020-11-16 2021-02-19 深圳市天行云供应链有限公司 跨银行多u盾系统以及应用跨银行多u盾系统的支付方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105812370A (zh) * 2016-03-16 2016-07-27 中国联合网络通信集团有限公司 智能卡处理方法、装置及系统
CN108537535A (zh) * 2018-03-27 2018-09-14 江苏恒宝智能系统技术有限公司 基于手机盾的移动终端及手机盾管理方法
US20180341937A1 (en) * 2015-09-01 2018-11-29 Samsung Electronics Co., Ltd. Method and apparatus for performing settlement transaction
CN111314064A (zh) * 2020-01-20 2020-06-19 中国银联股份有限公司 手机盾状态管理方法、tsm平台服务器及存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102053917B (zh) * 2010-12-29 2013-04-24 北京握奇数据系统有限公司 一种降低内存占用的智能卡及其处理指令的方法
US8706081B1 (en) * 2012-12-18 2014-04-22 Google Inc. Packet inspection in near field communication controller for secure element protection
CN103914713B (zh) * 2012-12-30 2017-05-31 北京握奇数据系统有限公司 一种改变智能卡应用类型的方法、智能终端、服务平台与系统
CN105592440A (zh) * 2015-12-25 2016-05-18 中国银联股份有限公司 智能卡内容管理系统
JP7122252B2 (ja) * 2016-03-29 2022-08-19 京セラ株式会社 管理システム、管理方法、機器及び管理装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180341937A1 (en) * 2015-09-01 2018-11-29 Samsung Electronics Co., Ltd. Method and apparatus for performing settlement transaction
CN105812370A (zh) * 2016-03-16 2016-07-27 中国联合网络通信集团有限公司 智能卡处理方法、装置及系统
CN108537535A (zh) * 2018-03-27 2018-09-14 江苏恒宝智能系统技术有限公司 基于手机盾的移动终端及手机盾管理方法
CN111314064A (zh) * 2020-01-20 2020-06-19 中国银联股份有限公司 手机盾状态管理方法、tsm平台服务器及存储介质

Also Published As

Publication number Publication date
CN111314064A (zh) 2020-06-19
CN111314064B (zh) 2021-09-17

Similar Documents

Publication Publication Date Title
EP3800909B1 (en) Remote management method, and device
CN102232304B (zh) 一种移动通信终端间进行系统升级的方法、系统及终端
JP6603311B2 (ja) ブラウザによりローカルサービスアセンブリを呼び出すための方法、デバイス及びシステム
WO2021147433A1 (zh) 手机盾状态管理方法、tsm平台服务器及存储介质
WO2020233361A1 (zh) 基于网关的内部服务调用方法、装置及终端设备
EP2521034A1 (en) Managing method, device and terminal for application program
US20170201378A1 (en) Electronic device and method for authenticating identification information thereof
EP3534583A1 (en) Secure processor chip and terminal device
WO2021164125A1 (zh) 会话创建方法及相关设备
WO2016023199A1 (zh) 一种安全域管理方法、装置及系统
CN111918274B (zh) 码号配置、管理方法、装置、电子设备及可读存储介质
CN109495874B (zh) Profile下载的方法和装置
WO2022073340A1 (zh) 移动终端应用程序安全检测方法、系统、终端及存储介质
WO2015180516A1 (zh) 一种实现携号升级入网的方法、装置及系统
CN106535156B (zh) 虚拟用户识别模块卡的迁移方法、终端、服务器、系统
CN111586671A (zh) 嵌入式用户识别卡配置方法、装置、通信设备和存储介质
CN112632573A (zh) 智能合约执行方法、装置、系统、存储介质及电子设备
KR20200017180A (ko) 전자 장치, 외부 전자 장치 및 외부 전자 장치의 eSIM 관리 방법
CN210627203U (zh) 一种带有安全存储功能的uicc装置
CN112637855B (zh) 基于区块链的机卡绑定方法和服务器
CN112188476B (zh) 通信方法、通信装置、移动终端和存储介质
JP2023546509A (ja) 通信接続を確立する方法と装置
CN113704773A (zh) 继电保护安全芯片操作系统及其通信方法
US9571272B2 (en) Image forming apparatus, information processing method, and control method
CN110990122A (zh) 一种虚拟机迁移方法和装置

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: 20914823

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: 20914823

Country of ref document: EP

Kind code of ref document: A1