Page 405 - Unleashing the potenti al of the Internet of Things

Unleashing the potential of the Internet of Things 4

8.6 Traffic and load awareness

To realize traffic and load optimization, SCN applications have the following requirements:
1) Information related to traffic and computational capabilities of SCN objects is
recommended to be registered for SCN applications.
2) Information about current traffic and computational load is recommended to be managed
for SCN applications.

8.7 Fault awareness
A SCN needs to react to the failure of any SCN objects in order to provide reliability and
availability.
1) Information about SCN object faults is required to be managed for SCN applications.

8.8 Routing

1) SCN applications are required to support routing using distributed mechanisms, such as
those based upon peer-to-peer (P2P) techniques.
2) SCN applications are recommended to identify the preferred path between any pair of SCN
objects. The path selection can be based on historical data or on real-time data to reflect the
traffic congestion situation between those SCN objects.

8.9 Load balancing

1) SCN applications are required to dynamically balance the traffic load of SCN objects,
based on the status and/or capabilities of SCN objects, traffic balancing policy, etc.

8.10 Scalability

1) SCN applications are required to offer scalability by using P2P and/or other distributed
mechanisms, so that the capacity of the SCN infrastructure to provide services to users is
proportional, or nearly proportional, to the number of the motes and actuators.

8.11 Fault tolerance

1) SCN applications are required to ensure reliability and availability of the SCN
infrastructure in order to handle a single mote failure and a mote group failure.

2) SCN applications are recommended to ensure reliability and availability of the SCN
infrastructure in the case of failure of the SCN controllers.
NOTE – In the case of these failures, the capabilities of the failed SCN object(s) can be dynamically
replaced by those of other SCN objects to provide consistent service to end users.

8.12 Quality of service (QoS)
Different SCN applications may have different QoS requirements. For example, data transmission
in verification applications may require much lower delays than in other SCN applications.
1) SCN applications are recommended to support QoS differentiation according to the
required service level quality.
2) It is required that the traffic volume generated by SCN applications be managed.

3) It is recommended that SCN applications avoid access concentration in a single SCN
controller or a single mote.

4) It is recommended that specific QoS support for emergency applications be provided.
NOTE 1 – Clause 8.18 provides further information and requirements about emergency applications
in SCNs.

Rec. ITU-T Y.4250/Y.2222 (04/2013) 391