14543-x-y  WD ISO/IEC:2013
–1–
SC25 WG1 N1633
INFORMATION TECHNOLOGY HOME ELECTRONIC SYSTEM (HES) ARCHITECTURE-
1
2
3
4
5
Part 4-3: Communication layers – OPEN Web Net - application layer for
network enhanced control devices of HES Class 1
6
FOREWARD
7
8
9
10
11
12
1)
ISO (International Organization for Standardization) and IEC (International Electrotechnical Commission) form the
specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the
development of International Standards. Their preparation is entrusted to technical committees; any ISO and IEC
member body interested in the subject dealt with may participate in this preparatory work. International governmental
and non-governmental organizations liaising with ISO and IEC also participate in this preparation.
13
14
15
2)
In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote.
16
17
18
3)
The formal decisions or agreements of IEC and ISO on technical matters express, as nearly as possible, an
international consensus of opinion on the relevant subjects since each technical committee has representation from
all interested IEC and ISO member bodies.
19
20
21
22
4)
IEC, ISO and ISO/IEC publications have the form of recommendations for international use and are accepted by IEC
and ISO member bodies in that sense. While all reasonable efforts are made to ensure that the technical content of
IEC, ISO and ISO/IEC publications is accurate, IEC or ISO cannot be held responsible for the way in which they are
used or for any misinterpretation by any end user.
23
24
25
26
5)
In order to promote international uniformity, IEC and ISO member bodies undertake to apply IEC, ISO and
ISO/IEC publications transparently to the maximum extent possible in their national and regional publications. Any
divergence between any ISO/IEC publication and the corresponding nati onal or regional publication should be clearly
indicated in the latter.
27
28
6)
ISO and IEC provide no marking procedure to indicate their approval and cannot be rendered responsible for any
equipment declared to be in conformity with an ISO/IEC publication.
29
7)
All users should ensure that they have the latest edition of this publication.
30
31
32
33
34
8)
No liability shall attach to IEC or ISO or its directors, employees, servants or agents including individual experts and
members of their technical committees and IEC or ISO member b odies for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses
arising out of the publication of, use of, or reliance upon, this ISO/IEC publication or a ny other IEC, ISO or ISO/IEC
publications.
35
36
9)
Attention is drawn to the normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
37
38
10) Attention is drawn to the possibility that some of the elements of this International Standard may be the subject of
patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
39
40
41
This working draft 14543-x-y was prepared by subcommittee xx: Interconnection of information
technology equipment, of ISO/IEC joint technical committee yy: Information technology.
42
43
44
The list of all currently available parts of the ISO/IEC 14543 series, under the general title
Information technology - Home electronic system (HES) architecture, can be found on the IEC
web site and ISO web site.
45
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
14543-x-y  WD ISO/IEC:2013
–2–
SC25 WG1 N1633
46
47
INTRODUCTION
48
49
This part of ISO/IEC 14543 specifies the protocol of the application layer for usage in Home
Electronic System. This document is based on OPEN Web Net protocol
50
51
ISO/IEC 14543 Information technology - Home Electronic System (HES) architecture, currently
consists of 14 parts:
52
Part 2-1: Introduction and device modularity
53
Part 3-1: Communication layers - Application layer for network based control of HES Class 1
54
55
Part 3-2: Communication layers - Transport, network and general parts of data link layer for
network based control of HES Class 1
56
Part 3-3: User process for network based control of HES Cl ass 1
57
58
Part 3-4: System management - Management procedures for network based control of HES
Class 1
59
60
Part 3-5: Media and media dependent layers - Powerline for network based control of HES Class
1
61
62
Part 3-6: Media and media dependent layers - Twisted pair for network based control of HES
Class 1
63
64
Part 3-7: Media and media dependent layers - Radio frequency for network based control of HES
Class 1
65
66
Part 3-10: Wireless Short-Packet (WSP) protocol optimized for energy harvesting -- Architecture
and lower layer protocols
67
Part 4: Home and building automation in a mixed -use building (technical report)
68
69
Part 4-1: Communication layers - Application layer for network enhanced control devices of HES
Class 1
70
71
Part 4-2: Communication layers - Transport, network and general parts of data link layer for
network enhanced control devices of HES Class 1
72
73
Part 4-3: Communication layers - ECHONET Lite - application layer light version for network
enhanced control devices of HES Class 1 (this standard)
74
75
Part x-y: Communication layers – OPEN Web Net - application layer for network enhanced
control devices of HES Class 1
76
Part 5-1: Intelligent grouping and resource sharing for HES Class 2 and Class 3 - Core protocol
77
78
Part 5-3: Intelligent grouping and resource sharing for HES Class 2 and Cla ss 3 -- Basic
application
79
80
Part 5-4: Intelligent grouping and resource sharing for HES Class 2 and Class 3 -- Device
validation
81
Part 5-5: Intelligent grouping and resource sharing for HES Class 2 and Class 3 -- Device type
14543-x-y  WD ISO/IEC:2013
–3–
SC25 WG1 N1633
82
Part 5-6: Intelligent grouping and resource sharing for HES Class 2 and Class 3 -- Service type
83
84
Part 5-21: Intelligent grouping and resource sharing for HES Class 2 and Class 3 -- Application
profile -- AV profile
85
86
Part 5-22: Intelligent grouping and resource sharing for HES Class 2 and Cla ss 3 -- Application
profile -- File profile
87
88
89
90
91
92
93
94
----------------------
14543-x-y  WD ISO/IEC:2013
95
96
97
98
99
–4–
SC25 WG1 N1633
INFORMATION TECHNOLOGY HOME ELECTRONIC SYSTEM (HES) ARCHITECTUREPart x-y: Communication layers - OPEN Web Net - application layer for
network enhanced control devices of HES Class 1
100
1 Scope
101
102
This part of the ISO/IEC 14543 specifies the protocol of the application layer for usage in
network enhanced home electronic system Class 1.
103
104
105
2 Normative references
106
107
108
The following referenced documents are mandatory for the application of this document. For
dated references, only the specifically mentioned editions apply. For undated references, the
latest edition of the referenced document (including any amendments) applies.
109
110
ISO/IEC 14543-2-1, Information technology - Home electronic system (HES) architecture - Part
2-1: Introduction and device modularity
111
112
113
3 Terms, definitions and abbreviations
114
115
116
3.1 Terms and definitions
For the purposes of this document the terms and definitions given in ISO/IEC 14543 -2-1 and the
following apply.
117
118
119
120
121
3.1.1
OPEN Web Net
Name of the communication protocol specified in this ISO/IEC 14543-x-y, the name stands for
Open Protocol for Electronic Networks
122
123
124
125
126
3.1.2
OPEN Web Net client
Client role, which is able to manage OPEN Web Net frames, typically played by management
systems in charge of controlling the whole set of plant functionality
127
128
129
130
131
3.1.3
OPEN Web Net server
Server role, which is able to manage OPEN Web Net frames, typically played by a plant gateway
device in charge of Ethernet vs. field bus mediation
14543-x-y  WD ISO/IEC:2013
–5–
132
133
3.2 Abbreviations
134
TCP
Transfer Control Protocol
135
IP
Internet Protocol
136
OPEN
Open Protocol for Electrical Networks
137
Open Web Net
OPEN Web Net
138
CSMA/CA
Carrier Sense Multiple Access with Collision Avoidance
139
PUL
Push button ...
140
Objects
Device objects
141
TODO
142
143
SC25 WG1 N1633
14543-x-y  WD ISO/IEC:2013
–6–
SC25 WG1 N1633
144
4 Conformance
145
For conformance to this International Standard the following applies.
146
147

