CN120636033A

CN120636033A - Card management method and related equipment

Info

Publication number: CN120636033A
Application number: CN202511113234.1A
Authority: CN
Inventors: 丁世杰; 江远; 戢国辉; 张秀平
Original assignee: Huaban Payment Shenzhen Co ltd
Current assignee: Huaban Payment Shenzhen Co ltd
Priority date: 2025-08-11
Filing date: 2025-08-11
Publication date: 2025-09-12

Abstract

This application discloses a card management method and related equipment. A terminal device can activate some or all of the multiple NFC simulated cards that have been activated. If the NFC simulated card that the user wants to use is in an activated state, the NFC simulated card can be used normally. If the NFC simulated card that the user wants to use is not in an activated state, the terminal device can automatically activate the NFC simulated card, and it can be used normally after activation. In this way, there is no need for the user to manually switch cards, which simplifies user operations, is convenient and quick, reduces the time spent on card swiping, improves the success rate of card swiping, and enhances the user experience.

Description

Card management method and related equipment

Technical Field

The application relates to the technical field of terminals, in particular to a card management method and related equipment.

Background

With the development of communication technology, many terminal devices (such as mobile phones, watches, etc.) can interact with card reading devices (such as subway/bus/park gates, home door locks, vehicles, etc.) through near field communication (NEAR FIELD communication) technology to implement Card Emulation (CE) functions, that is, the terminal devices can be used to simulate the interaction process between the entity card and the card reading device.

Taking the card reading device as a gate as an example, when a user wants to pass through the gate, the terminal device can be close to the gate to simulate card swiping operation, and the gate can be opened and pass through the gate after the card swiping is successful.

However, in the card swiping process, the problems of long card swiping time and low card swiping success rate generally occur, so that the use experience of a user is poor.

Disclosure of Invention

The embodiment of the application provides a card management method and related equipment, wherein terminal equipment can activate at least two NFC analog cards in a plurality of opened NFC analog cards. Therefore, when the NFC analog card is used, the time consumption for swiping the card can be reduced, the success rate of swiping the card is improved, and the use experience of a user is improved.

In a first aspect, an embodiment of the application provides a card management method applied to terminal equipment, wherein the method comprises the steps that the terminal equipment is close to first card reading equipment supporting a first near field communication NFC analog card, the terminal equipment receives a first identification sent by the first card reading equipment, the terminal equipment selects the first NFC analog card from a plurality of NFC analog cards in an activated state based on the first identification, the first NFC analog card is associated with the first identification, the terminal equipment executes a first task based on the first NFC analog card, and the terminal equipment sends an execution result of the first task to the first card reading equipment.

The first NFC analog card may be an NFC analog card (e.g., a traffic card, etc.) opened on the terminal device, the first card reading device may be a card reading device (e.g., a traffic card gate, etc.) supporting the first NFC analog card, the first identifier may be an AID of the first NFC analog card, and the first task may be a task that the first NFC analog card can execute (e.g., a task of payment, identity authentication, etc.).

It should be noted that, the "activated state" referred to in the present application may also be referred to as a first state.

By implementing the method provided in the first aspect, when a user uses the terminal device to execute a card swiping operation, the terminal device can directly select a first NFC analog card from a plurality of NFC analog cards in an activated state to conduct NFC transaction, the card does not need to be switched, card swiping time is reduced, and the card swiping success rate is improved.

In one possible implementation manner, the terminal device opens M NFC emulated cards, and part or all of the M NFC emulated cards are in an activated state, where the NFC emulated cards in the activated state include a first NFC emulated card and a second NFC emulated card.

Wherein the first NFC emulated card and the second NFC emulated card are two different NFC emulated cards.

That is, in the present application, at least 2 NFC analog cards among the plurality of NFC analog cards opened on the terminal device may be in an activated state and available at the same time, so that when the user performs the card swiping operation, the terminal device may reduce the number of times of switching the cards to a certain extent, and improve the card swiping success rate. Preferably, the terminal device can activate all the plurality of opened NFC analog cards, so that when a user performs a card swiping operation, the terminal device does not need to switch cards in real time, all the cards are available at the same time, and the user can directly perform NFC transaction when swiping the card, thereby improving the card swiping success rate to the greatest extent.

In one possible implementation manner, the method further comprises the steps that the terminal equipment approaches to second card reading equipment supporting a second NFC analog card, the terminal equipment receives a second identification sent by the second card reading equipment, the terminal equipment selects the second NFC analog card from a plurality of NFC analog cards in an activated state based on the second identification, the second NFC analog card is associated with the second identification, the terminal equipment executes a second task based on the second NFC analog card, the terminal equipment sends an execution result of the second task to the second card reading equipment, and the second identification and the first identification are different.

The second NFC emulated card may be an NFC emulated card (e.g. a car key, etc.) that is different from the first NFC emulated card and is opened on the terminal device, the second card reading device may be a card reading device (e.g. a car, etc.) that supports the second NFC emulated card, the second identifier may be an AID of the second NFC emulated card, and the second task may be a task that the second NFC emulated card can execute (e.g. a task of opening a car door, etc.).

Therefore, when a user executes a card swiping operation, the terminal equipment can directly select the first NFC analog card from the plurality of NFC analog cards in the activated state to conduct NFC transaction, the card does not need to be switched, the card swiping time is reduced, and the card swiping success rate is improved.

In one possible implementation, the first NFC emulated card is still in an active state after the terminal device selects the second NFC emulated card from the plurality of NFC emulated cards in an active state based on the second identification.

That is, when the terminal device selects to use the second NFC emulated card to perform NFC transaction with the second card reading device, the first NFC emulated card may still be in an activated state, so that when the first NFC emulated card needs to be used, the activating operation does not need to be executed again, time for swiping the card is reduced, and the success rate of swiping the card is improved.

In one possible implementation, before the terminal device sends the execution result of the second task to the second card reading device, the method further comprises the terminal device sending the first NFC protocol parameter of the first value to the second card reading device, and before the terminal device sending the execution result of the first task to the first card reading device, the method further comprises the terminal device sending the first NFC protocol parameter of the first value to the first card reading device.

The first NFC protocol parameter may be a non-contact parameter in the following embodiment, and the first value may be a system-level non-contact parameter in the following embodiment.

In the embodiment of the application, after the terminal equipment approaches the first card reading equipment and the second card reading equipment, the system-level non-contact parameters and the values thereof can be sent to the first card reading equipment and the second card reading equipment so as to carry out NFC interaction rate negotiation and the like with the first card reading equipment and the second card reading equipment, so that the NFC transaction task can be successfully completed in the follow-up.

In one possible implementation, the first NFC emulated card and the second NFC emulated card are both activated by the terminal device based on the first value of the first NFC protocol parameter.

That is, the terminal devices activate the opened NFC emulated card based on the value of the system-level non-contact parameter. In this way, the terminal device can use the non-contact parameter value of the system level to conduct NFC transaction with the card reading device when different NFC analog cards are used.

In one possible implementation manner, before the terminal device approaches the first card reading device supporting the first Near Field Communication (NFC) analog card, the method further comprises the steps that the terminal device obtains a first NFC protocol parameter with a second value, the terminal device adjusts the first NFC protocol parameter with the second value to the first NFC protocol parameter with the first value, before the terminal device approaches the second card reading device supporting the second NFC analog card, the method further comprises the steps that the terminal device obtains a first NFC protocol parameter with a third value, the terminal device adjusts the first NFC protocol parameter with the third value to the first NFC protocol parameter with the first value, the second value is related to the first NFC analog card, the third value is related to the second NFC analog card, and the second value and the third value are different.

The second value may be a value of an original non-contact parameter corresponding to the first NFC analog card, and the third value may be a value of an original non-contact parameter of the second NFC analog card.

That is, after activating the NFC analog card, the terminal device may first obtain the value of the original non-contact parameter corresponding to the NFC analog card, then adjust the value of the original non-contact parameter to the value of the system-level non-contact parameter, and then activate the NFC analog card based on the value of the system-level non-contact parameter.

In one possible implementation, the first NFC protocol parameter, the first value, the second value, and the third value are pre-stored on the terminal device or acquired by the terminal device at the server.

That is, the system-level non-contact parameter and the value thereof, and the original non-contact parameter of the NFC analog card and the value thereof may be pre-stored on the terminal device or stored on the server, and the terminal device may acquire the value from the server when needed.

In a possible implementation manner, the method further comprises the step that the terminal equipment updates the first NFC protocol parameter with the first value to the first NFC protocol parameter with the fourth value, before the terminal equipment sends the execution result of the second task to the second card reading equipment, the method further comprises the step that the terminal equipment sends the first NFC protocol parameter with the fourth value to the second card reading equipment, and before the terminal equipment sends the execution result of the first task to the first card reading equipment, the method further comprises the step that the terminal equipment sends the first NFC protocol parameter with the fourth value to the first card reading equipment.

That is, in practical application, the value of the system-level non-contact parameter may be updated according to the actual requirement, and after updating, the terminal device may use the updated value of the system-level non-contact parameter to perform NFC communication with the card reader.

In one possible implementation, the terminal device displays a first user interface, where the first user interface includes a plurality of NFC emulated cards in an activated state.

Wherein, the first user interface may be a user interface for displaying a currently activated card.

In this way, after the terminal device activates the plurality of NFC emulated cards, the plurality of NFC emulated cards in an activated state may also be displayed on the user interface for the user to view.

In one possible implementation manner, the terminal device comprises a security chip, the terminal device adjusts the second value first NFC protocol parameter to the first value first NFC protocol parameter, the terminal device specifically comprises the security chip adjusts the second value first NFC protocol parameter to the first value first NFC protocol parameter, the terminal device adjusts the third value first NFC protocol parameter to the first value first NFC protocol parameter, and the terminal device specifically comprises the security chip adjusts the third value first NFC protocol parameter to the first value first NFC protocol parameter.

That is, the terminal device may perform an operation of "adjusting the value of the original contactless parameter of the NFC emulated card to the value of the system-level contactless parameter" through the secure chip.

In one possible implementation, the terminal device further comprises a first application, before the secure chip adjusts the second valued first NFC protocol parameter to the first valued first NFC protocol parameter, the method further comprises the first application sending a first message to the secure chip, the first message being used to instruct the secure chip to adjust the second valued first NFC protocol parameter to the first valued first NFC protocol parameter, and before the secure chip adjusts the third valued first NFC protocol parameter to the first valued first NFC protocol parameter, the method further comprises the first application sending a second message to the secure chip, the second message being used to instruct the secure chip to adjust the third valued first NFC protocol parameter to the first valued first NFC protocol parameter.

Wherein the first application may be a service management application (e.g. wallet application).

That is, the terminal device may instruct the security chip to perform an operation of "adjusting the value of the original contactless parameter of the NFC emulated card to the value of the system-level contactless parameter" through the first application.

In a possible implementation manner, the terminal device further comprises an NFC chip and an NFC service module, the NFC service module sends a first NFC protocol parameter with a first value to the NFC chip, the NFC chip stores the first NFC protocol parameter with the first value, the terminal device sends the first NFC protocol parameter with the first value to the second card reading device, the terminal device specifically comprises the NFC chip sends the first NFC protocol parameter with the first value to the second card reading device, and the terminal device sends the first NFC protocol parameter with the first value to the first card reading device, and the terminal device specifically comprises the NFC chip sends the first NFC protocol parameter with the first value to the first card reading device.

That is, after activating the NCF analog card, the NFC service module may send the system-level non-contact parameter and its value used when the secure chip activates the NFC analog card to the NFC information, so that the subsequent NFC chip may use the system-level non-contact parameter and its value to perform NFC communication with the card reader.

In one possible implementation, the first NFC protocol parameters include one or more of a unique identifier UID, a request reply SAK for a SELECT command, a request reply ATQA for a REQA command, a history byte ATS History Bytes for a SELECT reply, a frame latency and startup frame guard time FWI, an SFGI, a supported card identifier field CID Support, a maximum Data transfer Rate Max Data Rate.

In one possible implementation, the terminal device is in a powered off state.

That is, when the terminal device is in the off state and the user performs the card swiping operation, the plurality of NFC analog cards in the active state are still available, so that the use experience of the user is improved.

In a second aspect, the embodiment of the application provides a card management method, which is applied to terminal equipment, and comprises the steps that the terminal equipment is close to first card reading equipment supporting a first NFC analog card, the terminal equipment sends first NFC protocol parameters with first values to the first card reading equipment, the terminal equipment is close to second card reading equipment supporting a second NFC analog card, the terminal equipment sends the first NFC protocol parameters with the first values to the second card reading equipment, and the first NFC analog card is different from the second NFC analog card.

That is, when the terminal device uses different NFC analog cards to perform NFC interaction with the card reader, the values of the NFC protocol parameters used by the terminal device are the same.

In one possible implementation manner, the method further comprises the steps that the terminal equipment receives a first identifier sent by the first card reading equipment, the terminal equipment selects a first NFC analog card from a plurality of NFC analog cards in an activated state based on the first identifier, the first NFC analog card is associated with the first identifier, the terminal equipment executes a first task based on the first NFC analog card, the terminal equipment sends an execution result of the first task to the first card reading equipment, the terminal equipment receives a second identifier sent by the second card reading equipment, the terminal equipment selects a second NFC analog card from the plurality of NFC analog cards in the activated state based on the second identifier, the second NFC analog card is associated with the second identifier, the terminal equipment executes a second task based on the second NFC analog card, and the terminal equipment sends an execution result of the second task to the second card reading equipment, wherein the second identifier and the first identifier are different.

Therefore, when a user uses the terminal equipment to execute the card swiping operation, the terminal equipment can directly select one NFC analog card from a plurality of NFC analog cards in an activated state to conduct NFC transaction, the card does not need to be switched, the card swiping time is reduced, and the card swiping success rate is improved.

In a third aspect, an embodiment of the present application provides a card management method, applied to a terminal device, where the method includes that the terminal device displays a first user interface of a first application, where the first user interface includes M NFC analog cards opened by the terminal device through the first application, M is a positive integer greater than 1, and at least 2 NFC analog cards in an activated state are included in the M NFC analog cards.

That is, after the terminal device activates the plurality of NFC emulated cards, the plurality of NFC emulated cards in an activated state may also be displayed on the user interface for the user to view.

In one possible implementation, at least 2 NFC emulated cards in an activated state include a first NFC emulated card, and before the first NFC emulated card is in an activated state, the method further includes enabling the first NFC emulated card by the terminal device, detecting an operation of confirming activation of the first NFC emulated card by a user by the terminal device, and activating the first NFC emulated card by the terminal device in response to the operation.

