Sie sind auf Seite 1von 16

Local Roaming Number for Inbound

Product Description

This material describing Starhome is for general information purposes and may be modified by Starhome at any
time without notice. This material is the proprietary and/or confidential information of Starhome, and may not be
disclosed, copied or transferred to any third party without Starhome's prior express consent. Starhome, its logo
and service names are registered trademarks or trademarks of Starhome GmbH. All other marks are the property
of their respective holders.
Copyright 2002-2007 Starhome. All rights reserved.

Product Description

Important Notice
This document is delivered subject to the following conditions and
restrictions:

* This document contains proprietary and/or confidential information


belonging to Starhome.

* Any unauthorized reproduction (electronic or mechanical), use, or

disclosure of this material, or any part thereof, is strictly prohibited. The


contents of this document or any part thereof may be used solely for the
purpose for which they are provided.

* This document is intended solely for the use of entities expressly


authorized by Starhome.

* Material describing Starhome is for general information purposes and


may be modified by Starhome at any time without notice.

* The text and graphics are for the purpose of illustration and reference

only. The specifications on which they are based are subject to change
without notice.

* Corporate and individual names and data used in examples herein are
fictitious unless otherwise noted.

* The information disclosed in this document is disclosed on an as is

basis, and Starhome shall not be liable for the accuracy or completeness
thereof.

* The system and the software described in this guide are furnished under

a license and may be used or copied only in accordance with the terms of
this license.

Copyright 2002-2007 Starhome. All rights reserved.


All company and brand products and service names are trademarks or
registered trademarks of their respective holders.

Document name
LRN for Inbound Product Description SHORT V500.doc

Local Roaming Number for Inbound

Page 2

Proprietary and Confidential

Product Description

Table of Contents
Glossary of Terms Used .....................................................................................................................4
1.

Introduction Service Overview...........................................................................................5

2.

Service Background ..................................................................................................................5

2.1

The Challenge ..............................................................................................................................5

2.2

The Solution.................................................................................................................................5
2.2.1
Visited Operator Benefits ...........................................................................................6
2.2.2
VPMN Service benefits Home Operators ..................................................................6
2.2.3
Roamer Benefits...........................................................................................................6

3.

Detailed Service Description..................................................................................................7

3.1

Connectivity .................................................................................................................................7
3.1.1
MSC interface ...............................................................................................................7
3.1.2
Probe Interface .............................................................................................................8
3.1.3
Provisioning Interface..................................................................................................8

3.2

Service
1.1.1
3.2.1
3.2.2

3.3

Mobile Terminated Call Flow...................................................................................................10


3.3.1
Called Party dialed number Notification ................................................................10

3.4

Mobile Terminated SMS Flow..................................................................................................10

3.5

Mobile Originated Call Flow ....................................................................................................10


3.5.1
Mobile Originated Calls - from Home MSISDN .....................................................10
3.5.2
Mobile Originated Calls - from Local Roaming Number ......................................11

3.6

When Roamer is Not Connected to Network.........................................................................11


3.6.1
Release Call - Status of Local Roaming Number ..................................................11

3.7

Number
3.7.1
3.7.2
3.7.3
3.7.4

3.8

Provisioning................................................................................................................................14
3.8.1
Provisioning for Customer Care ..............................................................................14
3.8.2
Customer Care User Interface .................................................................................15
3.8.3
Self Provisioning User Interface...............................................................................15
3.8.4
External Systems Provisioning Interface ...............................................................16

3.9

Communities..............................................................................................................................16

Initial Stage Service Activation.................................................................................8


Service Qualification Process.....................................................................................9
Service Announcement SMS ......................................................................................9
Out-of-Service Announcement SMS .......................................................................10

Allocation Logic ..........................................................................................................11


Local Roaming Number Usage.................................................................................11
Local Roaming Number Lifecycle ............................................................................12
Required Amount of Local Roaming Numbers ......................................................13
End of Reservation Notification ...............................................................................13

