To deploy SSG EPDG, integration with the following telecommunications operator systems needs to be configured:

• AAA server - for authentication and authorization;
• HSS (only if AAA server is absent);
• PGW - for receiving signaling and voice traffic.

Below are several possible integration cases.

The authorization of the client in EPDG is handled by the Authorization Management Module (AM), which allows implementing several cases on the operator's side.

Conditions:
Operator's AAA operates via the standard SWm interface.

Process:
Authorization Management (AM) module requests authorization from Operator's AAA via SWm, then AAA interacts with HSS via SWx, and during a call, interacts with PGW via S6b.

Conditions:
The operator does not have its own AAA server; in this case, the AM obtains authorization directly from the Operator's HSS via SWx.

Process:
During a call, the AM replaces Operator's AAA: Operator's PGW queries it for authorization confirmation via the S6b interface, the AM queries HSS via SWx.

The operator does not have its own AAA server, but there is some IS, for which it is needed, for example, TWAN or another EPDG. In this case, SSG EPDG can accept requests via the SWm interface and perform authorization on HSS and PGW via standard SWx and S6b interfaces.

The Tunneling Management Module (TMM) is responsible for organizing tunnels between EPDG Core and Operator's PGW. Several cases can be implemented on the operator's side with its help.

Conditions:
Operator's PGW supports EPDG's native interface - S2b.

Process:
Signaling traffic from EPDG to PGW flows through the GTP-C tunnel via the native S2b interface. User Plane (voice traffic) flows through the GTP-U tunnel.

Conditions:
Operator's PGW does not support S2b, only supports S5/S8.

Process:
In this case, TMM emulates the operation of SGW and communicates with PGW via the S5/S8 interface. User Plane (voice traffic) flows through the GTP-U tunnel.