TK301 PDF

TK301
EAGLE 5 ISS Release 40.1/EPAP Release 12.0
HLR Router for

GSM (G-Flex)
TK301v4.2
TEKELEC Confidential For Training Purposes Only
Table of Contents
Module #1 Basic GSM Network.....5
Module #2 G-Flex Architecture....27
Lesson 1 G-Flex HLR Manager.......29
Lesson 2 G-Flex Call Flow Update Location Messages......39
Lesson 3 G-Flex Call Flow SRI Messages........65
Module #3 G-Flex Configuration.81
Module #4 Optional Features..........99
TK301v4.2
Course Logistics
Course Instructor
Course Attendance and Participation
Certificate of course completion
Class Time and Breaks

Start and end
Lunch
Stretch, refreshment, etc.
Classmates
Tent card
Name, company, position
Background / experience
Security
Laboratory
Building
TK301v4.2
Student Guide Layout

In this guide, you will find the following structure:
Large units of learning are called Modules.
A Module is divided into smaller units of learning called
Lessons.
Each Module consists of:

Objectives for the entire module (aggregate of all lessons)
One or more lessons
Each Lesson consists of:

Lesson Objectives
Presentation and Lecture
Check-Your-Learning review questions
Hands-on Learning Activities (most lessons)
TK301v4.2
Module #1:
Basic GSM Network
TK301v4.2
Module #1
This module contains the following objectives:
Identify and interpret basic GSM terminology
Identify the purpose, function and contents of Number Plans
and Nature of Address Indicator
Review Simplified Call Flows without G-Flex
TK301v4.2
Basic GSM Knowledge
Basic GSM Knowledge
TK301v4.2
IMSI and MSISDN

The IMSI number is the unique number of the SIM
card given by an operator to a customer during
subscription
The MSISDN is a unique number of a mobile device
associated to an IMSI number
An IMSI number can be associated to either one or
several MSISDNs
An HLR stores IMSI numbers and their
associated MSISDN numbers
HLR
TK301v4.2
The HLR also contains subscriber profile

information and the number of the last VLR
where this subscriber was
Numbering Plan (NP)

The numbering plan value in the MSU is used to
indicate how a number is structured
Like GTT, the G-Flex feature basically works with
the information contained in the CdPA at the SCCP
level
In ITU, the NP field is used to understand the structure of
the GTA of the CdPA
TK301v4.2
10
Numbering Plan (NP)

In ITU, there are three kinds of Numbering Plans:
E.212
E.164
E.214
Depending on the type of transactions being

exchanged between the two SS7 nodes and the
configuration of the nodes, the appropriate NP is
then selected
TK301v4.2
10
11
Numbering Plan (NP)

E.212: This is the IMSI Numbering Plan
MCC
MNC
1 to 3
1 to 4
MSIN
National MSI
Maximum of 15 Digits
E.212 (International)
E.164: This is the MSISDN Numbering Plan

CC
1 to 3
NDC
SN
National (Significant) Number

E.212:
MCC stands for Mobile Country Code (uniquely identifies the country of the
subscriber)
MNC stands for Mobile Network Code (identifies the home GSM PLMN
(Public Land Mobil Network) of the subscriber)
MSIN stands for Mobile Subscriber Identification Number (identifies the
mobile subscriber within the GSM PLMN)
E.164:
CC stands for Country Code (uniquely identifies the country of the
subscriber)
NDC stands for Network Destination Code (area identifier for an operator)
SN stands for Subscriber Number
TK301v4.2
11
12
Numbering Plan (NP)

E.214 numbering plan is called the Roaming IMSI
It is a mixture of the numbering plans E.164 and E.212
CC
NC
MSIN
1 to 3
E.164
E.212
TK301v4.2
12
13
Numbering Plan (NP)

E.214 numbering plan is used to route the IMSI mobile
subscriber number when the destination address is not
known
In ITU network, all nodes have an E.164 number so the
beginning of an E.214 number is used for routing
because it has an E.164 format
E.214 format is used on ITU networks for the Update
Location MAP messages because, for this type of
transaction only, the IMSI is known and the destination
is unknown (so an E.164 number cant be used to
address a destination node)
TK301v4.2
13
14
Numbering Plan (NP)

E.214 converted example using E.164 and E.212
information
- E.164 information example
CC = 99 (Country identifier)
NDC = 70 (Geographical area identifier)
SN = 22222222222 (Subscriber Number)
- E.212 information example
MCC = 888 (Country identifier)
MNC = 01 (Network operator identifier)
MSIN = 1111111111 (Mobile Subscriber)
- E.214 international converted using previous information
99 70 1111111111 (CC + NDC + MSIN)
CC + NDC information is used for routing by SS7

nodes
TK301v4.2
14
15
Nature Address Indicator (NAI)

The Nature Address Indicator value in the MSU is
used to indicate how a number is formatted
As for GTT, the G-Flex feature basically works with
the information contained in the CdPA of the SCCP
level
In ITU, the NAI field is used to understand the format of
the GTA of the CdPA
TK301v4.2
15
16

In ITU, there are three types of NAI:
International
National
Subscriber
Depending on the level of transaction exchanged

between two SS7 nodes and the configuration of
the nodes, the appropriate NAI is then selected
TK301v4.2
16
17

E.164
CC + NDC + SN (International)
- 99 70 22222222222
NDC + SN (National)
- 70 22222222222
SN (Subscriber)
- 22222222222
TK301v4.2
17
18

E.212
MCC + MNC + MSIN (International)
- 888 01 1111111111
MNC + MSIN (National)

- 01 1111111111
MSIN (Subscriber)
- 1111111111
E.214
CC + NDC + MSIN (International)
- 99 70 1111111111
NDC + SN (National)
- 70 1111111111
SN (Subscriber)
- 1111111111
TK301v4.2
18
19
HLR Routing without G-Flex
HLR Routing & STP Configuration

