FIWARE Global Summit - Edge/Fog Computing in “Powered by FIWARE” Architectures
0 likes108 views
The document discusses the integration of edge computing within FIWARE architectures, highlighting Sakura Internet's experiments focused on IoT and edge computing. It addresses the challenges of achieving low-latency processing by utilizing edge computing nodes closer to data sources, providing an architecture proposal and evaluation results that confirm the speed advantages of edge processing. The conclusion emphasizes the need for edge management information and a protocol wrapper to improve interconnectivity and supports the continued development and implementation of this system.
![What is “Edge Computing” ?
§ Cloud is far away from IoT Devices.
• Requirement : under 10 [msec]. (ideally)
• Actually : over 20 [msec]
§ The solution is “Edge computing”.
• Put Nodes (computing resources) on the
edge (= local site) to process with low
latency.
• Not only “Edge”, but also “Cloud”.
□ Edge : for quick response
□ Cloud : for data storage, persistency,
reliability, ...
App
Smart phone , IOT Device
Round Trip Time : 20 msec 〜
App
RTT : 〜10
msec
Computer Resources
on the Edge
Cloud](https://image.slidesharecdn.com/2-shunsukekikuchi-edgefogcomputinginfiwarearchitectures-191030153358/85/FIWARE-Global-Summit-Edge-Fog-Computing-in-Powered-by-FIWARE-Architectures-4-320.jpg)
FIWARE Global Summit - Edge/Fog Computing in “Powered by FIWARE” Architectures
- 1. Scale Up for a Real Smart Future Berlin, Germany 23-24 October, 2019 Edge/Fog Computing in “Powered by FIWARE” Architectures Shunsuke KIKUCHI (Senior Researcher, SAKURA internet inc.)
- 2. Table of Contents § SAKURA internet inc. Corporate Profile and our ”Data Exchange” experiments, § What is ”Edge Computing”, § FIWARE and Edge Computing, § Proposal : Edge Computing in “Powered by FIWARE” Architecture, § Trial (Demo) System, and its evaluation, § Conclusion.
- 3. SAKURA internet inc. Cooperate Profile § SAKURA internet is a Datacenter Service Provider in Japan. § SAKURA internet offers “Cloud”, “VPS”, “Rental Server” service, etc. § SAKURA internet is conducting an experiments of “Data Exchange” powered by FIWARE with NEC. • We are focusing on the ”IoT” and ”Edge Computing” in the experiments. our Data Exchange Experiments
- 4. What is “Edge Computing” ? § Cloud is far away from IoT Devices. • Requirement : under 10 [msec]. (ideally) • Actually : over 20 [msec] § The solution is “Edge computing”. • Put Nodes (computing resources) on the edge (= local site) to process with low latency. • Not only “Edge”, but also “Cloud”. □ Edge : for quick response □ Cloud : for data storage, persistency, reliability, ... App Smart phone , IOT Device Round Trip Time : 20 msec 〜 App RTT : 〜10 msec Computer Resources on the Edge Cloud
- 5. Edge System interconnect § “Edge System” (=the system configured by devices, edge app and/or cloud app) will grow and connect each other in near future. § “Edge-connectability”: • “Interconnectivity” : Edge Systems can connect each other. • “Rapidly Connect” : connect not only in cloud, but also on the edge. Cloud …… On-site. On-site. 1 tenant Cloud Node Edge System Edge Node Device App App App App App App 1 tenant Edge Node Device App Edge Node Device App Edge
- 6. How to adapt FIWARE for edge computing ? § “Interconnectivity” : FIWARE is suitable. § “Rapidly Connect” : FIWARE is not Edge friendly. □ for Rapidly Connect , “Context broker on the edge” is required. □ but, How to deal two context brokers both cloud and edge ? Cloud App App Edge Node App Context Broker Context Broker Device App Edge
- 7. FIWARE Edge Architecture Design consideration. How to use 2 context brokers in Cloud and on edge ? → How to delivery a context information to all applications in the Cloud and on the edge ? App App Context Broker Context Info. Context Info. AppCloud Edge 2. Application Responsible Context Broker App App Context Broker Context Info. App 1. Context Broker Federation. Notification Register/ Update/ Delete Context Broker Get or
- 8. FIWARE Edge Architecture Design consideration.(Cont’d) App App Context Broker Context Info. Context Info. AppCloud Edge 2. Application Responsible Context Broker App App Context Broker Context Info. App 1. Context Broker Federation. Notification Register/ Update/ Delete Context Broker Get Register Register to Edge CB. and Provider and Notification config to Cloud CB. Register to Edge CB. and Register to Cloud CB. Update Update to Edge CB. Update to Edge CB. and update to Cloud CB. Get Get from nearby CB. Get from nearby CB. Notification Subscribe Notification to nearby CB. Subscribe Notification to nearby CB. (Edge CB. down) Edge CB. down detect -> Re-Register to Cloud CB. : (Cloud app may fail to get.) There is no impact on cloud app. or
- 9. FIWARE Edge Architecture Design consideration.(Cont’d) App App Context Broker Context Info. Context Info. AppCloud Edge 2. Application Responsible Context Broker App App Context Broker Context Info. App 1. Context Broker Federation. Notification Register/ Update/ Delete Context Broker Get Register Register to Edge CB. and Provider and Notification config to Cloud CB. Register to Edge CB. and Register to Cloud CB. Update Update to Edge CB. Update to Edge CB. and update to Cloud CB. Get Get from nearby CB. Get from nearby CB. Notification Subscribe Notification to nearby CB. Subscribe Notification to nearby CB. (Edge CB. down) Edge CB. down detect -> Re-Register to Cloud CB. : (Cloud app may fail to get.) There is no impact on cloud app. or
- 10. Proposal : Edge Computing in “Powered by FIWARE” Architecture Cloud Context Broker • Define “Edge Management Information” □ Manage “Edge CB Address, state, availability” Edge Context Broker • Notify the message to edge Apps. Edge Application • Send all messages to both Cloud CB. and Edge CB (for ensuring the reachability), • Receive notification message from only EdgeCB. □ Switch notification subscription from Cloud CB to Edge CB according to Edge Management Information. App App Context Broker Context Info. Context Info. AppCloud Edge Context Broker NGSI Protocol Stack Wrapper Edge Mgmt. Info. Notification Register/Update/Delete Notify Edge Info Subscription Edge Computing Architecture Standard App. (no wrapper)
- 11. Trial System § Trial System Specifications : • Edge Node : Raspberry Pi 3B+, Passive Infrared Sensor, LED Array (x4 Nodes) • Edge Context Broker : Intel Compute Stick BOXSTICK1A8LFC（ATOM, 1GB Mem） • Cloud Context Broker : SAKURA Cloud （1Core, 2GB Mem） Data Store & Analyze Edge Node Aisle Detect Aisle Lights up Sample Application “Collision Warning System” CB CB
- 12. Evaluation Results • Confirmed that Edge Round-trip is more rapid than the Cloud Round- trip. • (The impact of Edge CB performance is significant....) Context Broker RTT : 20.26 Context Broker RTT : 13.97 process time : 0.55 process time : 7.65 Target RTT (get version) RTT (get entities) ping Processing Time Edge Context Broker 8.90 13.97 6.32 7.65 Cloud Context Broker 20.01 20.26 19.71 0.55
- 13. Conclusion. § Cloud is far away from IoT Devices. § Edge Computing becomes a solutions. § FIWARE is suitable for the aspects of interconnectivity, but not Edge friendly. § We suggest ‘Edge computing “Powered by FIWARE” Architecture’ contains, • Edge management information, • NGSI Protocol Stack Wrapper for edge application, which manage notification subscription for edge communication. § We confirmed the effectiveness of Edge Round trip. § We will implement the system and publish soon. Thank you for your comment or suggestion !
- 14. Thank you! Keystone Sponsor: Join our newsletter Follow us!!! Community Partners: Media Partners: