2 Cartridge Pack Overview

This chapter contains an overview of Oracle Communications Offline Mediation Controller Nortel GSM/UMTS AMA cartridge pack.

The AMA cartridge pack provides the functionality to collect AMA data from DMS-MSC SDMs, process that data and send it to downstream applications such as billing systems and/or databases. The cartridge pack includes nodes that are responsible for collecting, processing and distributing the data. The DMS-MSC CC collects G-CDR and GHOT records from DMS-MSC SDMs and these records are distributed in AMA DIRP, ASCII or ASN.1 format to downstream billing systems and to databases for storage and search capabilities.

New Features

This section lists the new features.

AMA 6.0.0

This cartridge pack now works with Oracle Communications Offline Mediation Controller 6.0.

AMA 3.5.8

The following feature was added in this version of the AMA cartridge pack:

The NPL rule files for the JDBC and ASCII distribution cartridges are enhanced to provide a more targeted range of warnings for date stamps from a device. The NPL function changes from str2int to str2decimal.

AMA 3.5.7

The following feature was added in this version of the AMA cartridge pack:

  • The JDBC DC now checks for partition locking before trying to insert data into a table. A retry period has been added to the functionality, which prevents the JDBC DC from halting its operations.

AMA 3.5.6

The following feature was added in this version of the AMA cartridge pack:

  • The "File Retention" feature will delete or archive the files in the compressed folder when a "compression" option is selected.

AMA 3.5.5

The following feature was added in this version of the AMA cartridge pack:

  • 1:1 input/output file matching support for GSM18

AMA 3.5.4

The following feature was added in this version of the AMA cartridge pack:

  • Enhanced the filename capability of Parameter (PAR) script to include a timestamp

  • Additional GSM support: GSM16 in -> GSM16 out (ASCII and Database), GSM16 in -> GSM15 out (Database),GSM18 in -> GSM16 out (Database).

  • 1:1 input/output file matching support for G-CDR collection with AMA DIRP file distribution. The file matching support includes multiple characters in the configurable File Prefix parameters.

AMA 3.5.3

The following feature was added in this version of the AMA cartridge pack:

  • Ability to support the creation and archiving of multiple database tables, such as support for DMS 100 MMP and AMA.

The following change was made in this version of the AMA cartridge pack user guide:

  • Updated the procedures for the various supported upgrade options.

AMA 3.5.2

On the DMS-MSC AMADIRP DC, if the option "Keep Empty File" is unchecked and there is no CDR data, the file sequence number is erroneously incremented when the cartridge is stopped and restarted.

AMA 3.5.1

Previously, when the DMS-MSC AMADIRP DC was not configured to "Keep Empty Files" and the "Generate FTOR" option was selected, if there was no CDR processed during the rotation time, an empty CDR file was generated that contained only the FTIR and FTOR. The file sequence number was incremented.

The new behavior is the file will not be generated and the file sequence number will not be incremented.

AMA 3.5.0

The following feature was added and enhancement made to the DMS MSC AMA CC and the NRTT CC nodes in this version of the AMA cartridge pack:

  • The recovery files can now be deleted at user-configured intervals.

  • The value of the "Keep processed files duration" parameter is increased to 60 days.

The following fix was made in this version of the AMA cartridge pack:

  • The DMS-MSC AMA DIRP node can generate empty files even if the "Keep empty files" box is not selected. This issue has been fixed.

AMA 3.4.0

The AMA 3.4.0 cartridge pack was updated in conjunction with Offline Mediation Controller 6.0.

AMA 3.2.3

The following feature was propagated from a previous cartridge pack version:

  • Version hiding for GSM 18 to GSM 16/15: If the GSM 18 field "MS-Classmark" has the default value "FFF0FFFFFFFFFFFC", it will be mapped to "FFF0FF0C" instead of "FFF0FFFC" in the GSM 16/15 output.

AMA 3.2.2

The following fix was made in this version of the AMA cartridge pack:

  • The DMS-MSC AMA CC can lead to too many files being left open at the OS level. This problem only occurred when the FTP Push transport is used. This issue has been fixed.

AMA 3.2.1

The following feature was added in this version of the AMA cartridge pack:

  • The DMS-MSC CC and the NRTT CC now support processed file retention of up to 48 days.

