Skip Headers
Oracle® Communications Service Broker Processing Domain Configuration Guide
Release 6.0

Part Number E23525-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

28 Configuring IM-OFCF PCP

The following sections describe how to configure IM-OFCF PCP using the Service Broker Administration Console and Java MBeans.

Configuring IM-OFCF PCP with the Administration Console

This section describes how to configure the IM-OFCF PCP module instances using the Service Broker Administration Console.

To access the IM-OFCF PCP Configuration screen:

  1. In the domain navigation pane, expand OCSB.

  2. Expand Processing Tier.

  3. Select Interworking Modules.

    A list of currently deployed Interworking Modules is displayed.

  4. From the module list, select the module instance that you want to configure.

    The IM-OFCF PCP configuration screen contains the tabs described in Table 28-1.

Table 28-1 IM-OFCF PCP Configuration Tabs

Subtab Description

Call Handling

Enables you to define how IM-OFCF PCP handles calls.

See "Configuring Call Handling 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.

Rf PCP Mediation

Enables you to define how IM-OFCF PCP translates Rf messages to PCP messages and communicates with BRM applications.

See "Configuring Rf PCP Mediation" for more information.


Configuring Call Handling Parameters

The Call Handling subtab enables you to define how IM-OFCF PCP handles calls.

Table 28-2 describes configuration parameters on the Call Handling tab.

Table 28-2 IM-OFCF PCP Call Handling Parameters

Name Type Description

Destination Alias

STRING

Specifies an alias of the offline charging server realm that you defined in the SSU PCP configuration.

Service Context

STRING

Specifies the Service-Context-Id AVP if this AVP is not set in the session that IM-OFCF PCP receives from the network.

Failure Code For Processing Error

STRING

Specifies the SAL error that IM-OFCF PCP generates if IM-OFCF PCP failed to create an ACR.


Configuring Monitoring Parameters

The Monitoring tab enables you to define how Runtime MBeans and notifications operate for an IM-OFCF PCP. For more information about configuring monitoring, see "Configuring Monitoring with the Administration Console".

Configuring the Degraded Mode

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-OFCF PCP switches to the special mode known as degraded mode. This mode enables IM-OFCF PCP to continue a session and charge a mobile subscriber during the time when the charging server is temporarily unavailable.

To check the availability of the charging server, every time when IM-OFCF PCP sends an accounting request to the charging server, IM-OFCF PCP waits a specified period of time for a response from the server. If the server does not respond, IM-OFCF PCP switches to the degraded mode.

After IM-OFCF PCP switched to the degraded mode, IM-OFCF PCP handles the session in this mode until the session is terminated even if the online charging server becomes available. However, when the charging server becomes available, IM-OFCF PCP sends to the server charging information gathered during the session.

In the degraded mode, IM-OFCF 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-OFCF PCP.

To gather this information, IM-OFCF PCP writes Charging Data Records (CDRs). IM-OFCF PCP replays the CDRs to the online charging server after this server becomes available again. Then the server actually charges the mobile subscriber.

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 28-3.

Table 28-3 Degraded Mode Parameters

Name Type Description

On OCF Failure

STRING

Specifies the behavior of IM-OFCF Ro when the OCF fails.

Possible values:

  • ALWAYS_REFUSE

    Degraded mode is disabled. If the OCF fails, IM-OFCF Ro refuses to grant the service.

  • USE_LOCAL_REFUSE

    Degraded mode is enabled. IM-OFCF Ro writes CDRs. If a local OCF or CDR writing fails, IM-OFCF Ro refuses to grant the service.

  • USE_LOCAL_GRANT

    Degraded mode is enabled. IM-OFCF Ro writes CDRs. If a local OCF or CDR writing fails, IM-OFCF Ro grants the service.

    Note: This setting is overridden by the OCF AVPs 'Credit Control Failure Handling' and 'Realtime Required'.

Default value: USE_LOCAL_REFUSE

CDR Mode

STRING

Specifies how IM-OFCF PCP writes CDRs.

Possible options:

  • NORMAL

    IM-OFCF PCP begins to write CDRs when IM-OFCF PCP switches to the degraded mode.

  • HISTORY

    Like in the Normal mode, IM-OFCF PCP begins to write CDRs when IM-OFCF PCP switches to the degraded mode. In addition, IM-OFCF PCP stores all CDRs that IM-OFCF PCP previously sent to the OCS.

  • ALWAYS

    IM-OFCF PCP always writes CDRs.

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-OFCF 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-OFCF 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 Domain Configuration Guide.

