Credit Control Configuration: Operation Directions

Credit Control Configuration
OPERATION DIRECTIONS
55/1543-AXB 250 10/4 Uen L4

Copyright
© Ericsson AB 2008-2011. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design, and manufacturing. Ericsson
shall have no liability for any errors or damage of any kind resulting from the
use of this document.
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

Contents
Contents
1 Introduction 1
1.1 Scope 1
1.2 Target Groups 1
2 Enabling Credit Control 1

2.1 Activating Licensed Features 2
2.2 Selecting the Gy+ or Gy Interface 2
2.3 Associate a DAS with a Credit Control Profile 3
2.3.1 Configuring an Additional Allowed DAS 4
2.4 Associating a Credit Control Profile with a User Category 4
3 Configuring Charging Characteristics Query 4
4 Configuring Credit Control Sessions 5

4.1 Configuring Optional Message Attributes 5
4.1.1 Excluding the GGSN PLMN 5
4.1.2 Excluding the User PLMN 6
4.1.3 Configuring the APN Type 6
4.1.4 Configuring the PDP Context Type 6
4.1.5 Configuring the Default Trigger Format 6
4.1.6 Configuring the Service Identifier included in the MSCC
AVP 6
4.1.7 Including the PS-Previous-Information AVP in CCR
Messages 7
4.1.8 Configuring Total Usage Reporting 7
4.2 Disabling Session Creation On PDP Context Activation 8
4.3 Disabling Preemptive Quota from the OCS 8
4.4 Configuring the Failure Action 8
4.4.1 Configuring the Continue Options 8
4.4.2 Configuring Failure Handling 9
4.5 Configuring Single MSCC in CCR 9
4.6 Configuring Credit Session Termination per Result Code in
CCA Messages 10
4.6.1 Configuring Sending of Final Report with CCR-Finals 10
4.6.2 Configuring Gn Cause Code 11
4.6.3 Configuring Termination Action 11
5 Configuring Quota Reservation and Reporting 12

5.1 Configuring Quota Holding Time 13
5.2 Configuring Reporting of Exceeding Quota 13
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

5.3 Configuring Packet Handling Pending Quota 13

5.3.1 Configuring the Number of Packets to Buffer 14
5.3.2 Configuring Number of Packets to Pass 14
5.3.3 Configuring all Packets to Drop 15
5.4 Configuring Free Services 15
5.5 Configuring Default Quota Values 15
5.6 Configuring Error Result Codes at MSCC-Level 16
5.6.1 Configuring the Sending of Final Reports 16
5.6.2 Configuring Handling of the Ongoing Reported Period 17
5.6.3 Configuring Termination Action 18
5.7 Configuring GGSN-Initiated Update 20
5.8 Configuring User Quarantine Timer 20
6 Configuring Redirection Parameters 21
7 Configuring Alarms 21
Reference List 23
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

Enabling Credit Control
1 Introduction
This document describes configuration of the online credit control functions

for Service Aware Charging and Control (SACC) in the Gateway GPRS
Support Node (GGSN) for Global System for Mobile communication (GSM) and
Wideband Code Division Multiple Access (WCDMA) systems.
1.1 Scope
This document covers the following issues:
• Enabling credit control
• Configuring credit control sessions
• Configuring quota reservation and reporting
• Configuring redirection parameters
• Configuring alarms
For an overview of credit control, see Credit Control.
Note: This document applies for the SACC solution.
1.2 Target Groups

This document is intended for personnel performing configuration of the GGSN.
2 Enabling Credit Control
To enable SACC credit control in the GGSN the following mandatory actions
must be taken:
• Activate the Gy+ real-time charging license
• Select the Gy+ or Gy interface
• Configure a Diameter Application System (DAS) for the Ro application,

see Diameter Configuration.
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 1

• Associate a DAS with the credit control profile
• Associate the credit control profile with a user category
The following sections describes these actions.
2.1 Activating Licensed Features

