17. Appendix
17.1 PICS
A Protocol Implementation Conformance Statement (PICS) is required for every Sidewalk-enabled device, where the developer must confirm that their device implementation meets all requirements outlined in the Amazon Sidewalk protocol specification. The PICS serves as the developer’s attestation that is submitted along with a request for their Sidewalk product qualification review and approval.
17.2 Reference Table
Table 17.1 PICS Reference Table
| ID | Group | Implementation Name | Implementation Case | Test Required (Y)=YES / (C)=Conditional |
|---|---|---|---|---|
| Basic Conformance | Basic conformance is mandatory. The items shall be implemented for the selected operation band(s). | Mandatory | ||
| 1 | SID_VERSION | Amazon Sidewalk Compatible MCU | DUT is flashed with a valid MCU build for Amazon Sidewalk. | (Y) |
| 2 | BAND | Operation Band | DUT with BLE compatibility operates in the 2.4GHz ISM band in US, compliant with FCC ITU Region 2. | (Y) |
| 2.1 | BAND | Operation Band | DUT with Sub-1GHz compatibility operates in the sub-1GHz ISM band in US, compliant with FCC ITU Region 2. | (Y) |
| Protocol Implementation Conformance | Protocol conformance is mandatory. DUT can have selectable implementations for BLE, SubG-FSK, and SubG-CSS. The items shall be implemented for each chosen protocol. | Mandatory | ||
| 3 | BLE Protocol | BLE Link Type | DUT with BLE compatibility connects to the Amazon Sidewalk network using BLE version 4.2 (minimum), 1Mbps data rate. | (Y) |
| 3.1 | BLE Protocol | Device Connection - REG | DUT successfully completes Sidewalk device registration over BLE. | (Y) |
| 3.2 | BLE Protocol | Device Connection - REG | DUT successfully completes Sidewalk device registration with use of FFN. | (Y) |
| 3.3 | BLE Protocol | Device Connection - REG | DUT can be deregistered from Sidewalk network. | (Y) |
| 3.4 | BLE Protocol | Device Data - DL | DUT receives downlink packets with various sizes of Command data. | (Y) |
| 3.5 | BLE Protocol | Device Data - UL | Gateway receives uplink packets with various sizes of Command data from DUT. | (Y) |
| 3.6 | BLE Protocol | Device Connection - EST | Gateway establishes BLE connection on DUT’s request. | (Y) |
| 3.7 | BLE Protocol | Device Connection - EST | DUT can connect with Gateway via BLE, after reinitializing Sidewalk library. | (Y) |
| 3.8 | BLE Protocol | Device Connection - EST | DUT can connect with Gateway via BLE, after restarting Sidewalk library. | (Y) |
| 3.9 | BLE Protocol | Device Connection - DSC | BLE connection between Gateway and DUT is dropped after 30 seconds of being idle. | (Y) |
| 3.10 | BLE Protocol | Device Connection - DSC | BLE connection between Gateway and DUT is extended by uplink packet and dropped after additional 30 seconds. | (Y) |
| 3.11 | BLE Protocol | Device Connection - DSC | BLE connection between Gateway and DUT is extended by downlink packet and dropped after additional 30 seconds. | (Y) |
| 3.12 | BLE Protocol | Device Connection - DSC | DUT drops BLE connection in case of received downlink packet with duplicated SEQ. | (Y) |
| 3.13 | BLE Protocol | Device Connection - DSC | DUT drops BLE connection in case of received downlink packets with duplicated SEQ range. | (Y) |
| 3.14 | BLE Protocol | Device Connection - DSC | DUT drops BLE connection after stopping Sidewalk library. | (Y) |
| 3.15 | BLE Protocol | Device Connection - DSC | DUT drops BLE connection after de-initializing Sidewalk library. | (Y) |
| 3.16 | BLE Protocol | Device Connection - BCN | DUT transmits beacons only when BLE connection is not established. | (Y) |
| 3.17 | BLE Protocol | Device Connection - BCN | DUT transmits beacons that contain Identifier (TX-ID), which changes every 15 minutes. | (Y) |
| 3.18 | BLE Protocol | Device Connection - BCN | DUT transmits beacons with 160ms interval for the first 30 seconds after starting BLE protocol. | (Y) |
| 3.19 | BLE Protocol | Device Connection - BCN | DUT transmits beacons with 1s interval, 30 seconds after starting BLE protocol. | (Y) |
| 3.20 | BLE Protocol | Device Connection - BCN | DUT transmits beacons with valid header. | (Y) |
| 3.21 | BLE Protocol | Device Connection - DUP | BLE connection is closed after DUT receives 10 packets with duplicate SEQ number within one minute (filter duplicates enabled). | (Y) |
| 3.22 | BLE Protocol | Device Connection - DUP | BLE connection is closed after DUT receives 10 packets with various duplicate SEQ numbers within one minute (filter duplicates enabled). | (Y) |
| 3.23 | BLE Protocol | Device Connection - DUP | BLE connection is not closed after DUT receives 10 packets with duplicate SEQ number within one minute (filter duplicates disabled). | (Y) |
| 3.24 | BLE Protocol | Device Connection - DUP | BLE connection is not closed after DUT receives 10 packets with various duplicate SEQ numbers within one minute (filter duplicates disabled). | (Y) |
| 3.25 | BLE Protocol | Device Connection - DUP | BLE connection is not closed after 10 packets with duplicate SEQ number reach DUT, if not all of those packets are sent within one minute. | (Y) |
| 3.26 | BLE Protocol | Network Sync - Time | DUT completes the initial time sync procedure. | (Y) |
| 4 | SubG-FSK Protocol | SubG-FSK Link Type | DUT with SubG-FSK compatibility connects to the Amazon Sidewalk network using Sidewalk GFSK 50 kbps raw data rate. | (Y) |
| 4.1 | SubG-FSK Protocol | Beacon Discovery | FSK-WAN DUT discovers neighbor Gateway and synchronizes with it if roaming is allowed. | (Y) |
| 4.2 | SubG-FSK Protocol | Beacon Discovery | FSK-WAN DUT discovers home Gateway and synchronizes with it even if roaming is forbidden. | (Y) |
| 4.3 | SubG-FSK Protocol | Beacon Discovery | FSK-WAN DUT detects a neighbor Gateway Beacon but continues with the Gateway discovery process if roaming is forbidden. | (Y) |
| 4.4 | SubG-FSK Protocol | Device Connection - REG | DUT successfully completes Sidewalk device registration over BLE. | (Y) |
| 4.5 | SubG-FSK Protocol | Device Connection - REG | DUT can be deregistered from Sidewalk network. | (Y) |
| 4.6 | SubG-FSK Protocol | Device Connection - REG | DUT successfully completes Sidewalk device registration with the use of FFN. | (Y) |
| 4.7 | SubG-FSK Protocol | Device Connection - SEQ | Uplink packets contain SEQ number. | (Y) |
| 4.8 | SubG-FSK Protocol | Device Connection - SEQ | DUT increments uplink SEQ number until UUID changes. | (Y) |
| 4.9 | SubG-FSK Protocol | Device Connection - SEQ | DUT accepts and decodes downlink packets with increased and decreased SEQ. | (Y) |
| 4.10 | SubG-FSK Protocol | Device Connection - SEQ | DUT rejects downlink packet with duplicated SEQ. | (Y) |
| 4.11 | SubG-FSK Protocol | Device Connection - SEQ | DUT rejects downlink packet with duplicated SEQ range. | (Y) |
| 4.12 | SubG-FSK Protocol | Device Connection - SEQ | SEQ number can be accepted again after getting 10 other messages. | (Y) |
| 4.13 | SubG-FSK Protocol | Device Connection - SEQ | SEQ number can be accepted again after Sidewalk stack reinitialization. | (Y) |
| 4.14 | SubG-FSK Protocol | Device Connection - SEQ | DUT drops the packet with SEQ which is out of range. | (Y) |
| 4.15 | SubG-FSK Protocol | Device Data - DL | DUT receives downlink packets with various sizes of Command data. | (Y) |
| 4.16 | SubG-FSK Protocol | Device Data - UL | Gateway receives uplink packets with various sizes of Command data from DUT. | (Y) |
| 4.17 | SubG-FSK Protocol | Network Sync - Time | DUT completes the initial time sync procedure. | (Y) |
| 4.18 | SubG-FSK Protocol | Network Sync - JOIN | DUT completes the initial Join procedure. | (Y) |
| 4.19 | SubG-FSK Protocol | Network Sync - JOIN | DUT keeps synchronization with the network by periodic transmission of Join request. | (Y) |
| 4.20 | SubG-FSK Protocol | Network Sync - JOIN | DUT keeps synchronization with the network by embedded sync request. | (Y) |
| 4.21 | SubG-FSK Protocol | Device Security - UUID | DUT rotates UUID immediately after time sync. | (Y) |
| 4.22 | SubG-FSK Protocol | Device Security - UUID | UUID rotates every 15 minutes after time sync. | (Y) |
| 4.23 | SubG-FSK Protocol | Device Security - UUID | DUT can exchange UL/DL during UUID rotation. | (Y) |
| 5 | SubG-CSS Protocol | SubG-CSS Link Type | DUT with SubG-CSS compatibility connects to the Amazon Sidewalk network using LoRa CSS raw bit rate 2 kbps @ BW 500 kHz, SF11. SubG-CSS must exist with either BLE or SubG-FSK implementation. | (Y) |
| 5.1 | SubG-CSS Protocol | Device Data - DL | DUT receives downlink packets with various sizes of Command data. | (Y) |
| 5.2 | SubG-CSS Protocol | Device Data - UL | Gateway receives uplink packets with various Command data sizes from DUT. | (Y) |
| 5.3 | SubG-CSS Protocol | Device Security - UUID | DUT rotates UUID immediately after time sync. | (Y) |
| 5.4 | SubG-CSS Protocol | Device Security - UUID | UUID rotates every 15 minutes after time sync. | (Y) |
| 5.5 | SubG-CSS Protocol | Device Security - UUID | DUT can exchange UL/DL during UUID rotation. | (Y) |
| 5.6 | SubG-CSS Protocol | Device Connection - REG | DUT successfully completes Sidewalk device registration over BLE. | (Y) |
| 5.7 | SubG-CSS Protocol | Device Connection - REG | DUT can be deregistered from Sidewalk network. | (Y) |
| 5.8 | SubG-CSS Protocol | Device Connection - LP | DUT can select Profile A and complete the Join procedure. | (Y) |
| 5.9 | SubG-CSS Protocol | Device Connection - LP | DUT can select Profile B and complete the Join procedure. | (Y) |
| 5.10 | SubG-CSS Protocol | Device Connection - SEQ | Uplink packets contain SEQ number. | (Y) |
| 5.11 | SubG-CSS Protocol | Device Connection - SEQ | DUT increments uplink SEQ number until UUID changes. | (Y) |
| 5.12 | SubG-CSS Protocol | Device Connection - SEQ | DUT accepts and decodes downlink packets with increased and decreased SEQ. | (Y) |
| 5.13 | SubG-CSS Protocol | Device Connection - SEQ | DUT rejects downlink packet with duplicated SEQ. | (Y) |
| 5.14 | SubG-CSS Protocol | Device Connection - SEQ | DUT rejects downlink packet with duplicated SEQ range. | (Y) |
| 5.15 | SubG-CSS Protocol | Device Connection - SEQ | SEQ number can be accepted again after getting 10 other messages. | (Y) |
| 5.16 | SubG-CSS Protocol | Device Connection - SEQ | SEQ number can be accepted again after Sidewalk stack reinitialization. | (Y) |
| 5.17 | SubG-CSS Protocol | Device Connection - SEQ | DUT drops the packet with SEQ which is out of range. | (Y) |
| 5.18 | SubG-CSS Protocol | Network Sync - JOIN | DUT keeps synchronization with the network by periodic transmission of Join request. | (Y) |
| 5.19 | SubG-CSS Protocol | Network Sync - JOIN | DUT keeps synchronization with the network by embedded sync request. | (Y) |
| 5.20 | SubG-CSS Protocol | Network Sync - TIME | DUT completes the initial time sync procedure. | (Y) |
| 6 | SubG-CSS Protocol | Multi-Radio | DUT’s SubG-CSS exists with BLE implementation. | Y (conditional) |
| 6.1 | SubG-CSS Protocol | Multi-Radio - API INIT | DUT switches between 900MHz and BLE stack multiple times. | Y |
| 6.2 | SubG-CSS Protocol | Multi-Radio Connection - DL | DUT is able to receive a downlink packet using BLE. | Y |
| 6.3 | SubG-CSS Protocol | Multi-Radio Connection - DL | DUT is able to receive a downlink packet using LoRa. | Y |
| 6.4 | SubG-CSS Protocol | Multi-Radio Connection - DL | DUT is able to receive a downlink packet using LoRa, while BLE connection with Gateway is established. | Y |
| 6.5 | SubG-CSS Protocol | Multi-Radio Connection - Send LINK | Uplink performed through BLE, when send link 0 and active BT connection. | Y |
| 6.6 | SubG-CSS Protocol | Multi-Radio Connection - Send LINK | Uplink performed through BLE, when send link 1 and active BT connection. | Y |
| 6.7 | SubG-CSS Protocol | Multi-Radio Connection - Send LINK | Uplink performed through LoRa, when send link 3 and active BT connection. | Y |
| 6.8 | SubG-CSS Protocol | Multi-Radio Connection - Send LINK | Uplink performed through LoRa, when send link 0 and terminated BT connection. | Y |
| 6.9 | SubG-CSS Protocol | Multi-Radio Connection - Send LINK | Uplink not performed, when send link 1 and terminated BT connection. | Y |
| Functionality Implementation Conformance | Functionality conformance is optional. The implementation may choose to implement the items. | Optional | ||
| 7 | MLM | Multi-Link Connection | DUT enables any combination of BLE, and/or SubG-FSK, and/or SubG-CSS link type for Amazon Sidewalk network connection. | Y (conditional) |
| 8 | SBDT | File Transfer | DUT receives a file transfer via Sidewalk BLE. | Y (conditional) |
| 9 | EPMETRICS | Endpoint Metrics | DUT has the capability to collect and upload endpoint metrics. | Y (conditional) |
| 10 | CAPABILITY | Endpoint Capability | Capability of DUT can be uploaded and configured. | Y (conditional) |
| 11 | BLE BEACON | MAC Address | DUT MAC address rotation under specific conditions | Y (conditional) |
| 12 | Location Service | Location Service Uplink | DUT sends location data (GNSS, Wi-Fi, Gateway) to Cloud for device positioning. | Y (conditional) |
| 13 | Location Service | Location Service MCU | DUT location can be resolved and sent | Y (conditional) |
| 14 | POWER | Power Optimization | DUT can adjust RX window opening time | Y (conditional) |
| 15 | CONNECTION POLICY | BLE connection policy | BLE connection policy and parameters can be configured on DUT | Y (conditional) |
| 7.1 | MLM | Multi-Link Auto Connection - BLE | DUT sends UL without auto-connect, DUT is BLE disconnected (Link Mask 0) | C |
| 7.2 | MLM | Multi-Link Auto Connection - BLE | DUT sends UL with auto-connect, ack is true, retry is 3, TTL is 60 | C |
| 7.3 | MLM | Multi-Link Auto Connection - SubG-FSK | DUT sends UL without auto-connect, DUT is FSK disconnected (Link Mask 0) | C |
| 7.4 | MLM | Multi-Link Auto Connection - SubG-FSK | DUT sends UL with auto-connect, ack is true, retry is 3, TTL is 60 | C |
| 7.5 | MLM | Multi-Link Auto Connection - SubG-CSS | DUT sends UL without auto-connect, DUT is LoRa disconnected (Link Mask 0) | C |
| 7.6 | MLM | Multi-Link Auto Connection - SubG-CSS | DUT sends UL with auto-connect, ack is true, retry is 3, TTL is 60 | C |
| 7.7 | MLM | Multi-Link Auto Connection - BLE SubG-CSS | DUT sends UL with auto-connect when BLE link priority is higher than LoRa, EN Link Mask is 0, Specify BLE+LoRa link | C |
| 7.8 | MLM | Multi-Link Auto Connection - BLE SubG-CSS | DUT sends UL with auto-connect when BLE link priority is higher than LoRa, EN Link Mask is 0, Specify BLE+LoRa link, disable BLE on GW | C |
| 7.9 | MLM | Multi-Link Auto Connection - BLE SubG-CSS | DUT sends UL with auto-connect when BLE link priority is higher than LoRa, EN Link Mask is 0, disables BLE & LoRa on GW | C |
| 7.10 | MLM | Multi-Link Auto Connection - BLE SubG-CSS | DUT sends UL with auto-connect when BLE link priority is higher than LoRa, EN Link Mask is 0, Specify FSK link | C |
| 7.11 | MLM | Multi-Link Auto Connection - BLE SubG-FSK CSS | DUT sends UL through BLE when no connection | C |
| 7.12 | MLM | Multi-Link Auto Connection - BLE SubG-FSK CSS | DUT sends UL through FSK when no connection | C |
| 7.13 | MLM | Multi-Link Auto Connection - BLE SubG-FSK CSS | DUT sends UL through LoRa when no connection | C |
| 7.14 | MLM | Multi-Link Auto Connection - BLE SubG-FSK CSS | DUT doesn’t send UL when no connection and BLE/FSK/LoRa unavailable | C |
| 7.15 | MLM | Multi-Link Auto Connection - BLE SubG-FSK CSS | DUT sends UL through BLE when Link Mask is 1 | C |
| 7.16 | MLM | Multi-Link Active | DUT sends UL through BLE when no connection | C |
| 7.17 | MLM | Multi-Link Active | DUT sends UL through FSK when no connection | C |
| 7.18 | MLM | Multi-Link Active | DUT sends UL through LoRa when no connection | C |
| 7.19 | MLM | Multi-Link Active | DUT doesn’t send UL when no connection and BLE/FSK/LoRa unavailable | C |
| 7.20 | MLM | Multi-Link Active | DUT sends UL through BLE when Link Mask is 1 | C |
| 7.21 | MLM | Multi-Link Power | DUT sends UL through BLE when no connection | C |
| 7.22 | MLM | Multi-Link Power | DUT sends UL through FSK when no connection | C |
| 7.23 | MLM | Multi-Link Power | DUT sends UL through LoRa when no connection | C |
| 7.24 | MLM | Multi-Link Power | DUT doesn’t send UL when no connection and BLE/FSK/LoRa unavailable | C |
| 7.25 | MLM | Multi-Link Power | DUT sends UL through BLE when Link Mask is 1 | C |
| 7.26 | MLM | Multi-Link Performance | DUT sends UL through BLE when no connection | C |
| 7.27 | MLM | Multi-Link Performance | DUT sends UL through FSK when no connection | C |
| 7.28 | MLM | Multi-Link Performance | DUT sends UL through LoRa when no connection | C |
| 7.29 | MLM | Multi-Link Performance | DUT doesn’t send UL when no connection and BLE/FSK/LoRa unavailable | C |
| 7.30 | MLM | Multi-Link Performance | DUT sends UL through BLE when Link Mask is 1 | C |
| 7.31 | MLM | Multi-Link Latency | DUT sends UL through BLE when no connection | C |
| 7.32 | MLM | Multi-Link Latency | DUT sends UL through FSK when no connection | C |
| 7.33 | MLM | Multi-Link Latency | DUT sends UL through LoRa when no connection | C |
| 7.34 | MLM | Multi-Link Latency | DUT doesn’t send UL when no connection and BLE/FSK/LoRa unavailable | C |
| 7.35 | MLM | Multi-Link Latency | DUT sends UL through BLE when Link Mask is 1 | C |
| 7.36 | MLM | Multi-Link Reliability | DUT sends UL through BLE when no connection | C |
| 7.37 | MLM | Multi-Link Reliability | DUT sends UL through FSK when no connection | C |
| 7.38 | MLM | Multi-Link Reliability | DUT sends UL through LoRa when no connection | C |
| 7.39 | MLM | Multi-Link Reliability | DUT doesn’t send UL when no connection and BLE/FSK/LoRa unavailable | C |
| 7.40 | MLM | Multi-Link Reliability | DUT sends UL through BLE when Link Mask is 1 | C |
| 8.1 | SBDT | File Transfer | DUT initializes the feature and starts receiving a file | Y |
| 8.2 | SBDT | File Transfer | DUT cancels ongoing transfer | Y |
| 8.3 | SBDT | File Transfer | DUT prints the progress of the transfer and current file offset | Y |
| 8.4 | SBDT | File Transfer | DUT prints various parameters of the transfer | Y |
| 8.5 | SBDT | File Transfer Recovery | DUT recovers transfer after powered off and back on | Y |
| 8.6 | SBDT | File Transfer Recovery | DUT recovers transfer after being out of range from GW | Y |
| 8.7 | SBDT | File Transfer Recovery | DUT recovers transfer after GW that was using to send packets switched to another GW | Y |
| 8.8 | SBDT | File Transfer Recovery | DUT recovers transfer after GW that was using to send packets being opt-out | Y |
| 8.9 | SBDT | File Transfer Recovery | DUT recovers transfer after GW that was using to send packets powered off for a while and back on | Y |
| 9.1 | EPMETRICS | Endpoint Metrics - Common | DUT has corresponding metrics but not invalid metrics enabled | Y |
| 9.2 | EPMETRICS | Endpoint Metrics - BLE Report | DUT sends endpoint metrics to Cloud over BLE in a specific time interval | Y |
| 9.3 | EPMETRICS | Endpoint Metrics - BLE Report | DUT sends remaining endpoint metrics to Cloud over BLE via piggybacking on a periodic reporting | Y |
| 9.4 | EPMETRICS | Endpoint Metrics - BLE Report | DUT sends endpoint metrics via piggybacking over BLE if the explicit reporting is disabled | Y |
| 9.5 | EPMETRICS | Endpoint Metrics - BLE Uplink | DUT collects BLE uplink messages metrics | Y |
| 9.6 | EPMETRICS | Endpoint Metrics - BLE Downlink | DUT collects BLE downlink messages metrics | Y |
| 9.7 | EPMETRICS | Endpoint Metrics - BLE Connection | DUT collects BLE connection attempts metrics | Y |
| 9.8 | EPMETRICS | Endpoint Metrics - FSK Report | DUT sends endpoint metrics to Cloud over FSK in a specific time interval | Y |
| 9.9 | EPMETRICS | Endpoint Metrics - FSK Report | DUT sends remaining endpoint metrics to Cloud over FSK via piggybacking on a periodic reporting | Y |
| 9.10 | EPMETRICS | Endpoint Metrics - FSK Report | DUT sends endpoint metrics via piggybacking over FSK if the explicit reporting is disabled | Y |
| 9.11 | EPMETRICS | Endpoint Metrics - FSK Uplink | DUT collects FSK uplink messages metrics and total number of tx unique packets Metrics | Y |
| 9.12 | EPMETRICS | Endpoint Metrics - FSK Downlink | DUT collects FSK downlink messages metrics and total number of rx packets metrics | Y |
| 9.13 | EPMETRICS | Endpoint Metrics - LoRa Report | DUT sends endpoint metrics to Cloud over LoRa in a specific time interval | Y |
| 9.14 | EPMETRICS | Endpoint Metrics - LoRa Report | DUT sends remaining endpoint metrics to Cloud over LoRa via piggybacking on a periodic reporting | Y |
| 9.15 | EPMETRICS | Endpoint Metrics - LoRa Report | DUT sends endpoint metrics via piggybacking over LoRa if the explicit reporting is disabled | Y |
| 9.16 | EPMETRICS | Endpoint Metrics - LoRa Uplink | DUT collects LoRa uplink messages metrics and total number of tx normal packets metrics | Y |
| 9.17 | EPMETRICS | Endpoint Metrics - LoRa Downlink | DUT collects LoRa downlink messages metrics and total number of rx packets metrics | Y |
| 10.1 | CAPABILITY | Endpoint Capability - Common Report | DUT does not have the capability report saved, schedule an event to report the capability | Y |
| 10.2 | CAPABILITY | Endpoint Capability - Common Report | DUT have the capability report saved and match, should not schedule an event to report | Y |
| 10.3 | CAPABILITY | Endpoint Capability - Common Report | DUT default capability report | Y |
| 10.4 | CAPABILITY | Endpoint Capability - Common Uplink | DUT schedule an event, before EP capability report ACK receive, can send messages | Y |
| 10.5 | CAPABILITY | Endpoint Capability - Common Request | Send request to get DUT capabilities | Y |
| 10.6 | CAPABILITY | Endpoint Capability - Common Configure | DUT configure should be updated after setting | Y |
| 10.7 | CAPABILITY | Endpoint Capability - Common Register | DUT capability return to default after re-register | Y |
| 10.8 | CAPABILITY | Endpoint Capability - Common Threshold | DUT traffic threshold renew mechanism | Y |
| 10.9 | CAPABILITY | Endpoint Capability - Common Periodicity | DUT set metrics periodicity | Y |
| 10.10 | CAPABILITY | Endpoint Capability - Common Periodicity | DUT set metrics periodicity when link metrics is disabled | Y |
| 10.11 | CAPABILITY | Endpoint Capability - BLE Threshold | Traffic threshold for BLE stack | Y |
| 10.12 | CAPABILITY | Endpoint Capability - FSK Threshold | Traffic threshold for FSK stack | Y |
| 10.13 | CAPABILITY | Endpoint Capability - LoRa Threshold | Traffic threshold for LoRa stack | Y |
| 11.1 | BLE BEACON | MAC Address | DUT BLE MAC address should rotate after registration | Y |
| 11.2 | BLE BEACON | MAC Address | DUT BLE MAC address should rotate after time sync | Y |
| 11.3 | BLE BEACON | MAC Address | DUT BLE MAC address should rotate after time sync every 15 minutes together with UUID | Y |
| 11.4 | BLE BEACON | MAC Address | DUT BLE MAC address should rotate after connection request sent from EN to cloud | Y |
| 11.5 | BLE BEACON | MAC Address | DUT BLE MAC address should rotate after connection released | Y |
| 11.6 | BLE BEACON | MAC Address | DUT BLE MAC address should rotate after receiving a DL | Y |
| 11.7 | BLE BEACON | MAC Address | DUT BLE MAC address should rotate after key refresh | Y |
| 11.8 | BLE BEACON | MAC Address | DUT BLE MAC address should rotate every 15 minutes even during long live connection | Y |
| 12.1 | Location Service | Location Service Uplink - BLE | Resolve EN location for BLE uplink message containing GNSS scan information | Y |
| 12.2 | Location Service | Location Service Uplink - BLE | Resolve EN location for BLE uplink message containing Wi-Fi scan information | Y |
| 12.3 | Location Service | Location Service Uplink - BLE | Resolve EN location for BLE uplink message with connected GW location | Y |
| 12.4 | Location Service | Location Service Uplink - LoRa | Resolve EN location for LoRa uplink message containing GNSS scan information | Y |
| 12.5 | Location Service | Location Service Uplink - LoRa | Resolve EN location for LoRa uplink message containing Wi-Fi scan information | Y |
| 13.1 | Location Service | Location Service MCU | DUT send a location uplink at level 1 | Y |
| 13.2 | Location Service | Location Service MCU | DUT send a location uplink at level 1 via piggybacking | Y |
| 13.3 | Location Service | Location Service MCU | DUT send a location uplink at level 3 | Y |
| 13.4 | Location Service | Location Service MCU | DUT scan location at level 3 | Y |
| 13.5 | Location Service | Location Service MCU | DUT send a location uplink at level 4 | Y |
| 13.6 | Location Service | Location Service MCU | DUT scan location at level 4 | Y |
| 13.7 | Location Service | Location Service MCU | DUT re-transmit all missed fragments for Wi-Fi on LoRa | Y |
| 13.8 | Location Service | Location Service MCU | DUT re-transmit all missed fragments for GNSS on LoRa | Y |
| 13.9 | Location Service | Location Service MCU | DUT switch location resolution from level 1 to level 3 automatically | Y |
| 13.10 | Location Service | Location Service MCU | DUT switch location resolution from level 1 to level 4 automatically | Y |
| 14.1 | POWER | Power Optimization | DUT FSK RX duration can be adjusted | Y |
| 14.2 | POWER | Power Optimization | DUT FSK RX windows after control message sent should not be closed | Y |
| 14.3 | POWER | Power Optimization | DUT FSK RX window termination request stop RX window opened at profile 2 | Y |
| 14.4 | POWER | Power Optimization | DUT FSK RX window termination request should not stop RX window opened at profile 1 | Y |
| 14.5 | POWER | Power Optimization | DUT FSK beacon interval can be adjusted | Y |
| 14.6 | POWER | Power Optimization | DUT FSK beacon interval revert to default after 2nd beacon misses | Y |
| 14.7 | POWER | Power Optimization | DUT FSK can still perform uplinks and downlinks normally after a beacon skipped | Y |
| 14.8 | POWER | Power Optimization | DUT LORA number of RX windows is limited and can be changed | Y |
| 14.9 | POWER | Power Optimization | DUT LORA number of RX windows is reset after sending an additional uplink | Y |
| 14.10 | POWER | Power Optimization | DUT LORA RX window termination request stop RX window opened at profile A | Y |
| 14.11 | POWER | Power Optimization | DUT LORA RX window termination request should not stop RX window opened at profile B | Y |
| 14.1 | Connection Policy | BLE Connection Policy | Advertisement parameters and advertising intervals on default connection policy | Y |
| 14.2 | Connection Policy | BLE Connection Policy | Connection parameters on default connection policy | Y |
| 14.3 | Connection Policy | BLE Connection Policy | Both advertisement and connection parameters, advertising interval of BLE beacons on default connection policy | Y |
| 14.4 | Connection Policy | BLE Connection Policy | Both default advertisement and connection parameters, advertising interval of BLE beacons | Y |
| 14.5 | Connection Policy | BLE Connection Policy | DUT disconnects after inactivity timeout on default connection policy | Y |
| 14.6 | Connection Policy | BLE Connection Policy | Advertisement parameters and advertising intervals on long lived connection policy | Y |
| 14.7 | Connection Policy | BLE Connection Policy | DUT connection parameters on long lived connection policy | Y |
| 14.8 | Connection Policy | BLE Connection Policy | Both advertisement and connection parameters, advertising interval of BLE beacons on long lived connection policy | Y |
| 14.9 | Connection Policy | BLE Connection Policy | DUT disconnects after inactivity timeout on long lived connection policy | Y |
| 14.10 | Connection Policy | BLE Connection Policy | Advertisement parameters and advertising intervals on optimal advertising connection policy | Y |
| 14.11 | Connection Policy | BLE Connection Policy | Connection parameters on optimal advertising connection policy | Y |
| 14.12 | Connection Policy | BLE Connection Policy | Both advertisement and connection parameters, advertising interval of BLE beacons on optimal advertising connection policy | Y |
| 14.13 | Connection Policy | BLE Connection Policy | DUT disconnects after inactivity timeout on optimal advertising connection policy | Y |