hp opencall IN prepaid

service platform billing

backgrounder

generating revenue with a new breed of prepaid user

prepaid, driving mobile growth
More than 50% of new mobile network subscriptions are prepaid users. In Europe, these
now outnumber postpaid subscribers, at 59% of users in 2000,1 and in Asia, the figure is
set to reach 49% by 2006.2 Prepaid is no longer only a method of payment for credit-
challenged users, but has also proven to be an attractive way to offer new services and
technologies to a growing audience: a large part of SMS traffic is related to young
prepaid users for example. Other users wish to control spending or retain independency
from one particular service provider, and figures suggest that this new type of user is on
the increase: a recent study by the Yankee Group indicates that 37% buy prepaid to
control costs, and 23% because they “don’t want a contract”.3

However, this more discerning prepaid subscriber requires the same types of service as
the postpaid customer, in particular network roaming, as well as access to new services
that are becoming available, (mobile internet beyond the WAP, mobile commerce...).
Being independent from their service provider, able to change as they wish, they will not
hesitate to move where these services can be obtained, and accessed reliably.

new challenges for mobile operators

The change in the prepaid market has brought with it new considerations and challenges
for mobile service providers. Today, for many service providers, the majority of users are
prepaid customers. This large user base has, often, not enjoyed many of the value-added
services that already exist for post-paid subscribers. As the industry recognizes that
prepaid subscribers deserve access to these services, one of the quickest and easiest
paths to new revenue is to offer existing services to the already large numbers of prepaid
customers. Although certain operators have already opened these services to their
prepaid users, many of them are facing revenue loss due to a lack of real-time billing.
This last call exposure problem represents a high risk for operators as they lose money
whenever a call made by a prepaid subscriber cannot be released immediately once
their account balance has expired during the call (indeed the account balance could
actually reach negative by the end of the call).

Service providers are also already looking to tomorrow’s networks and services. In
today’s uncertain market, the need to rapidly roll out new services that not only generate
revenue but also differentiate them from the competition is more important than ever. With
tomorrow’s high-value services (music, video clips, etc.), in order to secure the highest
ROI and a seamless offering, service providers must ensure that these are open not only
to post-paid subscribers but also prepaid customers. However since tomorrow’s services
involve much higher levels of transaction, guaranteeing that operators are paid for the

1. Source: “Mobile Services: Western europe 1996-2005 (Executive Summary)”, published by the Gartner Group, 2001.
2. Source: “Asia Pacific Mobile Revenue Forecast: A Bright Future Ahead”, published by the Yanlee Group, 2001.
3. Source: “Wireless Prepaid: From Growth to Profitability”, published by the Yankee Group, 2002.
services that they deliver is absolutely vital. Whereas the inability to bill in real-time a $1
prepaid voice call might represent a significant revenue loss for today’s service provider,
the loss of revenue following the unbilled delivery of high-value content (which can
represent several $10s) would be simply unacceptable.

hp opencall IN service platform — the key to real-time prepaid

HP, with its Opencall IN service platform, can help service providers rise to these
challenges. In common with the HP Opencall software suite, the Opencall IN service
platform has been specifically designed to meet the telecom industry’s rigorous
requirements. Core features such as carrier grade service continuity (99.999%) and true
scalability are guaranteed thanks to a deep implementation that starts right from the
platform’s architecture. Today the HP Opencall IN service platform provides services for
millions of subscribers across the world.

As well as addressing the future, today’s solutions must also integrate with current services
on existing infrastructure. Thanks to its design, the HP Opencall IN service platform is well
positioned to power this evolution. Like all HP Opencall platforms, the IN service platform
is designed to be a multi-vendor and multi-network product thanks, in large part, to the
openness of its APIs and its full suite of customization tools. Not only do these qualities
accelerate the integration of the IN service platform into existing infrastructures but they
also protect the service provider’s choice of interfacing elements such as billing systems,
IVRs, etc. The platform’s openness and flexibility also benefit connectivity: in addition to
support for wireline, wireless and converged networks, the HP Opencall IN service
platform is ready for 3G networks. This powerful combination offers investment protection
vital to service providers in challenging environments.

As this whitepaper is about to explain in greater detail, the HP Opencall IN service

