Language:
PRODUCTS
MORE
Quantum Security 🔍 Search Request Access →
gateTelecom — Telecommunications Compliance Gate
// IMMO.QUICK · GATETELECOM · TKG · STGB §206 · BSI/NIS2 · GDPR

Four duty clusters, one deterministic verdict.

gateTelecom forensically seals that a telecommunications operation passes four clusters, consumer protection, interconnect & billing, lawful interception, and network/CRITIS security, before the action takes effect. Support for telecom operators and regulators, never a replacement for a regulator's own recognition as evidence.

In one sentence: gateTelecom checks every telecom operation against consumer-protection, billing, interception, and network-security duties before the action takes effect, and seals the result cryptographically.
✓ RELEVANT IF...
  • You need to legally document lock notices, reminders, and deadlines under §61 TKG
  • You need to safeguard lawful interception measures against expired warrants
✕ NOT RELEVANT IF...
  • You expect the regulator to automatically recognise the result as evidence
  • No telecommunications service or infrastructure is involved
// The problem

Four bodies of law, one operator.

Telecom operators are simultaneously subject to consumer-protection, billing, interception, and network-security duties under the TKG, the Criminal Code, the BSI Act, NIS2, and GDPR. gateTelecom brings all four together in a sealed run.

// Architecture

Four clusters, checked sequentially.

Every cluster is dispositive (material_block_mode: true), a hit blocks bindingly, not merely for documentation.

CLUSTER 1
Consumer Protection (§§57, 61, 62 TKG)
Checks locks, reminders, mitigation claims, and opt-in proof. A lock without a prior reminder or without observing the five-day deadline is blocked.
lock_notice_sent · reminder_sent · unlock_fee_disclosed · optin_confirmed
CLUSTER 2
Interconnect & Billing (§§58, 59, 164, 176 TKG)
Detects CLI spoofing (falsified caller ID via foreign gateways) and checks interconnect billing and number portability against SLA requirements.
cli_origin_verified · interconnect_route_valid · mnp_sla_met
CLUSTER 3
Lawful Interception & KYC (§§165, 170–174 TKG, §206 StGB, GDPR Art. 17)
Checks the validity of judicial warrants, the match between area code and postal code, and adherence to the maximum 180-day traffic-data retention limit.
warrant_valid_until · kyc_local_area_match · traffic_retention_days
CLUSTER 4
Network & CRITIS Security (§170 TKG, BSI, NIS2, 5G)
Verifies BSI certification, firmware attestation for 5G high-risk components (BMI approval), and timely NIS2 incident reporting within 24 hours.
bsi_approval_id · firmware_certified · nis2_incident_reported_within_24h
An important distinction: all four clusters are dispositive
Unlike purely documentary sub-gates, material_block_mode is set to true across all four clusters in gateTelecom. An expired judicial warrant or an exceeded retention period blocks bindingly, not merely for documentation.
// Test results

Seven tested scenarios.

All values on this page are fictional test data and serve only to illustrate the gate logic.

Scenario C1C2C3C4 Verdict Latency
§61 TKG lock without reminder, 30€ delay, 5-day deadlineFAILnot evaluatednot evaluatednot evaluatedBLOCK_T1_UNLAWFUL_LOCK_NOTICE_MISSING (+2)994ms
§§164/176 TKG CLI spoofing, DE number via RU gatewayPASSFAILnot evaluatednot evaluatedBLOCK_T2_CLI_SPOOFING_DETECTED986ms
§§170–174 TKG expired judicial warrant (2024-12-31)PASSPASSFAILnot evaluatedBLOCK_T3_INVALID_WARRANT_EXPIRED1131ms
§172 TKG area code 030 (Berlin) vs postcode 80331 (Munich)PASSPASSFAILnot evaluatedBLOCK_T3_KYC_OR_LOCAL_AREA_FAIL732ms
§165 TKG / GDPR Art. 17: 240-day retention > 180-day limitPASSPASSFAILnot evaluatedBLOCK_T3_TRAFFIC_DATA_OVER_RETENTION997ms
§170 TKG / BSI / NIS2: empty BSI ID, 5G high-risk without BMI, 30h alarm > 24h deadlinePASSPASSPASSFAILBLOCK_T4_BSI_APPROVAL_MISSING (+2)957ms
All clusters passPASSPASSPASSPASSTELECOM_SEALED387ms
Cryptographic chain continuation
Every test produces a deterministic receipt_id (VAR-TELCO-{TENANT}-{SEQ}), an input_snapshot_hash, an HMAC-SHA256 signature, and a merkle_link to the previous receipt. Persistence occurs in the TelecomReceipt entity with a 10-year retention period.
// Clarification

What gateTelecom is not.

  • Not automatic recognition by the Federal Network Agency or another regulator. The gate delivers a cryptographic proof, not regulatory admission as evidence.
  • Not an independent network management system. The gate seals the compliance attestation, it does not operate telecom infrastructure itself.

For telecom operators that want to make consumer protection, interception law, and network security provable.

Request Access →