Trusted Wi-Fi in a Mobile Core: Where a TWAN Fits for Wi-Fi Offload, VoWiFi and Fixed-Mobile Convergence

November 19, 2025
Mobile Networks
5 out of 5
Trusted Wi-Fi in a Mobile Core: Where a TWAN Fits for Wi-Fi Offload, VoWiFi and Fixed-Mobile Convergence
Trusted Wi-Fi is Wi-Fi that an operator uses as a trusted access to its mobile core, and it is one of several ways to bring Wi-Fi into that core. This article shows where a trusted WLAN access network (TWAN) fits for traffic offload, for Wi-Fi Calling (VoWiFi) and for fixed-mobile convergence (FMC). We also show where another path fits better.

A TWAN fits where the operator decides to treat a Wi-Fi network as trusted. It connects the phone to the core through a gateway to the PGW (PDN Gateway), and its attach procedures involve no IPsec tunnel from the phone. A network the operator has not declared trusted, which usually means Wi-Fi it does not control, goes through an ePDG (evolved Packet Data Gateway). Some traffic can also leave the Wi-Fi without entering the core.

What is a TWAN, and when does an operator treat Wi-Fi as trusted?

A TWAN is Wi-Fi that an operator uses as a trusted access to its EPC (Evolved Packet Core). It has three parts: the access points, a TWAP (Trusted WLAN AAA Proxy) that relays authentication signalling, and a TWAG (Trusted WLAN Access Gateway) that connects to the PGW. The home operator decides whether a network counts as trusted.

The standard gives a security criterion. The home operator may identify a network as trusted when it considers every security feature group of that network sufficiently secure. It may also decide for reasons unrelated to security. The phone learns the result from a policy configured on it or from an indication during 3GPP-based access authentication with the SIM. If the operator has declared nothing, the phone treats the network as untrusted. One trust relationship then covers every packet data network the phone reaches through that Wi-Fi.

In practice, trusted access suits Wi-Fi that the operator owns and manages. Untrusted access suits any network the operator does not control, including a subscriber’s own home router. Our glossary has a short definition of the TWAG. Our Stingray TWAG combines the TWAP and the TWAG in one node.

How can an operator offload traffic to its own Wi-Fi without IPsec tunnels?

Two paths fit. With NSWO, the offload path for flows that skip the EPC, the phone sends chosen IP flows straight out of the Wi-Fi. With a TWAN, traffic goes to the PGW over S2a, and the attach procedures involve no IPsec tunnel from the phone. NSWO keeps traffic out of the core; the TWAN path brings it in.

In NSWO the phone routes specific IP flows through the WLAN without traversing the EPC. The operator picks the flows with a policy configured on the phone or set through ANDSF (Access Network Discovery and Selection Function), and user preferences count as well. No ePDG is needed. A TWAN can support S2a, NSWO or both, and the AAA (authentication, authorization and accounting) server tells it what the subscriber is allowed to use.

On the EPC-routed path, the interfaces inside the TWAN must be integrity- and confidentiality-protected. The phone authenticates with its SIM using EAP-AKA’ (Extensible Authentication Protocol, Authentication and Key Agreement).

Path Where the traffic goes What the phone keeps
EPC-routed through a TWAN (S2a) To the PGW in the core An IP address from the PGW; the address can be kept on a move from LTE in Single-Connection and Multi-Connection modes
NSWO Straight out of the Wi-Fi, not through the EPC The local IP address of the Wi-Fi; no address is kept when the phone moves between Wi-Fi and 3GPP access

The two paths can share one network. An informative annex of the standard describes separate SSIDs for each path, or one SSID that gives one subscriber EPC-routed access and another subscriber offload only. In Multi-Connection mode, a TWAN supports NSWO alongside one or more PDN connections.

A phone that supports S2a finds such a network through ANQP (Access Network Query Protocol) procedures from the Wi-Fi Alliance Hotspot 2.0 specification. It needs a valid USIM and the policies configured on it. With Passpoint, a phone with a SIM then associates with the access point automatically, without the user handling credentials.

