BS EN 62295-2009 Multimedia systems Common communication protocol for inter-connectivity on heterogeneous networks《多媒体系统 异构网络相互连通性用常见的通信协议》.pdf

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationMultimedia systems Common communication protocol for inter-connectivity on heterogeneous networksBS EN 62295:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 23/11/2011

2、 07:43, Uncontrolled Copy, (c) BSINational forewordThis British Standard is the UK implementation of EN 62295:2009. It is identical to IEC 62295:2007.The UK participation in its preparation was entrusted to Technical Committee EPL/100, Audio, video and multimedia systems and equipment.A list of orga

3、nizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. BSI 2011ISBN 978 0 580 76114 0 ICS 33.040.40; 33.160.01; 35.110Compliance wi

4、th a British Standard cannot confer immunity from legal obligations.This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 July 2011.Amendments issued since publicationAmd. No. Date Text affectedBRITISH STANDARDBS EN 62295:2009Licensed Copy: Wang

5、 Bin, ISO/EXCHANGE CHINA STANDARDS, 23/11/2011 07:43, Uncontrolled Copy, (c) BSIEUROPEAN STANDARD EN 62295 NORME EUROPENNE EUROPISCHE NORM August 2009 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnis

6、che 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 62295:2009 E ICS 33.040.40; 33.160; 35.100 English version Multimedia systems - Common communication protoco

7、l for inter-connectivity on heterogeneous networks (IEC 62295:2007) Systmes multimdia - Protocole de communication commun relatif la connectivit entre rseaux htrognes (CEI 62295:2007) Multimediasysteme - Gemeinsames Kommunikationsprotokoll fr die Zusammenschaltung von heterogenen Netzwerken (IEC 622

8、95:2007) 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 bibliog

9、raphical 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

10、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,

11、Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. BS EN 62295:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 23/11/2011 07:43, Uncontrolled Cop

12、y, (c) BSIEN 62295:2009 Foreword The text of document 100/1200/CDV, future edition 1 of IEC 62295, prepared by technical area 8, Multimedia home server systems, of IEC TC 100, Audio, video and multimedia systems and equipment, was submitted to the IEC-CENELEC parallel vote and was approved by CENELE

13、C as EN 62295 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 national standard or by endorsement (dop) 2010-04-01 latest date by which the national standards conflicting with the EN have to be withdraw

14、n (dow) 2012-07-01 _ Endorsement notice The text of the International Standard IEC 62295:2007 was approved by CENELEC as a European Standard without any modification. _ BS EN 62295:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 23/11/2011 07:43, Uncontrolled Copy, (c) BSI62295 IEC:2007(E

15、) CONTENTS INTRODUCTION. 8 1 Scope and object. 9 2 Normative references . 10 3 Terms, definitions, abbreviations and conventions . . 10 3.1 Terms and definitions . 10 3.2 Abbreviations .13 3.3 Conventions . 14 4 Requirements .14 4.1 Home server interface requirements . .15 4.1.1 Basic requirements f

16、or data delivery.15 4.1.2 Functional requirements for HNMP . 15 4.1.3 Home server interface requirements for unicast, multicast and broadcast . .15 4.2 CCP device requirements . .16 4.2.1 Requirements for device registration 16 4.2.2 Requirements for classification of CCP devices . 16 5 Common commu

17、nication protocol (CCP) layer 17 5.1 CCP layer17 5.2 Data delivery over heterogeneous networks .19 6 CCP addressing . .20 6.1 General .20 6.2 An addressing structure to facilitate traffic switching for the home server.Version 0 . .20 6.2.1 Domain address .21 6.2.2 Cluster address 21 6.2.3 Device ID

18、field . .21 7 CCP packet format and fields 21 7.1 General .21 7.2 CCP packet format 22 7.2.1 CCP identification (CCPID).22 7.2.2 CCP header version (CCPHDRVER) 22 7.2.3 CCP address version (CCPADDRVER). .23 7.2.4 Destination address (DESTADDR). .23 7.2.5 Source address (SRCADDR) . 23 7.2.6 Type (TYP

19、E) field . .23 7.2.7 Reserved (RSV) field .25 7.2.8 CCP payload length (CCPPLEN) field.25 7.2.9 CCP payload field.25 8 Home network management protocol (HNMP) . 25 8.1 General .25 8.2 HNMP packet format . .26 8.2.1 Transaction ID (TID) 26 8.2.2 HNMP command (HNMPCMD). 26 8.2.3 Reserved (RSV) field .

20、26 BS EN 62295:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 23/11/2011 07:43, Uncontrolled Copy, (c) BSI62295 IEC:2007(E) 8.2.4 HNMP payload length (HNMPPLEN) field 26 8.2.5 HNMP payload . 26 8.3 Home server registration 27 8.4 Device registration 27 8.4.1 Device registration request (

21、DEV_REG_REQ) packet 27 8.4.2 Device registration response (DEV_REG_RES) packet. 28 8.5 Device management29 8.5.1 Add device (ADD_DEV) packet31 8.5.2 Delete device (DEL_DEV) packet . 31 8.5.3 Initialize device (INI_DEV) packet. 32 8.5.4 Alive-check request (ALV_CHK_REQ) packet. 32 8.5.5 Alive-check r

22、esponse (ALV_CHK_RES) packet 32 8.6 Address and name information of devices 32 8.6.1 Device address and name information request (DEV_INFO_REQ) packet 33 8.6.2 Device address and name information response (DEV_INFO_RES) packet 33 8.7 Other management functions.34 9 Universal home control protocol (U

23、HCP) .34 9.1 UHCP packet format34 9.1.1 Transaction ID (TID) 35 9.1.2 Message type (MT) and action type (AT) . 35 9.1.3 Reserved (RSV) field .36 9.1.4 UHCP payload length (UHCPPLEN) field . 36 9.1.5 UHCP payload. .36 9.2 Execution messages (EXE) . 36 9.2.1 Execution of registration (EXE_REG) .36 9.2

24、.2 Execution of control (EXE_CTRL) . 37 9.2.3 Response OK (EXE_RESOK) . .38 9.2.4 Response NOK (EXE_RESNOK) .38 9.3 Query messages (QUE)38 9.3.1 Query of registration status (QUE_REGSTAT). .38 9.3.2 Query of control status (QUE_CTRLSTAT) 39 9.3.3 Query of all status (QUE_ALLSTAT) .39 9.3.4 Response

25、OK (QUE_RESOK). .40 9.3.5 Response NOK (QUE_RESNOK).40 9.4 Notification messages (NTFY) .40 9.5 UHCP payload syntax. 40 9.5.1 Basic syntax for UHCP payload .40 9.5.2 Syntax for UHCP registration. 41 9.5.3 Syntax for device control . .42 9.5.4 Syntax for query of controlling and monitoring status . .

26、 43 9.5.5 Syntax for notification 44 10 Home data service protocol (HDSP) .45 10.1 Functional requirements of HDSP.45 10.1.1 Interoperability with CCP . .45 10.1.2 File and directory services 45 10.1.3 Messaging service. 46 10.2 HDSP packet format46 BS EN 62295:2009Licensed Copy: Wang Bin, ISO/EXCHA

27、NGE CHINA STANDARDS, 23/11/2011 07:43, Uncontrolled Copy, (c) BSI62295 IEC:2007(E) 10.2.1 Transaction ID (TID) 46 10.2.2 HDSP command .46 10.2.3 HDSP payload length (HDSPPLEN) field . 47 10.2.4 HDSP payload . .47 10.3 Messages for directory services . 47 10.3.1 Query request message (DIR_QUE_REQ) .

28、. 48 10.3.2 Query response message (DIR_QUE_RES).48 10.3.3 Deletion request message (DIR_DEL_REQ) . 49 10.3.4 Deletion response message (DIR_DEL_RES) . 49 10.3.5 Renaming request message (DIR_REN_REQ) 49 10.3.6 Renaming response message (DIR_REN_RES) .49 10.3.7 Making request message (DIR_MAKE_REQ)

29、. .49 10.3.8 Making response message (DIR_MAKE_RES). .50 10.4 Messages for file services . 50 10.4.1 Query request message (FILE_QUE_REQ) 53 10.4.2 Query response message (FILE_QUE_RES) 53 10.4.3 Deletion request message (FILE_DEL_REQ) . . 53 10.4.4 Deletion response message (FILE_DEL_RES) .53 10.4.

30、5 Renaming request message (FILE_REN_REQ) 53 10.4.6 Renaming response message (FILE_REN_RES) . 54 10.4.7 Negotiation request message (FILE_NEGO_REQ) . 54 10.4.8 Negotiation response message (FILE_NEGO_RES) 54 10.4.9 Getting request message (FILE_GET_REQ). 54 10.4.10 Getting response message (FILE_GE

31、T_RES) . 54 10.4.11 Putting request message (FILE_PUT_REQ) . 55 10.4.12 Putting response message (FILE_PUT_RES) . . 55 10.5 Messages for messaging service. .55 10.5.1 Sending request message (MSG_PUT_REQ) . 56 10.5.2 Sending response message (MSG_PUT_RES) .56 10.6 Error codes . .56 11 Home multimedi

32、a service protocol (HMSP) . 57 11.1 Functional requirements of HMSP 58 11.1.1 Interoperability with CCP . .58 11.1.2 Management of multimedia resource . 58 11.1.3 Stream and play of multimedia resource 58 Annex A (informative) FSM of FS-CCPDEV supporting HNMP . .60 Annex B (informative) FSM of FS-CC

