1. OpenHAN Attachment And Service Model Thoughts David Ress May 5, 2010 V0.2

2. OpenHAN Attachment Model Simplified HAN Device State Machine Error paths, de-registration, unenrollment, sub-states and events all ignored for clarity

3. An Example Domain View HAN Connected Devices – Two Exposed ESIs: ESI-U: interface to Utility Managed Services ESI-C: interface to third party EMSPs – 3 in home devices (Dev1..Dev3) – 2 Meters Registrations – Dev 1 and Dev 2 are registered with ESI-U – Dev 4 is registered with ESI-C – Meters are registered with ESI-U Enrollments – Dev 1 and Dev 2 are enrolled with Svc A and Svc B – Dev 3 is enrolled with Svc X and Svc Y

4. An IP Model Example HAN Attached – Unique local address negotiated on HAN (not DHCP) – Devices on HAN can talk to each other using local addressing (Local HAN services) E.g. Meter reads ESI Attached – Global address assigned (DHCP) – HAN device becomes part of a particular provider subnet (CIDR block) – If there is more than 1 ESI connected to HAN, then A DHCP Request could receive multiple offers – e.g. one from a utility and one from an ISP. – Device is ‘reachable’ from anywhere (subject to firewall, ACLs, security, etc) through the provider network that the device accepted the DHCP offer from – Likely consequence: Device can get services from a Utility OR third party providers but not both because the Utility will not want to provide over the top access to HAN devices via its AMI network and the device can not get multiple Global IP addresses on one physical interface. Svc Enrolled – One ore more provider services enrolled