IEC 62480:2008

Multimedia home network - Network interfaces for network adapter

IEC 62480:2008 specifies the requirements for the characteristics of the Network Adapter itself and the interface between the Network Adapter and Network-ready equipment. Data exchanged between the Network Adapter and Network-ready equipment are basically for HES Class 1. This bilingual version (2012-08) corresponds to the monolingual English version, published in 2008-05.

Réseaux résidentiels multimédia - Interfaces réseau pour adaptateur de réseau

La CEI 62480:2008 spécifie les exigences applicables aux caractéristiques de l'adaptateur de réseau proprement dit ainsi que celles de l'interface entre l'adaptateur de réseau et l'équipement prêt pour connexion au réseau. Les données échangées entre l'adaptateur de réseau et l'équipement prêt pour connexion au réseau correspondent fondamentalement à celles de la Classe 1 de systèmes électroniques domotiques (HES). La présente version bilingue (2012-08) correspond à la version anglaise monolingue publiée en 2008-05.

General Information

• Status: Published
• Publication Date: 13-May-2008
• ICS: 33.040.40 - Data communication networks
• ICS: 33.160.60 - Multimedia systems and teleconferencing equipment
• ICS: 35.110 - Networking
• Technical Committee: TC 100 - Audio, video and multimedia systems and equipment
• Current Stage: PPUB - Publication issued
• Start Date: 31-May-2008
• Completion Date: 14-May-2008

Standards Content (Sample)

IEC 62480
Edition 1.0 2008-05
INTERNATIONAL
STANDARD
Multimedia home network – Network interfaces for network adapter
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.
IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: [e-mail]
Web: www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: [e-mail]
Tel.: [phone]
Fax: [phone]
IEC 62480
Edition 1.0 2008-05
INTERNATIONAL
STANDARD
Multimedia home network – Network interfaces for network adapter
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XD
ICS 33.160.60; 33.040.40; 35.110 ISBN 2-8318-9744-0

– 2 – 62480 © IEC:2008(E)
CONTENTS
FOREWORD.6
INTRODUCTION.8
1 Scope.9
2 Normative references .9
3 Terms and definitions .10
4 Network Adapter communication interfaces and requirements .12
4.1 Overview .12
4.2 Requirement of functions.14
4.3 Mechanical and physical characteristics for a Network Adapter .15
4.3.1 Network Adapter.15
4.3.2 Network Adapter communication interface .16
4.4 Electrical characteristics.16
4.4.1 Network Adapter.16
4.4.2 Network Adapter communication interface .16
4.5 Logical requirements .18
4.5.1 Network Adapter.18
4.5.2 Network Adapter communication interface .18
4.6 Network Adapter communication software protocols .20
4.6.1 Equipment interface data recognition service software protocol .20
4.6.2 Communication software protocol for object generation type .29
4.6.3 Communication software protocol for peer-to-peer type .84
Annex A (informative) Application object.85
Annex B (informative) Access to the application object in the Node .89
Annex C (normative) Property map description format .94
Annex D (informative) Composite messages .95
Annex E (informative) Connector shape .96
Bibliography.103
Figure 1 – The specified portions .9
Figure 2 – Network Adapter communication software hierarchy.12
Figure 3 – Example of the equipment interface data recognition sequence .13
Figure 4 – Network Adapter functions .15
Figure 5 – Logic level.17
Figure 6 – Character composition .19
Figure 7 – Timing requirements .19
Figure 8 – Format of equipment interface data recognition service.21
Figure 9 – Format of request command.22
Figure 10 – Format of response command .24
Figure 11 – Format of request command.25
Figure 12 – Format of response command .25

62480 © IEC:2008(E) – 3 –
Figure 13 – Sequence of equipment interface data recognition service .26
Figure 14 – Status change diagram .27
Figure 15 – Format of object generation type commands .31
Figure 16 – Operation of IASet (IASetM).33
Figure 17 – Operation of IASetup (IASetMup) .34
Figure 18 – Operation of IAGet (IAGetM) .35
Figure 19 – Operation of IAGetup (IAGetMup) .36
Figure 20 – Network Adapter status changes .37
Figure 21 – Format of request command.39
Figure 22 – Format of response command .40
Figure 23 – Format of request command.41
Figure 24 – Format of response command .42
Figure 25 – Format of request command.43
Figure 26 – Format of response command .43
Figure 27 – Format of request command.44
Figure 28 – Format of response command .44
Figure 29 – Format of object data .45
Figure 30 – Format of equipment inquiry data .47
Figure 31 – Format of request command.47
Figure 32 – Format of response command .48
Figure 33 – Format of request command.49
Figure 34 – Format of response command .49
Figure 35 – Format of request command.50
Figure 36 – Format of response command .51
Figure 37 – Format of Object Data .51
Figure 38 – Format of equipment inquiry data .53
Figure 39 – Format of request command.54
Figure 40 – Format of response command .55
Figure 41 – Format of request command.56
Figure 42 – Format of response command .57
Figure 43 – Format of request command.58
Figure 44 – Format of response command .59
Figure 45 – Format of request command.60
Figure 46 – Format of response command .61
Figure 47 – Format of request command.62
Figure 48 – Format of response command .63
Figure 49 – Format of request command.64
Figure 50 – Format of response command .65
Figure 51 – Format of request command.67
Figure 52– Format of Response Command .68
Figure 53 – Format of request command.70
Figure 54 – Format of response command .71
Figure 55 – Format of request command.72

