Cisco Cisco Packet Data Gateway (PDG)
SaMOG Gateway Overview
How the SaMOG Gateway Works ▀
SaMOG Administration Guide, StarOS Release 17 ▄
31
Step
Description
5.
The MRME service sends a RADIUS Accounting Stop Response message to the WLC and clears the call at the SaMOG
Gateway.
Gateway.
6.
The MRME service triggers call deletion by the CGW service.
7.
The CGW service triggers a session deletion on the P-GW by sending a Delete Session Request message over the S2a
interface.
interface.
8.
The P-GW acknowledges the session deletion by sending a Delete Session Response message to the CGW service.
9.
The CGW service sends a Binding Revocation Indication message to the WLC.
10.
The WLC sends a Binding Revocation Acknowledgement message to the CGW service with applicable cause codes. The
CGW service marks the session as deleted upon receiving the message.
CGW service marks the session as deleted upon receiving the message.
SaMOG Gateway Data Flow
The figure below shows the user data flow on the SaMOG Gateway. The table that follows the figure describes each
step in the flow.
step in the flow.
Figure 9. 371100.jpg
Table 9. SaMOG Gateway Data Flow
Step
Description
1.
The UE sends the uplink (UL) data to the WLC.
2.
The WLC sends the user data to the SaMOG Gateway’s CGW service over the established bi-directional GRE tunnel.
3.
The CGW service sends the user data over a GTPU tunnel to the P-GW.
4.
The P-GW maps the downlink (DL) data on the GTPU tunnel to a GRE tunnel to the WLC.
5.
The CGW service sends the user data to the WLC over the GRE tunnel.
6.
The WLC sends the user data to the UE.