| Oracle® Communications Service Broker Service Controller Implementation Guide Release 6.1 Part Number E29460-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Communications Service Broker Service Controller Implementation Guide Release 6.1 Part Number E29460-01 |
|
|
PDF · Mobi · ePub |
This chapter describes the Oracle Communications Service Controller and Oracle Communications Online Mediation Controller online charging for SS7 networks solution and how to configure Service Controller and Online Mediation Controller for this solution.
You use the online charging for SS7 networks solution to deliver Portal Connection Protocol (PCP), ECE API, or Diameter-based charging for subscriber sessions in the legacy SS7 network. Service Controller and Online Mediation Controller deliver SS7 sessions to online charging systems (OCSs) including Oracle Communications Billing and Revenue Management (BRM), Oracle Communications Elastic Charging Engine (ECE) or third-party charging systems supporting the Diameter Ro protocol.
The online charging for SS7 networks solution requires the installation of Oracle Communications Online Mediation Controller. Online Mediation Controller mediates messages between the Service Controller and your OCS. See Oracle Communications Service Broker Online Mediation Controller Implementation Guide, for more information.
Figure 4-1 shows a basic session charging flow of the online charging for SS7 networks solution. Service Controller supports additional call flow scenarios not shown such as applying charging after answer and internal charging for CAP1, WIN and AIN networks.
Figure 4-1 Basic Call Flow in the Online Charging for SS7 Networks Solution
Figure 4-2 shows the components in the Service Controller and Online Mediation Controller processing tier that you set up to enable SS7 to OCS charging.
The IMSCF Service Controller module translates SS7 messages into an internal format used by the Orchestration Engine. You use different variants of the IMSCF module, depending on the protocol variant used in your network. For example, if your network uses CAP Phase 3, then you use the IMSCF-CAP-Phase 3 module.
The IMOCF Online Mediation Controller module translates internally formatted messages to PCP, ECE API or Diameter Ro messages processed by the OCS. You use the IMOCF variant specific to the OCS implemented in your environment. For example, use IMOCF-PCP when the OCS is BRM.
To enable Service Controller's SS7 and Online Mediation Controller's OCS connectivity, you also need to configure the appropriate SSU for your OCS in the signaling tier. The OCS SSUs are not included in the figure. See Oracle Communications Service Broker Signaling Server Units Configuration Guide, for more information about configuring the SSU(s) for your OCS.
Sessions flow from the SS7 network through the components in the following order:
SS7 Network
SSU SS7
IMSCF
Orchestration Engine
IMOCF-PCP/ECE/Ro
SSU PCP/ECE/Ro
OCS
Responses from the OCS flow in the reverse direction through the same components
Figure 4-2 Components Required for SS7 Session Charging
An end-to-end configuration enabling SS7 charging by BRM, ECE, or a Diameter Ro OCS, requires configuration of SSU SS7, the SSU for the OCS implemented, IMSCF, the IMOCF for the OCS implemented, and orchestration engine rules.
To set up this configuration:
Enable Service Controller to accept traffic of sessions arriving from the legacy SS7 network. See "Setting Up Connectivity to the Legacy SS7 Network" for information about the components that you need to configure and how to configure them.
Install and create an Online Mediation Controller domain. See Oracle Communications Service Broker Installation Guide, for more information.
Enable the Online Mediation Controller OCS interface to allow communication between Service Controller and the OCS. See "Setting Up Connectivity to the OCS" for more information.
Route sessions that arrive from the legacy SS7 network to the OCS. See "Defining a Service Orchestration Chain" for more information.
Before you start, make sure that you have a detailed plan of how Service Controller connects to your SS7 network, including point codes that you assign to Service Controller. To connect Service Controller to the legacy SS7 network:
Depending on the type of your SS7 network, configure the relevant SS7 SSU:
To connect a TDM-based SS7 network, configure the SS7 SSU for TDM as described in Oracle Communications Service Broker Signaling Server Units Configuration Guide.
To connect a SIGTRAN-based SS7 network, configure the SS7 SSU for SIGTRAN as described in Oracle Communications Service Broker Signaling Server Units Configuration Guide.
Deploy and configure the proper IMSCF module variant, as described in Oracle Communications Service Broker Modules Configuration Guide.
Configure routing rules in the SS7 SSU to route sessions arriving from the SS7 network to the IMSCF module that you deployed in the step 1.
In the Administration Console:
In the navigation tree, expand OCSB node, and then the Signaling Tier node.
If you connect to a TDM-based SS7 network, select SSU SS7 TDM. Otherwise, select SSU SS7 SIGTRAN.
In the Routing tab, in the left pane, click the Add button. The New dialog box appears.
In the Name field, enter a name for the routing rule. Click Apply. The newly created rule now appears in the rules tree in the left pane.
Select the newly created rule node, and then select the Incoming Routing Rules tab.
In the Module Instance field enter module.type@domain where module is the name of the IMSCF module that you deployed in step 2, type is the type of the IMSCF module that you deployed, and domain is the name of the domain where you deployed the module. For example, for an instance of IMSCFCAP3, imscf.IMSCFCAP3@ocsb.
Optionally, you can define criteria for the rule, so that the SSU SS7 route to the IMSCF application only sessions that meet the criteria. You define criteria for the rule in the Incoming Routing Rule Criteria tab.
Configure the IMSCF parameters under the Charging Service tab in the Administration Console. See the charging service configuration section for the IMSCF module you are using in Oracle Communications Service Broker Modules Configuration Guide, for more information on setting these parameters.
Before you start, make sure that you have a detailed plan of how Online Mediation Controller connects to your OCS, including information such as connection credentials and IP addresses or host names. Ask your OCS administrator for the required information
To connect Service Controller to the OCS, refer to one of the following sections relevant to the OCS implemented in your environment:
See "Connecting to BRM Through PCP", for implementations using BRM as the OCS.
See "Connecting to ECE Using the ECE SSU", for implementations using ECE as the OCS.
See "Connecting to a Standard OCS through Diameter Ro", for implementations using a Diameter Ro compliant OCS.
To connect Online Mediation Controller 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.
In the Password area, click the Set Password button.
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.
To connect Online Mediation Controller to ECE:
In the Administration Console:
In the navigation tree, expand the OCSB node, and then the Signaling Tier node.
Select the SSU ECE node.
In the ECE tab, select the Coherence tab.
Populate the ECE SSU values used to connect to the ECE OCS:
Coherence cluster name
JMX management read-only
Coherence log file name
Coherence log level
Use ECE well known address
Well known address 1 (ip:port)
Well know address 2 (ip:port)
Multicast address (ip:port)
Multicast TTL
For information about the ECE Coherence configuration values, see Oracle Communications Service Broker Signaling Server Units Configuration Guide.
Select the General tab to set the Request default timeout.
Configure the IMOCF-ECE instance as described in the chapter on configuring IMOCF-ECE in Oracle Communications Service Broker Modules Configuration Guide.
Specifically, you need to define the destination OCS that the IMOCF-ECE 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 IMOCF-ECE 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 coherence cluster name you defined in step 2. Alternatively, in the Destination-Realm AVP and in the Destination-Host AVP fields, enter the values that the IMOCF-ECE must set in the Destination-Host and Destination-Realm AVPs of outgoing Diameter request, in order to route requests to ECE.
Click the Apply button.
Activate the IMOCF-ECE instance that you deployed and configured in step 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 IMOCF-ECE module in the table.
Click the Activate button.
To connect Online Mediation Controller to the IMS network:
Define Online Mediation Controller as a Diameter node and configure how other Diameter entities access it, as described in the discussion about creating Diameter nodes in the chapter about the Diameter SSU in Oracle Communications Service Broker Signaling Server Units 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 Add button on the bottom of the list of existing Diameter nodes.
In the General tab, 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 Online Mediation Controller.
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.
Click Apply.
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, the Diameter SSU running on all signaling servers using the same port will result in network traffic collisions.Deploy the IMOCF-Ro module as described in the discussion on setting up IMOCF-Ro in Oracle Communications Service Broker Modules 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 IMOCF.
In the Name field, enter a module instance name. For example, rimocfro_instance.
Click the OK button.
Configure the IMOCF-Ro module as described in the discussion on setting up IMOCF-Ro in Oracle Communications Service Broker Modules Configuration Guide.
Activate the IMOCF-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 IMOCF-Ro module in the table.
Click the Activate button.
To route sessions to the OCS, you have to choose the method (LSS, HSS, or static service orchestration) that you want to use for service orchestration, and then, based on your choice, define a service orchestration chain with the OCS in it.
See "Configuring Service Orchestration" for information about the different options for service orchestration, and how to configure them.
|
 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
