SIST-TS CLC/TS 52056-8-7:2015

SLOVENSKI STANDARD
01-junij-2015
,]PHQMDYDSRGDWNRYSULPHUMHQMXHOHNWULþQHHQHUJLMH1L]'/06&26(0GHO
3/&SURILO]DGDSWLYQLPVSHNWURP]YHþQRVLOQLPLIUHNYHQFDPL]DRPUHåMD&;
Electricity metering data exchange - The DLMS/COSEM suite - Part 8-7: The adaptive
multi-carrier spread-spectrum PLC profile for CX1 networks
Ta slovenski standard je istoveten z: CLC/TS 52056-8-7:2015
ICS:
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
91.140.50 Sistemi za oskrbo z elektriko Electricity supply systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

TECHNICAL SPECIFICATION CLC/TS 52056-8-7

SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
April 2015
ICS 35.240.60; 91.140.50
English Version
Electricity metering data exchange - The DLMS/COSEM suite -
Part 8-7: AMC-SS PLC communication profile for neighbourhood
networks
This Technical Specification was approved by CENELEC on 2014-11-11.

CENELEC members are required to announce the existence of this TS in the same way as for an EN and to make the TS available promptly
at national level in an appropriate form. It is permissible to keep conflicting national standards in force.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2015 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. CLC/TS 52056-8-7:2015 E

CONTENTS
Foreword . 4
1 Scope . 5
2 Normative references . 5
3 Abbreviations . 6
4 Targeted communication environments . 8
5 Reference model . 9
6 Physical Layer (PHY) . 10
6.1 Overview – main features and functions . 10
6.2 PHY layer services . 10
7 Data Link Layer . 11
7.1 Functions and structure . 11
7.2 The Medium Access Control sub-layer. 13
7.3 The Logical Link Control sub-layer . 13
7.3.1 Overview . 13
7.3.2 Layer-2-network management functions . 13
7.3.3 Communication functions . 14
7.3.4 Segmentation and reassembly . 14
7.4 The Convergence sub-layer . 14
7.4.1 Overview . 14
7.4.2 DLMS/COSEM AL specific convergence sub-layer . 14
7.4.3 IPv4 specific convergence sub-layer . 19
7.4.4 IPv6 specific convergence sub-layer . 26
7.5 Identification and addressing . 32
8 Upper layers (Session, Presentation, Application) . 33
8.1 Overview . 33
8.2 Mapping of application layer services . 34
8.3 Registration services . 35
8.3.1 Overview . 35
8.3.2 CL_control.indication . 35
8.3.3 CL_IPv4_control.indication . 36
8.3.4 CL_IPv6_control.indication . 37
9 Data Model . 38
Annex A (normative) IP header compression parameters. . 39
Annex B (informative) Data exchange examples . 40
B.1 Data retrieval from slave node . 40
B.2 Data retrieval error case . 41

List of Figures
Figure 1 – Communication architecture . 8
Figure 2 – DLMS/COSEM AMC-SS PLC architecture . 9
Figure 3 – Primitives between layer 2 and layer 1 . 11
Figure 4 – Structure of Data Link Layer . 11
Figure 5 – DLMS/COSEM AL specific primitives between higher layer and layer 2 in a
bidirectional data transmission . 12

