NSN in Orientation

8/10/2019 NSN in Orientation

1/81

Intelligent Networks and Value-Added Services

NSN-IN ORIENTATION


2/81

COURSE OUTLINE

CHAPTER 1: CALL FLOWS

CHAPTER 2: OVERVIEW

CHAPTER 3: SUBSCRIBER LIFE CYCLECHAPTER 4: GHP SERVICES

CHAPTER 5: BASIC TROUBLESHOOTING


3/81

CHAPTER 1: CALL FLOWS

1. Normal GSM Call Flow

2. Prepaid GSM Call Flow

3. SMS Charging Flow

4. SMS-MT VAS (Hotbilling) Charging Flow5. SMS-MT VAS CSP Charging Flow


4/81

NORMAL GSM CALL FLOW

Sub A

Sub B

SS7

SS7

1

2

1

2

3

4

Sub A attempts to call Sub B

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

3


5/81

PREPAID GSM CALL FLOW

Sub A

Sub B

SS7 SS7

SS7

1

2

4

1

2

3

4

SS73

6

5

3

4

Sub A attempts to call Sub B

MSC checks prepaid balance in IN

IN confirms balance and allows the call

MSC checks Subs B status in HLR

HLR gives the location area of Sub B

MSC connects to Sub B


6/81

SMS CHARGING FLOW

Sub A

SS7 SS7

SS7

1

2

3

4

1

2

3

4

5

6

5

6

7

7

Sub Asends SMS to Sub B


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 Areceived Message Sent


7/81

SMS-MT VAS (HOTBILLING)

CHARGING FLOW

Sub A

SS7 SS7

SS7

1

2

3

41

2

3

4

5

7

5

7

8

8

Sub Asends SMS to request for VAS




SMSC stores SMS and acknowledges to Sub

SMSC creates log (charging file) and send to CMD

CMD joins the CDR files and transfers it to IN for charging.

CMDTCP/IP

TCP/IP

6 MSC requests IN to charge SMS (0 charge

since MT)

6


8/81

SMS MT VAS (CSP) CHARGING FLOW

Blade

Sub A

SS7 SS7

SS7

1

2

3

4

1

2

3

4

10

6

6

8

7

Sub Asends SMS to request for VAS




SMSC sends request to BladeBlade then sends the request to the CP for the content, CP sends

back the content to CSP

TCP/IP

TCP/IP

5 MSC requests IN to charge SMS (0 charge since

blade is doing the charging)

5

8 Blade charges sub balance in IN

CP

Blade 79

9 Blade request SMSC to deliver to sub

10 SMSC delivers to sub


9/81

CHAPTER 2: OVERVIEW

1. Charge@Once Component

2. Software Architecture

3. Network Architecture

4. 3rd

Party Applications5. Interfaces

6. External API


10/81

CHARGE@ONCE COMPONENT

Within the charge@once system, the rating data hasbeen organized into three levels of hierarchy for ease ofadministration and deployment of tariffs.

ContractAt the highest level which will define the commonproperties to be used across various products/accesstypes.

Product levels

define the type of access or type subscriptions whichinfluence the rating engine.

Tariff Model

lowest level of hierarchy. This is the level at which theexact tariffs for a call are defined.


11/81

Contract (Level 1)

A contract includes all properties agreed on duringsubscription.

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 whichcan be used by the subscriber.

The contract level has several tariff / rating data whichare common across various products.


12/81

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.


13/81

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 ofservice.

A product also represents subscription packages which

can be used by the subscriber.


14/81

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 tariffsand/or tariff models).

Subscription packages configurations

Discount Modifier Options

Periodic Options


15/81

Product (Level 2)


16/81

Tariff Model (Level 3)

defines the actual E-parameters or the cost of the

products.

charge@once can support up to 10 different tariff modelsper product. As it is possible to define 10 different tariff

models it is possible to offer 10 different rates for the

same call.


17/81

SOFTWARE ARCHITECTURE

