ETSI TS 103 357-2 telegram splitting · Downstream of mioty Service Center (SC) & Application Center (AC)

mioty Protects Telegrams Over the Air. Lumra Proves Stored Records Match What Arrived.

ETSI TS 103 357-2 already gives you TSMA 24-subpacket resilience, 32-bit packet counters, separate NWKKEY and APPKEY symmetric CMAC layers, and standardized typeEui Blueprints. One downstream webhook adds six dispute-ready protections outside your database for 10 cents per sensor, with zero extra radio bytes.

Free 24h Capture Pack Pilot → ▶ Play 90-Sec Walkthrough mioty (/v1/ingest/mioty) Stage 1 to 4 suite schema-tested against ETSI TS 103 357-2, Fraunhofer ACMQTTI, and native SC/AC schemas, with physical hardware capture validation in progress
01 · EXISTING SC/AC & ENDPOINT SPEND
$1 to $5/endpoint/mo
Base-station backhaul, SC/AC hosting & historians
02 · ADD LUMRA CONTINUOUS SEAL 2% TO 5% ADD-ON
$0.10/sensor/mo
$25/mo min · $0.08 at 500+ · $0.06 at 2,000+ · $0 exports
03 · SINGLE DISPUTED INCIDENT
$25k to $500k+at stake
Contested SML billing batch, cold-room loss, or audit

Why dedicated Cloud HSM sealing costs $0.10 per sensor: your mioty Service Center (SC) already reassembles subpackets, and Lumra seals compact JSON digests in automated SHA-256 Merkle batches with zero extra radio bytes.

01 · What Lumra adds to mioty's two security layers

6 Protections Your mioty Service Center, Application Center, and Database Lack Alone

Cryptographically sealed outside your admin boundary on arrival, offline-verifiable with Python 3 and OpenSSL.

01HSM + BLUEPRINTS

Seals CMAC, Raw Bytes & Blueprints

TODAY'S GAP:Symmetric APPKEY CMAC sits on your Application Center (AC), and unversioned JSON Blueprint edits can silently misparse bit-packed readings.
WITH LUMRA:Signs ciphertext, pktCnt, CMAC, and typeEui / mioty4OMS metadata in a Cloud HSM, with deterministic bit-level re-decode (/verify-redecode).
02PKTCNT + ATTACH/DROP

Separates Deleted Rows From TSMA Loss

TODAY'S GAP:Missing rows in SQL look identical whether caused by deleted OBIS readings, Class Z endpoint re-attachment, or >50% subpacket loss.
WITH LUMRA:Audits 32-bit pktCnt chains, seals Class Z ulAttach/ulDetach and BSSCI drops (iot.mioty_drop), and pairs gaps with received/24 subpackets, eqSnr, and foff.
03DUAL TSA + ETA

Time Anchors & Base-Station Consensus

TODAY'S GAP:Endpoint clocks drift, single base stations lose PTP/GPS lock, and internal AC server clocks get challenged in utility billing audits.
WITH LUMRA:Scores multi-base-station nanosecond rxTime clock consensus (eta_mioty_v1) and anchors batches to dual independent RFC 3161 authorities.
040 BYTES OR MS\x01

Zero Battery Drain + Variable-MAC Sign

TODAY'S GAP:Over-the-air public-key signatures blow past 10-byte single-burst meters, inflating TSMA subpackets and draining 10-year batteries.
WITH LUMRA:Seals 10-byte single-burst meters downstream with 0 extra radio bytes, or unpacks compact MS\x01 binary Ed25519 frames (≤254B) on Variable-MAC endpoints.
05SUBMETERING PRESET

Fuses Hybrid Meters & Billing Disputes

TODAY'S GAP:Your Service Center (SC) only vouches for mioty, while utility and cold-room disputes also span LoRaWAN, BMS logs, and calibration PDFs.
WITH LUMRA:Ingests ACMQTTI or native SC/AC JSON and binds hybrid mioty + LoRaWAN/BMS + invoice SHA-256 into one CasePackage (/v1/cases/presets/submetering-dispute).
06OFFLINE + DATA ACT

60-Sec Offline Check & Sealed Feeds

TODAY'S GAP:Regulators, commercial tenants, and EU Data Act third parties reject AC portal logins and unsigned spreadsheet exports.
WITH LUMRA:Verify ProofPacks offline with Python 3 and OpenSSL at $0, or stream signed JSONL feeds designed for EU Data Act Art. 3/4/5 workflows.
Don't take our word for it: alter 1 byte in a live ProofPack in your browser and watch the signature check fail. Test Tamper Detection in 60 Seconds →
▶ 90-second technical walkthrough player

See how Lumra seals mioty Application Center & Service Center uplinks in 90 seconds

Press Play 90s Walkthrough or click any of the 4 stages below to inspect how Lumra accepts your Service Center (SC) or Application Center (AC) output as is via /v1/ingest/mioty, seals ciphertext, packet counter, and CMAC inside a Cloud HSM hash chain, detects a 1-byte edit, and supports offline checking.

