Transcript Introduction to ISO/IEC software engineering standards

SC25 WG1-N1575
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
Contents
1. Introduction
2. HES Interoperability Framework
3. The proposed Application Interoperability Model
4. Outline of the WD
2
Introduction(1/2)
• 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 Service
Lobby door control
Remote utility metering
Complex
Network
CCTV monitoring
Elevator stop request
Vehicle location guide
Parking notification
Community announcement
Gateway
Community
System
Monitor
HES
3
Introduction(2/2)
• 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.
Ethernet
HES
Gateway
Dev
UPnP
Knx
Dev
Echonet Dev
Community System
Community Interface Protocols
A, B, C…
HES Protocols
A’, B’, C’…
4
HES Interoperability Method
Full Mash Translation vs. Generic Translation
W
Interoperability
Domain
W
L
?
L
E
?
E
K
?
U
Generic
Interface
?
?
K
?
?
?
ISO/IEC
29341
(UPnP)
WiBEEM
Wireless
Protocol
ISO/IEC
14908
(LonTalk)
ISO/IEC
14543-4
(Echonet)
ISO/IEC
14543-3
(KNX)
ISO/IEC
HES Standard
Protocols
U
5
HES Interoperability Framework
ISO/IEC 18012-2
HES Interoperability Framework
ISO/IEC 18012-2
Interoperability Domain
Generic Interface
(Interoperability Event Bus)
Application
Level
Interoperability
Object
Interoperability
Object
IWF
IWF
ISO/IEC
29341
(UPnP)
WiBEEM
Wireless
Protocol
ISO/IEC
14908
(LonTalk)
ISO/IEC
14543-4
(Echonet)
ISO/IEC
14543-3
(KNX)
Layer 1-7
6
The Proposed Application
Interoperability Model
HES Interoperability Framework
ISO/IEC 18012-2
Community interface application model
ISO/IEC 18012-3-X
Generic Interface
(Interoperability Event Bus)
Application
Level
CommunityServceClient
Object
CommunityServceServer
Object
IWF B
IWF A
Community Intf.
Protocol
B
Community Intf.
Protocol
A
ISO/IEC
29341
(UPnP)
Inside the home
(HES devices)
WiBEEM
Wireless
Protocol
ISO/IEC
14908
(LonTalk)
ISO/IEC
14543-4
(Echonet)
ISO/IEC
14543-3
(KNX)
Layer 1-7
Outside the home
(smart devices)
7
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
Specifications(1/3)
• Application interoperability model
Interoperability Domain
Community Interface Application
Object 2
Object 1
event/data logical bus
Standardized event passing
interface for “Interworking
functions”
System A IWF
Object1
CommunityServiceServer
System A
Community
System
System B IWF
Object 2
CommunityServiceClient
System B
User Interface
Community Network
HES Network
9
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
Specifications(3/3)
• Example: use case ‘Elevator Boarding Request’
–
Events & parameters included in each event
Event Name
(Event ID)
Parameter(s)
ElevatorBoardReq
Event Name
(02050001)
(Event ID)
HomeInfo
Parameter(s)
ElevatorBoardResp
(02050002)
ElevatorInfo
Data
Description
HomeID
Data
Direction
Floor
Section
Direction
14 bits ID
=Complex(4)+Building(4)+Number(4
)+Extension(2)
Description
Moving direction
Current floor
Elevator No.
Current moving direction
Status
Elevator operation status
Result
Elevator operation result
Example
00001000100100
Example
Up/Stop
5
3
Up/Stop/Down
Normal/Out-oforder/Temporarystopped
Moving/Arrived
– The event flow
Object1:
CommunitySer
viceServer
Event Bus
Object2:
CommunitySer
viceClient
ElevatorBoardReq
ElevatorBoardResp
11