The core functionality of the charge@once is to providereal time rating and charging of different products and or

services.

Charge@Once Solution Architecture


18/81

RATING LOGIC/ENGINE

responsible for the execution of rating.


19/81

CHARGING LOGIC/ENGINE

is the heart of the charge@once

does the processing of charging and recharging requestscoming from the different Service Logics

interacts with the Rating engine for all rating relatedoperations by calling the Rating engine at the start of asessions and at appropriate points during the sessions.

receives tariff information for the execution of charging

Calculates quota sizes (time, volume, price) to begranted.


20/81

CHARGING LOGIC/ENGINE

calculates charges at intermediate points duringsessions 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 theaccounts, updates bonus accounts and accumulatoraccounts or usage counters).


21/81

SERVICE LOGIC

responsible for call and session control.

provide the necessary functionality to trigger theservices, protocol handling, and the typical servicedependent features such as user interactive dialogue,announcements, etc.

hide protocol and service dependencies from rating andcharging.

forwards the charging requests to the Charging Logic.

receives charging responses from the Charging Logicand return the respective results to the underlyingnetwork elements (including the respective error

handling).


22/81

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


23/81

BALANCE LOGIC/MANAGEMENT

responsible for the access to accounts of prepaidsubscribers, as well as the respective storagetransactions.

interacts with Charging Logic for all account relatedtransactions for the execution of charging.

includes the Balancing Function which supports variousaccount types such as monetary accounts. All accountsare controlled and managed in real-time.

is accessed by the Charging Logic and performs allaccount related operations such as read, charge,recharge and reserve operations, and thresholdsupervision to avoid negative balances.


24/81

S

iemensAG,December2005

Charging

Logic Charging Profile

Balance

Management

20001

1000

Balance

2

AccountKey

InternalAPI Rater

Rate Plan

1

Contract ID

Rate Type

Tariff ID

2

8

Return

success

or failure

4Price, Tariff Parameters,

Charging Profile ID

Mapping

to Rate Plan

3

Reference to

Charging Profile5

6Reserve, charge,

recharge and read

7Return result

Internal Inter-working of the logics


25/81

NETWORK ARCHITECTURE

IPD Routing Node 1 IPD Routing Node 2

...IPD Routing Node x

IPD Load Balancer

IPD Group

SEP Node 1 SEP Node 2

Charge@Once Select PlatformAdvantage

Commander

(Adcom)

Backup and RestoreServer (B&R)

Bar/Debar Server(BDS)

RGW

VDS

IVRAMAX CSP Frontier Eagle

3rdParty Clients

CMD

CMG/SMSCCMG/SMSC

CMG/SMSC


26/81

SEP (SERVICE EXECUTION POINT)

6 Charge@Once Platforms (2 PFs in Aurora site

and 4 in Valero site).

7thc@o platform ready for service by July located in San

Juan site.

Each platform is composed of 2 SEP in load-sharingmode.

Hardware Specs: SUN E6900 server


27/81

SEP (SERVICE EXECUTION POINT)

The core NE of an @vantage platform, providing allfunctions required to execute IN services.

The @vantage SEP corresponds to the SCP of the INworld.

SCP (Service Control Point)

Core @vantage component controlling the execution ofthe service logics.

It is usually triggered by the SSP (Service Switching

Point) using the appropriate INAP (Intelligent NetworkApplication Part) operation.

It determines the destination number according to theactive RT (Routing Tree) and sends the answer to theSSP.

Controls registration and billing of calls.


28/81

IPD (IP DISPATCHER)

IPD will serve as a mediation device between thecharge@once and 3rd party applications.

It will do a proper routing of request and response to the

target charge@once platform.

IPDgrp14 IPD routing nodes (ipdp1 to ipdp4)

IPDgrp22 IPD routing nodes (ipdp5 to ipdp6)

IPDgrp34 IPD routing nodes (ipdp7 to ipdp10)IPDgrp42 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.


29/81

RGW (RECHARGE GATEWAY)

Since Charge@once SEP is using a standard platforminterface which VDS cannot understand, RGW mediatesthis charge@once messages towards the VDS during223 inquiry and recharge.

RGW is just a temporary element until such time that wefully 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


30/81

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


31/81


Service such as Roaming SMS MO are not charged in areal time mode but based on hot billing mechanismshence the need to bar these services on the HLR if asubscribers account balance goes below a certain

threshold Debaring of this service will be triggered after a rechargeestablishing enough money to allow the usage of theseservices to be operated in a hot billing mode.

Roaming SMS-MO Threshold = Php25

MMS Threshold = Php15


32/81


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.


33/81

B&R (BACKUP AND RESTORE

SERVER)

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

The @vantage-platform-based data is backed up atregular intervals to ensure a rapid restore of data whendata loss occurs. All data are restorable up to the point intime the failure occurs.

Hardware Specs: SUNFIRE V440 server w/ Storedge C4

B&R1backups IN1 and IN2 and located in Aurora.

B&R2backups IN3 and IN4 and located in Valero.

B&R3backups IN5 and IN6 and located in Valero.


34/81

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


35/81

ADCOM (ADVANTAGE COMMANDER)

Adcom has the following management functions:

1. Configuration management

2. Fault Management

3. Performance Monitoring

4. Security Management


36/81

CMD (CHARGE@ONCE MEDIATE)

collects the raw CDR files from the SMSCs via NFS.

Convert the raw SMSC CDRs from binary format tocomma-separated values (CSV) format.

Filter out the invalid CDRs.

Segregate the valid CDRs into Postpaid subscribersCDRs, TM subscribers CDRs and GHP Prepaid

subscribers MT VAS CDRs.

Hardware Specs:

HP RX2660 Server


37/81

CMD (CHARGE@ONCE MEDIATE)

Transfers the segregated CDRs to its respectiverecipients, namely;

1. Customer Care Billing System for postpaid

subscribers CDRs2. Ericsson Billing Gateway for TM subscriberss CDRs

3. Charge@Once SEPs for Globe Handy Phone prepaidsubscribers CDRs.

There are 2 CMDs in load-sharing mode located inAurora site.


38/81

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


39/81

3RDPARTY APPLICATIONS

NTG-MAINTAINED

1. IVR

2. Eagle

3. Claymore4. SLEAK

5. IN Portal

ISG-MAINTAINED

1. Amax

2. Santa

3. Fun and Fun2

4. PNS/INM5. CSP

6. SAL

7. New Frontier


40/81

3rdParty Clients IPD Distribution

IPD1 IPD2 IPD3 IPD4 IPD6

(ipdp1/ ipdp2/

ipdp3/ ipdp4)

(ipdp5/ ipdp6) (ipdp7/ ipdp8/

ipdp9/

ipdp10)

(ipd11/ ipdp12) (ipdp13/ipdp14/i

pdp15/ipdp1

6)

AMAX Amaretto CSP Amaretto

IVR SAL

Eagle New Frontier

SASN/OLG Trigger

Sleak Russia

INM Claymore

Fun

PNS

IN Portal


41/81

AutoloadMax (AMAX)

enables voucherless based recharging to GHPsubscribers via AutoloadMax distributor.

These distributors are typically shop keepers who resellrecharge to AMAX customers (GHP subscribers).

AMAX Distributors communicate to the AMAXapplication via a SIM based application which containsverification information. The AMAX application alsocontains a monetary wallet for each distributor which isused to recharge GHP subscribers accounts.

Charge@once doesnt have any visibility of the AMAXwallet. This information is part of the AMAX database.


42/81

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.


43/81

FUN

FUN

extension of expiry of Roaming subs

FUN2 activates and deactivates the Prepaid Roaming

subscription.


44/81

PNS/INM

This application client support voucher based recharging

via an ATM machine.


45/81

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.


46/81

SAL (Share-a-Load)

provides GHP subscribers the means of transferring

