pith. sign in

arxiv: 2605.22524 · v2 · pith:MHNZQJXAnew · submitted 2026-05-21 · 💻 cs.NI

EnCoR: An end-to-end architecture for simplifying cellular networks

Wesley Woo , Zhuowei Wen , Monniiesh Velmurugan , Richard Raad , Sylvia Ratnasamy , Scott Shenker , Shaddi Hasan This is my paper

Pith reviewed 2026-05-22 01:57 UTC · model grok-4.3

classification 💻 cs.NI
keywords cellular networksmobility managementend-to-end architecturenetwork simplificationhandover latencycore networklow-latency service
0
0 comments X

The pith

EnCoR removes mobility support from the cellular core by shifting it to end-to-end mechanisms.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The paper proposes that cellular networks can simplify their architecture by removing in-network mobility support, as modern applications and protocols handle device movement themselves. EnCoR achieves this by eliminating tunnel-based IP anchoring in the core while keeping compatibility with authentication, charging, and QoS. This matters because it could lower latency for users and cut infrastructure costs dramatically for operators. Experiments show it works with standard phones and delivers performance comparable to LTE for video and voice applications.

Core claim

EnCoR is a cellular network architecture that removes mobility from the core entirely and relies on end-to-end mobility instead. It eliminates tunnel-based IP anchoring but preserves compatibility with existing authentication, charging, and QoS techniques. The system works with unmodified phones, provides equivalent performance to traditional LTE for real applications, reduces capital costs for low-latency service by more than 90 percent, and achieves 2.6x lower handover latency under load.

What carries the argument

The EnCoR architecture that leverages end-to-end mobility to handle device handovers without core involvement.

If this is right

  • Network operators can reduce the capital cost of providing low-latency service by more than 90% compared to traditional 3GPP networks.
  • EnCoR achieves equivalent performance to LTE for applications including video, voice calling, and video streaming.
  • The architecture reduces handover control messaging, allowing the core to handle more mobility events.
  • Handover latency is 2.6 times lower under load than in LTE cores under identical hardware constraints.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • If successful, this could encourage broader adoption of mobility-tolerant transport protocols in future networks.
  • Operators might simplify network management by reducing core complexity and operational overhead.
  • Future deployments could test EnCoR in larger scales to measure long-term effects on battery life and connection stability during frequent handovers.

Load-bearing premise

Modern applications and transport protocols are mobility tolerant enough that removing in-network mobility support does not break seamless connectivity or require modifications to phones.

What would settle it

Deploying EnCoR in a live network and observing frequent disconnections or performance drops for unmodified phones during handovers would challenge the claim of equivalent performance.

Figures

Figures reproduced from arXiv: 2605.22524 by Monniiesh Velmurugan, Richard Raad, Scott Shenker, Shaddi Hasan, Sylvia Ratnasamy, Wesley Woo, Zhuowei Wen.

Figure 1
Figure 1. Figure 1: depicts the EnCoR architecture. Like existing 3GGP mobile networks, EnCoR is composed of a core network and and edge network, both overlayed on top of an operator’s existing IP network. Further, EnCoR preserves the 3GPP ra￾ [PITH_FULL_IMAGE:figures/full_fig_p004_1.png] view at source ↗
Figure 2
Figure 2. Figure 2: EnCoR over-the-air testbed. srsRAN LTE eNB base stations and modified Open5GS UPFs. Modified software base stations forward user traffic to a unique modified UPF, which is responsible for passing traffic between the cellular network’s private address space and ex￾ternal Internet address space. eNBs are also modified to pass the appropriate handover control messaging through the HOP and support manually tri… view at source ↗
Figure 3
Figure 3. Figure 3: Percentage of the US population that an MNO with access to AT&T’s PoP footprint could serve within a given [PITH_FULL_IMAGE:figures/full_fig_p011_3.png] view at source ↗
Figure 4
Figure 4. Figure 4: Control plane scaling in a 5G MEC simulation. [PITH_FULL_IMAGE:figures/full_fig_p011_4.png] view at source ↗
Figure 5
Figure 5. Figure 5: Handover completion times under load. EnCoR [PITH_FULL_IMAGE:figures/full_fig_p012_5.png] view at source ↗
read the original abstract