– 4 – 62480 © IEC:2008(E)
Figure 56 – Format of response command .73
Figure 57 – Communication error notification command .74
Figure 58 – Equipment interface data confirmation sequence .75
Figure 59 – Initialization sequence.77
Figure 60 – Object construction sequence (1) .78
Figure 61 – Object construction sequence (2) .79
Figure 62 – Equipment status access request sequence .80
Figure 63 – Equipment status notification request sequence .80
Figure 64 – Element designation equipment status access request sequence.81
Figure 65 – Element designation equipment status notification request sequence.81
Figure 66 – Object access request sequence.82
Figure A.1 – Device object configuration example.86
Figure B.1 – Service primitive (obtain other node status: synchronous type) .89
Figure B.2 – Service primitive (obtain other node status: asynchronous type) .90
Figure B.3 – Example of object view .90
Figure B.4 – Service primitive (control other node functions).91
Figure B.5 – Example of object view .91
Figure B.6 – Service primitive (notify other nodes of self-node status: synchronous
type) .92
Figure B.7 – Service primitive (notify other nodes of self-node status: asynchronous
type) .92
Figure B.8 – Example of object view .92
Figure B.9 – Example of AOJ configuration in a Node .93
Figure C.1 – Property map description format .94
Figure D.1 – Part of the non-composite messages type packet .95
Figure D.2 – Part of the composite messages type packet .95
Figure E.1 – Type B Socket (Network-ready equipment side).99
Figure E.2 – Type B plug (Network Adapter side).100
Figure E.3 – Mating of Type B connector .101
Figure E.4 – Type A connecter pin arrangement for Network Adapter communication
interfaces – Pin assignment 1 .101
Figure E.5 – Type B connecter pin arrangement for Network Adapter communication
interfaces – Pin assignment 2 .102
Table 1 – Acceptable combinations of types supported by Network Adapters and types
supported by Network-ready equipment .13
Table 2 – Specifications for supplying power – Network-ready equipment (Class 1).17
Table 3 – Specifications for supplying power – Network-ready equipment (Class 2).17
Table 4 – Specifications for supplying power – Network-ready equipment (Class 3).17
Table 5 – Specifications for Supplying Power – Network Adapter.17
Table 6 – Timing requirements.19
Table 7 – Definition of states .28
Table 8 – Object generation type interface command codes.32
Table 9 – Classification of internal services .33
Table 10 – Communication sequences (object generation type) .75

62480 © IEC:2008(E) – 5 –
Table 11 – Timeout values.84
Table A.1 – Format of the AOJ.85
Table A.2 – List of class codes by group code .87
Table A.3 – APC allocation table.88
Table E.1 – Physical specifications for Type B connector.97

– 6 – 62480 © IEC:2008(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
MULTIMEDIA HOME NETWORK –
NETWORK INTERFACES FOR NETWORK ADAPTER
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization
comprising all national electrotechnical committees (IEC National Committees). The object of IEC is to
promote international co-operation on all questions concerning standardization in the electrical and electronic
fields. To this end and in addition to other activities, IEC publishes International Standards, Technical
Specifications, Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as
“IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee
interested in the subject dealt with may participate in this preparatory work. International, governmental and
non-governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates
closely with the International Organization for Standardization (ISO) in accordance with conditions determined
by agreement between the two organizations.
2) The formal decisions or agreements of IEC 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 National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated
in the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be held responsible for any equipment
declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees 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, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) 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.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62480 has been prepared by technical area 9: Audio, video and
multimedia applications for end-user network, of IEC technical committee 100: Audio, video
and multimedia systems and equipment.
The text of this standard is based on the following documents:
FDIS Report on voting
100/1354/FDIS 100/1389/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.

62480 © IEC:2008(E) – 7 –
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in
the data related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
A bilingual version of this publication may be issued at a later date.

– 8 – 62480 © IEC:2008(E)
INTRODUCTION
There are several obstacles to the spread of networked appliances that can be overcome by
the concept of a Network Adapter described in this standard. As Home Networking technology
is rapidly evolving, network functions which are pre-installed in home electrical appliances
can easily become obsolete and may be difficult to upgrade. Many appliances strictly limit
resources such as the CPU, power capacity, and memory to achieve cost savings. If all
network functions are embedded in Home Networked appliances, this could result in a higher
cost for new appliances and an additional barrier to wide adoption of such systems. In
addition, when consumers want to add a new appliance to the network, they are forced to
choose equipment with the same interconnecting systems as the existing network or add a
router or gateway which can interconnect different systems.
To solve these problems, the network functions are divided into two parts. Since functions
from OSI layer 1 to 7 (refer to ISO/IEC 7498 in Bibliography) are necessary to network home
electrical appliances (including both multimedia equipment and household appliances such as
televisions, computers, refrigerators, washing machines, and sensors), network functions from
OSI layer 1 to 6 and most of layer 7 reside in an external Network Adapter and only a small
part of layer 7 resides in the home appliances.
The advantages of applying this standard are:
• Users can upgrade a Home Network by simply changing the Network Adapters.
NOTE For example, when an end-user wants to have higher QoS media.
• An electrical appliance without embedded network functions can be connected to an
existing Home Network with a Network Adapter.
NOTE For example, when an end-user wants to utilize some of the network application functions (i.e.
energy conservation, etc) on an appliance which does not have all of the network function integrated.
• By selecting Network Adapters which use the same interconnecting system as the existing
Home Network, routers or the gateways can be avoided.
NOTE 3 For example, when an end-user’s network is a powerline network, but the appliance the user wants
to connect to has only an RF network connection.
NOTE 4 For example, when an end-user’s network is based on home networking standard “A” (layer 1-7), but
the appliance the user wants to connect utilizes a home networking standard “B” (layer 1-7).
• Home appliance manufacturers can produce products that can be connected to Home
Networks with minimal cost increases since most of the network functions are not required
to be embedded in the appliance.
NOTE This standard is helpful for standardizing the manufacturing process for including the network
function in appliances- especially when the market has a low penetration of appliances that are network-ready.
• Device objects are based on the same object-oriented methodology used in almost all
existing network protocols.
62480 © IEC:2008(E) – 9 –
MULTIMEDIA HOME NETWORK –
NETWORK INTERFACES FOR NETWORK ADAPTER
1 Scope
This International Standard specifies the requirements for the characteristics of the Network
Adapter itself and the interface between the Network Adapter and Network-ready equipment
as shown in Figure 1. Data exchanged between the Network Adapter and Network-ready
equipment are basically for HES Class1. This standard does not specify the Home Networking
Protocol by OSI layer 1-6 in the Network Adapter and any implementation of the software
stack and hardware.
Node A Node B Node C
Network-ready equipment
Network-ready home electric
(home electric appliance) equipment (home appliance
electric appliance) including all
OSI layer 7, Adapter Interface
OSI layers
Cable
Cable
Network Adapter Network adapter
OSI layer 7 (Application)
Adapter Interface
OSI layer 6 (Presentation)
OSI layer 5 (Session)
OSI layer 4 (Transport)
OSI layer 3 (Network)
OSI layer 2 (Data link)
OSI layer 1 (physical)
Transmission media
NOTE Gray colored portions are standardized.
Figure 1 – The specified portions
2 Normative references
The following referenced documents are indispensable for the application of this document.
For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies.
None.
– 10 – 62480 © IEC:2008(E)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
Application Property Data
ADT
data value related to Application Property Code, such as status notification or specific setting
and control; data size, code value, and data format for ADT are specified
3.2
Application Object
AOJ
a model of information to be disclosed to the network from information owned by the
communications processing block, or an access procedure model. The information or control
target owned by each device is specified as a property, and the operating method (setting,
browsing) for this is specified as a service. X1, X2 and X3 are assigned for AOJ code
3.3
Application Property Code
APC
1 octet code for the Application Property of the Application Object
3.4
cold start
method for starting the Home Network node by starting initial setting processing while
abandoning previous information related to Network addresses and Application Object data.
Cold start (1) re-acquires all information, especially information related to Network addresses,
cold start (2) re-acquires only lower layer address, and cold start (3) re-acquires only upper
layer addresses. If the address is fixed, cold start (1), cold start (2), and cold start (3) are the
same.
3.5
Device object
helps the device operation functions of Application Objects to facilitate status confirmation
and control between devices via communications and prepared for appliances such as air
conditioner Application Objects, refrigerator objects, etc., with the Application Object
definitions for such Application Objects to be specified separately and individually as classes.
3.6
Get/GetM
request for reading the property value of Application Object. Get is for non-element type
property values. GetM is for element type property values; in this case, the element number is
given
3.7
HES Class1
home electronic systems with transport capabilities for telecontrol applications such as control,
monitoring, measurement, alarm and low speed data transfer. These capabilities are typically
provided for by single packet-mode, low bandwidth channel and digital transmission
3.8
Home Network
generic name for various equipment-type Home Network standards for mainly household
appliances; specifically, it refers to CEBus, Konnex, ECHONET, LonTalk, etc.

