© 2013 AT&T Intellectual Property

AT&T Developer Program

Near Field Communication and Open Mode Mobile Apps

Whitepaper

Revision 1.0 Revision Date 03/22/2013

Legal Disclaimer

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 ii

This document and the information contained herein (collectively, the "Information") is provided to you (both the individual receiving this document and any legal entity on behalf of which such individual is acting) ("You" and "Your") by AT&T, on behalf of itself and its affiliates ("AT&T") for informational purposes only. AT&T is providing the Information to You because AT&T believes the Information may be useful to You. The Information is provided to You solely on the basis that You will be responsible for making Your own assessments of the Information and are advised to verify all representations, statements and information before using or relying upon any of the Information. Although AT&T has exercised reasonable care in providing the Information to You, AT&T does not warrant the accuracy of the Information and is not responsible for any damages arising from Your use of or reliance upon the Information. You further understand and agree that AT&T in no way represents, and You in no way rely on a belief, that AT&T is providing the Information in accordance with any standard or service (routine, customary or otherwise) related to the consulting, services, hardware or software industries. AT&T DOES NOT WARRANT THAT THE INFORMATION IS ERROR-FREE. AT&T IS PROVIDING THE INFORMATION TO YOU "AS IS" AND "WITH ALL FAULTS." AT&T DOES NOT WARRANT, BY VIRTUE OF THIS DOCUMENT, OR BY ANY COURSE OF PERFORMANCE, COURSE OF DEALING, USAGE OF TRADE OR ANY COLLATERAL DOCUMENT HEREUNDER OR OTHERWISE, AND HEREBY EXPRESSLY DISCLAIMS, ANY REPRESENTATION OR WARRANTY OF ANY KIND WITH RESPECT TO THE INFORMATION, INCLUDING, WITHOUT LIMITATION, ANY REPRESENTATION OR WARRANTY OF DESIGN, PERFORMANCE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, OR ANY REPRESENTATION OR WARRANTY THAT THE INFORMATION IS APPLICABLE TO OR INTEROPERABLE WITH ANY SYSTEM, DATA, HARDWARE OR SOFTWARE OF ANY KIND. AT&T DISCLAIMS AND IN NO EVENT SHALL BE LIABLE FOR ANY LOSSES OR DAMAGES OF ANY KIND, WHETHER DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE, SPECIAL OR EXEMPLARY, INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, LOSS OF GOODWILL, COVER, TORTIOUS CONDUCT OR OTHER PECUNIARY LOSS, ARISING OUT OF OR IN ANY WAY RELATED TO THE PROVISION, NON-PROVISION, USE OR NON-USE OF THE INFORMATION, EVEN IF AT&T HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES OR DAMAGES.

Table of Contents

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 iii

© 2013 AT&T Intellectual Property All rights reserved.

AT&T, AT&T logo, Cingular and Cingular logos are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies.

All marks, trademarks, and product names used in this document are the property of their respective owners.

1 Introduction ....................................................................................................................................... 1

2 Scope and Audience ......................................................................................................................... 3

3 NFC Ecosystem ................................................................................................................................ 4

4 NFC Standards ................................................................................................................................. 6 4.1 NFC Forum .............................................................................................................................. 6

4.1.1 NFC Data Exchange Format (NDEF) ........................................................................... 6 4.1.2 Simple NDEF Exchange Protocol (SNEP).................................................................... 7 4.1.3 NFC Tags.................................................................................................................... 7

4.2 Global Platform ........................................................................................................................ 9 4.3 GSMA: Single Wire Protocol NFC handsets ........................................................................... 10 4.4 NFC Protocol Stacks.............................................................................................................. 11 4.5 NFC Smart Card Standards ................................................................................................... 12

5 Native NFC Framework for App Development ................................................................................. 13 5.1 Understanding Android NFC .................................................................................................. 13

5.1.1 Android NFC APIs ..................................................................................................... 14 5.1.2 Summary of the classes: ........................................................................................... 15

5.2 Understanding WP8 NFC ....................................................................................................... 16 5.3 Understanding the BlackBerry NFC Framework ..................................................................... 17

5.3.1 BlackBerry OS 7.1 APIs............................................................................................. 18 5.3.2 BlackBerry OS 10 ...................................................................................................... 19 5.3.3 BlackBerry Invocation Framework (IF) ....................................................................... 19

6 NFC Use Cases .............................................................................................................................. 21 6.1 Retail ..................................................................................................................................... 21 6.2 Social Media .......................................................................................................................... 21 6.3 Gaming and toys.................................................................................................................... 22 6.4 Location ................................................................................................................................. 22 6.5 Media and advertising ............................................................................................................ 22 6.6 Business cards and calendaring............................................................................................. 23

Table of Contents

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 iv

6.7 Device pairing ........................................................................................................................ 23 6.8 Product authentication ........................................................................................................... 24

7 Conclusion ...................................................................................................................................... 25

8 Terms and Acronyms ...................................................................................................................... 27

9 Contact Information ......................................................................................................................... 28

10 Works Cited .................................................................................................................................... 29

