This command configures the APN name to be included in CCR Gx messages.

Product

GGSN

IPSG

P-GW

SAEGW

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

apn-name-to-be-included { gn | virtual }
default apn-name-to-be-included

gn | virtual

Specifies which APN name must be sent in the Gx messages.

gn: Specifies to send the real APN name.

virtual: Specifies to send the virtual APN name if present, else to send the real APN name.

default

Applies the default setting for this command.

Default: gn

Usage Guidelines

This feature is developed to implement a single global APN for the Enterprise services with the ability to have separate virtual APNs per single Enterprise, group of Enterprises sharing the same service group or per department.

To implement this feature, a configurable option is introduced per interface Rf, Gx, Gy and per APN. That is, a service specific CLI "apn-name-to-be-included" is configured for interfaces Rf, Gx, Gy separately. It can take values 'gn' or 'virtual'. Based on the value configured for this command, the Called-Station-Id AVP is populated.

This command is used to configure the APN name to be included in the CCR Gx messages to the PCRF — the real APN name or the virtual APN name.

The name of the virtual APN and the IP pool are signaled during the UE attach to the Enterprise PDN from the 3GPP AAA server over S6b interface with a new vendor-specific AVP "Virtual-APN-Name". The RADIUS Start, Gy CCR to OFCS and Rf ACR to OCS messages contain the Virtual APN name instead of the Enterprise APN.

This feature provides customers the desired granularity per enterprise and per department. This also allows bundling of number of small enterprises under the umbrella of single APN and logically separating them by virtual APN.

This command enables mapping of the ARP priority-level value received from PCRF to inter-user-priority value and be sent in A11 session update.

Product

PDSN

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

arp-priority-level map-to inter-user-priority
{ default | no } arp-priority-level map-to

default

Configures the default setting for this command.

Default: arp-priority-level to inter-user-priority mapping not applicable

no

Disables arp-priority-level to inter-user-priority mapping.

Usage Guidelines

This command associates/disassociates a failure handling templateor a local policy template with the IMS authorization service.

Product

GGSN

HA

HSGW

IPSG

PDSN

P-GW

SAEGW

S-GW

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

associate { failure-handling-template template_name | local-policy-service service_name [ dual-mode ] }
no associate { failure-handling-template | local-policy-service } 

no

Disassociates a failure handling templateor local policy template with the IMS authorization service.

failure-handling-template template_name

Associates a previously created failure handling template with the IMS authorization service. template_name specifies the name for a pre-configured failure handling template. template_name must be an alphanumeric string of 1 through 63 characters.

For more information on failure handling templates, refer to the failure-handling-template command in the Global Configuration Mode Commands chapter.

local-policy-service service_name [ dual-mode ]

Associates a previously created local policy service with the IMS authorization service. service_name specifies the name for a pre-configured local policy service. service_name must be an alphanumeric string of 1 through 63 characters.

dual-mode: This keyword enables both PCRF and local-policy to work together. When this CLI command is enabled, for a few set of events, PCRF will be contacted and for a few local-policy will be contacted.

This keyword is configured to provide load balancing support for PCRF, and failure-handling support when PCRF is down or any failure is detected.

By default, the dual-mode keyword will not enabled and only on PCRF failure the local-policy will be contacted.

For more information on local policy service configuration, refer to the local-policy-service command in the Global Configuration Mode Commands chapter.

Usage Guidelines

Use this command to associate a configured failure handling template or local policy service with the IMS authorization service.

The failure handling template defines the action to be taken when the Diameter application encounters a failure supposing a result-code failure, tx-expiry or response-timeout. The application will take the action given by the template. For more information on failure handling template, refer to the Failure Handling Template Configuration Mode Commands chapter.

If the association is not made to the template then failure handling behavior configured in the application with the failure-handling command will take effect.

To support fallback to local policy in case of failure at PCRF for CCFH continue, the local policy service should be associated with an IMS authorization service. In case of any failures, the local policy template associated with the ims-auth service will be chosen for fallback.

This command configures the value of the Offline AVP sent to the PCRF based on the Charging Characteristics (CC) profile received from the SGSN.

Product

GGSN

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

cc-profile cc_profile_number [ to cc_profile_number_range_end ] map-to offline-avp { 0 | 1 }
{ default | no } cc-profile

default

Configures the default setting for this command.

Default: Deletes all previously configured mappings.

no

Deletes all previously configured mappings.

cc_profile_number

Specifies the CC profile number to map.

For example, 1 for Hot Billing.

cc_profile_number must be an integer from 0 through 15.

cc_profile_number_range_end

Specifies, for a range of CC profile numbers to map, the end number. That is, from cc_profile_number through cc_profile_number_range_end.

cc_profile_number_range_end must be an integer from 1 through 15.

map-to offline-avp { 0 | 1 }

Specifies to map the CC profile number(s) to the Offline AVP value sent to the PCRF.

Usage Guidelines

Use this command to configure the CC Profile to Offline AVP value mapping. The Offline AVP's value (DISABLE_OFFLINE (0), ENABLE_OFFLINE (1)) is derived based on the CC profile received from the SGSN as specified by this mapping.

The following example shows how this command can be configured multiple times:

cc-profile 1 to 2 map-to offline-avp 1
cc-profile 4 map-to offline-avp 0
cc-profile 8 map-to offline-avp 1

On configuring the above set of commands, the Offline AVP value is sent as 1 (Offline enabled) for the CC profiles 1 (Hot Billing), 2 (Flat Rate), and 8 (Post-Paid). And, as 0 (Offline disabled) for the CC profile 4 (Pre-paid).

When configuring this command, overlapping of CC profile numbers is not permitted. In the following example, after configuring the first command, which specifies to send the Offline AVP's value as 1 (Offline enabled) for the CC profiles 1 through 15, the second command, which specifies to map CC profile 7, is not permitted:

cc-profile 1 to 15 map-to offline-avp 1
cc-profile 7 map-to offline-avp 0

This command enables custom reauthorization event triggers.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

custom-reauth-trigger { apn-ambr-mod-failure | default-bearer-qos-change | default-bearer-qos-mod-failure | qos-change | resource-modification-request | ue-ip-addr-allocate | ue-ip-addr-release | none | { preservation-changed | reactivation-changed } + }
default custom-reauth-trigger

default

Configures the default setting for this command. The default setting is to enable all the event triggers.

none