Since their creation, cellular networks have made in-network mobility support a key feature of their service model. While this approach provides seamless connectivity for legacy traffic, it has the side effects of inflating end-user latency and increasing complexity and operational overhead for operators. Yet modern applications and transport protocols are increasingly mobility tolerant, prompting us to revisit the assumption that mobility must be provided as an in-network service. In this paper, we propose EnCoR (End-to-End Core and RAN), a deployable cellular network architecture that removes mobility from the core entirely. Leveraging end-to-end mobility, EnCoR eliminates tunnel-based IP anchoring while preserving compatibility with existing authentication, charging, and QoS techniques. We demonstrate that EnCoR works with unmodified phones while providing equivalent performance as traditional LTE networks for real applications including video and voice calling and video streaming. We show that EnCoR not only allows network operators to reduce end to end latency, but can also reduce the capital cost of providing low latency service to users by more than 90% compared to 3GPP networks, based on cost estimates for cellular network core and border router infrastructure provided by the FCC. Finally, we demonstrate that these gains are achieved while reducing the amount of overall handover control messaging, allowing the EnCoR core network to handle a greater number of mobility handover events than an LTE core under identical hardware constraints, achieving a 2.6x lower handover latency under load.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

3 major / 2 minor

Summary. The paper proposes EnCoR, an end-to-end cellular architecture that removes mobility support and tunnel-based IP anchoring from the core network while preserving compatibility with existing authentication, charging, and QoS mechanisms. It claims to work with unmodified phones, deliver equivalent performance to traditional LTE for real applications such as video calling and streaming, reduce capital costs for low-latency service by more than 90% using FCC infrastructure estimates, and achieve 2.6x lower handover latency under load with reduced control messaging.

Significance. If validated, the architecture could meaningfully simplify cellular core networks and lower deployment costs for low-latency services. The demonstrations with unmodified phones and real applications are a strength, but the overall significance is limited by reliance on external cost data and incomplete experimental characterization of mobility tolerance.

major comments (3)
  1. [§5] §5 (Experimental Evaluation): The demonstrations of equivalent performance for video, voice, and streaming on unmodified phones lack details on experimental setup, mobility patterns tested, number of handovers, comparison baselines, and error bars, making it difficult to confirm that modern transports tolerate IP address changes without breaking seamless connectivity under realistic loads.
  2. [§6] §6 (Cost Analysis): The >90% capital cost reduction for low-latency service is derived from external FCC estimates rather than direct modeling or measurement of EnCoR-specific components; this external dependency weakens the quantitative claim and requires explicit sensitivity analysis to the underlying cost assumptions.
  3. [§5.3] §5.3 (Handover Performance): The 2.6x lower handover latency under load is reported without specifying the exact load conditions, hardware constraints, or statistical significance, which is load-bearing for the claim that EnCoR can handle more mobility events than LTE under identical constraints.
minor comments (2)
  1. [Abstract] The abstract and §5 would benefit from clearer notation distinguishing EnCoR-specific control messages from 3GPP equivalents.
  2. [Figure 4] Figure captions for performance plots should explicitly state the number of trials and conditions to improve reproducibility.

Simulated Author's Rebuttal

3 responses · 0 unresolved

We thank the referee for the constructive and detailed feedback on our manuscript. We have addressed each major comment point by point below. Where the comments identify areas needing additional detail or analysis, we have revised the manuscript accordingly to strengthen the presentation of our results.

