NFC Services Concepts

This topic describes the additional protocols and technologies (besides the required NFC specifications) implemented by the NFC Services collection.

Note: You must be familiar with the NFC specifications (such as Connection Handover, NFC Data Exchange Format, NFC Record Type Definition (RTD) and LLCP) available at http://www.nfc-forum.org/specs/ to understand these concepts.

Also you can refer to Introduction to NFC on Nokia Developer to understand the NFC technology in general and the specifics that are supported on Nokia devices.

Reserved Record Type Definitions

The NFC implementation in Symbian platform provides support for handling following Record Type Definitions (RTD):

RTD	Identifier
Bluetooth 2.0	`urn:nfc:ext:nokia.com:bt`
Bluetooth 2.1	`application/vnd.bluetooth.ep.oob`
Handover Request	`urn:nfc:wkt:Hr`
Handover Select	`urn:nfc:wkt:Hs`
Smart Poster	`urn:nfc:wkt:Sp`
URI record	`urn:nfc:wkt:U`

MIME types supported in the NFC implementation in Symbian platform:

Type	Subtype
image	All subtypes are supported
audio	All subtypes are supported
text	All subtypes are supported
video	All subtypes are supported
application	vnd.Nokia.ringing-tone
application	vnd.symbian.install
application	java-archive
application	x-java-archive
application	vnd.wap

Note: Applications must be in the foreground to handle Reserved RTDs. It is not possible to read a Reserved NDEF from a background process.

Smart Poster RTD

The NFC Implementation provides support for handling Smart Poster RTD. For information on Smart Poster RTD, refer to NFC Forum Technical Specifications.

The Smart Poster message can have one or more records. The NFC implementation in Symbian platform supports URI record (mandatory record), and the optional records Action and Title .

The Action record specifies the action the device must perform with the content.

Value Action

0 Specifies that the action is to be done immediately

1 Specifies that the content in URL and SMS cases is to be saved for later use.
The content of the Title record is used to describe the action specified in the Action record.
The mandatory URI record contains an URI Identifier Code for specifying the URI scheme and shortening the actual URI field.

Value	Action
0	Specifies that the action is to be done immediately
1	Specifies that the content in URL and SMS cases is to be saved for later use.

The following is the list of use cases and that are supported:

**Table:** Open URL
URI Identifier Codes	Schemes
0x01	http://www.
0x02	https://www.
0x03	http://
0x04	https://

**Table:** Make a phone call
URI Identifier Codes	Schemes
0x05	tel:

**Table:** Send SMS
URI Identifier Codes	Schemes
0x00	sms:

**Table:** Open a local file or an application
URI Identifier Codes	Schemes
0x1D	file://

NFC Forum Tags

The NFC Forum has defined four tag types to enhance interoperability between different NFC tag providers and NFC device manufacturers.

Following is the list of tags defined by the NFC Forum:

NFC Forum Type 1 Tag
NFC Forum Type 2 Tag
NFC Forum Type 3 Tag
NFC Forum Type 4 Tag

For information on each tag type, refer to NFC Forum Tag Type Technical Specifications.