IPCF Node Configuration Procedures

This chapter is meant to be used in conjunction with the other chapters that describes the information needed to configure the IPCF to support PCRF functionality in UMTS/LTE networks.

It is recommended that you identify the options from the previous chapters that are required for your specific deployment. You can then use the procedures in this chapter to configure those options.

This chapter describes following:

IMPORTANT:

At least one Packet Services Card (PSC/PSC2) must be made active prior to service configuration. Information and instructions for configuring PSCs/PSC2s to be active can be found in the Configuring System Settings chapter of the System Administration Guide.

CAUTION:

While configuring any base-service or enhanced feature, it is highly recommended to take care of conflicting or blocked IP addresses and port numbers for binding or assigning. In association with some service steering or access control features, like Access Control List configuration, use of inappropriate port number may result in communication loss. Refer respective feature configuration document carefully before assigning any port number or IP address for communication with internal or external network.

Information Required for Configuring the System as an IPCF

This section provides a high-level series of steps and the associated configuration file examples for configuring the system to perform as an IPCF node in a test environment. Information provided in this section includes the following:

IMPORTANT:

The following sections describe the minimum amount of information required to configure and make the IPCF operational on the network. To make the process more efficient, it is recommended that this information be available prior to configuring the system.

IMPORTANT:

There are additional configuration parameters that are not described in this section. These parameters deal mostly with fine-tuning the operation of the IPCF in the network. Information on these parameters can be found in the appropriate sections of the Command Line Interface Reference.

Required Local Context Configuration Information

The following table lists the information that is required to configure the local context on an IPCF.


Table 1. Required Information for Local Context Configuration
Required Information Description
Management Interface Configuration
Interface name An identification string between 1 and 79 characters (alpha and/or numeric) by which the interface is recognized by the system.

Multiple names are needed if multiple interfaces are configured.
IP address and subnet IPv4 addresses assigned to the interface.

Multiple addresses and subnets are needed if multiple interfaces are configured.
Physical port number The physical port to which the interface is bound. Ports are identified by the chassis slot number where the line card resides followed by the number of the physical connector on the card. For example, port 17/1 identifies connector number 1 on the card in slot 17.

A single physical port can facilitate multiple interfaces.
Gateway IP address Used when configuring static IP routes from the management interface(s) to a specific network.
Security administrator name The name or names of the security administrator with full rights to the system.
Security administrator password Open or encrypted passwords can be used.
Remote access type(s) The type of remote access that is used to access the system such as telnetd, sshd, and/or ftpd.


Required Source Context Configuration Information

The following table lists the information that is required to configure the Source context on an IPCF.


Table 2. Required Information for Source Context Configuration
Required Information Description
VPN Context and Interface Configuration
Source context name An identification string from 1 to 79 characters (alpha and/or numeric) by which the Source context is recognized by the system. Generally it is identified as source context.
Gx Interface name An identification string between 1 and 79 characters (alpha and/or numeric) by which the interface is recognized by the system.

Multiple names are needed if multiple interfaces are configured.
IP address and subnet Local IPv4 addresses assigned to the interface to connect with PCEF or other components in network.

Multiple addresses and subnets are needed if multiple interfaces are configured.
Physical port number The physical port to which the interface is to be bound. Ports are identified by the chassis slot number where the line card resides followed by the number of the physical connector on the card. For example, port 17/1 identifies connector number 1 on the card in slot 17. A single physical port can facilitate multiple interfaces.
PCC-Service Name An identification string between 1 to 63 characters (alpha and/or numeric) by which the PCC-service can be identified on the system. It is configured in Context configuration mode.
PCC-Policy-Service Name An identification string between 1 to 63 characters (alpha and/or numeric) by which the PCC-Policy service can be identified on the system. It is configured in Context configuration mode.

Multiple names are needed if multiple PCC-Policy services are configured.
PCC-AF (Application Function) Service Name An identification string between 1 to 63 characters (alpha and/or numeric) by which the PCC-Application-Function-Service name can be identified on the system. It is configured in Context configuration mode.
PCC-Service Configuration
Action-Set Name

An identification string between 1 to 63 characters (alpha and/or numeric) by which the PCC-Action-Set can be identified on the system. It is configured in PCC-Service configuration mode.

Multiple names are needed if multiple PCC-Action-Sets are configured.
PCC-Action-Set Configuration
Monitoring Key

An integer value between 1 to 65535 to indicate the associated/disassociated Monitoring Key which is installed in PCEF for usage tracking. It is configured in PCC-Service configuration mode.
Rule name

An identification string between 1 to 63 characters (alpha and/or numeric) to indicate the configured rule on PCEF for activation of deactivation.
Rulebase name

An identification stringbetween 1 to 63 characters (alpha and/or numeric) to indicate the configured rule on PCEF for activation of deactivation.
QoS Profile name

An identification string between 1 to 63 characters (alpha and/or numeric) to indicate the associated/disassociated QoS profile. It is configured in PCC-Service configuration mode.
QCI

An integer value between 1 to 255 to indicate the QoS Class Identifier associated with specific QoS profile.
Condition-Group Name

An identification string between 1 to 63 characters (alpha and/or numeric) by which the PCC-Condition-Group can be identified on the system. It is configured in PCC-Service configuration mode.

Multiple names are needed if multiple PCC-Condition-Groups are configured.
Data-Service Name

