CN113553870B

CN113553870B - NFC tag identification method and device, NFC equipment and storage medium

Info

Publication number: CN113553870B
Application number: CN202110820786.1A
Authority: CN
Inventors: 王大耀
Original assignee: Shenzhen Goodix Technology Co Ltd
Current assignee: Shenzhen Goodix Technology Co Ltd
Priority date: 2021-07-20
Filing date: 2021-07-20
Publication date: 2022-09-27
Anticipated expiration: 2041-07-20
Also published as: CN113553870A; WO2023000774A1

Abstract

The embodiment of the invention provides an NFC label identification method, an NFC label identification device, NFC equipment and a storage medium. The label identification method comprises the following steps: when the identification of the last tag in the external tags is completed according to an NFC tag anti-collision mechanism, acquiring the current tag collision state of the external tags; if the current tag collision state indicates that tag collision is not detected in the external tags currently, sending a tag silent request to the identified previous tag, wherein the tag silent request is used for enabling the tag which is identified to enter a silent state; sending a tag discovery request, wherein the tag discovery request is used for discovering tags which are not in the silent state in the external tags; and if a response of the current tag to the tag discovery request is received, identifying the current tag according to the NFC tag anti-collision mechanism. The scheme of the embodiment of the invention improves the identification accuracy and reliability of the external label.

Description

NFC label identification method and device, NFC equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to an NFC tag identification method and device, NFC equipment and a storage medium.

Background

In Near Field Communication (NFC) technology, according to the specification of NFC forum, an organization that sets up NFC Communication protocol, an NFC device may implement Communication in a passive Communication mode, an active Communication mode or a peer-to-peer mode.

The digital specification of NFC forum specifies: in the active communication mode, the NFC reader-writer can transmit a radio frequency field for tag identification, and an external tag receiving the radio frequency field returns tag information carried by the external tag to the NFC reader-writer in a load modulation mode. When a plurality of tags return tag information to the NFC reader, the NFC reader can identify the plurality of tags which conflict with one another outside according to an NFC tag anti-collision mechanism.

However, there are still situations where the identification of the external tag is not accurate.

Disclosure of Invention

In view of the above, one of the technical problems to be solved by the embodiments of the present invention is to provide an NFC tag identification method, an apparatus, an NFC device, and a storage medium.

According to a first aspect of the embodiments of the present invention, there is provided an NFC tag identification method, including: when the identification of the last tag in the external tags is completed according to an NFC tag anti-collision mechanism, acquiring the current tag collision state of the external tags; if the current tag collision state indicates that tag collision is not detected in the external tags currently, sending a tag silent request to the identified previous tag, wherein the tag silent request is used for enabling the tag which is identified to enter a silent state; sending a tag discovery request, wherein the tag discovery request is used for discovering tags which are not in the silent state in the external tags; and if a response of the current tag to the tag discovery request is received, identifying the current tag according to the NFC tag anti-collision mechanism.

According to a second aspect of the embodiments of the present invention, there is provided an NFC tag identification apparatus including: the device comprises an acquisition module, a collision detection module and a collision detection module, wherein the acquisition module acquires the current tag collision state of an external tag when the identification of a previous tag in the external tag is completed according to an NFC tag anti-collision mechanism; a first sending module, configured to send a label silencing request to an identified previous label if the current label collision status indicates that a label collision is not currently detected in the external label, where the label silencing request is used to enable a label that has completed identification to enter a silencing state; a second sending module, configured to send a tag discovery request, where the tag discovery request is used to discover a tag that is not in the silent state in the external tags; and the judging module is used for identifying the current tag according to the NFC tag anti-collision mechanism if receiving the response of the current tag to the tag discovery request.

According to a third aspect of embodiments of the present invention, there is provided an NFC device including: one or more processors, a communication interface, a memory and a communication bus through which the one or more processors, the communication interface, the memory communicate with each other, and one or more programs stored in the memory and configured to be executed by the one or more processors to perform the method according to the first aspect.

According to a fourth aspect of embodiments of the present invention, there is provided a computer storage medium comprising a stored program, wherein a device comprising the storage medium is controlled to perform the method according to the first aspect when the program is run.

