01.12.2012 Views

Architecture of Computing Systems (Lecture Notes in Computer ...

Architecture of Computing Systems (Lecture Notes in Computer ...

Architecture of Computing Systems (Lecture Notes in Computer ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

158 B. Becker et al.<br />

freedom like wash<strong>in</strong>g mach<strong>in</strong>es or thermal storages can be re-scheduled several<br />

times <strong>in</strong> compliance with its local constra<strong>in</strong>ts. A stove or a multimedia device,<br />

on the other hand, has an extremely poor degree <strong>of</strong> freedom, so their demand<br />

pr<strong>of</strong>ile can be observed, but there is no possibility <strong>of</strong> re-schedul<strong>in</strong>g the operation.<br />

In our scenario, the degree <strong>of</strong> freedom is determ<strong>in</strong>ed by each appliance or<br />

by the smart-home’s resident us<strong>in</strong>g the web-<strong>in</strong>terface. Some appliances have to<br />

execute a specific program before they can be switched <strong>of</strong>f. Thus, the specific<br />

pr<strong>of</strong>ile for these appliances must be respected <strong>in</strong> the SHMD while generat<strong>in</strong>g the<br />

re-schedul<strong>in</strong>g <strong>of</strong> the appliances. Therefore, the local controller <strong>of</strong> each appliance<br />

has a set <strong>of</strong> static rules. The decision to change the operation state depends on<br />

these rules comb<strong>in</strong>ed with the rule set from the SHMD.<br />

5.2 Central Observer<br />

The smart-home’s observer unit captures power changes for each <strong>in</strong>telligent appliance,<br />

the charge condition <strong>of</strong> the electric vehicle’s battery, the devices’ degree<br />

<strong>of</strong> freedom, and the known device pr<strong>of</strong>iles. The latter is received from the <strong>in</strong>telligent<br />

appliance itself or calculated from the past power data. The whole set <strong>of</strong><br />

values is stored <strong>in</strong> the SHMD’s database. Reduced to the essential, the database<br />

conta<strong>in</strong>s a list <strong>of</strong> the attributed set <strong>of</strong> <strong>in</strong>telligent appliances and the data history<br />

<strong>of</strong> the power demand for each <strong>of</strong> them.<br />

Us<strong>in</strong>g a sufficient quantity <strong>of</strong> history data, it is possible to build a prediction,<br />

described <strong>in</strong> Fig. 4, for each day <strong>of</strong> the week. The history items are classified <strong>in</strong><br />

data sets by the day <strong>of</strong> week and a certa<strong>in</strong> timeslot. An appropriate data structure<br />

is a tree conta<strong>in</strong><strong>in</strong>g for each <strong>in</strong>telligent appliance a node on the first level.<br />

Each <strong>of</strong> these nodes branches <strong>in</strong>to seven nodes on the second level, represent<strong>in</strong>g<br />

the seven days <strong>of</strong> the week. The weekday node has subnodes for a fixed set <strong>of</strong><br />

timeslots (e. g., blocks à 5 m<strong>in</strong>utes) <strong>of</strong> the day. F<strong>in</strong>ally, every data set from the<br />

<strong>in</strong>telligent appliances’s history is associated to one <strong>of</strong> the timeslot nodes.<br />

This part’s challenge is to get timeslots, where an appliance is frequently<br />

switched on. Each timeslot is represented by the correspond<strong>in</strong>g daytime and<br />

weekday. To f<strong>in</strong>d these frequent item sets <strong>in</strong> the tree structure, the timeslot<br />

nodes can be easily scanned for such nodes hav<strong>in</strong>g more than a certa<strong>in</strong> number <strong>of</strong><br />

leaves <strong>in</strong> the tree. Hav<strong>in</strong>g found these timeslots, it is obvious that the associated<br />

device will probably be powered up on the same weekday’s timeslot dur<strong>in</strong>g the<br />

next weeks. To <strong>in</strong>crease the rate <strong>of</strong> adaption a digressive weight<strong>in</strong>g depend<strong>in</strong>g<br />

on the items’ age is used. Furthermore, this knowledge can be transformed <strong>in</strong>to<br />

a power forecast for each <strong>in</strong>telligent appliance for the next days.<br />

5.3 Central Controller<br />

Revert<strong>in</strong>g to an extensive pool <strong>of</strong> data collected by the observer <strong>of</strong> the SHMD,<br />

the ma<strong>in</strong> controller’s basic task is to send adequate rule sets to the subord<strong>in</strong>ated<br />

local controllers <strong>of</strong> the <strong>in</strong>telligent appliances. The f<strong>in</strong>al decision is made by the<br />

<strong>in</strong>telligent appliance’s controller, but it should be mostly consistent with the rule<br />

sets <strong>of</strong> the ma<strong>in</strong> controller. To simplify our <strong>in</strong>itial approach to the smart-home

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!