Disables all custom event triggers.

apn-ambr-mod-failure

Enables APN AMBR Modification Failure event trigger.

default-bearer-qos-change

Enables Default EPS bearer QoS change event trigger.

default-bearer-qos-mod-failure

Enables Default EPS Bearer QOS Modification Failure event trigger.

qos-change

Enables QoS change trigger.

resource-modification-request

Enables Resource modification trigger.

ue-ip-addr-allocate

Enables UE IP address allocate trigger.

ue-ip-addr-release

Enables UE IP address release trigger.

preservation-changed

Enables preservation-changed event trigger.

reactivation-changed

Enables reactivation-changed event trigger.

Usage Guidelines

Use this command to enable/disable custom reauth event triggers.

It is recommended that the preservation-changed and reactivation-changed triggers both be enabled. As, when the bearer goes into preservation mode with the preservation-changed trigger, the reactivation-changed trigger must also be enabled for the bearer to get reactivated subsequently.

In 16.0 and later releases, this CLI command overwrites the previously configured triggers with the new event triggers. For example, if the following triggers are configured – QoS change, UE IP address allocation, UE IP address release, preservation-changed, reactivation-changed, then the APN-AMBR modification failure and Resource modification request triggers should be configured. This operation will overwrite all previously configured triggers and will configure only new APN-AMBR modification failure and Resource modification request triggers. By default, these event triggers are enabled.

This command controls PCEF from sending Flow-Description, TFT-Filter, andPacket-Filter-Content AVPs in Rel. 9 format.

Product

GGSN

P-GW

SAEGW

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

[ no ] diameter 3gpp-r9-flow-direction

3gpp-r9-flow-direction

Encodes Flow-Direction, Flow-Description, TFT-Filter, and Packet-Filter-Content AVPs based on 3GPP Rel. 9 specification.

no

Encodes Flow-Direction, Flow-Description, TFT-Filter, and Packet-Filter-Content AVPs in Rel. 8 format. This is the default configuration.

Usage Guidelines

Use this command to enable Rel.9 changes for Flow-Description, TFT-Filter, and Packet-Filter-Content AVPs sent by PCEF in CCR-U. This CLI command works in conjunction with diameter update-dictionary-avps { 3gpp-r9 | 3gpp-r10 }. When diameter 3gpp-r9-flow-direction is configured and negotiated supported feature is 3gpp-r9 or above, PCEF will send Flow-Description, TFT-Filter, and Packet-Filter-Content AVPs in 3GPP Rel. 9 format.

Per the 3GPP Rel. 8 standards, the IPFilterRule in Flow-Description, TFT-Filter, and Packet-Filter-Content AVPs is sent as "permit in" for UPLINK and "permit out" for DOWNLINK direction. From 3GPP Rel. 9 onwards, the Flow-Description AVP within the Flow-Information AVP will have only "permit out" and the traffic flow direction is indicated through Flow-Direction AVP. In 3GPP Rel. 9 format, both UPLINK and DOWNLINK are always sent as "permit out" and hence the usage of "permit in" is deprecated.

Backward compatibility is maintained, i.e. both Rel. 8 (permit in/out) and Rel. 9 (permit out with flow-direction) formats are accepted by PCEF.

This CLI command must be used only after the PCRF is upgraded to Rel. 9. For more information on this feature, see the 3GPP Rel.9 Compliance for IPFilterRule section in the Gx Interface Support chapter in the administration guide for the product you are deploying.

This command specifies the Diameter Policy Control Application dictionary to be used by the IMS Authorization Service for the policy control application.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

diameter dictionary { Standard | dpca-custom1 | dpca-custom10 | dpca-custom11 | dpca-custom12 | dpca-custom13 | dpca-custom14 | dpca-custom15 | dpca-custom16 | dpca-custom17 | dpca-custom18 | dpca-custom19 | dpca-custom2 | dpca-custom20 | dpca-custom21 | dpca-custom22 | dpca-custom23 | dpca-custom24 | dpca-custom25 | dpca-custom26 | dpca-custom27 | dpca-custom28 | dpca-custom29 | dpca-custom3 | dpca-custom30 | dpca-custom4 | dpca-custom5 | dpca-custom6 | dpca-custom7 | dpca-custom8 | dpca-custom9 | dynamic-load | gx-wimax-standard | gxa-3gpp2-standard | gxc-standard | pdsn-ty | r8-gx-standard | std-pdsn-ty | ty-plus | ty-standard }
default diameter dictionary

dpca-custom1

Custom-defined Diameter dictionary for the Gx interface.

dpca-custom2

Custom-defined Diameter dictionary for Rel. 7 Gx interface.

dpca-custom3

Custom-defined Diameter dictionary for the Gx interface in conjunction with IP Services Gateway (IPSG).

dpca-custom4

Standard Diameter dictionary for 3GPP Rel. 7 Gx interface.

dpca-custom5

Custom-defined Diameter dictionary for Rel. 7 Gx interface.

dpca-custom6 ... dpca-custom30

Custom-defined Diameter dictionaries.

dynamic-load

Configures the dynamically loaded Diameter dictionary. The dictionary name must be an alphanumeric string of 1 through 15 characters.

For more information on dynamic loading of Diameter dictionaries, see the diameter dynamic-dictionary in the Global Configuration Mode Commands chapter of this guide.

gx-wimax-standard

Gx WiMAX standard dictionary.

gxa-3gpp2-standard

Gxa 3GPP2 standard dictionary.

gxc-standard

Gxc standard dictionary.

pdsn-ty

This keyword is restricted.

r8-gx-standard

R8 Gx standard dictionary.

Standard

Standard Diameter dictionary for the 3GPP Rel. 6 Gx interface.

Default: Enabled for Gx support in 3GPP networks.

std-pdsn-ty

This keyword is restricted.

ty-plus

This keyword is restricted.

ty-standard

This keyword is restricted.

default

Sets the default Diameter dictionary.

Default: Standard

Usage Guidelines

Use this command to specify the Diameter dictionary for IMS Authorization Service.

This command enables encoding of all the event-related information AVPs in CCR-U messages.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

[ default ] diameter encode-event-avps { always | local-fallback }

default

Applies the default setting for this command.

Default: Sends AVPs relevant to the Event-Trigger subscribed by the PCRF.

always

This keyword option always sends the event-related AVPs in all CCR messages.

local-fallback