In the scheme of the embodiment of the invention, the response of the current tag to the tag discovery request is received to indicate that the current tag is not in the silent state, and in addition, the tags which are completely identified enter the silent state through the indication of the tag silent request to further indicate that the current tag is not completely identified, so that the scheme of the embodiment of the invention can discover and identify the current tag which is not completely identified under the condition that tag collision is not detected in the external tag currently, the identification accuracy and reliability of the external tag are improved, and the situation that the tags which are collided cannot be identified completely under the condition that the tag collision is not detected in the external tag but the tag collision actually exists is avoided.

Drawings

Some specific embodiments of the present invention will be described in detail hereinafter, by way of illustration and not limitation, with reference to the accompanying drawings. The same reference numbers in the drawings identify the same or similar elements or components. Those skilled in the art will appreciate that the drawings are not necessarily drawn to scale. In the drawings:

fig. 1A is a schematic diagram illustrating a tag identification principle based on an NFC tag anti-collision mechanism according to a typical example;

fig. 1B is a schematic flow chart of the tag identification method based on the NFC tag anti-collision mechanism of fig. 1A;

fig. 2 is a schematic flow chart of an NFC tag identification method according to an embodiment of the present invention;

fig. 3 is a schematic interaction diagram of an NFC tag identification method according to another embodiment of the present invention;

fig. 4 is a schematic flow chart of an NFC tag identification method according to another embodiment of the present invention;

fig. 5 is a schematic flow chart of an NFC tag identification method according to another embodiment of the present invention;

fig. 6 is a schematic block diagram of an NFC tag identification apparatus according to another embodiment of the present invention; and

fig. 7 is a schematic diagram of an NFC device according to another embodiment of the present invention.

Detailed Description

The following further describes concrete implementation of the embodiment of the invention by combining the drawings of the embodiment of the invention. It should be understood that the NFC device or the electronic device equipped with the NFC function may be widely applied in the fields of entrance guard, bus, mobile payment, smart poster, data transmission, and the like. For example, the NFC device may be implemented as a contactless smart card (IC card), such as a bank card, a bus card, an access card, and specifically, the NFC controller and the secure element unit included in the mobile phone terminal may be used to implement simulation of the contactless smart card, such as the bank card, the bus card, and the access card, in cooperation with a software system. NFC devices may also be implemented as POS machines, card readers, and the like. NFC devices may also be implemented as Internet of things (IOT) devices.

In order to better implement the above functions and scenarios, NFC forum has formulated various NFC specifications. The Digital specification specifies the encoding format, modulation mode, transmission rate, frame format, transmission protocol and command set of the three technologies of NFC-A, NFC-B and NFC-F. The NFC reader-writer sends a radio frequency electromagnetic field carrying information to the NFC tag, and the NFC tag carries out load modulation on the radio frequency electromagnetic field so as to send data to the NFC reader-writer. For example, for NFC-a and NFC-B technologies, the carrier frequency fc of the load modulation is used to generate the subcarrier fs fc/16 (about 847 kHz). The NFC tag as a listening device indicates bit information of the return data starting at the rising or falling edge of the subcarrier.

Specifically, in the NFC-a technology, an NFC reader can transmit a radio frequency field for tag identification, and an external tag that receives the radio frequency field returns tag information carried by the external tag to the NFC reader in a load modulation manner. The NFC reader detects bit information for each bit of the tag information. When a plurality of different bit information are detected aiming at the same bit, the NFC reader judges that a plurality of tags to be identified which conflict with each other exist outside, and sends a polling instruction through an NFC tag anti-collision mechanism to distinguish the plurality of different bit information and identify the tags.

More specifically, the identification process based on the NFC tag anti-collision mechanism will be specifically described below with reference to fig. 1A and 1B, where fig. 1A shows an NFC tag identification principle of a typical example, and fig. 1B shows a schematic flow of an NFC tag identification method. As shown in fig. 1A, when receiving the radio frequency field, the tag a returns tag information 10101010 with 8 bits by means of load modulation, and the tag B returns tag information 10111010 with 8 bits by means of load modulation. The NFC reader detects bit information for the 8 bits, respectively, and if the bit information corresponding to the same bit in the tag information of each of the tag a and the tag B is identical, the NFC reader detects the bit information of the bit as type D (when the bit information corresponding to the same bit is both 1 for both tag information) or type E (when the bit information corresponding to the same bit is both 0 for both tag information). If the bit information corresponding to the same bit in the tag information of each of the tag a and the tag B is not consistent, the NFC reader may determine that different pieces of bit information exist corresponding to the same bit, in other words, the NFC reader may determine that there is conflicting bit information corresponding to the same bit. In this case, the NFC reader recognizes the bit information of the bit as type C, for example, the tag information of tag a and tag B correspond to bit information of the fourth bit as 0 and 1, respectively, i.e., collision bit information is formed, and thus the NFC reader recognizes the bit information of the fourth bit as type C.