62480 © IEC:2008(E) – 11 –
3.9
Network Adapter
Network Adapter contains the network functions from OSI layer 1 to 6, most of layer 7 and the
Network Adapter communication interface. Network-ready equipment can communicate with a
Home Network when connected via a Network Adapter
3.10
Network-ready equipment
network-ready equipment contains part of the network functions of OSI layer 7 and the
Network Adapter communication interface. Network-ready equipment cannot function as part
of a Home Network unless it is connected with a Network Adapter
3.11
Node
a communication node conforming to a Home Network standard. In a Home Network, this is a
Home Network communication function to be uniquely identified by a Network address. There
is no distinction between the application functions of nodes. The term node is used to
describe the function of one communication terminal on a Home Network. This is referred to
as node herein unless otherwise specified.
3.12
Node Profile Object
the Application object that represents Node related data, such as the operating state,
manufacturer data, address information, and the Device object list in the node, etc. These are
specified to enable manipulation (read/write) by application software and other nodes
3.13
NRZ method
non return to Zero method. This is one of the coding methods, in which 0 corresponds to low
level on the signal line, and 1 corresponds to high level on the signal line
3.14
Set/SetM
request for writing the property value of an Application Object. Set is for non-element type
property values. SetM is for element type property values. In the latter case, the element
number and setting value are given
3.15
Abbreviations
ADT Application Property Data
AOJ Application Object
APC Application Property Code
CN Command Number Code
DL Data Length Code
FCC Frame Check Code
FD Frame Data
FN Frame Number
FT Frame Type
– 12 – 62480 © IEC:2008(E)
4 Network Adapter communication interfaces and requirements
4.1 Overview
In this standard, two types of protocol specifications for Network Adapter communication
interface software are provided to minimize the burden placed on Network-ready equipment in
relation to network-related processing. The first is an object generation type and the second is
a peer-to-peer type.
a) Object generation type
AOJ related data are exchanged between the Network Adapter and Network-ready equipment
using a standardized communication method. AOJ related data preinstalled in the Network-
ready equipment (at least one) is configured in the Network Adapter using a standardized
procedure.
b) Peer-to-peer type
AOJ related data are exchanged between the Network Adapter and Network-ready equipment
using a vendor-defined communication method. The communication method is not defined in
this standard.
One appropriate type for the Network Adapter communication interface is selected after
equipment interface data recognition service. Figure 2 shows the Network Adapter
communication software hierarchy. Each box in the figure is described later.
Object Peer-to-peer
**type
type
Generation
type
Equipment interface
data recognition
service
Logical characteristics
Physical characteristics
Figure 2 – Network Adapter communication software hierarchy
Table 1 shows examples of acceptable combinations (i.e. combinations with which
communication is possible) of types supported by Network Adapters and types supported by
Network-ready equipment.
62480 © IEC:2008(E) – 13 –
Table 1 – Acceptable combinations of types supported by Network Adapters
and types supported by Network-ready equipment
Network Adapter Network-ready equipment
Object generation type Object generation type
Peer-to-peer type Peer-to-peer type
Figure 3 shows an example of an equipment interface data recognition service. The Network
Adapter inquires the communication type to the Network-ready equipment at 2 400/9 600 bps.
Network-ready
Network Adapter
equipment
What is your method?
(2 400 bps)
Not recognizable
What is your method?
(9 600 bps)
Recognizable
Object generation method
9 600 bps
Type-specific
communication procedure
NOTE 1 The figure shows a case where the Network-ready equipment is capable of handling 9 600 bps
communication and object generation method.
NOTE 2 This standard does not define the transmission speed confirmation order.
Figure 3 – Example of the equipment interface data recognition sequence

– 14 – 62480 © IEC:2008(E)
4.2 Requirement of functions
The four defined functions for a Network Adapter are shown below. All four functions, except
for b), shall be required for a Network Adapter as OSI layer 1-7. Only function d) is defined in
this standard. All other functions are defined according to the appropriate Home Network
protocols. The only function required for Network-ready equipment shall be d).
a) Message input and output function
A function to input and output electronic messages to and from the transmission medium in
accordance with the lower-layer communication protocol specifications. This function is
performed by lower-layer communication software and, therefore, requires a transceiver
capable of handling each Home Network lower-layer communication protocol.
b) Protocol difference absorption function
This function is performed by the protocol difference absorption processing section and allows
the necessary conversions to be made between the Home Network lower-layer
communication software and Home Network communications processing section protocol.
c) Home Network communications processing function
A function to be performed by the communications processing section which handles the
transmission frame, objects, etc.
d) Network Adapter communication interface function
This function performs the necessary communications between the Network Adapter and
Network-ready equipment and is defined in this standard. It performs communications
between the Network-ready equipment application function and the Home Network
communications processing function in the Network Adapter.

