IMS Rx Interface

This chapter describes the system’s support for an IMS Rx interface and explains how it is configured. The product administration guides provide examples and procedures for configuration of basic services on the system. It is recommended that you select the configuration example that best meets your service model and configure the required elements for that model, as described in the Cisco ASR 5000 Session Control Manager Administration Guide, before using the procedures in this chapter.

This chapter contains the following sections:

Feature Description

An IMS Rx interface is a 3GPP (3rd Generation Partnership Project) interface that runs between an application function (AF) and a Policy Charging and Rules Function (PCRF) in a 3GPP architecture. In this case, P-CSCF or A-BG is the AF.

IMPORTANT:

All future references in this chapter to P-CSCF imply support by the A-BG as well.

Overview

P-CSCF can use the IMS Rx interface to communicate with the PCRF during call initiation and renegotiation to provide session information to the PCRF and ensure that a call conforms to policy. P-CSCF uses the IMS Rx interface during registration to subscribe to learn access network information and signaling path status.

PCRF Policy Control

PCRF policy control enables authorization and subscription to PCRF during Registration and VOIP calls. If the P-CSCF cannot connect to the PCRF server (due to incorrect configuration in CSCF or PCRF unavailability), then P-CSCF does not authorize media and VOIP calls will be rejected due to authorization failure. Registrations will be handled normally.

When PCRF policy control is enabled:

  • The P-CSCF sends all media information for all supported media types present in SDP in AAR message to external PCRF via Rx.
    For the other (unsupported) media types, P-CSCF will not send media information in AAR.
  • The P-CSCF can be configured to allow or reject a session based on configuration in case of failure from PCRF.
  • The P-CSCF subscribes to Notification of Signaling Transmission Path Status, as well as IPCAN Change type notification.
    When enabled, the P-CSCF sends AAR to the external PCRF via the Rx interface after UE Registration.
    When disabled, the P-CSCF will not subscribe to any event during Registration with PCRF and no Diameter session will be established.
  • Early media support allows early media by doing QoS commit during QoS Authorization (with PCRF) in P-CSCF.
  • Early bandwidth authorization can be enabled in P-CSCF in SDP offer when communicating with external PCRF via Rx. By default, early bandwidth authorization is disabled.
  • In order to support SIP forking when PCC is applied, provisional response authorization can be enabled on the P-CSCF.
    When enabled, the P-CSCF sends AAR to the external PCRF via the Rx interface for provisional responses like 18X. By default, provisional response authorization is disabled.
  • The P-CSCF fills the required bandwidth for downlink and uplink from the Session Description Protocol (SDP) in the message when communicating with an external PCRF via Rx. QoS bandwidth settings can be configured to be used when the SDP does not contain bandwidth.
  • The P-CSCF shall send indication of emergency session to external PCRF via Rx interface.

Diameter Protocol

Diameter is an Authentication Authorization Accounting (AAA) protocol and is an enhanced version of the RADIUS (Remote Authentication Dial-In User Service) protocol.

When the Diameter protocol is implemented on an IMS network, the PCRF acts as the Diameter server and the P-CSCF acts as the Diameter client. P-CSCF performs the functions of an IMS Rx Diameter client application and handles policy information and media reservations at the border of an access network.

P-CSCF Diameter allows two types of routing:

  • Host-based routing
  • Realm-based routing where multiple peers can be configured

Interfaces are referred to as reference points in IMS. Reference points are named using unique acronyms, such as Rx (receiving reference point).

How it Works

Flows

This section presents call procedure flows.

The following topics and procedure flows are included:

Mobile Originated SIP Call (IMS UE)


Figure 1. Mobile Originated SIP Call (IMS UE) Call Flow

Mobile Terminated SIP Call (IMS UE)


Figure 2. Mobile Terminated SIP Call (IMS UE) Call Flow

SIP Call Termination


Figure 3. SIP Call Termination Call Flow

ASR for an Existing Session (IMS and Non-IMS Clients)


Figure 4. ASR for an Existing Session Call Flow

RAR for an Existing Session (IMS and Non-IMS Clients)


Figure 5. RAR for an Existing Session Call Flow

Authorization Failure for Mobile Originated Call


Figure 6. Authorization Failure for Mobile Originated Call Flow

Authorization Failure for Mobile Terminated Call @ 183


Figure 7. Authorization Failure for Mobile Terminated Call @ 183 Call Flow

Call Hold


Figure 8. Call Hold Call Flow

Call Waiting


Figure 9. Call Waiting Call Flow

Subscription to Notification of Signaling Path Status


Figure 10. Subscription to Notification of Signaling Path Status Call Flow

Figure 11. Notification of Signaling Path Status Call Flow

Figure 12. Cancellation of Subscription to Notification of Signaling Path Status Call Flow

Disabling Early Media


Figure 13. Disabling Early Media Call Flow

Standards Compliance

The IMS Rx interface complies with the following standards:

  • Release 8 3GPP TS 29.208 End-to-end Quality of Service (QoS) signalling flows
  • Release 8 3GPP TS 29.214 Policy and charging control over Rx reference point
  • RFC 3588 (September 2003): “Diameter Base Protocol”

Configuring an IMS Rx Interface

IMPORTANT:

Commands used in the configuration samples 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.

To configure an IMS Rx interface for PCRF policy control:

  1. Create an IMS Rx interface by applying the example configuration in the Creating and Configuring an IMS Rx Interface section.
  2. Optional: Configure Rx service policy rules by applying the example configuration in the Configuring Rx Service Policy Rules section.
  3. If Rx service policy rules are configured, assign the Rx service policy to the P-CSCF service by applying the example configuration in the Assigning Rx Service Policy to P-CSCF Service section.
  4. Optional: Allow early media on the P-CSCF service by applying the example configuration in the Allowing Early Media on P-CSCF Service section.
  5. Optional: Modify specific PCRF policy control options by applying the example configuration in the Configuring PCRF Policy Control Options 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.

