1 / 6

Embedded Building Application Stack

This overview focuses on the fragmented landscape of building data and the need to break down data silos for better access by consumers and developers. It introduces a novel design approach that starts with smarter sensors while keeping the system lightweight. Utilizing an embedded IPv6 stack, the application employs HTTP and JSON for streamlined communication and control. It emphasizes the importance of integrating raw data with metadata, supporting various functionalities like reporting and calibration, thereby enabling efficient data management and utilization across SCADA and building management systems.

telma
Download Presentation

Embedded Building Application Stack

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Embedded Building Application Stack Stephen Dawson-Haggerty

  2. Overview • Current state of world: building data exists in application stovepipes • SCADA/building management systems • Sensors accessed over RS485/Modbus • Goal: break open the data silos and make the data available to consumers, developers • Start with the sensor: make it smarter • Not too smart, though: keep things small

  3. System Designor, REST in 36kB • Build on blip, embedded IPv6 stack • Use HTTP for control channel • Standards in IETF, IEEE moving along nicely, but don’t get held up by them! Application Interface HTTP Engine TCP TinyOS/BLIP HYDRO Routing 6lowpan HC 802.15.4 Link

  4. Meter Interface: HTTP + JSON • Use HTTP as app-level control protocol • JSON is concise object transport • Also defined a compressed application/x-binaryjsoncontent type • Distinguish metering from sensing • Integrate raw data with metadata • Calibration • Engineering units • Reporting support allows pushing of sensor data

  5. Meter Interface /meter # meters of quantities of flow provide this service [GET] /channelID # a particular channel [GET] /reading # meter reading [GET] /format # calibration and units [GET/POST] /parameter # sampling parameter [GET/POST] /profile # history of readings [GET] /report # create and query periodic reports [GET/POST] POST requests supply JSON objects as arguments: POST: http://meter1.cs.berkeley.edu/report { "ReportResource" : "/meter/*/reading", "ReportDeliveryLocation" : "http://webs.cs.berkeley.edu/receivereports.php", "Period" : 60, "Minimum" : 50, "Maximum" : 100 }

  6. More information • Schema + API Documentation • http://webs.cs.berkeley.edu/blap/ • BLIP http://smote.cs.berkeley.edu:8000/tracenv/wiki/blip

More Related