62480 © IEC:2008(E) – 15 –
Figure 4 shows the Network Adapter functions.
Network-ready
equipment
Network Adapter
Application
function
Basic API
Basic API
Device Service
Network Adapter
object object
communication
interface function
Home Network
OSI layer 7
communications processing
Network Adapter
OSI layer
function
communication
2/3/4/5/6/7
interface function
Protocol difference absorption
OSI layer 7
function
Lower-layer communication
Network Adapter Network Adapter
interface
communication interface
communication interface
Message input and
output function
OSI layer 1
Transmission media
NOTE OSI layer diagram corresponds to the left side diagram inside the Network Adapter.
Figure 4 – Network Adapter functions
4.3 Mechanical and physical characteristics for a Network Adapter
Mechanical and physical characteristics for a Network Adapter are defined in 4.3.1 and 4.3.2.
4.3.1 Network Adapter
The shape and display section are specified as below.
a) Shape
Only the connector described in 4.3.2 is defined in this standard.
b) Display section
Where LEDs are provided as a means of indicating the operation status of a Network Adapter,
it is recommended that the minimum requirements listed below be satisfied. For status
indication using a method not described herein, the specifications for the individual products
are used.
• Number of LEDs: one (used to indicate the operation status)
• LED colour: green
• LED status indication
In operation: ON (solid)
Initial processing: Slow blinking
Abnormal state: Rapid blinking
Not operating: OFF
– 16 – 62480 © IEC:2008(E)
NOTE 1 Initial processing indicates an unrecognized status as specified in 4.6.1.4
NOTE 2 Slow blinking – repeated on-off sequence with approximately 2 s in the ON state followed by
approximately 0,5 s in the OFF state.
NOTE 3 Rapid blinking – repeated ON-OFF sequence with approximately 0,5 s in the ON state followed by
approximately 0,5 s in the OFF state.
4.3.2 Network Adapter communication interface
This subclause defines the mechanical and physical characteristics required for Network
Adapter communication interface.
a) Transmission medium
The recommended transmission medium for Network Adapter communication interface is as
follows:
Eight multi-conductor cables (conductor diameter is not specified).
b) Cable length
In the case of an open collector, the length for which a guarantee is provided shall be 2 m at
the maximum.
c) Connection style
One-to-one connection of a Network Adapter and a corresponding piece of Network-ready
equipment.
4.4 Electrical characteristics
Electrical characteristics for a Network Adapter is defined in 4.4.1 and 4.4.2.
4.4.1 Network Adapter
The Electrical characteristics required for OSI layer 1-7 are defined according to the
appropriate Home Network protocols.
4.4.2 Network Adapter communication interface
This subclause defines the electrical characteristics requirements for Network Adapter
communication interface.
a) Cable characteristics impedance
Not specified.
b) Signal transmission speed
For signals used by the equipment interface data recognition service of a Network Adapter
communication interface, the two transmission speeds specified below shall be implemented
for the Network Adapter. The Network-ready equipment shall be equipped with either of the
two transmission speeds.
Transmission speeds: 2 400 bps, 9 600 bps
c) Signal transmission method and waveform of transmitted signals
The signal transmission method and the waveform of transmitted signals shall be as follows
(the interface points are the connector pins).
• Transmission method: base band transmission
• Waveform: single-current NRZ method

62480 © IEC:2008(E) – 17 –
• Logic level:see Figure 5
0 1
High Level
Low Level
Figure 5 – Logic level
d) Output pin specifications
Type 1 or Type 2 shall be selected.
Type 1: open collector
Type 2: 3,3 V CMOS
e) Specifications for supplying power
Three cla sses are specified for supplying power to Network-ready equipment as shown in the
following tables: Table 2; Table 3; and Table 4.One method for supplying power to Network
Adapters is specified in Table 5. The supplying and receiving functions are optional for both
Network-ready equipment and Network Adapters.
Table 2 – Specifications for supplying power – Network-ready equipment (Class 1)
Supply voltage 4,5 to 15 V
Supply capacity 1 200 mVA or more
Table 3 – Specifications for supplying power – Network-ready equipment (Class 2)
Supply voltage 4,5 to 5,5 V
Supply capacity 300 mVA or more
Table 4 – Specifications for supplying power – Network-ready equipment (Class 3)
Supply voltage 3 to 4,5 V
Supply capacity 300 mVA or more
Table 5 – Specifications for Supplying Power – Network Adapter
Supply voltage 3,0 to 5,5 V
Supply capacity 100 mVA or more
f) Reset
A reset pin (RST) to electrically reset the Network Adapter from the Network-ready equipment
shall be implemented in the Network Adapter. Implementation in the Network-ready equipment
is optional. The High, Low, and Low ĺ High states of the RST pin shall correspond to normal
operation, deactivation of the Network Adapter, and reset start, respectively.

– 18 – 62480 © IEC:2008(E)
4.5 Logical requirements
Logical requirements for Network Adapters are defined in 4.5.1 and 4.5.2.
4.5.1 Network Adapter
The Logical requirements for OSI layer 1-7 are defined according to the appropriate Home
Network protocols.
4.5.2 Network Adapter communication interface
This subclause defines the logical requirements for Network Adapter communication interface.
a) Control method
The control method shall be a RTS/CTS-based method. RTS shall correspond to signals to
notify the other side that transmission will be started or that no message can be received and
CTS shall correspond to signals that the other side sends either to indicate its status as to
whether or not messages can be received or to notify that it will start communicating. The
RTS/CTS control procedure for transmitting an electronic message shall be as follows:
• If no message can be received, RTS is set to High Level. If messages can be
received, RTS is set to Low Level.
• A check is made before transmission to confirm that CTS is Low Level.
(No message is sent if CTS is High Level.)
• Data are output to TXD.
Service requests shall be handled in the order they are transmitted. In the event of a service
request collision, the service request from the Network Adapter shall be handled first. A CTS
status change during a frame transmission shall not require the sending side to abort
transmission of the frame. If the sending side aborts transmission of the frame, that frame
shall be considered invalid and the prescribed subsequent processing shall be performed.
RTS/CTS function is required for the Network Adapter side and is optional for the Network-
ready equipment side.
b) Synchronization method
Synchronization shall be achieved using a character-by-character start-stop synchronization
method. The following requirements shall be satisfied:
• Character composition (see Figure 6) A total of 11 bits
Start bit (ST): 1 bit
Data: 8 bits
Parity: 1 bit
Stop bit (STP): 1 bit
• Data transmission order: LSB first
• Start bit: logical 0
• Stop bit: logical 1
• Parity: even number parity
62480 © IEC:2008(E) – 19 –
ST b0 b1 b2 b3 b4 b5 b6 b7 P STP
LSB MSB
Figure 6 – Character composition
c) Timing requirements
The timing requirements for execution of the Network Adapter communication software
protocols are as shown in Figure 7 and Table 6. The Network Adapter sends a request frame
and the Network-ready equipment receives it and sends back a response frame, vice versa.
T1
Request frame
T2
Sending side
STX FCC
Response frame
T0
T3
Receiving side
STX FCC
T4
STP ST
Figure 7 – Timing requirements
Table 6 – Timing requirements
Symbol Name Requirement
T0 Receiving side frame 9 600 bps or less: No message is received for 10 ms or more.
synchronization
More than 9 600 bps: No message is received for a period equal to
confirmation (frame
3-character composition length or more.
completion / start position
detection)
T1 Response waiting timeout 300 ms from the end of the frame sent by itself
T2 Retransmission inhibition 300 ms from the end of the frame sent by itself
time
T3 Response transmission 9 600 bps or less: 10 ms or more
inhibition time (T4
More than 9 600 bps: a period equal to 3-character composition
confirmation time)
length or more
T4 Sending side character 9 600 bps or less: less than 10 ms
composition interval
More than 9 600 bps: less than a period equal to 3-character
composition length
– 20 – 62480 © IEC:2008(E)
d) Co
...

