WO2023185731A1

WO2023185731A1 - Nfc-based card swiping method, medium, and electronic device

Info

Publication number: WO2023185731A1
Application number: PCT/CN2023/084062
Authority: WO
Inventors: 高红星; 杨晗; 熊勇
Original assignee: 华为技术有限公司
Priority date: 2022-04-02
Filing date: 2023-03-27
Publication date: 2023-10-05
Also published as: CN116933809A

Abstract

The present application relates to the technical field of near field communications (NFC), and in particular to an NFC-based card swiping method, a readable medium, and an electronic device. The method comprises: an electronic device enters a card emulation mode, wherein the electronic device stores card information of a plurality of first-type emulation cards; and when the electronic device does not receive a service identifier, the electronic device selects the first-type emulation cards one by one from among the plurality of first-type emulation cards to perform emulation. Therefore, when storing a plurality of first-type emulation cards, the electronic device can automatically select the first-type emulation cards one by one for emulation, without manual switching by a user, thereby improving user experience. In addition, the card information of the first-type emulation cards can also be stored in a memory of the electronic device instead of a secure element or an embedded secure element, so that the speed of the electronic device switching the first-type emulation cards can be improved, the speed of the user swiping a card by using the electronic device is further improved, and the user experience is improved.

Description

NFC-based card swiping method, media and electronic device

This application claims priority to the Chinese patent application submitted to the China Patent Office on April 2, 2022, with the application number 202210352015.9 and the application name "NFC-based card swiping method, medium and electronic device", the entire content of which is incorporated by reference in in this application.

Technical field

This application relates to the field of near field communication technology, and in particular to an NFC-based card swiping method, readable media and electronic equipment.

Background technique

Near field communication (NFC) is a short-range wireless communication technology that allows contactless point-to-point data transmission and exchange of data between electronic devices. Currently, NFC has three working modes: card emulation mode, point-to-point mode (P2P mode), and reader/writer mode. Among them, card simulation is an integrated circuit (IC) card that uses radio frequency identification (RFID) technology to simulate physical cards, such as bus cards, access control cards, membership cards, bank cards, etc., and replaces physical cards with Card reading devices, such as card readers, provide card information for physical cards.

At present, electronic devices usually store physical card information in the embedded secure element (eSE) of the electronic device. When the electronic device simulates the physical card through the card emulation mode of NFC, the electronic device first obtains it from the card reading device. The business identifier of the current scenario, such as application identifier (AID). Then the electronic device obtains the card information of the simulated card corresponding to the AID from the eSE based on the obtained AID, and then writes the card information of the simulated card into the NFC controller, thereby transmitting the card information of the simulated card to the card reading device, completing Swipe your card. However, some physical cards, such as access control cards, do not have a unified business identifier. The electronic device does not store the AID corresponding to this type of card, and the card reading device of this type of card does not provide AID to the electronic device, resulting in When there are multiple cards without AID in the electronic device, the user is required to manually select the simulated card, which affects the user experience.

Contents of the invention

In view of this, embodiments of the present application provide an NFC-based card swiping method, a readable medium, and an electronic device. When the card information of multiple first-class simulation cards is stored in the electronic device, selecting the first-class simulation cards one by one to swipe the card will help improve the user experience.

In a first aspect, embodiments of the present application provide a card swiping method based on NFC. The method includes: the electronic device enters a card simulation mode, in which the card information of multiple first-type simulated cards is stored on the electronic device; when the electronic device When the service identification is not received, the electronic device selects the first type simulation cards one by one from multiple first type simulation cards for simulation.

In the embodiment of the present application, when the electronic device stores multiple first-type simulation cards (such as the simulation cards without AID below, such as access control cards, membership cards, etc.), the electronic device can automatically use the first-type simulation cards one by one. One type of model card can be simulated and tried to swipe without requiring the user to manually switch, which improves the user experience.

In a possible implementation of the above first aspect, the above electronic device selects the first type simulation cards one by one from multiple first type simulation cards for simulation, including: the electronic device selects the first type simulation cards one by one from the multiple first type simulation cards. The first type of simulation card performs card simulation until the preset termination conditions are met.

In the embodiment of the present application, the electronic device can cycle through each first-type simulation card for simulation until the preset termination conditions are met. This can avoid the situation where the card reader fails to swipe the card due to the card reader not reading the card information of the correct simulated card when the electronic device simulates the correct first-type simulated card, and the functionality rate of the user using the electronic device to swipe the card can be improved.

In a possible implementation of the above first aspect, the above preset termination condition includes any one of the following conditions:

The electronic device performs card emulation for longer than the preset time;

The NFC function of the electronic device is turned off;

The electronic device detects that the card has been successfully swiped;

The electronic device does not detect near field communication signals for more than the preset time;

The electronic device detects the user's cancellation operation or instruction.

In a possible implementation of the first aspect, the electronic device includes a memory; and card information of the first type of analog card is stored in the memory.

In the embodiment of the present application, the electronic device stores the card information of the first type of simulation card in the memory instead of the security unit or the embedded security unit, so that no security unit or embedded security unit is needed in the process of switching the first type of simulation card. The participation of the security unit can increase the speed of electronic devices switching among the above-mentioned first-class simulation cards, thereby increasing the speed of users using electronic devices to swipe cards and improving user experience.

In addition, since the card information of the first type of simulation card is stored in the memory, it can be stored in large quantities, and the security unit or embedded security unit can be used to store the card information of other simulation cards with higher security requirements, which can improve the support of electronic equipment. The number of emulated cards. Since no more security units or embedded security units are needed to store the card information of the first type of analog card, the manufacturing cost of the electronic device can be saved.

In a possible implementation of the above first aspect, the card information of the above first type simulation card is stored in the memory by the electronic device when opening each first type simulation card without obtaining the business identifier. middle.

In the embodiment of the present application, when the electronic device opens the first type of simulation card, the card information of the first type of simulation card is directly stored in the memory instead of the security unit or the embedded security unit, so that the electronic device There is no need to obtain the relevant procedures for opening the first type of simulation card from the network, and there is no need for the participation of a security unit or an embedded security unit, which can improve the speed of the electronic device for opening the first type of simulation card.

In a possible implementation of the above first aspect, the above electronic device further includes an NFC controller; and, the electronic device selects the first type simulation cards one by one from a plurality of first type simulation cards for simulation, including: the electronic device selects the first type simulation card from the memory The card information of each first-type simulation card is obtained one by one, and the obtained card information is written to the NFC controller for card simulation.

In a possible implementation of the first aspect, the electronic device includes a security unit SE or an embedded security unit eSE; and the card information of the first type of simulated card is stored in the security unit SE or the embedded security unit eSE.

In a possible implementation of the first aspect, a trusted application is run in the trusted execution environment of the electronic device, and the electronic device further includes an NFC controller; and, the electronic device selects one by one from multiple first-type simulation cards. The simulation of the first type of simulation card includes: the electronic device uses the trusted application, security unit SE or embedded security unit eSE to write the card information of the first type of simulation card into the NFC controller one by one to perform card simulation.

In a possible implementation of the first aspect, the card information includes a unique identifier UID; the service identifier includes an application identifier AID.

In a possible implementation of the above first aspect, the above electronic device enters the card emulation mode when detecting a user's preset operation on the electronic device and/or detecting a near field communication signal.

In a second aspect, embodiments of the present application provide an electronic device in which card information of multiple first-type analog cards is stored. The electronic device includes: a memory storing instructions; and a processor for instructing Execute the command to make the electronic device enter the card mode. After entering the simulation mode, when the electronic device does not receive the service identification, it selects the first type simulation cards one by one from multiple first type simulation cards for simulation.

In a possible implementation of the second aspect, the above-mentioned selection of the first type simulation cards from multiple first type simulation cards one by one for simulation includes: the electronic device selects the first type first simulation cards one by one from the multiple first type simulation cards. Class simulation card performs card simulation until the preset termination conditions are met.

In a possible implementation of the above second aspect, the above preset termination condition includes any one of the following conditions:

The electronic device performs card emulation for longer than the preset time;

The NFC function of the electronic device is turned off;

The electronic device detects that the card has been successfully swiped;

The electronic device detects the user's cancellation operation or instruction.

In a possible implementation of the above second aspect, the card information of the above first type of simulation card is stored in the memory.

In a possible implementation of the above second aspect, the card information of the above first type of simulation card is stored in the memory by the electronic device when opening each first type of simulation card without obtaining the business identifier. middle.

In a possible implementation of the second aspect, the electronic device further includes an NFC controller; and the first-type simulation cards are selected one by one from multiple first-type simulation cards for simulation, including:

The electronic device obtains the card information of each first-type simulation card one by one from the memory, and writes the obtained card information into the NFC controller for card simulation.

In a possible implementation of the second aspect, the electronic device further includes a security unit SE or an embedded security unit eSE; and the card information of the first type of simulated card is stored in the security unit SE or the embedded security unit eSE.

In a possible implementation of the second aspect, a trusted application is run in the trusted execution environment of the electronic device, and the electronic device further includes an NFC controller; and the first one is selected one by one from multiple first-type simulation cards. Simulation of a class of simulation cards includes: the electronic device uses a trusted application, security unit SE or embedded security unit eSE to write the card information of the first type of simulation card into the NFC controller one by one for card simulation.

