Skip to main content Link Menu Expand (external link) Document Search Copy Copied

LoRa Test Cases

Attribute Value
Case ID C83934651
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Send 1 DL packet from AWS IoT with 1 byte payload EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: 1, LINK: 4, LINK_MODE: <x>, ACK_REQUESTED: <x>, ACK: <x>, DUP: <x>, RSSI: <x>, SNR: <x> Data: <payload> Key check: Delivery ratio 100%
2 Send 1 DL packet from AWS IoT with 10 bytes payload EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: 10, LINK: 4, LINK_MODE: <x>, ACK_REQUESTED: <x>, ACK: <x>, DUP: <x>, RSSI: <x>, SNR: <x> Data: <payload> Key check: Delivery ratio 100%
3 Send 1 DL packet from AWS IoT with 19 bytes payload EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: 19, LINK: 4, LINK_MODE: <x>, ACK_REQUESTED: <x>, ACK: <x>, DUP: <x>, RSSI: <x>, SNR: <x> Data: <payload> Key check: Delivery ratio 100%
Attribute Value
Case ID C83934652
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Send 1 UL packet from EN with 1 byte payload: sid send <1-byte-payload> CMD: ERR: 0 TYPE: 2 ID: <id> EVENT SID SEND STATUS: SID ERR: 0, TYPE: 2, ID: <id>, LINK: 4 LINK_MODE: 0 ADDITIONAL ATTRS: 0 Key check: Packet received on AWS
2 Send 1 UL packet from EN with 10 bytes payload: sid send <10-byte-payload> CMD: ERR: 0 TYPE: 2 ID: <id> EVENT SID SEND STATUS: SID ERR: 0, TYPE: 2, ID: <id>, LINK: 4 LINK_MODE: 0 ADDITIONAL ATTRS: 0 Key check: Packet received on AWS
3 Send 1 UL packet from EN with 19 bytes payload: sid send <19-byte-payload> CMD: ERR: 0 TYPE: 2 ID: <id> EVENT SID SEND STATUS: SID ERR: 0, TYPE: 2, ID: <id>, LINK: 4 LINK_MODE: 0 ADDITIONAL ATTRS: 0 Key check: Packet received on AWS

Test Case ID: LORA/EN/SEC/UUID/BV-01: End Node rotates UUID immediately after time sync

Attribute Value
Case ID C83934653
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Get initial TX UUID: print txid TXID: 0x<uuid> Key check: Note the UUID value
2 Wait for time sync EVENT SID STATUS: State: 0, Reg: 0, Time: 0, Link_Mask: 4 EVENT SID STATUS LINK MODE: LORA: 1, FSK: 0, BLE: 0 Key check: Time: 0 (time synced)
3 Get TX UUID again: print txid TXID: 0x<new_uuid> Key check: UUID is different from Step 1 (rotated after time sync)

Test Case ID: LORA/EN/SEC/UUID/BV-02: UUID rotates every 15 minutes after time sync

Attribute Value
Case ID C83934654
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Get initial TX UUID: print txid TXID: 0x<uuid> Key check: Note the UUID value
2 Monitor UUID rotation for 2 rounds. Check UUID every 30 seconds: print txid Round 1: UUID rotated after ~15 minutes. Round 2: UUID rotated after ~15 minutes. Key check: Each rotation within 14-16 minutes
3 Verify all collected UUIDs are unique All UUIDs are unique. Key check: No duplicate UUID detected

Test Case ID: LORA/EN/SEC/UUID/BV-03: End Node can exchange UL/DL during UUID rotation

Attribute Value
Case ID C83934655
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Get initial TX UUID: print txid TXID: 0x<uuid>
2 Wait for 1st UUID rotation (check every 30s): print txid TXID: 0x<new_uuid> Key check: UUID rotated (1st rotation detected)
3 Wait ~14 minutes, then send UL/DL continuously until 2nd UUID rotation: sid send <5-byte-payload> (UL) and send DL from AWS IoT (DL). After 2nd rotation, send one more UL/DL to confirm. UL: EVENT SID SEND STATUS: SID ERR: 0, TYPE: 2, ID: <id>, LINK: 4 LINK_MODE: 0 DL: EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: 5, LINK: 4, ... 2nd UUID rotation detected. UL/DL still works after rotation. Key check: UL/DL successful before and after UUID rotation

Test Case ID: LORA/EN/CONN/REG/BV-02: End Node can be deregistered from Sidewalk network