3.10 Service Reports ..........................................................................................................................16

Local Roaming Number for Inbound

Page 3

Proprietary and Confidential

Product Description

List of Figures
Figure 1: System Architecture.............................................................................................................7
Figure 2: Service Announcement SMS example ...............................................................................9

Glossary of Terms Used


Term

Meaning

CAMEL

Customized Application For Mobile Network Enhanced Logic

CLI

Calling Line Identification

GMSC

Gateway Mobile Services Switching Center

HLR

Home Location Register

HPMN

Home Public Mobile Network

IN

Intelligent Network

INAP

Intelligent Network Application Protocol

IMSI

International Mobile Subscriber Identification

ISUP

ISDN User Part

LRN

Local Roaming Number

MO

Mobile Originated (Call)

MSC

Mobile Switch Controller

MSISDN

Mobile Subscriber ISDN Number

MSRN

Mobile Station Roaming Number

MT

Mobile Terminated (Call)

SIM

Subscriber Identity Module

SMSC

Short Message Service Center

SOAP

Simple Object Access Protocol

VLR

Visitor Location Register

VPMN

Visited Public Mobile Network

Local Roaming Number for Inbound

Page 4

Proprietary and Confidential

Product Description

1.

Introduction Service Overview


The Local Roaming Number (LRN) service enables VPMNs to provide a local
number to their inbound roamers. Roamers can receive calls on both their
home and new local number.
Frequent travelers pay premium rates for using their mobile phones while
roaming. To reduce their costs, they often purchase local prepaid SIM cards
and in this way can be reached at local call costs. This reduces mobile
terminated (MT) costs and removes the burden of international call expenses
from local contacts.
This situation causes travelers to:

* Carry 2 SIM cards or even 2 mobile handsets


* Replace the SIM in their mobile handset (if not SIM locked) - thus missing
incoming calls on the inactive SIM.

The LRN service offers the benefits of having 2 numbers without the need to
purchase a local prepaid SIM.

2.

Service Background

2.1

The Challenge
Mobile phone users expect their roaming
experience to match their mobile
lifestyles, with easy access to both
services and people anywhere, anytime.
Yet, dialing and receiving calls in visited
networks is usually carried out at
premium rates.
The result is that roamers look for
cheaper methods of using their
handsets. Turning OFF the handset is
one sure way to lower roaming expenses
and rejecting incoming calls is another. Many roamers, traveling frequently
to specific destinations, buy local prepaid cards for roaming in the visited
country. However, when they replace the SIM in their handsets, they become
unavailable via their home network MSISDN, These roamers tend to utilize
two handsets, in order to enable both numbers concurrently.

2.2

The Solution
Starhomes Local Roaming Number service provides roamers with all the
benefits of having a local number without the drawbacks of purchasing an
additional SIM.

Local Roaming Number for Inbound

Page 5

Proprietary and Confidential

Product Description

Inbound roamers, upon registering in the operators network, are


dynamically allocated a local number (MSISDN) to be associated with the
roamers handset while roaming in the network. Roamers can receive calls
both on the original number and on the new local number (free calls).
When originating calls, the roamer can select the CLI with which the call will
be identified with. The MO call can be identified with either the local roaming
number itself or with the home CLI (MSISDN). By adding a prefix before the
destination number, the call is identified with the local roaming number,
without the prefix (PBD), all MO calls are identified with the home MSISDN.
This feature enables the roamer to present a local presence while he is
roaming.
A smart usage-based mechanism reserves the local number for future visits.
Alternatively, the pre-set expiration date can be extended via Customer Care.
Note: The service can be offered with the Winback notification service, to notify your
subscribers when they roam to other networks

2.2.1

Visited Operator Benefits


With the Local Roaming Number service, operators can offer better tariffs
for inbound roamers, which:

*
*
*
*

2.2.2

Attract and retain inbound roamers