In a possible implementation of the second aspect, the card information includes a unique identifier UID; the service identifier includes an application identifier AID.

In a possible implementation of the second aspect, when the above instructions are executed by the processor, the electronic device also causes the electronic device to control the The electronic device enters card emulation mode.

In a third aspect, embodiments of the present application provide a readable medium that stores instructions. When the instructions are executed on an electronic device, the electronic device enables the electronic device to implement the first aspect and various possibilities of the first aspect. Implement any of the provided methods.

It can be understood that the beneficial effects of the above-mentioned second aspect and the third aspect can be referred to the relevant description in the above-mentioned first aspect, and will not be described again here.

Description of drawings

Figure 1 shows a schematic structural diagram of an access control system 00 according to some embodiments of the present application;

Figure 2 shows a schematic diagram of a card swiping interface displayed by a mobile phone 10 according to some embodiments of the present application;

Figure 3 shows a technical architecture diagram of an NFC-based card swiping method according to some embodiments of the present application;

Figure 4 shows a schematic flow chart of an NFC-based card swiping method according to some embodiments of the present application;

Figure 5A shows a schematic diagram of the main interface of the wallet application 11A displayed on the mobile phone 10 when the user sets the default card of the mobile phone 10 through the wallet application 11A according to some embodiments of the present application;

Figure 5B shows a schematic diagram of the setting interface of the wallet application 11A displayed on the mobile phone 10 when the user sets the default card of the mobile phone 10 through the wallet application 11A according to some embodiments of the present application;

Figure 5C shows a schematic diagram of the card swiping setting interface of the wallet application 11A displayed on the mobile phone 10 when the user sets the default card of the mobile phone 10 through the wallet application 11A according to some embodiments of the present application;

Figure 5D shows a schematic diagram of the default card setting interface of the wallet application 11A displayed on the mobile phone 10 when the user sets the default card of the mobile phone 10 through the wallet application 11A according to some embodiments of the present application;

Figure 6 shows a schematic diagram of a card swiping failure interface displayed by the mobile phone 10 according to some embodiments of the present application;

Figure 7 shows a schematic technical architecture diagram of another NFC-based card swiping method according to some embodiments of the present application;

Figure 8 shows a schematic flow chart of another NFC-based card swiping method according to some embodiments of the present application;

Figure 9 shows a schematic log diagram of the data transmitted by the mobile phone 10 during the process of automatically switching access control cards obtained by using the NFC air interface packet capture tool according to some embodiments of the present application;

Figure 10 shows a battery of the mobile phone 10 when the mobile phone 10 terminates activation/activation of the simulated card through the eSE 13, reads the card information of the simulated card from the memory 103 and writes it to the NFC controller 14, according to some embodiments of the present application. changes in current;

Figure 11 shows a schematic technical architecture diagram of yet another NFC-based card swiping method according to some embodiments of the present application;

Figure 12 shows a schematic flow chart of yet another NFC-based card swiping method according to some embodiments of the present application;

Figure 13 shows a schematic flow chart of a near field communication simulation card opening method according to some embodiments of the present application;

Figure 14A shows a schematic diagram of the main interface of the wallet application 11A displayed on the mobile phone 10 when the mobile phone 10 enters the card opening mode according to some embodiments of the present application;

Figure 14B shows a schematic diagram of the card package interface of the wallet application 11A displayed on the mobile phone 10 when the mobile phone 10 enters the card opening mode according to some embodiments of the present application;

Figure 14C shows a schematic diagram of the card-adding interface of the wallet application 11A displayed on the mobile phone 10 when the mobile phone 10 enters the card opening mode according to some embodiments of the present application;

Figure 14D shows a schematic diagram of the key-adding interface of the wallet application 11A displayed on the mobile phone 10 when the mobile phone 10 enters the card opening mode according to some embodiments of the present application;

Figure 14E shows a schematic diagram of the simulated access card interface of the wallet application 11A displayed on the mobile phone 10 when the mobile phone 10 enters the card opening mode according to some embodiments of the present application;

Figure 15 shows a schematic flow chart of another near field communication simulation card opening method according to some embodiments of the present application;

Figure 16 shows a schematic flow chart of yet another near field communication simulation card opening method according to some embodiments of the present application;

Figure 17 shows a schematic structural diagram of a mobile phone 10 according to some embodiments of the present application.

Detailed ways

Illustrative embodiments of the present application include, but are not limited to, NFC-based card swiping methods, readable media, and electronic devices.

The technical solutions of the embodiments of the present application will be described below with reference to the accompanying drawings.

It can be understood that the NFC-based card swiping method provided by the embodiment of the present application is applicable to any electronic device that can simulate a physical card through the NFC function, including but not limited to mobile phones, laptop computers, tablet computers, wearable devices, and headsets. display, mobile email device, portable game console, portable music player, reader device, etc., the embodiments of this application are not limited. For ease of description, the following introduction takes the mobile phone 10 as an electronic device that can simulate a physical card through the NFC function.

It can be understood that the NFC-based card swiping method provided by the embodiment of the present application is suitable for any scenario where the NFC function of an electronic device is used to simulate a physical card, such as simulating access control cards, membership cards, etc. For the convenience of description, the following uses an access control card as an example to introduce the technical solutions of the embodiments of the present application.

Figure 1 shows a schematic structural diagram of an access control system 00 according to some embodiments of the present application.

As shown in Figure 1, the access control system 00 includes an NFC reader 01, a door controller 02 and a door 03. When the simulated access card of the mobile phone 10 is close to the NFC card reader 01, the NFC card reader 01 obtains the unique identifier (UID) of the simulated access card of the mobile phone 10 and sends the obtained UID to the door controller 02; the door After controller 02 receives the UID, it compares the UID with each UID in the pre-stored UID white list. If the received UID exists in the UID white list, it means that the UID has the access authority of door 03. Door controller 02 Open door 03; otherwise, it means that the UID does not have the permission to pass door 03, and keep door 03 closed.

As mentioned above, since the access control card does not have a unified AID, when only one simulation card without AID is stored in the mobile phone 10, the mobile phone 10 can simulate the card through NFC when it does not receive the AID. However, when there are multiple simulation cards without AID stored in the mobile phone 10, the mobile phone 10 cannot determine the simulation card corresponding to the current scene, and the user needs to manually select the simulation card to be simulated. For example, referring to Figure 2, when the mobile phone 10 does not receive AID and there are multiple simulation cards without AID stored in the mobile phone 10, the interface shown in Figure 2 will be displayed. The user needs to perform operations on the mobile phone 10. For example, sliding up and down, clicking, etc., to select the simulated card simulated by mobile phone 10 will affect the user's card swiping experience.

In view of this, the embodiment of the present application provides a card swiping method based on NFC. When the mobile phone 10 is close to the NFC card reader 01, if the AID sent by the NFC card reader 01 is not received, the AID stored in the mobile phone 10 will be swiped one by one. The card information of the simulated card without AID is written into the NFC controller of the mobile phone 10 until the card is swiped successfully (for example, door 03 is opened) or the user cancels the card swipe. In this way, even if the access control card does not have a unified AID, the mobile phone 10 can automatically select the simulated card stored in the mobile phone 10 to complete the card swiping without the user having to manually select, which improves the user experience.

It can be understood that the card information of the simulated card includes but is not limited to the UID and Select Acknowledge (SAK) identification of the simulated card. Among them, UID can be used to uniquely identify a simulation card. SAK can be used to indicate the card type of the simulated card. For example, a card with SAK=08 can be an access control card, and a card with SAK=20 can be a transportation card, bank card, etc. Additionally, emulated cards with different SAKs can have different lengths and/or types of UIDs. In some embodiments, the NFC card reading device may determine the length or type of the received UID based on the received SAK.

It can be understood that the card information of the simulated card stored in the mobile phone 10 can be obtained by using the NFC management application in the mobile phone 10 to read the card information of the physical card. The specific process will be described later in conjunction with the specific technical architecture. This will not be described in detail.

Specifically, FIG. 3 shows a technical architecture diagram of an NFC-based card swiping method according to some embodiments of the present application.