This keyword option sends the event-related AVPs in CCR-U messages in the event of local fallback scenario.

Usage Guidelines

Use this command to facilitate sending of all the event-related information AVPs in CCR-U messages.

In releases prior to 14.0, per the 3GPP standards for Gx, AVPs relevant to the Event-Trigger subscribed by the PCRF were always sent in the CCR messages. This release onwards, sending of event-related AVPs for all update (both access side and internal) and terminate requests is CLI controlled.

Note that the QoS-Info AVP will be encoded in all CCR-U messages if the CLI command "diameter encode-event-avps always" is enabled. This implementation impacts only the dpca-custom15 dictionary.

This command enables/disables encoding and sending of Supported-Features AVP.

Product

GGSN

P-GW

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

diameter encode-supported-features { adc-rules | netloc | netloc-ran-nas-cause | pending-transactions | session-recovery | session-sync | sgw-restoration | sponsored-connectivity | virtual-apn }
{ default | no } diameter encode-supported-features

adc-rules

This keyword enables configuration of Application Detection and Control (ADC) rules over Gx interface. For ADC 6th bit of supported feature will be set. By default, this supported feature will be disabled.

This keyword "adc-rules" will be available only when the feature-specific license is configured.

In release 18, the gateway node will use ADC functionality over Gx as defined in the Release 11 specification of 3GPP standard. ADC extension over Gx provides the functionality to notify PCRF about the start and stop of a specific protocol or a group of protocols, and provide the possibility to PCRF that with the knowledge of this information, change the QoS of the user when the usage of application is started and until it is finished.

The provision of ADC information is done through the ADC rule, the action initiated by PCRF is done through the PCC rule.

ADC rules are certain extensions to dynamic and predefined PCC rules in order to support specification, detection and reporting of an application flow. These rules are installed (modified/removed) by PCRF via CCA-I/CCA-U/RAR events. ADC rules can be either dynamic PCC or predefined PCC rules, and the existing attributes of dynamic and predefined rules will be applicable.

Dynamic PCC rule contains either traffic flow filters or Application ID. When Application ID is present, the rule is treated as ADC rule. Application ID is the name of the ruledef which is pre-defined in the boxer configuration. This ruledef contains application filters that define the application supported by P2P protocols.

PCEF will process and install ADC rules that are received from PCRF interface, and will detect the specified applications and report detection of application traffic to the PCRF. PCRF in turn controls the reporting of application traffic.

PCEF monitors the specified applications that are enabled by PCRF and generates Start/Stop events along with the Application ID. Such application detection is performed independent of the bearer on which the ADC PCC rule is bound to. For instance, if ADC rule is installed on a dedicated bearer whereas the ADC traffic is received on default bearer, application detection unit still reports the start event to PCRF.

netloc

Enables the NetLoc feature. The NetLoc feature indicates the support for reporting of the Access Network Information.

A new feature "netloc" (feature bit 10) has been added as part of the Supported-Features AVP to implement the Network provided Location Info (NPLI) feature for IMS. NPLI is used to support variety of applications like emergency call, Lawful intercept, charging, etc.

The netloc feature bit will be sent to PCRF on demand via CCR-I message. A new event trigger "ACCESS_NETWORK_INFO_REPORT (45)" and a new Diameter AVP "Required-Access-Info" have been added to support the NPLI enhancement.

The gateway node provides the required access network information (e.g. user location and/or user time zone information) to the PCRF within the 3GPP-User-Location-Info AVP, User-Location-Info-Time AVP (if available), and/or 3GPP-MS-TimeZone AVP as requested by the PCRF. The gateway also provides the ACCESS_NETWORK_INFO_REPORT event trigger within Event-Trigger AVP.

netloc-ran-nas-cause

Enables the Netloc-RAN-NAS-Cause feature. By default, this supported feature will be disabled.

This feature is used to send detailed RAN and/or NAS release cause code information from the access network to PCRF. This feature is added to be in compliance with Release 12 specification of 3GPP TS 29.212. It requires that the NetLoc feature is also supported.

A new feature "netloc-ran-nas-cause" (feature bit 22) has been added as part of the Supported-Features AVP to support the 3GPP RAN/NAS Release Cause Code Information Element (IE) on Gx interface.

If the supported features "netloc-ran-nas-code" and "netloc" are enabled, then netloc-ran-nas-cause code will be sent to PCRF via CCR-T message. A new Diameter AVP "RAN-NAS-Release-Cause" has been added to support this feature. This AVP will be included in the Charging-Rule-Report AVP and in CCR-T for bearer and session deletion events respectively.

pending-transactions

Configures the Pending Transactions feature as part of supported features. This keyword addition is to handle race conditions on Gx i.e. process the Diameter messages in the order they are received.

Gx-based applications are vulnerable to certain race conditions (e.g. concurrent RAR/CCR). Enhancements are done on the Diameter protocol to deterministically handle the race conditions on Gx.

In a scenario wherein RAR is received while waiting for CCA-U, Gx application rejects RAR with Experimental-Result-Code AVP set to DIAMETER_PENDING_TRANSACTION. This should be done only if PCRF supports this functionality otherwise Gx client should continue with the current implementation.

If race conditions are not processed properly, it can lead to unpredictable behavior from each node, resulting in subscriber disconnection. With this feature, the outcome in such situation is deterministic and operator has the ability to influence the node behavior aligned with their policy.

session-recovery

Enables the Session Recovery feature. This functionality helps ensure that the PCRF and P-GW can be in sync on session information and recover any lost Gx sessions. By default, session recovery and session sync features are not enabled.

Gx sessions typically tend to be long-lived. In case of session loss in PCRF (e.g. due to software failure), or a message loss in PCRF (e.g. Gx:RAA is dropped due to overload control), there is no existing mechanism to allow the PCRF and P-GW to sync-up on session state like Rules Status, APN-AMBR, QoS, Event Triggers, etc. In this release, the Gx interface between P-GW and PCRF has been enhanced to allow the PCRF and P-GW to sync-up. This is currently not part of 3GPP 29.212.

This keyword is used to achieve the session recovery. When this feature is enabled, P-GW and PCRF will exchange session information and P-GW provides the complete subscriber session information to enable PCRF to build the session state.

session-sync

Enables the Session Synchronization feature. This functionality helps ensure that the PCRF and P-GW can be in sync on session information and recover any lost Gx sessions. By default, Session Recovery and Session Sync features will not be enabled.