In the NFC specification, an NFC reader determines whether a plurality of colliding tags are to be identified according to whether there is colliding bit information, and may adopt a tag identification method conforming to the NFC specification as shown in fig. 1B, and identify a plurality of colliding tags, such as tag a and tag B, one by one using a polling message until all colliding tags are identified.

In the NFC tag anti-collision mechanism shown in fig. 1B, an NFC reader (an NFC device in an active communication mode or a read-write mode) sends a polling message (a sense _ REQ message or an SDD _ REQ message), and each external NFC tag (for example, tag a and tag B) replies to the polling message of the NFC device at a predetermined time point.

It should be understood that the NFC tag identification method of fig. 1B is only one exemplary NFC tag identification method, and should not be construed as the only tag identification method. In addition, the tag identification method of fig. 1 may be applied between a polling device and a listening device. The polling device may include, but is not limited to, an NFC device, an NFC reader in reader mode. Listening devices include, but are not limited to, NFC devices, NFC tags, RFID tags in card emulation mode. The method of fig. 1 comprises the steps of:

s101: the NFC equipment sends the SENS _ REQ message or the ALL _ REQ message to start identification, and when receiving the SENS _ RES message returned by the tag, the NFC equipment checks b5-b1 in the SENS _ RES message and judges whether the tag supports tag identification of an NFC tag anti-collision mechanism (each tag is identified by detecting collision bit information). And if so, continuously judging whether the tag platform is configured as a type 1 tag platform. If so, executing tag identification of the type 1 tag platform according to an NFC tag anti-collision mechanism, otherwise, executing step 102. And if the tag identification of the NFC tag anti-collision mechanism is not supported, ending the identification process.

S102: the NFC device selects cascade level 1.

S103: the NFC device sets SEL _ CMD and SEL _ PAR bytes in the SDD _ REQ message, and transmits the SDD _ REQ message.

S104: the NFC device receives the SDD _ RES message and determines whether a collision is generated. If yes, go to step S105; otherwise, step S109 is executed.

S105: and the NFC equipment checks the configuration parameters and judges whether to identify the conflict equipment. If yes, go to step S106; otherwise, the execution is finished.

S106: the NFC device recognizes the valid data bit.

S107: the NFC device sets SEL _ PAR, includes a valid data bit after SEL _ PAR, and sets a collision bit to 1, and then transmits SDD _ REQ.

S108: and the NFC equipment receives the SDD _ RES and judges whether a conflict is generated. If a conflict is generated, step S106 is executed; otherwise, step S109 is executed.

S109: the NFC device sends a SEL _ REQ message.

S110: the NFC device receives the SEL _ RES message and determines whether NFCID1 is complete. If complete, execute step S111; otherwise, the cascade level is increased and step S103 is performed.

S111: the NFC device stores NFCID 1.

S112: and the NFC equipment checks the configuration parameters and judges whether to continue the tag identification of the NFC tag anti-collision mechanism. If yes, SLP _ REQ is sent, the previous tag is made to sleep, and SEL _ REQ is sent to execute S101 again to start detection; otherwise, the execution is finished.

However, in some cases, due to implementation differences of a physical layer (e.g., analog layer) of the NFC reader/writer and due to mutual influence of a plurality of tags colliding with each other at the time of load modulation, even if various specifications of NFC forum are satisfied, there may be a case where the type C indicating the colliding bit information cannot be recognized.

In other cases, the NFC reader can also identify Radio Frequency Identification (RFID) tags. Similar to the NFC tag described above, the RFID tag also returns tag information containing bit information through load debugging when receiving the radio frequency field of the NFC reader. However, the load modulation related analog layer design of RFID tags is not always compatible with the NFC specification. In other words, when the NFC reader interacts with an external RFID tag based on the NFC specification, the RFID tag often cannot meet the timing requirements of the NFC specification. For example, the actual time interval between the transmission timing of the SENS _ REQ message (polling message) by the NFC reader and the return timing of the SENS _ RES message (response of polling message) by the RFID tag is larger than the requirement of NFC forum, and in this case, collision bit information between RFID tags and NFC tags which actually collide with each other or collision bit information between a plurality of RFID tags which actually collide with each other cannot be detected, which results in a tag which cannot be identified among a plurality of tags which collide with each other, and the identification reliability of the external tag is poor.

