Card management method and related apparatus

Abstract

Provided in the present application are a card management method and a related apparatus. The method comprises: a near field communication (NFC) card reading device sending a select command to an electronic device, the select command being used for instructing the electronic device to perform an NFC interaction with the NFC card reading device; the electronic device sending a select acknowledge (SAK) command to the NFC card reading device, the SAK command indicating that an application layer protocol is not supported; the NFC card reading device sending to the electronic device a select AID command in the application layer protocol; and, on the basis of the select AID command, the electronic device determining a first NFC emulating card and executing a card swiping service of the first NFC emulating card with the NFC card reading device. Therefore, the present application can ensure that the electronic device and the NFC card reading device perform an application layer protocol communication process, so that the electronic device selects a suitable NFC emulating card from among a plurality of NFC emulating cards and executes the NFC card swiping service with the NFC card reading device, thereby allowing for simultaneous activation and coexistence of the plurality of NFC emulating cards.

Description

Card management method and related device

[0001] The present application claims priority to the Chinese patent application No. 202410875130.3, filed on June 29, 2024, with the State Intellectual Property Office of China, and entitled "Card management method and related device", the whole content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the field of wireless communication technology, in particular to a card management method and related device. BACKGROUND

[0003] With the development of wireless communication technology, near field communication (NFC) technology has been widely applied. NFC technology is evolved from non-contact radio frequency identification (RFID) and interconnection technology. In NFC technology, the working mode of NFC devices with NFC function when communicating through NFC technology can be divided into three types: proximity coupling device (PCD) mode (also known as reader mode), proximity integrated circuit card (PICC) mode (also known as card simulation mode) and point to point (P2P) mode.

[0004] Currently, some electronic devices (such as mobile phones, tablets, wearable devices, etc.) with NFC function can support both PICC mode and PCD mode. A user can open one or more NFC simulation cards in an electronic device, and therefore, the electronic device can include NFC parameters of the one or more NFC simulation cards. When the electronic device is in PICC mode, it can simulate itself as a PICC conforming to NFC related standards based on the data of the NFC simulation card, and interact with a NFC device (which can be referred to as a NFC reader device) in PCD mode. When the electronic device is close to the NFC reader device, the electronic device uses the NFC parameters of the NFC simulation card in an active state to interact with the NFC reader device to try to perform NFC services. However, only one NFC simulation card in the electronic device is in an active state, and multiple NFC simulation cards cannot coexist simultaneously because the NFC reader device cannot identify NFC signaling including NFC parameters of multiple NFC simulation cards, resulting in failure of NFC service execution. SUMMARY

[0005] The application discloses a card management method and related device, which can ensure the communication process of the application layer protocol between an electronic device and a near field communication (NFC) card reading device, so that the electronic device selects a suitable NFC analog card from multiple NFC analog cards to complete the NFC card swiping business with the NFC card reading device, and realizes the simultaneous activation and coexistence of the multiple NFC analog cards.

[0006] In a first aspect, the application provides a card management method applied to an NFC card reading device, for example, a target proximity integrated circuit card (PICC) of the NFC card reading device is a PICC supporting an access layer protocol (for example, an ISO 14443-3 protocol or an IEC 14443-3 protocol) and an application layer protocol (for example, an ISO 14443-4 protocol or an IEC 14443-4 protocol). The method comprises the following steps: sending a select command in the access layer protocol to an electronic device, the select command being used to select the electronic device to perform NFC interaction with the NFC card reading device; receiving a first select acknowledge (SAK) command in the access layer protocol sent by the electronic device in response to the select command, the first SAK command indicating that the application layer protocol is not supported; after receiving the first SAK command, sending a select application identifier (AID) command in the application layer protocol to the electronic device, for example, the NFC card reading device does not verify the first SAK command, so that after receiving the first SAK command, the communication process of the application layer protocol (including the sending of the select AID command) is continued; the select AID command is used to determine a first NFC analog card, for example, is used to determine the first NFC analog card from one or more NFC analog cards (supporting the access layer protocol and the application layer protocol) in the electronic device; then performing NFC interaction with the electronic device and completing the card swiping business of the first NFC analog card.

[0007] In the above method, even if the first SAK command sent by the electronic device to the NFC card reading device indicates that the application layer protocol is not supported, the NFC card reading device still sends the selection AID command to the electronic device, for example, the NFC card reading device does not check the SAK command. The selection AID command can enable the electronic device to determine the corresponding first NFC simulation card from one or more NFC simulation cards, and instead of only using the NFC simulation card in the default active state and the NFC card reading device to perform the NFC card swiping business, it can be understood that one or more NFC simulation cards in the electronic device will all "participate" in each NFC technology communication, thus achieving the simultaneous activation coexistence of multiple NFC simulation cards in the electronic device. Moreover, the first NFC simulation card selected by the electronic device according to the selection AID command meets the card swiping demand of the current scene, is more accurate, avoids the case that the NFC interaction is performed only using the NFC simulation card in the default active state and the NFC card reading device, but the NFC simulation card in the default active state is not the target PICC of the NFC card reading device, resulting in the card swiping failure, and also avoids the case that when the electronic device randomly switches the NFC simulation card in the default active state, the NFC technology communication needs to be performed multiple times, resulting in the slow card swiping, thus improving the success rate and speed of the NFC card swiping.

[0008] In a possible implementation, the first NFC emulation card supports an access layer protocol and an application layer protocol, the electronic device further includes a second NFC emulation card (for example, an NFC emulation card in a default active state), the second NFC emulation card supports the access layer protocol and does not support the application layer protocol, the first SAK command is obtained according to the NFC parameters of the second NFC emulation card, for example, the NFC parameters of the second NFC emulation card include the first SAK command; the method further includes: before the selection command is sent to the electronic device, a request command (for example, a class A request command REQA or a class B request command REQB) in the access layer protocol is sent to the electronic device; a request response command (for example, a class A request reply command ATQA or a class B request reply command ATQB) in the access layer protocol is received, which is sent by the electronic device in response to the request command, the request response command is obtained according to the NFC parameters of the second NFC emulation card, for example, the NFC parameters of the second NFC emulation card include the request response command; in response to the request response command, an anticollision command in the access layer protocol is sent to the electronic device, for example, the NFC card reading device does not check the request response command, and therefore continues the communication process in the access layer protocol with the electronic device (including sending the anticollision command) after receiving the request response command sent by the electronic device; a unique identifier UID of the second NFC emulation card is received, which is sent by the electronic device in response to the anticollision command, for example, the NFC card reading device does not check the UID of the second NFC emulation card sent by the electronic device, and therefore continues the communication process in the access layer protocol with the electronic device (including sending the selection command) after receiving the UID of the second NFC emulation card sent by the electronic device.

[0009] In the above method, the target PICC of the NFC card reading device can be the first NFC emulation card, not the second NFC emulation card, even if the request response command, the UID, and the first SAK command sent by the electronic device to the NFC card reading device are obtained according to the NFC parameters of the second NFC emulation card, the NFC card reading device still continues the subsequent communication process with the electronic device, for example, the NFC card reading device does not check the request response command, the UID, and the SAK command, which can ensure that the electronic device and the NFC card reading device perform the communication process in the application layer protocol, so that the electronic device selects the first NFC emulation card required by the NFC card reading device in the communication process in the application layer protocol, and performs the card swiping business of the first NFC emulation card with the electronic device, and further improves the success rate and speed of NFC card swiping.

[0010] In a possible implementation, the method further includes: after receiving the first SAK command sent by the electronic device, sending a request for selection response (RATS) command in the application layer protocol to the electronic device; receiving a selection response (ATS) command in the application layer protocol sent by the electronic device in response to the RATS command, wherein the content of the ATS command does not meet the preset requirement of the NFC card reading device, for example, the content of the ATS command is empty, or the content of the ATS command is a communication parameter (for example, including a length byte indicating a frame length, an interface byte indicating a rate, an interface byte indicating a frame waiting time (FWT) and a start frame guard time (SFGT), an interface byte indicating whether a logical channel ID (CID) is supported, and a history byte) used to implement a communication process of the application layer protocol, but the communication parameter in the ATS command does not meet the preset requirement of the NFC card reading device; the selection AID command is sent by the NFC card reading device in response to the ATS command, for example, the NFC card reading device determines that the format of the ATS command is correct (without checking the content of the ATS command), or the NFC card reading device does not check the format and content of the ATS command, and thus continues to send the selection AID command to the electronic device after receiving the ATS command.

[0011] In the method, even if the content of the ATS command sent by the electronic device to the NFC card reading device does not meet the preset requirement of the NFC card reading device, the NFC card reading device still continues the subsequent communication process of the application layer protocol (including sending the selection AID command) with the electronic device, for example, the NFC card reading device only checks the format of the ATS command or does not check the ATS command, so that the NFC card reading device can send the selection AID command to the electronic device, and the electronic device can select the first NFC analog card required by the NFC card reading device according to the selection AID command, and perform a card swiping service of the first NFC analog card with the electronic device, thereby further improving the success rate and speed of NFC card swiping.

[0012] In a second aspect, the present application provides a card management method applied to an electronic device, the method comprising: receiving a first select command in an access layer protocol (such as ISO 14443-3 protocol or IEC 14443-3 protocol) sent by an NFC card reading device, the first select command being used to select the electronic device to perform NFC interaction with the NFC card reading device; in response to the first select command, sending a first select acknowledgement (SAK) command in the access layer protocol to the NFC card reading device, the first SAK command indicating that an application layer protocol (such as ISO 14443-4 protocol or IEC 14443-4 protocol) is not supported; receiving a select AID command in the application layer protocol sent by the NFC card reading device, for example, the NFC card reading device does not check the first SAK command, and thus continues the communication process of the application layer protocol (including sending the select AID command) after receiving the first SAK command; determining a first NFC emulation card from one or more NFC emulation cards (supporting the access layer protocol and the application layer protocol) of the electronic device according to the select AID command; and performing NFC interaction with the NFC card reading device and completing a card swiping service of the first NFC emulation card.

[0013] In some examples, the target proximity integrated circuit card (PICC) of the NFC card reading device is a PICC supporting the access layer protocol and the application layer protocol.

[0014] In the above method, even if the first SAK command sent by the electronic device to the NFC card reading device indicates that the application layer protocol is not supported, the NFC card reading device still sends the select AID command to the electronic device, for example, the NFC card reading device does not check the SAK command. The select AID command allows the electronic device to determine the corresponding first NFC emulation card from the one or more NFC emulation cards, instead of only using the NFC emulation card in the default active state to perform NFC card swiping service with the NFC card reading device. It can be understood that one or more NFC emulation cards in the electronic device will "participate" in each NFC communication, thus achieving simultaneous activation and coexistence of multiple NFC emulation cards in the electronic device. Moreover, the first NFC emulation card selected by the electronic device according to the select AID command meets the card swiping demand of the current scenario, is more accurate, avoids the situation that the NFC card reading device fails to perform NFC interaction with the NFC emulation card in the default active state because the NFC emulation card in the default active state is not the target PICC of the NFC card reading device, and also avoids the situation that the electronic device needs to perform NFC communication multiple times when randomly switching the NFC emulation card in the default active state, resulting in slow card swiping. Therefore, the success rate and speed of NFC card swiping are improved.

[0015] In a possible implementation, the first NFC emulation card supports the access layer protocol and the application layer protocol, the electronic device further includes a second NFC emulation card (e.g., an NFC emulation card in a default active state), the second NFC emulation card supports the access layer protocol and does not support the application layer protocol, the first SAK command is obtained according to the NFC parameter of the second NFC emulation card, for example, the NFC parameter of the second NFC emulation card includes the first SAK command; the method further includes: before receiving the first select command sent by the NFC reading device, after entering the radio frequency field of the NFC reading device, receiving a request command (e.g., a class A request command REQA or a class B request command REQB) in the access layer protocol sent by the NFC reading device; in response to the request command, sending a request response command (e.g., a class A request reply command ATQA or a class B request reply command ATQB) in the access layer protocol to the NFC reading device, the request response command is obtained according to the NFC parameter of the second NFC emulation card, for example, the NFC parameter of the second NFC emulation card includes the request response command; receiving an anti-collision command in the access layer protocol sent by the NFC reading device in response to the request response command, for example, the NFC reading device does not check the request response command, and therefore continues the communication process of the access layer protocol with the electronic device (including sending the anti-collision command) after receiving the request response command sent by the electronic device; in response to the anti-collision command, sending a unique identifier UID of the second NFC emulation card (e.g., the NFC parameter of the second NFC emulation card includes the UID of the second NFC emulation card) to the NFC reading device; the first select command is sent by the NFC reading device in response to the UID of the second NFC emulation card sent by the electronic device, for example, the NFC reading device does not check the UID of the second NFC emulation card sent by the electronic device, and therefore continues the communication process of the access layer protocol with the electronic device (including sending the select command) after receiving the UID of the second NFC emulation card sent by the electronic device.

[0016] In some examples, the NFC parameter of one or more NFC emulation cards (supporting the access layer protocol and the application layer protocol) in the electronic device is obtained according to a corresponding configuration parameter and a configuration mask by bit-wise AND, the NFC parameter of the one or more NFC emulation cards includes at least one of the following: a SAK command used to implement a communication process of the access layer protocol, a request response command, and a UID, and the configuration mask corresponding to the NFC parameter of the one or more NFC emulation cards is zero, therefore, the NFC parameter of the one or more NFC emulation cards is zero.

[0017] In the above method, the target PICC of the NFC card reading device can be the first NFC analog card, not the second NFC analog card. Even if the request response command, the UID and the first SAK command sent by the electronic device to the NFC card reading device are obtained according to the NFC parameters of the second NFC analog card, the NFC card reading device will continue the subsequent communication process with the electronic device, for example, the NFC card reading device does not verify the request response command, the UID and the SAK command. In this way, the electronic device and the NFC card reading device can perform the communication process of the application layer protocol, so that the electronic device selects the first NFC analog card required by the NFC card reading device in the communication process of the application layer protocol, and performs the card swiping business of the first NFC analog card with the electronic device, thereby further improving the success rate and speed of NFC card swiping.

[0018] In a possible implementation, the above method further includes: after sending the first SAK command to the NFC card reading device, receiving a select response request RATS command in the application layer protocol sent by the NFC card reading device in response to the first SAK command; in response to the RATS command, sending a select response ATS command in the application layer protocol to the NFC card reading device, the content of the ATS command not meeting the preset requirement of the NFC card reading device, for example, the content of the ATS command being empty, or the content of the ATS command being communication parameters (for example, including a length byte indicating a frame length, an interface byte indicating a rate, interface bytes indicating a frame waiting time FWT and a start frame guard time SFGT, an interface byte indicating whether to support a logical channel number CID, and a history byte) used to implement the communication process of the application layer protocol, but the communication parameters in the ATS command do not meet the preset requirement of the NFC card reading device; the above select AID command is sent by the NFC card reading device in response to the ATS command, for example, the NFC card reading device determines that the format of the ATS command is correct (without verifying the content of the ATS command), or the NFC card reading device does not verify the format and content of the ATS command, so that the NFC card reading device continues to send the select AID command to the electronic device after receiving the ATS command.

