JP2017126353A - Tag identification method and apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a tag identification method and apparatus which can achieve reduction of steps of determining a format of a tag by a host device in an NFC terminal, so that the tag can be quickly processed.SOLUTION: A Near Field Communication (NFC) controller reads a type of a tag. The NFC controller determines whether a format of the tag is an NFC data exchange format (NDEF) according to the type of the tag. The NFC controller sends a notification message to a device host when the NFC controller determines that the format of the tag is the NDEF. The notification message includes that the format of the tag is the NDEF.SELECTED DRAWING: Figure 1

Description

  The present invention relates to the field of communication technology, and more particularly to a tag identification method and apparatus.

  Near Field Communication (NFC) is a short-range wireless connection technology that can realize communication between short-distance electronic devices using magnetic field induction. Realize data exchange.

  In the conventional technology, after the NFC terminal detects the NFC tag, the near field communication controller (NFC controller) of the NFC terminal reads the entire contents of the NFC tag and reads the entire contents of the NFC tag. Sent to the device host (Device Host), and the device host processes the NFC tag. In general, the device host determines whether or not the format of the NFC tag matches the NFC data exchange format (NFC Data Exchange Format, NDEF) according to the entire contents of the NFC tag.

  However, in the prior art, the device host can determine the format of the NFC tag only by acquiring the entire contents of the NFC tag. This results in the device host reading a large amount of NFC tag data and performing a relatively complex operation.

  Embodiments of the present invention provide a tag identification method and apparatus capable of realizing a reduction in the step of determining a tag format by a device host of an NFC terminal so that the NFC tag can be processed.

  According to a first aspect, an embodiment of the present invention provides a tag identification method, wherein a tag type is read by a near field communication (NFC) controller, and a tag type according to the tag type by an NFC controller. Determining whether the format is NFC data exchange format (NDEF), and sending a notification message to the device host when the NFC controller determines that the tag format is NDEF by the NFC controller Yes, the notification message includes a step including that the tag format is NDEF.

  In a first possible embodiment, referring to the first aspect, prior to reading a tag type by a near field communication (NFC) controller, the method was transmitted by a device host by the NFC controller. Receiving a configuration command, the configuration command further comprising a step used to indicate whether the NFC controller performs NDEF detection on the tag.

  In a second possible embodiment, referring to the first aspect or the first possible embodiment of the first aspect, the NFC controller converts the tag format according to the tag type into an NFC data exchange format (NDEF). The step of determining whether the tag type is Type 1 or not is determined by the NFC controller if the tag format is NDEF according to the tag header read only memory (HR) 0. If the tag type is Type 2, the NFC controller determines whether the tag format is NDEF according to the tag's capability container (CC), and if the tag type is Type 3, The NFC controller determines whether the tag format is NDEF according to the tag system code (System Code), and the tag type is Type If 4, the NFC controller includes determining whether the tag format is NDEF according to the file identifier of the tag's capability container (CC) file.

  In a third possible embodiment, referring to one of the first aspect or the previous possible embodiment of the first aspect, before receiving a configuration command sent by the device host by the NFC controller, The method includes sending a format function message to the device host by the NFC controller, the format function message holding information about whether the NFC controller has the ability to perform NDEF detection on the tag. In addition.

  In a fourth possible embodiment, with reference to the third possible embodiment of the first aspect, before sending a format capability message to the device host by the NFC controller, the method comprises: The method further includes receiving an initialization command sent by the device host, and sending the format function message to the device host by the NFC controller is a step of sending an initialization response to the device host by the NFC controller. The initialization response includes maintaining information about whether the NFC controller has the ability to perform NDEF detection on the tag.

  In a fifth possible embodiment, referring to the first possible embodiment of the first aspect, the configuration command is further used to indicate that the NFC controller performs data type detection on the tag. .

  In a sixth possible embodiment, after sending a notification message to the device host by the NFC controller with reference to any one of the first aspect or the previous possible embodiments of the first aspect, The method includes receiving a read / write command sent by a device host by using an NDEF radio frequency interface by an NFC controller and converting the read / write command to an NDEF read / write command by the NFC controller. And further comprising performing data read / write at the tag according to the NDEF read / write command by the NFC controller.

  According to a second aspect, an embodiment of the present invention provides a tag identification device, a reading module configured to read a tag type, and a tag format according to the tag type is NFC data exchange format (NDEF ) And a transmission module configured to send a notification message to the device host if the determination module determines that the tag format is NDEF. Yes, the notification message includes a transmission module including that the tag format is NDEF.

  In a first possible embodiment, referring to the second aspect, the apparatus is a receiving module configured to receive a configuration command sent by a device host, the configuration command being received by an NFC controller It further includes a receiving module used to indicate whether to perform NDEF detection on the tag.

  In a second possible embodiment, referring to the second aspect or the first possible embodiment of the second aspect, the determination module determines that if the tag type is Type 1, the tag format is tag Determines whether NDEF is according to the header read-only memory (HR) 0 of the tag, and if the tag type is Type 2, determines whether the tag format is NDEF according to the tag's capability container (CC) If the tag type is Type 3, it is determined whether the tag format is NDEF according to the tag system code (System Code). If the tag type is Type 4, the tag format is tag Specifically configured to determine whether it is an NDEF according to the file identifier of the capability container (CC) file.

  In a third possible embodiment, referring to one of the second aspect or the previous possible embodiment of the second aspect, the sending module is further configured to send a format capability message to the device host. The format function message holds information about whether the NFC controller has the ability to perform NDEF detection on the tag.

  In a fourth possible embodiment, referring to the third possible embodiment of the second aspect, the receiving module is further configured to receive an initialization command sent by the device host, wherein the sending module Is further configured to send an initialization response to the NFC controller, the initialization response holding information about whether the NFC controller is capable of performing NDEF detection on the tag.

  In a fifth possible embodiment, referring to the first possible embodiment of the second aspect, the configuration command is further used to indicate that the NFC controller performs data type detection on the tag. .

  In a sixth possible embodiment, referring to any one of the second possible aspect or the aforementioned possible embodiments of the second aspect, the receiving module uses the NDEF radio frequency interface to Further configured to receive a read / write command sent by the host, the device according to the NDEF read / write command and a conversion module configured to convert the read / write command to an NDEF read / write command; And a processing module configured to perform data reading / writing at the tag.

  According to a third aspect, an embodiment of the present invention provides a tag identification device, which includes a near field communication (NFC) controller and a device host, wherein the NFC controller is connected to the device host. The NFC controller is configured to read the tag type and determine whether the tag format is NFC data exchange format (NDEF) according to the tag type, and that the tag format is NDEF If the controller determines, the NFC controller sends a notification message to the device host, the notification message includes that the tag format is NDEF, and the device host receives the notification message sent by the NFC controller. Configured.

  In a first possible embodiment, referring to the third aspect, the device host is further configured to send a configuration command to the NFC controller, which performs NDEF detection on the tag by the NFC controller. The NFC controller is further configured to receive a configuration command sent by the device host.

  In the second possible embodiment, referring to the third aspect or the first possible embodiment of the third aspect, the NFC controller determines that if the tag type is Type 1, the tag format is tag Determines whether NDEF is according to the header read-only memory (HR) 0 of the tag, and if the tag type is Type 2, determines whether the tag format is NDEF according to the tag's capability container (CC) If the tag type is Type 3, it is determined whether the tag format is NDEF according to the tag system code (System Code). If the tag type is Type 4, the tag format is tag Specifically configured to determine whether it is an NDEF according to the file identifier of the capability container (CC) file.

  In a third possible embodiment, referring to one of the third aspect or the previous possible embodiment of the third aspect, the NFC controller is further configured to send a format capability message to the device host. The format function message holds information about whether the NFC controller has the ability to perform NDEF detection on the tag.

  In a fourth possible embodiment, referring to the third possible embodiment of the third aspect, the device host is further configured to send an initialization command to the NFC controller, wherein the NFC controller After receiving the initialization command sent by the host, it is further configured to send an initialization response to the device host, the initialization response as to whether the NFC controller has the ability to perform NDEF detection on the tag. The information of is retained.

  In the fifth possible embodiment, referring to the first possible embodiment of the third aspect, the configuration command is further used to indicate that the NFC controller performs data type detection on the tag. .

  In a sixth possible embodiment, referring to any one of the third aspect or the previous possible embodiments of the third aspect, the device host has received a notification message sent by the NFC controller Later, it is further configured to establish an NDEF radio frequency interface to perform data transmission with the NFC controller.

  In a seventh possible embodiment, referring to the sixth possible embodiment of the second aspect, the device host sends a read / write command to the NFC controller by using the NDEF radio frequency interface. Further configured, the NFC controller receives a read / write command sent by the device host by using the NDEF radio frequency interface, converts the read / write command to an NDEF read / write command, and reads the NDEF Further configured to perform data read / write in the tag according to the / write command.

  According to the tag identification method and apparatus provided in the embodiment of the present invention, the NFC controller reads the tag type and determines whether the tag format is an NFC data exchange format according to the tag type. If the NFC controller determines that the tag format is the NFC data exchange format, the NFC controller sends a notification message to the device host, and the notification message includes information that the tag format is the NFC data exchange format. . Only when the device host gets the entire contents of the NFC tag can the format of the NFC tag be determined, which means that the device host reads a large amount of data from the NFC tag and performs a relatively complex operation Compared to the prior art that results in this, embodiments of the present invention can achieve a reduction in the step of determining the format of the tag by the device host of the NFC terminal so that the NFC tag can be processed.

In order to clearly describe the technical solutions of the embodiments of the present invention or the prior art, the following briefly introduces the accompanying drawings required for describing the embodiments or the prior art. Apparently, the accompanying drawings in the following description show merely some embodiments of the present invention, and those skilled in the art can continue to draw other drawings from these accompanying drawings without creative efforts. Can lead.
The flowchart of the tag identification method by the Example of this invention Flowchart of another tag identification method according to an embodiment of the present invention Schematic diagram of a transmission configuration between a device host and an NFC controller and between an NFC controller and a tag in a tag identification method according to an embodiment of the present invention. 1 is a schematic configuration diagram of a tag identification device according to an embodiment of the present invention. The schematic block diagram of the other tag identification apparatus by the Example of this invention Schematic configuration diagram of still another tag identification device according to an embodiment of the present invention.

  DESCRIPTION OF EMBODIMENTS The following clearly and completely describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are merely a part rather than all of the embodiments of the present invention. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

  As shown in FIG. 1, an embodiment of the present invention provides a tag identification method, which includes:

  101: The NFC controller reads the tag type.

  The NFC controller is a controller of the NFC terminal. The NFC terminal may be a terminal having an NFC function such as a mobile phone, a tablet computer, or a camera. For ease of explanation, an embodiment will be described by using a mobile phone having an NFC function as an example. The NFC controller is a logical entity that serves to transmit data over the NFC radio frequency interface. In the example of a mobile phone with NFC function, the NFC controller indicates the NFC chip of the mobile phone.

  In this embodiment, the tag is an NFC tag. The types of NFC tags are Type1, Type2, Type3, and Type4. Reference may be made to the NFC Forum Analog standard, NFC Forum Digit standard, and NFC Forum Activity standard for the manner in which the NFC controller reads the tag type.

  The NFC controller may discover the tag and obtain the tag attributes using radio frequency discovery. Reference may be made to the NFC Forum Analog standard, the NFC Forum Digit standard, and the NFC Forum Activity standard for the process in which the NFC controller discovers a tag and acquires the attribute of the tag using radio frequency discovery. Tag attributes may include tag format, tag data type, functions supported by the tag, and the like. Here, the function supported by the tag indicates a capability required in the process of establishing communication between the NFC controller and the tag.

  102: The NFC controller determines whether the tag format is NDEF according to the tag type.

  NDEF defines the encapsulation format of information during information exchange. Information is transmitted between NFC terminals or between an NFC terminal and an NFC tag. The NDEF may be a lightweight binary message format and may be used to encapsulate one or more user-defined data of any type and any size.

  If the tag type is Type 1, the NFC controller determines whether the tag format is NDEF according to the header read-only memory (HR) 0 of the tag. Specifically, if the length of HR0 is 1 byte and the four high-order bits of HR0 are 0001b, the NFC controller determines that the tag format is NDEF. If the tag type is Type 2, the NFC controller determines whether the tag format is NDEF according to the tag's Capability Container (CC). Specifically, if the CC length is 4 bytes and the value of the first byte is E1h (E1 is a hexadecimal format), the NFC controller determines that the tag format is NDEF. When the tag type is Type 3, the NFC controller determines whether the tag format is NDEF according to the tag system code (System Code). Specifically, when the length of the System Code is 2 bytes and the value of the System Code is 12FCh (12FC is a hexadecimal format), the NFC controller determines that the tag format is NDEF. If the tag type is Type 4, the NFC controller determines whether the tag format is NDEF according to the file identifier of the tag's Capability Container (CC) file. Specifically, if the length of the file identifier of the CC file is 2 bytes and the value of the file identifier of the CC file is E103h (E103 is a hexadecimal format), the NFC controller uses NDEF as the tag format. Determine that there is.

  Optionally, if the NFC controller determines that the tag format is NDEF, the NFC controller may further determine the data type of the tag. The tag has 8 data types. Specifically, the NFC controller acquires data type information from the TNF field of the tags (Type1, Type2, Type3, and Type4), and determines the data type of the tag according to the content of the data type information. The value of the TNF field may be 0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, or 0x07, and the NFC controller may determine the tag data type information according to the value of the TNF field. The tag data type is specifically the NDEF message type. 0x00 indicates that the NDEF message is an empty message. 0x01 indicates that the NDEF message stores the internal data type defined in the RTD (Record Type Define) standard by the NFC Forum standard organization. 0x02 indicates that the NDEF message stores a media type defined in the RFC (Request For Comments) 2046 standard such as image and sound. 0x03 indicates that the NDEF message stores a Uniform Resource Identifier (URI) defined in the RFC 3986 standard. 0x04 indicates that the NDEF message stores the external data type defined in the RTD (Record Type Define) standard by the NFC Forum standard organization. 0x05 indicates that the NDEF message stores one piece of unknown type data. 0x06 indicates that the NDEF message is an intermediate tag in a series of consecutive NDEF tags, and the data type of the tag is the same as that of the previous NDEF tag. 0x07 indicates that the NDEF message is reserved and is not used temporarily.

  103: The NFC controller sends a notification message to the device host when the NFC controller determines that the tag format is NDEF. The notification message includes information that the tag format is NDEF.

  The device host includes management of the NFC controller such as initialization, configuration and power management, and serves to manage the operating environment of the NFC terminal and peripheral devices. In the example of a mobile phone with NFC capability, the device host may indicate the mobile phone's CPU.