The following describes the NFC tag identification method according to the embodiment of the present invention with reference to fig. 2, so as to improve the identification reliability of the external tag. Fig. 2 illustrates an NFC tag identification method of an embodiment of the present invention. The NFC tag identification method of fig. 2 may be used for an NFC device as a polling device, including:

s210: and when the identification of the last tag in the external tags is completed according to the NFC tag anti-collision mechanism, acquiring the current tag collision state of the external tags.

It should be understood that, before the last tag among the external tags is identified, the NFC device may determine, through the collision bit information, that there is a tag collision in the external tags, and start to identify each of the collided tags by using the NFC tag anti-collision mechanism, where the last tag is the first identified tag among the collided tags. Specifically, when the last tag in the external tags is identified according to the NFC tag anti-collision mechanism, the SDD _ REQ message may be sent, and the last tag may be identified by setting a corresponding parameter in the SDD _ REQ message. More specifically, when performing tag identification, the NFC device may sequentially transmit the SDD _ REQ message in a polling manner for each bit (collision bit) having collision bit information, and for any collision bit, the SDD _ REQ message may specify the bit information on the bit, and temporarily avoid bit information collision, so as to first obtain complete tag information of a tag, i.e., a "previous tag", in a plurality of tags colliding with each other. In other words, with such an anti-collision mechanism, when all bits of the tag information returned by the tag do not have collision bit information, the NFC device can identify all bits of the tag information, and thus identify the tag (previous tag).

It is also understood that the current tag collision state of the external tag may be information indicating whether there are tags that collide with each other, for example, information indicating whether there is collision bit information.

It should also be understood that this collision identification of the external tag may be started by sending a tag wakeup request (e.g., an ALL _ REQ message in the NFC specification), where the tag wakeup request is used to wake up ALL tags in a silent state (i.e., including the identified tags), and the ALL tag discovery request may also be used to initiate collision identification of the external tag again after the current identification of the external tag is finished.

S220: and if the current tag collision state indicates that tag collision exists in the external tags which are not detected currently, sending a tag silent request to the identified last tag, wherein the tag silent request is used for enabling the tag which is identified to enter a silent state.

It should be understood that the tag mute request herein can enable the tag that has completed identification to enter a mute state, and specifically, the tag mute request may be an SLP _ REQ message in the NFC specification, where the SLP _ REQ message is a message that can implement mute control on the last tag that has been identified without response.

It is also understood that it may be determined whether the current tag collision status indicates that no tag collision is currently detected in the external tag, for example, whether a tag collision is detected may be determined according to whether the information indicating the current tag collision status includes any detected collision bit information, if any collision bit information is detected, it is determined that a tag collision is detected, and if no collision bit information is detected, it is determined that a tag collision is detected.

S230: and sending a label discovery request, wherein the label discovery request is used for discovering the labels which are not in the silent state in the external labels.

It should be understood that the tag discovery request in this document can discover a tag that is not in a silent state in an external tag, and the tag discovery request may be a SENS _ REQ message in the NFC specification. Specifically, the SENS _ REQ message can discover tags that are not in the silent state among the external tags without performing wakeup on the tags that have completed identification and are in the silent state. In other words, a tag that has completed identification in a silent state may be considered to have no response to a tag discovery request.

S240: and if the response of the current tag to the tag discovery request is received, identifying the current tag according to an NFC tag anti-collision mechanism.

It should be understood that receipt of the current tag's response to the tag discovery request indicates that the current tag is different from, in other words, indicates that the current tag conflicts with, a previously identified tag. The current tag is identified according to an anti-collision mechanism of the NFC tag, the current tag can be updated to be the last tag for identification, and in other words, the current tag is identified in a mode of identifying the last tag.

Specifically, when the NFC device performs tag identification on three tags a (10101010), B (10111010), and C (10101011) that actually collide, the NFC device detects

collision bit information