In this way, the terminal device may support manual activation of the opened NFC emulated card by the user.

In one possible implementation manner, at least 2 NFC emulated cards in an activated state include a second NFC emulated card, and before the second NFC emulated card is in an activated state, the method further includes enabling the second NFC emulated card by the terminal device, and automatically activating the second NFC emulated card.

Therefore, the terminal equipment can automatically activate the opened NFC analog card without manual operation of a user, and is convenient and quick.

In one possible implementation manner, the second NFC emulated card is an NFC emulated card according to a preset rule, and the preset rule includes one or more of a priority of a service corresponding to the second NFC emulated card is higher than a first threshold, the second NFC emulated card is one NFC emulated card of the first X NFC emulated cards that have been opened in the terminal device, and X is a positive integer less than or equal to the second threshold.

That is, the terminal device may only automatically activate the NFC emulated card satisfying the preset rule, for example, a service priority rule, where the NFC emulated card with the service priority in the first M (where M is a positive integer greater than 1) may be automatically activated, that is, the NFC emulated card with the service priority higher than the first threshold may be automatically activated, and for example, a card opening order rule, that is, the first X NFC emulated cards that have been opened may be automatically activated.

In a fourth aspect, an embodiment of the present application provides a chip system, including a processor coupled to a memory for storing a program or instructions which, when executed by the processor, cause the chip system to perform the method as described in any one of the possible implementation manners of the first aspect or the second aspect or the third aspect.

In a fifth aspect, an embodiment of the present application provides an electronic device comprising one or more processors and one or more memories, wherein the one or more memories are coupled to the one or more processors, the one or more memories are configured to store computer program code, the computer program code comprising computer instructions that, when executed by the one or more processors, cause the electronic device to perform the method described in any of the possible implementations of the first aspect or the second aspect or the third aspect.

In a sixth aspect, an embodiment of the present application provides a computer storage medium storing a computer program comprising program instructions which, when run on an electronic device, cause the electronic device to perform the method as described in any one of the possible implementation manners of the first aspect or the second aspect or the third aspect.

In a seventh aspect, embodiments of the present application provide a computer program product which, when run on a computer, causes the computer to perform the method as described in any one of the possible implementations of the first or second or third aspects.

Drawings

FIG. 1 is a schematic diagram of a user interface for displaying an open NFC analog card according to an embodiment of the present application;

Fig. 2 is a schematic diagram of a scenario in which a terminal device and a card reader (such as a vehicle, a subway/bus gate, etc.) perform NFC communication according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a communication system according to an embodiment of the present application;

FIG. 4 is a schematic flow chart of a card management method according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a possible cooperation manner between each module in the terminal device and the card reading device when implementing the card management method shown in FIG. 4 according to an embodiment of the present application;

FIG. 6 is a flowchart of another card management method according to an embodiment of the present application;

Fig. 7 is a schematic diagram of one possible cooperation manner between each module inside the terminal device 100 and one possible cooperation manner between each module inside the terminal device 100, the card reader 300, and the modules inside the server 200 when implementing the card management method shown in fig. 6 according to the embodiment of the present application;

Fig. 8 is a schematic diagram of a change of non-contact parameters and activation states of an NFC emulated card before and after implementing the card management method shown in fig. 6 according to an embodiment of the present application;

fig. 9 is a basic logic diagram of implementation of the card management method shown in fig. 6 when the terminal device provided in the embodiment of the present application is in an on state or an off state;

Fig. 10 is a schematic diagram of a user interface for displaying an activated NFC emulated card before and after implementing the card management method shown in fig. 6 according to an embodiment of the present application;

FIGS. 11A-11V are a set of user interface diagrams for a card management method according to an embodiment of the present application;

FIG. 12 is a flowchart of another card managing method according to an embodiment of the present application;

Fig. 13 is a schematic software structure of a terminal device according to an embodiment of the present application;

Fig. 14 is a schematic structural diagram of a server according to an embodiment of the present application;

fig. 15 is a schematic hardware structure of a terminal device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the embodiment of the present application, unless otherwise indicated, "/" means or, for example, a/B may represent a or B, and "and/or" in the text is merely an association relationship describing an association object, which means that three relationships may exist, for example, a and/or B, and that three cases of a alone, a and B together, and B alone exist, and further, in the description of the embodiment of the present application, "a plurality" means two or more.

It should be understood that the terms first, second, and the like in the description and in the claims and drawings are used for distinguishing between different objects and not necessarily for describing a particular sequential or chronological order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.

Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the described embodiments of the application may be combined with other embodiments.

The term "User Interface (UI)" in the following embodiments of the present application is a media interface for interaction and information exchange between an application program or an operating system and a user, which enables conversion between an internal form of information and a form acceptable to the user. The user interface is a source code written in a specific computer language such as java, extensible markup language (extensible markup language, XML) and the like, and the interface source code is analyzed and rendered on the electronic equipment to finally be presented as content which can be identified by a user. A commonly used presentation form of a user interface is a graphical user interface (graphic user interface, GUI), which refers to a graphically displayed user interface that is related to computer operations. It may be a visual interface element of text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc., displayed in a display of the electronic device.

First, the working principle of NFC technology is introduced.

In general, two parties communicating using NFC technology may include a proximity smart card (proximity integrated circuit card, PICC), and a proximity coupling device (proximity coupling device, PCD), also referred to as a Reader device.

The PCD may enable proximity contactless communication with the PICC. PCD and PICC may allow near field communication at a particular data rate (e.g., 106, 212, 424, or 848 kilobits per second (kilobit per second, kbps)) and a particular frequency (e.g., 13.56 MHz). Communication between the PCD and the PICC may occur within a close range, such as within a range of less than or equal to 4 centimeters, between the PCD and the PICC.

The PCD may generate a high frequency alternating current to generate a radio frequency field at a specified frequency (e.g., 13.56 MHz) and transmit data to the PICC via the radio frequency field. After approaching the PCD, the PICC can sense the radio frequency field emitted by the PCD. After entering the radio frequency field emitted by the PCD, the PICC can obtain energy from the radio frequency field of the PCD in an electromagnetic induction mode, and generate electric power by the obtained energy so as to drive a circuit inside the PICC, analyze data sent by the PCD through the radio frequency field, and further realize data transmission from the PCD to the PICC. The PICC can also send data to the PCD in a mode of load modulation of the radio frequency field, so that the data transmission from the PICC to the PCD is realized.

The PICC may be an NFC tag card of an entity.

In the embodiment of the application, the terminal equipment (such as mobile phone, watch, bracelet and other electronic equipment) can simulate the terminal equipment into the PICC conforming to the NFC related standard by utilizing the data of the NFC analog card so as to realize the PICC function and communicate with the PCD based on the NFC technology.

In the embodiment of the application, the terminal equipment can open one or more NFC analog cards in a certain application (such as wallet application and the like) based on user operation, and the one or more NFC analog cards can be stored in the terminal equipment in the form of a digital card for simulating the functions of a traditional entity card, and can be widely applied to scenes such as access control, payment, ticketing, identity verification and the like.

The NFC analog card (may also be referred to as a key card or a digital card) may include various types of cards, such as a bank card, a traffic card, a door lock key, a membership card, a car key, a campus card (may also be referred to as an industrial card), and the like.

In the embodiment of the application, the terminal device can support the user to simultaneously open a plurality of NFC analog cards, such as a car key 1, a traffic card 1, a door lock key 1 and a campus card 1 shown in fig. 1.

For a part of NFC analog cards, the terminal equipment can support a user to open a plurality of NFC analog cards at the same time. For example, taking a car key as an example, if a user has a plurality of cars at the same time, the user can turn on a plurality of car keys at the same time, and for example, taking a traffic card as an example, if the user frequently works or lives in city 1 and city 2, the user can turn on a traffic card 1 corresponding to city 1 and a traffic card 2 corresponding to city 2 at the same time.

In practical application, after the terminal device opens the NFC analog card, the NFC analog card needs to be activated, and after activation, the NFC analog card can be normally used. Specifically, the user can complete corresponding tasks (such as payment, unlocking and other tasks) through the NFC technology only by approaching the terminal device to the card reading device, and the user does not need to carry the entity card.

The card reading device can be various devices capable of supporting execution of corresponding tasks through NFC functions, such as subway/bus/park gate, household door locks, vehicles and the like.

The position close to the card reading device can be a position close to the card reading device, which can identify the card, for example, a door handle/central control on a vehicle, a card attaching position of a subway/bus/park gate, a card attaching position of a household door lock, and the like.

Currently, under the condition that a plurality of NFC analog cards are simultaneously opened, the terminal equipment only can support to activate one NFC analog card. In some embodiments, the terminal device may support a default card mode, that is, the terminal device may support a user to designate one of the NFC analog cards that can be in an activated state, for example, referring to fig. 2, it may be seen that the car key is in an activated state and can be used normally, and the traffic card is in an inactivated state and cannot be used normally. Therefore, when the terminal equipment is close to the vehicle, the vehicle can normally complete the task of opening the door, and when the terminal equipment is close to the subway/bus gate, the gate cannot normally complete the task of opening the gate. In this case, the user is required to manually switch the card, trigger the terminal device to deactivate the car key, and activate the traffic card. And when the user wants to open the door next time, the user still needs to manually switch the card, trigger the terminal device to deactivate the traffic card and activate the car key. Therefore, the user needs to repeatedly and manually switch the card, the operation is complex, the inconvenience is caused, and poor use experience can be brought to the user.

Based on the above-mentioned problems, the embodiments of the present application provide a card management method, where a terminal device may activate some or all of a plurality of NFC analog cards that have been turned on, if an NFC analog card that a user wants to use is in an activated state, the NFC analog card may be directly used normally, and if the NFC analog card that the user wants to use is not in an activated state, the terminal device may automatically activate the NFC analog card, and after activation, may be used normally. Therefore, the user does not need to manually switch the card, the operation of the user is simplified, the card swiping time is reduced, the card swiping success rate is improved, and the use experience of the user is improved.

It should be noted that, in the embodiment of the present application, the card management method may be implemented by adjusting the value of the NFC protocol parameter, where the non-contact parameter included in the NFC protocol parameter is taken as an example for explanation, and the present application should not be limited to this embodiment. In some other embodiments of the present application, some other parameters other than the contact parameters included in the NFC protocol parameters may also be adjusted, which the present application is not limited to.

It should be noted that the non-contact parameter mentioned in the present application may also be referred to as a first NFC protocol parameter.

For ease of understanding, the "non-contact parameters" referred to in the present application will be described first.

The non-contact parameter (may also be referred to as a non-connection parameter) is an NFC protocol parameter used when the NFC analog card on the terminal device interacts with the card reading device (such as a gate, a door lock, etc.) through NFC in a non-contact manner, and is generally used for parameter negotiation such as type identification of the NFC analog card and NFC interaction rate.

The value of the non-contact parameter is generally defined by the Applet issuer of the NFC emulated card, and because of the lack of a unified specification, the value of the non-contact parameter is different for each NFC emulated card, and the non-contact parameter and the value thereof are issued to the terminal device when the Applet is installed, and the non-contact parameter and the value thereof are issued to the NFC chip when the Applet is activated, so that the NFC chip can apply the parameter. Because the NFC chip can only apply a group of non-contact parameters at the same time, the NFC chip cannot be compatible with the same group of non-contact parameters with different values at the same time, and therefore, the problem of non-contact parameter conflict can be generated when applets of different NFC analog cards are activated.

Based on the above problems, in the method provided by the application, the values of the original non-contact parameters of different NFC analog cards can be all adjusted to be uniform values of non-contact parameters, and the uniform values of non-contact parameters can also be called as system-level values of non-contact parameters. In this way, the problem of non-contact parameter conflicts can be eliminated.

The method mainly relates to the adjustment of the values of some non-contact parameters in the ISO 14443-3 protocol and the ISO 14443-4 protocol in the NFC protocol.

The ISO 14443-3 protocol is mainly used for defining the related contents of initialization and anti-collision, and the ISO 14443-4 protocol is mainly used for defining the related contents of data transmission.

Among other non-contact parameters mainly involved in the ISO 14443-3 protocol may include UID (unique identifier), SAK (select acknowledge), ATQA (answer to request, type a). The UID is used for indicating a unique identifier of the NFC analog card, the SAK is used for indicating a request response of the SELECT command, and the ATQA is used for indicating a request response of the REQA command.

Among other things, non-contact parameters mainly involved in the ISO 14443-4 protocol may include ATS History Bytes、FWI,SFGI（frame waiting time and start-up frame guard time）、CID Support（support of the card identifier field）、Max Data Rate. where ATS History Bytes is used to indicate a history byte of a select to select (ATS), FWI, SFGI is used to indicate frame latency and start frame guard time, CID Support is used to indicate supported card identifier fields, max Data Rate is used to indicate maximum Data transfer Rate.

Each of the non-contact parameters corresponds to a value thereof, which may include protocol data and a mandatory mask (mandatory mask). The values may be considered different as long as at least one of the protocol data and the forced mask is different.

For example, referring to table 1 and table 2, table 1 shows an example of an original non-contact parameter of a certain traffic card and a value thereof, and table 2 shows an example of an original non-contact parameter of a certain car key and a value thereof, it can be seen that, for the traffic card and the car key, the values of most non-contact parameters are different, and only the value of SAK is the same.

It is easy to understand that the values of the non-contact parameters of the two NFC emulated cards can be considered to be different as long as the value of one non-contact parameter in the set of non-contact parameters of the two NFC emulated cards is different.

Illustratively, referring to table 3, table 3 shows a sample of system level non-contact parameters and their values.

In the application, the system-level non-contact parameters and the values thereof are preset and can be pre-stored in the server, and the terminal equipment can be acquired from the server when needed or can be pre-stored on the terminal equipment. The system-level non-contact parameters and the values thereof can be a group of common non-contact parameters and the values thereof which are determined after the non-contact parameters and the values thereof of a plurality of NFC analog cards are verified, and the plurality of NFC analog cards can realize NFC transaction with card reading equipment by using the group of non-contact parameters and the values thereof.

TABLE 1

TABLE 2

TABLE 3 Table 3

The protocol data and the forced mask corresponding to each of the non-contact parameters shown in table 1, table 2, and table 3 are only exemplary, and should not be construed as limiting the present application.

