Cisco Cisco Packet Data Gateway (PDG)
SaMOG Gateway Overview
SaMOG Services ▀
SaMOG Administration Guide, StarOS Release 19 ▄
15
In addition, for class type Interactive, further categorization is done in combination with traffic handling priority and
allocation-retention priority. Data packets falling under the category of each of the traffic patterns are tagged with a
DSCP marking. Each traffic class is mapped to a QCI value according to mapping defined in TS 23.203. Therefore,
DSCP values must be configured for different QCI values.
allocation-retention priority. Data packets falling under the category of each of the traffic patterns are tagged with a
DSCP marking. Each traffic class is mapped to a QCI value according to mapping defined in TS 23.203. Therefore,
DSCP values must be configured for different QCI values.
DSCP markings can be configured to control the DSCP markings for downlink packets. The IP header of the packet is
updated with the value in TOS field. Note that there is no tunnel at the access side in SaMOG Gateway, hence the TOS
field in the subscriber IP packet is marked with the DSCP value directly.
updated with the value in TOS field. Note that there is no tunnel at the access side in SaMOG Gateway, hence the TOS
field in the subscriber IP packet is marked with the DSCP value directly.
GTPUv1 Support toward the P-GW—CGW
The SaMOG Gateway's CGW service supports GTPUv1 towards the P-GW as defined in 3GPP TS 29.281, V11,
including the following functions:
including the following functions:
The SaMOG Gateway's CGW service supports fragmentation and reassembly of the outer IP packets that flow
over the S2a interface via GRE tunnels, and supports reassembly of the incoming packets, including stripping
the GRE encapsulation and tunneling the resultant packets to the GGSN/P-GW via GTP encapsulation. The
CGW service supports GRE payloads over IPv4 transport only.
the GRE encapsulation and tunneling the resultant packets to the GGSN/P-GW via GTP encapsulation. The
CGW service supports GRE payloads over IPv4 transport only.
Routing of packets between the GGSN/P-GW and the WLAN UE via the WLC.
Tunnel management procedures for session creation and deletion.
Path management procedures for path existence checks.
Handling of the Recovery IE for detecting path failures.
GTP based Interface Support—CGW
The SaMOG Gateway's CGW service supports the GTPv2/GTPv1-based S2a/Gn interface towards the GGSN/P-GW for
session establishment per 3GPP TS 29.274 and 29.060 Release 11.5, including the following functions:
session establishment per 3GPP TS 29.274 and 29.060 Release 11.5, including the following functions:
Routing of packets between the GGSN/P-GW and the WLAN UE via the WLC.
Establishment of flows towards the WLC and the GGSN/P-GW.
Tunnel management procedures for session creation and deletion.
Path management procedures for path existence checks.
Handling of the Recovery IE for detecting path failures.
Important:
SaMOG does not initiate any MODIFY_BEARER_COMMAND (to P-GW) or
UPDATE_PDP_CONTEXT (to GGSN) message when a QoS update notification is received from the AAA server
during reauthentication. SaMOG expects the AAA server to initiate an RAR for notification of any QoS updates (QoS
changes are notified in the AA-Answer).
during reauthentication. SaMOG expects the AAA server to initiate an RAR for notification of any QoS updates (QoS
changes are notified in the AA-Answer).
GRE Tunnel Support—CGW
The SaMOG Gateway's CGW service supports dynamic per-session Generic Routing Encapsulation (GRE) tunnels from
the trusted 3GPP WLAN per RFC 5845.
the trusted 3GPP WLAN per RFC 5845.
P-GW Selection for LTE-to-WiFi Mobility—CGW
During LTE-to-WiFi mobility, the SaMOG Gateway’s CGW service selects the same P-GW that anchored the session
over LTE. The CGW service selects the GGSN/P-GW via an internal trigger from the SaMOG Gateway’s MRME
service.
over LTE. The CGW service selects the GGSN/P-GW via an internal trigger from the SaMOG Gateway’s MRME
service.