ASMM 8.2 - Overview

AMDOCS MEDIATION RELEASE 8.
Amdocs Service Mediation Manager 8.0

Overview
Document Information
Release: Publication Date: Catalog Number: Information Security: 8.0 December 2009; updated November 2011 for Service Pack 2 1531915 Level 1 Confidential
1997 2011 Amdocs. All Rights Reserved. The included software and/or documentation cannot be reproduced, downloaded, disseminated, published, transferred, or combined with any other materials, in whole or in part, in any form or by any means, without the prior written consent of Amdocs. The included software may contain and utilize third-party software products. These materials are confidential, and shall be returned to Amdocs upon request. Amdocs reserves the right to revise the included software and/or documentation and to make changes in the content from time to time without notice. The trademarks and service marks of Amdocs, including the Amdocs mark and logo, Ensemble, Enabler, Clarify, Return on Relationship, Intelecable, Collabrent, Intentional Customer Experience, CES, Cramer, Qpass, SigValue, DST Innovis, JacobsRimell, ChangingWorlds and jNETx are the exclusive property of Amdocs, and may not be used without permission. All other marks are the property of their respective owners.
Table of Contents
1 Introduction......................................................................................................................... 1
Purpose and Scope.............................................................................................................................2 Target Audience ..................................................................................................................................2 Prior Knowledge ..................................................................................................................................2 Related Documents.............................................................................................................................3 Typographical Conventions.................................................................................................................3 Terms and Definitions .........................................................................................................................4
System Features................................................................................................................. 7
Highlights and Benefits........................................................................................................................8 Convergent Mediation Platform...........................................................................................................9 Distributed Architecture and Carrier-Class Scalability.......................................................................10 Modular, Adaptable, and Easily Configurable ...................................................................................10 Next-Generation, Customer-Level Service Assurance......................................................................12 Extensibility .......................................................................................................................................12 High Reliability...................................................................................................................................13 Adaptability to the Network, Business Support Systems and Operator Support Systems ................13 Manageability ....................................................................................................................................14 System Repository for Managing Components.................................................................................15 Advanced Monitoring and Reporting Capabilities .............................................................................16 JMX Monitoring .................................................................................................................................17 Integration with Operational ..............................................................................................................18 Security Features ..............................................................................................................................18
Ability to Select the Security Mechanism ................................................................................................18 Session Timeout .....................................................................................................................................18 Secure Communication Channel ............................................................................................................19
Support for Multi-Language Text Encoding and Decoding................................................................19 Mediation Types ................................................................................................................................20 Active Mediation ................................................................................................................................20
Active Mediation Examples.....................................................................................................................21 Architecture.............................................................................................................................................21 Incremental Deployment .........................................................................................................................24
System Components........................................................................................................ 25
Introduction........................................................................................................................................26
Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs
iii
Amdocs Service Mediation Manager 8.0 Overview
Central Event Manager .....................................................................................................................27 User Interface Server ........................................................................................................................27 Gatherers ..........................................................................................................................................28 External and Modular Components...................................................................................................28
Information Sources................................................................................................................................28 Information Source Modules ...................................................................................................................29 Types of ISMs .........................................................................................................................................30
Configuration Database.....................................................................................................................31
System Functions............................................................................................................. 33
Supported Data Formats ...................................................................................................................34 Data Processing in Batch-Mediation Projects ...................................................................................35
Collecting Data........................................................................................................................................35 Enhancing and Processing Data.............................................................................................................35 Storing Data ............................................................................................................................................36 Exporting Data to External Systems and Applications............................................................................36
Data Processing in Active-Mediation Projects...................................................................................37 Component Repository......................................................................................................................38 Reporting...........................................................................................................................................38 Error Management ............................................................................................................................39 Auditing .............................................................................................................................................39
Audit Service...........................................................................................................................................39 Project-level Audit ...................................................................................................................................40
Monitoring..........................................................................................................................................42
Event Infrastructure and Log Files ..........................................................................................................42 Amdocs Service Mediation Manager Monitoring Interface .....................................................................43 Monitoring Runtime Operation of Projects ..............................................................................................43 Chain Monitor..........................................................................................................................................44
Statistics ............................................................................................................................................44
Statistics Service.....................................................................................................................................44 Statistics in Batch-Mediation Projects.....................................................................................................45 Statistics in Active-Mediation Projects ....................................................................................................45
Patch Management ...........................................................................................................................46
iv
Introduction
Amdocs Service Mediation Manager is a carrier-class business infrastructure converged mediation solution that combines data collection, data processing and data synthesis, data export, and automated user-account provisioning on a single platform. It collects information from data and voice networks and transforms the data into business intelligence, enabling providers to understand how their networks are used and to translate this knowledge into new revenue by developing and managing new profitable services. Amdocs Service Mediation Manager consists of the Network-to-Business platform and modules (ISMs). Amdocs Service Mediation Manager provides a bi-directional, real-time link between the physical network infrastructure and Operations and Business Support Systems (OSS/BSSs) to enable advanced network and service usage and automated service provisioning. Purpose and Scope .............................................................................................. 2 Target Audience.................................................................................................... 2 Prior Knowledge ................................................................................................... 2 Typographical Conventions .................................................................................. 3 Terms and Definitions ........................................................................................... 4
Purpose and Scope

This book provides an overview of Amdocs Service Mediation Manager. This book contains the following chapters:
Chapter 1, Introduction, (this chapter) explains the purpose and scope of this book and how to use it. Chapter 2, System Features, describes the features and benefits of Amdocs Service Mediation Manager. Chapter 3, System Components, contains a high-level description of the applications architecture the core system components and their functions. Chapter 4, System Features, provides an overview of how the system operates, provides information about the modules, explains some important concepts in the operation of the system, provides information about the functionality that the system supports, which you can use to collect, process, and output the data.
Target Audience
This document contains information useful for anyone who needs to understand the purpose, architecture, and functionality of Amdocs Service Mediation Manager, including, but not limited to:
Amdocs Service Mediation Manager administrators who set up and configure the system Amdocs Service Mediation Manager operators who monitor the system after it is installed Implementers who use Amdocs Service Mediation Manager either as a standalone mediation solution or as a mediation solution integrated with other Amdocs products Users who need to understand the mediation and data processing functionality of Amdocs Service Mediation Manager, such as marketing teams, trainers, testers, and installers Amdocs professional services and support staff who provide product support for Amdocs Service Mediation Manager
Prior Knowledge
This book assumes familiarity with basic mediation concepts. Familiarity with Amdocs billing products is helpful, but not required. This book is part of the set of documents in Related Documents and is designed to be used in conjunction with them.
Chapter 1. Introduction
Related Documents

Amdocs Service Mediation Manager Installation Guide Amdocs Service Mediation Manager User Guide Amdocs Service Mediation Manager Operator Guide Amdocs Service Mediation Manager Business Logic SDK Programmer Guide Amdocs Mediation Glossary Amdocs Service Mediation Manager Release Notes
Typographical Conventions
The following table presents typographic conventions used in this guide.
Typeface/ Symbol Meaning Example
Italics
References to other documents, new terms, and placeholders Names of menus, options, command buttons, and fields Command-line input, on-screen computer output, sample code examples, names of files, commands, and directories What you type contrasted with computer output Variable Optional parameter or flag. A parameter that is mandatory when the optional flag or parameter in square brackets is selected.
For detailed definitions of terms, see the Amdocs Mediation Glossary. From the Object menu, choose Edit. Execute the following command:
ps -ef | fgrep vold
Bold
Courier New
Courier New Bold
Type the following:

./xacct_install
angle brackets square brackets curly brackets
<UserName>
./xacct_config run_task isid <ISID> -q [-f <FunctionName>] [-u {UserName} -p {Password}]
<HOME>, unless stated otherwise, is the Amdocs Service Mediation Manager home directory. For example, <Home>/Shared/.
Terms and Definitions

The following table lists terms and acronyms used in this document. For more detailed definitions and a complete set of Amdocs Mediation terms, see the Amdocs Mediation Glossary. For definitions of Amdocs billing terms, see the Amdocs Billing Platform Glossary.
Terms Definitions
AMC Amdocs Service Mediation Manager Monitor BL SDK
Amdocs Monitoring and Control An AMC plug-in that enables the monitoring of Amdocs Service Mediation Manager using AMC. Business Logic SDK. An infrastructure of Amdocs Service Mediation Manager that allows users to develop customized code plug-ins geared at resolving specific business needs in a mediation solution. A component of the Network-to-Business platform that coordinates, manages, and controls the operation of the platform. A single place to define and manage components in the system. This way you can define a component, such as record, rule, or function once and then use it in the Business Logic for several ISMs. A type of ISM that serves as an interface between a Gatherer and a network element that feeds data from the network element into Amdocs Service Mediation Manager. A type of ISM that acts as an interface between a Gatherer and a network element that provides functions (DEM functions), which can be used to query the DEM in order to enhance the collected data with data from other sources such as reference tables or other modules. A type of ISM that receives data from another ISM and exports it to a batch file where the data can be accessed by post-processing applications, referred to as Customer Care and Billing (CCB) systems, such as rating and billing applications. A type of ISM that receives data, processes it, and stores or outputs the processed records. A type of ISM that acts as an interface between a database server and a Gatherer. It can store the data the system collects in the database and query the database. Data Collection Module Data Enhancement Module .A synchronous function of a DEM (a special type of task) that can be used in the enhancement process as part of the Field Enhancement definition. See task.
Central Event Manager Component Repository
Data Collection Module
Data Enhancement Module
Data Export Module
Data Processing Module Data Storage Module
DCM DEM DEM function
Chapter 1. Introduction
Terms
Definitions
DPM DSM DXM DC DC group
Data Processing Module Data Storage Module Data Export Module See direct connection. A group of IS instances connected through Enhancement Procedure instances configured to work in direct connection (DC) reliability mode. A reliability mechanism of an Enhancement Procedure (EP) instance used for transferring data between IS instances residing on the same Gatherer. The set of operations that define the route of the data in Amdocs Service Mediation Manager from its source (the trigger) to its destination (the target). For flat record streams, the EP includes Field Enhancements for every field in the target that receives data from the trigger. From the perspective of the Network-to-Business platform, a hierarchical record stream appears to have a single field whose data type is record, and the EP includes one simple Field Enhancement. Enhancement Procedure is the generic term that refers both to an Enhancement Procedure template and an Enhancement Procedure instance. The generic term (Enhancement Procedure) is used when the distinction between the Enhancement Procedure template and the Enhancement Procedure instance is not relevant (either because the statement applies to both types of objects or because the object type is clear from the context). Enhancement Procedure Part of an Enhancement Procedure transferring records that defines how the data obtained from a field in the trigger is processed to fill a single field in the target. A component of the Network-to-Business platform that hosts IS instances. An instance of an ISM. An add-on to the Network-to-Business platform, which enables it to collect, enhance, process, store, and export usage data, typically by providing an interface between a Gatherer and a specific network element, device, or database server. A file that is processed along a chain. Java runtime environment A core component in the Network-to-Business platform, such as the CEM, the UIS, and a Gatherer.
direct connection
Enhancement Procedure
EP Field Enhancement
Gatherer IS ISM
job JRE node
Terms
Definitions
project task
A subset of the system configuration, which includes a collection of configuration objects. A synchronous function exposed by an ISM instance that can be invoked from the Amdocs Service Mediation Manager user interface, from a command line interface, or from another ISM instance using an internal API. Compare to DEM function A blueprint of a configuration object used to create multiple instances of the object. A template can include one or more IS templates and Enhancement Procedure templates that are associated with these IS templates. User Interface Server A component of the Network-to-Business platform that provides local and remote control of the system by enabling users to access the Amdocs Service Mediation Manager user interface.
template
UIS User Interface Server
System Features
This chapter describes the features and benefits of Amdocs Service Mediation Manager. Highlights and Benefits ......................................................................................... 8 Convergent Mediation Platform ............................................................................ 9 Distributed Architecture and Carrier-Class Scalability ........................................ 10 Modular, Adaptable, and Easily Configurable..................................................... 10 Next-Generation, Customer-Level Service Assurance ....................................... 12 Extensibility......................................................................................................... 12 High Reliability .................................................................................................... 13 Adaptability to the Network, Business Support Systems and Operator Support Systems .............................................................................................................. 13 Manageability...................................................................................................... 14 System Repository for Managing Components .................................................. 15 Advanced Monitoring and Reporting Capabilities............................................... 16 JMX Monitoring................................................................................................... 17 Integration with Operational................................................................................ 18 Security Features................................................................................................ 18 Support for Multi-Language Text Encoding and Decoding ................................. 19 Mediation Types.................................................................................................. 20 Active Mediation ................................................................................................. 20
Highlights and Benefits

Amdocs Service Mediation Manager is a convergent mediation platform for all networks, services, and processing modes that reduces the total cost of ownership by enabling consolidation of business processes and systems. Amdocs Service Mediation Manager serves as a network abstraction layer for Operation Support Systems and Business Support Systems. It provides all information related to network services (such as subscriber-level usage data and quality-of-service data) that is needed to create a complete picture of the network. Amdocs Service Mediation Manager enhances and processes information based on customized business criteria, and then distributes the results to target systems in a ready-to-use format. Amdocs Service Mediation Manager provides these key features and benefits:
Convergent mediation platform for all types of networks, services, and processing modes. Distributed architecture and carrier-grade scalability enabling providers to leverage their hardware investment, scale with the growth of the network, upgrade quickly and easily. Highly modular, adaptable, and easily-configurable design that speeds up the time-to-market for new services and reduces operational costs. Support for next-generation service assurance at the customer level thereby improving customer relationship management and enabling quality-of-experience-based charging. Enhanced integration with Amdocs Charging enabling users to speed up and reduce costs of implementing a network-to-bill solution and to enhance revenue assurance. Extensibility allowing users to use a Business Logic SDK to customize the system to match their business needs. High reliability ensuring high system availability. Adaptability to the network, Business Support System, and Operation Support System environments and needs. Advanced manageability that enhances usability and reduces maintenance and operational costs. Advanced monitoring and reporting capabilities. Support for multi-language text encoding and decoding.
Chapter 2. System Features
Convergent Mediation Platform

Amdocs Service Mediation Manager is a convergent mediation platform for all networks, services, and processing modes. Amdocs Service Mediation Manager integrates with all types of networks (packet-switched and circuit-switched), including fixed, mobile, cable, satellite, and next-generation networks. It also supports all types of services, including voice, VoIP, data, content, and video services. Amdocs Service Mediation Manager collects usage data from both data and voice networks from a variety of network elements, such as switches, routers, firewalls, proxy servers, mail servers, directory servers, and application servers. The gathered information provides a complete view of network activity detailing the parameters of every session. Amdocs Service Mediation Manager can handle the data in its original (raw) format or as records (flat or hierarchical). The variety of data formats and processing modes the system supports provide users with the ability to preserve the information about the original context of the data, and the flexibility to process the data as individual records or as whole files. Having one mediation platform for all their mediation needs enables providers to eliminate multiple mediation silos and thus to reduce their total cost of ownership and to enhance their business agility. Managing all mediation streams on one platform allows providers to consolidate their business processes so that they use your system resources more effectively and efficiently. Any new developed or implemented system capabilities for one line of business can be re-used by all mediation lines of business. Because providers need to maintain, monitor, and control only one system across their entire organization, they are able to substantially reduce their operational costs for mediation as well. Amdocs Service Mediation Manager dynamically processes the data it collects from all layers of the network and transforms the data into meaningful business information, linking network elements to real-world entities. The system combines and consolidates data from multiple network elements to provide a clear and detailed picture of user-level service utilization because the complete view of network activity is often not readily available from a single information source.
Distributed Architecture and Carrier-Class Scalability

Amdocs Service Mediation Manager has a highly distributed architecture that allows it to scale with the growth of the network and with the increase of the network traffic. The distributed architecture ensures data integrity and high system availability by placing intelligent software agents throughout the network, enabling transmission to multiple data repositories. The architecture is composed of several functional layers that give Amdocs Service Mediation Manager virtually infinite scalability, flexibility, and manageability. Amdocs Service Mediation Manager enables users to install multiple systems on the same computer taking advantage of multi-processor servers to scale up and run several Gatherers on a single computer concurrently. A system configuration can be shared by several distinct mediation projects, each of which can be accessed by separate users, further expanding the scalability and manageability of the system. The distributed architecture of Amdocs Service Mediation Manager enables users to better leverage their hardware investment and to use the vertical scalability of the system to transfer higher volumes of data without any extra cost. The efficient distributed processing of the system, its horizontal and vertical scalability and its support for low-cost platforms contribute to cost-efficient scalability that is needed in order to handle the ever-increasing demands of processing large volumes of data.
Modular, Adaptable, and Easily Configurable

Amdocs Service Mediation Manager includes a vast array of network data collection, processing and distribution modules (also referred to as ISMs) for legacy and next-generation services in all types of networks. With comprehensive libraries of off-the-shelf independently configurable mediation building blocks for collection, processing, and distribution, and plug-and-play architecture, Amdocs Service Mediation Manager lets users quickly create mediation processes. The modular design enables quick and easy upgrades and adaptation to service changes: implementing a change typically only requires local updates to the relevant building blocks.
Figure 2.1 Modular Design
Gatherer
Collector
Parser Gatherer Validation module DeDuplicator Gatherer Aggregator Formatter Distributor
IP switch
external application
Gatherer
Parser
Collector
Radius server
10
Amdocs Service Mediation Manager has a modern, feature-rich graphical user interface of the system that you can use to configure the system and monitor its operation. Complex configuration tasks are assisted using the familiar window-based configuration guiding techniques of wizards. Even tasks involving writing custom code plug-ins are done through user-friendly graphical interfaces. Figure 2.2 displays the Amdocs Service Mediation Manager main screen. The menus and tabs available are determined by the project that is currently open.
Figure 2.2 Amdocs Service Mediation Manager Main Screen
Amdocs Convergent Mediation allows providers to launch new services quickly and cost-effectively to market through its flexible modular architecture, adaptability features, and simple configuration. It is interoperable with existing infrastructure systems and offers high extensibility and scalability. System administrators can easily customize mediation flows and external interfaces for existing and new services.
11
The advanced modular system architecture helps keep maintenance and upgrade costs to a minimum because changes are implemented by replacing modules rather than the entire system. In addition, the GUI-driven system configuration allows fast and independent change implementation. The system can also be used as an interfacing and processing bridge between Business Support Systems and Operator Support Systems, covering intersystems functionality gaps that are created as a result of convergence or systems upgrade. The overall effect of the system flexibility translates into faster time-to-market for new services and reduced operational costs.
Next-Generation, Customer-Level Service Assurance