Preserve roaming charges for MO calls
Encourage more local network traffic
Offer a competitive advantage in the local market, reducing churn

VPMN Service benefits Home Operators


The Local Roaming Number service will prevent roamers from removing the
home network SIM with the resulting lost revenue (no MT calls, SMS, GPRS,
MMS, VAS, etc.). This service enables roamers to be available on their home
MSISDN and to enjoy all their familiar value added services.

2.2.3

Roamer Benefits
Both local and roaming subscribers will benefit from the following:

* Visitors save money when calling other roaming subscribers via their local
MSISDN

* Provides local presence for frequent travelers by enabling them to be


reached via a local number

* Roamers can make and receive calls via both the home and local numbers
* Avoids the need to separately purchase, maintain and pay for a local
number

* The local number can be reserved for the roamers future visits

Local Roaming Number for Inbound

Page 6

Proprietary and Confidential

Product Description

3.

Detailed Service Description


This section includes a technical description of the signaling flows for Call
Control and SMS traffic, followed by a functional description of other product
features including Service Logic, Billing, Reports, Roamers Provisioning and
Service Counters.

3.1

Connectivity
Figure 1depicts the Local Roaming Number system architecture and
interfaces.

Figure 1: System Architecture

3.1.1

MSC interface
The Local Roaming Number system, based on the IntelliGate Roaming Service
Delivery Platform, can be integrated to the operators network via the GMSC
in one of the following two ways:

* Service Node (ISUP)


* Service Control Function - Intelligent Network (IN)
Based on these two alternative signaling methods, Starhome has developed a
generic technical solution for this service. The final delivered solution <Issue
# from File Properties>must be adjusted to the specific network configuration

Local Roaming Number for Inbound

Page 7

Proprietary and Confidential

Product Description

and parameters including the network size and topology, the traffic volume,
the INAP vendors variant, the CAMEL version - if relevant and the operators
preferences. All these are usually discussed prior to specifying the final
technical solution.
The two signaling options are described below.

3.1.1.1

ISUP
In particular cases, such as non-IN network environment and/or relatively
low inbound roaming traffic, call control is performed using ISUP signaling.
The IntelliGate is connected to the MSC, as call control does not require
connecting the IntelliGate to the network via voice channels, SS7 signaling
links are only used to convey the ISUP signaling. This inter-connection is
achieved by utilizing a Loop-Around technique on the MSC.
Loop-Around: With Loop-Around, every call requires two ports on the MSC.
These ports are connected together (that is the loop) via a cable, to ensure
that there is always a voice path between them. The IntelliGate uses the
ISUP signaling to control the looped-around ports using standard ISUP
messages.

3.1.1.2

Intelligent Network
The IntelliGate controls MO and MT calls delivered to inbound roamers
based on IN architecture. This solution suits networks that are IN-ready
and/or networks that experience relatively high inbound roaming traffic.
Using INAP, call control is performed with a combination of Trigger Detection
Points and Event Detection points.

3.1.2

Probe Interface
Using its SS7 Mobility Probe, the IntelliGate is connected to the operators
international SCCP signaling links in a completely passive mode.
This interface is used to obtain the relevant roamers information and acts as
a triggering point for service activation.

3.1.3

Provisioning Interface
The provisioning interface enables the operator to configure the behavior of
the service, set roamers qualification rules and view basic service status
parameters

3.2

Service Initial Stage Service Activation


The initial state of the service is responsible for the roamers registration and
activation process to the service. This stage includes the following activities:

*
*
*
*

Monitoring roamers update location


Obtaining subscriber information
Service qualification process for each roamer
Announcing service to roamers

Local Roaming Number for Inbound

Page 8

Proprietary and Confidential

Product Description

* Monitoring roamers cancel location and purge messages

1.1.1

Service Qualification Process


After the IntelliGate has detected a Location Update by an inbound roamer,
the qualification process needs to decide whether the inbound roamer is
entitled to the service.
The qualification process will decide if the roamer is allowed to originate and
receive calls on the local number by testing values in the MAP_ISD message.