without G-Flex
TK301v4.2
19
20
Typical HLR Routing

Typical HLR Routing is addressed by GTT from
STPs
Standard GTT can have a lack of flexibility when,
for example:
Some subscribers data has to be moved from one HLR
to another
Some subscribers have been ported out so some gaps
will be left in the HLR which can not be filled; therefore,
maximum HLR capacity can not be used (will be less than
100%)
TK301v4.2
20
21
Typical HLR Routing

For example: in case some new HLRs (HLR1,
HLR2) with higher capacity are purchased, this
could result in a reduction in the number of HLRs
required. This would then require a redistribution of
data from HLR3 to HLR1 and HLR2
New HLRs
Old HLR
HLR 1 HLR 2
STP
HLR 3
GTT tables need to be modified

to move the GTT result Point
Code for all MSISDN previously
stored in HLR3 to HLR1 and
HLR2
MSC
TK301v4.2
21
22
Typical HLR Routing

If some subscribers have been ported out, some
gaps will remain in the HLR which then can not be
filled to 100% capacity
Operator 1
HLR 1
HLR 2
Operator 2
HLR 1
GTT tables need to be modified to

delete those ported MSISDNs
STP
MSC
TK301v4.2
Possibly a range of GTT has to be split

to exclude those MSISDNs ported out,
and GTT capacity could therefore
quickly run out
The gap(s) created can not then be
filled totally, which means the HLR can
not be filled to 100% capacity
22
23
Learning Activity: Module 1
Learning Activities
Learning Activity: Define your network design

Purpose
To design a base line network without G-Flex routing.
Objective
After completing this exercise, students will set up a basic example of their
network and define the basic characteristics and call flows of their local network
without G-Flex.
Materials, Equipment, and References
Note Paper
Pencil
TK301v4.2
23

Instructions:
Use the following nodes to draw a small sample of your SS7 Network:
MSC
MSC or GMSC or MSC/VLR
HLR
HLR
STP
STP
Identify the following

1. Numbering Plan
2. Nature of Address Indicator
3. Data Requirements (MSISDN, IMSI, etc)
TK301v4.2
When completed, STOP and allow the instructor to verify your work.
24
25
Check Your Learning: Module 1

Answer the questions to the best of your ability.
We will review all answers as a group.
TK301v4.2
25

1. The ___________________________ number is the unique number of
the SIM card given by an operator to a customer during subscription.
2. The ___________________________ is the unique number of a mobile
phone associated to an IMSI number.
3. What is the purpose of the numbering plan?
__________________________________________________________
__________________________________________________________
4. E.212 is the _________________________ Numbering Plan.
5. E.164 is the _______________________ Numbering Plan.
6. E.214 is the _________________________________ Numbering Plan.
7. The E.214 numbering plan is used to
__________________________________________________________
___________________________________________________.
8. The E.214 format is mostly used on ITU networks for
_________________________________ MAP Messages.
9. Name three types of Nature of Address Indicator (NAI).
1. ___________________________________
2. ___________________________________
3. ___________________________________
TK301v4.2
26
Module #2:
GSM Flexible Numbering

(G-Flex) Architecture
TK301v4.2
27
28
Module # 2
This Module contains the following lessons:
Lesson 1 GSM Flexible Numbering (G-Flex) HLR Manager
Lesson 2 G-Flex Call Flow Update Location
Lesson 3 G-Flex Call Flow Send Routing Information (SRI)
TK301v4.2
28
Module #2
Lesson #1

(G-Flex)
HLR Manager
TK301v4.2
29
30
Module 2: Lesson 1
This lesson contains the following objectives:
Define the purpose and functions of the G-Flex feature
Define how the G-Flex node is deployed within the GSM
network
Analyze which Message Signaling Units (MSU) are affected
by G-Flex
TK301v4.2
30
31
G-Flex HLR Manager

G-Flex maintains a database with entries that map
a subscriber to an HLR
The database is constructed using IMSI or MSISDN
G-Flex intercepts SCCP messages destined for
HLRs and performs database lookup to identify the
HLR serving the subscriber
TK301v4.2
31
32
G-Flex HLR Manager

G-Flex basically represents an enhanced Global
Title Translation, analyzing all digits in the Called
Party address, which allows the flexible routing of
an E.164 or E.212/E.214 addressed SCCP
message to an HLR
TK301v4.2
32
33
G-Flex Architecture
G-Flex can be deployed as a standalone node
HLR 1
HLR 2
STP
HLR 3
G-Flex
G-Flex
STP
MSC
When an MSU destined to an HLR arrives to the STPs, it is routed to the G-Flex
node per GTT process
The G-Flex node finds the Point Code of the HLR and sends the MSU back to the
STPs which MTP3 route the MSU to the found HLR
TK301v4.2
33
34
G-Flex Architecture
G-Flex can be deployed along with an STP which is
the most common solution chosen
HLR 1
HLR 2
STP/
G-Flex
HLR 3
STP/
G-Flex
MSC
TK301v4.2
34
35
Which MSU are Concerned by G-Flex

G-Flex can be triggered for all MSUs destined to an
HLR
As an HLR receives MSUs with the MAP protocol,
only MAP protocol is affected by G-Flex
G-Flex is commonly used for the MAP Update
Location transactions when the Mobile Number
Portability is used within a country
TK301v4.2
35
36
Check Your Learning: Module 2 Lesson 1

TK301v4.2
36

