<![CDATA[What are the bandwidth and verification trade-offs between raw A-XDR hex payloads and edge JSON translation in DLMS MQTT gateways?]]>

🛡️ Technical Redaction & Safe Harbor Warning:
Cloud broker endpoints and telemetry structures use standardized synthetic vectors.

In cellular AMI architectures (NB-IoT / 4G Cat.1), smart meters push telemetry for load profile 1.0.99.1.0.255 and clock 0.0.1.0.0.255 to cloud brokers (MQTT / CoAP per IEC 62056-53 Clause 7.1).
There are two competing architectural paradigms:

  • Paradigm A (End-to-End Native DLMS): Meter sends raw binary DLMS Push (Class 40) A-XDR frames inside MQTT binary payloads; cloud microservices perform parsing.
  • Paradigm B (Edge JSON Translation): Cellular modem parses DLMS locally and publishes structured JSON objects ({"voltage_l1": 230.1, "energy": 1420.5}).

What are the bandwidth cost, cryptographic integrity, and firmware maintainability trade-offs at 10M+ meter scale?

]]>https://dlms.sharur.org/topic/71/what-are-the-bandwidth-and-verification-trade-offs-between-raw-a-xdr-hex-payloads-and-edge-json-translation-in-dlms-mqtt-gatewaysRSS for NodeFri, 16 Oct 2026 19:14:29 GMTSun, 23 Aug 2026 03:53:21 GMT60<![CDATA[Reply to What are the bandwidth and verification trade-offs between raw A-XDR hex payloads and edge JSON translation in DLMS MQTT gateways? on Sun, 23 Aug 2026 03:53:33 GMT]]>Looking closely at Paradigm A payload parsing for energy 1.0.1.8.0.255:

DB 08 4D 4D 4D 00 00 00 00 01 00 00 00 05 30 1A 2B 3C 4D 5E 6F 70 81 92 A3 B4 C5 D6 E7 F8

The cloud ingestion pipeline decrypts the 0xDB General-Glo-Ciphering payload and verifies the 12-byte MAC tag directly, providing end-to-end auditability at minimal bandwidth consumption per IEC 62056-53.

]]>https://dlms.sharur.org/post/266https://dlms.sharur.org/post/266Sun, 23 Aug 2026 03:53:33 GMT<![CDATA[Reply to What are the bandwidth and verification trade-offs between raw A-XDR hex payloads and edge JSON translation in DLMS MQTT gateways? on Sun, 23 Aug 2026 03:53:28 GMT]]>However, in non-billing sensor networks (e.g. distribution transformer monitoring over CoAP), CBOR (RFC 8949) provides a compelling middle ground:
CBOR retains type self-description while saving 60% bandwidth compared to JSON.
Nevertheless, for regulated metering, Green Book Chapter 8 General-Glo-Ciphering (0xDB) binary frames remain the global utility standard.

]]>https://dlms.sharur.org/post/265https://dlms.sharur.org/post/265Sun, 23 Aug 2026 03:53:28 GMT<![CDATA[Reply to What are the bandwidth and verification trade-offs between raw A-XDR hex payloads and edge JSON translation in DLMS MQTT gateways? on Sun, 23 Aug 2026 03:53:26 GMT]]>For large-scale utility operations, Paradigm A (Raw Binary A-XDR) is overwhelmingly superior for three critical reasons per Green Book Chapter 8:

  1. Cellular Data Bandwidth Cost:
    A 96-point daily load profile in native compact A-XDR is ~1.2 KB. The same dataset serialized to JSON with key strings expands to 8.5 KB+ (7x bandwidth expansion). Across 10 million SIM cards, this difference accounts for millions in monthly cellular carrier fees.

  2. Cryptographic Non-Repudiation:
    In Paradigm A, the raw frame contains the meter's GMAC authentication tag computed inside the secure element. In Paradigm B, translating to JSON at the modem breaks the cryptographic chain of custody, invalidating legal metrology audits.

  3. Firmware Decoupling:
    When new OBIS objects are added to meter profiles, Paradigm A requires updating only cloud parser schemas, without touching millions of field modem firmware images.

]]>https://dlms.sharur.org/post/264https://dlms.sharur.org/post/264Sun, 23 Aug 2026 03:53:26 GMT