IEC 62480 ®
Edition 1.0 2008-05
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Multimedia home network – Network interfaces for network adapter

Réseaux résidentiels multimédia – Interfaces réseau pour adaptateur de réseau

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite ni
utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie et les
microfilms, sans l'accord écrit de la CEI ou du Comité national de la CEI du pays du demandeur.
Si vous avez des questions sur le copyright de la CEI ou si vous désirez obtenir des droits supplémentaires sur cette
publication, utilisez les coordonnées ci-après ou contactez le Comité national de la CEI de votre pays de résidence.

IEC Central Office Tel.: [phone]
3, rue de Varembé Fax: [phone]
CH-1211 Geneva 20 [e-mail]
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.

Useful links:
IEC publications search - www.iec.ch/searchpub Electropedia - www.electropedia.org
The advanced search enables you to find IEC publications The world's leading online dictionary of electronic and
by a variety of criteria (reference number, text, technical electrical terms containing more than 30 000 terms and
committee,…). definitions in English and French, with equivalent terms in
It also gives information on projects, replaced and additional languages. Also known as the International
withdrawn publications. Electrotechnical Vocabulary (IEV) on-line.

IEC Just Published - webstore.iec.ch/justpublished Customer Service Centre - webstore.iec.ch/csc
Stay up to date on all new IEC publications. Just Published If you wish to give us your feedback on this publication
details all new publications released. Available on-line and or need further assistance, please contact the
also once a month by email. Customer Service Centre: [e-mail].

A propos de la CEI
La Commission Electrotechnique Internationale (CEI) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

A propos des publications CEI
Le contenu technique des publications de la CEI est constamment revu. Veuillez vous assurer que vous possédez
l’édition la plus récente, un corrigendum ou amendement peut avoir été publié.

Liens utiles:
Recherche de publications CEI - www.iec.ch/searchpub Electropedia - www.electropedia.org
La recherche avancée vous permet de trouver des Le premier dictionnaire en ligne au monde de termes
publications CEI en utilisant différents critères (numéro de électroniques et électriques. Il contient plus de 30 000
référence, texte, comité d’études,…). termes et définitions en anglais et en français, ainsi que
Elle donne aussi des informations sur les projets et les les termes équivalents dans les langues additionnelles.
publications remplacées ou retirées. Egalement appelé Vocabulaire Electrotechnique
International (VEI) en ligne.
Just Published CEI - webstore.iec.ch/justpublished
Service Clients - webstore.iec.ch/csc
Restez informé sur les nouvelles publications de la CEI.
Just Published détaille les nouvelles publications parues. Si vous désirez nous donner des commentaires sur
Disponible en ligne et aussi une fois par mois par email. cette publication ou si vous avez des questions
contactez-nous: [e-mail].
IEC 62480 ®
Edition 1.0 2008-05
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Multimedia home network – Network interfaces for network adapter

Réseaux résidentiels multimédia – Interfaces réseau pour adaptateur de réseau

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
CODE PRIX XD
ICS 33.040.40; 33.160.60; 35.110 ISBN 978-2-83220-246-3

– 2 – 62480  IEC:2008
CONTENTS
FOREWORD . 6
INTRODUCTION . 8

1 Scope . 9
2 Normative references . 9
3 Terms and definitions . 10
4 Network Adapter communication interfaces and requirements . 12
4.1 Overview . 12
4.2 Requirement of functions . 14
4.3 Mechanical and physical characteristics for a Network Adapter . 15
4.3.1 Network Adapter . 15
4.3.2 Network Adapter communication interface . 16
4.4 Electrical characteristics . 16
4.4.1 Network Adapter . 16
4.4.2 Network Adapter communication interface . 16
4.5 Logical requirements . 18
4.5.1 Network Adapter . 18
4.5.2 Network Adapter communication interface . 18
4.6 Network Adapter communication software protocols . 20
4.6.1 Equipment interface data recognition service software protocol . 20
4.6.2 Communication software protocol for object generation type . 29
4.6.3 Communication software protocol for peer-to-peer type . 84

Annex A (informative) Application object . 85
Annex B (informative) Access to the application object in the Node . 89
Annex C (normative) Property map description format . 94
Annex D (informative) Composite messages . 95
Annex E (informative) Connector shape . 96

Bibliography . 103

Figure 1 – The specified portions . 9
Figure 2 – Network Adapter communication software hierarchy. 12
Figure 3 – Example of the equipment interface data recognition sequence . 13
Figure 4 – Network Adapter functions . 15
Figure 5 – Logic level. 17
Figure 6 – Character composition . 19
Figure 7 – Timing requirements . 19
Figure 8 – Format of equipment interface data recognition service . 21
Figure 9 – Format of request command . 22
Figure 10 – Format of response command . 24
Figure 11 – Format of request command . 25
Figure 12 – Format of response command . 25