An identification string between 1 to 63 characters (alpha and/or numeric) by which the PCC-Data-Service can be identified on the system. It is configured in PCC-Service configuration mode.

Multiple names are needed if multiple PCC-Data Services are configured.
PCC-Map-Profile Priority

An integer value between 1 to 1024 to identify the keys used to match the profile for a subscriber in a PCC-service instance for IPCF configuration. It is configured in PCC-Service configuration mode.

The profile map is used when the subscriber session established. It is based on the priority of map and condition matches the corresponding named profile is used for the subscriber session.

Map-Profile priority needs to match with specific profile policy and optionally with following options:
  • APN name
  • Condition Group name
  • Missing SPR Profile
  • Subscription Attribute name and value

Multiple priority values are needed if multiple PCC-Map-Profile priorities are configured.
PCC-Monitoring Key Value

An integer value between 1 to 65535 to configure the Monitoring Key with a configurable grant volume size from 1 through 4294967296 bytes. IPCF installs this Monitoring Key in PCEF for usage tracking.

Multiple priority values are needed if multiple PCC-Monitoring Keys are configured.
Profile Name

An identification string between 1 to 63 characters (alpha and/or numeric) by which the PCC-Profile can be identified on the system. It is configured in PCC-Service configuration mode.

Multiple names are needed if multiple PCC-Profiles are configured.
PCC-Profile Configuration
Evaluation Priority

An integer value between 1 to 1024 to identify the keys used to match the PCC-Condition Group with corresponding PCC-Action Set in a PCC-Service Profile instance. It is configured in PCC-Service configuration mode.
Condition-Group Name

An identification string between 1 to 63 characters (alpha and/or numeric) by which the PCC-Condition-Group can be identified on the PCC-Profile instance to match with the PCC-Action Set with required evaluation priority. It is configured in PCC-Service configuration mode.
Action-Set Name

An identification string between 1 to 63 characters (alpha and/or numeric) by which the PCC-Action Set can be identified on the PCC-Profile instance to match with the PCC-Condition Group with required evaluation priority. It is configured in PCC-Service configuration mode.
QoS Profile name

An identification string between 1 to 63 characters (alpha and/or numeric) to indicate the associated/disassociated QoS profile. It is configured in PCC-Service configuration mode.
QCI

An integer value between 1 to 255 to indicate the QoS Class Identifier associated with specific QoS profile.
QoS Profile Name

An identification string between 1 to 63 characters (alpha and/or numeric) by which the PCC-QoS Profile can be identified on the system. It is configured in PCC-Service configuration mode.

Multiple names are needed if multiple PCC-QoS Profiles are configured.
PCC-QoS Profile Configuration
QCI

An integer value between 1 to 255 to indicate the QoS Class Identifier to associate with QoS profile instance.
Allocation and Retention Priority (ARP) value

An integer value between 1 to 15 to indicate the ARP value in QoS profile instance.
Guaranteed Bit Rate (GBR) value

An integer value between 0 to 104857600 to set the guaranteed bit rate in uplink/downlink direction in QoS profile instance.
Maximum Bit Rate (MBR) value

An integer between 0 to 104857600 to set the maximum bit rate in uplink/downlink direction in QoS profile instance.
PCC-Policy-Service Configuration
PCC-Service Name An identification string between 1 to 63 characters (alpha and/or numeric) which is associated with PCC-Policy-Service on system. The name is a pre configured PCC-Service instance in Context configuration mode.
Diameter Origin Endpoint (Gxx) name An identification string by which the Diameter endpoint towards PCEF is associated with PCC-Policy-Service on system. The name is a pre configured Diameter Endpoint instance for Gx/Gxa interface in Context configuration mode.
PCC-AF-Service Configuration
PCC-Service Name An identification string between 1 to 63 characters (alpha and/or numeric) which is associated with PCC-AF-Service on system. The name is a pre configured PCC-Service instance in Context configuration mode.
Diameter Origin Endpoint (Rx) name An identification string by which the Diameter endpoint towards PCEF is associated with PCC-AF-Service on system. The name is a pre configured Diameter Endpoint instance for Rx interface in Context configuration mode.
Diameter Dictionary name An identification string by which the Diameter dictionary in identified and used by AF service over Rx interface on system.


Required Destination Context Configuration Information

The following table lists the information that is required to configure the destination context.


Table 3. Required Information for Destination Context Configuration
Required Information Description
Destination context name An identification string between 1 to 79 characters (alpha and/or numeric) by which the destination context is recognized by the system.
IP address and subnet Local IPv4 addresses assigned to the interface to connect with SSC or other components in network.

Multiple addresses and subnets are needed if multiple interfaces are configured.
Physical port number The physical port to which the interface is to be bound. Ports are identified by the chassis slot number where the line card resides followed by the number of the physical connector on the card. For example, port 17/1 identifies connector number 1 on the card in slot 17. A single physical port can facilitate multiple interfaces.
Gateway IP address Used when configuring static IP routes from the management interface(s) to a specific network.
PCC-Sp-Endpoint Name An identification string between 1 to 63 characters (alpha and/or numeric) by which the PCC-Sp interface endpoint name to serve with SSC can be identified on the system. It is configured in Context configuration mode.

Multiple names are needed if multiple PCC-Sp interface endpoints are configured.
Event Notification Interface Endpoint Name An identification string between 1 to 31 characters (alpha and/or numeric) by which the Event Notification Interface endpoint name to connect with Event Notification server can be identified on the system. It is configured in Context configuration mode.