0 and 1 of the 4 th bit between tag a and tag B, determines that tag a and tag B collide with each other, and does not detect collision bit information of the 8 th bit between tag C and tag a or tag B, and therefore the NFC device starts identification of one of tag a and tag B that collide with each other, and the NFC device first detects tag a by transmitting an SDD _ REQ message to specify that the 4 th bit is 0, and brings tag a into a silent state. Then, by designating the 4 th bit as 1, the tag B (corresponding to the previous tag in the text) is detected, and thus the collision detection of the collision bit is completed. After the identification of tag B (equivalent to "last tag" in this document) is completed, the conventional flow considers that there is no more conflicting bit information. But since the 8 th bit collision between tag C and tag a cannot be detected, after bringing tag B into the silent state, tag C can still respond to the tag discovery request because it does not complete the identification, thus discovering tag C and identifying tag C as the next tag (i.e., the current tag) of the "previous tag". The conventional NFC tag anti-collision mechanism can be adopted for the tag C identification mode, and if no tag C has other tags with collision bit information, the tag information of the tag C can be directly identified by utilizing the process of the NFC tag anti-collision mechanism.

In the scheme of the embodiment of the invention, the received response of the current label to the label discovery request indicates that the current label is not in the silent state, and in addition, the labels which are completely identified enter the silent state through the indication of the label silent request, and further indicate that the current label is not completely identified, so that the scheme of the embodiment of the invention can discover and identify the current label which is not completely identified under the condition that label conflict exists in the external label, the identification accuracy and reliability of the external label are improved, and the condition that the label conflict does not exist in the external label but label conflict actually exists and the like is avoided, and the labels which conflict cannot be identified completely.

In other words, if the tag information of the current tag is the same as the previously recognized tag information (e.g., the last tag or an earlier recognized tag), the current tag will enter the mute state via the tag mute request without responding to the tag discovery request, and if the current tag is different from the previously recognized tag, the current tag and the previous tag belong to tags that actually collide with each other, and thus although the current tag collision state indicates that there is no tag collision among the external tags currently detected, the current tag is still discovered by the scheme of the embodiment of the present invention, and thus recognized.

It should be understood that, in the anti-collision mechanism specified by the existing protocol, the tag silence request (e.g., SLP _ REQ message) is sent when tag collision is detected in the external tag, whereas in the scheme of the embodiment of the present invention, the tag silence request is sent when tag collision is not detected in the external tag, and therefore the sending timing of the tag silence request in the scheme of the present invention is completely different from that of the conventional tag silence request.

In addition, the label silent request and the label discovery request in the label identification method of the embodiment of the invention can be consistent with the action of the conventional label silent request, thereby realizing backward compatibility to the existing protocol.

In addition, the mode of identifying a tag according to the NFC tag anti-collision mechanism in the embodiment of the invention is consistent with the tag identification mode specified by the existing protocol, so that the backward compatibility of the existing protocol is realized.

As another implementation manner of the present invention, if a response of the current tag to the tag discovery request is not received, the identification of the external tag is ended. Therefore, the implementation mode has more accurate and reliable judgment standard for judging whether the label conflict exists than the current label conflict state.

As another implementation manner of the present invention, if the current tag collision status indicates that a tag collision is not currently detected in the external tags, sending a tag muting request to an identified previous tag includes: if the current tag conflict state indicates that tag conflict is not detected in the external tags currently, judging whether to start to execute extended tag identification; if yes, sending a label silencing request to the identified last label. In this implementation, extended tag identification may be an alternative option, and flexibility of tag identification is achieved with the above-described simple configuration. In other words, when high recognition accuracy and reliability are required, extended tag recognition may be enabled, and when relatively low recognition accuracy and reliability are required, extended tag recognition may be disabled.

As another implementation manner of the present invention, if the current tag collision status indicates that a tag collision is not currently detected in the external tags, sending a tag muting request to an identified previous tag, further includes: and if the extended tag identification is not executed, ending the identification of the external tag. Based on such a configuration, a more reliable and accurate judgment is achieved for the current tag. In other words, the accuracy and the reliability of judging the label conflict are improved, and meanwhile, the flexibility of label identification is guaranteed.

As another implementation manner of the present invention, the tag identification method may further include: and updating the last label by using the current label. Because the label identification process is circularly executed by using an updating means, the simplicity and consistency of the identification process of each label are ensured. In addition, the implementation mode is better compatible with the conventional conflict detection circulation flow.