1. The G-Flex database contains:
_____________________________
____________________________
2. The G-Flex process performs database lookups of SCCP messages
destined for HLRs. Why?
3. The G-Flex can be deployed as a____________________________
node or along with an _________________________ node.
4. Which G-Flex deployment is most common?
5. G-Flex can not be triggered for all MSUs destined to an HLR.
TRUE
FALSE
6. What type of message transaction is G-Flex commonly used for?
TK301v4.2
37
Student Notes
TK301v4.2
38
Module #2
Lesson #2
G-Flex Call Flow

Update Location Messages
TK301v4.2
39
40
Module 2: Lesson 2
Identify purpose and function of the Update Location
message
Analyze and interpret call flows using Update Location
Messages and how these messages are processed by the
G-Flex feature
Analyze and interpret how an EAGLE extracts data from the
Update Location MSU and uses that data for G-Flex
processing
TK301v4.2
40
41
Update Location MAP Message

An Update Location is a Map Operation initiated by
a VLR to an HLR to retrieve information about a
mobile
When a mobile is detected in the area managed by
a VLR, this VLR needs to contact the home HLR of
this mobile before allowing it to attach to its own
network
TK301v4.2
41
42

A VLR could be located on the same node as an
MSC or could be located on a separate node
The initial information a VLR has is the IMSI. The
VLR converts the IMSI into an E.214 number when
initializing the Update Location Message.
TK301v4.2
42
43
Country B
Country A
MSC/
VLR
MSC/
VLR
5
HLR
TK301v4.2
6
1- Update Location
2- Insert Subscriber Data
3- Insert Subscriber Data Ack
4- Cancel Location
5- Cancel Location Ack
6- Update Location Ack
43
44

This E.214 roaming number of the mobile is put in
the CdPA of the Update Location message
At this stage, the VLR does not know which HLR
needs to be requested for subscriber information
about the roaming subscriber
TK301v4.2
44
45

With the CC of the E.214 number, the Update
Location message can be routed to the
corresponding country
The VLR puts its own E.164 number in the CgPA of
the Update Location message to enable it to receive
the answer back from the roaming subscribers
home HLR
TK301v4.2
45
46
G-Flex Call Flow

An example of the two first transactions of an
Update Location MAP message on ITU network
Network 2
Network 1
E164 = 336644444444444
E164 = 99700000
PC = 2000
HLR
VLR
SS7 Network
STP
G-Flex
MSISDN = 997022222222222
IMSI = 888011111111111
TK301v4.2
46
47
G-Flex Call Flow: VLR to G-Flex

TRANSMISSION
DIRECTION
SCCP Fields
CgPA
CdPA
GTT is required
An HLR is requested
NI=0 RI=0
MSU sent
by the VLR
to the STP
VLR
STP
G-Flex
E214 Number: 99701111111111
GTI=4
SSN=1PC=0
SSN=6
TT=0
ES=BCD
NP=E214
NAI=INTL
Digit 2=9
Digit 4=0
Digit 6=1
Digit 8=
Digit 1=9
Digit 3=7
Digit 5=1
Digit 7=1
CgPA contain the VLR information as its SSN and its E164 number to be able to
receive the answer from the HLR
TK301v4.2
47
48
G-Flex Call Flow: Service Selector Table

As GTT is requested, this MSU arrives at the
EAGLE Database Module.
The service selector table is first looked up
EAGLE Database Module
G-Flex conditioning and
lookup into RTDB table
No match
yes
Service
GTT
Selector
no
Table
Use
lookup
results
MSU out to IMT

MSU in from IMT
Remeber, the EAGLE Database Module can be either a DSM or E5-SM4G card.
TK301v4.2
48
49
G-Flex Call Flow: G-Flex Triggered

Fields extracted from the CdPA by the EAGLE
NI=0 RI=0
GTI=4
Parameters
extracted from
the CdPA to find
a match in
Service
Selectors Table
SSN=1PC=0
SSN=6
TT=0
ES=BCD
NP=E214
NAI=INTL
Digit 2=9
Digit 4=0
Digit 6=1
Digit 8=
Digit 1=9
Digit 3=7
Digit 5=1
Digit 7=1
Service Selectors Table contains:
GTIN=4:SSN=6:TT=0: NP=E214:
NAI=INTL:SERV=GFLEX
G-Flex is
triggered
Because the ES field is used by the EAGLE internally, this parameter does not
have to be filled during the configuration.
TK301v4.2
49
50
G-Flex Call Flow: Number Conditioning

G-Flex service has been triggered
The GTA number is conditioned if needed before RTDB
lookup
No match
yes
Service
GTT
Selector
no
Table
Use
lookup
results
MSU out to IMT

MSU in from IMT
TK301v4.2
50
51

NI=0 RI=0
GTI=4
SSN=1PC=0
SSN=6
TT=0
ES=BCD
NP=E214
NAI=INTL
Digit 2=9
Digit 4=0
Digit 6=1
Digit 8=
TK301v4.2
Digit 1=9
Digit 3=7
Digit 5=1
Digit 7=1
GTA Number
extracted from
the CdPA to
perform a
RTDB lookup
51
52

From the NP and NAI fields previously extracted,
the G-Flex service will know how to condition the
GTA number
The GTA number is converted to international format, if it
is not already in that format, as the RTDB contains only
international numbers
The E.214 Numbering Plan is converted to E.212
because the numbers stored in the RTDB are stored in
E.212 format (never E.214)
- E214 -> E212
- 99701111111111 -> 888011111111111
TK301v4.2
52
53
G-Flex Call Flow: RTDB Lookup

After number conditioning, the RTDB lookup is
performed to try to find the converted E.212 number
RTDB Database contains:
IMSI 888011111111111, DPC 2000 RI:SSN
EAGLE Database Card

RTDB
Results information used to
modify fields of the MSU
before to route it to the next
node
If the IMSI is not found within the RTDB IMSI table, this message will fall through to
regular GTT.
TK301v4.2
53
54
G-Flex Call Flow: G-Flex to HLR Routing