Attribute Value
Case ID C83934657
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Run the following command to deregister the device: sid factory_reset CMD: ERR: 0 EVENT SID STATUS: State: 1, Reg: 1, Time: 1, Link_Mask: 0 Key check: Reg: 1 (deregistered)

Test Case ID: LORA/EN/CONN/LP/BV-01: End Node can select Profile A and complete Join procedure

Attribute Value
Case ID C83934658
Executable by Customer Yes
Preconditions
  • sid option -lp_set 128 5
  • sid option -lp_get_l3
Test Steps
Step Description Expected Result
1 Initialize and start LoRa stack with Profile A: sid init 3 sid option -lp_set 128 5 sid start Each command returns: CMD: ERR: 0 EVENT SID STATUS: State: 0, Reg: 0, Time: 0, Link_Mask: 4 EVENT SID STATUS LINK MODE: LORA: 1, FSK: 0, BLE: 0 Njoin(1, 2) st 2->6 Key check: Time: 0 (time synced), join completed

Test Case ID: LORA/EN/CONN/LP/BV-02: End Node can select Profile B and complete Join procedure

Attribute Value
Case ID C83934659
Executable by Customer Yes
Preconditions
  • sid option -lp_set 129 0
  • sid option -lp_get_l3
Test Steps
Step Description Expected Result
1 Initialize and start LoRa stack with Profile B: sid init 3 sid option -lp_set 129 0 sid start Each command returns: CMD: ERR: 0 EVENT SID STATUS: State: 0, Reg: 0, Time: 0, Link_Mask: 4 EVENT SID STATUS LINK MODE: LORA: 1, FSK: 0, BLE: 0 Njoin(1, 2) st 2->6 Key check: Time: 0 (time synced), join completed
Attribute Value
Case ID C83934660
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Send 5 UL packets from EN with 10 byte payload: sid send <10-byte-payload> CMD: ERR: 0 TYPE: 2 ID: <id> EVENT SID SEND STATUS: SID ERR: 0, TYPE: 2, ID: <id>, LINK: 4 LINK_MODE: 0 ADDITIONAL ATTRS: 0 Key check: UL packets received on AWS
Attribute Value
Case ID C83934661
Executable by Customer Yes
Preconditions
  • The seq num field should be properly incremented by one for each subsequent packet sent by DUT within a maximum of 15 minutes from the previous UUID change, then a new sequence number should be generated in the range between 0 and 16383.
Test Steps
Step Description Expected Result
1 Send 1 UL packet: sid send TEST LoraTx:EnqPkt sqn:<seq> src_frmt:1 src_id:0x<txid> dst_frmt:0 dst_id:0x<gw_id> msg_id:<id> Key check: Note the SEQ number
2 Wait for UUID rotation (~15 minutes after time sync) UUID rotated (TX UUID changes)
3 Send 1 UL packet after UUID rotation: sid send TEST LoraTx:EnqPkt sqn:<new_seq> src_frmt:1 src_id:0x<new_txid> dst_frmt:0 dst_id:0x<gw_id> msg_id:<id> Key check: New SEQ number is different from Step 1 (reset after UUID change)
Attribute Value
Case ID C83934662
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Send 3 DL packets from AWS IoT with SEQ: 1, 2, 3 All 3 DL packets received and accepted by EN: EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: <len>, LINK: 4, ... Key check: Delivery ratio 100%
2 Send 3 DL packets from AWS IoT with SEQ: 6, 5, 4 All 3 DL packets received and accepted by EN: EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: <len>, LINK: 4, ... Key check: Delivery ratio 100%
Attribute Value
Case ID C83934663
Executable by Customer Yes
Preconditions
  • EN MCU <= 1.13
Test Steps
Step Description Expected Result
1 Send DL with SEQ=1, then send DL with SEQ=1 again (duplicate) First: EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: <len>, LINK: 4, ... (accepted). Second: No EVENT SID RECEIVED within 20 seconds (duplicate rejected). Key check: Duplicate rejected
2 Send DL with SEQ=2, then send DL with SEQ=2 again (duplicate) First: EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: <len>, LINK: 4, ... (accepted). Second: No EVENT SID RECEIVED within 20 seconds (duplicate rejected). Key check: Duplicate rejected
Attribute Value
Case ID C83934664
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Send 5 DL packets with SEQ: 1, 2, 3, 4, 5 EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: <len>, LINK: 4, ... Key check: All 5 packets received
2 Send 5 DL packets with SEQ: 1, 2, 3, 4, 5 again (all duplicates) No EVENT SID RECEIVED for any packet. Key check: All duplicates rejected