Figures Figure 1: The three modes of NFC ........................................................................................................... 2 Figure 2: NFC History .............................................................................................................................. 4 Figure 3: NDEF message format. ............................................................................................................. 7 Figure 4: GSM Association, requirements for SWP NFC Handsets V4.0. ............................................... 10 Figure 5: Protocol Stacks for NFC 3 Operation modes. .......................................................................... 11 Figure 6: NFC Operating Modes ............................................................................................................ 12

Tables Table 1: NFC Tags .................................................................................................................................. 8 Table 2: Summary of NFC Support by Platforms .................................................................................... 13 Table 3: NFC Tag Dispatch System Workflow ....................................................................................... 14 Table 4: NFC APIs Classes ................................................................................................................... 16 Table 5: Primary Windows NFC runtime classes. ................................................................................... 17 Table 6: BlackBerry 10 NFC Library Files .............................................................................................. 19

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 1

1 Introduction Near Field Communication (NFC) is a short-range wireless connectivity technology (also known as ISO 18092) that is built upon Radio Frequency Identification (RFID) technology. NFC operates at 13.56 MHz and transfers data at a rate up to 424 Kbits/second. It is also called “contactless” technology because there is no need for contact between two NFC devices, though the distance between them should be very small (about 10 cm).

NFC has the following three operational modes (shown in Figure 1: The three modes of NFC);

• Open mode to read from or write to tags: An NFC enabled device can read or write to an NFC tag.

An NFC reader is an active device that generates radio signals to communicate with NFC tags based on the ISO 15693 standard, provided that the tags employ the NFC Data Exchange Format (NDEF). An NFC tag is a thin, simple, and passive device that contains an antenna and memory, and that is powered by a magnetic field. For example; an NFC reader can read a sticker with an NFC tag embedded in order to download an application from the tag. An NFC writer can write an app to an NFC tag.

• Open mode to tap to connect and share: When two NFC enabled devices are brought within four centimeters of one another, a handshake is performed between the two devices in order to establish a connection. Once a connection is established, data can be transferred without the need for manual configuration.

• Secured mode that emulates a card: An NFC enabled device can be used for retail payments by using a mobile wallet app, or it can be used for accessing a secured building. A Secure Element (SE) is used in this mode.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 2

Figure 1: The three modes of NFC

NFC provides an easily interactive opportunity for end users, as well as new opportunities for engagement, configuration, data collection and distribution due to its ability to connect offline devices to online devices. The simplicity of the NFC technology makes it appealing to businesses and consumers. When combined with mobile and Cloud many interesting use cases and useful apps can be developed through mobile app developers’ creativity and insights.

ABI Research expects 285 Million NFC-enabled devices to be shipped in 2013 and believe the NFC will come out of its “trial phase”. The increase in potential use base is making the investment in NFC applications more justifiable (ABI, 2012) .

)))

Read/Write Peer-to-Peer

Card Emulation

Smart

Local

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 3

2 Scope and Audience This whitepaper provides an overview of the NFC technology. It is intended for mobile app developers who have little knowledge about NFC and who are interested in developing NFC apps.

The focus of this whitepaper is to address what NFC is, what kind of NFC standards are in work, and the frameworks that are available for developers to use in order to create Open Mode mobile apps.

After introducing the NFC ecosystem, this white paper provides an overview of important standards (data exchange, NFC tags, device interface protocols and communication protocol) to help understand the NFC fundamentals. With this knowledge, the developer will be able to easily read the specifications.

The white paper further explains the NFC mobile application development framework and the positioning of the current state of available technologies for mobile app development.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 4

3 NFC Ecosystem Since NFC is a connectivity technology based on RFID, its history has been under development since 1983 when the first RFID patent was granted. The first NFC-enabled phone was released in 2006 by Nokia. See Figure 2: NFC History.

Figure 2: NFC History

While the predominate use case for NFC has focused on payments and secure transactions enabled through the use of Secure Elements, NFC is not just about payment. The power of NFC as an enabling technology lies in its ability to open up new forms of communications, content discovery, social interaction, and sharing. All this is done through a simple and straightforward act of touching their device to a sign, poster, terminal, or another device to initiate interaction; removing the need for complex manual configurations.

An entire ecosystem stands ready to support applications ranging from contactless payment cards to authentication between mobile devices. This ecosystem includes a chip such as NFC-enabled microcontrollers, standards for wireless transactions, and protocol stacks for handling various communication tasks. (Zlatoustovskiy, NFC Expert, 2011)

The key players consist of telecom operators, manufacturers (readers, tags, smart cards, semiconductors, and consumer electronics), mobile device OEM, system integrators, banking/ financial institutions, merchant consumers, education, research, and government.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 5

In order to facilitate the growth of the ecosystem, communication and connectivity standards need to be agreed upon by key players so that fragmentation can be reduced and an investment can be made.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 6

4 NFC Standards NFC standards are acknowledged by ISO/IEC (International Organization for Standardization / International Electrotechnical Commission), ETSI (European Telecommunications Standards Institute), and ECMA (European association for standardizing information and communication systems).

4.1 NFC Forum The NFC Forum is a non-profit industry association that advances the use of NFC. It was formed in 2004 and now has 160+ members. It develops specifications, ensures interoperability among devices, and services and educates the market about NFC technology. The NFC Forum has released eighteen specifications to define core functions as follows:

• Data Exchange formats

• Tag types

• Record type definition

• Device interface controller

• Protocols

• Reference applications

Its 16th specification is the Simple NDEF Exchange Protocol (SNEP). SNEP is an application-level protocol suitable for sending or receiving messages between two NFC enabled devices. It uses NFC Logical Link Control Protocol (LLCP) to exchange NDEF messages. The SNEP and LLCP specifications are available to the public for download at no charge at the following location: NFC Forum: Technical Specifications.

4.1.1 NFC Data Exchange Format (NDEF) The NFC Data Exchange Format (NDEF) specification defines a message encapsulation format used to exchange information between NFC enabled devices or an NFC enabled device with an NFC tag. An NDEF message is composed of one or more NDEF records (NFCForum, 2006)

Each record carries a payload. For NFC-specific data types, the payload contents are defined in an NFC Record Type Definition (RTD) file which includes the type of data in the record and the size of the record. The type and size are indicated in a header attached to the payload. It is a lightweight binary format that can carry URLs, vCards and NFC-specific data types. In addition, because NDEF

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 7

abstracts tag type-specific details from the application layer NDEF allows NFC functionality to easily use any supported tag type to transfer data.

Figure 3: NDEF message format.

4.1.2 Simple NDEF Exchange Protocol (SNEP) The Simple NDEF Exchange Protocol (SNEP) is an application-level protocol that is suitable for sending or retrieving application data units in the form of NDEF messages between two NFC enabled devices operating in Peer Mode (NFCForums, 2011)

SNEP itself runs on top of an intermediate layer in the stack that contains a protocol called the Logical Link Layer Protocol (LLCP). Beneath the LLCP layer there are some optimizations for Peer to Peer Mode that are defined in a specification known as ISO 18092.

4.1.3 NFC Tags NFC tags are simple devices containing an antenna and a limited amount of memory. Because they are passive devices without power, NFC tags are used to communicate with active NFC readers and writer. When an active NFC device touches the tag, the tag takes a small amount of power from it and activates its electronics to transfer data to the NFC device.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 8

Usually, a small amount of data is stored on the NFC tag’ memory to serve as a pointer to other information; for example URLs to resources. The tags can be embedded in various mediums for accessing; for example a poster can contain a tag.

The initial NFC tag specification was released by the NFC Forum in 2006 (Forum, 2006). The NFC Forum defines four types of tags that provide different communication speeds and capabilities in terms of configurability, memory, security, data retention, and write endurance. Refer to the Table 1: NFC Tagsfor the tags standards, features, memory limitation, and speed. NFC Forum Tag Type Technical Specifications can be downloaded from the following location after a license agreement is signed: NFC: Specification Download.

Tag Type

Standard Features Memory Speed

1 ISO-14443A

Read, re-write or read-only; No data collision protection

96 bytes; expandable to 2KB

106 Kbits/second

2 ISO-14443A

Read, re-write or read-only Anti-collision support

48 bytes; expandable to 2KB

106 Kbits/second

3 JIS X 6319-4

Read, re-write or read-only Anti-collision support

Variable memory, up to 1 MB per service

212 or 424 Kbits/second

4 Compatible with ISO14443 (A&B)

Read, re-write or read-only Anti-collision support

Variable memory, up to 32 KB per service

106, 212 or 424 Kbits/second

Table 1: NFC Tags

An NFC reader is an active device that generates radio signals to communicate with NFC tags based on the ISO 15693 standard, provided that the tags employ the NFC Data Exchange Format (NDEF).

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 9

To download the complete NDEF specifications, go to the NFC Forum Specification Download site.

4.2 Global Platform Global Platform is a non-profit association. It identifies, develops and publishes specifications that facilitate the secure and interoperable deployment and management of multiple embedded applications using secure chip technology.

The association published a white paper "Global Platform's Requirements for NFC Mobile: Management of Multiple Secure Elements" [dated February 2010] to describe the requirements for managing multiple Global Platform Secure Elements.

Many of the potential NFC services require one or more Secure Elements to store keys and applications. With the use of appropriate standards to manage Secure Element contents; it is possible to achieve consistency, reliability, and interoperability in the NFC ecosystem.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 10

4.3 GSMA: Single Wire Protocol NFC handsets The following figure provides a high level architecture for the NFC mobile phone suggested by GSMA.

UICC is the smart card (defined in 3GPP TS102 221) that contains account information and memory that is used to enable GSM and UMTS cellular devices. Secure Element (SE) is the smart card in the handset that stores and executes the contactless applications. The NFC controller interfaces with UICC by using the Single Wire Protocol (SWP) and the Host Controller Interface (HCI).

Figure 4: GSM Association, requirements for SWP NFC Handsets V4.0.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 11

4.4 NFC Protocol Stacks There are three protocol stacks that support NFC communication; the peer-to-peer stack, card emulation stack, and reader/writer stack. (Zlatoustovskiy, NFC Expert, 2011)

Figure 5: Protocol Stacks for NFC 3 Operation modes.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 12

