| Oracle® Communications Service Broker Modules Configuration Guide Release 6.1 Part Number E29454-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Communications Service Broker Modules Configuration Guide Release 6.1 Part Number E29454-01 |
|
|
PDF · Mobi · ePub |
This chapter describes how to set up an IM-OCF PCP interworking module.
The process of IM-OCF PCP setup requires the following:
Adding an IM-OCF PCP to your Oracle Communications Service Broker deployment. You can add as many modules of type IM-OCF PCP as you need. See "Adding an IM-OCF PCP to the Service Broker Deployment" for more information.
Configuring the IM-OCF PCP. See "Configuring an IM-OCF PCP" for more information.
To add an IM-OCF PCP:
In the domain navigation pane, expand the OCSB node.
Expand the Processing Tier node.
Expand the Interworking Modules node.
Select IM Management.
On the bottom of the IM Management pane, click New.
In the New window, fill out the fields as follows:
In the Type list, select IMOCFPCP.
In the Version list, select the required version.
In the Name field, enter a name for this module as it should appear in the list of modules. In this field, you can only use lower case letters (a-z), upper case letters (A-Z), numbers (0-9), and underscores (_). If you attempt to use a character which is not allowed, Service Broker displays the error message and prompts you to enter a different name.
Click OK.
In the notification window that reminds you to commit the changes, click OK.
To add the new IM-OCF PCP to your deployment, in the Change Center pane, click Commit.
A new module of type IM-OCF PCP is now added to your Service Broker deployment. The new module is displayed in the domain navigation pane under the Interworking Modules node.
To configure an IM-OCF PCP:
In the Change Center, click Lock & Edit.
In the domain navigation pane, under the Interworking Modules node, select the newly added IM-OCF PCP.
The IM-OCF PCP configuration consists of three main tabs:
Configuration tab
Redirection tab
Ro PCP Mediation tab - Enables you to define how IM-OCF PCP translates Ro messages to PCP messages and communicates with BRM applications. See "Configuring Ro PCP Mediation", for more information.
The IM-OCF PCP Configuration tab contains the subtabs described in Table 23-1.
Table 23-1 IM-OCF PCP Configuration Subtabs
| Subtab | Description |
|---|---|
|
Call Handling |
Enables you to define how the IM-OCF PCP handles calls. See "Configuring Call Handling Parameters" for more information. |
|
Diameter Credit Control Application |
Enables you to configure parameters specific to the IM-OCF PCP DCCA interface. See "Configuring Diameter Credit Control Application Parameters" for more information. |
|
Async Announcement Manager |
Enables you to set up how IM-OCF PCP triggers the MRF to play announcements. See "Configuring Asynchronous Announcement Manager Parameters" for more information. |
|
Monitoring |
Enables you to define how Runtime MBeans and notifications should operate. See "Configuring Monitoring Parameters" for more information. |
|
Degraded Mode |
Enables you to set up how a session is charged when an online charging server is not available. See "Configuring the Degraded Mode" for more information. |
The Call Handling tab enables you to set up how IM-OCF PCP handles sessions. Table 23-2 describes configuration parameters in the General subtab.
Table 23-2 IM-OCF PCP Call Handling General Parameters
| Name | Type | Description |
|---|---|---|
|
Termination-Cause AVP on SAL BYE |
STRING |
Specifies how to set a CCR Termination-Cause AVP when session is disconnected by an internal Service Broker SAL BYE message. Possible values:
Default value: DIAMETER_LOGOUT |
|
Termination-Cause AVP on SAL CANCEL |
STRING |
Specifies how to set a CCR Termination-Cause AVP when session is disconnected by an internal Service Broker SAL CANCEL message. Possible values:
Default value: DIAMETER_SERVICE_NOT_PROVIDED |
|
Termination-Cause AVP on SAL Final Error Response |
STRING |
Specifies how to set a CCR Termination-Cause AVP when session is disconnected by an internal Service Broker SAL final error response message. Possible values:
Default value: DIAMETER_SERVICE_NOT_PROVIDED |
|
Send CCR OnThresholdIndication |
BOOL |
Indicates whether the IMOCF should send a CCR if the received SAL message indicates a threshold has been reached. Default value: FALSE |
The Diameter Credit Control Application tab enables you to configure parameters related to the IM-OCF PCP Diameter Credit Control Application (DCCA) interface. The Diameter Credit Control Application tab contains subtabs described in Table 23-3.
Table 23-3 IM-OCF PCP Diameter Credit Control Application Subtabs
| Subtab | Description |
|---|---|
|
AVPs |
Enables you to specify Attribute-Value Pairs (AVPs) to be set in CCRs. See "Configuring AVPs" for more information. |
|
General |
Enables you to set up a DCCA dialect and enables monitor call duration. See "Configuring General Parameters" for more information. |
The AVPs subtab enables you to specify Attribute-Value Pairs (AVPs) to be set in CCRs. Table 23-4 describes the AVPs that you can specify.
Table 23-4 IM-OCF PCP DCCA AVPs Subtab Parameters
| Name | Type | Description |
|---|---|---|
|
Destination-Host AVP |
STRING |
Specifies the value to set in a CCR Destination-Host AVP. The Destination-Host AVP combined with the Destination-Realm AVP defines a Diameter destination node that communicates with the IM-OCF PCP. The IM-OCF PCP sends messages to the address you specify for the Diameter destination node. An alternative way to specify a Diameter destination node is to set the Destination-Realm AVP field with an alias of a Diameter destination node, which you define in the Diameter SSU Outbound Destination (see the discussion on configuring outbound destinations in the Diameter SSU in Oracle Communications Service Broker Signaling Server Units Configuration Guide for more information.). In this case, the Destination-Host AVP is ignored. |
|
Destination-Realm AVP |
STRING |
Specifies the value to set in a CCR Destination-Realm AVP. The Destination-Realm AVP combined with the Destination-Host AVP defines a Diameter destination node that communicates with the IM-OCF PCP.The IM-OCF PCP sends messages to the address you specify for the Diameter destination node. An alternative way to specify a Diameter destination node is to set the Destination-Realm AVP field with an alias of a Diameter destination node, which you define in the Diameter SSU Outbound Destination (see the discussion on configuring outbound destinations in the Diameter SSU in Oracle Communications Service Broker Signaling Server Units Configuration Guide for more information.). In this case, the Destination-Host AVP is ignored. If you leave this field blank, the IM-OCF works in the degraded mode. |
|
Service-Context-Id AVP |
STRING |
Specifies the value to set in a CCR Service-Context-Id AVP. Default value: 32260@3gpp.org |
|
User-Name AVP |
STRING |
Specifies the value to set in a CCR User-Name AVP. |
|
Ro Node-Functionality AVP |
INT |
Specifies the value to set in a CCR Node-Functionality AVP. Possible values:
Default value: AS |
The General subtab enables you to set up a DCCA dialect and enable monitor call duration. Table 23-5 describes the parameters you can configure.
You can set up IM-OCF PCP to trigger an MRF to play announcements. Using the Async Announcement Manager tab, you can specify the alias of the MRF that plays announcements. In addition, you set up the rules that define the announcement to be played and the way how the MRF plays this announcement. For example, you can define that the MRF plays an announcement to a calling party when the time granted for the call is over, and the mobile subscriber is located in the home network.
You set up the Announcement Manager by configuring parameters on the subtabs described in Table 23-6.
Table 23-6 IM-OCF PCP Async Announcement Manager Subtabs
| Subtab | Description |
|---|---|
|
General |
Enables you to specify the alias of the MRF that plays announcements. See "Configuring General Parameters" for more information. |
|
Async Announcements |
Enables you to set up the rules that define announcements to be played as well as to specify how the MRF plays these announcements. See "Configuring Async Announcements" for more information. |
The General subtab enables you to specify the alias of the MRF that plays announcements. Table 23-7 describes the parameter you can configure.
The Async Announcements subtab enables you to set up rules for playing announcements. In addition, you set up the rules that define the announcement to be played and the way how the MRF plays this announcement.
The subtab contains the table in which each row represents a single rule. Table 23-8 describes the parameters you can configure.
Table 23-8 Async Announcement Manager Announcements Parameters
| Name | Type | Description |
|---|---|---|
|
Name |
STRING |
Specifies the unique identifier of the rule. |
|
Enabled |
BOOL |
Specifies whether or not the announcement is enabled. Possible values:
Default value: TRUE |
|
Reason Type |
STRING |
Specifies the parameter that IM-OCF PCP checks in the CCA message received from the online charging server. When the value of the specified parameter matches the range that you defined using the Lower Limit and Upper Limit parameters, IM-OCF PCP triggers the MRF to play the announcement. Possible values:
Default value: ANY Note: When you set Reason Type to ANY, IM-OCF PCP always triggers the MRF to play the announcement. |
|
Lower Limit |
INT |
Specifies the lower limit of the range for the parameter that you specified in Reason Type. When the value of the specified parameter is greater than the value set in Lower Limit and less than the value set in Upper Limit, IM-OCF PCP triggers the MRF to play the announcement. To configure IM-OCF PCP to trigger the MRF to play the announcement, regardless of the value of the lower limit, set this parameter to -1. Note: IM-OCF PCP does not use the Lower Limit parameter if you set Reason Type to ANY. |
|
Upper Limit |
INT |
Specifies the upper limit of the range for the parameter that you specified in Reason Type. When the value of the specified parameter is greater than the value set in Lower Limit and less than the value set in Upper Limit, IM-OCF PCP triggers the MRF to play the announcement. To configure IM-OCF PCP to trigger the MRF to play the announcement, regardless of the value of the upper limit, set this parameter to -1. Note: IM-OCF PCP does not use the Upper Limit parameter if you set Reason Type to ANY. |
|
Network |
STRING |
Specifies the location of the mobile subscriber required for triggering the MRF to play the announcement. Possible values:
Alternatively, you can specify the ID of a specific MSC that serves the mobile subscriber. |
|
Service Side |
STRING |
Specifies the IM-OCF PCP's service side required for triggering the MRF to play the announcement. Possible values:
Default value: BOTH |
|
Call State |
STRING |
Specifies the call state when IM-OCF PCP triggers the MRF to play the announcement. Possible values:
Default value: PRECALL |
|
Priority |
INT |
Specifies the order in which the MRF plays different announcement when the conditions of multiple rules are met. |
|
Announcement Code |
INT |
Specifies the identifier of the announcement that the MRF plays. |
|
Threshold |
INT |
Specifies how much time, in seconds, prior to the end of quota, IM-OCF PCP triggers the MRF to play the announcement. IM-OCF PCP uses the Threshold parameter only for the announcements whose Call State parameter is set to MIDCALL. Note: Setting the Threshold parameter to any positive value when Call State set to PRECALL or POSTCALL causes an error. |
The Monitoring tab enables you to define how Runtime MBeans and notifications operate for an IM-OCF PCP. For more information about configuring monitoring, see "Configuring Service Broker Monitoring" in "Monitoring Service Broker Using Runtime MBeans" in Oracle Communications Service Broker System Administrator's Guide.
In Online Mediation Solution Controller, Service Broker relies upon an external online charging server (OCS) to apply charges for the use of network services.
When an online charging server is unavailable, IM-OCF PCP switches to the special mode known as degraded mode. This mode enables IM-OCF PCP to continue a session and charge a mobile subscriber during the time when the charging server is temporarily unavailable.
When IM-OCF PCP sends an accounting request to the charging server, IM-OCF PCP waits a specified period of time for a response from the server. If the server does not respond, IM-OCF PCP switches to the degraded mode.
After IM-OCF PCP switches to degraded mode, IM-OCF PCP handles the session in until the session is terminated even if the online charging server becomes available. When the online charging server becomes available again, IM-OCF PCP sends the charging information gathered during the session to the server.
In the degraded mode, IM-OCF PCP communicates with the Service Broker local charging server. The local online charging server imitates the work of an external charging server. This means that the local charging server can receive Credit Control Requests (CCRs) from, and send Credit Control Answers (CCAs) to, IM-OCF PCP.
IM-OCF PCP writes charging data records (CDRs) which it replays to the online charging server when the server becomes available again. The online charging server charges the mobile subscriber based on the usage records in the CDRs.
For more information, see the discussion on administrating the degraded mode in Oracle Communications Service Broker Online Mediation Controller Implementation Guide.
You use the Degraded Mode tab to configure the parameters of this mode as described in Table 23-9.
Table 23-9 Degraded Mode Parameters
| Name | Type | Description |
|---|---|---|
|
On OCF Failure |
STRING |
Specifies the behavior of IM-OCF Ro when the OCF fails. Possible values:
Default value: USE_LOCAL_REFUSE |
|
CDR Mode |
STRING |
Specifies how IM-OCF PCP writes CDRs. Possible options:
Default value: NORMAL |
|
CDR Writer Impl |
STRING |
Specifies the full path of the bundle that implements the CDR writer functionality. This is a preset parameter. Do NOT change the value of this parameter. |
|
CDR Writer Service |
STRING |
Specifies the full path of the CDR writer service. This is a preset parameter. Do NOT change the value of this parameter. |
|
Degraded Mode Timer |
INT |
Specifies the period of time, in milliseconds, that IM-OCF PCP waits for a response from the online charging server. If the online charging server does not respond within the specified period of time, IM-OCF PCP switches to the degraded mode. |
|
Local-OCF Alias |
STRING |
Specifies the alias of the local online charging server. This alias is mapped to the destination host and destination realm of the local online charging server as defined in the configuration of Diameter SSU outbound routing rules. For more information, see the discussion on configuring outbound destinations in Diameter SSUs in Oracle Communications Service Broker Signaling Server Units Configuration Guide. |
|
Local-OCF External Protocol |
STRING |
Specifies the protocol that IM-OCF PCP uses to communicate with the local online charging server. |
|
Degraded Mode Error Codes |
STRING |
Specifies the error codes that trigger IM-OCF Ro to enable the degraded mode. You can type several error codes separated by comma. |
IM-OCF PCP translates Ro messages to PCP messages and communicates with BRM applications using the Ro PCP mediator.
You set up the mediator by configuring parameters on the subtabs described in Table 23-10.
Table 23-10 Ro PCP Mediation Subtabs
| Subtab | Description |
|---|---|
|
General |
Enables you to define how IM-OCF PCP communicates with BRM applications. See "Configuring General Parameters" for more information. |
|
SSU PCP Alias Resolver |
Enables you to configure the resolution mechanism that routes requests based on the value of an AVP inside the request. See "Configuring SSU PCP Alias Resolver" for more information. |
|
Service types |
Enables you to set up mapping between Diameter Ro Service-Identifier AVP and BRM service types. See "Configuring Service Types" for more information. |
|
Opcode mapping |
Enables you to map new Diameter Ro requests to BRM PCM operation codes. See "Configuring Opcode Mapping" for more information. |
|
Monitoring |
Enables you to define how Runtime MBeans and notifications should operate. See "Configuring Monitoring Parameters" for more information. |
Using the General subtab, you define how IM-OCF PCP communicates with BRM applications. Table 23-11 describes the parameters that you can configure.
Table 23-11 Ro to PCP Mediation General Parameters
| Name | Type | Description |
|---|---|---|
|
Client Program Name |
STRING |
The name representing IM-OCF PCP as a BRM client application when accessing BRM. Default value: Matrix |
|
Object Type |
STRING |
Always set this value to gsm. |
|
Default Opcode Timeout |
INT |
The time to allow for a charging requests to execute before it is considered to have timed out. Given in seconds. |
|
Charging Session State Timeout |
INT |
The charging session state timeout value. |
|
Reservation Expiration Time |
INT |
The time BRM applications keeps reservation objects before they release them. Given in milliseconds. Default value: 86400000 (24 hours) See "About Creating Reservations" in the chapter "Reserving Resources for Concurrent Network Sessions" in Oracle Communications Billing and Revenue Management Configuring and Collecting Payments. |
|
Customized Mapping Key Class |
STRING |
A class to be used for mapping processor key generation. It is needed only when opcode mapping tree structure is modified. Otherwise, the default processor key will be used. |
IM-OCF PCP routes outgoing PCP requests through connection pools that you create. For more information, see the discussion on creating BRM connection pools in Oracle Communications Service Broker Online Mediation Controller Implementation Guide.
By default, IM-OCF PCP routes requests through all connection pools in a round-robin fashion. However, you can also enable a resolution mechanism that routes requests based on the value of an AVP inside the request. In this case, the value of the AVP is resolved into a connection pool. The value of the AVP needs to match the alias of a destination BRM application, that is the alias of a PCP network entity configured in the PCP SSU.
Table 23-12 describes the parameters that you can configure.
Table 23-12 SSU PCP Alias Resolver Parameters
| Name | Type | Description |
|---|---|---|
|
Enable SSU PCP Alias Resolution |
BOOL |
Specifies whether to enable the connection pool resolution mechanism or not. Possible values:
Default value: FALSE |
|
AVP Code |
INT |
The code of the AVP based on which value the connection pool resolution is done. Default value: 283 (Destination-Realm AVP) |
|
AVP Vendor ID |
INT |
The vendor ID of the AVP you entered in AVP Code. Default value: 0 |
Using the Service types tab, you set up mapping between Diameter Ro Service-Identifier AVP and BRM service types. Table 23-13 describes the parameters that you can configure.
Table 23-13 Ro to PCP Mediation Service Types Parameters
| Name | Type | Description |
|---|---|---|
|
Service Identifier |
INT |
The Diameter Ro service identifier to be mapped to BRM service type |
|
Service Type |
STRING |
The BRM service type to use for the corresponding Diameter Ro service id. For example, |
|
Default Service Type |
BOOL |
Set to:
|
Using the Opcode mapping tab, you map new Diameter Ro requests to BRM PCM operation codes.
To map new Diameter Ro requests to BRM PCM operation codes:
In the Opcode mapping tab, in the navigation tree, select the type of Diameter request that you want to add mapping for.
Click the Plus (+) button at the bottom of the navigation tree area. A new AVP node is added.
In the AVP tab in the right hand pane, enter the following fields for the AVP that you want to map:
AVP Code
AVP Vendor ID
AVP Value
Click the Add Opcode Mapping button. The Mapping tab appears.
In the Mapping tab, set the following fields as described:
In the Processor Class field, enter name of the name of the processor class implementing the mapping that you are currently configuring.
In the Opcode ID and Opcode Flag fields, enter the BRM operation code and operation flag.
In the Opcode Timeout field, enter the time to allow for the BRM operation to execute before it is considered to have timed out. Given in milliseconds.
The Monitoring tab enables you to define how Runtime MBeans and notifications operate for Ro PCP Mediation. For more information about configuring monitoring, see "Configuring Service Broker Monitoring" in "Monitoring Service Broker Using Runtime MBeans" in Oracle Communications Service Broker System Administrator's Guide.
Charging IMs handling Diameter responses from online charging systems can perform session redirection based on criteria in Credit Control Answers (CCA). Configure the default IM redirection behavior in the IM configuration node Redirection tab.
See the discussion on redirection in Oracle Communications Service Broker Online Mediation Controller Implementation Guide for more information on using session redirection.
|
 Copyright © 2010, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