Application layer protocol data unit shall conform to the specifications described in 6.2 and
6.4.
148
149

Application sessions shall conform to the specifications described in Error! Reference
source not found.3.
150
151
152
5 The application layer
153
5.1 Positioning in Communication Layers
154
155
156
OPEN Web Net Communication Processing Block is positioned in the Session, Presentation and
Application layers. In Error! Reference source not found., greyed area shows the OPEN Web
Net Block to be specified.
OSI
Layer
7
OPEN Client
OPEN Server
6
OPEN Web Net frame
management
5
OPEN Web Net session
management
4
3
2
1
157
158
159
Figure 1 – Involved stack layers
14543-x-y  WD ISO/IEC:2013
–7–
SC25 WG1 N1633
160
161
As shown in the picture above, the OPEN protocol is specified as a function independent on
Layers 1 to 4, hence also independent from the transmission channel.
162
OPEN protocol sends and receives OPEN frames specified in Clause 6.
163
164
There are two kinds of sessions: synchronous (command session specified in 6.4) and
asynchronous (event session specified in 6.5).
165
166
167
Both command and event connections start opening a TCP socket on port 20000 of the
destination address that is in layer 4 or lower, so there are not broadcast messages. For this
reason, Network device discovery is performed using proper protocols (i.e. UPnP discovery).
168
169
170
Security is not specified in the OPEN protocol. By applying any existing security standard
technologies in Layer 4 or lower as necessary, security of OPEN protocol is ensured
transparently.
171
172
173
6
174
175
176
177
6.1 Overview
This protocol is designed for application layer in order to establish connections among OPEN
Clients and OPEN Servers and to manage home and building automation devices.
178
179
6.2 Open Web Net communication Frame
An OPEN frame is composed only by characters belonging to the following collection:
Syntax of OPEN Web Net message / Application layer protocol data unit (APDU)
0
1
2
3
4
5
6
7
8
9
*
#
180
181
182
183
184



