Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

Adding NAS Location Information to Access-Request Messages

Steel-Belted Radius Carrier core provides a special attribute handling feature which allows you to add NAS 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.

Note: The terms network access device (NAD), remote access server (RAS), and network access server (NAS) are interchangeable. This guide primarily uses the term NAS.

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 NAS through which the proxied request was processed. The NAS is geographically near the mobile device. The location of the NAS 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 NAS location based on an attribute (usually NAS-Identifier or NAS-IP-Address). The attribute that is used to look up the NAS location is user-configurable as the AttributeToIdentifyNAS in the locspec.ctrl file.

Figure 9 shows that Steel-Belted Radius Carrier queries the locspec plug-in to find the value of the attribute that identifies the NAS location. The NAS location is then added to the Access-Request that is sent to the service provider’s home AAA server.

Note: Each Steel-Belted Radius Carrier server that might be the target of a proxy request must be set up as a proxy target. Set up proxy targets with the Web GUI. For more information about setting up proxy RADIUS, see the SBR Carrier Administration and Configuration Guide.

Figure 9: Addition of NAS Location to Access-Request

Addition of NAS Location to Access-Request

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 11 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 72 defines the fields needed in the [Bootstrap] section for adding location-specific attributes to an Access-Request.

Table 72: locspec.ctrl [Bootstrap] Fields

Field

Description

LibraryName

Specifies the name of the executable binary.

Set to locspec.so

Enable

Set to 1 to enable this file.

Set to 0 to disable this file.

Set to 1.

InitializationString

Specifies the name of the control point plug-in file that activates location-specific information.

Set to LOCSPEC.

Example

[Bootstrap]
LibraryName=locspec.so
Enable=1
InitializationString=LOCSPEC

Table 73 defines the fields needed in the [Settings] section for adding location-specific attributes to an Access-Request.

Table 73: locspec.ctrl [Settings] Fields

Field

Description

AttributeToIdentifyNAS

Attribute to be used to identify the NAS. Typically, this value is set to one of the following:

NAS-Identifier

NAS-IP-Address

This parameter is reloaded every time that SBRC receives a SIGHUP (1) signal.

ConfigLog

Method for capturing log information.

  • None= Configuration information is not captured.
  • ConsoleAndLog= Log information is sent to both the console and the log.
  • Console= Log information is sent to the console only.
  • Log= Log information is sent to the log file only.

Default is ConsoleAndLog.

OperatorNameAttribute = TeliaSonera-Operator-Name
VisitedOperatorIdAttribute = TeliaSonera-Visited-Operator-ID
LocationInformation = TeliaSonera-Location-Information
LocationNameAttribute = TeliaSonera-Location-Name

Example

Table 74 defines the fields needed in the [NAS-LIST] section for adding location-specific attributes to an Access-Request.

Table 74: locspec.ctrl [NAS-LIST] Fields for Configuration of Location-specific Attributes

Field

Description

NAS designator

List of NAS devices.

The [NAS-List] section includes a list of NAS devices that are configured to transmit their location. The attribute used to identify a NAS in this list is configured in the AttributeToIdentifyNAS field within the [Settings] section of the locspec.ctrl field. Typically, the NAS-Identifier attribute or the NAS-IP-Address attribute is used to identify a NAS.

For example, if AttributeToIdentifyNAS=NAS-IP-Address, then all the NAS devices in this list are identified by their IP Address. If AttributeToIdentifyNAS=NAS-Identifier, then all the NAS devices in this list are identified by their NAS Identifier (name).

This parameter is reloaded every time that SBRC receives a SIGHUP (1) signal.

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 75 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.

Table 75: Location Attributes for the NAS Device

Field

Description

GSM-Operator-Name

GSM-Operator-Name = prefix:value

where

prefix = either GSM or REALM

code =If prefix=GSM, code = any GSMA assigned TADIG code in capital ASCII letters available at http:\\www.gsmworld.org; If prefix=REALM, code = or any valid domain name string

This parameter is reloaded every time that SBRC receives a SIGHUP (1) signal.

GSM-Location-Information

GSM-Location-Information = country= code [; civic-label=value]

where
code = ISO 3166 2-letter country code.
civic-label = A1, A2, A3, A4, A5, A6, PRD, POD, STS, HNO, HNS, LMK, LOC, NAM, ZIP, PCN, or an integer as defined in draft-ietf-geopriv-dhcp-civil-09.txt available at http:\\www.ietf.org.

This parameter is reloaded every time that SBRC receives a SIGHUP (1) signal.

GSM-Visited-Operator-Id

GSM-Visited-Operator-Id = prefix:value

where

prefix = either TADIG or REALM
code =If prefix=GSM, code = any GSMA assigned TADIG code in capital ASCII letters available at http:\\www.gsmworld.org; If prefix=REALM, code = or any valid domain name string

This parameter is reloaded every time that SBRC receives a SIGHUP (1) signal.

GSM-Location-Name

GSM-Location-Name = value

where

value = textual description of the WLAN Hot Spot (human readable string without mandated format).

This parameter is reloaded every time that SBRC receives a SIGHUP (1) signal.

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 10 shows the relationship between the AttributetoIdentifyNAS setting, the [NAS-LIST] section, and the [NAS identifier] section of the locspec.ctrl file.

Figure 10: [Settings], [NAS-LIST], and [NAS identifier] Sections of the locspec.ctrl File

[Settings], [NAS-LIST], and [NAS identifier]
Sections 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 76 defines the fields needed in the [Realms] section for adding location-specific attributes to an Access-Request.

Table 76: proxy.ini [Realms] Fields for Configuration of Location-specific Attributes

Field

Description

realm_name

Lists all the realms that can be included in an Access-Request.

For every realm_name, there must be an associated realm.pro file. For example, if the [Realms] section contains the lines:

[Realms]
CountryNet=countrynet.com

There must be an associated countrynet.profile.

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

Note: The [Auth-Outbound-To-Proxy] section and the [Acct-Outbound-To-Proxy] sections are required in the realm.pro files that are related to adding location information to an Access-Request. However, the realm.pro files require additional sections that are related to the functionality of Steel-Belted Radius Carrier. See the SBR Carrier Administration and Configuration Guide for more information about configuring realm support.

Example Configuration for Adding NAS Location Attributes to Access-Request

Figure 11 shows a sample configuration. The purpose of this example configuration is to add NAS 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 11) 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.

Figure 11: Example Configuration for Adding Location Information to an Access-Request

Example Configuration for Adding Location
Information to an Access-Request

Modified: 2018-01-11