Cisco Cisco Packet Data Gateway (PDG)
SaMOG Changes in Release 16
SaMOG Enhancements for 16.0 ▀
Release Change Reference, StarOS Release 16 ▄
423
With this feature, SaMOG acts as the AAA server and DHCP server to the user equipment (UE) that connects to the
WLAN network. SaMOG processes all the control packets from the UE and maintains the subscriber session to provide
3G/4G access. Acting as the DHCP-server, SaMOG creates the PDP context with GGSN/PGW and obtains the IP
address to allocate to the UE through DHCP-Response in the access-side. The interface with GGSN is similar to the
TTG's Gn' interface with GGSN for 3G, and the existing SaMOG's S2a interface with PGW for 4G. The DHCP and data
packets originating from the UE are forwarded by the Residential Gateway/WLC node through the EoGRE tunnel to
SaMOG.
WLAN network. SaMOG processes all the control packets from the UE and maintains the subscriber session to provide
3G/4G access. Acting as the DHCP-server, SaMOG creates the PDP context with GGSN/PGW and obtains the IP
address to allocate to the UE through DHCP-Response in the access-side. The interface with GGSN is similar to the
TTG's Gn' interface with GGSN for 3G, and the existing SaMOG's S2a interface with PGW for 4G. The DHCP and data
packets originating from the UE are forwarded by the Residential Gateway/WLC node through the EoGRE tunnel to
SaMOG.
The MRME service maintains all the access network parameters (Radius client and access client details) locally. The
MRME service determines the session’s access-type and if a request should be accepted or rejected, based on the NAS
IP (AVP in the Access-Request/ Accounting-Request) and Source IP of the request by looking up the local
configuration and conveys the same to CGW for session setup.
MRME service determines the session’s access-type and if a request should be accepted or rejected, based on the NAS
IP (AVP in the Access-Request/ Accounting-Request) and Source IP of the request by looking up the local
configuration and conveys the same to CGW for session setup.
Command Changes
twan-profile
Creates a Trusted Wireless Access Network (TWAN) profile and enters the TWAN Profile Configuration Mode for the
current context. The TWAN profile contains information on the RADIUS client addresses (WLC) and access-type
corresponding to the RADIUS clients.
current context. The TWAN profile contains information on the RADIUS client addresses (WLC) and access-type
corresponding to the RADIUS clients.
configure
context context_name
[ no ] twan-profile twan_profile_name
end
access-type
This command allows you to specify the access-type for the Radius client or specify a default access type for all Radius
clients under a TWAN profile.
clients under a TWAN profile.
configure
context context_name
twan-profile twan_profile_name
access-type [ client { ipv4/ipv6_address[/mask ] } ] { eogre | pmip }
no access-type { client { ipv4/ipv6_address[/mask ] } | eogre | pmip }
end
radius
This command allows you to specify the IP address and shared secret of the RADIUS accounting and authentication
client from which RADIUS accounting and authentication requests are received.
client from which RADIUS accounting and authentication requests are received.
configure
context context_name