WO2023000774A1

WO2023000774A1 - Nfc tag identification method and apparatus, nfc device and storage medium

Info

Publication number: WO2023000774A1
Application number: PCT/CN2022/091820
Authority: WO
Inventors: 王大耀
Original assignee: 深圳市汇顶科技股份有限公司
Priority date: 2021-07-20
Filing date: 2022-05-10
Publication date: 2023-01-26
Also published as: CN113553870B; CN113553870A

Abstract

An NFC tag identification method and apparatus, an NFC device and a storage medium. The tag identification method comprises: when identification of a previous tag in external tags is completed according to an NFC tag anti-collision mechanism, obtaining a current tag collision state of the external tags; if the current tag conflict state indicates that no tag conflict exists in the external tags is detected at present, sending a tag silence request to the identified previous tag, the tag silence request being used for enabling the identified tag to enter a silence state; sending a tag discovery request, the tag discovery request being used for discovering tags which are not in the silent state in the external tags; and if a response of a current tag to the tag discovery request is received, identifying the current tag according to the NFC tag anti-collision mechanism. According to the method, the identification accuracy and reliability of the external tags are improved.

Description

NFC tag identification method, device, NFC device and storage medium

technical field

The embodiments of the present invention relate to the technical field of communication, and in particular to an NFC tag identification method, device, NFC device and storage medium.

Background technique

In Near Field Communication (NFC) technology, according to the NFC forum (NFC Forum, an organization that formulates NFC communication protocols), NFC devices can communicate in passive communication mode, active communication mode or point-to-point mode.

The digital specification of the NFC forum stipulates that: in the active communication mode, the NFC reader can emit a radio frequency field for tag identification, and the external tag that receives the radio frequency field returns the information carried by the external tag to the NFC reader through load modulation. Label Information. When there are multiple tags returning tag information to the NFC reader, the NFC reader will identify multiple external tags that conflict with each other according to the NFC tag anti-collision mechanism.

However, there are still cases where the identification of external labels is not accurate.

Contents of the invention

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

According to the first aspect of an embodiment of the present invention, there is provided an NFC tag identification method, including: when the identification of the previous tag in the external tag is completed according to the NFC tag anti-collision mechanism, acquiring the current tag conflict of the external tag state; if the current label conflict status indicates that no label conflict is currently detected in the external label, a label silence request is sent to the previous label that has been identified, and the label silence request is used to allow the label that has completed the identification to enter Silent state; send a label discovery request, and the label discovery request is used to discover tags that are not in the silent state in the external tags; if a response from the current tag to the tag discovery request is received, then according to the NFC tag The anti-collision mechanism identifies the current label.

According to the second aspect of the embodiments of the present invention, there is provided an NFC tag identification device, including: an acquisition module, when the identification of the previous tag in the external tag is completed according to the NFC tag anti-collision mechanism, acquire the ID of the external tag Current label conflict state; the first sending module, if the current label conflict state indicates that no label conflict is currently detected in the external label, then send a label silence request to the identified last label, and the label silence request is used To make the tag that has been identified enter the silent state; the second sending module sends a tag discovery request, and the tag discovery request is used to discover tags that are not in the silent state among the external tags; if the judging module receives the current The tag responds to the tag discovery request by identifying the current tag according to the NFC tag anti-collision mechanism.

According to a third aspect of the embodiments of the present invention, an NFC device is provided, including: one or more processors, a communication interface, a memory and a communication bus, and one or more programs, wherein the one or more processing The processor, the communication interface, and the memory complete the mutual communication through the communication bus, and one or more programs are stored in the memory, and are configured to be executed by the one or more processors according to the first A method as described in one aspect.

According to a fourth aspect of the embodiments of the present invention, there is provided a computer storage medium, the computer storage medium includes a stored program, wherein when the program is running, the device including the storage medium is controlled to execute the program described in the first aspect. described method.

