TableDrivenDynamicPccRule

This section describes the parameters for the TableDrivenDynamicPccRule configuration.

TableDrivenDynamicPccRule service configuration object provides a mapping between the PCC rule attributes and the CRD table that backs the service. A one-to-many relation is supported between the service configuration object and the PCC rules.

Before setting the service parameters, ensure that you create a use case template and add a service for this configuration. For details, see Configuring the Use Case Template and Adding a Service.

The following table describes the TableDrivenDynamicPCCRule service parameters.

TableDrivenDynamicPCCRule Parameters
ParameterDescription
Priority

The priority assigned for this service configuration object (among similar service configuration objects) is used for policy evaluation by the Policy Engine. Higher the value, higher is its priority.

Default: 0

Search TableThe CRD table that is to be queried for the PCC rule data.
Search ColumnPrimary key column in the table configured under the Search Table field.
Search ValuePrimary key value for the column configured under Search Column.
Input List (List)Additional primary key column-value pairs in the table configured under the Search Table field.
PCC Rule Id SourcePCC Rule Id column in the table that is configured under the Search Table field corresponding to the pccRuleId attribute.
Precedence SourcePrecedence column in the table that is configured under the Search Table field corresponding to the precedence attribute.
App Id SourceApp Id column in the table that is configured under the Search Table field corresponding to the appId attribute.
QoS Id Source

QoS Id column in the table configured under the Search Table field corresponding to refQosData attribute.

Per 3GPP TS 29.512 v15.1.0, refQosData can be an array of string objects. To accommodate multiple string values in the CRD, the following convention is used:

  • The different refQosData objects are separated by “,”.

  • Any blank characters before and after the actual data is dropped.

Chg Id Source

The value must be bound to the Chg Id column in the STG. The value in the STG column must be of Type Text.

Flow Information Source

Flow Information column in the table configured under the Search Table field corresponding to flowInfos attribute.

Per 3GPP TS 29.512 v15.1.0, flowInfos can be an array of FlowInformation objects. To accommodate multiple FlowInformation values in the CRD, the following convention is used:

  • The different FlowInformation objects are separated by “,”.

  • The different attributes within each FlowInformation object are separated by “;”.

  • ethFlowDescription attribute within FlowInformation is not currently supported.

  • The expected format for each FlowInformation attribute is as follows: flowDescription;packetFilterUsage;tosTrafficClass

    ;spi;flowLabel;flowDirection .

  • If any of the FlowInformation is missing, leave the corresponding placeholder empty while preserving the format (for example tosTrafficClass and spi are missing: flowDescription;packetFilterUsage;;;flowLabel;flowDirection)

  • Any blank characters before and after the actual data is dropped.

  • The values that are allowed for flowDirection attribute are the ones that are specified in 3GPP TS 29.512, section 5.6.3.3 Enumeration: FlowDirection.