Cisco Cisco Packet Data Gateway (PDG)
SaMOG Gateway Overview
SaMOG Services ▀
SaMOG Administration Guide, StarOS Release 18 ▄
21
If the prefix for the user-name is uncategorized (not between 0 and 9), SaMOG considers the username portion of the
NAI as non-IMSI based.
NAI as non-IMSI based.
User Equipment (UE) Identity—MRME
In Release 18 and later, the SaMOG Gateway can receive the User Equipment's (UE) MAC address as the UE's identity
in the Calling-Station-ID AVP in the Radius message (Access-Request). The UE's identity can then be forwarded over
the GTPv1 or GTPv2 interface in the IMEI Software Version (SV) IE to GGSN, or Mobile Equipment Identity (MEI)
IE to P-GW.
in the Calling-Station-ID AVP in the Radius message (Access-Request). The UE's identity can then be forwarded over
the GTPv1 or GTPv2 interface in the IMEI Software Version (SV) IE to GGSN, or Mobile Equipment Identity (MEI)
IE to P-GW.
As the UE identity (MAC address) is 12 Bytes long (6 Bytes in the TBCD format), and the total length of the IMEIsV is
8 bytes, the additional 2 Bytes can be padded with an user configurable filler value.
8 bytes, the additional 2 Bytes can be padded with an user configurable filler value.
Access Point (AP) Location—MRME
In Release 18 and later, the SaMOG Gateway can share the location information of the AP in the User Location
Information (ULI) IE during the PDP context setup, and update the locations as Update Context Requests on the GTPv1
interface.When SaMOG detects a change in the AP's location during handovers, an Update PDP Context message is
triggered.
Information (ULI) IE during the PDP context setup, and update the locations as Update Context Requests on the GTPv1
interface.When SaMOG detects a change in the AP's location during handovers, an Update PDP Context message is
triggered.
SaMOG supports a new format to facilitate AP location in the Called-Station-ID AVP forwarded in the Radius
messages. APs are assigned AP-Names which contain the location details and its MAC address (identity). The AP
location (CGI) consists of the Location Area Code (LAC) and the Cell Identity (CI). SaMOG supports the following
formats in the Called-Station-ID AVP:
messages. APs are assigned AP-Names which contain the location details and its MAC address (identity). The AP
location (CGI) consists of the Location Area Code (LAC) and the Cell Identity (CI). SaMOG supports the following
formats in the Called-Station-ID AVP:
<
MAC
>
mac<
MAC
>
<
MAC
>:<
SSID
>
mac<
MAC
>:<
SSID
>
cgi<
CGI
>:<
SSID
>
mac<
MAC
>:cgi<
CGI
>
cgi<
CGI
>:mac<
MAC
>
mac<
MAC
>:cgi<
CGI
>:<
SSID
>
cgi<
CGI
>:mac<
MAC
>:<
SSID
>
For example, if an AP is assigned LAC = 1235, CI = 6789, AP-MAC = 11-22-33-44-55-66, and SSID = test, the Called-
Station-ID AVP will contain cgi<12356789>:mac<112233445566>:test.
Station-ID AVP will contain cgi<12356789>:mac<112233445566>:test.
Diameter STa Interface Support—MRME
The SaMOG Gateway complies with 3GPP Release 11 SaMOG specifications for the STa interface as defined in TS
29.273 V11.4. The STa interface is defined between a non-3GPP access network and a 3GPP AAA server/proxy. The
SaMOG Gateway uses the STa interface to authenticate and authorize the WLAN UEs.
29.273 V11.4. The STa interface is defined between a non-3GPP access network and a 3GPP AAA server/proxy. The
SaMOG Gateway uses the STa interface to authenticate and authorize the WLAN UEs.
Operator Policy Support (IMSI-based Server Selection)—MRME
The SaMOG Gateway’s MRME service supports the selection of a 3GPP AAA proxy based on the IMSI via the
operator policy feature.
operator policy feature.