credit from there main account to other GHP

subscribers.


47/81

New Frontier

activates/deactivates time-based and wallet-based

subscriptions.


48/81

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.


49/81

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#)


50/81


51/81


52/81

IN Portal

CS tool used for customer management


53/81

INTERFACES

Component A Component B Protocol Use Cases

charge@once Logica SMSC UCP Sending of SMS notifications

charge@onc e TopUp@vantage/

Recharging Gateway

Siemens Online

Interface

Voucher Recharging

charge@once @vantage

Commander

SNMP, FTP Operations Data and Fault Management

charge@once MSC Nokia INAP SS7 interface to the core network

charge@once B&R Server Proprietary Networker

Interface

Backup and restore of the database

charge@once ORS FTP Collection of ticket data

charge@once UCS Mediate (CMD) FTP Hotbilling IF for SMS CDRs

charge@once Barring server (BDS

Server)

FTP Unbarring of international SMS and barring/unbarring of GPRS-service

Address Resolution for:

Applicat ion servers linked to IPD

SMAF http for subscriber administration

charge@once IP Dispatcher Payment Plug-in

JAVA/HTTP, SMAF

HTTP/Corba


54/81

INTERFACES

Component A Component B Protocol Use Cases

Payment Plug-in

JAVA/HTTP, Payment Plug-in for Charging, Recharging for external 3rd

party applications, Balance Inquiry

SMAF Corba/HTTP SMAF http for subscriber administration/provisioning

IP Dispatcher IVR SMAF HTTP/ Payment

Plugin JAVA/HTTP

Balance inquiry and Recharging

IP Dispatcher SMAF & Tarif f Tool SMAF CORBA Service and subscriber management (incl. tarif f administrat ion)

Baring / Debarring

Server

Nokia HLR Telnet /MML Receive barring and de-barring informat ion from the charge@once

and send barring/debarring MML commands towards HLR.

SMAF GUI Client charge@once SMAF Customer Care

IP Dispatcher *Globes Application