Amdocs Service Mediation Manager enables providers to improve service assurance and customer service because it can collect and process quality-of-experience information at the customer level. Using the information the system collects, providers gain an understanding of the customer service experience that they can use to provide proactive, rather than reactive, customer service. Amdocs Service Mediation Manager can collect vital customer service experience information from both network elements and from Operator Support Systems, depending on the type and depth of information that is needed. This raw data includes details such as service failures and different types of service quality measurements. The system then correlates, aggregates, and adds this service experience data to the customer usage data and in that way provides an integrated view of the customer service experience. This information can be used to improve customer service by enabling an optimal and proactive response to customer problems. It also allows providers to improve the handling of service problems because it enables them to prioritize these problems more effectively based on the actual customer impact. Providers can also use the information to charge customers based on the quality of the entire experience, whereby customers are charged based on their usage and their service experience.
Extensibility
Mediation processes can be independently customized according to business needs by employing the Business Logic software development kit (SDK). The kit provides advanced tools for mediation processes creation including a configuration manager, processing functions manager, data mapping manager, rule manager and more. Amdocs Service Mediation Manager is the quintessential mediation applications development platform. For more information about the Business Logic SDK, see the Amdocs Service Mediation Manager Business Logic SDK Programmer Guide.
12
High Reliability
Amdocs Service Mediation Manager is designed to assure the highest level of reliability. The high system reliability of Amdocs Service Mediation Manager prevents the risk of data loss and data duplication. The system also has swift and efficient data recovery mechanisms. For more details about the reliability features, see the Amdocs Service Mediation Manager User Guide. The system has a high availability that is achieved through the Watchdog process, which runs in the background and monitors the operation of each component. The Watchdog restarts the component if one of its critical functions fails. Amdocs Service Mediation Manager allows users to implement a High Availability solution in a LAN and a WAN environment, ensuring uninterrupted functioning of all its components in the event of hardware failure.
Adaptability to the Network, Business Support Systems and Operator Support Systems
Amdocs Service Mediation Manager is fully adaptable to all major network technologies, including hardware, software, operations, and business support systems. The system is designed to work with industry standard protocols, which allows for the rapid and seamless assimilation of new, emerging network standards, devices and applications. A variety of flexible interface connectors enable quick and simple integration of Amdocs Service Mediation Manager with network and environments of Business Support Systems and Operator Support Systems, and quick responses to network changes. When network technology providers introduce new hardware or software, the extensive library of ISMs that Amdocs supplies allows service providers to quickly launch new services. As new network elements are deployed, new ISMs can be designed to collect and process any relevant information the network elements provide Interpretability with existing infrastructure systems is further supported by the open architecture and the use of technologies such as Java and XML. Amdocs Service Mediation Manager enables users to process the data according to their own business rules, and output it in a variety of formats to fit the needs of the downstream processing applications.
13
Manageability
The following features make it easy to set up, manage, and maintain Amdocs Service Mediation Manager:
Web-based graphical user interface through which authorized users can access the system System-wide and component-specific upgrades Amdocs Service Mediation Manager enables system-wide and component-specific upgrades, configuration changes and activation/deactivation of any of its components.
Import and export functionality Amdocs Service Mediation Manager has an import and export feature that enables users with the required access rights to export, import, and edit the configuration of the system, of individual projects, and of the environment variables, using Extensible Markup Language (XML).
Support for templates Amdocs Service Mediation Manager is configured using self-contained building blocks (templates) that are configured once and can be re-used many times. You re-use a template by creating multiple instances of the template. In each instance only some of the properties are modified. Using templates allows you to quickly configure repeating patterns of objects.
Support for self-contained independent projects Amdocs Service Mediation Manager has multi-project development environment that makes it easy for users to set up the system, manage its configuration, and monitor its operation. Each project includes a set of related objects allowing administrators to configure the system incrementally and to implement a sophisticated security policy that lets groups of users work on individual projects independently. In addition, support for projects makes it easier and less costly to make updates to individual projects without affecting the configuration of the entire system or of the other projects.
Support for users and user groups Amdocs Service Mediation Manager enables administrators of the system to implement a flexible user management policy tailored to their individual needs.
Support for environment variables Amdocs Service Mediation Manager supports environment variables: configuration parameters that are modified for every instance and stored in an external file, allowing users to easily migrate configurations from one environment to another.
For more information about templates and projects, see the Amdocs Service Mediation Manager User Guide. For more information about setting up a security policy, see the Amdocs Service Mediation Manager Operator Guide.
14 Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs
System Repository for Managing Components

Amdocs Service Mediation Manager allows administrators of the system to create, manage and search for components in a single component repository (referred to as the repository). The component repository enables configuring components (such as custom data types, records, and functions) and using the components in ISMs of the current project or projects across the system. Components in the repository are defined for use as follows:

Project-specific Can be used by all ISMs that belong to a specified project Common Can be used by all ISMs in the system
Components defined in the component repository appear in the Business Logic Configuration window of the ISMs in read-only mode. To modify a component that was defined in the component repository, you must first change the component in the component repository and then publish the repository. In the Business Logic configuration of ISMs, you can use components defined in the component repository in one of the following ways:
Attach the component The configuration of the component is referenced in the repository. If changes are made to the component in the repository and then published, the new configuration is automatically updated in the ISM. Attach and replace a component Attach a component from the repository to replace a local component. Detach the component The ISM deletes the component from the local configuration and no longer references it. Copy the component locally The ISM copies the component configuration locally. Changes that you make to the component are local and, therefore, do not affect other ISMs. Share a component with the component repository Adds components that are currently defined in the Business Logic configuration to the repository. You can share a component in one of the following ways: Share After you share the component with the repository, the component becomes read-only and you can no longer make changes to that component from the Business Logic configuration. The ISM attaches the component and references the component in the repository, and the component becomes available to other ISMs. Share as Owner The repository attaches the component and references it. Other ISMs can use the component. However, only the ISM that is the owner of the component can make changes to the component. This is useful for components that are generated by ISMs, such as an ASN.1 record.
15
The components in the repository are organized in folders. The system-defined folders define which ISMs can use the components. You can also create additional folders that are used for display purposes only and enable to easily locate components. Using the component repository ensures that:

Changes to repository components are updated across the system. If you change the configuration of a repository record, Enhancement Procedures that use the record are not deleted. If you change the configuration of a repository record, input and output tasks in the Business Logic configuration that use the repository record are automatically redefined.
Amdocs Service Mediation Manager contains a Flow to Repository Integrator wizard that enables integrating records in an existing flow with the repository automatically. For more information about the component repository, see Amdocs Service Mediation Manager User Guide.
Advanced Monitoring and Reporting Capabilities

Amdocs Service Mediation Manager provides you with a variety of ways to get information about its operation:

The log files of the system and its components Monitoring applications System Alerts Monitor Component Monitor Chain Monitor (relevant for monitoring chains in batch-mediation projects) SNMP Trap Exporter
Service Mediation Manager Monitor (batch-mediation projects only) The Management Information Base (MIB) extensions of the system and the ISMs that have a MIB User-interface indicators, such as color of icons or the status indicators for system components JMX-based monitoring
You can monitor the system or objects in the individual projects according to your access rights. You can define thresholds, configure filters and SNMP traps for all events in the Amdocs Service Mediation Manager user interface. Amdocs Service Mediation Manager also integrates with Amdocs Monitoring & Control. For more information, see Integration with Operational.
16
You can use the following methods to view auditing information:
Audit Service Configure the modules (ISMs) used to output audit information about the data that is being processed. You can direct the audit streams to external systems for further analysis or to a database, and then use the audit information that is collected to produce audit reports using the native Amdocs Service Mediation Manager reporting engine or other reporting tools. For more information, see Audit Service. Project-level Audit Tracks and reports the audit data for the entire project, rather than in the scope of the individual IS, and helps service providers reduce revenue leakage and billing errors through auditing of data. Project-level audit incorporates the audit counters and events of the Audit service. If your implementation uses the Audit service, you can either continue to use it or replace it with project-level audit. For more information, see Project-level Audit.
Amdocs Service Mediation Manager has sophisticated reporting tools that allows administrators, operators, and other users of the system to configure and generate reports using the data the system collects. Amdocs Service Mediation Manager supports a variety of output formats and formatting options allowing users to configure the system to send reports to an email address, to save them to a disk, and so on. Users can also configure the system to run scheduled reports at pre-defined intervals. For more information about the monitoring and reporting capabilities of the system, see the Amdocs Service Mediation Manager Operator Guide.
JMX Monitoring
Java Management Extensions (JMX) is a Java technology that is used in Amdocs Mediation to expose monitoring information about IS and enhancement procedure instances. You can use this information, for example, to identify potential bottlenecks or problems in a data flow and balance system load. The JMX server runs on the User Interface Server (UIS), and it receives up-to-the-minute status and statistical information from the monitoring server, including:
For each enhancement procedure, its ID, information about input and output rates, queue size, and current status. For each IS instance, its name and ID, information about the processing rate and status (such as whether it is working, paused or stopped) For each IS instance, statistical data defined in the Statistics Collection Point component and in the Statistics tab of the last page of the Information Source Properties wizard.
You can also view this information from any generic console (such as JConsole) or in-house monitoring application.
17
Integration with Operational

