LoRaWAN® Testbed with IPv6 for DLMS UA
TR011-1.0.0
©2022 LoRa Alliance® Page 10 of 12
The authors reserve the right to change
specifications without notice.
The RECOMMENDED Rule Identifier (RuleID) values for DLMS over LoRaWAN SCHC profile
are shown in Table 2. Use of these values by the SCHC gateway and the DUT will reduce the
configuration complexity of the Testbed.
Note: One RuleID is recommended as a minimum for compression/
decompression, additional rules can be defined by the user of the
testbed.
Mechanism Compression/
Decompression
Ack-on-Error
fragmentation
Ack-Always
fragmentation
RuleID value 30 20 21
Table 2: Recommended RuleID
6.3 Testbed Configuration
The Testbed SHALL support a configuration interface which allows the Testbed to
communicate with the DLMS UA CTT as defined in [DLMSYELLOWBOOK], as well as
provisioning of the DUT.
The DUT root keys are revealed to the Join Server of the Testbed. As such, the DUT SHALL
not be used in deployment unless its root keys have been replaced subsequent to testing.
6.4 Testbed Operation
The DLMS UA testing environment is described in [DLMSYELLOWBOOK].
The CTT runs on an arbitrary PC connected to an Ipv6 network. The Ipv6 network connecting
the DLMS UA CTT and the Testbed SHALL be configured to support end-to-end
communication between the CTT and the Testbed, and between the CTT and the DUT.
The Testbed SHALL be able to interface with the DLMS UA CTT and provide a report of the
testbed status and components via In2 as defined in [DLMSYELLOWBOOK].
6.5 Testbeds for different regional parameters
Different Testbed implementations MAY be used to cover different LoRaWAN Regional
Parameters specified in [RP002].
6.6 Documentation and Technical Support
Provider of a Testbed SHALL provide documentation to explain how to set up and use the
Testbed with the DLMS UA CTT. In addition, the Testbed provider SHALL provide support to
the DLMS UA.
