Cisco Cisco Packet Data Gateway (PDG)
SaMOG Gateway Overview
SaMOG Services ▀
SaMOG Administration Guide, StarOS Release 17 ▄
17
Normal: <prefix+pseudonym-id>@nai.epc.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org
Decorated: nai.epc.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org!<prefix+pseudonym-
id>@nai.epc.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org
id>@nai.epc.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org
Important:
Currently, SaMOG does not support multi-PLMN. If the PLMN ID of a UE changes during a re-
attach procedure, the User-Name changes from root to decorated NAI format or vice versa. The SaMOG service simply
logs the event and continutes with the session setup. The IPSG manager is updated with the permanent NAI (root
format) and sent to the WLC to be included in the PBU for the PMIPv6 session. If the WLC does not use the NAI
format in the PBU, call setup fails as the PBU is rejected. To avoid the change from root to decorated NAI or vice versa,
specify a serving PLMN ID with an IMSI range. When a serving PLMN ID changes, the existing call is taken down and
a re-attach procedure is initiated.
logs the event and continutes with the session setup. The IPSG manager is updated with the permanent NAI (root
format) and sent to the WLC to be included in the PBU for the PMIPv6 session. If the WLC does not use the NAI
format in the PBU, call setup fails as the PBU is rejected. To avoid the change from root to decorated NAI or vice versa,
specify a serving PLMN ID with an IMSI range. When a serving PLMN ID changes, the existing call is taken down and
a re-attach procedure is initiated.
The pseudonym-id part of the Pseudonym NAI complies with 3GPP 23.003 standards.
The following are examples of a typical NAI:
For EAP AKA authentication: 2<pseudonym-
id>@nai.epc.mnc<homeMNC>.mnc<homeMCC>.3gppnetwork.org
nai.epc.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org!2<pseudonym-
id>@nai.epc.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org
id>@nai.epc.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org
For SIM authentication: 3<pseudonym-id>@nai.epc.mnc<homeMNC>.mnc<homeMCC>.3gppnetwork.org
nai.epc.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org!3<pseudonym-
id>@nai.epc.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org
id>@nai.epc.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org
For EAP AKA’ authentication: 7<pseudonym-
id>@nai.epc.mnc<homeMNC>.mnc<homeMCC>.3gppnetwork.org
nai.epc.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org!7<pseudonym-
id>@nai.epc.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org
id>@nai.epc.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org
EAP Identity of Root NAI Formats—MRME
The SaMOG Gateway supports the use of the EAP identity of the Root NAI in the following format:
username@otherrealm
The username part of the Root NAI complies with RFCs 4187, 4816, and 5448 for EAP AKA, EAP SIM, and EAP
AKA’, respectively.
AKA’, respectively.
The following are examples of a typical NAI:
For EAP AKA authentication: 0<IMSI>@wlan.mnc<MNC>.mcc<MCC>.3gppnetwork.org
For EAP SIM authentication: 1<IMSI>@wlan.mnc<MNC>.mcc<MCC>.3gppnetwork.org
For EAP AKA' authentication: 6<IMSI>@wlan.mnc<MNC>.mcc<MCC>.3gppnetwork.org
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