B Regional Parameters
Appendix B
B.1 Parameters for SubG-FSK connection mode with 50 kbps data rate
Parameters introduced in 5.2.
| Name | Value | Description |
|---|---|---|
slot_int | 63 ms | The time interval between two subsequent Target Transmission Times. |
bcn_interval | 10080 ms | The time interval between start of the transmission of two subsequent beacons. |
nb_slot | 160 | The number of Target Transmission Times (counted from 0 to 159). The number of Target Transmission Times is equal to the number of slots. |
ul_dl_nb_slot | 156 | The number of Target Transmission Times that may be used for uplink and downlink scheduling.ul_dl_nb_slot = nb_slot - 4The number of Target Transmission Times that are reserved for the Beacon broadcasting is equal to 4 (slot number 159, 0, 1, 2). These cannot be used for Endpoint uplink, downlink transmission. |
last_ul_dl_nb_opp_index | 3 | The index of the first UL/DL opportunity within a bcn_interval. |
first_ul_dl_nb_opp_index | 158 | The index of the last UL/DL opportunity within a bcn_interval. |
nb_opp | 160 | The number of opportunities (counted from 0 to 159). |
tr_det_listening | 0.64 ms | Time period used for the preamble detection. |
ch_change | 1.36 ms | The time period used for channel change during the Beacon discovery. |
nb_channels | 69 | The total number of channels used for SubG-FSK communication (counted from 0 to 68). |
bcn_prm_dur | 140 ms | The Beacon preamble duration. |
nb_bcn_channels | 69 | The number of random channel indexes of selected channels for each Beacon hopping sequence. Each Beacon hopping sequence utilizes all available channels used in SubG-FSK communication (nb_channels). |
nb_neighb_bcn | 2 | The number of channels used in before and after the current channel for the Beacon transmission. |
nb_ul_dl_channels | 64 | The number of random channel indexes of selected channels for each uplink and downlink hopping sequence.nb_ul_dl_channels = nb_channels - 2*nb_neighb_bcn - 1 |
sub_slot_nb | 6 | The number of sub-slots in the contention window. |
sub_slot_time | 2 ms | The duration of a sub-slot in the contention mechanism. |
contend_time | 12 ms | The contention window duration in the contention mechanism.contend_time = sub_slot_nb * sub_slot_time |
nb_tx_retry | 3 | The default number of transmission retries in the contention mechanism. |
CS-UL | offset 8, period 50 | The common slot schedule defined by Sidewalk GWs in uplink direction. |
CS-DL | offset 9, period 50 | The common slot schedule defined in Sidewalk GWs in downlink direction. |
B.2 Parameters for SubG-CSS connection with 2 kbps data rate
Parameters introduced in 5.3.
| Name | Value | Description |
|---|---|---|
ul_separation | 367 ms | Separation of uplink Target Transmission Times. |
dl_separation | 5 s | Separation of downlink Target Transmission Times. The value of the parameter is also defined in Section 5.2 |
nb_ul_slot | 8 | The number of uplink slots. |
nb_slot | 9 | The total number of downlink and uplink slots in a dl_separation period.nb_slot = nb_ul_slot + 1 |
nb_dl_slot | 5, 10, 15, 20, infinite | The number of downlink slots after the last uplink. Numbers 5, 10, 15, 20 are applicable for Profile A. Infinite value is applicable for Profile B. The same as dl_slot_nb defined in Section 3.2.2.3. |
Parameters introduced in 5.5 .
| Name | Value | Description |
|---|---|---|
ul_sync_interval | 5 min | The maximum value of the time since last uplink for sending the synchronization packet with Epoch bit set. |
ul_sync_guard_interval | 1 min | Time interval within which uplink packets shall be used for downlink synchronization. Data packet in uplink direction within ul_sync_interval. |
nb_dl_slot | 5, 10, 15, 20, infinite | See description of nb_dl_slot. |
B.3 Parameters for use in security
Parameters introduced in 4.2.
| Name | Value | Description |
|---|---|---|
gcs_ret_num | 3 | The number of GET_TIME commands that are sent with the constant interval in case no response is received from the Sidewalk Cloud. |
gcs_resp_timeout | 30 s, 3, 5, 8, 10, 15 min | The interval between subsequent GET_TIME commands in case there is no response is received from the Sidewalk Cloud. The first interval value 30 s is used max retry count times. Time intervals 3, 5, 8, 10 are used once. 15 min is used till the moment the RESP_TIME is received. |
gcs_sync_int | 2 h | The time interval between two GET_TIME commands when the clock is synchronized on the Endpoint side. It is used for clock synchronization maintenance. |
gcs_clock_drift | 60 s | The maximum allowed clock drift on the Endpoint side. |
Parameters introduced in 4.7.2.
| Name | Value | Description |
|---|---|---|
T_IV_ref | 60 s | The validity of the reference time in Initialization Vector (IV). |