Creating and Configuring an IMS Rx Interface

The following example configures an IMS Rx interface:

configure
   require
diameter-proxy single
   context <p-cscf_vpn_context_name>
      diameter
endpoint <endpoint_name>
         origin
realm <realm_name>
         use-proxy
         origin
host <host_name> address <ip_address>
         peer <peer_name> realm <realm_name> address <ip_address> port <port_number>
         route-entry
realm <realm_name> peer <peer_name>
         exit
      cscf
access-profile default
         pcrf-policy-control
         exit
      cscf
service <p-cscf_service_name>
         proxy-cscf
            pcrf-policy-control
               exit
            diameter
policy-control dictionary <rx-dictionary>
            diameter
policy-control peer-select peer <peer_name>
            diameter
policy-control origin endpoint <endpoint_name>
            end

Notes:

  • The require diameter-proxy single command enables one Diameter proxy for the entire chassis.
  • The diameter endpoint command enables the creation, configuration, or deletion of a Diameter endpoint.
  • The origin realm command configures the realm to use in conjunction with the origin host.
    The realm is the Diameter identity. The originator‘s realm must be present in all Diameter messages. The origin realm can typically be a company or service name.
  • The use-proxy command enables Diameter proxy for the Diameter endpoint.
  • The origin host command sets the origin host for the Diameter endpoint.
  • The peer command specifies a peer address for the Diameter endpoint.
  • The route-entry command creates an entry in the route table for a Diameter peer.
  • The pcrf-policy-control command enables PCRF policy control functionality via PCRF through the Rx Diameter interface.
  • The diameter policy-control dictionary command configures the Rx-related Diameter dictionary used in this function.
  • The diameter policy-control peer-select peer command enables the selection of a Diameter policy control peer server providing Rx applications for this service.
  • The diameter policy-control origin endpoint command configures the policy control origin endpoint used in this function.

Configuring Rx Service Policy Rules

The following example configures a service policy profile within the system related to the Rx interface:

configure
   context <p-cscf_vpn_context_name>
      cscf
policy name <rx_policy_name>
         service-policy-rules
            authorization
early-bandwidth
            authorization
prov-response
            qos
bandwidth downlink peak <value>
            qos
bandwidth uplink peak <value>
            end

Notes:

  • The authorization early-bandwidth command enables early bandwidth authorization in P-CSCF in SDP offer when communicating with external policy server via Rx. By default, early bandwidth authorization is disabled.
  • In order to support SIP forking when PCC is applied, the authorization prov-response command enables AAR message to PCRF via Rx for provisional responses like 18X. By default, provisional response authorization is disabled.
  • The P-CSCF/A-BG fills the required bandwidth for downlink and uplink from the Session Description Protocol (SDP) in the message when communicating with an external policy server via Rx. The qos bandwidth command configures the peak uplink and downlink bandwidth to be used when the SDP does not contain bandwidth.
    Peak value of bandwidth is expressed in kilobits per second (kbits). <value> must be an integer from 1 to 99999999.

Assigning Rx Service Policy to P-CSCF Service

The following example assigns an Rx service policy to the P-CSCF service for all subscribers using this service:

configure
   context <p-cscf_vpn_context_name>
      cscf
service <p-cscf_service_name>
         policy-name <rx_policy_name>
         end

Note:

  • Service policies are created and maintained in the CSCF Policy Configuration Mode.

Allowing Early Media on P-CSCF Service

The following example allows early media support on the P-CSCF service:

configure
   context <p-cscf_vpn_context_name>
      cscf
service <p-cscf_service_name>
         policy
allow-early-media
         end

Note:

  • The policy allow-early-media command allows early media by doing QoS commit during QoS Authorization (with PCRF) in P-CSCF. By default, early media support is enabled.

Configuring PCRF Policy Control Options

The following example configures specific PCRF policy control options:

configure
   context <p-cscf_vpn_context_name>
      cscf
service <p-cscf_service_name>
         proxy-cscf
            pcrf-policy-control
               authorization
mediatype <media_type>
               authorization
policy-interworking-failure session-continue
               signaling-bearer-loss subscription
               end

Notes:

  • The authorization mediatype command enables media authorization, using external PCRF via Rx, of specific media types (present in the SDP of a SIP message) only. Be default, media authorization for all the media types is enabled.
  • The authorization policy-interworking-failure session-continue command allows P-CSCF to continue session in case of failure from PCRF. By default, session-reject is activated to reject session with default response code 500.
  • The signaling-bearer-loss command enables subscription to Notification of Signaling Transmission Path Status, as well as IPCAN Change type notification. This command is enabled by default.

Sample IMS Rx Interface Configuration

configure
   require
diameter-proxy single
   context
pcscfvpn
      diameter
endpoint asr5000.ciscosystems.com
         origin
realm ciscosystems.com
         use-proxy
         origin
host asr5000.ciscosystems.com address 192.208.1.10
         peer
minid1 realm ciscosystems.com address 192.208.1.13 port 400
         route-entry
realm ciscosystems.com peer minid1
         exit
      cscf
access-profile default
         pcrf-policy-control
         exit
      cscf
service pcscf
         proxy-cscf
            pcrf-policy-control
               exit
            diameter
policy-control dictionary rx-custom01
            diameter
policy-control peer-select peer minid1
            diameter
policy-control origin endpoint asr5000.ciscosystems.com
            end