In addition to the signaling technologies used by near field communication technology,including NFC TAG Type 1, type 2 nfc tag,NFC TAG Type 3,NFC TAG Type 4 exist. Tag types refer to the speed and compatibility between an NFC tag and NFC readers, and the roles define how active and passive devices respond during a NFC communication. Most often a URL will be embedded in a NFC tag. URLs take up only a small amount of memory, lowering the production cost of the NFC tags since many are placed on posters or other items that are thrown away later on. NFC tags can, however, hold nearly any type of information, though more memory costs more money.
NFC Tags let you perform various kinds of information-related tasks. For example, you can use a tag to store information on various topics at a kiosk. Each tag has specific functionality that lets you use the tag for particular tasks. NFC currently works with the following four tag types:
NFC TAG Type 1:
The NFC Type 1 tag is the simplest of the offerings. It’s also the slowest chip, but because of the simplicity it offers, you can stuff more memory on this chip. Because these tags are simple, they also tend to be inexpensive, but they can lack functionality you might need for some applications.Type 1 NFC tags have data collision protection and can be set to either read and rewrite capable or read-only. Read-only programming prevents the information from being changed or written over once embedded in the tag. Type 1 tags have 96 bytes of memory, enough for a URL or a small amount of data. The tag’s memory can expand to a larger size as needed. The low price makes type 1 tags to ideal choice for most near field communication needs.
The typically Application :tags used for the following types of applications:
One time provisioning
Pairing devices with Bluetooth
Reading a specific tag when more than one tag is present
NFC TAG Type 2:
Type 2 NFC tags also have data collision protection and can be rewriteable or read-only. They start at 48 bytes of memory, half of what the type 1 tags can hold, but can expand to be as large as a type 1 tag. Communication speeds are the same for tag types 1 and 2.
The Type 2 tag tends to be the most popular offering because it provides just enough functionality at the right price to meet a wide range of needs. The Type 2 tag is also faster than the Type 1 tag, so you can rely on it for applications in which a user expects nearly instant communication. You typically see these tags used The typically Application:
Day transit passes
NFC TAG Type 3:
Also equipped with data collision protection, NFC tag type 3 has larger memory and faster speeds than tag types 1 and 2. This tag is part of the FeliCa system. The bigger size lets it hold more complex codes beyond URLs, but it costs more to create each tag.The Type 3 tag relies on a different standard than the other tags in this group. The Sony FeliCa tag is a Japanese innovation and sees wide use in Asia. This is a sophisticated tag that provides a wide range of functionality but also comes with a relatively high price tagtypes of applications:
Health care devices
NFC TAG Type 4:
Type 4 NFC tags can use either NFC-A or NFC-B communication and have data collision protection. The tag is set as either rewritable or read-only when manufactured and this setting cannot be changed by the user, unlike the other NFC tags which can be altered at a later date. The tag holds 32 Kbytes in memory and has faster speeds than the other tags.
In addition to the four tag types, four modes of operation exist. The modes – reader/writer, card, initiator, and target – describe what role a device or tag is playing in an NFC transaction. Devices can switch between more than one role depending on the transaction being processed. The Type 4 tag offers the most flexibility and memory of all the tags. It comes with a moderate to high price tag, depending on the amount of memory you get. The most important reason to get this tag is security: It offers the functionality needed to perform true authentication. In addition, this is the only tag that provides support for ISO 7816 security. It also allows for self-modification of NDEF content. Given the extra capability that this tag provides, you typically see it used for transit ticket applications.