62
Internet of Things (IoT)
environment, society, and individuals. Standards are required for two-way communication and for exchange of information between things and environment. The design
of IoT standards should focus on efficient use of energy and network capacity [6]. It also
has to take into account other regulations which restrict frequency bands and power
levels for radio frequency communication. For IoT, European Telecommunications
Standards Institute (ETSI) produces globally applicable standards related to information and communication technology (ICT), and their goal is to strengthen the standardization efforts of Machine to Machine (M2M). Internet Engineering Task Force (IETF)
has come out with the new group 6LoWPAN (IPV6 over Low Power Wireless Personal
Area Networks) to integrate sensor nodes with IPV6 networks. Another group named
ROLL (Routing Over Low power and Lossy) has come out with the routing protocol
draft. It aims to provide basis for routing over low-power and lossy networks.
IETF along with other relevant organizations is working to come out with more
standards. Many organizations are putting a lot of effort to standardize protocol to
lower the cost of the IoT product. Although many protocols are emerging, at the application layer, the contribution toward data formats and encoding of independent standardization of information (i.e., information model) is lacking. It is obvious that the
emerging idea is to consider IoT standardization as an integral part of the future standardization process. Various issues faced in standardization are discussed in the following section.
TABLE 4.2
IoT Technical Interoperability Challenges
Requirements
Rationale and Remarks
Best Practice Awareness
Avoid spreading effort in
addressing interoperability for
worldwide protocols
• Supports interoperability market worldwide to support specifications
and protocols
• Develop market acceptance roadmap
• Use clear specification development and methodologies, leading to
improved quality while reducing time costs in a full chain optimized
development cycle
• Define profiles, if needed, to improve interoperability
Validations of Specifications
Reduce ambiguities in
specifications and
development time
• Specifications development time would be too long
• Ambiguities in development could lead to major noninteroperability
issues
• Quality, time, and cost factors lead to the needs of models and
automation
Tests Specification
Provide market accepted test
specifications ensuring
minimum accepted level of
interoperability
• Lack of test specifications lead inevitably to different specification,
implementation, and interoperability issues
• Development of test specification is too expensive for the limited
standard of stakeholders and effort should be collectively shared
• Tools processing and automation are the only way to reduce time and to
market
Tools and Validation programs
Develop market accepted and
affordable tools used in the
market accepted validation
programs
• Development of test tools is expensive
• Available test tools developed spontaneously by market forces can have
test scopes overlapping and may not even answer all test needs
• Full chain of specification for tool development is not considered
• Providing final confident to end users with consistent tests is not
considered
Source: Vermesan, O. and Friess, P., Internet of Things—Converging Technologies for Smart Environments and
Integrated Ecosystems, River, Alaborg, 2013.
Internet of Things (IoT)
environment, society, and individuals. Standards are required for two-way communication and for exchange of information between things and environment. The design
of IoT standards should focus on efficient use of energy and network capacity [6]. It also
has to take into account other regulations which restrict frequency bands and power
levels for radio frequency communication. For IoT, European Telecommunications
Standards Institute (ETSI) produces globally applicable standards related to information and communication technology (ICT), and their goal is to strengthen the standardization efforts of Machine to Machine (M2M). Internet Engineering Task Force (IETF)
has come out with the new group 6LoWPAN (IPV6 over Low Power Wireless Personal
Area Networks) to integrate sensor nodes with IPV6 networks. Another group named
ROLL (Routing Over Low power and Lossy) has come out with the routing protocol
draft. It aims to provide basis for routing over low-power and lossy networks.
IETF along with other relevant organizations is working to come out with more
standards. Many organizations are putting a lot of effort to standardize protocol to
lower the cost of the IoT product. Although many protocols are emerging, at the application layer, the contribution toward data formats and encoding of independent standardization of information (i.e., information model) is lacking. It is obvious that the
emerging idea is to consider IoT standardization as an integral part of the future standardization process. Various issues faced in standardization are discussed in the following section.
TABLE 4.2
IoT Technical Interoperability Challenges
Requirements
Rationale and Remarks
Best Practice Awareness
Avoid spreading effort in
addressing interoperability for
worldwide protocols
• Supports interoperability market worldwide to support specifications
and protocols
• Develop market acceptance roadmap
• Use clear specification development and methodologies, leading to
improved quality while reducing time costs in a full chain optimized
development cycle
• Define profiles, if needed, to improve interoperability
Validations of Specifications
Reduce ambiguities in
specifications and
development time
• Specifications development time would be too long
• Ambiguities in development could lead to major noninteroperability
issues
• Quality, time, and cost factors lead to the needs of models and
automation
Tests Specification
Provide market accepted test
specifications ensuring
minimum accepted level of
interoperability
• Lack of test specifications lead inevitably to different specification,
implementation, and interoperability issues
• Development of test specification is too expensive for the limited
standard of stakeholders and effort should be collectively shared
• Tools processing and automation are the only way to reduce time and to
market
Tools and Validation programs
Develop market accepted and
affordable tools used in the
market accepted validation
programs
• Development of test tools is expensive
• Available test tools developed spontaneously by market forces can have
test scopes overlapping and may not even answer all test needs
• Full chain of specification for tool development is not considered
• Providing final confident to end users with consistent tests is not
considered
Source: Vermesan, O. and Friess, P., Internet of Things—Converging Technologies for Smart Environments and
Integrated Ecosystems, River, Alaborg, 2013.