Support for operating system environment variables enables you to use standard operating system environment variables to configure the system (IS templates and IS instances). This way you can update the values in a centralized location during runtime and the configuration parameters are streamlined taking advantage of standardized operating system features.
Security Features
Amdocs Service Mediation Manager has advanced security features that enable users to implement to protect the integrity of their system and data. The security features include:
Ability to select one of the two supported security mechanisms Native security mechanisms Amdocs Security Manager
Session Timeout Support for a secure communication channel
Ability to Select the Security Mechanism

Amdocs Service Mediation Manager has its native security mechanism that enables administrators to easily implement and modify a flexible security policy. The security policy is based on having users, user groups, and permissions to perform certain actions. Managing users, user groups, and permissions. In addition to the native security mechanisms, Amdocs Service Mediation Manager supports Amdocs Security Manager. The integration of Amdocs Service Mediation Manager with Amdocs Security Manager enables using the security features of Amdocs Security Manager and managing the security policy of all Amdocs applications using the same application. For more information about the features and benefits of these security mechanisms and how to select the security mechanism, see the Amdocs Service Mediation Manager Operator Guide.
Session Timeout
Amdocs Service Mediation Manager provides a mechanism to handle session timeout after a configurable period of inactivity (inactivity period). The inactivity period specifies how long a user login session remains active when there has been no user activity. If there is no user activity for the pre-defined inactivity period, Amdocs Service Mediation Manager displays a countdown alert that informs you that your log in session to the Amdocs Service Mediation Manager user interface will close and provides you with the option to resume the session.
18 Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs
Secure Communication Channel

The Amdocs Service Mediation Manager components communicate using a proprietary TCP/IP-based protocol called Comm. The secure channel uses Secure Sockets Layer (SSL), a protocol for transmitting information securely on the Internet. SSL uses encryption to transmit the data securely. The URLs that use SSL start with https rather than http. The secure port for communication with the UIS should be used to log in when using https (and when the system works in secure mode).
Support for Multi-Language Text Encoding and Decoding

Amdocs Service Mediation Manager supports the Unicode standard, enabling users to use all major world languages in the system. Unicode is a single encoding scheme that supports all the currently known characters. Support for Unicode strings allows the system to accurately manipulate data in all languages, such as Japanese, Russian, and Hebrew.
Note: A Unicode-enabled browser, operating system, and database that support UTF-8 standard are required to take advantage of this feature.
Support for Unicode strings has the following main applications:
Allows using international characters (that is, characters that are not part of the Latin alphabet set, such as characters in Cyrillic, Devanagri, and Chinese characters) in the Amdocs Service Mediation Manager user interface. For example, users can enter the names of configurable system objects, such as queries, reports, users, and Gatherers in the Amdocs Service Mediation Manager user interface using international characters. Allows users to get and store data from Information Sources in languages that use international characters. For example, a file with data in Chinese can be used as an Information Source.
Note: In addition to the requirement for using a Unicode-enabled operating system and database configured to work with UTF-8, the ISMs that get, process, store, and export the data must support the Unicode standard for the system to get data in languages that use international characters.
19
Mediation Types
Amdocs Service Mediation Manager supports two types of mediation:
Batch Passive, uni-direction mediation that collects usage data from the network, processes the data, and then sends the results to the target system. Batch mediation receives requests, collects files off-line, and then processes the data. Batch processing does not return answers immediately. Use batch mediation for applications that do not require real-time processing of data, such as postpaid billing applications. Active Bi-directional mediation that responds to service-authorization requests in real-time, directly from network elements. Using active mediation you can support highly available and dynamically load-balanced environments that handle transactions in real-time. Active mediation enables to use services that require real-time response, such as prepaid data services, sophisticated content services authorization, and dynamic re-provisioning. For more information, see Active Mediation.
Each project can use either batch mediation or active mediation.
Active Mediation
Active mediation enables Amdocs Service Mediation Manager to act as a Decision Engine that intercepts service events of different types in real-time, and then activates a decision process that is based on Business information to determine the service flow. The decision process uses pre-defined decision trees that can be created or modified dynamically. Both event details and BSS/OSS parameters are used to get to a service decision. The service decision can be to approve the use of a service, to reject the use of a service, or it can define the next service execution step. The decision is then forwarded to the relevant network elements for implementation. The decision process is divided into two steps:
Sorting process Sorts the different types of events based on data that is part of the event data Decision process Defines the result of the process based on parameters that are part of part of the event data and external parameters obtained from the BSS/OSS
Active mediation enables to:
Automate the handling and validation of service-authorization requests and guarantee continuous service availability. Respond to service-authorization requests in real-time directly from network elements, including content-aware gateways and routers, to correlate the requests, price them according to flexible pricing rules, debit or replenish customer accounts, and then send service-authorization responses to calling applications. Provide an interface between new network elements (such as GGSN) and BSS. Maintain a mirror-image of the current state of each service-authorization request, thereby minimizing the risk of data loss and assuring a high level of service reliability.
20
Operate in a Highly available and dynamically load-balanced environments that handle transactions in real-time. Provide content and Access control.
Active Mediation Examples

The following scenarios provide examples for active mediation:
Define charging of a prepaid customers When a prepaid customer requests to use a certain data service such as MMS, the Service Control system sends a request for service authorization to the decision engine. The decision engine then requests rate and balance information from the rating and balance management systems. After the decision engine receives the information it determines whether to approve or reject the service. If the request is approved, quota for the session is reserved and the decision engine keeps tracking the session to enable proper charging and to terminate the session if the balance ends.
Dynamic re-provisioning that enables dynamic bandwidth management. When a request to increase bandwidth for a specific subscriber is received, the decision engine consults the provisioning system, which holds relevant information, and then decide whether to grant the request. If the request is approved, the decision engine sends the re-provisioning request to the provisioning system, which in turn implements it.
Architecture
An Active Mediation flow is constructed of one or more Clusters. Each cluster is constructed of nodes, which are represented by one or more Gatherers that operate according to schema-rules. Each Gatherer is a node in the cluster and contains a single instance of a template, which represents the business logic of a single node. A primary node in a partition handles tasks. A secondary node in a partition receives and saves updates of the current state of transactions that are handled by the primary node of that partition so that it can replace the primary node without any loss of data, if the primary node fails. Figure 2.3 describes the active-mediation architecture. Monitoring, statistics, and audit functions are not depicted.
21
Amdocs Service Mediation Manager 8.0 Overview Figure 2.3 Active-Mediation Architecture
Network-to-Business Platform Non-partitioned Cluster (Network-Interface) Partitioned Cluster (Service Logic)
Partition 1
Back-up Node - Gatherer 4 Node 1 - Gatherer 1 Primary Node - Gatherer 3
ISM Network Interface module (ISM)

Shared Memory Node 2 - Gatherer 2
ISM
ISM
Shared Memory
Partition 2
Back-up Node - Gatherer 6 Primary Node - Gatherer 5
ISM ISM Network Interface module (ISM)