– 3 – CLC/TS 52056-8-7:2015
Figure 6 – DLMS/COSEM AL specific primitives between higher layer and layer 2 in
the case of broadcast . 12
Figure 7 – DLMS/COSEM AL specific primitives between higher layers and layer 2 in
the case of an unsolicited data transmission . 13
Figure 8 – The IPv4 communication architecture . 20
Figure 9 – The IPv6 communication architecture . 26
Figure 10 – Mapping of the DLMS/COSEM Application layer services . 34
Figure 11 – Registration services specific for DLMS/COSEM AL . 36
Figure 12 – IPv4 registration services . 37
Figure 13 – IPv6 registration services . 38
Figure B 1 – Successful GET command specific for DLMS/COSEM AL . 40
Figure B 2 – Data retrieval error case specific for DLMS/COSEM AL . 41
List of Tables
Table 1 – Coding of the DLC extended control field . 14
Table 2 – Mapping of CL_data.request to DL_data.request in the master node . 15
Table 3 – Mapping of CL_data.request to DL_data.request in the slave node . 16
Table 4 – Mapping of DL_data.indication to CL_data.indication in the master node. 17
Table 5 – Mapping of DL_data.indication to CL_data.indication in the slave node . 17
Table 6 – Mapping of DL_data_identifier.confirm to CL_data_request.confirm in the
master node . 18
Table 7 – Mapping of DL_data_identifier.confirm to CL_data_request.confirm in the
slave node . 19
Table 8 – Reserved SAP values on the master node side . 19
Table 9 – Reserved SAP values on the slave node side . 19
Table 10 – Mapping of CL_IPv4_data.request to DL_data.request in the master node . 21
Table 11 – Mapping of CL_IPv4_data.request to DL_data.request in the slave node . 22
Table 12 – Mapping of DL_data.indication to CL_IPv4_data.indication in the master
node . 23
Table 13 – Mapping of DL_data.indication to CL_IPv4_data.indication in the slave
node . 23
Table 14 – Mapping of DL_data_identifier.confirm to CL_IPv4_data_request.confirm in
the master node . 25
Table 15 – Mapping of DL_data_identifier.confirm to CL_IPv4_data_request.confirm in
the slave node . 25
Table 16 – Mapping of CL_IPv6_data.request to DL_data.request in the master node . 28
Table 17 – Mapping of CL_IPv6_data.request to DL_data.request in the slave node . 28
Table 18 – Mapping of DL_data.indication to CL_IPv6_data.indication in the master
node . 29
Table 19 – Mapping of DL_data.indication to CL_IPv6_data.indication in the slave
node . 30
Table 20 – Mapping of DL_data_identifier.confirm to CL_IPv6_data_request.confirm in
the master node . 31
Table 21 – Mapping of DL_data_identifier.confirm to CL_IPv6_data_request.confirm in
the slave node . 32
Table 22 – Mapping of DL_control.indication to CL_control.indication . 36
Table 23 – Mapping of DL_control.indication to CL_IPv4_control.indication . 37
Table 24 – Mapping of DL_control.indication to CL_IPv6_control.indication . 38

Foreword
This document (CLC/TS 52056-8-7:2015) has been prepared by CLC/TC 13 "Electrical energy
measurement and control".
The following date is fixed:
(doa) 2015-07-24
• latest date by which the existence of
this document has to be announced
at national level
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such
patent rights.
This document has been prepared under a mandate given to CENELEC by the European Commission
and the European Free Trade Association.

– 5 – CLC/TS 52056-8-7:2015
1 Scope
This Technical Specification specifies the DLMS/COSEM communication profile using a
compatibly-extendable form (CX1) of Adaptive Multi-Carrier Spread-Spectrum (AMC-SS) PLC
for neighbourhood networks. Its structure is in line with the DLMS/COSEM framework as
described in EN 62056-1-0[GK1].
The transport layer, the application layer and the data model are as specified in the EN 62056
DLMS/COSEM suite.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
CLC/TS 50590:2015, Electricity metering data exchange - Lower layer PLC profile using
Adaptive Multi-Carrier Spread-Spectrum for CX1 networks
EN 61334-4-32:1996, Distribution automation using distribution line carrier systems – Part 4 :
Data communication protocols – Section 32: Data link layer – Logical link control (LLC)
(IEC 61334-4-32:1996)
EN 61334-4-1:1996, Distribution automation using distribution line carrier systems – Part 4 :
Data communication protocols – Section 1: Reference model of the communication system
(IEC 61334-4-1:1996)
EN 62056-5-3, Electricity metering data exchange – The DLMS/COSEM suite – Part 5-3:
DLMS/COSEM application layer (IEC 62056-5-3)
EN 62056-6-1, Electricity metering data exchange – The DLMS/COSEM suite – Part 61: OBIS
Object identification system (IEC 62056-6-1)
EN 62056-6-2, Electricity metering data exchange – The DLMS/COSEM suite – Part 62:
Interface classes (IEC 62056-6-2)
FprEN 62056-4-7:2014, Electricity metering data exchange - The DLMS/COSEM suite – Part
4-7: DLMS/COSEM transport layer for IP networks (IEC 62056-4-7:201X, 13/1570/CDV)
EN 62056-9-7:2013, Electricity metering data exchange – The DLMS/COSEM Suite – Part 9-
7: Communication profile for TCP-UDP/IP networks (IEC 62056-9-7:2013)
RFC 2507 - IP Header Compression. Authors: M. Degermark, B. Nordgren, S. Pink. February
1999. Available from http://tools.ietf.org/html/rfc2507
Ipv4 TOS Byte and Ipv6 Traffic Class Octet http://www.iana.org/assignments/ipv4-tos-
byte/ipv4-tos-byte.xml
3 Abbreviations
.cnf .confirm (primitive)
.ind .indication (primitive)
.req .request (primitive)
.res .response (primitive)
ACSE Association Control Service Element
AL Application Layer
AMC-SS Adaptive Multi-Carrier Spread Spectrum
AP Application Process
A-PDU Application Protocol Data Unit
ASE Application Service Element
CENELEC European Committee for Electrotechnical Standardization
CIN Channel Identification Number
CL Convergence Sub-Layer
COSEM Companion Specification for Energy Metering
CRC Cyclic Redundancy Check
CX1 Compatibly Extendable form of AMC-SS PLC
D8PSK Differential Eight-Phase Shift Keying
DBLMAX Maximum Data Block Length
DBPSK Differential Binary Phase Shift Keying
DID Device Identifier
DL Data Link
DLL Data Link Layer (layer 2)
DLMS Device Language Message Specification
DLS Data Link Service
DP Data Priority
DPSK Differential Phase Shift Keying
DQPSK Differential Quaternary Phase Shift Keying
DSAP Destination Service Access Point
FEC Forward Error Correction
HES (Metering) Head End System
Hz Hertz
IEC International Electrotechnical Commission
IP Internet Protocol
IPv4 Internet Protocol, version 4
IPv6 Internet Protocol, version 6
kHz kilo Hertz
LA Link Address
LCN Link Channel Number
LLC Logical Link Control (sub-layer)
L-SAP Data Link Layer Service Access Point
LNAP Local Network Access Point