[0019] In the above method, even if the content of the ATS command sent by the electronic device to the NFC card reading device does not meet the preset requirement of the NFC card reading device, the NFC card reading device will continue the subsequent communication process of the application layer protocol (including sending the select AID command) with the electronic device, for example, the NFC card reading device only verifies the format of the ATS command or does not verify the ATS command. In this way, the NFC card reading device can send the select AID command to the electronic device, so that the electronic device selects the first NFC analog card required by the NFC card reading device according to the select AID command, and performs the card swiping business of the first NFC analog card with the electronic device, thereby further improving the success rate and speed of NFC card swiping.

[0020] In a possible implementation, the method further includes: if the RATS command in the application layer protocol sent by the NFC card reading device is not received within a preset time period after the first SAK command is sent to the NFC card reading device, for example, the RATS command is not sent by the NFC card reading device when the first SAK command fails to be verified by the NFC card reading device, after the request command in the access layer protocol sent by the NFC card reading device is received, a request response command in the access layer protocol is sent to the NFC card reading device in response to the request command; the second selection command is received from the NFC card reading device, and the second selection command is used to select the electronic device to perform NFC interaction with the NFC card reading device; the second SAK command is sent to the NFC card reading device in response to the second selection command, and the second SAK command indicates that the application layer protocol is supported; the selection AID command is received from the NFC card reading device after the second SAK command is sent to the NFC card reading device, for example, the selection AID command is sent by the NFC card reading device to the electronic device when the second SAK command is verified by the NFC card reading device.

[0021] In some examples, the method further includes: after the second SAK command is sent to the NFC card reading device, the RATS command in the application layer protocol sent by the NFC card reading device in response to the second SAK command is received; the ATS command is sent to the NFC card reading device in response to the RATS command; and the selection AID command is sent by the NFC card reading device in response to the ATS command, for example, the selection AID command is sent by the NFC card reading device to the electronic device when the ATS command is verified by the NFC card reading device.

[0022] In some examples, the method further includes: after the request response command is sent to the NFC card reading device, the anti-collision command sent by the NFC card reading device in response to the request response command is received, for example, the anti-collision command is sent by the NFC card reading device when the request response command is not verified by the NFC card reading device; the UID of the NFC emulation card in the default active state is sent to the NFC card reading device in response to the anti-collision command; and the second selection command is received from the NFC card reading device after the UID of the NFC emulation card in the default active state is sent to the NFC card reading device, for example, the second selection command is sent by the NFC card reading device when the UID sent by the electronic device is not verified by the NFC card reading device.

[0023] In the method, the NFC card reading device can check the SAK command and other NFC signaling sent by the electronic device. After the electronic device sends the first SAK command indicating that the application layer protocol is not supported, if no RATS command sent by the NFC card reading device is received, the electronic device can re-perform the communication of the access layer protocol with the NFC card reading device, and send the second SAK command supporting the application layer protocol, so that the NFC card reading device initiates the communication of the application layer protocol. It can be understood that the electronic device dynamically switches the SAK command used. In this way, the electronic device can receive the select AID command sent by the NFC card reading device, and the select AID command can enable the electronic device to determine the first NFC emulation card required by the NFC card reading device from one or more NFC emulation cards. That is, even if the NFC card reading device checks the NFC signaling sent by the electronic device, the electronic device can realize the simultaneous activation of multiple NFC emulation cards, and automatically and accurately select the first NFC emulation card meeting the card swiping demand of the current scene to complete the card swiping business with the NFC card reading device.

[0024] In a possible implementation, the electronic device is in a shutdown state, and the card management method provided in the second aspect and any one of the implementation manners of the second aspect can be performed by the electronic device in the shutdown state. In this way, the electronic device can automatically and accurately select the first NFC emulation card required by the NFC card reading device and perform the card swiping business of the first NFC emulation card with the NFC card reading device, without switching the NFC emulation card in the default activation state, so that the card swiping failure caused by the inability to switch the NFC emulation card in the default activation state is avoided, that is, even if the electronic device is in the shutdown state, the NFC emulation card can be normally completed with the NFC card reading device, and the user experience is further improved.

[0025] In a third aspect, the present application provides a card management method applied to an electronic device, the method comprising: receiving a first select command in an access layer protocol (such as ISO 14443-3 protocol or IEC 14443-3 protocol) sent by an NFC card reading device, the first select command being used to select the electronic device to perform NFC interaction with the NFC card reading device; in response to the first select command, sending a first select acknowledgement (SAK) command in the access layer protocol to the NFC card reading device, the first SAK command indicating that an application layer protocol (such as ISO 14443-4 protocol or IEC 14443-4 protocol) is not supported; if a RATS command in the application layer protocol sent by the NFC card reading device is not received within a preset time period after the first SAK command is sent to the NFC card reading device, for example, the NFC card reading device does not send the RATS command when the first SAK command fails to pass the verification, after receiving a request command in the access layer protocol sent by the NFC card reading device, responding to the request command by sending a request response command in the access layer protocol to the NFC card reading device; receiving a second select command sent by the NFC card reading device, the second select command being used to select the electronic device to perform NFC interaction with the NFC card reading device; in response to the second select command, sending a second SAK command to the NFC card reading device, the second SAK command indicating that the application layer protocol is supported; receiving a select AID command in the application layer protocol sent by the NFC card reading device, for example, the select AID command is sent by the NFC card reading device to the electronic device when the second SAK command passes the verification; determining a first NFC emulation card from one or more NFC emulation cards (supporting the access layer protocol and the application layer protocol) of the electronic device according to the select AID command; and performing NFC interaction with the NFC card reading device and completing a card swiping service of the first NFC emulation card.

[0026] In some examples, the method further comprises: after the second SAK command is sent to the NFC card reading device, receiving a RATS command in the application layer protocol sent by the NFC card reading device in response to the second SAK command; in response to the RATS command, sending an ATS command to the NFC card reading device; and the select AID command is sent by the NFC card reading device in response to the ATS command, for example, the select AID command is sent by the NFC card reading device to the electronic device when the ATS command passes the verification.

[0027] In some examples, the method further includes: after sending the request response command to the NFC card reading device, receiving an anti-collision command sent by the NFC card reading device in response to the request response command, for example, the anti-collision command is sent when the NFC card reading device does not verify the request response command, or the anti-collision command is sent when the verification of the request response command is passed; in response to the anti-collision command, sending the UID of the NFC analog card in the default active state to the NFC card reading device; the second selection command is received from the NFC card reading device after sending the UID of the NFC analog card in the default active state to the NFC card reading device, for example, the second selection command is sent when the NFC card reading device does not verify the UID sent by the electronic device, or the second selection command is sent when the verification of the UID sent by the electronic device is passed.

[0028] In the above method, the NFC card reading device can verify the SAK command and other NFC signaling sent by the electronic device. After the electronic device sends the first SAK command indicating that the application layer protocol is not supported, if the RATS command sent by the NFC card reading device is not received, the electronic device can re-perform the communication of the access layer protocol with the NFC card reading device and send the second SAK command supporting the application layer protocol, so that the NFC card reading device initiates the communication of the application layer protocol. It can be understood that the electronic device dynamically switches the SAK command used. In this way, the electronic device can receive the selection AID command sent by the NFC card reading device, and the selection AID command can enable the electronic device to determine the first NFC analog card required by the NFC card reading device from one or more NFC analog cards, instead of only using the NFC analog card in the default active state to perform the NFC card swiping business with the NFC card reading device. It can be understood that one or more NFC analog cards in the electronic device will "participate" in each NFC communication, so that even if the NFC card reading device verifies the NFC signaling sent by the electronic device, the electronic device can also achieve the simultaneous activation and coexistence of multiple NFC analog cards. Moreover, even if the NFC card reading device verifies the NFC signaling sent by the electronic device, the electronic device can accurately select the first NFC analog card meeting the current card swiping demand according to the selection AID command to complete the card swiping business with the NFC card reading device, avoiding the situation that the NFC analog card in the default active state is used to perform the NFC interaction with the NFC card reading device, but the NFC analog card in the default active state is not the target PICC of the NFC card reading device, resulting in the failure of the card swiping. Also, the situation that the electronic device randomly switches the NFC analog card in the default active state and needs to perform the NFC communication multiple times, resulting in slow card swiping, is avoided, thereby improving the success rate and speed of NFC card swiping.

[0029] In a fourth aspect, the present application provides a communication device, comprising a transceiver, a processor and a memory; the memory is configured to store a computer program, and the processor is configured to invoke the computer program, so that the communication device performs the card management method provided in the first aspect and any possible implementation manner of the first aspect.

[0030] In a fifth aspect, the present application provides an electronic device, comprising a transceiver, a processor and a memory; the memory is configured to store a computer program, and the processor is configured to invoke the computer program, so that the electronic device performs the card management method provided in the second aspect and the third aspect, and any possible implementation manner of the second aspect and the third aspect.

[0031] In a sixth aspect, the present application provides a computer storage medium, comprising a computer program, when the computer program is executed by a processor, the computer program is configured to implement the card management method provided in the first aspect and any possible implementation manner of the first aspect, or implement the card management method provided in the second aspect and the third aspect, and any possible implementation manner of the second aspect and the third aspect.

[0032] In a seventh aspect, the present application provides a computer program product, comprising a computer program, when the computer program is executed on a processor, the computer program is configured to implement the card management method provided in the first aspect and any possible implementation manner of the first aspect, or implement the card management method provided in the second aspect and the third aspect, and any possible implementation manner of the second aspect and the third aspect.

[0033] In an eighth aspect, the present application provides a chip system, comprising a processing circuit and an interface circuit, the interface circuit is configured to receive code instructions and transmit the code instructions to the processing circuit, and the processing circuit is configured to execute the code instructions, so as to execute the card management method provided in the first aspect and any possible implementation manner of the first aspect, or execute the card management method provided in the second aspect and the third aspect, and any possible implementation manner of the second aspect and the third aspect.

[0034] In a ninth aspect, the present application provides an electronic device, the electronic device comprises the method or the device introduced in any aspect or embodiment of the present application. The electronic device is, for example, a chip.

[0035] It should be understood that the description of technical features, technical solutions, advantages or similar language in this application does not imply that all features and advantages can be realized in any single implementation. Instead, it is understood that the description of a feature or advantage means that the specific technical feature, technical solution or advantage is included in at least one implementation. Therefore, the description of technical features, technical solutions or advantages in this application does not necessarily refer to the same implementation. Further, the technical features, technical solutions and advantages described in this application can be combined in any appropriate manner. Those skilled in the art will understand that the present application can be implemented without one or more specific technical features, technical solutions or advantages of a particular implementation. In other implementations, additional technical features and advantages can be identified in specific implementations that do not embody all implementations. BRIEF DESCRIPTION OF DRAWINGS

[0036] The following describes the drawings used in this application.

[0037] Figure 1 is a schematic diagram of the working principle of a near field communication (NFC) provided in this application;

[0038] Figure 2 is a schematic diagram of the architecture of an NFC system provided in this application;

[0039] Figure 3 is a schematic diagram of the structure of an electronic device provided in this application;

[0040] Figure 4 is a schematic diagram of the architecture of an NFC protocol stack provided in this application;

[0041] Figure 5 is a schematic diagram of the flow of a communication process provided in this application;

[0042] Figure 6 is a schematic diagram of another communication process provided in this application;

[0043] Figure 7 is a schematic diagram of the architecture of another NFC system provided in this application;

[0044] Figure 8 is a schematic diagram of the architecture of another NFC system provided in this application;

[0045] Figure 9 is a schematic diagram of a setting method of an NFC parameter provided in this application;

[0046] Figure 10 is a schematic diagram of the flow of a card management method provided in this application;

[0047] Figure 11 is a schematic diagram of another card management method provided in this application;

[0048] Figure 12 is a schematic diagram of the hardware structure of an electronic device provided in this application;

[0049] FIGS. 13-16 are structural schematic diagrams of some communication devices provided by the present application. DETAILED DESCRIPTION

[0050] The technical solutions in the embodiments of the present application will be described below with reference to the drawings. The terms used in the implementation manner part of the embodiments of the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application.

[0051] In the description of the embodiments of the present application, unless otherwise specified, " / " represents the meaning of or, for example, A / B can represent A or B; "and / or" in the text only describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist together, and B exists alone, in addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0052] Hereinafter, the terms "first" and "second" are only used for description purposes, and cannot be understood as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Therefore, the features limited by "first" and "second" can explicitly or implicitly include one or more features, and in the description of the embodiments of the present application, unless otherwise specified, the meaning of "multiple" is two or more than two.

[0053] The working principle of the near field communication (NFC) technology in the embodiments of the present application will be introduced below.

[0054] FIG. 1 is a schematic diagram of the working principle of near field communication (NFC) provided by the embodiments of the present application.

[0055] As shown in FIG. 1, the two parties using NFC technology for communication can include a proximity coupling device (PCD) and a proximity integrated circuit card (PICC). Among them, the PCD can realize proximity non-contact communication with the PICC. The PCD and the PICC can allow near field communication at a specific data rate (for example, 106 kilobit per second (kbps), 212 kbps, 424 kbps or 848 kbps) and a specific frequency (for example, 13.56 megahertz (MHz)). The communication between the PCD and the PICC can occur within a short distance, for example, within a range of about 2-4 centimeters.

[0056] The PCD can generate high-frequency alternating current to generate a radio frequency field of a specified frequency (for example, 13.56 MHz) and transmit data to the PICC through the radio frequency field. After the PICC approaches the PCD, the PICC can sense the radio frequency field emitted by the PCD. The PICC can obtain energy from the radio frequency field of the PCD through electromagnetic induction after entering the radio frequency field of the PCD, and generate power by means of the obtained energy to drive the circuit inside the PICC, analyze the data transmitted by the PCD through the radio frequency field, so as to realize data transmission from the PCD to the PICC. The PICC can also send data to the PCD in a manner of modulating the radio frequency field, thereby realizing data transmission from the PICC to the PCD.

[0057] The NFC system in the embodiments of the present application is introduced as follows.

[0058] FIG. 2 is a schematic diagram of an architecture of an NFC system 10 provided by the embodiments of the present application.

