| Oracle® Communications Service Broker Online Mediation Controller Implementation Guide Release 6.0 Part Number E23527-02 |
|
|
View PDF |
| Oracle® Communications Service Broker Online Mediation Controller Implementation Guide Release 6.0 Part Number E23527-02 |
|
|
View PDF |
Oracle Communications Service Broker online mediation Controller provides a way for an Online Charging System (OCS) to charge subscribers and accounts, for services that they use in the IMS network.
This chapter describes how you set up and configure orchestrated charging mediation.
OCS allows communications service providers to charge their subscribers, in real time, based on service usage. An OCS authenticates subscribers and maintains accounts that subscribers use to pay for services that they use. It can influence, in real time, the service rendered to a subscriber and therefore needs a direct interaction with the communications network.
Service Broker provides an OCS with a front-end to the network. Service Broker communicates with the network through its native protocols, exposing one unified interface to the OCS.
The unified interface is based on either a standard Diameter Ro or PCP. You can use any of the two interfaces, depending on the type of OCS you are using. For integration with Oracle Communications Billing and Revenue Management (BRM) the PCP interface is used.
Figure 3-1 shows the application-facing interworking modules and network-facing interworking modules that you need to deploy and configure to apply an online charging service.
You use:
R-IM-OCF-Ro, to charge services in the IMS network
Depending on the type of OCS in your system, use one of the following:
OCS supporting a standard Diameter Ro interface: IM-OCF-Ro
Oracle Communications BRM: IM-OCF-PCP
To charge subscribers for voice sessions, data sessions and other service usage, in real time, you need to configure your network to route sessions and service usage events to Service Broker.
When you route subscriber sessions and events through Service Broker, you configure the subscriber's orchestration logic in the Subscriber Store to forward sessions to the OCS. You can also configure it to forward sessions to additional applications, thereby applying more services in your network to sessions, in addition to the charging service applied by the OCS.
To set up an end-to-end configuration for online charging:
To charge sessions and events in the IMS domain, connect Service Broker to the IMS network. See "Connecting to the IMS Network".
Connect Service Broker to your OCS. Depending on the type of OCS in your system, do one of the following:
OCS supporting a standard Diameter Ro interface: See "Connecting to an OCS Through Diameter Ro".
Oracle Communications BRM: See "Connecting to BRM Through PCP".
Route subscriber session to the OCS. See "Adding the OCS to the Service Orchestration Chain".
To connect Service Broker to the IMS network:
Define Service Broker as a Diameter node and configure how other Diameter entities access it, as described in the section "Creating a Diameter Node" in chapter "Configuring Diameter Signaling Server Units" in Oracle Communications Service Broker Processing Domain Configuration Guide.
In the Administration Console:
In the navigation tree, expand the OCSB node, and then the Signaling Tier node.
Select the SSU Diameter node.
In the DIAMETER tab, select the Diameter Configuration tab.
You can either use the default node or create a new node by clicking the Plus (+) icon below the Node tree. The General tab appears.
In the Name field, enter a unique name for the Diameter node.
In the Realm field, enter the realm name that other Diameter nodes use to access Service Broker.
In the Port field, enter the port number that signaling servers use to listen to Diameter traffic.
Leave the Address, Host and Target fields blank to apply the configuration to all signaling servers in the Signaling Domain and have them all provide a Diameter network channel on the same port.
Note:
If you run multiple signaling servers on the same physical machine, you have to define each signaling server as a different Diameter node which listens on a different port. Otherwise, if the Diameter SSU running on all signaling servers uses the same port, then the ports will collide.Deploy the R-IM-OCF-Ro module as described in "Managing Interworking Modules" in Oracle Communications Service Broker Processing Domain Configuration Guide.
In the Administration Console:
In the navigation tree, expand the OCSB node.
Expand the Processing Tier node, and then the Interworking Modules node.
Click IM Management.
In the IM Management tab, click the New button. The New dialog box appears.
From the Type list, select RIMOCF.
In the Name field, enter a module instance name. For example, rimocfro_instance.
Click the OK button.
Configure the R-IM-OCF-Ro module as described in "Configuring R-IM-OCF-Ro" in Oracle Communications Service Broker Processing Domain Configuration Guide.
Configure the Diameter SSU to accept incoming Diameter requests as described in "Configuring the Diameter SSU" in Oracle Communications Service Broker Signaling Domain Configuration Guide.
Specifically, add a new incoming routing rule to route incoming Ro requests to the R-IM-OCF module that you created in step 2.
In the Administration Console:
In the navigation tree, expand the OCSB node, and then the Signaling Tier node.
Select the SSU Diameter node.
In the SSU Diameter tab, select the Routing tab, and then the Incoming Routing Rules tab.
In the Name field, enter a name for the new routing rule.
In the Priority field, leave the default value.
In the Module Instance field, enter ssu:r-im-ocf-ro-module-name.RIMOCF@domain-id, where r-im-ocf-ro-module-name is the name you gave to the R-IM-OCF-Ro module in step 2, and domain-id is the name of the Processing Domain where you deployed the R-IM-OCF-Ro.
If your deployment includes only one Processing Domain, then set domain-id to ocsb. For example, rimocfro_instance.RIMOCF@ocsb.
Click the OK button.
Specify the criteria that Ro requests have to meet so that the Diameter SSU forward them to R-IM-OCF-Ro:
In the SSU Diameter tab, select the Routing tab, and then the Incoming Routing Criteria tab.
From the Parent list, select the name of the incoming routing rule that you have just created. You will now define the criteria to apply this rule.
Click the New button. The New dialog box appears.
In the Name field, enter a name for the new criteria.
In the Attribute field, select the AVP whose value the Diameter SSU checks in incoming request.
In the Value field, enter the value that the AVP should match for the Diameter SSU to route incoming requests into Service Broker.
Click the OK button.
Activate the R-IM-OCF-Ro module that you deployed and configured in steps 2 and 3.
In the Administration Console:
In the navigation tree, expand the OCSB node.
Expand the Processing Tier node and then the Interworking Modules node.
Click on IM Management.
In the IM Management tab, select the R-IM-OCF-Ro module in the table.
Click the Activate button.
To connect Service Broker to an OCS:
In the Diameter SSU, configure the OCS instances as Diameter peers, as described in "Configuring the Diameter SSU" in Oracle Communications Service Broker Signaling Domain Configuration Guide.
At a minimum, it is recommended to establish connection with two peers per realm.
In the Administration Console:
In the navigation tree, expand the OCSB node, and then the Signaling Tier node.
Select the SSU Diameter node.
In the DIAMETER tab, select the Diameter Configuration tab and then the Peers tab.
In the Address field, enter the IP address or DNS name of the peer.
In the Host field, enter the Destination-Host AVP value identifying the peer. You will refer this value later when configuring outgoing Diameter routes.
In the Port field, enter the listen port number of the peer node
In the Protocol field, enter the protocol used to communicate with the peer: tcp or sctp.
Check the Watchdog checkbox if the peer supports the Diameter Tw watchdog timer interval.
Repeat steps d through j for each OCS instance in your system.
In the Diameter SSU, define the OCS as a Diameter destination. You can define two or more destinations having different Destination-Host AVPs, that share the same alias, thereby adding a level of redundancy, treating all destinations as one logical destination, and balancing the load among destinations.
In the navigation tree, expand the OCSB node, and then the Signaling Tier node.
Select the SSU Diameter node.
In the SSU Diameter tab, select the Outbound Destinations tab.
In the Name field, enter a name for the OCS.
In the Alias field, enter an alias that you want to assign to the destination OCS. You can enter the same alias later when you define more destination OCSs, to have a number of destination OCSs share load.
In the Destination Host and Destination Realm fields, enter the Destination Host and Destination Realm of the peers running the OCS. Use the Destination Host of the peers you defined in step 1.
Repeat steps d through h for each additional destination OCS that you want to configure.
Deploy the IM-OCF-Ro module as described in "Managing Interworking Modules" in Oracle Communications Service Broker Processing Domain Configuration Guide.
In the Administration Console:
In the navigation tree, expand the OCSB node.
Expand the Processing Tier node, and then the Interworking Modules node.
Click on IM Management.
In the IM Management tab, click New.
From the Type list, select IMOCF.
In the Name field, enter a module instance name. For example, imocfro_instance.
Click the OK button.
Configure the IM-OCF-Ro instance as described in "Configuring IM-OCF-Ro" in Oracle Communications Service Broker Processing Domain Configuration Guide.
Specifically, you need to define the destination OCS that the IM-OCF-Ro instance communicates with. You can either specify Destination-Host and Destination-Realm AVPs, or you can use the alias of a destination that you defined in step 1.
In the Administration Console:
In the navigation tree, expand the OCSB node.
Expand the Processing Tier node, and then the Interworking Modules node.
Click on IM Management.
Select the IM-OCF-Ro module node.
In the Configuration tab, select the Diameter Credit Control Application tab, and then the AVPs tab.
In the Destination-Realm AVP field, enter the alias that you assigned to the destination OCS that you defined in step 1. Alternatively, in the Destination-Realm AVP and in the Destination-Host AVP fields, enter the values that the IM-OCF-Ro must set in the Destination-Host and Destination-Realm AVPs of outgoing Diameter request, in order to route requests to the destination OCS.
Click the Apply button.
Activate the IM-OCF-Ro module that you deployed and configured in steps 3 and 4.
In the Administration Console:
In the navigation tree, expand the OCSB node.
Expand the Processing Tier node and then the Interworking Modules node.
Click on IM Management.
In the IM Management tab, select the IM-OCF-Ro module in the table.
Click the Activate button.
To connect Service Broker to Oracle Communications BRM:
Create BRM connection pools in the PCP SSU, as described in "Defining Connection Pools" in the chapter "Configuring the PCP Signaling Server Unit" in Oracle Communications Service Broker Signaling Domain Configuration Guide.
See also "About Connection Pooling" in Oracle Communications Billing and Revenue Management System Administrator's Guide.
Secure the BRM connection pools that you created in step 1, as described in "Securing Connection Pools" in the chapter "Configuring the PCP Signaling Server Unit" in Oracle Communications Service Broker Signaling Domain Configuration Guide.
In the Administration Console:
In the navigation tree, expand the OCSB node, and then the Signaling Tier node.
Select the SSU PCP node.
In the PCP tab, select the Credential Store tab.
In the Password area, in the Key field, enter the ID of the connection pool that you want to secure. This should be the Pool ID that you assigned to the connection pool when you created the connection pool in step 1.
In the Password area, in the Password field, enter the password of the Oracle Communications BRM client application account used by the connection pool to access the BRM. This should be the password of the account that you configured in the BRM CM Login ID field when you initially defined the connection pool.
Repeat steps d through f for each connection pool that you want to secure.
Define destination BRM applications, as described in "Defining PCP Network Entities" in the chapter "Configuring the PCP Signaling Server Unit" in Oracle Communications Service Broker Signaling Domain Configuration Guide.
Deploy the IM-OCF-PCP module as described in "Managing Interworking Modules" in Oracle Communications Service Broker Processing Domain Configuration Guide.
In the Administration Console:
In the navigation tree, expand the OCSB node.
Expand the Processing Tier node, and then the Interworking Modules node.
Click on IM Management.
In the IM Management tab, click New.
From the Type list, select IMOCFPCP.
In the Name field, enter a module instance name. For example, imocfpcp_instance.
Click the OK button.
Configure the IM-OCF-PCP instance as described in "Configuring IM-OCF PCP" in Oracle Communications Service Broker Processing Domain Configuration Guide.
Specifically, you need to define the destination OCS that the IM-OCF-PCP module communicates with. You can either specify Destination-Host and Destination-Realm AVPs, or you can use an alias of a destination that you defined in step 1.
In the Administration Console:
In the navigation tree, expand the OCSB node.
Expand the Processing Tier node, and then the Interworking Modules node.
Click on IM Management.
Select the IM-OCF-PCP module node.
In the Configuration tab, select the Diameter Credit Control Application tab, and then the AVPs tab.
In the Destination-Realm AVP field, enter the alias that you assigned to the destination BRM connection pool that you defined in step 1. Alternatively, in the Destination-Realm AVP and in the Destination-Host AVP fields, enter the values that the IM-OCF-PCP must set in the Destination-Host and Destination-Realm AVPs of outgoing Diameter request, in order to route requests to the destination BRM.
Click the Apply button.
Activate the IM-OCF-PCP instance that you deployed and configured in steps 4 and 5.
In the Administration Console:
In the navigation tree, expand the OCSB node.
Expand the Processing Tier node and then the Interworking Modules node.
Click on IM Management.
In the IM Management tab, select the IM-OCF-PCP module in the table.
Click the Activate button.
To route subscriber sessions to the OCS:
Depending on your implementation, create an appropriate orchestration logic that routes network sessions through the OCS in your system. Use the Orchestration Studio to create the orchestration logic. See Oracle Communications Service Broker Orchestration Studio User's Guide.
Assign the orchestration logic you created in step 1 to subscribers. Use the Subscriber Provisioning API to provision the iFC source of the orchestration logic in subscribers' IfcProfileData. See "Using the Subscriber Provisioning API" in Oracle Communication Service Broker Subscriber Store User's Guide, for more information.
For information on setting up orchestrated mediation in Degraded Mode, see the discussion about the orchestrated mediation in "Using Degraded Mode".
|
 Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
