Cisco Cisco Packet Data Interworking Function (PDIF)
SaMOG Gateway Overview
▀ SaMOG Features and Functionality - Base Software
▄ SaMOG Administration Guide, StarOS Release 19
54
Step
Description
1.
Refer for the sequence of messages between the WLC to SaMOG, and SaMOG to P-GW.
2.
The UE triggers the sequence of messages using SLAAC to get the IPv6 prefix and DHCPv4 to get the IPv4 address.
3.
The WLC is transparent for the received SLAAC and DHCPv6 Info-req to get IPv6 Prefix and configuration parameters by
encapsulating and decapsulating the EoGRE Tunnel header to and from SaMOG.
encapsulating and decapsulating the EoGRE Tunnel header to and from SaMOG.
4.
WLC transparently receives DHCPv4 to get IPv4 address and configuration parameters by encapsulating and decapsulating
the EoGRE Tunnel header to and from SaMOG.
the EoGRE Tunnel header to and from SaMOG.
Offline Charging
The SaMOG Gateway supports generation of CDR files for offline charging. Offline charging works by collecting
charging information concurrently with resource usage and passes the information through a chain of logical charging
functions. At the end of the process, CDR files are generated by the network and transferred to the network operator's
Billing Domain.
charging information concurrently with resource usage and passes the information through a chain of logical charging
functions. At the end of the process, CDR files are generated by the network and transferred to the network operator's
Billing Domain.
For more information on offline charging for the SaMOG Gateway, refer to the SaMOG Gateway Offline Charging
chapter of this guide.
chapter of this guide.
SaMOG Wireless Access Gateway (WAG) Integration
Overview
The SaMOG Gateway supports additional deployment models and access-side connectivity by integrating various
Wireless Access Gateway (WAG) functions. The WAG functions include:
Wireless Access Gateway (WAG) functions. The WAG functions include:
Deployment in environments where the WLC/RGs do not use bridge mode to forward packets between the User
Equipment (UE) and the SaMOG Gateway.
Receive IP packets in 'plain L3' or within GRE, MPLS or VLL tunnels.
Route packets based on the IP address and the Layer 2 tunnel on the access-side to the GTP tunnel for the uplink,
and vice versa for the downlink.
Allow IP address allocation by either WLAN or SaMOG.
Layer 3 IP (L3IP)
The SaMOG Gateway supports out of band DHCP Layer 3 packet processing, and call setup with L3IP access type.
IP address assigned by the WLC (IP@W)
The User Equipment's (UE) IP address is assigned by WLC, and DHCP is not required in the call flow. WLC forwards
the assigned IP address in the Accounting-Start message inside the Framed IP Address field. SaMOG NATs the IP@W
with the IP address assigned by P-GW (IP@G).
the assigned IP address in the Accounting-Start message inside the Framed IP Address field. SaMOG NATs the IP@W
with the IP address assigned by P-GW (IP@G).
IP over GRE (IPoGRE)
The SaMOG Gateway supports GRE encapsulation on the L3IP access-type to ensure a scalable deployment model. The
SaMOG Gateway adds an extra IP and GRE header on top of the plain L3 IP. All control and data packets from one or
more WLCs use the same IPoGRE tunnel. The SaMOG Gateway performs encapsulation and decapsulation before
SaMOG Gateway adds an extra IP and GRE header on top of the plain L3 IP. All control and data packets from one or
more WLCs use the same IPoGRE tunnel. The SaMOG Gateway performs encapsulation and decapsulation before