– 7 – CLC/TS 52056-8-7:2015
MAC Medium Access Control (sub-layer)
MPDU MAC Protocol Data Unit
N_NIN Network Identification Number of a network node
NIN Network Identification Number
NN Neighbourhood Network
NNAP Neighbourhood Network Access Point
OBIS OBject Identification System
OSI Open System Interconnection
PDU Protocol Data Unit
PHY Physical
PLC Power-Line Communications
PPDU PHY Protocol Data Unit
SAP Service Access Point
SDU Service Data Unit
SSAP Source Service Access Point
TCP Transmission Control Protocol
xDLMS_ASE extended DLMS Application Service Element

4 Targeted communication environments
The DLMS/COSEM PLC AMC-SS communication profile is intended for remote data exchange
on Neighbourhood Networks (NN) between Neighbourhood Network Access Points (NNAP)
and Local Network Access Points (LNAPs) or End Devices using AMC-SS technology over the
low voltage electricity distribution network as a communication medium at the C interface. The
functional reference architecture is shown in Figure 1.
Electricity Metering End Device
Meter application functions
I
Meter communication functions
M
L
NN LN
C Local Network Access Point (LNAP)
N
C
Neigbourhood Network Access Point (NNAP)
WAN
AMI Head End System
Figure 1 – Communication architecture
End devices – typically electricity meters – comprise application functions and communication
functions. They may be connected directly to the NNAP via the C interface, or to an LNAP via
an M interface, while the LNAP is connected to the NNAP via the C interface. The LNAP
function may be co-located with the metering functions.
A NNAP comprises gateway functions and it may comprise concentrator functions. Upstream,
it is connected to the Metering Head End System (HES) using suitable communication media
and protocols.
End devices and LNAPs may communicate to different NNAPs, but to one NNAP only at a
time. From the PLC communication point of view, the NNAP acts as the master node while
end devices and LNAPs act as slave nodes.
NNAPs and similarly LNAPs may communicate to each other, but this is out of the scope of
this specification, which covers the C interface only.
When the NNAP has concentrator functions, it acts as a DLMS/COSEM client. When the
NNAP has gateway functionality only, then the HES plays the role of a DLMS/COSEM client.
The end devices or the LNAPs play the role of DLMS/COSEM servers.

– 9 – CLC/TS 52056-8-7:2015
5 Reference model
The proposed protocol stacks use the following OSI layers as shown in Figure 2.

Figure 2 – DLMS/COSEM AMC-SS PLC architecture
The protocol layer are:
• the DLMS/COSEM data model as specified in EN 62056-6-1 and EN 62056-6-2;
• the DLMS/COSEM Application layer as specified in EN 62056-5-3 covering the Application,
Presentation and Session functionalities;

