MDS/SAS and MDS/AMD
The Mediation Device Solutions are integrated applications for Network Operators to provide a cost-effective, seamless flow of information between The Telephone Network and Customer Care and Billing Systems consisting of two different application sets: Service Provisioning (MDS/SAS) and Call Collection, Processing and Data Warehouse (MDS/AMD).
English
Click on a technology to view similar products within this category.
Pricing
- Unspecified -
info@comptel.com
Additional Product Information
Introduction;Network Operators all over the world are looking for new ways to;compete in the deregulated, open telecommunications market.;New technology, new approaches to customer service, new products are;constantly being tested and deployed. The requirement for truly;integrated information has become a key factor in the search for;competitive advantage. With an integrated view of his corporate data;and operations, the network operator can ensure the quality of;service provisioning and the integrity of the revenue stream.;The seamless two-way flow of information between the business-oriented;downstream systems and the telephony network elements is a vital;prerequisite to effective management of the business processes.;The answer to these requirements is the Mediation Device. It provides;the link between the telephone network and the downstream applications;customer care and billing systems, fraud management systems, data ware;housing, interconnect administration etc.). It shields these;applications from the constant changes in the network and provides an;easy-to-manage, single point of interface to the network.;This interface is typically defined with two important functions and;streams of data: call collection and service provisioning.;Comptel is an expert in the field of Mediation Devices.;Our product family is called Mediation Device Solutions (MDS).;This is an integrated set of products that can be configured for;various different business environments. An advanced, component-based;architecture enables the operator to upgrade the system easily;whenever new elements or more transactions are introduced in the;network. An open UNIX platform and interfaces ensure that the MDS;functionality is readily available to any client system. The system;is easily adapted to accommodate changes within the operator's;business processes.;The main MDS applications are:;MDS/AMD (Accounting Mediation Device);Automatic collection, validation, conversion and pre-rating of the;Call Data Records (CDRs). Automatic delivery of CDRs to multiple;downstream systems in different formats or storage within a Call;Database.;MDS/SAS (Subscriber Administration System);On-line provisioning of customer services in the network elements,;based on service requests received from the customer care or other;downstream systems.;MDS/AMD: Call Data Management;The MDS/AMD enables reliable and powerful management of the call data;streams for itemised billing, hot billing, fraud management, revenue;analysis etc. The system can be configured for both real-time and;"polling" environments, where CDRs are collected, converted and rated;either immediately ("hot billing") or as soon as possible;("warm billing"). Intelligent options for filtering, matching,;converting and distributing the records are provided, together with;detailed auditing and error management functions.;Multiple network elements from any variety of different vendors can;be connected to the system. Intelligent "methods" govern the;processes and provide for a controlled and resilient execution;environment. As CDR volumes grow, new methods and new hardware can be;added to the system to accommodate the higher throughput requirements.;Centralised logging keeps statistical and revenue assurance;information on all CDR batches or transactions flowing through the;system, thus creating a highly auditable environment for handling the;revenue streams.;MDS/AMD consists of various modules, most of which are optional and;user configurable. This enables the system to be adapted to a wide;range of operational environments.;MDS/FTM (File Transfer Manager) is the manager of the overall CDR;processing. FTM is built around a concept of "methods". The methods;can consist of various collecting, filtering, conversion and rating;"steps", depending on the operator's requirements.;The interrelationship between the steps can be defined with a;selection of different logical operators. The processed CDRs can be;distributed to multiple billing systems and/or to an optional Call;Database. FTM has its own scheduler, which enables the automated;activation of methods. FTM can also manage real-time streams and;handle the buffering between the network elements and the billing;systems. ;MDS/ARC (Accounting Record Collector) is a common name for a set of;interfaces between the MDS and the network elements. The purpose of;these modules is to control the information exchange with the network;element. Typically, this means a file transfer operation using FTAM,;FTP etc. but it can also be a complex procedure including handshaking,;exchange of control information, real-time flow of CDR data and;proprietary protocols for transferring information.;MDS/ARM (Accounting Record Modifier) takes care of the CDR conversion;and validation requirements. It consists of three different;submodules: File Reader (FR), Conversion and Validation (CV) and File;Writer (FW). FR receives the CDR data and reformats it to an internal;format based on a set of layout definitions. The record is then handed;over to the CV module, which performs the required conversions and;validations on the call data record based on external rules. This;mechanism ensures very easy and flexible maintenance of the system.;Finally, the FW writes the resulting output record to one or more;output streams. The output formats are specified in an external output;description file. There can be several output streams and the data;format in each file may be different. The data can thus be delivered;to several destinations and, for each destination, it can be sorted;according to given criteria. The FW can also support hot billing;streams, where output records are sent as packets to the next step in;the method.;MDS/ARM can also perform operations other than conversion and;validation to the call records. For instance, different parts of the;call can be combined into a single call record in case of long calls;or when the logical call comprises of multiple physical call records. MDS/ARM can also trap multiple instances of the same call thus preventing possible double-billing.;MDS/ARP (Accounting Record Pre-rating) pre-rates the calls using;various rating parameters and attaches pre-rating information to the;call records. The prices are standard prices that can be further;processed in other applications to allow e.g. volume or other customer;specific discounts. MDS/ARP supports three different price types:;price per minute, price per call and price per impulse (a unit;generated by a switch). The use of combinations of different price;types is also possible.;MDS/ARS (Accounting Record Storage) takes the call records and stores;them in a call database. While storing the record, the module can also;perform duplicate checking and other customer specified operations.;MDS has its own, proprietary, high speed database but can also use;other standard relational databases.;MDS/ARDS (Accounting Record Delivery) delivers the call data records;to a single or to multiple client systems. The format can be different;for each system. Several interfaces already exist for the leading;billing systems.;MDS/FTM has also an enhanced Audit Trail option. This module is a set;of rules and reports for performing detailed revenue assurance;monitoring. The log information can be used also for other purposes,;as the data is stored in a standard Oracle database.;Various other interfaces can be used for configuring the system into;a global IS architecture. These include a standard SNMP management;interface and an interface for starting collection methods from some;external system.;MDS/AMD is a highly adaptive system with a large range of;functionality. The system can be flexibly changed and maintained to;cope with new technical and business requirements. For more;information on the MDS/AMD, please refer to the document "MDS/AMD;Product Description". ;MDS/SAS: Service Provisioning;MDS/SAS is used to automate the provisioning and activating of;telecommunication services so that no manual intervention is required;after the service order has been recorded in the Customer Care system.;The user does not need to have a profound knowledge of the;telecommunications network or the individual network elements. ;The keywords for MDS/SAS are openness and flexibility. MDS/SAS;resolves technical incompatibility issues, creates a standard;provisioning interface in a multi-vendor network and makes it easier;to commercially launch new network services. Due to the intelligent,;object-based "Service Package" concept, many of the complicated;interrelations between the services and network elements can be;hidden from the Customer Care system. Foe example, a typical scenario;could be a provisioning of a subscriber with a standard set of;services together with voice mail and short message services.;This may require actions in HLR, VMS and SMSC network elements.;Where there are multiple HLR's in the network, a MSISDN or IMSI;database may also need to be updated. MDS/SAS can break the single;service request into several tasks, each for a single network element,;perform the activations in a predefined sequence and take care of;different error situations in the activation process. Ultimately,;a status information for the 'entire' request is sent back to the;client system. All this happens automatically and instantaneously;after the customer order has been confirmed.;Thanks to its open, well-documented interfaces, MDS/SAS can easily;be introduced into the Information System architecture of the telecom;operator. The basic flow of information is based on Service Requests,;which MDS/SAS receives on-line from the Customer Care system through;an API connection (see picture 3). These requests contain all the;customer and service information that is necessary for provisioning;and/or activating the services. The "service" can be a single atomic;item or a high-level object with a number of detailed sub-services and;parameters. The Service Resolution Manager (SRM) identifies individual;services from the request, creates a separate task for each service;and forwards the tasks to the corresponding network elements, while;preserving the context and relationships between the various;sub-services. The resolution of the target network element is based on;various parameters stored in the Network Model Database.;Individual tasks will pass through various states before they are;considered to be "completed". These state changes are logged in the;Task Log Database, which the user can monitor through a graphical;user interface. The task is stored in a dynamically controlled queue,;which uses a prioritised, FIFO basis. When the task is ready for;processing, it will go through a multilayered Transaction Manager,;which translates the task's request parameters into commands;understood by the network element. These commands are then sent one;by one to the network element and executed. Responses from the;network element are analysed and delivered back to the transaction;manager. In the situation where an error is encountered, the system;tries to recover from the situation or, if no remedy is available,;the processing of the request is terminated. The Task State is;updated in the Task Log Database to reflect the status of the request.;MDS/SAS also guarantees that all the actions are performed in the;right order, as defined in the request parameters. This can ensure,;for instance, that the Voice Mail Service will not be provisioned;before the basic telephony service.;MDS/SAS comprises a number of individual system components, which are;linked via the CORBA architecture. This technology enables the design;of powerful distribution, security and availability strategies and;supports a highly scaleable expansion plan.;MDS/SAS has a large repertoire of interfaces with various network;elements in both wireline and wireless (digital and analogue);telecommunications networks. This covers not only the major switch;vendors e.g. Nokia, Ericsson, Siemens, Nortel and Lucent but also a;wide range of different value-added services such as Voice Mail,;Short Message, Intelligent Network, Prepaid systems etc.;For more information on the MDS/SAS, please refer to the document;"MDS/SAS Product Description".;Benefits;With experience in the field of mediation spanning over eleven years,;Comptel invested heavily in the development of the MDS products.;These applications are as suitable for a long established;wireline/wireless operator as they are for a new, burgeoning entrant;to the telecom market. The products have been proven in over 50;different networks in four different continents. With this established;position in all the major markets, Comptel and its partners can;provide the network operator with the best solutions for establishing;a competitive operation.;Comptel's 'Mediation Device Solutions' brings the following,;immediate benefits:;§ Instant Service-Provisioning results in higher customer satisfaction ;through quicker service at the point of sale.;§ Flexible Service-Packaging enables the combining of different;services together in a single service request. Even multiple networks;can be supported simultaneously; a must in a convergent telephony;operation.;§ Fast and reliable call record collection enhances the revenue;assurance of an operator and is a key factor when implementing;different "hot billing" or "warm billing" applications.;§ Single and uniform point of access to the network lowers the overall;cost of network management. This eliminates the need for multiple and;often rather expensive Operations Support Systems from several;vendors. The differences in the network are effectively hidden from;the customer care and billing applications.;§ Reduced manual effort is an obvious benefit from the high automation;level of MDS. The engineers can concentrate on tasks that are more;challenging and the subscriber service representatives do not have to;learn exotic tasks or command languages. This also has a tremendous;impact on the reliability and security of the operations.;§ Good architecture for growth, providing a path for larger;transaction volumes (both call records and service provisioning;transactions) just by adding new hosts in the overall MDS system.;Thanks to its CORBA integration, the system grows in line with you're;the operator's success. Adding support for new network elements or;new releases of an existing element is also easy through the flexible;Network Model Database. ;References;Current Mediation Device Solution references are listed below.;The relevant MDS applications used by each reference is indicated.;The type of network and the switch vendors are also listed.;International:;AERIAL, Chicago, IL, USA;Application: MDS/AMD, MDS/SAS;Network: PCS1900;Switch: Nokia;ADVANCED INFO SYSTEMS (AIS), Thailand;Application: MDS/SAS;Network: GSM and NMT;Switch: Nokia, Ericsson and Siemens;CONNECT AUSTRIA, Austria;Application: MDS/AMD, MDS/SAS;Network: GSM, Wireline;Switch: Nokia;CTM, Macao;Application: MDS/AMD, MDS/SAS;Network: GSM, TACS;Switch: Ericsson;diAx, Switzerland;Application: MDS/AMD, MDS/SAS;Network: Wireline;Switch: Nortel;DIGI TELECOMMUNICATIONS, Malaysia;Application: MDS/AMD, MDS/SAS;Network: GSM, Wireline;Switch: Ericsson, Siemens;EIRCELL, Ireland;Application: MDS/AMD, MDS/SAS;Network: GSM, TACS;Switch: Ericsson;ENERTEl, Netherlands;Application: MDS/AMD, MDS/SAS;Network: Wireline;Switch: Siemens;EUROTEL, Slovakia;Application: MDS/SAS;Network: GSM;Switch: Ericsson;GLOBALSTAR CANADA SATELITE CO, Canada;Application: MDS/SAS, MDS/AMD;Network: Satelite;Switch: Qualcomm, Alcatel;HUTCHISON, Australia;Application: MDS/AMD, MDS/SAS;Network: CDMA (wireless local loop);Switch: Samsung CDMA;KPN TELECOM, Netherlands;Application: MDS/AMD, MDS/ARMS for fraud detection;Network: GSM, NMT, Ermes;Switch: Ericsson;MOBILE ONE, Singapore;Application: MDS/AMD, MDS/SAS;Network: GSM, CDMA, Paging;Switch: Nokia, Motorola, Alcatel;NEW WORLD, Hong Kong;Application: MDS/AMD, MDS/SAS;Network: PCS1800, GSP;Switch: Nokia;OMNITEL PRONTO ITALIA, Italy;Applications: MDS/AMD, MDS/SAS;Network: GSM;Switch: Nokia;P&T LUXEMBOURG;Application: MDS/AMD, MDS/SAS ;Network: Wireline and GSM;Switch: Siemens;PACIFIC BELL MOBILE SERVICES, USA;Application: MDS/SAS;Network GSM;Switch: Ericsson ;PMCL, Pakistan;Application: MDS/AMD, MDS/SAS;Network: GSM;Switch: Siemens;PT TELKOMSEL, Indonesia;Application: MDS/AMD, MDS/SAS;Network: GSM;Switch: Siemens;SMARTONE Ltd, Hong Kong;Application: MDS/AMD, MDS/SAS;Network: GSM, PCS, ISP;Switch: Ericsson;STARHUB, Singapore;Application: MDS/AMD, MDS/SAS;Network: GSM 1800, Wireline, Data (ATM+Frame relay);Switch: Nokia, Ascend;SUNDAY, Hong Kong;Application: MDS/SAS, MDS/AMD;Network: GSM;Switch: Nortel;TATA TELECOMMUNICATIOSN, India;Application: MDS/SAS, MDS/AMD;Network: Wireline, TACS;Switch: Lucent;TELIA MOBILE, Sweden;Application: MDS/AMD;Network: GSM, NMT;Switch: Ericsson;TELSIM, Turkey;Application: MDS/SAS, MDS/AMD;Network: GSM;Switch: Nokia;TURKCELL, Turkey;Application: MDS/AMD;Network: GSM;Switch: Ericsson;VIAG, Germany;Application: MDS/SAS, MDS/AMD;Network: Wireline, GSM;Switch: Nortel, Siemens;VODAFONE Pty Ltd., Australia;Application: MDS/AMD;Network: GSM;Switch: Ericsson;Finland:;Radiolinja Oy ;Application: MDS/AMD, MDS/SAS;Network: GSM;Switch: Nokia, Siemens;Helsingin Puhelin Oyj;Application: MDS/AMD, MDS/ARMS;Network: Wireline;Switch: Nokia, Ericsson, Siemens;Päijät-Hämeen Puhelinyhdistys;Application: MDS/AMD;Network: Wireline;Switch: Ericsson, Siemens;Mikkelin Puhelinyhdistys;Application: MDS/AMD;Network: Wireline;Switch: Ericsson;Keski-Suomen Puhelin Oy;Application: MDS/AMD;Network: Wireline;Switch: Ericsson;Kaukoverkko Ysi Oy;Application: MDS/AMD;Network: Wireline (long distance);Finnet International;Application: MDS/ARMS including interaccount clearing;Network: Wireline (international);Joensuun Puhelin Oy;Application: MDS/AMD;Network: Wireline;Switch: Siemens;Turun Puhelin;Application: MDS/AMD;Network: Wireline;Switch: Ericsson, Siemens ;Lännen Puhelin Oy;Application: MDS/AMD;Network: Wireline;Switch: Ericsson, Nokia;FINNETCom Oy;Application: MDS/ARMS;Network: Wireline (Large customer accounts);Kuopion Puhelin Oy;Application: MDS/AMD;Network: Wireline, DCS (GSM1800);Switch: Ericsson;Oulun Puhelin Oy;Application: MDS/AMD;Network: DCS (GSM1800);Switch: Nokia;Summary of Network Element Interfaces;The following list indicates the currently supported interfaces with;network elements. This list is constantly evolving and new items are;developed on a monthly basis.;MDS/SAS;· HLR;J Ericsson AXE, Nokia DX, Nortel DMS, Siemens EWSD, Lucent 5ESS;· PSTN;J Ericsson AXE, GPT System X, Nokia DX, Siemens EWSD, Lucent 5ESS,;Nortel DMS;· VMS;J Comverse, Octel, Tecnomen;· NMT;J Ericsson AXE, Nokia DX;· SMS;J Aldiscon, Nokia;· AUC;J Ericsson AXE, Nokia DX, Sema, Siemens EWSD;· EIR;J Sema, Lucent 5ESS;· TACS;J Ericsson AXE;· SIS;J CMG;· OTA;J Gemplus, Sema;· DP;J Ericsson AXE, Lecco;· IN;J Aethos, Ericsson AXE, Nokia DX, Siemens EWSD;MDS/AMD;· Fixed line;J Ericsson AXE, Nokia DX, Siemens EWSD, GPT System X, Lucent 5ESS,;Nortel DMS;· VMS;J Comverse, Octel, Tecnomen;· NMT;J Ericsson AXE, Nokia DX;· SMS;J Aldiscon, Nokia;· TACS;J AXE;· IN;J Aethos, AXE, DX200, Siemens EWSD;· MSC;J Ericsson AXE, Nokia DX, Nortel DMS, Siemens EWSD, Lucent 5ESS