Multiple names are needed if multiple Event Notification interface endpoints are configured.
PCC-Sp-Endpoint Configuration
Access Type Defines the type of access used for SSC communication. By default it is “Diameter”.
Diameter Origin Endpoint (Sp) name An identification string by which the Diameter origin endpoint towards PCEF is associated with PCC-Sp-Endpoint on system. The name is a pre configured Diameter Endpoint instance for Sp interface in Context configuration mode.
Diameter Dictionary name An identification string by which the Diameter dictionary is identified and used by PCC-Sp-Endpoint over Sp interface on system.
Event Notification Interface Endpoint Configuration
IP address and subnet This is the assigned IP address of the IPCF node on which it will communicate with Event Notification server.

Multiple addresses and/or subnets are needed if multiple interfaces are configured.
Peer name This is an identification string between 1 to 79 characters (alpha and/or numeric) by which the peer (Event Notification Server) node is recognized by the IPCF.
Peer IP address and subnet This is the assigned IP address of the Event Notification server on which IPCF communicates for event notification management.

Multiple addresses and/or subnets are needed if multiple interfaces are configured.
Peer port number This specifies the port number between 1 to 65535 on which Event Notification will be received by Event Notification server from IPCF.


Required AAA Context Configuration Information

The following table lists the information that is required to configure the Diameter (AAA) context.


Table 4. Required Information for AAA Context Configuration
Required Information Description
AAA context name An identification string between 1 to 63 characters (alpha and/or numeric) by which the AAA context will be recognized by the system.
Diameter Endpoint Name Configuration
Diameter Endpoint name (Gx) An identification string by which the Diameter endpoint towards PCEF is recognized by the system. The name can be between 1 to 63 characters (alpha and/or numeric) and is not case sensitive. It may also contain dots ( . ) and/or dashes ( - ).

This Diameter endpoint name will be associated with PCC-Policy Service configuration instance.

Multiple names are needed if multiple Diameter Endpoints are used.
Diameter Endpoint name (Sp) An identification string by which the Diameter endpoint towards SSC is recognized by the system. The name can be between 1 to 63 characters (alpha and/or numeric) and is not case sensitive. It may also contain dots ( . ) and/or dashes ( - ).

This Diameter endpoint name will be associated with PCC-Sp-Endpoint configuration instance.

Multiple names are needed if multiple Diameter Endpoints are used.
Diameter Endpoint name (Rx) An identification string by which the Diameter endpoint towards AF is recognized by the system. The name can be between 1 to 63 characters (alpha and/or numeric) and is not case sensitive. It may also contain dots ( . ) and/or dashes ( - ).

This Diameter endpoint name will be associated with PCC-AF-Service configuration instance.

Multiple names are needed if multiple Diameter Endpoints are used.
Diameter Endpoint Name (Gx) Configuration
Origin Realm name This is an identification string between 1 to 63 characters (alpha and/or numeric) by which the Domain (Realm) of IPCF node is recognized by the PCEF.
Origin Host name This is an identification string between 1 to 63 characters (alpha and/or numeric) by which the host (IPCF) node is recognized by the PCEF.
Origin Host IP address and subnet This is the assigned IP address of the IPCF on which it will communicate with PCEF over Gx interface.

Multiple addresses and/or subnets are needed if multiple interfaces are configured.
Origin Host port number This specifies the port number between 1 to 65535 on which incoming traffic from PCEF will be accepted on IPCF.
Peer name This is an identification string between 1 to 79 characters (alpha and/or numeric) by which the peer (PCEF) node is recognized by the IPCF.
Peer IP address and subnet This is the assigned IP address of the PCEF on which IPCF communicates over Gx interface.

Multiple addresses and/or subnets are needed if multiple interfaces are configured.
Peer port number This specifies the port number between 1 to 65535 from which incoming traffic from PCEF will be sent to IPCF.
Diameter Endpoint Name (Rx) Configuration
Origin Realm name This is an identification string between 1 to 79 characters (alpha and/or numeric) by which the Domain (Realm) of IPCF node is recognized by the AF.
Origin Host name This is an identification string between 1 to 79 characters (alpha and/or numeric) by which the host (IPCF) node is recognized by the AF.
Origin Host IP address and subnet This is the assigned IP address of the IPCF on which it will communicate with AF over Rx interface.

Multiple addresses and/or subnets are needed if multiple interfaces are configured.
Origin Host port number This specifies the port number between 1 to 65535 on which incoming traffic from AF will be accepted on IPCF.
Peer name This is an identification string between 1 to 79 characters (alpha and/or numeric) by which the peer (AF) node is recognized by the IPCF.
Peer IP address and subnet This is the assigned IP address of the AF on which IPCF communicates over Rx interface.

Multiple addresses and/or subnets are needed if multiple interfaces are configured.
Peer port number This specifies the port number between 1 to 65535 from which incoming traffic from AF will be sent to IPCF.
Diameter Endpoint Name (Sp) Configuration
Origin Realm name This is an identification string between 1 to 79 characters (alpha and/or numeric) by which the Domain (Realm) of IPCF node is recognized by the PCEF.
Origin Host name This is an identification string between 1 to 79 characters (alpha and/or numeric) by which the host (IPCF) node is recognized by the SSC.
Origin Host IP address and subnet This is the assigned IP address of the IPCF on which it will communicate with SSC over Sp interface.