Local-OCF External Protocol

STRING

Specifies the protocol that IM-OFCF PCP uses to communicate with the local online charging server.

Degraded Mode Error Codes

STRING

Specifies the error codes that trigger IM-OFCF Ro to enable the degraded mode. You can type several error codes separated by comma.


Configuring Rf PCP Mediation

IM-OFCF PCP translates Rf messages to PCP messages and communicates with BRM applications using the Rf PCP mediator.

You set up the mediator by configuring parameters on the subtabs described in Table 28-4.

Table 28-4 Rf PCP Mediation Subtabs

Subtab Description

General

Enables you to define how IM-OFCF PCP communicates with BRM applications.

See "Configuring General Parameters" 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 Parameters" for more information.

Degraded Mode

Enables you to specify the error codes and response codes to trigger IM-OFCF PCP to process a request in the degraded mode.

See "Configuring the Degraded Mode" for more information.


Configuring General Parameters

Using the General subtab, you define how IM-OFCF PCP communicates with BRM applications. Table 28-5 describes the parameters that you can configure.

Table 28-5 Rf to PCP Mediation General Parameters

Name Type Description

brm-client-program-name

STRING

The name representing IM-OFCF PCP as a BRM client application when accessing BRM.

Default value: Matrix

brm-object-type

STRING

Always set this value to gsm.

incremental-mode

INT

Specifies how IM-OFCF PCP calculates the used quantity for the session.

Possible values:

  • True

    IM-OFCF PCP calculates the used quantity as the delta between updates.

  • False

    IM-OFCF PCP calculates the total used quantity in all updates.

acr-timeout

INT

Specifies the period of time, in milliseconds, that IM-OFCF PCP waits for a response from the BRM application.

If IM-OFCF PCP does not receive a response within the specified period of time, IM-OFCF PCP handles the request in the degraded mode.


Configuring Service Types Parameters

Using the Service Types tab, you set up mapping between Diameter Rf Service-Identifier AVP and BRM service types. Table 28-6 describes the parameters that you can configure.

Table 28-6 Rf to PCP Mediation Service Types Parameters

Name Type Description

Id

INT

The Diameter Rf service identifier to be mapped to BRM service type

type

STRING

The BRM service type to use for the corresponding Diameter Rf service id.

For example, service/telco/gsm/sms

default

STRING

Set to:

  • true to use this as a default value

  • false to not use this as a default value


Configuring the Degraded Mode

Using the Degraded Mode tab, you can specify the error codes and response codes to trigger IM-OFCF PCP to process a request in the degraded mode. Table 28-7 describes the parameters that you can configure.

Table 28-7 Rf to PCP Degraded Mode Parameters

Name Type Description

BRM error codes

STRING

Specifies the error codes that trigger IM-OFCF PCP to handle the request in the degraded mode. You can enter multiple error codes separated by comma.

Result code

STRING

Specifies the result code that the mediator should generate to trigger IM-OFCF PCP o handle the request in the degraded mode.


Configuring IM-OFCF PCP with Java MBeans

Service Broker provides a set of MBeans that provide attributes and operations for configuring the IM-OFCF PCP through JMX. Figure 28-1 shows the hierarchy of the IM-OFCF PCP MBeans.

Figure 28-1 IM-OFCF PCP MBean Hierarchy

IM-OFCF MBean Hierarchy

The following sections provide reference information for the IM-OFCF PCP configuration MBeans.

Note:

MBeans described in this guide may include additional advanced attributes, which are not described in the guide. Advanced attributes are reserved for internal use. Do not change these attributes.

The following MBeans are common for all components of Service Broker and described in "Configuring Monitoring with Java MBeans":


ImofcfPCPMBean

ImofcfPCPMBean is a root MBean for the IM-OFCF PCP configuration.

Factory Method

Created automatically

Attributes

None

Operations

ObjectName getCallHandling()

Gets a reference to the instance of CallHandlingMBean

ObjectName getMonitoringGeneral()

Gets a reference to the instance of MonitoringGeneralMBean

ObjectName getThresholdCrossedNotificationRules()

Gets a reference to the instance of ThresholdCrossedNotificationRulesMBean

ObjectName getStateChangedNotificationRules()

Gets a reference to the instance of StateChangedNotificationRulesMBean


CallHandlingMBean

CallHandlingMBean enables you to configure how the IM-OFCF PCP handles calls.

Factory Method

Created automatically

Attributes

For more information on these attributes, see Table 28-2.