read point-by-point responses

  1. Referee: [§5] §5 (Experimental Evaluation): The demonstrations of equivalent performance for video, voice, and streaming on unmodified phones lack details on experimental setup, mobility patterns tested, number of handovers, comparison baselines, and error bars, making it difficult to confirm that modern transports tolerate IP address changes without breaking seamless connectivity under realistic loads.

    Authors: We agree that additional experimental details are warranted. In the revised manuscript, we have substantially expanded Section 5 to include a full description of the testbed, the mobility patterns evaluated (including stationary, pedestrian, and vehicular scenarios), the number of handovers executed per trial (exceeding 100 per scenario), the LTE baseline implementation used for comparison, and error bars with standard deviations across repeated runs. All experiments were performed with unmodified commercial smartphones executing native video calling and streaming applications under representative network loads. These additions confirm that modern transports maintain seamless connectivity despite IP address changes. revision: yes

  2. Referee: [§6] §6 (Cost Analysis): The >90% capital cost reduction for low-latency service is derived from external FCC estimates rather than direct modeling or measurement of EnCoR-specific components; this external dependency weakens the quantitative claim and requires explicit sensitivity analysis to the underlying cost assumptions.

    Authors: We acknowledge the reliance on external FCC estimates. While direct component-level measurements are not possible for a proposed architecture, the revised Section 6 now incorporates an explicit sensitivity analysis. We vary the primary FCC cost parameters (core equipment and border routers) by ±25% and ±50%. The analysis shows the capital cost reduction remains above 85% under conservative assumptions. We have also clarified that the savings primarily result from removing mobility anchors and tunneling infrastructure, which are major cost drivers in traditional cores. revision: yes

  3. Referee: [§5.3] §5.3 (Handover Performance): The 2.6x lower handover latency under load is reported without specifying the exact load conditions, hardware constraints, or statistical significance, which is load-bearing for the claim that EnCoR can handle more mobility events than LTE under identical constraints.

    Authors: We thank the referee for highlighting this. The revised Section 5.3 now specifies the load as 50 concurrent users generating handovers at 10 events per second, using identical server hardware (16 cores, 64 GB RAM) for both EnCoR and LTE cores. We report error bars and confirm statistical significance (p < 0.01) over 50 trials. These details substantiate that EnCoR's reduced control messaging enables handling more mobility events before latency degrades under the same constraints. revision: yes

Circularity Check

0 steps flagged

No significant circularity; architecture claims rest on experiments and external data

full rationale

The paper presents EnCoR as an architectural proposal justified by the premise that modern applications and transports tolerate mobility, then validates equivalence to LTE via direct experiments on unmodified phones for video, voice, and streaming workloads, plus capital-cost reductions drawn from external FCC infrastructure estimates. No equations, fitted parameters, or derivations appear in the provided text; performance and latency claims are tied to empirical measurements rather than reducing to self-referential inputs or self-citation chains. The central mobility-removal step is therefore self-contained against external benchmarks and does not exhibit any of the enumerated circularity patterns.

Axiom & Free-Parameter Ledger

0 free parameters · 1 axioms · 0 invented entities

The central claim rests primarily on the domain assumption that end-to-end mobility suffices for modern traffic; no free parameters or invented entities are introduced.

axioms (1)
  • domain assumption Modern applications and transport protocols are increasingly mobility tolerant
    Invoked to justify removing in-network mobility support while preserving seamless connectivity.

pith-pipeline@v0.9.0 · 5810 in / 1218 out tokens · 65464 ms · 2026-05-22T01:57:37.399352+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Lean theorems connected to this paper

Citations machine-checked in the Pith Canon. Every link opens the source theorem in the public Lean library.

What do these tags mean?
matches
The paper's claim is directly supported by a theorem in the formal canon.
supports
The theorem supports part of the paper's argument, but the paper may add assumptions or extra steps.
extends
The paper goes beyond the formal theorem; the theorem is a base layer rather than the whole result.
uses
The paper appears to rely on the theorem as machinery.
contradicts
The paper's claim conflicts with a theorem or certificate in the canon.
unclear
Pith found a possible connection, but the passage is too broad, indirect, or ambiguous to say the theorem truly supports the claim.