Step 1

Log into Policy Builder.

Step 2

Select the Services tab, and then click Use Case Templates > Summary.

Step 3

Click Use Case Template link from the right side under Create Child to create a use case template for PreConfiguredRule.

Step 4

Enter the name for use case template. For example, name the new template as PreConfiguredRule.

Step 5

Select Actions tab.

Step 6

Click Add to open the Select Service Configuration dialog box.

Step 7

Select PreConfiguredRule, PreDefinedRule, and PreDefinedRuleBase one after another, and select the required service configuration parameters.

Step 8

Click OK to add the service in the Service Configuration pane.

Step 9

On the Services tab, click Services > Service Options to create a service option and add the configured use case template.

Step 10

On the Services tab, click Services > Services to create a service and add the configured use case template.

Step 1

Since this approach leverages Custom Reference and Search Table Group capabilities of CPS, we need to configure a Search Table Group to be able to use the above Service Configuration to configure a Search-Group-Table with the output column specified.

Step 2

It is possible to retrieve the redirect Address related elements of CISCO Service Group QoS from another table.

Step 1

Log into Control Center.

Step 2

Select the Configuration tab, and then select Configuration > Reference Data.

Step 3

Select the STG created in Policy Builder and add data by creating new rows.

Step 1

Log into Control Center.

Step 2

Select Configuration > Configuration > Reference Data.

Step 3

Select the STG created in Policy Builder and add data by creating new rows.

Step 1

Log into Policy Builder.

Step 2

Select the Reference Data tab.

Step 3

From the left pane, select Diameter Clients.

Step 4

Expand the Gx Clients by clicking on the arrow right next to “Gx Clients”. If you do not see this arrow, this means the Gx Client has not been created.

Step 5

Select the Gx Client name created by you. Gx Client attributes as shown below will come up in the right pane.

Step 6

Click Add to configure the emergency APNs. The following window is displayed.

Step 7

Type the name of the emergency APN that you want to add in the Value to Add (String) text box and click Add.

Step 8

Click OK. In the example shown above, four APN entries are already added.To remove an APN from this list, select the APN to be removed and click Remove.

Step 1

Log into Policy Builder.

Step 2

Select the Services tab.

Step 3

From the left pane, select Domains.

Step 4

Select the domain name that you want to use for emergency subscribers. Domain attributes open up in the right pane.

Step 5

Select the Advanced Rules tab.

Step 6

Click select near Anonymous Subscriber Service.

Step 7

In the new window displayed, select the service that you want to assign for emergency sessions and click OK.

Step 1

Log into Policy Builder.

Step 2

Select the Reference Data tab.

Step 3

From the left pane, select Systems and expand your system name or cluster name.

Step 4

Select and expand the Plugin Configurations.

Step 5

Select Diameter Configuration. Diameter configuration screen appears in the right pane.

Step 6

Check Inbound Message Overload Handling check box.

Step 7

Click Add under Message Handling Rules table.

Step 8

Click ... in the Diameter Client column.

Step 9

Select the Gx Client in which we added the emergency APNs in Configure Diameter Gx Client for Emergency APNs and click OK.

Step 10

Configure the other parameters of the table.

Note	For the detailed explanation of all the parameters of the Inbound Message Overload Handling feature, refer Inbound Message Overload Handling. The following table explains the parameters relevant to the prioritization of emergency sessions.

Table 16. Prioritization of Emergency Session - Parameters

Parameter	Description
Default Priority	Default priority to be assigned to an incoming message, if no specific one is defined in the Message Handling Rules table. Default value is 0.
Emergency Message Priority	Default priority assigned to incoming messages related to an emergency session. Default value is 0.
Message Handling Rules	Defines specific inbound message overload handling rules based on different criteria. Message Handling Rules are generic. This means for all CCR-I messages, if you want to process with priority, user needs to set the configuration in Message Handling Rules.

Note

Higher the value of the priority, the higher is the priority. User must take care that the Emergency Message Priority field value is higher than the priority column values present in the Message Handling Rules, so that the Emergency Messages are processed first than the usual messages. If we take the example values configured above, then this is how the priority is assigned to the incoming messages.

Incoming Message	Priority	Description
Any message for any emergency session/APN	5	The default emergency message priority is assigned as this is emergency APN.
A Gx CCR-I message for the non-emergency APN	3	The protocol, command code, and request type match the message handling rules.
A Gx CCR-U message for the non-emergency APN	0	Request type does not match with the value in the “Message Handling Rules”. So, the default priority is assigned.

Note	By default, the emergency message priority is higher than the default priority. This means, if you do not configure the Inbound Message Overload Handling, then default priority = 0 and emergency message priority = 1.

Step 1

Log into Policy Builder.

Step 2