4.5 NFC Smart Card Standards NFC Devices can operate in three different modes as specified by the ISO/IEC 18092, NFC IP-1 and ISO/IEC 14443 contactless smart card standards as shown in Figure 6: NFC Operating Modes.

The reader/writer mode on the RF interface is compliant with the ISO 14443 and FeliCa Schemes. (NFC-IP1Type A is based on ISO 14443, and Sony FeliCa is a contactless technology based on ISO18092 (212k/424k NFCIP1 Passive) [4] as the RF and on JIS X 6319-4 [5] as the command set.

The Peer-to-Peer mode is standardized on the ISO/IEC 18092 standards.

Figure 6: NFC Operating Modes1

1 Source: NFC Forum

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 13

5 Native NFC Framework for App Development Currently there are three NFC frameworks for mobile app developers to use when creating open mode NFC apps. Their release history is as follows:

• Google added NFC support to the Android 2.3 (Gingerbread) platform in 2010 and Google Nexus S was the first Smartphone to have NFC capability

• Blackberry first added NFC capabilities to its BlackBerry OS 7.0 platform with the launch of the Blackberry 9900 and 9930 in 2011 (Clark, 2011)

• Windows Phone 8 is the first Microsoft mobile OS that supports NFC with Proximity APIs. Nokia 920 and 820 were the first Windows Phone 8 devices released in November 2012.

OS P2P Reader/Writer Card Emulation

Android 2.3 and greater

YES YES Restricted

Blackberry OS 7.0 and greater

YES YES Restricted

Windows Phone 8 YES YES Restricted

Table 2: Summary of NFC Support by Platforms

5.1 Understanding Android NFC The 2010 release of the Google Nexus S Smartphone heralded the arrival of NFC on Android. With it, Google introduced “Google Wallet” as well as Read/Write mode that is enabled in the 2.3.x “Gingerbread” release of Android. Google further enhanced Android NFC capabilities in the 4.0 “Ice Cream Sandwich” release with the introduction of Android Beam™ peer-to-peer sharing. With Android 4.1, Android Beam™ was further enhanced to enable the use of Bluetooth.

Android NFC services include

• Read / Write mode for content discovery

• Contact Exchange

• Android Beam™ - Peer to Peer sharing via Wi-Fi Direct and Bluetooth

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 14

5.1.1 Android NFC APIs NFC Basic describes the NFC tasks that you may perform using Android. It explains how to send and receive NFC data in the form of NDEF messages and describes the Android framework APIs that support these features. Code Samples are given in the documentation (Google, MFC Basics).

The following workflow (Google, MFC Basics) shows how NFC Tags are dispatched to apps

Table 3: NFC Tag Dispatch System Workflow

When applications are not working with NDEF data, or are working with NDEF data that Android cannot fully understand, developers need to manually read or write to the tag in raw bytes using their own protocol stack. In this case, Android provides support to detect certain tag technologies and to open communication with the tag using the applications own protocol stack.

Android provides generic support for these use cases with the android.nfc.tech package. The android.nfc.tech API provides access to technology features of a tag, which vary by the type of tag that is scanned. A scanned tag can support multiple technologies, and you can find out what they are by calling getTechList( ).

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 15

For more information about dealing with tag technologies and handling the ones that you care about, see The Tag Dispatch System. The TagTechnology interface provides an overview of the supported technologies.

5.1.2 Summary of the classes: Android.nfc (Google, Package Android.nfc) provides access to NFC functionality, allowing applications to read NDEF message in NFC tags. An NFC tag may also be a device that appears as a tag.

There are six classes of NFC APIs as showed in the table below:

Class Description

NfcAdapter Represents the local NFC adapter, which is the entry-point to performing NFC operations. Use the helper getDefaultAdapter(Context) method to obtain the default NFC adapter for this Android device.

NfcManager Used to obtain an instance of an NfcAdapter. Use the getSystemService(java.lang.String) method with NFC_SERVICE to create an NfcManager, then call the getDefaultAdapter() method to obtain the NfcAdapter.

NdefMessage Constructs an NDEF Message by parsing raw bytes. Represents an immutable NDEF Message, which is the standard format in which "records" carrying data are transmitted between devices and tags. Your application can receive these messages from an ACTION_TAG_DISCOVERED intent.

NdefRecord Represents an immutable NDEF record, which is delivered in an NdefMessage and describes the type of data being shared and carries the data itself. An NDEF record contains typed data, such as MIME-type media, a URI, or a custom application payload. An NDEF message is a container for one or more NDEF records.

NfcEvent An immutable object the provides direct access to the (final) fields and usually is included in callbacks from NfcAdapter.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 16

Tag Represents an NFC tag that has been discovered. Tag is an immutable object that represents the state of a NFC tag at the time of discovery. It can be used as a handle to TagTechnology classes to perform advanced operations or directly queried for its ID via getId( ) and the set of technologies it contains via getTechList( ).

Table 4: NFC APIs classes.

For more information, see the Near Field Communication guide.

5.2 Understanding WP8 NFC In February 2012, Microsoft published a whitepaper titled “Windows 8 Near Field Proximity Implementation Specification”. It provided information about the implementation of Near Field Proximity solutions for Windows 8. In November 2012, Nokia 920 and 820 were released as the first Windows Phone 8 devices with NFC capability.

The Proximity API in the Windows 8 platform provides two new local communication methods; one for Bluetooth and one for NFC. It consists of classes in the namespace of Windows.Networking.Proximity and supports connections between devices that are within close range of each other. Other networking related classes, such as StreamSocket from the Windows Networking namespace, are very closely related to proximity operations and are often used in conjunction with it. For details on the networking namespace see the MSDN Networking API reference. (Using NFC to establish a persistent connection, 2013)

The Proximity API is used for NFC tasks (Proximity and Near Field Communication, 2013) to accomplish the following:

• Read and write NFC tags

• Exchange data between devices using NFC

• Use NFC to set up a Wi-Fi or Bluetooth connection between two phones for further longer range wireless communication

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 17

The following table lists the primary Windows’ Runtime classes (Microsoft, 2013):

Class Description

PeerFinder Enables discovery of another instance of the same app on a nearby device and create a socket connection between the peer apps by using a tap gesture, or by browsing. A peer app is another instance of an app that is running on another device.

ProximityDevice Enables apps to communicate with other devices within an approximate range of 3–4 centimeters, and exchange a small payload of data during the tap.

PeerInformation Contains information that identifies a peer.

ProximityMessage Represents a message that's received from a subscription.

ConnectionRequestedEventArgs

Contains properties that are passed to an application with the ConnectionRequested event.

TriggeredConnectionStateChangedEventArgs

Contains properties that the TriggeredConnectionStateChanged event passes to an application.

Table 5: Primary Windows NFC runtime classes.

A complete overview of Proximity for Windows Phone 8 can be found at the following location: http://msdn.microsoft.com/en-US/library/windowsphone/develop/jj207060(v=vs.105).aspx#BKMK_ProximityAPI

The Near Field Proximity Sample Driver demonstrates how to use User-Mode Driver Framework (UMDF) to write a near-field proximity driver.

5.3 Understanding the BlackBerry NFC Framework In August 2011, BlackBerry 7 Operating System (OS) was launched with the first NFC capable devices: the BlackBerry Bold 9900/9930/9790 and the BlackBerry

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 18

Curve 9350/9360/9370 (D, 2012). In January 2013, RIM officially introduced the BlackBerry 10 OS to the mobile world (BlackBerry 10 Release Event).

There are different ways to work with NFC in the BlackBerry 10 OS. NFC applications can be developed using a combination of C/C++, Cascades, and the invocation framework. Using C/C++ gives a developer access to the lower level operations of the NFC service and allows full control over the user experience. On the other hand, Cascades and the invocation framework hide the lower level aspects of service interactions, providing a quick and easy way to exploit the power of NFC (Using the general NFC service capabilities).

5.3.1 BlackBerry OS 7.1 APIs BlackBerry OS 7.1 introduced the BlackBerry tag. The Blackberry tag enables the following:

• Invite friend to BBM

• Exchanging contact information

• Sharing apps from Blackberry App World Storefront

• Sharing content, files, video, pictures, music and voice notes

• Pairing to NFC enabled Bluetooth devices

BlackBerry Applications provide whatever functionality that is desired and makes use of the NFC APIs for NFC use cases. NFC applications must be written in Java.

Blackberry 7 devices ship with standard reader/writer application Smart Tags. It enables reading and writing of NDEF compatible tags. Developing a blackberry tag reading application is relatively straightforward. It requires:

• Implementing the NDEFMessageListener interface

• Registering the listener with the system, including the NDEF record type to be read

• Parsing and acting on NDEF messages received by NDEFMessageListener

More specifics for Java SDK 7.1 NFC features can be found at the following location: Blackberry Java SDK 7.1: Near Field Communication

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 19

5.3.2 BlackBerry OS 10 Details of the Blackberry OS 10 support for NFC were first revealed in mid-2012 and the first two smartphones (Z10 touchscreen and Q10 Qwerty) to run the new BlackBerry 10 have been launched in January 2013.

In Blackberry OS 10, the NFC library provides various APIs for creating applications. See the table below for various files in the NFC library (BlackBerry Native SDK):

Library Files Description

nfc.h General functions for the Near Field Communication (NFC) API.

nfc_bps.h Functions available to enable applications to connect with Near Field Communication (NFC) systems using the BlackBerry Platform Services (BPS) event framework.

nfc_ndef.h Functions for Near Field Communication (NFC) Data Exchange Format (NDEF)

nfc_types.h Contains various enumerations, typedefs, and structures used to work with the New Field Communication (NFC) library

nfc_se_access.h Functions to provide access to the secure elements of the device

nfc_se_transaction.h Functions to parse and process transaction notifications from the secure elements (SEs) on the device.

Table 6: BlackBerry 10 NFC Library Files

Details of the BlackBerry 10 NFC Library can be found at http://developer.blackberry.com/native/beta/reference/com.qnx.doc.nfc/topic/manual/nfc_lib_nfc_conceptual_overview.html

5.3.3 BlackBerry Invocation Framework (IF) The Invocation Framework (IF) was introduced in the 10.0.06 Dev Alpha release and provides the ability for one application to invoke another by sending it a message. When an application calls for an invocation on some content, the

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 20

invocation framework responds with appropriate applications that can carry out a requested action on that particular content.

Many of the capabilities of NFC on the device have been integrated with the Invocation Framework in order to allow the developer to focus on the business logic of his application rather than having to be concerned with lower level aspects of how NFC works (NFC on BlackBerry 10 - Reading and Writing Tags using native APIs, 2012). This means that simpler integration of NFC capabilities with the higher level APIs in Qt and QML become possible.

Qt is a cross-platform application framework that is used to develop GUI (and non-GUI) applications. Qt uses and extends C++ through a code generator with Qt specific macros. Qt consists of several modules such as Core, GUI, Network, Multimedia etc. The Core modules supply an application developer with a Qt event loop and a signal/slot mechanism. This is generally used as the primary mechanism for sending and receiving messages within an application process. BlackBerry 10 utilizes the Qt framework and provides the Qt NFC API for sending and receiving content over NFC (Introduction to NFC and Qt). For more information on Invocation Framework and NFC, see Cascades ™ for BlackBerry 10: Near Field Communication.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 21

6 NFC Use Cases Open Mode NFC offers significant opportunity to imagine and create applications that leverage what NFC offers. The uses are virtually limitless with the potential to fundamentally change the way people interact with each other and the world around them.

6.1 Retail In the retail space, NFC changes the way customers interact with products and stores. With a tap of their device against a product or product display, customers can access detailed product information including ratings, reviews, care instructions, customization and upgrade options. They will be able to directly access information about incentives, promotions, discounts, and loyalty and membership benefits.

Customer service can be raised to a new level by enabling sales persons to respond to customers “on demand” and as needed. Narian Line is one such example. Part of the NFC4Retail platform from the Narian Line is an app designed to spare customers from having to stand in line for in-store services. The company describes it as "a modern, smarter upgrade" of "the dreaded take-a-number system" (Narian Line). Consumers touch a tag with their NFC phone to reserve a place in line, and then they continue with their shopping. When they can be served, the customer is paged with a built-in time buffer so they don't have to abandon what they are doing and rush back across the store.

6.2 Social Media NFC technology offers outstanding possibilities for social media (Facebook, LinkedIn, Twitter) updates, communication and sharing location information as well as for promoting products and events. Using NFC to enable consumers to “like” and share real-life content back onto their Facebook and Twitter pages is forthcoming.

Up until now “liking” and sharing on Facebook has remained for the most part an online activity, “liking” content via Facebook buttons on websites or within Facebook news feeds. By taking this process into the real world, NFC technology enables users to “like” and “share” anything they see with an NFC Facebook tag. For example, imagine browsing in a store and wanting to tell friends about the latest item that you are looking to buy. Using NFC on your smartphone, you will now be able to “like” the item from within the store and post this onto your Facebook wall. By making it easy for fans and customers to “share” and “like” as

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 22

part of the in-store browsing experience, the possibilities for brands to extend their reach and visibility into social media are significant.

Additionally, services that cater to event planning and viral marketing will find a creative use for NFC to spread the message on social networks. Users can tap on NFC tags at venue locations to update their location-based status and indirectly advertise via their social networks.

6.3 Gaming and toys NFC is already being utilized to elevate gaming and enhance toys. The Silicon Valley start-up Nukotoys has built a new kind of company that uses NFC technology to produce toys that children can play with in the real world and online. Their goal is to develop interconnected toys, trading cards and video games that take existing playground play patterns and use NFC to bring them into the virtual world so that children are equally engaged online and offline.

In the pursuit to merge digital and “real” goods, game makers are embedding NFC tags in plush toys linked to games. Rovio, the maker of highly successful mobile game Angry Birds, introduced stuffed toys that have NFC chips inside them. They also showcased an Angry Birds game that unlocked new levels and characters with an NFC-enabled phone. Tapping these “tags” together with friends would reveal new gaming levels.

6.4 Location Location services based on NFC may be related to logging/sharing location information, mapping/navigation, proximity/access control, healthcare, and online schedules. Combining GPS navigation and NFC gives truly accurate location information. Tourism can be enhanced with the use of geo-relative NFC tags.

Foursquare has updated its Android app to include support for tap-and-go check-ins and P2P sharing using NFC. The app will now be able to read NFC tags at a location and immediately take a user to a venue page, where they can check in. Users will also be able to share venues and lists and become friends by tapping their phones together using Android Beam, Google’s P2P NFC application. Foursquare previously showed off a test of NFC support last year at Google I/O.

6.5 Media and advertising NFC enabled advertisements allow direct interaction with users and a transfer of the experience to their mobile devices. For example, a user tapping on an

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 23

advertisement poster for a movie would be able to instantly preview a trailer and immediately purchase tickets or browse reviews. Capturing the attention of customers—as well as finding opportunities to engage with them—needs to happen very quickly when it comes to advertising and marketing. NFC allows this to occur instantaneously in comparison to many other avenues of customer interaction and user experience. It can augment existing promotions and campaigns to extend their reach and increase conversion.

Using NFC, users can make call requests to people, dial service phone numbers advertised via an NFC label for instant calls, add voice or video greetings to birthday cards or hear new music. When advertising websites and online shops through an NFC link, users are directly connected to the target site. NFC tags can have cross-media functionalities when attached to smart posters, pictures, cards, VIP badges, stickers or magazines providing access to exclusive internet content or downloadable NFC mobile phone applications. With NFC, it’s possible to view the menu when passing an interesting restaurant, book a table or order take-out.

6.6 Business cards and calendaring Uploading contact information or adding calendar entries is easier with NFC. By encoding NFC tags with business card or calendar entry information, users with NFC-capable devices will have the fastest and most convenient way to save contact details to their smartphones, address books, and calendars.

MOO.com's new NFC-enhanced cards—what the company refers to as a "third side" to a business card—have a built-in NFC tag. A touch of the card to an NFC-enabled smartphone can download your portfolio, play music, videos, load Web pages, maps, apps, and save your contact information.

Users can write and rewrite the URL on the chip to direct people to any digital properties. For example, a real estate agent could highlight different listings every day, or a local retailer could highlight seasonal sales and promotions.

6.7 Device pairing Device pairing is simplified with NFC. NFC-enabled (and realistically, Bluetooth enabled) devices can “connect” instantly as the complexity of pairing is reduced to a tap. Possible pairing NFC devices will include a wireless keyboard, speaker, headsets, handsets, camera, digital frames, in-car components, home entertainment system, and home computing components.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 24

6.8 Product authentication Authenticating products; whether highlighting the origin and production information or as a defense against counterfeiting; is enhanced with NFC. NFC technology companies have promoted the idea of using NFC tags to foil counterfeiters of luxury goods for some time. More companies are proposing to combine the antipiracy technology with brand-marketing messages.

ClikGenie, a U.S.-based app developer working with a tag supplier and printer, have produced an app that authenticates wine labels while also enabling vineyards and other wine brand promoters to send consumers more information using a tap of their NFC phones. ClikGenie, along with NFC tag supplier Smartrac and chip encoder and label printer FineLine Technologies, recently released CLIKSecure. CLIKSecure is an NFC product authentication app that combines tag-based product authentication with merchandising. The app adds an anti-counterfeiting feature to ClikGenie’s lineup, which had focused on mobile merchandising and promotion using 2-D bar codes.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 25

7 Conclusion NFC makes tapping a new consumer practice. The simplicity of tapping and the high volume deployment of the NFC devices will give the consumer the possibility to interact with the real world and the virtual world. For example, Nintendo uses NFC in the new Wii U gaming console; new playable characters can be added to a game by scanning its NFC chip and “importing” a virtual version into the Wii U game (Wii U NFC). Another example is how Hyundai will allow owners to unlock and start their cars with an NFC-enabled phone in the future. (Unlock your Hyundai with a tap of your smartphone by 2015, 2012)

Given the focus on open mode NFC, the opportunities for applications among the Tag Read/Write and Peer-to-Peer are greater than the opportunities for Card Emulation. The reason for this difference is that the Card Emulation mode has limited use cases that stand in contrast to secured NFC. Currently, the Read/Write mode offers the most opportunity for developers to innovate.

Although there are opportunities for Peer-to-Peer sharing, Peer-to-Peer sharing is complicated due to the differences between the operating systems as well as differences between devices from competing manufacturers. However, because the SNEP standard is part of the NFC Forum’s compliance and certification program for devices this could help reduce proprietary implementations. SNEP is enabled in Android 4.0.0 (API level 14), RIM and Windows Phone 8 NFC API. The ISMB-SNEP open source project is working on enabling Peer-to-Peer over NFC by using NPP and SNEP (Lotito).

NFC enabled devices will be used in a wide array of business applications. In order to be ready for the wave of opportunity that NFC will bring, it is important that developers are familiar with the use cases, standard protocols, and the current APIs using NFC technology. This paper provides the fundamental knowledge needed to start developing NFC apps.

Some recommendations to app developers are as follows:

• Deliver more convenient new products and service by using NFC’s read/write mode.

NFC is opening up opportunities for many new products and services. Think of use cases that impact the every life of consumers. Anticipate the impact of NFC on your business and apps.

• Use NFC to complement existing apps and services.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 26

Use NFC as an enabler to expand your current apps to the next level with tapping for establishing connectivity or information exchange.

• Make sure that the privacy of consumers is considered and addressed.

• Explore Peer-to-Peer implementations and support standards.

Proprietary systems prevent the NFC ecosystem from moving forward. Feedback to the standards body and advocates for the need to standardize will help to bring stakeholders to the next level alignment.

NFC, a disruptive technology for the mobile world, is presenting a wide open space for developers to explore and discover its power. NFC devices are available. We need more innovation, products and services in order to take advantage of the technology.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 27

8 Terms and Acronyms The following terms and acronyms are used in this whitepaper,

Acronym Definition API Application Programming Interface ECMA European association for standardizing information and

communication systems GUI Graphical User Interface HCI Host Controller Interface IEC International Electrotechnical Commission IF Invocation Framework ISO International organization for Standardization ms millisecond LLCP Logical Link Control Protocol OEM Original Equipment Manufacture OS Operating System NDEF MFC Data Exchange Format NFC Near Field Communication RFID Radio Frequency Identification RTD NFC Record Type Definition SDK Software Development Kit SE Secure Element SNEP Simple NDEF Exchange Protocol SWP Single Wire Protocol UICC Universal Integrated Circuit Card URL Uniform Resource Locator

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 28

9 Contact Information E-mail any comments or questions regarding this whitepaper to the AT&T Developer Program Web site. Please reference the title of this document in your e-Mail.

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 29

10 Works Cited The following works are cited in this whitepaper.

NFC on BlackBerry 10 - Reading and Writing Tags using native APIs. (2012, 11 2). Retrieved from BlackBerry Support Community: http://developer.blackberry.com/cascades/documentation/device_platform/invocation/invocation_framework.html

Unlock your Hyundai with a tap of your smartphone by 2015. (2012, 12 31). Retrieved from CNET: http://reviews.cnet.com/8301-13746_7-57561451-48/unlock-your-hyundai-with-a-tap-of-your-smartphone-by-2015/

Proximity and Near Field Communication. (2013, 2). Retrieved from Nikia Developer: http://www.developer.nokia.com/Community/Discussion/showthread.php?239396-New-NFC-and-Proximity-documentation-on-Windows-Phone-8&p=912124

Proximity and Near Field Communication. (2013, 2). Retrieved from Nokia Developer: http://www.developer.nokia.com/Community/Discussion/showthread.php?239396-New-NFC-and-Proximity-documentation-on-Windows-Phone-8&p=912124

Using NFC to establish a persistent connection. (2013, 2 21). Retrieved from Nikia Developer: http://www.developer.nokia.com/Resources/Library/Lumia/#!proximity-and-nfc/using-nfc-to-establish-a-persistent-connection.html

ABI. (2012, 11 2). NFC will Come Out of the Trial Phase in 2013 as 285 Million Enabled Devices are Expected to be Shipped. Retrieved from ABIresearch: http://www.abiresearch.com/press/nfc-will-come-out-of-the-trial-phase-in-2013-as-28

BlackBerry 10 Release Event. (n.d.). Retrieved from International Business Times: http://www.ibtimes.com/blackberry-10-release-event-z10-q10-phones-unveiled-rim-rebrands-itself-simply-blackberry-1048716

BlackBerry Native SDK. (n.d.). Retrieved from BlackBerry Developer: http://developer.blackberry.com/native/reference/bb10/nfc_libref/topic/manual/nfc_lib_nfc_conceptual_overview.html

Cascades™ for BlackBerry 10; NFC. (n.d.). Retrieved from BlackBerry: http://developer.blackberry.com/cascades/documentation/device_comm/nfc/

Clark, S. (2011, May 2). RIM unveils BlackBerry Bold 9900 and 9930 NFC phones. Retrieved from NFC World: http://www.nfcworld.com/2011/05/02/37197/rim-unveils-blackberry-bold-9900-and-9930-nfc-phones/

D, A. (2012, 1 12). BlackBerry Blog. Retrieved from BlackBerry : http://blogs.blackberry.com/2012/01/blackberry-tag-nfc/

Forum, N. (2006, June 5). NFC Forum News. Retrieved from NFC Forum: http://www.nfc-forum.org/news/pr/view?item_key=0b210bbd23e9c1a07cb3d975e6317d1d650ed51f

AT&T Proprietary

The information contained here is for use by authorized persons only and is not for general distribution

Whitepaper Rev. 1.0 30

Google. (n.d.). MFC Basics. Retrieved from http://developer.android.com/guide/topics/connectivity/nfc/nfc.html

Google. (n.d.). Package Android.nfc. Retrieved from http://developer.android.com/reference/android/nfc/package-summary.html

Introduction to NFC and Qt. (n.d.). Retrieved from BlackBerry Developer: http://developer.blackberry.com/cascades/documentation/device_comm/nfc/intro_to_nfc_and_qt.html

Lotito, A. (n.d.). ISMB-SNEP PROJECT. Retrieved from http://nfc-workshop.org/2013/documentation/12_Antonio_Lotito_ISMB_NFC-2013_v2.pdf

Microsoft. (2013, 2 1). Proximity for Windows Phone 8. Retrieved from http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj207060%28v=vs.105%29.aspx

Narian Line. (n.d.). Retrieved from Narian: http://www.nariantechnologies.com/ NFCForum. (2006, 07 24). NFC Data Exchange Format (NDEF) Technical

Specification. NFCForums. (2011, 8 31). Simple NDEF Exchange Protocol Technical Specification. Using the general NFC service capabilities. (n.d.). Retrieved from BlackBerry:

http://developer.blackberry.com/native/documentation/bb10/com.qnx.doc.nfc/topic/manual/c_stub_nfcdevguide_use_gen_nfc_capabilities.html

Wii U NFC. (n.d.). Retrieved from Wii U Daily: http://wiiudaily.com/wii-u-nfc/ Zlatoustovskiy, S. (2011, July). Retrieved from NFC Expert. Zlatoustovskiy, S. (2011, July). NFC Expert.