In the solution of the embodiment of the present invention, receiving the response of the current tag to the tag discovery request indicates that the current tag is not in the silent state. In addition, the tags that have been identified all enter the silent state through the indication of the tag silent request, which further indicates that the current tag The identification is not completed, so the solution of the embodiment of the present invention can discover and identify the current label that has not completed the identification when no label conflict in the external label is currently detected, which improves the identification accuracy and reliability of the external label , avoiding that in the case of label conflicts that are not detected in external labels but actually exist, all conflicting labels cannot be identified.

Description of drawings

Hereinafter, some specific embodiments of the embodiments of the present invention will be described in detail with reference to the accompanying drawings in an exemplary rather than restrictive manner. The same reference numerals in the drawings designate the same or similar parts or parts. Those skilled in the art will appreciate that these figures are not necessarily drawn to scale. In the attached picture:

Fig. 1A is a schematic diagram of the principle of tag identification based on the NFC tag anti-collision mechanism of 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 the schematic flow chart of the NFC label identification method of 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 the schematic flow chart of the NFC label identification method of another embodiment of the present invention;

Fig. 5 is the schematic flow chart of the NFC label identification method of another embodiment of the present invention;

Fig. 6 is the schematic block diagram of the NFC label identifying device of 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 specific implementation of the embodiments of the present invention will be further described below in conjunction with the accompanying drawings of the embodiments of the present invention. It should be understood that NFC devices or electronic devices equipped with NFC functions can be widely used in fields such as access control, public transport, mobile payment, smart posters, and data transmission. For example, the NFC device can be implemented as a contactless smart card (IC card), such as a bank card, bus card, access control card, etc. Specifically, it can be realized through the NFC controller and the secure element unit contained in the mobile terminal, in cooperation with the software system. Simulation of contactless smart cards such as bank cards, bus cards, and access control cards. The NFC device can also be implemented as a POS machine, a card reader, and the like. The NFC device can also be implemented as an Internet of Things (IOT) device.

In order to better realize the above functions and scenarios, the NFC forum has formulated various NFC specifications. Among them, the Digital specification stipulates 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 sends a radio frequency electromagnetic field carrying information to the NFC tag, and the NFC tag performs load modulation on the radio frequency electromagnetic field to send data to the NFC reader. 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 847kHz). The NFC tag acting as a listening device begins to indicate the bit information of the returned data at the rising or falling edge of the subcarrier.

Specifically, in the NFC-A technology, the NFC reader can emit a radio frequency field for tag identification, and the external tag that receives the radio frequency field returns the tag information carried by the external tag to the NFC reader through load modulation. The NFC reader/writer detects bit information for each bit of tag information. When multiple different bits of information are detected for the same bit, the NFC reader determines that there are multiple tags to be identified that conflict with each other externally, and sends a polling command through the NFC tag anti-collision mechanism to distinguish multiple different bits of information. These tags are identified.

More specifically, the identification process based on the NFC tag anti-collision mechanism will be specifically described below in conjunction with FIG. 1A and FIG. 1B. FIG. 1A shows a typical example of the NFC tag identification principle, and FIG. 1B shows a schematic diagram of the NFC tag identification method sexual process. As shown in FIG. 1A , when receiving a radio frequency field, tag A returns 8-bit tag information 10101010 through load modulation, and tag B returns 8-bit tag information 10111010 through load modulation. The NFC reader/writer detects the bit information for the 8 bits respectively. If the bit information corresponding to the same bit in the label information of the tag A and the tag B is consistent, the NFC reader/writer will detect the bit information of the bit as Type D (when the bit information corresponding to the same bit of the two tag information is both 1) or type E (when the bit information corresponding to the same bit of the two tag information is both 0). If the bit information corresponding to the same bit in the tag information of tag A and tag B is inconsistent, the NFC reader will determine that there are multiple different bit information corresponding to the same bit. Conflicting bit information exists in the same bit. In this case, the NFC reader/writer recognizes the bit information of this bit as type C, for example, the tag information of tag A and tag B corresponds to the bit information of the fourth bit being 0 and 1 respectively, that is, Conflicting bit information is formed, so the NFC reader/writer recognizes the bit information of the fourth bit as type C.