[0059] As shown in FIG. 2, the NFC system 10 can include an electronic device 100 and an NFC card reading device 200. The electronic device 100 can simulate itself as a PICC conforming to NFC related standards through the data of an NFC analog card, so as to realize the function of the PICC. The electronic device 100 can open one or more NFC analog cards and include the NFC parameters of the one or more NFC analog cards.

[0060] After the electronic device 100 and the NFC card reading device 200 approach each other, the electronic device 100 can act as a PICC and communicate with the NFC card reading device 200 acting as a PCD through the NFC parameters of the NFC analog card in the electronic device 100. The NFC card reading device 200 acting as a PCD when communicating through NFC technology can also be referred to as being in a PCD mode, and the electronic device 100 acting as a PICC when communicating through NFC technology can also be referred to as being in a PICC mode.

[0061] In some embodiments, the NFC emulation card in the electronic device 100 can support an NFC protocol, which can be the contactless card standard ISO 14443 / IEC 14443 protocol, and the electronic device 100 in the PICC mode can perform a communication process of the ISO 14443 / IEC 14443 protocol with the NFC card reading device 200 in the PCD mode. In some embodiments, the NFC emulation card in the electronic device 100 can include a first type and a second type, the NFC emulation card of the first type can support the access layer ISO 14443-3 / IEC 14443-3 protocol (which can be referred to as the access layer protocol) but not the application layer ISO 14443-4 / IEC 14443-4 protocol (which can be referred to as the application layer protocol), and the NFC emulation card of the second type can support the access layer protocol and the application layer protocol. In some examples, the NFC emulation card of the first type is a Mifare card (such as an access control card, etc.), and the NFC emulation card of the second type is a central processing unit (CPU) card (such as a transportation card, a car key, a digital certificate, a bank card, etc.). In some examples, the electronic device 100 can perform a communication process of the access layer protocol with the NFC card reading device 200 using the NFC emulation card of the first type. In some examples, the electronic device 100 can perform a communication process of the access layer protocol and the application layer protocol with the NFC card reading device 200 using the NFC emulation card of the second type.

[0062] In some embodiments, the electronic device 100 can support both the PICC mode and the PCD mode. When the electronic device 100 is in the PCD mode, it can emit a radio frequency field as a PCD to communicate with a PICC through the radio frequency field. When the electronic device 100 is in the PICC mode, it can passively receive a radio frequency field emitted by a PCD as a PICC to communicate with the PCD through a load modulation technology. In some examples, after the electronic device 100 starts the NFC function, it can be in the PICC mode, and in some examples, after the electronic device 100 starts the NFC function, it can switch between the PICC mode and the PCD mode in time.

[0063] In the embodiments of the present application, the device type of the electronic device 100 can be any one of a mobile phone, a tablet computer, a handheld computer, a desktop computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), and a smart large screen, a smart speaker, and the like smart home device, a smart bracelet, a smart watch, smart glasses, and the like wearable device, an augmented reality (AR), a virtual reality (VR), a mixed reality (MR), and the like extended reality (XR) device, a vehicle-mounted device or a smart city device, and the like.

[0064] In the embodiments of the present application, the device type of the NFC card reading device 200 can be any one of a mobile phone, a tablet computer, a handheld computer, a desktop computer, a laptop computer, an ultra-mobile personal computer, a netbook, a cellular phone, a personal digital assistant, and a smart large screen, a smart speaker, and the like smart home device, a smart bracelet, a smart watch, smart glasses, and the like wearable device, an augmented reality, a virtual reality, a mixed reality, and the like extended reality device, a vehicle, a gate, a smart door lock, a card swiping device, a cash register terminal (for example, a point of sales (POS) machine), a ticket buying and / or checking terminal, a bank service terminal, an identification card reading device, and the like.

[0065] The structure of the electronic device 100 in the embodiments of the present application will be introduced below.

[0066] FIG. 3 is a structural schematic diagram of an electronic device 100 provided in the embodiments of the present application.

[0067] As shown in FIG. 3, the electronic device 100 can include a processor 101 and an NFC module 102. One or more applications (APPs) can be run in the processor 101, and in some examples, the one or more applications can include a wallet application, one or more host-based card emulation (HCE) applications, a subscriber identity module (SIM) card application, and the like. In some embodiments, the electronic device 100 can further include a secure element (SE) 103 and / or a SIM card 104, and the processor 101 can be connected with the NFC module 102, the SE 103, and the SIM card 104 respectively, and the NFC module 102 can also be connected with the SE 103 and the SIM card 104.

[0068] In some embodiments, the electronic device 100 can open one or more NFC emulation cards in an application according to the input of the user, so as to enable the electronic device 100 to support one or more NFC services, wherein the business processing logic of the NFC emulation card in the electronic device 100 is specifically implemented by an applet, and the applet can be stored and run in the hardware device or software module (such as the HCE application, the SE 103, the SIM card 104, etc.) corresponding to the NFC emulation card.

[0069] The NFC module 102 can be used to implement the communication of the NFC technology of the electronic device 100 and the NFC reading device 200. The NFC module 102 can include an NFC controller (not shown in FIG. 3), an NFC transceiver (not shown in FIG. 3), and an NFC memory (not shown in FIG. 3), wherein the NFC controller can be connected with the processor 101, and the NFC controller can also be connected with the NFC transceiver and the NFC memory respectively.

[0070] The NFC controller in the NFC module 102 can be used for modulation and demodulation of non-contact communication signals, control the input and output of data in the NFC memory, and interact with the processor 101. The NFC transceiver in the NFC module 102 can be used to implement the transmission and reception of NFC signals (such as 13.56 MHz radio frequency signals), and in some embodiments, the NFC transceiver can include an EMC filter circuit, a matching circuit, a receiving circuit, and an NFC antenna, etc., wherein the NFC antenna can be a loop antenna, which is used to implement the proximity-based non-contact communication capability of the NFC module 102. The NFC memory in the NFC module 102 can be used to store the data transmitted by the NFC module 102 to the NFC reading device 200, and the data received from the NFC reading device 200.

[0071] In some embodiments, the NFC memory can be one memory that can be shared by the NFC module 102 and other modules in the electronic device 100, for example, some data in the NFC memory can be invoked by the NFC controller, while other data can be invoked by the SE 103. In other embodiments, the NFC memory can also be a collection of multiple memories, for example, the NFC controller can include a first memory in the multiple memories, the first memory can be used to store instructions or data that are used or recycled by the NFC controller, if the NFC controller needs to use the instructions or data again, the instructions or data can be directly invoked from the first memory, thus reducing the waiting time of the NFC controller. The SE 103 can include a second memory in the multiple memories, the second memory can be used to store card information of the NFC emulation card based on the secure component (SE) (for example, including the Applet of the NFC emulation card) and the like, thus if the SE 103 needs to read the card information of the NFC emulation card, the card information of the NFC emulation card can be read from the second memory in the SE 103. The SIM card 104 can include a third memory in the multiple memories, the third memory can be used to store card information of the NFC emulation card based on the SIM card (for example, including the Applet of the NFC emulation card) and the like, thus if the SIM card 104 needs to read the card information of the NFC emulation card, the card information of the NFC emulation card can be read from the third memory in the SIM card 104.

[0072] In some embodiments, the NFC memory can also be used to store routing information, for example, a first memory in the NFC memory can be used to store the routing information. In some embodiments, the routing information can be controlled or managed by the NFC controller, the routing information can include a routing table composed of a list of routing rules. Each routing rule contains an applet identifier (AID) and a corresponding destination, the AID is the identifier of the Applet used to implement the business logic of the NFC emulation card, and the destination corresponding to the AID is where the Applet of the AID runs (i.e., the hardware device or software module corresponding to the NFC emulation card of the AID), in some examples, the destination can include at least one of the following: one or more HCE applications in the processor 101, the SE 103 or the SIM card 104.

[0073] In some embodiments, the SE 103 and the NFC module 102 can be two independent chips. In other embodiments, the SE 103 and the NFC module 102 can be packaged in one chip.

[0074] In some embodiments, the card emulation mode of the NFC emulation card of the electronic device 100 can include a hardware-based virtual card mode and a software-based HCE mode.

[0075] In the hardware-based virtual card mode, the electronic device 100 can provide a running environment of the Applet corresponding to the NFC emulation card and storage and processing of the service data of the NFC emulation card through the SE 103 or the SIM card 104. The NFC module 102, as the front end of the contactless communication, forwards the NFC command received from the external NFC card reading device 200 to the SE 103 or the SIM card 104, the Applet in the SE 103 or the SIM card 104 processes the NFC command, and generates response data for the NFC card reading device 200, the SE 103 or the SIM card 104 can send the response data to the NFC module 102, and the NFC module 102 can send the response data to the external NFC card reading device 200. In some examples, the user can open one or more NFC emulation cards in the wallet application, the wallet application can write the Applet and the card data of the one or more NFC emulation cards into the SE 103, and the SE 103 can run the Applet of the one or more NFC emulation cards. In some examples, the user can open one or more NFC emulation cards in the SIM card application, the SIM card application can save the Applet and the card data of the one or more NFC emulation cards in the SIM card 104, and the SIM card 104 can run the Applet of the one or more NFC emulation cards.

[0076] In the hardware-based virtual card mode, the electronic device 100 can provide a running environment of the Applet corresponding to the NFC emulation card and storage and processing of the service data of the NFC emulation card through the SE 103 or the SIM card 104. The NFC module 102, as the front end of the contactless communication, forwards the NFC command received from the external NFC card reading device 200 to the SE 103 or the SIM card 104, the Applet in the SE 103 or the SIM card 104 processes the NFC command, and generates response data for the NFC card reading device 200, the SE 103 or the SIM card 104 can send the response data to the NFC module 102, and the NFC module 102 can send the response data to the external NFC card reading device 200. In some examples, the user can open one or more NFC emulation cards in the wallet application, the wallet application can write the Applet and the card data of the one or more NFC emulation cards into the SE 103, and the SE 103 can run the Applet of the one or more NFC emulation cards. In some examples, the user can open one or more NFC emulation cards in the SIM card application, the SIM card application can save the Applet and the card data of the one or more NFC emulation cards in the SIM card 104, and the SIM card 104 can run the Applet of the one or more NFC emulation cards.

[0077] Exemplarily, in the card emulation scenario described above, the electronic device 100 can be installed with a native application related to NFC, and in addition, a user can also download and install a third-party application in the electronic device 100 through an application store. Generally, the native application can adopt a hardware-based virtual card scheme, and the third-party application can adopt an HCE scheme. The native application can be a wallet application, a SIM card application, and the like, and the third-party application can be a payment application, a social application, a bank application, and the like. The above examples are only used to explain the embodiments of the present application, and should not constitute a limitation.

[0078] In some embodiments, the processor 101 can further include an NFC base service module. The NFC base service module can be used to provide common management functions for one or more NFC services. The common management functions can include file management, card long activation, security management, service routing management, and the like.

[0079] The following describes the NFC protocol stack in the embodiments of the present application.

[0080] FIG. 4 is a schematic diagram of an architecture of an NFC protocol stack provided by the embodiments of the present application.

[0081] As shown in FIG. 4, the NFC protocol stack can include a physical layer, a radio frequency layer, an access layer, a transmission layer, and an application layer. Among them,

[0082] The physical layer can be used to implement the physical characteristics during NFC technology communication.

[0083] The radio frequency layer can be used to implement the radio frequency specifications during NFC technology communication, for example, data rate, frequency of radio frequency signals, and the like.

[0084] The access layer can be used to implement the functions of polling and device discovery, service result notification, card conflict management, transmission protocol negotiation, timeout and retransmission mechanism, PICC / PCD mode switching, fusion card selection, and the like.

[0085] The transmission layer includes a high-speed data transmission protocol, through which data transmission between a PCD and a PICC at the application layer can be implemented.

[0086] The application layer can be used to implement one or more NFC services and one or more service management strategies. The one or more NFC services can include codeless payment, electronic ticket, access control, digital ID card, full-scene tap-to-tap, near-field data transmission, and the like. The one or more service management strategies can include any one or more of file management, card long activation, security management, and service routing management. In some embodiments, the processing logic of the NFC service can be executed by an Applet. In some embodiments, the processing logic of the service management strategy can be executed by the NFC base service module in the processor 101 shown in FIG. 3.

[0087] Currently, when the electronic device 100 is close to the NFC card reading device 200, the electronic device 100 uses the NFC parameters of one NFC analog card in an active state (for example, a preset default active card) to perform NFC technology communication with the NFC card reading device 200. For details, refer to FIG. 5 and FIG. 6.

[0088] FIG. 5 illustrates a flowchart of a communication process.

[0089] The communication process shown in FIG. 5 can be applied to an NFC system including the electronic device 100 and the NFC card reading device 200, for example, the NFC system 10 shown in FIG. 2. Among them, the electronic device 100 can be in a PICC mode, for example, the electronic device 100 is in the PICC mode by default after the NFC function is turned on, and the NFC card reading device 200 can be in a PCD mode.

[0090] FIG. 5 takes the NFC analog card in an active state in the electronic device 100 as an example of the first type of NFC analog card, and the communication process shown in FIG. 5 can be a communication process of an access layer protocol of NFC technology (for example, ISO14443-3 protocol / IEC14443-3 protocol).

[0091] The communication process shown in FIG. 5 can include but is not limited to the following steps:

[0092] S100: The electronic device 100 enters the radio frequency field of the NFC card reading device 200.

[0093] S101: The NFC card reading device 200 sends a request command to the electronic device 100.

[0094] In some embodiments of the present application, the NFC card reading device 200 in the PCD mode can broadcast a request command through the radio frequency field, and when the electronic device 100 in the PICC mode enters the radio frequency field of the NFC card reading device 200, the electronic device 100 can receive the request command broadcast by the NFC card reading device 200.

[0095] In some embodiments of the present application, the request command can be a class A request command (request command type A, REQA) or a class B request command (request command type B, REQB) in the ISO14443-3 protocol / IEC14443-3 protocol.

[0096] S102: The electronic device 100 sends a request response command to the NFC card reading device 200.

[0097] In some embodiments of the present application, the request response command can be an answer to request type A (ATQA) or an answer to request type B (ATQB) in the ISO 14443-3 protocol / IEC 14443-3 protocol. In the ISO 14443-3 protocol / IEC 14443-3 protocol, the NFC device in the PICC mode that receives the REQA / REQB can return the ATQA / ATQB if the ISO 14443-3 protocol / IEC 14443-3 protocol is supported. In some embodiments of the present application, the electronic device 100 includes an NFC emulation card that supports the NFC protocol (e.g., the ISO 14443 / IEC 14443 protocol), and thus, the electronic device 100 can send the request response command to the NFC card reading device 200 after receiving the request command broadcast by the NFC card reading device 200.