01 / 0:00 - 0:26ACTIVE
Downstream AC / SC Ingest
POST /v1/ingest/mioty (0 OTA bytes)
02 / 0:26 - 0:57STEP 2
Artifact Seal & Counter Chain
Ciphertext + PktCnt + CMAC + HSM Seal
03 / 0:57 - 1:19STEP 3
1-Byte Cover-Up Test
Post-incident SQL / CSV edit attempt
04 / 1:19 - 1:42STEP 4
Standalone Offline Check
verify_proofpack.py -> EXIT 0 (No Lock-In)
LIVE PAYLOAD & ARTIFACT INSPECTOR POST /v1/ingest/mioty
Over-the-Air Overhead0 Bytes (10-Yr Battery)
Sealed Integrity ArtifactsCiphertext + PktCnt + CMAC
Seal Latency184 ms (Cloud HSM)
CRYPTOGRAPHIC ENGINE & CHECK OUTPUT ECDSA P-256 + RFC 3161
CHAPTER 1 OF 4
0:00 / 1:40
02 · 30-Second Webhook & MQTT Integration

Connect your mioty Application Center (AC) or Service Center (SC) in 4 steps

Point your existing mioty Application Center (AC) or Service Center (SC) HTTPS webhook or MQTT broker directly at Lumra with no middleware, custom parsers, or payload reshaping required.

  1. 1. Issue a sandbox API key in 60 seconds (or request an MQTT subscription)

    Open https://api.privinet.net/sandbox to issue a self-serve key with the mioty profile enabled out of the box (500 sealed events, 5 device IDs, 20 ProofPack exports, zero credit card), or email [email protected] for a dedicated MQTT v3.1.1 topic binding.

  2. 2. Configure the HTTPS Webhook or ACMQTTI Broker feed (30 seconds)

    In your mioty Application Center (AC) or Service Center (SC) console, add an HTTPS POST webhook pointing to https://api.privinet.net/v1/ingest/mioty with header Authorization: Bearer <pk_live_...>, or point Lumra's MQTT v3.1.1 subscriber at your mioty/<app_root>/+/uplink broker topic. HMAC-signed partner webhooks are also supported at https://api.privinet.net/v1/webhooks/{partner_slug}/mioty.

  3. 3. Send a test uplink and inspect sealed mioty artifacts & Blueprints

    Confirm that your Service Center (SC) or Application Center (AC) output is accepted as is, with the endpoint's ciphertext, packet counter, CMAC, typeEui Blueprint / mioty4OMS metadata, Class Z ulAttach/ulDetach lifecycle events, and base-station rxTime clock consensus (eta_mioty_v1) sealed into the canonical record.

  4. 4. Verify ProofPacks offline with Python 3 and OpenSSL (zero lock-in)

    Standard signed JSON exports and EU Data Act (Reg. 2023/2854 Art. 3/4/5) streaming JSONL telemetry feeds (GET /v1/sources/{id}/sealed-feed) are included with your monthly sensor plan. Any utility customer, quality reviewer, or insurer can verify exported ProofPacks offline using verify_proofpack.py (v1.4.1) and lumra-tsa-bundle.pem or in the browser at privinet.net/audit.html.

03 · Complimentary 24-Hour Capture Pack Pilot

Send one day of Service Center JSON output. Get back a verified ProofPack at $0.

For mioty operators, utilities, and mioty Alliance members: before changing a single production setting, send us a 24-hour JSON or JSONL capture from your Service Center (SC) or Application Center (AC). Within one business day, we return a self-contained ProofPack and 24-hour packet-counter completeness report checkable offline.

01 / What We Need (Anonymized IDs Welcome)

24 hours of uplink JSON, zero radio keys

Share 24 continuous hours of JSON uplinks from 1 to 50+ endpoints (a 2-to-6-hour lab bench capture is also welcome). Hashed or masked 64-bit endpoint EUIs (epEui / EUI) and base-station EUIs (bsEui / gweui) work cleanly as long as each endpoint keeps a consistent pseudonym across the window. Never include NWKKEY, APPSKEY, or personal data.

02 / Accepted Drop-In Capture Formats

Fraunhofer ACMQTTI or native SC / AC JSON

Drop any of these directly into a .jsonl, .json, or .gz export with zero reformatting: (a) Fraunhofer IIS ACMQTTI MQTT dumps on mioty/<app>/<epEui>/uplink carrying baseStations, cnt, data, format, typeEui, and components; or (b) native Service Center (SC) and Application Center (AC) JSON exports from WEPTECH AVA, Swissphone, LZE, or BehrTech stacks.

