Sie sind auf Seite 1von 81

Intelligent Networks and Value-Added Services

NSN-IN ORIENTATION

COURSE OUTLINE
CHAPTER 1: CALL FLOWS

CHAPTER 2: OVERVIEW
CHAPTER 3: SUBSCRIBER LIFE CYCLE
CHAPTER 4: GHP SERVICES

CHAPTER 5: BASIC TROUBLESHOOTING

CHAPTER 1: CALL FLOWS


1.
2.
3.
4.
5.

Normal GSM Call Flow


Prepaid GSM Call Flow
SMS Charging Flow
SMS-MT VAS (Hotbilling) Charging Flow
SMS-MT VAS CSP Charging Flow

NORMAL GSM CALL FLOW

SS7

1
2
Sub A
SS7

1 Sub A attempts to call Sub B


2

MSC checks Sub B status in HLR

HLR gives the location area of Sub B

MSC pages the location and connects


To Sub B

4
Sub B

PREPAID GSM CALL FLOW


2
3

SS7

SS7

1
4
Sub A
SS7

1 Sub A attempts to call Sub B

2 MSC checks prepaid balance in IN


3 IN confirms balance and allows the call
4 MSC checks Subs B status in HLR
3 HLR gives the location area of Sub B
4 MSC connects to Sub B

6
Sub B

SMS CHARGING FLOW


2
1
3

SS7

SS7

6
Sub A

Sub A sends SMS to Sub B

MSC checks prepaid balance in IN

IN has enough balance and allows SMS to proceed

MSC sends SMS to SMSC for storage

SMSC confirms receiving of SMS

MSC requests IN to charge SMS

IN confirms charging and Sub A received Message Sent

5
SS7

SMS-MT VAS (HOTBILLING)


CHARGING FLOW
2
1
3

SS7

SS7

6
Sub A
1 Sub A sends SMS to request for VAS
2 MSC checks prepaid balance in IN

4
SS7

TCP/IP

3 IN has enough balance and allows SMS to proceed


4 MSC sends SMS to SMSC for storage
5 SMSC stores SMS and acknowledges to Sub
6 MSC requests IN to charge SMS (0 charge
since MT)
7 SMSC creates log (charging file) and send to CMD
8 CMD joins the CDR files and transfers it to IN for charging.

TCP/IP

CMD

SMS MT VAS (CSP) CHARGING FLOW


2
1
3

SS7

SS7

Sub A
1 Sub A sends SMS to request for VAS

10

2 MSC checks prepaid balance in IN

SS7

TCP/IP

3 IN has enough balance and allows SMS to proceed


Blade

4 MSC sends SMS to SMSC for storage


5 MSC requests IN to charge SMS (0 charge since
blade is doing the charging)
6 SMSC sends request to Blade
7 Blade then sends the request to the CP for the content, CP sends
back the content to CSP
8 Blade charges sub balance in IN
9 Blade request SMSC to deliver to sub
10 SMSC delivers to sub

TCP/IP

Blade

CP

CHAPTER 2: OVERVIEW
1.
2.
3.
4.
5.
6.

Charge@Once Component
Software Architecture
Network Architecture
3rd Party Applications
Interfaces
External API

CHARGE@ONCE COMPONENT
Within the charge@once system, the rating data has
been organized into three levels of hierarchy for ease of
administration and deployment of tariffs.
Contract
At the highest level which will define the common
properties to be used across various products/access
types.
Product levels
define the type of access or type subscriptions which
influence the rating engine.
Tariff Model
lowest level of hierarchy. This is the level at which the
exact tariffs for a call are defined.

Contract (Level 1)
A contract includes all properties agreed on during
subscription.
It refers to all products (MOC, SMS and MTC) accessible
by the subscriber and the corresponding tariff data.
It also pertains to all possible discount subscriptions,
periodic subscriptions and feature subscriptions which
can be used by the subscriber.

The contract level has several tariff / rating data which


are common across various products.

Contract (Level 1)
The data of a contract includes:
References to products and/or subscriptions.
Common contract data (valid for all referenced products)

At the subscriber level we have a reference to the contract,


thus during the creation of the subscriber on the charge@once
system, it must be referenced to a valid contract.