[0098] In some embodiments of the present application, the electronic device 100 can generate the request response command according to the request response command parameter in the NFC parameter of the NFC emulation card in the active state, and send the request response command to the NFC card reading device 200. In some examples, the request response command sent by the electronic device 100 can indicate whether the NFC emulation card in the active state in the electronic device 100 supports the anti-collision mechanism in the access layer protocol, such as the bit-oriented anti-collision mechanism in the ISO 14443-3 protocol / IEC 14443-3 protocol. In some examples, the request response command sent by the electronic device 100 can include the length of the unique identifier (UID) of the NFC emulation card in the active state in the electronic device 100.

[0099] S103: The NFC card reading device 200 verifies the request response command.

[0100] In some embodiments of the present application, the NFC card reading device 200 can determine whether the electronic device 100 supports the anti-collision mechanism in the access layer protocol according to the request response command sent by the electronic device 100, and if the determination result is yes, the request response command sent by the electronic device 100 is verified, and if the determination result is no, the request response command is not verified.

[0101] In some embodiments of the present application, the NFC card reading device 200 can not only determine whether the electronic device 100 supports the anti-collision mechanism in the access layer protocol, but also determine whether the length of the UID (i.e. the UID of the NFC emulation card in the active state in the electronic device 100) carried in the request response command conforms to the preset length range of the NFC card reading device 200, for example, the preset length range is the range in which the length of the UID of the target PICC required by the NFC card reading device 200 is located. When the electronic device 100 supports the anti-collision mechanism in the access layer protocol and the length of the UID carried in the request response command conforms to the preset length range of the NFC card reading device 200, the request response command sent by the electronic device 100 is verified by the NFC card reading device 200, otherwise, the verification fails.

[0102] In some embodiments of the present application, when the request response command sent by the electronic device 100 is verified by the NFC card reading device 200, the NFC card reading device 200 can continue the subsequent process of the access layer protocol, for example, perform S104.

[0103] S104: The NFC card reading device 200 sends an anti-collision command to the electronic device 100.

[0104] In some embodiments of the present application, the anti-collision command can instruct the NFC device in the PICC mode to return the entire UID. In some embodiments of the present application, the field SEL in the anti-collision command takes the value 93 and the field NVB takes the value 20. In some embodiments of the present application, the anti-collision command can also be referred to as a select command, and the anti-collision command and the select command described in S107 can be different select commands, for example, including different fields and taking different values.

[0105] S105: The electronic device 100 sends the UID of the NFC emulation card in the active state to the NFC card reading device 200.

[0106] In some embodiments of the present application, the electronic device 100 can send the UID parameter in the NFC parameter of the NFC emulation card in the active state to the NFC card reading device 200.

[0107] S106: The NFC card reading device 200 verifies the UID of the NFC emulation card in the active state.

[0108] In some embodiments of the present application, the NFC card reading device 200 can determine whether the UID of the electronic device 100 belongs to the preset UID list of the NFC card reading device 200, and if the determination result is yes, the UID of the electronic device 100 is verified. The preset UID list of the NFC card reading device 200 can include one or more UIDs, for example, the NFC card reading device 200 is a gate access machine of a cell A, and the preset UID list of the NFC card reading device 200 includes the UID of the access card of the cell A.

[0109] In some embodiments of the present application, when the UID of the electronic device 100 is verified by the NFC card reading device 200, the NFC card reading device 200 can continue the subsequent process of the access layer protocol, for example, execute S107.

[0110] S107: The NFC card reading device 200 sends a select command to the electronic device 100.

[0111] In some embodiments of the present application, the NFC card reading device 200 can determine to select the electronic device 100, and therefore can send a select command to the electronic device 100. In some examples, after the NFC card reading device 200 sends an anti-collision command, a UID sent by one electronic device 100 is received, and there is no conflict of multiple PICC mode NFC devices (i.e. no card conflict), therefore, the NFC card reading device 200 can determine to select the electronic device 100.

[0112] In some embodiments of the present application, the select command can include a field SEL, a field NVB, all UIDs of the selected electronic device 100, and a CRC, the field SEL can take a value of 20, and the field NVB can take a value of 70.

[0113] S108: The electronic device 100 sends a select acknowledge (SAK) command (indicating not supporting the application layer protocol) to the NFC card reading device 200.

[0114] In some embodiments of the present application, the select acknowledge command can indicate whether the application layer protocol (for example, the ISO14443-4 protocol or the IEC14443-4 protocol) is supported, in some examples, the length of the select acknowledge command is 1 byte, including 8 bit positions, and the 6th bit position is set to 1 when indicating that the application layer protocol is supported, and set to 0 when indicating that the application layer protocol is not supported.

[0115] In some embodiments of the present application, the electronic device 100 can generate a select acknowledge command according to the SAK parameter in the NFC parameter of the NFC emulation card in the active state, and send the select acknowledge command to the NFC card reading device 200. Since the NFC emulation card in the active state in the electronic device 100 is of the first type, i.e., does not support the application layer protocol, the select acknowledge command sent by the electronic device 100 to the NFC card reading device 200 indicates that the application layer protocol is not supported.

[0116] S109: The NFC card reading device 200 passes the verification of the select acknowledge command.

[0117] In some embodiments of the present application, the NFC card reading device 200 can determine whether the electronic device 100 supports the application layer protocol according to the received select acknowledge command, thereby realizing the verification of the select acknowledge command. FIG. 5 takes the target PICC required by the NFC card reading device 200 as an example, which is the first type of PICC that supports the access layer protocol and does not support the application layer protocol, therefore, when the received select acknowledge command indicates that the application layer protocol is not supported, the NFC card reading device 200 can pass the verification of the select acknowledge command.

[0118] In some embodiments of the present application, since the NFC card reading device passes the verification of the UID in S106, and the NFC card reading device passes the verification of the select acknowledge command in S109, the NFC card reading device 200 can determine that the verification of the NFC emulation card in the active state in the electronic device 100 is successful, and can perform the card swiping business of the NFC emulation card. The card swiping business can include any one of opening the access control, opening the door lock, unlocking the vehicle, transaction payment, electronic ticket ticket checking, digital certificate checking, and traffic card swiping getting on and off the vehicle. In some examples, the NFC card reading device 200 can send the card swiping result of the NFC emulation card in the active state in the electronic device 100 to the electronic device 100, since the NFC card reading device 200 verifies the NFC emulation card in the active state in the electronic device 100 successfully, the card swiping result indicates success, but is not limited to this, in another examples, when the NFC card reading device 200 fails to verify the NFC emulation card in the active state in the electronic device 100, the NFC card reading device 200 can send the card swiping result indicating failure to the electronic device 100.

[0119] In some examples, when the NFC card reading device 200 and the electronic device 100 perform the communication process shown in FIG. 5, the electronic device 100 can output a card swiping prompt of the NFC analog card in the active state, for example, the prompt information can be a card-shaped icon, and the card-shaped icon displays the name of the NFC analog card in the active state. The card swiping prompt of the NFC analog card in the active state can be used to prompt the user that the electronic device 100 is using the NFC analog card to swipe the card. In some examples, after the electronic device 100 receives the card swiping result of the NFC analog card in the active state in the electronic device 100 sent by the NFC card reading device 200, the electronic device 100 can output the card swiping result, for example, prompt the card swiping success or the card swiping failure, and when the card swiping is successful, the electronic device 100 can also prompt the payment information and the like.

[0120] FIG. 6 shows a flow diagram of another communication process.

[0121] The communication process shown in FIG. 6 can be applied to the NFC system including the electronic device 100 and the NFC card reading device 200, for example, the NFC system 10 shown in FIG. 2. In the communication process, the electronic device 100 can be in the PICC mode, for example, the electronic device 100 is in the PICC mode by default after the NFC function of the electronic device 100 is turned on, and the NFC card reading device 200 can be in the PCD mode.

[0122] FIG. 6 takes the NFC analog card in the active state in the electronic device 100 as an example of the second type of NFC analog card, and the communication process shown in FIG. 6 can include the communication process of the access layer protocol of the NFC technology (for example, the ISO 14443-3 protocol / IEC 14443-3 protocol) and the communication process of the application layer protocol (for example, the ISO 14443-4 protocol / IEC 14443-4 protocol).

[0123] The communication process shown in FIG. 6 can include but is not limited to the following steps:

[0124] S200: The electronic device 100 enters the radio frequency field of the NFC card reading device 200.

[0125] S201: The NFC card reading device 200 sends a request command to the electronic device 100.

[0126] S202: The electronic device 100 sends a request response command to the NFC card reading device 200.

[0127] S203: The NFC card reading device 200 verifies the request response command.

[0128] S204: The NFC card reading device 200 sends an anti-collision command to the electronic device 100.

[0129] S205: The electronic device 100 sends the UID of the NFC emulation card in the active state to the NFC card reader 200.

[0130] S206: The NFC card reader 200 passes the UID check of the NFC emulation card in the active state.

[0131] S207: The NFC card reader 200 sends a select command to the electronic device 100.

[0132] S208: The electronic device 100 sends a select acknowledge (SAK) command (indicating support of the application layer protocol) to the NFC card reader 200.

[0133] S209: The NFC card reader 200 passes the select acknowledge command check.

[0134] S200-S209 of FIG. 6 and S100-S109 of FIG. 5 are similar. In S208 of FIG. 6, since the NFC emulation card in the active state in the electronic device 100 is of the second type, i.e., supports the application layer protocol, the select acknowledge command sent by the electronic device 100 to the NFC card reader 200 indicates support of the application layer protocol. In S209 of FIG. 6, FIG. 6 takes the target PICC required by the NFC card reader 200 as the second type of PICC supporting the application layer protocol, and thus, when the received select acknowledge command indicates support of the application layer protocol, the NFC card reader 200 can pass the select acknowledge command check.

[0135] In some embodiments of the present application, when the NFC card reader 200 passes the select acknowledge command sent by the electronic device 100, the NFC card reader 200 can initiate the communication process of the application layer, e.g., S210 can be performed.

[0136] S210: The NFC card reader 200 sends a request for answer to select (RATS) command to the electronic device 100.

[0137] S211: The electronic device 100 sends an answer to select (ATS) command to the NFC card reader 200.

[0138] In some embodiments of the present application, the electronic device 100 includes an NFC emulation card supporting the application layer protocol, and thus, after receiving the RATS command sent by the NFC card reader 200, the electronic device 100 can send an ATS command to the NFC card reader 200.

[0139] In some embodiments of the present application, the ATS command can be used for the electronic device 100 and the NFC card reader 200 to negotiate the communication parameters used in the communication process of the application layer protocol, and the ATS command can include the communication parameters used in the communication process of the application layer protocol in the electronic device 100, such as the length byte (indicating the frame length), the interface byte 1 (indicating the rate), the interface byte 2 (indicating the frame waiting time (FWT) and the start frame guard time (SFGT)), the interface byte 3 (indicating whether the logical channel identity (CID) is supported), the history byte, and the like.

[0140] S212: The NFC card reader 200 checks the select response command.

[0141] In some embodiments of the present application, the NFC card reader 200 can obtain the communication parameters used in the communication process of the application layer protocol in the electronic device 100 according to the select response (ATS) command, and the NFC card reader 200 can determine whether the communication parameters meet the preset requirements of the NFC card reader 200, for example, determine whether the communication parameters are the same as the communication parameters required by the NFC card reader 200 for the communication process of the application layer protocol, if the result of the determination is yes, the check is passed, and if the result of the determination is no, the check is failed. When the NFC card reader 200 checks the ATS command, the NFC card reader 200 and the electronic device 100 can perform the transmission of the application protocol data unit (APDU) in the application layer protocol, for example, S213 can be performed.

[0142] S213: The NFC card reader 200 sends a select AID command (including a first AID) to the electronic device 100.

[0143] In some embodiments of the present application, the select AID command can carry the first AID corresponding to the target PICC required by the NFC card reader 200.

[0144] S214: The electronic device 100 sends the card information of the NFC analog card corresponding to the first AID to the NFC card reader 200.

[0145] In some embodiments of the present application, the electronic device 100 can obtain the first AID carried in the select AID command, and determine whether the NFC analog card corresponding to the first AID exists in one or more NFC analog cards included in the electronic device 100, when the electronic device 100 includes the NFC analog card corresponding to the first AID, the electronic device 100 can send the card information of the NFC analog card corresponding to the first AID to the NFC card reader 200.

[0146] In some examples, the card information of the NFC analog card can include one or more of access control information, key information, transaction account information, electronic ticket information, and the like. The access control information can include one or more of a card number, a validity period of the card number, and the like. The key information can include one or more of a key code, a validity period of the key code, and the like. The transaction account information can include one or more of a transaction account identifier, a remaining amount of the transaction account, and the like. The electronic ticket information can include one or more of an electronic ticket code, a ticket checking time of the electronic ticket, a validity period of the electronic ticket, and the like.

[0147] S215: The NFC card reading device 200 verifies the card information of the NFC analog card corresponding to the first AID.

[0148] In some embodiments of the present application, the NFC card reading device 200 can verify the card information of the NFC analog card corresponding to the first AID received, and when the verification is passed, the NFC card reading device 200 can perform the card swiping business of the NFC analog card. Examples of the card swiping business can be referred to the examples of the card swiping business in FIG. 5. In some examples, the NFC card reading device 200 can send the card swiping result of the NFC analog card in the active state in the electronic device 100 to the electronic device 100. Since the NFC card reading device 200 verifies the NFC analog card in the active state in the electronic device 100 successfully, the card swiping result indicates success, but is not limited to this. In another example, when the NFC card reading device 200 fails to verify the NFC analog card in the active state in the electronic device 100, the NFC card reading device 200 can send the card swiping result indicating failure to the electronic device 100.

[0149] In some examples, when the NFC card reading device 200 and the electronic device 100 perform the communication process shown in FIG. 6, the electronic device 100 can output the card swiping prompt of the NFC analog card in the active state to prompt the user that the electronic device 100 is using the NFC analog card to swipe the card. In some examples, after the electronic device 100 receives the card swiping result of the NFC analog card in the active state in the electronic device 100 sent by the NFC card reading device 200, the electronic device 100 can output the card swiping result, for example, prompt the card swiping success or the card swiping failure, and when the card swiping is successful, the electronic device 100 can also prompt the payment information and the like.

[0150] Not limited to the process shown in FIG. 6, in another embodiment, the NFC card reading device 200 can also not verify the request response command and / or the UID in the communication process of the access layer protocol, but only verify the select acknowledge command, that is, the communication process of the access layer protocol can also not include S203 and / or S206.

[0151] Based on the description of the communication processes shown in FIG. 5 and FIG. 6, it can be obtained that the NFC parameters of the NFC emulation card in the electronic device 100 can include, but are not limited to, a request response command parameter, a UID parameter and a select acknowledge command parameter, which can be referred to as the NFC parameters of the access layer protocol.