Multiple addresses and/or subnets are needed if multiple interfaces are configured.
Origin Host port number This specifies the port number between 1 to 65535 on which incoming and outgoing traffic from SSC will be processed by IPCF.
Peer name This is an identification string between 1 to 79 characters (alpha and/or numeric) by which the peer (SSC) node is recognized by the IPCF.
Peer IP address and subnet This is the assigned IP address of the SSC on which IPCF communicates over Sp interface.


IPCF Node Configuration

IPCF nodes are configured on system that allow the system to function as an IPCF in the 3G wireless data network.

IMPORTANT:

This section provides the minimum instruction set for configuring an IPCF node that allows the system to process the IP-CAN session. Commands that configure additional properties are provided in the different chapters of Command Line Interface Reference.

These instructions assume that you have already configured the system level configuration as described in System Administration Guide.

IMPORTANT:

Detailed procedure definition for step 1 to step 7 in following procedure is out of the scope of this guide. Kindly refer respective Administration Guides and References for more information.

To configure the system to work as IPCF node:

  1. Make sure that PCEF/BBERF is configured with Gx/Gxa interface support as described in respective Administration Guide.
  2. Make sure that Enhanced Charging Service Rules and Ruledefs are enabled on PCEF as described in Enhanced Charging Service Administration Guide.
  3. Optional. Configure the subscriber threshold parameters for IP-CAN sessions by applying the example configuration in the Thresholding Configuration Guide.
  4. Optional. Configure system to enable logging facilities for IP-CAN session subscribers and protocols by applying the example configuration in the Logging Facility Configuration section.
  5. Optional. Configure congestion control parameters for IP-CAN session instances on system by applying the example configuration in the Congestion Control Configuration section.
  6. Optional. Enable and configure the SNMP Traps to generate alarms and alerts from system for various events and thresholds for PCC related service instances by applying the example configuration in the Alarm and Alert Trap Configuration section.
  7. Create and configure the local interfaces and bind it to IPCF node towards PCEF, SSC or any other component in network by applying the example configuration in the Local Interface Configuration section.
  8. Create and configure the PCC-service and associate related parameters like policy profile, QoS profile, monitoring key, condition group, and action set on IPCF node by applying the example configuration in the PCC-Service Configuration section.
  9. Create and configure the PCC-Policy service and associate related parameters to provide policy processing with PCEF over Gx interface in IP-CAN session by applying the example configuration in the PCC-Policy-Service Configuration section.
  10. Create and configure the PCC-Sp-Endpoint and associate related parameters to provide SSC related processing with SSC over Sp interface for IP-CAN session by applying the example configuration in the PCC-Sp-Endpoint Configuration section.
  11. Create and configure the Diameter Endpoint for Gx and Sp interface to connect with PCEF and SSC by applying the example configuration in the Diameter Endpoint Configuration section.
  12. Create and configure the Event notification server node used to process event notification from IPCF by applying the example configuration in the Event Notification Interface Endpoint Configuration section.
  13. Optional. If using Non-3GPP access technology, modify the PCC-Condition-Group confiuaration to connect with PDSN as PCEF over Gx interface by applying the example configuration in the Non-3GPP IP-CAN Session Configuration section.
  14. Verify your IPCF configuration by following the steps in the IPCF Service Configuration Verification section.
  15. Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

Local Interface Configuration

Use the following example to configure the interfaces in context to be used for PCEF and SSC or other nodes in network:

configure

  context
<vpn_ctxt_name>
-noconfirm

    interface <gx_intf_name>

      ip
address <local_ip_address>/<mask>

      exit

    exit

    interface <sp_intf_name>

      ip
address <local_ip_address>/<mask>

      end
Notes:
  • <vpn_ctxt_name> is name of the source context in which IPCF service is to configure.
  • <gx_intf_name> is name of the interface which is to use IP address <local_ip_address> for communication between IPCF node and PCEF or other components in network.
  • <sp_intf_name> is name of the interface which is to use IP address <local_ip_address> for communication between IPCF node and SSC or other components like Event Notification Server in network.

PCC-Service Configuration

Use the following example to configure the PCC-service on system in context to provide the PCRF functionality in networks:

IMPORTANT:

This section provides the minimum instruction set for configuring an IPCF node that allows the system to process the IP-CAN session. Commands that configure additional properties are provided in the different chapters of Command Line Interface Reference.

  1. Create and configure PCC-Service in context configuration mode with timeout duration, monitoring key, profile mapping and other common parameters by applying the example configuration in the Basic PCC-Service Configuration section.
  2. Configure the QoS profile and parameters by applying the example configuration in the PCC-QoS-Profile Configuration section.
  3. Configure the Condition Group and related parameters by applying the example configuration in the PCC-Condition-Group Configuration section.
  4. Configure the Action set and related parameters by applying the example configuration in the PCC-Action-Set Configuration section.
  5. Configure the Service-Profile and related parameters along with usage monitoring limits by applying the example configuration in the PCC-Service-Profile and Usage Monitoring Configuration section.
  6. Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

Basic PCC-Service Configuration

Use the following example to configure the basic parameters for PCC-service on system to provide PCRF functionality related processing for IP-CAN session in network.

configure

  context <vpn_ctxt_name>

    pcc-service
<pcc_svc_name>
-noconfirm

      timeout
idle <idle_dur [ action reauthorize ]

      timeout