• the DLMS/COSEM transport layer as specified in FprEN 62056-4-7:2014, used with the
DLMS/COSEM TCP-UDP/IPv4 or TCP-UDP/IPv6 profile over AMC-SS, if IP transport is
used;
• the IPv4 or the IPv6 network layer, if IP transport is used;
• the AMC-SS Data link layer, which consists of the Convergence, LLC and MAC sub-layers;
• the AMC-SS Physical layer.
NOTE The Physical layer and data link layer service primitives are specified in CLC/TS 50590[GK2].
6 Physical Layer (PHY)
6.1 Overview – main features and functions
This layer provides the interface between the equipment and the physical transmission
medium that is the low-voltage distribution network. It transmits and receives MPDUs between
neighbour nodes. The AMC-SS PHY uses a fast frequency-hopping spread spectrum
technique combined with Differential Phase Shift Keying (DPSK) and forward error-correcting
coding. Three differential modulation schemes are used: DBPSK, DQPSK and D8PSK. The
system operates in the CENELEC A-band. This band covers the frequency range from 3 kHz
up to 95 kHz. Frequencies in this band shall only be used for applications for monitoring or controlling
the low-voltage distribution network, including energy usage of connected equipment and premises.
A typical example of an application in this band would be metering communications.
This technique provides the following advantages:
• Robustness against time-frequency-selective fading;
• Robustness against pulse and narrowband interference, pulsating non-gaussian noise and
combinations of them;
• Robustness against unwanted intermodulation effects;
• Low linearity requirements for the analogue front end;
• High power efficiency as a result of low peak to average ratio of the transmitted signal;
• Good electromagnetic compatibility between neighbouring systems.
The physical layer of AMC-SS is defined in Clause 5 of CLC/TS 50590:2015. The parameters
of the physical layer are preconfigured.
6.2 PHY layer services
PHY services are generated by the MAC layer entity whenever data is to be transmitted to a
peer MAC entity or entities, and passed to the PHY entity to request the sending of a PPDU to
one or more remote PHY using the PHY transmission procedures. The primitives which are
used between the MAC layer and the PHY layer are shown in Figure 3.

– 11 – CLC/TS 52056-8-7:2015
P_data.request
P_data.indication
Physical
medium
P_data.request
P_data.indication
MAC PHY PHY MAC
Figure 3 – Primitives between layer 2 and layer 1
The data, received from the MAC layer, is FEC-encoded. The encoded bit-sequence is
segmented, interleaved, differentially encoded and mapped to the symbols and carrier
frequencies.
7 Data Link Layer
7.1 Functions and structure
The Data Link Layer of AMC-SS provides a point to multi-point and point to point
communication on the low voltage distribution network between a master node and one or
more slave nodes. It contains three sub-layers:
• the Medium Access Control sub-layer;
• the Logical Link Control sub-layer;
• the Convergence sub-layer.
The structure of the Data Link Layer is shown in Figure 4.

Figure 4 – Structure of Data Link Layer
Layer 2 services are used by the higher layer entity whenever data is to be transmitted to a
peer entity or entities, and passed to the layer 2 entity to request the sending of a MPDU to
one or more remote entities. The transmission of data is initiated with a CL_data.request
primitive or CL_IPv4_data.request primitive (in the case of IPv4) or CL_IPv6_data.request
primitive (in the case of IPv6). The success or failure of the transmission is locally indicated

with a CL_data_request.confirm primitive or CL_IPv4_data_request.confirm primitive (in the
case of IPv4) or CL_IPv6_data_request.confirm primitive (in the case of IPv6).
Master Node Slave Node
DL_control.indication DL_control.indication
CL_control.indication CL_control.indication
CL_data.request
DL_data.request
DL_data.indication
DL_data_identifier.
CL_data.indication
CL_data_request.
confirm
confirm DL_data.response
DL_data.confirm
Physical
medium
CL_data.request
DL_data.request
DL_data_identifier.
CL_data_request.
confirm
confirm
DL_data.indication
CL_data.indication
DL_data.response
DL_data.confirm
Layer 3 to 7 CL LLC,MAC,PHY LLC,MAC,PHY CL Layer 3 to 7

Figure 5 – DLMS/COSEM AL specific primitives between higher layer and layer 2 in a
bidirectional data transmission
Received data is passed to the higher layer with a CL_data.indication primitive or
CL_IPv4_data.indication primitive (in the case of IPv4) or CL_IPv6_data.indication primitive
(in the case of IPv6).
Broadcast messages from a master node to the slave nodes, that are registered with it, are
supported. In this case ‘request’ and ‘indication’ primitives are used for passing the
information between layers. The success or failure of the transmission is locally indicated with
a CL_data_request.confirm primitive or CL_ipv4_data_request.confirm primitive (in the case
of IPv4) or CL_ipv6_data_request.confirm primitive (in the case of IPv6).

Master Node Slave Node
Physical
CL_data.request
DL_data.request
medium
DL_data.indication
DL_data_identifier.
CL_data.indication
CL_data_request.
confirm
confirm
Layer 3 to 7 CL LLC,MAC,PHY LLC,MAC,PHY CL Layer 3 to 7