[0152] FIG. 7 is a schematic diagram of another architecture of a NFC system 10 according to an embodiment of the present application.

[0153] As shown in FIG. 7, the electronic device 100 can open multiple NFC emulation cards, and can include the NFC parameters of the multiple NFC emulation cards. For example, the electronic device 100 can open a first type of NFC emulation card 1, a second type of NFC emulation card 2 and a third type of NFC emulation card 3, and can include the NFC parameters of the NFC emulation card 1, the NFC parameters of the NFC emulation card 2 and the NFC parameters of the NFC emulation card 3.

[0154] Based on the description of the communication processes shown in FIG. 5 and FIG. 6, in the case that the electronic device 100 opens multiple NFC emulation cards, the electronic device 100 will use the NFC parameters of one NFC emulation card in the active state to perform the NFC technology communication with the NFC card reading device 200. For example, as shown in FIG. 7, the first type of NFC emulation card 1 in the electronic device 100 is in the active state, and the other NFC emulation cards are in the inactive state. The electronic device 100 can use the NFC parameters of the first type of NFC emulation card 1 to perform the communication process with the NFC card reading device 200, in order to attempt to perform the NFC service. However, if the NFC emulation card 1 cannot perform the NFC service with the NFC card reading device 200, for example, the NFC emulation card 1 is not the target PICC required by the NFC card reading device 200, the NFC service will fail. In this case, the electronic device 100 in the powered-off state cannot switch the NFC emulation card in the active state, which directly leads to the card swiping failure, and the user cannot use the electronic device 100 and the NFC card reading device 200 to perform the card swiping business. While the electronic device 100 in the powered-on state can randomly switch the NFC emulation card in the active state, for example, switch the NFC emulation card 2 to the active state, and switch the NFC emulation card 1 to the inactive state, and then use the NFC parameters of the NFC emulation card 2 to perform the communication process with the NFC card reading device 200, for example, perform the communication process shown in FIG. 5 / FIG. 6 again. However, this will lead to a slow card swiping process, especially the NFC emulation card in the active state switched randomly by the electronic device 100 can still not be the target PICC required by the NFC card reading device 200, which leads to the need to perform the NFC technology communication process (for example, the communication process of the access layer protocol) multiple times, and the card swiping process is very slow.

[0155] And, in the case that the electronic device 100 opens multiple NFC emulation cards, multiple NFC emulation cards cannot be activated simultaneously, i.e., multiple NFC emulation cards in the electronic device 100 cannot be activated simultaneously. Because, if multiple NFC emulation cards in the electronic device 100 are activated simultaneously, the electronic device 100 uses the NFC parameters of multiple NFC emulation cards to communicate with the NFC reading device 200, for example, as shown in FIG. 7, the electronic device 100 uses the NFC parameter 1 of the NFC emulation card 1, the NFC parameter 2 of the NFC emulation card 2, and the NFC parameter 3 of the NFC emulation card 3 to communicate with the NFC reading device 200, the NFC reading device 200 cannot identify the NFC command including the NFC parameters of multiple NFC emulation cards, there is a conflict of the NFC parameters, and the NFC service fails to be executed.

[0156] The embodiment of the present application provides a card management method, which can set the NFC card reading device 200 in the PCD mode to not check the NFC parameter of the access layer protocol in the electronic device 100, for example, not to check the request response command, the UID and the selection confirmation command. The electronic device 100 in the PICC mode can use the NFC parameter of the NFC simulation card in the default active state to perform the communication process of the access layer protocol with the NFC card reading device 200, and since the NFC card reading device 200 does not check the NFC parameter of the access layer protocol, the NFC card reading device 200 initiates the communication process of the application layer protocol. In the communication process of the application layer protocol, the electronic device 100 can determine the corresponding NFC simulation card from the plurality of NFC simulation cards of the electronic device 100 according to the AID in the selection AID command sent by the NFC card reading device 200, and the electronic device 100 can use the determined NFC simulation card to perform the NFC service with the NFC card reading device 200. That is to say, the electronic device 100 determines the corresponding NFC simulation card of the NFC card reading device 200 from the plurality of NFC simulation cards of the electronic device 100 to perform the NFC service each time when the electronic device 100 performs the communication process of the NFC technology with the NFC card reading device 200, and the plurality of NFC simulation cards not only include the NFC simulation card in the default active state, but also include other NFC simulation cards, and the electronic device 100 does not directly use the NFC simulation card in the default active state to perform the NFC service with the NFC card reading device 200. It can be understood that the plurality of NFC simulation cards of the electronic device 100 will "participate" in each communication process of the NFC technology, and thus the simultaneous activation coexistence of the plurality of NFC simulation cards in the electronic device 100 is realized, and the NFC simulation cards except the NFC simulation card in the default active state in the plurality of NFC simulation cards can be called as being in the long active state. Therefore, the electronic device 100 which realizes the simultaneous activation coexistence of the plurality of NFC simulation cards can automatically and accurately select the appropriate NFC simulation card to complete the NFC service with the NFC card reading device, and the speed and efficiency of NFC card swiping are improved, and even the electronic device 100 in the shutdown state can normally swipe the card.

[0157] In some embodiments of the present application, the NFC card reading device 200 in the PCD mode can also be set to not check the NFC parameter of the application layer protocol in the electronic device 100, or only to judge whether the format of the NFC parameter of the application layer protocol is correct (it can be understood that no special requirement is made on the specific content of the NFC parameter of the application layer protocol), for example, not to check the selection response (ATS) command or only to judge whether the format of the ATS command is correct. Therefore, it can be ensured that the NFC card reading device 200 can send the selection AID command to the electronic device 100 in the communication process of the application layer protocol, so that the simultaneous activation coexistence of the plurality of NFC simulation cards of the electronic device 100 is realized.

[0158] In some embodiments of the present application, the second type of NFC emulation card in the electronic device 100 is in a long active state. In some embodiments of the present application, the NFC parameters of the access layer protocol of the NFC emulation card in the long active state in the electronic device 100 can be set to null, and optionally, the NFC parameters of the application layer protocol can also be set to null. For implementation examples, refer to the updated NFC parameter acquisition mode shown in FIG. 9, which is not described in detail here.

[0159] FIG. 8 is a schematic diagram of another architecture of a NFC system 10 according to an embodiment of the present application.

[0160] As shown in FIG. 8, the electronic device 100 can open multiple NFC emulation cards, and can include NFC parameters of the multiple NFC emulation cards, which can include one NFC emulation card in a default active state and one or more NFC emulation cards in a long active state. For example, the electronic device 100 can open a first type of NFC emulation card 1, a second type of NFC emulation card 2, and a second type of NFC emulation card 3, etc. The NFC emulation card 1 is in a default active state, and the NFC emulation card 2 and the NFC emulation card 3 are in a long active state. The electronic device can include the NFC parameters 1 of the NFC emulation card 1, and the NFC parameters of the NFC emulation card 2 and the NFC emulation card 3 are null.

[0161] In some embodiments of the present application, the electronic device 100 in the PICC mode can use the NFC parameters 1 of the NFC emulation card 1 in the default active state to perform the access layer protocol communication process with the NFC card reading device 200. The NFC parameters do not conflict, and the NFC card reading device 200 can normally identify the NFC signaling sent by the electronic device 100. The NFC card reading device 200 does not verify the request response command, UID, and SAK command sent by the electronic device 100, so the NFC card reading device 200 can normally perform the access layer protocol communication process, and can initiate the application layer protocol communication process. In the application layer protocol communication process, the electronic device 100 can determine the NFC emulation card corresponding to the first AID from the NFC emulation card 2 and the NFC emulation card 3 in the long active state according to the first AID in the select AID command sent by the NFC card reading device 200. Assuming that the determined NFC emulation card corresponding to the first AID is the NFC emulation card 2, the electronic device 100 can send the card information of the NFC emulation card 2 to the NFC card reading device 200 to perform the NFC service of the NFC emulation card 2 with the NFC card reading device 200.

[0162] FIG. 9 is a schematic diagram of a NFC parameter setting mode according to an embodiment of the present application.

[0163] FIG. 9 illustrates an example of the NFC parameters (including the ATQA parameter, the UID parameter, and the SAK parameter) of the access layer protocol.

[0164] As shown in FIG. 9, the NFC parameters of the NFC emulation card in the electronic device 100 can be obtained by performing a bitwise AND operation on the corresponding configured parameters and the corresponding configured masks. For example, the actual ATQA parameter (2 bytes in length) can be obtained by performing a bitwise AND operation on the configured ATQA parameter (2 bytes in length) and the configured ATQA mask (2 bytes in length), the actual SAK parameter (1 byte in length) can be obtained by performing a bitwise AND operation on the configured SAK parameter (1 byte in length) and the configured SAK mask (1 byte in length), and the actual UID parameter (4 bytes in length) can be obtained by performing a bitwise AND operation on the configured UID parameter (4 bytes in length) and the configured UID mask (4 bytes in length).

[0165] The updated NFC parameter acquisition method shown in FIG. 9 can be applied to the NFC emulation card in the long-activated state in the electronic device 100 to set the NFC parameters of the NFC emulation card in the long-activated state to zero. As shown in FIG. 9, the NFC parameters of the NFC emulation card in the long-activated state in the electronic device 100 can be obtained by performing a bitwise AND operation on the corresponding configured parameters and the corresponding configured masks, but the corresponding configured masks are all set to zero, and thus the obtained NFC parameters are all zero. For example, the actual ATQA parameter obtained by performing a bitwise AND operation on the configured ATQA parameter and the ATQA mask set to zero is zero, the actual SAK parameter obtained by performing a bitwise AND operation on the configured SAK parameter and the SAK mask set to zero is zero, and the actual UID parameter obtained by performing a bitwise AND operation on the configured UID parameter and the UID mask set to zero is zero.

[0166] Exemplarily, the NFC parameter file of the NFC emulation card in the electronic device 100 can include the parameters (for example, the configured ATQA parameter, the configured UID parameter and the configured SAK parameter) corresponding to the configuration of the NFC parameters and the masks (for example, the configured ATQA mask, the configured UID mask and the configured SAK mask) corresponding to the configuration of the NFC parameters. Based on the updated NFC parameter acquisition mode shown in FIG. 9, the configured masks in the NFC parameter file can be set to zero. For example, the NFC parameter file in which the configured masks are not set to zero includes: 80E640006D000010A00000033301010200634857504150200057EF55A053810100A5038201C08649A01E8005040878702C81012082020800830302424A8401908501018603020200A12780050FFFFFFFFF8101FF8202FFFF 830C0FFFFFFFFFFFFFFFFFFFFFFF8401FF8501FF8603FFFFFF00|9000, wherein the 80th-86th bits are the masks corresponding to the configuration of the NFC parameters. Based on the updated NFC parameter acquisition mode shown in FIG. 9, the 80th-86th bits can be set to zero, and thus the NFC parameter file in which the masks are set to zero includes: 80E640006D000010A00000033301010200634857504150200057EF55A053810100A5038201C08649A01E8005040878702C81012082020800830302424A8401908501018603020200A1278005000000000081010082020000830C000000000000000000000000840100850100860300000000|9000.

[0167] Not limited to the example shown in FIG. 9, in other examples, the NFC parameter acquisition mode shown in FIG. 9 can also be the NFC parameter acquisition mode of the application layer protocol. For example, the ATS parameter actually used by the NFC emulation card can be obtained by performing a bitwise AND operation on the configured ATS parameter and the configured ATS mask. Since the configured ATS mask of the NFC emulation card in the long active state is set to zero in the updated NFC parameter acquisition mode, the ATS parameter actually used by the NFC emulation card in the long active state is zero.

[0168] Not limited to the above examples, in other examples, the length of the actually used UID parameter, the configured UID parameter and the UID mask can also be 7 bytes or 10 bytes, etc. The length of the NFC parameter is not limited in the embodiments of the present application.

[0169] Next, a card management method provided by the embodiments of the present application is introduced.

[0170] FIG. 10 is a flow diagram of a card management method provided by the embodiments of the present application.

[0171] The method shown in FIG. 10 can be applied to an NFC system including the electronic device 100 and the NFC card reading device 200, for example, the NFC system 10 shown in FIG. 2. Wherein, the electronic device 100 can be in a PICC mode, for example, the electronic device 100 is in the PICC mode by default after the NFC function is turned on, and the NFC card reading device 200 can be in a PCD mode.

[0172] FIG. 10 takes the NFC emulation card in the default active state in the electronic device 100 as an example of the first type of NFC emulation card, and the method shown in FIG. 10 can include a communication process of an access layer protocol (for example, ISO14443-3 protocol / IEC14443-3 protocol) and a communication process of an application layer protocol (for example, ISO14443-4 protocol / IEC14443-4 protocol).

[0173] The method shown in FIG. 10 can include but is not limited to the following steps:

[0174] S300: The electronic device 100 enters the radio frequency field of the NFC card reading device 200.

[0175] S301: The NFC card reading device 200 sends a request command to the electronic device 100.

[0176] S302: The electronic device 100 sends a request response command to the NFC card reading device 200.

[0177] S300-S302 of FIG. 10 and S100-S102 of FIG. 5 are similar.

[0178] In some embodiments of the present application, after the NFC card reading device 200 receives the request response command sent by the electronic device 100, the NFC card reading device 200 can not verify the request response command, and directly perform the subsequent process of the access layer protocol, for example, perform S303.

[0179] S303: The NFC card reading device 200 sends an anti-collision command to the electronic device 100.

[0180] S304: The electronic device 100 sends the UID of the NFC emulation card in the default active state to the NFC card reading device 200.

[0181] S303-S304 of FIG. 10 and S104-S105 of FIG. 5 are similar.

[0182] In some embodiments of the present application, after receiving the UID of the NFC emulation card in the default active state sent by the electronic device 100, the NFC card reading device 200 can not verify the UID of the NFC emulation card in the default active state, and directly proceed to the subsequent process of the access layer protocol, for example, perform S305.

[0183] S305: The NFC card reading device 200 sends a select command to the electronic device 100.

[0184] S306: The electronic device 100 sends a select confirmation command (indicating that the application layer protocol is not supported) to the NFC card reading device 200.

[0185] S305-S306 of FIG. 10 and S107-S108 of FIG. 5 are similar.

[0186] In some embodiments of the present application, the electronic device 100 can generate a select confirmation command according to the SAK parameter in the NFC parameter of the NFC emulation card in the default active state, and send the select confirmation command to the NFC card reading device 200. Since the NFC emulation card in the default active state in the electronic device 100 is of the first type, that is, does not support the application layer protocol, the select confirmation command sent by the electronic device 100 to the NFC card reading device 200 indicates that the application layer protocol is not supported.

