Devices Requirements
High Level Conformance Requirements
Version 3.2.00
2022-06-02[DEVREQS]NFC ForumTM

Copyright © 2010-2022 NFC ForumContents

Contents
1 Overview ........................................................................................................ 5
1.1
1.2
1.3
1.4
1.5
1.6
1.7

Objectives ...................................................................................................................... 5
Applicable Documents or References ........................................................................... 5
Administration ............................................................................................................... 7
Intellectual Property ...................................................................................................... 7
Special Word Usage ...................................................................................................... 7
Abbreviations ................................................................................................................ 8
Glossary ......................................................................................................................... 8

2 Technology Definitions ............................................................................... 10
3 NFC Forum Devices .................................................................................... 11
3.1
3.2
3.3

Open ecosystem Device Classes.................................................................................. 12
Specific market ecosystem Device Classes ................................................................. 14Interoperability assessment of Device Classes of both categories .............................. 15

4 Interoperability Modules ............................................................................. 17
4.1

4.2
4.3

Interoperability Modules Overview............................................................................. 17
4.1.1
Reader/Writer Module .................................................................................. 17
4.1.2
Peer Modules ................................................................................................ 18
4.1.3
Card Emulation Modules .............................................................................. 18
4.1.4
Tag Modules ................................................................................................. 18
4.1.5
RF Collision Avoidance Module .................................................................. 19
4.1.6
Wireless Charging Poller Module................................................................. 19
4.1.7
Wireless Charging Listener Module ............................................................. 19
Interoperability of Modules ......................................................................................... 19
Requirements to Modules Mapping ............................................................................ 20

5 NFC Forum Requirements .......................................................................... 28
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
5.13

Requirements Terms.................................................................................................... 28
RF Requirements ......................................................................................................... 31
Requirements for NFC Forum Peer Mode .................................................................. 31
Requirements for NFC Forum Reader/Writer Mode ................................................... 32
Requirements for NFC Forum Card Emulation and Tag Mode .................................. 35
Requirements for NFC Forum Type 2 Tag Module .................................................... 36
Requirements for NFC Forum Type 3 Tag Module .................................................... 37
Requirements for NFC Forum Type 4A and 4B Tag Modules ................................... 38
Requirements for NFC Forum Type 5 Tag Module .................................................... 39
Tag Performance Requirements .................................................................................. 40
Wireless Charging Mode Requirements ...................................................................... 40
Requirements for NFC Forum Certification ................................................................ 41
Operating Volume and Reference Equipment ............................................................. 41

A. Use Cases .................................................................................................... 44
A.1
A.2
A.3

NFC Forum Communication Use Cases ..................................................................... 44
NFC Forum Wireless Charging Use Case ................................................................... 46
Legacy Communication Use Cases ............................................................................. 47

B. List of Device Classes containing other Device Classes ......................... 50
C. NFC Forum Architecture ............................................................................. 52
C.1

NFC Forum Device ..................................................................................................... 52

Devices Requirements

Page iContents
C.2

C.3

C.4

NFC Forum Protocol Stack ......................................................................................... 52
C.2.1
L1 and L2 - Analog and Digital Protocol Layers ......................................... 53
C.2.2
L2 - Logical Link Control Protocol .............................................................. 54
C.2.3
L4 and Up – Type X Tag Operation ............................................................. 54
C.2.4
L4 and Up – NDEF and RTDs...................................................................... 54
C.2.5
Protocol Partitioning ..................................................................................... 55
Operation Modes ......................................................................................................... 55
C.3.1
NFC Forum Peer Mode................................................................................. 55
C.3.2
NFC Forum Reader/Writer Mode ................................................................. 56
C.3.3
NFC Forum Tag Modes ................................................................................ 57
Device Architecture ..................................................................................................... 58
C.4.1
Generic Polling Architecture ........................................................................ 58
C.4.2
Generic Listening Architecture ..................................................................... 60

D. Revision History .......................................................................................... 62

Devices Requirements

Page ii

Figures

FiguresFigure 1: Conventions for Use Case Diagrams ............................................................................. 44
Figure 2: Two NFC Forum Devices Communicating in NFC Forum Peer Mode ........................ 45
Figure 3: NFC Forum Device in NFC Forum Reader/Writer Mode Communicating with an NFC
Forum Tag ..................................................................................................................................... 45
Figure 4: NFC Forum Device in NFC Forum Reader/Writer Mode Communicating with an NFC
Forum Device in NFC Forum Card Emulation Mode ................................................................... 46
Figure 5: NFC Forum Device in NFC Forum Reader/Writer Mode Communicating with an NFC
Forum Card Emulation Device ...................................................................................................... 46
Figure 6: NFC WLC Poller (WLC-P) is communicating and charging a NFC WLC Listener(WLC-L)........................................................................................................................................ 47
Figure 7: NFC Forum Device in NFC Forum Reader/Writer Mode Communicating with a SC .. 48
Figure 8: NFC Forum Device in NFC Forum Reader/Writer Mode Communicating with an NFC
Forum Device Emulating a SC ...................................................................................................... 48
Figure 9: Reader/Writer Terminal and NFC Forum Device Emulating a SC ............................... 49
Figure 10: Peer Mode Architecture ............................................................................................... 56
Figure 11: Reader/Writer Mode Architecture ............................................................................... 57
Figure 12: Tag Mode Architecture ................................................................................................ 58
Figure 13: Generic Polling Architecture ....................................................................................... 59
Figure 14 Generic Listening Architecture ..................................................................................... 60

TablesTable 1: Abbreviations .................................................................................................................... 8
Table 2: Open ecosystem NFC Forum Device Classes to interoperability module mapping ....... 12
Table 3: Specific market ecosystem devices to interoperability module mapping........................ 14
Table 4: NFC Forum Device interoperability................................................................................ 15
Table 5: Modules – Interoperability .............................................................................................. 20
Table 6: Generic requirements to modules mapping ..................................................................... 21
Table 7: Peer Mode requirements to interoperability modules mapping ...................................... 22
Table 8: Reader/Writer Mode requirements to module mapping .................................................. 22
Table 9: Card Emulation and Tag Mode requirements to module mapping ................................. 24
Table 10: DTA requirements to module mapping ......................................................................... 27
Table 11: WLC Mode Requirements to module mapping ............................................................ 27
Table 12: Requirements Terms ..................................................................................................... 28
Table 13: RF Requirements ........................................................................................................... 31

Devices Requirements

Page iii

Tables
Table 14: Requirements for NFC Forum Peer Mode .................................................................... 31
Table 15: Requirements for NFC Forum Reader/Writer Mode .................................................... 32
Table 16: Requirements for NFC Forum Tag Platform and Module ............................................ 35
Table 17: Requirements for NFC Forum Type 2 Tag Module ...................................................... 36
Table 18: Requirements for NFC Forum Type 3 Tag Module and Platform ................................ 37
Table 19: Requirements for NFC Forum Type 4A and 4B Tag Modules ..................................... 38
Table 20: Requirements for NFC Forum Type 5 Tag Module ...................................................... 39
Table 21: Tag Performance Requirements .................................................................................... 40
Table 22: Wireless Charging Mode Requirements........................................................................ 40
Table 23: Test Requirements ......................................................................................................... 41
Table 24 Reference Equipment and Operating Volume definition per Device Class ................... 43
Table 25: Device Class coverage of other Device Classes ............................................................ 50
Table 26: OSI Protocol Stack Mapping......................................................................................... 52
Table 27: Revision History............................................................................................................ 62

Devices Requirements

Page iv

Overview

1 Overview
The NFC Forum publishes a set of technical specifications for Near Field Communications
technology. The purpose of this document is to define which high level features of the NFC
Forum specifications are necessary to be implemented by a device for it to be eligible to receive
the NFC Forum Certification Mark. These high level features are identified as requirements(marked by ‘SHALL’ statements) in this document.

1.1

Objectives

The objective of this requirements document is to specify the sets of functionalities and featuresthat need to be supported by NFC-Forum-compliant devices to ensure basic interoperability. The
term “basic interoperability” requires conformance to the specifications listed in Section 1.2.

1.2

Applicable Documents or References

The documents listed below contain provisions that are referenced in this specification. Unless apublication date is explicitly stated, the latest version of each document, including all publishedamendments, applies.
[ACTIVITY]

NFC Activity Technical Specification,
Version 2.1,
NFC Forum[ANALOG]NFC Analog Technical Specification,
Version 2.1,
NFC Forum[DIGITAL]NFC Digital Protocol Technical Specification,
Version 2.2,
NFC Forum[GLOSS_CC]

