B-oo-levard® Interconnect -
Billing and Settlement in real-time
B-oo-levard® was designed to offer the functionality and the performance required by the most
dynamic and competitve market: the telecommunications market. B-oo-levard® has the capability to
support the increasingly complex range of services that every successful communication service provider needs to
offer. B-oo-levard® has the performance and scalability to deal with the highest call volumes. And
it is a system that you can get up-and-running as fast as possible.
B-oo-levard®'s powerful, multi-lingual, multi-currency client/server technology offers the
performance, functionality and reliability you need. B-oo-levard® can be implemented rapidly,
handling the voice and data products and services you offer today. And it's ready for the next generation of
services, such as VPNs and Intelligent Networks. The technology used and the architecture designd for
B-oo-levard® allows to used it as a stand-alone Interconnect Billing system or to have Interconnect
Billing as standard feature of the regular rating and illing process achieving highest effieciency.
B-oo-levard® was designed by B4E not only to meet the requirements of the most sophisticated
networks, services and charging agreements - but to be even independent of whatever the telecom system environment
and telecom offers are. Based on a very powerful and an extremely flexible rating engine, B-oo-levard®
includes all the facilities you need to unlock the revenue potential of your network:
Automated Least Cost Routing
B-oo-levard® supports Inerconnect with a sophistcated automated least cost routing process using
the Djikstra algorithm. Each time a Interconnect related price plan or campaign has been added or changed an action
will be started (automatically or initiated by a user) which establishes a new/updated LeastCostRoute (LCR) Table.
This table not only considers the least cost to define the best route at every point of time, but also supports
capacities. Such capacities are reduced in real-time accordingly whenever an event “eats” up such capacity.
In an Interconnect case B-oo-levard® checks the event against the LCR table and determines the best route for this
event in real-time. The table may be printed or displayed in a graphical mode on-line as well.
|
Mediation Layer
accepts and processes any format of XDR
features a user-friendly GUI for the format definitions
supports GSM, SMS, WAP, GPRS, UMTS, Switched Network, IP,
FTP, HTTP, xDSL, VPN, ATM, MPLS, etc.
supports XDRs from the mediation platform in push, pull and streaming modes
processes "hot" records immediately in real-time
assures complete processing: B-oo-levard® breaks files into single events which are
committed into a transaction stack in order to ensure no data is lost for e.g., a system breakdown.
supports XDRs from the mediation platform in push, pull and streaming modes
|
XDR Processing
XDRs can be filtered based on rules. Such rules may use all data elements provided to the
B-oo-levard® system enabling for a 100% flexibility.
B-oo-levard® event collection supports routing, filtering and / or duplication of events.
XDRs can be written out to multiple files and directories contingent upon their type (as defined by the filtering
requirement) allowing then for special further processing
B-oo-levard® assembles partial events based on customer-defined rules. The rules use
information available in the XDR or in other data (e.g. customer data) provided to the system to collate or
aggregate the partial events. XDRs can be enhanced with further external data.
|
|
Error Routines
duplicate record checking is performed for all incoming XDR files and all single events as well
rejected XDRs are stored for analysis and correction at all stages in the process
rejected XDRs can be resubmitted at all stages in the process
rejected XDRs are stamped with a reason code, the date of rejection and the process id
which rejected them
rejected messages are aged and can be deleted, e.g., by batch id or date
|
Charging Matrix
ability to set distance based rates (local,regional, national, international, …)
ability to set specific tariffs for a given period (peak, off-peak, week-end, holidays, …)
ability to rate specific services (ISDN, Premium Rated, Data, Fax, …)
ability to set special rates (volume discounts, calls to special numbers, calls routed through certain operators,
calls to mobile numbers, freephone, …)
ability to define detailed information on operators (contact name, terms of settlement, …)
ability to base SMS charging, e.g., on fixed price per length, banded pricing by length, periodic fixed or scaled
usage subscription
|
|
Call Rating
every XDR type can be rated by the B-oo-levard® rating engine, e.g. MSC, SMSC, VMS, MMS, IN etc.
unbilled, rated XDRs can be re-rated using available selection tools - in bulks or as single events
non-rateable calls can be viewed, edited and resubmitted for rating. Application security ensures that only specific
users can perform this function; the value of calls resubmitted can be limited
performs rating based on any and multiple user defined XDR fields and other information provided to
B-oo-levard®
the B-oo-levard® rating engine supports any rating complexity, such as tiered rating,
multi-currency rating, and multi-leg call rating, ...
each interconnect partner can have a separate rate plan that is used to cost its calls
|
Interconnect Billing
periodic (weekly, bi-weekly, monthly, quarterly, etc) invoices and reconciliation reports are produced for each interconnect partner
B-oo-levard® prevents calls from being included in more than one invoice
B-oo-levard® performs inter operator (inbound and outbound) invoice billing on a parameterised
cycle basis (weekly, monthly, quarterly, etc), and supports each interconnect party to have a separately defined
billing cycle
separate bills for each operator may be based on any criteria available with B-oo-levard®
supports user parameterised thresholds for the number of qualifying XDR records per billing cycle per operator
supports interconnect Mobile Number Portability charging for both ported Out and ported In numbers
supports MVNO (Mobile Virtual Network Operators) and similar “branded” operators
|
|
Interconnect Reconciliation and Analysis
models other interconnect party cost structures cost and revenue analysis and reconciliation, to provide tracking
and evidence for overcharging
ability to enquire the XDR database according to: operator, type of interconnect agreement, input/output criteria,
type of tariff or service, time period (monthly/range of months balances, date range), calls grouped by day, rate
plan and time interval, call aggregates for user defined periods
support standard interconnect agreements re dispute values and payments
provides dynamic analysis of interconnect data for operational management and decision making
Content Settlement and Partner Relationship Management
lets you define revenue sharing models according to different rules based on different charging parameters (event,
volume, duration, quality of service, …)
lets you introduce discounts to certain partners based on “frequently used partner or service” policies
provides a reconciliation management tool allowing to verify from the invoice and down to the XDRs
performs simulations of the agreements signed with the partner (to verify profitability, for example)
|
Data Services
rates IP services based on access to a specific service, Volume of data transferred, pay-per-event, quality of
service, any combination of these and any other criteria - and considering any discount
supports interconnection for WAP based content providers unstructured supplementary services data (USSD) via
multiple delivery media
rates IP VPN services (VPN Interconnection)
integrates with directory based access systems from major vendors using LDAP protocol for content and real time
integration with charging and billing systems
collects, collates and stores access and usage statistics for content providers for re-billing or cost charging
supports IP based accounting, billing and reconciliation to interconnect partners for supplementary services based
on usage or data content charging, for example: Web pages/articles accessed, MB/KB accessed and/or downloaded, pay
per view / play (video images, files, or audio files), data packets (sent or received), IP gateway port, application,
quality of service level accepted, one off access fees or other flat fee charge basis, royalty based payment
structures, subscription fees and renewals, time and duration of service access, distance and time of day, Value
based charging (e.g., new stock market information, alternative route information to avoid traffic jams),
transaction event based charging, co-location based charging, network bandwidth (network capacity usage) charging,
source and destination IP address, ...
|
Copyright © 2004 B4E Solutions GmbH. All rights reserved.
|