Product (Level 2)
A product is a part of a contract.

A product represents a type of service accessible by the


subscriber, and describes all tariffs for this type of
service.
A product also represents subscription packages which
can be used by the subscriber.

Product (Level 2)
The data of a product includes the following:
References to tariffs (and/or tariff models)
Common product data (valid for all referenced tariffs
and/or tariff models).
Subscription packages configurations
Discount Modifier Options
Periodic Options

Product (Level 2)

Tariff Model (Level 3)


defines the actual E-parameters or the cost of the
products.
charge@once can support up to 10 different tariff models
per product. As it is possible to define 10 different tariff
models it is possible to offer 10 different rates for the
same call.

SOFTWARE ARCHITECTURE
The core functionality of the charge@once is to provide
real time rating and charging of different products and or
services.

Charge@Once Solution Architecture

RATING LOGIC/ENGINE
responsible for the execution of rating.

CHARGING LOGIC/ENGINE
is the heart of the charge@once
does the processing of charging and recharging requests
coming from the different Service Logics

interacts with the Rating engine for all rating related


operations by calling the Rating engine at the start of a
sessions and at appropriate points during the sessions.
receives tariff information for the execution of charging
Calculates quota sizes (time, volume, price) to be
granted.

CHARGING LOGIC/ENGINE
calculates charges at intermediate points during
sessions as well as final charges at session end.
interacts with the Balance Management for all account
related transactions (selects accounts - monetary,
bonus, accumulator, makes reservations, charge the
accounts, updates bonus accounts and accumulator
accounts or usage counters).

SERVICE LOGIC
responsible for call and session control.
provide the necessary functionality to trigger the
services, protocol handling, and the typical service
dependent features such as user interactive dialogue,
announcements, etc.
hide protocol and service dependencies from rating and
charging.
forwards the charging requests to the Charging Logic.
receives charging responses from the Charging Logic
and return the respective results to the underlying
network elements (including the respective error
handling).

SERVICE LOGIC
Types of service logics:
#7 based Service Logic for #7 interfaces / SS7 (e.g.
CAP, INAP)
IP based Service Logic for IP interfaces (e.g.
Ro/Diameter)

IP based Hot Billing Service Logic for ticket interfaces

BALANCE LOGIC/MANAGEMENT
responsible for the access to accounts of prepaid
subscribers, as well as the respective storage
transactions.

interacts with Charging Logic for all account related


transactions for the execution of charging.
includes the Balancing Function which supports various
account types such as monetary accounts. All accounts
are controlled and managed in real-time.
is accessed by the Charging Logic and performs all
account related operations such as read, charge,
recharge and reserve operations, and threshold
supervision to avoid negative balances.

Rate Plan
Mapping

to Rate Plan
Price, Tariff Parameters,

Internal API

Contract ID

Charging Profile ID

Rater

Rate Type
Tariff ID

Charging
Logic

Reference to
Charging Profile

Charging Profile

Return
success
or failure

Reserve, charge,
recharge and read

Balance
Management
AccountKey

Return result

Balance

2000

1000

Internal Inter-working of the logics

Siemens AG, December 2005

NETWORK ARCHITECTURE
AMAX

CSP

Frontier

IVR

Eagle

3rd Party Clients

IPD Routing Node 1


CMG/SMSC
CMG/SMSC
CMG/SMSC

IPD Routing Node 2

...

IPD Routing Node x

IPD Load Balancer

IPD Group

CMD

Backup and Restore


Server (B&R)
SEP Node 1

RGW

SEP Node 2

Charge@Once Select Platform

Bar/Debar Server
(BDS)
VDS

Advantage
Commander
(Adcom)

SEP (SERVICE EXECUTION POINT)


6 Charge@Once Platforms (2 PFs in Aurora site
and 4 in Valero site).
7th c@o platform ready for service by July located in San
Juan site.
Each platform is composed of 2 SEP in load-sharing
mode.

Hardware Specs: SUN E6900 server

SEP (SERVICE EXECUTION POINT)


The core NE of an @vantage platform, providing all
functions required to execute IN services.
The @vantage SEP corresponds to the SCP of the IN
world.

