SWRA826 August   2025 CC1312R7 , CC1314R10 , CC1352P7 , CC1354P10 , CC1354R10

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1 Acronyms
  5. 2 Introduction
  6. 3 Network Configuration
  7. 4 Wi-SUN FAN and Joining Process
    1. 4.1 Wi-SUN FAN
    2. 4.2 Joining Process
  8. 5 Test Results
    1. 5.1 Join Time - Maximize Responsiveness, Balanced Mode, Maximize Scalability
    2. 5.2 Rejoin Time - One Router Node
    3. 5.3 Rejoin Time - Full Network
    4. 5.4 Throughput - Maximize Responsiveness, Balanced Mode, Maximize Scalability
    5. 5.5 BR Detection of RN Disconnection
    6. 5.6 RN Detection of BR Disconnection
  9. 6 Latency
  10. 7 Preferred Parent and Disconnected Parent
    1. 7.1 Preferred Parent
    2. 7.2 Disconnected Parent
    3. 7.3 Test Results for Preferred Parent and Disconnected Parent
  11. 8 Additional Information
  12. 9 Summary
  13. 10References

9 Summary

The TI Wi-SUN FAN design provides expected network performance for a given network configuration profile and topology. The TI Wi-SUN FAN offers three different network profiles to configure the network control packet overhead to varying levels for a given network size.

The network profile is determined by the network administrator based on the required network size and application traffic profile.

  • Network size: for large networks (for example, 1000+), a maximize responsiveness configuration is not possible as the control protocol overhead required is higher than the available network capacity.
  • Application traffic profile: if the typical data traffic profile is expected to be only one pair of nodes communicating at a given time in a request or response type transaction, then the overhead from such a data traffic needs to be less than the available data overhead for any configuration. In this case, only network size needs to be considered and TI recommends to pick the most aggressive profile possible to get a more responsive network. This is also corroborated by the latency test results in Latency, which was not affected by network configuration. However, if the application traffic requires every node to transmit and receive large chunks of data in parallel that can take up significant data capacity, then a less aggressive network profile is recommended.

For a typical e-metering application based on DLMS or COSEM, where the traffic pattern is most expected to be based on a central client reading for each server a time, the most aggressive profile possible for a network size is recommended. While actual network overhead depends on node placement and topology, which can affect the network profile determination, the following recommendations are for a typical network of given sizes.

Network Profile Network Size Recommendation
Maximize responsiveness < 300
Balanced mode 300 - 500
Maximize scalability > 500