As another implementation manner of the present invention, the tag identification method may further include: and judging whether the current tag conflict state indicates that the tag conflict exists in the external tags which are not detected currently. Therefore, compatibility and matching with the current label conflict state judgment step in the conventional label identification process are realized.

As another implementation manner of the present invention, the tag identification method may further include: storing the tag information of the last tag identified. Thus, storing the tag information of the last tag identified facilitates subsequent processing based on the identified tag information, e.g., to communicate with the tag. The implementation mode also realizes the compatibility and matching with the label identification step in the conventional label identification process.

As another implementation manner of the present invention, the tag identification method may further include: if a response of the current tag to the tag discovery request is received, identifying the current tag according to the NFC tag anti-collision mechanism, wherein the identification comprises the following steps: if a response of the current tag to the tag discovery request is received, acquiring configuration information included in the response of the current tag; and if the configuration information indicates that the current tag supports the NFC tag anti-collision mechanism, identifying the current tag according to the NFC tag anti-collision mechanism. The implementation mode realizes the compatibility and matching with the configuration parameter support judgment step in the conventional label identification process.

Fig. 3 is a schematic interaction diagram of an NFC tag identification method according to another embodiment of the present invention. Fig. 3 shows a part of the interaction process between the NFC device, the recognized conflicting tag 32 and the unrecognized conflicting tag 33. It should be appreciated that the interaction process of the present example may also include more or fewer parts, and may include alternative steps, based on the various steps shown in fig. 3. In particular, fig. 3 shows the following steps:

s301: the NFC device 31 determines the identity of the identified conflicting tag 32. Specifically, as an example according to the NFC tag anti-collision mechanism, the NFC device 31 may transmit an SDD _ REQ message to the collision tag 32 to identify the collision tag 32. The identification of the identified conflicting tag 32 (an example of tag information) may be stored after the conflicting tag 32 is obtained.

S302: the NFC device 31 does not find the unidentified current tag. Specifically, the NFC device 31 may determine whether the current tag to be identified is detected according to a tag collision state, where the tag collision state indicates that there is no collision bit information, and the NFC device 31 determines that the current tag to be identified is not detected.

S303: the NFC device 31 sends a tag mute request to the identified conflicting tags 32. Specifically, the NFC device 31 may transmit an SLP _ REQ message indicating that the identified conflicting tag 32 enters the silent state in response to the above determination result.

S304: the NFC device 31 transmits a tag discovery request. Specifically, the NFC device 31 transmits a SENS _ REQ message for discovering a tag that is not in a silent state among external tags.

S305: the unrecognized conflicting tag 33 sends a response of the tag discovery request to the NFC device 31. Specifically, the unrecognized collision tag 33 transmits a SENS _ RES message to the NFC device 31 as a response to the SENS _ REQ message. It should be understood that the SENS _ RES message may include configuration parameters whether the target tag supports conflicting tag identification.

S306: the NFC device 31 sends a tag identification message to the unrecognized conflicting tag 33. Specifically, the NFC device 31 may determine, according to the above configuration parameters, that the unrecognized collision tag 33 supports collision tag identification (a bit-oriented anti-collision mechanism in a polling manner), and send a message, for example, an SDD _ REQ message, to the unrecognized collision tag 33, indicating to continue tag identification.

Fig. 4 is a schematic flowchart of an NFC tag identification method according to another embodiment of the present invention.

S410: identification of the last tag in the external tags is performed. Specifically, a message indicating tag identification may be sent to perform collision tag identification with a bit-oriented NFC tag anti-collision mechanism. The identification of the last tag may be stored after the identification of the last tag is completed.

S420: and acquiring the current label collision state of the external label. Specifically, the purpose of acquiring the tag collision status is to determine whether a current tag is to be identified, so as to implement compatibility with a conventional collision tag identification process. Whether the collision bit information of the external tag is detected or not can be judged, if yes, the current tag to be identified is judged, and if not, the current tag not to be identified is judged.

S430: and if the current label collision state indicates that the current label to be identified is not detected, sending a label silencing request to the identified last label. Specifically, when it is determined that the current tag to be identified is not detected according to the tag collision state, an SLP _ REQ message is sent in response to the determination result, where the SLP _ REQ message indicates that the last tag identified enters a silent state.

S440: a tag discovery request is sent. Specifically, a SENS _ REQ message for discovering a tag not in a silent state among external tags may be transmitted to an unrecognized conflicting tag.