SCP (Service Control Point)


Core @vantage component controlling the execution of
the service logics.
It is usually triggered by the SSP (Service Switching
Point) using the appropriate INAP (Intelligent Network
Application Part) operation.
It determines the destination number according to the
active RT (Routing Tree) and sends the answer to the
SSP.
Controls registration and billing of calls.

IPD (IP DISPATCHER)


IPD will serve as a mediation device between the
charge@once and 3rd party applications.
It will do a proper routing of request and response to the
target charge@once platform.

IPDgrp1 4 IPD routing nodes (ipdp1 to ipdp4)


IPDgrp2 2 IPD routing nodes (ipdp5 to ipdp6)
IPDgrp3 4 IPD routing nodes (ipdp7 to ipdp10)
IPDgrp4 2 IPD routing nodes (ipdp11 to ipdp12)
Hardware Specs: SUNFIRE V440 server
* IPDgrp1 and 2 is deployed in Aurora site.
**IPDgrp3 and 4 is deployed in Valero site.

RGW (RECHARGE GATEWAY)


Since Charge@once SEP is using a standard platform
interface which VDS cannot understand, RGW mediates
this charge@once messages towards the VDS during
223 inquiry and recharge.
RGW is just a temporary element until such time that we
fully migrated to Management System TopUp@vantage
(VOMS).
There are 2 RGW per platform in load-sharing mode.
Hardware Specs:
Fujitsu Siemens Primergy TS300 S3
Windows NT 2000

BDS (BAR/DEBAR SERVER)


The barring/ debarring server fetches periodically the
files with the barring / debarring information from the
SEP nodes and sends the barring / debarring MML to
the HLRs.

There are 2 BDS servers in active-standby setup located


in Valero site.
Hardware Specs:
Sunfire V440 Server

BDS (BAR/DEBAR SERVER)


Service such as Roaming SMS MO are not charged in a
real time mode but based on hot billing mechanisms
hence the need to bar these services on the HLR if a
subscribers account balance goes below a certain
threshold
Debaring of this service will be triggered after a recharge
establishing enough money to allow the usage of these
services to be operated in a hot billing mode.
Roaming SMS-MO Threshold = Php25
MMS Threshold = Php15

BDS (BAR/DEBAR SERVER)


MSISDN IMSI Catching

The barring/debarring command send to the HLR have


to contain the IMSI as a key to find and to modify the
subscribers record.

To avoid a separate database for the MSISDN to IMSI


mapping, SEP is capable of catching and storing the
IMSI out of the IDP message coming from the core
network.

B&R (BACKUP AND RESTORE


SERVER)
The NetWorker server software installed on the B&R
server backs up and restores the backup data
(databases and files) of all @vantage clusters on a tape
library called Jukebox.

The @vantage-platform-based data is backed up at


regular intervals to ensure a rapid restore of data when
data loss occurs. All data are restorable up to the point in
time the failure occurs.
Hardware Specs: SUNFIRE V440 server w/ Storedge C4
B&R1 backups IN1 and IN2 and located in Aurora.
B&R2 backups IN3 and IN4 and located in Valero.
B&R3 backups IN5 and IN6 and located in Valero.

ADCOM (ADVANTAGE COMMANDER)


provides functions for the operation and maintenance of
a distributed system consisting of several Network
Elements (NEs).
communicates with the NEs via a set of element
management agents.
Hardware Specs:
Sunfire V440 server

ADCOM (ADVANTAGE COMMANDER)


Adcom has the following management functions:
1.

Configuration management

2.

Fault Management

3.

Performance Monitoring

4.

Security Management

CMD (CHARGE@ONCE MEDIATE)


collects the raw CDR files from the SMSCs via NFS.
Convert the raw SMSC CDRs from binary format to
comma-separated values (CSV) format.

Filter out the invalid CDRs.


Segregate the valid CDRs into Postpaid subscribers
CDRs, TM subscribers CDRs and GHP Prepaid
subscribers MT VAS CDRs.
Hardware Specs:
HP RX2660 Server

CMD (CHARGE@ONCE MEDIATE)

Transfers the segregated CDRs to its respective


