Routing & translation

5060 WCS (Wireless Call
Server)
W 5.1 Translation & Routing
TMO18326 D0 SG DEN Issue 2.0

STUDENT GUIDE

All Rights Reserved © Alcatel-Lucent @@YEAR

All rights reserved © Alcatel-Lucent @@YEAR
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

W 5.1 Translation & Routing - Page 1

Empty page
Switch to notes view!

2


5060 WCS (Wireless Call Server)

This page is left blank intentionally


Terms of Use and Legal Notices
1. Safety Warning
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to
wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the
equipment alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.

2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (“Marks”) are the property of their respective holders, including AlcatelLucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning
the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to
change without notice.

3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No
other use or transmission of all or any part of this document is permitted without Alcatel-Lucent’s written permission, and
must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may
be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from
Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly
prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or
describes, and is expressly prohibited from modifying the information or creating derivative works without the express
3
written consent of Alcatel-Lucent.


4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including
lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not AlcatelLucent has been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an
endorsement, nor a recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The
information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some
cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely
accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment
and its operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. AlcatelLucent disclaims any warranties in connection with the products as used and described in the courses or the related
documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties,
including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of
dealing, usage or trade practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed
internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in
nature

5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are
governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal
Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including,
but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a
valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these
Terms of Use and Legal Notices shall remain in full force and effect.


Blank Page

4





Course Outline
1. This Course
AboutT&R Process Theory

4. Topic/Section is Positioned Here

Course outline Process
1. T&R
Technical support
2. Translation provisioning
Course objectives


1. Normalization

2. Prefix Positioned
1. Topic/Section is Translation Here
Xxx
Xxx
Xxx


3. National Translation
4. International Translation


5. Modifier Based Translation

3. Routing provisioning

1. Route Liste & Bundles
2. Outpulse Maps

3. Orig Routing
4. Modifier Based Routing
4. Appendix
1. Appendix

5




Course Outline [cont.]

6




Course Objectives

Welcome to W 5.1 Translation & Routing

Upon completion of this course, you should be able to:

Identify the main uses of Translation & Routing process in the WCS
List and order the steps of T&R process
State the main purposes of each step of T&R Process
State the WCS system logic for each step of Translation
Provision translation objects
State the WCS system logic for each step of Routing
Provision routing objects

7




Course Objectives [cont.]

8




About this Student Guide
Conventions used in
Switch to notes view! this guide
Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful
or interesting.

Technical Reference
(1) 24.348.98 – Points you to the exact section of Alcatel-Lucent Technical
Practices where you can find more information on the topic being discussed.

Warning
Alerts you to instances where non-compliance could result in equipment
damage or personal injury.

9


Where you can get further information


If you want further information you can refer to the following:
Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com


About this Student Guide [cont.]

10




Self-assessment of Objectives
Contract number :

At the end of each section you will be asked to fill this questionnaire
Please, return this sheet to the trainer at the end of the training

Course title :

Client (Company, Center) :
Language :
Switch

to notes view!

Number of trainees :

Dates from :

to :

Location :

Surname, First name :
Did you meet the following objectives ?
Tick the corresponding box
Please, return this sheet to the trainer at the end of the training

Instructional objectives

11

Yes (or
globally
yes)

No (or
globally
no)




Comments

Self-assessment of Objectives [cont.]
Instructional objectives

12

Yes (or
Globally
yes)

No (or
globally
no)



Other comments

Thank you for your answers to this questionnaire


Comments

Do not delete this graphic elements in here:

1—1

Section 1
T&R Process Theory
Module 1
T&R Process
3JK10613AAAAWBZZA Edition 4

5060 WCS (Wireless Call Server) — W 5.1 Translation & Routing
All Rights Reserved © Alcatel-Lucent 2007

All Rights Reserved © 2007, Alcatel-Lucent
Section 1 — Module 1 — Page 1

Blank Page
T&R Process Theory — T&R Process

1—1—




Document History
Edition

Date

Author

Remarks

2006-10-20

LAPIERRE, Laurent

First version

2007-01-22

LAPIERRE, Laurent

Updates & minor correction

2007-07-23

LAPIERRE, Laurent

New template. Minor corrections.

01

2007-08-01

LAPIERRE, Laurent

3JK reference with ED1.

02

2008-07-30

LAPIERRE, Laurent

Updated 4.4w with CLI inpulse map

03

2009-08-31

LAPIERRE, Laurent

Updated 5.0

04

2011-03

LAPIERRE, Laurent

Updated 5.1


2

Objectives

1—1—

After the completion of this module, you should be able to:

Identify the main uses of Translation & Routing process in the WCS
List the steps of T&R process
Order the steps of T&R process
State the main purposes of each step of T&R Process
List the main objects used in the GUI for T&R




3

Objectives [cont.]


1—1—




4

Table of Contents

1—1—

1 Overview
1.1 Translation & Routing environment
1.2 Process principle
1.3 Main steps
1.4 Relationship with IN-CS2 Call Model
1.5 Main objects manipulated in the GUI
2 Translation process
2.1 Translation steps
2.2 Normalization
2.3 Prefix Translation
2.4 International & National Translation
3 Routing Process
3.1 Routing steps and Origination Routing
3.2 Other Routings
4 Outpulse Map
4.1 Outpulse Map definition
4.2 Regular Outpulse Map versus Digit Outpulse Map
4.3 Regular Outpulse Maps for ISUP/BICC IAM message
4.4 Regular Outpulse Maps for DTAP, CAP and INAP msgs
4.5 Digit Outpulse Maps
4.6 Source Number manipulation
5 Modifiers
5.1 Definition and Principles
5.2 System defined and user-defined modifiers
5.3 Table of all modifiers
6 Complete process overview
6.1 notes
6.2 Complete Process Overview
7 Starting Translation Trees
7.1 Starting Translation Trees
7.2 Starting Translation Trees provisioning
7.3 Starting Translation Trees rules


Page
7
8
9
10
11
12
14
15
16
17
18
22
23
24
26
27
28
29
30
32
33
34
35
37
38
39
40
41
42
43
44
45

5

Table of Contents [cont.]

1—1—






6


1—1—

1 Overview




7

1 Overview

1.1 Translation & Routing environment

1—1—

PSTN
NETWORK

PSTN

8

ISUP Trunk Group
BSS Trunk Group
SS7/MAP

HLR

NPDB



The WCS acts as a GMSC or a VMSC.
The WCS is connected to Network Elements such as GMSC, VMSC, PSTN switches, BSCs, RNCs, ...
The WCS may process Mobile-Mobile, Mobile-Land, Land-Mobile and Land-Land calls, thanks to the
Translation & Routing process.
When the Call Server performs Translation & Routing process, as a result it routes the call or performs
a call control action.
At the end of the Translation process, an outgoing trunk group may be selected for routing the call to
the next network element (Mobile/PSTN switch or BSS).


1 Overview

1.2 Process principle

1—1—

9

2 main steps:
Translation
Routing
MSISDN, ISDN
MSRN, IMSI

Call Control Action

…

Call Context

Translation
Translation

Routing
Routing

« Destination Found »,
cont. at Orig. Routing

Outgoing Trunk Group & resources chosen



The Translation & Routing process involves two main steps:
1/ Translation Step: The call server analyze the called number and the call context to find a result
which is either:
A call control action: for example in the case of a call to a HPLMN subscriber, the call server will find
that the called number is a local MSISDN, so the right HLR has to be contacted with the « Send Routing
Information message ». This case involves the « MSISDN to HLR » table, one HLR network node and/or
the SGW configuration.
A destination: For example in the case of a mobile Originating Call to a foreign subscriber, the
translation process may set the destination to « International PSTN ». This case involves the Prefix
Tree, the International Table and Orig Routing with a route index/Orig Route descriptor « International
PSTN ». Then the call server can continue the process at the Routing step.
2/ Routing Step:
With a given destination, the call server will combine the destination of the call with the origination
modifier, to choose a Route List, then an outgoing trunk group, then a circuit (or an equivalent
resource in the case of Voice over Packet communication).
Other types of « routing modifier » do exist, for example depending of the LAC/Cell ID origination of a
Mobile Originated call.


1 Overview

1.3 Main steps

1—1—

10

Translations
MO Call

Normalization
VLR
Prefix
Translations

ISUP/BICC Call

MSRN Mobility
Check
MSISDN
Check

HLR

Routing
Route
Selection
Paging
MS term
Outpulse
Map
MS


BICC

ISUP


The Translation & Routing process involves the following steps:
Normalization (only in case of Mobile Originating Call). The number is normalized into a format that is
acceptable for VLR processing, thanks to digit manipulations. VLR processing is done: ODB, CB, CAMEL
O-CSI triggers (for prepaid calls for example).
Prefix Translation: digits can be manipulated, as well as NOA (Nature of Address). In this step, the
system logic also performs MSRN mobility check, MSISDN check (and NPDB).
Route Selection: when the destination is found, the route selection can be done. This route selection is
usually based on the destination and the Origination (from which MG or which site the call is coming ?),
but it may be based on other modifiers (e.g. CPC, IMSI calling, …).
Outpulse Map: just before the outgoing IAM is sent, outpulse maps can be used to allow additional digit
manipulations of the Called Party Number, Calling Party Number, etc.

Note that depending of the type of call (Mobile Originating Call or Network Originating
Call (ISUP)), the Translation process is not entered at the same step.


1 Overview

1.4 Relationship with IN-CS2 Call Model

1—1—

PIC: Null
DP0
Example
IN/CAMEL
Services

PIC: Collect Info
Normalization
OM

The Originating Basic
Call Model can be used
to describe the Translation &
Routing process

Prepaid
SCP

OM

DP2

11

VPN
SCP

PIC: Analyse Info
Prefix
Translations

Mobility
Checks

DP3
PIC: Select Route
Route Selection
Paging/MS Term

OM

Outpulse MAP
capability

Outpulse
Map



The O-BCSM is used to describe the actions for VMSC/GMSC during originating (VMSC) or forwarded
(VMSC or GMSC) calls.
PIC – Point in Call (O-BCSM)
The following states are applicable in this model.
>

Null

>

Collect Info

>

Analyze Info

>

Select Route

Normalization is performed in the Collect Info State. Prefix translations and Mobility checking are
performed in the Analyze Information State. Route Selection/Paging and Outpulse Map are performed
in the Selected Route state. Outpulse MAP is also performed for the SCP query.
DP2 – Collected Info
For the DP2 Trigger, the O-CSI is obtained during VLR check and DP2 TDPs are triggered at this point.
DP3 – Analyzed Info
For the DP3 trigger, the D-CSI obtained earlier from VLR check (or from the SCP after a previous DP2
query) and DP3 TDPs are triggered at this point. N-CSI triggers (switch-wide triggers, not subscription
based) are also triggered at this point.


1 Overview

1.5 Main objects manipulated in the GUI

1—1—

12

Translations
MOC

ISUP

Normalization

Normalization

Prefix
Translations

VLR

Prefix Translation

MSRN Mobility
Check

MSRN-HON Distribution table

MSISDN
Check

HLR

MSISDN to HLR table

Routing
Paging
MS term

Route
Selection

Orig Routing

Outpulse
Map
MS

Outpulse Maps
ISUP

BICC


The above drawing show you the main WEM GUI items (in the Configuration tree) associated with the
main Translation & Routing steps.


Answer the Questions – Main translation & routing steps

1—1—

Find the right place for:

13

?

ISUP Originating Call

?

Mobile Originating Call

SCP

Prefix Translation

VLR checks

?
MSRN check

Route Selection

?

SCP
HLR

Paging

Mobility check

Normalization

10 min

?


IAM Outgoing Message


1—1—





14


2.1 Translation steps

1—1—

Translations
MOC

Normalization
VLR

ISUP
paging

Prefix
Translations
MSRN Mobility
Check
MSISDN
Check

HLR

National
or
International
Translation

Routing


This draw shows an overview of the different Translation steps.


15


2.2 Normalization

1—1—

16

Only in case of MOC

Digit Tree Index
<201>

Normalization
Normalization

Called Number
in E164I

digit manipulation

« Call Control » result

ODB Check

SCP

IN OCSI DP2

Finally going
to next step


ODB, prepaid checks

V
L
R

Go at
Prefix
Tree

Possibility to loop to
other Normalization
trees


Normalization content:
Normalization is processed for Mobile Originating Calls only.
The T&R process is usually entered in the Normalization D-Tree <201>.
The “Starting translation trees” system parameters may change this default value.
One normalization entry is triggered according to the called number parameters (digit pattern,
min/max number of digits,...)
the called number is normalized, usually to comply with the E164 International format.
Other parameters (outgoing NOA, etc.) can be set.
In a simple example only one Normalization D-Tree is used, but on request the system can loop to the
same or another Normalization D-Tree (analyze based on Called Party Number), or to a Normalization
M-Tree (analyze based on other modifiers such as IMSI calling party, LAC/CellID, etc).
The system logic perform VLR checks: ODB checks, CB checks and OCSI check. If calling party has
CAMEL trigger on OCSI-DP2, the SCP will be queried. (this is a call control action)
ODB checks and OCSI checks may be bypassed on request if needed.
The next action is to go to the Prefix Translation step.
For full details on Normalization system logic and provisioning see Section 2 Module 1.
For details on Modifiers based normalization see Section 1 Module 5, and Section 2 Module 5.



2.3 Prefix Translation

1—1—

IS UP Orig inating Call

From
Norm a liza tion

NOA Routing flag
NOA
routing ?
<1>

local MSRN

incoming NOA

NOA
in IAM

Yes

No
Prefix Translation
Prefix Translation
digit manipulation
No

Paging

17

Release with
Cause Code
Prefix translator <x>

MSRN/HON Check

SCP

IN NCSI

HLR

MSISDN Check

Continue
Trans


To Routing Step