Optional licensed features in the GGSN are turned off by default. In order to
employ these features in the GGSN, licenses must be purchased from Ericsson.
For information on how to purchase licenses and enable licensed features, see
Software License Management or contact your local Ericsson support.
2.2 Selecting the Gy+ or Gy Interface

To configure a credit control profile for credit control communication over the
Gy+ interface, include one of the following statements, depending on which
service context is desired (Ericsson Gy v1 or Ericsson Gy v2). The selected
service context determines which AVPs are included in the Gy+ specific
Diameter messages exchanged between the GGSN and the Online Charging
System (OCS). For details, see Gy+ Interface Description.
Gy+ interface using Ericsson Gy v1, include the following statement:
[edit services ggsn apn apn-name service-based-charging \

credit-control]
ro-profile profile-id {
service-context-id v1.gy.ggsn@ericsson.com;
}
Gy+ interface using Ericsson Gy v2, include the following statement:
[edit services ggsn apn apn-name service-based-

charging credit-control]
service-context-id v2.gy.ggsn@ericsson.com;
}
To configure a credit control profile for credit control communication over the Gy
interface, include one of the following statements, depending on which service
context is desired (3GPP Gy R6 or 3GPP Gy R8). The selected service context
determines which AVPs are included in the Gy specific Diameter messages
exchanged between the GGSN and the OCS. For details, see Gy+ Interface
Description.
Gy interface using 3GPP Gy R6, include the following statement:
2 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

Enabling Credit Control

service-context-id 6.32251@3gpp.org;
}
Gy interface using 3GPP Gy R8, include the following statement:

}
Optionally, free-form text may be configured for use as an alias for any of the
four predefined service-context-id values listed above. When used, such
a free-form service-context-id value replaces the selected predefined
service-context-id for the given APN in Credit Control Request (CCR)
messages sent to the OCS.
The free-form text can consist of up to 80 characters.
To configure a free-form service-context-id and associate it

with a predefined service-context-id for a given APN, use the
<ccr-context-id> keyword. In the following example, the free-form text is
myalias@ericsson.com and it is associated with the predefined Gy interface
value 8.32251@3gpp.org for apn1.com.
[edit services ggsn apn apn1.com service-based-charging \

credit-control]
[edit services ggsn apn apn1.com service-based-charging \

credit-control]
ccr-context-id myalias@ericsson.com;
Example 1 Configuring a free-form service context ID
2.3 Associate a DAS with a Credit Control Profile

To associate a DAS with a credit control profile, include the following statement:
[edit services ggsn apn apn-name service-based-charging

credit-control ro-profile profile-id]
diameter-application-system diameter-application-system;
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 3

In order to associate a DAS with the credit control profile, the DAS must be
previously configured in the GGSN, see Diameter Configuration.
Additional DASs allowed for the profile may also be configured. Additional
DASs should be configured if the DAS is received over the Gx+ interface.
2.3.1 Configuring an Additional Allowed DAS

To configure one or several additional DASs allowed for a credit control profile,
include the following statement:

additional-allowed-das [ diameter-application-system ];
2.4 Associating a Credit Control Profile with a User

Category
Associating a credit control profile with a user category requires PDP context
blocking, see Delete and Modify APNs.
To associate a credit control profile with a user category, include the following
statement:
[edit services ggsn apn apn-name user-category

category category-id]
credit-control-ro-profile credit-control-ro-profile;
The profile associated with a user category must be a configured according to

Section 2.3 on page 3.
The user category and the rule space must be configured according to the
instructions for enabling Packet Inspection and Service Classification (PISC)
in PISC Configuration.
3 Configuring Charging Characteristics Query
The following section describe the charging characteristics query. In case

no charging characteristics have been received over the Gn interface, a
query to the OCS may be used to select charging characteristics for a user.
SeeCDR-Based Charging. To configure the OCS query, include the following
statement:
4 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

Configuring Credit Control Sessions
[edit services ggsn apn-name service-based-charging

credit-control]
query-ocs {
credit-control-user {
cc charging-characteristics;
}
no-credit-control-user {
}
no-valid-answer {
}
}
The charging characteristics defined under the credit-control-user option