S450: and if the response of the current tag to the tag discovery request is received, identifying the current tag. Specifically, the current tag may return a SENS _ RES message to the NFC device as a response to the SENS _ REQ message. It should be understood that the SENS _ RES message may include configuration parameters whether the target tag supports conflicting tag identification.

S460: and updating the unidentified last label by using the current label to be identified. Specifically, tag identification is performed on the current tag in a manner similar to the previous tag. In other words, the collision tag identification process is performed cyclically by means of updating, for example, the current tag can be identified according to the NFC tag anti-collision mechanism.

Fig. 5 is a schematic flowchart of an NFC tag identification method according to another embodiment of the present invention.

S501: upon completion of the identification of the last unidentified tag, the current tag collision status of the external tag is acquired, and then S502 is performed.

S502: is it determined if the current tag collision status indicates that no tag collision was detected? If yes, executing S503; if not, S504 is performed.

S503: is it determined whether extended tag identification is performed? If yes, executing S505; if not, S506 is executed.

S504: and updating the unidentified last label by using the current label to be identified.

S505: a tag mute request is sent to the last tag identified and step S507 is performed. Wherein the tag mute request indicates that the last tag identified entered a mute state.

S506: the identification of the external tag is ended.

S507: a tag discovery request is sent and step S508 is performed. It should be understood that the tag discovery request is used to discover tags in the external tags that are not in the silent state.

S508: judging whether a response of the current tag to the tag discovery request is received, if so, executing step S509; if not, step S510 is performed.

S509: and identifying the current tag according to the NFC tag anti-collision mechanism.

S510: it is determined that there is no current tag to be identified, and the identification of the external tag is ended.

Fig. 6 is a schematic block diagram of an NFC tag identification apparatus according to another embodiment of the present invention. The NFC tag identification device of fig. 6 includes:

the obtaining module 610 obtains a current tag collision state of the external tag when the identification of a previous tag in the external tag according to the NFC tag anti-collision mechanism is completed.

The first sending module 620, if the current tag collision status indicates that tag collision is not currently detected in the external tags, sends a tag silence request to the identified previous tag, where the tag silence request is used to enable the tag that has completed identification to enter a silence state.

A second sending module 630, configured to send a tag discovery request, where the tag discovery request is used to discover tags that are not in the silent state in the external tags.

The identifying module 640 identifies the current tag according to the NFC tag anti-collision mechanism if a response of the current tag to the tag discovery request is received.

As another implementation manner of the present invention, the first sending module is specifically configured to: if the current tag conflict state indicates that tag conflict exists in the external tags which are not detected currently, judging whether to start to execute extended tag identification; if yes, sending a label silence request to the last label identified.

As another implementation manner of the present invention, the identification module is specifically configured to: if a response of the current tag to the tag discovery request is received, acquiring configuration information included in the response of the current tag; and if the configuration information indicates that the current tag supports the NFC tag anti-collision mechanism, identifying the current tag according to the NFC tag anti-collision mechanism.

As another implementation manner of the present invention, the first sending module is further configured to: and if the extended tag identification is not executed, ending the identification of the external tag.

As another implementation of the present invention, the apparatus further includes: and the updating module is used for updating the previous label by using the current label.

As another implementation of the present invention, the apparatus further includes: and the judging module is used for judging whether the current label collision state indicates that the label collision in the external labels is not detected currently.

As another implementation manner of the present invention, the identification module is further configured to: and if the response of the current tag to the tag discovery request is not received, finishing the identification of the external tag.

The apparatus of this embodiment is used to implement the corresponding method in the foregoing method embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described herein again. In addition, the functional implementation of each module in the apparatus of this embodiment can refer to the description of the corresponding part in the foregoing method embodiment, and is not described herein again.

Fig. 7 is a schematic block diagram of an electronic device of another embodiment of the present invention. The electronic device of fig. 7 includes: at least one processor (processor)702, memory (memory)704, bus 706, and communication Interface (Communications Interface) 708.

Wherein: the processor 702, communication interface 708, and memory 704 communicate with one another via a communication bus 706.

A communication interface 708 for communicating with other devices or components.

The processor 702, configured to execute the program 710, may specifically perform the relevant steps in the method described above.

In particular, the program 710 may include program code that includes computer operating instructions.