Prefix Translation content:
The MOC enters the Prefix Translation after the Normalization step, usually in the Standard Prefix Tree
<1>. The “Starting translation trees” system parameters may change this default value.
The ISUP enters first in NOA Routing. If NOA Routing is enabled in the incoming ISUP Trunk Group, the
Prefix translation step may be bypassed, or the call released, depending on the digits and incoming
NOA.
The ISUP calls do not use always the Prefix Translation D-Tree <1>. If another Prefix Translation <x> is
set in in the incoming ISUP trunk group properties, this one will be used.
One Prefix Translation entry is triggered according to the called number parameters (digit pattern,
The called number may be modified. Other parameters (outgoing NOA, etc.) can be set.IN NCSI may be
triggered on request. If yes, one SCP will be queried.
MSRN/HON check is processed. If the called number is a local MSRN (previously allocated by the same
VMSC), the mobile will be paged.
Mobility check is performed: NPDB and MSISDN check. If portability is not used only the „MSISDN to
HLR“ table is needed. The Mobility check can be bypassed on request if needed.
In a simple example only one D-Tree is used, but on request the system can loop to the same or
another Prefix Translation D-Tree (analyze based on Called Party Number), or to a Prefix Translation MTree (analyze based on other modifiers such as IMSI calling party, LAC/CellID, etc).
The next action is usually to continue translation at the National or International translation, or to go
directly at Routing step, if the destination is found. (end of translation step with destination found).
From W5.0, it is possible to play a tone or an announcement, before any repeat translation, continue
translation or go at routing step options.
For full details on Prefix Translation system logic and provisioning see Section 2 Module 2.
For details on Modifiers based Prefix Translation see Section 1 Module 5 and Section 2 Module 5.


2.4 International & National Translation

1—1—

18

From Prefix Translation

<202>
Internation
Prefix Tree

International
&
Translation

National
National
Translation
Translation

Translation
group

To Routing Step



From the Prefix Translation step, a „Continue National Translation“ will lead to National Translation
step, and a „Continue International Translation“ will lead to International Translation step.
For the International Translation:
First, the International Prefix Tree (usually D-Tree <202>) is entered. This is an optional tree where
CCNDC can be analyzed, mainly to select a dedicated destination for the call.
If a match is not found, the International Translation table is entered. This is a unique table that
contains only CC. If the called party match a CC entry (with min/max number of digits), the call will
be routed to a dedicated destination. (end of translation step with destination found).
For the National Translation:
There is one National Translation table per Translation Group.
Usually the Standard National Translation Group is used, but another National Translation may be
used if provisioned in the incoming trunk group parameters.
The National Translation table will only analyze NDC, to find a destination. (end of translation step
with destination found).
No Digit Manipulation is allowed in the International or National Translation.
No loop back to Prefix Translation step is allowed in the International or National Translation.


Answer the Questions – Normalization

1—1—

19

True or False ? Tick the following statements if they are true :
Normalization is the first mandatory Translation step
in case of Mobile Originating Call
Normalization is used, among others, to trigger the
SCP in case of prepaid call with OCSI mark DP2
Normalization is the only step in Translation & Routing
where the SCP may be triggered.

5 min
(Correct answer may require more than one choice)




Answer the Questions – Prefix Translation

1—1—

20

True or False ? Tick the following statements if they are true :
Prefix Translation is the only Translation step that
allows digit manipulation of the Called Party
for ISUP originating calls.
Prefix Translation is used only for ISUP originating calls:
for MOC, Normalization is used.
Prefix Translation is the translation step where the
called number may be recognized as a MSISDN of our
HPLMN.
5 min




Answer the Questions – National & Intern. Translation

1—1—

21

Choose the right answer:

National and International translation is a mandatory
step in Translation & Routing process, to find the
destination of the call.
National and International translation is a optional
step: the Prefix Translation may determine directly the
destination of the call, without the need of International
or National Translation.

5 min
(Correct answer requires only one choice)





1—1—

3 Routing Process




22

3 Routing

3.1 Routing steps and Origination Routing

Translation result,
destination found

1—1—

Orig Descriptor / Route Index

From Trans lation

Orig Route Modifier

Orig Routing

An Orig Routing entry combines the
origination and the destination

Route Action:
Route Immediately

The call server can choose an outgoing resource

Route List
(Bundles,
Trunk groups
and
Cause Code)

Ress ource & translated number

Outgoing NOA and digits can be modified

23

Outpuls e MAP


The Routing process is entered if the translation has ended with a „destination found“ result.
The Routing process is always entered with the Origination Routing.
The Orig Descriptor / Route Index is the destination, given from the last step of translation,
The Orig Route Modifier give the origination of the call, given in the incoming trunk group properties,
The Orig Routing will combine the destination and the origination of the call,
The result is usually a Route List if we decide to route the call immediately.
A Route List will help the system to choose an outgoing resource:
A Route List is a list a resources given with priority order. Each resource can be:
An outgoing Trunk Group,
A Bundle, which is a group of outgoing Trunk Groups in load sharing fashion,
A release with a cause code, use to release the call with a specific cause code / announcement, if
no outgoing resource is available.
Finally, with the Outpulse Map, the outgoing Nature of Address can be override, and the outgoing digits
can be modified.


3 Routing

3.2 Other Routings

1—1—

Orig Routing is the first routing,
Orig
and can be followed by:
Descriptor /

From Translation

Route Index
Orig Routing

-R3.1 legacy routings

Orig Route Modifier

Cont at (...) Routing
Routing based
on Modifiers

-Routing based
on modifiers

R3.1 legacy
Routings

CIC routing
IMSI routing
CPC routing

M-Selector with (CIC,
Routing with (CIC, IMSI,
IMSI,LAC,SAI,CLI,ToD)*,
LAC, SAI, CLI, ToD),
(CPC, OSSS, OCSI,
(CPC, OSSS, OCSI,
STL, Codec, Service)**
STL, Codec, Service,
NOA, OICK, ST, TICK)

LAC routing
OSSS routing
OCSI routing
Route
Immediately

Routing based on modifiers
is more powerful and
easier to provision.

Route List
(Bundles, Trunk groups
and Cause Code)

Ressources & translated number


ToD routing
Route
Immediately



Other routings steps can be used between the Orig Routing Step and the final step.


24

Answer the Questions – Orig Routing

1—1—

25

Right or False ? Orig Routing may be used to:
Choose next step of routing depending of the
Translation result and the Origination of the call
Choose a Route List for routing the call, depending on
the Translation result and the IMSI of the calling party
Choose a Route List for routing the call, depending on
the Translation result and the Origination of the call

5 min





1—1—

4 Outpulse Map




26

4 Outpulse Map

4.1 Outpulse Map definition

1—1—

Outpulse Map allows additional digit manipulation:
For Called Party Number, Calling Party Number, etc.
After all translation & routing steps
Just before one message is sent to another Network Element.

Main example:
To change NOA + digits of the Called Party
Just before sending the outgoing IAM.

2 different kinds of Outpulse Map objects:
Regular Outpulse Maps.
Digit Outpulse Maps.




27

4 Outpulse Map

4.2 Regular Outpulse Map versus Digit Outpulse Map

1—1—

28

Regular Outpulse Map:
One Outpulse Map for one kind of number to change.
Example: Change NOA and digit of ISUP Called Party Number.

Digit Outpulse Map:
One Outpulse Map may contain many changes in different fields, for
different numbers. (example change ISUP Called Party and Calling Party
Numbers).
More possibilities to change the number (example: insertion of LAC/CI, part
of IMSI, etc. at any part of the current number).

These 2 ways are mutually exclusive.
(one operator should use either regular OM or Digit OM - See note).
Compared to Regular Outpulse Maps, Digit Outpulse Maps are:
More efficient to use from provisioning point of view, in complex networks.
Give more possibilities to change and format the numbers.



Note:
Each operator should use either regular OM or Digit OM, for the fields (numbers) that are common to
Regular and Digit Outpulse Maps.
If there is a provioning conflict risk between the two Outpulse Map systems, a warning is displayed on the
GUI screen.
Conflicts may arise when two manipulations (regular OM and digit OM) are provisioned for the same digit
pattern. in this case digit manipulation in digit Outpulse Map takes precedence on "regular" outpulse
map.


4 Outpulse Map

4.3 Regular Outpulse Maps for ISUP/BICC IAM message

1—1—

ISUP Outpulse Map:
Change NOA and digit format of ISUP/BICC Called Party Number.

CLI Outpulse Map:
Change NOA and digit format of ISUP/BICC Calling Party Number.

RN Outpulse Map:
Change NOA and digit format of ISUP/BICC Redirecting Party Number.

OCN Outpulse Map:
Change NOA and digit format of ISUP/BICC Original Called Party Number.

These Outpulse Maps are chosen in Route List objects.




29

4 Outpulse Map

4.4 Regular Outpulse Maps for DTAP, CAP and INAP msgs

1—1—

30

Mobile Outpulse Map (for DTAP Setup message):
Change NOA/TON and digit format of DTAP Calling Party Number.

Mobile Outpulse Map (for CAP or INAP Initial DP message):
Change NOA and digit format of CAP/INAP Called Party Number.
Change NOA and digit format of CAP/INAP Calling Party Number.

For CAP/INAP, Outpulse Maps may be indexed on per SCP address basis.




Answer the Questions – Regular Outpulse Map

1—1—

10 min

In the following process, place each
regular outpulse map at the right place

?

CLI Outpulse Map

31

MOC

Normalization

CAP Called Party

SCP

?

VLR checks

? IS UP call

CAP Calling Party

MSRN check
SCP

DTAP Calling Party

?

HLR

? Paging

P refix Translation

Mobility check

?
ISUP Outpulse Map

?

Route S election




?

4 Outpulse Map

4.5 Digit Outpulse Maps

1—1—

32

One Outpulse Map may change (or not) the following fields:
Redirecting Party Number – ISUP, BICC, CAP, INAP
Original Called Party Number – ISUP, BICC, CAP, INAP
Calling Party Number – ISUP, BICC, CAP, INAP, DTAP
Location Number – ISUP, BICC, CAP, INAP
Called Party Number – ISUP, BICC, CAP, INAP
Connected Number – DTAP
Interrogate SS Forward to Number List – DTAP

One Digit Outpulse Map entry takes care of one specific change of
number, in one specific case. (like a regular Outpulse Map entry):
Change of NOA,
Insert/delete digits,
Various changes (number-dependant: APRI, SI, NI indicators, billing records)
Up to 5 Source Number Manipulation.




4 Outpulse Map


1—1—

33

A Source number manipulation is an object that:
Extract (grab) some digits from one of the following field:
MSISDN, Redirecting Number, Original Called Number,
LAC, Cell ID/SAC, IMSI, Carrier ID, CLI, MCC, MNC, IMEI;
Will insert these digits at a specific position of an other number, when it will
be used.
Example: « extract 5 first digits of the MSISDN, insert them at position 1 »
will just « Insert the MCCMNC in front ».

The same Source Number manipulation may be reused for various
numbers in Digit Outpulse Map entries.
The Source Number manipulation may be used also for digit
manipulation of the Called Number during Normalization and Prefix
Translation.





1—1—

5 Modifiers




34

5 Modifiers

5.1 Definition and Principles

1—1—

A modifier :
is an abstracted integer, or an index;
this index represents a value or a group of values for a specific call
parameter: location of the call (LAC/CellID, SAI), calling party identity
(IMSI, CLI…), etc;
can be used to modify the translation & routing process:
In Normalization and Prefix Translation, mainly to change the called
number.
In Routing, to change to Route List that will be used.




35

5 Modifiers

5.1 Definition and Principles [cont.]

1—1—

The list of usable modifiers is not the same for Normalization, Prefix
Translation and Routing steps.
For Normalization and Prefix translation steps:
Modifiers are used in Modifier-Trees (M-Tree).
M-Trees and D-trees are sharing the same IDs; typically trees ID from <2> to
<200> may be used for user-defined Digit-Trees or Modifier-Trees.

For Routing step:
Modifiers are used in Modifier Based Routing tree objects.

An M-Tree or a Modifier Based Routing tree is analysing from 1 to 5
modifiers in a single table.




36

5 Modifiers

5.2 System defined and user-defined modifiers

1—1—

Some Modifiers are System-defined, when the values are normalized:
CPC: Calling Line Party Category
OSSS: Operator Supplementary Service Support codes
OCSI: Originating Camel Subscriber Information value
STL: Satellite Link Modifier
Codec: Incoming Codec used
Service: Bearer capability
NOA: Nature of Address

Some Modifiers are user-defined for flexibility purposes:
IMSI: IMSI pattern
LAC: LAC/cellID ranges
SAI: LAC/SAC ranges
CLI: Calling Line Identity pattern
IN Service: SCP addresses and Service Keys
ToD: Time of Day: Day and Time
CIC: Carrier Instance Code, for equal access feature
ORM: Origination Modifier (multi-site multi-MG environment)



37

5 Modifiers

5.3 Table of all modifiers

1—1—

Called Party Number Nature of Address
M obile originator’s IM SI

CLIM

Calling Line Identity

N, PT, R X
Nature of Address Routing
N, PT, R
X X X M odify translations and routing based on which PLM N
originating subscriber belongs to
N, PT, R
X X X Similar to IM SI – used to alter translations and routing
based on CLI.
N, PT, R
X X X Location Area Code + Cell Range M odifier
N, PT, R
X X X Service Area Indicator M odifier (3G)
PT, R
X
Origin or WM G modifier. Note: PT, from W4.2
PT
X X
Different translations based on Service Key and SCP adr.
PT, R
X
Calling Party Category modifier. R (ISUP only) ,PT (VLR
only), from W4.2 R (ISUP and VLR)
PT, R
X
Operator Supplementary Service Support M odifier
PT, R
X
O-CSI based modifier
R
X
X For equal access feature
R
X
Satellite Link M odifier
R
X
try to select route using same type of codec
R
X
X Time of Day modifier
R
X
X Allows non-emergency calls (e.g. NA 611, 311) to use
same location –based routing as for emergency calls.
R
X
Bearer Capability

LACM
SAIM
ORM
INM
CPCM

CGI received from BSC
SAI received from RNC
Originating Trunk Properties
SCP Address and Service Key
CPC in subscriber's profile (M OC), or in
incoming IAM (ISUP originating call)
OSSSM
OSSS code in VLR
CAM ELM IN trigger information in the VLR
CICM
Dialed CAC or subscriber profile
STLM
connection indicators received in IAM
CODECM originating trunk properties or codec
TODM
System Time
EM Z
Emergency Zone M odifier

SERVICEM bearer service or teleservice from SETUP

Purpose
usr-d for R

NOAM
IM SIM

usr-d. for N&PT

Used In
User-def.

Obtained from

System-def.

Code


This table is given for reference.
N=Normalization
PT=Prefix Translation
R=Routing

Note: EMZ modifier is only available for North America.


38


1—1—

6 Complete process overview




39

6 Complete Process Overview

6.1 notes

1—1—

40

Please see the next full comment page.
This Complete Process Overview can help you to do the exercises, and
to understand the details of the training.
Please note that :
All the loops, features, links and bypasses of the Translation&Routing
process are not given in this drawing.
This draw gives list of Digit Outpulse Maps used, not the Regular Outpulse
Maps.



Note: since W4.20, a new optional feature “International Translation Prevention” may be used:
With this option off:
For MOC and ISUP/BICC incoming calls, an International number with destination international (CC do
not match your default Country Code) will be analysed in the International Prefix Tree, typically
<202>.
For a number coming from HLR/SCP/VLR, for example a Forwarded To Number, an International
number with destination international (CC do not match your default Country Code) will be analysed
in the International Prefix Tree, typically <202>.
With “International Translation Prevention” options on:
For MOC and ISUP/BICC incoming calls, all numbers will be analyzed in the “standard” prefix trees,
for example <1>.
All numbers coming from HLR/SCP/VLR, even International, will be analyzed in the “standard” return
tree, for example the HLR Prefix Tree for a MSRN, or the CFW Prefix Tree for a Forwarded-toNumber.
This option is an internal option of the system, not dynamically configurable.


6.2 Complete Process Overview

1—1—

A5060WCS – Translation & Routing
5060 WCS W4.x - TRANS LATION & ROUTING
Process Overviews view!
Co mple te PronotesOve rvie w
Switch to c e s
L. LAPIERRE / Alcatel University Lannion
-All loops, links and features are not written.
-Tree's Index are given as examples, they
depend on Starting Translation Trees.
-Ed8 dated July 30, 2008.

Starting
<201> Starting
< 1 > Starting
<202> Starting
<203> Starting
<205> Starting
<204> Starting

Mo bile Orig inating Call
<201>
Normalization
digit manipulation
ODB Check

2

<204> SCP PT (Connect or ETC)
Resume Route Action (Continue)

SCP

IN OCSI DP2

Normalization D-Tree or
Normalization D-Tree
Normalization D-TreeI,oror
M-Tree with IMS LAC,
M-Tree with with I, LAC,
M-Tree IMS
S AI, CLI modifiers
(IMSS AI, CLI modifiers
I, LAC, S AI, CLI)*,
(NOA)**
Multiple Trees can be looped

1

Parameter set by a previous
translation step, used in this
translation/routing step


P refix trans D-Tree or
P refix tr. D-Tree or M-tree
M-Tree with IMS I, CP C,
M-Tree with IMS S AI,
with (IMS I, LAC,I, CP C,,
LAC, S AI, CLI, OS S S
LAC, AI, erv. OS S S
CLI, INI,SIN s CLI, modifiers
OCS s ervice, ORM)*, ,
OCS I, OSs erv.Camel,
(CP C, IN S S , modifiers
NOA, OICK, S T, TICK)**

Multiple Trees
5060 WCS (Wireless Call Server)can be looped
Cont. to Nat / Intern trans / Orig
Routing (only from D-Tree)

x

Digit Outpuls e Map us ed
(s ee bottom-left key)

NOA Routing flag

(only from
D-Tree)

Go at
P refix
Tree

NOA
routing ?

<1>

Translation group

No

NOA Routing
NOA Routing

Yes

Prefix Translation
digit manipulation
No

<2> to <200>
* user-defined,
** system-defined
modifiers

Repeat
Norm.

Trees used:
Normalization tree
Prefix Tree
International tree
HLR tree
CFW tree
SCP tree

incoming trunk group
parameter impacting
a translation/routing step.

V
L
R

<2> to <200>
* user-defined,
** system-defined
modifiers

41

Key

Intercept

MSRN/HON Check

local MSRN 4
Paging

IN NCSI

SCP

MSISDN Check

Repeat
P refix Tr.

NOA in IAM

HLR

2

Continue at
Orig Routing
(to Blocked CC
then Orig Routing)

Resume Route Action (Continue)
<203> HLR PT (MSRN)
<201> Normalization, then
<205> Call Forwarding PT (FTN)


Cont. to
Nat. Trans

Continue at
Orig Routing

Cont. to
Intern. Trans

Termination
Type

Screening
Class
call permission: No

Screening

Intercept

Blocked CC
match
National
National
Translation
Translation

Intercept

<202>
<202>
Internation
Internation
Prefix Tree
Prefix Tree

Translation
group

& Intern.
Translation

Orig Descriptor
(Route Index)

Orig Route Modifier
(ORM)

Orig Routing
Route
Immediately

Routing based on Modifiers

* user-defined,
** system-defined
modifiers

LAC routing
OSSS routing
Route
Immediately

2
3

4

Calling P arty Number (inpuls e map)
Calling P arty Number
Called P arty Number
Original Called P arty Number
Redirecting P arty Number
Location Number
Calling P arty Number
Connected Number
Inter. S S Forward to Number Lis t

R3.1 legacy
Routings

CPC routing

Digit Outpuls e Maps may be us ed to change:
1

CIC routing
IMSI routing

M-S elector with (CIC,
Routingelector with IMS I,
M-S with (CIC, (CIC,
IMS I,LAC,S AI,CLI,ToD)*,
LAC, S AI, CLI, ToD)*,
(CP C, OS S S , OCS I,
(CP C, C, OS S S , OCS I,
(CP OS S S , Camel,
S TL, Codec, S ervice)**
SS TL,Codec, SS ervice)**
TL, Codec, ervice,
S ingle Modifier bas ed
routing after Orig Routing

Cont at (...) Routing

Route List

Camel routing
ToD routing
Route
Immediately

and Cause Code)
Intercept
3
Ressources & translated number




1—1—





42


7.1 Starting Translation Trees

1—1—

43

The previous complete process overview draw gives commonly used Trees
IDs for the Translation & Routing Process.
Now it is possible to choose more freely the Starting Translation Trees:
To be able to replace usual first Normalization tree <201> and/or first
Prefix Tree <1> by other user-defined trees.
To be able to start translation with a Modifier-Tree (not only a DigitTree).
To be able to replace usual System-Trees (<204> SCP PT, <203> HLR
PT…) by other user-defined trees.



Note: Trees <1>, <201> and <202> are still predefined to provide a default handling of existing trees.



7.2 Starting Translation Trees provisioning

1—1—

44

Starting translation trees can be defined in the WEM, as
System Parameters / Call Manager:



Prefix Translation Starting Tree:
For ISUP calls, the Prefix Translation starting tree is defined in the Trunk Group Parameters.
Note: Trees <1>, <201> and <202> are always predefined to provide a default handling of existing trees.

The following pages details the rules for choosing starting translation trees.



7.3 Starting Translation Trees rules

1—1—

45

MO-SMS B-party Starting Tree :
Optional, used to block MO-SMS based on the translation result of analyzing the Bparty number

SMS Prefix Tree :
Used for SMS-SC translations
Default is <1>; modifiable to any user defined tree, typically <207>
This tree allows the translation of SMS-SC address. It is possible to use the SMS
starting tree to perform SMS-SC translations based on modifiers .

Starting Normalization Tree:
Used as First Normalization Tree for Mobile Originating Calls.
Default is <201>; modifiable to any user-defined tree.

Starting Prefix Tree:
Used as First Prefix Translation tree for Mobile Originating Calls, after Normalization.

Starting HLR Prefix tree:
Used to analyse any MSRN returned by the HLR as response of the Send Routing
Information message.
Default is <1>; modifiable to any user-defined tree, typically <203>



MO-SMS B-party Starting Tree (new from 5.0 SP7)
By default MO-SMS B-party checking is not done, The B-party check is performed only if the provisioning
flag “SmsBparty Active” is enabled. By default all MO-SMS B-party numbers are allowed.
The MSC analyzes the MO-SMS B-party number contained in RP-UserData in the prefix translations tree. If
the B-party number matches an entry during the analysis, the MO-SMS is to be blocked, and the
rejection sent to the user with RP-Cause 21 (Short Message Transfer Rejected). Otherwise, if the Bparty number does not match an entry in the prefix tree, the MO-SMS is allowed to proceed.
The B-party check is performed after the analysis of the SC address and prior to any CAMEL or INAP MOSMS query. If the result of the B-party check is to block the SMS, the CAMEL/INAP action is not
performed. If the result of the B-party check is to allow the SMS, then MSC performs the CAMEL/INAP
query. If SCP modifies the B-party address, then MSC does not reanalyze the modified digits. Note that
any digit manipulation of the SMS destination number in the prefix tree(s) does NOT change the value
of the B-party address in the MO-SMS that is sent to the SC, nor in the CDR that is generated. The
routing action upon a match in the SMS B-party prefix tree is also not relevant.
SMS Prefix Tree
This tree allows the translation of SMS-SC address in a tree separate from other translations. The
primary function of SMS-SC translations is to analyze the SMS-SC digits. Any digit manipulation or NOA
modification is preserved in the output of SMSC translation and subsequent GT routing. IMSI modifiers
are supported, but no other modifiers are supported for SMS.



7.3 Starting Translation Trees rules [cont.]

1—1—

46

Starting SCP Prefix tree:
Used to analyse the DestinationRouting Address returned by the SCP as response of
the Initial-DP message, in case of « Connect » or « ETC » message.

Starting Call ForWarding Prefix Tree:
Used to analyse any Forwarded-To-Number received from HLR or VLR.

Starting NPDB Prefix Tree:
Used to analyse a LRN from a number portability result, so that the LRN can be
concatenated with the dialed digits for ported-out numbers.

Starting OSSS Prefix Tree (to be renamed Starting PRBT Prefix Tree):
Used for the PRBT service to add the MSISDN.

Starting International Tree:
Used as first step of International Translation, before International Translation table
is invoked.



SCP Starting Translation Tree
In case of « Continue » message, the standard Prefix Translation Starting Tree is used.
It is also possible to use a M-tree based on IN modifier to perform translation differently according to
SCP address and Service Key.
NPDB Starting Translation Tree
It is used for example in New Zealand Number Portability applications so that the LRN can be
concatenated with the dialed digits for ported-out numbers.
Note that NPDB start tree cannot be provisioned (it is not used) for the North-America market.
WPS Start Tree
This tree allows the operator to populate WPS entries in a separate tree. It may be used in the NAR
(Noth-America Region) market, for the Wireless Priority Service.
E911 Start Tree (new from 4.32 SP1 or 5.1)
When the MSC is handling a mobile origination for a E911 type 1 or type 2 call, the MSC uses the E911
start tree to analyze the resulting E911 digits (ESRK, ESRD, etc). If the start tree has default value 0,
then the MSC uses the standard prefix tree 1 as the default start prefix tree. The specified tree
applies for all E911 originations, regardless of whether a GMLC, INAP, or local translations are used to
determine the routing number to the PSAP. For GMLC case, the E911 digits to be translated and
routed are contained in the MAP Subscriber Location Report Result. For INAP, the digits to be
translated/routed are contained in the Connect message; in case no digits are returned (continue
operation or timeout/error), the fallback emergency number digits are analyzed in the ESRK starting
prefix tree. The prefix tree is also used in case of timeout or error in receiving GMLC or INAP based
E911 digits.


Answer the Questions – Translation Trees IDs

1—1—

47

Associate each Tree ID to the possible usage(s)

Firs t Norm a liz a tion Tre e for MO ca lls
<2 0 1 >
Us e r-d e fin e d Tre e for Norm a liza tion

F irs t P re fix Tra n s la tion Tre e for MO ca lls
<1 >
F irs t P re fix Tra n s la tion Tre e for IS UP ca lls

<2 0 2 >

<2 > to <2 0 0 >

Us e r-d e fin e d Tre e for P re fix Tra n s la tion

S ta rtin g Tre e : In te rn a tion a l P re fix Tre e
<2 0 3 > to <2 0 5 >
S ta rtin g Tre e : HLR , S C P , CF P re fix Tre e

10 min



Answer the Questions – Trunk Group Parameters

1—1—

Can you select the ISUP trunk group parameters which have
an impact on the Translation & Routing process ?


48

10 min


Note: The incoming BSS Trunk Group parameters are similar, except for the Prefix Translator:
for MOC, the Prefix Translator used after Normalization is the Starting Prefix Tree, usually <1>.


Exercise

1—1—

Please do the exercise 1 of your Exercise Book:
„Terminating Call received at the GMSC“

Time allowed: 1h




49

Self-Assessment on the Objectives

1—1—

Please be reminded to fill in the form
for this module
The form can be found in the first part
of this course documentation




50


1—1—

End of Module
T&R Process




51


2—1

Section 2
Translation provisioning
Module 1
Normalization



Blank Page
Translation provisioning — Normalization


2—1—



Document History
Edition

Date

Author

Remarks

2006-10-20

LAPIERRE, Laurent

First version

2007-01-22

LAPIERRE, Laurent


2007-07-23

LAPIERRE, Laurent


01

2007-08-01

LAPIERRE, Laurent


02

2011-03

LAPIERRE, Laurent

Update for 5.1.


2

Objectives

2—1—


Provision Normalization Digit-Tree entry.
State the purpose of Source Modifiers.
Provision Normalization Tree.
State the content of the WCS system logic
for the Normalization process.




3

Objectives [cont.]


2—1—



4

Table of Contents

2—1—

Page

1 Normalization
1.1 Normalization Content (review)
1.2 Normalization D-Tree entry: overview
1.3 Normalization D-Tree entry: identification
1.4 Normalization D-Tree entry: identif. – wild card
1.5 Normalization D-Tree entry: manipulations
1.6 Source Modifiers objects
1.7 Source Modifiers: use in Normalization entry
1.8 Normalization D-Tree entry: output
1.9 Normalization D-Tree entry: System logic
1.10 Normalization D-Tree entry: CBOI & CBOIexHC
1.11 Normalization D-Tree object




7
8
10
11
12
13
15
17
18
20
21
22
23

5


2—1—





6


2—1—

1 Normalization




7

1 Normalization

1.1 Normalization Content (review)

2—1—

8

<201>

Normalization
Normalization
digit manipulation
ODB Check

SCP

IN OCSI DP2

V
L
R

Go at
Prefix
Tree



Normalization is processed for Mobile Originating Calls only.
The T&R process is usually entered in the Normalization D-Tree <201>.
One normalization entry is triggered according to the called number parameters: digit pattern, min/max
number of digits.
The called number is normalized, usually to comply with the E164 International format.
Other parameters (outgoing NOA, etc.) can be set.
The system logic perform VLR checks: Operator Determined Barring checks, Call Barring checks and OCSI
check. If calling party has CAMEL trigger on OCSI-DP2, the SCP will be queried. (this is a call control action)
ODB checks and OCSI checks may be bypassed on request if needed.
The next action is usually to go to the Prefix Translation step, but it‘s possible to loop again to the same or
another Normalization D-Tree (analyze based on Called Party Number), or to a Normalization M-Tree
(analyze based on other modifiers such as IMSI calling party, LAC/CellID, etc).
It‘s also possible to release the call with a cause code directly in the Normalization step.


Exercise

2—1—

Please do the exercice 2 of your Exercice Book:
„Short number translation for Mobile Originating Calls“

Time allowed: 1 h 30




9

1 Normalization


2—1—

10

New D-Tree “Query & table view” in WEM GUI



The Normalization D-Tree entries are found in the WEM GUI in the context:
Office Parameters / Routing and Translation / Wireless Translation / Wireless Normalization / Digit
Translation / <Tree_Id>
The standard Normalization D-Tree is usually the Tree <201>.
This value can be changed in System Parameters: Call Manager / ‘Starting Tree Parameters’ properties.
From the release 5.1, the Digit-Trees entries are now presented with a table in the User Interface, not in the
navigation tree. You may query all entries or display only a subset of entries. It changes only the way to
access, add or modify an entry. The principle and content of a D-tree entry is the same.


1 Normalization


2—1—

11

identification

manipulations

output



In a Normalization D-Tree entry, we can split the object into 3 groups of parameters:
Identification: used to select an entry of the Tree,
Manipulations: digit manipulations, modification of called party number and other characteristics of the
call context,
Output: system logic and output of the Normalization entry.
The Manipulations and the Output parameters may have an impact on the system logic.
These parameters are detailed in the following pages.


1 Normalization

1.3 Normalization D-Tree entry: identification

2—1—

identification


12

Digit pattern,
Min and max number of digits
must match together
To select a Normalization D-Tree entry


To use one D-Tree entry, the incoming Called Number must match
The Digit String (digit pattern).
The Min digit count: minimum number of digits.
The Max digit count: maximum number of digits.
The name represent a free name, for example „National“ or „0+9D“ (for „0 plus 9 digits“).
After the entry is created, the Name and/or the Max Digit Count may be modified, but not the Digit String
or the Min Digit Count.
The system will refuse the creation of 2 overlapping entries.
If one incoming call matches more than one entry, the entry with the longest digit pattern will be selected.


1 Normalization

1.4 Normalization D-Tree entry: identif. – wild card

2—1—

identification

13

Digit String may contain
the ‘?’ wildcard.

The ‘?’ wildcard can be used for each Digit String identification
in Normalization and Prefix Translation entries



The Digit String (Digit Pattern) may contain now the ‘?’ wildcard.
So it is possible for example to create an entry that matches numbers based on the middle or last digits.
The current example: Digit String: ‘??00’, min=4, max=4 will match all the 4 digits-short numbers with ’00’
at the end.
Rules for selecting the best match are:
"the longest pattern" match is chosen.
an explicit single digit is more prioritary than the wildcard digit.
Example 1:
incoming number: 1234.
Entry A: Pattern 123, min 3, max 4.
Entry B: Pattern 12?4, min 4, max4.
The entry B is chosen since it matches 4 digits and not only 3.
Example 2:
incoming number: 1234
Entry A: Pattern 12?4, min 4, max 4.
Entry B: Pattern 1234, min 4, max 5.
The entry B is chosen since the explicit digit “3” is more prioritary than the wildcard.


Answer the question - wild card

2—1—

Look at the two following Normalization entries:

If the incoming
number is ‚1234‘,
which entry will
be selected by the
system?




5 min

14

1 Normalization

1.5 Normalization D-Tree entry: manipulations

manipulations


2—1—

15

Add/Remove digits, Start Position: modify called number.
Digit String Type: set type of call or invoque specific logic.
Echo Cancellation: override incoming trunk group specification.
Tarrif Group & Destination type: choose CDR fields content.


Manipulations allowed in a Normalization D-Tree entry are:
Digit Manipulations:
Add leading Digit Type: system defined for most countries. (NPA-NXX is US-specific)
Digit String Type: characterize the type of call: National / International / Emergency…, or modify the
system logic to invoke a Service: CLIP / CLIR...
Start Position: used in conjunction with Remove/Add leading digits to remove or add digits in the current
cumber. Start Position 1: at beginning, Start Position 255: at the end.
Remove Leading digits: number of digits to remove in the number.
Add Leading digits: digits to add in the number.
The ‚remove digits‘ action is always performed BEFORE the ‚add digits‘ action.
Country Code: the default country code and be quickly added in front of the number with this feature.
Other Manipulations:
International Prefix Length: if not 0, give the length of the International Prefix in the number, so the
system can check properly the International Barings, even if the number still contains a Prefix before the
Country Code.
Echo cancellation: ‚Default As Trunk CFG‘ means that the use of echo cancellation is determined by the
incoming trunk group properties. But it‘s possible to force at on or off the echo cancellation, and to
override the incoming trunk parameter.
CDR / Tariff Group and Destination Type: the Tariff Group and Destination Type will be written in the CDR
for this call. It‘s possible to select them with the Normalization.
Tariff Groups and Destination Types are created in ‚Office Parameters/Billing Parameters‘.
Other steps of Translation may select Tariff Group and Destination Type. During the
Translation&Routing process for one call, if Tariff Group and Destination Types are modified several
times, only the last values will be recorded in the CDR.

1 Normalization

1.5 Normalization D-Tree entry: manipulations [cont.]

manipulations

2—1—

16

Modify Digit Source is a way to insert values from the call context
in the current analyzed called number.
Source Number x are references to Source Modifiers objects.



Digit Manipulations / Modify Digit Source:
Digit Source manipulation is a way to insert values from the call context in the current analyzed called
number.
The following numbers (or parts of) can be added:
MSISDN
Redirecting Number (Forwarding Number)
Original Called Number
Original Dialed Number (pre-translated dialed Number)
CLI
LAC (5 Digits BCD representation)
SAC (5 Digits BCD representation)
Cell ID (5 Digits BCD representation)
MCC (of the originating cell)
MNC (of the originating cell)
IMSI
Carrier ID
IMEI
The digits from the above numbers can be added at the beginning, end of, or anywhere in between the
Called Number in translations.
This is provisioned with “Source Modifier” objects.
Up to 5 different source numbers from above can be selected to modify the specified called party number
in specific order.

1 Normalization


2—1—

17

Source Modifiers are created in Outpulse Maps / Digits Manipulations.
Then they can be used in Digit Outpulse Map entries, and in Normalization or Prefix
Translation entries.



Source Modifiers are created in Outpulse Maps / Digits Manipulations.
Each Source Modifier object:
Extract some digits from a given Source Number (example: IMSI).
Digit to grab: number of digit to grab.
Start Position: define where to grab digits (1=at the beginning).
Default Digits: indicates the digits to use in place of grabbing digits if the Source Number is not available.
Insert position: define where to insert the grabbed digits, when the Source Modifier is used.
Maximum values for Start Position and Digit to grab are:

If no digits are found at the start position then
the provisioning entry is ignored.
If only partial digits are present at the start position then
only the partial digits are inserted.
LAC, Cell ID/SAC are two bytes fields, value from 0 to 65535.
These numbers will be converted to 5 ASCII digits format by
padding leading 0 to make up 5 digits.
For example, if the Cell ID is 1, then the padded Cell ID is ’00001’.

MS IS DN
LAC
Cell ID/S AC
IMS I
Carrie r ID
Redire cting Number
Original Ca lled Numbe r
Original Dia led Numbe r
Calling P arty Number (CLI)
MCC
MNC
IMEI


32
5
5
15
4
32
32
32
32
3
2 or 3
15

1 Normalization

1.7 Source Modifiers: use in Normalization entry

2—1—

18

manipulations

« Insert MCCMNC of the
calling subscriber in front
of the current called
number »


When used in a Normalization tree entry, a Modify Source Number modification refers to an Source Modifier
object defined in “Outpulse Map / Digit Manipulation / Source Modifier”.


Exercise – Source numbers

2—1—

„ Source Modifiers “





19

1 Normalization

1.8 Normalization D-Tree entry: output

2—1—

20

output

Next translation action


Optional Output NOA change


The Route Action will modify the system logic and determine the next step of T&R process:
Check VLR, start at Prefix Trans: check CB and ODB, check IN OCSI, if both passes, go to Prefix
Translation. (usual case)
No VLR check, start at Prefix Trans: do not check CB neither ODB, do not check IN OCSI DP2, go directly to
Prefix Translation (for example for emergency calls).
Skip OCSI-DP2, start at Prefix Trans: check CB and ODB, do not check IN OCSI DP2, go to Prefix Trans.
Skip barring, start at Prefix Tree: do not check CB neither ODB, check IN OCSI DP2, then go to Prefix Tr.
For the 4 above cases, the Prefix Translation Tree used will be the “Starting Prefix Tree”, usually <1>.
Intercept: a cause code must be selected. In most of cases it leads to a call release.
Repeat Wireless Normalization: loop to a Normalization D-Tree or M-Tree. A Tree Index must be selected.
The Outgoing NOA can be modified or chosen:
No Change: not change, the actual NOA value will be kept.
Translated: the NOA value will be determined by the system logic according to the incoming NOA value,
Digit String Type and digit manipulations.
Other value: the NOA can be manually chosen.
International Destination (only if the system is internally configured with
“International Translation Prevention” option off):
If NOA is set to International, and the destination is International (CC do not match default Country
Code), after the Normalization step, the system logic will go directly in the International Prefix Tree
(usually <202>). See Section 2 Module 4 „International Translation“ for more details.


1 Normalization

1.9 Normalization D-Tree entry: System logic

2—1—

21

<201>
Normalization
digit manipulation
ODB Check

OM
Resume Route Action (continue)

SCP

IN OCSI DP2

V
L
R

Release with
Cause Code

<2> to <200>
* user-defined, Normalization D-Tree oror
M-Tree with IMSI, LAC,
M-Tree withwith LAC,
** system-defined
M-Tree IMSI,
SAI, CLI modifiers
SAI, CLI modifiers
modifiers (IMSI, LAC, SAI, CLI)*,
(NOA)**

Repeat
Norm.

Multiple Trees can be looped
(only from D-Tree)


Go at
Prefix
Tree

Release with
Cause Code


Depending of the Route Action, the system will perform this logic:
CB and ODB checks: VLR check of Call Barings and Operator Determined Barings, with the modified number.
IN OCSI DP2: VLR check of OCSI triggers. If OCSI DP-2 trigger is armed:
Digit Outpulse Maps (for Redirecting Party Number, Original Called Party Number, Location Number,
Called Party Number) or Mobile Outpulse Maps: CAP/INAP Calling Party and CAP/INAP Called Party are
used.
The SCP is queried. (Note: query can be done with the dialed number thanks to the internal system
parameter "DP2useDialedNumber")
Depending of the result of the query:
SCP answers „Continue“: the system resume the route action, typically with Prefix Translation Starting
Tree, usually Standard Prefix Tree <1>.
SCP answers „Connect“ or „ETC“: the system jump to Prefix Translation with SCP Starting Translation
Tree (for example SCP Prefix Tree <204>).
If Route Action is set to „Repeat Prefix Translation“, the same or another Normalization tree is used.
The system allows up to 8 trees in a loop.
Please refer to Module 2 Section 5 for details about Normalization based on Modifiers.
‚+‘ dialing: in case of Mobile Incoming Call with ‚+‘ dialing, the system automatically adds the International
Prefix (for example “00” or “011” before the number) and replace the Type of Number INTERNATIONAL with
an input NOA "Unknown" before entering Normalization.


1 Normalization

1.10 Normalization D-Tree entry: CBOI & CBOIexHC

2—1—

22

FPLMN
FPLMN

MS
MS

HPLMN

Outgoing
international
calls (CBOI)

FPLMN

Outgoing international calls except
to the home country (CBOIEXHC)



CBOI: Call Barring Outgoing International Calls.
CBOICexHC: Call Barring Outgoing International Calls except those directed to the Home Country
If the „Home Country“ is only determined by your CC, no other provisioning is needed:
For CBOI and CBOIexHC, the system will compare the CC of the Called party with any “Own MSC” CC. If
a match is found, the call is National, and is allowed.
For CBOIexHC only, the system will compare the CC of the Called Party with the CC of the Calling Party
Number. If a match is found, the call is to the Home Country, and is allowed.
If a country/region CCNDC must be considered „Foreign“ even if CC=your Home Country CC:
in Office Parameters/Mobility Config Parameters/Country Info:
Create one ‚Country/Region ID‘ with barring = International
In Office Parameters/Mobility Config Parameters/Digit Prefix:
Create one or more ‚Digit Prefix‘ associated with the previous Country/Region ID.
If a country/region CCNDC must be considered „Home Country“ even if CC is different from your Home
Country CC:
in Office Parameters/Mobility Config Parameters/Country Info:
Create one ‚Country/Region ID‘ with barring = National
In Office Parameters/Mobility Config Parameters/Digit Prefix:
Create one or more ‚Digit Prefix‘ associated with the previous Country/Region ID.

Note: this logic is used for the corresponding ODB as well.


1 Normalization

1.11 Normalization D-Tree object

2—1—


23


Normalization D-Trees are created in the following context:
Routing and Translation / Wireless Translation / Wireless Normalization / Digit Translation
Normalization D-Tree is identified by:
A unique ID, in the range [1-255]. Typically, ID <2> to <200> can be used for user-defined Trees.
A free name.
The Tree Type is always “Wireless Normalization”.
Once a Normalization D-Tree is created, only the name can be modified, not the ID.
To delete a Normalization D-Tree, it‘s mandatory to have this tree not used by the translation process
actually. (that is, no Normalization entry that loops to this Normalization D-Tree).

Note: for Normalization M-Tree, creation please refer to Section 2 Module 5.



2—1—

for this module




24


2—1—

End of Module
Normalization




25


2—2

Section 2
Module 2
Prefix Translation



Blank Page
Translation provisioning — Prefix Translation


2—2—



Document History
Edition

Date

Author

Remarks

2006-10-20

LAPIERRE, Laurent

First version

2007-01-22

LAPIERRE, Laurent


2007-07-23

LAPIERRE, Laurent


01

2007-08-01

LAPIERRE, Laurent

3JK ref ED1. MNP SRF introduced.

02

2008-07-04

LAPIERRE, Laurent

MNP Ported-in modifications for W4.21,
Inpulse map for W4.4x

03

2009-08-31

LAPIERRE, Laurent

Updated for W5.0

04

2011-03

LAPIERRE, Laurent

Updated for W5.1


2

Objectives

2—2—


Provision Prefix Translation Digit-Tree entry.
Provision Prefix Translation D-Tree.
for the Prefix Translation process.




3

Objectives [cont.]


2—2—




4

Table of Contents

2—2—

Page

1 Prefix Translation
1.1 Prefix Translation content (review)
1.2 NOA Routing
1.3 Prefix Tree entered & CLI inpulse manipulation
1.4 PT D-Tree entry: overview
1.5 PT D-Tree entry: identification
1.6 PT D-Tree entry: manipulations
1.7 System logic: overview
1.8 System Logic: MSRN/HON Check
1.9 PT D-Tree entry: IN NCSI
1.9 PT D-Tree entry: IN NCSI / SCP Node and Bundles
1.10 PT D-Tree entry: Output
1.10 PT D-Tree entry: Output – Call Gapping
1.10 PT D-Tree entry: Output – Insert tone / announcement
1.11 Mobile Number Portability - overview
1.12 System Logic: Mobility Check: NPDB IN solution
1.13 System Logic: Mobility Check: NPDB SRF solution
1.14 System Logic: MSISDN to HLR table
1.15 System Logic: Screening
1.16 System Logic: Blocked Country Code + NPA
1.17 PT D-Tree object




7
8
9
10
12
14
15
17
18
19
20
21
22
23
24
26
27
29
30
31
32

5


2—2—






6


2—2—





7


1.1 Prefix Translation content (review)

2—2—


From
Norm a liza tion

NOA Routing flag
NOA
routing ?
<1>

local MSRN

NOA
in IAM

incoming NOA
Yes

No
Prefix Translation
Prefix Translation
digit manipulation
No

Paging

8

Release with
Cause Code

MSRN/HON Check

SCP

IN NCSI

HLR

MSISDN Check

Continue
Trans


To Routing Step


Prefix Translation content:
The MOC enter the Prefix Translation Starting Tree (usually <1>) after the Normalization step.
The ISUP enters first in NOA Routing. If NOA Routing is enabled in the incoming ISUP Trunk Group, the
Prefix translation step may be bypassed, or the call release, depending of the digits and incoming NOA.
The ISUP calls do not use always the Prefix Translation Starting Tree. If another Prefix Translation <x>
is set in in the incoming ISUP trunk group properties, this one will be used.
One Prefix Translation entry is triggered according to the called number parameters (digit pattern,
the called number may be modified. Other parameters (outgoing NOA, etc.) can be set.
IN NCSI may be triggered on request. If yes, one SCP will be queried.
MSRN/HON check is processes. If the called number is a local MSRN (previously allocated by the same
VMSC), the mobile will be paged.
Mobility check is performed: NPDB and MSISDN check. If portability is not used only the „MSISDN to
HLR“ table is needed. The Mobility check can be bypassed on request if needed.
In a simple example only one D-Tree is used, but on request the system can loop again to the same or
another Prefix Translation D-Tree (analysis based on Called Party Number), or to a Prefix Translation MTree (analysis based on other modifiers such as IMSI calling party, LAC/CellID, etc).
The next action is usually to continue translation at the National or International translation, or to go
directly at Routing step, if the destination is found. (end of translation step with destination found).
The next pages will detail all the system logic associated with Prefix Translation, and the Prefix
Translation Digit Tree provisioning.



1.2 NOA Routing

2—2—

9

Nature of Address Routing is a way to modify or bypass translation:
Only for ISUP incoming calls.
Only for specified ISUP trunk groups with ‘NOA Routing=Enabled’,
Depending on the NOA field in the incoming IAM.

Now NOA Routing may be replaced by NOA Modifier Translation, which
is more efficient and more powerful.


NOA Routing is provisioned in this context:
Office Parameters/Routing and Translation/NOA Routing/Route/
One table can be created for each Translation Group (usually only Translation Group 1 is created).
Each entry in the table :
Is identified by the incoming NOA. (description is a free name).
May modified the called number by removing and/or adding digits.
Modify the translation process with one Route Action:
No Mob. Check Cont. At Orig Routing: bypass the translation process
(Digit Type and Route Index must be provided),
Intercept: release the call (a Cause Code must be provided).
Cont. At prefix Translation: resume the normal Translation process at the Prefix Tree.
If one NOA is not provided in the tree, (or if the tree itself is not created), the call will be accepted
and will go to the Prefix Tree.
Now NOA Routing may be replaced by NOA Modifier Translation, which is more efficient and more
powerful. For NOA Modifier translation details please refer to Section 2 Module 5 « Modifier Based
Translation ».



1.3 Prefix Tree entered & CLI inpulse manipulation

2—2—

10

For Mobile Originating Call: Starting Prefix Tree
(usually Standard Prefix Tree <1>) is used after Normalization.
For ISUP Originating Call: depends on the incoming Trunk:



For an ISUP/BICC incoming call, the Prefix Translator entered if one important parameter of the
incoming Trunk.
Note also that for an ISUP/BICC incoming call, prior to enter the Prefix Translator, it is possible to
modify the Calling Party Number (Calling Line Identity):
Depending on the incoming ISUP/BICC trunk and incoming digits/NOA of the Calling Party Number :
Cli Inpulse Map Index used is a parameter of the incoming Trunk, see above.
For example of CLI Inpulse Map entry, see next slide.
The first purpose of the Cli Inpulse Map is for Local Large Network (LLN – used in China), to be able to
add the area code in the calling party for incoming PSTN call.



1.3 Prefix Tree entered & CLI inpulse manipulation [cont.]

2—2—

CLI inpulse Map entry example:

identification


manipulations


In this CLI Inpulse Map entry example:
If the call is coming from an ISUP/BICC Trunk with CliInpulseMap Index = 2,
If the incoming calling number is NOA=National, begin by digit 8, and has from 8 to 10 digits,
Then:
The incoming calling number is prefixed with leading digits 511,
The NOA is not change,
The CDR will contain the initial Calling Number, not the modified one.
Note that:
Inpulse Digit Type is always „CLI Inpulse map“.
Inpulse Node ID and Inpulse Service Key are not significant and are reserved for a future use.


11


1.4 PT D-Tree entry: overview

2—2—

12

New D-Tree “Query & table view” in WEM GUI



The Prefix Translation D-Trees are found in the WEM GUI in the context:
Office Parameters / Routing and Translation / Wireless Translation / Prefix Translation / Digit
Translation / <Tree_Id>
The standard PT D-Tree is usually the Tree <201>.
This value can be changed in System Parameters: Call Manager / ‘Starting Tree Parameters’ properties.
From the release 5.1, the Digit-Trees entries are now presented with a table in the User Interface, not in
the navigation tree. You may query all entries or display only a subset of entries. It changes only the
way to access, add or modify an entry. The principle and content of a D-tree entry is the same.



1.4 PT D-Tree entry: overview [cont.]

2—2—

13

identification

manipulations

output



The Prefix Tree D-Tree entries are found in the WEM GUI in the context:
Office Parameters/Routing and Translation/Wireless Translation/ Prefix Translation/Digit
Translation/<Tree_Id>.
The standard Prefix Tree is <1>. It is usually the Prefix Translation Starting Tree.
In a Prefix Tree D-Tree entry, we can split the object into 3 groups of parameters:
Identification: use to select an entry of the Tree,
Manipulations: digit manipulations, modification of the called party number and other characteristics
of the call context,
Output: system logic and output of the Prefix Tree entry.
These parameters and the system logic are detailed in the following pages.



1.5 PT D-Tree entry: identification

2—2—

identification

Digit pattern,
min and max number of digits
must match together
to select a Prefix Trans. D-Tree entry
In a Closed Numbering Plan,
Min Digit Cnt = Max Digit Cnt
It’s also possible to use the wildcard ‘?’ in the Digit String pattern



To use one D-Tree entry, the incoming Called Number must match
The Digit String (digit pattern),
The Min digit count: minimum number of digits,
The Max digit count: maximum number of digits.
The name represents a free name, for example „National“ or „0+9D“ (for „0 plus 9 digits“).
After the entry is created, the Name and/or the Max Digit Count may be modified, but not the Digit
String or the Min Digit Count.
The system will refuse the creation of 2 overlapping entries.
If one incoming call match 2 entries, the entry with the longest digit pattern will be selected.
It’s also possible to use the wildcard ‘?’ in the Digit String pattern.
For details about use and rules of the wildcard, please refer to Section 2 Module 1 – Normalization.


14


1.6 PT D-Tree entry: manipulations

manipulations


2—2—

15

Add/Remove digits: modify called number.
Digit String Type: set type of call.
Service Index: invoque IN-NCSI and other specific services.
Echo Cancellation: override incoming trunk group specification.
Carried Id: Carrier Identification Code for equal access.
Tarrif Group & Destination type: choose CDR fields content.
CPC Override: change output Calling Party Category


Manipulations allowed in a Prefix Translation D-Tree entry are:
Digit Manipulations:
Add leading Digit Type: system defined for most countries. (NPA-NXX is US-specific)
Digit String Type: characterize the type of call: National / International / Emergency…
Service Index: for IN-NCSI or modify the system logic to invoke a Service: CLIP / CLIR...
Start Position: used in conjunction with Remove/Add leading digits to remove or add digits in the
current cumber. Start Position 1: at beginning, Start Position 255: at the end.
Other Manipulations:
Echo cancellation: ‚Default As Trunk CFG‘ means that the use of echo cancellation is determined by
the incoming trunk group properties. But it‘s possible to force on or off the echo cancellation, and to
override the incoming trunk parameter.
CDR / Tariff Group and Destination Type: the Tariff Group and Destination Type will be written in
the CDR for this call. It‘s possible to select them with the Normalization.
Tariff Groups and Destination Types are created in ‚Office Parameters/Billing Parameters‘.
Other steps of Translation may select Tariff Group and Destination Type. During the
Translation&Routing process for one call, if Tariff Group and Destination Types are modified
several times, only the last values will be recorded in the CDR.
Carrier Id: Carrier Identification Code for equal access feature. Use is optional.
CPC override: change the Calling Party Category.
Termination Type: set the termination type for the screening feature.


1.6 PT D-Tree entry: manipulations [cont.]

manipulations

2—2—

16

Modify Digit Source is a way to insert values from the call context
in the current analyzed called number.
•The following numbers (or parts of) can be added: MSISDN,
Forwarding Number, Calling Party Number, LAC, SAC, Cell
ID/SAC, MCC, MNC, IMSI, Carrier ID, IMEI.
•The digits from the above numbers can be added at the
beginning, at the end, or anywhere in between the Called Number
in translations.



Manipulations allowed in a PT D-Tree entry are:
Digit Manipulations / Modify Digit Source:
Digit Source manipulation is a way to insert values from the call context in the current analyzed
called number.
MSISDN
Forwarding Number
Calling Party Number
IMSI
Carrier ID
IMEI
This is provisioned with “Source Number” objects.
Up to 5 different source numbers from above can be selected to modify the specified called party
number in specific order.
Please refer to Section 2 - Module 1 – Normalization for details about “Source Number” provisioning.


1.7 System logic: overview

2—2—

Prefix Translation
digit manipulation
No
Paging

local MSRN


MSRN/HON Check

SCP

IN NCSI

HLR


17

MSISDN Check


After the Digit manipulations and other modifications, the Prefix Translation system logic will do the
following:
IN NCSI: to trigger any IN Service, depending of the called number, if it‘s specified in the Prefix tree
entry.
And, depending of the output of the Prefix Translation Tree entry (Route action):
Mobility check: Number portability and local MSISDN check, to determine if the called number is a
local mobile number and trigger the GMSC function, or to recognize any ported-in or ported-out
number if Number Portability is used.
MSRN/HON Check: to check any terminating call at the VMSC (MSRN recognition) and page the mobile,
or to invoke the Handover logic. (Note: MSRN/HON check is not performed in case of route action:
repeat Prefix Translation).
Screening: to prevent some calls depending of the incoming trunk group and the kind of called
number.
Blocked CC+NPA: to prevent some calls to specific destinations.

The following pages will detail the system logic, and the output provisioning of the Prefix Tree entry.



1.8 System Logic: MSRN/HON Check

2—2—

18

P refix translator <x>
local MSRN
MSRN/HO N Check


P aging


MSRN/HON Check
If the call is a Mobile terminating call received at the VMSC, the called number is an MSRN previously
allocated by the same WCS.
Review: The MSRN/HON pools are provisioned in Office Parameters / Mobility Configuration Parameters /
MSRN-HON Distribution.
MSRN/HON check is done after the digit manipulations, with the modified number.
However, the MSRN/HON check is done even if a number processed in Prefix Tree does not match any
entry,.
If the called number is recognized as a local MSRN Number, before the mobile is paged, the Digit
Outpulse Maps (Connected Number , index 1; Calling Party Number in W4.1, index 1) and/or the
Regular Outpulse Map Mobile Outpulse Map: DTAP Calling Party is used.
In case of inter-MSC Handover process, the HON is also recognized at the same step at the MSC target of
the Handover.



1.9 PT D-Tree entry: IN NCSI

2—2—

IN NCSI


19

Connect or ETC: SCP PT <204>
SCP

Continue: Resume Route Action


IN NCSI
If „Service Index: NCSI“ is provisioned into a Prefix Tree D-Tree entry, it means the SCP will be queried,
based on the Called Party analyze. Then, a second Tab „CAMEL-N-CSI“ must be provisioned to select:
The Protocol Type: CAMEL (CAP), INAP-CS1 or INAP-GSM.
The Default Handling: Continue Call or Release the call. (in case of the SCP is not accessible, or there
is no response to the InitialDP operation, or there is an error response to the InitialDP operation.)
The Service Key triggered.
The SCP Node to reach, with Default SCP Node and optionally a SCP Node Bundle.
See next page for details about the SCP Node Bundles
The Service Network List: this service can be restricted to some networks. The service network lists
must be created in Office Parameters / Service Parameters / Service Network List. List „0 All Network
Allowed“ is the default choice. If another list is used, the system check the MCC-MNC of the Calling
Party IMSI. If the MCC-MNC do not match with one of the list, the call is rejected.
Before the WCS send the Initial-DP message to the SCP, the following Outpulse Maps are used:
Digit Outpulse Maps: Redirecting Party Number, Original Called Party Number , Location Number.
And/or Regular Outpulse Maps: Mobile Outpulse Map: CAP or INAP Calling Party, CAP or INAP Called
Party.
When the WCS receive the answer from the SCP, the translation process continue:
In the Starting SCP Tree (eg. <204>) in case of „connect“ or „ETC“ answer.
By resuming the current Route Action, in case of „continue“ answer.


1.9 PT D-Tree entry: IN NCSI / SCP Node and Bundles


2—2—

20


IN NCSI / SCP Bundles

With the SCP bundles, it’s possible to chose the SCP to query according to the Calling Party.

SCP Bundles are provisioned in “Office Parameters / Routing and Translation / Calling IMSI to SCP“.
A SCP Bundle (also named Multiple SCF) contains multiple entries (rows).
Each entry is a range of E.164 calling numbers (ISDNs and/or MSISDN) associated to a specific SCP
node.
Use by a NCSI entry object during the translation step:
The SCP node is derived from the bundle and the calling party if a bundle is given.
If the calling [MS]ISDN is not found in any range of the bundle (or if no bundle is given), the default SCP
Node is used.



1.10 PT D-Tree entry: Output

2—2—

Cont. to
Nat. Trans

output

Mobility Check

Continue at
Orig Routing

21

Cont. to
Intern. Trans

(optionnal)
Mobility Check

Screening & Blocked CC
National Translation
Step

Intern. Translation
Step

to Routing Step



Continue National Translation: Perform Mobility checks, then go to National translation. A National Tree
Selector must be selected (or with ‘0’ the National Tree Selector from the incoming Trunk Group will be used).
It’s possible to have several National tables, see Section 2 Module 3 National Translation for more details.
Continue International Translation: Don’t perform Mobility checks, go to International Starting Tree for
International translation.
Cont. at Orig Routing: Perform Mobility check, then go to Routing Step. The translation is ended with a
„destination found“ action. The Route Index, which is the destination, must be selected.
No Mobility Check, Cont at Orig Routing: do not perform Mobility check, go directly to Routing step. The
translation is ended with a „destination found“ action. The Route Index, which is the destination, must be
selected. Can be used if we are sure the called number is neither a local MSISDN neither a ported-in/ported-out
number.
Cont. at Calling Prefix Trans: a R3.1 legacy feature: loop to another Prefix Tree (Prefix Tree ID must be given),
and identify a Prefix Tree entry by matching the [MS]ISDN Calling Number. This feature is not recommended.
Now it‘s more powerful to use CLI Modifier M-Tree instead.
Cont. ar Calling IMSI Prefix Trans: a R3.1 legacy feature: loop to another Prefix Tree (Prefix Tree ID must be
given), and identify a Prefix Tree entry by matching the IMSI Calling Number. This feature is not recommended.
Now it‘s more powerful to use IMSI Modifier M-Tree instead.
Intercept: release the call (a cause code must be selected).
Repeat Prefix Translation: loop to a Prefix Tree D-Tree or M-Tree. A Tree Index must be selected.
The Outgoing NOA can be modified or chosen:
No Change: not change, the actual NOA value will be kept.
Translated: the NOA value will be determined by the system logic according to the incoming NOA value, Digit
String Type and digit manipulations.
Other value: the NOA can be manually chosen.



1.10 PT D-Tree entry: Output – Call Gapping

2—2—

22

Optional Call Gapping
for specific destinations
output



Since W 5.0, Call Gapping is available to limit call to a specific set of destinations while allowing calls to other
destinations to remain ungapped.
Up to 64 Call Gapping Filter IDs may be defined.
A PT D-Tree entries may use, or not, any Call Gapping Filter (most entries will probably not used any Call
Gapping filter).
Call Gapping filter is available for all Route Action parameters except the intercept action.
Call Gapping Filters are in Office Params / Routing and Translation / Switch Based Call Gapping. Each entry
contains:
Filter ID (1 to 64), and name (free form)
Measurement interval: 5s, 10s, 15s, 20s, 25s, or 30seconds.
Max allowed Call/CCM: from 0 to 65535, max number of calls allowed per CCM pair for the interval. For
example, if “7” is selected, then each active CCM will allow seven calls per interval for that filter. Any
additional calls beyond MaxCalls within the interval are released with the defined cause value defined in
Release Cause.
Filter Activated: a activation/deactivation flag for the call gapping filter.
The Prefix Tree – Digit String drop down list is a read-only list for information, showing the current PT entries
associated to this Call Gap Filter. (The same filter may be used for many PT entries.)
Notes:
Call gapping always allow any priority call (eMLPP or WPS calls).
SMS Originations are not subject to call gapping.



1.10 PT D-Tree entry: Output – Insert tone / announcement

2—2—

23

output

Optional Tone or
Announcement prior to
Routing or GMSC HLR query


Since 5.0, it is possible to play a tone or an announcement prior to the route action :
Action Before Routing is “nothing” per default, but an announcement or a Tone can be chosen.
The feature is not available for an intercept action (but intercept will also lead to a Tone or Announcement in
Cause Code treatments).
If set to Announcement, the announcement id must be chosen.
If set to Tone, the tone and tone duration must be chosen. Duration is in hundred milliseconds (1/10th of
seconds), so here 30 means 3 seconds.
It is then played when the WCS exits prefix translations in order to route the call or to query the HLR. Other
route actions ignore the specified tone or announcement.
Notes:
This feature is mainly designed for the Mobile Originating Calls. In case of terminating call (incoming HON or
MSRN recognition before paging), the tone/announcement is not played.
Re-entering prefix translations (except for “repeat prefix translations” route action) clears any previously
provisioned tone or announcement value for that call. Thus, the tone/announcement is initially cleared when
entering prefix translations from normalization or from an incoming trunk group. It is also cleared when entering
into a new start tree such as HLR, SCP, or CFN.
No announcement is played when DP3 is triggered (CAMEL or N-CSI). The translations phase is suspended during
the interaction with the SCP, and is resumed after the SCP interaction completes. A connect action clears any
previously provisioned tone/announcement since prefix translations is re-entered. Continue and default handling
reuse any tone or announcement that was provisioned for the call. Other SCP results will cause the WCS to
ignore any previously provisioned tone or announcement.



1.11 Mobile Number Portability - overview

2—2—

Number Range
Owner Network
NPDB
IAM

24

Subscription Network
HLRB

MNP-SRF

(MS
ISD
N)

PSTN

MNP-SRF
GMSCA

IAM

(( R N

+) MS
ISDN
)

NPDB

GMSCB

IAM (MSRN)

PORTABILITY CLUSTER


Mobile Number Portability (MNP)
This function allows a mobile subscriber to change his subscription to another PLMN of the same country,
keeping the same subscriber number (MSISDN).
In this case a new IMSI, belonging to the new PLMN, is assigned to the mobile subscriber.
The MNP function is based on a database NPDB (Number Portability Data Base), used to route the calls
(or SMS) to the new subscription network
The mobile number portability is only related to a set of PLMNs « Portability cluster ».
NPDB ACCESS METHODE - 2 possibilities:
Intelligent Network (IN) : the NPDB is located on a SCP.
Use of NPDB Node, LNP order, LRN List in the WCS.
Signaling Relay Function (SRF) : the NPDB is interrogated through a SCCP relay addressed by a
MSISDN.
NPDB Node is seen as HLR Node in the WCS provisioning.



1.11 Mobile Number Portability – overview [cont.]

2—2—

Number Range
Owner Network
NPDB

I
1a.
INDIRECT
ROUTING

AM

Subscription Network
HLRB

MNP-SRF

GMSCA

IAM

MNP-SRF

((RN

+) M
SIS
DN
)
1b.

)
DN
SIS
(M

NPDB

INDIRECT
ROUTING
Other Network
NPDB

GMSCB

MNP-SRF

M
IA

VMSC

25

((

RN

M
+)

IAM (MSRN)

N)
SD
SI

2. DIRECT ROUTING

GMSC

PORTABILITY CLUSTER


Mobile Number Portability (MNP)
In this Example, the calling subscriber is a Mobile Station.
The “other network” can select an indirect Routing, which is the same as previously.
The “other network” can also select a direct routing by interrogation of its NPDB.



1.12 System Logic: Mobility Check: NPDB IN solution

2—2—

26

WCS provisioning:
M ob ility Ch eck

LRN List
(ported-in)

HLR

LNP Order
(ported-out)
Query
NPDB
First

Not
Portable
or
Absent

Query
NPDB

MSISDN to HLR
(query HLR)


Query
HLR
First
MSISDN to HLR
(query HLR)

Query
NPDB


The IN NPDB solution (used for example in US) requires on the WCS:
in Office Parameters / Mobility Config Params / Network Nodes:
One or more Network Nodes of type “NPDB”. Note that the default NPDB Node must be defined in
System Parameters / Profile Manager, as “NPDB NE Index”.
in Office Parameters/Network Parameters:
LRN List table to provision the Local Routing Number for the numbers ported-in from the point of view
of the PLMN. So the system will catch the incoming calls after Direct or Indirect Routing.
LNP Order table to provision the ranges of numbers that can be ported-out. Each MSISDN Pattern can
be declared „Not Portable“, „Query NPDB first“ or „Query HLR First“.
NPDB Node table to route optionally to different NPDB Nodes depending on the called MSISDN.

and

Note: The SRF Signaling Relay Function based-solution NPDB does not requires LRN List
LNP Order provisioning. SRF solution is described next page.

Note: If portability is not implemented, the Mobility check is reduced to “MSISDN to HLR” check.



1.13 System Logic: Mobility Check: NPDB SRF solution

2—2—

27

WCS W4.20 provisioning:
M ob ility Ch eck

MNP SRF
(if ported-in:
remove RN)

HLR

MSISDN to HLR

Found

not Found

"HLR" Node:
NPDB or HLR
(continue
trans lation)
HLR



The SRF Signaling Relay Function NPDB solution requires on the WCS:
in Office Parameters / Mobility Config Params / Network Nodes
MNP SRF Node(s) declared as Network Node(s) of type “HLR”.
Routing Method may be “route by called number”.
in Office Parameters / Routing and Translation:
For ported-out numbers, the HLR Starting Tree (for example <203>) must analyze the Routing
Numbers (RN+MSIDN), to route the call to the subscription network GMSC.
For ported-in numbers, the “MNP SRF” table must contains the Routing Numbers. At the
subscription network GMSC, the WCS can flag the incoming calls as ported-in calls (to avoid for
example infinite loops with the MNP SRF in case of misconfiguration). The WCS removes also
automatically the Routing Number from the (RN+MISDN): the MAP SRI Called Party Address sent to
HLR/NPDB is the MSISDN.
in System Parameters / Profile Manager, some System Parameters may be used:
At the Number Range Owner Network (NRON) GMSC, for a ported-out number, The MNP may reply to
the SRI with (RN+MSISDN) or with (RN) only. In this later case, if MNP_SRF_RN_Enable is enabled, the
WCS NRON GMSC concatenates the RN received by the MNP SRF with the MSISDN.
At the Subscription Network GMSC, for a ported-in number, if MNP_SRF_CC_RN_Enable is enabled, the
WCS insert the RN after the CC in the MSISDN in the SCCP Called Party Address. The SCCP Called Party
Address is then CC+RN+DN. Otherwise it is RN+CC+DN. Note that in all cases, The MAP SRI Called Party
Address is still the MSISDN (CC+DN).


1.13 System Logic: Mobility Check: NPDB SRF solution [cont.]

2—2—

28

WCS W4.21 and above provisioning:
M ob ility Ch eck
Prefix Tree:
RN for ported-in: remove RN digits,
Service Index="MNP Routing Number"

HLR

MSISDN to HLR

Found

not Found

"HLR" Node:
NPDB or HLR
(continue
trans lation)
HLR



The SRF Signaling Relay Function NPDB solution requires on the WCS:
in Office Parameters / Mobility Config Params / Network Nodes
MNP SRF Node(s) declared as Network Node(s) of type “HLR”.
Routing Method may be “route by called number”.
in Office Parameters / Routing and Translation:
For ported-out numbers, the HLR Starting Tree (for example <203>) must analyze the Routing
Numbers (RN+MSIDN), to route the call to the subscription network GMSC.
For ported-in numbers, the regular Prefix Tree must contains entries for the Routing Numbers,
with service index "MNP Routing Number“. The Digit String is stored as RN by the WCS, and the calls
are tags as ported-in calls, to avoid for example infinite loops with the MNP SRF in case of
misconfiguration.
in System Parameters / Profile Manager, some System Parameters may be used:
At the Number Range Owner Network (NRON) GMSC, for a ported-out number, during the creation of
the SRI message to the MNP-SRF, depending of field MNP_SRF_MSISDN_Format, the format and NOA of
the MSISDN in MAP and SCCP message may be changed to national (remove the country code). Values
available are: No Change (default value), National, International.
At the Number Range Owner Network (NRON) GMSC, for a ported-out number, The MNP may reply to
the SRI with (RN+MSISDN) or with (RN) only. In this later case, if MNP_SRF_RN_Enable is enabled, the
WCS NRON GMSC concatenates the RN received by the MNP SRF with the MSISDN.
At the Subscription Network GMSC, for a ported-in number, if MNP_SRF_CC_RN_Enable is enabled, the
WCS insert the RN after the CC in the MSISDN in the SCCP Called Party Address. The SCCP Called Party
Address is then CC+RN+DN. Otherwise it is RN+CC+DN. Note that in all cases, The MAP SRI Called Party
Address is still the MSISDN (CC+DN).


1.14 System Logic: MSISDN to HLR table

2—2—

29

MSRN: HLR PT <203>
HLR

MSISDN Check

FTN: Normalization <201>, then
Call Forwarding PT <205>


MSISDN to HLR table
This table is used to trigger the Gateway MSC function, that is, to query the right HLR is case of incoming
call to a mobile at the GMSC.
MSIDN to HLR table is located in Office Parameters / Routing and Translation.
Each entry of the table is provisioned with:
An MSISDN range, in E.164 International Format (including Country Code).
An HLR number. It can be:
Any HLR provisioned as Network Nodes.
„0 MSISDN Routing“. In this case „HLR number“ can be understood as „Routing Choice“, and the
MSISDN of the called party is used as Global Title. So it will be used in the default Signaling Gateway,
to find a matching entry in Global Title Routing.
The answer of the HLR will be analyzed:
In case of MSRN received, in Starting HLR Tree, for example <203>.
In case of FTN received, first in Normalization Tree, then in Call Forwarding Number Starting
Translation Tree, for example <205>.



1.15 System Logic: Screening

2—2—

Termination Type choosen
From Prefix Trans entry

Termination
Type

Screening
Class

Screening
No

Call permission: Yes


30

Release with
Cause Code


Screening
The screening is a way to prevent some calls depending on:
Screening Class of the incoming trunk Group. (typically „1 Default“)
The Destination Type given by the Prefix Tree entry. (typically „1 Default termination Type“).
The result of the screening is simply:
Call permission: Yes: resume the Translation process.
Call permission: No: release the call (a Cause Code must be provided).
The Provisioning is done in Office Parameters / Routing and Translation / Call Screening, where:
Screening Classes gives:
the list of available Screening Classes.
For each Screening Classes, the list of Termination types with result associated: Call permission:
yes/no.
Termination Type gives:
The list of available Termination Types.



1.16 System Logic: Blocked Country Code + NPA

2—2—

31

B locked C C+N P A
not fou nd


fou nd

Release with
Cau se C ode


Blocked CC+NPA
Blocked CC+NPA is a way to simply prevent all calls to a specific destination.
Typically, this feature can be used to temporarily prevent all calls to a specific destination, without
modifying any Prefix Tree, National and International translation.
Blocked CC+NPA is provisioned in Office Parameters / Routing and Translation / Routing / Blocked
Country Code + NPA.
The pattern must be entered in E.164 International format, including CC.
The destinations can be blocked based on CC only, CCNDC, or any E.164 digit pattern.



1.17 PT D-Tree object


2—2—


Prefix Translation D-Trees are created in the following context:
Routing and Translation / Wireless Translation / Prefix Translation / Digit Translation
Prefix Translation D-Tree is identified by:
A unique ID, in the range [1-255]. Typically, ID <2> to <200> can be used for user-defined Trees.
A free name.
A Tree Type that match the purpose of the tree.
(Standard Prefix Translation Tree for the most usual case).
Once a Prefix Translation D-Tree is created, only the name can be modified, not the ID.
To delete a Prefix Translation D-Tree, it‘s mandatory to have this tree not used by the translation
process actually. (that is, no Prefix Tree entry that loops to this Prefix Translation D-Tree).

Note: for Prefix Translation M-Tree creation, please refer to Section 2 Module 5.


32

Answer the Questions – Prefix Tree output

2—2—

33

Associate each situation to the right Route Action:
in a Prefix Tree entry...

...I use the Route Action:

The destination is
known (GMSC...)

Intercept

This is a normal call,
and destination
is national

Cont at Orig Routing

This call is not
authorized

Continue Nat. Trans.
5 min





2—2—

for this module




34


2—2—

End of Module
Prefix Translation




35


2—3

Section 2
Module 3



Blank Page
Translation provisioning — National Translation


2—3—



Document History
Edition

Date

Author

Remarks

2006-10-20

LAPIERRE, Laurent

First version

2007-01-22

LAPIERRE, Laurent


2007-07-23

LAPIERRE, Laurent


01

2007-08-01

LAPIERRE, Laurent


02

2011-03

LAPIERRE, Laurent

Update for 5.1


2

Objectives

2—3—


Provision National Translation Table entry.
Provision National Translation Table.
for the National Translation process.




3

Objectives [cont.]


2—3—




4

Table of Contents

2—3—

Page

1 National Translation
1.1 System Logic: National Translation
1.2 Translation Group: creation and use
1.3 National Translation entry: Identification and Output




7
8
9
10

5




All is Reserved © Alcatel-Lucent 2007
This pageRightsleft blank intentionally


2—3—

6


2—3—





7


1.1 System Logic: National Translation

2—3—

8

"Continue National
Translation"
National
National
Translation
Translation

Translation group

pattern match

Routing Step
(Destination is found)


Release with Cause Code


System Logic for National Translation:
National translation is entered:
After Prefix Translation step, with „Cont. National Translation“ route action.
The system can have more than one National Translation table. One table per Translation Group is
created.
The Translation Group used may be the one which is set as parameter for the incoming BSS/UTRAN/ISUP
Trunk Group. It can also be overridden is specified by the “Cont. National Translation” Route Action of
the Prefix Tree.
Usually only Translation Group 1 is defined.
In a National Translation Table:
The called number must matches a E.164 National pattern (NDC or NDC+digits).
There is no number of digits check.
As usual if the called number match more than one entry the longest match will be used.
If the number does not match any entry the call will be released with default cause code
„1 Unallocated Number“.
One entry will lead to the following Output possibility:
Intercept: release the call and provide a Cause Code.
Cont. at Orig. Routing: go to Routing Step. The translation is ended with a „destination found“ action.
The Route Index, which is the destination, must be selected.

The next pages will detail the National Table provisioning.



1.2 National Tree Selector: creation and use

2—3—

More than one National Tree Selection may be created :
The National Tree Selector is used for incoming Trunk Groups.




9


1.3 National Translation entry: Identification and Output

2—3—

identification

10

output

When a National Table is opened, to see the table and add or modify an entry:
Select ‚Digit Translation‘ Tab to see the table.
Use „Add Row“ or „Modify row“ to add or modify an entry.
For a National Table entry:
Identification: one entry is identified with a Digit String and a free Name. The Digit String is used to
match any incoming called number with the entry.
Output: the Route Action can be either:
Intercept: release the call and provide a Cause Code.
Cont. at Orig. Routing: go to Routing Step. The translation is ended with a „destination found“ action.
The Route Index, which is the destination, must be selected.

Note: Local Number Portability: LNP Ported office indicates if LNP dip is needed for the
call.
WSS only performs LNP dip if this in an intra-LATA ISUP terminating call.
This is a US-specific feature. In other countries, leave this box unchecked.



2—3—

for this module




11


2—3—

End of Module




12


2—4

Section 2
Module 4
International Translation



Blank Page
Translation provisioning — International Translation


2—4—



Document History
Edition

Date

Author

Remarks

2006-10-20

LAPIERRE, Laurent

First version

2007-01-22

LAPIERRE, Laurent


2007-07-23

LAPIERRE, Laurent


01

2007-08-01

LAPIERRE, Laurent


02

2009-08-30

LAPIERRE, Laurent

Upd for W5.0

02

2011-03

LAPIERRE, Laurent

Upd for W5.1


2

Objectives

2—4—


Provision International Prefix Tree entry.
Provision International Translation Table entry.
for the International Translation process.




3

Objectives [cont.]




2—4—

4

Table of Contents

2—4—

Page

1 International Translation
1.1 System Logic: International Translation
1.2 International Prefix Tree entry
1.3 International Translation table entry




7
8
9
10

5






2—4—

6


2—4—





7


1.1 System Logic: International Translation

2—4—

8

From Normalization
"Go at Prefix Tree"
NOA International
& destination is International (**)
(**): only if internal option
"Prevent International Translation"
is off

From SCP or HLR or VLR

"Continue International
Translation"

NOA International
& destination is International (**)
<202>
International
Prefix Tree
pattern match

digit manipulation
match

no match

International
Translation
table
CC match
match

no
match

Routing Step

Routing Step


Release with
Cause Code


System Logic for International Translation:
International translation is entered:
After Prefix Translation step, with „Cont. International Translation“ route action, or
Only if the internal options “Prevent International Translation” are off:
Directly after Normalization with Route Action “Go at Prefix Trans.”, if NOA of Called Party is
International and destination is International (CC is different from the default Country Code).
When the SCP/HLR/VLR is returning a number with NOA international and destination is international.
International translation implies 2 steps:
International Prefix Tree (example <202>), where the called number can be matched with E.164
International pattern (CCNDC...), to find the destination.
International Translation, where the called number can be matched with CC only, to find the destination.
Important notes:
The International Translation Table is used for internal system logic, so the table must contains only CC,
not any other E.164 pattern (CCDNC...).
The International Prefix Tree can also be a Modifier-Tree.
From the International Prefix Tree it’s possible to repeat Translation to another Tree.
Entries of the International Prefix Tree are optional, that means if any called number does not match any
entry in the International Prefix Tree, the call is not released, but the International Translation Table is
used.
The International Prefix Tree is typically the <202>, but it can be changed with the System Parameter
Starting trees. (International Starting Tree).
The next pages will detail the International Prefix Tree and International Translation provisioning.



1.2 International Prefix Tree entry

identification

2—4—

manipulations

9

output


International Prefix Tree (example <202>) is available in the context:
Office Parameters/Routing and Translation/Wireless Translation/ Prefix Translation / Digit Translation /
202 International Prefix

A International Prefix Tree entry looks like a regular Prefix Tree entry. The differences are:
Only „Route Actions“: ‘go at Orig routing’ and ‘Repeat Prefix Translation’ are can be selected. In both
cases, mobility checks (MSRN/HON and MSISDN) are not performed.
Only „Digit String Type“ International can be selected.
If the incoming called number does not match any entry, the call is not released, but the system uses the
International Translation Table to find a match.

Note: after the last digit manipulation (International Prefix Tree entry with route action
‘go at Orig Routing’, or match found in the International Translation Table), the system logic
performs Screening and Blocked CC, before entering the Routing Step.
For details on Screening and Blocked CC system logic, see Section 2 Module 2.



1.3 International Translation table entry

2—4—

identification

10

output

International Translation Table is available in the context:
Office Parameters/Routing and Translation/Wireless Translation/International Translation
The entries are not presented in the Navigation Tree.
You have to perform a query to see the table with the CC entries.
To add or modify an entry of the International Translation table:
Use „Add“ or „Modify row“ to add or modify an entry.
One International Translation Table entry contains:
Identification: one entry has a free name, and is identified with a Digit String, Min and Max length (min and
max number of digits). The Digit String is always a E.164 International pattern.
Output: Cont. at Orig Routing is implicit, and the „Orig Route Descriptor“ identify the destination. (same as
the „Route Index“ in any Route Action: Cont. at Orig Routing in a Prefix Tree entry). The translation is
ended with a „destination found“ action.



2—4—

for this module




11


2—4—

End of Module
International Translation




12


2—5

Section 2
Module 5
Modifier Based Translation



Blank Page
Translation provisioning — Modifier Based Translation


2—5—



Document History
Edition

Date

Author

Remarks

2006-10-20

LAPIERRE, Laurent

First version

2007-01-22

LAPIERRE, Laurent


2007-07-23

LAPIERRE, Laurent


01

2007-08-01

LAPIERRE, Laurent


02

2009-08-30

LAPIERRE, Laurent

Updte W5.0


2

Objectives


List the Modifiers available for Normalization and Prefix Translation.
Provision Modifiers for Normalization and Prefix Translation.
Provision Prefix Translation M-Tree entry.
Provision Prefix Translation M-Tree.
Provision Normalization M-Tree entry.
Provision Normalization M-Tree.
for Modifier based Translation.




2—5—

3

Objectives [cont.]





2—5—

4

Table of Contents

Page

1 Modifier Based Translation
1.1 Review: Modifier principles for Translation
1.1 Review: Modifiers available for Translation
1.2 System-defined modifiers
1.3 User-defined modifiers
1.3 User-defined Modifier: IMSI Modifier
1.3 User-defined Modifier: CLI Modifier
1.3 User-defined Modifier: LAC Modifier
1.3 User-defined Modifier: SAI Modifier
1.3 User-defined Modifier: IN Modifier
1.4 M-Trees versus D-Trees
1.5 M-Tree use for Normalization: overview
1.5 Normalization M-Tree object
1.5 Normalization M-Tree entry: overview
1.5 Normalization M-Tree entry: identification
1.5 Normalization M-Tree entry: manipulations
1.5 Normalization M-Tree entry: output
1.6 M-Tree use for Prefix Translation: overview
1.6 Prefix Translation M-Tree object
1.6 Prefix Translation M-Tree entry: overview
1.6 Prefix Translation M-Tree entry: identification
1.6 Prefix Translation M-Tree entry: manipulations
1.6 Prefix Translation M-Tree entry: output

2—5—



7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
25
26
27
28
29
30

5






2—5—

6






2—5—

7


1.1 Review: Modifier principles for Translation

2—5—

Modifier-based translation can be used:
to modify normal Normalization and/or Prefix Translation process,
depending on a call parameter which is not the called number, but a
modifier: example location of the call (LAC/CellID, SAI), calling party
identity (IMSI, CLI…), etc,

For Normalization and Prefix Translation:
The list of usable modifiers is not the same for Normalization and Prefix
Translation.
Some Modifiers are System-defined, when the values are normalized (eg
CPC), some others are user-defined for flexibility purposes (eg IMSI
patterns).
User-defined modifiers usable for Normalization and for Prefix Translation
are created only once.
Modifiers are used in Modifier-Trees (M-Tree).
An M-Tree is analyzing from 1 to 5 modifiers in a single table.




8


1.1 Review: Modifiers available for Translation

Obtained from

Used In

IM SIM


N, PT

X M odify translations based on which PLM N
X used to alter translations based on CLI.
X Location Area Code + Cell Range M odifier
X Service Area Indicator M odifier (3G)
X Origin or WM G modifier. Note: PT (R4.2)
X

CLIM
LACM
SAIM
ORM
NOAM

N, PT
N, PT
CGI received from RNC
N, PT
Originating Trunk Properties PT, R
Called Party Number Nature N, PT
of Address
CPCM
CPC in subscriber's profile
PT
(M OC)
OSSSM
OSSS code in VLR
PT
CAM ELM IN trigger information in the VLRT
P


Purpose
User-defined

Code

System-defined

2—5—

X
X
X

Calling Party Category modifier.
PT (VLR only)
different treatment in case of OCSI Camel M ark
present for the calling party (M OC)


N = Normalization
PT = Prefix Tree

The following pages will detail:
The values of system-defined modifiers
The provisioning of user-defined modifiers
The provisioning of M-Trees for Normalization and Prefix Translation
The provisioning of M-Tree entry for Normalization
The provisioning of M-Tree entry for Prefix Translation


9



2—5—

CPC: Calling Party Category:
10 Ordinary calling sub, 11 Calling sub. with priority, …
Usable for Prefix Translation for MOC only, based on the CPC in subscriber’s
profile.

OSSS: Operator Supplementary Service Support:
Each OSSS codes available,
0 OSSS unavailable,
Usable for Prefix Translation step.

Camel:
OCSI Camel Mark absent,
OCSI Camel Mark present.

NOA: Nature of Address:
National, International, Unknown, Subscriber.

There is no need to create explicitly the System-Defined modifiers.



Note: the CPC Calling Party Category modifier from incoming ISUP call can be used only for Routing
Step. (Routing based on Modifiers). See Section 3 Module 4 for details.


10



2—5—

11

for Normalization & Prefix Translation:
IMSI
CLI
LAC
SAI

for Prefix Translation only:
IN service, Orig Routing Modifier (ORM)

All user defined modifiers except ORM
are provisioned in:
Office Parameters / Routing and Translation /
Wireless Translation / Modifiers



Note: The Orig Routing Modifiers are defined in ‚Office Parameters / Routing and Translation / Routing /
Orig Routing / Orig Routing Modifier‘.
An Orig Route Modifier represents the Origination of a call.
Orig Route Modifiers are used in incoming Trunk Groups, for MOC and ISUP incoming calls.
(See Groups / ISUP or BSS)

They are mainly used in Routing Step. For details about Orig Routing Modifiers, see Section 3 Module 3
‚Orig Routing‘.




2—5—

Up to 255 Modifiers
One modifier entry is a IMSI pattern.
Many IMSI patterns may belong to a single modifier.
Modifier 255 is the default one.



IMSI modifiers for Normalization and Prefix Translation are created in
Office Parameters / Routing and Translation / Wireless Translation / Modifiers / IMSI Translation
Modifier.
The name is free, and is given for the single IMSI pattern, not the modifier.
The Default IMSI modifier may be used for:
All other IMSIs
No IMSI provided (I.e. ISUP incoming call)


12



2—5—

Up to 255 Modifiers
One modifier entry is identified by:
Nature of Address, CLI pattern, Min and Max digit Count
A free name




CLI modifiers for Normalization and Prefix Translation are created in
Office Parameters / Routing and Translation / Wireless Translation / Modifiers / CLI Translation
Modifier.
The Default CLI modifier may be used for:
All other CLIs
No CLI provided


13



2—5—

14

Up to 65535 Modifiers
MCC/MNC, LAC, CellID range
A free name




LAC modifiers for Normalization and Prefix Translation are created in
Office Parameters / Routing and Translation / Wireless Translation / Modifiers / LAC Translation
Modifier.

Notes:
The LAC drop-down list presents to you the list of „GSM LAC or CELL“ objects created in Mobility
Config. Parameters. So the same LAC may be presented several times if the LAC is split over 2 BSCs, or
is declared with several ranges of cells. But only the value of the LAC is significant here.
For LAC modifiers created by the Command Line Interface, only the value of the LAC is asked, no
reference to any „GSM LAC or CELL“ object is needed.




2—5—

Up to 65535 Modifiers
MCC/MNC, LAC, SAC Range.
A free name




SAI modifiers for Normalization and Prefix Translation are created in
Office Parameters / Routing and Translation / Wireless Translation / Modifiers / SAI Translation
Modifier.
Notes:
The SAI field gives the list of LACs: the LAC has to be chosen.
The CellID range does represent the SAC range for the modifier entry.


15


1.3 User-defined Modifier: IN Modifier

Up to 255 Modifiers
The SCP Node (previously created as a Network Node), A Service Key.
A free name.

Modifier 255 is the default one



IN modifiers for Prefix Translation are created in
Office Parameters / Routing and Translation / Wireless Translation / Modifiers / IN Translation
Modifier.


2—5—

16


1.4 M-Trees versus D-Trees

2—5—

17

Modifiers are used inside Modifier Trees
Similarities between M-Trees and D-Trees, for translations:
D-Trees and M-Trees shares the same range: IDs <1> to <255>
In Normalization or in Prefix Translation step, we can loop in the same way
between Digit Trees and Modifier Trees.
Both M-Trees and D-Trees will modify the called number and next step of
translation.

Differences between M-Trees and D-trees, for translations:
M-trees entries are identified with call context modifiers, D-trees entries
are identified with called party number prefix pattern.
Manipulations and output possibilities in M-Tree are reduced compared to DTree entries.





1.5 M-Tree use for Normalization: overview

2—5—

18

M
obile Originating Call
<201>
Normalization
digit m
anipulation
ODB Check
SCP

IN OCSI DP2

V
L
R

<2> to <200>
* user-defined, Normalization D-Tree oror
M
-Tree with IM LAC,
SI,
M M withwith LAC,
-Tree
SI,
** system-defined
-Tree IM
SAI, CLI modifiers
modifiers (IM SAI, CLI modifiers
SI, LAC, SAI, CLI)*,
(NOA)**

Repeat
Norm.

M
ultiple Trees can be looped

(only from D-Tree)


Go at
Prefix
Tree

<1>


From any Normalization M-Tree or D-Tree, it is possible to loop to another or the same Normalization MTree or D-Tree.
A maximum of 8 loops for the Normalization step is allowed.
A Normalization M-tree will analyze from 1 to 4 modifiers together: IMSI, LAC, SAI, CLI, NOA.
Limitation: LAC and SAI cannot be analyzed together in a single M-Tree.
Like a Normalization D-tree entry, a Normalization M-tree entry can modify the called number and
modify further steps of Translation & Routing.



1.5 Normalization M-Tree object


2—5—

19


M-Trees for Normalization are created in
Office Parameters / Routing and Translation / Wireless Translation / Wireless Normalization / Modifier
Translation.
Parameters for a Normalization M-Tree:
Translator Identifier: from 1 to 255. Shared with all M and D-Trees for Normalization and Prefix Trees.
Typically <2> to <200> can be user-defined.
Name : free name
Selector: from 1 to 5 modifiers together, in the list of available modifiers for Normalization.

The example above shows the creation of one Normalization M-Tree that will modify normalization
depending on 2 modifiers: IMSI and LAC.



1.5 Normalization M-Tree entry: overview

identification

manipulations

2—5—

20

output


Normalization M-trees entries are created in
Office Parameters / Routing and Translation / Wireless Translation / Modifier Translation / Translation
/ Wireless Normalization / <Tree_ID>.
In a Normalization M-Tree entry, we can split the object into 3 groups of parameters:
Manipulations: digit manipulations to modify called party number,
Output: system logic and output of the Normalization entry.



1.5 Normalization M-Tree entry: identification

identification


2—5—

21

All modifiers must match
to select a Normalization M-Tree entry


To use one M-Tree entry, the incoming Call Context parameters must match all modifiers values.
In the example above, IMSI pattern must match the IMSI Modifier 253, and Location of the call must match
the LAC Modifier 3, to select this Normalization M-Tree entry.



1.5 Normalization M-Tree entry: manipulations

manipulations

2—5—

22

Modify Digit Source : insert values from the call context in the
current analyzed called number.



Manipulations allowed in a Normalization M-Tree entry are:
Properties:
system can check properly the International Barings, even if the number still contains a Prefix before
the Country Code.
Digit Source manipulation is a way to insert values from the call context in the current analyzed
called number.
MSISDN, Forwarding Number, Calling Party Number, LAC (5 Digits BCD representation), SAC (5 Digits
BCD representation), Cell ID (5 Digits BCD representation), MCC (of the originating cell), MNC (of the
originating cell), IMSI, Carrier ID, IMEI
This is provisioned with “Source Number” objects.
Up to 5 different source numbers from above can be selected to modify the specified called party
number in specific order.



1.5 Normalization M-Tree entry: output

2—5—

output



Intercept: release the call (a cause code must be selected).
Repeat Wireless Normalization: loop to a Normalization D-Tree or M-Tree. A Tree Index must be
selected.
Since W5.0, Action Before Routing (Nothing, Announcement, Tone) may be used to play a tone or a
announcement prior to the route action.
This feature has been described in the Prefix Translation chapter.


23

Answer the Question – Normalization M-Tree entry

Look at this example.
Try to guess what can be the purpose of such an entry.




2—5—

24

5 min


1.6 M-Tree use for Prefix Translation: overview

2—5—

25

From Normalization step,
ISUP Originating Call,
Network origin

Prefix Translation
digit manipulation
No
Paging

local MSRN

MSRN/HON Check

SCP

IN NCSI

HLR

MSISDN Check

<2> to <200>
* user-defined,
** system-defined
modifiers

P refix trans IMS I, or
P refix tr. D-Tree or M-tree
M-Tree with D-TreeCP C,
M-Tree S AI, CLI, OS S S
with (IMS I, LAC,I, CP C,,
LAC, with IMS S AI,
LAC, service, ORM)*, ,
CLI, INI,SIN sCLI, modifiers
OCS AI, erv. OS S S
OCS I, IN S S , modifiers
(CP C, OSserv.Camel,

Repeat
P refix Tr.

Continue
Trans

(only from
D-Tree)

National or
International
Translation

Multiple Trees
can be looped
Release with
Cause Code

Release with
Cause Code

go at Orig
Routing

go at Orig
Routing

ROUTING



From any Prefix Translation M-Tree or D-Tree, it is possible to loop to another or the same Prefix
Translation M-Tree or D-Tree.
A maximum of 8 loops for the Prefix Translation step is allowed.
A Prefix Translation M-tree will analyze from 1 to 5 modifiers together: IMSI, LAC, SAI, CLI, IN Service,
ORM, CPC, OSSS, Camel, NOA, OICK, ST, TICK.
Limitation: LAC and SAI cannot be analyzed together in a single M-Tree.
Like a Prefix Translation D-tree entry, a Prefix Translation M-tree entry can modify the called number
and modify further steps of Translation & Routing.



1.6 Prefix Translation M-Tree object


2—5—

26


M-Trees for Prefix Translation are created in
Office Parameters / Routing and Translation / Wireless Translation / Prefix Translation / Modifier
Translation
Parameters for a Prefix Translation M-Tree:
Translator Identifier: from 1 to 255. Shared with all M and D-Trees for Normalization and Prefix Trees.
Typically <2> to <200> can be user-defined.
Name : free name
Selector: from 1 to 5 modifiers together, in the list of available modifiers for Prefix Translation.

The example above shows the creation of one Prefix Translation M-Tree that will modify normalization
depending on one modifier: IMSI.



1.6 Prefix Translation M-Tree entry: overview

identification

manipulations

2—5—

output


Prefix Translation M-trees entries are created in
Office Parameters / Routing and Translation / Wireless Translation / Prefix Translation / Modifier
Translation / <Tree_ID>.
In a Prefix Translation M-Tree entry, we can split the object into 3 groups of parameters:
Manipulations: digit manipulations, modify called party number and other characteristics of the call
context,
Output: system logic and output of the Prefix Translation entry.
The Output parameters may have an impact on the system logic.
These parameters and the system login are detailed in the following pages.


27


1.6 Prefix Translation M-Tree entry: identification

identification


2—5—

All modifiers must match
to select a Prefix Translation M-Tree entry


To use one M-Tree entry, the incoming Call Context parameters must match all modifiers values.
In the example above, only one modifier is used.


28


1.6 Prefix Translation M-Tree entry: manipulations

2—5—

29

CPC Override: change output Calling Party Category

manipulations


Modify Digit Source : insert values from the call context in the
current analyzed called number.

Usual Digit Manipulations:
system can check properly the International Barings, even if the number still contains a Prefix before
the Country Code.
Other Manipulation:
CPC override: change the Calling Party Category.
Digit Source manipulations:
The following numbers (or parts of) from the call context can be inserted in the current analyzed
number:
MSISDN, Forwarding Number, Calling Party Number, LAC (5 Digits BCD representation), SAC (5 Digits
BCD representation), Cell ID (5 Digits BCD representation), MCC (of the originating cell), MNC (of the
originating cell), IMSI, Carrier ID, IMEI



1.6 Prefix Translation M-Tree entry: output

2—5—

output



Intercept: Release the call. (a Cause Code must be selected).
Repeat Prefix Translation: loop to a Prefix Tree D-Tree or M-Tree. A Tree Index must be selected.
Since W5.0, Action Before Routing (Nothing, Announcement, Tone) may be used to play a tone or a
announcement prior to the route action.
This feature has been described in the Prefix Translation chapter.


30

Exercise – “Modifier Tree”

Please do the exercise 4 of your Exercice Book:
„Modifier Tree for Normalization“





2—5—

31


for this module




2—5—

32


2—5—

End of Module
Modifier Based Translation




33


3—1

Section 3
Routing provisioning
Module 1
Route Liste & Bundles



Blank Page
Routing provisioning — Route Liste & Bundles


3—1—



Document History
Edition

Date

Author

Remarks

2006-10-20

LAPIERRE, Laurent

First version

2007-01-22

LAPIERRE, Laurent


2007-07-23

LAPIERRE, Laurent


01

2007-08-01

LAPIERRE, Laurent


02

2009-08-31

LAPIERRE, Laurent

Update for W5.0


2

Objectives

3—1—


Provision Route List.
Provision Bundle.
State the purpose of Route List in the T&R process
State the content of the WCS system logic for the Route List step.




3

Objectives [cont.]


3—1—




4

Table of Contents

3—1—

Page

1 Route List & Bundle
1.1 Routing step and Route List (review)
1.2 Route List: System Logic
1.2 Route List: Overview
1.2 Route List: Identification & properties
1.2 Route List: Route type parameters
1.3 Trunk Group Bundle




7
8
9
10
11
12
13

5






3—1—

6


3—1—





7


1.1 Routing step and Route List (review)

3—1—

From Translation


Routing
Route Immediately
Release with
Cause Code
Route List
and Cause Code)

resources & translated number

Outpulse MAP



When the translation ends with a “destination found” action, the Routing step is invoked.
Based on the destination, the origination of the call, and optionally other call context parameters, the
routing step will either:
Select a Route List for the call
Release the call with a Cause Code.
If the routing has selected a Route List, this route list will be used to select an outgoing resource.
The logic of the Routing step will be discussed later. Before that, we will see what is a Route List, and
how to select the outgoing resources for a call.


8


1.2 Route List: System Logic

3—1—

9

From Routing
Route List

Route Type 1:
-Bundle or Trunk
-Outpulse Maps
Route Type 2:
-Bundle or Trunk
-Outpulse Maps

Trunk A

Outpulse
MAP s

Outgoing IAM

Bundle:
Trunk B
Trunk C

Outpulse
MAP s

Outgoing IAM

...
...
...
Route Type 8:
-Bundle or Trunk
or Dis c onne c t
-Cause Code


Release with
Cause Code


A Route List is an object that groups some outgoing resources, to help the system to choose one.
A Route List contains:
Up to 8 Route Types.
The Route Types are ordered. Each of them is composed of either:
A reference to a Trunk Group, and some Outpulse Maps associated.
A reference to a Trunk Group bundle, and some Outpulse Maps associated.
A “disconnect” action: release with a cause code.
The System Logic is simple:
When a Route List is selected, the system try to look at the Route Type 1:
If Route Type 1 is a Trunk Group, the system will try to reserve a resource in this trunk group.
If this is possible, the outgoing resource is reserved and the call is routed.
If this is not possible, the system passes to Route Type 2.
If Route Type 1 is a Trunk Group Bundle, the system will use the load sharing fashion of the bundle to
try to reserve a resource in one specific Trunk Group of the Bundle.
If this is possible, the outgoing resource is reserved and the call is routed.
If this is not possible, the system passes to Route Type 2.
If Route Type 1 is a disconnect action, the call is released.
If the system has passed to Route Type 2, the same logic is used.
Usually the Disconnect action is the last Route Type used.
If all Route Types fails, the call will be released with the default cause code “No Route to Destination”.
The Route Type “Queue” is reserved for queuing calls, only in case of WPS (US-Specific feature).


1.2 Route List: Overview

3—1—

properties

identification

Route types


The Route Lists are found in the WEM GUI in the context :
Office Parameters / Routing and Translation / Route List
A query is needed to display the route lists.
As usual, the ‘add’ button can be used to add a Route List.
A Route List is an object that groups some outgoing resources, to help the system to choose one.
A Route List contains:
Some identification and global parameter,
Up to 8 Route Types.



10


1.2 Route List: Identification & properties

3—1—

identification

A Route Type is simply identified
with an ID and a name

properties

11

Global properties for a Route List



A Route Type is identified by a unique ID and a free name.

The global properties part contains now only one parameter: “Look Ahead” : This feature allows a look
ahead between the originating side and the terminating side of the network for determining the status of
the terminating side without the need to establish a connection.
For more information, refer to standards: Q.2724.1 and B-ISDN User Part (CS2.1)



1.2 Route List: Route type parameters

3—1—

12

For a Route Type “Trunk Group”:
-Trunk Group selected.
-Digits Outpulse Index for the digit outpulse map.
-Predefined CLI to be optionnaly used (if no CLI present)
-All other Outpulse values are the regular Outpulse Maps
Associated with the Route List

Route type 1



Each Route Type contains in “type” the action associated to this Route Type:
Trunk Group: The trunk must be selected in “Value”.
Bundle: The trunk group bundle must be selected in “Value”.
Disconnect: release the call; a Cause Code must be selected in “Value”.
Queue: reserved for the WPS service.
Empty: route type not used.
If the type is “Trunk Group” or “Bundle”:
It’s possible to select the regular ISUP/BICC Called Party Number Outpulse Map that will be used
(Called Outpulse), as well as the Calling Party Number (CLI Outpulse Map), Redirecting Party Number
(RN Outpulse Map) and Original Called Party Number (OCN Outpulse Map)
It’s also possible to select the Digit Outpulse Map that will be used (Digit Outpulse Index), to modify
some or all of the following numbers with a single Map Index:
Redirecting Party Number
Called Party Number
Original Called Party Number
Location Number
For details about Outpulse Maps, please refer to the Section 3 Module 2 “Outpulse Maps”.
Bundles are detailed in the following pages.



1.3 Trunk Group Bundle


3—1—

13


Bundles are defined in Office Parameters / Routing and Translation / Trunk Group Bundles.
Each bundle contains Trunk Groups, each Trunk Group do have an Order and a Weight:
Order is unique: two trunks in a bundle can not have the same order.
Weight represents the relative weight of the Trunk Inside the bundle.
System Logic: If for one call a bundle is selected:
Based on order and weight, the system will select for this call a Trunk Group of the Bundle.
If one resource is available on this trunk, this resource will be reserved.
If no resource is available on this trunk, the system will pass to the next trunk in the Bundle.
If no resource is available on all the trunks of the bundle, the system will pass to the next Route Type.
In the above example, for the flow of calls that selects this Bundle, the system will choose the following
trunks: 5077, 5067; 5077, 5067; … …
Each Trunk Group can be associated to Outpulse Maps:
CLIOutpulse for Calling Party Number (reference to a CLI Outpulse Map Index)
CldOutpulse for Called Party Number (reference to an ISUP Outpulse Map Index)
DgtOutpulse for Digit Outpulse map (reference to a Digit Outpulse Map to change Redirecting Party
Number, Calling Party Number, Called Party Number, Original Called Party, Number Location Number)
Choosing Outpulse Maps for each Trunk in a Bundle is optional: if not chosen, the Outpulse Maps chosen
in the Route List/Route Types are used. If chosen, Outpulse Maps for each Trunk in a Bundle takes
priority over information in the Route List/Route Types.



3—1—

for this module




14


3—1—

End of Module
Route Liste & Bundles




15


3—2

Section 3
Module 2
Outpulse Maps



Blank Page
Routing provisioning — Outpulse Maps


3—2—



Document History
Edition

Date

Author

Remarks

2006-10-20

LAPIERRE, Laurent

First version

01

2007-08-01

LAPIERRE, Laurent


02

2009-08-31

LAPIERRE, Laurent

Update for 5.0

03

2011-01-31

LAPIERRE, Laurent

Update for 5.1


2

Objectives

3—2—


Provision Outpulse Maps entries.
Provision Digit Outpulse Maps entries.
Provision Source Modifiers entries.
State the list of Outpulse Maps usable for ISUP IAM/BICC message
State the content of the WCS system logic for the
Outpulse Map step
State the list of Outpulse Maps usable for DTAP/INAP/CAP messages
State the list of Digit Outpulse Maps usable for
ISUP/BICC/CAP/INAP/DTAP messages




3

Objectives [cont.]


3—2—




4

Table of Contents

3—2—

Page

1 Outpulse Maps
1.1 Outpulse Maps: principles (review)
1.2 Regular Outpulse Maps for ISUP/BICC (review)
1.3 ISUP Outpulse Map (ISUP/BICC)
1.4 ISUP Outpulse Map entry
1.5 CLI Outpulse Map (ISUP/BICC)
1.6 RN Outpulse Map (ISUP/BICC)
1.7 OCN Outpulse Map (ISUP/BICC)
1.8 Mobile Outpulse Map for paging (DTAP)
1.9 Mobile Outpulse Maps for SCP query (CAP/INAP)
1.10 Digit Outpulse Map: principles
1.11 Digit Outpulse Map: scope
1.14 Source Modifier entry
1.15 Digit Outpulse Map query
1.16 Digit Outpulse Map: possible usage
1.17 Digit Outpulse Map entry
1.18 Digit Outpulse map entry: use of Source Modifiers




7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
25
27

5


3—2—





6


3—2—

1 Outpulse Maps




7

1 Outpulse Maps

1.1 Outpulse Maps: principles (review)

3—2—

8

Purpose of the Outpulse Maps:
Allows digit manipulation and change of properties for different numbers
(Called Party Number, Calling Party Number, etc.)
After all translation & routing steps
Just before an outgoing message is sent in ISUP, BICC, CAP, INAP, or DTAP.

2 different kinds of Outpulse Map objects:
Regular Outpulse Maps: legacy Outpulse Maps.
Digit Outpulse Maps: new feature, more powerful.

Following pages will detail:
Regular Outpulse Maps for ISUP/BICC.
Regular Outpulse Maps for INAP, CAP and DTAP.
New Digit Outpulse Maps for ISUP/BICC, INAP, CAP and DTAP.



Note:
Each operator should use either regular OM either Digit OM, for the fields (numbers) that are common to
Regular and Digit Outpulse Maps.
If there is a provisoning conflict risk between the two Outpulse Map systems, a warning is displayed on the
GUI screen.
Conflicts may arise when two manipulations (regular OM and digit OM) are provisioned for the same digit
pattern. In this case manipulations in digit Outpulse Map takes precedence on "regular" outpulse map.


1 Outpulse Maps

1.2 Regular Outpulse Maps for ISUP/BICC (review)

3—2—

9

From Route Lis t
Outgoing res s ouces choos en

IS UP Outpuls e Map

Change NOA & Format digits
ISUP/BICC Called Party Number

CLI Outpuls e Map

ISUP/BICC Calling Party Number

RN Outpuls e Map

ISUP/BICC Redirecting Party Number

OCN Outpuls e Map

ISUP/BICC Original Called Party Number


Outgoing
IAM
mes s age


For ISUP/BICC outgoing calls, Outpulse Maps are used:
After the Route List step (the selected Route Type has chosen the Outpulse Maps)
Before the outgoing IAM is sent.

For the outgoing IAM messages, 4 outpulse Maps are used, to change NOA and digit format of 4 fields of
the outgoing Initial Address Message.
The following pages will detail the Outpulse Maps used for ISUP/BICC outgoing IAM messages.
Note: Regular Outpulse Maps for DTAP, CAP and INAP (named Mobile Outpulse maps) are detailed later in
this Module:
Paging result, for Setup message:
Mobile Outpulse Map / DTAP Calling number: change NOA/TON and digits format of DTAP Calling
number.
This Outpulse Map is provisioned for all Setup messages.
Query IN/SCP result, for Initial-DP message:
Mobile Outpulse Map / CAP or INAP Called Party number: change NOA and digit format of Called Party
Number.
Mobile Outpulse Map / CAP or INAP Calling Party number: change NOA and digit format of Calling
Party Number.
Theses Outpulse Maps are provisioned per SCP address basis.


1 Outpulse Maps

1.3 ISUP or BICC or SIP Outpulse Map


3—2—


ISUP or BICC or SIP Outpulse Maps are located in Office Parameters / Outpulse Maps:
Different Outpulse Maps can be created, with a unique Outpulse Map number.
We have to query outpulse maps entries to see the outpulse map entries.
So to see all entries associated to Outpulse Map 1, we can query on the basis “Outpulse Map=1”.
The Outpulse Map used is selected in the Route List, and can be different for each Route Type of the
Route List.
Each Outpulse Map entry will modify the NOA and digit format in one way, depending of the incoming
NOA, incoming digit string pattern, and min/max number of digits.
As usual, use “Modify Row” and “Add” buttons to modify or create an ISUP Outpulse Map entry.


10

1 Outpulse Maps

1.4 ISUP or BICC or SIP Outpulse Map entry

identification

3—2—

manipulations

11

CPC change


Each ISUP Outpulse Map entry may be split into 3 groups of parameters; the system logic is the following:
Identification: used to select an entry of the Outpulse Map:
Outpulse Map value: ID of the Outpulse Map,
Name: free name,
Input NOA,
Input Digit String,
Min / Max number of digits,
Input NOA, digit string, Min/Max refers to output of all the previous Translation Steps.
Manipulations: NOA and digit format manipulations:
Rm Leading digits: number of digits to remove.
Add Leading digits: digits to add in front of the number. (eventually, after digits removing).
Operation (1 to 32) with optional Cause Value (1 to 32): Outpulse operations. Most of the values are not
used. Typically, the Operation 1 is “dialed number” to outpulse the called number (after optional
remove/add modifications), and Operation 2 is “Outpulse End” to end the outpulse.
Nature of Address: outgoing Nature of Address may be set.
OLI: Originating Line Information may be changed. (OLI list are provisioned in Office Parameters /
Routing and Translation / OLI List)
CPC Change:
Call Override: Capability to change the outgoing CPC for all calls except priority calls.
CPC Override Priority: Capability to change the outgoing CPC in case of priority call.


1 Outpulse Maps

1.5 CLI Outpulse Map (ISUP/BICC)

3—2—

identification

12

manipulations


CLI Outpulse Map for ISUP/BICC Calling Number is located in Office Parameters / Outpulse Maps.
CLI Outpulse Maps are manipulated in the GUI the same way as the ISUP Outpulse Maps.
CLI Outpulse Maps entries are more simple and each entry contains:
Outpulse Map value: ID of the Outpulse Map.
Name: free name.
Input NOA.
Input Digit String
Min / Max number of digits.
input NOA, digit string, Min / Max refers to output of all the previous Translation Steps.
Manipulations: NOA, digit format and other manipulations:
Digit Manipulation:
Presentation Restriction Indicator, Screening Indicator and Number Incomplete Indicator can be set :
Presentation indicator: Presentation allowed / Presentation Restricted / No change.
Screening Indicator: User provided, not verified (national use) / User provided, verified and passed /
User provided, verified and failed (National use) / Network provided / No change.
Number Incomplete Indicator: Complete / Incomplete / No change.
CDR capture: Override in CDR: if yes the modified number will be captured in the Call Data Record.
If no, the initial number before modification will be captured. The default value is set to Yes for all
digit types except for Calling Number, and set to No for Calling Number.

1 Outpulse Maps

1.6 RN Outpulse Map (ISUP/BICC)

3—2—

identification

manipulations


RN Outpulse Map for ISUP/BICC Redirecting Party Number is located in Office Parameters / Outpulse
Maps.
RN Outpulse Maps are manipulated in the GUI the same way as the ISUP Outpulse Maps.
Each RN Outpulse Map entry contains:
Name: free name.
Input NOA.
Input Digit String
input NOA, digit string, Min/Max refers to output of all the previous Translation Steps.
Digit Manipulation:
Presentation Restriction Indicator (APRI) can be set :
Override OCN: If Yes, the current RN Outpulse Map will override the Original Called Number field as
well.
CDR capture :
Override in CDR: if yes the outpulsed RN number will be captured in the Call Data Record,
if no, the initial RN will be captured in the Call Data Record.

13

1 Outpulse Maps

1.7 OCN Outpulse Map (ISUP/BICC)

3—2—

identification

14

manipulations


OCN Outpulse Map for ISUP/BICC Original Called Party Number is located in Office Parameters / Outpulse
Maps. OCN Outpulse Maps are manipulated in the GUI the same way as the ISUP Outpulse Maps.
Each OCN Outpulse Maps entry contains:
Name: free name.
Input NOA.
Input Digit String
input NOA, digit string, Min/Max refers to output of all the previous Translation Steps.
Digit Manipulation:
Presentation Restriction Indicator (APRI) can be set :
CDR capture:
Override in CDR: if yes the outpulsed number will be captured in the Call Data Record.
If no the original number before outpulse modifications will be captured in the Call Data Record.


1 Outpulse Maps

1.8 Mobile Outpulse Map for paging (DTAP)

3—2—

identification

15

manipulations


Mobile Outpulse Maps are not really part of Routing step of T&R process, since they are used for a “Call
Control” results of Translation, that leads to an DTAP, CAP or INAP message.
They are located in Office Parameters / Outpulse Maps, and are manipulated in the GUI the same way as
the ISUP Outpulse Maps. The single “Mobile Outpulse Map” object contains several types of Outpulse
Maps, used for different cases:
Paging result of translation: ‘DTAP Calling Party Number’ type of Mobile Outpulse Map entry:
Name: free name.
Input NOA, Input Digit String, Min / Max number of digits. They refers to output of all the previous
Translation Steps.
Query SCP result of translation: see next page for details.


1 Outpulse Maps

1.9 Mobile Outpulse Maps for SCP query (CAP/INAP)

3—2—

identification

16

manipulations


Mobile Outpulse Maps are not really part of Routing step of T&R process, since they are used for a “Call
Control” results of Translation, that leads to an DTAP, CAP or INAP message.
They are located in Office Parameters / Outpulse Maps, and are manipulated in the GUI the same way as
the ISUP Outpulse Maps. The single “Mobile Outpulse Map” object contains several types of Outpulse
Maps, used for different cases.
Query SCP result of translation: 6 type of Outpulse Map entries: CAP Calling Party Number, CAP Called
Party Number, CAP Called Party Number BCD, INAP Calling Party Number, INAP Called Party Number,
INAP Called Party Number BCD. Each entry contains:
Name: free name.
Input NOA, Input Digit String, Min / Max number of digits. They refers to output of all the previous
Translation Steps.
SCP Node: refers to the previous translation step and/or call context.


1 Outpulse Maps

1.10 Digit Outpulse Map: principles

3—2—

17

Digit Outpulse Map is an alternative to the use of Regular Outpulse Map
previously described.
Digit Outpulse Maps are more powerful and more versatile:
One Digit Outpulse Map may change more than one kind of field/number for
ISUP/BICC. After provisioning, it’s more easy in a Route List to point out a
single Digit Outpulse Map than to point out regular Outpulse Map for each
ISUP/BICC field.
Like a regular outpulse map entry, a Digit Outpulse map entry takes care of
one specific field/number, to alter NOA, digit, various changes. (numberdependant: APRI, SI, NI indicators, billing records)
In addition to these manipulations, with the Source Number Manipulations,
it’s also possible to insert in one number parts (or all) of other call-context
dependant numbers:
MSISDN, Redirecting Number, Original Called Number,
LAC, Cell ID/SAC, IMSI, Carrier ID, CLI, MCC, MNC, IMEI




1 Outpulse Maps

1.11 Digit Outpulse Map: scope

3—2—

Digit Outpulse Maps may change (or not) the following numbers:

One Digit Outpulse Map entry takes care of one specific change of
number, in one specific case. (like a regular Outpulse Map entry):
Change of NOA,
Insert/delete digits,
Various changes
Up to 5 Source Number Manipulation.




18

1 Outpulse Maps


3—2—

19

A Source number manipulation is an object that:
Extract (grab) some digits from one of the following field:
MSISDN, Redirecting Number, Original Called Number, Orig Dialed Number,
LAC, Cell ID/SAC, IMSI, Carrier ID, CLI, MCC, MNC, IMEI;
Will insert these digits at a specific position of an other number, when it will
be used.
Example: « extract 5 first digits of the IMSI, insert them at position 1 » will
just « Insert the MCCMNC in front ».

The same Source Number manipulation may be reused for various
numbers in Digit Outpulse Map entries.
The Source Number manipulation may be used also by a Normalization
or Prefix Translation entry.



The following numbers (or parts of) can be grabbed by a Source Modifier object:
MSISDN
Redirecting Number (Forwarding Number)
Original Called Number
Original Dialled Number (pre-translated dialled Number)
CLI
IMSI
Carrier ID
IMEI


1 Outpulse Maps


3—2—

20

Source Modifiers are created in Outpulse Maps / Digits Manipulations/Source Modifier.
Then they can be used in Digit Outpulse Map entries, and in Normalization or Prefix
Translation entries.



Source Modifiers are created in Office Parameters Outpulse Maps / Digits Manipulations / Source Modifiers.
A unique entry is used in the navigation tree for all the Source Numbers.
Source Modifiers entries can be queried.
For each Source Number type (example IMSI or CellID/SAC), multiple entries can be defined (different
ways to grab the same number), each entry is identified with a unique index.


1 Outpulse Maps

1.14 Source Modifier entry

3—2—

identification

Identify the Source Modifier, for future use as Source Number in Digit
Outpulse Map entries, (or Normalization or Prefix Translation entries).

grabbing

Identify the digits to grab in the Source Number, and where the digits
will be inserted when the Source Modifier is used.



Source Modifiers objects are created or queried like the other objects in the navigation tree.
Each Source Modifier object contains:
An Identification part that contains:
The given Source Number: MSISDN, Redirecting Number, Original Called Number, Original Dialed
Number, CLI, LAC, Cell ID/SAC, IMSI, Carrier ID, MCC, MNC, IMEI.
An Index, that identify the current described grabbing for the given source number.
Index is unique only for the given source number.
A Digit Source that describes the way to grab the Source Number:
Digit to grab: number of digit to take from the Source Number.
Start Position: define where to grab digits (1=at the beginning).
Default Digits: indicates the digits to use in place of grabbing digits if the Source Number is not
available.
Insert position: define where to insert the grabbed digits, when the Source Modifier is used.
MaximumDN
MS IS values for Start Position and Digit to grab are:
32
LAC
5
Cell ID/S AC
5
Notes:
IMS I
15
-If no digits are found at the start position then
Carrier ID
4
the provisioning entry is ignored.
Redirec ting Number
32
Original Called Number -If only partial digits are present at the start position
32
then only the partial digits are inserted.
Original Dialed Number
32
Calling P arty Numbe r (CLI) 32 Cell ID/SAC are converted to 5 digits format.
-LAC,
MCC
3
For example, if the Cell ID is 1, then the padded
Cell ID is ’00001’.
MNC
2 or 3
IMEI
15

21

1 Outpulse Maps

1.15 Digit Outpulse Map query


3—2—

22


Digit Outpulse Maps are located in Office Parameters / Outpulse Maps / Digit Manipulations / Digits
Outpulse Map:
Multiple entries may be defined to modify multiple numbers, for different cases, for different conditions.
We have to query Digit outpulse map entries to see content of the outpulse maps.
So to see all entries associated to one Digit Outpulse Map index, it’s possible to query with the Outpulse
Map Index condition.
Each Outpulse Map entry will modify for one number (named Digit Type), NOA, digit format and other
parameters in one way, depending of the incoming NOA, incoming digit string pattern, and min/max
number of digits, and for one kind of protocol (ISUP or BICC, CAP or INAP, DTAP).


1 Outpulse Maps

1.16 Digit Outpulse Map: possible usage

3—2—

23

Digit Type

SCP Node, Outpulse Map used for:
Service Key Index
ISUP and BICC:
Redirecting Number
N/A
Redirecting Party Number
>1
Calling Line Number
N/A
>1
Called Party Number
N/A
Called Party Number
>1
Original Called Party Number N/A
Original Called Party Number
>1
Location Number
N/A
Location Number
>1
CAP or INAP:
Redirecting Number
choosen
N/A (0 is used) Redirecting Party Number
Calling Line Number
choosen
N/A (0 is used) Calling Party Number
Called Party Number
choosen
N/A (0 is used) Called Party Number
Original Called Party Number choosen
N/A (0 is used) Original Called Party Number
Location Number
choosen
N/A (0 is used) Location Number
DTAP:
DTAP Calling Line Number
N/A
N/A (1 is used) Calling Party Number
DTAP Connected Number
N/A
N/A (1 is used) Connected Number
SS_FTN
N/A
N/A (1 is used) Interrogate SS Forward to Number List
N/A=Not Applicable


This chart gives you a sum-up of the possibilities of the Digit Outpulse Map entries, depending of the Digit
Type selected, the Outpulse Map Index and the SCP Node/SK provisioned.
General guidelines are:
For an entry used for CAP/INAP, SCP Node and Service Key is provisioned (and identify the entry), and
the Digit Outpulse Map Index is not used.
For an entry used for DTAP, only one Digit Outpulse Map is used for DTAP messages. SCP Node, Service
Key and Outpulse Map Index are not used.
For an entry used for ISUP/BICC, the Outpulse Map Index is freely choosen; SCP Node and Service Key
are not used. This Digit Outpulse map index will be later used in as Digit Outpulse Index (in a Route List Route Type x – Trunk Group or Bundle, or in the Bundle itself).
Depending of the Source Number, different manipulations are possible. These manipulations are detailed
in the following pages.
Note: other Digit Types are available specifically for SIP (MGCF) function, to change the SIP headers of the
outgoing message: SIP Request URI, To: header, From: header, P-Assested-Identity, Forwarding Number,
Routing Number. There are not detailed here.


Digit Outpulse Maps: possible usage (cont):
Depending of the Source Number type, different manipulations are available:
Add/delete digit operation should be available.
Change NOA assignment to National, International, Subscriber and Unknown
Change the APRI to Allowed/Restricted
Change the Screening Indicator
Change the Number Incomplete Indicator (ISUP only)
Note: This digit Outpulse MAP provides manipulation on the Forwarded-To-Number address sent to the MS
as result of Call Forwarding interrogation using the InterrogateSS information element.
This feature does not change the InterrogateSS functionality. It just provides a mechanism to manipulate
the digits in the FTN information of the InterrogateSS Return Result.


1 Outpulse Maps

1.17 Digit Outpulse Map entry

3—2—

identification

25

manipulations


Each Digit Outpulse Map entry contains 3 groups of parameters:
Identification: identify the Source Number, the purpose of the Digit Outpulse Map, and the incoming
parameters used to match an entry.
Source number: one of the source number previously described;
Outpulse Map Index: ID of the Outpulse Map, case of ISUP/BICC only.
SCP Node and Service Key: case of CAP/INAP only.
Name: free name (optional).
Input NOA, Digit Pattern, Min / Max number of digits: used to determine if this entry will be used,
depending of the incoming number. The incoming number refers to output of all the previous
Translation Steps done.
Properties: NOA, digit format and other manipulations (depends on the Source Number):
Send: checkbox to choose if the Source Number has to be sent or not in the outgoing message.
Start Position, Digits to delete, insert digits: optionally remove and add digits, anywhere in the current
number.
Output NOA: outgoing Nature of Address may be changed, or kept “no change”.
For the other manipulations (Source Number dependant), please see next page.
Modify Digit Source: insert values of other numbers thanks to Source Modifier objects.
These modifications are done after the previous “properties” digit manipulations.
Up to 5 Source Modifiers can be used.


1 Outpulse Maps

1.17 Digit Outpulse Map entry [cont.]

3—2—

26

Source Number dependant manipulations



Digit Outpulse Map entry (cont)
Properties: Source Number dependant properties:
Normalized LOC: Indication if Location Number needs to be converted to the same format (either
national or international) as Called Party Number (Location Number only).
Presentation Ind: Presentation Restriction Indicator (APRI) can be set : allowed / Presentation
Restricted / No change. (CLI, or RN, or OCN).
Num Incomplete Ind: specifies the value of the Number Incomplete Indicator (NI) field : Complete,
Incomplete, no change. (CLI only).
Screening Ind: specifies the value of Screening Indicator (SI) field : User Provided, Not Verified / User
Provided, Verified and Passed /User Provided, Verified and Failed / Network Provided / No Change (CLI
only)
Capture in CDR: specifies if the modified digits needs to be captured in CDR.
The default value is ‘No’ for Calling Number, ‘Yes’ for all other digit types.
Note: In existing WCS implementation CaptureInCDR is overridden by another config param flag
use_OutpulsedCldInCDR, if the modified digits needs to be captured in CDR then
use_OutpulsedCldInCDR flag needs to be set as well.


1 Outpulse Maps

1.18 Digit Outpulse map entry: use of Source Modifiers

3—2—

27

identification

manipulations

« Insert MCCMNC of the
calling subscriber in front
of the current called
number »


When used in a Digit Outpulse Map entry, a Modify Digit Source / Source Number modification refers to an
Source Modifier object defined in “Outpulse Map / Digit Manipulation / Source Modifier”.
The meaning of the Source Modifier object is complete only when it’s used, because it depends also on the
Digit Type of the Digit Outpulse Map entry.


Exercise – Digit Outpulse Maps and Source Modifiers

3—2—

„ Digit Outpulse Maps and Source Modifiers “

Time allowed: 1h30




28


3—2—

for this module




29


3—2—

End of Module
Outpulse Maps




30


3—3

Section 3
Module 3
Orig Routing



Blank Page
Routing provisioning — Orig Routing


3—3—



Document History
Edition

Date

Author

Remarks

2006-10-20

LAPIERRE, Laurent

First version

2007-01-22

LAPIERRE, Laurent


2007-07-23

LAPIERRE, Laurent


01

2007-08-01

LAPIERRE, Laurent


02

2011-03

LAPIERRE, Laurent

Updt for 5.1


2

Objectives

3—3—


Provision Origination Routing entries.
Provision Origination Routing Modifiers.
State the content of the WCS system logic for the
Orig Routing step.




3

Objectives [cont.]


3—3—




4

Table of Contents

3—3—

Page

1 Orig Routing
1.1 Orig Routing use (review)
1.2 Orig Routing : example of use
1.3 Orig Route Descriptor
1.4 Orig Route Modifier
1.5 Orig Routing Entry


7
8
9
10
11
12



5


3—3—





6


3—3—

1 Orig Routing




7

1 Orig Routing

1.1 Orig Routing use (review)

3—3—


From Translation

Orig Routing

Orig Route Modifier
Route Action:
Route Immediately

R3.2 Modifier Based Routing


R3.1 Legacy Routings

Release with
Cause Code

Route List


After Translation steps, if translation end with “destination found” result, the system will go in Routing
Step.
The Orig Routing is the first Routing step.
Orig stands for “Origination Routing” because the system logic is the following:
Destination is known, given from Translation Result.
Origination is known, given from the incoming Trunk Group properties.
Orig Routing combines Origination and Destination to choose the next Action, which can be:
Route immediately: select a Route List and go in Route List step to choose an outgoing resource.
Intercept: release the call with a Cause Code.
Modifier Based Routing: go to a M-Tree for Routing to perform further Routing choice based on
modifiers.
Go at (…) Routing: use legacy R3.1 Routings to perform routing based on selected modifier.

In the following pages we will see an example of provisioning that requires Orig Routing and “Route
Immediately” action.


8

1 Orig Routing

1.2 Orig Routing : example of use

3—3—

Site A

9

GMSC_XYZ
Trunk A

PSTN
PSTN

Trunk B
Site B

BSS
BSS



Orig Routing may be very important since with Distributed MSC it is possible with a single MSC (single
WCS) to control the switching for more than one location.
In the above example:
Our WCS controls 2 Media Gateways in 2 different locations.
GMSC_XYZ is one Gateway connected to the PSTN.
To perform MOC Translation & Routing to the “PSTN” destination, one way to provision the Call Server
is the following:
2 Originations are created: Orig Route Modifiers: “Orig from Site A” and “Orig from Site B”.
1 Destination is created: Orig Route Descriptor: “to PSTN_GMSC_XYZ”
For this Destination “to PSTN_GMSC_XYZ”, 2 Orig Routing entries are created for the 2 originations:
“Orig from Site A”

Route Immediately, use Route List “11 MGA_to_GSMC_XYZ”.

“Orig from Site B”

Route Immediately, use Route List “12 MGB_to_GSMC_XYZ”.

Of course both Route List contains Route Types with different Trunks, typically “Trunk A“ and “Trunk B”.
The following pages will detail this provisioning example.


1 Orig Routing

1.3 Orig Route Descriptor


3—3—

10


Orig Route Descriptors are provisioned in Office Parameters / Routing and Translation / Routing / Orig
Routing / Orig Route Descriptor.
An Orig Route Descriptor represents the destination of the translation.
Orig Route Descriptors will be used in translation results as Route Index, for example in case of Cont at
Orig Routing Route Action.

Note: one Orig Route Descriptor may be used as Route Index in Translation steps only when at least one
Orig Route entry is provisioned.

1 Orig Routing

1.4 Orig Route Modifier


3—3—

11


Orig Route Modifiers are provisioned in Office Parameters / Routing and Translation / Routing / Orig
Routing / Orig Route Modifier.
An Orig Route Modifier represents the Origination of a call.
Orig Route Modifiers are used in incoming Trunk Groups, for MOC and ISUP incoming calls.
(See Group / ISUP or BSS)

Note: Orig Route Modifier may be used in incoming Trunk Group properties only if at least one Orig Routing
entry is provisioned for this Orig Route Modifier.


1 Orig Routing

1.5 Orig Routing Entry


3—3—

12


Orig Routing Entries are provisioned in Office Parameters / Routing and Translation / Routing / Orig
Routing / Orig Route.
The way to access to Orig Routing entries is slightly different from the release W 5.1.
The Orig Route object in presented in a query, with results in a table.
The best way to edit and understand Orig Routings entries is to filter:
-either for a specific Orig Route Modifier (typically, MGW or Site of switching). The display before W 5.1
was per Orig Route modifier.
-or for a specific Orig Route Description (“destination” result of Translation).

For the above example:
For the destination “To SIPp” (Orig route Descriptor #9),
For the origination “Orig from WMG1” (Orig Route Modifier #1),
No other Routing step is used, the system will use the Route List #740 “To SIPp (SIP)” to route the call.

Note: AMA index must be provisioned but is only used in US for the “Baby Bells”.


Exercise

3—3—

„MSRN Translation at the Gateway MSC“

Time allowed: 2 h




13


3—3—

for this module




14


3—3—

End of Module
Orig Routing




15


3—4

Section 3
Module 4
Modifier Based Routing



Blank Page
Routing provisioning — Modifier Based Routing


3—4—



Document History
Edition

Date

Author

Remarks

2006-10-20

LAPIERRE, Laurent

First version

2007-01-22

LAPIERRE, Laurent


2007-07-23

LAPIERRE, Laurent


01

2007-08-01

LAPIERRE, Laurent


02

2009-08-31

LAPIERRE, Laurent

Update for 5.0


2

Objectives

3—4—


List the Modifiers available for Routing.
Provision Modifiers for Routing Step.
Provision Routing Based on Modifiers entry.
Provision Routing Based on Modifiers M-Tree.
for Modifier based Routing.




3

Objectives [cont.]


3—4—




4

Table of Contents

3—4—

Page

1 Modifier Based Routing
1.1 Review: Modifier principles for Routing
1.1 Review: Routing based on Modifiers: overview
1.2 Modifiers for Routing versus Modifiers for Translation
1.3 Review: Modifiers available for Routing
1.5 User-defined Modifier: CIC Modifier
1.5 User-defined Modifier: ToD Modifier
1.6 Routing M-Tree object
1.7 Routing M-Tree entry




7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

5






3—4—

6


3—4—





7


1.1 Review: Modifier principles for Routing

3—4—

Modifier-based Routing can be used:
to select a specific outgoing Route List,
or to release the call with a specific cause code,
depending on a call parameter such as: location of the call (LAC/CellID,
SAI), calling party identity (IMSI, CLI…), etc,

System and User-defined modifiers for Routing:
Some Modifiers are System-defined, when the values are normalized (eg
CPC), some others are user-defined for flexibility purposes (eg IMSI
patterns).

Modifiers are used in “Routing Based on Modifiers” M-Trees.




8


1.1 Review: Routing based on Modifiers: overview

3—4—

9

From Orig Routing
Routing based on Modifiers

* user-defined,
** system-defined
modifiers

M-S elector with (CIC,
Routingelector with IMS I,
M-S with (CIC, (CIC,
LAC, S AI, CLI, ToD)*,
(CP C, OS S S , OCS I,
(CP C,C, OSS ,S , OCS I,
(CP OS S S OCS I,
S TL, Codec, S ervice)**
SS TL,Codec, SS ervice)**
TL, Codec, ervice,
Intercept

Release with
Cause Code


Route Immediately
Route List


Routing M-Tree is used optionally, after Orig Routing, with a Route Action “Routing based on Modifier”.
Only one Routing M-Tree used is allowed: it is not possible to loop from a Routing M-Tree to another
Routing M-Tree.
A Routing M-Tree analyzes up to 5 modifiers together.
The result of a Routing M-Tree is always :
Route immediately with a specific Route List,
or Release the call with a specific Cause Code.



1.2 Modifiers for Routing versus Modifiers for Translation

3—4—

10

Similarities between Modifiers for Routing and for Translation:
System-defined modifiers values are common.
Routing M-Tree will analyze up to 5 modifiers, as Translation M-Trees do.
Routing M-Tree modify next step of Routing, as Translation M-Tree modify
next step of Translation.

Differences between Modifiers for Routing and for Translation:
Types of modifiers usable for Routing and Translation are different.
For user-defined modifiers common for Routing and Translation, modifier
values are declared two times: for Translation, and for Routing.
Routing M-Tree do have a Identifier ID (range <1> to <255>) that is not
shared with the Tree IDs for Translation.
Is it not possible to loop from an Routing M-Tree to another Routing M-Tree.





1.3 Review: Modifiers available for Routing

3—4—

CICM
IM SIM

Dialed CAC or subscriber profile

CLIM


LACM
SAIM
TODM
NOAM
CPCM
OSSSM
CAM ELM

SAI received from RNC
System Time
Called Party Number Nature of Address
CPC in incoming IAM message
OSSS code in VLR
IN trigger information in the VLR

STLM
CODECM
EM Z

connection indicators received in IAM
originating trunk properties or codec
Emergency Zone M odifier

SERVICEM bearer service or teleservice from SETUP

X
X
X
X
X
X

X

Purpose
User-def.

Obtained from

System-def.

Code

X For equal access feature
X M odify translations and routing based on which PLM N
X Similar to IM SI – used to alter translations and routing
based on CLI.
X Location Area Code + Cell Range M odifier
X Service Area Indicator M odifier (3G)
X Time of Day modifier
Calling Party Category modifier (ISUP only)
Routing based on absence or presence of OCSI Camel
M ark for the calling party (M OC)
Satellite Link M odifier
try to select route using same type of codec
X Allows non-emergency calls (e.g. 611, 311) to use same
location –based routing as for emergency calls.
Bearer Capability


The following pages will detail:
The values of system-defined modifiers
The provisioning of user-defined modifiers
The provisioning of Routing M-Trees
The provisioning of Routing M-Tree entry

Note: Emergency Zone Modifier is only available for North-America.


11



3—4—

CPC: Calling Party Category:
0 Unknown, 1 French Operator, …
Usable for ISUP originating calls only.

OSSS:
Each OSSS codes available; 0 for OSSS unavailable.

Camel:
OCSI Camel Mark absent, OCSI Camel Mark present.

STL:
No satellite, one, or two satellites in the connection.

Codec:
FR, HR, EFR, FR_AMR, HR_AMR, Default Modifier.

Service:
BS20, BS30, etc.

NOA: Nature of Address:
National, International, Unknown, Subscriber.

There is no need to create explicitly the System-Defined modifiers.



12



3—4—

13

They are provisioned in Office Parameters /
Routing and Translation / Routing

CICM
IMSIM
LACM
SAIM
CLIM
ToDM



CIC: Carrier Instance Code, for Equal Access Carrier feature. Mainly used in US.
R3.1 Legacy Routings (cont at … routing) and Routing Based on Modifiers shares some modifiers values.
That’s why each User-defined Routing Modifier is provisioned at a dedicated place in the navigation
tree.
This place comes from the place of the user-defined modifier used in the R3.1 legacy routings.

Note: EMZ Modifiers are defined in Office Param / Mobility Config Params / Emergency Zone Provisioning.



1.5 User-defined Modifier: CIC Modifier

3—4—

14

CIC Route Selector is the Modifier.
Each Carrier Identity Code value is linked to a CIC Route Selector.



CIC modifiers for Routing are created in
Office Parameters / Routing and Translation / Routing / CIC Routing.
CIC Modifiers values are declared in 2 steps:
Carrier Feature Group / FGB associates each CIC value to a CIC Route Selector (Carrier Selector).
CIC Route Selector is the modifier value.
Maximum value 32767.
Free name.
Note: the CIC value can be chosen in a Prefix Tree entry.
Note: The CIC Carrier Identity Code described here has nothing to do with the CIC number in ISUP or in
BICC (Circuit Id Code or Call Instance Code)




3—4—

Up to 255 Modifiers
One modifier entry is a IMSI pattern.
Many IMSI patterns may belong to a single modifier.



IMSI modifiers for Routing are created in
Office Parameters / Routing and Translation / Routing / IMSI Routing / IMSI Route Modifier:
The name is free, and is given for the single IMSI pattern, not the modifier.
The Default IMSI modifier may be used for:
All other IMSIs
No IMSI provided (for example ISUP incoming call)


15



3—4—

16

Up to 65535 Modifiers. Modifier 255 is the default one.
MCC/MNC, LAC, CellID range
A free name



LAC modifiers for Routing are created in
Office Parameters / Routing and Translation / Routing / LAC Routing / LAC Route Modifier.

Notes:
The LAC drop-down list presents to you the list of „GSM LAC or CELL“ objects created in Mobility
Config. Parameters. So the same LAC may be presented several times if the LAC is split over 2 BSCs, or
is declared with several ranges of cells. But only the value of the LAC is significant here.
For LAC modifiers created by the Command Line Interface, only the value of the LAC is asked, no
reference to any „GSM LAC or CELL“ object is needed.




3—4—

Up to 65535 Modifiers.
MCC/MNC, LAC, SAC Range.
A free name



SAI modifiers for Routing are created in
Office Parameters / Routing and Translation / Routing / SAI Route Modifier.
Notes:
The SAI field gives the list of LACs: the LAC has to be chosen.
The CellID range does represent the SAC range for the modifier entry.


17



3—4—

Up to 255 Modifiers. Modifier 255 is the default one.
Nature of Address, CLI pattern, Min and Max digit Count
A free name



CLI modifiers for Routing are created in
Office Parameters / Routing and Translation / Routing / CLI Route Modifier.
The Default CLI modifier may be used for:
All other CLIs
No CLI provided
More than one CLI modifier entry may belong to the same CLI Modifier.


18


1.5 User-defined Modifier: ToD Modifier

3—4—

ToD Route Selectors are the modifiers:
Index: up to 32767 modifiers.
Class: free name.

ToD By Source Groups is used to
associate days / hours to
a ToD Route Selector.



ToD modifiers for Routing are created in
Office Parameters / Routing and Translation / Routing / ToD Routing / ToD Route Selector.
Note: for ToD by Source Group provisioning, only Subscriber Group “1 Generic” is available.


19


1.6 Routing M-Tree object


3—4—

20


M-Trees for Routing are created in
Office Parameters / Routing and Translation / Routing / Modifier Based Routing.
Parameters for a Routing M-Tree:
Route Selector: from 1 to 255. This ID is not shared with the others M and D-Trees for Normalization
and Prefix Trees.
Name : free name
Selector: from 1 to 5 modifiers together, in the list of available modifiers for Normalization.

The example above shows the creation of one Routing M-Tree that will modify routing depending of 2
modifiers: Number of Satellite(s) in the connection, and nature of the call: prepaid/postpaid.



1.7 Routing M-Tree entry

3—4—

identification

21

output



Routing M-trees entries are created in
Office Parameters / Routing and Translation / Routing / Modifier Based Routing / <Tree_ID>.
In a Routing M-Tree entry, we can split the object into 3 groups of parameters:
Identification: use to select an entry of the Tree:
Free name for the M-Tree entry.
Selector: the incoming Call Context parameters must match all modifiers values to select this M-Tree
entry.
Output: system logic and output of the Modifier Based Routing: only 2 possibilities:
Intercept: release the call, a cause code must be provided.
Route Immediately: route the call, a Route List must be provided.


Exercise – Digit Outpulse Maps and Source Modifiers

3—4—

Please do the exercise 7 of your Exercises Book:
„ Emergency Number Translation and Routing
depending on LAC/Cell and IMSI “

Time allowed: 2h00




22


3—4—

for this module




23


3—4—

End of Module
Modifier Based Routing




24


4—1

Section 4
Appendix
Module 1
Appendix



Blank Page
Appendix — Appendix


4—1—



Document History
Edition

Author

Remarks

2006-10-20

LAPIERRE, Laurent

First version

2007-01-22

LAPIERRE, Laurent


2007-07-23
01

Date

LAPIERRE, Laurent


2007-08-01

LAPIERRE, Laurent



2

Objectives

4—1—

Give a description of the following features:

E911 Emergency Calls
HPLMN ODB Configuration
7-digit dialing
WPS
Time Based Substitution




3

Objectives [cont.]


4—1—




4

Table of Contents

4—1—

Page

1
2
3
4
5
6

E911 Emergency Calls provisioning
HPLMN ODB Configuration
7-digit dialing
WPS
Abbreviations and Acronyms




7
12
18
24
29
37

5


4—1—





6


4—1—

1 E911 Emergency Calls provisioning




7

Emergency Service – LAC or CELL Call Provisioning

4—1—

8

Type of E911 Solution Phase2 E911
Phase0 911
Phase1 E911
Phase2 E911



Emergency Service – LAC or CELL Call Provisioning
Dialed digits of 911 trigger an emergency call.
The MCC/MNC, LAC, and Cell ID of the emergency call are delivered in the
incoming BSSAP message.
The call is first processed here. No other pre-processing is performed.
Emer Srvc Zone ID points to the record containing information that enables
identification of the specific PSAP to which the call would be routed. This information
is provisioned in Emergency Service Zone Provisioning.
The Type of E911 Solution (Phase 0,1,2) is specified here.


Emergency Service – Phases
4—1—9


PSAP
GMLC

IMPC

SMLC

LAC/Cell



Emergency Service – Phases
Phase 0: MSC does Translations on PSAP DN (provisioned on the MSC) to route to PSAP. The
Emergency Service Zone and associated PSAP DN is selected based on LAC/Cell of
incoming 911 call. The LAC/Cell information is not relayed to the PSAP.
Phase 1: The MSC can pick a ESRK from a set of ranges provisioned and do translations to
route to the PSAP or simply translate based on ESRD. The ESRK may be provisioned on the
MSC or the MSC can query the IMPC (SCP) for ESRK based on LAC/Cell of incoming 911 call.
MSC does translations on ESRK or ESRD to route to PSAP.
Phase 2: In addition to all of Phase 1, Lat/Long location of the subscriber is retrieved
from SMLC by MSC and forwarded to GMLC. GMLC forwards the same information to PSAP.


Emergency Service – Zone Provisioning
4 — 1 — 10


EC Routing Option Route using PSAP DN
Route
Route
Route
Route


using
using
using
using

PSAP DN
ESRC
ESRK
INAP SCP response


Emergency Service – Zone Provisioning
Emer Srvc Zone Id, Emer Srvc Zone Name, PSAP Zone DN, ESRK Pool
ranges and other related parameters are provisioned here.
EC Routing Option specifies how the switch routes the call to the PSAP.
The choices are:
•

Route by PSAP DN (Phase 0,1,2)

•

Route by ESRD/ESRK (Phase 1,2)

•

Route by INAP SCP response


Emergency Service – Call Parameters
4 — 1 — 11




Emergency Service – Call Parameters
System default parameter values for E911 are provisioned here.



4—1—

2 HPLMN ODB Configuration




12

ODB Configuration (Logic Flow)

Wireless
Normalization

4—1—

Check VLR

ODB
Configuration

PLMN ODB Mapping table
PLMN Specific Barring Type
mapped to Service Key

Service Key =
OBD Specific Type

Service Criteria List table Not
Digit Pattern mapped
Found
to dialed digits

Intercept

Found
Not Allow
Service Criteria table
OBD Specific Type =
Allow or Not Allow


Allow

Service Key =
Local Call Only

Match LCO Exception List table
Digit Pattern mapped
Found
to dialed digits
No
Match
Found

Mobile Number
Portability check


ODB Configuration (Logic Flow)
ODB pertains only to mobile originated calls and is performed after
Wireless Normalization.
ODB allows the operator to regulate access by subscribers to services
such as voice SMS, supplementary services, and roaming.
Note: PLMN Specific Barring Types are defined in the HLR for each
subscriber. This information is downloaded to the VLR upon
mobile
registration.


13

ODB Configuration

4—1—

Identification
PLMN ODB ID PLMN Specific Barring Type 1
Properties
Service Key ODB Specific Type 1



ODB Configuration
In the PLMN OBD Mapping table, each PLMN Specific Barring Type
(1,2,3,4) is mapped to a Service Key on the switch. These Service Keys
have the following values:
•

ODB Specific Type1

•

ODB Specific Type2

•

ODB Specific Type3

•

ODB Specific Type4

•

Local Call Only


14

ODB Configuration

4—1—

Identification
Service Key

Digit Type

Digit Pattern

ODB Specific Type 1

Service Code

972



ODB Configuration
After the PLMN Specific Barring Type has been mapped to the ODB
Specific Type, the Service Criteria List table is checked.
The Digit Pattern field is checked for a match with the dialed digits,
based on the Digit Type field.
The Digit Type field has two options:
•

Service Code: A 3-digit code used to access telephone company
services, for example, 123 (voice mail), 611 (customer service),
411 (directory information), and 911 (emergency service).

•

International Formatted DN: A telephone number that includes
the country code. For example, 011972.

Whether the choice is Service Code or International Formatted DN, the
Digit Pattern field is compared to the dialed digits for a match.
•

For Service Code, it must be exact length and match.

•

For International Formatted DN, it can be just a prefix pattern
match.

You can add multiple entries in Service Criteria List table.
If the ODB check fails to find a match, the call is not allowed.

15

ODB Configuration

4—1—

Service Key ODB Specific Type 1

Criteria Allow
Allow
Not Allow



ODB Configuration
If the ODB check does find a match, it doesn’t automatically mean the
call is allowed.
The switch will check the Service Criteria table, where the Service Key
(ODB Specific Type X) is mapped to Criteria (Allow, Not Allow).
Only if it’s allowed, will the call pass ODB process.


16

ODB Configuration

4—1—

Identification

Properties

LCO Exception ID

Digit Pattern

0

1212



ODB Configuration
If the PLMN Specific Barring Type is mapped to Local Call Only (rather
than an ODB Specific Type), the switch will look in the LCO Exception
List table.
The LCO Exception List table is a list of digits that the customer will not
have access to.
If the dialed number matches any digits in the exception list, the call is
not completed. For example, if you do not want a subscriber to have
access to 900 service, add it to the exception list so the call is not
completed when 900 is dialed.


17


4—1—

3 7-digit dialing




18

7-Digit Dialing
4 — 1 — 19


Dialing Digit Flag 10-digits dialing
10-digits dialing
BSS 7-digits dialing
WSS 7-digits dialing
No WSS 7-digit allowed



7-Digit Dialing
This feature allows the mobile user to dial only the last 7 digits instead
of all 10 digits when making a call within the same NPA.
In System Parameters you can choose one of the following values to
activate 7-digit dialing:
•

BSS 7-digits dialing

•

WSS 7-digits dialing

•

No WSS 7-digit allowed


7-Digit Dialing – BSS
4 — 1 — 20


BSSAP
Calling Party = 2148675309
LATA = 552
BSS Entity = 11

Radio Network Id 11

Lata Number 552 Dallas



7-Digit Dialing – BSS
If the BSS 7-digits dialing option is active, the BSS Entity must be
configured with a LATA.
The system checks to see if the calling party number matches any NPA
configured under the LATA.
•

If found, the call is allowed to proceed.

•

If not found, the call is released.


7-Digit Dialing – Default LATA
4 — 1 — 21




7-Digit Dialing – Default LATA
LATA 1 is a system-wide default LATA.
If the WSS 7-digits dialing option is active, or the No WSS 7-digits
dialing option is active, the system uses the default LATA.
LATA 1 and it’s information must be provisioned.


7-Digit Dialing – WSS
4 — 1 — 22


BSSAP
LATA = 552
BSS Entity = 11

NPA found,
call proceeds.

Digit Dialing Flag WSS 7-digits dialing



7-Digit Dialing – WSS
If the WSS 7-digits dialing option is active, the system checks to see if
the calling party number matches any NPA configured under the
default LATA.
•

If found, the call is allowed to proceed.

•

If not found, the call is released.


7-Digit Dialing – No WSS
4 — 1 — 23


BSSAP
LATA = 552
BSS Entity = 11

NPA not found,
call proceeds.

Digit Dialing Flag No WSS 7-digit allowed



7-Digit Dialing – No WSS
If the No WSS 7-digits dialing option is active, the system checks to see
if the calling party number matches any NPA configured under the
default LATA.
•

If found, the call is released.

•

If not found, the call is allowed to proceed.



4—1—

4 WPS




24

Wireless Priority Service
4 — 1 — 25


Name WPS


Description Wireless Priority Service


WPS is a feature to support routing of high priority calls, like calls
originating from police, fire department, ambulance, and such.
All such calls have a *272 prefix for the called number. The WCS
recognizes the high priority call based on this prefix.
A WPS subscriber dials *272 + called party number. The *272 is
stripped on the first pass of prefix translation and the remaining digits
are processed on the second pass of translations.
Dialing *272911 for emergency is not allowed and will be dropped
by the switch.
A WPS resource has to be activated as one of the provisioning steps.


4 — 1 — 26


Mobile Country Code 310

Mobile Network Code 260
WPS Allowed



Under Network Allowed Services, you need to add a resource with
MCC, MNC values and WPS Allowed box checked.
There are also certain parameters in System Parameters that need to
be given specific values. These parameters are under Call Manager
and Facility Manager.


4 — 1 — 27


Group Number 12345

Precedence



In ISUP trunk group properties, check the Precedence box. This
indicates that this trunk group is designated to send out a WPS call
from the switch after translations.


4 — 1 — 28


Name *272 4D-15D

Digit String *272

Digit String Type Wireless Priority Service



In the Standard Normalization Tree, make sure you have an entry to
match *272 pattern as shown here.



4—1—

5 Time Based Substitution




29


4—1—

Timed Prefix
Substitute

DN = xxx-xxx-xxxx

Continue translations

No

DN=
Yes
Substituted
Prefix?

Get Time Slot Index
(Permissive period)

No
Current
Yes
time within
Time Slot?

Return
Error Cause

Get TmSlt Indx For Err


Prefix Substitute
Time Slot

No

Current
Yes
time within
Time Slot?

Convert old
NPA to new.
Return DN


This feature is used to support NPA split.
NPA split is made subscriber friendly via prefix substitution for a given
period of time.


30



4—1—


For each old NPA and new NPA combination, the following dates are
defined:
•

Start of NPA split (T1)

•

End of Permissive Dialing (T2)

•

End of NPA split (T3)

For example, an area code is split in two with 2 NPAs.
•

For a T1 period of time, you want to treat calls to all affected 7
digit numbers + either NPA the same (i.e. both valid).

•

After that, for a T2 period of time, you want to support only the
new NPA and reject all called numbers with the old NPA + 7
digits (i.e. only new NPA + same 7 digits is valid).

•

After T3, you want to treat all numbers (with old or new NPA)
independently (i.e. there could be valid numbers with the same 7
digits, each with a different NPA).


31

Time Based Substitution – T1 Time Period
4 — 1 — 32


Incoming

DN = 909-323-4567

Substituted Prefix 9093

Match old NPA

Time Slot Index 3
Substituting Prefix 4513

TmSlt Indx For Err 4

Error Cause Unallocated number

Time Index 3
Year 2006

Month 7

Day 1
Year 2006

Month 10

Current date/time
within Time Slot

Day 1

DN = 909-323-4567
Outgoing:
NPA unchanged



Let’s say NPA 909 is split into two NPAs, 909 and 451:
•

New NPA covers numbers 451-3xx-xxxx

A call is made to 909-323-4567.
A match is made of the incoming dialed NPA with the old NPA in the
Time Prefix Substitute table.
The Time Slot Index value is used to index into the Prefix Substitute
Time Slot table, Time Index field.
•

The current date/time is within the specified time slot.

•

The dialed number contains the old NPA.

•

Therefore, the dialed number is sent out unchanged.


4 — 1 — 33


Incoming

DN = 451-323-4567
Match new NPA

Time Slot Index 3




Time Index 3
Year 2006
Day 1
Year 2006
Day 1

Month 7

Month 10

Current date/time
within Time Slot

DN = 909-323-4567
Outgoing:
Old NPA substituted



A match is made of the incoming dialed NPA with the new NPA in the
•


•

The dialed number contains the new NPA.

•

Therefore, the switch will substitute 4513 with 9093 and the call
will go to 909-323-4567.


4 — 1 — 34


Incoming

DN = 909-323-4567


Match old NPA

Time Slot Index 3



Time Index 4
Year 2006
Day 1
Year 2007
Day 1

Month 10

Month 02

Current date/time
within Time Slot

DN = 909-323-4567
Outgoing:
NPA unchanged



A match is made of the incoming dialed NPA with the old NPA in the
•

The current date/time is not within the specified time slot, so no
action is taken.

The TmSlt Indx For Err value is used to index into the Prefix Substitute
•


•

The dialed number contains the old NPA.

•



4 — 1 — 35


Incoming

DN = 451-323-4567
Match new NPA

Time Slot Index 3



Call rejected.
Announcement played.

Time Index 4
Year 2006

Month 10

Day 1
Year 2007

Month 02

Current date/time
within Time Slot

Day 1



A match is made of the incoming dialed NPA with the new NPA in the
•

action is taken.

•


•

The dialed number contains the new NPA.

•

Therefore, no NPA substitution will be made. The call is rejected
and an announcement is played (since the number is not allowed
to exist yet).


4 — 1 — 36


Incoming

DN = 909-323-4567 or 451-323-4567

Match NPA

Time Slot Index 3


Time Index 3
Year 2006

Time Index 4
Month 7

Day 1
Year 2006
Day 1

Year 2006
Day 1

Month 10

Month 10
Year 2007
Day 1

Current date/time
not within Time Slot

Month 02

Current date/time
not within Time Slot
DN = xxx-x23-4567


Outgoing,
unchanged


T2 time period ends and T3 time period begins:
•

451-323-4567 is added to the directory. This is allowed after T2
time period ends. In the directory you now have 451-323-4567
and also 909-323-4567.

A call is made to either 909-323-4567 or 451-323-4567.
A match is made of the incoming dialed NPA with the NPA in the Time
Prefix Substitute table.
•

action is taken.

•

action is taken.

•




4—1—

6 Abbreviations and Acronyms




37

Abbreviations and Acronyms

4—1—


A
AAL2

ATM Adaptation Layer Level 2

AI

ATM Interfaces

ATM

Asynchronous Transfer Mode

B
BSC

Base Station Controller

BSS

Base station System

BSSAP

BSS Application Part

C


CAMEL

Customized Application for Mobile network Enhanced Logic

CAS

Channel Associated Signaling

CCM

Call Control Module

CDPA

Called Party Address

CGPA

Calling Party Address

CI

Channelized Interface

CIC

Circuit Identification Code (ISUP), Call Instance Code (BICC),
Carrier Identification Code

CLI

Command Line Interface

CPC

Calling Party Category


38

Abbreviations and Acronyms [cont.]

4—1—


D
DN

Dialed Number

DP2

Detection Point 2

DP3

Detection Point 3

DPC

Destination Point Code

DS0

Digital Signal Level Zero

DS1

Digital Signal Level One

DS3

Digital Signal Level Three

E
ESRD


Emergency Service Routing Digits

ESRK

Emergency Service Routing Key

ETC

Establish Temporary Connection

FGD

Feature Group D

FPLMN

Future Public Land Mobile Network

F

G
GAP

Generic Access Parameter

GMLC

Gateway Mobile Location Center

GMSC

Gateway Mobile Switching Center

GTT

Global Title Translation


39


4—1—


H
HLR

Home Location Register

HON

Handover Number

I
IAM

SS7 Initial Address Message

IMPC

I? Mobile Positioning Center

IMSI

International Mobile Subscriber Identity

INAP

Intelligent Network Application Part

ISUP

ISDN User Part



L
LAC

Location Area Code

LATA

Local Access and Transport Area

LCO

Local Call Only

LNP

Local Number Portability

LRN

Location Routing Number


40


4—1—


M
MAP

Mobile Application Part

MCC

Mobile Country Code

MGW

Media Gateway

MNC

Mobile Network Code

MNP

Mobile Number Portability

MO

Mobile Originated

MSC

Mobile-service Switching Center

MSISDN

Mobile Subscriber ISDN Number

MSRN

Mobile Station Roaming Number

MTP2

Message Transfer Part Level 2


MTP3


Message Transfer Part Level 3

N
NCSI

Network CAMEL Subscription Information

NOA

Nature of Address

NPA

Numbering Plan Area

NPDB

Number Portability Database

NS EP

National Security Emergency Preparedness

OC3

Optical Carrier level 3

ODB

Operator Determined Barring

OPC

Origination Point Code

OCSI

Originating CAMEL Subscription Information

OSSS

Operator Services Supplementary Service

O


41


4—1—


P
PLMN

Public Land Mobile Network

PRN

Provide Roaming Number

PSAP

Public Safety Answering Point

PSTN

Public Switched Telephone Network

R2U

Ring To You

R

S

SCP

All
Service Rights Reserved © Alcatel-Lucent 2007
Control Point

SCCP

Signaling Connection and Control Part

SMLC

Serving Mobile Location Center

SMS

Short Message Service

SRI

Send Routing Information

SS7

Signaling System #7

SSN

Subsystem Number

STP

Signal Transfer Point

STS-1

Synchronous Transport Signal 1

T
T&R

Translations & Routing

TG

Trunk Group

ToD

Time of Day


42


4—1—


U
UMTS

Universal Mobile Telecommunications System

UTRAN

UMTS Radio Access Network

VLR

Visitor Location Register

VMSC

Visiting MSC

VT

Virtual Tributary

V

W


WCS

Wireless Call Server

WEM

Wireless Element Manager

WMG

Wireless Media Gateway

WPS



43


4—1—

End of Module
Appendix




44

Last But One Page

1
@@PRODUCT
@@COURSENAME



@@COURSENAME - Page 1

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
@@COURSENAME - Page 2

Routing & translation

More Related Content

What's hot (20)

Similar to Routing & translation (20)

Recently uploaded (20)

Routing & translation