|
SIST EN 62480:2009
01-oktober-2009
9HþSUHGVWDYQRVWQRGRPDþHRPUHåMH2PUHåQLYPHVQLNL]DRPUHåQLSULODJRGLOQLN
,(&
Multimedia home network - Network interfaces for network adapter (IEC 62480:2008)
Multimedia Heimnetzwerk - Netzwerkschnittstellen für Netzwerkadapter (IEC
62480:2008)
Réseaux résidentiels multimédia - Interfaces de réseau relatifs aux adaptateurs de
réseaux (CEI 62480:2008)
Ta slovenski standard je istoveten z: EN 62480:2009
ICS:
33.040.40 Podatkovna komunikacijska Data communication
omrežja networks
33.160.60 9HþSUHGVWDYQL PXOWLPHGLMVNL Multimedia systems and
VLVWHPLLQRSUHPD]D teleconferencing equipment
WHOHNRQIHUHQFH
35.110 Omreževanje Networking
SIST EN 62480:2009 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 62480:2009
---------------------- Page: 2 ----------------------
SIST EN 62480:2009
EUROPEAN STANDARD
EN 62480
NORME EUROPÉENNE
August 2009
EUROPÄISCHE NORM
ICS 33.160.60; 33.040.40; 35.110
English version
Multimedia home network -
Network interfaces for network adapter
(IEC 62480:2008)
Réseaux résidentiels multimédia - Multimedia-Heimnetzwerk -
Interfaces de réseau Netzwerkschnittstellen
relatifs aux adaptateurs de réseaux für Netzwerkadapter
(CEI 62480:2008) (IEC 62480:2008)
This European Standard was approved by CENELEC on 2009-07-01. CENELEC members are bound to comply
with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard
the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on
application to the Central Secretariat or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CENELEC member into its own language and notified
to the Central Secretariat has the same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the
Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and the United Kingdom.
CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
Central Secretariat: Avenue Marnix 17, B - 1000 Brussels
© 2009 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 62480:2009 E
---------------------- Page: 3 ----------------------
SIST EN 62480:2009
EN 62480:2009 - 2 -
Foreword
The text of document 100/1354/FDIS, future edition 1 of IEC 62480, prepared by technical area 9, Audio,
video and multimedia applications for end-user network, of IEC TC 100, Audio, video and multimedia
systems and equipment, was submitted to the IEC-CENELEC parallel vote and was approved by
CENELEC as EN 62480 on 2009-07-01.
The following dates were fixed:
– latest date by which the EN has to be implemented
at national level by publication of an identical
(dop) 2010-04-01
national standard or by endorsement
– latest date by which the national standards conflicting
(dow) 2012-07-01
with the EN have to be withdrawn
__________
Endorsement notice
The text of the International Standard IEC 62480:2008 was approved by CENELEC as a European
Standard without any modification.
__________
---------------------- Page: 4 ----------------------
SIST EN 62480:2009
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
---------------------- Page: 5 ----------------------
SIST EN 62480:2009
– 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
---------------------- Page: 6 ----------------------
SIST EN 62480:2009
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
---------------------- Page: 7 ----------------------
SIST EN 62480:2009
– 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
---------------------- Page: 8 ----------------------
SIST EN 62480:2009
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
---------------------- Page: 9 ----------------------
SIST EN 62480:2009
– 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.
---------------------- Page: 10 ----------------------
SIST EN 62480:2009
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.
---------------------- Page: 11 ----------------------
SIST EN 62480:2009
– 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.
---------------------- Page: 12 ----------------------
SIST EN 62480:2009
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.
---------------------- Page: 13 ----------------------
SIST EN 62480:2009
– 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 uppe
...