Oracle DB with fast logging table component
ISM
Service Logic Manager module
Shared Memory
UID 1352632 Legend Service Connection Smart Load-Balancer Task (hierarchical)
The active mediation architecture is modular and hierarchical, consisting of the following main elements:
ISMs and ISs Enable to collect, enhance, and process data. An IS is a configured instance of an ISM. Each IS is assigned a unique name and is configured to belong to a cluster. The ISMs in an active-mediation project fall into the following main categories: Network-interface module Interacts with network elements, such as GGSN, handles service-authorization requests, and converts the incoming requests from raw data into hierarchical records. Network-interface modules are configured in non-partitioned clusters, in which all Gatherers are active and redundant. For example, the Diameter Server ISM is a network-interface module. Service-logic manager module Acts as the main processing point between the network-interface cluster and service elements (such as a rating engine or a balance manager), and can query data from another module. Service-logic manager modules are configured on partitioned clusters and therefore there is load balancing between their instances. For example, you can configure the Business Logic SDK ISM as a service-logic manager module.
22
Upstream Servers
Network Element
Service Logic Manager module
Enhancement module Enhances the data of a network-interface module or service-logic manager module, such as loading and storing reference data, or connecting to an external balance manager. For example, the you can configure the Business Logic SDK ISM as a service-logic manager module. Audit module Active Mediation Audit Logging ISM collects auditing and revenue-assurance data and loads the data to an Oracle database. This ISM is required for the implementation of the project-level audit feature.
Gatherers Main component of the Network-to-Business platform that supports the main usage-data processing operations. A dedicated Gatherer is used for a Cluster Lookup Agent that maintains information on the state of the clusters, such as the Gatherers currently running on a cluster, and the partitions to which each Gatherer belongs.
Clusters A group of one or more Gatherers. Each cluster has a unique system-wide name. You can define a Shared State Table (SST) that maintains state of the nodes in the cluster and enables to manage sessions. Clusters can have one of the following types: Non-partitioned Clusters that contain a module (ISM) that interfaces with a network element such as the Diameter Server ISM. Non-partitioned clusters are fully redundant and all Gatherers perform the same tasks. Typically, the contents of a non-partitioned cluster are not resource-consuming and do not require load balancing. The network-interface ISM receives service requests, parses the requests, validates them, and then sends them on a Service Connection to a partitioned cluster. Partitioned Clusters that contain one or more service-logic modules (ISMs) or that interface with service elements. Each Gatherer is assigned to a partition. Each partition contains one active Gatherer, which is the first Gatherer to launch, and one or more hot back-up Gatherers. Only the active Gatherer of a partition processes data. Amdocs Service Mediation Manager performs load balancing between the partitions by dividing messages between nodes based on the routing criteria. If you select a user defined routing criteria you perform load balancing based on values of fields such as Subscriber ID and service-type.
Service Connections Bi-directional connections between non-partitioned clusters and partitioned clusters. A service connection carries responses to the original request messages so that the network-interface module, which sends these responses to the network element. A Service Connection is analogous to an Enhancement Procedure in a batch-mediation project, but it supports two-way data traffic.
23
Incremental Deployment
Incremental deployment ensures high availability in an active-mediation project. It allows data processing to continue while configuration changes are deployed and eliminates the risk of data loss or data corruption when deploying the project configuration. When a Gatherer receives the configuration, it compares the version of its current configuration to the version that it has just received. If the new configuration is more recent, the Gatherer updates its configuration and then restarts. A project can contain partitioned or non-partitioned clusters. Each cluster can contain several nodes, which stop their runtime operation and restart to deploy configuration changes. To allow data processing while deploying configuration changes, the configuration is incrementally deployed in two stages as follows:
1. Configuration is deployed to the backup nodes in the partition. The backup nodes send
the deployed version back to the CEM.

2. Configuration is deployed to the primary nodes.
In non-partitioned clusters and for cluster lookup agents, the deployment priority determines which set of Gatherers update the configuration during the first stage and which set update the configuration during the second stage.
24
System Components
This chapter contains a high-level description of the applications architecture the core system components and their functions. Introduction ......................................................................................................... 26 Central Event Manager....................................................................................... 27 User Interface Server.......................................................................................... 27 Gatherers............................................................................................................ 28 External and Modular Components .................................................................... 28 Configuration Database ...................................................................................... 31
25
Introduction
Amdocs Service Mediation Manager consists of the Network-to-Business platform and modules, which are also referred to as ISMs. The Network-to-Business platform includes the following components:
Central Event Manager (CEM) Coordinates, manages, and controls the operation of Amdocs Service Mediation Manager and all its components. User Interface Server (UIS) Web-accessible secure point of contact for administration and management of Amdocs Service Mediation Manager. Gatherers Smart-agents that host and manage ISMs and the data collection and processing activities of those ISMs. You can add one or more Gatherers.
You can add any number of ISMs to Amdocs Service Mediation Manager. Amdocs Service Mediation Manager stores configuration data in a database server, which is sometimes referred to as the configuration database (see Configuration Database for more information).
Figure 3.4 Amdocs Service Mediation Manager Architecture (Example)
OSS/BSS system processing application

reports access to user interface
processing application
CEM Amdocs Service Mediation Manager

Enhancement Procedure Gatherer
report data
UIS
DPM
DXM
Parser
Business Logic ISM
DCM
DSM
DPM DEM
File Transporter ISM
Formatter
network element network infrastructure
store
query
database server
network element
network element
26
Chapter 3. System Components
Central Event Manager

The Central Event Manager (CEM) coordinates, manages, and controls the operation of Amdocs Service Mediation Manager and all its components. The CEM has the following main functions:
Coordinates, controls, and manages the collection, processing, and transfer of data. The CEM coordinates the operation of the Gatherers and manages the flow of data in the system through the collection scheme defined in the system configuration. Based on the collection scheme the CEM determines the computation flow (the set of operations Amdocs Service Mediation Manager performs to obtain the desired information). The CEM controls all the Gatherers, instructing them to perform the sequence of operations defined in the computation flow. Provides centralized system-wide licensing and ISM installation. ISMs are installed on the host computer of the CEM. The CEM distributes the ISM software to the appropriate Gatherers. It maintains a list of licenses installed in the system and verifies periodically if the system is properly licensed. This feature lets users centrally install and uninstall licenses. It also prevents unlicensed use of the system and any of its components. Monitors the state of the Gatherers, the ISMs, the enhancement, and the data collection process. The Gatherers periodically communicate with the CEM. The CEM continuously monitors the state of each Gatherer and Information Source in the system.
User Interface Server

The User Interface Server (UIS) is a Web-accessible secure point of contact for administration and management of Amdocs Service Mediation Manager. It enables multiple users to access the Amdocs Service Mediation Manager user interface concurrently through a Web browser, providing local and remote platform-independent control of the system. The UIS provides these functions through the Amdocs Service Mediation Manager user interface. The UIS is the server and the Amdocs Service Mediation Manager user interface is the Java client running in the Web browser. Access to the Amdocs Service Mediation Manager user interface is password-protected and limited to authorized users.
27
Gatherers
The Gatherers are multi-threaded smart-agents that run as background processes (daemons on UNIX operating systems). Each Gatherer can host multiple ISMs, allowing scalable configuration of the system. The Gatherers manage the ISMs that they host and their data collection and processing activities. Typically the Gatherers are strategically located close to the network elements the ISMs access to minimize traffic on the network. The Gatherers load and run the ISMs without interfering with the operation of the network elements or the other Gatherers. The Gatherers are remotely administered and controlled by the Central Event Manager, allowing for low cost central administration of the entire distributed Amdocs Service Mediation Manager system. Each Gatherer stores relevant configuration information locally ensuring that it can operate even when it is temporarily disconnected from the CEM. The Gatherers ensure the integrity of all the data in the system using their own local persistent storage, a light-weight file-based database. The Gatherers save the usage data from the ISM instances that they host persistently on the disk in a buffer, called a persistent queue (PQ). The persistency infrastructure of the Gatherers ensures the full reliability of the system. It guarantees that all the usage data that is in the system will reach its target destination and eliminates the risk of data duplication.
External and Modular Components

Amdocs Service Mediation Manager collects network session data from Information Sources. It uses Information Source Modules (ISMs) to interface with the Information Sources.
Information Sources
An Information Source (IS) is a network device or application server from which Amdocs Service Mediation Manager collects network session data. Most network devices and application servers provide logging or statistical information about their activity. Amdocs Service Mediation Manager can collect network session data from the log file of a mail server, the logging facility of a firewall, a traffic statistics table available on a router and accessible through SNMP, a database entry accessible through the Web, an authentication servers query interface, and other network devices. Routers, Web servers, firewalls, mail servers, directory servers, authentication servers, and others are examples of Information Sources. Each type of Information Source is accessed using a different method or protocol. Some generate logs, others are accessible via SNMP, yet others have proprietary APIs or any other proprietary protocol.
28
Information Source Modules

