IEC 62056-8-12:2023

IEC 62056-8-12 ®
Edition 1.0 2023-09
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Electricity metering data exchange – The DLMS®/COSEM suite –
Part 8-12: Communication profile for Low-Power Wide Area Networks (LPWANs)

Échange des données de comptage de l’électricité – La suite DLMS®/COSEM –
Partie 8-12: Profil de communication pour réseaux étendus à basse
consommation (LPWAN)
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite ni
utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie et
les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des
questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez
les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence.

IEC Secretariat Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.

IEC publications search - webstore.iec.ch/advsearchform IEC Products & Services Portal - products.iec.ch
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews. With a subscription you will always have
committee, …). It also gives information on projects, replaced access to up to date content tailored to your needs.
and withdrawn publications.
Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
The world's leading online dictionary on electrotechnology,
Stay up to date on all new IEC publications. Just Published
containing more than 22 300 terminological entries in English
details all new publications released. Available online and once
and French, with equivalent terms in 19 additional languages.
a month by email.
Also known as the International Electrotechnical Vocabulary

(IEV) online.
IEC Customer Service Centre - webstore.iec.ch/csc

If you wish to give us your feedback on this publication or need
further assistance, please contact the Customer Service
Centre: sales@iec.ch.
A propos de l'IEC
La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des
Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

A propos des publications IEC
Le contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la
plus récente, un corrigendum ou amendement peut avoir été publié.

Recherche de publications IEC -  IEC Products & Services Portal - products.iec.ch
webstore.iec.ch/advsearchform Découvrez notre puissant moteur de recherche et consultez
La recherche avancée permet de trouver des publications IEC gratuitement tous les aperçus des publications. Avec un
en utilisant différents critères (numéro de référence, texte, abonnement, vous aurez toujours accès à un contenu à jour
comité d’études, …). Elle donne aussi des informations sur les adapté à vos besoins.
projets et les publications remplacées ou retirées.

Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
Le premier dictionnaire d'électrotechnologie en ligne au monde,
Restez informé sur les nouvelles publications IEC. Just
avec plus de 22 300 articles terminologiques en anglais et en
Published détaille les nouvelles publications parues.
français, ainsi que les termes équivalents dans 19 langues
Disponible en ligne et une fois par mois par email.
additionnelles. Egalement appelé Vocabulaire

Electrotechnique International (IEV) en ligne.
Service Clients - webstore.iec.ch/csc

Si vous désirez nous donner des commentaires sur cette
publication ou si vous avez des questions contactez-nous:
sales@iec.ch.
IEC 62056-8-12 ®
Edition 1.0 2023-09
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
Electricity metering data exchange – The DLMS®/COSEM suite –

Part 8-12: Communication profile for Low-Power Wide Area Networks (LPWANs)

Échange des données de comptage de l’électricité – La suite DLMS®/COSEM –

Partie 8-12: Profil de communication pour réseaux étendus à basse

consommation (LPWAN)
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 35.110  ISBN 978-2-8322-7574-0

– 2 – IEC 62056-8-12:2023 © IEC 2023
CONTENTS
FOREWORD . 4
1 Scope . 6
2 Normative references . 6
3 Terms, definitions and abbreviated terms . 7
3.1 Terms and definitions . 7
3.2 Abbreviated terms . 7
4 Targeted communication environments . 8
4.1 General . 8
4.1.1 Overview . 8
4.1.2 Security . 9
4.2 Use of the communications layers for this profile . 9
4.2.1 Information related to the use of the standard specifying the lower
layers (IEC TS 62056-1-1:2016, 5.1) . 9
4.2.2 Structure of the communication profiles (IEC TS 62056-1-1:2016, 5.2) . 9
4.2.3 Lower protocol layers and their use (IEC TS 62056-1-1:2016, 5.3) . 10
4.2.4 Service mapping and adaptation layers (IEC TS 62056-1-1:2016, 5.4) . 11
4.2.5 Registration and connection management (IEC TS 62056-1-1:2016, 5.5) . 11
4.3 Identification and addressing schemes (IEC TS 62056-1-1:2016, Clause 6) . 11
4.4 Specific considerations for the application layer service (IEC TS 62056-1-
1:2016, Clause 7) . 11
4.4.1 Overview (IEC TS 62056-1-1:2016, 7.1) . 11
4.4.2 Application Association establishment and release: ACSE services
(IEC TS 62056-1-1:2016, 7.2) . 12
4.4.3 xDLMS services (IEC TS 62056-1-1:2016, 7.3) . 12
4.4.4 Security mechanisms (IEC TS 62056-1-1:2016, 7.4) . 12
4.4.5 Transferring long application messages (IEC TS 62056-1-1:2016, 7.5) . 12
4.4.6 Media access, bandwidth and timing consideration (IEC TS 62056-1-
1:2016, 7.6) . 12
4.5 Communication configuration and management (IEC TS 62056-1-1:2016,
Clause 8) . 12
4.6 The COSEM application process (IEC TS 62056-1-1:2016, Clause 9) . 12
Annex A (informative) Examples . 13
A.1 Example 1: DLMS®/COSEM GET Service transported through LPWAN using
LoRaWAN technology . 13
A.2 Example 2: DLMS®/COSEM DataNotification Service transported through
LPWAN with SCHC fragments . 15
A.3 Example 3: DLMS®/COSEM Access Service transported through LPWAN
with SCHC fragments . 22
Bibliography . 30

