TNEP Explained: How NFC Tags Can Talk Back to Your Phone

Most NFC tags are simple. Your phone reads a message, and that's that. The tag never answers. TNEP, the Tag NDEF Exchange Protocol, changes that by letting a device behind the tag reply to what the phone sends. It isn't brand new, though. The NFC Forum approved it in 2020, and it mostly lives in device firmware, not on desk stickers. Here's how a conversation actually runs.

What TNEP is

The NFC Forum describes TNEP version 1.0 as a way to exchange NDEF messages in both directions. It builds on the communication already used by NFC Forum Tag Types 2, 3, 4 and 5, and it is aimed at NFC-enabled IoT devices that need to swap data with a phone. The Forum names configuring and reading smart meters, controlling thermostatic radiator valves, and setting up smart home lighting as examples.

According to NFCW's coverage, the Forum announced TNEP and an updated Connection Handover specification (version 1.5) on 19 May 2020. Because TNEP rides on the ordinary tag read and write process, a phone app that can already access tags can support it without implementing peer-to-peer mode (LLCP). The phone can check a device's status and change its settings, which is the "talk back" part.

How a TNEP exchange works

Picture a device that presents itself as a tag but has real logic behind it. Nordic's documentation for its TNEP tag library shows the typical flow. It sits on top of a Type 4 Tag.

The tag advertises its services

The device's first NDEF message holds one Service Parameter record for each service it offers. That is the menu. A reader that knows nothing about TNEP can still read the other ordinary records in the message, such as a URL, so the device stays useful to any phone. If you want a refresher on what those records look like, our piece on custom NDEF records covers the basics.

The phone selects a service and gets answers

The tag starts in a Service Ready state. When the phone writes a new NDEF message containing a Service Select record, the tag moves to Service Selected, and the menu message is no longer offered. The tag's application can then place reply data in its answer, or reply with nothing if it has nothing to say. If the application takes too long, longer than the timeout set in the service's parameters, the phone deselects the service.

In short: read the menu, pick an item, write a request, read the response. It's all NDEF.

Connection handover: from a tap to Bluetooth

One service that uses TNEP is Connection Handover, which lets a tap set up a faster link. With Connection Handover 1.5, the NFCW report says TNEP allows negotiated handover between a reader or writer and a tag, which was previously limited to peer-to-peer connections. The idea is to use NFC for the introduction, then move large transfers or streaming to Bluetooth or Wi-Fi, such as Bluetooth audio or a photo sent from a camera.

Nordic's handover documentation separates two modes:

• Static handover: the phone just reads a Handover Select message from the tag. TNEP is not involved.
• Negotiated handover: the requester sends a Handover Request listing the carriers it supports, and the other side answers with a Handover Select naming the ones both sides share. TNEP carries those messages.

In Nordic's sample, the pairing data travels as Bluetooth LE out-of-band records, including the device address and secure connection data, so the devices can connect without a manual pairing step.

Where you'll see it

Expect TNEP in products, not craft projects. Meters, radiator valves, lighting and similar devices benefit because a tap can both read their state and change their settings,. For a related look at tap-based setup, see our article on tap-to-pair smart-home setup. Support is the manufacturer's call, so check a product's documentation.

What it means for your NFCore tags

An ordinary NTAG sticker only stores data. It cannot run a service or reply after your phone writes to it, so it cannot do TNEP. The tags you use for business cards, Wi-Fi sharing or automations rely on standard NDEF records, and that is what NFCore reads and writes. TNEP matters when you build or buy a device that has its own microcontroller and wants a two-way tap conversation.

If you are working with everyday tags, you can read, write and organize NDEF messages with NFCore, available on the App Store and Google Play.

Frequently Asked Questions

Is TNEP new?

No. The NFC Forum announced TNEP 1.0 and Connection Handover 1.5 on 19 May 2020. It remains a niche protocol, mostly found in device firmware.

Can an ordinary NTAG sticker do TNEP?

No. TNEP needs something that can run logic and answer after a write, such as a chip connected to a microcontroller. A passive sticker only holds data.

Can my phone read a TNEP device without TNEP support?

Often, yes, for the plain NDEF records. The initial message can carry ordinary records that readers without TNEP support still see, though they cannot use the services.

Does NFCore write TNEP services?

NFCore works with standard NDEF records. It is not documented as a TNEP tool, so treat TNEP as a device-side feature.