444 ◾ Slobodanka Tomic et al.
functionalities to acquire and reason on the user contexts. e rst functional-
ity includes access to the measured environmental conditions and device status,
as well as access to actuators for conguration and activation of functionalities.
e second contains a variety of interactive interfaces that allow a user to specify
his preferences to congure the management of resources in his environment or
receive the feedback of his actions. e third is the reasoning core that main-
tains context information and allows the system to make automatic decisions to
achieve the required actions.
e demand management environment intersects with the home environment at
the smart meter. is device has a special role, as it directly measures parameters of
the user context and operates under the exclusive access and control of the advanced
metering infrastructure (AMI) provider. We based our design on the availability of
complementary external Web information services that provide end customers with
relevant energy market information (types of available energy, taris, criteria for
selecting energy providers, etc.). We believe an innovative integration approach is
required to make energy awareness a genuine parameter of cost saving and energy
saving control within the home and demand management environments. e
application of ontology management to create an interoperable multienvironment
description will contribute to the pan-European vision of an “Internet of ings” as
part of the future Internet initiative (EU Future Internet 2009).
To achieve this vision, SESAME designs architecture that brings together
advanced service infrastructure, ontology and policy infrastructure, and context
and policy-based reasoning. e central element is an extended ontology for the
home and demand management environments that includes a model of ener-
gy-related entities, parameters, and situations; energy management and usage
Smart
meter
Smart metering
and
energy services
Gateway and
universal control
box
Home automation
and energy Services
Figure 16.1 SESAME system overview.
Semantics for Energy Efficiency in Smart Home Environments ◾ 445
policies; and complementing ontologies describing home environment controls.
e overall model enables automatic activation of services that encapsulate dif-
ferent interactions including data harvesting, actuator-based control, and interac-
tions with users. Components of SESAME’s integrated architecture are illustrated
in Figure16.2.
Smart
concentrator
Energy utility
Energy
suppliers
Web/Mobile
clients
UCB
WAN/Internet interfaces
Firewall
WebFilter
Web Interfaces
(Web App and services)
Web Client Smart Display Client
Service layer
Prediction
Semantics & Multi-
Objective reasoning
Data layer (Permanent storage)
Notification Interfaces
HAN interfaces
SESAME logic interfaces
Configuration
Interfaces
Data reading
Interfaces
Control
Interfaces
Sys. Update
Interfaces
Permanent storage
Service layer
Driver layer
Physical communication interfaces
Ambient
light
sensor
CO
2
sensor
Electric
actuator
Heat
sensor
Humidity
sensor
HVAC
control
Occupancy
sensor
Smart
electric plug
PLC WiredM-Bus BluetoothZigbee
System Update Comm.
Interfaces
TCP/IP
Authentication, authorization
VPN access
Content and application publishing
UCB
manufacturer
Figure 16.2 SESAME system architecture.
446 ◾ Slobodanka Tomic et al.
Services within the SESAME architecture provide dierent functionalities
at dierent interfaces. For example, smart meter data is published by the AMI
provider through an external SOAP-based Web service. On the same side of
SESAME, the Web service client invokes this service and updates the knowl-
edge base. Sensors, appliances, and displays are also implemented as service-based
information publishers and consumers. As a home automation system is inher-
ently an event-based system, each service interface also implements a notication
passing capability for service-based interactions of users and energy providers or
grid operators.
e SESAME service architecture is based on the OSGI. To account for
dynamic changes in the environment and user expectations, SESAME designs
exible life-cycle management of ontologies and services. is provides means for
dealing with dynamic additions of new system components (new types of devices)
or adding a new user policy or workow, a new energy provider, or a new home.
e system allows “plug-in” ontologies and ontology evolution and selection driven
by user needs.
16.4.3 Ontology Design
SESAME uses an ontology-based modeling approach to describe an energy-aware
home and the relationships of the objects and actors within its control scenario. e
SESAME ontology provides a hierarchy of concepts to model the automation and
energy domains and is specied in OWL. e main components are the automa-
tion ontology, meter data ontology, and pricing ontology.
SESAME Automation Ontology (Figure16.3) includes a number of general
concepts such as Resident and Location, and concepts in the automation and in
the energy domain, such as Device, and Conguration. e Device class has sub-
classes modeling Appliances, Sensors, or simple message-based User Interface (UI)
devices. New energy-related properties in the Device model are consumption per
hour, peak power, and the switch on/o status as well as the required state “to be
switched on/o.” For an Appliance, we also introduce the property “canBeStarted”
which models the state of the devices for which activation can be scheduled. For
example, after a user lls in his washing machine he congures it (via a new UI)
with the “canBeStarted” set to “true,” and with the time interval within which the
washing task should be accomplished.
To model dierent types of control functionality, the SESAME ontology intro-
duces the Conguration class, which has two subclasses: Activity (or automation
activity) and EnergyPolicy. An Activity connects Appliance, Sensor, and UI Device
into a joint task. A ContextBased Activity can provide regulation of dierent types,
e.g., regulation on time, occupancy of location, or threshold value. For this pur-
pose it includes properties including thresholds and scheduled times. An example
of a ContextBased Activity would be HeatingRegulationBedroom which would
connect TemperatureSensor in the Bedroom and Heater. is Activity would be
Semantics for Energy Efficiency in Smart Home Environments ◾ 447
congured as regulatesOnreshold, and hasresholdSwitchOn and hasresh-
oldSwitchO would be set to 20° and 23°C, respectively.
Figure 16.3 also shows how the Automation Ontology links to the Meter
Data Ontology (through the Meter class) and to the Pricing Ontology (through
TariModel and Provider classes).
SESAME meter data ontology—is ontology (Figure16.4) is based on the
DLMS standard (2009) for meter data modeling. e DLMS/COSEM specica-
tion denes a data model and communication protocols for data exchange with
metering equipment.
A set of interface classes (register, activity calendar, clock) and a set of instances
of these classes enable the meter to act as a server and publish its data to utili-
ties, customers, or providers that can access the meter data as clients. A published
measured object has a unique OBIS code consisting of six numbers. OBIS naming
Automation
Context
Device
Location
subclassOf
subclassOf
Resident
subcalssOf
Energy Context
hasAutomationContext
Sensor
Appliance
subcalssOf
hasEnergyContext
Profile
subclassOf
Provider
Account
UIDevice
subcalssOf
UIDeviceInConfiguration
ApplianceInConfiguration
SensorInConfiguration
containsLocation
Humidity
Sensor
Temperature
Sensor
Illumination
Sensor
Presence
Sensor
subcalssOf
subcalssOf
subcalssOf
detectsPresenceOfResident
hasLocation
TariffModel
subclassOf
subclassOf
providesAccount
providesTariff
hasLocation
ContextBased
Interruptable
Schedulable
subcalssOfEnergyPolicy
Meter
subcalssOf
subcalssOf
subcalssOf
subcalssOf
subcalssOf
regulatesOnreshold
Location
regulatesInverseOnreshold
regulatesOnOccupancy
- hasLocation
- hasID
- hasName
- hasScheduledBegining
- hasScheduledEnd
- shallFinishBefore
- shallStartAfter
- canBeStartd
- consumesPH
- hasPeekPower
- hasReading
- hasTimeStamp
- hasMessage
- hasTimeStamp
- hasHumidity
- hasIllumination
- hasTemperature
- isOccupied
- hasID
- hasName
- hasID
- hasName
hasProfile
hasTariff
hasAccount
- hasresholdSwitchOff
- hasresholdSwitchOn
- regulatesOnConsumption
- regulatesOnPeekPower
- regulatesOnTime
- hasID
- hasName
*
*
Configuration
- hasPreferenceWeight
- isActive
Activity
- hasSwitchOffTime
- hasSwitchOnTime
- isSwitchedOn
- isSwitchedOff
- isToBeSwitchedOn
- isToBeSwitchedOff
- switchOn
- switchOff
- manualOverrule
- manualOnly
- hasActivityTimeWindowStart
- hasActivityTimeWindowEnd
- hasActivityFixTimeStart
- hasActivityFixTimeStart
- hasActivityDuration
subcalssOf
Figure 16.3 SESAME automation ontology.
448 ◾ Slobodanka Tomic et al.
is used in logical name (LN) referencing. For a specic implementation of OBIS
convention on a specic meter, a manufacturer must specify the objects supported
and their OBIS codes.
As shown in Figure16.4, stored data is of three major types, and every type
provides dierent information. For example, the register keeps all data about
active and reactive (+/–) current average power, active and reactive (+/–) energy,
voltage, current, THD, cos φ, and active and reactive (+/–) maximum power for
a dened period. Conguration data relates to meter status, status of all mea-
sured data, last and calibration date. e clock keeps information about time
and meter time parameters. Since data can be stored on the meter in log objects
(15-minute, daily, or monthly basis), they are also modeled in the ontology. Every
object has a unique OBIS code that accompanies the description of what the
object measures.
SESAME pricing ontology—is ontology (Figure16.5) captures the con-
cept of making energy-aware decisions and selecting an optimal tari model for a
specied time and energy load based on certain classes. SelectionCriteriaPonders is
Time
- MeasuredValue (float)
- Scaler (int)
- Unit (int)
- TimeOnMeter (datetime)
- TimeZone (int)
- Status (string)
- DayLightSavingsEnabled (bool)
Register
Clock
Data
isPartOf
DataLog
- TimeStamp (datetime)
- EntriesCount (int)
- MaxEntriesCount (int)
Resident
- OBIS_Code
- Description
- ClassName
subclassOf
subclassOf
- TimeStamp (datetime)
- DataStatus (int)
hasldentificator
SystemObjectIdentificator
hasIdentificator
subclassOf
measuredBy
Meter
storedBy
livesInformation
givesInformation
- UniqueID (long)
- SerialNumber (string)
- CaliburationDate (datetime)
- MeterTypeName (string)
- Data (String)
InformationType
givesInformation
Measured ValuesConfigurationData
ConfigurationData
isMeasuringFor
Figure 16.4 SESAME meter data ontology.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.