is used when the OCS enables credit control. The charging characteristics
defined under the no-credit-control-user option is used when the
OCS disables credit control. The charging characteristics defined under the
no-valid-answer option is used when no valid answer is received from
the OCS.
4 Configuring Credit Control Sessions
The following sections describe configurable parameters related to the credit

control sessions.
4.1 Configuring Optional Message Attributes

Three of the Attribute Value Pairs (AVPs) included in credit control requests
are configurable.
4.1.1 Excluding the GGSN PLMN

To configure the GGSN not to include the GGSN Public Land Mobile Network
(PLMN) identifier in credit control request messages, include the following
statement:

credit-control ro-profile profile-id ccr-avp]
no-ggsn-plmn-id;
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 5

4.1.2 Excluding the User PLMN
To configure the GGSN not to include the user PLMN identifier in credit control
request messages, include the following statement:

no-user-plmn-id;
4.1.3 Configuring the APN Type
To configure the GGSN to include the Gn Access Point Name (APN) instead of
the Gi APN in the AVP Called-Station-Id, include the following statement:

apn-type {
gn-apn;
}
4.1.4 Configuring the PDP Context Type

To configure the GGSN not to send PDP context type information included in
the PS-information AVP to the OCS, include the following statement:

no-pdp-context-type {
}
4.1.5 Configuring the Default Trigger Format
To configure the GGSN to send a trigger-type AVP in CCR messages

instead of the default trigger format trigger. This configuration takes only
effect when there is not any trigger ever received from OCS for this Rating
Group (RG). The configuring include the following statement:

default-trigger-format {
trigger-type;
}
4.1.6 Configuring the Service Identifier included in the MSCC AVP

To configure the GGSN to include a Service-Identifier AVP for each
MSCC AVP when allocating quota, include the following statement:
6 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03


ccr-avp {
service-identifier \
(use-rating-group | default-service-identifier SI);
}
As default, the Service-Identifier AVP is not included in the MSCC AVP.
The SI value is a fixed integer. It is not related to service identifiers used on

GGSN. This configured value will only be used in the MSCC AVP. The purpose
is to adapt the interface for when a customer requires an SI-field in the MSCC
AVP. This configuration is not needed otherwise.
4.1.7 Including the PS-Previous-Information AVP in CCR Messages

To configure the GGSN to include the PS-Previous-Information AVP,
within the Service Information AVP in a CCR at rating condition change,
include the following statement:
ps-previous-information;
As default, the PS-Previous-Information AVP is not included in the CCR

message.
4.1.8 Configuring Total Usage Reporting

To configure any of the CCR AVPs to be sent to the OCS, include the following
statements respectively:
granted-service-unit;
cumulative-used-service-unit;
service-start-timestamp;
credit-instance-id;As default, none of the AVPs above (the
Granted-Service-Unit AVP, Cumulative-Used-Service-Unit AVP,
Service-Start-Timestamp AVP or Credit-Instance-Id AVP) are
included in the CCR message.
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 7

4.2 Disabling Session Creation On PDP Context Activation

To configure the GGSN not to create credit control sessions at PDP context
creation, include the following statement:

no-initiate-session-on-activation;
4.3 Disabling Preemptive Quota from the OCS

To configure the GGSN not to accept preemptive quota from the OCS, include
the following statement:

no-preemptive-reservation;
4.4 Configuring the Failure Action

To configure the OCS communication failure action, include the following
statement:

credit-control ro-profile profile-id failure]
failure-action (continue | terminate | retry-
and-terminate);
Only one of the three available failure actions can be configured for each
credit control profile.
4.4.1 Configuring the Continue Options

If the configured failure action is continue, it is possible to configure two
parameters:
• Timeout
• Prevention of reestablishment
The default timeout value is 1800 seconds. To configure the duration of the
traffic without credit control, include the following statement:

credit-control ro-profile profile-id failure continue]
timeout seconds;
8 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