In the NFC specification, the NFC reader judges whether there are multiple conflicting tags to be identified according to whether there are conflicting bit information, and can adopt the tag identification method conforming to the NFC specification as shown in Figure 1B, and use the polling message to identify tags such as tag A Multiple conflicting labels such as label B are identified one by one until all conflicting labels are identified.

In the NFC tag anti-collision mechanism shown in Figure 1B, the NFC reader (NFC device in active communication mode or read-write mode) will send a polling message (SENS_REQ message or SDD_REQ message), and each external NFC tag (for example, tag A and tag B) will reply the polling message of the NFC device at the agreed time point.

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

S101: The NFC device sends a SENS_REQ or ALL_REQ message to start identification. When receiving the SENS_RES message replied by the tag, the NFC device checks b5-b1 in the SENS_RES message to determine whether the tag supports the tag identification of the NFC tag anti-collision mechanism (by detecting the conflict bit information to identify individual tags). If it is supported, continue to judge whether it is configured as a type 1 label platform. If yes, perform tag recognition on the type 1 tag platform according to the NFC tag anti-collision mechanism, otherwise, go to step 102 . If the tag identification of the NFC tag anti-collision mechanism is not supported, the identification process is ended.

S102: The NFC device selects cascading level 1.

S103: The NFC device sets SEL_CMD and SEL_PAR bytes in the SDD_REQ message, and sends the SDD_REQ message.

S104: The NFC device receives the SDD_RES message, and determines whether a conflict occurs. If yes, execute step S105; otherwise, execute step S109.

S105: The NFC device checks configuration parameters, and determines whether to identify conflicting devices. If yes, execute step S106; otherwise, the execution ends.

S106: The NFC device identifies valid data bits.

S107: The NFC device sets SEL_PAR, includes valid data bits after SEL_PAR, and sets the conflict bit to 1, and then sends SDD_REQ.

S108: The NFC device receives the SDD_RES, and determines whether a conflict occurs. If a conflict occurs, execute step S106; otherwise, execute step S109.

S109: the NFC device sends a SEL_REQ message.

S110: The NFC device receives the SEL_RES message, and determines whether the NFCID1 is complete. If it is complete, execute step S111; otherwise, increase the cascading level, and execute step S103.

S111: The NFC device stores NFCID1.

S112: The NFC device checks the configuration parameters, and judges whether to continue the tag identification of the NFC tag anti-collision mechanism. If yes, send SLP_REQ to make the previous tag sleep, and send SENS_REQ to re-execute S102 to start detection; otherwise, the execution ends.

However, in some cases, due to the differences in the implementation of the physical layer (for example, the analog layer) of the NFC reader, and due to the mutual influence of multiple tags that conflict with each other during load modulation, even if the various NFC forum requirements are satisfied Specifications, there may also be cases where Type C indicating conflicting bit information cannot be recognized.

In other cases, the NFC reader can also identify radio frequency identification (Radio Frequency Identification, RFID) tags. Similar to the above-mentioned NFC tag, the RFID tag also returns tag information including 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 NFC specifications. In other words, when an NFC reader/writer communicates 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 NFC reader's sending timing of the SENS_REQ message (poll message) and the RFID tag's return timing of the SENS_RES message (response of the polling message) is greater than the requirements of the NFC forum, in this case , the conflicting bit information between RFID tags and NFC tags that actually conflict with each other, or the conflicting bit information between multiple RFID tags that actually conflict with each other cannot be detected, and thus the multiple tags that conflict with each other cannot be detected. Recognition, the recognition reliability of external tags is poor.

The NFC tag identification method of the embodiment of the present invention will be described in detail below with reference to FIG. 2 , which can improve the reliability of identification of external tags. Fig. 2 shows an NFC tag identification method according to an embodiment of the present invention. The NFC label identification method of Fig. 2 can be used for the NFC equipment as polling equipment, including:

S210: Obtain the current tag conflict state of the external tag when the identification of the last tag among the external tags according to the NFC tag anti-collision mechanism is completed.

It should be understood that before identifying the previous label in the external label, the NFC device can judge that there is a label conflict in the external label through the conflict bit information, and start to use the NFC label anti-collision mechanism to identify each conflicting label. The tag is the first identified tag among the conflicting tags. Specifically, when the previous label among the external labels is identified according to the NFC label anti-collision mechanism, an SDD_REQ message can be sent, and the previous label can be identified by setting corresponding parameters in the SDD_REQ message. More specifically, when performing tag identification, the NFC device will successively send SDD_REQ messages in a polling manner for each bit with conflicting bit information (conflicting bits), and for any conflicting bit, the SDD_REQ message will specify the bit The bit information on the bit, to temporarily avoid bit information conflicts, so as to first obtain the complete label information of a label among the multiple labels that conflict with each other, this label is the "previous label". In other words, through such an anti-collision mechanism, when all bits of the tag information returned by the tag do not have conflicting bit information, the NFC device can identify all the bit information in the tag information, thereby identifying the tag (the previous tag ).

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

It should also be understood that a tag wakeup request (for example, the ALL_REQ message in the NFC specification) can be sent to start this conflict identification of the external tag, and the tag wakeup request is used to execute all tags in the silent state (that is, including identified tags) The wake-up, all tag discovery request can also be used to re-initiate conflict identification of external tags after the current identification of external tags ends.

S220: If the current tag conflict state indicates that no tag conflict is currently detected in the external tag, send a tag silence request to the previous tag that has been identified, and the tag silence request is used to make the tag that has been identified enter a silent state.

It should be understood that the tag silence request in this article can make the tag that has been identified enter the silent state. Specifically, the tag silence request can be the SLP_REQ message in the NFC specification. A tab's silent control message.

It should also be understood that it may be determined whether the current label conflict state indicates that no label conflict is currently detected in the external label. Label collision, if any conflicting bit information is detected, it is judged that there is a label collision detected, and if no conflicting bit information is detected, it is judged that there is no label collision detected.

S230: Send a tag discovery request, where the tag discovery request is used to discover tags that are not in a silent state among the external tags.

It should be understood that the tag discovery request herein can discover tags that are not in a silent state among the external tags, and the tag discovery request can be a SENS_REQ message in the NFC specification. Specifically, the SENS_REQ message can discover tags that are not in the silent state in the external tags, and do not perform wakeup on the tags that have been identified and are in the silent state. In other words, it can be considered that the identified tag in the silent state does not respond to the tag discovery request.

S240: If a response from the current tag to the tag discovery request is received, identify the current tag according to the NFC tag anti-collision mechanism.

It should be understood that receiving the current tag's response to the tag discovery request indicates that the current tag is different from the previously identified tag, in other words, indicates that the current tag conflicts with the previously identified tag. According to the NFC tag anti-collision mechanism to identify the current tag, the current tag can be updated to the previous tag for identification, in other words, the current tag is identified by identifying the previous tag.

Specifically, when the NFC device performs tag identification on the three tags A (10101010), B (10111010) and C (10101011) that actually collide, the NFC device detects the 4th bit between tag A and tag B The conflict bit information of 0 and 1, it is judged that tag A and tag B collide with each other, but the conflict bit information of the 8th bit between tag C and tag A or tag B is not detected, so the NFC device starts tag A that conflicts with each other For the identification of one of the tags B, the NFC device sends the SDD_REQ message and specifies that the fourth bit is 0, then first detects the tag A, and makes the tag A enter the silent state. Then, by specifying the 4th bit as 1, the label B (equivalent to the previous label in the text) is detected, and the collision detection of the conflicting bits is completed so far. After completing the identification of label B (equivalent to the "previous label" in the text), the conventional process considers that there is no more conflicting bit information. However, since the 8th bit conflict between tag C and tag A cannot be detected, when tag B enters the silent state, tag C can still respond to the tag discovery request because it has not completed the identification, so the tag is found C, and identify label C as the next label (ie, the current label) of the "previous label". The conventional NFC tag anti-collision mechanism can be used to identify tag C. If there is no other tag with tag C that has conflicting bit information, the process of using the NFC tag anti-collision mechanism will directly identify the tag information of tag C.