62480  IEC:2008 – 3 –
Figure 13 – Sequence of equipment interface data recognition service . 26
Figure 14 – Status change diagram . 27
Figure 15 – Format of object generation type commands . 31
Figure 16 – Operation of IASet (IASetM) . 33
Figure 17 – Operation of IASetup (IASetMup) . 34
Figure 18 – Operation of IAGet (IAGetM) . 35
Figure 19 – Operation of IAGetup (IAGetMup) . 36
Figure 20 – Network Adapter status changes . 37
Figure 21 – Format of request command . 39
Figure 22 – Format of response command . 40
Figure 23 – Format of request command . 41
Figure 24 – Format of response command . 42
Figure 25 – Format of request command . 43
Figure 26 – Format of response command . 43
Figure 27 – Format of request command . 44
Figure 28 – Format of response command . 44
Figure 29 – Format of object data . 45
Figure 30 – Format of equipment inquiry data . 47
Figure 31 – Format of request command . 47
Figure 32 – Format of response command . 48
Figure 33 – Format of request command . 49
Figure 34 – Format of response command . 49
Figure 35 – Format of request command . 50
Figure 36 – Format of response command . 51
Figure 37 – Format of Object Data . 51
Figure 38 – Format of equipment inquiry data . 53
Figure 39 – Format of request command . 54
Figure 40 – Format of response command . 55
Figure 41 – Format of request command . 56
Figure 42 – Format of response command . 57
Figure 43 – Format of request command . 58
Figure 44 – Format of response command . 59
Figure 45 – Format of request command . 60
Figure 46 – Format of response command . 61
Figure 47 – Format of request command . 62
Figure 48 – Format of response command . 63
Figure 49 – Format of request command . 64
Figure 50 – Format of response command . 65
Figure 51 – Format of request command . 67
Figure 52 – Format of Response Command . 68
Figure 53 – Format of request command . 70
Figure 54 – Format of response command . 71
Figure 55 – Format of request command . 72

– 4 – 62480  IEC:2008
Figure 56 – Format of response command . 73
Figure 57 – Communication error notification command . 74
Figure 58 – Equipment interface data confirmation sequence . 75
Figure 59 – Initialization sequence . 77
Figure 60 – Object construction sequence (1) . 78
Figure 61 – Object construction sequence (2) . 79
Figure 62 – Equipment status access request sequence . 80
Figure 63 – Equipment status notification request sequence . 80
Figure 64 – Element designation equipment status access request sequence . 81
Figure 65 – Element designation equipment status notification request sequence . 81
Figure 66 – Object access request sequence . 82
Figure A.1 – Device object configuration example . 86
Figure B.1 – Service primitive (obtain other node status: synchronous type) . 89
Figure B.2 – Service primitive (obtain other node status: asynchronous type) . 90
Figure B.3 – Example of object view . 90
Figure B.4 – Service primitive (control other node functions). 91
Figure B.5 – Example of object view . 91
Figure B.6 – Service primitive (notify other nodes of self-node status: synchronous
type) . 92
Figure B.7 – Service primitive (notify other nodes of self-node status: asynchronous
type) . 92
Figure B.8 – Example of object view . 92
Figure B.9 – Example of AOJ configuration in a Node . 93
Figure C.1 – Property map description format . 94
Figure D.1 – Part of the non-composite messages type packet . 95
Figure D.2 – Part of the composite messages type packet . 95
Figure E.1 – Type B Socket (Network-ready equipment side) . 99
Figure E.2 – Type B plug (Network Adapter side) . 100
Figure E.3 – Mating of Type B connector . 101
Figure E.4 – Type A connecter pin arrangement for Network Adapter communication
interfaces – Pin assignment 1 . 101
Figure E.5 – Type B connecter pin arrangement for Network Adapter communication
interfaces – Pin assignment 2 . 102

Table 1 – Acceptable combinations of types supported by Network Adapters and types
supported by Network-ready equipment . 13
Table 2 – Specifications for supplying power – Network-ready equipment (Class 1) . 17
Table 3 – Specifications for supplying power – Network-ready equipment (Class 2) . 17
Table 4 – Specifications for supplying power – Network-ready equipment (Class 3) . 17
Table 5 – Specifications for Supplying Power – Network Adapter . 17
Table 6 – Timing requirements . 19
Table 7 – Definition of states . 28
Table 8 – Object generation type interface command codes. 32
Table 9 – Classification of internal services . 33
Table 10 – Communication sequences (object generation type) . 75

62480  IEC:2008 – 5 –
Table 11 – Timeout values . 84
Table A.1 – Format of the AOJ . 85
Table A.2 – List of class codes by group code . 87
Table A.3 – APC allocation table . 88
Table E.1 – Physical specifications for Type B connector . 97

– 6 – 62480  IEC:2008
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
MULTIMEDIA HOME NETWORK –
NETWORK INTERFACES FOR NETWORK ADAPTER

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization
comprising all national electrotechnical committees (IEC National Committees). The object of IEC is to
promote international co-operation on all questions concerning standardization in the electrical and electronic
fields. To this end and in addition to other activities, IEC publishes International Standards, Technical
Specifications, Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as
“IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee
interested in the subject dealt with may participate in this preparatory work. International, governmental and
non-governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates
closely with the International Organization for Standardization (ISO) in accordance with conditions determined
by agreement between the two organizations.
2) The formal decisions or agreements of IEC 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 National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated
in the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be held responsible for any equipment
declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees 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, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) 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.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62480 has been prepared by technical area 9: Audio, video and
multimedia applications for end-user network, of IEC technical committee 100: Audio, video
and multimedia systems and equipment.
This bilingual version (2012-08) corresponds to the monolingual English version, published in
2008-05.
The text of this standard is based on the following documents:
FDIS Report on voting
100/1354/FDIS 100/1389/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
The French version of this standard has not been voted upon.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.

62480  IEC:2008 – 7 –
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in
the data related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
– 8 – 62480  IEC:2008
INTRODUCTION
There are several obstacles to the spread of networked appliances that can be overcome by
the concept of a Network Adapter described in this standard. As Home Networking technology
is rapidly evolving, network functions which are pre-installed in home electrical appliances
can easily become obsolete and may be difficult to upgrade. Many appliances strictly limit
resources such as the CPU, power capacity, and memory to achieve cost savings. If all
network functions are embedded in Home Networked appliances, this could result in a higher
cost for new appliances and an additional barrier to wide adoption of such systems. In
addition, when consumers want to add a new appliance to the network, they are forced to
choose equipment with the same interconnecting systems as the existing network or add a
router or gateway which can interconnect different systems.
To solve these problems, the network functions are divided into two parts. Since functions
from OSI layer 1 to 7 (refer to ISO/IEC 7498 in Bibliography) are necessary to network home
electrical appliances (including both multimedia equipment and household appliances such as
televisions, computers, refrigerators, washing machines, and sensors), network functions from
OSI layer 1 to 6 and most of layer 7 reside in an external Network Adapter and only a small
part of layer 7 resides in the home appliances.
The advantages of applying this standard are:
• Users can upgrade a Home Network by simply changing the Network Adapters.
NOTE 1 For example, when an end-user wants to have higher QoS media.
• An electrical appliance without embedded network functions can be connected to an
existing Home Network with a Network Adapter.
NOTE 2 For example, when an end-user wants to utilize some of the network application functions (i.e.
energy conservation, etc) on an appliance which does not have all of the network function integrated.
• By selecting Network Adapters which use the same interconnecting system as the existing
Home Network, routers or the gateways can be avoided.
NOTE 3 For example, when an end-user’s network is a powerline network, but the appliance the user wants
to connect to has only an RF network connection.
NOTE 4 For example, when an end-user’s network is based on home networking standard “A” (layer 1-7), but
the appliance the user wants to connect utilizes a home networking standard “B” (layer 1-7).
• Home appliance manufacturers can produce products that can be connected to Home
Networks with minimal cost increases since most of the network functions are not required
to be embedded in the appliance.
NOTE 5 This standard is helpful for standardizing the manufacturing process for including the network
function in appliances- especially when the market has a low penetration of appliances that are network-ready.
• Device objects are based on the same object-oriented methodology used in almost all
existing network protocols.
62480  IEC:2008 – 9 –
MULTIMEDIA HOME NETWORK –
NETWORK INTERFACES FOR NETWORK ADAPTER