To configure the GGSN to not attempt reestablishement, include the following

statement:

credit-control ro-profile profile-id failure continue]
no-reestablish;
Note: This parameter overrides any timeout value.
4.4.2 Configuring Failure Handling

For instructions for the configuration of failover handling for direct access, refer
to Credit Control.
For agent access, the default failure handling type is agent-retry. With
agent-retry, the GGSN attempts to send the message to another agent if
several agents are configured.
To prevent the GGSN from resending to another agent and to configure an

optional peer-timeout during which traffic can be allowed, include the
following statement:
[edit services ggsn service-based-charging diameter-app

lication-system das-id agent-retry] no-session
[edit services ggsn service-based-charging diameter-applic
ation-system das-id agent-retry] peer-timeout timeout;
The value range for peer-timeout is 1–60, indicating seconds. The value of
peer-timeout must be greater than the value of das-timeout.
The no-session flag can only be set if access-type is agent. The parameter
peer-timeout can only be used if no-session is configured.
4.5 Configuring Single MSCC in CCR

To configure the use of a single MSCC AVP in CCR messages, include the

ccr-avp {
single-mscc;
}
As default, the single MSCC AVP in the CCR message feature is not enabled.
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 9

4.6 Configuring Credit Session Termination per Result

Code in CCA Messages
To configure session termination when receiving certain error result codes in
a CCA message, follow the instructions in the sections below. A set of error
result codes, specified as a list of ranges, can be configured to initiate session
terminations. Result codes within the range 4000 to 5999 can be configured
as error result codes. The following can be configured for each session
termination:
• Sending of a CCR-Final with the reporting-reason AVP set to Final
• Gn cause code included in PDP context reject responses
• Termination action
Note: If the use of a single MSCC AVP is configured, the termination of a

credit control session is performed in several steps. One CCR-Update
is sent for each RG that needs to be final-reported. One CCR-Update
includes only one MSCC. Finally, a CCR-Final is sent without MSCC.
4.6.1 Configuring Sending of Final Report with CCR-Finals
To configure the GGSN to send or not to send a CCR-Final with the

reporting-reason AVP set to Final for all active rating groups, include the
session-termination {
id {
error-result-codes [error-result-code];
final-report (send | not-send);
}
}
By default, the GGSN does not send any CCR-Final with the reporting-reason
AVP set to Final when an error result code is received. In the default scenario,
the final reporting of the MSCCs occurs in the CCR-Final.
An exception is made for result codes DIAMETER_END_USER_

SERVICE_DENIED, DIAMETER_CREDIT_LIMIT_REACHED and
DIAMETER_AUTHORIZATION_REJECTED, where a CCR-Final with the
reporting-reason AVP set to Final is sent if the failure occurs during a
CCA-Update.
Note: It is not possible to configure the GGSN to send a Final Report message
for the error result codes DIAMETER_UNKNOWN_SESSION_ID and
DIAMETER_USER_UNKNOWN.
10 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

4.6.2 Configuring Gn Cause Code
It is possible to configure the rejection cause code sent over the Gn interface
in a PDP context reject response. Possible cause values are 129-176 and
192-240. The default cause code is User Authentication Failed (209).
To configure the Gn cause code, include the following statement:

id {
error-result-code [error-result-code];
gn-cause-code code;
}
}
4.6.3 Configuring Termination Action
When receiving an error result code within a CCA-Initial message, it is possible

to configure the GGSN to either reject the PDP context at activation or apply
credit control failure handling, see Section 4.4 on page 8. If, instead, the
error result code is received within a CCA-Update message, it is possible to
configure either termination of the credit session followed by PDP context
termination or apply credit control failure handling. To configure the termination
action, include the following statement:

id {
error-result-code [error-result-code];
termination-action (terminate | failure-action);
}
}
Table 1 shows the default behavior when the termination action is not
configured.
Table 1 Default Behavior of the Termination Action.

