Introduction to roof computing by Nishant Krishna
4 likes1,382 views
The document introduces the IEEE P1931.1 standard for roof computing, which provides a framework for real-time, onsite operations of Internet of Things (IoT) systems in secure, local environments. It outlines the importance of interoperability, security, and efficient connectivity for IoT devices, while aiming to lower operational costs and foster innovation. A significant focus is placed on enabling autonomous decision-making and collaboration among connected devices within various applications, including smart cities and connected industries.
Introduction to roof computing by Nishant Krishna
- 1. IEEE P1931.1 Introduction to ROOF Computing Nishant Krishna Software Architect and Consulting Engineer, Avaya Member, P1931.1 Working Group (Slides reused from Syam Madanapalli, Chair, P1931.1)
- 2. 2 About Nishant Krishna Ø Software Architect, Innovator and Inventor with ~17 years of experience working on Network Management Systems (NMS), Cloud and Virtualization, Software-Defined Network (SDN), API Development and Internet of Things (IoT) technologies. Ø 2 patent granted and 5 patents filed/pending with US Patent Office in the areas of Network Management Systems, Cloud, Virtualization and SDN Technologies. Ø I participate actively in User Experience (UX) and Wireframing related activities. Ø My areas of interest include Cloud and Virtualization, SDN, IoT, UX, User Interfaces, Network Security, Cryptography, public speaking and latest tech and gadgets. Ø Nishant has a Master of Science (MS) in Software Engineering degree from BITS, Pilani, along with many technical certifications. https://in.linkedin.com/in/nishantkrishna https://twitter.com/nishantkrishna
- 3. 3 “There are two types of organizations in today’s world, those that have been breached and those that just don’t know it yet.”
- 4. 6/18/174 Standards Title: Standard for an Architectural Framework for Real-time Onsite Operations Facilitation (ROOF) for the Internet of Things • Technical and functional interoperability for IoT systems that operate and co-operate in a secure and independent manner within the context of a local environment such as home, factory, office or airport, etc. • Defines an architectural framework, protocols and Application Programming Interfaces (APIs) for providing Real-time Onsite Operations Facilitation (ROOF). • ROOF computing and networking for the data and the devices include next-hop connectivity for the devices, real-time context building and decision triggers, efficient backhaul connectivity to the cloud, and security & privacy. • Defines how an end user is able to securely provision, commission and decommission the devices. Working Group Chair: Syam Madanapalli, Dell IEEE P1931.1: ROOF Computing
- 5. 6/18/175 Standards Title: Standard for Harmonization of Internet of Things (IoT) Devices and Systems • Define a metadata bridge to facilitate IoT protocol transport for sensors, actuators, and devices. • The standard addresses issues of security, scalability, and interoperability. This standard can provide significant cost savings and reduce complexity, and offer a data sharing approach leveraging current instrumentation and devices used in industry • The backend of such a globally scalable, secure and interoperable network would be based on the eXtensible Messaging and Presence Protocol (XMPP), • Key components and needs of a successful Smart City infrastructure will be identified and addressed. This standard does not develop Application Programming Interfaces (APIs) for existing IoT or legacy protocols. Working Group Chair: Dr. William Miller, MACT-USA, Dr. Muzzammil Hussain, Samsung (India Focus Group for 1451) IEEE P1451-99: IoT Harmonisation
- 7. History of Computing Paradigms 1960s Server Computing 1990s Distributed Computing 2000s Cloud Computing Server VPN Cloud Headquarters Subsidiaries Remote users Remote users Headquarters Subsidiaries Terminals
- 8. Roof, Humans and the Internet of Things 8 Roof protects people and their possessions.* * "Roof". Wikipedia. N.p., 2016. Web. The Internet of Things, the constrained devices, require an environment wherein they can operate, build trust, collaborate and be protected. Need a Roof for the Internet of Things.
- 9. IoT and the Autonomy 9 An IoT system should have various decision and automation tools that operate and cooperate autonomously within the context of a local environment.
- 10. What is Roof? 10 The ROOF • A new computing paradigm for the Internet of Things • ROOF is both a metaphor and acronym • Below the Cloud and Fog The Primary goal • To provide Autonomous and Realtime Response over a period of time • Context building using edge analytics Others • To support plug and play connectivity for the Things • Efficient connectivity to the Cloud/Service providers • Security by default with contextual analysis • Local storage
- 11. The Roof – for the Better Internet of Things 11 Cloud Hundreds Up to 1000s of kilometers away Fog Tens of thousands Few kilometers away ROOF Millions to billions Few meters/one-hop away Things Billions to trillions ROOF – Realtime Onsite Operations Facilitation for the Internet of Things
- 12. Motivation for the Roof 12 Various access & data protocols Realtime and offline support Constrained nodes, and device & data protection Variety of sensor & data and evolving infrastructure Connectivity Context Security Data Framework for interoperabilit y Realtime computing Computing for security and privacy Flexible backhaul and services
- 13. Roof Computing Data/Service Context Security Connectivity 13 Roof is a computational paradigm for the Internet of Things to provide • Next-hop connectivity for the Things • Realtime context building and actions • Efficient data & service connectivity to the Cloud/service provider • Framework and computing for security & privacy
- 14. The Roof and the Spatiotemporal Location 14 It is important to treat all events with respect to their temporal location! If (this) then (react) If (this) then (act) If (this) then (optimiz e) If (this) then (plan) Time Realtime Near realtime Future Things Fog Cloud Roof Fog Roof Roof Roof
- 15. Roof Functional Model 15 IoT Services Device&Network Management Security&Privacy Management Thing Connectivity Cloud Connectivity & Service Management Context Building Local Storage Physical world (Things) Intruders Users Cyber world/Service Providers
- 16. Roof Applications 16 Roof is essential for any IoT application, including: • Connected homes • Connected industries • Connected vehicles • Connected healthcare services • Connected public authorities • Clusters of IoT deployments in the smart cities • Other highly distributed IoT application deployments Clou d Gateway Things Mobile App Internet
- 17. Roof with Blockchain 17 Cloud Blockchain • Establish peer-to-peer trust & reputation • Information sharing and collaboration • Move away on security from passive prevention to cooperative distributed assurance
- 18. Roof vs. Fog vs. Cloud 18 Consideration Computing Model Roof Fog Cloud Distance to Things Few meters Upto few kilometers Upto thousands of kilometers Deployment numbers Millions to billions Tens of thousands Few hundreds Technology complexity Simple Complex Simple Implementation complexity Easy Difficult Easy Content Machine data The Internet fringe Big data Drivers The things - constrained devices Support for mobility and to reduce the latency Big Data storage and analytics Applications All IoT applications Large distributed IoT applications Appcesory, storage and analytics Cost of implementation Low High Medium
- 19. Goals for the Roof 1. Enable the devices under the Roof to collaborate and act in realtime 2. Bridge the physical and cyber world, and allow horizontal integration 3. Confirming to Roof requires security & privacy by design 4. Lower operational and maintenance cost with ease of configuration, commissioning, use and maintenance 5. Easy to build and repeatable – hence increased reliability, resilience and scalability for IoT deployments 6. Allow innovation for new business models and lower the barrier for entry for device manufacturers and service providers 19
- 20. Goal 1: Context Building Context Action Devices Sensor Fusion Cn=2^s – 1 Cn = Max. no. of contexts S= No. of States/services Compute Context Aggregate the data Route the data Data condensing is critical because of the sheer volumes of Data being generated.
- 21. Goal 2: Hormonization Service A Vendor IoT Platform Vendor IoT Hub Service B Vendor IoT Platform Vendor IoT Hub Service A IoT Platform Service B Roof Service C Vendor specific vertical solutions Roof harmonization
- 22. Goal 3: Security by Design Security fusion, combining multiple security touchpoints, helps curb security threats. Device manufacturers and Service providers require support Security by design to fit into the Roof Model. Context Authorization Authentication Network Security Role Based
- 23. Goal 4: Better User Experience Configuration Commissioning and decommissioning Software updates Coherent services and distributed user experience User aware security & privacy
- 24. Goal 5: Reuse & Scalability A model that can be replicated easily Be able to build large scale IoT applications, e.g. a Smart City A model that can be used across multiple applications and verticals Act autonomously in realtime Connect to the Cloud for more value creation Cloud
- 25. Goal 6: Innovation Roof allows evolution of common IoT platforms for rapid application/service delivery Applications can evolve independently & enables an environment for rapid innovation Devices can evolve independently Open IoT Platform Service BService A Service N
- 26. What’s happening right now? ¾ Working group is meeting once every month. On an average close to 50 members join the meeting. The group has representation from industry, standards body, device manufacturers, academia and many more areas, from around the world. ¾ Sub-groups are already formed for various smaller sections of the standard and they are activity working. ¾ Discussions about creating reference and open-source implementation are going on. ¾ Use cases and areas where ROOF can be applicable are actively identified in many of the sectors and are being expanded. 26
- 27. Few parting thoughts… ¾ Interoperability can be achieved through mandating a common set of API, ontology and data semantics. ¾ We need to consider capability of establishing secure ownership of all “things” including ROOF infrastructure. A “Software Roof of Trust” may need to be established. ¾ We must allow ROOF and things to be private/business owned or rented (owner maintains final control) and/or provided by an internet provider. ¾ May need to use blockchain to control both ownership and allowed administrator/user along with a kill switch. ¾ We can’t leave out requirements for safety conformance of things, communications, and processing of so many of the ROOFs and Things that will be (already are) safety critical. ¾ Billions of ”things” out there use variety of protocols and standards. We need to work towards developing protocols and strategies to integrate such vast diversity of communication technologies. 27
- 28. Thank You! 28