Gx sessions typically tend to be long-lived. In case of session loss in PCRF (e.g. due to software failure), or a message loss in PCRF (e.g. Gx:RAA is dropped due to overload control), there is no existing mechanism to allow the PCRF and P-GW to sync-up on session state like Rules Status, APN-AMBR, QoS, Event Triggers, etc. The Gx interface between P-GW and PCRF is enhanced to allow the PCRF and P-GW to sync-up. This is currently not part of 3GPP 29.212.

This keyword is used to achieve the session sync-up. When this feature is enabled, P-GW and PCRF will exchange session information and P-GW provides the complete subscriber session information to enable PCRF to build the session state.

sgw-restoration

This keyword enables configuration of S-GW Restoration feature.

P-GW is configured to support S-GW Restoration feature. P-GW sends S-GW Restoration feature in Supported-Features AVP through the CCR-I message during session creation. If P-GW receives S-GW Restoration feature in Supported-Features AVP in CCA-I message, then P-GW enables S-GW Restoration feature.

If P-GW and PCRF support S-GW Restoration feature, then the P-GW accepts CCA and RAR during S-GW restoration. Only Rule removal or RAR with session release cause is processed. Any rule install or modify is dropped. P-GW triggers CCR-U with PCC rule failure report and AN_GW_STATUS AVP to inform PCRF that S-GW is down. After receiving the SGW_Restoration indication, PCRF does not initiate any rule install or modification towards the P-GW. The P-GW informs the PCRF when the S-GW has recovered using the Event-Trigger AVP set to AN_GW_CHANGE and including the AN-GW-Address AVP related to the restored or new S-GW. If S-GW restoration is reported to PCRF, then the P-GW sends CCR-U with AN_GW_CHANGE trigger.

If S-GW Restoration feature is not negotiated through the Supported-Features AVP, then P-GW falls back to the old behavior as follows:

After configuring the S-GW Restoration feature on Gx interface, the failure is sent to PCRF with Rule-Failure-Code as AN_GW_FAILED in both failure and restoration scenarios.

sponsored-connectivity

Enables the Sponsored (data) Connectivity feature.

With sponsored data connectivity, the sponsor has a business relationship with the operator and the sponsor reimburses the operator for the user's data connectivity in order to allow the user access to an associated Application Service Provider's (ASP) services. Alternatively, the user pays for the connectivity with a transaction which is separate from the subscriber's charging. It is assumed the user already has a subscription with the operator.

The purpose of this feature is to identify the data consumption for a certain set of flows differently and charge it to sponsor. To support this, a new reporting level "SPONSORED_CONNECTIVITY_LEVEL" is added for reporting at Sponsor Connection level and two new AVPs "Sponsor-Identity" and "Application-Service-Provider-Identity" have been introduced at the rule level.

This CLI command "diameter encode-supported-features" has been added in Policy Control Configuration mode to send Supported-Features AVP with Sponsor Identity.

Sponsored Connectivity feature will be supported only when both P-GW and PCRF support 3GPP Rel. 10. P-GW advertises release as a part of supported features in CCR-I to PCRF. If P-GW supports Release 10 and also Sponsored Connectivity but PCRF does not support it (as a part of supported features in CCA-I), this feature is turned off.

This feature implementation impacts only the Gx dictionary "dpca-custom15".

virtual-apn

This keyword enables configuration of Gx-based Virtual APN (VAPN) feature. For VAPN 4th bit of supported feature will be set. By default, this supported feature will be disabled.

This keyword "virtual-apn" will be available only when the feature-specific license is configured.

In releases prior to 19, VAPN selection was possible through RADIUS or local configuration. In Release 19, ASR5K uses PCRF and Gx interface for Virtual APN selection to achieve signaling reduction.

This keyword enables Gx based Virtual APN Selection feature for a given IMS authorization service. When this configuration is enabled at P-GW/GGSN, then P-GW/GGSN advertises this feature to PCRF through the Supported-Features AVP in CCR-I. When the VAPN is selected, then the PCRF rejects the CCR-I message with the Experimental-Result-Code AVP set to 5999 (DIAMETER_GX_APN_CHANGE), and sends a new APN through the Called-Station-Id AVP in CCA-I message. The existing call is then disconnected and established with the new virtual APN. Note that the Experimental Result Code 5999 will have the Cisco Vendor ID.

Limitations:

default | no

This keyword removes the previously configured supported features.

Usage Guidelines

This command is used to enable encoding and sending of Supported-Features AVP.

This command controls pacing of the reselection or switching of the PCRF after a change occurs in the table configuration for an IMS Authorization Service.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

diameter host-select reselect subscriber-limit subs_limit time-interval duration
{ default | no } diameter host-select reselect

subscriber-limit subs_limit

Specifies the limit of subscribers to switch or reselect the PCRF for subscribers not more than subs_limit in time duration of duration second(s).

subs_limit must be an integer from 1 through 10000000.

time-interval duration

Specifies the time duration, in seconds, to reselect PCRF for subscribers not more than subs_limit in time duration of duration second(s).

duration must be an integer from 1 through 3600.

default

Applies the default setting for this command.

Sets the PCRF reselection or switching to default state.

no

Removes the configured PCRF reselection method and disables the reselection or switching of PCRF.

Usage Guidelines

Use this command to specify the pacing of reselection or switching of the PCRF in an IMS authorization service..

In case IMS authorization session have been opened on certain PCRF on the basis of the current selection table, and the current active table configuration is changed, the IMSA starts selection procedure for the PCRF. Existing sessions on current PCRF from earlier table is required to close and reopened on the selected PCRF from the new table. This reselection periodicity is controlled by this command and it indicates the number of subscriber sessions subs_limit to be reselected or moved in duration seconds.

For example, if this command is configured with 100 subscribers and 2 seconds, then the system reselects the PCRF for no more than 100 subscribers per 2 seconds.

This command adds/appends rows with precedence to a Diameter host table or MSISDN prefix range table.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

diameter host-select row-precedence precedence_value table { { { 1 | 2 } host host_name [ realm realm_id ] [ secondary host host_name [ realm realm_id ] ] } | { prefix-table { 1 | 2 } msisdn-prefix-from msisdn_prefix_from msisdn-prefix-to msisdn_prefix_to host host_name [ realm realm_id ] [ secondary host sec_host_name [ realm sec_realm_id ] algorithm { active-standby | round-robin } ] } } [ -noconfirm ]
no diameter host-select row-precedence precedence_value table { { 1 | 2 } | prefix-table { 1 | 2 } }