Result Code Value CCA-Initial CCA-Update CCA-Final
DIAMETER_E 4010 Reject Terminate Terminate
ND_USER_SE
RVICE_DENI
ED
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 11

Result Code Value CCA-Initial CCA-Update CCA-Final

DIAMETER_C 4011 Continue Continue Terminate
REDIT_CONT
ROL_NOT_AP
PLICABLE
DIAMETER_C 4012 Reject Terminate Terminate
REDIT_LIMI
T_REACHED
Transient 4xxx Credit Cont Credit Cont Terminate
failure (other) rol Failure rol Failure
Handling Handling
DIAMETER_U 5002 Credit Cont Terminate Terminate
NKNOWN_SES rol Failure
SION_ID Handling
DIAMETER_A 5003 Reject Terminate Terminate
UTHORIZATI
ON_REJECTE
D
DIAMETER_I 5004 Credit Cont Credit Cont Terminate
NVALID_AVP rol Failure rol Failure
_VALUE Handling Handling
DIAMETER_U 5030 Reject Terminate Terminate
SER_UNKNOW
N
Permanent 5xxx Credit Cont Credit Cont Terminate
failure (other) rol Failure rol Failure
Handling Handling
5 Configuring Quota Reservation and

Reporting
The following sections describes configuration of parameters related to quota

reservation and reporting.
12 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

Configuring Quota Reservation and Reporting
5.1 Configuring Quota Holding Time

The Quota Holding Time (QHT) may be configured either to a number of
seconds, or to infinity. The default QHT is 180 seconds. The configurable
range is 5 to 86,400 seconds.
To configure the QHT to a number of seconds, include the following statement:
[edit services ggsn rule-space rule-space-nam

e quota-handling]
holding-time-period seconds;
To configure the QHT to infinity, include the following statement:

e quota-handling]
holding-time-infinity;
5.2 Configuring Reporting of Exceeding Quota

The GGSN can be configured to limit reported usage when the granted quotas
are exceeded. By default, this is turned off.
To configure the GGSN to limit reported usage, include the following statement:
[edit services ggsn rule-space] rule-space-name

quota-handling quota-reporting report-limit-granted;
The GGSN can be configured not to limit the reported usage in the final report.
This requires that report-limit-granted is configured.
To configure the GGSN not to limit reported usage in the final report, include
[edit services ggsn rule-space] rule-space-name

quota-handling quota-reporting no-final-report-limit;
5.3 Configuring Packet Handling Pending Quota

How to handle packets pending quota reservation is configured per ACR. The
default behavior is to allow all packets to pass. Three alternative methods
are available:
• Buffer a configured number of packets, then drop.
This method is recommended if redirection controlled by the OCS is used

for the service.
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 13

Note: Buffering is not supported when Service Classification without

Packet Inspection is configured.
• Allow a configured number of packets to pass, then drop.
Note: When Service Classification without Packet Inspection is configured

at APN level, and at the same time is configured at rule space level
to buffer or limit passage of packets during an OCS interrogation, a
maximum of 254 packets will be allowed to pass while waiting for
the OCS to respond to an initial credit request for a credit instance.
• Drop all packets pending authorization.
Note: An ACR may only be configured for one of these methods.
5.3.1 Configuring the Number of Packets to Buffer

To configure the GGSN to buffer a number of packets classified into specified
ACRs, include the following statement:
[edit services ggsn rule-space rule-space-name]

buffer-pending-authorization {
access-control-rule [ ACR-id ];
buffer-limit packets;
}
If the mapping between Service Data Flow ID (SDF-ID) and ACR is not
configured, the SDF-ID is used as ACR-id.
The default limit for the number of packets to buffer is 5. The configurable
range is 0 to 100.
For more information about the mapping between SDF-ID and ACR, see PISC
Configuration
5.3.2 Configuring Number of Packets to Pass

To configure the GGSN to allow a number of packets classified into specified
ACRs, include the following statement:

pass-through-pending-authorization {
access-control-rule [ ACR-id ];
pass-through-limit packets;
}
If the mapping between SDF-ID and ACR is not configured, the SDF-ID is
used as ACR-id.
The default limit for the number of packets allowed to pass is 5. The
configurable range is 1 to 254.
14 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

