[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]

About Local Profiles

In 3GPP networks, authorization is based on subscriber data provided by the HSS (Home Subscriber Server). The IMS AAA Server can enforce fine-grained policy authorization policy by using Local Profiles.

Local profiles are used in combination with the subscriber profile stored in the HSS to provide additional security for authorization. A Local profile is configured in the IMS AAA Server Administrator by defining ordered lists of attributes and an I-WLAN policy. You can define as many local profiles as you require.

Each profile consists of six configurations, one for each 3GPP WLAN service scenario supported by the IMS AAA Server as shown in Table 22.

Table 22: IMS AAA Server Service Scenarios
3GPP WLAN Service Scenarios
Subscriber/IMS AAA Server Location
Direct IP Access
3GPP IP Access

IMS AAA Server and the subscriber are in the HPLMN

Direct IP

Tunneled IP

IMS AAA Server is in the HPLMN and the subscriber is in some VPLMN

Direct IP (Home)

Tunneled IP (Home)

IMS AAA Server is in the VPLMN and the subscriber is in the HLMN

Direct IP (Visited)

Tunneled IP (Visited)

NOTE: At minimum, each IMS AAA Server in your network needs to be configured with at least one local profile that includes the policy configuration for each 3GPP WLAN service scenario the server needs to support.

One way a mobile operator might use profiles, would be to create a profile for each wireless plan they offer. For example, you might offer a voice only plan, as well as a voice and data plan. A profile could be defined for each plan and customized for the specific requirements of the 3GPP WLAN access scenarios supported in the plan.

[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]