[0187] In some embodiments of the present application, after receiving the SAK command sent by the electronic device 100, the NFC card reading device 200 can not verify the SAK command. Therefore, even if the SAK command indicates that the application layer protocol is not supported, the NFC card reading device 200 will initiate the communication process of the application layer protocol, for example, can perform S307.

[0188] S307: The NFC card reading device 200 sends a request for a select response (RATS) command to the electronic device 100.

[0189] S308: The electronic device 100 sends an application select response (ATS) command to the NFC card reading device 200.

[0190] In some embodiments of the present application, the electronic device 100 can generate an ATS command according to an ATS parameter in the NFC parameter of the application layer protocol of any one of the NFC emulation cards in the long active state, and send the ATS command to the NFC reader 200. In some examples, the content of the ATS command can be set to empty according to the updated NFC parameter acquisition mode shown in FIG. 9.

[0191] S309: The NFC reader 200 checks the select response command.

[0192] S307-S309 of FIG. 10 and S210-S212 of FIG. 6 are similar.

[0193] Not limited to the above embodiments, in some other embodiments of the present application, after receiving the ATS command sent by the electronic device 100, the NFC reader 200 can also not check whether the content (i.e., the communication parameter for implementing the communication process of the application layer protocol in the electronic device 100) in the ATS command meets the preset requirement of the NFC reader 200, but only determine whether the format of the ATS command is correct, which can be understood as not having special requirements for the specific content of the ATS command. In S309, if the NFC reader 200 determines that the format of the ATS command is correct, the check is passed, and if the NFC reader 200 determines that the format of the ATS command is incorrect, the check is failed. When the NFC reader 200 passes the check of the ATS command, the NFC reader 200 and the electronic device 100 can perform the transmission of the APDU in the application layer protocol, for example, S310 can be performed.

[0194] In some other embodiments of the present application, the NFC reader 200 can also be configured not to check the NFC parameter of the application layer protocol in the electronic device 100, for example, not to check the ATS command sent by the electronic device 100.

[0195] S310: The NFC reader 200 sends a select AID (select AID) command (including the first AID) to the electronic device 100.

[0196] In some embodiments of the present application, the select AID (select AID) command can carry the first AID corresponding to the target PICC required by the NFC reader 200.

[0197] S311: The electronic device 100 determines the NFC emulation card corresponding to the first AID.

[0198] S312: The electronic device 100 sends the card information of the NFC emulation card corresponding to the first AID to the NFC reader 200.

[0199] In some embodiments of the present application, the electronic device 100 can obtain the first AID according to the select AID command, and the electronic device 100 can determine the NFC emulation card corresponding to the first AID from the plurality of NFC emulation cards of the electronic device 100, the plurality of NFC emulation cards of the electronic device 100 can include one NFC emulation card in the default active state and one or more NFC emulation cards in the long active state. The electronic device 100 can send the card information of the determined NFC emulation card corresponding to the first AID to the NFC card reading device 200, and examples of the card information of the NFC emulation card can refer to the examples of the card information of the NFC emulation card in S214 of FIG. 6.

[0200] S313: The NFC card reading device 200 verifies the card information of the NFC emulation card corresponding to the first AID.

[0201] S313 of FIG. 10 and S215 of FIG. 6 are similar.

[0202] For example, the electronic device 100 can include an access card (the first type of NFC emulation card) in the default active state, a transportation card (the second type of NFC emulation card) in the long active state, and a bank card (the second type of NFC emulation card) in the long active state. When the NFC card reading device 200 is a transportation gate, the electronic device 100 can first use the NFC parameters of the access card and the NFC card reading device 200 to perform the communication process of the access layer protocol, and obtain the first AID in the select AID command sent by the NFC card reading device 200 in the communication process of the application layer protocol, the electronic device 100 can determine the transportation card corresponding to the first AID, and use the transportation card and the NFC card reading device 200 to perform the business of transportation card swiping. When the NFC card reading device 200 is a POS machine, the electronic device 100 can first use the NFC parameters of the access card and the NFC card reading device 200 to perform the communication process of the access layer protocol, and obtain the first AID in the select AID command sent by the NFC card reading device 200 in the communication process of the application layer protocol, the electronic device 100 can determine the bank card corresponding to the first AID, and use the bank card and the NFC card reading device 200 to perform the business of transaction payment.

[0203] Not limited to the above embodiments, in some embodiments of the present application, the electronic device 100 can also use the preset NFC parameters and the NFC card reading device 200 to perform the communication process of the access layer protocol. In some examples, the request response command in S302, the UID in S304, and the select confirmation command in S306 shown in FIG. 10 can be generated and sent according to the preset NFC parameters, the UID in S304 is sent according to the preset NFC parameters, for example, the parameters of the request response command, the parameters of the select confirmation command, and the UID obtained according to the preset NFC parameters are empty.

[0204] It can be understood that when the electronic device 100 is in the power-off state, the electronic device 100 can perform the transmission process of the APDU in the application layer protocol with the NFC card reading device 200, in which the electronic device 100 can automatically and accurately select a suitable NFC emulation card and send the card information of the NFC emulation card to the NFC card reading device 200, for example, by obtaining the card information of the NFC emulation card through the Applet in the SE 103 or the SIM 104, without switching the NFC emulation card in the default active state, so that the card swiping failure caused by the inability to switch the NFC emulation card in the default active state is avoided, and thus the NFC service can be normally completed between the electronic device 100 and the NFC card reading device 200 even when the electronic device 100 is in the power-off state.

[0205] In the method shown in FIG. 10, the NFC card reading device 200 in the PCD mode can be set to not verify the NFC parameter of the access layer protocol, so that the NFC card reading device 200 initiates the communication process of the application layer protocol regardless of whether the SAK command sent by the electronic device 100 indicates that the application layer protocol is supported. In addition, the NFC card reading device 200 can be set to not verify the NFC parameter of the application layer protocol or only determine whether the format of the NFC parameter of the application layer protocol is correct, so that the transmission of the APDU in the application layer protocol between the NFC card reading device 200 and the electronic device 100 can be ensured. In the transmission process of the APDU in the application layer protocol, the electronic device 100 can determine the NFC emulation card required by the NFC card reading device 200 from the NFC emulation card in the default active state and the NFC emulation card in the long active state to perform the NFC service, instead of using only the NFC emulation card in the default active state to perform the NFC service. The electronic device 100 realizes the activation coexistence of multiple NFC emulation cards, and the electronic device 100 can automatically and accurately select a suitable NFC emulation card to complete the NFC service with the NFC card reading device through one communication process (for example, the flow shown in FIG. 10), and the card swiping can be normally performed regardless of whether the electronic device 100 is in the power-on state or the power-off state, thereby improving the speed and efficiency of NFC card swiping, for example, the card swiping time is less than 400 milliseconds.

[0206] Not limited to the above embodiments, in some other embodiments of the present application, the NFC card reading device 200 in PCD mode can also not be set to not check the NFC parameter, which can be understood as not modifying the processing logic of the NFC card reading device 200. The electronic device 100 in PICC mode can first use the NFC parameter of the NFC emulation card in the default active state (for example, the first type of NFC emulation card) to perform the communication process of the access layer protocol with the NFC card reading device 200. If the NFC card reading device 200 does not initiate the communication process of the application layer protocol within a preset time period, the electronic device 100 can dynamically switch / modify the NFC parameter, for example, modify the SAK parameter to indicate that the application layer protocol is supported, and perform the communication process of the access layer protocol and the communication process of the application layer protocol with the NFC card reading device 200 using the new NFC parameter. For specific implementation examples, please refer to FIG. 11.

[0207] FIG. 11 is a flow diagram of another card management method according to an embodiment of the present application.

[0208] The method shown in FIG. 11 can be applied to an NFC system including an electronic device 100 and an NFC card reading device 200, for example, the NFC system 10 shown in FIG. 2. Among them, the electronic device 100 can be in PICC mode, for example, the electronic device 100 is in PICC mode by default after the NFC function is turned on, and the NFC card reading device 200 can be in PCD mode.

[0209] FIG. 11 takes the NFC emulation card in the default active state in the electronic device 100 as the first type of NFC emulation card as an example for illustration. The communication process shown in FIG. 11 can include the communication process of the access layer protocol (for example, ISO14443-3 protocol / IEC14443-3 protocol) and the communication process of the application layer protocol (for example, ISO14443-4 protocol / IEC14443-4 protocol).

[0210] FIG. 11 takes the target PICC of the NFC card reading device 200 as the second type of PICC, that is, the PICC supporting the application layer protocol as an example for illustration. Moreover, FIG. 11 takes the processing logic of the NFC card reading device 200 as an example for illustration, which does not check the request response command and the UID, but checks the SAK command.

[0211] The method shown in FIG. 11 can include but is not limited to the following steps:

[0212] S400: The electronic device 100 enters the radio frequency field of the NFC card reading device 200.

[0213] S401: The NFC card reading device 200 sends a request command to the electronic device 100.

[0214] S402: The electronic device 100 sends a request response command to the NFC card reader 200.

[0215] S403: The NFC card reader 200 sends an anti-collision command to the electronic device 100.

[0216] S404: The electronic device 100 sends a UID of the NFC emulation card in a default active state to the NFC card reader 200.

[0217] S405: The NFC card reader 200 sends a select command to the electronic device 100.

[0218] S406: The electronic device 100 sends a select acknowledgement command (indicating that the application layer protocol is not supported) to the NFC card reader 200.

[0219] S400-S406 of FIG. 11 and S300-S306 of FIG. 10 are similar.

[0220] S407: The NFC card reader 200 fails to verify the select acknowledgement command.

[0221] In some embodiments of the present application, the NFC card reader 200 can determine whether the electronic device 100 supports the application layer protocol according to the received select acknowledgement (SAK) command, thereby verifying the select acknowledgement command. FIG. 11 takes the target PICC required by the NFC card reader 200 as the second type of PICC supporting the application layer protocol as an example, and therefore, when the received SAK command indicates that the application layer protocol is not supported, the NFC card reader 200 fails to verify the select acknowledgement command, and therefore, does not initiate the communication process of the application layer protocol.

[0222] S408: The electronic device 100 determines that the select response request command is not received within a preset time period.

[0223] In some embodiments of the present application, after the electronic device 100 sends the select acknowledgement command to the NFC card reader 200, if the select response request (RATS) command of the application layer protocol is not received within a preset time period, and the electronic device 100 is still in the radio frequency field of the NFC card reader 200, the electronic device 100 can determine to switch / modify the NFC parameters and obtain new NFC parameters. In some examples, the SAK command in the new NFC parameters is different from the SAK command in the old NFC parameters, and the SAK command in the new NFC parameters indicates that the application layer protocol is supported. The electronic device 100 can use the new NFC parameters to communicate with the NFC card reader 200 in the NFC technology, and implement a process such as S409-S414.

[0224] S409: The NFC card reading device 200 sends a request command to the electronic device 100.

[0225] S410: The electronic device 100 sends a request response command to the NFC card reading device 200.

[0226] S411: The NFC card reading device 200 sends an anti-collision command to the electronic device 100.

[0227] S412: The electronic device 100 sends the UID of the NFC emulation card in the default active state to the NFC card reading device 200.

[0228] S413: The NFC card reading device 200 sends a select command to the electronic device 100.

[0229] S414: The electronic device 100 sends a select acknowledgement command (indicating support of the application layer protocol) to the NFC card reading device 200.

[0230] S409-S414 are similar to S401-S406 described above. The request response command in S402, the UID in S404 and the select acknowledgement command in S406 are obtained according to the old NFC parameters (i.e. the NFC parameters of the NFC emulation card in the default active state in the electronic device 100). The request response command in S410, the UID in S412 and the select acknowledgement command in S414 are obtained according to the new NFC parameters obtained by modification, and therefore the select acknowledgement command in S414 can indicate support of the application layer protocol.

[0231] S415: The NFC card reading device 200 verifies the select acknowledgement command.

[0232] In some embodiments of the present application, the NFC card reading device 200 can determine whether the electronic device 100 supports the application layer protocol according to the received select acknowledgement (SAK) command, thereby verifying the select acknowledgement command. FIG. 11 takes the target PICC required by the NFC card reading device 200 as the second type of PICC supporting the application layer protocol as an example, and therefore when the received SAK command indicates support of the application layer protocol, the NFC card reading device 200 verifies the select acknowledgement command, and therefore initiates the communication process of the application layer protocol, such as performing S416.

[0233] S416: The NFC card reading device 200 sends a request response command to the electronic device 100.

[0234] S417: The electronic device 100 sends an ATS (select answer) command to the NFC card reader 200.

[0235] S418: The NFC card reader 200 verifies the select answer command.

[0236] S419: The NFC card reader 200 sends a select AID (select AID) command (including the first AID) to the electronic device 100.

[0237] S420: The electronic device 100 determines the NFC analog card corresponding to the first AID.

[0238] S421: The electronic device 100 sends the card information of the NFC analog card corresponding to the first AID to the NFC card reader 200.

[0239] S422: The NFC card reader 200 verifies the card information of the NFC analog card corresponding to the first AID.

[0240] S416-S422 of FIG. 11 and S307-S313 of FIG. 10 are similar.

[0241] Without being limited to the above examples, in other examples, when the electronic device 100 dynamically switches / modifies the NFC parameters, the electronic device 100 can modify not only the SAK command parameters, but also the request response command parameters and / or the UID parameters, for example, the request response command parameters can be modified when the anti-collision command is not received within the preset time length, and for example, the UID parameters can be modified when the select command is not received within the preset time length, and the judgment conditions and specific manners of dynamically switching / modifying the NFC parameters are not limited in the embodiments of the present application.

[0242] Without being limited to the above embodiments, in other embodiments of the present application, the electronic device 100 can also use the preset NFC parameters to perform the communication process of the access layer protocol with the NFC card reader 200, for example, in the case that the electronic device 100 does not include the first type of NFC analog card. In some examples, the request response command in S402, the UID in S404 and the select confirmation command in S406 shown in FIG. 11 can be generated and sent according to the preset NFC parameters, and the UID in S404 is sent according to the preset NFC parameters.

[0243] Without being limited to the examples shown in FIG. 10 and FIG. 11, in other examples, the electronic device 100 can determine the card information of the corresponding NFC analog card according to the first AID and other information sent by the NFC card reader 200, and the specific parameters for determining the card information of the NFC analog card are not limited in the embodiments of the present application.

[0244] Not limited to the examples shown in FIG. 10 and FIG. 11, in other examples, the electronic device 100 can also not send the card information of the NFC emulation card corresponding to the first AID, for example, S311-S313 of FIG. 10 or S420-S422 of FIG. 11 can be: the NFC reading device 200 and the electronic device 100 perform NFC interaction, and complete the card swiping business of the NFC emulation card in the electronic device 100.