Select the Services tab, and then click Use Case Templates > Summary.

Step 3

Click Use Case Template link from the right side under Create Child to create a use case template for PreDefinedRuleBase.

Step 4

Enter the name for use case template. For example, name the new template as PreDefinedRuleBase.

Step 5

Select Actions tab.

Step 6

Click Add to open Select Service Configuration.

Step 7

Select PreDefinedRuleBase and click required service configuration parameters that need to be configured. Click OK to add the service in Service Configuration pane.

• In order to achieve the RAN congestion use case to install rules based on congestion levels, we need to configure use case initiators to modify the rules based on congestion level.

  • Use case initiator - on condition that congestionLevel = 1, changes rulename to internetlvl1

  • Use case initiator - on condition that congestionLevel = 2, changes rulename to internetlvl2

  • Use case initiator - on condition that congestionLevel = 3, changes rulename to internetlvl3

• Assume congestionLevel is 1 for current hour and 2 for next hour. When services are evaluated for current time, this evaluates only to internetlvl1. In order to also evaluate services for the look ahead hour, we need to add corresponding modified rules for each with use case initiators as follows:

  • Use case initiator - on condition that congestionNextHourLevel = 1, changes rulename to internetlvl1

  • Use case initiator - on condition that congestionNextHourLevel = 2, changes rulename to internetlvl2

  • Use case initiator - on condition that congestionNextHourLevel = 3, changes rulename to internetlvl3

Example of configuration for one of the use case modifiers is shown below:

Step 1

Log into Control Center.

Step 2

Select Configuration > Configuration > Reference Data.

Step 3

Select the STG created in Policy Builder and add data by creating new rows.

A sample configuration is as follows:

Note	0-3 are congestion levels Currently, we supports only current and next level congestion.

Step 1

Login to Policy Builder.

Step 2

Select the Services tab, and then click Use Case Templates > Summary.

Step 3

Click Use Case Template link from the right side under Create Child to create a use case template for TableDrivenCiscoQosGroupRule.

1. Enter the name for use case template. For example, name the new template as UsageMonitoringKey.

2. Select Actions tab.

3. Click Add under Service Configurations.

   Select Service Configuration dialog box opens, and all of the service configuration objects that are available on the PCRF are listed.

4. Scroll down to the gx area in the list of service configuration objects, and select the required usage monitoring object. For example, UsageMonitoringKey.

   For parameter descriptions under UsageMonitoringKey, refer to UsageMonitoringKey.

   For parameter descriptions under UsageMonitoringKeyDual, refer to UsageMonitoringKeyDual.

Step 4

In the left pane of the Services tab, click Services > Service Options to create a service option and add the UsageMonitoringKey use case template.

Step 5

In the left pane of the Services tab, click Services > Services to create a service and add the configured UsageMonitoringKey use case template.

Step 1

Log into Policy Builder.

Step 2

Select the Services tab and then click Use Case Templates.

Step 3

If you want to create a new use case template, click Use Case Template in the main window under Create Child to open the default use case template.

Step 4

Enter the name for the template. For our example, name it as Bandwidth Monitoring.

Step 5

Select Actions tab.

Step 6

Click Add under Service Configurations to open the Select Service Configuration dialog box.

Step 7

Select the necessary service configuration objects and click OK to add the objects in Service Configurations pane.

Step 8

Click Services > Service Options > name of the Use Case Template.

Step 9

Click Service Options in the main window under Create Child to open the Select Service Configuration dialog box, which contains already defined Service Configurations, and click OK.

Step 10

Select BandwidthMonitor from the Service Configurations pane.

1. We can monitor the Bandwidth usage on a per session rule base or per PCC rule base. For example, let us name this bandwidth monitor per session base as SESSION.

2. Under Monitoring Key, enter the values for Monitoring Key, Dosage, and Monitoring Level. For session level, the Monitoring Level should be 0.

3. Also enable the BaseUsageMonotoringKey.

4. Under Bandwidth Threshold, define three levels for bandwidth - Low, Medium and High.

Step 11

Click Services > Service Options > name of the Use Case Template.

Step 12

Click Use Case Option in the main window under Create Child to open the Use Case Option pane and name it as Low Bandwidth Usage.

Step 13

Click Add to open the Select Service Configuration dialog box, select DefaultBearerQoS and click OK to add the service.

Step 14

Rename the configured service as LowDefaultBearerQoS.

Step 15

Click Use Case Initiators tab. Click plus sign (+) to add a service initiator. Rename the initiator as Low.

Step 16

Under Conditions, click Add to open the Select the Condition Phrase which you would like to use dialog box, select the required condition and click OK.

Step 17

Click Add All under Available Input Variables.

1. In the Value column under name (String), enter the name for the bandwidth monitor that you specified in 10.a.

