Adding NAD Location Information to Access-Request Messages
Steel-Belted Radius Carrier core provides a special attribute handling feature which allows you to add NAD location information to proxied Access-Request messages.
This section describes how this feature works, and the files which must be configured to enable this feature.
Service providers might require the location of the mobile device that is requesting access. For example, a service provider might offer weather reports or advertising based on the location of the mobile device.
You can configure an Access-Request to include the location of the NAD through which the proxied request was processed. The NAD is geographically near the mobile device. The location of the NAD closely approximates the location of the mobile device.
When a mobile device is outside the area of its provider, it roams by sending the request to a local foreign AAA (FAAA) server that is owned by another provider. The FAAA server proxies (forwards) the request to the appropriate home AAA (HAAA) server for the user.
For proxied requests, Steel-Belted Radius Carrier can perform a lookup to find a NAD location based on an attribute (usually NAS-Identifier or NAS-IP-Address). The attribute that is used to look up the NAD location is user-configurable as the AttributeToIdentifyNAS in the locspec.ctrl file.
Figure 12 shows that Steel-Belted Radius Carrier queries the locspec plug-in to find the value of the attribute that identifies the NAD location. The NAD location is then added to the Access-Request that is sent to the service provider's home AAA server.
Use the following procedure to add NAS location attribute information to Access-Request messages.
Location-Specific Configuration Files
The following files and file sections require configuration to add location attributes to the Access-Request. Figure 14 provides an example showing the relationship between all the configuration files.
locspec.ctrl file
[Bootstrap] section
[Settings] section
[NAS-LIST] section
[NAS Identifier] section
proxy.ini file
[Realms] section
realm.pro file
[Auth-Outbound-To-Proxy] section
[Acct-Outbound-To-Proxy] section
locspec.ctrl File
The locspec.ctrl file calls the LOCSPEC control point plug-in, which enables the addition of location-specific information to an Access-Request.
Table 65 defines the fields needed in the [Bootstrap] section for adding location-specific attributes to an Access-Request.
Specifies the name of the control point plug-in file that activates location-specific information. |
Example
[Bootstrap]
LibraryName=locspec.so
Enable=1
Initializationstring=LOCSPEC
Table 66 defines the fields needed in the [Settings] section for adding location-specific attributes to an Access-Request.
Example
[Settings]
AttributetoIdentifyNAS=NAS-Identifier
ConfigLog=ConsoleAndLog
Table 67 defines the fields needed in the [NAS-LIST] section for adding location-specific attributes to an Access-Request.
Example
[NAS-LIST]
NAS_1
NAS_2
For each NAS device listed in the [NAS-LIST] section, there must be a separate section in locspec.ctrl providing location information about the NAS.
Table 68 defines the fields needed in the [NAS Identifier] section that provide location-specific information to an Access-Request. The Access-Request can contain all of these four attributes or a subset.
Example
[NAS_1]
GSM-Operator-Name=REALM:worldnetwork.com
GSM-Location-Name=BostonNeighborsClub
GSM-Visited-Operator-Id=GSM:USACD
GSM-Location-Information=country=US;A1=MA;A3=Boston;ZIP=02116
Figure 13 shows the relationship between the AttributetoIdentifyNAS setting, the NAS-LIST section, and the NAS identifier section of the locspec.ctrl file.
proxy.ini File
The proxy.ini file identifies the .pro files that are used to specify configuration settings. With respect to adding location information to an Access-Accept, the .pro files are needed to invoke the LOCSPEC plug-in.
Table 69 defines the fields needed in the [Realms] section for adding location-specific attributes to an Access-Request.
Lists all the realms that can be included in an Access-Request. For every realm_name, there must be an associated |
Example
[Realms]
Realm_Example_1=nationwide.com
Realm_Example_2=peoplesnetwork.com
realm.pro File
The realm.pro file specifies the control point plug-in that is needed for attaching location-specific information to an Access-Request if the Access-Request is proxied from a foreign AAA server to the home AAA server.
Add the field LOCSPEC to both the [Auth-Outbound-To-Proxy] section and the [Acct-Outbound-To-Proxy] section in the realm.pro file. These sections call the location-specific control plug-in when an Access-Request is proxied (forwarded) to a home AAA server.
Example realm.pro file:
[Auth-Outbound-To-Proxy]
LOCSPEC
[Acct-Outbound-To-Proxy]
LOCSPEC
M
Example Configuration for Adding NAD Location Attributes to Access-Request
Figure 14 shows a sample configuration. The purpose of this example configuration is to add NAD location information to Access-Requests for NAS_1.
Example Overview
In this example, an Access-Request is sent for a mobile device through an example NAS identified by the name NAS_1. The example realm associated with the mobile device is nationwide.com. Three location attributes are assigned to NAS_1 and included in the Access-Request that goes to the nationwide.com service provider. These three attributes are GSM-Location-Name, GSM-Operator-Name, and GSM-Visited-Operator-Id.
Example Configuration
The example configuration lines and syntax (shown in Figure 14) associate all the configuration files together to attach NAS location information to an Access-Request.
The example configuration shows that if the realm is nationwide.com, then the .pro file to be used is Realm_Example_1.pro. The file Realm_Example_1.pro turns on NAS location information feature with the LOCSPEC commands.
