Cisco Cisco Packet Data Interworking Function (PDIF)
SaMOG Changes in Release 16
SaMOG Enhancements for 16.0 ▀
Release Change Reference, StarOS Release 16 ▄
435
show apn-profile full all
With this release, the following fields have been added to the output of this command in support of the SaMOG offline
charging feature:
charging feature:
Accounting Context Name (SaMOG) : <acct-context>
Accounting GTPP Group Name (SaMOG) : <gtpp-group-name>
Accounting Mode (SaMOG) : Gtpp
Accounting Policy (SaMOG) : <policy-name>
show gtpp group name <name>
With this release, the following fields have been added to the output of this command in support of the SaMOG offline
charging feature:
charging feature:
Record-Type (SaMOG) : SGSNPDPRECORD/sgwrecord (only for SAMOG mixed license)
CSCug95483, CSCuj80861 - SaMOG support for 3G subscribers
Feature Changes
SaMOG Support for 3G Subscribers
This feature enables the use of SaMOG gateway to service 3G subscribers by anchoring GTPv1 WiFi sessions to the
GGSN of existing 3G networks. Billing and other 3G services like DPI are available for the subscriber attached to the
WiFi session. On the data plane, SAMOG accepts L3 WiFi packets, encapsulates them into GTP tunnels, and forwards
them to GGSN. These packets are then decapsulated in the downlink direction by SAMOG and forwarded to the WiFi
network.
GGSN of existing 3G networks. Billing and other 3G services like DPI are available for the subscriber attached to the
WiFi session. On the data plane, SAMOG accepts L3 WiFi packets, encapsulates them into GTP tunnels, and forwards
them to GGSN. These packets are then decapsulated in the downlink direction by SAMOG and forwarded to the WiFi
network.
The AAA server is selected based on the local policy configuration that contains the serving PLMN (derived from NAI)
of the subscriber. The configuration also indicates the authentication method (RADIUS or STa) for that AAA server.
The call type (3G or 4G) depends on the subscriber profile information received from the AAA server.
of the subscriber. The configuration also indicates the authentication method (RADIUS or STa) for that AAA server.
The call type (3G or 4G) depends on the subscriber profile information received from the AAA server.
SaMOG used in an operator's WLAN offload scheme typically follow the models outlined below:
3G only Packet Core (Pre-release 8 Mobile Packet Core (MPC)): The network nodes in this model are not
Release 8 complaint. MRME uses the Radius interface towards AAA Server for authentication and fetches the
3G specific attributes of the authenticated user such as IMSI, MSISDN, APN from the Radius Access-Accept
Message from the AAA Server.
3G specific attributes of the authenticated user such as IMSI, MSISDN, APN from the Radius Access-Accept
Message from the AAA Server.
Overlay 3G/4G network (Release 8 Complaint Evolved Packet Core (EPC) Nodes): This is a deployment
model where EPC nodes and 3G MPC coexist. Assuming that the 3GPP AAA Server is Release 8 compliant,
3G subscribers are authenticated using the STa interface. As a 4G network can support an STa interface,
Radius-based authentication is used only for 3G subscribers.
3G subscribers are authenticated using the STa interface. As a 4G network can support an STa interface,
Radius-based authentication is used only for 3G subscribers.
Important:
As 3GPP specifications do not provide guidance for receiving 3G QoS
parameters on STa interface or supporting a GTPv1 call with STa authentication, this feature for
3G/GTPv1 support with STa authentication is a proprietary solution until the 3GPP specifications
are updated to accommodate the same.
3G/GTPv1 support with STa authentication is a proprietary solution until the 3GPP specifications
are updated to accommodate the same.
License Requirements