platform is the key for operators seeking to quickly implement real-time prepaid billing,
convergent billing, allowing prepaid subscribers access to the full range of existing
services, as well as tomorrow’s high-value services.
hp opencall IN service platform in the mobile network
With prepaid billing, the HP Opencall IN service platform controls access to voice and data on mobile networks:
• the network layer performs the service switch function
• the billing server performs the cost control function

The integration between these three layers must ensure reliability, short latency and efficient usage of all resources.
Effective integration must exist both with SS7 network signaling, and advanced prepaid billing systems, in order to enable
effective new business/charging models. To achieve this, we must define the role of each application in each layer and
how they will be integrated. The diagram above illustrates the end-to-end prepaid solution.

functional capability of billing

The prepaid billing system provides the key capability to support the Cost Control Function in sessions for voice, data and
content. It supports
• a two-way interface to the access and service control function, carried out by the HP Opencall IN service platform, in
• order to receive user requests for service usage, and to control the connection session
• a rating function and balance management to calculate, in real time, the tariff to be applied, and to verify the credit
• level, and execute the authorization function
• a database to hold the subscriber balance

In a typical scenario, a prepaid customer must obtain authorization before making a call (or using a service). The rating
engine must determine, in real time, which tariff to apply, according to the service requested. It must then request the
balance management to verify the credit level, reserve credit, and control the connection accordingly, using HP Opencall
IN service platform as the access and service control function.
functional capability of the access and service control layer

To illustrate how the HP Opencall IN service platform functions as the pivotal point in a
prepaid solution, the examples presented here describe simple voice and data scenarios
using the CAMEL (Customized Applications for Mobile network Enhanced Logic) message
sets defined by ETSI (European Telecom Standards Institute), which are being deployed on
GSM networks.

The same scenarios can be implemented in networks using the CDMA standards, through
the use of the WIN message sets defined by TIA (Telecom Industry Association). The
message flows are functionally similar.

The HP Opencall IN service platform interfaces with the SS7 network, and manages the
dialog between the network and prepaid billing system, in real time. Together this can be
considered as a service access controller. It needs to have some degree of flexibility and
configuration to be able to adapt to the implementation of the message set, and interface
with a billing system.

• network messages are treated in real-time by the service access controller which also
• performs the appropriate function to interface with a billing system — various
• transaction requests need to be managed: Connection Authorization, Pre-Advise of
• Charge, Request Credit Token on Apply Charge, Release Call, Manage Exception
• handling (Play Announcement) and, Monitoring and Managing Connection
• Performance Throughput
• additional services can be provided such as location information, and SMS receipt
• and emission
• the service access controller also allows roaming users to access these services
• via their home network
how it works: prepaid message flows
The following examples represent possible voice, and data scenarios for prepaid billing. In these examples the IN system
handles call signaling information between the 2G, 2.5G or 3G mobile networks, and the prepaid billing system.
Essentially, the IN system acts as a network front-end for the billing system.

The diagrams show simple message flows between the switch or MSC (Message Switching Center), the HP Opencall IN
service platform, and a prepaid billing system. The message flows are specific cases and do not detail every possibility,
e.g. caller or callee chooses to end the call normally, error cases, use of voice announcements or short messages to
request credit recharging etc.

These scenarios also assume a basic prepaid model. In practice the chosen billing system may provide extra features such
as the ability to adapt to a postpaid model once prepaid credit has expired. This depends on the prepaid billing system’s
capabilities as well as the subscriber options, which the billing system maintains in a subscriber profile.

The scenarios can be extended to include user interaction, with IVR (Interactive Voice Response), using CAMEL or WIN,
and also to the use of location information for home-zone billing, or of short messages, for example, to notify users that
their credit is low (MAP message set on GSM networks or IS-41 message set on CDMA).

In the following call flows:

• mobile networks are GSM and GPRS standard
• all interactions between MSC (Mobile Switiching Centers) and the HP Opencall IN service platform use the CAMEL
• message set
• interactions between the HP Opencall IN service platform and the prepaid billing server use the flexible plug-in facility
• of HP Opencall which allows the platform to be easily modified to support any available or future billing system. The
• plug-in also enables connection to Parlay/OSA-capable billing systems (OSA is Open Service Access as defined
• by 3GPP - Third Generation Partnership Project.

voice call message flow

scenario 1: call terminated by billing system on credit expiration

In this example the call is terminated by the prepaid billing system as the available credit expires.

1) The prepaid subscriber dials