In this embodiment, for example, the NFC controller transmits a notification message to the device host. For example, the notification message is a radio frequency discovery notification (RF_DISCOVER_NFT). The specific format of RF_DISCOVER_NFT is shown in Table 1.

In Table 1, examples of meanings or values indicated by the fields are as follows.
NDEF Info indicates NDEF information that occupies 1 byte (1 Octet).
X indicates whether the tag format is NDEF.
If X ≠ 0000 0000, this indicates that the tag format is NDEF.

  Optionally, if the NFC controller determines that the tag format is not an NFC data exchange format, the NFC controller may still send a notification message to the device host. When X of the notification message (RF_DISCOVER_NFT) satisfies X = 0000 0000, this indicates that the tag format is not NDEF.

Optionally, the notification message sent by the NFC controller to the device host may further include a tag data type. For example, the NFC controller transmits RF_DISCOVER_NFT to the device host. The specific format of RF_DISCOVER_NFT is shown in Table 2.

In Table 2, examples of meanings or values indicated by the fields are as follows. For a detailed description of NDEF Info, reference may be made to the description of Table 1, and details are not described here again.
The type name format (Type Name Format, TNF) indicates information on the data type of the tag and occupies 1 byte (1 Octet).
If X = 0x00, this indicates that the NDEF message is an empty message (the tag includes the NDEF message).
When X = 0x01, this indicates that the NDEF message stores the internal data type defined in the RTD (Record Type Define) standard by the NFC Forum standard organization.

  It should be noted that in this example, X is not limited to indicating the specific data type of the tag. For example, if X = 0x07, this indicates that the NDEF message is reserved and not used temporarily.

  According to the tag identification method provided in this embodiment of the present invention, the NFC controller reads the tag type and determines whether the tag format is an NFC data exchange format according to the tag type. If the NFC controller determines that the tag format is the NFC data exchange format, the NFC controller sends a notification message to the device host, and the notification message includes information that the tag format is the NFC data exchange format. . Only when the device host gets the entire contents of the NFC tag can the format of the NFC tag be determined, which means that the device host reads a large amount of data from the NFC tag and performs a relatively complex operation Compared to the prior art that results in this embodiment, this embodiment of the present invention can achieve a reduction in the step of determining the format of the tag by the device host of the NFC terminal so that the NFC tag can be processed.

  In another embodiment of the present invention, a tag identification method is provided. As shown in FIG. 2, the method includes:

  201: The NFC controller sends a format function message to the device host. The format function message holds information about whether the NFC controller has the ability to perform NDEF detection on the tag.

  Optionally, the NFC controller sends a format capability message to the device host in the following two ways:

  Method 1: The device host transmits an initialization command to the NFC controller. After receiving the initialization command, the NFC controller transmits an initialization response to the device host. That is, the format function message is specifically an initialization response, and the initialization command is used to initialize the NFC controller. For example, the device host transmits CORE_INIT_CMD (initialization command) to the NFC controller. That is, the device host initializes the NFC controller. Next, after receiving CORE_INIT_CMD, the NFC controller feeds back CORE_INIT_RSP (initialization response) to the device host. In the CORE_INIT_RSP response, if the supported Radio Frequency Discovery Interface (Supported RF Interface) field contains 0x04, ie, NDEF Access RF Interface, this indicates that the NFC controller has the ability to detect NDEF.

  Method 2: The device host transmits a format inquiry command to the NFC controller. After receiving the format inquiry command, the NFC controller transmits a format inquiry response to the device host. That is, the format function message is specifically a format inquiry response. For example, the device host transmits FORMAT_INQ_CMD (format inquiry command) to the NFC controller, and after receiving the FORMAT_INQ_CMD, the NFC controller feeds back FORMAT_INQ_RSP (format inquiry response) to the device host.

  Obviously, this embodiment is not limited to the two previously described schemes used as examples. The NFC controller may further add to the message sent to the device host information about whether the NFC controller has the ability to perform NDEF detection on the tag.

  202: The device host sends a configuration command to the NFC controller. The configuration command is used to indicate whether the NFC controller performs NDEF detection on the tag.