The Information Source Modules (ISMs), which typically act as an interface between the Gatherers and the network elements, extend the functionality of the system, enabling it to collect usage data from the network as well as to enhance, process, export, and store the gathered information. The functionality of an ISM determines its type. For example, a Data Collection Module (DCM) is responsible for collecting data from the network. A DCM typically provides an interface for a particular network element. The ISMs communicate with the network elements using protocols and formats such as UDP/IP, TCP/IP, SNMP, telnet, file access, ODBC, native API, and others. ISMs are add-ons to the Network-to-Business platform. They can be removed or added to the system without affecting its basic configuration. A minimum of two ISMs must be installed and configured for the system to collect and store data a Data Collection Module to get the data from the network element and a Data Storage Module to store that data in the database server and to query it. One or multiple instances of the same ISM can be configured in the system. For example, to access the data from several firewalls of the same type, several instances of the same ISM must be configured. Thus the term Information Source (IS) is also used to refer to an instance of the ISM. ISM installation, licensing, and upgrades are centrally administered by the CEM. Refer to the Amdocs Service Mediation Manager Installation Guide for details on the installation. For instructions on configuring ISMs, refer to the documentation of the specific module.
Figure 3.5 Information Source Modules (ISMs)
LDAP Server
Gatherer Aggregator ISM
Gatherer
LDAP Enhancement ISM
DNS ISM
Cisco NetFlow Pro ISM
Oracle Server ISM
RADIUS Accounting ISM
Nokia CG Pro ISM
query
store
Cisco router
Oracle Server database
Remote Access Server
Nokia Charging Gateway
DNS Server
29
Types of ISMs
ISMs exhibit several types of behaviors, according to which they are classified as Data Collection Modules, Data Enhancement Modules, Data Processing Modules, Data Storage Modules, and Data Export Modules. Most ISMs exhibit one type of behavior, but some exhibit several. For example, an ISM, such as the Cisco NetFlow Pro ISM, acts only as a Data Collection Module. The Aggregator ISM, on the other hand, is a Data Processing Module that also behaves as a Data Collection Module.
A Data Collection Module (DCM) feeds the data it collects from a network element into Amdocs Service Mediation Manager and thus triggers the flow of information through the system. The DCM receives the data from the network element and relays it to its associated Gatherer asynchronously (independently from and without synchronization with any other event in Amdocs Service Mediation Manager). For example, the Cisco NetFlow Pro ISM is a DCM. When a network session is initiated, the ISM receives the details of the session from the Cisco device and relays the data to the Gatherer. Every DCM provides at least one output stream. A Data Enhancement Module (DEM) enhances the data the system collects from primary sources using data from another source, such as a remote access server, a DHCP server, a DNS server, an LDAP server and a database. The DEM adds correlated data from the source. For example, Source/Destination IP addresses collected from a DCM are temporary, normally assigned for the duration of the user session. Using a DEM, the service provider can determine, which subscriber was assigned to that particular address for the session. A DEM supplies new information when queried by the Gatherer that hosts it. When it receives an information request from the Gatherer, it attempts to retrieve the information from the source it interfaces with and then relays the response back to the Gatherer. A DEM enhances the data by supplying DEM functions that are used in the enhancement process.
Note: DEMs can only enhance the data in flat records. Hierarchical records are transparent to the platform. The data in hierarchical records can be enhanced only using custom code plug-ins developed with the help of the Business Logic SDK infrastructure. Raw data cannot be enhanced.
A Data Processing Module (DPM) receives and processes the data. The processing stage can include flexible, policy-based data filtering, de-duplication, association, aggregation, applying business logic rules, and so on. A DPM can have input and output streams that allow it to function in a variety of ways in the enhancement process. It can receive data on its input streams, and can serve as the destination of data flowing through the system. A DPM can also send data on its output streams and thus trigger the flow of data through the system acting like a DCM. An input stream of a DPM can be the target of an Enhancement Procedure, and an output stream can be the trigger. (For more information on Enhancement Procedures, see The Flow of Data in the System in the Amdocs Service Mediation Manager User Guide.) A DPM can also act as a DEM, supplying DEM functions. A Data Storage Module (DSM) is a type of DPM that acts as an interface between a database server and a Gatherer. It can be configured either to store data and to query the data it stores or to query the data stored by another DSM.
30
DSMs that are configured to store data behave like Data Processing Modules (DPMs) because they can receive data and forward data to other ISMs. Like DPMs, DSMs have input streams that can be targets of Enhancement Procedures, and output streams that can be triggers of Enhancement Procedures. Each DSM is associated with a single table structure with a specific set of fields. The DSM performs clean-up and aging procedures on the data in the table it is associated with. It removes old data to free space for new data periodically based on a userdefined expiration period. The DSM places a timestamp on every record when the record enters the database and deletes the record after its validity expires.
A Data Export Module (DXM) is a type of DPM that receives usage data and exports it to external systems and applications, such as billing, churn, fraud detection, and other analytic applications. DXMs enable numerous formatting options for the data the system outputs, and allow users to match the data format to the requirements of the post-processing application. DXMs can use different export mechanisms to transfer the data. For example the Text File Export ISM uses batch files. The export mechanism is determined by the needs of the application to which the data is exported. The DXMs serve as an interface between Amdocs Service Mediation Manager and external applications and provide a means of exporting data from the system. In the enhancement process DXMs are like Data Processing Modules (DPMs) because they have input streams that can be targets of Enhancement Procedures and output streams that can be triggers of Enhancement Procedures. DXMs provide a direct, efficient, and reliable mechanism for data export. They enable data from multiple points on the Network-to-Business platform to be exported to destination applications, eliminating potential bottlenecks and enabling concurrent data transfer to multiple applications. DXMs have very low latency, which makes them suitable for near-real-time data transfer. DXMs support multiple input streams (like DPMs) and thus enable users to direct the data from multiple flows to a billing system (in a single file that combines the records from multiple sources).
Configuration Database
Amdocs Service Mediation Manager stores all the configuration data in an Oracle or MySQL database. Amdocs Service Mediation Manager supports the following connection modes:
For an Oracle database Supports two database connection modes. It can connect to an Oracle database instance or service. The Oracle service connects to Oracle Real Application Clusters (RAC), which enables you to deploy a single database across a cluster of servers providing high availability of the configuration database.
For a MySQL database Supports MySQL InnoDB (Transactional database) in instance mode only.
For information about the supported database servers, see the Amdocs Service Mediation Manager Installation Guide.
Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs 31
System Functions
This chapter briefly discusses the following functional components of Amdocs Service Mediation Manager. Supported Data Formats .................................................................................... 34 Data Processing in Batch-Mediation Projects..................................................... 35 Data Processing in Active-Mediation Projects .................................................... 37 Component Repository ....................................................................................... 38 Reporting ............................................................................................................ 38 Error Management.............................................................................................. 39 Auditing............................................................................................................... 39 Monitoring ........................................................................................................... 42 Statistics.............................................................................................................. 44 Patch Management............................................................................................. 46
33
Supported Data Formats

Amdocs Service Mediation Manager can transfer data in the original format (as raw files), as records, or as events. In active-mediation projects, Amdocs Service Mediation Manager transfers data in hierarchical record streams only. A record is a data structure that consists of a set of fields exposed by the stream of an IS. The record structure can be one of the following:
Flat Contains a set of fields of primitive data types such as Integer, String, Date/ Time, and Float. The structure of a flat record stream is defined by the fields that it contains. The fields that the flat record stream contains are registered in the Networkto-Business platform. You can enhance the data in flat record streams by configuring complex Field Enhancements (Field Enhancements that use DEM functions or tasks).
Hierarchical Contain a set of fields arranged in a hierarchical structure. The fields can be Primitive data types (such as Integer, String, and Float), complex data types (such as compound elements, which can be a SEQUENCE in ASN.1 terminology, and repeating elements, which can be SEQUENCE OF in ASN.1 terminology), or lists of data types. The structure of a hierarchical record and a hierarchical record stream is defined and stored in the configuration of the IS template that introduces the records to the Network-to-Business platform. The structure of the record is transparent to the Network-to-Business platform, which handles the stream as though it contains of a single field whose data type is a hierarchical record. Because of this, the structure of a hierarchical record is not displayed in the Amdocs Service Mediation Manager user interface. For example, you cannot expand an Enhancement Procedure to view the fields in its streams. Because hierarchical records are transparent to the platform, they cannot be enhanced by configuring complex Field Enhancements (Field Enhancements that use DEM functions or tasks). Hierarchical records can only be enhanced by invoking functions using customized code developed with the help of the Business Logic SDK infrastructure.
For more information about the data formats and streams the system supports, see Types of ISM Streams in the Amdocs Service Mediation Manager User Guide.
34
Chapter 4. System Functions
Data Processing in Batch-Mediation Projects

This section describes how Amdocs Service Mediation Manager collects, enhances, processes, stores, and exports data in batch-mediation projects.
Collecting Data
The Information Sources available on your network and their configuration determine what data Amdocs Service Mediation Manager collects. Depending on the network configuration, the same Information Sources may be collecting different data. The ISMs collect the data from the network elements and relay it to the Gatherers. The Central Event Manager initiates the data collecting process on startup, signaling the Gatherers to instruct the ISMs to begin collecting data from the network. The Gatherers manage the collection process of the ISMs they host: they get the relevant information about the collection scheme from the CEM, receive the data from either the ISMs they host or from other Gatherers, and then forward the data to other ISMs or to other Gatherers for enhancement, storage, or export.
Enhancing and Processing Data

Once the data enters the system, it is typically augmented by additional data from other sources available on the network through Enhancement Procedures (for flat records) or functions of the Business Logic SDK infrastructure (for hierarchical records). The data can also be subjected to additional processing, such as filtering and aggregation. Amdocs Service Mediation Manager uses Enhancement Procedures to transfer the data from one ISM to another and route the data through the system. Each Enhancement Procedure has a trigger, which supplies the source data and initiates the flow of data through the system, and a target, which is the destination of the data. Both the trigger and the target are ISM streams. When the data is in flat record format, an Enhancement Procedure can define the set of rules to obtain the data from the Data Collection Module and then add details to the record using the data supplied by one or more Data Enhancement Modules. For additional information about Enhancement Procedures, see The Flow of Data in the System and Using Field Enhancements in the Amdocs Service Mediation Manager User Guide.
35
Storing Data
The system uses Data Storage Modules (DSMs) to store the data in a database. DSMs enable the use of a distributed database system to store the usage data. Using DSMs to store the data enhances the reliability of the system by eliminating a single point of failure and the potential bottlenecks in the flow. DSMs enhance the modular architecture of the system making it flexible and scalable. The usage data can be stored in the same database as the configuration data, or in different databases. DSMs also enable system load balancing by separating the querying function from the data storage function. Amdocs Service Mediation Manager supports two database-connection modes: Oracle database instance or service. The Oracle service connects to Oracle Real Application Clusters (RAC), which enables you to deploy a single database across a cluster of servers providing high-availability of the configuration database.
Note: You must store the data in a database to enable the reporting functionality.
Exporting Data to External Systems and Applications

