Cisco Cisco Packet Data Interworking Function (PDIF)
SaMOG Gateway Overview
▀ Network Deployment and Interfaces
▄ SaMOG Administration Guide, StarOS Release 16
20
Network Deployment and Interfaces
The SaMOG Gateway provides IP access from the WLAN UEs to the P-GW and the Packet Data Network (PDN) in the
Evolved Packet Core (EPC) network. From Release 16.0 and above, the SaMOG Gateway provides IP access from the
WLAN UEs to GGSN/P-GW and the Packet Data Network (PDN) over PMIPv6 or EoGRE tunnel.
Evolved Packet Core (EPC) network. From Release 16.0 and above, the SaMOG Gateway provides IP access from the
WLAN UEs to GGSN/P-GW and the Packet Data Network (PDN) over PMIPv6 or EoGRE tunnel.
Deployment Scenarios
Operators deploying SaMOG in their WLAN offload scheme typically fall under one of the three categories described
below:
below:
4G Deployments: The operator has already upgraded their core network elements to EPC specifications and
wants to use SaMOG to provideservices to PLMNs which have the network devices capable of setting up 4G
calls. In addition, the deployed DNS server supports the post release 7 DNS procedures (S-NAPTR queries) to
resolve the P-GW address from APN/P-GW FQDN.
calls. In addition, the deployed DNS server supports the post release 7 DNS procedures (S-NAPTR queries) to
resolve the P-GW address from APN/P-GW FQDN.
A 3G subscriber can connect to an SaMOG Gateway in 4G deployment as long as the STa based AAA server
is capable of fetching the 3G policy from HSS/HLR and convert the 3G profile parameters to 4G parameters as
per 3GPP specification 23.401 and provide the same to the SaMOG during authentication.
is capable of fetching the 3G policy from HSS/HLR and convert the 3G profile parameters to 4G parameters as
per 3GPP specification 23.401 and provide the same to the SaMOG during authentication.
3G Deployments: For operators with a 3G infrastructure, and wants to use SaMOG to provide services only to
3G subscribers nt with RADIUS authentication with a AAA server assuming that the AAA server is capable of
fetching the 3G profile from HLR/HSS and provide the same to SaMOG. The network elements of all the
PLMNs served by this SaMOG are pre-release 8. The DNS server in such a network is capable of doing pre-
release 8 DNS procedures only to resolve GGSN address from APN FQDN.
fetching the 3G profile from HLR/HSS and provide the same to SaMOG. The network elements of all the
PLMNs served by this SaMOG are pre-release 8. The DNS server in such a network is capable of doing pre-
release 8 DNS procedures only to resolve GGSN address from APN FQDN.
A 4G subscriber can connect to an SaMOG Gateway in 3G deployment as long as the RADIUS based AAA
server can fetch 4G profiles from HSS, convert the 4G profile parameters to 3G values, and provide the same
to SaMOG during authentication.
server can fetch 4G profiles from HSS, convert the 4G profile parameters to 3G values, and provide the same
to SaMOG during authentication.
Mixed Mode Deployment: For operators with infrastructure to deploy both 3G and 4G sessions, and wants to
use SaMOG to provide services to both 3G and 4G subscribers.
When a 3G/4G subscriber connects to a PLMN supporting 3G network elements, a GTPv1 session is
established with GGSN for the subscriber.
established with GGSN for the subscriber.
When a 3G subscriber connects to a PLMN supporting 4G network elements, if the DNS procedures result in a
GGSN IP address, GTPv1 call is set for the subscriber. If the DNS query provides a P-GW, or both GGSN and
P-GW interface IP address, a GTPv2 session is established with the P-GW. The AAA server will forward a 3G
QoS profile or map it to a 4G QoS profile, and forward the same to SaMOG. The SaMOG Gateway converts
the QoS back to 3G/4G parameters depending on whether GTPv1 or GTPv2 call is set.
GGSN IP address, GTPv1 call is set for the subscriber. If the DNS query provides a P-GW, or both GGSN and
P-GW interface IP address, a GTPv2 session is established with the P-GW. The AAA server will forward a 3G
QoS profile or map it to a 4G QoS profile, and forward the same to SaMOG. The SaMOG Gateway converts
the QoS back to 3G/4G parameters depending on whether GTPv1 or GTPv2 call is set.
The figure below shows the SaMOG Gateway terminating the WLAN interface from the trusted non-3GPP IP access
network and providing access to the P-GW and the operator’s IP services via GTPv2 over the S2a interface. It also
shows the network interfaces used by the MME, S-GW, and P-GW in the EPC network.
network and providing access to the P-GW and the operator’s IP services via GTPv2 over the S2a interface. It also
shows the network interfaces used by the MME, S-GW, and P-GW in the EPC network.