SCCP Fields
TRANSMISSION
DIRECTION
MSU routed
by the STP
to the HLR
CdPA
NI=0 RI=1
MTP3 Fields
DPC=2000
GTI=4
SSN=1PC=0
SSN=6
TT=0
ES=BCD
NP=E214
STP
G-Flex
TK301v4.2
NAI=INTL
HLR
Digit 2=9
Digit 4=0
Digit 6=1
Digit 8=
Digit 1=9
Digit 3=7
Digit 5=1
Digit 7=1
54
55
G-Flex Call Flow: HLR to STP Routing

TRANSMISSION
DIRECTION
SCCP Fields
GTT is required
MSU routed
by the STP
to the HLR
NI=0 RI=0
VLR is requested
HLR
CdPA
STP
G-Flex
GTI=4
SSN=1PC=0
SSN=7
TT=0
ES=BCD
NP=E164
NAI=INTL
Digit 2=3
Digit 4=6
Digit 6=4
Digit 8=
Digit 1=3
Digit 3=6
Digit 5=4
Digit 7=4
The HLR looks up the requested information about this subscriber and answers
back (Update Location Ack) to the VLR by inverting CdPA and CgPA
TK301v4.2
55
56
G-Flex Call Flow: STP Routing to Next Node

As GTT is requested, this MSU arrives at the
No match
yes
Service
GTT
Selector
no
Table
Use
lookup
results
MSU out to IMT

MSU in from IMT
TK301v4.2
56
57
G-Flex Call Flow : STP Routing to Next Node

NI=0 RI=0
GTI=4
Parameters
extracted from
the CdPA to find
a match in
Service
Selectors Table
SSN=1PC=0
SSN=7
TT=0
ES=BCD
NP=E164
NAI=INTL
Digit 2=3
Digit 4=6
Digit 6=4
Digit 8=
Digit 1=3
Digit 3=6
Digit 5=4
Digit 7=4
NAI=INTL:SERV=GFLEX
No match found with the

extracted parameters
have to be filled during the configuration
TK301v4.2
57
58

MSU fall through GTT
No match
yes
Service
GTT
Selector
no
Table
Use
lookup
results
MSU out to IMT

MSU in from IMT
TK301v4.2
58
59

NI=0 RI=0
GTI=4
Parameters
extracted from
the CdPA to find
a GTT Selector
in the GTTSEL
Table
SSN=1PC=0
SSN=7
TT=0
ES=BCD
NP=E164
NAI=INTL
Digit 2=3
Digit 4=6
Digit 6=4
Digit 8=
Digit 1=3
Digit 3=6
Digit 5=4
Digit 7=4
GTTSEL Table contains:
GTIN=4:TT=0: NP=E214:
NAI=INTL:GTTSN=E164INTL
A match is found, the table

E164INTL has to be looked up
have to be filled during the configuration
TK301v4.2
59
60

NI=0 RI=0
GTI=4
SSN=1PC=0
SSN=6
TT=0
ES=BCD
NP=E214
NAI=INTL
Digit 2=9
Digit 4=0
Digit 6=1
Digit 8=
TK301v4.2
Digit 1=9
Digit 3=7
Digit 5=1
Digit 7=1
GTA Number
extracted from
the CdPA to
perform a
lookup into the
GTA Table
60
61

E164 INTL table is looked up to find the GTA (E164
number of the VLR)
E164INTL Table contains:
GTA: 336644444444444 DPC: 1000 RI:GT
EAGLE Database Card

E164INTL
node
TK301v4.2
61
62
MSU routed
by the STP
to the Next
Node
STP
G-Flex
TK301v4.2
MTP3 Fields
SCCP Fields
TRANSMISSION
DIRECTION
CdPA
NI=0 RI=0
DPC=1000
GTI=4
SSN=1PC=0
SSN=7
TT=0
ES=BCD
NP=E164
NAI=INTL
Next
Node
Digit 2=3
Digit 4=6
Digit 6=4
Digit 8=
Digit 1=3
Digit 3=6
Digit 5=4
Digit 7=4
62
63

TK301v4.2
63

1. Update Location is a ____________________________________________
initiated by a _________________________ to an _____________________ to
retrieve information about a mobile device.
2. The initial information that a VLR has about a mobile is its Roaming IMSI (E.212)
number.
TRUE
FALSE
3. When the Update Location message reaches an EAGLE with G-Flex, the
______________________________ table is the first table this message is sent
to.
4. What data is extracted from the SCCP CdPA for the purpose of matching
contents within the EAGLEs selector table?
1. __________________________________
2. __________________________________
3. __________________________________
4. __________________________________
5. __________________________________
5. If the GTA needs number conditioning, what two fields previously extracted from
the MSU will identify how to condition the GTA?
1. _______________________________
2. _______________________________
6. After number conditioning, the RTDB lookup is performed to try to find the E.212
number.
TRUE
FALSE
7. What can cause the Location Update message to be processed by regular GTT?
_______________________________________________________
8. When a match is found within the Service Selector Table and the RTDB, the
Location Update message will be sent to the
_______________________________.
TK301v4.2
64
Module #2
Lesson #3
G-Flex Call Flow

Send Routing Information (SRI)
Messages
TK301v4.2
65
66
Module 2: Lesson 3
Identify purpose and function of the Send Routing
Information (SRI) message
Analyze and interpret call flows using SRI messages
and how these messages are processed by the GFlex feature
Analyze and interpret how EAGLE extracts data from
the SRI MSU and uses this data for G-Flex
processing
TK301v4.2
66
67
SRI Message
A MAP Send Routing Information (SRI) message is
a request from a MSC (or GMSC) to an HLR to ask
where the mobile called is currently located
When the MSC receives the response from the
HLR, it is able to continue the routing setup process
A SRI message is call related using the E.164
Numbering Plan and will put the MSISDN of the
called mobile into the CdPA of the message
MSC and VLR can be located on the same node
TK301v4.2
67
68
G-Flex Call Flow

