Cisco Cisco Packet Data Gateway (PDG)

SaMOG Gateway Overview

Network Deployment and Interfaces ▀

SaMOG Administration Guide, StarOS Release 16 ▄

Table 3. Logical Network Interfaces on the SaMOG Gateway

Interface

Description

WLAN
Interface

The interface to the WLCs and WLAN UEs in the trusted non-3GPP IP access network has not yet been defined in
the 3GPP standards. The SaMOG Gateway uses Remote Access Dial In User Service (RADIUS) messages generated
by the IP access network to provide session information such as the IP addresses of the WLAN UEs to the EPC
network via the WLCs and to set up the access side associations.

STa
Interface

The interface from the SaMOG Gateway’s MRME service to the 3GPP AAA server, the STa interface is used for
WLAN UE authentication. It supports the transport of mobility parameters, tunnel authentication, and authorization
data. The EAP-AKA, EAP-SIM, and EAP-AKA’ methods are used for authenticating the WLAN UEs over this
interface.

S2a
Interface

The interface from the SaMOG Gateway’s CGW service to the GGSN/P-GW, the S2a interface runs the
GTPv1/GTPv2 protocol to establish WLAN UE sessions with the GGSN/P-GW.

Transport Combinations

The table below lists the IPv4 transport combinations for the SaMOG Gateway, and whether each combination is
supported for deployment in this release.

Table 4. Transport Combinations for the SaMOG Gateway

IP Address

Allocated by the P-

GW for the WLAN

UEs

RADIUS Authentication and

Accounting (between the WLCs

and the SaMOG Gateway)

PMIPv6 Interface

(between the WLCs

and the SaMOG

Gateway)

EoGRE Interface

(between the WLCs

and the SaMOG

Gateway)

Is this Combination

Supported for

Deployment?

IPv4

Yes

Important:

Currently, SaMOG does not support IPv6 Transport with other network elements.