You can use ISMs that exports data, such as DXMs, the File Transporter ISM, or any of the formatter ISMs to export data to external systems and applications, such as balance managers. You can forward the data that the system processes in any of the following ways:
Directly from the system (by configuring an Enhancement Procedure that targets the relevant ISM) Storing the data in a database, then processing it further using the Amdocs Service Mediation Manager reporting engine to filter, aggregate, sort, format, and forward the data according to their specifications. You can configure Amdocs Service Mediation Manager to generate periodic scheduled reports at pre-set intervals automatically. Using these reports, you can channel data to external applications at regular intervals.
36
Data Processing in Active-Mediation Projects

In active-mediation projects, Amdocs Service Mediation Manager processes data in real-time. A typical active mediation process is built from network interaction, database interaction and business logic processing building blocks.
Figure 4.1 Active-Mediation Data Processing Flow
Amdocs Service Mediation Manager processes data as follows:

1. Intercepts an event, such as a service authorization request, service flow indication
request, real-time usage event, or real-time network performance event. Amdocs Service Mediation Manager, using a Data Collection Module such as the Diameter Server ISM, can receive requests that are initiated by a network system (such as a Service Control Point or an application server) and generates events internally as a result of pre-defined types of status change based on real-time monitoring of usage and network status. Service Connections are used to pass data and link the streams of two ISs in two different clusters. The flow of data in Service Connections is bi-directional. You can configure how to enhance the data in the ISMs. The trigger in a Service Connection is a Service Consumer stream, and the target is a Service Provider stream.
2. Sorts the events, using a Data Collection Module such as the Diameter Server ISM, so
that each event can be handled according to the relevant business logic. When sorting the events, Amdocs Service Mediation Manager can also load balance the data processing and prioritize the events based on the business logic application.
3. Using the Business Logic ISM, collects the data parameters that are required for the
business logic applications (business decision process) from databases, such as BSS, OSS, and Amdocs Mediation data store. Data that is needed in real-time is stored in-memory. Data that is needed in near real-time is stored in the Amdocs Mediation data store, which is populated with data collected from the relevant BSS and OSS databases. Amdocs Mediation can populate databases with information such as event and decision event.
37
4. Applies the relevant business logic to each event in order to determine the next
operational step. In the Business Logic ISM a decision tree that reflects the business logic that should be applied is defined for each event type. Events are processed in real-time based on the business decision tree, the Network systems, and BSS and OSS input data. The collected input data and the produced output information for one service decision can be used for other service decisions.
5. Creates a decision event for the next operational step, which can be applied by third
party systems. Decision event types can be a service authorization request approval or rejection or an action trigger, such as provisioning or an SMS or MMS notification. Amdocs Service Mediation Manager then forwards the decision event to systems that can enforce and implement the decision. These systems can be Service Control Points, application servers, provisioning systems, and SMSC, MMSC, or email servers. The decision event is created in the Business Logic ISM and sent back to a Data Collection Module, such as the Diameter Server ISM, that sends the respond back to the network system.
Component Repository
Amdocs Service Mediation Manager provides a workspace for managing components, such as custom data types, records, and functions in a centralized component repository referred to as repository. The repository enables creating, modifying, deleting and searching for all components, such as records and functions. Components can be part of a specific project or common to all projects. The repository also enables attaching components stored in the repository to any BL-based ISM. When a component is modified or deleted from the repository, the component is automatically updated in or deleted from the ISMs to which it is attached.
Reporting
For batch-mediation projects, Amdocs Service Mediation Manager provides easy access to the usage data in a number of output formats (HTML and CSV), and charts. It can email the report results directly, or save them as a file on the disk. Each report is based on a source query. The query defines the criteria for filtering the data in the report. The query determines how Amdocs Service Mediation Manager processes the data in the report which data table the query runs on, which fields and records are included in the results, how the data is sorted, arranged, and aggregated. The report specifies the output format and media and also whether the results include a chart. Amdocs Service Mediation Manager can run scheduled reports at regular user-defined intervals.
38
You can create queries and produce reports through the Amdocs Service Mediation Manager user interface. Multiple users can produce and view reports at the same time. Queries target the data stored by a single DSM. When you configure a query, you must select the DSM that runs that query. The Gatherer that hosts the DSM instance runs the query and then presents the UIS with the results.
Note: The data must be in flat record format and must be stored in a database for the reporting functionality of the system to be used.
Error Management
Amdocs Service Mediation Manager has streamlined error management capabilities that enable the recovery of rejected and suspended records using error management systems, such as the Amdocs Error Manager, to facilitate and automate a workflow process for detection, isolation, correction, and reprocessing of erroneous data.
Auditing
Amdocs Service Mediation Manager enables to collect and display information about the data that it collects and processes. This section contains the following topics:
Audit Service Enables to track the data flowing through Amdocs Service Mediation Manager in batch-mediation projects Project-level Audit Enables to track and view the audit data for the entire project
Audit Service
The Network-to-Business platform provides the infrastructure for ISMs that either support the Audit service or have audit capabilities, to supply audit information about the data that they process. BL-Based ISMs and ISMs that were developed using the ISM SDK can support services. If an ISM supports a service, you can enable the service when you configure the ISM. The audit information lets you track the data flowing through Amdocs Service Mediation Manager. You can retrieve audit information about data involving ISMs that support the Audit service, such as the Text File Export ISM, and for ISMs that do not support the Audit service, but have audit capabilities, such as the Interface Log File ISM. The audit information ISMs can be used to create revenue assurance reports:
For ISMs configured to work in real-time mode that use flat record streams, the revenue assurance report compares the number of input records to the number of output records. This comparison could be done for an individual ISM instance, but typically it is done for a chain of ISMs through which the data flows. For example, suppose that a DCM gets usage data from an external source generates flat records,
39
and sends the flat records to a DPM for processing. The DPM then sends the records to a DSM for storage in the database. The revenue assurance report would compare the number of records that the DCM has read from the external source to the number of records that were stored in the database. If the numbers match, there is no data loss or duplication.
For ISMs that work in file-based mode, the revenue assurance report enables you to track the progress of a job (file) along the chain of ISM by getting a snapshot of the job status at the time the report is run. The revenue assurance reports provide a convenient way to monitor the progress of jobs in the system, which can be used in either in conjunction with the Chain Monitor, or as an alternative.
Project-level Audit
Project-level audit tracks and reports the audit data for the entire project, rather than in the scope of the individual IS, and helps service providers reduce revenue leakage and billing errors through auditing of data. Project-level audit automates much of the process for logging and processing the audit information in a project and provides the following:

Collects raw audit data at critical reporting points in the flow Consolidates the raw audit data Reports the data filtered by various criteria and in a variety of output formats Provides out-of-the-box reports and audit data export Enables to define your own counters, such as money, volume, and time and map them to record fields
Project-level audit incorporates the audit counters and events of the Audit service. If your implementation uses the Audit service, you can either continue to use it or replace it with project-level audit. You can use project-level audit in both batch-mediation and active-mediation projects:
Batch-mediation projects Audit of a file in the entire flow, which provides information on the records that were added, dropped, merged, and split in that file. Active-mediation projects Audit for a time interval, which provides information for the project records in every time interval.
This section contains the following topics:

Business Logic SDK Infrastructure Project-level Audit in Batch-Mediation Projects Project-level Audit in Active-Mediation Projects Customizing Project-level Audit
40
Business Logic SDK Infrastructure The Business Logic SDK infrastructure provides the following components to support or enhance the project-level audit functionality:
Audit Mapper Maps fields in a specified BL record to user-defined audit counter types. When the information is put into the database, the values of the mapped fields are included. Audit Reporting Point Enables to manage the values for audit counter types. Each Audit Reporting Point is associated with an instance of the Audit Mapper. The project type (batch-mediation or active-mediation) affects the functionality and use of the Audit Reporting Point. In active-mediation projects the project-level audit functionality automatically includes a record counter so you do not need to associate the Audit Reporting Point with an Audit Mapper.
Project-level Audit in Batch-Mediation Projects The project-level audit functionality collects ISM-specific audit events and audit counters and user-defined Audit Counters and Audit Events. One Audit Reporting Point must be configured for every location in which you want to collect audit information. For example, if an IS template has an input stream and an output stream, you must create two instances of the Audit Reporting Point component. If the ISM does not automatically configure an Audit Reporting Point, you must configure one. Use the following ISMs to enable project-level audit in batch-mediation projects:
Oracle Exporter ISM Collects the project-level audit information and puts the data into a specified database table. Audit Consolidator Logic ISM (Optional) Processes the data and to checks whether usage data has been lost. Non-BL-based ISMs, such as the Text File Export ISM (Optional) Transparently interface with the project-level audit infrastructure.
Project-level Audit in Active-Mediation Projects You can enable and disable the collection of audit information, and specify Audit Mappers in the configuration of the following components:
Service Provider Stream Receives and sends hierarchical records over a Service Connection from a Service Consumer Stream. Works in partitioned clusters only. Service Consumer Stream Receives and sends hierarchical records over a Service Connection to a Service Provider Stream. Hierarchical Enhancement Function Creates tasks that the IS exposes that enable to perform synchronous tasks (such as updating data in the database) and asynchronous tasks (such as database queries).
The project-level audit functionality automatically includes a record counter, so you do not need to specify an Audit Mapper if you require the number of records that the component processes only.
Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs 41
Use the Active Mediation Audit Logging ISM to enable project-level audit in activemediation projects. The Active Mediation Audit Logging ISM collects the project-level audit information and puts the data into a specified database table. Customizing Project-level Audit You can customize your implementation to:
Use user-defined counter types (for example, to keep track of money and volume, and other counters Reduce overhead by using a record that contains a superset of all unique audit event fields Implement project-level audit in Aggregation mode to reduce audit table size and improve performance by reducing the number of insertions into the database (in batch-mediation projects only)
Monitoring
Amdocs Service Mediation Manager provides a variety of applications and ways to monitor its operation:
Event Infrastructure and Log Files Enables to view log messages that the system generates Amdocs Service Mediation Manager Monitoring Interface Provides information about objects that are exposed in the MIB Monitoring Runtime Operation of Projects Enables to monitor the runtime operation and status of core system components Chain Monitor Enables to monitor the status of each file in the system when it passes from one ISM to another in batch-mediation projects
Event Infrastructure and Log Files

All core system components (the CEM, the UIS, the Gatherers) and their associated log modules generate log messages. The ISMs also generate log messages, and write them to the log file of the Gatherer. The event infrastructure of the system provides a unified mechanism for reporting log messages in the system and its components. It enables you to view the log messages using:

The log files of the system components The System Alerts Monitor (a monitoring window in the Amdocs Service Mediation Manager user interface that displays messages that are written to the log files of the system components) The Component Monitor (a monitoring window in the Amdocs Service Mediation Manager user interface that displays the messages that are written to the log files of a specific component)
42
The event infrastructure of the system also enables users with the required permissions to:
Specify thresholds for critical conditions in the operation of the system components based on the system statistics (statistics that the system components provide about their operation, such as low free disk space, high memory usage, and so on), and get notifications in the form of log messages when the value of the system crosses these thresholds. For more information, see Getting Information About System Statistics in the Amdocs Service Mediation Manager Operator Guide. Define SNMP traps based on any of the log messages, including the messages generated for the system statistics, using the SNMP Trap Exporter. For more information, see Configuring SNMP Traps in the Amdocs Service Mediation Manager Operator Guide.
For more information about using the event infrastructure, see Understanding the Event Infrastructure in the Amdocs Service Mediation Manager Operator Guide.
Amdocs Service Mediation Manager Monitoring Interface

The Amdocs Service Mediation Manager Monitoring Interface (XMI) provides information about the objects exposed in the Network-to-Business platform (N2B) Management Information Base (MIB) extension through a MIB browser or a Network Management Station (NMS). The XMI allows you to identify link disconnections and potential bottlenecks or problems in the flow, to balance system load, to monitor memory usage, and to perform other tasks. For more information about the Network-to-Business platform MIB, see the Amdocs Service Mediation Manager Operator Guide.
Monitoring Runtime Operation of Projects

You can monitor the runtime operation and status of core system components (the CEM, UIS and Gatherers) in the Runtime Data Flow view and tree. The following real-time information is presented in the Runtime Data Flow view:
ToolTip with information on the object and its properties, such as name, identifier, state, and versions Configuration version of the core system component Core system component status (a monitoring bar provides real-time status of each core system component, such as whether the Gatherer is stopped or initializing) Gatherer status Gatherer configuration version Cluster organization, such as partitions and Gatherers in a cluster (in active-mediation projects)
You can also configure the core system components to record every change in their state to a data file.
43
Chain Monitor
In batch-mediation projects you can monitor each file as it is inserted in the system using the Chain Monitor, which is a window in the Amdocs Service Mediation Manager user interface that shows the status of each file in the system as it is being passed from one ISM to another. The Chain Monitor is relevant for file-based mediation, and is available when the ISMs that process a file are configured to work in file-based mode. For more information about using the Chain Monitor, see Using the Chain Monitor in the Amdocs Service Mediation Manager Operator Guide.
Statistics
Amdocs Service Mediation Manager provides status and statistics as follows:
Statistics Service Enables an ISMs in batch-mediation projects to export information about its operation, such as the number of records or files it has processed, the number of records that have not been transferred Statistics in Batch-Mediation Projects Provides status and statistics for batch-mediation projects Statistics in Active-Mediation Projects Provides real-time statistics for active-mediation projects
Statistics Service
The Statistics service enables an ISM to export information about its operation, such as the number of records or files it has processed, the number of records that have not been transferred. BL-Based ISMs and ISMs that were developed using the ISM SDK can support services. If an ISM supports a service, you can enable the service when you configure the ISM. Each data unit the ISM exports is a statistics field that has a name and a type. The statistics fields are arranged in statistics groups. The set of fields in each group is called a statistics record. When the Statistics service is enabled, the service automatically reports statistics for the interfaces of the ISM. You can enable the Statistics service when you configure the ISM and then select whether the ISM exports the statistics to a file or to the Network-to-Business platform MIB. You can also select the statistics fields that the ISM exports, and choose the format of the export file. For more information about the specific statistic information an ISM exports and how to configure the service, see the documentation of the ISM.
44
Statistics in Batch-Mediation Projects

The core platform components (the CEM, UIS, and Gatherers) collect information about their operation, and the operation of the system called system statistics. The currently available system statistics are: CPU utilization, memory usage, available disk space, and EP instance rate (during the last minute and during the last hour). Authorized users can set thresholds for these statistics in order to get notifications when the value of the statistic reaches a critical level, or goes back to the normal level after reaching a critical level.
Statistics in Active-Mediation Projects

You can configure the system to output latency and throughput statistics for active-mediation projects. The system can provide reports and graphs for:

Latency histogram statistics Throughput statistics Latency statistics
The system can output these statistics in a CSV file, a database table, and in the Amdocs Service Mediation Manager main screen. In addition to the latency and throughput statistics in active-mediation projects, the system also provides the statistics that are available in batch mediation projects:
System statistics, such as CPU utilization and memory usage (for more information, see Statistics in Batch-Mediation Projects) Statistics that the ISs provide when the Statistics Service is enabled. These statistics are in the format selected in the configuration of the IS (MIB, file or both MIB and file). For more information about the Statistics Service, see the documentation of the specific ISM.
You must configure and enable statistics, in the components and in the Gatherer that hosts the IS instance of which the component is a part, to collect statistics information.
45
Patch Management
The package management mechanism enables users belonging to the Administrators group to use the user interface or command line interface to:

Install one or more individual packages or groups of packages Monitor installed packages throughout the system Uninstall one or more individual packages or groups of packages
A package consists of one or more executable codes that were changed since the last update of a module. It may be a patch, patch bundle, upgrade, or service pack.
Note: Currently, packages consist of core and ISM patches only.
46

ASMM 8.2 - Overview

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ASMM 8.2 - Overview

Hochgeladen von

Copyright:

Verfügbare Formate

AMDOCS MEDIATION RELEASE 8.

Amdocs Service Mediation Manager 8.0

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Amdocs Service Mediation Manager 8.0 Overview

Patch Management ...........................................................................................................................46

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Amdocs Service Mediation Manager 8.0 Overview

Purpose and Scope

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Courier New Bold

Type the following:

angle brackets square brackets curly brackets

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Amdocs Service Mediation Manager 8.0 Overview

Terms and Definitions

AMC Amdocs Service Mediation Manager Monitor BL SDK

Central Event Manager Component Repository

Data Collection Module

Data Enhancement Module

Data Export Module

Data Processing Module Data Storage Module

DCM DEM DEM function

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

DPM DSM DXM DC DC group

job JRE node

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Amdocs Service Mediation Manager 8.0 Overview

UIS User Interface Server

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Amdocs Service Mediation Manager 8.0 Overview

Highlights and Benefits

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Chapter 2. System Features

Convergent Mediation Platform

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Amdocs Service Mediation Manager 8.0 Overview

Distributed Architecture and Carrier-Class Scalability

Modular, Adaptable, and Easily Configurable

Parser Gatherer Validation module DeDuplicator Gatherer Aggregator Formatter Distributor

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Chapter 2. System Features

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Amdocs Service Mediation Manager 8.0 Overview

Next-Generation, Customer-Level Service Assurance

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Chapter 2. System Features

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Amdocs Service Mediation Manager 8.0 Overview

Chapter 2. System Features

System Repository for Managing Components

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Amdocs Service Mediation Manager 8.0 Overview

Advanced Monitoring and Reporting Capabilities

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Chapter 2. System Features

You can use the following methods to view auditing information:

Information Security Level 1 Confidential Proprietary and Confidential Information of Amdocs

Amdocs Service Mediation Manager 8.0 Overview

Integration with Operational

Session Timeout Support for a secure communication channel

Ability to Select the Security Mechanism

Chapter 2. System Features