{"title":"Service Abstraction Layer for Building Operating Systems: Enabling portable applications and improving system resilience","authors":"Jakob Hviid, M. Kjærgaard","doi":"10.1109/SmartGridComm.2018.8587543","DOIUrl":null,"url":null,"abstract":"For large scale implementation of Demand Response programs, applications enabling Demand Response would need to be portable between buildings. Building Operating Systems are an essential strategic piece for enabling portable applications, which work with several hardware implementations from different vendors. These building operating systems can effectively be used to implement large-scale Demand Response implementations. Currently, though, the service layer of building operating systems requires direct integration with specific services, and thereby have requirements for specific implementations of services to be present in a specific building. This paper proposes the introduction of a Service Abstraction Layer to decouple the application from the specific implementations of services, as well as to introduce the concept of redundancy in service responsibility areas. These changes would allow for application portability between buildings but also allow for building operating system resiliency.A prototype abstraction layer is implemented and tested. Results show the introduction of a Service Abstraction Layer has promising benefits for building operating systems, and successfully decouples the applications from the building operating system implementation, as well as improving system reliability and resiliency. For smart grid applications, the addition of a service abstraction layer allows for large-scale portable applications, but would still require some form of standardization of communication protocols for different service types.","PeriodicalId":213523,"journal":{"name":"2018 IEEE International Conference on Communications, Control, and Computing Technologies for Smart Grids (SmartGridComm)","volume":"4 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2018-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"6","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2018 IEEE International Conference on Communications, Control, and Computing Technologies for Smart Grids (SmartGridComm)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SmartGridComm.2018.8587543","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 6
Abstract
For large scale implementation of Demand Response programs, applications enabling Demand Response would need to be portable between buildings. Building Operating Systems are an essential strategic piece for enabling portable applications, which work with several hardware implementations from different vendors. These building operating systems can effectively be used to implement large-scale Demand Response implementations. Currently, though, the service layer of building operating systems requires direct integration with specific services, and thereby have requirements for specific implementations of services to be present in a specific building. This paper proposes the introduction of a Service Abstraction Layer to decouple the application from the specific implementations of services, as well as to introduce the concept of redundancy in service responsibility areas. These changes would allow for application portability between buildings but also allow for building operating system resiliency.A prototype abstraction layer is implemented and tested. Results show the introduction of a Service Abstraction Layer has promising benefits for building operating systems, and successfully decouples the applications from the building operating system implementation, as well as improving system reliability and resiliency. For smart grid applications, the addition of a service abstraction layer allows for large-scale portable applications, but would still require some form of standardization of communication protocols for different service types.