This chapter provides an overview of the various feature enhancements introduced in Oracle Communications Offline Mediation Controller 6.0.
For the 6.0 release, the product's name has changed from Network Mediation to Oracle Communications Offline Mediation Controller.
Offline Mediation Controller now supports the following software:
Oracle Linux, x86-64 (64-bit) 5 UL3+
Red Hat Enterprise Linux, x86-64 (64-bit) 5 UL3+
Oracle Solaris for SPARC (64-bit) 10 Update 4+
Oracle Solaris for x86 (64-bit) 10 Update 6+
Oracle 11g R2, and Oracle RAC 11g R2 databases
Oracle Unified Directory 11.1.1.5.0
See Offline Mediation Controller Installation Guide for information on other software support.
This section describes all security enhancements.
Previously, Offline Mediation Controller Administration Server used Open LDAP for user management.
Offline Mediation Controller now uses Oracle Unified Directory for secure and centralized storage for users and user's role information.
See Offline Mediation Controller System Administrator's Guide for information about the security enhancements.
Offline Mediation Controller now includes the following security enhancements:
Secure Sockets Layer (SSL) is used for communication between the Offline Mediation Controller components.
When you create a user account in Offline Mediation Controller, it assigns a default password policy to that user account.
Offline Mediation Controller provides two user groups: administrators to manage the operations in Offline Mediation Controller and the general user to view the node and the node host information.
The Offline Mediation Controller installer stores account passwords (for administrator and general user) in encrypted form in Oracle Unified Directory. The Offline Mediation Controller components can automatically decrypt the passwords when retrieving them from Oracle Unified Directory.
See Offline Mediation Controller System Administrator's Guide for information about the security enhancements.
You can now configure the session timeout after a preconfigured idle time between the Administration Client and the Administration Server. The session should never expire between an Administration Server and a Node Manager, where user intervention is not expected.
See Offline Mediation Controller System Administrator's Guide for information about the session timeout between Administration Server and Administration Client.
This section describes the NMShell enhancements.
Offline Mediation Controller NMShell now performs the following tasks at the command line:
Before you import the node configuration or customization into a mediation host, you must first add the mediation host to the Node Manager. Offline Mediation Controller now allows you to add a mediation host by using the new addhost command.
See "Adding Mediation Hosts to the Node Manager" in Offline Mediation Controller System Administrator's Guide.
Offline Mediation Controller now allows you to export a mediation host's node configuration and node customization by using the new export command.
See "Exporting Node Configuration and Node Customization" in Offline Mediation Controller System Administrator's Guide.
Offline Mediation Controller now allows you to import node configuration and node customization into a mediation host by using the new import command.
See "Importing Node Configuration and Node Customization" in Offline Mediation Controller System Administrator's Guide.
Offline Mediation Controller now allows you to start all nodes in a mediation host by using the new startNodes command.
See "Starting All Nodes" in Offline Mediation Controller System Administrator's Guide.
This section describes the cartridge pack enhancements.
Offline Mediation Controller now supports Oracle Communications Elastic Charging Engine. It can now:
Process the Network Accounting Record (NAR) data.
Submit the usage requests to Elastic Charging Engine.
The Elastic Charging Engine cartridge pack contains a single Distribution Cartridge (DC) node that creates usage requests based on the input call data records (CDRs) and submits the usage requests to Elastic Charging Engine for processing. The cartridge pack is used with the following existing cartridge packs to process the input records:
Simple ASCII
IMS
SGSN
See Offline Mediation Controller Oracle Communications Elastic Charging Engine Cartridge Pack User Guide for more information.
The IMS CDF/CGF cartridge pack now complies with the following standards:
3GPP Technical Specification 32.298 V10.5
3GPP Technical Specification 32.260 V10.4
3GPP Technical Specification 32.299 V10.2
See Offline Mediation Controller IMS CDF/CGF Cartridge Pack User Guide for information about the IMS CDF/CGF cartridge pack.
The SGSN06 cartridge pack now includes the following enhancements and updates:
New SGSN CDR fields based on 3GPP TS 32.251
Support for 3GPP TS 32.298 V10.5.0 for ASN.1 definition
Version hiding support for V10.5.0 to 7.3.0 and V10.5.0 to V6.4.1
See Offline Mediation Controller SGSN06 Cartridge Pack User Guide for information about the SGSN06 cartridge pack.
Previously, the Microsoft IPTV Collection Cartridge (CC) sent a single request for billing event records to the IPTV platform, and the IPTV platform would return the billing event records in one batch over the SOAP/HTTP connection. When there was a high volume of billing event records, the SOAP/HTTP connection often timed out before the IPTV platform could finish preparing and returning the billing event records.
To prevent timeout errors, the CC now allows you to send multiple small requests for billing event records.
You specify how each CC node manages its billing event record requests by using new fields in the Administration Client's SOAP Settings tab. Table 1-1 describes the new fields.
Table 1-1 SOAP Settings Tab Fields
| Field Name | Description |
|---|---|
|
Timeout |
Specifies the timeout value for each connection from the CC to the IPTV platform. The timeout value is specified in minutes or hours. The default is 1 hour. |
|
Start Time |
Specifies the starting timestamp for all billing event records that you are requesting. The CC requests all billing event records that were created after the specified start time. The default is the current date and time. |
|
Use Configurable Window |
Specifies whether the CC sends a single request or multiple requests to the IPTV platform.
|
|
Configurable Window |
Used when calculating the ending timestamp for all billing event records that you are requesting. Enter a value and then select MIN(S), HR(S), or DAY(S). The CC calculates the ending timestamp by adding the Configurable Window value to the Start Time value. The CC requests all billing event records that were created between the specified start time and the calculated end time. For example, if you set Start Time to Jan 1, 20012 12:00:00 and Configurable Window to 24 HR(S), the CC requests all billing event records that were created between 12:00 pm on January 1, 2012 and 11:59 am on January 2, 2012. |