1 Scope
This International Standard specifies the requirements for the characteristics of the Network
Adapter itself and the interface between the Network Adapter and Network-ready equipment
as shown in Figure 1. Data exchanged between the Network Adapter and Network-ready
equipment are basically for HES Class1. This standard does not specify the Home Networking
Protocol by OSI layer 1-6 in the Network Adapter and any implementation of the software
stack and hardware.
Node A
Node B Node C
Network-ready equipment Network-ready home electric
(home electric appliance)
equipment (home appliance
electric appliance) including all
OSI layer 7, Adapter Interface
OSI layers
Cable
Cable
Network Adapter
Network adapter
OSI layer 7 (Application)
Adapter Interface
OSI layer 6 (Presentation)
OSI layer 5 (Session)
OSI layer 4 (Transport)
OSI layer 3 (Network)
OSI layer 2 (Data link)
OSI layer 1 (physical)
Transmission media
NOTE Gray colored portions are standardized.

Figure 1 – The specified portions

2 Normative references
The following referenced documents are indispensable for the application of this document.

For dated references, only the edition cited applies. For undated references, the latest edition

of the referenced document (including any amendments) applies.

None.
– 10 – 62480  IEC:2008
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
Application Property Data
ADT
data value related to Application Property Code, such as status notification or specific setting
and control; data size, code value, and data format for ADT are specified
3.2
Application Object
AOJ
a model of information to be disclosed to the network from information owned by the
communications processing block, or an access procedure model. The information or control
target owned by each device is specified as a property, and the operating method (setting,
browsing) for this is specified as a service. X1, X2 and X3 are assigned for AOJ code
3.3
Application Property Code
APC
1 octet code for the Application Property of the Application Object
3.4
cold start
method for starting the Home Network node by starting initial setting processing while
abandoning previous information related to Network addresses and Application Object data.
Cold start (1) re-acquires all information, especially information related to Network addresses,
cold start (2) re-acquires only lower layer address, and cold start (3) re-acquires only upper
layer addresses. If the address is fixed, cold start (1), cold start (2), and cold start (3) are the
same.
3.5
Device object
helps the device operation functions of Application Objects to facilitate status confirmation
and control between devices via communications and prepared for appliances such as air
conditioner Application Objects, refrigerator objects, etc., with the Application Object
definitions for such Application Objects to be specified separately and individually as classes.
3.6
Get/GetM
request for reading the property value of Application Object. Get is for non-element type
property values. GetM is for element type property values; in this case, the element number is
given
3.7
HES Class1
home electronic systems with transport capabilities for telecontrol applications such as control,
monitoring, measurement, alarm and low speed data transfer. These capabilities are typically
provided for by single packet-mode, low bandwidth channel and digital transmission
3.8
Home Network
generic name for various equipment-type Home Network standards for mainly household
appliances; specifically, it refers to CEBus, Konnex, ECHONET, LonTalk, etc.

62480  IEC:2008 – 11 –
3.9
Network Adapter
Network Adapter contains the network functions from OSI layer 1 to 6, most of layer 7 and the
Network Adapter communication interface. Network-ready equipment can communicate with a
Home Network when connected via a Network Adapter
3.10
Network-ready equipment
network-ready equipment contains part of the network functions of OSI layer 7 and the
Network Adapter communication interface. Network-ready equipment cannot function as part
of a Home Network unless it is connected with a Network Adapter
3.11
Node
a communication node conforming to a Home Network standard. In a Home Network, this is a
Home Network communication function to be uniquely identified by a Network address. There
is no distinction between the application functions of nodes. The term node is used to
describe the function of one communication terminal on a Home Network. This is referred to
as node herein unless otherwise specified
3.12
Node Profile Object
the Application object that represents Node related data, such as the operating state,
manufacturer data, address information, and the Device object list in the node, etc. These are
specified to enable manipulation (read/write) by application software and other nodes
3.13
NRZ method
non return to Zero method. This is one of the coding methods, in which 0 corresponds to low
level on the signal line, and 1 corresponds to high level on the signal line
3.14
Set/SetM
request for writing the property value of an Application Object. Set is for non-element type
property values. SetM is for element type property values. In the latter case, the element
number and setting value are given
3.15
Abbreviations
ADT Application Property Data
AOJ Application Object
APC Application Property Code
CN Command Number Code
DL Data Length Code
FCC Frame Check Code
FD Frame Data
FN Frame Number
FT Frame Type
– 12 – 62480  IEC:2008
4 Network Adapter communication interfaces and requirements
4.1 Overview
In this standard, two types of protocol specifications for Network Adapter communication
interface software are provided to minimize the burden placed on Network-ready equipment in
relation to network-related processing. The first is an object generation type and the second is
a peer-to-peer type.
a) Object generation type
AOJ related data are exchanged between the Network Adapter and Network-ready equipment
using a standardized communication method. AOJ related data preinstalled in the Network-
ready equipment (at least one) is configured in the Network Adapter using a standardized
procedure.
b) Peer-to-peer type
AOJ related data are exchanged between the Network Adapter and Network-ready equipment
using a vendor-defined communication method. The communication method is not defined in
this standard.
One appropriate type for the Network Adapter communication interface is selected after
equipment interface data recognition service. Figure 2 shows the Network Adapter
communication software hierarchy. Each box in the figure is described later.
Object Peer-to-peer
**type
type
Generation
type
Equipment interface
data recognition
service
Logical characteristics
Physical characteristics
Figure 2 – Network Adapter communication software hierarchy
Table 1 shows examples of acceptable combinations (i.e. combinations with which
communication is possible) of types supported by Network Adapters and types supported by
Network-ready equipment.
62480  IEC:2008 – 13 –
Table 1 – Acceptable combinations of types supported by Network Adapters
and types supported by Network-ready equipment
Network Adapter Network-ready equipment
Object generation type Object generation type
Peer-to-peer type Peer-to-peer type