recipients, namely;

1.

Customer Care Billing System for postpaid


subscribers CDRs
Ericsson Billing Gateway for TM subscriberss CDRs
Charge@Once SEPs for Globe Handy Phone prepaid
subscribers CDRs.

2.
3.

There are 2 CMDs in load-sharing mode located in


Aurora site.

IVR (INTERACTIVE VOICE RESPONSE)


Callcard reloading via 223.
There are a total of 7 IVRs being used by GHP
subscribers.
3 IVRs are located in Pioneer and 4 are located in
Valero.
Hardware Specs: Alpha Server DS20E

3RD PARTY APPLICATIONS


NTG-MAINTAINED
1. IVR
2. Eagle
3. Claymore
4. SLEAK
5. IN Portal

ISG-MAINTAINED
1. Amax
2. Santa
3. Fun and Fun2
4. PNS/INM
5. CSP
6. SAL
7. New Frontier

3rd Party Clients IPD Distribution


IPD1

IPD2

IPD3

IPD4

IPD6

(ipdp1/ ipdp2/
(ipdp5/ ipdp6)
ipdp3/ ipdp4)

(ipdp7/ ipdp8/
ipdp9/
ipdp10)

(ipd11/ ipdp12)

(ipdp13/ipdp14/i
pdp15/ipdp1
6)

AMAX

CSP

Amaretto

Amaretto

IVR

SAL

Eagle

New Frontier

SASN/OLG

Trigger

Sleak

Russia

INM

Claymore

Fun
PNS
IN Portal

AutoloadMax (AMAX)
enables voucherless based recharging to GHP
subscribers via AutoloadMax distributor.
These distributors are typically shop keepers who resell
recharge to AMAX customers (GHP subscribers).
AMAX Distributors communicate to the AMAX
application via a SIM based application which contains
verification information. The AMAX application also
contains a monetary wallet for each distributor which is
used to recharge GHP subscribers accounts.
Charge@once doesnt have any visibility of the AMAX
wallet. This information is part of the AMAX database.

Santa
used as a bonus solution where the subscribers main
account and free SMS account are credited based on
subscriber activity.
uses input from various sources to calculate these
bonuses, such as call records, top up information etc.

FUN
FUN
extension of expiry of Roaming subs
FUN2
activates and deactivates the Prepaid Roaming
subscription.

PNS/INM
This application client support voucher based recharging
via an ATM machine.

CSP (Consolidated Service Platform)


used to charge and perform balance inquiries on
subscribers main accounts.
CSP is intended to be the primary system that performs
charging and balance inquires for external applications.
It contains centralized rating information for most
external applications.

SAL (Share-a-Load)
provides GHP subscribers the means of transferring
credit from there main account to other GHP
subscribers.

New Frontier
activates/deactivates time-based and wallet-based
subscriptions.

IVR
callcard reloading via 223
will only allow 5 invalid 223 reloading attempts. The 6th
attempt will be blocked. IVR blocking time is 3 hours.

