Description
Nomadic EPS is a deployable variant of the Evolved Packet System defined by 3GPP to support public safety and mission-critical operations in environments where the regular macro network is unavailable, damaged, or has never been deployed. It is closely tied to the Isolated E-UTRAN Operation for Public Safety (IOPS) concept introduced in Release 13. A Nomadic EPS consists of one or more deployable IOPS-capable eNodeBs, a local core network (typically a lightweight EPC or a local gateway), and the necessary local IP or Ethernet connectivity to interconnect these elements. The system can be transported to an incident scene, powered up, and brought into service independently of the national public land mobile network.
Architecturally, the Nomadic EPS provides radio access through deployable eNBs that broadcast a PLMN identity and support IOPS mode operation. IOPS-enabled UEs are configured to recognize and attach to such networks. The local core network provides the essential EPC functions needed for session management, authentication, and local routing: MME functionality for control-plane procedures, S-GW/P-GW functionality for user-plane anchoring, and HSS-like subscriber data for the locally authorized users. Because the system may operate without backhaul to the central EPC, it must be able to authenticate UEs and authorize services locally, often using pre-provisioned credentials or a local subscriber database.
A key characteristic of Nomadic EPS is its ability to operate in isolation from the normal EPS. When connectivity to the central network is restored, procedures exist to reconcile state, hand over sessions, and return UEs to normal operation. The system also supports local IP connectivity, meaning that UEs attached to the Nomadic EPS can communicate with each other and with local application servers (e.g., command posts, video surveillance) without traffic leaving the incident site. This is essential for low-latency group communication and for scenarios where backhaul is congested or non-existent.
Security is a major consideration. The specifications 33.401 and 33.897 address the security architecture for IOPS and nomadic deployments, including how authentication vectors are managed when the central HSS is unreachable, how keys are derived for local sessions, and how the system protects against unauthorized use of deployable infrastructure. The Nomadic EPS must also support priority and QoS mechanisms so that mission-critical voice and data take precedence over less urgent traffic.
In later releases, the definition was refined to explicitly mention local connectivity for IP or Ethernet and to use the term eNodeB rather than eNB, reflecting a broader scope that includes Ethernet-based local applications. Nomadic EPS remains a foundational concept for public safety broadband, disaster recovery, and tactical communications, and it complements other 3GPP work on isolated operation, non-public networks, and edge computing.
Purpose & Motivation
Nomadic EPS exists to solve the problem of providing reliable broadband public safety communications when the normal cellular infrastructure is unavailable. Traditional commercial networks are designed for continuous coverage and central backhaul; they fail in disasters, remote areas, or tactical situations. Earlier public safety systems (e.g., TETRA) offered voice but limited data. Nomadic EPS brings LTE-based broadband, local IP services, and group communication to the incident scene without dependency on the macro network.
The concept was motivated by the need for deployable, rapidly installable systems that can operate in isolation while still leveraging commercial LTE devices and ecosystem. It allows first responders to use IOPS-enabled UEs that automatically detect and attach to the nomadic network, preserving familiar services and security. By localizing the core network, it reduces latency and backhaul requirements, and it enables local applications such as video streaming from body-worn cameras or drone feeds.
Over time, the definition evolved to explicitly include Ethernet connectivity and to align terminology with 3GPP conventions, reflecting the growing role of local IP networks and edge applications in public safety operations.
What changed in its specifications
The latest release-to-release comparison of specifications that define Nomadic EPS. Each summary describes the whole specification, not only this term.
Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.
Full comparison in TS 23.401 →Rel-19 adds security annex clauses for Store and Forward Satellite operation to TS 33.401. It also adds definitions for feeder link, service link, Store and Forward Satellite operation, and IOPS-enabled UE.
Full comparison in TS 33.401 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Introduced the concept of Nomadic EPS as a deployable system providing radio access via deployable IOPS-capable eNBs, local IP connectivity, and public safety services to IOPS-enabled UEs in the absence of normal EPS. Defined IOPS-enabled UE as a UE configured to use networks operating in IOPS mode.
Wording changed: 'eNB' was replaced by 'eNodeB', and 'local IP connectivity' was broadened to 'local connectivity (e.g. for IP or Ethernet)'. The phrase 'Public Safety services' was lowercased to 'public safety services', and the trailing sentence defining IOPS-enabled UE was removed from the definition.
Defining Specifications
3GPP specifications that define or reference Nomadic EPS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 23.797 vd00 | Isolated E-UTRAN Operation for Public Safety (IOPS) | Rel-13 read |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 read |
| TS 33.897 vd10 | Security for Isolated E-UTRAN Operation | Rel-13 read |