Which gateway does VoWiFi need on operator hotspots and on a customer’s home Wi-Fi?

On a customer’s home Wi-Fi, which an operator typically does not control and does not treat as trusted, VoWiFi goes through an ePDG over an IPsec tunnel. On a hotspot the operator owns, it can treat the network as trusted and connect it through a TWAN, and that network then needs no ePDG. Trust is the operator’s decision.

GSMA publishes one profile for each path. IR.51 covers voice, video and SMS over untrusted Wi-Fi access through S2b and says that trusted access over S2a is not covered. NG.106 is its non-binding counterpart for trusted Wi-Fi access over S2a, and it also requires telephony based on the IMS (IP Multimedia Subsystem).

Each profile gives the IMS service its own connection. In the trusted profile, the TWAN must provide Multi-Connection Mode. The phone sets up a separate SWw instance for the APN (Access Point Name) of the IMS service. SWw is the interface between the phone and the WLAN access network. In the untrusted profile, the phone sets up a separate IPsec tunnel to the same ePDG for that APN.

Wi-Fi the operator does not manage, for example a subscriber’s own home router Operator-owned hotspot treated as trusted
Trust Treated as untrusted; the operator does not control the network Treated as trusted by the operator’s decision; the operator owns and manages the network
Gateway ePDG TWAG, so that network needs no ePDG
Phone to the core IPsec tunnel to the ePDG Attach procedures involve no IPsec tunnel from the phone
Link to the PGW S2b S2a
GSMA profile IR.51 NG.106
IMS APN Separate IPsec tunnel to the same ePDG Separate SWw instance, Multi-Connection Mode required

An operator may also leave its own hotspot untrusted. The ePDG path then applies, as on any other network that is not trusted.

Emergency calls follow the same split. On the untrusted path, the phone selects an ePDG for emergency services. On the trusted path, the TWAN tells the phone during authentication whether it supports emergency services. Which access the phone uses for an emergency call when both Wi-Fi and LTE are available depends on the phone and on operator settings.

When a PDN connection moves from LTE to a TWAN in Single-Connection mode, the TWAN sets a Handover Indication so that the PGW can re-allocate the same IP address. The PGW can also decide to allocate a new one. In Multi-Connection mode, one or more PDN connections move the same way, with a Handover Indication from the TWAN. On the untrusted path, the ePDG asks for the same address only if the phone supports address preservation and sent the address.

Our Stingray ePDG serves the untrusted path and supports Wi-Fi Calling. Our Stingray PGW works with the native S2b interface.

How do converged fixed-mobile operators connect carrier Wi-Fi to the mobile core?

Through the same trusted and untrusted paths, with the fixed network as the access. A trusted fixed Wi-Fi connects to the EPC over S2a and STa. For an untrusted one, the phone builds an IPsec tunnel to an ePDG, which connects to the PGW over S2b. The providers decide which path applies.

3GPP maps a trusted fixed access onto the trusted WLAN model. The EPC and the fixed network then interact only over S2a and STa, and the functional split inside the fixed network is outside 3GPP scope.

Broadband Forum TR-203 (2012) puts the broadband gateway of the fixed network at the S2a boundary. The PDN gateway interfaces with it directly, and the fixed network proxies the authentication of the phone to the home 3GPP network. TR-291 (2014) shows two trusted deployments. In one, the TWAG sits on the multi-service BNG (broadband network gateway) of the fixed network. In the other, a dedicated router acts as both TWAG and TWAP.

In the untrusted case, the traffic crosses the fixed network between the phone and the ePDG in the mobile network. A business agreement and a trust relationship between the two providers are assumed.

For offload, traffic can stay in the fixed network: it is routed to an external network directly, and offload and EPC-routed traffic can co-exist.

One scenario for a provider that runs both networks: its own home routers carry a second SSID of the operator with Passpoint support. A subscriber connects with the SIM, and the router traffic reaches the TWAG over IP. Separately, our Stingray Service Gateway runs fixed and mobile subscribers through the same user plane on standard x86 servers.