Configuration
5.3.3 Configuring all Packets to Drop

To configure the GGSN to drop packets classified into specified ACRs, include

drop-pending-authorization [ ACR-id ];
If the mapping between SDF-ID and ACR is not configured, the SDF-ID is
used as ACR-id.
Configuration
5.4 Configuring Free Services

To configure free services, include the following statement:

e quota-handling]
no-quota-handling [ rating-group ];
5.5 Configuring Default Quota Values

Default quota values can be configured and thus included at the
Multiple-Service-Credit-Control (MSCC) AVP level in the
Requested-Service-Unit AVP in CCRs sent to the OCS.
To configure a default volume quota, include the following statement:
[edit services ggsn rule-space]

"rule-space-name quota-handling service-unit
volume octets";
The value range is 0-18,446,744,073,709,551,615 octets.
To configure a default unit quota, include the following statement:

"rule-space-name quota-handling service-unit unit units";
The value range is 0-18,446,744,073,709,551,615 units.
To configure a default time quota, include the following statement:
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 15

"rule-space-name quota-handling \
service-unit time seconds";
The value range is 0-4294967295 seconds.
Example
To configure a default volume quota of 100 octets, a default time quota of 200
seconds, and a default unit quota of 300 units for the rs1 rule space, include
the following statements:
user@host> set services ggsn rule-space1 "rs1 quota-handling \

service-unit volume 100"
service-unit time 200"
service-unit unit 300"
5.6 Configuring Error Result Codes at MSCC-Level

It is possible to configure the GGSN to handle credit instances depending on
error result codes received at MSCC-level. Result codes within the range 4000
to 5999 can be configured as error result codes.
Note: Result codes 3xxx (Protocol errors) are not configurable.
5.6.1 Configuring the Sending of Final Reports

To configure the GGSN to send or not to send a final report if an initiate or
update answer is received from the OCS with an error result code, include
[set services ggsn rule-space rule-space-name]

quota-handling {
quota-termination {
id {
final-report (send | not-send);
}
}
}
Table 2 shows the default behavior when sending of final reports is not
configured.
16 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

Table 2 Default Behavior when Sending of Final Reports is not Configured.

Result Code Value MSCC -Initial MSCC -Update
DIAMETER_END 4010 Do not send Send report
_USER_SERVIC report
E_DENIED
DIAMETER_CRE 4011 Do not send Do not send
DIT_CONTROL_ report report
NOT_APPLICAB
LE
DIAMETER_CRE 4012 Do not send Send report
DIT_LIMIT_RE report
ACHED
Transient failure 4xxx Do not send Do not send
(other) report report
DIAMETER_AUT 5003 Do not send Do not send
HORIZATION_R report report
EJECTED
DIAMETER_RAT 5031 Do not send Do not send
ING_FAILED report report
Permanent 5xxx Do not send Do not send
failure (other) report report
5.6.2 Configuring Handling of the Ongoing Reported Period
To configure whether the GGSN completes or interrupts an ongoing reported

resolution period, include the following statement:

quota-handling {
quota-termination {
id {
ongoing-reported-period (allow | not-allow);
}
}
}
Table 3 shows the default behavior when handling of the ongoing reported
period is not configured.
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 17

Table 3 Default Behavior for When Handling of the Ongoing Reported Period
is not Configured.
Result Code Value MSCC -Update
DIAMETER_END_USER 4010 Allow reported period to
_SERVICE_DENIED complete
DIAMETER_CREDIT_C 4011 Do not allow reported
ONTROL_NOT_APPLIC period to complete
ABLE
DIAMETER_CREDIT_L 4012 Allow reported period to
IMIT_REACHED complete
Transient failure (other) 4xxx Do not allow reported
period to complete
DIAMETER_AUTHORIZ 5003 Do not allow reported
ATION_REJECTED period to complete
DIAMETER_RATING_F 5031 Do not allow reported
AILED period to complete
Permanent failure 5xxx Do not allow reported
(other) period to complete
5.6.3 Configuring Termination Action