The following describes a communication system provided by an embodiment of the present application.

Fig. 3 illustrates a communication system provided by an embodiment of the present application.

Referring to fig. 3, the communication system may include a terminal device 100, a server 200, and a card reading device 300.

The terminal device 100 may be various types of intelligent electronic devices, such as a wearable device like a mobile phone, a watch/bracelet, etc. The embodiment of the present application does not limit the type of the terminal device 100.

In an embodiment of the present application, the terminal device 100 may include a service management application, an NFC service (NFC SERVICE) module, an NFC chip, and a security chip.

The service management application is an application (e.g. wallet application) installed on the terminal device 100, and can be used as a service initiator to accept a card opening (i.e. opening an NFC analog card) request of a user, write applets of one or more NFC analog cards and card data thereof into the security chip, send system-level non-contact parameters and values thereof to the security chip during card opening, trigger the security chip to activate the applets of one or more opened NFC analog cards, and the like.

The Applet may be an application program for implementing the service processing logic of the NFC emulated card, as a carrier of the NFC emulated card in the security chip, may be used for service key storage, and after being activated, may support the terminal device 100 to communicate with the card reading device 300 via NFC. The Applet may be stored and run in the secure chip. Each NFC emulated card may correspond to an Applet, each Applet may correspond to a unique application identifier (application identifier, AID), and an activated Applet may be selected by specifying the AID for subsequent NFC transactions with the card reader device 300.

In the embodiment of the application, activating the Applet of the NFC analog card can be represented by activating the NFC analog card.

The NFC service module is a system service module in the terminal device 100, and may be used to receive an instruction issued by the service management application to trigger the security chip to activate an Applet of the opened NFC analog card, and may also be used to receive an instruction issued by the service management application to trigger the security chip to adjust the stored non-contact parameter and its value, and may also be used to send the non-contact parameter and its value to the NFC chip so that the NFC chip may store the non-contact parameter and its value, and so on.

The NFC chip, which is an NFC module in the terminal device 100, is a front end (contactless front, CLF) module for contactless communication, and may be used to communicate with the card reader 300 based on the NFC standard protocol, and may also be used to save the contactless parameters of the activated NFC analog card and its value, and so on.

In general, in the process of NFC communication between the terminal device 100 and the card reader device 300, the NFC chip may forward the NFC command received from the card reader device 300 to an Applet in the security chip to trigger the Applet to process the NFC command and generate response data, the security chip may transmit the response data to the NFC chip, and the NFC chip may transmit the response data to the card reader device 300.

The secure chip is a Secure Element (SE) in the terminal device 100, and is used as a non-contact registration service (contactless REGISTRY SERVICE, CRS) module and a secure storage module, and can be used for storing applets of NFC analog cards of various services, managing activation states of the applets, providing running environments of the applets of the NFC analog cards and storing and processing service data of the NFC analog cards, and the like.

It is easy to understand that the Applet can support the terminal device 100 to perform NFC transaction with the card reader device 300 in case that the security chip activates the Applet of a certain NFC analog card, and the Applet cannot support the terminal device 100 to perform NFC transaction with the card reader device 300 in case that the security chip does not activate the Applet of a certain NFC analog card.

It should be noted that, in order to enable application of the system-level non-contact parameter, the security chip is required to support modification of more parameters, so in the embodiment of the present application, the security chip may provide a new instruction through firmware upgrade to uniformly modify the values of the original non-contact parameters as shown in the foregoing table 1 and table 2 into the values of the system-level non-contact parameters as shown in the foregoing table 3.

The server 200 may be a conventional server or a cloud server, which is not limited in this embodiment of the present application.

In an embodiment of the present application, the server 200 may include a Trusted Service Management (TSM) module, and may also include other service modules.

The trusted service management module can be used for providing cloud side management service of the security chip, holds a security chip key and can realize secure communication with the security chip based on a security channel.

In the embodiment of the present application, the server 200 may manage the security chip of the terminal device 100 through a trusted service management module, implement a parameter issuing capability, and the like.

For example, when the terminal device 100 needs to open the NFC emulated card, the server 200 may send the Applet of the NFC emulated card, the original non-contact parameter of the NFC emulated card and its value to the terminal device 100, so that the security chip of the terminal device 100 may install the Applet of the NFC emulated card and store the original non-contact parameter of the NFC emulated card and its value.

For another example, before the terminal device 100 activates the NFC emulated card, the server 200 may send the system-level contactless parameter and its value to the terminal device 100, so that the security chip of the terminal device 100 may adjust the value of the original contactless parameter of the NFC emulated card to the value of the system-level contactless parameter, and so on.

The card reading device 300 may be various devices capable of supporting the execution of corresponding tasks through NFC functions, such as subway/bus/park gate, home door lock, vehicle, etc.

In the embodiment of the present application, the card reading device 300 may communicate with the terminal device 100 through NFC, so that the card reading device 300 may perform a corresponding task.

Illustratively, taking the example that the card reading device 300 is a subway/bus gate, in the case that the terminal device 100 turns on and activates a traffic card and approaches the card reading device 300, the card reading device 300 may open a gate for a user to pass.

Illustratively, taking the card reader device 300 as a campus gate, in the case where the terminal device 100 opens and activates a campus card and is close to the card reader device 300, the card reader device 300 may open the gate for the user to pass.

Illustratively, taking the card reading device 300 as a home door lock as an example, in a case where the terminal device 100 opens and activates a door lock key and approaches the card reading device 300, the card reading device 300 may unlock for the user to open the home door.

Illustratively, taking the card reader device 300 as an example of a vehicle, in the case where the terminal device 100 turns on and activates a vehicle key and approaches the card reader device 300, the card reader device 300 may unlock for the user to open a door.

Based on the communication system shown in fig. 3, the card management method provided by the present application will be described in detail in the following through the first embodiment and the second embodiment, respectively.

Embodiment 1,

In the first embodiment, the terminal device may support an intelligent flash card mode, in which the terminal device may only support to activate one of the opened NFC analog cards, when the terminal device opens the NFC function and is in a power-on state, the terminal device is close to the card reading device, and the terminal device may implement intelligent recognition and context awareness, and automatically match the NFC analog card corresponding to the card reading device, if the NFC analog card currently in an active state is not the NFC analog card corresponding to the card reading device, the terminal device may cancel to activate the NFC analog card first, and then deactivate the NFC analog card corresponding to the card reading device, without requiring the user to manually select the card, thereby simplifying user operation and improving user experience.

Fig. 4 illustrates a specific flow of a card management method according to an embodiment of the present application.

As shown in fig. 4, the method can be applied to a communication system including a terminal device 100, a card reading device 300. Taking the scenario that the terminal device 100 is a mobile phone and the card reader 300 is a gate, and the user opens a traffic card and a car key as an example, the following detailed steps of the method are described:

S401, the terminal device 100 opens the traffic card and the car key based on the user operation, wherein the Applet of the car key is activated and the Applet of the traffic card is not activated.

The user operation may be an operation of opening a traffic card and a car key by a user.

In some embodiments, in the case of opening multiple NFC analog cards at the same time, because different NFC analog cards have different issuers and corresponding original non-contact parameters are inconsistent, the terminal device 100 can only apply the non-contact parameters of one NFC analog card at the same time, and the non-contact parameters conflict when the NFC analog cards with different non-contact parameters are activated, so that the terminal device 100 can only activate one NFC analog card, and in particular, the terminal device 100 can determine which NFC analog card Applet is activated based on a preset rule. The preset rule is not specifically limited in the embodiment of the present application.

For example, the preset rule may be a preset service priority rule, where the terminal device 100 may preferentially activate the Applet of the NFC analog card with a higher service priority, for example, the service corresponding to the vehicle key is a vehicle service, the service corresponding to the traffic card is a traffic service, and if the priority of the vehicle service is higher than that of the traffic service, the terminal device 100 may preferentially activate the Applet of the vehicle key. It is easy to understand that in the case where the Applet of the car key is in an activated state, the Applet of the traffic card is in an inactivated state.

S402, the terminal device 100 approaches to the card reading device 300, wherein the card reading device 300 is a traffic card gate.

In the embodiment of the present application, the terminal device 100 is close to the card reader device 300, which may specifically refer to that the terminal device 100 enters a radio frequency field of the card reader device 300 (for example, the terminal device 100 touches the card reader device 300), that is, a distance between the terminal device 100 and a card reading area of the card reader device 300 is within a communication distance range of NFC.

S403, the card reader 300 transmits the AID of the traffic card to the terminal 100.

Specifically, since the card reader device 300 is a traffic card gate, in the case where the terminal device 100 is detected to be close to the card reader device 300, the card reader device 300 may send the AID of the traffic card to the terminal device 100 to apply for the terminal device 100 for the NFC transaction with the Applet of the traffic card.

S404, the terminal device 100 determines that the Applet of the traffic card is not activated based on the AID of the traffic card.

Specifically, since the Applet of one NFC emulated card corresponds to one AID and the Applet currently activated is the Applet of the car key, the terminal device 100 can determine that the Applet of the traffic card is not activated based on the AID after receiving the AID of the traffic card transmitted from the card reading device 300.

S405, the terminal device 100 sends a response message to the card reader device 300, where the response message is used to indicate that the Applet of the traffic card is not activated.

Specifically, after determining that the Applet of the traffic card is not activated, the terminal device 100 may send a response message (for example, 6a82 error code) to the card reader device 300, so as to notify the card reader device 300 that the Applet of the traffic card is not activated, and the terminal device 100 cannot select the Applet of the traffic card to perform the NFC transaction with the card reader device 300, that is, the present transaction fails.

S406, the terminal device 100 closes the card simulation function.

S407, the terminal device 100 cancels the Applet for activating the car key and activates the Applet of the traffic card.

S408, the terminal device 100 starts the card simulation function.

Specifically, after determining that the Applet of the traffic card is not activated, the terminal device 100 may close the card emulation function first, then cancel the Applet of the activated car key, after canceling the Applet of the activated car key, the terminal device 100 may activate the Applet of the traffic card, and after activating the Applet of the traffic card, the card emulation function may be restarted so that the subsequent card reading device 300 may perform NFC transactions with the Applet of the traffic card.

S409, the card reader 300 transmits the AID of the traffic card to the terminal 100.

Specifically, after receiving the response message sent by the terminal device 100 in the above step S405, the card reading device 300 may send the AID of the traffic card to the terminal device 100 again, so as to apply for the card reading device 300 to the terminal device 100 to perform the NFC transaction with the Applet of the traffic card again.

In one possible implementation, in a case where the distance between the terminal device 100 and the card reading area of the card reading device 300 is within the communication distance range of NFC, the card reading device 300 may periodically send the AID of the traffic card to the terminal device 100 until the Applet transaction of the card reading device 300 with the traffic card is successful.

In another possible implementation manner, if the distance between the terminal device 100 and the card reading area of the card reading device 300 is within the communication distance range of NFC, if the first NFC transaction between the card reading device 300 and the Applet of the traffic card fails, the user needs to distance the terminal device 100 from the card reading area of the card reading device 300 and then approach the card reading area of the card reading device 300, so that the card reading device 300 can send the AID of the traffic card to the terminal device 100 again, and apply for the NFC transaction between the card reading device 300 and the Applet of the traffic card to the terminal device 100 again.

S410, the terminal device 100 determines that the Applet of the traffic card has been activated based on the AID of the traffic card, and determines that the authentication is passed based on the Applet of the traffic card.

S411, the terminal device 100 transmits a processing result to the card reader device 300, the processing result being used to indicate that authentication is passed.

S412, the card reading device 300 determines that the authentication passes based on the processing result and opens the gate.

Specifically, in the case of activating the Applet of the NFC emulated card, the terminal device 100 may emulate the function of the physical card, process the NFC transaction request of the card reading device 300 through the Applet of the NFC emulated card, and respond, for example, send a processing result to the card reading device 300, so that the card reading device 300 performs a corresponding task based on the processing result, for example, the NFC emulated card is a traffic card, and after receiving the processing result that the terminal device 100 passes the authentication, the card reading device 300 may determine that the authentication passes and switch on based on the processing result.

One possible cooperation between the respective modules inside the terminal device 100 and the card reader device 300 when the method shown in fig. 4 described above is implemented are exemplarily described below with reference to fig. 5.

As shown in fig. 5, the terminal device 100 may include an NFC chip, an NFC service module, a security chip, and a service management application. The following is a detailed description.

Stage one, card opening and activating stage

S501, the service management application opens the traffic card and the car key based on user operation.

Wherein the service management application may be, for example, a wallet application.

The user interface involved in the process of opening the traffic card and the car key by the user will be described in detail in the embodiments related to the subsequent interfaces, and will not be expanded here.

In the embodiment of the application, the service management application opens the NFC analog card, which can include but is not limited to the following two possible implementation manners.

In one possible implementation manner, when the service management application opens a certain NFC analog card, the service management application may obtain data of the NFC analog card from the server, where the data includes, but is not limited to, installation data of an Applet of the NFC analog card, an original non-contact parameter of the NFC analog card and a value thereof, and further, the service management application may send the data to the security chip, where the security chip may install the Applet of the NFC analog card and store the original non-contact parameter of the NFC analog card and the value thereof. So far, the NFC analog card is successfully opened.

In another possible implementation manner, the data of some NFC analog cards may be pre-stored in the security chip, and when detecting that a user opens one of the NFC analog cards, the security chip may install an Applet of the NFC analog card based on the pre-stored data of the NFC analog card. So far, the NFC analog card is successfully opened.

In some embodiments, in the case of simultaneously opening a plurality of NFC emulated cards, since the values of the original non-contact parameters of different NFC emulated cards are inconsistent and the NFC chip can only apply the non-contact parameters of one NFC emulated card at the same time, the service management application may determine which NFC emulated card Applet to activate based on a preset rule. The preset rule is not specifically limited in the embodiment of the present application.

For example, the preset rule may be a preset service priority rule, where the service management application determines to preferentially activate the Applet of the NFC analog card with a higher service priority, for example, the service corresponding to the vehicle key is a vehicle service, the service corresponding to the traffic card is a traffic service, and if the priority of the vehicle service is higher than that of the traffic service, the service management application determines to preferentially activate the Applet of the vehicle key. It is easy to understand that in the case where the Applet of the car key is in an activated state, the Applet of the traffic card is in an inactivated state.

In the embodiment of the present application, in the case of determining that the Applet of the car key needs to be activated, the service management application instructs the security chip to activate the Applet of the car key through the NFC service module, and one possible implementation manner is as follows in step S502-step S503.