An example of an SRI MAP message on ITU
network
Network 2
Network 1
E164 = 99700000
PC = 2000
SS7 Network
GMSC
HLR
STP
G-Flex
E164 = 336644444444444
MSISDN = 997022222222222
MSISDN called = 997077777777777
TK301v4.2
68
69
G-Flex Call Flow: GMSC to G-Flex

TRANSMISSION
DIRECTION
SCCP Fields
CgPA
CdPA
GTT is required
An HLR is requested
NI=0 RI=0
MSU sent
by the MSC
to the STP
GMSC
STP
G-Flex
MSISDN = 997022222222222
MSISDN called = 997077777777777
GTI=4
SSN=1PC=0
SSN=6
TT=0
ES=BCD
NP=E164
NAI=INTL
Digit 2=9
Digit 4=0
Digit 6=7
Digit 8=
Digit 1=9
Digit 3=7
Digit 5=7
Digit 7=7
CgPA contain the MSC information as its SSN and its E164 number to be able to
receive the answer from the HLR
The SSN number of a MSC is eight
TK301v4.2
69
70
G-Flex Call Processing: Service Selector Table

As GTT is requested, this MSU arrives to the
No match
yes
Service
GTT
Selector
no
Table
Use
lookup
results
MSU out to IMT

MSU in from IMT
TK301v4.2
70
71
G-Flex Call Flow: G-Flex Triggered

NI=0 RI=0
GTI=4
Parameters
extracted from
the CdPA to find
a match in
Service
Selectors Table
SSN=1PC=0
SSN=6
TT=0
ES=BCD
NP=E164
NAI=INTL
Digit 2=9
Digit 4=0
Digit 6=7
Digit 8=
Digit 1=9
Digit 3=7
Digit 5=7
Digit 7=7
NAI=INTL:SERV=GFLEX
G-Flex is
triggered
ES field is used by the EAGLE internally, this parameter doesnt have to be filled
during the configuration
TK301v4.2
71
72
G-Flex Call Processing: Number Conditioning

G-Flex service has been triggered
The GTA number is conditioned if needed before RTDB
lookup
No match
yes
Service
GTT
Selector
no
Table
Use
lookup
results
MSU out to IMT

MSU in from IMT
TK301v4.2
72
73

NI=0 RI=0
GTI=4
SSN=1PC=0
SSN=6
TT=0
ES=BCD
NP=E164
NAI=INTL
Digit 2=9
Digit 4=0
Digit 6=7
Digit 8=
TK301v4.2
Digit 1=9
Digit 3=7
Digit 5=7
Digit 7=7
GTA Number
extracted from
the CdPA to
perform a
RTDB lookup
73
74

From the NP and NAI fields previously extracted,
the G-Flex service knows how to condition the GTA
number
The GTA number needs to be converted to the
international format if it is not already in that format, as
the RTDB contains only international numbers
The E164 Numbering Plan does not need to be
converted, as MSISDNs are stored in the RTDB database
TK301v4.2
74
75
G-Flex Call Processing: RTDB Lookup

After number conditioning, the RTDB lookup is
performed to try to find the E.164 number
RTDB Database contains:
MSISDN: 997077777777777 DPC: 2000 RI:SSN

RTDB
node
If the MSISDN is not found as a single MSISDN table, the range of MSISDN table
is looked up to try to find a range containing the MSISDN
TK301v4.2
75
76
G-Flex Call Flow: G-Flex to HLR

SCCP Fields
TRANSMISSION
DIRECTION
MSU routed
by the STP
to the HLR
CdPA
NI=0 RI=1
MTP3 Fields
DPC=2000
GTI=4
SSN=1PC=0
SSN=6
TT=0
ES=BCD
NP=E164
STP
G-Flex
TK301v4.2
NAI=INTL
HLR
Digit 2=9
Digit 4=0
Digit 6=7
Digit 8=
Digit 1=9
Digit 3=7
Digit 5=7
Digit 7=7
76
77
G-Flex Call Flow: SRI Acknowledgement

The SRI-Ack message sent back by the HLR to the
GMSC is routed in the same way as the Update
Location Ack
When the HLR answers back to the GMSC, the CdPA
and the CgPA of the MSU are exchanged
When SRI-Ack arrives at the STP, the Service Selector
lookup failes as the SSN from the CdPA is not six (to an
HLR)
Messages falls through GTT to be routed back to the
E.164 number of the GMSC
The SSN of the GMSC extracted from the CdPA is eight
(to an MSC)
TK301v4.2
77
78

TK301v4.2
78

1. A MAP SRI message is a request from ____________________________ to an
__________ to ask where the mobile ___________ is currently located.
2. The SRI message is _______________________________ using
_________________________ numbering plan.
3. Within the SCCP message, where will the MSISDN be located?
____________________________________________
4. What data is extracted from the SCCP CdPA for the purpose of matching
contents within the EAGLEs selector table?
1. __________________________________
2. __________________________________
3. __________________________________
4. __________________________________
5. __________________________________
5. If the GTA needs number conditioning, what two fields previously extracted from
the MSU will identify how to condition the GTA?
1. _______________________________
2. _______________________________
6. After number conditioning, what is the next G-Flex process for the SRI
message?
TK301v4.2
79
Student Notes
TK301v4.2
80
Module #3:
G-Flex Configuration
TK301v4.2
81
82
Module #3
This module contains the following objectives:
Identify the steps and EAGLE commands needed to
provision the G-Flex feature on the EAGLE
Identify the PDBI commands needed to provision
MNP data into EAGLE Database Modules
TK301v4.2
82
83
G-Flex Configuration Prerequisites

