SaMOG supports Radius Access-Request, Radius Accounting-Request and DHCP messages as the triggers for session creation.
Based on the AP/WLC capabilities, SaMOG can support session establishment in the following ways:
When the AP/WLC is capable of RADIUS-based authentication, SaMOG acts as a AAA server and initiates session creation when it receives a RADIUS Access-Request from the AP/WLC.
When the AP/WLC is capable of only forwarding DHCP messages from the UE through an EoGRE tunnel, SaMOG initiates session creation on receiving DHCP Discover and DHCP Request messages from the AP/WLC.
When the AP/WLC is not capable of establishing EoGRE connections, is configured with a DHCP server, and the UE IP is allocated by the AP, SaMOG acts as an accounting server and allocates an IP. SaMOG then performs NAT between the IP allocated by the AP, and the IP allocated by SaMOG to establish a session for the subscriber.
With this feature, the SaMOG Gateway can also initiate session creation when it receives a PMIPv6 (PBU) message from the access point (AP). This feature integrates SaMOG as a gateway in deployment architectures where the AP/WLC can only initiate PMIPv6 messages, and not RADIUS or DHCP messages.
The following licenses are required for this feature:
SaMOG General license (3G and 4G)
SaMOG Local Breakout - Enhanced license to configure a local P-GW
Relationship to Other Features
DHCP-triggered and RADIUS-based Session Creation
DHCP-triggered and RADIUS (Access and Accounting) triggered sessions can co-exist with the PMIPv6-based sessions if the AP initiating the sessions are on different TWAN profiles. These TWAN profiles must have a corresponding session trigger configured.
The PMIPv6-based sessions can be recovered for both unplanned failures and planned migrations.