S502, the service management application sends a message 1 to the NFC service module, wherein the message 1 is used for indicating the NFC service module to inform the security chip to activate the Applet of the car key.

S503, the NFC service module sends a message 2 to the security chip, wherein the message 2 is used for indicating the security chip to activate an Applet of the car key.

S504, the security chip activates an Applet of the car key.

Specifically, after receiving the message 2 sent by the NFC service module, the security chip may perform an activation operation on the Applet of the installed car key to activate the Applet of the car key, because the security chip installs the Applet of the car key when the traffic management application starts the car key.

It is easy to understand that the security chip may be in an active state after activating an Applet of a certain NFC emulated card.

In the embodiment of the application, that a certain Applet is in an activated state may mean that the Applet is in a normal running state.

S505, the NFC service module sends original non-contact parameters of the car key and the value thereof to the NFC chip.

Specifically, after the security chip activates the Applet of the car key, the NFC service module may send the original non-contact parameter of the car key and its value to the NFC chip, and the NFC chip may store the original non-contact parameter of the car key and its value, so that the subsequent NFC chip may perform NFC communication with the card reader based on the original non-contact parameter of the car key and its value.

It is easy to understand that the original non-contact parameters of the car key and the values thereof can be obtained by the NFC service module in the security chip.

Stage two, transaction stage

S506, the terminal device 100 approaches to the card reading device 300, wherein the card reading device 300 is a traffic card gate.

S507, the card reader 300 sends the AID of the traffic card to the NFC chip.

In the embodiment of the present application, the card reader 300 may perform NFC communication with the terminal device 100 through an NFC chip in the terminal device 100.

Specifically, since the card reader device 300 is a traffic card gate, in the case that the terminal device 100 is detected to be close to the card reader device 300, the card reader device 300 may send the AID of the traffic card to the NFC chip to apply for the terminal device 100 for the NFC transaction between the card reader device 300 and the Applet of the traffic card.

In one possible implementation, the AID of the traffic card may be sent by the card reader device 300 to the NFC chip in the terminal device 100 through a SELECT AID instruction.

The AID may be a unique identification of an Applet of the NFC emulated card defined by the ISO 14443-4 protocol.

And S508, the NFC chip sends a message 3 to the security chip, wherein the message 3 is used for requesting the security chip to select an Applet of the traffic card to execute a transaction task.

Specifically, after receiving the AID of the traffic card sent by the card reader 300, the NFC chip may directly route to the security chip based on the AID of the traffic card, so as to request the security chip to select an Applet using the traffic card to perform a transaction task.

S509, the security chip detects that the Applet of the traffic card is not activated.

Specifically, after receiving the above message 3 sent by the NFC chip, the security chip may detect whether the Applet of the traffic card is activated, and as known in step S504, the security chip activates the Applet of the car key, and only one NFC analog card can be kept in an activated state, so that the security chip may determine that the Applet of the traffic card is not activated.

In one possible implementation manner, the message 3 may include an AID of the traffic card, and the on-chip operating system (chip operating system, COS) in the security chip may perform an AID distribution operation of the traffic card, that is, distribute the AID of the traffic card to an Applet of the corresponding traffic card, if the distribution fails, it indicates that the Applet of the traffic card is not activated, and if the distribution is successful, it indicates that the Applet of the traffic card is activated.

S510, the security chip sends a message 4 to the NFC chip, wherein the message 4 is used for indicating that the Applet of the traffic card is not activated.

Specifically, after detecting that the Applet of the traffic card is not activated, the security chip may notify the NFC chip that the Applet of the traffic card is not activated so that the NFC chip may answer the card reading device 300.

S511, the NFC chip sends a response message to the card reader 300, where the response message is used to indicate that the Applet of the traffic card is not activated.

Specifically, after receiving the above message 4 sent by the security chip, the NFC chip may send a response message (for example, a 6a82 error code) to the card reader 300 based on the message 4 to notify the card reader 300 that the Applet of the traffic card is not activated, where the security chip cannot select the Applet of the traffic card to perform the NFC transaction with the card reader 300, i.e. the present transaction fails.

S512, the NFC chip sends the AID of the traffic card to the NFC service module.

Specifically, after receiving the above message 4 sent by the security chip, the NFC chip may send the AID of the traffic card to the NFC service module, so as to instruct the NFC service module to apply for activating the Applet of the traffic card to the security chip, that is, the NFC chip sends a card-cutting application, so that the security chip switches the Applet of the NFC analog card that has been activated currently from the Applet of the car key to the Applet of the traffic card.

It should be noted that, in the embodiment of the present application, the execution time sequence of the step S511 and the step S512 is not limited, the step S511 and the step S512 may be executed simultaneously, and the step S511 may be executed before/after the step S512.

S513, the NFC service module closes the card simulation function.

Specifically, after receiving the AID of the traffic card sent by the NFC chip, the NFC service module may close the card emulation function of the terminal device 100, so that a subsequent card cutting operation, that is, an operation of "activating an Applet of a traffic card by deactivating an Applet of a car key" in step S515 described below may be performed.

And S514, the NFC service module sends a message 5 to the security chip, wherein the message 5 is used for indicating the security chip to activate the Applet of the traffic card.

S515, the security chip cancels the Applet for activating the car key and activates the Applet of the traffic card.

Specifically, after receiving the above message 5 sent by the NFC service module, the security chip generally uses two different NFC analog cards, where the values of the original non-contact parameters of the two NFC analog cards are inconsistent, so that the security chip may cancel the Applet of the vehicle key and then activate the Applet of the traffic card when detecting that the values of the original non-contact parameters of the vehicle key and the original non-contact parameters of the traffic card are inconsistent.

S516, the security chip sends a message 6 to the NFC service module, wherein the message 6 is used for indicating that the Applet of the traffic card is activated.

S517, the NFC service module starts a card simulation function.

Specifically, the NFC service module may restart the card emulation function of the terminal device 100 after receiving the above message 6 sent by the security chip, so that the subsequent card reading device 300 may perform an NFC transaction with the Applet of the traffic card.

S518, the NFC service module sends the original non-contact parameters of the traffic card and the value thereof to the NFC chip.

Specifically, after activating the Applet of the traffic card, the NFC service module may send the original non-contact parameter of the traffic card and its value to the NFC chip, and the NFC chip may store the original non-contact parameter of the traffic card and its value, so that the subsequent NFC chip may perform NFC communication with the card reading device based on the original non-contact parameter of the traffic card and its value.

It is easy to understand that the original non-contact parameters and the values of the traffic cards can be obtained by the NFC service module in the security chip.

In one possible implementation, after the NFC chip saves the original non-contact parameters and the values thereof of the traffic card, the original non-contact parameters and the values thereof of the vehicle key saved before may be deleted.

S519, the card reader 300 sends the AID of the traffic card to the NFC chip.

Specifically, after receiving the response message sent by the NFC chip of the terminal device 100 in the above step S511, the card reading device 300 may send the AID of the traffic card to the NFC chip of the terminal device 100 again, so as to apply for the card reading device 300 to the terminal device 100 to perform the NFC transaction with the Applet of the traffic card again.

S520, the NFC chip sends a message 7 to the security chip, wherein the message 7 is used for requesting the security chip to select an Applet of the traffic card to execute a transaction task.

S521, the security chip detects that the Applet of the traffic card is activated, and determines that the authentication is passed based on the Applet of the traffic card.

S522, the security chip sends a processing result to the card reading device 300 through the NFC chip, wherein the processing result is used for indicating that authentication is passed.

S523, the card reader 300 determines that the authentication is passed based on the processing result, and opens the gate.

Specifically, after receiving the above message 7 sent by the NFC chip, the security chip may detect whether the Applet of the traffic card has been activated, and as known in the above step S515, the security chip has activated the Applet of the traffic card, and thus, the security chip may determine that the Applet of the traffic card has been activated.

Further, in the case where it is determined that the Applet of the traffic card has been activated, the security chip may process the NFC transaction request of the card reading device 300 through the Applet of the traffic card and respond, for example, send a processing result to the card reading device 300 through the NFC chip, so that the card reading device 300 performs a corresponding task based on the processing result, for example, after receiving the processing result that the authentication of the terminal device 100 is passed, the card reading device 300 may determine that the authentication is passed based on the processing result and open the gate.

By implementing the method shown in fig. 4 and 5, when the terminal device 100 approaches the card reader device 300, the terminal device 100 can automatically activate the Applet of the NFC analog card corresponding to the card reader device 300 without manually selecting the card by the user, thereby simplifying the user operation. The methods shown in fig. 4 and 5 described above also have the following problems:

1. When the terminal device 100 is in a power-on state and the terminal device 100 approaches to the card reading device 300, the terminal device 100 needs to be triggered to match an NFC analog card corresponding to the card reading device 300 by reporting features of the NFC analog card (for example, AID of the NFC analog card) to the terminal device 100 by the card reading device 300, and if the NFC analog card currently in an active state is not the NFC analog card corresponding to the card reading device 300, the terminal device needs to switch cards in real time, that is, cancel activating the NFC analog card first and then deactivate the NFC analog card corresponding to the card reading device 300.

In this way, on the one hand, the whole process takes a long time, for example, it may take at least 700ms, on the other hand, if the card reading device 300 fails to report the features of the NFC analog card to the terminal device 100 in time, the terminal device 100 may select by default to use the NFC analog card currently in the activated state to perform the NFC transaction with the card reading device 300, and if the NFC analog card is not the NFC analog card corresponding to the card reading device 300, the NFC analog card corresponding to the card reading device 300 is still in the unactivated state, so that the transaction fails, and a user needs to manually operate to trigger the terminal device 100 to activate the NFC analog card corresponding to the card reading device 300 and re-execute the transaction process, so that the user experience is poor.

2. After the terminal device 100 completes the switching of the card through the security chip, that is, after the NFC analog card corresponding to the card reader device 300 is activated, the card reader device 300 needs to initiate a transaction application to the terminal device 100 again to execute a subsequent transaction process, and different card readers 300 and suppliers are different, so that the mechanism of reinitiating the transaction application may be different and difficult to return to unity, which may result in uncontrollable time consumption of the whole process, and may require the user to execute the card swiping operation (that is, execute the operation of the terminal device 100 approaching the card reader device 300 multiple times), which is bad in user experience.

3. Since the service module (for example, NFC service module) of the software layer of the terminal device 100 is usually powered down and is in a closed state when the terminal device 100 is in a power-off state, in the case where the terminal device 100 is in a power-off state and a plurality of NFC analog cards have been turned on, the terminal device 100 does not perform the operation of switching cards, that is, only the NFC analog card currently in an active state is available, another NFC analog card is not deactivated, and if the NFC analog card corresponding to the card reading device 300, which is close to the current terminal device 100, is not the NFC analog card currently in an active state, a transaction failure is caused, and the user experience is poor.

Based on the above-described problems, the present application provides a solution shown in fig. 6 in the following second embodiment, which will be described in detail below.

Embodiment II,

In the second embodiment, when the terminal device opens each NFC analog card, the terminal device may adjust the value of the original non-contact parameter of each NFC analog card to the value of the system-level non-contact parameter, that is, the values of the non-contact parameters of all the NFC analog cards are normalized to the values of the same group of non-contact parameters, so that the terminal device may simultaneously place the plurality of NFC analog cards in an active state when opening the plurality of NFC analog cards, so as to realize that all the opened NFC analog cards are available at the same time. In addition, when the terminal device is in a shutdown state, the plurality of NFC analog cards still can be kept in an activated state and are available at the same time, and special processing is not needed. Therefore, the method and the device have the advantages that extra operation of a user is not needed, the card swiping time can be reduced, the card swiping success rate under the condition of encountering non-standard card reading equipment or other abnormal scenes is improved, and the card swiping experience of the user is improved.

Fig. 6 illustrates a specific flow of another card management method according to an embodiment of the present application.

As shown in fig. 6, the method can be applied to a communication system including a terminal device 100, a server 200, and a card reading device 300. Taking the scenario that the terminal device 100 is a mobile phone, the card reader 300 is a gate, and the user opens the traffic card first and then opens the car key as an example, the specific steps of the method are described in detail below:

stage one, traffic card opening and activating stage

S601, the terminal device 100 detects an operation of opening the traffic card by the user.

S602, the terminal device 100 sends a message 1 to the server 200, where the message 1 is used for applying to adjust the original non-contact parameter value of the traffic card to the system-level non-contact parameter value.

Specifically, after detecting an operation of opening a traffic card by a user, the terminal device 100 may send a message 1 to the server 200 in response to the operation, so as to apply for the server 200 to adjust the value of the original non-contact parameter of the traffic card to the value of the system-level non-contact parameter, and obtain the system-level non-contact parameter and the value thereof.

S603, the server 200 sends a message 2 to the terminal device 100, where the message 2 includes the system-level non-contact parameter and the value thereof.

Specifically, after receiving the above-mentioned message 1 sent by the terminal device 100, the server 200 may send a message 2 to the terminal device 100 based on the above-mentioned message 1 to issue a system-level non-contact parameter and its value to the terminal device 100, which indicates that the server 200 has filed the above-mentioned application by the terminal device 100.

S604, the terminal device 100 adjusts the original non-contact parameter value of the traffic card to the system-level non-contact parameter value.

Specifically, after receiving the above message 2 sent by the server 200, the terminal device 100 may adjust the value of the original contactless parameter of the traffic card to the value of the system-level contactless parameter based on the message 2, and store the value, so that the subsequent terminal device 100 may perform NFC communication with the card reader corresponding to the traffic card based on the system-level contactless parameter and the value thereof.

S605, the terminal device 100 activates an Applet of the traffic card.

Specifically, the terminal device 100 may activate an Applet of the traffic card after the terminal device 100 adjusts the value of the original non-contact parameter of the traffic card to the value of the system-level non-contact parameter.

It is easily understood that the terminal device 100 will be in an activated state after activating the Applet of the traffic card.

It should be noted that, the data of a certain NFC analog card (for example, the installation data of the Applet of the NFC analog card, the original non-contact parameter of the NFC analog card, the value thereof, and the like) may be stored in the terminal device 100 in advance before the terminal device 100 detects the operation of opening the NFC analog card by the user, after detecting the operation of opening the NFC analog card by the user, the terminal device 100 may install the Applet of the NFC analog card, thereby successfully opening the NFC analog card, or the terminal device 100 may obtain the data from the server 200 after detecting the operation of opening the NFC analog card by the user, and after obtaining the data, the terminal device 100 may install the Applet of the NFC analog card, and store the original non-contact parameter of the NFC analog card and the value thereof, thereby successfully opening the NFC analog card.