setup <setup_dur>

      timeout
long-duration <ldt_timeout> [ action {detection | disconnect}]

      monitoring-key
<mon_key>
grant-size <volume>

      map-profile
priority <priority_value>
profile-policy name <prof_policy_name>

      multiple-pcef-per-subscriber

      end
Notes:
  • <vpn_ctxt_name> is name of the source context in which PCC-service is configured.
  • <pcc_svc_name> is name of the PCC-service which is to be configured for IPCF functionality in network.

PCC-QoS-Profile Configuration

Use the following example to configure the parameters for PCC-QoS Profiles parameters like QCI, MBR, GBR etc. on system to provide PCRF functionality related processing for IP-CAN session in network.

configure

  context <vpn_ctxt_name>

    pcc-service <pcc_svc_name>

      qos-profile <qos_prof_name>

        qci <qci_id>

        max-bitrate
uplink <ulink_mbr> downlink
<dlink_mbr>

        gauranteed-bitrate
uplink <ulink_gbr>
downlink <dlink_gbr>

        arp-priority
<arp_prior_value> pre-emption {capable | not-capable} {not-vulnerable | vulnerable}

        end
Notes:
  • <vpn_ctxt_name> is name of the source context in which PCC-service is configured.
  • <pcc_svc_name> is name of the PCC-service which is to be configured for IPCF functionality in network.
  • <qos_prof_name> is name of the PCC-QoS-Profile which is to be used to configure the QoS profiles for IPCF functionality in network. This command can be entered multiple times to configure multiple QoS profiles with other parameters, if required. For more information on available parameters for QoS Profile, refer PCC-QoS-Profile Configuration Mode Commands chapter in Command Line Interface Reference.

PCC-Condition-Group Configuration

Use the following example to configure the parameters for various condition parameters like threshold, RAT, event triggers etc. on system to provide PCRF functionality related processing for IP-CAN session in network.

configure

  context <vpn_ctxt_name>

    pcc-service <pcc_svc_name>

      condition-group <cond_grp_name>

        threshold-condition
usage-monitor <usage_mon_name>
usage {= | !=} {absolute
value <volume> | subscription-limit | subscription-threshold <subs_thres_limit>}

        radio-access-technology { = | != } <RAT>

        event-trigger { = | != } {an-gw-change | bearer-qos-change | bearer-setup | bearer-termination | default-eps-bearer-qos-change | ip-can-change | loss-of-bearer | out-of-credit | pgw-trace-control | plmn-change | qos-change | qos-change-exceeding-authorization | rai-change | rat-change | reallocation-of-credit | recover-of-bearer | resource-modification-request | revalidation-timeout | session-setup | session-termination | sgsn-change | successful-resource-allocation | tft-change | ue-ip-address-allocate | ue-ip-address-release | ue-time-zone-change | user-location-change}

        bearer-count { = | != | <= | >= } <num_bearer>

        user-equipment-info
eui64 {= | !=} <eui64>

        user-equipment-info
imeisv  {= | !=} <imei_sv >

        user-equipment-info
mac {= | !=} <mac_value>

        user-equipment-info
modified-eui64 {= | !=} <meui64>

        exit
Notes:
  • <vpn_ctxt_name> is name of the source context in which PCC-service is configured.
  • <pcc_svc_name> is name of the PCC-service which is to be configured for IPCF functionality in network.
  • <cond_grp_name> is name of the PCC-Condition-Group which is to be used to configure the session condition parameters for IPCF functionality in network. This command can be entered multiple times to configure multiple condition groups with other parameters, if required. For more information on available parameters for PCC-Condition-Group, refer PCC-Condition-Group Configuration Mode Commands chapter in Command Line Interface Reference.

PCC-Action-Set Configuration

Use the following example to configure the parameters for action-set parameters like rule activation, authorization, usage monitoring key association with PCC-Service etc. on system to provide PCRF functionality related processing for IP-CAN session in network.

configure

  context <vpn_ctxt_name>

    pcc-service <pcc_svc_name>

      action-set <actionset_name>

        rule-activate <rule_name>

        associate
monitoring-key <mon_key_id>
usage-monitor <usage_mon_name>

        authorize {apn-mbr | default-eps-bearer | qci} qos-profile
<qos_prof_name>

        end
Notes:
  • <vpn_ctxt_name> is name of the source context in which PCC-service is configured.
  • <pcc_svc_name> is name of the PCC-service which is to be configured for IPCF functionality in network.
  • <actionset_name> is name of the PCC-Action-set which is to be used to configure the set of action to initiate on the basis of condition parameters for IPCF functionality in network. This command can be entered multiple times to configure multiple action-sets with other parameters, if required. For more information on available parameters for Action-set, refer PCC-Action-Set Configuration Mode Commands chapter in Command Line Interface Reference.

PCC-Service-Profile and Usage Monitoring Configuration

Use the following example to configure the service profile and sets the parameters like usage limits, rulebase association, service-tag etc. on system to provide PCRF functionality related processing for IP-CAN session in network.

configure

  context <vpn_ctxt_name>

    pcc-service <pcc_svc_name>

      profile <profile_name>

        eval-priority
<priority_value> condition-group
<cond_grp_name>
action-set <actionset_name>

        associate
monitoring-key <mon_key_id>
usage-monitor <usage_mon_name>

        default-rulebase-name <rulebase_name>

        service-tag
