Site Tools


the_re-discovery_problem

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
the_re-discovery_problem [2016/05/18 20:33]
rightbrain
the_re-discovery_problem [2016/05/19 15:21]
rightbrain
Line 6: Line 6:
   * Currently, IoTivity discovery typically requires many (if not most) IoTivity servers to respond, given the small amount of information in the discovery packets on which to base a response.   * Currently, IoTivity discovery typically requires many (if not most) IoTivity servers to respond, given the small amount of information in the discovery packets on which to base a response.
   * As IoTivity becomes ubiquitous, two issues will become critical that may not be considered very important today: scaling and energy. We should start orienting IoTivity to support those issues now.   * As IoTivity becomes ubiquitous, two issues will become critical that may not be considered very important today: scaling and energy. We should start orienting IoTivity to support those issues now.
-  * The scaling issue is that IoTivity is intended to support large number of systems from a variety of companies, and each system may consist of multiple client, gateway and server applications. For example, a node might have a dozen or more independent IoTivity server application sharing the same IP stack, and a network may support hundreds of different server applications in various groupings across thousands of server nodes.+  * The scaling issue is that IoTivity is intended to support large number of systems from a variety of companies, and each system may consist of multiple client, gateway and server applications. For example, a server ​node might have a dozen or more independent IoTivity server application sharing the same IP stack, and a network may support hundreds of different server applications in various groupings across thousands of server nodes.
   * The energy issue only becomes apparent when we consider the intended scale of IoTivity. Over time, we expect IoTivity to be used in millions and possibly billions of devices. This means that any unnecessarily repetitive activity can potentially waste much energy. Making the problem worse is that much of that energy will be in devices depending on batteries or scavenged power, where energy usage can determine the lifetime or availability of IoTivity systems.   * The energy issue only becomes apparent when we consider the intended scale of IoTivity. Over time, we expect IoTivity to be used in millions and possibly billions of devices. This means that any unnecessarily repetitive activity can potentially waste much energy. Making the problem worse is that much of that energy will be in devices depending on batteries or scavenged power, where energy usage can determine the lifetime or availability of IoTivity systems.
   * Networks can experience temporary disruptions. Such disruptions can interrupt or otherwise interfere with IoTivity systems. The disruptions can occur in both wired and wireless networks, and their cause can be natural (such as wireless interference) or as a result of technology issues such as re-configuring a network. Networks talking directly to IoTivity server nodes are more likely to experience disruptions. We can't eliminate disruptions.   * Networks can experience temporary disruptions. Such disruptions can interrupt or otherwise interfere with IoTivity systems. The disruptions can occur in both wired and wireless networks, and their cause can be natural (such as wireless interference) or as a result of technology issues such as re-configuring a network. Networks talking directly to IoTivity server nodes are more likely to experience disruptions. We can't eliminate disruptions.
the_re-discovery_problem.txt ยท Last modified: 2016/05/19 15:29 by rightbrain