6.1 Amazon Sidewalk BLE requirements
An Endpoint hosting an Amazon Sidewalk mobile application or working as a Gateway shall support the following functionalities:
| Functionality | A device hosting mobile application or a Gateway requirement |
|---|---|
| BLE spec support | Minimum: BLE 4.2 (Not leveraging security features) |
| Number of concurrent connections | Minimum: 4 Preferred: 6 |
| Supported PHY layers | 1.0 Mbps (minimum) 2.0 Mbps |
6.1.1 Endpoint software requirements
| Functionality | Endpoint requirement |
|---|---|
| BLE spec support | Minimum: BLE 4.2 (Not leveraging security features) |
| Profile | ATT (GATT) and GAP |
| Support for peripheral role (and advertiser) | Yes |
| Support for central role (and scanner) | No |
| Number of concurrent connections | N/A - only one connection support |
| Supported PHY layers | 1.0 Mbps (minimum) 2.0 Mbps |
| Support for configurable ATT MTU size | Minimum: 185B Recommended: 512B |
| Support for extended advertising | No |
| Support for data length extension | Yes - 251B |
| Support for L2CAP with LE credit-based flow control mode | No |
| Support for LL privacy | Yes |
| Advertisement Interval | Alternating 160 ms and 30 s and 1 s [+/- 10 ms] for the rest of the time |
| Advertisement delay/window | 0-10 ms |
| Connection Interval | 30 ms - 4 s (based for use case) - enforced by central |
| Peripheral latency | Default 0 |
6.1.2 BLE KPIs
| KPIs | Type | Target | Definition | Notes |
|---|---|---|---|---|
| Concurrent connection | Minimum: 4 Preferred: 6 | Minimum simultaneous connection | KPIs for the Gateway or cellular phone with end user mobile application | |
| Packet latency | Less than 2 s | Latency for beacon detection | Based on scanning interval KPIs for the Gateway or cellular phone with end user mobile application | |
| Latency to connection | Less than 1s | Latency to get connected via central after beacon detection |
6.1.3 Traffic patterns
| Pattern | Occurrence | Description | Size | Comments |
|---|---|---|---|---|
| Advertisement | 160 ms for 30 s, 1 s afterwards | Standard Advertisement packet | 31B | |
| Connection management | Upon each connection establishment | AMA stack handshake messages | Less than 32 Bytes each | The procedure contains two TX and two RX transmissions |
| Authentication | Beacon packet message on BLE connection | Fragmentation dependent. AMA fragmentation size depends on negotiated BLE MTU between central and peripheral | ||
| Time synchronization message | Up to 255 Bytes of BLE payload |