Operations

None


DegradedModeMBean

DegradedModeMBeanMBean enables you to configure how IM-OCF Ro operates in the degraded mode.

Object Name

com.convergin:Type=DiameterCreditControlApplicationAvps,Version=MBean_Version,Location=AdminServer,Name=IMOCF.Instance_Name

Factory Method

Created automatically

Attributes

For more information on these attributes, see Table 28-3.

Operations

None


pcp-2-rf-mediator-configMBean

pcp-2-rf-mediator-configMBean is the root MBean that you use to configure the Rf PCP mediator.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config

Factory Method

Created automatically.

Attributes

None

Operations

void addOpcode_mapping()

Creates an instance of opcode_mappingMBean.

void removeOpcode_mapping(int OpcodeID)

Destroys an instance of opcode_mappingMBean.


brm-client-program-nameMBean

Using brm-client-program-nameMBean, you specify the name that represents IM-OFCF PCP as a BRM client application when accessing BRM.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=brm-client-program-name

Factory Method

Created automatically.

Attributes

brm-client-program-name

For more information on this attribute, see Table 28-5.

Operations

None


brm-object-typeMBean

Using brm-object-typeMBean, you specify the object type. Always set this value to gsm.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=brm-object-type

Factory Method

Created automatically.

Attributes

brm-object-type

For more information on this attribute, see Table 28-5.

Operations

None


incremental-modeMBean

Using incremental-modeMBean, you specify how IM-OFCF PCP calculates the used quantity for the session.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=incremental-mode

Factory Method

Created automatically.

Attributes

incremental-mode

For more information on this attribute, see Table 28-5.

Operations

None


acr-timeoutMBean

Using acr-timeoutMBean, you specify the period of time, in milliseconds, that IM-OFCF PCP waits for a response from the BRM application.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=acr-timeout

Factory Method

Created automatically.

Attributes

acr-timeout

For more information on this attribute, see Table 28-5.

Operations

None


service-typesMBean

service-typesMBean is the root MBean is the root MBean for setting up mapping between Diameter Rf Service-Identifier AVP and BRM service types.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=service-types

Factory Method

Created automatically.

Attributes

None

Operations

void addService()

Creates a new instance of serviceMBean.

void removeService(int ServiceID)

Destroys an instance of serviceMBean.


serviceMBean

Using serviceMBean, you can specify parameters of a single service.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=service-types,name2=service[0]

Factory Method

Created automatically.

Attributes

None

Operations

void cloneIt()

Clones the current instance of serviceMBean.

void addDefault()

Creates a new instance of defaultMBean.

void removeDefault()

Destroys an instance of defaultMBean.


idMBean

Using idMBean, you specify the Diameter Rf service identifier to be mapped to BRM service type.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=service-types,name2=service[0],name3=default

Factory Method

Created automatically.

Attributes

id

For more information on this attribute, see Table 28-6.

Operations

None


typeMBean

Using typeMBean, you specify the BRM service type to use for the corresponding Diameter Rf service id.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=service-types,name2=service[0],name3=type

Factory Method

Created automatically.

Attributes

type

For more information on this attribute, see Table 28-6.

Operations

None


defaultMBean

Using defaultMBean, you specify whether the service defined in serviceMBean should be used as a default value.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=service-types,name2=service[0],name3=default

Factory Method

service.addDefault()

Attributes

default

For more information on this attribute, see Table 28-6.

Operations

None


degraded-modeMBean

degraded-modeMBean is the root MBean for specifying the error codes and response codes to trigger IM-OFCF PCP to process a request in the degraded mode.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=degraded-mode

Factory Name

Created automatically.

Attributes

None

Operations

None


brm-error-codesMBean

Using brm-error-codesMBean, you specify the error codes that trigger IM-OFCF PCP to handle the request in the degraded mode. You can provide multiple error codes separated by comma.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=degraded-mode,name2=brm-error-codes

Factory Method

Created automatically.

Attributes

brm-error-codes

For more information on this attribute, see Table 28-7.

Operations

None


result-codeMBean

Using result-codeMBean, you specify the result code that the mediator should generate to trigger IM-OFCF PCP to handle the request in the degraded mode.

Object Name

oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.ocsb.app.rcc.mediation.pcp2rf,version=MBean_Version.SNAPSHOT,name0=pcp-2-rf-mediator-config, name1=degraded-mode,name2=result-code

Factory Method

Created automatically.

Attributes

result-code

For more information on this attribute, see Table 28-7.

Operations

None