Documente Academic
Documente Profesional
Documente Cultură
10
Configuring Gx Support
CSG2 provides policy control via the Gx interface.
Gx is a Third Generation Partnership Project (3GPP) Diameter application. In a Gx-enabled network, a
Gx reference point is located between a Policy and Charging Rules Function (PCRF) and a Policy and
Charging Enforcement Function (PCEF). The Gx reference point can be used for charging control and
policy control by applying Attribute Value Pairs (AVPs) relevant to the application.
The PCRF acts as a Diameter server and performs the following functions:
It uses the Gx interface to provision PCC rules to, and remove PCC rules from, the PCEF.
It provides network control regarding the service data flow detection, gating, Quality of Service
(QoS), and flow-based charging (except credit management) towards the PCEF.
It receives session- and media-related information from Application Functions (AFs) and informs
the AFs of traffic plane events.
The PCEF acts as a Diameter client and performs the following functions:
It enforces policy, handles flow-based charging, and controls QoS and the handling of user plane
traffic.
It provides service data flow detection and counting as well as online and offline charging
interactions.
Provide applicable charging parameters and policy control for a service data flow.
PCC rules are dynamically provisioned by the PCRF to the PCEF over the Gx interface. Dynamic PCC
rules are dynamically generated in the PCRF. Dynamic PCC rules can be activated, modified, and
deactivated at any time.
Cisco Content Services Gateway - 2nd Generation Release 3.5 Installation and Configuration Guide
OL-19290-02
10-1
Chapter 10
Configuring Gx Support
In a Gx-enabled network, the CSG2 acts as a PCEF, either as part of an eGGSN node, with a CSG2 and
a GGSN as separate cards in a Cisco 7600 Series Router, or as a stand-alone Gi-node, with
interoperability from external GGSNs.
In eGGSN mode, the CSG2 acts as a Gx interface endpoint while the GGSN manages PDP contexts.
The CSG2 and the GGSN communicate with each other using the RADIUS protocol.
The CSG2 provides basic Gx support with enhancements for per-user Layer 7 rules, policy
preloading, and per-user service policies.
The GGSN provides GTP, PDP AAA Authentication, and QoS RAN Signaling.
To enable the CSG2 to parse user profile attributes in eGGSN mode, you must configure either the
ip csg entries user profile radius pass command or the ip csg entries user profile radius remove
command.
In Gi-node mode, the stand-alone CSG2 acts as a Gx interface endpoint. Gi-node mode supports all
of the same functions as eGGSN mode, with the following exception:
PDP Context QoS Signaling is not supported.
The CSG2 supports both the eGGSN mode and the Gi-node mode in both RADIUS endpoint and
RADIUS proxy modes.
Figure 10-1 illustrates the placement of the CSG2 in a Gx-enabled network:
Figure 10-1
Application
Function
Proxy
Call Session
Control Function
V
AAA
IP
Ri
Ri
PCRF
275940
Gi
GPRS
GGSN
CS G2
Cisco Content Services Gateway - 2nd Generation Release 3.5 Installation and Configuration Guide
10-2
OL-19290-02
Chapter 10
Configuring Gx Support
Enabling Gx on the CSG2
Purpose
Defines the Mobile Policy Control & Charging (MPCC) profile to be used by the CSG2 when
sending per-user Credit Control Requests (CCRs) to the PCRF.
Cisco Content Services Gateway - 2nd Generation Release 3.5 Installation and Configuration Guide
OL-19290-02
10-3
Chapter 10
Configuring Gx Support
Preloading Policies
To define a user profile, enter the following commands beginning in global configuration mode:
Command
Purpose
Step 1
Step 2
csg2(config-csg-user-profile)# pcc gx
Step 3
(Optional) Defines the actions that the CSG2 is to take for a PCC
user if the PCRF fails when the user session is activated.
terminateDo not create the CSG2 User Table entry for the
PCC user and do not forward the RADIUS Accounting Start
request. This is the default setting.
Step 4
Step 5
To associate a user profile with a subscriber, enter the following command in global configuration mode:
Command
Purpose
The CSG2 determines that a user is a Gx user in one of the following ways:
The GGSN sends a RADIUS Accounting Start Request or a RADIUS Accounting Interim Request
with Cisco VSAs that indicate that the user is a Gx user.
The CSG2 compares the access point name (APN) name in attribute 30 (Called-Station-Id) of the
RADIUS Accounting Start against a configured list of APN names to determine that the user is a Gx
user.
Preloading Policies
The CSG2 can preload global contents, maps, policies, billing plans, and services, as necessary, from
the PCRF. If configured to do so, the CSG2 preloads policies when it boots up. However, you can also
dynamically load new and changed policies at any time, without rebooting the CSG2.
Note
The standby CSG2 must have replicated all preloaded policy information before requesting replicated
User Table, session, and service information from the active CSG2.
Cisco Content Services Gateway - 2nd Generation Release 3.5 Installation and Configuration Guide
10-4
OL-19290-02
Chapter 10
Configuring Gx Support
Support for Gx TCP Signature Reporting
To preload policies for the CSG2 from the PCRF without rebooting, enter the following command in
privileged EXEC mode:
Command
Purpose
You can also configure a policy preloading retransmission delay and a retransmission number for the
CSG2 to use when sending a Policy Preloading Request to the PCRF.
To configure a delay and retry number, enter the following command in global configuration mode:
Command
Purpose
Cisco Content Services Gateway - 2nd Generation Release 3.5 Installation and Configuration Guide
OL-19290-02
10-5
Chapter 10
Configuring Gx Support
Step 1
After identifying a user is a Gx user, the CSG2 sends a Diameter CCR to the PCRF.
Step 2
The PCRF responds with a CCA message with one or more Layer 4 DGRs formatted as standard
Charging-Rule-Definition AVPs.
Step 3
The CSG2 associates the DGRs with the User Table entry, downloads the DGRs, and sends a RADIUS
CoA Request to the GGSN when complete.
Note
If the CSG2 is a Gi-node, it does not send a RADIUS CoA to the GGSN. Instead, it delays the
proxy or acknowledgement of the RADIUS Accounting Request until it has successfully
downloaded the rules.
If the PCRF fails, the CSG2 does not create the User Table entry for the PCC user, and it does
not forward or acknowledge the RADIUS Accounting Start request.
When provisioning with Cisco AVPs, the CSG2 uses the following procedure:
Step 1
After identifying a user is a Gx user, the CSG2 sends a Diameter CCR to the PCRF.
Step 2
The PCRF responds with a CCA message with one or more Layer 4 DGRs formatted as
Cisco-Charging-Rule-Definition AVPs. (The use of Cisco-Charging-Rule-Definition AVPs enables
features that are available with configured Gx contents.)
Step 3
The CSG2 associates the DGRs with the User Table entry, downloads the rules, and proxies (or ACKs)
the RADIUS request when complete.
Note
If the CSG2 is a Gi-node, it does not send a RADIUS CoA to the GGSN. Instead, it delays the
proxy or acknowledgement of the RADIUS Accounting Request until it has successfully
downloaded the rules.
If the PCRF fails, the CSG2 does not create the User Table entry for the PCC user, and it does
not forward or acknowledge the RADIUS Accounting Start request.
After identifying a user is a Gx user, the CSG2 sends a Diameter CCR to the PCRF.
Cisco Content Services Gateway - 2nd Generation Release 3.5 Installation and Configuration Guide
10-6
OL-19290-02
Chapter 10
Configuring Gx Support
Roaming Support
Step 2
The PCRF responds with a CCA message with one or more Layer 7 DGRs formatted as
Cisco-Charging-Rule-Definition AVPs. The CCA can also include one or more Layer 4 DGRs formatted
as either standard Charging-Rule-Definition AVPs or Cisco-Charging-Rule-Definition AVPs.
Step 3
The CSG2 associates the DGRs with the User Table entry, downloads the rules, and proxies (or ACKs)
the RADIUS request when complete.
Note
If the CSG2 is a Gi-node, it does not send a RADIUS CoA to the GGSN. Instead, it delays the
proxy or acknowledgement of the RADIUS Accounting Request until it has successfully
downloaded the rules.
If the PCRF fails, the CSG2 does not create the User Table entry for the PCC user, and it does
not forward or acknowledge the RADIUS Accounting Start request.
Roaming Support
The CSG2 supports the use of armed event triggers to provide the following roaming features in a
Gx-enabled network:
Dynamic blocking of subscriber traffic, of a service, or of a change in the service-level Qos when a
subscriber roams. The PCRF might also indicate that the CSG2 is to continue forwarding traffic
without blocking or modifying any QoS.
Blocking the establishment of the PDP context, or of traffic for specific DGRs or services when a
subscriber roams.
Policy reauthorization.
The CSG2 supports triggers for the following per-user 3GPP events:
SGSN_CHANGE (0)
RAT_CHANGE (2)
PLMN_CHANGE (4)
IP_CAN_CHANGE (7)
The CSG2 supports triggers for the following per-PDP context 3GPP events:
QOS_CHANGE (1)
TFT_CHANGE (3)
LOSS_OF_BEARER (5)
RECOVERY_OF_BEARER (6)
QOS_CHANGE_EXCEEDING_AUTHORIZATION (11)
Cisco Content Services Gateway - 2nd Generation Release 3.5 Installation and Configuration Guide
OL-19290-02
10-7
Chapter 10
Configuring Gx Support
The PCRF specifies the maximum DGR volume usage in an armed volume trigger. When a
subscriber passes traffic that matches a DGR, and the IP byte volume (uplink plus downlink)
associated with the DGR equals or exceeds the trigger value, the CSG2 reports the usage for the
DGR to the PCRF in a CCR and disables the trigger. The PCRF can re-arm the trigger in the CCA.
The PCRF specifies the maximum DGR duration an armed time duration trigger. When a subscriber
passes traffic that matches a DGR, the CSG2 notes the timestamp of the first packet. Each time the
CSG2 processes another packet, it compares the timestamp to that of the first packet. If the
difference between the two timestamps exceeds the duration trigger, the CSG2 reports the usage for
the DGR to the PCRF in a CCR and disables the trigger. The PCRF can re-arm the trigger in the
CCA.
Cisco Content Services Gateway - 2nd Generation Release 3.5 Installation and Configuration Guide
10-8
OL-19290-02
Chapter 10
Configuring Gx Support
Secondary PDP Context Activation
Report the failed PCRF in BMA CDRs and quota server messages
To define PCRF failure handling for the CSG2, enter the following command in global configuration
mode:
Command
Purpose
(Optional) Defines the actions that the CSG2 is to take for a PCC user if
the PCRF fails when the user session is activated.
continueCreate the CSG2 User Table entry for the PCC user and
forward the RADIUS Accounting Start request.
terminateDo not create the CSG2 User Table entry for the PCC
user and do not forward the RADIUS Accounting Start request. This
is the default setting.
The CSG2 applies the already provisioned per-user rules to the flows.
The CSG2 reports the timed-out PCRF in BMA CDRs and quota server messages.
Cisco Content Services Gateway - 2nd Generation Release 3.5 Installation and Configuration Guide
OL-19290-02
10-9
Chapter 10
Configuring Gx Support
Restrictions for Gx
To define PCRF timeout handling for the CSG2, enter the following command in global configuration
mode:
Command
Purpose
(Optional) Defines the actions that the CSG2 is to take for a PCC user if
the PCRF times out when the user session is activated.
continueCreate the CSG2 User Table entry for the PCC user and
forward the RADIUS Accounting Start request.
terminateDo not create the CSG2 User Table entry for the PCC
user and do not forward the RADIUS Accounting Start request. This
is the default setting.
Restrictions for Gx
For Gx, the CSG2 imposes the following restrictions:
Gx is supported for only Internet Protocol version 4 (IPv4) packet data protocol (PDP) types. It is
not supported for Internet Protocol version 6 (IPv6), Point-to-Point Protocol (PPP) PDP, or PPP
regeneration (PPP-Regen) types.
In a Gx charging rule, the flow descriptions in both the uplink and downlink directions must map to
the same service.
Provisioning of charging gateways (BMAs, quota servers, and so on) is not supported.
Per-rule QoS enforcement is not supported. Instead, the PCRF can specify service-level QoS.
If a global content update results in changed parameters, the CSG2 closes all open transactions and
sessions associated with the content.
Only one external preloading server can be active at any given time.
If the CSG2 receives a flow before it receives per-user PCC rules from PCRF, the CSG2 matches the
flow against existing CSG2 contents.
Preloaded policy objects must not reference CLI-configured objects, and vice versa. For example, a
preloaded billing plan must not reference a CLI-configured service.
You cannot use preloading to modify a CLI-configured object, and you cannot use the CLI to modify
a preloaded policy object.
Cisco Content Services Gateway - 2nd Generation Release 3.5 Installation and Configuration Guide
10-10
OL-19290-02