OSS deals with critical issues of operators

OSS deals with critical issues of operators:

•Order management systems allow operators to coordinate the process of configuring the network to deliver the services ordered by a customer.
•Provisioning systems allow operators to turn up (activate) services on the network/service infrastructure.
•Inventory systems allow operators to accurately track their network assets, and assign those assets to customers.
•Mediation systems allow operators to determine service usage.
•Rating systems allow operators to determine how much to bill based on the service usage for a particular customer.
•Network management systems allow operators to detect and isolate network failures, and quickly restore service.
•Service assurance systems allow operators to correlate network performance with service quality requirements, and appropriately communicate and compensate customers for any disruption.
•EAI systems allow operators to quickly integrate diverse support systems and network elements.

EAI : Enterprise Application Integration in Telco

EAI = electronic integration of support systems is required for an automated back-office in large-scale operations.

The role of EAI : is to simplify the integration headache by creating an open data exchange platform optimized for heterogeneous inter-process communication ("plug and play").
EAI is the software designed to support communication between software systems, including OSS

Rating Engine

The Role of Rating Engine

The role of the rating engine is to apply pricing rules to a given transaction, and route to the rated transaction to the appropriate billing/settlement system.

Rating steps:

(1)Determine
a.Connection date & time
b.Duration
c.Rate period for discounts

i.Time of day (TOD)
ii.Day of week (DOW), holidays
d.Rating increments
i.1, 6, 10, 30, 60 second increments
ii.Per packet, per byte
e.Jurisdiction
i.Regional, National, International
ii.May be used for rating, settlement, tax
(2)Rate table look-up using
a.Event date
b.Event type
c.Optionally
i.Rate table ID
ii.Rate period
iii.Jurisdiction
(3)Calculate event charge
(4)Calculate tax (optional)
(5)Store relevant information on the xDR

Steps to rate a call

(1)Determine charge points

a.Originating charge point
i.“A” number from the CDR (May be the originating cell site address)
ii.Originating charge point = country code + city code + exchange

b.Terminating charge point
i.“B” number from the CDR (May be the terminating cell site address)
ii.Terminating charge point = country code + city code + exchange

(2)Retrieve place names

a.Table: Charge point place names
b.Originating & terminating
c.Store on CDR

(3)Determine band
a.Fixed or Mobile
b.Terminating country
c.Terminating network
d.First 5 minutes etc

(4)Rate table look up using

a.Rate Table ID (optional)
i.Assuming rates specific to rate plans
b.Call date
c.Call type
d.Band
e.Rate period (optional)
i.May be a flat discount percentage applied

(5)Rate table look up may return

a.Flat price per event
b.Rate per increment
c.Rate per increment + discounts

Billing Process

Definition:Network data management (i.e., mediation) and rating are the key OSS elements that support the billing process.


Purpose of a Billing System:

•Meter and bill the services consumed by the customer
•Allow definition of different rates for services
•Allow easy management of customer accounts
•Maintain record of payments received

Billing Functionality:

Billing is more than just a means of collecting money. In a marketplace fueled by competition, Carriers are recognizing billing as a strategic weapon in the battle for new and retained business.

Various types of telecom billing includes

Wireless Billing
Convergent Billing
Interconnect Billing
IP Billing

Critical Billing requirements include

•Flexible rating capability for new services
•Multi-mode processing : real time, hot or batch
•Multi-party settlement capability
•Service convergent
•Unified accounting: postpay/ prepay/ nowpay
•Adaptability and ease of use
•Multi-territory and multi-role capabilities
•Carrier- grade performance
–Functional
–Scalable
–Useable
–Available

Key definitions

•Account: Any customer is represented in the billing system as an account. One account can have only one customer

•Plan: A plan is a bundle of services associated with the account

•Service / Product: Different billing vendors have different definitions for service…. check out the definition for specific package

•Billing cycle: A periodic cycle for which the customer is billed. E.g. from the 4th of a month to the 3rd of the next month. Can be weekly, monthly, bi monthly, quarterly

•Accounting cycle: A cycle for which the charges against an account are calculated (not billed)…typically monthly.

•Recurring Charge (RC): A predetermined charge associated with a product or service that is assessed on a regular interval i.e., monthly, quarterly, annually

Mediation Systems:

The role of mediation systems is to capture usage information from the network and service infrastructure, and distribute it to upstream billing, settlement, marketing and other BSSs.

Mediation processes the Call Detail Record (CDR), call, message, usage, traffic, ticket, event, xDR

Usage types can be

•Fixed to Fixed
•Fixed to Mobile
•Mobile to Fixed
•Mobile to Mobile
•Roaming
•Value Added Services (SMS, Call Forward, etc.)

Key activities in Mediation – Usage collection

•Polling / Data Collection
•Consolidator across network elements
•Standardize inputs to Biller
•Support for real time applications
•Drop non-billable usage
•Reformat, validate, number translations
•Direct usage between applications
•Insulate the biller from Network elements

The validation functions in mediation includes:

•Duplicate checks
•Drop calls
•Perform edits and translations
•Creating message legs
•Table look up and conversion (CLLI -> country code, city code, exchange)
•Assign a unique tag number to the event