diameter host-select row-precedence precedence_value table { 1 | 2 } host host_name [ realm realm_id ] [ secondary host sec_host_name [ realm sec_realm_id ] ]

This command adds/appends a row in the specified Diameter host table.

In 8.0, a maximum of 16 rows can be added to a table. In 8.1 and later releases, a maximum of 128 rows can be added per table.

row-precedence precedence_value: Specifies precedence of the row in the Diameter host table.

table { 1 | 2 }: Specifies the Diameter host table to add/append the primary and secondary Diameter host addresses.

host host_name: Specifies the primary host name. host_name must be an alphanumeric string of 1 through 127 characters in length.

realm realm_id: Specifies the primary realm ID. realm_id must be an alphanumeric string of 1 through 127 characters in length.

secondary host sec_host_name [ realm sec_realm_id ]: Specifies the secondary host name and realm ID:

host sec_host_name: Specifies the secondary host name. host_name must be an alphanumeric string of 1 through 127 characters in length.

realm sec_realm_id: Specifies the secondary realm ID. realm_name must be an alphanumeric string of 1 through 127 characters in length.

no diameter host-select row-precedence precedence_value table prefix-table { 1 | 2 } }

Removes the row with the specified precedence from the specified MSISDN prefix range table.

diameter host-select row-precedence precedence_value table prefix-table { 1 | 2 } msisdn-prefix-from msisdn_prefix_from msisdn-prefix-to msisdn_prefix_to host host_name [ realm realm_id ] [ secondary host sec_host_name [ realm sec_realm_id ] algorithm { active-standby | round-robin } ] [ -noconfirm ]

Use this command to configure the MSISDN prefix range based PCRF selection mechanism for Rel. 7 Gx interface support, wherein the PCEF is required to discover and select an appropriate PCRF to establish control relationship at primary PDP context activation.

This command adds a row in the specified MSISDN prefix range table. A maximum of 128 rows can be added per prefix range table.

row-precedence precedence_value: Specifies precedence of the row in the table.

prefix-table { 1 | 2 }: Specifies the MSISDN prefix range table to add the primary and/or secondary Diameter host addresses.

msisdn-prefix-from msisdn_prefix_from: For a range of MSISDNs, specifies the starting MSISDN.

msisdn-prefix-to msisdn_prefix_to: For a range of MSISDNs, specifies the ending MSISDN.

host host_name: Specifies the primary host name. host_name must be an alphanumeric string of 1 through 127 characters in length.

realm realm_id: Specifies the primary realm ID. realm_id must be an alphanumeric string of 1 through 127 characters in length.

secondary host sec_host_name [ realm sec_realm_id ]: Specifies the secondary host name and realm ID: host sec_host_name: Specifies the secondary host name. sec_host_name must be an alphanumeric string of 1 through 127 characters in length.

realm sec_realm_id: Specifies the secondary realm ID. sec_realm_id must be an alphanumeric string of 1 through 127 characters in length.

algorithm { active-standby | round-robin }: Specifies the algorithm for selection between primary and secondary servers in the MSISDN prefix range table.

Default: active-standby

active-standby: Specifies selection of servers in the Active-Standby fashion.

round-robin: Specifies selection of servers in the Round-Robin fashion.

[-noconfirm]

Specifies that the command is to execute without any additional prompt and confirmation from the user.

no diameter host-select row-precedence precedence_value table { 1 | 2 }

Removes the row with the specified precedence from the specified Diameter host table.

Usage Guidelines

Use this command to add, update, or delete rows specified with a precedence from a Diameter host table or MSISDN prefix range table.

In the Rel. 7 Gx implementation, when the Gateway interworks with multiple PCRFs, the Gateway can configure the primary and secondary server based on the MSISDN-prefix range in the MSISDN prefix range table. Using this command, you can add a new prefix row into the MSISDN prefix table.

If a row with the precedence that you add already exists in a table, the existing prefix row is removed and the new row is inserted with the same precedence.

This command selects the Diameter host table or the MSISDN prefix range table, and the algorithm to select rows from the Diameter host table.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

diameter host-select table { { 1 | 2 } algorithm { ip-address-modulus [ prefer-ipv4 | prefer-ipv6 ] | msisdn-modulus | round-robin } | prefix-table { 1 | 2 } }
{ default | no } diameter host-select table

diameter host-select table { 1 | 2 } algorithm { ip-address-modulus | msisdn-modulus | round-robin }

table { 1 | 2 }: Specifies the Diameter host table to obtain the primary and secondary host names for PCRF.

algorithm { ip-address-modulus [ prefer-ipv4 | prefer-ipv6 ] | msisdn-modulus | round-robin }: Specifies the algorithm to select row from the Diameter host table.

diameter host-select table prefix-table { 1 | 2 }

Specifies the MSISDN Prefix Range table to be used in case of MSISDN prefix range based PCRF discovery mechanism.

default

Applies the default setting for this command.

no

Removes previous configuration.

When no table is selected, the system will not communicate with any PCRF for new sessions.

Usage Guidelines

Use this command to configure the Diameter host table and row selection methods to select host name or realm for PCRF.

When this command is used to change which table the system should be using, user must re-determine which E-PDF the system should be using for each subscriber. If a different E-PDF results from the configuration change in the table, the system will wait for all of the IMS sessions for the subscriber to be no longer active and then the system either closes/opens Gx sessions with the old/new PDFs respectively, or the system deactivates the PDP contexts of the subscriber.

Here is an example of how row selection is configured for three hosts that the system will use for load-balancing. Operator can configure six rows in a table, as follows.

In the above table, the three hosts are named 1, 2, and 3. When all hosts are working, the load will be distributed among all the three hosts. If host 1 fails, then the load will be distributed between the remaining two hosts. In this scenario, the modulo 6 results of 2 and 4 will return rows that have primary hosts but no working back-up host.

In the Rel. 7 Gx implementation, the GGSN/PCEF is required to discover and select an appropriate PCRF to establish control relationship at primary PDP context activation. The ip-address-modulus, msisdn-modulus, and round-robin algorithms are supported by the GGSN/PCEF for PCRF discovery. In addition, the active/standby and round-robin algorithms are used for selection between primary and secondary servers based on the MSISDN Prefix Range Table.