Stage two, vehicle key opening and activating stage

S606, the terminal device 100 detects an operation of opening the key by the user.

S607, the terminal device 100 sends a message 3 to the server 200, where the message 3 is used to apply for adjusting the original non-contact parameter value of the vehicle key to the system-level non-contact parameter value.

Specifically, after detecting the operation of the user to start the car key, the terminal device 100 may send a message 3 to the server 200 in response to the operation, so as to apply for the server 200 to adjust the value of the original non-contact parameter of the car key to the value of the system-level non-contact parameter, and obtain the system-level non-contact parameter and the value thereof.

S608, the server 200 sends a message 4 to the terminal device 100, where the message 4 includes the system-level non-contact parameter and the value thereof.

Specifically, after receiving the above-mentioned message 3 sent by the terminal device 100, the server 200 may send a message 4 to the terminal device 100 based on the above-mentioned message 3 to issue a system-level non-contact parameter and its value to the terminal device 100, which indicates that the server 200 has filed the above-mentioned application by the terminal device 100.

In some embodiments, when the terminal device 100 does not first open the NFC analog card and the system-level non-contact parameter and the value thereof are not updated after the last opening of the NFC analog card, the message 4 may not include the system-level non-contact parameter and the value thereof, but only be used to indicate that the server 200 has passed the application, and after receiving the message 4, the terminal device 100 may directly use the system-level non-contact parameter and the value thereof obtained when the last opening of the NFC analog card to adjust the original non-contact parameter and the value thereof of the currently opened NFC analog card.

S609, the terminal device 100 adjusts the original non-contact parameter value of the car key to the system-level non-contact parameter value.

Specifically, after receiving the above message 4 sent by the server 200, the terminal device 100 may adjust the value of the original non-contact parameter of the car key to the value of the system-level non-contact parameter based on the message 4, and store the value, so that the subsequent terminal device 100 may perform NFC communication with the card reader device corresponding to the car key based on the system-level non-contact parameter and the value thereof.

S610, the terminal device 100 activates the Applet of the car key while keeping the Applet of the traffic card in an activated state.

Specifically, after the terminal device 100 adjusts the value of the original non-contact parameter of the car key to the value of the system-level non-contact parameter, the terminal device 100 may activate the Applet of the car key.

It is easy to understand that after the terminal device 100 activates the Applet of the traffic card, the Applet of the traffic card is in an activated state, i.e., a normal operation state.

It can be seen that, unlike the foregoing embodiment, since the non-contact parameters of the car key and the traffic card and the values thereof use the system-level non-contact parameters and the values thereof, the values of the non-contact parameters of the two NFC analog cards are identical, and there is no conflict problem, in the step S610, the terminal device 100 can still keep the Applet of the traffic card in the activated state at the same time after activating the Applet of the car key, thereby achieving the purpose of activating a plurality of NFC analog cards at the same time. It is easy to understand that under the condition that a plurality of NFC analog cards are activated simultaneously, the NFC analog cards are available simultaneously, manual operation of a user is not needed, time consumption is reduced, the success rate of card swiping is improved, and greater convenience and better card swiping experience can be brought to the user.

Stage three, transaction stage

S611, the terminal device 100 approaches to the card reading device 300, wherein the card reading device 300 is a traffic card gate.

S612, the card reader 300 transmits the AID of the traffic card to the terminal 100.

S613, the terminal device 100 determines that the Applet of the traffic card has been activated based on the AID of the traffic card, and determines that the authentication is passed based on the Applet of the traffic card.

S614, the terminal device 100 transmits a processing result to the card reader device 300, the processing result being used to indicate that authentication is passed.

S615, the card reading device 300 determines that the authentication passes based on the processing result and opens a gate.

One possible cooperation between the modules inside the terminal device 100 and the modules inside the card reader device 300 and the server 200 when the method shown in fig. 6 is implemented are exemplarily described below with reference to fig. 7.

As shown in fig. 7, the terminal device 100 may include an NFC chip, an NFC service module, a security chip, a service management application, and the server 200 may include a trusted service management module. The following is a detailed description.

Stage one, traffic card opening and activating stage

S701, the service management application detects the operation of opening the traffic card by the user.

The user interface involved in the process of opening the traffic card by the user will be described in detail in the embodiments related to the subsequent interfaces, which are not developed here.

S702, the service management application sends a message 1 to the trusted service management module, wherein the message 1 is used for applying to adjust the original non-contact parameter value of the traffic card to the system-level non-contact parameter value.

Specifically, after detecting an operation of opening a traffic card by a user, the service management application may respond to the operation, and send a message 1 to a trusted service management module of the server 200, so as to apply for the server 200 to adjust the value of the original non-contact parameter of the traffic card to the value of the system-level non-contact parameter, and obtain the system-level non-contact parameter and the value thereof.

S703, the trusted service management module sends a message 2 to the service management application, wherein the message 2 comprises the system-level non-contact parameters and the values thereof.

Specifically, after receiving the above-mentioned message 1 sent by the service management application of the terminal device 100, the trusted service management module may send a message 2 to the service management application of the terminal device 100 based on the above-mentioned message 1, so as to issue a system-level non-contact parameter and its value to the service management application of the terminal device 100, which indicates that the server 200 has filed the above-mentioned application through the service management application of the terminal device 100.

In one possible implementation, the message 2 may be sent in the form of an instruction, where the instruction may be used to instruct an Applet that manages the NFC emulated card, adjust the value of the original contactless parameter of the NFC emulated card, etc.

And S704, the service management application sends a message 3 to the security chip, wherein the message 3 is used for indicating the security chip to adjust the original non-contact parameter value of the traffic card to the system-level non-contact parameter value.

In one possible implementation, the message 3 and the message 2 may be the same message, and after receiving the message 2 sent by the trusted service management module of the server 200, the service management application may send the message 2 to the security chip in a transparent manner, so that the security chip may perform an operation of adjusting the value of the original contactless parameter of the traffic card to the value of the system-level contactless parameter.

And S705, the security chip adjusts the original non-contact parameter value of the traffic card to the system-level non-contact parameter value.

Specifically, after receiving the message 3 sent by the service management application, the security chip may adjust the value of the original non-contact parameter of the traffic card to the value of the system-level non-contact parameter based on the message 3.

S706, the security chip sends a message 4 to the service management application, wherein the message 4 is used for indicating that the security chip has adjusted the original non-contact parameter value of the traffic card to the system-level non-contact parameter value.

Specifically, after the security chip adjusts the value of the original non-contact parameter of the traffic card to the value of the system-level non-contact parameter, the security chip may send a message 4 to the service management application to notify the service management application that the security chip has adjusted the value of the original non-contact parameter of the traffic card to the value of the system-level non-contact parameter, so that the service management application may continue to perform subsequent operations.

In one possible implementation manner, when the service management application opens a certain NFC analog card, data of the NFC analog card may be obtained from the server, where the data includes, but is not limited to, installation data of an Applet of the NFC analog card, an original non-contact parameter of the NFC analog card and a value thereof, and further, the service management application may send the data to the security chip, where the security chip may install the Applet of the NFC analog card and store the original non-contact parameter of the NFC analog card and the value thereof. Further, the service management application can also acquire and send the system-level non-contact parameter and the value thereof to the security chip, and the security chip can adjust the value of the original non-contact parameter of the NFC analog card to the value of the system-level non-contact parameter. So far, the NFC analog card is successfully opened.

In another possible implementation manner, the security chip may also pre-store data of some NFC analog cards, when detecting that a user opens one of the NFC analog cards, the security chip may install an Applet of the NFC analog card based on the pre-stored data of the NFC analog card, further, the service management application may further obtain and send a system-level non-contact parameter and a value thereof to the security chip, and the security chip may then adjust the value of the original non-contact parameter of the NFC analog card to the value of the system-level non-contact parameter. So far, the NFC analog card is successfully opened.

And S707, the service management application sends a message 5 to the NFC service module, wherein the message 5 is used for indicating the NFC service module to inform the security chip to activate the Applet of the traffic card.

And S708, the NFC service module sends a message 6 to the security chip, wherein the message 6 is used for indicating the security chip to activate the Applet of the traffic card.

Specifically, after receiving the message 4 sent by the security chip, the service management application determines that the security chip has adjusted the original non-contact parameter of the traffic card to the system-level non-contact parameter based on the message 4, and further, the service management application can notify the security chip to activate the Applet of the traffic card through the NFC service module.

S709, the security chip activates the Applet of the traffic card.

Specifically, after receiving the message 6 sent by the NFC service module, the security chip may perform an activation operation on the Applet of the installed traffic card to activate the Applet of the traffic card, because the security chip installs the Applet of the traffic card when the traffic management application opens the traffic card.

It is easy to understand that after the security chip activates an Applet of a certain NFC emulated card, the Applet may be in an activated state, i.e. a normal running state.

S710, the NFC service module sends the system-level non-contact parameters and the values thereof to the NFC chip.

Specifically, after activating the Applet of the traffic card, the NFC service module may send the system-level non-contact parameter and its value to the NFC chip, where the NFC chip may store the system-level non-contact parameter and its value, so that the subsequent NFC chip may perform NFC communication with the card reader based on the system-level non-contact parameter and its value.

It is easy to understand that, since the traffic card is the first NFC analog card activated on the terminal device 100, no other non-contact parameters are stored in the NFC chip before the Applet of the traffic card is activated, and therefore, after the Applet of the traffic card is activated, the NFC chip can normally store and apply the system-level non-contact parameters without collision problems.

It is easy to understand that the system-level non-contact parameter and the value thereof can be obtained by the NFC service module in the secure chip.

Stage two, vehicle key opening and activating stage

S711, the service management application detects the operation of a user driving a car key.

And S712, the service management application sends a message 7 to the trusted service management module, wherein the message 7 is used for applying to adjust the original non-contact parameter value of the car key to the system-level non-contact parameter value.

S713, the trusted service management module sends a message 8 to the service management application, wherein the message 8 comprises the system-level non-contact parameters and the values thereof.

S714, the service management application sends a message 9 to the security chip, wherein the message 9 is used for indicating the security chip to adjust the original non-contact parameter value of the car key to the system-level non-contact parameter value.

S715, the security chip adjusts the original non-contact parameter value of the car key to the system-level non-contact parameter value.

S716, the security chip sends a message 10 to the service management application, wherein the message 10 is used for indicating that the security chip has adjusted the original non-contact parameter value of the car key to the system-level non-contact parameter value.

S717, the service management application sends a message 11 to the NFC service module, where the message 11 is used to instruct the NFC service module to notify the security chip to activate the Applet of the car key.

S718, the NFC service module sends a message 12 to the security chip, wherein the message 12 is used for indicating the security chip to activate an Applet of the car key.

S719, the security chip activates the Applet of the car key, and simultaneously keeps the Applet of the traffic card in an activated state.

The specific execution of steps S711 to S719 in the second stage is similar to the specific execution of steps S701 to S709 in the first stage, and the description thereof will be referred to in the related text and will not be repeated here.

It is easy to understand that, since the car key is an NFC analog card activated by the terminal device 100 after activating the traffic card, the NFC chip stores the non-contact parameters before activating the Applet of the car key, but since the car key and the traffic card both use the system-level non-contact parameters, after activating the Applet of the car key, the Applet of the traffic card is still in an activated state, and the NFC chip can normally apply the system-level non-contact parameters, so that no collision problem occurs.

Stage three, transaction stage

S720, the terminal device 100 approaches to the card reading device 300, wherein the card reading device 300 is a traffic card gate.

S721, the card reader 300 transmits the AID of the traffic card to the NFC chip.

S722, the NFC chip sends a message 13 to the secure chip, where the message 13 is used to request the secure chip to select an Applet using the traffic card to execute the transaction task.

S723, the security chip detects that the Applet of the traffic card is activated, and determines that the authentication is passed based on the Applet of the traffic card.

S724, the security chip sends a processing result to the card reading device 300 through the NFC chip, wherein the processing result is used for indicating that authentication is passed.

S725, the card reading device 300 determines that the authentication is passed based on the processing result and opens the gate.

Specifically, after receiving the above message 13 sent by the NFC chip, the security chip may detect whether the Applet of the traffic card has been activated, and as known in step S709 above, the security chip has activated the Applet of the traffic card, and thus, the security chip may determine that the Applet of the traffic card has been activated.

In one possible implementation manner, the message 13 may include an AID of the traffic card, and the on-chip operating system (chip operating system, COS) in the security chip may perform an AID distribution operation of the traffic card, that is, distribute the AID of the traffic card to an Applet of the corresponding traffic card, if the distribution fails, it indicates that the Applet of the traffic card is not activated, and if the distribution is successful, it indicates that the Applet of the traffic card is activated.

It is easy to see that since all the NFC emulated cards that have been turned on have been activated in advance, compared with the previous embodiment, the NFC transaction with the card reading device 300 can be directly started without the security chip performing the operation of activating the NFC emulated cards again, i.e. without switching cards.

By implementing the methods shown in fig. 6 and 7, the following advantages can be achieved:

1. Referring to fig. 8, the values of the non-contact parameters of each NFC analog card are different, the NFC chip can only apply one set of non-contact parameters at the same time, and cannot be compatible with the same set of non-contact parameters with different values at the same time, and when different NFC analog cards are activated at the same time, the problem of non-contact parameter collision can occur, so that only one NFC analog card (such as the traffic card 1 shown in fig. 8) can be in an activated state, and other NFC analog cards are in a deactivated state, and when other NFC analog cards need to be activated, the currently activated analog card needs to be deactivated first, and then the other NFC analog cards need to be deactivated. By implementing the improvement scheme in the second embodiment, the values of the non-contact parameters of all the NFC analog cards can be globally unified and used by all the NFC analog cards, so that the problem of non-contact parameter conflict can be solved, and all the NFC analog cards can be in an activated state and available at the same time. In this way, when the user performs the card swiping operation, the terminal device 100 does not need to switch cards in real time, so that time consumption (for example, at least 700 ms) for deactivating the original card and activating the target card can be saved, and in addition, all cards are available at the same time, NFC transaction can be directly performed when the user swipes the card, and the card swiping success rate can be improved.