3.2.1

Service Announcement SMS

Figure 2: Service Announcement SMS example

The Service Announcement SMS promotes the service to inbound roamers


and supplies information about the service. An example of such an
announcement is presented below:
The following capabilities are configurable by the operator:
1. The announcement message can be delayed for a specified amount of time
after registration to the visited network, values are provided in minutes.
2. The announcement supports multiple languages and provides automatic
best- match logic between the home country and the supported
languages, in cases of no match, a default language is activated.
3. The message can include parameter fields that can be replaced with
actual values before sending the message such as:

* Local Roaming Number the allocated LRN

Local Roaming Number for Inbound

Page 9

Proprietary and Confidential

Product Description

3.2.2

Out-of-Service Announcement SMS


The Out-of-Service Announcement SMS enables the operator to alert
inbound roamers, who switched to another network (within the same
country), about the loss of the Local Roaming Number service. The message
may notify the roamers how to switch back to this visited network.

3.3

Mobile Terminated Call Flow


For Mobile-Terminated calls the roamer is available on both MSISDNs, the
home MSISDN and the Local Roaming Number.
Mobile-Terminated calls received on the home MSISDN shall start in the
home network thus charged as normal roaming MT call. On the other hand,
calls received on the local MSISDN (Local Roaming Number) are started in
the visited network (like any other call to a local destination within the
visited network) and thus charged as a local MT within the network. In most
mobile networks (except in North America, Russia and other specific
regions), local mobile terminated calls are free of charge.

3.3.1

Called Party dialed number Notification


The service allows B-Party to know if the caller has used B-Partys Local
Roaming Number for this call or the home MSISDN prior to the call.
NOTE: This feature requires specific network capabilities in order to be
supported

3.4

Mobile Terminated SMS Flow


The service allows the roamer to receive SMS (Mobile Terminated SMS) on
both MSISDNs (home MSISDN and Local Roaming Number).
Mobile-Terminated SMS received on the home MSISDN is charged via regular
roaming charges for MT SMS while roaming. No charges apply for MobileTerminated SMS on the Local Roaming Number (in case no MT SMS charges
apply within the visited network).

3.5

Mobile Originated Call Flow


This section presents the call flow for mobile originated calls. The caller
(inbound roamer) may choose the CLI to be used in the next call, by adding a
prefix to the dialed number.

3.5.1

Mobile Originated Calls - from Home MSISDN


Mobile originated calls from the Home MSISDN have a regular MO call flow
with no changes. The call is first handled by the serving MSC and is then
routed by the dialed number

Local Roaming Number for Inbound

Page 10

Proprietary and Confidential

Product Description

3.5.2

Mobile Originated Calls - from Local Roaming Number


Roamers may want to originate calls and to be identified via their Local
roaming number. In order to present a local CLI to the called party,
roamers may add a predefined prefix before the dialed number and the Local
Roaming Number service shall replace the original home MSISDN number in
the caller ID field to the new local roaming number. No changes to regular
roaming charges are applied to this type of call.

3.6

When Roamer is Not Connected to Network


This section focuses on the service when an inbound roamer is not
connected to the visited network and the allocated number is in the
Reservation Period. The various options outlined below will enhance both
the caller experience and the service to inbound roamers when absent.

3.6.1

Release Call - Status of Local Roaming Number


The network can provide the caller with accurate notification about the
status of the roamer with a local roaming number. If the network fails to
page the roamer, the following will apply:

* During visit and reservation period, the service will release the call with a
subscriber is not available notification release cause.

* During cooling period, the service will release the call with a number is
invalid notification release cause.

3.7

Number Allocation Logic

3.7.1

Local Roaming Number Usage


