1 / 1

LoCal Protocol Architecture

LoCal Protocol Architecture. Jorge Ortiz and Ariel Rabkin. LoCal-ized Grid. Layered Architecture. Relies on information overlay to coordinate flow of power Three kinds of devices: power producers/consumers Intelligent Power Switch: arbitrate flow of power to devices

yakov
Download Presentation

LoCal Protocol Architecture

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. LoCal Protocol Architecture Jorge Ortiz and Ariel Rabkin LoCal-ized Grid Layered Architecture • Relies on information overlay to coordinate flow of power • Three kinds of devices: • power producers/consumers • Intelligent Power Switch: arbitrate flow of power to devices • Broker-IPS: responsible for buying and selling power • All protocols are “application layer” in networking sense. • Not a precise analog with OSI model. Upper Layers Lower Layers • Interior planning protocol (IPP) • spoken between IPSes including broker/IPSes.)  This protocol expresses things like "I expect to have this much power available tomorrow", and "I need this much power, starting in ten minutes, and continuing indefinitely". • Discovery (Disc) • spoken between brokers, which is comparable to BGP.  This is the protocol used to discover the capacities of ASes, including things like topology. (Needed in order to arrange delivery) • Contract formation layer • spoken between machines called *brokers*, that speak for real-world principals.  The protocol defines machine-readable ways for offering future power delivery, with prices and delivery probabilities/ quality constraints.  This is analogous to SIP, the VOIP session initiation protocol. • Link state/device layer (LS) • protocol which the IPS speaks with local hardware. This protocol lets devices express thoughts like "please give me DC power at 100V", and "you're turning off in 15 seconds". • Device Query Protocol (DQP) • IPS speaks to local hardware. This protocol defines how to query devices for things like "how much power do you have stored?  How much power do you need to operate?  How much power do you expect to generate?" Architectural Overview Future Work • Need to define abstract syntax of each protocol • Implementation probably layered on existing wire protocols. • Can reuse SNMP, Web Services, X.509, etc • Challenges: • How to name and identify devices? • How to identify and authenticate market principals? • How to describe resource needs and wants? Do we need to measure slack? “AS” “AS” Energy Storage Energy Storage bIPS bIPS Disc DQP DQP IPP IPP P IPS IPS C C P C C DQP/LS DQP/LS DQP/LS DQP/LS C C C C C C

More Related