Routing and Dialing Plan Process

Lucent Technologies Proprietary

References
401-610-036, Database Update Manual
401-661-030, Digit-by-Digit Feature Users Guide
CL3630, Digit Routing Translations Course

Lucent Technologies Proprietary

Concept:
When a Mobile Subscriber originates a call, the dialed digits must be
analyzed one digit at a time from left to right, until enough digits are
analyzed to match the specific pattern in dialing plan and then direct
the call to the appropriate trunk.
ECP plays major role in analyzing digits and making routing
decisions. But it does not mean that 5E has no role in routing.
For all incoming calls 5E does the digit analysis and makes a
decision to handover the calls to ECP.
For outgoing calls, ECP sends a message to 5E to tell which trunk
group shall be used and in this case no call routing is done at 5E
end.

Lucent Technologies Proprietary

Call Flow Chart

Lucent Technologies Proprietary

Objective
Recognize the basic steps of call processing
Identify the process of digit-by-digit analysis
Identify the data organization used for digit analysis
Identify the forms associated with DxD analysis (which includes the
sub/vlr, start, dplan, dnmod, and fscode forms)
Identify forms associated with DxD call routing (which includes the
dxdrte, rls and tgl forms)
Understand how each form impacts call routing
Identify the relationships between certain key fields and the efficiency
of call analysis with DxD routing
Identify the basic design of a digit-by-digit dialing plan

Lucent Technologies Proprietary

Simple Call Flow

Step-2

Step-1

Step-2a

Step-2b
dplan form

sub/vlr form

start form

MIN _____
NSN _____

PDC _____
SDC _____
PRC _____
RC _____

OR

Dialing Plan ___

Pattern # ___
Query by Pat ____

Dialing Class __
Proc Type ___
Logical # ___
Server Grp ___
Ant. Face __
Dialing Plan ___

Step-2c

Pattern
________
Call Type _____
Dest Index ____
Prefix Type ____
# Digits to Del _____
Reanalyze __
DN Mod Type
____

Step-3b

Step-3a

rls form

dxdrte form
Dest Index ____
Rate Center ____
Switch Routing List:
RI 0
____
RI 1
____
Call Rte Type ___

Switch ID
__
Route Index ___
Route Class ___

OR

Step-3

tgl form
Switch ID ____
RLS
____

Trk Grp ____

Route List Sel __
Digs Deld ___
Prefix
____
Out Fmt ____
ANI
____
Lucent Technologies Proprietary

Step-4

To
DCS
6

Step-1: Subscriber Validation

Lucent Technologies Proprietary

Step-1: Sub/VLR Form

AUTOPLEX
Cellular
System

SUBSCRIBER AND FEATURE INFORMATION (sub)

Screen 1 of 14
(General Info)

Mobile Directory Number

Area Code *2) sub Office Code *3) 233 Station Number *4) 0070
National Significant Number *5)6142330070
Mobile Identification Number *6) 6142330070 IMSI *7)_______________
IMSI 11_12....................... 8)__
IMSI_S............... 9)__________
Mobile Directory Number Type.... 10)h
Mobile Serial Number.12)hc313339a
Visited System Identifier: Switch 13)1
ECP 14)1
System 15)32766 SMPA 16)0
Switch Identification........... 17)1
AR Capable.................... 27)y
Cellular Geographic Service Area 18)1
Routing Class................. 28)70
Origination Major Class......... 19)1
Paging Channel................ 29)0
Visited Origination Major Class. 20)___
Number of Pages............... 30)2
Termination Major Class......... 21)1
Flood Page FTN................ 31)n
Primary Interexchange Carrier... 22)____ Refresh or Delete VLR......... 32)n
Primary Dialing Class........... 23)___
Call Delivery Outside FTN..... 33)n
Secondary Dialing Class......... 24)70
Currently Activated........... 34)n
Primary Rate Center............. 25)70
Billing - Type................ 35)0
Reserved for Administrative Use. 26)___
- Number. 36)6142330070

Lucent Technologies Proprietary

Mobile Directory Number Types

a roamer access number X X
b CDMA test mobile
c home CN test mobile
d direct dial access for MRS-AMSS
e premium home subscriber
f remote feature activation number
h home subscriber number X X X X
j CDMA mobile loopback test (CMLT)
k CMLT timed test
l roamer II temporary local DN
m maintenance test line X X
n roamer CN test mobile
o mobile station test (MOST)
p pseudo DN X X X X
q data access
r registered roamer X X X X
s special DN
t TDMA test mobile
u tone and announcement type 1-15
w WSCP or standalone HLR
x priority subscriber
y CRTU test mobile
Lucent Technologies Proprietary

Originating Major Class Values

Value

Description

Value

Description

All classes of service available

Operator origination and selected DN[1-3] DN[4-6]

All originations denied

10

Operator origination and selected NPA(s) in the stdldb

Manual originations only (operator calls only)

11

Operator origination and North American dialing only

Operator origination

12

Positive directory number (DN) check call allowed if

in the stdldb and the Allowed Call Number Table (ACNT)
feature is active

Hot-line service

13

Negative DN check call denied if in the stdldb and the

ACNT feature is active

Selected DN[1-3] DN[4-6] combination in the

standard list database (stdldb)

14

Operator and local calls only

Selected NPA(s) in the stdldb

15

Local calls only

Lucent Technologies Proprietary

10

Step-1: Sub/VLR Form

The sub (subscriber and feature information) form is used to review,
add, or change data that defines the basic operating parameters and
custom calling features for each subscriber in a system. Stand-alone
or external databases, e.g., the vlr (visitor location register
information) form, store equivalent data.
Following important Routing/DP fields are obtained from Sub form
This fields provides pointer to routing and dialing plan databases

Lucent Technologies Proprietary

11

Primary and Secondary Dialing Class

start form

sub/vlr form
MIN _____
NSN _____

OMC _____
PDC
OR
SDC
PRC _____
RC _____

Dialing Class
Procr Type
Logical No.
Server Grp.
Ant. Face
Dialing Plan

.
Since PDC and SDC are used in digit analysis, we will
concentrate on PDC/SDC. PRC and RC are used during routing
and will be discussed later in this presentation
Lucent Technologies Proprietary

12

Primary and Secondary Dialing Class

Lucent Technologies Proprietary

13

Primary and Secondary Dialing Class

Lucent recommends to use Secondary Dialing Class (SDC) for most
used dialing plan and leave Primary Dialing Class null for specific
needs.

Lucent Technologies Proprietary

14

Summary: Step-1
In Step-1 we have seen:
Purpose of Sub form in routing the call
fields used to route the call to next phase start form
PDC/SDC and their usage

Lucent Technologies Proprietary

15

Step-2: Digit-by-Digit Analysis

Lucent Technologies Proprietary

16

Simple Call Flow

Step-2

Step-1

Step-2a

Step-2b
dplan form

sub/vlr form

start form

MIN _____
NSN _____

PDC _____
SDC _____
PRC _____
RC _____

OR

Dialing Plan ___

Pattern # ___
Query by Pat ____

Dialing Class __
Proc Type ___
Logical # ___
Server Grp ___
Ant. Face __
Dialing Plan ___

Step-2c

Pattern
________
Call Type _____
Dest Index ____
Prefix Type ____
# Digits to Del _____
Reanalyze __
DN Mod Type
____

Step-3b

Step-3a

rls form

dxdrte form
Dest Index ____
Rate Center ____
Switch Routing List:
RI 0
____
RI 1
____
Call Rte Type ___

Switch ID
__
Route Index ___
Route Class ___

OR

Step-3

tgl form
Switch ID ____
RLS
____

Trk Grp ____

Route List Sel __
Digs Deld ___
Prefix
____
Out Fmt ____
ANI
____
Lucent Technologies Proprietary

Step-4

To
DCS
17

Step-2a: Accessing the Start Form

start form

sub/vlr form

Dialing Class
Procr Type
Logical No.
Server Grp.
Ant. Face

MIN _____
NSN ______

OMC _____
PDC
SDC
PRC _____
RC _____

Dialing Plan

OR

If cell data is entered,

it must match data
received in the
origination request
message.

Lucent Technologies Proprietary

18

Step-2a: Accessing the Start Form

DxD analysis initiated from start form.

70
d
1

70

Lucent Technologies Proprietary

19

Step-2a: start form Searches

Call processing (CP) makes as many as six attempts to find a
matching start form.
CP-2 entry
CP Entry
Is subs PDC
populated?

No *

Is subs SDC
populated?

Yes
Does a
start form match
PDC+cell+face+
server
group?

Yes
Yes

Continue digit
analysis using
dialing plan from
start form.

Yes

No
Does a
start form match
PDC+cell?

No
Yes

Yes

No
No
Go to CP-2

Does a
start form match
PDC+switch?

Does a
start form match
SDC+cell+face+
server
group?

Does a
start form match
SDC+cell?

Send reorder
to sub and
defensive
check (assert)
failure message
to ROP.

No
Yes

Yes

Lucent Technologies Proprietary

Does a
start form match
SDC+switch?

No

20

Step-2a: start form-location based (Continued)

Configuration: # of MSC = 3
# of Cell = 75

Method

No. Start forms Required

Location DCS

Location Cell

75

Location Cell/Face/Server

225

Lucent Technologies Proprietary

21

Step-2a: Switch-based start form - Example 1

A group of subscribers is limited to dialing only local calls within one area
code. This example also assumes the simplest location data, switch of
origination.
Two DCSs in the system, DCS 1 and DCS 2.
Dial plan number 1 allows seven-digit dialing to all local NXXs.
A dialing class (PDC or SDC, typically SDC) of 1 for all subscribers in this
group.

Lucent Technologies Proprietary

22

Step-2a: Cell based start form Example

Lucent Technologies Proprietary

23

Step-2a: Pros and Cons: DC Vs. Location based

Organized By

Benefits

Weaknesses

Dialing Class

Simplicity
Less Start forms

Less CP efficiency because

of extra database reads
Less flexible

Location

Efficient CP
Very Flexible

Increase Complexity
More Start forms

Lucent Technologies Proprietary

24

Step-2b: Accessing the dplan form

The output of the start form identifies the dplan (dialing
plan) form to be used for analysis of digit patterns.
It is important to keep in mind that call processing relies
on the digit tables developed by the dplan forms; not
the dplan forms, themselves.
The output of the start form is a dialing plan number. The
dialing plan number is the number of a dplan form.

Dial Plan defines:

One number or number pattern dialed

within plan

Type of call related to this number pattern

How number should be modified,if

applicable

What information (Destination Index) should be

used

Lucent Technologies Proprietary

25

Step-2b: Dplan form

70
1

221 X(4)
1
2
n

Lucent Technologies Proprietary

26

Allowed Characters for Digit String

Lucent Technologies Proprietary

27

Digit Analysis Call Types

Lucent Technologies Proprietary

28

Digit Analysis Call Types - Continued

Lucent Technologies Proprietary

29

Step-2b: Dialing Plan Decisions

Division of mobile subscribers
Location-based variations
Call restrictions
Logically separated dialing patterns

Lucent Technologies Proprietary

30

Step-2b: Goals of Dialing Plan Team

Support all valid dialing patterns
Logical organization of dialing plans
Keep dialing plans small as possible
High-runners match first plan selected

Lucent Technologies Proprietary

31

Step-2b: Utility Programs: getdp

Lucent Technologies Proprietary

32

Step-2b: Utility Programs: dpsrch

Lucent Technologies Proprietary

33

Step-2b: Digit Tables

Digit tables are lookup tables generated from the data contained in
dialing plans. These tables are generated when the tg utility is
executed.

Lucent Technologies Proprietary

34

Step-2b: Types of Tables

PDTs (primary digit tables) - tables with 12 positions for *, #, and
digits 0 through 9. PDTs are used to sort digits until a match or
possible match is identified.
ATs (ambiguous tables) - tables used to decide if a match has been
identified or the analysis should continue.
RTs (resolution tables) - tables used to determine what happens
after a match is identified.
RE (resolution entry) - a subset of the resolution tables; every entry
in the RT is obtained from a corresponding RE.

Lucent Technologies Proprietary

35

Step-2b: Digit Table tree Analysis

Originating
Subscriber

Dialed Digits: 221 1212

start form
sub form

Dialing Class
Procr Type
Logical #
Server Grp
Ant. Face

MIN
NSN

PDC
SDC
PRC
RC

Digit table
tree for
dialing plan
70

Dialing Plan 70

OR

4
5
6

201

3
4

PD
T
to

PDT 202
0
1

202

3
4
5

310

1
2

Go

PDT 201

o
G

to

Head PDT 70

20
1
PD
T

20
2