What should an operator check before choosing a Wi-Fi access path?

Check who decides on trust, which TWAN connection modes are offered, whether the phones support the path, how roaming and emergency calls are handled, and which traffic should stay local. The answers decide whether a TWAN, an ePDG or local offload fits.

  • Who decides that a network is trusted, and does the phone learn it through authentication or from a configured policy?
  • Which connection modes does the TWAN offer? Keeping the IP address on a move from LTE needs Single-Connection or Multi-Connection mode. If the phone and the network support no mode in common, the TWAN uses Transparent Single-Connection mode, if the network supports it. That mode does not keep the address. The GSMA trusted-access profile requires Multi-Connection Mode.
  • Does the phone discover the network through ANQP and support S2a? Discovery needs a valid USIM and the policies configured on the phone.
  • Which flows should leave the Wi-Fi locally, and is the policy configured on the phone or set through ANDSF?
  • When subscribers roam, does the TWAN have STa to the registered or home network of the phone? Roaming without it is not supported in 3GPP Release 19.
  • Does the TWAN tell the phone that it supports emergency services?
  • On a Single-Connection handover, is it acceptable that the PGW may allocate a new IP address instead of the old one?

How we work with operators on trusted Wi-Fi

We build the gateways on both sides of this choice. Our Stingray TWAG connects Wi-Fi networks to the operator core as a trusted access per 3GPP TS 23.402. It works with the operator’s existing PGW, HSS (Home Subscriber Server) and AAA server, so the core does not have to be replaced.

In our solution, the phone finds the operator’s network through a Passpoint profile or a known SSID and connects with its SIM. The TWAP handles SIM authentication through the operator’s AAA server over STa, and the TWAG sets up the session on the PGW over S2a.

Our Stingray TWAG supports Multi-Connection Mode, which the GSMA trusted-access profile NG.106 requires for VoWiFi. In this mode, the phone requests each PDN connection over WLCP (WLAN Control Protocol), which is protected by DTLS. One subscriber can then hold several PDN connections at once, for example one for internet access and a separate one for the IMS APN.

Our Stingray PGW has an S2a interface for trusted Wi-Fi networks (TWAN) and an S6b interface that integrates it with authentication systems for subscribers on non-3GPP access, over both S2a and S2b.

Our Stingray ePDG brings in networks the operator does not trust and supports Wi-Fi Calling. Our Stingray TWAG and Stingray ePDG hand subscribers over to the same core.

For our PGW and ePDG, the operator fills in the form on the product page. We clarify the task and discuss traffic volume, available equipment and the functionality needed. Our engineers install the selected software for the operator’s test and adapt it to the task. For the TWAG and ePDG pair, we can also run a demonstration on our test bed with the operator’s own SIM cards and access point, from connection to call.

FAQ

What is the difference between a TWAN and a TWAG?

A TWAN is the whole trusted Wi-Fi access network. A TWAG is one part of it: the gateway that terminates S2a towards the PGW. The other parts are the access points and the TWAP.

Does trusted Wi-Fi need an IPsec tunnel from the phone?

The TWAN attach procedures involve no IPsec tunnel from the phone, and the interfaces inside the TWAN must be integrity- and confidentiality-protected. An untrusted network goes through an ePDG over IPsec instead.

Can VoWiFi run over a trusted Wi-Fi network?

Yes, GSMA publishes a separate non-binding profile, NG.106, for IMS voice, video and SMS over trusted Wi-Fi access through S2a. Our Stingray TWAG supports Multi-Connection Mode.

Can a phone keep its IP address when it moves between LTE and a TWAN?

It can, in Single-Connection and Multi-Connection modes. In the Single-Connection procedure, the TWAN sets a Handover Indication, and the PGW can re-allocate the same address or allocate a new one.

Is a TWAN used in 5G networks?

In the 5G system, trusted non-3GPP access has its own gateway, the TNGF (Trusted Non-3GPP Gateway Function). Unlike on the EPC path above, the phone sets up an IPsec tunnel with it to register.

Related pages