Figure 6 – DLMS/COSEM AL specific primitives between higher layer and layer 2 in the
case of broadcast
An unsolicited message is transmitted by the slave node when it is polled by the master node
or during the quick-check procedure (see Clause 6 of CLC/TS 50590:2015). In both cases
‘request’ and ‘indication’ primitives are used for passing the information between layers. The
success or failure of the transmission is locally indicated with a CL_data_request.confirm
primitive or CL_ipv4_data_request.confirm primitive (in the case of IPv4) or
CL_ipv6_data_request.confirm primitive (in the case of IPv6).

– 13 – CLC/TS 52056-8-7:2015
Master Node Slave Node
CL_data.request
DL_data.request
Physical
medium
DL_data_identifier.
CL_data_request.
confirm
confirm
DL_data.indication
CL_data.indication
DL_data.confirm
Layer 3 to 7 CL LLC,MAC,PHY LLC,MAC,PHY CL Layer 3 to 7

Figure 7 – DLMS/COSEM AL specific primitives between higher layers and layer 2 in the
case of an unsolicited data transmission
The Figure 5, Figure 6 and Figure 7 above show the DLMS/COSEM AL specific examples of
CL primitive usage. In case of IPv4 or IPv6, instead of the primitives with the prefix ‘CL’ the
corresponding primitives with the prefixes ‘CL_IPv4’ or ‘CL_IPv6’ respectively are used.
The functions and the coding of the message are defined in Annex B of CLC/TS 50590:2015.
7.2 The Medium Access Control sub-layer
The Medium Access Control sub-layer provides a connection-less transport-mechanism.
Point-to-point, point-to-multipoint and multicast/broadcast services are supported. The MAC
sub-layer provides the simultaneous forwarding procedure, where all involved nodes
retransmit the received messages simultaneously (synchronous). This procedure extends the
range and improves the transmission quality. The transmitted information is protected by CRC
sequences. The MAC sub-layer of AMC-SS is defined in 6.1 to 6.3 of CLC/TS 50590:2015.
The parameters of the MAC sub-layer are preconfigured and listed in Annex D of
CLC/TS 50590:2015.
7.3 The Logical Link Control sub-layer
7.3.1 Overview
The Logical Link Control sub-layer is specified in 6.4 to 6.9 of CLC/TS 50590:2015. The
parameters of the LLC sub-layer are preconfigured and listed in Annex D of
CLC/TS 50590:2015. The LLC sub-layer provides two types of services:
• layer-2-network management functions;
• point to point and point to multi-point communication functions.
7.3.2 Layer-2-network management functions
The transport of network management information is indicated by setting the Data Link
Service (DLS) bit in the LLC control field to DLS=0. The network management functions are:
• Search for new slave nodes;
• Registration and link address management;
• Polling of registered nodes;
• Telegrams for the coordination between nodes;
• Cell change by slave node;
• Clock synchronization for lower layer management;
• Status enquiry;
• PHY link test;
• PHY quality data enquiry.
The network management procedures are described in Clauses 6 and 7 of
CLC/TS 50590:2015. The coding of the messages is defined in Annex B of
CLC/TS 50590:2015.
7.3.3 Communication functions
The transport of higher layer information is indicated by setting the Data Link Service (DLS)
bit in the LLC control field to DLS=1. If DLS=1, then the first byte of the data block contains
the LLC extended control field, which consists of the 4-bit Data Priority (DP) and the 4-bit Link
Channel Number (LCN). These are used for the prioritization and multiplexing of different
protocols and applications. The usage of the Data Priority is left to the implementation. The
coding of the LLC extended control field byte is shown in the Table 1 below.
Table 1 – Coding of the DLC extended control field
Field Code value Meaning
Data Priority, DP 0 to 15 0: lowest priority
1-14: priority 1 to 14
15: highest priority
Link Channel Number, LCN 0 to 4, 8 to 15 reserved
5 IPv4-PDU
6 IPv6-PDU
7 DLMS-PDU
7.3.4 Segmentation and reassembly
The Logical Link Control sub-layer will perform segmentation and reassembly, if the packet is
too long. The coding details are defined in Annex B of CLC/TS 50590:2015. An example
diagram can be found in 6.5.12 of CLC/TS 50590:2015.
7.4 The Convergence sub-layer
7.4.1 Overview
The Data Link layer contains at the top a convergence sub-layer that provides the service
access points for the higher layers. The following types of this sub-layer are specified:
• DLMS/COSEM AL specific convergence sub-layer;
• IPv4 specific convergence sub-layer;
• IPv6 specific convergence sub-layer.
7.4.2 DLMS/COSEM AL specific convergence sub-layer
7.4.2.1 General
The DLMS/COSEM AL specific convergence sub-layer provides transport and distribution of
the DLMS/COSEM Application layer data. This convergence sub-layer provides the service
access points (SAPs) for the application processes in the master and slave nodes.
7.4.2.2 Primitives
7.4.2.2.1 CL_data.request
The CL_data.request primitive is used by the application layer to initiate the data transmission
process.
The semantics of the primitive are as follows:
CL_data.request (ServiceType, DestinationSAP, SourceSAP, DestinationAddress,
SourceAddress, DataPriority, DataLength, Data)
The ServiceType parameter specifies the type of the required transmission. The parameter
may have one of the following values:
0: unicast data transmission is requested;
1: non-acknowledged broadcast data transmission is requested. This type is only
used by a master node.
– 15 – CLC/TS 52056-8-7:2015
The DestinationSAP and SourceSAP parameter contain 8-bit-values of data link layer
selectors (also called "L-SAP”) DSAP and SSAP respectively that specify the destination
service access point and source service access point field in the data link layer PDU. For the
specification of the L-SAP values (SSAP, DSAP) refer to EN 61334-4-32 and EN 61334-4-1.
The DestinationAddress parameter specifies the destination address for the transmission. If
used in the master node, it contains the serial number (device identifier, DID) of the slave
node. In the slave node, the field contains CIN of the master node.
The SourceAddress parameter specifies the source address of the transmission. If used in the
slave node, it contains the serial number (device identifier, DID) of the slave node. In the
master node the field contains CIN of the master node.
The DataPriority parameter indicates the priority of the data to be sent. The master node is
free to select the priority value. If a slave node responds to a previously received request,
then the same priority value as contained in the corresponding request should be used in the
response. It may have any of the following 16 values:
0: priority level 0 (lowest priority);
1 to 14: priority level 1 to 14 respectively;
15: priority level 15 (highest priority).
The DataLength parameter is the length of the Data parameter in octets. It depends on the
value of the parameter DBLMAX (see Annex D of CLC/TS 50590:2015). For the ServiceType
values 0 and 1 the DataLength may have any value in the range from 1 to (16 x (DBLMAX-3)
– 2).
The Data parameter is a buffer of octets that contains the data to be transmitted.
The following Table 2 shows the mapping of the CL_data.request primitive to the
DL_data.request primitive in the master node.
Table 2 – Mapping of CL_data.request to DL_data.request in the master node
CL_data.request DL_data.request
Parameter Contents Parameter Contents
ServiceType 0, 1 ServiceType 1, if ServiceType of
CL_data.request =0
0, if ServiceType of
CL_data.request =1
SourceAddress CIN CellIdentificationNumber CIN
DestinationAddress Device Identifier, if LinkAddress LA = 0 to 0xFFFD, if
ServiceType = 0 ServiceType of
CL_data.request =0
Not used, if ServiceType LA = 0xFFFF, if
= 1 ServiceType of
CL_data.request =1
LinkChannelNumber 7
DataPriority 0 to 15 DataPriority 0 to 15
DataLength 1 to DataLength 3 to 16 x (DBLMAX-3)
16 x (DBLMAX-3) – 2
st
DestinationSAP 0 to 255 1 byte of Data DSAP
nd
SourceSAP 0 to 255 2 byte of Data SSAP
Data A-PDU Data bytes 3 to DataLength A-PDU
The following Table 3 shows the mapping of the CL_data.request primitive to the
DL_data.request primitive in the slave node.

Table 3 – Mapping of CL_data.request to DL_data.request in the slave node
CL_data.request DL_data.request
Parameter Contents Parameter Contents
ServiceType 0 ServiceType 1
DestinationAddress CIN CellIdentificationNumber CIN
SourceAddress Device Identifier LinkAddress LA
LinkChannelNumber 7
DataPriority 0 to 15 DataPriority 0 to 15
DataLength 1 to DataLength 3 to 16 x (DBLMAX-3)
16 x (DBLMAX-3) – 2
st
DestinationSAP 0 to 255 1 byte of Data DSAP
nd
SourceSAP 0 to 255 2 byte of Data SSAP
Data A-PDU Data bytes 3 to DataLength A-PDU
7.4.2.2.2 CL_data.indication
The CL_data.indication primitive informs the application layer about the reception of data.
The semantics of the primitive are as follows:
CL_data.indication (ServiceType, DestinationSAP, SourceSAP, DestinationAddress,
SourceAddress, DataPriority, DataLength, Data)
The ServiceType parameter specifies the type of the transmission. The parameter may have
one of the following values:
0: unicast data transmission was used;
1: non-acknowledged broadcast data transmission was used.
The DestinationSAP and SourceSAP parameter contain 8-bit-values of data link layer
selectors ( also called “L-SAP”) DSAP and SSAP respectively that specify the destination
service access point and source service access point field in the data link layer PDU. For the
specification of the L-SAP values (SSAP, DSAP) refer to EN 61334-4-32 and EN 61334-4-1.
The DestinationAddress parameter specifies the destination address for the transmission. If
used in the master node, it contains CIN of the master node. In the slave node, the field
contains the serial number (device identifier, DID) of the slave node.
The SourceAddress parameter specifies the source address of the transmission. If used in the
master node, it contains the serial number (device identifier, DID) of the slave node. In the
slave node the field contains CIN of the master node.
The DataPriority parameter indicates the priority of the data that has been received. It may
have any of the following 16 values:
0: priority level 0 (lowest priority)
1 to 14: priority level 1 to 14 respectively
15: priority level 15 (highest priority)
The DataLength parameter is the length of the Data parameter in octets. It depends on the
value of the parameter DBLMAX. For the ServiceType parameter values 0 and 1 the
DataLength parameter may have any value in the range from 1 to 16 x (DBLMAX-3) – 2.
The Data parameter is a buffer of octets that contains the data that was received.
The following Table 4 shows the mapping of the DL_data.indication primitive to the
CL_data.indication primitive in the master node.

– 17 – CLC/TS 52056-8-7:2015
Table 4 – Mapping of DL_data.indication to CL_data.indication in the master node
DL_data.indication CL_data.indication
Parameter Contents Parameter Contents
DataIdentifier 255 ServiceType 0
CellIdentificationNumber CIN DestinationAddress CIN
LinkAddress LA SourceAddress Device Identifier
LinkChannelNumber 7
DataPriority 0 to 15 DataPriority 0 to 15
DataLength 3 to 16 x (DBLMAX-3) DataLength 1 to
16 x (DBLMAX-3) – 2
st
1 byte of Data DSAP DestinationSAP 0 to 255
nd
2 byte of Data SSAP SourceSAP 0 to 255
Data bytes 3 to DataLength A-PDU Data A-PDU
The following Table 5 shows the mapping of the DL_data.indication primitive to the
CL_data.indication primitive in the slave node.
Table 5 – Mapping of DL_data.indication to CL_data.indication in the slave node
DL_data.indication CL_data.indication
Parameter Contents Parameter Contents
DataIdentifier 254, 255 ServiceType 0, if DataIdentifier = 255
1, if DataIdentifier = 254
CellIdentificationNumber CIN SourceAddress CIN
LinkAddress LA = 0 to 0xFFFD, if DestinationAddress Device Identifier, if
DataIdentifier = 255; DataIdentifier = 255;
LA = 0xFFFF, if Not used, if DataIdentifier
DataIdentifier = 254 = 254
LinkChannelNumber 7
DataPriority 0 to 15 DataPriority 0 to 15
DataLength 3 to 16 x (DBLMAX-3) DataLength 1 to
16 x (DBLMAX-3) - 2
st
1 byte of Data DSAP DestinationSAP 0 to 255
nd
2 byte of Data SSAP SourceSAP 0 to 255
Data bytes 3 to DataLength A-PDU Data A-PDU
7.4.2.2.3 CL_data_request.confirm
The CL_data_request.confirm primitive is a local response to the application layer entity,
which indicates the local success or failure of the associated previous CL_data.request
primitive.
The semantics of the primitive are as follows:
CL_data_request.confirm (Status, ServiceType, DestinationSAP, SourceSAP,
DestinationAddress, DataPriority, DataLength, Data)
The Status parameter is used to pass the status information back to the requesting
application layer entity. It is used to indicate the success or failure of the associated previous
CL_data.request primitive. The parameter may have one of the following values:
0: success of the associated previous CL_data.request;
1: failure of the associated previous CL_data.request. The transmit buffer of the
requested entity is occupied;
2: failure of the associated previous CL_data.request. There is no communication to
the addressed destination node. The node registration is lost;

3: failure of the associated previous CL_data.request. The communication to the
addressed destination node is temporarily lost.
The ServiceType parameter specifies the type of the requested transmission. The parameter
may have one of the following values:
0: unicast data transmission is requested;
1: non-acknowledged broadcast data transmission is requested. The value is only
used by a master node.
The DestinationSAP and SourceSAP parameter contain 8-bit-values of data link layer
selectors ( also called "L-SAP”) DSAP and SSAP respectively that specify the destination
service access point and source service access point field in the data link layer PDU. Their
values correspond to those of the previous associated CL_data.request primitive. For the
specification of the L-SAP values (SSAP, DSAP) refer to EN 61334-4-32 and EN 61334-4-1.
The DestinationAddress parameter specifies the destination address for the transmission. Its
value corresponds to that of the associated previous CL_data.request primitive. If used in the
slave node, the DestinationAddress parameter contains the serial number (device identifier,
DID) of the slave node. In the master node the field contains the CIN of the master node.
The DataPriority parameter indicates the priority of the data to be sent. The same priority
value as contained in the corresponding request should be used. It may have any of the
following 16 values:
0: priority level 0 (lowest priority);
1 to 14: priority level 1 to 14 respectivelly;
15: priority level 15 (highest priority).
The DataLength parameter is the length of the Data parameter in octets. It depends on the
value of the parameter DBLMAX (see Annex D of CLC/TS 50590:2015). The DataLength may
have any value in the range from 1 to (16 x (DBLMAX-3) – 2).
The Data parameter is a buffer of octets that contains the data to be transmitted.
The following Table 6 shows the mapping of the DL_data_identifier.confirm primitive to the
CL_data_request.confirm primitive in the master node.
Table 6 – Mapping of DL_data_identifier.confirm to CL_data_request.confirm in the
master node
DL_data_identifier.confirm CL_data_request.confirm
Parameter Contents Parameter Contents
Status 0 to 3 Status 0 to 3
DataIdentifier 254 or 255, if Status = 0; ServiceType 0, if DataIdentifier = 255;
Not used, if Status = 1 1, if DataIdentifier = 254;
to3. Not used, if Status = 1
to3.
CellIdentificationNumber CIN
LinkAddress LA = 0 to 0xFFFD, if DestinationAddress DeviceIdentifier, if
DataIdentifier = 255; ServiceType = 0;
LA = 0xFFFF, if Not used, if ServiceType
DataIdentifier = 254 = 1
LinkChannelNumber 7
DataPriority 0 to 15 DataPriority 0 to 15
DataLength 3 to 16 x (DBLMAX-3) DataLength 1 to
16 x (DBLMAX-3) – 2
st
1 byte of Data DSAP DestinationSAP 0 to 255
nd
2 byte of Data SSAP SourceSAP 0 to 255
Data bytes 3 to DataLength A-PDU Data A-PDU

– 19 – CLC/TS 52056-8-7:2015
The following Table 7 shows the mapping of the DL_data_identifier.confirm primitive to the
CL_data_request.confirm primitive in the slave node.
Table 7 – Mapping of DL_data_identifier.confirm to CL_data_request.confirm in the
slave node
DL_data_identifier.confirm CL_data_request.confirm
Parameter Contents Parameter Contents
Status 0 to 3 Status 0 to 3
DataIdentifier 255, if Status = 0; ServiceType 0, if Status = 0;
Not used, if Status = 1 to Not used, if Status = 1 to
3. 3.
CellIdentificationNumber CIN DestinationAddress CIN
LinkAddress LA = 0 to 0xFFFD
LinkChannelNumber 7
DataPriority 0 to 15 DataPriority 0 to 15
DataLength 3 to 16 x (DBLMAX- DataLength 1 to
3) 16 x (DBLMAX-3) – 2
st
1 byte of Data DSAP DestinationSAP 0 to 255
nd
2 byte of Data SSAP SourceSAP 0 to 255
Data bytes 3 to DataLength A-PDU Data A-PDU
7.4.2.2.4 Reserved SAP values
The reserved SAP values for the master node operating as DLMS-client and for the slave
node operating as DLMS server are shown in following Table 8 and Table 9.
Table 8 – Reserved SAP values on the master node side
Address Meaning
0x00 No-station
0x01 Client (Master Node) management process.
0x10 Public Client
Table 9 – Reserved SAP values on the slave node side
Address Meaning
0x00 No-station
0x01 Management Logical Device
0x02 to 0x0F Reserved
0xFF All-station (Broadcast)
7.4.3 IPv4 specific convergence sub-layer
7.4.3.1 Architecture
The IPv4 specific convergence sub-layer provides an efficient method for transferring IPv4
packets over the AMC-SS networks. The IPv4 PDUs may be compressed according to
RFC 2507 with the predefined compression parameters specified in Annex A. The
communication architecture for IPv4 is shown in Figure 8.

SIST-
...