Compliance Committee Glossary(available at http://nfc-forum.org)
NFC Forum[GLOSS_TC]

Technical Acronyms and Glossary
NFC Forum[DEVINFO]

Device Information Record Type Definition Technical Specification
NFC Forum[DTA]

Device Test Application Specification,
Version 2.4,
NFC Forum[LLCP]NFC Logical Link Control Protocol (LLCP) Technical Specification,
Version 1.2,
NFC Forum[NCI]

NFC Controller Interface Technical Specification
NFC Forum[NDEF]NFC Data Exchange Format (NDEF) Technical Specification,
Version 1.0,
NFC Forum

Devices Requirements

Page 5

Overview[PERF]Tag Performance Requirements
Version 1.0,
NFC Forum[RFC2119]

Key words for use in RFCs to Indicate Requirement Levels,
RFC 2119,
S. Bradner,
March 1997,
Internet Engineering Task Force[RTD]

NFC Record Type Definition,
Technical Specification,
Version 1.0,
NFC Forum[SNEP]NFC Simple NDEF Exchange Protocol (SNEP) Technical
Specification,
Version 1.0,
NFC Forum[SIGNATURE]

Signature Record Type Definition Technical Specification
NFC Forum[SMARTPOSTER]

Smart Poster Record Type Definition Technical Specification
NFC Forum[T2T]

NFC Forum Type 2 Tag Specification
Technical Specification,
Version 1.1,
NFC Forum[T3T]

NFC Forum Type 3 Tag Specification
Technical Specification,
Version 1.1,
NFC Forum[T4T]

NFC Forum Type 4 Tag Specification
Technical Specification,
Version 1.1,
NFC Forum[T5T]

NFC Forum Type 5 Tag Specification
Technical Specification,
Version 1.1,
NFC Forum[TEXT]

Text Record Type Definition
Technical Specification,
NFC Forum[URI]

Universal Resource Identifier (URI) Record Type Definition
Technical Specification,
NFC Forum[VERB]

Verb Record Type Definition
Technical Specification,
NFC Forum

Devices Requirements

Page 6

Overview[WLC]

Wireless Charging Specification
Technical Specification,
Version 2.0
NFC Forum

If the manufacturer decides to implement a device based on a newer version of the NFC Forumspecifications, that device remains eligible to receive NFC Forum Certification, assuming the
manufacturer confirms functional compliance of the device to the specifications listed above.
This confirmation is given as part of the application for NFC Forum Certification for the device.

1.3

Administration

This document is supported and maintained by the Near Field Communication Forum, Inc.,located at:
401 Edgewater Place, Suite 600
Wakefield, MA, 01880
Tel.: +1 781-876-8955
Fax: +1 781-610-9864
http://www.nfc-forum.org/

1.4

Intellectual Property

This document conforms to the Intellectual Property guidelines specified in the NFC Forum'sIntellectual Property Rights Policy (NFC-Forum-IPR-Policy.pdf), as outlined in the NFC Forum
Rules of Procedure (NFC-Forum-Rules-of-Procedure.pdf).

1.5

Special Word Usage

The key words “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, and “MAY” in thisdocument, with the exception of the RESTRICTION ON USE section, are to be interpreted as
described in [RFC2119].

Devices Requirements

Page 7

Overview

1.6

Abbreviations
Table 1: Abbreviations

Abbreviation

Description

ACM

Active Communication Mode

APDU

Application Protocol Data Unit

CCC

Car Connectivity Consortium®

CMD

CommandCE

Card Emulation

DTA

Device Test Application

IEC

International Electrotechnical Commission

ICS

Implementation Conformance Statement

ISO

International Organization for Standardization

LLCP

Logical Link Control Protocol, as defined in [LLCP]NDEF

NFC Data Exchange Format, as defined in [NDEF]

NFC

Near Field Communication

NMD

NFC Mobile Device

OSI

Open Systems Interconnection

P2P

NFC Forum Peer Mode, based on peer-to-peer communication

PCM

Passive Communication Mode

RW

Read / Write

RF

Radio Frequency

RTD

Record Type Definition

SMS

Short Message Service

URI

Universal Resource Identifier

USI

Universal Stylus Initiative

WLC

Wireless Charging

1.7

Glossary

For the definitions of Glossary terms see [GLOSS_CC] and [GLOSS_TC].
Normal Power Mode
The Device is sufficiently powered to operate all functions in the device including allfunctions supported by the NFC interface.

Devices Requirements

Page 8

Overview
Reduced Power Mode
The Devices power supply is insufficient to operate all its functions (e.g., the Battery hasreached a threshold to indicate low Battery). In this case most functionalities of theDevice are automatically switched off. The device however has sufficient power tosupport the NFC controller to execute all the functions for the card emulation mode.
NOTE

In this mode the supply voltage available to the NFC controller may be
reduced and other inputs like the system clock of the devcice may not be
available.

NOTE

In the Reduced Power Mode it is assumed that no other mode than the cardemulation mode is available. Therefore only this mode will be in the scopefor certification testing.

NOTE

In other standards the Reduced Power Mode is also known as Battery Low
Mode.

Communication
Process of transferring data (information) between two NFC Devices.
Charging
Process of transferring power from an NFC WLC Reader to an NFC WLC Tag using themagnetic field of the Operating Field.

Devices Requirements

Page 9

Technology Definitions

2 Technology Definitions
In this document the terms NFC-A, NFC-B, NFC-F and NFC-V are used when referring to NFC
Forum Devices. The terms ISO/IEC 14443A, ISO/IEC 14443B, JIS X 6319-4 (also known as
FeliCa) and ISO/IEC 15693 are used for the equivalent technologies that are not defined by the
NFC Forum.

Devices Requirements

Page 10

NFC Forum Devices

3 NFC Forum Devices
An NFC Forum Device consists of one or more interoperability modules, as defined in Section 4.
Section 3 defines classes of NFC Forum Devices by mapping the interoperability modules to theimplementation requirements of specific NFC Forum Devices. Then this section shows theinteroperability between NFC Forum Devices.
NFC Forum distinguishes between two categories of Device Classes. The first category, as
detailed in section 3.1, defines Device Classes ensuring interoperability between all Device
Classes. This category ensures interoperability in an open ecosystem across all Device Classes
and therefore is strongly recommended by NFC Forum. The second category of Device Classes,
as detailed in section 3.2, is defined to meet requirements of specific market segments and isdenoted as specific market ecosystem. The Device Classes defined for a specific market
ecosystem are interoperable within that market segment. However, those specific Device Classes
do not interoperate in the open ecosystem since not all interoperability modules mandatory for the
open ecosystem are implemented. NFC Forum introduces this second category to addressapplication needs of specific market segments. Specific market ecosystem devices are to be
implemented only for the designated market segments, and not available for other market
segments.
NOTE

This definition of an NFC Forum Device deviates from the definition of an NFC Forum Device
contained in the previous versions of the Devices Requirements document up to version 1.5(when only one class of NFC Forum Device existed). The term 'NFC Forum Device' changed
from describing a specific device implementation to a general term that can be replaced by any
defined NFC Forum Device Class.

An NFC Forum Device SHALL implement at least one specific class of NFC Forum Device (asdefined in sections 3.1 or 3.2).
This document uses the following requirement levels:•

Mandatory (M) – for features that SHALL be implemented•

Optional (O) – for features that MAY be implemented•

Conditional (C) – for subfeatures that SHALL be implemented if the parent optionalfeature is implemented or the parent feature is mandatory.

A device that implements a certain class of NFC Forum Device SHALL implement all modules
that are marked as mandatory for that class.
A device that implements a certain class of NFC Forum Device MAY implement any or all
modules that are marked as optional for that class.
A device that implements a certain class of NFC Forum Device SHALL implement every modulethat is marked as conditional for that class when the condition related to that module is set true.
A device that is claimed to implement one or more classes of NFC Forum Device SHALL not
support modules (requirements) that are not part of the claimed NFC Forum Device classes.
However, an NFC Forum Device is allowed to support multiple NFC Forum Device classes.
Some tables below contain Gray colored fields or cells to indicate that for the device classs orinteroperability module the property is undefined.

Devices Requirements

Page 11

NFC Forum Devices

3.1

Open ecosystem Device Classes

This section defines the Device Classes dedicated to the open ecosystem ensuring use caseindependent interoperability. Table 2 defines the Device Class to interoperability module
mapping.

O3

M

M

M

O3

O2 O2

O2

C1,2 C1,2 C1,2

O3

M

NFC Type 3
Tag

M

NFC Type
4A TagM

NFC Type
4B TagM

NFC Type 5
Tag

M

WLC Reader Device O M O3 O3 O3 M3M
O2 O2,3 O2,3 O2,3 O2,3

WLC Tag Device

NOTE

WLC ListenerO3

O M M M M M

NFC Type 2
Tag

WLC PollerType 5 Tag Module

T 4B T Platform

Type 4B Tag Module

T 4A T Platform

O

Type 4A Tag Module

T3T Platform

O

Type 3 Tag Module

ACM

O

Type 2 Tag Module

PCM

TargetACM

O1

NFC Card
Emulation Device

NFC Tag Device

Initiator
PCM

M

T4BT OPO1

T4AT OPM

T3T OPM M M M M M

NFC Mobile Device M M M M M M
NFC Reader
DeviceCard
EmulationMode

T5T OPNFC Universal
DeviceReader / Writer

T2T OPNFC Forum Device/ Module

RF Collision Avoidance

Table 2: Open ecosystem NFC Forum Device Classes to interoperability module mapping

O1: None or all options marked as O1 for a Device Class SHALL be selected.
O2: It is mandatory for a device to select at least one of the listed options.
C1: If the feature is selected the respective platform must also be selected.
C2: At least one module must be selected if the optional WLC Listener module issupported.

Devices Requirements

Page 12MNFC Forum Devices
O3 or M3: Please check the NFC Forum webpage if this feature is already available
for certification.
From this version of Devices Requirements onwards the T1T OP interoperability module isremoved.
Appendix B analysis which Devices Classes are contained in another Device Class.

Devices Requirements

Page 13

NFC Forum Devices

3.2

Specific market ecosystem Device Classes

This section defines the Device Classes dedicated to specific market segments to enable a single
particular use case, called, specific market ecosystem. Table 3 defines the Device Class tointeroperability module mapping.
To serve the specific needs of the automotive industry the following automotive Device Classes
are defined: CCC Digital Key Reader Device and CCC Digital Key CE Device.

CCC Digital Key
Reader DeviceO

CCC Digital Key
CE Device
USI WLC Reader
DeviceWLC Listener

WLC Poller

T4BT Platform
Type 2 Tag Module
Type 3 Tag Module
Type 4A Tag Module
Type 4B Tag Module
Type 5 Tag Module

T4AT Platform

TargetInitiator

T5T OP
PCM
ACM
PCM
ACM
T3T Platform

T4AT OP

Platform
NDEF support
Platform
NDEF support

T4BT OP

T3T OPNDEF support

Platform

T2T OPNFC Forum Device/ Module

RF Collision Avoidance

Reader / Writer

Card
Emulation
Mode

Table 3: Specific market ecosystem devices to interoperability module mapping

O O1 M O O O1
O M O

O M

M

It is mandatory for CCC Digital Key CE Devices to support Normal Power and Reduced Power
Mode for each supported Tag Platform.
NOTE

O1: If the feature is selected the respective platform must also be selected.

NOTE

No USI WLC Tag Device Class is defined because it is implicitly covered by the
WLC Tag Device implementing Type 2 Tag and claiming support for WLC OV 7.

Devices Requirements

Page 14

NFC Forum Devices

3.3

Interoperability assessment of Device Classes of bothcategories

The interoperability on communication level between different Device Classes is analyzed inTable 4. This table contains the Device Classes defined for the open ecosystem as well as for the
specific market ecosystem. Green colored cells indicate interoperability between the combinationof Device Classes. Yellow colored cells indicate that interoperability between the Device Classes
is only provided if an optional feature is implemented. Red colored cells indicates noninteroperability between the combination of Device Classes.
The interoperability analysis of Table 4 shows that interoperability is provided only for open
ecosystem Device Classes. Interoperability between specific market ecosystem Device Classes
and open ecosystem Device Classes is only provided for specific Device Classes and not ingeneral. No interoperability can be assumed for specific market ecosystem Device Classes notbelonging to the same ecosystem segment.

NFC Mobile Device

NFC Reader Device

NFC CE Device

NFC Type 2 Tag

NFC Type 3 Tag

NFC Type 4A Tag

NFC Type 4B Tag

NFC Type 5 Tag

WLC Reader Device

WLC Tag Device

CCC Digital Key Reader Device

CCC Digital Key CE Device

NFC Universal Device

X

X

X1

X

X

X

X

X

X

X1

X

X1

X

NFC Mobile Device

X

X

X

X

X

X

X

X

X

X

X

X

X

NFC Reader Device

X

1

X

X

X

X

X

X

X

NFC CE Device

X

X

X

X

X4

NFC Type 2 Tag

X

X

X

X

X5

X

NFC Type 3 Tag

X

X

X

X

X3

X6

NFC Type 4A Tag

X

X

X

X

X

X6

NFC Type 4B Tag

X

X

X

X

X3

X6

NFC Type 5 Tag

X

X

X

X

WLC Reader Device

X1

X

NFC Tag Device

NFC Tag Device

Device Name

WLC Tag Device

X

X

CCC Digital Key Reader
DeviceX1

X

CCC Digital Key CE Device

X

X

USI WLC Reader Device

Devices Requirements

X

X

X

X

X

X

X

X
X5

X3

X

X

X3

X

X
X6

X6

X6

X
4

X4

X
X

X

X6

X
X4

X6

USI WLC Reader Device

NFC Universal Device

Table 4: NFC Forum Device interoperability

X2
X

X
X2

Page 15

NFC Forum Devices
NOTE

X1: A device can communicate with an NFC Universal Device if the opional CE
Mode is supported.
X2: USI WLC Reader Device can communicate with a WLC Tag Device
implementing the Type 2 Tag Module.
X3: CCC Digital Key Reader Device can communicate with a NFC Tag Device if
supporting the optional Type 3 Tag or Type 4B Tag Platform.
X4: CCC Digital Key Reader Device can communicate with a WLC Tag Device or
CE Device implementing T4AT or if both are supporting the optional Type 3 Tag or
Type 4B Tag Platform.
X5: CCC Digital Key Reader Device can activate a T2T Platform.
X6: USI WLC Reader Device can communicate with an NFC Tag if the according

optional Tag Type is supported.

Devices Requirements

Page 16

Interoperability Modules

4 Interoperability Modules
A number of interoperability modules have been defined for devices implementing NFC Forumspecifications. Each of these modules has an associated set of requirements.

4.1

Interoperability Modules Overview

This section lists and defines the modules that serve as the foundation for interoperability
between NFC Forum Devices.
The defined interoperability modules are:
•

•

•

•

Reader/Writer ModulesoType 2 Tag OperationoType 3 Tag OperationoType 4A Tag OperationoType 4B Tag OperationoType 5 Tag Operation

Peer Modules:oInitiator ModuleoTarget Module

Card Emulation ModulesoType 3 Tag Platform ModuleoType 4A Tag Platform ModuleoType 4B Tag Platform Module

Tag Modules:oType 2 Tag ModuleoType 3 Tag ModuleoType 4A Tag ModuleoType 4B Tag ModuleoType 5 Tag Module.

•

RF Collision Avoidance Module•

Wireless Charging Poller Module•

Wireless Charging Listener Module

4.1.1 Reader/Writer Module
The Reader/Writer Module covers the behavior of an NFC Forum Device implementing Poll
Mode behavior in combination with the Reader/Writer functionality, as defined by [DIGITAL]
and [ACTIVITY]. This includes the ability to read and/or write to a Type 2 Tag, Type 3 Tag,
Type 4A Tag, Type 4B Tag and Type 5 Tag.

Devices Requirements

Page 17

Interoperability Modules

4.1.2 Peer Modules
4.1.2.1

Initiator Module

The Initiator Module covers the behavior of an NFC Forum Device implementing Poll Modebehavior using either ACM or PCM in combination with the Initiator functionality, as defined by[DIGITAL] and [ACTIVITY]. The Initiator Module using ACM generates an Operating Field
only when it sends a frame to a peer device, as defined by [DIGITAL] and [ACTIVITY].

4.1.2.2

Target Module

The Target Module covers the behavior of an NFC Forum Device implementing Listen Modebehavior in combination with the Target functionality, as defined by [DIGITAL] and[ACTIVITY]. The Target Module uses PCM in case the Initiator uses PCM and uses ACM incases the Intiator uses ACM. The Target Module using ACM generates an Operating Field only
when it sends a frame to a peer device, as defined by [DIGITAL] and [ACTIVITY].

4.1.3 Card Emulation Modules
The Card Emulation Mode is offered for 3 different Tag Platforms, the Type 3 Tag, Type 4A Tag
and Type 4B Tag Platforms.

4.1.3.1

Type 3 Tag Platform

The Type 3 Tag Platform Module covers the behavior of an NFC Forum Device implementing
Listen Mode behavior in combination with the Type 3 Tag Platform functionality, as defined by[DIGITAL] and [ACTIVITY].

4.1.3.2

Type 4A Tag Platform

The Type 4A Tag Platform Module covers the behavior of an NFC Forum Device implementing
Listen Mode behavior in combination with the Type 4A Tag Platform functionality, as defined by[DIGITAL] and [ACTIVITY].

4.1.3.3

Type 4B Tag Platform

The Type 4B Tag Platform Module covers the behavior of an NFC Forum Device implementing
Listen Mode behavior in combination with the Type 4B Tag Platform functionality, as defined by[DIGITAL] and [ACTIVITY].

4.1.4 Tag Modules
The Tag Module is offered for 5 different Tag Types, the Type 2 Tag, Type 3 Tag, Type 4A Tag,
Type 4B Tag and Type 5 Tag.

4.1.4.1

Type 2 Tag Module

The Type 2 Tag Module covers the behavior of an NFC Forum Device implementing Type 2 Tag
Platform and Type 2 Tag functionality, as defined by [T2T], [DIGITAL] and [ACTIVITY].

4.1.4.2

Type 3 Tag Module

The Type 3 Tag Module covers the behavior of an NFC Forum Device implementing Type 3 Tag
Platform and Type 3 Tag functionality, as defined by [T3T], [DIGITAL] and [ACTIVITY].

4.1.4.3

Type 4A Tag Module

The Type 4A Tag Module covers the behavior of an NFC Forum Device implementing Type 4A
Tag Platform and Type 4A Tag functionality, as defined by [T4T], [DIGITAL] and [ACTIVITY].

Devices Requirements

Page 18

Interoperability Modules

4.1.4.4

Type 4B Tag Module

The Type 4B Tag Module covers the behavior of an NFC Forum Device implementing Type 4B
Tag Platform and Type 4B Tag functionality, as defined by [T4T], [DIGITAL] and [ACTIVITY].

4.1.4.5

Type 5 Tag Module

The Type 5 Tag Module covers the behavior of an NFC Forum Device implementing Type 5 Tag
Platform and Type 5 Tag functionality, as defined by [T5T], [DIGITAL] and [ACTIVITY].

4.1.5 RF Collision Avoidance Module
The RF Collision Avoidance Module covers the behavior of an NFC Forum Device implementing
the Listen before Talk approach in Poll mode as defined in [ACTIVITY].

4.1.6 Wireless Charging Poller Module
The Wireless Charging Module covers the behavior of an NFC Forum Device implementing thewireless charging functionality for the Poll mode as defined in [WLC].

4.1.7 Wireless Charging Listener Module
The Wireless Charging Module covers the behavior of an NFC Forum Device implementing thewireless charging functionality for the Listen mode as defined in [WLC].

4.2

Interoperability of Modules

This section provides an overview of the interoperability between the defined modules.
Interoperability is defined so that two NFC Forum Devices are able to interact and communicate
with each other. This means that certain modules implemented in the two NFC Forum Devices
are interoperable.
Table 5 defines the interoperability between modules in a matrix. No interoperability is definedfor the gray colored (both dark and light gray) fields.
NOTE

Type 2 Tag and Type 5 Tag are not emulated on a device.

NOTE

RF Collision Avoidance ensures that two NFC Forum Devices are not in Poll mode at the sametime and therefore enables basic interoperability (Listen before Talk). The below interoperability
analysis applies once RF collision avoidance was already successfully performed. Therefore RF
Collision Avoidance will not be shown in Table 5.

Devices Requirements

Page 19

Interoperability Modules
Table 5: Modules – Interoperability
Initiator

Reader/Writer

WLC Poller

PCM

Type 5 Tag Operation

Type 4B Tag Operation

Type 4A Tag Operation

Type 3 Tag Operation

Type 2 Tag Operation

Type 5 Tag Operation

Type 4B Tag Operation

Type 4A Tag Operation

Type 3 Tag Operation

ACM

PCM

REPLICA

Type 2 Tag Operation

PRIMARY

X

TargetACM

X

Type 3 Tag Platform

X

Type 4A Tag Platform

X

Type 4B Tag Platform
Type 2 Tag Module
Type 3 Tag Module
Type 4A Tag Module

X
X
X
X

Type 4B Tag Module

WLC Listener

Type 5 Tag Module
Type 2 Tag Module
Type 3 Tag Module
Type 4A Tag Module
Type 4B Tag Module
Type 5 Tag Module

4.3

X
X
X
X
X
X
X

Requirements to Modules Mapping

Table 6 to Table 11 map the individual defined requirements grouped by functionality to the NFC
Forum interoperability modules and indicates its applicability. If no requirement of a groupapplies to an NFC Forum interoperability modules, for simplicity such interoperability modules
are not shown.

Devices Requirements

Page 20

Interoperability Modules

REQ-1.B

M

M

Type 4B Tag Platform

M

Type 4A Tag Platform

ACM

M

Type 3 Tag Platform

PCM

TargetInitiator
ACM

REQ-1.A

PCM

Reader/Writer

Number

RF Collision Avoidance

Table 6: Generic requirements to modules mapping

Comment

Peer mode

M

Read/Writer (RW)

REQ-1.CC

C

C

Card Emulation

REQ-1.1C

C1

C1

C1

CE support in Normal Power Mode

REQ-1.2C

C2

C2

C2

CE support in Reduced Power Mode

REQ-2.A

M

M

Poll Mode

REQ-2.B

M

REQ-2.C

M

C

C

C

C

REQ-3.A
REQ-3.1A

Listen Mode
RF Collision AvoidanceM

NFC Tag detectionM

5 second NFC Tag detection

REQ-3.B
REQ-3.1B
REQ-4.A

M

REQ-4.B

M

REQ-4.C

M

REQ-4.D

M

M

M

NFC Universal Device DetectionMM

5 second NFC Universal Device
detection

M

Poll for NFC-A Technology
Poll for NFC-B Technology

M

Poll for NFC-F Technology
Poll for NFC-V Technology

REQ-5

VOID

REQ-6

M

M

REQ-7

M

M

M

M

M

NDEF forming

REQ-8

M

M

M

M

M

NDEF accepting

REQ-RF-1

M

M

M

M

M

NOTE

Multiple Device/Tag detection

C

C

C

Communication Operating Volume

C1: If Card Emulation for a Tag Platform is supported then the according condition
for Normal Power Mode MUST be selected.
C2: If Card Emulation for a Tag Platform is supported then the according condition
for Reduced Power Mode in addition MAY be selected. For the CCC Digital Key
CE Device the support of the Reduced Power Mode is mandatory.

Devices Requirements

Page 21

Interoperability Modules

Table 7: Peer Mode requirements to interoperability modules mappingPeer Mode
Initiator

Number

ACM

PCM

ACM

M

M

M

M

P2P communication

M

Data exchange in PCM as Initiator

REQ-P2P-1.1.2

M

REQ-P2P-1.2.1

Data exchange in ACM as Initiator
M

Data exchange in PCM as Target

REQ-P2P-1.2.2
REQ-P2P-1.3

REQ-P2P-2

Comment

PCM

REQ-P2P-1.1.1
REQ-P2P-1

TargetM

Data exchange in ACM as Target

M

M

M

M

Payload

M

M

M

M

LLCP

REQ-P2P-2.1

M

M

M

M

LLCP service class

REQ-P2P-2.2

M

M

M

M

Protocol bindings

M

M

M

M

SNEP

M

M

M

M

SNEP Server

REQ-P2P-3
REQ-P2P-3.1

Table 8: Reader/Writer Mode requirements to module mapping

REQ-9.A1

RATS
M

M
REQ-RW-1.2

M

M

Comment

Type 5 Tag Operation

NDEF support

M

REQ-9.B1

REQ-RW1

Platform

NDEF support

Platform

NDEF support

NumberType 3 Tag Type 4A Tag Type 4B Tag
Operation
Operation
Operation

Platform

Type 2 Tag Operation

Reader/WriterM

ALLB_REQ, SENSB_REQ, ATTRIB
M

M

NDEF read
T2T NDEF readM

T3T Platform

M

Payload

REQ-RW-1.3
RW-1.3.1

Devices Requirements

Page 22

Interoperability Modules

RW-1.3.2

REQ-RW-1.5

T3T NDEF readM

ISO DEP

RW-1.4.1

M

M

T4T NDEF read

RW-1.4.2

M

M

Payload

RW-1.4.3

M

M

APDU MV 2.x

RW-1.4.4

M

M

APDU MV3.x
M

Reading NDEF

RW-1.5.1M

1 byte command support

RW-1.5.2M

2 byte command support

RW-1.5.3

M

Read Payload

RW-1.5.4

M

Mapping Version

REQ-RW-2.2

M

NDEF write

M

T2T NDEF write
M

REQ-RW-2.3

REQ-RW2

REQ-RW-2.4

REQ-RW-2.5

Comment

Type 5 Tag Operation

NDEF support

M
M

REQ-RW-1.4

Platform

NDEF support

Platform

NDEF support

NumberType 3 Tag Type 4A Tag Type 4B Tag
Operation
Operation
Operation

Platform

Type 2 Tag Operation

Reader/Writer

REQ-RW2.3.1

T3T send payload size
M

T3T NDEF write
M

M

T4T NDEF write

REQ-RW2.4.1

M

M

Payload

REQ-RW2.4.2

M

M

APDU MV 2.x

REQ-RW2.4.3

M

M

APDU MV3.x
M

T5T NDEF write

RW-2.5.1M

1 byte command support

RW-2.5.2M

2 byte command support

RW-2.5.3

M

Write Payload

RW-2.5.4

M

Mapping Version

Devices Requirements

Page 23

Interoperability Modules

REQ-RW-3

Comment

Type 5 Tag Operation

NDEF support

Platform

NDEF support

Platform

NDEF support

NumberType 3 Tag Type 4A Tag Type 4B Tag
Operation
Operation
Operation

Platform

Type 2 Tag Operation

Reader/Writer

REQ-RW3.0

C1

C1

C1

C1

C1

Support of various options ofminimum NDEF Message sizes

REQ-RW3.1

C2

C2

C2

C2

C2

Support of 130KB of minimum NDEF
Message size

C1: REQ-RW-3.0 SHALL be selected for all Device Classes supporting
Reader/Writer mode except the NFC Mobile Device. Otherwise not applicable.

NOTE

C2: REQ-RW-3.1 SHALL be selected for the NFC Mobile Device Class. Otherwise
not applicable.

Table 9: Card Emulation and Tag Mode requirements to module mapping

REQ-TAG-1.AC

REQ-TAG-1.B

M

Type 5 Tag Module

M

C

REQ-TAG-1.C

Type 4B Tag Module

Type 4A Tag Module

Type 3 Tag Module

Type 2 Tag Module

Tag ModeType 4B Tag Platform

Type 4A Tag Platform

NumberType 3 Tag Platform

CE ModeNFC-A Technology support
M

C

NFC-B Technology support

M

NFC-F Technology support

REQ-TAG-1.D

M
REQ-TAG-1.2
REQ-TAG-1.3
REQ-TAG-1.4A

M
C

REQ-TAG-1.4B

T3T Platform support

Devices Requirements

T4AT Platform and ISO-DEP
support

M
C

T4BT Platform and ISO-DEP
supportM

REQ-TAG-1.5
REQ-9.A2

M
C

NFC-V Technology support
T2T Platform support

M
C

Comment

O

T5T Platform support
ATS

Page 24

Interoperability Modules

REQ-9.B2

C

REQ-T2T-1

O

Type 5 Tag Module

Type 4B Tag Module

Type 4A Tag Module

Type 3 Tag Module

Type 2 Tag Module

Tag ModeType 4B Tag Platform

Type 4A Tag Platform

NumberType 3 Tag Platform

CE ModeComment

SENSB_RESM

T2T CMD set

REQ-T2T-1-1

M

READ CMD

REQ-T2T-1-2

C

WRITE CMD

REQ-T2T-1-3

C

SECTOR_SELECT

REQ-T2T-2

M

Life Cycle State

REQ-T2T-3

M

CC and NDEF

REQ-T2T-4

M

Mapping Version

REQ-T3T-1

M

T3T CMD set

REQ-T3T-1-1

M

CHECK

REQ-T3T-1-2

C

UPDATE

REQ-T3T-2

M

Life Cycle State

REQ-T3T-3

M

NDEF storage service

REQ-T3T-4

M

Attribute Information Block

REQ-T3T-5

M

Mapping Version

REQ-T4T-1

M

M

T4T Mapping Version

REQ-T4T-2

M

M

CMD set

REQ-T4T-2-1

M

M

ReadBinary

REQ-T4T-2-2

CC

UpdateBinary

REQ-T4T-2-3

CC

Mapping Version 3.x
ReadBinary and ODO

REQ-T4T-2-4

CC

Mapping Version 3.x
UpdateBinary and ODO and
DDO

REQ-T4T-3

M

M

Short Field coding

REQ-T4T-4

CC

Extended Field coding

REQ-T4T-5

M

M

Life Cycle State

Devices Requirements

Page 25

Interoperability Modules

M

M

Type 5 Tag Module

Type 4B Tag Module

REQ-T4T-6

Type 4A Tag Module

Type 3 Tag Module

Type 2 Tag Module

Tag ModeType 4B Tag Platform

Type 4A Tag Platform

NumberType 3 Tag Platform

CE ModeComment

Application, CC, NDEF
M

T5T: generic requirement on
CMDs

REQ-T5T-1-1

M

Minimum required CMDs

REQ-T5T-1-2

C

EXTENDED_READ_SINGLE_BLOCK

REQ-T5T-1-3

C

WRITE_SINGLE_BLOCK
support

REQ-T5T-1-4

C

EXTENDED_WRITE_SINGLE_BLOCK support

REQ-T5T-1-5

O

SELECT CMD support

REQ-T5T-1-6

O

LOCK_SINGLE_BLOCK

REQ-T5T-1-7

O

EXTENDED_LOCK_SINGLE_BLOCK

REQ-T5T-1-8

O

READ_MULTIPLE_BLOCK
CMD support

REQ-T5T-1-9

O

EXTENDED_READ_MULTIP
LE_BLOCK CMD support

REQ-T5T-1-10

O

Special Frame support

REQ-T5T-2

M

Valid Life Cycle State

REQ-T5T-3

M

CC and NDEF

REQ-T5T-4

M

Mapping Version

REQ-T5T-1

M

M

M

M

M

Communication Operating
Volume

REQ-TagPerf-1

M

M

M

M

M

Requirements for
Tagcompliance operating
volume

REQ-TagPerf-2

M

M

M

M

M

Requirements for Tag
performance operating volume

REQ-RF-1

Devices Requirements

M

M

M

Page 26

Interoperability Modules

REQ-TST-1.A

Type 4B Tag Platform

Type 4A Tag Platform

Type 3 Tag Platform

ACM

PCM

TargetInitiator
ACM

PCM

NumberReader/Writer

RF Collision Avoidance

Table 10: DTA requirements to module mapping

Comment[DTA] support in

M

REQ-TST-1.B

RW modeM

REQ-TST-1.C[DTA] support as P2P
Initiator

M
M

REQ-TST-1.D

M[DTA] support as P2P Target[DTA] support as T3T
ListenerC

REQ-TST-1.E

C[DTA] support as T4T
ListenerC

NOTE

WLC Listen Module

NumberWLC Poll Module

Table 11: WLC Mode Requirements to module mapping

Comment

REQ-WLC-P-1

M

WLC protocol support

REQ-WLC-P-2

M

Power Class support

REQ-WLC-L-1

M

WLC protocol support

REQ-WLC-L-2

M

To be charged from any power class

REQ-RF-2.1

C1C1

WLC OV6 Operating Volume

REQ-RF-2.2

C1C1

WLC OV7 Operating Volume

1

C : At least one of REQ-RF-2.x must be selected by a module.

Devices Requirements

Page 27

NFC Forum Requirements

5 NFC Forum Requirements
The NFC Forum Devices requirements are listed in the following subsections:•

5.1 Requirements Terms (see Table 12): Defines capabilities of NFC-Forum-compliant
devices.

•

5.2 RF Requirements (see Table 13): Defines common performance requirements (forexample, Operating Volume).

•

5.3 Requirements for NFC Forum Peer Mode (see Table 14): Defines in detail the capabilities
of NFC-Forum-compliant devices in NFC Forum Peer Mode.

•

5.4 Requirements for NFC Forum Reader/Writer Mode (see Table 15): Defines in detail thecapabilities of NFC-Forum-compliant devices in NFC Forum Reader/Writer Mode.

•

5.5 Requirements for NFC Forum Card Emulation and Tag Mode (see Table 16): Defines
generic capabilities of NFC Forum Universal Devices in CE Mode and NFC Tag Devices.

•

5.6 - 5.9 Tag Module Requirements (see Table 17 to Table 20): Defines in detail thecapabilities of NFC Tag Devices.

•5.10 Tag Performance Requirements (see Table 21): Defines generic requirements on
performance for NFC Tag Devices.

•

5.12 Requirements for NFC Forum Certification (see Table 23): Defines requirements forcertification of NFC Universal and NFC Reader Devices.

NOTE

5.1

Requirements terms are specific to each class of devices.

Requirements Terms
Table 12: Requirements Terms

NumberRequirements Terms

Remark

REQ-1.A

The ability to communicate in Peer Mode.

See Section 5.3.

REQ-1.B

The ability to communicate in NFC Forum
Reader/Writer Mode.

See Section 5.4.

REQ-1.C

The ability to communicate in NFC Forum Card
Emulation Mode.

See Section 5.5.

REQ-1.1C

The ability to operate in Card Emulation Mode whenin Normal Power Mode.

REQ-1.2C

The ability to operate in Card Emulation Mode whenin Reduced Power Mode.

REQ-2.A

The ability to operate in Poll Mode.

REQ-2.B

The ability to operate in Listen Mode.

REQ-2.C

In Poll Mode the ability to perform RF Collision
Avoidance.

REQ-3.A

The ability to detect any NFC Forum Tag (potentiallycontaining an NDEF message).

Devices Requirements

Page 28

NFC Forum Requirements
NumberRequirements Terms

Remark

REQ-3.1A

The ability in Poll Mode to detect an NFC Tag Device
within 5 seconds after the tag or device enters the
Operating Volume.

This is not a requirement to force
a device to poll all the time.
However, when the device ispolling, this requirement applies.
This requirement applies to thedigital protocol layer and defines
an upper limit to detect a Tag.

REQ-3.B

The ability to detect an NFC Forum Universal Device.

REQ-3.1B

The ability in Poll Mode to detect an NFC Forum
Device in Peer Mode within 5 seconds after the device
enters the Operating Volume.

REQ-4.A

The ability to poll for Technology: NFC-A

REQ-4.B

The ability to poll for Technology: NFC-B

REQ-4.C

The ability to poll for Technology: NFC-F

REQ-4.DThe ability to poll for Technology: NFC-V

REQ-5

Void

Devices Requirements

This is not a requirement to force
a device to poll all the time.
However, when the device ispolling, this requirement applies.
This requirement applies to thedigital protocol layer and defines
an upper limit to detect a peer
device.

Page 29

NFC Forum Requirements
NumberRequirements Terms

Remark

REQ-6

The ability to detect whether multiple NFC Forum
Devices and/or NFC Tag Devices respond to a pollcommand. There is no requirement to identify each
responding device.

REQ-7

The ability to generate an NDEF message, as definedby [NDEF].

REQ-8

The ability to accept an NDEF message, correctly
formatted according to [NDEF].

REQ-9.A1

In NFC-A, the ability to set the parameters to disable
the support of advanced protocol features, as follows:• In the RATS command, the ability to set FSDI
to at least 8h.

Poll mode requirement on RATS
command

REQ-9.A2

In NFC-A, the ability to set the parameters to disable
the support of advanced protocol features, as follows:• In response to the RATS command, the ability
to set the following to 0b:• Bits b7 to b5 and b3 to b1 of TA(1)Listen mode requirement on
RATS response

REQ-9.B1

In NFC-B, the ability to set the parameters to disable
the support of advanced protocol features, as follows:• In the ALLB_REQ and SENSB_REQ
commands, the ability to set bit b5 of PARAM
to 0b.

Support for the advanced
protocol features as described in[DIGITAL] will be allowed
when the necessary
specifications are developed.

REQ-9.B2•

In the ATTRIB command, the ability to set
bits b8 to b3 of Param 1 to 0b.

•

In the ATTRIB Command the ability to set
bits b4 to b1 (FSDI) of Param 2 to at least 8h.

In NFC-B, the ability to set the parameters to disable
the support of advanced protocol features, as follows:• In the SENSB_RES response, the ability to set
the following to 0b:•

Bits b7 to b5 and b3 to b1 of the
Bit_Rate_Capability field•

Bits b3 and b2 of the Protocol_Type field.

Devices Requirements

Page 30

NFC Forum Requirements

5.2

RF Requirements
Table 13: RF Requirements

RF
Number

RF Requirement

RemarkREQ-RF-1

The ability to exchange data with another compliant NFC Forum
Device in the Operating Volume, as defined in [ANALOG].

REQ-RF-2.1

The ability to exchange data and to be charged in the Operating
Volume WLC OV 6, as defined in [WLC].

REQ-RF-2.2

The ability to exchange data and to be charged in the Operating
Volume WLC OV 7, as defined in [WLC].

5.3

Requirements for NFC Forum Peer Mode
Table 14: Requirements for NFC Forum Peer Mode

REQ-P2P
NumberP2P Requirement

RemarkREQ-P2P-1

In Peer Mode the ability to communicate with anotherdevice in Peer Mode to exchange data.

REQ-P2P-1.1.1

In Peer Mode the ability to exchange data as initiator inpassive communication mode using at least one of thefollowing bit rates: 106, 212 or 424 kbit/s.

PCM Initiator

REQ-P2P-1.1.2

In Peer Mode, the ability to exchange data as initiator in
active communication mode using at least one of thefollowing bit rates: 106, 212, or 424 kbit/s.

ACM Initiator

REQ-P2P-1.2.1

In Peer Mode the ability to exchange data as the target inpassive communication mode at 106, 212 and 424 kbit/s.

PCM Target

REQ-P2P-1.2.2

In Peer Mode, the ability to exchange data as the target in
active communication mode at 106, 212, and 424 kbit/s.

ACM Target

REQ-P2P-1.3

In Peer Mode the ability to support payload sizes up to
and including 254 bytes.

The definition of payload
is according to NFC-DEP
Protocol as defined in[DIGITAL].

REQ-P2P-2

In Peer Mode the ability to support LLCP as defined in[LLCP].

REQ-P2P-2.1

In Peer Mode the ability to support LLCP link service
class 3 as defined in [LLCP].

REQ-P2P-2.2

In Peer Mode the ability to support protocol bindings for
NFC Forum Registered Protocols (LLCP or SNEP orboth).

Devices Requirements

Page 31

NFC Forum Requirements
REQ-P2P
NumberP2P Requirement

REQ-P2P-3

In Peer Mode the ability to communicate with anotherdevice in Peer Mode to exchange NDEF Data as definedin [SNEP].

REQ-P2P-3.1

In Peer Mode the ability to support a Default SNEP
Server as defined in [SNEP].

5.4

RemarkRequirements for NFC Forum Reader/Writer Mode
Table 15: Requirements for NFC Forum Reader/Writer Mode

REQ-RW Number

Reader/Writer Mode Requirement

REQ-RW-1

The ability to read an NDEF message from all NFC
Tag Types when a single tag is present in the Operating
Volume.

REQ-RW-1.2

The ability to read an NDEF message of an NFC Type2 Tag [T2T].

REQ-RW-1.3

The ability to send Type 3 Tag Platform Commands
and receive Type 3 Tag Platform Responses as definedfor Type 3 Tag Platform in [DIGITAL] and[ACTIVITY].

REQ-RW-1.3.1

The ability to read payload sizes up to 254 bytes at a bit
rate of at least 212 kbit/s from an NFC Type 3 Tag.
Payload is defined according to [DIGITAL] for theType 3 Tag Platform.

REQ-RW-1.3.2

The ability to read an NDEF message of an NFC Type
3 Tag [T3T].

REQ-RW-1.4

The ability to support ISO-DEP for communicating to
NFC Type 4A and 4B Tag [T4T].

REQ-RW-1.4.1

The ability to read an NDEF message of an NFC Type
4A and 4B Tag.

REQ-RW-1.4.2

Reading an NFC Type 4A and 4B Tag, the ability tosupport a payload size of 254 bytes and a bit rate of
106 kbit/s.
Payload is defined according to [DIGITAL].

REQ-RW-1.4.3

Reading an NFC Type 4A and 4B Tag implementing
Mapping Version 2.x, the ability to support 256 databytes in the response APDU.
The definition of data bytes is used in accordance with
[T4T].

Devices Requirements

Remark

256 bytes is the maximum
amount of data that can beread by a command
APDU.

Page 32

NFC Forum Requirements
REQ-RW Number

Reader/Writer Mode Requirement

REQ-RW-1.4.4

Reading an NFC Type 4A and 4B Tag implementing
Mapping Version 3.x, the ability to support at least
256B data within the response APDU.
The definition of data bytes is used in accordance with
[T4T].

REQ-RW-1.5

The ability to read an NDEF message of an NFC Type
5 Tag.

REQ-RW-1.5.1

The ability to support 1 Byte Commands for reading an
NDEF message of an NFC Type 5 Tag as defined in[T5T].

REQ-RW-1.5.2

The ability to support 2 Byte Commands for reading an
NDEF message of an NFC Type 5 Tag as defined in[T5T].

REQ-RW-1.5.3

The ability to read payload sizes up to 256 bytes at a bit
rate of 26 kbit/s from a NFC Type 5 Tag.
The definition of payload is according to [DIGITAL]
for Type 5 Tag Platform.

REQ-RW-1.5.4

Reading NDEF data from an NFC Type 5 Tag
implementing Mapping Version 1.x as defined in[T5T].

REQ-RW-2

The ability to write an NDEF message to NFC Tag
Types when a single tag is present in the Operating
Volume.

REQ-RW-2.1

VOID

REQ-RW-2.2

The ability to write an NDEF message to an NFC Type2 Tag [T2T].

REQ-RW-2.3

The ability to write payload sizes up to 254 bytes at a
bit rate of at least 212 kbit/s to an NFC Type 3 Tag.
Payload is defined according to [DIGITAL] for theType 3 Tag Platform.

REQ-RW-2.3.1

The ability to write an NDEF message to an NFC Type
3 Tag [T3T].

REQ-RW-2.4

The ability to write an NDEF message to an NFC Type
4A and 4B Tag [T4T].

REQ-RW-2.4.1

Writing NDEF data to an NFC Type 4A and 4B Tag,the ability to support a payload size of 254 bytes and a
bit rate of 106 kbit/s.
Payload is defined according to [DIGITAL].

Devices Requirements

RemarkPage 33

NFC Forum Requirements
REQ-RW Number

Reader/Writer Mode Requirement

RemarkREQ-RW-2.4.2

Writing NDEF data to an NFC Type 4A and 4B Tag
implementing Mapping Version 2.x, the ability tosupport 255 data bytes in the command APDU.
The definition of data bytes is used in accordance with
[T4T].

255 bytes is the maximum
amount of data that can be
written by a command
APDU.

REQ-RW-2.4.3

Writing NDEF data to an NFC Type 4A and 4B Tag
implementing Mapping Version 3.x, the ability tosupport 256B data within the command APDU.
The definition of data bytes is used in accordance with
[T4T].

REQ-RW-2.5

The ability to write an NDEF message to an NFC Type
5 Tag [T5T].

REQ-RW-2.5.1

The ability to support 1 Byte Commands for writing an
NDEF message to an NFC Type 5 Tag.

REQ-RW-2.5.2

The ability to support 2 Byte Commands for writing an
NDEF message to an NFC Type 5 Tag.

REQ-RW-2.5.3

The ability to write payload sizes up to 32 Bytes at a bit
rate of 26 kbit/s to an NFC Type 5 Tag.
The definition of payload is according to [DIGITAL]
for Type 5 Tag Platform.

REQ-RW-2.5.4

Writing NDEF data to an NFC Type 5 Tag
implementing Mapping Version 1.x as defined in[T5T].

REQ-RW-3.0

The ability to read or write an NDEF message size of at Minimum limit on max
least one of the following options from any NFC Forum NDEF message size
defined Tag Type: 1.6kB, 8kB, 16kB, 32kB, 130kB
NOTE
The Tag Type may impose further limits
on the maximum NDEF message size.

REQ-RW-3.1

The ability to read or write an NDEF message size of
130kB.
NOTE

Devices Requirements

The Tag Type may impose further limits
on the maximum NDEF message size.

Page 34

NFC Forum Requirements

5.5

Requirements for NFC Forum Card Emulation and Tag
ModeTable 16: Requirements for NFC Forum Tag Platform and Module

Tag Number

Tag Mode Requirement

Remarks

REQ-Tag-1.A

The ability to support NFC-A in listen mode.

T2T, T4AT

REQ-Tag-1.B

The ability to support NFC-B in listen mode.

T4BT

REQ-Tag-1.C

The ability to support NFC-F in listen mode.

T3T

REQ-Tag-1.D

The ability to support NFC-V in listen mode.

T5T

REQ-Tag-1.2

Compliant with the Type 2 Tag Platform as defined in[DIGITAL] and [ACTIVITY].

T2T

REQ-Tag-1.3

Compliant with the Type 3 Tag Platform defined in[DIGITAL], and [ACTIVITY].

T3T

REQ-Tag-1.4A

Compliant with the Type 4A Tag Platform and ISO-DEP
Protocol as defined in [DIGITAL], and [ACTIVITY].

T4AT

REQ-Tag-1.4B

Compliant with the Type 4B Tag Platform and ISO-DEP
Protocol defined in [DIGITAL] and [ACTIVITY].

T4BT

REQ-Tag-1.5

Compliant with the Type 5 Tag Platform defined in[DIGITAL] and [ACTIVITY].

T5T

NOTE

In Card Emulation Mode no requirements are specified for tag emulation to
exchange NDEF data between NFC Devices.

Devices Requirements

Page 35

NFC Forum Requirements

5.6

Requirements for NFC Forum Type 2 Tag Module
Table 17: Requirements for NFC Forum Type 2 Tag Module

T2T
NumberTag Mode Requirement

Remarks

REQT2T-1

The ability to support the command set defined in [T2T].

CMD set

REQT2T-1-1

The ability to support the READ command.

CMD needed to read data

REQT2T-1-2

If in INITIALIZED or READ/WRITE life cycle state, theability to support the WRITE command.

CMD needed to write data

REQT2T-1-3

If the T2T_Area exceeds Sector Number 0, the ability tosupport the SECTOR_SELECT command.

REQT2T-2

Compliant with at least one of the Life Cycle states, as
defined in [T2T].

Tag access

REQT2T-3

The ability to contain at least the Capability Container andthe NDEF TLV, as defined in [T2T].

A T2T contains at least the CC
and the NDEF TLV.

REQT2T-4

The ability to support Mapping Version 1.x, as defined in[T2T].

Valid versions: 1.0 – 1.9

Devices Requirements

Page 36

NFC Forum Requirements

5.7

Requirements for NFC Forum Type 3 Tag Module
Table 18: Requirements for NFC Forum Type 3 Tag Module and Platform

T3T Number

Tag Mode Requirement

Remarks

REQ-T3T-1

The ability to support the command set defined in[T3T].

CMD set

REQ-T3T-1-1

The ability to support the CHECK command.

CMD needed to read data

REQ-T3T-1-2

If in INITIALIZED or READ/WRITE life cycle
state, the ability to support the UPDATE command.

CMD needed to write data

REQ-T3T-2

Compliant with at least one of the Life Cycle
States, as defined in [T3T].

Tag access

REQ-T3T-3

The ability to contain the Service with the Service
Number 0, as defined in [T3T].

NDEF storage service

REQ-T3T-4

The ability to contain at least the Attribute
Information Block, as defined in [T3T].

REQ-T3T-5

The ability to support Mapping Version 1.x, as
defined in [T3T].

Devices Requirements

Valid versions: 1.0 – 1.9

Page 37

NFC Forum Requirements

5.8

Requirements for NFC Forum Type 4A and 4B Tag Modules
Table 19: Requirements for NFC Forum Type 4A and 4B Tag Modules

T4T
NumberTag Mode Requirement

Remarks

REQ-T4T1

The ability to implement either Mapping Version 2.x or
Mapping Version 3.x, as defined in [T4T].

Valid versions: 2.0 – 2.9
orValid versions: 3.0 – 3.9

REQ-T4T2

The ability to support the command set for Mapping
Version 2.x or Mapping Version 3.x, as defined in[T4T].

CMD set

REQ-T4T2-1

The ability to support the Select and ReadBinarycommands.

Needed to read NDEF

REQ-T4T2-2

If in INITIALIZED or READ/WRITE Life Cycle State,
the ability to support the UpdateBinary command.

Needed to write NDEF

REQ-T4T2-3

If implementing the Mapping Version 3.x the ability tosupport ReadBinary with ODO.

Needed to read NDEF from T4T
Mapping Version 3.x

REQ-T4T2-4

If in INITIALIZED or READ/WRITE life cycle andimplementing the Mapping Version 3.x, the ability tosupport UpdateBinary with ODO and DDO.

Needed to write NDEF to T4T
Mapping Version 3.x

REQ-T4T3

The ability to support Short Field coding.

Mandatory

REQ-T4T4

If MLc is larger than a Data field length of 255 bytes
and/or MLe is larger than an expected response lengthof 256 bytes, the ability to support Extended Field
coding.

Conditional

REQ-T4T5

Compliant with at least one of the Life Cycle states, as
defined in [T4T].

Life Cycle State

REQ-T4T6

The ability to contain at least the NDEF Tag application,
Capability Container and the NDEF file, as defined in[T4T].

Devices Requirements

Page 38

NFC Forum Requirements

5.9

Requirements for NFC Forum Type 5 Tag Module
Table 20: Requirements for NFC Forum Type 5 Tag Module

T5T
NumberTag Mode Requirement

Remarks

REQ-T5T-1

The ability to support the defined subset ofcommands, as defined in [T5T].

Generic requirement on commandset

REQ-T5T1-1

The ability to support the INVENTORY,READ_SINGLE_BLOCK and SLPV_REQ
commands.

Minimum set of CMDs to besupported by a T5T (need to readcontent).

REQ-T5T1-2

If 2-byte address mode is supported, the ability tosupport the EXTENDED_READ_SINGLE
command.

Additional minimum required CMD
in case 2-byte address mode issupported (need to read content).

REQ-T5T1-3

If in INITIALIZED or READ/WRITE life cycle
states, the ability to support the
WRITE_SINGLE_BLOCK command.

For READ/WRITE Tags, the write
CMD is supported.

REQ-T5T1-4

If 2-byte address mode is supported and if in
INITIALIZED or READ/WRITE life cycles state,
the ability to support the
EXTENDED_WRITE_SINGLE_BLOCK
command.

For READ/WRITE Tags and, if 2byte address mode is supported,
additionally the write CMD is
supported.

REQ-T5T1-5

The ability to support the SELECT command.

Optional feature.

REQ-T5T1-6

The ability to support the
LOCK_SINGLE_BLOCK command.

Optional feature, to move the Tagfrom READ/WRITE to Read-Only
Life Cycle State.

REQ-T5T1-7

If 2-byte address mode is supported, the ability tosupport the
EXTENDED_LOCK_SINGLE_BLOCK command.

Optional feature, to move the Tagfrom READ/WRITE to Read-Only
Life Cycle State.

REQ-T5T1-8

The ability to support the
READ_MULTIPLE_BLOCK command.

Optional feature.

REQ-T5T1-9

If 2-byte address mode is supported, the ability tosupport the
EXTENDED_READ_MULTIPLE_BLOCK
command.

Optional feature.

REQ-T5T1-10

The ability to support the special frame during
Write-Alike command execution.

Optional feature.

Devices Requirements

Page 39

NFC Forum Requirements
T5T
NumberTag Mode Requirement

Remarks

REQ-T5T-2

Compliant to at least one of the Life Cycle states, as
defined in [T5T].

Life Cycle State.

REQ-T5T-3

The ability to contain at least the Capability
Container and the NDEF TLV, as defined in [T5T].

A T5T contains at least the CC andthe NDEF TLV.

REQ-T5T-4

The ability to support Mapping Version 1.x, as
defined in [T5T].

Valid versions: 1.0 – 1.9

5.10 Tag Performance Requirements
Table 21: Tag Performance Requirements
Tag-Perf
NumberTag Mode Requirement

Remarks

Tag-Perf-1

The ability to successfully transmit an NDEF message
in the compliance operating volume (see[ANALOG]), as defined in [PERF].

Applies to T2T, T3T, T4T and
T5T.

Tag-Perf-2

Measuring the maximum distance of successful
NDEF message transmission in the performance
operating volume, as defined in [PERF].

Applies to T2T, T3T, T4T and
T5T.

5.11 Wireless Charging Mode Requirements
Table 22: Wireless Charging Mode Requirements
WLC Number

Wireless Charging Requirement

REQ-WLC-P-1

The ability to support the static and negotiated protocol as
defined in [WLC].

REQ-WLC-P-2

The abililty to provide the power level for the supported
power class as defined in [WLC].

REQ-WLC-L-1

The ability to indicate and support either the static or
negotiated mode as defined in [WLC].

REQ-WLC-L-2

The ability to support to be charged independent of the powerclass of the WLC-P as defined in [WLC].

Devices Requirements

Remarks

Page 40

NFC Forum Requirements

5.12 Requirements for NFC Forum Certification
Table 23: Test Requirements
REQ-TST
NumberTest Requirement

Remark

REQ-TST1.A

Implementation of the Device Test
Application for Reader/Writer mode,as defined in [DTA] for use during
NFC Forum certification testing.

Besides NFC Forum certification testing, themanagement of the presence and visibility of the
DTA during the lifetime of the NFC Forum
Device is out of scope.

REQ-TST1.B

Implementation of the Device Test
Application for Initiator, as defined in[DTA] for use during NFC Forumcertification testing.

In DTA Initiator is referred to Poll mode.
Besides NFC Forum certification testing, themanagement of the presence and visibility of the
DTA during the lifetime of the NFC Forum
Device is out of scope

REQ-TST1.C

Implementation of the Device Test
Application for Target, as defined in[DTA] for use during NFC Forumcertification testing.

In DTA Target is referred to Listen mode.
Besides NFC Forum certification testing, themanagement of the presence and visibility of the
DTA during the lifetime of the NFC Forum
Device is out of scope.

REQ-TST1.D

Implementation of the Device Test
Application for Type 3 Tag Platform
Listen mode, as defined in [DTA] foruse during NFC Forum certification
testing.

Besides NFC Forum certification testing, themanagement of the presence and visibility of the
DTA during the lifetime of the NFC Forum
Device is out of scope.

REQ-TST1.E

Implementation of the Device Test
Application for Type 4 Tag Platform
Listen mode, as defined in [DTA] foruse during NFC Forum certification
testing.

Besides NFC Forum certification testing, themanagement of the presence and visibility of the
DTA during the lifetime of the NFC Forum
Device is out of scope.

5.13 Operating Volume and Reference Equipment
NFC Forum defines different operating volumes, one for generic use cases [ANALOG], one toassess the Tag performance [PERF] and two for wireless charging [WLC]. The four distinct
operating volumens are denoted as Comms OV, Perf OV, WLC OV6 and WLC OV7. Basicinteroperability between devices having a different coil size is covered by NFC Forumcertification. Each device will be tested using a reference equipment having different coil sizes as
defined in [ANALOG] and [WLC]. The different coil sizes of the reference equipment cover the
span of device form factors targeted by NFC Forum use cases.
NFC Forum defines the following reference equipment to test communication related parameters:•

Reference Poller 0 - Coil:o

Shape: round, outer diameter 60mm

Devices Requirements

Page 41

NFC Forum Requirements•

Reference Poller 3 – Coil:o•Reference Poller 6 – Coil:o•

Rectangular, outer dim: 71.6mm x 41.5mm

Reference Listener 3 – Coil:o•

Rectangular, outer dim: 24.5mm x 19.5mm

Reference Listener 1 – Coil:o•

Rectangular, outer dim: 47.5mm x 33.5mm

Rectangular, outer dim: 46.0mm x 32.0mm

Reference Listener 6 – Coil:o

Rectangular, outer dim: 24.7mm x 19.7mm

NFC Forum defines the following reference equipment to test wireless charging relatedparameters:•

Reference WLC-P6 – Coil:o•Reference WLC-P7 – Coil:o•

Rectangular, outer dim: 10.5mm x 5.5mm

Reference WLC-L6 – Coil:o•

Rectangular, outer dim: 27.5mm x 22.5mm

Rectangular, outer dim: 24.7mm x 19.7mm

Reference WLC-L7 – Coil:o

Rectangular, outer dim: 9.0mm x 4.0mm

Table 24 lists the reference equipment to be mandatorily and optionally used for certification
testing depending on the Device Class and operating volume. The Tag performance operating
volume (Perf OV) is only defined for Tag devices and therefore is only shown for this Device
Class. If an Operating Volume does no apply for a particular Device Class it will not be shown.

Devices Requirements

Page 42NFC Forum Requirements

NFC Universal Device

NFC Mobile Device

NFC Reader Device

Card Emulation Device
NFC Tag Device
WLC Reader Device
WLC Tag Device
CCC Digital Key Reader
Device
CCC Digital Key CE
DeviceUSI WLC Reader Device

Devices Requirements

Ref Lis 6

M

M

M
O
O

M

M

M

WLC OV 7

M

M

M
O
O

M

M

M
O
O

M

M

M
O
O

O
O

M
M

M
M
O

O
O

M

M
M

M
M
M
M

M
M

O
O

M
M

Comms
Comms

Ref WLC-L7

Ref Lis 3

M

Ref WLC-L6

Ref Lis 1

M

Ref WLC-P7

Ref Pol 6

M

Ref WLC-P6

Ref Pol 3

Comms
WLC OV 6WLC OV 7Comms
WLC OV 6WLC OV 7Comms
WLC OV 6WLC OV 7Comms
WLC OV 6WLC OV 7Comms
Perf
WLC OV 6WLC OV 7WLC OV 6WLC OV 7

Ref Pol 0

Device Class

Operating
VolumeTable 24 Reference Equipment and Operating Volume definition per Device Class

M

M

O

M

M
M

Page 43

Use Cases

Use Cases

A.

(Informative)
Three broad categories of use cases were considered in identifying the requirements:•

Those in which the communication protocols are wholly defined by the NFC Forum•

Those in which the communication and charging protocols are defined by NFC Forum•

Those in which an NFC Forum Device communicates with another device using compatible
legacy protocols.

The use cases are described in the sections below and illustrated in the accompanying figures.
Figure 1 describes the conventions used in the figures below to indicate the roles of the different
actors in the use cases. This usage is confined to the illustrations of the use cases in this document
and does not indicate the general usage of the marks.
The NFC Forum Certification Mark in the
below use case examples is used to indicatethat a device is a Certified Implementation.
The NFC Forum N-Mark, in the below use
case examples, lets consumers know that NFC
services are available. It indicates where to
touch to enable NFC services.

SC

Indicates a device operating as a smart card orother contactless tag not defined by the NFC
Forum.
Indicates in the below use case examples thefield emitting device.
Indicates direction of communication control:
arrow shown from the Initiator pointing
toward the Target device.

Figure 1: Conventions for Use Case Diagrams

A.1

NFC Forum Communication Use Cases

The use cases defined in this section deal with communication between an NFC Forum Device
and another actor, as defined below. Interoperability on the communication level is ensured by
the NFC Forum Certification Program.
1. An NFC Forum Device is able to communicate with another NFC Forum Device in NFC
Forum Peer Mode. This is illustrated in Figure 2.

Devices Requirements

Page 44

Use Cases

P2P

Figure 2: Two NFC Forum Devices Communicating in NFC Forum Peer Mode

2. An NFC Forum Device in NFC Forum Reader/Writer Mode is able to communicate with an
NFC Forum Tag. The NFC Forum specifies the requirements for NFC Forum Tags as well as
how to operate these tags. This is illustrated in Figure 3.

RW

Figure 3: NFC Forum Device in NFC Forum Reader/Writer Mode
Communicating with an NFC Forum Tag

3. An NFC Forum Device in NFC Forum Reader/Writer Mode is able to communicate with an
NFC Forum Device emulating an NFC Forum Tag. This is illustrated in Figure 4.

Devices Requirements

Page 45

Use Cases

RW

Figure 4: NFC Forum Device in NFC Forum Reader/Writer Mode Communicating with an
NFC Forum Device in NFC Forum Card Emulation Mode

4. An NFC Forum Device in NFC Forum Reader/Writer Mode is able to communicate with an
NFC Forum Device emulating an NFC Card Emulation Device. This is illustrated in Figure 5.

RW

Figure 5: NFC Forum Device in NFC Forum Reader/Writer Mode Communicating with an
NFC Forum Card Emulation Device

A.2

NFC Forum Wireless Charging Use CaseThe use case defined in this section deals with the charging of an NFC WLC Tag Device by an
NFC WLC Reader Device. In order to enable the wireless charging use case the two devices
communicate to optimize the charging process. Figure 6 shows an use case example for wirelesscharging.

Devices Requirements

Page 46Use Cases

WLC-L

WLC-P

Figure 6: NFC WLC Poller (WLC-P) is communicating and charging a NFC WLC Listener(WLC-L)

A.3

Legacy Communication Use Cases

The use cases defined in this section deal with communication between an NFC Forum Device
and legacy systems that are not defined by the NFC Forum. However, parts of the implementationof an NFC Forum Device, such as the RF layer or lower layer protocols, are also used by legacy
infrastructure.
The NFC Forum takes into account the possibility that requirements for some parts of the
protocol stack might impact the usability of NFC Forum Devices within existing contactless
infrastructure. Therefore the NFC Forum takes the needs of legacy systems into consideration
when it specifies tests that involve parts of the protocol stack that are also relevant for legacy
systems.
An NFC Forum Device in Reader/Writer Mode can communicate to an external smart card (SC)or other contactless card or tag that is supporting applications and protocols defined outside the
NFC Forum. The smart card system is based on one of the technologies (ISO/IEC 14443A,
ISO/IEC 14443B, and/or JIS X 6319-4) that is compatible with the technologies defined by the
NFC Forum (NFC-A, NFC-B, and/or NFC-F). This is illustrated in Figure 7.

Devices Requirements

Page 47

Use Cases

RW

SC
C

Figure 7: NFC Forum Device in NFC Forum Reader/Writer Mode
Communicating with a SC

5. An NFC Forum Device in Reader/Writer mode can communicate with another NFC Forum
Device emulating a smart card (or other contactless card or tag) that supports applications andprotocols defined outside of the NFC Forum. The smart card system is based on a technology
defined by the NFC Forum (NFC-A, NFC-B, and/or NFC-F). This is illustrated in Figure 8.

RW

SC

Figure 8: NFC Forum Device in NFC Forum Reader/Writer Mode
Communicating with an NFC Forum Device Emulating a SC

6. An NFC Forum Device emulating a smart card (or other contactless card or tag) can beaccessed by an external reader/writer terminal. The smart card system is based on one of thetechnologies (ISO/IEC 14443A, ISO/IEC 14443B, and/or JIS X 6319-4) compatible withthose defined by the NFC Forum (NFC-A, NFC-B, and/or NFC-F). This is illustrated in
Figure 9.

Devices Requirements

Page 48

Use Cases

RW
Terminal

RW

SC

Figure 9: Reader/Writer Terminal and NFC Forum Device Emulating a SC

Devices Requirements

Page 49

List of Device Classes containing other Device Classes

B.

List of Device Classes containing other Device
ClassesThis section analysis which Device Classes implicitely contain other Device Classes as a functionof mandatory and optional supported interoperability modules. Table 25 shows for the Parent
Device Class which Child Device Classes are contained. For Device Class combinations notshown in the Parent Device Class section no Child Device Class exists.

Table 25: Device Class coverage of other Device Classes

Parent Device ClassX1

X

NFC Reader Device

X

X

1

X

NFC Card Emulation Device

X

X

X
X

NFC Type 2 Tag
NFC Type 3 Tag

X4

NFC Type 4A Tag

X4

NFC Type 4B Tag

X4

NFC Type 5 Tag
WLC Reader Device

X3

X3

X3

X

WLC Tag Device
Specific market
ecosystem
devices

NFC Card Emulation
DeviceNFC Mobile Device

WLC Reader Device

X

NFC Reader Device

NFC Universal Device

NFC Mobile Device

Parent Device classes (in thisrow) cover the Child Deviceclasses selected (in thecolumn):NFC Universal Device

Open ecosystem Device Classes

Child Device Class

Open ecosystem NFC Forum Device Classes

X4

CCC Digital Key Reader Device

X

X

CCC Digital Key CE Device

X2

X2

USI WLC Reader Device

X3

X3

X

X
X2

X3

X5

X1 : only if the NFC Universal Device supports Card Emulation Mode for T3T, T4AT, and/or
T4BT Platform
X2 : only if the NFC Universal, NFC Mobile Device or the NFC CE Device support Card
Emulation Mode for T4AT Platform in normal and reduced Power mode
X3:Only if the optional WLC Poller Module is supported by the Parent Device.

Devices Requirements

Page 50

List of Device Classes containing other Device Classes
X4: Only if the Tag Platform and Tag Module for the Tag Type are supported by the Parent
Device.
X5: Only if the WLC Reader Device supports the Ref WLC-L7 operated in the WLC OV 7 (seesection 5.13).
NOTE

Other coverage of Child Device classes by Parent Devices classes is not possible assome options are not foreseen in the Parent device class, but are mandatory in theChild Device Class

Devices Requirements

Page 51

NFC Forum Architecture

NFC Forum Architecture

C.

(Informative)
C.1 NFC Forum Device
The NFC Forum defines an NFC Forum Device, which is within the scope of the NFC Forum. An
NFC Forum Device supports at least one of the classes of NFC Forum Devices defined in thisdocument. The properties of each class are specified in Section 3.
Each class of NFC Forum Device complies with at least one of the sets of NFC Forum
Interoperability Modules as defined in Section 3. Independent of the class of device, the NFC
Forum Device can also include additional protocols and applications not defined by the NFC
Forum. Currently the NFC Forum defines seven classes of NFC Forum Devices: NFC Universal
Device, NFC Mobile Device, NFC Reader Device, NFC CE Device, NFC Tag Device, NFC
WLC Reader and NFC WLC Tag Device. Section 3 defines which interoperability modules aremandatory or optional for a specific device class. A detailed assessment on interoperability
between defined device classes is provided in Section 3.3.

C.2 NFC Forum Protocol Stack
The NFC Forum Protocol Stack contains all interoperability modules defined in Section 3:-Peer Mode to enable communication with another device implementing the peer mode-

Reader/Writer Mode which interoperates with a device implementing either the Type X
Tag Module or the CE Mode-

CE Mode enables the communication with devices implementing the Reader/Writer
Mode or a technology-compatible reader/writer terminal-

Type X Tag Module enables the communication with devices implementing theReader/Writer Mode or a technology-compatible reader/writer terminal-

Wireless Charging Module enabling the use case of NFC based charging. The WLC Poll
Module uses the Tag Operation Mode to execute the WLC protocol. The WLC Listen
Mode enables to be charged supporting one Tag Platform for the WLC protocol.

This NFC Forum Protocol Stack design includes no assumptions about the implementation or
overall architecture of an NFC Forum Device.
Table 26 maps the NFC Forum protocol stack components of NFC Forum definedinteroperability modules in relation to the ISO/OSI defined protocol layers.
Table 26: OSI Protocol Stack Mapping
ISO/OSI
Layer

ReaderWriterModulePeer Module

CE Module

Tag Module

WLC Poll
ModuleWLC
ListenModuleL5 and up:
Session,Presentation,
Application

NDEF,
RTDs,
Applications

SNEP,
NDEF,
RTDs,
Applications

Applications

NDEF,
RTDs,
Applications

WLC
protocol,
NDEF,
RTDs

WLC
protocol,
NDEF,
RTDs

Devices Requirements

Page 52

NFC Forum Architecture
L4:Transport

Type X Tag
Operation,
Type X Tag
Platform

Type Y Tag,
Type Y Tag
Platform

Type X Tag,
Type X Tag
Platform

Type X Tag
Operation,
Type X Tag
Platform

Type X
Tag, TypeX Tag
Platform

L3: Network

None

None

None

None

None

None

L2: Data
Link

None

LLCP

None

None

None

None

DigitalProtocol,Activity,
ISO-DEP1

DigitalProtocol,Activity,
NFC-DEP

DigitalProtocol,Activity,
ISO-DEP1

DigitalProtocol,Activity,
ISO-DEP1

DigitalProtocol,Activity,
ISO-DEP1

DigitalProtocol,Activity,
ISO-DEP1

L1: PhysicalAnalogAnalogAnalogAnalogAnalogAnalogNOTE

1: ISO-DEP transport protocol is defined for T4AT and T4BT communication.

C.2.1

L1 and L2 - Analog and Digital Protocol Layers

The NFC Forum specifications that cover the analog [ANALOG] and digital protocol [DIGITAL]
layers are based on several other specifications, including:-

ISO/IEC 14443 standard series-

ISO/IEC 18092-

JIS X 6319-4-

ISO/IEC 15693 standard series.

[ACTIVITY] defines a listen state machine and polling operations for all four Technologies.
Together, these specifications define how NFC Forum Devices communicate with other devices
in the following ways.
-

Devices in Peer Mode use the NFC-DEP transport to exchange information. NFC-DEP
can be executed on either NFC-A or NFC-F Technology using either PCM or ACM.

-

A Device in Reader/Writer Mode communicates with:o

Devices supporting CE Mode. The CE Mode implements a Type X Tag Platformrunning on NFC-A (Type 4A Tag), NFC-B (Type 4B Tag) or NFC-F (Type 3Tag) Technologyo

NFC Tag Devices supporting the Tag Module. The Tag Modules provides the
NDEF application using the appropriate Type X Tag Platform running on NFC-A(Type 2, or Type 4A Tag), NFC-B (Type 4B Tag), NFC-F (Type 3 Tag) or NFCV (Type 5 Tag) Technology. For Type 4A and Type 4B Tag the ISO-DEP
transport facilitates the data exchange.

oISO/IEC 14443 smart cards using Type 4A/B Tag Platform and ISO-DEP
running on either NFC-A or NFC-B TechnologyoJIS X 6319-4 (FeliCa) smart cards running on NFC-F TechnologyoISO/IEC 15693 Tags running on NFC-V Technology.

Devices Requirements

Page 53

NFC Forum Architecture--

Devices supporting CE Mode:o

If supporting Type 4A or 4B Tag Platform, communication using ISO-DEP
running on either NFC-A or NFC-B Technology, with Devices supporting
Reader/Writer Mode or a legacy reader/writer that supports that capabilityoIf supporting Type 3 Tag Platform, communication using NFC-F Technology,
with Devices supporting Reader/Writer Mode or a legacy reader/writer that
supports that capability.

Devices supporting Tag Mode:o-Devices supporting WLC Poll Mode:o-Communicates with and charges a device supporting WLC Listen mode using the
Tag Platform and Module/Tag Operation supported by both devices.

Devices supporting WLC Listen Mode:
o

C.2.2

Communicates and exchanges NDEF messages with a device supporting
Reader/Writer Mode.

Communicates with and will be charged by a device supporting WLC Poll modeusing the Tag Platform and Module supported by both devices.

L2 - Logical Link Control Protocol

The Logical Link Control Protocol (LLCP) data link layer of the NFC Forum protocol stack[LLCP] allows the upper protocol layers to have a reliable bidirectional data link over NFC-DEP
and hides the target-initiator model from these upper layers.
LLCP is only used for P2P Communication using both, PCM and ACM. It provides an interface
to NFC applications, but it can also be used as a foundation for network layers in existing
protocol stacks, such as OBEX or TCP/IP.

C.2.3

L4 and Up – Type X Tag Operation

This transport layer includes the command sets needed to read from, or write to, NFC Tag
Devices and the NDEF Mapping that defines how the NDEF data are mapped within thesecommand sets for the different types of NFC Tag Device. The command sets and NDEF data
mappings are defined in [T2T], [T3T], [T4T] and [T5T].

C.2.4

L4 and Up – NDEF and RTDs

This presentation layer includes the NFC data exchange format [NDEF], record type definition[RTD], [URI], [TEXT], [SMARTPOSTER], [SIGNATURE], [VERB] and [DEVINFO].
Together these specifications describe a data format that is used to exchange information between
two NFC Forum Devices that supports that capability, or between a NFC Forum Device and areader/writer, tag, or smart card that supports that capability.
An RTD specifies the way NDEF is used by specific applications. For example, a smart poster
application on a NFC Forum Device that supports that capability retrieves a universal resource
identifier (URI) or a short message service (SMS) message. Therefore, [SMARTPOSTER]
defines how the URI or SMS content is stored in an NDEF Message.

Devices Requirements

Page 54

NFC Forum Architecture

C.2.5

Protocol Partitioning

To assist with the implementation of some classes of NFC Forum Device, [NCI] defines aninterface between a Device Host and an NFC Controller. The mechanisms defined in NCI allow
the Device Host to manage an NFC Controller at different levels in the OSI Protocol Stack. NCI
applies to an NFC Universal Device and an NFC Reader Device, but not to an NFC Tag Device.

C.3 Operation Modes
The NFC Forum Protocol Stack can be mainly split into four different operation modes:-

The Peer Mode, which defines the communication between an Initiator and a Target. The
Peer Mode is implemented in a NFC Universal Device or optionally in an NFC Reader
Device (Initiator).

-

The Reader/Writer Mode, which reads from, and potentially writes to, devices implementing
the Card Emulation Mode or the Tag Mode. This mode also allows for communication withexisting technology-compatible smart cards.

-

The Card Emulation Mode, which emulates the behavior of a smart card or tag. This mode
allows for communication with devices implementing the Reader/Writer Mode. It alsoenables the communication with existing technology-compatible reader/writer terminals. The
Card Emulation Mode enables the communication to the Reader/Writer Mode but does notdefine the application to be executed like the NDEF application.

-

The Tag Mode enables the communication with devices implementing the Reader/Writer
Mode. It also enables the communication with existing technology-compatible reader/writerterminals. The Tag Mode provides a previously written NDEF message which also may be
updated during its life time.

-

The WLC Poll Mode enables charging of a device implementing WLC Listen mode using thesame Tag Platform and Module.

-

The WLC Listen Mode enables to be charged by a device implementing the WLC Poll modeusing the same Tag Operation.

Section 3 identifies which operation modes are implemented by each class of NFC Forum
Device.
The following three sections and figures depict the protocol stack for each Operation Mode. The
analog layer and digital protocol layer are common for all six modes. While the digital protocol
layer of the stack is depicted as a single layer, it is defined in two separate specifications,[DIGITAL] and [ACTIVITY].

C.3.1

NFC Forum Peer Mode

A Peer Mode capable NFC Forum Device is able to communicate with another Peer Modecapable NFC Forum Device using NFC-DEP using either PCM or ACM, as defined in[DIGITAL]. The device uses the procedures defined in [LLCP] to establish and manage the link.
Figure 10 shows the NFC Forum Peer Mode architecture.
The service discovery protocol defined in [LLCP] is used to identify the common services
supported by both NFC Forum Devices.
The simple NDEF exchange protocol defined in [SNEP] is a protocol for exchanging NDEF
Messages between peer applications on different NFC Forum Devices.

Devices Requirements

Page 55

NFC Forum Architecture
Upper-level protocols registered with the NFC Forum can be bound to LLCP using bindings
defined by the NFC Forum. Upper-level protocols not registered with the NFC Forum can also bebound to LLCP using proprietary bindings.
All peer applications will communicate with peer applications on another NFC Forum Device
using one of these underlying protocols.
Applications
Service
Discovery
ProtocolSimpleNDEF
Exchange
ProtocolNFC Forum
RegisteredProtocols

Other
Protocols

Protocol Bindings

LLCP
Digital Protocol
PCM

ACM
AnalogNFC Forum Specifications

External Specifications

Figure 10: Peer Mode Architecture

C.3.2

NFC Forum Reader/Writer Mode

A Reader/Writer Mode capable NFC Forum Device is able to communicate with an NFC Tag
Device or a device supporting CE Mode. In this mode the Tag Operation parts of the Type X Tag
specifications are supported. Figure 11 shows the Reader/Writer Mode architecture.
If the device supports the NDEF Application, it can exchange data with an NFC Tag Device
using the NFC Forum-defined message coding format.
If the device supports third-party NDEF applications, it can exchange data with an NFC Tag
Device using the third-party defined message coding format.
The device can also support non-NDEF reader/writer applications that can use the underlying
layers to communicate with a variety of components (smart cards, memory cards, tags, etc.) thatare compliant with one of the contactless Technologies.
An NFC Forum Device implementing the Reader/Writer Mode supports the RF interfaces (NFCA, NFC-B, NFC-F and NFC-V) defined in [ANALOG] and [DIGITAL]. It establishes
communication using the poll mode operations in [ACTIVITY], then performs NDEF applicationlevel communication using the Tag Operation defined in [T2T], [T3T],[T4T] and [T5T].
Figure 11 shows the architecture for the Reader/Writer Mode following the OSI layer structure.

Devices Requirements

Page 56

NFC Forum Architecture

WLC Application

Third-party NDEF
Application

NDEF Application

Non-NDEF
Applications

Type X Tag Operation
Digital Protocol

AnalogNFC Forum Specifications

External Specifications

Figure 11: Reader/Writer Mode Architecture

NOTE

The WLC Poll Mode is not shown as a dedicated mode since it can be regarded as anapplication using the entire stack of the Reader/Writer protocol stack.

C.3.3

NFC Forum Tag Modes

An NFC Forum device that is CE Mode capable behaves as a smart card or tag in front of either
another NFC Forum Device that implements the Reader/Writer Mode or a conventional
technology-compatible reader/writer. This mode includes the emulation of memory cards, tags
and smart cards. The emulation of smart cards is intended mainly for portable devices that can beconveniently presented to reader/writers. The Tag mode is typically implemented in NFC Tag
Devices and serve the same purpose as devices supporting CE Mode.
An NFC Forum Device that supports one of these modes enables communication to existing
technology-compatible terminal infrastructures (e.g., for payment and ticketing). Figure 12 shows
the architecture of the Tag and CE Mode.
The behavior of an NFC Forum Device in CE or Tag Mode is described using a state machine
defined in [ACTIVITY].
The Tag Mode independent on the implemented Tag Type supports the NDEF application, the
CE Mode may contain the NDEF application.
If the device supports an NDEF Application, it can exchange data with a reader/writer using the
NFC Forum-defined message coding format.
If the device supports third-party NDEF applications, it can exchange data with a reader/writerusing the third-party defined message coding format.
Devices supporting either of both modes can also support non-NDEF applications that canemploy the underlying layers to communicate with a reader/writer using the application-specificmessages.
Figure 12 shows the architecture for the CE and the Tag Mode. The CE Mode is avialble for theType 3 Tag, Type 4A Tag and Type 4B Tag Platforms. The Tag mode is available for all NFC
Forum defined Tag Types.

Devices Requirements

Page 57

NFC Forum Architecture

WLC Application

Third-party NDEF
Application

NDEF Application

Non-NDEF
Applications

Type X Tag Platform
Digital Protocol

AnalogNFC Forum Specifications

External Specifications

Figure 12: Tag Mode Architecture

NOTE

The WLC Listen Mode is not shown as a dedicated mode since it can be regarded as
an application using the entire stack of the Tag protocol stack.

C.4 Device Architecture
Figure 13 and Figure 14 show the generic architecture of an NFC Forum Device when the device
is Polling (Figure 13) or Listening (Figure 14) at the point when another device is detected in its
proximity. Each block identifies an activity to be performed, and the activities depend on the
behavior of the device(s) in the proximity of the NFC Forum Device. Depending on theInteroperability Modules supported, a Device Class may only implement parts of the Poll and/or
Listen architecture.
Section 3 describes which configurations are possible for each class of NFC Forum Device.
NOTE

Before starting an activity, the adjacent activity listed below has to be completed.

NOTE

All P2P Communication uses LLCP.

All NFC Tag Device applications are based on NDEF. If a device also supports proprietary nonNDEF applications, these are out of scope of the NFC Forum.

C.4.1

Generic Polling Architecture

Devices Requirements

Page 58

NFC Forum Architecture
Peer ModeWLC Poll Mode
Reader/Writer Mode

Initiator Role

Reader/Writer RoleP2P Communication

Type X Tag Operation

Device Activation
Activity

Wait for Device
Activation

Wait for Device
Activation

Wait for Device
Activation

Capabilities Discovery

Capabilities Discovery

Capabilities Discovery

Capabilities Discovery

Collision Detection &Resolution Activity

Collision Detection &Resolution Activity

Collision Detection &Resolution Activity

Collision Detection &Resolution Activity

Technology Detection Activity
ACM

PCM

NFC-F

ACM

PCM

NFC-A

NFC-B

NFC-V

Figure 13: Generic Polling Architecture

Starting from the bottom, Figure 13 shows four different contactless technologies: NFC-A, NFCB, NFC-F and NFC-V.
The Technology Detection Activity determines which Technology is supported by the listening
device(s) in the proximity of the NFC Forum Device.
Each Technology has its own Collision Resolution Activity and capability discovery activities,
which provide similar functionality using technology-specific commands. The Device Activation
Activity which establishes the communication link is protocol-specific.
After setting all communication parameters, the device either engages with another NFC Forum
Device in direct P2P Communication (note that P2P Communication is not possible with the
NFC-B or NFC-V Technology), or it engages with an NFC Tag Device.
The P2P Communication using PCM or ACM is shown on the top left side of the figure. The
activities in NFC Forum Peer Mode comprise the use of NFC-DEP data exchange and LLCP.
Application-specific activities on top of LLCP are not displayed. At this point, the device is an
NFC-DEP Initiator.
The Tag Operation part of the Type X Tag is shown on the top right side of the figure. The
activities in NFC Forum Reader/Writer Mode comprise the use of the appropriate tag commands
and NDEF applications. Application specific activities on top of NDEF are not displayed. At thispoint, the device is a Reader/Writer. In case the WLC Poll mode is supported and the received
NDEF message contains the WLC Capability record the WLC mode can be used to charge thedevice in proximity. At this point the device is a WLC Reader.
Reader/Writer Communication is allowed with devices other than one of the Type X Tag
Platforms and whose data is not formatted according to NDEF (for example, communicating withpayment or transit contactless smart cards), although out of scope of the NFC Forum.
In all cases, the protocol-specific Device Deactivation Activity can be used to close the link to theremote device.
Devices Requirements

Page 59

NFC Forum Architecture

C.4.2

Generic Listening ArchitectureThis section describes the generic listen mode architecture. An NFC Forum defined Device Class
may only implement parts of this architecture. Still it can be derived from this generic listen modearchitecture.
Peer Mode

Card Emulation Mode

Target Role

Card Emulation RoleP2P Communication

Type Y Tag Platfrom

WLC Listen Mode
Tag Mode
Tag Role

Type X Tag Platform

Wait for Device
Activation

Wait for Device
Activation

Wait for Device
Activation

Wait for Device
Activation

Capabilities Discovery

Capabilities Discovery

Capabilities Discovery

Capabilities Discovery

Information for
Collision detection /resolution

Information for
Collision detection /resolution

Information for
Collision detection /resolution

Information for
Collision detection /resolution

Information for Technology Detection
ACM

PCM

NFC-F

ACM

PCM

NFC-A

NFC-B

NFC-V

Figure 14 Generic Listening Architecture

Starting from the bottom, Figure 14 shows four different contactless technologies: NFC-F, NFCA, NFC-B, and NFC-V.
The configuration of the Listener determines whether it responds to poll commands sent during
the Technology Detection Activity, and the parameters sent in the responses. The response tofurther commands during the Technology Detection, Collision Resolution, and Device Activation
activities proceeds according to the Listen State Machine for the selected Technology.
Depending on the supported modes and after setting all communication parameters, the device
either engages with another NFC Forum Device in direct P2P Communication using either PCM
or ACM, or, if the Device supports Card Emulation Mode or the Tag Mode, it engages with a
Reader/Writer and will respond to the Tag Operation part of the Type X Tag.
The P2P communication using either PCM or ACM is shown on the top left side of the figure.
The activities in Peer Mode comprise the use of the NFC-DEP data exchange protocol and LLCP.
Application-specific activities on top of LLCP are not displayed. At this point, the device is an
NFC-DEP Target.
For a device that supports CE Mode, the Type X Tag Platform is shown in the top middle side of
the figure. The activities of a Device in CE Mode comprise the use of the appropriate commands
for the Platform. At this point, the device is emulating a Type Y Tag.
An NFC Tag Device supports the Tag mode for at least one technology and Type X Tag
Platform, as shown on the top right side of the figure. The activities of a NFC Tag Device
comprise the use of the appropriate commands for the supported Type X Tag Platform and the
NDEF application. In case the WLC listen mode is supported the device provides in its NDEF

Devices Requirements

Page 60

NFC Forum Architecture
message the WLC Capability record. If the WLC poll mode is supported by the countpart theWLC protocol is used to charge the device. At this point the device is a WLC Tag Device.

Devices Requirements

Page 61

Revision History

D.

Revision History

Table 27 outlines the revision history of the “Devices Requirements” document.
Table 27: Revision History
Document
Name

Revision andRelease Date

StatusChange Notice

Supersedes

DeviceRequirements

Version 1.0,
April 2012

Final

Initial Publication-

DeviceRequirements

Version 1.1,
May 2012

Final

Update references to latest available
NFC Forum specifications, add
clarification on specific specification
versions listed, updated figure of
NFC Forum Card Emulation Mode,
added more precise requirements for
the NFC Forum Peer Mode, NFC
Forum N-Mark related text update,applied some minor text
clarifications

Version 1.0,
April 2012

DeviceRequirements

Version 1.2, July
2012

Final

Removed Section 1.3 with the Interim
Exceptions;High level requirments for ANALOG
added;
Added the reference to the RTD;
Minor editorial corrections.

Version 1.1,
May 2012

DeviceRequirements

Version 1.3,
December 2013

Final

Added requirement for the support of
DTA and updated the DTA version

Version 1.2,
July 2012

DeviceRequirements

Version 1.4.01,
March 2016

Final

v1.4.00, July 2015
Addition of high level requirements forversion 1.1 of DIGITAL and ACTIVITY
1.4.01, Feb 2016
- new logo included in all occurences- editorial improvements

Version 1.3,
December 2013

DeviceRequirements

Version 1.5.02,
February 2017

Final

v1.5.01, September 2016
Update to incorporate ANALOG v2.0 for
Certification Release 10
v1.5.02, February 2017
Added [ARCHITECTURE] in section
1.4.
Changed http link in Appendix C.

Version 1.4.01,
March 2016

DevicesRequirements

Version 2.0.00,
August 2017

Final

Addition of NFC Tag and Reader Deviceclasses as well as Tag Performancerequirements.

Version 1.5.02,
February 2017

DevicesRequirements

Version 2.1,
June 2018

Final

Addition of the following features:- P2P ACM
- T4T OP MV3.0- T5T OP

Version 2.0.00,
August 2017

Devices Requirements

Page 62

Revision History
Document
Name

Revision andRelease Date

StatusChange Notice

Supersedes- for T4ABT OP, frame size larger than
256B may be supported
The support of the T1T OP has been
made optional for the NFC Universal andReader Devices.
DevicesRequirements

Version 2.1.01
January 2020

Final

Changes version number of several
Technical Specifications in the
Reference documents

Version 2.1,
June 2018

DevicesRequirements

Version 3.0
September 2021

Final

-

RF Collision Avoidance Req.
Extended
T1T OP removed
Specific market ecosystem addition
CCC Device Classes addition
Operating Volume and Reference
Equipment section addition
Appendix B, device classcompatibility analysis forcertification

Version 2.1.01

WLC feature and device classes
addition
USI WLC reader device addition
CE Device addition

Version 3.0

Update requirement for T4T MV3.0
APDU size
Add minimum requirement on
maximum NDEF message size

Version 3.1
November 2021-

DevicesRequirements

Version 3.1
November 2021

Final

-

DevicesRequirements

Version 3.2
March 2022

Final

-

Devices Requirements

Page 63