Clients (SPS, Blade,

UCP, Velocity, PNS,


55/81

INTERFACES

Interface Used Software versions

Payment Plug IN JacORB V2.2.2java run time environment 1.4.2

or 1.5

SMAF Corba JacORB V2.2.2

UCP V3.5

FTP V8.0


56/81

EXTERNAL API

API (application programming interface) will be usedby the external clients to access subscriber data,provision the accounts or wallets, enables charging,recharging and etc.

1. Payment Plugin HTTP (Pay-Http)/JAVA /J2EEinterface (Pay Corba)

2. SMAF Interface

P t Pl i HTTP (P Htt )/JAVA


57/81

Payment Plugin HTTP (Pay-Http)/JAVA

/J2EE interface (Pay Corba)

provides a synchronous HTTP-based interface for a webbased application and allows this application to sendrequests to the charge@once and can also handleCORBA communication.

provides the JAVA based API for a non- Web basedExternal Client while it also support JAVA 2 EnterpriseEdition (J2EE) connector interface to J2EE compliantservers.

implements two timeout methods to prevent infiniteblocking of the interface called the Response Timed Outand Confirmation Timed Out.


58/81

SMAF Interface

Service Management Access Function (SMAF) isgoing to be used by the external 3rd party client ofGlobe to do the provisioning of subscribers andactivation/deactivation of subscriptions.

There are 2 types of supported SMAF interfaces:

1. SMAF HTTP

2. Batch Interface


59/81

SMAF Interface

1. 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.

2. Batch Interface

This makes it possible to process large numbers of

service management operations offline andasynchronously.

This makes synchronous dialog interactions betweenan external user and the system unnecessary.


60/81


61/81

PRE-ACTIVE

the initial status of the subscriber.

the first access initiates the change of status of asubscriber from pre-active to active. Following activitiesis accepted as first access:

- MOC

- SMS

- Recharging via IVR

- Balance Inquiry (BALI Voice/BALI SMS)- 3rd Party application requests

- VAS Requests


62/81

PRE-ACTIVE

If a subscriber makes his first access on or before theexpiration date of the pre-active status (3019-01-0100:00:00), his status becomes active and an expirationdate is calculated:

Active Period/1st expiry: current date + 60 days

CreditExpiryPeriod/2nd Expiry: current date + 150 days

Those Recharge initiated by the subscriber either via223 or 3rd party application (SAL, AMAX, PNS etc.) onor before the expiration date of the pre-active status the

calculation of the expiration date may vary depending onreload amount.


63/81

PRE-ACTIVE (SubsciberStatus 0)

Since there are several 3rd Party applications that cantrigger the setting of the first access flag, an indicatorflag is added on the SMAF and Plugin messages thatonce the request is received by the charge@once, itdetermines if the request from the 3rd party application

should initiate the setting of the first access flag.


64/81

ACTIVE STATUS (SubsciberStatus 1)

Main status of the subscriber.

starts after the subscribers first access till the definedCredit Expiry date.

When the subscriber is in this period all activities areallowed.

On every recharge, a new expiration date is reassess.

The used recharging channel and denomination valuewill be dictating the expiry date that will becompared against the previous expiry date before thetop up. Whichever is the longest expiry date, this will bethe one taken into account.


65/81

GRACE PERIOD (SubsciberStatus 3/4)

After the Credit Expiration date (1st expiry date) ispassed.

The balance remaining on the subscribers main accountis zeroed out. Sub accounts such as Free SMS and

Wallets will be kept.

This status allows subscriber only with a limited set ofactivities.

When a subscriber does a recharging, he gets into activestatus 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


66/81

GHP SUBSCRIPTION EXPIRY

(SubsciberStatus 5)

This is the phase where subscriber is locked from usingthe services.

Normally the 2nd expiry date is set based on the credit

expiry date (+ grace period).


67/81

Near Credit Expiry (2)(MOC, SMS-MO,

MTC,SMS-MT, Recharge)

Credit Expiry (3)(MOC Free Calls,MTC,

SMS-MT, Recharge)

Near GHP Subscription

Expiry (4)

(MOC Free Calls,MTC,

SMS-MT, Recharge)

First access

Successful

recharging

GHP Subscription

Expiry (5)(Locked/ deletion)

Not activated

after x days

Pre-active (0)

Active (1)

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

Active phase

Grace period phase

SUBSCRIBER LIFE CYCLE


68/81

LIFE CYCLE HANDLING

Subscriber can access emergency numbers atwhichever state he is except locked state.

Free access numbers is only accessible by subscriberswho are on Active and Grace Period state.

The life cycle of Globe Handyphone subscribers aresupervised online.

The status of subscribers can change either as a resultof some activities in the service (On-Touch) or as a resultof time (Periodic Activities/DBA). For every statuschange, the resulting new status flag is defined.


69/81

LIFE CYCLE HANDLING

Periodic Activities/DBA

This application is started once every 24 hours tocheck if the subscribers state has to be changedaccording to the number of days the state continues.

This is for the case the no service is initiated by thesubscriber within the day.

Whenever the subscriber status is changed, the dataof the subscriber will be written into a confirmationticket.

When the active period ends, the main account has tobe set to 0 and a confirmation ticket is written.


70/81

CHAPTER 4: GHP SERVICES

1. Default Services

2. Subscription-Based Services

3. Wallet-Based Services

4. Checkers/VPN Group


71/81

DEFAULT SERVICES

1. PrepaidGHP

the default base Prepaid IN Service for GHPsubscribers. The service provides online rating and

charging for Voice/Data services and is provisioned toall GHP subscribers.

Service Offerings:

- Special IDD Rates- Eagle and Rescue

- BALI (Balance Inquiry via Voice)


72/81

DEFAULT SERVICES

2. Bali (Balance Inquiry delivered thru SMS)

Bali service provides the balance checking capabilityto all GHP subscribers.

Subscribers can access the BALI service in 2 ways,either by sending SMS to the access no. 222 or viacalling the number 222.

Both methods trigger charge@once to send an SMSnotification to the SMSC via UCP with the currentbalance of the main account, FreeSMS counter andexpiration date of the subscriber.


73/81


74/81

DEFAULT SERVICES

2 Types of SMS VAS Transactions:

1. 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 theMO-SM sent by the subscriber is considered an MO-VAS service.

2. Mobile Terminated Value Added Services (MT-VAS)

This is used for the charging of VAS services based onthe successful delivery of the service to the subscriber.

A subscriber sending a MO-SM to the SMSCapplication activates MT-VAS services. The SMSCapplication then sends the MT-VAS service to the

subscriber.


75/81

SUBSCRIPTION-BASED SERVICES

uses main account.

offer special limited-time promotions based on certaincriteria i.e. call type, B-Number prefix.

GHP subscribers activate these subscriptions by sendingtext messages to Globe SMS gateways like New Frontierthru access number 8888.

these gateways uses charge@once APIs toactivate/deactivate the subscription.

the gateways also charge the subscribers main accountfor the subscription.


76/81

SUBSCRIPTION-BASED SERVICES

Project Name Service Name Subscription Description

Cheetos Unlitxt/Supertxt Cheetos Unli intra SMS service

Barricade2 SuperUnli Barricade2 Unli intra SMS/Voice service

Doritos NA Doritos Unli intra SMS service from 8AM to 8PMBarricade SuperDuo Longshot bundled unli intra voice + Duo

Piattos UnliDaytime Piattos_DayTime Unli intra SMS service from XXXH to yyyyH

Piattos UnliNighttime Piattos_NighTime Unli intra SMS service from XXXH to yyyyH

Madagascar NA Madagascar unlimited IDD to US/Canada from 10PM to 6AM


77/81

WALLET-BASED SERVICES

Wallet based subscriptions are service offerings that aresimilar to subscriptions except that they use a dedicatedaccounts 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 GHPsubscribers sending an activation text message to GlobeSMS gateways. These gateways use IN Platform APIs

to activate the account.

A total of fourteen wallets were created. A subscriber canactivate 14 wallet subscriptions at one time.


78/81

WALLET-BASED SERVICES

Project Name Service Name Wallet Description

Fondue Immortaltxt Wallet1_SMS intra sms w/ no expiry; inter sms are credited in free SMS account

Sulitxt Wallet2_SMS 100 intra sms valid for 24 hours

Gattaca ITXT Wallet3_iSMS International SMS wallet service

Valley Unyt NSWallet1_Voice unlimited intra voice from 10PM to 6AMFondue ImmortalCall Wallet2_Voice intra voice wallets w/out expiry

Russia2 Suki IDD20 Wallet3_Voice IDD voice wallets to US/Canada/HK/Singapore/Taiwan

Kalahari Etxt Wallet4_SMS intra and inter SMS wallet

Kalahari/Monte TxtOther/Etxt (inter) Wallet5_SMS inter SMS wallet

Russia2 Suki IDD30 Wallet4_Voice IDD voice wallets to Kuwati/SA/UAE


79/81

CHECKERS/VPN GROUPS

provides VPN functionality to Globe Handy PhoneSubscribers (GHP) who are part of CorporateOrganisation.

Checkers subscription is consist of Group ID and Class

ID. Group ID essentially equates to a company or largeorganisation. Checkers also provides the option forsubscribers to join up to 3 groups/companies.

Class ID provides the ability to segment Group members

into sub-groups. This provides extra functionality for intraGroup calls, allowing different tariffs to be applied. Eachgroup can have up to 5 Classes.

CHAPTER 5: BASIC


80/81

CHAPTER 5: BASIC

TROUBLESHOOTING

1. SEP

2. IPD

3. BDS

4. Backup and Restore Server

5. CMD

6. IVR


81/81

THANK YOU!!!

Documents

NSN in Orientation