Cisco Cisco Mobility Unified Reporting Release Note
Generally Available 04-30-2013
Modified Configuration Commands
3-89
GGSN Commands - Modified in Release 12.0
This section provides information on GGSN commands modified in Release 12.0.
virtual-apn
Virtual APN selection is based on configuration parameters like roaming mode, bearer
access service etc. Three more parameters ‘cc-profile’, ‘msisdn-range’, and ‘rat-type’ are
added based on them virtual-apn will be selected. ‘CC-profile option specifies the APN for
charging characteristics (CC)-profile index. The APN selection will be applied to all
subscribers that have msisdn in the configured ‘msisdn-range’. The range has lower and
upper limit configured as ‘from’ and ‘to’ respectively. The ‘rat-type’ option configures the
APN for rat-type (eutran, gan, geran, hspa, utran, wlan) received in the message.
access service etc. Three more parameters ‘cc-profile’, ‘msisdn-range’, and ‘rat-type’ are
added based on them virtual-apn will be selected. ‘CC-profile option specifies the APN for
charging characteristics (CC)-profile index. The APN selection will be applied to all
subscribers that have msisdn in the configured ‘msisdn-range’. The range has lower and
upper limit configured as ‘from’ and ‘to’ respectively. The ‘rat-type’ option configures the
APN for rat-type (eutran, gan, geran, hspa, utran, wlan) received in the message.
Another addition is the ‘msin-range from <start_refix> to <end_prefix>’ keywords have
been added to the MCC-MNC in this command to enable the IMSI prefix based
prepaid/postpaid subscribers selection on GGSN. This enhancement extends the
MCC+MNC based virtual APN selection to MCC+MNC+MSIN Range based virtual APN
selection.
been added to the MCC-MNC in this command to enable the IMSI prefix based
prepaid/postpaid subscribers selection on GGSN. This enhancement extends the
MCC+MNC based virtual APN selection to MCC+MNC+MSIN Range based virtual APN
selection.
Virtual APN selection parameter ‘rat-type’ has been enhanced with the inclusion of a new
keyword “eutran” along with the utran, geran, wlan, gan, and hspa. It is an enhanced 3GPP
standard air interface for LTE mobile networks. Rat-type has also been included as an
optional keyword for MCC+MNC.
keyword “eutran” along with the utran, geran, wlan, gan, and hspa. It is an enhanced 3GPP
standard air interface for LTE mobile networks. Rat-type has also been included as an
optional keyword for MCC+MNC.
CLI (APN Configuration Mode)
virtual-apn { gcdr apn-name-to-be-included {
gn | virtual } | preference
priority
apn
apn_name
[ access-gw-address {
ip_address
|
ip_address/mask } |
bearer-access-service
svc_name
| cc-profile
cc_profile_index [ rat-type {
eutran | gan | geran | hspa | utran | wlan } ] | domain
domain_name
| mcc
mcc_number
mnc
mnc_number
[ msin-range from
msin_range_from
to
msin_range_to
| rat-type { eutran | gan | geran | hspa | utran | wlan } ] | msisdn-range
{ from
msisdn_start_range
to
msisdn_to_range | rat-type { eutran | gan |
geran | hspa | utran | wlan } } | rat-type { eutran | gan | geran | hspa |
utran | wlan } | roaming-mode { home | visiting | roaming } } }
authentication
This command configures the APN’s authentication parameters. A new option
‘prefer-chap-pco’ has been added to be used along with msisdn-auth/imsi-auth parameter.
With this option, if enabled, GGSN performs CHAP authentication if CHAP parameters are
received in Protocol Configuration Options (PCO). However, chap username would be
constructed as msisdn@apn / imsi@apn and chap challenge, chap response parameters
should be used as it is from CHAP parameters received in PCO IE. If CHAP parameters are
not received in PCO IE of CPC Request, GGSN should do normal PAP authentication with
PAP username as msisdn@apn / imsi@apn (ignoring any PAP username if received).
‘prefer-chap-pco’ has been added to be used along with msisdn-auth/imsi-auth parameter.
With this option, if enabled, GGSN performs CHAP authentication if CHAP parameters are
received in Protocol Configuration Options (PCO). However, chap username would be
constructed as msisdn@apn / imsi@apn and chap challenge, chap response parameters
should be used as it is from CHAP parameters received in PCO IE. If CHAP parameters are
not received in PCO IE of CPC Request, GGSN should do normal PAP authentication with
PAP username as msisdn@apn / imsi@apn (ignoring any PAP username if received).