WO2017219513A1 - 开卡数据写入方法、装置及系统 - Google Patents

开卡数据写入方法、装置及系统 Download PDF

Info

Publication number
WO2017219513A1
WO2017219513A1 PCT/CN2016/098946 CN2016098946W WO2017219513A1 WO 2017219513 A1 WO2017219513 A1 WO 2017219513A1 CN 2016098946 W CN2016098946 W CN 2016098946W WO 2017219513 A1 WO2017219513 A1 WO 2017219513A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
card
thread
chip
smart device
Prior art date
Application number
PCT/CN2016/098946
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 WO2017219513A1 publication Critical patent/WO2017219513A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3278—RFID or NFC payments by means of M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K1/00—Methods or arrangements for marking the record carrier in digital fashion
    • G06K1/12—Methods or arrangements for marking the record carrier in digital fashion otherwise than by punching
    • G06K1/128—Methods or arrangements for marking the record carrier in digital fashion otherwise than by punching by electric registration, e.g. electrolytic, spark erosion
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
    • G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
    • G06K19/067—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components
    • G06K19/07—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips
    • G06K19/077—Constructional details, e.g. mounting of circuits in the carrier
    • G06K19/07701—Constructional details, e.g. mounting of circuits in the carrier the record carrier comprising an interface suitable for human interaction
    • G06K19/07703—Constructional details, e.g. mounting of circuits in the carrier the record carrier comprising an interface suitable for human interaction the interface being visual
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/204—Point-of-sale [POS] network systems comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3227—Aspects of commerce using mobile devices [M-devices] using secure elements embedded in M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/352—Contactless payments by cards
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/355—Personalisation of cards for use
    • G06Q20/3552—Downloading or loading of personalisation data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/356—Aspects of software for card payments
    • G06Q20/3567—Software being in the reader
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists

Definitions

  • the present disclosure relates to the field of computer technologies, and in particular, to a method, device, and system for writing card data.
  • NFC near field communication
  • the secure element (English: secure dlement, SE) on the NFC device has its own computing power.
  • the NFC device writes the card data required for card emulation in the SE through offline preset or network card issuance.
  • a common way to write card data to the SE is to install a corresponding application (English: application, App) on the NFC device.
  • the NFC device needs to be executed multiple times with the server.
  • the interaction operation after the related interaction operation is completed, finally obtains the data required for the card opening from the server, and writes the acquired data to the SE chip at one time, because the interaction process and the data writing process take a long time. Therefore, it takes too long to open the card with the NFC device.
  • the present disclosure provides a method, device and system for writing card opening data.
  • the technical solution is as follows:
  • a card opening data writing method for use in a smart device including an SE chip, the method comprising: implementing a related operation before opening a card by using a user interface UI thread
  • the first background thread is created; the first background thread is used to obtain the first part of data required for opening the card from the server, and the first part of data is written into the SE chip;
  • the second background thread is created, and the second background thread is used to write the second part of data required for the card opening into the SE chip, the first The partial data and the second partial data are data related to the card opening that needs to be written into the SE chip.
  • creating the first background thread includes: performing the related operations before the card opening by using the UI thread, if the UI
  • the first background thread is created when the thread receives an allow indication indicating that the card is allowed to be opened. Since the UI thread implements the related operations before the card opening is complicated and diverse, in order to write the data required for the card opening to the SE chip as soon as possible, the first thread can be created when the UI thread receives the permission indication for allowing the card to be opened.
  • the background thread performs the data required to write the card to the SE chip, so that the UI thread can write data to the SE chip as early as possible during the related operation of the UI thread to minimize the time required to open the card.
  • the creating the second background thread includes: detecting whether the first background thread writes all the first part of data into the SE chip; if the first background thread has not yet the first part All the data is written into the SE chip, waiting for the first background thread to continue writing the remaining first portion of data to the SE chip, after all the first partial data is written into the SE chip, Creating the second background thread; if the first background thread has written all of the first portion of data into the SE chip, creating the second background thread.
  • the method further includes: detecting whether the UI thread completes a related operation before the card is opened; if the UI thread completes a related operation before the card is opened, displaying the card opening control; When triggered, it is determined that the related operation before the card opening is completed by the UI thread and the card opening is determined. In order to avoid a leak operation in the related operation before the card is opened, it is necessary to display the card opening control after determining that the UI thread completes the related operation before the card is opened, so as to perform the operation of finally writing the remaining data to the UE chip.
  • the method further includes: the first part of data and the second part of data are both After successfully writing to the SE chip, a prompt message for prompting the card issuance success is displayed.
  • the first part of data is non-personalized data required for opening a card
  • the second part of data is personalized data required for opening a card.
  • the non-personalized data is data that must be written to the SE chip when the card is instantiated, the data is not affected by the operation of the UI thread, so the non-personalized data can be performed during the UI thread to perform related operations before the card is opened.
  • Write to the SE chip, and then write the personalized data to the SE chip when the UI thread completes the relevant operations before the card is opened, thereby ensuring the correctness of the data in the SE chip when the card is opened.
  • a card opening data writing method is provided, which is applied to a server, the method comprising: receiving a first data acquisition request sent by a smart device, and sending a card issuing office to the smart device The first part of the data is required to be sent by the first background thread after the first background thread is created in the process of using the user interface UI thread to implement the related operation before the card is opened.
  • the first part of the data is used to trigger the smart device to write the first part of data into the secure element SE chip of the smart device; acquire the second part of data required for the smart device to open the card; a second data acquisition request sent by the smart device, where the second part of data is sent to the smart device, where the second data acquisition request is related to the smart device before the card is opened by using the UI thread.
  • the second background thread is created, the second part of the data is sent by the second background thread, and the second part of data is used to trigger the smart Preparation of the second portion of the write data SE chip.
  • the first part of the data related to the card opening is sent to the smart device, so that the smart device has written to the SE chip when the UI thread completes the related operation before the card is opened.
  • the final step only some data that has not been written to the SE chip needs to be written, which saves the writing and writing to the SE chip during the related operation before the UI thread realizes the card opening.
  • the writing time required for the related partial data solves the problem that the NFC device takes too long to open the card in the related art, and reduces the time taken when the NFC device is used for card opening.
  • the acquiring the second part of data required for the smart device to open the card includes: receiving a third part of data sent by the smart device, where the third part of data is that the smart device uses the UI Thread generated; generating the second portion of data according to a predetermined card opening rule and the third portion of data.
  • the first part of data is non-personalized data required for opening a card
  • the second part of data is personalized data required for opening a card.
  • a card opening data writing apparatus for use in a smart device including an SE chip, the apparatus comprising: a first creation module configured to utilize a user interface UI thread In the process of implementing the related operations before the card opening, the first background thread is created; the first writing module is configured to acquire, by using the first background thread created by the first creating module, the first required for opening the card from the server a part of the data, the first part of the data is written into the SE chip; the second creation module is configured to create a second background thread after completing the relevant operation before the card is opened by the UI thread and determining to open the card; a second write module configured to use the second background thread created by the second creation module to write a second portion of data required to open the card into the SE chip, the first portion of data and the The second part of the data is the data related to the card opening that needs to be written into the SE chip.
  • the first creating module is further configured to: if the UI thread receives an permission indication for allowing the card to be opened, in the process of implementing the related operation before the card is opened by using the UI thread, Then creating the first background thread.
  • the second creating module includes: a detecting submodule configured to detect whether the first background thread writes all the first part of data into the SE chip; the first creating submodule is Configuring to wait for the first background thread to continue writing the remaining first portion of data when the detecting submodule detects that the first background thread has not written all of the first portion of data into the SE chip. Entering the SE chip, after writing the first partial data to the SE chip, creating the second background thread; and the second creating submodule configured to detect the first in the detecting submodule The second background thread is created when a background thread has written all of the first portion of data into the SE chip.
  • the device further includes: a detecting module configured to detect whether the UI thread completes a related operation before the card is opened; the first display module is configured to detect, in the detecting module, that the UI thread is completed When the related operation before the card is opened, the card opening control is displayed; the determining module is configured to determine, when the card opening control displayed by the first display module is triggered, that the UI thread is used to complete the card opening Related operations and determine the card opening.
  • a detecting module configured to detect whether the UI thread completes a related operation before the card is opened
  • the first display module is configured to detect, in the detecting module, that the UI thread is completed When the related operation before the card is opened, the card opening control is displayed
  • the determining module is configured to determine, when the card opening control displayed by the first display module is triggered, that the UI thread is used to complete the card opening Related operations and determine the card opening.
  • the device further includes: a second display module, configured to display a prompt for prompting the card issuance after the first partial data and the second partial data are successfully written into the SE chip information.
  • a second display module configured to display a prompt for prompting the card issuance after the first partial data and the second partial data are successfully written into the SE chip information.
  • the first part of data is non-personalized data required for opening a card
  • the second part of data is personalized data required for opening a card.
  • a card opening data writing device which is applied to a server, the device comprising: a first transceiver module configured to receive a first data acquisition request sent by the smart device, The smart device sends a first part of data required for opening a card, where the first data acquisition request is a process in which the smart device creates a first background thread in a process of implementing a related operation before the card is opened by using a user interface UI thread.
  • the first part of data is used to trigger the smart device to write the first part of data into the secure element SE chip in the smart device, and the acquiring module is configured to acquire the The second part of the data is required to be opened by the smart device; the second transceiver module is configured to receive the second data acquisition request sent by the smart device, and send the second part acquired by the acquiring module to the smart device Data, the second data acquisition request is after the smart device completes the related operation before the card is opened by using the UI thread, and after determining to open the card, After building a second background thread with the second thread sends the background, the second portion of the data for triggering the smart device, the second portion of the write data SE chip.
  • the acquiring module includes: a receiving submodule configured to receive a third portion of data sent by the smart device, where the third portion of data is generated by the smart device by using the UI thread; And a submodule configured to generate the second partial data according to a predetermined card opening rule and the third partial data received by the receiving submodule.
  • the first part of data is non-personalized data required for opening a card
  • the second part of data is personalized data required for opening a card.
  • a card opening data writing system comprising a smart device and a server, the smart device comprising any of the various optional implementations of the third aspect and the third aspect A card opening data writing device, the server comprising the card opening data writing device according to any of the fourth aspect and the fourth aspect of the invention.
  • an open card data writing device which is applied to a smart device including an SE chip, the device comprising:
  • a memory for storing the processor executable instructions
  • processor is configured to:
  • the first background thread Using the first background thread to obtain the first part of data required to open the card from the server, The first part of data is written into the SE chip;
  • the second background thread is created, and the second background thread is used to write the second part of data required for the card opening into the SE chip.
  • the first partial data and the second partial data are data related to card opening that need to be written into the SE chip.
  • an open card data writing device which is applied to a server, the device comprising:
  • a memory for storing the processor executable instructions
  • processor is configured to:
  • Receiving a first data acquisition request sent by the smart device and sending, to the smart device, a first part of data required for opening the card, where the first data acquisition request is related to the smart device before using the user interface UI thread to implement card opening
  • the first background thread is created, the first part of the data is sent by the first background thread, and the first part of data is used to trigger the smart device to write the first part of data into the security element SE of the smart device.
  • the second part of the data is sent by the second background thread, and the second part of data is used to trigger the smart device to write the second part of data into the SE chip. in.
  • FIG. 1 is a schematic structural diagram of a smart device according to an exemplary embodiment
  • FIG. 2 is a flowchart of a method for writing card data according to an exemplary embodiment
  • FIG. 3A is a flowchart of a method for writing card data according to another exemplary embodiment
  • FIG. 3B is a flowchart showing a second background thread when creating a second background thread according to an exemplary embodiment
  • 3C and 3D are schematic diagrams showing the durations of use of each process in two card opening processes according to an exemplary embodiment
  • FIG. 4 is a flowchart of a method for writing card data according to still another exemplary embodiment
  • FIG. 5A is a block diagram of an card opening data writing apparatus according to an exemplary embodiment
  • FIG. 5B is a block diagram of an card opening data writing apparatus according to another exemplary embodiment
  • FIG. 6A is a block diagram of an card opening data writing apparatus according to still another exemplary embodiment
  • FIG. 6B is a block diagram of an card opening data writing apparatus according to still another exemplary embodiment
  • FIG. 7 is a block diagram of an open card data writing system according to an exemplary embodiment
  • FIG. 8 is a block diagram of an card opening data writing apparatus according to still another exemplary embodiment.
  • FIG. 9 is a block diagram of an card opening data writing apparatus according to still another exemplary embodiment.
  • FIG. 1 is a schematic structural diagram of a smart device according to an exemplary embodiment. As shown in FIG. 1 , the smart device 100 may include at least an SE chip 120 and an NFC radio frequency unit 140 .
  • the SE chip 120 is used to store data that needs to be stored in the physical card when the physical card is simulated, and the SE chip 120 has the computing capability, and the stored data can be modified.
  • the NFC radio unit 140 has a radio frequency communication function, which can communicate with an external NFC communication device through radio frequency technology.
  • the SE chip 120 can exchange information with the NFC radio unit 140.
  • the SE chip 120 transmits the data to be sent through the NFC radio unit 140.
  • the NFC radio unit 140 can send the received data to the SE chip 120.
  • the SE chip 120 Perform operations or modify stored data.
  • the smart device 100 may further include other communication units 160, which may communicate with a network side device (such as a server), and the SE chip 120 passes through other communication units 160 and the network.
  • the network side device performs data interaction.
  • the smart device 100 When the smart device 100 is used to simulate an NFC card (such as a common bus card or a bank card), the smart device 100 is generally required to have an SE chip 120 and an NFC radio frequency unit 140.
  • the SE chip 120 is used to store data required for simulating a physical card, NFC.
  • the RF unit 140 is combined with the SE chip 120 to implement the functions of the NFC card.
  • the smart device 100 having the above-described SE chip 120 and NFC radio frequency unit 140 may also be referred to as an NFC device.
  • Each of the following embodiments implements the function of card opening based on the smart device of the structure of FIG. 1.
  • FIG. 2 is a flowchart of a method for writing card data according to an exemplary embodiment. As shown in FIG. 2, the card data writing method is applied to the smart device 100 shown in FIG. 1 and includes the following. step.
  • a first background thread is created in the process of implementing a related operation before the card is opened by using the UI thread.
  • the UI thread is a thread that performs related operations before the card is opened.
  • the UI thread is used to display pages related to card opening operations before card opening, related operations for executing these pages, and the like.
  • the smart device can usually install an application related to the instantiated NFC card, and use the application to create a UI thread, and the UI thread can interact with the server to obtain a page to be displayed and an execution page during the card opening process.
  • an application related to the instantiated NFC card and use the application to create a UI thread
  • the UI thread can interact with the server to obtain a page to be displayed and an execution page during the card opening process.
  • the common page related to card opening includes a display page of the service terms related to the card opening, a personalized data input page related to the card opening, etc., and these pages may have a user input personalization.
  • step 202 the first background thread is used to obtain the first part of data required for card opening from the server, and the first part of data is written into the SE chip.
  • step 203 after the UI thread is used to complete the related operations before the card is opened and the card is determined to be opened, the second background thread is created, and the second background thread is used to write the second part of the data required for the card opening into the SE chip.
  • Part of the data and the second part of the data are the card-related data that needs to be written into the SE chip.
  • the first part of the data is the data that needs to be written into the SE chip when the card is opened by the server.
  • the first part of the data is generally the preloaded data required for the card opening.
  • the first part of the data is usually not changed due to the operation of the UI thread.
  • the second part of the data is the data that needs to be written into the SE chip when the card is opened, and the second part of the data may be due to The operation of the UI thread changes.
  • the method for writing card data needs to write a card to the SE chip by using the created first background thread in the process of implementing the related operations before the card is opened in the UI thread.
  • Part of the data so that when the UI thread completes the relevant operations before the card is opened, the partial data related to the card opening has been written to the SE chip, and only the data that has not been written to the SE chip can be written in the last step.
  • the utility model saves the writing time required for writing part of the data related to the card opening of the SE chip during the related operation process before the UI thread realizes the card opening, and solves the problem of using the NFC device for card opening in the related art. The problem of being too long reduces the time taken when opening an NFC device.
  • FIG. 3A is a flowchart of a card-opening data writing method according to another exemplary embodiment. As shown in FIG. 3, the card-opening data writing method is applied to the smart device 100 shown in FIG. The following steps.
  • a first background thread is created in the process of implementing a related operation before the card is opened by using the UI thread.
  • the UI thread is a thread that performs related operations before the card is opened.
  • the UI thread is used to display pages related to card opening operations before card opening, related operations for executing these pages, and the like.
  • the smart device can usually install an application related to the instantiated NFC card, and use the application to create a UI thread, and the UI thread can interact with the server to obtain a page to be displayed and an execution page during the card opening process.
  • an application related to the instantiated NFC card and use the application to create a UI thread
  • the UI thread can interact with the server to obtain a page to be displayed and an execution page during the card opening process.
  • the common page includes a display page of the service terms related to the card opening, a personalized data input page related to the card opening, etc., and these pages may have an input box for guiding the user to input personalized data. And controls that guide the user to confirm or cancel the input of personalized data.
  • the UI thread receives the permission indication for indicating that the card is allowed to be opened, the first background thread is created.
  • the permission indication here generally means that the card-opening user allows the card to be opened, and the UI thread can continue to perform related operations before the card is opened.
  • the allowable indication means that the user is prepared to perform related operations before the card is opened according to the UI thread.
  • the UI thread in a common card opening process, usually displays the service terms related to the card opening obtained from the server. When the user agrees to the terms of service, it can be determined that the UI thread receives the indication for permission. The permission indication of the card is opened, and the first background thread can be created at this time.
  • the UI thread may display a prompt asking the user if he wishes to open the card.
  • the user confirms that he wishes to open the card, it may be determined that the UI thread receives the indication for allowing the card to be opened.
  • the indication is allowed, in which case the first background thread can be created.
  • the first background thread generally does not involve the display or operation of the UI interface. During the execution of the UI thread, it may run in parallel with the UI thread, or may run serially with the UI thread. During the serial running of the first background thread with the UI thread, since the UI thread may pause during the entire process of the operation, such as waiting for a user operation, the first background thread may run at an interval at which the UI thread stops running. However, from a macro perspective, the first background thread and the UI thread can still be regarded as a side-by-side relationship, that is, the first background thread can run simultaneously during the entire duration of the UI thread execution.
  • step 302 the first background thread is used to obtain the first part of data required for opening the card from the server, and the first part of data is written into the SE chip.
  • the first part of the data is the data that needs to be written into the SE chip when the card is opened by the server.
  • the data is generally the preloaded data required for the card opening.
  • the first part of the data is usually not changed due to the operation of the UI thread.
  • the first part of the data is independent of the personalized data, and in order to make the identification of the NFC card after the instantiation, it is necessary to write data related to the user information to the SE chip, so that the NFC card has a unique identity, such data is generally This is called personalization data, that is, the second part of data mentioned below in this embodiment.
  • the second part of the data is usually the data related to the user information that needs to be written into the SE chip when the card is opened, and the second part of the data may be changed due to the operation of the UI thread. Since the user may need to input personalized data when using the UI thread, such as the user's phone number, identity information, recharge amount, etc., the user acquired by the UI thread when the user performs the relevant operation before the card is opened by the UI thread.
  • the input data may be different or partially different, so this data can be determined by the operation of the UI thread.
  • the personalized data may further include data allocated by the server for the card opening operation to uniquely identify the identity of the user.
  • the first part of the data may include data that interacts with the NFC radio unit, and may further include data for modifying the personalized data in the SE chip.
  • the data that needs to be written into the SE chip can be divided into a first part of data and a second part of data, wherein the first part of data is non-personalized data required for opening the card, and the second part of data is It is the personal data needed to open the card.
  • the first background thread When the first background thread writes the first part of data to the SE chip, it can be written in a predetermined manner, and the path written to the SE chip can also be preset.
  • the UI thread guides the user to input personalized data during the process of using the smart device to open the card, the UI thread takes a certain amount of time, and the duration is necessary in the card opening process. Obviously, during the execution of the UI thread, By using the first background thread to write the first part of data to the SE chip, the writing time of the user waiting for the thread to write the first part of data to the SE chip can be saved.
  • step 303 it is detected whether the UI thread completes the related operation before the card is opened.
  • the related operations performed by the UI thread are known. Therefore, according to the related operations performed by the UI thread, it can be determined whether the UI thread completes the correlation before the card is opened. operating. That is to say, whether the UI thread has the condition for displaying the card opening control, so that the user can use the card opening control to determine the card opening.
  • step 304 if the UI thread completes the related operation before the card is opened, the card opening control is displayed.
  • the card opening control is triggered, it is determined that the related operation before the card opening is completed by the UI thread and the card opening is determined.
  • the attribute of the displayed card opening control is to allow the operation or allow the operation response.
  • the user can trigger the card opening control.
  • the UI thread can know that the card opening control is triggered.
  • the attributes of the opened card control are generally prohibited or prohibited, such as the common gray representation. In this case, even if the user triggers the open card control, the UI thread will not respond to the trigger operation.
  • the display card opening control described here refers to the card opening control whose display attribute is to allow operation or allow operation response.
  • the user triggers the card opening control it indicates that the user no longer modifies the data input of the interface involved in the UI thread, so at this time, it can be determined that the card opening is determined.
  • step 305 after the relevant operation before the card opening is completed by the UI thread and the card opening is determined, the second background thread is created.
  • the UI thread After the UI thread is used to complete the related operations before the card is opened and the card is determined to be opened, it usually means that the user no longer modifies the personalized data. At this time, the second background thread can be created to implement the writing of the personalized data to the SE chip.
  • the smart device creates a second background thread by using the application, it can refer to the steps shown in FIG. 3B.
  • step 305a it is detected whether the first background thread writes all of the first partial data into the SE chip.
  • the application releases the first background thread.
  • the first background thread When the first background thread has not been released, it can be determined that the first background thread has not written all the first part of data to the SE chip; when the first background thread has been released, it can be determined that the first background thread has already been The first part of the data is all written into the SE chip.
  • step 305b if the first background thread has not written all the first part of data into the SE chip, waiting for the first background thread to continue writing the remaining first part of data to the SE chip, and writing the first part of the data to the SE chip. After that, create a second background thread.
  • step 305c if the first background thread has written all of the first portion of data into the SE chip, a second background thread is created.
  • the second background thread writes the second part of the data to the second path of the SE chip, the first path and the second path are different. In this case, there is generally no write data error.
  • the second background thread can be created without waiting for the first background thread to be completely released.
  • step 306 the second background thread is used to write the second portion of data required to open the card into the SE chip.
  • the second part of the data required to open the card is generally the data obtained in the related operations performed by the UI thread.
  • the second part of the data may also be obtained by the UI thread to perform related operations, and then synchronized to the server data, so that when implemented, the second background thread may be pulled from the server to the second required for card opening. part of data.
  • the server performs the audit, and after the audit is passed, the first part of the data is bound and stored.
  • the second background thread sends a request for obtaining the second part of data to the server, and the second part of the server passes the feedback.
  • the second part of the data acquired from the server is written into the SE chip.
  • the second background thread When the second background thread writes the second part of data to the SE chip, it can be written in a predetermined manner, and the path written to the SE chip can also be preset.
  • step 307 after the first partial data and the second partial data are successfully written into the SE chip, prompt information for prompting the card issuance success is displayed.
  • the prompt information can be used to prompt the user to issue the card successfully, so that the user can use the NFC device instead of the practice card for use.
  • the NFC device can communicate with the NFC receiver using the NFC radio unit, and modify the data in the SE chip by using the communication information.
  • the SE chip in the NFC device includes data for indicating the remaining amount.
  • the NFC radio unit in the NFC device can learn the bus fee deductor. Informing the resource value that needs to be deducted, the NFC radio unit will notify the SE chip to modify the data indicating the remaining amount, and reduce the data by the resource value.
  • the duration of the operation is shorter than the length of the related operation before the UI thread executes the card opening, and after the UI thread is created, the first background thread is created after the predetermined length ⁇ t.
  • the total length of time used to open the card is the length of time that the UI thread performs the relevant operations before the card is opened, and the length of time that the second background thread writes the second part of the data. As shown in FIG.
  • t1 is the duration of the UI thread executing the related operation before the card is opened
  • t2 is the duration of writing the first part of data by using the first background thread
  • the first background thread is created after the predetermined length ⁇ t is created after the UI thread is created
  • T3 is the duration of writing the second part of data by using the second background thread
  • t2 is less than t1
  • the total length of time used for opening the card is t1+t3.
  • the first background thread is used to write the first part of the data, and the UI thread executes the relevant operation time before the card is opened, and the first background thread is created after the UI thread is created for a predetermined time period ⁇ t, the total length of the card is used.
  • t1 is the duration of the UI thread executing the related operation before the card is opened
  • t2 is the duration of writing the first part of data by using the first background thread
  • the first background thread is created after the predetermined length of time ⁇ t is created after the UI thread is created.
  • T3 is the duration of writing the second partial data by using the second background thread, and t2 is greater than t1.
  • the total length of time used for opening the card is ⁇ t+t2+t3, and ⁇ t is smaller than t1.
  • the total length of time used to open the card is less than the total length of the conventional card opening time t1 + t2 + t3.
  • the card opening data writing method provided in the embodiment of the present disclosure is implemented in a UI thread.
  • the first background thread created is used to write the partial data required for the card opening to the SE chip, so that the UI chip has been written to the SE chip when the UI thread completes the related operation before the card is opened.
  • only the data that has not been written to the SE chip needs to be written, which saves the writing and writing of the SE chip during the related operation before the UI thread realizes the card opening.
  • the writing time required for the card-related partial data solves the problem that the NFC device takes too long to open the card in the related art, and reduces the time taken when the NFC device is used for card opening.
  • the UI thread implements the related operations before the card opening is complicated and diverse, in order to write the data required for the card opening to the SE chip as soon as possible, the UI thread can be created when the UI thread receives the permission indication for permitting the card opening.
  • the first background thread performs the data required to write the card to the SE chip, so that the UI thread can write data to the SE chip as early as possible during the operation of the UI thread to open the card, so as to minimize the time required to open the card. .
  • the problem that the data may be written when the two threads simultaneously write data to the SE chip is avoided.
  • the server since the first part of data is written by the smart device by using the first background thread, the second part of data is written by the smart device by the second background thread, so for the first part of data and the second part of data provided,
  • the server will also have corresponding improvements.
  • the following steps in Figure 4 explain the implementation process of the smart device and the server during the card opening process.
  • FIG. 4 is a flowchart of a method for writing card data according to still another exemplary embodiment, the method for writing card data includes the following steps.
  • step 401 the smart device creates a first background thread in the process of implementing a related operation before the card is opened by using the UI thread.
  • Step 401 is similar to step 301.
  • Step 401 refers to the description of step 301, and details are not described herein again.
  • step 402 the smart device sends a first data acquisition request to the server using the first background thread.
  • the smart device may send the first data acquisition request to the server by using the first background thread in order to obtain the first part of the data related to the card opening.
  • step 403 the server receives the first data acquisition request.
  • the server may receive the first data acquisition request.
  • step 404 the server feeds back to the smart device the first portion of data needed to open the card.
  • the smart device may feed back the first part of data required for the card opening.
  • the first part of the data here, refer to the explanation of the first part of the data in step 302.
  • step 405 the smart device receives the first partial data, and uses the first background thread to write the first partial data into the SE chip.
  • Step 405 is similar to step 302. For details, refer to the description of step 302, and details are not described herein again.
  • step 406 the smart device creates a second background thread after completing the related operations before the card is opened by the UI thread and determining to open the card.
  • Step 406 can be implemented by step 303 to step 305 or by step 305.
  • Step 303 to step 305 For details, refer to the description of step 303 to step 305, and details are not described herein again.
  • step 407 the server acquires the second part of data required for the smart device to open the card.
  • the server may receive the third part of data sent by the smart device when acquiring the second part of data required for the smart device to open the card, where the third part of the data is generated by the smart device by using the UI thread, according to a predetermined card opening rule and The third portion of data generates the second portion of data.
  • the UI thread prompts the user to input personalized data related to the card opening, and verification information related to the card opening, etc., and the personalized data and the verification information can be sent to the server as the third part of the data.
  • the server may perform verification according to the verification information.
  • the second part of the data is generated according to the pre-stored predetermined card opening rules and the third part of the data.
  • the second part of the data is personalized when the user opens the card.
  • Data, where the personalization data includes personalization data generated by the server for the user in addition to the personalized data input by the user according to the UI thread.
  • step 408 the smart device sends a second data acquisition request to the server using the second background thread.
  • the second background thread Since the first background thread only pulls the first part of the data from the server, when the smart device needs When the second part of data is obtained, the second background thread needs to be used to send a second data acquisition request to the server.
  • step 409 the server receives the second data acquisition request.
  • the server may receive the second data acquisition request.
  • step 410 the server sends the second portion of data to the smart device.
  • the server may feed back, to the smart device, the second part of data related to the smart device card opening.
  • step 411 the smart device receives the second portion of data, and uses the second background thread to write the second portion of data into the SE chip.
  • Step 411 is similar to step 306. For details, refer to the description of step 306, and details are not described herein again.
  • the smart device writes the card to the SE chip by using the created first background thread in the process of implementing the related operations before the UI thread is opened.
  • Part of the data required so that when the UI thread completes the relevant operations before the card is opened, part of the data related to the card opening has been written to the SE chip, and in the last step, only the data that has not been written to the SE chip needs to be written.
  • the utility model can save the writing time required for writing part of the data related to the card opening of the SE chip during the related operation before the UI thread realizes the card opening, and solves the problem that the NFC device is used for opening the card in the related art. The problem of taking too long time reduces the time taken when opening an NFC device.
  • step 401, step 402, step 405, step 406, step 408, and step 411 can be separately implemented as a card-opening data writing method with the smart device as the execution subject;
  • step 403, step 404, step 407, and step 409 and step 410 can be separately implemented as a card-opening data writing method using a server as an execution subject.
  • FIG. 5A is a block diagram of an card-opening data writing device according to an exemplary embodiment. As shown in FIG. 5A, the card-opening data writing device is applied to the smart device 100 shown in FIG.
  • the data writing device includes but is not limited to: a first creating module 510, a first writing module 520, a second creating module 530, and a second writing module 540.
  • the first creating module 510 is configured to implement related operations before the card is opened by using the UI thread of the user interface. In the process of creating, create the first background thread.
  • the UI thread is a thread that performs related operations before the card is opened.
  • the UI thread is used to display pages related to card opening operations before card opening, related operations for executing these pages, and the like.
  • the smart device can usually install an application related to the instantiated NFC card, and use the application to create a UI thread, and the UI thread can interact with the server to obtain a page to be displayed and an execution page during the card opening process.
  • an application related to the instantiated NFC card and use the application to create a UI thread
  • the UI thread can interact with the server to obtain a page to be displayed and an execution page during the card opening process.
  • the common page includes a display page of the service terms related to the card opening, a personalized data input page related to the card opening, etc., and these pages may have an input box for guiding the user to input personalized data. And controls that guide the user to confirm or cancel the input of personalized data.
  • the UI thread receives an permission indication for instructing execution of the card opening, the first background thread is created.
  • the permission indication here generally means that the card-opening user allows the card to be opened, and the UI thread can continue to perform related operations before the card is opened.
  • the allowable indication means that the user is prepared to perform related operations before the card is opened according to the UI thread.
  • the UI thread in a common card opening process, usually displays the service terms related to the card opening obtained from the server. When the user agrees to the terms of service, it can be determined that the UI thread receives the indication for permission. The permission indication of the card is opened, and the first background thread can be created at this time.
  • the UI thread may display a prompt asking the user if he wishes to open the card.
  • the user confirms that he wishes to open the card, it may be determined that the UI thread receives the indication for allowing the card to be opened.
  • the indication is allowed, in which case the first background thread can be created.
  • the first background thread generally does not involve the display or operation of the UI interface. During the execution of the UI thread, it may run in parallel with the UI thread, or may run serially with the UI thread. During the serial running of the first background thread with the UI thread, since the UI thread may pause during the entire process of the operation, such as waiting for a user operation, the first background thread may run at an interval at which the UI thread stops running. However, from a macro perspective, the first background thread and the UI thread can still be regarded as a side-by-side relationship, that is, the first background thread can run simultaneously during the entire duration of the UI thread execution.
  • the first writing module 520 is configured to obtain the first part of data required for opening the card from the server by using the first background thread created by the first creating module 510, and write the first part of data into the SE chip.
  • the first part of the data is the data that needs to be written into the SE chip when the card is opened by the server.
  • the data is generally the preloaded data required for the card opening.
  • the first part of the data is usually not generated by the operation of the UI thread. Change.
  • the first part of the data is independent of the personalized data, and in order to make the identification of the NFC card after the instantiation, it is necessary to write data related to the user information to the SE chip, so that the NFC card has a unique identity, such data is generally This is called personalization data, that is, the second part of data mentioned below in this embodiment.
  • the second part of the data is usually the data related to the user information that needs to be written into the SE chip when the card is opened, and the second part of the data may be changed due to the operation of the UI thread. Since the user may need to input personalized data when using the UI thread, such as the user's phone number, identity information, recharge amount, etc., the user acquired by the UI thread when the user performs the relevant operation before the card is opened by the UI thread.
  • the input data may be different or partially different, so this data can be determined by the operation of the UI thread.
  • the personalized data may further include data allocated by the server for the card opening operation to uniquely identify the identity of the user.
  • the first part of the data may include data that interacts with the NFC radio unit, and may further include data for modifying the personalized data in the SE chip.
  • the data that needs to be written into the SE chip can be divided into a first part of data and a second part of data, wherein the first part of data is non-personalized data required for opening the card, and the second part of data is It is the personal data needed to open the card.
  • the first background thread When the first background thread writes the first part of data to the SE chip, it can be written in a predetermined manner, and the path written to the SE chip can also be preset.
  • the UI thread guides the user to input personalized data during the process of using the smart device to open the card, the UI thread takes a certain amount of time, and the duration is necessary in the card opening process. Obviously, during the execution of the UI thread, By using the first background thread to write the first part of data to the SE chip, the writing time of the user waiting for the thread to write the first part of data to the SE chip can be saved.
  • the second creating module 530 is configured to create a second background thread after completing the related operations before the card opening by using the UI thread and determining to open the card.
  • the UI thread After the UI thread is used to complete the related operations before the card is opened and the card is determined to be opened, it usually means that the user no longer modifies the personalized data. At this time, the second background thread can be created to implement the writing of the personalized data to the SE chip.
  • the second writing module 540 is configured to use the second background thread created by the second creating module 530 to write the second part of data required for the card opening into the SE chip, the first part of data and the second part of data. It is the data related to the card opening that needs to be written into the SE chip.
  • the second part of the data required to open the card is generally the data obtained in the related operations performed by the UI thread.
  • the second part of the data may also be obtained by the UI thread to perform related operations, and then synchronized to the server data, so that when implemented, the second background thread may be pulled from the server to the second required for card opening. part of data.
  • the server performs the audit, and after the audit is passed, the first part of the data is bound and stored.
  • the second background thread sends an acquisition request for obtaining the second part of data to the server, and the server feeds back the second part of the data passed by the server, and the second background thread writes the second part of the data acquired from the server into the SE chip.
  • the second background thread When the second background thread writes the second part of data to the SE chip, it can be written in a predetermined manner, and the path written to the SE chip can also be preset.
  • the first creating module 510 may be further configured to: when the UI thread is used to implement the related operation before the card opening, if the UI thread receives the permission indication for indicating that the card is allowed to be opened , then create the first background thread.
  • the second creation module 530 may include: a detection submodule 531, a first creation submodule 532, and a second creation submodule 533. See FIG. 5B. Shown.
  • the detecting submodule 531 is configured to detect whether the first background thread writes all of the first partial data into the SE chip.
  • the application releases the first background thread.
  • the first background thread When the first background thread has not been released, it can be determined that the first background thread has not written all the first part of data to the SE chip; when the first background thread has been released, it can be determined that the first background thread has already been The first part of the data is all written into the SE chip.
  • the first creating submodule 532 is configured to wait for the first background thread to continue writing the remaining first portion of data to the SE chip when the detecting submodule 531 detects that the first background thread has not written all of the first partial data into the SE chip. After the first part of the data is all written to the SE chip, a second background thread is created.
  • the second creation submodule 533 is configured to create a second background thread when the detection submodule 531 detects that the first background thread has written all of the first portion of data into the SE chip.
  • the second background thread writes the second part of the data to the second path of the SE chip, the first path and the second path are different. In this case, there is generally no write data error.
  • the second background thread can be created without waiting for the first background thread to be completely released.
  • the card data writing device may further include: a detecting module 550, a first display module 560, and a determining module 570.
  • the detecting module 550 is configured to detect whether the UI thread completes a related operation before the card is opened.
  • the related operations performed by the UI thread are known. Therefore, according to the related operations performed by the UI thread, it can be determined whether the UI thread completes the correlation before the card is opened. operating. That is to say, whether the UI thread has the condition for displaying the card opening control, so that the user can use the card opening control to determine the card opening.
  • the first display module 560 is configured to display the card opening control when the detecting module 550 detects that the UI thread completes the related operation before the card is opened;
  • the determining module 570 is configured to determine, when the card opening control displayed by the first display module 560 is triggered, that the related operation before the card opening is completed by the UI thread and to determine the card opening.
  • the attribute of the displayed card opening control is to allow the operation or allow the operation response.
  • the user can trigger the card opening control.
  • the UI thread can know that the card opening control is triggered.
  • the attributes of the opened card control are generally prohibited or prohibited, such as the common gray representation. In this case, even if the user triggers the open card control, the UI thread will not respond to the trigger operation.
  • the display card opening control described here refers to the card opening control whose display attribute is to allow operation or allow operation response.
  • the user triggers the card opening control it indicates that the user no longer modifies the data input of the interface involved in the UI thread, so at this time, it can be determined that the card opening is determined.
  • the card data writing device may further include: a second display module 580.
  • the second display module 580 is configured to display, after the first partial data and the second partial data are successfully written into the SE chip, prompt information for prompting the card issuance success.
  • the prompt information can be used to prompt the user to issue the card successfully, so that the user can use the NFC device instead of the practice card for use.
  • the NFC device can communicate with the NFC receiver using the NFC radio unit, and modify the data in the SE chip by using the communication information.
  • the SE chip in the NFC device includes data for indicating the remaining amount.
  • the NFC radio unit in the NFC device can learn the bus fee deductor. Informing the resource value that needs to be deducted, the NFC radio unit will notify the SE chip to modify the data indicating the remaining amount, and reduce the data by the resource value.
  • the card-opening data writing device needs to write a card to the SE chip by using the created first background thread in the process of implementing the related operations before the card is opened in the UI thread.
  • Part of the data so that when the UI thread completes the relevant operations before the card is opened, the partial data related to the card opening has been written to the SE chip, and only the data that has not been written to the SE chip can be written in the last step.
  • the utility model saves the writing time required for writing part of the data related to the card opening of the SE chip during the related operation process before the UI thread realizes the card opening, and solves the problem of using the NFC device for card opening in the related art. The problem of being too long reduces the time taken when opening an NFC device.
  • the UI thread implements the related operations before the card opening is complicated and diverse, in order to write the data required for the card opening to the SE chip as soon as possible, the UI thread can be created when the UI thread receives the permission indication for permitting the card opening.
  • the first background thread performs the data required to write the card to the SE chip, so that the UI thread can write data to the SE chip as early as possible during the operation of the UI thread to open the card, so as to minimize the time required to open the card. .
  • the problem that the data may be written when the two threads simultaneously write data to the SE chip is avoided.
  • FIG. 6A is a block diagram of an card-opening data writing device according to an exemplary embodiment. As shown in FIG. 6A, the card-opening data writing device is applied to a server, and the card-opening data writing device includes but not The method is limited to: a first transceiver module 610, an acquisition module 620, and a second transceiver module 630.
  • the first transceiver module 610 is configured to receive the first data acquisition request sent by the smart device, and send the first part of data required for the card opening to the smart device, where the first data acquisition request is that the smart device uses the user interface UI thread to implement the card opening.
  • the first background thread is created, the first part of the data is sent by the first background thread, and the first part of the data is used to trigger the smart device to write the first part of data into the SE element chip of the smart device in the smart device;
  • the obtaining module 620 is configured to obtain a second part of data required for the smart device to open the card;
  • the second transceiver module 630 is configured to receive the second data acquisition request sent by the smart device, and send the second part of the data acquired by the acquisition module 620 to the smart device, where the second data acquisition request is before the smart device completes the card opening by using the UI thread. After the related operation is performed and the second background thread is created, the second background thread is used to trigger the smart device to write the second part of data into the SE chip.
  • the obtaining module 620 may include: a receiving submodule 621 and a generating submodule 622, as shown in FIG. 6B.
  • the receiving sub-module 621 is configured to receive the third partial data sent by the smart device, where the third partial data is generated by the smart device by using the UI thread.
  • the generating submodule 622 is configured to generate the second partial data according to the predetermined card opening rule and the third partial data received by the receiving submodule 621.
  • the UI thread prompts the user to input personalized data related to the card opening, and verification information related to the card opening, etc., and the personalized data and the verification information can be sent to the server as the third part of the data.
  • the server may perform verification according to the verification information.
  • the second part of the data is generated according to the pre-stored predetermined card opening rules and the third part of the data.
  • the second part of the data is personalized when the user opens the card.
  • Data, where the personalization data includes personalization data generated by the server for the user in addition to the personalized data input by the user according to the UI thread.
  • the first part of the data is the non-personalized data required for opening the card
  • the second part of the data is the personalized data required for opening the card
  • the card-opening data writing device receives intelligence through The first data acquisition request of the device sends the first part of the data related to the card opening to the smart device, so that the smart device has written the part related to the card opening to the SE chip when the UI thread completes the related operation before the card is opened.
  • Data in the last step, only need to write data that has not been written to the SE chip, which saves some data related to the card opening that is written to the SE chip during the related operation before the UI thread realizes the card opening.
  • the required writing duration solves the problem that the NFC device takes too long to open the card in the related art, and reduces the time taken when the NFC device is used for card opening.
  • FIG. 7 is a block diagram of an open card data writing system including a smart device 710 and a server 720, according to an exemplary embodiment.
  • the smart device 710 may include the card opening data writing device as shown in FIG. 5A and FIG. 5B, and the description of FIG. 5A and FIG. 5B may be specifically omitted, and details are not described herein again.
  • the server 720 may include the card-opening data writing device as shown in FIG. 6A and FIG. 6B, and the description of FIG. 6A and FIG. 6B may be specifically omitted, and details are not described herein again.
  • the smart device writes the card to the SE chip by using the created first background thread in the process of implementing the related operations before the UI thread is opened.
  • Part of the data required so that when the UI thread completes the relevant operations before the card is opened, part of the data related to the card opening has been written to the SE chip, and in the last step, only the data that has not been written to the SE chip needs to be written.
  • the utility model can save the writing time required for writing part of the data related to the card opening of the SE chip during the related operation before the UI thread realizes the card opening, and solves the problem that the NFC device is used for opening the card in the related art. The problem of taking too long time reduces the time taken when opening an NFC device.
  • An exemplary embodiment of the present disclosure provides a card-opening data writing device, which can implement the card-opening data writing method provided by the present disclosure, and the card-opening data writing device is applied to the smart device 100 shown in FIG.
  • the card opening data writing device may include: a processor, a memory for storing processor executable instructions;
  • processor is configured to:
  • the first background line is created.
  • the second background thread is created, and the second background thread is used to write the second part of data required for the card opening into the SE chip, and the first part of the data is The second part of the data is the data related to the card opening that needs to be written into the SE chip.
  • Another exemplary embodiment of the present disclosure provides an card opening data writing apparatus capable of implementing the card opening data writing method provided by the present disclosure, the card opening data writing apparatus is applied to a server, and the card opening data is written.
  • the apparatus can include: a processor, a memory for storing processor executable instructions;
  • processor is configured to:
  • Receiving a first data acquisition request sent by the smart device and sending, to the smart device, a first part of data required for opening the card, where the first data acquisition request is related to the smart device before using the user interface UI thread to implement card opening
  • the first background thread is created, the first part of the data is sent by the first background thread, and the first part of data is used to trigger the smart device to write the first part of data into the security element SE of the smart device.
  • the second part of the data is sent by the second background thread, and the second part of data is used to trigger the smart device to write the second part of data into the SE chip. in.
  • FIG. 8 is a block diagram of an card opening data writing apparatus according to still another exemplary embodiment.
  • device 800 can be a smart device that includes an SE chip, such as a common mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, and the like.
  • SE chip such as a common mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, and the like.
  • apparatus 800 can include one or more of the following components: processing component 802, memory 804, power component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, and Communication component 816.
  • Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 802 can include one or more processors 818 to execute instructions to perform all or part of the steps described above.
  • processing component 802 can include one or more modules to facilitate interaction between component 802 and other components.
  • processing component 802 can include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.
  • Memory 804 is configured to store various types of data to support operation at device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 804 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Electrically erasable programmable read only memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • Power component 806 provides power to various components of device 800.
  • Power component 806 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 800.
  • the multimedia component 808 includes a screen between the device 800 and the user that provides an output interface.
  • the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can sense not only the boundaries of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 808 includes a front camera and/or a rear camera. When the device 800 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 810 is configured to output and/or input an audio signal.
  • the audio component 810 includes a microphone (MIC) that is configured to receive an external audio signal when the device 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal may be further stored in memory 804 or transmitted via communication component 816.
  • the audio component 810 also includes a speaker for outputting an audio signal.
  • the I/O interface 812 provides an interface between the processing component 802 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 814 includes one or more sensors for providing device 800 with a status assessment of various aspects.
  • sensor assembly 814 can detect an open/closed state of device 800, a relative positioning of components, such as a display and a keypad of device 800, and sensor component 814 can also detect a change in position of a component of device 800 or device 800, the user The presence or absence of contact with device 800, device 800 orientation or acceleration/deceleration and temperature variation of device 800.
  • Sensor assembly 814 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 814 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 816 is configured to facilitate wired or wireless communication between device 800 and other devices.
  • the device 800 can access a wireless network based on a communication standard, such as Wi-Fi, 2G or 3G, or a combination thereof.
  • communication component 816 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • communication component 816 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the device 800 further includes an SE chip (not shown) connected to the NFC module, and the SE chip communicates with the external device through the NFC module.
  • the SE chip can also communicate with the network side device through a communication module of other communication means (such as Wi-Fi, 2G or 3G) in the communication component 816.
  • device 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the above described card opening data writing method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor or other electronic component implementation for performing the above described card opening data writing method.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 804 comprising instructions executable by processor 818 of apparatus 800 to perform the above described card opening data writing method .
  • the non-transitory computer readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.
  • FIG. 9 is a block diagram of an card opening data writing apparatus according to still another exemplary embodiment.
  • device 900 can be provided as a network side device, such as a server.
  • apparatus 900 includes a processing component 902 that further includes one or more processors, and memory resources represented by memory 904 for storing instructions executable by processing component 902, such as an application.
  • An application stored in memory 904 can include one or more modules each corresponding to a set of instructions.
  • processing component 902 is configured to execute instructions to perform the card opening data writing method described above.
  • Device 900 may also include a power supply component 906 configured to perform power management of device 900, a wired or wireless network interface 908 configured to connect device 900 to the network, and an input/output (I/O) interface 910.
  • the device 900 can operate based on an operating system stored in the memory 904, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Finance (AREA)
  • Computer Security & Cryptography (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Computer Hardware Design (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种开卡数据写入方法、装置及系统，属于计算机技术领域。所述开卡数据写入方法包括：在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程（201）；利用所述第一后台线程从服务器获取开卡所需要的第一部分数据，将所述第一部分数据写入SE芯片中（202）；在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程，利用所述第二后台线程将开卡所需要的第二部分数据写入所述SE芯片中（203）。解决了相关技术中利用NFC设备进行开卡时耗时过长的问题，降低了利用NFC设备进行开卡时的耗时。

Description

开卡数据写入方法、装置及系统
本申请基于申请号为201610466532.3、申请日为2016年6月23日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及计算机技术领域，特别涉及一种开卡数据写入方法、装置及系统。
背景技术
随着近场通讯(英文：near field communication，NFC)技术及智能设备的迅速发展，NFC设备的卡模拟功能在移动支付及公交卡等领域已日渐成熟。
NFC设备上的安全元件(英文：secure dlement，SE)具有自己的计算能力，在卡模拟应用中，NFC设备通过离线预置或者是网络发卡的形式在SE中写入卡模拟时需要的卡数据，以实现卡模拟的功能。常见的一种将卡数据写入SE的方式是：NFC设备上安装有对应的应用程序(英文：application，App)，在利用App开卡的过程中，NFC设备需要多次执行与服务器之间的交互操作，等相关的交互操作完成后，最后从服务器获取开卡需要的数据，将获取的数据一次性写入SE芯片中，由于交互操作过程以及数据写入的过程均需要较长的时间，因此导致利用NFC设备进行开卡时耗时过长。
发明内容
本公开提供一种开卡数据写入方法、装置及系统。所述技术方案如下：
根据本公开实施例的第一方面，提供一种开卡数据写入方法，应用于包含有SE芯片的智能设备中，所述方法包括：在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程；利用所述第一后台线程从服务器获取开卡所需要的第一部分数据，将所述第一部分数据写入所述SE芯片中；在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程，利用所述第二后台线程将开卡所需要的第二部分数据写入所述SE芯片中，所述第一 部分数据和所述第二部分数据是需要写入SE芯片中的与开卡相关的数据。
通过在UI线程实现开卡前的相关操作的过程中，即利用创建的第一后台线程向SE芯片写入开卡需要的部分数据，从而使得在UI线程完成开卡前的相关操作时，已经向SE芯片写入了开卡相关的部分数据，在最后一步仅需要写入尚未被写入至SE芯片的数据即可，节省了在UI线程实现开卡前的相关操作过程中，被写入至SE芯片的与开卡相关的部分数据所需要的写入时长，解决了相关技术中利用NFC设备进行开卡时耗时过长的问题，降低了利用NFC设备进行开卡时的耗时。
可选的，所述在利用UI线程实现开卡前的相关操作的过程中，创建第一后台线程，包括：在利用所述UI线程实现开卡前的相关操作的过程中，若所述UI线程接收到用于指示允许开卡的允许指示，则创建所述第一后台线程。由于UI线程实现开卡前的相关操作较为复杂和多样，因此为了尽快的向SE芯片写入开卡需要的数据，可以在UI线程接收到用于指示允许开卡的允许指示时，创建第一后台线程，以执行向SE芯片写入开卡需要的数据，从而使得在UI线程实现开卡的相关操作过程中，能尽量早的向SE芯片写入数据，以尽量减少开卡耗时。
可选的，所述创建第二后台线程，包括：检测所述第一后台线程是否将所述第一部分数据全部写入所述SE芯片中；若所述第一后台线程尚未将所述第一部分数据全部写入所述SE芯片中，则等待所述第一后台线程继续将剩余的所述第一部分数据写入所述SE芯片，在将所述第一部分数据全部写入所述SE芯片后，创建所述第二后台线程；若所述第一后台线程已将所述第一部分数据全部写入所述SE芯片中，则创建所述第二后台线程。通过在判定第一后台线程将第一部分数据全部写入了SE芯片之后，再创建第二后台线程，避免了在利用两个线程同时向SE芯片写入数据时可能出错的问题。
可选的，所述方法还包括：检测所述UI线程是否完成开卡前的相关操作；若所述UI线程完成了开卡前的相关操作，则显示开卡控件；在所述开卡控件被触发时，判定利用所述UI线程完成了开卡前的相关操作且确定开卡。为了避免开卡前的相关操作发生了漏操作，需要在确定UI线程完成了开卡前的相关操作后显示开卡控件，以便于执行最后向UE芯片写入剩余数据的操作。
可选的，所述方法还包括：在所述第一部分数据和所述第二部分数据均被 成功写入所述SE芯片后，显示用于提示发卡成功的提示信息。
可选的，所述第一部分数据是开卡所需要的非个人化数据，所述第二部分数据是开卡所需要的个人化数据。由于非个人化数据是实例化卡时必须写入至SE芯片的数据，这些数据不受UI线程操作的影响，因此可以在UI线程执行开卡前的相关操作的过程中，将非个人化数据写入SE芯片，然后在UI线程完成了开卡前的相关操作时，将个人化数据写入SE芯片，从而保证了开卡时SE芯片中数据的正确性。
根据本公开实施例的第二方面，提供一种开卡数据写入方法，应用于服务器中，所述方法包括：接收智能设备发送的第一数据获取请求，向所述智能设备发送开卡所需要的第一部分数据，所述第一数据获取请求是所述智能设备在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程后，利用所述第一后台线程发送的，所述第一部分数据用于触发所述智能设备将所述第一部分数据写入所述智能设备中安全元件SE芯片中；获取所述智能设备开卡所需要的第二部分数据；接收所述智能设备发送的第二数据获取请求，向所述智能设备发送所述第二部分数据，所述第二数据获取请求是所述智能设备在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程后，利用所述第二后台线程发送的，所述第二部分数据用于触发所述智能设备将所述第二部分数据写入所述SE芯片中。
通过在接收到智能设备的第一数据获取请求时向智能设备发送与开卡相关的第一部分数据，从而使得智能设备在UI线程完成开卡前的相关操作时，已经向SE芯片写入了与开卡相关的部分数据，在最后一步仅需要写入尚未被写入至SE芯片的数据即可，节省了在UI线程实现开卡前的相关操作过程中，写入至SE芯片的与开卡相关的部分数据所需要的写入时长，解决了相关技术中利用NFC设备进行开卡时耗时过长的问题，降低了利用NFC设备进行开卡时的耗时。
可选的，所述获取所述智能设备开卡所需要的第二部分数据，包括：接收所述智能设备发送的第三部分数据，所述第三部分数据是所述智能设备利用所述UI线程产生的；根据预定开卡规则以及所述第三部分数据生成所述第二部分数据。
可选的，所述第一部分数据是开卡所需要的非个人化数据，所述第二部分数据是开卡所需要的个人化数据。
根据本公开实施例的第三方面，提供一种开卡数据写入装置，应用于包含有SE芯片的智能设备中，所述装置包括：第一创建模块，被配置为在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程；第一写入模块，被配置为利用所述第一创建模块创建的所述第一后台线程从服务器获取开卡所需要的第一部分数据，将所述第一部分数据写入所述SE芯片中；第二创建模块，被配置为在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程；第二写入模块，被配置为利用所述第二创建模块创建的所述第二后台线程将开卡所需要的第二部分数据写入所述SE芯片中，所述第一部分数据和所述第二部分数据是需要写入SE芯片中的与开卡相关的数据。
可选的，所述第一创建模块，还被配置为：在利用所述UI线程实现开卡前的相关操作的过程中，若所述UI线程接收到用于指示允许开卡的允许指示，则创建所述第一后台线程。
可选的，所述第二创建模块，包括：检测子模块，被配置为检测所述第一后台线程是否将所述第一部分数据全部写入所述SE芯片中；第一创建子模块，被配置为在所述检测子模块检测到所述第一后台线程尚未将所述第一部分数据全部写入所述SE芯片中时，等待所述第一后台线程继续将剩余的所述第一部分数据写入所述SE芯片，在将所述第一部分数据全部写入所述SE芯片后，创建所述第二后台线程；第二创建子模块，被配置为在所述检测子模块检测到所述第一后台线程已将所述第一部分数据全部写入所述SE芯片中时，创建所述第二后台线程。
可选的，所述装置还包括：检测模块，被配置为检测所述UI线程是否完成开卡前的相关操作；第一显示模块，被配置为在所述检测模块检测到所述UI线程完成了开卡前的相关操作时，显示开卡控件；判定模块，被配置为在所述第一显示模块显示的所述开卡控件被触发时，判定利用所述UI线程完成了开卡前的相关操作且确定开卡。
可选的，所述装置还包括：第二显示模块，被配置为在所述第一部分数据和所述第二部分数据均被成功写入所述SE芯片后，显示用于提示发卡成功的提示信息。
可选的，所述第一部分数据是开卡所需要的非个人化数据，所述第二部分数据是开卡所需要的个人化数据。
根据本公开实施例的第四方面，提供一种开卡数据写入装置，应用于服务器中，所述装置包括：第一收发模块，被配置为接收智能设备发送的第一数据获取请求，向所述智能设备发送开卡所需要的第一部分数据，所述第一数据获取请求是所述智能设备在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程后，利用所述第一后台线程发送的，所述第一部分数据用于触发所述智能设备将所述第一部分数据写入所述智能设备中安全元件SE芯片中；获取模块，被配置为获取所述智能设备开卡所需要的第二部分数据；第二收发模块，被配置为接收所述智能设备发送的第二数据获取请求，向所述智能设备发送所述获取模块获取的所述第二部分数据，所述第二数据获取请求是所述智能设备在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程后，利用所述第二后台线程发送的，所述第二部分数据用于触发所述智能设备将所述第二部分数据写入所述SE芯片中。
可选的，所述获取模块，包括：接收子模块，被配置为接收所述智能设备发送的第三部分数据，所述第三部分数据是所述智能设备利用所述UI线程产生的；生成子模块，被配置为根据预定开卡规则以及所述接收子模块接收到的所述第三部分数据生成所述第二部分数据。
可选的，所述第一部分数据是开卡所需要的非个人化数据，所述第二部分数据是开卡所需要的个人化数据。
根据本公开实施例的第五方面，提供一种开卡数据写入系统，所述系统包括智能设备和服务器，所述智能设备包括如第三方面和第三方面各种可选实现方式中任一所述的开卡数据写入装置，所述服务器包括如第四方面和第四方面各种可选实现方式中任一所述的开卡数据写入装置。
根据本公开实施例的第六方面，提供一种开卡数据写入装置，应用于包含有SE芯片的智能设备中，所述装置包括：
处理器；
用于存储所述处理器可执行指令的存储器；
其中，所述处理器被配置为：
在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程；
利用所述第一后台线程从服务器获取开卡所需要的第一部分数据，将所述 第一部分数据写入所述SE芯片中；
在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程，利用所述第二后台线程将开卡所需要的第二部分数据写入所述SE芯片中，所述第一部分数据和所述第二部分数据是需要写入SE芯片中的与开卡相关的数据。
根据本公开实施例的第七方面，提供一种开卡数据写入装置，应用于服务器中，所述装置包括：
处理器；
用于存储所述处理器可执行指令的存储器；
其中，所述处理器被配置为：
接收智能设备发送的第一数据获取请求，向所述智能设备发送开卡所需要的第一部分数据，所述第一数据获取请求是所述智能设备在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程后，利用所述第一后台线程发送的，所述第一部分数据用于触发所述智能设备将所述第一部分数据写入所述智能设备中安全元件SE芯片中；
获取所述智能设备开卡所需要的第二部分数据；
接收所述智能设备发送的第二数据获取请求，向所述智能设备发送所述第二部分数据，所述第二数据获取请求是所述智能设备在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程后，利用所述第二后台线程发送的，所述第二部分数据用于触发所述智能设备将所述第二部分数据写入所述SE芯片中。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并于说明书一起用于解释本公开的原理。
图1是根据一示例性实施例示出的智能设备的结构示意图；
图2是根据一示例性实施例示出的一种开卡数据写入方法的流程图；
图3A是根据另一示例性实施例示出的一种开卡数据写入方法的流程图；
图3B是根据一示例性实施例示出的创建第二后台线程时的流程图；
图3C和3D是根据一示例性实施例示出的两种开卡过程中各流程使用时长的示意图；
图4是根据再一示例性实施例示出的一种开卡数据写入方法的流程图；
图5A是根据一示例性实施例示出的一种开卡数据写入装置的框图；
图5B是根据另一示例性实施例示出的一种开卡数据写入装置的框图；
图6A是根据再一示例性实施例示出的一种开卡数据写入装置的框图；
图6B是根据再一示例性实施例示出的一种开卡数据写入装置的框图；
图7是根据一示例性实施例示出的一种开卡数据写入系统的框图；
图8是根据再一示例性实施例示出的一种开卡数据写入装置的框图；
图9是根据再一示例性实施例示出的一种开卡数据写入装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
图1是根据一示例性实施例示出的智能设备的结构示意图，如图1所示，该智能设备100至少可以包括SE芯片120和NFC射频单元140。
为了能够实现对实体卡的模拟，SE芯片120用于存储模拟实体卡时实体卡中需要存储的数据，SE芯片120具备运算能力，可以对存储的数据进行修改。
NFC射频单元140具备射频通信功能，其可以通过射频技术与外界NFC通信设备进行通信。
SE芯片120可以与NFC射频单元140进行信息交互，SE芯片120将需要发送出的数据通过NFC射频单元140进行发送，NFC射频单元140可以将接收到的数据发送至SE芯片120，由SE芯片120进行运算或修改存储的数据。
该智能设备100还可以包括其他通信单元160，该其他通信单元160可以与网络侧设备(比如服务器)进行通信，SE芯片120通过其他通信单元160与网 络侧设备进行数据交互。
在利用智能设备100模拟NFC卡(比如常见的公交卡、银行卡)时，通常需要智能设备100具备SE芯片120和NFC射频单元140，SE芯片120用于存储模拟实体卡时需要的数据，NFC射频单元140与SE芯片120结合实现NFC卡的功能。具备上述SE芯片120和NFC射频单元140的智能设备100也可以称为NFC设备。
下述各个实施例均基于图1结构的智能设备实现开卡的功能。
图2是根据一示例性实施例示出的一种开卡数据写入方法的流程图，如图2所示，该开卡数据写入方法应用于图1所示的智能设备100中，包括以下步骤。
在步骤201中，在利用UI线程实现开卡前的相关操作的过程中，创建第一后台线程。
UI线程是执行开卡前相关操作的线程，一般的，UI线程用于显示开卡前与开卡相关操作的页面、执行这些页面的相关操作等。
在实际应用中，智能设备通常可以安装与实例化NFC卡相关的应用程序，利用该应用程序创建UI线程，该UI线程可以与服务器进行交互，以获取开卡过程中需要显示的页面以及执行页面所提供的相关操作。
比如，在开卡过程中，常见与开卡相关的页面包括显示的与开卡相关的服务条款的显示页面、开卡相关的个人化数据输入页面等，这些页面上可以有引导用户输入个人化数据的输入框以及引导用户确认或取消输入个人化数据的控件等。
在步骤202中，利用第一后台线程从服务器获取开卡所需要的第一部分数据，将第一部分数据写入SE芯片中。
在步骤203中，在利用UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程，利用第二后台线程将开卡所需要的第二部分数据写入SE芯片中，第一部分数据和第二部分数据是需要写入SE芯片中的与开卡相关的数据。
第一部分数据是服务器提供的开卡时需要写入SE芯片中的数据，第一部分数据一般是开卡所需要的预加载数据，第一部分数据通常不会因UI线程的操作而发生变化。
第二部分数据是开卡时需要写入SE芯片中的数据，第二部分数据可能会因 UI线程的操作而发生变化。
综上所述，本公开实施例中提供的开卡数据写入方法，通过在UI线程实现开卡前的相关操作的过程中，即利用创建的第一后台线程向SE芯片写入开卡需要的部分数据，从而使得在UI线程完成开卡前的相关操作时，已经向SE芯片写入了开卡相关的部分数据，在最后一步仅需要写入尚未被写入至SE芯片的数据即可，节省了在UI线程实现开卡前的相关操作过程中，被写入SE芯片的与开卡相关的部分数据时所需要的写入时长，解决了相关技术中利用NFC设备进行开卡时耗时过长的问题，降低了利用NFC设备进行开卡时的耗时。
图3A是根据另一示例性实施例示出的一种开卡数据写入方法的流程图，如图3所示，该开卡数据写入方法应用于图1所示的智能设备100中，包括以下步骤。
在步骤301中，在利用UI线程实现开卡前的相关操作的过程中，创建第一后台线程。
UI线程是执行开卡前相关操作的线程，一般的，UI线程用于显示开卡前与开卡相关操作的页面、执行这些页面的相关操作等。
在实际应用中，智能设备通常可以安装与实例化NFC卡相关的应用程序，利用该应用程序创建UI线程，该UI线程可以与服务器进行交互，以获取开卡过程中需要显示的页面以及执行页面所提供的相关操作。
比如，在开卡过程中，常见的页面包括显示的与开卡相关的服务条款的显示页面、开卡相关的个人化数据输入页面等，这些页面上可以有引导用户输入个人化数据的输入框以及引导用户确认或取消输入个人化数据的控件等。
可选的，智能设备在利用UI线程实现开卡前的相关操作的过程中，若UI线程接收到用于指示允许开卡的允许指示，则创建第一后台线程。
这里的允许指示一般意味着开卡用户允许开卡，此时UI线程可以继续执行开卡前的相关操作。换句话说，允许指示意味着用户准备根据UI线程执行开卡前的相关操作。
比如，在一种常见的开卡流程中，UI线程通常会先显示从服务器获取的与开卡相关的服务条款事项，当用户同意服务条款事项时，则可以判定UI线程接收到用于指示允许开卡的允许指示，此时则可以创建第一后台线程。
还比如，在另一种常见的开卡流程中，UI线程可能会显示询问用户是否希望开卡的提示，当用户确认希望开卡时，则可以判定UI线程接收到用于指示允许开卡的允许指示，此时则可以创建第一后台线程。
第一后台线程一般不涉及UI界面的显示或操作，其在UI线程执行的过程中，可以与UI线程并列运行，也可以与UI线程串行运行。第一后台线程在与UI线程串行运行的过程中，由于UI线程在操作的整个流程可能会暂停运行，比如等待用户操作时，因此第一后台线程可以在UI线程停止运行的间隔运行。但从宏观角度看，第一后台线程与UI线程仍旧可以看成是并列运行的关系，也即在UI线程执行的整个时长内，第一后台线程可以同时运行。
在步骤302中，利用第一后台线程从服务器获取开卡所需要的第一部分数据，将第一部分数据写入SE芯片中。
第一部分数据是服务器提供的开卡时需要写入SE芯片中的数据，这些数据一般是开卡所需要的预加载数据，第一部分数据通常不会因UI线程的操作而发生变化。
也就是说，第一部分数据与个人化数据无关，而为了使得实例化后NFC卡的辨识，需要向SE芯片写入与用户信息相关的数据，以使得NFC卡具备唯一的身份，这类数据一般称为个人化数据，也即本实施例中下面提及的第二部分数据。
第二部分数据通常是开卡时需要写入SE芯片中的与用户信息相关的数据，第二部分数据可能会因UI线程的操作而发生变化。由于在利用UI线程操作时可能需要用户输入个人化数据，比如用户的电话号码、身份信息、充值金额等，因此不同用户在利用UI线程执行开卡前的相关操作时，UI线程获取到的用户输入的数据可能全部或部分不同，因此这些数据可以由UI线程的操作而决定。
可选的，个人化数据还可以包括服务器为开卡操作分配的用于唯一标识用户身份的数据。
可选的，第一部分数据可以包括与NFC射频单元交互的数据，还可以包括用于修改SE芯片中个人化数据的数据。
为了进行上述数据的区分，可以将开卡需要写入SE芯片中的数据分为第一部分数据和第二部分数据，其中，第一部分数据是开卡所需要的非个人化数据，第二部分数据是开卡所需要的个人化数据。
第一后台线程在向SE芯片写入第一部分数据时，可以通过预定的方式写入，写入至SE芯片的路径也可以是预先设定的。
由于在利用智能设备开卡的过程中，UI线程引导用户输入个人化数据，因此UI线程会占用一定的时长，且该时长是开卡流程中必须占用的，很显然，在UI线程执行期间，利用第一后台线程将第一部分数据写入SE芯片，可以节省用户后期等待线程将第一部分数据写入SE芯片的写入时间。
在步骤303中，检测UI线程是否完成开卡前的相关操作。
一般的，当应用程序利用UI线程执行开卡前的相关操作时，UI线程执行的相关操作是已知的，因此，根据UI线程执行的相关操作即可判定UI线程是否完成开卡前的相关操作。也就是说，UI线程是否具备显示开卡控件的条件，以促使用户利用开卡控件确定开卡。
在步骤304中，若UI线程完成了开卡前的相关操作，则显示开卡控件，在开卡控件被触发时，判定利用UI线程完成了开卡前的相关操作且确定开卡。
一般的，当UI线程完成了开卡前的相关操作，显示的开卡控件的属性为允许操作或允许操作响应。这种情况下，用户可以触发该开卡控件，当用户触发该开卡控件时，UI线程可以得知该开卡控件被触发。
而当线程未完成开卡前的相关操作，则显示的开卡控件的属性一般为禁止操作或禁止操作响应，比如常见的以灰色形式表示。这种情况下，即使用户触发了该开卡控件，UI线程仍然不会对该触发操作进行响应。
这里所讲的显示开卡控件是指显示属性为允许操作或允许操作响应的开卡控件。
当用户触发开卡控件，表明用户不再修改UI线程中所涉及界面的数据输入，因此此时则可以判定确定开卡。
在步骤305中，在利用UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程。
在利用UI线程完成开卡前的相关操作且确定开卡后，通常意味着用户不再修改个人化数据，此时则可以创建第二后台线程，实现个人化数据向SE芯片的写入。
然而，由于已经建立了第一后台线程向SE芯片写入第一部分数据，如果该第一部分数据尚未写完，且第一后台线程和第二后台线程同时向SE芯片写入数 据，则可能出现数据写入错误，为了避免这种情况，智能设备在利用应用程序创建第二后台线程时，可以参见图3B中所示的步骤。
在步骤305a中，检测第一后台线程是否将第一部分数据全部写入SE芯片中。
一般的，当第一后台线程将第一部分数据全部写入SE芯片，则应用程序会释放掉该第一后台线程。
当第一后台线程尚未被释放掉时，则可以判定第一后台线程尚未将第一部分数据全部写入SE芯片；当第一后台线程已经被释放掉时，则可以判定第一后台线程尚已经将第一部分数据全部写入SE芯片中。
在步骤305b中，若第一后台线程尚未将第一部分数据全部写入SE芯片中，则等待第一后台线程继续将剩余的第一部分数据写入SE芯片，在将第一部分数据全部写入SE芯片后，创建第二后台线程。
若第一后台线程尚未将第一部分数据全部写入SE芯片中，则等待第一后台线程继续将剩余的第一部分数据写入SE芯片，直到第一后台线程被释放，此时则可以创建第二后台线程。
在步骤305c中，若第一后台线程已将第一部分数据全部写入SE芯片中，则创建第二后台线程。
可替换地，如果第一后台线程将第一部分数据写入SE芯片的第一路径下，第二后台线程将第二部分数据写入SE芯片的第二路径下，第一路径和第二路径不同，这种情况下，一般不会出现写入数据错误，此时在创建第二后台线程时，可以不用等到第一后台线程完全释放，即可创建第二后台线程。
在步骤306中，利用第二后台线程将开卡所需要的第二部分数据写入SE芯片中。
开卡所需要的第二部分数据一般由UI线程执行的相关操作中得到的数据。
可选的，第二部分数据也可以是先由UI线程执行相关操作得到，然后被同步到服务器的数据，这样在实现时，第二后台线程则可以从服务器拉取到开卡需要的第二部分数据。
举例来讲，利用UI线程获得的第二部分数据被同步至服务器后，由服务器进行审核，并在审核通过后，与第一部分数据进行绑定存储。第二后台线程向服务器发送获取第二部分数据的获取请求，服务器反馈审核通过的第二部分数 据，第二后台线程将从服务器获取到的第二部分数据写入SE芯片中。
第二后台线程在向SE芯片写入第二部分数据时，可以通过预定的方式写入，写入至SE芯片的路径也可以是预先设定的。
在步骤307中，在第一部分数据和第二部分数据均被成功写入该SE芯片后，显示用于提示发卡成功的提示信息。
提示信息可以用于提示用户发卡成功，这样用户则可以利用NFC设备代替实务卡进行使用。
在发卡成功之后，NFC设备可以利用NFC射频单元与NFC接收器进行通信，利用通信信息修改SE芯片中的数据。
以模拟公交卡的NFC设备为例，NFC设备中的SE芯片中包含用于指示剩余金额的数据，当NFC设备靠近公交费用扣除器时，则NFC设备中的NFC射频单元可以获知公交费用扣除器告知的需要扣除的资源值，NFC射频单元会通知SE芯片修改指示剩余金额的数据，将该数据减少该资源值。
通过上述开卡流程，如果利用第一后台线程写入第一部分数据的时长短于UI线程执行开卡前的相关操作的时长，且创建UI线程后预定时长△t后创建第一后台线程，则开卡使用的总时长为UI线程执行开卡前的相关操作的时长加上利用第二后台线程写入第二部分数据的时长。如图3C所示，t1为UI线程执行开卡前的相关操作的时长，t2为利用第一后台线程写入第一部分数据的时长，创建UI线程后预定时长△t后创建第一后台线程，t3为利用第二后台线程写入第二部分数据的时长，t2小于t1，此时开卡使用的总时长为t1+t3。
而如果利用第一后台线程写入第一部分数据的时长长于UI线程执行开卡前的相关操作的时长，且创建UI线程后预定时长△t后创建第一后台线程，则开卡使用的总时长为利用第一后台线程写入第一部分数据的时长加上利用第二后台线程写入第二部分数据的时长。如图3D所示，t1为UI线程执行开卡前的相关操作的时长，t2为利用第一后台线程写入第一部分数据的时长，创建UI线程后预定时长△t后创建第一后台线程，t3为利用第二后台线程写入第二部分数据的时长，t2大于t1，此时开卡使用的总时长为△t+t2+t3，△t小于t1。
很显然，不论图3C还是图3D，开卡使用的总时长均小于常规的开卡使用总时长t1+t2+t3。
综上所述，本公开实施例中提供的开卡数据写入方法，通过在UI线程实现 开卡前的相关操作的过程中，即利用创建的第一后台线程向SE芯片写入开卡需要的部分数据，从而使得在UI线程完成开卡前的相关操作时，已经向SE芯片写入了开卡相关的部分数据，在最后一步仅需要写入尚未被写入至SE芯片的数据即可，节省了在UI线程实现开卡前的相关操作过程中，被写入SE芯片的与开卡相关的部分数据时所需要的写入时长，解决了相关技术中利用NFC设备进行开卡时耗时过长的问题，降低了利用NFC设备进行开卡时的耗时。
另外，由于UI线程实现开卡前的相关操作较为复杂和多样，因此为了尽快的向SE芯片写入开卡需要的数据，可以在UI线程接收到用于指示允许开卡的允许指示时，创建第一后台线程，以执行向SE芯片写入开卡需要的数据，从而使得在UI线程实现开卡的相关操作过程中，能尽量早的向SE芯片写入数据，以尽量减少开卡耗时。
通过在判定第一后台线程将第一部分数据全部写入了SE芯片之后，再创建第二后台线程，避免了在利用两个线程同时向SE芯片写入数据时可能出错的问题。
为了避免开卡前的相关操作发生了漏操作，需要在确定UI线程完成了开卡前的相关操作后显示开卡控件，以便于执行最后向UE芯片写入剩余数据的操作。
在实际应用中，由于第一部分数据是智能设备利用第一后台线程写入的，第二部分数据是智能设备通过第二后台线程写入的，因此针对提供的第一部分数据和第二部分数据，服务器也会有对应改进，下面通过图4中的步骤对开卡过程中智能设备与服务器的实现过程进行解释说明。
图4是根据再一示例性实施例示出的一种开卡数据写入方法的流程图，该开卡数据写入方法包括如下步骤。
在步骤401中，智能设备在利用UI线程实现开卡前的相关操作的过程中，创建第一后台线程。
步骤401与步骤301类似，具体可以参见对步骤301的描述，这里就不再赘述。
在步骤402中，智能设备利用第一后台线程向服务器发送第一数据获取请求。
当智能设备建立第一后台线程后，为了能够获取与开卡相关的第一部分数据，智能设备可以利用第一后台线程向服务器发送第一数据获取请求。
在步骤403中，服务器接收该第一数据获取请求。
当智能设备向服务器发送第一数据获取请求后，对应的，服务器可以接收到第一数据获取请求。
在步骤404中，服务器向该智能设备反馈开卡所需要的第一部分数据。
当服务器接收到智能设备发送的第一数据获取请求之后，则可以向该智能设备反馈开卡所需要的第一部分数据。这里第一部分数据的解释可以参见步骤302中对第一部分数据的解释。
在步骤405中，智能设备接收该第一部分数据，利用第一后台线程将该第一部分数据写入SE芯片中。
步骤405与步骤302类似，具体可以参见对步骤302的描述，这里就不再赘述。
在步骤406中，智能设备在利用UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程。
步骤406可以通过步骤303至步骤305或者通过步骤305来实现，具体可以参见对步骤303至步骤305的描述，这里就不再赘述。
在步骤407中，服务器获取该智能设备开卡所需要的第二部分数据。
服务器在获取该智能设备开卡所需要的第二部分数据时，可以接收智能设备发送的第三部分数据，该第三部分数据是该智能设备利用该UI线程产生的，根据预定开卡规则以及该第三部分数据生成该第二部分数据。
一般来讲，UI线程会提示用户输入与开卡相关的个人化数据，以及与开卡相关的验证信息等，这些个人化数据以及验证信息等均可以作为第三部分数据被发送至服务器。比如，服务器可以根据验证信息进行验证，在验证成功时，根据预先存储的预定开卡规则以及第三部分数据生成第二部分数据，一般来讲，第二部分数据为用户开卡时的个人化数据，这里的个人化数据除了包含用户根据UI线程输入的个人化数据之外，还可以包括服务器为用户生成的个人化数据。
在步骤408中，智能设备利用第二后台线程向服务器发送第二数据获取请求。
由于第一后台线程仅从服务器拉取了第一部分数据，因此当智能设备需要 获取第二部分数据时，需要利用第二后台线程向服务器发送第二数据获取请求。
在步骤409中，服务器接收该第二数据获取请求。
当智能设备向服务器发送第二数据获取请求后，对应的，服务器可以接收到第二数据获取请求。
在步骤410中，服务器向智能设备发送该第二部分数据。
服务器接收该第二数据获取请求后，可以向智能设备反馈该智能设备开卡相关的第二部分数据。
在步骤411中，智能设备接收该第二部分数据，利用该第二后台线程将第二部分数据写入SE芯片中。
步骤411与步骤306类似，具体可以参见对步骤306的描述，这里就不再赘述。
综上所述，本公开实施例中提供的开卡数据写入方法，智能设备在UI线程实现开卡前的相关操作的过程中，即利用创建的第一后台线程向SE芯片写入开卡需要的部分数据，从而使得在UI线程完成开卡前的相关操作时，已经向SE芯片写入了开卡相关的部分数据，在最后一步仅需要写入尚未被写入至SE芯片的数据即可，节省了在UI线程实现开卡前的相关操作过程中，被写入SE芯片的与开卡相关的部分数据时所需要的写入时长，解决了相关技术中利用NFC设备进行开卡时耗时过长的问题，降低了利用NFC设备进行开卡时的耗时。
在实际实现时，步骤401、步骤402、步骤405、步骤406、步骤408和步骤411可以单独实施成为以智能设备为执行主体的开卡数据写入方法；步骤403、步骤404、步骤407、步骤409和步骤410可以单独实施成为以服务器为执行主体的开卡数据写入方法。
下述为本公开装置实施例，可以用于执行本公开方法实施例。对于本公开装置实施例中未披露的细节，请参照本公开方法实施例。
图5A是根据一示例性实施例示出的一种开卡数据写入装置的框图，如图5A所示，该开卡数据写入装置应用于图1所示的智能设备100中，该开卡数据写入装置包括但不限于：第一创建模块510、第一写入模块520、第二创建模块530和第二写入模块540。
第一创建模块510，被配置为在利用用户界面UI线程实现开卡前的相关操 作的过程中，创建第一后台线程。
UI线程是执行开卡前相关操作的线程，一般的，UI线程用于显示开卡前与开卡相关操作的页面、执行这些页面的相关操作等。
在实际应用中，智能设备通常可以安装与实例化NFC卡相关的应用程序，利用该应用程序创建UI线程，该UI线程可以与服务器进行交互，以获取开卡过程中需要显示的页面以及执行页面所提供的相关操作。
比如，在开卡过程中，常见的页面包括显示的与开卡相关的服务条款的显示页面、开卡相关的个人化数据输入页面等，这些页面上可以有引导用户输入个人化数据的输入框以及引导用户确认或取消输入个人化数据的控件等。
可选的，智能设备在利用UI线程实现开卡前的相关操作的过程中，若UI线程接收到用于指示允许执行开卡的允许指示，则创建第一后台线程。
这里的允许指示一般意味着开卡用户允许开卡，此时UI线程可以继续执行开卡前的相关操作。换句话说，允许指示意味着用户准备根据UI线程执行开卡前的相关操作。
比如，在一种常见的开卡流程中，UI线程通常会先显示从服务器获取的与开卡相关的服务条款事项，当用户同意服务条款事项时，则可以判定UI线程接收到用于指示允许开卡的允许指示，此时则可以创建第一后台线程。
还比如，在另一种常见的开卡流程中，UI线程可能会显示询问用户是否希望开卡的提示，当用户确认希望开卡时，则可以判定UI线程接收到用于指示允许开卡的允许指示，此时则可以创建第一后台线程。
第一后台线程一般不涉及UI界面的显示或操作，其在UI线程执行的过程中，可以与UI线程并列运行，也可以与UI线程串行运行。第一后台线程在与UI线程串行运行的过程中，由于UI线程在操作的整个流程可能会暂停运行，比如等待用户操作时，因此第一后台线程可以在UI线程停止运行的间隔运行。但从宏观角度看，第一后台线程与UI线程仍旧可以看成是并列运行的关系，也即在UI线程执行的整个时长内，第一后台线程可以同时运行。
第一写入模块520，被配置为利用第一创建模块510创建的第一后台线程从服务器获取开卡所需要的第一部分数据，将第一部分数据写入SE芯片中。
第一部分数据是服务器提供的开卡时需要写入SE芯片中的数据，这些数据一般是开卡所需要的预加载数据，第一部分数据通常不会因UI线程的操作而发 生变化。
也就是说，第一部分数据与个人化数据无关，而为了使得实例化后NFC卡的辨识，需要向SE芯片写入与用户信息相关的数据，以使得NFC卡具备唯一的身份，这类数据一般称为个人化数据，也即本实施例中下面提及的第二部分数据。
第二部分数据通常是开卡时需要写入SE芯片中的与用户信息相关的数据，第二部分数据可能会因UI线程的操作而发生变化。由于在利用UI线程操作时可能需要用户输入个人化数据，比如用户的电话号码、身份信息、充值金额等，因此不同用户在利用UI线程执行开卡前的相关操作时，UI线程获取到的用户输入的数据可能全部或部分不同，因此这些数据可以由UI线程的操作而决定。
可选的，个人化数据还可以包括服务器为开卡操作分配的用于唯一标识用户身份的数据。
可选的，第一部分数据可以包括与NFC射频单元交互的数据，还可以包括用于修改SE芯片中个人化数据的数据。
为了进行上述数据的区分，可以将开卡需要写入SE芯片中的数据分为第一部分数据和第二部分数据，其中，第一部分数据是开卡所需要的非个人化数据，第二部分数据是开卡所需要的个人化数据。
第一后台线程在向SE芯片写入第一部分数据时，可以通过预定的方式写入，写入至SE芯片的路径也可以是预先设定的。
由于在利用智能设备开卡的过程中，UI线程引导用户输入个人化数据，因此UI线程会占用一定的时长，且该时长是开卡流程中必须占用的，很显然，在UI线程执行期间，利用第一后台线程将第一部分数据写入SE芯片，可以节省用户后期等待线程将第一部分数据写入SE芯片的写入时间。
第二创建模块530，被配置为在利用UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程。
在利用UI线程完成开卡前的相关操作且确定开卡后，通常意味着用户不再修改个人化数据，此时则可以创建第二后台线程，实现个人化数据向SE芯片的写入。
第二写入模块540，被配置为利用第二创建模块530创建的第二后台线程将开卡所需要的第二部分数据写入所述SE芯片中，第一部分数据和第二部分数据 是需要写入SE芯片中的与开卡相关的数据。
开卡所需要的第二部分数据一般由UI线程执行的相关操作中得到的数据。
可选的，第二部分数据也可以是先由UI线程执行相关操作得到，然后被同步到服务器的数据，这样在实现时，第二后台线程则可以从服务器拉取到开卡需要的第二部分数据。
举例来讲，利用UI线程获得的第二部分数据被同步至服务器后，由服务器进行审核，并在审核通过后，与第一部分数据进行绑定存储。第二后台线程向服务器发送获取第二部分数据的获取请求，服务器反馈审核通过的第二部分数据，第二后台线程将从服务器获取到的第二部分数据写入SE芯片中。
第二后台线程在向SE芯片写入第二部分数据时，可以通过预定的方式写入，写入至SE芯片的路径也可以是预先设定的。
在一种可能的实现方式中，该第一创建模块510还可以被配置为：在利用UI线程实现开卡前的相关操作的过程中，若UI线程接收到用于指示允许开卡的允许指示，则创建第一后台线程。
在另一种可能的实现方式中，由于已经建立了第一后台线程向SE芯片写入第一部分数据，如果该第一部分数据尚未写完，且第一后台线程和第二后台线程同时向SE芯片写入数据，则可能出现数据写入错误，为了避免这种情况，该第二创建模块530可以包括：检测子模块531、第一创建子模块532和第二创建子模块533，请参见图5B所示。
检测子模块531，被配置为检测第一后台线程是否将第一部分数据全部写入SE芯片中。
一般的，当第一后台线程将第一部分数据全部写入SE芯片，则应用程序会释放掉该第一后台线程。
当第一后台线程尚未被释放掉时，则可以判定第一后台线程尚未将第一部分数据全部写入SE芯片；当第一后台线程已经被释放掉时，则可以判定第一后台线程尚已经将第一部分数据全部写入SE芯片中。
第一创建子模块532，被配置为在检测子模块531检测到第一后台线程尚未将第一部分数据全部写入SE芯片中时，等待第一后台线程继续将剩余的第一部分数据写入SE芯片，在将第一部分数据全部写入SE芯片后，创建第二后台线程。
若第一后台线程尚未将第一部分数据全部写入SE芯片中，则等待第一后台线程继续将剩余的第一部分数据写入SE芯片，直到第一后台线程被释放，此时则可以创建第二后台线程。
第二创建子模块533，被配置为在检测子模块531检测到第一后台线程已将第一部分数据全部写入SE芯片中时，创建第二后台线程。
可替换地，如果第一后台线程将第一部分数据写入SE芯片的第一路径下，第二后台线程将第二部分数据写入SE芯片的第二路径下，第一路径和第二路径不同，这种情况下，一般不会出现写入数据错误，此时在创建第二后台线程时，可以不用等到第一后台线程完全释放，即可创建第二后台线程。
在另一种可能的实现方式中，请参见图5B所示，该卡数据写入装置还可以包括：检测模块550、第一显示模块560和判定模块570。
检测模块550，被配置为检测UI线程是否完成开卡前的相关操作。
一般的，当应用程序利用UI线程执行开卡前的相关操作时，UI线程执行的相关操作是已知的，因此，根据UI线程执行的相关操作即可判定UI线程是否完成开卡前的相关操作。也就是说，UI线程是否具备显示开卡控件的条件，以促使用户利用开卡控件确定开卡。
第一显示模块560，被配置为在检测模块550检测到UI线程完成了开卡前的相关操作时，显示开卡控件；
判定模块570，被配置为在第一显示模块560显示的开卡控件被触发时，判定利用UI线程完成了开卡前的相关操作且确定开卡。
一般的，当UI线程完成了开卡前的相关操作，显示的开卡控件的属性为允许操作或允许操作响应。这种情况下，用户可以触发该开卡控件，当用户触发该开卡控件时，UI线程可以得知该开卡控件被触发。
而当线程未完成开卡前的相关操作，则显示的开卡控件的属性一般为禁止操作或禁止操作响应，比如常见的以灰色形式表示。这种情况下，即使用户触发了该开卡控件，UI线程仍然不会对该触发操作进行响应。
这里所讲的显示开卡控件是指显示属性为允许操作或允许操作响应的开卡控件。
当用户触发开卡控件，表明用户不再修改UI线程中所涉及界面的数据输入，因此此时则可以判定确定开卡。
在另一种可能的实现方式中，请参见图5B所示，该卡数据写入装置还可以包括：第二显示模块580。
第二显示模块580，被配置为在第一部分数据和第二部分数据均被成功写入SE芯片后，显示用于提示发卡成功的提示信息。
提示信息可以用于提示用户发卡成功，这样用户则可以利用NFC设备代替实务卡进行使用。
在发卡成功之后，NFC设备可以利用NFC射频单元与NFC接收器进行通信，利用通信信息修改SE芯片中的数据。
以模拟公交卡的NFC设备为例，NFC设备中的SE芯片中包含用于指示剩余金额的数据，当NFC设备靠近公交费用扣除器时，则NFC设备中的NFC射频单元可以获知公交费用扣除器告知的需要扣除的资源值，NFC射频单元会通知SE芯片修改指示剩余金额的数据，将该数据减少该资源值。
综上所述，本公开实施例中提供的开卡数据写入装置，通过在UI线程实现开卡前的相关操作的过程中，即利用创建的第一后台线程向SE芯片写入开卡需要的部分数据，从而使得在UI线程完成开卡前的相关操作时，已经向SE芯片写入了开卡相关的部分数据，在最后一步仅需要写入尚未被写入至SE芯片的数据即可，节省了在UI线程实现开卡前的相关操作过程中，被写入SE芯片的与开卡相关的部分数据时所需要的写入时长，解决了相关技术中利用NFC设备进行开卡时耗时过长的问题，降低了利用NFC设备进行开卡时的耗时。
另外，由于UI线程实现开卡前的相关操作较为复杂和多样，因此为了尽快的向SE芯片写入开卡需要的数据，可以在UI线程接收到用于指示允许开卡的允许指示时，创建第一后台线程，以执行向SE芯片写入开卡需要的数据，从而使得在UI线程实现开卡的相关操作过程中，能尽量早的向SE芯片写入数据，以尽量减少开卡耗时。
通过在判定第一后台线程将第一部分数据全部写入了SE芯片之后，再创建第二后台线程，避免了在利用两个线程同时向SE芯片写入数据时可能出错的问题。
为了避免开卡前的相关操作发生了漏操作，需要在确定UI线程完成了开卡前的相关操作后显示开卡控件，以便于执行最后向UE芯片写入剩余数据的操作。
图6A是根据一示例性实施例示出的一种开卡数据写入装置的框图，如图6A所示，该开卡数据写入装置应用于服务器中，该开卡数据写入装置包括但不限于：第一收发模块610、获取模块620和第二收发模块630。
第一收发模块610，被配置为接收智能设备发送的第一数据获取请求，向智能设备发送开卡所需要的第一部分数据，第一数据获取请求是智能设备在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程后，利用第一后台线程发送的，第一部分数据用于触发智能设备将第一部分数据写入智能设备中安全元件SE芯片中；
获取模块620，被配置为获取智能设备开卡所需要的第二部分数据；
第二收发模块630，被配置为接收智能设备发送的第二数据获取请求，向智能设备发送获取模块620获取的第二部分数据，第二数据获取请求是智能设备在利用UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程后，利用第二后台线程发送的，第二部分数据用于触发智能设备将第二部分数据写入SE芯片中。
在一种可能的实现方式中，获取模块620可以包括：接收子模块621和生成子模块622，请参见图6B所示。
接收子模块621，被配置为接收智能设备发送的第三部分数据，第三部分数据是智能设备利用UI线程产生的。
生成子模块622，被配置为根据预定开卡规则以及接收子模块621接收到的第三部分数据生成第二部分数据。
一般来讲，UI线程会提示用户输入与开卡相关的个人化数据，以及与开卡相关的验证信息等，这些个人化数据以及验证信息等均可以作为第三部分数据被发送至服务器。比如，服务器可以根据验证信息进行验证，在验证成功时，根据预先存储的预定开卡规则以及第三部分数据生成第二部分数据，一般来讲，第二部分数据为用户开卡时的个人化数据，这里的个人化数据除了包含用户根据UI线程输入的个人化数据之外，还可以包括服务器为用户生成的个人化数据。
在另一种可能的实现方式中，第一部分数据是开卡所需要的非个人化数据，第二部分数据是开卡所需要的个人化数据。
综上所述，本公开实施例中提供的开卡数据写入装置，通过在接收到智能 设备的第一数据获取请求时向智能设备发送与开卡相关的第一部分数据，从而使得智能设备在UI线程完成开卡前的相关操作时，已经向SE芯片写入了与开卡相关的部分数据，在最后一步仅需要写入尚未被写入至SE芯片的数据即可，节省了在UI线程实现开卡前的相关操作过程中，写入至SE芯片的与开卡相关的部分数据所需要的写入时长，解决了相关技术中利用NFC设备进行开卡时耗时过长的问题，降低了利用NFC设备进行开卡时的耗时。
图7是根据一示例性实施例示出的一种开卡数据写入系统的框图，该开卡数据写入系统包括智能设备710和服务器720。
智能设备710可以包括如图5A和图5B所示的开卡数据写入装置，具体可以对图5A和图5B的描述，这里就不再赘述。
服务器720可以包括如图6A和图6B所示的开卡数据写入装置，具体可以对图6A和图6B的描述，这里就不再赘述。
综上所述，本公开实施例中提供的开卡数据写入系统，智能设备在UI线程实现开卡前的相关操作的过程中，即利用创建的第一后台线程向SE芯片写入开卡需要的部分数据，从而使得在UI线程完成开卡前的相关操作时，已经向SE芯片写入了开卡相关的部分数据，在最后一步仅需要写入尚未被写入至SE芯片的数据即可，节省了在UI线程实现开卡前的相关操作过程中，被写入SE芯片的与开卡相关的部分数据时所需要的写入时长，解决了相关技术中利用NFC设备进行开卡时耗时过长的问题，降低了利用NFC设备进行开卡时的耗时。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本公开一示例性实施例提供了一种开卡数据写入装置，能够实现本公开提供的开卡数据写入方法，该开卡数据写入装置应用于图1所示的智能设备100中，该开卡数据写入装置可以包括：处理器、用于存储处理器可执行指令的存储器；
其中，处理器被配置为：
在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线 程；
利用第一后台线程从服务器获取开卡所需要的第一部分数据，将第一部分数据写入SE芯片中；
在利用UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程，利用第二后台线程将开卡所需要的第二部分数据写入所述SE芯片中，第一部分数据和第二部分数据是需要写入SE芯片中的与开卡相关的数据。
本公开另一示例性实施例提供了一种开卡数据写入装置，能够实现本公开提供的开卡数据写入方法，该开卡数据写入装置应用于服务器中，该开卡数据写入装置可以包括：处理器、用于存储处理器可执行指令的存储器；
其中，处理器被配置为：
接收智能设备发送的第一数据获取请求，向所述智能设备发送开卡所需要的第一部分数据，所述第一数据获取请求是所述智能设备在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程后，利用所述第一后台线程发送的，所述第一部分数据用于触发所述智能设备将所述第一部分数据写入所述智能设备中安全元件SE芯片中；
获取所述智能设备开卡所需要的第二部分数据；
接收所述智能设备发送的第二数据获取请求，向所述智能设备发送所述第二部分数据，所述第二数据获取请求是所述智能设备在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程后，利用所述第二后台线程发送的，所述第二部分数据用于触发所述智能设备将所述第二部分数据写入所述SE芯片中。
图8是根据再一示例性实施例示出的一种开卡数据写入装置的框图。例如，装置800可以是包含有SE芯片的智能设备，比如常见的移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图8，装置800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)接口812，传感器组件814，以及通信组件816。
处理组件802通常控制装置800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器818来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在装置800的操作。这些数据的示例包括用于在装置800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为装置800的各种组件提供电力。电源组件806可以包括电源管理系统，一个或多个电源，及其他与为装置800生成、管理和分配电力相关联的组件。
多媒体组件808包括在装置800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当装置800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当装置800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为装置800提供各个方面的状态评估。例如，传感器组件814可以检测到装置800的打开/关闭状态，组件的相对定位，例如组件为装置800的显示器和小键盘，传感器组件814还可以检测装置800或装置800一个组件的位置改变，用户与装置800接触的存在或不存在，装置800方位或加速/减速和装置800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于装置800和其他设备之间有线或无线方式的通信。装置800可以接入基于通信标准的无线网络，如Wi-Fi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。对应的，装置800还包括SE芯片(未图示)，该SE芯片与NFC模块连接，SE芯片通过NFC模块与外部设备进行通信。SE芯片还可以通过通信组件816中其他通信方式(比如Wi-Fi，2G或3G)的通信模块，与网络侧设备通信。
在示例性实施例中，装置800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述开卡数据写入方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由装置800的处理器818执行以完成上述开卡数据写入方法。例如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
图9是根据再一示例性实施例示出的一种开卡数据写入装置的框图。例如，装置900可以被提供为一网络侧设备，比如服务器。参照图9，装置900包括处理组件902，其进一步包括一个或多个处理器，以及由存储器904所代表的存储器资源，用于存储可由处理组件902的执行的指令，例如应用程序。存储器904中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件902被配置为执行指令，以执行上述开卡数据写入方法。
装置900还可以包括一个电源组件906被配置为执行装置900的电源管理，一个有线或无线网络接口908被配置为将装置900连接到网络，和一个输入输出(I/O)接口910。装置900可以操作基于存储在存储器904的操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (21)

  1. 一种开卡数据写入方法，其特征在于，应用于包含有安全元件SE芯片的智能设备中，所述方法包括：
    在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程；
    利用所述第一后台线程从服务器获取开卡所需要的第一部分数据，将所述第一部分数据写入所述SE芯片中；
    在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程，利用所述第二后台线程将开卡所需要的第二部分数据写入所述SE芯片中，所述第一部分数据和所述第二部分数据是需要写入SE芯片中的与开卡相关的数据。
  2. 根据权利要求1所述的方法，其特征在于，所述在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程，包括：
    在利用所述UI线程实现开卡前的相关操作的过程中，若所述UI线程接收到用于指示允许开卡的允许指示，则创建所述第一后台线程。
  3. 根据权利要求1所述的方法，其特征在于，所述创建第二后台线程，包括：
    检测所述第一后台线程是否将所述第一部分数据全部写入所述SE芯片中；
    若所述第一后台线程尚未将所述第一部分数据全部写入所述SE芯片中，则等待所述第一后台线程继续将剩余的所述第一部分数据写入所述SE芯片，在将所述第一部分数据全部写入所述SE芯片后，创建所述第二后台线程；
    若所述第一后台线程已将所述第一部分数据全部写入所述SE芯片中，则创建所述第二后台线程。
  4. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    检测所述UI线程是否完成开卡前的相关操作；
    若所述UI线程完成了开卡前的相关操作，则显示开卡控件；
    在所述开卡控件被触发时，判定利用所述UI线程完成了开卡前的相关操作且确定开卡。
  5. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述第一部分数据和所述第二部分数据均被成功写入所述SE芯片后，显示用于提示发卡成功的提示信息。
  6. 根据权利要求1至5中任一所述的方法，其特征在于，所述第一部分数据是开卡所需要的非个人化数据，所述第二部分数据是开卡所需要的个人化数据。
  7. 一种开卡数据写入方法，其特征在于，应用于服务器中，所述方法包括：
    接收智能设备发送的第一数据获取请求，向所述智能设备发送开卡所需要的第一部分数据，所述第一数据获取请求是所述智能设备在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程后，利用所述第一后台线程发送的，所述第一部分数据用于触发所述智能设备将所述第一部分数据写入所述智能设备中安全元件SE芯片中；
    获取所述智能设备开卡所需要的第二部分数据；
    接收所述智能设备发送的第二数据获取请求，向所述智能设备发送所述第二部分数据，所述第二数据获取请求是所述智能设备在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程后，利用所述第二后台线程发送的，所述第二部分数据用于触发所述智能设备将所述第二部分数据写入所述SE芯片中。
  8. 根据权利要求7所述的方法，其特征在于，所述获取所述智能设备开卡所需要的第二部分数据，包括：
    接收所述智能设备发送的第三部分数据，所述第三部分数据是所述智能设备利用所述UI线程产生的；
    根据预定开卡规则以及所述第三部分数据生成所述第二部分数据。
  9. 根据权利要求7或8所述的方法，其特征在于，所述第一部分数据是开卡所需要的非个人化数据，所述第二部分数据是开卡所需要的个人化数据。
  10. 一种开卡数据写入装置，其特征在于，应用于包含有安全元件SE芯片的智能设备中，所述装置包括：
    第一创建模块，被配置为在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程；
    第一写入模块，被配置为利用所述第一创建模块创建的所述第一后台线程从服务器获取开卡所需要的第一部分数据，将所述第一部分数据写入所述SE芯片中；
    第二创建模块，被配置为在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程；
    第二写入模块，被配置为利用所述第二创建模块创建的所述第二后台线程将开卡所需要的第二部分数据写入所述SE芯片中，所述第一部分数据和所述第二部分数据是需要写入SE芯片中的与开卡相关的数据。
  11. 根据权利要求10所述的装置，其特征在于，所述第一创建模块，还被配置为：
    在利用所述UI线程实现开卡前的相关操作的过程中，若所述UI线程接收到用于指示允许开卡的允许指示，则创建所述第一后台线程。
  12. 根据权利要求10所述的装置，其特征在于，所述第二创建模块，包括：
    检测子模块，被配置为检测所述第一后台线程是否将所述第一部分数据全部写入所述SE芯片中；
    第一创建子模块，被配置为在所述检测子模块检测到所述第一后台线程尚未将所述第一部分数据全部写入所述SE芯片中时，等待所述第一后台线程继续将剩余的所述第一部分数据写入所述SE芯片，在将所述第一部分数据全部写入所述SE芯片后，创建所述第二后台线程；
    第二创建子模块，被配置为在所述检测子模块检测到所述第一后台线程已将所述第一部分数据全部写入所述SE芯片中时，创建所述第二后台线程。
  13. 根据权利要求10所述的装置，其特征在于，所述装置还包括：
    检测模块，被配置为检测所述UI线程是否完成开卡前的相关操作；
    第一显示模块，被配置为在所述检测模块检测到所述UI线程完成了开卡前的相关操作时，显示开卡控件；
    判定模块，被配置为在所述第一显示模块显示的所述开卡控件被触发时，判定利用所述UI线程完成了开卡前的相关操作且确定开卡。
  14. 根据权利要求10所述的装置，其特征在于，所述装置还包括：
    第二显示模块，被配置为在所述第一部分数据和所述第二部分数据均被成功写入所述SE芯片后，显示用于提示发卡成功的提示信息。
  15. 根据权利要求10至14中任一所述的装置，其特征在于，所述第一部分数据是开卡所需要的非个人化数据，所述第二部分数据是开卡所需要的个人化数据。
  16. 一种开卡数据写入装置，其特征在于，应用于服务器中，所述装置包括：
    第一收发模块，被配置为接收智能设备发送的第一数据获取请求，向所述智能设备发送开卡所需要的第一部分数据，所述第一数据获取请求是所述智能设备在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程后，利用所述第一后台线程发送的，所述第一部分数据用于触发所述智能设备将所述第一部分数据写入所述智能设备中安全元件SE芯片中；
    获取模块，被配置为获取所述智能设备开卡所需要的第二部分数据；
    第二收发模块，被配置为接收所述智能设备发送的第二数据获取请求，向所述智能设备发送所述获取模块获取的所述第二部分数据，所述第二数据获取请求是所述智能设备在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程后，利用所述第二后台线程发送的，所述第二部分数据用于触发所述智能设备将所述第二部分数据写入所述SE芯片中。
  17. 根据权利要求16所述的装置，其特征在于，所述获取模块，包括：
    接收子模块，被配置为接收所述智能设备发送的第三部分数据，所述第三部分数据是所述智能设备利用所述UI线程产生的；
    生成子模块，被配置为根据预定开卡规则以及所述接收子模块接收到的所述第三部分数据生成所述第二部分数据。
  18. 根据权利要求16或17所述的装置，其特征在于，所述第一部分数据是开卡所需要的非个人化数据，所述第二部分数据是开卡所需要的个人化数据。
  19. 一种开卡数据写入系统，其特征在于，所述系统包括智能设备和服务器，所述智能设备包括如权利要求10至15中任一所述的开卡数据写入装置，所述服务器包括如权利要求16至18中任一所述的开卡数据写入装置。
  20. 一种开卡数据写入装置，其特征在于，应用于包含有安全元件SE芯片的智能设备中，所述装置包括：
    处理器；
    用于存储所述处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程；
    利用所述第一后台线程从服务器获取开卡所需要的第一部分数据，将所述第一部分数据写入所述SE芯片中；
    在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程，利用所述第二后台线程将开卡所需要的第二部分数据写入所述SE芯片中，所述第一部分数据和所述第二部分数据是需要写入SE芯片中的与开卡相关的数据。
  21. 一种开卡数据写入装置，其特征在于，应用于服务器中，所述装置包括：
    处理器；
    用于存储所述处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    接收智能设备发送的第一数据获取请求，向所述智能设备发送开卡所需要的第一部分数据，所述第一数据获取请求是所述智能设备在利用用户界面UI线程实现开卡前的相关操作的过程中，创建第一后台线程后，利用所述第一后台线程发送的，所述第一部分数据用于触发所述智能设备将所述第一部分数据写入所述智能设备中安全元件SE芯片中；
    获取所述智能设备开卡所需要的第二部分数据；
    接收所述智能设备发送的第二数据获取请求，向所述智能设备发送所述第二部分数据，所述第二数据获取请求是所述智能设备在利用所述UI线程完成开卡前的相关操作且确定开卡后，创建第二后台线程后，利用所述第二后台线程发送的，所述第二部分数据用于触发所述智能设备将所述第二部分数据写入所述SE芯片中。
PCT/CN2016/098946 2016-06-23 2016-09-14 开卡数据写入方法、装置及系统 WO2017219513A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610466532.3 2016-06-23
CN201610466532.3A CN106156667B (zh) 2016-06-23 2016-06-23 开卡数据写入方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2017219513A1 true WO2017219513A1 (zh) 2017-12-28

Family

ID=57353319

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/098946 WO2017219513A1 (zh) 2016-06-23 2016-09-14 开卡数据写入方法、装置及系统

Country Status (4)

Country Link
US (1) US10558973B2 (zh)
EP (1) EP3261041A1 (zh)
CN (1) CN106156667B (zh)
WO (1) WO2017219513A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109285001A (zh) * 2018-08-31 2019-01-29 阿里巴巴集团控股有限公司 可支付交通费用的设备、组合设备、系统及方法
CN110490285B (zh) * 2019-08-26 2023-11-28 北京小米支付技术有限公司 模拟卡片的方法、装置及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110098023A1 (en) * 2009-10-27 2011-04-28 Visa U.S.A. Inc. System and Method for Enabling a Mobile Communication Device to Operate as a Financial Presentation Device
CN202444629U (zh) * 2012-02-29 2012-09-19 中国工商银行股份有限公司 利用移动终端进行卡操作的系统
CN102929532A (zh) * 2012-09-29 2013-02-13 东莞宇龙通信科技有限公司 应用程序的启动方法及通信终端
CN104602224A (zh) * 2014-12-31 2015-05-06 浙江融创信息产业有限公司 一种基于nfc手机swp-sim卡的空中开卡方法
CN105046486A (zh) * 2015-07-17 2015-11-11 百度在线网络技术（北京）有限公司 基于nfc的移动支付方法和装置
CN105678618A (zh) * 2015-12-31 2016-06-15 深圳前海微众银行股份有限公司 空中发卡方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8807440B1 (en) * 2010-12-17 2014-08-19 Google Inc. Routing secure element payment requests to an alternate application
WO2013130982A1 (en) * 2012-03-01 2013-09-06 Mastercard International Incorporated Dba Mastercard Worldwide Systems and methods for mapping a mobile cloud account to a payment account

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110098023A1 (en) * 2009-10-27 2011-04-28 Visa U.S.A. Inc. System and Method for Enabling a Mobile Communication Device to Operate as a Financial Presentation Device
CN202444629U (zh) * 2012-02-29 2012-09-19 中国工商银行股份有限公司 利用移动终端进行卡操作的系统
CN102929532A (zh) * 2012-09-29 2013-02-13 东莞宇龙通信科技有限公司 应用程序的启动方法及通信终端
CN104602224A (zh) * 2014-12-31 2015-05-06 浙江融创信息产业有限公司 一种基于nfc手机swp-sim卡的空中开卡方法
CN105046486A (zh) * 2015-07-17 2015-11-11 百度在线网络技术（北京）有限公司 基于nfc的移动支付方法和装置
CN105678618A (zh) * 2015-12-31 2016-06-15 深圳前海微众银行股份有限公司 空中发卡方法及装置

Also Published As

Publication number Publication date
US20170372295A1 (en) 2017-12-28
CN106156667A (zh) 2016-11-23
EP3261041A1 (en) 2017-12-27
US10558973B2 (en) 2020-02-11
CN106156667B (zh) 2019-04-16

Similar Documents

Publication Publication Date Title
US9886264B2 (en) Method and device for upgrading firmware
EP3261037A1 (en) Method and apparatus for activating virtual card
CN105975166B (zh) 应用控制方法及装置
US9800666B2 (en) Method and client terminal for remote assistance
EP3285219A1 (en) Resource transfer method and apparatus, computer program and recording medium
RU2669063C2 (ru) Способ и устройство получения изображений
RU2628258C2 (ru) Способ и устройство для обработки детского режима
WO2016090822A1 (zh) 对固件进行升级的方法及装置
US10433169B2 (en) Method and device for controlling information transmission, and smart terminal
CN107315609B (zh) 卡模拟功能的切换方法及装置
US20170123644A1 (en) Interface display method and device
EP3136793A1 (en) Method and apparatus for awakening electronic device
WO2017071078A1 (zh) 通讯模组固件和插件生成方法及装置
US20170272425A1 (en) Method and device for accessing smart camera
CN107798309B (zh) 指纹录入方法、装置及计算机可读存储介质
RU2641949C2 (ru) Способ и устройство для управления интеллектуальным устройством
US20170300260A1 (en) Method, device and computer-readable storage medium for data migration
CN104317402B (zh) 描述信息的显示方法及装置、电子设备
US11663022B2 (en) Method and apparatus for displaying widget
EP3322227A1 (en) Methods and apparatuses for controlling wireless connection, computer program and recording medium
WO2016150104A1 (zh) 应用主题的加载方法及装置
US20170308397A1 (en) Method and apparatus for managing task of instant messaging application
CN104407981B (zh) 内存管理方法和装置
CN108829473B (zh) 事件响应方法、装置及存储介质
WO2017219513A1 (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: 16906053

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

Country of ref document: EP

Kind code of ref document: A1