Latency vs. Processing Efficiency

Segment workloads by latency sensitivity, placing critical processing at the edge and delay-tolerant functions centrally, ensuring NIS2 resilience without over-provisioning edge compute.

CyberTRIZ analysis · Telecommunications contradiction NC012 · one of 8,235 worked contradictions published by CyberTRIZ.AI

Regulations

EU_NIS2 IEC_62443 ISO_20000 NIST_RMF EU_GDPR

Business Context

Low-latency telecommunications services require traffic and processing decisions to occur rapidly, often close to users or network access points. Centralized processing can improve resource pooling and computational efficiency, but the additional transport distance and processing path can increase latency. Distributing processing closer to demand reduces response time while potentially creating underutilized computing resources across many locations.

Telecommunications TRIZ Resolution

Processing should be distributed according to workload sensitivity rather than forcing every function into either centralized or edge environments. Latency-critical processing can operate closer to users, while delay-tolerant analysis, storage, and background functions remain centralized where resource pooling is more efficient. Workloads can also migrate dynamically as demand and resource conditions change.

Applicable TRIZ Principles

Principle 1 – Segmentation separates latency-critical functions from workloads that tolerate centralized processing.

Principle 3 – Local Quality places processing resources where specific service conditions require them.

Principle 15 – Dynamics moves or scales workloads according to latency, demand, and infrastructure conditions.

Expected Outcome

Lower latency for critical services

Higher overall computing utilization

Reduced unnecessary edge duplication

Better alignment between processing location and workload requirements

Decision Indicators

Early indicators include:

Centralized processing meets efficiency targets but fails latency requirements.

Edge resources remain significantly underutilized.

All workloads are assigned to the same processing architecture regardless of latency sensitivity.

Low-latency services require widespread duplication of computing resources.

Processing location is fixed even when demand patterns change.

TRIZ principles applied

P1 SegmentationP3 Local qualityP15 Dynamics

Controls that address this (22)

EU_NIS2-CTRL-001 - Daily safeguarding reconciliationoperational · critical priority · Daily reconciliation between safeguarded customer balances, core ledger balances and safeguarded bank accounts. Variances above EUR 100 must EU_NIS2-CTRL-002 - Critical ICT incident reportingoperational · critical priority · All major ICT incidents impacting payment services, customer data or availability must be classified within 4 hours and reported under DORA EU_NIS2-CTRL-003 - GDPR breach notification workflowoperational · critical priority · Personal data breaches must be assessed within 12 hours and reported to the Belgian DPA within 72 hours where risk to data subjects exists.