EN 62295:2009

SLOVENSKI STANDARD
01-oktober-2009
9HþSUHGVWDYQRVWQLVLVWHPL6NXSQLNRPXQLNDFLMVNLSURWRNRO]DRVQRYQR
SRYH]RYDQMHVKHWHURJHQLPLRPUHåML,(&
Multimedia systems - Common communication protocol for inter-connectivity on
heterogeneous networks (IEC 62295:2007)
Multimediasysteme - Gemeinsames Kommunikationsprotokoll für die
Zusammenschaltung von heterogenen Netzwerken (IEC 62295:2007)
Systèmes multimédia - Protocole de communication commun relatif à la connectivité
entre réseaux hétérogènes (CEI 62295:2007)
Ta slovenski standard je istoveten z: EN 62295:2009
ICS:
35.110 Omreževanje Networking
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 62295
NORME EUROPÉENNE
August 2009
EUROPÄISCHE NORM
ICS 33.040.40; 33.160; 35.100
English version
Multimedia systems -
Common communication protocol
for inter-connectivity on heterogeneous networks
(IEC 62295:2007)
Systèmes multimédia -  Multimediasysteme -
Protocole de communication commun Gemeinsames Kommunikationsprotokoll
relatif à la connectivité für die Zusammenschaltung
entre réseaux hétérogènes von heterogenen Netzwerken
(CEI 62295:2007) (IEC 62295: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 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 62295:2009 E
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 CENELEC 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 withdrawn (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.
__________
IEC 62295
Edition 1.0 2007-11
INTERNATIONAL
STANDARD
Multimedia systems – Common communication protocol for inter-connectivity
on heterogeneous networks
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XB
ICS 33.040.40; 33.160; 35.100 ISBN 2-8318-9351-8

– 2 – 62295 © IEC:2007(E)
CONTENTS
FOREWORD.6
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 for 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 communication protocol (CCP) layer.17
5.1 CCP layer.17
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 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 (TYPE) 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.26

62295 © IEC:2007(E) – 3 –
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 (DEV_REG_REQ) packet.27
8.4.2 Device registration response (DEV_REG_RES) packet.28
8.5 Device management.29
8.5.1 Add device (ADD_DEV) packet.31
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 response (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 (UHCP) .34
9.1 UHCP packet format.34
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.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 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.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 format.46

– 4 – 62295 © 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).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).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.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_GET_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 multimedia 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-CCPDEV 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,
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

62295 © IEC:2007(E) – 5 –
Figure 8 – CCP address 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_DEV, 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 information .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 message.39
Figure 24 – Example of QUE_CTRLSTAT message .39
Figure 25 – Example 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
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
Table 8 – Error codes for HDSP.57

– 6 – 62295 © IEC:2007(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
MULTIMEDIA SYSTEMS –
COMMON COMMUNICATION PROTOCOL
FOR INTER-CONNECTIVITY ON HETEROGENEOUS NETWORKS

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 rendered 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 62295 has been prepared by technical area 8: Multimedia home
server systems, of IEC technical committee 100: Audio, video and multimedia systems and
equipment.
The text of this standard is based on the following documents:
CDV Report on voting
100/1200/CDV 100/1283/RVC
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.

62295 © IEC:2007(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 – 62295 © IEC:2007(E)
INTRODUCTION
Numerous wired and wireless home network technologies of various types have been
developed and are in use today. However, 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 single 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 technologies. 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 need 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 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;
– available at a low cost and simple to implement on a device;
– able to provide diverse home network services (or applications).

62295 © IEC:2007(E) – 9 –
MULTIMEDIA SYSTEMS –
COMMON COMMUNICATION PROTOCOL
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 transmission 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
capable 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 home entertainment services. HDSP
deals with data and messaging services.
This standard is to be applied to systems with network capabilities and those that constitute
home networks such as electronic appliances, A/V components, control devices, network
terminals and home servers. Moreover, this standard is applicable to a home network
consisting of a single home server.
This International Standard gives
– a definition of the CCP layer,
– a data transmission scheme in the CCP layer,
– a CCP packet structure,
– a CCP addressing scheme,
– a home network management protocol (HNMP),
– a universal home control protocol (UHCP),
– a home data service protocol (HDSP),
– requirements of home multimedia service protocol (HMSP).
A home network provides interoperability and interconnectivity regardless of the appliance
manufacturer or the network type so that the user is able to receive desired services at any
point in time. However, current home network technologies have independent communication
protocol layer structures, as shown in Figure 1, with different addressing schemes, data
transmission schemes, data processing methods and data formats.
In order to solve problems associated with interoperability and interconnectivity among
heterogeneous network technologies, this standard aims to define the CCP layer as a type of
a convergence layer.
Further objectives of this standard include specifying the data transmission method, packet
structure and common addressing scheme as well as the signaling protocol for providing
home network management, control, A/V and data services.

– 10 – 62295 © IEC:2007(E)
Application
Application
Application Application
Presentation Application
RFCOMM/SDP
L2CAP
Session
Transaction Session
HCI
Transport TCP/UDP Transport
Link Manager
Network IP Link Network
Link Controller
Data Link Link Link
Baseband
Physical Physical Physical Physical
Radio
OSI 7 Layer TCP/IP IEEE1394 LonTalk Bluetooth

IEC  2072/07
Figure 1 – Communication layer structures of network technologies
2 Normative references
None.
3 Terms, definitions, abbreviations and conventions
For the purposes of this document, the following definitions apply.
3.1 Terms and definitions
3.1.1
CCP device
device which has networking capabilities using commercial network technologies to link to a
home network; it also supports at least home network management protocol (HMNP) among
four protocols provided in the CCP layer and CCP
3.1.2
CCP addressing
common addressing scheme used in the CCP layer which consists of four fields: domain
address, cluster address and device ID
NOTE One of the characteristics of CCP addressing is that it has a structure that is understood by application
programs embedded in devices linked to heterogeneous networks as well as the device users.
3.1.3
home server interface
HSI
interface module in a home server responsible for connection with a particular network which
can process the corresponding physical interface and the communication protocol according
to the type of network it is connected to
NOTE A home server interface is shown in Figure 2.

62295 © IEC:2007(E) – 11 –
: Device
Home Server
Network A Network B
HSI HSI
Home server
internal
processing
block
Network C Network C
HSI HSI
IEC  2073/07
Figure 2 – Server interface
3.1.4
cluster network
collection of devices using an identical physical interface and communication protocol
NOTE 1 As shown in Figure 3, a cluster network is a collection of devices using an identical physical interface
and communication protocol. Moreover, a HSI that links a home server to the devices within the cluster network is
also part of the cluster network. A cluster address is one of the CCP addressing fields defined in the CCP layer,
and it is used to distinguish multiple cluster networks linked to a single home server.
NOTE 2 A HSI that links a home server to the devices within the cluster network is also part of the cluster network.
NOTE 3 A cluster network is shown in Figure 3.
3.1.5
cluster address
one of the CCP addressing fields defined in the CCP layer which is used to distinguish
multiple cluster networks linked to a single home server
NOTE A cluster address is shown in Figure 3.

– 12 – 62295 © IEC:2007(E)
Domain network
Home Home
server
server
Cluster network
Home
server
: Home server interface
: Cluster network
: Domain network
IEC  2074/07
Figure 3 – Cluster and domain network
3.1.6
domain network
collection of devices connected to a single home server
NOTE 1 Devices within the multiple cluster networks linked to the home server and the HSIs managing the cluster
network interface constitute the domain network.
NOTE 2 A domain network is shown in Figure 3.
3.1.7
domain address
one of the CCP addressing fields defined in the CCP layer which is used to distinguish
multiple domain networks in the home.
NOTE A domain address is shown in Figure 3.
3.1.8
single-HS network
a home network comprising a single home server where there is only one domain network
under the single-HS network environment
3.1.9
multi-HS network
a home network with two or more home servers where there are multiple domain networks
under the multi-HS network environment
NOTE A multi-HS network is shown in Figure 3.

62295 © IEC:2007(E) – 13 –
3.1.10
CCP application program
a CCP application program is positioned at the top of the CCP layer. A CCP application
program sends and receives data to/from CCP layer through CCP application programming
interface
3.1.11
application program data unit
APDU
the unit of data exchanged among multiple application programs on an equivalent level
3.1.12
CCP application programming interface(API)
the interface between the application program and the CCP layer
3.1.13
lower protocol layers
lower protocol layers refer to all communication protocol layers below the CCP layer, with the
exception of the physical layer
NOTE A diagram of lower protocol layers is shown in Figure 5.
3.1.14
lower protocol layers interface
the interface between the APDU and lower protocol layers which are referred to as the lower
protocol layers interface
NOTE A diagram of lower protocol layers interface is shown in Figure 5.
3.2 Abbreviations
ACDS Active Control & Data Service
ACMS Active Control & Multimedia Service
ACS Active Control Service
ALLSTAT All Status
APDU Application Program Data Unit
API Application Program Interface
AT Action Type
ATTR Attribute
CCP Common Communication Protocol
CCPADDRVER CCP Address Version
CCPDEV CCP Device
CCPH CCP Header
CCPHDRVER CCP Header Version
CCPID CCP Identification
CCPPLEN CCP Payload Length
CMD Command
CT Cast Type
CTRLSTAT Control Status
DATALEN Data Length
DEV Device
DMS Data & Multimedia Service
DS Data Service
– 14 – 62295 © IEC:2007(E)
DSTADDR Destination Address
ERRCODE Error Code
FMTS Final Maximum Transfer Size
FS Full Service
FSM Finite State Machine
HDSP Home Data Service Protocol
HDSPPLEN HDSP Payload Length
HMSP Home Multimedia Service Protocol
HNMP Home Network Management Protocol
HNMPCMD HNMP Command
HNMPPLEN HNMP Payload Length
HS Home Server
HSI Home Server Interface
MCS Monitoring Control Service
MON Monitoring
MS Multimedia Service
MT Message Type
MTS Maximum Transfer Size
MYMTS My Maximum Transfer Size
PATHLEN Path Length
PCS Passive Control Service
PnP Plug-and-Play
PT Payload Type
QoS Quality of Service
REG Registration
REGSTAT Registration Status
RES Response
SEC Second
SEGNO Segmentation Number
SEQNO Sequence Number
SRCADDR Source Address
STAT Status
TID Transaction ID
TT Traffic Type
UHCP Universal Home Control Protocol
UHCPPLEN UHCP Payload Length
3.3 Conventions
UHCP payload content is expressed as italic character as follows:
E.g. argument
4 Requirements
This clause describes the requirements in order to implement the HSI and CCP devices.

62295 © IEC:2007(E) – 15 –
4.1 Home server interface requirements
The HSI shall satisfy the following requirements.
4.1.1 Basic requirements for data delivery
– In order to support the device registration process, the HSI shall be able to receive all
packets being broadcast to the cluster network from the physical layer and relay them to
the CCP layer.
– The HSI shall maintain and manage an address table that contains the CCP addresses of
CCP devices in its cluster network as well as the physical addresses used in the cluster
network.
– Upon completion of the device registration process, when delivering packets to a
particular CCP device within its cluster network, the HSI shall be able to transmit packets
from the physical layer using the CCP device’s physical address that corresponds to the
CCP destination address.
– An HSI shall support the CCP layer as well as the requirements specified in 4.1. HSI can
be implemented with the card module-type for the physical interface, communication
protocol and the CCP layer.
4.1.2 Functional requirements for HNMP
– After receiving a Device Registration Request (DEV_REG_REQ) packet, the HSI shall be
able to send a Device Registration Response (DEV_REG_RES) packet to the CCP device
from which the DEV_REG_REQ packet originated.
– The HSI shall be able to store CCP and physical addresses of the CCP device contained
in the DEV_REG_REQ packet in the address table.
– The HSI shall be able to allocate a unique Device ID to the CCP device from which the
DEV_REG_REQ packet originated. The HSI shall also specify data such as the allocated
Device ID, domain address and the HSI’s own physical address in DEV_REG_RES
packet’s HNMP payload prior to transmission.
– The HSI shall be able to notify the fact that a new CCP device has been registered in the
home network to all CCP devices within its cluster network as well as all other HSIs in its
domain network by transmitting an Add Device (ADD_DEV) packet.
– In order to support CCP device’s Plug-and-Play (PnP) function, the HSI shall send on a
regular basis an Alive-Check Request (ALV_CHK_REQ) packet to the CCP devices that
have completed the device registration process and assess the response packets from
them. The HSI shall be able to determine that the non-responsive CCP devices have lost
connection with the home network.
– The HSI shall be able to notify the fact that a particular CCP device has been
disconnected from the home network to all CCP devices within its cluster network as well
as all other HSIs in its domain network by transmitting a Delete Device (DEL_DEV) packet.
4.1.3 Home server interface requirements for unicast, multicast and broadcast
– The HSI shall be able to process all packets received at its physical layer from the
physical layer to lower protocol layers before sending them to the CCP layer.
– The HSI shall be able to examine the cluster address in the CCP destination address field
of a packet arriving at the CCP layer through lower protocol layers and send the packet to
the HSI responsible for the interface of the cluster network that corresponds to the cluster
address.
– When a CCP packet arrives from another HSI
• if the cast type of the received CCP packet is unicast and the CCP destination address
is specified, then the HSI receiving the packet shall be able to relay the packet to the
particular CCP device within its cluster network,
• if the cast type of the received CCP packet is multicast, then the HSI receiving the
packet shall be able to relay the packet to only the restricted number of the CCP
devices within its cluster network in accordance with the content of the multicast,

– 16 – 62295 © IEC:2007(E)
• if the cast type of the received CCP packet is broadcast, then the HSI receiving the
packet shall be able to relay the packet to all CCP devices within its cluster network.
4.2 CCP device requirements
This subclause specifies the requirements for the device registration process needed for CCP
devices to perform the plug-and-play function, as well as the requirements for classifying CCP
devices according to the CCP functions provided by CCP devices.
4.2.1 Requirements for device registration
– If a CCP device is not aware of the physical address of the HSI of its own cluster network,
the HSI’s physical address (or network address) shall be obtained through the device
registration process.
– For the purpose of device registration, a CCP device shall be able to initially broadcast a
device registration request (DEV_REG_REQ) packet to its own cluster network.
– Upon completion of the device registration process, when a CCP device transmits data to
a heterogeneous network, it shall send all packets from the physical layer to the HSI of its
own cluster network, regardless of the cast type and the CCP destination address.
4.2.2 Requirements for classification of CCP devices
CCP devices refer to devices that support HNMP among the functions provided by the CCP
layer and the CCP. CCP devices can be classified according to their processing capabilities
and the network technologies being used. This standard shall classify CCP devices into nine
categories according to the functions provided by the CCP devices, as shown in Figure 4.
Data Service
(HDSP)
DS-CCPDEV
ACDS-CCPDEV
DMS-CCPDEV
FS-CCPDEV
PCS-CCPDEV
Passive Control Service
(UHCP)
ACS
...