2. Referring to fig. 9, by implementing the modification of the second embodiment, when the terminal device 100 is in the on state, the terminal device 100 may adjust the values of the non-contact parameters of each card when opening each card, so as to keep the values of the non-contact parameters of each card consistent, and after activating the Applet of each card, the Applet of each card with consistent values of the non-contact parameters may simultaneously keep the activated state and the plurality of cards may be simultaneously available. Thus, the purpose that a plurality of cards are simultaneously available in the starting-up state is achieved.

With continued reference to fig. 9, by implementing the improvement in the second embodiment, in the shutdown state of the terminal device 100, since the terminal device 100 after shutdown still supplies power to the security chip and the NFC chip independently, and the applets of each card in the security chip are in an activated state before shutdown, the activated states of the applets of the cards can be kept unchanged and still stand by in real time after the terminal device 100 is shutdown. Therefore, the problem that only a single card is available in the shutdown scene is solved, and the aim that a plurality of cards are available at the same time in the shutdown state is fulfilled.

3. Referring to fig. 10, in the case where the terminal device 100 can only place an Applet of one NFC emulated card of the plurality of NFC emulated cards that have been turned on in an activated state, the terminal device 100 can only display one NFC emulated card that has been activated (for example, the traffic card 1 shown in (a) of fig. 10) on the user interface for displaying the card that is currently activated. By implementing the modification of the second embodiment, the terminal device 100 may put the applets of the plurality of already-opened NFC analog cards in an activated state, and then the terminal device 100 may display the plurality of already-activated NFC analog cards (e.g., the car key 1, the traffic card 1, the door lock key 1, the campus card 1, etc. shown in (b) of fig. 10) on the user interface for displaying the currently-activated cards. In this way, the terminal device 100 can support the user to view a plurality of activated NFC emulated cards.

As can be seen from the methods shown in fig. 6 and fig. 7, each time the terminal device 100 opens an NFC analog card, the Applet of the NFC analog card is automatically activated, that is, the terminal device 100 can automatically keep all the applets of the opened NFC analog card in an activated state.

In some embodiments, the terminal device 100 may also automatically only hold all of the applets of the partially opened NFC emulated card in an activated state while the applets of the other partially opened NFC emulated card remain in an inactivated state, in which case the terminal device 100 may determine which of the applets of the NFC emulated card may be automatically activated and which of the applets of the NFC emulated card may not be automatically activated based on preset rules, where the preset rules may include, but are not limited to, 1, a service priority rule, e.g., the applets of the NFC emulated card having a service priority of the first M (where M is a positive integer greater than 1) may be automatically activated, 2, an opening order rule, e.g., the first N (where N is a positive integer greater than 1) of the applets of the NFC emulated card may be automatically activated, and so on. In this way, for the NFC analog cards of most of the common services of the users or the NFC analog cards of each user, the terminal device 100 can be automatically activated, so that when the user uses the NFC analog cards, the user does not need to switch the cards, which is convenient and fast, and the user can be ensured to have better use experience.

In other embodiments, the terminal device 100 may also support the user to manually activate an Applet of some or all of the NFC emulated card that has been turned on. In this way, the user wants to activate the Applet of which NFC emulated card, and more space and autonomous settings can be given to the user. It is easy to understand that, when the number of applets of the NFC analog card manually activated by the user is greater than or equal to 2, the original non-contact parameter of the NFC analog card needs to be adjusted to be the system-level non-contact parameter, that is, the plurality of NFC analog cards use the same set of non-contact parameters.

The user interface related to the card management method according to the embodiment of the present application is described below with reference to fig. 11A to 11T.

Taking two NFC analog cards, i.e., a traffic card and a car key, as an example, it is assumed that the traffic card is turned on first and then the car key is turned on, and exemplary description is given below.

Fig. 11A-11I illustrate a series of user interfaces involved in provisioning a traffic card.

Referring to fig. 11A, the user interface shown in fig. 11A may be one provided by a desktop in the terminal device 100, and one or more icons of applications (e.g., an icon of a wallet application, an icon of a setup application, etc.) may be included in the user interface. The terminal device 100 may detect an operation (e.g., a click operation) of the icon of the wallet application by the user, and in response to the operation, the terminal device 100 may display a user interface exemplarily shown in fig. 11B.

Referring to fig. 11B, the user interface shown in fig. 11B may be a "home" user interface provided by a wallet application, where a plurality of functionality controls may be included in the user interface, and a user may operate on the plurality of functionality controls to use functionality corresponding to the plurality of functionality controls. Assuming that the user wants to add an NFC emulated card (e.g., traffic card, car key, etc.) on the terminal device 100, the terminal device 100 may detect a user operation (e.g., a clicking operation) for an "add" functionality control included in the user interface shown in fig. 11B, in response to which the terminal device 100 may display a window as exemplarily shown in fig. 11C, which may include one or more controls therein (e.g., a "swipe" control, an "add card" control, etc.), the user may click on the "add card" control to trigger the terminal device 100 to display the user interface as exemplarily shown in fig. 11D.

It should be noted that, the operation entries for triggering the terminal device 100 to display the user interface for adding a card shown in fig. 11D may be various, and the foregoing description only uses the "add" function control shown in fig. 11B as an example of the operation entry, and should not be construed as limiting the present application, and in some other embodiments of the present application, the terminal device 100 may be triggered to display the user interface for adding a card through other operation entries, for example, the "card package" function control shown in fig. 11B, and so on.

Referring to fig. 11D, a plurality of card addition entries (e.g., a "bank card" addition entry, a "traffic card" addition entry, a "car key" addition entry, a "certificate" addition entry, a "membership card" addition entry, an "entity card" addition entry, etc.) may be included in the user interface shown in fig. 11D, and if the user wants to open a traffic card on the terminal device 100, the user may click on the "traffic card" addition entry to trigger the terminal device 100 to display the user interface for adding a traffic card exemplarily shown in fig. 11E.

Referring to fig. 11E, a traffic card of the city in which the terminal device 100 is currently located may be displayed in the user interface shown in fig. 11E, for example, if the city in which the terminal device 100 is currently located is XX city, a traffic card of XX city (for example, "XX interconnection card") may be displayed, and a control (for example, "immediately open" control) for opening the traffic card may be displayed in the user interface shown in fig. 11E.

Optionally, the user interface shown in fig. 11E may also display an add-on entry for a traffic card of another city (e.g., an "XXX interworking card" add-on entry, an "XXXX public traffic card" add-on entry, etc.) for the user to add traffic cards of cities other than the city in which the user is currently located on the terminal device 100.

With continued reference to fig. 11E, if the user wants to turn on the traffic card of the city in which the terminal device 100 is currently located on the terminal device 100, the user may click on the "immediately on" control to trigger the terminal device 100 to display the user interface illustrated by way of example in fig. 11F.

Referring to fig. 11F, the user interface shown in fig. 11F may be used for a user to view the card opening service fee, select the recharging amount of the traffic card, and the like, and the user interface may also display a "confirm open" control, and after determining the recharging amount of the traffic card, the user may click on the "confirm open" control to trigger the terminal device 100 to display the user interface shown in fig. 11G.

Referring to fig. 11G, the user interface shown in fig. 11G may be used by the user to look up the amount to be paid, select the payment mode, etc., and a "confirm payment" control may be displayed in the user interface, and after determining the payment mode, the user may click on the "confirm payment" control, so that the terminal device 100 may perform the operation of opening the traffic card.

