Cisco Cisco Packet Data Interworking Function (PDIF)
SaMOG Gateway Overview
▀ How the SaMOG Gateway Works
▄ SaMOG Administration Guide, StarOS Release 19
34
Step
Description
19.
The CGW originates a “GTPv2 Create Session Request” message on the S2a interface towards PDN-GW, by including S2a
GTP-U TEID to be used for downlink data transfer, MSISDN, IMSI, APN, PAA, PDNType, Bearer-Context-List, APN-
AMBR and Charging characteristic.
GTP-U TEID to be used for downlink data transfer, MSISDN, IMSI, APN, PAA, PDNType, Bearer-Context-List, APN-
AMBR and Charging characteristic.
20.
The PDN-GW allocates the requested IP address for the subscriber and responds to the CGW with a “GTPv2 Create
Session Response” message by including the Cause, PAA, Bearer-Context-List, APN-AMBR and GTP-U PGW TEID for
uplink data transfer.
Session Response” message by including the Cause, PAA, Bearer-Context-List, APN-AMBR and GTP-U PGW TEID for
uplink data transfer.
21.
The CGW responds with a “PMIPv6 PBA” to the WLC, by including the UEs IP address.
22.
A GTPv2 tunnel is established between the CGW and P-GW.
23.
A PMIPv6 tunnel is established between the WLC and CGW.
24.
The WLC initiates a “Radius Accounting-Request” with “Acct-Status-Type” as “Start” and by including the assigned UEs
address.
address.
25.
The MRME proxies the received “Radius Accounting-Request” towards the RADIUS accounting server.
26.
The MRME receives the “Radius Accounting-Response” from the Radius accounting server.
27.
The MRME proxies the received “Radius Accounting-Response” towards the WLC.
SaMOG Gateway Session Establishment (StarOS Release 18 and later)
The figure below shows an SaMOG Gateway session establishment flow in StarOS Release 18 and later. The table that
follows the figure describes each step in the flow.
follows the figure describes each step in the flow.