2) a number to setup a voice
2) call.
2) The MSC sends an InitialDP
2) to the HP Opencall IN
2) service platform which
2) interrogates the billing system
2) to determine whether the
2) subscriber has credit for the
2) voice call.
3) The billing system calculates
2) the tariff for the call based
2) on information passed in the
3) Request_Authorize message –
2) derived from the InitialDP –
2) and authorizes or denies the
3) call based on the subscriber’s
2) credit.
4) The HP Opencall IN service platform sends a Continue message to the MSC to allow
2) establishment of the voice call. It also requests event reporting
2) (RequestReportBCSMEvent) to know when the call starts and ends, apply charging
2) (ApplyCharging) to receive notification when credit must be rechecked and reserved,
2) and charging information (FurnishChargingInformation).
5) When the call is established, i.e. the called party has answered, the MSC informs the
2) HP Opencall IN service platform via an EventReportBCSM message which in turn
2) notifies the billing system of the start of the call.
6) At this moment the billing system reserves a credit for the call to cover the period until
2) the first charging report.
7) Periodically the MSC will send ApplyChargingReports to the HP Opencall IN service
2) platform. The platform passes the information to the billing system which checks that
2) the credit has not been exhausted.
8) If insufficient credit remains to continue the call the billing system requests the HP
2) Opencall IN service platform to terminate the call (ReleaseCall) as is demonstrated in
2) this call flow.

scenario 2: call terminates normally

In this example the call is terminated normally by the caller or called party.

Steps 1) through 7) are as previous scenario.

8) When the called or calling party ends the call, an EventReportBCSM message is sent
2) to the HP Opencall IN service platform to indicate that a party has disconnected. A
2) final AnalyseChargingReport is sent to indicate how much of the previously reserved
2) credit was used. The IN platform indicates to the billing system how much credit was
2) used in the last AnalyseChargingReport.
data session message flow

successful prepaid data session

This scenario represents billing a data session based on volume, that is per kilobyte of data transferred or duration of
session only, and not on the “market value” of the content accessed.

1) The prepaid subscriber initiates a data session using GPRS.

2) The SGSN sends an InitialDPGPRS to the HP Opencall IN service platform which interrogates the billing system to
2) determine if the subscriber has credit for the session.
3) The billing system calculates the tariff for the session based on information passed in the authorization message
2) (number dialed, location, subscriber account information, time) – derived from the InitialDPGPRS – and authorizes or
2) denies the session based on the subscriber’s credit.
4) The HP Opencall IN service platform sends a ConnectGPRS message to the SGSN to allow the session to be
2) established. It also requests event reporting (RequestReportGPRSEvent) to know when the session starts and ends, as
2) well as requesting charging information (AnalyseChargingGPRS) to be able to periodically check that the subscriber has
2) sufficient remaining credit and provides charging information (FurnishChargingInformationGPRS).

5) When the session is established the SGSN informs the HP Opencall IN service platform via an EventReportGPRS
2) message which in turn notifies the billing system of the start of the session.
6) At this moment the billing system reserves a credit for the session.
7) Periodically the SGSN will send ApplyChargingReportsGPRS to the IN platform. The IN platform passes the
2) information to the billing system which checks and allocates further credit if available.
8) If insufficient credit remains to continue the session, the billing system requests the IN platform to terminate the session.
9) In this example the session terminates normally sending an EventReportGPRS to signal the end of the session and an
2) AnalyseChargingReportGPRS to indicate how much of the reserved credit was used.

The HP Opencall IN service platform provide all these message sets.

content-based and data-based billing

Content-based billing refers to credit being reserved for transferring high-value content,
such as an MP3 audio file, and the session being charged based on the “value” of the
medium (price charged by the content provider), and the successful download of the
complete medium. Data-based billing refers to the number of bytes downloaded. Both of
these can be handled by the HP Opencall IN service platform.

