Name
|
The
client name used to reference this particular client in the service
configuration object.
|
Realm
Pattern
|
The
pattern that peer realm name should match in order for this diameter client to
be used. The pattern needs to follow the standard Java regular expression
syntax.
The
first choice for Realm Pattern value should always be the exact peer realm
name.
|
Add
Subscriber Id
|
Adds
Subscription-Id grouped AVP in Gx CCA-i message with one of the following
Subscription-Id-Type AVP value and Subscription-Id-Data AVP value depending on
the selection. The values will be copied from the incoming Gx CCR-i message if
available.
|
Rx PCC
Rule Flow Direction Behavior
|
Controls how the Flow-Direction AVP value under Flow-Information
grouped AVP is derived. This option is used for Rx dedicated bearers.
-
Derive Flow-Direction (default): Flow-Direction AVP is derived
based on Flow-Description AVP value and Flow-Status AVP value. This option is
used in case the PCEF advertised support for Rel10 feature under
Supported-Features AVP.
-
3GPP Gx Rel11 Compliant: Flow-Direction AVP is derived as per
3GPP TS 29.212 v11
-
Exclude Flow-Direction: Flow-Direction AVP is not set.
|
Emergency Called Station Ids
|
List
of APNs that are allowed to initiate IMS emergency calls. For more information,
see
CPS
Mobile Configuration Guide.
|
Sending Delayed Message Wait Time Ms
|
This
parameter specifies the amount of time the Gx RAR will be delayed after Gx CCA
is sent when "Gx Triggered Session-Release-Cause in RAR" is enabled.
In
case of multiple Media-Component-Descriptions being received in an AAR message
by CPS, where one of them is rejected after evaluating for Gx Authorization,
CPS sends a successful AAA for the accepted Media-Component-Descriptions and
also creates a scheduled event for sending a delayed Rx RAR for rejected Media
component.
This
Gx RAR is sent to AF based on Sending Delayed Message Wait Time configured.
Default value is 500 milliseconds.
|
Control Session Lifecycle
|
Decides if all the other sessions bound to the current Gx
session get terminated upon Gx session termination.
Default value is checked.
|
Remove
Realm In User ID Mapping
|
When
enabled removes the realm from the NAI (if present) before attempting to load
the session by username.
Default value is not checked.
|
Exclude Sponsor Identity AVP
|
When
enabled it does not add the Sponsor-Identity AVP to the
Charging-Rule-Definition grouped AVP. This option is used only in case the PCEF
advertised support for SponsoredConnectivity feature under Supported-Features
AVP.
Default value is not checked.
|
Load
By Imsi
|
When
enabled attempts to load the session by IMSI (Subscription-Id-Data AVP value
under Subscription-Id grouped AVP where Subscription-Id-Type AVP value is
END_USER_IMSI (1)).
Default value is not checked.
|
Load
By Nai
|
When
enabled attempts to load the session by NAI (Subscription-Id-Data AVP value
under Subscription-Id grouped AVP where Subscription-Id-Type AVP value is
END_USER_NAI (3)).
Default value is not checked.
|
Load
By Msisdn
|
When
enabled attempts to load the session by MSISDN (Subscription-Id-Data AVP value
under Subscription-Id grouped AVP where Subscription-Id-Type AVP value is
END_USER_E164 (0)).
Default value is not checked.
|
Imsi
Based Nai
|
If
checked, the subscriber is identified by PCRF using "IMSI based NAI", where the
identity is represented in NAI form as specified in RFC 4282 [5], and formatted
as defined in 3GPP TS 23.003 [6], clause 19.3.2. The IMSI based NAI is sent
within the Subscription-Id AVP with the Subscription-Id-Type set to
END_USER_NAI at IP-CAN session establishment.
Default value is unchecked.
|
Load
By Framed Ip
|
When
enabled attempts to load the session by IP v4 address (Framed-IP-Address AVP
value).
Default value is not checked.
|
Load
By Ip V6 Prefix
|
When
enabled attempts to load the session by IP v6 address (Framed-IPv6-Prefix AVP
value).
Default value is not checked.
|
Session Chained
|
When
enabled it does not attempt to terminate the Gx session by sending a Gx RAR to
PCEF.
Default value is not checked.
|
Remove Realm In User Id Mapping
|
If
checked, removes the realm from the NAI (if present) before attempting to load
the session by username. For more details on NAI see RFC 2486.
Default value is unchecked.
|
Exclude Sponsor Identity Avp
|
If
checked, it does not add the Sponsor-Identity AVP to the
Charging-Rule-Definition grouped AVP. This option is used only in case the PCEF
advertised support for SponsoredConnectivity feature under Supported-Features
AVP.
Default value is unchecked.
|
Load
By Called Station Id
|
When
enabled attempts to load the session by IMSI and APN. To effectively use this
option Load By Imsi option needs to be enabled.
|
Re-install Rule on Monitoring Key Change
|
When
enabled attempts to re-install a charging rule in case the only AVP value that
changed for a PreConfiguredRule is the monitoring key value.
Default value is not checked.
|
Limit
with Requested QoS on modification failure
|
If
checked, authorizes bound QoS between retained and calculated QoS after CPS has
received QoS modification failure event from PCEF.
Default value is checked.
|
Enforce Missing Avp
|
Enables CPS to validate missing AVP and send
DIAMETER_MISSING_AVP (5005) result in the answer message.
If
this attribute is unchecked, then CPS will not perform the missing AVP
validation.
Default value is checked.
|
One Gx Rule Per flow
|
This
parameter applies only to the dynamic charging rules over Gx that are generated
by CPS due to the APPLICATION_START event trigger received over the Sd
interface for ADC rules.
When
enabled CPS creates one dynamic charging rule over Gx per flow information
received in the Application-Detection-Info AVP over the Sd interface. CPS also
creates a unique TDF-Application-Identifier over Gx for each of these rules.
So, each generated rule has a unique TDF-Application-Identifier and only one
Flow-Information AVP.
When
disabled CPS generates only one rule per TDF-Application-Identifier received
over the Sd interface. This one rule has all the Flow-Information AVPs. The
TDF-Application-Identifier over Gx is same as over Sd.
Default value is unchecked.
|
Selective Muting
|
When
enabled CPS selectively mutes the flow corresponding to a
TDF-Application-Identifier on dedicated bearer after it receives the first
Application_Start event trigger on the dedicated bearer.
For
default bearer, CPS selectively mutes the flow corresponding to a
TDF-Application-Identifier after it receives the Application_Start event
trigger on default bearer and maximum limit is reached on dedicated bearer.
Note
|
Limit on dedicated bearer is based on a combination of QCI and
ARP limit. This value is configurable in Policy Builder.
|
After
CPS receives Application_Stop event trigger for a specific
TDF-Application-Identifier (with TDF-App-Instance-ID=0), CPS removes that rule
from dedicated bearer and installs the rule on the default bearer and unmutes
all the rules related to that TDF-Application-Identifier on default bearer.
|
Re-Install Predefined Rules on Rulebase Change
|
Indicates whether all
the existing predefined rules that are applicable for the session are
re-installed if there is a Rule-Base change. Select this option if you want all
the predefined rules (that are applicable to the session) to be re-installed if
the Rule-Base changes due to any reason. If unchecked, whenever there is a
Rule-Base change, CPS only notifies the changes (if any) in predefined rules to
PCEF and does not re-install all the existing predefined rules.
Note
|
The rules that are not applicable are removed.
This option does not apply to preconfigured or dynamic
rules from Rx/Sd.
|
Restriction
|
Use this checkbox only in consultation with Cisco
Technical Representative.
|
|
Gx
triggered Session-Release-Cause in RAR
|
When
enabled, any Gx initiated session termination is responded to with a RAR
immediately after CCR/CCA exchange with the PCEF. The RAR contains the
Session-Release-Cause AVP.
When
disabled, any Gx initiated session termination response from the PCRF in the
CCA-U contains the Session-Release-Cause AVP. This is the default behavior.
|
Cisco
Pending Transaction Retry
|
Select to enable Cisco Pending Transaction Retry.
|
Sponsored Profile
|
Allows
for customization of the monitoring key name.
This
option is used only in case the PCEF advertises support for
SponsoredConnectivity feature under Supported-Features AVP.
|
Rx Based QoS Upgrade Of Default Bearer
|
Select to enable Rx based QoS upgrade
|
Count
of Flow Descriptions in one Charging
|
Select to enable Count of Flow Descriptions in one Charging Rule.
|
Max
number of Flow Descriptions on a bearer
|
Defines the maximum number of flows that can be installed on a
default bearer per QCI.
On
receiving the APPLICATION_START event trigger over the Sd interface, CPS
installs the corresponding flows over the Gx interface and QCI maps to that of
the default bearer. Essentially, this is the limit of flows per QCI that CPS
can accept from TDF over the Sd interface. Once this limit is reached, CPS
ignores any more flows received from TDF does not install any rules for those
flows.
Default value is 64.
|
Charging Rule Retry
|
Select to enable Charging Rule Retry Configuration.
|
Redirect Requests
|
CPS
can reject incoming CCR-I messages with DIAMETER_REDIRECT_INDICATION (3006)
error by acting as a redirect agent (RFC 3588). This decision to redirect a
request is configured using an STG or CRD.
CPS
expects the STG or CRD to include a Redirect Request Column (of type True or
False). There is no restriction on the condition that determines the redirect
behavior.
|
Pending Transaction Retry
|
Back
Off Algorithm
|
- Constant_Interval: The
configured retry Interval is used (without any change) for all retry attempts.
- Linear_Interval: Retry
interval is derived by multiplying the attempt number with the retry interval.
This is applicable only when RAR messages are retried due to pending
transactions.
Default value is Constant_Interval.
|
RAR
Retry Interval (MilliSeconds)
|
Retry
time interval (milliseconds) after which same RAR is retried after receipt of
Pending Transactions (4144) Experimental Result code in RAA.
Default value is 1000 milliseconds.
|
Time
(MilliSeconds) to hold CCR-U processing
|
Time
interval (milliseconds) during which CCR-U processing is withheld till pending
RAA is received from PCEF.
Default value is 1000 milliseconds.
|
Time
(MilliSeconds) to wait for CCR-U retry
|
Time
interval (milliseconds) during which CPS should wait for PCEF to initiate a
CCR-U retry after sending a RAA with Pending Transactions (4144) Experimental
Result code.
Default value is 1000 milliseconds.
|
Max
No of additional RAR's to be stored
|
Number of RARs generated during pending transactions situations that need to be
held and retried in sequence. Additional maximum RARs that can be stored is
three. If this value is more that three, Policy Builder displays configuration
violation error message.
Default value is 1. If set to 0, additional RAR's are discarded.
|
Extract Avps
|
Name
|
Enter
a logical name for the extracted AVP. This name will be used in Initiator
conditions and CRD tables to identify the extracted AVP. This is a mandatory
parameter.
|
Avp
Path
|
Enter
the complete AVP path. This is a mandatory parameter.
|
Command Code
|
If
Command Code is specified, CPS attempts to extract the AVPs from only that
command (and skip the rest). This is an optional parameter.
|
Custom Dynamic Rule Name
|
Af
Application Id
|
The
AF-Application-Id for which the QoS values should be applied.
|
Media
type
|
The
Media-Type for which the QoS values should be applied. (Use an Integer value as
per 3GPP specifications).
|
Partial Rule Name
|
Value
matching the current Af Application Id and Media Type values for the current
Media-Sub-Component grouped AVP or "AF" if no match.
|