[0245] In the method shown in FIG. 11, the NFC reading device 200 in PCD mode can not modify the processing logic, but dynamically switch / modify the NFC parameters used by the electronic device 100, and use the new NFC parameters to communicate with the NFC reading device 200, so that the NFC reading device 200 initiates the communication process of the application layer protocol. In the communication process of the application layer protocol, the electronic device 100 can determine the NFC emulation card required by the NFC reading device 200 from the NFC emulation card in the default active state and the NFC emulation card in the long active state to perform NFC service, instead of only using the NFC emulation card in the default active state to perform NFC service. Therefore, even if the processing logic of the NFC reading device 200 is not modified, the electronic device 100 can realize the activation coexistence of multiple NFC emulation cards, and automatically and accurately select the appropriate NFC emulation card to complete the NFC service with the NFC reading device. It can be understood that the forward compatibility of the NFC reading device 200 with unmodified processing logic is realized by the electronic device 100 dynamically switching / modifying the NFC parameters.

[0246] Next, another hardware structure of the electronic device 100 provided by the embodiments of the present application is introduced.

[0247] FIG. 12 is a schematic diagram of a hardware structure of an electronic device 100 provided by an embodiment of the present application.

[0248] The following will be described in detail with the electronic device 100 as an example. It should be understood that the electronic device 100 shown in FIG. 12 is only an example, and the electronic device 100 can have more or fewer components than those shown in FIG. 12, can combine two or more components, or can have a different component configuration. The various components shown in the figure can be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and / or application-specific integrated circuits. As shown in FIG. 12, the electronic device 100 can include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headset interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a SIM card interface 195, etc. The sensor module 180 can include a pressure sensor 180A, a gyroscope sensor 180B, a barometric 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, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

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

[0250] The controller can generate operation control signals according to instruction operation codes and timing signals to complete the control of fetching and executing instructions.

[0251] The processor 110 can also include a memory for storing instructions and data. In one embodiment, the memory in the processor 110 is a cache memory. The memory can hold instructions or data that the processor 110 has just used or is using in a loop. If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. This avoids repeated access and reduces the latency of the processor 110, thus improving the efficiency of the system.

[0252] In one embodiment, the processor 110 can include one or more interfaces. The interfaces can include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM interface, and / or a universal serial bus (USB) interface, etc.

[0253] The charging management module 140 is configured to receive charging input from a charger. The charger can be a wireless charger or a wired charger. In some embodiments of wired charging, the charging management module 140 can receive charging input from a wired charger through the USB interface 130. In some embodiments of wireless charging, the charging management module 140 can receive wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 can charge the battery 142 while also supplying power to the electronic device 100 through the power management module 141.

[0254] The power management module 141 is configured to connect the battery 142 and the charging management module 140 to the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 can also be configured to monitor parameters such as battery capacity, battery cycle count, battery health (leakage, impedance), and the like. In another embodiment, the power management module 141 can also be disposed in the processor 110. In another embodiment, the power management module 141 and the charging management module 140 can also be disposed in the same device.

[0255] The wireless communication function of the electronic device 100 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor, and the like.

[0256] The antenna 1 and the antenna 2 are configured to transmit and receive electromagnetic wave signals. Each antenna in the electronic device 100 can be configured to cover a single or multiple communication frequency bands. When an antenna covers multiple communication frequency bands for different communication modes, the antenna can be referred to as a mutual antenna, and the mutual antenna can be described with reference to the above-described case 1, case 2, and case 3. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example, the antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In another embodiment, the antenna can be used in combination with a tuning switch.

[0257] The mobile communication module 150 can provide a solution for wireless communication including second generation (2G) / third generation (3G) / fourth-generation (4G) / fifth generation (5G) / sixth generation (6G) or the like applied to the electronic device 100. The mobile communication module 150 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), or the like. The mobile communication module 150 can receive an electromagnetic wave by the antenna 1, and perform filtering, amplification, or the like on the received electromagnetic wave, and transfer the same to the modem processor to be demodulated. The mobile communication module 150 can also amplify a signal modulated by the modem processor, and radiate the same as an electromagnetic wave through the antenna 1. In an embodiment, at least part of the function modules of the mobile communication module 150 can be disposed in the processor 110. In an embodiment, at least part of the function modules of the mobile communication module 150 can be disposed in the same device as at least part of the modules of the processor 110.

[0258] The modem processor can include a modulator and a demodulator. The modulator can modulate a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator can demodulate a received electromagnetic wave signal into a low-frequency baseband signal. The demodulator can then transfer the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal processed by the baseband processor can be transferred to the application processor. The application processor can output a sound signal through an audio device (not limited to the speaker 170A, the microphone 170B, or the like), or display an image or a video through the display screen 194. In an embodiment, the modem processor can be a separate device. In another embodiment, the modem processor can be disposed in the same device as the mobile communication module 150 or other function modules independently of the processor 110.

[0259] The wireless communication module 160 can provide a solution for wireless communication including wireless local area networks (WLAN) (e.g., wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), sparklink alliance specification-based wireless communication technology (e.g., sparklink low energy (SLE), sparklink basic (SLB)), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives an electromagnetic wave via the antenna 2, frequency-modulates and filters the electromagnetic wave signal, and transmits the processed signal to the processor 110. The wireless communication module 160 can also receive a signal to be transmitted from the processor 110, frequency-modulate it, amplify it, and radiate it as an electromagnetic wave via the antenna 2.

[0260] In one embodiment, the antenna 1 and the mobile communication module 150 of the electronic device 100 are coupled, and the antenna 2 and the wireless communication module 160 are coupled, so that the electronic device 100 can communicate with a network and other devices through wireless communication technology. The wireless communication technology can include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS can include a global positioning system (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and / or a satellite based augmentation systems (SBAS).

[0261] The electronic device 100 implements a display function through a GPU, a display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, which is connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 can include one or more GPUs, which execute program instructions to generate or change display information.

[0262] The display screen 194 is configured to display images, videos, and the like. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flex light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light emitting diodes (QLED), or the like. In an embodiment, the electronic device 100 can include N display screens 194, where N is a positive integer greater than 1.

[0263] The electronic device 100 can implement the photographing function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, and the application processor.

[0264] The ISP is configured to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, the light is transmitted to the camera photosensitive element through the lens, the light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing to convert it into an image visible to the naked eye. The ISP can also optimize the algorithm for the noise and brightness of the image. The ISP can also optimize the exposure and color temperature of the shooting scene. In an embodiment, the ISP can be arranged in the camera 193.

[0265] The camera 193 is configured to capture still images or videos. An object generates an optical image through a lens and projects it onto a 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 light signal into an electrical signal, which is then transmitted to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In an embodiment, the electronic device 100 can include one or N cameras 193, where N is a positive integer greater than 1.

[0266] The digital signal processor is used to process digital signals, in addition to being able to process digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy, etc.

[0267] The video codec is used to compress or decompress digital video. The electronic device 100 can support one or more video codecs. In this way, the electronic device 100 can play or record videos in multiple encoding formats, such as: moving picture experts group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0268] The NPU is a neural-network (NN) calculation processor, which can quickly process input information by drawing on the structure of a biological neural network, such as drawing on the transmission mode between human brain neurons, and can also constantly self-learn. Through the NPU, the electronic device 100 can realize intelligent cognition applications such as image recognition, face recognition, voice recognition, text understanding, etc.

[0269] 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 electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to realize data storage functions. For example, music, video, etc. Files are saved in the external memory card.

[0270] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 can include a program storage area and a data storage area. The program storage area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.), etc. The data storage area can store data created during the use of the electronic device 100 (such as audio data, a phonebook, etc.), etc. In addition, the internal memory 121 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various function applications and data processing of the electronic device 100 by running instructions stored in the internal memory 121 and / or instructions stored in the memory arranged in the processor.

[0271] The electronic device 100 can implement an audio function through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone interface 170D, and an application processor, etc. The electronic device 100 can also implement an audio function through a connected Bluetooth device. For example, music play, voice recording, etc.

[0272] The audio module 170 is used to convert digital audio information into an analog audio signal output, and also used to convert an analog audio input into a digital audio signal. The audio module 170 can also be used to encode and decode an audio signal. In an embodiment, the audio module 170 can be disposed in the processor 110, or part of the functions of the audio module 170 can be disposed in the processor 110.

[0273] The speaker 170A, also called "loudspeaker", is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or listen to a hands-free call through the speaker 170A.

[0274] The receiver 170B, also called "earpiece", is used to convert an audio electrical signal into a sound signal. When the electronic device 100 answers a call or a voice message, the receiver 170B can be held close to a human ear to listen to the voice.

[0275] The microphone 170C, also called "microphone", "sound transducer", is used to convert a sound signal into an electrical signal. When making a call or sending a voice message, a user can speak into the microphone 170C close to the human mouth to input a sound signal into the microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In another embodiment, the electronic device 100 can be provided with two microphones 170C, in addition to collecting a sound signal, it can also implement a noise reduction function. In another embodiment, the electronic device 100 can also be provided with three, four or more microphones 170C, in addition to collecting a sound signal, noise reduction, it can also identify the source of the sound, implement a directional recording function, etc.

[0276] The pressure sensor 180A is configured to sense a pressure signal and convert the pressure signal into an electrical signal. In an embodiment, the pressure sensor 180A can be disposed on the display screen 194. The pressure sensor 180A can be of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, etc. The capacitive pressure sensor can include at least two parallel plates of conductive material. When a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation is applied to the display screen 194, the electronic device 100 detects the intensity of the touch operation based on the pressure sensor 180A. The electronic device 100 can also calculate the location of the touch based on the detection signal of the pressure sensor 180A. In an embodiment, touch operations applied to the same touch location but with different touch operation intensities can correspond to different operation instructions. For example, when a touch operation with an intensity less than a first pressure threshold is applied to a short message application icon, an instruction to view short messages is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the short message application icon, an instruction to create a new short message is executed.

[0277] The gyroscope sensor 180B can be configured to determine the motion posture of the electronic device 100. The barometric sensor 180C is configured to measure air pressure. The magnetic sensor 180D includes a Hall sensor. The acceleration sensor 180E can detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The distance sensor 180F is configured to measure distance. The proximity light sensor 180G can include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode can be an infrared light emitting diode. The ambient light sensor 180L is configured to sense ambient light brightness. The fingerprint sensor 180H is configured to acquire a fingerprint. The electronic device 100 can use the acquired fingerprint characteristics to implement fingerprint unlocking, access application locking, fingerprint photographing, fingerprint answering a call, etc. The temperature sensor 180J is configured to detect temperature. The bone conduction sensor 180M can acquire a vibration signal.

[0278] The touch sensor 180K, also referred to as a "touch device". The touch sensor 180K can be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 together form a touch screen, also referred to as a "touch screen". The touch sensor 180K is configured to detect a touch operation applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In another embodiment, the touch sensor 180K can also be disposed on the surface of the electronic device 100, which is different from the location of the display screen 194.

[0279] The keys 190 include a power on key, a volume key, and the like. The keys 190 can be mechanical keys. The keys 190 can also be touch keys. The electronic device 100 can receive key input and generate key signal input related to user settings and function control of the electronic device 100. The motor 191 can generate a vibration prompt. The indicator 192 can be an indicator light and can be used to indicate a charging state, a power change, and can also be used to indicate a message, a missed call, a notification, and the like. The SIM card interface 195 is used to connect a SIM card.

[0280] The above describes the method provided by the embodiments of the present application. In order to better implement the above scheme of the embodiments of the present application, the embodiments of the present application further provide a corresponding device or apparatus.

[0281] The embodiments of the present application can divide the electronic device 100 and the NFC card reading device 200 into functional modules according to the above method examples. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of the modules in the embodiments of the present application is illustrative and is only a logical functional division. Actual implementation can have another division manner.

[0282] The communication apparatus in the embodiments of the present application will be described below with reference to FIG. 13-FIG. 16.

[0283] In the case of using an integrated unit, referring to FIG. 13, FIG. 13 is a structural schematic diagram of a communication apparatus 1300 provided by the embodiments of the present application. The communication apparatus 1300 can be the electronic device 100 in the above embodiments. In some embodiments, the communication apparatus 1300 can be a chip / chip system, for example, an NFC chip. As shown in FIG. 13, the communication apparatus 1300 can include a transceiver unit 1310 and a processing unit 1320.

[0284] The transceiver unit 1310 shown in FIG. 13 can be used to perform the function steps related to NFC sending and NFC receiving and the like performed by the electronic device 100 in the above embodiments of the present application.

[0285] In some embodiments, the processing unit 1320 shown in FIG. 13 can be used to perform the function steps related to NFC protocol analysis and packaging, NFC service processing flow, and display and the like performed by the electronic device 100 in the above embodiments of the present application.

[0286] It should be understood that the communication apparatus 1300 in this design can correspond to perform the method steps performed by the electronic device 100 in the above embodiments. For brevity, the details are not described here.

[0287] In the case of using the integrated unit, refer to Fig. 14, which is a structural schematic diagram of a communication apparatus 1400 provided by an embodiment of the present application. The communication apparatus 1400 can be the NFC card reading device 200 in the above-mentioned embodiments. As shown in Fig. 14, the communication apparatus 1400 can include a transceiver unit 1410 and a processing unit 1420.

[0288] The transceiver unit 1410 shown in Fig. 14 can be used to perform the function steps related to NFC sending and NFC receiving, etc. performed by the NFC card reading device 200 in the above-mentioned embodiments of the present application.

[0289] In some embodiments, the processing unit 1420 shown in Fig. 14 can be used to perform the function steps related to NFC protocol analysis and packaging, NFC service processing flow, etc. performed by the NFC card reading device 200 in the above-mentioned embodiments of the present application.

[0290] It should be understood that the communication apparatus 1400 in this design can correspond to perform the method steps performed by the NFC card reading device 200 in the above-mentioned embodiments, and for the sake of brevity, will not be described here again.

[0291] The electronic device 100 and the NFC card reading device 200 of the embodiments of the present application are introduced above, and it should be understood that any product with the functions of the electronic device 100 shown in Fig. 13, and any product with the functions of the NFC card reading device 200 shown in Fig. 14, fall within the protection scope of the embodiments of the present application.

[0292] As a possible product form, the electronic device 100 described in the embodiments of the present application can be realized by a general bus architecture.