Content billing is made possible by processing usage events from equipment such as
WAP gateways or specialized content servers. HP IUM (Internet Usage Manager) is
capable of aggregating information from diverse equipment in real-time, which means it
operates on streams of usage information rather than batch processing log files.
Combining HP IUM and the Opencall IN service platform allows the best of both worlds:
real-time session control (access to services, value-added services, and call authorization),
and real-time content-based billing.

The HP Opencall IN service platform’s ability to interface with diverse network elements
as well as directly dialog with HP IUM enables customer service to be enhanced. Tariffs
can even be precisely tailored to the subscriber according to information such as location
details and user profile (interests, likes and dislikes, purchase history, for example).
Conversely, information aggregated by HP's IUM can generate an action which the HP
Opencall IN service platform will immediately handle: for example, following end-user
data activity, HP IUM may request the Opencall IN service platform to bar the user's
access.

For more information on HP Internet Usage Manager, please consult

www.hp.com/communications/press/ium.html
hp opencall meets the prepaid challenges

enabling services the customer wants — voice, content, roaming

As was illustrated, the HP Opencall IN service platform interfaces with all the elements of a network through its highly
flexible architecture:
• interfacing with any billing system system through its flexible plug-in mechanism
• allowing a high degree of adaptability through its wide range of customizable message sets
and in this way, enables the rapid deployment of revenue-generating services.

HP has proven experience of full integrations of several leading real-time prepaid billing systems, and accompanies its
customers every step of the way with consulting and integration services.

In addition, the HP Opencall IN service platform integrates smoothly into 2.5G and 3G networks to enable data services
and network roaming.

robust, reliable platforms reduce the risk of service downtime and call exposure

HP Opencall IN is a carrier-grade, highly available, platform that runs in a reliable environment ensuring availability
greater than 99.999%. It is able to preserve call and session contexts so that, in case of billing server failure, the session
is correctly billed. This level of reliability not only ensures a satisfied end-customer, it also ensures revenue is not lost when
a call is lost.

Even faster response times, as well as high availability for the total solution, can be achieved through more advanced
integration which involves caching reserved credit information in the HP Opencall IN service platform to enable it to
monitor and terminate the call, or other action, itself. It would then require less interaction with the billing server, enabling
higher performance and lower latency, and therefore potentially greater fault resilience.

investment protection

The HP Opencall IN service platform is designed to be highly scalable to ensure deployment and operational costs can be
optimized: as subscriber traffic increases, the underlying platform can be upgraded. The HP Opencall IN service platform
also benefits from all the scalable attributes of HP’s UNIX® based servers, allowing operators to take advantage of rapid
advances in general-purpose computing power and the price-performance ratio.

With the trend towards convergence of both prepaid and postpaid billing systems into real-time billing, the HP Opencall
IN service platform ensures service providers can respond to today’s challenges, while preparing the way for new revenue
opportunities through high value content billing, and the reduction of operating costs through unification of their complete
subscriber base under one billing system.
 how hp can help you

HP’s portfolio of products and solutions currently

addresses both circuit switched and packet switched
networks, and possesses the necessary capabilities to
address 3G networks and services. Built on top of our
HP Opencall SS7 signaling platform, the HP Opencall
IN service platform enables service creation and
deployment in a multi-network and multi-signaling
context. HP Opencall platforms already comply with
CAMEL phase 3 and WIN2 (IS-826), and HP is
implementing protocols and standards defined for 3G.

For further information regarding the HP Opencall IN

service platform, please consult the datasheet on the HP
Opencall website:
www.hp.com/communications/opencall

about hp opencall

HP Opencall is an HP Netaction product, providing

comprehensive, carrier-grade platforms for the development
and deployment of next generation voice, data and converged
services. With more than 1,600 installations in 100 countries
worldwide, HP Opencall is a world leader in SS7 software
stacks and the number one software for Service Control Points
and Short Message Service Centers.

Backed by HP's Telecom Critical Support, which provides

world-class restoration service internationally, as well as HP's
superior combination of hardware and software, HP Opencall
enables the communication industry to harness the
convergence of the Internet with the world of voice
communication.

For further information on HP Opencall platforms, please visit

our web site at: www.hp.com/communications/opencall

The information contained in this document is subject to change without notice

UNIX is a registered trademark of The Open Group.

© Copyright Hewlett-Packard Company 2002

06/02 5981-1595EN