Orange NFC Office template

This feature is restricted and experimental. It shall not be used for anything else than internal tests.

Overview

Use this template to read an identifier from the Orange NFC Office application running on a smartphone.

Orange NFC APIs for Office is a framework for NFC services, offered by Mobile Network Operator Orange. It targets user identification applications (access control, private e-purse, car park & card sharing, and alikes). The services are provided by the smartphone either in host-based card emulation mode (HCE) or through a SIM card. Organisations are identified by an ApplicationId (variable length) and their organisation units by a ZoneId (on 6 bytes). A diversified AES key protects the data. Every user “belonging” to the organisation is identified by a Badge number on 10 bytes.

Configuration

Register t0: select the Orange NFC APIs (Office) template

Register 03t0 (1 byte) selects the template. Use C1 for Orange NFC APIs (office).

Register t1: output format

Register 03t1 defines the output format. Refer to Template engine : Output Format register.

Register t2: output prefix

Register 03t2 defines the output prefix. Refer to Template engine : Output Prefix.

Register t3: Location of data

Register 03t3 defines the Authentication method on 1 to 3 Bytes.

Bytes Content Notes / Valid range
Bytes 0 (Mandatory)
0 00: no authentication
01: use AES authentication
See below
Optional bytes
5 Offset within the field 0 to 10
6 Shift bits to the left 0 to 7

Register t4: miscellaneous options

If register 03t4 is set, the reader adds a token to its output to tell the receiver what kind of object has been read.

Bytes Bits Meaning
0 7-4 RFU
3-2 Position of the “card type” token in the output
00: Before the PFX constant
01: After the PFX constant, but before the actual data
10: After the actual data
11: RFU
0-1 Add a “card type” token to the output
00: Do not add the “card type” token
01: Add a C1 as “card type” token
10: Add a O as “card type” token
11: Add 00

Register t5: Application ID

Register 03t5 defines the Application ID on 1 to 32 Bytes.

Bytes Value
Bytes 0 to ... Application ID. This value is transmitted by the reader to the mobile phone within a SELECT APPLICATION command APDU (00 A4 04 00 … )

Register t6: Zone ID

Register 03t6 defines the Zone ID on 6 Bytes.

Bytes Value
Bytes 0 to 5 Zone ID. This value is transmitted by the reader to the mobile phone within a PUT DATA command APDU (80 B0 80 00 06 )

Register t6: Master Key

Register 03t7 defines the Master Key on 16 Bytes.

Bytes Value
Bytes 0 to 15 Master Key. This value is diversified with the data returned by the SELECT APPLICATION and used to decrypt the Badge number if the authentication is enabled.