[0293] Refer to Fig. 15, which is a structural schematic diagram of a communication apparatus 1500 provided by an embodiment of the present application. The communication apparatus 1500 can be the electronic device 100, or a device therein. As shown in Fig. 15, the communication apparatus 1500 includes a processor 1501 and a transceiver 1502 connected with the processor 1501 internally. The processor 1501 is a general processor or a special-purpose processor, etc. For example, it can be a central processing unit and / or an NFC controller, etc. The transceiver 1502 can be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc. and is used to realize the transceiving function. The transceiver 1502 can include a receiver and a transmitter. The receiver can be referred to as a receiver or a receiving circuit, etc. and is used to realize the receiving function, for example, the NFC receiving function. The transmitter can be referred to as a transmitter or a transmitting circuit, etc. and is used to realize the transmitting function, for example, the NFC transmitting function.

[0294] In some embodiments, the communication apparatus 1500 can further include an antenna 1503 and / or a radio frequency unit (not shown in FIG. 15), for example, an NFC antenna, wherein the NFC antenna can be an antenna in the form of a coil. The antenna 1503 and / or the radio frequency unit can be located inside the communication apparatus 1500, or can be separate from the communication apparatus 1500, i.e., the antenna 1503 and / or the radio frequency unit can be a remote or distributed deployment.

[0295] In some embodiments, one or more memories 1504 can be included in the communication apparatus 1500, and instructions can be stored on the memories, which can be computer programs, the computer programs can be run on the communication apparatus 1500, so that the communication apparatus 1500 performs the method steps described in the above embodiments of the present application. Optionally, data can also be stored in the memory 1504. The communication apparatus 1500 and the memory 1504 can be separately arranged, or can be integrated together.

[0296] The processor 1501, the transceiver 1502, and the memory 1504 shown in FIG. 15 can be connected through a communication bus.

[0297] In one design, the communication apparatus 1500 can be configured to perform the functions of the electronic device 100 in the above embodiments: the processor 1501 can be configured to perform the function steps and / or other processes related to NFC protocol analysis and packaging, NFC service processing flow, display, etc. performed by the electronic device 100 in the above embodiments of the present application; and the transceiver 1502 can be configured to perform the function steps and / or other processes related to NFC transmission and NFC reception, etc. performed by the electronic device 100 in the above embodiments of the present application.

[0298] In any of the above designs, the processor 1501 can include a transceiver for implementing receiving and transmitting functions. For example, the transceiver can be a transceiver circuit, or an interface, or an interface circuit. The transceiver circuit, the interface, or the interface circuit for implementing receiving and transmitting functions can be separate, or can be integrated together. The above transceiver circuit, interface, or interface circuit can be used for reading and writing of code / data, or the above transceiver circuit, interface, or interface circuit can be used for transmission or transfer of signals.

[0299] In any of the above designs, the processor 1501 can store instructions, which can be computer programs, the computer programs running on the processor 1501 can make the communication apparatus 1500 perform the method steps performed by the electronic device 100 in the above embodiments of the present application. The computer programs can be fixed in the processor 1501, in which case the processor 1501 can be implemented by hardware.

[0300] In an implementation, the communication apparatus 1500 can include circuitry that can implement the functions of transmitting or receiving or communicating in the foregoing method embodiments. The processor and transceiver described in the present application can be implemented on an integrated circuit (IC), an analog IC, an RFIC, a mixed-signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0301] The scope of the communication apparatus described in the present application is not limited thereto, and the structure of the communication apparatus can not be limited by FIG. 15. The communication apparatus 1500 can be a standalone device or can be part of a larger device. For example, the communication apparatus 1500 can be:

[0302] (1) a standalone integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a set of one or more ICs, optionally including storage components for storing data, computer programs; (3) an ASIC, such as an NFC chip; (4) a module that can be embedded in other devices; (5) a receiver, terminal, smart terminal, cellular phone, wireless device, handset, mobile unit, car equipment, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0303] As a possible product form, the NFC card reading device 200 described in the embodiments of the present application can be implemented by a general bus architecture.

[0304] Referring to FIG. 16, FIG. 16 is a structural schematic diagram of a communication apparatus 1600 provided by an embodiment of the present application. The communication apparatus 1600 can be the NFC card reading device 200 or an apparatus therein. As shown in FIG. 16, the communication apparatus 1600 includes a processor 1601 and a transceiver 1602 connected with the processor 1601 internally. The processor 1601 is a general processor or a special purpose processor, for example, can be an NFC controller. The transceiver 1602 can be referred to as a transceiving unit, a transceiver, or a transceiving circuit, etc., and is configured to implement a transceiving function. The transceiver 1602 can include a receiver and a transmitter. The receiver can be referred to as a receiver or a receiving circuit, etc., and is configured to implement a receiving function. The transmitter can be referred to as a transmitter or a transmitting circuit, etc., and is configured to implement a transmitting function. Optionally, the communication apparatus 1600 can further include an antenna 1603 and / or a radio frequency unit (not shown in the figure). The antenna 1603 and / or the radio frequency unit can be located internally in the communication apparatus 1600, or can be separated from the communication apparatus 1600, i.e., the antenna 1603 and / or the radio frequency unit can be remotely deployed or distributedly deployed.

[0305] In some embodiments, one or more memories 1604 can be included in the communication apparatus 1600, and instructions can be stored in the memories 1604. The instructions can be computer programs, and the computer programs can be run on the communication apparatus 1600, so that the communication apparatus 1600 performs the method steps described in the above embodiments of the present application. Optionally, data can also be stored in the memories 1604. The communication apparatus 1600 and the memories 1604 can be separately arranged, or can be integrated together.

[0306] The processor 1601, the transceiver 1602, and the memories 1604 shown in FIG. 16 can be connected through a communication bus.

[0307] In one design, the communication apparatus 1600 can be configured to perform the functions of the NFC card reading device 200 in the above embodiments. The processor 1601 can be configured to perform the function steps related to NFC protocol analysis and packaging, NFC service processing flow, and / or other processes for the technologies described herein, which are performed by the NFC card reading device 200 in the above embodiments of the present application. The transceiver 1602 can be configured to perform the function steps related to NFC transmission and NFC reception, and / or other processes for the technologies described herein, which are performed by the NFC card reading device 200 in the above embodiments of the present application.

[0308] In any of the above designs, the processor 1601 can include a transceiver for implementing receiving and sending functions. For example, the transceiver can be a transceiver circuit, or an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and sending functions can be separate or integrated together. The above transceiver circuit, interface, or interface circuit can be used for reading and writing of code / data, or the above transceiver circuit, interface, or interface circuit can be used for transmission or transfer of signals.

[0309] In any of the above designs, the processor 1601 can store instructions, which can be a computer program, running on the processor 1601, which can cause the communication device 1600 to perform the method steps performed by the NFC card reading device 200 in the above method embodiments. The computer program can be fixed in the processor 1601, in which case the processor 1601 can be implemented by hardware.

[0310] The embodiments of the present application also provide a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the steps performed by the electronic device 100 in the above various method embodiments.

[0311] The embodiments of the present application also provide a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the steps performed by the NFC card reading device 200 in the above various method embodiments.

[0312] The embodiments of the present application also provide a computer program product, which includes a computer program, and when the computer program is run on a computer, the computer can implement the steps performed by the electronic device 100 in the above various method embodiments.

[0313] The embodiments of the present application also provide a computer program product, which includes a computer program, and when the computer program is run on a computer, the computer can implement the steps performed by the NFC card reading device 200 in the above various method embodiments.

[0314] The embodiments of the present application also provide a chip system, which includes a processing circuit and an interface circuit, the interface circuit is used to receive code instructions and transmit to the processing circuit, and the processing circuit is used to run the code instructions to make the chip system implement the steps performed by the electronic device 100 in any method embodiment of the present application. The chip system can be a single chip, or a chip module composed of multiple chips.

[0315] The embodiment of the present application further provides a chip system, which comprises a processing circuit interface circuit, the interface circuit is used for receiving code instructions and transmitting to the processing circuit, the processing circuit is used for running the code instructions so that the chip system realizes the steps executed by the NFC card reading device 200 in any method embodiment of the present application. Wherein, the chip system can be a single chip, or a chip module composed of multiple chips.

[0316] The above-described and above-embodied examples are only used to illustrate the technical solutions of the present application, but not to limit the same; although the present application is described in detail with reference to the foregoing examples, those skilled in the art should understand that the technical solutions recorded in the foregoing examples can be modified, or some technical features can be replaced by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A card management method characterized by comprising: The method is applied to a near field communication (NFC) card reading device, and comprises the following steps: sending a selection command to an electronic device, the selection command being used to select the electronic device to perform NFC interaction with the NFC card reading device; after receiving a first selection acknowledgement (SAK) command sent by the electronic device, sending a selection applet identification (AID) command in an application layer protocol to the electronic device, the first SAK command indicating that the application layer protocol is not supported, and the selection AID command being used to determine a first NFC analog card; completing a card swiping service of the first NFC analog card with the electronic device.

2. The method of claim 1, wherein, The selection AID command is used to determine the first NFC analog card from one or more NFC analog cards in the electronic device, and the one or more NFC analog cards support an access layer protocol and the application layer protocol.

3. The method of claim 1 or 2, wherein, The selection AID command is sent in a case where the NFC card reading device does not verify the first SAK command.

4. The method according to any one of claims 1 to 3, characterized in that, The first NFC analog card supports the access layer protocol and the application layer protocol, the electronic device further comprises a second NFC analog card, the second NFC analog card supports the access layer protocol and does not support the application layer protocol, and the first SAK command is obtained according to NFC parameters of the second NFC analog card; before the step of sending the selection command to the electronic device, the method further comprises the following steps: sending a request command in the access layer protocol to the electronic device; receiving a request response command in the access layer protocol sent by the electronic device, the request response command being obtained according to the NFC parameters of the second NFC analog card; sending an anti-collision command in the access layer protocol to the electronic device; receiving a unique identification (UID) of the second NFC analog card sent by the electronic device.

5. The method according to any one of claims 1 to 4, wherein The method further comprises the following steps: after receiving the first SAK command sent by the electronic device, sending a selection response request (RATS) command in the application layer protocol to the electronic device; receiving a selection response (ATS) command in the application layer protocol sent by the electronic device; The selection AID command is sent in a case where the NFC card reading device determines that the ATS command is correct in format, or the NFC card reading device does not verify the ATS command.

6. The method according to any one of claims 1 to 5, wherein, The access layer protocol is an ISO 14443-3 protocol or an IEC 14443-3 protocol, and the application layer protocol is an ISO 14443-4 protocol or an IEC 14443-4 protocol.

7. A card management method characterized by comprising: The method is applied to an electronic device, and comprises the following steps: receiving a first selection command sent by an NFC card reading device, the first selection command being used to select the electronic device to perform NFC interaction with the NFC card reading device; sending a first selection acknowledgement (SAK) command to the NFC card reading device, the first SAK command indicating that an application layer protocol is not supported; receiving a selection applet identification (AID) command in the application layer protocol sent by the NFC card reading device; determining a first NFC analog card according to the selection AID command, and completing a card swiping service of the first NFC analog card with the NFC card reading device.

8. The method of claim 7, wherein, The select AID command is used to determine the first NFC emulation card from one or more NFC emulation cards in the electronic device, and the one or more NFC emulation cards support an access layer protocol and the application layer protocol.

9. The method of claim 7 or 8, wherein, The select AID command is sent in a case where the NFC reading device does not verify the first SAK command.

10. The method according to any one of claims 7 to 9, characterized in that, The first NFC emulation card supports the access layer protocol and the application layer protocol, and the electronic device further comprises a second NFC emulation card, the second NFC emulation card supports the access layer protocol and does not support the application layer protocol, and the first SAK command is obtained according to NFC parameters of the second NFC emulation card. Before the receiving the first select command sent by the NFC reading device, the method further comprises: receiving a request command in the access layer protocol sent by the NFC reading device; sending a request response command in the access layer protocol to the NFC reading device, the request response command being obtained according to the NFC parameters of the second NFC emulation card; receiving an anti-collision command in the access layer protocol sent by the NFC reading device; sending a unique identification UID of the second NFC emulation card to the NFC reading device.

11. The method of claim 10, wherein, The select AID command is used to determine the first NFC emulation card from one or more NFC emulation cards in the electronic device, and the one or more NFC emulation cards support an access layer protocol and the application layer protocol, and NFC parameters of any one of the one or more NFC emulation cards are obtained according to corresponding configuration parameters and configuration masks by bitwise AND operation, the NFC parameters including a SAK command, a request response command and a UID used to implement a communication process of the access layer protocol, the corresponding configuration mask of the NFC parameters being zero, and the NFC parameters being zero.

12. The method according to any one of claims 7 to 11, wherein, The method further comprises: after the sending the first select confirmation SAK command to the NFC reading device, receiving a select response request RATS command in the application layer protocol sent by the NFC reading device; sending a select response ATS command in the application layer protocol to the NFC reading device, content of the ATS command not meeting preset requirements of the NFC reading device; The receiving the select AID command in the application layer protocol sent by the NFC reading device comprises: after the sending the select response ATS command in the application layer protocol to the NFC reading device, receiving the select AID command sent by the NFC reading device.

13. The method of claim 7 or 8, wherein, The method further comprises: when no RATS command in the application layer protocol is received within a preset time period after the sending the first select confirmation SAK command to the NFC reading device, after receiving a request command in the access layer protocol sent by the NFC reading device, sending a request response command in the access layer protocol to the NFC reading device; receiving a second select command sent by the NFC reader, the second select command being used to select the electronic device to interact with the NFC reader in NFC; sending a second SAK command to the NFC reader, the second SAK command indicating that the application layer protocol is supported; the receiving the select AID command in the application layer protocol sent by the NFC reader comprises: the receiving the select AID command sent by the NFC reader after the sending the second SAK command to the NFC reader.

14. The method according to any one of claims 7 to 13, wherein, The access layer protocol is ISO 14443-3 protocol or IEC 14443-3 protocol, and the application layer protocol is ISO 14443-4 protocol or IEC 14443-4 protocol.

15. A communications device, characterized by The computer program product comprises a transceiver, a processor and a memory, the memory is used to store a computer program, and the processor invokes the computer program to execute the method in any one of claims 1-6 or the method in any one of claims 7-14.

16. A computer storage medium, comprising, The computer storage medium stores a computer program, and the computer program is executed by the processor to implement the method in any one of claims 1-6 or the method in any one of claims 7-14.

17. A computer program product, characterised in that, The computer program product is used to implement the method in any one of claims 1-6 or the method in any one of claims 7-14 when the computer program product runs on the processor.

18. A chip system, characterized by The computer program product comprises a processing circuit and an interface circuit, the interface circuit is used to receive code instructions and transmit to the processing circuit, and the processing circuit is used to run the code instructions to execute the method in any one of claims 1-6 or the method in any one of claims 7-14.

Images