Figure 3 shows an example of an equipment interface data recognition service. The Network
Adapter inquires the communication type to the Network-ready equipment at 2 400/9 600 bps.
Network-ready
Network Adapter
equipment
What is your method?
(2 400 bps)
Not recognizable
What is your method?
(9 600 bps)
Recognizable
Object generation method
9 600 bps
Type-specific
communication procedure
NOTE 1 The figure shows a case where the Network-ready equipment is capable of handling 9 600 bps
communication and object generation method.
NOTE 2 This standard does not define the transmission speed confirmation order.
Figure 3 – Example of the equipment interface data recognition sequence

– 14 – 62480  IEC:2008
4.2 Requirement of functions
The four defined functions for a Network Adapter are shown below. All four functions, except
for b), shall be required for a Network Adapter as OSI layer 1-7. Only function d) is defined in
this standard. All other functions are defined according to the appropriate Home Network
protocols. The only function required for Network-ready equipment shall be d).
a) Message input and output function
A function to input and output electronic messages to and from the transmission medium in
accordance with the lower-layer communication protocol specifications. This function is
performed by lower-layer communication software and, therefore, requires a transceiver
capable of handling each Home Network lower-layer communication protocol.
b) Protocol difference absorption function
This function is performed by the protocol difference absorption processing section and allows
the necessary conversions to be made between the Home Network lower-layer
communication software and Home Network communications processing section protocol.
c) Home Network communications processing function
A function to be performed by the communications processing section which handles the
transmission frame, objects, etc.
d) Network Adapter communication interface function
This function performs the necessary communications between the Network Adapter and
Network-ready equipment and is defined in this standard. It performs communications
between the Network-ready equipment application function and the Home Network
communications processing function in the Network Adapter.

62480  IEC:2008 – 15 –
Figure 4 shows the Network Adapter functions.

Network-ready
equipment
Network Adapter
Application
function
Basic API
Basic API
Device Service
Network Adapter
object object
communication
interface function
Home Network
OSI layer 7
communications processing
Network Adapter
OSI layer
function
communication
2/3/4/5/6/7
interface function
Protocol difference absorption
OSI layer 7
function
Lower-layer communication
Network Adapter Network Adapter
interface
communication interface
communication interface
Message input and
output function
OSI layer 1
Transmission media
NOTE OSI layer diagram corresponds to the left side diagram inside the Network Adapter.
Figure 4 – Network Adapter functions
4.3 Mechanical and physical characteristics for a Network Adapter
Mechanical and physical characteristics for a Network Adapter are defined in 4.3.1 and 4.3.2.
4.3.1 Network Adapter
The shape and display section are specified as below.
a) Shape
Only the connector described in 4.3.2 is defined in this standard.
b) Display section
Where LEDs are provided as a means of indicating the operation status of a Network Adapter,
it is recommended that the minimum requirements listed below be satisfied. For status
indication using a method not described herein, the specifications for the individual products
are used.
• Number of LEDs: one (used to indicate the operation status)
• LED colour: green
• LED status indication
In operation: ON (solid)
Initial processing: Slow blinking
Abnormal state: Rapid blinking
Not operating: OFF
– 16 – 62480  IEC:2008
NOTE 1 Initial processing indicates an unrecognized status as specified in 4.6.1.4
NOTE 2 Slow blinking – repeated on-off sequence with approximately 2 s in the ON state followed by
approximately 0,5 s in the OFF state.
NOTE 3 Rapid blinking – repeated ON-OFF sequence with approximately 0,5 s in the ON state followed by
approximately 0,5 s in the OFF state.
4.3.2 Network Adapter communication interface
This subclause defines the mechanical and physical characteristics required for Network
Adapter communication interface.
a) Transmission medium
The recommended transmission medium for Network Adapter communication interface is as
follows:
Eight multi-conductor cables (conductor diameter is not specified).
b) Cable length
In the case of an open collector, the length for which a guarantee is provided shall be 2 m at
the maximum.
c) Connection style
One-to-one connection of a Network Adapter and a corresponding piece of Network-ready
equipment.
4.4 Electrical characteristics
Electrical characteristics for a Network Adapter is defined in 4.4.1 and 4.4.2.
4.4.1 Network Adapter
The Electrical characteristics required for OSI layer 1-7 are defined according to the
appropriate Home Network protocols.
4.4.2 Network Adapter communication interface
This subclause defines the electrical characteristics requirements for Network Adapter
communication interface.
a) Cable characteristics impedance
Not specified.
b) Signal transmission speed
For signals used by the equipment interface data recognition service of a Network Adapter
communication interface, the two transmission speeds specified below shall be implemented
for the Network Adapter. The Network-ready equipment shall be equipped with either of the
two transmission speeds.
Transmission speeds: 2 400 bps, 9 600 bps
c) Signal transmission method and waveform of transmitted signals
The signal transmission method and the waveform of transmitted signals shall be as follows
(the interface points are the connector pins).
• Transmission method: base band transmission
• Waveform: single-current NRZ method

62480  IEC:2008 – 17 –
• Logic level:see Figure 5
0 1
High Level
Low Level
Figure 5 – Logic level
d) Output pin specifications
Type 1 or Type 2 shall be selected.
Type 1: open collector
Type 2: 3,3 V CMOS
e) Specifications for supplying power
Three cla sses are specified for supplying power to Network-ready equipment as shown in the
following tables: Table 2; Table 3; and Table 4.One method for supplying power to Network
Adapters is specified in Table 5. The supplying and receiving functions are optional for both
Network-ready equipment and Network Adapters.
Table 2 – Specifications for supplying power – Network-ready equipment (Class 1)
Supply voltage 4,5 to 15 V
Supply capacity 1 200 mVA or more

Table 3 – Specifications for supplying power – Network-ready equipment (Class 2)
Supply voltage 4,5 to 5,5 V
Supply capacity 300 mVA or more

Table 4 – Specifications for supplying power – Network-ready equipment (Class 3)
Supply voltage 3 to 4,5 V
Supply capacity 300 mVA or more

Table 5 – Specifications for Supplying Power – Network Adapter
Supply voltage 3,0 to 5,5 V
Supply capacity 100 mVA or more

f) Reset
A reset pin (RST) to electrically reset the Network Adapter from the Network-ready equipment
shall be implemented in the Network Adapter. Implementation in the Network-ready equipment
is optional. The High, Low, and Low → High states of the RST pin shall correspond to normal
operation, deactivation of the Network Adapter, and reset start, respectively.
...