To configure the GGSN whether to block Rating Groups (RGs) when an error
result code is received at MSCC-level, include the following statement. The
possible configuration options are described below:
services-not-allowed
The GGSN drops all the packets received on this RG
until the service is allowed again.
activate-denied-timer
The GGSN activates the user-denied-time when the
error code is received. The GGSN drops the packets
and does not send any credit request to the OCS until
the timer times out. The GGSN continues sending credit
request for this RG when the user-denied-time times out
and traffic is detected again.
18 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

no-activate-denied-timer
The GGSN sends a credit request when any packet
is received on the RG after the error code has been
received.
Note: It results in a high traffic load on the Gy interface

if the subscriber keeps trying to access the
service. Therefore this configuration is not
recommended.

quota-handling {
quota-termination {
id {
termination-action (activate-denied-timer | \
no-activate-denied-timer | services-not-allowed);
}
}
}
Note: It is not possible to configure a termination action for the error result
code DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE as offline
charging is applied to the rating group.
Table 4 shows the default behavior when the termination action is not
configured.
Table 4 Default Behavior of Termination Action.

Result Code Value MSCC -Initial MSCC-Update
DIAMETER_END 4010 Active denied Active denied
_USER_SERVIC timer timer
E_DENIED
DIAMETER_CRE 4011 No control No control
DIT_CONTROL_ (offline) (offline)
NOT_APPLICAB
LE
DIAMETER_CRE 4012 Active denied Active denied
DIT_LIMIT_RE timer timer
ACHED
Transient failure 4xxx Active denied Active denied
(other) timer timer
DIAMETER_AUT 5003 Services not Services not
HORIZATION_R allowed allowed
EJECTED
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 19

Result Code Value MSCC -Initial MSCC-Update

DIAMETER_RAT 5031 Services not Services not
ING_FAILED allowed allowed
Permanent 5xxx Active denied Active denied
failure (other) timer timer
5.7 Configuring GGSN-Initiated Update

It is possible to configure the GGSN to initiate a quota update for the following
reasons:
• A change of sgsn-address
• A change of sgsn-plmn-id
• A change of rat-type
• A change of qos (not applicable for event-based charging)
• A change of lac
• A change of cell-id
By default, an update is not triggered by any of these reasons.
To configure one or more reasons for quota update, include the following
statement:
[edit services ggsn rule-space \

rule-space-name quota-handling]
re-authorization-triggers {
qos;
rat-type;
sgsn-address;
sgsn-plmn-id;
lac
cell-id
}
5.8 Configuring User Quarantine Timer

The default value of the user quarantine timer is 180 seconds. The configurable
range is 5 to 86,400 seconds.
To configure the user quarantine timer, include the following statement:
[edit services ggsn rule-space \

rule-space-name quota-handling]
20 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

Configuring Alarms
user-denied-time seconds;
6 Configuring Redirection Parameters
Before redirection parameters can be configured, traffic redirection must

be enabled in the GGSN. For information on how to enable redirection for a
service, see Traffic Redirection Configuration.
To configure the GGSN to append the request Uniform Resource Identifier

(URI) to the redirect URI, include the following statement:

credit-control ro-profile profile-id redirect]
append-uri;
To configure the GGSN to suppress URI formatting, include the following

statement:

credit-control ro-profile profile-id redirect]
no-uri-formatting;
For information on how to configure service denied redirection, see Traffic

Redirection Configuration.
7 Configuring Alarms
It is possible to configure if the following alarms related to credit control are

active or inactive:
• no-invalid-service-context-id-ccr
• invalid-rating-group-ccr (default: inactive)
• no-invalid-rating-group-cca
• no-invalid-cca
• no-invalid-rule-space-cca
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 21

• error-indication-cca [ error-code-range ] (default: inactive)
To toggle the generation of one or more of these alarms, include the following
statements:
[edit services ggsn fault-management alarm service-based-charging]