PDT 2`
d
a
e
H
Go t o

Lucent Technologies Proprietary

RT 310
Four X digits
remain; treat
with RT 310:
call type = 1
(intra-SDCA) call

36

Step-2b: Example Dial Plan

Dial Plan

Pattern #

Pattern

Call Type

Dest.

# to del

Prefix Type

Reanalyze?

70

221 X(4)

During a call, digit analysis will use the data found in the digit tables which were generated
from the dplan forms. The following happens when the subscriber originates a call:
The subscriber dials 2211212 and presses the SEND button.
The serving cell sends an origination request message to the MSC.
CP searches the subscribers sub form for directions to a start form.
The start form directs CP to a digit table tree previously generated from dialing plan 70.
CP looks up the first digit, 2, in the head PDT (primary digit table) 70 and finds a cont
(continue analysis) action which points to PDT 201.
CP looks up the second digit, 2, in PDT 201 and finds a cont action which points to PDT 202.
CP looks up the third digit, 1, in PDT 202 and finds a done (analysis done) action which points
to RT (resolution table) 310.
CP moves to the associated RT to determine how to continue call routing. Because the
remaining 4 digits are all X format digits (0 through 9), a match is identified.
CP continues the call using call type 1 (intra-SDCA) to a destination of 2.

Lucent Technologies Proprietary

37

Step-2c: dnmod
During digit analysis, it may be necessary to modify the dialed digit
string. The dnmod (dialed number modification) form contains the
data used to modify dialed numbers during the digit analysis process.

Lucent Technologies Proprietary

38

Step-2c: Dnmod form

Lucent Technologies Proprietary

39

DN Modification Types

Lucent Technologies Proprietary

40

DN Modification Types - Continued

Lucent Technologies Proprietary

41

Step-2c: Dnmod form

Dialed digits can be altered during call processing by implementing
dnmod in the dial plan for the subscriber.

Lucent Technologies Proprietary

42

Step-2c: dnmod Selection Method

The dplan form selects dnmod using these fields:
DN Modification Type - contains the number to
be found in field 1 (DN Modification Type) of the
correct dnmod form.

Destination Index - contains the number to be found

in field 2 (DN Modification Index) of the correct dnmod
form.

Lucent Technologies Proprietary

43

Key Note on Dialing plan: Vacant Code Treatments

Vacant code treatment is used to handle following call processing
situations:
Incorrect dialed Digits
Restricted level of services

Vacant codes are patterns that do not match any pattern in a dialing
pattern or which may match a pattern determined to be handled
separately from valid patterns. One must provide a routing treatment
for vacant codes to give subscribers an indication of dialing errors or
attempts to dial digit strings not allowed for their level of service

Lucent Technologies Proprietary

44

Vacant Code Treatment Methods

There are two methods of providing vacant code treatment:
Implicit vacant code - treatment that is the same for all vacant
patterns that are not defined in a dialing plan (NEGITIVE dn match).
Explicit vacant code - identifies a specific pattern, which is defined in a
dialing plan as vacant (POSITIVE dn match).

Lucent Technologies Proprietary

45

Vacant Code: Implicit Code

Implicit vacant code treatment is typically used to provide a routing
safety net to catch any dialed digit strings that do not match a pattern
in the dialing plan.
Implicit vacant code treatment is assigned by running tg with the v
option.
Example: tg -d 1 -t db -o db -v 2

Lucent Technologies Proprietary

46

Vacant Code: Explicit Code

Explicit vacant code treatment provides a means of applying special
routing treatment for a number or range of numbers without
performing re-searches of DxD databases such as the startdb.

Lucent Technologies Proprietary

47

Implicit Vacant Code Example

Lucent Technologies Proprietary

48

Explicit Vacant Code Example

Lucent Technologies Proprietary

49

Summary
In this section/Step-2 we have Seen:
recognize the basic steps of call processing
identify the process of digit-by-digit analysis
identify the data organization used for digit analysis
concepts of digit-by-digit call analysis
identify the forms associated with DxD analysis which include the sub,
start, dplan, dnmod, and fscode forms
Identify the relationships between certain key fields and the efficiency of
call analysis with DxD routing
identify the basic design of a digit-by-digit dialing plan
identify the two methods of treatment of vacant codes
identify when and how to run the getdp software tool
identify when and how to run the tg software tool

Lucent Technologies Proprietary

50

Step-3: Digit Routing

Lucent Technologies Proprietary

51

Step-3: Digit Routing

Step-2

Step-1

Step-2a

Step-2b
dplan form

sub/vlr form

start form

MIN _____
NSN _____

PDC _____
SDC _____
PRC _____
RC _____

OR

Dialing Plan ___

Pattern # ___
Query by Pat ____

Dialing Class __
Proc Type ___
Logical # ___
Server Grp ___
Ant. Face __
Dialing Plan ___

Step-2c
Step-3b

Step-3a

rls form

dxdrte form
Dest Index ____
Rate Center ____
Switch Routing List:
RI 0
____
RI 1
____
Call Rte Type ___

Pattern
________
Call Type _____
Dest Index ____
Prefix Type ____
# Digits to Del _____
Reanalyze __
DN Mod Type
____

Switch ID
__
Route Index ___
Route Class ___

OR

tgl form
Switch ID ____
RLS
____

Trk Grp ____

Route List Sel __
Digs Deld ___
Prefix
____
Out Fmt ____
____
Step-3Lucent Technologies ProprietaryANI

Step-4

To
DCS
52

Step-3: Digit Routing

Call Routing: When a mobile telephone user originates a call, the
dialed digits must be analyzed and the call directed to a trunk. This
over-all process is referred to as call routing.
Call Routing Tasks: Basic tasks performed by call routing include:
Select a trunk group(s)
Determine digits to be outpulsed

Lucent Technologies Proprietary

53

Step-3a: DxDrte
The illustration below points out that the destination index of the dxdrte (digit-by-digit
route) form is obtained from either the output of the dplan form or the dnmod form.
The pointer from dplan or dnmod is used in conjunction with PRC from the sub/vlr
form and Prefix Type from dplan to select a specific dxdrte form.

Lucent Technologies Proprietary

54

Step-3a: DxDrte Form

70
16

Lucent Technologies Proprietary

55

Call Routing Types

Lucent Technologies Proprietary

56

Step-3b: Accessing RLS Form

The output of the dxdrte form is a pointer to an rls (route list selector)
form. The pointer from dxdrte is used in conjunction with RC from the
sub/vlr form and the DCS number to select a specific rls form.

Lucent Technologies Proprietary

57

RLS form

1
16
70
142

Lucent Technologies Proprietary

58

Step-4: tgl Allocation

Step-2

Step-1

Step-2a

Step-2b
dplan form

sub/vlr form

start form

MIN _____
NSN _____

PDC _____
SDC _____
PRC _____
RC _____

OR

Dialing Plan ___

Pattern # ___
Query by Pat ____

Dialing Class __
Proc Type ___
Logical # ___
Server Grp ___
Ant. Face __
Dialing Plan ___

Step-2c
Step-3b

Step-3a

rls form

dxdrte form
Dest Index ____
Rate Center ____
Switch Routing List:
RI 0
____
RI 1
____
Call Rte Type ___

Pattern
________
Call Type _____
Dest Index ____
Prefix Type ____
# Digits to Del _____
Reanalyze __
DN Mod Type
____

Switch ID
__
Route Index ___
Route Class ___

OR

tgl form
Switch ID ____
RLS
____

Trk Grp ____

Route List Sel __
Digs Deld ___
Prefix
____
Out Fmt ____
____
Step-3Lucent Technologies ProprietaryANI

Step-4

To
DCS
59

Step-4: tgl form

The output of the rls form is a pointer to a tgl (trunk group list) form.
The purpose of the tgl form is to provide the DCS with the trunk group selected, by the
ECP, to connect the mobile subscribers call. The trunk group may point to a looparound trunk group (mobile-to-mobile), an announcement trunk group, a land-line
trunk group to the PSTN (public switched telephone network), or some other
destination).

Lucent Technologies Proprietary

60

Tgl form

1
16

200 0

Lucent Technologies Proprietary

61

Outpulsing Format

Lucent Technologies Proprietary

62

Outpulsing Format - Continued

Lucent Technologies Proprietary

63

End-End Dialing Plan Flow

Lucent Technologies Proprietary

64

Conclusion
Understood Database implementation in Autoplex system and their
migration path
Understood 4 Step Routing and dialing plan process
Understood Various call routing related forms e.g. sub, start, dplan,
dnmod, dxdrte, rls, and tgl.
Understood the impact of each form on call routing
Understood dial plan tools e.g getdp and dpsrch

Lucent Technologies Proprietary

65

Backup Slides

Lucent Technologies Proprietary

66

Call Routing Overview

Feature

When a mobile call is originated, the dialed

digits must be analyzed and call directed to
trunk.

Read
fscode
form/db

Read
dxdrte
form/db

Read
rls
form/db

Read
start/dplan
forms/db

NO

Read
tgl
form/db

Mobile

Origination

Obtain
sub/vlr data

Read
pn
form/db

DN
Ported?

Read
dnmod
form/db

Outpulse
digits
Routing

Digit Analysis
Lucent Technologies Proprietary

67