A frame starts with the character ‘*’
A frame ends with the couple of characters ‘##’.
The character ‘*’ is also used as a separator among tags that compose a frame.
An OPEN frame is structured in this way:
*tag1*tag2*tag3*...*tagN##
185
186
A tag is composed by characters belonging to this set:
0
1
2
3
4
5
6
7
8
187
188
189
190


A tag can’t contain the couple of characters ‘##’.
A tag may be omitted.
An Open frame with omitted tags is built in this way:
*tag1*..*..*tag4*...*tagN**##
191
9
#
14543-x-y  WD ISO/IEC:2013
192
193
194
195
196
197
198
199
200
201
202
203
204
205
–8–
SC25 WG1 N1633
6.3 Open Web Net Communication Sessions
OpenWebNet Gateways offer the OPEN Server on a well-known TCP-IP port number (20000).
There are four main phases to establish a working session between OPEN Client and Server:
1. Connection
2. Authentication ( Optional )
3. Identification
4. Communication
OPEN Server
OPEN Client
Connection
Choose the session kind
Communication
206
Figure 2 – main phases during connection between OPEN Client and Server
207
208
209
210
The authentication phase is optional and can be implemented to increase the safety level of
communication.
211
The identification phase is used to choose the typology of session.
212
Each OPEN Client can establish two different kinds of sessions versus an OPEN Sever:
213
214
215
216
217

Command Session (actions): used to send commands, status requests, dimension
requests and writing