This command specifies the Diameter host server template to be associated with this IMS Authorization service. The service uses the specified template (and associated host-select table) to select a Diameter peer server. It then uses the returned host name(s) to contact the PCRF and establish the call.

Product

GGSN

HA

HSGW

IPSG

PDSN

P-GW

SAEGW

S-GW

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

diameter host-select-template tmplt_name
no diameter host-select-template

no

Removes the binding of the Diameter host select template with the IMS Authorization service.

tmplt_name

Specifies the name of an existing Diameter host server template (configured in Global Configuration mode) to bind with the IMS Authorization service. It is an alphanumeric string of 1 through 255 characters.

Usage Guidelines

Use this command to bind a configured Diameter host select template to the IMS Authorization service for DPCA. This IMS authorization service searches the associated host select table to select a Diameter peer server. For additional information refer to the Diameter Host Select Configuration Mode Commands chapter and the description of the diameter-host-template command in the Global Configuration Mode Commands chapter.

This command enables selecting the value to which the USAGE_REPORT and APN_AMBR_MOD_FAILURE Event-Trigger should be mapped to.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

diameter map usage-report { 29 | [ 26 | 33 ] [ 26 | 33 ] }
default diameter map usage-report

usage-report { 29 | [ 26 | 33 ] [ 26 | 33 ] }

Maps the USAGE_REPORT of Event-Trigger AVP to one or a combination of these values.

default

The default behavior is to configure the Event-Trigger USAGE_REPORT to be mapped to 26.

Usage Guidelines

The Event-Trigger AVP's USAGE_REPORT has been given different values in the 3GPP TS 29.212 standard spec. As a result of that, the releases of TS 29.212 are not backward compatible. To address this, this CLI command has been introduced in Policy Control configuration mode to map the USAGE_REPORT to either 26/29/33 or a combination of these values in order to be flexible enough to interoperate with various operators.

If this CLI command diameter map usage-report 29 is configured in the chassis and PCRF sends 29 event-trigger then on volume threshold breach CCR-U with volume-report and event-trigger 29 will be sent to the PCRF. Same is the case with the values 26 and 33.

In 17.1 and later releases, to be able to gracefully handle the change when moving between 3GPP releases supporting the different values for the Usage Report, the existing CLI command diameter map usage-report is modified to support configuration of multiple values of usage report mapping. While migrating from older versions to current version, all of the sessions created before the migration will continue to use 26 as usage report event trigger value. The new session will use usage-report value based on PCRF value or default value.

In releases prior to 17.1, when diameter map usage-report is mapped to 26, then APN AMBR modification failure event trigger is not supported. In 17.1 and later releases, APN AMBR modification failure event trigger is supported for all usage report trigger values (26, 33, 29).

This command binds the origin endpoint configured in Context Configuration mode to the IMS Authorization service for Diameter Policy Control Application (DPCA).

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

diameter origin endpoint endpoint_name
no diameter origin

endpoint endpoint_name

endpoint_name is the Diameter endpoint configured in Context Configuration Mode to bind with IMS authorization service, and must be an alpha/numeric string of 1 through 63 characters in length.

no

Removes the binding of Diameter origin endpoint with IMS Authorization service.

Usage Guidelines

Use this command to bind a configured Diameter origin endpoint to the IMS Authorization service for DPCA. This IMS authorization service searches all system contexts until it finds one with a matching Diameter origin endpoint name specified.

This command configures the request-timeout setting for Diameter-IMSA Gx interface.

Product

GGSN

P-GW

SAEGW

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

diameter request-timeout timeoutdeciseconds msg-type { any | ccr-initial | ccr-terminate | ccr-update }
default diameter request-timeout

timeout

Specifies the timeout duration (in deciseconds). The value must be an integer from 1 through 3000.

Default: 10 seconds

deciseconds msg-type { any | ccr-initial | ccr-terminate | ccr-update }

Specifies independent timers (in deciseconds) for all message types like CCR-I, CCR-U and CCR-T. The default time will be 100 deciseconds (10 seconds).

This keyword option provides additional flexibility for operator to configure independent timers with reduced granularity.

This feature implementation ensures that the timer configuration is backward compatible. If the CLI command is configured without "desiseconds" and "msg-type", the configured time will be taken as seconds and while displaying the CLI it will be converted to deciseconds and msg-type will be "any".

default

Applies the default setting for this command.

Usage Guidelines

Use this command to configure the request-timeout setting for Diameter-IMSA Gx interface. At the request-timeout value, DPCA will apply failure-handling to the subscriber. Action will be taken based on the failure-handling configuration (terminate/retry-terminate/continue).

This command enables reporting of SGSN_CHANGE event trigger and SGSN-Address AVP for 2G and 3G calls on GnGp P-GW.

Product

GGSN

P-GW

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

diameter sgsn-change-reporting
no diameter sgsn-change-reporting

sgsn-change-reporting

This keyword specifies to detect SGSN change and send SGSN-Address AVP and SGSN_CHANGE event trigger for a subscriber in 2G/3G on Gx interface during GnGp scenario.

no

This variant specifies to send AN-GW-Address AVP during the call setup, when SGSN change happens, or during the handoff from 4G to 3G. This is the default setting.

Usage Guidelines

The current implementation does not send SGSN_CHANGE event trigger and SGSN- Address AVP. Instead it sends AN-GW-Address AVP and AN_GW_CHANGE event trigger for GnGp case. This behavior is not compliant to 3GPP standard TS 29.212 specification. Hence, in release 18, this CLI command "diameter sgsn-change-reporting" has been introduced to control this behavior.

This release provides, the GnGp P-GW users, the flexibility to configure detection of SGSN_CHANGE event trigger and to send SGSN-Address AVP for a subscriber in 2G/3G on Gx interface, so that PCRF can use this information to apply appropriate policies.

In releases prior to 18, AN-GW-Address AVP was sent in CCR-I message on GnGp scenario. AN_GW_CHANGE event trigger and AN-GW-Address AVP were sent when the inter-sgsn handoff or 4G to 2G/3G GnGp handoff happens.

When this CLI command is configured, SGSN-Address AVP will be sent in the CCR-I message for 2G/3G GnGp P-GW subscribers. SGSN_CHANGE event trigger and SGSN-Address AVP will be sent when the inter-sgsn handoff or 4G to 2G/3G GnGp handoff happens.