The SS7 configuration into the EAGLE STP is
presumed to be already done:
Point codes of the HLRs
Links, linksets and routes to those HLRs
The information will be used for MTP3 routing
As the G-Flex feature sits on GTT/EGTT features,

those have to be activated prior to G-Flex feature
activation
We presume GTT is already configured
We also presume the EAGLE Database Modules

have already been configured
TK301v4.2
83
84
G-Flex feature is activated by the commands
ENABLE-CTRL-FEAT:PARTNUM=893021701:FAK=XXXXX
CHG-CTRL-FEAT:PARTNUM=893021701:STATUS=ON
When a non-international number has to be

converted to an international format, it is necessary
to define the default E.212 MCC and MNC
CHG-GSMOPTS:DEFMCC=888:DEFMNC=01
Note: The default MCC and MNC can be used by the G-Flex and G-Port feature.
TK301v4.2
84
85
If G-Flex is used with an MSU in E.164 Numbering
Plan, it is necessary to define your CC and default
NDC in case the number has to be converted to
international format
CHG-STPOPTS:DEFCC=99:DEFNDC=70
TK301v4.2
85
86
If G-Flex is used with MSU in E.214 Numbering
Plan, it is necessary to first define your CC and
default NDC (if not already done) in case numbers
have to be converted to international format
CHG-STPOPTS:DEFCC=99:DEFNDC=70
Then it is necessary to define the internal

conversion table between CCNC and MCCMNC to
condition the number to E.212 Numbering Plan
before RTDB lookup
CHG-GSMOPTS:CCNC=9970:MCCMNC=88801
TK301v4.2
86
87
Service Selector entry for the Update Location
example
ENT-SRVSEL:GTIN=4:SSN=6:TT=0:NP=e214:NAI=INTL
:SNP=E214:SNAI=INTL:SERV=GFLEX
Optional parameter to specify how
the G-Flex service has to process
the number
Service triggered if all the

previous parameters matches
the MSU (GTIN, SSN, TT, NP,
NAI)
In the oldest release of EAGLE, the SSN had to be entered separately in another
table:
ent-gsm-ssn:ssn=20:obj=hlr
Only messages that met both ent-srvsel and ent-gsm were sent to G-Flex
For G-Flex service, SNP and SNAI is always equal to NP and NAI so it is not
necessary to define them
TK301v4.2
87
88
To load the VSCCP CARD with the RTDB, OAM,
GPL, and GTT data, once the G-Flex feature is
turned on, always boot the DSM cards with the
following command:
INIT-CARD:LOC=<DSM CARD>
To display IS-NR status of VSCCP card input:

REPT-STAT-CARD
TK301v4.2
88
89
To set the G-Flex service to be online, use:
CHG-SCCP-SERV:SERV=G-FLEX:STATE=ONLINE
This parameter specifies
the name of the service
(gflex , gport , mnp).
This parameter specifies the

state of the service (offline
or online). Re-routing is
performed when the service
state is offline.
Confirm success of activation with the following

commands:
REPT-STAT-SCCP
REPT-STAT-MPS
REPT-STAT-DB:DISPLAY=ALL
TK301v4.2
89
90
Data Provisioning of the Database Modules

The Customers Provisioning Database contains the
latest MNP information
This information must be sent to the EAGLE STP
through the MPS/EPAP platform to allow it to
correctly route G-Flex traffic
TK301v4.2
90
91
Provisioning Data Flow

Active
STP1
Database
Module
EPAP A Active PDBA

RTDB
Database
Module
RTDB
Database
Module
RTDB
RTDB
PDB
PDBI
RTDB
EPAP B
Standby
STP2
EPAP A
Database
Module
RTDB
Database
Module
RTDB
Database
Module
RTDB
RTDB
PDBA
Customers
Provisioning
Database
PDB
RTDB
EPAP B Active
TK301v4.2
91
92
Provisioning Configuration
Provisioning commands are sent to the Active PDBA
through the PDBI port
The HLR has to be entered first, if not already
configured
ent_entity(id 99700000, type SP, ri SSN, pctype NATL, pc 2000)
Command to
add a new SP
or a RN
Type of this
entity is a
Signaling Point
ID of this HLR,
usually its E.164
number
TK301v4.2
Point Code of the HLR and

its format
Final GTT to
this HLR
92
93
Then an IMSI or MSISDN can be associated with
this HLR
IMSI have to be provisioned if G-Flex is triggered for
E.212 and E.214
ent_sub(imsi 888011111111111, sp 99700000)
Command to
associate a new IMSI
to an HLR
IMSI number to
provisioned
ID of the HLR to
link to that IMSI
MSISDN have to be provisioned if G-Flex is triggered for

E.164
ent_sub(dn 997077777777777, sp 99700000)
MSISDN number to provisioned
TK301v4.2
93
94
IMSI and related MSISDN can be associated with
this HLR if G-Flex is triggered for E.212/E.214 and
E.164
Up to a maximum of 8 MSISDNs can be associated
to the same IMSI
ent_sub(imsi 888011111111111, dn 997022222222222,
sp 99700000)
TK301v4.2
94
95
Learning Activities
Learning Activity: G-Flex Activation

Purpose
To provide practical application on the steps and commands needed to provision and validate the
G-Flex service on the EAGLE STP.
Objective
After completing this exercise, the student will be able to locate the procedure within the EAGLE
Documentation Library to active the G-Flex service; to recognize the step and commands needed
to provision the G-Flex service on the EAGLE STP; and to use EAGLE commands to validate the
successful completion of G-Flex service activation.
Materials, Equipment, and References

