“It Is How Mediation Can Be Done”

Mercury has the flexibility to mediate various types of network transactions at different volumes, providing you scalable mediation for current and future capacity. Mercury’s tiered architecture allows for the manipulation of data in a single tier while supporting continuous processing in the other tiers. The flexibility of Mercury allows for the delivery of a single transaction to multiple destinations.

The basic Mercury package takes the formats provided by the switches, routers and third party feeds and delivers filtered and translated formatted records to the billing platform.

Mercury Architecture

Mercury consists of the multiple tiers that are designed in such a way to complement the preceding and the following tiers, but each tier has no internal dependencies with those tiers.

It is required that each tier pass the data forward for the following tier to process the data, but if one tier is hung up, or undergoing maintenance, the other tiers will continue to process all available data.

Mercury Mediation consists of the tiers for collecting the traffic from the multiple sources, translating the transactions and producing them in an aggregated file for delivery to the billing platform.

Features

• Compatibility
  Mercury is Hardware and OS independent.
  
• Maintenance and Operations
  Mercury was designed to reduce operator and management time expenditures by monitoring its own activities and sending messages when  attention is required. Reports may be scheduled to run at specific times and the results can be emailed to the recipients. The Mercury backup methodology provides the ability to pause the data store module processing, backup critical data and resume the module without requiring operator intervention.
  
• Availability
  Mercury is designed to provide maximum availability. Each module is designed to run independently of other modules. Upgrades or infrastructure outages on one module do not interrupt the unaffected modules.
  
• Reporting
  Mercury provides access to enriched data transactions by using third party data and connections to the billing system to provide. Mercury contains a module that provides web based reporting to access individual detail records in seconds. Web based graphs and charts provide an easy to use and easy to understand interface.
  
• Flexibility
  Custom processes may be integrated into to Mercury by simply entering a record into the process workflow or job schedule. The special job for the difficult customer becomes a part of the system instead of an additional operator task. New feeds and formats may be added without interfering with the current system.
  
• Scalability
  Every processing element of Mercury is scalable. Collectors, Translators and data stores may be added as transaction volumes increase.
  
• Processing Features
  • Polling On Lucent 5ESS Switches using AMATPS
  • Supports Primary and Secondary polling
  • Polling parameters for each switch are user definable
  • Supports Remote Node polling and Delivery
  • Automated unattended polling (if other subsystems are shutdown, polling continues)
  • Provides status messages during polling
    
• AMATP tape processing and third party feeds are supported
  • Users can create and edit file formats
  • Fixed (EMI), Variable, Comma Delimited
    
• Translation Capabilities
  • Supports multiple user inputs and outputs
  • Supports packet based or file based data transfer
  • Generates processing reports, statistics and emails
  • Supports remote Node data translation
  • Supports multiple translators
  • User definable processing parameters are supported