The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
RequestReject service configuration can be used to send an error code to reject a session during initial attach or update when certain condition (such as, APN-RAT combination) is met. This configuration has two attributes, ErrorCode and IsExperimentalErrorCode and values to these two attributes gets populated using result column of STG (output columns of CRD).
Note | Error-Code is a Number type column and IsExpermentalErrorCode is a Boolean type column. |
CRD table gets evaluated with retrievers/request bindings (such as, APN, RAT-TYPE, Cmd-Code, application-id, Request-Type) done at CRD level and gives ErrorCode and IsExperimentalErrorCode as derived output. Based on this ErrorCode, CPS sends the response message. If no Error-Code is derived, then CPS behaves normally.
CPS logs a counter for each request rejection. For this a new statistics, <InterfaceName>_<RequestType>_policy_driven_rejection_<ResultCode> has been added.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Error Code |
Value of this field is pulled from the CRD output column which is of type Number (need to configure pull value from column to map to a result column of the CRD table), which represents the error code that needs to be sent in response. Default value of Error Code is 0. |
Is Experimental Error Code |
Value of this field is pulled from the CRD output column which is of type Boolean (need to configure pull value from column to map to a result column of the CRD table), which represents how CPS has to send the Error Code in response either through Result-Code AVP or 'Experimental-Result-Code' grouped AVP. Default value is false that means CPS sends an error code in response through Result-Code AVP. |
The ActionBasedOnGxEventTrigger service configuration object allows CPS to make policy decisions based on the following event triggers received over Gx:
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Collapse Dedicated Bearer |
If this value is set to true, then on Default Bearer QoS uplift, a check is done to see if any of the existing dedicated bearers have the same QoS as the uplifted QoS (specifically same QCI and ARP). CPS then installs those rules and flows on the default bearer associated with existing dedicated bearer. This is due to the fact that PGW removes the dedicated bearer when QCI and ARP matches with the default bearer. With the removal of the dedicated bearer all the flows and rules associated with that bearers are removed. |
Evaluate Static Rules |
Reserved for future use. |
Evaluate Qo S Group Rules |
Reserved for future use. |
ADTMAttributeStagePriority configuration object is used to provide stage and priority values for the ADTM (Advanced Dynamic Traffic Management) attribute.
The following table describes the service configuration parameters:
ADTMIMSServiceAction configuration object is used to define IMS service action.
The following table describes the service configuration parameters:
ADTMMogServiceAction configuration object is used to define MOG service action.
The following table describes the service configuration parameters:
ADTMSDServiceAction configuration object is used to define TDF Sd service action.
The following table describes the service configuration parameters:
ADTMSPRBearerAction configuration object is used to define SPR Bearer service action.
The following table describes the service configuration parameters:
The ApnMapping service configuration object pushes the configured Target APN in a CCA-I message by matching the incoming APN in a CCR-I message with the configured source APN.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Source APN |
The APN that will be mapped to the target APN. |
Target APN |
The APN that will be the used instead of the source APN. |
The BandwidthMonitor service configuration object grants PCEF a specified amount/dosage and records the timestamp when it was granted.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Name |
Any name can be specified. |
Reporting Timeout |
The number of minutes used to set the Revalidation-Time AVP so that the subscriber has a chance to get unthrottled before the allocated dosage is used. |
Monitoring Key |
BaseUsageMonitoringKey For detailed descriptions of these parameters, see Common Parameter Descriptions. |
Bandwidth Threshold (List) |
BandwidthThresthold
|
The BearerControlMode service configuration object sets the Bearer Control Mode to the specified value. If you do not specify a value, the value is derived. This value overwrites any previously specified value.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Mode Type |
The type of mode that is being set explicitly. |
The CcGroup service configuration object is used with entitlement to specify which credit-control-group the session should be associated with.
Note | This configuration object requires custom properties be enabled in the qns.conf file. |
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Name |
The name of the CC-Group value to be assigned to the user's session. |
The ChargingInformation service configuration object sets the session charging information to the specified value.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Online |
|
Offline |
|
Primary O C S |
The primary Online Charging System to be used. |
Secondary O C S |
The secondary Online Charging System to be used. |
Primary O F C S |
The primary Offline Charging System to be used. |
Secondary O F C S |
The secondary Offline Charging System to be used. |
The goal of Content Filtering is to provide support for content filtering within the network by use of Policy IDs. Policy identifiers (Policy IDs) are rules that are configured on the ASR 5000 platform and invoked by the CPS. Policy IDs are used to implement the required Content Filtering policies defined for the subscriber. The Policy IDs are selected at the ASR 5000 by provisioning their values through the Gx interface by the PCRF.
When a user initiates a session, the ASR5K communicates with the CPS to initialize the defined policies. CPS provides the Policy ID to the ASR5K to provide the necessary Content Filtering services for the user.
The primary purpose of this feature is for CPS to provide Policy IDs configured in the subscriber's service to the PCEF (ASR5K).
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Cisco Content Filtering Policy |
The name of the policy being applied by this configuration. |
The CiscoEventTriggerType service configuration object allows CPS to arm Cisco Custom event to get notified whenever a Gy failure occurs at PCEF. For arming event, 5 is sent and for disarming, 0 is sent.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Event Trigger |
CPS supports Override-Control specific AVPs in CCA-i and CCA-u responses to the PCEF on the Gx Interface and Gx RAR message. These AVPs are used to override charging parameters for predefined and static rules on the PCEF.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Override Rule (List) |
Specifies the name of the rule (predefined or static) for which override values are sent. |
Override Charging Action Exclude Rule (List) |
Exclude Rule – Defines the rule name where the override will not be applied. |
Override Service Identifier |
Used to override the value of Service Identifier configured in the charging action. |
Override Rating Group |
Defines the value of the rating group configured for a static/predefined rule. |
Override Reporting Level |
Used to override the value of reporting level configured in the charging action. |
Override Online |
|
Override Offline |
|
Override Metering Method |
Used to override the value of Metering Method configured in the charging action. |
Override QoS |
Used to Override QoS-Information for a predefined rule or charging action. |
Override-Max-Requested-Bandwidth-UL |
Defines the maximum bit rate allowed for the uplink direction. |
Override-Max-Requested-Bandwidth-DL |
Defines the maximum bit rate allowed for the downlink direction. |
Override-Guaranteed-Bitrate-UL |
Defines the guaranteed bit rate allowed for Uplink direction. This AVP should be included only for rules on dedicated bearers. |
Override-Guaranteed-Bitrate-DL |
Defines the guaranteed bit rate allowed for downlink direction. This AVP should be included only for rules on dedicated bearers. |
Override-Allocation-Retention-Priority |
Used to override the pre-configured value of ARP. |
The CiscoQosGroupRule service configuration object defines QoS Group Rules (and their sub-rules), on which CRD Driven rules depend.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Qos Group Rule Name |
The name of the QoS group rule to which the policy is being applied. |
Flow Status |
|
Encoding Format |
|
Monitoring Key |
|
Redirect Server |
RedirectServer |
Cisco Qos Information |
CiscoQoSInformation For detailed information about these parameters, see Common Parameter Descriptions. |
The DefaultBearerQoS service configuration object configures the QoS attributes for the default bearer.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Qci |
|
Max Req Bandwidth U L |
|
Max Req Bandwidth D L |
|
Guaranteed Bit Rate U L |
|
Guarnateed Bit Rate D L |
|
Apn Agg Max Bit Rate U L |
|
Apn Agg Max Bit Rate D L |
|
Arp |
|
ConditionalApnAggregateMaxBitrate |
Stores values corresponding to the Conditional-APN-Agg-Max-Bitrate grouped AVP. |
The DefaultBearerQoSActions service configuration object sets the values for the various DBQ Attributes based on Policy or the configured DBQ object. There are three types of DefaultBearerQoSActions:
Mirror: The value requested is granted.
Enforce: (Default) The default bearer qos value is granted.
Bound: A min between the two is granted.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Qci |
|
Max Req Bandwidth U L |
|
Max Req Bandwidth D L |
|
Guaranteed Bit Rate U L |
|
Guarnateed Bit Rate D L |
|
Apn Agg Max Bit Rate U L |
|
Apn Agg Max Bit Rate D L |
|
Arp |
The DefaultBearerQciArpOverride service configuration object is used to override the calculated default bearer Qci and ARP attributes.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Qci |
|
Allocation Retention Priority |
|
Priority Level |
Priority Level AVP value. |
Preemption Capability |
Pre-emption Capability AVP value. |
Preemption Vulnerability |
Pre-emption Vulnerability AVP value. |
The DelayBearerCreation service configuration object is used to decide whether to delay the bearer creation or not. Delay value can be configured in the service (or) can be pulled from CRD. Using this configuration CPS holds the CCA-I and Gx-RAR messages for the configured delay time. This service configuration gets added to policy state based on specific use case initiators.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Default Bearer Delay In Milliseconds |
Based on this value CPS initiates delay timer for holding the CCA-I message. Default value is zero which indicates that there is no delay. |
Dedicated Bearer Delay In Milliseconds |
Based on this value CPS initiates delay timer for holding the Gx-RAR message. Default value is zero which indicates that there is no delay. |
The DetectedAppDefaultBearerQos service configuration object is used to apply the Default Bearer QoS based on the TDF-Application-Identifier received in Sd CCR-U and Gx CCR-U. This can be used for both Gx and Sd detected applications.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Search Table Group |
Name of the CRD table used in the service configuration. |
Apply Prev Applied T D F Id Qos |
By default, the value is set to false that indicates CPS considers QoS derived from Rx and default bearer QoS service for missing QoS attributes. If set to true, CPS considers QoS derived from previously applied TDF ID QoS for missing QoS attributes. |
Input Column Binding (List) |
Input parameters in terms of CRD column name and mapped AVP Code. Supported AVP code is TDF-Application-Identifier. |
Output Column Binding (List) |
Output parameters in terms of CRD column name and mapped AVP Code. Supported AVP codes are: QoS-Class-Identifier, Priority-Level, Preemption Capability, Preemption Vulnerability, APN-Aggregate-Max-Bitrate-UL, APN-Aggregate-Max-Bitrate-DL, Max-Requested-Bandwidth-UL, Max-Requested-Bandwidth-DL, Guaranteed-Bitrate-UL, and Guaranteed-Bitrate-DL. |
The DetectedAppPriorityDeafaultBearerQoS to populate 'Priority' and 'CC-Time' by taking TDF-Application-Identifier as input. This can be used for both Gx and Sd detected applications.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Default T D F App Id Priority |
When default value for the TDF Id is not configured, CPS considers this by default value is -1, which takes high precedence and if multiple TDF-APP-Id`s does not have priority then both will have same priority then CPS may not process in order so behavior would vary every time CPS evaluate this table. |
Default C C Time In Seconds |
Default CC-Time when not received in Sd_CCR-U. |
Stg Name |
Name of the CRD table used in this service configuration. |
List Of Input Column Avp Pairs (List) |
Defines the mapping between the AVP Names and the key columns defined in the selected STG. These AVPs are used as inputs while evaluating the CRD table in STG. |
TDF App Id priority Column |
Priority Configured for TDF-Application-Identifier. |
C C Time Output Column |
CC-Time Configured for the TDF-Application-Identifier. |
Note |
The DynamicTrafficSteering service configuration object is not used.
The EMPS (Enhanced Multimedia Priority System) service configuration object defines the MPS EPS Priority MPS Priority Level and IMS Signaling Priority level. This is required for Always on MPS.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Mps Eps Priority Enabled |
When selected, invokes the Priority EPS Service. |
Mps Priority Level |
Indicates the priority level (Integer range 1-15). |
Ims Signaling Priority |
IMS signaling priority level (Integer range 1-15). |
The EventTrigger service configuration object specifies the event to be sent.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Event Trigger |
The GxDynamicRuleReference configuration object is used only when the ADC (Application Detection & Control) Feature is enabled at PCEF and new dynamic rules need to be installed over the Gx interface based on Application Detection on the Gx interface by the PCEF.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
STG Table |
The name of the Search Table group table that is being referenced. |
List Of Input Column Avp Paris (List) |
|
List Of Output Column Avp Paris (List) |
|
Retry Pcc Rules On Failure |
Can be set to true or false. Default: false |
The IntermediateRulesParamOnFailure service configuration is used to send Flow-Status, Rating-Group, Service-Id when Retry Profile is configured with interval.
The following table describes the service configuration parameters:
The MaxQoS service configuration object authorizes the requested QoS against the maximum-allowed QoS.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Qci |
|
Max Req Bandwidth U L |
|
Max Req Bandwidth D L |
|
Guaranteed Bit Rate U L |
|
Guaranteed Bit Rate D L |
|
Apn Agg Max Bit Rate U L |
|
Apn Agg Max Bit Rate D L |
|
Arp |
Override QoS service configuration is used to allow configuring override for Gx default bearer QoS APN AMBR UL/DL values.
CPS first evaluates the derived QoS values for default bearer. CPS then evaluates the table provided in Override QoS service configuration by using the key values and determine the result APN AMBR UL/DL values. If the "Condition to Override" is "LT", then CPS limits the derived QoS values with these override values. If the "Condition to Override" is "GT", then CPS selects the maximum UL/DL among the derived and override values.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Stg Reference |
This is the reference to the STG that contains the QoS reference and the QoS parameter values (QCI, APN-MBR-UL, and so on). |
List Of Input Column Avp Pairs (List) |
Defines the list to specify the mapping for input (key) columns for determining their values for querying the STG. |
Apn Agg Max Bit Rate U L |
Reference to the STG output column that gives the "APN-Aggregate-Max-Bitrate-UL" value for limiting QoS. This value and the corresponding value derived after QoS actions are compared to determine the final value for APN-Aggregate-Max-Bitrate-UL. |
Apn Agg Max Bit Rate D L |
Reference to the STG output column that gives the "APN-Aggregate-Max-Bitrate-DL" value for limiting QoS. This value and the corresponding value derived after QoS actions are compared to determine the final value for APN-Aggregate-Max-Bitrate-DL. |
Condition to Override |
The condition to compare the values. Only two values are supported "LT" and "GT". If LT is selected, CPS picks the lowest QoS parameter value from the two QoS references. If GT is selected, CPS picks the highest QoS parameter value from the two QoS references. Possible Values: |
The PreConfiguredRule service configuration object configures a dynamic rule; these values are then used in the charging rule definition.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Rule Group |
|
Rule Name |
|
Enable Resource Allocation Notification |
|
Dual Stack Session |
|
Framed I P Type |
|
ToD Schedule |
|
Scheduled Hour |
|
Retry Profile |
|
Online |
|
Offline |
|
Flow Status |
|
Rating Group |
|
Service Identifier |
The identity of the service or service component that the service data flow in a PCC rule relates to. |
Reporting Level |
The Reporting-Level AVP is of type Enumerated and it defines on what level the PCEF reports the usage for the related PCC rule. There are three types of reporting levels:
|
Precedence |
Determines the order in which the service data flow templates are applied at service data flow detection at the PCEF. A PCC rule with the Precedence AVP having a lower value will be applied before a PCC rule with the Precedence AVP having a higher value. |
Metering Method |
The Metering-Method AVP (AVP code 1007) is of type Enumerated and it defines what parameters will be metered for offline charging. The PCEF may use the AVP for online charging in case of decentralized unit determination. There are three types of metering method: |
Monitoring Key |
|
Flow Information (List) |
FlowInformation |
QoS Information |
QoSInformation |
Redirect Information |
RedirectInformation |
Mirror Default Bearer QCI/ARP |
When set to true, CPS mirrors the QCI and ARP from the command level to the rule level, and enforces the rule level MBR values from the Policy Builder configuration for the rule level. Default: false. |
Provision Default Bearer QoS |
|
Tdf Application Identifier |
|
Mute Notification |
|
Use in Rule Status Condition |
Controls whether or not the PCC rule reported status AVPs are created. Default: true |
Use in Rule Install Condition |
Controls whether or not the PCC rule installed AVPs are created. Default: false |
The PreDefinedRule service configuration object creates static rules that will be mapped to the charging rules that will be installed.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Rule Group |
|
Rule Name |
|
Enable Resource Allocation Notification |
|
Dual Stack Session |
|
Framed I P Type |
|
ToD Schedule |
|
Scheduled Hour |
|
Retry Profile |
The PreDefinedRuleBase service configuration object creates static rules that will be mapped to the charging rule base name.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Rule Group |
|
Rule Name |
|
Enable Resource Allocation Notification |
|
Dual Stack Session |
|
Framed I P Type |
|
ToD Schedule |
|
Scheduled Hour |
|
Retry Profile |
The ReleaseBearerDelayMessage service configuration object is used to release CCA-I /Gx-RAR messages which is held based on delay bearer creation configuration. For more information on Delay Bearer Creation service configuration object, refer to DelayBearerCreation.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
The ReprovisionObjects service configuration object forces the Policy Charging Control (PCC) rules to be reprovisioned when the flag is set to true.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
PCC Rules |
Can be set to true or false. When set to true, the PCC rules will be reprovisioned. Default: false |
Default Bearer QoS |
Can be set to true or false. When set to true, the Default Bearer QoS will be reprovisioned. Default: false |
Override Control |
Can be set to true or false. When set to true, the AVP Override Control is repovisioned during handoff. Default: false |
The RevalidationTime service configuration object populates the revalidation time AVP at the message level; the PCEF will come back to the PCRF when that timestamp is hit.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Absolute Time Flag |
This flag can be set to true or false. true – The next revalidation time is set using the absolute values specified for the following three revalidation attributes (Hour Minute, and Sec). false – The next revalidation time is derived by adding the values specified for the following three revalidation attributes to the system time. |
Revalidation Time in Hour |
The hour the revalidation will occur. Specify this value using 24-hour format. |
Revalidation Time in Minute |
The minutes setting in the revalidation timestamp. |
Revalidation Time in Sec |
The seconds setting in the revalidation timestamp. |
The SupressRxMessage service configuration object is used to suppress the Rx ASR message. CPS evaluates the STG configured in this service and derives the information whether to suppress Rx ASR or not.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Search Table Group |
Search Table Group table that is being referenced. The STG (and the contained CRDs) can also contain key columns that do not directly refer to Diameter AVPs in the trigger message. For example, Outputs of other tables. These columns must be bound correctly. |
Input Column Binding (List) |
ColumnAndAvpPair |
Is Message Suppressed Output Column |
References to the output column defined in the CRD. |
The TableDrivenChargingRule service configuration object represents a charging rule in stored CRD format; there can be multiple charging rules.
Parameter |
Description |
||
---|---|---|---|
Priority |
|||
Diameter Client |
|||
Logical Grouping |
No longer used. |
||
Search Table |
The name of the table from which to perform a lookup. |
||
Search Group |
A constant value that CPS uses to search within the Search Table Group indicated by “Search Table” element. |
||
Search Column |
Must be bound to the key column of the STG. The data contained in the STG column is of type Text. |
||
Best Match Excludes Star Match |
By default, the parameter is set to true. When set to true, the best match result records with exact match and if the exact match records are not found then it return records with star and pattern match. When set to false, then the result includes exact match as well as star and pattern match. |
||
Rule Name Source |
A key column that must be bound to the Rule Name column within the STG. The data in the STG column is of type Text. |
||
Flow Status Source |
Must be bound to the Flow Status column in the Search Table Groups (STG). The data contained in the STG column is of type Text. |
||
Monitoring Key Source |
Must be bound to the Monitoring Key column in the STG. The data contained in the STG column is of type Text. |
||
Redirect Address Table |
The name of the Redirect Address Table. This table contains redirected attributes, such as these (described in the following four rows): |
||
Redirect Enabled Source |
Must be bound to the Redirect Enabled column in the STG. The data contained in the STG column is of type True/False. |
||
Redirect Address Type Source |
Must be bound to the Redirect Address Type column in the STG. The data contained in the STG column is of type Text. |
||
Redirect Address Source |
Must be bound to the Redirect Address column in the STG. The data contained in the STG column is of type Text. |
||
Redirect Support Source |
Must be bound to the Redirect Support column in the STG. |
||
Online Source |
Must be bound to the Online column in the STG. The data contained in the STG column is of Type Number. The possible values are mentioned in 3GPP specification 29.212. |
||
Offline Source |
Must be bound to the Offline column in the STG. The data contained in the STG column is of Type Number. The possible values are mentioned in 3GPP specification 29.212. |
||
Rating Group Source |
Must be bound to the Rating Group column in the STG. The data contained in the STG column is of Type Number. The possible values are mentioned in 3GPP specification 29.212. |
||
Service ID Source |
Must be bound to the Service ID column in the STG. The data contained in the STG column is of Type Number. The possible values are mentioned in 3GPP specification 29.212. |
||
Reporting Level Source |
Must be bound to the Reporting Level column in the STG. The data contained in the STG column is of Type Number. The possible values are mentioned in 3GPP specification 29.212. |
||
Precedence Source |
Must be bound to the Precedence column in the STG. The data contained in the STG column is of Type Number. The possible values are mentioned in 3GPP specification 29.212. |
||
Metering Method Source |
Must be bound to the Metering Method column in the STG. The data contained in the STG column is of Type Number. The possible values are mentioned in 3GPP specification 29.212. |
||
Flow Information Source |
Must be bound to the Flow Information column in the STG. The data contained in the STG column is of type Text.
|
||
Use Override Server Address |
Must be bound to the Override Server Address column in the STG. The data contained in the STG column is of type True/False. If set to true, the address is taken from the service option. If set to false, the redirect server address will not be overridden. |
||
QCI Source |
Must be bound to the QCI column in the STG. The data contained in the STG column is of Type Number. For more information, see Common Parameter Descriptions. |
||
Max Req Bandwidth U L Source |
Must be bound to the Max Req Bandwidth UL column in the STG. The data contained in the STG column is of Type Number. For more information about Max Req Bandwidth U L, see Common Parameter Descriptions. |
||
Max Req Bandwidth D L Source |
Must be bound to the Max Req Bandwidth DL column in the STG. The data contained in the STG column is of Type Number. For more information about Max Req Bandwidth D L Source, see Common Parameter Descriptions. |
||
Guaranteed Bit Rate U L Source |
Must be bound to the Guaranteed Bit Rate UL column in the STG. The data contained in the STG column is of Type Number. For more information about Guaranteed Bit Rate U L see Common Parameter Descriptions. |
||
Guaranteed Bit Rate D L Source |
Must be bound to the Guaranteed Bit Rate DL column in the STG. The data contained in the STG column is of Type Number. For more information about Guaranteed Bit Rate D L, see Common Parameter Descriptions. |
||
ARP Priority Level Source |
Must be bound to the ARP Priority Level column in the STG. The data contained in the STG column is of Type Number. For more information about Priority Levels, see Common Parameter Descriptions. |
||
ARP Preemption Capability Source |
Must be bound to the ARP Preemption Capability column in the STG. The data contained in the STG column is of Type Number. For more information about Preemption Capability, see Common Parameter Descriptions. |
||
ARP Preemption Vulnerability Source |
Must be bound to the ARP Preemption Vulnerability column in the STG. The data contained in the STG column is of Type Number. For more information about Preemption Vulnerability, see Common Parameter Descriptions. |
||
Apn Agg Max Bit Rate U L |
|||
Apn Agg Max Bit Rate D L |
|||
Rule Retry Profile Name |
Must be bound to the Rule Retry Profile column in the STG. The data contained in the STG column is of type Text. |
||
Mirror Default Bearer QCI/ARP |
When set to true, CPS mirrors the QCI and ARP from the command level to the rule level, and enforces the rule level MBR values from the Policy Builder configuration for the rule level. Default: false. |
||
Provision Default Bearer QoS |
|||
Tdf Application Identifier Source |
References the application detection filter (for example, its value may represent an application such as a list of URLs, etc.) to which the PCC rule for application detection and control in the PCEF applies. Tdf Application Identifier Source must be bound to the appropriate column in the STG, and Type should be Text. For more information about Tdf Application Identifier, see Common Parameter Descriptions. |
||
Mute Notification Source |
Must be bound to the Mute Notification column in the STG. The data contained in the STG column is of Type Number or Decimal. For more information about Mute Notification, see Common Parameter Descriptions. |
||
Input List (list) |
InputColumnObject:
|
||
Use in Rule Status Condition |
Controls whether or not the PCC rule reported status AVPs are created. By default, this parameter is set to true. |
||
Use in Rule Install Condition |
Controls whether or not the PCC rule installed AVPs are created. By default, this parameter is set to false. |
The TableDrivenChargingRuleRefresh service configuration object forces a rule revalidation based on the rule reporting status.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Search Table |
The name of the table from which to perform a lookup. |
Input Rule Name Column |
The input column for the Search Table Group (STG), which contains the rule name. |
Input Rule Status Column |
The input column for the STG, which contains the rule status against which new rules are to be added. |
Output Rule Group Column |
The output column for the STG, which contains the rule group used as a group to search the TableDrivenChargingRule. |
Output Search Table |
If there are multiple TableDrivenChargingRules mapped with multiple Search Tables, and if we want to use only one table to be looked at for new rules installation on rule failure, we can give the table as Output Search Table so that only one TableDrivenChargingRule object, which has the ‘Search Table’ matching the ‘Output Search Table’ in TableDrivenChargingRuleRefresh, is evaluated for refresh rules. |
The TableDrivenChargingRuleRefresh service configuration option forces a rule revalidation based on the rule reporting status.
Parameter |
Discription |
---|---|
Priority |
|
Diameter Client |
|
Logical Grouping |
No longer used. |
Search Table |
The name of the table from which to perform a lookup. |
Search Group |
A constant value that CPS uses to search within the STG indicated by “Search Table” element. |
Search Column |
Must be bound to the key column of the STG. The data contained in the STG column is of type Text. |
Best Match Excludes Star Match |
By default, the parameter is set to true. When set to true, the best match result records with exact match and if the exact match records are not found then it return records with star and pattern match. When set to false, then the result includes exact match as well as star and pattern match. |
Rule Name Source |
A key column that must be bound to the Rule Name column within the STG. The data contained in the STG column is of type Text. |
Monitoring Key Source |
Must be bound to the Monitoring Key column within the STG. The data contained in the STG column is of type Text. |
Encoding Format Source |
Must be bound to the Encoding format column within the STG. The data contained in the STG column is of type True/False. |
Redirect Address Table |
The name of the Redirect Address Table. This table contains redirected attributes, such as these (described below): |
Redirect Enabled Source |
Must be bound to the Redirect Enabled column within the STG. The data contained in the STG column is of type True/False. |
Redirect Address Type Source |
Must be bound to the Redirect Address Type column within the STG. The data contained in the STG column is of type Text. |
Redirect Address Source |
Must be bound to the Redirect Address column within the STG. The data contained in the STG column is of type Text. |
Use Override Server Address |
Must be bound to the Override Server Address column within the STG. The data contained in the STG column is of type True/False. If set to true, the address is taken from the service option. If set to false, the redirect server address will not be overridden. |
Override Server Address |
Must be bound to the corresponding column within the STG. |
The TableDrivenPredefinedChargingRule service configuration object represents a charging rule in stored CRD format; there can be multiple charging rules.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Logical Grouping |
No longer used. |
Search Table |
The name of the table from which to perform a lookup. |
Search Group |
A constant value that CPS uses to search within the Search Table Group indicated by “Search Table” element. |
Search Column |
Must be bound to the key column of the STG. The data contained in the STG column is of type Text. |
Best Match Excludes Star Match |
By default, the parameter is set to true. When set to true, the best match result records with exact match and if the exact match records are not found then it return records with star and pattern match. When set to false, then the result includes exact match as well as star and pattern match. |
Rule Name Source |
A key column that must be bound to the Rule Name column within the STG. The data in the STG column is of type Text. |
Input List (list) |
InputColumnObject:
|
Use In Rule Status Condition |
Controls whether or not the PCC rule reported status AVPs are created. By default, this parameter is set to false. |
Use In Rule Install Condition |
Controls whether or not the PCC rule installed AVPs are created. By default, this parameter is set to false. |
The TableDrivenRuleNameSupport service configuration object allows CPS to perform a UNION operation on two sets of rule lists. This operation uses the rules that are common to both lists obtained from two different Search Table Groups (STGs).
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Logical Grouping |
No longer used. |
Search Table |
The name of the table from which to perform a lookup. |
Search Group |
A constant value that CPS uses to search within the STG indicated by “Search Table” element. |
Search Column |
Must be bound to the key column of the STG. The data contained in the STG column is of type Text. |
Best Match Excludes Star Match |
By default, the parameter is set to true. When set to true, the best match result records with exact match and if the exact match records are not found then it return records with star and pattern match. When set to false, then the result includes exact match as well as star and pattern match. |
Rule Name Source |
A key column that must be bound to the Rule Name column within the STG. The data contained in the STG column is of type Text. |
The TDFServerInformation service configuration object is used to configure TDF-Server-Information based on Gx APN, GX-MCCMNC and LDAP attribute SUB_TYPE. Based on the service configuration, CRD look up is done to obtain the TDF-Server-Information and TSR would be initiated towards Sd interface.
Parameter |
Description |
---|---|
Priority |
The priority of the message for processing. The higher the number, the higher the priority. Default: 0 For more information, see Common Parameter Descriptions. |
Diameter Client |
The client configuration is used to apply different policies based on PCEF type. This is optional parameter. For more information, see Common Parameter Descriptions. |
Search Table Group |
Search Table Group table that is being referenced. The STG (and the contained CRDs) can also contain key columns that do not directly refer to Diameter AVPs in the trigger message. For example, Outputs of other tables. These columns must be bound correctly. |
List Of Input Column Avp Pairs (List) |
Defines the mapping between the AVP Names and the key columns defined in the selected STG. These AVPs are used as inputs while evaluating the CRD table in STG. ColumnAndAvpPair |
List Of Output Column Avp Pairs (List) |
Defines the mapping between the AVP Names and the output columns defined in the STG selected. These mapping indicate how the output column's values are mapped to AVPs after the CRD is evaluated. ColumnAndAvpPair |
The UsageMonitoringKey service configuration object allows scheduled monitoring in the Monitoring Schedule (List) parameter.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Encoding Format |
|
Monitoring Key |
|
Dosage |
|
Monitoring Level |
|
Enabled |
Can be set to true or false. |
Balance Code |
|
Validity Period Minutes |
The number of minutes that the balance code representing the quota is valid. The default value is 60 minutes. This parameter is deprecated. |
Reporting Threshold |
Not used. |
Dosage Override (List) |
Default dosage override based on remaining balance on the selected account. |
Monitoring Schedule (List) |
UsageMonitoringSchedule:
|
Target Balance Code |
Indicates a text input for the balance code name to be mapped to the specific target balance. |
The UsageMonitoringKeyDual service configuration object allows time usage monitoring (The UsageMonitoringKey is supported for Volume Usage monitoring). This service configuration object provides a way to configure usage monitoring for both time and volume (independently as well as together under single monitoring key). To monitor usage under one key for Volume and Time, both the balance codes need to be provided in the Service Configuration. For independent monitoring, only the relevant type of fields can be set. For example, for only Volume monitoring, fields related to time monitoring can be left blank/null and vice versa. Multiple instances of UsageMonitoringKeyDual can also be included in the service configuration each corresponding to a unique monitoring key.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Encoding Format |
|
Monitoring Key |
|
Dosage |
|
Monitoring Level |
|
Enabled |
Can be set to true or false. |
Validity Period Minutes |
The number of minutes that the balance code representing the quota is valid. The default value is 60 minutes. This parameter is deprecated. |
Volume > UsageMonitoringBucket > Balance Code |
This value indicates the Volume type balance with which the key is associated. |
Time > UsageMonitoringBucket > Balance Code |
This value indicates the Time type balance with which the key is associated. |
Target Balance Code |
Indicates a text input for the balance code name to be mapped to the specific target balance. |
Inactivity Detection Time |
The time interval in seconds after which the time measurement shall stop for the Monitoring Key, if no packets are received belonging to the corresponding Monitoring Key. Corresponds to Quota-Consumption-Time AVP |
This section describes the parameters for the following Gy Service Configuration Objects:
The ExternalRatingGroup service configuration object is used to identify if a rating group status is indicated by an external component. If the status is invalid, the final unit actions are applied as specified in this object.
The rating group for this object is list of values identifying all external rating groups.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Rating Group |
Corresponds to a value configured on the ASR5000 that represents which data should be monitored. |
Ocs State |
Indicates the status of the external rating group as notified by the external component. The possible values are VALID/INVALID. Default: VALID |
Final Unit Action |
Can be set to one of the following options:
Default: TERMINATE |
Redirect Address Type |
|
Redirect Address |
|
Filter ID |
When the Final Unit Action is RESTRICT_ACCESS, the access device must restrict the user access to the IP packet filters identified by Filter-id AVP. |
Restriction Filter Rule |
When the Final Unit Action is RESTRICT_ACCESS, the access device must restrict the user access to the IP packet filters defined in the Restriction-Filter-Rule AVP. |
Please configure the GySessionWallet service configuration object only with the help of Cisco Advanced Services or the Cisco Technical Assistance Center (TAC).
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Rating Group |
Corresponds to a value that represents which data should be monitored. |
Rg Type |
Rating Group Type. The value can be set to either Volume or Time. |
Dosage |
|
Balance Code |
|
Final Unit Action |
Can be set to one of the following options:
Default: TERMINATE |
Redirect Address Type |
|
Redirect Address |
|
Restriction Filter Rule |
When the Final Unit Action is RESTRICT_ACCESS, the access device must restrict the user access to the IP packet filters defined in the Restriction-Filter-Rule AVP. |
Filter ID |
When the Final Unit Action is RESTRICT_ACCESS, the access device must restrict the user access to the IP packet filters identified by Filter-id AVP. |
Tariff Change Time |
Outside the scope of this document. Default: 0 |
Tariff Switch Model |
Outside the scope of this document. Default: SINGLE_COUPON |
Validity Time |
Sets a session timer for the Gy quota grant; even if quota is not exhausted, the PCEF must check back in at the end of the validity time (in seconds). Default: 3600 |
Volume Quota Threshold |
PCEF will check back in with OCS when the Volume Quota Threshold has been reached. The value must be set to less than the overall Dosage (in bytes). Default: 0 |
Time Quota Threshold |
PCEF will check back in with OCS when the Time Quota Threshold has been reached. The value must be set to less than the overall Dosage (in seconds). Default: 0 |
Quota Holding Time |
The amount of time the quota should be available on the PCEF without activity from the user (in seconds). Default: 0 |
Quota Consumption Time |
Idle traffic threshold time (in seconds); only used with time quota rating groups. Default: 0 |
Use Shared Bucket |
Used in a shared quota use case in which the same account balance and rating group can be used within a shared group of users. Default: false |
The RatingGroupServiceId service configuration object identifies a set of services that are identified by Service-Identifier and subject to the same cost and rating type. The service identifier is provisioned along with the rating group this object is used.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Rating Group |
Corresponds to a value configured on the ASR5000 that represents which data should be monitored. |
Service Identifier |
Identifies a set of services subject to the same cost and rating type. |
Rg Type |
Rating Group Type. The value can be either Volume or Time. |
Dosage |
|
Balance Code |
|
Final Unit Action |
Can be set to one of the following options:
Default: TERMINATE |
Redirect Address Type |
|
Redirect Address |
|
Restriction Filter Rule |
When the Final Unit Action is RESTRICT_ACCESS, the access device must restrict the user access to the IP packet filters defined in the Restriction-Filter-Rule AVP. |
Filter ID |
When the Final Unit Action is RESTRICT_ACCESS, the access device must restrict the user access to the IP packet filters identified by Filter-id AVP. |
Tariff Change Time |
Outside the scope of this document. Default: 0 |
Tariff Switch Model |
Outside the scope of this document. Default: SINGLE_COUPON |
Validity Time |
Sets a session timer for the Gy quota grant; even if quota is not exhausted, the PCEF must check back in at the end of the validity time (in seconds). |
Volume Quota Threshold |
PCEF will check back in with OCS when the Volume Quota Threshold has been reached; value must be set as less than the overall Dosage (in bytes). |
Time Quota Threshold |
The threshold value in seconds and can be provisioned by OCS when granted service units include cc-time. The PCEF shall seek re-authorization from OCS for the quota when the quota contents fall below the supplied threshold. |
Quota Holding Time |
The amount of time the quota should be available on the PCEF without activity from the user (in seconds). |
Quota Consumption Time |
Idle traffic threshold time (in seconds); only used with time quota rating groups. |
Rate1 |
When tariff time is provisioned by OCS, PCEF reports usage before and after tariff change time when reporting after tariff change time. Rate 1 indicates at what rate usage before tariff change time is charged. |
Rate2 |
When tariff time is provisioned by OCS, PCEF reports usage before and after tariff change time when reporting after tariff change time. Rate2 indicates at what rate usage after tariff change time is charged. |
Use Shared Bucket |
Used in a shared quota use case in which the same account balance and rating group can be used within a shared group of users. Default: false |
In CPS 13.1.0 and higher releases, LdapAddProfile service configuration has been deprecated. Instead of using LdapAddProfile, you can use LdapAddEntries.
LdapAddProfile service configuration can be used to define an LDAP profile (list of attributes) that can be written to an external LDAP server.
Parameter |
Description |
---|---|
Ldap Server Set |
The parameter is used to define the target server set to which the add request is sent. |
Dn |
This is the LDAP Distinguished Name for the new entry that is added via the add request. |
Dn Replacement Rules (List) |
This parameter is used to specify the replacement rules (one for each Dn parameter) that helps to resolve the parameters provided as part of Dn. ReplacementMapping: |
Ldap Add Attribute (List) |
This parameter is used to specify the list of attributes (name/value pairs) that are to be included in the new profile added using add request. LdapSynchAttribute: |
Controls (List) |
This parameter is used to specify the LDAP controls that needs to be send in the LDAP modifyRequest. Control is a way to specify extension information to the LDAP server. Control: A control is a way to specify extension information. Controls which are sent as part of a request apply only to that request and are not saved.
These above mentioned configuration fields are added as per the LDAP controls defined in RFC-2251. |
LdapAddEntries service configuration allows you to define multiple LDAP entries (DNs) to add on external server in specified order (sequential in synchronous mode).
Parameter |
Description |
---|---|
Ldap Server Set |
The parameter is used to define the target server set to which the add request is sent. |
Entries (List) |
Multiple attributes can be defined to be added under each LDAP entry (which are added under the specified DN). If an entry already exists or add operation for an entry returns an error, CPS continues sequentially adding other entries in the list as long as the connection is usable. LdapEntries: For more information, refer to Table 2. |
Parameter |
Description |
---|---|
Dn |
This is the LDAP Distinguished Name for the new entry that is added via the add request. |
Dn Replacement Rules (List) |
This parameter is used to specify the replacement rules (one for each Dn parameter) that helps to resolve the parameters provided as part of Dn. ReplacementMapping: |
Modify If Exists |
If the "Modify If Exists" flag is set to true for the entry that already exists, CPS attempts a LDAP modify operation with "change type: replace" for each included attribute for which the "Add Only" flag is false ("Add Only" = true attributes are not included in the modify operation). This modify operation is executed in parallel to the other add operations (for other DNs). |
Ldap Attributes (List) |
This parameter is used to specify the list of attributes (name/value pairs) that are to be included in the new profile added using add request. LdapSynchAttribute:
|
Controls (List) |
This parameter is used to specify the LDAP controls that needs to be send in the LDAP modifyRequest. Control is a way to specify extension information to the LDAP server. Control: A control is a way to specify extension information. Controls which are sent as part of a request apply only to that request and are not saved.
These above mentioned configuration fields are added as per the LDAP controls defined in RFC-2251. |
Note | If both LdapAddEntries and LdapSynchProfile are found in policy, CPS consolidates the LDAP add (from LdapAddEntries) and LDAP modify (from LdapSynchProfile) operations into a single LDAP add operation if any of the LDAP DNs provided under LdapAddEntries matches the DN provided under LdapSynchProfile. If a match is found, all attributes under LdapSynchProfile are copied into the LDAP add operation (and the "Modify If Exists" flag is overridden to "true" for that DN entry). If a DN match is not found, both operations execute separately in parallel. |
LdapSyncProfile service configuration can be used to define a LDAP profile (list of attributes) that is updated on the external LDAP server. CPS calculates the values and tracks the LDAP attributes (included in the profile) for any changes through the lifetime of the session. If changes are detected, the server is updated with the new version of the profile.
Parameter |
Description |
---|---|
Ldap Server Set |
A reference to the LdapServerSet configured in the reference-data. It links to the LDAP Plugin Configuration to identify the LDAP server configuration parameters. |
Dn |
This is the Distinguished Name for identifying the subscriber to be updated on the LDAP directory. |
Dn Replacement Rules (List) |
This gives the option to dynamically replace the variables (identified with $) defined in DN. ReplacementMapping: |
Modified Date Attribute Name |
Specifies the LDAP attribute name for storing the date when the LDAPModify request is triggered. |
Ldap Synch Attribute (List) |
Specifies the list of attributes that should be updated on the LDAP server through the modify request. LdapSynchAttribute:
|
Controls (List) |
Specifies the LDAP controls that needs to be send in the LDAP modifyRequest. Control is a way to specify extension information to the LDAP server. Control: A control is a way to specify extension information. Controls which are sent as part of a request apply only to that request and are not saved.
These above mentioned configuration fields are added as per the LDAP controls defined in RFC-2251. |
This section describes the parameters for the following Rx Service Configuration Objects:
ActionBasedOnSyPolicyCounters Service Configuration is used to pull CRD data from the STG.
The input parameters are: The Sy Policy Counter Identifier and Status in the format Identifier:Status. For multiple Policy Counters, each set of identifiers and counters are separated with semi-colons, for example: Identifier1:Status1;Identifier2:Status
When CPS receives Rx AAR or Sy SLA/SNR messages, CPS performs a one-time query on the CRD Table with the Sy Policy Counter Status as the input Key. Based on the output parameters, CPS sets SyCounterActions Object in Policy State with output parameters to handle in triggerAdditionalMessages method.
The output parameters are:
Specific Action : The Specific Action to be sent in Rx-RAR
Restricted-Media Type : The media types mapped. For multiple media types, each type is separated by a comma.
Rx-Action : Action to be taken on Rx. Possible values are Continue (no action), Reject, and Terminate.
Sy-Action : Possible values are Continue (no action), Terminate.
Gx-Action : Rule-Group name in TableDrivenChardingRule STG which has Gx Rules for Flow-Status, Service-Id, Rating-Group , offline/online Metering method
Sponsored-Identity : Sponsor Identity of session. For multiple Sponsor Identities, each is separated by a comma.
Application-Service-Provider-Identity : Application-Service-Provider-Identity of session. For multiple Application-Service-Provider-Identity, each is separated by a comma.
The following table describes the service configuration parameters:
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Policy Counter Name (List) |
Enter the Policy Counter Names in the order in which the CRD Input Column ‘Policy-Counter-Status’ is configured. Expected format is PolicyCounterIdentifier1:PolicyCounterStatus1; PolicyCounterIdentifier2:PolicyCounterStatus2 |
Stg Name |
References the Search table group containing the CRD table. |
List of Input Column Avp Pairs (List) |
Defines the mapping between the AVP Names and the key columns defined in the selected STG. These AVPs are used as inputs while evaluating the CRD table in STG. |
List of Output Column Avp Pairs (List) |
List of Output AVPs for the CRD. |
You must configure a table search initiator to the Search Table Group mapped in ActionBasedOnSyPolicyCounters with the condition "a customer reference data AVP exists" , which ensures that the table is not evaluated every time on any event by the policy engine. In the Table Search Initiator, enter a name for the initiator and add code as "CRD-CODE" and set the value to True.
Rx Dynamic Rules can be modified by configuring ModifyRxDynamicRule service configuration and the modification can be based on Default Bearer QoS, Media-Type, AF-Application-identifier, Sponsor-Id and Application-Service-Provider-Identity.
The following table describes the service configuration parameters:
Parameter |
Description |
||
---|---|---|---|
Priority |
|||
Diameter Client |
|||
Stg Name |
References the Search table group containing the CRD table. |
||
List of Input Column Avp Pairs (List) |
Defines the mapping between the AVP Names and the key columns defined in the selected STG. These AVPs are used as inputs while evaluating the CRD table in STG.
|
||
List of Output Column Avp Pairs (List) |
List of Output AVPs for the CRD.
|
||
Ignore Existing Rule |
This flag is used to ignore modification of existing Rx dedicated bearer which needs to be true to avoid existing rule modification on default bearer boost. |
The RxAppQoSInformation service configuration option defines the QoS to be used for Rx dedicated bearer based on the application ID and media type.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Qci |
|
Max Req Bandwidth U L |
|
Max Req Bandwidth D L |
|
Guaranteed Bit Rate U L |
|
Guaranteed Bit Rate D L |
|
Arp |
|
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). |
For more information, refer to RxAppQosInformation Service Configuration.
RxAuthorizationSTGConfiguration service configuration can be used to evaluate Rx Authorization table and obtain the output values configured. The RxAuthorizationSTGConfiguration supports chained evaluation of STGs which means multiple Search Table Groups can be configured hierarchically in the RxAuthorizationSTGConfiguration and outputs of one table can be used as input keys for another table. The Rx Authorization table from which Bearer Authorization and Error Cause output values are received needs to be configured as the last table in the list of chained STGs configured under RxAuthorizationSTGConfiguration.
Note |
|
The following table describes the service configuration parameters:
Parameter |
Description |
||
---|---|---|---|
Priority |
|||
Diameter Client |
|||
Stg Details (List) |
StgNameReferencePair:
|
The RxChargingParameterSTGConfiguration service configuration object sets the charging parameters for dedicated bearers created for IMS session (non-sponsored data case).
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Chargingparameterstg Name |
References the Search table group containing the CRD tables that define the Qos Action. |
List Of Input Column Avp Pairs (List) |
See Common Parameter Descriptions. The following is the list of supported AVP Names under Input Column: |
List Of Output Column Avp Pairs (List) |
See Common Parameter Descriptions. The following is the list of supported AVP Names under Output Column: |
RxDelayedMCDProcessing service configuration is used to delay the processing of media reported in AAR until it receives response for Gx RAR triggered based on Event-Triggers enabled based on RxTableDrivenEventTriggers.
The following table describes the service configuration parameters:
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
RxDelayedMCDProcessing service configuration also requires defining the RxTableDrivenEventTriggers to determine the Event-Triggers to be sent on the dummy Gx RAR message.
When CPS evaluates the RxDelayedMCDProcessing and determines that a dummy Gx RAR is required to be triggered then CPS skips the Rx Authorization processing. No need to add specific condition on RxAuthorizationSTGConfiguration template to disable it when dummy RAR needs to be triggered.
A policy with policy-action "Create Sy Service Session" is required to be configured for selectively triggering Sy SLR only after dummy RAR response is received. But if the CPS service does not have "Balance Service" check-box enabled and selective Sy needs to be triggered after dummy RAR response is received then "Calculate service configuration - on demand" policy-action is required to be added before the policy-action for triggering the "Create Sy Service Session".
The RxDRMPSTGConfiguration service configuration object sets the priority of the Gx-RAR diameter message using the DRMP AVP in the circumstance of high priority traffic (for example, Multimedia Priority Service (MPS)) from the Rx interface. The DRMP AVP value is derived based on the Reservation-Priority AVP and MPS-Identifier AVP. Both, Reservation-Priority AVP and MPS-Identifier AVP, must present in the AAR message.
Note | Reservation-Priority AVP present at the message level in the AAR is only used. Reservation-Priority AVP present at Media-Component-Description level is not used. |
Parameter |
Description |
---|---|
D R M P Reservation Priority Table |
The name of the STG that is referenced. |
Drmp Output Column |
The output column of the STG, whose value on evaluation of the table, sets the DRMP AVP to set the priority of the Gx-RAR diameter message. |
List Of Input Column Avp Pairs (List) |
Defines the mapping between the AVP names and the key columns defined in the selected STG. These AVPs are used as inputs while evaluating the CRD table in the STG. |
The RxGuaranteedBitRateOverride service configuration object overrides the GBR, and sets it from the MBR value.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Set Guaranteed Bit Rate from Max Requested |
This configuration is applicable when CPS is not able to derive guaranteed bit rate values based on the QoS derivation algorithm defined in 3GPP 29.213 specification. So if GBR is not derived and this service option is configured, then CPS copies the values derived for Max Requested Bitrates into Guranteed Bitrates (applicable for both UL and DL). Default: true |
Set Guaranteed Bit Rate from Max Requested (Qos-Action) |
Set this flag to true for copying the Max-Requested-Bitrate values into Guaranteed-Bitrate after QoS-Actions (RxSTGConfiguration) are applied. The bit rate values are copied only if the new QCI is < 5 and the Qos-Action on Guaranteed Bitrates (UL/DL) is Mirror. Default: false |
For more information, refer to RxGaranteedBitRateOverride Service Configuration.
The RxQoSInformation service configuration option sets QoS values for Rx dedicated bearer.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Qci |
|
Max Req Bandwidth U L |
|
Max Req Bandwidth D L |
|
Guaranteed Bit Rate U L |
|
Guaranteed Bit Rate D L |
|
Arp |
For more information, refer to RxQoSInformation Service Configuration.
The RxSponsoredDataChargingParameterSTGConfiguration service configuration object configures the CRD details for setting charging parameters for dedicated bearers that are created for sponsored data.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Sponsored Datachargingparameterstg Name |
References the Search table group containing the CRD tables that define the Qos Action. |
List Of Input Column Avp Pairs (List) |
See Common Parameter Descriptions. DPCC_NAME - Used to derive the Dynamic PCC rule from CRD tables. DPCC_VALUE - Used to derive the Dynamic PCC rule from CRD tables. |
List Of Output Column Avp Pairs (List) |
The following parameters can be configured under RxSTGConfiguration service configuration:
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Stg Name |
References the Search table group containing the CRD tables that define the Qos Action for Rx specific dynamic rules (dedicated bearer). |
List Of Input Column Avp Pairs (List) |
Define the mapping between the 'AVP Names' and the key 'Columns' defined in the selected STG. These AVPs will be the inputs while evaluating the CRD table in STG. ColumnAndAvpPair:
|
Input Codec Data |
See Table 2. |
ArpPrecedence |
Determines which RxSTGConfiguration to use for the new ARP eMPS feature. |
QosPrecedence |
Determines which RxSTGConfiguration to use for QCI lookup. |
Parameter |
Description |
---|---|
Prefer Answer |
Supported values are: |
Input Columns Media Format |
InputCodecMediaFormatColumns
|
List of Input Columns Sdp Pairs |
InputCodecParameterColumnPair
|
Media Comp Rtpmap Payload Type Index |
Indicates which RTP map line to be used for codec matching. For example, index 2 indicates that the second rtp-map/fmtp line in codec AVP is used for configuration matching. To disable this parameter, the value must be less than 1. If Media Component Description AVP comes with multiple codec-data AVP (offer and answer), then in order to select the codec-data with answer, "prefer_answer" configuration has to be enabled under service option. If the configuration is not enabled, first codec-data is used for configuration matching, which means offer is expected to be first codec-data. |
Note |
|
For more information, see Basic Options.
RxSTGDefaultBearerConfiguration service configuration is used for CRD evaluation of default bearer QoS on receiving Rx AAR with Dynamic-PCC-Requested-QoS AVP. The same service configuration can also be used to support modification of default bearer based on MPS-Identifier and Reservation-Priority received in AAR from P-CSCF.
The following parameters can be configured under RxSTGDefaultBearerConfiguration service configuration:
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Stg Name |
References the Search table group containing the CRD tables that define the Qos Action for Rx specific dynamic rules (dedicated bearer). |
List Of Input Column Avp Pairs (List) |
Defines the mapping between the 'AVP Names' and the key 'Columns' defined in the selected STG. These AVPs are the inputs while evaluating the CRD table in STG. ColumnAndAvpPair:
|
List of Output Column Avp Pairs (List) |
ColumnAndAvpPair:
|
RxTableDrivenEventTriggers service configuration is used to derive a list of event-triggers that CPS should subscribe based on table evaluation. The input columns to this table are the Media-Component-Description AVP values or any other input parameters (derived from gx-session) and the output columns give the list of applicable event-triggers. Based on the selection logic user can configure any AVP received at MCD level to the input columns. In the CRD table, output columns can give an event-trigger number. So, there can be multiple output columns depending upon the number of event-triggers that are to be supported. You need to configure all these output columns that derive the event-trigger number in the service configuration.
This service configuration is also used for configuring the STG used to specify the event-triggers to be sent in dummy GxRAR. In this case, the same service option needs to be linked to two separate CRD tables (Rx-Table or dummy RAR Event-Trigger table). So, these service-options are created by modifying the RxTableDrivenEventTriggers Use Case Template with Use Case Initiator conditions that checks for triggering dummy RAR. This avoids enabling both the service option at the same time.
The following table describes the service configuration parameters:
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Stg Name |
References the Search table group containing the CRD tables that define the Qos Action for Rx specific dynamic rules (dedicated bearer). |
List Of Input Column Avp Pairs (List) |
Defines the mapping between the 'AVP Names' and the key 'Columns' defined in the selected STG. These AVPs are the inputs while evaluating the CRD table in STG. ColumnAndAvpPair: |
List of Output Column Avp Pairs (List) |
ColumnAndAvpPair: |
When using RxTableDrivenEventTriggers for both Rx-Table event-triggers and dummy RAR event-triggers, the template must be configured with modify conditions to have two service options that can be linked to the two STG tables. The condition to modify the template for dummy RAR event-triggers must be set as per the requirement to trigger the dummy Gx RAR message.
If dummy RAR Event-Trigger table indicates no new Event-Triggers are required then the actual RAR with bearer installation will not have the correct subscription based on the Rx Table (since the Rx table event-triggers will not get evaluated). Therefore, a limitation would be that whatever entries having event-trigger subscription in Rx-Table for specific media-type that media-type will also have corresponding event-triggers enabled for dummy RAR event-trigger table also.
The EvaluateRxDedicatedBearer service configuration object evaluates the Rx dedicated bearer depending on the trigger for the policy evaluation.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Stg Name |
|
List Of Input Column Avp Pairs |
|
List Of Input Column Avp Pairs |
The ThrottleRxBasedOnBearer service configuration object enables you to throttle default bearer.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Qci |
|
Allocation Retention Priority |
|
Max Required Bandwidth U L |
|
Max Required Bandwidth D L |
The ThrottleRxBasedOnMediaType service configuration object enables you to throttle Rx calls based on media type.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Q O S Allocation Parameters (List) |
List of parameters that can be configured to enable you to throttle Rx calls with the media type as follows:
|
The BindingDbHealthCheck service configuration object is used to configure PCRF to initiate a message that results in sending dummy AAR to PolicyDRA to check if binding is available at PolicyDRA and allowing the PCRF to take corrective action based on the response.
Parameter |
Description |
---|---|
Enable Health Check |
This field is used to enable the feature for a particular APN. This field can be read from a CRD table which has mapping to an APN name. |
Destination Realm |
This field notifies the destination realm of the Policy DRA or Rx peer. |
Note | The dummy AAR sent by PCRF for PolicyDRA binding database health check is routed back to PCRF. This dummy AAR has to be ignored/rejected. To identify the dummy (health-check) AAR the diameter session ID is appended with BindingDbCheck keyword. When PCRF receives an AAR with session ID ending with BindingDbCheck keyword, it needs to be replied by using RequestReject configuration that must be enabled using the condition that makes use of session ID having BindingDbCheck keyword. For configuration, refer to RequestReject. |
This section describes the parameters for the following Sd Service Configuration Objects:
The ADCPreconfiguredRule service configuration object configures a dynamic application detection rule.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Rule Group |
Not used |
Rule Name |
Not used |
Adc Rule Name |
The name of the ADC rule. |
Tdf Application Identifier |
|
Flow Status |
|
Mute Notification |
|
Monitoring Key |
|
QoS Information |
QoSInformation For detailed information about the following parameters, see Common Parameter Descriptions. |
Redirect Information |
RedirectInformation For detailed information about the following parameters, see Common Parameter Descriptions. |
The ADCPredefinedRule object configures a static ADC rule.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Rule Group |
|
Rule Name |
The ADCPredefinedRuleBase object configures a predefined group of ADC rules. The group can contain predefined, pre-configured, dynamic, and predefined rule base rules.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Rule Group |
|
Rule Name |
The EventTrigger service configuration object specifies the event to be sent.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Event Trigger |
The SdDynamicRuleReference service configuration object is used to define the CRD table and column details for determining the rule-name and charging-parameters for the Sd Sponsored Data Dynamic PCC Rule.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
STG Table |
The name of the Search Table group table that is being referenced. |
List Of Input Column Avp Pairs (List) |
|
List Of Output Column Avp Pairs (List) |
|
Retry Pcc Rules On Failure |
Can be set to true or false. Default: false |
The SdDefaultBearerQosADCRuleConfiguration service configuration object is used to derive ADC rules.
The following Query Table Input/Output can be used:
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Crd Tables (List) |
QueryTable Each Query Table represents a Customer Reference Data table. The application references the Input List and selects parameters and values along with it to query the table.
All inputs to CRD table must be through retrievers only. |
Realm |
See Common Parameter Descriptions. This value provides the information on the TDF node to which the Sd Diameter Interface connects. |
The SdToggleMonitoringKey service configuration object defines the monitoring-key to be used for the Sponsored Data Dynamic PCC Rule.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Monitoring Key |
This section describes the parameters for the following Service Configuration Objects:
ServiceNotificationservice configuration under the"service" section needs to be configured for the subscriber service to trigger notifications.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Enable Rx Service |
If this is set to false, no device indicator notification will be sent for Rx event. Possible values are true or false. |
Enable Sd Service |
If this is set to false, no device indicator notification will be sent for Sd event. Possible values are true or false. |
Enable Sy Service |
If this is set to false, no device indicator notification will be sent for Sy event. Possible values are true or false. |
Enable Dscp Service |
If this is set to false, no device indicator notification is sent for DSCP event. Default: false |
Rx Service Crd Column |
Resultcolumn of the CRD table. Value in this column specifies whether to send device notification or not for Rx event. To send device notification the value in the column should be"ON". Value other than "ON" will result in no device notification. |
Sy Service Crd Column |
Result column of the CRD table. Value in this column specifies whether to send device notification or not for Sy event. To send device notification the value in the column should be "ON". Value other than "ON" will result in no device notification. |
Sd Service Crd Column |
Result column of the CRD table. Value in this column specifies whether to send device notification or not for Sd event. To send device notification the value in the column should be "ON". Value other than "ON" will result in no device notification. |
Dscp Service Crd Column |
Result column of the CRD table. Value in this column specifies whether to send device notification or not for Dscp event. To send device notification the value in the column should be "ON". Value other than "ON", results in no device notification. |
Sy Service STG |
ServiceSTGConfiguration: STG Configuration for Sy Event.
|
Sd Service STG |
ServiceSTGConfiguration: STG Configuration for Sd Event.
|
Initial Off On C C R I |
Default: true |
Initial Off On Sy S L A |
Default: false |
Dscp Service STG |
ServiceSTGConfiguration: STG Configuration for DSCP Event. |
This section describes the parameters for the following Sy Service Configuration Object:
The SpendingLimitReport service configuration object is used for the 3GPP Sy interface. The Sy reference point is located between the Policy and Charging Rules Function (PCRF) and the Online Charging System (OCS). The Sy reference point enables transfer of policy counter status information relating to subscriber spending from OCS to PCRF and supports the following functions:
Request of policy counter status reporting from PCRF to OCS, and subscribe to or unsubscribe from spending limit reports (notifications of policy counter status changes).
Notification of spending limit reports from OCS to PCRF.
Cancellation of spending limit reporting from PCRF to OCS.
Parameter |
Description |
---|---|
Priority |
|
Diameter Client |
|
Subscriber Id (List) |
Identifier – The user identity, which is mapped to the Subscription-Id AVP. Based on your requirements, you can configure one or more identifiers. Possible values for identifiers include:
Skip Subscriber Id in SLR Initial – Flag to skip configured Subscriber id in SLR initial. When set to true, skips configured subscriber id in SLR initial. When set to false, subscriber id is sent in SLR initial. Default value is false. Skip Subscriber Id in SLR Intermediate – Flag to skip configured subscriber id in SLR intermediate. When set to true, skips configured subscriber id in SLR intermediate. When set to false, subscriber id is sent in SLR intermediate. Default value is false. |
Asynchronous |
This parameter can be set to true or false. True – Use asynchronous mode for Sy interface (PCRF will not wait for SLA response from OCS before sending the message on another interface like Gx.) False – Use synchronous mode for Sy interface (PCRF waits for the SLA response from the OCS or SLA timeout before sending the message on another interface like Gx.) Asynchronous mode is preferred. |
Retry Time Seconds |
Not used. |
Realm |
The Sy peer realm (OCS) where the message needs to be sent from PCRF. |
Identifier (List) |
Identifier Name – The subscribed Sy Policy Counter Identifier list, which maps to the Policy-Counter-Identifier AVP. PCRF uses this list to send the Policy-Counter-Identifiers to the OCS in the SLR message. If this list is blank, the PCRF requests subscription to all available policy counters. |
Defaults On Failure (List) |
DefaultSpendingLimitReport – The default list of Policy Counter Identifiers that are subscribed to in case of failures. This parameter is optional. |
Subscriber Id In S T R |
This parameter can be set to true or false. It specifies whether to send subscriber-id AVP in the STR message. This is a custom feature, and is not as per 3GPP standards. Default: false |
Subscriber Id In S N A |
This parameter can be set to true or false. It specifies whether to send subscriber-id AVP in the SNA message. This is a custom feature, and is not as per 3GPP standards. Default: false |
Force Create Session |
This parameter can be set to true or false. When set to true, it initiates a new Sy session (if one does not already exist) irrespective of the policy event or the re-initiation count/time. Default: false |
Resend Counter In SLR Inter Mediate |
When this flag is set to true, CPS sends counter in SLR intermediate. Default value is false. |
Receive Unknown Counter |
When this flag is set to true, CPS honors the unknown counters received in SNR message. Default value is false. |
Update Next Evaltime of session On Expiry |
When this flag is set to true, CPS keeps sending check-alive SLR based on stale session configuration and does not extend time of check-alive SLR if SNR is received. |
The Sy Action service configuration object is used to send the SLR-U during policy counter-conflicts.
Parameter |
Description |
---|---|
Priority |
The priority of the message for processing. The higher the number, the higher the priority. Default for most settings: 0 |
Diameter Client |
The client configuration is used to apply different policies based on OCS type. To filter a service based on the Diameter client, specify which Diameter client you want the service to be applied to. Diameter clients are configured in .This parameter is optional. |
Send SLR-Intermediate |
When this parameter is set to true, CPS sends an SLR-U with a list of currently subscribed policy counter-identifiers. Default value is false. |
SLR-Intermediate Max Retry |
Number of retry attempts allowed on a non-successful SLR-Intermediate request. Default value is 1. |
TableDrivenActionOverSy service configuration is used to evaluate and retrieve action to be taken over Sy interface on receiving messages. On each policy evaluation (including Gx CCR-U), if TableDrivenActionOverSy is found in policy, CPS evaluates the referenced table and determine the Action to be executed on the Sy interface. If the Action value is Update, CPS then initiates a sync SLR-Inter message (provided Sy session exists). When the SLR-Inter response is received (Result Code 7000 if there is timeout), CPS reevaluates the TableDrivenActionOverSy configuration and determines the next Action. If that Action is Reinitiate, CPS terminates the existing session and initiates a new one (by sending an SLR-Initial).
When CPS terminates the existing session, if the Standard Sy flag is false, the STR message is not sent out and instead the session is cleaned up immediately. If the Standard Sy flag is true, then a sync Sy STR is sent out. On receiving response (can be success or failure or timeout), CPS cleans up the session.
Note | To allow TableDrivenActionOverSy to be evaluated properly for timeouts, the Policy Director (LB) node must send back the 7000 response before the Sync action (for sending SLR-Inter message) times out. Also, CPS by default, retries the timed out request once directly from the Policy Director (LB) node. |
Parameter |
Description |
||
---|---|---|---|
Priority |
|||
Diameter Client |
|||
Search Table Group |
Search Table Group table that is being referenced. The STG (and the contained CRDs) can also contain key columns that do not directly refer to Diameter AVPs in the trigger message. For example, Outputs of other tables. These columns must be bound correctly. |
||
Input Column Binding (List) |
ColumnAndAvpPair |
||
Output Column Binding (List) |
ColumnAndAvpPair
|
Note | TableDrivenActionOverSy service configuration only accepts trigger Diameter message AVPs for Input column binding. Thus, the AVP Code has to exactly match to what is received in the message. In addition to message AVPs, the following AVP codes can be used as input AVP codes:
|
The ADTMAttribue service configuration object is used to specify the attribute name which should be a LDAP attribute.
The following table describes the service configuration parameters:
Parameter |
Description |
---|---|
Attribute Name |
This parameter is used by CPS to inform UDC about the attribute update. |
Logical Apn |
Specifies the different Logical APN values for the encoded LDAP Attribute value. |
For more information, refer to ADTMAttribute Service Configuration Object section in CPS UDC Guide.
These parameters are common between many service configuration objects. They are listed in alphabetical order.
Parameter |
Description |
---|---|
Defines the total bandwidth usage for the downlink direction of non-GBR QCIs at the APN. |
|
Defines the total bandwidth usage for the uplink direction of non-GBR QCIs at the APN. |
|
Arp |
AllocationRetentionPriority |
Balance Code |
Indicates with which balance the quota is associated. You can subscribe to multiple balances, but the monitoring key is associated with one balance. |
The client configuration is used to apply different policies based on PCEF type. To filter a service based on the Diameter client, specify which Diameter client you want the service to be applied to. Diameter clients are configured in the section of the interface. This parameter is optional. |
|
Dosage |
How much quota to initially give the client (in bytes). Default: 0 |
Dual Stack Session |
Can be set to enabled or disabled. Default: disabled |
Enable Resource Allocation Notification |
Can be set to enabled or disabled. Default: disabled |
Encoding Format |
Can be set to true or false. If the Monitoring Key parameter is numeric, set this parameter to true. Default: false |
Event Trigger |
Used primarily to notify the starting and stopping of applications or to report usage. It is not used to rerequest rules. |
Flow Status |
Defines whether the service data flow is enabled or disabled. |
Framed I P Type |
Can be set to one of the following options: Default: ANY_ONE |
Defines the guaranteed bit rate allowed for the downlink direction. |
|
Defines the guaranteed bit rate allowed for the uplink direction. |
|
List of Input Column Avp Pairs (List) |
Defines the mapping between the AVP Names and the key columns defined in the selected STG. These AVPs are used as inputs while evaluating the CRD table in STG. |
List Of Output Column Avp Pairs (List) |
Defines the mapping between the AVP Names and the output columns defined in the selected STG. These mappings indicate how the output columns' values are mapped to AVPs after the CRD is evaluated. |
Defines the maximum bit rate allowed for the downlink direction. |
|
Defines the maximum bit rate allowed for the uplink direction. |
|
Monitoring Key |
Identifies a usage monitoring control instance. You can specify any value. |
Monitoring Level |
Can be set to one of the following values: |
Mute Notification |
Indicates whether notifications for application starts and stops are muted for ADC Rule by the TDF. |
New String Value |
The new string value that is used to overwrite the “String Value” if the value of “String Value” field matches exactly with the value of “String Value To Override”. |
Online |
Defines whether the online charging interface from the PCEF for the associated PCC rule is enabled. The default charging method provided by the CPS takes precedence over any preconfigured default charging method at the PCEF. |
Offline |
Defines whether the offline charging interface from the PCEF for the associated PCC rule is enabled. The default charging method provided by the CPS takes precedence over any preconfigured default charging method at the PCEF. |
Precedence |
Defines the second level priority when the highest priority matches among the multiple generic service configurations. |
When provided within the QoS-Information AVP, the AVP defines whether a service data flow can get resources that were already assigned to another service data flow that has a lower priority level. If it is provided within the Default-EPS-Bearer-QoS AVP, the AVP defines whether the Default Bearer can get resources that were already assigned to another bearer with a lower priority level.
|
|
When provided within the QoS-Information AVP, the AVP defines whether a service data flow can lose the resources assigned to it in order to admit a service data flow that has a higher priority level. If it is provided within the Default-EPS-Bearer-QoS AVP, the AVP defines whether the Default Bearer can lose the resources assigned to it in order to admit a pre-emption capable bearer with a higher priority level.
|
|
The priority of the message for processing. The higher the number, the higher the priority. Default for most settings: 0 |
|
Priority Levels |
Used to decide whether a bearer establishment or modification request can be accepted, or rejected due to resource limitations (typically used for admission control of GBR traffic). The AVP can also be used to decide which existing bearers to pre-empt during resource limitations. The priority level defines the relative importance of a resource request. Values 1 to 15 are defined, with value 1 as the highest level of priority. |
Provision Default Bearer QoS |
Must be bound to the appropriate column in the STG. The data contained in the STG column is of type True/False. If the value is True, the Default Bearer QoS information from the session is applied to the rule, while QoS information derived from the prior parameters in this STG is ignored. |
The Quality of Service (QoS) Class Identifier. The QoS class identifier identifies a set of IP-CAN specific QoS parameters that define QoS, excluding the applicable bitrates and ARP. It is applicable both for uplink and downlink direction. The QCI values 0, 10 to 255 are divided for usage as follows: |
|
Rating Group |
The charging key for the PCC rule used for rating purposes. |
Realm |
The destination realm where the message is sent from PCRF. |
Redirect Address |
Indicates the target for redirected application traffic. |
Redirect Address Type |
Defines the address type of the address given in the Redirect-Server-Address AVP. Default: IPV4_ADDRESS |
Redirect Server Address |
Indicates the target for redirected application traffic. |
Redirect Support |
This value indicates that Redirection is enabled for a detected application's traffic. |
Retry Profile |
Indicates the Rule Retry Profile to be used. When CPS receives a Charging-Rule-Report indicating failure to install or to activate one or more rules, it evaluates the failed rules and takes further action. |
Rule Group |
Used to classify rules at PCRF to change set of predefined rules based on policy. This parameter is optional. |
Rule Name |
A partial name configured in Policy Builder (as derived using AF-Application-Identifier and Media-Type values from the Custom dynamic rule name table in Gx Client). Default: AF |
Scheduled Hour |
Can be set to one of the following values: Default: Turns off the Hour Boundary RAR enhancement feature for look-ahead rules installation at hour boundary. This causes rules to be installed at hour boundary as applicable. CurrentHour: Rule activation time will be current time, deactivation time will be the next hour. NextHour: Rule activation time will be the next hour, and deactivation time will be next-next hour. |
Search Column |
Must be bound to the Key column in the STG. The data contained in the STG column is of type Text. |
Search Group |
A constant value that CPS uses to search within the Search Table Group indicated by the Search Table parameter. |
Search Table |
The name of the table from which to perform a lookup. |
String Value to Override |
Indicates whether overriding is required. For virtual services, if the value of “String Value” field matches exactly with the value of “String Value To Override”, then the value of “String Value” is over written with the “New String Value". |
Tdf Application Identifier |
References the application detection filter (for example, its value may represent an application such as a list of URLs) to which the PCC rule for application detection and control in the PCEF applies. |
ToD Schedule |
Identifies the schedule for rule activation and deactivation. |