In other words, if the tag information of the current tag is the same as that of a previously recognized tag (e.g., the previous tag or an earlier recognized tag), the current tag will enter the mute state via a tag silence request without any In response to a discovery request, if the current tag is different from the previously identified tag, then the current tag and the previous tag belong to tags that actually conflict with each other, so although the current tag conflict status indicates that no tag conflict is currently detected in the external tag, through this In the solution of the embodiment of the invention, the current tag is still found and thus identified.

It should be understood that in the anti-collision mechanism specified in the existing protocol, a label silence request (for example, an SLP_REQ message) is sent when a label conflict in an external label is detected, while in the solution of the embodiment of the present invention, when no external label is detected The label silence request is sent when there is a label conflict in the system, and therefore the sending timing of the label silence request in the solution of the present invention is completely different from that of a conventional label silence request.

In addition, the tag silence request and the tag discovery request in the tag identification method of the embodiment of the present invention can have the same function as the conventional tag silence request itself, which realizes backward compatibility with existing protocols.

In addition, the method of identifying a tag according to the NFC tag anti-collision mechanism in the embodiment of the present invention is consistent with the tag identification method specified in the existing protocol, and realizes backward compatibility with the existing protocol.

As another implementation manner of the present invention, if no response from the current tag to the tag discovery request is received, the identification of the external tag is ended. Therefore, this implementation has a more accurate and reliable criterion for judging whether there is a tag conflict than the current tag conflict status.

As another implementation of the present invention, if the current tag conflict state indicates that no tag conflict is currently detected in the external tag, then sending a tag silence request to the identified previous tag includes: if the current tag If the conflict status indicates that there is no label conflict detected in the external label, it is judged whether to start to perform extended label identification; if yes, a label silence request is sent to the previously identified label. In this implementation manner, extended tag identification can be used as an alternative option, and the flexibility of tag identification is realized by using the above simple configuration. In other words, when high recognition accuracy and reliability are required, extended tag recognition can be enabled, and when relatively low recognition accuracy and reliability are required, extended tag recognition can be disabled.

As another implementation of the present invention, if the current label conflict status indicates that no label conflict is currently detected in the external label, then sending a label silence request to the previous identified label also includes: if it is judged not to execute The identification of the extended label ends the identification of the external label. Based on such a configuration, a more reliable and accurate judgment of the current label is realized. In other words, while improving the accuracy and reliability of judging label conflicts, the flexibility of label identification is guaranteed.

As another implementation manner of the present invention, the label identification method may further include: using the current label to update the previous label. Since the tag identification process is executed cyclically by means of updating, the brevity and consistency of the identification process of each tag are guaranteed. In addition, this implementation is also better compatible with the conventional conflict detection loop process.

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

As another implementation manner of the present invention, the label identification method may further include: storing label information of the previous identified label. Therefore, storing the tag information of the last identified tag facilitates subsequent corresponding processing based on the identified tag information, for example, establishing a communication connection with the tag. This implementation also achieves compatibility and matching with the label identification step in the conventional label identification process.

As another implementation of the present invention, the tag identification method may also include: if a response from the current tag to the tag discovery request is received, identifying the current tag according to the NFC tag anti-collision mechanism, including: if After receiving the response of the current tag to the tag discovery request, obtain the configuration information included in the response of the current tag; if the configuration information indicates that the current tag supports the NFC tag anti-collision mechanism, then according to the The NFC tag anti-collision mechanism identifies the current tag. This implementation is compatible with and matches the determination steps supported by the configuration parameters 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 part of the interaction process between the NFC device, the identified conflicting tag 32 and the unidentified conflicting tag 33 . It should be understood that, based on the various steps shown in FIG. 3 , the interaction process in this example may also include more or less parts, and may also include alternative steps. Specifically, Figure 3 shows the following steps:

