1. ISO/IEC WD 18012-3-X Guidelines for product interoperability – Part 3-x: Community interface application model 2012. 9. 10. Ho-Jin Park ETRI, Korea 1 SC25 WG1-N1575

2. Contents 1.Introduction 2.HES Interoperability Framework 3.The proposed Application Interoperability Model 4.Outline of the WD 2

3. Introduction(1/2) 3 The community service is a shared service at the complex level –Collective residence such as apartment, mixed use building, etc. For the community service, the community system should be installed inside the complex –requires an interface with the HES Community System HES CCTV monitoring Elevator stop request Lobby door control Vehicle location guide Complex Network Parking notificationCommunity announcement GatewayMonitor Remote utility metering Community Service

4. Introduction(2/2) 4 Dev UPnP Knx Echonet HES Gateway Community System Ethernet How to provide an interoperability between community interface protocols and home network protocols? –Various kinds of community interface protocols according to the vendors –Multiple HES protocol standards such as UPnP, Knx, Echonet, etc. Community Interface Protocols A, B, C… HES Protocols A’, B’, C’…

5. HES Interoperability Method ISO/IEC 14543-3 (KNX) ISO/IEC 14543-4 (Echonet) ISO/IEC 14908 (LonTalk) WiBEEM Wireless Protocol ISO/IEC 29341 (UPnP) Interoperability Domain ISO/IEC HES Standard Protocols Full Mash Translation vs. Generic Translation W L E K U ? ? ? W L E K U ? ? ? Generic Interface ?? 5

6. HES Interoperability Framework ISO/IEC 18012-2 ISO/IEC 14543-3 (KNX) ISO/IEC 14543-4 (Echonet) ISO/IEC 14908 (LonTalk) WiBEEM Wireless Protocol ISO/IEC 29341 (UPnP) Application Level Layer 1-7 HES Interoperability Framework ISO/IEC 18012-2 Interoperability Object Interoperability Object Generic Interface (Interoperability Event Bus) Interoperability Domain IWF 6

7. The Proposed Application Interoperability Model ISO/IEC 14543-3 (KNX) ISO/IEC 14543-4 (Echonet) ISO/IEC 14908 (LonTalk) WiBEEM Wireless Protocol ISO/IEC 29341 (UPnP) Application Level Layer 1-7 HES Interoperability Framework ISO/IEC 18012-2 CommunityServceClient Object CommunityServceServer Object Generic Interface (Interoperability Event Bus) Community interface application model ISO/IEC 18012-3-X IWF A IWF B Community Intf. Protocol A Community Intf. Protocol B Outside the home (smart devices) Inside the home (HES devices) 7

8. Scope Addresses the application interoperability model based on ISO/IEC 18012-2 the community system and the HES for the community service. –ISO/IEC 18012-2 addresses basic taxonomy and application model aspects related to the operational mode of interoperable HESs. Defines the application objects needed to support the service, and describes the interrelationship among those objects. –The use cases of the generally available community service are listed. –To support those services, events and their flows for command, status report or data, which are exchanged among the application objects of the application interoperability model, are defined. 8

9. Specifications(1/3) 9 Application interoperability model Object1 CommunityServiceServer Object 2 CommunityServiceClient Community Network HES Network Interoperability Domain Community Interface Application System A Community System System B User Interface Object 1 event/data logical bus Object 2 Standardized event passing interface for “Interworking functions” System A IWF System B IWF

10. Specifications(2/3) Use cases –Logging in and obtaining initial data –Opening the lobby door of a residential building –Obtaining remote utility metering data –Monitoring CCTV video –Elevator boarding request –Parked vehicle location guide –Parking notification –Parcel delivery notification –Community announcements For each use case, the followings are specified; –Events exchanged between the application objects through the event bus –Parameters included in each event –The event flow 10

11. Event Name (Event ID) Parameter(s)DataDescriptionExample ElevatorBoardRes p (02050002) ElevatorInfo FloorCurrent floor5 SectionElevator No.3 DirectionCurrent moving directionUp/Stop/Down StatusElevator operation status Normal/Out-of- order/Temporary- stopped ResultElevator operation resultMoving/Arrived Specifications(3/3) Example: use case ‘Elevator Boarding Request’ – Events & parameters included in each event –The event flow 11 Event Name (Event ID) Parameter(s)DataDescriptionExample ElevatorBoardReq (02050001) HomeInfo HomeID 14 bits ID =Complex(4)+Building(4)+Number(4) +Extension(2) 00001000100100 DirectionMoving directionUp/Stop