Event Session: used by the OPEN Client to read all what happens on the home
automation system in an asynchronous way.
14543-x-y  WD ISO/IEC:2013
–9–
SC25 WG1 N1633
Command/Action
Session
OPEN
Server
218
219
OPEN
Client
Event
Session
Figure 3 – OPEN sessions between OPEN Client and Server
220
221
222
223
An OPEN Server has to be able to manage in parallels, at least, a given number of command
and event sessions depending on its own capabilities.
14543-x-y  WD ISO/IEC:2013
224
225
226
– 10 –
SC25 WG1 N1633
6.3.1 Command Session
After having established a TCP-IP connection between a Client and a Server, the
communication flow will be the following:
OPEN Server
OPEN Client
TCP/IP Connection
ACK
*99*0##
ACK
*1*1*77##
ACK
*1*1*22##
ACK
TCP/IP Connection Closure
227
228
Figure 4 – Example of Command Session
229
230
The OPEN Client sends a frame *99*0## to the OPEN Server in order to open a Command
session, then Client is able to send commands and receive back acknowledges (ACK/NACK).
231
232
If a Command session remains inactive for 30 seconds, it will be automatically closed by the
Server.
14543-x-y  WD ISO/IEC:2013
233
234
235
– 11 –
SC25 WG1 N1633
6.3.2 Event Session
After having established a TCP-IP connection between a Client and a Server, the
communication flow will be the following:
OPEN Server
OPEN Client
TCP/IP Connection
ACK
*99*1##
ACK
*1*1*12##
*1*0*13##
*2*0*32##
*1*1*44##
*1*1*88##
236
237
Figure 5 – Example of Event Session
238
239
240
The OPEN Client sends a frame *99*1## to the OPEN Server in order to open an Event
session, then the OPEN Server notifies the Client with events frames (unidirectional
communication flow).
241
Event Session terminates when client closes the TCP socket connection.
14543-x-y  WD ISO/IEC:2013
– 12 –
SC25 WG1 N1633
242
243
244
6.4 OPEN Web Net Messages
Table 1 shows the different kinds of messages that can be sent or received in a n OPEN ClientServer communication:
245
Table 1 - Kind of OPEN messages
ACK
*#*1##
NACK
*#*0##
COMMAND
STATUS REQUEST
DIMENSION REQUEST
DIMENSION WRITING
*WHO*WHAT*WHERE##
*#WHO*WHERE##
*#WHO*WHERE*DIMENSION##
*#WHO*WHERE*#DIMENSION*VAL1*VAL2*...*VALn##
246
247
248
249
6.4.1 Command / Status OPEN frame
The OPEN message that has this function is so structured:
*WHO*WHAT*WHERE##
250
251
This frame is used both in the action/commands session and in the events one.
252
253
254
255

Events session: indicates that a managed device has changed its status.

Commands / Actions session: message sent by the Server to the Client as response to
a status request; message sent by the Client to the Server to require an action execution.
256
257
Tag WHO:
258
259
The Tag WHO identifies the home automation system’s area involved by the OPEN frame
used.
260
261
Tag WHAT:
262
263
264
The tag WHAT identifies the action to make (ON lights, OFF lights, dimmer at 20%, shutters
UP, shutters DOWN, set program 1 in thermoregulation central, etc...) . For each WHO
(hence for every function) is described a WHAT table.
265
The WHAT tag can contain other parameters:
266
WHAT#PAR1#PAR2...#PARn
267
14543-x-y  WD ISO/IEC:2013
– 13 –
SC25 WG1 N1633
268
Tag WHERE:
269
270
The tag WHERE detects the objects involved by the frame (environment, room, single object,
whole system). For each WHO (and so for every function) is described a WHAT table.
271
The WHERE tag can contain other parameters
272
WHERE#PAR1#PAR2...#PARn
273
274
275
6.4.2 Status Request OPEN frame
Status request OPEN message is so structured:
*WHO*WHERE##
276
277
278
279
280
281
The Client sends this message in the Command/action session to require information on the
status of either a single object or the entire system. The Server replies to this request by
sending one or more Open status messages. The reply must end with an ACK or NACK
frame. If the field WHERE isn’t specified, the request is generic and sent to the whole
system.
282
283
284
6.4.3 Dimension Request OPEN frame
OPEN message to require the dimension is so structured:
*#WHO*WHERE*DIMENSION##
285
286
287
288
The client sends in the commands session to require information about the dimension value
of either one single object or an entire system. The server replies by sending one or more
Open status messages, so structured:
*#WHO*WHERE*DIMENSION*VAL1*...*VALn##
289
290
291
292
293
294
295
The number of VAL fields depends on the DIMENSION requested. The answer message is
followed by the ACK. If there is an error in the dimension request then a NACK frame will be
sent back. The reply message is generically sent even in the Events connections. The Open
Server forwards the dimension message if there are variation s on that dimension or simply if
the device has to signal periodically his dimension status (for example the thermo probe has
to communicate a value every 15 minutes).
296
297
298
6.4.4 Dimension writing OPEN frame
The OPEN message to write the dimension is so structured:
14543-x-y  WD ISO/IEC:2013
– 14 –
SC25 WG1 N1633
*#WHO*WHERE*DIMENSION*VAL1*...*VALn##
299
300
301
302
303
The message implies a modification only for the dimensions which can be modified. The
Client sends this message in the Commands/actions session to modify the dimension values
of a single object or the whole system. The Server will answer with an ACK or NACK
message.
304
305
306
307
6.4.5 ACK/NACK OPEN frames
In addition to the command messages there are special messages that will be sent during the
communication flow: ACK and NACK frames
308
ACK message
309
Acknowledgement OPEN message has the following syntax:
*#*1##
310
311
312
This frame indicates that the Open message, sent by the Client, or received by the Server, is
semantically and syntactically correct.
313
314
315
Furthermore it is used as an ended message when it is the answer to an Open frame which
involves the forwarding of one or more messages in sequence (status or dimension
requests).
316
NACK message
317
OPEN message for not-acknowledge (NACK) is:
*#*0##
318
319
320
321
322
323
324
This frame means that the Open message, sent by the Client to the Server, is semantically or
syntactically wrong. Furthermore, it is used as an ended message when it is the answer to an
Open frame which involves the forwarding of one or more messages in sequence (status or
dimension requests).In this case, the Client may consider invalid any messa ge received
before the NACK.
14543-x-y  WD ISO/IEC:2013
– 15 –
SC25 WG1 N1633
325
7
326
327
7.1 General
Basic sequences of OPEN frames can be divided into two main categories:
328
329
330
331
Basic sequence of OPEN Web Net frames