Figure 1 – Communication architecture . 8
Figure 2 – LPWAN (SCHC) architecture outline . 9
Figure 3 – DLMS®/COSEM LPWAN communication profile . 10
Figure A.1 – The DLMS®/COSEM GET Service on LPWAN . 15

Table 1 – Client and server SAPs . 11
Table A.1 – Get Service example . 13
Table A.2 – Data-Notification Service with Profile Generic . 16
Table A.3 – Example – Access Service . 22

– 4 – IEC 62056-8-12:2023 © IEC 2023
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
ELECTRICITY METERING DATA EXCHANGE –
THE DLMS®/COSEM SUITE –
Part 8-12: Communication profile for
Low-Power Wide Area Networks (LPWANs)

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 itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
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) IEC draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). IEC takes no position concerning the evidence, validity or applicability of any claimed patent rights in
respect thereof. As of the date of publication of this document, IEC had not received notice of (a) patent(s), which
may be required to implement this document. However, implementers are cautioned that this may not represent
the latest information, which may be obtained from the patent database available at https://patents.iec.ch. IEC
shall not be held responsible for identifying any or all such patent rights.
IEC 62056-8-12 has been prepared by IEC technical committee TC 13: Electrical energy
measurement and control. It is an International Standard.
The text of this International Standard is based on the following documents:
Draft Report on voting
13/1877/CDV 13/1901/RVC
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/standardsdev/publications.
A list of all parts in the IEC 62056 series, published under the general title Electricity metering
data exchange – The DLMS®/COSEM suite, can be found on the IEC website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn, or
• revised.
IMPORTANT – The "colour inside" logo on the cover page of this document indicates
that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this document using a colour printer.

– 6 – IEC 62056-8-12:2023 © IEC 2023
ELECTRICITY METERING DATA EXCHANGE –
THE DLMS®/COSEM SUITE –
Part 8-12: Communication profile for
Low-Power Wide Area Networks (LPWANs)

1 Scope
This part of IEC 62056 describes the use of DLMS®/COSEM for Low-Power Wide Area
Networks (LPWANs). It specifies how the COSEM data model and the DLMS®/COSEM
application layer can be used over various LPWAN technologies using an adaptation layer
based on IETF RFC 8724, and in particular over LoRaWAN.
This profile is intended to be used with LPWANs as defined in IETF RFC 8724, in particular
LoRaWAN. Low-Power Wide Area Networks (LPWANs) are wireless technologies with
characteristics such as large coverage areas, low bandwidth, possibly very small packet and
application-layer data sizes, and long battery life operation. This document does not provide
functionality to manage the lower layers of the LPWANs.
This part of the DLMS®/COSEM suite specifies the communication profile for Low-Power Wide
Area Networks (LPWANs).
The DLMS®/COSEM LPWAN communication profiles use connection-less transport layer based
on the Internet Standard User Datagram Protocol (UDP) and Internet Protocol (IPv6).
The adaptation layer is based on IETF RFC 8724 which provides both a header
compression/decompression mechanism and an optional fragmentation/reassembly
mechanism. SCHC compression is based on static context with small context identifier to
represent full IPv6/UDP/COSEM wrapper headers. If required, SCHC fragmentation is used to
support IPv6 MTU over the LPWAN technologies.
This document follows the rules defined in IEC 62056-5-3:2023, Annex A, and in IEC 62056-1-0,
and IEC TS 62056-1-1:2016 for its structure. See also Annex A for examples.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies.
For undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 62056-1-0, Electricity metering data exchange – The DLMS®/COSEM suite – Part 1-0
Smart metering standardisation framework
IEC TS 62056-1-1:2016, Electricity metering data exchange – The DLMS®/COSEM suite –
Part 1-1: Template for DLMS®/COSEM communication profile standards
IEC 62056-4-7:2015, Electricity metering data exchange – The DLMS®/COSEM suite –
Part 4-7: DLMS®/COSEM transport layer for IP networks
IEC 62056-5-3:2023, Electricity metering data exchange – The DLMS®/COSEM suite –
Part 5-3: DLMS®/COSEM application layer

IEC 62056-6-1, Ed4 , Electricity metering data exchange – The DLMS®/COSEM suite –
Part 6-1: Object Identification System (OBIS)
IEC 62056-6-2:2023, Electricity metering data exchange – The DLMS®/COSEM suite –
Part 6-2: COSEM interface classes
IEC 62056-9-7:2013, Electricity metering data exchange – The DLMS®/COSEM suite –
Part 9-7: Communication profile for TCP-UDP/IP networks
IETF RFC 2460, Internet Protocol, Version 6 (IPv6) Specification. Edited by S. Deering, R.
Hinden. December 1998. Available from http://www.ietf.org/RFC /RFC 2460.txt
IETF RFC 8376, Low-Power Wide Area Network (LPWAN) Overview (available from
https://www.rfc-editor.org/rfc/pdfrfc/rfc8376.txt.pdf)
IETF RFC 8724, SCHC – Generic Framework for Static Context Header Compression and
Fragmentation (available from https://www.rfc-editor.org/rfc/rfc8724.html)
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62056-5-3:2023,
IETF RFC 8376 and IETF RFC 8724 apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.2 Abbreviated terms
AA Application Association
ABP Activation by Personalization
APDU Application Layer Protocol Data Unit
COSEM Companion Specification for Energy Metering
C/D Compression and Decompression
CSAP Client Service Access Point
DevAddr 32-bit non-unique identifier assigned to an end-device statically or dynamically
after a Join Procedure (depending on the activation mode)
DEVEUI IEEE EUI-64 used to identify the device during the Join Procedure
DLMS Device Language Message Specification
F/R Fragmentation and Reassembly
HDLC High-level Data Link Control
IP Internet Protocol
LNAP Local Network Access Point
NGW Network Gateway
PAN Personal Area Network
___________
Under preparation. Stage at the time of publication: IEC 13/1852/CDV

– 8 – IEC 62056-8-12:2023 © IEC 2023
RG Radio Gateway
SAP Service Access Point
SSAP Server Service Access Point
SCHC Static Context Header Compression and fragmentation, a generic framework
TCP Transmission Control Protocol
UDP User Datagram Protocol
4 Targeted communication environments
4.1 General
4.1.1 Overview
The DLMS®/COSEM communication profiles for LPWAN networks are intended for remote data
exchange on WAN between the HES and the end devices. From a DLMS® point of view, they
are connected directly to the HES via the G1 interface. All dotted elements are out of the scope
for this profile.
The functional smart metering reference architecture is shown in Figure 1.

Figure 1 – Communication architecture
End devices comprise application functions and communication functions. They can be utility
meters or any other kind of IoT devices. They use UDP/IPv6, SCHC
compression/decompression and fragmentation/reassembly features as specified in
IETF RFC 8724 and communicate with their related application server via the network gateway.
This profile maps to Figure 2.

Figure 2 – LPWAN (SCHC) architecture outline
4.1.2 Security
LPWAN technologies provide various lower layer security features. The application security
features provided by DLMS®/COSEM can be used over any of them.
4.2 Use of the communications layers for this profile
4.2.1 Information related to the use of the standard specifying the lower layers
(IEC TS 62056-1-1:2016, 5.1)
IETF RFC 8724 can be considered as an adaptation layer between UDP/IPv6 and the
underlying LPWAN technology. SCHC comprises two sublayers, compression and
fragmentation that are independent of the specific LPWAN technology. IETF RFC 8724
supports UDP/IPv6 and as such supports the DLMS®/COSEM UDP/IP profile. No adaptations
or limitations to IETF RFC 8724 or DLMS®/COSEM are expected to be required when using
SCHC to transport COSEM APDUs.
4.2.2 Structure of the communication profiles (IEC TS 62056-1-1:2016, 5.2)
See Figure 3.
– 10 – IEC 62056-8-12:2023 © IEC 2023

Figure 3 – DLMS®/COSEM LPWAN communication profile
4.2.3 Lower protocol layers and their use (IEC TS 62056-1-1:2016, 5.3)
4.2.3.1 Overview (IEC TS 62056-1-1:2016, 5.3.1)
Lower layers are any LPWAN lower layers that can transport SCHC packets as specified in
IETF RFC 8724.
NOTE IETF RFC 8376 provides an overview of LPWAN technologies that can be used for running IP in LPWANs.
ABP is not permitted when the LoRaWAN network is being applied. See also
IEC 62056-6-2:2023, 4.16.
4.2.3.2 Physical layer (IEC TS 62056-1-1:2016, 5.3.2)
The physical layer is out of the scope of this document; it is specific to the LPWAN technology
used.
4.2.3.3 MAC layer (IEC TS 62056-1-1:2016, 5.3.3)
The MAC layer is out of the scope of this document; it is specific to the LPWAN technology
used.
4.2.3.4 Adaptation layer (IEC TS 62056-1-1:2016, 5.3.4)
The adaptation layer is in accordance with IETF RFC 8724. It interfaces at the upper layer IPv6
as specified in IETF RFC 2460.
4.2.4 Service mapping and adaptation layers (IEC TS 62056-1-1:2016, 5.4)
The DLMS®/COSEM transport layer for IP networks performs the necessary binding of the
COSEM object model and the DLMS®/COSEM application layer in one part and the
communication lower layers in the other part. The service mapping is fully specified in the UDP-
DATA service, see IEC 62056-4-7:2015, 5.2.2.
4.2.5 Registration and connection management (IEC TS 62056-1-1:2016, 5.5)
Registration and connection management are specific to each LPWAN technology and network.
Details can be found in IEC 62056-6-2:2023, 4.16.
4.3 Identification and addressing schemes (IEC TS 62056-1-1:2016, Clause 6)
The identification and addressing of SAPs is as described in Table 1.
Table 1 – Client and server SAPs
Client SAPs
Client Management Process 0x01
Public Client 0x10
0x02 …0x0F
Open for client SAP assignment
0x11… 0xFF
Server SAPs
Management Logical Device 0x01
Reserved for future use 0x02…0x0F
Open for server SAP assignment 0x10…0x7E
All-station (broadcast) 0xFF
4.4 Specific considerations for the application layer service (IEC TS 62056-1-1:2016,
Clause 7)
4.4.1 Overview (IEC TS 62056-1-1:2016, 7.1)
The constraints and options available to AL services are those dictated by any UDP-based
DLMS® approach.
– 12 – IEC 62056-8-12:2023 © IEC 2023
4.4.2 Application Association establishment and release: ACSE services
(IEC TS 62056-1-1:2016, 7.2)
In accordance with IEC 62056-9-7:2013, 9.1 and 9.2.
4.4.3 xDLMS services (IEC TS 62056-1-1:2016, 7.3)
According to IEC 62056-9-7:2013, 9.4 and 9.5.
4.4.4 Security mechanisms (IEC TS 62056-1-1:2016, 7.4)
4.4.4.1 DLMS®/COSEM security
DLMS/COSEM security applies at the application layer and model level. As a consequence,
application security does not depend on the structure of this communication profile. All the
security mechanisms as defined in the IEC 62056-5-3:2023, IEC 62056-6-1, Ed4 and
IEC 62056-6-2:2023 are applicable without any restrictions. The security suites and the security
policies chosen and the PKI to use are project specific. They depend on the project specific
companion specification.
4.4.4.2 Lower layers security
In addition to the DLMS®/COSEM security, the lower layers can also provide security features
addressing confidentiality, data authenticity and integrity. These security features are out of the
scope of this standard.
4.4.4.3 Registration and deregistration of lower layers security
Registration and deregistration security are specific to the LPWAN technology used (see
IEC 62056-6-2:2023).
4.4.5 Transferring long application messages (IEC TS 62056-1-1:2016, 7.5)
For transporting long messages, either the service specific block transfer or the general block
transfer (GBT) DLMS®/COSEM application layer mechanisms can be used (the latter is
preferred).
4.4.6 Media access, bandwidth and timing consideration (IEC TS 62056-1-1:2016, 7.6)
Out of the scope of this document; these aspects are specific to the LPWAN technology used
(see IEC 62056-6-2:2023).
4.5 Communication configuration and management (IEC TS 62056-1-1:2016, Clause 8)
The parameters allowing the configuration of the adaptation layer and the LPWAN lower layers
are mapped to attributes and methods of DLMS®/COSEM interface classes:
• a setup and a diagnostic IC for SCHC-LPWAN are specified in IEC 62056-6-2:2023;
• a setup and a diagnostic IC should be specified for each specific LPWAN technology. For
LoRaWAN they are specified in IEC 62056-6-2:2023, 4.16.
4.6 The COSEM application process (IEC TS 62056-1-1:2016, Clause 9)
All the features defined in IEC 62056-6-1, Ed4, IEC 62056-6-2:2023 and IEC 62056-5-3:2023
are applicable without any restrictions.

Annex A
(informative)
Examples
A.1 Example 1: DLMS®/COSEM GET Service transported through LPWAN
using LoRaWAN technology
See Table A.1 and Figure A.1.
Table A.1 – Get Service example
Message elements Contents LEN
(Bytes)
C0 1
Get-Request
01 1
get-request-normal
40 1
invoke-id-and-priority
cosem-attribute-descriptor
0001 2
class-id
0000600100FF 6
instance-id
02 1
attr-id
00 1
access-selection
Get-Request (encoded) C0014000010000600100FF0200 13

IPv6
60045604001E1180 8
IPv6 Header
FE80000000000000745500FFFE000100 16
IPv6 Source Address
FE80000000000000745500FFFE000101 16
IPv6 Destination Address
UDP
0FDB0FDB001E3A86 8
UDP Header
COSEM Wrapper
000100010001000D 8
COSEM Wrapper Header
C0014000010000600100FF0200 13
get-request
IPv6 (encoded) 60045604001E1180FE80000000000000745500FF 69
FE000100FE80000000000000745500FFFE000101
0FDB0FDB001E3A86000100010001000DC0014000
010000600100FF0200
SCHC Packet
02C0014000010000600100FF0200 14
Rule
ID=0x02|CompressionResidue=|SCHC Payload |
Padding=
02C0014000010000600100FF0200 14
SCHC (encoded)
LoRaWAN (Downlink)
– 14 – IEC 62056-8-12:2023 © IEC 2023
Message elements Contents LEN
(Bytes)
60 1
LoRaWAN Header
(Mtype=011b,RFU=000b,Major=00)
LoRaWAN FHDR (LoRaWAN FHDR CD160126800100 7
(DevAddr=260116CDh,FCtrl=10000000b,FC
nt=0001,FOpts=)
02 1
LoRaWAN Fport
2F4D36ED10CEEDD7B588C9CA01 13
LoRaWAN Payload (Encrypted SCHC=
C0014000010000600100FF0200)
AppSKey =
0x88F282F3F9E901CDC37C3311F01050B2
A1CD20D1 4
MIC (little Endian)
NwkSKey =
0x8A69FAD35B3CF856EC86EFE77B3F21C4
60CD160126800100022F4D36ED10CEEDD7B588C9 26
LoRaWAN (encoded)
CA01A1CD20D1
C4 1
Get-Response
01 1
get-response-normal
40 1
invoke-id-and-priority
result CHOICE
00 1
data
octet-string  09083030303030303031 10
C401400009083030303030303031 14
Get-Response (encoded)
IPv6
IPv6 Header 60045604001E1180 8
FE80000000000000745500FFFE000101 16
IPv6 Source Address
FE80000000000000745500FFFE000100 16
IPv6 Destination Address
UDP
0FDB0FDB001E3A86 8
UDP Header
COSEM Wrapper
000100010001000E 8
COSEM Wrapper Header
C401400009083030303030303031 14
get-response
60045604001E1180FE80000000000000745500FF 70
IPv6 (encoded)
FE000101FE80000000000000745500FFFE000100
0FDB0FDB001E3A86000100010001000EC4014000
SCHC Packet
Rule 02C401400009083030303030303031 15
ID=0x02|CompressionResidue=|SCHC Payload |
Padding=
02C401400009083030303030303031 15
SCHC (encoded)
Message elements Contents LEN
(Bytes)
LoRaWAN (Uplink)
40 1
LoRaWAN Header
(Mtype=010b,RFU=000b,Major=00b)
CD160126800100 7
LoRaWAN FHDR
(DevAddr=260116CDh,FCtrl=10000000b,FC
nt=0001,FOpts=)
02 1
LoRaWAN Fport (= RuleID)
5FFABD9D2ADDAF75E0B1A0DC65D1 14
LoRaWAN Payload (Encrypted
SCHC=C401400009083030303030303031)
AppSKey =
0x88F282F3F9E901CDC37C3311F01050B2
E07194EE 4
MIC (little endian)
NwkSKey =
0x8A69FAD35B3CF856EC86EFE77B3F21C4
40CD160126800100025FFABD9D2ADDAF75E0B1A0 27
LoRaWAN (encoded)
DC65D1E07194EE
Figure A.1 – The DLMS®/COSEM GET Service on LPWAN
A.2 Example 2: DLMS®/COSEM DataNotification Service transported through
LPWAN with SCHC fragments
See Table A.2.
– 16 – IEC 62056-8-12:2023 © IEC 2023
Table A.2 – Data-Notification Service with Profile Generic
Message elements Contents LEN (Bytes)
0F 1
Data-Notification
00000001 4
long-invoke-id-and-priority
00 1
date-time
notification-body
data-value 0
0118 2
array [24]
0203 2
structure [3]
090C07E2020C0500000000800000 14
octet-string
1100 2
unsigned
06000186A0 5
double-long-unsigned
0203 2
structure [3]
null-data 00 1
00 1
null-data
0600018840 5
double-long-unsigned
structure [3] 0203 2
00 1
null-data
00 1
null-data
06000189E0 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
double-long-unsigned  0600018B80 5
0203 2
structure [3]
00 1
null-data
null-data 00 1
0600018D20 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
0600018EC0 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
0600019060 5
double-long-unsigned
Message elements Contents LEN (Bytes)
0203 2
structure [3]
00 1
null-data
00 1
null-data
0600019200 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
null-data 00 1
06000193A0 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
0600019540 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
06000196E0 5
double-long-unsigned
structure [3] 0203 2
00 1
null-data
00 1
null-data
double-long-unsigned  0600019880 5
0203 2
structure [3]
00 1
null-data
00 1
null-data
0600019A20 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
0600019BC0 5
double-long-unsigned
0203 2
structure [3]
null-data 00 1
00 1
null-data
0600019D60 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
– 18 – IEC 62056-8-12:2023 © IEC 2023
Message elements Contents LEN (Bytes)
0600019F00 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
060001A0A0 5
double-long-unsigned
0203 2
structure [3]
null-data 00 1
00 1
null-data
060001A240 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
060001A3E0 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
double-long-unsigned  060001A580 5
0203 2
structure [3]
00 1
null-data
null-data 00 1
060001A720 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
060001A8C0 5
double-long-unsigned
0203 2
structure [3]
00 1
null-data
00 1
null-data
060001AA60 5
double-long-unsigned
structure [3] 0203 2
00 1
null-data
00 1
null-data
060001AC00 5
double-long-unsigned
Message elements Contents LEN (Bytes)
0F000000010001180203090C07E2020C05000000 238

00800000110006000186A0020300000600018840
0203000006000189E0020300000600018B800203
00000600018D20020300000600018EC002030000
0193A00203000006000195400203000006000196
E0020300000600019880020300000600019A2002
0300000600019BC0020300000600019D60020300
000600019F0002030000060001A0A00203000006
0001A24002030000060001A3E002030000060001
A58002030000060001A72002030000060001A8C0
02030000060001AA6002030000060001AC00
IPv6
60045604001E1180 8
IPv6 Header
FE80000000000000745500FFFE000101 16
IPv6 Source Address
IPv6 Destination Address FE80000000000000745500FFFE000100 16

UDP
0FDB0FDB001E3A86 8
UDP Header
COSEM Wrapper
00010001000100EE 8
COSEM Wrapper
Header
60045604001E1180FE80000000000000745500FF 294
IPv6 (encoded)
FE000101FE80000000000000745500FFFE000100
0FDB0FDB001E3A8600010001000100EE0E000000
000001180203090C07E2020C0500000000800000
110006000186A002030000060001884002030000
06000189E0020300000600018B80020300000600
018D20020300000600018EC00203000006000190
600203000006000192000203000006000193A002
03000006000195400203000006000196E0020300
000600019880020300000600019A200203000006
00019BC0020300000600019D6002030000060001
9F0002030000060001A0A002030000060001A240
02030000060001A3E002030000060001A5800203
0000060001A72002030000060001A8C002030000
060001AA6002030000060001AC00
SCHC
C/D
090E000000000001180203090C07E2020C050000 239
SCHC Header (Rule ID=09,
0000800000110006000186A00203000006000188
Compression Residue=) |
400203000006000189E0020300000600018B8002
SCHC Payload
0300000600018D20020300000600018EC0020300
000193A002030000060001954002030000060001
96E0020300000600019880020300000600019A20
020300000600019BC0020300000600019D600203
00000600019F0002030000060001A0A002030000
060001A24002030000060001A3E0020300000600
01A58002030000060001A72002030000060001A8
C002030000060001AA6002030000060001AC00

F/R
SCHC Fragment 1 (Uplink),
Current LoRaWAN MTU=115
(EU868,SF9)
– 20 – IEC 62056-8-12:2023 © IEC 2023
Message elements Contents LEN (Bytes)
143E090E000000000001180203090C07E2020C05 116
SCHC Header (Rule
00000000800000110006000186A0020300000600
ID=00010100b, W=00b,
0188400203000006000189E0020300000600018B
FCN=111110b) | SCHC
80020300000600018D20020300000600018EC002
Fragment Payload
0006000193A002030000060001954002

SCHC Fragment 2 (Uplink),
Current LoRaWAN MTU=115
(EU868,SF9)
143D03000006000196E002030000060001988002 116
SCHC Header (Rule
0300000600019A20020300000600019BC0020300
ID=00010100b, W=00b,
000600019D60020300000600019F000203000006
FCN=1111101b) |
0001A0A002030000060001A24002030000060001
SCHC Fragment
A3E002030000060001A58002030000060001A720
Payload
02030000060001A8C002030000060001

SCHC Fragment 3 (Uplink),
Current LoRaWAN MTU=115
(EU868,SF9)
143FAA6002030000060001AC00 13
SCHC Header (Rule
ID=00010100b, W=00b,
FCN=1111111b) |
SCHC Fragment
Payload
SCHC ACK (Downlink)
1440 2
SCHC Header (Rule
ID=00010100b, W=00b,
C=1) | Padding 5 bits
LoRaWAN
LoRaWAN SCHC Fragment 1 (Uplink)
40 1
LoRaWAN Header
(Mtype=010b,RFU=000b,Major
=00b)
CD160126800000 7
LoRaWAN FHDR
(DevAddr=260116CDh,FCtrl=1
0000000b,FCnt=0,FOpts=)
14 1
LoRaWAN Fport (F/R RuleID)
2748ED7C9F0CE0BA6324C14D11ED80420B54CA32 115
LoRaWAN Payload
891E6816E3B30F7285687309478E4CB9C04C39AF
(Encrypted
87B89FA97336D5919FF7F400D69ADE735BF0B498
SCHC=3E090E0000000000011
122538D41BDBA07398783B24E04C9CDEC942002A
80203090C07E2020C05000000
920B564F33ABE64B9C0322A7E0C8D073DB0240F4
00800000110006000186A0020
98F25E06354C2CC836F0E677D18E3E
00189E0020300000600018B80
020300000600018D200203000
00600018EC002030000060001
000006000193A002030000060
001954002)
AppSKey =
0x88F282F3F9E901CDC37C33
11F01050B2
673C84CA 4
MIC
NwkSKey =
0x8A69FAD35B3CF856EC86E
FE77B3F21C4
Message elements Contents LEN (Bytes)
40CD160126800000142748ED7C9F0CE0BA6324C1 128
LoRaWAN (encoded)
4D11ED80420B54CA32891E6816E3B30F72856873
09478E4CB9C04C39AF87B89FA97336D5919FF7F4
00D69ADE735BF0B498122538D41BDBA07398783B
24E04C9CDEC942002A920B564F33ABE64B9C0322
A7E0C8D073DB0240F498F25E06354C2CC836F0E6
77D18E3E673C84CA
LoRaWAN SCHC Fragment 2 (Uplink)
LoRaWAN Header 40 1
(Mtype=010b,RFU=000b,Major
=00b)
LoRaWAN FHDR CD160126800100 7
(DevAddr=260116CDh,FCtrl=1
0000000b,FCnt=1,FOpts=)
14 1
LoRaWAN Fport (F/R RuleID)
A6F8FD9D25D59ED3308393EC55E6BF948E013E42 115
LoRaWAN Payload
7A91FCC607CA3AF68ABE23C7416E15827CE2513F
(Encrypted
B9A235A9561B17D380F2543A560BAF644FBACA1B
SCHC=3D03000006000196E00
0E5D50348D19BCB83C1F80277FABEAC9583AFF05
9C6E435C1EBAF08FD670F4EA027E24F7E9FE9B02
600019A20020300000600019B
5F059A9D70F69D57C1FE54791DFC31
C0020300000600019D6002030
0000600019F00020300000600
01A0A002030000060001A2400
2030000060001A3E002030000
060001A58002030000060001A
72002030000060001A8C00203
0000060001)
AppSKey =
0x88F282F3F9E901CDC37C33
11F01050B2
28DC4820 4
MIC
NwkSKey =
0x8A69FAD35B3CF856EC86E
FE77B3F21C4
40CD16012680010014A6F8FD9D25D59ED3308393 128
LoRaWAN (encoded)
EC55E6BF948E013E427A91FCC607CA3AF68ABE23
C7416E15827CE2513FB9A235A9561B17D380F254
3A560BAF644FBACA1B0E5D50348D19BCB83C1F80
277FABEAC9583AFF059C6E435C1EBAF08FD670F4
EA027E24F7E9FE9B025F059A9D70F69D57C1FE54
791DFC3128DC4820
LoRaWAN SCHC Fragment 3 (Uplink)
40 1
LoRaWAN Header
(Mtype=010b,RFU=000b,Major
=00)
LoRaWAN FHDR CD160126800200 7
(DevAddr=260116CDh,FCtrl=1
0000000b,FCnt=2,FOpts=)
LoRaWAN Fport (F/R RuleID) 14 1
DB5BD320BDFB419791EF6859 12
LoRaWAN Payload
(Encrypted
SCHC=3FAA600203000006000
1AC00)
AppSKey =
0x88F282F3F9E901CDC37C33
11F01050B2
– 22 – IEC 62056-8-12:2023 © IEC 2023
Message elements Contents LEN (Bytes)
363E5E39 4
MIC
NwkSKey =
0x8A69FAD35B3CF856EC86E
FE77B3F21C4
40CD16012680020014DB5BD320BDFB419791EF68 25
LoRaWAN (encoded)
59363E5E39
LoRaWAN SCHC ACK (Downlink)
60 1
LoRaWAN Header
(Mtype=011b,RFU=000b,Major
=00b)
CD160126800100 7
LoRaWAN FHDR
(DevAddr=260116CDh,FCtrl=1
0000000b,FCnt=1,FOpts=)
02 1
LoRaWAN Fport (= RuleID)
AF 1
LoRaWAN Payload
(Encrypted SCHC=40h)
AppSKey =
0x88F282F3F9E901CDC37C33
11F01050B2
E250164E 4
MIC (little endian)
NwkSKey =
0x8A69FAD35B3CF856EC86E
FE77B3F21C4
LoRaWAN (encoded) 60CD16012680010002AFE250164E 14

A.3 Example 3: DLMS®/COSEM Access Service transported through LPWAN
with SCHC fragments
See Table A.3.
Table A.3 – Example – Access Service
Message elements Contents LEN
(Bytes)
D9 1
Access-Request
4000000 4
long-invoke-id-and-priority
date-time 00 1
access-request-body
access-request-specification
04 1
SEQUENCE OF CHOICE
01 1
access-request-get
cosem-attribute-descriptor
0001 2
class-id
0000600100FF 6
instance-id
Message elements Contents LEN
(Bytes)
02 1
attr-id
01 1
access-request-get
cosem-attribute-descriptor
0008 2
class-id
instance-id 0000010000FF 6
02 1
attr-id
02 1
access-request-set
cosem-attribute-descriptor
0014 2
class-id
00000D0000FF 6
instance-id
07 1
attr-id
02 1
access-request-set
cosem-attribute-descriptor
0014 2
class-id
instance-id 00000D0000FF 6
08 1
attr-id
access-request-list-of-data
SEQUENCE OF Data  04 1
00 1
null-data
00 1
null-data
01040203090100090CFF01FFFFFFFFF 90
array
F00000000000901000203090101090C
FF04FFFFFFFFFF00000000000901010
203090102090CFF07FFFFFFFFFF0000
0000000901020203090103090CFF0AF
FFFFFFFFF0000000000090103
0104020809010011FF11FF11FF11FF1 78
array
1FF11FF11FF02080901011102110111
011101110111011101020809010211F
F11FF11FF11FF11FF11FF11FF020809
– 24 – IEC 62056-8-12:2023 © IEC 2023
Message elements Contents LEN
(Bytes)
D94000000000040100010000600100F 218
Access-Request (encoded)
F020100080000010000FF0202001400
000D0000FF0702001400000D0000FF0
804000001040203090100090CFF01FF
FFFFFFFF00000000000901000203090
101090CFF04FFFFFFFFFF0000000000
0901010203090102090CFF07FFFFFFF
FFF0000000000090102020309010309
0CFF0AFFFFFFFFFF000000000009010
30104020809010011FF11FF11FF11FF
11FF11FF11FF0208090101110211011
FF11FF11FF11FF11FF11FF11FF02080
IPv6
60045604001E1180 8
IPv6 Header
IPv6 Source Address FE80000000000000745500FFFE00010 16
FE80000000000000745500FFFE00010 16
IPv6 Destination Address
UDP
0FDB0FDB001E3A86 8
UDP Header
COSEM Wrapper
00010001000100DA 8
COSEM Wrapper Header
IPv6 (encoded) 60045604001E1180FE8000000000000 274
0745500FFFE000100FE800000000000
00745500FFFE0001010FDB0FDB001E3
A8600010001000100DAD94000000000
040100010000600100FF02010008000
0010000FF0202001400000D0000FF07
02001400000D0000FF0804000001040
203090100090CFF01FFFFFFFFFF0000
0000000901000203090101090CFF04F
FFFFFFFFF0000000000090101020309
...