For example, the device host transmits a CORE_SET_CONFIG_CMD command to the NFC controller. The CORE_SET_CONFIG_CMD command includes format parameters. The specific format of the format parameter is shown in Table 3.

In Table 3, examples of meanings or values indicated by the fields are as follows.
Parameter 1 indicates a format parameter, and the format parameter has 3 bytes (3 octets).
The ID (identifier) occupies 1 byte (1 Octet), and 0xA0 indicates the identifier of the format parameter.
Len (length) occupies 1 byte (1 Octet), and 1 indicates that the length of Val is 1 byte.
If Val (value) occupies 1 byte (1 Octet), and the value of Val is 0000 0000, this tells the NFC controller to not perform NDEF detection on the tag. Show. If the value of Val is not zero (eg, 0000 0001), this indicates that the configuration command instructs the NFC controller to perform NDEF detection on the tag.

  It should be noted that the value of the byte occupied by Parameter 1 is not limited in this embodiment. When the byte occupied by ID, Len, or Val included in Parameter 1 changes, the value of the byte occupied by Parameter 1 may also change.

Optionally, the configuration command is further used to indicate that the NFC controller performs data type detection on the tag. If the CORE_SET_CONFIG_CMD command sent by the device host to the NFC controller is further used to indicate that the NFC controller performs data type detection on the tag, the CORE_SET_CONFIG_CMD command includes a format parameter and a data type parameter. There are two expression methods for CORE_SET_CONFIG_CMD, and specific formats are shown in Tables 4 and 5.

  For a detailed description of the format parameter Parameter 1, reference may be made to the description of Table 3, and the details will not be described again here.

In Table 4, examples of meanings or values indicated by the fields are as follows.
Parameter 2 indicates a data type parameter, and the data type parameter has 3 bytes (3 Octets).
The ID (identifier) occupies 1 byte (1 Octet), and 0xA1 indicates the identifier of the data type parameter.
Len (length) occupies 1 byte (1 Octet), and 1 indicates that the length of Val is 1 byte.
If Val (value) occupies 1 byte (1 Octet) and Val value X is 0101 0000, this means that the configuration command performs detection in the second and fourth data types for the NFC controller Indicates that you are instructed to do so. It can be seen that the tag has 8 data types. The device host arranges the eight data types in a specific order, and associates each bit of the value of Val with one data type. If the bit of X is 1, this indicates that the data type corresponding to that bit needs to be detected. If a bit is 0, this indicates that the data type corresponding to that bit need not be detected. For example, a sequence of eight data types from the first type to the eighth type is as 0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, and 0x07. Correspondingly, the first bit corresponds to 0x00, the second bit corresponds to 0x01, the third bit corresponds to 0x02, the fourth bit corresponds to 0x03, and analogy, The bit corresponds to 0x07. In accordance with the configuration command requirements in Table 4, the NFC controller detects whether the data type of the tag is one of two data types, namely 0x01 or 0x03.

In Table 5, examples of meanings or values indicated by the fields are as follows. For a detailed description of the format parameter Parameter 1, reference may be made to the description of Table 3, and the details will not be described again here.
Parameter 2 indicates a data type parameter, and the data type parameter has 3 bytes (3 Octets).
The ID (identifier) occupies 1 byte (1 Octet), and 0xA1 indicates the identifier of the data type parameter.
Len (length) occupies 1 byte (1 Octet), and 1 indicates that the length of Val is 1 byte.
If Val (value) occupies 1 byte (1 Octet) and Val value is 0000 0000, this tells the NFC controller not to perform data type detection on the tag. Indicates. If the value of Val is not zero (eg, 0000 0001), this indicates that the configuration command instructs the NFC controller to perform data type detection on the tag.

  In this step, reference may be made to step 102 in FIG. 1 for descriptions of the device host, NFC controller, and NDEF.

  203: The NFC controller sends a configuration command response message to the device host.

  After receiving the configuration command sent by the device host, the NFC controller sends a configuration command response message to the device host. The configuration command response message may be CORE_SET_CONFIG_RSP.

  204: The device host sends a radio frequency discovery start command to the NFC controller.

  After receiving the configuration command response message sent by the NFC controller, the device host sends a radio frequency discovery start command to the NFC controller. Alternatively, the device host waits for a predetermined time after transmitting the configuration command, and starts transmitting a radio frequency discovery start command to the NFC controller. For example, the device host transmits RF_DIS_CMD (radio frequency discovery start command) to the NFC controller.

  The range of the predetermined time is not limited in this embodiment. For example, when the predetermined time is 200 ms, the device host starts transmitting a radio frequency discovery start command to the NFC controller 200 ms after transmitting the configuration command to the NFC controller.

  205: The NFC controller sends a radio frequency discovery response message to the device host and initiates radio frequency discovery to read the tag type.

  The radio frequency discovery response message includes notification information that the NFC controller has received a radio frequency discovery start command. For example, the NFC controller transmits RF_DIS_RSP (radio frequency discovery response message) to the device host.

  206: The NFC controller determines whether the tag format is NDEF according to the tag type.

  Reference may be made to step 102 of FIG. 1 for the manner in which the NFC controller determines whether the tag format is NDEF, and details are not described herein again.

  207: If it is determined that the tag format is NDEF, the NFC controller determines the data type of the tag.

  Note that this step is optional and the NFC controller only needs to perform step 207 if the configuration command further includes information indicating that the NFC controller detects the tag's data type. It is. Therefore, in FIG. 2, step 207 is represented by a dotted box.

  Reference may still be made to step 102 of FIG. 1 for the manner in which the NFC controller determines the tag data type.

  208: The NFC controller sends a notification message to the device host.

  For a detailed description of the notification message, reference may be made to step 103 of FIG.

  209: If the tag format is NDEF, the device host establishes an NDEF radio frequency interface.

  The NDEF radio frequency interface is an interface between the device host and the NFC controller. The NFC controller uses the NDEF radio frequency interface to transmit data transmitted between the NFC controller and the tag (the tag format is NDEF) to the device host. Alternatively, the device host first transmits data to be transmitted to the tag to the NFC controller by using the NDEF radio frequency interface, and then the NFC controller transfers the data to the tag.

Specifically, the device host transmits RF_DISCOVER_SELECT_CMD (radio frequency discovery selection command) to the NFC controller. RF_DISCOVER_SELECT_CMD includes information that the device host has established the NDEF interface. The specific format of RF_DISCOVER_SELECT_CMD is shown in Table 6.