AMA 3.2.0

The following feature was added in this version of the AMA cartridge pack:

  • DMS MSC AMA DIRP DC: The "Generate FTOR" checkbox was added to optionally enable the File Transfer Out Record parameter. The FTOR parameter contains the following fields, as per the GSM 16 Specification:

    • Record Header

    • Auxiliary Record Header

    • Date and Time

    • Generic Identity

    • File Transfer Type

    • File Sequence Number

    • Record Count

    • Block Count

    • Record Number

AMA 3.1.5

The following fix was made in this version of the AMA cartridge pack:

  • Version hiding for GSM 18 to GSM 16/15: If the GSM 18 field "MS-Classmark" has the default value "FFF0FFFFFFFFFFFC", it will be mapped to "FFF0FF0C" instead of "FFF0FFFC" in the GSM 16/15 output

AMA 3.1.4

The following feature was added in this version of the AMA cartridge pack:

  • DMS MSC CC: Keep/Delete recovery file tracking was added for the FTP Push transport parameter, to prevent the processing of duplicate input files.

AMA 3.1.3

The following fixes were made in this version of the AMA cartridge pack:

Fix:

  • Version hiding for GSM 18 to GSM 16/15: The GSM 18 field "MSC/MGW Number" in the record "Common Equipment Usage" (Structure Code 0019) is mapped to the GSM 16/15 field "MSC-Number".

  • Version hiding for GSM 18 to GSM 16: National Use-Values in Calling/Called Subscriber Category for MOC and MTC will be converted correctly to "000" for new values in GSM 18.

  • Version hiding for GSM 18 to GSM 15: Data Rate Character (Char 4) value "8" is mapped to value "0" if Character 3 is equal to "0" and Character 1 is equal to "2".

AMA 3.1.2

The Crystal Reports templates for the following call/service records have been updated to include the Data Service module code:

  • Incoming Gateway Call Attempt

  • Outgoing Gateway Call Attempt

  • Incoming Intra-PLMN Trunk Record

  • Outgoing Intra-PLMN Trunk Record

  • Roaming Call Attempt

AMA 3.1.1

The following fixes were made in this version of the cartridge pack:

  • Version hiding for GSM18 to GSM16 or GSM15:

    • Module Code 028 Field "Patch Identity" will be deleted

    • Module Code 09 will be deleted for records with Structure Code 0013, 0014, 0015 and 0016

    • Characters 'Channel Rate and Type' and 'Data Rate' of the Field Channel Type in MC03 will be mapped according to the version hiding tables in this document

    • Field "SMS Result" Protocol Value "01" will be changed to "00"

  • Version hiding for GSM16 to GSM15:

    • National Use-Values in Calling/Called Subscriber Category for MOC and MTC will default to "000"

AMA 3.1.0

The AMA 3.1.0 cartridge pack includes Input Stream Monitoring on the DMS-MSC CC, NRTT CC and on all DCs. Input stream monitoring is enabled on a per-cartridge basis to detect whether any records have been received for an operator-defined period of time. The cartridge raises an alarm when it does not receive any new records within a specified time period, and clears the alarm when it begins to receive records again.

Alarms

All Offline Mediation Controller alarms are listed in the alarms.txt file located in the OMC_Home directory (OMC_Home is the directory in which you installed Offline Mediation Controller.) No new alarms are introduced in this cartridge pack.

Architecture diagrams

Figure 2-1, Figure 2-2, and Figure 2-3 show the supported node chains for the AMA cartridge pack, and how the node chains collect, process and distribute data.

Figure 2-1 AMA Architecture with G-CDR Collection in AMA DIRP File Format

Description of Figure 2-1 follows
Description of "Figure 2-1 AMA Architecture with G-CDR Collection in AMA DIRP File Format "

Figure 2-2 AMA Architecture with G-CDR Collection in NRTT Distribution

Description of Figure 2-2 follows
Description of "Figure 2-2 AMA Architecture with G-CDR Collection in NRTT Distribution "

Figure 2-3 AMA Architecture with G-CDR and GHOT Collection in AMA DIRP File Format

Description of Figure 2-3 follows
Description of "Figure 2-3 AMA Architecture with G-CDR and GHOT Collection in AMA DIRP File Format "