Cisco Cisco Packet Data Gateway (PDG)
SaMOG Local Breakout
▀ Flow-based Local Breakout
▄ SaMOG Administration Guide, StarOS Release 19
88
Flow-based Local Breakout
The Flow-based Local Breakout (LBO) model enables SaMOG to selectively offload certain user data directly to the
Internet without employing an external or internal P-GW or GGSN service, and forward the remaining traffic to an
external P-GW or GGSN (via. the S2a tunnel) depending on configured Layer 4 rules. The User Equipment's (UE) IP
address is allocated by the external P-GW or GGSN service. SaMOG applies NAT addressing to all traffic that are
offloaded directly to the Internet to differentiate between packets intended for local offload, and packets intended to be
forwarded to P-GW or GGSN.
Internet without employing an external or internal P-GW or GGSN service, and forward the remaining traffic to an
external P-GW or GGSN (via. the S2a tunnel) depending on configured Layer 4 rules. The User Equipment's (UE) IP
address is allocated by the external P-GW or GGSN service. SaMOG applies NAT addressing to all traffic that are
offloaded directly to the Internet to differentiate between packets intended for local offload, and packets intended to be
forwarded to P-GW or GGSN.
License Requirements
The Flow-based LBO model requires a separate feature license. This license is mutually exclusive with the LBO -
Enhanced license, and can co-exist with the LBO - Basic license.
Enhanced license, and can co-exist with the LBO - Basic license.
Flow-based LBO models
SaMOG applies Layer 4 rules to the data traffic using Access Control Lists (ACLs) to determine the part of traffic to be
offloaded directly or sent to the P-GW or GGSN service. This decision can be based off an ACL whitelist or an ACL
blacklist. While the ACL whitelist identifies the data to be forwarded to the P-GW or GGSN service, the ACL blacklist
identifies the data to be locally offloaded.
offloaded directly or sent to the P-GW or GGSN service. This decision can be based off an ACL whitelist or an ACL
blacklist. While the ACL whitelist identifies the data to be forwarded to the P-GW or GGSN service, the ACL blacklist
identifies the data to be locally offloaded.
Flow-based LBO using a Whitelist
A flow-based LBO using a whitelist is ideal in situations when a subscriber signs up for some premium content, and this
content must be charged differently. SaMOG uses the ACL to route all traffic intended for the premium content server
to be forwarded to P-GW or GGSN where special charging is applied using the Gx/Gy interface. SaMOG offloads the
rest of the traffic that does not match the ACL directly to the Internet.
content must be charged differently. SaMOG uses the ACL to route all traffic intended for the premium content server
to be forwarded to P-GW or GGSN where special charging is applied using the Gx/Gy interface. SaMOG offloads the
rest of the traffic that does not match the ACL directly to the Internet.
Flow-based LBO using a Blacklist
A flow-based LBO using blacklist is ideal in situations when SaMOG is deployed in a vicinity where a large number of
subscribers access the same content (for example, a streaming video of an event in a stadium where the server is locally
hosted). SaMOG offloads this content directly from the local server, and all other data traffic is routed to the P-GW or
GGSN service.
subscribers access the same content (for example, a streaming video of an event in a stadium where the server is locally
hosted). SaMOG offloads this content directly from the local server, and all other data traffic is routed to the P-GW or
GGSN service.