## 3 DSM Use Case
### Mapping of Use Case to SGAM Layers  
In this section we depict the mapping of the use case on the SGAM interoperability layers. Figure 4 shows a possible mapping of the Load Management Based on Demand Response/Demand Side Management Use Case at the Component Layer. It should be noted that the grey area at the graph indicates that the respective assets in the building/home may not be owned by the electricity service supplier, but by the customer. This scheme is not definite as Member State market models can vary. Figure 5 shows a possible mapping of the Load Management Based on Demand Response/Demand Side Management Use Case at the Business Layer. The diagram shows the areas which are affected by the use case and influenced by underlying business objectives. Figure 4: Component Layer. Figure 6 shows a possible mapping of the Load Management Based on Demand Response/Demand Side Management Use Case at the Function Layer. It represents functions which are derived from the use case by extracting its functionality. The step-by-step analysis provides the functions of the use case. Figure 5: Business Layer. Figure 7 shows a possible mapping of the Load Management Based on Demand Side Management/Demand Response Use Case at the Information Layer. It describes the information exchanged between actors. The standards identified are derived from references [7; 42]. Please note that the G2, C, M, H2 and H3 interfaces are the ones referred to in reference [42]. Several standards can be used for each of these interfaces. Table 3 shows the various options for the standards and the relevant interfaces. Figure 6: Function Layer. \begin{table}
\begin{tabular}{l} \hline \hline
**Interface G2—Standard(s) for Information layer** \\ \hline EN 62056-61: Electricity metering—Data exchange for meter reading, tariff and load control—Part 61: \\ Object Identification system \\ \hline EN 62056-62: Electricity metering—Data exchange for meter reading, tariff and load control—Part 62: \\ Interface classes \\ \hline
**Interfaces C, M—Standard(s) for Information layer** \\ \hline EN 62056: Electricity metering—Data exchange for meter reading, tariff and load control \\ \hline
**Interfaces H2, H3—Standard(s) for Information layer** \\ \hline EN 50090-3-3: Home and building electronics systems (HBES)—Part 3.3: Aspects of application—HBES \\ Interworking model and common HBES data types \\ \hline EN 14908: Open Data Communication in Building Automation, Controls and Building Management \\ \hline \hline \end{tabular}
\end{table} 
Table 3: Interfaces and standards for the information layer. Figure 7: Information Layer. For the link between the CEMS and the smart device and the link between CEMS and the HAED, no specific interface is defined in reference [42]. Therefore, it is left blank in the layer representation. In practice, standards like the ones mentioned for the H2 interface can be applied. It is considered that there is a non-smart appliance; therefore, it cannot support any information exchange. The Home Automation end-Device is the one that defines when the appliance will be on or off. There is no information exchange afterwards. Figure 8 shows a possible mapping of the Load Management Based on Demand Response/Demand Side Management Use Case at the Communication Layer. It presents the communication protocols for data exchange of the necessary information between the components. The standards identified are derived from references [7; 42]. Please note that the G2, C, M, H2 and H3 interfaces are the ones referred in reference [42]. Several technologies can be used for each of these interfaces. To be more specific, for interface G2, the technologies to be used can be the public cellular mobile network (GSM, GPRS, EDGE, UMTS),  
Figure 8: Communication Layer. For the link between the CEMS and the smart device and the link between CEMS and the HAED, no specific interface is defined in reference [42]. Therefore, it is left blank in the layer representation.