The system can define different logics (time thresholds) based on the
roamers usage figures. The figures are calculated as average calls (both MO
and MT) per visit-day.
If the local number wasnt used even once, then both reservation and cooling
period values are 0 (zero) and the number is immediately returned to the
pool.
The calculation of usage upper value is based on the following formula:

NumberOfCalls
VisitPeriod
* Accumulated Number of Calls: the accumulated figure of all calls

received and originated with the local roaming number on all visits until
now

* Accumulated Visit Period: the accumulated figure for the total number
of days of all previous visits until now

Local Roaming Number for Inbound

Page 11

Proprietary and Confidential

Product Description

Type

Usage upper
value

Reservation Period
(days)

Cooling Period
(days)

Send end-ofreservation
Notification

Newcomer

0-0.1

No

Minimal

>0.1-1

60

45

No

Silver

>1-5

60

60

No

Gold

>5-10

90

60

Yes

Platinum

>10

90

90

Yes

NOTE: The table includes sample values that are configurable via service
provisioning

3.7.2

Local Roaming Number Lifecycle

Visit Period
Number allocated

Reservation Period
until revisit

Cooling Period until


reallocation

Local Calls Diverted


to Roamer

Network Announcement:

Network Announcement:

Subscriber Unavailable

Invalid Number

Number
reallocated

Roamers who have used the local roaming number will be entitled to longer
reservation and cooling periods than roamers who havent used their
number at all.
As the allocation of local numbers is dynamic, the system may encounter low
availability of local roaming numbers for allocation. In this case, the
following handling method is applied:
1. Yellow alarm will be triggered at 80% allocation
2. Red alarm will be triggered at 100% allocation
3. The system will start reusing numbers in Cooling Period from oldest to
newest
4. After all numbers in Cooling Period have been reused no new numbers
will be allocated and assigned to arriving inbound roamers

3.7.2.1

Visit Period
The visit period is calculated from the first update location monitored within
the visited network until expiration of day after end-of-visit parameter (see
Section 3.7.1).

3.7.2.2

Reservation Period
The reservation period is calculated from end-of-visit until the defined
period of time (in days) for the roamers type (see Section 3.7.1)

Local Roaming Number for Inbound

Page 12

Proprietary and Confidential

Product Description

3.7.2.3

Cooling Period
The cooling period is calculated from the end of the reservation period until
the defined period of time (in days) for the roamers type (see Section 3.7.1)

3.7.3

Required Amount of Local Roaming Numbers


This section explains how to calculate the required amount of local roaming
numbers in a network as a function of the number of inbound roamers:
Parameter Name

Meaning

CIR

Number of concurrent inbound roamers

AVD

Average visit duration in days

DUE

Days until end-of-visit number of days since last update-location until the system
decides that the roamer has ended the visit

ULR

Used LRN rate the percentage of roamer who have used (MO or MT) their Local
Roaming Number

RSP

Reservation Period

CLP

Cooling Period

Number of local roaming numbers for first visit periods:

(CIR / DUE ) ( AVD + DUE )


Number of allocated local roaming numbers for reservation and cooling
periods:

((CIR / DUE ) ULR ) (RSP + CLP )


Total required Local Roaming Numbers:

(CIR / DUE ) ( AVD + DUE ) + ((CIR / DUE ) ULR ) (RSP + CLP )


Below is a simplified example for the calculation of maximum allocation
(all platinum roamers):

*
*
*
*
*
*

CIR
AVD
DUE
ULR
RSP
CLP

=10,000 concurrent roamers


= 4 days
= 2 days
= 0.05 (5%)
= 90 days
= 90 days

(10000 / 4) (4 + 2) + ((10000 / 4) 0.05) (90 + 90)

= 37,500 local roaming numbers required

3.7.4

End of Reservation Notification


the operator sends an automated notification to a former inbound roamer
notifying about the reservation period expiration. The message may include

Local Roaming Number for Inbound

Page 13

Proprietary and Confidential

Product Description

instructions to call Customer Care and extend the reservation period or