Eagle
This provides the USSD services for our outbound
prepaid and postpaid roamers Project EAGLE services
are:
BALI (Balance Inquiry *122#)
TOPUP (Reload *123*card number + pin#)
CALLBACK (Outgoing Call *131*63917xxxxxxx#)

Claymore
used to charge GPRS transactions. It reserves money
for such transactions by performing charge requests
towards the charge@once.
In case the GPRS actions finished and the reserved
money on the application hasnt been used up, Claymore
will perform a Recharge respectively and a Refund
Request to store the not used portion of the money back
in the customers account.

Sleak
used to charge SMS sent by GHP Roamers.
The Sleak Server receives MO-SMS information via
GeoRoam system. The GeoRoam system listens to
SS7 international links for MO-SMS sent by GHP
subscribers. Any traffic that it identifies is forwarded to
Sleak for charging and barring if required.
Sleak doesnt perform any unbarring function.

IN Portal
CS tool used for customer management

INTERFACES
Component A
charge@once
charge@once

charge@once
charge@once
charge@once
charge@once
charge@once
charge@once
charge@once

Component B
Logica SMSC
IP Dispatcher

Protocol

UCP
Payment Plug-in
JAVA/HTTP, SMAF
HTTP/Corba
TopUp@vantage/ Siemens Online
Recharging Gateway Interface
@vantage
SNMP, FTP
Commander
MSC
Nokia INAP
B&R Server
Proprietary Networker
Interface
ORS
FTP
UCS Mediate (CMD) FTP
Barring server (BDS FTP
Server)

Use Cases
Sending of SMS notifications
Address Resolution for:

Application servers linked to IPD

SMAF http for subscriber administration


Voucher Recharging
Operations Data and Fault Management
SS7 interface to the core network
Backup and restore of the database
Collection of ticket data
Hotbilling IF for SMS CDRs
Unbarring of international SMS and barring/unbarring of GPRS-service

INTERFACES
Component A Component B
IP Dispatcher
*Globes Applic ation
Clients (SPS, Blade,
UCP, Velocity, PNS,
GIT
IP Dispatcher
IVR and Sleak)

Protocol
Payment Plug-in
JAVA/HTTP,

Use Cases

Payment Plug-in for Charging, Recharging for external 3rd


party applic ations, Balance Inquiry
SMAF Corba/HTTP
SMAF http for subscriber administration/provisioning
SMAF HTTP/ Payment Balance inquiry and Recharging
Plugin JAVA/HTTP
IP Dispatcher
SMAF & Tariff Tool SMAF CORBA
Servic e and subscriber management (incl. tariff administration)
Baring / Debarring Nokia HLR
Telnet/MML
Receive barring and de-barring information from the charge@once
Server
and send barring/debarring MML commands towards HLR.
SMAF GUI Client charge@once
SMAF
Customer Care

INTERFACES
Interface

Used Software versions

Payment Plug IN

JacORB V2.2.2
java run time environment 1.4.2
or 1.5

SMAF Corba

JacORB V2.2.2

UCP

V3.5

FTP

V8.0

EXTERNAL API

API (application programming interface) will be used


by the external clients to access subscriber data,
provision the accounts or wallets, enables charging,
recharging and etc.

1.

Payment Plugin HTTP (Pay-Http)/JAVA /J2EE


interface (Pay Corba)

2.

SMAF Interface

Payment Plugin HTTP (Pay-Http)/JAVA


/J2EE interface (Pay Corba)
provides a synchronous HTTP-based interface for a web
based application and allows this application to send
requests to the charge@once and can also handle
CORBA communication.
provides the JAVA based API for a non- Web based
External Client while it also support JAVA 2 Enterprise
Edition (J2EE) connector interface to J2EE compliant
servers.

implements two timeout methods to prevent infinite


blocking of the interface called the Response Timed Out
and Confirmation Timed Out.

SMAF Interface

Service Management Access Function (SMAF) is


going to be used by the external 3rd party client of
Globe to do the provisioning of subscribers and
activation/deactivation of subscriptions.

There are 2 types of supported SMAF interfaces:

1.
2.

SMAF HTTP
Batch Interface

SMAF Interface
1.

2.

SMAF HTTP
This interface connects an external client to the SMAF
via internet with the Hypertext Transfer Protocol
(HTTP).
It offers customers the opportunity to create their own
clients.
Batch Interface
This makes it possible to process large numbers of
service management operations offline and
asynchronously.
This makes synchronous dialog interactions between
an external user and the system unnecessary.

CHAPTER 3: SUBSCRIBER LIFE


CYCLE
1.
2.
3.
4.
5.

Pre-active
Active Status
Grace Period
GHP Subscription Expiry
Life Cycle Handling

PRE-ACTIVE
the initial status of the subscriber.
the first access initiates the change of status of a
subscriber from pre-active to active. Following activities
is accepted as first access:
- MOC
- SMS
- Recharging via IVR
- Balance Inquiry (BALI Voice/BALI SMS)
- 3rd Party application requests
- VAS Requests

PRE-ACTIVE
If a subscriber makes his first access on or before the
expiration date of the pre-active status (3019-01-01
00:00:00), his status becomes active and an expiration
date is calculated:
Active Period/1st expiry: current date + 60 days
CreditExpiryPeriod/2nd Expiry: current date + 150 days
Those Recharge initiated by the subscriber either via
223 or 3rd party application (SAL, AMAX, PNS etc.) on
or before the expiration date of the pre-active status the
calculation of the expiration date may vary depending on
reload amount.

PRE-ACTIVE (SubsciberStatus 0)
Since there are several 3rd Party applications that can
trigger the setting of the first access flag, an indicator
flag is added on the SMAF and Plugin messages that
once the request is received by the charge@once, it
determines if the request from the 3rd party application
should initiate the setting of the first access flag.

ACTIVE STATUS (SubsciberStatus 1)


Main status of the subscriber.

starts after the subscribers first access till the defined


Credit Expiry date.
When the subscriber is in this period all activities are
allowed.
On every recharge, a new expiration date is reassess.
The used recharging channel and denomination value
will be dictating the expiry date that will be
compared against the previous expiry date before the
top up. Whichever is the longest expiry date, this will be
the one taken into account.

GRACE PERIOD (SubsciberStatus 3/4)


After the Credit Expiration date (1st expiry date) is
passed.
The balance remaining on the subscribers main account
is zeroed out. Sub accounts such as Free SMS and
Wallets will be kept.
This status allows subscriber only with a limited set of
activities.

When a subscriber does a recharging, he gets into active


status again and a new expiration date is calculated.
Subscriber is able to make use of his sub accounts (i.e.
Free SMS and Wallets) again.

GHP SUBSCRIPTION EXPIRY


(SubsciberStatus 5)
This is the phase where subscriber is locked from using
the services.
Normally the 2nd expiry date is set based on the credit
expiry date (+ grace period).

Pre-active (0)

First access
Active (1)
(MOC, SMS-MO,
MTC,SMS-MT, Recharge)

Near Credit Expiry (2)

Active phase

(MOC, SMS-MO,
MTC,SMS-MT, Recharge)

Successful
recharging
Credit Expiry (3)
(MOC Free Calls,MTC,
SMS-MT, Recharge)

Grace period phase


Near GHP Subscription
Expiry (4)

Not activated
after x days

(MOC Free Calls,MTC,


SMS-MT, Recharge)

GHP Subscription
Expiry (5)
(Locked/ deletion)

SUBSCRIBER LIFE CYCLE

LIFE CYCLE HANDLING


Subscriber can access emergency numbers at
whichever state he is except locked state.
Free access numbers is only accessible by subscribers
who are on Active and Grace Period state.
The life cycle of Globe Handyphone subscribers are
supervised online.
The status of subscribers can change either as a result
of some activities in the service (On-Touch) or as a result
of time (Periodic Activities/DBA). For every status
change, the resulting new status flag is defined.

LIFE CYCLE HANDLING


Periodic Activities/DBA

This application is started once every 24 hours to


check if the subscribers state has to be changed
according to the number of days the state continues.

This is for the case the no service is initiated by the


subscriber within the day.

Whenever the subscriber status is changed, the data


of the subscriber will be written into a confirmation
ticket.

When the active period ends, the main account has to


be set to 0 and a confirmation ticket is written.

CHAPTER 4: GHP SERVICES


1.
2.
3.
4.

Default Services
Subscription-Based Services
Wallet-Based Services
Checkers/VPN Group

DEFAULT SERVICES
1.

PrepaidGHP

the default base Prepaid IN Service for GHP


subscribers. The service provides online rating and
charging for Voice/Data services and is provisioned to
all GHP subscribers.

Service Offerings:
Special IDD Rates
Eagle and Rescue
BALI (Balance Inquiry via Voice)

DEFAULT SERVICES
2.

Bali (Balance Inquiry delivered thru SMS)

Bali service provides the balance checking capability


to all GHP subscribers.

Subscribers can access the BALI service in 2 ways,


either by sending SMS to the access no. 222 or via
calling the number 222.

Both methods trigger charge@once to send an SMS


notification to the SMSC via UCP with the current
balance of the main account, FreeSMS counter and
expiration date of the subscriber.

DEFAULT SERVICES
3.

Short Message Service Online Charging (SMSOLC)

the default SMS based Prepaid IN Service for GHP


subscribers inside Globe.

the service provides tariffs for SMS accessed by all


GHP subscribers.

FreeSMS Counter - a bonus account that is credited after


Topups have been made based on certain values from
certain channels.

DEFAULT SERVICES
2 Types of SMS VAS Transactions:
1.

2.

Mobile Originated Value Added Services (MO-VAS)


This service cover such things as ringtone downloads,
screen savers, news, etc.
Any value added service that is charged based on the
MO-SM sent by the subscriber is considered an MOVAS service.
Mobile Terminated Value Added Services (MT-VAS)
This is used for the charging of VAS services based on
the successful delivery of the service to the subscriber.
A subscriber sending a MO-SM to the SMSC
application activates MT-VAS services. The SMSC
application then sends the MT-VAS service to the
subscriber.

SUBSCRIPTION-BASED SERVICES
uses main account.
offer special limited-time promotions based on certain
criteria i.e. call type, B-Number prefix.
GHP subscribers activate these subscriptions by sending
text messages to Globe SMS gateways like New Frontier
thru access number 8888.
these gateways uses charge@once APIs to
activate/deactivate the subscription.

the gateways also charge the subscribers main account


for the subscription.

SUBSCRIPTION-BASED SERVICES
Project Name
Cheetos
Barricade2
Doritos
Barricade
Piattos
Piattos
Madagascar

Service Name
Unlitxt/Supertxt
SuperUnli
NA
SuperDuo
UnliDaytime
UnliNighttime
NA

Subscription
Cheetos
Barricade2
Doritos
Longshot
Piattos_DayTime
Piattos_NighTime
Madagascar

Description
Unli intra SMS service
Unli intra SMS/Voice service
Unli intra SMS service from 8AM to 8PM
bundled unli intra voice + Duo
Unli intra SMS service from XXXH to yyyyH
Unli intra SMS service from XXXH to yyyyH
unlimited IDD to US/Canada from 10PM to 6AM

WALLET-BASED SERVICES
Wallet based subscriptions are service offerings that are
similar to subscriptions except that they use a dedicated
accounts called Wallet.
The criteria for activating a wallet during a voice or SMS
call are also based on similar criteria for subscriptions.
As per subscriptions wallets are also activated by GHP
subscribers sending an activation text message to Globe
SMS gateways. These gateways use IN Platform APIs
to activate the account.
A total of fourteen wallets were created. A subscriber can
activate 14 wallet subscriptions at one time.

WALLET-BASED SERVICES
Project Name Service Name
Fondue
Immortaltxt
Sulitxt
Gattaca
ITXT
Valley
Unyt
Fondue
ImmortalCall
Russia2
Suki IDD20
Kalahari
Etxt
Kalahari/Monte TxtOther/Etxt (inter)
Russia2
Suki IDD30

Wallet
Wallet1_SMS
Wallet2_SMS
Wallet3_iSMS
NSWallet1_Voice
Wallet2_Voice
Wallet3_Voice
Wallet4_SMS
Wallet5_SMS
Wallet4_Voice

Description
intra sms w/ no expiry; inter sms are credited in free SMS account
100 intra sms valid for 24 hours
International SMS wallet service
unlimited intra voice from 10PM to 6AM
intra voice wallets w/out expiry
IDD voice wallets to US/Canada/HK/Singapore/Taiwan
intra and inter SMS wallet
inter SMS wallet
IDD voice wallets to Kuwati/SA/UAE

CHECKERS/VPN GROUPS
provides VPN functionality to Globe Handy Phone
Subscribers (GHP) who are part of Corporate
Organisation.
Checkers subscription is consist of Group ID and Class
ID. Group ID essentially equates to a company or large
organisation. Checkers also provides the option for
subscribers to join up to 3 groups/companies.
Class ID provides the ability to segment Group members
into sub-groups. This provides extra functionality for intra
Group calls, allowing different tariffs to be applied. Each
group can have up to 5 Classes.

CHAPTER 5: BASIC
TROUBLESHOOTING
1.
2.
3.
4.
5.
6.

SEP
IPD
BDS
Backup and Restore Server
CMD
IVR

THANK YOU!!!

Das könnte Ihnen auch gefallen