33、PDEV for supporting UHCP .63 Figure 1 Communication layer structures of network technologies . 10 Figure 2 Server interface . 11 Figure 3 Cluster and domain network .12 Figure 4 Classification of CCP devices . 16 Figure 5 Definitions of application program, CCP API, lower protocol layers interface,

34、and lower protocol layers .18 Figure 6 Location of CCP layer . 18 Figure 7 Example of data transmission over heterogeneous networks using CCP layer . 20 BS EN 62295:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 23/11/2011 07:43, Uncontrolled Copy, (c) BSI62295 IEC:2007(E) Figure 8 CCP a

35、ddress format of CCP address by version 0 .21 Figure 9 CCP packet format of CCP header by version 0 . 22 Figure 10 Type fields 23 Figure 11 HNMP packet format . 26 Figure 12 DEV_REG_REQ and DEV_REG_RES packets . 28 Figure 13 Example of HNMP command sequence for device registration 29 Figure 14 ADD_D

36、EV, DEL_DEV and INI_DEV packets . .30 Figure 15 ALV_CHK_REQ and ALV_CHK_RES packets . .30 Figure 16 Example of HNMP command sequence for device management. 31 Figure 17 DEV_INFO_REQ and DEV_INFO_RES packets .33 Figure 18 Example of HNMP command sequence for retrieving device address and name informa

37、tion . .33 Figure 19 UHCP packet format . 35 Figure 20 Message type and action type fields of UHCP packet 36 Figure 21 Example of registration process 37 Figure 22 Example of EXE_CTRL message 38 Figure 23 Example of QUE_REGSTAT message39 Figure 24 Example of QUE_CTRLSTAT message . 39 Figure 25 Examp

38、le of QUE_ALLSTAT message .40 Figure 26 HDSP packet format. .46 Figure 27 Example of usage of directory service messages . . 50 Figure 28 Example of usage of file service messages . . 52 Figure 29 Example of usage of Messaging service messages . 56 Figure A.1 FSM of FS-CCPDEV for supporting HNMP.60

39、Figure B.1 FSM of FS-CCPDEV for supporting UHCP .63 Table 1 Cast type field 24 Table 2 Traffic type field . .24 Table 3 Payload type field. .25 Table 4 HDSP commands 47 Table 5 Messages for directory services . 48 Table 6 Messages for file services . 51 Table 7 Messages for messaging services 55 Tab

40、le 8 Error codes for HDSP. 57 BS EN 62295:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 23/11/2011 07:43, Uncontrolled Copy, (c) BSI 8 62295 IEC:2007(E) INTRODUCTION Numerous wired and wireless home network technologies of various types have been developed and are in use today. However,

41、 since these technologies have been developed for specific functions such as control, A/V and data services, interoperability is not guaranteed among products employing these technologies. Hence, users who wish to implement the home network environment either purchase devices that are based on a sin

42、gle technology for interoperability or install independent, non-compatible networks in their home. To solve these problems, home network businesses and service providers have taken into account and developed a number of specific technologies in order to allow interoperability among home network tech

43、nologies. However, most of these technologies are local and offer interoperability between a limited range of devices and give rise to new problems caused by complexity and diversity in technologies of different companies. In order to incorporate such complex and diverse technologies, there is a nee

44、d to develop a new convergence technology that can integrate not only current technologies but also those expected to surface in the future. The needs for the new convergence technology are the following: provide interoperability and interconnectivity among heterogeneous networks through a specific

45、convergence layer; provide expandability for applications in not only current network technologies, but also new technologies to be developed in the future; are applicable in small devices with low processing capabilities by providing protocols such as simple signaling in the convergence layer; avai

46、lable at a low cost and simple to implement on a device; able to provide diverse home network services (or applications). BS EN 62295:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 23/11/2011 07:43, Uncontrolled Copy, (c) BSI62295 IEC:2007(E) 9 MULTIMEDIA SYSTEMS COMMON COMMUNICATION PRO

47、TOCOL FOR INTER-CONNECTIVITY ON HETEROGENEOUS NETWORKS 1 Scope and object This International Standard specifies the common communication protocol (CCP) layer that is capable of providing interoperability and interconnectivity between heterogeneous network technologies, as well as the basic data tran

48、smission scheme between devices linked to heterogeneous networks through the CCP layer. The standard also specifies the packet structure in the CCP layer and the common addressing scheme that can be understood among heterogeneous devices. Furthermore, there are specifications regarding protocols cap

49、able of providing diverse home network applications through the CCP layer such as the home network management protocol (HNMP), universal home control protocol (UHCP), home multimedia service protocol (HMSP) and home data service protocol (HDSP). NOTE HNMP is the overall home network management protocol that detects or registers devices. UHCP controls and monitors devices from remote locations. HMSP is the A/V protocol for hom