FORIS OSS
The system FORIS is a complex OSS, or Operation Support System, which provides support for the operations of a modern telecommunication services operator (provider). The system solves problems such as network inventory and management, collection of service usage data, data storage and analysis, pre-billing tasks, creation of a convergent bill for all services, management of the complex relationship between customers/subscribers and partner operators. It consists of the following subsystems:; Network resources inventory system TelRES; Mediation Device System TelMD; Storage system for service usage data (Usage Metering Records) - UMR Storage; Data rating (billing pre-processing) system TelCharge; Fraud Detection - TelFD; Billing and inter-billing system TelBill; Customer care system (Customer Relationship Management System CRM)
Afrikaans,
Arabic,
Bulgarian,
Byelorussian,
Croatian,
Czech,
Danish,
English,
French,
Italian,
Macedonian,
Polish,
Portuguese,
Romanian ,
Russian,
Serbian,
Slovak,
Spanish,
Turkish
Supported Technologies
HP/UX,
Linux,
Solaris/Sun OS,
Windows XP/2000/NT
Software, Web-Based (Browser)
Click on a technology to view similar products within this category.
Pricing
Users (# of seats)
depends
kuren.shakhnazarov@strom.cz
420606742243
installations: Germany, Russia, Czech Republic, USA, Bosnia, Uzbekistan
Additional Product Information
1 Introduction
This document describes the FORIS operations support system (OSS), which is used for telecommunication operator support.
The description of the system and its subsystems is given in Chapter 2.
The relations and correlations between the eTOM (extended Telecom Operations Map) concept and the FORIS system concept are described in Chapter 3.
The role and importance of technologies used in FORIS system development are described in Chapter 4.
Some of the important terms used in the text are briefly explained here; for more detail see the document under the title Terms.
The illustrations of particular system parts (i.e. screenshots) reflect the actual installations of those parts, which is why they appear in different languages.
2 FORIS Operations Support System (OSS)
The system FORIS is a complex OSS, or Operation Support System, which provides support for the operations of a modern telecommunication services operator (provider). The system solves problems such as network inventory and management, collection of service usage data, data storage and analysis, pre-billing tasks, creation of a convergent bill for all services, management of the complex relationship between customers/subscribers and partner operators. It consists of the following subsystems:
Network resources inventory system TelRES
Mediation Device System TelMD
Storage system for service usage data (Usage Metering Records) - UMR Storage
Data rating (billing pre-processing) system TelCharge
Fraud Detection - TelFD
Billing and inter-billing system TelBill
Customer care system (Customer Relationship Management System CRM)
The solution supports fixed, mobile and data networks.
**Figure 1. FORIS structure
FORIS OSS, together with its subsystems, provides the following functions:
Access to service usage data generated from different network elements, such as telephone exchanges, network access servers, etc.
Collection of completed service data from different network elements (telephone exchanges) through the use of different interfaces and protocols for communication
Automatic data collection without the need for personal supervision
Temporary data storage and usage of queuing for secure transfer
Data validation and quality control
Equipment testing
Equipment configuration during service provisioning process
A different process of data verification
The conversion of completed service dates from their original format into the UMR (UMR-Usage Metering Record) structure and their storage at the central location.
Data transfer to the central location based on RDBMS UMR storage technology
A variety of analyses of stored UMR data,
Pre-billing processing of used service data (UMR) for price calculation
Administration of charge data (charge book)
Support for different price categories
A simple implementation of the new charge algorithm without changes to the charge module
Charge data storage and analysis,
Implementation of different billing cycles creation of bills for customers/subscribers
Definition and implementation of a price discount depending on services and subscriber level
Definition and implementation of tax addition to completed services
Printing of detailed or less detailed bills (invoices)
Debt processing
Creation of different reports (statistics, subscriber profiles, invoices)
The possibility of connection to financial information systems (General Ledger)
Convergent billing solutions based on the ability to bill different services (water, electricity, etc.) on one and same bill of telecommunication services
Compilation of integral bills for subscribers
Support for Inter-billing solution, i.e. creation of reports of split income between the operators (Interconnect Report)
Support for content billing (billing of services made in GPRS, cable TV and data networks)
Support for near real-time billing that charges for services done in the near past
Bills e-presentation and payment (EBPP)
Centralization and update of technological process administration
Fully secured data access
Alarm activation in the case of a critical error generated during data processing
Support for number portability whenever a subscriber changes the operator yet wishes to retain the number
Re-numeration of some or all subscribers,
Support of billing for of streaming media services, such as streaming video, videoconferencing, streaming audio, and data conferencing
Support of the complete CRM cycle, from the customer request to its fulfillment along with service provisioning trough mediation device
Easy design of processes and customer messages with the integrated workflow.
The following figure presents the general data flow: making bills on the basis of network element generated data, dispatching bills to customers, payment processing, handling customer requests and inter-billing. Every subsystem of FORIS OSS is shown likewise.
Figure 2. General data stream in FORIS OSS
2.1 The Mediation Device System (TelMD)
One of the goals in working with a telecommunication network is the ability to communicate with network elements and to control them at the same time. At present, there is a new challenge in telecommunication networks, with Network Elements (NE) based on different technologies made by different manufacturers and with consequently different means of communication and control. Examples of such network elements are telephone exchanges, routers, and so forth. STROM Telecoms Mediation Device TelMD is a set of program components providing communication with, as well as transfer and information/data translation from and to a NE. A particular TelMD is designed for a particular type of NE.
2.1.1 Goals
Mediation Device enables the collection of traffic and other type of data from NEs. It offers a fairly uniform way of presenting the information (UMR) obtained from different NEs, thus making it easier to comprehend and manage.
Furthermore, it offers an easy way of sending control commands (command sequences) to exchanges that support such functionality. It is a base for complete and successful monitoring, management, collection and processing of data generated from network elements. Mediation Device TelMD is one of the key elements of success of the TelCharge system (billing pre-processing/rating system).
2.1.2 Functionality
The system offers the following functionality:
Collection of used service data and communication with network elements
Reformatting/conversion of the collected data
Data validation
Service provisioning
Equipment testing
Detection and processing of alarm event
Process administration
2.1.2.1 Used service data collection and communication with network elements
The system establishes a communication channel with a network element, collects used service data and checks it for completeness and correctness. The data may originate from the following switches:
**Telephone exchanges from major vendors:AXE 10, EWSD, S12, 5ESS, SDX 100, ET 200, DKTS, SI 2000/224,
Routers and other Internet and multimedia NE for CISCO, NORTEL etc...
Others.
The means of communication between a network element and the mediation device may be one of the following:
Synchronous communication between two computers
Magnetic tape emulator
Switch-specific communication ports
LAN connection
The protocols that are used for communication include the following:
FTAM
FTNEA
MTP
FTP
TCAP based protocols (INAP, CAMEL)
RADUIS
TACAS
The following figure shows the structure of the data collection system.
Figure 3. Data collection scheme
2.1.2.2 Data Conversion
The system converts (reformats) collected data from its various native formats to a single uniform format, the so-called UMR, which enables simpler handling and more convenient further processing. This format is also an internal format for service usage data in the billing pre-processing system TelCharge.
During the conversion, the system performs syntax checks. Possible errors are reported along with the most probable error cause.
2.1.2.3 Data Validation
The system performs several validation (checking) procedures on the collected data, according to the following criteria:
The length of calling party numbers must conform to a certain value (it must take values from a pre-defined range)
The length of called party numbers must conform to a pre-defined value
A calls end time cannot precede its start time
There cannot be more than a single phone call from a particular phone number at the same time
The non-existence of data for a certain time period or part of NE(s)
These criteria may vary depending on the actual service usage data that is being collected. The list of validation procedures may be expanded or reduced depending on one's needs. Data collection, conversion and validation functionalities conform to TMN Functional Areas Of Management Configuration Management (see Figure 3 later in the text).
2.1.2.4 Service Provisioning
Alongside data collection, service provisioning is a very important function of TelMD. TelMD receives requests for service provision (customer activation/deactivation, configuration of customer line according to SLA) from the customer care or billing system, translates it into format that can be recognized by the network element (switch), issues a command to the switch and waits for an answer. Then, it sends the answer to the sub-system that issued the request. This functionality conforms to TMN Functional Areas Of Management Configuration Management (see Figure 3 later in the text).
2.1.2.5 Equipment Testing
Equipment testing is another function of TelMD. As is the case with the service provisioning function, TelMD receives requests for equipment testing, translates them into the format that can be recognized by the NE, issues a command to the NE and waits for an answer. The answer is then translated into the universal format and sent to the sub-system that issued the request.
Equipment testing can be run from any point in a network. Test results are collected in the administration center and analyzed. The appropriate reports are generated and sent to servicing personnel automatically.
A good example of equipment testing is measuring a subscribers line parameters, which makes the solution appropriate for the implementation of the trouble ticketing application.
The actual measured parameters depend on a particular NE. This functionality conforms to TMN Functional Areas Of Management Performance Management (see Figure 4 later in the text).
2.1.2.6 Alarm Events Detection and Processing
The system provides procedures for the detection and processing of alarm events (activation, deactivation, analyses). Alarm messages generated in the system are collected, reviewed and stored in the administrative center. The functionality conforms to TMN Functional Areas Of Management Fault Management (see Figure 4 later in the text).
2.1.2.7 Process Administration
The system provides means of system (technological) process monitoring and administration. The means are realized using a graphical user interface.
The administration enables:
Control of system metadata
Control of data transformation processes
Archiving of data
System disaster recovery
System events logging
Distribution of new versions of system applications
The processes administration functionality conforms with the TMN standards and covers the following functional areas of management:
Configuration management
Fault management
Simple security management
The TMN functional areas of management are presented in the scheme below.
**Figure 4. Functional areas of management
The following figures show some examples of process administration.
Figure 5. Administration console
Figure 6. System events journal
2.2 Service Usage Data Storage System UMR Storage
The handling of service usage data generated by various network elements grows more complex as more telecommunication services are being introduced. The large volume of data that a telecommunication operator must handle demands a system that provides reliable and effective data processing, storage and archiving. The system must be able to assure simple and organized data access in order to enable various analyses, export and import to and from other systems or organizations (roaming partners, billing systems). It must also be able to restrict data access and grow with the network operators business.
2.2.1 Functionality
STROM Telecoms service usage data storage solution UMR Storage uses RDBMS as the base for data storage. The RDBMS of choice is ORACLE 9 on the Windows 2000 platform. Other platforms are also available (SUN SPARC, RDBMS MS SQL Server 2000 on Windows 2000).
The system provides the following functionality:
Import and storage of service usage data
Data export
Data archiving
Control of restricted data access
Data analyses
2.2.1.1 Data Import
The system imports service usage data into the data storage. The imported data are already pre-formatted into the UMR format (the uniform format of service usage data used by the TelMD and TelCharge systems). In addition to the UMR format, the system also enables import of data from other formats (roaming partners etc.). The import of XML data is also supported.
The system logs all activities and reports possible import errors.
2.2.1.1 Data Export
The system enables export of data to other systems through certain interfaces. The most significant of these are interfaces towards the billing pre-processing system TelCharge and the billing system TelBill. Data can be exported to other systems, such as roaming partners, in the form of TAP files. Various output formats (XML) and export mechanisms that depend on the target system may be used.
The system logs all export related activities and reports any errors.
2.2.1.2 Data Archiving
The standard RDBMS and operating system methods are used to provide the data archiving functionality. Data are archived to magnetic tapes (tape libraries).
2.2.1.3 Restricted Access Control
The system provides restricted access functionality through the means of RDBMS and operating system platform.
2.2.1.4 Data Analyses
UMR Storage provides various reports concerning the quality of data being analyzed. Such information may influence some business decisions of a telecommunication operator. The system uses the advantages of OLAP technology.
The following categories of reports (analyses) are provided:
Error reports (unsuccessful calls) of class definition and cause for selected nodes operators and time period
Successful call reports that present the total calls, volume duration, and charged duration for selected nodes, providers, destinations (services) and time period
financial reports (if financial data are available)
other reports (inter-billing reports)
The actual reports depend solely on telecommunication operator/provider needs.
The following screen shots show examples of some of the reports provided by the system:
Figure 7. Error Statistics - the structure of unsuccessful calls by class definition. We can see the percent occurrence of class definition according to all unfinished calls by hours within a