TecTile

TecTiles NFC tags
Galaxy SIII and a pair of TecTile stickers

TecTiles are a near field communication (NFC) application, developed by Samsung, for use with mobile smartphone devices.[1]

Each TecTile is a low-cost[2] self-adhesive sticker with an embedded NFC Tag.[3] They are programmed before use, which can be done simply by the user, using a downloadable Android app.[3]

When an NFC-capable phone is placed or 'tapped' on a Tag, the programmed action is undertaken. This could cause a website to be displayed, the phone switched to silent mode, or many other possible actions.

NFC Tags are an application of RFID technology. Unlike most RFID, which makes an effort to give a long reading range, NFC deliberately limits this range to only a few inches or almost touching the phone to the Tag. This is done deliberately, so that Tags have no effect on a phone unless there is a clear user action to 'trigger' the Tag. Although phones are usually touched to Tags, this does not require any 'docking' or galvanic contact with the Tag, so they are still considered to be a non-contact technology.

Although NFC Tags can be used with many smartphones, TecTiles gained much prominence in late 2012 with the launch of the Galaxy SIII.[4][5]

Applications

Some applications are intended for customising the behaviour of a user's own phone according to a location, e.g. a quiet mode when placed on a bedside table; others are intended for public use, e.g. publicising web content about a location.[note 1] This programming is carried out entirely on the Tag. Subject to security settings, any compatible phone would have the same response when tapped on the Tag. When the Tag's response is a Facebook 'Like' or similar, this is carried out under the phone user's credentials (such as a Facebook identity), rather than the Tag's identity.

Samsung group Tags' functions under four headings:[6] Settings, Phone, Web and Social. A handful of examples:

Settings
Phone
Web
Social

Tags may also be pre-programmed and distributed to users. Such a Tag could be set to take the user to a manufacturer's service support page and sent out stuck to washing machines or other domestic whitegoods. Factory-prepared Tags can also be printed with logos, or moulded into forms apart from stickers, such as key fobs or wristbands.

Lifespan

The re-programmability of a Tag is claimed at over 100,000 programming cycles.[5]

Where a Tag is placed on a doorway or noticeboard, it may be re-programmed in situ and could thus have a long life (e.g. many conferences, meetings or events). Tags may be locked after programming,[3] to avoid unauthorized reprogramming. Locked tags may only be unlocked by the same phone that locked them.

The duration of a locked Tag's relevance will be the main constraint on Tag lifetime if unlocking is not possible. The lifespan of a Tag is also likely to be limited by physical factors such as the glue adhesion, or the difficulty of peeling them from the glue.

Compatibility

The TecTile app is not installed by default.[6] If a Tag is read before it is installed, the user is directed to the app download site.

Using a Samsung TecTile NFC tag requires a device with the MIFARE Classic chipset.[7] This chipset is based on NXP's NFC controller, which is outside the NFC Forum's standard. Using a TecTile thus requires the NXP chipset. The NXP chipset is found in many Android phones. Recently Android phone manufacturers have chosen to drop TecTile support; notably in Samsung's latest flagship phone the Galaxy S4[8] and Google's Nexus 4.[9] TecTiles also do not work with BlackBerry and Windows NFC phones. The new version of TecTile, called TecTile 2, have improved compatibility,[10] but currently the Samsung Galaxy S4 is the only device that comes with native support for TecTile 2.[11]

NFC Tags that do comply with NFC Forum Type 1 or Type 2 compatibility protocols [12] are much more widely compatible than the MIFARE dependant Samsung TecTile,[13] and are also widely available. Popular standards compliant NFC Tags are the NTAG213 (137 bytes of usable memory), and the Topaz 512 (480 bytes of usable memory).[14]

Tag encoding

The need for the installed app is one of the drawbacks to TecTile and to NFC Tags in general. The basic NFC Tag standards support Tags carrying URLs, where the scheme or protocol (e.g. the http:// prefix) may be either http (for web addresses), tel for telephony, or an anonymous data scheme. Although support for the http and tel schemes may be assumed in a basic handset, support for the others will not be available unless an App has been installed and registered to handle them.

In general, NFC Tags (in the non-TecTile sense) are only useful for web addresses and telephony.

To provide features beyond this, Samsung offers the TecTile App. This could have used any scheme on a tag, or even invented a whole new scheme. When installed, such an App would register itself to handle these new schemes. However the App is not part of the default install for a handset, even a Samsung. To allow users to install the App automatically, on first encountering a TecTile, all the TecTile's sophisticated and phone-specific features are still provided through the http scheme. The basic URL is that for initially downloading the App, details of the TecTile operation are encoded as URL parameters within the query string in addition to this.

When reading a Tag, one of two things happens:

This convoluted behaviour was chosen to make the App effectively self-installing for naive users. Why the App was not supplied as default is unknown. The downsides of this design choice though are that the URLs required to activate TecTile functions are relatively long, meaning that non-TecTile NFC Tags with limited memory size (137 bytes) cannot generally be used for functions other than web addresses. Additionally, the lack of a non-proprietary approach to these more capable functions limits the development of NFC Tags as a general technique across all such handsets, rather than just Samsung TecTiles.

Similar tag technologies

Notes

  1. ↑ This could be used to build a system similar to QRpedia.

References

This article is issued from Wikipedia - version of the 7/22/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.