<svc_tag> {rule-name
<rule_name> | rulebase-name <rulebase_name>}

        usage-monitor
<usage_mon_name> -noconfirm

          usage-limit
volume [downlink <dlink_volume> | total
<total_volume> | uplink
<uplink_volume>]

          end
Notes:
  • <vpn_ctxt_name> is name of the source context in which PCC-service is configured.
  • <pcc_svc_name> is name of the PCC-service which is to be configured for IPCF functionality in network.
  • <profile_name> is name of the PCC-Service-Profile which is to be used to map in IP-CAN for IPCF functionality in network. This command can be entered multiple times to configure multiple Subscriber profiles with other parameters, if required. For more information on available parameters for Subscriber Profile, refer PCC-Profile-Configuration Mode Commands chapter in Command Line Interface Reference.
  • <usage_mon_name> is name of the PCC-Usage-Monitor-Key which is to be used to monitor the usage in IP-CAN for IPCF functionality in network. This command can be entered multiple times to configure multiple PCC-Usage-Monitor-Key, if required. For more information on available parameters for PCC-Service-Profile, refer PCC-Usage-Monitor Configuration Mode Commands chapter in Command Line Interface Reference.

PCC-Policy-Service Configuration

Use the following example to configure the PCC-Policy-service on system in to provide the Gx interface functionality for Policy related processing with PCEF in network:

configure

  context <vpn_ctxt_name>

    pcc-policy-service <pcc_policy_svc_name>
-noconfirm

      associate <pcc_svc_name>

      diameter
origin endpoint <gx_end_name>

      diameter
dictionary {gxa-standard | r7-standard | standard}

      max
policy-sessions <max_session>

      subscriber-binding-identifier {imsi | msisdn | nai | sip-uri}

      ehrpd-access-bcm {as-requested | ue-nw | ue-only}

      gprs-access-bcm {as-requested | ue-nw | ue-only}

      end
Notes:
  • <vpn_ctxt_name> is name of the source context in which PCC-service is configured.
  • <pcc_policy_svc_name> is name of the Gx interface configuration instance which provides Gx interface functionality on IPCF node for subscriber policy processing with PCEF in IP-CAN session.
  • <pcc_svc_name> is name of the PCC-Service which is to be associated with PCC-Policy service and configured in PCC-Service Configuration section.
  • <gx_end_name> is name of the Diameter Endpoint node which is to be used as Gx interface node with PCEF and configured in Diameter Endpoint Configuration section.

PCC-Sp-Endpoint Configuration

Use the following example to configure the PCC-Sp-Endpoint on system to provide Sp interface functionality for subscriber profile related processing for IP-CAN session with SSC in network:

configure

  context <vpn_ctxt_name>

    pcc-sp-endpoint
<sp_endpoint_node> -noconfirm

      access-type {custom | diameter | ldap}

      diameter
origin endpoint <sp_end_name>

      diameter
dictionary {sh-custom-starent | sh-standard}

      profile-update-notification {allow | disallow}

      spr
subscriber identifier {imsi | msisdn

      end
Notes:
  • <vpn_ctxt_name> is name of the source context in which PCC-Sp-Endpoint is configured.
  • <sp_endpoint_node> is name of the Sp interface configuration instance which provides Sp interface functionality on IPCF node for subscriber profile processing with SSCP in IP-CAN session.
  • <sp_end_name> is name of the Diameter Endpoint node which is to be used as Sp interface node with SSC and configured in Diameter Endpoint Configuration section.

Diameter Endpoint Configuration

Use the following example to configure the Diameter Endpoints on IPCF node for Gx/Gxa and Sp interface to interact with PCEF and SCC respectively for IP-CAN session processing in network:

configure

  context <vpn_ctxt_name>

    diameter
endpoint <gx_end_name>

      origin
realm <realm_ipcf>

      origin
host <ipcf_host_name > address
<local_ip_address >
port <inbound_gx_port>
accept-incoming-connections 

      no
watchdog-timeout

      use-proxy
server-mode demux-mode

      peer
<pcef_peer_name>
realm <pcef_realm_name>
address <pcef_ip_address>
port <outbound_pcef_port>

      exit

    diameter
endpoint <sp_end_name>

      origin
realm <realm_ipcf>

      origin
host <ipcf_host_name > address
<local_ip_address >
port <inbound_sp_port>

      no
watchdog-timeout

      use-proxy

      connection
timeout <dur>

      connection
retry-timeout <dur>

      peer
<ssc_peer_name>
realm <ssc_realm_name>
address <ssc_ip_address>

      end
Notes:
  • <vpn_ctxt_name> is name of the source context in which PCC-service is configured.
  • <gx_end_name> is name of the Gx interface instance which is to be configured for subscriber policy processing over Gx interface in network with PCEF.
  • <realm_ipcf> is name of the domain (Realm) in which IPCF node is located.
  • <pcef_peer_name> is name of the PCEF (GGSN) node which is to be connected with IPCF for subscriber policy processing over Gx interface in network.
  • <pcef_ip_address> is IP address of the PCEF (GGSN) node which is to be connected with IPCF for subscriber policy processing over Gx interface in network.
  • <pcef_realm_name> is name of the domain (Realm) in which PCEF node is located.
  • <sp_end_name> is name of the Sp interface instance which is to be configured for subscriber profile processing over Sp interface in network with SSC.
  • <ssc_peer_name> is name of the SSC node which is to be connected with IPCF for subscriber profile processing over Sp interface in network.
  • <ssc_realm_name> is name of the domain (Realm) in which SSC node is located.
  • <ssc_ip_address> is IP address of the SSC node which is to be connected with IPCF for subscriber profile processing over Sp interface in network.

Event Notification Interface Endpoint Configuration

Use the following example to configure the Event Notification Interface Endpoint on IPCF node to interact with Event Notification server for event notification management during IP-CAN session in network:

configure

  context <vpn_ctxt_name>

    event-notif-endpoint <event_notif_intc_name>

      address <local_ip_address>

      peer
name <remote_server_name> address
<remote_server_ip_address>
port <out_remote_serv_port>

      end
Notes:
  • <vpn_ctxt_name> is name of the context in which PCC-service is configured.
  • <event_notif_intc_name> is name of the Event notification interface instance on IPCF which is to be used for with remote Event notification server.
  • <local_ip_address> is IP address of the IPCF node which configured in Local Interface Configuration section.
  • <remote_server_name> is name of the remote Event Notification collection and processing server. Multiple peers can be configured in one Event Notification Interface.
  • <remote_server_ip_address> is IP address of the remote Event notification collection processing server which is to be used for event notification management for IP-CAN session.

Non-3GPP IP-CAN Session Configuration

Use the following example to modify the PCC-Condition Group configuration to support the conditions to process CDMA UE subscribers coming from PDSN node over Gx interface where PDSN acts as PCEF with IPCF node for non-3GPP IP-CAN session in network:

configure

  context <vpn_ctxt_name>

    pcc-service <pcc_svc_name>

      condition-group <cond_grp_name>

        base-station-id {[ sid {= | != | <| <= | >| >= } <sys_identifier>] | range <start_range>
to <end_range>]] [ nid {= | != | <| <= | >| >= } <netwrk_identifier> ] | range <start_range>
to <end_range>]] [ cellid {= | != | <| <= | >| >= } <cell_identifier> ] | range <start_range>
to <end_range> ]]}

        nai {= | !=} {username <user_name> [domain
<domain>] | domain <domain>}

        user-equipment-info
