180 likes | 291 Views
Live E! Project Multi-Domain Sensor Networking. Live E! Tech. WG. Outline. Live E! Project Overview Deployment Status Interfaces and Data Expressions Interface Data Structure Example Multi-Domain and Interoperability Issues Application Protocol Level Interoperability
E N D
Live E! ProjectMulti-Domain Sensor Networking Live E! Tech. WG
Outline • Live E! Project • Overview • Deployment Status • Interfaces and Data Expressions • Interface • Data Structure • Example • Multi-Domain and Interoperability Issues • Application Protocol Level Interoperability • Data Semantics Level Interoperability
What is Live E! project ?? • A research project for Internet-based sensor networking • Multi-domain (multiple-organizations) • Global-scale (sensor data on the Earth) • A data platform of sensor readings • 10 server nodes • 100 working weather sensor nodes • Data archive (for 3 years) • A testbed for sensor applications • Disaster management application • Business model trial • ...
Live E! System Architecture Science Global Warming / Heat island Disaster Management Facility Management Education Agriculture Live E! Application Live E! Data Platform Sensor
Live E! Internet Weather Station Temperature, Humidity, Air Pressure RainFall, Wind Speed/Direction SOAP/XML CPU: ARM 200MHz OS: Linux
Live E! Multi-Domain Sensor Systemsover the Internet User Applications 1. Organization A, B, C 2. Server deployment & Link configuration 3. Management 4. Request from user applications 5. Iterative search lookup request: lookup response: Organization A API Live E! server ① Access ② API API ③ Live E! server Live E! server ④ ⑤ ⑥ Profile Organization C Organization B Sensor
Live E! Server Operating Status International: Chinese Taipei: Taiwan Network Information Center (TWNIC) National I-lan University (NIU) Thailand: Prince of Songkla University (PSU) Loei Rajabhat University (LRU) In Japan: The University of Tokyo Keio University Nara Institute of Science and Tech. Hiroshima-City University Tottori-Environmental University
Dense Deployment Area (Testbed)Kurashiki-city, Okayama, JAPAN Disaster Management Application Rain Detection and Notification Business Application Analysis of Correlation as a Basic Research About 30 sensor nodes in 25km × 25km
Outline • Live E! Project • Overview • Deployment Status • Interfaces and Data Expressions • Interface • Data Structure • Example • Multi-Domain and Interoperability Issues • Application Protocol Level Interoperability • Data Semantics Level Interoperability
Live E! Interface and Data Format Live E! Applications Data Retrieval I/F FETCH Interface - Applications call for the data SOAP/XML Live E! Service Profile Registration I/F Data Upload I/F SOAP/XML or Console SOAP/XML PUSH Interface - Periodically: 10[sec]~10[min] (*) Data upload from sensors behind FW / NAT location: Tokyo sensorModel: WM918 Sensor Profile
Live E! Sensor Nodes Temperature RainRall combined WindDir Humidity Pressure WindSpeed element Vaisala WXT510 <sensorGroup class=“combined” id=“...”> <sensor id=“...” type=“Temperature” /> <sensor id=“...” type=“Humidity” /> <sensor id=“...” type=“Pressure” /> <sensor id=“...” type=“RainFall” /> <sensor id=“...” type=“WindDir” /> <sensor id=“...” type=“WindSpeed” /> </sensorGroup> id: unique character string
The Structure of Sensor Object Combined Sensor latitude=“35.5” Weather Station longitude=“120.3” vendor=“...” Combined Sensor Attribute Element Sensor Attribute Sensor Profile Unit type=“Temperature” Data Upload / Retrieval Unit T H P R Element Sensor type=“Humidity” Element Sensor Attribute The definition of attributes, which is managed by a profile schema in the system global, can be flexibly changed depending on the target environment. Value time=“2009-02...” error=“overflow” 25.0 25.5 Value Attribute 25.2
Profile Registration and Data Upload Live E! server Profile Registration Sensor Profile Data Upload GW s1 s2 s3 *) Attributes should include ID, BuildNo., RoomNo., PointName, Latitude, Longitude, Class, Type, SamplingFreq. MeasurementUnit, DataType(e.g., scalar/radius/string), and any other properties. s4 s5 A System Operator A Sensor System
Data Sharing PlatformProfile Sharing for Sensor Lookup Operator / User Profile Profile Profile Lookup Lookup Lookup Data Data Data Search Plane Data Plane DB DB DB Sensors Domain A Domain B Domain C
Outline • Live E! Project • Overview • Deployment Status • Interfaces and Data Expressions • Interface • Data Structure • Example • Multi-Domain and Interoperability Issues • Application Protocol Level Interoperability • Data Semantics Level Interoperability
Two Types of Interoperability • Application Protocol (L7) level interoperability can be achieved by making the protocol standard. • Semantics level interoperability management are always needed. Located in Tokyo Deployed Outside Data Semantics Level Interoperability for Temperature Application Protocol (L7) Level Interoperability
Data Semantics Level Interoperabilitiy& Application Protocol Level Interoperability Operator / User Profile Profile Profile Lookup Lookup Lookup Data Semantics Level Interoperability Data Data Data Search Plane Data Plane DB DB DB Application Protocol Level Interoperability Sensors Domain A Domain B Domain C