Skip to main content

IoT Services Platform: Functions and Requirements

  • Chapter
  • First Online:
  • 204k Accesses

Abstract

This chapter introduces the IoT Service Platform, which is considered to be the cornerstone of successful IoT solutions. It illustrates that the Service Platform is responsible for many of the most challenging and complex tasks of the solution. It automates the ability to deploy, configure, troubleshoot, secure, manage and monitor IoT entities, ranging from sensors to applications, in terms of firmware installation, patching, debugging and monitoring to name just a few. The Service Platform also provides the necessary functions for data management and analytics, temporary caching, permanent storage, data normalization, policy-based access control and exposure. Given the complexity of the Services Platform in IoT, the chapter groups the core capabilities into 11 main areas: Platform Manager, Discovery & Registration Manager, Communication (Delivery Handling) Manager, Data Management & Repository, Firmware Manager, Topology Management, Group Management, Billing and Accounting Manager, Cloud Service Integration Function / Manager, API Manager and finally Element Manager addressing Configuration Management, Fault Management, Performance Management and Security Management across all IoT entities.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   84.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Notes

  1. 1.

    OneM2M is the global standards initiative for Machine-to-Machine Communications and the Internet of Things

  2. 2.

    (37.76724070774898, −122.37890839576721) are the GPS Coordinate for a northern California area.

  3. 3.

    YANG is a tree-structured data modeling language (defined by IETF) used to model configuration and state data [6].

  4. 4.

    TR-069 as a bidirectional SOAP/HTTP-based protocol that was originally for remote management of end-user devices. It was published by the Broadband Forum and entitled CPE WAN Management Protocol (CWMP).

  5. 5.

    LWM2M (Lightweight Machine-to-Machine) protocol is defined by the Open Mobile Alliance for M2M / IoT, as an application layer communication protocol between a LWM2M Server and a LWM2M Client (located in a LWM2M Device).

  6. 6.

    Some researchers use the term QoS to refer to both QoS and GoS as defined above.

  7. 7.

    Alternatively, an Authorization, Authentication, and Accounting (AAA) server may be used for device authorization.