EAGLE STP connected to the MPS/EPAP
EAGLE Commands Manuals:
Commands Manual
Feature G-Flex Manual
Instruction (s):
Follow directions for Student Assignments A and B.
Stop after each assignment, and let the instructor review your work.
TK301v4.2
95

Student Assignment A:
Using the parameter input values below, write out the EAGLE commands needed to
activate the G-Flex Feature.
PARAMETERS
INPUT VALUES
Feature Part Number
See Instructor
Feature Access Key
See Instructor
E.214 country code and network code
9070
Default GSM mobile country code
286
Default GSM mobile network code
01
E.212 mobile country code and mobile network code
28601
Default country code
90
Default network destination code
70
Global Title Indicator
National
Translation Type
Zero
Subsystem Number
Six
Number Plan
ISDN/mobile numbering Plan
Nature of Address Indicator
International
Service
Student Assignment B:
Where applicable, use the data from Assignment A and provision an EAGLE STP
for G-Flex activation.
TK301v4.2
96
97

TK301v4.2
97

1. Number the following in the correct procedural order.
_____ rept-stat-sccp
_____ rept-stat-db:display=all
_____ chg-ctrl-feat
_____ chg-stpopts
_____ rept-stat-mps
_____ init-card
_____ chg-gsmopts
_____ enable-ctrl feat
_____ rept-stat-card
_____ ent-srvel
_____ chg-sccp-serv
2. What is the function of the chg-gsmopts command?
3. What is the function of the chg-stpopts command?
4. What is the function of the ent-srvsel command?
5. The G-Flex data comes from the _____________________________

and is sent to the ______________________________ through the
______________________________ platform.
TK301v4.2
98
Module #4:
Optional Features
TK301v4.2
99
100
Module # 4
This Module contains the following objectives:
Identify the purpose and function of Optional
Features, such as:
EPAP Provisioning Blacklist
G-Flex SCCP Service Re-Route Capability
G-Flex Map Layer Routing
Identify and practice new EAGLE commands to

implement Optional Features
TK301v4.2
100
101
TK301v4.2
101
102

Problem/Need
If an E.164 address of an HLR is incorrectly provisioned
as a customers MSISDN, the incorrect provisioning can
caused severe outages in the network until the MSISDN
is removed and the customers MSISDN is correctly
provisioned. If this scenario occurs, all customers on this
HLR will be unable to receive calls until the situation is
corrected.
Currently, the provisioning of G-Flex data does not have
the ability to check for protected E.164 addresses (such
as HLRs) prior to processing the data record.
TK301v4.2
102
103

Solution
The EPAP Provisioning Blacklist feature provides a
blacklist functionality and allows the user to define a list
of prohibited address strings that are not allowed as DN,
DN Block, or IMSI address strings.
All G-Flex provisioning data will be checked against this
blacklist to prevent inadvertent population of protected
E.164 addresses into the G-Flex database as MSISDNs.
The E.164 addresses of all HLRs should be provisioned
in the provisioning blacklist.
TK301v4.2
103
104

Provisioning of the E.164 addresses for this feature is only
made via the EPAP GUI.
The EPAP GUI menus are used to add and delete G-Flex blacklist
ranges and are only accessible to the PDBA group and the User
Administration (uiadmin) user
The EPAP GUI is also used to retrieve, view, and delete entries in the
blacklist.
The G-Flex blacklist ranges are stored only in the PDB

database. G-Flex blacklist ranges are not sent to or stored in
the RTDB.
This feature provides for PDBI checks against the blacklist
ranges when the PDBI is used for the provisioning of DNs,
DN blocks, and IMSIs. The command is rejected if a conflict
is found.
A maximum of 150 blacklist ranges is supported by the EPAP.
TK301v4.2
104
105
G-Flex SCCP Service Re-Route

Capability
TK301v4.2
105
106

Problem/Need
If the G-Flex database is incoherent with MPS data and
the GTT data is valid, the EAGLE G-Flex node needs to
be able to handle and control re-routing of G-Flex traffic
from an affected node to alternate nodes within an
operators network.
Solution
The G-Flex SCCP Service Re-Route feature provides the
capability to re-route traffic from the EAGLE to other GFlex database nodes and inform the originating nodes to
re-route the G-Flex service related traffic to other G-Flex
service nodes.
TK301v4.2
106
107

This feature consists of the following main functions:
Service State
Indicates the current state of G-Flex (ONLINE or OFFLINE). If the state
is marked OFFLINE, the G-Flex will initiate re-routing procedure.
G-Flex Re-Routing
When G-Flex is marked OFFLINE and alternate PCs are provisioned,
any messages destined for G-Flex are re-routed to the available
alternate PCs that are defined for G-Flex.
If alternate PCs are not provisioned or none are available, then
messages destined for G-Flex will fall through to GTT.
This feature is enabled by defining a list of alternate PCs or by defining
the GTT option.
G-Flex Capability Point Codes

The use of G-Flex capability point code aids in notifying adjacent nodes
about G-Flex service outages.
TK301v4.2
107
108
TK301v4.2
108
109

Define alternate point codes to re-route G-Flex traffic.
Up to 7 alternate G-Flex nodes can be provisioned to
re-route all the incoming G-Flex traffic.
chg-sccp-serv:serv=GFLEX:pci1=1-1-1:rc1=10:
pci2=2-2-2:rc2=10:pci3=3-3-3:rc3=10:pci4=4-4-4:rc4=10
Command to
add, service,
and PCs with
associated RC
TK301v4.2
Parameter to
specifies service
name (gflex, gport,
mmp)
Parameters to add PCs to an

existing service group and
change the relative cost (RC) of
existing point codes in a group
109
110