Test Case ID: LORA/EN/CONN/SEQ/BV-07: SEQ number can be accepted again after getting 10 other messages

Attribute Value
Case ID C83934665
Executable by Customer Yes
Preconditions
  • EN MCU <= 1.13
  • Seq=1,2,3,4,5,6,7,8,9,10,11,1
Test Steps
Step Description Expected Result
1 Send 10 DL packets from AWS IoT with SEQ: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 All 10 DL packets received and accepted by EN. Delivery ratio 100%
2 Send 1 DL packet with SEQ=1 (duplicate) No EVENT SID RECEIVED within 20 seconds. Key check: Delivery ratio 0%
3 Send 1 DL packet with SEQ=11 (new, non-duplicate) EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: <len>, LINK: 4, ... Key check: Delivery ratio 100%
4 Send 1 DL packet with SEQ=1 again (now outside the 10-SEQ window) EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: <len>, LINK: 4, ... Key check: SEQ=1 accepted again after 10 other messages

Test Case ID: LORA/EN/CONN/SEQ/BV-08: SEQ number can be accepted again after End Node reinitialization

Attribute Value
Case ID C83934666
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Send DL packet with SEQ=1 EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: <len>, LINK: 4, ... Key check: Packet accepted
2 Send DL packet with SEQ=1 again (duplicate) No EVENT SID RECEIVED within 20 seconds. Key check: Duplicate rejected
3 Reinitialize Sidewalk stack: sid stop sid deinit sid init 3 sid start Each command returns: CMD: ERR: 0 Wait for time sync: EVENT SID STATUS: State: 0, Reg: 0, Time: 0, Link_Mask: 4 Wait for join: Nsync st ->2
4 Send DL packet with SEQ=1 again (after reinit) EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: <len>, LINK: 4, ... Key check: SEQ=1 accepted again after reinit

Test Case ID: LORA/EN/CONN/SEQ/BV-09: End Node drops the packet with SEQ which is out of range

Attribute Value
Case ID C83934667
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Send DL packet with SEQ=0 (minimum valid) EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: <len>, LINK: 4, ... Key check: Accepted
2 Send DL packet with SEQ=16383 (maximum valid) EVENT SID RECEIVED: TYPE: <type>, ID: <id>, LEN: <len>, LINK: 4, ... Key check: Accepted
3 Send DL packet with SEQ=-1 (out of range) No EVENT SID RECEIVED within 20 seconds. Key check: Rejected (out of range)
4 Send DL packet with SEQ=16384 (out of range) No EVENT SID RECEIVED within 20 seconds. Key check: Rejected (out of range)

Test Case ID: LORA/EN/NW-SYNC/JOIN/BV-02: End Node keeps synchronization with the network by periodic transmission of Join request

Attribute Value
Case ID C83934668
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Initialize and start LoRa stack: sid init 3 sid start Wait for time sync and join Each command returns: CMD: ERR: 0 EVENT SID STATUS: State: 0, Reg: 0, Time: 0, Link_Mask: 4 Njoin(1, 2) st 2->6 Key check: Time synced and joined
2 Wait 14 minutes after time sync. Do not send any UL. No UL packets sent during this period
3 Wait for join response Njoin(1, 2) st 2->6 Key check: Join response received (periodic join request)

Test Case ID: LORA/EN/NW-SYNC/JOIN/BV-03: End Node keeps synchronization with the network by embedded sync request

Attribute Value
Case ID C83934669
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 EN time-sync and joined EN is time-synced and joined to the network
2 Wait 150 seconds, EN send a UL packet EN receives NTFY_JOIN_REQ
3 Wait 170 seconds EN does not send SET_JOIN_REQ in this period

Test Case ID: LORA/EN/NW-SYNC/TIME/BV-01: End Node completes the initial time sync procedure

Attribute Value
Case ID C83934670
Executable by Customer Yes
Test Steps
Step Description Expected Result
1 Reboot EN, then initialize and start LoRa stack: reboot sid init 3 sid start Wait for time sync Each command returns: CMD: ERR: 0 EVENT SID STATUS: State: 0, Reg: 0, Time: 0, Link_Mask: 4 EVENT SID STATUS LINK MODE: LORA: 1, FSK: 0, BLE: 0 Key check: Time: 0 (time synced)

Back to top

©2023 Amazon.com, Inc. or its affiliates (collectively, “Amazon”). All Rights Reserved.