References

  1. IoT – Converging Technologies for Smart Environments and Integrated Ecosystems, Reviwer Publishers, Online: http://www.internet-of-things-research.eu/pdf/Converging_Technologies_for_Smart_Environments_and_Integrated_Ecosystems_IERC_Book_Open_Access_2013.pdf

  2. Internet of Things, Evolving the Manufacturing Industry, Online: http://www.cisco.com/c/en/us/solutions/internet-of-things/iot-products/services.html

  3. The Internet of Things: Between the Revolution of the Internet and the Metamorphosis of Objects, Gerald Santucci, Online: http://cordis.europa.eu/fp7/ict/enet/documents/publications/iot-between-the-internet-revolution.pdf

  4. From the Internet of Computers to the Internet of Things, Friedemann Mattern and Christian Floerkemeier, Distributed Systems Group, Institute for Pervasive Computing, Online: http://www.vs.inf.ethz.ch/publ/papers/Internet-of-things.pdf

  5. Reaping the Benefits of the Internet of Things, Cognizant Reports, May 2014, http://www.cognizant.com/InsightsWhitepapers/Reaping-the-Benefits-of-the-Internet-of-Things.pdf

  6. Philip N. Howard (8 June 2015). "How big is the Internet of Things and how big will it get?". The Brookings Institution. Retrieved 26 June 2015

  7. Stefan Wallina and Claes Wiksrom, “Automating Network and Service Configuration Using NETCONF and YANG: Online: http://www.tail-f.com/wordpress/wp-content/uploads/2013/03/Tail-f-NETCONF-YANG-Service-Automation-LISA-Usenix-2011.pdf

  8. BJORKLUND, M. YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF). RFC 6020, Oct. 2010

    Google Scholar 

  9. Broadband Forum Technical Report TR-069, CPE WAN Management Protocol, Issue 1 Amendment 5, Version 1.4, Nov 2013

    Google Scholar 

  10. Open Mobile Alliance M2M Device Management Specifications, Online: http://openmobilealliance.hs-sites.com/lightweight-m2m-specification-from-oma

  11. Open Mobile Alliance LightweightM2M Version 1.0, Online: http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/oma-lightweightm2m-v1-0

  12. Sokullu, R. and Karaca, O., “Fault Management for Smart Wireless Sensor Networks,” Ubiquitous Intelligence & Computing and 9th International Conference on Autonomic & Trusted Computing (UIC/ATC), Sept 4, 2012

    Google Scholar 

  13. G. Stanley and Associate, White Paper, “A Guide to Fault Detection and Diagnosis”, Online: http://gregstanleyandassociates.com/whitepapers/FaultDiagnosis/faultdiagnosis.htm

  14. IETF Network Working Group, Request for Comments (RFC) 3433, Entity Sensor Management Information Base, Online: https://tools.ietf.org/html/rfc3433

  15. G. Huston, “Measuring IP Network Performance”, the Internet Protocol Journal, Vol 6, Number 1, Online: http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_6-1/measuring_ip.html

  16. H. Hui-Ping, X. Shi-De, M. Xiang-Yin, “Applying SNMP technology to manager sensors in IoT”, The Open cybernetics & Systemic Journal, 2015, pp. 1019–1024, Online: http://benthamopen.com/contents/pdf/TOCSJ/TOCSJ-9-1019.pdf

  17. L. Adaro, Monitoring 101 eBook, Nov 2015, Online: https://thwack.solarwinds.com/docs/DOC-187523

  18. Stanford Sensor Course, Online: http://web.stanford.edu/class/me220/data/lectures/lect02/lect_2.html

  19. B. Hedstrom, A. Watwe, S. Sakthidharan “Protocol Efficiencies of NETCONF versus SNMP for Configuration Management Functions , University of Colorado, May 2011, Online: http://morse.colorado.edu/~tlen5710/11s/11NETCONFvsSNMP.pdf

  20. OMA LightweightM2M v.10, Open Mobile Alliance, Online: http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/oma-lightweightm2m-v1-0

  21. S. Duquet, Smart Sensors, Enabling Detection and Ranging for IoT and Beyond, Ladder Technology Magazine Elektronik Praxis, April 2015, Online: http://leddartech.com/smart-sensors

  22. 50 Sensors Applications for Smarter World, Libelium, Online: http://www.libelium.com/top_50_iot_sensor_applications_ranking/

  23. P. Seneviratne, Internet Connected Smart Water Sensors, September 2015, Online: https://www.packtpub.com/books/content/internet-connected-smart-water-meter

  24. P. Jain, Pressure Sensors, Prototype PCB from $10, Online: http://www.engineersgarage.com/articles/t

  25. D. Merrill, J. Kalanithi, P. Maes, “Siftables: Towards Sensor Network User Interfaces”, Online: http://alumni.media.mit.edu/~dmerrill/publications/dmerrill_siftables.pdf

  26. Whatis.com, Online: http://whatis.techtarget.com/definition/firmware

  27. Mobileburn, Online: http://www.mobileburn.com/definition.jsp?term=firmware

Download references

Author information

Authors and Affiliations

Authors

Problems and Exercises