Optionally, during the operation of opening the traffic card, the terminal device 100 may also display a user interface as exemplarily shown in fig. 11H, where a prompt (for example, "about 1 minute is required for later) may be displayed in the user interface to prompt that the user terminal device 100 is opening the traffic card, and a real-time progress of opening the traffic card by the terminal device 100 may also be displayed in the user interface, so that the user may learn timely.

In the embodiment of the present application, the terminal device 100 performs an operation of opening a traffic card, which may specifically include obtaining installation data of an Applet of the traffic card, obtaining an original non-contact parameter of the traffic card and a value thereof, installing the Applet of the traffic card, obtaining a system-level non-contact parameter and a value thereof, adjusting the value of the original non-contact parameter of the traffic card to the value of the system-level non-contact parameter, and the like.

Referring to fig. 11I, after the terminal device 100 successfully opens the traffic card, the user interface exemplarily shown in fig. 11I may be displayed to prompt the user that the terminal device 100 successfully opens the traffic card. To this end, the terminal device 100 successfully opens the traffic card. The terminal device 100 may allow the user to view the traffic cards that have been opened in a "card package" provided by the wallet application.

It is to be readily understood that the operations for opening the traffic card by the user mentioned in the foregoing embodiments one and two may include a series of user operations exemplarily shown in fig. 11D to 11G.

11A-11I are only exemplary illustrations of user interactions involved in opening a traffic card, and should not be construed as limiting the application.

11J-11P illustrate a series of user interfaces involved in the process of activating a car key.

With continued reference to fig. 11D, if the user wants to turn on the car key on the terminal device 100, the user may click on the "car key" add entry to trigger the terminal device 100 to display the user interface exemplarily shown in fig. 11J, where the user interface may include car keys (e.g., car keys, two-wheel car keys, etc.) corresponding to multiple types of vehicles, and since each type of vehicle has multiple brands, each brand of car keys is different, the user interface may include multiple brands of car key add controls (e.g., a "brand 1 car key" add control corresponding to a car key, "brand 2 car key" add control, "brand 3 car key" add control, a "brand a car key" add control corresponding to a two-wheel car key, "brand B car key" add control, etc.). Assuming that the user wants to turn on the "brand 1 car key" corresponding to the car key on the terminal device 100, the user may click on the "brand 1 car key" add control to trigger the terminal device 100 to display the user interface illustrated in the example of fig. 11K.

Referring to fig. 11K, relevant information (such as a car key display style, a name (for example, "my love car") and the like) of the brand 1 car key may be displayed in the user interface shown in fig. 11K, an "add immediately" control may also be displayed, and the user clicking the "add immediately" control may trigger the terminal device 100 to execute the operation of opening the car key.

Optionally, during the operation of opening the car key, the terminal device 100 may also display a user interface as exemplarily shown in fig. 11L, where a prompt (for example, "adding the car key, about 1 minute, please wait") may be displayed to prompt the user that the terminal device 100 is opening the car key, and a real-time progress of opening the car key by the terminal device 100 may also be displayed in the user interface, so that the user may learn timely.

In the embodiment of the present application, the terminal device 100 performs the operation of opening the vehicle key, which may specifically include obtaining the installation data of the Applet of the vehicle key, obtaining the original non-contact parameter of the vehicle key and the value thereof, installing the Applet of the vehicle key, obtaining the system-level non-contact parameter and the value thereof, adjusting the value of the original non-contact parameter of the vehicle key to the value of the system-level non-contact parameter, and the like.

In some embodiments, after displaying the user interface shown in fig. 11L, the terminal device 100 may also display a series of user interfaces for guiding the user to pair the car key added on the terminal device 100 with the corresponding car.

For example, referring to fig. 11M, the user interface shown in fig. 11M may be used for a user to input a pairing code, where the pairing code may be sent to the terminal device 100 in a short message, and the user may execute the pairing code sending operation on the key application on the vehicle to trigger the key application to send the pairing code to the mobile phone number bound to the vehicle. After receiving the pairing code, the user may manually input the pairing code and click on the "next" control in the user interface shown in fig. 11N to trigger the terminal device 100 to display the user interface shown in fig. 11O, where a prompt (e.g., "place cell phone in tray under center console") may be displayed to prompt the user to place the terminal device 100 in tray under center console of the vehicle so that the vehicle and the terminal device 100 may be paired, and a real-time progress of pairing may also be displayed in the user interface so that the user may learn in time. After pairing is successful, the terminal device 100 may display a user interface exemplarily shown in fig. 11P to prompt the user that pairing is successful.

After the terminal device 100 successfully opens the car key, the terminal device 100 may allow the user to view the car key that has been opened in a "card pack" provided by the wallet application.

It will be readily appreciated that the operations of the user start-up key mentioned in the foregoing embodiments one and two may include a series of user operations exemplarily shown in fig. 11J to 11N.

11J-11P are only exemplary illustrations of user interactions involved in the process of turning on a car key, and should not be construed as limiting the application.

11Q-11T illustrate a series of user interfaces involved in setting a card activation policy.

In the embodiment of the present application, the terminal device 100 may support the user to autonomously set a card activation policy for the opened NFC analog card, where the card activation policy may include an automatic activation policy and a manual activation policy.

In the case where the terminal device 100 applies the automatic activation policy, the terminal device 100 may automatically activate an Applet of a partially or entirely opened NFC emulated card without requiring the user to manually perform an activation operation. Where the Applet of the NFC emulated card that has been partially opened is automatically activated, the terminal device 100 may determine which NFC emulated card applets may be automatically activated and which NFC emulated card applets may not be automatically activated based on a preset rule, where the preset rule may include, but is not limited to, 1, a service priority rule, for example, an Applet of an NFC emulated card whose service priority is M (where M is a positive integer greater than 1) may be automatically activated, 2, a card opening order rule, for example, the first N (where N is a positive integer greater than 1) NFC emulated card applets that have been opened first may be automatically activated, and so on.

In the case where the terminal device 100 applies the manual activation policy, after the terminal device 100 has opened an NFC emulated card, the Applet of the NFC emulated card is not automatically activated, but is activated after the user confirms the activation manually.

The process of setting a card activation policy is described in exemplary detail below in connection with a series of user interfaces.

Referring to fig. 11Q, the user interface exemplarily shown in fig. 11Q may be a setup interface provided by a wallet application, and one or more setup items (e.g., a "swipe card setup" item, a "card activation setup" item, a "payment and security setup" item, a "privacy" item, an "other" item, etc.) may be included in the user interface. The user may click on the "card activation settings" entry to trigger the terminal device 100 to display the user interface shown in the example of fig. 11R, in which the terminal device 100 may support the user to set the card activation policy.

Referring to fig. 11R, a control corresponding to the card activation policy selected by the user may be displayed in the user interface shown in fig. 11R, for example, an "automatically activate all opened cards" control, an "automatically activate opened cards" control that accords with a preset rule, and a "manually activate" control.

In the embodiment of the present application, the terminal device 100 may first apply a card activation policy by default, which card activation policy is applied by the terminal device 100, and the terminal device 100 will place the control corresponding to which card activation policy in the selected state. For example, as shown in fig. 11R, when the "automatically activate all cards that have been opened" control is in the selected state, it indicates that the card activation policy "automatically activate all cards that have been opened" is being applied by the terminal device 100. It will be readily appreciated that, in the case where the terminal device 100 applies the card activation policy of "automatically activating all the cards that have been activated", if the user wants to newly activate one or more NFC emulated cards on the terminal device 100, the terminal device 100 will automatically activate the Applet of the one or more NFC emulated cards after activating the one or more NFC emulated cards, that is, each time an NFC emulated card is activated, the terminal device 100 will automatically activate the Applet of the NFC emulated card.

If the user wants to switch the currently applied card activation policy, the user may directly click on the control corresponding to the target card activation policy, trigger the terminal device 100 to place the control in the selected state, and switch and apply the target card activation policy.

For example, assuming that the above-mentioned target card activation policy is a card activation policy of "automatically activating an opened card meeting a preset rule", if the terminal device 100 applies this card activation policy and the user wants to newly open an NFC emulated card on the terminal device 100, the terminal device 100 determines whether to automatically activate an Applet of the NFC emulated card based on the preset rule after opening the NFC emulated card, where the above-mentioned preset rule may refer to the above-mentioned related text description and will not be repeated here.

For example, assuming that the above-mentioned target card activation policy is a card activation policy of "manual activation", if the terminal device 100 applies this card activation policy and if the user wants to newly open an NFC emulated card on the terminal device 100, the terminal device 100 will only open the NFC emulated card, and will not automatically activate an Applet of the NFC emulated card after opening the NFC emulated card. After the user needs to manually confirm activation, the terminal device 100 activates the Applet of the NFC emulated card. For example, referring to fig. 11S, the terminal device 100 may support a user to perform a confirmation activation operation on a user interface for displaying a currently opened card, where the user interface may display an activation control corresponding to each opened NFC analog card, and the user clicking the activation control may trigger the terminal device 100 to activate the corresponding NFC analog card, for example, the user clicking the activation control corresponding to the car key shown in fig. 11S may trigger the terminal device 100 to activate an Applet of the car key, and after activation, the terminal device 100 may display a state in which the car key has been activated on the user interface shown in fig. 11T so that the user may learn in time, for example, the user clicking the activation control corresponding to the traffic card shown in fig. 11T may trigger the terminal device 100 to activate the Applet of the traffic card, and after activation, the terminal device 100 may display a state in which the traffic card has been activated on the user interface shown in fig. 11U so that the user may learn in time, and so on.

In the embodiment of the present application, if the terminal device 100 applies the card activation policy of "automatically activating the opened card conforming to the preset rule" and if the newly opened NFC analog card is not automatically activated because the newly opened NFC analog card does not conform to the preset rule, the terminal device 100 may also display an activation control corresponding to the NFC analog card on the aforementioned user interface for displaying the currently opened card, and the user may trigger the terminal device 100 to activate the Applet of the NFC analog card by clicking the control.

In the embodiment of the present application, the terminal device 100 may also support the user to manually delete the NFC emulated card or to deactivate the Applet of the NFC emulated card. The specific operation mode can be various, and the embodiment of the application is not limited to the specific operation mode. Illustratively, taking a car key as an example, the user may click on the car key entry shown in fig. 11U to trigger the terminal device 100 to display the user interface shown in fig. 11V, where a "delete card" control and a "deactivate card" control may be displayed, and the user click may trigger the terminal device 100 to delete the car key, and the user click may trigger the terminal device 100 to deactivate the Applet of the car key.

It should be noted that in the process of executing the card management method provided by the embodiment of the present application, the terminal device 100 needs to start the NFC function, where there may be various ways to start the NFC function, for example, the user may click the NFC switch control in the control center to start the NFC function, or, for example, the user may click the NFC switch control in the setting application to start the NFC function, or the like, which is not limited by the embodiment of the present application.

Fig. 12 illustrates a specific flow of another card management method according to an embodiment of the present application.

As shown in fig. 12, the method is applied to a terminal device, and specific steps of the method are described in detail below:

s1201, the terminal device approaches a first card reader device supporting the first NFC emulated card.

S1202, the terminal equipment receives a first identification sent by the first card reading equipment.

S1203, the terminal device selects a first NFC emulated card from the plurality of NFC emulated cards in an activated state based on the first identifier, where the first NFC emulated card is associated with the first identifier.

And S1204, the terminal equipment executes a first task based on the first NFC analog card.

S1205, the terminal equipment sends the execution result of the first task to the first card reading equipment.

Therefore, when the user uses the terminal equipment to execute the card swiping operation, the terminal equipment can directly select the first NFC analog card from the plurality of NFC analog cards in the activated state to conduct NFC transaction, the card does not need to be switched, the card swiping time is reduced, and the card swiping success rate is improved.

The first NFC protocol parameter may be a non-contact parameter in the foregoing embodiment, and the first value may be a system-level non-contact parameter in the foregoing embodiment.

In one possible implementation, the terminal device is in a powered off state.

In a possible implementation manner, the method further comprises the step that the terminal equipment displays a first user interface of the first application, wherein the first user interface comprises M NFC analog cards which are opened by the terminal equipment through the first application, M is a positive integer greater than 1, and at least 2 NFC analog cards in an activated state are included in the M NFC analog cards.

The terminal device provided by the embodiment of the application can run an Operating System (OS), which can be various Operating systems applied in the current industry, such as an Operating System developed based on OpenHarmony, for example HarmonyOS, or other Operating systems such as an Android mobile Operating System, various open-source Operating systems or derivative Operating systems thereof, such as a Linux OS, other embedded Operating systems and the like, and also can be a future novel Operating System, such as an AI Operating System based on artificial intelligence. An operating system is a set of interrelated system software programs that manage and control the operation, deployment and execution of hardware, software resources, and provide common services for organizing user interactions by a terminal device. The operating system is in a position of being up and down in the terminal equipment, is downwards connected with the physical equipment of the hardware layer, and provides an operating environment for the application software upwards.

The operating system may generally include a kernel layer, a middleware layer, and an application layer, which includes applications, which may include system applications and third party applications. The middleware layer is a series of software or framework that provides various services to application developers, for providing various services such as databases, multimedia and graphics, or for providing various capabilities such as distributed scheduling, system expansion, etc. The middleware layer may also be roughly divided into a framework layer and/or a system service layer, for example. The framework layer provides an application programming interface (application programming interface, API) and programming framework for the application programs of the application layer. The system service layer includes a set of core capabilities of the system, and provides services to applications through the framework layer. The kernel layer is a layer between hardware and software. The kernel layer may include a hardware driver and an operating system kernel. The kernel layer provides hardware drive and also supports functions such as memory management, system process management and the like.

The types and the forms of the terminal equipment used in the daily life are different, and the applied scenes of the terminal equipment are very wide, so that the operating systems applied to the terminal equipment can be different based on the forms and the functions of the different terminal equipment, different application scenes and different user requirements, and the operating systems have commonalities and respective characteristics, and the user experience, the application ecology and the system performance are influenced by the different operating systems. The basic functions realized by the terminal equipment provided by the application can be realized by a general operating system or a special operating system. For more clarity of description of implementation of the embodiments of the present application under a specific operating system, the following illustrates HarmonyOS architectures, from which those skilled in the art can derive implementation of the embodiments of the present application under other specific operating systems, such as implementation under an Android operating system.

Fig. 13 illustrates a software structure of a terminal device according to an embodiment of the present application.

As shown in fig. 13, the software architecture of the terminal device may be divided into several layers, in some embodiments, a kernel layer, a system service layer, a framework layer, and an application layer, which are sequentially from bottom to top, and the layers are communicated through software interfaces. The system functions can be cut, added or combined according to the granularity of the subsystems under the deployment scenes of different equipment forms, and the interior of each subsystem can be cut, added or combined according to the granularity of the functions.

The kernel abstraction layer (KAL, kernel Abstract Layer) provides basic kernel capabilities to upper layers, including but not limited to, for process/thread management, memory management, file system, network management, peripheral management, etc., by masking multi-kernel differences.

And the kernel subsystem supports the selection of proper OS kernels aiming at different resource-constrained devices, and is not limited to Linux kernels, meng Nahe, liteOS and the like.

The driving subsystem, the driving framework is the ecologically opened foundation of the system hardware, and provides unified peripheral access capability and driving development and management framework. The driving frame comprises a display driver, a camera driver, an audio driver, a Bluetooth driver, a sensor driver and the like.

The system service layer includes a set of core capabilities of the system, and provides services to applications through the framework layer. This layer includes a set of subsystems, but is not limited to the following:

The system basic capability subsystem set provides basic capability for running, scheduling, migrating and other operations of the distributed application on multiple devices, and can comprise a distributed soft bus, distributed data management, distributed task scheduling, compiling/running device, a multimode input subsystem, a graphics subsystem, a security subsystem, an AI subsystem and the like.

A basic set of software services subsystems that provide common, generic software services, e.g., event notification subsystems, telephony services subsystems, multimedia subsystems, etc.

The enhanced software services subsystem set provides differentiated capability enhanced software services for different devices, which may include, for example, a smart screen proprietary services subsystem, a wearable proprietary services subsystem, an IoT proprietary services subsystem, and the like.

The set of hardware service subsystems, providing hardware services, may include, for example, a location service subsystem, a user IAM (IDENTITY AND ACCESS MANAGEMENT, unified identity and access management) subsystem, a wearable proprietary hardware service subsystem, a biometric identification, ioT proprietary hardware service, etc. subsystem, etc.

The distributed task scheduling can realize distributed service management (discovery, synchronization, registration, call) and support operations such as remote starting, remote call, remote connection, migration and the like on the application of the cross-equipment.

Distributed data management may enable full-scene, inter-device data synchronization, data storage, data sharing, and data access functions.

The distributed soft bus provides communication-related capabilities for seamless interconnection between multiple devices, including WLAN service capabilities, bluetooth service capabilities, soft bus, interprocess communication RPC (Remote Procedure Call), and the like.

The compiler/runner is a unified compilation runtime platform designed to support the joint compilation and running of multiple programming languages, multiple chip platforms. For example, the compiler/operator may be a ark compiler (ArkCompiler).

The framework layer provides application programming interfaces (application programming interface, APIs) and programming frameworks for application programs of the application layer, e.g., UI framework modules (UI framework modules provide complete infrastructure for UI development of system applications, including UI functions such as components, layout, animation, and interactive events, etc., as well as real-time interface preview tools), user program frameworks, ability frameworks (Ability is a lightweight application, ability frameworks schedule and manage the operation and lifecycle of Ability). The operating systems that different devices carry may vary, as may the APIs supported by them.

HarmonyOS API is a set of open capabilities provided to support HarmonyOS application development. HarmonyOS API may be provided in the frame layer or may be provided separately from the frame layer. Such as Audio API (Audio service), push API (Push service), account API (Account service), etc.

The application layer may include applications (or applications) in the terminal device including, but not limited to, desktop, business management, settings, phone, short messages, mail, social, memo, calendar, contacts, shopping, and the like.

The service management may be an application program (e.g. wallet application program) installed on the terminal device 100, as a service initiator, may be used to accept a card opening request of a user, write an Applet of one or more NFC analog cards and card data thereof into the security chip, may be used to send system-level non-contact parameters and values thereof to the security chip during the card opening process, may be used to trigger the security chip to activate the Applet of one or more opened NFC analog cards, and so on.

For specific functions of the service management application, reference may be made to the related descriptions in the foregoing embodiments, which are not repeated herein.

It should be noted that, the name of the service management application is only a word used in the embodiments of the present application, and the meaning of the term is already described in the embodiments of the present application, and the name of the term should not be construed as limiting the embodiments of the present application.

The following describes a structure of a server provided by an embodiment of the present application.

Fig. 14 exemplarily shows a structure of a server provided by an embodiment of the present application.

As shown in fig. 14, the server 200 may include one or more processors 1401, memory 1402, a communication interface 1403, a transmitter 1405, a receiver 1406, a coupler 1407, and an antenna 1408. These components may be connected by a bus 1404 or other means, fig. 14 being an example of a connection via a bus. Wherein:

the communication interface 1403 may be used for the server 200 to communicate with other devices, such as the terminal device 100, etc. Specifically, the communication interface 1403 may be a 3G communication interface, a 4G communication interface, a 5G communication interface, or a communication interface of a new air interface in the future. Not limited to a wireless communication interface, the server 200 may also be configured with a wired communication interface 1403, such as a local access network (local access network, LAN) interface. The transmitter 1405 may be used to perform transmission processing on the signal output from the processor 1401. The receiver 1406 may be used for receiving the mobile communication signals received by the antenna 1408.

In some embodiments of the application, the transmitter 1405 and the receiver 1406 may be considered as one wireless modem. In the server 200, the number of transmitters 1405 and receivers 1406 may each be one or more. The antenna 1408 may be used to convert electromagnetic energy in a transmission line to electromagnetic waves in free space or to convert electromagnetic waves in free space to electromagnetic energy in a transmission line. The coupler 1407 is used to divide the mobile communication signal received by the antenna 1408 into a plurality of channels and distributes the channels to the plurality of receivers 1406.

Memory 1402 is coupled to processor 1401 for storing various software programs and/or sets of instructions. In particular, memory 1402 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 1402 may store network communication programs that may be used to communicate with one or more additional devices, one or more terminal devices, and one or more network devices.

In some embodiments of the present application, the memory 1402 may be used to store a program for implementing the card management method provided by one or more embodiments of the present application on the server 200 side.

The processor 1401 may be used to read and execute computer readable instructions. In particular, the processor 1401 may be configured to invoke a program stored in the memory 1402, for example, a program for implementing the card management method provided by one or more embodiments of the present application on the server 200 side, and execute instructions contained in the program.

It should be noted that the server 200 shown in fig. 14 is only one implementation manner of the embodiment of the present application, and in practical application, the server 200 may further include more or fewer components, which is not limited herein.

For more details on the function and working principle of the server 200, reference may be made to the relevant content in the above embodiments, which is not described here again.

The hardware structure of the terminal device provided by the embodiment of the application is described below.

Fig. 15 exemplarily shows a hardware structure of a terminal device provided in an embodiment of the present application.

As shown in fig. 15, the terminal device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (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, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display 194, a subscriber identity module (subscriber identification module, SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It will be appreciated that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the terminal device. In other embodiments of the application, the terminal device may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (IMAGE SIGNAL processor, ISP), a controller, a memory, a video codec, a digital signal processor (DIGITAL SIGNAL processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can be a neural center and a command center of the terminal equipment. The controller can generate operation control signals based on the instruction operation codes and the time sequence signals to complete the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-INTEGRATED CIRCUIT, I2C) interface, an integrated circuit built-in audio (inter-INTEGRATED CIRCUIT SOUND, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

The I2C interface is a bi-directional synchronous serial bus comprising a serial data line (SERIAL DATA LINE, SDA) and a serial clock line (derail clock line, SCL). In some embodiments, the processor 110 may contain multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, charger, flash, camera 193, etc., respectively, through different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through an I2C bus interface to implement a touch function of the terminal device.

The I2S interface may be used for audio communication. In some embodiments, the processor 110 may contain multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through the I2S interface, to implement a function of answering a call through the bluetooth headset.

The MIPI interface may be used to connect the processor 110 to peripheral devices such as a display 194, a camera 193, and the like. The MIPI interfaces include camera serial interfaces (CAMERA SERIAL INTERFACE, CSI), display serial interfaces (DISPLAY SERIAL INTERFACE, DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement a photographing function of the terminal device. The processor 110 and the display 194 communicate via a DSI interface to implement the display function of the terminal device.

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

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge a terminal device, or may be used to transfer data between the terminal device and a peripheral device. And can also be used for connecting with a headset, and playing audio through the headset. The interface may also be used to connect other terminal devices, such as AR devices, etc.

It should be understood that the connection relationship between the modules illustrated in the embodiment of the present application is only illustrative, and does not limit the structure of the terminal device. In other embodiments of the present application, the terminal device may also use different interfacing manners in the foregoing embodiments, or a combination of multiple interfacing manners.

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

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.

The wireless communication function of the terminal device may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the terminal device may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example, the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G or the like applied on a terminal device. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (WIRELESS FIDELITY, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation SATELLITE SYSTEM, GNSS), frequency modulation (frequency modulation, FM), near field communication (NEAR FIELD communication, NFC), infrared (IR), etc. applied on the terminal device. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

In some embodiments, the antenna 1 of the terminal device is coupled to the mobile communication module 150 and the antenna 2 is coupled to the wireless communication module 160 so that the terminal device can communicate with the network and other devices through wireless communication technology. The wireless communication techniques can include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (GENERAL PACKET radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation SATELLITE SYSTEM, GLONASS), a beidou satellite navigation system (beidou navigation SATELLITE SYSTEM, BDS), a quasi zenith satellite system (quasi-zenith SATELLITE SYSTEM, QZSS) and/or a satellite based augmentation system (SATELLITE BASED AUGMENTATION SYSTEMS, SBAS).

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

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a Liquid Crystal Display (LCD) CRYSTAL DISPLAY, an organic light-emitting diode (OLED), an active-matrix organic LIGHT EMITTING diode (AMOLED), a flexible light-emitting diode (FLED), miniled, microLed, micro-oLed, a quantum dot LIGHT EMITTING diode (QLED), or the like. In some embodiments, the terminal device may include 1 or N display screens 194, N being a positive integer greater than 1.

In the embodiment of the present application, the terminal device may display one or more activated NFC emulated cards and one or more opened NFC emulated cards through the display screen 194.

The terminal device may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to realize expansion of the memory capability of the terminal device. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store computer executable program code including instructions. The processor 110 executes various functional applications of the terminal device and data processing by executing instructions stored in the internal memory 121. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the terminal device (such as audio data, phonebook, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like.

The terminal device may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The terminal device can listen to music through the speaker 170A or listen to hands-free calls.

A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When the terminal device picks up a call or voice message, the voice can be picked up by placing the receiver 170B close to the human ear.

Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The terminal device may be provided with at least one microphone 170C. In other embodiments, the terminal device may be provided with two microphones 170C, and may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the terminal device may be further provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the source of sound, implement directional recording functions, etc.

The earphone interface 170D is used to connect a wired earphone. The earphone interface 170D may be a USB interface 130 or a 3.5mm open mobile terminal platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The terminal device determines the strength of the pressure based on the change in capacitance. When a touch operation is applied to the display 194, the terminal device detects the intensity of the touch operation based on the pressure sensor 180A. The terminal device may also calculate the position of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example, when a touch operation with a touch operation intensity smaller than a first pressure threshold is applied to the short message application icon, an instruction to view the short message is executed. And executing an instruction for newly creating the short message when the touch operation with the touch operation intensity being greater than or equal to the first pressure threshold acts on the short message application icon.

The touch sensor 180K, also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the terminal device at a different location than the display 194.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The terminal device may receive key inputs, generating key signal inputs related to user settings of the terminal device and function control.

The motor 191 may generate a vibration alert. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects by touching different areas of the display screen 194. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch shock feedback effect may also support customization.

The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be contacted and separated from the terminal device by inserting the SIM card interface 195 or extracting it from the SIM card interface 195. The terminal device may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support Nano SIM cards, micro SIM cards, and the like. The same SIM card interface 195 may be used to insert multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The terminal equipment interacts with the network through the SIM card to realize the functions of communication, data communication and the like. In some embodiments, the terminal device employs an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the terminal device and cannot be separated from the terminal device.

It should be understood that the terminal device shown in fig. 15 is only one example, and that the terminal device may have more or fewer components than shown in fig. 15, may combine two or more components, or may have a different configuration of components. The various components shown in fig. 15 may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

The embodiment of the application provides a chip system, which comprises a processor and a memory, wherein the processor is coupled with the memory, and the memory is used for storing programs or instructions, and when the programs or instructions are executed by the processor, the chip system realizes the method in any method embodiment.

Alternatively, the processor in the system-on-chip may be one or more. The processor may be implemented in hardware or in software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general purpose processor, implemented by reading software code stored in a memory.

Alternatively, the memory in the system-on-chip may be one or more. The memory may be integral with the processor or separate from the processor, and embodiments of the present application are not limited. The memory may be a non-transitory processor, such as a ROM, which may be integrated on the same chip as the processor, or may be separately provided on different chips, and the type of memory and the manner of providing the memory and the processor are not particularly limited in the embodiments of the present application.

Illustratively, the chip system may be a field programmable gate array (field programmable gatearray, FPGA), an Application Specific Integrated Chip (ASIC), a system on chip (SoC), a central processing unit (centralprocessor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (DIGITAL SIGNAL processor, DSP), a microcontroller (micro controllerunit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chip.

It should be understood that the steps in the above-described method embodiments may be accomplished by integrated logic circuitry in hardware in a processor or instructions in the form of software. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Drive (SSD)), etc.

Those of ordinary skill in the art will appreciate that implementing all or part of the above-described method embodiments may be accomplished by a computer program to instruct related hardware, the program may be stored in a computer readable storage medium, and the program may include the above-described method embodiments when executed. The storage medium includes a ROM or a random access memory RAM, a magnetic disk or an optical disk, and other various media capable of storing program codes.

The foregoing embodiments are merely for illustrating the technical solution of the present application, but not for limiting the same, and although the present application has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that modifications may be made to the technical solution described in the foregoing embodiments or equivalents may be substituted for parts of the technical features thereof, and such modifications or substitutions do not depart from the spirit of the corresponding technical solution from the scope of the technical solution of the embodiments of the present application.

Claims

1. A card management method, applied to a terminal device, comprising:

the terminal equipment is close to first card reading equipment supporting a first near field communication NFC analog card;

the terminal equipment receives a first identifier sent by the first card reading equipment;

the terminal equipment selects a first NFC analog card from a plurality of NFC analog cards in an activated state based on the first identifier, wherein the first NFC analog card is associated with the first identifier;

The terminal equipment executes a first task based on the first NFC analog card;

and the terminal equipment sends the execution result of the first task to the first card reading equipment.

2. The method of claim 1, wherein the terminal device opens M NFC emulated cards, and some or all of the M NFC emulated cards are in an active state, where the NFC emulated cards in the active state include the first NFC emulated card and the second NFC emulated card.

3. The method according to claim 2, wherein the method further comprises:

The terminal equipment is close to second card reading equipment supporting the second NFC analog card;

the terminal equipment receives a second identifier sent by the second card reading equipment;

The terminal equipment selects a second NFC analog card from the NFC analog cards in the activated state based on the second identification, wherein the second NFC analog card is associated with the second identification;

the terminal equipment executes a second task based on the second NFC analog card;

The terminal equipment sends an execution result of the second task to the second card reading equipment;

Wherein the second identifier and the first identifier are different.

4. A method according to claim 3, characterized in that the first NFC emulated card is still in an active state after the terminal device has selected the second NFC emulated card from the plurality of NFC emulated cards in an active state based on the second identification.

5. The method according to claim 3 or 4, wherein,

Before the terminal device sends the execution result of the second task to the second card reading device, the method further includes:

the terminal equipment sends a first NFC protocol parameter with a first value to the second card reading equipment;

before the terminal device sends the execution result of the first task to the first card reading device, the method further includes:

and the terminal equipment sends the first NFC protocol parameter with the first value to the first card reading equipment.

6. The method of claim 5, wherein the first NFC emulated card and the second NFC emulated card are each activated by the terminal device based on the first NFC protocol parameter of the first value.

7. The method of claim 6, wherein the step of providing the first layer comprises,

Before the terminal device approaches the first card reading device supporting the first near field communication NFC emulated card, the method further includes:

the terminal equipment acquires the first NFC protocol parameter of a second value, and adjusts the first NFC protocol parameter of the second value into the first NFC protocol parameter of the first value;

Before the terminal device approaches a second card reading device supporting the second NFC emulated card, the method further includes:

the terminal equipment acquires the first NFC protocol parameter of a third value, and adjusts the first NFC protocol parameter of the third value into the first NFC protocol parameter of the first value;

the second value is associated with the first NFC emulated card, the third value is associated with the second NFC emulated card, and the second value and the third value are different.

8. The method of claim 7, wherein the first NFC-protocol parameter, the first value, the second value, and the third value are pre-stored on the terminal device or are acquired by the terminal device at a server.

9. The method according to any one of claims 6-8, further comprising:

The terminal equipment updates the first NFC protocol parameter with the first value to the first NFC protocol parameter with a fourth value;

the terminal equipment sends the fourth valued first NFC protocol parameter to the second card reading equipment;

And the terminal equipment sends the first NFC protocol parameter with the fourth value to the first card reading equipment.

10. The method of claim 1 or 2 or 3 or 4 or 6 or 7 or 8, further comprising:

the terminal equipment displays a first user interface, wherein the first user interface comprises the plurality of NFC analog cards in an activated state.

11. The method according to claim 7 or 8, wherein the terminal device comprises a security chip,

The terminal device adjusts the first NFC protocol parameter of the second value to the first NFC protocol parameter of the first value, and specifically comprises that the security chip adjusts the first NFC protocol parameter of the second value to the first NFC protocol parameter of the first value;

The terminal device adjusts the first NFC protocol parameter of the third value to the first NFC protocol parameter of the first value, and specifically comprises the security chip adjusting the first NFC protocol parameter of the third value to the first NFC protocol parameter of the first value.

12. The method of claim 11, wherein the terminal device further comprises a first application,

Before the secure chip adjusts the first NFC protocol parameter of the second value to the first NFC protocol parameter of the first value, the method further includes the first application sending a first message to the secure chip, where the first message is used to instruct the secure chip to adjust the first NFC protocol parameter of the second value to the first NFC protocol parameter of the first value;

before the secure chip adjusts the third valued first NFC protocol parameter to the first valued first NFC protocol parameter, the method further includes the first application sending a second message to the secure chip, where the second message is used to instruct the secure chip to adjust the third valued first NFC protocol parameter to the first valued first NFC protocol parameter.

13. The method of claim 12, wherein the terminal device further comprises an NFC chip, an NFC service module, the method further comprising:

the NFC service module sends the first NFC protocol parameter with the first value to the NFC chip;

the NFC chip stores the first NFC protocol parameter of the first value;

The terminal device sends a first NFC protocol parameter of a first value to the second card reading device, and specifically comprises that the NFC chip sends the first NFC protocol parameter of the first value to the second card reading device;

The terminal device sends the first NFC protocol parameter of the first value to the first card reading device, and specifically comprises that the NFC chip sends the first NFC protocol parameter of the first value to the first card reading device.

14. The method of claim 6 or 7 or 8 or 12 or 13, wherein the first NFC protocol parameters include one or more of a unique identifier UID, a request response SAK for a SELECT command, a request response ATQA for a REQA command, a history byte ATS History Bytes for SELECT responses, a frame latency and startup frame guard time FWI, an SFGI, a supported card identifier field CID Support, a maximum Data transfer Rate Max Data Rate.

15. A method according to claim 1 or 2 or 3 or 4 or 6 or 7 or 8 or 12 or 13, characterized in that the terminal device is in a power-off state.

16. A card management method, applied to a terminal device, comprising:

The terminal equipment displays a first user interface of a first application, wherein the first user interface comprises M NFC analog cards which are opened by the terminal equipment through the first application, M is a positive integer greater than 1, and the M NFC analog cards comprise at least 2 NFC analog cards in an activated state.

17. The method of claim 16, wherein the at least 2 NFC emulated cards in an active state include a first NFC emulated card, the method further comprising, prior to the first NFC emulated card being in an active state:

the terminal equipment opens the first NFC analog card;

and the terminal equipment detects the operation of confirming the activation of the first NFC analog card by a user, and responds to the operation, the terminal equipment activates the first NFC analog card.

18. The method of claim 16, wherein the at least 2 NFC emulated cards in an active state include a second NFC emulated card, the method further comprising, prior to the second NFC emulated card being in an active state:

And the terminal equipment opens the second NFC analog card and automatically activates the second NFC analog card.

19. The method of claim 18, wherein the second NFC emulated card is an NFC emulated card that conforms to a preset rule, the preset rule including one or more of a priority of a service corresponding to the second NFC emulated card being higher than a first threshold, the second NFC emulated card being one of a first X NFC emulated cards that have been opened in the terminal device, the X being a positive integer that is less than or equal to a second threshold.

20. An electronic device comprising one or more processors and one or more memories, wherein the one or more memories are coupled to the one or more processors, the one or more memories to store computer program code comprising computer instructions that, when executed by the one or more processors, cause the electronic device to perform the method of any of claims 1-15 or 16-19.

21. A computer storage medium storing a computer program comprising program instructions which, when run on an electronic device, cause the electronic device to perform the method of any one of claims 1-15 or 16-19.

22. A computer program product, characterized in that the computer program product, when run on a computer, causes the computer to perform the method of any of claims 1-15 or 16-19.