esn {= | !=} <esn>

        user-equipment-info
meid {= | !=} <meid>

        end
Notes:
  • <vpn_ctxt_name> is name of the context in which PCC-service is configured.
  • Currently following are not supported for non-3GPP IP-CAN session support: multiple bearer in single Non-3GPP IP-CAN session Bearer control mode when initiated by both, the UE and Network Network initiated bearer creation/modification/deletion
  • <cond_grp_name> is a preconfigured PCC-Condition-Group which is to be used to configure the session condition parameters for IPCF functionality in network. For more information on initial configuration for PCC-Condition-Group, refer PCC-Condition-Group Configuration in PCC-Service Configuration section.

Verifying IPCF Configuration

This section shows the configuration parameters configured for IPCF service.
  1. Verify that your PCC-service was created and configured properly by entering the following command in Exec Mode: 
    show pcc-service service-name <pcc_svc_name>
    The output of this command shows a concise listing of PCC-service parameter settings.
  2. Verify configuration errors of your PCC-service by entering the following command in Exec Mode: 
    show configuration
errors section pcc-service verbose}
    The output of this command displays current configuration errors and warning information for the target configuration file as specified for PCC-service.
  3. Verify that your PCC-Policy service was created and configured properly by entering the following command in Exec Mode: 
    show pcc-policy service
name <pcc_policy_svc_name>
    The output of this command shows a concise listing of PCC-Policy service parameter settings.
  4. Verify configuration errors of your PCC-Policy service by entering the following command in Exec Mode: 
    show configuration
errors section pcc-policy-service verbose}
    The output of this command displays current configuration errors and warning information for the target configuration file as specified for PCC-Policy service.

IMPORTANT:

Output descriptions for commands are available in the Statistics and Counters Reference.

Logging Facility Configuration

Use the following example to configure the IPCF node system to enable the logging and debug facilities for IP-CAN session subscribers and related protocols.

IMPORTANT:

This section provides the minimum instruction set for configuring logging facilities for system monitoring that allows the user to monitor the events and logging. Commands that configure additional logging facilities are provided in the Exec Mode Command chapter of Command Line Interface Reference.

configure

  logging
console

  logging
display event-verbosity {min | concise | full}

  logging
filter runtime facility bindmux { critical | error | warning | unusual | info | trace | debug }

  logging
filter runtime facility diameter { critical | error | warning | unusual | info | trace | debug }

  logging
filter runtime facility event-notif { critical | error | warning | unusual | info | trace | debug }

  logging
filter runtime facility evlog { critical | error | warning | unusual | info | trace | debug }

  logging
filter runtime facility  pccmgr { critical | error | warning | unusual | info | trace | debug }

  logging
filter runtime facility sprmgr { critical | error | warning | unusual | info | trace | debug }

  logging
filter runtime facility threshold { critical | error | warning | unusual | info | trace | debug }

  end

IMPORTANT:

Refer System Administration Guide for more information on logging facility configuration.

Displaying Logging Facility

This section shows the logging facility event logs for logging facilities enabled on IPCF node.
  1. Verify the logging facilities configured on IPCF node by entering the following command in Exec Mode: 
    show logging [ active | verbose]
    The output of this command provides the display of event logs for configured logging facilities.