mosquitto_sub -h <sc-broker-host> -p 8883 -u <user> -P <pass> \ -t 'mioty/+/+/uplink' -F '{"topic":"%t","payload":%p}' > mioty_24h_capture.jsonl
Current Conformance Disclosure: The mioty (/v1/ingest/mioty) Stage 1 to 4 suite (typeEui Blueprint bit-offset re-decode, Class Z ulAttach/ulDetach and BSSCI drop sealing, eta_mioty_v1 multi-base-station clock consensus, optional MS\x01 binary Ed25519 frames, and submetering-dispute preset) is schema-verified against ETSI TS 103 357-2 and Fraunhofer ACMQTTI mioty output schemas, with physical mioty hardware capture validation pending. Operator 24-hour capture packs are replayed in an isolated single-tenant sandbox (retention_policy: "sandbox").
COMPLIMENTARY 1-DAY PILOT · $0

Request a Private Upload Link

Tell us which Service Center (SC) or Application Center (AC) format you run and we will send a private pre-signed upload URL and return your ProofPack within one business day.

  • Self-contained .proofpack.json receipt bundle for your 24h capture
  • Per-endpoint 24h Packet-Counter Completeness Report (missing counter ranges, duplicates, out-of-order arrivals, and resets)
  • Offline one-click browser check at privinet.net/audit.html and CLI check via verify_proofpack.py
  • Sandbox isolation: raw capture purged after delivery at your request
Capture file under 20 MB ready now? Email it directly to [email protected] with subject mioty 24h Capture Pack.
04 · Transparent mioty & Enterprise Pricing

Metered per active sensor for utilities. Predictable for facilities & fleets.

Standard JSON ProofPack exports and standalone offline checking (verify_proofpack.py) are included with every monthly plan, with synchronous Google Cloud KMS HSM arrival signing and ~2-minute dual RFC 3161 batch anchoring (freetsa.org and ts.ssl.com).

Utility & IoT Sensor Metering Tier (mioty)
$0.10 / active sensor / mo
$25/month minimum · zero radio payload overhead

Purpose-built for high-density mioty Service Centers (SC), Application Centers (AC), and Smart Meter Light (SML) utility networks.

  • $0.10 / active sensor / month ($25/mo min): Volume discounts drop to $0.08 at 500+ sensors and $0.06 at 2,000+ sensors
  • Preserves mioty Integrity Artifacts: Seals ciphertext, packet counter, and CMAC from your Service Center (SC) or Application Center (AC) output as is
  • Continuous Cryptographic Sealing: SHA-256 hash chains, packet-counter continuity checks, Google Cloud KMS HSM ECDSA P-256 signatures, and dual RFC 3161 batch anchors
  • Self-Serve JSON Exports & Standalone Checker Included: Export signed JSON records anytime and check them offline via verify_proofpack.py (v1.4.1) at no extra cost
Connect mioty Webhook ($0.10/sensor)
Commercial Fleet Crash Legal-Hold Vault
$5 to $7 / truck / mo
$1,500/mo fleet minimum · $3/truck/mo MGA book (5,000+ units)

Automated collision legal-hold preservation for MyGeotab fleets, Lytx Surfsight dashcams, and commercial auto insurers.

  • Standard Fleet ($5/truck/mo, $1,500/mo min): Automated MyGeotab collision holds, 3-year WORM MP4 + 1Hz ExecuteMultiCall retention, and unlimited instant FRE 902(13)/(14) PDF certificates
  • Pro Fleet ($7/truck/mo, $2,000/mo min): Adds zero-app post-crash driver SMS live-camera walkaround capture, 7-to-10-year WORM retention, and 1-click insurer share rooms
  • Commercial Auto MGA Tier ($3/truck/mo at 5,000+ units): Portfolio-wide FNOL evidence lock and automated subrogation exports
Launch Interactive Crash Demo
Complimentary 24-Hour Capture Pack Pilot
$0 / 24h evaluation
single-tenant sandbox replay · 1-business-day turnaround

Validate downstream mioty sealing and 32-bit packet-counter completeness against your own Service Center (SC) or Application Center (AC) capture before changing production settings.

  • Self-Contained ProofPack Bundle: Returned for your 24-hour JSON or JSONL capture with anonymized endpoint EUIs
  • 24h Packet-Counter Completeness Report: Separates missing counter ranges, Class Z attach/detach events, and BSSCI drops
  • Multi-Source Submetering Fusion: Test hybrid mioty + LoRaWAN/BMS + invoice SHA-256 CasePackages offline
Request 24h Upload Link
Engineering & Evidence Boundary: Lumra records timestamp_trust: "unverified_source_claim" for endpoint and base-station observation timestamps, binds Lumra receipt order and Merkle batch roots, and is structured to preserve received artifacts without claiming sensor calibration accuracy, automatic legal admissibility, or positive EU-qualified status without authenticated LOTL/TL validation. Inspect the full cryptographic specification on the Technical Architecture Page.

Seal your first mioty Application Center or Service Center stream today.

Send us a sample JSON uplink from your mioty Application Center (AC) or Service Center (SC) output and we will return a signed, independently checkable ProofPack free within one business day, or provision your tenant key for https://api.privinet.net/v1/ingest/mioty.