Once provisioned, the G-Flex service can be
changed to OFFLINE.
chg-sccp-serv:serv=GFLEX:state=offline
Parameter to change the
G-Flex service state to
online or offline
TK301v4.2
110
111
G-Flex MAP Layer Routing
TK301v4.2
111
112

Problem/Need
In an ITU network, when a visited network entity (e.g. VLR,
GGSN, SGSN, or GMLC) needs to contact a home network
entity (e.g. AuC or HLR) given only the IMSI of a subscriber,
it will convert the E.212 IMSI into an E.214 MGT.
When an E.212 IMSI is converted into an E.214 MGT for
routing, the MSIN portion of the IMSI digits may be
truncated during this conversion when the resulting E.214
MGT exceeds 15 digits.
If this occurs, the message sent to the EAGLE for G-Flex
would not contain the complete MSIN, therefore the EAGLE
cannot reconstruct the missing MSIN digit. Thus, G-Flex
lookup may fail.
TK301v4.2
112
113

Solution
The G-Flex MAP Layer Routing feature allows subscriber
digits to be obtained from either the SCCP layer or the
MAP layer of a message during G-Flex database lookup.
This ability resolves the issue of truncation of digits by the
mobile switching center (MSC) that may occur in the
SCCP layer.
This feature allows the user to specify whether the
subscriber digits are obtained from the SCCP or MAP
layer when performing G-Flex database lookup.
TK301v4.2
113
114

This feature applies only to the following GSM messages:
MAP Update_Location,
Send_Parameters
MAP Send_Authentication_Information operations
These three MAP operations commonly encode the SCCP

CdPA GTA in the E.214 format (MGT) where trailing IMSI
digits may be truncated from MGT, and these messages
always include IMSI in the MAP layer.
CdPA digits from the SCCP layer are always used to route all
other MAP messages.
TK301v4.2
114
115

This command is used to specify whether G-Flex
MAP layer routing is performed.
chg-gsmopts:gflexmaplayerrtg=ON
Parameter defines
the G-Flex MAP
layer routing status
(ON or OFF)
The G-flex MAP Layer Routing feature must be

enabled and turned on before this parameter can be
specified.
TK301v4.2
115
116

TK301v4.2
116

1. The ___________________________________________ feature provides a
blacklist functionality to define a list of prohibited address strings that are not
allowed as ___________, _____________________________, or
______________________ address strings.
2. The EPAP Provisioning Blacklist can be provisioned on the EPAP and the
EAGLE.
TRUE
3.
FALSE
When G-Flex is offline, how will the G-Flex route SCCP messages?
_____________________________________________________________________
_____________________________________________________________________
____________________________________________________________
4. Which EAGLE command will define alternate point codes to re-route G-Flex
traffic?
a) chg-gsmopts
b) chg-stpopts
c) chg-sccp-serv
d) chg-ctrl-feat
e) none of the above
5. The G-Flex Map Layer Routing allows subscriber digits to be obtained from only
the MAP layer of the SCCP message during database lookup.
TRUE
FALSE
6. What is the command and parameter that defines the G-Flex MAP layer routing
status?
___________________________________________________________
TK301v4.2
117
118
Final Course Evaluation

Tekelec Course Evaluations are tools that help us
maintain the quality of our training programs.
Please complete the form, and return it to your
instructor upon completion of the course.
Thank You!
TK301v4.2
118

TK301 PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

TK301 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

TK301

EAGLE 5 ISS Release 40.1/EPAP Release 12.0

HLR Router for

TEKELEC Confidential For Training Purposes Only

TEKELEC Confidential For Training Purposes Only

Class Time and Breaks

TEKELEC Confidential For Training Purposes Only

Student Guide Layout

Each Module consists of:

Each Lesson consists of:

TEKELEC Confidential For Training Purposes Only

Basic GSM Network

TEKELEC Confidential For Training Purposes Only

TEKELEC Confidential For Training Purposes Only

Basic GSM Knowledge

Basic GSM Knowledge

TEKELEC Confidential For Training Purposes Only

IMSI and MSISDN

The HLR also contains subscriber profile

TEKELEC Confidential For Training Purposes Only

Numbering Plan (NP)

TEKELEC Confidential For Training Purposes Only

Numbering Plan (NP)

Depending on the type of transactions being

TEKELEC Confidential For Training Purposes Only

Numbering Plan (NP)

E.164: This is the MSISDN Numbering Plan

National (Significant) Number

TEKELEC Confidential For Training Purposes Only

Numbering Plan (NP)

TEKELEC Confidential For Training Purposes Only

Numbering Plan (NP)

TEKELEC Confidential For Training Purposes Only

Numbering Plan (NP)

CC + NDC information is used for routing by SS7

TEKELEC Confidential For Training Purposes Only

Nature Address Indicator (NAI)

TEKELEC Confidential For Training Purposes Only

Nature Address Indicator (NAI)

Depending on the level of transaction exchanged

TEKELEC Confidential For Training Purposes Only

Nature Address Indicator (NAI)

TEKELEC Confidential For Training Purposes Only

Nature Address Indicator (NAI)

MNC + MSIN (National)

TEKELEC Confidential For Training Purposes Only

HLR Routing without G-Flex

HLR Routing & STP Configuration

TEKELEC Confidential For Training Purposes Only

Typical HLR Routing

TEKELEC Confidential For Training Purposes Only

Typical HLR Routing

GTT tables need to be modified

TEKELEC Confidential For Training Purposes Only

Typical HLR Routing

GTT tables need to be modified to

Possibly a range of GTT has to be split

TEKELEC Confidential For Training Purposes Only

Learning Activity: Module 1

Learning Activity: Define your network design

TEKELEC Confidential For Training Purposes Only

Learning Activity: Module 1