Congestion Control Configuration

To configure Congestion Control functionality:

  1. Configure Congestion Control Threshold by applying the example configuration in the Configuring the Congestion Control Threshold section.
  2. Configure Service Congestion Policies for PCC related services by applying the example configuration in the Configuring Service Congestion Policies section.
  3. Optional. Operator can configure the system to reject the all new incoming call coming to specific or all PCC related service instances in a busy-out or planned maintenance or for troubleshooting by applying the example configuration in the Configuring New Call Policy section.
  4. Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration. For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

Configuring the Congestion Control Threshold

To configure congestion control threshold, apply the following example configuration:

configure

   congestion-control
threshold max-sessions-per-service-utilization <percent>

   congestion-control
threshold tolerance <percent>

   end

Notes:

  • There are several additional threshold parameters. See the Global Configuration Mode chapter of the Command Line Interface Reference for more information.
  • The tolerance is the percentage under a configured threshold that dictates the point at which the condition is cleared.
  • Repeat this configuration as needed for additional thresholds.

Configuring Service Congestion Policies

To create a congestion control policy for PCC related sessions, apply the following example configuration:

configure

   congestion-control
policy {pcc-af-service | pcc-policy-service } action { drop | none | reject }

   end
Notes:
  • For all IP-CAN session on PCC related services none is the default action, if this command is not configured.

Configuring New Call Policy

To create a new call policy in a busy hour or planned maintenance or other operator intervened scenario, apply the following example configuration:

newcall policy pcc-af-service [all | name <pcc_af_svc_name> ] reject

newcall policy pcc-policy-service [all | name <pcc_policy_svc_name> ] reject
Notes:
  • For IP-CAN sessions reject is the default action for all new calls coming on a specific or all PCC related service instance.

Alarm and Alert Trap Configuration

To enable and configure the SNMP Traps to generate alarms and alerts from system for various events and thresholds in PCC related services, apply the following example configuration:

configure

    snmp
trap { enable | suppress} [Congestion
         CongestionClear] {ThreshPCCAFSessions | ThreshPCCPolicySessions} [ target <trap_collector>]

    snmp
trap { enable | suppress} [Congestion
         CongestionClear] {ThreshPerServicePCCAFSessions | ThreshPerServicePCCPolicySessions} [ target <trap_collector>]

    snmp
trap { enable | suppress} [Congestion
         CongestionClear] {ThreshClearPCCAFSessions | ThreshClearPCCPolicySessions} [ target
<trap_collector>]

    snmp
trap { enable | suppress} [Congestion
         CongestionClear] {ThreshClearPerServicePCCAFSessions | ThreshClearPerServicePCCPolicySessions} [ target <trap_collector>]

    snmp
trap { enable | suppress} [Congestion
         CongestionClear] {PCCAFServiceStart | PCCAFServiceStop} [ target <trap_collector>]

    snmp
trap { enable | suppress} [Congestion
         CongestionClear] {PCCPolicyServiceStart | PCCPolicyServiceStop} [ target <trap_collector>]

   end
Notes:
  • Repeat these configuration as needed for additional traps.
  • There are several additional SNMP Traps which can be configured. Refer Global Configuration Mode chapter of the Command Line Interface Reference for more information.
  • For more information on SNMP Traps, refer System SNMP-MIB Reference.

SNMP-MIB Traps for IPCF Node

SNMP traps are used to manage and monitor the service on IPCF node.

Supported SNMP traps and its id are indicated in the following table.
Table 5. SNMP Traps and Object Ids
Traps Object Id

starPCCPolicyServiceStart

starentTraps 1127

starPCCPolicyServiceStop

starentTraps 1128

starPCCQuotaServiceStart

starentTraps 1129

starPCCQuotaServiceStop

starentTraps 1130

starPCCAFServiceStart

starentTraps 1131

starPCCAFServiceStop

starentTraps 1132

starSPRServerUnreachable

starentTraps 1133

starSPRServerReachable

starentTraps 1134

starNtfyIntfPeerUnreachable

starentTraps 1173

starNtfyIntfPeerReachable

starentTraps 1174


IMPORTANT:

For more information on SNMP trap configuration and supported object ids, refer System SNMP-MIB Reference.

Event IDs for IPCF Node

Identification numbers (IDs) are used to reference events as they occur when logging is enabled on the system. Logs are collected on a per facility basis.

Each facility possesses its own range of event IDs as indicated in the following table.

IMPORTANT:

Not all event IDs are used on all platforms. It depends on the platform type and the license(s) running.

For more information on logging facility configuration and event id, refer Configuring and Viewing System Logs chapter in System Administration Guide.
Table 6. System Event Facilities and ID Ranges
Facility Event ID Range
Demux-Bindmux Facility Events 158200-158999
PCC Manager Facility Events 159000-159499
SPR Manager Facility Events 159500-159999
LDAP Request Facility Events 160000-160499
Event Notification Interface Facility Events 170000-170499
AAA Client Facility Events 6000-6999
Alarm Controller Facility Events 65000-65999
Card/Slot/Port (CSP) Facility Events 7000-7999
Command Line Interface Facility Events 30000-30999
Event Log Facility Events 2000-2999
Statistics Facility Events 31000-31999
System Facility Events 1000-1999
System Initiation Task (SIT) Main Facility Events 4000-4999
Threshold Facility Events 61000-61999
Virtual Private Network Facility Events 5000-5999