7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 1/38
This material describing Starhome is for general information purposes and may be modified by Starhome at anytime without notice. This material is the proprietary and/or confidential information of Starhome, and may not bedisclosed, copied or transferred to any third party without Starhome's prior express consent. Starhome, its logoand service names are registered trademarks or trademarks of Starhome GmbH. All other marks are the propertyof their respective holders.
© Copyright 2002-2007 Starhome. All rights reserved.
Local Roaming Number TM
Solution
Product Description
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 2/38
Product Description
Local Roaming Number Page 2 Proprietary and Confidential
Important Notice This document is delivered subject to the following conditions andrestrictions:
* This document contains proprietary and/or confidential informationbelonging to Starhome.
* Any unauthorized reproduction (electronic or mechanical), use, ordisclosure of this material, or any part thereof, is strictly prohibited. Thecontents of this document or any part thereof may be used solely for thepurpose for which they are provided.
* This document is intended solely for the use of entities expresslyauthorized by Starhome.
* Material describing Starhome is for general information purposes andmay 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 changewithout notice.
* Corporate and individual names and data used in examples herein arefictitious 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 completenessthereof.
* The system and the software described in this guide are furnished undera license and may be used or copied only in accordance with the terms ofthis license.
Copyright ©2002-2007 Starhome. All rights reserved.
All company and brand products and service names are trademarks orregistered trademarks of their respective holders.
Document name
LRN Product Description LONG V500.doc
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 3/38
Product Description
Local Roaming Number Page 3 Proprietary and Confidential
Table of Contents
Glossary of Terms Used ........................................... ................................................... ..........................6
1. Introduction – Service Overview ......................................... .................................................... ...7
2. Service Background ............................................... ................................................... ..................7
2.1 The Challenge................................................................................................................................7
2.2 The Solution .................................. .................................................. ...............................................8 2.2.1 Visited Operator Benefits................................................................................................8 2.2.2 Benefits to Home Operators ........................................ ................................................... 8 2.2.3 Roamer Benefits ......................................... .................................................. ..................8
3. Detailed Technical Description...................................................................................................9
3.1 Connectivity....................................................................................................................................9 3.1.1 MSC interface ............................................. .................................................. ................10 3.1.2 Probe Interface ........................................... .................................................. ................11 3.1.3 Provisioning Interface .......................................... ................................................. ........11 3.1.4 Prepaid System Interface – Optional............................................................................11
3.2 Prepaid Service Setup – Prepaid Option ........................................ .............................................12
3.3 Service Initial Stage – Service Activation.....................................................................................12 3.3.1 Service Qualification Process.......................................................................................13 3.3.2 Service Announcement SMS........................................................................................15
3.4 Active Profile Selection – optional........................................... .................................................. ...16
3.5 Mobile Terminated Call Flow........................................................................................................17
3.5.1 Called Party Notification ............................................ ................................................... 17 3.5.2 Mobile Terminated Calls - Billing ............................................. .....................................18
3.6 Mobile Terminated SMS Flow ......................................... ..................................................... ........18 3.6.1 Mobile Terminated SMS - Billing ............................................. .....................................18
3.7 Mobile Originated Call Flow ...................................... ................................................... ................19 3.7.1 Caller Line Identification (CLI) replacement mode .................................... ...................19 3.7.2 Mobile Originated Calls - with Home MSISDN.......................................... ...................20 3.7.3 Mobile Originated Calls - Billing....................................................................................21
3.8 Mobile Originated SMS Flow........................................................................................................22 3.8.1 Mobile Originated SMS - Billing....................................................................................23
3.9 Number Allocation Logic ........................................... ................................................... ................23
3.9.1 Local Roaming Number Usage ......................................... ...........................................23 3.9.2 Local Roaming Number Lifecycle.................................................................................24 3.9.3 Required Amount of Local Roaming Numbers.............................................................25 3.9.4 End of Reservation Notification ....................................... .............................................26
3.10 MT Calls Handling when Roamer is Not Connected to Network ...................................... ...........26 3.10.1 Release Call - Status of Local Roaming Number.........................................................26 3.10.2 Optional: Send “Missed Call Notification” SMS ......................................... ...................26
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 4/38
Product Description
Local Roaming Number Page 4 Proprietary and Confidential
3.10.3 Optional: Divert Calls to Home MSISDN........................................... ...........................26
3.11 Out-of-Serving Notification ........................................ ................................................... ................27
3.12 Provisioning..................................................................................................................................27
3.12.1 Provisioning for Customer Care ........................................ ...........................................27 3.12.2 Customer Care User Interface......................................................................................29 3.12.3 External Systems Provisioning Interface ........................................... ...........................29
3.13 Billing Processes..........................................................................................................................30 3.13.1 Billing Process for Mobile-Originated CDRs.................................................................30 3.13.2 Billing Process for Mobile-Terminated CDRs.................................... ...........................30
3.14 Service Configuration Parameters .......................................... .................................................... .30 3.14.1 Number Reservation Period ........................................ ................................................. 31 3.14.2 Number Cooling Period ............................................. ................................................... 31 3.14.3 Days until “end-of-visit”.................................................................................................31
3.15 Communities Configuration..........................................................................................................31
3.15.1 HPMN Blacklist/Whitelist ........................................... ................................................... 31 3.15.2 CAMEL Roamers..........................................................................................................31 3.15.3 MO-Barred Roamers ............................................ ................................................ ........31 3.15.4 MSISDN List .................................... .................................................. ...........................31
3.16 Service Reports............................................................................................................................32
3.17 Service Counters..........................................................................................................................32 3.17.1 Current Number of Active Local Roaming Numbers ......................................... ...........32 3.17.2 Current Number of Allocated Local Roaming Numbers .................................... ...........32 3.17.3 Current Available Local Roaming Numbers ...................................... ...........................32 3.17.4 Total MT Calls Duration of Local Roaming Numbers........................................ ...........32 3.17.5 Total LRN MO Calls Duration ............................................ ...........................................32 3.17.6 Average Visit Duration ............................................... ................................................... 32
4. Providing Local Roaming Number with Local Prepaid Account...........................................33
4.1 Work Process with Prepaid Accounts ............................................. .............................................33 4.1.1 Prepaid Account management .......................................... ...........................................33 4.1.2 Charging for MO Calls and SMS ............................................. .....................................33
4.2 Service Activation and Roamer’s Qualification ......................................... ...................................34
4.3 Prepaid Account Maintenance ........................................ ..................................................... ........34 4.3.1 Topping-up Prepaid Accounts ........................................... ...........................................35
4.4 Handling End-of-Life for LRN and Prepaid Account ......................................... ...........................35
4.5 Mobile Terminated Calls ........................................... ................................................... ................36
4.6 Mobile Originated Calls ........................................... ..................................................... ................36
4.7 Mobile Terminated SMS...............................................................................................................37
4.8 Mobile Originated SMS ............................................. ................................................... ................37
5. Summary.....................................................................................................................................38
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 5/38
Product Description
Local Roaming Number Page 5 Proprietary and Confidential
List of FiguresFigure 1: System Architecture ........................................... .................................................. ...................10
Figure 2: Service Initial Stage - Registration Activation & Announcement ............................................ 12
Figure 3: Service Announcement SMS example ...................................... .............................................15
Figure 4: IN-based call flow with CF deactivation ............................................. .....................................17
Figure 5: Mobile Originated Call Flow with Prefix ............................................. .....................................20
Figure 7: LRN Service Activation with Local Prepaid Account...............................................................34
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 6/38
Product Description
Local Roaming Number Page 6 Proprietary and Confidential
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
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 7/38
Product Description
Local Roaming Number Page 7 Proprietary and Confidential
1. Introduction – Service Overview
The Local Roaming Number (LRN) service enables VPMNs to provide a localnumber to their inbound roamers. Roamers can make and receive calls onboth their home and new local number.
Frequent travelers pay premium rates for using their mobile phones whileroaming. To reduce their costs, they often purchase local prepaid SIM cardsand in this way they can be reached ay local call costs. This reduces mobileterminated (MT) costs and removes the burden of international call expensesfrom 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 missingincoming calls on the inactive SIM.
The LRN service offers the benefits of having 2 numbers without the need tomanage a local prepaid SIM.
2. Service Background
2.1 The Challenge
Mobile phone users expect their roamingexperience to match their mobile lifestyles,
with easy access to both services andpeople anywhere, anytime. Yet, dialing andreceiving calls in visited networks isusually carried out at premium rates.
The result is that roamers look for cheapermethods of using their handsets. TurningOFF the handset is one sure way to lowerroaming expenses and rejecting incomingcalls is another. Many roamers, travelingfrequently to specific destinations, buylocal prepaid cards for roaming in thevisited country. However, when they replace the SIM in their handsets, theybecome unavailable on their home network MSISDN, These roamers tend to
use two handsets, in order to enable both numbers concurrently.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 8/38
Product Description
Local Roaming Number Page 8 Proprietary and Confidential
2.2 The Solution
Starhome’s Local Roaming Number™ service provides roamers with all thebenefits of having a local number without the drawbacks of purchasing anadditional SIM.
Inbound roamers, upon registering in the operator’s network, aredynamically allocated a local number (MSISDN) to be associated with theroamer’s handset while roaming in the network. Roamers can receive callsboth on the original number and on the new local number .
When originating calls, the roamer can select the CLI with which the call willbe identified with. The MO call can be identified with either the local roamingnumber itself or with the home CLI (MSISDN). By adding a prefix before thedestination number or by setting the default profile to “LRN”, the call isidentified with the local roaming number. This feature enables the roamer topresent a ‘local presence’ while 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.
2.2.1 Visited Operator Benefits
With the Local Roaming Number™ service operators can offer better tariffs forinbound roamers, which:
* Attract and retain inbound roamers
* Allowing operators total control over charges for MO and MT calls
* Encourage more local network traffic
* Offer a competitive advantage in the local market, reducing churn
2.2.2 Benefits to Home Operators
The Local Roaming Number™ service will prevent roamers from removing thehome network SIM with the resulting lost revenue (no MT calls, SMS, GPRS,MMS, VAS, etc.). This service enables roamers to be available on their homeMSISDN 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 localMSISDN.
* Provides “local presence” for frequent travelers by enabling them to bereached 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 localnumber
* The local number can be reserved for the roamer’s future visits
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 9/38
Product Description
Local Roaming Number Page 9 Proprietary and Confidential
3. Detailed Technical Description
This section includes a technical description of the signaling flows for CallControl and SMS traffic, followed by a functional description of other productfeatures including Service Logic, Billing, Reports, Roamers Provisioning andService Counters.
3.1 Connectivity
Figure 1depicts the Local Roaming Number system architecture andinterfaces.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 10/38
Product Description
Local Roaming Number Page 10 Proprietary and Confidential
Figure 1: System Architecture
3.1.1 MSC interface
The Local Roaming Number system, based on the IntelliGate gateway, can beintegrated to Orascom’s 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 ageneric technical solution for this service. The final delivered solutionORASCOMmust be adjusted to the specific network configuration andparameters including the network size and topology, the traffic volume, theINAP vendor’s variant, the CAMEL version - if relevant and Orascom’spreferences. All these are usually discussed prior to specifying the finaltechnical solution.
The two signaling options are described below.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 11/38
Product Description
Local Roaming Number Page 11 Proprietary and Confidential
3.1.1.1 ISUP
In particular cases, such as non-IN network environment and/or relativelylow inbound roaming traffic, call control is performed using ISUP signaling.
The IntelliGate is connected to the MSC, as call control does not requireconnecting the IntelliGate to the network via voice channels, SS7 signalinglinks are only used to convey the ISUP signaling. This inter-connection isachieved 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 ensurethat there is always a voice path between them. The IntelliGate uses theISUP signaling to control the looped-around ports using standard ISUPmessages.
3.1.1.2 Intelligent Network
The IntelliGate controls MO and MT calls delivered to inbound roamersbased on IN architecture. This solution suits networks that are IN-readyand/or networks that experience relatively high inbound roaming traffic.
Using INAP, call control is performed with a combination of Trigger DetectionPoints and Event Detection points.
3.1.2 Probe Interface
Using its SS7 Mobility Probe, the IntelliGate is connected to Orascom’sinternational SCCP signaling links in a completely passive mode.
This interface is used to obtain the relevant roamer’s information and acts asa triggering point for service activation.
3.1.3 Provisioning Interface
The provisioning interface enables Orascom to configure the behavior of theservice, set roamers’ qualification rules and view basic service statusparameters
3.1.4 Prepaid System Interface – Optional
This interface allows the service to interact with an existing Prepaid system. The service uses this interface to charge calls in real-time.
The prepaid system interface is highly customizable and can be easilyadapted to any prepaid system.
NOTE: The prepaid system interface is not mandatory for the Local RoamingNumber service and is configured during deployment of the service – withoutit the service can be provided with regular roaming charges for MO calls.
To read more about Local Roaming Number service with the prepaid systeminterfacing option please refer to chapter 4
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 12/38
Product Description
Local Roaming Number Page 12 Proprietary and Confidential
3.2 Prepaid Service Setup – Prepaid Option
When the Local Roaming Number service is configured with prepaid accounts
the service manager (Operator) has to set up a range of prepaid accountscorrelating to the Local Roaming Numbers reserved for allocation. The LRNservice shall use corresponding prepaid accounts during call charging.
After the LRN is allocated to an inbound roamer, the roamer is required totop-up the account. The inbound roamer may use ALL available topping-upmethods that are already in use for the local subscribers. For moreinformation about top-up methods for LRN prepaid accounts refer to chapter4.3.1.
3.3 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 roamer’s update location
* Obtaining subscriber information
* Service qualification process for each roamer
* Announcing service to roamers
* Monitoring roamer’s cancel location and purge messages
The following diagram depicts the initial stage process:
Figure 2: Service Initial Stage - Registration Activation & Announcement
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 13/38
Product Description
Local Roaming Number Page 13 Proprietary and Confidential
Step Action
Steps 1 & 2 Roamer registers location from the visited network via MAP_UPDATE_LOCATION to HLR
Step 3 The HLR responds with MAP_ISD (Insert Subscriber Data)
Step 4 The IntelliGate monitors the MAP_ISD message which triggers the service activation for this
roamer. The IntelliGate also sends an SMS with the service announcement and the allocated
local roaming number for this roamer.
3.3.1 Service Qualification Process
After the IntelliGate has detected a Location Update by an inbound roamer,the qualification process needs to decide whether this inbound roamer inentitled/qualified for 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.3.1.1 CAMEL Triggers
Inbound roamers with CAMEL triggers are in many cases Prepaid roamerswhich means that their charging and billing is done in real-time in theirhome network (HPMN). Local Roaming Number service identifies CAMELenabled roamers and provides visited network operators with three levels ofservice for those CAMEL subscribers:
1. NO Service – once a CAMEL enabled inbound roamer is detected theservice will not allocate a local number and the service will be barred forthis roamer.
2. MT Only service – this options enables the operator to offer a limitedservice for CAMEL enabled inbound roamers and allowing roamers toreceive calls and SMS on their local number – this option preserves theattraction of roamers into the network (by providing them service) withminimal impact on the network.
3. Full Service – MT and MO service preserving the charges for MO calls(with the HPMN or a local prepaid system interface) while providing acomplete service.
3.3.1.2 Barring Supplementary Services Information
Operator may decide not to provide the service to inbound roamers with MObarring information. The barring of MO calls may indicate that the inbound
roamer is a prepaid roamer not allowed to originate calls.If Operator decides to provide the service to barred inbound roamers, theonly way to charge these roamers is by providing them with a local prepaidaccount. For more information please refer to chapter 4.
The setting of this parameter is part of the provisioning of the service.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 14/38
Product Description
Local Roaming Number Page 14 Proprietary and Confidential
3.3.1.3 Roamers without Roaming Agreements - Optional
When the inbound roamer comes from an HPMN that does not have roamingagreements with this specific VPMN, the LRN service can be provided to theroamer while allowing roaming in the VPMN ONLY with the provided local
number. All charges shall be applied by a prepaid account.
This capability does NOT require any SIM changes or resetting of thehandset.
NOTE: Some networks (HPMNs) might consider this feature as a breach ofGSMA rules and regulation, an act that might effect (negatively) the VPMN’sstatus.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 15/38
Product Description
Local Roaming Number Page 15 Proprietary and Confidential
3.3.2 Service Announcement SMS
Figure 3: Service Announcement SMS example
The Service Announcement SMS promotes the service to inbound roamersand supplies information about the service. An example of such an
announcement is presented below:
The following capabilities are configurable by Orascom:* The announcement message can be delayed for a specified amount of time
after registration to the visited network, values are provided in minutes.
* The announcement supports multiple languages and provides automaticbest- match logic between the home country and the supportedlanguages, in cases of no match, a default language is activated.
* The message can include parameter fields which can be replaced withactual values before sending of the message
* Local Roaming Number – the allocated LRN
* The message can include instructions how to top-up the prepaid accountand how to activate the number (if required) via USSD commands.
* A different message can be sent to returning roamers receiving the sameLRN as in their previous visit. This message is called: “Return UserNotification”.
3.3.2.1 Out-of-Service Announcement SMS
The Out-of-Service Announcement SMS enables Orascom to alert inboundroamers who switched to another network (within the same country) about
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 16/38
Product Description
Local Roaming Number Page 16 Proprietary and Confidential
the loss of Local Roaming Number™ service. The message may notify theroamers how to switch back to this visited network.
The following capabilities are configurable by Orascom:
1. Send Out-of-Service announcement only if Local Roaming Number hasbeen used at least once (MO or MT) within this or any previous visits.
2. The announcement message can be delayed for a specified amount oftime after registration to another visited network. Values are given inminutes.
3. The announcement supports multiple languages and provides automaticbest- match logic between the home country and the supportedlanguages, In case no match a default language is activated.
4. The message can include parameter-fields to be replaced with actualvalues before sending of the message, like: the LRN, etc.
3.4 Active Profile Selection – optional The Local Roaming Number service can enable the user to toggle between twoprofiles: 1. the HPMN profile and 2. the VPMN profile.
The profiles include the following information:
1. The default CLI to be used for MO calls and SMS (e.g., when an HPMNprofile is selected, all my MO calls will show my home MSISDN as myCLI).
2. Charging Method to be used for traffic I generate with the active profile(e.g., when using the VPMN profile, all calls shall be charged via my localprepaid account.
The selection can be done via an USSD command or SMS.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 17/38
Product Description
Local Roaming Number Page 17 Proprietary and Confidential
3.5 Mobile Terminated Call Flow
This section presents the call flow for mobile terminated calls, when a local
roaming number is used to reach inbound roamers.
Figure 4: IN-based call flow with CF deactivation
Step 1 A mobile terminated (MT) call arrives at Orascom’s-GMSC, the call’s dialed number =
local roaming number
Step 2 The GMSC is configured to send all calls with a DN in a specified range to the IntelliGate
via INAP_IDP or ISUP_IAM or MAP_SRI
Step 3 The IntelliGate sends MAP_PRN to the serving VLR (taken from the MAP_ISD
monitoring)
Step 4 The serving VLR returns MAP_PRN_ACK with the MSRN
Step 5 The IntelliGate diverts the call via the MSRN to the inbound roamer – using
INAP_CONNECT(MSRN), ISUP_IAM(MSRN) or MAP_SRI_ACK(MSRN).
Steps 6 & 7 The GMSC sends the call via the MSRN to the serving MSC and the mobile handset
3.5.1 Called Party Notification
When a call is received, the called party (B-Party) would theoretically like toknow that the caller (A-party) used the Local Roaming Number to make thiscall (and not the home MSISDN).
Marking the CLI for incoming calls – with a special indication (like: “#” or “*”or another special character) so that the called party will know that thecaller has used the Local Roaming Number.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 18/38
Product Description
Local Roaming Number Page 18 Proprietary and Confidential
3.5.2 Mobile Terminated Calls - Billing
If LRN service is provided with MT calls free-of-charge, the VPLMN shouldfilter-out the MTCDRs for the mobile-terminated calls on the local roamingnumber and not send those CDRs to the roamer’s HPLMN.
3.6 Mobile Terminated SMS Flow
This section presents the flow for a mobile terminated SMS sent to a LocalRoaming Number.
Step Action
Step 1 A mobile terminated (MT) SMS arrives to Orascom’s Inter-working SMSC (or GMSC
or SMSC), the destination number=local roaming number
Step 2 The IntelliGate is configured as the HLR for all Local Roaming Numbers thus the Inter-
working SMSC sends MAP_SRI_SM to the IntelliGate
Step 3 IntelliGate returns the MAP_SRI_SM_ACK with IMSI and service MSC address
Step 4 The Inter-working SMSC forwards the SMS to the serving MSC via MAP_FSM
(Forward Short Message)
Step 5 The short message is sent to the handset
3.6.1 Mobile Terminated SMS - Billing
No billing issues are raised for Mobile terminated SMS, as short messages isfree of charge and does not require any HPMN involvement.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 19/38
Product Description
Local Roaming Number Page 19 Proprietary and Confidential
3.7 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 aprefix to the dialed number.
3.7.1 Caller Line Identification (CLI) replacement mode
3.7.1.1 Manual CLI Selection via Prefix Dialing
When the service is configured with “Manual CLI Selection” all MO calls aregenerated with the Home MSISDN unless the roamer added a predefinedprefix before the dialed number – adding such prefix shall make the serviceto replace the original CLI with the new local roaming number.
3.7.1.2 Automatic CLI Selection by Destination The CLI selection is done automatically according to the call’s destination.All calls to local destinations shall carry the local roaming number whilecalls to international destination shall have the home MSISDN as CLI.
This option can be combined with a prefix dialing which shall force the CLIreplacement for the next call (regardless of the destination).
3.7.1.3 Default CLI Selection by Selecting Active Profile
When “Active Profile” selection is enabled, the CLI to be used for MO Calls(and MO SMS) is provided by the active Profile for the roamer. The activeprofile also affects the charging method of the calls, whether via CDRs or viathe local prepaid account.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 20/38
Product Description
Local Roaming Number Page 20 Proprietary and Confidential
3.7.2 Mobile Originated Calls - with Home MSISDN
Mobile Originated calls from the Home MSISDN have a regular MO call flowwith no changes. The call is first handled by the serving MSC and is thenrouted by the dialed number. In “automatic CLI selection” mode or in “ActiveProfile selection”, all Mobile-Originated calls generated by inbound roamersshall be handled by the IntelliGate and the Local Roaming Number service.
The below call flow shows how the Local Roaming Number is presented asthe Caller ID for specific MO calls made by the inbound roamer.
Figure 5: Mobile Originated Call Flow with Prefix
Step Action
Step 1 An inbound roamer originates a call towards the serving MSC with a prefixed dialed
number (to local or international a destination )
Step 2 The prefixed call is handed by the MSC to the IntelliGate via INAP_IDP or ISUP_IAM.
Only calls with a specific service prefix (e.g. “#”) will be handed to the IntelliGate, other MO
calls will be handled in the regular way.
Step 3 The IntelliGate checks the service qualification for the caller. If qualified, then the
IntelliGate removes the prefix (the prefix can be removed by the serving MSC before
handing the call), changes the CLI to the Local Roaming Number and sends the call back
to the original destination (only now with the modified CLI)
Step 4 The MSC sends the call to the destination based on the dialed number (without the prefix)
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 21/38
Product Description
Local Roaming Number Page 21 Proprietary and Confidential
3.7.3 Mobile Originated Calls - Billing
The service is designed to have bronze interference with the billing and
charging processes.When using HPMN-based (CDRs) charging, for Mobile Originated calls withhome MSISDN no changes required to billing process.
For MO calls from the local roaming number (with prefix or automatic), theservice offers three billing methods (mutually exclusive):
1. Charging MO calls with a local prepaid accountWhen a prepaid account is allocated with the LRN all MO calls shall behandled by the prepaid service.
* The serving MSC will generate the CDRs (in the regular way) with one ofthe following two options:
▪ The MSC will remove the service prefix before generating the CDR
▪ When using IN, the IntelliGate can sendIN_FurnishChargingInformation to mark the CDR for later CDRprocessing
* The IntelliGate will generate CDRs for MO calls to be transferred to thebilling GW for processing at a later time. For more information about thebilling details and CDRs, see Section 3.13.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 22/38
Product Description
Local Roaming Number Page 22 Proprietary and Confidential
3.8 Mobile Originated SMS Flow
This section presents the flow for a mobile originated SMS sent with theLocal Roaming Number as CLI.
Figure 6: Mobile Originated SMS Flow
Step Action
Step 1 An inbound roamer originates an SMStowards the serving MSC with a prefixed dialed
number (to local or international a destination )
Step 2 The serving MSC forwards the SMS to the GMSC
Step 3,4 The GMSC forward the SMS to the SMSC. The message is passing through
IntelliGate’s Signaling Relay Module. On the way out the SMS destination Address in
changed to a temporary DID, this action shall make the SMS return to this network
after handled by HPMN SMSC.
Step 5 The HPMN SMSC queries for the serving MSC of this Destination Number (DID)
Step 6 IntelliGate transfers the query to B-Party’s HLR (the actual destination of this SMS)
Step 7 The HLR returns the serving MSC address and IMSI of the actual destination
Step 8 IntelliGate returns the actual IMSI of B-Party’s and IntelliGate’s global title as the
serving MSC for this destination
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 23/38
Product Description
Local Roaming Number Page 23 Proprietary and Confidential
Step 9 The SMSC forwards the SMS to IntelliGate (as the serving MSC)
Step 10 IntelliGate forwards the SMS to the actual serving MSC to be delivered
Step 11, 12 Acknowledgement messages for the MT forward Short Message all the way back to
the SMSC
3.8.1 Mobile Originated SMS - Billing
Using the above method the inbound roamer is charged normally fororiginating an SMS while roaming without the need for a local prepaidaccount, and without changing any roaming agreements or any coordinationwith A-party’s home network.
If a local prepaid account is provided with the LRN, it can be used to directlycharge the roamer for MO SMS. For more information, please refer tochapter 4.8.
3.9 Number Allocation Logic
3.9.1 Local Roaming Number Usage
The system can define different logics (time thresholds) based on theroamer’s usage figures. The figures are calculated as average calls (both MOand MT) per “visit-day”.
If the local number wasn’t used even once, then both reservation and coolingperiod values are 0 (zero) and the number is immediately returned to thepool.
The calculation of usage upper value is based on the following formula:
Usage Factor =
* Accumulated Number of Calls: the accumulated figure of all callsreceived and originated with the local roaming number on all visits untilnow
* Accumulated Visit Period: the accumulated figure for the total numberof days of all previous visits until now
Type Usage upper
value
Reservation Period
(days)
Cooling Period
(days)
Send “end-of-
reservation”Notification
Ivory 0-0.1 0 0 No
Bronze >0.1-1 60 45 No
Silver >1-5 60 60 No
Gold >5-10 90 60 Yes
od dVisitPeri Accumulate
allsdNumberOfC Accumulate
∑∑
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 24/38
Product Description
Local Roaming Number Page 24 Proprietary and Confidential
Type Usage upper
value
Reservation Period
(days)
Cooling Period
(days)
Send “end-of-
reservation”
Notification
Platinum >10 90 90 Yes
NOTE: The table includes sample values that are configurable via serviceprovisioning
3.9.2 Local Roaming Number Lifecycle
A roamer who has used the local roaming number will be entitled to longerreservation and cooling periods than roamers who haven’t used theirnumber at all.
As the allocation of local numbers is dynamic, the system may encounter lowavailability of local roaming numbers for allocation. In this case, thefollowing 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 numberswill be allocated and assigned to arriving inbound roamers
5. Arriving inbound roamers will be queued for available numbers – eachnumber returning to the pool will be immediately assigned to the first-in-queue roamer
During the cooling period the service manager (at VPMN) is required tomaintain the remaining prepaid account before allowing the reuse of thesave prepaid accounts (in case the previous account owner left a positivebalance in the account). Once accounts are ready to be reused, a list of“ready” accounts is uploaded to the system to be allocated again.
3.9.2.1 Visit Period The visit period is calculated from the first update location monitored withinthe visited network until expiration of “day after end-of-visit” parameter (Seesection 3.14.3).
t
Visit Period
Number allocated
Reservation Period
until revisit
Cooling Period until
reallocation
Number
reallocated
Network Announcement:
“Subscriber Unavailable”
Network Announcement:
“Invalid Number”
Local Calls Diverted
to Roamer tt
Visit Period
Number allocated
Reservation Period
until revisit
Cooling Period until
reallocation
Number
reallocated
Network Announcement:
“Subscriber Unavailable”
Network Announcement:
“Invalid Number”
Local Calls Diverted
to Roamer
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 25/38
Product Description
Local Roaming Number Page 25 Proprietary and Confidential
3.9.2.2 Reservation Period
The reservation period is calculated from “end-of-visit” until the definedperiod of time (in days) for the roamer’s type (see Section 3.9.1)
3.9.2.3 Cooling Period
The cooling period is calculated from the end of the reservation period untilthe defined period of time (in days) for the roamer’s type (see Section 3.9.1)
3.9.3 Required Amount of Local Roaming Numbers
This section explains how to calculate the required amount of local roamingnumbers 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:
( ) ( ) DUE AVD AVDCIR +×/
Number of allocated local roaming numbers for reservation and coolingperiods:
( )( ) ( )CLP RSP ULR AVDCIR +××/
Total required Local Roaming Numbers:
( ) ( ) DUE AVD AVDCIR +×/ + ( )( ) ( )CLP RSP ULR AVDCIR +××/
Here is a simplified example for the calculation of maximum allocation (allplatinum roamers):
* CIR =10,000 concurrent roamers
* AVD = 4 days
* DUE = 2 days* ULR = 0.05 (5%)
* RSP = 90 days
* CLP = 90 days
( ) ( )244/10000 +× + ( )( ) ( )909005.04/10000 +×× = 37500 local roaming
numbers required
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 26/38
Product Description
Local Roaming Number Page 26 Proprietary and Confidential
3.9.4 End of Reservation Notification
Orascom sends an automated notification to a former inbound roamernotifying about the reservation period expiration. The message may includeinstructions to call Customer Care and extend the reservation period orinstructions for self provisioning of the reservation period.
3.10 MT Calls Handling when Roamer is Not Connected toNetwork
This section focuses on the service when an inbound roamer is notconnected to the visited network and the allocated number is in the“Reservation Period”. The various options outlined below will enhance boththe caller experience and the service to the inbound roamers when they areabsent.
3.10.1 Release Call - Status of Local Roaming Number The network can provide the caller with accurate notification about thestatus of the roamer with the Local Roaming Number. If the network fails topage 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 isinvalid” notification release cause.
3.10.2 Optional: Send “Missed Call Notification” SMS
The service will send an SMS with the missed call details to the homeMSISDN. The message will include the caller identification (if provided bynetwork) and the call time stamp.
NOTE: This feature can benefit the HPMN by generating international trafficfrom the “ex-roamer”, which is registered to another network, back to thecaller.
3.10.3 Optional: Divert Calls to Home MSISDN
This option enables inbound roamers to continue to receive calls on bothMSISDNs, even if they are not connected to the VPMN. With this option, theinbound roamer is charged for the forwarded leg. Charging can be made withthe following:
* Local Prepaid account* Inbound roamer’s Credit Card
* Other payment methods: Paypal, etc.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 27/38
Product Description
Local Roaming Number Page 27 Proprietary and Confidential
3.11 Out-of-Serving Notification
When an inbound roamer with an active Local Roaming Number has left thisvisited network and roamed into a competitor’s network (in the same
country) the service can be configured to send an “Out-of-service”notification SMS for notifying the roamer that the Local Roaming Number isnot available anymore. The notification should encourage the roamer tomanually select the correct network.
3.12 Provisioning
The service provisioning interface enables service configuration.
3.12.1 Provisioning for Customer Care
This section presents the provisioning capabilities available to Customer
Care representatives
3.12.1.1 Local Roaming Number Recovery
This function retrieves the last roaming number for a roamer.
The response returns the following details:
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, free
4. Days until end of current status period (free=unlimited)
5. Number was used by roamer: Yes/No
3.12.1.2 Reservation Period Query
This function retrieves the number of days until end of reservation period bythe roamer’s Home MSISDN or Local Roaming Number. The function alsoreturns the number of days in the cooling period for the roamer. Both values- reservation and cooling - are based on the roamer’s type (see Section 3.9.1)
3.12.1.3 Reservation Period Extension
This function enables customer care representatives to extend thereservation 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 LocalRoaming Number to an inbound roamer.
3.12.1.4 Exclusion of Roamer from Service
An inbound roamer may contact Customer Care and ask to be excluded fromthe service permanently or for the current visit
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 28/38
Product Description
Local Roaming Number Page 28 Proprietary and Confidential
3.12.1.5 View List of Roamers Excluded from Service
This function provides a list of all the excluded-by-request roamers.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 29/38
Product Description
Local Roaming Number Page 29 Proprietary and Confidential
3.12.1.6 Renew Local Roaming Number for Roamer
This function allocates a new local roaming number for a roamer throughthe home MSISDN
This function can be used after a roamer has requested to be excluded fromthe service (remove the roamer from excluded list)
This function can be used when the roamer requests the current localroaming number be replaced. The previous local roaming number, if used,starts a “Cooling period” before being returned to the available pool. If theprevious local roaming number was not used, then it can be returned to theavailable local roaming number pool immediately.
3.12.2 Customer Care User Interface
This is a web-based interface that enables Customer Care personnel tocontrol the provisioning functions, (see Section 3.12.1).
3.12.2.1 Local Roaming Number Recovery
This function enables inbound roamers to recover the last local roamingnumber allocated for this home MSISDN.
3.12.2.2 Reservation Period Query
This function enables inbound roamers to query how many days are left fortheir reservation period.
NOTE: Roamers may query their reservation period from any network (not only fromthe VPMN)
3.12.3 External Systems Provisioning Interface
This is a Simple Object Access Protocol (SOAP) based interface that allowsconnectivity of the service to existing CRM systems and other provisioningsystems.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 30/38
Product Description
Local Roaming Number Page 30 Proprietary and Confidential
3.13 Billing Processes
This section presents the billing and CDR aspects offered by Local Roaming
Number™ service.
3.13.1 Billing Process for Mobile-Originated CDRs
The main issue with the billing process for MO calls is the prefixed DN fieldand the actual connected DN that should be added into the MOCDR or TAPfile.
3.13.1.1 When Originating MSC Generates CDRs
If billing is carried out using the regular CDRs generated by the service MSC,
the IntelliGate can add additional information by using Furnish ChargingInformation (INAP/CAP operation), (only where INAP is used for Call control).
The specific details are to be agreed with Orascom on deployment.
3.13.1.2 When IntelliGate Generates CDRs
When the IntelliGate generates the CDRs locally, it sends them periodicallyto the billing mediation device for further processing by Orascom.
3.13.2 Billing Process for Mobile-Terminated CDRs
The main issue is how to identify the MTCDRs for special handling by themediation device
3.13.2.1 Identifying LRN MTCDRs by Decorated CLI (CgP)When IntelliGate sends a Mobile-Terminated call on the Local RoamingNumber, it adds a prefix (preconfigured) to the CLI field(CallingPartyNumber) in order to show the receiving side that this is a“special” incoming call.
The decoration of the CLI appears in the terminating MSC generated CDRand should be used to identify the MTCDR.
3.13.2.2 Identifying LRN MTCDRs by LRN Value in OCN/RDN Filed
When IntelliGate sends a Mobile-Terminated call on the Local RoamingNumber, it can put the LRN value (the called number) in the OCN (OriginalCalled Number) field on in the RDN (Redirecting Number) field.
These fields are inserted into the MTCDR and as the LRN values are all in apredefined range, the billing mediation device can easily distinct those CDRsfrom the rest.
3.14 Service Configuration Parameters
This section presents the parameters configuring the service
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 31/38
Product Description
Local Roaming Number Page 31 Proprietary and Confidential
3.14.1 Number Reservation Period
The Number Reservation period is number of days that the local roamingnumber is reserved for the next visit of the inbound roamer. During thistime, the number will not be allocated to another roamer and MT callattempts will be handled as described in Section 3.4
3.14.2 Number Cooling Period
After the reservation period has expired the “Cooling Period” starts. This isthe number of days, during which the number will not be allocated to otherroamers. Callers will receive an “invalid number” announcement.
3.14.3 Days until “end-of-visit”
The number of days without a monitored update location before the servicewill decide that the roamer has ended the visit.
When this threshold is reached, the system sends a MAP_SRI_SM to the HLRto verify whether the roamer is not in the country anymore.
If the roamer has migrated to a competitor’s network, no “end-of-visit” can bedeclared and the timer is then reset for the same amount of days again.
3.15 Communities Configuration
3.15.1 HPMN Blacklist/Whitelist
A list of HPMNs, to whose respective outbound roamers the service will notbe available for their. Roamers from these networks will only be able to
receive the service, if they have specifically requested to opt-in via CustomerCare
3.15.2 CAMEL Roamers
This configuration is an automatic community built from inbound roamerswith CAMEL subscription records in their MAP_ISD message
3.15.3 MO-Barred Roamers
An automatic community built from inbound roamers with a barringsupplementary Services activated record in their MAP_ISD message
3.15.4 MSISDN List
A community of subscribers within a specified MSISDN list. The list may alsoinclude wildcards and ranges
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 32/38
Product Description
Local Roaming Number Page 32 Proprietary and Confidential
3.16 Service Reports
The service accumulates traffic data and details that can be used to analyzethe service behavior and usage.
The data provided by the service supports generating reports.
3.17 Service Counters
3.17.1 Current Number of Active Local Roaming Numbers
This counter shows the status of the system with the number of localroaming numbers currently attached to inbound roamers.
3.17.2 Current Number of Allocated Local Roaming Numbers
This counter will show the status of the system with the number of localroaming number in the attached and reserved status
3.17.3 Current Available Local Roaming Numbers
This counter will show how many local roaming numbers are in an availablestate (not attached, not reserved, and not cooling).
3.17.4 Total MT Calls Duration of Local Roaming Numbers
This counter will show the total duration of answered mobile terminatedcalls that were applied to the Local Roaming Number.
3.17.5 Total LRN MO Calls Duration
This counter will show the total duration of answered mobile originated callsthat were applied using the Local Roaming Number for CLI (prefix based MOcalls).
3.17.6 Average Visit Duration
This counter will show the average visit duration in the VPMN.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 33/38
Product Description
Local Roaming Number Page 33 Proprietary and Confidential
4. Providing Local Roaming Number with LocalPrepaid Account
This chapter presents the Local Roaming Number service when using a localprepaid account provided for charging inbound roamers
4.1 Work Process with Prepaid Accounts
Using a local prepaid account provides the operator with additional chargingcapabilities when offering the service to inbound roamers, this chapter willpresent the options alongside some considerations and decisions needed tobe taken by the operator:
4.1.1 Prepaid Account management
When setting up the service for each number in the Local Roaming Numberrange a prepaid account is created (using existing prepaid system tools). Thisaccount is coupled with the LRN lifecycle. When a roamers is registering ontothe VPMN, the LRN service allocates a local number with an empty prepaidaccount ready to be topped-up. At “end-of-life” of the local roaming number,the LRN service shall provide a report of non-reserved numbers (numbersthat passed the reservation period) to the service manager (personnel). Theservice manager shall use the list to reset the prepaid account (includingmoney remaining in the account – according to the existing reset procedure).
NOTE: Operator may decide, for service promotion, to add an initial amountof money into the account to encourage usage and lower service adoptionbarriers.
4.1.2 Charging for MO Calls and SMS
The service provided a few levels of charging options as follows
4.1.2.1 Charging all MO calls and MO SMS via the local prepaid account
This option charges all mobile-originated and mobile terminated calls via thelocal prepaid system. This option suits inbound non-CAMEL prepaidroamers with barring enabled for MO calls.
4.1.2.2 Charging MO calls and SMS via local prepaid account based on
CLI replacement This option enables distinct charging based on roamer’s request or on CLIreplacement – whenever the CLI for MO calls and SMS are changed to theLocal Roaming Number (Manual, Automatic, Active-Profile) the charging forthe calls is done via the local prepaid account.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 34/38
Product Description
Local Roaming Number Page 34 Proprietary and Confidential
4.1.2.3 Charging via Local Prepaid Account Based on Destination
Under this option, whenever the roamer calls local destinations the chargingis done via the local prepaid account regardless of the CLI replacement.
4.1.2.4 Charging via Local Prepaid Account Based on “Active Profile”
Based on the “Active Profile”, when LRN profile is used, the service shallcharge all traffic (MO and MT if needed) with the local prepaid account.
4.2 Service Activation and Roamer’s Qualification
Figure 7: LRN Service Activation with Local Prepaid Account
Service activation is done when the inbound roamer is registering to thevisited network, this stage include the same stages as in chapter 3.2.
After the user had successfully registered to the visited network, LRN servicechecks the roamers qualification for the service and take action for eachroamers group (postpaid, CAMEL, MO barring) based on the rules define insection 4.1.2
4.3 Prepaid Account Maintenance
The unique design of the LRN prepaid integration, provides call control andbasic number translation functionality from the IntelliGate platform.
Maintenance of the prepaid accounts is done externally to the service byusing existing components, such as Scratch cards management system andUser interaction methods. This architecture enables the operator tomaximize productivity from previous investments and eliminate the need tosetup a parallel/LRN specific prepaid operation (no new scratch cards, nonew distribution channels, etc.)
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 35/38
Product Description
Local Roaming Number Page 35 Proprietary and Confidential
4.3.1 Topping-up Prepaid Accounts
This operation is done via externally to the LRN service by the existing top-up methods in the network.
The LRN service requires translating the user’s home identification (MSISDNand IMSI) with the new LRN allocated details. Following sections describe thedifferent top-up methods and behavior.
4.3.1.1 Via USSD
The user sends a USSD command with top-up details, the LRN service isrequired to handle USSD top-up request from inbound roamers and generateanother request with the translated LRN details towards the Top-up moduleof the prepaid system.
Two methods:
1. Providing LRN user a separate USSD command code for top-up. LRNservice may translate the special code to the “general” top-up code.
2. Redirecting the USSD commands (SCCP level or MAP level) through theLRN service
4.3.1.2 Via Customer Care
No changes are required, as the Customer Care representative can obtainthe LRN details from the user.
4.3.1.3 Via SMS
The users send an SMS with top-up details, LRN service is required to
translate the details to top-up the corresponding LRN prepaid account.
4.3.1.4 Via IVR
The users dial into an interactive voice response unit to top-up, the LRNservice shall put the correct Call Line Identification before connecting thecall to the IVR.
The network should send all MO calls from inbound roamers to the specifictop-up DN to the LRN service.
4.4 Handling End-of-Life for LRN and Prepaid Account
This section describes the procedure for handling “end-of-life” Local roamingnumber and there corresponding prepaid accounts.
At the end of the LRN reservation period (for LRN lifecycle, please refer tochapter 3.9.2), the number can be reassigned to another inbound roamertogether with the corresponding prepaid account.
The action of resetting prepaid accounts may require some accountingactions like, book keeping is account has positive or negative balance, thisaction should be done manually by authorized prepaid system personnel.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 36/38
Product Description
Local Roaming Number Page 36 Proprietary and Confidential
The LRN service shall produce a list of number that are candidates for reset,and after the list was processed by the service managers, it should beuploaded into the system to put the selected number back in the availablenumbers pool.
Both actions of generating the numbers list and uploading the numbers arepart of the LRN service provisioning interface.
4.5 Mobile Terminated Calls
The visited network operator may decide to provide the service by charginginbound roamers for mobile-terminated calls. In this case all mobile-terminated calls to the local roaming number shall be charged via the localprepaid account.
NOTE: this option may be also valid in countries where MT call charges existfor the domestic market, or if the VPMN would like to charge a reduced“roaming like” MT call charges.
4.6 Mobile Originated Calls
The flow for Mobile-Originated calls is affected by the CLI mode and the localprepaid account configuration for charging mobile originated traffic.
Figure 8: Mobile-Originated Call with local prepaid account
The following “high-level” diagram shows the flow for mobile originated call.
The service can also be configured and provided for MO calls with localprepaid charging if balance is positive and with regular roaming charges ifthe local prepaid account is empty.
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 37/38
Product Description
Local Roaming Number Page 37 Proprietary and Confidential
4.7 Mobile Terminated SMS
The recommended charging method is to allow reception of MT SMS for freein the network. Nevertheless, LRN serves can still trigger the local prepaid
account for each MT SMS and charge the user.
4.8 Mobile Originated SMS
In this solution the IntelliGate act as a Signaling Relay Module to interceptthe MO SMS on its way to the home SMSC and as the HLR for the localroaming numbers.
Figure 9: Mobile-Originated SMS with local prepaid account
Step Action
Step
1&2&3
An inbound roamer originates an SMS towards the home SMSC with a prefixed dialed
number (to local or international a destination )
Step 3* The SMS is intercepted by the signaling relay module in the Intelligate, which removes the
prefix and changes the CLI
Step 4 IntelliGate forwards the SMS to the local SMSC for further handling – sending the
message to its destination with the new CLI
Step 5 IntelliGate acts as the HLR for all MSISDNs allocated for Local Roaming Number service.
The SMSC sends MAP_SRI_SM to Intelligate which may relay the query to the actual HLR
to locate B-Party
Step 6 The SMSC charges A-Party for the SMS sending from the local account
7/23/2019 LRN Product Description
http://slidepdf.com/reader/full/lrn-product-description 38/38
Product Description
Step Action
Step
1&2&3
An inbound roamer originates an SMS towards the home SMSC with a prefixed dialed
number (to local or international a destination )
Step 7 The SMSC sends the SMS to its destination via MAP_FSM to the GMSC
5. Summary
Local Roaming Number service attracts inbound roamers by providing them avaluable resource – a local number.
The service focuses on creating loyalty between the inbound roamers and thevisited network by providing the roamers smooth and easy access into theservice without language barriers.
Local Roaming Number creates differentiation between networks in a visitedcountry by giving one network an edge over others.