no-invalid-service-context-id-ccr;
invalid-rating-group-ccr;
no-invalid-rating-group-cca;
no-invalid-cca;
no-invalid-rule-space-cca;
error-indication-cca {
error-codes [ error-codes ]
}
For more information on Diameter result codes indicating error used in the
error-indication-cca statement, see SoC for IETF RFC 3588.
22 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

Reference List
Reference List
Ericsson Documents
[1] CDR-Based Charging

TECHNICAL PRODUCT DESCRIPTION, 9/221 02-AXB 250 10/4
[2] Credit Control

[3] Delete and Modify APNs

OPERATION DIRECTIONS, 12/1543-AXB 250 10/4
[4] Diameter Configuration

[5] Gy+ Interface Description

DESCRIPTION, 6/1551-AXB 250 10/4
[6] PISC Configuration

[7] Software License Management

[8] Traffic Redirection Configuration

Statements of Compliance
[9] SoC for IETF RFC 3588

Statement of compliance, Diameter Base Protocol RFC 3588, 1/174
02-CSA 113 35/4
55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 23

Credit Control Configuration: Operation Directions

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Credit Control Configuration: Operation Directions

Uploaded by

Copyright:

Available Formats

Credit Control Configuration

55/1543-AXB 250 10/4 Uen L4

© Ericsson AB 2008-2011. All rights reserved. No part of this document may be

55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

2 Enabling Credit Control 1

3 Configuring Charging Characteristics Query 4

4 Configuring Credit Control Sessions 5

5 Configuring Quota Reservation and Reporting 12

55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

5.3 Configuring Packet Handling Pending Quota 13

6 Configuring Redirection Parameters 21

55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

This document describes configuration of the online credit control functions

• Enabling credit control

• Configuring credit control sessions

• Configuring quota reservation and reporting

• Configuring redirection parameters

For an overview of credit control, see Credit Control.

Note: This document applies for the SACC solution.

1.2 Target Groups

2 Enabling Credit Control

• Activate the Gy+ real-time charging license

• Select the Gy+ or Gy interface

• Configure a Diameter Application System (DAS) for the Ro application,

55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 1

• Associate a DAS with the credit control profile

• Associate the credit control profile with a user category

The following sections describes these actions.

2.1 Activating Licensed Features

2.2 Selecting the Gy+ or Gy Interface

[edit services ggsn apn apn-name service-based-charging \

[edit services ggsn apn apn-name service-based-

2 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

[edit services ggsn apn apn-name service-based-

[edit services ggsn apn apn-name service-based-

The free-form text can consist of up to 80 characters.

To configure a free-form service-context-id and associate it

[edit services ggsn apn apn1.com service-based-charging \

[edit services ggsn apn apn1.com service-based-charging \

2.3 Associate a DAS with a Credit Control Profile

[edit services ggsn apn apn-name service-based-charging

55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 3

2.3.1 Configuring an Additional Allowed DAS

[edit services ggsn apn apn-name service-based-charging

2.4 Associating a Credit Control Profile with a User

[edit services ggsn apn apn-name user-category

The profile associated with a user category must be a configured according to

3 Configuring Charging Characteristics Query

The following section describe the charging characteristics query. In case

4 55/1543-AXB 250 10/4 Uen L4 | 2011-02-03

[edit services ggsn apn-name service-based-charging

The charging characteristics defined under the credit-control-user option

4 Configuring Credit Control Sessions

The following sections describe configurable parameters related to the credit

4.1 Configuring Optional Message Attributes

4.1.1 Excluding the GGSN PLMN

[edit services ggsn apn apn-name service-based-charging

55/1543-AXB 250 10/4 Uen L4 | 2011-02-03 5

4.1.2 Excluding the User PLMN

[edit services ggsn apn apn-name service-based-charging

4.1.3 Configuring the APN Type

[edit services ggsn apn apn-name service-based-charging

4.1.4 Configuring the PDP Context Type