Incorporating Wi-Fi Networks

Since both mobile and satellite traffic ultimately route through the mobile core, it may seem logical to treat Wi-Fi as trusted non-3GPP access and backhaul Wi-Fi traffic directly to the core. While this approach offers advantages—such as enabling the mobile operator to charge for Wi-Fi traffic or apply consistent deep-packet inspection (DPI) regardless of whether the traffic comes from the mobile network, satellite, or Wi-Fi—it’s worth reconsidering when designing the architecture for Wi-Fi integration.

The reality is, subscribers do not typically care about how the mobile network operator builds or integrates their networks. Their primary expectation is to receive a «converged service» with good Quality of Experience (QoE). Therefore, if there is a more cost-effective and efficient way to integrate Wi-Fi services, this option should be seriously considered—regardless of what the 3GPP specifications suggest.

As discussed in the Lessons from the Past chapter, history has shown that most customers favor local traffic breakout, as this approach simplifies management, reduces latency, and enhances user experience. Importantly, the introduction of NTN D2C satellites has not fundamentally changed the perceived value of local breakout from the Wi-Fi perspective. Learning from past experiences, the focus should be on delivering seamless, cost-effective, and high-quality services to the end-user.

So, there is no compelling reason to backhaul zero-rated (free) traffic to the mobile core, and traffic can be directed to a central DPI without relying on the traditional 3GPP backhauling architecture. Additionally, a variety of control functions—such as charging and policy management—can be decentralized and handled at the network edge, enhancing flexibility and efficiency.