It is recommended that before using the procedures in this chapter you select the configuration example that best meets your service model, and configure the required elements for that model as described in the Gateway GPRS Support Node Administration Guide or the IP Services Gateway Administration Guide.Important: The IMS Authorization Service feature described in this chapter is only available if you have purchased and installed a Dynamic Policy Interface feature license on the chassis. If you have not previously purchased this enhanced feature, contact your sales representative for more information.
Important: In addition to standard Gx interface functionality, the Gx interface implemented here provides support of SBLP with additional AVPs in custom DPCA dictionaries. For more information on customer-specific support contact your local technical support representative. In view of required flow bandwidth and QoS, the system provides enhanced support for use of Service Based Local Policy (SBLP) to provision and control the resources used by the IMS subscriber. SBLP is based on the dynamic parameters such as the media/traffic flows for data transport, network conditions and static parameters, such as subscriber configuration and category. It also provides Flow-based Charging (FBC) mechanism to charge the subscriber dynamically based on content usage. With this additional functionality, the Cisco Systems Gateway can act as an Enhanced Policy Decision Function (E-PDF).
[ 600-00-7585 ] Dynamic Policy Interface — license for IMS Authorization Service featureThe Rel 6. Gx interface support is based on the following standards and request for comments (RFCs):
Step 1
Step 2
Step 3
Step 5 Save your configuration as described in the Verifying and Saving Your Configuration chapter.Important: Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.
context <context_name>ims-auth-service <ims_auth_service>p-cscf table { 1 | 2 } row-precedence <precedence_value> { address <ip_address> | ipv6-address <ipv6_address> }diameter origin endpoint <endpoint_name>diameter dictionary <dictionary>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-and-terminate | terminate }diameter host-select row-precedence <precedence_value> table { 1 | 2 } host <host_name> [ realm <realm_name> ] [ secondary host <host_name> [ realm <realm_name> ] ]diameter host-select table { 1 | 2 } algorithm { ip-address-modulus | msisdn-modulus | round-robin }
• <context_name> must be the name of the context where you want to enable IMS Authorization Service.
• <ims_auth_service> must be the name of the IMS Authorization Service to be configured for the Gx interface authentication.
• qos-update-timeout <timeout_duration>signaling-flow permit server-address <ip_address> [ server-port { <port_number> | range <start_number> to <end_number> } ] [ description <string> ]diameter host-select table { 1 | 2 } algorithm { ip-address-modulus | msisdn-modulus | round-robin }
Step 1 context <context_name>show ims-authorization service name <ims_auth_service>context <context_name>apn <apn_name>ims-auth-service <ims_auth_service>
• <context_name> must be the name of the context in which the IMS Authorization service was configured.
• <ims_auth_service> must be the name of the IMS Authorization Service configured for IMS authentication in the context.show subscribers ims-auth-service <ims_auth_service><ims_auth_service> must be the name of the IMS Authorization Service configured for IMS authentication.To save changes made to the system configuration, refer to the Verifying and Saving Your Configuration chapter.
• [ 600-00-7585 ] Dynamic Policy Interface — for IMS Authorization Service feature
• [ 600-00-7574 ] Enhanced Charging Bundle 2 1k Sessions — for ECS functionality
• Binding: Binding is the generation of an association between a Service Data Flow (SDF) and the IP CAN bearer (for GPRS a PDP context) transporting that SDF.
• Gating Control: Gating control is the blocking or allowing of packets, belonging to an SDF, to pass through to the desired endpoint. A gate is described within a PCC rule and gating control is applied on a per SDF basis. The commands to open or close the gate leads to the enabling or disabling of the passage for corresponding IP packets. If the gate is closed, all packets of the related IP flows are dropped. If the gate is opened, the packets of the related IP flows are allowed to be forwarded.
• Event Reporting: Event reporting is the notification of and reaction to application events to trigger new behavior in the user plane as well as the reporting of events related to the resources in the Gateway (PCEF).Important: In this release, event triggers “IP-CAN_CHANGE” and “MAX_NR_BEARERS_REACHED” are not supported.
• QoS Control: QoS control is the authorization and enforcement of the maximum QoS that is authorized for a SDF or an IP-CAN bearer or a QoS Class Identifier (QCI). In case of an aggregation of multiple SDFs (for GPRS a PDP context), the combination of the authorized QoS information of the individual SDFs is provided as the authorized QoS for this aggregate.Important: In this release, coordination of authorized QoS scopes in mixed mode (BCM = UE_NW) is not supported.
Important: In this release, provisioning of primary or secondary charging collection function name (Offline Charging Server (OFCS) addresses) over Gx is not supported.
Important: In this release, PCEF does not send the default online and offline charging method in the Credit Control Request - Initial (CCR(I)).
Important: A third kind of rule, the static PCC rule can be preconfigured in the chassis by the operators. Static PCC rules are not explicitly known in the PCRF, and are not under control of the PCRF. Static PCC rules are bound to general purpose bearer with no Gx control.
Important: In this release, configuring the Metering Method and Reporting Level for dynamic PCC rules is not supported.
Important: When a PCRF-provided PCC rule and a predefined PCC rule have the same precedence, the uplink SDF filters of the PCRF-provided PCC rule is applied first.
Important: When a PCRF-provided PCC rule and a predefined PCC rule have the same precedence, the downlink SDF filters of the PCRF-provided PCC rule are applied first.
[ 600-00-7822 ] Charging Over GxImportant: Only total data usage reporting is supported. Uplink/Downlink level reporting is not supported in this release.
Important: The PCEF only reports the accumulated usage since the last report for usage monitoring and not from the beginning.
Important: If the usage threshold is set to zero (infinite threshold), no further threshold events will be generated by PCEF, but monitoring of usage will continue and be reported at the end of the session.
Important: In this release, the Usage-Monitoring-Informtion AVP is expected to be present without a new threshold to disable the usage monitoring after usage reporting when the threshold is breached. If no Usage-Monitoring-Informtion AVP is present in the CCA-U, the monitoring will continue with the old threshold value and the reporting happens when the threshold is breached again.
For information on how to configure the Volume Reporting over Gx feature, see the Configuring Volume Reporting over Gx section.
Step 1
Step 3
Step 5 Optional: Configure the Volume Reporting over Gx feature as described in the Configuring Volume Reporting over Gx section.
Step 6 Save your configuration as described in the Verifying and Saving Your Configuration chapter.Important: Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.
context <context_name>ims-auth-service <ims_auth_service>p-cscf table { 1 | 2 } row-precedence <precedence_value> { address <ip_address> | ipv6-address <ipv6_address> } [ secondary { address <ip_address> | ipv6-address <ipv6_address> } ]diameter origin endpoint <endpoint_name>diameter dictionary <dictionary>diameter request-timeout <timeout>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 ]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-and-terminate | terminate }
• <context_name> must be the name of the context where you want to enable IMS Authorization service.
• <ims_auth_service> must be the name of the IMS Authorization service to be configured for Rel. 7 Gx interface authentication.To enable the Gx interface to connect to a specific PCRF for a range of subscribers configure msisdn-prefix-from <msisdn_prefix_from> and msisdn-prefix-to <msisdn_prefix_to> with the starting and ending MSISDNs respectively.To enable the Gx interface to connect to a specific PCRF for a specific subscriber, configure both msisdn-prefix-from <msisdn_prefix_from> and msisdn-prefix-to <msisdn_prefix_to> with the same MSISDN.qos-update-timeout <timeout_duration>
• Option: To configure signalling restrictions, in the IMS Authorization Service Configuration Mode, enter the following commands:signaling-flow permit server-address <ip_address> [ server-port { <port_number> | range <start_number> to <end_number> } ] [ description <STRING> ]
• Option: To configure action on packets that do not match any policy gates in the general purpose PDP context, in the IMS Authorization Service Configuration Mode, enter the following command:
• To configure the PCRF host destinations configured in the GGSN/PCEF, use the diameter host-select CLI commands.
• To configure the GGSN/PCEF to use a pre-defined rule when the Gx fails, set the failure-handling cc-request-type CLI to continue. Policies available/in use will continue to be used and there will be no further interaction with the PCRF.
Step 1 context <context_name>show ims-authorization service name <ims_auth_service>Use the following example to apply IMS Authorization service functionality to a previously configured APN within the context configured in the Configuring Rel. 7 Gx Interface section.context <context_name>apn <apn_name>ims-auth-service <ims_auth_service>active-charging rulebase <rulebase_name>
• <context_name> must be the name of the context in which the IMS Authorization service was configured.
• <ims_auth_service> must be the name of the IMS Authorization service configured for IMS authentication in the context.show subscribers ims-auth-service <ims_auth_service><ims_auth_service> must be the name of the IMS Authorization service configured for IMS authentication.active-charging service <ecs_service_name>rulebase <rulebase_name>action priority <priority> dynamic-only ruledef <ruledef_name> charging-action <charging_action_name> monitoring-key <monitoring_key>To save changes to the configuration, refer to the Verifying and Saving Your Configuration chapter.
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |