Skip to content
Use case 182

Mobile Core Network Functions

A deployment concept for mobile network operators, telecom vendors, governments and managed network providers.

Deployment concept · Suitability unverified
Telecommunications, Cloud, Finance and Digital Assets

Why this environment matters

The platform for mobile core network functions handles subscriber identity, session control, routing and policy inside cellular networks. The operational risk is specific: software compromise can expose subscriber data, redirect traffic or disrupt service across a large population. NØNOS could provide a smaller, memory-safe base for dividing that workflow into signed, least-privilege components and restoring it from a known state after each sensitive session or incident.

The security challenge

The threat model should assume that one component will eventually fail or be exploited. In this case, software compromise can expose subscriber data, redirect traffic or disrupt service across a large population. These platforms concentrate identity, connectivity, keys, transactions and multi-tenant workloads. A single privileged compromise can propagate quickly or create irreversible financial effects. The aim is to prevent that single failure from automatically gaining the keys, devices, records and network paths of the whole platform.

How the capsule model could help

A candidate NØNOS architecture would run each network function as a signed capsule with explicit peer, database and key-store access rather than broad platform trust. The design would prioritise attested execution and a signed software supply chain, supported by ephemeral privileged sessions and scoped key and network access. Each capsule would carry a declared policy for files, networks, devices and secrets, and unknown or altered software would not receive the same authority as an approved component.

Separate address spaces and capability checks can limit cross-process reach. They cannot stop harmful use of legitimate permissions, prove AI decisions correct or substitute for domain-specific safety controls.

Deployment requirements

Deployment would still require secure hardware, key governance, independent approvals, monitoring, resilience engineering and compliance controls. NØNOS can narrow software trust but cannot remove business or market risk.

Current public-beta limitations, hardware support and application availability must be assessed before any pilot. Neither this use case nor an industry source establishes NONOS certification or a current customer deployment.

Who could buy or integrate it?

  • Mobile-core software vendors qualifying execution platforms
  • Mobile operators buying supported core-network stacks
  • Telecom cloud integrators implementing network-function hosting

Industry examples: Ericsson, Nokia. These are research prospects, not represented as NONOS customers, partners or endorsers.

Opportunity research

Separate the market from the model.

Published industry benchmark
US$41.4 billion

5G infrastructure

Global · 2025 · annual market estimate

Radio, core and associated network infrastructure hardware and services; excludes mobile-operator service revenue.

Modelled global devices
50K–2M

Candidate OS endpoints

Hypothetical planning range · 2025

Low, hypothetical planning assumptions. Hardware eligibility, procurement and adoption remain unverified.

Illustrative annual licensing
$7.5M–$1.4B

USD / year at full model coverage

Device scenario × assumed US$150–$700 per device / year.

Not a revenue forecast, announced price or measured serviceable market.

Device calculation

Hypothetical global planning range, 2025 scenario: assume 500–2,000 mobile network operators and substantial private-core deployments × 100–1,000 candidate OS endpoints per site/asset = 50,000–2,000,000 endpoints. Counting unit: durable mobile-core compute hosts/VMs; subscribers and functions sharing a host excluded. Site/asset counts and endpoint densities are author assumptions, not a measured installed base. Coverage is limited to the defined equipped subset; includes all candidate endpoints within that assumed subset. Hardware eligibility, certification, adoption and achievable NØNOS share are unverified; overlaps other cases.

5G infrastructure market report ↗

Context only, inherited market research; not a device/site denominator. Original monetary-market scope and geography are preserved in benchmark. This source does not establish the assumed worldwide site count or endpoint density.

How to interpret the figures

Adjacent or broader commercial market benchmark; not the NØNOS OS market, licensable-device count or revenue forecast.

Modelled candidate endpoints × assumed annual USD per-endpoint price. Price is an author assumption, not a vendor quote. Full-range mathematical scenario only: not a revenue forecast or TAM; excludes adoption timing, procurement, certification, support costs, channel economics and attainable market share. Case totals overlap and must not be added.

Inherited research compiled 13 Sep 2026; publisher estimates, not independently audited.

Read the full methodology

Explore NONOS

Choose your
NONOS experience.

Discover the platform for your organisation or explore the software.

You can reopen this chooser from the footer at any time.