S301: The polling device 31 (for example, an NFC device) 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 send an SDD_REQ message to the conflicting tag 32 to identify the conflicting tag 32. After conflicting tags 32 are obtained, identifications of identified conflicting tags 32 (an example of tag information) may be stored.

S302: The NFC device 31 does not find an unrecognized current tag. Specifically, the NFC device 31 may determine whether the current tag to be identified has been detected according to the tag conflict status. The tag conflict status indicates that there is no conflicting bit information, and the NFC device 31 determines that the current tag to be identified has not been detected.

S303: The NFC device 31 sends a tag silence request to the identified conflicting tag 32 . Specifically, the NFC device 31 may send an SLP_REQ message in response to the above judgment result, and the SLP_REQ message indicates that the identified conflicting tag 32 enters a silent state.

S304: The NFC device 31 sends a tag discovery request. Specifically, the NFC device 31 sends a SENS_REQ message, and the SENS_REQ message is used to find tags that are not in the silent state among the external tags.

S305: The unidentified conflicting tag 33 sends a tag discovery request response to the NFC device 31 . Specifically, the unidentified conflicting tag 33 sends 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 of whether the target tag supports identification of conflicting tags.

S306: The NFC device 31 sends a tag identification message to the unidentified conflicting tag 33 . Specifically, the NFC device 31 can judge that the unrecognized conflicting tag 33 supports conflicting tag identification (a bit-oriented anti-collision mechanism using polling mode) according to the above-mentioned configuration parameters, and send an instruction to the unidentified conflicting tag 33 to continue tag identification. Messages, for example, SDD_REQ messages.

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

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

S420: Obtain the current label conflict state of the external label. Specifically, the purpose of acquiring the tag conflict status is to determine whether there is a current tag to be identified, so as to achieve compatibility with the conventional conflicting tag identification process. It can be judged whether the conflicting bit information of the external tag is detected, if yes, it is judged that there is no current tag to be identified, and if not, it is judged that there is no current tag to be identified.

S430: If the current label conflict status indicates that no current label to be identified is detected, send a label silence request to the previous identified label. Specifically, when it is judged that the current tag to be identified is not detected according to the tag conflict status, an SLP_REQ message is sent in response to the judgment result, and the SLP_REQ message indicates that the last tag identified has entered the silent state.

S440: Send a tag discovery request. Specifically, a SENS_REQ message may be sent to an unrecognized conflicting tag, and the SENS_REQ message is used to find a tag that is not in a silent state among the external tags.

S450: If a response from the current tag to the tag discovery request is received, identify 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 of whether the target tag supports identification of conflicting tags.

S460: Utilize the current label to be recognized to update the unrecognized previous label. Specifically, label identification is performed on the current label in a similar manner to the previous label. In other words, the conflicting tag identification process is cyclically executed 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: Acquire the current label conflict status of the external label when the identification of the previous unidentified label is completed, and then execute S502.

S502: Determine whether the current label conflict state indicates that no label conflict is detected? If yes, execute S503; if no, execute S504.

S503: Determine whether to perform extended label recognition? If yes, execute S505; if no, execute S506.

S504: Utilize the current tag to be recognized to update the previous unrecognized tag, and execute S501.

S505: Send a tag silence request to the identified last tag, and execute step S507. Wherein, the label silence request indicates that the last identified label enters the silence state.

S506: End the identification of the external label.

S507: Send a tag discovery request, and execute step S508. It should be understood that the tag discovery request is used to discover tags that are not in a quiet state among the external tags.

S508: Judging whether a response from the current tag to the tag discovery request has been received, if yes, execute step S509; if no, execute step S510.

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

S510: Determine that there is no current tag to be identified, and end the identification of the external tag.

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

The acquiring module 610 acquires the current tag conflict state of the external tag when the identification of the last tag among the external tags according to the NFC tag anti-collision mechanism is completed.

The first sending module 620, if the current label conflict state indicates that no label conflict is currently detected in the external label, then send a label silence request to the identified previous label, and the label silence request is used to make the completed Recognized tags are silenced.

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

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

As another implementation of the present invention, the first sending module is specifically configured to: if the current label conflict state indicates that no label conflict is currently detected in the external label, then judge whether to start performing extended label identification; if yes , a label silence request is sent to the previous identified label.

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

As another implementation manner of the present invention, the first sending module is further configured to: end the identification of the external label if it is determined that the identification of the extended label is not to be performed.

As another implementation manner of the present invention, the device further includes: an update module, configured to use the current label to update the previous label.

As another implementation manner of the present invention, the device further includes: a judging module, judging whether the current tag conflict state indicates that no tag conflict among the external tags is currently detected.

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

The device of this embodiment is used to implement the corresponding methods in the foregoing multiple method embodiments, and has the beneficial effects of the corresponding method embodiments, so details are not repeated here. In addition, for the function implementation of each module in the apparatus of this embodiment, reference may be made to the description of corresponding parts in the foregoing method embodiments, and details are not repeated here.

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

Wherein: the processor 702 , the communication interface 708 , and the memory 704 communicate with each other through the communication bus 706 .

The communication interface 708 is used for communicating with other devices or components.

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

Specifically, the program 710 may include program codes including computer operation instructions.

The processor 702 may be a central processing unit CPU, or an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present invention. The one or more processors included in the electronic device may be of the same type, 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 to store programs. The memory may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

The NFC device in the embodiment of the present invention can be configured with various devices with NFC functions, including but not limited to:

(1) Mobile communication equipment: This type of equipment is characterized by mobile communication functions, and its main goal is to provide voice and data communication. Such terminals include: smart phones (such as iPhone), multimedia phones, feature phones, and low-end phones.

(2) Ultra-mobile personal computer equipment: This type of equipment belongs to the category of personal computers, with computing and processing functions, and generally also has the characteristics of mobile Internet access. Such terminals include: PDA, MID and UMPC equipment, such as iPad.

(3) Portable entertainment equipment: This type of equipment can display and play multimedia content. Such devices include: audio and video players (such as iPod), handheld game consoles, e-books, as well as smart toys and portable car navigation devices.

(4) Other electronic devices with data interaction functions.

So far, specific embodiments of the subject matter have been described. Other implementations 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 certain implementations, multitasking and parallel processing may be advantageous.

In the 1990s, the improvement of a technology can be clearly distinguished as an improvement in hardware (for example, improvements in circuit structures such as diodes, transistors, and switches) or improvements in software (improvement in method flow). However, with the development of technology, the improvement of many current method flows can be regarded as the direct improvement of the hardware circuit structure. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by hardware physical modules. For example, a programmable logic device (Programmable Logic Device, PLD) (such as a field programmable gate array (Field Programmable Gate Array, FPGA)) is such an integrated circuit, the logic function of which is determined by the user's programming of the device. It is programmed by the designer to "integrate" a digital system on a PLD, instead of asking a chip manufacturer to design and make a dedicated integrated circuit chip. Moreover, nowadays, instead of making integrated circuit chips by hand, this kind of programming is mostly realized by "logic compiler (logic compiler)" software, which is similar to the software compiler used when program development and writing, but before compiling The original code of the computer must also be written in a specific programming language, which is called a hardware description language (Hardware Description Language, HDL), and there is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language) , AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., are currently the most commonly used The most popular are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. It should also be clear to those skilled in the art that only a little logical programming of the method flow in the above-mentioned hardware description languages and programming into an integrated circuit can easily obtain a hardware circuit for realizing the logic method flow.

The controller may be implemented in any suitable way, for example the controller may take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (such as software or firmware) executable by the (micro)processor , logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that, in addition to realizing the controller in a purely computer-readable program code mode, it is entirely possible to make the controller use logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded The same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as structures within the hardware component. Or even, means for realizing various functions may be regarded as a structure within both a software module realizing a method and a hardware component.

