OSGi World Congress 2003

1. Smart Metering in Smart Homes
Dr Paul KOPFF Electricité de France

2. gatewaygateway gateway
devicesdevices devices
different home (automation) networks
PSTN / xDSL networks
service aggregator
InterNet
service
provider
service
provider
Sporadic
access ?
General
architecture

3. I will disturb any
preprogrammed
automation scheme
INTENTS:
Energy Management
Load Management
Tariff Management
…
Other Value Added
Services ?
00115.637
kWh
Smart
Power
Meter
Smart Appliances…
The customer is
THE unpredictable part
of the system
predefined data from utilities
Our initial
perspective

4. Seller service
HH
tariff
PowerMeter
owner service
00115.637
kWh
alarm
events
teleinfo from
power meter
Domotic networks
Other’s service
Smart
Home
A simple
example
HH tariff service cooperates with Smart Home service
Users do’nt have to bother !

5. Power
Meter
Owner
CUSTOMER
Smart
HOME
Power
Meter
Owner
Consum.
per
Usage
HH
Tariff
Seller
Appliance
installer
Validated
data
Validated
data
Validated device driving
Tariff
alarms
Consumption
alarms
Pricing Uses
Automation Maintenance
(different price / differing usage)
Generalisation
The @HOMium
implies also many B to B interactions !

6. 2 implementation bundles
- Serial Meter (RS232 port)
- PseudoMeter (simulation)
EURIDIS Bundle
for the basic services
and interfaces definition
Others : basic test bundles
EURIDIS
project
The power meter owner will provide
the basic power metering services !
000115.637
kWh
EURIDIS TELEINFO
Serial port : 1200 bauds
1 data frame per sec.

7. EURIDIS
packages
Services Interfaces

8. Subscribing to DataService
the client gets all the data
from a DataListener through the Data interface
the Meter interface is for the implementations
of various power-meters and simulations
The Data
Service
Services Interfaces

9. The Data
Service
package fr.edf.euridis.services ;
public interface DataService {
public void addDataListener(DataListener dl) ;
public void removeDataListener(DataListener dl) ;
}
package fr.edf.euridis.interfaces ;
public interface DataListener {
public void available(Data d) ;
}
New data frame arrived available(Data d)

10. Subscribing to WarpService
the client gets data around an event of interest
from a WarpListener for a GivenWarp
this service is generically implemented in the Warp, Weft
and Loom classes of fr.edf.euridis.implement
The Warp
service
Services Interfaces

11. package fr.edf.euridis.services ;
public interface WarpService {
public GivenWarp add(int past,int future) ;
public void remove(GivenWarp gw) ;
}
The Warp
service
past data future data
Event of interest
startRecording( )
available(Data[ ] past,Data[ ] future)
recording( ) TRUE

12. package fr.edf.euridis.services ;
public interface GivenWarp {
public void addWarpListener(WarpListener wl) ;
public void removeWarpListener(WarpListener wl) ;
public void startRecording( ) ;
public boolean recording( ) ;
}
package fr.edf.euridis.interfaces ;
public interface WarpListener {
public void available(Data[ ] past,Data[ ] future) ;
}
The Warp
service

13. The events of interest could be simple metering events,
like tariff change, overshot detection, etc.
With every Watcher service goes a listener type
interface for the client. It may start a given warp…
metering
events
Services Interfaces

14. two client configurable events are defined for
- load management client applications,
- per use consumption evaluations etc.
Their configuration follows the same model as the Warp
service, with GivenLoad and GivenUse specs.
configurable
events
Services Interfaces

15. firstOn( )
confirmedOn( )
firstOff( )
confirmedOff( )
LOAD
constance
constance
load
events
The LoadListeners « hear » four different types of events :

16. USE
variance
constance
firstUp( )
confirmedUp( ) USE
firstDown( )
variance
confirmedDown( )
constance
use
events
The UseListeners « hear » four different types of events :

17. package fr.edf.overshotClient.implement ;
public class RecordOvershot implements OvershotDetection {
private GivenWarp w ;
public RecordOvershot( GivenWarp gw ) { w = gw ; }
public void triggered(int overAmp) {
System.out.println("Overshot of "
+ String.valueOf(overAmp)
+ " A detected") ;
if (! w.recording( ))
w.startRecording( ) ;
}
}
Overshot
client

18. package fr.edf.overshotClient.implement ;
public class LogOvershot implements WarpListener {
public void available(Data[ ] before, Data[ ] after) {
if (before != null) {
System.out.println(String.valueOf(before.length)
+" samples before the overshot") ;
}
if (after != null) {
System.out.println(String.valueOf(after.length)
+" samples after the overshot") ;
}
}
}
Overshot
client

19. Conclusions
Successful services will be REAL TIME
They will be immediately responsive to all kinds of signals
and also to the perturbative customer (who will not be bothered)
The service providers community will
dynamically manage rich local resources
The services running in the gateways
will also cooperate (B to B interactions)
To achieve this, they will have to support a common standard
tailored as a model of services : current best fit, OSGi !
In order to optimize the use of servers and access resources
thus promoting cheaper offers to more potential customers

20. Questions?