In Table 6, examples of meanings or values indicated by the fields are as follows.
The RF Discovery ID indicates a radio frequency discovery identifier and is used to identify a tag corresponding to radio frequency discovery.
XX indicates a tag identifier.
The RF Protocol indicates a communication method (for example, a tag protocol) between the NFC controller and the tag.
RF Interface indicates an interface (for example, NDEF radio frequency interface (NDEF RF Interface)) between the device host and the NFC controller.

  After the NDEF radio frequency interface is established between the device host and the NFC controller, and after the NFC controller receives the data sent by the device host, the NFC controller is in a format that allows the data to be received by the tag. May be converted to The tag is a tag identified by an RF Discover ID corresponding to the NDEF radio frequency interface.

  In steps 201-209, it can be seen that the interface used by the NFC controller to perform the interaction with the device host may be an NFC controller interface (NFC controller interface, NCI). NCI is a logical interface between the device host and the NFC controller, and the NCI is configured to transmit various commands between the device host and the NFC controller.

  210: The device host sends a read / write command to the NFC controller by using the NDEF radio frequency interface.

  Read / write commands are used to obtain tag data. Alternatively, read / write commands are used to change tag data.

  211: The NFC controller converts the read / write command into an NDEF read / write command, and executes data read / write in the tag according to the NDEF read / write command.

  The contents of read / write commands received by different types of NFC tags are different. For example, the read / write command received by Type 1 is Read, and the read / write command received by Type 2 is R. The NFC controller uses the NDEF radio frequency interface to translate read / write commands sent by the device host into NDEF read / write commands corresponding to different types of tags. The NDEF read / write command may be an NDEF read command or an NDEF write command.

  For example, the NFC controller sends an NDEF read command to the tag, and the NDEF read command instructs the NFC tag to send tag data. After receiving the NDEF read command, the NFC tag transmits the tag data to the NFC controller.

  212: The NFC controller sends the tag data to the device host.

  213: The device host transmits the received tag data to the NFC application.

  It should be noted that prior to step 213, the device host may receive a registration message sent by the NFC application. Specifically, after being installed or first run, the NFC application performs registration with the device host according to the NFC application's ability to process the tag data type. For example, a browser application program that supports NFC scanning may register the data type, that is, URI (0x03) with the device host.

  When the notification message includes that the tag format is NDEF, the device host transmits the tag data to the execution application. For example, the execution application includes a browser that supports NFC scanning, a video player that supports NFC scanning, and a photo album that supports NFC scanning. The device host sends the tag data to the three execution applications described above, and the three execution applications process the tag according to the actual situation (the application's ability to process the tag data type).

  If the notification message includes that the tag format is NDEF and includes the tag data type, the device host transmits the tag data to the application corresponding to the data type. For example, the execution application includes a browser that supports NFC scanning, a video player that supports NFC scanning, and a photo album that supports NFC scanning. If the tag data type is URI (0x03), the device host sends the tag data to a browser that supports NFC scanning according to the tag data type.

  According to the tag identification method provided in this embodiment of the present invention, it can be realized that the device host of the NFC terminal determines the tag format and the tag data type by using the NFC controller. After obtaining the tag format and tag data type, the device host sends the tag data to the application corresponding to the tag data type for processing according to the tag data type. This allows the device host to determine the tag format and tag data type without having to analyze the entire contents of the tag. Further, the NDEF radio frequency interface established by the device host may allow NFC tag data to be transmitted between the device host and the NFC controller. This achieves the goal that the tag can be processed by the device host.

  In the implementation of this embodiment of the invention, the transmission interface between the device host and the NFC controller is clearly described. As shown in FIG. 3, the command between the device host and the NFC controller before the device host does not receive the notification message sent by the NFC controller (ie, before the device host establishes the NDEF radio frequency interface). Transmission is performed by using NCI. After the device host receives the notification message sent by the NFC controller, the device host establishes the NDEF radio frequency interface, and NDEF data transmission between the device host and the NFC controller shall use the NDEF radio frequency interface Executed by.

  As shown in FIG. 4, an embodiment of the present invention provides a tag identification device 40 that includes a reading module 401, a determining module 402, and a transmitting module 403. This device may be a unit of an NFC terminal, for example, an NFC controller.

  The reading module 401 is configured to read the tag type.

  The determination module 402 is configured to determine whether the format of the tag is NDEF according to the tag type and to transmit the determination result to the transmission module 403.

  The transmission module 403 is configured to transmit a notification message to the device host when the determination module 402 determines that the tag format is NDEF. The notification message includes that the tag format is NDEF.

  For a detailed description of the notification message, reference may be made to step 103 of FIG.

  Further, as shown in FIG. 5, in the tag identification device 50, the tag identification device 50 further includes a reception module 404, a conversion module 405, and a processing module 406.

  Specifically, before the reading module 401 reads the tag type, the transmission module 403 transmits a format function message to the device host. The format function message holds information about whether the NFC controller has the ability to perform NDEF detection on the tag. Specifically, the format function message may be an initialization response. For example, the reception module 404 receives an initialization command transmitted by the device host. Next, the transmission module 403 transmits an initialization response to the NFC controller. The initialization response holds information about whether the NFC controller has the ability to perform NDEF detection on the tag.

  If the initialization response holds information about whether the NFC controller has the ability to perform NDEF detection on the tag, the receiving module 404 receives the configuration command sent by the device host. The configuration command is used to indicate whether the NFC controller performs NDEF detection on the tag. If the configuration command indicates that the NFC controller needs to perform NDEF detection on the tag, the read module 401 can know to read the tag type.

  Optionally, the configuration command is further used to indicate that the NFC controller performs data type detection on the tag.

  Further, if the tag type is Type 1, the determination module 402 determines whether the tag format is NDEF according to the tag HR0. If the tag type is Type 2, the determination module 402 determines whether the tag format is NDEF according to the CC of the tag. When the tag type is Type 3, the determination module 402 determines whether the tag format is NDEF according to the tag System Code. If the tag type is Type 4, the determination module 402 determines whether the tag format is NDEF according to the file identifier of the CC file of the tag.

  Further, after the sending module 403 sends a notification message to the device host, the receiving module 404 receives the read / write command sent by the device host by using the NDEF radio frequency interface, and the conversion module 405 Converting the read / write command to an NDEF read / write command, the processing module 406 then performs a data read / write on the tag according to the NDEF read / write command.

  According to the tag identification device provided in this embodiment of the present invention, it can be realized that the device host of the NFC terminal determines the tag format and the tag data type by using the NFC controller. After obtaining the tag format and tag data type, the device host sends the NFC tag data to the application corresponding to the tag data type for processing according to the tag data type. This allows the device host to determine the tag format and tag data type without having to analyze the entire contents of the NFC tag.

  As shown in FIG. 6, the embodiment of the present invention provides a tag identification device 60 including an NFC controller 601 and a device host 602. The NFC controller 601 is connected to the device host 602.

  The NFC controller 601 is configured to read the tag type and determine whether the tag format is an NFC data exchange format (NDEF) according to the tag type. When the NFC controller 601 determines that the tag format is NDEF, the NFC controller 601 transmits a notification message to the device host 602. The notification message includes that the tag format is NDEF.

  When the tag type is Type 1, the NFC controller 601 determines whether the tag format is NDEF according to the tag HR0. When the tag type is Type 2, the NFC controller 601 determines whether the tag format is NDEF according to the tag CC. When the tag type is Type 3, the NFC controller 601 determines whether the tag format is NDEF according to the tag System Code. When the tag type is Type 4, the NFC controller 601 determines whether the tag format is NDEF according to the file identifier of the CC file of the tag.

  For a detailed description of the notification message, reference may be made to step 103 of FIG.

  The device host 602 is configured to receive the notification message transmitted by the NFC controller 601.

  Further, the NFC controller 601 is further configured to send a format capability message to the device host 602. The format function message holds information about whether the NFC controller 601 has the ability to perform NDEF detection on the tag. Specifically, the format function message may be an initialization response. For example, the device host 602 first transmits an initialization command to the NFC controller 601. After receiving the initialization command transmitted by the device host 602, the NFC controller 601 transmits an initialization response to the device host 602. The initialization response holds information about whether the NFC controller has the ability to perform NDEF detection on the tag.

  Further, the device host 602 is further configured to send a configuration command to the NFC controller. The configuration command is used to indicate whether the NFC controller 601 performs NDEF detection on the tag.

  The NFC controller 601 is further configured to receive a configuration command sent by the device host 602.

  Optionally, a configuration command is used to indicate that NFC controller 601 performs data type detection on the tag.

  Furthermore, the device host 602 is further configured to establish an NDEF radio frequency interface to perform data transmission with the NFC controller 601 after receiving the notification message sent by the NFC controller 601.

  In addition, the device host 602 is further configured to send read / write commands to the NFC controller 601 by using the NDEF radio frequency interface.

  The NFC controller 601 uses the NDEF radio frequency interface to receive read / write commands sent by the device host 602, convert the read / write commands to NDEF read / write commands, and according to the NDEF read / write commands Further configured to perform data read / write at the tag.

  The apparatus illustrated in FIG. 6 may be an NFC terminal, and the NFC terminal may be a terminal having an NFC function such as a mobile phone, a tablet computer, and a camera.

  6 is based on the same inventive concept as the method embodiment of the present invention, and the contents of the specific implementation processing of the module and information exchange between the modules in the apparatus 60 shown in FIG. 6 are referred to in the method embodiment. It should be noted that this may be done, and details are not described here again.

  According to the tag identification device provided in this embodiment of the present invention, it can be realized that the device host of the NFC terminal determines the tag format and the tag data type by using the NFC controller. After obtaining the tag format and tag data type, the device host sends the NFC tag data to the application corresponding to the tag data type for processing according to the tag data type. This allows the device host to determine the tag format and tag data type without having to analyze the entire contents of the NFC tag.

  It will be clearly understood by those skilled in the art that the division of the functional modules described above is given as an illustrative example for the sake of convenience and concise explanation. In practical applications, the aforementioned functions may be implemented by being assigned to different functional modules according to requirements. In other words, the internal configuration of the apparatus is divided into different functional modules in order to realize all or part of the functions described above. For detailed operational processing of the aforementioned system, apparatus and unit, reference may be made to the corresponding processing of the foregoing method embodiment, and details are not described herein again.

  It should be appreciated that in the embodiments provided in this application, the disclosed apparatus and method may be implemented in other ways. For example, the described apparatus embodiment is merely exemplary. For example, the division of modules or units is merely logical function division and may be other division in actual implementation. For example, multiple units or components may be combined, integrated into other systems, and some functions may be ignored or not performed. Furthermore, the mutual coupling or direct coupling or communication connection shown or described may be realized by using several interfaces. Indirect coupling or communication connections between devices or units may be realized in electrical, mechanical or other form.

  The units described as separate parts may or may not be physically separate. The portion displayed as a unit may be a physical unit or may not be a physical unit, may exist in one position, and may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the measures of the embodiment.

  Furthermore, the functional units in the embodiments of the present invention may be integrated into one processing unit, each of the units may physically exist alone, or two or more units may be integrated into one unit. May be. The integrated unit may be realized in the form of hardware or may be realized in the form of a functional unit of software.

  If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored on a computer-readable storage medium. Based on this understanding, basically, the technical measures of the present invention or the part contributing to the conventional technology, or all or part of the technical measures may be realized in the form of a software product. The computer software product is stored in a storage medium so that a computer device (which may be a personal computer, server, network device, or the like) or a processor performs some or all of the method steps described in the embodiments of the present invention. Includes a plurality of instructions. The aforementioned storage medium can store program codes such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk. Including any medium.

  The foregoing descriptions are merely specific implementation manners of the present invention, and are not intended to limit the protection scope of the present invention. Any modification or replacement readily figured out by a person skilled in the art within the technical scope disclosed in the present invention shall fall within the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

In a fourth possible embodiment, referring to the third possible embodiment of the second aspect, the receiving module is further configured to receive an initialization command sent by the device host, wherein the sending module Is further configured to send an initialization response to the device host , the initialization response holding information about whether the NFC controller has the ability to perform NDEF detection on the tag.

In a seventh possible embodiment, referring to the sixth possible embodiment of the third aspect, the device host sends a read / write command to the NFC controller by using the NDEF radio frequency interface. Further configured, the NFC controller receives a read / write command sent by the device host by using the NDEF radio frequency interface, converts the read / write command to an NDEF read / write command, and reads the NDEF Further configured to perform data read / write in the tag according to the / write command.

In order to clearly describe the technical countermeasures of the embodiments of the present invention, the following briefly introduces the accompanying drawings required for describing the embodiments or the prior art. Apparently, the accompanying drawings in the following description show merely some embodiments of the present invention, and those skilled in the art can continue to draw other drawings from these accompanying drawings without creative efforts. Can lead.
The flowchart of the tag identification method by the Example of this invention Flowchart of another tag identification method according to an embodiment of the present invention Schematic diagram of a transmission configuration between a device host and an NFC controller and between an NFC controller and a tag in a tag identification method according to an embodiment of the present invention. 1 is a schematic configuration diagram of a tag identification device according to an embodiment of the present invention. The schematic block diagram of the other tag identification apparatus by the Example of this invention Schematic configuration diagram of still another tag identification device according to an embodiment of the present invention.

If the tag type is Type 1, the NFC controller determines whether the tag format is NDEF according to the header read-only memory (HR) 0 of the tag. Specifically, if the length of HR0 is 1 byte and the four high-order bits of HR0 are 0001b, the NFC controller determines that the tag format is NDEF. If the tag type is Type 2, the NFC controller determines whether the tag format is NDEF according to the tag's Capability Container (CC). Specifically, if the CC length is 4 bytes and the value of the first byte is E1h (E1 is a hexadecimal format), the NFC controller determines that the tag format is NDEF. If the type of tag is a Type 3, NFC controller, format tag to determine whether it is therefore NDEF in S ystem Cod e tag. Specifically, when the length of the System Code is 2 bytes and the value of the System Code is 12FCh (12FC is a hexadecimal format), the NFC controller determines that the tag format is NDEF. If the tag type is Type 4, the NFC controller determines whether the tag format is NDEF according to the file identifier of the tag's Capability Container (CC) file. Specifically, if the length of the file identifier of the CC file is 2 bytes and the value of the file identifier of the CC file is E103h (E103 is a hexadecimal format), the NFC controller uses NDEF as the tag format. Determine that there is.

Optionally, if the NFC controller determines that the tag format is NDEF, the NFC controller may further determine the data type of the tag. The tag has 8 data types. Specifically, the NFC controller uses a tag (Type 1, Type 2, Type 3 and Type Obtain data type information from the TNF field in 4) and determine the tag data type according to the contents of the data type information. The value of the TNF field may be 0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, or 0x07, and the NFC controller may determine the tag data type information according to the value of the TNF field. The tag data type is specifically the NDEF message type. 0x00 indicates that the NDEF message is an empty message. 0x01 indicates that the NDEF message stores the internal data type defined in the RTD (Record Type Define) standard by the NFC Forum standard organization. 0x02 indicates that the NDEF message stores a media type defined in the RFC (Request For Comments) 2046 standard such as image and sound. 0x03 indicates that the NDEF message stores a Uniform Resource Identifier (URI) defined in the RFC 3986 standard. 0x04 indicates that the NDEF message stores the external data type defined in the RTD (Record Type Define) standard by the NFC Forum standard organization. 0x05 indicates that the NDEF message stores one piece of unknown type data. 0x06 indicates that the NDEF message is an intermediate tag in a series of consecutive NDEF tags, and the data type of the tag is the same as that of the previous NDEF tag. 0x07 indicates that the NDEF message is reserved and is not used temporarily.

In this embodiment, for example, the NFC controller transmits a notification message to the device host. For example, the notification message is a radio frequency discovery notification ( RF_DISCOVER_NTF ). The specific format of RF_DISCOVER_NTF is shown in Table 1.

Optionally, if the NFC controller determines that the tag format is not an NFC data exchange format, the NFC controller may still send a notification message to the device host. If X in the notification message ( RF_DISCOVER_NTF ) satisfies X = 0000 0000, this indicates that the tag format is not NDEF.

Optionally, the notification message sent by the NFC controller to the device host may further include a tag data type. For example, the NFC controller transmits RF_DISCOVER_NTF to the device host. The specific format of RF_DISCOVER_NTF is shown in Table 2.

Method 1: The device host transmits an initialization command to the NFC controller. After receiving the initialization command, the NFC controller transmits an initialization response to the device host. That is, the format function message is specifically an initialization response, and the initialization command is used to initialize the NFC controller. For example, the device host transmits CORE_INIT_CMD (initialization command) to the NFC controller. That is, the device host initializes the NFC controller. Next, after receiving CORE_INIT_CMD, the NFC controller feeds back CORE_INIT_RSP (initialization response) to the device host. In CORE_INIT_RSP response, S upported RF Interfac e field is 0x04, that is, if it contains NDEF Access RF Interface, which indicates that it has the ability to NFC controller detects NDEF.

Specifically, the device host transmits RF_DISCOVER_SELECT_CMD (radio frequency discovery selection command) to the NFC controller. RF_DISCOVER_SELECT_CMD contains information that the device host has established an NDEF radio frequency interface. The specific format of RF_DISCOVER_SELECT_CMD is shown in Table 6.

In Table 6, examples of meanings or values indicated by the fields are as follows.
The RF Discovery ID indicates a radio frequency discovery identifier and is used to identify a tag corresponding to radio frequency discovery.
XX indicates a tag identifier.
RF Protocol, a method of communication between the NFC controller and the tag (e.g., Tagupurotoko Le) shows a.
RF Interface shows an interface (e.g., NDEF radio frequency interface) between the device host and NFC controller.

In the implementation of this embodiment of the invention, the transmission interface between the device host and the NFC controller is clearly described. As shown in FIG. 3, before receiving a notification message that the device host is sent by NFC controller (i.e., before the device host establishes the NDEF radio frequency interface) commands between the device host and NFC Controller Transmission is performed by using NCI. After the device host receives the notification message sent by the NFC controller, the device host establishes the NDEF radio frequency interface, and NDEF data transmission between the device host and the NFC controller shall use the NDEF radio frequency interface Executed by.

Claims (22)

Reading the tag type with a near field communication (NFC) controller;
Determining, by the NFC controller, whether the format of the tag is an NFC data exchange format (NDEF) according to the type of the tag;
When the NFC controller determines by the NFC controller that the format of the tag is the NDEF, the NFC controller transmits a notification message to a device host, and the notification message includes the tag having the format of the NDEF A method of identifying a tag, comprising the steps of: Before reading the type of the tag by the near field communication (NFC) controller,
Receiving a configuration command sent by the device host by the NFC controller, wherein the configuration command is used to indicate whether the NFC controller performs NDEF detection in the tag. The method of claim 1 further comprising: Determining by the NFC controller whether the format of the tag is the NFC data exchange format (NDEF) according to the type of the tag,
If the type of the tag is Type 1, the NFC controller determines whether the format of the tag is the NDEF according to the tag header read only memory (HR) 0;
If the type of the tag is Type 2, the NFC controller determines whether the format of the tag is the NDEF according to the tag's capability container (CC);
If the type of the tag is Type 3, the NFC controller determines whether the format of the tag is the NDEF according to the tag system code (System Code);
When the type of the tag is Type 4, the NFC controller determines whether the format of the tag is the NDEF according to a file identifier of the capability container (CC) file of the tag. The method according to claim 1 or 2. Before receiving a configuration command sent by the device host by the NFC controller,
Sending a format function message to the device host by the NFC controller, the format function message holding information about whether the NFC controller has the ability to perform the NDEF detection in the tag The method according to claim 1, further comprising a step. Before sending the format capability message to the device host by the NFC controller,
The NFC controller further includes a step of receiving an initialization command transmitted by the device host,
The step of transmitting the format function message to the device host by the NFC controller,
Sending an initialization response to the device host by the NFC controller, the initialization response holding the information about whether the NFC controller has the ability to perform the NDEF detection in the tag The method according to claim 4, further comprising the step of:   The method of claim 2, wherein the configuration command is further used to indicate that the NFC controller performs data type detection on the tag. After sending the notification message to the device host by the NFC controller,
Receiving a read / write command sent by the device host by using the NDEF radio frequency interface by the NFC controller;
Converting the read / write command into an NDEF read / write command by the NFC controller;
The method according to claim 1, further comprising: performing data reading / writing in the tag according to the NDEF read / write command by the NFC controller. A reading module configured to read the tag type;
A determination module configured to determine whether the format of the tag is an NFC data exchange format (NDEF) according to the type of the tag;
When the determination module determines that the format of the tag is the NDEF, the transmission module is configured to transmit a notification message to a device host, and the notification message has the format of the tag A tag identification device comprising: a transmission module having NDEF.   A receiving module configured to receive a configuration command sent by the device host, wherein the configuration command is used to indicate whether the NFC controller performs the NDEF detection in the tag The apparatus of claim 8, further comprising a receiving module.   The determination module determines whether the format of the tag is the NDEF according to the header read-only memory (HR) 0 of the tag when the type of the tag is Type 1, and the tag If the type is Type 2, determine whether the format of the tag is the NDEF according to the tag's capability container (CC), and if the type of the tag is Type 3, the tag Determines whether the format is the NDEF according to the system code of the tag, and if the type of the tag is Type 4, the format of the tag is a capability container (CC) file of the tag 10. The apparatus according to claim 8 or 9, wherein the apparatus is specifically configured to determine whether the NDEF is according to a file identifier.   The sending module is further configured to send a format capability message to the device host, the format capability message indicating whether the NFC controller has the ability to perform the NDEF detection on the tag. 11. A device according to any one of claims 8 to 10, wherein the device is held. The receiving module is further configured to receive an initialization command sent by the device host;
The sending module is further configured to send an initialization response to the NFC controller, wherein the initialization response is the information about whether the NFC controller has the ability to perform the NDEF detection on the tag. The apparatus of claim 11, wherein   The apparatus of claim 9, wherein the configuration command is further used to indicate that the NFC controller performs data type detection on the tag. The receiving module is further configured to receive a read / write command sent by the device host by using an NDEF radio frequency interface;
A conversion module configured to convert the read / write command to an NDEF read / write command;
14. The apparatus according to any one of claims 8 to 13, further comprising: a processing module configured to perform data reading / writing in the tag according to the NDEF read / write command. A near field communication (NFC) controller and a tag identification device having a device host, the NFC controller is a tag identification device connected to the device host,
The NFC controller is configured to read a tag type and determine whether the tag format is an NFC data exchange format (NDEF) according to the tag type, wherein the tag format is the NDEF If the NFC controller determines that the NFC controller sends a notification message to the device host, the notification message has the format of the tag as the NDEF;
The tag identification device, wherein the device host is configured to receive the notification message transmitted by the NFC controller. The device host is further configured to send a configuration command to the NFC controller, and the configuration command is used to indicate whether the NFC controller performs the NDEF detection in the tag;
The apparatus of claim 15, wherein the NFC controller is further configured to receive the configuration command sent by the device host.   When the type of the tag is Type 1, the NFC controller determines whether the format of the tag is the NDEF according to a header read only memory (HR) 0 of the tag, and the tag If the type is Type 2, determine whether the format of the tag is the NDEF according to the tag's capability container (CC), and if the type of the tag is Type 3, the tag Determines whether the format is the NDEF according to the system code of the tag, and if the type of the tag is Type 4, the format of the tag is a capability container (CC) file of the tag 17. An apparatus according to claim 15 or 16, wherein said apparatus is specifically configured to determine whether said NDEF is according to a file identifier.   The NFC controller is further configured to send a format capability message to the device host, the format capability message including information about whether the NFC controller has the ability to perform the NDEF detection on the tag. 18. A device according to any one of claims 15 to 17, wherein the device is held. The device host is further configured to send an initialization command to the NFC controller;
The NFC controller is further configured to send an initialization response to the device host after receiving the initialization command sent by the device host, wherein the initialization response is received by the NFC controller in the tag. The apparatus of claim 18, wherein the apparatus retains the information as to whether it has the ability to perform the NDEF detection.   The apparatus of claim 16, wherein the configuration command is further used to indicate that the NFC controller performs data type detection on the tag.   21. The device host is further configured to establish an NDEF radio frequency interface to perform data transmission with the NFC controller after receiving the notification message sent by the NFC controller. The apparatus of any one of these. The device host is further configured to send a read / write command to the NFC controller by using the NDEF radio frequency interface;
The NFC controller receives the read / write command sent by the device host by using the NDEF radio frequency interface, converts the read / write command to an NDEF read / write command, and reads the NDEF read 23. The apparatus of claim 21, further configured to perform data read / write at the tag according to a / write command.

Images