1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationMultimedia home network Network interfaces for networkadapterBS EN 62480:2009National forewordThis British Standard is the UK implementation of EN 62480:2009. It is identical to
2、IEC 62480:2008.The UK participation in its preparation was entrusted to Technical CommitteeEPL/100, Audio, video and multimedia systems and equipment.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the
3、necessary provisions of acontract. Users are responsible for its correct application. BSI 2010ISBN 978 0 580 59553 0ICS 33.040.40; 33.160.60; 35.110Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of the Standards
4、Policy and Strategy Committee on 31 January 2010Amendments issued since publicationAmd. No. Date Text affectedBRITISH STANDARDBS EN 62480:2009EUROPEAN STANDARD EN 62480 NORME EUROPENNE EUROPISCHE NORM August 2009 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normal
5、isation Electrotechnique Europisches Komitee fr 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 ICS 33.160.60; 33.040.40; 35.110
6、English version Multimedia home network - Network interfaces for network adapter (IEC 62480:2008) Rseaux rsidentiels multimdia - Interfaces de rseau relatifs aux adaptateurs de rseaux (CEI 62480:2008) Multimedia-Heimnetzwerk - Netzwerkschnittstellen fr Netzwerkadapter (IEC 62480:2008) This European
7、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 con
8、cerning 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 int
9、o 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, Irela
10、nd, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. BS EN 62480:2009EN 62480:2009 - 2 - Foreword The text of document 100/1354/FDIS, future edition 1 of IEC 62480, prepared by tech
11、nical 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 th
12、e EN has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2010-04-01 latest date by which the national standards conflicting with the EN have to be withdrawn (dow) 2012-07-01 _ Endorsement notice The text of the International Standard IEC 6
13、2480:2008 was approved by CENELEC as a European Standard without any modification. _ BS EN 62480:2009 2 62480 IEC:2008(E) CONTENTS INTRODUCTION.81 Scope.92 Normative references .93 Terms and definitions .104 Network Adapter communication interfaces and requirements 124.1 Overview .124.2 Requirement
14、of functions.144.3 Mechanical and physical characteristics for a Network Adapter .154.3.1 Network Adapter154.3.2 Network Adapter communication interface .164.4 Electrical characteristics164.4.1 Network Adapter164.4.2 Network Adapter communication interface .164.5 Logical requirements .184.5.1 Networ
15、k Adapter184.5.2 Network Adapter communication interface .184.6 Network Adapter communication software protocols 204.6.1 Equipment interface data recognition service software protocol .204.6.2 Communication software protocol for object generation type .294.6.3 Communication software protocol for pee
16、r-to-peer type .84Annex A (informative) Application object85Annex B (informative) Access to the application object in the Node .89Annex C (normative) Property map description format .94Annex D (informative) Composite messages 95Annex E (informative) Connector shape.96Bibliography103Figure 1 The spec
17、ified portions9Figure 2 Network Adapter communication software hierarchy.12Figure 3 Example of the equipment interface data recognition sequence .13Figure 4 Network Adapter functions .15Figure 5 Logic level17Figure 6 Character composition .19Figure 7 Timing requirements 19Figure 8 Format of equipmen
18、t interface data recognition service21Figure 9 Format of request command.22Figure 10 Format of response command 24Figure 11 Format of request command.25Figure 12 Format of response command 25BS EN 62480:200962480 IEC:2008(E) 3 Figure 13 Sequence of equipment interface data recognition service .26Fig
19、ure 14 Status change diagram 27Figure 15 Format of object generation type commands 31Figure 16 Operation of IASet (IASetM).33Figure 17 Operation of IASetup (IASetMup) .34Figure 18 Operation of IAGet (IAGetM) 35Figure 19 Operation of IAGetup (IAGetMup) 36Figure 20 Network Adapter status changes 37Fig
20、ure 21 Format of request command.39Figure 22 Format of response command 40Figure 23 Format of request command.41Figure 24 Format of response command 42Figure 25 Format of request command.43Figure 26 Format of response command 43Figure 27 Format of request command.44Figure 28 Format of response comma
21、nd 44Figure 29 Format of object data .45Figure 30 Format of equipment inquiry data .47Figure 31 Format of request command.47Figure 32 Format of response command 48Figure 33 Format of request command.49Figure 34 Format of response command 49Figure 35 Format of request command.50Figure 36 Format of re
22、sponse command 51Figure 37 Format of Object Data51Figure 38 Format of equipment inquiry data .53Figure 39 Format of request command.54Figure 40 Format of response command 55Figure 41 Format of request command.56Figure 42 Format of response command 57Figure 43 Format of request command.58Figure 44 Fo
23、rmat of response command 59Figure 45 Format of request command.60Figure 46 Format of response command 61Figure 47 Format of request command.62Figure 48 Format of response command 63Figure 49 Format of request command.64Figure 50 Format of response command 65Figure 51 Format of request command.67Figu
24、re 52 Format of Response Command .68Figure 53 Format of request command.70Figure 54 Format of response command 71Figure 55 Format of request command.72BS EN 62480:2009 4 62480 IEC:2008(E) Figure 56 Format of response command 73Figure 57 Communication error notification command74Figure 58 Equipment i
25、nterface data confirmation sequence .75Figure 59 Initialization sequence77Figure 60 Object construction sequence (1) .78Figure 61 Object construction sequence (2) .79Figure 62 Equipment status access request sequence .80Figure 63 Equipment status notification request sequence.80Figure 64 Element des
26、ignation equipment status access request sequence.81Figure 65 Element designation equipment status notification request sequence.81Figure 66 Object access request sequence82Figure A.1 Device object configuration example.86Figure B.1 Service primitive (obtain other node status: synchronous type) .89F
27、igure B.2 Service primitive (obtain other node status: asynchronous type) .90Figure B.3 Example of object view .90Figure B.4 Service primitive (control other node functions).91Figure B.5 Example of object view .91Figure B.6 Service primitive (notify other nodes of self-node status: synchronous type)
28、 .92Figure B.7 Service primitive (notify other nodes of self-node status: asynchronous type) .92Figure B.8 Example of object view .92Figure B.9 Example of AOJ configuration in a Node.93Figure C.1 Property map description format .94Figure D.1 Part of the non-composite messages type packet .95Figure D
29、.2 Part of the composite messages type packet 95Figure E.1 Type B Socket (Network-ready equipment side)99Figure E.2 Type B plug (Network Adapter side)100Figure E.3 Mating of Type B connector 101Figure E.4 Type A connecter pin arrangement for Network Adapter communication interfaces Pin assignment 1
30、.101Figure E.5 Type B connecter pin arrangement for Network Adapter communication interfaces Pin assignment 2 .102Table 1 Acceptable combinations of types supported by Network Adapters and types supported by Network-ready equipment 13Table 2 Specifications for supplying power Network-ready equipment
31、 (Class 1)17Table 3 Specifications for supplying power Network-ready equipment (Class 2)17Table 4 Specifications for supplying power Network-ready equipment (Class 3)17Table 5 Specifications for Supplying Power Network Adapter17Table 6 Timing requirements19Table 7 Definition of states 28Table 8 Obje
32、ct generation type interface command codes32Table 9 Classification of internal services 33Table 10 Communication sequences (object generation type) 75BS EN 62480:200962480 IEC:2008(E) 5 Table 11 Timeout values84Table A.1 Format of the AOJ85Table A.2 List of class codes by group code 87Table A.3 APC
33、allocation table.88Table E.1 Physical specifications for Type B connector97BS 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 techn
34、ology 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 em
35、bedded 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
36、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 (incl
37、uding 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. T
38、he 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 Net
39、work 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 exist
40、ing Home Network, routers or the gateways can be avoided. NOTE 3 For example, when an end-users 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-users network is based on home networking standard “A” (la
41、yer 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 a
42、ppliance. 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
43、 all existing network protocols. BS EN 62480:200962480 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 N
44、etwork-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 hardw
45、are. 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
46、referenced document (including any amendments) applies. None. Transmission media Network Adapter OSI layer 2 (Data link)OSI layer 3 (Network) OSI layer 4 (Transport)OSI layer 5 (Session)OSI layer 6 (Presentation)OSI layer 1 (physical)OSI layer 7 (Application)Adapter Interface OSI layer 7, Adapter In
47、terface Node A Network-ready equipment (home electric appliance) Cable Network adapter Node B Network-ready equipment (home electric appliance) Node C home electric appliance including all OSI layers CableBS EN 62480:2009 10 62480 IEC:2008(E) 3 Terms and definitions For the purposes of this document
48、, 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 th
