User's Manual

7 NFC
NFC reader is implemented within In-Car Trigger to retrieve the Bluetooth MAC address
and user defined data from the NFC tag implemented within BWC for triggering the
Bluetooth pairing between In-Car Trigger and BWC (refer to chapter 8 for detail
description about Bluetooth pairing)
The NFC read/write communication between In-Car Trigger and BWC follows
ISO
14443A protocol.
7.1 NFC Tag information
Storage of Each BWC’s NFC tag contains the listed data which is programmed
individually at manufacturing:
 Bluetooth MAC address
A 6 bytes length unique MAC address of the Bluetooth module within the BWC.
When performing NFC sensing with In-Car Trigger, it will be retrieved by In-Car
Trigger to initiate Bluetooth pairing.
This 6 bytes address is programmed in specific offset within the storage of NFC tag
and is not wrapped with standard NFC Data Exchange Format (NDEF). NFC
reader other than In-Car Trigger might unable to retrieve or parsing this data
successfully out from NFC tag of BWC.

User Data
A data space is preserved in NFC tag to store a user self-defined max 32 bytes
length string. When performing NFC sensing, In-Car Trigger follow the
Plain Text
record format with “
en” IANA language code specified defined within NDEF to
parse out this 32 bytes user data from the retrieved raw data and buffer it for the
connected host device’s usage.
By following the same NDEF Plain Text record format, NFC reader other than In-
Car Trigger also could read/write this user data on BWC’s NFC tag.