Skip to content

Commit 19742ce

Browse files
author
Donatien Garnier
committed
Bump up use cases at the top of the doc
1 parent c1c5af9 commit 19742ce

File tree

1 file changed

+18
-18
lines changed

1 file changed

+18
-18
lines changed

features/nfc/doc/nfc_design.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,27 @@ NFC offers three modes;
77
2. NFC reader/writer
88
3. NFC peer to peer
99

10-
To support the commissioning of NFC enabled IoT endpoints, Mbed OS should support the NFC card emulation mode. This will allow for commissioning of the device via an NFC-enabled smartphone.
10+
To support new use cases such as commissioning, BLE pairing and identification/authentication of NFC enabled IoT endpoints, Mbed OS should support the card emulation mode.
1111

1212
However the architecture should be future-proofed and should also be extendable to support other NFC modes in the future.
1313

14+
## Use cases
15+
### Commissioning
16+
17+
NFC is a great medium to support commissioning requirements.
18+
19+
#### Identification
20+
21+
An NDEF message can be used to carry a device's unique identifier to ease identification before handing over to another transport medium such as BLE.
22+
23+
#### Transport
24+
25+
If the NFC controller can emulate a smartcard, no handover is necessary and the full commissioning flow can happen over NFC.
26+
27+
### BLE Pairing
28+
29+
A specifically crafted NDEF message can be used to facilitate out-of-band pairing wth man-in-the-middle protection as specified in the [Bluetooth® Secure Simple Pairing Using NFC](https://members.nfc-forum.org/apps/group_public/download.php/18688/NFCForum-AD-BTSSP_1_1.pdf) document.
30+
1431
# System Architecture and High-Level Design
1532

1633
## Compliance with NFC Forum Specifications
@@ -375,23 +392,6 @@ void on_backend_has_erased_bytes(bool success)
375392

376393
This API will be defined in phase 2.
377394

378-
# Usage Scenarios and Examples
379-
## Commissioning
380-
381-
NFC is a great medium to support commissioning requirements.
382-
383-
### Identification
384-
385-
An NDEF message can be used to carry a device's unique identifier to ease identification before handing over to another transport medium such as BLE.
386-
387-
### Transport
388-
389-
If the NFC controller can emulate a smartcard, no handover is necessary and the full commissioning flow can happen over NFC.
390-
391-
## BLE Pairing
392-
393-
A specifically crafted NDEF message can be used to facilitate out-of-band pairing wth man-in-the-middle protection as specified in the [Bluetooth® Secure Simple Pairing Using NFC](https://members.nfc-forum.org/apps/group_public/download.php/18688/NFCForum-AD-BTSSP_1_1.pdf) document.
394-
395395
# Testing strategy
396396
## NFC Forum Compliance
397397

0 commit comments

Comments
 (0)