The systems, devices, modules, or units described in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementing device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Combinations of any of these devices.

For the convenience of description, when describing the above devices, functions are divided into various units and described separately. Of course, when implementing the present invention, the functions of each unit can be implemented in one or more pieces of software and/or hardware.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, the present invention can 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, etc.) 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 should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, whereby the The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

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

Memory may include non-permanent memory in computer readable media, random access memory

(RAM) and/or non-volatile memory such as read-only memory (ROM) or flash RAM. Memory is an example of computer readable media.

Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information. 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 Disc (DVD) or other optical storage, Magnetic tape cartridge, tape magnetic disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes Other elements not expressly listed, or elements inherent in the process, method, commodity, or apparatus are also included. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems or computer program products. Accordingly, the present invention can 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, etc.) having computer-usable program code embodied therein.

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 can 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 storage devices.

Each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the related parts, please refer to the part of the description of the method embodiment.

The above descriptions are only examples of the present invention, and are not intended to limit the present invention. Various modifications and variations of the present invention will occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the scope of the claims of the present invention.

Claims

A near-field communication NFC label identification method is characterized in that, comprising:

When the identification of the previous label in the external label according to the NFC label anti-collision mechanism is completed, the current label conflict state of the external label is obtained;

If the current label conflict status indicates that no label conflict is currently detected in the external label, a label silence request is sent to the previous identified label, and the label silence request is used to make the identified label enter a silent state ;

sending a tag discovery request, where the tag discovery request is used to discover tags that are not in the silent state among the external tags;

If the response of the current tag to the tag discovery request is received, the current tag is identified according to the NFC tag anti-collision mechanism.
The method according to claim 1, further comprising:

Utilizing the current label to update the previous label.
The method according to claim 1, wherein if the response of the current tag to the tag discovery request is received, identifying the current tag according to the NFC tag anti-collision mechanism includes:

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

If the configuration information indicates that the current tag supports the NFC tag anti-collision mechanism, then identify the current tag according to the NFC tag anti-collision mechanism.
The method according to claim 1, wherein if the current label conflict status indicates that no label conflict is currently detected in the external label, sending a label silence request to the identified last label includes :

If the current label conflict state indicates that no label conflict is currently detected in the external label, it is judged whether to start to perform extended label identification;

If yes, send a tag silence request to the last tag identified.
The method according to claim 4, wherein if the current label conflict state indicates that no label conflict is currently detected in the external label, a label silence request is sent to the identified previous label, and include:

If it is determined that the identification of the extended label is not to be performed, the identification of the external label is ended.
The method according to claim 1, further comprising:

Judging whether the current label conflict state indicates that no label conflict is currently detected in the external label.
The method according to claim 1, further comprising:

If no response from the current tag to the tag discovery request is received, the identification of the external tag is ended.
A kind of NFC tag identification device, is characterized in that, comprises:

The acquisition module acquires the current tag conflict state of the external tag when the identification of the previous tag in the external tag is completed according to the NFC tag anti-collision mechanism;

The first sending module, if the current tag conflict state indicates that no tag conflict is currently detected in the external tag, then send a tag silence request to the previous identified tag, and the tag silence request is used to make the identification completed The label of the goes into silent state;

The second sending module sends a tag discovery request, where the tag discovery request is used to discover tags that are not in the silent state among the external tags;

The identifying module, if a response from the current tag to the tag discovery request is received, identifies the current tag according to the NFC tag anti-collision mechanism.
A kind of NFC device, is characterized in that, comprises:

At least one processor, memory, bus, and communication interface, wherein the memory stores programs, the processor, the communication interface, and the memory complete mutual communication through the communication bus, and the communication interface For communicating with other devices or components, the processor executes the program to implement: the method according to claims 1-7.
A computer storage medium, characterized in that the computer storage medium includes a stored program, wherein when the program is running, the device including the storage medium is controlled to execute the method according to any one of claims 1-7. method.