As shown in Figure 3, the software environment of the mobile phone 10 includes a rich execution environment (Rich Execution Environment, REE) 11 and a trusted execution environment (Trusted Execution Environment, TEE) 12. Among them, REE 11 can be used to run general-purpose operating systems, such as Android ^TM , IOS ^TM , Hongmeng ^TM , etc. The general-purpose operating system can be used to run applications/services with low security requirements, such as wallet application 11A, NFC service 11B, etc. Or store data with lower security requirements. TEE 12 can be used to run highly secure operating systems, such as Trusted Operating System (Trusted OS), Card Operating System (COS), etc. The Trusted Operating System is used to run trusted applications ( Trusted Application (TA), such as the trusted application corresponding to the wallet application (hereinafter referred to as wallet application TA) 12A, applications or services related to payment/biometrics/security verification, etc., or used to store data with high security requirements, For example, keys, biometric information, card information of simulated cards, etc.

The NFC-related hardware of the mobile phone 10 may include the eSE 13 and the NFC controller 14.

Among them, eSE 13 can be used to store card information of simulated cards (such as card A1, card A2, card B1, etc. shown in Figure 3), and according to the instructions of the trusted application in TEE 12, store the card information of simulated cards. The information is written into the NFC controller 14 , or the card information of the physical card currently close to the NFC controller 14 is obtained from the NFC controller 14 , and stored in the eSE 13 . In other embodiments, the eSE 13 may also be other types of hardware used to store data with high security requirements, such as a security element (Secure Element, SE), etc., which is not limited here.

It can be understood that in some embodiments, the eSE 13 can also be used to run a Java applet to write the card information of the simulated card to the NFC controller 14 according to the instructions of the trusted application in the TEE 12.

It can be understood that in some embodiments, the eSE 13 can also be used to run a Java applet, which is used to read the card information of the physical card through the eSE 13 according to the trusted application in the TEE 12.

The NFC controller 14 may be configured to send a message to an application in the REE 11, such as the wallet application 11A and/or the NFC service 11B, when a near field communication signal is detected, such as a near field communication signal of the NFC card reader 01. A triggering instruction that triggers the NFC-based card swiping method provided by the embodiment of the present application. The NFC controller 14 can also be used to send the card information to the eSE 13 when the card information is read. The NFC controller 14 can also be used to send the card information to a card reading device through NFC technology after receiving the card information sent by the eSE 13, for example, to the NFC card reader 01 to realize card swiping.

It can be understood that the technical architecture diagram shown in Figure 3 is only an example. In other embodiments, the mobile phone 10 may include more or less execution environments/hardware, and the functions/hardware of part of the execution environments may also be split or combined. Hardware is not limited in the embodiments of this application.

The following describes the NFC-based card swiping method provided by the embodiment of the present application based on the scenario shown in Figure 1 and the technical architecture diagram shown in Figure 3.

Specifically, FIG. 4 shows a schematic flow chart of an NFC-based card swiping method according to some embodiments of the present application. The execution subject of this process is the mobile phone 10. As shown in Figure 4, the process includes the following steps.

S401: A card swipe trigger instruction is detected.

When the mobile phone 10 detects the card swiping triggering instruction, it triggers the NFC-based card swiping method provided by the embodiment of the present application. Specifically, in some embodiments, the mobile phone 10 can use an application/service in the mobile phone 10 to detect the card swipe triggering instruction, such as the aforementioned wallet application 11A, NFC service 11B, etc.

In some embodiments, referring to FIG. 1 , when the mobile phone 10 is close to the NFC card reader 01 and the NFC controller 14 detects a near field communication signal, the mobile phone 10 can detect the card swipe triggering instruction. In other embodiments, the mobile phone 10 can detect the user's operation for swiping the card on the mobile phone 10, for example, detecting that the user presses the power button of the mobile phone 10 twice in succession when the screen of the mobile phone 10 is turned off. A card swipe trigger command is detected.

It can be understood that in other embodiments, the card swipe triggering instruction can also be other instructions, such as voice instructions, instructions triggered according to the location of the mobile phone 10 , etc. The embodiments of the present application do not limit the form in which the card swiping triggering instruction is detected by the mobile phone 10 .

It can be understood that in some embodiments, after the mobile phone 10 detects the card swiping triggering instruction, the default card of the mobile phone 10 can be activated. Among them, the default card can be the default simulation card set by the user in the application (such as wallet application 11A) used by the mobile phone 10 to manage the NFC simulation card, or it can be the simulation card used when the mobile phone 10 last swiped the card, or it can also be the mobile phone 10. 10 The simulation card determined based on the location and application scenario of the mobile phone 10 is not limited here. When the NFC function is activated on Mobile Phone 10, the default card will be activated first.

In some embodiments, the user can set the default card of the phone 10 through the wallet application 11A.

For example, FIGS. 5A to 5D show a schematic interface diagram of the wallet application 11A displayed on the mobile phone 10 when the user sets the default card of the mobile phone 10 through the wallet application 11A. Referring to Figures 5A to 5D, the user can first enter the setting interface shown in Figure 5B by clicking on the "My" control 51 shown in Figure 5A; and then click on the "Card Swipe Settings" control 52 shown in Figure 5B Click to enter the card setting interface shown in Figure 5C; then click on the "default card" control 53 shown in Figure 5C to enter the default card setting interface shown in Figure 5D; finally, click on the "default card" control 53 shown in Figure 5C Select the default card of the mobile phone 10 in the default card setting interface. For example, by clicking the "Smart Flash Card" control 54, select the Smart Flash Card as the default card of the mobile phone 10.

It can be understood that after the mobile phone 10 selects "Smart Flash Card" as the default card, the mobile phone 10 can automatically set different default cards according to different scenarios. For example, the last simulated card used by the mobile phone 10 is used as the default card, or according to the mobile phone 10 10. The geographical location where the user is located, selects the simulation card frequently used by the user in that geographical location as the default card, etc.

It can be understood that in other embodiments, the user can also set the default card of the mobile phone 10 through other methods, which is not limited here.

S402: Determine whether a near field communication signal is detected. If a near field communication signal is detected, it means that the mobile phone 10 has been close to the NFC card reader device, such as the aforementioned NFC card reader 01; otherwise, step S402 is repeated.

Specifically, in some embodiments, when the NFC controller 14 of the mobile phone 10 detects a near field communication signal, it may send information that the near field communication signal is detected to the wallet application 11A or the NFC service 11B.

It can be understood that in some embodiments, the mobile phone 10 may not determine whether a near field communication signal is detected, but directly go to step S403 after executing step S401, which is not limited here.

S403: Determine whether AID is received. If AID is received, it means that the current card swiping scene is a scene with AID, such as a transportation card, bank card, etc. scene, and go to step S404; otherwise, it means that the current scene is a scene without AID, and go to step S405.

It can be understood that for scenarios with AID, such as scenarios where the mobile phone 10 simulates a bank card or a transportation card, when the corresponding card reading device (such as the aforementioned NFC card reader 01) detects a device with an NFC function, for example, when a nearby card is detected, When communicating in the field, the AID corresponding to the scene can be actively sent through NFC technology, so that the electronic device with NFC function can select the corresponding simulation card based on the AID to complete the card swiping.

S404: Determine whether the received AID exists in the mobile phone 10.

When the mobile phone 10 receives the AID, it detects whether the received AID exists in the mobile phone 10 . If the AID exists in the mobile phone 10, it means that there is a simulation card corresponding to the AID in the mobile phone 10, and go to step S405; otherwise, it means that the simulation card corresponding to the AID does not exist in the mobile phone 10, and go to step S406.

For example, in some embodiments, the AID list of cards with AID in the mobile phone 10 can be stored in the aforementioned eSE 13, so that a trusted application in the TEE 12 of the mobile phone 10, such as the wallet application TA 12A, determines whether the card in the mobile phone 10 There is a received AID.

For example, in other embodiments, the AID list of simulated tablets with AID stored in the mobile phone 10 can also be stored in the memory of the mobile phone 10, so that the application/service in the REE 11 of the mobile phone 10, such as a wallet application, can 11A and NFC service 11B to determine whether the received AID exists in the mobile phone 10 . The embodiment of the present application does not limit the location where the AID list is stored.

S405: Terminate the activation state of the default card based on TEE 12 and eSE 13, and activate the simulation card corresponding to the received AID.

After determining that the received AID exists in the mobile phone 10, the mobile phone 10 terminates the activation state of the default card based on the TEE 12 and eSE 1, and activates the analog chip corresponding to the received AID.

In some embodiments, the mobile phone 10 can first interact with the eSE 13 and the NFC controller 14 through the wallet application TA 12A. For example, the wallet application TA 12A sends an instruction to terminate the activation state of the default card to the eSE 13; and after the activation of the default card When the status has been terminated, interact with the eSE 13 through a preset interface, such as the Open Mobile Application Programming Interface (OMAPI), such as writing the received AID corresponding to the NFC controller 14 Card information of the simulated card to activate the simulated card. That is to say, under the technical architecture shown in Figure 3, every time the mobile phone 10 activates a simulation card, it must first terminate the activation state of the currently activated simulation card (such as the default card), and then activate the simulation card to be activated. (For example, write the card information of the simulated card to be simulated into the NFC controller 14). In the process of activating an emulated card on the mobile phone 10, it is necessary to interact with the eSE 13 and/or the NFC controller 14 multiple times through the trusted application in the TEE 12.

S406: Prompt that card swiping failed.

When the mobile phone 10 determines that the received AID does not exist in the mobile phone 10, it prompts the user that the card swiping failed. For example, in some embodiments, the mobile phone 10 can display the prompt box 61 shown in FIG. 6 to prompt the user to "Failed to swipe the card, please try again."

It can be understood that in other embodiments, the mobile phone 10 can also prompt the user to fail to swipe the card through other forms, such as playing sound effects, voices, etc. for failure to swipe the card. The embodiments of the present application do not limit the specific form of prompting the user to fail to swipe the card.

S407: Determine whether there is a simulation card without AID in the mobile phone 10. If there is a simulation card without AID in the mobile phone 10, it means that there may be a simulation card without AID corresponding to the current scene in the mobile phone 10, and go to step S408; otherwise, it means that there is no simulation card in the mobile phone 10. If there is a simulation card without AID corresponding to the current scene, go to step S406.

In some embodiments, the mobile phone 10 can determine whether there is a simulation card that does not have an AID in the mobile phone 10 by determining whether each simulation card stored in the eSE 13 has an AID. In the eSE 13, there is a situation where the simulation card does not have an AID. Next, confirm that there is a simulation card without AID in the mobile phone 10.

In other embodiments, the mobile phone 10 can also determine whether there is a simulation card without AID in the mobile phone 10 based on the card type identification of the simulation card stored in the mobile phone 10, such as the Select Acknowledge (SAK) identification. For example, in some embodiments, the mobile phone 10 may determine that there is a simulation card without AID in the mobile phone 10 when there is a simulation card with SAK=08 in the mobile phone 10 .

It can be understood that the mobile phone 10 can also use other methods to determine whether there is a simulation card without AID in the mobile phone 10, which is not limited here.

It can be understood that the simulation card with or without AID can be an access control card, a membership card, etc., or other simulation cards, which are not limited here.

S408: Terminate the activation status of the current card based on TEE 12 and eSE 13, and select a simulated card without AID for activation.

When there are multiple simulation cards without AID in the mobile phone 10, the activation state of the currently activated simulation card is terminated based on TEE 12 and eSE 13, and one of the simulation cards without AID is selected for activation.

It can be understood that after the mobile phone 10 activates a simulation card without AID, the simulation card without AID can be marked as activated, so that the next time you select an activated simulation card without AID, you will not repeat the selection. This is a simulation card without AID to increase switching speed.

It can be understood that the current card can be the default card of the mobile phone 10, or it can be the simulated card that was last activated by the mobile phone 10.

In some embodiments, when the mobile phone 10 selects one of the multiple simulated cards without AID to activate, it can select according to the storage order of the simulated cards without AID, or according to the use of the simulated cards without AID. Frequency selection can also be selected based on the current location of the mobile phone 10. It can be understood that in other embodiments, the mobile phone 10 can also use other methods to select one of the simulation cards without AID for activation, such as randomly selecting an unactivated simulation card without AID for activation, which is not the case here. Make limitations.

Specifically, the mobile phone 10 can send a termination activation instruction and an activation instruction to the NFC controller 14 through a trusted application in the mobile phone 10, such as the wallet application TA 12A. After receiving the activation termination instruction/activation instruction, the NFC controller 14 terminates The activation status of the currently activated simulation card/or activate the selected simulation card without AID.

S409: Determine whether the termination conditions are met. If it is determined that the termination condition is met, end this card swiping session; otherwise, go to step S410 for further judgment.

In some embodiments, the termination condition may include at least one of the following conditions: the mobile phone 10 does not detect a near field communication signal beyond the preset waiting time (that is, the mobile phone 10 has moved away from the NFC card reader 01), the NFC function of the mobile phone 10 has expired. Closed, the current card swiping time has exceeded the preset card swiping time, the card swiping is successful, and the mobile phone 10 detects the user's operation or instruction to cancel the card swiping on the mobile phone 10.

S410: Determine whether all simulation cards without AID have been activated. If it is determined that all the simulation cards without AID have been activated, it means that the card swiping failed this time, and go to step S406; otherwise, go to step S408 to activate the next simulation card without AID.

It can be understood that in other embodiments, when the mobile phone 10 determines that all simulation cards without AID have been activated, if a near field communication signal is still detected, all the simulated cards without AID can be cleared. Activated marks, re-activate the simulated cards without AID one by one and try to swipe the card, so as to avoid card swiping failure due to other reasons when the mobile phone 10 activates the correct simulated card and increase the success rate of swiping the card.

It can be understood that the execution order of steps S401 to S410 is just an example. In other embodiments, the execution order of some steps can be adjusted, some steps can be merged or split, and some steps can also be added or deleted. The application examples are not limiting.

Through the method provided by the embodiment of the present application, the mobile phone 10 can simulate a card without AID through NFC, such as an access control card. Automatically select the simulated card without AID stored in the mobile phone 10 to try until the card swiping is successful or the card swiping is terminated, without the user having to manually select, which improves the user's card swiping experience.

In the above embodiment, the card information of the simulated card without AID (such as access control card) is stored in the eSE 13. In the process of selecting the simulated card without AID stored in the mobile phone 10 to swipe the card, the mobile phone 10 activates a card. Each simulated card requires a trusted application in TEE 12 (such as wallet application TA 12A) to interact with eSE 13 to terminate the activation status of the activated simulated card and activate the simulated card to be activated. Since it takes a long time to terminate the activation status of the card and activate the card through TEE 12, eSE 13, and NFC controller 14, the operation of terminating activation and activation usually takes about 0.7 seconds. The simulated card without AID stored in the mobile phone 10 When the quantity is large, the card swiping time will be longer, affecting the user's card swiping experience. In addition, due to the small storage space of eSE 13 (usually 50KB), if you want to store more simulation cards, you need to equip the mobile phone 10 with multiple eSEs or increase the storage space size of eSE, which increases development costs.

In order to solve the above problem, embodiments of the present application provide another technical architecture of an NFC-based card swiping method. By storing the card information of a simulation card with lower security requirements (such as a simulation card without AID) in the memory of the mobile phone 10 instead of storing it in the eSE. And during the process of swiping this type of simulated card, the application in the REE of the mobile phone 10 or the trusted application in the TEE of the mobile phone 10 reads the card information of the simulated card without AID from the memory, and stores the card The information is written to the NFC controller to realize automatic selection of the simulated card. Since there is no need to terminate the activation and activation operations every time a simulated card is selected, and there is no need for the participation of TEE 12 and eSE13, it can save the time of swiping the card and improve the user experience. In addition, since the card information of the analog card with lower security requirements is stored in the memory of the mobile phone 10 without occupying the space of the eSE 13, the development cost of the mobile phone 10 can be reduced while increasing the simulation card data supported by the mobile phone 10.

Specifically, FIG. 7 shows a schematic technical architecture diagram of another NFC-based card swiping method according to some embodiments of the present application.

As shown in Figure 7, the software layer of the mobile phone 10 includes TEE 12 and REE 11, and the hardware layer includes eSE 13, NFC controller 14 and memory 103. In the schematic diagram of the technical architecture shown in Figure 6 and that shown in Figure 3, modules with the same labels have similar functions. For details, please refer to the relevant description of the embodiment shown in Figure 3. The differences from the embodiment shown in Figure 3 will be introduced below. at.

Referring to Figure 7, in the embodiment of the present application, the mobile phone 10 stores card information of simulated cards with high security requirements (bank cards with AID, transportation cards, etc., such as card A1, card A2 and card A3 shown in Figure 7). It is stored in the eSE 13, and the card information of simulation cards with lower security requirements (simulation cards without AID, etc., such as card B1, card B2, and card B3 shown in Figure 7) is stored in the memory 103. After the mobile phone 10 detects the card swipe triggering command, if it receives the AID, it will refer to the aforementioned embodiment to realize the selection of the simulated card through the interaction between the trusted application in the TEE 12, the eSE 13 and the NFC controller 14; if it does not receive the AID AID reads the card information of the simulated card from the memory 103 through the application program or service in the REE 11 or TEE 12, and writes the card information into the NFC controller 14 to complete the selection of the simulated card.

The technical solution of the embodiment of the present application will be introduced below in conjunction with the technical architecture shown in Figure 7 .

Specifically, FIG. 8 shows a schematic flow chart of another NFC-based card swiping method according to some embodiments of the present application. The execution subject of this process is the mobile phone 10. As shown in Figure 8, the method includes the following steps.

S801: A card swipe trigger instruction is detected.

When the mobile phone 10 detects the card swiping trigger instruction, it triggers the near field communication simulation card selection method provided by the embodiment of the present application. For details, please refer to step S401, which will not be described again here.

S802: Determine whether a near field communication signal is detected.

The mobile phone 10 determines whether a near field communication signal is detected. If a near field communication signal is detected, it means that the mobile phone 10 is close to the NFC card reader device and goes to step S803. Otherwise, step S802 is repeated and the judgment is continued. For details, reference may be made to step S402, which will not be described again here.

S803: Determine whether AID is received.

The mobile phone 10 determines whether it has received AID. If it receives the AID, it means that the simulation corresponding to the NFC card reading device currently close to the mobile phone 10 The card information of the card is stored in the eSE 13, and the process goes to step S804; otherwise, it means that the card information of the simulated card corresponding to the NFC card reading device currently close to the mobile phone 10 is stored in the memory 103, and the process goes to step S807.

S804: Determine whether the received AID exists in the mobile phone 10.

The mobile phone 10 determines whether the received AID exists in the mobile phone 10. If the received AID exists in the mobile phone 10, then go to step S805, otherwise go to step S806. For the specific process, please refer to the aforementioned step S404, which will not be described again here.

S805: Terminate the activation state of the default card based on TEE 12 and eSE 13, and activate the simulation card corresponding to the received AID.

When the mobile phone 10 determines that the stored AID has been received, it terminates the activation state of the default card based on the TEE 12 and eSE 13 and activates the simulated card corresponding to the received AID. For the specific process, please refer to the aforementioned step S405, which will not be described again here.

S806: Prompt that card swiping failed.

When the mobile phone 10 determines that the AID has not been received and there is no analog card without AID in the mobile phone, it prompts that the card swiping fails. For the specific prompting method, please refer to the aforementioned step S406, which will not be described again here.

S807: Determine whether there is a simulation card without AID in the mobile phone 10.

When the mobile phone 10 determines that it has not received AID, it determines whether there is a simulation card without AID in the mobile phone 10 through the wallet application 11A in the REE 11. If there is a simulation card without AID, it means that the mobile phone 10 may store For the card information of the simulated card corresponding to the NFC card reading device that the mobile phone 10 is currently close to, go to step S808; otherwise, it means that the card information of the simulated card corresponding to the NFC card reading device that the mobile phone 10 is currently close to is not stored in the mobile phone 10, go to Step S806.

In some embodiments, the mobile phone 10 may determine that there is a simulation card without AID in the mobile phone 10 when the card information is stored in the file used to store the card information of the simulation card without AID; in other embodiments , the mobile phone 10 may also determine that there is a simulated card without AID in the mobile phone 10 when the card information without AID is stored in the mobile phone 10 . The mobile phone 10 can also determine whether there is a simulation card without AID in the mobile phone 10 through other methods. For example, the mobile phone 10 can determine if there is a simulation card with SAK=08 in the stored card information of the simulation card. There are emulation cards in 10 that do not have AID. It can be understood that the embodiment of the present application does not limit the specific method of determining whether there is a simulation card without AID in the mobile phone 10 .

It can be understood that simulation cards without AID can be access control cards, membership cards, etc., or other cards. There is no limitation here on having AID.

S808: Terminate the activation state of the default card.

When the mobile phone 10 determines that there is a simulation card without AID in the mobile phone 10, it terminates the activation state of the default card.

For example, when the card information of the default card is stored in eSE 13, the mobile phone 10 can interact with the eSE 13 through the aforementioned wallet application TA 12A to terminate the activation state of the default card.

For another example, when the card information of the default card is stored in the memory 103 of the mobile phone 10, the mobile phone 10 can interact with the NFC controller 14 through the aforementioned wallet application 11A to terminate the activation state of the default card.

In other embodiments, the mobile phone 10 can also terminate the activation state of the default card through other applications/services, which is not limited here.

It can be understood that in some embodiments, when the default card is an analog card without AID, for example, when the default card is an access control card, the mobile phone 10 may skip step S808 after executing step S807 and directly Go to step S809. Therefore, the time of terminating the activation state of the default card can be saved, and the card swiping speed can be further improved.

S809: Obtain card information of a simulated card without AID from the memory 103, and write the acquired card information into the NFC controller 14.

When there is a simulation card without AID in the mobile phone 10 , the mobile phone 10 obtains the card information of a simulation card without AID from the memory 103 , and writes the obtained card information into the NFC controller 14 . For example, the mobile phone 10 can utilize the aforementioned wallet application 11A, Select a simulation card without AID from the memory, and write the card information of the simulation card without AID into the NFC controller 14. After receiving the card information, the NFC controller 14 passes the card information through NFC technology is transmitted to NFC card reading devices, such as the aforementioned NFC card reader 01.

It can be understood that the card information of the simulation card without AID can include the UID of the simulation card without AID, and can also include the UID and SAK of the simulation card without AID. It can also include more information, which is not limited here. .

In some embodiments, when the mobile phone 10 obtains the card information of the simulated cards without AID from the memory 103, it can obtain it according to the card information storage order of the simulated cards without AID, or it can obtain it according to the card information of the simulated cards without AID. It can be obtained based on the usage frequency, and can also be obtained based on the current location of the mobile phone 10. It can be understood that in other embodiments, the mobile phone 10 can also use other methods to determine which card information of a simulation card without AID to obtain, such as randomly selecting the card information of an unselected simulation card without AID. , no limitation is made here.

In some embodiments, the NFC controller 14 may include a contactless front-end chip (Contactless Frontend, CLF), and the mobile phone 10 completes the card swiping by updating the card information of the simulated card without AID to the CLF. Among them, CLF is an NFC control chip used to send card information to the card reading device through the NFC transmitting antenna.

It can be understood that in some embodiments, after obtaining the card information of a simulation card without AID, the mobile phone 10 can also mark the selection status of the simulation card without AID as selected to avoid obtaining the card information next time. When the card information of a simulated card without AID is obtained, the card information of the simulated card without AID is repeatedly obtained to increase the card swiping speed.

It can be understood that after the mobile phone 10 writes the card information of an analog card without AID into the NFC controller 14, the card reading device, such as the aforementioned NFC card reader 01, can receive the analog card without AID. card information. For example, FIG. 9 shows a schematic log diagram of the data transmitted by the mobile phone 10 during the process of automatically switching to a simulation card without AID obtained by using an NFC air interface packet capture tool. Referring to Figure 9, the row corresponding to serial number 57 records the data corresponding to the UID sent by mobile phone 10 received by NFC card reader 01, where "11 11 11 11" is the UID of the simulation card without AID; the serial number The row corresponding to 58 records the data corresponding to the SAK sent by the mobile phone 10 to the card reader 01, where "18" is the SAK of the simulated card (that is, the simulated card without AID). Continuing to refer to Figure 9, in the case where the above-mentioned simulation card without AID with the UID of "11 11 11 11" does not have the access authority of the above-mentioned door 04, refer to the row corresponding to the serial number 80, the mobile phone 10 can communicate with the NFC card reader 01 Send the UID data of another simulated card without AID, where "33 33 33 33" is the UID of the simulated card; then, referring to the serial number 81 and the corresponding line, NFC card reader 01 receives the UID "33 33 33 33", referring to the row corresponding to serial number 82, mobile phone 10 sends the SAK data of the simulation card with UID "33 33 33 33" to NFC card reader 01, where "08" is the SAK of the simulation card.

S810: Determine whether the termination condition is met.

The mobile phone 10 determines whether the termination condition is met, and if the termination condition is met, the card swiping session ends, otherwise, the process goes to step S811.

In some embodiments, the termination condition may include at least one of the following conditions: the mobile phone 10 does not detect a near field communication signal beyond the preset waiting time (that is, the mobile phone 10 has moved away from the NFC card reader 01), the NFC function of the mobile phone 10 It has been closed, the current card swiping time has exceeded the preset card swiping time, the card swiping is successful, and the mobile phone 10 detects the user's operation or instruction to cancel the card swiping on the mobile phone 10.

S811: Determine whether all simulation cards without AID have been selected.

The mobile phone 10 determines whether all the simulation cards without AID have been selected. If it is determined that the mobile phone 10 has selected all the simulation cards without AID, then go to step S806; otherwise, go to step S809 to obtain the next card without AID. The card information of the simulated card with AID is written to the NFC controller 14.

It can be understood that in some embodiments, when the mobile phone 10 determines that all simulation cards without AID have been selected, the selection status of all simulation cards without AID can be set to unselected, so that the mobile phone 10 can The next time you swipe your card, you can select one of the simulated cards without AID whose selection status is unselected to swipe your card.

It can be understood that in some embodiments, after the mobile phone 10 determines that all simulation cards without AID have been selected, if the near field communication signal is still detected, the selected status of all simulation cards without AID can also be changed. All are set to unselected, and go to step S809 to write the card information of each simulated card without AID into the NFC controller 14 one by one for the next round of attempts to prevent the mobile phone 10 from correctly emulating the simulated card without AID. After the card information of the card is written into the NFC controller 14, if the card swiping fails due to other reasons, the success rate of the card swiping is increased.

It can be understood that the execution order of the aforementioned steps S801 to S811 is just an example. In other embodiments, the execution order of some steps can be adjusted, some steps can be merged or split, and some steps can also be added or reduced. Limitations here.

Through the method provided by the embodiment of the present application, since the card information of the stored analog card without AID is obtained from the memory 103 of the mobile phone 10 and the card information is written to the NFC controller 14, there is no need to interact with the TEE 12 and Interaction with eSE 13 takes less time (usually one acquisition and writing operation takes about 0.1 seconds). Compared with the embodiment shown in Figure 4, when there are many simulation cards without AID stored in the mobile phone 10, you can Save time on card swiping and improve user experience. For example, in the case where the card information of 10 simulated cards without AID is stored in the mobile phone 10, in the worst case, the embodiment shown in Figure 4 takes 7 seconds from selecting a card to successfully swiping the card, and this application implements The method provided in the example only takes 1 second, which greatly shortens the user's waiting time and improves the user experience. In addition, since the card information of the simulated card without AID is stored in the memory 103 of the mobile phone 10 instead of being stored in the eSE 13, the mobile phone 10 can store more cards without increasing the storage space or quantity of the eSE and reducing the cost. development costs.

In particular, in the embodiment shown in Figure 4, since the activation and termination of activation of the card requires interaction between the eSE 13 and the NFC controller 14, more power will be consumed. Therefore, for the method provided by the embodiment of the present application, Since the process of switching to a simulation card without AID does not require the participation of the eSE 13, the power consumption of the mobile phone 10 can be saved and the battery life of the mobile phone 10 can be improved. For example, FIG. 10 shows the battery of the mobile phone 10 when the mobile phone 10 terminates activation/activation of the simulated card through the eSE 13, reads the card information of the simulated card from the memory 103 and writes it to the NFC controller 14, according to some embodiments of the present application. changes in current. Referring to Figure 10, it can be seen that when the eSE 13 terminates activation/activation of the simulated card, the current of the battery of the mobile phone 10 increases significantly, and during the process of reading the card information of the simulated card from the memory 103 and writing it to the NFC controller 14 , the current of the battery of the mobile phone 10 is basically unchanged, where I ₀ is the current of the battery when the mobile phone 10 does not simulate a physical card through NFC.

The methods provided by the embodiments shown in Figure 4 and Figure 8 are applicable to all electronic devices equipped with eSE. The embodiment of the present application also provides another NFC-based card swiping method, which can be applied to devices with NFC functions but excluding eSE. Electronic devices, such as smart bracelets, etc., enable such electronic devices to automatically select a simulated card to complete card swiping when multiple simulated cards without AID are stored.

It can be understood that the method provided by the embodiment of the present application can be applied to any electronic device with NFC function, but does not include eSE, such as smart watches, smart bracelets, etc. For the convenience of description, the smart bracelet 20 is taken as an example for introduction below.

For example, referring to Figure 11, the software layer of the smart bracelet 20 includes REE 201, which is used to run lightweight systems, such as Wear OS ^TM , Lite OS ^TM, etc., and the smart bracelet 20 is used to manage NFC function applications, such as NFC Application 2011 runs on the lightweight system described above. The hardware related to the NFC function in the smart bracelet 20 includes a memory 202 and an NFC controller 203. The memory 202 is used to store card information of different simulated cards, and the NFC controller 203 is used to send the card information of the simulated cards to NFC through NFC technology. Card reading equipment or card information that reads physical cards.

The following describes the technical solution of the embodiment of the present application in conjunction with the technical architecture shown in Figure 11.

Specifically, FIG. 12 shows a schematic flow chart of yet another NFC-based card swiping method according to some embodiments of the present application. As shown in Figure 12, the execution subject of this process is the smart bracelet 20. In Figure 12, the execution process of step S1201 to step S1203 can refer to the aforementioned step S801 to step S803, the execution process of step S1207 can refer to the aforementioned step S807, and the execution process of step S1208 to step S1210 can refer to the aforementioned step S809 to step S811. The following is The execution process of step S1204 to step S1206 that is different from the previous embodiment will be introduced.

S1204: Determine whether the received AID exists in the smart bracelet 20.

After receiving the AID, the smart bracelet 20 can compare the received AID with the AID of the card information of each simulated card stored in the memory 202 to determine whether the received AID exists in the smart bracelet 20 .

S1205: Read the card information of the simulated card corresponding to the received AID from the memory 202, and write the card information into the NFC controller 203.

When the smart bracelet 20 determines that the received AID exists in the smart bracelet 20 , it reads the card information of the analog card corresponding to the received AID from the memory 202 , and writes the card information to the NFC controller 203 , so that the NFC controller 203 sends the card information to the card reading device through NFC technology.

S1206: Prompt that card swiping failed.

When the smart bracelet 20 determines that there is no AID received by the smart bracelet 20, it prompts that the card swiping fails. For example, the smart bracelet 20 may display a card swiping failure message, vibrate, emit a prompt sound, flash the breathing light of the smart bracelet 20, etc.

It can be understood that in some embodiments, if the smart bracelet 20 does not support the simulation of a physical card with AID, the smart bracelet 20 directly executes step S1207 when detecting a near field communication signal in step S1202 without executing The contents of step S1203 to step S1205.

Through the method provided by the embodiments of this application, electronic devices that support NFC functions but do not have eSE can also automatically select simulated cards for card swiping, which improves user experience.

The card opening process of the simulated card in each of the above embodiments is introduced below.

First, under the technical architecture shown in Figure 3, the process of the mobile phone 10 obtaining the card information of the physical card and storing it in the eSE 13 of the mobile phone 10 is introduced.

Specifically, FIG. 13 shows a schematic flow chart of a near field communication simulation card opening method according to some embodiments of the present application. The execution subject of this process is the mobile phone 10. As shown in Figure 13, the process includes the following steps.

S1301: Enter card opening mode.

The application in the mobile phone 10 that manages the NFC function, such as the aforementioned wallet application 11A, enters the card opening mode after detecting the user's card opening operation. It can be understood that after the mobile phone 10 enters the card opening mode, the NFC controller 14 of the mobile phone 10 enters the card reader mode.

For example, FIG. 14A to FIG. 14E show a schematic interface diagram of the wallet application 11A displayed on the mobile phone 10 when the mobile phone 10 enters the card opening mode according to some embodiments of the present application. Referring to Figures 14A to 14E, the user can enter the card package interface shown in Figure 14B by clicking the "card package" control 141 shown in Figure 14A; and then click the "+" control shown in Figure 14B to enter the card package interface shown in Figure 14C. The add card interface shown in Figure 14C; secondly, use the controls in the add card interface shown in Figure 14C to select the type of card to add, for example, by clicking on the "key" control 143 to enter the add key interface shown in Figure 14D; finally, by clicking on Figure 14D The "access card" control 144 in the key adding interface shown operates the mobile phone 10 to enter the card opening mode. For example, after detecting the user's click operation on the "access card" control 144, the mobile phone 10 enters the card opening mode and displays Figure 14E The simulated access card interface shown.

It can be understood that in other embodiments, the mobile phone 10 can also enter the card opening mode through other methods, such as receiving the user's voice command, card opening gesture, etc., to enter the card opening mode, which is not limited by the embodiments of this application.

S1302: Determine whether the physical card is detected.

After the mobile phone 10 enters the card opening mode, it determines whether the physical card is detected. If detected, proceed to step S1303; otherwise, repeat step S1302 to continue detection.

For example, the mobile phone 10 may determine that a physical card is detected when a near field communication signal is detected.

S1303: Obtain the card information of the physical card and determine whether the physical card has AID.

When the mobile phone 10 detects the physical card, it obtains the card information of the physical card and determines whether the physical card has AID. If it is determined that the physical card has AID, go to step S1304; otherwise, go to step S1305.

In some embodiments, the mobile phone 10 can determine whether the physical card has AID based on the SAK in the obtained card information. For example, if the SAK in the obtained card information is 08, it is determined that the physical card does not have AID. It can be understood that in other embodiments, the mobile phone 10 can also determine whether the physical card has AID in other ways, such as determining whether the physical card has AID according to the length of the UID in the card information, which is not limited in the embodiments of this application.

It can be understood that in some embodiments, the mobile phone 10 can obtain the card information of the physical card from the NFC controller 14 through an application program in the REE 11, such as the wallet application 11A or the NFC service 11B.

It can be understood that in other embodiments, the mobile phone 10 can also obtain the card information of the physical card from the NFC controller 14 through an application program in the TEE 12, such as the wallet application TA 12A. It can be understood that the wallet application TA 12A can obtain the card information of the physical card from the NFC controller 14 through the eSE 13, or can directly obtain the card information of the physical card from the NFC controller 14, which is not limited here.

S1304: Use the card opening logic corresponding to other physical cards.

When the mobile phone 10 determines that the physical card has AID, it uses the card opening logic corresponding to other physical cards.

It can be understood that the mobile phone 10 is preset with card opening logic for different types of physical cards. For example, for bank cards, due to high security requirements, a complex security verification process is required. The mobile phone 10 can perform security verification through the corresponding server, and If the verification is successful, the card information of the bank card is written to eSE 13.

S1305: Get the first file from the server and write the first file to eSE 13.

It can be understood that the first file includes the card opening logic of the simulated card without AID and the data writing method of eSE 13. eSE 13 can write the card information into eSE 13 based on the first file. The first file is generally stored in a server, such as a Trusted Service Manager (TMS) server, and is obtained from the server by a trusted application in the mobile phone 10, such as the aforementioned wallet application TA 12A when opening a card.

It can be understood that in some embodiments, the first file may include a Java applet, and the Java applet includes running logic for writing card information into the eSE 13.

S1306: Based on the first file, write the card information of the physical card into eSE 13.

Based on the card opening logic in the first file, the mobile phone 10 writes the card information of the physical card into the eSE 13. For example, the mobile phone 10 can use a trusted application, such as the aforementioned wallet application TA 12A, to write the card information of the physical card to the eSE based on the card opening logic of the simulated card without AID in the first file and the data writing method of the eSE 13 In 13, card opening is completed.

In the aforementioned card opening process corresponding to the technical architecture shown in Figure 3, the mobile phone 10 needs to obtain the first file from the server, and based on the card opening logic of the simulated card without AID and the data of the eSE 13 recorded in the first file The writing method is to write the read card information into eSE 13, which takes a long time. It takes about 20 seconds to obtain the first file from the server, and it takes 20 seconds to write the card information of the physical card into eSE 13. It takes a long time to open a card. Corresponding to the technical architecture shown in Figure 7, since only the card information of the simulated card without AID, such as UID and SAK, needs to be stored in the memory 103, there is no need to write the card information to the eSE 13, which can be shortened. The opening time of the simulation card without AID. In addition, since the first file is stored in the server, the mobile phone 10 must be able to connect to the server, that is, be able to access the network, before opening the card, which affects the user experience.

Specifically, FIG. 15 shows a schematic flow chart of another near field communication simulation card opening method according to some embodiments of the present application. The execution subject of this process is the mobile phone 10. For the execution process of steps S1501 to S1504, reference can be made to the aforementioned steps S1301 to S1304, which will not be described again here. Differences from the embodiment shown in FIG. 13 will be introduced below.

S1505: Store the card information of the physical card in the memory 103.

For example, when the mobile phone 10 determines that the physical card is a simulated card without AID, the UID and SAK of the physical card can be stored in the memory 103 of the mobile phone 10 .

It can be understood that in some embodiments, the mobile phone 10 can also store only the UID of the physical card, and can also store other information of the physical card. No limitation is made here.

It can be understood that in some embodiments, the mobile phone 10 can also upload the card information of each physical card stored in the mobile phone 10 to the server when the mobile phone 10 can access the network, so that the user can obtain the card from the server through other electronic devices. information, and use other electronic devices to simulate the simulation cards corresponding to each card information.

Through the card opening method provided by the embodiment of this application, the mobile phone 10 does not need to access the server when opening the card, nor does it need to write the card information to the eSE 13 through the aforementioned first file. Instead, the card information of the physical card is directly stored in the mobile phone. In the memory 103, it takes less time (usually less than 1 second to store the information of a card), which reduces the card opening time of the mobile phone 10 and improves the user experience.

Furthermore, FIG. 16 shows a schematic flow chart of yet another near field communication simulation card opening method according to some embodiments of the present application. The execution subject of this process is the smart bracelet 20. As shown in Figure 16, the process includes the following steps.

S1601: Enter card opening mode.

The smart bracelet 20 can establish a binding relationship with other electronic devices, such as the aforementioned mobile phone 10, and then the mobile phone 10 controls the smart bracelet 20 to enter the card opening mode.

S1602: Determine whether the physical card is detected.

The smart bracelet 20 determines whether the physical card is detected. If detected, the process goes to step S1603. Otherwise, step S1602 is repeated to continue detection.

For example, the smart bracelet 20 may determine that the physical card is detected when a near field communication signal is detected.

S1603: Determine whether the physical card is supported.

The smart bracelet 20 determines whether the physical card is supported. If so, go to step S1605; otherwise, go to step S1604.

In some embodiments, the smart bracelet 20 can determine whether to support the physical card based on the type of the physical card. For example, the smart bracelet 20 can obtain the SAK of the physical card, and when the obtained SAK is in the list of SAKs supported by the smart bracelet 20, it is determined that the smart bracelet 20 supports the physical card.

S1604: Prompt card activation failed.

When the smart bracelet 20 determines that the smart bracelet 20 does not support the current physical card, it prompts that the card activation fails. For example, the smart bracelet 20 prompts the user to fail to open a card through breathing light, prompt sound, display prompt message, vibration, etc.

S1605: Obtain the card information of the physical card and store the card information in the memory 202.

When the smart bracelet 20 determines that the smart bracelet 20 supports the current physical card, it obtains the card information of the physical card and stores the card information in the memory 202 . Among them, the card information of the physical card includes but is not limited to the UID, AID, SAK, etc. of the physical card.

It can be understood that for some smart bracelets 20 , the card information stored in the electronic device can also be shared with the smart bracelet 20 through an electronic device connected to the smart bracelet 20 .

Through the card opening method provided by the embodiment of the present application, even if the smart bracelet 20 does not have an eSE chip, the card information of the simulated card without AID can be stored in the memory, so as to facilitate the method provided by the embodiment shown in Figure 12 To simulate a simulated card without AID, realize card swiping and improve the user experience.

Further, FIG. 17 shows a schematic structural diagram of a mobile phone 10 according to some embodiments of the present application.

As shown in Figure 17, the mobile phone 10 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, and a battery 142. Antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, Display 194, and subscriber identification module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light. Sensor 180L, bone conduction Sensor 180M and so on.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors.

The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system. In some embodiments, the processor 110 can call and execute the execution instructions of the NFC-based card swiping method provided by various embodiments of the present application stored in the memory to implement the NFC-based card swiping method provided by the embodiments of the present application.

In some embodiments, processor 110 may include one or more interfaces. Interfaces can include integrated circuit (inter-integrated circuit, I2C) interface, integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, pulse code modulation (pulse code modulation, PCM) interface, serial peripheral interface (Serial Peripheral) Interface (SPI), universal asynchronous receiver/transmitter (UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, Subscriber identity module (SIM) interface, and/or universal serial bus (USB) interface, etc.

The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (derail clock line, SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 can separately couple the touch sensor 180K, charger, flash, camera 193, NFC controller, etc. through different I2C bus interfaces. For example, the processor 110 can be coupled to the NFC controller through the I2C interface to obtain card information from the NFC controller or write card information to the NFC controller.

The I2S interface can be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 can be coupled with the audio module 170 through the I2S bus to implement communication between the processor 110 and the audio module 170 . In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the I2S interface to implement the function of answering calls through a Bluetooth headset.

The PCM interface can also be used for audio communications to sample, quantize and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 through the PCM interface to implement the function of answering calls through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

The SPI interface is a full-duplex three-wire synchronous serial peripheral interface first proposed by Motorola ^TM . It adopts a master-slave mode (Master-Slave) architecture and supports one or more Slave devices. In some embodiments, the SPI interface can be used to couple the eSE so that the trusted application can obtain card information from the eSE or write card information to the eSE.

The UART interface is a universal serial data bus used for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 and the wireless communication module 160 . For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 . MIPI interface includes camera string serial interface (camera serial interface, CSI), display serial interface (display serial interface, DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate through the CSI interface to implement the shooting function of the mobile phone 10 . The processor 110 and the display screen 194 communicate through the DSI interface to realize the display function of the mobile phone 10 .

The GPIO interface can be configured through software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193, display screen 194, wireless communication module 160, audio module 170, sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, I2S interface, UART interface, MIPI interface, etc.

The USB interface 130 is an interface that complies with the USB standard specification, and may be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the mobile phone 10, and can also be used to transmit data between the mobile phone 10 and peripheral devices. It can also be used to connect headphones to play audio through them. This interface can also be used to connect other electronic devices, such as AR devices, etc.

The charging management module 140 is used to receive charging input from the charger. While the charging management module 140 charges the battery 142, it can also provide power to the electronic device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, the wireless communication module 160, and the like.

The wireless communication function of the mobile phone 10 can be realized through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied on the mobile phone 10 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be disposed in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

The wireless communication module 160 can provide applications on the mobile phone 10 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (bluetooth, BT), and global navigation satellite system. (global navigation satellite system, GNSS), frequency modulation (FM), NFC, infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

The NFC solution can be implemented by the technical architecture shown in Figure 3 and Figure 7 mentioned above. For example, in some implementations, the hardware layer may include the aforementioned eSE 13 and NFC controller 14.

The mobile phone 10 implements display functions through the GPU, the display screen 194, and the application processor. The GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, videos, etc. Display 194 includes a display panel. The display panel can use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light). emitting diode, AMOLED), Flexible light-emitting diodes (FLED), Mini-LED, Micro-LED, Micro-OLED, quantum dot light emitting diodes (QLED), etc. In some embodiments, the mobile phone 10 may include 1 or N display screens 194, where N is a positive integer greater than 1.

Camera 193 is used to capture still images or video. The object passes through the lens to produce an optical image that is projected onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to convert it into a digital image signal. ISP outputs digital image signals to DSP for processing. DSP converts digital image signals into standard RGB, YUV and other format image signals. In some embodiments, the mobile phone 10 may include 1 or N cameras 193, where N is a positive integer greater than 1.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone 10 . The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store computer executable program code including instructions, such as the aforementioned memory 103 . Internal memory 121 may include program storage areas and data storage areas. Among them, the program storage area can store the operating system, at least one application required for the function (such as the aforementioned wallet application 11A, wallet application TA 12A), etc. The data storage area can store data created during the use of the mobile phone 10 (such as the card information of the aforementioned simulation cards), etc. In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional applications of the mobile phone 10 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor 110 .

The mobile phone 10 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playback, recording, etc.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. Audio module 170 may also be used to encode and decode audio signals.

Speaker 170A, also called "speaker", is used to convert audio electrical signals into sound signals. For example, in some embodiments, the speaker 170A may be used to play a prompt sound indicating success/failure of a card swipe to the user.

Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals.

Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals.

The headphone interface 170D is used to connect wired headphones.

The pressure sensor 180A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, pressure sensor 180A may be disposed on display screen 194 . There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor may include at least two parallel plates of conductive material. When a force is applied to pressure sensor 180A, the capacitance between the electrodes changes. The mobile phone 10 determines the intensity of the pressure based on changes in capacitance. When a touch operation is performed on the display screen 194, the mobile phone 10 detects the intensity of the touch operation according to the pressure sensor 180A. The mobile phone 10 can also calculate the touch position based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch location but with different touch operation intensities may correspond to different operation instructions.

The acceleration sensor 180E can detect the acceleration of the mobile phone 10 in various directions (generally three axes). When the mobile phone 10 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of electronic devices and be used in horizontal and vertical screen switching, pedometer and other applications.

The ambient light sensor 180L is used to sense ambient light brightness. The mobile phone 10 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L also works with a proximity light sensor 180G cooperates to detect whether the mobile phone 10 is in the pocket to prevent accidental touching.

Fingerprint sensor 180H is used to collect fingerprints. Mobile phone 10 can use the collected fingerprint characteristics to achieve fingerprint unlocking, access to application locks, fingerprint photography, fingerprint answering incoming calls, etc. In the embodiment of this application, the main space and the private space can use different unlocking fingerprints for verification and login to ensure the security of private data in the private space. Users can verify different fingerprints on the mobile phone 10 to enter the main space and private space respectively.

Touch sensor 180K, also known as "touch device". The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation on or near the touch sensor 180K. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation may be provided through display screen 194 . In other embodiments, the touch sensor 180K may also be disposed on the surface of the mobile phone 10 in a position different from that of the display screen 194 .

Bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire the vibration signal of the vibrating bone mass of the human body's vocal part. The bone conduction sensor 180M can also contact the human body's pulse and receive blood pressure beating signals.

The buttons 190 include a power button, a volume button, etc. Key 190 may be a mechanical key. It can also be a touch button. The mobile phone 10 can receive key input and generate key signal input related to user settings and function control of the mobile phone 10 . For example, in some embodiments, when the mobile phone 10 presses the power button twice in a row while the screen is off, the NFC-based card swiping method provided by the embodiments of the present application is triggered.

The motor 191 can generate vibration prompts. For example, in some embodiments, the mobile phone 10 can prompt the user by vibrating when the user successfully/fails to swipe the card.

The indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, or may be used to indicate messages, missed calls, notifications, etc. For example, in some embodiments, the mobile phone 10 can prompt the user by setting the indicator light to different colors when the user successfully/fails to swipe the card.

The SIM card interface 195 is used to connect a SIM card.

It can be understood that the structure of the mobile phone 10 shown in the embodiment of the present application does not constitute a specific limitation on the mobile phone 10 . In other embodiments of the present application, the mobile phone 10 may include more or less components than shown in the figures, or some components may be combined, some components may be separated, or some components may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

Various embodiments of the mechanisms disclosed in this application may be implemented in hardware, software, firmware, or a combination of these implementation methods. Embodiments of the present application may be implemented as a computer program or program code executing on a programmable system including at least one processor, a storage system (including volatile and non-volatile memory and/or storage elements) , at least one input device and at least one output device.

Program code may be applied to input instructions to perform the functions described herein and to generate output information. Output information can be applied to one or more output devices in a known manner. For the purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

Program code may be implemented in a high-level procedural language or an object-oriented programming language to communicate with the processing system. When necessary, assembly language or machine language can also be used to implement program code. In fact, the mechanisms described in this application are not limited to the scope of any particular programming language. In either case, the language may be a compiled or interpreted language.

In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried on or stored on one or more transitory or non-transitory machine-readable (e.g., computer-readable) storage media, which may be operated by one or more processors Read and execute. For example, instructions may be distributed over a network or through other computer-readable media. Thus, machine-readable media may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including, but not limited to, floppy disks, optical disks, optical disks, read-only memories (CD-ROMs), magnetic Optical disc, read only memory (ROM), random access memory (RAM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), magnetic card or Optical card, flash memory, or tangible machine-readable memory used to transmit information using electrical, optical, acoustic, or other forms of propagation signals (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet. Thus, machine-readable media includes any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (eg, computer).

In the drawings, some structural or methodological features may be shown in specific arrangements and/or orders. However, it should be understood that such specific arrangement and/or ordering may not be required. Rather, in some embodiments, the features may be arranged in a manner and/or order different than that shown in the illustrative figures. Additionally, the inclusion of structural or methodological features in a particular figure is not meant to imply that such features are required in all embodiments, and in some embodiments these features may not be included or may be combined with other features.

It should be noted that each unit/module mentioned in each device embodiment of this application is a logical unit/module. Physically, a logical unit/module can be a physical unit/module, or it can be a physical unit/module. Part of the module can also be implemented as a combination of multiple physical units/modules. The physical implementation of these logical units/modules is not the most important. The combination of functions implemented by these logical units/modules is what solves the problem of this application. Key technical issues raised. In addition, in order to highlight the innovative part of this application, the above-mentioned equipment embodiments of this application do not introduce units/modules that are not closely related to solving the technical problems raised by this application. This does not mean that the above-mentioned equipment embodiments do not exist. Other units/modules.

It should be noted that in the examples and descriptions of this patent, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply There is no such actual relationship or sequence between these entities or operations. Furthermore, the terms "comprises," "comprises," or any other variations thereof are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that includes a list of elements includes not only those elements, but also those not expressly listed other elements, or elements inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a" does not exclude the presence of additional identical elements in a process, method, article, or device that includes the stated element.

Although the present application has been illustrated and described with reference to certain preferred embodiments thereof, it will be understood by those of ordinary skill in the art that various changes may be made in form and detail without departing from the present invention. The spirit and scope of the application.

Claims

An NFC-based card swiping method is characterized by including:

The electronic device enters the card simulation mode, wherein the card information of multiple first-type simulation cards is stored on the electronic device;

When the electronic device does not receive the service identification, the electronic device selects the first-type simulation cards one by one from the plurality of first-type simulation cards for simulation.
The method of claim 1, wherein the electronic device selects the first-type simulation cards one by one from the plurality of first-type simulation cards for simulation, including:

The electronic device selects the first-type simulation cards from the plurality of first-type simulation cards one by one to perform card simulation until the preset termination conditions are met.
The method according to claim 2, characterized in that the preset termination conditions include any one of the following conditions:

The duration for which the electronic device performs card simulation exceeds the preset duration;

The NFC function of the electronic device is turned off;

The electronic device detects that the card is successfully swiped;

The electronic device does not detect a near field communication signal for more than a preset time period;

The electronic device detects the user's cancellation operation or instruction of card swiping.
The method according to any one of claims 1 to 3, characterized in that the electronic device includes a memory; and the card information of the first type of simulation card is stored in the memory.
The method according to claim 4, characterized in that the card information of the first type of simulation card is obtained by the electronic device when the business identification is not obtained when opening each of the first type of simulation cards. case, stored in the memory.
The method of claim 5, wherein the electronic device further includes an NFC controller; and the electronic device selects the first-type simulation cards one by one from the plurality of first-type simulation cards. Simulations, including:

The electronic device obtains the card information of each of the first-type simulated cards one by one from the memory, and writes the obtained card information into the NFC controller to perform card simulation.
The method according to any one of claims 1 to 3, characterized in that the electronic device includes a security unit SE or an embedded security unit eSE; and the card information of the first type of simulation card is stored in the Security unit SE or embedded security unit eSE.
The method according to claim 7, characterized in that a trusted application runs in a trusted execution environment of the electronic device, the electronic device further includes an NFC controller; and, the electronic device obtains the information from the plurality of The first type of simulation cards are selected one by one from the first type of simulation cards for simulation, including:

The electronic device uses the trusted application, the security unit SE or the embedded security unit eSE to write the card information of the first type of simulation card into the NFC controller one by one to perform card simulation.
The method according to any one of claims 1 to 8, wherein the card information includes a unique identifier UID; and the service identifier includes an application identifier AID.
The method according to any one of claims 1 to 8, characterized in that, when the electronic device detects a user's preset operation on the electronic device and/or detects a near field communication signal, Enter card emulation mode.
An electronic device, characterized in that the electronic device stores card information of multiple first-type analog cards, and the electronic device includes:

A memory in which instructions are stored;

and a processor, configured to execute the instruction so that after the electronic device enters the card emulation mode, when the electronic device does not receive When the service identification is reached, the first-type simulation cards are selected one by one from the plurality of first-type simulation cards for simulation.
The electronic device according to claim 11, characterized in that, selecting the first-type simulation cards one by one from the plurality of first-type simulation cards for simulation includes:

The electronic device selects the first-type simulation cards from the plurality of first-type simulation cards one by one to perform card simulation until the preset termination conditions are met.
The electronic device according to claim 12, wherein the preset termination condition includes any one of the following conditions:

The duration for which the electronic device performs card simulation exceeds the preset duration;

The NFC function of the electronic device is turned off;

The electronic device detects that the card is successfully swiped;

The electronic device does not detect a near field communication signal for more than a preset time period;

The electronic device detects the user's cancellation operation or instruction of card swiping.
The electronic device according to any one of claims 11 to 13, characterized in that the card information of the first type of simulation card is stored in the memory.
The electronic device according to claim 14, characterized in that the card information of the first type of simulation card is obtained by the electronic device when the business identifier is not obtained when opening each of the first type of simulation cards. , stored in the memory.
The electronic device according to claim 15, wherein the electronic device further includes an NFC controller; and the first-type simulation cards are selected one by one from the plurality of first-type simulation cards for simulation, include:

The electronic device obtains the card information of each of the first-type simulated cards one by one from the memory, and writes the obtained card information into the NFC controller to perform card simulation.
The electronic device according to any one of claims 11 to 13, characterized in that the electronic device further includes a security unit SE or an embedded security unit eSE; and the card information of the first type of simulation card is stored in The security unit SE or the embedded security unit eSE.
The electronic device according to claim 17, characterized in that a trusted application runs in a trusted execution environment of the electronic device, the electronic device further includes an NFC controller; and the first The first type of simulation cards are selected one by one for simulation, including:

The electronic device uses the trusted application, the security unit SE or the embedded security unit eSE to write the card information of the first type of simulation card into the NFC controller one by one to perform card simulation.
The electronic device according to any one of claims 11 to 18, wherein the card information includes a unique identifier UID; and the service identifier includes an application identifier AID.
The electronic device according to any one of claims 11 to 18, characterized in that, when the instruction is executed by the processor, the electronic device also causes the electronic device to detect that the user has preset on the electronic device. In case of operation and/or detection of a near field communication signal, the electronic device is controlled to enter a card emulation mode.
A readable medium, characterized in that instructions are stored on the readable medium, and when the instructions are executed on an electronic device, the electronic device implements the method described in any one of claims 1 to 10.