| Oracle® Communications Service Broker Policy Controller Implementation Guide Release 6.0 Part Number E23528-02 |
|
|
View PDF |
| Oracle® Communications Service Broker Policy Controller Implementation Guide Release 6.0 Part Number E23528-02 |
|
|
View PDF |
This chapter explains how to install and configure a Policy Controller implementation.
Policy Controller is a part of Oracle Communications Service Broker 6.0, so you must install that release. For details on installation see Oracle Communications Service Broker Installation Guide. Be sure to select the Policy Controller 6.0.0.0 option during the installation.
You must create a Service Broker managed server and domain for each Policy Controller implementation. See the discussions on creating the domain and adding a managed server to the domain in Oracle Communication Service Broker Installation Guide for details. That manual also has instructions for starting the domain and managed server.
This chapter explains how to configure a Policy Controller implementation. This section assumed that you have installed Policy Controller as part of Oracle Communications Service Broker 6.0 and created a domain for it as described in "About Creating a Domain and Managed Server for Policy Controller".
Configuring a Policy Controller implementation involves these tasks:
Create, configure, and provision a Service Broker Subscriber Profile Store to store subscriber data for Policy Controller to use.
Configure the Service Broker SSU Diameter to connect the Policy Controller PCRF to AFs (Application Functions) and PCEFs (Policy and Charging Enforcement Functions).
Configure Policy Controller Global Parameters.
Configure Policy Controller System Parameters.
Configure Policy Controller Data Store (BDB or JDBC).
Configure Your PCEF Server to work with Policy Controller.
Configure your AF server to work with a Policy Controller.
Configure and start the Policy Designer.
Policy Controller obtains individual subscriber information from a Subscriber Profile Repository (SPR) set up for that purpose. Policy Controller uses SPR data to interpret policy rules, and decide which services and bandwidth levels a subscriber is entitled to. The Service Broker Subscriber Store feature is an SPR designed for this purpose. See Oracle Communications Service Broker Subscriber Store User's Guide for instructions on how to set up Subscriber Store, provision it with data for the Policy Controller to use, and configure an Sp reference point to communicate with.
If you use another SPR for this purpose, see that product documentation for instructions on how to configure and provision that SPR, and communicate with its Sp reference point.
Table 2-1 lists the default Subscriber Store parameters.
Table 2-1 Policy Controller Subscriber Profile Parameters
| Parameter | Multiciplicity | Level | Data Type | Description |
|---|---|---|---|---|
|
Subscriber-Id |
1..* |
N/A |
String |
The subscriber ID value. |
|
Subscriber-Id-Type |
1..* |
N/A |
Integer |
The subscriber ID type. |
|
accountState |
1 |
Global |
String |
The status of the account, such as active or inactive. |
|
AccountType |
1 |
Global |
String |
Can be Prepaid, Postpaid, Hybrid. |
|
SubscriberActivationDate |
1 |
Global |
Calendar |
A calendar date in the form of YYYYMMDD. |
|
DateOfBirth |
1 |
Global |
Calendar |
A calendar date in the form of YYYYMMDD. |
|
SubscriberCategory |
1 |
PCRF |
String |
These are the plan categories that you create to sell to subscriber. For example premium, average, and economy. |
|
HomeZone |
* |
PCRF |
HomeZone |
The subscriber's home zone, indicating the subscriber's location and location type. |
You can extend subscriber profiles with any number of key-value pairs that your Policy Controller implementation requires. For details on using the Subscriber Store API to add key/value pairs, see Oracle Communications Service Broker Subscriber Store User's Guide.
Set your PCEF servers and AFs (application functions) as a Diameter peers, and define Diameter routing rules that directs all Gx service data flow from your PCEF to Policy Controller, and Rx service data flow from Policy Controller to the AF with the following steps. This section assumes that you know the host name and IP address of each of your PCEF and AF servers.
For details on the supported Gx and Rx messages see "Gx Command Codes Supported by Policy Controller" and "Diameter Rx Command Codes Supported by Policy Controller".
Open the Service Broker Administration Console.
Navigate to Platform, OCSB, Signaling Tier, SSU Diameter, DIAMETER, then Diameter Configuration.
Click Edit, then the plus sign button to create a node (if not using the default).
Click the Peers subtab.
Click the plus sign button to create a new peer.
In the New Data popup screen, enter your PCEF identifying data:
Address - The URL of your PCEF server.
Host - The host name of your PCEF server.
Port - A server port number to use on your PCEF.
Protocol - A service data flow protocol to use.
Watchdog - Enables/disables the watchdog timer.
Click OK.
Repeat these steps to specify each of your PCEF servers and AF servers as a peer.
The Diameter SSU routing rules specify how the PCEF and AF server service data flow is routed through Policy Controller. Use the following steps to create these routing rules:
Open the Service Broker Administration Console.
Navigate to Platform, OCSB, Signaling Tier, SSU Diameter, SSU Diameter, Routing, then Incoming Routing Rules.
Click Edit, then New to create a new Incoming Routing Rule for Gx traffic.
Name: Enter an informal name for the new rule.
Priority: Leave the 0 default priority.
Module Instance: Enter ssu:ocsb/pcrf.
Click OK.
Click the Incoming Routing Criteria subtab to define the Gx traffic routing criteria.
Select your new incoming routing rule from the Parent dropdown list.
Click New and enter the following routing rule criteria for Gx traffic:
Name: Enter an informal name for the criteria.
Attribute: Select APPLICATION_ID from the dropdown list.
Value: Enter 16777238 to specify Gx service data flow.
Click the Incoming Routing Rules subtab.
Click New to create a new Incoming Routing Rule for Rx traffic.
Name: Enter an informal name for the new rule.
Priority: Leave the 0 default priority.
Module Instance: Enter ssu:ocsb/pcrf.
Click the Incoming Routing Criteria subtab to define the Rx traffic routing criteria.
Select your new incoming Rx routing rule from the Parent dropdown list.
Click New and enter the following routing rule criteria:
Name: Enter an informal name for the criteria.
Attribute: Select APPLICATION_ID from the dropdown list.
Value: Enter 16777236 to specify Rx service data flow.
Click Commit to save your new rules.
This section lists the Policy Controller global parameters that you must approve or change before using Policy Controller.
This section assumes that you have acquired and configured a rating engine and know the values you use to indicate rating groups and PCC service identifiers.
This section lists Policy Controller parameters that you set by using the Service Broker Administration Console.
By default Policy Controller comes with the global parameters listed in Table 2-2.
Table 2-2 Default Policy Controller Global Parameter Settings
| Global Parameter | Default Value | Data Type | Description |
|---|---|---|---|
|
revalidation-time |
14400000 (4 hours) |
Milliseconds |
The maximum time before your PCEF should trigger Policy Controller. |
|
events-subscribed |
15,16,17,22 |
Comma-separated list of integers |
Specifies the list of 3GPP 29.211 event triggers to use. This field accepts the integer values that represent the Event-Trigger AVP. See the 3GPP 29.211 specification for a complete list. The default trigger events are:
|
|
primary-event-charging-fn |
N/A |
URL |
The primary online charging server address. |
|
secondary-event-charging-fn |
N/A |
URL |
The secondary online charging server address. |
|
primary-charging-collection-fn |
N/A |
URI |
The primary online collection server address. |
|
secondary-charging-collection-fm |
N/A |
URL |
The secondary online collection server address. |
|
online |
N/A |
Boolean |
Specifies whether online charging is allowed. |
|
offline |
N/A |
Boolean |
Specifies whether offline charging is allowed. |
|
access-nw-charging-address |
N/A |
URL |
A credit card charging IP address to use. |
|
install-default-plan |
true |
Boolean |
Whether to automatically install the default Policy Profile. |
Set Policy Controller system parameters in the PCRF tab of the Service Broker Administration Console with the following steps:
Bring up the Service Broker Administration Console.
Navigate to PCRF, OCSG, Execution Blocks, then System Parameters.
Click the PCRF System Parameters tab, then the Global Parameters subtab.
Click Edit.
Enter the required new values in the fields displayed.
Click Apply.
Click Confirm.
The Default Execution Blocks tab (under the PCRF tab of the Administration Console) is reserved for Oracle use.
By default, Policy Controller uses the timers and timer values listed in Table 2-3 to control and protect Rx and Gx sessions. These settings work for a test and evaluation system and may also work for a production implementation. Configure them to fit your implementation's requirements.
Table 2-3 RX and Gx Timer Names, Default Values, and Descriptions.
| Timer | Timer Name (alternate name) | Default Value (ms) | Description |
|---|---|---|---|
|
Gx Session Duration timer |
TGXSESSION (Tcc) |
36000000 |
Determines how long to keep sessions with pending Gx traffic open. Prevents stale sessions and releases session-related information. This timer is started on each Gx CCA-Initial or CCR-Update message, and canceled on any subsequent Gx CCR received from the network. |
|
Gx Session Guard Timer |
TGXGUARD (Tg) |
1000 |
This timer is started each time a Gx request arrives at the PCRF, and is canceled when the response is sent. If the timer expires the response is sent with an result code of 3002. |
|
Rx Session Duration Timer |
TRXSESSION (Tcc) |
36000000 |
Determines how long to keep sessions with pending Rx traffic open. Prevents stale sessions and releases session-related information. This timer is started by the Rx AAR-Initial message, and canceled by the STR message. |
|
Rx Session Guard Timer |
TRXGUARD (Tg) |
1000 |
Determines how long to keep sessions with pending Rx traffic open. Prevents stale sessions and releases session-related information. This timer is started on each Rx CCA-Initial or CCR-Update message, and canceled on any subsequent Gx CCR received from the network. |
Change each timer settings with the following steps:
Bring up the Service Broker Administration Console.
Navigate to PCRF, OCSG, Execution Blocks, then System Parameters.
Click the PCRF System Parameters tab, then the Timers subtab.
Click Edit.
Select a timer to change.
Click Update.
An Update window appears.
Enter new values in the timer-value fields.
Click OK to make your changes take effect.
Policy Controller requires that you set up persistent data storage using the Data Storage feature. For information on setting up data storage, see the discussion on configuring data storage in Oracle Communications Service Broker Installation Guide.
This section explains the steps necessary to make your PCEF server work with Policy Controller. For details on the tasks to perform see your PCEF product documentation.
See your PCEF product documentation for instructions on how to set up and configure your PCEF server. Specifically:
Configure your PCEF server to use the Diameter Gx messages listed in "Gx Command Codes Supported by Policy Controller".
This section explains the steps necessary to make your AF Server work with the Service Broker Policy Controller. For details on the tasks to perform see your AF product documentation.
Configure your PCEF server to use the Diameter Gx messages listed in "Diameter Rx Command Codes Supported by Policy Controller".
The following sections explain how to start and configure Policy Designer.
Use the following steps to start Policy Designer:
Log on to the Service Broker system on which you created the Policy Controller domain.
Start the web access Administration Console with these commands (this also starts the Policy Controller JETTY server):
cd Oracle_home/ocsg60/admin_console
./web.sh Domain_configuration_directory
Where:
Oracle_home is the Oracle Home directory you defined when you installed Service Broker.
Domain_configuration_directory is the path to the domain configuration directory.
Note:
If you use basic authorization (axia.basic.auth=true in Oracle_home/ocsg60/admin_console/properties/web.properties) you will be prompted for two sets of credentials to use when starting the Administration Console. The first set is required to access the Administration Console, and the second set is required to access the Policy Designer user interface.Note:
The Policy Controller does not work with the stand-alone version of the Administration Console.Start the managed server you created during installation with these commands:
cd Oracle_home/ocsg60/managed_server
./start.sh Managed_server_name file:///Domain_configuration_directory/initial.zip
Where:
Oracle_home is the Oracle Home directory you defined when you installed Service Broker.
Managed_server_name is the name of the managed server file you created.
Domain_configuration_directory is the path to the domain configuration directory.
Open a web browser.
Enter one of these Policy Designer URLs:
(SSL off) https: // [ localhost | IP_Address ] : Port_Number /policydesigner
(SSL on) http: // [ localhost | IP_Address ] : Port_Number /policydesigner
Where:
IP_Address is the IP address of the Service Broker server running Policy Controller.
Port_Number is the server port number to use. The defaults are 8090 (SSL off) and 8091 (SSL on). You can change these default port numbers by using the oracle.ocsb.app.rcc.pcrf.gui.port (SSL off) or pcrf.gui.http.port.secure (SSL on) system property.
If you enabled basic authorization (axia.basic.auth=true in Oracle_home/ocsg60/admin_console/properties/web.properties) you are prompted for the username and password that you entered when you created the Policy Controller domain.
This example starts the Policy Designer with SSL off on your local system using the default port number:
http://localhost:8090/policydesigner
Note:
If SSL is off, use http, not https to avoid ssl_error_rx_record_too_long errors.For information on changing the default port number, see Setting the Policy Designer Port Number.
The default Policy Designer uses port 8090. You can change this by following these steps:
Open a command-line shell.
Add this entry to the Oracle_Home/admin_console/common.properties file:
If you set SSL to false:
oracle.ocsb.app.rcc.pcrf.gui.port=Port_Number
If you set SSL to true:
pcrf.gui.port.secure=Port_Number
Where Port_Number is the new port number to use.
Restart the Administration Console. For details, see the discussion on starting the Web Administration Console Server in Oracle Communications Service Broker System Administrator's Guide.
By default, the Policy Designer process is started when you start the Service Broker domain that contains it. To prevent this automatic startup, use the following steps:
Add this entry to the Oracle_Home/admin_console/common.properties file:
oracle.ocsb.app.rcc.pcrf.gui.disable=true
A value of true disables the automatic startup. If this entry is false or missing, the Policy Designer starts automatically.
Restart the Administration Console. For details, see the discussion on starting the Web Administration Console Server in Oracle Communications Service Broker System Administrator's Guide.
|
 Copyright © 2011, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|