By default, AN-GW-Address AVP will be sent during the call setup, when SGSN change happens, or during the handoff from 4G to 3G.

This command enables dictionary control of the AVPs that need to be added based on the version of the specification to which the PCEF is compliant with.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

diameter update-dictionary avps { 3gpp-r8 | 3gpp-r9 | 3gpp-r10 }
{ default | no } diameter update-dictionary avps

default | no

Configures this command with the default setting.

The default behavior is that R9 support will not be indicated as part of Supported-Features AVP in a R7/R8 dictionary and R8 support will not be indicated as part of Supported-Features AVP in a R7 dictionary.

3gpp-r8

Specifies to select the 3GPP Rel. 8 AVPs for encoding.

3gpp-r9

Specifies to select the 3GPP Rel. 9 AVPs for encoding.

3gpp-r10

Specifies to select the 3GPP Rel. 10 AVPs for encoding.

Usage Guidelines

Use this command to encode the AVPs in the dictionary based on the release version of the specification to which the PCEF is compliant with.

Release 12.0 onwards, if a 3GPP Rel. 7 based dictionary is already configured with diameter dictionary dpca-custom4 command, and then if the diameter update-dictionary-avps 3gpp-r9 command is applied, the Supported-Features AVP with feature bit 1 being set will be sent in the CCR-I to indicate that 3GPP Rel. 9 AVPs are also supported.

Both default and no command have the same behavior, as if the CLI command is not configured. Hence, in the output of show configuration verbose command, the default and no command is shown as no diameter update-dictionary-avps.

This CLI command when configured results in behavioral changes as indicated in the following table.

In 14.1 and later releases, Supported-Features AVP is extended to support 3GPP Rel. 10 in EPS 3.0 in addition to 3GPP Rel. 8 and Rel. 9. If the diameter update-dictionary-avps 3gpp-r10 command is applied, the Supported-Features AVP with feature bit 1 being set will be sent in the CCR-I / CCA to indicate that 3GPP Rel. 10 AVPs are also supported. The 'M' bit setting for the Feature-List AVP and Feature-List-ID AVP must be the same as defined in 3GPP TS 29.229 and must not be affected by the 'M' bit setting of the Supported-Features AVP.

Exits the current configuration mode and returns to the Exec mode.

Product

All

Privilege

Security Administrator, Administrator

Syntax

Syntax Description

end

Usage Guidelines

Use this command to return to the Exec mode.

This command enables Diabase to select the Diameter peers in all failure scenarios.

Product

GGSN

PGW

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

endpoint-peer-select [ on-host-select-failure | on-inactive-host ]
{ default | no } endpoint-peer-select

on-host-select-failure

Specifies to perform server selection at Diabase when the hosts could not be selected by IMS Authorization application.

on-inactive-host

Specifies to perform server selection at diabase when the hosts selected by application are inactive.

default | no

Default/no behavior is to terminate the call when the hosts could not be selected by application or when the hosts selected by application are inactive.

Usage Guidelines

Use this command to perform server selection at Diabase when the hosts could not be selected by application or when the hosts selected by the IMS Authorization application is inactive. For example, host table is not configured in IMSA service, host table is configured but not activated, none of the rows in prefix table match the subscriber, host template is not associated with IMSA service, host template could not select the hosts.

This CLI command is added in policy control configuration mode to maintain backward compatibility with the old behavior of terminating the call when server selection fails at application.

This command enables event report indication.

Product

P-GW

SAEGW

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

event-report-indication { all | pgw-trace-control | qos-change | rai-change | rat-change | sgsn-change | ue-timezone-change | user-loc-change } [ pgw-trace-control ] [ qos-change ] [ rai-change ] [ rat-change ] [ sgsn-change ] [ ue-timezone-change ] [ user-loc-change ]
{ default | no } event-report-indication

all | pgw-trace-control | qos-change | rai-change | rat-change | sgsn-change | ue-timezone-change | user-loc-change

default | no

Disables event report indication.

Usage Guidelines

Use this command to determine what type of event changes are reported from the PCRF.

This command configures sending usage monitoring information in event updates either for all event triggers or for a specific event trigger.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

event-update send-usage-report [ reset-usage ] [ events { an-gw-change | apn-ambr-mod-failure | bearer-loss | bearer-rcvry | charging-correlation-exchange | default-bearer-qos-change | default-bearer-qos-mod-failure | ip-can-change | out-of-credit | pgw-trace-control | plmn-change | qos-change | qos-excess-change | rai-change | rat-change | reallocation-of-credit | resource-modification-request | revalidation-timeout | sgsn-change | successful-resource-alloc | tft-change | ue-ip-addr-allocate | ue-ip-addr-release | ue-timezone-change| user-loc-change }+ ]
{ default | no } event-update

default

Configures the default setting for this command.

Default: Usage report is not sent in event update.

no

Disables sending usage report in event update.

reset-usage

Resets the usage at PCEF after reporting in event update.

events { an-gw-change | apn-ambr-mod-failure | bearer-loss | bearer-rcvry | charging-correlation-exchange | default-bearer-qos-change | default-bearer-qos-mod-failure | | ip-can-change | out-of-credit | pgw-trace-control | plmn-change | qos-change | qos-excess-change | rai-change | rat-change | reallocation-of-credit | resource-modification-request | revalidation-timeout | sgsn-change | successful-resource-alloc | tft-change | ue-ip-addr-allocate | ue-ip-addr-release | ue-timezone-change| user-loc-change }+

Usage Guidelines

Use this command to send volume usage information when an event change is reported to the PCRF in a CCR-U message.

To send customized usage information based on specific event triggers, the event should be accordingly configured with the event-update send-usage-report events command. For example, if the usage report is required whenever RAT change occurs, this can be accomplished using the event-update send-usage-report events rat-change command.

Exits the current mode and returns to the parent configuration mode.

Product

All

Privilege

Security Administrator, Administrator

Syntax

Syntax Description

exit

Usage Guidelines

Use this command to return to the parent configuration mode.

This command configures Diameter failure handling behavior.

Product

All

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

In Release 8.0:

failure-handling { continue | retry-and-terminate | terminate | diameter-result-code { any-error | result_code } ccfh { continue | retry-and-terminate | terminate } [ cc-request-type { initial-request | terminate-request | update-request } ] }
no failure-handling diameter-result-code { any-error | integer result_code } [ cc-request-type { initial-request | terminate-request | update-request } ]

