GCRI · Technology
Communications and network technology
Communications and network technology cover the systems that carry voice, data and control signals, including fixed, mobile, satellite and undersea links. They are critical for coordination during crises and for the operation of other infrastructure. Critical Infrastructure stewards this page for the Nexus Consortium.
The workspace for communications and network technology.
Telemetry network
The Global Centre for Risk and Innovation (GCRI) · Communications and network · Run R-4557 · Example interface, not a record
- Channels reporting91of 100Normal
- Median latency74ms
- Records failing checks1.7per 1,000Watch
- Backlog33min
Latency, p95
Events
- 06:25WarnChannel C-77 stale
- 07:49InfoSchema v5 accepted
- 08:48ErrorChecksum mismatch, batch quarantined
- 08:34DoneReplay complete
GCRI · Telemetry network. Telemetry network: example names and illustrative values, not a record.
What communications and network technology covers.
- 01
Core methods
network topology analysis; traffic engineering; radio propagation modelling; redundancy and diversity planning; protocol design; outage analysis.
- 02
Data and instruments
network performance monitoring; outage reports; spectrum measurements; cable and tower registries; routing tables.
- 03
Validation
Network designs are tested through simulation, field measurement and failover drills. Post-incident reviews compare expected and observed performance.
- 04
Limits
Shared ducts, landing points and power supplies create hidden common-mode failures. Demand surges during emergencies can exceed planned capacity.
- 05
Use in risk decisions
Communications analysis shows how outages cascade to payments, emergency services and grid control. It informs priorities for redundancy and emergency communication plans.
Communications networks are governed by ITU and IETF standards.
| Reference | What it sets |
|---|---|
| ITU-T and ITU-R recommendations | Telecommunication and radio standards |
| Common Alerting Protocol (ITU-T X.1303) | Public warning message format |
| IETF RFC series | Internet protocols |
How the process runs.
Process
Communications and network technology: Source to evidence record
A source is registered and assessed, its record labelled and classified, and a Digital Evidence Passport carries provenance; a correction reaches every dependent record.
01 Intake
- 01Identify the sourceSource · The source stewardDiscovery is not ingestion. Source identification records the source class, steward, institutional role and jurisdiction.
- 03Register the sourceStepRegistration makes a discovered source a governed participant in the evidence lifecycle. It implies no endorsement or certification.
02 Assessment
- 04Jurisdiction and rights classificationGateRights classification identifies licence, consent, confidentiality and reuse limits. The result determines access and routing.
- 05Evidence quality assessmentStepQuality assessment decides whether a record is fit for a defined use. Quality is multidimensional and never a single score.
- 06Evidence labelStepEvery finding carries one of nine evidence labels. Missing data is shown as missing, never as zero.
03 Record
- 07Evidence classificationRecordClassification gives records lifecycle states, such as source-verified, public-safe or restricted. States can coexist and set evidence use.
- 08Source release and identifierRecord · NXS-GRX (canonical data, provenance and risk)A source release records rights, temporal coverage and source lineage. A UNI is allocated through a catalogue and never typed by hand.
- 09Digital Evidence PassportRecordThe passport records provenance, quality, rights, jurisdiction, permitted use and history, so evidence keeps its context when it travels.
04 Use and correction
- 02Correction reaches dependent recordsStep · NXS-GRX (canonical data, provenance and risk)A source correction propagates to dependent cuts and products without rewriting old results.
- 10Public-safe reviewGatePublic-safe review decides whether a record can be shared publicly. It is a distinct stage and is not validation.
Data protocols: evidence lifecycle · Data protocols: core data objects and evidence records · The Global Risks Index (NXS-GRX)Designed programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The data-protocol pages describe a design, not a running system.
Connectivity as a shared dependency.
Telecommunications carry warnings, payments, grid control and emergency coordination. Their own dependencies (power at cell sites, submarine cables, a few internet exchange points) make them a channel through which local failures spread. Warning systems must work when networks are congested or partly down.
- Map backup power duration at cell sites.
- Identify cable landing and exchange concentration.
- Test warning delivery under congestion.
- Applications on Critical Infrastructure and Cyber and Digital Resilience.
Platforms that apply this method.
Who maintains this page.
Critical Infrastructure stewards communications and network technology: it keeps this description current and reviews how the method is applied across the platforms.
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
Why does one institution host every method page?
How do I suggest a correction to a method page?
Contribute evidence from this page.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Bring a method, a dataset or a question.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.