basic sequences for object start-up and configuration
basic sequences for object control
Since Open Web Net protocol commands can act on one or more building automation
devices at the same time, there are point-to-point commands and group commands.
332
333
334
335
7.2 Basic sequences for object start-up and configuration
Basic sequences for start-up are sequence of commands to be run at the first start -up of the
home automation network after the installation.
336
337
Basic sequences for object configuration are predefined sequence of commands to be
applied to each specific device according to user settings.
338
339
340
This chapter provides detailed specifications for the OPEN frames which implement the
Scene management, thus the automatically activation of a wide list of contemporaneous
actions at a specific time and date or triggered by precise events.
341
342
The following OPEN frames implement the Scene macros management (WHO = 0 SCENES) through proper Scenes Unit. (“Hard coded” and programmable scenes…)
343
Table 2 – WHAT for Scene management
344
What
Notes
What
Notes
1
Scene 1*
40#X
Start recording Scene X
2
Scene 2*
41#X
End recording Scene X
3
Scene 3*
42
Erase all the Scene X
4
Scene 4*
42#x
Erase Scene X
5
Scene 5*
43
Lock Scenes unit
…
…
44
Unlock Scenes unit
20
Scene 20*
45
Unavailable Scenes unit
…
…
46
Memory full of Scenes unit
345
346
347
348
349
Table 3 - WHERE for Scene management
14543-x-y  WD ISO/IEC:2013
– 16 –
SC25 WG1 N1633
Where
Notes
01
Scene Unit 01
02
Scene Unit 02
…
…
99
Scene Unit 99
…
…
350
351
352
Open messages: command session
-
Scene activation (WHAT 1, 2, … , 20)
Command session
Open frame
TCP/IP Client  Server
*0*WHAT*WHERE##
Notes
WHAT = Scene activated
WHERE: Scene Unit address
TCP/IP Client  Server
*#*1##
or
*#*0##
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
353
354
-
Start recording Scene (WHAT 40#1 - 40#20)
Command session
Open frame
Notes
X = Scene number
TCP/IP Client  Server
*0*40#X*WHERE##
WHERE: Scene Unit address
TCP/IP Client  Server
*#*1##
or
*#*0##
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
355
356
-
End recording Scene (WHAT 41#1 - 41#20)
Command session
Open frame
Notes
X = Scene Number
TCP/IP Client  Server
*0*41#X*WHERE##
WHERE: Scene Unit address
TCP/IP Client  Server
357
*#*1##
or
*#*0##
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
14543-x-y  WD ISO/IEC:2013
358
-
– 17 –
SC25 WG1 N1633
Erase all the Scene (WHAT 42)
Command session
TCP/IP Client  Server
Open frame
*0*42*WHERE##
*#*1##
or
*#*0##
TCP/IP Client  Server
Notes
WHERE: Scene Unit address
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
359
360
-
Erase a single Scene X (WHAT 42#1 - 42#20)
Command session
Open frame
Notes
X = Scene number
TCP/IP Client  Server
*0*42#X*WHERE##
WHERE: Scene Unit address
*#*1##
or
*#*0##
TCP/IP Client  Server
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
361
362
-
Lock Scene Unit (WHAT 43)
Command session
TCP/IP Client  Server
TCP/IP Client  Server
Open frame
*0*43*WHERE##
*#*1##
or
*#*0##
Notes
WHERE: Scene Unit address
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
363
364
-
Unlock Scene Unit (WHAT 44)
Command session
TCP/IP Client  Server
TCP/IP Client  Server
365
Open frame
*0*44*WHERE##
*#*1##
or
*#*0##
Notes
WHERE: Scene Unit address
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
14543-x-y  WD ISO/IEC:2013
366
367
– 18 –
SC25 WG1 N1633
Open messages: events sessions
-
Scene activated (WHAT 1-20)
Event session
Open frame
TCP/IP Server  Client
*0*WHAT*WHERE##
Notes
WHAT = Scene activated
WHERE: Scene Unit address
368
369
-
Start programming Scene (WHAT 40#1 - 40#20)
Event session
Open frame
TCP/IP Server  Client
*0*40#X*WHERE##
Notes
X = Scene number
WHERE: Scene Unit address
370
371
-
End programming Scene (WHAT 41#1 - 41#20)
Event session
Open frame
TCP/IP Server  Client
*0*41#X*WHERE##
Notes
X = Scene number
WHERE: Scene Unit address
372
373
-
Erase all the Scene (WHAT 42)
Event session
Open frame
TCP/IP Server  Client
*0*42*WHERE##
Notes
WHERE: Scene Unit address
374
375
-
Erase single scenario X (WHAT 42#1 - 42#20)
Event session
Open frame
TCP/IP Server  Client
*0*42#X*WHERE##
Notes
X = Scene number
WHERE: Scene Unit address
376
377
378
379
380
381
382
7.3 Basic sequences for global configuration
Open frames which implement the Scene scheduling through proper Scene high level SW
applications.
Is VC3 part of this document?
14543-x-y  WD ISO/IEC:2013
383
384
385
– 19 –
SC25 WG1 N1633
7.4 Basic sequences for Object control
Open frames which implement the lightning, automation, thermo … (how many WHOs should
be mentioned?)
386
387
388
7.4.1 Basic sequences for Lightning
Open frames that implement lightning management (WHO = 1 LIGHTNING)
389
390
Table 4 - WHAT (for Lighting)
What
Notes
What
Notes
0
OFF
16
ON timed 15 min
0#speed
OFF at x speed
17
ON timed 30 sec
1
ON
18
ON timed 0,5 sec
1#speed
ON at x speed
19
NO Load (only for dimmer)
2
20%
20
Blinking for 0,5 sec
3
30%
21
Blinking for 1 sec
4
40%
22
Blinking for 1,5 sec
5
50%
23
Blinking for 2 sec
6
60%
24
Blinking for 2,5 sec
7
70%
25
Blinking for 3 sec
8
80%
26
Blinking for 3,5 sec
9
90%
27
Blinking for 4 sec
10
100%
28
Blinking for 4,5 sec
11
ON timed 1 min
29
Blinking for 5 sec
12
ON timed 2 min
30
Up one level (only for dimmer)
13
ON timed 3 min
30#level#speed
Up y levels at x speed (only for dimmer)
14
ON timed 4 min
31
Down one level (only for dimmer)
15
ON timed 5 min
31#level#speed
Down y levels at x speed (only for dimmer)
391
392
Table 5 - WHERE (for Lighting)
Where
Notes
Where
Notes
0
General
…
…
1
Area 1
59
Light Point 59
…
…
61
Light Point 61
14543-x-y  WD ISO/IEC:2013
– 20 –
SC25 WG1 N1633
9
Area 9
62
Light Point 62
11
Light Point 11
…
…
12
Light Point 12
69
Light Point 69
…
…
71
Light Point 71
19
Light Point 19
…
…
21
Light Point 21
79
Light Point 79
22
Light Point 22
81
Light Point 81
…
…
82
Light Point 82
29
Light Point 29
…
…
31
Light Point 31
89
Light Point 89
32
Light Point 32
91
Light Point 91
…
…
92
Light Point 92
39
Light Point 39
…
…
41
Light Point 41
99
Light Point 99
42
Light Point 42
#1
Group 1
…
…
#2
Group 2
49
Light Point 49
…
…
51
Light Point 51
#256
Group 256
52
Light Point 52
393
394
Table 6 - DIMENSION (for Lighting )
Dimension
Notes
1
Set y level at x speed
2
Timers
395
396
397
Open messages: commands session
398
-
Light OFF command (WHAT 0)
Commands session
Open frame
TCP/IP Client  Server
*1*0*WHERE##
Notes
WHERE:
0
General command (every light
points in the system)
14543-x-y  WD ISO/IEC:2013
TCP/IP Client  Server
399
– 21 –
*#*1##
or
*#*0##
SC25 WG1 N1633
1-9
Area command (only light points
belonging to the specific Area)
#1 - #256
Group command (every light point
belonging to a specific group)
11 - …
Point to Point command
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
14543-x-y  WD ISO/IEC:2013
400
-
– 22 –
SC25 WG1 N1633
Switch ON light command (WHAT 1)
Commands session
Open frame
Notes
WHERE:
TCP/IP Client  Server
TCP/IP Client  Server
*1*1*WHERE##
*#*1##
or
*#*0##
0
General command (every light
points in the system)
1–9
Area command (only light points
belonging to the specific Area)
#1 - #256
Group command (every light point
belonging to a specific group)
11 – …
Point to Point command
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
401
402
-
Dimmer luminosity from 20% to 100% (WHAT 2-10)
Commands session
Open frame
Notes
WHERE:
TCP/IP Client  Server
TCP/IP Client  Server
0
General command (every light
points in the system)
1-9
Area command (only light points
belonging to the specific Area)
#1 - #256
Group command (every light
point belonging to a specific
group)
11 – …
Point to Point command
*1*[2-10]*WHERE##
*#*1##
or
*#*0##
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
403
404
-
Temporization command (WHAT 11-18)
Commands session
Open frame
TCP/IP Client  Server
*1*[11-18]*WHERE##
Notes
WHERE:
14543-x-y  WD ISO/IEC:2013
TCP/IP Client  Server
– 23 –
SC25 WG1 N1633
*#*1##
or
*#*0##
0
General command (every light
points in the system)
1-9
Area command (only light points
belonging to the specific Area)
#1 - #256
Group command (every light
point belonging to a specific
group)
11 - 99
Point to Point command
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
405
406
-
Light blinking command (WHAT 20-29)
Commands session
Open frame
Notes
WHERE:
TCP/IP Client -> Server
TCP/IP Server -> Client
0
General command (every light
points in the system)
1-9
Area command (only light points
belonging to the specific Area)
#1 - #256
Group command (every light point
belonging to a specific group)
11 - 99
Point to Point command
*1*[20-29]*WHERE##
*#*1##
or
*#*0##
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
407
408
-
UP/DOWN dimmer level command (WHAT 30-31)
Commands session
Open frame
Notes
WHERE:
TCP/IP Client  Server
0
General command (every light
points in the system)
1-9
Area command (only light points
belonging to the specific Area)
*1*[30-31]*WHERE##
14543-x-y  WD ISO/IEC:2013
– 24 –
TCP/IP Client  Server
SC25 WG1 N1633
#1 - #256
Group command (every light point
belonging to a specific group)
11 - 99
Point to Point command
*#*1##
or
*#*0##
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
Open frame
Notes
409
410
-
Set up the level at X speed
Commands session
WHERE:
TCP/IP Client  Server
TCP/IP Client  Server
0
General command (every light
points in the system)
1-9
Environment command (only light
points belonging to the specific
Raiser of the Environment)
#1 - #256
Group command (every light point
belonging to a specific group of
the entire system)
11 - 99
Point to Point command
Level: 1-100
The increase of the luminosity
intensity of the light point;
expressed as a percentage value:
1= level 1
100= level 100
Speed: 0 - 255
Set the speed to increase the
luminosity:
0 = immediate
255 = maximum delay
#1*WHERE*#1*level*speed##
*#*1##
or
*#*0##
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
411
412
Open messages: Events session
413
-
Light status
Events session
Open frames
Notes
14543-x-y  WD ISO/IEC:2013
– 25 –
SC25 WG1 N1633
WHAT = 0 - 1
TCP/IP: Server -> Client
*1*WHAT*WHERE##
WHERE = [11-99]
414
415
416
417
418
7.4.2 Basic sequences for Automation
Open frames that implement the automation functions (WHO = 2 AUTOMATION)
419
420
Table 7 - WHAT for Automation
Dimension
Notes
0
STOP
1
UP
2
DOWN
421
422
Table 8 - WHERE for Automation
Dimension
Notes
Dimension
Notes
0
General
…
…
1
Area 1
59
Automation Point 59
…
…
61
Automation Point 61
9
Area 9
62
Automation Point 62
11
Automation Point 11
…
…
12
Automation Point 12
69
Automation Point 69
…
…
71
Automation Point 71
19
Automation Point 19
72
Automation Point 72
21
Automation Point 21
…
…
22
Automation Point 22
79
Automation Point 79
…
…
81
Automation Point 81
29
Automation Point 29
82
Automation Point 82
31
Automation Point 31
…
…
32
Automation Point 32
89
Automation Point 89
…
…
91
Automation Point 91
14543-x-y  WD ISO/IEC:2013
– 26 –
SC25 WG1 N1633
39
Automation Point 39
92
Automation Point 92
41
Automation Point 41
…
…
42
Automation Point 42
99
Automation Point 99
…
…
#1
Group #1
49
Automation Point 49
#2
Group #2
51
Automation Point 51
…
…
52
Automation Point 52
#9
Group #9
423
424
Open messages: commands session
425
-
Commands STOP / UP / DOWN (WHAT 0,1,2)
Commands session
Open frame
Notes
WHERE:
TCP/IP Client -> Server
*2*[0-2]*WHERE##
*#*1##
or
*#*0##
TCP/IP Server -> Client
0
General command
(Every system automation points)
1–9
Area command (only
automation points belonging to the
specific Raiser of the Area)
#1 - #256
Group command (every automation
point belonging to a specific group
of the entire system)
11 – 99
Point to Point command
ACK: if the command is sent to the Bus
NACK: if the command is not sent to the Bus
426
427
Open messages: Events session
Events session
Open frames
TCP/IP: Server -> Client
*2*WHAT*WHERE ##
Notes
WHAT= [0-2]
WHERE = [11-99]
428
429
430
431
7.4.3 Basic sequences for Thermo
Open frames that implement thermo management (WHO = 4 THERMO)
TODO
14543-x-y  WD ISO/IEC:2013
– 27 –
432
433
434
435
436
437
7.4.4 xxx
TODO:
Which additional WHOs should be included?
SC25 WG1 N1633
14543-x-y  WD ISO/IEC:2013
– 28 –
SC25 WG1 N1633
438
8
439
440
441
442
443
8.1 General
Bus device objects can either be sensors or actuators, utilized for control of building
management devices, such as: lighting, shading/shutters, security systems, energy
management, heating, signalling and monitoring systems, service interface and building
control systems, remote control, video/audio controls, etc.
444
445
All of these functions can be performed through a unified system that is capable of
controlling, monitoring and sending signals.
OPEN Web Net Objects: Detailed Specifications
446
447
8.2 Types of objects
448
449
450
8.2.1 Device objects
Device objects are leaf objects, thus actuators (supplied with high voltage power) and
commands.
451
TODO: describe frames that address leaf objects
452
453
454
8.2.2 Interfaces
14543-x-y  WD ISO/IEC:2013
– 29 –
Annex A Bibliography
455
456
457
458
459

OPEN Web Net specifications
http://www.myopen-legrandgroup.com/resources/own_protocol/default.aspx
SC25 WG1 N1633