2. In the Value column under label (String), enter the Bandwidth threshold value defined in 10.d.

Step 18

Create another initiator and add the condition A bandwidth monitor status does not exist to it. Add the name (String) to the condition.

Step 19

Repeat the steps from Step 12 to Step 17 for Medium and High bandwidth usage.

Step 20

Click Services > Service Options > name of the Use Case Template provided in Step 4. Add all the service configurations.

Step 21

Define the different parameters for low, medium and high bandwidth usage monitoring in the Service Configurations pane according to the customer requirements.

A sample configuration for Low Bandwidth Usage Monitoring is shown below.

Step 22

Click Services > Services, and the click Service under Create Child to open the Service dialog box.

Step 23

Enter the name in Code and Name text fields.

Step 24

Click Add to open the Select Service Configuration dialog box. Select the service that you configured in Step 4, and click OK.

Step 25

Select Use V9 Event Trigger Mapping and Rel8 Usage Monitoring Supported under Diameter Configuration.

Step 1

Log into Policy Builder.

Step 2

Select the Services tab, and then click Use Case Templates > Summary.

Step 3

Click Use Case Template link from the right side under Create Child to create a use case template.

Step 4

Enter the name for the template. For our example, name the new template as CiscoOverrideControl.

Step 5

Select Actions tab.

Step 6

In the newly created template, click Add under the Service Configurations pane. This will list all the service configuration objects available on the PCRF. Select the CiscoOverrideControl object from the gx section.

Step 7

After selecting the necessary service configuration object, click OK to add the object in Service Configurations pane.

                        Override-Control  
                        		*Override-Rule-Name  
                        		Override-Charging-Action-Parameters  
                                            Override-Control-Merge-Wildcard 
                        			Charging-Action-Name  
                        			*Online-Charging-Action-Exclude-Rule  
                        			Override-Charging-Parameters  
                        			Override-Service-Identifier 
                        				Override-Rating-Group  
                        				Override-Reporting-Level  
                        				Override-Online  
                        				Override-Offline  
                        				Override-Metering-Method  
                        			Override-Policy-Parameters  
                        				Override-QoS-Information  
                        					Override-QoS-Class-Identifier  
                        					Override-Max-Requested-Bandwidth-UL  
                        					Override-Max-Requested-Bandwidth-DL  
                        					Override-Guaranteed-Bitrate-UL  
                        					Override-Guaranteed-Bitrate-DL  
                        					Override-Allocation-Retention-Priority  
                        						Override-Priority-Level  
                        						Override-Pre-emption-Capability  
                        						Override-Pre-emption-Vulnerability   
                    

Step 1

Log into Policy Builder.

Step 2

Click REFERENCE DATA > Custom Reference Data Tables > Search Table Groups.

Step 3

Click Search Table Group.

Step 4

Under Table Search Initiators do the following to evaluate the CRD such that the condition is always false and table is not evaluated every time on any event by the policy engine:

1. Click the + sign to add an initiator.

2. Enter a name for the initiator in the Initiator Name field.

3. Select A customer reference data AVP exists as the initiator conditions.

4. Select A customer reference data AVP exists, click the Add code, and then enter CRD-CODE (dummy value to restrict CRD evaluation) as the code value. Similarly, click Add value, and then enter true as the value.

Step 5

Click the Custom Reference Data Table link.

Step 6

Under Columns, click Add and enter the following input and output values:

Step 7

Select the Services tab, and then click Use Case Templates > Summary.

Step 8

Click the Use Case Template link from the right side under Create Child to create a use case template.

Step 9

Enter the name for the template. In this example, name the new template as ActionBasedOnGxEventTrigger .

Step 10

Click the Actions tab.

Step 11

In the newly created template, click Add under the Service Configurations pane. This will list all the service configuration objects available on PCRF. Select the ActionBasedOnGxEventTrigger object under the gx section.

Step 12

Click OK to add the object in Service Configurations pane.

Step 13

Click Use Case Initiators and do the following so that the use case is true only in the following conditions:

1. Click the + sign to add a service initiator.

2. Enter a name for the initiator in the Initiator Name field.

3. Select A Gx Event Triggr exists as the initiator conditions.

4. Select A Gx Event Triggr exists, click the Add All, and then enter 46 as the eventTrigger value.

1. Click the + sign to add a service initiator.

2. Enter a name for the initiator in the Initiator Name field.

3. Select CustomCiscoEvent as the initiator conditions.

4. Select A Cisco Custom Gx Event Trigger exists, click the Add All, and then enter 5 as the eventTrigger value.

5. Select A Gx Event Trigger exists as the initiator conditions.

6. Select A Gx Event Trigger exists, click the Add All, and then enter 46 as the eventTrigger value.