instructions for self provisioning of the reservation period.

3.8

Provisioning
The service provisioning interface enables service configuration and self
provisioning for inbound roamers.

3.8.1

Provisioning for Customer Care


This section presents the provisioning capabilities available to Customer
Care representatives

3.8.1.1

Local Roaming Number recovery


This function retrieves the last roaming number for a roamer.
The response returns details such as:
1. Last allocation date (or last date in-use)
2. The home MSISDN the number was last allocated to
3. Number current allocation status: in-use, reserved, cooling and free
4. Days until end of current status period (free=unlimited)
5. Number was used by roamer: Yes/No

3.8.1.2

Reservation Period Query


This function retrieves the number of days until end of reservation period by
the roamers Home MSISDN or Local Roaming Number. The function also
returns the number of days in the cooling period for the roamer. Both values
- reservation and cooling - are based on the roamers type (see Section 3.7.1)

3.8.1.3

Reservation Period Extension


This function enables Customer Care representatives to extend the
reservation period for a roamer.
The extension values are provided in days. A (-1) value represents an
unlimited extension and this is effectively a permanent allocation of a local
roaming number to an inbound roamer.

3.8.1.4

Exclusion of Roamer from Service


An inbound roamer may contact Customer Care and ask to be permanently
excluded from the service or for the current visit.

3.8.1.5

View List of Roamers Excluded from Service


This function provides a list of all the excluded-by-request roamers.

Local Roaming Number for Inbound

Page 14

Proprietary and Confidential

Product Description

3.8.1.6

Renew Local Roaming Number for Roamer


This function allocates a new local roaming number for a roamer through
the home MSISDN.
This function can be used after a roamer has requested to be excluded from
the service (remove the roamer from excluded list).
This function can be used when the roamer requests that the current local
roaming number be replaced. The previous local roaming number, if used,
starts a Cooling period before being returned to the available pool. If the
previous local roaming number was not used, then it can immediately be
returned to the available local roaming number pool.

3.8.2

Customer Care User Interface


This is a web-based interface that enables Customer Care personnel to
control the provisioning functions, (see Section 3.8.1).

3.8.2.1

Local Roaming Number Recovery


This function enables inbound roamers to recover the last local roaming
number allocated for the home MSISDN.

3.8.2.2

Reservation Period Query


This function enables inbound roamers to query how many days are left for
their reservation period.
NOTE: Roamers may query their reservation period from any network (not only from
the VPMN)

3.8.3

Self Provisioning User Interface


This section presents the possibilities of self provisioning for the roamer
without the need to contact the local Customer Care representatives.
This interface can be WAP or Web-based for self provisioning that will enable
roamers to set all their settings.
The authentication is performed via a username (home MSISDN) and
password login.
The password is provided, on-the-fly, via SMS to the home MSISDN.
The WAP user interface may be integrated into Starhomes Roaming Mate
service for inbound roamers.
Note: Starhome can offer SMS and USSD interfaces for the self provisioning
interface to address market segments where these access methods are
deemed more acceptable.

Local Roaming Number for Inbound

Page 15

Proprietary and Confidential

Product Description

3.8.4

External Systems Provisioning Interface


This is a Simple Object Access Protocol (SOAP) based interface that allows
connectivity of the service to existing CRM systems and other provisioning
systems.

3.9

Communities
As the service is provided to inbound roamers, the system does not have any
prior information about the roamers. Inbound roamers are categorized into
automatic communities by their roaming profile.
An example of such automatic communities may be: specific HPMN
community, CAMEL subscriber community, IMSI range community, etc.

3.10

Service Reports
The service accumulates traffic data and details that can be used to analyze
the service behavior and usage.
The data provided by the service supports generating reports like: usage
reports by usage type (silver, gold, etc.) or distribution of usage between
HPMNs, etc.

Local Roaming Number for Inbound

Page 16

Proprietary and Confidential

Das könnte Ihnen auch gefallen