In 8.1 and later releases:

failure-handling cc-request-type { any-request | initial-request | terminate-request | update-request } { diameter-result-code { any-error | result_code [ to end_result_code ] } } { continue [ retry-server-on-event | send-ccrt-on-call-termination ] | retry-and-terminate | terminate }
no failure-handling cc-request-type { any-request | initial-request | terminate-request | update-request } [ diameter-result-code { any-error | result_code [ to end_result_code] } ] [ continue { send-ccrt-on-call-termination } ]

no

Disables previous failure-handling configuration.

retry-and-terminate

Specifies that in the event of a failure the user session continues for the duration of one retry attempt with the server. If this retry attempt also fails, the session is terminated.

terminate

Specifies that in the event of a failure the user session be terminated.

diameter-result-code { any-error | result_code [ to end_result_code ] }

Specifies failure handling behavior for any/specific result-code(s) to identify the type of failure and failure handling action for specific credit control request type.

any-error: Specifies failure handling behavior for those result-codes for which failure-handling behavior has not been specified.

result_code: Specifies a Diameter failure result code. result_code is the code returned for a failure handling action and must be an integer from 3000 through 4999.

to end_result_code: Use to specify a range of Diameter failure result codes. end_result_code must be an integer from 3000 through 4999, and must be greater than result_code.

continue [ retry-server-on-event | send-ccrt-on-call-termination ] | retry-and-terminate | terminate

As in 8.1 and later releases:

ccfh { continue | retry-and-terminate | terminate }

As in 8.0 release:

cc-request-type

As in 8.0 release:

Usage Guidelines

Use this command to configure the Diameter Policy Control Application (DPCA) failure handling behavior.

When an unknown rulebase comes in CCA, changing of rulebase and failure handling is managed in the following manner:

The default failure handling behavior is:

failure-handling diameter-result-code any-error ccfh terminate

In StarOS release 14.1 and earlier, when an IP CAN session is up, if any CCR-U message delivery fails due to timeout or TCP link failure, the failure-handling action "continue" will be taken for the session and there will not be any further interaction with PCRF and RAR from PCRF is also not accepted (result code 5002 is sent in RAA). If the CCR-U that is triggered for reporting Usage-Monitoring-Information AVP fails, then the usage information is lost.

In 15.0 and later releases, after the IP-CAN session is up, if CCR-U message delivery fails due to timeout or TCP link failure, the failure-handling action "continue retry-server-on-event" will be taken at PCEF. Any request coming from session manager will be forwarded to PCRF, and if message delivery again fails session manager will be notified with status "SN_STATUS_NO_ACTIONS_TAKEN".

If CCR-U for reporting Usage-Monitoring-Information fails, then the unreported usage information is given back to ECS and the usage information is stored at ECS. Usage will be reported in CCR-T or in the next CCR-U (if CLI "event-update send-usage-report" is configured). Also, RAR message from PCRF will be processed and responded with result-code success in RAA.

Refer to the Cisco ASR 5000 Lawful Intercept Configuration Guide for a description of this command.

This command enables or disables the gateway to send multiple back-to-back CCR-Us to PCRF.

Product

GGSN

HA

PDSN

P-GW

S-GW

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

[ default ] max-outstanding-ccr-u value

default

This keyword sets the default value as 1 for the maximum number of outstanding CCR-U messages to be sent to PCRF.

value

This keyword configures a value for the maximum number of outstanding CCR-U messages to be sent to PCRF.

value must be an integer value from 1 through 12.

Usage Guidelines

This command enables the gateway to send multiple outstanding CCR-Us per session to PCRF.

In releases prior to 17.0, ASR5K node supports only one pending CCR-U message per session over Gx interface. Any request to trigger CCR-U (for access side updates/internal updates) were ignored/dropped, when there was already an outstanding message pending at the node. PCEF and PCRF were out of synch if CCR-U for critical update (like RAT change/ULI change) was dropped.

In 17.1 and later releases, this CLI command "max-outstanding-ccr-u" under IMS Authorization Service configuration mode allows multiple CCR-Us towards PCRF. That is, this CLI will allow the user to configure a value of up to 12 as the maximum number of CCR-U messages per session.

The CLI-based implementation allows sending request messages as and when they are triggered and processing the response when they are received. The gateway does re-ordering if the response messages are received out of sequence.

This command enables required subscription-id types for various services. The Subscription-ID AVP will be encoded based on the configured subscription-ID type.

Product

GGSN

HA

IPSG

PDSN

P-GW

Privilege

Security Administrator, Administrator

Mode

Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control Configuration

configure > context context_name > ims-auth-service service_name > policy-control

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-imsa-dpca)#

Syntax

Syntax Description

subscription-id service-type { closed_rp | ggsn | ha | ipsg | l2tplns | mipv6ha | pdsn | pgw } { e164 | imsi | nai } +
{ default | no } subscription-id service-type { closed_rp | ggsn | ha | ipsg | l2tplns | mipv6ha | pdsn | pgw }

default | no

Configures this command with the default setting.

The default behavior is that Subscription-ID AVP will be encoded based on service-type and Diameter dictionary.

{ closed_rp | ggsn | ha | ipsg | l2tplns | mipv6ha | pdsn | pgw } { e164 | imsi | nai }

Controls the encoding of Subscription-ID AVP based on the following service-types associated with services such as GGSN, HA, IPSG, PDSN, etc.

+

Indicates that more than one of the keywords can be entered in a single command.

Usage Guidelines

In releases prior to 15.0, Subscription-ID AVP is encoded based on service-type and Diameter dictionary.

In 15.0 and later releases, when IMS Authorization service encodes the Subscription-ID AVP, IMSA will first check whether or not this CLI command subscription-id service-type is configured. If the CLI is configured for the current service, then IMSA will encode the Subscription-ID AVP based on the configured subscription-ID type. This CLI command takes more precedence than the default behavior.

If the CLI configuration does not encode any Subscription-ID AVP, then IMSA will encode this AVP based on the default behavior. For example, in GGSN/IPSG service, NAI support is not available. If this CLI command is configured for GGSN/IPSG service with NAI type, then based on CLI IMSA cannot encode any Subscription-ID AVP. By this time default behavior (old behavior based on service-type and dictionary) will add the subscription-ID.