Problems and Exercises

  1. 1.

    This chapter categorized the IoT Services Platform into 11 functions. a. Name and define each of the 11 functions. b. List and define the Element Manager functions.

  2. 2.

    What are the traditional FCAPS management functions? Do they also apply to IoT? If so, Are they sufficient?

  3. 3.

    List six reasons why the overall management functions of IoT solutions are more multifaceted than traditional networks.

  4. 4.

    IoT solutions are considered much more complex to manage than traditional networks?

    1. A.

      Why?—List top five factors.

    2. B.

      Why does the Fog layer introduce new changes for IoT?

  5. 5.

    This chapter mentioned that not all IoT entities will be IP address enabled.

    1. A.

      Why is that? Provide an example of IoT devices that are not IP addresses enabled.

    2. B.

      How does management system track such devices?

  6. 6.

    What is device registration on IoT? Why is it needed?

  7. 7.

    List the key responsibilities of the discovery function.

  8. 8.

    It was mentioned in Sect. 5.1 that for non-IP addressed enabled sensors, IoT sensors may be tracked by the combined (1) IP address of the gateway and (2) sensor address. Why both addresses do are needed?

  9. 9.

    Why IoT device self-registration is preferred over the method where a new IoT device have the capability to be identified during the discovery process?

  10. 10.

    The IETF has released NETCONF and YANG which are standards focusing on Configuration management. Name two other older methods that can be used for configuration management? What are their shortcomings?

  11. 11.

    Section 5 indicated that Accurate discovery is essential for many management tasks including asset management, network monitoring, network diagnosis and fault analysis, network planning, high availability, and others.

    1. A.

      Provide short definitions of asset management, network monitoring, network diagnosis and fault analysis, network planning, and high availability.

    2. B.

      Why is accurate discovery essential for each of the above functions?

  12. 12.

    What are the key differences between Provisioning and Configuration functions? Which one is done first?

  13. 13.

    What are key differences between deployment, provisioning, and orchestration?

  14. 14.

    What are the most basic two management functions to provide new services?

  15. 15.

    Provide an example of Service-Level Diagnostics and Fault Management Function in IoT where all devices are working correctly but the service level parameters are not being meet.

  16. 16.

    Why Fault Management is considered by many experts to be most challenging and important management function of IoT-based networks?

  17. 17.

    What are the three main functions of Fault Management? Provide detailed description of each term.

  18. 18.

    What are the concepts of fault tolerance in IoT networks? Give three examples of failures that should be handled by fault tolerance function in IoT-based networks.

  19. 19.

    Fault tolerance is not just a property of individual IoT element; it may also impact the IoT communication protocol. For example, the Transmission Control Protocol (TCP) was design as reliable two-way communication protocol, even in the presence of failed or overloaded communications links. How is this achieved in TCP?

  20. 20.

    There are special software and instrumentation packages designed to detect failures. A good example is a fault masking system. How does Fault Masking system detect failure?

  21. 21.

    What is Diagnostic Signature? Where it used?

  22. 22.

    In priority order, what are the top three IoT management functions that a service provider needs to provide to provide very basic services? Justify your answer.

  23. 23.

    Why Fault Management is considered to be very challenging in IoT network? That is, what are the main differences between managing IoT network and a traditional network?

  24. 24.

    Why IoT management is considered to be most challenging and complex task of the solution?

  25. 25.

    Section 7.2 indicated the need for a complete configuration backups with rollback capabilities as a key requirement for the IoT Platform Manager. What is configuration rollback? Why is it needed? Provide an example?

  26. 26.

    What are the definitions of Sensitivity and Dynamic Range? What are the typical units of Sensitivity and Dynamic Range?

  27. 27.

    What is Hysteresis? What is a typical unit of Hysteresis?

  28. 28.

    What is a firmware? What does it do? Why is it called so?

  29. 29.

    Why firmware Images are loaded into ROM and not the device storage?

  30. 30.

    How come Firmware Management was not part of the tradition FCAPS?

  31. 31.

    Data may be retrieved from various IoT sources including IoT devices and network elements (e.g., sensors, gateways, switches), IoT subscribers and IoT applications. IoT device and network element data is assumed to be collected by collection systems or by collection agents.

    1. A.

      What are the key differences between a collection system and a collection agent?

    2. B.

      What is IoT subscriber data? How is the data collected?

    3. C.

      What is an IoT application data? How is the application data collected?

  32. 32.

    In a table list three subscription and notification requirements along with examples of a subscriber and notification message.

Rights and permissions

Reprints and permissions

Copyright information

© 2019 Springer Nature Switzerland AG

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Rayes, A., Salam, S. (2019). IoT Services Platform: Functions and Requirements. In: Internet of Things From Hype to Reality. Springer, Cham. https://doi.org/10.1007/978-3-319-99516-8_7

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-99516-8_7

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-99515-1

  • Online ISBN: 978-3-319-99516-8

  • eBook Packages: EngineeringEngineering (R0)

Publish with us

Policies and ethics