The processor 702 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement an embodiment of the present invention. The electronic device comprises one or more processors, which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.

The memory is used for storing programs. The memory may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The NFC device of the embodiment of the present invention may be various devices configured with an NFC function, including but not limited to:

(1) a mobile communication device: such devices are characterized by mobile communications capabilities and are primarily targeted at providing voice, data communications. Such terminals include: smart phones (e.g., iphones), multimedia phones, functional phones, and low-end phones, among others.

(2) Ultra mobile personal computer device: the equipment belongs to the category of personal computers, has calculation and processing functions and generally has mobile internet access characteristics. Such terminals include: PDA, MID, and UMPC devices, etc., such as ipads.

(3) A portable entertainment device: such devices may display and play multimedia content. This type of device comprises: audio, video players (e.g., ipods), handheld game consoles, electronic books, and smart toys and portable car navigation devices.

(4) And other electronic equipment with a data interaction function.

Thus, particular embodiments of the present subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may be advantageous.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in one or more of software and/or hardware in implementing the invention.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular transactions or implement particular abstract data types. The invention may also be practiced in distributed computing environments where transactions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the system embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and reference may be made to the partial description of the method embodiment for relevant points.

The above description is only an example of the present invention, and is not intended to limit the present invention. Various modifications and alterations to this invention will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.

Claims

1. A Near Field Communication (NFC) tag identification method is characterized by comprising the following steps:

when the identification of the last tag in the external tags is completed according to an NFC-A tag anti-collision mechanism, acquiring the current tag collision state of the external tags;

if the current tag collision state indicates that tag collision is not detected in the external tags currently, sending a tag silent request to the identified previous tag, wherein the tag silent request is used for enabling the tag which is identified to enter a silent state;

sending a tag discovery request, wherein the tag discovery request is used for discovering tags which are not in the silent state in the external tags;

and if a response of the current tag to the tag discovery request is received, identifying the current tag according to the NFC-A tag anti-collision mechanism.

2. The method of claim 1, further comprising:

and updating the last label by using the current label.

3. The method of claim 1, wherein identifying the current tag according to the NFC tag anti-collision mechanism if a response from the current tag to the tag discovery request is received comprises:

if a response of the current tag to the tag discovery request is received, acquiring configuration information included in the response of the current tag;

and if the configuration information indicates that the current tag supports the NFC tag anti-collision mechanism, identifying the current tag according to the NFC tag anti-collision mechanism.

4. The method of claim 1, wherein if the current tag collision status indicates that no tag collision is currently detected in the external tags, sending a tag muting request to an identified previous tag comprises:

if the current tag conflict state indicates that tag conflict exists in the external tags which are not detected currently, judging whether to start to execute extended tag identification;

if yes, sending a label silencing request to the identified last label.

5. The method of claim 4, wherein if the current tag collision status indicates that no tag collision is currently detected in the external tags, sending a tag mute request to the identified previous tag, further comprising:

and if the extended tag identification is not executed, ending the identification of the external tag.

6. The method of claim 1, further comprising:

and judging whether the current tag conflict state indicates that tag conflict exists in the external tags which are not detected currently.

7. The method of claim 1, further comprising:

and if the response of the current tag to the tag discovery request is not received, finishing the identification of the external tag.

8. An NFC tag identification device, comprising:

the acquisition module is used for acquiring the current tag collision state of the external tag when the identification of the last tag in the external tags is finished according to the NFC-A tag anti-collision mechanism;

a first sending module, configured to send a label silencing request to an identified previous label if the current label collision status indicates that a label collision is not currently detected in the external label, where the label silencing request is used to enable a label that has completed identification to enter a silencing state;

a second sending module, configured to send a tag discovery request, where the tag discovery request is used to discover a tag that is not in the silent state in the external tags;

and the identification module is used for identifying the current tag according to the NFC-A tag anti-collision mechanism if the response of the current tag to the tag discovery request is received.

9. An NFC device, comprising:

at least one processor, a memory, a bus and a communication interface, wherein the memory stores programs, the processor, the communication interface and the memory complete mutual communication through the bus, the communication interface is used for communicating with other devices or components, and the processor executes the programs to realize: the method of any one of claims 1-7.

10. A computer storage medium comprising a stored program, wherein the program, when executed, controls an apparatus comprising the storage medium to perform the method of any of claims 1-7.